Results 1 to 7 of 7
Like Tree1Likes
  • 1 Post By doogald
  1. Thread Author  Thread Author    #1  
    joat1513's Avatar

    Posts
    1 Posts
    ROM
    5.7.906.xt862 2.3.4

    Default Droid 3-once rooted, since recent update, can no longer root

    I have a droid 3 which I had rooted once b4 and loaded a custom rom onto it. I had to fall back to the stock rom recently. I didn't think anything about it as I was sure I could re-root. However, my phone updated as soon as I went back to stock to a very recent Verizon update and now can no longer use my former rooting process to root. Can anyone help me please re-root my phone.....Before I try it, I wonder if anyone can answer a question for me.

    If I can get my stock image back to an earlier stock rom and successfully root, will I lose root if my phone automatically updates again?

    Phone:
    Droid 3
    5.7.906.xt862-------system version
    2.3.4------------------android version
    2.6.35.7-g5fa4155-kernel version

    Thanks for any help anyone can provide.
  2. #2  

    Default Re: Droid 3-once rooted, since recent update, can no longer root

    You can root using the Motofail method for the Droid 4 - it is reported to work fine for the Droid 3.

    The download and instructions are here:
    Thanked by 4:
    XXcgaXX likes this.
  3. #3  

    Default Re: Droid 3-once rooted, since recent update, can no longer root

    Thanks dooglad. I had the same basic issue as joat1513. This root method worked when the listed previously would not.
  4. #4  

    Default Re: Droid 3-once rooted, since recent update, can no longer root

    Motofail worked for me, with a Droid 3
  5. #5  

    Default Re: Droid 3-once rooted, since recent update, can no longer root

    Motofail method for Droid4 didn't work for my Droid3, ran it several times. Downloaded latest PC drivers from Motorola, phone is unlocked, Debugging Mode is on, and USB connection method is set to Charge.
    cannot stat 'motofail': No such file or directory
    Unable to chmod /data/local/motofail: No such file or directory[*] Owning phone...
    /data/local/motofail: not found[*] Rebooting device...[*] Waiting for phone to reboot.[*] Attemping persistence...
    remount failed: Operation not permitted
    failed to copy 'su' to '/system.bin.su'" Read-only file system
    Unable to chmod /system/bin/su: No such file or directory
    link failed Read-only file system
    etc, etc.. finishes off[*] Exploit complete!

    >.< Any ideas?

    Update: Tried manual root via adb shell
    mv /data/local/12m /data/local/12m.bak (entered ok)
    In -s /data /data/local/12m (returned error message: In permission denied)

    further attempts at continuing with manual rooting returned errors of permission denied and "failed for ... is a directory"

    Last edited by Hopcake; 02-14-2013 at 03:13 PM.
  6. #6  

    Default Re: Droid 3-once rooted, since recent update, can no longer root

    a few things to try
    reboot pc, turn off antivirus scanner,
    verify device is showing up in device manager correctly as I believe as adb interface>Mot Composite ADB Interface
    [ROOT] Framaroot, a one-click .APK to root
    I have verified it works with these Motorola devices running android 2.3.4
    Droid 2 (a955), Droid 2 Global (a956), R2D2 (a957), & Droid X (MB810)
  7. #7  

    Default Re: Droid 3-once rooted, since recent update, can no longer root

    Quote Originally Posted by Hopcake View Post
    Motofail method for Droid4 didn't work for my Droid3, ran it several times. Downloaded latest PC drivers from Motorola, phone is unlocked, Debugging Mode is on, and USB connection method is set to Charge.
    cannot stat 'motofail': No such file or directory
    Unable to chmod /data/local/motofail: No such file or directory[*] Owning phone...
    /data/local/motofail: not found[*] Rebooting device...[*] Waiting for phone to reboot.[*] Attemping persistence...
    remount failed: Operation not permitted
    failed to copy 'su' to '/system.bin.su'" Read-only file system
    Unable to chmod /system/bin/su: No such file or directory
    link failed Read-only file system
    etc, etc.. finishes off[*] Exploit complete!

    >.< Any ideas?
    Yes. The "cannot start 'Motofail'" suggests to me that you did not extract these files to a folder - in other words, unzip the Motofail_windows.zip file - and are instead trying to run Motofail from within the zip file. Right-click on the motofail_windows.zip file, extract the files to a folder on your PC (I suggest creating a folder called c:\motofail) and run the "run.bat" file from that folder; it will work fine.

Posting Permissions

B