i did the htc unlock blootloader.
and downloaded and plate the PH8.... on my sd card
when i go to fastboot it says i have older version faild to flash
then i tried the one click root and i get this
C:\Zerg rush root>adb wait-for-device
C:\Zerg rush root>adb push zergRush /data/local/
1328 KB/s (21215 bytes in 0.015s)
C:\Zerg rush root>adb shell chmod 777 /data/local/zergRush
C:\Zerg rush root>adb shell rm /data/local/tmp/*sh
C:\Zerg rush root>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 rush root>adb wait-for-device
C:\Zerg rush root>adb shell sleep 1
C:\Zerg rush root>adb remount
remount failed: Operation not permitted
C:\Zerg rush root>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\Zerg rush root>adb shell mount -o remount,suid /dev/block/mmcblk0p29 /system
mount: Operation not permitted
C:\Zerg rush root>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg rush root>adb push ./busybox /system/bin
failed to copy './busybox' to '/system/bin/busybox': Read-only file system
C:\Zerg rush root>adb shell chmod 4755 /system/bin
Unable to chmod /system/bin: Read-only file system
C:\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg rush root>adb push ./Superuser.apk /system/app
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Zerg rush root>adb install ./androidterm.apk
1936 KB/s (92780 bytes in 0.046s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Zerg rush root>adb wait-for-device
C:\Zerg rush root>adb shell sync
C:\Zerg rush root>pause
Press any key to continue . . .
i have the htc drivers aswell on fastboot says unlocked but s-on????
i had tried to do this method with pc and mac. and no luck
what am i doing wrong. please help. i have 3 days trying to root my phone
Do you have USB Debugging checked?
It should say S-On. there is not way to get S-off right now.
when you put the PH85IMG on your sd card and when to hboot did it ask you to update?
did you volume up and hit update?
If it worked then go to Hboot screen and volume down to recovery. Should bring up clockworkmod and you can flash a rom.
thanks for the quick respond. and yes i have Debugging checked on.
i didnt know we couldnt have s-off yet but im trying to root this device just like it says on the thread. and cant seem to have luck
gypsy214 said:
thanks for the quick respond. and yes i have Debugging checked on.
i didnt know we couldnt have s-off yet but im trying to root this device just like it says on the thread. and cant seem to have luck
Click to expand...
Click to collapse
are you using this one?
http://forum.xda-developers.com/showthread.php?t=1324177
never did the one click one..
bmbrad said:
are you using this one?
http://forum.xda-developers.com/showthread.php?t=1324177
never did the one click one..
Click to expand...
Click to collapse
i tried that one first. did that htc unlock and put this PG58IMG on the sd card but fastboot says fail older version
gypsy214 said:
i tried that one first. did that htc unlock and put this PG58IMG on the sd card but fastboot says fail older version
Click to expand...
Click to collapse
hmmmm.... try this one PH85IMG
http://forum.xda-developers.com/attachment.php?attachmentid=814010&d=1323710332
your not extracting it right?
never extracted it. i downloaded it from pc and mac and still. im gonna try this one and report back
bmbrad said:
hmmmm.... try this one PH85IMG
http://forum.xda-developers.com/attachment.php?attachmentid=814010&d=1323710332
your not extracting it right?
Click to expand...
Click to collapse
this one did the work thank you so much... they need to update the file in the op from the guide thread.
gypsy214 said:
this one did the work thank you so much... they need to update the file in the op from the guide thread.
Click to expand...
Click to collapse
It's because the hboot needs to verify the current file. For example in this new file that you just downloaded it has:
modelid: PH8511000
cidnum: T-MOB010
mainver: 1.43.531.3
hbootpreupdate:0
DelCache:1
The previous version that you tried earlier:
modelid: PH8511000
cidnum: T-MOB010
mainver: 1.36.531.5
hbootpreupdate:0
DelCache:1
See the difference? So all I did was modified the 1.36.531.5 with 1.43.531.3 and replaced the android-info.txt file in the zip file and it worked.
I'm not sure why HTC does this or even if there is a way around it but so far we have three versions for the US PH85IMG.zip files.
1.43.531.3 (newest)
1.36.531.6 (kinda new)
1.36.531.5 (shipped)
Other carriers such as Wind may have a different version so it's kinda difficult to make a universal PH85IMG.zip file. I'm curious if we could just use something as simple as:
modelid: PH8511000
cidnum: T-MOB010
hbootpreupdate:0
DelCache:1
or
modelid: PH8511000
cidnum: T-MOB010
mainver: *
hbootpreupdate:0
DelCache:1
Anyone is welcome to try if you like.
gypsy214 said:
this one did the work thank you so much... they need to update the file in the op from the guide thread.
Click to expand...
Click to collapse
Were you able to do this using your Mac or did you have to use your PC? I am tempted to root, but I have Mac and haven't even been able to temp root successfully so I'm hesitant to unlock bootloader.
sh!mon said:
Were you able to do this using your Mac or did you have to use your PC? I am tempted to root, but I have Mac and haven't even been able to temp root successfully so I'm hesitant to unlock bootloader.
Click to expand...
Click to collapse
You really don't even need a computer. Just place the PH85IMG.zip (with the recovery inside) on the root of your external sdcard once you have an unlocked bootloader then flash it from hboot. Voila! Root!
while i was visiting my uncle i took their computer to unlock the bootloader.
so in another words. i got the new update on the phone that one the includes wifi calling. thats why the old file didnt work and says older version fail.
so now thanks to you i am fool rooted and i have recovery. when s-off comes available is it something i would need?
on my sensation i have to wait for s-off to have perm root
gypsy214 said:
so in another words. i got the new update on the phone that one the includes wifi calling. thats why the old file didnt work and says older version fail.
so now thanks to you i am fool rooted and i have recovery. when s-off comes available is it something i would need?
on my sensation i have to wait for s-off to have perm root
Click to expand...
Click to collapse
we already have perm root with the unlock bootloader. we're able to do everything s-off allows us to do but to update radio hboot bootloader
Oh my god thank you so much! I was having the same problem and I was just about to post asking for help when i came across! Whew! thx guys I have a great and rooted amaze again!
westcoastfishing86 said:
Oh my god thank you so much! I was having the same problem and I was just about to post asking for help when i came across! Whew! thx guys I have a great and rooted amaze again!
Click to expand...
Click to collapse
The wonders of the search feature.
Binary100100 said:
The wonders of the search feature.
Click to expand...
Click to collapse
lol tell me about it.. anywho thx again guys
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.
Ok...I'm at my wits end here with the ZergRushRoot method.
I unlocked my bootloader and attempted the "one click" method BUT still receive the following error message:
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb wait-for-device
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push zergRush /data/local/
2071 KB/s (21215 bytes in 0.010s)
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 777 /data/local/zergRush
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell rm /data/local/tmp/*sh
C:\Zerg_Root_OneClick(1)\Zerg rush root>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_Root_OneClick(1)\Zerg rush root>adb wait-for-device
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell sleep 1
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb remount
remount failed: Operation not permitted
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell mount -o remount,suid /dev/blo
ck/mmcblk0p29 /system
mount: Operation not permitted
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push ./busybox /system/bin
failed to copy './busybox' to '/system/bin/busybox': Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 4755 /system/bin
Unable to chmod /system/bin: Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push ./Superuser.apk /system/app
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb install ./androidterm.apk
2831 KB/s (92780 bytes in 0.032s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb wait-for-device
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell sync
C:\Zerg_Root_OneClick(1)\Zerg rush root>pause
Press any key to continue . . .
I'm fairly certain that I followed the instructions as they were presented on the main thread and in the YouTube video by Ted.
I have verified that my bootloader is unlocked...what should I do next?
I've searched through numerous previous posts and spend over a day on this. Please suggest next steps...thank you!
dudro said:
Ok...I'm at my wits end here with the ZergRushRoot method.
I unlocked my bootloader and attempted the "one click" method BUT still receive the following error message:
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb wait-for-device
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push zergRush /data/local/
2071 KB/s (21215 bytes in 0.010s)
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 777 /data/local/zergRush
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell rm /data/local/tmp/*sh
C:\Zerg_Root_OneClick(1)\Zerg rush root>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_Root_OneClick(1)\Zerg rush root>adb wait-for-device
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell sleep 1
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb remount
remount failed: Operation not permitted
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell mount -o remount,suid /dev/blo
ck/mmcblk0p29 /system
mount: Operation not permitted
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push ./busybox /system/bin
failed to copy './busybox' to '/system/bin/busybox': Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 4755 /system/bin
Unable to chmod /system/bin: Read-only file system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb push ./Superuser.apk /system/app
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb install ./androidterm.apk
2831 KB/s (92780 bytes in 0.032s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb wait-for-device
C:\Zerg_Root_OneClick(1)\Zerg rush root>adb shell sync
C:\Zerg_Root_OneClick(1)\Zerg rush root>pause
Press any key to continue . . .
I'm fairly certain that I followed the instructions as they were presented on the main thread and in the YouTube video by Ted.
I have verified that my bootloader is unlocked...what should I do next?
I've searched through numerous previous posts and spend over a day on this. Please suggest next steps...thank you!
Click to expand...
Click to collapse
Are you running as administrator?
It's not working because it's not mounting the root partition.
Why don't you try using fastboot instead?
http://forum.xda-developers.com/showthread.php?t=1316855
I don't have an unlocked bootloader but have used the method for temp root in order to restore game data backed up from my Rooted Inspire 4G. I had errors the second time I used the tool which I can only assume were caused by Norton messing up the files while they were just sitting on the computer (since I disable it which doing anything between the phone and PC).
I had to delete all the tool files and re download with the security once again disabled, that did the trick.
Good luck!
Sent from my HTC Ruby using xda premium
Binary100100 said:
Are you running as administrator?
It's not working because it's not mounting the root partition.
Why don't you try using fastboot instead?
http://forum.xda-developers.com/showthread.php?t=1316855
Click to expand...
Click to collapse
When you ask whether I am running as administrator, are you referring to my PC? If so, yes. I am logged in with Admin rights.
Once I perform the fastboot method using the "PH85IMG.zip", do I then try the Zerg one click again?
Trevorhimself said:
I don't have an unlocked bootloader but have used the method for temp root in order to restore game data backed up from my Rooted Inspire 4G. I had errors the second time I used the tool which I can only assume were caused by Norton messing up the files while they were just sitting on the computer (since I disable it which doing anything between the phone and PC).
I had to delete all the tool files and re download with the security once again disabled, that did the trick.
Good luck!
Sent from my HTC Ruby using xda premium
Click to expand...
Click to collapse
Oh...this is interesting...perhaps I will disable AVG and try again...I will post my results.
dudro said:
When you ask whether I am running as administrator, are you referring to my PC? If so, yes. I am logged in with Admin rights.
Once I perform the fastboot method using the "PH85IMG.zip", do I then try the Zerg one click again?
Click to expand...
Click to collapse
Wow you're really making this much harder than it needs to be.
You have two ways to do it.
Use the PH85IMG.zip file according to your software version.
Use the fastboot flash recovery recovery.img command.
Once you get the recovery you do not need to do Zerg. You are free to flash a custom rom.
If you don't want a custom rom then just flash the file attached for perm root (from recovery of course).
Binary100100 said:
Wow you're really making this much harder than it needs to be.
You have two ways to do it.
Use the PH85IMG.zip file according to your software version.
Use the fastboot flash recovery recovery.img command.
Once you get the recovery you do not need to do Zerg. You are free to flash a custom rom.
If you don't want a custom rom then just flash the file attached for perm root (from recovery of course).
Click to expand...
Click to collapse
This finally worked! Thank you!
dudro said:
This finally worked! Thank you!
Click to expand...
Click to collapse
No problem. You could have used the thanks button though.
I tried to root my phone and i'm having problem. Did anybody have the problem?
C:\Users\Peter\Downloads\Zerg rush root>ZergRushTempRoot.bat
C:\Users\Peter\Downloads\Zerg rush root>adb wait-for-device
C:\Users\Peter\Downloads\Zerg rush root>adb push zergRush /data/local/
2071 KB/s (21215 bytes in 0.010s)
C:\Users\Peter\Downloads\Zerg rush root>adb shell chmod 777 /data/local/zergRush
C:\Users\Peter\Downloads\Zerg rush root>adb shell rm /data/local/tmp/*sh
C:\Users\Peter\Downloads\Zerg rush root>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:\Users\Peter\Downloads\Zerg rush root>adb wait-for-device
C:\Users\Peter\Downloads\Zerg rush root>adb shell sleep 1
C:\Users\Peter\Downloads\Zerg rush root>adb remount
remount failed: Operation not permitted
C:\Users\Peter\Downloads\Zerg rush root>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\Users\Peter\Downloads\Zerg rush root>adb shell mount -o remount,suid /dev/block/mmcblk0p29 /system
mount: Operation not permitted
C:\Users\Peter\Downloads\Zerg rush root>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\Users\Peter\Downloads\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Users\Peter\Downloads\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Users\Peter\Downloads\Zerg rush root>adb push ./busybox /system/bin
failed to copy './busybox' to '/system/bin/busybox': Read-only file system
C:\Users\Peter\Downloads\Zerg rush root>adb shell chmod 4755 /system/bin
Unable to chmod /system/bin: Read-only file system
C:\Users\Peter\Downloads\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Users\Peter\Downloads\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Users\Peter\Downloads\Zerg rush root>adb push ./Superuser.apk /system/app
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
C:\Users\Peter\Downloads\Zerg rush root>adb install ./androidterm.apk
3124 KB/s (92780 bytes in 0.029s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Users\Peter\Downloads\Zerg rush root>adb wait-for-device
C:\Users\Peter\Downloads\Zerg rush root>adb shell sync
C:\Users\Peter\Downloads\Zerg rush root>pause
Press any key to continue . . .
don't use that!!! it's old...use the guide on top of the page!
That only works with version 1.36. Do what seansk said and you should be fine.
Thanks guys!!!!
Now i'm getting this
C:\Users\Peter\Downloads\STOCK_RECOVERY_FLASHER>adb kill-server
C:\Users\Peter\Downloads\STOCK_RECOVERY_FLASHER>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
C:\Users\Peter\Downloads\STOCK_RECOVERY_FLASHER>fastboot flash recovery stock_recovery.img
< waiting for device >
pcurator said:
Now i'm getting this
C:\Users\Peter\Downloads\STOCK_RECOVERY_FLASHER>adb kill-server
C:\Users\Peter\Downloads\STOCK_RECOVERY_FLASHER>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
C:\Users\Peter\Downloads\STOCK_RECOVERY_FLASHER>fastboot flash recovery stock_recovery.img
< waiting for device >
Click to expand...
Click to collapse
make sure the phone drivers are installed on your computer!
P.s. did you unzip the files into a directory?
Yes i have the drivers installed. Files are unzip as well.
pcurator said:
Yes i have the drivers installed. Files are unzip as well.
Click to expand...
Click to collapse
what part of the guide are you stuck in? and what step? WHY ARE YOU TRYING TO FLASH STOCK RECOVERY??????? you need custom recovery! not stock..
---------- Post added at 06:40 PM ---------- Previous post was at 06:33 PM ----------
seansk said:
what part of the guide are you stuck in? and what step? WHY ARE YOU TRYING TO FLASH STOCK RECOVERY??????? you need custom recovery! not stock..
Click to expand...
Click to collapse
I urge you to read a little more carfeully and don't just skim over things while your following the guide!!! it specifically states what those files are and the one you're using reverts you back to stock recovery. You're trying to put a custom recovery on, not the original one that came with the factory and is already on your phone at this point...you trying to replace stock recovery with stock recovery!!!
I know you're new so It understandable but next time you should post all this stuff in the appropriate thread!!! the [How to] guide to rooting...you'll get more responses this way and people will not get pissed off, especially the moderators
I swear to GOD!!! If I keep seeing those stupid Zergrush errors for 1.43+ firmware I'm going to be forced to check myself as a 5150. This is getting out of hand.
If a .bat script isn't your thing then try this thread: [TOOL] HTC Amaze 4G All-In-One Toolkit by Hasoon2000
Binary100100 said:
I swear to GOD!!! If I keep seeing those stupid Zergrush errors for 1.43+ firmware I'm going to be forced to check myself as a 5150. This is getting out of hand.
If a .bat script isn't your thing then try this thread: [TOOL] HTC Amaze 4G All-In-One Toolkit by Hansoon2000
Click to expand...
Click to collapse
Sadly, you got my username wrong. You disappoint me, B.
hasoon2000 said:
Sadly, you got my username wrong. You disappoint me, B.
Click to expand...
Click to collapse
NO! I've sent a PM to the administrator to have you renamed to Hansoon2000.
Hope you enjoy your new name Hansoon2000. See you around the forum Hansoon2000. I'll fix it.
Binary100100 said:
NO! I've sent a PM to the administrator to have you renamed to Hansoon2000.
Hope you enjoy your new name Hansoon2000. See you around the forum Hansoon2000. I'll fix it.
Click to expand...
Click to collapse
Haha. Jackass! Hasoon is actually the name of my cat who passed away a 2 years ago. I'd rather keep it the same.
Binary100100 said:
I swear to GOD!!! If I keep seeing those stupid Zergrush errors for 1.43+ firmware I'm going to be forced to check myself as a 5150. This is getting out of hand.
If a .bat script isn't your thing then try this thread: [TOOL] HTC Amaze 4G All-In-One Toolkit by Hasoon2000
Click to expand...
Click to collapse
lol I love it when binary goes mad!!! that tool isn't needed anymore, unless for a handfull of people who wish to stay on their old firmware and do temproot!!! why don't we just get rid of it!
Binary100100 said:
I swear to GOD!!! If I keep seeing those stupid Zergrush errors for 1.43+ firmware I'm going to be forced to check myself as a 5150. This is getting out of hand.
If a .bat script isn't your thing then try this thread: [TOOL] HTC Amaze 4G All-In-One Toolkit by Hasoon2000
Click to expand...
Click to collapse
Learn my tough love Lesson from this guy... Never pissed this guy.
seansk said:
lol I love it when binary goes mad!!! that tool isn't needed anymore, unless for a handfull of people who wish to stay on their old firmware and do temproot!!! why don't we just get rid of it!
Click to expand...
Click to collapse
I could totally see you making a bunch of duplicate accounts pretending to be noobs just to piss me off.
Binary100100 said:
I could totally see you making a bunch of duplicate accounts pretending to be noobs just to piss me off.
Click to expand...
Click to collapse
too late all the new questions regarding root was me!!! I also like to answer my own questions!!
Log below..dev says the root should work just fine for the Evo 3D
---------------------------------------------------------------
One-Click Root ToolKit For Evo 4G LTE!
Script by Max Lee from OneXRoot.com
Credits go to XDA users sparkym3 and Dan Rosenburg for exploit.
---------------------------------------------------------------
[*] This script will:
(1) root your Evo 4G LTE on ICS
(2) install Busybox
(3) install SU files
[*] Before u begin:
(4) Make sure to read full instructions at HTCEvoHacks.com!
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Please hit Enter when ready.
Press any key to continue . . .
Rooting...
Start Rooting...
failed on '/data/local/tmp' - Permission denied
link failed File exists
reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
/system/bin/sh: cannot create /data/local.prop: Permission denied
reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, No such file or directory
link failed Read-only file system
failed to copy 'Superuser.apk' to '/system/app/./Superuser.apk': Read-only file
system
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
3952 KB/s (0 bytes in 1075144.000s)
mount: permission denied (are you root?)
/system/xbin/busybox: cannot open for write: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rebooting
All Done rooting Evo 4G LTE, check out OneXRoot.com for more cool stuff like ROM
s, hacks, tips, and more!
Press any key to continue . . .
This is running on my C2D unlocking computer ( I run a phone unlocking) shop.
WinXP sp3
Any help would be appreciated. Its an Evo 3d on stock ICS.
Try this
http://forum.xda-developers.com/showthread.php?p=17250151
Sent from my HTC EVO 3D X515m using xda premium
As best as I can tell, the script fails to mount partition as writable, I imagine it's because it was intended for a previous version of hboot? though i'm not sure how similar the 3D and 4G are in terms of partitions to begin with... bottom line the method flashallthetime suggested should work just fine, but if you want S-OFF you would need to figure out what hboot u have, downgrade if necessary and then use revolutionary method to get S-OFF
C:\Users\masroorkhan\Desktop\Zerg rush root>adb wait-for-device
C:\Users\masroorkhan\Desktop\Zerg rush root>adb push zergRush /data/local/
1883 KB/s (21215 bytes in 0.011s)
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell chmod 777 /data/local/zerg
Rush
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell rm /data/local/tmp/*sh
rm failed for /data/local/tmp/*sh, No such file or directory
C:\Users\masroorkhan\Desktop\Zerg rush root>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.
[-] Cannot copy boomsh.: Permission denied
C:\Users\masroorkhan\Desktop\Zerg rush root>adb wait-for-device
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell sleep 1
C:\Users\masroorkhan\Desktop\Zerg rush root>adb remount
remount failed: Operation not permitted
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell mount -o rw,remount rootfs
/
mount: Operation not permitted
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell mount -o remount,suid /dev
/block/mmcblk0p29 /system
mount: Operation not permitted
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\Users\masroorkhan\Desktop\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Users\masroorkhan\Desktop\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Users\masroorkhan\Desktop\Zerg rush root>adb push ./busybox /system/bin
failed to copy './busybox' to '/system/bin/busybox': Read-only file system
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell chmod 4755 /system/bin
Unable to chmod /system/bin: Read-only file system
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Users\masroorkhan\Desktop\Zerg rush root>adb push ./Superuser.apk /system/app
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Users\masroorkhan\Desktop\Zerg rush root>adb install ./androidterm.apk
failed to copy './androidterm.apk' to '/data/local/tmp/androidterm.apk': Permiss
ion denied
C:\Users\masroorkhan\Desktop\Zerg rush root>adb wait-for-device
C:\Users\masroorkhan\Desktop\Zerg rush root>adb shell sync
C:\Users\masroorkhan\Desktop\Zerg rush root>pause
Press any key to continue . . .
We have a temp root?
Sent from my Amaze 4G using xda app-developers app
Did u extract (SDK) into c/: DRIVE. After it'll have folders AndroidSDK, Tools ,fastboot all folders, once that is done in your c/: DRIVE. Open command prompt type c/ , then AndroidSDK or however u spelled it, then type CD/ tools or just tools, and hopefully after that ur SDK IS set up, if so after all that type in fastboot devices then enter. If good ur device I.D should pop up and now ur good to go. If not just .... P.M.... ME
Use my toolkit.
http://forum.xda-developers.com/showthread.php?t=1493905
Also, ZergRush was only for 1.36 ROMs. This has been patched up a long time ago.