Database Develop

Going back to S-on with Hboot 1.54

Hi Guys,
I'm trying to get back to 100% stock so I can send my phone back for replacement/repair. There was no RUU so I used some kindly donated nandroid back ups and OTA firmware to get back to what should be my current stock 2.29.980.2 (Australian Unbranded HTC__039). Ive got stock recovery back on and OTA's are working. I'm still S-Off and boot loader unlocked.
The last think i need to do is get S-on and relock the bootloader. But in flashing the current firmware, HBoot is at 1.54.
Before I do any brash, does anyone know if revone one will still work to allow me to relock the bootloader and S-on?
If not will I have to downgrade Hboot to 1.44 and get S-On back on then reflash the firmware to upgrade HBoot back to 1.54?
I've also read that if there is anything other than stock HBoot and S-On you can brick the phone. But I take if the Hboot has upgraded from the OTA firmware this should be fine?
Thanks

Ali Baba 84 said:
Hi Guys,
I'm trying to get back to 100% stock so I can send my phone back for replacement/repair. There was no RUU so I used some kindly donated nandroid back ups and OTA firmware to get back to what should be my current stock 2.29.980.2 (Australian Unbranded HTC__039). Ive got stock recovery back on and OTA's are working. I'm still S-Off and boot loader unlocked.
The last think i need to do is get S-on and relock the bootloader. But in flashing the current firmware, HBoot is at 1.54.
Before I do any brash, does anyone know if revone one will still work to allow me to relock the bootloader and S-on?
If not will I have to downgrade Hboot to 1.44 and get S-On back on then reflash the firmware to upgrade HBoot back to 1.54?
I've also read that if there is anything other than stock HBoot and S-On you can brick the phone. But I take if the Hboot has upgraded from the OTA firmware this should be fine?
Thanks
Click to expand...
Click to collapse
noooooooooooooo, don't s-on with 1.54.

criszz said:
noooooooooooooo, don't s-on with 1.54.
Click to expand...
Click to collapse
You might want to be a bit more helpful and actually tell him why not

I would also advise against reverting to S on, because you won't be able to regain S off again, at least currently with 1.54 hboot.
If you wish to send for repair, my advice would be ensure you have stock recovery and stock Rom.
Use revone to remove tampered, and also relock bootloader .
No real need to revert to S on, as Soff doesn't indicate that you tampered with your device as a small number of HTC One were sold with S off
Sent from my HTC One using xda app-developers app

Ali Baba 84 said:
Hi Guys,
I'm trying to get back to 100% stock so I can send my phone back for replacement/repair. There was no RUU so I used some kindly donated nandroid back ups and OTA firmware to get back to what should be my current stock 2.29.980.2 (Australian Unbranded HTC__039). Ive got stock recovery back on and OTA's are working. I'm still S-Off and boot loader unlocked.
The last think i need to do is get S-on and relock the bootloader. But in flashing the current firmware, HBoot is at 1.54.
Before I do any brash, does anyone know if revone one will still work to allow me to relock the bootloader and S-on?
If not will I have to downgrade Hboot to 1.44 and get S-On back on then reflash the firmware to upgrade HBoot back to 1.54?
I've also read that if there is anything other than stock HBoot and S-On you can brick the phone. But I take if the Hboot has upgraded from the OTA firmware this should be fine?
Thanks
Click to expand...
Click to collapse
I am on the same boat with you. unbranded Aussie One..
I had my own backup 1.29.980.17 from TWRP and restoring from my backup made my screen not working at all..
I have 1.54 hboot as well. Does 1.54 hboot and 4.1.2 doesnt work together? Isnt backup from xda is also 4.1.2 as well?
Sorry about asking question in your thread, but I just want to do same thing like you and I failed..

paul_59 said:
I would also advise against reverting to S on, because you won't be able to regain S off again, at least currently with 1.54 hboot.
If you wish to send for repair, my advice would be ensure you have stock recovery and stock Rom.
Use revone to remove tampered, and also relock bootloader .
No real need to revert to S on, as Soff doesn't indicate that you tampered with your device as a small number of HTC One were sold with S off
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I didnt think revone was compatable with 4.2.2?
i too am needing to remove TAMPERED from mine on 4.2.2 i have the stock rom and recovery now.

rotten.monkey said:
I didnt think revone was compatable with 4.2.2?
i too am needing to remove TAMPERED from mine on 4.2.2 i have the stock rom and recovery now.
Click to expand...
Click to collapse
It says tampered because you have some unsigned software installed. Probably hboot or recovery.

Unlocking HTC One, few Q's please

I attempted to flash my UK Vodafone HTC One as I wanted Android Revolutiion HD ROM on my phone, i've sort of got half way and i'm not sure how to continue (or if I should)
So i've unlocked the bootloader, and flashed the clockwork recovery so my phone now says *TAMPERED*
It is still S-On and is on HBOOT 1.54 - having read around this cannot be done, right?
Also, one other quick question. If I ever wanted to go back to complete stock, how can I do this? I can't seem to find the RUU for my phone, and how would I remove *TAMPERED*
Here is my radio version: 4A.17.3250.14
ANY HELP IS MUCH APPRECIATED GUYS! I've rooted other HTC's before but not the One yet

You can't go S-Off on 1.54
You could just flash the stock rom and stock recovery, which has the same result as an RUU/
Tampered is removed when you lock, but you can't remove -relocked- without S-Off

