[Nook Color General] edison:
It's working!

Unfortunately, I'm not 100% sure which step I did make it work, but I list everything I can recall.

I'll first answer a few of my own questions in the hopes it'll help others.

Output of `adb -d logcat`:

C:\>adb -d logcat > logcat.txt
_adb_connect: host:version
socket_loopback_client: could not connect to tcp:5037
_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: 4f4b4159 OKAY
Switch transport success
writex: 101 0x28dcd7 4: 30303265 002e
writex: 101 ok
writex: 101 0x28dde1 46: 7368656c6c3a6578706f727420414e44 shell:export AND
writex: 101 ok
readx: 101 0x28dc57 4
readx: 101 ok: 4f4b4159 OKAY

I had to redirect to the txt file because the screen was filled with a bunch of the following lines:

I/ActivityManager( 822): Starting activity: Intent { flg=0x10000000 cmp=android/com.android.internal.app.UMSServerActivity }

D/DeviceManagerBroadcastReceiver( 1011): action (android.intent.action.BATTERY_CHANGED)

D/WifiService( 822): ACTION_BATTERY_CHANGED pluggedType: 0

I've attached the usb_drivers I used, although I can't see any difference in them and the ones I had before.

Now for the stuff I did in-between my first post and this one (from memory).

I plugged the USB cable directly into the ports on my motherboard, instead of my PCI-X internal USB2.0 card. This was in response to suggestions on the other Win7 thread that you remove USB hubs from the mix. I'll try again with it plugged into the card later and report back.

I should note that in order to do this, I had to unplug my HP Deskjet which has a card reader slot. I had two USB Mass Storage and USB Composite devices listed in Device Manager prior to removing this - one each for the NC and the HP. After the removal, only a single set. Dunno if it made any difference, but it's worth mentioning. I'll try it with that plugged in, too, and report back.

I uninstalled the 'Android Composite ADB Interface' from under 'Android phone' from Device Manager, without checking the "Delete driver software" box. Obviously at this point I had the drivers installed. To be honest, I can't recall which of the native (Nook, USB Composite Device, USB Mass Storage Device) I updated the drivers on, but I *believe* it was the "Nook".

After the above step, I unplugged the USB cable and plugged it back in. This was based on several suggestions to that effect. I repeated these two steps multiple times but nothing ever showed up in `adb devices`, so I tried rebooting.

During this and all subsequent reboots, I hit F8 on startup and selected the "Disable Driver Signature Enforcement".

Still nothing after the reboot, so I uninstalled the 'USB Composite Devices'. Windows informed me a reboot was required. Whoah! That was new!

After the 2nd reboot, Windows automatically installed drivers (presumably for the device I had just removed), but again required a reboot.

Since the required rebooting behavior was so different than previous attempts (none of which asked to boot), I tried `adb devices` again.

Nothing.

Drat!

Then I checked the c:\Users\edison\.android\adb_usb.ini file that I created yesterday. All it had was this!

# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.

I *know* I had inserted a single '0x2080' in the file with no spaces or CRs. I had double-, triple- and quadruple-checked that stinkin' file during the last two days of frustration and it always existed and contained the right string. Something had to have changed it, but I'm not sure what it was. At one point, I had run the SDK Manager (from \androidsdk) and removed the non-2.1-related packages, including the "USB drivers package, revision 4". That's my best guess for the culprit.

So I added the "0x2080" to the adb_usb.ini file (after the 3 existing commented lines) and `adb-remount` gave me the sought-after "remount failed: No such file or directory", after which `adb devices` listed my NC!

Woo.

Hoo.

FWIW, I don't know that `adb remount`, specifically, is necessary. I ran `adb kill-server`, then `adb start-server` afterwards and it worked that way as well. I think the key is restarting the server once everything else is in place.

Since there are SO many others having this exact problem, can those of you who are and who try these steps, record what you do and report back?

My guess is that rebooting without the signed drivers req, removing the 'USB Composite Device' and the subsequent reboots/auto driver installs is what worked.

I do want to clarify that I know my NC was properly rooted as I was able to sideload apks from my laptop. This was only an ADB issue on my PC. IMO, the best way to confirm your NC is rooted is to boot with the nooter SD card installed. If you get a standard nook boot process, it's not rooted. If the device shows up in Windows (as *anything*), but the screen stays blank, you're rooted. I was pretty careful on my SD boots, as per the guides, to wait long enough for the root to "take" (2 full mins).

I sincerely hope this helps as I've spent all of last night and today working on this and I hope to save as many others from the same rage-inducing frustrations as possible.

Thanks to everyone who has put in the effort to make this possible, and everyone who has stuck by the community and taken the time to help the rest of us out!