yashsingh1/xdaforums huggingface dataset:
[Nook Color Q&A, Help & Troubleshooting] psychoticsmiley:
You don't even need to go into Linux, if the sd card has existing partitions you can get the sd formatter software (free tool)

Google sd card tool or sd formatter 2 and restore the sd card to default. It will wipe any partitions on the card.

That's only on windows xp, 2000, vista, and I got it to work perfectly on Win 7.

You can also restore your sd card after putting the nooter image and rooting to bring the card back above the 40mb size as well with the same technique.

The first time I tried to put the image on the sd card it didn't take until I used the tool to completely and correctly format it. (win7 didn't format it correctly)
[Nook Color Q&A, Help & Troubleshooting] droidlover:
OK - I am somewhat new to rooting Droid, but I consider myself smarter than the average bear when it comes to Windows, Linux, and the Motorola Droid and Droid 2. I tried this method and it is not quite working.

I am using a Lenovo T500 laptop running Windows XP SP3. I am using a PNY Micro SD 4 GB Class 4 with the included SD adapter and just putting it into my laptop's SD slot. I used WinImage 8.5 and the 40 MB image appears to have been created just fine.

I followed the procedures on putting the card into the NC and I plugged in the cable. The cable is lighting up, but the screen stays dark - I understand this is what is supposed to happen. So, as far as I can tell - it appears to work. I let the NC sit there connected for 5 minutes just to make sure before I unhooked it.

I got the SDK installed, editted my INI file, etc. When I hook it up, I can now pull up Device Manager on my XP laptop and see Android Phone - Android ADB Interface. So it looks like everything SHOULD be working, but when I run the ADB commands, I do not see my device listed.

Should I continue to troubleshoot this or should I try booting the laptop from a Linux live cd distro and try going that route instead?

Thanks in advance for the assistance!
[Nook Color Q&A, Help & Troubleshooting] jonghast:
Go with linux, no one knows how to fix this particular problem.

I've been stuck where you are since the 2nd.

I don't care enough to bother with linux, and I figure custom roms will be available soon enough.
[Nook Color Q&A, Help & Troubleshooting] jsmith.nook:
What USB driver are you using? The NookDevs wiki linked to, what I guess I'll call a "version 2" of the driver a few days ago. I tried to use that driver and it didn't work for me. There is now a "version 3" driver. I downloaded that driver, updated the inf file as normal, then updated the driver through device manager.

And while that update seemed to work, I noticed the USB mass storage devices weren't appearing in device manager. I right-clicked on the ADB interface entry in device manager and selected UNINSTALL and checked the box to delete the driver software.

Once that was done I plugged my Nook back in. Windows found the USB mass storage devices and also installed the ADB driver. I was then able, for the first time, to use the adb utility in the android sdk to connect to the device.
[Nook Color Q&A, Help & Troubleshooting] droidlover:
Doh. I am using the "version 2" driver. OK - I will go ahead and uninstall the device and the drivers. I just went and re-downloaded the drivers AND re-setup the .android directory. The device is now showing up!

Thanks!
[Nook Color Q&A, Help & Troubleshooting] SheldorTheConqueror:
Can't download Nooter .2

I can't seem to download nooter .2. The page keeps timing out. I've tried in several browsers. Is there any other location it's at besides the mediafire.com site?

EDIT: I've also tried a couple different Computers.
[Nook Color Q&A, Help & Troubleshooting] SheldorTheConqueror:
Nevermind. After waiting for a few minutes and trying one last time, it downloaded. :)
[Nook Color Q&A, Help & Troubleshooting] boret:
The same thing happened to me and found a solution which works.

When I connect the Nook Color to the computer I go to the AndroidSDK\Tools\ folder and do the following:

adb kill-server (enter)

adb kill-server (enter)

adb kill-server (enter)

adb kill-server (enter)

adb kill-server (enter)

That is right, I sent the same command 5 times.

I then type:

adb remount

and the:

adb devices

And I can see the Nook Color

C:\android\android-sdk-windows\tools>adb kill-server
C:\android\android-sdk-windows\tools>adb kill-server
C:\android\android-sdk-windows\tools>adb kill-server
C:\android\android-sdk-windows\tools>adb kill-server
C:\android\android-sdk-windows\tools>adb kill-server

C:\android\android-sdk-windows\tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: No such file or directory

C:\android\android-sdk-windows\tools>adb devices
List of devices attached
2##########09 device

C:\android\android-sdk-windows\tools>

From then on all the adb commands work!

