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?
In response to my Q below, a user wrote that if I go S-ON (to take the phone into repair) I can never go S-ON again. Is that true? I've restored my phone 100% to stock HBOOT, recovery OS etc. and I'm presently at HBOOT 1.57 and have locked the bootloader and have "*** LOCKED ***". So the only thing left is to go S-ON. But I'm wondering if this means I can never go S-ON again.
Thanks!
The original question: http://forum.xda-developers.com/htc-one/help/restore-m7-to-stock-q-hboot-t2999854
kenzorio said:
In response to my Q below, a user wrote that if I go S-ON (to take the phone into repair) I can never go S-ON again. Is that true? I've restored my phone 100% to stock HBOOT, recovery OS etc. and I'm presently at HBOOT 1.57 and have locked the bootloader and have "*** LOCKED ***". So the only thing left is to go S-ON. But I'm wondering if this means I can never go S-ON again.
Thanks!
The original question: http://forum.xda-developers.com/htc-one/help/restore-m7-to-stock-q-hboot-t2999854
Click to expand...
Click to collapse
You can go S On again any time
He advised you should not make it S On
because keep your SOff is beneficial
your phone is GPE so that's had firmware problem after 1.55 locking Bootloader it cant be unlocked if you are on S On that time
if you keep S Off you can Unlock your phone easily
as you know 1st time you need Unlock Bootloader then you make S Off but if you update Hboot then Lock Bootloader then S On its quiet hard to make it S Off again and using root custom Roms etc
IF YOU NOT UNDERSTAND ANSWER DONT WRITE A NEW THREAD ASK AGAIN IN SAME THREAD WE WILL HELP YOU THERE
kenzorio said:
In response to my Q below, a user wrote that if I go S-ON (to take the phone into repair) I can never go S-ON again. Is that true? I've restored my phone 100% to stock HBOOT, recovery OS etc. and I'm presently at HBOOT 1.57 and have locked the bootloader and have "*** LOCKED ***". So the only thing left is to go S-ON. But I'm wondering if this means I can never go S-ON again.
Thanks!
The original question: http://forum.xda-developers.com/htc-one/help/restore-m7-to-stock-q-hboot-t2999854
Click to expand...
Click to collapse
I did not mean you can never go s-off again. Most likely you phone will be returned with the latest software and hboot 1.57 installed and you'll have to pay to s-off. Many here have sent their phone to repair with s-off and had no problems getting repair.
and their phones were returned to them still s-off
clsA said:
I did not mean you can never go s-off again. Most likely you phone will be returned with the latest software and hboot 1.57 installed and you'll have to pay to s-off. Many here have sent their phone to repair with s-off and had no problems getting repair.
and their phones were returned to them still s-off
Click to expand...
Click to collapse
OK just to clarify - it originally wasn't a GPE. I converted it to GPE, and now I converted it back to stock (incl HBOOT, recovery etc.). Btw, in the post I mistakenly asked if it meant I could never go S-ON again. What I meant to ask was if I couldn't get S-OFF again!
But you say I have to pay to get S-OFF again. Is that because Sunshine is the only way to get S-OFF with HBOOT >= 1.57? Any chance that a free tool will come out that works as well?
Thanks
Moderator Information,
I will keep this thread open as you are getting help on it, but in future can you please keep to one thread per topic.
Thanks.
my htc one is stuck in the bootloader with the tampered banner on it, RELOCKED bootloader and also s-on. I have a viper one ROM on it an a twrp custom recovery.. now funny story I guarantee you will laugh. I knew the htc oem update was coming soon so I could get lollipop but I was rooted and couldn't do it. So I was trying to get s-off on my device but I missed a step on some gadget hacks tutorial and locked the bootloader (thats the funny part) then I tried unlocking it again but it didn't work. I tried going into recovery but it just rebooted back to the bootloader. I tried everything in the bootloader options and nothing worked.
my Hboot is version 1.57 and my OS is 6. 10.531.9
I tried flashing a recovery again and I cant do it it says "error cannot load--" and the same with the Unlock_code.bin it just wasn't working? what am I doing wrong and how can i fix it. please its urgent
if you have any answers you can comment here and also e-mail me at [email protected] (I would usually say text me :crying: ) once again please help I don't know what to do next.
kage_outram said:
my htc one is stuck in the bootloader with the tampered banner on it, RELOCKED bootloader and also s-on. I have a viper one ROM on it an a twrp custom recovery.. now funny story I guarantee you will laugh.
I knew the htc oem update was coming soon so I could get lollipop but I was rooted and couldn't do it. So I was trying to get s-off on my device but I missed a step on some gadget hacks tutorial and locked the bootloader (thats the funny part) then I tried unlocking it again but it didn't work. I tried going into recovery but it just rebooted back to the bootloader. I tried everything in the bootloader options and nothing worked.
my Hboot is version 1.57 and my OS is 6. 10.531.9
I tried flashing a recovery again and I cant do it it says "error cannot load--" and the same with the Unlock_code.bin it just wasn't working? what am I doing wrong and how can i fix it. please its urgent
if you have any answers you can comment here and also e-mail me at [email protected] (I would usually say text me :crying: ) once again please help I don't know what to do next.
Click to expand...
Click to collapse
Since, you are S-ON with a locked bootloader run this RUU 6.10.531.10. It will put you back at stock, then you can try to unlock you bootloader. To get S-OFF you will need to use Sunshine with your hboot 1.57.
majmoz said:
Since, you are S-ON with a locked bootloader run this RUU 6.10.531.10. It will put you back at stock, then you can try to unlock you bootloader. To get S-OFF you will need to use Sunshine with your hboot 1.57.
Click to expand...
Click to collapse
What commands do I put in to add the RUU
kage_outram said:
What commands do I put in to add the RUU
Click to expand...
Click to collapse
Download the RUU to your Windows computer
Connect the phone to the computer via USB
Boot into Bootloader/FASTBOOT USB on your phone
Double-click the RUU on your computer
majmoz said:
Download the RUU to your Windows computer
Connect the phone to the computer via USB
Boot into Bootloader/FASTBOOT USB on your phone
Double-click the RUU on your computer
Click to expand...
Click to collapse
what should happen next
Hi,
I have a HTC One that is not rooted, and has the problem with the camera (Pink in dark places).
What do i need to do for the phone to return to the original and turned to locked
I'm on H.BOOT 1.61, UNLOCKED and S-ON
Thanks for all the help
http://imgur.com/pXW59cZ
nurogo said:
Hi,
I have a HTC One that is not rooted, and has the problem with the camera (Pink in dark places).
What do i need to do for the phone to return to the original and turned to locked
I'm on H.BOOT 1.61, UNLOCKED and S-ON
Thanks for all the help
http://imgur.com/pXW59cZ
Click to expand...
Click to collapse
Are you running a custom ROM or stock ROM? And if it is stock ROM, does version are you running and does it match your current firmware? Please post a fastboot getvar all and remove your Serial No and IMEI
Because you are S-ON, you cannot LOCK the bootloader again, instead it will read RELOCKED. You need to be S-OFF to change the lock status
You may also get a TAMPERED message when you lock the bootloader using the command fastboot oem relock
If all is running stock I would chance it and send it in for repair, as at the end of the day this is a hardware fault not brought around by unlocking your bootloader
nurogo said:
Hi,
I have a HTC One that is not rooted, and has the problem with the camera (Pink in dark places).
What do i need to do for the phone to return to the original and turned to locked
I'm on H.BOOT 1.61, UNLOCKED and S-ON
Thanks for all the help
http://imgur.com/pXW59cZ
Click to expand...
Click to collapse
stovie_steve said:
If all is running stock I would chance it and send it in for repair, as at the end of the day this is a hardware fault not brought around by unlocking your bootloader
Click to expand...
Click to collapse
not 100% true, dont send your phone back relocked, you will need to do whatsteve says and get s-off, then flash an early RUU and HBOOT before locking the bootloader and going s-on, otherwise you risk the tampered flags coming back, the phone must be 100% stock.
HTC will refuse a warranty repair in any other condition, they will blame you on the grounds that since you unlocked the bootloader you could of done anything with the phone like flashed an unsupported kernal and overclocked etc, the camera issue is caused by overheating.
Seanie280672 said:
not 100% true, dont send your phone back relocked, you will need to do whatsteve says and get s-off, then flash an early RUU and HBOOT before locking the bootloader and going s-on, otherwise you risk the tampered flags coming back, the phone must be 100% stock.
HTC will refuse a warranty repair in any other condition, they will blame you on the grounds that since you unlocked the bootloader you could of done anything with the phone like flashed an unsupported kernal and overclocked etc, the camera issue is caused by overheating.
Click to expand...
Click to collapse
From my own experiencea friend sent it in with an unlocked boot loader and they repaired it. But they may have just been lucky.
I wouldn't return to s on on any bootloader later than 1.54, as when you do the writesecureflag command the phone will display a TAMPER DETECTED message and then you're back to square one
Best thing to do would be achieve s off using sunshine
Downgrade hboot to earlier version e.g. 1.44
flash an earlier RUU
Use revone to reset the status of the bootloader to LOCKED, ensure tamper message is not there
Then, if you really must, run the writesecureflag command. That's how I've done it before, and after hboot 1.54 you will def get the tamper detected message
I always leave my phone s off tho
stovie_steve said:
Are you running a custom ROM or stock ROM? And if it is stock ROM, does version are you running and does it match your current firmware? Please post a fastboot getvar all and remove your Serial No and IMEI
Because you are S-ON, you cannot LOCK the bootloader again, instead it will read RELOCKED. You need to be S-OFF to change the lock status
You may also get a TAMPERED message when you lock the bootloader using the command fastboot oem relock
If all is running stock I would chance it and send it in for repair, as at the end of the day this is a hardware fault not brought around by unlocking your bootloader
Click to expand...
Click to collapse
Seanie280672 said:
not 100% true, dont send your phone back relocked, you will need to do whatsteve says and get s-off, then flash an early RUU and HBOOT before locking the bootloader and going s-on, otherwise you risk the tampered flags coming back, the phone must be 100% stock.
HTC will refuse a warranty repair in any other condition, they will blame you on the grounds that since you unlocked the bootloader you could of done anything with the phone like flashed an unsupported kernal and overclocked etc, the camera issue is caused by overheating.
Click to expand...
Click to collapse
I'm on stock rom, but the problem is that i dont know how i can lock the bootloader ang going to s-on.
What steps should i follow?
Thanks for all the help
nurogo said:
I'm on stock rom, but the problem is that i dont know how i can lock the bootloader ang going to s-on.
What steps should i follow?
Thanks for all the help
Click to expand...
Click to collapse
At this point, how can i solve my problem?
Can anybody help me?
nurogo said:
At this point, how can i solve my problem?
Can anybody help me?
Click to expand...
Click to collapse
you need s-off so you can downgrade using a ruu, lock the bootloader and turn back s-on.
Try sunshine s-off and then follow nkk71's guide linke in my signature.