Database Develop

[SOLVED] HTC One can't unlock bootloader

I am attempting to unlock the bootloader on my HTC One. I am using the HTCdev method. I get to the step where I have to type "fastboot flash unlocktoken Unlock_code.bin" into cmd. cmd returns the following:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.151s
Click to expand...
Click to collapse
However, my phone stays on the white fastboot menu and doesn't shift to a new prompt.
Other possibly relevant information:
HTCsync doesn't recognize my device at all.
My computer DOES recognize my device, however, as it appears as an entry in device manager.
Typing "adb devices" into cmd returns a list with nothing in it, so adb is not recognizing the device either apparently.
Thanks very much to anyone who can offer help.

Toadsplat said:
I am attempting to unlock the bootloader on my HTC One. I am using the HTCdev method. I get to the step where I have to type "fastboot flash unlocktoken Unlock_code.bin" into cmd. cmd returns the following:
However, my phone stays on the white fastboot menu and doesn't shift to a new prompt.
Other possibly relevant information:
HTCsync doesn't recognize my device at all.
My computer DOES recognize my device, however, as it appears as an entry in device manager.
Typing "adb devices" into cmd returns a list with nothing in it, so adb is not recognizing the device either apparently.
Thanks very much to anyone who can offer help.
Click to expand...
Click to collapse
''adb devices'' only works when phone booted into OS or in recovery. In bootloader mode, use ''fastboot devices''.
You device should be listed as ''My Htc'' in windows devices manager. If not, your drivers are probably not installed.
Is this a GPE htc one?

alray said:
''adb devices'' only works when phone booted into OS or in recovery. In bootloader mode, use ''fastboot devices''.
You device should be listed as ''My Htc'' in windows devices manager. If not, your drivers are probably not installed.
Is this a GPE htc one?
Click to expand...
Click to collapse
Thanks for replying.
Yeah, "fastboot devices" turns up one entry just fine.
Yeah, there is an entry called "My HTC" under "Android Devices" in my devices manager.
No, it's not the GPE one.

Problem is still unresolved, thanks to anyone who might have advice

Let us see..
Toadsplat said:
Problem is still unresolved, thanks to anyone who might have advice
Click to expand...
Click to collapse
Could you please elaborate on the PC that u r using? Is it a windows 8.1 PC? Have you installed HTC Sync software? May be I could help you out.. I had lot of issues with my drivers before i could settle in with a working situation:victory:..

harihacker said:
Could you please elaborate on the PC that u r using? Is it a windows 8.1 PC? Have you installed HTC Sync software? May be I could help you out.. I had lot of issues with my drivers before i could settle in with a working situation:victory:..
Click to expand...
Click to collapse
Haha, actually, I think I may have just figured out the problem...I got the phone from ebay and I think it already must have had bootloader unlocked. I just flashed a recovery and it worked, so I think I just successfully rooted it...
Kind of embarrassing.
I will change the title tag to [solved] as soon as I confirm.
Sorry for being a noob!
Edit: Figured it all out. Got it rooted w/ s-off. Now time to try flashing a rom...thanks all.

Unable to unlock N6 bootloader (Android 6.0.1 Build MMB29X) [resolved]

Hi,
I am unable to unlock the bootloader on my Nexus 6, which was purchased new from Amazon.com. Or more accurately, I can issue the fastboot flashing unlock command without error, but my phone still says LOCKED and screen is frozen for 60 seconds.
I have followed the various HOWTOs on this website to the best of my ability:
1. Installed latest Android SDK tools(25.1.4.rc1), Platform-tools (24rc2) & Java8. I originally installed with the 23.1 platform-tools but then moved to the preview channel release when I had no luck.
2. USB debugging and OEM unlocking are both ON
3. Both "adb device" and "fastboot device" show my phone's serial number when in their respective modes, so I know communication is good between my laptop and phone.
How to replicate problem:
a. With my phone connected, I first issued "adb reboot bootloader". My phone then sucessfully changes to the AP Fastboot Flash Mode (Secure) screen. Beneath the green BATTERY OK (Charging) are the lines
Device is LOCKED. Status Code: 2
Transfer Mode: USB Connected
b. I then type "fastboot flashing unlock" and the output is
...
OKAY [ 0.016s]
finished. total time: 0.016s
However my phone does not ask me if I want to unlock. In fact, the screen then appears to be frozen -- pressing the volume up and down buttons does not change the power button selection menu. If I try to issue any other fastboot command, it says FAILED (command write failed (Unknown error)) finished. total time: 5.017s
The screen is frozen for 60 seconds. After that, the bootloader screen is once again functional (I can change menu options again) and I can issue new fastboot commands, such as 'fastboot reboot'
However, the device still says LOCKED and will refreeze for 60 seconds if I type 'fastboot flashing unlock'
Any suggestions would be appreciated!
Thank you.

