Android ADB does not detect the device in Mac OS X, although the device is detected in Android File Transfer

Question

After installing Android studio, I also installed ADB. However, for some reason, ADB does not detect my device. To make a note, I think I did all the basic things that I found on the Internet, that is:

• Install the device in developer mode and enable USB debugging

• The cable works well (Android file transfer opens automatically when the device is connected)

• Installed Java JDK 8

• I did "adb kill-server", restarted my device and Mac, but still did not work.

I use Android Studio 2.2 and run Mac OS X Sierra on my laptop, and Android 5.0.1 runs on an Android phone (on an LG phone).

NB: I tried other solutions when stack overflowing, but this is not a problem.

ADB (installed) and works from the command line, but when I run:

• 'adb usb', he says: "Error: no devices / emulators found"
• 'adb devices', it prints a list of connected devices with an empty line at the bottom.

I think this is a special problem, and general solutions for installing ADB or rebooting do not work here, since I tried all this.

• I uninstalled and reinstalled Android studio, still not working.

• I uninstalled and reinstalled adb, adb and fastboot, still not working.

• I restarted my device, disabled and turned on developer mode again, still not working.

• Obviously, I unplugged and reconnected the cable back, still not working (only Android File Transfer continues to rise)

Just in case, I have my root device, maybe a problem, or does it not matter?

Can someone please help?

Answer 1

Finally, a strange problem has been fixed: -

Basically, you need to set USB mode to PTP mode instead of multimedia messaging protocol (MTP) mode.

When I connected the device via USB, the USB icon and the debug mode icon appeared in the device status bar.

If you open the control center by scrolling from the top, you should see "MTP media devices" - tap for more USB options. Click it and switch the mode to "Send Images (PTP)" and it should ask you if you want to enable USB debugging. Turn it on, and the device must be recognized by ADB and Android Studio.

Thank you for your time to those who suggested other solutions.

Greetings

Answer 2

Maybe I was a little late for the party at this, but I just cleaned my MBP installed and ran into the same problem. I tried the things suggested here, but nothing worked.

What I needed to do to fix this was "Cancel USB debugging authorization" from the developer options.

As soon as I did this, he offered the usual option "You want to enable debugging on this device", and everything was fine.

Hope this helps someone out there!

Answer 3

None of these answers sufficed me. I was already in a state of debugging USB, and also switched the USB configuration to PTP. It was still in constant charge mode no matter what I do. I even reinstalled everything related to Android, tried it on several devices to find a solution. Finally, what I got is a new cable.

I posted the question here (now marked as duplicate), as these answers were missing my situation.

Answer 4

Go to the developer options and enable USB debugging:

Settings> Advanced> Developer options> Debugging> USB debugging.

Remarks:

You must first enable developer mode on your phone

Answer 5

If anyone still has problems, consider the cable you are using. Not all USB cables are created equal! Some charge a fee but do not allow data transfer. See this post .

Answer 6

In my case, the problem was that the developer mode disappeared after updating the Android system. Double check developer mode and USB debugging settings.

Answer 7

My solution with Android 7:

• Activate developer mode by going to settings> about phone> software information> click "build number" 7 times
• connect usb to your <-> macbook phone and select the “charge” option
• Settings> Developer options> enable "USB debugging" (if this field is disabled, first cancel USB debugging, then disconnect and reconnect)

Answer 8

I tried everything on my MBP but could not solve the problem. Finally, with the least expectation, I dropped my MBP SMC and everything returned to normal !!! https://support.apple.com/en-us/HT201295

Answer 9

Make sure that other services are not trying to access the device through adb. For me, I used Chrome Inspect to check network requests. When I closed this window, the studio automatically detected the device.