Unfortunatly no one will help you here, they will just give you links to docs you have already read.
You are replying to a post from December 16th. Doubtful that the OP is still waiting on an answer.
Nice pot shot at people that do try to help, though. Either that or an unmet entitlement issue. No one in here is entitled to an answer for anything. Anything you or others provide in response to an inquiry is a gift, plain and simple. The answers might even be completely wrong or crap; but they are still a gift.
If the OP is still waiting, then they should know that all the detail that they showed (screenshots) are immaterial as they were taken with the device booted into the OS (composite ADB + MTP/PTP showing in Device Manager) instead of the mode that was having communication difficulties - fastboot/bootloader mode.
Immaterial information does not imply that the wrong driver is installed for a different operating mode for which similar information was not provided.
Most of the trouble in these types of post are due to the fact that the posters have no clue how
WINDOWS drivers are managed/installed/ etc. That has everything to do with WINDOWS and user skills, and almost nothing to do with the device on the other end of the cable.
Having said that, the principal reason there is confusion is due to the following set of circumstances:
- Casual Windows users are "accustomed to" doing a single install of a driver package when they buy a new device. Even when that device might have many logical endpoints across the USB bus. (Think of a multi-function printer - it might have an SD card slot on it, the printer, a scanner function, etc). When that multifunction behavior exists, usually the OEM provides a "driver installer" package which will actually install
multiple drivers, depending on the plurality of USB endpoints in the device.
- Unfortunately, if you carefully inspect any of these three driver bundles:
- Google (SDK) USB Driver
- Asus Nexus 7 USB Driver
- XDA "Universal Naked Driver"
you will find that (as shipped)
NONE OF THEM will work for all of the following modes of the Nexus 7:
- Fastboot mode
- ADB Mode, OS (Single or Composite)
- ADB Mode, Custom Recovery
- APX Mode
- PTP Mode*
- MTP Mode*
That's right. As shipped NONE OF THEM will handle
all of these cases. The "as shipped" part is a reference to the fact that a trivial edit of the "android_winusb.inf" file for any of them will allow a single driver to handle all fastboot and ADB modes.*
* The MTP/PTP drivers are meant to be handled by MS Windows generic class drivers; in the case of Windows XP you might need to install a Windows Media package to get the MTP driver - I'm not sure that it is part of Vanilla XP SP3
So, anyhow - people get confused because they "install the driver" for one mode (usually ADB), and then are surprised when they boot the device into a different mode (fastboot or ADB running under custom recovery) and surprise, surprise - their PC says "unknown device".
My advice?
Install the
Asus Nexus 7 Driver for everything but the Custom Recovery ADB mode, and then install the
Universal Naked Driver for that.
Or, prior to installation fix up the android_winusb.inf file that comes with the Asus driver so that it also supports
%GoogleNexus7ADBInterface% = USB_Install, USB\VID_18D1&PID_D001
%GoogleNexus7ADBInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_9999
Then a single driver will support everything but APX, MTP, and PTP. The latter two of which are provided by Mister$oftie, and the first of which is currently of unknown value to Nexus 7 rooters.
cheers
