This post in the droidDorums.net forum helped me find the answer – but I thought it’d help some other poor droid developer if it was spelt out. This is what I had to do.
The problem is installing the Motorola USB debugging drivers on for a Droid X. This might apply to other droid phones. In particular: I had my phone working fine with the USB debugger and something changed – most likely the update to froyo – but I’m not 100% sure about that.
On to the solution:
- Find the file <eclipseDir>\usb_driver\android_winusb.inf
- In the INF file, look for lines identifying the phone like: USB\VID_22B8&PID_41DB – mine had 4 entries with this string. We’re going to search/replace this to your phone’s correct ID.
- To find your phones ID open the devices list like so:
- Click Start
- Right Click Computer
- Select Manage
- Select “Device Manager” from left menu
- Select Android Phone->Android Composite ADB Interface
- Right click and select Properties
- Choose the Details Tab
- From the Property Drop down, select “Hardware ID’s”
- Cut/paste the shorter string from the value’s section
- In your .INF file, do a search/replace with this new string – replace all instances of “USB\VID_22B8&PID_41DB’ with your device ID. Mine was “USB\VID_22B8&PID_4286&MI_01”
At this point the driver will proceed past the “Cannot install Driver.” You’ll be presented with a “Cannot verify this driver” message – but selecting “Install Anyway” will install and then you’ll be able to find your phone (provided it’s still plugged in) in the list of devices to debug/run your app on.
Some Meta info to help folks find this: Can’t Debug on Phone, Can’t Install ADB Driver, Phone not listed in Android Device Chooser