Develop Reference

ADB doesn't list my Device

I'm trying to push an app from eclipse to my phone but adb doesn't work. It doesn't see my phone when I write 'adb devices'. First I thought it could be a problem of Cyanogen Unofficial Android 5.0, so I reverted to 4.4, but it doesnt work either. I followed an answer on this this question 'adb doesn't show nexus 5 device' by installing the driver but the device manager tells me, that the driver isn't installed (Code 28). When I try to install it manually it doesn't work, neither uninstalling works.

I had same problem. Fixed it by doing to device manager
1. Find the ADB driver. If it shows the warning sign then click on update driver.
2. Choose to update the file locally yourself.
3. Browse the file. It always shows a SAMSUNG COMPOSITE DRIVER. Select that option and let it happen.
Don't worry if your device is not Samsung. The same driver works for almost all devices. Mine is a YU Yureka with CM12.
Hope this helped you.

Delete the device from Device Manager.
Rescan for hardware changes.
List item will show up with "Unknown driver" status.
Click on "Update Driver" and select /extras/google/usb_driver
Device Manager will find the driver and warn you about installing it. Select "Yes." This time the device got installed properly.
[source] Android device does not show up in adb list

Try this tool when your device is connected.
--> http://adbdriver.com/
Normally it should list your device and notice it has a faulty driver.
Hit the install button and it wil replace the faulty one with a working one.
[Source] Personal Experience

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

After upgrade Android on Nexus to 4.2.2, Eclipse shows target unknown for device?

I just upgraded my phone to 4.2.2, but now i cannot use it in eclipse anymore.
I tried rebooting the device, reset my debug-settings but I cannot get it to work anymore.
I saw it is already a registered issue. There are some new security enhancements, so there should be a dialog (see here at bottom) but this dialog doesn't appear. I don't have several accounts on the phone, which is pointed out in the issue..
Anyone any suggestions?
EDIT: Look at accepted answer below, this should cover all cases. In my case, there were some packages missing, which weren't shown in the Android SDK Manager. I just found the Packages -> Reload in the Android SDK Manager... And I thought this happens automatically

You need three things in order to make sure this update goes smoothly:
Make sure your device is actually running 4.2.2 and the problem is not something else
Your SDK is updated to the latest tools. The adb binary in all but the latest version does not support the 4.2.2 security enhancements.
You are on the main account of your device in case of multiple user accounts.
Connect your Device to your computer and execute adb devices (make sure USB debugging is enabled). You should see something like this:
3tiu52839ry082j3 offline
Right about now, there should be a dialog on your device that looks something like:
Check the Always allow from this computer box if you want and click OK.
That's about it.
Some other things to check:
Make sure your USB cable isn't broken. Sometimes, the smaller cables break inside the main one, and your device may charge but have no data connection. Try with a different cable, or try accessing files on the device over USB (this will go fine if your cable is fine)
Make sure you're using the newest version of adb. Even after I updated my SDK tools, I couldn't get my device authorized when using adb. I eventually figured out that the Nvidia install of the NDK and SDK tools had updated my PATH variable to use the adb from that install, which wasn't the latest update. By using the adb in my newly updated install, I was able to get it all working.

For me it was solved by changing Nexus 7 tablet to "Camera(PTP)" mode.
Check out this blog post on how to do it.
After USB connection of Nexus 7 and confirming digest on Nexus 7, also connecting through TCP/IP with ADB worked.

Wierdly, unchecking and rechecking the "Allow USB Debugging" option popped me the window and selecting "ok" solved my problem.

If none of the solutions worked for you then Reset ADB.
Go to Devices ---Click the right most down arrow----Select Reset ADB from the list.

