Add instructions for yet unsupported devices

[TheSchmidt]

I have tried to install the ADB driver in Windows for a Galaxy S2 with a "SlimKat" custom ROM on it. With the current version of the installer, the phone is not recognized, and the driver is not activated.

But I found a simple workaround to make Windows install the driver for the device nevertheless:

1. In the windows device information, look for the USB ids the phone uses. In my case there were the strings "USB\VID_18D1&PID_D002" and "USB\VID_18D1&PID_D002&REV_0226".
2. In the file android_winusb.inf from the installer, locate some lines that contains the same VID_* id in the section [ClockworkMod.NTx86] and/or [ClockworkMod.NTamd64].
   In my case I found these lines:
   %SamsungGalaxyNexusADBInterface% = USB_Install, USB\VID_18D1&PID_D001
   %SamsungGalaxyNexusADBInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0216
3. Duplicate these lines and change them to hold the ids determined in step 1:
   %SamsungGalaxyNexusADBInterface% = USB_Install, USB\VID_18D1&PID_D002
   %SamsungGalaxyNexusADBInterface% = USB_Install, USB\VID_18D1&PID_D002&REV_0226
4. Save the file (you may need to be admin) and install the driver. This worked for my phone.

Is it possible to add this workaround to the readme file?

[user3bss]

NextBook8 NX785QC8G

I modified the inf file with vid and pid from device manager like so
[ClockworkMod.NTamd64]

;Nook
%Nook% = USB_Install, USB\VID_2922&PID_30F3
%Nook% = USB_Install, USB\VID_2922&PID_30F3&MI_01

then used freehexeditorneo to edit androidwinusba64.cat
located the old nook values from inf file
;B & N Nook Color
%Nook% = USB_Install, USB\VID_2080&PID_0002
%Nook% = USB_Install, USB\VID_2080&PID_0002&MI_01
and updated them

then manually installed driver via deviceMgr->"OLD ADB device name"->updatedriversoftware->browse->letmepick->havedisk->

it complained about driver not being installed -> continue

and it installed as Nook android interface, however adb still doesn't recognize it

[TheSchmidt]

It does not seem possible to install the driver using the Windows device manager. But I had success simply starting the .exe from the UniversalAdbDriver installer package, after making the changes. This worked on two different machines.