Database Develop

Security Warning when installing OTA Update?

I'll explain what I did, Downgraded to 2.3.4 and 2.1 HBOOT 1.13, I S-OFF then S-ON again (I was bored)
So with S-ON again I did the OTA to 2.3.5 and 3.0 downloaded fine, rebooted and came up in HBOOT with a security warning message at the top of the HBOOT menu. What happened? Is it showing S-OFF but its actually not?

Just checked and its still rooted even though it says S-OFF, How do we unroot?

slugger09 said:
Just checked and its still rooted even though it says S-OFF, How do we unroot?
Click to expand...
Click to collapse
Show us the complete HBOOT screen please.
How did you gain S-OFF on HBOOT 1.13 and how did you get S-ON back on?
If you still have S-OFF, what is the HBOOT version?

S-Off using Alphavex or what ever its called. S-on using a guide on here titled Get S-on for warranty. Physically it looks like s is on but superuser etc titanium still work so its still rooted.

slugger09 said:
S-Off using Alphavex or what ever its called. S-on using a guide on here titled Get S-on for warranty. Physically it looks like s is on but superuser etc titanium still work so its still rooted.
Click to expand...
Click to collapse
Yes that is entirely possible. The steps you followed simply removed the Revolutionary S-OFF HBOOT and restored a HTC HBOOT which removed S-OFF.
This process did not remove the superuser binary, thus the ROM you have in place is still rooted.
I also noticed that on the S-ON thread you referenced, the OP stated that this could leave you with the SECURITY WARNING on the HBOOT screen and there is a link on how to fix that.
So I believe that the SECURITY WARNING occurred during the S-OFF -> S-ON process and not because you installed the OTA.

Interesting, I got around the issue by getting stock 3.0 rom renaming it PG32IMG etc, worked fine, But now the dreaded ***RELOCKED*** has come back, So I suspect HBOOT 2.0 Can detect if you ever unlocked your bootloader in the past, the rest can't.

[Q] preserve s-off, locked status on stock 1.54

Hi, I recently got a new HTC One sim free, shipped with 1.54 bootloader from HTC. I knew that revone/moonshine do not enable s-off with 1.54 so I shipped the device off for s-off to fonefunshop and got them to do s-off and supercid on the device. Before shipping it off I rooted and installed twrp recovery.
When I received the device back, it still has the shipped rom on it, along with a few apps I installed. TWRP is still installed its still rooted. The bootloader is showing that its locked (not relocked), but it still shows the tampered flag.
Q1. What is the best way of getting rid of the tampered flag and keeping s-off, and locked status (not relocked).
Q2. If the above is possible will I be able to get OTA's without loosing s-off or locked?
The bootloader currently looks as follows:
*** TAMPERED ***
*** LOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.401.8
eMMC-boot 2048MB
Aug 9 2013, 16:15:36.22931
Jun 22 2013,00:54:00.0
I really dont want to lose s-off, or get to relocked status again if possible.
Apologies if this has been answered elsewhere, I did search, but because s-off was not achieved with moonshine/revone I am a little unsure how to proceed.

Getting rid of the tampered flag is simple but fraught with problems
Flashing modified hboots is risky at the best of times..... if you try to go back to s-on or relock then you will brick your device. You will need to flash the original hboot if you want to go back.
Look at Vomers thread
http://forum.xda-developers.com/showthread.php?t=2365506&page=4

1.54 s-off yaaaaaaaaaaaaaaay
Hi,
I fixed this with my funfoneshop buddies.
Just flashed an old RUU and after 5 OTA's 1.54, still s-off, locked, and no tampered flag.
Just in case someone else gets the same problem.

Was just gonna say use the 1.28.401.7 RUU and then OTA it until at 2.24.401.8 but you've sorted it out so it's all good

