Develop Reference

ADB stopping at <waiting for devices>

I was trying to install some custom recovery and ROM on to my phone when I got to this situation.
(I have my windows update turned off)
ADB or fastboot shows
<waiting for devices>
I tried and saw few solutions.
I'm writing a detailed solution to this.
this was how I solved it.
if you have more suggestions you can answer below.

the only reason for this is that your PC is not recognizing Phone.which is a driver problem.
You have to understand a few things before starting with the solution.
you may know this too.
when you are in your recovery adb gets into something like recovery mode(just framing some terms myself)
in bootloader, it takes fastload mode.
each of this mode needs different drivers other than what the driver you use with adb when your phone is running on OS.
so what you have to do is.
if you are trying to get into recovery mode or fastload mode.
open device manager(settings>devices>(more options)Device manager).
now boot the phone into the required mode using manual or adb method.
the device manager reloads and a new driver will be shown. either in Android or pointing device or others folder.
select the driver and update online.(always preferred).
if you don't find an online driver you have to select manual update here.
select browse my computer.
select let me pick.
select browse.
at last, you have to select the usb-driver provided by the google.
in
sdk>extras>google>usb-driver
it will show the updatable driver.select and press next to install.
press ok now it should work correctly.

Happened to MACOS Mojave 10.14.6 while trying to install twrp-3.3.1-2-enchilada.img.
Solved it by running:
adb reboot-bootloader
Then, when the phone boot into bootloader,
fastboot boot twrp-3.3.1-2-enchilada.img
worked like a charm

Run following command to get your device into FastBoot mode (from adb-driver folder if using Windows System)
adb reboot-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 https://www.lg.com/us/lgeai/Drivers/pages/mobile-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.

For me it was not turning on usb debugging.
(settings -> developer options(you should activate this if you don't see this option) -> usb debugging.)

I had to update Windows 10 to resolve this issue.
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.

Usually it's the drivers' issue on Windows!
Just install the appropriate OEM driver from here:
https://developer.android.com/studio/run/oem-usb#Drivers

I've just spent a lot of time with the same problem, and it turns out to be because I have a Samsung phone.
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.
There's another post with more info here: https://android.stackexchange.com/a/187573/111755.

Easy way
download the Google USB Driver from the official website (https://developer.android.com/studio/run/win-usb)
Turn off your device and connect with your PC or laptop with a USB plugging
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

Android Studio - No USB devices detected

I tried to play Android Studio 2.0 with my mobile without success, what I did are:
In my mobile, Apps/gear icon/Settings/SYSTEM/{} Developer options/ Android debugging/, enable the Android Debug Bridge(adb) interface (set tick).
After plug in my mobile to my PC with a USB cable, I found A0001 in my Computer folder. Within A0001, I can see the files in my mobile.
In my PC, run Android Studio/bin/studio.exe, "Select Deployment Target" window shows with message "No USB devices or running emulators detected"
I have tried two different USB drivers but got no lucky.
Perhaps I should tell Android Studio where is my USB driver? But, how?
Can you help?

I had the same problem too and I managed to resolve it this way.
First, enable debugger mode in your android device.
Go to Device Manager from Start Menu and try to find ADB Interface with an error symbol on it. This generally happens because windows sometimes fail to load all the mobile device drives.
Next, Go to http://adbdriver.com/downloads/ and download the driver installer, unzip and run it.
Now go to Android Studio and you should find that everything is working fine.
Chill....

same here... but I hope you can avoid this problem the same way I Did.
There is an "universal ADB Driver for all Android Devices".
Yep... sounds like magic.
Just follow this link.
https://devs-lab.com/usb-adb-drivers-for-all-android-devices.html
Fun fact there is no "Step 5" in that article so I'll give you.
you have to enable "USB Depuration" from "Developer Options" connect your cellphone to computer as a "MTP storage" , after windows detected your cellphone as a "Portable Device" Execute ADBDriverInstaller.exe (that downloaded from devs-lab)
check the device list and your cellphone will say "Driver incorrectly", select your cellphone and press install.
Step 6: Once the process is completed, you’ll see something like the image that appears there (in the link).
I hope that somebody else work this

Go to Run > Edit Configurations...
Under Deployment Target Options select Show Device Chooser
Dialog from the drop-down-list
See picture for reference

After struggling with this problem for a while, I found that there are certain cables that can only charge your phone, and even though they seem to be working, they do not allow your phone to be used as a "Media Device" and therefore Android Studio does not detect it.

Go to
Tools | Android | Enable ADB Integration
Make sure it's enabled. When I upgraded to 2.X it was for some reason disabled for me and it took me hours to find it.

I just cannot beleive why it is so difficult! let me try again and please check my steps again:
I installed Android Studio 2.0, then run Computer/OS(C:)/....../Android Studio/bin/studio.exe.
The Android Studio window appeared in my working area Computer/OS2(J:)/Users/MyAccount/Desktop/.
I connected my mobile with my computer, Cpmputer/A0001/ appeared, from it, I can see the files in my mobile.
I clicked the run icon in the Android Studio window, a "Select Deployment Target" window apeared with message "No USB devices or running emulators detected".
(I got two USB ports and tried both but got the same result.)

Finally found the solution : )
1. Install device’s required driver. (for me it was motorola device
manager)
2. Download Google Usb Driver from SDK Manager
3. Open your phone's setting->developer options and turn on USB debugging.
4. connect your device to computer
5. Go to Device Manager from Start Menu and try to find if there is ADB Interface with an error symbol on it.
5.1. If yes, then right click on the ADB interface->Update driver
software->Browse my computer for driver software-> Let me pick from
a list of device drivers on my computer->Select Motorola ADB interface
5.2. Now one confirmation will pop up in your mobile, accept it
5.3. Now you should see no error mark beside the ADB interface in your
device manager

There are 3 steps to set up your phone for debugging:
1) Change your phone to developer's mode by going to Settings, About Phone, Software Info, Android Version - tap at least 7 times on the Build Number text. You will get a message saying you are now a Developer.
2) Enable USB Debugging in Settings - Developer Options. Make sure you are not connected to your USB port to see the USB Debugging option enabled, otherwise it will be disabled.
After you plug in your USB, swipe at the top of your screen, you will see USB Debugging on.
3) Make sure USB connection is set to Photo Transfer (or MTP - Transfer photos and videos). After you plug in your USB, swipe at the top of your screen, and you will see Tap to change USB options on the menu. Tap it, and select Photo Transfer option.

