In cmd when I try to do the command:
adb shell
it shows device not found error. Can someone help me please. It'll be appreciated.
In cmd when I try to do the command:
adb shell
it shows device not found error. Can someone help me please. It'll be appreciated.
Don't forget to go to your device and enable Settings->Developer Options->USB debugging.
Try any of the following solutions. I get errors with adb every now and then. And one of the following always works.
Solution 1
Open command prompt as administrator and enter
adb kill-server
adb start-server
Solution 2
Install drivers for your phone if you're not testing on emulator.
Solution 3
Open android sdk manager and install "Google USB Driver" from extras folder. (attached screenshot)
Android SDK Google USB Driver missing
Solution 4
Go to settings > Developer Options > Enable USB Debugging.
(If you don't see Developer Options, Go to Settings > About Phone > Keep tapping "Build number" until it says "You're a developer!"
It depends on windows system but usually:
<sdk>\extras\google\usb_driver\i386
(or amd64 for and).For my mobile it works, but depend on your mobile if it work or not.
Hope this help, bye.
If you installed Eclipse have Android SDK, go to DDMS. If the list device display "?????????"
you do adb kill-server
and then adb start-server
.
Please make sure you install USB driver and enable debug mode.
Another issue here is that you likely need to turn off "connect as media device" to be able to connect with adb.
For me, I have to Revoke USB debugging authorizations
in Developer Options. Here is the steps:
USB Debugging
,USB Debugging
I solved:
Just turn off USB debugging and re-enable debugging it immediately
On my G2 I had to select PTP instead of MTP mode to get the connection to work.
I had this problem suddenly crop up in Windows 7 with my Nexus One - somehow the USB drivers had been uninstalled. I ran android-sdk/SDK Manager.exe, checked Extras/Google USB Driver and installed it. Then I unplugged the phone and plugged it back in, and ran "adb devices" to confirm the phone was attached.
This doesn't work for all phones, just the ones listed here: http://developer.android.com/sdk/win-usb.html
Developer options
if you can not see developer option, go to about. build version and click build version until developer options in unlock.
I have a Droid 3 (Verizon). I went to Motorola here and found the driver for the device 'Motorola ADB Interface' which was showing in device manager. It's kind of a big download for just the driver, but during installation it found it and installed correctly.
How about:
Settings -> System -> Developer options -> Debugging -> turn on toggle for Wireless ADB debugging
or:
Revoke USB debugging authorizations
and try from the scratch.
On my Sony Xperia XZ1 Compact on Oreo I had to switch USB mode to MIDI to get it working. Only after this my Windows recognised Android ADB, however it couldn't autoinstall driver. I opened Device Manager and installed the Google USB Driver for the ADB.
Just wanted to provide a simple answer here. I am just messing with an old Android device for the first time doing these root and unlock procedures. I received an error like this one when an adb push "..." "/sdcard/"
command failed, and the key was that my device was in the bootloader screen. Booting to recovery then allowed me copy over the file(s), and I presume the normal OS would as well.
This worked for me, my AVG anti virus was deleting my adb.exe file. If you have AVG try:
1) opening the program
2) go to options
3) go to the virus vault and click on it
4) find your adb program, click on it, and press RESTORE at the bottom
This will move the file back to its original place.
However, unless you turn off the AVG it will delete the file again.
After this android studio located the file. Good luck.
I found my solution from this similar thread by enabling USB tethering on my LG G6 (requires data saver to be turned off)
Go to: Settings -> Tethering & networks -> switch on USB tethering
For completeness, I've just had a case here I had to change my USB cable. Guess the one I had was for charging only, accursed thing.
To solve this problem,
Add adb folder to your windows path (system veriable)
This solves the problem
In my case I needed to swap the ends of the cable connecting my device to the computer...