yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] lekofraggle:
For bluetooth, usb host and all the other goodies, you need a non-stock kernel. Try the apps to sd install options.

~Leko
[Nook Color Android Development] jonty12:
reinstalled using .19. all working now.

thanks all.
[Nook Color Android Development] forcie270:
well you should be able to find the "browser" in the apps drawer and then hold and drag to where it was before.
[Nook Color Android Development] baker2gs:
I do not see it in there. Is there a simple way to get it back in there app drawer? It still loads just fine so I know I didn't uninstall it.
[Nook Color Android Development] nrapallo:
i installed AnyCut (from market) and placed the browser shortcut onto the desktop using that. Then, just drag it onto the dock.
[Nook Color Android Development] nuttsp:
Hi,

First thank you for this very simple root guide.

I must have done something wrong because I can not get my nook to boot from the SD card. My nook already has 1.14.1 on it. Below are the steps that I took.

I have a 2g card and formatted it with my nook.

Then used Win32DiskImager and wrote the "1gb_clockwork-3.2.0.1-eyeballer.img" to the card.

Then I copied "manualnooter-5.02.19.zip" to the root of the card.

Then I put the card in the nook and powered on.

After that the nook just powers up normally.

Can someone help me understand what I am doing wrong? I must be missing something.

Thanks

After this post I think I have found the issue. I was loading "1gb_clockwork-3.2.0.1-eyeballer.img" on my 2gb card. I will retry using the correct img.
[Nook Color Android Development] baker2gs:
Perfect, this works great. Thank you!
[Nook Color Android Development] Omega Ra:
I don't need the apps2sd version to install the OC kernel right? what is apps2sd anyway?

edit: love the new boot animation btw. I installed the kernel fine. how do I do the adb thing again to get a different keyboard?
[Nook Color Android Development] nuttsp:
Well I must be missing something I installed the image for my 2gb card, inserted it into my nook, powered it up and nothing. It booted normally. Anyone have ideas on what I could try next?
[Nook Color Android Development] LinuxNewb:
So I realize this post is for an already registered Nook but does anyone know how to bypass the Out of Box Experience on 1.4.1? The Wiki tip doesn't work on the latest firmware.

My buddy bought a Nook Color for dirt cheap on Craigslist and Tech Support won't unlink the serial number and account. My friend doesn't care about the B&N content, he just wanted a cheap Android tablet.

Any advice on bypassing the Setup screen so I can get this thing nootered?
[Nook Color Android Development] fpga_guy:
Formatting the card with the NC was the problem. Take out the sd card, blow away all the partitions with easus partition manager. Then using Win32DiskImager create the bootable sd card. I would use the 2gb cwm from http://androidforums.com/nookcolor-...od-recovery-twrp-version-3-2-0-1-sd-card.html
[Nook Color Android Development] -somebody-:
updated to 1.4.1 and this worked great to get root, thanks a bunch
[Nook Color Android Development] nuttsp:
Thanks for the help. I tried this with two different SD cards and still no luck. The nook always boots normally.
[Nook Color Android Development] fpga_guy:
If you can describe EXACTLY the equipment you used (what computer PC or MAC), the OS version (XP or Win 7, x86, x64, Lion, ..) what SD card reader, and exactly the process you followed - someone might be able to help you. I suspect that the image is not written to the SD card correctly.
[Nook Color Android Development] GMPOWER:
I tested this with Dolphin HD version 7.3.0, and Adobe flash player 11.1.111.6. Dolphin HD was set as user agent desktop, and plug-in always on. For the ABC content I noticed that you must not run any ad-blocking add-ons, or ad blocking from the host file. I had an ad-blocking host file on my system, once I deleted it, and rebooted the system, I could watch the ABC content. Sometimes it would fail on first attempted, but would work on the second try.

There is no Bluetooth support in the factory firmware. We don’t have access to the source code that builds the stock ROM, so we can’t enable Bluetooth in the boardconfig.mk file.

It does not matter if you use the 1gb, 2gb, or whatever size image file. The 1gb file just means that you will have a 1gb partition on the SD card, I have used the 1gb on a 16gb SD card without a problem. I put the 1gb file in the directions to accommodate everyone’s SD card size.

