yashsingh1/xdaforums huggingface dataset:
[Nook Color Q&A, Help & Troubleshooting] jsmith.nook:
In step 8 you probably won't have to point the driver installer wizard to your usb_drivers folder. In every instance I've had to or I've heard of others doing this Windows finds the drivers on its own even after the uninstall.

Uninstall the "USB Composite ADB Device" under "Android Phone"
[Nook Color Q&A, Help & Troubleshooting] pandarus:
It seems that I got the things done.

There are several misleading information in here: nookdevs.com/NookColor_USB_ADB

For windows in step 7, it says that:

Now, verify that everything worked:

Start > run > cmd

cd android-sdk-windows\tools -------sometimes if you input cmd and enter, it does come up with C:\users\XXX(your account name)

in this case, you need to type cd\ to return to C: then you could type cd android-sdk-windows\tools

I also find that the adb.exe is located in platform-tools folder instead of tools. You can check the android-sdk_r08-windows.zip file. So, in that case, you should type cd android-sdk-windows\platform-tools, right?

adb kill-server

adb devices

I hope it will helps.
[Nook Color Q&A, Help & Troubleshooting] Tapiozona:
Awesome, this worked. Only change I had to make to your instructions was point out where the driver was. Thanks a ton for the help.
[Nook Color Q&A, Help & Troubleshooting] califrag:
Thanks I tried to clean up the walkthrough a little bit but didn't touch that part at all. I will fix it up to add the extra steps to get to the correct directory
[Nook Color Q&A, Help & Troubleshooting] discourse:
I've run into an error while trying to root my NC. I'm doing it on a Windows7 32bit machine

When I reach this step " A new window will appear. In the Copy manufacturers files from: window enter c:\androidsdk\usbdrivers" it says that the folder I specified doesn't contain driver software.

I followed the USB ADB instruction to the letter quite a few times but still no luck.

Does anyone know what could be wrong?
[Nook Color Q&A, Help & Troubleshooting] califrag:
try again, the folder wasn't correct but I fixed it. it should be C:\android-sdk-windows\usb_driver
[Nook Color Q&A, Help & Troubleshooting] discourse:
Giving thanks is the way it should have worked on this forum since day one.

Thank! :D

During the next step though, after start run cmd and cd android-sdk-windows\tools

I get: The system cannot find the path specified.

The device is showing up in Device Manager as an Android phone Android ADB interface.
[Nook Color Q&A, Help & Troubleshooting] califrag:
refresh your nook portal page, i updated all the steps so it should work without any issues. the previous version had incorrect paths for that step
[Nook Color Q&A, Help & Troubleshooting] discourse:
cd\ works but the next command cd android-sdk-windows\platform-tools doesn't. I get "The system cannot find the path specified". I know the path exists because I can see it.

I entered cd \Program Files\Android\android-sdk-windows\platform-tools instead and it worked.

After # adb kill-server and # adb devices, I get:

* daemon not running. starting it now on port 5037 * * daemon started successfully * List of devices attached

[blank]

Does this mean my device was not found?
[Nook Color Q&A, Help & Troubleshooting] pandarus:
I finished the root procedures and can use adb to install apk files without any problem.

But when I tried to install .apk files directly use astro file manager or other "black market', there is a message pop off, saying that" installation of download apks is not supported'.

Anyone knows what is the problem? Thanks.

Update: I searched the forum and figured out the problem!
[Nook Color Q&A, Help & Troubleshooting] califrag:
:confused: that doesn't look like the right folder... your Android SDK should have been installed into c:\android-sdk-windows. If you unzip the SDK zip file directly to your C:\ folder it should put everything in the right place.
[Nook Color Q&A, Help & Troubleshooting] discourse:
It may not have been done the right way but is it properly rooted? It shows us as Android phone - Android ADB Interface in Device Manager. Would I be able to install apps on it yet?
[Nook Color Q&A, Help & Troubleshooting] califrag:
nah not until it shows up in devices. double check your adb_usb file.. if that isnt in the right folder either than you will have problems.
[Nook Color Q&A, Help & Troubleshooting] discourse:
I officially suck at rooting. I've followed all instructions several times but after "adb devices", my device serial number still doesn't show up in terminal.:mad:
[Nook Color Q&A, Help & Troubleshooting] Tapiozona:
Sounds like you're having the exact same problems I was having.

I followed these instructions and then everything worked perfectly...

1. Plug in your NC

2. Go into Windows Device Manager

3. Right-click on the ADB interface thingie (the one under "Android Phone")