Thanks for your reply.
So what you're saying is in the situation I am in at the moment, I can't flash the ARHD ROM to my phone without being S-OFF first?
It's basically just a waiting game for S-OFF to become available for 1.54 and then I could just flash the stock ROM and recovery and then S-OFF to remove the TAMPERED or RELOCKED.
This will be just incase id ever need to send the phone off to Vodafone for whatever reason

[Q] Question regarding repairs...

Ok so I bought my phone from O2 so it was completely stock and CID was O2___001. I s-off'd using rumrunner, then downgraded my hboot to stock 1.44 and ran revone to remove tampered and 're lock boot loader. I changed my CID to HTC__032 and flashed a RUU to subsequently update to sense 5.5 and the latest firmware. The hboot has not been flashed with a modified version as I didn't get the red text after downgrading and then running revone and RUU
My question is if I send my phone into HTC for repairs in the future should I keep the phone as is or try and revert to stock O2? The phone is now purely stock and unbranded. I prefer HTC repair to O2 anyway. The bootloader reads locked and it's s-off
Thanks!

Anyone ? Better to stay unbranded and full stock or carrier branded full stock for repairs? Can HTC know my phone was carrier branded originally?

[Q] Just reverted to stock, safe to S-ON?

So my phone was S-OFF, superCID, custom firmware, running ARHD with TWRP recovery. I carried out the procedure to revert to 100% stock, I have a Rogers HTC One but a Rogers RUU doesn't exist, however I was able to get OTA updates after reverting to stock so I'm assuming the hboot, bootloader, recovery, stock ROM are all Rogers based.
However, when reverting to stock, I used an AT&T RUU to go down to 1.26 firmware and then Rogers OTA updates took me from 1.26 to 1.29 to finally 3.22 firmware. Everything at this point is stock and hopefully Rogers based, only modification that remains is S-OFF.
I need to S-ON for warranty purposes, I know how to S-ON, but I was wondering if it safe to S-ON considering I used a non-Rogers RUU to downgrade in the first place. I read somewhere that if I try to S-ON after using RUU that isn't the same as my carrier I will brick my phone, which is something I don't want to do. So is it safe to S-ON or am I at risk of bricking my phone?
My bootloader is locked, no tampered flag, hboot 1.55, CID is no longer superCID but ROGER001 (specific to my carrier)

Your good
Ali812 said:
So my phone was S-OFF, superCID, custom firmware, running ARHD with TWRP recovery. I carried out the procedure to revert to 100% stock, I have a Rogers HTC One but a Rogers RUU doesn't exist, however I was able to get OTA updates after reverting to stock so I'm assuming the hboot, bootloader, recovery, stock ROM are all Rogers based.
However, when reverting to stock, I used an AT&T RUU to go down to 1.26 firmware and then Rogers OTA updates took me from 1.26 to 1.29 to finally 3.22 firmware. Everything at this point is stock and hopefully Rogers based, only modification that remains is S-OFF.
I need to S-ON for warranty purposes, I know how to S-ON, but I was wondering if it safe to S-ON considering I used a non-Rogers RUU to downgrade in the first place. I read somewhere that if I try to S-ON after using RUU that isn't the same as my carrier I will brick my phone, which is something I don't want to do. So is it safe to S-ON or am I at risk of bricking my phone?
My bootloader is locked, no tampered flag, hboot 1.55, CID is no longer superCID but ROGER001 (specific to my carrier)
Click to expand...
Click to collapse
If you have changed your CID back to your carrier specific code you should be OK.
However, with the 4.4 update, there have been a few issues with the Bootloader not unlocking again, if you are sending your phone back under warranty for repair or replacement then your good to S-On, if you just want to set S-on for the hell of it (like me) I would hold fire for now.
Its will be your only remaining access to unlock the phone in one way or another.

Ali812 said:
I read somewhere that if I try to S-ON after using RUU that isn't the same as my carrier I will brick my phone, which is something I don't want to do. So is it safe to S-ON or am I at risk of bricking my phone?
Click to expand...
Click to collapse
Like I said, no bricks involved, but read below too.
zeushacker said:
if you are sending your phone back under warranty for repair or replacement then your good to S-On
Click to expand...
Click to collapse
if he tries to go s-off to s-on on hboot 1.55, then there is a high probability, that after a few reboots "tamper detected - rebooting" -> and the TAMPERED sign is back.
I wrote the guide in a specific order 1, then 2, then 3, etc, because of that reason.
If the OP wants to give it a shot, he can go ahead, maybe the "tamper detected" won't happen; if it does, he will have to s-off using rumrunner, and start the procedure again.

s-on is not needed on waranty, there are always some devices shiped from factory with s-off. my advice is to keep s-off.

Need to go back to stock. Am I missing any steps? s-off

First I need to flash a normal hboot and then run a RUU on my phone.
I remember reading once that using an engineered hboot and then trying to return to stock can brick the phone
After running the RUU
all I have to do is lock my bootloader
and then s-on my phone right?

The order looks correct to me, however, if you just want to run a stock ROM, then you only need to flash the hboot and then run the RUU. You only need to lock the bootloader and s-on if you never plan to run a custom or rooted ROM. Personally, I would only do that if you are selling the phone. I wrote a guide for s-off members to run the RUU if you'd like to follow it: http://forum.xda-developers.com/spr...de-reset-phone-using-ruu-htcfastboot-t2876110

I am returning the phone to htc for repair hence I need it completely wiped