Database Develop

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.

Oem unlock Blackview BV6000

Oem unlock Blackview BV6000
I go to settings "settings" -> "Developer Option" -> "Oem unlock" -> Enabe
When i type in bootloader -> use fastboot, "fastboot oem unlock"
It shows a menu and ask me to press volume up , This button is desableb
So it mean bootloader is ocked , how can i unlock it?

blu3m3 said:
Oem unlock Blackview BV6000
I go to settings "settings" -> "Developer Option" -> "Oem unlock" -> Enabe
When i type in bootloader -> use fastboot, "fastboot oem unlock"
It shows a menu and ask me to press volume up , This button is desableb
So it mean bootloader is ocked , how can i unlock it?
Click to expand...
Click to collapse
@blu3m3,
when it asks to press volume up, just press it and in a few seconds bootloader will get unlocked
But don't forget to type the command 'fastboot format userdata ' & hot enter after unlocking bootloader.
And one more thing, just don't worry about that OEM unlock option in dev settings, it does nothing

Utkarsh_Tiwari said:
@blu3m3,
when it asks to press volume up, just press it and in a few seconds bootloader will get unlocked
But don't forget to type the command 'fastboot format userdata ' & hot enter after unlocking bootloader.
And one more thing, just don't worry about that OEM unlock option in dev settings, it does nothing
Click to expand...
Click to collapse
I Tried , i pressed it about one minute and nothing.
Can you send me a full list of commands from the beggining?
Thank you.

blu3m3 said:
I Tried , i pressed it about one minute and nothing.
Can you send me a full list of commands from the beggining?
Thank you.
Click to expand...
Click to collapse
After connecting your phone in fastboot mode, type
1. " fastboot oem unlock " and press enter & press vol up button on yr phone
2. " fastboot format userdata " enter.
3. " fastboot reboot " enter
thats it. done

Utkarsh_Tiwari said:
After connecting your phone in fastboot mode, type
1. " fastboot oem unlock " and press enter & press vol up button on yr phone
2. " fastboot format userdata " enter.
3. " fastboot reboot " enter
thats it. done
Click to expand...
Click to collapse
That's what i do too,
I enabled in Developer Options OEM unlocking
I done what you told me , but still not working
I pressed up and waited about 2 minutes pressed.
I think bootloader must be locked something else, but i don't know how.

blu3m3 said:
That's what i do too,
I enabled in Developer Options OEM unlocking
I done what you told me , but still not working
I pressed up and waited about 2 minutes pressed.
I think bootloader must be locked something else, but i don't know how.
Click to expand...
Click to collapse
check if your phone's drivers are installed correctly and whether your phones is recognised in fastboot mode or not.
you can check it by typing "fastboot devices" and enter.
If it shows something like device serial name or anything, then your device is connected in fastboot mode otherwise install correct drivers.
Hope this helps.
Sent from my Sparkle V

Utkarsh_Tiwari said:
check if your phone's drivers are installed correctly and whether your phones is recognised in fastboot mode or not.
you can check it by typing "fastboot devices" and enter.
If it shows something like device serial name or anything, then your device is connected in fastboot mode otherwise install correct drivers.
Hope this helps.
Sent from my Sparkle V
Click to expand...
Click to collapse
Yes it is installed correctly, it shows a number,
same with adb devices, it dsplays a number

blu3m3 said:
Yes it is installed correctly, it shows a number,
same with adb devices, it dsplays a number
Click to expand...
Click to collapse
wait! wait!, if you wanna flash a ROM after unlocking bootloader, then you can do that without unlocking it too. Follow the steps.
1). Download flashable twrp zip by 1cefire and put it in your sdcard and also extract recovery.IMG from it.
2). Put that recovery image into the folder where you have your fastboot and adb files.
3). Reboot to fastboot and type
"fastboot boot recovery.img"
after that phone will temporarily boot into TWRP. Now just flash the flashable zip of TWRP from yr sdcard to permanently install TWRP recovery.
Hurray, now you can flash any ROM without unlocking bootloader.
Press thanks if it helps.

Utkarsh_Tiwari said:
wait! wait!, if you wanna flash a ROM after unlocking bootloader, then you can do that without unlocking it too. Follow the steps.
1). Download flashable twrp zip by 1cefire and put it in your sdcard and also extract recovery.IMG from it.
2). Put that recovery image into the folder where you have your fastboot and adb files.
3). Reboot to fastboot and type
"fastboot boot recovery.img"
after that phone will temporarily boot into TWRP. Now just flash the flashable zip of TWRP from yr sdcard to permanently install TWRP recovery.
Hurray, now you can flash any ROM without unlocking bootloader.
Press thanks if it helps.
Click to expand...
Click to collapse
Where can i find twrp zip by 1cefire ?

When i type fastboot recovery.img
I sais :
downloading 'boot.ing'
OKAY [ 0.477s]
booting...
FAILED <remote: oem unlock is false>
Finished. total time: 0.458s