Perhaps your mobile manufacturer does not provide the proper driver.
Go to Device MAnager and look for: Android Composite ADB Interface. If it's there, the driver is properly installed. If not... You and I are on the same "wagon"...
I tell you: Acer? Never again.

USB debugging somehow got turned off under developer options on my Samsung. Turned it back on and it worked, but only by clicking on "debug app" instead of on "run app".

With me, when connecting the mobile to the pc, three options appeared on my mobile.
Charge this phone
Transfer Files
Transfer Images
I thought I should select "Transfer Files", but it dd not work
But it only when works I choose "Charge this phone"

Few ways to resolve this problem.
Case 1: Install PdaNet+ in your system. (worked for me).
Case 2: Enable the USB debugging option in your mobile. Setting > developer > Check "USB Debugging".
Case 3: Change from MTP to PTP.(sometimes vise versa works).

Question is Your development sdk no mobile version android sdk Platform.
For example, my android phone system is 6.0, i need download sdk Platform 6.0.

First, try to revoke the usb sessions in the developer options, then try downloading an oem usb driver
If then doesn’t help you can try opening the device manager on windows, right click on your phone, select uninstall. This worked for me if I had the same issue.

I couldn't find my android phone or any USB device I connect to my windows laptop on the hidden icons. Well, my mouse and phone could charge but I can't seem to see my phone in the File Explorer option.
I prefer running Apps using my phone rather than emulator in Android Studio and yet I couldn't see my phone when I connect using the USB.
This helped me solve all my problems after several hours of searching for solution.
Download Universal ADB Drivers - One size fits all Windows Drivers for Android Debug Bridge
Please use this link: https://adb.clockworkmod.com/
I hope this works for you like magic!
I can see all the devices I connect using the USB cable and my mouse receiver.

LG G3 device not recognized by Eclipse on Windows

I recently bought LG G3 and I have enabled debugging mode but Eclipse is still not recognizing it, back when I used the Galaxy S3 for development I had to install Samsung Kies. The G3 drivers are installed and I can see it in My Computer, do I need something like the Kies but for the LG? If so can someone please post a link for that?

