Android device not showing in adb list

Question

I have a Slate 21 HP that is connected to my Windows window using a USB cable. USB debugging is enabled on the device. After adding the correct %SingleAdbInterface% and %CompositeAdbInterface% android_winusb.inf file, android_winusb.inf now see the “Android ADB interface” in my device manager. However, running adb devices on the command line does not display the device.

I have another slider number 7, which is displayed only under adb devices .

The only difference that I see from Device Manager is that the one that works is called the “Android Composite ADB Interface” and the other is called the “Android ADB Interface”.

There is another subtle difference. In the winusb.inf file for Slate 7, I have two %CompositeAdbInterface% entries, but for Slate 21 there is only one %CompositeAdbInterface% entry.

What could be wrong in my setup?

Answer 1

It looks like the installed driver was in poor condition. Here is what I did to make it work:

• Remove device from Device Manager.
• Rescan hardware changes.
• The "Slate 21" list item will be displayed with the status "Unknown driver".
• Click "Update Driver" and select / extras / google / usb _driver

Device Manager will find the driver and warn you about installing it. Select "Yes." This time the device is correctly installed.

Please note that I did not need to modify the winusb.inf file or update any other driver.

Hope this helps.

Answer 2

Make sure your device is not connected as a media device.

Answer 3

I had a similar problem and decided to follow these steps after connecting the device via USB:

• enable developer options on your Android device.
• enable the checkbox for wakefulness.
• Check the box to debug USB.
• open cmd
• got platform tools like D:\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools .
• adb kill-server
• adb start-server
• adb devices

Now we see the connected devices.

Answer 4

For me, the solution was to use a different USB port on my laptop

Answer 5

Enabling fraud actually allowed me to install and debug an LG device, and that was the only way I could work.

Answer 6

Do you ever reset adb after installing a new device?

Or from the command line:

• Close Eclipse at startup
• Go to the Android SDK platform directory on the command line (well, you knew that, I know!)
• type adb kill-server
• then enter adb start-server
• Read if there are some errors, try adb devices again

Answer 7

Disable and re-enable "use debug mode" on your phone.

Answer 8

I also had the same problem, I tried to use every possible solution posted in this thread, but I found out that I had the same problem as explained by JohnnyFun , but according to HenrikB I could not find any parameters in my phone Samsung Galaxy S6 (Android 6.0.1)

Settings → Storage → menu → USB connection to computer

Finally, I draw - when I connect my mobile charger in the drop-down menu, I see options such as

Then click "Connected for charging" →> you will see options such as →

There you can change the option "Transfer media type files"

Answer 9

So the methods mentioned above did not help me. What worked for me is the Google Gigabyte USB USB driver, which downloads and launches an application that recognized my device when I made adb devices. Since I used the Samsung Galaxy, I used this link to download the USB driver from the official Samsung website. Would you like google to match your own Android usb model driver.

http://www.samsung.com/us/support/owners/product/SCH-I925EAAVZW

After downloading it, I launched an application to install my USB driver, and then made adb devices. Make sure your Google USB driver from the Android SDK is loaded and your sdk is also updated. Also, make sure your USB debugging mode is turned on by choosing Settings → Developer Options →, then check USB debugging. After that, your device in the device manager should not have a yellow exclamation mark next to it. When you start adb devices, your device should appear. Hope this helps people. I literally spent hours trying to figure this out. I hope my answer will save you guys in the hours that I spent on the Internet.

Answer 10

adb did not find the connected communication device 5. The phone is turned on, the developer options are enabled, USB debugging mode is Enabled, now it can be seen using adb. In addition, the USB configuration is still MTP. Hope this helps.

Answer 11

just try adb kill-server then

 adb devices 

Answer 12

While many of these solutions worked for me in the past, all of them I failed today on a Mac with Samsung S7. After trying a few cables, someone suggested that connecting an ADB requires an official Samsung cable to work. Indeed, when I used the Samsung cable, ADB worked perfectly. Hope this helps someone else!

Answer 13

For WINDOWS users, follow the instructions here. https://software.intel.com/en-us/xdk/docs/installing-android-debug-bridge-adb-usb-driver-on-windows

Basically, MTP / PTP is all not needed. You need to configure the device from the device manager, following the instructions on the screenshots of the page.

Hope this helps.

Answer 14

For what it's worth, I had problems installing the ADB driver from my Windows7 machine. It turned out that the Virusscan access protection prevents (only some) drivers that need to be installed properly. Unplugged USB, removed the samsung device from the device manager, disabled access protection VS, reconnected the USB and everything was in order. Spent an hour hoping he will save you.

Answer 15

Switching USB debugging and then back was the trick for me.

Answer 16

In the Windows configuration, go to device management. Check if your device is displayed and drivers are installed. You probably haven’t installed the correct drivers for your device.

Answer 17

Remove the battery from the phone, wait 10 seconds, add it again and try again (next to the developer’s options, etc. in other matters).

I tried all the other answers, but this was necessary in addition to other suggestions for me.

Answer 18

I tried all the options in the answers above

• disable debug mode and on
  
• USB configuration done - charging
• made the stay awake

Does not work. For my mobile phone Samsung J7 downloaded the USB driver
After installation, the device was shown in adb devices.

Answer 19

My Galaxy S8 no longer appears as a USB device with any USBC cable, not on Linux, not on Mac, and not on windows. Its only charge. I look through all the settings (developer mode, etc.). But I can not find the problem.

Answer 20

After all the solutions were resolved and still have not found a solution, I brought the problem to the USB cable (s).

Since it worked sometimes for me (i.e. at work), and not at other times (for example, at home), I decided to try the different cables and different Android phones that I had. And, of course, some of the cables do not work (adb cannot see the phone) with any of the phones, but they still charged the phone, and Android recognized that it was connected.

Good cables obviously charged the phones and were immediately recognized by adb. That was a pretty clear difference.

I could not tell the cables physically from the outside, but all were free USB cables that I have been building over the years.

Answer 21

I had a similar problem with my “Xiaomi Redmi Note 4” and I tried almost 10 solutions that I found over the Internet, but none of them helped me. I wrote this answer to help someone like me.

Installing "Intel USB Driver for Android Devices" completely solved my problem. This is fully described here .

Answer 22

Try updating your ADB and phone .

Then, if it still does not work, try connecting to the phone using usb debugging or using usb strong> storage .

Answer 23

I had the same problem in my ubuntu. When I run the adb devices command, it shows me ?????????? No permission ?????????? No permission .

Then I tried with adb kill-server , and then sudo su and adb devices . There is no need to run the adb start-server devices command, it will start automatically if it is not already running.

Hope this saves 1 minute.