The Vendor ID is 0x18D1 (Google).
\nThe Device ID is 0x4EE2.<\/p>\n
Then you edit the file c:\\windows\\inf\\wpdmtp.inf<\/p>\n
and edit this:<\/p>\n
[Generic.NTx86]\r\n%GenericMTP.DeviceDesc%=MTP, USB\\MS_COMP_MTP<\/pre>\nto append the line that makes this device a target of this inf.<\/p>\n
[Generic.NTx86]\r\n%GenericMTP.DeviceDesc%=MTP, USB\\MS_COMP_MTP\r\n%GenericMTP.DeviceDesc%=MTP, USB\\VID_18D1&PID_4EE2&MI_00<\/pre>\n(At first, I was not sure what the &MI=0 does, so\u00a0I just left it unmodified).\u00a0 At this point, the ‘Found New Hardware Wizard’ using Automatic settings will install it, and then you can copy files to and from the device’s Internal Storage. \u00a0An additional step is needed to set up for Android debugging (see below).<\/p>\n
I’ve had to edit the .INF before (for other devices) to add new lines to use the same drivers when the PCI Device ID, Subsystem Vendor ID, Subsystem Device ID, etc. change.<\/p>\n
Thanks to the post here for sending me in the right direction: https:\/\/groups.google.com\/forum\/#!topic\/andreasliebigapps\/FERbuAQfTnk<\/a><\/p>\n
Update on 12\/18:<\/p>\n
I noticed my Nexus 7 was still showing up with a yellow ! under Other in Device Manager, and I couldn’t see it when I ran “adb devices” from the command line, which is necessary to develop Android apps.\u00a0 The driver installation dialog was still coming up when I plugged it in, so I investigated this further.<\/p>\n
“&MI_” was referring to ‘Matching Device ID’ which you can see in Device Manager (Properties, Details tab).<\/p>\n
The missing driver was for the Android Composite ADB Interface.\u00a0 The driver zip has been removed from the Asus site, so I had to get it elsewhere (from the ASUS Nexus 7 Tablet ADB USB Driver 6.0 download page<\/a>).<\/p>\n
Later, I found this Google link, but didn’t try it: http:\/\/developer.android.com\/sdk\/win-usb.html#top<\/p>\n
The Google version (in source.catalog) is Rev. 8; the other one is Rev. 6, but they are binary exact\u00a0 driver files (only the date changed), with the only exception being the .inf and .cat files (which as I understand it, specify new compatible devices).<\/p>\n
Again, the .inf needed to first be edited to include this new device’s Device ID.\u00a0 In the file android_winusb.inf, add one line to the end of the [Google.NTx86] section, which pertains to 32-bit XP, for this Nexus 7:<\/p>\n
;Google Nexus 7
\n%SingleBootLoaderInterface% = USB_Install, USB\\VID_18D1&PID_4E40
\n%SingleAdbInterface%\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 = USB_Install, USB\\VID_18D1&PID_4E41
\n%CompositeAdbInterface%\u00a0\u00a0\u00a0\u00a0 = USB_Install, USB\\VID_18D1&PID_4E42
\n%CompositeAdbInterface%\u00a0\u00a0\u00a0\u00a0 = USB_Install, USB\\VID_18D1&PID_4E42&MI_01
\n%CompositeAdbInterface%\u00a0\u00a0\u00a0\u00a0 = USB_Install, USB\\VID_18D1&PID_4E44&MI_01
\n%CompositeAdbInterface%\u00a0\u00a0\u00a0\u00a0 = USB_Install, USB\\VID_18D1&PID_4EE2&MI_01<\/p>\nI am only installing XP 32-bit drivers (x86) and not 64-bit, so I did not modify the following section at all, although the general concept is the same.<\/p>\n
[Google.NTamd64]<\/p>\n
Prior to doing this, my Nexus 7 was in Device Manager (Other) with a yellow !<\/p>\n
Now it correctly appears as a Nexus 7 under Portable Devices, and also under Android Phone, as Android Composite ADB Interface. (Android Debug Bridge).\u00a0 Here’s a screenshot.<\/p>\n
![\"nexus](\"http:\/\/lkramer.net\/xblkx\/wp-content\/uploads\/2013\/12\/nexus-7-shoehorn-drivers-1-300x165.jpg\")
<\/a><\/p>\n