Fastboot Device Not Found

[Justina Ky]

TLDRIn addition to the previous responses. There might be a problem with the version of the fastboot command. Try to download the newest one via Android SDK Manager instead of default one available in the OS repository.

There is one more thing you can do to fix this issue. I had the similar problem when trying to flash Nexus Player. All the adb commands we working fine while in normal boot mode. However, after switching to fastboot mode I wasn't able to execute fastboot commands. My device was not visible in the output of the fastboot devices command. I've set the right rules in /etc/udev/rules.d/11-android.rules file. The lsusb command showed that the device has been pluged in.

The problem is that once the device is in fastboot mode, it shows up as a different device: "Google, Inc Android 1.0." So doing "lsusb" in the VM showed no device connected, and obviously "fastboot devices" returned nothing until I added the "second" device as a filter for the VM as well.

If you got nothing when inputted fastboot devices, it meaned you devices fail to enter fastboot model. Make sure that you enter fastboot model via press these three button simultaneously, power key, volume key(both '+' and '-').Then you can see you devices via fastboot devices and continue to flash your devices.

Adding udev rules halfway through added confusion for me. Later I found out I never was properly reloading the udev rules. Restarting the udev.service does not work. I had to:udevadm control --reloadthenudevadm trigger as found here:

The set of udev rules that I copied from a recent .deb package had me covered; however on a side note I found that my device has different vendor ID's when mounted normally versus when it is in fastboot.

Then I could: adb reboot bootloader but fastboot devices would not return my device and I never resolved that problem (which was the second issue); however this post helped me (actually the original poster has covered this already in their question):

I found that fastboot could still communicate to the device and I could issue commands but I would always have to specify the device via the -i option. For example: fastboot -i 0xVENDOR_ID getvar WHATEVER

If anyone's experiencing the same problem, it's possible that you're trying to use fastboot with a Samsung phone. After trying everything on Stack Exchange, I learnt that many Samsung phones don't support fastboot for flashing firmware, and instead use Samsung's own system called Odin.

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.

I've read a lot of articles about this problem but I can't resolve it. I decided to install my developer application on phone using wifi. To do this I need to do some things with my phone. The first step is to unlock bootloader. I stack on step 8, fastboot oem get_identifier_token shows info . adb sees my device but fastboot can't. An idea?

Problem solved. At the end I saw that drivers for android were not installed. I installed drivers from this site -developers.com/showthread.php?t=2126036 and device is visible by fastboot. One thing I don't understand is why adb saw device and fastboot not.

Scenario: the device is visible with adb devices but is not detected with fastboot devices and the other suggestions here don't work; you still end up with "waiting for device" on Windows and aren't able to choose a driver to install via rahul pandey's answer using the Google USB driver.

I didn't realize it right away, but there are different ADB drivers and Fastboot drivers. I had installed the google usb drivers with the SDK extras and ADB worked great but I got the "waiting for device" trying to flash in fastboot mode.

I went to device manager from the control panel and saw the "Android 1.0" device with the yellow icon showing it wasn't working right. I had to update the driver and pick from the list of existing drivers which had a fastboot entry.

I had the same problem described by 'pepuch' on my HTC Desire S. I tried different drivers on relatively new computers running Windows 8 and Windows 10. In the end I found a link suggesting that I should try the (same) procedure on an older (desktop) computer which I did and the computer managed to detect my Desire S in fastboot USB mode and I managed to read the ID token. The link which steered me to the solution follows: -one-rooting-roms-hacks/345350-htc-one-pc-doesn-t-recognize-bootloader.html

If no drivers work on Windows 10 or 8.1/8 and your goal is to just use fastboot to flash boot.img (Probably because you have S-ON), there's the way of the Linux:Get a USB stick ready and use Live Linux Creator and install a Live Linux like Ubuntu or Lubuntu onto the stick. Boot to the Live version (maybe you can use VirtualBox VM on Windows, not sure). Open Terminal with Ctrl+Alt+T.Type (without comments with // ofc):

