WinXP detects your spanking new android phone as a USB mass storage device instead of a Composite ADB interface, no matter how you install the USB drivers from the android sdk. Here’s what you need to do.
- Right click My Computer, Hardware Tab, Windows Update, “Never search windows update for drivers”, OK.
- Enable debugging on your phone.
- Run USBDeview and remove all instances of Android Phone
- Unplug your phone, and plug it in again.
- When windows finally prompts for new drivers, direct them to your sdk directory containing android_usb.inf (Usually looks like android-sdk-windows-1.5_r2\usb_driver\x86)
If it works, this is what you ought to see:
If this doesn’t work, try to delete all the registry keys and values which contain “vid_0bb4&pid_0c02″, and start from step 1 again.
Good luck and hope this helps you.
4 Comments
Can you offer the same solution for Windos Vista users please.
Hi Paul,
To be perfectly honest, I’m not running vista on any of my computers, so I wouldn’t be able to test if any solution worked. Sorry.
Works on Windows 7 - thank you (especially for pointing to USBDeview)!
@Alexander: No problem, pleased to be of help to anyone : )
One Trackback/Pingback
[...] 1) Install the Android Developer Kit and get the driver installed for the ADB interface. If you have problems, here is a perfect article to solve the problems. [...]
Post a Comment