Hi there, this could have been already answered, but I just wanna make sure I don't make a mistake and brick my phone. So I have a sprint HTC one with hboot 1.55. I already S-OFFed using rumrunner, and everything is fine and dandy. Now I want to get rid of the stupid tamper flag. I know this was possible when using revone on hboot 1.44, but how would I do that on hboot 1.55 if I used rumrunner? and secondly, should I ever need to restore back to stock and set S-ON, would this be possible?
PS: I figured the process for removing the tamper flag was probably the same as when using revone, but again I don't want to brick my phone by doing something stupid.
Thanks in advance!
matinm90 said:
Hi there, this could have been already answered, but I just wanna make sure I don't make a mistake and brick my phone. So I have a sprint HTC one with hboot 1.55. I already S-OFFed using rumrunner, and everything is fine and dandy. Now I want to get rid of the stupid tamper flag. I know this was possible when using revone on hboot 1.44, but how would I do that on hboot 1.55 if I used rumrunner? and secondly, should I ever need to restore back to stock and set S-ON, would this be possible?
PS: I figured the process for removing the tamper flag was probably the same as when using revone, but again I don't want to brick my phone by doing something stupid.
Thanks in advance!
Click to expand...
Click to collapse
Check out http://forum.xda-developers.com/showthread.php?t=2487888
I haven't done it personally yet but read threw it I haven't had time to check if it will work with sprint
Related
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.
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 just S-Offed with Firewater. I know in the past (maybe in the revone days), I read a lot of warnings about not going back to S-On because you might never be able to gain S-Off again. Is this still the case? I think I need to have my phone serviced, and I'm worried they might not replace it--in that case, I don't want to be stuck with a devie whose firmware I can't ever upgrade.
fenstre said:
I just S-Offed with Firewater. I know in the past (maybe in the revone days), I read a lot of warnings about not going back to S-On because you might never be able to gain S-Off again. Is this still the case? I think I need to have my phone serviced, and I'm worried they might not replace it--in that case, I don't want to be stuck with a devie whose firmware I can't ever upgrade.
Click to expand...
Click to collapse
S-OFF is hard to achieve on hboot 1.56. If you turn s-on on hboot 1.55 and above, the tampered flag will come back after a few reboot. So only s-on on hboot 1.44-1.54.
alray said:
S-OFF is hard to achieve on hboot 1.56. If you turn s-on on hboot 1.55 and above, the tampered flag will come back after a few reboot. So only s-on on hboot 1.44-1.54.
Click to expand...
Click to collapse
Thanks! So the biggest problem is that people S-Off, then upgrade hboot, then turn S-On again? I suspected that... sounds like the problem with people that convert their phone to GPe, and then relock their bootloaders.
I have hboot 1.54, so I guess I'm good to S-Off and S-On at will? Thanks!
Sure, that's a good HBOOT to start with if you want to S-OFF.
But just to get back to the original topic of this thread, it's not particularly "safe" to go S-ON. Ever.
The danger is not about whether it's easy to change your mind and go back to S-OFF later.
The larger danger is you can brick the phone (for real-- hard brick, truly dead phone) if your HBOOT has been modified or damaged at some point before you attempt S-ON.
Going back and forth between S-OFF and S-ON "at will" is just asking for trouble.
My personal policy is never S-ON for any reason. Not even warranty repair.
Sent from my HTC One using xda app-developers app
NxNW said:
The danger is not about whether it's easy to change your mind and go back to S-OFF later.
The larger danger is you can brick the phone (for real-- hard brick, truly dead phone) if your HBOOT has been modified or damaged at some point before you attempt S-ON.
Click to expand...
Click to collapse
Oh, that makes sense. And I see that, for example, modifying HBoot would make it pretty easy to make it so you can't ever root. So I'll cross "hboot mod" off my list of options.
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.
Hi all. I just unlocked my HTC m7 (GSM) with HTCdev.com and then installed TWRP and used that to install SuperSU. After that, I ran Sunshine to get S-OFF, and then I ran Guru Bootloader Reset in order to remove the "tampered" flag. Then I set SuperCID to 11111111, and I think I'm ready to flash a rom (I"m looking at ViperOne, since I used it on my Sensation and liked it).
I'm on hboot 1.61. Is it worth downgrading to 1.44 so that I can easily get s-on/s-off in the future? If so, should I flash the new hboot before or after the rom? Does it matter?
Thanks all. I spent quite a bit of time flashing and testing roms on my HTC Touch Pro and then my HTC Sensation. I've held off for a couple of years, but I'm looking forward to playing around with my M7 again!
MPenguin said:
(...), I ran Sunshine to get S-OFF
(...)
I'm on hboot 1.61. Is it worth downgrading to 1.44 so that I can easily get s-on/s-off in the future? If so, should I flash the new hboot before or after the rom? Does it matter?
Thanks all. I spent quite a bit of time flashing and testing roms on my HTC Touch Pro and then my HTC Sensation. I've held off for a couple of years, but I'm looking forward to playing around with my M7 again!
Click to expand...
Click to collapse
Your phone is already S-OFF why would you want to turn it back S-ON? Never go back S-ON, the only time it should be done is before sending the phone for repair under warranty. Going back S-ON is the same as intentionally locking your car with the keys left inside... And even if you go back S-ON why hboot 1.44 should make it easier to achieve S-OFF again? You just paid for Sunshine, you can use it as many time as you want on that phone + If you already have paid for Sunshine, its actually the easiest method to S-OFF your phone on any hboot version.
If I buy a SunShine license, can I use it on multiple phones?
No - one license is good for one device. You can reuse SunShine on that device, if necessary, we however NEVER recommending setting your device S-ON
Click to expand...
Click to collapse
ref: http://theroot.ninja/faq.html
Another thing to know is that hboot 1.44 is incompatible with windows 8 and 10, so say goodbye to fastboot connectivity (fastboot commands) after flashing it, unless you are using a Mac, Win7 or Linux.
For your last question, it doesn't matter when you flash the hboot, if you need to flash one. Would recommend to stay on 1.61