Waiting for any device what to do. Android - tips and tricks. What to do if ADB does not see your tablet or smartphone among the devices connected to the computer. Solution waiting for device in Fastboot
Experienced owners of Android devices quite often use the ADB and Fastboot programs included in the Android SDK to unlock the bootloader of their tablets and smartphones, install custom firmware, obtain root rights and much, much more.
However, one “fine” day you may find that after you have connected your Android device to the PC and typed the usual “adb devices” command in the command line window, the list of devices connected to the computer that this program should display is empty. What to do in such cases to correct the situation?
If this happens to you, then first of all you need to check the following:
1. Check if it is enabled in your tablet's settings
2. Check that the USB cable you are using to connect to your computer is working and connected correctly
3. Check if you have the Android SDK installed and updated to the latest version to date
4. Try switching the connection mode of your tablet or smartphone from a media device (MTP) to a camera (PTP) or vice versa.
You may ask - why do all this if the device worked fine before? There can be many reasons for such a 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 original cable that came with it, but with a longer one purchased later, in order to make it easier to use the device is charging, or – the USB drivers of your device are not installed correctly.
Speaking of drivers. If you checked all of the above, but it did not help you and the ADB program still does not see your device, try removing it from the system and reinstalling it again.
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 right-click on the device and select the “Delete” option in the menu that opens.
Disconnect your tablet or smartphone from your computer, confirm the removal by clicking on the “OK” button and after completing the device removal process, reconnect it and wait until Windows installs it again. After this, your tablet or smartphone should appear in the list of devices connected to the computer in the ADB program.
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 really a mistake, if we literally translate this phrase - waiting for the device to connect. That is, when you try to do something in adb or fastboot and you get the message waiting for device in the command line, this means that your Android smartphone or tablet is not visible!
Message waiting for device - adb or fastboot does not see the connected Android device!
To continue reading this article and to understand what we are talking about, 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 solutions for waiting for device in adb and waiting for device in fastboot.
Solution waiting for device in ADB
link page. Certain devices require a special ADB driver.
2. USB Debugging is not enabled! If you do not have USB debugging enabled, then working in ADB is not possible!
It is also worth noting that with Android 4.2 and higher, you must confirm trust in the connected computer on the device!
3. ADB only works when your Android is turned 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 too early to talk about 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, under any circumstances, use USB hubs; working with ADB becomes like luck - you'll be lucky or unlucky.
8. Try connecting Android to a different USB port.
9. If you have the Windows 8.1 operating system installed, you need to make some minor changes
Solution waiting for device in Fastboot
Not all Androids have Fastboot mode (99% of all Samsung and Lenovo), therefore 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, do you have the driver installed? You can download the driver on this page, find out how to install it on this link. Certain devices require a special Fatboot driver (for example Sony).
Have you installed the driver? Restart your computer!
2. Make sure that the device is in bootloader mode, otherwise fastboot will not 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 too early to talk about large-scale implementation. Fastboot works only with USB 2.0 ports!
6. Do not use USB hubs! Since Fastboot mode is necessary for flashing Android firmware, it’s good if Fastboot simply does not see your device, but if there is any failure in the USB hub, then 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 installed, then you need to make small changes, after which everything should work.
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 is not really an error, if we literally translate this phrase - waiting for the device to connect. That is, when you try to do 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 does not see the connected Android device!
To make it clear what this article is about and to understand what we are talking about, 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”.
Solution waiting for device in ADB
1. The first thing you should pay attention to is whether you have the driver installed?
You can download the driver here page how to install find out on this link . If unsigned driver, then Windows must be restarted by disabling the scan. Certain devices require a special ADB driver.
Have you installed the driver? Restart your computer!
2. Make sure that the device is in bootloader mode, otherwise fastboot will not see your Android!
3. Use an original and undamaged microUSB cable! Everything should be clear here, if the cable is damaged, hence the problem of visibility, 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 too early to talk about large-scale implementation. Fastboot working 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 luck - you'll be lucky or unlucky.
7. Try connecting Android to a different USB port.
9. Open the command line as “administrator”.
If you once had a similar problem “waiting for device” and solved it in your own way, not from the methods listed, 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!
Waiting for device - Error in ADB or Fastboot (Android). 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” is not really an error, if we literally translate this phrase - waiting for the device to connect.
That is, when you try to do something in adb or fastboot and you get the message waiting for device in the command line, this means that your Android smartphone or tablet is not visible!
Video: Fastboot Mode Waiting for Device
Message waiting for device - adb or fastboot does not see the connected Android device! To continue reading this article and to understand what we are talking about, it is advisable to read the following articles:
Video: Micromax YU Yureka USB Drivers — Fix Waiting for device error in Fastboot Mode Windows 7/8/8.1
Although almost all the reasons for the message are solved in the same way, for convenience, the article will be divided into solutions for waiting for device in adb and waiting for device in fastboot.
Solution waiting for device in ADB
- The first thing you should pay attention to is, do you have the driver installed? You can download the driver on this page, find out how to install it on this link. Certain devices require a special ADB driver. Have you installed the driver? Restart your computer!
- USB Debugging is not enabled! If you do not have USB debugging enabled, then working in ADB is not possible! It is also worth noting that with Android 4.2 and higher, you must confirm trust in the connected computer on the device!
3. ADB only works when your Android is turned 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 too early to talk about 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, under any circumstances, use USB hubs; working with ADB becomes like luck - you'll be lucky or unlucky. 8. Try connecting Android to a different USB port.
Video: Waiting for device Problem-Solution (ADB/FASTBOOT)
9. If you have the Windows 8.1 operating system installed, then you need to make small changes, after which everything should work.
Solution waiting for device in Fastboot
Not all Androids have Fastboot mode (99% of all Samsung and Lenovo), therefore these models will not work in this mode and will always give the error waiting for device!
- The first thing you should pay attention to is, do you have the driver installed? You can download the driver on this page, find out how to install it on this link. Certain devices require a special Fatboot driver (for example Sony). Have you installed the driver? Restart your computer!
- Make sure that the device is in bootloader mode, otherwise fastboot will not see your Android!
- 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!
- Do not use a damaged USB port on your computer! The reasons are the same as with the cable.
- Use only USB 2.0 port! Despite the fact that the USB 3.0 standard has already existed for several years, it is still too early to talk about large-scale implementation. Fastboot works only with USB 2.0 ports!
- Do not use USB hubs! Since Fastboot mode is necessary for flashing Android firmware, it’s good if Fastboot simply does not see your device, but if there is any failure in the USB hub, then it will cost you a lot.
- Try connecting Android to a different USB port.
Video: Fastboot / ADB / Device Drivers - Installation - Tutorial
If you have the Windows 8.1 operating system installed, then you need to make small changes, after which everything should work.
