• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [International] My HTC One M7 becomes tampered and locked. Please help

Alvanista

Newbie
Mar 5, 2015
20
1
Hello guys, im new to this forums and i need help for my HTC One, yesterday my phone suddenly jammed and i tried to reboot it many times till it came out a screen showed **Tampered** **Locked** ** Security warning** and i tried to search in how to remove the tampered screen because everytime i tried to reboot, the home screen did not come out and it keep rebooting many times showing the hTc logo.

Now after following some guides, i was able to unlock my HTC one phone and i read some of the guides that my phone need to be S-OFF ( it's still S-ON now), so i downloaded CWM for the recovery and managed to get to the recovery screen thingy when i try to install the zip from SDcard it said no files found and im stuck there till now. Please help me.
 
On that screen with "tampered" etc (which means it had been unlocked in the past) there would be a "hboot version". Can you tell us what that was - it's relevant if you want S-Off. Also what type of One do you have (GSM, Sprint, Verizon)?

Sorry that was a bit short - was on my phone in a rail station with limited time.

From the description it sounds like your ROM got corrupted somehow. I've never heard of this happening spontaneously, so would be interested to know what you were doing when this occurred - understanding the problem will help with finding a solution.

The word "tampered" did not appear spontaneously. That means that at some point in the past the phone has been unlocked and had the software modified. Did you do this, or did you ask someone else to root it, or did you buy it second-hand? I'm guessing you didn't do it yourself or else you'd have recognised the hboot screen. Again, I'm not being nosy, but trying to understand the state of the phone and how much you know about these operations.

The most important thing though is what you want to do. The word "tampered" only matters if the phone is still under warranty, and you only actually need S-Off to remove that word. So if you don't have (or don't care about) a warranty and just want to get the phone working S-Off is actually not that important. My guess is that to get the phone working again you just need to install a new ROM.

When you try to install "the zip" from recovery, which zip is this? Did you already have a ROM zip on the phone? Otherwise you'll need to download one and push it to the phone (via ADB while in recovery) before you can install it (or use a flash drive and an OTG cable).

The important thing is that ROMs are for specific phone models. There is more than one version of the M7, and some ROMs do not support all versions (hence some of the questions in my first post). So you need to choose one that's right for your phone, then get it onto the device as above. As part of the installation you will need to do a factory reset. As this will erase your apps and data (if those are still intact, which we can't know at the moment) you may want to do a backup first. The custom recovery (CWM) can do a backup of the whole phone - ROM, apps, data. You don't want to restore that backup (would return the phone to its current state), but the paid version of Titanium Backup can extract data from a recovery backup, so if you make a recovery backup (aka a "nandroid") you may be able to extract some of your data from it. If you are confident that your important data are backed-up somewhere already then don't worry about this bit.

Finally, some ROMs work better with some recoveries. So if you have trouble installing your preferred ROM using CWM, TWRP is actually more widely-used on the M7.

Good luck :)
 
Last edited:
Upvote 0
Thanks for the reply. my hboot was 1.57.0000. I was playing a game when suddenly my phone hang and i tried to switch off and switch on back and try to play the same game and it still hang, so i decided to switch off and switch on when suddenly the **tampered** **Locked** screen showed up. I have no idea what type of One im using now because it was not stated in the packages but it was made from Taiwan.

I never tried to modified software in my phone and im not an expert about the phone too. Im using it just to make a call, messaging and surfing the internet.

I read this article and it tells me that i need to be UNLOCKED and S-OFF
http://www.htc1guru.com/guides/guru-bootloader-reset/

Hence i went to this website and succesfully unlocked my phone
http://forum.xda-developers.com/showthread.php?t=2265618

After that i followed this video for my custom recovery
http://www.xda-developers.com/how-to-root-the-htc-one-m7-and-install-recovery-xda-developer-tv/
I managed to get into the CWM screen but unable to backup my files and i tried many times but it still showed FAILED to backup.

According to this website http://forum.xda-developers.com/showthread.php?t=2488772 , step 2 ask me to go to settings, and i am so confused because im still stuck in bootloop.

So i tried to follow this guide
http://androidforums.com/threads/bricked-htc-one-m8-help-asap.904630/
and i managed to flash TWRP openrecovery-twrp-2.8.5.0-m7.img , and tried to make a backup but it also failed and i just ignore it. I downloaded boot.img from Android_Revolution_HD-One_91.1_c699f4.zip and i managed to flash the boot but when i fastboot reboot, my phone rebooted but it stucked at the hTc logo for the whole one day.

Please help me.
 
Upvote 0
Sorry, very little time just now. You say you tried to flash ARHD 91.1, but you talk about "flashing boot" and doing a fastboot reboot which confuses me slightly. The way to flash that ROM is by copying it to the phone then using recovery, so I'm not sure what you were doing with fastboot. You also need to do a factory reset (though unlocking will have done that) or else it won't boot.

Your firmware is still KitKat (Android 4.4), but the ROM is Lollipop (5.0). It's possible there may be problems from that combination. If so the 3rd post of the ARHD thread at XDA has links to older versions (or says it has), or ViperOne is still KitKat based at the moment. But try to get the ROM booting first: force a shutdown (press and hold power until it restarts) and go into recovery and do a factory reset (data and cache). If that doesn't fix it, let us know how you installed the ROM and we'll see if we can spot the problem.
 
Upvote 0
I tried to do factory reset and reboot but still not working.
I tried to install my ROM by following this guide :
http://androidforums.com/threads/bricked-htc-one-m8-help-asap.904630/

Plug your phone into your pc, ensure that the phone says FASTBOOT USB highlighted.

Open a command window and say -
cd \sdk-tools

