Related
So I've installed stock Rom and stock recovery and relocked the bootloader but when I start the phone up it still says development Rom and in fastboot it says tampered. Somethings not right.
Any ideas?
Sent from my HTC One using xda app-developers app
recklesslife85 said:
So I've installed stock Rom and stock recovery and relocked the bootloader but when I start the phone up it still says development Rom and in fastboot it says tampered. Somethings not right.
Any ideas?
Click to expand...
Click to collapse
From my understanding it will say Tampered in the bootloader when it is unlocked. If you relock it the bootloader it will say relocked. This is there for HTC to know if the phone was unlocked for warranty stuff. It may also say Tampered because it isn't 100% stock yet. Once you unlock the phone there is no way right now to get back to 100% locked. This will not happen until we get S-Off.
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.
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.
Hi,
I have a HTC One that is not rooted, and has the problem with the camera (Pink in dark places).
What do i need to do for the phone to return to the original and turned to locked
I'm on H.BOOT 1.61, UNLOCKED and S-ON
Thanks for all the help
http://imgur.com/pXW59cZ
nurogo said:
Hi,
I have a HTC One that is not rooted, and has the problem with the camera (Pink in dark places).
What do i need to do for the phone to return to the original and turned to locked
I'm on H.BOOT 1.61, UNLOCKED and S-ON
Thanks for all the help
http://imgur.com/pXW59cZ
Click to expand...
Click to collapse
Are you running a custom ROM or stock ROM? And if it is stock ROM, does version are you running and does it match your current firmware? Please post a fastboot getvar all and remove your Serial No and IMEI
Because you are S-ON, you cannot LOCK the bootloader again, instead it will read RELOCKED. You need to be S-OFF to change the lock status
You may also get a TAMPERED message when you lock the bootloader using the command fastboot oem relock
If all is running stock I would chance it and send it in for repair, as at the end of the day this is a hardware fault not brought around by unlocking your bootloader
nurogo said:
Hi,
I have a HTC One that is not rooted, and has the problem with the camera (Pink in dark places).
What do i need to do for the phone to return to the original and turned to locked
I'm on H.BOOT 1.61, UNLOCKED and S-ON
Thanks for all the help
http://imgur.com/pXW59cZ
Click to expand...
Click to collapse
stovie_steve said:
If all is running stock I would chance it and send it in for repair, as at the end of the day this is a hardware fault not brought around by unlocking your bootloader
Click to expand...
Click to collapse
not 100% true, dont send your phone back relocked, you will need to do whatsteve says and get s-off, then flash an early RUU and HBOOT before locking the bootloader and going s-on, otherwise you risk the tampered flags coming back, the phone must be 100% stock.
HTC will refuse a warranty repair in any other condition, they will blame you on the grounds that since you unlocked the bootloader you could of done anything with the phone like flashed an unsupported kernal and overclocked etc, the camera issue is caused by overheating.
Seanie280672 said:
not 100% true, dont send your phone back relocked, you will need to do whatsteve says and get s-off, then flash an early RUU and HBOOT before locking the bootloader and going s-on, otherwise you risk the tampered flags coming back, the phone must be 100% stock.
HTC will refuse a warranty repair in any other condition, they will blame you on the grounds that since you unlocked the bootloader you could of done anything with the phone like flashed an unsupported kernal and overclocked etc, the camera issue is caused by overheating.
Click to expand...
Click to collapse
From my own experiencea friend sent it in with an unlocked boot loader and they repaired it. But they may have just been lucky.
I wouldn't return to s on on any bootloader later than 1.54, as when you do the writesecureflag command the phone will display a TAMPER DETECTED message and then you're back to square one
Best thing to do would be achieve s off using sunshine
Downgrade hboot to earlier version e.g. 1.44
flash an earlier RUU
Use revone to reset the status of the bootloader to LOCKED, ensure tamper message is not there
Then, if you really must, run the writesecureflag command. That's how I've done it before, and after hboot 1.54 you will def get the tamper detected message
I always leave my phone s off tho
stovie_steve said:
Are you running a custom ROM or stock ROM? And if it is stock ROM, does version are you running and does it match your current firmware? Please post a fastboot getvar all and remove your Serial No and IMEI
Because you are S-ON, you cannot LOCK the bootloader again, instead it will read RELOCKED. You need to be S-OFF to change the lock status
You may also get a TAMPERED message when you lock the bootloader using the command fastboot oem relock
If all is running stock I would chance it and send it in for repair, as at the end of the day this is a hardware fault not brought around by unlocking your bootloader
Click to expand...
Click to collapse
Seanie280672 said:
not 100% true, dont send your phone back relocked, you will need to do whatsteve says and get s-off, then flash an early RUU and HBOOT before locking the bootloader and going s-on, otherwise you risk the tampered flags coming back, the phone must be 100% stock.
HTC will refuse a warranty repair in any other condition, they will blame you on the grounds that since you unlocked the bootloader you could of done anything with the phone like flashed an unsupported kernal and overclocked etc, the camera issue is caused by overheating.
Click to expand...
Click to collapse
I'm on stock rom, but the problem is that i dont know how i can lock the bootloader ang going to s-on.
What steps should i follow?
Thanks for all the help
nurogo said:
I'm on stock rom, but the problem is that i dont know how i can lock the bootloader ang going to s-on.
What steps should i follow?
Thanks for all the help
Click to expand...
Click to collapse
At this point, how can i solve my problem?
Can anybody help me?
nurogo said:
At this point, how can i solve my problem?
Can anybody help me?
Click to expand...
Click to collapse
you need s-off so you can downgrade using a ruu, lock the bootloader and turn back s-on.
Try sunshine s-off and then follow nkk71's guide linke in my signature.
Hello,
I have just managed to unroot my htc one m7 successfully after a lot of difficulty.
However, the bootloader still shows "RELOCKED" although TAMPERED is gone but I would like it to show "LOCKED" as it was before I had rooted it for the first time. Is it possible to get it back to show LOCKED while you are S-ON?
Any help will be highly appreciated.
Thanks.
singh_harman said:
Is it possible to get it back to show LOCKED while you are S-ON?
Click to expand...
Click to collapse
No
Only possible with S-OFF.
alray said:
No
Only possible with S-OFF.
Click to expand...
Click to collapse
How about if you unlock the bootloader to go S-OFF in order to get it locked and then lock the bootloader again to show S-ON?
Is this possible.
Also, even if it remains relocked, does this void warranty at all? Or does it still get recognized as never been rooted.
singh_harman said:
How about if you unlock the bootloader to go S-OFF in order to get it locked and then lock the bootloader again to show S-ON?
Is this possible.
Click to expand...
Click to collapse
Yes, you'll need to unlock the bootloader, achieve s-off, set back the bootloader to locked and remove the tampered flag, flash a RUU and then turn back s-on.
Also, even if it remains relocked, does this void warranty at all?
Click to expand...
Click to collapse
Relocked means your bootloader was unlocked and locked back. Unlocking the bootloader might void your warranty light explained on htcdev.com/bootloader.
Or does it still get recognized as never been rooted.
Click to expand...
Click to collapse
Only a phone showing S-ON and ***LOCKED*** (and without ***tampered*** or ***security warning*** flags showing) is under warranty. And even if your phone only shows S-ON and LOCKED like if it was never unlocked, they (HTC) can still look for your IMEI# in their database and know if you already requested an Unlock_code.bin file from htcdev.com to unlock your bootloader (not a problem if you are dealing with your carrier but might be a problem if dealing directly with HTC).
alray said:
Yes, you'll need to unlock the bootloader, achieve s-off, set back the bootloader to locked and remove the tampered flag, flash a RUU and then turn back s-on.
Relocked means your bootloader was unlocked and locked back. Unlocking the bootloader might void your warranty light explained on htcdev.com/bootloader.
Only a phone showing S-ON and ***LOCKED*** (and without ***tampered*** or ***security warning*** flags showing) is under warranty. And even if your phone only shows S-ON and LOCKED like if it was never unlocked, they (HTC) can still look for your IMEI# in their database and know if you already requested an Unlock_code.bin file from htcdev.com to unlock your bootloader (not a problem if you are dealing with your carrier but might be a problem if dealing directly with HTC).
Click to expand...
Click to collapse
That is what I did, when going from root to unroot I had to first lock the bootloader and when I did so, the S-OFF went to S-ON by itself, so its not like I had to do something specific in order to achieve S-ON, similarly when you unlock the bootloader S-OFF comes by itself. Suppose I just unlocked and it is S-OFF, what fastboot commands will I need to input to lock it while S-OFF remains unchanged and does not go S-ON after locking?
When I locked the bootloader, tampered flag went away by itself too...
I want to lock it ensuring its S-OFF so that it shows locked rather than relocked. What commands will I need to achieve this output?
singh_harman said:
That is what I did, when going from root to unroot I had to first lock the bootloader and when I did so, the S-OFF went to S-ON by itself, so its not like I had to do something specific in order to achieve S-ON, similarly when you unlock the bootloader S-OFF comes by itself. Suppose I just unlocked and it is S-OFF, what fastboot commands will I need to input to lock it while S-OFF remains unchanged and does not go S-ON after locking?
When I locked the bootloader, tampered flag went away by itself too...
Click to expand...
Click to collapse
There is no possible way that happened. When you unlock your bootloader, you don't automaticaly get s-off, and only way to get back to s-on from s-off is with "fastboot oem write secureflag 3" command. You got something very wrong there my friend
singh_harman said:
I want to lock it ensuring its S-OFF so that it shows locked rather than relocked. What commands will I need to achieve this output?
Click to expand...
Click to collapse
with s-off it will be very easy to remove tampered and locked your device by using Guru reset tool , it has aroma ..
http://forum.xda-developers.com/showthread.php?t=2471869
I return back to full stock with no tampered and locked status for at least 3 m7 phones.
singh_harman said:
That is what I did, when going from root to unroot I had to first lock the bootloader and when I did so, the S-OFF went to S-ON by itself, so its not like I had to do something specific in order to achieve S-ON, similarly when you unlock the bootloader S-OFF comes by itself. Suppose I just unlocked and it is S-OFF, what fastboot commands will I need to input to lock it while S-OFF remains unchanged and does not go S-ON after locking?
When I locked the bootloader, tampered flag went away by itself too...
Click to expand...
Click to collapse
donkeykong1 said:
There is no possible way that happened. When you unlock your bootloader, you don't automaticaly get s-off, and only way to get back to s-on from s-off is with "fastboot oem write secureflag 3" command. You got something very wrong there my friend
Click to expand...
Click to collapse
^^This
Unlocking the bootloader doesn't set it S-OFF and re-locking it doesn't set it S-ON neither. Its 2 completely different things.