4. Select UNINSTALL

5. Check "Delete the driver software for this device"

6. Click okay.

7. Unplug the Nook, Replug it in and wait about a minute for Windows to recognize everything. Cancel out of the driver part when it prompts you.

8. In Device Manager, right click on the nook and follow the steps to adding the drivers you did previously

9. Try ADB again

9a. adb kill-server

9b. adb devices

I had to do this on one Win7 box to get it to work. I've heard from others that this got their NC working with ADB under Win7.

Not sure why this worked but after I uninstalled the drivers and reinstalled them, it recognized my nook through adb. I also copied the entire contents of the "Tools" folder into C:\windows\System32\ (dont copy the actual tools folder, just the contents). This allowed me to "adb" from any directory I was in when I was at a command prompt.
[Nook Color Q&A, Help & Troubleshooting] discourse:
That worked!!! This should be added to the tutorial for people who run into the same problem.
[Nook Color Q&A, Help & Troubleshooting] discourse:
never mind :)
[Nook Color Q&A, Help & Troubleshooting] Novarider:
I'm considering getting a NC can someone tell me is it rootable? If so can someone link me to the root tutorial please.
[Nook Color Q&A, Help & Troubleshooting] rbebber:
r u serious?
[Nook Color Q&A, Help & Troubleshooting] plariers:
I hope this post is a joke
[Nook Color Q&A, Help & Troubleshooting] Novarider:
Did I miss it or something? Its not in the first 4 pages and I don't want to read 122 pages worth of posts. I tried searching but didn't find it.
[Nook Color Q&A, Help & Troubleshooting] moovius:
In his defense, there should be a FAQ or similar stickied in this forum. If someone is just now coming to these threads, they will have a harder time finding the right info.
[Nook Color Q&A, Help & Troubleshooting] Novarider:
Thank you. Today is my first day reading the nook forums. I'm not new to this website or android I have a rooted htc evo. So I'm not a complete noob
[Nook Color Q&A, Help & Troubleshooting] Malk3rs:
Nova: Google nookdevs they have a website that has a step by step guide for windows linux and mac that is a product of this monstrous thread and work done apart from xda. I know this thread is a beast.
[Nook Color Q&A, Help & Troubleshooting] plariers:
I'll write it if it's needed
[Nook Color Q&A, Help & Troubleshooting] whgarner:
needs a rom bible post

needs a rom bible post even though no roms yet, it should be flag by the administrator so it does not end up on the bottom of the pile and probably should include links to adb install, linux root, osx root, windows root and etc as needed.

bg
[Nook Color Q&A, Help & Troubleshooting] Novarider:
Thank you very much!
[Nook Color Q&A, Help & Troubleshooting] nikolag:
Problem rooting the NC

Hi guys,

I am having an issue with the root procedure. When I plug-in the USB cable the Nook just boots normal. It does not appear to be booting from the SD card. I have imaged the card from Winimage, from Ubuntu and even from Nokia N900 and it just does not make any difference. :( Has anyone experienced this problem? Any suggestions?

Thanks in advance!
[Nook Color Q&A, Help & Troubleshooting] Tapiozona:
I think I read somewhere in this thread that the size of the SD card could be the problem (newer, larger ones, being the ones which didnt work) I went and bought a generic, cheapo 2gb card for 10 bucks at Best Buy (PNY i think) and used winimage to flash it onto that. Worked like a charm.

I also had problems because I skimmed the directions and tried writing the image a different way..make sure you...

"Click on disk menu and select "restore virtual hard disk image".
[Nook Color Q&A, Help & Troubleshooting] nikolag:
Thanks, worked.

I guess I did the same thing. :) Thanks for you help, it worked!

I am curious why it didn't work with DD under Linux though.
[Nook Color Q&A, Help & Troubleshooting] redbluff:
ADB Help Please

I have the Nook rooted. But I can't get ADB drivers right. I followed the guide posted on Nookdev and even did it twice. After completing it still can't identify the device even though under device manager in Windows XP I see Android phone and ADB Composite. Properties show it as the Nook with serial number and 0x2080. But if I test with type command the response on the adb_usb.ini says:

#android third party USB vendor ID List -- Do not edit

# Use Android update ADB to generate

#1 USB vendor ID per line

Any ideas?
[Nook Color Q&A, Help & Troubleshooting] jpl605615:
there is an apk some where in this thread that will allow you to drag and drop apps. no editing needed. its called APK0.3.0. maybe that will help. saves me alot of time
[Nook Color Q&A, Help & Troubleshooting] Dunkshot32:
bellow those lines it should say "0x2080"

