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
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.
Hello, I got a google pixel 1 stuck in fastboot, power button is not working just cicling through commands like start, restart bootloader, recovery mode, power off. Flashshing stock rom not working... android 7.1 wich is in inside this phone, android 8, android 10 nothing all of those nothing. Every flash is giving me that error. I used "flash-all.bat" inside the google factory image folder... Drivers are installed and working... Fastboot devices recognise it, Fastboot reboot reboot's the device in fastboot mode.... Device is locked and I can't unlock it... Can somebody help me please ? Thank you so much !!!
target reported max download size of 536870912 bytes
sending 'bootloader' (32380 KB)...
OKAY [ 0.769s]
writing 'bootloader'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.869s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57240 KB)...
OKAY [ 1.335s]
writing 'radio'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.432s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
< waiting for device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate 1622564756 bytes
error: update package missing system.img
Press any key to exit...
SAMPPLE said:
Hello, I got a google pixel 1 stuck in fastboot, power button is not working just cicling through commands like start, restart bootloader, recovery mode, power off. Flashshing stock rom not working... android 7.1 wich is in inside this phone, android 8, android 10 nothing all of those nothing. Every flash is giving me that error. I used "flash-all.bat" inside the google factory image folder... Drivers are installed and working... Fastboot devices recognise it, Fastboot reboot reboot's the device in fastboot mode.... Device is locked and I can't unlock it... Can somebody help me please ? Thank you so much !!!
target reported max download size of 536870912 bytes
sending 'bootloader' (32380 KB)...
OKAY [ 0.769s]
writing 'bootloader'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.869s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57240 KB)...
OKAY [ 1.335s]
writing 'radio'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.432s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
< waiting for device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate 1622564756 bytes
error: update package missing system.img
Press any key to exit...
Click to expand...
Click to collapse
What do you mean the device is locked?
If the bootloader is locked you can not manually flash a factory image.
If the IMEI starts with 35 it is a verizon Pixel XL with a locked boot loader.
Go to this thread and try to unlock the bootloader.
If you are successful.
Download this Fastory image: 10.0.0 (QP1A.191005.007.A3, Dec 2019) from Prerequisites b.
in the guide below.
Download the latest SDK platform-tools r29.0.5 from Prerequisites c. in the guide below.
Use this guide to update to android 10 (Q). Do #4 'wipe data' then do #9 if you want to root.
Homeboy76 said:
What do you mean the device is locked?
If the bootloader is locked you can not manually flash a factory image.
If the IMEI starts with 35 it is a verizon Pixel XL with a locked boot loader.
Go to this thread and try to unlock the bootloader.
If you are successful.
Download this Fastory image: 10.0.0 (QP1A.191005.007.A3, Dec 2019) from Prerequisites b.
in the guide below.
Download the latest SDK platform-tools r29.0.5 from Prerequisites c. in the guide below.
Use this guide to update to android 10 (Q). Do #4 'wipe data' then do #9 if you want to root.
Click to expand...
Click to collapse
Thank you so much for your reply but the devices will not exit fastboot whatever I do and yes bootloader is locked.
SAMPPLE said:
Thank you so much for your reply but the devices will not exit fastboot whatever I do and yes bootloader is locked.
Click to expand...
Click to collapse
What did you try to exit fastboot?
Homeboy76 said:
What did you try to exit fastboot?
Click to expand...
Click to collapse
Cmd command fastboot reboot and let it drain until 0% and nothing... because power button is working like a volume button...
SAMPPLE said:
Cmd command fastboot reboot and let it drain until 0% and nothing... because power button is working like a volume button...
Click to expand...
Click to collapse
How To Turn ON And OFF Pixel And Pixel XL With Broken Power Button
Google is your friend don't be afraid to use it.
Homeboy76 said:
How To Turn ON And OFF Pixel And Pixel XL With Broken Power Button
Google is your friend don't be afraid to use it.
Click to expand...
Click to collapse
I know I tried a lot of things to make it work... but nothing... Anyway thank you for helping me
put it in the freezer for an hour and tell me what happens, mine booted up with that, just put it in properly (all phone holes covered)