A fairly very common problem in Android is the error waiting for device 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 on the command line, this means that your Android smartphone or the 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 original and undamaged cable 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 port 2.0! 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 installed operating system Windows 8.1, then 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. Working in Fastboot only with USB ports 2.0!
6. Do not use USB hubs! Since Fastboot mode is necessary for Android firmware, it’s good if Fastboot simply doesn’t 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 an operating system installed Windows system 8.1, then you need to make some minor edits, after which everything should work.
- Tutorial
And here an unpleasant surprise awaited me - either the native driver turned out to be crooked, or Windows, or the wire... in general, the driver stopped working, the Windows Device Manager reported that the device was fully operational, but upon request adb devices I received an empty list in the console and, naturally, I was unable to test the application on the tablet.
I wrote a request to TeXeT support, they even answered me with a link to the driver itself, which, as I was already convinced, did not work. I started looking for an answer on the Internet and found a bunch of different assemblies of this driver and manuals, but still none of them started up properly, and even the native driver from the SDK did not work at all, which made me despondent... but not despair.
Here I decided to try my hand at writing drivers using the good old method of scientific poking and opened the driver inf file. What gave me hope was the understanding that the software part of the adb interface on the tablet side should be identical for all devices, and USB worked anyway. And so, after several unsuccessful attempts at manually editing the inf file, I found a recipe for treating the inf file seasoning so that it would install and, most importantly, work.
So let's get started.
Step 1. Download the driver. If you haven't done this already, open Android SDK Manager, find the Extras section, check the box next to Google USB Driver and click Install Packages. It's simple. Wait for it to load.
Step 2. Find the driver and make a copy of it in a separate folder. Go to the %android-sdk%\extras\google\ folder and see the treasured usb_driver folder there. Copy it somewhere, and we will carry out further manipulations there. In principle, you can edit the “original”, but I preferred to keep the original intact just in case.
Step 3. Edit the inf file. In the folder, open the file android_winusb.inf and look for lines like this:
;Google Nexus One %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01 %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11 %CompositeAdbInterface% = USB_Install, USB\V ID_18D1&PID_4E12&MI_01
Make a copy of these lines and replace Google Nexus One on %your_device_name% for identification in the future and... open the Windows Device Manager. We are looking for our device there ( Android, Android Composite ADB Interface or something like that). Open the device properties, the “Details” tab, select the “Equipment ID” item in the list and see this picture.
We copy the line that is most similar to the one shown in the figure (It is, in theory, just a little shorter), and paste it into our inf file.
;TEXET TM-7025 %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0003 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0003&MI_01 %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0003 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0003&MI_01
In %SingleAdbInterface% we delete the end of the line; as you can see, in %CompositeAdbInterface% we insert the whole line. There’s probably no need to repeat everything twice, but I already have everything and I’m too lazy to experiment :)
We save (be careful - in some cases you need to run notepad with administrator rights, because in user mode you will not be allowed to overwrite the inf file).
Step 4. Driver installation. Now that everything is prepared, go back to the device manager and remove all previously installed adb drivers (if any). We update the list of devices and see our device without drivers. We open its properties and select “update drivers”, select the installation from the folder, specify the folder with the corrected inf and start the installation - our driver is instantly found, but during installation it may swear about incompatibility with the question “should I continue, nasalneka?” Let's continue. That's it, the driver is installed.
Step 5. Final. To be precise, unplug the USB port, wait until everything is detected, open the console (Win+R, enter cmd) and write adb devices. If everything went well, we see the treasured list item, indicating that adb now sees our device. 
From now on, you can safely launch eclipse and build programs, enjoying convenient automatic assembly, installation and the ability to debug directly on your device.
If adb command doesn't work for you at all. Computer -> Properties -> Environment Variables. We are looking for the Path variable and at the end we add(in no case do we overwrite it) at the end there is a semicolon, and after that the address of the folder where adb lives (usually %android-sdk%\platform-tools\). After a reboot it should work.
Sometimes adb does not start automatically when the system starts. Start manually.
What was it?
It's actually simple. For some reason (Winda is a must-have / progers have crooked hands / the Google inf-file was written only for native Google devices / the Higgs bosons have ruined everything on your computer) Windows does not want to use the Google driver for non-Google devices that are not recorded in the inf-file. Apparently, everything there is tied to these ID equipment. But the software on the vast majority of Android devices is identical in terms of the debugger connector to the PC, so the driver should communicate normally with any Android device. Our task is to deceive Windows and force it to accept the device as a “driver-compatible” device, which we did by adding its ID to the driver inf file.
I hope this manual will help someone get their own Chinese or other device for which they forgot to make a normal one when assembling the system adb driver, or for those who are bothered to download the official driver from the device manufacturer (this can be so annoying that it’s faster to do everything described above - I did this with the driver for the LG E510 phone).
P.S. I did not conduct mass testing this method, so I can’t guarantee that it will work 100% in all cases. But it worked for me on Windows 7, and then on Windows 8. I had to edit the file separately for each time, but I don’t think that’s such a problem.
Here we will figure out how to install it correctly adb. If DDMS does not see adb devices in Eclipse ( if our device does not see in DDMS in eclipse). My texet 9750hd device (Android tablet) cannot be seen.
I couldn't install drivers for the 9750HD from the website. And adb didn’t see it, but only showed “9750hd” with exclamation point in Device Manager.
You can also try installing drivers via Super One Click by going to advanced -> check driver. If nothing works then continue.
It constantly showed only List of attach devices and that's it, without a list, showing that adb devices There is not. No matter how much I tried to follow other sites. Although the dispatcher showed that adb was installed, it still did not see the device in adb: 
Download “google usb driver” via “Android SDK manager” in the extras category (check the box and click install packages): 
After downloading, open our folder with installed drivers:
%android_sdk%\sdk\extras\google\usb_driver
Open and edit the file “android_winusb.inf”, depending on the architecture, let’s say you have x86 (add to required block), let's add our device, here's what it was:
;Google Nexus One
Now we will add our device, copy the desired line from device manager: 
Now let's copy ;Google Nexus One and replace it in CompositeAdbInterface USB\VID_18D1&PID_4E12&MI_01 and without last parameter MI_01 in SingleAdbInterface:
;Google Nexus One
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
; texet 9750hd
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
Now let's edit one more file C:\Users\%user%\.android\. Let's add our VID to it, which we copied above with the prefix 0x**** (16-digit), and save:
Now we update our driver by pointing to our driver folder: 
Click install from disk, click browse, and select the directory with our file android_winusb.inf:
When updating, you may be asked whether to install it, but install it of course. After this, the system can see, and possibly our DDMS. In my case, this was also not enough, now let’s replace it adb.exe:
\%android_sdk%\sdk\platform-tools\ adb.exe.
We download a normally working file and replace it in our folder, after which it is directly in the folder ( platform-tools) and launch.
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:
- Otladka via USB
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 the driver is unsigned, then Windows must be restarted by disabling verification. 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 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 too early to talk about 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 luck - you'll be 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 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!
November 7, 2012 at 02:56 pmManual ADB driver installation
- Android development
- Tutorial
And here an unpleasant surprise awaited me - either the native driver turned out to be crooked, or Windows, or the wire... in general, the driver stopped working, the Windows Device Manager reported that the device was fully operational, but upon request adb devices I received an empty list in the console and, naturally, I was unable to test the application on the tablet.
I wrote a request to TeXeT support, they even answered me with a link to the driver itself, which, as I was already convinced, did not work. I started looking for an answer on the Internet and found a bunch of different assemblies of this driver and manuals, but still none of them started up properly, and even the native driver from the SDK did not work at all, which made me despondent... but not despair.
Here I decided to try my hand at writing drivers using the good old method of scientific poking and opened the driver inf file. What gave me hope was the understanding that the software part of the adb interface on the tablet side should be identical for all devices, and USB worked anyway. And so, after several unsuccessful attempts at manually editing the inf file, I found a recipe for treating the inf file seasoning so that it would install and, most importantly, work.
So let's get started.
Step 1. Download the driver. If you haven't already done so, open Android SDK Manager, find the Extras section, check the Google USB Driver box, and click Install Packages. It's simple. Wait for it to load.
Step 2. Find the driver and make a copy of it in a separate folder. Go to the %android-sdk%\extras\google\ folder and see the treasured usb_driver folder there. Copy it somewhere, and we will carry out further manipulations there. In principle, you can edit the “original”, but I preferred to keep the original intact just in case.
Step 3. Edit the inf file. In the folder, open the file android_winusb.inf and look for lines like this:
;Google Nexus One %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01 %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11 %CompositeAdbInterface% = USB_Insta ll, USB\VID_18D1&PID_4E12&MI_01
Make a copy of these lines and replace Google Nexus One on %your_device_name% for identification in the future and... open the Windows Device Manager. We are looking for our device there ( Android, Android Composite ADB Interface or something like that). Open the device properties, the “Details” tab, select the “Equipment ID” item in the list and see this picture.
We copy the line that is most similar to the one shown in the figure (It is, in theory, just a little shorter), and paste it into our inf file.
;TEXET TM-7025 %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0003 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0003&MI_01 %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0003 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0003&MI_01
In %SingleAdbInterface% we delete the end of the line; as you can see, in %CompositeAdbInterface% we insert the whole line. There’s probably no need to repeat everything twice, but I already have everything and I’m too lazy to experiment :)
We save (be careful - in some cases you need to run notepad with administrator rights, because in user mode you will not be allowed to overwrite the inf file).
Step 4. Driver installation. Now that everything is prepared, go back to the device manager and remove all previously installed adb drivers (if any). We update the list of devices and see our device without drivers. We open its properties and select “update drivers”, select the installation from the folder, specify the folder with the corrected inf and start the installation - our driver is instantly found, but during installation it may swear about incompatibility with the question “should I continue, nasalneka?” Let's continue. That's it, the driver is installed.
Step 5. Final. To be precise, unplug the USB port, wait until everything is detected, open the console (Win+R, enter cmd) and write adb devices. If everything went well, we see the treasured list item, indicating that adb now sees our device.
From now on, you can safely launch eclipse and build programs, enjoying convenient automatic assembly, installation and the ability to debug directly on your device.
If the adb command does not work for you at all. Computer -> Properties -> Environment Variables. We are looking for the Path variable and at the end we add(in no case do we overwrite it) at the end there is a semicolon, and after that the address of the folder where adb lives (usually %android-sdk%\platform-tools\). After a reboot it should work.
Sometimes adb does not start automatically when the system starts. Start manually.
What was it?
It's actually simple. For some reason (Winda is a must-have / progers have crooked hands / the Google inf-file was written only for native Google devices / the Higgs bosons have ruined everything on your computer) Windows does not want to use the Google driver for non-Google devices that are not recorded in the inf-file. Apparently, everything there is tied to these ID equipment. But the software on the vast majority of Android devices is identical in terms of the debugger connector to the PC, so the driver should communicate normally with any Android device. Our task is to deceive Windows and force it to accept the device as a “driver-compatible” device, which we did by adding its ID to the driver inf file.
I hope this manual will help someone get their own Chinese or other device for which they forgot to make a normal adb driver when assembling the system, or for those who are bothered to download the official driver from the device manufacturer (this can be so annoying that it’s faster to do everything described above - This happened to me with the driver for the LG E510 phone).
P.S. I have not conducted mass testing of this method, so I cannot guarantee that it will work 100% in all cases. But it worked for me on Windows 7, and then on Windows 8. I had to edit the file separately for each time, but I don’t think that’s such a problem.
Loading...
