Android SDK not recognizing debug-able device

Question

I'm new to Android development, and am attempting to run a test application on my actual device. I followed the instructions at http://developer.android.com/guide/developing/device.html (and related links), but the Android Debug Bridge (adb) doesn't recognize my connected device.

Some quick background info, I'm running WinXP, developing with Eclipse, with a Motorola Droid running Android 2.1 as my physical device.

An overview of the steps I've taken:

Installed the Android SDK, downloading all necessary packages.
Enabled USB Debugging on my device.
Connected Device via USB, installing the driver from the SDK folder.

I'll stop here (though I continued to setup my application to be debug-able in Eclipse), because I at this point I noticed a problem.

Running "sdk\tools\adb devices" at this point (at least, by my understanding), should list my device as connected. However, running this yields only:

List of devices attached

My device recognizes that it's connected to a computer in debug mode, and my computer recognizes the device. However, I can't seem to get the sdk to recognize it. I'll leave out the steps I used to setup Eclipse for debugging on a device, as it doesn't seem relevant to the problem. I'll include them if requested.

If anyone has any ideas, I'd greatly appreciate some assistance. Thanks in advance for your time.

maybe [this](http://stackoverflow.com/a/11931514/1369566) could help you? — cosmincalistru, Aug 13 '12 at 09:35

Neil Han · Accepted Answer · 2012-10-10T04:43:48.837

19

I am using HTC OneS. Eclipse on Ubuntu 12.04. I had the USB debugging enabled. But after plugged in, it doesn't let me deploy. It was recognized as a device: ????... no permissions

What solved my issue is the USB device permission. I found my answer here.

What I did:

$ sudo vi /etc/udev/rules.d/51-android.rules

I added this 2 lines in the rule file:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0cec", MODE="0666"
SUBSYSTEMS=="usb", SYSFS{product}=="Android Phone", MODE="0666"

My device USB vendor:product is "0bb4:0cec". To find it out, use command >lsusb. Then I unplug/plug my phone. It was recognized.

edited Oct 10 '12 at 04:43

answered Sep 29 '12 at 05:20

Neil Han

420
5
8

Wow thats great. Worked like a charm. But I have a confusion here. It was working fine for more than a year. Yesterday it stopped working. Now I tried this solution and working again. I didn't update any thing on my system at all, neither on my phone. Don't know what exactly happened. – jem May 23 '13 at 07:12

score 11 · Answer 2 · edited Jul 09 '13 at 08:18

11

When I had this issue, I figured out that my phone's USB connection was set to media sync mode. When I switched it to mass storage mode, the hello world program loaded right up. I did this by dragging down the USB icon in the top tool bar of the phone's home page.

edited Jul 09 '13 at 08:18

Jan Wrobel

6,969
3
37
53

answered Nov 27 '12 at 03:30

dan

111
1
2

1

Consider improving your answer by simply "Providing an answer", while it might be the right answer, it's better to keep it to the point for other users. – emartel Nov 27 '12 at 03:52
After a few days trying to figure what could be wrong, I was able to configure my LG in the XE10 device list just using your simple tip. – André Murta Mar 06 '16 at 10:55

score 9 · Answer 3 · answered Mar 07 '12 at 13:00

What usually works for me:

Unplug device
Run ./adb wait-for-device in terminal in your android-sdk platform-tools
Connect device
Turn on device

Every time one of my devices doesn't read, this seems to fix the problem.
An alternative is to repeat all those above steps, but don't disconnect the device (i.e. turn it off, run the command, turn it on).

If that doesn't work, another thing that I found that works for the older devices I use (2.1 update 1 and 2.3) is to unplug the usb, turn off usb debugging, turn back on usb debugging, and reconnect.

score 2 · Answer 4 · answered Nov 07 '12 at 01:04

2

I was trying to get this to work for an Acer A500 with Eclipse on Windows 8 Pro. I eventually found the solution via this link. I also had to follow the instructions at this link in order to allow installation of an unsigned driver in Windows 8.

answered Nov 07 '12 at 01:04

daveywc

3,136
7
45
58

score 1 · Answer 5 · edited May 23 '17 at 12:02

Assuming the correct driver has been installed successfully (No exclamation mark on the driver icon in device manager), check if the device vendor ID is listed in User\.android\adb_usb.ini.

You device vendor ID can be found at http://developer.android.com/tools/device.html

After adding the new vendor ID, reconnect the device and restart adb

For more details see this thread adb not finding my device / phone (MacOS X)

score 1 · Answer 6 · edited May 23 '17 at 12:34

1

I am using an HTC, so it may be different, but for me i have to sync the device with the pc before it will recognize the phone. When its ready, a notification pops saying that the device is attached for debugging.

Also, you need to mark your app as debuggable if you haven't already done that as explained here

edited May 23 '17 at 12:34

Community

1
1

answered Jun 05 '10 at 22:51

mtmurdock

12,756
21
65
108

The application is flagged as debugable. I've done all of that. – Kal Zekdor Jun 05 '10 at 22:53
sorry, i reread your question and edited my answer. maybe it will help – mtmurdock Jun 05 '10 at 22:55

score 0 · Answer 7 · answered Feb 06 '13 at 13:54

When adb stops recognizing my device on Windows, it usually gets fixed with the "adb kill-server / start-server" trick. But this time nothing seemed to get it back running, tried every answer on this thread multiple times (restarting, reconnecting, reinstalling, everything)... Then I tried connecting the device to another USB port and everything worked again.

score 0 · Answer 8 · answered Jul 09 '13 at 08:34

0

sometimes killing and restarting adb fix this:

in your console:

adb kill-server
adb start-server

(Don't forget to add the sdk's platform-tools folder in your PATH)

answered Jul 09 '13 at 08:34

VinceFR

2,551
1
21
27

score 0 · Answer 9 · answered Aug 03 '13 at 13:37

0

I followed the steps suggested by Neil Han, but adb still could not recognize my tablet (cheap chinese device - Freelander PD10).

what solved this problem for me was restarting adb as superuser:

adb kill-server
sudo adb start-server

answered Aug 03 '13 at 13:37

Olexiy

535
1
7
14

score 0 · Answer 10 · answered Aug 08 '13 at 18:26

0

Put the phone in mass storage mode. This took me a day and half.

answered Aug 08 '13 at 18:26

user1366372

23
4

score 0 · Answer 11 · answered Aug 18 '13 at 06:27

0

You may try to install the USB drivers for the devices from official Android page, those are:

answered Aug 18 '13 at 06:27

Nam G VU

33,193
69
233
372

the_prole · Answer 12 · 2014-02-19T12:36:40.010

0

Correct if I'm wrong, but cleaning the lint out of the USB port seems to work for some people. Here is a video on how to do it.

http://www.youtube.com/watch?v=R6p0Eg-yq3A

edit: Seems to have improved connection performance. Device is recognized with the -devices command if the cable it turned upwards and maintained in that position. Connection to the charger is working perfectly so far.

edited Feb 19 '14 at 12:36

answered Feb 19 '14 at 11:47

the_prole

8,275
16
78
163

score 0 · Answer 13 · answered Feb 23 '14 at 15:24

I have this problem with my Sony Experia L, the problem was my windows firewall, I just change some Inbound and Outbound setting ( Firewall advance setting ) for abd.exe ( Emulator ) and problem fixed. Do it and reset your emulator. Hope this help you.

score 0 · Answer 14 · answered Dec 16 '14 at 22:04

0

None of these solutions worked for me!

The device driver wasn't installing properly and i had to reboot my computer while holding F8 and turn off forced device signatures.

answered Dec 16 '14 at 22:04

Marcin D

918
7
14

score 0 · Answer 15 · edited May 23 '17 at 12:18

0

Kal I had the same situation some months ago, my device was recognized for my computer but adb doesn't recognize my device is connected, I had to update from the device manager.... hope it helps you!

adb driver isntalling error

edited May 23 '17 at 12:18

Community

1
1

answered Jun 05 '10 at 18:30

Jorgesys

124,308
23
334
268

Yes, yes I do. I did mention I followed the steps to make my application debug-able. However, that's not relevant, as the problem is the sdk is not detecting my device. It has nothing to do with a specific application. – Kal Zekdor Jun 05 '10 at 18:40

score 0 · Answer 16 · answered Jun 05 '10 at 19:27

0

Make sure you have Motorola's USB driver, as is described on this thread.

answered Jun 05 '10 at 19:27

CommonsWare

986,068
189
2,389
2,491

The usb driver is installed, yes. However, the device is not recognized by the adb. – Kal Zekdor Jun 05 '10 at 19:33
@Kal Zekdor : Perhaps the driver is not being recognized by XP -- with the device plugged in, follow the instructions on http://developer.android.com/sdk/win-usb.html to "Update an existing driver", and see if there is any indication of a problem. Perhaps your micro-USB cable is faulty, as I seem to recall running into that once. – CommonsWare Jun 05 '10 at 19:41
No, the driver is recognized, and windows recognizes the device properly. I'll try on another computer when I get the chance, but for now, I have no idea what the problem is. – Kal Zekdor Jun 05 '10 at 19:54
Having the same issue with the Droid 1 running CM7. – Artem Russakovskii Sep 30 '11 at 18:01
Nightlive's solution here worked for me: http://community.developer.motorola.com/t5/Android-App-Development-for/adb-devices-does-not-show-Droid/m-p/10524. – Artem Russakovskii Sep 30 '11 at 18:14

score 0 · Answer 17 · answered Jun 05 '10 at 23:03

0

Have you tried killing the adb process and starting it back up again? That's worked for me before.

answered Jun 05 '10 at 23:03

JRL

76,767
18
98
146

score 0 · Answer 18 · answered Aug 21 '15 at 15:11

0

type on Chrome:

chrome://inspect

All your connected devices will be listed. If debug session was not enabled, a confirmation dialog should appear in your device. Accept it.

It worked for me.

answered Aug 21 '15 at 15:11

Mario M.

416
2
10

score 0 · Answer 19 · answered Jan 17 '12 at 19:35

0

I just purchased a new android phone (LG) and was also having some difficulty. It seems that my phone would disable debugging on its own whenever I would plug it in to the USB port.

My solution is to plug the phone in, and THEN enable debugging.

answered Jan 17 '12 at 19:35

SMBiggs

11,034
6
68
83

Android SDK not recognizing debug-able device

19 Answers19

Linked