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've been trying to flash a stock recovery or CWM Touch onto my HTC One using fastboot.exe that came with the latest version of ADK.
This is what happened:
sending 'recovery' (9480 KB)...
OKAY [ 1.096s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.630s
Please help. I've looked upon at least 30 websites, including xda-developers.Thanks!
Why don't you just flash it through the app? Or flash twrp through goo manager. It's also touch based.
mr_verystock said:
I've been trying to flash a stock recovery or CWM Touch onto my HTC One using fastboot.exe that came with the latest version of ADK.
This is what happened:
sending 'recovery' (9480 KB)...
OKAY [ 1.096s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.630s
Please help. I've looked upon at least 30 websites, including xda-developers.Thanks!
Click to expand...
Click to collapse
Redownload the image.
mr_verystock said:
I've been trying to flash a stock recovery or CWM Touch onto my HTC One using fastboot.exe that came with the latest version of ADK.
This is what happened:
sending 'recovery' (9480 KB)...
OKAY [ 1.096s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.630s
Please help. I've looked upon at least 30 websites, including xda-developers.Thanks!
Click to expand...
Click to collapse
It sounds like your bootloader is still locked. Unlock it through htcdev before trying to fastboot flash recovery.
Sent from my HTC One S using Tapatalk 2
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
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.
After i got my unlock Code from Huawei and enabled Usb Debugging mode and Oem unlock in developer options,I've Unlocked my bootloader Successfully.
my phone Started to Do a factory reset and it failed so i did it by myself manually.
after that i enabled Usb Debugging mode ,but i couldnt enable oem unlock option and i boot my phone to fastboot and Started flashing the TWRP...but it said:
Writing...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
can Someone help me to Flash recovery and root my phone?
phone info's:
Model:MHA-L29
Build num. : MHA-L29C185B138
Bootloader Unlocked
Maybe lock it and unlock again.
gm007 said:
Maybe lock it and unlock again.
Click to expand...
Click to collapse
the problem is that i cant do any operation on Bootloader including locking bootloader...
ezraiil1 said:
the problem is that i cant do any operation on Bootloader including locking bootloader...
Click to expand...
Click to collapse
C:\Users\Abolfazl\Desktop\>fastboot flash recovery 1.img
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.500s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
C:\Users\Abolfazl\Desktop\>fastboot flash recovery 1.img
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.500s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
C:\Users\Abolfazl\Desktop\>fastboot oem lock
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\Users\Abolfazl\Desktop\>fastboot oem unlock *********
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\Users\Abolfazl\Desktop\>fastboot oem lock
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\Users\Abolfazl\Desktop\>fastboot devices
AHK7N16B18003212 fastboot
What version of fastboot do you have?
5[Strogino] said:
What version of fastboot do you have?
Click to expand...
Click to collapse
Minimal ADB and Fastboot
ezraiil1 said:
After i got my unlock Code from Huawei and enabled Usb Debugging mode and Oem unlock in developer options,I've Unlocked my bootloader Successfully.
my phone Started to Do a factory reset and it failed so i did it by myself manually.
after that i enabled Usb Debugging mode ,but i couldnt enable oem unlock option and i boot my phone to fastboot and Started flashing the TWRP...but it said:
Writing...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
can Someone help me to Flash recovery and root my phone?
phone info's:
Model:MHA-L29
Build num. : MHA-L29C185B138
Bootloader Unlocked
Click to expand...
Click to collapse
try to revoke usb debugging then enable again
eddmecha said:
try to revoke usb debugging then enable again
Click to expand...
Click to collapse
it doesnt work...
ezraiil1 said:
it doesnt work...
Click to expand...
Click to collapse
have you tried with a different cable & pc?how about your drivers?is it the lastest?
I had the exact same problem. Disable everything related to "Find my phone" and restart. TWRP will flash after this.
ezraiil1 said:
After i got my unlock Code from Huawei and enabled Usb Debugging mode and Oem unlock in developer options,I've Unlocked my bootloader Successfully.
my phone Started to Do a factory reset and it failed so i did it by myself manually.
after that i enabled Usb Debugging mode ,but i couldnt enable oem unlock option and i boot my phone to fastboot and Started flashing the TWRP...but it said:
Writing...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
can Someone help me to Flash recovery and root my phone?
phone info's:
Model:MHA-L29
Build num. : MHA-L29C185B138
Bootloader Unlocked
Click to expand...
Click to collapse
eddmecha said:
have you tried with a different cable & pc?how about your drivers?is it the lastest?
Click to expand...
Click to collapse
Problem Solved.
Had to pay 30$ to Funkyhuawei to Flash a firmware and Unlock it again.
Problem Solved.
Had to pay 30$ to Funkyhuawei to Flash a firmware and Unlock it again.
Thank you everybody,all of you were Useless xD
love u all.
Cya!