Are you using a memory card reader to access the SD card from your computer? It almost sound like you are leaving the SD card in your NC, and then plugging your NC into your computer to flash the drive with Win32DiskImager. If Win32DiskImager is finishing without error with a memory card reader to access the SD card, then it should work when you put it into your NC, and turn it on.

No, the OC kernel can be installed on both versions without any problems. Apps2sd is exactly what it sounds like, you can install your applications to your SD card to free up space on the device. Some of the larger applications require apps2sd to install. Apps can me moved back and forth from the device and SD card using manage application from NookColor Tools.

To get another keyboard, you need to place the apk file for that keyboard into the /system/app folder. You then reboot the device, and select the new keyboard using NookColor Tools. If you need to know how to do this using ADB, just let me know, and I will tell you how.

If your buddy does not care about the B&N content, then you should just make a bootable CWM card, download the CyanogenMod 7.2 file, place it onto the bootable CWM card, turn off the NC, place that bootable CWM card into the NC, turn on the NC, and flash the CM 7.2 image. There is no need to root the factory firmware, just to install another Rom on the NC.
[Nook Color Android Development] fpga_guy:
Just to reinforce this note: you must use an external memory card reader in order to create a bootable SD card. Using the NC is probably the reason why you are bypass the SD card on boot.
[Nook Color Android Development] framitz:
I think you wrote clockwork mod to internal memory, so you will need to wipe back to totally stock to successfully apply the update and root.

This post shows reverting to 1.2, which I had to do, the second option will return it to 1.2 stock, then when you power up and set up it should get the 1.4.1 update. CWM won't be there, so going back to the first post should get you going toward root.

http://xdaforums.com/showthread.php?t=1050520

Maybe a quicker fix,

Try booting to CWM recovery to see if it is internal;

Hold n , press power and hold until it shuts back down, then press n and power again and hold about 8 seconds, if CWM recovery comes up, try flashing the zip file from SD, it might / should?, take it that way and you'll be rooted.
[Nook Color Android Development] LinuxNewb:
I was trying to find a way like my phone where I could get in to a download mode and either flash a new kernel through a .tar with CWM baked in so I could mount the internal storage from CWM. (Odin + tarball = easy life)

Your suggestion will definitely work, my buddy just needs to go buy a MicroSD card :)
[Nook Color Android Development] el_venga:
im having same problem as nuttsp. no boot from sdcard, tried 2x 2gb and 1x 4gb, still no recovery boot. even tried generic installer with cm7. im going to reinstall 1.4.1 again.
[Nook Color Android Development] fpga_guy:
Nuttsp seem to be quiet - hopefully that is good news. I have an old version of CWM (3.0.2.8) and wanted to create a new bootable CWM.

Here's what I did (a few minutes ago).

Purchased a 4gb microsd card from Microcenter.

Ran h2testw 1.4 to verify that the sd card was error free; time: 15minutes

Copy the bootable 4gb cwm (not TWRP) from the dropbox share:

http://androidforums.com/nookcolor-...od-recovery-twrp-version-3-2-0-1-sd-card.html

Using 7zip, unzip the the rar file to PC running Win7x64.

Inserted my microsd into USB card reader (not the Nook!)

Used win32image to write the 4gb image to the microsd (about 15 minutes)

Power down my NC, inserted the microsd and now doing a backup....

The important point is NOT to use NC to create the image, you need an external usb card reader.
[Nook Color Android Development] GMPOWER:
I don't see reinstalling 1.4.1 helping you out any with this issue. Here are a couple guidelines that should help you out:

You MUST use an external memory card reader to write the file to the SD card

You MUST run Win32DiskImager as administrator, right-click on the application, and select "Run as Administrator"

You MUST turn off your NC before you insert the SD card

If you reach "Read Forever" when you start-up, turn off the device, and then power on again.
[Nook Color Android Development] el_venga:
EDIT: problem solved. this is nook tablet and not nook color. the model from the back is not readable so i searched a lot and confirmed it.
[Nook Color Android Development] Bobioden:
I installed 5.12.20 back in Dec 20. I hadn't been on for a bit, came back to see the version is 5.02.19 on the front page is the most current? Is the version I have an old one and should not be used? It seems pretty stable.
[Nook Color Android Development] GMPOWER:
By upgrading, you should get a lot more apps in the market, facebook, angrybirds, tweetdeck, among a lot of others. Just make sure that you follow step 14 under “Let’s get started” to clear out the old market information. Since you have one of the old versions, there is no need to do a wipe of the system. If you are happy with the function, and app results in the market, then by all means keep what you have. There is also the option for apps2sd, if you need that support.
[Nook Color Android Development] luck13lefty:
Followed the instructions and happy to say I have full access to the market, and my info from B&N is still on my nook. I have no problems with my device that I can see. Thanks for your hard work !!!
[Nook Color Android Development] fpga_guy:
Two questions:

