Database Develop

OEM Lock failed - stuck!!

Hi
I went to update my firmware earlier so went to update the firmware, but first had to relock the bootloader.
I typed fastboot oem lock and got ... underneath it and it stuck there for hours. The screen on the phone had frozen too.
In the end I pulled the cable to go back into bootloader. The CMD prompt then said it had relocked it and then some read error.
I think the system is now wiped as all it does is boot into bootloader or fastboot. I tried to send the stock recovery img from ARHD site but get a signature error.
What should I do?
I have tampered and relocked at the top of the bootloader screens and fastbootoem lock does confirm it is locked
Thanks!

I have done the exact same thing! I am kinda freaking out.

TheMathMan said:
Hi
I went to update my firmware earlier so went to update the firmware, but first had to relock the bootloader.
I typed fastboot oem lock and got ... underneath it and it stuck there for hours. The screen on the phone had frozen too.
In the end I pulled the cable to go back into bootloader. The CMD prompt then said it had relocked it and then some read error.
I think the system is now wiped as all it does is boot into bootloader or fastboot. I tried to send the stock recovery img from ARHD site but get a signature error.
What should I do?
I have tampered and relocked at the top of the bootloader screens and fastbootoem lock does confirm it is locked
Thanks!
Click to expand...
Click to collapse
1. try and unlock the bootloader again
2. flash custom recovery twrp or cwm
3. adb sideload rom.zip within custom recovery.
hopefully that will get you up and running again.
i had a similar problem where system got completely wiped, i couldnt adb sideload though. just couldn't get it to work. luckily i have an otg cable, so i mounted a flash stick in twrp and flashed custom rom via otg and everything fine again.
hope this helps

dazbutler1 said:
1. try and unlock the bootloader again
2. flash custom recovery twrp or cwm
3. adb sideload rom.zip within custom recovery.
hopefully that will get you up and running again.
i had a similar problem where system got completely wiped, i couldnt adb sideload though. just couldn't get it to work. luckily i have an otg cable, so i mounted a flash stick in twrp and flashed custom rom via otg and everything fine again.
hope this helps
Click to expand...
Click to collapse
OK. Phew!!!
Unlocked bootloader again with the unlock token. Then it rebooted straight into ARHD 4.6 that was on there, so it obviously hadn't been wiped but some sort of odd issue.
Now a bit concerned about trying to update firmware again, as when it had "security warning" fastboot oem rebootRUU didn't work at all.
Would love some more info about this and how to do it better next time!

TheMathMan said:
OK. Phew!!!
Unlocked bootloader again with the unlock token. Then it rebooted straight into ARHD 4.6 that was on there, so it obviously hadn't been wiped but some sort of odd issue.
Now a bit concerned about trying to update firmware again, as when it had "security warning" fastboot oem rebootRUU didn't work at all.
Would love some more info about this and how to do it better next time!
Click to expand...
Click to collapse
Glad you got it running again. are you talking about flashing the new firmware.zip ota file that contains new radio. If so i can't really shed any light on this for you as my cid is h3g_001 so currently i can't update my firmware

dazbutler1 said:
Glad you got it running again. are you talking about flashing the new firmware.zip ota file that contains new radio. If so i can't really shed any light on this for you as my cid is h3g_001 so currently i can't update my firmware
Click to expand...
Click to collapse
Yep thats right, the firmware.zip. CID is HTC__001 on mine. Assume that it is anyway, and that reading it from within ARHD doesn't show it differently? Never looked before flashing the custom rom.

TheMathMan said:
Yep thats right, the firmware.zip. CID is HTC__001 on mine. Assume that it is anyway, and that reading it from within ARHD doesn't show it differently? Never looked before flashing the custom rom.
Click to expand...
Click to collapse
easiest way to confirm cid is download cid getter from play store. if its HTC_001 you should be fine.

Yep, done that and confirmed with getvar all so should be fine. Now I just need to relock the bootloader so it lets me rebootRUU. Last time it refused and froze.

