hey guys, I plan to sell my one as I just bough the nexus 5, and I want to return the phone back to stock. However,the link in the faq seems to refer more towards the boot loader text, not the splash screen warning message. Would running of the RUU get rid of it? I am s-off.
Sorry updated my post to be more clear was driving when I wrote it.
If the red text states things about it being a developmental devices then that is due to your device being S-Off. Once you re-enable the security flag then it will disappear but you need to do this while rooted so you can then use Revone to remove "Tampered" and to "Lock" the device instead of "Relock".
Simply changing the s-off flag will get rid of the message on the splash screen when you boot the phone?
EPayne123 said:
If the red text states things about it being a developmental devices then that is due to your device being S-Off. Once you re-enable the security flag then it will disappear but you need to do this while rooted so you can then use Revone to remove "Tampered" and to "Lock" the device instead of "Relock".
Click to expand...
Click to collapse
Actually I think it will work even if he isnt rooted, in fact I would recommend flashing the stock ruu first then use the write secure flag command. Its always confusing to figure out which lock command from revone locks the bootloader and which one relocks the bootloader lol
Related
I was just wondering, I have the HTC ONE/ M7 and I was trying to root it but was never successful. I unlocked it with the HTCDev website and installed GOO on my phone but thats about as far as I got. Now my phone shows **TAMPERED** and **UNLOCKED** in the HBOOT menu, I was just curious as to how I would get those to go away.
THANKS!
I believe you have to wait for s-off so you can downgrade hboot to remove that message.
Flashing back the stock firmware (RUU) will remove the tampered but it will always say relocked if you locked the bootloader again.
What does S-off mean? Sorry I'm really new to this, I know it's probably a dumb question. Is going back to the factory firmware a long process?
Sent from my HTC One using xda app-developers app
Tampered can be removed when you flash the official RUU.
Relocked cant be as of now. And I have no hopes for it to happen in device's life cycle as well.
So how would I flash it? Is there a general way or is it device specific?
Sent from my HTC One using xda app-developers app
Take a look through this:
http://forum.xda-developers.com/showthread.php?t=2265618
When you rooted your phone it added tampered and unlocked in bootloader menu.
If you want to take them out you will have to unroot your phone or wait for s-off (it will fully unlock the phone)
I didn't have the tampered message on my rooted OneX,it must be something new as well as the red warning in booting the phone that it's a dev phone that must not be sold
There is a thread with RUU archive for each device. Check for specific RUU for your specific carrier make or model.
But if you install RUU you will have phone that is as good as stock phone. You will lose root and will have to re-root it.
Dont bother with it unless you have to go back to factory condition.
There are also zipped versions of stock ROMs available so you can try those if you have CWM or TWRP installed successfully.
You dont really need to remove that tampered / unlocked status. It does not hinder your phone in any way. You have already lost your warranty and even if you relock your bootloader and remove Tampered message by flashing factory RUU, your phone will still show RELOCKED message. So point going back unless as I said you must have factory condition phone.
Hi~!
So does this mean the factory will always know that our phones are rooted with S ON?
TrueYears said:
Hi~!
So does this mean the factory will always know that our phones are rooted with S ON?
Click to expand...
Click to collapse
Yes HTC will know for sure the phone has been tampered with and unless s-off is achieved for the masses which does not involve taking the phone apart then it will always say tampered, unlocked, relocked.
Oh, okay, thank you, my phone has vibrating problems, with the intensity, in some hits, the vibrating just keeps going slowly fading in. I read somewhere that 1.29 fixes this but its isnt out around my region yet and I dont want to flash this 1.29 stock rom to find out its a hardware issue and lose my warranty
Spacky03 said:
What does S-off mean? Sorry I'm really new to this, I know it's probably a dumb question. Is going back to the factory firmware a long process?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Security-Off if what it officially means. Means you can write to the bootloader and mod things
Title says all.
anonymousthing said:
Title says all.
Click to expand...
Click to collapse
Can you get to the bootloader screen by hold Volume Down + Power button?
If not, then no.
Yes, I can. But when I try and flash the stock HBOOT back, it says 'can not roll back hboot version'.
I'm trying to restore the stock HBOOT so I can send it in for warranty without big black "Blackrose" text along the top
anonymousthing said:
Yes, I can. But when I try and flash the stock HBOOT back, it says 'can not roll back hboot version'.
I'm trying to restore the stock HBOOT so I can send it in for warranty without big black "Blackrose" text along the top
Click to expand...
Click to collapse
I think you have to uninstall Blackrose before you can restore anything, open the Blackrose program, there should be an option to uninstall
Gizmo648 said:
I think you have to uninstall Blackrose before you can restore anything, open the Blackrose program, there should be an option to uninstall
Click to expand...
Click to collapse
I believe Blackrose gave a similar error, though I'll need to go check the specifics
anonymousthing said:
I believe Blackrose gave a similar error, though I'll need to go check the specifics
Click to expand...
Click to collapse
Yes if you have BlackRose S-OFF HBOOT, the only way to replace it is to run the BlackRose installer with the /uninstall option.
Very strange - I booted into CWM recovery and when I run adb devices, it detects my phone
But when I run BlackRose_IS.exe /uninstall, it gives *Waiting for device* and stays stuck there. Any ideas? Can BlackRose even be installed/uninstalled from recovery? :\
Never mind, I have successfully removed Blackrose by booting into an SD card bootable CM7.1 image, then using terminal emulator and dd to force write a new hboot. I tried writing the stock hboot that came with the virgin mobile RUU, but now I'm getting "security warning" and I'm stuck to the bootloader. I'll search through the forums now for what to do... thanks guys anyway!
anonymousthing said:
Never mind, I have successfully removed Blackrose by booting into an SD card bootable CM7.1 image, then using terminal emulator and dd to force write a new hboot. I tried writing the stock hboot that came with the virgin mobile RUU, but now I'm getting "security warning" and I'm stuck to the bootloader. I'll search through the forums now for what to do... thanks guys anyway!
Click to expand...
Click to collapse
With the security warning you should now be able to flash the official HTC ICS RUU.
Yup, I successfully flashed it and now it's back to what appears to be the factory settings, so hopefully the service guy will replace my mobo when I send it in.
On a side note, does the bootloader, when locked by HTC (and you unlock using htcdev.com) normally say *LOCKED* along the top? Mine doesn't say this (I don't really care about getting that back anyway, just wondering)
anonymousthing said:
Yup, I successfully flashed it and now it's back to what appears to be the factory settings, so hopefully the service guy will replace my mobo when I send it in.
On a side note, does the bootloader, when locked by HTC (and you unlock using htcdev.com) normally say *LOCKED* along the top? Mine doesn't say this (I don't really care about getting that back anyway, just wondering)
Click to expand...
Click to collapse
There are 3 statuses: "LOCKED", "UNLOCKED" and "RELOCKED" if your HBOOT is 2.00.0000 or above. If your HBOOT is version 1.13.0000 or 1.16.0000, then they did not show that type of status on the HBOOT screen.
[Q] what triggers "TAMPERED", "SECURITY WARNING", and red text on boot
Hi Guys and Gals,
So I'm really trying to understand what triggers "TAMPERED", "SECURITY WARNING" (though I haven't seen it), and the red text on bootup, and how to undo them.
It was my general understanding that these are caused by a custom recovery, and in theory should disappear when you relfash stock rom and stock recovery, and possibly relock booltoader.
For some this seems to work, for others not.
I'm not looking for the methods using S-Off, such as revone -t or modified hboots. Just the general requirements (short of running RUU), that would allow these flags to go back to normal.
Thanks
The tampered flag seems to pop up when you're using a non-stock recovery, or have changed something in the ROM. Same with the red warning text on the splash screen. As soon as you flash a custom recovery (but leave the ROM 100% stock) you get the 'this is a test build, etc.' warning come up
If you're S-OFF, there are guides in General on how to remove these warnings (and not using revone too), e.g. to remove the tampered label, read this http://forum.xda-developers.com/showthread.php?t=2477792
EddyOS said:
The tampered flag seems to pop up when you're using a non-stock recovery, or have changed something in the ROM. Same with the red warning text on the splash screen. As soon as you flash a custom recovery (but leave the ROM 100% stock) you get the 'this is a test build, etc.' warning come up
Click to expand...
Click to collapse
Agreed, but shouldn't going back to a 100% stock ROM and 100% stock RECOVERY, remove the "this is a test build" and TAMPERED. or do these stay in either case because you did "at one point in time" use a custom recovery?
I've read people returning to stock, where these have gone away, and for other people they stayed.
I know you can achieve this with S-Off, but I'm just trying to understand the basic "logic" of these warnings, and when (and when not) they will appear.
I'm bumping this for more info. Still no conclusive results.
Sent from my HTC One using xda app-developers app
Unsigned kernel or recovery causes tampered warning, flashing RUU will clear tampered.
Sent from a van down by the river.
When I unlocked my phone, there was no TAMPERED message until I flashed a custom recovery
akuma24 said:
When I unlocked my phone, there was no TAMPERED message until I flashed a custom recovery
Click to expand...
Click to collapse
mine (TAMPERED message) never goes away even with a stock recovery and no root
not until i got s-off and run the adb command
So I was trying to restore my HTC one back to normal stocks, with both tampered gone and for it to say Locked again. I haven't used the phone in a few months (switched to a Nexus 5). All I had done with it was unlock the bootloader, install TWRP, and use some random ROMs, with the last one on there being a pretty old version of the Insert Coin Rom, which was based on one of the leaked 4.2.2 OTAs prior to its release.
So what I had read that I needed to do was use revone to get S-OFF. At first I was having issues, repeatedly getting error code = -1. I was able to do the " ./revone -P " command, which would say success and then waiting for device reboot. After this, when trying to run any command I would get that error code. Somehow I got it to work, but on the wrong command (at least I think): " ./revone -l " which then relocked my bootloader. From my limited knowledge, I believe that you need to be complete stock so that it will work. Well as I said, I'm not, so I now have "security warning" with both S-On and the bootloader being Locked (not relocked) and Tampered.
I can't get fastboot to detect the phone, nor does an RUU detect it. I'm just stuck in the bootloader.
I'm on hboot 1.44 and got the phone around June I believe although I'm not sure. It's an AT&T variant, so perhaps I had a patched hboot?
Anyways, any help is much appreciated!
SniperofFear said:
So I was trying to restore my HTC one back to normal stocks, with both tampered gone and for it to say Locked again. I haven't used the phone in a few months (switched to a Nexus 5). All I had done with it was unlock the bootloader, install TWRP, and use some random ROMs, with the last one on there being a pretty old version of the Insert Coin Rom, which was based on one of the leaked 4.2.2 OTAs prior to its release.
So what I had read that I needed to do was use revone to get S-OFF. At first I was having issues, repeatedly getting error code = -1. I was able to do the " ./revone -P " command, which would say success and then waiting for device reboot. After this, when trying to run any command I would get that error code. Somehow I got it to work, but on the wrong command (at least I think): " ./revone -l " which then relocked my bootloader. From my limited knowledge, I believe that you need to be complete stock so that it will work. Well as I said, I'm not, so I now have "security warning" with both S-On and the bootloader being Locked (not relocked) and Tampered.
I can't get fastboot to detect the phone, nor does an RUU detect it. I'm just stuck in the bootloader.
I'm on hboot 1.44 and got the phone around June I believe although I'm not sure. It's an AT&T variant, so perhaps I had a patched hboot?
Anyways, any help is much appreciated!
Click to expand...
Click to collapse
Uninstall Htc sync, driver htc, reinstall Driver htc. reset computer . Go to bootloader on device, connect USB.
hoangvanchung said:
Uninstall Htc sync, driver htc, reinstall Driver htc. reset computer . Go to bootloader on device, connect USB.
Click to expand...
Click to collapse
It still shows up as an unrecognized usb device.
Edit: of course the issue is windows 8. testing on win 7 laptop currently...
SniperofFear said:
It still shows up as an unrecognized usb device.
Edit: of course the issue is windows 8. testing on win 7 laptop currently...
Click to expand...
Click to collapse
did you ever figure this one out? I am stuck here
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.