Fastboot sees the phone and adb does not. What to do if the computer does not see the phone through the USB port. We quickly identify the culprit

Quite often, a common problem in Android is the waiting for device error when working with ADB or Fastboot, in this article we will learn how to fix it!

What is this waiting for device?

This error is not quite an error, if you literally translate this phrase - waiting for the device to connect. That is, when you try to execute something in ADB or FASTBOT and you get the message waiting for device in the command line, it means that your Android smartphone or tablet is not visible!

Message - adb or fastboot cannot see the connected Android device!

To make it clear what this article is about and to understand what it is about, it is advisable to read the following articles:

  • OtlauSB connection

Although almost all the reasons for the message are solved in the same way, for convenience, the article will be divided into the solution "waiting for device in adb" and "waiting for device in fastboot".

Waiting for device solution in ADB

1. The first thing to look out for is whether you have a driver installed?

You can download the driver on this pagehow to install find out on this link... If the driver is unsigned, then Windows must be restarted by disabling verification. For certain devices, a special ADB driver is required.

Have you installed the driver? Reboot your computer!

2. Make sure your device is in bootloader mode, otherwise fastboot won't see your Android!

3. Use an original and not damaged microUSB cable! Everything should be clear here, if the cable is damaged, hence the visibility problem, perhaps you can transfer or receive files from this cable, but you won't be able to work with Fastboot! Also, do not use a damaged USB port on your computer!

4.Use only USB 2.0 port! Despite the fact that the USB 3.0 standard has already existed for several years, it is still very early to speak before a large-scale implementation. Fastboot operation with USB 3.0, although possible, is still not desirable!

5. Do not use USB hubs! Never, under any circumstances, use USB hubs, working with Fastbot becomes like a fortune - lucky or unlucky.

7. Try connecting Android to a different USB port.

9. Open a command prompt as "administrator".

If you once had a similar "waiting for device" problem and solved it in your own way, not from the listed methods, then do not hesitate to write in the comments!

That's all! Read more articles and instructions in the section. Stay with the site, it will be even more interesting further!

ADB, or Android Debug Bridge, is a PC console application that lets you control your Android device right from your computer. It looks like this: first, the ADB toolkit and drivers for Android are installed on the computer, then the mobile device is connected to the PC via a USB cable in debug mode, and, finally, after starting ADB in the console (command line), special commands are executed that initiate certain actions with a gadget. Detailed information about the principle of operation of the debugging tool itself is presented on the official website of the developer, so we will not dwell on this, but go straight to the capabilities of ADB and how to install it on a computer.

What does ADB allow?

First, let's point out why ADB is needed at all. With it you can:

  • Reboot the device in different modes;
  • Share files / folders with your phone;
  • Install / uninstall applications;
  • Install custom firmware (including TWRP Recovery);
  • To produce;
  • Run all sorts of scripts.

The ADB tool is usually installed in conjunction with the Fastboot console application.

Installing ADB and Fastboot from Android SDK

This method involves using the official Android Studio application development and testing tool. Go to https://developer.android.com/studio/index.html and find the title "Get just the command line tools". Below we download the SDK tools archive for Windows (we agree to the terms of use before downloading).

Unpack the archive to disk C. In our case, the files were extracted to the folder sdk-tools-windows-3859397.

We go to the directory, and then go to the directory tools / bin... Here we are interested in the file sdkmanagerwhich will help you install ADB and Fastboot on your computer.

Now you need to open the folder with sdkmanager, for which you should run the command in the console cd C: \\ sdk-tools-windows-3859397 \\ tools \\ binwhere C: \\ sdk-tools-windows-3859397 \\ tools \\ bin - path to the sdkmanager file.

If you unpacked the Android SDK not to drive C, but to some other place, then the full address can be found using the top line of Explorer (right-click on the destination folder and click "Copy address").

So we went to tools \\ bin and now we need to execute the command sdkmanager "platform-tools"which will install the Platform-tools package containing the ADB and Fastboot files.

During installation, read the license agreement and press Y to complete the operation.

