-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [CDMA] How to manually flash a recovery image (via fastboot OR from SD card)
- Thread starter novox77
- Start date
-
- Tags
- htc evo 3d
@Wake69
Sorry for the late reply, I found a working way to get TWRP installed. Looks like I was using a method that had me renaming the file to P####img.zip or some business, looks like all I needed was to copy the img file to the root of the sd card and use fastboot to flash it in, worked like a charm. I am now well on my way to getting a new ROM installed. Thank you for your willingness to help.
Sorry for the late reply, I found a working way to get TWRP installed. Looks like I was using a method that had me renaming the file to P####img.zip or some business, looks like all I needed was to copy the img file to the root of the sd card and use fastboot to flash it in, worked like a charm. I am now well on my way to getting a new ROM installed. Thank you for your willingness to help.
I am having the problem you were having. I did the fastboot flashing of the recovery, and I see recovery on my bootloader screen. when i select it though i get the htc screen and then phone eventually goes into a normal bootup...no recovery image screen...WTF? this ish is super annoying. nothing like the evo4g which was a frikkin snap. any help is appreciated
wake69
Android Expert
try this before you unroot
[GUIDE] HTC Unlock for Hboot 1.50 + Root + TWRP Recovery - xda-developers
That guide is actually what I ended up following, worked like a charm for the first time everything followed the guide. Also included are the exact files used in the process so no confusion about what version of what file to grab.
scotty0717
Lurker
Ok, someone please help me. Ive been at this for almost 6 hours..I own the evo 3d. Was one of the first ones to get mine because i work for sprint so i was lucky and recived on that was already s-off. Having been fully up to date, i used htcdev.com to root my phone today and it was pretty easy. Now i show "unlocked" and "s-off" BUT...I dont have root permission. So i though ok, ill just download superuser i get an erro message saying i need to boot into recovery and update the su.apk and so on. Well when i try to boot into recovery it hangs up because i dont have clockworld mod flashed. Having tried manual and rom manager trying to install clockworld mod just to be able to get superuser to work in order to have root access of my rooted phone rom manager wont let me download and flash clockworld mod because i dont have superuser installed.....HELP I am stuck in a endless circle. Much like a battery operated battery changer. Please help.
wake69
Android Expert
http://forum.xda-developers.com/showthread.php?t=1239821
Follow this guide. To flash su u need to first install recovery. The copy of twrp in guide has been modified for hboot 1.5. Give it a go and report back and good luck.
Follow this guide. To flash su u need to first install recovery. The copy of twrp in guide has been modified for hboot 1.5. Give it a go and report back and good luck.
that's what i'm following and when i select recovery, it just boots up normally and doesn't go to the recovery screen...how do i remove the recovery i have on there....clearly something isn't right, and i'd rather get my phone back to the way it was out of the box if root is not going to work....no point in having bootloader unlocked and recovery on there if i can't achieve root. I've done factory resets and all that, but recovery option is still listed in my hboot screen.
don't know what the hell i did, but i am now at least getting the recovery screen. please please please let me be able to do the next steps without incident....
i have a Desire HD , its with S-off (as in bootloader it says on top "ACE PVT SHIP S-OFF RL"), but its not rooted (as titanium backup says and typing su in terminal APP says permission denied).. shld i flash clockworkmod via fastboot and then flash any rom like CM7 ( and will i have super access as well)... or do some thing else.....
thnxxx
thnxxx
wake69
Android Expert
how did you get s-off, and isnt there a desire thread?
... as for S-OFF i bought this 2nd hand Desirehd... and when i decided to root, i checked bootloader and its already S-off'd but root was lost :|... 
Thanksguys, I need some help.
I downloaded recovery-clockwork-4.0.1.5-shooter.img and renamed it PG86IMG.ZIP and went through the bootloader, but it didn't find it. I tried again without renaming it, and it couldn't find it either.
I then went to download PG86IMG-twrp-shooter-1.1.1.zip and changed to PG86IMG.zip and i think this one and failed and finally i left it as PG86IMG-twrp-shooter-1.1.1.zip and it seems to have worked (one of the two worked, I went ahead with the update...) but then I rebooted and I don't see anything different...am I supposed to have root now? a new app?
i'm somewhat lost...I would have preferred CWMR since it's the one I have used in the past, but whatever works.
I downloaded recovery-clockwork-4.0.1.5-shooter.img and renamed it PG86IMG.ZIP and went through the bootloader, but it didn't find it. I tried again without renaming it, and it couldn't find it either.
I then went to download PG86IMG-twrp-shooter-1.1.1.zip and changed to PG86IMG.zip and i think this one and failed and finally i left it as PG86IMG-twrp-shooter-1.1.1.zip and it seems to have worked (one of the two worked, I went ahead with the update...) but then I rebooted and I don't see anything different...am I supposed to have root now? a new app?
i'm somewhat lost...I would have preferred CWMR since it's the one I have used in the past, but whatever works.
For HTC Desire GSM file should be named: PB99IMG.zip and inside it you can place http://download.clockworkmod.com/recoveries/recovery-clockwork-2.5.0.7-bravo.img file.
First I appreciate all that I've been able to learn from here and hopefully this is giving back a little for all that!
My clarifications/fixes are for the UPDATE.ZIP METHOD section for flashing. I've only tested/used this method with a recovery image. It may work for other image files, but it would seem it would be the same case:
"The filename needs to be named PG86IMG.ZIP for the Evo 3D, and it needs to contain the .img files named the same as the partition name."
"If you only have the .img file, you can make your own update.zip file. For example, if you have a recovery image file, it needs to be named recovery.img. Then, put it in a ZIP file without compression. Name the file PG86IMG.ZIP, and you're all set."
Do let me know if I'm missing anything or am off base on any of my observations!
My clarifications/fixes are for the UPDATE.ZIP METHOD section for flashing. I've only tested/used this method with a recovery image. It may work for other image files, but it would seem it would be the same case:
"The filename needs to be named PG86IMG.ZIP for the Evo 3D, and it needs to contain the .img files named the same as the partition name."
- The image included in the zip file can have the original name (ie. recovery-clockwork-4.0.1.5-shooter.img) and flashes to the recovery partition. Could this be based on the Windows fastboot command syntax. Unless of course I'm partially incorrect and it's flashing to the correct partition by parsing recovery from the name?
"If you only have the .img file, you can make your own update.zip file. For example, if you have a recovery image file, it needs to be named recovery.img. Then, put it in a ZIP file without compression. Name the file PG86IMG.ZIP, and you're all set."
- The phone specific android-info.txt file needs to be included in the zip file. If not, it will scan it and return to the HBOOT screen. Included and it will function as described in the guide.
Do let me know if I'm missing anything or am off base on any of my observations!
Other posters please note that I moved this post, so that's why he links back to this thread.
If I'm following your post right:
I believe that the update.zip method does parse the file and find the script that identifies it as a recovery partition 'update'.
And users could make their own update zip, but most people do not feel comfortable doing so. Especially seeing how many are available already and update.zips do not work on S-ON Unlocked bootloaders.
If I'm following your post right:
I believe that the update.zip method does parse the file and find the script that identifies it as a recovery partition 'update'.
And users could make their own update zip, but most people do not feel comfortable doing so. Especially seeing how many are available already and update.zips do not work on S-ON Unlocked bootloaders.
I cleaned up my post so no confusing link back to this thread as mentioned in jerofld's reply above. I'd originally posted wrongly as a new post and referred back to this one...
I'm assuming your reference to "parse the file" is to the recovery image contained in the zip rather than the zip file itself. If so, it appears no real need to change the name to the particular partition being updated.
And makes sense not reinventing the wheel where a zip already exists. In my case I hunted for zip files of the Clockworkmod recovery image, but could only find the standalone .img files. This forced me to create my own zip file to flash the Clockwork recovery image. Note1: Each phone model appears to have its own specific android-info.txt file. Note2: while the UPDATE.zip method worked for me, I recommend further reading/asking questions before proceeding if unsure about this!
Personally I'd prefer manually updating via flashboot rather than using the UPDATE.zip method. Unfortunately for me it always errors out during the manual flash method. I can also use a Market app, but I do like knowing I can do it manually in case of problems.
Off topic to the OP on this thread but in case anyone wonders, the error I get is "FAILED <remote: not allowed>" during the manual flash method. I've tried all the recommended suggestions found to no avail. At this point I'm thinking it's related to still having the stock HBOOT v1.40.000 & permissions not set 100%. Revolutionary's method ended for me without error before downloading/installing a custom recovery image. Also think it was supposed to update HBOOT from v1.40.0000 to v1.40.1000 before completing. In any case, like said - I'll possibly post this last part as a new question so as not to get this post off topic!
Ah, I haven't used CWM in ages. so I didn't know it didn't have a flashable zip. I used to be a fan of TWRP until recently where I've used ext4 Touch. I feel that flashing via fastboot is better, anyways, because I won't forget that I put the pg86img.zip in my SD card and the next time I try to restore via bootloader, I don't get stuck on it.
But flashing the file via update.zip works on the Evo 3D? I figured you would have to name it 'pg86img.zip' to get the bootloader to flash it.
As for your problem connecting:
1) There is no 1.40.1000 that I know of. It's either 1.30, 1.40, or 1.50. With the tertiary build number assumed to be .0000.
2) Did you use a RUU at any point? I used a RUU once and it prevented me from flashing the custom recovery via fastboot. So I had to use the flashable zip to get recovery to flash. I can now flash anything via fastboot again, but the first time after the RUU, it wouldn't work, even though I was S-OFF.
But flashing the file via update.zip works on the Evo 3D? I figured you would have to name it 'pg86img.zip' to get the bootloader to flash it.
As for your problem connecting:
1) There is no 1.40.1000 that I know of. It's either 1.30, 1.40, or 1.50. With the tertiary build number assumed to be .0000.
2) Did you use a RUU at any point? I used a RUU once and it prevented me from flashing the custom recovery via fastboot. So I had to use the flashable zip to get recovery to flash. I can now flash anything via fastboot again, but the first time after the RUU, it wouldn't work, even though I was S-OFF.
Sorry for the confusion - the OP used the term "UPDATE.ZIP" for the method of flashing via a zip file. The file does need to be named PG86IMG.zip for the EVO 3D to flash properly. Sorry if referring to the method created some confusion!
I'd come across reference to 1.40.1000 in reading before I rooted my phone - doing a google on it makes it sound like it's S-OFF version of HBOOT 1.40.0000 S-ON. I interpreted it to mean Revolutionary's unlock updated the HBOOT to that version, but maybe they are factory shipped that way? Appears I misinterpreted and it's irrelevant to my problem!
Never used an RUU, though I did do a temp root using the zergrush exploit. I did this to gain root access and make Titanium Backups before proceeding. I've been wondering if some remnant of Superuser or su remained with improper permissions. I had rebooted and uninstalled/re-installed Superuser but could there still be something left behind?
I did reflash the TWRP 1.1.1 recovery after running CWM (installed just to create a CWM android to cover all bases) but I still get the error. I was considering unrooting my phone so it'd be factory fresh and trying again. Though you mentioned fastboot didn't work the first time after you'd run an RUU. Plus not sure I need to (or should) attempt this. Wonder if I'm asking for more trouble than it's worth to just get fastboot to function?! Part of me says yes, but... Any thoughts?
I'd come across reference to 1.40.1000 in reading before I rooted my phone - doing a google on it makes it sound like it's S-OFF version of HBOOT 1.40.0000 S-ON. I interpreted it to mean Revolutionary's unlock updated the HBOOT to that version, but maybe they are factory shipped that way? Appears I misinterpreted and it's irrelevant to my problem!
Never used an RUU, though I did do a temp root using the zergrush exploit. I did this to gain root access and make Titanium Backups before proceeding. I've been wondering if some remnant of Superuser or su remained with improper permissions. I had rebooted and uninstalled/re-installed Superuser but could there still be something left behind?
I did reflash the TWRP 1.1.1 recovery after running CWM (installed just to create a CWM android to cover all bases) but I still get the error. I was considering unrooting my phone so it'd be factory fresh and trying again. Though you mentioned fastboot didn't work the first time after you'd run an RUU. Plus not sure I need to (or should) attempt this. Wonder if I'm asking for more trouble than it's worth to just get fastboot to function?! Part of me says yes, but... Any thoughts?
I used Revolutionary and my HBOOT is 1.40.0000. I don't know what .1000 is and details seem to be sketchy. Perhaps it's the build from the 1.50 > 1.40 downgrade process. I never had to downgrade, as I rooted when I had a 1.40 HBOOT from the start.
As for the errors you see, have you tried using Mini SDK?
http://androidforums.com/faqs/443072-adb-guide-updated-12-05-2011-a.html
Sometimes the main Android SDK can be touchy.
As for the errors you see, have you tried using Mini SDK?
http://androidforums.com/faqs/443072-adb-guide-updated-12-05-2011-a.html
Sometimes the main Android SDK can be touchy.
I started off with mini SDK and after it didn't work, ended up trying installing the full package. Nothing doing so I just stayed with mini SDK... *sigh* Like I said, it's a small thing but guess it's the perfectionist in me!
Make sense possibly just going back to stock via RUU and starting over with a "clean" slate? Figure with it being pretty safe, it at least would give me something to play with - whether it fixes the problem or not! And from your experience, using an RUU actually caused this problem for you until you reflashed a new recovery image so would think it'd more be an exercise (practice and learning) rather than a fix.
Make sense possibly just going back to stock via RUU and starting over with a "clean" slate? Figure with it being pretty safe, it at least would give me something to play with - whether it fixes the problem or not! And from your experience, using an RUU actually caused this problem for you until you reflashed a new recovery image so would think it'd more be an exercise (practice and learning) rather than a fix.