Database Info

[Q] CANNOT UNLOCK BOOTLOADER USING htcdev.com

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

Can't unlock bootloader

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 can't flash my Wiko View 3 Lite ROM (can someone help me pls? :/ )

Hello to everyone that read and thanks you for the time passing to read my problem.
First of all : this is not my native language so excuse me for my english ... :/
After that, this is my first thread ... :/
And then , i'm tryin to learn but i'm pretty newbie on computing ... :/
(i'm trying to root my phone like every newbie does first by following slowly and accurately this tutorial: https://www.getdroidtips.com/root-wiko-view-3-lite/
i'm gonna details all i did step by step but at the end cause i don't think that the problem come from here)
so after etablishing the connection between my device and the PC using a wiko usb driver
i tried to flash my Wiko View 3 Lite ROM to boot the patched "boot.img" via Minimal ADB and Fastboot V1.4.3 (latest version)
so once i enter the command : fastboot flash boot "MyPatchedBootFile".img
i got a :
Failed.(flashing lock flag is locked. Please unlock it first!)
so i should able the flashing option somehow somewere ?
i tried several fastboot command but nothing... (btw i is there a way to kow all the comandes i can do on my PC cause i see the command changing depending phones or fastboot )
that's what i have :
FAILED (remote :Not implemet.)
i'm not sure to understand what "no implemet" mean ??
I can't find any useful info exept this one unfortunately that could be the same for my phone's model :
Rooting a wiko jerry is impossible due to all fastboot commands lock the phone
On Linux: All fastboot commands lock. Particularly fastboot oem unlock or fastboot flashing unlock. After removing and re-attaching the phone to the usb port (without turning it off), the phone bec...
android.stackexchange.com
i'm continuing to look for anwsers, can someone have an idea ??
( that's what i did:
1/ i've downloaded magisk.apk's last vertion on my phone
2/ found a Wiko View 3 Lite full ROM online for the rom.pac file
3/ converted it w the SPD flash tool (i didn't really understood this step :/) : https://www.getdroidtips.com/patch-boot-img-root-spreadtrum-device/
4/ sent it to my phone
5/converted it agan via magisk.apk on my phone
6/ took it back from my computer to the same folder that i launch the ADB and fastboot comand prompt
7/last step normally :/ i should write the command: fastboot flash boot xxxxxxxxx.img and i gotstuck here ....
)
thanks again for all your help guys ))

Hakodu13 said:
...
so once i enter the command : fastboot flash boot "MyPatchedBootFile".img
i got a :
Failed.(flashing lock flag is locked. Please unlock it first!)
so i should able the flashing option somehow somewere ?
i tried several fastboot command but nothing... (btw i is there a way to kow all the comandes i can do on my PC cause i see the command changing depending phones or fastboot )
that's what i have :
FAILED (remote :Not implemet.)
i'm not sure to understand what "no implemet" mean ??
I can't find any useful info exept this one unfortunately that could be the same for my phone's model :
Rooting a wiko jerry is impossible due to all fastboot commands lock the phone
On Linux: All fastboot commands lock. Particularly fastboot oem unlock or fastboot flashing unlock. After removing and re-attaching the phone to the usb port (without turning it off), the phone bec...
android.stackexchange.com
i'm continuing to look for anwsers, can someone have an idea ??
...
Click to expand...
Click to collapse
Before trying to deal with phone's bootloader, will say running any Fastboot commands, you have to enable "OEM unlock" option in phone's Android Settings->Developer option. If done so, reboot phone. Afterwards run Fastboot commands
Code:
fastboot devices
fastboot oem unlock <- or: fastboot flashing unlock

jwoegerbauer said:
Before trying to deal with phone's bootloader, will say running any Fastboot commands, you have to enable "OEM unlock" option in phone's Android Settings->Developer option. If done so, reboot phone. Afterwards run Fastboot commands
Code:
fastboot devices
fastboot oem unlock <- or: fastboot flashing unlock
Click to expand...
Click to collapse
Hey
Thanks for your awnser,
i did it already, i've activated EOM unlock , USB debug and also desactivated the standby when the phone is plugged
also i think all fastboot command work cause i can reboot my phone using "fastboot reboot"command
fastboot devices reconize my phone
fastboot flashing unlock dosn't work
it is writed: FAILED (remote: Not implemet.)
fastboot oem unlock dosn't work,
it is writed: FAILED (remote: unknown cmd.)
something interesting is when i write fastboot "AnithingElse" unlock
it says: fastboot: usage: unknown command "AnithingElse"
and no: FAILED (remote: unknown cmd.)
like if adbandfastboot know the commannd " fastboot oem unlock " somehow but not my phone.
thanksthanksthanks again for your awnser!!!

My guess is that running Fastboot commands is denied by OEM/Carrier. And that's not wondering me because phone is based on UniSoc chipset.
AFAIK to get Fastboot working on such phones you have to request from OEM/Carrier the unlock-code as 1st thing of all things and when received have to flash it to phone.

jwoegerbauer said:
My guess is that running Fastboot commands is denied by OEM/Carrier. And that's not wondering me because phone is based on UniSoc chipset.
AFAIK to get Fastboot working on such phones you have to request from OEM/Carrier the unlock-code as 1st thing of all things and when received have to flash it to phone.
Click to expand...
Click to collapse
Ye i guessed the commands is denied on purpose
but why ? just for me not to have root acces ?
and what if i want to flash or reflash my ROM just to have back a new fresh boot ?
do a lot of phone constructor use that radical trick ?
and what is OEM/Carrier ? where can i find this ? i can't find anything online ...
merci ))

OEM is an acronym and stands for Original Equipment Manufacturer ( e.g Samsung )
Carrier is the is cell phone company that provide cellular service to cell phone users ( e.g. AT&T, Verizon )

zte a7 blade 2019 instant switch to os from fastboot*

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.

Question Is it possible to OEM Unlock a CN to WW ROG Pho 5s Pro, I've tried everything

I'm on the latest Android 13. I've been trying to unlock and root this phone but OEM Unlock isn't in Developer Options and most fastboot commands give the error FAILED (remote: 'Command not supported in default implementation').
I contaced Asus and that's how I found out it was originally a CN version(now WW) but they said they can't help me. I've installed ADB, Fastboot and the USB drivers and the phone is detected by "fastboot devices" but "fastboot oem unlock" gives the above error. fastboot flashing unlock gives error Unrecognised command.
Not sure if this means anything but all the adb commands to reboot to bootloader/recovery/fastboot all just reboot to the first "Start" page option.
I found a thread here that seemed to be specifically about my problem but the contents were deleted and nothing else I've found has helped me past this point(a few other posts were very helpful though).
Am I stuck on this? Thanks for any info you can give.

<Moderator Edit>: Post edited. I will PM you as to why shortly.
I have rog phone 5s pro tencent edition china rom... and I success to convert to global ww rom

krampyl said:
I'm on the latest Android 13. I've been trying to unlock and root this phone but OEM Unlock isn't in Developer Options and most fastboot commands give the error FAILED (remote: 'Command not supported in default implementation').
I contaced Asus and that's how I found out it was originally a CN version(now WW) but they said they can't help me. I've installed ADB, Fastboot and the USB drivers and the phone is detected by "fastboot devices" but "fastboot oem unlock" gives the above error. fastboot flashing unlock gives error Unrecognised command.
Not sure if this means anything but all the adb commands to reboot to bootloader/recovery/fastboot all just reboot to the first "Start" page option.
I found a thread here that seemed to be specifically about my problem but the contents were deleted and nothing else I've found has helped me past this point(a few other posts were very helpful though).
Am I stuck on this? Thanks for any info you can give.
Click to expand...
Click to collapse
You can't root this device that way. You need the ASUS unlock tool and I believe ASUS have pulled their unlock service for the time being. I think you will find tens if not hundreds of posts related to this topic on the forum. Patching via EDL is an option but not done so far as everyone have used the ASUS Unlock tool?

krampyl said:
I'm on the latest Android 13. I've been trying to unlock and root this phone but OEM Unlock isn't in Developer Options and most fastboot commands give the error FAILED (remote: 'Command not supported in default implementation').
I contaced Asus and that's how I found out it was originally a CN version(now WW) but they said they can't help me. I've installed ADB, Fastboot and the USB drivers and the phone is detected by "fastboot devices" but "fastboot oem unlock" gives the above error. fastboot flashing unlock gives error Unrecognised command.
Not sure if this means anything but all the adb commands to reboot to bootloader/recovery/fastboot all just reboot to the first "Start" page option.
I found a thread here that seemed to be specifically about my problem but the contents were deleted and nothing else I've found has helped me past this point(a few other posts were very helpful though).
Am I stuck on this? Thanks for any info you can give.
Click to expand...
Click to collapse
Also, do not pay anyone on Facebook or other places for this type of work. Just a friendly advise to save you some $.