1. How did you fix the limited visibility for market?

2. What was the cause for Flash boot looping and the fix?

Thanks - great job.
[Nook Color Android Development] reebz:
can't install alternate keyboard

I'm trying to install Swiftkey X from Amazon App store. When I download and hit install a box pops up and gives me two choices, install with app installer or package installer. If I hit App installer, i get the message, "unable to install, this application was not able to install onto your device. Please "Archive" and then "Unarchive" the application to try again." If I use package installer, I get the message, "Parse error. There is a problem parsing the package." Any assistance would be greatly appreciated.

I am MN'd on 1.4.1

I get same messages when trying to install Swype Installer.

I used MN 5.01.24.apps2sd when I rooted. might that be the issue with being unable to install alternate keyboards?
[Nook Color Android Development] GMPOWER:
1.	B&N removed some permissions files starting with the 1.3 update, so I just restored those permissions in this package.

2.	B&N built the stock firmware with Adobe Flash and Air built into it, so when the market updated Flash/Air, the old files were left on the device causing the boot loop. The MN package simply deletes all traces of the old Flash/Air, updates both of them, and allows you to update them in the market without causing the boot loop again. I first built a Flash fix back on August 10, LINK . That fix did not address Adobe Air, because it was not updated until October.

Parse errors generally are cause by an error in the download, or an sdk version mismatch. Try deleting the apk file in /sdcard/Android/data/com.amazon.venezia/cache. Is it the beta Swype Installer? The MN 5.01.24 package is the same as the current release, so that should not be the problem.
[Nook Color Android Development] fpga_guy:
google voice - no voicemail download

With 5.02.19 and using google voice, I can send and receive text messages. However, I am unable to playback voice messages. I get an error downloading the voicemail.

Tried wiping data with Titanium backup but that didn't fix it. No really urgent but would be nice to have. The workaround is to read the message in mail and then open a browser to download the voicemail.

ah.. google thinks the NC is not compatible with google voice. Which is true for calls - but not for playback of voice mail. It previously worked with BN 1.3 and MN.
[Nook Color Android Development] reebz:
Using Root Explorer, I go to that location, but there is no SwiftKey X .apk there. It is the beta Swype Installer I'm trying to use. In the Amazon App Store, under My Apps, the only option is to reinstall SwiftKey X, so I can't try downloading again.
[Nook Color Android Development] WyldWolf:
GMPOWER,

I flashed both my wife's nook and mine with 5.02.19.apps2sd same steps side by side and having issues on mine and some inconsistencies. Flashed again with this build using the same procedures (below). Mine has newer screen hardware. Both were stable on manualnooter-5.01.24.apps2sd but have been updating every build both to test and work out any bugs.

Both flashed using following method:

1. Boot CM 3.2.0.1 - format system, data, cache, wipe devalik.

2. Install 1.41 stock on both (have to since nothing else works on my new screen hardware)

3. Boot, register nc, download content, let sit for 30 min

4. Boot CM again, install manualnooter-5.02.19.apps2sd.zip, then update-Froyo1.2-dalingrin-OC-emmc-09011.zip and reboot

5. Open market, register to gmail acct, let market update.

**Inconsitencies begin here**

6. Wife's shows a couple manual updates including rommanager - no softkeys update listed or adobe updates but when searched in market they show with updates - mine, auto-updates all google apps, adobe, and rommanager and shows a softkeys update without searching

7. Wife's no longer shows "sd card inserted" in notifications even though her normal card with content is inserted (and usuable) - every other reboot it shows

8. Mine, after going into "deep sleep" with dalingrin's kernel and his nook tweaks app - Screen touch no longer registers. Also, on both NC the 1200mhz OC is dead after going into deep sleep mode once - only runs at level3 800mhz.

I'm in the process of re-flashing mine now for the 3rd time in a row before I roll back to 5.01.24 but a couple questions.

