[04/Jan][ROOTING/UNROOTING] DooMLoRD's Easy Rooting Toolkit [v4.0](zergRush Exploit)

[gidsxda]

Not working but found alternate

I'm using an ME863 (mainland China version) running Android 2.6.3. The zergRush method in this Toolkit gave me the "hellions" error and didn't work, but it appears that http://forum.xda-developers.com/showthread.php?t=1586570 has worked for me.
Thanks to DooMLoRD for trying, and please have a beverage on me to encourage you to keep trying! :good:

 

[peryp9]

Motorola Admiral - Latest ROOT Guide - January 2013

What slightly different commands? There was no link in your post.

Also trying to root a Moto Admiral, this would be greatly appreciated.

Bringing back threads from the dead ...


Motorola Admiral XT603 - Lazy people's root !! Works on the most recent update from January 2013 - 55.11.79 ... see attached RAR file, inside you will find MotoROOT.bat.

Anyone with the Admiral that lost root during recent software upgrade, just run the file in Administrator Mode. It will do all the rooting for you. More detailed instructions were posted here.


Good luck.

 

[drneely]

will this workwith the droid Milestone X with 4.5.604 v. 2.3.5


Nevermind guys, did it anyways hahah, worked like a charm

 

[Tauros360]

Tried on Motorola Fire XT530.. Did not work. Here is what I got -




