[Droid Incredible Android Development] jerrberr:
So far, I've been able to get adb in recovery 1 time, but didn't get superuser apk installed correctly, and cannot duplicate that one success to fix it.

I have the PNY 2gb microsd

Win 7 32bit

I have the first OTA update - current ver. is 1.22.605.2

I'm convinced that at least part of my problem is that I have a driver issue.

Here are the additions to android_winusb.inf that I've collected from various posts. These are also the changes that I added to the usb driver inf that I had installed when I went into recovery that 1 time:

;

;HTC Incredible

%SingleAdbInterface%	= USB_Install, USB\VID_0BB4&PID_0C9E

%CompositeAdbInterface%	= USB_Install, USB\VID_0BB4&PID_0C9E&MI_01

%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94

;

;HTC Incredible

%SingleAdbInterface%	= USB_Install, USB\VID_0BB4&PID_0FF9

%CompositeAdbInterface%	= USB_Install, USB\VID_0BB4&PID_0FF9&REV_0100

%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FF9

;

Here are my device ids when booting into various modes:

HTC Incredible in normal boot mode

USB\VID_0BB4&PID_0C9E&REV_0100&MI_01

USB\VID_0BB4&PID_0C9E&MI_01

HTC Incredible in normal boot mode USB COMPOSITE DEVICE

USB\VID_0C45&PID_6282&REV_0100

USB\VID_0C45&PID_6282

HTC Incredible in normal boot mode USB COMPOSITE DEVICE

USB\VID_0BB4&PID_0C9E&REV_0100

USB\VID_0BB4&PID_0C9E

HTC Incredible in normal boot mode MASS STORAGE

USB\VID_0BB4&PID_0C9E&REV_0100&MI_00

USB\VID_0BB4&PID_0C9E&MI_00

HTC Incredible in optical mouse/power bootloader mode

USB\VID_0BB4&PID_0FFF&REV_0100

USB\VID_0BB4&PID_0FFF

HTC Incredible in vol dwn/power bootloader mode

USB\VID_0BB4&PID_0C94&REV_0100

USB\VID_0BB4&PID_0C94

HTC Incredible in recovery mode

USB\VID_0BB4&PID_0FF9&REV_0100

USB\VID_0BB4&PID_0FF9

To view the device ids, boot your phone into whatever mode, plug the phone into usb, and view Device Manager. It doesn't matter if you have a driver installed or not. Right click the device (or installed driver), choose Properties, Details tab, and select Hardware IDs from the drop down. If you can't figure out if the device id is for the Android phone, choose Parent, Children, or Siblings. You'll see that some of them say AndroidPhone, while others such as USB\VID_0BB4&PID_0C9E have a string that corresponds to your individual device.

If I do not remove the following 2 files, the phone always shows up in Device Manager under Disk Drives as 2 drives, and in Universal Serial Bus Controllers as USB Mass Storage Device:

C:\Windows\inf\usbstor.inf

C:\Windows\inf\usbstor.PNF

I don't know if removing this file does anything or not:

C:\Windows\System32\drivers\USBSTOR.SYS

It seems like I need to have the correct driver installed for the correct device id, but I'm still experimenting.

I should mention that if I use:

;

;HTC Incredible

%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E

%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01

%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94

then I cannot install any driver for adb in recovery. Device Manager always says driver not found when browsing to the edited usb driver inf.

My question is:

Are some people able to install the drivers just fine using the following inf file settings and then get adb in recovery using these hardware ids:

;

;HTC Incredible

%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E

%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01

%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94

And are others having issues because when they are in recovery, their hardware id is:

;

;HTC Incredible

%SingleAdbInterface%	= USB_Install, USB\VID_0BB4&PID_0FF9

%CompositeAdbInterface%	= USB_Install, USB\VID_0BB4&PID_0FF9&REV_0100

%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FF9

Just to reiterate: I have to install drivers using %CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF9&REV_0100

The other 'normal' inf settings (%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01) that are on many, many posts will not allow me to install the usb driver.