TheMathMan said:
Yep, done that and confirmed with getvar all so should be fine. Now I just need to relock the bootloader so it lets me rebootRUU. Last time it refused and froze.
Click to expand...
Click to collapse
hope you have more luck this time then.

Odd. Worked perfectly second time around. Done and dusted within minutes. No idea what went wrong!?!?

Please help, possible brick after following guide to flash firmware

I was following Vomer's guide on my One, which has been working great. I had HBOOT 1.54, S-Off, SuperCID, and pushed the firmware twice, got the success message, and waited and when it says finished used adb to tell it to reboot. Now I get the splash, with the lock gone, as expected, and then the screen goes black. If I hold power, or power and down, the hardware keys start blinking and then nothing. A few seconds later I get the splash again, then blank again.
It appears to be communicating briefly over USB because my laptop starts trying to install a HTC MTP device (drive is already on the PC and has been fine) before it looses comms and drops out. I can't seem to get adb device to recognize it....
PLEASE tell me someone can help me recover my phone!!! I will be immensely grateful.

And what the HBOOT version you wanted to downgrade to?

Ivanovic said:
And what the HBOOT version you wanted to downgrade to?
Click to expand...
Click to collapse
I wasn't trying to downgrade HBOOT, just rather ensure my firmware was up to date. I'd had mine set up as a GPE and was flashing the DE (after supercid).
By way of an update, I've been able to get into bootloader and I'm a bit scared on what to do next so I dont screw this up. I notice that I still have S-OFF, but HBOOT is now showing 1.56 and it says RELOCKED at the top. My plan was to use rumrunner (just because of the HBOOT, but it is erroring anyway) to unlock bootloader, and then to look up the fastboot commands to push a ROM and recovery. Any advice?

Downgrade to 1.44 and change cid according to the Rom you want. Then unlock or set your bootloader to LOCKED
Here is the file for 1.44 http://www69.zippyshare.com/v/95229262/file.html
Sent from my HTC One using Tapatalk

Can you help me with the adb commands to flash that boot zip? Also, should I run " fastboot flash unlocktoken Unlock_code.bin" to unlock my bootloader first?

vettejock99 said:
Can you help me with the adb commands to flash that boot zip? Also, should I run " fastboot flash unlocktoken Unlock_code.bin" to unlock my bootloader first?
Click to expand...
Click to collapse
You can unlock if you want to flash custom recovery.
Place the file i gave you to the fastboot folder. Boot into bootloader and choose FASTBOOT.
Run the following : fastboot oem rebootRUU
fastboot flash zip filename.zip *where filaname the actual filename of the file i gave you
You will get FAILED or sth so do this command again to succesfully flash the firmware.

Ivanovic said:
You can unlock if you want to flash custom recovery.
Place the file i gave you to the fastboot folder. Boot into bootloader and choose FASTBOOT.
Run the following : fastboot oem rebootRUU
fastboot flash zip filename.zip *where filaname the actual filename of the file i gave you
You will get FAILED or sth so do this command again to succesfully flash the firmware.
Click to expand...
Click to collapse
Awesome. So I've got HBOOT 1.44, S-OFF, bootloader unlocked, supercid, and TWRP 2.6.3.3 flashed again, and I tried sideloading ARHD rom. It all looked good but same thing for the moment, I get the splash and then black......I can't figure out why I can't boot into a rom right now. About to try flashing ROM again.
Okay, so didnt' work. After sideload flashing gets to 100% it just does nothing. Manually rebooting gets me back into the splash then blackness bootloop......

Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu

SaHiLzZ said:
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
Click to expand...
Click to collapse
The former didn't get me anywhere, but I did follow your thinking and decided to use the RUU and start over. I'm happy to report that got me going, and then I was able to get AR HD on. I probably had to do that all along once I wiped the ROM and recovery, as sideloading clearly wasn't going to work (in retrospect) as it has an AROMA installer.
Thanks so much everyone!!

SaHiLzZ said:
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
Click to expand...
Click to collapse
Nice that everything is solved now.
Verstuurd van mijn HTC One