if you have that it should work

Edit: In notepad edit the .ini file so that it reads only "0x2080" minus the quotes. Try again. I got stuck and had to uninstall the android ADB interface.. as soon as I plugged the nook back in it worked, so go figure.
[Nook Color Q&A, Help & Troubleshooting] Robertjm:
Grumble! Grumble! Grumble! I wish I'd known that.

The only microSD I have at the house is a 16gb mSDHC card. It did the same thing, booting normally.
[Nook Color Q&A, Help & Troubleshooting] TainT:
and I thought the drivers where the hard part??

Ola Fellas

Before I head over to the ADB for dummies thread (which 2 years ago was as long as this one )

I was wondering if someone would point a brother to a "what to do when this happens" thread.

I`m running Windows 7 64 bit.

Got Adb installed and all edited up and all the checks pass. (using a combo of the xda-dev process and the windows 7 process in another thred)

Used WinImage to write by boot image on the card. (i also BELIEVE this worked correctly)

I see an adroid phone and adb composite device in my device manager.

But now when I go to do this.....

cd\

cd android-sdk-windows\platform-tools

adb kill-server

adb devices

I get and adb kill-server is not a recognized exe or batch file.

How couldnt adb be installed though....I see it??

Preciate chas in advance :thumbsup:
[Nook Color Q&A, Help & Troubleshooting] jamesbra:
if you can see adb.exe in that folder than your problem is probably one of syntax, if you keep having the problem try copy and pasting the exact log.
[Nook Color Q&A, Help & Troubleshooting] plariers:
I used a 16 gb Patriot mSDHC card; worked perfectly
[Nook Color Q&A, Help & Troubleshooting] Dunkshot32:
same hgere, exact same card actually. Works fine
[Nook Color Q&A, Help & Troubleshooting] rad131304:
It is likely that you are imaging into a partition and not the root of the disk. For example, the following pseudocode is correct:

dd if=nooter_40mb.img of=/dev/sdc

Whereas the following pseudocode is incorrect:

dd if=nooter_40mb.img of=/dev/sdc0

Note the number at the end of the outfile position. This indicates targeting a partition instead of the root of the disk.

I'm only SWAGing here, but that's the most common issue. Others have had problems with imaging when the card reader is not on the main usb hub (i.e. you are plugged into a combo card reader or usb port on the front of the pc which can be on a different ?system bus? [I don't know the correct hardware term]), but I don't know if these problems were limited to Windows.
[Nook Color Q&A, Help & Troubleshooting] TH513:
I am having trouble just getting the color nook to even be recoginized by by Windows 7. I tried it on 3 different machines. It does not show up in the device manager, drives, or anywhere. It works fine, I just cannot get a computer to recognize it. I have tried resetting back to factory defaults and reflashing with no luck. The only thing I have done this far is try to boot the image file off the microSD card to the black screen. Any ideas?
[Nook Color Q&A, Help & Troubleshooting] Robertjm:
That was what I was using. However, something else is going on as I scrounged a 540mb card from an old cell phone and it's ignoring it as well. Hmmmm......
[Nook Color Q&A, Help & Troubleshooting] Robertjm:
THANKS rad131304!!

This is exactly what I'm doing. I have a 50-in-One card reader and the microSD is the only card I have in the reader. It's hooked up to one of my front USB ports.

(using Ubuntu Lucid Lynx)

I go to System --> Administration --> Disk Utility

The card reader I have has four "buses" one of which is called CardReader SD. Each of the different buses has a different letter (sdc, sdd, etc.).

When I click on the SD bus at the top it tells me the device is /dev/sdf. However, when I look at the Volumes section, it tells me the device is /dev/sdf1.

I noticed that this time, when I just used sdf I got a response in my terminal, which I didn't get the last time.

nooter$ sudo dd if=nooter_sdcard_40mb.img of=/dev/sdf

[sudo] password for robertjm:

80326+0 records in

80326+0 records out

41126912 bytes (41 MB) copied, 18.8246 s, 2.2 MB/s

Hope that helps others!

Robert

-------------------------------
[Nook Color Q&A, Help & Troubleshooting] rad131304:
Have you tried to force them to find new hardware?

in compmgmt.msc, click on Device Manager

at the root in the pane to the left, right click on one of the items and select "Scan for hardware changes"
[Nook Color Q&A, Help & Troubleshooting] sudhirkhanger:
Its any body working on custom rom?
[Nook Color Q&A, Help & Troubleshooting] TH513:
I did try this many times. I cannot get any of my Windows 7 computers to recognize it. I wonder if I just have a faulty one. Everything else works fine.
[Nook Color Q&A, Help & Troubleshooting] rad131304:
Sounds like its defective, if its NEVER been recognized by any machine, even sans root, then it doesn't sound like its working right.
[Nook Color Q&A, Help & Troubleshooting] TH513:
Took it into Barnes and Noble. It turned out to be a bad cable. It would charge fine but not work with computer.
[Nook Color Q&A, Help & Troubleshooting] rad131304:
try using:

.\adb.exe kill-server

Alternatively, if you add platform-tools to %PATH% it might solve the problem of needing the extension, but I rarely mess with path unless its really important, just because it can cause lots of unintended consequences.
[Nook Color Q&A, Help & Troubleshooting] TainT:
Thanks rad! !

I'm certain the syntax was right so ill dive back into this after dinner.

Galaxy Tabs.....Worth every penny!!
[Nook Color Q&A, Help & Troubleshooting] italiano1964:
I finally got the root process to work out. I was having problems creating a functioning image on my microsdhd card, but solved the issue and was able to upload several apps on the NC. However, Engadget says that the NC will get Froyo (2.2) in January, as well as Market access. See link below (sorry, can't post links yet):

engadget.com/2010/12/14/nook-color-getting-android-2-2-and-market-in-january-current-ha
[Nook Color Q&A, Help & Troubleshooting] italiano1964:
Take the Market access thing with a grain of salt. According to CNET, Engadget may have confused B&N own app Marketplace with the Android Market (which will still be off limits-unless of course you root the NC and follow the nookdevs method to implement it).
[Nook Color Q&A, Help & Troubleshooting] italiano1964:
Does anyone know if bluetooth software drivers are being developed for the Nook Color?
[Nook Color Q&A, Help & Troubleshooting] kitzuki:
I think i have become the first dummy to brick this thing followed the proccess to root when i went to power the device on its just stuck at the N screen tried reseting the device with holding the home screen and all but nothing works guess im going back to barnes and noble tomorrow again...

edit got it working however adb reconizes the devices but it keeps telling me that the device is offline it has the serial number then to the right says offline any way i can fix this?
[Nook Color Q&A, Help & Troubleshooting] Profondo_Rosso:
Hey guys, reading through this thread has helped immensely, so thanks for that.

I am having a problem though. I have rooted my NC, and that went well. The market works, and I have installed apps. I'm trying to go through the adb guide now, and I get through fine until it's time to

Now that you have identified the nookColor

Right-Click the device > Update Driver > Browse my computer > Let me pick > Have Disk

In the "Copy manufacturers files from:" window enter C:\android-sdk-windows\usb_driver

Press OK. This should install the correct drivers. (If a dialog appears asking which driver to choose, select "Android Composite ADB Device")

Disconnect nookColor from your computer (unplug the USB cord)

Reconnect nookColor

Windows should automatically detect the device and install all necessary drivers, including ADB.

Everything works until it says that the driver is not in the folder. It's says windows 64 driver isn't in the folder, or the driver I have isn't compatible with x64. That's where it ends for me obviously. Now, I'm running Vista 64 bit, does this require a few other steps? I know I read that a file has to be changed or edited somewhere, but I have no idea which file or where.

Any help would be appreciated...I've been fiddling for hours.
[Nook Color Q&A, Help & Troubleshooting] wir3dal:
I had similar problems with Win7 x64 but the combination of the following ended up working. I don't know Vista well but hopefully these steps are the same.

1. Open C:\Users\<yourname>\.android\adb_usb.ini and verify that ONLY the value "0x2080" (without quotes) is there. Delete anything before or after this.

2. With the NC plugged in, go through Device Manager and look for devices with the Hardware ID of "USB\VID_2080".. one example could be a 'USB Composite Device' in 'Universal Serial Bus controllers'. Uninstall the device(s) with VID_2080 (your NC) I checked the box to delete the driver file as well. Don't uninstall anything if you don't see the VID_2080 entry in Properties->Details->Hardware Ids.

3. Unplug your NC and reboot your PC.

4. After reboot, plug your NC back in and wait for Windows to do its thing with the new hardware. I saw "Nook" show up and "USB Mass Storage Device" come up in DevMgr.

5. Find the "USB Mass Storage Device" with VID_2080 and select Properties->Driver->Update Driver. I chose "Browse my computer.." and then "Let me pick..". Select "Have Disk.." and browse to C:\android-sdk-windows\usb_driver\, and hit Open. After it installs unplug and re-plug in the NC.

6. For me, this still didn't fix my issue. When I did 'adb kill-server' and 'adb devices' my NC never showed up.

7. In DevMgr, I had "Nook" listed with the driver warning icon. I followed the exact same steps for updating the driver (step 5) and choosing "Android Composite ADB Interface" when asked.

8. I unplugged, re-plugged and it showed up with the adb commands.

Hope this helps!
[Nook Color Q&A, Help & Troubleshooting] spikey911:
If this gets 2.2, will it be fast enough for flash?
[Nook Color Q&A, Help & Troubleshooting] Profondo_Rosso:
Thanks man, somehow it worked, though I don't know how. It gave me the same error message, but when I did a cmd adb kill-server and adb devices, it read like it was supposed to. Now my question is, what do I do now? I'm not a complete noob, but by doing this I can run live wallpapers and install apks right? Ok maybe I am a noob, though I have been running CM 6.1 on my Nexus:)
[Nook Color Q&A, Help & Troubleshooting] cantellay:
Audible App Nook Color

I had this same issue and sent a report to Audible. It looks like the problem is that they are not getting a consistant device id for use in authentication. If you can force the DeviceID field to always give the same value, then your activation problems should stop.

Now I have no clue how to do this but would love to test if anybody has an idea how to get this working.

Sean
[Nook Color Q&A, Help & Troubleshooting] jaredtims:
To root or not to root.....

If i root my NC, will all apps work or just certain ones? Is it enough to make it worth my effort. It seems from what i read that not everything works?

If I root my NC now, what happens when Barnes and pushes froyo 2.2 in January? Will it upgrade ok, upgrade with issues, or will it fail entirely? Or will i have to wait for XDA to release a howto?

One other question. What is the success rate of performing a factory reset after rooting? I hear it is pretty hard to brick the NC, so I'm not too concerned. I am a Java Developer, so i feel very comfortable doing it.

thanks,

sorry for the level 101 questions
[Nook Color Q&A, Help & Troubleshooting] Tom in AZ:
My 1.0.0 NC was rooted and still updated to 1.0.1 on its own.

Factory reset is no problem since the factory software is a download provided by B&N.

Working with the NC has been a breeze. Being a Java developer, you should have no problem with the current methods.

Hope that helps,

Tom
[Nook Color Q&A, Help & Troubleshooting] wvcachi:
Not all apps, but in my experience, most can be installed one way or another... At least more than enough to make me extremely happy with it. There's a thread in apps/themes of working apps.

There's a file that can be changed that, so far, seems to successfully disable OTA updates (etc/security/otacerts.zip - just change the file's name to anything else), so I'd say you'd be safe to refrain from the froyo update until it's known to be safe for root.

Data can be reset from the OS, system is automatically restored after 8 unsuccessful boots. I haven't had to do this, so that's the best I can tell you, but I haven't heard of any bring truly bricked.
[Nook Color Q&A, Help & Troubleshooting] glacon:
Barnes & Noble Soft Root/ Extended Warranty

I am sure it would no be hard for Barnes & Noble to keep track of which NC were soft rooted, rooted, etc. We already know that the in store features don't work on a rooted device. They also pushed the 1.01 update without asking permission to my device, which means they are wirelessly meddling with it when I am not looking. Do you guys think they are keeping active track of the rooting in relation to warranty/ extended warranties on the devices? I had bought the extended before I decided to soft root. Love the soft root. If Big Brother is watching I should probably get my money back while I still can. If they are not, I'd keep it around just in case I crack the screen.
[Nook Color Q&A, Help & Troubleshooting] wvcachi:
Interesting theory, but I'm gonna guess there's nothing to worry about. Android phone manufacturers/carriers have their products rooted all the time, they push OTA's all the time, and I've never heard of someone being flagged as a rooter via OTA detection and turned down for a warranty. Your guess is as good as mine, but I don't see the NC being different in that respect.

Even Apple, who I'd expect that from more than any company, recently abandoned their code to detect jailbroken iPhones in their latest firmware update.

The denial of in-store features could be as simple as the NC's method of identifying itself to networks being modified during the rooting process (so rather than barring rooted Nook Colors, their network may not know it's a Nook Color . . .)

Devs have been ripping the file system open; if there were some code to alert B&N of rooting, I'm sure it'd be discovered soon--if not already.