Database Develop

[Q] cannot root 2.3.6 using DooMLoRD zergrush

I ran the runme.bat and everything seemed to run just fine, no errors. after reboot, I'm still at unroot. no SU permissions. BTW, I just want to root, not flash a custom ROM. Sorry I'm posting here. XDA wouldnt' let me add to the current thread about zergrush.
CODE:
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
720 KB/s (23060 bytes in 0.031s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000151e0
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40119cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd193a3 0xafd3908f
[*] Popping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
1222 KB/s (1075144 bytes in 0.859s)
--- correcting permissions
--- remounting /system
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
--- Free space on /system : 12380 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.503 secs (2137463 bytes/sec)
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
694 KB/s (22228 bytes in 0.031s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
--- pushing Superuser app
1169 KB/s (785801 bytes in 0.656s)
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .

i had the same problem i downloaded super one click and rooted my phone using that method it worked like a charm on the first try

Or you could just unlock it..

superoneclick is easy and quick
http://forum.xda-developers.com/showthread.php?t=803682
Sent from my Nexus One using Tapatalk

Thanks for the advice. I forgot to mention that I tried SuperOneClick as well. It told me that I was already rooted and did I want to run it anyway. I said yes. I tried Root Check Baisc and it said I'm rooted as well. the problem is when I open Terminal Emulation I get a $. If I type SU, I get permission denied. SU binary is up to date.
BTW, I'm primarily doing all this so I can clear dalvik-cache and perhaps move some of my apps to SD. Still can't do that.
If I open ADB shell on my computer, I can change $ to #, but after I reboot phone, it's back to no permissions.

what abt your firmware version? its impossible to root .62. you must downgrade it first to .58. Same was the case with and after downgrading it worked like a charm.
this helped me get there:
http://forum.xda-developers.com/showthread.php?t=1695514

[Q] Root problem

Hi all, i was update my droid 3 up to .906. Now i want root my device (never root before), can i use old method like one_click_root?

do a search for motofail. That is the only known method that works for the .906 update.

Failing to Root
I too am attempting to root my Droid 3 for the first time. I tried both motofail from Dan Rosenberg and MotorolaOneClickRoot from Pete Souza. Below is a screen capture of my attempt.
Phone specifics:
Motorola Droid 3 on Verizon Android version 2.3.4 System version 5.7.906.XT862
[*]
[*] Motofail: Universal Motorola Android Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
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
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Cleaning up...
/data/local/motofail: not found
rm failed for /data/local/motofail, No such file or directory
[*] Rebooting...
"[*] Exploit complete!"
"[*] Press any key to exit."
Press any key to continue . . .
Thanks in advance,
Bonsai144

Make sure that USB Debugging is selected (under menu->Applications->Development), and also make sure that you select Charge Only mode when you connect to your computer via USB.

For good measure, turn on "Never sleep while charging" or something along those lines. It should be near where you turn of USB Debugging.

linuxgator said:
Make sure that USB Debugging is selected (under menu->Applications->Development), and also make sure that you select Charge Only mode when you connect to your computer via USB.
Click to expand...
Click to collapse
+1
---------- Post added at 04:59 AM ---------- Previous post was at 04:57 AM ----------
LFerryT said:
Hi all, i was update my droid 3 up to .906. Now i want root my device (never root before), can i use old method like one_click_root?
Click to expand...
Click to collapse
you can find the sbf,motofail and .906 update all in my thread...link in my sig

You may also be missing drivers for it...
You can download the Moto Device Manager here
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
and this should be able to install the latest, proper drivers. These may not be needed, but it's just one more step in troubleshooting.

[Q] Motofail v905 = FAIL

Went to root the wife's phone today which has the 905 update on it, tried some of my old methods (pete's, tehRoot) they failed. So then found out the 'new hotness' is motofail. Downloaded that (not sure what version) and it failed as well. Can't seem to find an answer why, here's the output. Yes, Dev is enabled, USB Charging Mode, x64 moto drivers, Unknown Sources checked.
Code:
[*]
[*] Motofail: Universal Motorola Android Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
adb server is out of date. killing...
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
push: motofail/Superuser.apk -> /data/local/motofail/Superuser.apk
push: motofail/su -> /data/local/motofail/su
push: motofail/run.bat -> /data/local/motofail/run.bat
push: motofail/motofail -> /data/local/motofail/motofail
push: motofail/busybox -> /data/local/motofail/busybox
push: motofail/AdbWinUsbApi.dll -> /data/local/motofail/AdbWinUsbApi.dll
push: motofail/AdbWinApi.dll -> /data/local/motofail/AdbWinApi.dll
push: motofail/adb.exe -> /data/local/motofail/adb.exe
8 files pushed. 0 files skipped.
2667 KB/s (3972528 bytes in 1.454s)
[*] Owning phone...
/data/local/motofail: permission denied
[*] 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
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
[*] Cleaning up...
/data/local/motofail: permission denied
rm failed for /data/local/motofail, Is a directory
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
Ideas?
Thanks,
Chad

I don't know what to tell you. I used motofail several times on my 905 and had no problems whatsoever.
Sent from my DROID BIONIC using xda premium

Ditto. rooted it first go around after the patch.

Are there different versions of the motofail? Maybe I just have an old one?

Try this one http://www.corusa.com/public/motofail.exe Download to your desktop. Right click downloaded file (run as administrator) follow program prompts. Celebrate your rooted.

Ah That worked! Thanks. I had to go in and manually rm the files in /data/local/motofail and the directory however. Most likely one of the old exploits stuck stuff in there and motofail was unable to overwrite them. Either way. Rooted and Rootkeeper installed.
Thanks,
Chad

Good for you, glad it worked out. :victory:

phone will not root after software update

my droid 3 was previously rooted with no problem. i had the liberty rom on it, with safestrap, after a software update forced itself onto my phone, it pushed my phone between the root and unroot process. like it was trying to flash the stock rom back onto the phone and ended up with a mix of both. i was stuck in a setup screen and the only way to get my phone back to use was to factory reset my phone.
well now after the software update and all of that mess my phone will not root again! ive tried motofail and petestoolkit and neither worked. it told me it could not push the su, super user and busybox files onto it. it was able to edit local.prop. weird i just need a way to root my phone again, im guessing its the software update that is blocking it. it was update 5.5.1_84_d3g-66_m2-10
anyone know another method of root that my phone will allow? id think since its kind of an old phone there might be a solution :/
please and thank you

Tl;Dr but try zergrush
Sent from my GT-P5113 using xda premium

I just installed the .906 update and used MotoFail to root after the update. Worked fine.
Got it here --> vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment

i tried zergrush and it did not work this is what happened
---------------------------------------------------------------
Easy rooting toolkit (v3.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (16 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush"
2881 KB/s (23056 bytes in 0.007s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00016118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
4757 KB/s (1075144 bytes in 0.220s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .

Flash sbf, then reroot
Sent from my XT860 using xda app-developers app

go to my thread and download the 1click sbf. exe
follow the directions and sbf your device
once done download motofail also found in my thread
run it and follow the directions

Rooting Droid 4 Problem

Hi Guys,
I am trying to root my Droid 4 ICS 4.0.4 stock. However when I try it I keep getting this error...
Code:
[*]
[*] Motofail: Universal Motorola Android Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
[*] Device found.
[*] Deploying payload...
failed to copy 'motofail' to '/data/local/motofail': Permission denied
Unable to chmod /data/local/motofail: No such file or directory
[*] Owning phone...
/system/bin/sh: /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 File exists
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Cleaning up...
/system/bin/sh: /data/local/motofail: not found
rm failed for /data/local/motofail, No such file or directory
[*] Rebooting...
I also tried this one:
Code:
http://www.motoask.com/motorola-droid-4-xt894-updates-f146/rooting-motorola-droid-4-xt894-with-android-4-0-4-ics-t5761.html
But it closes for some odd reason
Any idea what the problem is? or any other tools recommended?

never mind, problem solved - got it rooted

andonecool said:
never mind, problem solved - got it rooted
Click to expand...
Click to collapse
What was the solution???

paulpas said:
What was the solution???
Click to expand...
Click to collapse
Yes, I'd really like to know as well. Looking into rooting my wife's D4, but I've never messed with Moto's before. Always had an HTC phone, so rooting was quite simple for me.

Hi, rooting process for droid 4 ics is quite simple too.. Just install drivers properly and use "droid 4 ICS tool". No worries.