I had tried everything suggested here and suggested in every log/blog that I could find in google, but still no go. The USB cable is known to be good. ADB is version 1.0.31 (as shown with , USB Debugging is enabled in the Nexus 7 tablet, the SDK was updated to the very latest tools as available on 1-mar-2013 for 4.2.2/API 17. I had tried both Media and Camera modes for USB, rebooted windows, rebooted device over and over again, re-installed latest google USB driver, etc. etc. but ADB Devices still showed nothing.
I hard reset the Nexus 7 tablet thinking that maybe the screen to allow usb debugging had appeared but got hit with cancel. But that didn't work either.
What finally worked was:
going into windows control panel | Device Manager,
selecting NEXUS under Portable devices,
then in the Driver tab clicking on update and manually selecting the Google USB driver (the check feature said it was up to date). Previously, the date shown was in 2006, afterwards a date in 2012 (but more on this in a moment).
That didn't fix anything though.
So then I switched USB from MEDIA device to Camera device - THEN it wanted to install driver software, so I let it do that. Afterwards, I noticed that the driver for the Nexus was back with the 2006 version, BUT then ADB DEVICES FINALLY SHOWED OFFLINE!!!! HALLELUJAH AND the Nexus was displaying the Dialog to allow USB debugging, and it now all works.
What I am not sure of is what step actually solved the problem. I don't think it was necessary to hard reset the Tablet, but the fiddling with the device driver wasn't a very convincing solution either - I don't think the driver was corrupt - but maybe it had to be changed to get the right driver associated with the tablet when connected as a Camera Device. In any event, it is necessary to connect the tablet as a Camera device for ADB to work...

Restarting device or enabling USB debugging did not solve my problem.
However I changed USB PC Connection to "Camera(PTP)" mode and adb devices showed the device id of the phone.

After reading a lot post talking about this particular problem, I actually solved it by resetting user permissions on files (that were owned by root): ${HOME}/.android/adbkey and ${HOME}/.android/adbkey.pub

Go to Device Manager and uninstall your device and remove from USB
HAve you CMD opend and make sure you are at least in ADB Help.
Connect device to USB and continue with steps provided by Raghav Sood - few answers ahead of me.
Worked for me just fine

I tried with this custom build and it works for me. Now I can see my logcat in Eclipse again.
https://github.com/khaledev/ADT/releases
Download the zip file then in Eclipse menu Help > Install New Software... > Add > Archive... Just pick the downloaded zip and do the rest of the install process.

Windows won't recognize Galaxy S2 at all

I'm having an issue with my Galaxy S2. I typically leave it in Debug mode, up until a few days ago it has worked great. I've successfully loaded APK's for testing through eclipse previously.
I tried to load a prototype of a new app im working on and when I plugged in the S2 nothing happened, Windows didn't beep like usual and when I tried to view running devices it did not show up.
When I look at the device manager under universal serial bus controllers, it doesn't show any 'unknown devices'
I've tried reinstalling drivers through kies, and third party sources (as well as removing all drivers and letting windows install them again for me.
I've tried connecting as Mass Storage Device, with debug mode on and off.
I've restarted both my computer and phone many times.
When my phone is off and plugged in Windows will beep and say that a device was connected but not recognized (which is more then what I get when the phone is on)
And sometimes when I "troubleshoot connection issues" in Kies it will reinstall the drivers and after the process is complete windows will report "Drivers were not successfully installed"
I've tried plugging it into my Windows XP laptop and it will show up as "Unrecognized device" even after I installed Kies on the laptop, and tried the driver installation it with the same results.
Posting here is my last resort as I've spent close to 5 hours troubleshooting this issue, and searching for answers. My biggest concern is that when I do plug my phone in it will beep to say that it is charging, but windows 7 doesnt even see it!
I appreciate all suggestions & help!
EDIT: Also I installed the Samsung Android USB Driver for Windows and windows reports that the drivers were not successfully installed
Thanks
Jon

Try to key in dialer:
*#7284#
It has 4 options:
UART
MODEM
PDA
USB
MODEM
PDA
In USB section, select the PDA. If it already selected to PDA then reselect it by selecting MODEM and then PDA again.
Only change the USB setting and then press back and try reconnect to kies again.
Hope it helps..

I had the same problem and JUST as i was about to give up, i realized that I had replaced my usb cord with a generic one from the store. I happened to still have the old one around still and that ended up being my issue -.-; Hope this helps someone else!

This really sucks, I know I've had this happen a few times and it's really annoying to have to deal with. I had luck with this post where they suggest:
... they suggested removing battery from hero with usb pluged in and
then putting battery back in, so i did this thinking it wouldn't work
and hey presto, mounting option became available. I was then able to
follow your first set of intructions to install the drivers through
devices and sync is now working!
If that doesn't work there are a few suggestions and helpful driver websites on there for you to follow :-D
I know I would:
Uninstall all drivers related to your device
Restart Computer without connected
Pull battery on device, plug it in, and once detected put battery back in.
If driver doesn't install correctly, or "unknown device", go to the website on that forum to get the CORRECT driver for your device and Windows OS
Go to Control Panel->Device Manager->(unknown device)->Update Driver
Locate downloaded driver, install
Make sure that when connected, the device says "USB Connected" in it's notification area
Click "Turn on USB storage", or "USB Debugging -> USB debugging"
.. this will at least show you that you have the right drivers.
IF you did all of this and you still can't get it to debug through eclipse, you either have conflicting drivers somehow, or your eclipse IDE isn't setup properly. Maybe update Eclipse, and Android SDK and try again?
Sorry can't give you exact details but this problem could be ANYTHING lol

I had the same problem while using a generic cord.
Don't use for usb transfert
I think they are made only for charging.
Solve by using a stock cord not a generic one.

Okay, so after talking to Samsung they informed me that there is a small defect with the female usb connection, and that it can sometimes be loose.
Only solution, mail it to them...

This fix works on all my computers that "don't recognize" my rooted Samsung Android. Plug the phone into the computer and restart phone. When it comes up again, the computer recognizes it.

My method is KIES AIR.
Open Kies Air
Go to settings > Bluetooth off set.
More settings > Tethering and portable hot spot > Bluetooth tethering check true and portable Wi-Fi hotspot check true.
Now KIES air open on your device and start button click. copy IP address to browser
Your s2 is connected your computer.
Open browser, and copied ip then click paste.

I have two Win XP SP3 workstations that would not connect to my Galaxy. Finally fixed it by installing this particular Intel driver and installing Windows Media Player 11.

if you are running a custom kernel on your phone, you may want to check too if you have "force fast charge" turned on or not. I thought my phone and computer would never talk to each other again but it turned out I had fast charge enabled. Turning that off solved the problem for me.

It might be an issue with USB 3.0 ports. I was tormented by this issue too and I was at the point where I was so ready to burn this device to kingdom come. Before I did that, I decided to use my never-used 2.0 port and guess what, IT WORKED! If your PC doesn't have a 2.0, good luck with that.

punch in code *#7284#, (UART set to PDA) and (USB set to PDA)
solved my problem

Debug Motorola Triumph

I have installed the latest Motorola USB drivers which include support for the Triumph.
When I plug in my phone, "adb devices" does not list my phone.
My device manager shows my device under Phone as well as Disk Drive. Both use the WPD FileSystem Volume Driver and refuse to let me update the driver by pointing the motorola drivers in Program Files. It continues to tell me that "Windows has determined the driver software for your device is up to date."
Any ideas?

I am currently in just about the exact same predicament =/
I have some possible avenues that we could both share:
Idk if you were able to find a phone number for Motorola (American that is) but i finally found one
Motorola Mobility, Inc.
600 North U.S. Highway 45
Libertyville, Illinois 60048 USA
Telephone: +1 847 523 5000
Here is a link to yet ANOTHER programmer having the same prob as us =/, but he got it figured out using the steps he posted there
Also there is live support chat here.
If you find a solution to this problem, please, please, please let me know =) And i will do the same for you if i get it figured out soon.
Edit:
Nevermind, i got mine to work just fine =)
Heres what i did:
Used USBDeview to uninstall all previously failed attempts at drivers lol
NOTE: You will have to run USBDeview as an Administrator(right click, select Run as administrator)
In the device manager, after uninstalling all the others, right click on what pops up for the device, click update driver, browse for your own, than from there it was a series of selecting from lists, but the key thing here is to remember that eclipse debugs programs on external devices using the adb interface, which should be a pre loaded option in said select lists =)
Hope this helps!!!

