Alan, You are right - the modem device has nothing to do with adb.
I think the Google disk drive device might be what you need, i.e. actually adb. No sense in changing lines starting with a semicolon in the .inf file, as those are just comments. Devices are matches based on their vendor and device ID's. Also, if your phone has multiple USB connection modes, you might want to try different ones. My Moto Milestone only shows up in adb when I select "Portal & Tools" connection mode in the phone (see my blog for screenshots, this is in case your phone has something similar). If phone settings are correct, you should get an adb device in the Windows device manager, with a yellow question mark at first. This is the device whose vendor and device ID's you should use in the .inf file. I wish there was an easier and more consistent way to enable adb in Windows..... -- Kostya Vasilyev -- http://kmansoft.wordpress.com 27.08.2010 0:54 пользователь "Alan" <[email protected]> написал: Hello Kostya, thank you for your reply. I knew I'd forgotten to mention something -- I had tried what you mentioned, and after seeing your post, I was encouraged to try again, but I still can't get it to work. Here's what I did (shortened version!) 1) Turned debugging on on the Ally 2) Plugged the USB in 3) Looked at device manager: when I plugged it in, these things appeared: a) Under "Disk drives": GOOGLE Mass storage USB device b) Under "Other devices:"LG Mobile USB Modem" There are 5 "LG Mobile USB Modem" entries. If I look at the first one, the Hardware Ids entry says: USB\VID_1004&PID_618&REV_0100&MI_00 USB\VID_1004&PID_618&MI_00 The next one is the same except it says "MI_01" and so on incremented for each of the entries. The "Device description" for each of the entries is "LG Mobile USB Modem". 4) I cut and pasted the entry for "; HTC Dream" (the first entry) and changed the entry to ; LG Ally %SingleAdbInterface% = USB_Install, USB\VID_1004&PID_618 %CompositeAdbInterface% = USB_Install, USB\VID_1004&PID_618&MI_00 5) That didn't work. I tried "LGE Ally", LG Mobile Ally", "LG Mobile USB Modem", "Ally", "LG", "LGE"... all to no avail 6) Iterating in with that I started changing the entry itself to match the others more by changing PID to "PID_0618". I tried putting the "REV_0100" in. 7) I tried many things like the above. Nothing worked. Windows always would come back and say (quickly), "Windows was unable to install your LG Mobile USB Modem". It seems like that's a clue, since I want ADB and not a modem, but I'm at a loss as to what to try next. The folder I always gave windows to look in was the "usb_driver" folder within my Android SDK installation. It could well be that I'm missing the particular combination of things that'll make it work, but I don't know what it is. Any further ideas would be greatly appreciated. Thank you again, Alan On Aug 26, 12:10 pm, Kostya Vasilyev <[email protected]> wrote: > Alan, > > Apparently all "adb"... -- You received this message because you are subscribed to the Google Groups "Android Developers" g... -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