If everything went well, a directory will appear in the Android SDK root folder. platform-tools with the necessary files adb.exe and fastboot.exe.

Minimal ADB and Fastboot

The second way is even simpler. On the developer forum Xda Developers you can download the package Minimal ADB and Fastboot with all the necessary files. To do this, go to the page https://forum.xda-developers.com/showthread.php?t\u003d2317790 and, by clicking on the link, download the installation exe-file.

We launch it and follow the instructions.

We installed Minimal ADB and Fastboot to the root of the same C drive.

Basically, that's all. It remains to check the existence of files.

Checking ADB and Fastboot work

After installing applications using any of the above methods, you need to make sure that the utilities work correctly. To do this, through the command line, go to the folder with adb and fastboot files (command cd C: \\ sdk-tools-windows-3859397 \\ platform-tools or cd C: \\ Minimal ADB and Fastboot), and then execute the command adb help... It should display the version of the Android Debug Bridge installed and a list of ADB commands. If you see something like the one shown in the screenshot below, then everything is working correctly.

Now you should connect a mobile device to the PC and check if the ADB application sees it. We connect the phone (or tablet) to the computer using a USB cable, set the MTP connection mode (file exchange) in the settings and go to the section Settings - For Developers.

If there is no such item in the settings, then go to the "About phone" page and click on the line with the build number seven times.

Developer Mode will be activated and the "For Developers" section will become available. We go into it and enable the "Debugging via USB" option.

After all these manipulations with the gadget in the Windows command line, enter the command adb devices... It will display information about the connected device in approximately the same format as in the screenshot.

Thus, we tested ADB and Fastboot and made sure that the Android Debug Bridge is functioning normally, which means that you can now control your phone through your computer.

If you cannot establish communication with the device, then you need to check the presence and correctness of the installation of Android drivers. To do this, with the debug mode turned on, go to the "Device Manager" and see if there are exclamation marks in the "USB Devices" branch, the "ADB Interface" item (may be called a little differently).

If any problems are found, we try to reinstall the drivers. You can download them on the phone manufacturer's website or at https://adb.clockworkmod.com/.

We hope this article was helpful to you.

A fairly common problem in Android is the waiting for device error when working with ADB or Fastboot, in this article we will learn how to fix it!

What is this waiting for device?

This error waiting for device not quite an error, if you literally translate this phrase - waiting for the device to connect. That is, when you try to execute something in adb or fastboot and you get the message waiting for device in the command line, it means that your Android smartphone or tablet is not visible!

Waiting for device message - adb or fastboot cannot see the connected Android device!

To continue reading this article and to understand what is at stake, it is advisable to read the following articles:

Although almost all the reasons for the message are solved in the same way for convenience, the article will be divided into the solution waiting for device in adb and waiting for device in fastboot.

Waiting for device solution in ADB

page link. For certain devices, a special ADB driver is required.

2. USB debugging not enabled! If you do not have USB debugging enabled, then work in ADB is not possible!

It is also worth noting that with Android 4.2 and higher, the trust to the connected computer must be confirmed on the device!

3. ADB only works when your Android is on!

4. Use an original and undamaged microUSB cable! Everything should be clear here, if the cable is damaged, hence the visibility problem, perhaps you can transfer or receive files from this cable, but ADB will no longer work!

5. Do not use a damaged USB port on your computer! The reasons are the same as with the cable.

6. Use only USB 2.0 port! Despite the fact that the USB 3.0 standard has already existed for several years, it is still very early to speak before a large-scale implementation. Although ADB is possible if the device is connected to a USB 3.0 port, it is still not desirable!

7. Do not use USB hubs! Never and under no circumstances use USB hubs, working with ADB becomes like a fortune - lucky or unlucky.

8. Try connecting Android to a different USB port.

9. If you have the operating system Windows 8.1, then you need to make small edits

Waiting for device solution in Fastboot

Not all Androids have Fastboot mode (99% of all Samsung and Lenovo), so these models will not work in this mode and will always give the error waiting for device!

1. The first thing you should pay attention to is what, and do you have a driver installed? You can download the driver on this page, find out how to install it on this link. Certain devices require a dedicated Fatboot driver (eg Sony).