Have you enabled debug mode for your phone? This can be done via settings->application settings->development->USB debugging

Whenever I've had a problem with adb recognizing my devices I've managed to fix it by adding a reference to it in my .android/adb_usb.ini file.
I only run Linux/OS X at home and I don't want to try and blindly describe how to do it on Windows from memory, but they discuss it here http://android.modaco.com/topic/294799-adb-windows-7-and-the-pulse-tutorial/
And google gives the USB Vendor ID's here http://developer.android.com/guide/developing/device.html .
On my linux box I added:
0x0489
To my adb_usb.ini (using the Foxconn ID which on linux you can find directly via lsusb, I think you could use devcon on Windows to find it) and it shows up on my device list.

Just because this link hasn't been dropped in any answers (and I always find myself looking for it), here are the manufacturer's development drivers.

This is what worked for me. I have a Moto Triumph and Win7 x64...
Turn on Unknown Sources, USB Debugging
Install Motorola USB development driver. Unfortunately, Motorola broke the old driver URL, as well as many development forum URL's. Fortunately, Softpedia has copies of the installer. Grab the 32 bit or 64 bit version depending on your OS.
Plug in your phone by USB
Open Device Manager
View hidden devices
Uninstall default drivers (Disk Drives\Qualcomm USB, DVD\CD\Android SCSI CD-ROM, Portable Devices\F:)
Action > scan for hardware changes, or Disconnect/reconnect phone
Repeat till ADB appears (probably w/ a yellow icon indicating it's not fully installed)
Right-click ADB > update driver > browse my computer for driver > pick from a list > Motorola > Android Sooner ADB (the first entry)
Accept security warning
Done. If it worked properly, you can now view your device using adb devices.