Nooting the Nook Color 1.3

For those readers who do not know, the Nook Color actually runs a B&N version of Android. For the first six weeks that I used my Nook Color, I was too busy enjoying to start experimenting with modifying, or replacing, the distributed version. Then I moved to Costa Rica, and ran into a problem. The Nook Color does not support the Ad Hoc topology for WiFi, and my Nokia, and Android phones, only support this topology when running as a WiFi Hot Spot.

The choice was between Nooting, which provides root access, and installing the CM7 version of Android (seenookworks Definitions article for the list of methods). Since I want to keep my Nook Color as an eBook reader, I opted to Noot the distributed version. Using autonooter was not an option, as its development seems to have stopped with version 1.1 of the Nook Color. Consequently, I decide to go with the manual noot option. This post describes my experiences with this project.

When I did a Google search, I found a lot of information about nooting version 1.2 of the Nook Color, but I had already upgraded to version 1.3 to solve problems with the Adobe Flash Player. The discussions on Android Forums and the Barnes and Noble Community forum led me to try manual nooting my Nook Color.

The Barnes and Noble post led me the “I want to root my NC (different methods)” on the nookworks blog. The above post is a good guide to nooting (rooting) various versions of the Nook Color. Since the publishing of the article, there have been a number of changes:

  • Monster Root Pack is now a Google Code Project. I only download the ClockworkMod image for the size of microSD card that I am using. I did not use the all-in-one Monster Rootpack, as it does not have the latest version of noot.
  • The nooter project is also hosted as a Google Code Project. I went with version 4.6.16, instead the 4.5.18 version referenced in the nookworks article.
ClockworkMod provides a way to backup the flash image on the Nook Color. I followed the “Creating the SD Card” instructions on the Monster Rootpack site. On Linux Mint 10, the microSD card appeared as /dev/sdb and /dev/sdb1. Make sure you use the version of ClockworkMod that matches the size of your microSD card. While ClockworkMod only requires a 256mb card, I used a 4gig card to provide room for the backups.
Neither the Monster Rootpack site nor the nookworks site provide any instructions on how to use ClockworkMod. For instructions you need to read the guide on the addictivetips site. CWM is not a touch screen tool. To navigating the menu, you use the following keys:
  • The volume control key allow you to move between menu items.
  • Pressing the n button acts as a selection key.
  • The power button is the back key.
Before proceeding with installing nooter, I performed a backup. If you ever need a fresh image, you can check the ClockworkMod site. No, the site does not containing any instructions on using the CWM tool. After the backup, I installed ManualNooter.

The Boot Loop Problem (Update)

I did run into the boot loop problem caused by conflicting versions of Adobe Flash. When you reboot, everything works fine, until Android Market downloads an automatic update to Adobe Flash Player. On the next boot, the two version conflict and then live gets interesting.

I have read everything about this problem, and came up with a simple workaround. My recommended steps are:

  1. After installing manual noot, immediately perform a backup. This backup establishes a safe restart point should you fall into the boot loop problem.
  2. Reboot the NC.
  3. Before doing any exploring, go to the menu and select the Market icon to open access the Android Market.
  4. Once you are in Android Market, touch the menu icon and then select My Apps.
  5. Touch the Adobe Flash Player 11 selection, and deselect the Automatic Update option. This is easier if you hold your NC in a horizontal position.
  6. If the update was applied before you were able to prevent the install, navigate to the Adobe Flash Player page in the Android Market. Turn off the  Automatic Update option, and uninstall Adobe Flash.
The problem is that the Android Market update cannot modify the /system directory, which B&N mounts as read-only. Instead, it installs the update in the /data directory. The result is that there is a /system/app/FlashPlayer.apk and the update is in /data/app directory. The next time you boot your NC, there are conflicting versions. I am working on a more permanent solution.

The Noot Experience

I powered off my NC, and swapped microSD cards, as I have a lot of music and images stored on the card. I have big fingers, and swapping microSD cards is a challenge. When I turned the NC back on, I immediately notices a change in the boot screen. The initial boot takes awhile, but it does eventually boot.
Once installed, I had to interfaces: the normal B&N interface and Zeam. When presented a menu Home is B&N and Zeam is what it is. Zeam shows all apps, while B&N only shows B&N apps. So far, everything seems to work.
It is important to note that I started from a clean 1.3 update. I had not installed ManualNooter on a previous update. This seems to make a big difference.
Now, back to exploring.
pixelstats trackingpixel
Share

October 20, 2011 · Filed under Android

4 Comments »

  1. Bill Anderson Said,

    October 21, 2011 @ 7:45 am

    I went through all the apps, and only two do not work. Pulse starts, briefly displays the screen, and then dies. News and Weather starts to a blank screen, and then dies. Not sure what is causing this problem. Android Market works just fine. Still need to solve the WiFi problem of connecting to Ad Hoc WiFi networks.

  2. Bill Anderson Said,

    October 22, 2011 @ 6:08 am

    After an early morning su update, Pulse worked. Can’t verify if it was the update that made the difference or not. I switched two of my GMail accounts to the GMail app. It is faster than the B&N Mail app, and I have access to all my contacts. I am only leaving none GMail accounts on the Mail app.

    I have noticed that the NC seems to run faster.

    Nooting was definitely worth the time and effort.

    With everything working, it is time to research the Ad Hoc WiFi issue.

  3. Jonathan Burt Said,

    October 27, 2011 @ 10:27 am

    Hi – the Flash Player fix from this thread worked for me.

    http://forum.xda-developers.com/showthread.php?t=1208896

  4. Bill Anderson Said,

    October 27, 2011 @ 11:32 am

    The fix I mentioned in the article is a temporary work around. I documented a permanent fix in the latest article. I discovered that even though I turned off automatic update, the Android Market decided to install the update the next day. I saw the download occurring and implemented a permanent fix before rebooting.

Leave a Comment

WordPress Mobile