You should now be able to start an adb shell, install an apk, etc.

If you see your Android device listed, as shown in the output of the last step, above, then you’re in business.

Finally, restart the adb server on the USB device and check that your device appears.

Go back to the Android SDK directory (unless you have adb in your path) and kill the adb server, in case it’s still running$ cd -$.

$ sudo kextunload EasyTetherUSBEthernet.kext If you’re using a different app, you’ll have to find out what kernel extension it uses on OS X Go to the system extensions directory and unload the EasyTether kernel extension.

Now, it’s time to free the USB device.

Verify that the device and usb port aren’t available by executing the commands “adb devices” and “adb usb”.

In my case, it’s in ~/android-sdk-macosx/platform-tools

Connect your Android device (phone, tablet, etc.) to the USB port.

If you use a similar tethering app, this solution may also be helpful. If you also use EasyTether or EasyTether Pro, the instructions below will get you up and running. Both wanted to use the USB port to communicate with the phone. Similarly, issuing the “adb usb” command would result in “error: device not found”.Īs it turns out, the problem was due to a conflict between adb and EasyTether, a USB tethering app. In my case, when I would issue the “adb devices” command, I would get back “List of devices attached” and nothing afterward. Getting started with Android development on OS X? Is the debugger unable to see your Android phone via USB? I ran into a similar issue and solved it as follows.

Mac adb devices empty emulator