See update below
I found the answer that worked for me.
When you plug in the phone, bring down the status shade, pick the USB item ("USB connected") then, from there, pick "Internet connection" -- I chose Ethernet, but I'm not sure the choice matters on the dialog that pops up..
This enables USB debugging to become active; leaving it on Charging, MTP, or PTP does not work.
Once you do this, you can follow #Siddharth's steps to setting the ADB drivers, if needed. (You may need to use the actual LG drivers and not the Google drivers, but once I got this far, it was just like any other phone.)
Caveat
For me, even after going through this once, I still get the "installer" first and then have got go in and choose the "Internet connection" again. But, at least it works.
Update 10 Dec 2014
A recent firmware update has, indeed, removed the "Internet connection" as an option. Instead, PTP now works. I still get the "Connected as an installer" notification every time I plug in the phone and have to click on the notification then click on "Camera (PTP)" -- or wait about a minute. It's slightly better than what It was.
Also note: When this change occurred I had to install the drivers again for the phone, since it comes up as a different type of device when "Camera (PTP)" is chosen than when I used the "Internet connection" option.

For me, this has solved the problem: simply go to LG's website, http://www.lg.com/us/support/software-manuals, select the model (I have selected 'D850') and go to Software Updates tab where you can download the driver. I have installed it and then Eclipse recognized my device. I'm working on Windows 8.1, by the way.
yakobom

