I've read revone leaves hboot stock... is that even after changing the flag? Is it safe to s-on again?
After hunreds of pages read I haven't seen it explicitly stated so just wanted to confirm I am not set up for failure.
Also will it still not say tampered?
Thanks!
I'd just leave it S-OFF. It's recommended only to go back to S-ON again if you're running a 100% stock device (e.g. you've just run an RUU) as it can brick the phone otherwise
EddyOS said:
I'd just leave it S-OFF. It's recommended only to go back to S-ON again if you're running a 100% stock device (e.g. you've just run an RUU) as it can brick the phone otherwise
Click to expand...
Click to collapse
How about with an adb backup restored, flag off and relocked?
I guess my concern is what does the flag change and should I turn it back on before s-on or just leave it? This is purely informative.
Turning your security flag back on will re enable the checks the phone does when booting. It's making sure all the parts (hboot, radio, etc....) are signed. If you flashed a radio or hboot that's unsigned (like the one from revone or moonshine) the device will simply not boot. One of the ways to cause a Perma brick which can only be fixed with a jtag jig which doesn't exist yet for the one
Sent from my Tricked out HTC One
The first post of the thread used to say it's safe to do (although as I type it I feel like I spelt it wrong)
fastboot oem writesecureflag 3
It's fine, if you want to do it, but there's little point before flashing everything else to stock and returning it for warranty.
Related
Hi, have been reading up as much as possible, but am after confirmation before I start trying to return to stock.
Basically, I have an unlocked HTC__001 HTC One, s-on ,with an unlocked bootloader which was unlocked via HTCDev.
It was unlocked after being updated to 2.24.401.1, so I have bootloader 1.54, and an active "tampered" flag.
So, i've been playing with a GE rom for a bit but have decided I would like to get my device back to stock. I am under the impression that I could use my custom recovery to flash a stock odexed ROM suitable for my CID from here, then flash the correct radio, then re-flash the correct stock recovery, then re-lock the bootloader and be back to stock. My questions are these:
a) Am I right?
b) If I am right, will I still have the "tampered" flag set in the bootloader? I'm assuming I would.
c) If the flag is still set, will it affect any future OTA updates I may receive?
d) Does anyone know of a method other than this which will get me back to stock?
I have noted that the RUU for my device does not seem to be availabe to download as of yet, only the previous version is available which has the 1.44 bootloader, obviously, if I try to flash that, it will complain about the bootloader version being lower ect. So I don't think that is an option.
Any help would be appreciated, Cheers.
Clivectmob said:
Hi, have been reading up as much as possible, but am after confirmation before I start trying to return to stock.
Basically, I have an unlocked HTC__001 HTC One, s-on ,with an unlocked bootloader which was unlocked via HTCDev.
It was unlocked after being updated to 2.24.401.1, so I have bootloader 1.54, and an active "tampered" flag.
So, i've been playing with a GE rom for a bit but have decided I would like to get my device back to stock. I am under the impression that I could use my custom recovery to flash a stock odexed ROM suitable for my CID from here, then flash the correct radio, then re-flash the correct stock recovery, then re-lock the bootloader and be back to stock. My questions are these:
a) Am I right?
b) If I am right, will I still have the "tampered" flag set in the bootloader? I'm assuming I would.
c) If the flag is still set, will it affect any future OTA updates I may receive?
d) Does anyone know of a method other than this which will get me back to stock?
I have noted that the RUU for my device does not seem to be availabe to download as of yet, only the previous version is available which has the 1.44 bootloader, obviously, if I try to flash that, it will complain about the bootloader version being lower ect. So I don't think that is an option.
Any help would be appreciated, Cheers.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2358738 Check this guide out
Thanks, but I have read that thread, it doesn't really apply to my situation. That thread is for S-off devices, mine is S-on. And also, it requires running an RUU which for me isn't available. The trouble (i believe) is that when S-on, I cannot run an older RUU than my current device is at. Hence my asking here.
Clivectmob said:
Thanks, but I have read that thread, it doesn't really apply to my situation. That thread is for S-off devices, mine is S-on. And also, it requires running an RUU which for me isn't available. The trouble (i believe) is that when S-on, I cannot run an older RUU than my current device is at. Hence my asking here.
Click to expand...
Click to collapse
Run a stock ROM like found in mike1986's thread, install the stock recovery and relock your bootloader ... That's all you can do at the moment because you can't go S-Off on Hboot 1.54 so the tampered flag will have to stay until you can.
Read through this, http://forum.xda-developers.com/showthread.php?t=2265618 .. there's everything there that you need to return to stock and receive OTA updates while being S-On. The only time you'll have an issue is if you can't go S-Off to remove the tampered flag and change it from relocked to locked, only an issue if you need to return it under warranty for anything that's happened as a result of you unlocking the bootloader and flashing stuff.
Yeah! That's pretty much what I thought.
Will the tamper flag give me issues do you think?
Clivectmob said:
Yeah! That's pretty much what I thought.
Will the tamper flag give me issues do you think?
Click to expand...
Click to collapse
According to the guy I spoke to at HTC when I sent mine back the other day, it shouldn't. He said they should only refuse to cover repair under warranty if the fault is caused by something you've done, i.e, flashing stuff or deliberate damge or something. Unfortunately that's the risk you take if you need to return it, unless there's a method to change the flag by being S-Off you just have to either not risk it and wait until you can go S-Off and be sure to remove all traces of messing, or you return it and hope for the best lol
Well, I don't need to get it fixed or anything. Just had me play and wanna return it back to normal. I have done as I said I would in the first post and applied a small application update from HTC, so it appears to have worked. As expected, I have Re-locked and Tampered displayed. Will Just wait for S-off to emerge and deal with it then. Thanks for all the replies.
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.
Alright, I've been through thread after thread and plenty of pages found on google.
Some say to Lock the bootloader BEFORE using the RUU and some say to lock it AFTER or you'll brick the phone?
I've got a T-mobile Variant of the HTC one M7 It's rooted, SuperCID and obviously the bootloader is unlocked.... I think it's on 1.55, not exactly sure, I'm currently backing up all my data.
I've got the new 5.14.531.1 RUU straight from the HTC website.
Since it's a Tmobile rom, I'm guessing resetting the CID to T-MOB010 before installing would be a good idea?
And what of the bootloader? running the RUU should install the new Hboot correct? from there I would just need to relock it or am I not understanding this?
~Out of all my phones I've NEVER returned one to stock, so this is all kinda new to me.
Vonrottes said:
I've got the new 5.14.531.1 RUU straight from the HTC website.
Click to expand...
Click to collapse
SuperCID means you're S-Off, so no need to lock/relock bootloader, but where did you get that RUU from? link please, cause I don't think it's an RUU (how big is the file??)
nkk71 said:
SuperCID means you're S-Off, so no need to lock/relock bootloader, but where did you get that RUU from? link please, cause I don't think it's an RUU (how big is the file??)
Click to expand...
Click to collapse
Doesn't exactly answer the question... I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
Also the link, right from HTC
http://dl3.htc.com/application/RUU_M7UL_TMOUS_5.14.531.1_With Partial.exe
it's a whooping 1.49GB
Vonrottes said:
Doesn't exactly answer the question... I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
Also the link, right from HTC
http://dl3.htc.com/application/RUU_M7UL_TMOUS_5.14.531.1_With Partial.exe
it's a whooping 1.49GB
Click to expand...
Click to collapse
ah ok, 1.49GB sounds good for an RUU
and to answer your question differently, if you are S-Off, then you do not need to lock/relock bootloader; the RUU should work fine with unlocked bootloader
refer to "Not so FAQ #2": http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
and remember to stay S-Off
nkk71 said:
ah ok, 1.49GB sounds good for an RUU
and to answer your question differently, if you are S-Off, then you do not need to lock/relock bootloader; the RUU should work fine with unlocked bootloader
refer to "Not so FAQ #2": http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
and remember to stay S-Off
Click to expand...
Click to collapse
Jolly good, I didn't even see that Not so FAQ.
So basically I just run the RUU according to the instructions on the HTC page ( http://www.htc.com/us/support/news.aspx?p_id=630&p_name=htc-one-t-mobile ) and I should be good?
Vonrottes said:
Jolly good, I didn't even see that Not so FAQ.
So basically I just run the RUU according to the instructions on the HTC page ( http://www.htc.com/us/support/news.aspx?p_id=630&p_name=htc-one-t-mobile ) and I should be good?
Click to expand...
Click to collapse
hmm, i can't seem to be able open that web page, but if the file is a full RUU (I'm downloading it, but with my connection it's gonna take quite a while), then hook up the phone, and run the RUU and all should be good.
Remember an RUU will fully wipe your phone (including sdcard/internal storage), and if for whatever reason you want to change bootloader to the original LOCKED (not relocked),
you can use this tool: http://forum.xda-developers.com/showthread.php?t=2527194
(though I don't see any reason to do it )
as long as you stay S-Off, you can easily get it unlocked again anytime
out of curiosity, any particular reason you're doing this?
nkk71 said:
hmm, i can't seem to be able open that web page, but if the file is a full RUU (I'm downloading it, but with my connection it's gonna take quite a while), then hook up the phone, and run the RUU and all should be good.
Remember an RUU will fully wipe your phone (including sdcard/internal storage), and if for whatever reason you want to change bootloader to the original LOCKED (not relocked),
you can use this tool: http://forum.xda-developers.com/showthread.php?t=2527194
(though I don't see any reason to do it )
as long as you stay S-Off, you can easily get it unlocked again anytime
out of curiosity, any particular reason you're doing this?
Click to expand...
Click to collapse
I know, that's why I'm currently backing up everything important on Google Drive.
I was just looking at Scotty1223's threads with the ADB commands to remove tampered flag and reset locked.
and like I said in my second post
I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
So to go back stock with no need to ever unlock or root again,
I'll be fine LOCKING the bootloader and resetting the CID to T-MOB010 Before running the RUU?
Vonrottes said:
I know, that's why I'm currently backing up everything important on Google Drive.
I was just looking at Scotty1223's threads with the ADB commands to remove tampered flag and reset locked.
and like I said in my second post
I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
So to go back stock with no need to ever unlock or root again,
I'll be fine LOCKING the bootloader and resetting the CID to T-MOB010 Before running the RUU?
Click to expand...
Click to collapse
I understood the part about upgrading your phone, but seeing your signature, you're running a custom ROM and kernel, so i'm not clear what you mean by upgrading
Anyway, if you are going back to stock, here's what I personally would do:
1- stay S-OFF
2- change CID back to original
3- remove TAMPERED and set LOCKED (using scotty1223's commands, or the Guru Bootloader Reset tool) not because it's necessary, just aesthetically more stock
4- run the RUU
5- stay S-OFF
nkk71 said:
I understood the part about upgrading your phone, but seeing your signature, you're running a custom ROM and kernel, so i'm not clear what you mean by upgrading
Anyway, if you are going back to stock, here's what I personally would do:
1- stay S-OFF
2- change CID back to original
3- remove TAMPERED and set LOCKED (using scotty1223's commands, or the Guru Bootloader Reset tool) not because it's necessary, just aesthetically more stock
4- run the RUU
5- stay S-OFF
Click to expand...
Click to collapse
Upgrading as in:
http://www.t-mobile.com/phone-upgrade.html
To get an HTC One M8 I have turn in my Current M7... Which has to be stock...as far as the T-mobile store tech needs to know.... I guess?
Vonrottes said:
Upgrading as in:
http://www.t-mobile.com/phone-upgrade.html
To get an HTC One M8 I have turn in my Current M7... Which has to be stock...as far as the T-mobile store tech needs to know.... I guess?
Click to expand...
Click to collapse
gotcha :good:
that's a completely different kind of upgrade, i thought you meant software
Do they care about S-OFF?? because if you intend on going S-ON, then I would highly recommend a 1.xx ruu, nothing higher.
because going from S-Off to S-On on hboot 1.55+, has been known to trigger "tamper detected - rebooting" and TAMPERED is back in bootloader screen.
nkk71 said:
gotcha :good:
that's a completely different kind of upgrade, i thought you meant software
Do they care about S-OFF?? because if you intend on going S-ON, then I would highly recommend a 1.xx ruu, nothing higher.
because going from S-Off to S-On on hboot 1.55+, has been known to trigger "tamper detected - rebooting" and TAMPERED is back in bootloader screen.
Click to expand...
Click to collapse
Yeah, it's gonna need to be S-on when I take it into the store...
Pretty sure they check the bootloader for S-ON, ***TAMPERED*** and ***LOCKED***
Is it just the 1.55+ Hboot that throws the tampered when locked?
If so Can I flash the 1.54.401.5 Hboot from Firewater and proceed like that?
Can't do the 1.44, My PC is running 8.1 and I've not played with Linux since 2009
Vonrottes said:
Yeah, it's gonna need to be S-on when I take it into the store...
Pretty sure they check the bootloader for S-ON, ***TAMPERED*** and ***LOCKED***
Click to expand...
Click to collapse
In that case, I recommend you use a 1.xx RUU
(check my guide in my signature)
Vonrottes said:
Is it just the 1.55+ Hboot that throws the tampered when locked?
Click to expand...
Click to collapse
Unknown when/what exactly triggers the "tamper detected" or some people have been able to S-On and not get that, others have not, so I can't say if it will happen or not. but if you wanna play it safe, go for 1.xx ruu.
Vonrottes said:
If so Can I flash the 1.54.401.5 Hboot from Firewater and proceed like that?
Click to expand...
Click to collapse
brick alert: Definitely NOT, that is a custom HBOOT, if you actually manage to S-On it with an unsigned hboot, you'll have an paperweight on your hands!! stay away from that.
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.
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