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

Ned help with this please

i didnt found a solution. i have a problem with the root. i cant root mi galaxy note.
my phone info is....
samsung gt-n7000
gingerbread 2.3.6
kernel 2.6.35.7-n7000vskl1-cl778075
[email protected] #2
compilation gingerbread.vskl1
have the same problem of many ppl here.
---------------------------------------------------------------
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
--- cleaning
--- pushing zergRush"
2251 KB/s (23056 bytes in 0.010s)
--- 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 ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] 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
2282 KB/s (1075144 bytes in 0.460s)
--- 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 . . .

lfcpato said:
i didnt found a solution. i have a problem with the root. i cant root mi galaxy note.
my phone info is....
samsung gt-n7000
gingerbread 2.3.6
kernel 2.6.35.7-n7000vskl1-cl778075
[email protected] #2
compilation gingerbread.vskl1
have the same problem of many ppl here.
---------------------------------------------------------------
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
--- cleaning
--- pushing zergRush"
2251 KB/s (23056 bytes in 0.010s)
--- 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 ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] 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
2282 KB/s (1075144 bytes in 0.460s)
--- 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 . . .
Click to expand...
Click to collapse
Flash stock rom kk9 via Odin and use root files kk9 and should be good to go as its a directly root able rom

+1 above
You are on later versions of the ROM which are not directly rootable.

[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:

problems with rooting

Im trying to root my galaxy mini 2.3.6 with DooMLoRD_v4_ROOT-zergRush-busybox-su and can't get it work. When I start rooting it shows me this msg:
Code:
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
1443 KB/s (23060 bytes in 0.015s)
--- 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
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] 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
3831 KB/s (1075144 bytes in 0.274s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
71 KB/s (439 bytes in 0.006s)
df: /mnt/.lfs: Function not implemented
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 17244 bytes
--- no cleanup required
--- 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 . . .
what's wrong?

first, wrong section
trx it with a update.zip root package via stock recovery to get root.
cause your problem is the firmware u wanr to root!
Sent from my GT-S5660 using xda app-developers app

But my phone have no recovery. I bought it few days ago and I get it with 2.3.6 by default. what to do?

it has one, a stock samsung one,
which makes hlupdate.zip's aviable
Sent from my GT-S5660 using xda app-developers app

There's something noobs don't always understand: THERE IS A ****ING GENERAL SECTION.

how can I get that recovery?
i tried with pressing some buttons but cant get it in

wrong section
press and hold volume up AND home button, while pressing buttons turn the phone on and apply update.zip from menu

Just a reminder, the only things that belong in Development are things that you have created yourself. Not questions. Your thread has been moved.

no problem about topic

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.