Macbook adb cannot open interface

Question

I am having trouble debugging Android ADB via USB.

Using a Macbook Air 2013 and trying to connect a Nexus 6 phone.

MAC Android Studio has Android sdk installed.

When i do

adb kill-server adb devices 

I get:

 adb I 661 9881 usb_osx.cpp:259] Found vid=18d1 pid=**** serial=***** adb I 661 9881 usb_osx.cpp:259] adb E 661 9881 usb_osx.cpp:331] Could not open interface: e00002c5 adb E 661 9881 usb_osx.cpp:265] Could not find device interface 

Thus, it was discovered that the device, vendor identifier, product identifier and serial number correspond to what I find in the system information for Nexus 6.

The following sentences found on the Internet, I tried - but did not have time - to solve the following:

• disable and re-enable debugging mode on the phone, as well as switch between USB configurations for charging, MTP, PTP, RNDIS, Audio Source, MIDI, always checking that authorization for the Mac RSA fingerprint is set

• shutting down Android Studio / DDMS, destroying adb via the kill-server command, and the kill process using Apple's activity monitor

• run adb as root

• restart your Mac several times

• reboot Nexus 6

• fully install Android SDK

• I tried to use another device to work with debugging (Samsung Galaxy Tab, also here adb found the correct information about the device, but cannot access the interface with the same error)

• tried with 3 different USB cables, all the cables that were originally sent with Android devices

Through google, I found out that the error code e00002c5 means that the device is already in use by another driver.

I recently installed Sophos Home Antivir. Thinking that this might prevent ADB from opening the device’s interface, I completely uninstalled Sophos with the uninstaller provided and rebooted the Mac.

Any hints are welcome:

• What steps need to be addressed?

• since e00002c5 seems to be a clear indicator that another driver has the device being used, how to find out which process is and how to stop it.

Answer 1

I ran into this error and it turned out that the problem for me was that the Stetho tab was open in Chrome (i.e. the tab in the URL chrome: // inspect / # devices), which, it seems to me, causes the use devices. Closing this tab, then running adb kill-server , do adb devices again.

Answer 2

Same symptoms as Galaxy S7 connected to Mac via USB. In my case, I had a Tizen IDE for Samsung Gear Development. It also interfered with adb. Closing the Tizen IDE immediately helped.

If this is your first time connecting a mobile phone, you may have already confirmed authorization for the computer on the phone. You must remove authorization on the phone and reconnect / re-authorize. Otherwise, the device will appear in the list of devices, but will be unauthorized. (Ie you can't debug ...)

Answer 3

I ran into this problem with the message "Could not open interface: e00002c5". e00002c5 indicates that another application is using the device. The Titsen Studio was the application causing this problem. Tizen's private IDEs and connected devices were available on the adb device list.

Answer 4

I debugged the Mobillyo app using the LG K4 phone. I closed Android Studio, then turned on USB debugging in the phone’s settings, left the settings open, Android Studio RUN reopened, a dialog box with information about the phone and Unauthorized was offered to approve the phone, touched Ok, and it worked.

Answer 5

If you use VirtualBox and open a virtual machine, you are probably trying to use adb from your host while it is connected to your virtual machine. The problem is that you cannot connect the device at the same time.

Solution . Uncheck your device in the lower right pane if it is detected by your virtual machine.

Answer 6

If you have accessed your device in a virtual box and are now trying to access it from your operating system, you first need to disconnect the device from the virtual window. To do this, go to setting> USB > unchecked the device from list

Then unplug the phone first and replace it. Or kill and start the server using >adb kill-server >adb start-server . It works for me.