Well the update that hit tmous today have any effect on One S user who are already rooted and using a 4.2.2 Rom?
Sent from my One S using xda app-developers app
mrminor13 said:
Well the update that hit tmous today have any effect on One S user who are already rooted and using a 4.2.2 Rom?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
No. You must me on the stock rom to get notification. You must then have a locked bootloader and stock recovery to actually run the update.
fbihawk said:
No. You must me on the stock rom to get notification. You must then have a locked bootloader and stock recovery to actually run the update.
Click to expand...
Click to collapse
That's what I thought. I'm excited that I get to see it on my wife's phone.
Sent from my One S using xda app-developers app
fbihawk said:
No. You must me on the stock rom to get notification. You must then have a locked bootloader and stock recovery to actually run the update.
Click to expand...
Click to collapse
Locked bootloader? I have done an update before with an unlocked boot loader. Just curious. Plan to try this afternoon.
Sent from my HTC One S using Tapatalk 2
SoTacMatt said:
Locked bootloader? I have done an update before with an unlocked boot loader. Just curious. Plan to try this afternoon.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
That's been my experience. Try it without if you would like. Can't hurt anything.
i am currently S-off and running viper rom. If I change my cid back to the TMo version and reflash the ruu so I return to stock, would I get the update? DO i need to lock the bootloader and S-ON?
I hav relocked the bootloader bt cn some one provide me stock recovery for cid 044 jelly bean
Sent from my HTC One S using xda app-developers app
Just so you guys know...i dont condone everyone to do this but it worked for me...
Was: SuperCid 111111 , Rooted, and S-Off running latest(before today) Tmo Us rom .
Flashed stock recovery, locked bootloader, ran ota update, unlocked bootloader, flashed twrp, flashed Supersu in said recovery.
Now rooted/supercid/soff on Tmo us jelly bean 4.1.1 ...
aegentirony said:
Just so you guys know...i dont condone everyone to do this but it worked for me...
Was: SuperCid 111111 , Rooted, and S-Off running latest(before today) Tmo Us rom .
Flashed stock recovery, locked bootloader, ran ota update, unlocked bootloader, flashed twrp, flashed Supersu in said recovery.
Now rooted/supercid/soff on Tmo us jelly bean 4.1.1 ...
Click to expand...
Click to collapse
You should not use supercid for an ota there are many reports of bricked phones that way! change your cid to original also stock recovery is a must!
fbihawk said:
That's been my experience. Try it without if you would like. Can't hurt anything.
Click to expand...
Click to collapse
Re-locked bootloader and the RUU is working. Thanks!!!
Have you guys updated your phone yet, and if so were you able to unlock and root again? I just finished restoring the gf's phone back to stock but all her apps were backed up via Titanium and from Viper 2.0, which is JB based. I can't restore her apps and data unless she's on a JB rom, if I remember correctly.
Sent from the other One.
Could someone please point me in the right direction to where I can get my wife's T-MobileUS One S (S4) back to where she can OTA update it to JB? I've been around quite awhile, but am personally a Nexus user and am not very familiar with Sense roms yet. I've done a lot of reading up on it but am getting a little confused. I keep reading about the HBOOT version possibly causing problems? Here is her setup.
Stock 4.0.4/rooted
CWM recovery
CID-T-MOB010
***TAMPERED ***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Aug 14 2012,18:01:48
I'm not sure what ROM my gf was on. First I backed up with Titanium Backup. I flashed the stock recovery with fastboot, locked the bootloader, ran the 2.35 Tmobile RUU (to get her to completely stock), ran the Software Update from the About Menu to get JB, unlocked the bootloader, flashed TWRP recovery with fastboot, and flashed the supersu.zip in TWRP. All is good, I have working root and was able to restore using Titanium. She'll be happy when she wakes up.
Is a locked bootloader necessary?
SoTacMatt said:
Re-locked bootloader and the RUU is working. Thanks!!!
Click to expand...
Click to collapse
Did you try updating without re-locking the bootloader? I was able to update the last time (the security fix they pushed out) without re-locking the bootloader. I'd like to avoid re-locking if possible. I know I need to revert to the stock recovery (that's fine).
--------------
ROM: T-Mobile Stock 4.0.4
HBOOT: 1.14.0005
Recovery: CWM 5.8.3.1
Rooted: Yes
I did try to use the RUU without locking the bootloader. It failed. That is when I did 'fastboot oem lock' and everything else went smoothly!!!
Not necessary to re-lock bootloader for OTA
I can confirm that it is not necessary to re-lock the bootloader to receive the OTA update to JB. I am on Stock TMOUS, rooted and with an unlocked bootloader. I suspect that one needs to re-lock the bootloader only if one is restoring the device to factory settings using an RUU. It certainly isn't required for a successful OTA update.
Here are the steps I followed (assuming you have the android SDK configured and the phone plugged in via USB into a PC):
1. Installed the stock recovery (fastboot flash recovery <name_of_recovery_file.img>)
2. Un-installed Superuser.apk to remove root. ( rm /system/app/Superuser.apk )
3. Rebooted the phone.
4. Checked for system update (Settings - About - Software updates - Check now...)
5. Chose to download the update. It took a while to download even on WiFi.
6. Chose to install the update.
7. Let the phone settle for about 30 minutes. It will not be as responsive during this time.
8. Re-install custom recovery (I use ClockworkMod).
9. Re-install root.
Once the update was complete (step 6 above), I did have a minor issue where the keypad was not showing up for me to enter the PIN to unlock the phone. I rebooted (hold down the Power button for about 10 seconds) and then I was able to get past that just fine.
------------
ROM: T-Mobile US Stock 4.1.1
HBOOT: 2.15.0000
Radio: 1.13.50.05.31
Recovery: CWM 5.8.3.1
Rooted: Yes
Related
I never rooted my phone, it was done halfway there in procedure (never installed a custom ROM)
I had installed bootloader (4ext) and S-off
As of now on the phone I had a rom backup using 4ext for January (back when I was trying to root)
I waited long and hard for the OTA ICS update, which now I realize is out for Bell.
I tried to apply the update, phone reboots and 4ext tries to perform the update and I get a path error SDCARD\download\ (update file name)
Alternatively I tried booting up 4EXT and using "update from zip", with the OTA update file, and that applies and reboots to a stuck HTC white screen.
I just want to get this OTA update installed, thanks for advice!!!
PS: I don't think a factory reset is possible, I don't know where the factory reset data is stored or if its gone
funkbro2 said:
I never rooted my phone, it was done halfway there in procedure (never installed a custom ROM)
I had installed bootloader (4ext) and S-off
As of now on the phone I had a rom backup using 4ext for January (back when I was trying to root)
I waited long and hard for the OTA ICS update, which now I realize is out for Bell.
I tried to apply the update, phone reboots and 4ext tries to perform the update and I get a path error SDCARD\download\ (update file name)
Alternatively I tried booting up 4EXT and using "update from zip", with the OTA update file, and that applies and reboots to a stuck HTC white screen.
I just want to get this OTA update installed, thanks for advice!!!
PS: I don't think a factory reset is possible, I don't know where the factory reset data is stored or if its gone
Click to expand...
Click to collapse
man, mustn't update with official ota updates when you are rooted or s-off!
How can I s-on?
funkbro2 said:
How can I s-on?
Click to expand...
Click to collapse
Dude for ota soff is fine... Just flash the stock recovery And make sure cid is unchanged.. Then apply the OTA again
(just get the stock recovery.img from any gb RUU and flash it via fastboot
fastboot flash recovery recovery.img)
That's all... Dont lose soff... SOFF is fine For ota
Sent from my pyramid.. Through blazing fast sonic waves
funkbro2 said:
How can I s-on?
Click to expand...
Click to collapse
you can be S=OFF but you must have stock recovery installed not 4ext and with the rooted part you will loose when you update, so just flash the stock recovery back on your phone and you are set to update.
What may work for you is to try to install the stock Gingerbread RUU for your phone first. Since you can't boot into GB, you may have to extract the rom.zip file from the RUU, rename it to PG58IMG.zip and place it in the root folder of your sdcard. Then restart your phone into the Bootloader and Gingerbread should reload. You do not need to be S-ON. If that is successful, your bootloader and recovery will be back to stock and you should still be S-OFF. The OTA should work at that point.
Now why would I need to reflash to a previous rom, if I never rooted?
My phone boots when I reverted to the Jan 5 rom backup (which is still phone original rom)
I can definitely try installing original gingerbread rom and then apply the OTA update as suggested
funkbro2 said:
Now why would I need to reflash to a previous rom, if I never rooted?
My phone boots when I reverted to the Jan 5 rom backup (which is still phone original rom)
I can definitely try installing original gingerbread rom and then apply the OTA update as suggested
Click to expand...
Click to collapse
Didn't know you were able to recover from a backup. Thought you were stuck on the white HTC screen. In that case, go ahead and try to fall back to a stock recovery, then try to do the OTA.
OTA still fails for same reason
After downloading OTA update, clicking apply.. Phone restarts and loads up 4EXT which proceeds to apply update. And then results in the cannot load path error
funkbro2 said:
OTA still fails for same reason
After downloading OTA update, clicking apply.. Phone restarts and loads up 4EXT which proceeds to apply update. And then results in the cannot load path error
Click to expand...
Click to collapse
As long as you don't have the stock recovery the OTA fails.. Read my previous post.. For God sake
Sent from my pyramid.. Through blazing fast sonic waves
Used RUU to flash back to "original"
Then did OTA update and it worked no problems
Now using ICS from OTA
Thank you everyone
ganeshp said:
Dude for ota soff is fine... Just flash the stock recovery And make sure cid is unchanged.. Then apply the OTA again
(just get the stock recovery.img from any gb RUU and flash it via fastboot
fastboot flash recovery recovery.img)
That's all... Dont lose soff... SOFF is fine For ota
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
Will this work if I have SuperCID, or do I need to change it back?
Also, once OTA update is done, just reflash 4EXT and then SuperSU?
alza6991 said:
Will this work if I have SuperCID, or do I need to change it back?
Also, once OTA update is done, just reflash 4EXT and then SuperSU?
Click to expand...
Click to collapse
probably you have to change your cid to original
and yes after ota update flash 4ext again
rzr86 said:
probably you have to change your cid to original
and yes after ota update flash 4ext again
Click to expand...
Click to collapse
Posted in help thread, but asking you as well:
My phone is HTC Sensation XE, from Australia on Vodafone network.
I need to change my CID back to original, but I can't remember if it was:
HTC-Australia HTC__023
Hutch-Australia HUTCH001
VODA-Australia VODAP021
In Australia, the network is Vodafone-Hutchinson together, so I don't know which one to take.
Not sure what for, but x.xx.862.x - Voda-Hutch AU (Australia) is my provider/location code.
Any help is much appreciated, thanks in advance.
alza6991 said:
Posted in help thread, but asking you as well:
My phone is HTC Sensation XE, from Australia on Vodafone network.
I need to change my CID back to original, but I can't remember if it was:
HTC-Australia HTC__023
Hutch-Australia HUTCH001
VODA-Australia VODAP021
In Australia, the network is Vodafone-Hutchinson together, so I don't know which one to take.
Not sure what for, but x.xx.862.x - Voda-Hutch AU (Australia) is my provider/location code.
Any help is much appreciated, thanks in advance.
Click to expand...
Click to collapse
install cid getter app from play store
it will show the original cid
Hello. So I have an HTC One S on the Telus network. My bootloader is tampered / unlocked. My carrier came out with an update OTA_Ville_U_TELUS_WWE_1.84.661.9-1.70.661.1_release_265425nbzfb5rjuc5cfhg0 that I was able to download but it will not install.
I was just wondering if anyone has come across this issue?
Some info on my phone
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-1.08.0000
RADIO-0.16.31501S.02
OpenDSP-v23.1.0.32.0323
eMMC-boot
I just would like if someone can do a walk through and show us how to get this update installed and then beable to unlock / root the update
Also, my phone is tethered rooted meaning I can't reboot the phone without it being hooked up to my computer so I can run the superboot img
so my phone gets past that htc screen with the red lettering at the bottom. I am wondering if anyone has been able to fix this?
Thanks for any help
Need to re lock bootloader first ' it is not q problem ' go to fastboot and with phone connected and type 'fastboot OEM lock' without the '' and then run it
Sent from my HTC One S using xda premium
k1llacanon said:
Need to re lock bootloader first ' it is not q problem ' go to fastboot and with phone connected and type 'fastboot OEM lock' without the '' and then run it
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I relocked the bootloader but it just kept restarting into the bootloader, no recovery. I might be missing something but it just won't load into the OS now with it locked. I am using the ville-superboot hack atm...maybe i broke it...
Unfortunately i Cant help you with that issue. But can i ask when you downloaded that file. From I have desperately been looking for a stock os for my telus one s.
NVM: Found your post, Now all i need is an RUU for telus. This might be your issue too. is your rom stock? This is only an update so You probably need to be running the RUU rom.
I have a nandroid backup of the stock rom in a .zip file. I don't know how to make it into an RUU or else I would. I am on a stock rom also. I have it rooted and a custom recovery but I didn't load a custom rom on it. Just use the super.boot method to load the OS. Kinda works like a tethered jailbreak.
did you restore cwm recovery to stock recovery?
and2cs said:
did you restore cwm recovery to stock recovery?
Click to expand...
Click to collapse
I tried doing a factory reset and I get the phone symbol with the yellow triangle and it wouldn't go into CMW recovery but I didn't uninstall or load a new recovery after doing the factory reset
What radio has this rom??
coroneta said:
What radio has this rom??
Click to expand...
Click to collapse
See first post
OK so for you TELUS subscribers out there, this is for you. I have a nandroid backup of a stock Telus system. This system is on the lasted update from Telus OTA_Ville_U_TELUS_WWE_1.84.661.9-1.70.661.1. The only thing I have done is obviously unlocked the bootloader and flashed custom recovery to make the backup. I have also included a stock boot.img and a stock recovery.img as well as the actual OTA update (don't think it's needed but it's there).
So, if you can get into the bootloader, you can revert back to a stock rom on TELUS with this backup.
I have tested it so I know that it works.
If you have any questions let me know
The link is to my Dropbox and its been shortened so just copy and paste it into your browser - goo.gl/cyDrg -
Cheers!
P.S. Give it about an hour or so to upload. I live in Canada and our upload sucks
Clonz said:
Hello. So I have an HTC One S on the Telus network. My bootloader is tampered / unlocked. My carrier came out with an update OTA_Ville_U_TELUS_WWE_1.84.661.9-1.70.661.1_release_265425nbzfb5rjuc5cfhg0 that I was able to download but it will not install.
I was just wondering if anyone has come across this issue?
Some info on my phone
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-1.08.0000
RADIO-0.16.31501S.02
OpenDSP-v23.1.0.32.0323
eMMC-boot
I just would like if someone can do a walk through and show us how to get this update installed and then beable to unlock / root the update
Also, my phone is tethered rooted meaning I can't reboot the phone without it being hooked up to my computer so I can run the superboot img
so my phone gets past that htc screen with the red lettering at the bottom. I am wondering if anyone has been able to fix this?
Thanks for any help
Click to expand...
Click to collapse
If you already have rooted your phone why didn't you make the root permanent? There is no excuse for for not being able to reboot without a PC.
Also, I would suggest not updating by OTA or RUU as it will update the HBoot and you won't be able to flash whatever you want after that.
dc211 said:
If you already have rooted your phone why didn't you make the root permanent? There is no excuse for for not being able to reboot without a PC.
Also, I would suggest not updating by OTA or RUU as it will update the HBoot and you won't be able to flash whatever you want after that.
Click to expand...
Click to collapse
That was a different issue with the boot.img I was using. That is not the case with this one.
We are you interested in updating via the ota or just making sure your phone is current with everything? You can do either, your best move is to avoid the OTA and do everything manually.
Is there a way to go back to the HBOOT-1.08.0000 if you did do the OTA?
Clonz said:
Is there a way to go back to the HBOOT-1.08.0000 if you did do the OTA?
Click to expand...
Click to collapse
No there is not at this time.
So a few weeks ago I updated my phone on the TELUS network to 1.84.661.9. This changed my HBOOT and RADIO
My info is now
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-0.17.31501S.10_2
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 20 2012,151418
So because I updated I was told that I can't get root access any longer. Well I was bored so I went to htcdev.com and reunlocked my bootloader, flashed recovery-clockwork-touch-5.8.3.1-ville, and flashed TrickDroid_v7.1.0. Let the rom boot into the OS and updated my binarys in SU and they installed fine.
So if you also updated your device OTA and your on TELUS, you are fine...you can still flash custom roms with the new hboot without any issues.
I have added some screenshots
Cheers!
I don't think they showed up in the last post
ota update
Relock bootloader
Reflash stock recovery
Do ota update
Than unlock back
Your done enjoy
no, its the same as you said but before doing OTA run RUU
ota update
Flash back stock recovery
Than relock bootloader
Last remake ota process to install or
Supose to work
This is probably a long shot but does anyone have a STOCK T-mobile 2.3.6 NAND back I can flash? I tried to update my HTC Sensation 4G to ICS via RUU since I rooted and such. Keeps failing due to some error, doesn't say which. I had some ROM on it but it couldn't connect to Wi-Fi and my mum was furious about that, so I attempted RUU, no beans.
I unlocked bootloader, S-ON, 4EXT TOUCH recovery.
creepinm3 said:
This is probably a long shot but does anyone have a STOCK T-mobile 2.3.6 NAND back I can flash? I tried to update my HTC Sensation 4G to ICS via RUU since I rooted and such. Keeps failing due to some error, doesn't say which. I had some ROM on it but it couldn't connect to Wi-Fi and my mum was furious about that, so I attempted RUU, no beans.
I unlocked bootloader, S-ON, 4EXT TOUCH recovery.
Click to expand...
Click to collapse
i see that you still in gingerbread android
then you must use revolutionary.io method to S-OFF the device
it was unecessary to unlock the bootloader
rzr86 said:
i see that you still in gingerbread android
then you must use revolutionary.io method to S-OFF the device
it was unecessary to unlock the bootloader
Click to expand...
Click to collapse
I don't even want to bother with that anymore, I am just looking for a way to get back to stock T-mobile Gingerbread ROM.
EDIT: I constantly get error 155 no matter what version of the RUU I try.
creepinm3 said:
I don't even want to bother with that anymore, I am just looking for a way to get back to stock T-mobile Gingerbread ROM.
EDIT: I constantly get error 155 no matter what version of the RUU I try.
Click to expand...
Click to collapse
ddi you relock the bootloader first?
rzr86 said:
ddi you relock the bootloader first?
Click to expand...
Click to collapse
Yes, I did
Sent from my SAMSUNG-SGH-T989 using xda premium
Hi, I really f up.
I can't install roms, and I got TMOB-101.
I tried recently flash a new rom. and didn't backed it up.
please someone send me TMOB-101 backup ot RUU.
HELP!
if you've unlocked your hboot, you need to relock it and then you can install a RUU.
http://www.htconeforum.com/forum/ht...unbrick-restore-htc-one-s-stock-relocked.html
Good luck
No ruu for me there
Sent from my HTC One S using Tapatalk 2
Do you have the TMo USA?
No. I've got t-mob101 (t-mobile Germany)
Sent from my HTC One S using Tapatalk 2
try this:
http://androidfiles.org/ruu/?dir=Ville
Tried this already...
No ruu
Sent from my HTC One S using Tapatalk 2
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
Really not?
It's a early ruu. I need the 3.16 one
Sent from my HTC One S using Tapatalk 2
lol. There isn't one from TMOB_101 and I really doubt that there ever will be one...
If you want to stick to your CID you should flash this one above and check the OTA updates. Things can be soooo easy...
If you want to go for JB you'll have to change CID to HTC__001 and flash the appropriate RUU. 3.16 will come in by OTA update.
Isn't it will brick my device? (flashing a earlier version then I got)
Sent from my HTC One S using Tapatalk 2
No, it will simply not flash (= exit with an error).
Each RUU/OTA update comes with a certain new bootloader version. Dependant on this version you can upgrade to the next higher hboot but usually not downgrade to a lower hboot. E.g. if youre on 2.15 JB you can't downgrade to 1.14 ICS by RUU anymore. But you are still able to flash custom roms based on whatever android version. The only thing here is with bootloaders > 1.09 the kernel needs to be flashed separately in fastboot mode.
That's where s-off / downgrading bootloader comes into game. As downgrading bootloader is a pain, s-off would be the way to go. For warranty purposes you will be able to restore a stock phone (locked, tampered warning removed, s-on). And if your screen is blank, it will also be blank for TMOB, so there is no need to restore stock.
Look here: http://forum.xda-developers.com/showthread.php?t=2200930
There is the "RUU_Ville_U_ICS_40_S_TMO_DE_2.38.111.10_Radio_1.09 es.50.02.07_2_10.09d.50.04L_ver2_release_287723_signed.exe"
(Android 4.04 version)
rootrider said:
No, it will simply not flash (= exit with an error).
Each RUU/OTA update comes with a certain new bootloader version. Dependant on this version you can upgrade to the next higher hboot but usually not downgrade to a lower hboot. E.g. if youre on 2.15 JB you can't downgrade to 1.14 ICS by RUU anymore. But you are still able to flash custom roms based on whatever android version. The only thing here is with bootloaders > 1.09 the kernel needs to be flashed separately in fastboot mode.
That's where s-off / downgrading bootloader comes into game. As downgrading bootloader is a pain, s-off would be the way to go. For warranty purposes you will be able to restore a stock phone (locked, tampered warning removed, s-on). And if your screen is blank, it will also be blank for TMOB, so there is no need to restore stock.
Click to expand...
Click to collapse
I've got the same Problem.
But I can't SuperCID / S-Off my Phone like here: http://forum.xda-developers.com/showthread.php?t=1671396
It just doesn't work!!!
How could I go back to a Stock ROM ??
I have really no idea
TMOB-101 ?
Which bootloader version?
rootrider said:
TMOB-101 ?
Which bootloader version?
Click to expand...
Click to collapse
hboot-2.15.0000
Golden-One said:
I've got the same Problem.
But I can't SuperCID / S-Off my Phone like here: http://forum.xda-developers.com/showthread.php?t=1671396
It just doesn't work!!!
How could I go back to a Stock ROM ??
I have really no idea
Click to expand...
Click to collapse
I can sent you a twrp nandroid backup from my phone (s4-tmobile germany)
I have backups from the 3.16.111.5.and from the latest 3.16.111.7. They are the stock roms with the supersu added.
If you recover the 3.16.111.5 nandroid backup you will take a OTA update to clean 3.16.111.7 (without supersu).
hi
Can you send me the backups too?
thank you so much!
kevin3688 said:
hi
Can you send me the backups too?
thank you so much!
Click to expand...
Click to collapse
You can find it/them here.
It's just plain stock nandroids. No root - nothing.
rootrider said:
You can find it/them here.
It's just plain stock nandroids. No root - nothing.
Click to expand...
Click to collapse
Thanks a lot!
I got the backup of stock jelly bean 4.1.2 that i did when it was released. I am using TWRP and my Hboot is unlocked and its set to s-off i also got supercid and i am rooted.
What i am wondering do i have to turn s-off to s-on to install over the air updates?
Also i replaced my splash screen, would i need to replace that with the original before the OTA will work?
Which s-on should i use to get s-off back to s-on cause i used facepalm's s-off method.
Reason i am asking is when i checked for updates i had a 15 mb update (yes i haven't checked for a long time for updates) and when i went into my Cricket store to get more screen protectors i seen they was advertising the update to 4.2.2 so i wanted to go back to stock so i can get the update.
You have noticed that there is a RUU with 4.2.2 for your device out?
old.splatterhand said:
You have noticed that there is a RUU with 4.2.2 for your device out?
Click to expand...
Click to collapse
I forgot to say my 4.1.2 is stock.
Is that untouched and full stock still odexed?
Why is it an exe?
And do i just flash it in recovery with out doing all that extra work of turn stuff on then off again lol.
Edit: Sorry i just never used an ruu before.
The RUU runs on your computer like a program. Hence the .exe
HTC One SV - K2_PLC_CL
It wipes all your data, but S-off will remain.