Hi Xda people
Hey for people having troubles after running the latest global ruu.
1- Make sure to flash the ruu twice. After is done flashing and it says update complete just reboot to hboot and run the ruu again that way everything is truly wiped and everything is truly flashed/installed the way it is.
2- Make sure after you run the ruu twice make a factory reset from hboot BEFORE THE PHONE FIRST BOOT. after the 2 flashes if the phone reboots automatically just pull the battery and reboot to hboot and do a factory reset.
Doing this two steps will avoid a LOT OF TROUBLES.
Enjoy
Unfortunately I read this too late. I just did the RUU today after a borked mod on the last leaked ICS before the OTA came out. Anyway, ran the RUU and then when trying to unlock everything was fine, but after rebooting into Hboot, it still said locked, and then I had all sorts of trouble getting into the hboot itself. Trying to get amon ra on there again was a PIA. All is fine now and factory restore went ok. But man, what a PIA.
Related
I have a new HTC Evo LTE and HBOOT 1.15.000 Radio 1.05.11.0606and do not have S-OFF.
I installed Fresh 5.2.1 and had problems, when back and did a wipe including system and installed 5.2.1 again and it didn't work. After doing that I went back, wiped system again, and then restored the backup I previously made. Now the backup sometimes loads, sometimes doesn't, but even when it does I have no radio. I am going to try to install a stock rom through recovery or fresh 5.1.1 and HOPE I get radio back.
Any other suggestions of what I could do?
jeggen said:
I have a new HTC Evo LTE and HBOOT 1.15.000 Radio 1.05.11.0606and do not have S-OFF.
I installed Fresh 5.2.1 and had problems, when back and did a wipe including system and installed 5.2.1 again and it didn't work. After doing that I went back, wiped system again, and then restored the backup I previously made. Now the backup sometimes loads, sometimes doesn't, but even when it does I have no radio. I am going to try to install a stock rom through recovery or fresh 5.1.1 and HOPE I get radio back.
Any other suggestions of what I could do?
Click to expand...
Click to collapse
So now I'm just in a boot loop. I relocked, installed stock recovery and ran RUU. When I did that I booted just long enough that I could almost slide the ring to unlock before I rebooted. Then the device just constantly reboots.
I unlocked again, installed TWRP 2.2.2.0 in case there was a bug causing flashing issues. Recovery boots just fine now. I flashed Stock Rooted DeOdexed 1.22.651.3 from here since that was the version I had before this whole fiasco. I'm going to try to restore backup again but don't know how to get out of this horrible mess. Worse part about it is that it's my wife's phone! Help please!
You might need to run a different RUU. I'm not too experienced with that kind of issue though.
"We're coming from a pure power source"
metalfan78 said:
You might need to run a different RUU. I'm not too experienced with that kind of issue though.
"We're coming from a pure power source"
Click to expand...
Click to collapse
I reflashed stock recovery, relocked bootloader (fastboot oem lock), ran RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.22.651.3_Radio_1. 05.11.0606_NV_SPCS_2.45_003_release_268323_signed. exe), and still had the boot loop problem. RUU said it completed but the bootloader still said "relocked". Isn't RUU supposed to totally wipe and restore the entire device?
I recall on my old EVO there was a zip you could place in the SDcard that the bootloader automatically looked for and would use to reflash to factory everything. Is there a way to do this with the EVO 4g LTE?
Is it possible that radios/firmware somehow got borked even though I am on S-ON? Is there a way to reflash them from bootloader?
Just thinking through ideas I'd try next and something that could possibly help recover or at least put me in a position to go back to Sprint for help.
Could have been a bad download. I think there is info on re locking in the development sticky section. It might give you some more information on what to do next.
"We're coming from a pure power source"
Just an update. Flashed again a stock ROM and installed the boot.img from stock using fastboot to be sure it was in place. (fastboot flash boot boot.img). That didn't work, still had boot loop where the phone loads enough to show the background and then restarts.
Used the PJ75IMG.zip file and attempted to install automatically in bootloader (from here) <-- Didn't install says "Main Version is older! Update Fail!
I then installed stock recovery and locked bootloader. Bootloader now shows "*** TAMPERED*** and *** RELOCKED***.
Ran RUU <-- Have a hard time doing anything since it doesn't boot up long enough to connect. Eventually RUU will fail with a connection error. I haven't been able to run RUU from HBOOT either and without the device stable long enough I'm not sure how to get RUU to run on the phone.
Still only boot far enough to see the background screen (wallpaper) and then reboot.
I'll gladly give $20 to anyone who offers a workable solution, paid either to you, or dev/charity of your choice if you don't want it.
This all started when I installed Fresh 5.2.1. Not sure if it was the fresh install or using TWRP to wipe data/cache and I also wiped system. Was that a mistake?
I just don't understand why I can't flash back even to stock. Since I'm relocked and never had S-OFF I don't understand how I was able to do something that can't be undone by flashing. I've flashed phones dozens of times so am comfortable with the process and just can't understand what went wrong and how to recover.
Is there an updated version of the PJ75IMG.zip file I could use?
Would it work to flash CM10 & the boot.img using fastboot?
jeggen said:
Just an update. Flashed again a stock ROM and installed the boot.img from stock using fastboot to be sure it was in place. (fastboot flash boot boot.img). That didn't work, still had boot loop where the phone loads enough to show the background and then restarts.
Used the PJ75IMG.zip file and attempted to install automatically in bootloader (from here) <-- Didn't install says "Main Version is older! Update Fail!
I then installed stock recovery and locked bootloader. Bootloader now shows "*** TAMPERED*** and *** RELOCKED***.
Ran RUU <-- Have a hard time doing anything since it doesn't boot up long enough to connect. Eventually RUU will fail with a connection error. I haven't been able to run RUU from HBOOT either and without the device stable long enough I'm not sure how to get RUU to run on the phone.
Still only boot far enough to see the background screen (wallpaper) and then reboot.
I'll gladly give $20 to anyone who offers a workable solution, paid either to you, or dev/charity of your choice if you don't want it.
This all started when I installed Fresh 5.2.1. Not sure if it was the fresh install or using TWRP to wipe data/cache and I also wiped system. Was that a mistake?
I just don't understand why I can't flash back even to stock. Since I'm relocked and never had S-OFF I don't understand how I was able to do something that can't be undone by flashing. I've flashed phones dozens of times so am comfortable with the process and just can't understand what went wrong and how to recover.
Is there an updated version of the PJ75IMG.zip file I could use?
Would it work to flash CM10 & the boot.img using fastboot?
Click to expand...
Click to collapse
I sent you a PM
Sent from my EVO using xda premium
I'm back up and running. With a kind and helpful tech we ran RUU again (twice) and still had boot loop. I was going to give up on it but we went into the default recover and cleared data and factory reset and it seems to be back to normal again and working fine.
Sent from my MB855 using Tapatalk 2
jeggen said:
I'm back up and running. With a kind and helpful tech we ran RUU again (twice) and still had boot loop. I was going to give up on it but we went into the default recover and cleared data and factory reset and it seems to be back to normal again and working fine.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
Awesome glad you got it fixed.
Sent from my EVO using xda premium
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 I am probably going to call verizon tomorrow to get a replacement for my rez, but I am worried about unrooting mine. This one is a replacement and after i got it s off I tried to flash the newest RUU to get the radios, but it would constantly get stuck when updating the system and would then loop and try again and never finish. So I just flashed a recovery and then got the flashable version of the radios and it worked good enough. But now my problem is that before when I sent in my rez I just reflashed the RUU and it reset everything and my HBOOT showed that it was locked s on and not tampered. That would be ideal if I could get that again, how would I go about doing that? just flashing a stock rom, deleting superuser, and then flashing a HBOOT that shows s on and not tampered? any help would be greatly appreciated
No one answered so im trying to figure this out by myself, and i cant get my hboot to not say tampered but still be on the stock hboot so i can adb the s on command. I have pulled the hboot update out of the RUU and it flashed fine but it still says tampered
hboot says tampered if a custom recovery is installed. You have to be on stock recovery (not hboot) to keep it from saying tampered. Flashing a stock RUU is the easiest way.
shrike1978 said:
hboot says tampered if a custom recovery is installed. You have to be on stock recovery (not hboot) to keep it from saying tampered. Flashing a stock RUU is the easiest way.
Click to expand...
Click to collapse
thanks for answering, but that my problem. My phone doesnt like flashing a RUU, it will update until it gets to system, then it will just gt in a loop of flashing and unzipping the system. I had made a modified version that just flashed the hboot and recovery in hboot but it didnt change the tampered
xxtsxx said:
thanks for answering, but that my problem. My phone doesnt like flashing a RUU, it will update until it gets to system, then it will just gt in a loop of flashing and unzipping the system. I had made a modified version that just flashed the hboot and recovery in hboot but it didnt change the tampered
Click to expand...
Click to collapse
It usually takes at least twice for an RUU to fully flash. I've had it take 3 times. When it's done completely, it will reboot normally.
Edit: Also, system is huge and is actually made up of a bunch of files. It does each of those individually, so you see it flashing system several dozen times. That's completely normal.
shrike1978 said:
It usually takes at least twice for an RUU to fully flash. I've had it take 3 times. When it's done completely, it will reboot normally.
Edit: Also, system is huge and is actually made up of a bunch of files. It does each of those individually, so you see it flashing system several dozen times. That's completely normal.
Click to expand...
Click to collapse
wow oh crap i feel stupid. im gonna just let it do its thing for awhile then and see what happens
Edit: well that worked perfectly. i guess a little patience goes a long way. thanks for all the help
For the last week or so, I've noticed my Wi-Fi has been dropping in and out. I had been trying some JB ROMS lately and restoring to another Sense ROM. I figured it needed a big refresh, so I ran the 403.605.2 RUU from the root of the SD card in the PH98IMG.zip form.
Still the same issues, and now my 4G is really flaky.
Now I'm wondering if my phone is just on its way out.
Is running the RUU from a PC better?
Can I do any other wipe/flash combos to reset it even further?
I am S-Off...
Run the ruu again and perform a factory reset in hboot BEFORE installing a custom recovery.
bwthor20 said:
For the last week or so, I've noticed my Wi-Fi has been dropping in and out. I had been trying some JB ROMS lately and restoring to another Sense ROM. I figured it needed a big refresh, so I ran the 403.605.2 RUU from the root of the SD card in the PH98IMG.zip form.
Still the same issues, and now my 4G is really flaky.
Now I'm wondering if my phone is just on its way out.
Is running the RUU from a PC better?
Can I do any other wipe/flash combos to reset it even further?
I am S-Off...
Click to expand...
Click to collapse
the most up to date ruu is firmware_4.05.605.14 with the 2.28 HBoot and 2.23.10.0123r, 2.23.10.0124r radios.....here is a link ( https://dl.dropboxusercontent.com/u/12405441/new.global.firm.PH98IMG.zip ) make sure you re install your recovery afterwards and that both radios read 2.23 and not 2.22...theres much more info on this here ( http://forum.xda-developers.com/showthread.php?t=2260154 ) but make sure its the new global ota latest update...this is what i did and hope this helps you
Edit: i too am s-off and ran this with all jb roms posted and it works perfectly fine....also always make backups and rename that file on the link and make sure it looks like PH98IMG.zip
REV3NT3CH said:
the most up to date ruu is firmware_4.05.605.14 with the 2.28 HBoot and 2.23.10.0123r, 2.23.10.0124r radios.....here is a link ( https://dl.dropboxusercontent.com/u/12405441/new.global.firm.PH98IMG.zip ) make sure you re install your recovery afterwards and that both radios read 2.23 and not 2.22...theres much more info on this here ( http://forum.xda-developers.com/showthread.php?t=2260154 ) but make sure its the new global ota latest update...this is what i did and hope this helps you
Edit: i too am s-off and ran this with all jb roms posted and it works perfectly fine....also always make backups and rename that file on the link and make sure it looks like PH98IMG.zip
Click to expand...
Click to collapse
Thanks for the info. I had run the 4.03.605.2 RUU a couple of times, and also the latest official RUU that updated to 4.05.605.14 with the correct radios you listed. I have no idea what was going on, but my phone seemed to get worse every step. It would reboot, Wi-Fi quit, the 4G quit. It would go into a bootloop on the white HTC screen and wouldn't boot until I ran the RUU again. It finally went to that mode where it wouldn't boot at all until I charged the battery for a few hours. I figured it was hosed, and started browsing eBay for something new.
I finally ran the latest official RUU again and let it update OTA to the latest. I then did a factory reset under settings, then from the bootloader. I ran it stock for a day, then finally last night installed Amon RA and installed EclipticRez v9 and (fingers crossed) things seem to be back to normal.
I really wish I knew what happened, and I'm wondering if it could be battery related. I was sure it was something hardware related. Nothing I did for the couple of days before I first posted helped...
Weird...my phone wasn't that loopy...I've seen similar errors on other posts but if followed proper steps should work fine...I always read twice and flash once just to be safe instead of getting flash happy lol..I updated radios because signal and battery life was poor and read that jelly bean required the latest ruu...so I did tons of research
Sent from my L1QU1D H311H0UND using xda app-developers app
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
brownsfan said:
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
Click to expand...
Click to collapse
So I think I found out what I did. 2.28 is the Global version. I must of rooted that version and flashed roms. I wanted to unroot and get back to stock software version.
Where should I go from here? Is there an RUU for the ICS Global? I can not seem to find one.
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Thingula said:
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Yes I can unlock again and that does get me unstock from the boot screen but still cant get where I want. Hmm.
I wonder if you can fastboot-flash the older kernels, using a computer, then flash the old stock ROM, lock the bootloader, then run an RUU.. Can anyone confirm this? Sounds too simple to work on an HTC phone.
Edit: No, of course that doesn't work. Sorry, I can't really offer any more help.. I'll have to just hope that someone more knowledgeable can take over.
Sent from my ADR6425LVW using xda app-developers app
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Very much so! Thank you. If I could hit the thanks button 10x I would.
Im sure im not the only only to have the Hboot 2.28 issue.
hey man you still around ? i need some help with a situation like this
dust906 said:
hey man you still around ? i need some help with a situation like this
Click to expand...
Click to collapse
I replied to you in your thread.
S-On Locked stock !
mikeyk101 said:
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Click to expand...
Click to collapse
This guide was FREAKING AWESOME. It led me to finally after 2 years go S-Off (wire trick) to do RUU, etc. Have to return phone and have already got replacement. Crossed my fingers and everything looks stock stock stock !