• 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

Yeah, it still keep rebooting. Here's what i did :

1) I unzipped ViperOne into my mini-sdk folder (making sure there's only one boot.img and only from the ViperOne).
2) I went to TWRP recovery -->factory reset --> installed ViperOne zip file --> successful and it asked me to reboot system and i did.
3) It keeps rebooting after managed to get to 2nd animated hTc screen.
4) I put my phone on FASTBOOT USB mode
5) Fastboot flash boot boot.img
6) Fastboot reboot --> my phone rebooting
7) Still stuck at 2nd animated hTc logo and keep rebooting
 
If that doesn't work, send us the information I suggested a few posts ago (fastboot getvar all) and we'll see if there's a suitable RUU.

I admit there's something about this I don't like - the way the problem started is very, very unusual, and is a bit of a worry.
 
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4282mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
 
Thanks. So that's an Asia WWE device (cid HTC__044), Android version 4.4.3 (from the version-main information plus a quick web search).

Unfortunately it's proving quite tricky to find an RUU which will work. The problem is that these things are ROM Upgrade Utilities, and won't let you use them to downgrade the software, and all the HTC_Asia WWE ones I can find are older software versions. There are some collections of RUUs in this thread, but I don't see anything there that I think will work.

If you were S-Off there would be more options, but you won't be able to take it S-Off without getting it booting, so that doesn't help.

I've also searched HTCdev (HTC's own developer resources site) but can't find anything.

The first post of this XDA thread does include a couple of HTC Asia "TWRP Nandroid Backups". These will be backups of the stock HTC Asia ROM (Jelly Bean by the look, so older than your current software) made using TWRP recovery. So if you were to download one, push it to your phone, then try to "restore" the backup using TWRP then it should install a stock ROM. Now I've no idea why your custom ROMs aren't working, so no guarantee this will either, but it's something else you could try.

I can't help feeling that we're missing part of the story here, but I suspect that it's part you don't know: the phone had clearly been modified before you had it, but we don't know what they did, and certainly have no way of telling now.
 
Alvanista said:
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.
Click to expand...