---------------------------------------------------------------
Easy rooting toolkit (v1.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 zergRush exploit
(2) install Busybox (1.18.4)
(3) install SU files (3.0.5)
[*] 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
--- pushing zergRush"
459 KB/s (23052 bytes in 0.049s)
--- 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 ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x00015180
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x2abcdcf4 0x0064
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0x6fd25157 0x6fd39287
[*] Popping 8 more zerglings
[*] Sending 157 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
463 KB/s (1075144 bytes in 2.263s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Permission denied
--- 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': Permission denied
--- 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, No such file or directory
link failed Permission denied
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Permissio
n denied
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .

It does the same with my HTC ChaCha ! in the description it was writen that is supported...

 

[munmun]

bootloop

guy please help ...!!
i rooted my galaxy s II successfully but after some time it got switched off because of low battery.
now when i am restarting it ...it got struck in bootloop...
pleaes help//

 

[Lim Wee Huat]

guy please help ...!!
i rooted my galaxy s II successfully but after some time it got switched off because of low battery.
now when i am restarting it ...it got struck in bootloop...
pleaes help//

If there's no custom recovery and backup, I'm afraid you need to reflash stock via Odin..

Sent from my GT-I9003 using xda app-developers app

 

[rapak]

i get error ++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)



[+] Rush did it ! It's a GG, man !

[+] Killing ADB and restarting as root... enjoy!

export PS1=""

 

[Hermes300]

Hi Im in England and I have a SII on T-mobile UK , it has Tmobile branding and has some issues, mainly connectivity via the SIM card, which I have tested in another SII which didnt show such issues. Basically my SII never goes to H, only 3G if Im lucky. Then it will suddenly give me a page not found and no connection. When I first had it I think it was fine, but an update was applied automatically and since then it has been working intermittently. Its as if the update knocked out the modem-I can only really use it viw WiFi. Which makes it unusable away from the house. We submitted the phone to the Tmobile store (now EE) but it came back the same only factory reset.
Is there a kernel I can put on it which will fix this issue?

I notice in the compatibilty list this entry:
Samsung Galaxy S II for T-Mobile (SGH-T989), I guess this is applicable to my device?
I have rooted devices in the past but I hear the SII is a little more complicated!
Any help gratefully received!

Model number
GT-I9100
Android version 4.0.4
Baseband version
I9100BVLPE

Kernel version
3.0.15-I900BVLPH-CL969772
[email protected]#3
SMP PREEMPT Mon Jul 30 15:28:47 KST 2012

Build Number
IMM76D.BVLPH

 

[hamba9551]

Confirmed to be working on the following devices:

• Sony Xperia X10 (GB firmware)
• Sony Xperia Arc
• Sony Xperia Arc S
• Sony Xperia Play [R800i/R800x]
• Sony Xperia Ray
• Sony Xperia Neo
• Sony Xperia Neo V
• Sony Xperia Mini
• Sony Xperia Mini S51SE
• Sony Xperia Mini Pro
• Sony Xperia Pro
• Sony Xperia Active
• Sony Xperia Live Walkman
• NTT Docomo Xperia ARCO SO-02C
• Samsung Galaxy S2 [GT-i9100/i9100P/i9100T]
• Samsung Galaxy S II for T-Mobile (SGH-T989)
• Samsung Galaxy S II for AT&T (SGH-I777), Skyrocket (SGH-i727)
• Samsung Galaxy S II LTE Rogers Canada (SGH-I727R), Android version 2.3.5, Baseband version I727RUXKJ7
• Samsung Galaxy S II Epic 4g Touch
• Samsung Galaxy S2 HD LTE (SHV-E120S)(korea)
• Samsung Galaxy S2 LTE (SHV-E110S)
• Samsung Galaxy S2 LTE Japanese version (carrier DoCoMo) [SC-03D] (2.3.6) {OMKK3}
• Samsung Galaxy i9100G
• Samsung Galaxy S [i9000B] & [i9000 2.3.3 (PDA I9000BOJV8, Phone I9000XXJVO, CSC I9000GDTMJV7) and german T-Mobile branding], XWJVW (2.3.6)
• Samsung Galaxy S 4G (aka SGH-T959V)
• Samsung Galaxy S Plus (GT-I9001) OS 2.3.3 and 2.3.6 (I9001ZSKP6) & 2.3.4 firmware (i9001XXKP4)
• Samsung Galaxy Mini GT-S5570 (GB only)
• Samsung Galaxy Mini Pro i5510
• Samsung Galaxy W [i8150]
• Samsung Galaxy Y
• Samsung Galaxy Y pro [B5510] (2.3.5)
• Samsung Galaxy Tab [P1000] (2.3.3 firmware), [P1000N]
• Samsung Galaxy Note [N7000]
• Samsung Galaxy Player YP-G70 2.3.5 (GINGERBREAD.XXKPF)
• Samsung Galaxy Ace (2.3.3, 2.3.4 firmware)
• Samsung S5670 FIT DDKQ5 2.3.5
• Samsung Nexus S [i9023] (2.3.6)
• Samsung Nexus S 4G 2.3.7
• Samsung Galaxy Nexus S [i9020] (2.3.6) & Nexus S i9020A (2.3.6)
• Samsung Exhibit (SGH-T759)
• Samsung Exhibit 4G (SGH-T759) (2.3.3) Build UVKE8
• Samsung Epic 4G
• Samsung Captivate i897 UCKH3
• Motorola ATRIX
• Motorola Milestone 3 [ME863 HK]
• Motorola Milestone 2 with Gingerbread
• Motorola XT860, Bell XT860
• Motorola Defy+
• Motorola Droid X sys ver 4.5.605 w/ gingerbread
• Motorola Droid X2 (2.3.4) Sys ver 1.3.380.MB870.Verizon.en.US Build 4.5.1A-DTN-150-30
• Motorola XT883 (China Telecom)
• Motorola XT862 (Verizon Droid3)
• Motorola DROID RAZR
• Nexus One (2.3.6 stock)
• LG Revolution
• LG Nitro HD
• Vizio VTAB1008 Tablet
• Huawei Ideos U8150 (2.2)
• Huawei Ideos X5 [U8800] (2.3.5)
• HTC Sensation (S-OFF only)
• HTC Raider (Rogers)
• HTC Chacha
• Acer Liquid Mini (2.3.5)
• Acer Liquid Metal (2.3.6)

hello, im using Samsung Galaxy S2 HD LTE (SHV-E120L) running stock 4.1.2>>juast try to root using DooMLoRD_v4_ROOT-zergRush-busybox-su>>FAILED!!! any SUGGESTION for sharing?? please help me..really need to root my phone...hurmmm..

 

[bombaybadboy]

hello, im using Samsung Galaxy S2 HD LTE (SHV-E120L) running stock 4.1.2>>juast try to root using DooMLoRD_v4_ROOT-zergRush-busybox-su>>FAILED!!! any SUGGESTION for sharing?? please help me..really need to root my phone...hurmmm..

Dont no enough about your device but this thread may help
http://forum.xda-developers.com/showthread.php?p=22256156#post22256156

Sent from my GT-I9100 using xda premium

 

[Ccasarguedas]

Xperia Active

Thank you very much!!!
It worked nice on my Xperia Active.:good:

 

[leo_kendall]

if u could help me to root my phone canadian motoluxe i'll send ya a 6 pack of beer lol.

 

[Erdiou]

Any support for the Walkman Z?

Android 4.0.4; Kernel: 2.6.39.4

I assume that the Tablet S ICS-ROM is identical to the Walkman Z-ROM, but the player can't get root from the toolkit.

If additional files needed, Like a system dump? I can supply files. :angel:

 

[amir2418]

could someone help me to root my lg su640 2.3.5 i have tried this method over and over still same results getting this error pls correct me if i was doing wrong i don,t understand why it wont copy busybox into the system files pls help me. thanks in advance

--- 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
3267 KB/s (1075144 bytes in 0.321s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
109 KB/s (439 bytes in 0.003s)
export: 14%: bad variable name
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: Read-only file system
--- correcting permissions
Unable to chmod /system/xbin/busybox: Read-only file system
--- installing busybox
--install: applet 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 . . .

 

[fits79]

I try that method at sony xperia u with android 2.3.7 and nothing happened the mobile DOESN'T ROOTED.

So can anyone tell me what i do wrong?

 

[Mathubala420]

Any idea for Hcl me u2

No developers is coming to give a tutorial for rooting HCL ME U 2 ...pkease give us a tutorial to root that device... Can we root or not? You devs have given many rooting procedure for many devices and its a shame that we cannot root a small budget device...that is Hcl....Even Doomlord cant do it? tried zergrush and other methods but none roots...

 

[Spidinator]

Tried this on my Xperia Ray following the guide using flashtool to .562 first and then back to .431 but I keep getting this. Any ideas?

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
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- 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.

[-] Not a 2.2/2.3 Android ...
--- 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
4486 KB/s (1075144 bytes in 0.234s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
--- Free space on /system : 63724 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/bin/sh: /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 . . .

 

[Ccasarguedas]

I had the same problem with my Xperia Active. what I did it was to turn the antivirus software off(avg), then tried again and worked fine, after the procces turn avg back on. It might be the same problem you are having.
Hope that works for you.

Sent from my GT-B5510L using Tapatalk 2

 

[IronBlossom]

didnt worked for me!!! Neo v 2.3.4 .62

 

[micallen]

Droid X2 running 2.3.5. What do I need to do???


Thanks,


---------------------------------------------------------------
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
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
900 KB/s (23060 bytes in 0.025s)
--- 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 ...
[*] 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
1955 KB/s (1075144 bytes in 0.537s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
85 KB/s (439 bytes in 0.005s)
--- Free space on /system : 72% bytes
test: 72%: bad number
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
rm: can't remove '/system/app/Maps.apk': Read-only file system
--- 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 . . .