33

adb doesn't recognize my Nexus 10 on Windows 7. Here's what I've done:

  1. Installed the SDK and USB driver from Google. Windows 7 sees the tablet as an 'Android ADB Interface.'
  2. Put the tablet in developer mode by clicking on 'About tablet' and clicking the build number seven times
  3. Put the tablet in Camera (PTP) mode by going to Storage > USB Computer Connection.
  4. Started and restarted the tablet, my computer, and the adb server repeatedly.

None of this helps. When I run 'adb devices,' it gives me an empty list. What else can I do?

Thanks.

Manfred Moser
  • 29,539
  • 13
  • 92
  • 123
MatthewScarpino
  • 5,672
  • 5
  • 33
  • 47
  • 7
    Is your USB debugging mode **on**? – Shashank Kadne Nov 18 '12 at 06:42
  • 4
    AIUI, the Nexus 10 doesn't have a USB debugging mode. Instead, click 'About tablet' and click the build number seven times. – MatthewScarpino Nov 18 '12 at 14:43
  • 3
    My mistake. I didn't notice the new Developer options setting, so I didn't put the device in USB debugging mode. Sure enough, that does the trick. Thanks. – MatthewScarpino Nov 19 '12 at 01:36
  • 1
    You should mark an answer as correct please. For me the main issue was finding out about the "click build # 7 times" (are you kidding me?) and then setting developer mode options. – Mark Rausch May 28 '13 at 21:55
  • I had the same problem on Windows 7.
    This should help: http://stackoverflow.com/a/17186551/2207405
    – obi4niy Jun 19 '13 at 08:46
  • **JUST CLICKING 7 TIMES IS NOT ENOUGH!!!!** You need actually enable debugging in the developer menu which appears on the top level after you clicked 7 times. Also, if your can see device, but it's always `offline` --> check adb version! (should be 1.0.31 or newer) – Mike Keskinov Sep 10 '14 at 21:16

11 Answers11

62

I had the same problem on Windows 7.

First make sure the Nexus 10 developer mode and USB debugging is on ( if you dont see developer options, tap on About Settings -> Tablet -> Build Number a several time and it should activate developer mode)

Check if your ADB driver is in good shape by going into the Device Manager. If not un-install the ADB device manager and re-install it by pointing Windows to Android SDK location (It should pick up the driver automatically).

Once it is installed and still it does not work. Go into Settings-> Storage -> USB Computer Connection and select PTP option. Reconnect tablet to the USB.

Hope it helps!.

Peter Tran
  • 1,626
  • 1
  • 17
  • 26
Ramp
  • 1,772
  • 18
  • 24
  • 2
    I still have the issue with Nexus 10 driver on Windows 7. Doing all the above installed the driver but when type `adb devices` it doesn't recognize the device. Hence I still can't USB debug on the device. – Jonathan Feb 15 '13 at 18:29
  • +1 and I'll add I had problems because I had an old version of the USB driver. Reinstalling a newer one seemed to help. – parkerfath Mar 20 '13 at 02:24
  • Any idea why it has to be PTP Connection, this works for me but I would like to access storage one device which doesn't work in PTP. – draksia Mar 20 '13 at 19:45
  • check if Enable USB debugging is turned on after all the above steps – raj May 30 '13 at 15:51
  • 7
    It took me a while to find USB Computer Connection. You should add to your answer, that it can be found in the upper right Corner when you click on Storage. –  Jun 06 '13 at 14:19
  • 6
    This worked for me, also. I've had devices where I had to select MTP connection, or none of the MTP / PTP options, but sure enough, selecting PTP (Camera Mode) worked for me. And for those of who you might have difficulty finding this setting, it IS under Settings > Storage, but you have to select the ... menu option in the upper right corner to be able to select the USB Computer Connection option, and change those MTP / PTP settings! –  Aug 22 '13 at 00:09
  • For me PTP mode also worked, MTP didn't work at all. – AndyB Oct 10 '13 at 07:35
  • After activating “developer mode”, a reboot of the tablet was needed before I could find settings for USB debug mode. – Jesse Glick Jun 25 '14 at 02:20
27

I had some problems with this as well. I was on win 8.

  1. Install the SDK and USB driver from Google. USB driver is available in 'Android SDK Manager' in eclipse.
  2. Put the tablet in developer mode by clicking on 'About tablet' and clicking the build number seven times (crazy)
  3. Open Windows Device Manager and right click 'Android ADB Interface'
  4. Click Properties
  5. Driver Tab
  6. Update Driver
  7. Select 'Browse my computer for driver software' Select the 'sdk' folder under the location you installed your sdk in step 1 (e.g. D:\Dev\Software\adt-bundle-windows-x86_64-20130219\sdk)

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.

Lance Johnson
  • 1,226
  • 12
  • 8
  • works, i see it, but for some reason I get Failed to install appname.apk on device 'R23D1...': timeout! Launch canceled! – OWADVL Apr 02 '13 at 09:36
  • This worked for me on Windows 8 as well -- note that it may not say "Android ADB Interface", mine just said ADB interface under Device Manager>Portable Devices – brendan Apr 23 '13 at 20:23
  • Excellent, solved my problem on Windows 8 after a lot of frustration! Mine was reported as "Android Composite ADB Interface" – Tony Aug 09 '13 at 09:42
  • worked for me on Windows 8, one thing I had to 0) uninstall USB drivers and reinstall them before the other steps – petrumo Nov 06 '13 at 10:51
9

I started with the same problem as you, but managed to get my adb connection working on a Fedora 16 system as follows:

  1. Inserted 0x18d1 into adb_usb.ini (I do not bother with the device ID)

  2. 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"
    
  3. Pressed the settings->about->version number 7 times.

  4. Rebooted tablet and noticed that a new section is created in settings called "developer options".

  5. Enabled USB debugging in settings->about->developer options.

  6. On Fedora performed adb kill-server.

  7. On Fedora performed adb start-server.

  8. 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.

Pedro Romano
  • 10,973
  • 4
  • 46
  • 50
  • That is works, but is it necessary to edit adb_usb.ini and reboot device? It worked for me on gentoo without the steps. I did not 6-8 also. – Sergei Krivonos Jan 15 '14 at 02:16
4

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.

3

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

brendan
  • 1,705
  • 1
  • 18
  • 24
  • This app worked for me 2. SkipSoft.net http://www.skipsoft.net/?wpdmpro=wpdmpro&download=27 Thanx !!! – pyccki Mar 30 '14 at 18:08
2

Followed these instruction installed the correct ADB-drivers for me on Windows 7 http://developer.android.com/tools/extras/oem-usb.html

Alexander Pacha
  • 9,187
  • 3
  • 68
  • 108
  • This was the solution tht worked for me, initially failed, so I clicked on properties with tablet on dev mode on, went to driver tab, and clicked on update driver, selected the folder downloaded from the URL and it's working now. – Juan Carlos Alpizar Chinchilla Nov 17 '14 at 19:52
2

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.

enter image description here

On the picture: the red cable is bad, the black one is good.

Have fun,

-Stan

Michael Hoffmann
  • 2,411
  • 2
  • 24
  • 42
stanm
  • 3,201
  • 1
  • 27
  • 36
  • My problem was also due to the wrong (or possible faulty) USB cable. Possibly I was using a cable from another device! Switching to a different cable helped. – Joel Malone Aug 14 '13 at 05:14
1

All I had to do was restart the tablet.

Undo
  • 25,519
  • 37
  • 106
  • 129
RelativeGames
  • 1,593
  • 2
  • 18
  • 27
0

You should have done at least two things to get your device recognized on Linux:

  1. specify USB manufacturer and device ID in your hot-plug manager
  2. add an entry to ~/.android/adb_usb.ini using USB manuacturer ID

You may find manufacturer and device IDs with 'lsusb' command (that's LSUSB in lower case).

lenik
  • 23,228
  • 4
  • 34
  • 43
  • Thank you, but it's still not working. On Ubuntu 11, I added "18d1:4ee5" to ~/.android/adb_usb.ini and I used the same ID in 99-android.rules: – MatthewScarpino Nov 18 '12 at 13:53
  • Here's my first line of 99-android.rules: SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1:4ee5", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev" Any changes needed? – MatthewScarpino Nov 18 '12 at 14:11
  • @user934904 adb_rules says "# 1 USB VENDOR ID PER LINE.", you should not put device ID there, only the manufacturer ID. when you connect your tablet, do you see any activity in `dmesg` ? – lenik Nov 18 '12 at 22:40
0

As strange as it sounds, try switching the tablet between media device and camera mode. On the 10 ADB only works for me in camera mode, while on the 7 it only works in media device mode.

0

Try a different usb port. Worked for me on windows 8.1 with Nexus5/10.

free4ride
  • 1,613
  • 1
  • 18
  • 21