Database Info

fastboot flashing unlock = Failed (remote: unknown comand)

Hi,
I recently updated from stock Kit Kat to stock MarshMallow using the factory image mra58n.
Fastboot reports:
Bootloader version: HHZ12K
Baseband version: M8974A-2.0.50.2.27
Secure Boot: enabled
Lock State: unlocked
I noticed that the new fastboot 'flashing' commandline switches (ie fastboot.exe flashing unlock) all respond with:
FAILED (remote: unknown command)
However, the old fastboot 'oem' commands (ie fastboot.exe oem unlock) work. Which is somewhat odd because if I run 'fastboot.exe -h', 'oem' is not listed as a valid option.
Any thoughts why "fastboot flashing get_unlock_ability", etc might not be working with my Nexus 5?
Edit: Fastboot is able to detect the Nexus 5. 'fastboot reboot-bootloader' and 'fastboot devices' both work as expected.
Edit2: Not sure if related, but in Settings > Developer Options, there is no "Allow OEM unlock" option. Is this only visible if the bootloader is locked?
- Scrawl

The right command is fastboot oem unlock. Why are you using fastboot.exe xxx?
I didn't try the new official commands so I can't give you a feedback but did you try to update your SDK/fastboot?

Allow oem unlock option is for the nexus 9, nexus 5x, and nexus 6p. Not sure if the nexus 6 has this option.

audit13 said:
Allow oem unlock option is for the nexus 9, nexus 5x, and nexus 6p. Not sure if the nexus 6 has this option.
Click to expand...
Click to collapse
Have g the same problem.s on my new HTC desire 626..
Sent from my HTCD200LVW using XDA Free mobile app

Hmm, I guess the "allow oem unlock" option is not limited to Nexus devices.

audit13 said:
Hmm, I guess the "allow oem unlock" option is not limited to Nexus devices.
Click to expand...
Click to collapse
Nah,it was added in Android 5.1.1 for most if not all devices.
Sent from my Nexus 6

I looked at my N5 and don't see the option on the latest Marshmallow.

audit13 said:
I looked at my N5 and don't see the option on the latest Marshmallow.
Click to expand...
Click to collapse
Really? That's weird, could be wrong

I didn't see that option in the latest lollipop or marshmallow on a nexus 5.

have the same issue
did you ever get it to work - im tring in my cheep silver line sl1069
alps

ASUS zenpad C 7.0 tablet, no device in fastboot

I've got ASUS ZenPad C 7.0 (z170cg) and I'm using Debian 8.2. adb is working fine, but fastboot does't see the tablet. I want to unlock bootloader, but I am not even sure if it's locked (device in bootloader mode only show running android on the green background and nothing else). 'sudo fastboot devices' doesn't show anything and 'sudo fastboot oem unlock' is giving me only < waiting for device >. To get in bootloader I'm using 'sudo adb reboot-bootloader'. And if it's important, I am using adb and fastboot from debian packages 'android-tools-adb' and 'android-tools-fastboot'

Honor 6x fastboot issue(SOLVED WITH UBUNTU).

Hello, I've searched and searched and can't seem to figure it out but for some reason I can run adb commands within the OS but can't run fastboot commands. Says waiting for device. Yes USB debugging is enabled and oem unlock is to. Running windows 10 with minimal adb and fastboot. The device is running Android 6.0 and the bootloader says ftp locked. Please help I'm trying to unlock the bootloader via my unlock code.

Reinstall the adb drivers

Try a with a windows 7 PC

Sorry for the late response but I had to use Ubuntu to do it must be something with windows 10. All is well now, thanks everyone.

Windows 10 doesn't work well with adb or fastboot

Need help with enabling OEM on Galaxy a5

Hi i was trying to enable oem in Galaxy a5 SM-A500H i tried enabling it in developer settings but it didnt work i tried changing time
i tried it with adb i ran adb reboot bootloader and then it started the bootloader and i tried to run fastboot devices and fastboot oem unlock
first didnt print any devices
and fastboot oem unlock says "waiting for devices" i waited 5 minutes nothing changed
but adb devices worked before booting into bootloader

pasha5 said:
Hi i was trying to enable oem in Galaxy a5 SM-A500H i tried enabling it in developer settings but it didnt work i tried changing time
i tried it with adb i ran adb reboot bootloader and then it started the bootloader and i tried to run fastboot devices and fastboot oem unlock
first didnt print any devices
and fastboot oem unlock says "waiting for devices" i waited 5 minutes nothing changed
but adb devices worked before booting into bootloader
Click to expand...
Click to collapse
Maybe you find something more in the specific forum for the "old" A series on here https://forum.xda-developers.com/f/galaxy-a3-a5-a7-a8-a9-android-development.4857/
Regarding the fastboot commands you are trying to execute, this model doesn't support fastboot, the OEM unlock won't work at all.

Pc can't communicate when in bootloader(tried everything)....

I just purchased a OnePlus Nord N10 5G (BE2026)
Originally it was running OxygenOs 10.x.x.x
Following guides from oneplus website and here on XDA I was able to successfully unlock the bootloader and of course ADB worked fine as well as Fastboot in the bootloader etc...
After unlocking the bootloader I realized that OxygenOs 11.0.2.BE86AA was available via OTA. Which is now what the phone is currently running.
***MAIN ISSUE***
after unlocking the bootloader in order to gain root access via TWRP and Magisk my PC fails to find any devices while the phone is in Fastboot mode... ADB still works just fine but as soon as I run "adb reboot bootloader" or boot to bootloader via buttons the PC will not detect the phone any longer while in the bootloader or Fastboot mode...
I have triple checked that:
SDK USB drivers
ONEPLUS USB DRIVERS
Windows Universal USB drivers
USB Debugging
OEM Unlocking
PC is granted developer access
newest version of ADB & Fastboot
and everything else I can find on this issue searching Google & XDA for the past 3 days
* one issue that I found strange, only when the phone was booted into the bootloader Windows device manager showed Android as an unknown device. Which I could only solve by using Zadig and installing Winusb driver... but still running "fastboot devices" while phone is in bootloader / Fastboot mode still shows no devices....
I've been trying to solve this about 4 days now scouring the internet for any information I could find and nothing seems to work. But everything worked just fine before I unlocked the bootloader / flashed OxygenOs 11 via OTA and now windows to see the phone while in the bootloader....

When phone is got booted into bootloader / fastboot mode then phone can't get seen / accessed by ADB. Point.

jwoegerbauer said:
When phone is got booted into bootloader / fastboot mode then phone can't get seen / accessed by ADB. Point.
Click to expand...
Click to collapse
@jwoegerbauer not entirely sure what you are trying to imply with your message...
If you are trying to point out that ADB doesn't work in bootloader / fastboot mode, I am completely aware of this. And never mentioned otherwise in my original message.
With my phone booted up into Android
And I run "adb fastboot bootloader" the phone will reboot into bootloader mode but my PC still shows waiting for devices... Or if I boot into bootloader / fastboot mode manually and run “fastboot devices" it shows no connected devices. And no fastboot Commands work either... I am not trying to run ADB Commands in fastboot mode.

AFAIK starting with Android 10 the command sequence should be as this
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
...
fastboot reboot
because fastbootd got moved to Android's userspace.