Now that S-OFF is available we can use the eng bootloader to get extra fastboot commands. If you set S-ON for whatever reason you must flash a SHIP bootloader first or you will brick your phone. If you aren't sure if you need this or not odds are you probably don't, it can be extremely useful but it assumes you know what you are doing so it is much easier to brick your phone with it.
To flash either rename to PG86IMG, place on your sd card and then reboot to the bootloader; or you can use 'fastboot oem rebootRUU' followed by 'fastboot flash zip PG86IMG_eng-hboot.zip'. A list of the available commands can be found here.
hBoot 1.04.2000, mirror - MD5: 3348C361FED927DABB853E49744BD7F2
If you would like to go back to the SHIP one you can download it here. The process to flash it is the same except over USB you can do it straight from fastboot without RUU mode.
PG86IMG_1.40-hboot - MD5: 1B994699EA226390B47282BCB54088DD
For more versions of hboots including hacked ones check out ramjet73's post here.
Thank you to the AlphaRev & Unrevoked teams for getting us all S-OFF! I also want to say thank you to TeamWin for making the wait bearable by getting us root and to everyone who has spent time ripping this phone apart.
Also thanks go out to SolsticeZero for being a guinea pig and making sure it flashed correctly
Thanks Haus!
Did you already check to see if they included the extra commands??
have you flashed this hboot? would like to have a confirmation first. I am s-off, rooted and nandroided!
TMartin said:
Thanks Haus!
Did you already check to see if they included the extra commands??
Click to expand...
Click to collapse
Yep, they're all there. I would have loved to get the 1.40.2000 hBoot that was pictured a few days ago but this works fine for me so far. I am still using the ancient 0.76 hBoot on the 4G and never had any trouble with it.
welrope said:
have you flashed this hboot? would like to have a confirmation first. I am s-off, rooted and nandroided!
Click to expand...
Click to collapse
I have used it and it works fine
xHausx said:
Yep, they're all there. I would have loved to get the 1.40.2000 hBoot that was pictured a few days ago but this works fine for me so far. I am still using the ancient 0.76 hBoot on the 4G and never had any trouble with it.
Click to expand...
Click to collapse
Do you think we will get a later version on it?
xHausx said:
Yep, they're all there. I would have loved to get the 1.40.2000 hBoot that was pictured a few days ago but this works fine for me so far. I am still using the ancient 0.76 hBoot on the 4G and never had any trouble with it.
Click to expand...
Click to collapse
I have the 1.40.0000 on dropbox
Bentenrai said:
I have the 1.40.0000 on dropbox
Click to expand...
Click to collapse
ENG or SHIP'd?
xHausx said:
ENG or SHIP'd?
Click to expand...
Click to collapse
How do I tell? I thought it was eng. Let me get into fastboot
Bentenrai said:
How do I tell? I thought it was eng. Let me get into fastboot
Click to expand...
Click to collapse
It should tell you at the top
Please specify the extra commands and what they do would be much appreciated.
Also, do we flash this via Recovery or fastboot (with flash recovery option??)
Bentenrai said:
I have the 1.40.0000 on dropbox
Click to expand...
Click to collapse
If it's the ENG can you post it?
vboyz103 said:
Please specify the extra commands and what they do would be much appreciated.
Also, do we flash this via Recovery or fastboot (with flash recovery option??)
Click to expand...
Click to collapse
A list of all the commands can be found here. To flash it you can rename it to PG86IMG and place it on your sdcard, then boot into the bootloader. Or, you can also flash through fastboot by using:
fastboot oem rebootRUU
fastboot flash zip PG86IMG_eng-hboot.zip
graffixnyc said:
If it's the ENG can you post it?
Click to expand...
Click to collapse
It's the SHIP.
I'm sorry for being such a noob and now my dropbox upload won't be too much use but just for clarification (I only got dropbox to host this specific file since my websites ftp is acting screwy) how do I make like a hyperlink straight to the .img file in my dropbox so I can share it?
Dumb question lol I just never jumped on the dropbox bandwagon
EDIT: NVM, got it, one sec
EDIT 2: Okay gotta reup it, apparently deleting my public folder caused my issue. I'll be back with a hyperlink if anyone needs.
xHausx said:
A list of all the commands can be found here. To flash it you can rename it to PG86IMG and place it on your sdcard, then boot into the bootloader. Or, you can also flash through fastboot by using:
fastboot oem rebootRUU
fastboot flash zip PG86IMG_eng-hboot.zip
Click to expand...
Click to collapse
Alpharev didn't include the extended fastboot commands in there hboot?? I thought they normally did that.
http://dl.dropbox.com/u/36719158/mmcblk0.img
This is a COMPLETE dump of every partition on a freshly restored 1.13, SHIP 1.40.0000 HBOOT Evo 3D. Sure hope it helps somewhere.
Thanks for posting this Haus. Glad to be of assistance.
Bentenrai said:
http://dl.dropbox.com/u/36719158/mmcblk0.img
This is a COMPLETE dump of every partition on a freshly restored 1.13, SHIP 1.40.0000 HBOOT Evo 3D. Sure hope it helps somewhere.
Click to expand...
Click to collapse
Did you say you had some of the eng apps installed? If so the system partition would be useful. Otherwise everything should already be included in the 1.13.651.7 RUU.
xHausx said:
Did you say you had some of the eng apps installed? If so the system partition would be useful. Otherwise everything should already be included in the 1.13.651.7 RUU.
Click to expand...
Click to collapse
I'm not sure if I do or not, pretty sure not. But I might.. would I have got those apps from the OTA or should I look at a dump from before the OTA? Either way I'll make dumps of the individual partitions as well now that I got that freaking public folder working.
Thanks haus. Now I got eng. hboot root recovery and s=off! I know I've seen you in these threads since day one so I wanted to thank you first. This all made my day after a long one at work.
Related
PG86IMG_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101-signed
http://d-h.st/AVU
hboot 1.58
PG86IMG_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06 .00.1216_NV_NV_spcs_1.42_release_233304-signed.zip
http://dev-host.org/jqp5rpess1ic
hboot 1.50
PG86IMG_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_219445-signed
http://dev-host.org/8agfa005a671
hboot 1.50
PG86IMG_Shooter_S_Sprint_WWE_2.08.651.2_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_208230-signed
http://d-h.st/Vlf2
hboot 1.50
PG86IMG_Shooter_S_Sprint_WWE_1.13.651.7_Radio_0.97.10.0530_NV_NV_SPCS_1.16_release_198109-signed
http://dev-host.org/c1purqm3amox
hboot 1.40
PG86IMG_Shooter_Sprint_WWE_1.11.651.2_Radio_radio_0.97.00.0518_NV_SPCS_1.15_release_193503_signed
http://dev-host.org/3zhc8tgto66j
hboot 1.30
These images are very useful especially for people, who have HBOOT 1.5 that want to lock their bootloader and go back to Stock in order to get latest OTA upgrade.
Your contribution is much appreciated.
alammori said:
These images are very useful especially for people, who have HBOOT 1.5 that want to lock their bootloader and go back to Stock in order to get latest OTA upgrade.
Your contribution is much appreciated.
Click to expand...
Click to collapse
That's a good point! I'm on hboot 1.5. So I would have to unroot, update to new OTA, then HTC unlock again? I'm just trying to understand. I'm gonna try this route, if I can unlock/root my phone again.
sent from America....F__k yeah!
Jabawockee said:
That's a good point! I'm on hboot 1.5. So I would have to unroot, update to new OTA, then HTC unlock again? I'm just trying to understand. I'm gonna try this route, if I can unlock/root my phone again.
Click to expand...
Click to collapse
Yes, this is the route to go. I myself have an evo3d with hboot1.5. my phone was unlocked prior the OTA update. I tried everything to get that OTA installed but no chance. The reason is that the radio within the OTA wont install because you are still S-On even though you are unlocked .
So I had to
1. Run:
adb reboot bootloader
Click to expand...
Click to collapse
then:
fastboot oem lock
Click to expand...
Click to collapse
to lock my phone.
2. Download PG86IMG_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_219445-signed.zip from the OP
3. Copy this image to my SDcard and rename to: PG86IMG.zip
4. Run:
adb reboot bootloader
Click to expand...
Click to collapse
and install this image from there.
5. Reboot into system and update the HTC sofware from there.
6. Copy my the file "Unlock_code.bin" (This is the file, that HTC sent me at the time I unlocked my phone) to the same folder where adb and fastboot are located.
7. Run again:
adb reboot bootloader
Click to expand...
Click to collapse
then
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Congratulation, you are back in business with the latest update. It worked for me and should work for you.
Edit: You have to reinstall the TWRP, to install custom roms.
alammori said:
...
3. Copy this image to my SDcard and rename to: PG86IMG.zip
4. Run: and install this image from there.
5. Reboot into system and update the HTC sofware from there.
6. Copy my the file "Unlock_code.bin" (This is the file, that HTC sent me at the time I unlocked my phone) to the same folder where adb and fastboot are located.
7. Run again: then
Congratulation, you are back in business with the latest update. It worked for me and should work for you.
Edit: You have to reinstall the TWRP, to install custom roms.
Click to expand...
Click to collapse
I got to Step 5 and am now STUCK.
It goes in and says it is loading, then checking the PG86.IMG.ZIP file, then nothing..
It goes back to FASTBOOT, RECOVERY, FACTORY RESET, (which I've tried, to no avail), SIMLOCK, and IMAGE CRC.
If I reboot without holding down any keys, it goes back there again.
It says RELOCKED at the top. It also says I'm still S-ON. I don't know how to get back to standard factory E3D.
HELP!
KnoxBNYC said:
I got to Step 5 and am now STUCK.
It goes in and says it is loading, then checking the PG86.IMG.ZIP file, then nothing..
It goes back to FASTBOOT, RECOVERY, FACTORY RESET, (which I've tried, to no avail), SIMLOCK, and IMAGE CRC.
If I reboot without holding down any keys, it goes back there again.
It says RELOCKED at the top. It also says I'm still S-ON. I don't know how to get back to standard factory E3D.
HELP!
Click to expand...
Click to collapse
it should be "PG86IMG.zip
it will say relocked not locked
Mr.Esp said:
it should be "PG86IMG.zip
it will say relocked not locked
Click to expand...
Click to collapse
#noobQ
Do these contain hboot? What version? Thanks. These are ass savers is you bork hard
il Duce said:
#noobQ
Do these contain hboot? What version? Thanks. These are ass savers is you bork hard
Click to expand...
Click to collapse
yes sir they contain hboot ill add versions to OP
Going to try this on mine today to get back to stock....hboot 1.50 the directions above are right on track
Hmmmm, possibly role back to hboot 1.40?? That might come in handy instead of loading ROMs via fastboot all the time, I like to switch on the fly, and I can't really do that with having to break out my laptop and run through cmd...
Any chance I could get someone to upload this to mega uploads for me? My work network blocks the site listed above. Just the full Rom if you could please.
Hmm getting wrong PG86IMG... re-downloading from OP
JJsax said:
Hmmmm, possibly role back to hboot 1.40?? That might come in handy instead of loading ROMs via fastboot all the time, I like to switch on the fly, and I can't really do that with having to break out my laptop and run through cmd...
Click to expand...
Click to collapse
As far as I know you cannot roll back hboot.
So far no you cannot roll back H-boot. But you can still flash on the fly. I use Flash Img GUI from the market to flash the kernel for the Rom, then I boot to recovery and flash the Rom. Works just fine for me even when switching from ASOP to Sense.
You can roll back hboot if you have s off
Sent from my PG86100 using xda premium
For people having trouble with image in the OP, download this:
http://goo-inside.me/shooter/ruu/2.08.651.2
once you have booted to the system, you have to run the htc update twice, one time to upgrade to 2.08.651.3 and the second time to upgrade to 2.08.651.5.
alammori said:
For people having trouble with image in the OP, download this:
http://goo-inside.me/shooter/ruu/2.08.651.2
once you have booted to the system, you have to run the htc update twice, one time to upgrade to 2.08.651.3 and the second time to upgrade to 2.08.651.5.
Click to expand...
Click to collapse
Awesome, thank you so much. Thought I was going to have to wait until I got home from work to tackle this.
Thanks again!
KnoxBNYC said:
I got to Step 5 and am now STUCK.
It goes in and says it is loading, then checking the PG86.IMG.ZIP file, then nothing..
It goes back to FASTBOOT, RECOVERY, FACTORY RESET, (which I've tried, to no avail), SIMLOCK, and IMAGE CRC.
If I reboot without holding down any keys, it goes back there again.
It says RELOCKED at the top. It also says I'm still S-ON. I don't know how to get back to standard factory E3D.
HELP!
Click to expand...
Click to collapse
You are not bricked yet. The problem is PG86.IMG.ZIP. This is not how it suppose to be renamed. It should say PG86IMG.zip and not PG86.IMG.ZIP
If the downloaded zip from the OP does not work, download the file from the post #16 and you should be good to go.
That PG86IMG Alammori provided works for anyone who was unsuccessful with the ones in the OP.
Back to stock and I'm almost done. Time to root again and get back on with the rooted good life lol
Thanks was sent and thanks again
steve97ta said:
That PG86IMG Alammori provided works for anyone who was unsuccessful with the ones in the OP.
Back to stock and I'm almost done. Time to root again and get back on with the rooted good life lol
Thanks was sent and thanks again
Click to expand...
Click to collapse
I am glad, it is working for you. I love to see success stories.
Hey all, just received a replacement rezound under warranty due to the charge port being all muffed up, and of coarse the first thing was unlock via htcdev which worked fine.
Here is the issue.. when trying to flash amonra via fastboot or PH98IMG.zip in bootloader it won't flash. For fastboot it says "unknown error" and as a PH file in bootloader it says "parsing..." for a few seconds then disappears without flashing anything. I've re-downloaded and checked md5's and still get the same errors.
My last rezound was s-off and that whole process was quick and painless and I don't understand why the same procedure I used on my last rezound isn't working now.
Any help would be greatly appreciated.
zac41189 said:
Hey all, just received a replacement rezound under warranty due to the charge port being all muffed up, and of coarse the first thing was unlock via htcdev which worked fine.
Here is the issue.. when trying to flash amonra via fastboot or PH98IMG.zip in bootloader it won't flash. For fastboot it says "unknown error" and as a PH file in bootloader it says "parsing..." for a few seconds then disappears without flashing anything. I've re-downloaded and checked md5's and still get the same errors.
My last rezound was s-off and that whole process was quick and painless and I don't understand why the same procedure I used on my last rezound isn't working now.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
What firmware is on the device?
hgoldner said:
what firmware is on the device?
Click to expand...
Click to collapse
ota 3.14.605.12 710rd.
Can you flash in fastboot usb? (And, to be perfectly clear to avoid a dumb question, does hboot reflect that you are unlocked?)
hgoldner said:
Can you flash in fastboot usb? (And, to be perfectly clear to avoid a dumb question, does hboot reflect that you are unlocked?)
Click to expand...
Click to collapse
indeed *** unlocked *** is displayed at the top on hboot. and ive tried "fastboot flash recovery (nameofrecovery.img) with nameofrecovery changed to what i have it saved as and no luck. even tried relocking and ruuing too just to make sure it wasnt the software messing everything up.
Can't remember but can you try to S-OFF first? (It's been so long, but I can't remember whether you have a custom recovery already on).
Ah, one other stupid thing.... have you tried a different sdcard?
hgoldner said:
Can't remember but can you try to S-OFF first? (It's been so long, but I can't remember whether you have a custom recovery already on).
Ah, one other stupid thing.... have you tried a different sdcard?
Click to expand...
Click to collapse
I was thinking about the sd card being the issue but it installed an ruu via ph98img.zip perfectly fine bit its worth a shot. And on unlimited.io's site they say you need to be completely stock with root and as far as I know amonra is the only way to root on a stock ruu. I managed to s-off tho after using hasoon's tool to flash amonra. I'm now completely stock again after ruuing back to gb then accepting ota
so I'll try flashing amonra again and report back. Thank you for your help!
Sent from my ADR6425LVW using xda premium
You can install any custom recovery and use it to flash SuperUser. The root option in Amon Ra doesn't usually work by itself anyway.
shrike1978 said:
You can install any custom recovery and use it to flash SuperUser. The root option in Amon Ra doesn't usually work by itself anyway.
Click to expand...
Click to collapse
Oh ok thats good to know actually. just cant seem to install any custom recoveries lol. i chose to install amon ra 3.15 with hasoons tool and for some reason i have 3.06 installed.. dont know how or why but i do. tried to install 3.15 with his toolkit again and got the stupid error again. i dont know what to do at this point lol. never had this problem with the last rezound. i am s-off now but do not have the recovery i want installed.
should i try ruu'ing again and start fresh?
and for what its worth i do have the jb hboot installed just to see if that was the issue. had to use fastboot commands to install it so i dont think thats the issue. i think its the download for amonra 3.15 i have. if anyone has a personal copy of 3.15 that is confirmed working and is willing to share it itd be greatly appreciated.
To use the fastboot commands you must be unlocked. With the parsing error. That will sometimes happen if you have a file called "update.zip" on your sdcard. Try seeing if you have one of those files. If your HBOOT does say s-off. Flash the GB RUU. Just so you can verify everything has changed. and then restart with the ICS RUU then flash a recovery. This time not with that tool.
Flyhalf205 said:
To use the fastboot commands you must be unlocked. With the parsing error. That will sometimes happen if you have a file called "update.zip" on your sdcard. Try seeing if you have one of those files. If your HBOOT does say s-off. Flash the GB RUU. Just so you can verify everything has changed. and then restart with the ICS RUU then flash a recovery. This time not with that tool.
Click to expand...
Click to collapse
Thank you for the response. i tested to see if i really did have s-off by doing just that. ruu'd back to gb without a hitch. then accepted the ota. so im thinking ill just ruu the ota (3.14.605.12) and see what happens. and im with you on not using the tool again. ive heard really good things about it but never used it personally until today. my old method worked well i just didn't know what else to do at that point lol
zac41189 said:
Thank you for the response. i tested to see if i really did have s-off by doing just that. ruu'd back to gb without a hitch. then accepted the ota. so im thinking ill just ruu the ota (3.14.605.12) and see what happens. and im with you on not using the tool again. ive heard really good things about it but never used it personally until today. my old method worked well i just didn't know what else to do at that point lol
Click to expand...
Click to collapse
To s-off you got to do the wire trick. But RUU then don't use the tool. lol Lets us now if it works out.
Flyhalf205 said:
To s-off you got to do the wire trick. But RUU then don't use the tool. lol Lets us now if it works out.
Click to expand...
Click to collapse
Yupp s-off'd with no issues. Just want amonra lol. Ruu'd to OTA and am waiting for my battery to charge up enough to flash via hboot. The amonra thread has a PH98IMG.zip but I think that one was the 3.06 version. Dunno. Will report back.
Sent from my ADR6425LVW using xda premium
zac41189 said:
Yupp s-off'd with no issues. Just want amonra lol. Ruu'd to OTA and am waiting for my battery to charge up enough to flash via hboot. The amonra thread has a PH98IMG.zip but I think that one was the 3.06 version. Dunno. Will report back.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I'm not trying to be a jerk or whatever but have you read the bottom of the AmonRA OP? It has a link to 3.15 I am pretty sure.
Curious. Why you want AR so bad? We have 2 other fully functional recoveries. lol
Flyhalf205 said:
I'm not trying to be a jerk or whatever but have you read the bottom of the AmonRA OP? It has a link to 3.15 I am pretty sure.
Curious. Why you want AR so bad? We have 2 other fully functional recoveries. lol
Click to expand...
Click to collapse
The ph98img.zip in that post is 3.06. I just got really used to it lol. I have twrp 2.3.2.3 downloaded for a couple weeks now.. might as well try it out lol.
Sent from my ADR6425LVW using xda premium
zac41189 said:
The ph98img.zip in that post is 3.06. I just got really used to it lol. I have twrp 2.3.2.3 downloaded for a couple weeks now.. might as well try it out lol.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Since you're on the OTA ICS firmware, you should definitely NOT be running Amon Ra 3.06. You need to be on 3.15. If the md5's match what's on your sdcard and what's on the OP at that thread, it shouldn't be a bad download, but just in case, I loaded it up on my Dropbox and you can try the one here.
As far as alternate recoveries, while I was very impressed with TWRP, it is incapable of wiping boot, so that's a nonstarter. Admittedly, if Flyhalf solved that issue, I'd switch to it. As far as CWM Touch, that has issues with reading sdcard2, as of the last time I checked, or at least with respect to its interaction with various ROMs and their features. For me at least, having tried all of the Rezound recoveries, Amon Ra is my preferred choice.
just push AR manually instead of using the tool:
Unzip the file from the link listed below onto the root of the C drive on your PC, and it should create a folder called Android on the root of C.
1) open a cmd prompt and type " cd c:\Android " without quotes
2) boot to fastboot and make sure your USB is plugged into the pc and phone
3) type " fastboot flash recovery recovery.img " without the quotes
This should push the AR 3.15 to your device. I included AR 3.15 in the Android folder below.
the folder contains a txt file of a few other handy commands that i use. that txt file is for reference only
https://www.dropbox.com/s/aycfqc37tvkhbdl/Android12-14-2012_22+21+19.rar
I ended up flashing twrp and it worked great. Like a previous poster said if it could wipe boot it would be perfect. But it got the job done and am up and running again. Thank you all for your help!
Sent from my Rezound using xda premium
Glad everything worked out for ya. Wiping boot can cause a lot of problems just sayin. So I debating on putting it back into TWRP. Just ask snuzzo in his kernel thread
So I have the virgin mobile 3d and I am rooted with s-on. I've been trying to get it off tho. So I was following the quick and dirty thread. And so I relocked the boot loader and then I started up the RUU like the guide. And about halfway through the installation it gave me boot loader version error 140. So I looked it up and I think it means that I was trying to downgrade. And that's why it didn't work. I was supposedly going from 1.14 down to 1.13. These are the version The ruu gave. I'm not sure what the numbers were about but can someone help? That ruu was supposed to be the most updated one. And i have been searching like crazy. Any help would be appreciated. I understand these things, so don't be afraid to talk techy to me lmfao. Thanks
Sent from my SPH-L710 using xda app-developers app
monstaX said:
So I have the virgin mobile 3d and I am rooted with s-on. I've been trying to get it off tho. So I was following the quick and dirty thread. And so I relocked the boot loader and then I started up the RUU like the guide. And about halfway through the installation it gave me boot loader version error 140. So I looked it up and I think it means that I was trying to downgrade. And that's why it didn't work. I was supposedly going from 1.14 down to 1.13. These are the version The ruu gave. I'm not sure what the numbers were about but can someone help? That ruu was supposed to be the most updated one. And i have been searching like crazy. Any help would be appreciated. I understand these things, so don't be afraid to talk techy to me lmfao. Thanks
Click to expand...
Click to collapse
See the note for S-ON users in this post, which is also linked in the informational posts after Step3 of the guide. The reason you are having this problem is because you have already installed the OTA, which has a higher main version (mainver) than the VM RUU.
ramjet73
ramjet73 said:
See the note for S-ON users in this post, which is also linked in the informational posts after Step3 of the guide. The reason you are having this problem is because you have already installed the OTA, which has a higher main version (mainver) than the VM RUU.
ramjet73
Click to expand...
Click to collapse
ramjet youre the man. Im about to read it. I will try and then report back thanks
monstaX said:
ramjet youre the man. Im about to read it. I will try and then report back thanks
Click to expand...
Click to collapse
Good.
Don't forget to download and flash the OTA again after the RUU is flashed since it requires the stock recovery.
ramjet73
ramjet73 said:
Good.
Don't forget to download and flash the OTA again after the RUU is flashed since it requires the stock recovery.
ramjet73
Click to expand...
Click to collapse
So it worked!! I finally got s-off!!! Now one last thing, how do i go about downgrading the hboot. I plan on going SlimBean. I tried flashing the sprint 1.5 hboot but it failed. The error said that the custom ID failed. . Is there any way to downgrade?
monstaX said:
So it worked!! I finally got s-off!!! Now one last thing, how do i go about downgrading the hboot. I plan on going SlimBean. I tried flashing the sprint 1.5 hboot but it failed. The error said that the custom ID failed. . Is there any way to downgrade?
Click to expand...
Click to collapse
That's in this post, which is also linked after Step3 of the guide.
ramjet73
I have tried this. And a side note* when I boot into the boot loader it doesn't look for PG86IMG.zip it looks for PG86DIAG.zip. its really weird. Anyone know what this is? I tried renaming it to that but it doesn't do anything. It just reboots the boot loader. I have also tried flashing it through fastboot
Sent from my SPH-L710 using xda app-developers app
monstaX said:
I have tried this. And a side note* when I boot into the boot loader it doesn't look for PG86IMG.zip it looks for PG86DIAG.zip. its really weird. Anyone know what this is? I tried renaming it to that but it doesn't do anything. It just reboots the boot loader. I have also tried flashing it through fastboot
Click to expand...
Click to collapse
The PG86DIAG.zip file is an advanced diagnostic that is very tightly controlled by HTC, but the bootloader always looks for it anyway.
The filename for the zip doesn't matter when you use the fastboot flashing method. Can you paste the messages you are getting here starting with the "fastboot erase cache" command? Make sure you delete the PG86IMG.zip file from the root of the SD card before trying the fastboot method.
ramjet73
ramjet73 said:
The PG86DIAG.zip file is an advanced diagnostic that is very tightly controlled by HTC, but the bootloader always looks for it anyway.
The filename for the zip doesn't matter when you use the fastboot flashing method. Can you paste the messages you are getting here starting with the "fastboot erase cache" command? Make sure you delete the PG86IMG.zip file from the root of the SD card before trying the fastboot method.
ramjet73
Click to expand...
Click to collapse
OK sweet that it good to know. I tried both methods and it didn't work. But when I used the fast boot method I got a custom I'd check failed error. I'm not by the phone right now. But I remember the error. That's the only one I got. When I tried downgrading from 1.57jboot to 1.5
Sent from my SPH-L710 using xda app-developers app
monstaX said:
OK sweet that it good to know. I tried both methods and it didn't work. But when I used the fast boot method I got a custom I'd check failed error. I'm not by the phone right now. But I remember the error. That's the only one I got. When I tried downgrading from 1.57jboot to 1.5
Click to expand...
Click to collapse
If you are on hboot 1.57 then you probably have the Evo V 4G which means you need to use the Virgin Mobile version of the RUU.
ramjet73
ramjet73 said:
If you are on hboot 1.57 then you probably have the Evo V 4G which means you need to use the Virgin Mobile version of the RUU.
ramjet73
Click to expand...
Click to collapse
So you're saying I should extract the PG86IMG.zip from an older VM ruu? And then place in the root of my sdcard? That would give me the stock boot loader :-/. I already got s-off with jbear hboot 1.7
I'm trying to dual boot eventually so I want to be on hboot 1.5
Edit: one thing I haven't tried is leaving it named PG86IMG.zip and placing it on the SD card. But using 1.5 is that safe to try?. I'm thinking it will work because it is a sprint phone. It has sprint branding. It is just on VM. Let me know what you think
Sent from my SPH-L710 using xda app-developers app
monstaX said:
So you're saying I should extract the PG86IMG.zip from an older VM ruu? And then place in the root of my sdcard? That would give me the stock boot loader :-/. I already got s-off with jbear hboot 1.7
I'm trying to dual boot eventually so I want to be on hboot 1.5
Edit: one thing I haven't tried is leaving it named PG86IMG.zip and placing it on the SD card. But using 1.5 is that safe to try?. I'm thinking it will work because it is a sprint phone. It has sprint branding. It is just on VM. Let me know what you think
Click to expand...
Click to collapse
Follow the instructions in this post since you are S-OFF already. I recommend the JBear 1.50.5050 instead on the 1.50 hboot since that doesn't need to be unlocked to run extended fastboot commands.
ramjet73
It seems like the questions about returning to 100% stock are coming up more often lately, possibly because more users are moving on to other devices. Whatever the reason, I thought a simple guide might be useful to avoid having to duplicate this info in other threads and PM's.
This procedure should work for any CDMA or GSM Evo 3D/V that is S-OFF. There is no way to get an S-ON device that has been HTC unlocked back to 100% stock since relocking the bootloader will result in a status of "relocked".
Here are the steps to do it:
1. Flash the "query_bootloader.zip" file attached to this post in recovery. If the status message shows your bootloader is "unlocked" or "relocked" flash the "lock_bootloader.zip" file from the same post to reset it to "locked".
2. Download an RUU.exe (Windows) or RUU.zip (bootloader) file for your model from this page and flash it using the appropriate method.
If you use the .exe version from Windows it works best if you put the phone into "fastboot USB" mode, and you may have to cancel the RUU utility and restart if it hangs after flashing the stock bootloader when you start with a custom hboot installed.
To flash the RUU.zip via the bootloader it must be renamed to PG86IMG.zip and placed in the root of your SD card, and may need to be flashed twice if a custom hboot is installed the first time it is flashed.
I recommend using the latest version for your model but any compatible RUU can be flashed while S-OFF. It's also a good idea to boot the ROM without doing any setup after flashing the RUU to make sure the ROM has been reset to the stock version.
3. Confirm that the bootloader shows "***LOCKED***" on the top line of the screen and the HBOOT version is a stock bootloader for your device.
4. Issue the "fastboot oem writesecureflag 3" command from a PC.
Note: Make 100% sure you have the stock bootloader installed before issuing this command or you will brick your phone.
Your phone will now be 100% stock.
ramjet73
Thanks for the nice toturial but i´m just wondering one thing.
If you fail with the command
Code:
fastboot oem writesecureflag 3
, will your phone get hardbricked or is it possible to flash a recovery and start over again with fastboot?
dR.BaNaNe said:
Thanks for the nice toturial but i´m just wondering one thing.
If you fail with the command
Code:
fastboot oem writesecureflag 3
, will your phone get hardbricked or is it possible to flash a recovery and start over again with fastboot?
Click to expand...
Click to collapse
If that command fails nothing will happen and your phone will stay S-OFF but the odds of that happening are very small unless your phone is not in "fastboot usb" mode when you issue it.
The risk involves issuing that command when you have a custom hboot like JBear or Revolutionary installed because those bootloaders are not signed and will cause the phone to brick. In that scenario you would not be able to get into recovery.
ramjet73
Ok thanks man.
Ok, in the RUU's I can download I have 2 problems:
1) How do I know which one to download? I see a few that have Sprint ICS. I have the Virgin Mobile phone Evo V 4g. Which one would I get?
2) I have already tried downloading a few of them, and each time it stops at a different point and windows says the zip file is not valid. Is there another place I can download the correct RUU?
I need to get this done soon as I have a replacement headed this way.
matt965 said:
Ok, in the RUU's I can download I have 2 problems:
1) How do I know which one to download? I see a few that have Sprint ICS. I have the Virgin Mobile phone Evo V 4g. Which one would I get?
Click to expand...
Click to collapse
This is the correct RUU for your phone.
2) I have already tried downloading a few of them, and each time it stops at a different point and windows says the zip file is not valid. Is there another place I can download the correct RUU?
Click to expand...
Click to collapse
If that link doesn't work for you the same RUU is available here, including an MD5 checksum you can use to verify the download.
I need to get this done soon as I have a replacement headed this way.
Click to expand...
Click to collapse
ramjet73 said:
1. Flash the "query_bootloader.zip" file attached to this post in recovery. If the status message shows your bootloader is "unlocked" or "relocked" flash the "lock_bootloader.zip" file from the same post to reset it to "locked".
Click to expand...
Click to collapse
how do i do this if i have no working recovery? iv been trying to ruu with RUU_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_219445_signed.exe
iv tried many ruu's but only 2 have ever gone through. when it does i just get reboots on htc screen. recovery does not seem to work.
thanks for the help. hope i havnt bricked my phone
birddseedd said:
how do i do this if i have no working recovery? iv been trying to ruu with RUU_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_219445_signed.exe
iv tried many ruu's but only 2 have ever gone through. when it does i just get reboots on htc screen. recovery does not seem to work.
thanks for the help. hope i havnt bricked my phone
Click to expand...
Click to collapse
This is the wrong thread for what you need to do and I posted a link to the correct guide in the thread you opened in the development forum that got moved to Q&A.
When you are ready to download the RUU look for the 2.89.651.2 version.
ramjet73
thank you ramjet for the link. my phone is now 99% stock. The 1% is because of the S-OFF part of the bootloader. It shows it is locked so that's good, but I think that means I can't turn S-ON, as it says in the first post. Oh well, hopefully they will accept it like that.
matt965 said:
thank you ramjet for the link. my phone is now 99% stock. The 1% is because of the S-OFF part of the bootloader. It shows it is locked so that's good, but I think that means I can't turn S-ON, as it says in the first post. Oh well, hopefully they will accept it like that.
Click to expand...
Click to collapse
if you figure out how to get jb roms to boot post back so we all can know how
birddseedd said:
if you figure out how to get jb roms to boot post back so we all can know how
Click to expand...
Click to collapse
JB roms don't boot with this phone??? Strange since mine booted just fine with them.
matt965 said:
JB roms don't boot with this phone??? Strange since mine booted just fine with them.
Click to expand...
Click to collapse
They do.
This is the wrong thread to discuss booting JB ROM's and I don't know why he posted that here.
ramjet73
Thanks for this thread, great to go back to 100% stock for warranty purposes...
But for sellers who's warranty has run out, the newest JB or ICS rom is the best
Which RUU do i use for a Sprint Evo 3?
I'd like to follow the instructions here; you pointed me to this OP in another reply when I asked how to go back to stock, but I don't know which one to use. I'm on hboot 1.50.5050 running CM 10.1 on a Sprint Evo 3D, using "Wild for the Night" and I want to go back to 100% stock, S-ON, unrooted, locked.
Is 'WWE' the US version? I know not to use RUUs for other countries but I can't tell which to use from the list.
(I used the jbear wire trick and have Ext4 installed if it makes any difference.)
occulus said:
I'd like to follow the instructions here; you pointed me to this OP in another reply when I asked how to go back to stock, but I don't know which one to use. I'm on hboot 1.50.5050 running CM 10.1 on a Sprint Evo 3D, using "Wild for the Night" and I want to go back to 100% stock, S-ON, unrooted, locked.
Click to expand...
Click to collapse
This is the RUU you want to use.
ramjet73
Does it work for EVO 3D GSM with Revolutionary?
Sorry for my english.
ramjet73 said:
This procedure should work for any CDMA or GSM Evo 3D/V that is S-OFF. There is no way to get an S-ON device that has been HTC unlocked back to 100% stock since relocking the bootloader will result in a status of "relocked".
Click to expand...
Click to collapse
t_mcpardi said:
Does it work for EVO 3D GSM with Revolutionary?
Sorry for my english.
Click to expand...
Click to collapse
Probably not, since ramjet said that in the OP.
t_mcpardi said:
Does it work for EVO 3D GSM with Revolutionary?
Sorry for my english.
Click to expand...
Click to collapse
raptoro07 said:
Probably not, since ramjet said that in the OP.
Click to expand...
Click to collapse
If he has Revolutionary and is S-OFF this guide should work as long as the RUU is available for the model of his phone. That's the only thing that is specific to the GSM or CDMA model.
ramjet73
Which ruu do I use I'm running hboot 1.50.5050 and bootloader is unlocked
rafylora1230 said:
Which ruu do I use I'm running hboot 1.50.5050 and bootloader is unlocked
Click to expand...
Click to collapse
The hboot doesn't matter, but if you are on Virgin Mobile you need this one.
ramjet73
I would like to start out with saying that I am not new to rooting/roms but a lot has changed since I went to iOS. I have TWRP accessible and I can push files to my /sdcard/
I have tried several rooms but all of them fail to install.
Can someone please tell me the steps I need to take to go back to either stock or have another ROM working? (RUU fails as well, however it does detect the phone)
Any help is appreciated and trust me I spent hours reading threads so not just posting this for an easy way out.
chirayu said:
I would like to start out with saying that I am not new to rooting/roms but a lot has changed since I went to iOS. I have TWRP accessible and I can push files to my /sdcard/
I have tried several rooms but all of them fail to install.
Can someone please tell me the steps I need to take to go back to either stock or have another ROM working? (RUU fails as well, however it does detect the phone)
Any help is appreciated and trust me I spent hours reading threads so not just posting this for an easy way out.
Click to expand...
Click to collapse
First, this should probably be in the Q&A section
Second, gonna need WAY more info about your phone. I assume you're rooted? S-off or S-on? What hboot version are you on? What version of TWRP are you currently using? What ROM are you on now? What RUU are you trying to use? Gonna have to give a little bit for us to work with.
Edit: Your signature also says you have the Evo Shift? Are you on the write forum?
Greenfieldan said:
First, this should probably be in the Q&A section
Second, gonna need WAY more info about your phone. I assume you're rooted? S-off or S-on? What hboot version are you on? What version of TWRP are you currently using? What ROM are you on now? What RUU are you trying to use? Gonna have to give a little bit for us to work with.
Edit: Your signature also says you have the Evo Shift? Are you on the write forum?
Click to expand...
Click to collapse
I apologize for posting this in the wrong forum, like I was saying I haven't been here in a while and signature is outdated by about 6 years
Heres the info
TWRP v2.7.1.0
S-ON
HBOOT-2.10.0000
RADIO-1.13.11.1105
I had the last leaked RUU installed before I attempted flashing a custom ROM
Thank you for your reply!
chirayu said:
I apologize for posting this in the wrong forum, like I was saying I haven't been here in a while and signature is outdated by about 6 years
Heres the info
TWRP v2.7.1.0
S-ON
HBOOT-2.10.0000
RADIO-1.13.11.1105
I had the last leaked RUU installed before I attempted flashing a custom ROM
Thank you for your reply!
Click to expand...
Click to collapse
Is your goal to flash another ROM or to go back to stock?
If you're going to be trying to flash another ROM I'd highly recommend running rumrunner and getting s-off. Otherwise there are a lot of hoops you'll need to jump through in order to flash ROMs (for starters, you'll need to flash the kernel separately).
Code:
Greenfieldan said:
Is your goal to flash another ROM or to go back to stock?
Click to expand...
Click to collapse
Whichever one is faster, I just want the phone up and running again.
So it's not running at all now? I'm assuming you can boot into bootloader and recovery but nothing else, right? You can run an RUU while in fastboot if I recall, which will give you at least a usable phone. That's also probably the fastest thing to do.
After that I'd highly recommend using rumrunner to get s-off. Otherwise flashing new ROMs will be a bear.
Greenfieldan said:
So it's not running at all now? I'm assuming you can boot into bootloader and recovery but nothing else, right? You can run an RUU while in fastboot if I recall, which will give you at least asable phone. That's also probably the fastest thing to do.
After that I'd highly recommend using rumrunner to get s-off. Otherwise flashing new ROMs will be a bear.
Click to expand...
Click to collapse
RUU fails with errors and it gets stuck at "HTC" screen
Do you have HTC Sync installed on your computer?
Greenfieldan said:
Do you have HTC Sync installed on your computer?
Click to expand...
Click to collapse
Ah, I think something else made me delete it.
That'll do it. You need to have HTC Sync and all of the necessary drivers to run the RUU
Greenfieldan said:
That'll do it. You need to have HTC Sync and all of the necessary drivers to run the RUU
Click to expand...
Click to collapse
Thank you! giving that a try now
greenfieldan said:
that'll do it. You need to have htc sync and all of the necessary drivers to run the ruu
Click to expand...
Click to collapse
error [155]: Uknown error
chirayu said:
error [155]: Uknown error
Click to expand...
Click to collapse
D'oh! I bet your bootloader is still unlocked. It needs to be relocked before running the RUU.
Fastboot command 'fastboot oem lock' ought to do the trick.
Greenfieldan said:
D'oh! I bet your bootloader is still unlocked. It needs to be relocked before running the RUU.
Fastboot command 'fastboot oem lock' ought to do the trick.
Click to expand...
Click to collapse
You're a life saver! at least you can bet I have rooting/unrooting down for this EVO. Just like the old times
Moved to Q&A forum