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
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
Hi Kostya, well, I checked the Google Mass Storage USB device by
mounting the phone as a disk -- it shows up as an L drive. I can
then successfully navigate folders on the phone from my PC. If I then
go to Device Manager and disable the Google Mass Storage device,
then the L drive disappears from
Success for this stage!!! My own fault!!! After checking the device
manager for the 1000th time, I noticed
that the PID of 618 was actually 618E. I changed that and changed
the MI_0x to match one of the LG Mobile USB Modem
entries and then told it to reload the driver pointed it to the
Android
Well, after 2 days off on, I am thrilling to Hello World on my LG
Ally.
After realizing that my problem with ADB was that I'd typed in the PID
wrong (see earlier post),
I still couldn't make adb see the device (adb devices).
But, the thread connected Motorola droid not recognized by adb did
5 matches
Mail list logo
