Sorry for being such a noob. I've followed every instruction to the "T".
I've unlocked the bootloader from HTC with no problems. Then I ran OneClickRoot_1.1... it stated I had achieved Perm root. But no su binary is found. I tried to manually install Superuser from the market as well as busybox. I can't figure it out. I've researched these forums for hours. I also made sure phone was in "Charge only", usb debugging was enabled, and HTC Sync was closed.
Does this have anything to do with me accepting the OTA on Thursday, before I tried to root. Please help. I'll include the script from the OneClick.
Press any key to continue . . .
--- WAITING FOR DEVICE ---
--- Device Connected ---
Checking for previous attempts...
Pushing Zergrush...
2251 KB/s (23060 bytes in 0.010s)
Setting Permissions...
Gaining Perm Root (Aka running 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 ---
--- Device Connected ---
Pushing Busybox
2592 KB/s (1075144 bytes in 0.405s)
Setting Permissions...
Remounting System...
mount: permission denied (are you root?)
Coping Busybox to /system/xbin/...
/system/xbin/busybox: cannot open for write: Read-only file system
Installing Busybox...
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
Installing Superuser...
failed to copy 'tools\su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
failed to copy 'tools\Superuser.apk' to '/system/app/./Superuser.apk': Read-onl
file system
Removing tools That Was Pushed To Data...
Congrats You Are Now Perm Rooted...
Press any key to continue . . .
I assume this is this the one click root NilsP posted? That one worked great for me. Make sure USB debugging is enabled and you have checked the box under applications to enable use of non-market apps.
If you continue to have issues, flash the AmonRa recovery via fastboot and under Developer Options you can choose to install superuser while in recovery.
You will have to flash Amon Ra recovery through fastboot. There is info about that in development thread. Read through first few pages of Amon Ra thread. Once you have recovery, boot it up from hboot, and then install su and superuser from development section in Amon Ra recovery. The only confusing part for me was preparing to flash Amon Ra thru Windows command prompt due to my inexperience. PM me for further assistance. Good luck. One click does not work for the OTA.
Thanks guys...wish me luck
Kbartley77 said:
Thanks guys...wish me luck
Click to expand...
Click to collapse
You should be able to put Amon Ra inside the same folder you just used for unlocking. Then use command:
Fastboot flash recovery (nameofrecoveryfilehere)
You will need to add .IMG to the file name for it to work.
Sent from my ADR6425LVW using Tapatalk
Kbartley77 said:
Sorry for being such a noob. I've followed every instruction to the "T".
I've unlocked the bootloader from HTC with no problems. Then I ran OneClickRoot_1.1... it stated I had achieved Perm root. But no su binary is found. I tried to manually install Superuser from the market as well as busybox. I can't figure it out. I've researched these forums for hours. I also made sure phone was in "Charge only", usb debugging was enabled, and HTC Sync was closed.
Does this have anything to do with me accepting the OTA on Thursday, before I tried to root. Please help. I'll include the script from the OneClick.
Press any key to continue . . .
--- WAITING FOR DEVICE ---
--- Device Connected ---
Checking for previous attempts...
Pushing Zergrush...
2251 KB/s (23060 bytes in 0.010s)
Setting Permissions...
Gaining Perm Root (Aka running 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 ---
--- Device Connected ---
Pushing Busybox
2592 KB/s (1075144 bytes in 0.405s)
Setting Permissions...
Remounting System...
mount: permission denied (are you root?)
Coping Busybox to /system/xbin/...
/system/xbin/busybox: cannot open for write: Read-only file system
Installing Busybox...
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
Installing Superuser...
failed to copy 'tools\su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
failed to copy 'tools\Superuser.apk' to '/system/app/./Superuser.apk': Read-onl
file system
Removing tools That Was Pushed To Data...
Congrats You Are Now Perm Rooted...
Press any key to continue . . .
Click to expand...
Click to collapse
if you can't root using oneclickroot,
flash AmonRA recovery using cleanflash
then install su and superuser under Developer menu under AmonRA recovery.
Amonra Recovery: http://forum.xda-developers.com/showthread.php?t=1339679
Cleanflash: http://forum.xda-developers.com/showthread.php?t=1416791
Same Issue
feralicious said:
You should be able to put Amon Ra inside the same folder you just used for unlocking. Then use command:
Fastboot flash recovery (nameofrecoveryfilehere)
You will need to add .IMG to the file name for it to work.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Hello, I am having the same issue. I use Clean Flash 1.0, and the image file from Amonra PH98IMG.zip. Everything says that it worked. I load SU through Recovery. No icon appears under Apps for superuser so I go to the market and load SuperUser. The first time I run Root Explorer the SuperUser image appears allowing me to grant approval. When I go into Terminal Emulator and type SU I am granted access. So I restart my phone and go back to Terminal Emulator, when I type SU I get Access Denied. The one thing that is stated here and in another thread is the part about "Fastboot flash recovery (recovery.img)". What is this and were is it done? Do you type it just as shown minus the quotes? Is that what I am missing and causing a permanent root to act like a temporary root.
Thank you for your help.
dnvm said:
Hello, I am having the same issue. I use Clean Flash 1.0, and the image file from Amonra PH98IMG.zip. Everything says that it worked. I load SU through Recovery. No icon appears under Apps for superuser so I go to the market and load SuperUser. The first time I run Root Explorer the SuperUser image appears allowing me to grant approval. When I go into Terminal Emulator and type SU I am granted access. So I restart my phone and go back to Terminal Emulator, when I type SU I get Access Denied. The one thing that is stated here and in another thread is the part about "Fastboot flash recovery (recovery.img)". What is this and were is it done? Do you type it just as shown minus the quotes? Is that what I am missing and causing a permanent root to act like a temporary root.
Thank you for your help.
Click to expand...
Click to collapse
go here
http://forum.xda-developers.com/showthread.php?t=1466474
Im in the same boat.. I took the ota update and now i cant root. I tried going into cmd to flash the recovery img, and it says "cannot load recovery img" I also tried using clean flash 1.0 and i get the same thing "cannot load" and than the phone just boots in fastboot.. What could be the problem?
feralicious said:
You should be able to put Amon Ra inside the same folder you just used for unlocking. Then use command:
Fastboot flash recovery (nameofrecoveryfilehere)
You will need to add .IMG to the file name for it to work.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Still not showing root. Any more ideas??
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\KC>cd c:\Android
c:\Android>Fastboot flash recovery recovery.img
sending 'recovery' (7062 KB)...
OKAY [ 1.430s]
writing 'recovery'...
OKAY [ 5.036s]
finished. total time: 6.467s
c:\Android
Kbartley77 said:
Still not showing root. Any more ideas??
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\KC>cd c:\Android
c:\Android>Fastboot flash recovery recovery.img
sending 'recovery' (7062 KB)...
OKAY [ 1.430s]
writing 'recovery'...
OKAY [ 5.036s]
finished. total time: 6.467s
c:\Android
Click to expand...
Click to collapse
c:/Android>fastboot flash recovery (name of recovery).img
Not recovery.img
Sent from my ADR6425LVW using xda premium
Alright I rebooted into Bootloader and selected recovery.
It put me into RA-Vigor-v3.0.6
Which option do I select?
-Reboot system now
-USB-MS Toggle
-Backup/Restore
-Wipe
-Partition
-Mounts
-Other
-Format Data
-Dev. Menu
-Power off
Please forgive me for my newbness.
Kbartley77 said:
Alright I rebooted into Bootloader and selected recovery.
It put me into RA-Vigor-v3.0.6
Which option do I select?
-Reboot system now
-USB-MS Toggle
-Backup/Restore
-Wipe
-Partition
-Mounts
-Other
-Format Data
-Dev. Menu
-Power off
Please forgive me for my newbness.
Click to expand...
Click to collapse
Developer menu if your trying to achieve root. Then there is an option to install su and superuser. Select that then after that is done immediately reboot. You may or may not still have to download the superuser off the market and update it. I didn't but alot of people reported having to do so.
I'm ROOTED!!!! Thank you everyone for your time and patience!!!
qudwis, thank you for responding. That Post is what I followed, but I do not see any way once in Fastboot were I can type "fastboot flash recovery recovery_signed.img". I restart my phone and I get to the screen were HBOOT and Fastboot are located. But there is no command line to type into. That is were I need the step by step to help me.
Thank you for your help.
dnvm said:
qudwis, thank you for responding. That Post is what I followed, but I do not see any way once in Fastboot were I can type "fastboot flash recovery recovery_signed.img". I restart my phone and I get to the screen were HBOOT and Fastboot are located. But there is no command line to type into. That is were I need the step by step to help me.
Thank you for your help.
Click to expand...
Click to collapse
You have to do this in Cmd, while the phone is in fastboot
Sent from my DROID RAZR using XDA App
dnvm said:
qudwis, thank you for responding. That Post is what I followed, but I do not see any way once in Fastboot were I can type "fastboot flash recovery recovery_signed.img". I restart my phone and I get to the screen were HBOOT and Fastboot are located. But there is no command line to type into. That is were I need the step by step to help me.
Thank you for your help.
Click to expand...
Click to collapse
You run those commands on your PC in a command/DOS prompt.
Related
I've seen the Zerg root for the 4G, but after reading some comments about it there's been speculation that the 1.45.1500.2 is Zerg root proof. It there a way to root the Amaze with 1.45.1500.2 software?
On another note... I'm not able to tether with my phone? i'm able to make a hot spot and all yet, I cannot connect any devices to it. The devices seem to not be able to acquire the IP address.
All tips and suggestions are helpful, so please comment as I'm sure you'll be able to help me with my issues one way or another.
Have you unlocked your bootloader?
Sent from my HTC Amaze 4G using xda premium
*edit
What's the complete process in rooting the device with the 1.45.1500.2 software? I'm going to bootload it as soon as it's fully charged.
To unlock your bootloader:
Go to http://htcdev.com/register/ and register an account with them.
Then select "Begin Unlock bootloader"
Follow the steps. It is easy. Just back up your info because when you unlock it, it will require a hard reset.
To do install ClockWorkMod Recovery (CWM), go to this link.
http://forum.xda-developers.com/showthread.php?t=1316855
Follow the instructions that says "Installation from fastboot (hboot only ||Hard Method||):" (It's actually very easy and it worked on the new ROM update)
Download the ClockworkMOD 5.0.2.7 Amaze 4g and not the ClockworkMOD 5.0.2.0 Amaze 4g.
To root, you can install a prerooted Custom ROM or you can download SuperUser (SU) from here
http://www.multiupload.com/TI14RLNE8A
Just boot into CWM and flash the su-2.3.6.3-ef-signed.zip if you want to root it with your stock ROM.
To get WiFi Tethering working, you need root (duh).
Download WiFi Tether for Root Users 3.1-beta9
http://code.google.com/p/android-wifi-tether/downloads/detail?name=wifi_tether_v3_1-beta9.apk
After you install it, press the menu button. Select "Settings". Change the Device Profile to HTC Amaze / HTC Ruby. You are good to go!
Much appreciated, will try this tonight and will get back to you
Alright, so I've tried the Bootloader process and I've received an error:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: .
Error Reason: .
That's after I went through the steps and had to paste the coding from the cmd onto the site. What's the problem?
HTC Bootloader unlock
I just read another post that said the HTC bootloader unlock page is broken today. I was trying to unlock my new t-mobile US amaze today and have the same errors as you.
RyanB125 said:
Alright, so I've tried the Bootloader process and I've received an error:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: .
Error Reason: .
That's after I went through the steps and had to paste the coding from the cmd onto the site. What's the problem?
Click to expand...
Click to collapse
Tardango said:
I just read another post that said the HTC bootloader unlock page is broken today. I was trying to unlock my new t-mobile US amaze today and have the same errors as you.
Click to expand...
Click to collapse
Alright, I guess i'll have to try again tomorrow.
The site is down I believe. I tried it for my friend. If it works, let me know!
Zerg not working on my unlocked Amaze
I have unlocked my bootloader and am running 1.43.531.3. I get pretty much the same set of errors every time I run the bat file. I have tried factory resetting it 3 times and trying again, but it always does the same thing. Occasionally it'll also say rm failed: no such file or directory on the adb shell rm /data/local/tmp/*sh command. USB debugging is on.
C:\Zerg>adb wait-for-device
C:\Zerg>adb push zergRush /data/local/
1294 KB/s (21215 bytes in 0.016s)
C:\Zerg>adb shell chmod 777 /data/local/zergRush
C:\Zerg>adb shell rm /data/local/tmp/*sh
C:\Zerg>adb shell /data/local/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 ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
C:\Zerg>adb wait-for-device
C:\Zerg>adb shell sleep 1
C:\Zerg>adb remount
remount failed: Operation not permitted
C:\Zerg>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\Zerg>adb shell mount -o remount,suid /dev/block/mmcblk0p29 /system
mount: Operation not permitted
C:\Zerg>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\Zerg>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg>adb push ./busybox /system/bin
failed to copy './busybox' to '/system/bin/busybox': Read-only file system
C:\Zerg>adb shell chmod 4755 /system/bin
Unable to chmod /system/bin: Read-only file system
C:\Zerg>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg>adb push ./Superuser.apk /system/app
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Zerg>adb install ./androidterm.apk
1969 KB/s (92780 bytes in 0.046s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Zerg>adb wait-for-device
C:\Zerg>adb shell sync
C:\Zerg>pause
Press any key to continue . . .
Have you installed CWM?
Still getting the same errors as before. :/
edit* is there any report as to when the HTCdev page will be fixed?
I tried is an hour ago. The HTCDev site is working. I got my friend's unlock key.
its not the HTCdev site, its the way you copied the key over to the box. absolutely no spaces are allowed.
but im gettin the same error for zerg. this is crap, i basically blanked my phone just to unlock it and restore everything.
is this a software version problem?
hasoon2000 said:
I tried is an hour ago. The HTCDev site is working. I got my friend's unlock key.
Click to expand...
Click to collapse
I'm still receiving the same error!
PM me the token ID in a text file attachment. I will see what the issue is.
pepsishine said:
its not the HTCdev site, its the way you copied the key over to the box. absolutely no spaces are allowed.
but im gettin the same error for zerg. this is crap, i basically blanked my phone just to unlock it and restore everything.
is this a software version problem?
Click to expand...
Click to collapse
Assuming you are trying to root, you might try this approach. Worked for me. After the wifi update I had to reset to factory and remove CWM to get the update to install. After the update I did this again and all went well except I got an error during the root process using the file I downloaded from that thread. Thought maybe I was out of luck, but after rebooting the phone it was rooted. Been working fine for the past several days.
hasoon2000 said:
PM me the token ID in a text file attachment. I will see what the issue is.
Click to expand...
Click to collapse
Alright, give me a sec, i'll pm you.
Are you on Telus or Wind mobile? I heard that they didn't give HTC permission to allow the customers to unlock their bootloaders
Sent from my HTC_Amaze_4G using xda premium
I'm with Wind.
Everytime I run the .bat for the my prompt reads Your device is a Nook Tablet meaning we can continue!
[/quote]Now, just making sure you WANT to root it!
[-] Cannot copy boomsh.: Permission denied
Installing superuser and su...
2313 KB/s (843503 bytes in 0.356s)
1819 KB/s (22364 bytes in 0.012s)
failed to copy 'root-files\su' to '/system/bin/su': Read-only file system
Installing and setting up busybox...
failed to copy 'root-files\busybox' to '/system/xbin//busybox': Read-only file s
ystem
1963 KB/s (12066 bytes in 0.006s)
[quote/]
I tried to root when in version 1.4.0 then downgraded back to 1.4.0 when the OTA hit and tried once more only to get the same error. Tried to cmod the entire system folder from both an adb shell and android terminal. any ideas guy?
Do you have USB Debugging enabled (in both boxes)?
Yea, its shows my device in the beginning of the script. =\
I think you need to run the runmefirst. bat then apply the other .bat to root
Sent from my LG GT540 Swift using XDA App
Did the runmefirst.bat.
logoguy said:
Did the runmefirst.bat.
Click to expand...
Click to collapse
ok then if that didn't work then its 100% drivers issue check this its the best step by step tutorial i have found , check step 3 or better the whole tut
hey all,
so i purchased my phone pretty much brand new, the person only opened to unlock phone and root/install super user.
he froze all the bloatware and useless stuff as well.
last night i received the ota update? and accepted it.
now the phone has been unrooted? or all frozen apps have returned.
could someone please help me root my phone?
i have tried the different root methods but none is working.
phone is still showing 2.3.5 not 6!
here is the log/error i get:
---------------------------------------------------------------
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
rm failed for *, No such file or directory
--- pushing zergRush"
703 KB/s (23056 bytes in 0.032s)
--- 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
2876 KB/s (1075144 bytes in 0.365s)
--- 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: Read-only file system
--- correcting permissions
Unable to chmod /system/xbin/busybox: Read-only file system
--- installing busybox
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: Read-only file system
--- correcting permissions
Unable to chmod /system/bin/su: Read-only file system
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed File exists
--- 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 . . .
i have tried soft/hard reset.
so what do i need to do?
unroot? reroot?
if all else fails how do i remove the ota update i got and hopefully i can root and then use the keeproot or something?
any help would be great!
THANK YOU!!!
First of all, when you post you need to specify whether you have a Droid Razr XT912 or GSM Razr XT910.
I will assume you have XT910.
1. Use RSDLite 5.6 to downgrade to this software.
http://sbf.droid-developers.org/umt...SASPDRTIMIT_HWp2b_Service1FF_fastboot.xml.zip
2. Root.
3. Install VooDoo OTA Rootkeeper from the Market and backup root.
4. Install the OTA and restore root via VooDoo.
Szadzik said:
First of all, when you post you need to specify whether you have a Droid Razr XT912 or GSM Razr XT910.
I will assume you have XT910.
1. Use RSDLite 5.6 to downgrade to this software.
http://sbf.droid-developers.org/umt...SASPDRTIMIT_HWp2b_Service1FF_fastboot.xml.zip
2. Root.
3. Install VooDoo OTA Rootkeeper from the Market and backup root.
4. Install the OTA and restore root via VooDoo.
Click to expand...
Click to collapse
hey,
i apologise about that.
im stressing out about the root stuff i completely forgot.
yes i have a xt910.
i will give your advice ago.
thank you very much!
hopefully that solves my issue!
you're a life saver!!!
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.
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...