Hi all,
As the title suggests I need to get my HTC One back to S-On to send it back for repair, as I'm from Australia there is no RUU available for my Carrier but I have flashed back to stock using a Guru Nandroid, currently it's Bootloader is locked it's CID is OPTUS001 (default) and HBoot 1.55 S-Off which I need to get back to on and it's had it's latest OTA installed.
Earlier today I did achieve S-Off and locked but ended up with the tamper flag above locked which obviously couldn't be returned like that.
At the moment I am wondering if I need to downgrade just HBoot to 1.44 so I can S-On again but I'm worried it will show tampered again after I S-On like it did before, now in further if this is the only way to do it how can I get HBoot 1.55 back in after I S-On, I haven't found any firmware downloads out there at all specific to my device.
Thanks in advance for any help.
Just leave it s off its not a problem. As long as tampered is gone and boot loader is locked that is fine
Sent from my HTC One using XDA Premium 4 mobile app
Ok thank you for the reply, I have tried so many different things today and to be honest I'm surprised it's not bricked doing some of the things I have done, cheers.
Sent from my HTC One using Tapatalk Pro
Going from s off to s on is actually one of the easiest ways to brick your phone if your not careful. There really is no need. Some phones actually come out of the factory s off. And with warranty repairs I've heard of plenty of people with custom roms and unlocked bootloaders get it fixed no problem. Yours sounds fine
Sent from my HTC One using XDA Premium 4 mobile app
Sojourner353 said:
Hi all,
As the title suggests I need to get my HTC One back to S-On to send it back for repair, as I'm from Australia there is no RUU available for my Carrier but I have flashed back to stock using a Guru Nandroid, currently it's Bootloader is locked it's CID is OPTUS001 (default) and HBoot 1.55 S-Off which I need to get back to on and it's had it's latest OTA installed.
Earlier today I did achieve S-Off and locked but ended up with the tamper flag above locked which obviously couldn't be returned like that.
At the moment I am wondering if I need to downgrade just HBoot to 1.44 so I can S-On again but I'm worried it will show tampered again after I S-On like it did before, now in further if this is the only way to do it how can I get HBoot 1.55 back in after I S-On, I haven't found any firmware downloads out there at all specific to my device.
Thanks in advance for any help.
Click to expand...
Click to collapse
delete quote
Related
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.
Hello everyone,
I have several issues with my HTC One and so I've got to send it to HTC. But for this I have to reset it back to stock so I have the right to claim warranty. Now I proceeded every step from using a RUU and setting the locked state to installing every OTA update. But now the only thing that has to be removed is the S OFF. I heard that you can instantly brick your device if you "fastboot writesecureflag 3" and you have a custom hboot. So now I have the stock hboot 1.55 recieved OTA. Is it secure the turn my phone back S ON? Or do I have to downgrade the hboot 1.44?
Don't go S-On. S-Off won't void your warranty
Sent from my Nexus 10 using Tapatalk 4
altimax98 said:
Don't go S-On. S-Off won't void your warranty
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
really? It would just.. be ... f***ing awesome And if they say s off voided my warranty i'm gonna punch them... thanks..
And is it true that some devices are shipped s off by mistake?
LibertyMarine said:
really? It would just.. be ... f***ing awesome And if they say s off voided my warranty i'm gonna punch them... thanks..
And is it true that some devices are shipped s off by mistake?
Click to expand...
Click to collapse
Yeah its true.. keep in mind your warranty can still be voided by requesting an unlock token from HTCDev
Sent from my Nexus 10 using Tapatalk 4
altimax98 said:
Yeah its true.. keep in mind your warranty can still be voided by requesting an unlock token from HTCDev
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I know but they don't have any evidences that I used the unlock_code.bin so I think i am on the safe side... At least I hope so...
altimax98 said:
Don't go S-On. S-Off won't void your warranty
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
why not go son？
Sent from my HTC One using Tapatalk 2
dingnangen said:
why not go son？
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Don't go S-On with hboot 1.55 - A few users have reported the ***TAMPER*** returning to the bootloader screen even with the bootloader Locked
Don't know if they patched something in the latest hboot. Only way around it was to go S-ON in hboot 1.54 and then receive the OTA
stovie_steve said:
Don't go S-On with hboot 1.55 - A few users have reported the ***TAMPER*** returning to the bootloader screen even with the bootloader Locked
Don't know if they patched something in the latest hboot. Only way around it was to go S-ON in hboot 1.54 and then receive the OTA
Click to expand...
Click to collapse
hmm.. that's crappy... do you know a thread where this particular problem is mentioned? I searched for it.. but didn't find anything
LibertyMarine said:
hmm.. that's crappy... do you know a thread where this particular problem is mentioned? I searched for it.. but didn't find anything
Click to expand...
Click to collapse
It's happened with myself despite being completely stock and to someone else in an earlier thread today
Only way I could bypass this was by basically starting from hboot 1.44 and then installing an RUU before going s on, then taking the ota s right up to the latest hboot
stovie_steve said:
It's happened with myself despite being completely stock and to someone else in an earlier thread today
Only way I could bypass this was by basically starting from hboot 1.44 and then installing an RUU before going s on, then taking the ota s right up to the latest hboot
Click to expand...
Click to collapse
So this basically means you locked and untampered your phone after installing the RUU? And another question: Did you also flash this stock hboot before installing the RUU?
http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
But I decided not to go back s on because they won't void my warranty for that and if they say that will void it, I am gonna argue with them until they accept the only fair option: SOFWARE MODIFICATION CAN'T CAUSE ANY HARDWARE DAMAGE except overclocking can melt your phone^^
LibertyMarine said:
So this basically means you locked and untampered your phone after installing the RUU? And another question: Did you also flash this stock hboot before installing the RUU?
http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
But I decided not to go back s on because they won't void my warranty for that and if they say that will void it, I am gonna argue with them until they accept the only fair option: SOFWARE MODIFICATION CAN'T CAUSE ANY HARDWARE DAMAGE except overclocking can melt your phone^^
Click to expand...
Click to collapse
This is how I did it
http://forum.xda-developers.com/showthread.php?t=2519259
My method was for a carrier branded phone (o2 UK) but this guide can be changed to suit unbranded phones. The problem I had, as well as others, was getting back to s on and once writesecureflag 3 was performed on hboot 1.55 tamper was detected. Guess it may be a patch in latest hboot. I had to go s on with hboot 1.54 or earlier and then upgrade to hboot 1.55 via ota once I was happy everything was stock
stovie_steve said:
Don't go S-On with hboot 1.55 - A few users have reported the ***TAMPER*** returning to the bootloader screen even with the bootloader Locked
Don't know if they patched something in the latest hboot. Only way around it was to go S-ON in hboot 1.54 and then receive the OTA
Click to expand...
Click to collapse
my phone is son unlock with hb1.54 now,i want to go soff using RumRunner ,then flash 4.1 ruu and back to 100% stock(s-on) using revone for warranty,can i get soff Using revone again?
dingnangen said:
my phone is son unlock with hb1.54 now,i want to go soff using RumRunner ,then flash 4.1 ruu and back to 100% stock(s-on) using revone for warranty,can i get soff Using revone again?
Click to expand...
Click to collapse
As long as your using it on a downgraded hboot ie 1.44. Rumrunner will only work on hboot 1.5x
To run the 4.1 RUU you will have to downgrade the hboot or it will give error 155
stovie_steve said:
This is how I did it
http://forum.xda-developers.com/showthread.php?t=2519259
My method was for a carrier branded phone (o2 UK) but this guide can be changed to suit unbranded phones. The problem I had, as well as others, was getting back to s on and once writesecureflag 3 was performed on hboot 1.55 tamper was detected. Guess it may be a patch in latest hboot. I had to go s on with hboot 1.54 or earlier and then upgrade to hboot 1.55 via ota once I was happy everything was stock
Click to expand...
Click to collapse
Sorry that this question seams to be very simple.. but did you go s on with this version of bootloader?
http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
Because I really don't want to risk anything by going s on again..
Or did you go s on again with the 1.54 hboot from the OTA?
LibertyMarine said:
Sorry that this question seams to be very simple.. but did you go s on with this version of bootloader?
http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
Because I really don't want to risk anything by going s on again..
Or did you go s on again with the 1.54 hboot from the OTA?
Click to expand...
Click to collapse
When I ran the RUU after downgrading the hboot I was on android 4.1.2 and hboot 1.44
I restored a nandroid backup then for my o2 carrier. Although the recovery was stock, it wasn't 100% stock for my carrier. I knew this would be fixed with the OTA so that's why I went s on then with hboot 1.54 as EVERYTHING was stock
If you are going to an unbranded model, you can change the CID to run the RUU if you have to, then once completed change the CID back, push revone for locking bootloader, remove tampered etc then when satisfied you can s on again. Just don't s on with hboot 1.55!
i was running custom rom but decided the blue haze on the camera wasn't doing it for me and turns out htc are able to repair it once i send in
I got to relocked s-on only showing no tampered or anything by flashing ruu
running latest sense rom and hboot 1.56 atm
need to get back to just [locked] showing s-on
this is frustrating me I need help
i unlocked this originally through htc if that matters
You will need s-off to reset the bootloader back to locked instead of re-locked
Sent from my HTC One using xda app-developers app
adoboFosho said:
i was running custom rom but decided the blue haze on the camera wasn't doing it for me and turns out htc are able to repair it once i send in
I got to relocked s-on only showing no tampered or anything by flashing ruu
running latest sense rom and hboot 1.56 atm
need to get back to just [locked] showing s-on
this is frustrating me I need help
i unlocked this originally through htc if that matters
Click to expand...
Click to collapse
S-OFF the phone. Then, use the flash the Guru Bootloader Reset zip in TWRP/CWM. From there, you can set it to Locked. But, HBOOT 1.56 has a lot of problems when trying to S-OFF. Its a hit and miss chance. Try using Firewater to S-OFF
raghav kapur said:
S-OFF the phone. Then, use the flash the Guru Bootloader Reset zip in TWRP/CWM. From there, you can set it to Locked. But, HBOOT 1.56 has a lot of problems when trying to S-OFF. Its a hit and miss chance. Try using Firewater to S-OFF
Click to expand...
Click to collapse
the instructions on firewater on their site probably doesn't work with what I have atm cant link to the site yet not enough posts..
what is the best course of action I take?
im running latest android not 4.3 with an m7 not m8 and unrooted
i tried temprooting using firewater just to get s-off didn't work since i have newest android
can someone tell me what to do from here? flash 4.3? root again?!
Reason I ask is because everyone here recommends you leave your phone S-off when returning to stock. My phone is a carrier based phone (O2-UK)
I figured that all phones under 02-UK are shipped as s-on (from experience only, I worked with 02 and only had a few HTC phones where I checked and they were S-on)
My phone has to be sent back for repair. At present it is S-off with locked boot loader and completely stock Rom. I can easily go back to S-on if needed so this is out of curiosity
stovie_steve said:
Reason I ask is because everyone here recommends you leave your phone S-off when returning to stock. My phone is a carrier based phone (O2-UK)
I figured that all phones under 02-UK are shipped as s-on (from experience only, I worked with 02 and only had a few HTC phones where I checked and they were S-on)
My phone has to be sent back for repair. At present it is S-off with locked boot loader and completely stock Rom. I can easily go back to S-on if needed so this is out of curiosity
Click to expand...
Click to collapse
it's getting harder to get s-off (no phones ship with s-off)
that's why everyone recommends leaving it s-off until the last possible second
Yeah I know that as well
The issue is if I go s on for repairs now on hboot 1.56 I will get a **TAMPER DETECTED** message and need to unlock via HTC dev again
If I NEED s on I can downgrade the hboot to 1.44, install an earlier 1.29.xxx.x Rom and return to S-on and accept OTA's til latest version
So it's either send it off now as is and hope for the best or just suck it up and go back to s-on
Sent from my HTC One using xda app-developers app
In response to my Q below, a user wrote that if I go S-ON (to take the phone into repair) I can never go S-ON again. Is that true? I've restored my phone 100% to stock HBOOT, recovery OS etc. and I'm presently at HBOOT 1.57 and have locked the bootloader and have "*** LOCKED ***". So the only thing left is to go S-ON. But I'm wondering if this means I can never go S-ON again.
Thanks!
The original question: http://forum.xda-developers.com/htc-one/help/restore-m7-to-stock-q-hboot-t2999854
kenzorio said:
In response to my Q below, a user wrote that if I go S-ON (to take the phone into repair) I can never go S-ON again. Is that true? I've restored my phone 100% to stock HBOOT, recovery OS etc. and I'm presently at HBOOT 1.57 and have locked the bootloader and have "*** LOCKED ***". So the only thing left is to go S-ON. But I'm wondering if this means I can never go S-ON again.
Thanks!
The original question: http://forum.xda-developers.com/htc-one/help/restore-m7-to-stock-q-hboot-t2999854
Click to expand...
Click to collapse
You can go S On again any time
He advised you should not make it S On
because keep your SOff is beneficial
your phone is GPE so that's had firmware problem after 1.55 locking Bootloader it cant be unlocked if you are on S On that time
if you keep S Off you can Unlock your phone easily
as you know 1st time you need Unlock Bootloader then you make S Off but if you update Hboot then Lock Bootloader then S On its quiet hard to make it S Off again and using root custom Roms etc
IF YOU NOT UNDERSTAND ANSWER DONT WRITE A NEW THREAD ASK AGAIN IN SAME THREAD WE WILL HELP YOU THERE
kenzorio said:
In response to my Q below, a user wrote that if I go S-ON (to take the phone into repair) I can never go S-ON again. Is that true? I've restored my phone 100% to stock HBOOT, recovery OS etc. and I'm presently at HBOOT 1.57 and have locked the bootloader and have "*** LOCKED ***". So the only thing left is to go S-ON. But I'm wondering if this means I can never go S-ON again.
Thanks!
The original question: http://forum.xda-developers.com/htc-one/help/restore-m7-to-stock-q-hboot-t2999854
Click to expand...
Click to collapse
I did not mean you can never go s-off again. Most likely you phone will be returned with the latest software and hboot 1.57 installed and you'll have to pay to s-off. Many here have sent their phone to repair with s-off and had no problems getting repair.
and their phones were returned to them still s-off
clsA said:
I did not mean you can never go s-off again. Most likely you phone will be returned with the latest software and hboot 1.57 installed and you'll have to pay to s-off. Many here have sent their phone to repair with s-off and had no problems getting repair.
and their phones were returned to them still s-off
Click to expand...
Click to collapse
OK just to clarify - it originally wasn't a GPE. I converted it to GPE, and now I converted it back to stock (incl HBOOT, recovery etc.). Btw, in the post I mistakenly asked if it meant I could never go S-ON again. What I meant to ask was if I couldn't get S-OFF again!
But you say I have to pay to get S-OFF again. Is that because Sunshine is the only way to get S-OFF with HBOOT >= 1.57? Any chance that a free tool will come out that works as well?
Thanks
Moderator Information,
I will keep this thread open as you are getting help on it, but in future can you please keep to one thread per topic.
Thanks.