adb not detecting Nook Color

dewyatt · 2011-09-06 02:52:59

I know there's another thread about this but since it didn't go anywhere...
adb never detects my Nook Color. I had it working in Fedora 15 but switched to Arch and haven't been able to get it working.

$ lsusb
Bus 004 Device 007: ID 2080:0002 Barnes & Noble NOOKcolor

$ dmesg
[36858.396242] usb 4-4: new high speed USB device number 7 using ehci_hcd
[36858.539784] scsi14 : usb-storage 4-4:1.0
[36859.539248] scsi 14:0:0:0: Direct-Access B&N Ebook Disk 0101 PQ: 0 ANSI: 2
[36859.539472] sd 14:0:0:0: Attached scsi generic sg5 type 0
[36859.540895] scsi 14:0:0:1: Direct-Access B&N Ebook Disk 0101 PQ: 0 ANSI: 2
[36859.540983] sd 14:0:0:1: Attached scsi generic sg6 type 0
[36859.551005] sd 14:0:0:0: [sde] Attached SCSI removable disk
[36859.552254] sd 14:0:0:1: [sdf] Attached SCSI removable disk

I have installed android-sdk, android-sdk-platform-tools, and android-udev from AUR.
I have even tried manually installing the official sdk/tools.
I have also tried running everything as root:

$ sudo adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ sudo adb devices
List of devices attached
(nothing...)

The udev rules for my device, from the android-udev AUR package are:

# Nook
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666", GROUP="adbusers"

This matches up with the lsusb output above.
In fact, if I add SYMLINK+="android_adb" to the udev rules and replug the device, the node is created.

$ ls -l /dev/android_adb
lrwxrwxrwx 1 root root 15 Sep 5 22:42 /dev/android_adb -> bus/usb/004/007

I guess udev isn't the problem since it should still show up as root.
Also, I do have USB debugging enabled on my device (and it notifies me when connected "USB debugging connected").
I really don't know what else to try.

Last edited by dewyatt (2011-09-06 02:54:02)

ewaller · 2011-09-06 03:01:44

Do you still have access to the Fedora system. If so , boot it without the Nook attached, take note of the modules that are installed (lsmod), attach the Nook, and see if any modules have been added. If so, can you let us know what it is.

In addition, attach the Nook to your arch system and look at the last dozen or so lines from dmesg and see if there are any interesting messages therein.

dewyatt · 2011-09-06 03:36:50

ewaller wrote:

Do you still have access to the Fedora system. If so , boot it without the Nook attached, take note of the modules that are installed (lsmod), attach the Nook, and see if any modules have been added. If so, can you let us know what it is.
In addition, attach the Nook to your arch system and look at the last dozen or so lines from dmesg and see if there are any interesting messages therein.

Unfortunately, I replaced the Fedora install with Arch.

As for the dmesg output, I included that in the original post.
That is all of the dmesg output produced when the device is plugged in.
I cleared the dmesg with "dmesg -c" first and then plugged in the device and ran dmesg.

I may just reinstall Fedora alongside Arch and try to see if any new modules are loaded as you said.
This issue is the only thing I don't love about Arch.

ewaller · 2011-09-06 03:55:34

dewyatt wrote:

...As for the dmesg output, I included that in the original post...

Sometime I just don't pay attention -- my apologies.

I see that it did see two drives:

[36859.551005] sd 14:0:0:0: [sde] Attached SCSI removable disk
[36859.552254] sd 14:0:0:1: [sdf] Attached SCSI removable disk

Do /dev/sde and /dev/sdf not appear?
If they do, can you hand mount them?

ewaller · 2011-09-06 04:03:39

Oh, And you did check your Nook to ensure that it your Nook is set correctly. On my HTC Incredible:
Applications->Development->USB debugging is checked

dewyatt · 2011-09-06 04:04:12

ewaller wrote:

I see that it did see two drives:
[36859.551005] sd 14:0:0:0: [sde] Attached SCSI removable disk
[36859.552254] sd 14:0:0:1: [sdf] Attached SCSI removable disk
Do /dev/sde and /dev/sdf not appear?
If they do, can you hand mount them?

Yes, the device nodes appear and can be mounted, written/read, no issues there.
Unfortunately, mounting those doesn't help adb find the device (I did test it, as root).
As I understand it, adb doesn't care if the drives are mounted or not.

dewyatt · 2011-09-06 04:05:08

ewaller wrote:

Oh, And you did check your Nook to ensure that it your Nook is set correctly. On my HTC Incredible:
Applications->Development->USB debugging is checked

Yes, it's enabled and my Nook acknowledges the connection with a notification saying "USB debugging connected".

ewaller · 2011-09-06 04:13:01

On my system:

[ 2646.189831] usb 2-2: new high speed USB device number 3 using ehci_hcd
[ 2646.662228] usbcore: registered new interface driver uas
[ 2646.693028] Initializing USB Mass Storage driver...
[ 2646.693487] scsi6 : usb-storage 2-2:1.0
[ 2646.693664] usbcore: registered new interface driver usb-storage
[ 2646.693667] USB Mass Storage support registered.
[ 2647.696488] scsi 6:0:0:0: Direct-Access     HTC      Android Phone    0100 PQ: 0 ANSI: 2
[ 2647.696974] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 2647.701362] scsi 6:0:0:1: Direct-Access     HTC      Android Phone    0100 PQ: 0 ANSI: 2
[ 2647.701673] sd 6:0:0:1: Attached scsi generic sg3 type 0
[ 2647.706348] scsi 6:0:0:2: CD-ROM            HTC      Android Phone    0100 PQ: 0 ANSI: 2
[ 2647.713336] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[ 2647.718332] sr1: scsi3-mmc drive: 0x/0x caddy
[ 2647.718583] sr 6:0:0:2: Attached scsi CD-ROM sr1
[ 2647.718739] sr 6:0:0:2: Attached scsi generic sg4 type 5
[ 2647.724351] sd 6:0:0:1: [sdc] Attached SCSI removable disk
ewaller@odin:~ 1002 %

But it does not load any modules

dewyatt · 2011-09-06 04:18:30

Hmmm I just don't have a clue what's up.
I finished downloading Fedora so I'll go ahead and install that alongside Arch and get adb working in there.
Then I can see if any modules must be loaded, compare dmesg output, etc.
Other than that I'm out of ideas.

dewyatt · 2011-09-06 05:37:21

Well! Now it's not being detected in Fedora either!
So I guess this is not Arch-specific, something else must be going on.
I can think of two things that have changed since it last worked:
1) Firmware has been updated (I use CM7 nightly). I think others would be complaining if the firmware broke adb though.
2) USB cable replaced (using car-charger cable, since the original broke). I think the cables may be identical really but I'm not positive.

I'm going to update Fedora and maybe grep around in my logs.
I also might try downgrading to an older firmware.
If I still can't get it working, I'll probably head over to the xda-developers forum for help.

ewaller · 2011-09-06 05:52:24

Well, I feel a little better. I doubt it is the cable since you can mount the two drives that are instantiated when you connect it.

dewyatt · 2011-09-06 06:06:22

ewaller wrote:

Well, I feel a little better. I doubt it is the cable since you can mount the two drives that are instantiated when you connect it.

Well I wasn't thinking the cable is defective or anything.
It's just that the Nook Color USB cable is somewhat special, it has a few extra pins for high amp charging.
I was just wondering if those extra pins are also used for debugging but I don't know (I do think the car-charger version of the cable would have those pins too though).

Anyways, I did at least find that I can install the adbWireless app and use adb over my WiFi connection.
So if I have to do that, I can.

I'm still going to go ahead and start a thread over @ xda-developers to see what's up here.

kahlil88 · 2011-09-15 00:40:07

dewyatt wrote:

It's just that the Nook Color USB cable is somewhat special, it has a few extra pins for high amp charging.
I was just wondering if those extra pins are also used for debugging but I don't know (I do think the car-charger version of the cable would have those pins too though).

Interesting...I'm trying to help someone with a Nook Color but he didn't supply me with the special cable you speak of, so I've been using a standard one and noticed that it charges very slowly (says "not charging" but has definitely increased from 10-13% battery over maybe 2 hours). I'm also having trouble getting adb to see it -- tried adding the extra product-specific bits to udev rules after installing android-udev.

dxxvi · 2011-11-24 04:24:50

Hi Everybody,

Is anyone able to adb to the nookcolor from Arch? I can adb to my nookcolor if the OS is Ubuntu or LMDE, but like the OP, I replaced Ubuntu with LMDE and then replaced LMDE with Arch.

Thanks.

empthollow · 2011-11-24 04:52:20

Yes, I have done quite a bit of adb from arch. I use cm7 mainly. I had to edit a udev rule for permissions. Instructions from this site from this site http://nookdevs.com/NookColor_USB_ADB
One thing I did differently is that I installed adb in my home directory using a download link from the previous url. I did not install the aur packages.

Last edited by empthollow (2011-11-24 04:55:23)

dxxvi · 2011-11-25 00:10:47

empthollow wrote:

Yes, I have done quite a bit of adb from arch. I use cm7 mainly. I had to edit a udev rule for permissions. Instructions from this site from this site http://nookdevs.com/NookColor_USB_ADB
One thing I did differently is that I installed adb in my home directory using a download link from the previous url. I did not install the aur packages.

Could you please post your 5x-android.rules? Is it 50-android.rules or 51-android.rules?
Are you using Arch32 or Arch64?

Thank you.

PS: I just installed Linux Mint Debian XFCE in virtualbox hosted by Arch64 and was able to adb my nook color. So if anybody wants to see the difference in Arch64 and LMDE, please send me the commands to run and I'll post the results.

empthollow · 2011-11-26 04:45:15

I am using Arch 32. Here is my android rules file.

SUBSYSTEMS=="usb", ATTRS{idVendor}=="2080", MODE="0660", OWNER="empthollow"

SUBSYSTEMS=="usb", SYSFS{idVendor}=="0bb4", MODE="0666", OWNER="1000"

I have 2 rules files, I believe the first is for my nook. The other is for my hero. The 50 or 51 makes no difference. It indicates a processing order. They all get loaded.

dxxvi · 2011-11-26 11:17:51

empthollow wrote:

I am using Arch 32. Here is my android rules file.
SUBSYSTEMS=="usb", ATTRS{idVendor}=="2080", MODE="0660", OWNER="empthollow"
SUBSYSTEMS=="usb", SYSFS{idVendor}=="0bb4", MODE="0666", OWNER="1000"
I have 2 rules files, I believe the first is for my nook. The other is for my hero. The 50 or 51 makes no difference. It indicates a processing order. They all get loaded.

Do you know when to use ATTRS and when to use SYSFS? and when to use uid and when to use name for OWNER?

empthollow · 2011-11-27 06:07:51

I'm not sure about ATTRS vs SYSFS but I do know that if you do a 'lsusb' there anumbers that look something like

2080:3333

The 2080 corresponds to the ATTRS. I haven't plugged my hero in lately but the SYSFS may correspond to the 2nd set of digits. The instructions for the nook color said to use ATTRS. I don't believe uid vs username makes any difference. In my experience of linux config files those are interchangeable.

Jello_Raptor · 2011-12-28 12:50:45

I'm having the exact same issue, with both my nook color and my CM7 rooted touchpad. In fact everything is the exact same, excepting that i've installed my adk in /usr/bin/ and set my path to include the tools directory.

Arch Linux

#1 2011-09-06 02:52:59

adb not detecting Nook Color

#2 2011-09-06 03:01:44

Re: adb not detecting Nook Color

#3 2011-09-06 03:36:50

Re: adb not detecting Nook Color

#4 2011-09-06 03:55:34

Re: adb not detecting Nook Color

#5 2011-09-06 04:03:39

Re: adb not detecting Nook Color

#6 2011-09-06 04:04:12

Re: adb not detecting Nook Color

#7 2011-09-06 04:05:08

Re: adb not detecting Nook Color

#8 2011-09-06 04:13:01

Re: adb not detecting Nook Color

#9 2011-09-06 04:18:30

Re: adb not detecting Nook Color

#10 2011-09-06 05:37:21

Re: adb not detecting Nook Color

#11 2011-09-06 05:52:24

Re: adb not detecting Nook Color

#12 2011-09-06 06:06:22

Re: adb not detecting Nook Color

#13 2011-09-15 00:40:07

Re: adb not detecting Nook Color

#14 2011-11-24 04:24:50

Re: adb not detecting Nook Color

#15 2011-11-24 04:52:20

Re: adb not detecting Nook Color

#16 2011-11-25 00:10:47

Re: adb not detecting Nook Color

#17 2011-11-26 04:45:15

Re: adb not detecting Nook Color

#18 2011-11-26 11:17:51

Re: adb not detecting Nook Color

#19 2011-11-27 06:07:51

Re: adb not detecting Nook Color

#20 2011-12-28 12:50:45

Re: adb not detecting Nook Color

Board footer