[Solved] [Q] ADB over USB on 1.1

---

Has anyone gotten ADB over USB working with the NST 1.1 firmware? There seem to be guides all over the place, but they're either for the 1.0 firmware or for the original Nook, and every set of instructions I've followed doesn't do anything for me.

I'm trying to figure out why when I connect the NST to my computer via USB, adb can't see the device, no matter what I do. Looking at the ramdisk and the init.rc, it seems I have everything set up correctly. Of course, I could just use adb wireless that came with touchnooter, but I'd really like to get the USB version working again.

So, has anyone had any luck?

Not sure what ramdisk you're using but these are the ones used by most rooting methods around here.

The USB one works just fine, but I must say that getting the drivers set up on Windows 7 was a bit of a pita..
After trying several pre-packaged drivers I ended up editing the inf file in the android usb driver pack manually and got it working both at home and at work now, no problems.

Runs good on 1.1. here. I also tried a lot of drivers and the working one only after 3 installs. I think it was the driver of the forum here (but Im not sure anymore after that mess).

Originally Posted by Gogolo2

Runs good on 1.1. here. I also tried a lot of drivers and the working one only after 3 installs. I think it was the driver of the forum here (but Im not sure anymore after that mess).

Well, it's important to know that all those driver packages are actually based on the one you get with the Android SDK.

So people should save themselves the hassle and just get that one, and edit the android_winusb.inf manually.

Just add this to both the [Google.NTx86] and [Google.NTamd64] sections:

;B&N Nook Simple Touch
%SingleAdbInterface%        = USB_Install, USB\VID_2080&PID_0003
%CompositeAdbInterface%     = USB_Install, USB\VID_2080&PID_0003&MI_01

---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------

Ah, and ofc you need to add/edit %USER/.android/adb_usb.ini

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

Thanks for the replies folks. Good to know that those ramdisks work well with 1.1 (those are the ones I've been using too)...so I must be doing something wrong, or my computer must be set up incorrectly. I'm on a Mac, so AFAIK, I don't need to install any extra usb drivers or anything.

I can connect fine to my phone with adb over usb, so I'm not sure why the nook is failing.

Originally Posted by michaelwill

Thanks for the replies folks. Good to know that those ramdisks work well with 1.1 (those are the ones I've been using too)...so I must be doing something wrong, or my computer must be set up incorrectly. I'm on a Mac, so AFAIK, I don't need to install any extra usb drivers or anything.

I can connect fine to my phone with adb over usb, so I'm not sure why the nook is failing.

Well the ramdisks are nothing but a copy of the 1.1.0 ramdisk with adb enabled.

I have zero experience with OSx, but you might want to look at the Linux adb threads..

Yeah - there must be something wrong with my machine. I just reverted to the 1.0 version of the firmware, and went through the rooting procedure again, but my machine still can't see the device over ADB. I swear I had this working some weeks ago.

By the way, when you guys plug in the nook, and it shows the "USB mode" screen, do you first eject it from your PC, and then ADB works? Or does ADB work for you regardless of whether the NOOK drive is ejected or not?

Answering my own question here:

It turned out to be a fairly trivial solution - here's to not checking over your setup carefully enough.

It all came down to adding 0x2080 (the nook touch vendor id - which happens to be the same as the nook color vendor id - you can verify by using lsusb on linux) to the ~/.android/adb_usb.ini file, which basically just tells adb to look at additional vendor ids. This is stated clearly in the nook color docs, and I could have sworn that I did that hours ago, but when I re-looked at the file, I found mine was blank . As soon as I added 0x2080 back, everything started working perfectly.

Note, this is necessary for both mac and linux.

And, it doesn't matter if your NST is on the "Usb mode" screen or not; I got it to work both ways.