Hope that helps.
[Nook Color Q&A, Help & Troubleshooting] cabbieBot:
I don't know if anyone has it working on XP, I tried and failed, had to use w7
[Nook Color Q&A, Help & Troubleshooting] edison:
Just picked up my NC and can't get the SD to boot.

I haven't regged it yet - is that necessary before it'll boot from the SD? I'd like to root it before any personalization or customization happens, if possible.

The SD card appears to be formatted properly, as per pokey9000's description (on this or another thread).

TIA.
[Nook Color Q&A, Help & Troubleshooting] moovius:
Live cd option for rooting?

Anyone that has used a Live CD to perform the root from linux:

Please explain how I would install the android sdk to the Live CD so I can root my NC?

I'm tired of playing around with the Windows 7 install instructions. I get nothing but frustration out of it.

Thank you.
[Nook Color Q&A, Help & Troubleshooting] edison:
Where are you stuck?
[Nook Color Q&A, Help & Troubleshooting] ruze:
not working :P

I just got a brand new NC today, and went through the process exactly on *both* Windows and Mac. First tried it with Windows and it came up with the Android ADB Device driver showing but no 'adb devices' :P

Exact same thing on Mac. I can SSH in during the SD boot phase, but when it reboots into the regular NC UI no joy. :(

Could they have updated already? Or, could it be that the version of the Android SDK is 8?

Any ideas? Anything I can do manually while SSHed in during the SD boot?
[Nook Color Q&A, Help & Troubleshooting] moovius:
I'm getting "error no device" when I run adb remount or adb devices.

I have been through the entire process a few times. I have re-imaged the NC a few times too to make sure, doing a factory restore between attempts.

It's just not working.
[Nook Color Q&A, Help & Troubleshooting] wvcachi:
10 characters
[Nook Color Q&A, Help & Troubleshooting] edison:
I'm having the same problem with my Win7 desktop. Installed the SDK on my laptop, downloaded the google_drivers v4, added the requisite lines to the google-usb_driver/android_winusb.inf and it works.

I doubt the google drivers are the issue - I think it may have something to do with the raw USB device itself. Dunno.

Either way, try another PC and report back.
[Nook Color Q&A, Help & Troubleshooting] johnopsec:
Simply do a factory reset and they will never know.
[Nook Color Q&A, Help & Troubleshooting] moovius:
Tried my netbook, which has win 7 64 bit on that also... same result.

I'm hoping for a packaged root program or a step-by-step LiveCD guide at this point.
[Nook Color Q&A, Help & Troubleshooting] rutter9:
mine works perfectly fine.
[Nook Color Q&A, Help & Troubleshooting] deeoh:
Here's step-by-step what I did to get it working. Again, I'm running CyanogenMod Froyo on a rooted Aria, so this may not be exactly the same for non-rooted/non-CyanogenMod devices.

1) On your android phone, go to Menu > Settings > Wireless & Networks > Tethering & Portable Hotspot

2) Turn on portable wi-fi hotspot

3) Go to Portable wifi hotspot settings

4) Configure wifi hotspot: Name it whatever you want and leave the security set to Open.

5) On your nook color, go to settings > wireless

6) Turn on wireless

7) Select the wireless network you created, make sure it sees the open security setting and connect.

That's all I got. As for hacking/rooting, I have been playing around in linux to see if I could get any more info on the hardware. It showed two disks when I plugged in my NC with no microSD card installed and I thought that may be a system partition. Unfortunately, it was just the empty microSD slot as it had no media present. If you do mount the NC on linux, you can see some more hidden folders/files, but nothing system-related.

On a less related note, I took the SD card out of my phone to test in my nc, which had some books on it from the nook for android app and guess what? I was able to open books that I had downloaded there. The kicker is that the account I'm running on my phone is a different one than the one I'm running on my nc. It looks like I've stumbled on a way to get around the drm! I'll post more if I figure out what was going on.
[Nook Color Q&A, Help & Troubleshooting] wilvc:
Is this exploit helpful?

There appears to be a known exploit to the browser in Android 2.1 :

www exploit-db com/exploits/15423/

Can someone make use of this to cause the NC to enter recovery mode?
[Nook Color Q&A, Help & Troubleshooting] madsquabbles:
how about streaming video? the only site i got to stream was an adult site, but it played choppy. youtube mobile didn't work. all my existing mp4 will play but just like streaming they play at like 5 or 10 fps.