After a lot of searching and trying all solutions still I couldn't connect my LG G3 to eclipse on mac. Finally I find this solution, it works for me hope for you works too:
Install LG USB driver for mac
Go and enable developer mode in your G3 (Setting->About phone (in General Tab)--> Software information --> Tap 8 times on Build Number) then you will see the message which says the Developer option is enabled
In this step you expect that after connecting your mobile via USB cable, the Eclipse detect it
But for me it didn't happen
in this step you need to go (Setting--> Developer Options--> and turn off this option from above green (on/off) switch then again switch on this option from same place (If you don't do this step the "USB Debugging" mode will stay fray and you can not enable it)
In Developer Options menu scroll down until find the "USB Debugging" then tic it and enable it.
almost finished , you should back and configure running mode for your application and see the G3 in your connected usb devices

Try this solution :
Right click on My Computer --> Properties --> Device Manager
Right Click on your device --> Update driver software
Click on "Browse my computer for driver software"
Give path of your android sdk like "D:\Android_Sdk\sdk\extras\google\usb_driver" and tick "Include subfolders"
Click
Now repeat the steps till "Browse my computer for driver software".
Then click on "Let me pick form list of device drivers on my computer". Click on the first option and click next and then click yes. Drivers will be installed for your device.
Hope this helps.

Change the USB mode to PTP and you will get the RSA prompt.
Within the prompt, select allow it > ok and you are done.
This worked for me when I had the same problem on a Mac computer.

To contribute to possible solutions for this fix: I am using an LG G3 on a Mac.
In my case, ADB saw it as a device when I checked, and the Mac showed the device information in the System Information window, yet Eclipse did not see it. I also did not get the RSA confirmation pop-up when I connected the device through USB.
To fix, with my G3 connected, I selected the USB PC Connection (either from the navigation bar or through the settings) and changed it to be Send Images (PTP). Once this was on, I was given the RSA pop up and Eclipse recognized the phone in the Run Configurations window.

If you have this problem on Ubuntu; here is what I did to get it working:
Switch to PTP from MTP on the phone (this assumes you're connected via USB)
Disconnect the USB cable
Go to settings -> developer options and select revoke usb authorizations then ok
Make sure USB Debugging is checked
Reconnect the USB cable and your phone will say its connected as an installer; wait a minute or three and debugging mode should appear on the status bar (on the phone)
Open Eclipse and go to DDMS
Select "reset adb" in the dropdown if your phone isn't appearing yet

Working on Windows 7. All of the solutions from other sites didn't help (i.e. restarting adb and switching between MTP, PTP, Charing). In the end, I found this article (http://www.technobuzz.net/install-lg-g3-lg-drivers-windows-mac-usb-adb/), which contains links for the necessary drivers for the lg g3 (and some others I think). This did the trick and made the RSA key fingerprint dialog appear finally. After confirming, adb and eclipse recognize my device perfectly!

I had this buggy error with my LG Optimus L3 phone connecting to Win7/8 machines!
Cause: Device Driver was missing as it seemed at the end when I fixed it!
How to Fix:
Search through web (using Google) "LG < Your_Phone_Model Number > Drivers Download".(Ex.:- Go to About phone in your settings list > Model Number, for me it's LG-E400f)
Mostly the first few links are related to the required Device Driver download page.(Ex.:- for me I got the following link and for each device driver LG or most of the other vendors/manufactures have that kind of a Manuals and Drivers Page) Visit that page mentiioning about software update and drivers downloads.
Scroll down to the section of "Manuals and Software Update" and doing just the Step 1 was enough for me, which is "Install the USB DRIVERS "
Download it(for Mac or Windows) > Install It > Check Your Eclipse ADT > and it should be visible under Devices tab by now
Cheers!!!
Hope this helps to someone else to clearly get to the solution!

it seems that Eclipse shows the offline mode for lg G3 and some newer devices
and there is no way no use these devices for ADB debugging
there is a way
I am using windows 10
1- download this 11 MB file < http://dl2.uncox.com/android/upload/platform-tools-v22.zip>
2- then go to the directory that you installed the SDK
3- extract the zip file in to the platform-tools folder , override all files(click yes to all) be sure that Eclipse doesn't running
4- open Eclipse and select your android device that stands in devices tab at the right-top corner of your screen and then you can see the arrow near the screen- capture icon and you will find the reset-ADB. click on it ,after that your phone will ask you to allow android debugging for your device click on it
5- congratulations .now you can see that your device shown online
i hope this will help .sorry for my english

I also had a great deal of trouble when attempting to debug android applications on my shiny new LG G3. What ended up working for me was first installing the default google drivers onto the G3 and then following the process detailed by #lilbyrdie.
The process of installing the google usb drivers is very nicely gone through here.
However, with the most recently pushed android update to the G3 there are no longer the options for internet connection or charge only; but they seem to have fixed this defect forcing you to make this odd choice to enable debugging. The only options remaining are MTP and PTP, but if you pull down the notification drawer, choose the 'USB connected' notification (assuming the device is connected to your computer via USB of course) and from there click on 'Media sync (MTP)' even if it is already selected then debugging should be enabled.

Android can't update on the fly the developer mode. So, after turning on developer mode (and given you have the latest driver) switch the green button(under settings->general->developer options) to off and then back on. Then turn debug mode on (after that windows recognizes a new device) and you should be good to go.

In my solution for Windows 7 was helpful to update Android SDK Tools to latest version.

ADB Single/Composite values for LG G3 phones -
I found it was necessary to update (~userName/.android/)adb_usb.ini file with the line 0x1004:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2207
0x1004
In addition, I needed to add the following entry in (.../sdk/extras/google/usb_driver/)android_winusb.inf:
;
; Android WinUsb driver installation.
;
...
[Google.NTx86]
...
;LGE Android Phone
%SingleAdbInterface% = USB_Install, USB\VID_1004&PID_633E
%CompositeAdbInterface% = USB_Install, USB\VID_1004&PID_631D&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_1004&PID_631D&MI_01
[Google.NTamd64]
...
Oh, and set USB to PTP as well as turn-on USB debugging.
When you're all done with the file modifications and several passes at installing the drivers (ref. earlier posts), you can verify your phone is ready via the Device Manager. It will list your phone as "Android Device"->"Android Composite ADB Interface". I believe an earlier post explains setting up the drivers

Eclipse not detecting my Galaxy S3 GT-I9305 in list of devices

I know this question has been asked numerous times, but none of the threads have had an answer to solve my problem. It seems no matter what i try Eclipse just wont detect my phone, I have set it to debug mode in the settings, i've installed "Kies 3" on my laptop and it says i have the latest drivers already installed on my phone when i try to update it.
I've installed the google USB driver package from the sdk manager and have downloaded and installed the samsung driver from the samsung website. Windows recognizes the device and in the device manager under android phone it appears as "SAMSUNG android ADB Inerface".
Im running windows 7 and have even tried deleting all the mounted dive drivers from regedit as i seen suggested in another thread but still no joy! Really starting to get frustrated with this at this stage i've been trying for two days now to figure this out!
This is such a pain! I need to be able to debug on my phone too as i'm using features that the emulator can't handle (i.e. audio recording). I'm all out of ideas here so any help would really be appreciated!
Thanks

The method I followed to install my GT-I9300 drivers was this:
Download samsung drivers from this link:
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
Then just connect your phone and make sure you have a stable Internet connection: It will download required drivers automatically.
Also, make sure you have enabled Android developer options in your phone settings. Enable USB debugging in developer options.

I usually get it to work, when I switch the USB mode in my smartphone (e.g. MTP to PTP). This way, windows starts downloading more drivers.

1) Try disconnecting device from PC, revoke USB Debug authorization from settings menu, and then re-authorize the computer you are working on once you connect it again.
2) Check to see if you see the phone in DDMS perspective (left hand side) - if so, try clicking on it and it should work.
3) try removing all drivers (Google, Samsung etc.) + scan "leftover" registery entries using a reg cleaning program. Then install ONLY Kies Light version and try again.
4) It once worked for me - try changing the USB cable (preferably, to an original one)
Let us know if something worked!

