adb doesn't show nexus 5 device

Question

Android Studio 0.3.6
Fedora 18 3.11.7-100.fc18.x86_64
Nexus 5 Kitkat

Hello,

I have been using my Samsung Galaxy Tab 3 7.0 runn

Answer 1

Something nobody has mentioned yet:

Some cables do NOT support data. I was sitting here wondering why my Nexus 5 was refusing to show up on OSX. It turned out I was using a cable that didn't support data.

I swapped to a different cable which did support it, and suddenly I was able to use USB debugging.

Answer 2

If anyone is trying to connect Nexus 5 to a formatted Windows XP then follow these steps:

1. Download and install media transfer protocol porting kit: MTP porting kit
2. Download and install WMFDistributable-11 for XP: WMFDist-11 XP
3. Download and install LG United Mobile Driver v3.10.1: stackoverflow is not allowing to share more than 2 links, please google this.
4. Connect your device.
5. Go to Device Management
6. Right click on Nexus 5 and click Update Driver
7. Select Yes this time only
8. Select Install Software Automatically
9. Wait for sometime.. and enjoy transferring files

Answer 3

ADB and driver versions matter. The newer the device, the lower the chances of an older version ADB to work correctly.

Apps using their own ADB copy need to be updated or at least have their ADB updated manually.

When installing Helium / Carbon for instance, it uses an old / incomplete ADB. Newer devices might not link to the ADB server for this very reason.

What I'm writing here should work for any future devices on Windows and possibly *nix OSes.

First the systems must be prepared. on Android:

• activate developer mode, either from an app (like Helium, when prompted) or by accessing the about phone section, taping build number until the developer mode unlocks
• in developer settings enable USB debugging
• in security settings allow unknown sources
• (when connected with USB cable) set USB connectivity to PTP mode (camera device, if so labeled)

in Windows:

• uninstall older USB driver (with file removal) if there is one, but only when the device is connected and in developer mode, otherwise that particular device won't be listed
• install latest USB driver after the device has been plugged in and developer mode is active, the device will be listed as unknown or other in Device Manager; the drivers can be downloaded separately from Google Android support site, these are the same as vendor drivers, with only fewer ID's in inf file making the driver not being recognized for all Android devices
• if the driver does not recognise the device, no problem, install it generically: Manual Install > Show All Devices > Have Disk > pick inf location of the Android USB driver and from the list select Android ADB Interface; there's not need to edit the inf by adding hardware ids, the end result is the same
• each of the modes, PTP and MTP will have their own driver entry, so if the device asks for MTP, the same driver installation procedure must be followed, again

Once these steps are/were previously done correctly, adb must be tested. If Android SDK was installed previously, open a command prompt where adb.exe is and test the listing of the device.

adb start-server IMPORTANT NOTE: This command will prompt the device to allow the communication between the computer it's been linked to on the first run. The prompt will also list an RSA key specific to the PC in question. Without this prompt on start-server, ADB will NOT work! Nor will any application relying on ADB.

adb devices Must list the device(s). If the list is empty, and most likely the RSA prompt did not occur, then no communication will work. If the list is empty the current ADB (and SDK) must be updated or installed fresh (in the case of apps bringing in their own ADB runtime, like Helium / Carbon).

In the case of applications that do bring their own ADB, if the version is old, and these apps insist in using it instead of the SDK one, these files need to be replaced with the latest ones from Android SDK. Plain and simple copy & paste.

As for Android SDK, the only required packages to be installed are SDK Tools and Platform-tools. There, ADB.exe will need some support libraries, on Windows these files are AdbWinApi.dll and AdbWinUsbApi.dll. After all is done, the SDK can be uninstalled from SDK Manager while being able to retain the ADB tool if this is the only runtime used, depending on the case in question.

Answer 4

I had the same problem, USB debugging enabled, device showing up in windows but I never got the question about RSA fingerprint when I connected my Nexus (6) device, nor did it show up in the Android Device Manager.

BUT In the windows device manager I did have an entry saying it was an android device and Composite ADB interface etc. Still didn't work. When I tried the previous tips about manually updating the drivers, Windows 8.1 just responded that "Windows has determined that the driver software for your device is up to date" this was not true. Looking at the driver details I saw that the driver was published by "ClockworkMod". I realized this must be because I had installed the Helium app sometime last year. So I uninstalled that, still had the same problem. Checked again, this time it was indeed google drivers, but version 7 published in 2012 (and not version 11 published 2014). I uninstalled these AS WELL and then tried the trick of reinstalling the driver from the SDK located in: %localappdata%\Android\sdk\extras\google\usb_driver

Now when I replugged my device it finally works and can be debugged with Android Studio. Indeed a driver problem.

Answer 5

For those who are still frustrated, if you are using the experimental ART runtime, try switching back to dalvik (in developer options on device)

Answer 6

Follow these steps,

• Enable Developer options in your device. To enable the developer mode, Settings->About phone, tap Build number option 7 times continuously
• Go to Settings-> Developer options and Turn on USB debugging
• Make sure you reconnected the device via USB and grant permission on the dialog that appears.
• From the above steps it didn't work try this step, Go to Settings->Security and turn on Unknown Sources