Hi,
I encountered problem while unlocking bootloader . After i press enter in the end of the instructions to unlock bootloader, i see a message : (bootloader) Check 'Enable OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.008s.
I followed the official instructions of unlocking bootloader in motorola site . Got the unlock code, and everything went fine until this point .
Any guesses ?
KabalLV said:
Hi,
I encountered problem while unlocking bootloader . After i press enter in the end of the instructions to unlock bootloader, i see a message : (bootloader) Check 'Enable OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.008s.
I followed the official instructions of unlocking bootloader in motorola site . Got the unlock code, and everything went fine until this point .
Any guesses ?
Click to expand...
Click to collapse
Which model/variant do you have?
Did you update Android?
Did you go to Settings, About Phone, Tapped Build number 7 times, to enable Developer Options?
Do you have a "OEM unlocking" option under Developer Options? Enable USB Debugging...
Boot into Bootloader Mode:
fastboot oem unlock thecodeyougot
didnt have OEM Unlocking enabled . Thanks !
check the unlock in fastboot
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
I'm trying to unlock the bootloader. I got fastboot and adb to respond correctly. Here is what happens when I try:
Code:
C:\WINDOWS\system32>fastboot -i 0x0fce oem unlock 0x0FF21ECC85757B85
...
FAILED (remote: Command not allowed)
finished. total time: 0.068s
Any advice? I checked and my bootloader can be unlocked.
Aside question:
For some reason 'adb reboot fastboot' simply reboots the phone but 'adb reboot bootloader' boots into fastboot (so that fastboot devices responds correctly)
LuminousOne said:
I'm trying to unlock the bootloader. Any advice?
Click to expand...
Click to collapse
Developer options, OEM unlock - enable.
If it's greyed out then you may not be able to unlock.
Some phones sold though service providers have unlock disabled, no workround.
Didgesteve said:
Developer options, OEM unlock - enable.
If it's greyed out then you may not be able to unlock.
Some phones sold though service providers have unlock disabled, no workround.
Click to expand...
Click to collapse
My phone had the same problem showing the "OEM unlock" option greyed out.
Activating WiFi and checking for "system updates" fixed it for me, and I successfully unlocked the phone.
Hello everyone,
So after messing around a bit too much with my phone, I may have finally lost him.
I was having problems updating it, so decided to try and restore it to stock, since not even factory resetting was solving the problem.
Long story short, I now have a "flashing_locked" on the bootloader menu, so if I try to flash a new one I get something like "(bootloader) check 'allow oem unlock' in developer options", but as I said, I can't get into the system. Is it possible to do this via the bootloader?
Am I doomed here? Will probably try taking it to Motorola and see if they don't mind the bootloader unlocked...
Thank you for any help
EDIT: After going through Lenovo Smart Assistant, I'm now stuck on a "Your device has loaded a differente operating system" loop. RIP I guess.
in the bootloader execute the command "fastboot oem unlock" once a message appears informing that it has lost the data and execute again the same command "fastboot oem unlock"
I hope it helps
Same thing
Code:
fastboot oem unlock
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.001s]
Finished. Total time: 0.002s
Hi, I have problem with unlock bootloader in my moto G7 power because my firmware is broke I have Unlock Code from Motorola site when use command fastboot OEM unlock #code receives a message (bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer but I can't enable developer options because my firmware not work, I can only enter fastboot mode. I tried to run developer option from ADB but I have empty list devices even though I have installed drivers Android ADB Interface. I tried to install stock firmware but I need to unlock bootloader first. Does someone have an idea for this problem??