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
Related
I can't get the bootloader unlocked on a phone I just purchased with a relocked bootloader. I am on firmware 2.20 and my CID reads 11111111. I enter the unlock code and it says successful and I get the warning message on my phone about unlocking the bootloader and I hit yes to unlock. After the phone reboots all my data is wiped but when I reboot back into bootloader it still says relocked. I have tried multiple times with multiple unlock codes but no dice. I cannot get into stock recovery either after running the stock RUU. Anyone have any ideas? Thanks.
bsharp8 said:
I can't get the bootloader unlocked on a phone I just purchased with a relocked bootloader. I am on firmware 2.20 and my CID reads 11111111. I enter the unlock code and it says successful and I get the warning message on my phone about unlocking the bootloader and I hit yes to unlock. After the phone reboots all my data is wiped but when I reboot back into bootloader it still says relocked. I have tried multiple times with multiple unlock codes but no dice. I cannot get into stock recovery either after running the stock RUU. Anyone have any ideas? Thanks.
Click to expand...
Click to collapse
boot into the ROM and make sure USB debugging is enabled.. Reboot to fastboot and type "fastboot erase cache" and then try to unlock again
absolutelygrim said:
boot into the ROM and make sure USB debugging is enabled.. Reboot to fastboot and type "fastboot erase cache" and then try to unlock again
Click to expand...
Click to collapse
Bingo! That did the trick. Thank you very much. Man I do miss my old s-off phones.
Hi,
I got into a frustrating situation, I installed Oneplus OTA update after that phone is stuck in bootloop, only thing I can access is fastboot, after reading many articles, I found that unlocking bootloader can fix my problem.
But unlocking bootloader has become worst nightmare in OnePlus one, when I run # sudo fastboot oem unlock, it will reboot phone and goes into 1+ logo, then I reboot the phone again boot into bootloader and situation is still the same bootloader is still locked.
I also tried OnePlus toolkit, onplus toolbox and oneplus tool for linux, nothing is unlocking the bootloader.
Phone is not enabled for adb (debugging mode).
adb shows "offline" mode while phone in bootloop logo.
is there any way I can atleast force the phone to unlock boot, any help is appreciated?
I am a linux user, but I aslo tried in windows, samething.
Thanks
I think you need to sit down and re-read the guide on how to unlock your bootloader because you're not having a good understanding on what you're supposed to do.
http://forum.xda-developers.com/showthread.php?t=2788632 Read that thread and adjust accordingly to Linux unless you do it on a Windows-based machine.
zephiK said:
I think you need to sit down and re-read the guide on how to unlock your bootloader because you're not having a good understanding on what you're supposed to do.
http://forum.xda-developers.com/showthread.php?t=2788632 Read that thread and adjust accordingly to Linux unless you do it on a Windows-based machine.
Click to expand...
Click to collapse
Hi,
Thanks for reply, I have followed the complete guide to unlock bootloader, I updated the android sdk to the latest with android drivers.
Find the attachment how I have done that, but still the bootloader is locked.
In device status it shows that device temperted: true, is there any way I can change that to false using fastboot command?,
maybe that is the thing preventing me to unlock the bootloader.
Your help is appreciated.
Thanks
Dani
I only used 15 second adb installer on my PC for adb drivers. That way I don't copy paste files into SDK folder.
Anyways fastboot OEM device-info gives back tamper true and what is the other flag?
Make sure u don't put in typo like your op "ulock" lol fastboot OEM unlock should bring up wipe options on your phone :s
Sent From Bacon
ek69 said:
I only used 15 second adb installer on my PC for adb drivers. That way I don't copy paste files into SDK folder.
Anyways fastboot OEM device-info gives back tamper true and what is the other flag?
Make sure u don't put in typo like your op "ulock" lol fastboot OEM unlock should bring up wipe options on your phone :s
Sent From Bacon
Click to expand...
Click to collapse
Hi ek,
screen shots are attached with the reply to zephiK's message (all flags can been seen), however, fastboot oem unlock doesnt bring me wipe option (though I am ok to wipe).
Dani
After the fastboot OEM unlock command look at the phone, that is where the wipe stuff appears. Or it should.
Sent From Bacon
Hi everyone,
Today I decided to root my Mate 9.
I started out with turning 'OEM unlock' on and usb debugging. With ADB installed and the huawei drivers, I began to unlock my bootloader. On the 'EMUI Huawei' homepage I filled out my device details and obtained an unlock code. I opened ADB and checked with 'adb devices' if my device was there. It was. So I continued with typing 'adb reboot bootlader'. After that I typed 'fastboot devices'. My device was still showing up. I typed 'fastboot oem unlock CODE (with the code). On my screen I pressed 'Yes'. Bootloader unlocked.
After this step I tried to flash twrp with the command 'fastboot flash recovery xxxx.img'. I couldn't continue because every adb/fastboot command keeps failing (remote: command not allowed). Now when I boot up my phone it shows 'your device has been unlocked and can't be trusted'. Phone=unlocked, FRP=locked. I can't do anything.
Device: Mate 9 L29C432B198
What did I do wrong or what did I missed? :crying:
I had this issue at first to had to redownload the original rom via the phone recovery this will fix the frp lock then u have to unlock and flash twrp 3.1.01 that is linked in the threads on here
Did it format after it unlocked?
You can try fastboot oem relock UNLOCKCODE
Then go to Settings -> Dev options -> enable OEM Unlocking
Then unlock again.
It probably will fail though if FRP is locked, but worth a shot.
Edit: It's supposed to say
PHONE Unlocked FRP Unlock
Hi, i am loading booting to bootloader from adb with commnad (adb reboot bootloader) this isnt working, only restart its instantly switch to normal os, any ideas ?
Run
Code:
adb reboot
or
Code:
fastboot reboot
oh sorry man, i am idiot, and i am say it wrong.. I trying boot to fastboot but not working instantly switch to os, any ideas please ?
Unlock bootloader if not done yet.
where i unlock bootloader ? In developer settings ? (i have unlocked)
Enabling OEM Unlock in Developer options doesn't unlock the bootlader, it simply prepares the bootloader to get unlocked via fastboot command.
More info here:
How to Unlock Bootloader via Fastboot on Android
Unlocking the bootloader via Fastboot is the easiest thing to do. But not all Android devices support straightforward bootloader unlocking. Many manufacturers put up a setup on their devices to let…
nerdschalk.com
xXx yYy said:
Enabling OEM Unlock in Developer options doesn't unlock the bootlader, it simply prepares the bootloader to get unlocked via fastboot command.
More info here:
How to Unlock Bootloader via Fastboot on Android
Unlocking the bootloader via Fastboot is the easiest thing to do. But not all Android devices support straightforward bootloader unlocking. Many manufacturers put up a setup on their devices to let…
nerdschalk.com
Click to expand...
Click to collapse
Only I have a small problem I don't unlock my bootloader via fastboot when it doesn't work :/ It immediately jumps to my system when I boot fastboot, even with a command like ,,adb reboot fastboot"
Matyas66055 said:
Only I have a small problem I don't unlock my bootloader via fastboot when it doesn't work :/ It immediately jumps to my system when I boot fastboot, even with a command like ,,adb reboot fastboot"
Click to expand...
Click to collapse
I have new thread, where i am writing all info :/ https://forum.xda-developers.com/t/zte-blade-a7-2019-fastboot-mode-missing.4462035/
I don't know if you are still interested in accessing Fastboot but you can access it using a specific firmware version.
Still, let me tell you that unlocking the bootloader is virtually impossible. Since the well-known generic method doesn't work for the SoC SC9863A, you need to have a special Fastboot's program version and a dedicated private key that only they provide.... and I emphasize the word "dedicated" since apparently ZTE did not use a generic key to sign their ROMS. At least on this device.
Unless they decide to release the key or give support to unlocking the bootloader, all we can do is wait for them to change their minds. Because they don't want to provide it. I know because I tried to order it several times.
Used MSMDT to reset to TMO firmware on KB2007 (OnePlus 8T) and now bootloader is locked and unlock token doesn't work again "FAILED (remote: 'Error - Verify Failed ! (4:-2)')" and my bootloader is permanently locked. Any help would be appreciated.
The MSM Tool returns the device to the way it was when you took it out of the box and booted it for the first time. Do you have USB Debugging enabled in Developer Options? You only need the token once. Have you tried using ADB to unlock the bootloader?
I checked oem unlock in the settings, and then tried to flash twrp and got an error saying the device was locked, tried fastboot oem unlock, and it told me to flash the unlock token, but it won't accept the token.
Try requesting another through OnePlus Support then.