Is there anyway to reset the Rezound to the factory locked bootloader?
http://forum.xda-developers.com/showthread.php?p=25165453
Assuming you have done the HTC Dev unlock, you must do S-off and follow the guide here to get back to reading "Locked" and "S-on" simultaneously.
Edit: Ok, so I see you are S-off at the moment, you are going to want to backup all your data in your custom recovery if you haven't done so already (still on CWM or got that straightened out?)
Going to download the latest official RUU available (the GB OTA at the moment); here is a link to the GB OTA thanks to con247: http://forum.xda-developers.com/sho...uide to S-On to restore that too if you wish.
PhantasmRezound said:
http://forum.xda-developers.com/showthread.php?p=25165453
Assuming you have done the HTC Dev unlock, you must do S-off and follow the guide here to get back to reading "Locked" and "S-on" simultaneously.
Edit: Ok, so I see you are S-off at the moment, you are going to want to backup all your data in your custom recovery if you haven't done so already (still on CWM or got that straightened out?)
Going to download the latest official RUU available (the GB OTA at the moment) and have it handy; here is a link to the GB OTA thanks to con247: http://forum.xda-developers.com/showthread.php?p=22045045
Now make sure your bootloader is Locked before running the RUU. Check this and be certain; have to do a bit of extra work if it isn't, so please say you didn't Dev Unlock again after doing S-off lol. (I did this. Had to repeat the whole S-off process to achieve a "Locked" message ultimately. Not fun.)
Ok, after making sure bootloader is Locked... Running that RUU should put the stock hboot back on, verify that after the process. And remeber to turn USB Debugging back on in the stock ROM after running that RUU lol . Then proceed with the guide on the same computer you got all those Dev tools on from doing S-off.
Click to expand...
Click to collapse
If I remember correctly if it's a patched hboot and not the stock hboot your not supposed relock it because you can brick that way. Since the phone is S-OFF just running the GB RUU will be fine then just factory reset from hboot after the RUU finishes and your good to go. Also it's ok to keep it S-OFF because some phones come stock that way but if you really want you can run the command to get S-ON.
Sent from my ICS Rezound
LakerStar25 said:
If I remember correctly if it's a patched hboot and not the stock hboot your not supposed relock it because you can brick that way. Since the phone is S-OFF just running the GB RUU will be fine then just factory reset from hboot after the RUU finishes and your good to go. Also it's ok to keep it S-OFF because some phones come stock that way but if you really want you can run the command to get S-ON.
Sent from my ICS Rezound
Click to expand...
Click to collapse
Yes, this. Didn't mean to suggest actually trying to Relock your phone post S-off. That would definitely be bad if you accepted the JuopunutBear hboot or flashed the Engineer one instead of Stock hboot.
So in any case, you should go ahead and run the RUU after backing up data, do the factory reset, and follow through with turning the security flag to ON if you're wanting the full original state (though Verizon almost certainly won't check or care, and the next user mostly benefits from S-off)
((Sorry, I was just thinking how I jumped the whole gun the hour after JuopunutBear came out. Kept my stock hboot before anybody knew why the process was wanting to push that patched hboot to the phone lol. I used the Dev unlock procedure again *after* S-off. So, at this point I would have to do this process twice to get the same result, to first get a plain Locked status by running the RUU and doing the S-off procedure again... then RUU and do S-on too. Totally forgot those custom JB hboots will say "JuopunutBear" instead of whatever lock status it may be. Edited original post.))
PhantasmRezound said:
Yes, this. Didn't mean to suggest actually trying to Relock your phone post S-off. That would definitely be bad if you accepted the JuopunutBear hboot or flashed the Engineer one instead of Stock hboot.
So in any case, you should go ahead and run the RUU after backing up data, do the factory reset, and follow through with turning the security flag to ON if you're wanting the full original state (though Verizon almost certainly won't check or care, and the next user mostly benefits from S-off)
((Sorry, I was just thinking how I jumped the whole gun the hour after JuopunutBear came out. Kept my stock hboot before anybody knew why the process was wanting to push that patched hboot to the phone lol. I used the Dev unlock procedure again *after* S-off. So, at this point I would have to do this process twice to get the same result, to first get a plain Locked status by running the RUU and doing the S-off procedure again... then RUU and do S-on too. Totally forgot those custom JB hboots will say "JuopunutBear" instead of whatever lock status it may be. Edited original post.))
Click to expand...
Click to collapse
Cool I was just trying to help out lol.
Sent from my ICS Rezound
I have a Rezound on RezRom (latest). The phone is s-off... I can't believe I got through that with my old eyes and limited tech ability...
I got a new phone, and want to give the Rezound to my daughter. What would be the right thing to flash to make her stock, and able to receive updates? I don't care if the phone stays s-off or goes back to s-on-- she'll never use that feature anyhow.
I'm guessing I can just run this: RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00.1123r_3161E_9K_QMR_release_233635_signed.exe and all will be back to stock, the updates will work, the phone will be erased and probably s-on again.
If someone can point me in the right direction, I'd appreciate it. (So would she... she's still rocking an OG droid!)
Thanks much in advance for any help!
Cheers,
SteveRN
S-OFF will remain after RUU but there's a thread about returning to S-ON but make sure it's after the RUU or you'll brick your phone beyond repair.
Sent from my ADR6425LVW
Running that ruu will get you completely back to stock with the exception of s-off. If you want to set it back to s-on there's simply a fast boot command you need to run. There are a few threads around here that talk about it if that's the way you want to go.
Sent from my ADR6425LVW using XDA
Here's the thread for s-on btw.
http://forum.xda-developers.com/showthread.php?t=1612937
Sent from my ADR6425LVW using XDA
Many thanks to you all. (of course I hit the button) ;-)
I'll run the RUU and leave it S-off. As long as it's on the upgrade path I'm a happy camper... and If I ever need to flash something for her, I can.
If it breaks or anything I'll be able to s-on it I suppose, she would only send it in through me anyway... (yeesh... kids )
Still stuck trying to flash stock back to my S-Off rezound...
Uh oh. Still stuck. I run the RUU i listed above and it errors out.
I boot the phone into the latest RezRom (ics) and run the RUU; the RUU gets to the part where it says "ok, say ok to flash this" and then it comes up "unknown error".
Am I supposed to start this up while the phone is in recovery? or is there a zip I can flash like a ph98img.zip that would take me to stock, even if it's s-off stock?
Argh.
RezRom still boots up fine. I can reboot into TWRP as well.
Help! (I need a clue....)
try preforming a factory reset in bootloader then try the ruu again
steven.rn said:
I have a Rezound on RezRom (latest). The phone is s-off... I can't believe I got through that with my old eyes and limited tech ability...
I got a new phone, and want to give the Rezound to my daughter. What would be the right thing to flash to make her stock, and able to receive updates? I don't care if the phone stays s-off or goes back to s-on-- she'll never use that feature anyhow.
I'm guessing I can just run this: RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00.1123r_3161E_9K_QMR_release_233635_signed.exe and all will be back to stock, the updates will work, the phone will be erased and probably s-on again.
If someone can point me in the right direction, I'd appreciate it. (So would she... she's still rocking an OG droid!)
Thanks much in advance for any help!
Cheers,
SteveRN
Click to expand...
Click to collapse
Ignore this post.......
Sent from my MB870 using Xparent Cyan Tapatalk 2
dogredwing1 said:
try preforming a factory reset in bootloader then try the ruu again
Click to expand...
Click to collapse
Thanks bud... that didn't work either.
When I run adb devices, I see the rezound listed... I'm still thinking there is a zip i could flash from twrp, but I don't know where to find a stock zip that I could rename to ph98img.zip for that.
I am a bit mystified why the RUU won't run.
the hboot is 2.25, could that be it?
steven.rn said:
Thanks bud... that didn't work either.
When I run adb devices, I see the rezound listed... I'm still thinking there is a zip i could flash from twrp, but I don't know where to find a stock zip that I could rename to ph98img.zip for that.
I am a bit mystified why the RUU won't run.
the hboot is 2.25, could that be it?
Click to expand...
Click to collapse
Does it say unlocked at the top by any chance? In hboot that is?
If so you run, "fastboot OEM lock" while in fastboot. Then run the ruu.
Sent from my ADR6425LVW using XDA
nosympathy said:
Does it say unlocked at the top by any chance? In hboot that is?
If so you run, "fastboot OEM lock" while in fastboot. Then run the ruu.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
It says "locked" but I do remember unlocking it before s-off. I'll chase that down a bit, I think you have something here. I'll let you know in a bit
nosympathy said:
Does it say unlocked at the top by any chance? In hboot that is?
If so you run, "fastboot OEM lock" while in fastboot. Then run the ruu.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
What ended up working was booting the phone into fastboot and then running the RUU. I didn't know you had to do that.... I don't know if I was just clueless on this one or if things are different with an S-Off phone.
Thanks, Dr. No
steven.rn said:
What ended up working was booting the phone into fastboot and then running the RUU. I didn't know you had to do that.... I don't know if I was just clueless on this one or if things are different with an S-Off phone.
Thanks, Dr. No
Click to expand...
Click to collapse
glad it worked out, second recommendation was going to be pulling the rom.zip file from the ruu.exe and running that through hboot itself.
I received a replacement Rezound today and have messed it up beyond my repair. When I powered the new phone on it was on the old GB software. I manually searched for an update which was finally found. I downloaded the update and went through the process of installing it. About half way through the update, a red triangle with an exclamation point appeard. I tried this process twice and then decided to run the RUU that I had installed on my sd card from my prior phone. The RUU was the most recent ICS.
At this point I was not S-off or rooted, but completly stock. The RUU did not fully run but it did update my HBOOT and Radio's. When I boot the phone, it is still on GB software. I have some how changed my bootloader to show Tampered as well.
I was able to flash a zip file of AmonRa 3.15 and was able to flash ViperRom 1.03. I thought this would correct the problems and allow me to S-Off but it did not.
I thought that if I could S-off I could maybe get this all straight. But I am not sure.
At this point, I have a phone that reboots after a few short minutes.
Any help will be greatly appreciated!!
Romans8vs1 said:
I received a replacement Rezound today and have messed it up beyond my repair. When I powered the new phone on it was on the old GB software. I manually searched for an update which was finally found. I downloaded the update and went through the process of installing it. About half way through the update, a red triangle with an exclamation point appeard. I tried this process twice and then decided to run the RUU that I had installed on my sd card from my prior phone. The RUU was the most recent ICS.
At this point I was not S-off or rooted, but completly stock. The RUU did not fully run but it did update my HBOOT and Radio's. When I boot the phone, it is still on GB software. I have some how changed my bootloader to show Tampered as well.
I was able to flash a zip file of AmonRa 3.15 and was able to flash ViperRom 1.03. I thought this would correct the problems and allow me to S-Off but it did not.
I thought that if I could S-off I could maybe get this all straight. But I am not sure.
At this point, I have a phone that reboots after a few short minutes.
Any help will be greatly appreciated!!
Click to expand...
Click to collapse
If it tanked doing the OTA ICS update right out of the box, I'd call VZW for another phone...
Thank you for the reply, but my hboot now says tampered and relocked. I do not think I could send the phone back in this condition and get a new one.
Anyone else have any ideas?
Un-lock using HTC unlock then s-off your phone using some wire tied to a couple thumb tacks. Run latest ruu again, then install recovery, then flash Rom.
Sent from my ADR6425LVW using xda app-developers app
iHateWebOS said:
Un-lock using HTC unlock then s-off your phone using some wire tied to a couple thumb tacks. Run latest ruu again, then install recovery, then flash Rom.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Why on earth do you hate WebOS?!?
I wasted a lot of life thinking it was the greatest....... Lies! Lies! Do you have any idea how lucky android users are to have on device recovery? When ya boot loop a webos phone ya need to hook up to a computer no matter what ya did wrong. Now I just restore a nandroid....I was so happy when I upgraded to a pre 2.... Now I just feel dumb for staying with webos for so long
Sent from my ADR6425LVW using xda app-developers app
AshtonTS said:
Why on earth do you hate WebOS?!?
Click to expand...
Click to collapse
Why do you not hate webOS? Awful.
In case anyone else has this problem, I was able to re-lock and flash the RUU through adb to get everything corrected. I'm now rooted, S-off, and running inef 1.2!
for some reason i'm having a big problem going back to stock.
here's my current set up...
tampered
unlocked
s-on
hboot 1.12.0000
TWRP recovery
Stock with Goodies 3.40
all i'm trying to do is get back to stock!
here's what i've done so far...
1. connected phone to PC with USB Debugging on and ran RUU of the latest release
2. phone reboots and goes to the black HTC screen and just gets stuck there forever
then I realize I have to relock it so I relock and then reboot but then it just gets stuck in bootloader and won't go into OS or recovery...just reboots to bootloader when I try to do anything. plus when I try to do adb or run RUU from PC, the PC doesn't think the phone is actually connected to it.
so i've re-unlocked and now it goes back to OS but my whole point is to go to stock and unroot...what the hell am I doing wrong? I'm about to just throw the phone into the ground and get a new one since I have squaretrade warranty.
I know many of you are probably just thinking...why doesn't he s-off? because i don't have access to 32 bit windows 7 PC and figured just unrooting and then updating to latest RUU and then rerooting/unlocking would be sufficient.
THANKS in advance for any advice...
maybe
u might watch this video. i did the same this morning. made it easy for me anyway.
http://www.qbking77.com/how-to-unroot/unrootunbrick-the-htc-evo-4g-lte.html
all his videos are great.
that's what I started with...relocked and then ran RUU but it just gets stuck at the black HTC logo screen forever...like we're talking over an hour. the thing says it may take 10 minutes or so...i'm not getting anything status update...it just gets stuck there...
trsix said:
u might watch this video. i did the same this morning. made it easy for me anyway.
http://www.qbking77.com/how-to-unroot/unrootunbrick-the-htc-evo-4g-lte.html
all his videos are great.
Click to expand...
Click to collapse
umm
maybe instead of the latest ruu u should run the 1.12
http://www.androidfilehost.com/?fid=9390326628153819199
then again i'm still learning and don't know jack sheet
mine was 2.09 thats what i ran worked fine
Maybe Try Again
It took me a few tries or so, to get the RUU to work, but it finally worked.
One thing I realized is that I had to flash stock recovery prior to relocking, otherwise you're wasting your time, afaik.
...which leads me to how I came across this thread. I can't remember where I found stock recovery. I've been searching xda almost an hour. Can anyone tell me?
Dr Lexus said:
It took me a few tries or so, to get the RUU to work, but it finally worked.
One thing I realized is that I had to flash stock recovery prior to relocking, otherwise you're wasting your time, afaik.
...which leads me to how I came across this thread. I can't remember where I found stock recovery. I've been searching xda almost an hour. Can anyone tell me?
Click to expand...
Click to collapse
Click the link in my sig
Sent from my PoS MoPho
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
BrahManty said:
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
Click to expand...
Click to collapse
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
acejavelin said:
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
Click to expand...
Click to collapse
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
BrahManty said:
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
Click to expand...
Click to collapse
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
acejavelin said:
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
Click to expand...
Click to collapse
Oh, thank god. Hahah. I didn't remember ever flashing any leaked firmware before, so I was kind of confused there. I figured I may have done it somewhere in the unlocking/rooting process and just couldnt remember. Okay, thanks again for the help. RUU's have always confused me with the way they work. I should be stable in no time hopefully.
And now I'm having more issues... I can't use the Rom Updater because somethings wrong with my usb connection. I can plug it in and transfer files and such, but trying to use any ADB commands results in "Device not found" and the Rom Updater says it can't connect to my device either. My HTC Drivers are up to date, so I'm not sure why this is happening. Is there any way I can just get the PH98IMG.zip for 3.14.605.12 instead of having to use the RUU?
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
acejavelin said:
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
Click to expand...
Click to collapse
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
BrahManty said:
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
Click to expand...
Click to collapse
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
acejavelin said:
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
Click to expand...
Click to collapse
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
BrahManty said:
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
Click to expand...
Click to collapse
Cool, glad you got it working.
That firmware is actually pretty decent and rock solid stable, you shouldn't have any more software related issues... Plus you can root/ROM like normal from that version, the radios may be slightler lower than most recommended versions, but they should work fine. If you do decide to go the ROM route again, I would suggest going S-OFF before starting, it will just make it easier in the long run.
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
*** TAMPERED ***
*** LOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
Click to expand...
Click to collapse
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
JoeKamel said:
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
Click to expand...
Click to collapse
You should be able to just boot into twrp and flash a rom
Sent from my ADR6425LVW using xda premium
izzaeroth said:
You should be able to just boot into twrp and flash a rom
Click to expand...
Click to collapse
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
JoeKamel said:
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
Click to expand...
Click to collapse
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Sent from my ADR6425LVW using xda premium
izzaeroth said:
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Click to expand...
Click to collapse
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
JoeKamel said:
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
Click to expand...
Click to collapse
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Click to expand...
Click to collapse
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
JoeKamel said:
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
Click to expand...
Click to collapse
Recovery = twrp
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
S-off is S-off... installing a RUU wont change that, it may set you back to 'Locked", but you are S-off so it doesn't matter, you can stay locked&s-off and its no different than unlocked/S-off.
If you are going back to stock and are S-off I would use the Global Mode Leak (4.3.605.2) available on AndroidPolice and flash in Hboot... rename file to PH98IMG.zip and place in root of SD card (how it gets there is a irrelevant) then reboot into Hboot, confirm and wait.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app