Windows XP, Xoom USB Debugging and driver problem
I've got Windows XP SP3 and already had WMP11. I installed 'Motorola_End_User_Driver_Installation_5.5.0_32bit .msi' (where does it actually install the drivers?) and when I first connected the Xoom it installed the drivers and the device appears as 'Portable Devices > MZ604' and I can browse its folder structure, but when I enable USB Debugging the problems begin.
Upon enabling USB Debugging and connecting the Xoom, 'Portable Devices > MZ604' disappears and 'Android USB Devices > Mot Composite ADB Interface' appears along with 'Other devices > MTP', but this section has got question marks on it and the 'Found new hardware wizard' pops up and I can't get any further.
I have tried the various suggestions I have seen on here, rebooting both devices, all my USB ports and get to the same dead end.
I'm trying to GED my UK Wi-Fi, but can't even get past the driver step. Does anybody have any ideas please?
04-23-2012 05:56 PM
I'd get USBDeview on your PC and uninstall all the Xoom usb drivers then plug the Xoom back in and see if it's recognized.
Ways to get Windows to recognize your Xoom
Last edited by ggrant3876; 04-23-2012 at 06:10 PM.
Note 3 - Jedi Elite V4.5
Nexus 4 - CyanMod 10.1.2
SGS-II - Rooted - Jedi Mind Trick VX3
Samsung Note II - Jedi Master 17
Motorola Xoom - WiFi - Rooted - EOS 4.2.1 Nightlies
I think I was being a drama llama! After I posted, I re-read some things and tried the 'adb devices' command again and it found the device.
What made me think something was wrong was that I didn't expect to see any question marked items in Device Manager, no matter what state the Xoom was in (non-debug or USB Debugging). Device Manager detected the Xoom based on whichever state it was connected:
Non-debug = 'Portable Devices > MZ604' and internal storage accessible in Windows Explorer
USB Debugging = 'Android USB Devices > Mot Composite ADB Interface' along with 'Other devices > MTP(?)' and 'adb devices' finds it
Just for information, I was still able to GED my UK Xoom in spite of the Xoom Device Manager behaviours I've described above.