[Q] preserve s-off, locked status on stock 1.54 - One (M7) Q&A, Help & Troubleshooting

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

Related

[Q] Phone relocked, s-off but unable to flash to stock

Hi All
I am new to the forums but i have searched and searched for the answer to my predicament to find only part answers and so on.....So here it goes:
Basically i unrooted my device and want to unroot back to stock so that i can return the phone. I have Relocked the bootloader and got S-Off but beyond this any RUU file that i try to flash to the phone it comes back with errors and does not allow it. When it is in the developer menus of fastboot,recovery etc it states this:
*** Tampered ***
*** Relocked ***
M7_UPL PVT SHIP S-OFF RH
CID-HTC__001
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.0
I bought my Phone unlocked and i live in the UK!
I am unable to do system update, i cannot flash a RUU to the phone. I am completely lost and like i said i have looked and there are answers for other problems but not this in particular.
Any Help would be greatly appreciated :good:
I found out the issue, it was that I hadn't changed the cid. Only issue is that I'm unable to do software update when back to stock....
So just flashed a 4.3 jelly beans version
Sent from my HTC One using xda app-developers app

Help ! Keep on getting ruu error 155 flashing htc one back to stock

Thx for all your kindness, I'm completely new and noob here and i keep getting ruu error 155 while flashing my htc one back to stock.
I'm using an Asia wwe model, I have already unlock the bootloader and use both Asia wwe RUU from here: http://forum.xda-developers.com/showthread.php?p=39588860.
But i still can't update my phone. Here is the information shown in my bootloader screen:
Relocked
M7_UL PVT SHIP S-ON RH
HBOOT-1.55 0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.63.707.3
eMMc-boot 2048MB
Oct 30 2013,20:18:02.19197
I relock the bootloader , tick allow usb debugging in developer setting, boot into fastboot usb mode and run the ruu as admin, and it wont work. I really need help for this.
Your help will be much appreciate !!!
you need s-off and 1.44 hboot dude
Yeah, Ive just been through all this yesterday. My advice. Well, the safest option is to flash a guru reset rom through your custom recovery from http://www.htc1guru.com/downloads/stock-rom-downloads/. It basically takes your rom and recovery back to stock. I think HTC must've built in protection to the RUU to prevent flashing under Hboot 1.55 to prevent failure of the touch screen........I didn't want to start messing with downgrading bootloaders so I flashed Guru's reset.....I'm now on stock with S-off and "Locked" bootloader.....which GURU also has a flashable zip for.... once again, flash it in recovery....also removes tampered flag if you've got that. Get that here http://www.htc1guru.com/guides/guru-bootloader-reset/
EDIT. Just noticed your S-ON...you need to be S-OFF to do all the above, sorry man.

[Q] Converting to Stock from Carrier Version

I've got a HTC One from EE (UK), who are being retardedly slow in providing updates.
So I'd like to change to a stock HTC and still receive OTA updates. I'd prefer not to change to Google Play Edition if possible.
My bootloader currently says:
*** TAMPERED ***
*** LOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-HTC__001
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-V32.120.274.0909
OS-
eMMC-boot 2048MB
I've got TWRP installed v2.7.1.1
I've also changed my CID to HTC__0001 and also the MID to PC0710000 using the MID Change tool.
Its currently running Android v4.3, HTC Sense 5.5 and Software 3.63.61.1.
What do I need to do next? I *think* I need to install a RUU? but not sure.
cjb110 said:
I've got a HTC One from EE (UK), who are being retardedly slow in providing updates.
So I'd like to change to a stock HTC and still receive OTA updates. I'd prefer not to change to Google Play Edition if possible.
My bootloader currently says:
*** TAMPERED ***
*** LOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-HTC__001
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-V32.120.274.0909
OS-
eMMC-boot 2048MB
I've got TWRP installed v2.7.1.1
I've also changed my CID to HTC__0001 and also the MID to PC0710000 using the MID Change tool.
Its currently running Android v4.3, HTC Sense 5.5 and Software 3.63.61.1.
What do I need to do next? I *think* I need to install a RUU? but not sure.
Click to expand...
Click to collapse
You are right, you now need to run the .401 ruu. Just to be sure, you said you have changed your CID to HTC__0001 ? Its HTC__001 (only 8 characters)
stay s-off and bootloader unlocked after the conversion.
your twrp recovery will be overwritten with the stock recovery included in the RUU.
I did exactly the same thing with my Vodafone branded one, best move I ever made, I got the update a month before Vodafone started sharing it.
Just make sure you backup your current Rom and take note or remember your original cid should the worst happen and you need to return it for any reason, copy the backup , once created, to your pc before running the ruu.
I'm on EE too and in the process of grabbing all the files needed for this. My fone is 100% stock so need to unlock, root and S-Off yet.
I grabbed the RUU from here. 1.5GB. HTC Europe
http://forum.xda-developers.com/showthread.php?t=2428276
Thanks, all done now.
Sweet. All go ok? No problems?
Might get time to do mine later this week.

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

Categories

Resources