1. Download this: http://slimroms.net/index.php/downl...7/17938-slim-m7-4-4-4-build-9-0-official-8303
2. Put your phone in TWRP ( make sure it`s the latest, from the TWRP OFFICIAL website, not junk found in other places)
3. Do a data wipe in TWRP. ( Tap on Wipe -> then Swipe to confirm. NOTHING ELSE )
4. Open up a terminal. type this: adb push rom.zip /sdcard (where rom.zip is the one downloaded from the link)
5. Wait until it`s pushed on the phone. Grab a smoke.
6. In TWRP: Install-> ZIP-> Rom.zip. DO A DATA WIPE
7. Reboot into bootloader.
8. Extract the rom.zip. Put the boot.img into your adb folder.
9. fastboot flash boot boot.img
10. Wait.
11. Setup the phone. Get your SlimGapps.
 
@ Mod.
Why ? Becuase that`s a ROM that`s tested by me personally on THAT device, on THAT procedure ?
Jeez ... talk about helping a guy out.
Like SlimRoms would actually need your advertisement ...
But fine. Let him stay with a brick. Because you didn`t like the post.
 
r3w1NNNd said:
@ Mod.
Why ? Becuase that`s a ROM that`s tested by me personally on THAT device, on THAT procedure ?
Jeez ... talk about helping a guy out.
Like SlimRoms would actually need your advertisement ...
But fine. Let him stay with a brick. Because you didn`t like the post.
Click to expand...
It has nothing to do with liking the post or the rom. Neither was yours the only one.

The OP has flashed multiple roms and boot images and clearly has a deeper issue with the phone because nothing is working - and Hadron is trying to focus for a causal (causal, not casual) solution.

The answer in these cases is to not keep throwing roms at it until something sticks.

That's a disservice in cases like these.

Next time rather than derailing the thread some more to talk to "mod" with your personal complaint, tap my name and start a private conversation.

Thank you.
 
I just wish I could work out what the cause is. :(.

I've found an alternative thread for most of the files in that XDA link in another XDA post, but it has the same problem: the download site is offline (and was yesterday too, so I don't think it's a temporary glitch).

I don't suppose you know anything about the software that was on the phone before it broke? I'm just wondering whether there might have been some deeper modification made that we're unaware of (though the relocking sounds like the previous owner had tried to put it back to stock).

Just a crazy thought: what TWRP version were you using? Some versions have had problems with some phones or some ROMs. TWRP 2.6.3.3 has worked well for me with Jelly Bean (4.3) and KitKat (4.4), but I had to switch to 2.8.5 to flash a recent Lollipop (5.0) ROM (but 2.8.5 didn't work with my flash drive and OTG, which was a pain!). I didn't try the 2.7 versions, but it might be worth a shot. Now to be fair the sorts of problems people have reported have either been failure to install at all or some ROM features not working afterwards, rather than the sort of thing you've experienced, but if you were using the latest TWRP it might be worth trying 2.6.3.3 with ViperOne, as that combination has been generally reported to be unproblematic.

You've not had any error messages from any of the installs? It sounds like the phone thinks that everything has worked, but it behaves as if it's not installed cleanly.

I'm generally very sceptical of recipes which ask for multiple wipes (a ROM install will erase the system partition anyway, so I regard doing these things more than once as superstition), but right now if you want to format /system as well as wiping data and cache before flashing the ROM, feel free to give it a shot.

Sorry if this is a bit random, but this one is a bit puzzling.
 
Last edited:
The message "**Tampered** **Locked** ** Security warning**" means, in 99% of the cases, that the phone was at a certain point, UNLOCKED and ROOTED. After which, there was an RUU applied. The phone became "Tampered" this way.
What is indeed ODD is the LOCKED (instead of RE-LOCKED). Also, the fact that his BL is locked but he has a twerp on it makes me say what i said above, about the phone being rooted.
As coming from someone who works ( as in works - gets paid for ), do the following:
Unlock the BL ( via HTC dev)
Flash a new recovery ( via fastboot )
Flash a custom rom ( following the steps from the post that got delete - sorry bro, can`t help you there )
Reboot. It will work.

@Mod: He`s only shot is to revive that phone, one way or another. Set priorities. Can`t get to the "causal" solution, if the phone won`t boot up, can we now ? So, in this case, a casual solution is his best hope.

Good luck OP :)
 
Hadron said:
Though he did say in the first post that he unlocked it.
Click to expand...
Hmm ... Yeah ... he did say it ... I missed that.
Would need a confirmation from the OP. Does the phone say ***UNLOCKED*** in the Hboot ?
If that`s the case, his best chance is still to flash a slightly older TWRP ( for example 2.7.1.0/2.7.0.0 ), and try to revive it with a custom ROM. From there, we can revert it as close to stock as possible.
Also, a Sense Based stock rom ( as in NORMAL, STOCK, rooted ROM ) would be good, if AOSP based fails.
 
Yup, i did unlocked it and currently using this version openrecovery-twrp-2.8.5.0-m7.img. ill try using the suggested version 2.6.3.3 and let you know how's the result.
 
i flashed TWRP version 2.6.3.3 and version 2.7.0.0 but both stucked on hTc logo screen with entering recovery sentence above it. TWRP version 2.7.1.0 caused my phone to power off and showed battery image (meaning charging since my USB connected to my PC). Currently im downloading the SlimROM and it may take a while to finish.
 
r3w1NNNd said:
1. Download this: http://slimroms.net/index.php/downl...7/17938-slim-m7-4-4-4-build-9-0-official-8303
2. Put your phone in TWRP ( make sure it`s the latest, from the TWRP OFFICIAL website, not junk found in other places)
3. Do a data wipe in TWRP. ( Tap on Wipe -> then Swipe to confirm. NOTHING ELSE )
4. Open up a terminal. type this: adb push rom.zip /sdcard (where rom.zip is the one downloaded from the link)
5. Wait until it`s pushed on the phone. Grab a smoke.
6. In TWRP: Install-> ZIP-> Rom.zip. DO A DATA WIPE
7. Reboot into bootloader.
8. Extract the rom.zip. Put the boot.img into your adb folder.
9. fastboot flash boot boot.img
10. Wait.
11. Setup the phone. Get your SlimGapps.
Click to expand...

Oh my goodness. It works !! Thank you. I have no idea how it works but it works. Haha. It looks like Iph**. And now what should i do? Do you know how to restore back all my files, images etc ?
 
Please make a backup in recovery now. Might be worth trying to get s_off now as it gives you so much more options if things go wrong.
 
r3w1NNNd said:
What is indeed ODD is the LOCKED (instead of RE-LOCKED).
Click to expand...
Sounds to me like the phone was s-off at some point and returned to stock,and thrown off balance by something it has recently encountered,hence the locked display instead of relocked with the security warning

The fact that an AOSP Rom has booted suggests some partition damage that will likely only be fixed by an ruu.

You have m7_ul,so your device can easily be converted to Europe or us developer for which ruus are plentiful.

Since you have a working phone now,I'd do s-off so we can do the conversion. I'm not 100% sure if the current solution(sunshine) or some other will work in your scenario,so hopefully one of the guys here whose a bit more up to date with m7 can provide a bit more info there.

In a nutshell:
-s-off
-convert mid
-change cid
-run ruu

Hope that helps :)
 
@Mod: apologies accepted. :))))
@Alvanista: glad u saw the msg before it got removed
@scotty85 : Sunshine won`t work with 4.4.4. That IS a custom Rom, BUT Sunshine will work on 4.4.2. However, just to be safe, he can try Rumrunner, IF he`s willing to flash a 4.4.2 ROM.

EDIT: Coming after 19 hours of being awake. TLDR: instead of paying $25 for Sunshine, we can try a 4.4.2 Custom Rom
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom