Hardware: 003
HBOOT: 2.09.0000
Radio: 1.12.11.1210
ROM: Stock 3.16.651.3
I am having several additional issues other than what is described in the title:
Firstly, I ran ViperRUU 3.16.651.3 to restore my phone to stock. I was S-OFF via DirtyRacun. I toggled the security back on. ViperRUU, however, didn't relock the bootloader, which I found odd. After receiving an update notification, I tried to update the ROM to 3.17.651.4, but it wouldn't update. I acquired "RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.17.651.4_Radio_1.13.11.0830_NV_3.02_003_PRL25007_release_334470_signed.exe" from HTC's website, and tried to run the RUU, but it won't update the phone, citing "Error 155". I tried to run ViperRUU again, and now it won't run RUU in bootloader. ViperRUU claims that the ROM.zip updated, but I saw no progress bar, and the phone is configured the exact same before the RUU.
Any ideas? My goal is to have this phone completely back to stock and OTA updated.
You have to relock for the RUU to run.
Related
Currently I am Hboot 1.5 S-ON and trying to downgrade to HBoot 1.4 S-OFF. When trying to brick my phone on the PG86IMG.zip update it doesn't brick, at least I don't think so. I can enter HBoot, flash a rom, and all that stuff. I believe my problem is because I am presently on RUU 2.17 flashing a 2.17 update and I need to downgrade to RUU 1.13. However, when I try to run RUU 1.13 EXE with a relocked HBoot I get an error message part way through the utility.
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
First of all, do I need to downgrade to RUU 1.13 to brick my phone on the PG86IMG update? And second, if that being so, how do I downgrade?
IXKastling said:
Currently I am Hboot 1.5 S-ON and trying to downgrade to HBoot 1.4 S-OFF. When trying to brick my phone on the PG86IMG.zip update it doesn't brick, at least I don't think so. I can enter HBoot, flash a rom, and all that stuff. I believe my problem is because I am presently on RUU 2.17 flashing a 2.17 update and I need to downgrade to RUU 1.13. However, when I try to run RUU 1.13 EXE with a relocked HBoot I get an error message part way through the utility.
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
First of all, do I need to downgrade to RUU 1.13 to brick my phone on the PG86IMG update? And second, if that being so, how do I downgrade?
Click to expand...
Click to collapse
You need to be relocked/have 2.17 firmware on your phone.
Once you press (UP) to update does your device turn off right away?
I am relocked and have 2.17 firmware. When I press (UP) for the update it updates with a series of purple and black updating sequences. But I am trying to brick it and I can't seem to do so cause I am pulling out the power cord with no battery but I see no dim red light on the top of the phone. Like I said, everything boots as normal and I even can run the 2.17 RUU EXE and boot up that. I saw that the "HBoot downgrade tutorial" said...
If you're already S-OFF, but on 1.50, you can do one of two things... I have attached the PG86IMG.zip with the 1.40 bootloader on it, download it copy to sd card and flash via bootloader.
The other option is to simply re-run 1.13 RUU, this will downgrade it as well, but this will also erase all data in the process.
Now I assume that means if I am 2.17 and S-ON, which I am, I need to downgrade to 1.13 to have the 2.17 PG86IMG.zip update properly so I can pull the plug and brick it. Do I need to do that or am I just needing to repeat the bricking process until it works?
IXKastling said:
Currently I am Hboot 1.5 S-ON and trying to downgrade to HBoot 1.4 S-OFF. When trying to brick my phone on the PG86IMG.zip update it doesn't brick, at least I don't think so. I can enter HBoot, flash a rom, and all that stuff. I believe my problem is because I am presently on RUU 2.17 flashing a 2.17 update and I need to downgrade to RUU 1.13. However, when I try to run RUU 1.13 EXE with a relocked HBoot I get an error message part way through the utility.
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
First of all, do I need to downgrade to RUU 1.13 to brick my phone on the PG86IMG update? And second, if that being so, how do I downgrade?
Click to expand...
Click to collapse
I downgraded yesterday. This is what I did. I downloaded this hbootdowngrade217.zip along with another download zip file that contained the 1.13 ruu and I downloaded a 2.08.zip file as well. I relocked my phone and ran the 2.17 ruu thats in that hbootdowngrade217.zip file. Then I rename the 2.08.zip file to PG86IMG.zip onto the root on my sd card. Booted into bootloader let it read the file. Once it read n I had to update. I plugged in the charger from the laptop to the phone then took the battery out. let it sit for a min then hit up on sp it can begin the update n right after it said UNZIPPING n said Updating I counted to 5 n took the charger out on 5. If u did this before it went to the next step you have bricked your device correctly. You can check this by going into the control panel>view devices<manage devices n u put the battery back in hold down the down volume button then plug your phone back up n u will see something saying: Qualcomm MMC Storage but it should change to QSUSB_ (something) that means have bricked it correctly. If u didnt then its gone read unknown device. Just continue trying to brick it. Hope this works for you.
I have read pages and pages from the Android Development forum for the HTC Evo 4G LTE and I can't seem to find a solution that works for me because going S-OFF or re-locking bootloader and loading RUU does not seem feasible for my situation.
The phone has custom recovery (TWRP) and we successfully loaded Viperboy's deodexed 3.15 stock ROM.
Baseband is 1.02.12.0427 (super outdated)
This phone was bought second hand and is a HTC dev unlocked phone, S-ON
I would like to update the baseband to 1.12.11.1200 and update the firmware to 3.16
Caveats: I don't have access to the phone, my friend can reload custom ROMs through TWRP, but beyond that I don't think we can go through Dirty Racun and S-Off, I don't know how we can easily check the HBOOT version to determine if the HBOOT version is 1.12
What would happen if we accepted the Sprint OTA? Are we SOL with the baseband because we are S-ON?
Is there any way we can get on MeanBean 3 or stock rooted 3.16?
Any advise would be greatly appreciated.
I wouldnt accept the OTA update to 3.16
I actually did just that when I relocked my phone on Saturday and had all sort of problems after that. Now, I'm not too sure you would even be able to install the update being that your phone is unlocked *citation needed*.
http://forum.xda-developers.com/showthread.php?t=2135670 - talks about the 3.16 OTA problems
thanks, I've definitely advised my friend to stay away from the OTA and disregard it. I think we are experiencing call/wifi issues due to the old baseband. I wonder what are the next possible steps to move forward from here...
BaconMunch said:
thanks, I've definitely advised my friend to stay away from the OTA and disregard it. I think we are experiencing call/wifi issues due to the old baseband. I wonder what are the next possible steps to move forward from here...
Click to expand...
Click to collapse
1. Stay on this baseband and deal with it.
2. Relock and RUU your way up to 3.15 (stay away from 3.16)
3. S-off and Flash a couple full firmware zips.
Sadly I think those are your only option. And to check your hboot just boot into bootloader. Hold volume down when powering on.
tilltheend714 said:
1. Stay on this baseband and deal with it.
2. Relock and RUU your way up to 3.15 (stay away from 3.16)
3. S-off and Flash a couple full firmware zips.
Sadly I think those are your only option. And to check your hboot just boot into bootloader. Hold volume down when powering on.
Click to expand...
Click to collapse
Thanks, I think that seems realistic, I'm concerned that if I relock through HTCDev, I read that some email/password might go to the original seller of the phone (ebay) for confirmation code, so I don't want to get stuck halfway
I am definitely crossing my fingers for HBoot v1.12, to confirm, once I check my version in the bootloader, I guess I can escape without taking any of the menu options (checking YouTube, I'll just go to recovery, enter TWRP, reboot, system).
BaconMunch said:
Thanks, I think that seems realistic, I'm concerned that if I relock through HTCDev, I read that some email/password might go to the original seller of the phone (ebay) for confirmation code, so I don't want to get stuck halfway
I am definitely crossing my fingers for HBoot v1.12, to confirm, once I check my version in the bootloader, I guess I can escape without taking any of the menu options (checking YouTube, I'll just go to recovery, enter TWRP, reboot, system).
Click to expand...
Click to collapse
Relocking the phone is done through fastboot on the computer. Nothing to do with HTC. And Dev unlocked means you get an unlock token from HTC to the email that you signed up with. So if you make your own account on HTC dev and request a token, it should send nothing to the other owner.
And sorry, but I don't understand what you mean by having Hboot 1.12. You mean only flashing the radio through recovery? If that's what you mean than I can't help with that. Not sure how that works or if there are problems with that.
great news! I had someone take screen shots of the HBoot (v.1.12.0000) and TWRP (v2.2.1) menu
Bootloader shows:
Code:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMM-boot
So as far as I know, I'm going to make sure there's nothing wrong with the TAMPERED, and then I can flash 1.12.11.1210 through Captain_Throwbacks Radio Only zip and then looks for a 3.16 custom firmware compatible with S-On since I'm on build number 3.15.651.16 CL124461.
I'd appreciate anyone to chime in if I'm going down a bad path here. Cheers!
BaconMunch said:
great news! I had someone take screen shots of the HBoot (v.1.12.0000) and TWRP (v2.2.1) menu
Bootloader shows:
Code:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMM-boot
So as far as I know, I'm going to make sure there's nothing wrong with the TAMPERED, and then I can flash 1.12.11.1210 through Captain_Throwbacks Radio Only zip and then looks for a 3.16 custom firmware compatible with S-On since I'm on build number 3.15.651.16 CL124461.
I'd appreciate anyone to chime in if I'm going down a bad path here. Cheers!
Click to expand...
Click to collapse
You've indeed unlocked the bootloader properly but this only let's you flash recoveries and custom roms. You have to S-OFF the phone to update firmware via bootloader. You're other option would be to RUU which would upgrade the firmware and software and that CAN be done with S-ON, however there is a problem with the update which disables touch input so you should either wait for a dev to make custom 3.16 rom and forget about the firmware OR wait for a fix from HTC and run that RUU whenever it comes out.
xlxcrossing said:
You've indeed unlocked the bootloader properly but this only let's you flash recoveries and custom roms. You have to S-OFF the phone to update firmware via bootloader. You're other option would be to RUU which would upgrade the firmware and software and that CAN be done with S-ON, however there is a problem with the update which disables touch input so you should either wait for a dev to make custom 3.16 rom and forget about the firmware OR wait for a fix from HTC and run that RUU whenever it comes out.
Click to expand...
Click to collapse
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
BaconMunch said:
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
Click to expand...
Click to collapse
My advice is get s-off it will save alot of headaches down the road
Sent from my PoS MoPho
BaconMunch said:
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
Click to expand...
Click to collapse
Sent you a PM
The advice is free....the bandwidth, not so much
Just wanted to say thank you all for the support and advice.
I finally walked my friend over gtalk and successfully achieved S-OFF after relock, 1.15 RUU, unlock with HTC DEV, dirtyracun
Then updated full firmwares incrementally to 3.16
Then while trying to load MeanBean, realized we lost TWRP (and possibly root, need to confirm), I can only guess that went away with the RUU? That's not really documented anywhere unless that's a known thing.
TWRP installation via goomanager failed (maybe due to lack of root), I was able to find TWRP v2.3.1 bootloader, installed that and installed MeanBean 3.0.4
I think that makes us up to date, however we will likely install SuperSU via TWRP once we customize and ensure the phone is running smoothly.
Thanks again all!
Super su is included with the ROM
Sent from my EVO using xda premium
I updated my phone using the latest 4.03.605.2 and the latest firmware.zip (am S-ON). Now I got my replacement phone, and got it all set up and working fine. Now I can't seem to get the original phone (has a bad touch screen) to restore... every time I try to run the RUU (PH98IMP.zip, 4.03.605.2), it says bad mainver, which I found a mainvir patch and flashed it.
Now it says the HBOOT is newer and won't flash. My HBOOT is on 2.28. The 4.03.605.2 apparently is 2.27, and the latest firmware zip I flashed updated it.
I have both zips still... obviously firmware.zip doesn't include the whole OS... is there a 4.03.605.2 ruu with the updated 2.28 and 2.23 radios already in it?
Help?
Thanks!
Apparently the firmware.zip file was from the global .14 update. Am I stuck until an RUU is released?
Phew... took me a couple hours but got a rom running again, tracked down a download of the s-off windows files, went s-off, ruu'ed, then s-on.
Stock-Rooted 4.05.605.14 rom, loadable from recovery (post #3): http://forum.xda-developers.com/showthread.php?t=2288479
Windows S-Off files (post 361): http://forum.xda-developers.com/showthread.php?p=40950251#post40950251
Followed this guide to reset my locked flag (since I unlocked after going S-Off /facepalm): http://androidforums.com/rezound-all-things-root/659453-how-reset-your-lock-status-flag.html
Then followed this guide to go back to S-ON (after running the RUU): http://androidforums.com/rezound-al...-off-guide-info-return-stock.html#post4394129
Result: Fully stock, locked, and S-ON, to send back to VZW
Hello, I need help getting the right RUU to restore my HTC Evo 3D back to stock ROM.
I read this page but found it confusing and didn't find the stuff that my commands gave me
http://forum.xda-developers.com/showthread.php?t=1672425
My CID: SPCS_002
My version-main: 2.95.652.5
Hope to get some help here!
I too need this! I am bricked.
Same here!
CID: SPCS_002
Version: 1.14.652.0
I just need one corresponding to the CID because basically any RUU I try shoots me an error saying "invalid CID". Please and thank you for any help!
There is only one ruu available for the Virgin Mobile Evo V and it can be found here: http://goo.im/stock/shooter/ruu
If you are s-off, you can run it any time.
If s-on...
If you took the march ota you can run it as long as beforehand you flash the SetMainVersionLow.zip in recovery.
http://db.tt/JUdxrcC0
If you took the November ota which updated you to hboot 1.58, then unfortunately you cannot run the ruu.
Once again if s-off you can run no matter what without problems. But for s-on you either have to change your main version or on the latest ota you are left without an ruu
I upgrade to latest firmware and hboot for the international 4.2.2 ROM. Everything works fine.
Now, the OTA arrived and in order to apply OTA for enabling new LTE band, I need to go back to stock. So, i download the stock ROM and flash. After boot up, touch screen doesn't work.
I tried to revert it back to 1.4.4 hboot/firmware (not AT&T i think). Still doesn't work. Anyone know where I can get the stock firmware and applied? Try to avoid the full RUU if possible.
Thanks.
I haven't seen anyone post a AT&T firmware flashable zip. Most likely they stayed on stock firmware that came with the phone, like me, or they updated to 2.24 firmware.
RUU might be your only choice. But in order to RUU, you need the 1.44 HBOOT. If you're S-OFF, flash the 1.44 HBOOT first then run the RUU. If you're S-ON, you're stuck. RUU won't run because it can't bypass the security check of S-ON.
cee43ja1 said:
I haven't seen anyone post a AT&T firmware flashable zip. Most likely they stayed on stock firmware that came with the phone, like me, or they updated to 2.24 firmware.
RUU might be your only choice. But in order to RUU, you need the 1.44 HBOOT. If you're S-OFF, flash the 1.44 HBOOT first then run the RUU. If you're S-ON, you're stuck. RUU won't run because it can't bypass the security check of S-ON.
Click to expand...
Click to collapse
You are right. I have to use RUU to roll back to stock. At least, I got S-OFF to get back. Now, when checking update, didn't give me anything yet.