Fastboot doesn’t see device but ADB does (windows 10)

I am attempting the unlock the bootloader on my Google Pixel 2 XL. I know this problem seems to be very common, but I have yet been unable to find a solution for my particular case after searching through just about all the relevant cases online. I have installed the latest Google USB drivers as well as the ADB/Fastboot platform tools. When I run adb devices I get one listed, which is my phone. I am able to then run adb reboot bootloader to get to the fastboot screen. This is where my problem starts.

Not only does the device not appear under fastboot (when I run fastboot devices), but I don’t think my PC is recognizing that an Android phone is connected. Many guides at this point say to go to Device Manager, and find the Android device under ‘Other Devices’ with a yellow indicator showing that it isn’t working, and then point Windows towards a working driver. However, my Device Manager looks like this:

Device Manager

As far as I can tell, when I plug in the phone when in fastboot mode, it appears as Intel(R) USB 3.1 extensible Host Controller - 1.10 (Microsoft) and as USB Root Hub (USB 3.0)

I guess my question is at this point is this a hardware issue? I can do everything with my Pixel normally, like exchange files and USB debugging.

How to factory reset a locked phone when you cant access fastboot or usb debug mode

I have a Hyundai Orbit android phone. The situation is as follows:

  1. The phone has a pin which we don’t know
  2. The phone was never signed into any google or other accounts
  3. USB debugging is not turned on
  4. We have tried starting the phone while holding all combinations of buttons and it always just boots normally, never into fastboot/recovery mode. We have been able to boot with “Safe mode” in the bottom right hand corner of the screen

Is there any way to do a factory reset under these conditions?

Fastboot Device not Detecting my Device

I’m following this tutorial about how to unlock bootloader on Moto. My device is a Moto G5, and my computer has windows 10.

On the command line, I can type

adb devices 

and it returns my device. I then do

adb reboot bootloader 

and it turns my phone into bootloader mode. But when I do

fastboot devices 

it returns a blank line. According to this source (the second answer), I need to update some the “Unknown ‘Android’ device”. However, I don’t have anything like that. The closest I have is Other devices->Fastboot potter S. Do I update this driver? If so, how? If I choose “Search automatically for updated driver software,” it doesn’t find anything. If I choose “Browse my computer for driver software” and then “Let me pick from a list of available drivers on my computer”, I have to “Select [my] device’s type from the list below.” but I don’t know which one I’m supposed to choose.

How do I fix this problem with fastboot devices? What drivers am I supposed to update? How do I fix them?

If this question is better suited on another stackexchange such as superusers on account of it’s being more about windows than android, let me know. I tried asking it there first, but the “android” tag said that the question would be off topic.

Troubleshoot fastboot error ‘remote: ‘ command not defined


Device: iMX 7ULP evaluation kit

Platform-tools: r28.0.3

Image: O8.1.0_1.4.0_ANDROID_TOOL_7ULP_GA (ARM 32 Android 8.1)

I used the image provided by nxp website on the device. Then I tried unlocking it.

According to a tutorial, I used adb to bring the system in bootloader via

> ./adb reboot bootloader 

The device goes to the splash screen and stop there (Not sure if that’s how it should be). adb does not recognize the device anymore and fastboot fails on any command as fowllows

> ./fastboot.exe oem unlock                                 FAILED (remote: ' unlock device failed.') fastboot: error: Command failed 
> ./fastboot oem device-info                                 FAILED (remote: ' command not defined') fastboot: error: Command failed 
> ./fastboot flashing unlock                                 FAILED (remote: ' unlock device failed.') fastboot: error: Command failed 

How can I troubleshoot that and unlock the device?

Unlocking oem via fastboot says command failed

I planned to unlock oem via fastboot.

I downloaded the latest adroid platform-tools (r28.0.3) and Run the following commands on a device while its dev option is enabled.

./adb.exe reboot bootloader ./fastboot.exe devices  # fine 

But the last command fails

./fastboot.exe oem unlock                                                    FAILED (remote: ' unlock device failed.') fastboot: error: Command failed 

What is the possible reason? And how to fix this problem.

Nokia 3 – Can’t do fastboot commands for installing TWRP

I am trying to install Lineage OS on my Nokia 3 TA 1020 and at first I can’t get into fastboot via ADB (i get a -1 error), although I do see the devices with adb devices.

I enter fastboot manually via recovery mode and then when I type fastboot devices on command prompt it shows nothing. Also, when i try to flash TWRP anyways, I get a “waiting for device” message and nothing happens on both screens.

Anybody got any idea? I got debugging enabled and OEM unlocked from dev options on android.

Thx

Nokia 3 – Can’t do fastboot commands for installing TWRP

I am trying to install Lineage OS on my Nokia 3 TA 1020 and at first I can’t get into fastboot via ADB (i get a -1 error), although I do see the devices with adb devices.

I enter fastboot manually via recovery mode and then when I type fastboot devices on command prompt it shows nothing. Also, when i try to flash TWRP anyways, I get a “waiting for device” message and nothing happens on both screens.

Anybody got any idea? I got debugging enabled and OEM unlocked from dev options on android.

Thx