I have a HP Slate 21 that is connected to my Windows box using a USB cable. USB debugging is enabled on the device. After adding the proper %SingleAdbInterface%
and %CompositeAdbInterface%
entries to the android_winusb.inf
file, I now see "Android ADB Interface" in my Device Manager. However, running adb devices
at the command-line does not show the device.
I have another HP slate 7 that shows up just fine under adb devices
.
The only difference I see from Device Manager is that the one that works is named "Android Composite ADB Interface" and the other one is named "Android ADB Interface."
There is yet another subtle difference. In the winusb.inf file, for Slate 7 I have two %CompositeAdbInterface%
entries defined but for Slate 21, there is just one %CompositeAdbInterface%
entry defined.
What could be wrong with my setup?
Remove battery from phone, wait 10s, re-add it and try it again (alongside developer options etc.. in other questions)
I tried all other answers, but that was required in addition to the other suggestions for me.
I was having same problem in my ubuntu. When I run command
adb devices
it shows me?????????? No permission
.Then I tried with
adb kill-server
and thensudo su
andadb devices
. No need to run commandadb start-server
devices command will start it automatically if it is not already started.Hope this will save once one's minutes.
I had a similar issue and solved with the following steps after connecting the device via USB:
D:\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools
.Now we can see attached devices.
On Android 7.1 Nougat (in my case, a Moto G), manually re-enabling USB debugging on Developer Options did the trick:
Settings > Developer Options > USB debugging
In Galaxy s6 - I resolved it by: Settings -> About device -> Software info -> Build number - tap it 7 times to enable Developer options. Go back to Settings -> Developer options -> turn on USB debugging.
Go back to your terminal
adb devices
and you should see the connected device. Hope that helps.Click on Attach Debuger to Android Process and Click On Restart ADB.