[Q] How to go back S-ON with hboot 1.55? - One (M7) Q&A, Help & Troubleshooting

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!

Related

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.

HBOOT question

So I had an issue with a HTC One, but I got a replacement! I turned S-OFF, flashed the shipped ROM, locked the bootloader and turned S-ON.
Worked perfectly and looks like new!
Anyhow, during this, I found out that revone doesn't work with newer HBOOT versions.
I have a new HTC One and it has the compatible version of HBOOT so I am in luck.
I want to flash custom ROM's such as ARHD but I don't want to update the hboot.
Does a newer version of HBOOT come with ARHD, or is that something only OTA updates include? Does ARHD stick with older HBOOT?
If it does update hboot,
If I turn S-OFF right away, will I be protected in-case a new HBOOT comes through? Will I be able to flash an older HBOOT version in case I need to turn S-ON?
Is it safe to turn S-OFF right now, and just leave it off, just in the case if my hboot gets updated or something - I can always revert to an older version.
I would also like to say thank you for all of your posts! I am an old time iPhone user for 5 years and I'm glad I switched to Android. There is just so much more you can do.
Your posts really help, contributors! It helped me return my device to new status, without 'relocked' and 'tampered' flags in the bootloader!
So thumbs up to XDA! :good:
rowebil said:
So I had an issue with a HTC One, but I got a replacement! I turned S-OFF, flashed the shipped ROM, locked the bootloader and turned S-ON.
Worked perfectly and looks like new!
Anyhow, during this, I found out that revone doesn't work with newer HBOOT versions.
I have a new HTC One and it has the compatible version of HBOOT so I am in luck.
I want to flash custom ROM's such as ARHD but I don't want to update the hboot.
Does a newer version of HBOOT come with ARHD, or is that something only OTA updates include?
If I turn S-OFF, will I be protected in-case a new HBOOT comes through? Will I be able to flash an older HBOOT version?
I would also like to say thank you for all of your posts! I am an old time iPhone user for 5 years and I'm glad I switched to Android. There is just so much more you can do.
Your posts really help, contributors! It helped me return my device to new status, without 'relocked' and 'tampered' flags in the bootloader!
So thumbs up to XDA! :good:
Click to expand...
Click to collapse
I have never update the hboot when using ARHD, I just gave it a flash.
As to updating via ota, the only thing close to that for me is when I did a gpe conversion to hboot 1.54 but I could go back.
Sent from my One using Tapatalk 4
squabbi said:
I have never update the hboot when using ARHD, I just gave it a flash.
As to updating via ota, the only thing close to that for me is when I did a gpe conversion to hboot 1.54 but I could go back.
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
It is just in the case that I need to do this replacement all over again. I don't want to update to another HBOOT accidentally through a ROM, and then find out I can't get S-OFF/S-ON and I'm stuck lol.
I can't get my words out too clear tonight! I'm not really sure as of why.
If I have S-OFF, and my HBOOT updates somehow, can I go back and flash another HBOOT?
Then another thought comes, I don't want to turn S-OFF because the thread says may not work with all ROM's, which is why I asked if ARHD will update my HBOOT.
Also, thanks for your AIO toolkit! I was looking for it earlier today. I used it when I bought my phone and worked great! Thanks for that!
rowebil said:
It is just in the case that I need to do this replacement all over again. I don't want to update to another HBOOT accidentally through a ROM, and then find out I can't get S-OFF/S-ON and I'm stuck lol.
I can't get my words out too clear tonight! I'm not really sure as of why.
If I have S-OFF, and my HBOOT updates somehow, can I go back and flash another HBOOT?
Then another thought comes, I don't want to turn S-OFF because the thread says may not work with all ROM's, which is why I asked if ARHD will update my HBOOT.
Also, thanks for your AIO toolkit! I was looking for it earlier today. I used it when I bought my phone and worked great! Thanks for that!
Click to expand...
Click to collapse
If you want to go back to S-ON you should use an ruu to go back to stock then use the S-ON command.
I'm sure you can downgrade back to hboot 1.44 but some say you can't, but it worked for the Google edition conversion and I returned to 1.44.
I'm glad the toolkit worked for you!
Sent from my One using Tapatalk 4
squabbi said:
If you want to go back to S-ON you should use an ruu to go back to stock then use the S-ON command.
I'm sure you can downgrade back to hboot 1.44 but some say you can't, but it worked for the Google edition conversion and I returned to 1.44.
I'm glad the toolkit worked for you!
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
Ah okay, I didn't think about that!
So an RUU will also downgrade hboot?
I don't want to be stuck with a junk hboot that is locked down.
It is going to work for me again, when I unlock this new phone!
It's safe to go S-Off now and leave it off. hboot updates won't cause S-On
ARHD won't update your hboot.
If your hboot is updated, you must be already S-Off to downgrade.
You are on 1.44 right now. If you go s-off now, you will remain s-off even after accepting OTAs, and you can downgrade your hboot whenever you feel like. On the other hand, if you are s-on right now, and accept an OTA, you'll be upgraded to the locked down 1.54, on which you can't get s-off, nor can you downgrade.. What I suggest is going s-off right now, and doing whatever flashing you want to do.. Beware, with s-off, you can permanently brick(hard brick) your phone. If you ever want to go back to s-on, flash an RUU of ONLY 4.1.2. All roms work with s-off, so no need to worry
Sent from my HTC One using Tapatalk 4
rowebil said:
Ah okay, I didn't think about that!
So an RUU will also downgrade hboot?
I don't want to be stuck with a junk hboot that is locked down.
It is going to work for me again, when I unlock this new phone!
Click to expand...
Click to collapse
An ruu should, but if you don't want to factory restore, you can just flash the ruu.
Sent from my One using Tapatalk 4

