I'm at the last step of this guide : http://forum.xda-developers.com/showthread.php?t=1864053
I got the unlock_code.bin and it said the token check was successful but the screen that asks me if I want to unlock bootloader does not show up.
try this
take your nunlock code bin and place it in adb/fastboot folder
open a command prompt there an do the last command from the thread you used
i hope i helped
edit:connect your device into the pc from bootloader
Related
So I followed the steps linked in this post to unlock the bootloader:
http://forum.xda-developers.com/showthread.php?t=1672284
Which links to this site:
http://briefmobile.com/how-to-unlock-att-one-x-bootloader
Everything was fine until I got to step 21) Press any key in the tool to resume.
I pressed the space bar after clicking the tool to highlight it and the tool just closed. My phone is still hooked up to the computer and is sitting on the bootloader mode.
What should I do from here? I have the unlock token, root, 1.73, etc.
Thanks in advance!
***SOLVED***
In case anyone is wondering I solved the problem by finishing the Bootloader Unlock steps manually.
In the email sent from HTCDev with the Unlock token, I followed the link that outlines the steps.
I downloaded the SDK to get the adb and fastboot executables. Following the HTCDev steps, I moved the Unlock_token.bin into the same dir as the aforementioned executables and then sent the Unlock token through the command prompt.
Unlocked and ready to go!
while unlocking bootloader on the command prompt window i gave first command ''fastboot'" devices and it succeded but when i entered the second command correctly along with the key it showed failed to command ,,plssss help i want to unlock the bootloader
Which method you used for unlocking bootloader and which phone you are using
Hello,
I tried to unlock my bootloader following the guide stickied in general. I got the message from minimal adb and fastboot the unlock was succesful, now when I try to root it fails on install, so I went to check the status through the # code thingy. Before it said yes, now it says no.. What happened?
So I got my new U12+, bought the unlocked version, I'm pretty sure when it updated it became locked??
Anyway, went to HTCdev to unlock and I get this message when I try
Security checking failed DENY
Shows it as locked S-ON
Should I reset it then get S-Off?
Sounds like you might be confusing a few things.
The Unlocked version is the sim-unlocked. The boot loader will be Locked S-ON. Two different things.
Now to unlock your boot loader to run custom software make sure you follow the steps exactly on HTCdev website.
Get your token key while in Download Mode, copy and paste the correct parts. Then unlock once you have the correct unlock token bin from HTC.
Unlocking your boot loader is all down while in Download Mode. Make sure your have OEM boot loader unlock enabled in Developer Settings.
What a dummy....
OK, de-bugging on and OEM unlocking is enabled.
Tried the steps at HTC and got no response from the phone after typing the get identifier command
I'll try again
BTW, is it just me or is it a pain to get the button sequence just right?
geoffwoerner said:
What a dummy....
OK, de-bugging on and OEM unlocking is enabled.
Tried the steps at HTC and got no response from the phone after typing the get identifier command
I'll try again
BTW, is it just me or is it a pain to get the button sequence just right?
Click to expand...
Click to collapse
It's annoying. But if you have adb on your computer with Debugging enabled within Developer Settings.
adb reboot bootloader
Thatll save you a few a minute or two
OK, so now I'm stumped again,
adb reboot bootloader
phone reboots as it should
fastboot oem get_identifier_token and nothing
<waiting for any device>
Never Mind, took a few tries and new drivers, we're good to go!
How were you able to resolve it? what drivers should i download? I tried twice and i am getting the same message:
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
HTC u 12 Plus . android 9. adb and fastboot installed on a mac os mojave
I posted this in the appropriate forum but this phone is so old I've not received any response.
So I've decided to root and customize my Z2 Force and want to unlock the bootloader to get TWRP installed. All device side settings are correct (USB Debug, OEM unlock etc.) in developer mode. ADB commands are working fine as I can see my SN when using ADB Devices command. I then reboot to the bootloader through ADB (adb reboot bootloader) and it works fine and my Z2 boots into the bootloader. Then I try to get the unlock code (fastboot oem unlock) and I get a message after trying to run the command: access denied. I started my CMD window using run as admin - no help. Installed ADB all over again with new generic drivers and moto drivers - no help. Even installed everything in the root directory on my hard drive - no help
I don't understand why I'm getting this message. I've unlocked and rooted all my phones over the years but they've all been HTC. Never messed with a moto phone before. Anyone think this is a permalocked bootloader version - MODEL:XT1789-04 TYPE:M29E2
Things I have not tried yet:
Another computer
Tested fastboot command on one of my other phones
Any help is appreciated.
theandies said:
I posted this in the appropriate forum but this phone is so old I've not received any response.
So I've decided to root and customize my Z2 Force and want to unlock the bootloader to get TWRP installed. All device side settings are correct (USB Debug, OEM unlock etc.) in developer mode. ADB commands are working fine as I can see my SN when using ADB Devices command. I then reboot to the bootloader through ADB (adb reboot bootloader) and it works fine and my Z2 boots into the bootloader. Then I try to get the unlock code (fastboot oem unlock) and I get a message after trying to run the command: access denied. I started my CMD window using run as admin - no help. Installed ADB all over again with new generic drivers and moto drivers - no help. Even installed everything in the root directory on my hard drive - no help
I don't understand why I'm getting this message. I've unlocked and rooted all my phones over the years but they've all been HTC. Never messed with a moto phone before. Anyone think this is a permalocked bootloader version - MODEL:XT1789-04 TYPE:M29E2
Things I have not tried yet:
Another computer
Tested fastboot command on one of my other phones
Any help is appreciated.
Click to expand...
Click to collapse
The process to unlock a moto phone is a bit different. OEM commands are as it says, defined by the OEM. They need to be precise and functional. The command:
Code:
fastboot oem unlock
alone will not work.
Step1:
Instead, You should enter:
Code:
fastboot oem get_unlock_data
You will get an unique 131 ID string that looks for example like this:
Code:
(bootloader) 0000000000000000000000000000001
(bootloader) 0000000000000000000000000000002
(bootloader) 0000000000000000000000000000003
(bootloader) 0000000000000000000000000000004
(bootloader) 0000005
Copy the output to a text editor and delete the (bootloader) and the spaces in between, so it's one whole string.
Step2:
Visit the official Moto unlock website. Sign-in with your account, you will be using the E-mail used to create said account to receive the unlock key. Paste the edited 131 ID string and click Can my device be unlocked? button. If it is unlockable, then a conformation page will appear asking for consent and warranty bla bla bla.... Just read it and accept.
Step3:
When you click unlock, you will receive a KEY through your E-mail attached to the moto account used. Save that E-mail somewhere offline, as it can be used to re-unlock the bootloader in the future if you relock it. Connect your device in fastboot again and type:
Code:
fastboot oem unlock KEY
Where KEY is the one you got in the E-mail.
Done!!! Enjoy your freedom , also check the mark near my answer if it solved your question so others don't have to search for long.
Thanks for your reply. Yes I wrote the fastboot command wrong in my post.
The problem I'm having is even when using the fastboot command you posted I still get "access denied" when using fastboot commands. ADB works fine allowing me to reboot into the bootloader through the command prompt/USB as in ADB devices.
theandies said:
Thanks for your reply. Yes I wrote the fastboot command wrong in my post.
The problem I'm having is even when using the fastboot command you posted I still get "access denied" when using fastboot commands. ADB works fine allowing me to reboot into the bootloader through the command prompt/USB as in ADB devices.
Click to expand...
Click to collapse
As long as in Android -> Settings -> Developer options the option "OEM unlock" isn't got enabled - and phone got rebooted afterwards - you receive the reported error.
OEM unlocking is turned on in developer settings
I'll post up some screenshots soon. Right now I'm on day three of work on the 12 hour night shift.