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?
I converted my phone to a Developer Edition phone a while back, and in the process went S-OFF. I would like to S-ON, as I have read this removes the 'test device' status that apparently sends HTC information. I also read that going S-ON with a custom HBOOT is a very bad thing, but how do I tell if my HBOOT is custom? The top just reads M7_UL PVT SHIP S-OFF RH and the version is HBOOT 1.56.
hjjfffaa said:
I converted my phone to a Developer Edition phone a while back, and in the process went S-OFF. I would like to S-ON, as I have read this removes the 'test device' status that apparently sends HTC information. I also read that going S-ON with a custom HBOOT is a very bad thing, but how do I tell if my HBOOT is custom? The top just reads M7_UL PVT SHIP S-OFF RH and the version is HBOOT 1.56.
Click to expand...
Click to collapse
From Rumrunner documentation
How to get rid of S-OFF warnings
There are two visual differences that will indicate that your device is S-OFF (other than checking in the bootloader):
1. Go to Settings > About. You should see "Tell HTC and error reporting" option right under "Software updates".
If you don't see that option, then you're already using a custom ROM and you can skip this step. But if you see the "Tell HTC and error reporting" option, select it and scroll down to read a warning message in red text. The "Tell HTC" option is permanently enabled and cannot be turned off without flashing a custom ROM. If you are not comfortable with HTC collecting information from your device, you can load your custom recovery, wipe data, cache, dalvik and install a custom ROM - the "Tell HTC and error reporting" option will be gone.
2. Boot up or restart your phone. In the boot splash screen, if you see a warning message in red text: "This build is for development purposes only..." you can remove it by flashing a custom hboot, now supplied by the developers of Rumrunner: http://rumrunner.us/hboots/. If your phone's firmware and carrier are not listed, the custom Hboots provided on the Rumrunner site will not work and you will likely brick your device. But you can look for other sources. Try this one: http://forum.xda-developers.com/show....php?t=2316726. Alternatively, you can request for a custom Rumrunner Hboot for your specific firmware and carrier. Instructions: Do fastboot getvar all and don't forget to remove your serialno and imei. Paste the info into an email. Upload your RUU or firmware.zip from OTA to dropbox and add link in email and don't forget to mention your carrier, if any. Send to: [email protected]. Then, check the Rumrunner Hboots page regularly for the update: http://rumrunner.us/hboots/.
mb_guy said:
From Rumrunner documentation
How to get rid of S-OFF warnings
There are two visual differences that will indicate that your device is S-OFF (other than checking in the bootloader):
1. Go to Settings > About. You should see "Tell HTC and error reporting" option right under "Software updates".
If you don't see that option, then you're already using a custom ROM and you can skip this step. But if you see the "Tell HTC and error reporting" option, select it and scroll down to read a warning message in red text. The "Tell HTC" option is permanently enabled and cannot be turned off without flashing a custom ROM. If you are not comfortable with HTC collecting information from your device, you can load your custom recovery, wipe data, cache, dalvik and install a custom ROM - the "Tell HTC and error reporting" option will be gone.
2. Boot up or restart your phone. In the boot splash screen, if you see a warning message in red text: "This build is for development purposes only..." you can remove it by flashing a custom hboot, now supplied by the developers of Rumrunner: http://rumrunner.us/hboots/. If your phone's firmware and carrier are not listed, the custom Hboots provided on the Rumrunner site will not work and you will likely brick your device. But you can look for other sources. Try this one: http://forum.xda-developers.com/show....php?t=2316726. Alternatively, you can request for a custom Rumrunner Hboot for your specific firmware and carrier. Instructions: Do fastboot getvar all and don't forget to remove your serialno and imei. Paste the info into an email. Upload your RUU or firmware.zip from OTA to dropbox and add link in email and don't forget to mention your carrier, if any. Send to: [email protected]. Then, check the Rumrunner Hboots page regularly for the update: http://rumrunner.us/hboots/.
Click to expand...
Click to collapse
I'm aware of these options, but would rather not have anything custom to worry about. According to this a custom ROM or HBOOT is the only way to actually disable the reporting while keeping S-OFF, which I do not care to keep.
hjjfffaa said:
I'm aware of these options, but would rather not have anything custom to worry about. According to this a custom ROM or HBOOT is the only way to actually disable the reporting while keeping S-OFF, which I do not care to keep.
Click to expand...
Click to collapse
Bump. Just need to know if I have the hboot for the Developer Edition so I can run the RUU and S-ON, or where I could find it. Been searching.
hjjfffaa said:
Bump. Just need to know if I have the hboot for the Developer Edition so I can run the RUU and S-ON, or where I could find it. Been searching.
Click to expand...
Click to collapse
After running the RUU you know for sure you have stock hboot because the RUU installs it
I still can't recommend s-on for any reason
hjjfffaa said:
I'm aware of these options, but would rather not have anything custom to worry about. According to this a custom ROM or HBOOT is the only way to actually disable the reporting while keeping S-OFF, which I do not care to keep.
Click to expand...
Click to collapse
You understand correctly.
If you *really* object to the Tell HTC reporting *and* you do not wish to run a custom ROM, S-ON may be your only choice, and I have to say I personally would never S-ON not even for warranty repair.
As you correctly concluded, going S-ON with a custom HBOOT is fatal. If there is no question (ie you had total control over the phone during its entire lifetime and prefect memory of what you did to it), just go S-ON . Odds are, unless you *know* you flashed a custom HBOOT (which is invariably for the sole purpose of getting rid of annoying red warning text), you have a stock HBOOT. Life is short. It's only a phone. Just flash.
If you're *not* sure what HBOOT you may have flashed, the best way to prevent disaster is to just take total control of the situation and manually flash a stock HBOOT yourself just before attempting S-ON. There are plenty of threads that have the zip files you need. One caveat, a failed HBOOT flash is also fatal, so start with a fully charged battery and if you see "FAILED" during flashing, be sure NOT to reboot the phone before you fix it and confirm success.
Or, as suggested above, just RUU. Drastic, but failsafe.
Note *any* stock HBOOT, regardless of version, will allow the phone to boot after S-ON, although good style dictates you use one of the same vintage as all the other firmware and software you are running.
Sent from my HTC One using xda app-developers app
NxNW said:
Or, as suggested above, just RUU. Drastic, but failsafe.
Click to expand...
Click to collapse
Thank for taking all the time to write this up. Am I to gather from this sentence here that an RUU will reinstall the stock HBOOT? I'm not bothered about wiping the phone since I am not keeping it and already have all of my data backed up. I have had total control of the phone, the only problem was that I was getting android-info parse errors trying to run the Developer Edition RUU with the stock, but S-OFF, HBOOT. Someone provided an HBOOT for me that apparently had the correct android-info setup and it worked perfectly.
Well, yes, RUU touches every partition and puts each one back exactly the way HTC approves of, including the partition containing HBOOT. (And the write method it uses is safer than flashing things manually.)
But you have already observed it can be a pain to get RUU's to succeed sometimes. In your case, S-OFF helps greatly so you should eventually be able to run a RUU just fine. If, in the process, you change your CID to "SuperCID" (11111111) be sure to change it back to your phone's real CID before going S-ON. S-ON is the absolute last step in any procedure you are contemplating.
Sent from my HTC One using xda app-developers app
Alright, lets get into this. My camera has purple tint, so I was going to return to stock and take it in. This isn't my first attempt at returning to stock, last time I failed but was able to flash the GPE RUU. I'm with Rogers, so on this attempt I once again tried using the rogers RUU, I changed my CID back to ROGER001, I re-locked bootloader and put S-ON. Ran the RUU and got error 155. So I re-acquired s-off with Rumrunner. Then I locked the bootloader and put S-ON again. When I tried rebooting I got Tampered, Locked, Security Warning. Recovery seems to have disappeared, any attempt to reboot brings me back to the bootloader. I've attempted flashing a rogers recovery from an OTA, I've tried flashing the rom.zip out of the Rogers RUU, I've tried flashing the GPE RUU zip. Basically anything I try ends with (bootloader) signature checking... FAILED (remote: signature verify fail). I've tried unlocking the bootloader from HTCDEV, the screen prompt to unlock the bootloader doesn't appear on my device. I've tried running fastboot oem unlock (because it was GPE). Anything I could think of I tried.
TLR I bricked it good. Do I have any options?
Cazrelleum said:
Alright, lets get into this. My camera has purple tint, so I was going to return to stock and take it in. This isn't my first attempt at returning to stock, last time I failed but was able to flash the GPE RUU. I'm with Rogers, so on this attempt I once again tried using the rogers RUU, I changed my CID back to ROGER001, I re-locked bootloader and put S-ON. Ran the RUU and got error 155. So I re-acquired s-off with Rumrunner. Then I locked the bootloader and put S-ON again. When I tried rebooting I got Tampered, Locked, Security Warning. Recovery seems to have disappeared, any attempt to reboot brings me back to the bootloader. I've attempted flashing a rogers recovery from an OTA, I've tried flashing the rom.zip out of the Rogers RUU, I've tried flashing the GPE RUU zip. Basically anything I try ends with (bootloader) signature checking... FAILED (remote: signature verify fail). I've tried unlocking the bootloader from HTCDEV, the screen prompt to unlock the bootloader doesn't appear on my device. I've tried running fastboot oem unlock (because it was GPE). Anything I could think of I tried.
TLR I bricked it good. Do I have any options?
Click to expand...
Click to collapse
nope your pretty much done, you could have run over it with a truck ..same effect
http://forum.xda-developers.com/showthread.php?t=2664757
Cazrelleum said:
Alright, lets get into this. My camera has purple tint, so I was going to return to stock and take it in. This isn't my first attempt at returning to stock, last time I failed but was able to flash the GPE RUU. I'm with Rogers, so on this attempt I once again tried using the rogers RUU, I changed my CID back to ROGER001, I re-locked bootloader and put S-ON. Ran the RUU and got error 155. So I re-acquired s-off with Rumrunner. Then I locked the bootloader and put S-ON again. When I tried rebooting I got Tampered, Locked, Security Warning. Recovery seems to have disappeared, any attempt to reboot brings me back to the bootloader. I've attempted flashing a rogers recovery from an OTA, I've tried flashing the rom.zip out of the Rogers RUU, I've tried flashing the GPE RUU zip. Basically anything I try ends with (bootloader) signature checking... FAILED (remote: signature verify fail). I've tried unlocking the bootloader from HTCDEV, the screen prompt to unlock the bootloader doesn't appear on my device. I've tried running fastboot oem unlock (because it was GPE). Anything I could think of I tried.
TLR I bricked it good. Do I have any options?
Click to expand...
Click to collapse
GPE bootloader 1.54+ can not be unlocked (the well known GPE bootloader bug)
You did the final blow when turning it back S-ON.
Now that you can't boot it, you can't achieve s-off anymore and the only work around for the GPE bootloader unlock bug require S-OFF.
So you are stuck with a non-bootable, non s-off'able, non-unlockable phone, well, a brick with written proof that you have caused it yourself (tampered flag in the bootloader)
Sorry :crying:
Now time to send your phone for repair or to buy another one.
Try this
http://forum.xda-developers.com/showthread.php?t=2363516
Thread closed and cleaned up at OP's request.