score:88

Accepted answer

had the same problem with an lg phone. rebooting it (phone) worked for me

score:0

i had this same issue, and i found this post, which fixed it for me.

just download http://dl.google.com/android/repository/platform-tools_r16.0.1-windows.zip unzip it and replace your "c:\program files (x86)\android\android-sdk\platform-tools" directory with that

credit goes to hack_on

here is his post that helped me: https://stackoverflow.com/a/15000565/342497

thanks! :-)

score:0

if you cannot select the ok button when choosing a device it probably means you cant do things like adb logcat either in my experience.

i usually kill adb from task manager and it starts working. i noticed adb kill-server only sometimes works, and that there are often multiple processes called adb running... not sure if this is a bug or by design.

score:0

step 1 : rigth click on the project => properties => android => select api level that your device suport.

step 2 : restart your phone

work for me ...

score:0

had the exact same problem. working fine for over two years then all of a sudden this error pops up. the fix for me was running the sdk manager.exe located here on my machine: c:\program files (x86)\android\android-sdk turns out i did not have the ability to run on the device with android operating system 4.2.2, only 4.0.2. after the sdk updated recognition worked perfectly. turns out my phones operating system was updated and i forgot to update the sdk.

score:0

had the same problem. turns out i had changed my usb connection mode from mtp to msc. changing it back to mtp solved the problem. thanx.

score:0

i used to debug w/o problems in my htc one x, i broke the screen and until they repair it i managed to get an htc one (m7 i think it's called internally).

i was unable to debug with this same problem, what actually happened is that besides having to follow a weird procedure to make debug options appear (press 7 times in the firmware version in "about" menu) the phone was showing a message asking me to verify that the computer trying to debug on it was authorized.

i had not seen this behavior before in any the the phones i have used, not sure if this is a new functionality or simply it was not enforced on the other ones.

score:0

it is because that you didn't allow your phone to be debug by this computer.

lock your screen, unplug and plug it then unlock screen click allow in the dialog.

score:0

kitkat 4.4.2+ users, try to switch from art to dalvik or from dalvik to art. :) solved mine.

score:0

i tried different drivers, turning usb debugging on/off, rebuilding program with lower level api, killing abd and restarting. then i saw post on here regarding cable swap. changed usb cable to samsung usb cable and worked immediately.

score:0

you need to authorize the device to that computer. i was connecting the phone to my centos vm and kept getting this. i had to kill the adb server and then run it as root user. then you will get the prompt on the phone to authorize machine.

score:0

for me it worked by disabling and enabling the usb-debugging option while adb is running. thanks for all the suggestions.

score:0

i had the same problem, restarting the pc worked for me.

score:0

(debugging was already on, usb cable plugged in, fresh restart)

solution: switched usb connection from media device (mtp) to camera (ptp). when i did this it the pc installed device drivers, then phone gave me my computer's fingerprint and had a dialog concerning allow device to use usb debugging. accept. device shows up in eclipse. all good.

(on samsung note ii api 19) note: it's good habit to always try toggling the usb mode. i don't think it's the act of designating camera (ptp), but the dialogs that are generated when doing so. also, i had my phone replaced: i remember seeing this dialog before but not on this phone. maybe there's an option somewhere to enable it per device?

score:0

i had the same problem. turns out my device was prompting a dialog asking me whether i should allow connecting to my laptop or not. after clicking yes this problem went away.

score:0

the problem for me turned out to be insufficient rights of adb server.

i run android studio through remote desktop (used laptop to connect to a local, more powerful computer). apparently i didn't have all the privileges when running through remote desktop.

after stopping adb server and restarting it with root privileges solved the problem.

sudo ./adb kill-server
sudo ./adb root

edit:

turns out i had to do this just the first time. since the first time i don't have to do this anymore.

score:1

do you have a driver for your phone installed on your computer, eclipse doesn't automaticly come with drivers for phones.

score:1

my problem solved by changing the cable. nothing else worked for me.

score:1

for this problem i had tried disconnecting/reconnecting the usb cable, toggling on/off the usb debugging and relaunching eclipse with no effect. trying a different android device showed exactly the same eclipse errors, with two entries marked 'offline' and after disconnecting the usb connection it still showed one entry while nothing was connected. my problem was solved by rebooting my computer and starting again. probably ending the adb.exe programme (answer 4) would have done it too in my case.

score:1

galaxy s5

i know this has been answered heaps of times already but if you have a galaxy s5 then the turn off and turn on of usb debugging works to resolve this problem

score:1

when the phone is plugged in and the eclipse window shows the "unknown" icon...on the phone turn off usb debugging then on again, it will then ask to allow that computer to connect, and you can say to always let it do so. then it comes up ok.

score:3

go to settings -> storage -> click on top right menu button -> usb computer connection-> check media device(mtp) is enable or not

score:5

the reason that my sch-i535 device was not being targeted... is because i had the device plugged into a usb 3.0 port. once i plugged it into a 2.0, everything began to work properly.

score:5

i tried these suggestions, but unfortunately, nothing worked.

what worked for me was:

  1. close eclipse
  2. end the adb.exe process (using windows task manager)
  3. restart eclipse (the device was now recognized in android device chooser)

score:6

also try this, on your phone:

  1. go to "usb computer connection"
  2. select connect as "media device (mtp)"

score:8

one simple trick works fine for me.

  1. disconnect device from pc
  2. tap revoke usb debugging authorization in phone setting
  3. reconnect device to pc
  4. tap ok for rsa authorization

score:9

check your device that

usb connected

and

usb debugging connected

or check the following

the solution was to create a udev rule for the device. see http://developer.android.com/guide/developing/device.html#setting-up for how to setup a udev rule for your specific vendor device.

with the rule in place. eclipse was able to launch and debug.

enter image description here

score:22

follow these steps, if your device is recognised but the eclipse is stating it as unknown:

->open cmd   
->go to the your android sdk directory --> go to platform-tools
->adb kill-server
->adb start-server

this will definitely solve your problem :)

if you already installed usb driver and still your device showing as unknown then follow this solution. i had same problem with my moto g and this solution works fine for me

score:65

one solution i am aware of is to just turn off and on usb debugging on your phone. it also happens to solve a bunch of other device-not-recognized kinds of problems.


Related Query

More Query from same tag