I've noticed on a handful of threads here, people are wondering about locking your bootloader again to upgrade to the 1.85 RUU so I figured I'd post a little guide on how I did it.
If you're reading this I'm going to assume you are already on 1.82 with your bootloader unlocked. I will tell you how to relock it, upgrade, and unlock it again.
Just to make things simple, open the folder where you downloaded the tools to unlock your bootloader, and copy the adb.exe AdbWinApi.dll fastboot.exe and your Unlock_code.bin to C:\Android
First to Relock your device, you will want to boot into your bootloader and select fastboot. After you've selected fastboot plug your device into your pc and open a command prompt. You'll want to type 'cd C:\Android' and then 'fastboot oem lock' and your phone will restart with a locked bootloader. Now you can upgrade to the 1.85 RUU without any issues. Download 1.85 here: http://d-h.st/bS4 (thanks to kennethpenn)
Once you've finished upgrading to 1.85 you will want to boot into your bootloader again, with your device unplugged, and select fastboot. THEN plug your device in and run your command prompt again on your PC. Again, cd to C:\Android and type in the following command to unlock your bootloader again: 'fastboot flash unlocktoken Unlock_code.bin' (I've heard reports of some people having to type this command two or three times for it to work but it went the first time for me)
Now once you've finished unlocking your bootloader again you can install CWM Recovery the same way you did before.
I hope this helps! (And don't forget to hit thanks if it does)
And root will remain threw this process??? That's the only thing keeping me from updating...
Sent from my HTC One X using XDA
freshleysnipes said:
(I've heard reports of some people having to type this command two or three times for it to work but it went the first time for me)
Click to expand...
Click to collapse
I'm on my 5th try using that command, my 10th try in total.
Now on my 15th...
For those of you having trouble, try getting into recovery mode by sending the adb command:
adb reboot bootloader
Then unplug the cord as the phone is black
It should become filled with the bootloader, and then send the unlock command.
Its worked every time on the first time for me and I've done it 3 times.
rohan32 said:
For those of you having trouble, try getting into recovery mode by sending the adb command:
adb reboot bootloader
Then unplug the cord as the phone is black
It should become filled with the bootloader, and then send the unlock command.
Its worked every time on the first time for me and I've done it 3 times.
Click to expand...
Click to collapse
I just tried this twice. I'm going to just wait for jcase's root and try it again from scratch.
rpomponio said:
And root will remain threw this process??? That's the only thing keeping me from updating...
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Root will not remain. Once you upgrade to 1.85 and unlock bootloader and get cwm recovery, you will need to put this file (https://www.dropbox.com/s/z5un4z0kqye5dg0/CWM-SuperSU-v0.89.zip) anywhere in your sdcard/. Then use CWM to install it. This will give you root.
jmattp said:
I'm on my 5th try using that command, my 10th try in total.
Now on my 15th...
Click to expand...
Click to collapse
Try this: Before you type in that command use this one "fastboot devices" hit enter, then use "fastboot flash unlocktoken Unlock_code.bin".
jmattp said:
I just tried this twice. I'm going to just wait for jcase's root and try it again from scratch.
Click to expand...
Click to collapse
I believe some guy went up to 50 times before it worked. I'd try it out for a couple more mins.
Just type the command the first time, and then after that if it fails just hit the up arrow and hit enter again. and keep repeating that.
It's not just like it's failing though. I have to boot the phone up, skip through the setup screens, enable USB debugging, then start all over.
I'll give it a few more tries but I just don't see the logic in doing this so many times.
I bet this phone is pretty cool once you get to use it.
works for me on 2nd attempt. thank you. now to install su and dl custom rom
Holy crap it finally worked. I apologize for my nay-saying.
What I did different:
I actually turned it off instead of rebooting it with adb. I used the button combo to boot into fastboot. The first time it asked if I wanted to unlock or not. The second time it just changed to "unlocked" when I pushed the unlock code.
That was probably one of the worst ways I could have ever spent four hours.
Thanks for all of your suggestions.
see this seem like everything when ok....even get unlock lock with yes or no with all bla...bla it might void ur warranty....but when i hold vol down before rebooting and take me back to bootloader....still say relocked....? am i missing something here.....
C:\Android>cd android-sdk
C:\Android\android-sdk>cd platform-tools
C:\Android\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.018s]
finished. total time: 0.162s
C:\Android\android-sdk\platform-tools>
C:\Android\android-sdk\platform-tools>flash unlocktoken Unlock_code.bin
'flash' is not recognized as an internal or external command,
operable program or batch file.
C:\Android\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.150s
C:\Android\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.144s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.152s
C:\Android\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.148s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.156s
C:\Android\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.151s
C:\Android\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
OKAY [ 0.144s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.009s]
finished. total time: 0.158s
C:\Android\android-sdk\platform-tools>
ted77usa said:
see this seem like everything when ok....even get unlock lock with yes or no with all bla...bla it might void ur warranty....but when i hold vol down before rebooting and take me back to bootloader....still say relocked....? am i missing something here.....
C:\Android>cd android-sdk
C:\Android\android-sdk>cd platform-tools
C:\Android\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.018s]
finished. total time: 0.162s
C:\Android\android-sdk\platform-tools>
C:\Android\android-sdk\platform-tools>flash unlocktoken Unlock_code.bin
'flash' is not recognized as an internal or external command,
operable program or batch file.
C:\Android\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.150s
C:\Android\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.144s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.152s
C:\Android\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.148s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.156s
C:\Android\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.151s
C:\Android\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
OKAY [ 0.144s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.009s]
finished. total time: 0.158s
C:\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
Try what I did. Turn it off first. Completely shut it off. Unplug the phone.
Power on while holding volume down to get into bootloader. Press power again to enter fastboot.
Plug in the phone, flash unlocktoken, choose "yes". When it reboots, power off again. Unplug the phone.
Power on while holding volume down to get into bootloader. Press power again to enter fastboot
Plug in the phone, flash unlocktoken.
When I did this, "relocked" changed to "unlocked". There was no prompt... it just changed. Maybe you'll have the same experience.
what do you do if you didnt save the original files?
The_Zodiac said:
what do you do if you didnt save the original files?
Click to expand...
Click to collapse
If you still have the email you got from HTCDev, either in your inbox or trash can, just redownload the attachment they gave you to unlock
freshleysnipes said:
If you still have the email you got from HTCDev, either in your inbox or trash can, just redownload the attachment they gave you to unlock
Click to expand...
Click to collapse
i just seen this post, and yes it works. i did it after upgrading, but i relocked it for now because i cant root, or install recovery. so, unlocked isnt really doing anything for me right now.
rob219 said:
i just seen this post, and yes it works. i did it after upgrading, but i relocked it for now because i cant root, or install recovery. so, unlocked isnt really doing anything for me right now.
Click to expand...
Click to collapse
You can install CWM Recovery without root, and still flash custom roms.
I have a little bit different of an issue with the unlocked bl upgrading to RUU 1.85. I keep getting an error when doing so that says "Signature verification failed". Looking at the the ruu logs, I see that is the case from the adb commands.
Here is what I have done. I am finally to the point of asking for some advice on this.
1. Stock 1.73, obtained root, unlocked bootloader through one-click method, obtaining superCID (verified it was such through fastboot)
2. Installed CWM
3. relocked phone via fastboot command (verified hboot said "relocked")
4. Tried to update via RUU, no dice
5. Went ahead and reunlocked, pulled the recovery image out of the 1.73 package, pushed that to phone, relocked, tried again, nothing
6. Tried to upgrade to 1.73 just in case, same error
7. Set CID back to CWS__01 just in case that was causing me some problems.
Same issues all around. I have been told by Scott that all my version numbers on an untouched device match mine.
I am trying to push the RUU from Windows XP running inside vmware fusion on my mac.
-jason
If I unlocked and changed to SuperCID, do I have to relock or can I just flash the new RUU, install CWM through the script and then use it to push SU?
Sent from my HTC One X using XDA
mzimmer88 said:
If I unlocked and changed to SuperCID, do I have to relock or can I just flash the new RUU, install CWM through the script and then use it to push SU?
Click to expand...
Click to collapse
You will have to relock before flashing the new RUU or else you will get an error
----
@jtalley I've never seen that error myself, but surely someone else around here has
freshleysnipes said:
You will have to relock before flashing the new RUU or else you will get an error
----
@jtalley I've never seen that error myself, but surely someone else around here has
Click to expand...
Click to collapse
So this is how it is until S-OFF is achieved, eh?
Sent from my HTC One X using XDA
i have problem in my sensation ,when do unlock for bootloader then make lock bootloader i forget and do lock bootloader twice ,and now apeear to me <relocked bootloader> with <s-on>and now i make unlock bootloader toooooo much times and bad result and when install recovery write it <<<<FAILED (remote: signature verify fail)>>>>please help me to unlock it again
gawgaw said:
i have problem in my sensation ,when do unlock for bootloader then make lock bootloader i forget and do lock bootloader twice ,and now apeear to me <relocked bootloader> with <s-on>and now i make unlock bootloader toooooo much times and bad result and when install recovery write it <<<<FAILED (remote: signature verify fail)>>>>please help me to unlock it again
Click to expand...
Click to collapse
did you try to use unlocked bin code again?if not then do it again
i do it tooo much,and using many tools
now i can think only one thing.flash the specific ruu.exe for your device and start from the beginning
see here
http://forum.xda-developers.com/showthread.php?t=1672425
otherwise if you have patience wait for someone else to provide you a solution
i do all of this and install <RUU FILES>and the problem not fixed ,i copy this information to help you and indicate my problem
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\george>cd C:\Program Files\Android\android\platform-tools
C:\Program Files\Android\android\platform-tools>Unlock_code.bin
C:\Program Files\Android\android\platform-tools>fastboot flash unlocktoken Unloc
k_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.160s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.192s
C:\Program Files\Android\android\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 3.243s]
finished. total time: 3.250s
C:\Program Files\Android\android\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
OKAY [ 3.190s]
finished. total time: 3.195s
C:\Program Files\Android\android\platform-tools>fastboot flash zip PG58IMG.zip
sending 'zip' (23984 KB)...
OKAY [ 4.164s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 9.370s
C:\Program Files\Android\android\platform-tools>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.431s]
finished. total time: 0.435s
confirm something
when you use the ruu.exe did you have successful result for flashing it?
yes,the result successful but the problem not fixed ,bootloader relocked
gawgaw said:
yes,the result successful but the problem not fixed ,bootloader relocked
Click to expand...
Click to collapse
ok then
the only thing that i can tell you is to follow the whole process for unlocking the bootloader
start from the beginning.if that don't work too then i am out of ideas
best wishes
if i think something else i will tell you
thank you tooo much ,im sorry to tired you
Can you boot the phone now?
Also did the phone came from a repair with motherboard replaced?
Sent from my HTC Sensation using xda premium
Hi guys ;
i tried to unlock bootloader on my desire s via htcdev.com. i got file Unlock_code.bin. On the next step
C:\Android>fastboot flash unlockten Unlock_code.bin
sending 'unlockten' (0 KB)...
OKAY [ 0.018s]
writing 'unlockten'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.034s
i got this. i couldn't unlock bootloader. i tried on different usb ports Do you have any idea How can i fix this ?
qurshot said:
Hi guys ;
i tried to unlock bootloader on my desire s via htcdev.com. i got file Unlock_code.bin. On the next step
C:\Android>fastboot flash unlockten Unlock_code.bin
sending 'unlockten' (0 KB)...
OKAY [ 0.018s]
writing 'unlockten'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.034s
i got this. i couldn't unlock bootloader. i tried on different usb ports Do you have any idea How can i fix this ?
Click to expand...
Click to collapse
fixed. I tried different computers and usb ports. Finally fixed. :good:
qurshot said:
fixed. I tried different computers and usb ports. Finally fixed. :good:
Click to expand...
Click to collapse
Make sure fastboot is unchecked in the settings. Menu, settings, power options than uncheck fastboot and ensure usb debugging is enabled
qurshot said:
fixed. I tried different computers and usb ports. Finally fixed. :good:
Click to expand...
Click to collapse
It was because you used "unlockten" instead of "unlocktoken". The error message is not helpful since it says signature is invalid because it tried to flash a partition such as boot or recovery or whatever. But our Unlock_code.bin is not signed this kind of way.
A friend brought a HTC One Mini in a very unusual situation to me. The phone bootloader is "Locked" and "S-ON". It only boots to fastboot usb mode only. The battery is still ok because I checked with a script that is used to charge in that mode when the battery is low; at least it still has about 3870mV, and the minimum is around 3680mV. The problem is that:
1. When I try to unlock so I can flash a custom TWRP recovery the unlock spalsh screen does not appear, although the unlock command says sucessful.
C:\fastboot-win>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.154s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.161s
Click to expand...
Click to collapse
2. I downloaded this stock file OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_HK_3.10.708.4-2.12.708.3_release_351634.zip because it matches the OS version showing on the fastboot screen on the phone. When I try to flash it from fastboot I get this error:
C:\fastboot-win>fastboot flash zip OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_HK_3.10.708.4-2.12.708.3_release_351634.zip
sending 'zip' (346477 KB)...
OKAY [ 16.826s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 49.466s
Click to expand...
Click to collapse
Can anyone please render any help? I can follow any instructions to the letter, just that I have never come across this kind of issue before.
Thanks in advance.
Hi, I have a very frustrating problem with my HTC One Mini.
Out of nowhere, my phone won't boot into the OS but goes straight into the bootloader.
This is what my bootloader looks like:
Code:
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
OS-4.09.401.3
eMMC-boot 1024MB
Jun 24 2014, 15:21:25 0
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can't perform a factory reset and I can't get into recovery either. I tried to unlock the phone so I could flash the recovery and install a ROM from there. So I went to htcdev.com and started the bootloader unlock process. I downloaded the Unlock_code.bin file and tried to flash the unlock token:
Code:
fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800227328 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.016s]
finished. total time: 0.172s
Nothing happens on the phone after this. I read on the forums I maybe had to run a RUU so I went to the HTC ROM download page and downloaded the RUU and ran it. The phone rebooted but didn't go into RUU mode. After some time, I get a USB Connection error (171).
I tried to get into RUU mode with fastboot but that also doesn't work.
Code:
fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 2
(bootloader) Start Verify: 3
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 1.953s]
finished. total time: 1.953s
From here, I don't know what to do next and I hope you can help me.
Thanks in advance.
Welcome to the XDA forums, Vyperz52! I'm currently trying to solve a very similar problem with my HTC One Mini, and I have one suggestion that might help. Have you tried flashing some different form of recovery? Trying to flash TWRP recovery might work, it didn't for me but it's worth a try [https://twrp.me/devices/htconeminigsm.html]. Try the Fastboot install method (reading and accepting the risks that come with trying to install different recovery software).
imapanther said:
Welcome to the XDA forums, Vyperz52! I'm currently trying to solve a very similar problem with my HTC One Mini, and I have one suggestion that might help. Have you tried flashing some different form of recovery? Trying to flash TWRP recovery might work, it didn't for me but it's worth a try. Try the Fastboot install method (reading and accepting the risks that come with trying to install different recovery software).
Click to expand...
Click to collapse
Thank you for your reply.
I tried what you said but unfortunately, it's not working.
Code:
fastboot flash recovery twrp.img
target reported max download size of 800227328 bytes
sending 'recovery' (11460 KB)...
OKAY [ 1.500s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.424s
My phone is still locked so I think that's why flashing the recovery fails.
im also having problem with the bootloader unlock.
i have stuck in the 10th step of htcdev.com
any ideas why i cant see the warning on the phone?
btw the phone doesnt boot. i have access only to bootloader and fastboot on my phone
elessargr said:
im also having problem with the bootloader unlock.
i have stuck in the 10th step of htcdev.com
any ideas why i cant see the warning on the phone?
btw the phone doesnt boot. i have access only to bootloader and fastboot on my phone
Click to expand...
Click to collapse
I contacted HTC about the bootloader unlock issue but they won't help because they don't recommend unlocking the BL because it can cause the phone to crash and become unusable. After which I replied to them that's already the case without doing the unlock.
hi guys i got the same problem as you i m stuck on bootloader menu my phone looks like this
*** UNLOCKED ***
M4_UL PVT SHIP S-OFF RL
CID-HTC__102
HBOOT-2.22.0000
OS-4.09.401.3
eMMC-boot 1024MB
Jun 24 2014, 15:21:25 0
Click to expand...
Click to collapse
this what i got when i tried somes fastboot command
PHP:
C:\Android>fastboot flash zip cm12.zip
sending 'zip' (257726 KB)...
OKAY [ 11.875s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 11.969s
C:\Android>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.031s
C:\Android>fastboot flash recovery recovery14.img
sending 'recovery' (9320 KB)...
OKAY [ 1.234s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.391s
cant boot into recovery and cant flash it via fastboot
can someone help us to solve this issue