To reinstall TWRP -
fastboot flash recovery openrecovery-twrp-file-name-goes-here.img

Install the boot image, a common issue when s-on -
fastboot flash boot boot.img

Then,fastboot reboot.

p.s Suddenly my internal storage of the phone appeared on my PC (which previously did not) and sadly noted all my files are gone =(
 
Upvote 0
So where did you get the boot.img from? That's the Linux kernel, and has to be right for both phone and ROM (e.g. some kernels only work with HTC Sense ROMs, some only work with AOSP, and you will need a different kernel for an Android 5 ROM such as ARHD 91.1 from an Android 4.4 one). That all said, even when S-On the M7 ROMs come with the kernels and there's no need for a separate boot flash the way there was with some devices.

Also what you describe doesn't install a ROM, just the kernel. If you copy the ROM zip to the phone now and go into recovery you can try installing the ROM.
 
Last edited:
Upvote 0
  • Like
Reactions: Hadron
Upvote 0
I've tried to install the ROM from the TWRP by selecting install image and it stated there successful but then when i reboot my phone, it still stuck at the hTc logo.

I've tried all the steps from those threads but still not working. Please help me.
Did you go back to your pc and fastboot flash the boot.img?
 
Upvote 0
You'll find a number of different ROMs here.

I don't know whether your firmware might be a problem with a Lollipop ROM, but it might be worth trying a KitKat one. ViperOne is still KitKat at the moment (though that might be about to change this weekend).

Of course we don't actually know for sure that a new ROM will fix this - we don't know what actually happened here, just that the phone isn't dead but won't boot, hence hoping that a fresh ROM will fix it.

If it doesn't, then an RUU would be the next thing to try. If it comes to that (and it doesn't until a few ROMs have failed) could you use the fastboot command "fastboot getvar all" and post the output here (with your serial number and IMEI removed for security). That would help us work out whether there is a suitable RUU for your phone.

@EarlyMon: I really don't think he needs to fastboot flash a boot image. Even S-On M7 can flash kernels from recovery.
 
  • Like
Reactions: EarlyMon
Upvote 0
@EarlyMon: I really don't think he needs to fastboot flash a boot image. Even S-On M7 can flash kernels from recovery.

That's true for most HTCs - but I've found that some s-on phones are individually stubborn, so I thought I'd toss it out there. :)

(As well as some rom installer zips not being really as s-on aware as they claim - and why I hung a thanks on the ARHD suggestion. :))
 
  • Like
Reactions: Hadron
Upvote 0
Good point. @Alvanista, you tried flashing a boot.img earlier, but never told us which one it was (so we don't know whether it was suitable). If there's any doubt you could try unzipping a copy of the ROM (keep a zipped copy too!) and you'll find a boot.img in there. fastboot flash that and see whether that helps.
 
  • Like
Reactions: EarlyMon
Upvote 0
I previously flashed a boot.img from ARHD 91.1 ROM but it failed (which i had the zip file unzipped to get the boot.img)
I tried to install ARHD 91.1 ROM from TWRP and it was successful but stuck at hTc logo.
I tried to fastboot flash boot boot.img again and still not working (although the cmd showed OKAY).
Now im trying to download ViperOne.
 
Last edited:
Upvote 0
I previously flashed a boot.img from ARHD 91.1 ROM but it failed.
That's disturbing.

The phone was in FASTBOOT USB mode?

You put the boot.img in the same folder as fastboot and said?

fastboot flash boot boot.img

I recommend it after the rom install.

OK, enough from me. You were in good hands when I popped in checking threads for other things, so excuse me while I exit - too many cooks in the kitchen, bad thing, etc etc, cheers. :)
 
Last edited:
Upvote 0
Try the ARHD boot.img now, after you've installed the ROM. Just in case.

You did do a factory reset from recovery before installing the ROM? If not, go back to recovery and do one now.

Otherwise try Viper 7.0.2, which should be a better match to your firmware (though I'd not expect a firmware-ROM mismatch to produce quite such a dramatic problem).

If that doesn't work it's probably time to consider the full reflash ("RUU" = ROM Upgrade Utility).
 
Upvote 0
OK, I guess we try a different ROM to see whether that works better. If not then "fastboot getvar all" as described in post #11 and we'll see whether we can find a suitable RUU and reflash the phone completely? RUUs are Windows utilities, so do you have access to a Windows PC? I guess you do because you used a "\" in "cd \sdk" above, whereas Linux and OSX would use "/".
 
Upvote 0
Yes, I did these things :

1) On Fastboot USB mode
2) Then i proceed with factory reset from TWRP
3) Install ARHD from TWRP
4) Then i fastboot flash boot boot.img ARHD after i installed it (the boot.img in the same folder - in my case mini-sdk)

Still not working.
If that's really exactly what you did, these steps are wrong.

Fastboot flash must be done while in FASTBOOT USB mode - not after entering TWRP.

Boot back to fastboot mode from TWRP.


(sorry)
 
Last edited:
Upvote 0
OK i installed ViperOne and managed to get to the 2nd screen of hTc logo (the moving one) and after that my phone keep rebooting by itself.
I hate to sound like a broken record but -

Get the boot.img from the Viper rom, put the phone in FASTBOOT USB mode, not TWRP, and

fastboot flash boot boot.img

Bootlooping after a rom flash on an HTC is a boot.img problem.
 
Upvote 0
I'm going to assume that you took the boot.img from the Viper rom and aren't using the old one you had in the fastboot folder from earlier - boot images being not interchangeable.

And that you've checked the folder and don't have some multiple file confusion with a "boot (1).img" file in there as well (which - if you do, remove all boot image files, get the Viper one so it's the only one there and try the fastboot flash again).

Assuming both of the above, reflash your Viper rom.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones