[Captivate Q&A, Help & Troubleshooting] jahfry:
I'm running AOKP m6 with the default Glitch kernel v14. The problem I'm was having is no adb over USB.

My PC is running Windows 7 64-bit.

The problem lies in the device showing in Device Manager as "SGH-I897" instead of one of the more common identifiers (which obviously were used by other kernels and/or ROMs as other ones worked fine).

NOTE: unless you NEED adb over USB for something, it will probably just be easier for you to use adb over WIFI. The following isn't super-hard but if adb over WIFI works for you ... use it.

What I attempted to do to fix before doing the workaround (add "tested adb: FAIL" to each step below) ... try these, they may work in your case:

Updated to latest Android SDK, rebooted

"Uninstalled" device in Windows

Tried to "Update Driver Software" using Android SDK USB driver ... error: "Windows could not find driver software for your device"

Tried to "Update Driver Software" using Samsung Kies USB driver ... same error.

(over WIFI adb) ran `setprop persist.sys.usb.config mass_storage,adb` ... no luck, Mass Storage worked before and after, no adb

WORKAROUND:

Summary: you need to add your device string to the USB driver INF file. The following ATTEMPTS to be a full step-by-step to show those who haven't done this before what to do.

Go to your android-sdk folder (assuming you have installed the SDK -and- included the USB drivers ... if not ... that's your first step)

Open %ANDROID-SDK%\usb_driver\android_winusb.inf in your favorite text editor

add the following lines to BOTH sections [Google.NTx86] and [Google.NTamd64]

;Samsung Captivate with Glitch kernel

SGH-I897	= USB_Install, USB\VID_18D1&PID_4E22&REV_0231&MI_01

For OTHER phones with this same problem (skip if you are using a Captivate)

NOTE: For other phones or other ROMs ... try the steps I outline at the end of this post to see if they work BEFORE you hack the driver file. You may not have the same problem I've had here.

You will need to change the lines you add to the file above. To find the right string to add to your inf file:

find your Android device in Device Manager, it SHOULD have a yellow "disabled" triangle icon and is probably under "Other Devices".

right-click the entry for your phone and select "Properties"

go to the "Details" tab

change the "Property" from "Device Description" to "Hardware Ids"

right-click and "Copy" the first entry (should look similar to USB\VID_18D1&PID_4E22&REV_0231&MI_01)

Replace USB\VID_18D1&PID_4E22&REV_0231&MI_01 from my lines above with the value you copied in the previous step

Replace ;Samsung Captivate with Glitch kernel in my lines above with something that describes your device. KEEP the semi-colon at the front of the line.

find your Android device in Device Manager

right-click it and select "Uninstall"

(IF your computer tells you to reboot at this point ... yeah ... you gotta ... so just come back here when done and make sure you've done the "Uninstall" step)

in Device Manager, do "Action" > "Scan"

find your Android device again, this time likely under "Other devices"

right-click the device in Device Manager and select "Update Driver Software"

"Browse my computer for driver software"

click the "Browse" button and find %ANDROID-SDK%\usb_driver\

click "Next"

if it tells you it can't find a driver for your device, SOMETHING above went wrong OR this workaround can't solve your problem

if it tells you "Windows can't verify the publisher of this software" ... select ... "Install this driver software anyway"

you're basically done. Verify it worked by trying the command `adb devices`. Your device should now appear.

NOTES:

If you have this problem, both Recovery mode and normal mode will be unable to connect adb via USB

adb works over WiFi, but I have some scripts that are expecting a USB connection and don't behave well without USB connection for sensing when the device has rebooted

I had adb over USB running on the same phone using Doc's ICS, Stock 2.2 and Stock 2.3

adb recovery mode on my phone works with Corn kernel, so I really think this is an issue with Glitch kernel rather than AOKP