Have you installed the driver? Reboot your computer!

2. Make sure the device is in bootloader mode otherwise fastboot won't see your Android!

3. Use an original and undamaged microUSB cable! Everything should be clear here, if the cable is damaged, hence the visibility problem, perhaps you can transfer or receive files from this cable, but ADB will no longer work!

4. Do not use a damaged USB port on your computer! The reasons are the same as with the cable.

5. Use only USB 2.0 port! Despite the fact that the USB 3.0 standard has already existed for several years, it is still very early to speak before a large-scale implementation. Fastboot work only with USB 2.0 ports!

6. Do not use USB hubs! Since Fastboot mode is necessary for Android flashing, it's good if Fastboot just doesn't see your device, but if any failure in the USB hub passes, it will cost you a lot.

7. Try connecting Android to a different USB port.

8. If you have the Windows 8.1 operating system, then you need to make small edits, after which everything should work.

Everyone faces this problem at least once, but everyone: you connect a smartphone or tablet to a computer via a USB cable, but nothing happens except charging. The computer does not see the phone or identifies it as an unknown device. The situation is common, but ambiguous, and there are quite a few reasons why it occurs. Today we will figure out what causes such problems and how to deal with them.

The situation when the PC does not recognize the mobile device connected to it is caused by software and hardware failures:

  • The lack of a device driver in the PC operating system.
  • The driver does not match the device model.
  • USB driver missing or malfunctioning.
  • Connection with a cable that is not suitable for data transmission or is damaged.
  • Defective USB socket (both on the computer and on the phone), socket group, or USB controller on the PC.
  • Something malfunctioning in the computer hardware, blocking by static electricity.
  • Error in the system settings of the phone.
  • Blocking access to the phone by security programs running on a PC (including when the gadget is virally infected).
  • The application that synchronizes the phone and the PC (if using) has crashed.

In case of software problems, the computer, as a rule, does not display the contents of the phone's memory, but the device charges normally when connected to it. If the problem has arisen due to a physical malfunction, charging most often also does not work, but there are exceptions when only the data lines do not work.

An analysis of the previous situation - what happened before the problem arose - helps to outline the range of possible causes. For example:

  • You reinstalled the operating system on the computer or removed some of the drivers (the reason is the lack of the required driver).
  • The phone (tablet) was no longer detected after flashing, cleaning from viruses, removing applications, optimizing and other manipulations with the OS (failure of the operating system of the mobile device).
  • The device was subjected to mechanical stress (damaged USB socket) or was repaired (after replacing parts, a driver of a different version is needed or the malfunction has not been completely eliminated).
  • You are using a USB cable that you have never connected your phone to a computer with (the cable is for charging only or is broken), etc.

We quickly identify the culprit

Tracking the cause-and-effect relationship greatly facilitates the localization of the problem, but in about half of the cases, nothing concrete precedes it. If this is the case for you, the following steps will help you determine where the failure occurred - in the mobile device, PC or USB cable.

  • Wiggle the cable in the area of \u200b\u200bthe connectors (kinks are most common in these places) and watch if the phone (tablet) is detected in the explorer or the computer device manager. Alternatively, connect the devices with another cable that is known to be working and suitable for data transmission.
  • Connect your phone to another computer, as well as another mobile device to this PC. If the phone is not found anywhere, the problem is definitely in it. The same is the case with a computer.
  • If the reason is presumably in the computer, check the phone in all USB sockets, perhaps the problem is in one or more of them (for example, only in the front group).

If you conclude that the cable is the source of the problem, simply replace it. What to do in other cases, read on.

The culprit of the failure is the telephone. What to do?

