[Nook Color General] edison:
Since there seems to be a number of people fighting to get ADB working with the NC on Win7-64 machines, I thought I'd start a dedicated thread to get to the bottom of this issue.

In my case, ADB is working from my laptop but not my desktop. At various stages I have different devices, including an "Android Composite ADB Interface" and and "Android ADB Interface". At no point does `adb devices` return anything.

Here's some bits that will hopefully be helpful in troubleshooting.

Without the drivers installed (more accurately, with them uninstalled and deleted), I have the following devices in Device Manager:

Other devices -> Nook
[INDENT]Hardware Ids:
USB\VID_2080&PID_0002&REV_0216&MI_01
USB\VID_2080&PID_0002&MI_01[/INDENT]
Universal Serial Bus controllers -> USB Composite Device
[INDENT]Hardware Ids:
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002[/INDENT]
Universal Serial Bus controllers -> USB Mass Storage Device
[INDENT]Hardware Ids:
USB\VID_2080&PID_0002&REV_0216&MI_00
USB\VID_2080&PID_0002&MI_00[/INDENT]

Could someone with a working ADB under Win7-64 uninstall their drivers and post the above information? If it's the same, could you zip your usb_drivers dir and upload that?

ADB version from SDKr08:

C:\>adb version
Android Debug Bridge version 1.0.26

ADB logcat with debug all:

C:\>set ADB_TRACE=all

C:\>adb -d logcat
_adb_connect: host:version
socket_loopback_client: could not connect to tcp:5037
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
_adb_connect: shell:export ANDROID_LOG_TAGS="" ; exec logcat
socket_loopback_client: port 5037 type tcp => fd 101
writex: 101 0x28dcd2 4: 30303132 0012
writex: 101 ok
writex: 101 0x28dc92 18: 686f73743a7472616e73706f72742d75 host:transport-u
writex: 101 ok
Switch transport in progress
readx: 101 0x28dc57 4
readx: 101 ok: 4641494c FAIL
readx: 101 0x28dc57 4
readx: 101 ok: 30303130 0010
readx: 101 0x4221a0 16
readx: 101 ok: 646576696365206e6f7420666f756e64 device not found
adb_close: 101(lo-client:5037)
Switch transport failed
- waiting for device -
_adb_connect: host:version
socket_loopback_client: port 5037 type tcp => fd 102
writex: 102 0x28baf7 4: 30303063 000c
writex: 102 ok
writex: 102 0x41d3ed 12: 686f73743a76657273696f6e host:version
writex: 102 ok
readx: 102 0x28ba77 4
readx: 102 ok: 4f4b4159 OKAY
readx: 102 0x28bb34 4
readx: 102 ok: 30303034 0004
readx: 102 0x28bb34 4
readx: 102 ok: 30303161 001a
adb_close: 102(lo-client:5037)
_adb_connect: host-usb:wait-for-usb
socket_loopback_client: port 5037 type tcp => fd 103
writex: 103 0x28baf7 4: 30303135 0015
writex: 103 ok
writex: 103 0x28cc01 21: 686f73742d7573623a776169742d666f host-usb:wait-fo
writex: 103 ok
readx: 103 0x28ba77 4
readx: 103 ok: 4f4b4159 OKAY
readx: 103 0x28bb97 4

Again, if we can get a working environment's output, that would be great.

Those who are having the same problem, post the results of the above command here, too. Don't forget the `set ADB_TRACE=all`. We can see if there's any differences in the behavior in the non-working envs.

I should note that some people have been successful by removing and deleting the drivers, un/re-plugging the NC and letting Windows auto-install the drivers (if I'm understanding the process).