There are a log of Fastboot blogs out there but what they don't always mention is, Samsung devices have no fastboot mode. So if yours is a Samsung device, don't waste time on any of the drivers and settings, because it will not work on Samsung. You can use adb but not fastboot.

For me, I couldn't even see my Android device in Windows 10 Device Manager until I went into Settings/General/Developer options and set Select USB Configuration to MTP (Media Transfer Protocol) instead of the default Charging Only, and also found a different USB cable that wasn't a charging-only one. Then, as @sushanthkille indicated above, I still had to install an updated driver, but the way he describes via Device Manager didn't work. For my LG G4, I had to go to -drivers.html (found via googling for windows 10 LG G4 drivers) download the Windows driver, and install it manually. After all that, my G4 finally showed up in Windows 10.

I believe the needed update was a driver update for Android Bootloader Interface from Google, Inc. Windows updated several things at once so I can't verify that is what specifically solved the problem for me.

go to the device manager, You will see Other devices. There you will see the Android option. Right-click on it and press on update driver, then click on Brouse my computer for driver S/W. then Let me pick from the list and continue with All devices and next. Then browse again and select the file from the folder you have downloaded and click on install. and restart

That is, although it was detected by adb (adb devices), when i instructed it to reboot in fastboot (adb reboot bootloader), it did not recognize the device straight away. Reconnecting allowed it to realize the change in state, and now it was properly recognized (fastboot devices) and it would follow any instruction properly.

I did some hacky stuff with my xz2 compact to resolve this error. I read out all variables with fastboot getvar all and took the serialnimber and set it manually in the flash.sh script. Then i commented out the check for the number of devices and then i commented out the hashcheck and it flashed

wyliecon Can you check fastboot --version on a Mac?

I'm asking because on Arch I had the platform tools version 34 which were seriously broken (fastboot devices for instance showed me the correct serial on anything connected, but the string there was from my Focusrite Scarlett audio interface), and I think I've seen the same message there.

On Debian where I still had fastboot version 33.0.3-8952118 everything worked nicely, but as of now it's changed to "at least 34.0.4" on -fastboot

I recommend trying every possible combination of cables and usb ports you can (C to C, A to C in each port). I had the same problem and the only thing that would get the browser to recognize the device was specifically using an A to C cable in a usb 2.0 port. All other configurations failed. I don't know why this happens but I have seen others solve it this way too (which prompted me to try it in the first place).

I tried to install Universal ADB Driver a described in this page -us/articles/9425348234513-Connect-to-a-computer , I tried to install Google USB Driver from Tlcharger le pilote USB Google Android Studio Android Developers but Windows device manager do not found any suited driver in the zip archive.

If the FP is not recognized in Fastboot:

It can be the cable or USB port, but most of the time it is a fastboot driver problem (on Windows). To update the driver: connect the FP in fastboot mode to the PC, go to Windows Updates, check for updates manually, go to Optional Updates and Drivers and install everything regarding Google/Bootloader (e.g. Kedacom/LeMobile).

After checking your test one by one I realized the problem was not in the phone but the fastboot in subdirectory of the installer files. After granting executable permissons to the scripts in the bin-linux-x86 subdirectory the script worked.

I try to stop/kill/terminate the first fastboot process from task manager, but it does not work. Also, when I shut down, it says something like waiting for session 2 to stop. Only way to stop it is to disconnect device USB.

My device is Sony Xperia XZ2 Compact Dual. I have bootloader already unlocked using Windows (because fastboot does not work on Linux). I would like to use fastboot on Linux without having to boot into Windows everytime...

I think I have to correct this (from the input of the earlier attempt in a German topic). What you did successfully is allowing to unlock the bootloader by entering the unlock code in the developer option on the stock ROM. That is not yet the actual unlocking.

edit:

The easy installer wasnt working because the device had some issues with adb while running on android. But with the now really unlocked bootloader and working fastboot i flashed /e/OS. It is running now smoothly. Thanks again for your help.

3a8082e126