OS X 10.6.6 and “adb devices” fails to list androi

Question

adb devices was working fine last year, but after upgrades and new software installs, adb devices no longer recognizes USB attached Android devices.

Here is what I have tried:

adb kill-server
adb devices

adb usb
  error: Device not found

Answer 1

The EasyTether fix worked for me, although first I had to load the kext file, then unload it. My Droidx popped up right away!

By the way, I'm running Snow Leopard 10.6.8 on my MacBookPro, so those who are having trouble with adb and connecting devices should check any USB applications, like EasyTether, for conflicts. Also be sure to follow all the above rules for 1. Application debugging (Settings->Applications->Development) USB debugging: ON 2. USB connection (on notification bar). Choose USB Mass Storage (altho Charge Only also works with my droidx and MacBookPro) 3. Unknown Sources (Settings->Applications->Unknown Sources = ON)

Answer 2

I was having the same issue and tried connecting as charge only, but that didn't solve the problem, then unchecked the "Unknown sources" option to allow installation of non-market applications, tried it again and it recognized the device. I'm running android 2.2.3.

Answer 3

I too am having this problem. However, it isn't just a problem with ADB, it's a problem with android devices in general on Mac OSX 10.6.6 Snow Leopard. Devices that used to work in 10.6.4 will no longer even mount the device as a USB drive. Googling to see if I can find the answers.

Answer 4

I just ran into this problem using my HTC Inspire (Android 2.3.3) and Mac OS 10.6.8.  The phone did not enter USB debugging mode when I connected it to my USB hub, but it did start USB debugging mode when I connected it directly to my MacBook Pro.

... and then, of course, it showed up in the list of devices attached.

Answer 5

Another alternative: on modern Apple iMac's, the USB port closest to the outside edge of the machine never works with ADB, whereas all others work fine. I've seen this on two different iMacs, possibly those are USB 1.0 ports (or something equally stupid) - or it's a general manufacturing defect.

Plugging USB cables (new, old, high quality or cheap) into all other USB ports works fine, but plugging into that one fails ADB

NB: plugging into that port works for file-transfer, etc - it's only ADB that breaks.

Answer 6

The bug report to Google is http://code.google.com/p/android/issues/detail?id=15583

If you have encountered this bug (upgrade to MacOS 10.6.6 and adb no longer sees some phones on USB) please add a comment with any useful relevant info (like your exact hardware type).