- 02-06-2011, 03:06 PM #3
- 02-06-2011, 03:21 PM #4
- 02-06-2011, 03:36 PM #5
Thanks, Tom S. At least I now know that the issue is likely with my computer, rather than with the Nook. I'll have to proceed with debugging now.
One question: What version of the SDK should I have installed?
I first installed the SDK back in October. It might have been version 7, or .7, back then? It worked fine at that time when I was rooting my Evo. When I started following the steps for getting ADB working on the NC, I saw that there was a newer version of the SDK available. v.9, maybe? Anyway, I was afraid that the older SDK version wouldn't be compatible with these newer Nook instructions, so I nuked my SDK folder and reinstalled the latest-greatest. I now wonder if this broke something.
It looks like I should get my NC rooted, and then try to get ADB Wireless working.
- 02-06-2011, 03:54 PM #7
- 11,773 Posts
- Stock for now
- 02-06-2011, 03:54 PM #8
- 5 Posts
don't know if it helps the conversation or not. I have an HTC evo and can use adb just fine. With the nook, adb will not see it. In win 7 device manager, it comes up as "Android Composite ADB interface" (and not the nookcolor that it was when it didn't have the driver installed. Maybe I need a different driver? I believe I used the nook usb files that someone had posted somewhere.) Any help appreciated, thanks! Sean
- 02-06-2011, 04:13 PM #9
- 5 Posts
I think I already tried the script that SeanFL mentions, but I will go check out that how-to thread that DroidXcon linked.
I actually made a bit more progress last night. I went back into Device Manager and found that USB Mass Storage entry that has the 2080 hardware ID. (If you delete it, and then scan for changes while the NC is connected, it recreates itself. So, that's definitely the NC.) This time, I tried updating the driver, and then went through the "Have Disk" procedure. I pointed it at the .inf file that was down in my SDK directories somewhere. It installed some more drivers, and now Device Manager shows an entry for "Android Composite ADB Interface" (or something to that effect). Also, when I do the "Eject Hardware" thing before unplugging the NC, Windows refers to it as a Nook, instead of just a generic mass storage device. So, that's progress. I think.
Unfortunately, ADB still doesn't list anything as a device. So, I'm still unable to do anything.
I'm running rooted Eclair 1.1.0 on the internal memory now, so I should be able to get Wireless ADB up and running there. I'm also playing with Honeycomb on the SD card. I'm stuck there, since I need ADB to work just to install the market or any app. But I'm sure a newer version of H will come along soon enough.
- 02-08-2011, 03:01 PM #11
- 02-09-2011, 09:00 PM #12
- 02-10-2011, 08:32 AM #13
- 20 Posts
Had the same problem. Followed all the directions multiple time, but adb would not see nooks serial numbers.
What works for me window7:
Disconnect Nook from usb, Go to device manager, Android Composite ADB interface, update driver, CLICK UNINSTALL DRIVER, plug nook back into usb, window7 searches and installs drivers, then I do this, per sticky;
Start > Run > cmd > Enter
This works for me every time. Don't know why.
- 02-16-2011, 08:14 PM #14