NM reboot fixed everything. my ripped videos and stuff downloaded with videodownload helper play fine now. my ripped vids are done with handbrake using iphone setting and just increasing or decreasing the res. 300kbps is all i used for the small screens. they play perfectly on my nc as do the ripped youtube vids using videodownloadhelper.
[Nook Color Q&A, Help & Troubleshooting] dirtygreek:
Just copying that code to a file on my server and trying to hit it using my NC browser, nothing happens. At least, after a few minutes, nothing has happened. If anything does, I'll report.
[Nook Color Q&A, Help & Troubleshooting] KCHASE731:
youtube mobile worked for me. i also can connect to my evo using wifi tether. i like the nook color...but i starving for a root option. the hardware is much nicer to carry than the galaxy tab, or something like the archos 70. this thing feels solid, and looks really good. i have my fingers crossed for a way to turn it into something "more"
[Nook Color Q&A, Help & Troubleshooting] KCHASE731:
i tried my web server also. green loading bar moves half an inch and stalls. i also seem to remember a similar exploit for the evo when the page was trying to load flash if you did something you could cause it to glitch on android 2.1. ill look back and see if i can find that.

also. not sure if this exploit will help:

http:// imthezuk blogspot com/
[Nook Color Q&A, Help & Troubleshooting] TheDoctor1971:
I didn't have any problem tethering mine with my Evo's wifi either.
[Nook Color Q&A, Help & Troubleshooting] bobdude5:
http://xdaforums.com/showpost.php?p=9332362&postcount=16
[Nook Color Q&A, Help & Troubleshooting] syncron:
That sounds promising!
[Nook Color Q&A, Help & Troubleshooting] bobdude5:
this guy is on a role ! someone help him!
[Nook Color Q&A, Help & Troubleshooting] PHiZ:
That code shovels a reverse shell back to a hardcoded IP and port. So, unless you have set up a machine to listen, you won't see anything interesting happening.

If you want to play with it change this code:

var ip = unescape("\ua8c0\u0100"); // ip = 192.168.0.1

var port = unescape("\u3930"); //port 12345 (hex(0x3039))

to the IP address of your server. Note the // are comments. So, take your ip, convert it hexadecimal and put it in reverse-byte order. You should be able to figure it out by example.

Then set up a listener on port 12345 or whatever. Netcat should work.

I played with it a little, but got sidetracked trying to see if I could get Wireshark to sniff WPA encrypted traffic (I want to see what the Nook is doing.)
[Nook Color Q&A, Help & Troubleshooting] pezhore:
Any ideas what the exact syntax of nc should be? All I did was alter the IP address to match my desktop, can't seem to get it connected though.

EDIT: I've tried nc -l 12345, but I'm not sure if its actually connecting, or just timing out. I found a few other exploits that *may* work, but unfortunately its been way too long since I've messed with exploits.
[Nook Color Q&A, Help & Troubleshooting] Tom in AZ:
Have mine in hand, and think it is a nice tablet. Can't wait to get root an be able to install apks. It blew me away to find out it has a ARM Cortex A8-based TI OMAP3621 800Mhz proc. Still no idea on RAM for it though, but hope it is 512. In any case, thank you guys for working on this! I'll have to send out a beer or two to the person who gets us root!

Tom
[Nook Color Q&A, Help & Troubleshooting] dirtygreek:
It is 512.
[Nook Color Q&A, Help & Troubleshooting] dirtygreek:
Ah, awesome.
[Nook Color Q&A, Help & Troubleshooting] Tom in AZ:
Thanks! Any other interesting points we should know about?
[Nook Color Q&A, Help & Troubleshooting] PHiZ:
I believe you can add the -v flag, for "verbose" and get a notification upon connection.
[Nook Color Q&A, Help & Troubleshooting] dirtygreek:
Well, I tried using that web exploit on my machine with ip 192.168.1.110 (\ua8c0\u6e01) and port 12345 (\u3930) but nothing ever shows up on my netcat listen. The browser does seem to just keep looking for the page for a while, then it eventually crashes (did the same to Firefox on my desktop as well) and drops back to the home screen.
[Nook Color Q&A, Help & Troubleshooting] drmazu:
Old Nook ADB option

Has anyone tried to adapt the old Nook ADB method over usb for the NC?

ADB Over USB

ADB, or Android Debug Bridge, is a versatile tool lets you manage the state of an emulator instance or Android-powered device.

As of NookDevs Softroot/ROM 2.4.1 (B&N:1.4.0), ADB on the nook is done over USB only by default.

This functionality was introduced thanks to JesusFreke. The source diff and relevant files can be found here.