[Q] Downgrade Hboot 1.54 to 1.44?

Ok so i have searched but unable to find an answer to my question.
I want to downgrade my Hboot from 1.54 back to 1.44. I do have s-off. I s-offed when my hboot was on 1.44 using revone. My hboot was upgraded after doing a firmware update.
So i need to send my phone in for repairs (the infamous purple camera) and i want to downgrade so I can return to stock, remove "tampered" and relock.
As stated I am currently S-off and have read its possible to downgrade if you are s-off, just need to be pointed in the right direction
broli-zn said:
Ok so i have searched but unable to find an answer to my question.
I want to downgrade my Hboot from 1.54 back to 1.44. I do have s-off. I s-offed when my hboot was on 1.44 using revone. My hboot was upgraded after doing a firmware update.
So i need to send my phone in for repairs (the infamous purple camera) and i want to downgrade so I can return to stock, remove "tampered" and relock.
As stated I am currently S-off and have read its possible to downgrade if you are s-off, just need to be pointed in the right direction
Click to expand...
Click to collapse
I wouldn't downgrade and s-on for warranty, it isn't necessary, they won't check and you will regret it because you will get back your phone s-on and upgraded to hboot 1.54, so non-s-offable for now. I did it too without any problems.
Just make you phone stock again (install a stock ruu is it is available), lock (not relock) your phone and remove tampered flag (running an ruu would remove it, if there is no ruu do it first because revone won't work without root on hboot 1.54)
BTW purple camera is just software whitebalance problem not a hardware problem
You just need to downgradethe firmware. It contains the hboot.
But as @godutch said, it's not necessary.
Sent from my One using XDA Premium 4 mobile app
Ok cool, thanks guys, so I just need a flash a firmware zip containing 1.44 Hboot and im good to go?
Basically i just want to get rid of the tampered flag.
Iv done the 4.3 upgrades with supposedly fix the camera but its made no effect on mine :crying: so the only other option I have to try and get them to change the camera module.
Thanks again guys. Much appreciated. You will get a thanks each
you don't need to downgrade. h-boot 1.54 is normal and considerated STOCK for devices who made OTA update.
don't do stupid thing's
i removed tampared flag with revone -t
criszz said:
you don't need to downgrade. h-boot 1.54 is normal and considerated STOCK for devices who made OTA update.
don't do stupid thing's
i removed tampared flag with revone -t
Click to expand...
Click to collapse
i flashed firmware using ADB, revone doesnt work with 1.54 unfortunately
broli-zn said:
i flashed firmware using ADB, revone doesnt work with 1.54 unfortunately
Click to expand...
Click to collapse
it does but you need to be s-off and rooted for it to work but you don't have to do what you are trying to do and you will regret it later....
just try with 1.54 , multiple times
hboot 1.55
godutch said:
I wouldn't downgrade and s-on for warranty, it isn't necessary, they won't check and you will regret it because you will get back your phone s-on and upgraded to hboot 1.54, so non-s-offable for now. I did it too without any problems.
Just make you phone stock again (install a stock ruu is it is available), lock (not relock) your phone and remove tampered flag (running an ruu would remove it, if there is no ruu do it first because revone won't work without root on hboot 1.54)
BTW purple camera is just software whitebalance problem not a hardware problem
Click to expand...
Click to collapse
I had my phone repaired twice and they didn't say any thing about the boot loader being unlock. However, since that I have s-off and the phone needs to go to repair for the microphone not working and I wonder if I could either s-on and lock the boot loader with hboot 1.55? If you have any advice, I would appreciate it. Thanks.
amauryaa said:
I had my phone repaired twice and they didn't say any thing about the boot loader being unlock. However, since that I have s-off and the phone needs to go to repair for the microphone not working and I wonder if I could either s-on and lock the boot loader with hboot 1.55? If you have any advice, I would appreciate it. Thanks.
Click to expand...
Click to collapse
not recommended, as far as i've seen, going from s-off to s-on (on 100% stock everything), after a few reboots, has a high chance of resulting in "tamper detected - rebooting" and the TAMPERED sign is back.

Downgrade Hboot to 1.44 to achive s-off? Interesting tutorial that a dude made...

Hi, so I got my HTCOne black edition and it had 4.2.2 Sense and I just saw that it has hboot 1.54 and s-on
I want to root but I want to be able to lock my bootloader (make it say locked and not relocked) incase I get into warranty problems...
So I came across this: http://htc-one.wonderhowto.com/how-...one-into-htc-one-with-sense-no-bloat-0148220/
He shows how to get Sense on Google Edition but on Step two he says that you need to downgrade 1.54 to 1.44 for this to be able to work
He changes the cid to make the bootloader think he can downgrade it (he says)
So can I do the same thing by
1. Unlocking my bootloader, root and then downgrade the hboot?
2. Unlock bootloader, root and turn my phone into google edition --> Downgrade to 1.44 ---> Reinstall Sense RUU or Rom or whatever to get it back?
3. Any other way?
I searched a bit but could not find anything about this so I hope we can keep a nice discussion here for people like me who are stuck on 1.54 with s-on (thanks htc for sending me a new HTCOne, except that it is s-on and on 1.54 and on 4.2.2 :/ )
Thanks in advance
sopaj96 said:
Hi, so I got my HTCOne black edition and it had 4.2.2 Sense and I just saw that it has hboot 1.54 and s-on
I want to root but I want to be able to lock my bootloader (make it say locked and not relocked) incase I get into warranty problems...
So I came across this: http://htc-one.wonderhowto.com/how-...one-into-htc-one-with-sense-no-bloat-0148220/
He shows how to get Sense on Google Edition but on Step two he says that you need to downgrade 1.54 to 1.44 for this to be able to work
He changes the cid to make the bootloader think he can downgrade it (he says)
So can I do the same thing by
1. Unlocking my bootloader, root and then downgrade the hboot?
2. Unlock bootloader, root and turn my phone into google edition --> Downgrade to 1.44 ---> Reinstall Sense RUU or Rom or whatever to get it back?
3. Any other way?
I searched a bit but could not find anything about this so I hope we can keep a nice discussion here for people like me who are stuck on 1.54 with s-on (thanks htc for sending me a new HTCOne, except that it is s-on and on 1.54 and on 4.2.2 :/ )
Thanks in advance
Click to expand...
Click to collapse
Changing CID (to allow RUUs that are not for your phone) is not possible with S-ON. So that guide requires S-OFF.... S-ON + hboot 1.54 = No S-OFF untill exploit is revealed. Sorry.
Thread for attempts to get S-OFF on hboot 1.54 -> http://forum.xda-developers.com/showthread.php?p=46263968
EDIT:
First comment on the guide you linked to states the following which is correct:
For #1, using your instructions, the CID will not change. it seems that i need to set S-Off....
Click to expand...
Click to collapse
sopaj96 said:
Hi, so I got my HTCOne black edition and it had 4.2.2 Sense and I just saw that it has hboot 1.54 and s-on
I want to root but I want to be able to lock my bootloader (make it say locked and not relocked) incase I get into warranty problems...
So I came across this: http://htc-one.wonderhowto.com/how-...one-into-htc-one-with-sense-no-bloat-0148220/
He shows how to get Sense on Google Edition but on Step two he says that you need to downgrade 1.54 to 1.44 for this to be able to work
He changes the cid to make the bootloader think he can downgrade it (he says)
So can I do the same thing by
1. Unlocking my bootloader, root and then downgrade the hboot?
2. Unlock bootloader, root and turn my phone into google edition --> Downgrade to 1.44 ---> Reinstall Sense RUU or Rom or whatever to get it back?
3. Any other way?
I searched a bit but could not find anything about this so I hope we can keep a nice discussion here for people like me who are stuck on 1.54 with s-on (thanks htc for sending me a new HTCOne, except that it is s-on and on 1.54 and on 4.2.2 :/ )
Thanks in advance
Click to expand...
Click to collapse
Won't work, you already have to be S-Off to downgrade hboot, the tutorial should have stated that at the beginning. Sorry
TwinAdk said:
Changing CID (to allow RUUs that are not for your phone) is not possible with S-ON. So that guide requires S-OFF.... S-ON + hboot 1.54 = No S-OFF untill exploit is revealed. Sorry.
Thread for attempts to get S-OFF on hboot 1.54 -> http://forum.xda-developers.com/showthread.php?p=46263968
EDIT:
First comment on the guide you linked to states the following which is correct:
Click to expand...
Click to collapse
But... How did he get s-off with a Google Edition phone when he had 1.54? Mu thoughts are that Google Edition has s-off... So maybe if we root and turn our phone to a google edition phone and then do what he does...then put it back on sense?
I want to root so badly lol xd
GPe are s-on. He probably had an s-off device converted to GPe.
Sent from my One using XDA Premium 4 mobile app
CoryTallman said:
GPe are s-on. He probably had an s-off device converted to GPe.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well that sucks if its true :/
Do you think I should root anyway?
As of now I dont have any problems with my phone and by the time it takes for it to break, if it even breaks or defects or something, maybe someone has made some tool or have hacked 1.54... It cant take more than 1 year right?
They're looking for an exploit for hboot 1.55 not 1.54. And it may never come. No one knows till someone finds it. There's always the java card option though.
Sent from my One using XDA Premium 4 mobile app

[Q] HBoot 1.55 S-Off back to S-On needed?

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

Categories

Resources