If the diagnostics clearly indicate a problem with your mobile device, follow these steps in order. Check after each step to see if the problem is resolved. If not, move on to the next one.

  • Reboot your device.
  • Connect your phone to your computer. After connecting, slide down the shutter of the quick settings menu and make sure that “only charging”, as well as “camera” or “media device” are not marked in the “Connect as” list. Select the "USB storage" option.

  • Open the Android system settings (in older versions - "Options"). Go to the "Wireless networks" section. Turn on modem mode. Or vice versa, if it's on, turn it off. In some editions of Android, this parameter controls not only the modem, but also the connection of the gadget to the PC as a drive.

  • Experiment with putting the device into USB debugging mode. Open the "System" and "For Developers" section in the settings. Uncheck or check the box next to USB Debugging.

  • Disconnect the phone from the computer, turn off and remove the battery (of course, if it is removable) from it (phone). After 5 minutes, replace the battery, turn on the device and try to connect again.
  • Uninstall applications that crashed after installing. If the connection doesn't work for a particular sync app, clear its cache. If it does not help, reinstall (both on a mobile device and on a PC) or try using an analogue.
  • Scan your device with antivirus software.
  • Reset the operating system of the device to factory settings.

The culprit of the failure is the computer. What to do?

  • Shut down the OS, turn off the PC from the outlet (or press the key on the power supply) and hold down the power button for 15-20 seconds. This will discharge capacities and discharge static electricity that may be blocking detection of the connected device.
  • If the phone is not recognized by only one group of USB ports, open the lid of the system unit and make sure that they are connected securely. By the way, normal charging of a mobile device through the port does not mean that the second device is working properly.
  • Load the operating system. Open Device Manager and check if portable devices are in the list of equipment, and among them is your phone. If it is present, but marked with a black arrow in a circle (disabled), right-click on the line and select the "Enable device" command from the menu.

  • If there are unknown devices in the hardware list (marked with an exclamation mark in a yellow triangle), one of them may be the phone. To make sure it is him, disconnect the mobile device from USB. If the unknown device disappears from the list, then it is. And the reason for the failure is the lack of the necessary driver in the system. How to reinstall and where to download the driver to your phone, we will tell you a little below.
  • The problem with recognizing connected devices may also be due to a boot failure, damaged or missing USB drivers. In this case, exclamation marks will be in the USB Controllers section.
  • Reinstalling the drivers didn't help? Scan your computer's disks with an antivirus and then temporarily disable the security programs. By the way, the latter can block access to a mobile device as a carrier if it contains suspicious or clearly malicious software. So check your phone for viruses too.

  • Uninstall the programs after which the problem was installed, or perform a system restore to the checkpoint created on the day when the problem did not exist.
  • If, in addition to the phone, the computer does not recognize other devices connected via USB - a mouse, keyboard, printer, flash drives, etc. (whether they are charged or not is not indicative), the source of the failure may be any faulty component of the system unit or something then from the periphery. It is possible to determine the culprit at home by alternately disconnecting or replacing the equipment with a known good one.

How to reinstall the mobile device driver and USB on a Windows computer

iPhone

  • Connect iPhone to PC.
  • Open the folder% CommonProgramW6432% \\ Apple \\ Mobile Device Support \\ Drivers (in order not to type the command manually, copy it from here, paste it into the address bar of any folder and click the go button). It contains 2 files (out of four) with the .inf extension - usbaapl.inf and usbaapl64.inf.

  • Open the context menu of each of these files and execute the "Install" command.
  • After installation, restart your computer.

Android

Android smartphones and tablets, such as Samsung, Xiaomi, Lenovo, Meizu, HTC, etc., as a rule, do not create separate folders to store their drivers, and they are often not found on the official websites to just download and reinstall. Therefore, for a start, you should entrust the reinstallation of the drivers already present in the system to Windows itself.

How to do it:

  • Open the context menu of the problem device in the device manager. Select the Update Driver option.

  • In the next window, first select the automatic search for updates. If Windows does not find anything suitable, check the second item - installing and searching for drivers manually.

  • Then click "Select from the list available on the computer." A new window will display all mobile device drivers that are already installed on the PC.

  • To narrow your search, under "Select a driver for this device" check the box "Compatible only". Check the one that best suits your request (if there is more than one item in the list) and click "Next" to proceed to the installation.

Restart your computer for the driver to work correctly.

