OK so I've tried googling and all that but this problem doesn't seem to be as common as the mainver is older issue.
Background:
Just sold the phone on swappa but I need to return to stock before I send it, hopefully tomorrow. I was s on running neo 1.7 before I got into this mess.
Issue:
I booted into recovery and did a factory reset. I then booted into hboot and did a factory reset there also. I think I then selected the wipe internal storage option. I then proceeded to relock the bootloader which I believe was successful since it says relocked now.
I have downloaded and tried flashing 3 different ICS RUUs by renaming them to the appropriate phxxx name and flashing them in hboot. It goes thru the process a little ways and then all of a sudden I get the "hboot is older" error and "update failed" message. My Hboot version is showing 2.27 which i believe is the newest one. I can't do anything and can't find a solution. I really need to figure out how to fix this asap so I can get the buyer his phone. All help is greatly appreciated!
It is impossible to downgrade HBoot without S-Off, so you will only be able to run an RUU with HBoot version 2.27 or higher (I believe that's either the ICS OTA or the Global leak - correct me if I'm wrong).
To get completely stock, i.e., stock firmware and Locked (as opposed to Relocked), you will need to get S-Off, then flash whatever RUU you want, then get S-On again.
However, just flashing any RUU - either the ICS OTA or the Global leak, and staying Relocked should be fine - many people receive used phones with custom ROMs and all, so an RUU would be a big step up from that (in terms of being as stock as possible).
EDIT: as LOBBS said (below), you will need to run the Global Leak RUU. That will get you on the latest leaked firmware / radios, which is probably the best anyway if you are selling the phone to the 'average', uninformed user (or to the informed user, for that matter). You will have Relocked bootloader.
Alternatively, you could get S-Off and then get on stock firmware / radios, Locked bootloader, and back to S-On, but I assume you won't want to bother to do all that just to sell the phone.
Hboot 2.27 is the global leak RUU 4.03.605.
Sent from my ADR6425LVW using xda app-developers app
Thanks fellas. I will try that one. I thought I had already but maybe I haven't. Let ya know what happens!
I flashed the global leak and all went well. Thanks for the quick help!
I saw CyanogenMod10 with JellyBean for Evo3D phones on here, so I decided to give it a try since ICS is running like crap on my phone, only problem is I can't get past the boot animation. This was on Hboot 1.58, so I read around and most people said you have to downgrade to 1.4 or an Engineering version for it to work. Another said you have to completely unroot and re-root, which I tried with no success.
Well I was successful in the temp brick + linux live cd downgrade, I am now running Hboot 1.40. The problem is with the 1.13 RUU not wanting to install, it gives me a bootloader version error after a few minutes of attempting to update the phone. ICS not surprisingly boot loops or freezes on boot animation.
I did read somewhere that bricking the phone twice works, though I don't quite understand how. If someone can confirm it does work I'm willing to do it.
Here's the guide I was following:
http://forum.xda-developers.com/showthread.php?t=1563342
And I'm currently stuck on:
28. Now. Reboot into Windows and run the 1.13 RUU EXE that you downloaded.
Another question I just thought of, do I even need to flash 1.13? Would I be able to just flash the jellybean rom onto the phone now?
Thanks!
Nevermind, I got it working!
Did the brick twice in a row and was able to then update to the 1.13 RUU.
Hi everyone,
I used RegawMod to unlock the bootloader, get root, and installed TWRP flash recovery. Phone is "S-ON". The phone was having issues with repeated SMS and I couldn't take the OTA. So I was told to relock the bootloader and install stock RUU file.
Ok so I did just that, relocked bootloader and then went to reinstall the RUU. When I went to download the RUU's I saw that the latest version was:
"RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe"
I figured it would be ok to flash this and this would give me Jelly Bean all in one shot. My phone was running the stock rom which was software version "1.13.651.1"
So I installed the RUU and everything seemed to work properly until the phone rebooted. I noticed that none of the settings had been reset and the email account was still there etc. Typically when you flash an RUU everything goes back to configure mode on reboot. So I went into the settings software version etc and sure enough the software was the old software.
Looks like the RUU only changed my boot loader! When I checked originally I had bootloader 1.12.0000 after flashing the latest RUU file my bootloader was now 2.09.0000.
I then downloaded the "1.13.651.1" RUU to try and install it but it said not compatible with the bootloader.
Any advice on why the rom didn't update? What can I do now?
http://forum.xda-developers.com/showthread.php?p=36308826#post36308826
Welcome to the machine, where have you been? It's alright, we know where you've been.
Got a pretty lengthy thread, it seems the more people that run the new RUU are having the same exact issue. My radio is stuck on 1.05 and hboot 2.09 after running that thing. Should have known not to trust anything stock. Always thought those RUUs were safe.
Anyways, a bunch of us are subscribed to the thread I posted at the top of this post, I recommend you subscribe to it to keep things clean.
Hey everyone. I've been on Neo's Infection 2.4. Wanted to try out Eclipze rom so I relocked bootloader, grabbed the latest ruu I could find, renamed it to whatever it was (PH98 something or other) and put that on my sd card. I rebooted into fastboot and it goes through the process of updating but then I get the error message. At the top of the fastboot screen it says hboot: 2.28. Is there another ruu somewhere that I don't know about. I'm downloaded a 4.03 ruu, is there a newer one I don't know about or am I pretty well screwed?
flybub said:
Hey everyone. I've been on Neo's Infection 2.4. Wanted to try out Eclipze rom so I relocked bootloader, grabbed the latest ruu I could find, renamed it to whatever it was (PH98 something or other) and put that on my sd card. I rebooted into fastboot and it goes through the process of updating but then I get the error message. At the top of the fastboot screen it says hboot: 2.28. Is there another ruu somewhere that I don't know about. I'm downloaded a 4.03 ruu, is there a newer one I don't know about or am I pretty well screwed?
Click to expand...
Click to collapse
Hem... that's the current bootloader. Are you s-on or off ?
dottat said:
Hem... that's the current bootloader. Are you s-on or off ?
Click to expand...
Click to collapse
I'm S-On. I downloaded the PH98 file again thinking maybe it was bad, but no dice. I get the same error message. I can't get anything to boot. I was able to flash a recovery so I flashed Infection 2.5 but I keep getting stuck at the Android looking screen (yes boot.img was flashed in fastboot). I flashed a couple different ICS roms but none of them boot up. I figured if I could get back to stock I would just go s-off and be done with it but I think this phone is done.
Edit: Gave the phone to a friend of mine who is much better at this stuff than I am. Maybe he can figure it out. Thanks for the help
Hm, if you flashed the kernel you should be able to boot up.
If you're s-on and on hboot 2.28 there's no RUU as of yet you can run. There's a stock OTA ROM of the lates OTA in the dev section you can run that and see if that helps. You probably can s-off on that but don't take my word for it, especially since you're on 2.28 hboot.
I would make a nandroid before so you can always get back to that if needed.
If you really want to run an RUU you need to s-off, but confirm that it's still going to work on the latest OTA before trying it.
Hey all,
So I'm sending my Rezound back to Verizon as a warranty replacement, and today I tried to revert it to stock. It was rooted, S-OFF, with Infected ROM installed (based off CM10.1.2). However, the re-lock process didn't work correctly. I received the below error in the command prompt when I tried to relock it with fastboot oem lock:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
The steps I took are as follows:
1) Re-installed RUU using this file: Rezound_Global_ICS_4.03.605.2_Full_RUU_PH98IMG (renamed to PH98IMG and done through bootloader)
2) Attempted fastboot oem lock (and got the above error)
This process worked on a different Rezound that I also received as a warranty replacement which itself was also defective, but in that case I locked the phone first and THEN flashed the RUU. In my haste today I accidentally flipped the order to what you see above.
Now, the phone will not go back to ***LOCKED*** up at the top. Instead, it says ***RELOCKED*** which is not what I want here. I am afraid to set the S-OFF flag back to ON while the phone is displaying "relocked". The RUU did work, as the phone has stock firmware on it once again and boots up fine. I attempted to relock it again and RUU it again with the same results, still got the above error and still showing ***RELOCKED***.
I did some research but couldn't find anything specific to the Rezound; the nearest thing I was able to find was some info about how CleanROM can cause this on a different device, and something about mainver, which I'm not familiar with. I did use CleanROM for nearly a year before going S-OFF and moving to CM10. If anyone has an idea on how to fix it I would be eternally grateful.
tigerxchaos said:
Hey all,
So I'm sending my Rezound back to Verizon as a warranty replacement, and today I tried to revert it to stock. It was rooted, S-OFF, with Infected ROM installed (based off CM10.1.2). However, the re-lock process didn't work correctly. I received the below error in the command prompt when I tried to relock it with fastboot oem lock:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
The steps I took are as follows:
1) Re-installed RUU using this file: Rezound_Global_ICS_4.03.605.2_Full_RUU_PH98IMG (renamed to PH98IMG and done through bootloader)
2) Attempted fastboot oem lock (and got the above error)
This process worked on a different Rezound that I also received as a warranty replacement which itself was also defective, but in that case I locked the phone first and THEN flashed the RUU. In my haste today I accidentally flipped the order to what you see above.
Now, the phone will not go back to ***LOCKED*** up at the top. Instead, it says ***RELOCKED*** which is not what I want here. I am afraid to set the S-OFF flag back to ON while the phone is displaying "relocked". The RUU did work, as the phone has stock firmware on it once again and boots up fine. I attempted to relock it again and RUU it again with the same results, still got the above error and still showing ***RELOCKED***.
I did some research but couldn't find anything specific to the Rezound; the nearest thing I was able to find was some info about how CleanROM can cause this on a different device, and something about mainver, which I'm not familiar with. I did use CleanROM for nearly a year before going S-OFF and moving to CM10. If anyone has an idea on how to fix it I would be eternally grateful.
Click to expand...
Click to collapse
You need to get ahold of either the ph98img.zip for 3.14.605.12 like HERE and put it on your sd card and run that at hboot after renaming it ph98img.zip or get a copy of the full RUU (RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe) for 3.14.605.12 at ONE OF THESE LINKS and run this on your pc with the phone connected by the USB cable. Make sure on the exe version that you have USB debugging enabled. The RUU you used is a leak and not an "official" full RUU. You need to run a full official RUU to accomplish what you want and the full RUU for 4.05.605.14 has not been released yet. If you use either of the ones I provided links for, the hboot will show "locked" but an earlier version. Then if you want it to show the latest version, leave your SIM card in the phone, let it bootup, when the setup starts, just press the home key and it will bypass setup. The get into settings and into the software update and run that. It will update to the next version. Let it reboot and again bypassing the setup. Then run software update one more time and you will have 4.05.605.14 which is the latest version and your hboot will now show locked. Now you can go ahead and re S-on the phone.
However, I have heard over and over that Verizon never checks the software on the phones and you could just send it back the way it is now. But I'm sure that you are paranoid about this like I am and want it fully stock again so there are no red flags...
mikeyk101 said:
You need to get ahold of either the ph98img.zip for 3.14.605.12 like HERE and put it on your sd card and run that at hboot after renaming it ph98img.zip or get a copy of the full RUU (RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe) for 3.14.605.12 at ONE OF THESE LINKS and run this on your pc with the phone connected by the USB cable. Make sure on the exe version that you have USB debugging enabled. The RUU you used is a leak and not an "official" full RUU. You need to run a full official RUU to accomplish what you want and the full RUU for 4.05.605.14 has not been released yet. If you use either of the ones I provided links for, the hboot will show "locked" but an earlier version. Then if you want it to show the latest version, leave your SIM card in the phone, let it bootup, when the setup starts, just press the home key and it will bypass setup. The get into settings and into the software update and run that. It will update to the next version. Let it reboot and again bypassing the setup. Then run software update one more time and you will have 4.05.605.14 which is the latest version and your hboot will now show locked. Now you can go ahead and re S-on the phone.
However, I have heard over and over that Verizon never checks the software on the phones and you could just send it back the way it is now. But I'm sure that you are paranoid about this like I am and want it fully stock again so there are no red flags...
Click to expand...
Click to collapse
Thanks very much for the suggestion. I'll give this a try shortly.
It's just weird that this RUU successfully took another phone back to fully stock. The only difference between the two is that the other phone never had CleanROM installed on it.
EDIT: Just realized one other thing, at one point I manually updated the radios on the first phone (the one that is now giving me trouble) but didn't do this on the one that went back to stock properly. I'm going to give the PC method a try since it mentions the radios in the file name.
Sent from my SCH-I535 using xda app-developers app
Went ahead and ran the full RUU from my PC as suggested above. Unfortunately it didn't accomplish the goal. The RUU completed successfully, but HBOOT still says ***RELOCKED***. I tried unlocking and then relocking again, and got the same error:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 0.958s
Not sure where to go from here.
With S-off, the radios shouldnt matter. Seems to me when I s-offed this latest phone, it was on 4.05.605.14 and I had to unlock the bootloader to do the s-off. After I achieved s-off, I dont remember relocking, I just ran that ph98img from android police. The bootloader then displayed that it was locked. Maybe try to run either of those RUUs after unlocking the bootloader.
mikeyk101 said:
With S-off, the radios shouldnt matter. Seems to me when I s-offed this latest phone, it was on 4.05.605.14 and I had to unlock the bootloader to do the s-off. After I achieved s-off, I dont remember relocking, I just ran that ph98img from android police. The bootloader then displayed that it was locked. Maybe try to run either of those RUUs after unlocking the bootloader.
Click to expand...
Click to collapse
I think the key is this error I'm getting via the command line. I didn't get it with the other phone and on that one, after I relocked, it said **TAMPERED** across the top; after the RUU, it just said **LOCKED**. This one is saying **RELOCKED** instead of **TAMPERED** and it's the one that won't go back to locked after a RUU. If we can figure out what's causing this error, might be the key to solving the issue. However, that's where I'm falling short in my research.
tigerxchaos said:
I think the key is this error I'm getting via the command line. I didn't get it with the other phone and on that one, after I relocked, it said **TAMPERED** across the top; after the RUU, it just said **LOCKED**. This one is saying **RELOCKED** instead of **TAMPERED** and it's the one that won't go back to locked after a RUU. If we can figure out what's causing this error, might be the key to solving the issue. However, that's where I'm falling short in my research.
Click to expand...
Click to collapse
IIRC, when it says Tampered across the top of the bootloader, it just means that the bootloader is unlocked and that a other than factory recovery has been installed such as TWRP or AmonRa. Relocked means that the bootloader had originally been unlocked at some point and then locked again. If it were me, I would
1. Try to unlock the bootloader again,
2. Reinstall either AmonRa or TWRP if either is not there, then
3. Wipe everything such as cache, dalvik cache, wipe ALL data/factory reset, and possibly even wipe system.
(Normally you would not want to wipe system because pretty much everything is then gone but since you have the RUU.exe, you have the means to reinstall the original OS.)
4. After wiping everything above, reboot from recovery to bootloader and try running that RUU again.
You are right though and this is weird. Normally when you run a full factory RUU, it should reset EVERYTHING back to factory original condition.
BTW, I have just been trying to come up with a workable solution. I was kind of hoping that someone with more experience would pipe in. Unfortunately it looks like the Rezound and development is dying a slow but sure death and many have moved on...
Just trying to think of alternate solutions again, I know that it is possible to change just the hboots by using the proper ph98img.zip files. I remember using one awhile back when I was unlocked that changed the hboot from tampered to read locked. I cant find the thread but I think it came from Vinylfreak . I attached it in this post but it will read 2.27.0000 as the version. I have also included the factory 2.28.0000 in a separate ph98img file below. Maybe try one of these and it might take care of it. Put these on your sd card, change the name of the first one to ph98img.zip and get into the bootloader hboot and let it update. If that doesn't work, try the second one.
If needed, I could also probably make one for the 3.05.605.12 and upload that as well. I just need to check the hboot version it came with.
ETA, I think the first one came from THIS THREAD and it is just renamed by me so I could keep track of what it was...
mikeyk101 said:
Just trying to think of alternate solutions again, I know that it is possible to change just the hboots by using the proper ph98img.zip files. I remember using one awhile back when I was unlocked that changed the hboot from tampered to read locked. I cant find the thread but I think it came from Vinylfreak . I attached it in this post but it will read 2.27.0000 as the version. I have also included the factory 2.28.0000 in a separate ph98img file below. Maybe try one of these and it might take care of it. Put these on your sd card, change the name of the first one to ph98img.zip and get into the bootloader hboot and let it update. If that doesn't work, try the second one.
If needed, I could also probably make one for the 3.05.605.12 and upload that as well. I just need to check the hboot version it came with.
ETA, I think the first one came from THIS THREAD and it is just renamed by me so I could keep track of what it was...
Click to expand...
Click to collapse
Thanks again for all your suggestions, you've been REALLY helpful.
I'll try out the hboot method you listed above and see what I can come up with. My concern there is that I think vinylfreak's hboot was an engineering hboot, which will brick the phone if I try to go back to S-ON with it installed.
Rezound development is actually still alive and well, among several dedicated developers who are working on some great software for the phone. @Flyhalf205 has been releasing regular updates to his Rezound build of CyanogenMod 10.1 and as I understand it, is responsible for a ton of the recent progress made on bringing Jellybean to the Rezound. @IAmTheOneTheyCallNeo has a fantastic ROM based off of CM called Infection, and a variant of it based on PACMan called Tron. @iHateWebOS has a great kernel called HIRO, @Snuzzo has another one called Funky Kernel, and there are other devs that I'm less familiar with working on other projects. Check out their work, it breathed new life into my phone.
tigerxchaos said:
Thanks again for all your suggestions, you've been REALLY helpful.
I'll try out the hboot method you listed above and see what I can come up with. My concern there is that I think vinylfreak's hboot was an engineering hboot, which will brick the phone if I try to go back to S-ON with it installed.
Rezound development is actually still alive and well, among several dedicated developers who are working on some great software for the phone. @Flyhalf205 has been releasing regular updates to his Rezound build of CyanogenMod 10.1 and as I understand it, is responsible for a ton of the recent progress made on bringing Jellybean to the Rezound. @IAmTheOneTheyCallNeo has a fantastic ROM based off of CM called Infection, and a variant of it based on PACMan called Tron. @iHateWebOS has a great kernel called HIRO, @Snuzzo has another one called Funky Kernel, and there are other devs that I'm less familiar with working on other projects. Check out their work, it breathed new life into my phone.
Click to expand...
Click to collapse
I didn't quite elaborate on what I was thinking. But you are absolutely correct about doing S-on with an engineered hboot and that it would brick it. However, since it is going back as a warranty replacement, maybe bricking it might not be such a bad idea. LOL. I should have added that by using the fake locked hboot, it may trick the phone into thinking it really was locked. And then flash the second one and the banner just might stay showing locked. I have actually gone back and forth between the two but have always been locked so I am not sure how yours would work out. BTW, that second one is the original factory hboot extracted off the full OTApkg.zip for 4.05.605.14 and packaged in a ph98img file. I extracted it in the event that I might have to S-on again sometime in the future. I also extracted the original factory recovery and packaged that in a ph98img file as well in case I ever had to revert back to stock for the same reason. I just have to unroot (I am using supersu), reinstall the factory recovery, reinstall the factory hboot, do a factory wipe in recovery and finally do the write secure flag command and I am golden. I know that there are still many very cool roms out there. I used to be a big fan of CleanROM but that is no longer supported by the developer. Since then I have gotten kind of used to using a rooted stock rom. I know I may be missing some bells and whistles but I mostly rooted and S-offed just because I could and have a few more choices available to me. I hope you are able to find a solution.
I had this happen a wile ago what worked for me was that I ran the ruu to back to stock, then go through the unlock process, once unlocked s-off. Once s-off run ruu, then follow directions in this link http://forum.xda-developers.com/showthread.php?t=1612937
Sent from my Infected Rezound using xda app-developers app