1. Is there an exact changelog of what changed between 5.01.24 and 5.02.19 so that I can help narrow down what's going on, particulariy with nooks with new screen hardware as this is the first build with 1.41-based that the screen touch seems flaky? Same dalingrin kernel zip used only thing that changed was MN build.

2. Other than dalingrin's NC tweaks app, what other methods can even accomplish utilizing the OC kernel since without installing anything is seems to run at stock speeds of 800 according to cpu spy? What's the best OC method?

3. Is there a way to kill this "deep sleep" cpu level that appears to kill wifi on both whenever asleep killing any active processes trying to sync? Stock keeps it alive for OTA updates, etc but with dalingrin's kernel and his tweak app it does not stay alive.

Thanks!
[Nook Color Android Development] GMPOWER:
I just flashed back to a fresh install of 1.2 and 1.3, and both did not have google voice listed in the market. I do remember at some point in time being able to download it from the market on 1.2, I never flashed 1.3 for personal use. I will look into it some more, along with side-loading the app into the NC.

When you are looking for the SwiftKey X apk, you will have to look for the Swiftkey icon, because the title will be in this format vnzXXXXX.apk.

Attached below is a copy of the Swype installer that I have, it have tested that it works. I recommend downloading it on your computer and then transferring it over to your NC.

The changelog between 5.01.24 and 5.02.19 is as follows. Nothing really changed, and this is why in the OP I put "Update is not needed if you have flashed manualnooter-5.01.24" since nothing but the RomManager changed and that can be done in the market. The number just changed to reflect the release date. MN-5.02.12 accidentally had the kernel move script in the base package, and since people were not installing a kernel with it, were left with a bootloop. I decided that I would just remove that part of the script for both packages, so that this problem does not happen again in the future.

Headings in the install script changed

RomManager was upgraded from 4.2.0.2 to version 5.0.0.5

Script that moved the factory kernel to uImage.cwbak was removed

You can use SetCPU to adjust the clock speeds,LINK.

The dalingrin kernel has a WiFi driver included with it that is supposed to fix the SOD, sleep of death. You can try the app "Spare Parts" to set the WiFi sleep policy to never.

I find it interesting that you are getting two completely different results. I have never payed attention after installing as to what apps asked for an update, I just went to market settings, and set the market to auto-update apps. Some of your overclock problems might simply be that your device does not do well with the clock set at 1200mhz, and you might do better at 1100mhz.

I hope that this addressed all of your question, if you have any more feel free to ask.
[Nook Color Android Development] fpga_guy:
caution: 1.4.2 is out

Be sure to block upgrades until further information is available. Best way is to use sqlite to change the OTA field from "auto" to "manual".
[Nook Color Android Development] morganpe:
Listen to fpga_guy 's advice.

I didn't know there was an update coming and now I think my Nook lost it's root.

If you restart it goes through the start up where the nook screen shatters and boots up with the android (rather than nook) desktop / home screen.

Unfortuantly, market won't let you sign in. Gmail won't start, Soft Keys won;t work and Home catcher is gone so once you hit the "n" hard key you are at the nook interface and you cannot get back to the "android/zeam launcher" interface.

I wish I would have put the block. things were going great for me prior to that. Had the 1.4.1 with Manual Nooter 5.02.19.

I will be watching to find out how to get back to "normal"

Thanks to all of you experts out there who keep finding the work arounds for these "helpful" upgrades.
[Nook Color Android Development] bluepen61:
Oh, I was supposed to block 1.4.2? Opps, I downloaded it yesterday and it took until this morning for it to take. Here are my observations:

1. Reboot took a long time, I waited patiently.

2. Android home showed up, but after going to the B&N home, I could not return without rebooting.

3. Rebooting, returned to Android home, Nookcolor Tools missing; Market would fc.

4. Powered down and booted to CWM.

5. Reinstalled MN 5.2.19 and Dalingrin's 9.1.11; rebooted.

6. Market appeared, signed in and ok. Gmailed works.

7. No apps appear in Market. Market, build version 3.4.4.

8. Appears that my other apps are still around and working.

9. Did the Market visibility fix in OP but didn't work...

So that is my experience with 1.4.2 and MN 5.2.19. It is nice that they are working! (except for Market of course) :)
[Nook Color Android Development] GMPOWER:
I would try uninstalling updates to the market