If reinstalling the driver that was already in the system did not help, you will have to look for something else in the open spaces of the network (with the risk of downloading a virus instead of the desired one), so download them only from reliable and trusted sites, like w3bsit3-dns.com, and check with an antivirus before installing.

Drivers of the most common models of mobile gadgets are also collected in the "USB Drivers for Android" application, which is available for free download on Google Play.

USB drivers for Windows are usually found without problems on the websites of laptop or desktop motherboard manufacturers. Sometimes they are included in the chipset driver.

If the phone is not recognized in firmware mode

The fact that the computer and the phone do not see each other in fastboot mode is indicated by the message "Waiting for device" that appears in the firmware program. Most often, this error occurs due to the absence of a mobile device driver in the system, so the first thing to do is do what is written above - reinstall the driver or download and install it again.

If it doesn't help:

  • Make sure you follow the instructions for using the firmware installer exactly and that it is running as an administrator.
  • Check if USB debugging is enabled on the smartphone (if not, enable it), and the device itself is in bootloader mode. If this mode is blocked, look on the network for instructions on unlocking the bootloader specifically for your device model.
  • Connect the phone with the shortest and known good cable to the rear USB socket, without using any adapters or hubs.
  • Your phone may not support USB 3 (blue jack), so only connect to USB 2.0 (black jack).
  • Install any released Windows updates on your computer.

If the problem persists even after doing this, try flashing the phone on a different PC. And better - with a different version of the operating system.

When the problem is a breakdown of the physical interface

It is advisable not to use faulty physical interfaces, especially on a mobile gadget (do not use current in order to avoid aggravating the breakdown), even if the phone or tablet retains the ability to charge through them. Content transfer can be organized either wirelessly (Wi-Fi, bluetooth), or through cloud services that are available on both devices. In particular, iTunes and iCloud for Apple technology, Google Drive, Yandex Drive, Dropbox, Microsoft OneDrive and many others - for everyone.

Cloud services are convenient for transferring photos, videos, music, documents and other types of files. To synchronize contacts on Android and PC, the capabilities of Gmail are enough. And in order to control the phone directly from the computer, you can put on them an application like MyPhoneExplorer (consists of 2 parts - for the phone and for the PC), which supports both wired and wireless connection of devices without requiring the installation of drivers. Very comfortably.

In short, there is always a way out and often much simpler than it seems at first glance.

Experienced owners of Android devices often use the ADB and Fastboot programs included in the Android SDK to unlock the bootloader for their tablets and smartphones, install custom firmware, get root rights, and much, much more.

However, one "fine" day, you may find that after you connected your Android device to the PC and typed the familiar command "adb devices" in the command prompt window, the list of devices connected to the computer that this program should display is empty. What to do in such cases to rectify the situation?

If this happened to you, then first of all you need to check the following:

1. Believe it is enabled in your tablet settings

2. Check that the USB cable you are using to connect to the computer is working properly and is connected correctly

3. Check if you have Android SDK installed and updated to the most recent version

4. Try switching the connection mode of your tablet or smartphone from media device (MTP) to camera (PTP) or vice versa.

You may ask - why do all this, if the device worked fine before? There can be many reasons for this situation. For example, you updated the operating system on your PC and forgot to install the Android SDK, or you haven’t updated the SDK for a long time, or you connected your tablet or smartphone not with the proprietary cable that came with it, but with a longer one purchased later in order to make it convenient to use device is charging, or - your device's USB drivers are not installed correctly.

Speaking of drivers. If you have checked all of the above, but it did not help you and the ADB program still does not see your device, try uninstalling it from the system and reinstalling it.

To do this, on a computer with a tablet or smartphone connected to it, open the device manager and find the device with "Composite ADB Interface" in the name. For example: "Android Composite ADB Interface" or "Google NexusADB Interface"

Then click on the device with the right mouse button and select the "Delete" option in the menu that opens

Disconnect the tablet or smartphone from the computer, confirm the deletion by clicking on the "OK" button and after completing the process of removing the device, reconnect it and wait for Windows to reinstall it. After that, your tablet or smartphone should appear in the list of devices connected to the computer in the ADB program.

© 2020 Mobile and Computer Gadgets