Related
I am stuck in HBOOT after after fastboot oem lock from cmd
Now reads:
RELOCKED
Security Warning
HBOOT 2.10
Radio -0.95.00.1017_2r/0.95.00.1013r
OpenDSP-v10.6.0.7611.00.0919
Reboot sends me back..
Power Down ..reboots to HBOOT
Can I run RUU via pc? Is this>>> WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_8k_1.12_9k_1.83_V_APT_release_2215<<< the correct version?
If so..How do i enter RUU mode??
Please Help! Thanks
drknrgy said:
I am stuck in HBOOT after after fastboot oem lock from cmd
Now reads:
RELOCKED
Security Warning
HBOOT 2.10
Radio -0.95.00.1017_2r/0.95.00.1013r
OpenDSP-v10.6.0.7611.00.0919
Reboot sends me back..
Power Down ..reboots to HBOOT
Can I run RUU via pc? Is this>>> WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_8k_1.12_9k_1.83_V_APT_release_2215<<< the correct version?
If so..How do i enter RUU mode??
Please Help! Thanks
Click to expand...
Click to collapse
you can pull the rom.zip from the ruu, and run that in hboot.. or just unlock the bootloader again
drknrgy said:
I am stuck in HBOOT after after fastboot oem lock from cmd
Now reads:
RELOCKED
Security Warning
HBOOT 2.10
Radio -0.95.00.1017_2r/0.95.00.1013r
OpenDSP-v10.6.0.7611.00.0919
Reboot sends me back..
Power Down ..reboots to HBOOT
Can I run RUU via pc? Is this>>> WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_8k_1.12_9k_1.83_V_APT_release_2215<<< the correct version?
If so..How do i enter RUU mode??
Please Help! Thanks
Click to expand...
Click to collapse
Yes, you can run the RUU via pc in fastboot. That's how I ran it . Just as long as it says fastbootusb , it will work.
I was stuck in Hboot as well.. so not sure how you avoid it. Easy enough to run the RUU out of fastboot though.
andybones said:
you can pull the rom.zip from the ruu, and run that in hboot.. or just unlock the bootloader again
Click to expand...
Click to collapse
Can I run the RUU.exe directly on pc while in fastboot usb?
"you can pull the rom.zip from the ruu, and run that in hboot." not sure what that means if you run RUU.exe on pc How could I "pull the rom.zip from the ruu" if I cant run recovery??
Never ran RUU
Ok Just to make sure then.. Am I running the correct RUU? Will this further effect me if trying to run the wrong RUU file ? I guess my question is, to be more specific, does my listed RADIO in hboot need the correct RUU file ??
drknrgy said:
Ok Just to make sure then.. Am I running the correct RUU? Will this further effect me if trying to run the wrong RUU file ? I guess my question is, to be more specific, does my listed RADIO in hboot need the correct RUU file ??
Click to expand...
Click to collapse
It won't let you run the wrong RUU.. if you havent taken the OTA yet, the correct RUU is 1.06.xxxxx
Yes, you run the exe on the PC while in fastboot.
mjh68 said:
It won't let you run the wrong RUU.. if you havent taken the OTA yet, the correct RUU is 1.06.xxxxx
Yes, you run the exe on the PC while in fastboot.
Click to expand...
Click to collapse
Is there a way to determine the correct RUU? This one>>>>
WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_ 8k_1.12_9k_1.83_V_APT_release_2215<<<<
FAILED
"ERROR [140] BOOTLOADER VERSION ERROR"
Would the latest > new RUU for 2.01.605.11 < WorK?
drknrgy said:
Is there a way to determine the correct RUU? This one>>>>
WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_ 8k_1.12_9k_1.83_V_APT_release_2215<<<<
FAILED
"ERROR [140] BOOTLOADER VERSION ERROR"
Would the latest > new RUU for 2.01.605.11 < WorK?
Click to expand...
Click to collapse
Did you update with the OTA or have your main ver updated ? Sounds like you had a partial update with the bootloader being updated to 2.11 maybe.
Try the new RUU see if it will run it.
mjh68 said:
Did you update with the OTA or have your main ver updated ? Sounds like you had a partial update with the bootloader being updated to 2.11 maybe.
Try the new RUU see if it will run it.
Click to expand...
Click to collapse
I do not have the new OTA. I was root/unlocked. I tried doing wipe from ra and then run CleanRom GBE 1.6OTA zip from sd. Then I think I ran fastboot boot.img...
I have lost track of my steps at this point but the bootloader still states HBOOT-2.10.0000 on the white security warning screen w/3 droids at the bottom
BTW...Is there a direct link for new RUU available? DpBox??
drknrgy said:
I do not have the new OTA. I was root/unlocked. I tried doing wipe from ra and then run CleanRom GBE 1.6OTA zip from sd. Then I think I ran fastboot boot.img...
I have lost track of my steps at this point but the bootloader still states HBOOT-2.10.0000 on the white security warning screen w/3 droids at the bottom
BTW...Is there a direct link for new RUU available? DpBox??
Click to expand...
Click to collapse
It is in the developement forum.. Sticky thread for the Vigor rom collection. It was on the last page.. might have been bumped back a page or so.
Hmm , not sure why it is giving you that error if you still have hboot 2.10 , let me check and make sure that first RUU was the right one. Yes, you quoted the same RUU I used when I did the process.
mjh68 said:
It is in the developement forum.. Sticky thread for the Vigor rom collection. It was on the last page.. might have been bumped back a page or so.
Hmm , not sure why it is giving you that error if you still have hboot 2.10 , let me check and make sure that first RUU was the right one. Yes, you quoted the same RUU I used when I did the process.
Click to expand...
Click to collapse
Thanks for the D/L on the latest RUU.. almost finished. If I run this one via .exe and still get a failure re: bootloader what are my other options? I have other options don't I? Can I use a cmd to "push"? Any ideas? Thanks for all the help!
before running the RUU...
current image Version:
2.01.605.11
(same as latest RUU) crossing fingers now..
drknrgy said:
Thanks for the D/L on the latest RUU.. almost finished. If I run this one via .exe and still get a failure re: bootloader what are my other options? I have other options don't I? Can I use a cmd to "push"? Any ideas? Thanks for all the help!
before running the RUU...
current image Version:
2.01.605.11
(same as latest RUU) crossing fingers now..
Click to expand...
Click to collapse
Looks like somehow your mainver did get updated so the newest RUU should work. If this one fails I am out of ideas, I am fairly new to this myself so learning as I go. RUU's are similar to SBF's from motorla to return phone to stock out of the box condition. The way they work I don't think you can force push it to restore as far as I know.
This one worked perfectly and included the OTA . I am however complete stock now, lost root. My mind is a bit warped from all this confusion. How do I get root back again..? Flash amon ra ? go into Developer and install su. ?
drknrgy said:
This one worked perfectly and included the OTA . I am however complete stock now, lost root. My mind is a bit warped from all this confusion. How do I get root back again..? Flash amon ra ? go into Developer and install su. ?
Click to expand...
Click to collapse
Yes, just go into amon ra install su and superuser , then reboot. Might have to still download superuser from the market and install ,but then you should be good to go.
mjh68 said:
Yes, just go into amon ra install su and superuser , then reboot. Might have to still download superuser from the market and install ,but then you should be good to go.
Click to expand...
Click to collapse
Thanks for the great advice. I am back up and running w/OTA and root. Just need to nan-restore now. Bring on ICS!
i have read this post and my problem is somewhat similar. i can't seem to get my computer to read my phone. my sd port isn't coming up. i have my phone connected and using hasoon2000 all in one tool kit. my hboot version is 20225.0000 and radio is 1.22.10.0421r/1.22.10.042r. how can i get my phone off this white screen and also how can i get my phone and computer to read each other??? im also relocked i tried to unlock it using hasoon 2000 all in one tool kit but can't get it to kick in. and when i go into the cmd command prompt it tells me device error. the phone isn't reading.
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
I am S-ON and was on the JB OTA and was going to relock and run the RUU and get back to stock and take the latest update. I know i should have been S-OFF but was uncomfortable. OK now I am stuck on the white bootloader screen and I cant get into recovery or restart or even power down the phone just restarts. All i did was relocked and now im stuck like this. What do I do next? Run the RUU? I downloaded the RUU 3.15.651.16 - HBOOT 2.09 zip off the DirtyRacun site but it keeps telling me windowns cannot open the folder to let me run it as administrator. Any help would be much appreciated I have done this before and didnt have this problem.
xbmoyx said:
I am S-ON and was on the JB OTA and was going to relock and run the RUU and get back to stock and take the latest update. I know i should have been S-OFF but was uncomfortable. OK now I am stuck on the white bootloader screen and I cant get into recovery or restart or even power down the phone just restarts. All i did was relocked and now im stuck like this. What do I do next? Run the RUU? I downloaded the RUU 3.15.651.16 - HBOOT 2.09 zip off the DirtyRacun site but it keeps telling me windowns cannot open the folder to let me run it as administrator. Any help would be much appreciated I have done this before and didnt have this problem.
Click to expand...
Click to collapse
I am currently downloading the 3.15 RUU and am watching QBKing77's video on unrooting. He runs the RUU with the phone turned on. I cannot turn my phone on can I run this RUU with the phone in bootloader/Fastboot USB?
Steps 6, 7, 8, and 9 on the unlimited Io website have you relock and RUU from fastboot. You can stop there if you don't feel confident going for full s-off. Their Dirty racoon zip for windows has adb and fastboot in it. Just put the RUU.zip in there and run the commands from that directory.
Or wait for someone who knows more than me and be completely sure.
tilltheend714 said:
Steps 6, 7, 8, and 9 on the unlimited Io website have you relock and RUU from fastboot. You can stop there if you don't feel confident going for full s-off. Their Dirty racoon zip for windows has adb and fastboot in it. Just put the RUU.zip in there and run the commands from that directory.
Or wait for someone who knows more than me and be completely sure.
Click to expand...
Click to collapse
OK so I am currently downloading the RUU_PLUS_ROOT.zip from BigDaddy619's sig. Do I open a command prompt in the location of the download and type...
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU.zip
???? Sorry kinda noob at this and havent had this problem before. I am not trying to S-OFF just get back to Jellybean stock to take the latest OTA.
I'm not sure what that zip contains so I can't help with that.
On your first post you said you downloaded the RUU from the dirty racun site. It should be called "RUU.zip". That can be flashed through fastboot with those commands. Do you still have that file?
Edit: And steps 1-9 of the S-off procedure are to get you locked and RUU so you can be completely stock for the procedure. So you can stop there if you don't want to attempt s-off.
tilltheend714 said:
I'm not sure what that zip contains so I can't help with that.
On your first post you said you downloaded the RUU from the dirty racun site. It should be called "RUU.zip". That can be flashed through fastboot with those commands. Do you still have that file?
Edit: And steps 1-9 of the S-off procedure are to get you locked and RUU so you can be completely stock for the procedure. So you can stop there if you don't want to attempt s-off.
Click to expand...
Click to collapse
Yes I still have it on my desktop. It wont let me open it or extract it its a Zip file.
Ok. Leave it as a zip file, confirm that the md5 matches, and put it in your adb, fastboot directory. Since you said you relocked, I think you know where that is. Make sure you're locked, then run those commands one by one. And pay special attention to step 9:
"If you get the following after you run RUU: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" then you need to rerun the fastboot flash zip RUU.zip command again. Press the up arrow and enter."
Especially this part
"you need to rerun the fastboot flash zip RUU.zip command again. Press the up arrow and enter."
tilltheend714 said:
Ok. Leave it as a zip file, confirm that the md5 matches, and put it in your adb, fastboot directory. Since you said you relocked, I think you know where that is. Make sure you're locked, then run those commands one by one. And pay special attention to step 9:
"If you get the following after you run RUU: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" then you need to rerun the fastboot flash zip RUU.zip command again. Press the up arrow and enter."
Especially this part
"you need to rerun the fastboot flash zip RUU.zip command again. Press the up arrow and enter."
Click to expand...
Click to collapse
Got it! Thanks for all your help man.
Sent from my EVO using xda premium
No problem.
Are you back up and running?
tilltheend714 said:
No problem.
Are you back up and running?
Click to expand...
Click to collapse
Yup! I'll stay unrooted until the new update for Viper rolls out, hopefully soon!
Sent from my EVO using xda premium
Can't wait for that update.
If you ever want to s-off and have questions send a pm. It's not as scary as it sounds.
tilltheend714 said:
Can't wait for that update.
If you ever want to s-off and have questions send a pm. It's not as scary as it sounds.
Click to expand...
Click to collapse
It just sucks that the only computer I have is a 64bit windows laptop. All that ubuntu talk confuses the hell outta me. I appreciate it though man ill keep that in mind if I ever want to s-off. :thumbup:
Sent from my EVO using xda premium
I'm still getting data disconnected even on the latest OTA man I was hoping it got fixed. Having to cycle airplane mode to get data to turn back on
I only have 64bit windows. I just used a live disc. Easy as downloading an iso from ubuntus website and burning it to a disc. 10 minutes to get familiar with ubuntu and download the files, and a couple fastboot commands. You were pretty much done with the procedure today . Then just eject the disc and store it for next time you need ubuntu.
Did you try updating prl and profile?
Nope but just did and am on a new PRL. Hopefully this helps.
Sent from my EVO using xda premium
Doesn't matter that the system is 64 bit, just download a 32 bit iso of Ubuntu. It's really not as hard as it seems. I would say it's actually more reliable on Ubuntu then windows
om4 said:
Doesn't matter that the system is 64 bit, just download a 32 bit iso of Ubuntu. It's really not as hard as it seems. I would say it's actually more reliable on Ubuntu then windows
Click to expand...
Click to collapse
Well seeing how long it takes for an update on this phone I may not need to S-OFF. I just flashed the latest OTA so I'm 100% up to date. As long as the S-ON support continues regarding ROMs I should be good. Maybe the next phone ill look into getting S-OFF out the gate.
Sent from my EVO using xda premium
Well its getting to be more of a hassle with each update. The first update disabled flashing kernels and radios, the next update blocked you from writing to the system, this one has an update to the touch panel which breaks more then a few roms. Add to that the hassle of having to flash stock rom/recovery to update firmware or flashing a ruu which can cause more problems then it solves.
om4 said:
Well its getting to be more of a hassle with each update. The first update disabled flashing kernels and radios, the next update blocked you from writing to the system, this one has an update to the touch panel which breaks more then a few roms. Add to that the hassle of having to flash stock rom/recovery to update firmware or flashing a ruu which can cause more problems then it solves.
Click to expand...
Click to collapse
Wow jeez didn't hear about any cons with the latest update. I pray Viper is still going to be OK.
Sent from my EVO using xda premium
I think so far only aosp roms and mean bean (and twrp of course) are affected by the touch panel update
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
[Q] Getting "Error [140]: Bootloader Version Error" when I try to downgrade my HBoot
Okiedoke. So, I've got a little experience with the Evo 3D, but my last one was shoddily done and I don't think I ever even attained S-OFF on it, so when I had to get mine replaced by Sprint, I figured I'd follow a guide and do this thing right.
I first followed the HTC method of unlocking my bootloader and rooting the device, and then installed TWRM. I was using my phone for about a week before I just today decided I had enough time to look at these instructions and follow them. I successfully used this PG86IMG file (from this thread) to brick my device, followed the instructions from the original thread up to 27, and then realized I might have a problem on my hands. I can't boot my phone into the OS anymore (I get a sudden slowdown and then freeze of the boot animation before it restarts itself), but I can still get into the bootloader and Fastboot. So, I figured, why not just run the 1.13 RUU EXE in Fastboot? So I tried, but every time I try to run an RUU EXE (I've tried several, both 1.13 and 2.17 versions), after the RUU pushes the file to the phone and checks signatures I get error 140. I saw that Unknownforce said here that these instructions are "extremely dated" and to use the new ones in his newer thread, but I'm not sure where to pick up.
In short, I would love it if someone could recognize what the next step I need to take is. Ask me for any further information I haven't provided, I'll be more than glad to help you guys help me!
I'm having a similar issue, the only difference between our issues being that I get Error 131: CUSTOMER ID ERROR. Still working on how to fix it.
Macadamia Daze said:
I'm having a similar issue, the only difference between our issues being that I get Error 131: CUSTOMER ID ERROR. Still working on how to fix it.
Click to expand...
Click to collapse
Well this probably won't help with my issue, but this guy seems to have found a solution for yours.
Macadamia Daze said:
I'm having a similar issue, the only difference between our issues being that I get Error 131: CUSTOMER ID ERROR. Still working on how to fix it.
Click to expand...
Click to collapse
Put the PG86IMG(.zip) on the sdcard and boot to bootloader and update that way. The ruu exe checks the Cid, the bootloader flash doesn't.
Sent from my SPH-L720 using xda app-developers app
Unknownforce said:
Put the PG86IMG(.zip) on the sdcard and boot to bootloader and update that way. The ruu exe checks the Cid, the bootloader flash doesn't.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I tried this two different ways:
Got a 1.13 PG86IMG ZIP from Shipped ROMs, renamed to PG86IMG and put on my SD card, but my phone didn't want anything to do with it (it would load and check it, but then kick me back out to the main bootloader screen). Then I downloaded a 1.13 RUU EXE and extracted the "rom" file from it, renamed and slapped on card. Phone loads and checks correctly, but then returns the "Main version is older!" error.
DavisJ3608 said:
I tried this two different ways:
Got a 1.13 PG86IMG ZIP from Shipped ROMs, renamed to PG86IMG and put on my SD card, but my phone didn't want anything to do with it (it would load and check it, but then kick me back out to the main bootloader screen). Then I downloaded a 1.13 RUU EXE and extracted the "rom" file from it, renamed and slapped on card. Phone loads and checks correctly, but then returns the "Main version is older!" error.
Click to expand...
Click to collapse
Then your misc version didn't downgrade as it should have. Go to the main thread and flash the firmware zip file that's listed there, it will put you up to 1.58 hboot, then start that process from scratch.
Unknownforce said:
Then your misc version didn't downgrade as it should have. Go to the main thread and flash the firmware zip file that's listed there, it will put you up to 1.58 hboot, then start that process from scratch.
Click to expand...
Click to collapse
Okiedoke. Just to verify (sorry for being thick), when you say "Main Thread" you're talking about this one, right? I ask because the only firmware I see there is for Virgin, and I'd rather keep Sprint firmware on my phone (unless it really, truly doesn't change anything but the name).
Also, your method requires launching a Linux distro, yes? Is it OK if it's off a live USB, like the Ubuntu installer OS? For some reason I can't get my machine to cooperate when I try to install a permanent Linux OS (something to do with UEFI settings, I think).
DavisJ3608 said:
Okiedoke. Just to verify (sorry for being thick), when you say "Main Thread" you're talking about this one, right? I ask because the only firmware I see there is for Virgin, and I'd rather keep Sprint firmware on my phone (unless it really, truly doesn't change anything but the name).
Also, your method requires launching a Linux distro, yes? Is it OK if it's off a live USB, like the Ubuntu installer OS? For some reason I can't get my machine to cooperate when I try to install a permanent Linux OS (something to do with UEFI settings, I think).
Click to expand...
Click to collapse
That thread yes, but I mean the PG86IMG file from the downgrade section there, use that to update the hboot and firmware, then start that section from scratch.
And yes any linux will work USB or not.
Unknownforce said:
That thread yes, but I mean the PG86IMG file from the downgrade section there, use that to update the hboot and firmware, then start that section from scratch.
And yes any linux will work USB or not.
Click to expand...
Click to collapse
I actually ended up pulling an old laptop out from storage and putting Ubuntu on that so I can have an actual workstation. I ran the PG86IMG you mentioned, which got my phone back up and running with HBOOT 1.58. Then I followed all of your instructions to the letter, down to where you say to run the 1.13 RUU EXE. I tried running that on Ubuntu using WINE, but I kept getting an error. Then I tried running it on Windows 8, but I can't seem to get the EXE to detect my phone is connected. Then I even tried running the RUU in a WinXP virtual machine, but I can't seem to get that to work either. I then tried simply using the 1.13 ZIP as PG86IMG, but I'm getting the same error where after it loads and scans the file, it kicks me out to the main bootloader screen with no warnings or error messages.
At this point, what would be the better option? Should I attempt Revolutionary and get S-Off, then redo the instructions? Or should I do something else? Do I even need to install the 1.13 RUU? I assume I do, because my phone is unusable if I don't...
DavisJ3608 said:
I actually ended up pulling an old laptop out from storage and putting Ubuntu on that so I can have an actual workstation. I ran the PG86IMG you mentioned, which got my phone back up and running with HBOOT 1.58. Then I followed all of your instructions to the letter, down to where you say to run the 1.13 RUU EXE. I tried running that on Ubuntu using WINE, but I kept getting an error. Then I tried running it on Windows 8, but I can't seem to get the EXE to detect my phone is connected. Then I even tried running the RUU in a WinXP virtual machine, but I can't seem to get that to work either. I then tried simply using the 1.13 ZIP as PG86IMG, but I'm getting the same error where after it loads and scans the file, it kicks me out to the main bootloader screen with no warnings or error messages.
At this point, what would be the better option? Should I attempt Revolutionary and get S-Off, then redo the instructions? Or should I do something else? Do I even need to install the 1.13 RUU? I assume I do, because my phone is unusable if I don't...
Click to expand...
Click to collapse
If the bootloader is not saying anything about the zip file it's not a valid signed zip. Find another copy of it or extract it from the ruu exe. Run the exe and open up the temp folder and search for rom.zip then rename to PG86IMG(.zip) and put on sdcard. Then try again. You need special drivers for windows 8, which is why that didn't work, the other two are emulated versions of Windows, and don't have the proprietary drivers to work properly either. So unless you have access to another windows pc that isn't 8, your only option is to get the sdcard the correct file.
Sent from my SPH-L720 using xda app-developers app
DavisJ3608 said:
Well this probably won't help with my issue, but this guy seems to have found a solution for yours.
Click to expand...
Click to collapse
No dice. I can't change my CID without getting an error, presumably because I can't HTCDev unlock (when I get to the final step, I get success on fastboot but never the prompt on the phone).
Unknownforce said:
Put the PG86IMG(.zip) on the sdcard and boot to bootloader and update that way. The ruu exe checks the Cid, the bootloader flash doesn't.
Click to expand...
Click to collapse
Hboot just checked my CID and kicked me out.
Macadamia Daze said:
No dice. I can't change my CID without getting an error, presumably because I can't HTCDev unlock (when I get to the final step, I get success on fastboot but never the prompt on the phone).
Hboot just checked my CID and kicked me out.
Click to expand...
Click to collapse
Uhhh... Pretty sure that is to super cid a gsm phone
I don't think it's meant for CDMA!!
Unknownforce said:
If the bootloader is not saying anything about the zip file it's not a valid signed zip. Find another copy of it or extract it from the ruu exe. Run the exe and open up the temp folder and search for rom.zip then rename to PG86IMG(.zip) and put on sdcard. Then try again. You need special drivers for windows 8, which is why that didn't work, the other two are emulated versions of Windows, and don't have the proprietary drivers to work properly either. So unless you have access to another windows pc that isn't 8, your only option is to get the sdcard the correct file.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Oh my god, I feel like a dumbass for not pulling the rom from the EXE before saying anything o.o
Anywho, I pushed the 1.13 PG86IMG correctly, then ran Revolutionary on Ubuntu, and now my phone's S-Off and 1.40! Thanks so much! Hand to god, when I get paid I'm sending you beer money.
DavisJ3608 said:
Oh my god, I feel like a dumbass for not pulling the rom from the EXE before saying anything o.o
Anywho, I pushed the 1.13 PG86IMG correctly, then ran Revolutionary on Ubuntu, and now my phone's S-Off and 1.40! Thanks so much! Hand to god, when I get paid I'm sending you beer money.
Click to expand...
Click to collapse
Haha, glad it worked :highfive: