Database Develop

Help reverting back to stock.

I'm trying to unroot and revert back to stock and having a bit of a nightmare. I didn't make my own nandroid backup before I installed a customer rom (lesson learnt), so I downloaded the one I needed off a thread on here (UK Unbranded CWM). Every time I try to flash the nandroid I get an MD5 sum mismatch error. I've tried various methods people have suggested across the internet to no joy. Is there a stock .401 rom knocking about? I saw mikes thread but that has the latest 4.22 stock rom, is there one for an older version? Thanks.

if you have s-off you should
1)download this ruu http://androidfiles.org/ruu/getdownload.php?file=M7/RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
2)lock your bootloader (use command "fastboot oem lock")
3)run ruu
4)done

Rayskull said:
if you have s-off you should
1)download this ruu http://androidfiles.org/ruu/getdownload.php?file=M7/RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
2)lock your bootloader (use command "fastboot oem lock")
3)run ruu
4)done
Click to expand...
Click to collapse
Thank you very much. I've managed to restore from a nandroid backup and I've installed stock recovery, I'm now installing a OTA as prompted by the device. As I now have stock rom, recovery and no root access, gain I still use revone to lock bootloader and go S-On? The reason I want to use revone is so that it doesn't say 're-locked'. If so, how? Thanks for all your help.

if you recieved the OTA i think there's no need to relock the bootloader, but if you want to... so yes, use revone.
"./revone -l" to lock it (no relocked warning)
if you recieve the tampared warning use:
"./revone -t"
cheers

maj4.2.2 ,revone doesn't works!

hello. i've just having 4.2.2 ota. i have unlocked bootloader . but revone doesn't work to s-off, allways "segmentation fault (core dumped) when using command " ./revone -P". how to do to re "locked" without revone ??

Fastboot oem lock

gunnyman said:
Fastboot oem lock
Click to expand...
Click to collapse
it's for re s-on that ,i am allready in s-on , i want to "locked" hboot...arggg no flash ,no Tools ....!!! :-s
i have try my usual RUU and it's not compatible with the 4.2.2 ...i wanted to downgrade and use revone to re "locked" (./revone -l -t )... and re- ota with 4.2.2 cleanly but....

absynte said:
it's for re s-on that ,i am allready in s-on , i want to "locked" hboot...arggg no flash ,no Tools ....!!! :-s
i have try my usual RUU and it's not compatible with the 4.2.2 ...i wanted to downgrade and use revone to re "locked" (./revone -l -t )... and re- ota with 4.2.2 cleanly but....
Click to expand...
Click to collapse
You can't s-off if you took the 4.2.2 ota. Revone doesn't work on that hboot.

[Q] How to go back to stock with HBoot 1.54 and OS 2.24.206.7

Hi everyone.
First of all, I'd like to apologise for creating a new thread about a thing that has been discussed here before. Since the problem hasn't been solved yet and I haven't unrooted a phone before I hope someone will guide me.
The phone: HTC One with Android 4.2.2
Carrier: O2 UK
CID: O2_001
S-on
HBoot: 1.54
OS: 2.24.206.7
I rooted my phone a couple of weeks ago. I unlocked the bootloader on the htcdev site and flashed the clockworkmod recovery. I like the HTC version of Android so I didn't flash a custom ROM. Last week I was notified that an OTA was available. I thought I'd only need a stock recovery to unroot my phone. So I started looking for it but I can't find it anywhere. There are no RUUs for my system. Nor Nandroid backups.
So my first question is if anyone has got a Nandroid backup of Android 4.2.2?
If not, can I use a different version of firmware? Some people suggested that 2.24.401.8 and 2.24.206.7 are actually the same.
I also found flashable zips of Android 4.1.2 but I know they don't work with hboot 1.54 and will break the touchscreen drivers so I'll need an otg cable. I don't like this solution. I'll do it when everything else fails.
Have you got any other suggestions? Or a step-by-step guide?
Cheers

Hey mate
I made a guide earlier today about returning to stock 02
http://forum.xda-developers.com/showthread.php?t=2519259
Try these steps and let me know how you get on
---------- Post added at 11:01 PM ---------- Previous post was at 10:59 PM ----------
zuchs said:
Hi everyone.
First of all, I'd like to apologise for creating a new thread about a thing that has been discussed here before. Since the problem hasn't been solved yet and I haven't unrooted a phone before I hope someone will guide me.
The phone: HTC One with Android 4.2.2
Carrier: O2 UK
CID: O2_001
S-on
HBoot: 1.54
OS: 2.24.206.7
I rooted my phone a couple of weeks ago. I unlocked the bootloader on the htcdev site and flashed the clockworkmod recovery. I like the HTC version of Android so I didn't flash a custom ROM. Last week I was notified that an OTA was available. I thought I'd only need a stock recovery to unroot my phone. So I started looking for it but I can't find it anywhere. There are no RUUs for my system. Nor Nandroid backups.
So my first question is if anyone has got a Nandroid backup of Android 4.2.2?
If not, can I use a different version of firmware? Some people suggested that 2.24.401.8 and 2.24.206.7 are actually the same.
I also found flashable zips of Android 4.1.2 but I know they don't work with hboot 1.54 and will break the touchscreen drivers so I'll need an otg cable. I don't like this solution. I'll do it when everything else fails.
Have you got any other suggestions? Or a step-by-step guide?
Cheers
Click to expand...
Click to collapse
If you have any difficulties just let me know but my steps helped me return completely to stock

How come I haven't found your post?! I'll give it a go straight away.
Thanks a lot.
Sent from my HTC One using xda app-developers app

zuchs said:
How come I haven't found your post?! I'll give it a go straight away.
Thanks a lot.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Lol I only made the post today cos I was having the same difficulties and it took my a while to obtain s on again without tampered or warning messages
Good luck with returning to stock I posted as many links for you to download and you shouldn't need to use the otg cable

stovie_steve said:
Lol I only made the post today cos I was having the same difficulties and it took my a while to obtain s on again without tampered or warning messages
Good luck with returning to stock I posted as many links for you to download and you shouldn't need to use the otg cable
Click to expand...
Click to collapse
Haha. That explains everything. Thanks once again.

I have got a few questions:
1. There is no rumrunner for 2.24.206.7. Which one do I use? 2.24.401.8? Or it doesn't matter?
2. Do I have to remove the "TAMPERED" flag?
3. How do I downgrade hboot? Do I flash it using fastboot?
4. The version of the missing apps is different. Will they install?
Thanks

zuchs said:
I have got a few questions:
1. There is no rumrunner for 2.24.206.7. Which one do I use? 2.24.401.8? Or it doesn't matter?
2. Do I have to remove the "TAMPERED" flag?
3. How do I downgrade hboot? Do I flash it using fastboot?
4. The version of the missing apps is different. Will they install?
Thanks
Click to expand...
Click to collapse
1. For that version, you can use the 2.24.401.8, but before you do so please make a nandroid backup as it has been reported with some people to cause the WiFi to stop working. After you run rumrunner with this version you can restore your stock backup again
2. To downgrade the hboot, you have to download from the link in the guide I posted to you and edit the android-info.txt. This is done by opening the .rar file (NOT EXTRACTING IT!) and opening the text file. Change the model ID to PN710000. Reboot your phone into fastboot. Run the command fastboot writecid HTC__001 and then do fastboot oem rebootRUU. You then flash the hboot here using fastboot flash zip name_of_file_with_no_spaces.zip
The flash is then completed by typing fastboot reboot-bootloader. You can check the hboot there
3. By doing the above, run the RUU on my guide and then follow the steps to run the backup nandroid etc and you should be fine mate

stovie_steve said:
1. For that version, you can use the 2.24.401.8, but before you do so please make a nandroid backup as it has been reported with some people to cause the WiFi to stop working. After you run rumrunner with this version you can restore your stock backup again
2. To downgrade the hboot, you have to download from the link in the guide I posted to you and edit the android-info.txt. This is done by opening the .rar file (NOT EXTRACTING IT!) and opening the text file. Change the model ID to PN710000. Reboot your phone into fastboot. Run the command fastboot writecid HTC__001 and then do fastboot oem rebootRUU. You then flash the hboot here using fastboot flash zip name_of_file_with_no_spaces.zip
The flash is then completed by typing fastboot reboot-bootloader. You can check the hboot there
3. By doing the above, run the RUU on my guide and then follow the steps to run the backup nandroid etc and you should be fine mate
Click to expand...
Click to collapse
What about the flag? Do I have to remove the "TAMPERED" flag?
BTW, I ran rumrunner before I read your reply. I didn't make a backup. The wifi isn't working. Any ideas?

zuchs said:
What about the flag? Do I have to remove the "TAMPERED" flag?
BTW, I ran rumrunner before I read your reply. I didn't make a backup. The wifi isn't working. Any ideas?
Click to expand...
Click to collapse
Was rumrunner successful in achieving S-OFF? If so then it doesnt matter that the WiFi doesnt work, we can fix it
Make sure USB debugging is on - to do this go to your build number under settings and tap until it says you are now a developer
Go to developer settings and click the enable USB debugging option
To LOCK the bootloader:
Open command prompt
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
After this carry on with changing the CID to HTC__032 and flashing the hboot I told you about. Then run the RUU from here http://d-h.st/Gt8 from fasboot
After that you will be Android 4.1.2 hboot 1.44 and completely stock
---------- Post added at 12:56 AM ---------- Previous post was at 12:51 AM ----------
zuchs said:
What about the flag? Do I have to remove the "TAMPERED" flag?
BTW, I ran rumrunner before I read your reply. I didn't make a backup. The wifi isn't working. Any ideas?
Click to expand...
Click to collapse
For tampered - http://forum.xda-developers.com/showthread.php?t=2477792

stovie_steve said:
Was rumrunner successful in achieving S-OFF? If so then it doesnt matter that the WiFi doesnt work, we can fix it
Make sure USB debugging is on - to do this go to your build number under settings and tap until it says you are now a developer
Go to developer settings and click the enable USB debugging option
To LOCK the bootloader:
Open command prompt
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
After this carry on with changing the CID to HTC__032 and flashing the hboot I told you about. Then run the RUU from here http://d-h.st/Gt8 from fasboot
After that you will be Android 4.1.2 hboot 1.44 and completely stock
---------- Post added at 12:56 AM ---------- Previous post was at 12:51 AM ----------
For tampered - http://forum.xda-developers.com/showthread.php?t=2477792
Click to expand...
Click to collapse
Yes. It was successful.
Scotty1223 used a slighly different echo command:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
Why did you use a different one?

zuchs said:
Yes. It was successful.
Scotty1223 used a slighly different echo command:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
Why did you use a different one?
Click to expand...
Click to collapse
The one you are referring to is for tampered yes
The one I gave you was for locking your bootloader
Please read the guide my friend, I tried to make it as straightforward as possible I'm heading off to bed here anyways but I'll be on fairly early again in the morning to give you a hand again if you don't mind, but crack away at that guide and see how you get on!

stovie_steve said:
The one you are referring to is for tampered yes
The one I gave you was for locking your bootloader
Please read the guide my friend, I tried to make it as straightforward as possible I'm heading off to bed here anyways but I'll be on fairly early again in the morning to give you a hand again if you don't mind, but crack away at that guide and see how you get on!
Click to expand...
Click to collapse
OK Thank you very much. You've been more than helpful, I'll let you know if I am successful. Cheers.

zuchs said:
OK Thank you very much. You've been more than helpful, I'll let you know if I am successful. Cheers.
Click to expand...
Click to collapse
Just wondered how you got on with returning to stock?

stovie_steve said:
Just wondered how you got on with returning to stock?
Click to expand...
Click to collapse
I'm sure you got my message but just to close the thread I'd like to confirm that I successfully went back to stock.
The screenshot below:
Screenshot

zuchs said:
I'm sure you got my message but just to close the thread I'd like to confirm that I successfully went back to stock.
The screenshot below:
Screenshot
Click to expand...
Click to collapse
Yaaaay! Well done

[Q] Can't unlock HTC One GPE that is RELOCKED

I bough a GPE HTC One from the Play store. I used HTC Dev to unlock it, had enjoyed custom roms and recoveries. I wanted to learn how to revert back to stock so before the 4.4 OTA update I relocked the bootloader and restored a stock recovery (not my own original).
I received the 4.4 OTA update yesterday and I attempted to unlock the bootloader once more. I used the original bin file and went through the steps to do it again but am met with the same results. I can at times get a successful unlock command in terminal, but not the screen that is supposed to appear and unlock the device.
I've seen some threads that sort of have the same problem but none that have resolutions that work for me. I've attempted flashing RUU's but am always met with signature verification failures. I've tried fastboot oem unlock but that doesn't work either.
Hoping someone might have an idea.
TAMPERED
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-3.58.1700.5
eMMC-boot 2048MB
Nov 21 2013, 20:19:24.0
cid: GOOGL001
Misc:
HTC Sync manager installed then uninstalled
latest Android SDK installed for adb
debugging mode on
usb 2.0 on windows 7 x86

Hopefully someone with actual knowledge will come to help you, but why don't you try to S-off? that will give you more solution options.

Arjen_Arg said:
Hopefully someone with actual knowledge will come to help you, but why don't you try to S-off? that will give you more solution options.
Click to expand...
Click to collapse
From what I've been able to determine I'm unable to achieve S-OFF with HBOOT 1.54, or else I definitely would.

There are no RUU for GPE. The conversion RUU is not properly signed and was made from a system dump.
The GPE should be unlockable without a token or using htc dev.
fastboot oem unlock
what do you get?
You can't S-OFF on the GPE rom. you would have to flash a sense rom and then use rumrunner. You can't flash a different rom without unlocking and flashing a custom recovery...
msw141 said:
I bough a GPE HTC One from the Play store. I used HTC Dev to unlock it, had enjoyed custom roms and recoveries. I wanted to learn how to revert back to stock so before the 4.4 OTA update I relocked the bootloader and restored a stock recovery (not my own original).
I received the 4.4 OTA update yesterday and I attempted to unlock the bootloader once more. I used the original bin file and went through the steps to do it again but am met with the same results. I can at times get a successful unlock command in terminal, but not the screen that is supposed to appear and unlock the device.
I've seen some threads that sort of have the same problem but none that have resolutions that work for me. I've attempted flashing RUU's but am always met with signature verification failures. I've tried fastboot oem unlock but that doesn't work either.
Hoping someone might have an idea.
TAMPERED
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-3.58.1700.5
eMMC-boot 2048MB
Nov 21 2013, 20:19:24.0
cid: GOOGL001
Misc:
HTC Sync manager installed then uninstalled
latest Android SDK installed for adb
debugging mode on
usb 2.0 on windows 7 x86
Click to expand...
Click to collapse

That's old information. There has been an S-Off exploit for 1.54 for over a month. I've done it on a GPE just like yours. Search for Rumrunner S-Off.
---------- Post added at 07:43 PM ---------- Previous post was at 07:35 PM ----------
ipfreelytech said:
You can't S-OFF on the GPE rom. you would have to flash a sense rom and then use rumrunner. You can't flash a different rom without unlocking and flashing a custom recovery...
Click to expand...
Click to collapse
This is wrong. You CAN S-OFF a GPE. Although you need root access or unlocked bootloader.
Do you have root?
Rumrunner S-Off http://rumrunner.us/

edit. answered in post above

ipfreelytech said:
There are no RUU for GPE. The conversion RUU is not properly signed and was made from a system dump.
The GPE should be unlockable without a token or using htc dev.
fastboot oem unlock
what do you get?
You can't S-OFF on the GPE rom. you would have to flash a sense rom and then use rumrunner. You can't flash a different rom without unlocking and flashing a custom recovery...
Click to expand...
Click to collapse
I try unlock but don't succeed. This is the result:
[PG_ERROR] htc_pg_part_traverse(839):
invalid traverse range
[PG_ERROR] htc_pg_part_read(1092):
htc_pg_part_traverse failed
[DISPLAY_ERR] sp_custom partition: unlock_disp_bu:img_buf read error!
[DISPLAY_ERR] Can not load custom splash!
Loading custom splash failed!
OKAY [ 0.537s]
finished. total time: 0.538s

Arjen_Arg said:
Do you have root?
Click to expand...
Click to collapse
No root, sadly. And probably can't get it with locked bootloader and s-on either.

interesting.
Last night just for fun I relocked the bootloader on my GPE converted AT&T one. I then attempted to unlock using fastboot oem unlock and got the exact same results. I suspected it had to do with my phone being converted instead of legit GPE and also having a custom splash screen.
I'm s-off so I just unlocked using a a few quick commands while booted.
Try re-flashing the firmware.zip from the 4.4 ota for good measure. that will re-write your hboot and recovery and other firmwares.
you can download here: https://mega.co.nz/#!DV0UEbBY!Vv6H4Ebf8WRCXrKwe5TGDUQqnvNk-9FiSjOvhjXAQvE
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 fimrware.zip
fastboot reboot-bootloader
then attempt unlock again.
msw141 said:
I try unlock but don't succeed. This is the result:
[PG_ERROR] htc_pg_part_traverse(839):
invalid traverse range
[PG_ERROR] htc_pg_part_read(1092):
htc_pg_part_traverse failed
[DISPLAY_ERR] sp_custom partition: unlock_disp_bu:img_buf read error!
[DISPLAY_ERR] Can not load custom splash!
Loading custom splash failed!
OKAY [ 0.537s]
finished. total time: 0.538s
Click to expand...
Click to collapse

ipfreelytech said:
Try re-flashing the firmware.zip from the 4.4 ota for good measure. that will re-write your hboot and recovery and other firmwares.
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 fimrware.zip
fastboot reboot-bootloader
then attempt unlock again.
Click to expand...
Click to collapse
Well the firmware flash worked just fine. But then I tried flashboot oem unlock and I got the same error as documented earlier. I even tried the HTCdev method again, got a successful result but no unlock screen.
So I'm still stuck on relocked. But I'm encouraged that your file was able to flash with no error. Do you think there might be more files I could attempt to flash in that manner that could help?

ipfreelytech said:
interesting.
Last night just for fun I relocked the bootloader on my GPE converted AT&T one. I then attempted to unlock using fastboot oem unlock and got the exact same results. I suspected it had to do with my phone being converted instead of legit GPE and also having a custom splash screen.
I'm s-off so I just unlocked using a a few quick commands while booted.
Try re-flashing the firmware.zip from the 4.4 ota for good measure. that will re-write your hboot and recovery and other firmwares.
you can download here: https://mega.co.nz/#!DV0UEbBY!Vv6H4Ebf8WRCXrKwe5TGDUQqnvNk-9FiSjOvhjXAQvE
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 fimrware.zip
fastboot reboot-bootloader
then attempt unlock again.
Click to expand...
Click to collapse
Hi @ipfreelytech
If fastboot oem unlock didn't work for you, how did you unlock the bootloader?

SaHiLzZ said:
Hi,
If fastboot oem unlock didn't work for you, how did you unlock the bootloader?
Click to expand...
Click to collapse
When I first got my phone I unlocked via that HTCdev method by betting the unlock_code.bin file and flashing it. I wasn't aware until today that there was a different method for GPE that didn't require that. The problem now is that the oem unlock doesn't work, and HTCdev method says it works but doesn't complete.

Yeah this a new issue that we are seeing being reported more and more after 4.4 GPE update.. Unfortuantely no fix yet.

SaHiLzZ said:
Yeah this a new issue that we are seeing being reported more and more after 4.4 GPE update.. Unfortuantely no fix yet.
Click to expand...
Click to collapse
OK, understood. What do you suggest I keep an eye out for on the forums?
A new S-OFF method for 1.54 with a locked bootloader...a new firmware update where it might work again...or updated drivers for the hardware/adb? Appreciate your input.

adb shell
su
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
more info here: http://forum.xda-developers.com/showthread.php?t=2470340
this only works if you're s off and have root
SaHiLzZ said:
Hi @ipfreelytech
If fastboot oem unlock didn't work for you, how did you unlock the bootloader?
Click to expand...
Click to collapse

Ah Ok, that is what Guru's bootloader zip is based on. Thanks!

ipfreelytech said:
adb shell
su
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
more info here: http://forum.xda-developers.com/showthread.php?t=2470340
this only works if your s off and have root
Click to expand...
Click to collapse
This method that you used to unlock and "relocked" phone, is there any way to do it with S-On? I had previously rooted, and am now stuck, as the others (I have been posting on other threads).
I'm wondering, hoping that there is line code like this one that would allow for us to recover our phones....

doubtful. s-off is required because your modifying a "black box" partition. The solutions used to gain s-off in the first place require using an exploit to write to that partition. What i posted is just directly modifying it using dd.
elisaw99 said:
This method that you used to unlock and "relocked" phone, is there any way to do it with S-On? I had previously rooted, and am now stuck, as the others (I have been posting on other threads).
I'm wondering, hoping that there is line code like this one that would allow for us to recover our phones....
Click to expand...
Click to collapse

SaHiLzZ said:
Yeah this a new issue that we are seeing being reported more and more after 4.4 GPE update.. Unfortuantely no fix yet.
Click to expand...
Click to collapse
Hi I'm replying to you on this original thread instead of starting a new one. I received the 4.4.2 OTA update this morning and I still cannot unlock bootloader, getting the same error messages as documented earlier in this thread.
I am checking to see if you've heard of any success stories for people on a stock GPE HTC One (s-on, relocked, no root) getting their bootloader to unlock after 4.4 or 4.4.2. I've checked the forums regularly but most other people seem to have root, s-off, or customer recovery which I have neither of.

msw141 said:
Hi I'm replying to you on this original thread instead of starting a new one. I received the 4.4.2 OTA update this morning and I still cannot unlock bootloader, getting the same error messages as documented earlier in this thread.
I am checking to see if you've heard of any success stories for people on a stock GPE HTC One (s-on, relocked, no root) getting their bootloader to unlock after 4.4 or 4.4.2. I've checked the forums regularly but most other people seem to have root, s-off, or customer recovery which I have neither of.
Click to expand...
Click to collapse
Im getting this same issue after updating to 4.4.2 after i got my phone back from repair. It is completely stock now and when i try to unlock the phone it wont show the screen that asks me if im sure i want to unlock my phone, which is the last step on the htcdev site.
Im thinking its a kitkat issue.

HBOOT 1.56 how to S-on and LOCK bootloader?

i know revone doesnt work to S-oFF, but can i revert back to S-on and remove "RELOCKED" on hboot 1.56 KITKAT 4.4.2?
or is the only way running a RUU, (then running revone) than updating to KITKAT with S-ON and ***RELOCKED*** removed?

For_itembine said:
i know revone doesnt work to S-oFF, but can i revert back to S-on and remove "RELOCKED" on hboot 1.56 KITKAT 4.4.2?
or is the only way running a RUU, (then running revone) than updating to KITKAT with S-ON and ***RELOCKED*** removed?
Click to expand...
Click to collapse
To get your bootloader back to LOCKED, first you need to unlock the bootloader and flash CWM. then flash this zip in CWM:
http://www.htc1guru.com/guides/guru-bootloader-reset/
Choose the option so set the bootloader back to LOCKED. You can also remove TAMPERED using this tool
To go back to S-ON, after setting the bootloader back to LOCKED, enter fastboot mode and type this in Command Prompt without the inverted comma,
"fastboot oem writesecureflag 3"
then follow the on-screen instructions to S-ON. reboot 3 times after the procedure
Feel free to ask any doubts and hit the THANKS button if I helped you

S-on on 1.55/56 hboot may bring back tampered text in bootloader. You have to be on 1.44 hboot to do it. Why do you need to s-on. Its not recommended
sent from my mobile device

raghav kapur said:
To get your bootloader back to LOCKED, first you need to unlock the bootloader and flash CWM. then flash this zip in CWM:
http://www.htc1guru.com/guides/guru-bootloader-reset/
Choose the option so set the bootloader back to LOCKED. You can also remove TAMPERED using this tool
To go back to S-ON, after setting the bootloader back to LOCKED, enter fastboot mode and type this in Command Prompt without the inverted comma,
"fastboot oem writesecureflag 3"
then follow the on-screen instructions to S-ON. reboot 3 times after the procedure
Feel free to ask any doubts and hit the THANKS button if I helped you
Click to expand...
Click to collapse
given link expired...
Please provide the alternate
Thank you

For_itembine said:
i know revone doesnt work to S-oFF, but can i revert back to S-on and remove "RELOCKED" on hboot 1.56 KITKAT 4.4.2?
or is the only way running a RUU, (then running revone) than updating to KITKAT with S-ON and ***RELOCKED*** removed?
Click to expand...
Click to collapse
Yes, revone -l will set back to LOCKED state on any hboot version. Or simply this command in a terminal or adb shell will do it:
Code:
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
Do not go back S-ON, just don't.

Here you go buddy:
http://forum.xda-developers.com/showthread.php?t=2541082
Read all instructions before beginning. Make sure you have the original ADB drivers and the HTC provided drivers coming from HTC sync. Make sure HTC sync is then uninstalled. Make sure your firewall and antivirus is disabled through the process. Make sure you follow all directions to a T. Done this twice following this guide.