I have tested on a fresh install, and everything seems to be working the same. The market download fix is the same for this version. I did a file compare for the apps2sd fix, it is 100% the same, so that will work fine. It will be another couple hours before I can do a full file system, and kernel compare.
[Nook Color Android Development] viskon:
What is the process to block the OTA?
[Nook Color Android Development] rubyv:
because i've changed my password with gmail. I now cannot log into my google/market/etc. It keeps saying that I've entered the wrong password after the update. Any ideas?
[Nook Color Android Development] lukepda:
I guest it could be the problem of Google's new account policy.

They changed it to '2-step verification' months ago.

From that time, you need to assign different passwords in different mobile devices when you use a same google account.
[Nook Color Android Development] fpga_guy:
There is an entry in a database: devicemanager.db which as a field name "com.bn.device.fota.mode" which control "off the air" (OTA) updates. The default is "auto". You want to change it to "manual". Credit goes to this post for the solution.

http://xdaforums.com/showpost.php?p=12557048&postcount=4
[Nook Color Android Development] lukepda:
To GMPOWER:

BN has released the 1.4.2 for NookColor, do you have a new plan to update ManualNooter to support it ?
[Nook Color Android Development] GMPOWER:
Both kernels, and packages, are 100% compatible with the 1.4.2 update, the OP has been changed to reflect this.

Here is a 1.4.2 update that can be flashed using CWM, it will keep CWM in place if you flash from internal. LINK
[Nook Color Android Development] gsutton:
Thanks, GMPOWER!
[Nook Color Android Development] bluepen61:
Maybe that is my problem with market. Maybe the update triggered it.
[Nook Color Android Development] harliquin:
1.4.2 update caught me asleep.

I rebooted, market had lost setting, no gmail, etc.

I reapplied manualnooter-5.02.19.zip from OP

(originally had 5.12.20.zip)

Came up okay.

Started Gmail, had to login. Gmail works

Market first said problems connecting / RETRY.

Then limited visibility.

Did the fix visibility in OP.

Now market was stuck at Connecting/RETRY.

Went into Nook Tools, forced closed market, CLEARED DATA and CACHE.

Restarted market, everything is fine.

I can even load the Facebook app. (I couldn't before, it said device incompatible)

Things are good.

Thanks!
[Nook Color Android Development] glassr:
I currently have CM7 installed internally. If I install this 1.4.2 rom through CWM, will my new stock nook color keep root? How can I be assured that I will not receive B&N updates? Thanks. And, if I do a OTA update block, does it have to be done immediately, does B&N shoot the updates asap?
[Nook Color Android Development] bluepen61:
Went into Nook Tools, forced closed market, CLEARED DATA and CACHE.

Worked perfectly! Thanks!!!
[Nook Color Android Development] GMPOWER:
If you have CWM installed on your device, it will install the stock 1.4.2 ROM to your device, and keep CWM on your device. To get root access of the stock 1.4.2 ROM, you will need to flash one of the MN packages using CWM. By having CWM installed on your device, it will keep the device from flashing OTA updates. Just to be safe, you can follow one of the block OTA update guides. Since this is the most up to date B&N firmware, you will have between now, and whenever they put out another update to block it.
[Nook Color Android Development] fpga_guy:
I don't have CWM in emmc but instead have a bootable CWM sd card. Will this link work with my NC to upgrade to 1.4.2 before rooting again?
[Nook Color Android Development] GMPOWER:
Yes, you should be fine. If you currently have a way to flash CWM recovery, you can flash that, and then download my CWM Remover, LINK. Just flash the file through CWM, it will remove CWM, and restore the stock files.
[Nook Color Android Development] collins521:
Thanks for this! Just got a Nook Color today and got it up and going just fine with your instructions...hopefully this is a ok question to ask here. Is there a way to get Bluetooth to work like this setup or do I need to load a completely different rom?
[Nook Color Android Development] bluepen61:
I believe you need CM7 either on uSD or emmc to use bluetooth.
[Nook Color Android Development] collins521:
Ya I was reading more up on it last night...appears it is a B&N thing that blocks the BT function...might dual boot so I can save the regular reader for the "Read to Me" function for my daughter. Definitely a lot to absorb about what this thing can do