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

问题:

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

回答1:

If you have installed EasyTether on OS X, the EasyTetherUSBEthernet.kext can prevent adb from communicating with your mobile device.

If you use Easy Tether, BEFORE you plug in your phone run:

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

(or unplug/plug your phone in after)

If you are done debugging and want to use EasyTether again, either restart or:

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

---

If you want to remove the EasyTether kext so it never hassels you again:

sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
sudo rm -rf /System/Library/Extensions/EasyTetherUSBEthernet.kext

---

Reference/Credit: http://www.intohand.com/post.php?s=2011-02-17-android-debug-bridge-not-just-working-on-mac

回答2:

Having just connected a brand new Motorola Atrix 2 to my Mac running 10.6.8, I had to pull down the menu from the top of the screen, tap on "USB Connection", and change it from "Motorola Phone Portal" to "Charge Only" before it would show up in my list of devices from adb. Hope this helps!

回答3:

Following the google bug submission... I set usb mode to Charge Only, and it detected the phone immediately. Pretty silly.

回答4:

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.

回答5:

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.

回答6:

Change the USB connection type to 'Charge Only'. That was the only change I made it showed up on my device list. Weird.;)

回答7:

If none of the above works for you just as it didn't for me, just try using a different cable. The cable I was using was my friend's cable but it was only meant to charge over USB, not to pass data over USB. I don't know how to tell the difference between micro USB cables that do or don't support data over USB but it's worth a try! Good luck!

回答8:

I have seen another report of this bug. I have not been able to reproduce it myself yet.

The bug is: MacOS X 10.6.6 [on some hardware] breaks adb [for some phones].

If anyone is able to reproduce the bug, feel free to add details of the exact hardware, build numbers and so on. I've asked the person who can reproduce the bug, to report it to google using the form at http://code.google.com/p/android/issues/entry

When he does that, I will add the bug report URL here, and people can add their hw/sw details to the bug report.

In the meantime, to be safe, I would recommend Apple users should NOT accept the snow leopard upgrade to 10.6.6, which was pushed on Jan 6 2011 (so it may already be too late for most).

Peter

回答9:

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.

回答10:

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).

回答11:

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.

回答12:

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)

回答13:

I have the same problem, I solved using an alternate install method.

First I put an sd card in my device. Then I use a File Manager to transfer the .apk to the device, and I install it from the device

You can see a tutorial in http://www.youtube.com/watch?v=7UOAw124y1s

回答14:

I had this problem today with my HTC mytouch phone and OS 10.6.8. At the same time, the phone reported a damaged SD card. The solution was to remove the Micro SD card and erase/format it using disk utility as FAT 32. The name I gave the SD card volume appeared in the Finder when I tried connecting again (charge only). For some reason, Android reported the card as damaged but could not format it. I used a Micro SD USB adapter. My Macbook didn't see the card until I carefully slid it out and back into the adapter slot. This is a known problem with HTC android phones.

回答15:

The last time I updated my tablet, it turned off "allow USB debugging", and I spent a half hour or so spinning my wheels. Double check that that is turned on in settings.

回答16:

This thread is old but perhaps my answer will help somebody. Using a Motorola MB865 with OSX, ADB would recognize my phone only after I performed a factory reset.

I got the idea from this thread.

This was after I tried all the other tricks listed in other threads:

1. adb kill-server followed by adb start-server

2. Make sure USB Debugging is enabled

3. Make sure vendor USB ID listed in adb_usb.ini

4. Switching USB cables. For what it's worth, I did have to switch cables in order for the Mac to see the device. But this had no effect on ADB.

In the end, the factory reset did the trick.

回答17:

in my case what worked:

• disconnect device
• exit android studio
• run 'Activity Monitor' and kill adb
• start android
• studio reconnect device

回答18:

For some devices running Android 4.4.2, you must enable tethering. You can do this in "Tethering and Mobile hotspot" and then check "USB tethering".

回答19:

Try restarting the Mac in "Safe Mode". It worked for me (macos X.9.5)

回答20:

Make sure that USB Debugging is enabled in Settings -> Application -> Developemnt, and also that the selected USB method is PTP and not MTP (not supported in OSX).

回答21:

After connecting the device and enabling the USB debugging please go to the path of adb, which is now inside the android-sdk-->platform-tools and type the following command ./adb devices. I think this will list the devices connected.