You may need to do some extra steps in order for your ADB over USB to work.

Contents

1 Installation

1.1 Windows

1.2 Linux

1.3 Mac OSX

2 README from initial distribution

3 Note for 1.4.1

Installation

Windows

Download the Android SDK from http://developer.android.com/sdk/index.html Unpackage to c:\androidsdk

Download the driver here: http://www.multiupload.com/OI0V0DB96Q Unpackage to C:\nookadbdriver

Run C:\androidsdk\android-sdk-windows\SDK Setup.exe

Go to "Settings", check "Force HTTPS to HTTP"

Go to "Available Packages", click the >

Click the checkbox next to the android 1.5 platform sdk.

Click "Install Selected" then "accept", it will then download and install the 1.5 SDK platform. You can close the setup when completed.

Go to Control Panel/System/Advanced System Settings, click the "Environmental Variables" button.

Click the "Path" in the system variables and edit it. Add (DO NOT DELETE ANYTHING) ;C:\androidsdk\android-sdk-windows\tools

Save and get out of there, plug in your nook.

Go to your device manager (Should be in system somewhere), Click "Other devices" and you should see "ADB Device"

Double click it, and click "update driver"

Choose to browse your computer for it, point it at c:\nookadbdriver

It may pop up a warning about verifying publisher, click "OK"

Hit windows key + R and type adb shell

You're done!

(Optionally if the above doesn't do it.)

Restart/start ADB daemon

adb kill-server

adb start-server

Make sure "Start ADB" is selected in Wifi Locker.

Read more: http://nookdevs.com/ADB_Over_USB#ixzz15wUZznGP

Under Creative Commons License: Attribution Non-Commercial Share Alike

Taken from nookdevs.com/ADB_Over_USB
[Nook Color Q&A, Help & Troubleshooting] ruze:
Is there a way to find out the version of ROM/bootloader on the device? If B&N updated it over the weekend to fix the hole how can we tell?
[Nook Color Q&A, Help & Troubleshooting] ruze:
Ok got it working amazingly. I uninstalled the driver (Android ADB Interface) and checked the delete files option. When I rescanned it found it and installed the correct drivers under W7. No idea about Mac and YMMV.
[Nook Color Q&A, Help & Troubleshooting] droidseban:
I used the Linux Live CD to just get the image into the SD card. The rest of the steps were done in Win 7. Main reason I used Linux was because winimage didn't work for me in Win 7. Also, I used the nooter1 image with the usb drivers version 2 - it shows the devices slightly differently. Make sure when you get to the part where you update the drivers under device manager, do it to the one that shows as usb mass storage device and not the "nook" entries.
[Nook Color Q&A, Help & Troubleshooting] edison:
Did you have an 'Android Composite ADB Interface' root device or was it under 'Android Phone'?

I've uninstalled and reinstalled the drivers about 10 times, with no success. My NC's obviously rooted since it shows up on my laptop and I can sideload from there, but I'm stumped as to why it's not working from my PC.
[Nook Color Q&A, Help & Troubleshooting] jed394:
2.2 update

Just a heads up. I bought my nook last night and I of course told the kiosk guy that i was goign to root it. he told me he was going to root his as well, but the also said that B&N was going to release a 2.2 update sometime in January. Who knows if thats true but a little FYI.

Great job guys on the root!!
[Nook Color Q&A, Help & Troubleshooting] Dunkshot32:
I have been told the same and a few other sources also agree. The nook color will be getting android 2.2 early 2011 (january or early febuary were mentioned) and this update will add a B&N specific app store. What this will do to the actual root process I'm not sure, but it seems that every B&N employee is already aware of the ability to root and none seem to perterbed by it. Call me crazy but, I'm sure B&N will make at least a small attempt to patch the hole we're using, but I don't think they really care. I mean, they left it so it booted from SD before internal, that has to say something.
[Nook Color Q&A, Help & Troubleshooting] Tapiozona:
Hi all,

I'm having problems with my NC root. I'm using winXP and from what I can tell everything went smooth with the microSD and nooter. My problem is with the ADB part. I added the drivers and when I go back to device manager I see "Android Phone" and under that "Android ADB Interface". According to the walkthrough it should be "ADB Composite device".

I figured it was the same thing but when I went to verify if everything worked by doing this...

1. Start > run > cmd

2. cd androidsdk\tools

3. adb kill-server

4. adb devices

I run into issues. Mainly there is no androidsdk\tools folder in \Documents and Settings\<MyUserName>. There's only a .android folder and no tools folder in there. There is however a androidsdk folder in root C: but then I have to go through \android-sdk-windows\ to find a tools folder. There's no adb in there and "adb kill-server" only gets me a

"adb' is not recognized as an internal or external command, operable program or batch file."

Any help would be much appreciated. This is my first try rooting anything and I'm not 100% comfortable in this type of environment. Sorry if my problem's description doesn't make sense..hard for me to describe.
[Nook Color Q&A, Help & Troubleshooting] califrag:
start>right click 'my computer', properties (if you are on windows 7, click 'Advanced system properties' on the left)

click 'Advanced' tab

click 'Environment Variables'

Under 'System Variables' scroll down to 'PATH' and double click it

go to the end of 'Variable Value' and add ";C:\androidsdk\tools\"

(without the "s)

reboot your computer, should work now
[Nook Color Q&A, Help & Troubleshooting] Tapiozona:
That folder doesn't exist (c:\androidsdk\tools\) but I did find adb.exe here instead....

C:\androidsdk\android-sdk-windows\platform-tools

and when I killed server and did "adb devices" I got this...

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

List of devices attached

However my NC isn't listed..it's just blank. Linux, however, was able to recognize it with the serial number...just not windows.
[Nook Color Q&A, Help & Troubleshooting] dirtygreek:
Well, keep in mind B&N didn't actually build the devices, a third party did. That third party may not care if it's rootable, but B&N may. We'll see. Now they know about this (they may not have even been aware of the possibility) they may ask the builders to try and block it.
[Nook Color Q&A, Help & Troubleshooting] glacon:
Firmware Update

I have a Nook Color with major flicker issues.

Tried to change it out, but the three I opened in the store all had dead pixels, so did their display model all in the lower right hand corner of the screen. Would be covered up by the black menu bar normally, but visible when the black menu bar goes away.

Anyway I kept my flickering nook, and talked to someone at Barnes and Noble tech support while still in the store. He told me the dead pixels were new to him, but they knew about screen flicker issues. He said they would be releasing a firmware update to address this and other problems very soon.

My guess is they will remove root and patch the way of doing it with the update.
[Nook Color Q&A, Help & Troubleshooting] jsmith.nook:
1. Plug in your NC

2. Go into Windows Device Manager

3. Right-click on the NC

4. Select UNINSTALL

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

6. Click okay.

7. Select "Scan for hardware changes" from the ACTION menu

8. It should find and install the NC device drivers

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.
[Nook Color Q&A, Help & Troubleshooting] edison:
Just for clarification, in Step 8 you have to point the driver installer wizard to your usb_drivers folder, right? It doesn't automatically find the drivers that you deleted in Step 5, does it?

And which NC device did you delete in Step 3-4? The "Nook" device with the warning icon, or the "USB Composite ADB Device" under "Android Phone" or one of the other devices with the NC's ID (0x2080)?
[Nook Color Q&A, Help & Troubleshooting] sipdrone:
One thing I found was that the NookDevs tutorial told you to download the folder named adb_usb (contains the .ini file) and place it in your c:/users/<name> directory. On my system (Vista) I had to extract the .ini file and place it in the existing .android folder. So for clarification the .ini file must be in c:/users/<name>/.android/adb_usb.ini, not in c:/users/<name>/adb_usb/.android/adb_usb.ini

that fixed my issue when I couldn't see the device under adb
[Nook Color Q&A, Help & Troubleshooting] mad5427:
Something is really messed for me right now.

I rooted a while back, loaded a bunch of stuff, installed superuser, live wallpapers. Something went wrong somewhere and the machine just wasn't working quite right. I flashed back to the original software. Back to square one.

I rooted again and everything seems just fine. I tried to enable app install from on-device methed. I can't seem to get the line: update secure set value=1..... to work. I figured I'd redo the adb steps and see if that somehow fixes it. Redownloaded the necessary files and did that process. I have adb access now, but something is weird.

I gave up on enabling the apk install and tried to enable live wallpapers. Now, when I type: adb shell it used to go to the next command line and show a #

Now that next line shows a $

It won't allow me to mount -o remount. Something is just not working right and I have no idea what I did. Any ideas.
[Nook Color Q&A, Help & Troubleshooting] zdrifter:
With NC connected, delete "USB Composite ADB Device", disconnect NC being sure to use the correct process to disconnect a USB device, wait a minute of so, connect the NC and you should see all the devices as windows scans and installs them and ADB should work.