[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.

[Q] Restore M7 to stock - Q on HBOOT

Hi I need to restore my HTC One M7 European to stock, since I want to return it for repair of the purple tint issue. My question is what HBOOT is now the "official" from HTC Europe, so I can choose the right one.
When I got the phone in summer 2013 I initially just followed the OTA upates. In December I converted to Google GPE to get KitKat faster (and also later got Lolipop). This involved getting S-OFF etc.
Phone info before I converted (December 2013) - had HBOOT 1.55.
M7_UL PVT SHIP SON RH
HBOOT 1.55
RADIO 4A.21.3263.04
OpenDSP-32.120.274.0909
OS-3.62.401.1
eMMC boot 2048MB
Oct 17 2013
Used RumRunner to get S-OFF, change cid etc. and convert to GPE. Then followed OTA updates for a while, including upgrade to Lolipop. Status today:
M7_UL PVT SHIP S-OFF RH
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4T.30.3218.21
OpenDSP-v34.120.274.0429
OS-5.11.1700.3
eMMC-boot 2048MB
Dec 2 2014 22:11:20.0
So I'm actually on a lower HBOOT now than before I did any hacking.
Questinon is - if I had followed the official upgrade cycle would I still be at HBOOT-1.55?
Here's my idea for reverting this phone to stock:
1) Rewrite CID to original
2) Install suitable KitKat RUU
3) Upgrade to HBOOT 1.55 (since this was the original - I'm wondering if I get 1.55 automatically through step #2 though).
4) fastboot oem writesecureflag 3 (in order to return to S-ON)
5) Install OTA updates
Will the phone now be in the same state as if I had not done any hacking? I've also seen people somewhere suggest you need HBOOT-1.44 to get S-ON back. Is that true? If so, can I downgrade to 1.44, put S-ON and then upgrade to 1.55? Also what about the other elements in the list (OpenDSP etc.) will they return to stock via the RUU? The trouble is I have no way to tell what the values would have been if I had not hacked the phone and had just followed official OTA's.
Any help will be much appreciated. I'm a bit confused over HBOOT issues.

kenzorio said:
Hi I need to restore my HTC One M7 European to stock, since I want to return it for repair of the purple tint issue. My question is what HBOOT is now the "official" from HTC Europe, so I can choose the right one.
When I got the phone in summer 2013 I initially just followed the OTA upates. In December I converted to Google GPE to get KitKat faster (and also later got Lolipop). This involved getting S-OFF etc.
Phone info before I converted (December 2013) - had HBOOT 1.55.
M7_UL PVT SHIP SON RH
HBOOT 1.55
RADIO 4A.21.3263.04
OpenDSP-32.120.274.0909
OS-3.62.401.1
eMMC boot 2048MB
Oct 17 2013
Used RumRunner to get S-OFF, change cid etc. and convert to GPE. Then followed OTA updates for a while, including upgrade to Lolipop. Status today:
M7_UL PVT SHIP S-OFF RH
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4T.30.3218.21
OpenDSP-v34.120.274.0429
OS-5.11.1700.3
eMMC-boot 2048MB
Dec 2 2014 22:11:20.0
So I'm actually on a lower HBOOT now than before I did any hacking.
Questinon is - if I had followed the official upgrade cycle would I still be at HBOOT-1.55?
Here's my idea for reverting this phone to stock:
1) Rewrite CID to original
2) Install suitable KitKat RUU
3) Upgrade to HBOOT 1.55 (since this was the original - I'm wondering if I get 1.55 automatically through step #2 though).
4) fastboot oem writesecureflag 3 (in order to return to S-ON)
5) Install OTA updates
Will the phone now be in the same state as if I had not done any hacking? I've also seen people somewhere suggest you need HBOOT-1.44 to get S-ON back. Is that true? If so, can I downgrade to 1.44, put S-ON and then upgrade to 1.55? Also what about the other elements in the list (OpenDSP etc.) will they return to stock via the RUU? The trouble is I have no way to tell what the values would have been if I had not hacked the phone and had just followed official OTA's.
Any help will be much appreciated. I'm a bit confused over HBOOT issues.
Click to expand...
Click to collapse
DO NOT GO S-ON EVER !!!
DO NOT RELOCK YOUR BOOTLOADER (you will never get it unlocked again)
Hboot 1.54 is what all GPe phone's have
Simply change your CID and MID back to what they were and flash a RUU and your back to Sense Firmware with the hboot in that RUU
theirs a full guide for returning to stock here >> http://forum.xda-developers.com/showthread.php?t=2541082