1) enable USB debugging in your phone's settings.
2) ensure that you have the proper drivers installed.
3) open adb in command prompt and run "adb connect"

Why won't Eclipse/adb detect my Samsung Galaxy Tab device on my Mac?

I've connected my Samsung Galaxy Tab device to my Mac. Yes, I've turned on debugging. When I go to run my application to test on the device the device is not listed on the Android Device Chooser menu. Running the ./adb devices shows no results.
NOTE: Posting this question for others to find. When looking for the solution earlier all I was able to locate were answers to broken links to device driver downloads for Windows.

Make sure you uncheck
Settings > Applications > Unknown Sources (Allow installation of non-Market applications)

Turn on USB Debugging inside Settings > Applications > Developers Settings

If you're trying to connect to a Mac, I had this issue with a Samsung Galaxy Tab 10.1 running Android 4.3. To enable developer options, open the Settings app, tap on "About device" under the "General" tab and then tap on the "Build number" repeatedly (it's grayed out but you can tap on it anyway). A small pop-up will appear showing the amount of additional taps you need to do to turn on these options.
Once enabled, just turn on USB Debugging and it'll show up in Eclipse just fine.

I had this problem on my Mac and after 30 minutes tried switching USB ports and it finally started working on the second port.

I fixed it by reboot the device (Samsung Galaxy Tab2 7.0)

Update your driver for samsung. It can be found here: http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
Connecting your phone after development mode is on, and USB debugging is on.
At connecting to the PC the phone asks to trust this location. Finally.
This fixed my problem while all other tips were incomplete.

It does not answer your question of how to get ADB to see the device - I could not get that working. But what I did to install an APK I needed to test was to put it in Dropbox on my computer, then install it from there on the device.

Connect your device via USB hub instead of directly connecting to one of the usb ports on MAC. It worked that way for me. Please give a try.

There's also a pop-up that comes up at times requesting the currently connected computer to have access to your device(not to be confused with the Linux not supported pop-up; it lies ; ] ). I continued to receive Target:Unknown in Eclipse until I managed to catch it and accept. This is on a Samsung Note 8", which I believe is registered as a Tab 10.1 in my Arch Linux udev rules.

It may also happen that USB debugging is not checked on your device. Please go to developper options in your device and check it is enabled.
By the way, for devices with android Jelly Beam (4.2) and later versions, you will find out that this option is hidden. To activate it, click 7 times on the compilation number, and the option will be activated.

Tried everything, nothing helped. Including
USB debugging enabled
MTP/PTP
ADB restarted
Device/PC restarted
Tried Samsung's USB driver
By tricking/modifying driver installer, installed Google OEM Usb drivers for Galaxy Tab.
All software up-to-date
The only thing that helped is installing Kies3 + setting PTP on device, instantly authorization pops out in device. Everything OK now.
Kies3 download here: http://www.samsung.com/uk/support/usefulsoftware/KIES/

Enable USB Debugging mode solve the problem!
For those who don't know how to enable it (it's very hidden on Android 4.3 onward), see this.

In my case, this solved the problem:
unchecked the Settings->Security->Unknown Sources,
clicked on the upper left corner and changed USB mode from MTP to PTP,
unplugged/plugged the device, and
clicked OK on the USB debugging prompt.

Had this problem last year, never solved it. Again, after googling high and low, I could not find a cure for the USB debugging flakiness. Now for the good news:
1) Root your device. 2) Install adbWireless widget from Play (I am in no way associated with the author).
You are now good to go. After starting adbWireless and following its directions, you can now debug through adb wirelessly to your device, in my case, the original 7" Galaxy Tab.