By David Hogue

2013-06-30 21:30:10 8 Comments

So I have a Nexus 7 that I'm trying to connect to my Windows computer for debugging over adb. Adb works fine with my phone, but when I plug in the tablet and run adb devices in Windows I get an empty list back:

C:\android\sdk\platform-tools> .\adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached


The tablet is running stock Android 4.2.2 build JDQ39. USB debugging is enabled, I did click on the build number 7 times to get the developer options enabled, and I've tried connecting both as a Media device (MTP) and as a Camera (PTP). The tablet is not rooted and I have not unlocked the bootloader.

The computer is running Windows 7 Enterprise SP1 x64. I have the latest adb version, 1.0.31. The SDK manager tells me I have SDK Tools rev 22.0.1 and SDK Platform-tools rev 17. I've tried using the Google generic usb driver version and 6.0 as well as the Asus usb_driver_r06 from Each driver I try does show the tablet as connected in device manager as either "Android Composite ADB Interface" or "Android ADB Interface"

If I plug the tablet in to my Macbook Pro and run adb devices, I get the the RSA fingerprint dialog as I would have expected to see in Windows:

Allow USB debugging?

Also if I start the tablet in fastboot by holding down the power and volume down buttons. I can see it with the fastboot utility:

C:\android\sdk\platform-tools> .\fastboot devices
015d262e32540802        fastboot

I am completely out of ideas here. Any and all off the wall suggestions would be welcome.


@Marc Wojcik 2013-11-15 16:08:51

I had to add the following: %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0228 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001

If you Go into device manager and open the properties for the Nexus 7 entry, click the details tab and drop the property section down to hardware IDs under value you will see the updated Hardware values. Take these values and add them to the Nexus 7 section of the android_winusb.inf file. Try re-running the driver install. It will complain that the driver is unsigned. Just ignore... ;)

If you are using Windows 8.1, you're going to have to reboot in Advanced Mode with Driver Signatures disablled for this to work. See this post:

@user43189 2013-10-12 20:31:48

Try to delete the key UpperFilters from


Helped me after 4 hours of trying to connect my Nexus 7 to win 7 64bit.

@David Hogue 2013-07-24 22:24:47

I finally found my problem. This might have been specific to my Windows machine, but I'm writing it down here in case someone else has the same problem.

Turns out I didn't have a usb.inf file in my C:\Windows\inf directory. Apparently some installers/uninstallers have been known to mess with that file. I found the tip in this thread while trying to figure out why my new mouse didn't work...

I copied the four files from C:\Windows\System32\DriverStore\FileRepository\usb.inf_amd64_neutral_153b489118ee37b8 over to C:\Windows\inf and re-installed the drivers and the security dialog popped right up on the tablet.

@rkagerer 2014-07-18 23:58:40

I too had similar symptoms that seemed to be caused by underlying issues in my USB stack. A complete uninstall and reinstall of my USB drivers didn't immediately solve it, but did cause an option similar to "Composite USB Device" to show up alongside "Google Nexus 7 ADB Interface" in the list of compatible drivers for my phone (under Update Driver, Browse my computer, Let me pick). In my case I had to first tell it to use the drivers for the Composite USB Device, then a new item showed up in device manager which I assigned the "Google Nexus 7 ADB Interface" driver. Hope this helps someone.

@aggieNick02 2015-02-16 22:28:31

Huge kudos to your answer David. I had the exact same symptoms. After about 5 hours of trying different things, I finally found your answer. I needed a different folder for my drivers which is an important bit in that thread you linked to. And after that, uninstall tablet driver, reinstall, and it just worked. I was on the edge of just wiping the OS and starting over.

@yohoho 2013-10-02 04:48:22

What fixed it for me was clicking on the "Connected as a media device" up at the top left corner, de-selecting Media Device (MTP) and then checking Camera (PTP). This essentially made it show up as a different kind of USB device with different options and allowed the process to work perfectly.

@David Hogue 2013-10-02 17:00:33

That does seem to be a common cause of the problem, but I did switch to PTP and still got nothing. What finally did work in my relatively unique case was replacing a corrupt usb.inf in Windows.

@ccallendar 2013-10-18 22:41:23

My nexus showed up in the list when I unchecked "Media Device (MTP)". As soon as I checked it (or PTP) then it disappeared from the list.

@lebress 2013-09-10 13:32:33

Got the same issue, and fixed it by updating the driver from the ASUS driver pack.

The issue is that this driver does not report properly the supported devices (at least mine were not listed)

My device is reported as a PID 4EE2 which is not part of the supported devices.

I had to add the following lines in the android_winusb.inf file (in the Google Nexus 7 Section)

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE2
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE2&MI_01

Device now appears properly in the Device List, and the Google Nexus 7 is part of the list of devices in ADB.

In addition, "tap" 7 times on the Settings|About Tablet|Build version to enable the USB Debugging.

@Steve Rukuts 2013-07-22 15:35:30

I have exactly the same device as you, down to the Android version and build number. I discovered that it was necessary to change my USB transfer mode.

You can do this on the Nexus 7 by going to Settings > Storage, clicking on the strange menu icon in the top right hand corner and selecting "USB computer connection". I then changed the storage mode to "Camera (PTP)", and it immediately prompted me with the permission dialog as shown in your post above. I was then able to deploy apps, debug, etc and it all worked.

Unfortunately I am very new to Android development so I am unable to say why this is the case. I am also unable to say why this worked on your Mac. Perhaps this is what must be done with this particular device on Windows. Anyway, I hope that you find this information useful.

@David Hogue 2013-07-22 20:17:53

Thank you for the suggestion. Unfortunately I had already tried both USB connection modes each driver I was able to find.

@Steve Rukuts 2013-07-23 08:40:16

David, it is possible that something I did previously fixed this. I also installed the drivers from the Android Package Manager as well as attempting to install the ASUS drivers:…

@Steve Rukuts 2013-07-23 08:50:47

Furthermore I note a difference: You're running Windows 7, and I'm running Windows 8. That shouldn't affect anything but perhaps you might try this on a Windows 8 machine.

@Tony D 2014-08-07 20:28:35

I followed Google's instruction to update the driver from Device Manager, but it wouldn't recognize the drivers. Once I changed my transfer mode on my Nexus 7, I repeated the process and voila it worked. Thanks!

Related Questions

Sponsored Content

4 Answered Questions

[SOLVED] How to install ADB drivers on Windows 10 (OPO)

5 Answered Questions

[SOLVED] How to fix "error: device not found" when I try to use ADB

2 Answered Questions

[SOLVED] ADB Device Unauthorized [Android 6.0.1 Nexus 6P]

1 Answered Questions

[SOLVED] How can I get back access to the media interface drivers?

1 Answered Questions

[SOLVED] ADB not seeing device after update

  • 2014-06-13 20:06:02
  • Will
  • 2568 View
  • 2 Score
  • 1 Answer
  • Tags:   adb

2 Answered Questions

[SOLVED] Problem connecting Nexus 7 as mass storage device on Windows 7

2 Answered Questions

Sponsored Content