Cannot find an Android device using the "adb devices" command

Question

I am developing an Android application on macOS , and my application works well on an emulator. I want to run it on a device, but when I run adb devices , I get nothing.

 localhost:platform-tools BF$ adb devices List of devices attached localhost:platform-tools BF$ 

I checked the documentation in the link "Configure device for development". I have done everything step by step.

There are a few words in the documentation: Configuring your system to detect your device. If you are developing Mac OS X, this just works. Skip this step.

Now I can not find a solution. Do I need special drivers for Android devices?

Answer 1

I know this thread is outdated, but I think it can help anyway. Almost all the time “it just works” on OS X, but sometimes new / prototypes or obscure devices are not matched. Try to help with these steps (I'm not close to my Mac right now, but I did it last night and think I remember):

1 - Open the system profiler and find the device on USB. Browse it to find the provider ID. For example, Motorola devices will show 0x2bb8. Or just google for your vendor hardware id.

If nothing is shown, make sure you are using different cables. Android file transfer is good for detecting a device if you have a working cable.

2 - Change ~ / .android / adb_usb.ini to include this provider ID. If the file does not exist, create it only with this line.

3 - Restart ADB

 adb kill-server adb start-server 

4 - Perhaps disconnect / connect your phone.

And I hope you see your device.

Answer 2

Do you accidentally use the EasyTether app while connecting to your Mac? If you use this application, you are in luck because the solution should call:

 sudo kextunload -v /System/Library/Extensions/EasyTetherUSBEthernet.kext 

from the terminal. I forgot if you need to reboot or not.

This will disable the binding, but now you can see your device through adb.

To update the binding after debugging is complete, use

 sudo kextload -v /System/Library/Extensions/EasyTetherUSBEthernet.kext 

Of course, if you are not using EasyTether, then hopefully someone has an idea ....

Answer 3

Same problem. osx 10.6.6 and adb devices giving $. / adb devices The list of connected devices ... is empty ....

Rebooting the phone did not help, although it was indicated with adb devices only for a second at boot time.

Debugging has been enabled in adroidsettings-> applications

What, in the end, made a mark: disable and enable debugging mode again.

Answer 4

If you are struggling with such a problem using Lollipop (Android 5. *), you guys should probably take one simple step that I took before my ADB (I use Ubuntu) received my phone:

Change the USB PC connection type to “Send Images (PTP)” (before I used the “Media Device (MTP)”)

Similar:

And do not forget to activate the "USB Debugging" checkbox.

Answer 5

I had this problem today when the phone was charging when connected, but the Mac did not see it. It turned out that the micro USB cable that I used was intended only for charging and did not make data. As soon as I changed the USB cable, it began to work normally.

Answer 6

Link to this link!

THIS IS ONLY FOR OIL!

Here is what you need to do to make your phone visible to adb:

• Open terminal (Applications / Utilities / Terminal)
• cd /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBCompositeDriver.kext/Contents
• sudo nano Info.plist (or vi, or emacs, or whatever console editor you prefer)
• Copy the IOUSBComposite section (from <key> to </dict> )
• Insert the section on line 66 (immediately after it appears) so that you have 2 copies in the file
• Change the value of bDeviceSubClass from 0 to 2
• Change the key name from IOUSBComposite to GW620

---

The end result should look something like this:

  <key>GW620</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.driver.AppleUSBComposite</string> <key>IOClass</key> <string>IOUSBCompositeDriver</string> <key>IOProviderClass</key> <string>IOUSBDevice</string> <key>bDeviceClass</key> <integer>0</integer> <key>bDeviceSubClass</key> <integer>2</integer> </dict> 

---

8. sudo diskutil repairpermissions / and complete it
9. sudo touch /System/Library/Extensions and wait a few minutes to reindex the extension to complete
10. adb devices should now see your phone

Please note that this is VERY kludgy, and will probably break every time OSX updates itself, but it works. I can finally stop rebooting every time I want to work on the phone !: D

Answer 7

If adb devices does not display the device, although you have connected it to the system, you need to make sure that the USB debugging option is USB debugging on the Developer Options tab in the Settings section. In Android 4.2.2 and higher (from what I observed), Developer Options are hidden unless explicitly stated. To make Developer Options active, tap 7 times on Settings > About device > Build number . After that, go back to Settings > Developer Options and activate USB debugging .

Using adb version 1.0.31 , I was able to make the device visible.

Answer 8

I had this problem. Turns out my fix is ​​to replace the USB cable I was contacting. I switched to using the cable that came with the phone and it worked.

Using Samsung Galaxy Player and Samsung micro USB.

Yes. This is incredibly stupid.

Answer 9

If you use adb devices on Mac OS X , the device does not display and, of course, you have enabled USB debugging on your device (see http://developer.android.com/tools/device.html ), then try:

 $ android update adb adb has been updated. You must restart adb with the following commands adb kill-server adb start-server 

Then:

 $ adb kill-server $ adb start-server * daemon not running. starting it now on port ... * * daemon started successfully * 

And finally:

 $ adb devices List of devices attached ...... device 

Your device should be listed.

Answer 10

In Mac Lion:

I just needed to go to /path/to/android-sdk/tools and run android adb update for the devices that would be detected.

Answer 11

make sure you have the same level of higher level API installed on the SDK packages with your devices.

example:

I have Android 2.3.4 on my Xperia Play. ADB will not detect my device if only Mac API 10 is installed on my Mac (Android 2.3.3). When I installed SDK 11 (Android 3.0), since I did not find the SDK for 2.3.4, ADB is working fine.

Hope this helps you.

Answer 12

You will need a USB driver installed correctly and enabled in the debug settings. if they do not work, there may be something wrong with your device.

Also see this .

Answer 13

rebooting adb server works for me, in emulator, vmwware and virtual

 adb kill-server adb start-server 

if you are using a virtual machine, make sure you have the IP address set:

 Alt + 1 type: netcfg 

to come back:

 Alt + 7 

if you have:

  eth0: DOWN 0.0.0.0/XX 

change the configuration to:

 NAT or BRIDGE 

Reboot the virtual machine and server and try again.

if you use a phone or tablet:

• unplug the device

• wait a bit and plug it in again

• and restart adb server

Hope this help helps you.

Answer 14

The same problem as Windows 7. It so happened that I used the USB binding function along with an attempt to use adb. There are several ways to bypass this usb cable and debug at the same time.

Answer 15

I installed Xamarin and tried to use Unity. In principle, in any case, you need to kill any application that can talk to your device via ADB