[Q] - Need immediate help on removing "TAMPERED" and "RELOCKED" text on boot
Hello,
I bought a HTC ONE M7 about 2 month ago. After two week of using phone, I decided to use my phone on 3G network but faced a problem.
When I use a 3G network, I can send and receive SMS, also can receive CALLs, but I can't make out going CALLs. After dialing, call ended immediately! I have this problem also on 2G network in some areas of our city. I checked my SIM on another phones (Nokia N97 and Samsung Galaxy S3) and worked fine.
I thought this may be a bug on software, and wait for 4.2.2. After installing OTA, the problem is still remained.
Now I decided to send it to warranty. But I think there is a problem. I UNLOCKED my phone from HTCDEV.com and RELOCKED again. I do it, because they wrote on the warning this "MAY' void your warranty. Now my phone has a "TAMPERED" and "RELOCKED" text on hboot.
How can I remove them and take my phone to fully stocked as 1st day?
Regards.
komsboy_more said:
Hello,
I bought a HTC ONE M7 about 2 month ago. After two week of using phone, I decided to use my phone on 3G network but faced a problem.
When I use a 3G network, I can send and receive SMS, also can receive CALLs, but I can't make out going CALLs. After dialing, call ended immediately! I have this problem also on 2G network in some areas of our city. I checked my SIM on another phones (Nokia N97 and Samsung Galaxy S3) and worked fine.
I thought this may be a bug on software, and wait for 4.2.2. After installing OTA, the problem is still remained.
Now I decided to send it to warranty. But I think there is a problem. I UNLOCKED my phone from HTCDEC.com and RELOCKED again. I do it, because they wrote on the warning this "MAY' void your warranty. Now my phone has a "TAMPERED" and "RELOCKED" text on hboot.
How can I remove them and take my phone to fully stocked as 1st day?
Regards.
Click to expand...
Click to collapse
Use the Revone toolkit if you can to gain s-on and to remove the relock and then flash with stock RUU.
This should be sufficiant to fool them in to believing that the phone is stock
gazlufc said:
Use the Revone toolkit if you can to gain s-on and to remove the relock and then flash with stock RUU.
This should be sufficiant to fool them in to believing that the phone is stock
Click to expand...
Click to collapse
Thanks you, but there is no RUU exe !
Version : 2.24.401.1
komsboy_more said:
Thanks you, but there is no RUU exe !
Version : 2.24.401.1
Click to expand...
Click to collapse
Use an older RUU and then try to update the device OTA.
Should work if i'm not mistaken.
gazlufc said:
Use an older RUU and then try to update the device OTA.
Should work if i'm not mistaken.
Click to expand...
Click to collapse
When I use an Older RUU, I receive ERROR! After searching, it seems that can't install older RUU to downgrade!
Even if it doesn't update right away, it's not a crime to have an older o's on your device. My girlfriends dad never updates his phones
Sent from my YP-G70 using Tapatalk 2
dB Zac said:
Even if it doesn't update right away, it's not a crime to have an older o's on your device. My girlfriends dad never updates his phones
Sent from my YP-G70 using Tapatalk 2
Click to expand...
Click to collapse
No it's no problem having older Firmware, aslong as it's not Modified, Has root Access or is S-Off.
So for warranty purpose it should be fine.
I know I accepted devices that haddent been updated when I was a repair agent
gazlufc said:
No it's no problem having older Firmware, aslong as it's not Modified, Has root Access or is S-Off.
So for warranty purpose it should be fine.
I know I accepted devices that haddent been updated when I was a repair agent
Click to expand...
Click to collapse
So do you have any solution for me ?
komsboy_more said:
So do you have any solution for me ?
Click to expand...
Click to collapse
I think you have to have S-off to go back to older firmware/RUU
maxal said:
I think you have to have S-off to go back to older firmware/RUU
Click to expand...
Click to collapse
Can I go S-OFF from whis guide ? :http://forum.xda-developers.com/showthread.php?t=2314582
Is it usable on windows ? ... I think CHMOD command is a linux command.
And for last question... If I go S-OFF then downgrade RUU and then update again, the "TAMPERED" text will removed ? and "RELOCKED" will changed to "LOCKED" as first day?
Regards.
komsboy_more said:
Can I go S-OFF from whis guide ? :http://forum.xda-developers.com/showthread.php?t=2314582
Is it usable on windows ? ... I think CHMOD command is a linux command.
And for last question... If I go S-OFF then downgrade RUU and then update again, the "TAMPERED" text will removed ? and "RELOCKED" will changed to "LOCKED" as first day?
Regards.
Click to expand...
Click to collapse
Yes that's the right guide for S-off The tampered text will not be removed but if you read through the Revone instructions it will tell you how to remove tampered text and lock your bootloader again, but do it before you upgrade to 4.2.2 as people are reporting revone is not working on the new bootloader within the 4.2.2 update.
htcdev.com is the problem I think...
komsboy_more said:
Hello,
I bought a HTC ONE M7 about 2 month ago. After two week of using phone, I decided to use my phone on 3G network but faced a problem.
When I use a 3G network, I can send and receive SMS, also can receive CALLs, but I can't make out going CALLs. After dialing, call ended immediately! I have this problem also on 2G network in some areas of our city. I checked my SIM on another phones (Nokia N97 and Samsung Galaxy S3) and worked fine.
I thought this may be a bug on software, and wait for 4.2.2. After installing OTA, the problem is still remained.
Now I decided to send it to warranty. But I think there is a problem. I UNLOCKED my phone from HTCDEC.com and RELOCKED again. I do it, because they wrote on the warning this "MAY' void your warranty. Now my phone has a "TAMPERED" and "RELOCKED" text on hboot.
How can I remove them and take my phone to fully stocked as 1st day?
Regards.
Click to expand...
Click to collapse
I think the problem will be the following :
You unlocked your phone via HTCDEV.com and so, HTC knows that your phone is unlocked...
Will it be accepted??
go figure...
gortys said:
I think the problem will be the following :
You unlocked your phone via HTCDEV.com and so, HTC knows that your phone is unlocked...
Will it be accepted??
go figure...
Click to expand...
Click to collapse
Yeah, but everyone MAY USE NOT the bin file to unlock the bootloader. May just download it. Right ?
maxal said:
Yes that's the right guide for S-off The tampered text will not be removed but if you read through the Revone instructions it will tell you how to remove tampered text and lock your bootloader again, but do it before you upgrade to 4.2.2 as people are reporting revone is not working on the new bootloader within the 4.2.2 update.
Click to expand...
Click to collapse
Thanks for your help man ...
I think that the steps I should fallow is like these:
1 - Go S-OFF through revone guide (I'll see S-OFF and "UNLOCKED" text in hboot after doing it. Right?)
2 - Removed "TAMPERED" text with this command : revone -t
3 - I should relocked my phone to prepare installing exe RUU. Right? How do this? With this command ? revone -l (or) revone -r. Witch one?
4 - Run related exe RUU. My best option will: http://www.androidfiles.org/ruu/?developer=M7
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
(or)
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.exe
5 - Now I should go S-ON. I found this guide : http://forum.xda-developers.com/showthread.php?t=2358738
Is it necessary that I change my CID? My current one is : HTC__J15
Then fallow to S-ON and remove the revone from temp as guide.
After these steps I have a phone that is "LOCKED' with NO "TAMPERED" text in hboot.Right?
And can update it to 2.24.401.1 again from wifi and OTA.
Right?
Regards
htcdev.com is the problem I think...
komsboy_more said:
Yeah, but everyone MAY USE NOT the bin file to unlock the bootloader. May just download it. Right ?
Click to expand...
Click to collapse
Yeah, I think it's right, I already saw it but I think a little bit difficult to put in place. But in this case, HTC knows it
komsboy_more said:
Thanks for your help man ...
I think that the steps I should fallow is like these:
1 - Go S-OFF through revone guide (I'll see S-OFF and "UNLOCKED" text in hboot after doing it. Right?)
2 - Removed "TAMPERED" text with this command : revone -t
3 - I should relocked my phone to prepare installing exe RUU. Right? How do this? With this command ? revone -l (or) revone -r. Witch one?
4 - Run related exe RUU. My best option will: http://www.androidfiles.org/ruu/?developer=M7
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
(or)
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.exe
5 - Now I should go S-ON. I found this guide : http://forum.xda-developers.com/showthread.php?t=2358738
Is it necessary that I change my CID? My current one is : HTC__J15
Then fallow to S-ON and remove the revone from temp as guide.
After these steps I have a phone that is "LOCKED' with NO "TAMPERED" text in hboot.Right?
And can update it to 2.24.401.1 again from wifi and OTA.
Right?
Regards
Click to expand...
Click to collapse
Once you gain S-off just run the RUU Iused 1.28.401.7 then remove tampered and then lock the bootloader folowing instructions from the Revone thread Ithink it's the second post.
Just reread through this thread and I beleive you have taken the OTA 4.2.2 update if this is correct I don't think you will be able to gain S-off as the new bootloader blocks it.
maxal said:
Once you gain S-off just run the RUU Iused 1.28.401.7 then remove tampered and then lock the bootloader folowing instructions from the Revone thread Ithink it's the second post.
Just reread through this thread and I beleive you have taken the OTA 4.2.2 update if this is correct I don't think you will be able to gain S-off as the new bootloader blocks it.
Click to expand...
Click to collapse
OK. Thanks. I don't need S-OFF again on 4.2.2.
I'll try it today and post result here.
komsboy_more said:
OK. Thanks. I don't need S-OFF again on 4.2.2.
I'll try it today and post result here.
Click to expand...
Click to collapse
No, you've misunderstood. As you are on 4.2.2 you cannot S-off so you are stuck with 'relocked' but you can remove 'Tampered' by flashing stock. Without S-off, you cannot go back to 'locked'
Sent from my HTC One using xda premium
drspikes said:
No, you've misunderstood. As you are on 4.2.2 you cannot S-off so you are stuck with 'relocked' but you can remove 'Tampered' by flashing stock. Without S-off, you cannot go back to 'locked'
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
OUW !
As there is no RUU for 4.2.2 also i CAN'T flash to stock to remove "TAMPERED"
I think removing "TAMPERED" will not help me. Because when a phone gone "UNLOCKED", the "TAMPERED" text appeared at same time.
And when a "RELOCKED" shown without "TAMPERED" => They found that it's un-normal.
Right?
komsboy_more said:
OUW !
As there is no RUU for 4.2.2 also i CAN'T flash to stock to remove "TAMPERED"
I think removing "TAMPERED" will not help me. Because when a phone gone "UNLOCKED", the "TAMPERED" text appeared at same time.
And when a "RELOCKED" shown without "TAMPERED" => They found that it's un-normal.
Right?
Click to expand...
Click to collapse
If your hboot is 1.54/1.55 then you cannot currently s-off so you either have to wait or send it back saying tampered/relocked.
However if this is a physical fault with the phone you should still be covered but if it's a firmware related issue then you maybe out of luck.
Related
Hi guys
I just contacted HTC to send in my device to repair my battery (my battery life is terrible).
They said that they could refuse to repair my device if they detect some illegal software and stuff (root and custom ROM I guess).
What do they exactly mean by "illegal software"?
How can I can "clean" my device so I looks like it is an untouched one?
ATM, I have rooted my device and flashed a ROM (but I returned to the old one via a backup).
Thanks
Matt
If you're S-OFF, you can easily flash an earlier RUU to return to stock, and then use revone to gain S-ON. In that way you will have a completely "clean" phone.
If you're S-ON With Hboot 1.54 you're stuck until revone finds an exploit, unfortunately.
Lucifer- said:
If you're S-OFF, you can easily flash an earlier RUU to return to stock, and then use revone to gain S-ON. In that way you will have a completely "clean" phone.
If you're S-ON With Hboot 1.54 you're stuck until revone finds an exploit, unfortunately.
Click to expand...
Click to collapse
I just checked and I'm S-ON.
So I think I'll just have to factory reset my deivce and hope for the best, right?
Which Hboot version do you have? You'll find the version nr. in bootloader. Either 1.44 or 1.54..
It's 1.44.0000
You're Lucky.
http://forum.xda-developers.com/showthread.php?t=2314582
Just follow the directions in this thread to get S-OFF, and then you can flash an older original RUU for your device before you set your device back to S-ON with a clean bootloader and stock os.
Awesome!
Thanks, I really appreciate it
No problem
To bad I'm in the same situation but with hboot 1.54 and an almost broken wifi-antenna.
Ow, that's stupid.
I hope I'll do everything right to remove the root, those instructions seem kinda complicated and hard
Sent from my HTC One using xda app-developers app
Yep, those are pretty hard. But if you look around in the forum you will find some guides on how to do it. Look at mike1986's going back to stock-thread for an example.
Allright, great!
I'll definitely look into that.
I have a few more days before the come picking up my device.
Hopefully things will be unrooted by then
Sent from my HTC One using xda app-developers app
Good Luck
I haven't really started yet and the first problem rises.
Following this thread (like you suggested, method 2)
---> http://forum.xda-developers.com/showthread.php?t=2265618
Apparently I need to find the RUU for my device, but I'm not sure if I'm choosing the right one.
Here's a collection of the RUU's for the HTC One, but my version isn't listed (I guess).
--> http://forum.xda-developers.com/showthread.php?p=39588860
My radio is 4D.14.3250.26 and the only files for the International version (Europe) are starting with 4A.
So I guess those won't work for me.
Am I right or did I do something wrong?
You'll also need to change the bootloader to locked instead of relocked and also remove the tampered flag if you want to be safe because that's two sure fire ways of them knowing you've done some fiddling lol
I've found a way to get S-off on my phone.
After that, I've changed the flags from unlocked to locked (so not relocked) and removed the tampered flag.
Next, I'm gonna return to S-on and reset everything using the option in the settings menu.
My device will still be rooted, but it will be harder to see for them, I hope.
Right?
Sent from my HTC One using xda app-developers app
Repair
I actually just got my phone back from HTC after they repaired it. I sent it in with it being rooted and having the bootloader unlocker. They didn't bat an eye. They replaced the battery for free and sent it back
So apparently you have to be lucky if they will repair it or not.
My device will be send to some place in the Netherlands, I really hope they will be good to me
Sent from my HTC One using xda app-developers app
MattProductions said:
Hi guys
I just contacted HTC to send in my device to repair my battery (my battery life is terrible).
They said that they could refuse to repair my device if they detect some illegal software and stuff (root and custom ROM I guess).
What do they exactly mean by "illegal software"?
How can I can "clean" my device so I looks like it is an untouched one?
ATM, I have rooted my device and flashed a ROM (but I returned to the old one via a backup).
Thanks
Matt
Click to expand...
Click to collapse
when you unlock your HTC phone over the Internet your IMEI and SN will be listed in their database as (NOT Original)
most of the times repair people will look at the "TAMPERED" text in Hboot, and they will because its hard to remove, if you will take it to repair
make sure you are running %100 stock with the phone NON Root and NO TAMPERED text
Muhammad.Muayad said:
when you unlock your HTC phone over the Internet your IMEI and SN will be listed in their database as (NOT Original)
most of the times repair people will look at the "TAMPERED" text in Hboot, and they will because its hard to remove, if you will take it to repair
make sure you are running %100 stock with the phone NON Root and NO TAMPERED text
Click to expand...
Click to collapse
Well, I've managed to remove the "TAMPERED" text and change the other text to "LOCKED", but my phone is still rooted.
To unroot it I need the correct RUU (according to my research), but I'm unable to find the right one for my device.
So I guess I'm screwed?
MattProductions said:
Well, I've managed to remove the "TAMPERED" text and change the other text to "LOCKED", but my phone is still rooted.
To unroot it I need the correct RUU (according to my research), but I'm unable to find the right one for my device.
So I guess I'm screwed?
Click to expand...
Click to collapse
NO you can unRoot your device
https://www.google.com/search?site=&source=hp&q=unroot+htc+one&oq=unroot+htc+one&gs_l=hp.3..0l10.595.4665.0.5161.14.8.0.6.6.1.246.1339.2j0j6.8.0....0...1c.1.24.hp..1.13.1169.h3qqJ12POGs
Hi guys.
First time posting, but have used the site extensively over the past 6-8 months. I have an AT&T HTC One. I had unlocked it, s-off, rooted, installed GPe, and decided to go back. The ROM I went back to was supposed to be MY stock ROM, but it turns out it was unbranded 4.2.2. I thought nothing of it, and as of yesterday, had sold my phone on ebay. I decided to wipe my phone to get ready to ship. I locked my bootloader and went to s-on, but when I went to factory reset, I got a "security warning" and it won't reboot into recovery. I've tried everything- tried to re-unlock it with htcdev, which freezes at the bootloader. I've tried to unlock via revone, since I still have root (root checker verified this to be the case), but get the -6 error when using terminal emulator in ROM Toolbox, and get the same error when doing it via adb commands. I've tried probably 50 different things about 10 different times, and am about to pull my hair out! I've read and searched probably hundreds of threads over the past 24 hours. Trying to flash stock RUU (the exe) just freezes as well. Any help would be appreciated! Let me know what info you need from me.
Android 4.2.2
Hboot 1.44
Software number 2.24.401.8
HTC SDK API level 5.34
Kernel version 3.4.10-g28df0d6 [email protected] #1 SMP PREEMPT
Baseband version 4A.18.3263.15_10.38h.1157.04L
Build number 2.24.401.8 CL235216 release-keys
Thanks guys! Awesome community!
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
but also Read Mike 1986's Return to stock Guide before - this will ensure you are aware of what needs doing before you start to do it
http://forum.xda-developers.com/showthread.php?t=2265618
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
The search option would have found these for you and saved some time and heartache :highfive:
L0rdNels0n said:
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Click to expand...
Click to collapse
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads (every RUU I've tried fails miserably, and extracted rom.zips don't work either). It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
AndyM3 said:
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads. It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
Click to expand...
Click to collapse
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
nkk71 said:
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
Click to expand...
Click to collapse
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
nkk71 said:
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
Click to expand...
Click to collapse
I downloaded a 1.20.401 RUU (should be 4.1.2, probably), and I am on mike1986's odexed ROM right now. I'd downgrade, but how? I can't install a custom recovery.
Edit: RUU exited with a "bootloader version error". Could I have downloaded a corrupt HBOOT or something? revone gave success messages about five times now, but the bootloader still says "LOCKED" and "S-ON".
AndyM3 said:
the bootloader still says "LOCKED" and "S-OFF".
Click to expand...
Click to collapse
So S-Off achieved great.
What's still the problem?
nkk71 said:
So S-Off achieved great.
What's still the problem?
Click to expand...
Click to collapse
Typo, sorry. It's S-ON.
AndyM3 said:
Typo, sorry. It's S-ON.
Click to expand...
Click to collapse
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
nkk71 said:
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
Click to expand...
Click to collapse
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
AndyM3 said:
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
Click to expand...
Click to collapse
Sometimes a factory reset can help with the unlock token, but since you're on 1.54 now it would make little difference.
Sorry & good luck
Sent from my HTC One using xda app-developers app
Yep. I'm in exactly the same boat. Actually, I am on 1.44 HBOOT, dated May 3rd, and none of the available options worked. And yes, I've tried the links included in subsequent posts. And I'm "locked" via same way as above. Since I was selling the phone and trying to revert to stock, my only option was to manually erase everything and send it off. I couldn't do a factory reset, because it just kicked me to bootloader with a "security warning" error. Couldn't install older RUU, as it would just hang at the HTC black screen with no green progress bar.
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
Same problem
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
PlaviiCZ said:
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
Sorry for my bad english, but I hope hope you'll understand.
Click to expand...
Click to collapse
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
clsA said:
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
Click to expand...
Click to collapse
Yeah, I'm dumbass...Yes, I did, and nothing...just "failed" in cmd. Should I try again to tell you, what is in cmd exactly written?
EDIT: Please help (
No one knows anything?
There is no ruu for my phone (02___001) so now I have s off I was going to run a stock ruu and update to the latest firmware. If I send the phone back for repair and change my cid to HTC_001 would HTC know I have changed my cid even if I s on?
Anyone help me at all?
stovie_steve said:
Anyone help me at all?
Click to expand...
Click to collapse
Two things:
1- I dont know if they keep a record of IMEI (or s/n) <--> carrier, but I think they have to and do.
2- the CID is stored in several partitions, not only the one you change with fastboot writecid.
HOWEVER, it really depends on how far they're going to dig into this, if they are going to check their IMEI database or check the different partitions on the phone, just to "prove you wrong", I guess they could.
But then again, would it be worth all that hassle for them?
I dont have any experience with repair centers or how far they would go to prove that you changed something on your phone, and it's really quite country (and HTC people) dependent; for some they have no problem with an unlocked or relocked phone, and other even have a problem with S-Off (though they can't prove the phone didn't ship that way in the first place)
Better have someone from your region (O2 so UK?) post their experience(s)
Ah that's ok
So you reckon it would be better to be completely stock with stock CID and leave it s-off as it could ha e shipped that way anyway even for a carrier branded phone?
stovie_steve said:
Ah that's ok
So you reckon it would be better to be completely stock with stock CID and leave it s-off as it could ha e shipped that way anyway even for a carrier branded phone?
Click to expand...
Click to collapse
I honestly cannot say mate, have ZERO experience with this, just what I've read from other people; can't remember which countries, but some have sent their phone in for repair (eg for the purple camera issue) with tampered, unlocked etc and got either a repair or a brand new phone, others sent it completely stock, only with S-Off and were refused service (and the service center can't even prove it didn't ship that way, nor did they try).
Sorry can't help you out, or give any good advice about that.
I can help get you back to stock, or at least as close to stock as possible (you can check some of the other guys I've helped out in the Q&A section), but that's about as far as I can go.
Cheers & good luck
EDIT: one guy I helped (I think from Canada) got it 100% stock and S-On, and the a**holes still gave him a hard time, don't know what happened in the end, hope they fixed it for him.
nkk71 said:
I honestly cannot say mate, have ZERO experience with this, just what I've read from other people; can't remember which countries, but some have sent their phone in for repair (eg for the purple camera issue) with tampered, unlocked etc and got either a repair or a brand new phone, others sent it completely stock, only with S-Off and were refused service (and the service center can't even prove it didn't ship that way, nor did they try).
Sorry can't help you out, or give any good advice about that.
I can help get you back to stock, or at least as close to stock as possible (you can check some of the other guys I've helped out in the Q&A section), but that's about as far as I can go.
Cheers & good luck
EDIT: one guy I helped (I think from Canada) got it 100% stock and S-On, and the a**holes still gave him a hard time, don't know what happened in the end, hope they fixed it for him.
Click to expand...
Click to collapse
If you could help me yes that would be great mate
The steps I took to get where I am are as follows:
1. I was running a stock 02 UK Rom (2.24.206.7) and achieved s off using rumrunner
2. I downgraded hboot to 1.44 and installed a stock ruu for cid HTC__001
3. I flashed cwm recovery and nandroid restored my phone to o2 backup 1.29.206.1 and flashed a stock recovery before locking the bootloader using adb shell command and then installing the updates (my cid was also changed back to 02___001 to do this). I note also that I'm not sure that the recovery was completely stock, as I had to manually reboot the phone a few times to allow the ota to install.
4. I upgraded my phone via various OTA's until the latest 3.62.206.1 firmware
5. Satisfied that the OTA had flashed the latest stock hboot, stock recovery and stock Rom I did fastboot oem writesecureflag 3. I got success and when I reboot it said tamper detected - rebooting. The bootloader is now locked, s on and tampered
What steps would you add/take away or change?
I can unlock again using htcdev and start again I guess
Would you advise maybe re running rumrunner once I'm back to version 2.24.206.7 and run all the commands again (lock, remove tampered) and then s on?
The reason I ran the ota from an earlier nandroid was because I thought I would restore everything to stock by ota
If you help me achieve this I will gladly buy you a beer lol!
stovie_steve said:
If you could help me yes that would be great mate
The steps I took to get where I am are as follows:
1. I was running a stock 02 UK Rom (2.24.206.7) and achieved s off using rumrunner
2. I downgraded hboot to 1.44 and installed a stock ruu for cid HTC__001
3. I flashed cwm recovery and nandroid restored my phone to o2 backup 1.29.206.1 and flashed a stock recovery before locking the bootloader using adb shell command and then installing the updates (my cid was also changed back to 02___001 to do this). I note also that I'm not sure that the recovery was completely stock, as I had to manually reboot the phone a few times to allow the ota to install.
4. I upgraded my phone via various OTA's until the latest 3.62.206.1 firmware
5. Satisfied that the OTA had flashed the latest stock hboot, stock recovery and stock Rom I did fastboot oem writesecureflag 3. I got success and when I reboot it said tamper detected - rebooting. The bootloader is now locked, s on and tampered
What steps would you add/take away or change?
I can unlock again using htcdev and start again I guess
Would you advise maybe re running rumrunner once I'm back to version 2.24.206.7 and run all the commands again (lock, remove tampered) and then s on?
The reason I ran the ota from an earlier nandroid was because I thought I would restore everything to stock by ota
If you help me achieve this I will gladly buy you a beer lol!
Click to expand...
Click to collapse
1- Well the steps you took sound very good (I personally, would have skipped all the OTAs), but can you elaborate on "when I reboot it said tamper detected - rebooting", do you mean that you had removed TAMPERED and it suddenly came back by itself???
2- For you to be able to fix this, you will need S-Off, I just checked rumrunner, and there's only a 3.62.401.1 package around, hopefully it will work, otherwise you will need: "If you mainver is not listed, please contact [email protected] with firmware version AND a link to the corresponding RUU and/or firmware ota package." (http://forum.xda-developers.com/showthread.php?t=2487888)
3- I guess you're going to have to unlock again, and try rumrunner 3.62.401.1 package and hope it works without the hassle of having to send in you firmware.
4- Beer won't be necessary, I'm actually enjoying a scotch at the moment ; maybe when I'm in London next time Otherwise hitting the thanks button, is more than enough!
So I guess, go ahead an unlock and try to get S-Off, post back with results. I'll keep an :cyclops: on the thread and help as much I can.
nkk71 said:
1- Well the steps you took sound very good (I personally, would have skipped all the OTAs), but can you elaborate on "when I reboot it said tamper detected - rebooting", do you mean that you had removed TAMPERED and it suddenly came back by itself???
2- For you to be able to fix this, you will need S-Off, I just checked rumrunner, and there's only a 3.62.401.1 package around, hopefully it will work, otherwise you will need: "If you mainver is not listed, please contact [email protected] with firmware version AND a link to the corresponding RUU and/or firmware ota package." (http://forum.xda-developers.com/showthread.php?t=2487888)
3- I guess you're going to have to unlock again, and try rumrunner 3.62.401.1 package and hope it works without the hassle of having to send in you firmware.
4- Beer won't be necessary, I'm actually enjoying a scotch at the moment ; maybe when I'm in London next time Otherwise hitting the thanks button, is more than enough!
So I guess, go ahead an unlock and try to get S-Off, post back with results. I'll keep an :cyclops: on the thread and help as much I can.
Click to expand...
Click to collapse
Yes the phone said on booting up the Rom - "tamper detected - rebooting" and then my bootloader said tampered
I had to do the ota as I didn't have the stock recovery for version 1.29.206.7 as I knew the ota would flash an official recovery
I guess I could 're-run s off rumrunner when I'm on 2.24.206.7 (the 2.24.401.7 version works for this) and reset all the flags and then s on again?
You think that could work?
stovie_steve said:
Yes the phone said on booting up the Rom - "tamper detected - rebooting" and then my bootloader said tampered
Click to expand...
Click to collapse
Hmmm, interesting (only saw 1 other post like that, I think), did that happen after the last OTA which updated hboot to 1.55; wondering if they "patched" something in 1.55.
stovie_steve said:
I had to do the ota as I didn't have the stock recovery for version 1.29.206.7 as I knew the ota would flash an official recovery
Click to expand...
Click to collapse
The first OTA would have been enough, you didn't need to go all the way to 3.62; you had to manually reboot the first OTA yourself because stock recovery wasn't 100% correct, but after the OTA was successfully installed, you could have stopped at that.
stovie_steve said:
I guess I could 're-run s off rumrunner when I'm on 2.24.206.7 (the 2.24.401.7 version works for this) and reset all the flags and then s on again?
You think that could work?
Click to expand...
Click to collapse
Problem is you are already on 3.62 and downgrading isn't possible with S-On, so you're going to have to unlock and try a rumrunner package that get's you s-off. If the 3.62.401 rumrunner works or the 2.24.206.7 or whichever one works to get you S-Off it doesn't matter, but you do need to get S-Off (IMHO).
nkk71 said:
Hmmm, interesting (only saw 1 other post like that, I think), did that happen after the last OTA which updated hboot to 1.55; wondering if they "patched" something in 1.55.
The first OTA would have been enough, you didn't need to go all the way to 3.62; you had to manually reboot the first OTA yourself because stock recovery wasn't 100% correct, but after the OTA was successfully installed, you could have stopped at that.
Problem is you are already on 3.62 and downgrading isn't possible with S-On, so you're going to have to unlock and try a rumrunner package that get's you s-off. If the 3.62.401 rumrunner works or the 2.24.206.7 or whichever one works to get you S-Off it doesn't matter, but you do need to get S-Off (IMHO).
Click to expand...
Click to collapse
I'm going to unlock via HTC dev, install guru reset via recovery and s off again. Then 're run the nandroid backup ota til 2.24.206.7, n 're run rumrunner
stovie_steve said:
I'm going to unlock via HTC dev, install guru reset via recovery and s off again. Then 're run the nandroid backup ota til 2.24.206.7, n 're run rumrunner
Click to expand...
Click to collapse
Okidoke, good luck :fingers-crossed:.
I'm two hours ahead of you... okay that sounds bad :silly:, what I mean is there's a two hour difference between us, but I'll keep checking your thread for a while longer (an hour or two). if you post something and I don't get back to you tonight, I'll definitely check again tomorrow.
nkk71 said:
Okidoke, good luck :fingers-crossed:.
I'm two hours ahead of you... okay that sounds bad :silly:, what I mean is there's a two hour difference between us, but I'll keep checking your thread for a while longer (an hour or two). if you post something and I don't get back to you tonight, I'll definitely check again tomorrow.
Click to expand...
Click to collapse
No problem!
Right these are the steps I'm going to do
1. Unlock bootloader via HTC dev
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off
4. Downgrade hboot to 1.44
5. Restore nandroid backup for my 02 version 1.28.206.7
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match)
7. Go s-on to see what happens
8. If s-on fails in any way then redo the HTC dev unlock, 're run rumrunner and get s off again using the same version of rumrunner
9. Reset tampered flag and lock bootloader via adb shell
10. Retry s-on again
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Thoughts on this method? I'm just wondering if people tried going s on in hboot 1.55 caused this tampered message to appear or if I s on first and then update will it appear then after? I do t know. I'd like to hear your thoughts tho
stovie_steve said:
No problem!
Right these are the steps I'm going to do
1. Unlock bootloader via HTC dev
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off
4. Downgrade hboot to 1.44
5. Restore nandroid backup for my 02 version 1.28.206.7
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match)
7. Go s-on to see what happens
8. If s-on fails in any way then redo the HTC dev unlock, 're run rumrunner and get s off again using the same version of rumrunner
9. Reset tampered flag and lock bootloader via adb shell
10. Retry s-on again
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Thoughts on this method? I'm just wondering if people tried going s on in hboot 1.55 caused this tampered message to appear or if I s on first and then update will it appear then after? I do t know. I'd like to hear your thoughts tho
Click to expand...
Click to collapse
Ok, my thoughts, in a nutshell
1. Unlock bootloader via HTC dev <- YES
2----- try rumrunner 3.62
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off <- Ok, try, if it fails use above rumrunner 3.62
Once S-Off:
--- remove tampered: revone or http://forum.xda-developers.com/showthread.php?t=2477792
5. Restore nandroid backup for my 02 version 1.28.206.7
--- set phone to LOCKED, using revone (or http://forum.xda-developers.com/showthread.php?t=2475914)
------- you will need to have SU privileges which you can get using revone or flashing SuperSU; if you do flash SuperSU, uninstall it after getting LOCKED
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match) <- Yep
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Once you have your bootloader "LOCKED", no TAMPERED, no red text on bootup, do "fastboot oem writesecureflag 3"
reboot three times and see if everything sticks, and don't take any other OTAs.
Hit me with a thanks if this was useful
So you think I shouldn't upgrade to the latest OTA once I get s on?
stovie_steve said:
So you think I shouldn't upgrade to the latest OTA once I get s on?
Click to expand...
Click to collapse
Since you're sending it in for repair, why would you want to?
But anyway, as long as the above steps work to get S-Off (again and again, if necessary), you can try and see if you dont get that "tamper detected" thing again. If it doesnt show up again you're all good to go.
(and I would be curious if we could find out where that comes from. the "tamper detected" hmmm )
nkk71 said:
Since you're sending it in for repair, why would you want to?
But anyway, as long as the above steps work to get S-Off (again and again, if necessary), you can try and see if you dont get that "tamper detected" thing again. If it doesnt show up again you're all good to go.
(and I would be curious if we could find out where that comes from. the "tamper detected" hmmm )
Click to expand...
Click to collapse
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
stovie_steve said:
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
Click to expand...
Click to collapse
N I need to downgrade the hboot otherwise my touch screen won't work with the nandroid backup. Then again I don't necessarily have to run the ruu either
stovie_steve said:
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
Click to expand...
Click to collapse
Yep, sounds good, except I would unlock using HTCdev then immediately try the 3.62 rumrunner to get S-Off, if it works GREAT and you're pretty much sure to be able to "easily" get S-Off on any version.
If it doesn't S-Off then try the Guru Reset.
BTW, as soon as you unlock, do a nandroid and "adb pull" it to your PC! just in case.
nkk71 said:
Yep, sounds good, except I would unlock using HTCdev then immediately try the 3.62 rumrunner to get S-Off, if it works GREAT and you're pretty much sure to be able to "easily" get S-Off on any version.
If it doesn't S-Off then try the Guru Reset.
BTW, as soon as you unlock, do a nandroid and "adb pull" it to your PC! just in case.
Click to expand...
Click to collapse
And how to I keep hold of the 3.62.206.1 recovery before I do a nandroid backup?
stovie_steve said:
N I need to downgrade the hboot otherwise my touch screen won't work with the nandroid backup. Then again I don't necessarily have to run the ruu either
Click to expand...
Click to collapse
the touchscreen drivers were part of the 2.xx firmware package, not hboot, so if you don't use a full RUU, it will break the touchscreen drivers, but you can use an OTG cable + mouse.
stovie_steve said:
And how to I keep hold of the 3.62.206.1 recovery before I do a nandroid backup?
Click to expand...
Click to collapse
Unfortunately you can't (anymore), but this one should be close enough: http://d-h.st/users/guich/?fld_id=25920#files, or the best thing is to get a hold of the OTA 3.62.206.1 file and extract it from it.
Anyway, in my humble opinion, first things first: unlock using HTCdev and see if you can get rumrunner to S-Off on 3.62.
2.24.980.2
s-off
CID-OPTUS001
HBOOT1.54.0000
returned to stock back up - android 4.2.2 (after using viperone rc2)
recovery - latest twrp
how the heck can i remove *Tampered* and *Unlocked* and restore the stock recovery? can i downgrade hboot because every method i have found has said "does not work with hboot 1.54+"
i need to return my phone under warranty because the speakers are making terrible crackling sounds and the phone doesnt vibrate anymore. . . i am so damn carful with my phones always have an otterbox on them and never dropped it ever so its ticking me off a bit.
any help would be greatly appreciated
jande425 said:
2.24.980.2
s-off
CID-OPTUS001
HBOOT1.54.0000
returned to stock back up - android 4.2.2 (after using viperone rc2)
recovery - latest twrp
how the heck can i remove *Tampered* and *Unlocked* and restore the stock recovery? can i downgrade hboot because every method i have found has said "does not work with hboot 1.54+"
i need to return my phone under warranty because the speakers are making terrible crackling sounds and the phone doesnt vibrate anymore. . . i am so damn carful with my phones always have an otterbox on them and never dropped it ever so its ticking me off a bit.
any help would be greatly appreciated
Click to expand...
Click to collapse
since you are s-off just download a ruu and flash it s-off allows you to run any ruu
jande425 said:
2.24.980.2
s-off
CID-OPTUS001
HBOOT1.54.0000
returned to stock back up - android 4.2.2 (after using viperone rc2)
recovery - latest twrp
how the heck can i remove *Tampered* and *Unlocked* and restore the stock recovery? can i downgrade hboot because every method i have found has said "does not work with hboot 1.54+"
i need to return my phone under warranty because the speakers are making terrible crackling sounds and the phone doesnt vibrate anymore. . . i am so damn carful with my phones always have an otterbox on them and never dropped it ever so its ticking me off a bit.
any help would be greatly appreciated
Click to expand...
Click to collapse
Have you checked my guide http://forum.xda-developers.com/showthread.php?t=2541082
nkk71 said:
Have you checked my guide http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Fails every time i try to flash the zip it goes through a couple steps then says failed. . . . :/
jerrycoffman45 said:
since you are s-off just download a ruu and flash it s-off allows you to run any ruu
Click to expand...
Click to collapse
will a ruu remove the tampered and unlocked ??
jande425 said:
will a ruu remove the tampered and unlocked ??
Click to expand...
Click to collapse
will removed tampered but not unocked
jerrycoffman45 said:
will removed tampered but not unocked
Click to expand...
Click to collapse
fu** sake i cant even flash the correct RUU
i downgraded my hboot to 1.44 and got super cid
but i still cant remove unlocked and tampered
alright if anyone happens to see this this is where i am at now
i have removed tampered and unlocked (replaced with locked) but i can not for the life of me figure out how to restore the stock recovery without having the device saying "unlocked"
i have the guru tool which can remove tampered and lock and unlock boot loader but i want the stock recovery on my phone so i an return for warranty purposes the only way i can use the guru tool is through cwm. . when i lock the bootloader i cant change the recovery . . . what in the damn hell do i do hahaha
currently hboot 1.44
s off
jande425 said:
alright if anyone happens to see this this is where i am at now
i have removed tampered and unlocked (replaced with locked) but i can not for the life of me figure out how to restore the stock recovery without having the device saying "unlocked"
i have the guru tool which can remove tampered and lock and unlock boot loader but i want the stock recovery on my phone so i an return for warranty purposes the only way i can use the guru tool is through cwm. . when i lock the bootloader i cant change the recovery . . . what in the damn hell do i do hahaha
currently hboot 1.44
s off
Click to expand...
Click to collapse
check my thread, replied to you there
Alright, I've been through thread after thread and plenty of pages found on google.
Some say to Lock the bootloader BEFORE using the RUU and some say to lock it AFTER or you'll brick the phone?
I've got a T-mobile Variant of the HTC one M7 It's rooted, SuperCID and obviously the bootloader is unlocked.... I think it's on 1.55, not exactly sure, I'm currently backing up all my data.
I've got the new 5.14.531.1 RUU straight from the HTC website.
Since it's a Tmobile rom, I'm guessing resetting the CID to T-MOB010 before installing would be a good idea?
And what of the bootloader? running the RUU should install the new Hboot correct? from there I would just need to relock it or am I not understanding this?
~Out of all my phones I've NEVER returned one to stock, so this is all kinda new to me.
Vonrottes said:
I've got the new 5.14.531.1 RUU straight from the HTC website.
Click to expand...
Click to collapse
SuperCID means you're S-Off, so no need to lock/relock bootloader, but where did you get that RUU from? link please, cause I don't think it's an RUU (how big is the file??)
nkk71 said:
SuperCID means you're S-Off, so no need to lock/relock bootloader, but where did you get that RUU from? link please, cause I don't think it's an RUU (how big is the file??)
Click to expand...
Click to collapse
Doesn't exactly answer the question... I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
Also the link, right from HTC
http://dl3.htc.com/application/RUU_M7UL_TMOUS_5.14.531.1_With Partial.exe
it's a whooping 1.49GB
Vonrottes said:
Doesn't exactly answer the question... I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
Also the link, right from HTC
http://dl3.htc.com/application/RUU_M7UL_TMOUS_5.14.531.1_With Partial.exe
it's a whooping 1.49GB
Click to expand...
Click to collapse
ah ok, 1.49GB sounds good for an RUU
and to answer your question differently, if you are S-Off, then you do not need to lock/relock bootloader; the RUU should work fine with unlocked bootloader
refer to "Not so FAQ #2": http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
and remember to stay S-Off
nkk71 said:
ah ok, 1.49GB sounds good for an RUU
and to answer your question differently, if you are S-Off, then you do not need to lock/relock bootloader; the RUU should work fine with unlocked bootloader
refer to "Not so FAQ #2": http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
and remember to stay S-Off
Click to expand...
Click to collapse
Jolly good, I didn't even see that Not so FAQ.
So basically I just run the RUU according to the instructions on the HTC page ( http://www.htc.com/us/support/news.aspx?p_id=630&p_name=htc-one-t-mobile ) and I should be good?
Vonrottes said:
Jolly good, I didn't even see that Not so FAQ.
So basically I just run the RUU according to the instructions on the HTC page ( http://www.htc.com/us/support/news.aspx?p_id=630&p_name=htc-one-t-mobile ) and I should be good?
Click to expand...
Click to collapse
hmm, i can't seem to be able open that web page, but if the file is a full RUU (I'm downloading it, but with my connection it's gonna take quite a while), then hook up the phone, and run the RUU and all should be good.
Remember an RUU will fully wipe your phone (including sdcard/internal storage), and if for whatever reason you want to change bootloader to the original LOCKED (not relocked),
you can use this tool: http://forum.xda-developers.com/showthread.php?t=2527194
(though I don't see any reason to do it )
as long as you stay S-Off, you can easily get it unlocked again anytime
out of curiosity, any particular reason you're doing this?
nkk71 said:
hmm, i can't seem to be able open that web page, but if the file is a full RUU (I'm downloading it, but with my connection it's gonna take quite a while), then hook up the phone, and run the RUU and all should be good.
Remember an RUU will fully wipe your phone (including sdcard/internal storage), and if for whatever reason you want to change bootloader to the original LOCKED (not relocked),
you can use this tool: http://forum.xda-developers.com/showthread.php?t=2527194
(though I don't see any reason to do it )
as long as you stay S-Off, you can easily get it unlocked again anytime
out of curiosity, any particular reason you're doing this?
Click to expand...
Click to collapse
I know, that's why I'm currently backing up everything important on Google Drive.
I was just looking at Scotty1223's threads with the ADB commands to remove tampered flag and reset locked.
and like I said in my second post
I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
So to go back stock with no need to ever unlock or root again,
I'll be fine LOCKING the bootloader and resetting the CID to T-MOB010 Before running the RUU?
Vonrottes said:
I know, that's why I'm currently backing up everything important on Google Drive.
I was just looking at Scotty1223's threads with the ADB commands to remove tampered flag and reset locked.
and like I said in my second post
I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.
So to go back stock with no need to ever unlock or root again,
I'll be fine LOCKING the bootloader and resetting the CID to T-MOB010 Before running the RUU?
Click to expand...
Click to collapse
I understood the part about upgrading your phone, but seeing your signature, you're running a custom ROM and kernel, so i'm not clear what you mean by upgrading
Anyway, if you are going back to stock, here's what I personally would do:
1- stay S-OFF
2- change CID back to original
3- remove TAMPERED and set LOCKED (using scotty1223's commands, or the Guru Bootloader Reset tool) not because it's necessary, just aesthetically more stock
4- run the RUU
5- stay S-OFF
nkk71 said:
I understood the part about upgrading your phone, but seeing your signature, you're running a custom ROM and kernel, so i'm not clear what you mean by upgrading
Anyway, if you are going back to stock, here's what I personally would do:
1- stay S-OFF
2- change CID back to original
3- remove TAMPERED and set LOCKED (using scotty1223's commands, or the Guru Bootloader Reset tool) not because it's necessary, just aesthetically more stock
4- run the RUU
5- stay S-OFF
Click to expand...
Click to collapse
Upgrading as in:
http://www.t-mobile.com/phone-upgrade.html
To get an HTC One M8 I have turn in my Current M7... Which has to be stock...as far as the T-mobile store tech needs to know.... I guess?
Vonrottes said:
Upgrading as in:
http://www.t-mobile.com/phone-upgrade.html
To get an HTC One M8 I have turn in my Current M7... Which has to be stock...as far as the T-mobile store tech needs to know.... I guess?
Click to expand...
Click to collapse
gotcha :good:
that's a completely different kind of upgrade, i thought you meant software
Do they care about S-OFF?? because if you intend on going S-ON, then I would highly recommend a 1.xx ruu, nothing higher.
because going from S-Off to S-On on hboot 1.55+, has been known to trigger "tamper detected - rebooting" and TAMPERED is back in bootloader screen.
nkk71 said:
gotcha :good:
that's a completely different kind of upgrade, i thought you meant software
Do they care about S-OFF?? because if you intend on going S-ON, then I would highly recommend a 1.xx ruu, nothing higher.
because going from S-Off to S-On on hboot 1.55+, has been known to trigger "tamper detected - rebooting" and TAMPERED is back in bootloader screen.
Click to expand...
Click to collapse
Yeah, it's gonna need to be S-on when I take it into the store...
Pretty sure they check the bootloader for S-ON, ***TAMPERED*** and ***LOCKED***
Is it just the 1.55+ Hboot that throws the tampered when locked?
If so Can I flash the 1.54.401.5 Hboot from Firewater and proceed like that?
Can't do the 1.44, My PC is running 8.1 and I've not played with Linux since 2009
Vonrottes said:
Yeah, it's gonna need to be S-on when I take it into the store...
Pretty sure they check the bootloader for S-ON, ***TAMPERED*** and ***LOCKED***
Click to expand...
Click to collapse
In that case, I recommend you use a 1.xx RUU
(check my guide in my signature)
Vonrottes said:
Is it just the 1.55+ Hboot that throws the tampered when locked?
Click to expand...
Click to collapse
Unknown when/what exactly triggers the "tamper detected" or some people have been able to S-On and not get that, others have not, so I can't say if it will happen or not. but if you wanna play it safe, go for 1.xx ruu.
Vonrottes said:
If so Can I flash the 1.54.401.5 Hboot from Firewater and proceed like that?
Click to expand...
Click to collapse
brick alert: Definitely NOT, that is a custom HBOOT, if you actually manage to S-On it with an unsigned hboot, you'll have an paperweight on your hands!! stay away from that.