blu3m3 said:
Where can i find twrp zip by 1cefire ?
Click to expand...
Click to collapse
here is the link https://www.androidfilehost.com/?fid=24562946973632081
enjoy
Hit thanks.

Utkarsh_Tiwari said:
here is the link https://www.androidfilehost.com/?fid=24562946973632081
enjoy
Hit thanks.
Click to expand...
Click to collapse
When i type fastboot recovery.img
I sais :
downloading 'boot.ing'
OKAY [ 0.477s]
booting...
FAILED <remote: oem unlock is false>
Finished. total time: 0.458s

blu3m3 said:
When i type fastboot recovery.img
I sais :
downloading 'boot.ing'
OKAY [ 0.477s]
booting...
FAILED <remote: oem unlock is false>
Finished. total time: 0.458s
Click to expand...
Click to collapse
you have to type "fastboot boot recovery.img" and not "fastboot recovery. img"

Utkarsh_Tiwari said:
you have to type "fastboot boot recovery.img" and not "fastboot recovery. img"
Click to expand...
Click to collapse
Yes i typed "fastboot boot recovery.img" but whe i wrote here on forum i wrote with missing word
I still receive this error (remote : oem unlock is false)

blu3m3 said:
Yes i typed "fastboot boot recovery.img" but whe i wrote here on forum i wrote with missing word
I still receive this error (remote : oem unlock is false)
Click to expand...
Click to collapse
them you should try flashing the same recovery.img with SP FLASH TOOL. Just replace stock recovery with this one and uncheck all other options except recovery while downloading through SPFT.

Utkarsh_Tiwari said:
them you should try flashing the same recovery.img with SP FLASH TOOL. Just replace stock recovery with this one and uncheck all other options except recovery while downloading through SPFT.
Click to expand...
Click to collapse
I've done that, when i press volume up and power it doesn't enter recovery, it loads a black screen

blu3m3 said:
When i type fastboot recovery.img
I sais :
downloading 'boot.ing'
OKAY [ 0.477s]
booting...
FAILED <remote: oem unlock is false>
Finished. total time: 0.458s
Click to expand...
Click to collapse
Bro if u want to unlock your boot loader without this fastboot code method just try All in one toolkit by faiyaz5yaz
http://forum.xda-developers.com/cro...bootloader-t2997696/post58055051#post58055051 try if u want to do nau work related to locking ,unlocking, flashing recovery etc stuffs .

Nobody has anything new to unlock the bootloader ?

Hello friends,
I'm have made a "Flashing guide" to update your Blackview BV6000's ROM to Nougat 7.0.
Please follow the link below and update ROM. You could also find a "TWRP installation + Rooting Guide" for your Blackview BV6000 in the archives.
http://dreamworks75.blogspot.in/2017/08/rom-flashing-guide-blackview-bv6000.html
Happy Flashing !!

+1 on this one.
I'm too stuck on that disabled volume up button, when confirming whether to oem unlock the phone.
I've read in a blog post (can't link yet) that one can specify a 16-digit unlock code for the fastboot oem unlock command, but I have no idea whether it would allow me to confirm unlocking - and also no clue where that code could be obtained from in the first place.
So, any further info?

Nexus 6 soft bricked - OEM Unlocking enabled / Bootloader Locked

I rooted my Nexus 6 in an attempt to install nethunter linux distro by Kali. I was using the Nexus Root Toolkit v2.1.9. The phone will connect to PC and I can get it to load into fastboot with the normal options available but the bootloader is locked. When attempting to use any recovery option the phone boots to the "Google" logo and then flashes the android icon laying down with the red triangle and the words "No command" then shuts off. I have searched numerous threads and articles on the internet I keep getting stuck at the bootloader locked.
Nexus Root Toolkit v2.1.9
Masterlists:
- LatestToolkitFiles.ini 3150
- AndroidDeviceListFull.ini 3150
- AndroidDeviceListFlash.ini 3150
SHAMU-SHAMU: Android 7.1.1 - Build: N6F26U
Live log initiated [2017-08-16]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G22HSLB fastboot
+ Fastboot Device Connected
+ Bootloader Status: Locked.
adb devices
fastboot devices
ZX1G22HSLB fastboot
+ OEM Unlocking Enabled
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G22HSLB fastboot
+ Fastboot Device Connected
+ Bootloader Status: Locked.
+ OEM Unlocking Enabled
fastboot oem unlock
Rebooting your device...

First thing to do is ditch the toolkit. Learn how to use ADB via the command line. Second thing to do is download an OTA image from Google and sideload it. That should restore your device to operating condition, despite the bootloader being locked. All data on the device will be wiped when doing this.

I have used the ADB / Fastboot cmd lines within powershell but each time I try to flash the bootloader I get the
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)

Are you in recovery mode when trying to sideload the OTA? If not, you need to be. The only command needed is "adb sideload [ota]".

As long as Allow OEM unlock is checked in developer options, you can unlock the bootloader via fastboot, with fastboot oem unlock.

@Char_G: I guess I read "OEM Unlocking Enabled" differently, i.e. wrong, when I attempted to help him.

Strephon Alkhalikoi said:
@Char_G: I guess I read "OEM Unlocking Enabled" differently, i.e. wrong, when I attempted to help him.
Click to expand...
Click to collapse
I've always unlocked my bootloader as soon as I got the device so I've never seen that particular text before, I'm assuming it means that he's checked that box but I don't know for sure lol

when running the command in powershell i get
PS C:\Users\n0n3m\Desktop\android-sdk-windows\platform-tools> ./fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.003s
the phone will no longer stay on the android with the red triangle to allow me into the recovery mode option to select sideload with adb

n0n3mulat0ry said:
when running the command in powershell i get
PS C:\Users\n0n3m\Desktop\android-sdk-windows\platform-tools> ./fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.003s
the phone will no longer stay on the android with the red triangle to allow me into the recovery mode option to select sideload with adb
Click to expand...
Click to collapse
Sounds like it flash stock recovery hold power button and press the volume up key that should allow you to select adb sideload in recovery
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:13 PM ---------- Previous post was at 09:11 PM ----------
Jnewell05 said:
Sounds like it flash stock recovery hold power button and press the volume up key that should allow you to select adb sideload in recovery
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
But you saying that it won't stay on screen long enough to get into recovery.. that's strange. I haven't experienced this before
Sent from my Nexus 6 using Tapatalk

Have you fixed your issue?

Huawei P9 stuck In bootloop

what I have done is this:
Rooted phone
Installed TWRP
than I updated (stupid)
Lost root than I wanted to install Custom frimware what didnt work
Factory resetted phone, phone doesnt boot anymore now.
I can only access fastboot but I can not get fastboot to work on pc installed many different drivers just dont work.

lucmaas99 said:
what I have done is this:
Rooted phone
Installed TWRP
than I updated (stupid)
Lost root than I wanted to install Custom frimware what didnt work
Factory resetted phone, phone doesnt boot anymore now.
I can only access fastboot but I can not get fastboot to work on pc installed many different drivers just dont work.
Click to expand...
Click to collapse
Every two or three days people report here they bricked phones by forcing update or Factory reset (or relocking Bootloader) from custom or rooted phones (or by having TWRP) - one must first go back to the original stock firmware he had, before upgrading/resetting/relocking...
And this thread will also not help to somebody else -
since 'somebody' will not read (before bricking the phone) ;(
---
Do you still have TWRP - use HWOTA to flash stock
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
If you have no TWRP but Fastboot is showing Bootloader unlocked, you should be able to flash TWRP.
If Fastboot is showing Bootloader locked but FRP unlocked, you should be able to unlock Bootloader.
But if there is no more TWRP and Fastboot is showing FRP and Bootloader locked - maybe DC Phoenix can help you
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial

I used this command in fastboot: fastboot oem device-info
But I get this error: FAILED (remote: Command not allowed)
On my phone it says: Phone: unlocked and FRP: Lock

lucmaas99 said:
I used this command in fastboot: fastboot oem device-info
But I get this error: FAILED (remote: Command not allowed)
On my phone it says: Phone: unlocked and FRP: Lock
Click to expand...
Click to collapse
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick

zgfg said:
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
Click to expand...
Click to collapse
I cannot get into to recovery but when I let the phone die and than it starts normally,
but everytime it turns off its get back stuck in bootloop I got my oem key when it booted back but now I tried unlocking it agian but it says this:
C:\adb>fastboot oem unlock <code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.024s

lucmaas99 said:
I cannot get into to recovery but when I let the phone die and than it starts normally,
but everytime it turns off its get back stuck in bootloop I got my oem key when it booted back but now I tried unlocking it agian but it says this:
C:\adb>fastboot oem unlock <code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.024s
Click to expand...
Click to collapse
I cannot flash anything because I cannnot enable USB debugging in developers options

zgfg said:
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
Click to expand...
Click to collapse
What can I do I can access phone but cannot unlock bootloader because cannot use remote commands and I can not get into any recovery menu I am out of idea's

lucmaas99 said:
I cannot flash anything because I cannnot enable USB debugging in developers options
Click to expand...
Click to collapse
You can boot to system?
Which (full name) build it shows in About?
Can you enable Developer options - then why cannot you enable USB debugging?!
You must first enable Allow ADB debugging in charge... and only then USB debugging -otherwise USB debugging switches off

zgfg said:
You can boot to system?
Which (full name) build it shows in About?
Can you enable Developer options - then why cannot you enable USB debugging?!
You must first enable Allow ADB debugging in charge... and only then USB debugging -otherwise USB debugging switches off
Click to expand...
Click to collapse
Modelnumber: EVA-L19
Build: NRD90M test-keys
I think I should not supposed to have test-keys doesnt seem correct?

So I got my phone to boot but everytime I want to do something in recovery or something else It wont boot anymore and than I need to make the battery run out of juice. are there anyfix without needing root recovery or fastboot.

ADB wont work because usb debugging wont turn on (tried many things), Fastboot kinda works but gives the error (remote command not allowed)
Cannot get into any Recovery I can boot to OS

"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