Hello,
I've got a bricked htc One mini with S-on and HBOOT version: 2.22 and i'm trying to unlock the boot-loader via HTCDev and I've got the token for the unlock but when I try and push it onto the device (via fastboot) I get a message in the command prompt saying "unlock token check successfully" but I don't get any prompt on the phone for boot-loader unlock.
I have the drivers from HTC sync manager and uninstalled it. I have checked with the "ADB DEVICES" but no devices are listed despite having the drivers.
Any help would be much appreciated thanks.
Related
Hi I have unlocked bootloader via htcdev but done nothing else. I am still on stock rom but would like to now run the new ruu. what should I do. how do i lock the bootloader again. Thanks in advance
Use adb/Fastboot tool from command prompt in windows.
Load the phone into bootloader, connect your phone through usb to your computer and run the following commands:
Fastboot devices
Fastboot oem lock
You may need to install HTC sync for the usb drivers
This will lock your bootloader.
Sent from my HTC Desire S using xda app-developers app
i have registered on htcdev.com.
i followed the steps to the point where i had to execute the fastboot file to get an identifier token using a cmd command.
for some reason it say "waiting for device"
it has been like that for hours.
tried it about 3 times. I had a problem with rebooting into bootloader using VOLUME DOWN + POWER button so i ised abd and it worked
exact command i typed was "fastboot oem get_identifier_token"
PLEASE HELP ME
You don't have the right drivers for fastboot, it seems.
Find a guide and install them.
I always run ADB devices or fastboot devices first to check that I'm connected to the phone, before running any other commands.
Sent from my Nexus 7
Hello for everyone!
Htc one s (s3) can't unlock bootloader, always stay relocked. I try everything, many unlocking tools, regular metod whit Htcdev, token subm, kingo unlocked... Nothing change.
VILLEC2 PVT SHIP S-ON RL
HBOOT-3.01.0000
RADIO-16.11.20.24_M
Software stock JB4.1.1
Any solution.
Greeting from Serbia
Aleksic82 said:
Hello for everyone!
Htc one s (s3) can't unlock bootloader, always stay relocked. I try everything, many unlocking tools, regular metod whit Htcdev, token subm, kingo unlocked... Nothing change.
VILLEC2 PVT SHIP S-ON RL
HBOOT-3.01.0000
RADIO-16.11.20.24_M
Software stock JB4.1.1
Any solution.
Greeting from Serbia
Click to expand...
Click to collapse
Hi,
I have the exact same problem... unable to unlock the phone...
when in bootloader : "adb devices" show my device
when in fastboot : "fastboot devices" show nothing and "fastboot oem get_identifier_token" get stuck in "<waiting for device>"
Also, when in bootloader, if i choose "recovery", i can't enter the recovery menu, instead i have a warning sign for about 1 minut, then unit reboot.
Hope someone found a solution...
Thanks,
ndaneau said:
Hi,
I have the exact same problem... unable to unlock the phone...
when in bootloader : "adb devices" show my device
when in fastboot : "fastboot devices" show nothing and "fastboot oem get_identifier_token" get stuck in "<waiting for device>"
Also, when in bootloader, if i choose "recovery", i can't enter the recovery menu, instead i have a warning sign for about 1 minut, then unit reboot.
Hope someone found a solution...
Thanks,
Click to expand...
Click to collapse
Whn you see the red warning sing, I believe, you have to press VOLUME UP to see the recovery menu. As for undetectable devices in fastboot, I assume you are using Windows 8.1 or higher. Fastboot doesn't work there, unless fixed by using the instructions and registry edit from this thread (I can confirm, it works like a charm).
Let me know if you need any more help and if it worked.
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.