My 3G has been terrible since I got the phone, so I finally took it in to the sprint repair shop. They said before they can look at it I need to unroot and take the latest sprint update.
If I go stock and take the official OTA update, will I be able to achieve S-OFF and root again?
How do I go about going completely back to stock?
Thanks!
If you are s-off, flash the ruu.exe. Everything will go back to stock (ROM, recovery, etc), but you will remain s-off. I think you have to lock the bootloader first, but you don't need to be s-on.
Imagika FTW... with Tapatalk 2
Raillery said:
My 3G has been terrible since I got the phone, so I finally took it in to the sprint repair shop. They said before they can look at it I need to unroot and take the latest sprint update.
If I go stock and take the official OTA update, will I be able to achieve S-OFF and root again?
How do I go about going completely back to stock?
Thanks!
Click to expand...
Click to collapse
Hello,
I believe I can help you out with this. Are you s-off right now? If so, then all you have to do is download the latest ruu. It's easy. You can find it in the development section under stickies. If your s-on however you will need to run the ruu.exe on your pc which I believe you can find that file under the stickies. Now if your s-off, you can flash the ruu file by renaming it to PG86IMG in all caps and placing it on the root of your sdcard and booting into bootloader and flashing it from there. If you are going to turn s-off back to s-on you must do this immediately after you flash the ruu. Just go to fastboot on your computer with your phone in fastboot and type this command fastboot oem write securityflag 3. I believe that's the right command. Just make sure your hboot is stock and not modified or else you will brick your phone. And of course you can still achieve s-off and reroot after that. Ramjet wrote a very simple and easy guide that will help you step by step with the easiest way to get there. You can find his guide in the general discussion section. If you have any questions please do not hesitate to ask.
Please hit the thanks button if helped you in Anyway. Goodluck.
This ruu? The second one?
Raillery said:
This ruu? The second one?
Click to expand...
Click to collapse
Those are firmware .zip's that won't return everything to stock. I'd suggest that you download the 2.89.651.2 ICS RUU.exe from one of the links in this post and run it from Windows. Then you will be totally stock except for S-OFF and they shouldn't care about that. When you get the phone back you can just flash a custom recovery then root the stock ROM or flash a custom rooted ROM without having to worry about getting S-OFF again, unless they set it back to S-ON when it is serviced.
ramjet73
ramjet73 said:
Those are firmware .zip's that won't return everything to stock. I'd suggest that you download the 2.89.651.2 ICS RUU.exe from one of the links in this post and run it from Windows. Then you will be totally stock except for S-OFF and they shouldn't care about that. When you get the phone back you can just flash a custom recovery then root the stock ROM or flash a custom rooted ROM without having to worry about getting S-OFF again, unless they set it back to S-ON when it is serviced.
ramjet73
Click to expand...
Click to collapse
Do you have the link to the ruu that can be run through the phone? I keep getting error 155 unknown error.
EDIT: Nvm it worked, just had to manually rebooted to bootloader.
Raillery said:
Do you have the link to the ruu that can be run through the phone? I keep getting error 155 unknown error.
Click to expand...
Click to collapse
That error means you didn't lock the bootloader first. Use the fastboot command: fastboot oem lock. Then run the ruu.
Imagika FTW... with Tapatalk 2
hey forum
i really need some help now. i have a gsm evo 3d unlocked up and running a custom rom (nonsense). now i want to return to stock, ive tried flashing the ruu for several times, but each time it says bootloader version error. so i guessed that i have to downgrade my hboot version from 1.53.0007 to something 1.49.007 or similiar. i just cant get it to work, neither with flashmaniacs way, or the manual way. in bootloader when loading the PG86IMG ist says version older update fail.each time i fail i reunlock the bootloader, so atleast i can use my phone. the worst and most foolish part of me: no nandroid backup. so i recognize my fault.
Do you have the newest ruu.exe for your region/carrier? Once you get it, boot into bootloader, connect to computer (should say fastboot usb), lock bootloader, then run ruu. That should put you at stock.
Test shooter u ruu for ics?
coal686 said:
Do you have the newest ruu.exe for your region/carrier? Once you get it, boot into bootloader, connect to computer (should say fastboot usb), lock bootloader, then run ruu. That should put you at stock.
Click to expand...
Click to collapse
i dont know wether its the newest or not, ive tried the one i got from file factory its called
RUU_Shooter_U_HTC_Europe_1.20.401.8_Radio_10.59.9020.00_10.15.9020.06_M_release_219793_signed.exe
im not sure, but i think its gingerbread. ive been searching for an ics ruu fpr europe, but havent found one yet, only one "test ruu" which is official, should i give it a go? it seems to have some minor bugs.
heres the thread
http://forum.xda-developers.com/showthread.php?t=1669104
do you know where to get a stock ics ruu for sure?
I'm in the US, so I don't know exactly. Did you look here: http://forum.xda-developers.com/showthread.php?t=1208485
Have you relocked your bootloader before flashing ruu? Bootloader must locked or relocked if you want to flash stock soft. I've flashed RUU named:
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed
It's stock ics rom. Here is direct link:
http://www.filefactory.com/file/2hw...00U_11.25.3504.06_M_release_262714_signed.exe
c000ler said:
Have you relocked your bootloader before flashing ruu? Bootloader must locked or relocked if you want to flash stock soft. I've flashed RUU named:
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed
It's stock ics rom. Here is direct link:
http://www.filefactory.com/file/2hw...00U_11.25.3504.06_M_release_262714_signed.exe
Click to expand...
Click to collapse
yes i relocked my bootloader each time i tried to flash. thanks alot! ive been looking for a ICS ruu for quite some while, gonna download it and try it out. hope itll work out fine.
the ones i downloaded from the filefactory link somehow didnt work, dont know why.
i really appreciate your help, thanks guys
it worked, im back to stock, so it was the old ruu which created problems. thanks
Alright, I hate having to post a new thread on this topic, but I cannot find any solution, or anything close to a solution for this. my problem is that i cant get back to stock from the newest firmware. I had unlocked, rooted, and gotten s-off all before the update. After that, i flashed a few things, and ended up updating to the newest radio and firmware number (2.04.605.2, and 1.01.01.0110). now i want to go back to stock and start fresh, but nothing seems to work. Trying the RUU method only gets me to a 158 Image error about 3 minute into the process, and i cant seem to get back to 1.15. any help is much appreciated. I've been at it, searching for 5 days. if i missed something, or missed a thread, please let me know, thank you in advance
Flash the ENG Hboot then you will be able to run the RUU. Making sure you have the bootloader drivers installed. I generally boot into the bootloader and verify the drivers are loaded BEFORE running the RUU. I can say I have flashed the RUU numerous times so I know it works with the ENG hboot.
Yeap zone is correct, flash the Eng RUU or relock your bootloader either way and then run the RUU. It won't run on a stock hboot that's unlocked.
Sent from my HTC6435LVW using Xparent Red Tapatalk 2
zone23 said:
Flash the ENG Hboot then you will be able to run the RUU. Making sure you have the bootloader drivers installed. I generally boot into the bootloader and verify the drivers are loaded BEFORE running the RUU. I can say I have flashed the RUU numerous times so I know it works with the ENG hboot.
Click to expand...
Click to collapse
Thank you! worked like a charm, i appreciate your quick response I've been running in circles for days now, i can finally get back on track!
Glad I could help.
ENG Hboot & unroot
I'm having the same problem as the op. I downloaded the updates, and i'm trying to unroot my device and put it back to stock (I broke my screen and I want Verizon to fix it, without giving me grief about my software). I have the RUU and Its giving me an 158 Image Error. Sounds like I need to flash eng Hboot and then run the ruu.
Two Questions:
1. Where can I get / download eng Hboot for my DNA?
2. Which version of Hboot do I need? I currently have hboot 1.33.0001.
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.
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