adb doesn\'t recognize my Nexus 10 on Windows 7. Here\'s what I\'ve done:
For those who are still stuck after following the other good answers, try a different USB port ...plus adb restarts just to make sure. That had me stalled for ages.
I had the same issue, but I downloaded the drivers from this application and it started working. I used this same technique on Windows 7 and Windows 8
Followed these instruction installed the correct ADB-drivers for me on Windows 7 http://developer.android.com/tools/extras/oem-usb.html
I started with the same problem as you, but managed to get my adb connection working on a Fedora 16 system as follows:
Inserted 0x18d1
into adb_usb.ini
(I do not bother with the device ID)
Inserted the following extra line into 99-android.rules
. It's not the quite the same as yours but I leave you to experiment.
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev", OWNER="johnp"
Pressed the settings->about->version
number 7 times.
Rebooted tablet and noticed that a new section is created in settings called "developer options".
Enabled USB debugging in settings->about->developer
options.
On Fedora performed adb kill-server
.
On Fedora performed adb start-server
.
On Fedora performed adb devices
.
I now see a new USB device in the list. When I go to my development environment (Eclipse) I see the device there as well.
I have been struggling with the same problem for a month. I tried other Nexus 10's, other ports, other computers ... everything. I thought I tried other USB cables too, but maybe not enough, as when a friend gave me yet another cable debugging worked.
It turns out the problem for me was that the EMI protection of the PC fires off when Nexus 10 is connected via a bad cable to a bad (front-case) port. It is a big tablet, so my guess is it draws a lot of current, and this combined with a badly shielded cable makes the PC freak out.
So my suggestion to people who couldn't solve the problem in any other way is: get a good USB cable (one where the connectors are bulky - means better shielding), rather than a cheap one.
On the picture: the red cable is bad, the black one is good.
Have fun,
-Stan
I had some problems with this as well. I was on win 8.
Not sure why windows didn't auto-detect it but it didn't. Could have been because google doesn't actually 'install' the driver into windows or perhaps it was because I had the HTC USB drivers installed because of my old phone.