Please has anyone gotten root on the mytouch by huawei/
Use a standard mode. If you have the adb drivers use any rooter.
Sent from my RK29 tab...
Bump
Sent from my T-Mobile myTouch using xda app-developers app
superbart007 said:
Bump
Sent from my T-Mobile myTouch using xda app-developers app
Click to expand...
Click to collapse
Sorry for my short answer but I recommend you to try (if you have adb drivers working) z4root or superoneclick.
The root process in Android is not as difficult as it seems. Just use a exploit to adb push files and change to rw system.
Sent from my RK29 tab...
I just attempted both of those root methods and also ZergRush nothing seems to work
darklink528 said:
I just attempted both of those root methods and also ZergRush nothing seems to work
Click to expand...
Click to collapse
Make sure to have the correct Adb drivers, sometimes the google drivers doesn't work with the oems driver...
If it doesn't work try with doomslord method. I'm getting without ideas
Sent from my RK29 tab...
Tried that one too nothing :/
What said the log, you get sucked at waiting for device ? Or were ?
Sent from my RK29 tab...
SferaDev said:
What said the log, you get sucked at waiting for device ? Or were ?
Sent from my RK29 tab...
Click to expand...
Click to collapse
I took a screenshot of where it gets stuck this one is Zergrush but superoneciclick gets stuck at waiting for device on step 7.
http://puu.sh/XigH
^^
Screenshot
darklink528 said:
I took a screenshot of where it gets stuck this one is Zergrush but superoneciclick gets stuck at waiting for device on step 7.
http://puu.sh/XigH
^^
Screenshot
Click to expand...
Click to collapse
Have you enabled USB debugging ?
Sent from my RK29 tab...
Yeah of course
darklink528 said:
Yeah of course
Click to expand...
Click to collapse
Then May be the vendor Id in the drivers !
Sent from my RK29 tab...
I'm having the same problem. I've rooted many Android devices. Yes USB debugging is enabled. Yes I can get adb access to the phone with a user level shell prompt. Yes it shows up in device manager as an Android Composite ADB interface. Yes I've added the PID and VID to android_winusb.inf.
Superoneclick gets stuck at step 7.
This phone seems like a decent phone for my wife (as a replacement for her stolen Samsung Galaxy S 4G), but it's LOADED with bloatware. I really need to figure out how to root this thing.
jb0ne said:
I'm having the same problem. I've rooted many Android devices. Yes USB debugging is enabled. Yes I can get adb access to the phone with a user level shell prompt. Yes it shows up in device manager as an Android Composite ADB interface. Yes I've added the PID and VID to android_winusb.inf.
Superoneclick gets stuck at step 7.
This phone seems like a decent phone for my wife (as a replacement for her stolen Samsung Galaxy S 4G), but it's LOADED with bloatware. I really need to figure out how to root this thing.
Click to expand...
Click to collapse
Try the doomslord method then. This method works pretty fine in lots of unnoficial or non tested devices.
SferaDev said:
Try the doomslord method then. This method works pretty fine in lots of unnoficial or non tested devices.
Click to expand...
Click to collapse
Thanks for the suggestion. Downloaded latest version of it (version 4). No luck.
Here's the output:
[*] Sending 149 zerglings ...
bugreport dir[/data/local/tmp] exist.
[*] 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
4038 KB/s (1075144 bytes in 0.260s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
32 KB/s (439 bytes in 0.013s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 98% bytes
test: 98%: 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 . . .
After that mount error I adb shelled in tried su for the heck of it and got permission denied. Also confirmed normal user can run mount. Checked df and /system is 370M, but only has 7M free. I wonder if that's the problem? How much space is needed for the zergrush method? Obviously I can't remove anything from /system if that is the problem. Also the df output is standard unix output so doesn't look like his bat file does very good error checking or does something odd.
For some problem the exploit doesn't works... Sniff...
make a request in ready2root.com
Sent from my RK29 tab...
Related
New day. I ran Dan's exploit again today and got root! Mod, feel free to delete post...
I'm having the same issue this is what i get when trying to root my Droid Razr
Easy rooting toolkit (v2.0)
created by DooMLoRD
Modified by Frasertag
Modified for Linux/Mac by Max Lee at DroidRazrRoot.com
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 (10 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) enable USB DEBUGGING
from (Menu\Settings\Applications\Development)
(2) enable UNKNOWN SOURCES
from (Menu\Settings\Applications)
(3) [OPTIONAL] increase screen timeout to 10 minutes
(4) connect USB cable to PHONE and then connect 2 computer
---------------------------------------------------------------
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
3108 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 ! 0x00019118
[*] 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
2604 KB/s (1075144 bytes in 0.403s)
--- 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 '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 'Superuser.apk' to '/system/app/./Superuser.apk': Read-only file system
--- cleaning
--- rebooting
--- WAITING FOR DEVICE
3562 KB/s (3104805 bytes in 0.851s)
pkg: /data/local/tmp/recovery.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
All Done, run Bionic Recovery from App Draw
Check out DroidRazrRoot.com for more cool hacks!
Matt's Utility!
Guarantee this Utility will get you rooted:
http://forum.xda-developers.com/showthread.php?t=1486718
same problem no solution
WVULTRA said:
Guarantee this Utility will get you rooted:
http://forum.xda-developers.com/showthread.php?t=1486718
Click to expand...
Click to collapse
I tried that and everything else and no dice... the problem i have is that i rooted once before and then unrooted to show my brother how it works and not i cannot root anymore... every utility i try says that it cant write an that it is read only or the location doesnt exist... i am so totally lost. can anyone help me?!?!?!?
lpoppe22 said:
I tried that and everything else and no dice... the problem i have is that i rooted once before and then unrooted to show my brother how it works and not i cannot root anymore... every utility i try says that it cant write an that it is read only or the location doesnt exist... i am so totally lost. can anyone help me?!?!?!?
Click to expand...
Click to collapse
I'm having the same problem... it fail to copy the files, then the phone restarts but still no root
jachar said:
I'm having the same problem... it fail to copy the files, then the phone restarts but still no root
Click to expand...
Click to collapse
http://goo.im/apps/mattlgroff/DroidRazrRoot404.zip
Use this to root, works on ics too
BakaPhoenix said:
http://goo.im/apps/mattlgroff/DroidRazrRoot404.zip
Use this to root, works on ics too
Click to expand...
Click to collapse
worked like a charm!!! thanks!
Hi all,
I have some problems with trying to root my Xperia Ray with the DooMLoRD's Easy Rooting Toolkit [v4.0](zergRush Exploit).
I have done all the pre-work, allowing USB debugging and unknown apps, connecting the device to the computer (Windows 7) per USB, drivers were installed automatically and I installed the Sync Companion, too. Starting the script --> Does not work.
Using adb then manually and working myself through the script, there is one line where the script stops working (all other command lines prior were working fine):
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
Error message: mount: permission denied (are you root?)
as all the other command lines depend on this command, there are more error messages later, but I guess this is the most crucial one. It seems for this command you need root access, but I dont have it (since I am trying to get it with the script... ;-) )
Any ideas how to get the command and the script working?
Device: Xperia Ray, Android Version 2.3.4, Build Number 4.0.2.A.0.69, Kernel Version 2.6.32.9-perf [email protected] #1
Cheers and thanks for helping!
Chris
You cant root the .69 firmware. Unless you flash a different kernel.
And please post your questions here http://forum.xda-developers.com/showthread.php?t=1450295
Sent from my ST18i using xda premium
boni2504 said:
Hi all,
I have some problems with trying to root my Xperia Ray with the DooMLoRD's Easy Rooting Toolkit [v4.0](zergRush Exploit).
I have done all the pre-work, allowing USB debugging and unknown apps, connecting the device to the computer (Windows 7) per USB, drivers were installed automatically and I installed the Sync Companion, too. Starting the script --> Does not work.
Using adb then manually and working myself through the script, there is one line where the script stops working (all other command lines prior were working fine):
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
Error message: mount: permission denied (are you root?)
as all the other command lines depend on this command, there are more error messages later, but I guess this is the most crucial one. It seems for this command you need root access, but I dont have it (since I am trying to get it with the script... ;-) )
Any ideas how to get the command and the script working?
Device: Xperia Ray, Android Version 2.3.4, Build Number 4.0.2.A.0.69, Kernel Version 2.6.32.9-perf [email protected] #1
Cheers and thanks for helping!
Chris
Click to expand...
Click to collapse
i am also have problem like him too...but i using Xperia Ray ICS 4.0.4 Build Number 4.1.B.0.431
GB 2.3.4 .69 and ICS 4.0.4 you can't
Root. Search for solution. Gb .42 and 4.0.3 can
Sent from my ST18i using XDA
snailboykh said:
i am also have problem like him too...but i using Xperia Ray ICS 4.0.4 Build Number 4.1.B.0.431
Click to expand...
Click to collapse
for 4.0.4, u have to downgrade the kernel to 4.0.3 and use the ics emulator hack exploit to root it. Then flash back to 4.0.4 kernel
Downgrade to fw.42 or 58 with flashtool.
I also have the same problems as you.
Which is better fw?
.42 or 58?
I cant share a link here cos i am a newbie. Just read my post yesterday...
Sent from my ST18i using XDA
guys i am trying to root my xperia ray with zerg rush
but its not working please help
[+] Found a GingerBread ! 0x00015118[*] 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
3016 KB/s (1075144 bytes in 0.348s)
--- 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 . . .
which version do you vant to root?
Please post your question in Q&A thread, its a development section.
If I were you, I would research regarding which FW's do the ZergRush exploit apply...
and please post in the proper thread...
There are rooting methods for each FW, please use search
and to the viewers, PLEASE DON'T TRY TO ANSWER THE QUESTION, it is better to redirect the user to the proper thread... so please let us break the cycle
Hi,
I went back to factory settings using CWM to try to root again and update ota to .62, but after I went back to factory I can't get it to root anymore
I am trying to use DooMLoRD_v4_ROOT-zergRush-busybox-su
This is what I get:
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
--- creating temporary directory
mkdir: permission denied
--- cleaning
rm: permission denied
--- pushing zergRush
461 KB/s (23060 bytes in 0.048s)
--- correcting permissions
chmod: permission denied
--- executing zergRush
./data/local/tmp/zergRush: permission denied
--- 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
2945 KB/s (1075144 bytes in 0.356s)
--- correcting permissions
chmod: permission denied
--- remounting /system
/data/local/tmp/busybox: permission denied
--- checking free space on /system
87 KB/s (439 bytes in 0.004s)
chmod: permission denied
./data/local/tmp/makespace: permission denied
--- copying busybox to /system/xbin/
dd: permission denied
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
chmod: permission denied
--- installing busybox
/system/xbin/busybox: not found
rm: permission denied
--- 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
chmod: permission denied
--- correcting symlinks
rm: permission denied
ln: permission denied
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
rm: permission denied
--- rebooting
ALL DONE!!!
Any ideas?
USB Debugging turned on? Unknown sources allowed? ADB drivers properly installed?
usb debugging was on, unknown sources allowed and I could adb shell... so I guess no problem there either.
For now I recovered the cwm backup I did before I tried going back to 'new'. 58 (to root and update to. 62)
I'll probably start trying again tomorrow.
Just to be clear I now reverted to a rooted .58
But I would like to be able to start over with. 58 (been messing around to much ), root it and update to. 62 (hoping to keep root).
I do have cwm installed, but no unlocked bootloader
All tips are welcome
Thanks
I tried to use a .58 firmware file and flashtool yesterday, but got problems with drivers.
Where can I get the correct driver for sk17i?
TIA
I got one step further using flashtool on my work pc, it rooted, but when trying to update ota, it gives 'could not install new software'...
It worked
Just to keep you guys updated, I downloaded the .58 ftf from http://forum.xda-developers.com/showthread.php?t=1529049 and installed it using flashtool...
I hate that moment when flashtool says 'Please wait. Phone will reboot' ... and it didn't, but just disconnecting it and pressing the power button worked fine
Next I used flashtool to force zergRush exploit: Got stuck at Waiting for device...
Then i rebooted manually with volume down button pressed as is sugested in
http://forum.xda-developers.com/showthread.php?t=1557924 while 'waiting for device.... this didn't work, I must have misunderstood the post.
After the reboot with volume down and failing to complete the root I tried it again and it worked, just to be sure I went to adb shell and tried su... it worked.
Time for a backup with cwm
Which got apparently uninstalled when using flashtool to go to .58 ... that's a lesson learned and probably logical,so I reinstalled it from the market ...
Strangely cwm installer had a force closed, but it didn't seem to affect anything.
Now for OTA update to .62 ... Done
Root still there? Yes
time for another CWM backup...
And I can go about messing with it again, freezing/uninstalling apps...
Thanks for the help
angelofhope said:
Just to keep you guys updated, I downloaded the .58 ftf from http://forum.xda-developers.com/showthread.php?t=1529049 and installed it using flashtool...
I hate that moment when flashtool says 'Please wait. Phone will reboot' ... and it didn't, but just disconnecting it and pressing the power button worked fine
Click to expand...
Click to collapse
Phone is restarted again to flashmode
That's why you have to disconnect and power up.
angelofhope said:
Next I used flashtool to force zergRush exploit: Got stuck at Waiting for device...
Then i rebooted manually with volume down button pressed as is sugested in
http://forum.xda-developers.com/showthread.php?t=1557924 while 'waiting for device.... this didn't work, I must have misunderstood the post.
After the reboot with volume down and failing to complete the root I tried it again and it worked, just to be sure I went to adb shell and tried su... it worked.
Click to expand...
Click to collapse
Phone has to be turned on in order to root
Just turn it on, make sure USB debugging and Unknown Sources are allowed and leave it on home screen for example.
After having some issues previously with ROMs randomly rebooting, I decided to unroot to UCKH7 and start over, using a different rooting method. Previously, since I was on UCK66, I used method 2c from this thread (http://forum.xda-developers.com/showthread.php?t=1311081). This time around I wanted to try method 2a, as it is the preferred method for UCKH7 build. I ensured that the flash counter was not tripped, downloaded and extracted DooMLoRD's Easy Rooting Toolkit v4.0, ensured I had necessary drivers, and enabled USB debugging, Unknown sources, and 10-minute screen timeout.
Upon running the "runme.bat" script, this is the message from the terminal window:
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
cannot stat 'files\zergRush': No such file or directory
--- correcting permissions
Unable to chmod /data/local/tmp/zergRush: No such file or directory
--- executing zergRush
./data/local/tmp/zergRush: not found
--- 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
2792 KB/s (1075144 bytes in 0.376s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
107 KB/s (439 bytes in 0.004s)
df: /mnt/.lfs: Function not implemented
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 44224 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!!!
All of this was in the span of 10 seconds. I searched the forums to see if anyone had any similar experience with I777 or in general, and the only thread I found was this one: http://forum.xda-developers.com/search.php?searchid=58896743
There doesn't seem to be a consensus as to what the issue may be, and I haven't seen any I777 users clamor about this. Is anyone familiar with the messages above? Thank you.
Phone details:
Model No: SGH-I777
Android version: 2.3.4
Baseband version: I777UCKH7
Kernel Version: 2.6.35.7
Build no: GINGERBREAD.UCKH7
wwjd3 said:
After having some issues previously with ROMs randomly rebooting, I decided to unroot to UCKH7 and start over, using a different rooting method. Previously, since I was on UCK66, I used method 2c from this thread (http://forum.xda-developers.com/showthread.php?t=1311081). This time around I wanted to try method 2a, as it is the preferred method for UCKH7 build. I ensured that the flash counter was not tripped, downloaded and extracted DooMLoRD's Easy Rooting Toolkit v4.0, ensured I had necessary drivers, and enabled USB debugging, Unknown sources, and 10-minute screen timeout.
All of this was in the span of 10 seconds. I searched the forums to see if anyone had any similar experience with I777 or in general, and the only thread I found was this one: http://forum.xda-developers.com/search.php?searchid=58896743
There doesn't seem to be a consensus as to what the issue may be, and I haven't seen any I777 users clamor about this. Is anyone familiar with the messages above? Thank you.
Phone details:
Model No: SGH-I777
Android version: 2.3.4
Baseband version: I777UCKH7
Kernel Version: 2.6.35.7
Build no: GINGERBREAD.UCKH7
Click to expand...
Click to collapse
Sorry no one helped you out, I can't say why it didn't work but I see "cannot stat 'files\zergRush': No such file or directory" That tells me you didn't extract the zip file and then run it from the extracted folder and NOT the .zip file.... 2c. wouldn't be the reason for the ROMS randomly rebooting it's the ROMS you flashed not the rooted KH7 package.... Always make sure before flashing any ROMS you wipe data/factory reset in recovery, then wipe cache & dalvik (I always wipe data/factory reset again after flashing the ROM) I can tell you I have been running AOKP for awhile with 0 issues maybe try that ROM.... GL
http://forum.xda-developers.com/showthread.php?t=1574718 Link to AOKP
The Rooting is taking forever also facing the adb server is out of date. killing...
Tried rooting my WT19i on .58 stock rom with GB. I used Flashtool to flash it with stock rom as it was on ICS before. Flashed successfully. But then after trying to root via this toolkit facing these errors. please help.
this is incomplete log.. process terminated later without rooting...
---------------------------------------------------------------
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
cannot open 'files\zergRush': No such file or directory
--- correcting permissions
--- executing zergRush
--- 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
2447 KB/s (1075144 bytes in 0.429s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
docrj said:
Tried rooting my WT19i on .58 stock rom with GB. I used Flashtool to flash it with stock rom as it was on ICS before. Flashed successfully. But then after trying to root via this toolkit facing these errors. please help.
this is incomplete log.. process terminated later without rooting...
---------------------------------------------------------------
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
cannot open 'files\zergRush': No such file or directory
--- correcting permissions
--- executing zergRush
--- 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
2447 KB/s (1075144 bytes in 0.429s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
Click to expand...
Click to collapse
You're kidding right? You don't even have a device with the same manufacturer and you come here asking for help?
Sent from my Zanpakuto using Getsuga Tensho!
ooops
Nick281051 said:
You're kidding right? You don't even have a device with the same manufacturer and you fine here asking fit help?
Sent from my Zanpakuto using Getsuga Tensho!
Click to expand...
Click to collapse
I had couple of tabs open and both had xda pages that were related to same doomlord issue. posted in the wrong one. Apologies.
docrj said:
I had couple of tabs open and both had xda pages that were related to same doomlord issue. posted in the wrong one. Apologies.
Click to expand...
Click to collapse
Ah okay well no harm no foul.
Sent from my Zanpakuto using Getsuga Tensho!
Nick281051 said:
Ah okay well no harm no foul.
Sent from my Zanpakuto using Getsuga Tensho!
Click to expand...
Click to collapse
I feel a bit harmed. . Like one third. I want compensation.
Phalanx7621 said:
I feel a bit harmed. . Like one third. I want compensation.
Click to expand...
Click to collapse
Nope nothing for you!
Sent from my Zanpakuto using Getsuga Tensho!
Nick281051 said:
Nope nothing for you!
Sent from my Zanpakuto using Getsuga Tensho!
Click to expand...
Click to collapse
I'm a saaaaad panda.
Hi guys,
i,ve tried rooting my phone with easy toolkit by Doomlord but it shows up the below message in the cmd which i dont understand cuz i,ve installed everything required and working such as adb and on firmware .42(i was on .62 and downgraded it) but it gave no result. helpppppppppppp:
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
360 KB/s (23060 bytes in 0.062s)
--- 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
476 KB/s (1075144 bytes in 2.203s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
27 KB/s (439 bytes in 0.015s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 172736 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 . . .
Make sure to enable 'unknown sources' in applications and 'usb debugging'
Sent from my Xperia Neo V using Tapatalk 2
iamdchosen1 said:
Make sure to enable 'unknown sources' in applications and 'usb debugging'
Sent from my Xperia Neo V using Tapatalk 2
Click to expand...
Click to collapse
yes, i did that but didnt work
How you downgrade it? Since by the error looks like you are still on .62
--
sent from my vacation
Madfysh said:
How you downgrade it? Since by the error looks like you are still on .62
--
sent from my vacation
Click to expand...
Click to collapse
i downgraded through flashtool and it went perfectly fine, in About Telephone section says that i,ve .42 firmware.
one question, did i need to enable adb debugging on or off for flashing? (i idid it with enabled debugging).
UmerRM said:
i downgraded through flashtool and it went perfectly fine, in About Telephone section says that i,ve .42 firmware.
one question, did i need to enable adb debugging on or off for flashing? (i idid it with enabled debugging).
Click to expand...
Click to collapse
Since ur phone will be in flashmode.. Doesn't matter if usb debugging is on or off.
Sent from my MT11i using Tapatalk 2
try flashtool....and post the output from it
find flashtool in the dev section
gregbradley said:
try flashtool....and post the output from it
find flashtool in the dev section
Click to expand...
Click to collapse
yes, finally. did it with flashtool. thanks to all, thanks a lot:good: