Database Users

[Q] Cannot get adb to connect to Nook Color

Ok I've researched this to death and tried in on both Windows 7 and osx 10.6.6 to attach using adb and install a couple of .apk's and the same thing happens on both platforms - NOTHING :-(.
You would think this would be pretty basic, but I am missing something somewhere.
Summary:
1. Am running the stock rooted b&n rom.
2. Can access both the internal and SD cards on the nook on both windoze and
osx. Eliminates cables, drivers etc...
3. Debug is selected in the nookstools settings
On both OSX and Win 7 installed the latest version of the Android SDK - both installs provided me with the platform-tools directory from which I will initiate all adb commands. So far so good...
on mac: ./adb devices returns:
$ ./adb kill-server
$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
$
As you can see I never get any device information returned, does not matter if Im on Windows or mac - same response.
Just for grins I downloaded the wireless app and tried to connect adb that way...no luck...
I could go into everything that i have tried over the last 24 hours...but that would also be pointless.
Bottom line...assuming this is something simpleI am just missing. Assuming since the symptoms are the same on both platforms that the issue lies on the nook but for the life of me I cannot find it.
Assuming if I cannot figure this out I will slowly go insane..my next step is to flash either froyo or honeycomb rom and see if this helps with the problems. Of course I MUST have the market available to me or I will not b able to load any .apk's.
Hpe Im in the right place. Any guidance is GREATLY appreciated.
Love this little Nook....BG

I know this will sound stupid, but I had this same problem and the only way I found to fix it is to adb while I have the superuser app running.
YMMV, but it solved that issue fo me.

Who Swami - It Worked
Swami,
I fall to my knees and bask in your knowledge: It WORKED!
I knew it was something simple, there is not a post on the entire Internet in any forum I have ever found (and I may have searched them all!) that mentions superuser needs to be running for adb to be able to communicate with the device. I wonder if this is a nook issue only. Will test on my wife's Epic this evening and post the results tonight.
My sanity now restored I bid you all a hearty SEE-Ya!
-BG

Omg I actually helped someone!
Glad it worked for ya I'm sure you felt the same relief I did when I finally stumbled across that fix.. I was pulling my hair out for hours LOL

Thanks Once More
As was I such a simple fix you would think I would have thought about permissions on the client side , such is life and tech thats why we all hang together.
Must say I was going to purchase the iPad 2 when it came out (NEVER buy 1st gen Apple) but now I'm not so sure...LOVING my Nook.

themirthfulswami said:
I know this will sound stupid, but I had this same problem and the only way I found to fix it is to adb while I have the superuser app running.
Click to expand...
Click to collapse
I'm not sure if this is related but I *think* that what made it work for me was to freshly enable the Debugging USB mode immediately before connecting the USB cable. Maybe that also triggered the Superuser app??? It's always the small things in life that make us smile

my problem is a little different.... I have sd cards with honeycomb (no market) and froyo (market and other apps). I can see the NC in adb with both, but honeycomb shows the device offline... and adb cannot talk to it. froyo show the device online and I can use adb. Both honeycomb and froyo show up in windows too.
I can't find anything that talks about getting the NC to show online to adb.

Same Problem
I have the same problem of trying to get my nook recognized. The only thing I can see different between my setup and the instructions on NookDevs was that they said I should see Android ADB Composite Interface on my Device Manager. Mine reads Android ADB Interface.
Tried the Superuser and the USB Debugging with no luck. Just really trying to get this set up so in case I need to factory reset. Because the 8x method manually is way too hard.

Have you guys read though this thread?
http://forum.xda-developers.com/showthread.php?t=910008&highlight=ADB
it worked for me like a charm.

that thread didnt work for me..
i tried lots more ways. just not able to get my nook (running honeycomb) online.
adb devices
just shows a serial code and says offline.
what do i do?
i want to install the G-apps.

I had intermittent ADB success with my Mac. After installing the ADB Wireless app there have been no problems.

Seaweedbrain said:
that thread didnt work for me..
i tried lots more ways. just not able to get my nook (running honeycomb) online.
adb devices
just shows a serial code and says offline.
what do i do?
i want to install the G-apps.
Click to expand...
Click to collapse
nvm
i connected my nook to the back of the cpu.
for some reason, it seemed to work fine.
it read the device as online.
got the g-apps

[Q] What's the micro usb port for?

Does anyone use the micro usb port? I have yet to find a use for it. I can't transfer files with it, charge with it nor are there any peripherals (that I know of) that can use it. I searched around but couldn't find much useful stuff on the port. All I found was this useless video:
**Ok I can't post the video because of more stupid forum rules but just go to youtube.com and append this after the url: /watch?v=1xBVu-IatDQ **
Anyway, if someone has ideas on how this port can be used I'm all ears... Thanks.
dq

It is a file transfer port. you plug a cable into it and into your PCs usb port. works like the ones on your phone.

Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq

don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
What OS are you using on your computer, and have you installed the drivers for it?

don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
Computer OS? i just plugged it into my Win7 system and it was there instantly. 3.0 shows up as a media device, which allows both the tablet and the computer to talk to the sdcard at the same time. So you won't see a mount prompt on the tablet. BTW my Incredible2 is running 2.3 and also lets me access the SD card on it and the computer at the same time.

I'm still using an old tiny xp and it worked fine for me just plugged it in and there it was

I tried Gentoo Linux and XP and neither worked. What drivers do I need to install?
I also have access to a Win7 system so I'll try that.
dq

Drivers from acer website.

I have adb installed should this not be enough?

You need none installed. ADB if its running in some form might be interfering. its just a basic driver in windows it uses.

I only run adb-server when I need it and not all the time. I thought that any needed drivers would have been installed when I installed adb.
For my Gentoo machine what should I do? It's not detected at all if I plug it in. My x10 mini and Nexus One are detected no problem and I can mount them and everything so what's up? Is there a kernel module that I need to build?
Thanks.
dq

I had to download these drivers for my xp netbook ,,
http://global-download.acer.com/GDF...A Tab&Step3=A500&OS=a05&LC=en&BC=Acer&SC=PA_6

I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium

Yes, well I only really use adb in the same capacity as what you describe-- to root a device. After that busybox can be installed and I can either ssh into the device (which I prefer) or use the terminal on the device itself.
But my problem is the detection of the device once it is plugged into my Linux box. I'm not sure if I need a special driver for that and I'd rather not aimlessly search through the kernel config in order to build one (I've done that before and it's painful!). It's good to know that one can mount it on an external device and still use it simultaneously though. That will save me time in trying to fiddle around with settings in the tablet itself...
dq

don quixada said:
I have adb installed should this not be enough?
Click to expand...
Click to collapse
If you are not able to transfer files Try enabling usb debugging before connecting to pc.

If the tab is not in the usb devices list and it doesn't show up as an unknown device, you might want to try another usb cable. Or another port if you have the Windows and Linux on the same machine and you are trying to connect on the same port.
Sent from my A500 using XDA Premium App

gradyzero said:
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Not nearly what I was saying. Not even close enough that a bomb would touch it.
Simple answer is my vista and win7 systems accessed the iconia as a media player device requiring no drivers as they are a common system driver. My only comment about ADB was that it might be interfering if it somehow was left running in the background.

I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.

sandiegoan said:
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
Click to expand...
Click to collapse
Sometimes mine gets a bit wonky as well. Every now and then, I'll plug it in, get the windows dialogue box asking me what I want to do. I open it up and the box is blank, no drives, nothing. Unplug it, wait a few seconds, pop it back in, and everything is OK. No rhyme or reason, and it doesn't happen all the time.

Quick trick for win7 .
Plug in the device.go into device manager delete its entry and the USB controller it resides on.unplug device.install driver from acer web site.then try the device again.
This works on several USB type issues
Good luck if you don't understand don't try

[Q] Rooted NST not recognized by PC

Apologies if this duplicates an old thread, but I couldn't find another one...
I rooted my Nook Simple Touch using Touchnooter 1.1, and now it can't be recognized by my PC. I can't copy files to it.
I bought several Google eBooks recently that I'd like to read on my NST, but they can't be loaded, as Adobe Digital Editions can't see the Nook (or doesn't recognize it). Google Books doesn't work, either. It just stays on a rotating 'loading' icon forever, never loading the book.
Any thoughts?

Not recognized? You mean on USB? No volumes mounted?
You can certainly transfer your books over ADB on WiFi if that's working.
If you can get to a shell on ADB try a "mount" command.
The last two lines should be like:
Code:
/dev/block//vold/179:6 /media vfat rw ...
/dev/block//vold/179:17 /sdcard vfat rw ...

DoomMunky said:
Apologies if this duplicates an old thread, but I couldn't find another one...
I rooted my Nook Simple Touch using Touchnooter 1.1, and now it can't be recognized by my PC. I can't copy files to it.
I bought several Google eBooks recently that I'd like to read on my NST, but they can't be loaded, as Adobe Digital Editions can't see the Nook (or doesn't recognize it). Google Books doesn't work, either. It just stays on a rotating 'loading' icon forever, never loading the book.
Any thoughts?
Click to expand...
Click to collapse
Using a root method that enables ADB over USB can mess up the drivers on Windows and make the Nook partition inaccessible.
There are two options:
1: Re-root with a ramdisk that enables ADB over WiFi (might not help)
2: Properly install Google drivers for ADB over USB (search this forum)

Dammit. It's so darn complicated. I was hoping to recommend this method to my non-geek friends so they could have simple little tablets too, but this all is just too much work for them (and for me). This is why people buy Apple.
If I go back to a rooted Nook (I returned to stock) I'll look into this stuff. Thanks for the tips, folks.

Oh! Check what driver you have on the Windows machine.
Under "Device Manager" if it shows Android anywhere then you have the Android ADB USB drivers loaded.
This would prevent the USB Mass Storage driver from being loaded.
Did you load the ADB USB drivers?

God, I have no idea if I loaded the ADB USB drivers. I just did the normal TouchNooter1.1 install, which includes basic Google Apps.
Then when my PC didn't recognize the rooted NST, I gave up and went back to stock! I'm not a true rooter.

@DoomMunky: Aw, don't get disheartened. Soon you'll be rolling your own kernels!
So you got your Nook to be recognized by your PC now?

Only by reverting to stock firmware. I'm running basic 1.1 now, no Android anything, and it's fine.
If I end up re-rooting in the future, what steps should I take to ensure my PC still allows simple book transfers to my Nook Simple Touch?

[Q] Rebooting on its own (Mirage ROM on SD)

I'm hoping there's something I can do to diagnose this problem further. I'm not exactly sure how to proceed.
Latest update was to Mirage's 7.2 RC1 (03-23) off of a SanDisk 32GB, which I tried after getting the same symptoms with the previous version (03-04, I believe).
The issue is that I can boot into Cyanogen Mirage, then after about 3 or 4 minutes, it restarts back to the Android w/Orbiting Arrow. If I let it go on, it will continue cycling like that until the end of time (or the battery runs out).
Like I said above, I'm unsure how to even diagnose this any further, or if there's any point to trying to fix it before I zap everything and start from scratch. Any help would be appreciated.

I don't know wether you are on windows, os x or linux. So you'll have figure out where to type the commands by yourself for a bit.
Download the Android SDK, install the "Android SDK Platform-tools".
Connect your Nook Color over USB. Now run "adb" (from platform-tools). If you see a pretty much empty text window with "#" on the last line you are now connected to the commandline of your Nook Color.
Type "cat /proc/last_kmsg" (without the ""), hit enter. If this says anything, the last couple of lines will give a hint what your Nook Color was doing just before it rebooted.

Right now, I'm using Windows 7 at work; I have access to both Windows and Ubuntu, though I prefer Ubuntu given the choice.
I've installed ADB, but when running the command "adb devices", the Nook Color isn't being recognized. Under the Device Manager, the Nook Color driver has a warning symbol on it, so I attempted to install the USB driver under android-sdk/extras/google/usb_driver; Windows doesn't want to recognize that as a valid driver, so I'm stuck.
I've got USB debugging enabled on the Nook, if that's a clue.

Follow-up:
Finally got a proper ADB driver for the Nook, and adb is recognizing the device.
Code:
List of devices attached
2010610044772004 device
However, when I try:
Code:
C:\Users\[redacted]>adb -d shell cat /proc/last_kmsg
/proc/last_kmsg: No such file or directory
Any pointers?

taserian said:
I'm hoping there's something I can do to diagnose this problem further. I'm not exactly sure how to proceed.
Latest update was to Mirage's 7.2 RC1 (03-23) off of a SanDisk 32GB, which I tried after getting the same symptoms with the previous version (03-04, I believe).
The issue is that I can boot into Cyanogen Mirage, then after about 3 or 4 minutes, it restarts back to the Android w/Orbiting Arrow. If I let it go on, it will continue cycling like that until the end of time (or the battery runs out).
Like I said above, I'm unsure how to even diagnose this any further, or if there's any point to trying to fix it before I zap everything and start from scratch. Any help would be appreciated.
Click to expand...
Click to collapse
I would suggest you reflashing it one more time and see the problem still persists.

Tried re-flashing it with Mirage 03-04, and no dice; it's not rebooting anymore, just staying in the Orbiting Arrow screen permanently. I think this chicken is cooked, and I'll have to install from scratch. Thanks anyway, Henk Poley and votinh!

Back at it again with the same symptoms, but this time I've pulled what I can from "adb logcat". The following files came from a reboot and a total freeze, where I had to do a hard reboot with the power button.
Mind you, these are long files, so they've been pastebinned (pastebin limits free users to 500K, so I had to split it into two) :
http://pastebin.com/t2ww7xFq (001)
http://pastebin.com/8n5xdKmF (002)
I'm not even sure what to look for, but if anyone can point me in the right direction, I'd appreciate it.

Cannot get ADB. Please help

So I just bought a brand new Nook HD+ from best buy. It is in shrink wrap so looks factory new.
I first turn it on and it gives me the select the lanuage and country page (No wifi selected). I do not proceed. Press volume down and tap lower left hand corner. If gves me the Enable ADB button. I do not press it yet. Instead I plug it into computer, which then puts it in MTp mode.
I unplugged cable and now press the Enable ADB button. I plugged it back in and same MTP mode.
I then decided to skip OBE. So I press lower volume button and then lower left screen followed by lower right screen. Then I press the Factory button. Then the Skip OBE option.
Now I am at home screen, I go to settings, then developers, and I confirm the ADB status. just to be sure, I uncheck ADb and then rechecked it. Plugged it back in and same result. It puts it in MTP mode.
I then confirm by going to Device Manager and see no entry for Android Composite device.
I do notice out of the box, it is 2.0.2 not 2.0.0? Does this mean it is a customer return? Even though it was shrink wrapped?

Need Windows Driver for Nook
I believe you need a windows driver for the Nook HD and HD+ on Windows. On Ubuntu, I just do "android update device && adb kill-server && adb start-server && adb devices"
I can't post links. google usb_driver_r04-windows

superflysocal said:
I do notice out of the box, it is 2.0.2 not 2.0.0? Does this mean it is a customer return? Even though it was shrink wrapped?
Click to expand...
Click to collapse
They could be working now on out of the box 2.0.2 now. Don't know.
You are not telling us much about your PC, which we need to know to help you. What version of Windows are you running? Have you got ADB running on any other devices?
No other new devices are showing? Did you follow the B&N trouble shooting guide section 4.6 which I reference in my HD+ tips thread linked in my signature.
Sent from my Nook HD+ Running CM10 on SD

I have win xp, but I have also tried it on win 7 machine and win mce2005 machine.
I am not sure if i ever had adb working for other devices but I think i have. Actually pretty sure I have.
I do know for absolutely sure I have had multiple android phones connected to this machine and in usb debugging mode, they show up as Android Composite Device.
I also have Android SDk installed on this machine (but not in the win 7 machine)

superflysocal said:
I have win xp, but I have also tried it on win 7 machine and win mce2005 machine.
I am not sure if i ever had adb working for other devices but I think i have. Actually pretty sure I have.
I do know for absolutely sure I have had multiple android phones connected to this machine and in usb debugging mode, they show up as Android Composite Device.
I also have Android SDk installed on this machine (but not in the win 7 machine)
Click to expand...
Click to collapse
Well, since you had other devices using ADB, then go to device manager and look under USB controllers. Uninstall any USB composite device there, especially any that has the device id under properties and details listing 2080 as part of the number. That will force the system to re-recognize and reinstall the right driver you can get from my HD+ tips thread.
Sent from my Nook HD+ Running CM10 on SD

There was a usb composite but it was for my wintv usb, I uninstalled it anyways. Nothing else, still not doing anything. Any chance this is a new hardware version that has this locked down?
It did come with 2.0.2 instead of 2.0.0

I don't see a reason for a hardware revision, and there is no reason for 2.0.2 instead of 2.0.0 other than bug fix since you can still root with 2.0.0 - 2.0.4. The inability to ADB is on your part. Seriously I don't see why would B&N lock down people ability to ADB since it's a requirement for people to develop for Nook platform. It's not like B&N will make 2 different versions of each device, one for developers and the other for consumers. I can still see B&N may lock down ability to root with current method on future revision (say 2.0.5+) but as of now it's open. ADB will never be lock. I think the fact that ADB for Nook devices are hard to get to will not only deter people from root but people to develop for the platform as well. Personally I think it's a bad choice on B&N part to have it hard for people to ADB.

I do agree with you, but I am open to any suggestion.
I have a win7 64-bit laptop that I can use. Should I try that? I thought win xp machine would be easier.
Should I reset nook hd+ and NOT skip OOBE?
I was hoping to avoid wifi so that I don't update to 2.0.4 which was reported to have corrupt microsd card writes.

superflysocal said:
I do agree with you, but I am open to any suggestion.
I have a win7 64-bit laptop that I can use. Should I try that? I thought win xp machine would be easier.
Should I reset nook hd+ and NOT skip OOBE?
I was hoping to avoid wifi so that I don't update to 2.0.4 which was reported to have corrupt microsd card writes.
Click to expand...
Click to collapse
I just bought a HD+ from Walmart. It was 2.0.2 out of the box and I was able to root the device successfully after OOBE was completed. I don't remember if the device upgraded itself to 2.0.4, I'll check later. I did the all in one root process on a Win7 64bit lappy so try it and see if it works.
IMO the person who posted about the sdcard file corruption has hardware issues but who knows? No one else is reporting having this issue afaik.

There are people that report a success ADB driver install on win7 64bits via my method. Check the tips thread.

someone0,
just curious, what firmware are you on? 2.0.4? Are you having any sd card write issues?

So I reset the nook hd+, then registered (did not skip oobe) and it updated 2.0.4, but still same issue. It will not recognize device as Android Composite USB device, only as MTP media device.
i am beginning to think I got defective unit.

superflysocal said:
So I reset the nook hd+, then registered (did not skip oobe) and it updated 2.0.4, but still same issue. It will not recognize device as Android Composite USB device, only as MTP media device.
i am beginning to think I got defective unit.
Click to expand...
Click to collapse
No, I don't think so. If you read through the posts on the other threads you will see about half the users have a very difficult time making adb work. And it is never anything wrong with the HD, it is always something with your PC. There are so many different setups for windows that it is very hard to advise people. Just keep trying things others have. I still have problems and I have been doing it for weeks and each time it fails it is a different thing. The only thing I can advise you is to keep uninstalling things because something that is installed is blocking your PC from recognizing the new device. I would uninstall any device under portable devices, other, android phone and any device under USB controllers that has 2080 as part of the device id.

leapinlar said:
No, I don't think so. If you read through the posts on the other threads you will see about half the users have a very difficult time making adb work. And it is never anything wrong with the HD, it is always something with your PC. There are so many different setups for windows that it is very hard to advise people. Just keep trying things others have. I still have problems and I have been doing it for weeks and each time it fails it is a different thing. The only thing I can advise you is to keep uninstalling things because something that is installed is blocking your PC from recognizing the new device. I would uninstall any device under portable devices, other, android phone and any device under USB controllers that has 2080 as part of the device id.
Click to expand...
Click to collapse
Oh you are so rght. I never did figure out what is blocking it, too impatient to uninstall stuff.
BUT, I did find an old seldom used laptop with win 7 32-bit. When plugged in it gave me error that drivers could not be installed!. Went to device manager, found the device and updated driver. Adb achieved and all in one root done.

No, I'm on 2.0.0