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
Related
Is there a way to downgrade htc hboot 1.58. I have tried the live cd tool, but when i try to brick my phone, the hboot says file is older than main verson or something like that and it makes me reboot. Please help. I really dont want to HTC unlock, but will if i have to.
You can S OFF on Hboot 1.58
Ask Jesus for help!
Uncle Lizard said:
Ask Jesus for help!
Click to expand...
Click to collapse
Thanks for being helpful.
Stay on topic. Also, if you cannot help, it would be better not to post these insignificant responses.
Uncle Lizard said:
Ask Jesus for help!
Click to expand...
Click to collapse
I did, but help dosen't come in miracles or thunder bolts. It is sent through others. I will pray that you open your eyes to God. :angel:
Back on topic. I am trying to downgrade my h-boot not gain s-off. I want to go to 1.4 again.
jesuslovesyou said:
I am trying to downgrade my h-boot not gain s-off. I want to go to 1.4 again.
Click to expand...
Click to collapse
You should S OFF first. i think it's possible to downgrade with S ON there may be a thread in the Dev section, but I don't recommend that.
Uncle Lizard said:
Ask Jesus for help!
Click to expand...
Click to collapse
He can't ask Jesus for help because he's dead and his body died 2000 years ago. lmao! What I've found is there is no need to downgrade as long as you stick with ICS. of course I have no idea what I'm talking about. BUT those guys that figured it out do!
kgs1992 said:
You should S OFF first. i think it's possible to downgrade with S O there may be a thread in the Dev section, but I don't recommend that.
Click to expand...
Click to collapse
You cannot downgrade and flash a different downloader unless you are s-off.
Sent from my PG86100 using xda app-developers app
Flash an RUU that would have 1.4 like ver 1.13 in Fastboot USB:
http://shipped-roms.com/index.php?category=android&model=Shooter
From there, flash a recovery. I suggest getting 4ext control app.
Tribulattifather said:
Flash an RUU that would have 1.4 like ver 1.13 in Fastboot USB:
http://shipped-roms.com/index.php?category=android&model=Shooter
From there, flash a recovery. I suggest getting 4ext control app.
Click to expand...
Click to collapse
I tried running the RUU and and it said ERROR wrong bootloader or some equivalent . ( im on 1.58 locked S-ON)
having a helluva time downgrading, even HTC Dev unlock is telling me the same bootloader crap
grandpasghost said:
I tried running the RUU and and it said ERROR wrong bootloader or some equivalent . ( im on 1.58 locked S-ON)
having a helluva time downgrading, even HTC Dev unlock is telling me the same bootloader crap
Click to expand...
Click to collapse
Running the RUU will not downgrade. If it did why would they have had to make all of the complex steps to downgrade from 1.50.
Is there a way to make the RUU see the phone as a lower h-boot version without root access by tweaking the RUU exe. just a thought.
jesuslovesyou said:
Running the RUU will not downgrade. If it did why would they have had to make all of the complex steps to downgrade from 1.50.
Is there a way to make the RUU see the phone as a lower h-boot version without root access by tweaking the RUU exe. just a thought.
Click to expand...
Click to collapse
Like a previous poster responded, get s-off using the wire trick. It only takes five minutes once you setup. People who have done it wish they would have done it sooner.
Look the bottom line is if you want to go back to H-boot 1.40 you need to S-off.
Countless people in this thread have said that and you refuse to accept the fact your stuck on H-boot 1.58 until you S-off.
I am on relocked 1.58 s-off from 1.4s-off. how do i go about reverting it back to 1.4 s-off?
failmatic said:
I am on relocked 1.58 s-off from 1.4s-off. how do i go about reverting it back to 1.4 s-off?
Click to expand...
Click to collapse
Download the 1.4 hboot, rename the file PG86IMG.zip (case sensitive) and place it on the root of your sd card. Make sure that the ROM you are running will boot with the 1.4 hboot first. If not, boot to recovery and flash one (the reason I suggest this is if you have an hboot 1.58 ROM on there and flash the 1.4 hboot, you'll get bootloops). Then, boot to bootloader and have it "update" to 1.4. Reboot and remove the file from the root of your sd card.
raptoro07 said:
You cannot downgrade and flash a different downloader unless you are s-off.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Bricking the phone with S ON will cause it to enter emmc mode in which an Hboot can be flashed.
But he should change the main version to the lower one before attempting to brick it.
After flashing the hboot, device will have been unbricked, but RUU still needs to be flashed.
It is possible, but whether there is a guide for this or not, I don't know; nor do I know if it is practically possible either.
failmatic said:
I am on relocked 1.58 s-off from 1.4s-off. how do i go about reverting it back to 1.4 s-off?
Click to expand...
Click to collapse
If you have PG86IMG.zip that contains only hboot 1.40, you can flash it through bootloader or you can flash eng bootloader
Sent from my PG86100 using Tapatalk 2
Go with this thread. It gave me s-off and I went back with no problem to hboot 1.50. Excellent tutorial. just follow it to the tee and you'll have no problems!!! :victory:
http://forum.xda-developers.com/showthread.php?t=1813818
coal686 said:
Download the 1.4 hboot, rename the file PG86IMG.zip (case sensitive) and place it on the root of your sd card.
Click to expand...
Click to collapse
Where does one find the 1.4 hboot by itself?
Sent from my PG86100 using xda app-developers app
Roosafur said:
Where does one find the 1.4 hboot by itself?
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Try this post: http://forum.xda-developers.com/showthread.php?p=29844085
Read, Search, Read again, ... Then Ask with Tapatalk 2
may sound like a stupid question but I have been googleing this and searching xda for over an hr. Im not new to android rooting and such but I always want to be carefull when doing the initial rooting and such.
I followed the Juopunutbear S-OFF instructions and now im trying to do the
[MOD][S-OFF] SuperCID Your Amaze!
http://forum.xda-developers.com/showthread.php?t=1612475
My device has ICS and as per the OP it says
Also, if you've upgraded to ICS, the 1.93.0002 SHP Hboot is required to SuperCID!
Im trying to find out how to get this HBOOT installed.
All the software I found says I need a HBOOT.img file. I found some HBOOT files on JuopunutBear site but they dont have any img files only
hboot_8x60-lte_1.93.2222_20120315_signedbyaa.nb0
How am I supposed to downgrade?
Any help is welcomed
fidorulz said:
may sound like a stupid question but I have been googleing this and searching xda for over an hr. Im not new to android rooting and such but I always want to be carefull when doing the initial rooting and such.
I followed the Juopunutbear S-OFF instructions and now im trying to do the
[MOD][S-OFF] SuperCID Your Amaze!
http://forum.xda-developers.com/showthread.php?t=1612475
My device has ICS and as per the OP it says
Also, if you've upgraded to ICS, the 1.93.0002 SHP Hboot is required to SuperCID!
Im trying to find out how to get this HBOOT installed.
All the software I found says I need a HBOOT.img file. I found some HBOOT files on JuopunutBear site but they dont have any img files only
hboot_8x60-lte_1.93.2222_20120315_signedbyaa.nb0
How am I supposed to downgrade?
Any help is welcomed
Click to expand...
Click to collapse
The .2222 Hboot will work.
Sent from my HTC Ruby using xda app-developers app
Keylogger_0 said:
The .2222 Hboot will work.
Sent from my HTC Ruby using xda app-developers app
Click to expand...
Click to collapse
but do I have to rename the file extension?
The Amaze_SOFF_All-In-One_Kit says it needs a HBOOT.img file
Thanks
fidorulz said:
but do I have to rename the file extension?
The Amaze_SOFF_All-In-One_Kit says it needs a HBOOT.img file
Thanks
Click to expand...
Click to collapse
Yep just rename it. However, make SURE it's the right Hboot.
Other than that, just rename it to hboot.img and you should be golden.
Out of curiosity, what HBOOT are you currently on?
Keylogger_0 said:
Yep just rename it. However, make SURE it's the right Hboot.
Other than that, just rename it to hboot.img and you should be golden.
Out of curiosity, what HBOOT are you currently on?
Click to expand...
Click to collapse
When you mean the right one you mean GB or ICS right? You may find this funny but im getting the phone in about 1hr.
Whenever I get a new android phone I like to research all the procedures and possible issues and download all the needed files prior to getting it.
That way im not stuck with a bricked phone trying to figure stuff out afterwards
fidorulz said:
When you mean the right one you mean GB or ICS right? You may find this funny but im getting the phone in about 1hr.
Whenever I get a new android phone I like to research all the procedures and possible issues and download all the needed files prior to getting it.
That way im not stuck with a bricked phone trying to figure stuff out afterwards
Click to expand...
Click to collapse
You should worry about S-OFF first before you actually worry about supercid. Also, if you do S-OFF and you choose to install the j-bear modified hboot, it installs the .2222 hboot so you really don't need to flash an hboot, because it does that already. But still, do check before you actually attempt supercid
Keylogger_0 said:
You should worry about S-OFF first before you actually worry about supercid. Also, if you do S-OFF and you choose to install the j-bear modified hboot, it installs the .2222 hboot so you really don't need to flash an hboot, because it does that already. But still, do check before you actually attempt supercid
Click to expand...
Click to collapse
Ya I saw that step just didnt know it did the HBOOT also
Thanks
fidorulz said:
Ya I saw that step just didnt know it did the HBOOT also
Thanks
Click to expand...
Click to collapse
Once you s-off, shp hboot should be your default.
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
This is going to be a short and simple guide for S-OFF users that want to update to the current RUU level or refresh their phone because they are having issues like being unable to boot certain ROM's. You will not lose S-OFF by flashing the RUU.
1. Do a nandroid backup of your current ROM if you want to restore it later.
2. Download the current version of the RUU for your phone in exe or zip format from this page.
3. Run the exe version of the RUU in Windows or the zip version as a PG86IMG.zip file through the bootloader. If using the bootloader method make sure the file is named exactly "PG86IMG.zip" and placed in the root of your SD card before starting the bootloader.
There is no need to unlock the bootloader before running it if you are S-OFF and there is troubleshooting information in this post if you have problems. It may be necessary to run the RUU twice if you have a custom bootloader installed when it is run the first time. If the utility hangs after flashing the bootloader from Windows just cancel it and restart.
I recommend downloading and installing the OTA(s) immediately after flashing the RUU to get the most current firmware while still 100% stock, but the OTA firmware update(s) can be downloaded as a separate PG86IMG.zip file if you forget or can't do that for some reason.
4. Flash a custom hboot using the instructions in this post. My recommendation for a good general purpose hboot is the JBear GB 1.50.5050 version unless you are running an ICS Sense ROM like stock or Cool ICS that requires an ICS bootloader (1.57.xxxx or 1.58.xxxx).
5. Connect your phone to a PC and start the bootloader in "fastboot USB " mode, then issue the following command to flash your favorite recovery:
fastboot flash recovery recovery.img (where "recovery.img" is the name of the recovery file in your ADB/fastboot directory)
6. Boot into recovery and restore a nandroid or flash another custom ROM. You may have to wipe cache+dalvik and restart recovery if you get any error messages from the recovery program.
That's it. You're now updated or re-synced with the current firmware, the hboot that meets your requirements and your favorite recovery.
Here are some additional links that might be helpful:
4EXT Recovery OP for the Evo 3D CDMA thread with a direct link to recovery.img in the download section (not the most current version)
Current TeamWin (TWRP2) touch recovery for the CDMA Evo 3d.
Virgin Mobile OTA firmware only in PG86IMG.zip format.
Sprint OTA firmware only in PG86IMG.zip format.
ramjet73
Thanks for this.
Question,the RUU links...
Am I looking for the link with the radio he has currently on his phone?
0.97.10.0530?
3volution said:
Thanks for this.
Question,the RUU links...
Am I looking for the link with the radio he has currently on his phone?
0.97.10.0530?
Click to expand...
Click to collapse
No. That's an older GB level and the most current RUU for the Evo 3D is the 2.89.651.2 ICS version. That's the one I recommend.
Since he is S-OFF already it's easy to revert to a GB RUU if neccessary.
ramjet73
I better not mess with it,lol
This isn't anything like flashing new ROM's on my phone.
Thanks though.
3volution said:
I better not mess with it,lol
This isn't anything like flashing new ROM's on my phone.
Thanks though.
Click to expand...
Click to collapse
You're welcome.
It's not really that difficult if you are familiar with rooting and flashing HTC devices but I can understand how it might be for users coming from other brands. Samsung in particular is definitely less complicated.
ramjet73
Thanks!
Thanks for this great post ramjet. Really a great concise How-to.
Nevermind, fixed.
ramjet73 said:
No. That's an older GB level and the most current RUU for the Evo 3D is the 2.89.651.2 ICS version. That's the one I recommend.
Since he is S-OFF already it's easy to revert to a GB RUU if neccessary.
ramjet73
Click to expand...
Click to collapse
I flashed the above RUU .exe and I'll get to 10%, then my phone reboots (RUU program says "attaining bootloader" or something) and go into a bootloop. Is there a specific hboot necessary to run this. I am on 1.04.200 and s-off, 1.09.00.706
I also tried updating via the bootloader method as well..... runs well....updates like four of the ten check offs and then bootloops as well.
Edit: turns out I was flashing the wrong version, oops
Hedied4me said:
I flashed the above RUU .exe and I'll get to 10%, then my phone reboots (RUU program says "attaining bootloader" or something) and go into a bootloop. Is there a specific hboot necessary to run this. I am on 1.04.200 and s-off, 1.09.00.706
Click to expand...
Click to collapse
From experience I've discovered that the RUU.exe utility will sometimes stop after flashing the stock bootloader if it is run with a custom hboot installed, which is why I put this comment in the OP:
If the utility hangs after flashing the bootloader from Windows just cancel it and restart.
Click to expand...
Click to collapse
I've had no problem completing the RUU.exe flash if I just cancel the utility in the Windows task manager and restart it.
Others have reported that re-flashing the RUU.zip file through the bootloader also works if the original flash is incomplete.
Also, make sure that you downgrade your hboot after flashing the RUU since the stock hboot won't boot GB or AOSP based ROM's.
ramjet73
Ok one more stupid question, after successfully flashing the correct RUU my phone boots into the stock virgin mobile. How do I get into bootloader (to flash OTA update and hboot) from here since holding power and volume down button from off no longer work.
Sent from my HTCEVOV4G using Tapatalk 2
Hedied4me said:
Ok one more stupid question, after successfully flashing the correct RUU my phone boots into the stock virgin mobile. How do I get into bootloader (to flash OTA update and hboot) from here since holding power and volume down button from off no longer work.
Click to expand...
Click to collapse
Try removing/replacing the battery and then use the Power+VolumeDown buttons together to enter the bootloader.
The stock ROM has the "fast boot" option turned on in the power settings by default and that will interfere if you try to enter the bootloader after powering down from the stock ROM.
ramjet73
Thank you very much for your patience and help Ramjet. Everything went well.
Sent from my Evo V 4G using Tapatalk 2
Please excuse me this might have been asked before.
I'm currently S-Off H-boot 1.40 but still on gingerbread firmware(2.17 radio 0.97.10.0530). also flashed to Boost Mobile. My question is if I run RUU to newest build will I lose boost mobile flash?
El Queson said:
Please excuse me this might have been asked before.
I'm currently S-Off H-boot 1.40 but still on gingerbread firmware(2.17 radio 0.97.10.0530). also flashed to Boost Mobile. My question is if I run RUU to newest build will I lose boost mobile flash?
Click to expand...
Click to collapse
I honestly don't know.
There is a post by a cricket user in my rooting and S-OFF guide that says the customization is not lost for that carrier but I've never used Boost and can't speak to that.
Perhaps another Boost user on these forums has experience with flashing the RUU.
ramjet73
++sorry++
Using the bootloader procedure is, by far, the easiest way of doing the RUU process that I've encountered. From custom ROM, to stock, back to a custom ROM in less than 45 minutes.
ramjet, thank you for your contributions to our platform.
so my wife is hboot 1.40, radio version 0.97.... running a GB ROM. I need to update her EVERYTHING(you pointed me here) and get her on NegaLite BluROM. I believe I will need to update her hboot as well. At what point in this process should that be done? Do I need to be worried that her current ROM is incompatible with either the new RUU or the new bootloader? And if it is, then I just work through it all in recovery?
Very useful thread, and thank you very much, by the way.
GAPO said:
so my wife is hboot 1.40, radio version 0.97.... running a GB ROM. I need to update her EVERYTHING(you pointed me here) and get her on NegaLite BluROM. I believe I will need to update her hboot as well. At what point in this process should that be done? Do I need to be worried that her current ROM is incompatible with either the new RUU or the new bootloader? And if it is, then I just work through it all in recovery?
Very useful thread, and thank you very much, by the way.
Click to expand...
Click to collapse
Is her phone S-OFF? If so, there is a link in the OP to a post that covers updating the hboot. If not, the only way to update the hboot is to flash a more current RUU.
ramjet73
ramjet73 said:
Is her phone S-OFF? If so, there is a link in the OP to a post that covers updating the hboot. If not, the only way to update the hboot is to flash a more current RUU.
ramjet73
Click to expand...
Click to collapse
Yes she is S-off. She also already has 4ext recovery installed.
Does this negate my need to flash recovery in the downloader?
Since she is S-off, this should be pretty easy.
I will still need to access the bootloader via Windows cmd, yes? Or can I accomplish all of this using only the handset?
Sent from my PG86100 using xda premium
---------- Post added at 07:07 PM ---------- Previous post was at 06:52 PM ----------
Her hboot is:
SHOOTER XC SHIP S-OFF RL
HBOOT-1.40.0000
RADIO-0.97.10.0530
eMMC-boot
Jun 8 2011, 17:20:22
Is this a custom hboot, or stock? I ask because of the caution on the OP regarding custom bootloaders. And I am not sure because I changed her bootloader a week or so ago and had to change it back.
Sent from my PG86100 using xda premium
GAPO said:
Is this a custom hboot, or stock? I ask because of the caution on the OP regarding custom bootloaders. And I am not sure because I changed her bootloader a week or so ago and had to change it back.
Click to expand...
Click to collapse
That's a stock hboot so you should be fine. You can still update using the RUU if a custom hboot is installed, but it might take a restart to complete after the stock hboot is installed.
ramjet73
Hello. Never made a thread before and was really hoping I wouldn't have to or would find an answer elsewhere.
Since that didn't work out, here's my problem:
Background: Evo 3d, virgin mobile, unlocked bootloader, s-off, hboot was at 1.50, and I don't remember what the radio was at. I was running CM11 and was quite happy until two days ago when I stopped receiving texts! No clue why, just stopped. Hangouts, etc etc. Called VM and they had no idea why that was happening either. Tried switching roms, reinstalling backups, etc etc. Clean wipes and all. Then I saw someone said they had to [for some reason] reinstall everything stock and then they had messaging back. So that's what I set out to do.
In Between: Used the RUU that I'm fairly certain came with my phone. Everything was good, it erased everything, and "updated system" and signatures. It was almost finished when BAM, popped up with error 152 Image Update Error; right at the very end. Quite disappointing. Tried it multiple times again with the same result. Not sure what to do.
Current: Only screen I can see (looks like shortened bootloader screen) says "***locked***" at the top, hboot 1.57.0000, radio 1.06.00.126, then says openADSP-v02.6.0.2226.00.0217eMMc-boot
Also tried flashing the unlock_code.bin, and while it took it, it changed nothing. One screen I did see very briefly but cannot replicate said that everything was there except system. Not really sure how to take that or what to do. Any and all help would be helpful. As is it sits on the HTC screen with exclamation points in each corner. When unplugged from usb it gives me that above screen. Removing battering and restarting to bootloader still gives the same screen.
Did you run ruu through windows or pg86img.zip?
Sent from my Evo 3D CDMA using xda app-developers app
hossman said:
Did you run ruu through windows or pg86img.zip?
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
Through Windows; the RUU exe.
SammyMak said:
Through Windows; the RUU exe.
Click to expand...
Click to collapse
You can try this
https://www.dropbox.com/s/d4baafpgchgg4ef/ruu-PG86IMG.zip
Put that on the root of your SD card and rename to pg86img.zip
Make sure its the only one there
Boot to boot loader and accept updates
It may reboot itself to bootloader, if it asks to accept again then accept
When its done reboot your phone
Rename or remove the file when done
Hope that helps
Sent from my Evo 3D CDMA using xda app-developers app
So I have my phone working now. I think it was the RUU.exe that I was using. I downloaded a different one from here http://androidruu.com/Shooter/ after much googling. That finally restored it to original VM stock rom etc. I couldn't use your method of placing the zip onto the root of my SD because despite it being there, it wouldn't go through the normal search for the file. I would remove the battery, put it back in, use the button key combo to try and open to bootloader, and it would go but it would be the page with the status and then it would instantly go back to the black screen with HTC logo.
Thank you for your help though!
Also I'm not sure how useful exactly this will be for anyone else, but if you find yourself ruu'd and needing better files...
The hboot ENG 1.04 I got from here: http://forum.xda-developers.com/showthread.php?t=1817513
ALL other downloads of that hboot did not work AT ALL.
I got the updated radio from here: http://androidforums.com/cdma-evo-3d-all-things-root/648902-radios-hboot-firmware-all-downloads.html
The hboots on that site however are stock and most likely won't run the custom roms as well, if at all, as 1.04.
SammyMak said:
I got the updated radio from here: http://androidforums.com/cdma-evo-3d-all-things-root/648902-radios-hboot-firmware-all-downloads.html
But the hboots on the site aren't helpful fyi
Click to expand...
Click to collapse
Hey, that's my thread. Just curious what you mean by the hboots aren't helpful?
If there is a problem I'm unaware of, I'd be happy to know what it is so I can get it squared away.
hossman said:
You can try this
https://www.dropbox.com/s/d4baafpgchgg4ef/ruu-PG86IMG.zip
Put that on the root of your SD card and rename to pg86img.zip
Make sure its the only one there
Boot to boot loader and accept updates
It may reboot itself to bootloader, if it asks to accept again then accept
When its done reboot your phone
Rename or remove the file when done
Hope that helps
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
thank you!
Brian706 said:
Hey, that's my thread. Just curious what you mean by the hboots aren't helpful?
If there is a problem I'm unaware of, I'd be happy to know what it is so I can get it squared away.
Click to expand...
Click to collapse
I must apologize! I seem to have mis stated that; they are helpful with regards to them being the stock hboots. However in my particular case those stock hboots weren't for me. I'll edit that here in a sec, but if I was going back to full stock I'd definitely use your stock VM hboot and it would be helpful in that case. Hope that makes sense, no disrespect meant!
SammyMak said:
I must apologize! I seem to have mis stated that; they are helpful with regards to them being the stock hboots. However in my particular case those stock hboots weren't for me. I'll edit that here in a sec, but if I was going back to full stock I'd definitely use your stock VM hboot and it would be helpful in that case. Hope that makes sense, no disrespect meant!
Click to expand...
Click to collapse
Thanks for clarifying that! I see what you meant now.
No worries, I didn't take offense or think you were disrespectful; I just wanted to make sure the downloads were working properly!
And for the record, the stock hboots will work just fine with custom roms. Hboot 1.50 for example will be compatible with the same selection of roms as JuopunutBear 1.50.5050. The difference is that JuopunutBear is patched and will allow for extra fastboot commands and allow them to be run on a locked bootloader.
The eng 1.04 hboot allows for extra fastboot commands that the stock hboot cannot. But you can boot any rom out there on the stock hboots. I've used stock 1.50 forever on this device.