I know this type of question has been asked before but I couldn't solve my problem with any of the solutions.
My device is not being recognized by my emulator and the the in adb devices List.
I have enabled USB debugging in my phone and tried setting USB devices as my default device in edit configurations but the problem still persists.
I am using windows 8.1 and it doesn't work no matter which android device i connect.
Any help will be highly appreciated.
I have experienced this before. Here is what I have done (for Windows 10 OS). I am not sure whether you have tried this solution before.
Go https://developer.android.com/studio/run/oem-usb and download the OEM driver of your android device
Go to Windows Device Manager. For my case, I found a device, namely "adb" with a warning sign. (something like the following picture)
Click your device -> Driver -> Update Driver -> Browse my computer for driver software. Choose the OEM driver that you have downloaded in (1).
After the update, you should be able to see the device on Android Studio
i'll suggest you to check ur device driver or u can use this link universal ADB driver
& check with the minimal ADB & fast boot, device is recognizing or not.get ADB fastboot from this link
I have recently updated my drivers and I am unable to connect to my Nexus 4.
The nexus is on 5.1. I'm using Windows 7. My HTC desire can be seen listed in adb devices.
I have tried re-installing the drivers. The automatic driver installation installs v7.0.0.1. I don't know if this is the latest version as when I point the installer at \extras\google it says that the current driver is up-to-date.
The phone is in debugging mode, and I have also tried different USB ports on the computer.
Try to manually change/assign the driver in the Device Manager.
Go to Device Manager - Android Device.
Select whatever entry you can find here, then choose:
Update Driver - Browse my computer for driver Software - Let me pick from a List...
Here you should be able to select the proper driver (unticking "Show compatible hardware" should bring some more choices.
If it doesn't work you might want to try using the Universal adb driver (it will be at the "ClockworkMod" manufacturer in the device maanger).
Last but not least, sometimes the issue can be resolved by an adb restart. Just do a adb kill-server, then check again for your device using adb devices
Setting the phone to connect as camera made it show up on adb devices.
With the new update to 4.2.2 to my Galaxy Nexus and Nexus 7, I can't find both my devices under adb.
These are the steps I took:
Updated to 4.2.2
Updated ADT and SDK through the SDK Manager
Checked ADB version, it's at 1.0.31
Restarted PC and Tablet and Phone numerous times
When I run adb devices, it's just blank. I have the same issue on Windows 8 and on Ubuntu 12.10, but on Ubuntu it shows my device and it says offline.
Are there any other steps I can take?
From the adb docs
When you connect a device running Android 4.2.2 or higher to your
computer, the system shows a dialog asking whether to accept an RSA
key that allows debugging through this computer. This security
mechanism protects user devices because it ensures that USB debugging
and other adb commands cannot be executed unless you're able to unlock
the device and acknowledge the dialog. This requires that you have adb
version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher)
in order to debug on a device running Android 4.2.2 or higher
So, unplug, wait, replug in the cable, and hit ok (on modal dialog that appears on your device)
If you hit cancel, the device will show up as offline via adb devices
Try pre-installing the drivers for your devices. Make sure, under Windows, that your device is recognized in the System control panel first.
I use Windows 7 and my Galaxy Nexus wouldn't be recognized by the system until I installed the device drivers before plugging them in. From the comments, this works on Windows 8 as well.
Galaxy Nexus drivers
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW#
Goto Manual & Drivers > Software
Nexus 7
http://support.asus.com/Download.aspx?SLanguage=en&m=Nexus+7&p=28&s=2
Just though Id share my experience, I had -
Unplugged and re plugged in the device
Installed the correct platform tools
Installed the correct Android bridge Turned USB debugging on and off
and on and off an...
Tried WiFi but it said it was offline
etc. etc.
What fixed it for me was changing the device connection from Mass Storage to MTP. To do so, with the phone unplugged you go into -
"Settings" -> "Storage" -> Click the menu Button -> "USB computer
connection" -> "Media device (MTP)"
Hope this helps some one from going crazy!
Thanks,
Ash.
I tried everything mentioned here and in other posts. It wasn't the cable, the USB port, rebooting the PC or Nexus 7, killing and starting adb or enabling/disabling USB Debugging.
It was due to the 4.2.2 OTA update, I simply replaced the \platform-tools\ folder, as described here: Android ADB device offline, can't issue commands
Download the updated platform-tools: http://dl.google.com/android/repository/platform-tools_r16.0.1-windows.zip
adb wait-for-device
works for me. Just unplug your usb device, run this command, and while it's waiting, plug your device in, then it will just work. :)
Here is what I did (Galaxy S4 4.2.2):
go to Settings => about this device => click several times on "Version number", that is to say something like "JDQ39.I9505XXBHYTGKDD" (not android version or anything else) ; here you will see that Google or Samsung have a lot of humour as you have to click until multiple times until having a toast displaying "You are at few clicks from being a developer" ; after something like 10 clicks, you have a toast "You are a developer"
Go "Development options" (in the "More" tab (rigjt tab of settings menu)) ; be sure that "USB debugging" is checked.
And it works ! Eclipse can see your S4(or any other device) 4.2.2 !
I had this problem today and fixed it by rebooting the Tab2 while leaving it plugged into the laptop/eclipse
Check if you have installed android-adb-tools in Ubuntu. If you do, the adb tool may be old. Uninstall and make an alias to the latest adb tool you download with the ADB plugin. To check the adb version do "adb version" if it's 1.0.29 is the old, the latest and working for Android 4.2.2 is 1.0.31.
I made a lot of stuff until i realized this.
going to Developer Options and checking USB Debugging solved it for me
My solution used on cm10.1 nightly build on droid bionic, was after updating the newest usb drivers, using the Mass storage option (instead of the MTP option for USB computer connection), then unchecking and rechecking in developer options, "ADB over network" option. Then it did the RSA pop up dialog.
For me the best solution was:
Update the Android SDK via the SDK-Manager. Removing the '.android' folder in my usr directory ( Windows 7 ) and re-plugging the device back in. Worked flawlessly due to the ADB RSA key issue. I had an older version of ADB that I stashed into c:\windows\system32\ due to not wanting to install an entire freakin SDK when all I wanted was a command prompt. Good ol' Google, the new Microsoft.
You may use an old version of adb.exe. Update platform-tools.
You may have to set a new path to adb.exe as well.
In case it helps someone else arriving here, I had this problem with a ZTE phone.
I tried installing the driver based on the offical list here but in Device Manager the driver was marked as not installed correctly.
In the end I found the way to make this work was:
Press Menu Button
Choose "Connect to PC"
Choose "Default connect type"
Choose "Install Driver"
Plug in phone and on PC select option to install the driver
Then change "Default connect type" to "PC software"
After doing this I was able to do:
adb kill-server
adb start-server
adb devices
and view my device.
It's working on windows 8 using Android 4.4.2
Reset your phone,
go to setting->about phone-> seven time click on build number.
go to back and go to developer options check USB debugging.
go to windows 8 start menu click on profile picture and click change profile picture.
Select devices and on Download over metered connections.
Connect your phone via cable your PC and wait.
I'm trying to test an Android Application on my Galaxy Nexus (from Google). I use Windows 7 Home Premium 64 bit and Eclipse Java EE IDE for Web Developers.
My device doesn't show in Eclipse DDMS view. My device also doesn't show when I run adb devices in cmd.
I have USB debugging enabled.
When I try to install the USB driver as shown here I get a message that my device software is up to date.
I also tried killing the adb server and starting it again.
Give the Universal Naked Driver a try? Be sure to follow the steps in the forum post.
Nexus devices require the Google USB Drivers, you can get them through the SDK Manager.
If you have them installed and the device still is not detected try the following:
Use a different USB port (for me the USB 3.0 port is always making problems)
Restart the device and the computer
Restart ADB
Also take a look here, which explains how to install drivers for the Nexus S.
I had a similar problem. I could not get my device to show up in my Eclipse devices window. When I typed adb devices, no devices were discovered. Fortunately, I discovered this website. It basically had me install a generic driver for my Motorola (Android 2). It had other drivers for Samsung and other manufacturers. After the install, my Motorola phone became visible with ADB.
Here i saw various question related to "usb debugging" but answers not really helped me . can any one put light on this issue...
Your any help is appreciable
My problem solved after doing this
I updated usb driver :
i followed step written here under WINDOWS XP .
Device manager view
and ...
i reconnected my device to pc(winXP).
enabled usb debugging in device
usb debugging= set true in android manifest
In command prompt...
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
emulator-5554 device
e4567855.... device
For most android phones you will also need to install custom adb drivers in order to get it to work. Try installing any software suites that came with the phone as these may have the required drivers. Otherwise look on google for the adb drivers for the particular phone.
For the xperia in particular I was unable to get adb to find the phone until it was upgraded to 2.1 so you may need to do this if you are using an older android version.
If you run android at a command prompt it brings up the Android SDK Manager: under "Available Packages expand the Third party Add-Ons option. There looks to be a new Sony-Ericsson driver. Making sure you have that downloaded and then update the driver for your device from the downloaded driver file may solve your problem.