clsA said:
DO NOT GO S-ON EVER !!!
DO NOT RELOCK YOUR BOOTLOADER (you will never get it unlocked again)
Hboot 1.54 is what all GPe phone's have
Simply change your CID and MID back to what they were and flash a RUU and your back to Sense Firmware with the hboot in that RUU
theirs a full guide for returning to stock here >> http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Hi thanks. I had great troubles using the KitKat RUU. I suspected it was due to incompatibility with HBOOT. Downgraded HBOOT to 1.44, still didn't work. Then instead I used an RUU for Jelly Bean (in fact the original image) and this worked like a charm. Then I've applied a tons of OTA updates and now I'm on HBOOT 1.54. But now I'm stuck because it can't find the 4.19.401.11 update on HTC's server! I guess they have simply removed it and most people aren't bothered because they are way past.
BTW, why would it be a problem to go S-ON? Can't I go S-OFF again using the same method I originally used (using Rumrunner etc.)? Why would this S-ON be more permanent than a factory S-ON? I need to be S-ON to send the phone into service.

kenzorio said:
Hi thanks. I had great troubles using the KitKat RUU. I suspected it was due to incompatibility with HBOOT. Downgraded HBOOT to 1.44, still didn't work. Then instead I used an RUU for Jelly Bean (in fact the original image) and this worked like a charm. Then I've applied a tons of OTA updates and now I'm on HBOOT 1.54. But now I'm stuck because it can't find the 4.19.401.11 update on HTC's server! I guess they have simply removed it and most people aren't bothered because they are way past.
BTW, why would it be a problem to go S-ON? Can't I go S-OFF again using the same method I originally used (using Rumrunner etc.)? Why would this S-ON be more permanent than a factory S-ON? I need to be S-ON to send the phone into service.
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/ota_m7_...19-401-11_release_372404wj19h95c0x6oa19n-zip/
if not helped Run this RUU http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/ then try to update

[Q] Can't S-OFF, tried everything!

Hey guys,
I know there are threads everywhere like this, but all I want to do is take my M7 back to stock and sell it. I've tried everything I've seen and I'm frustrated. I have root with SuperSU and TWRP recovery. I had S-OFF with an unlocked bootloader and stock Lollipop, then used revone to set the lock flag and set S-ON and remove tampered. Then I hit factory reset in bootloader, which was a huge mistake because now it's S-ON and tampered.
Since then I've tried revone, and setting the -P flag does not work, and running ./revone -s 0 -u on my mac doesn't work either. I'm running revone with su. I've also tried rumrunner in Windows on VMWare, which never gets past the sanitizing stage (even though SuperUser is granting permission to 'id'), and it just displays TTTTT**************** and press Enter to Exit.
I've also tried both locked and unlocked, and I had a newer hboot before and it didn't work either.
Here's my bootloader:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.60.0000
RADIO-1.01.20.1225
OpenDSP-v35.120.274.0718
OS-6.16.651.2
eMC-boot 2048MB
Jan 9 2015,22:07:44.0
I'm out of ideas and I just want the quickest way to be done with this phone and sell it.
Thanks in advance!

Lock the bootloader and flash the 7.x RUU and forget about it
Only HTC cares about the phone saying Tampered / Relocked no one else cares

Ok I guess. Was hoping there's a simple way to do it because the phone just sold and I hadn't posted that it has a tampered flag. Is this the RUU I should use? http://forum.xda-developers.com/showthread.php?t=2658910. I need a decryped version I can install with Mac because I'm not having luck with the Windows RUUs in VMWare.

Sunshine s off is your only chance with hboot 1.60

How can I upgrade hboot to have more options? Also, is that that the right RUU to use? Lastly, trying to relock bootloader with revone and that's not working now.
Thanks for the help!

Sunshine is the only option for hboot 1.57 and up. Upgrading hboot won't give you more options. Revone is only to be used with hboot 1.44. If you want to relock then use fastboot oem lock. And no this is not the right ruu. It must be same version or higher when s-on.