type fastboot oem unlock to unlock your bootloader, then follow instruction. But beware, this will wipe your device

TMG1961 said:
type fastboot oem unlock to unlock your bootloader, then follow instruction. But beware, this will wipe your device
Click to expand...
Click to collapse
In newer versions of fastboot, the command is fastboot flashing unlock, not OEM unlock.
Code:
$ ./fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
flashall Flash boot, system, vendor, and --
if found -- recovery.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.

@webtrader,
@TMG1961 was trying to help you. Have you tried his recommendation before replying?

cam30era said:
@webtrader,
@TMG1961 was trying to help you. Have you tried his recommendation before replying?
Click to expand...
Click to collapse
No, I had not. I tried using fastboot oem unlock on an older version of the SDK toolkit and that had failed, but I had not tried using oem unlock again on the latest version, having noticed that "oem unlock" was no longer listed as an option.
I just tried it now on the latest SDK toolkit and it does indeed work for me. :good:
Thank you to the both of you for helping me out!

webtrader said:
No, I had not. I tried using fastboot oem unlock on an older version of the SDK toolkit and that had failed, but I had not tried using oem unlock again on the latest version, having noticed that "oem unlock" was no longer listed as an option.
I just tried it now on the latest SDK toolkit and it does indeed work for me. :good:
Thank you to the both of you for helping me out!
Click to expand...
Click to collapse
Welcome

i do believe the "fastboot flashing unlock" is for when a manufacture issues a binary token kinda of like how HTC does it. If the Nexus or any phone that is not carrier branded, "fastboot oem unlock" will be the command to pass.

OEM Unlock Command Failed - "Not supported command in current status"

I recently reverted to stock so I can start from scratch and install everything over again. After all that and booting into android, I checked the ADB and OEM Unlock options in my settings. Then I rebooted into the bootloader and entered the "fastboot OEM unlock" command I followed the on-screen instructions and selected "yes" to continue. The command prompt then shows the following:
(bootloader) Unlocking bootloader...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 24.776s
I've googled this for about an hour and a half and can't seem to find an answer. Any help would be greatly appreciated.

I don't know if it's a typo, but you said you "booted into android" which to me suggests normal android system.
(which might explain why you needed adb...you don't need to enable adb for fastboot mode)
How about booting into fastboot / bootloader mode instead and try your commands there.
(press/hold power and volume down buttons to get to fastboot/bootloader mode)
Sorry if I'm misunderstanding and you are in fact attempting this in fastboot/bootloader mode.
also type a "fastboot devices" command to make sure fastboot is working between phone and pc

Someone else posted exactly this question a few months ago.
Answer? The device was already unlocked.
http://forum.xda-developers.com/nexus-6/help/help-bootloader-unlock-t3349455

I figured that might be the case. I assumed flashing the factory image also re-locked the bootloader.

You had it right. I booted the Android system. I was following the steps on the All-In-One Beginner's guide which included enabling adb. But as for me running the unlock command, I was in the bootloader when trying that.
@dahawthorne gave me the right answer in saying the device is already unlocked. Now I have a separate issue where I can't complete the rooting process, but I'll post a separate thread if I can't figure that out.

TWRP Fastboot Command not allowed (P10)

Hi!
I'm trying to install TWRP on my P10. I've unlocked bootloader on Huawei website.
Whenever I'm typing in fastboot "flash recovery twrp.img" it goes through and everything says OK
But when i try to "fastboot boot twrp.img" I get FAILED (remote: command not allowed)
"fastboot oem device-info" gives me the same error too and "fastboot oem unlock" gives me already fastboot unlocked

What do you thing "fastboot boot twrp.img" should do? This command isn't allowed because it does not exist.
If you want to boot into your flashed TWRP recovery, you have to enter "fastboot reboot" and press volume up while booting - the USB cable has to be disconnected.
Instead of "fastboot oem device-info" try "fastboot Gevtvar unlocked".

or use adb when the phone is running.
"adb reboot recovery"
you can't go direct from fastboot to recovery simply by a command

Yeah, the command was wrong, sorry xD
Anyway I thinks it's fixed now and I'm able to boot manually to recovery from phone now!

jejeje i was coming here to tell you about wrong command

I have the same problem with FAILED (remote: command not allowed). When I try to install or flash anything I see the info about FAILED (remote: command not allowed). I have FRP locked and I can't enable OEM developing option (it is inactive). I can't relock bootloader, can't instal TWRP, I have only simply erocevery where I can't wipe - only reboot and shutdown device.
I tried do update via dload, hwota - all with defeat
In ADB and Fastboot I can see my device connected.
Does anyone have any idea?

do you have instaled driver for P10, does computer recognice device like P10 ?

DiMeteo24 said:
I have the same problem with FAILED (remote: command not allowed). When I try to install or flash anything I see the info about FAILED (remote: command not allowed). I have FRP locked and I can't enable OEM developing option (it is inactive). I can't relock bootloader, can't instal TWRP, I have only simply erocevery where I can't wipe - only reboot and shutdown device.
I tried do update via dload, hwota - all with defeat
In ADB and Fastboot I can see my device connected.
Does anyone have any idea?
Click to expand...
Click to collapse
Any news? My p10+ it's in the same case

same problem im already unlock but the twr not install what is propper command

Hey guys, for all of you with "command not allowed" problem, you have to check OEM unlock setting on developer options but if you have a greyed out button, you need to flash again your stock room with a tool like dc-phoenix unlocker and bypass frp lock (on YouTube you will find tons of videos regarding this matter). Also, you can check if your Fastboot is protected (frp locked) on Fastboot screen...

There you go---> https://forum.xda-developers.com/hu...ution-bl-unlockedfrp-locked-fastboot-t3684302
PS READ the post to the END!! don't make mistakes it's really easy and fast. It works!

Hi guys.
I know this thread is pretty old but I'm getting the exact same problem as the OP except on my P20 Pro: I can flash a recovery but not boot one from fastboot.
The biggest difference is that my bootloader is unlocked and I have FRP Unlock, so according to every post I've seen it SHOULD be working.
My fastboot log:
PS C:\adb> fastboot devices
LCL0218415002142 fastboot
PS C:\adb> fastboot boot twrp-3.2.1-0-charlotte.img
downloading 'boot.img'...
OKAY [ 0.187s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.187s

Armand Bernard said:
Hi guys.
I know this thread is pretty old but I'm getting the exact same problem as the OP except on my P20 Pro: I can flash a recovery but not boot one from fastboot.
The biggest difference is that my bootloader is unlocked and I have FRP Unlock, so according to every post I've seen it SHOULD be working.
My fastboot log:
PS C:\adb> fastboot devices
LCL0218415002142 fastboot
PS C:\adb> fastboot boot twrp-3.2.1-0-charlotte.img
downloading 'boot.img'...
OKAY [ 0.187s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.187s
Click to expand...
Click to collapse
Have you try this command fasboot reboot recovery_ramdisk?

I get:
PS C:\adb> fastboot reboot recovery_ramdisk
fastboot: usage: unknown reboot target recovery_ramdisk
with "fastboot boot recovery_ramdisk" I get
error: cannot load 'recovery_ramdisk': No such file or directory

I sorted out my problem from a different angle so I no longer need to boot to TWRP from fastboot. Thanks for your help!

Question
Armand Bernard said:
I sorted out my problem from a different angle so I no longer need to boot to TWRP from fastboot. Thanks for your help!
Click to expand...
Click to collapse
Could you please tell me how did u solve this problem. thx

darkdante13 said:
Could you please tell me how did u solve this problem. thx
Click to expand...
Click to collapse
This was quite some time back so I don't remember all that well, but I think I just used the built in Huawei recovery, erecovery, to restore my whole phone and then I was able to reinstall my custom recovery and boot to it normally. I can't guarantee this as I don't remember the whole context of this. Using erecovery I didn't lose my locally stored files, only my apps and app data. Hope this helps.

"FAILED (remote: unknown command)" trying to unlock bootloader

Hello, I'm trying to follow This guide and This one to unlock the bootloader with no luck.
This is what I get:
Code:
C:\Minimal ADB and Fastboot>fastboot devices
ZY322MF6XP fastboot
C:\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
FAILED (remote: unknown command)
finished. total time: 0.000s
I updated drivers and adb and fastboot with no luck.
Any help?
Edit: I have a Moto G6 Plus in RETLA channel with the march security patch.

I'd double check that Allow OEM Unlock in dev options is actually on

ZeroPoke said:
I'd double check that Allow OEM Unlock in dev options is actually on
Click to expand...
Click to collapse
Tried it with it on and off twice!

Angelelz said:
Tried it with it on and off twice!
Click to expand...
Click to collapse
Same thing happened to me. When you get your unique identifier find an online generator and then paste that into the Motorola website, worked for me.

H0LT3R said:
Same thing happened to me. When you get your unique identifier find an online generator and then paste that into the Motorola website, worked for me.
Click to expand...
Click to collapse
Yeah, can't get the unique identifier though, that particular command is not working for me. Anyone have any idea why?

Hi,
For Working this command "Fastboot oem get_unlock_data"
First you need to remove or delete your phone's SCREEN LOCKS like your fingerprint, face-unlock, pattern or password etc... And keep on NONE option in lock screen. After all above procedure done than, You run that commend "Fastboot oem get_unlock_data". After runing thant command, You will not get "FAILED (remote: unknown command)"
It will work 200%.

PRUTHVIRAJ S VASUDEV said:
It will work 200%.
Click to expand...
Click to collapse
no. it doesnt.

It depends on your fastboot version. Please check "fastboot --version" and post it here.
---------- Post added at 03:49 AM ---------- Previous post was at 03:44 AM ----------
...or try "fastboot oem help". This option will show you whether this command is available.

hi!
i have same problem.
product: Lenovo TB-7504x
fastboot getvar info:
warranty: yes
unlocked: no
secure: yes
kernel: lk
product: WT98997_LTEROW
version-preloader: 0.1.00
version: 0.5
PS: Allow OEM Unlock in developer options is actually on

Also having this issue trying to root my LG G6; I successfully set up adb, fastboot, and started up into bootloader, but it keeps returning the failed/unknown command error when I try to do any further steps. "fastboot devices" shows up correctly but "fastboot oem device-info", device-id, "fastboot flash recovery twrp.img", all keep failing

renforrest-EX said:
Also having this issue trying to root my LG G6; I successfully set up adb, fastboot, and started up into bootloader, but it keeps returning the failed/unknown command error when I try to do any further steps. "fastboot devices" shows up correctly but "fastboot oem device-info", device-id, "fastboot flash recovery twrp.img", all keep failing
Click to expand...
Click to collapse
same

Did you try another USB port? Some users reported that USB 3.0 did not work but 2.0.

I would be willing to bet this is happening on devices that are not allowed to be unlocked. Like those purchased from a phone company.

its been a week since i'm trying on my htc 10, but getting the same error, i tried,
- delete the drivers and re-install
- delete sync manager
- enabled debug & oem unlock
- done reset factory for the phone
- change USB ports and cables
- tried 3 latops
nothing works, sometimes i'll just the error "waiting for any phone" and other times "FAILED (remote: unknown command)"

Angelelz said:
Hello, I'm trying to follow This guide and This one to unlock the bootloader with no luck.
FAILED (remote: unknown command)
finished. total time: 0.000s[/CODE]
I updated drivers and adb and fastboot with no luck.
Try fastboot oem unlock first, then fastboot oem get_unlock_data
Any help?
Edit: I have a Moto G6 Plus in RETLA channel with the march security patch.
Click to expand...
Click to collapse
Try fastboot oem unlock first then fastboot oem get_unlock_data

I'm following a tutorial and obviously got stuck and the very same step as you did. And presumably you are following a tutorial, too.
1. Go to Security Settings and remove device lock (PIN, fingerprint, whatever you are using) and set it to NONE.
2. Go to Developer Settings and Unlock Bootloader. (If you skip step 1., you'll be asked to unlock your device here, but find that the Unlocking failed afterwards. Hence, go to step 1. and remove the lock first.)
3. fastboot oem unlock
Done. (Bootloader is unlocked now. Confirm via boot to fastboot mode (Volume down + Power button))
fastboot oem get_unlock_data is probably removed (deprecated) and maybe you don't even need a key from the manufacturer to unlock anymore.

gelignite said:
maybe you don't even need a key from the manufacturer to unlock anymore.
Click to expand...
Click to collapse
You still need a key to unlock the bootloader for the first time! When it's locked with status "flashing_locked" you don't need a key for it.
Is it a brand new device...?

WoKoschekk said:
You still need a key to unlock the bootloader for the first time! When it's locked with status "flashing_locked" you don't need a key for it.
Is it a brand new device...?
Click to expand...
Click to collapse
If that question refers to my post: I have a Moto E4 (XT1762). Bought it like half a year ago to tinker around with. I started it, ran all updates available and set a device lock (here: PIN).
Today I finally found the time to get started with lineageos and followed the guide at: rootmygalaxy.net (download-and-install-lineage-os-16-on-motorola-moto-e4-android-9-0-pie)
I got stuck at the error the OP had. (This lead me here.)
In my case I got past the error by doing the steps mentioned in my first post, i.e.
1. started the device (normal boot) and got rid of the device lock (PIN in my case), enabled USB debugging, enabled bootloader unlocking
2. powered off the device and started it again in fast boot mode (volume down + power button)
3. On computer / in terminal: fastboot oem unlock (without any key from the manufacturer)
The device showed a confirmation dialog. (Volume up: Yes, Volume down: No)
Code:
[email protected]:~/downloads/lineageos/Android_SDK_platform_tools/platform-tools$ ./fastboot oem unlock
(bootloader) Start unlock flow
OKAY [ 9.657s]
Finished. Total time: 9.667s
Now in fast boot screen I see Device Status: unlocked
I just wanted to share my experiences from today's struggles and maybe it'll help the OP.

gelignite said:
If that question refers to my post: I have a Moto E4 (XT1762). Bought it like half a year ago to tinker around with. I started it, ran all updates available and set a device lock (here: PIN).
Today I finally found the time to get started with lineageos and followed the guide at: rootmygalaxy.net (download-and-install-lineage-os-16-on-motorola-moto-e4-android-9-0-pie)
I got stuck at the error the OP had. (This lead me here.)
In my case I got past the error by doing the steps mentioned in my first post, i.e.
1. started the device (normal boot) and got rid of the device lock (PIN in my case), enabled USB debugging, enabled bootloader unlocking
2. powered off the device and started it again in fast boot mode (volume down + power button)
3. On computer / in terminal: fastboot oem unlock (without any key from the manufacturer)
The device showed a confirmation dialog. (Volume up: Yes, Volume down: No)
Code:
[email protected]:~/downloads/lineageos/Android_SDK_platform_tools/platform-tools$ ./fastboot oem unlock
(bootloader) Start unlock flow
OKAY [ 9.657s]
Finished. Total time: 9.667s
Now in fast boot screen I see Device Status: unlocked
I just wanted to share my experiences from today's struggles and maybe it'll help the OP.
Click to expand...
Click to collapse
Moto E4 is a developer's device without a locked bootloader. I thought you were talking about a Moto G6.

Baronstragen said:
Try fastboot oem unlock first then fastboot oem get_unlock_data
Click to expand...
Click to collapse
fastboot oem unlock worked for me