[Q] I Have Completely Bork'd My Phone

After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams

misterasset said:
After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams
Click to expand...
Click to collapse
You've had an htc one for two years?

BableMan said:
You've had an htc one for two years?
Click to expand...
Click to collapse
No. Started out with my Nexus S, then moved to a Nexus 4, then gave that to my wife and got an HTC One. I love this phone so much I wish I'd had it for two years already, but no.
Do you have any idea of a new path I can try?

misterasset said:
After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams
Click to expand...
Click to collapse
Just to know.. Did you try to flash a RUU.exe or a RUU.zip? I had a lot of problems with the .exe files, while flashing the RUU.zip from command line usually work like a charm to me.
Sent from my HTC One using Tapatalk

Delgra said:
Just to know.. Did you try to flash a RUU.exe or a RUU.zip? I had a lot of problems with the .exe files, while flashing the RUU.zip from command line usually work like a charm to me.
Click to expand...
Click to collapse
I have tried both actually. I used Hansoon2000's (I'm at work so hopefully I'm referencing that correctly) all in one toolkit to try to flash the RUU.zip file back to the device. It fails while transferring to the device every single time.
So next I tried to use the RUU.exe, both a newer and older version, for my CID and I get the mysterious Error 155 Unknown Error.
How do I flash the RUU.zip from the command line? I have tried using "Install zip from sideload" but I get a Status Error 7 when trying to flash ROM.zip files, and I have tried using ADB PUSH to push the ROM.zip over to the phone but since there's no file structure it doesn't really ever end up anywhere on the phone. (I'm using ROM.zip generically here for my CM ROMs, not RUU) Is there a command line or ADB function to flash the RUU.zip file that I'm not aware of?
Thanks,
Chris

misterasset said:
So next I tried to use the RUU.exe, both a newer and older version, for my CID and I get the mysterious Error 155 Unknown Error.
Thanks,
Chris
Click to expand...
Click to collapse
Error 155 -> you're probably on hboot 1.55+, so you need to downgrade hboot separately first, (to hboot 1.44) then you can run the RUU. download here: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot reboot-bootloader
-> confirm hboot is 1.44
and run RUU.
PS: you have to be s-off obviously.

nkk71 said:
Error 155 -> you're probably on hboot 1.55+, so you need to downgrade hboot separately first, (to hboot 1.44) then you can run the RUU. download here: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot reboot-bootloader
-> confirm hboot is 1.44
and run RUU.
PS: you have to be s-off obviously.
Click to expand...
Click to collapse
Thanks for the info. I'm actually on HBOOT 1.44 already luckily. But I am not S-Off. Is that why the RUU is not working? I tried to use the All-In-One Toolkit to achieve S-Off now, but without a file structure it didn't work.
Any direction on achieving S-Off while it's so messed up?
Thanks,
Chris

misterasset said:
Thanks for the info. I'm actually on HBOOT 1.44 already luckily. But I am not S-Off. Is that why the RUU is not working? I tried to use the All-In-One Toolkit to achieve S-Off now, but without a file structure it didn't work.
Any direction on achieving S-Off while it's so messed up?
Thanks,
Chris
Click to expand...
Click to collapse
Please:
1- date of bootloader
2- a "fastboot getvar all" (remove IMEI and s/n)
3- link to the RUU you are trying to use.
Don't forget pressing the little thanks button for people who have helped

No offense but it sounds as if you simply aren't running an ruu.zip correctly. I'm not understanding all this hensonn2000 or toolkit talk that you have going on. You flash ruu.zip while the phone is in fastboot oem RUU mode. Not that complicated. Also the error 155 was the bootloader being unlocked if I recall correctly. You have to relock it before flashing or running the appropriate RUU. Specially if youre s-on.

Thanks guys. I ended up getting it all working. I did not have the Bootloader relocked and that was why the RUU kept failing.
Thanks again for the extra direction,
Chris

[Q] HTC One unrooting stuck on bootloader

Hi Everyone
While trying to unroot my one i eventually got stuck on my bootloader. What happened was that I typed in "fastboot oem lock" in adb and now I can't go into recovery or reboot. I know I should install a RUU at this point but I can't find an RUU for my phone! When I get "fastboot getvar all" I see that my "version-main" is 3.23.666.1 (is that the right one to look at?) and so I've scoured for hours for an RUU but only found OTAs which I don't know how to use. If it helps I'm on HBOOT 1.55.
I also remember pressing unroot in OTA unroot (I don't remember the exact app name) and tried pressing restore root but it did nothing so I started doing the above stuff with RUUs.
I'm pretty stumped right now and I would appreciate any help at all, thank you!

KoalaSuccess said:
Hi Everyone
While trying to unroot my one i eventually got stuck on my bootloader. What happened was that I typed in "fastboot oem lock" in adb and now I can't go into recovery or reboot. I know I should install a RUU at this point but I can't find an RUU for my phone! When I get "fastboot getvar all" I see that my "version-main" is 3.23.666.1 (is that the right one to look at?) and so I've scoured for hours for an RUU but only found OTAs which I don't know how to use. If it helps I'm on HBOOT 1.55.
I also remember pressing unroot in OTA unroot (I don't remember the exact app name) and tried pressing restore root but it did nothing so I started doing the above stuff with RUUs.
I'm pretty stumped right now and I would appreciate any help at all, thank you!
Click to expand...
Click to collapse
If you have an unlocktoken flash it with fastboot flashunlocktoken Unlock_code.bin
If you dont have it, go to htcdev.com and visit unlock bootloader section and follow instructions there.
Once your bootloader is unlocked again, flash twrp recovery and ABD sideload some ROM.
After this you can start all over again whatever it is you were trying to do.
P.S. this will not get you the right RUU package but it will get your phone back to useful condition.
My advice is first you find an RUU for your phone and then do the bootloader manipulations.

7ftnick said:
If you have an unlocktoken flash it with fastboot flashunlocktoken Unlock_code.bin
If you dont have it, go to htcdev.com and visit unlock bootloader section and follow instructions there.
Once your bootloader is unlocked again, flash twrp recovery and ABD sideload some ROM.
After this you can start all over again whatever it is you were trying to do.
P.S. this will not get you the right RUU package but it will get your phone back to useful condition.
My advice is first you find an RUU for your phone and then do the bootloader manipulations.
Click to expand...
Click to collapse
Thanks for the reply! I did that and my phone was working fine again. I went to go flash a stock rom that I found and it flashed fine but now the NFC logo flashes in the status bar even though it's not on. Also, my wifi doesn't work! It constantly says turning on wifi.. I'm trying to flash a different stock rom but I can't enter recovery anymore I would be fine except no wifi is a bit of a problem. Thank you for the reply by the way, is there a chance you can help me find an RUU for my phone? I've searched everywhere but there doesn't seem to be one.

KoalaSuccess said:
Thanks for the reply! I did that and my phone was working fine again. I went to go flash a stock rom that I found and it flashed fine but now the NFC logo flashes in the status bar even though it's not on. Also, my wifi doesn't work! It constantly says turning on wifi.. I'm trying to flash a different stock rom but I can't enter recovery anymore I would be fine except no wifi is a bit of a problem. Thank you for the reply by the way, is there a chance you can help me find an RUU for my phone? I've searched everywhere but there doesn't seem to be one.
Click to expand...
Click to collapse
There is no RUU for Bell devices. Have you checked my restore to stock for canadian users thread? Post #1 should be ok for you

SaHiLzZ said:
There is no RUU for Bell devices. Have you checked my restore to stock for canadian users thread? Post #1 should be ok for you
Click to expand...
Click to collapse
I took a look and I'll try it! Do you know if my device is Bell? I'm not sure how to tell.

SaHiLzZ said:
There is no RUU for Bell devices. Have you checked my restore to stock for canadian users thread? Post #1 should be ok for you
Click to expand...
Click to collapse
So I managed to get my phone working again thanks to your guide! but once I went in to get my S-OFF the program got stuck on pouring 2 after I left it for an hour I hard reset my phone and now I can't boot into recovery or main OS, just bootloader. But in bootloader I see at the top that it says my phone is S-OFF but I can't do the remove tampered because I can't use adb because I can't boot into main OS! I've tried flashing different recovery TWRP but it isn't changing anything..
Any help would be greatly appreciated

KoalaSuccess said:
So I managed to get my phone working again thanks to your guide! but once I went in to get my S-OFF the program got stuck on pouring 2 after I left it for an hour I hard reset my phone and now I can't boot into recovery or main OS, just bootloader. But in bootloader I see at the top that it says my phone is S-OFF but I can't do the remove tampered because I can't use adb because I can't boot into main OS! I've tried flashing different recovery TWRP but it isn't changing anything..
Any help would be greatly appreciated
Click to expand...
Click to collapse
did you erased cache after flashing the recovery?
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot in recovery again.

alray said:
did you erased cache after flashing the recovery?
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot in recovery again.
Click to expand...
Click to collapse
Yeah I did try to erase cache, no luck. but I managed to fix it by turning my S-OFF back to S-ON by typing fastboot oem writesecureflag 3
after that I flashed twrp again and then i was able to boot up to OS again. Thanks for the help everyone!

KoalaSuccess said:
Yeah I did try to erase cache, no luck. but I managed to fix it by turning my S-OFF back to S-ON by typing fastboot oem writesecureflag 3
after that I flashed twrp again and then i was able to boot up to OS again. Thanks for the help everyone!
Click to expand...
Click to collapse
well that is strange, you should have kept s-off and try other things first but well, its to late. At least your phone is working now

[Q] Q softbricked help please

hi i have done sum thing terrible to my phone and now i can only asses the boot loader cant get in to OS or recovery,
unable to flash new recovery and after trying to flash stock RUU i am stuck with boot loader relocked have tried to re unlock it but no luck.
s-on with os 7.19.401.2 any ideas on what to do?

Necrolog_92 said:
hi i have done sum thing terrible to my phone and now i can only asses the boot loader cant get in to OS or recovery,
unable to flash new recovery and after trying to flash stock RUU i am stuck with boot loader relocked have tried to re unlock it but no luck.
s-on with os 7.19.401.2 any ideas on what to do?
Click to expand...
Click to collapse
What steps did you take that led you to this point? Are you stock recovery at minute or are you custom recovery? Is your phone detected by fastboot (type fastboot devices)
Also I assume to tried HTC.com/dev to unlock using a different unlock token?

stovie_steve said:
What steps did you take that led you to this point? Are you stock recovery at minute or are you custom recovery? Is your phone detected by fastboot (type fastboot devices)
Also I assume to tried HTC.com/dev to unlock using a different unlock token?
Click to expand...
Click to collapse
just for future reference, he needs to flash the stock firmware, same one he already has, my suspicions say he has re-locked his bootloader with a custom recovery on there, thats why he cant unlock his bootloader, it requires stock recovery, the only way to get stock recovery on an s-on and re-locked device is to flash stock firmware. :good:

Seanie280672 said:
just for future reference, he needs to flash the stock firmware, same one he already has, my suspicions say he has re-locked his bootloader with a custom recovery on there, thats why he cant unlock his bootloader, it requires stock recovery, the only way to get stock recovery on an s-on and re-locked device is to flash stock firmware. :good:
Click to expand...
Click to collapse
Yeah I figured he'd done that, which is why I wondered was he custom recovery

thanks for the reply’s, i have now tried to use a new unlock token but i get the same problem as before, before i relocked the boot loader i flashed what i think was the stock recovery but now i can’t get in to recovery i can use fastboot and it does show up under fastboot devices and when i try to put the unlock token on i get the screen to confirm but when i confirm it boot into recovery and just stays there till the battery drains on i reboot it any more idea’s or advice ?