[GUIDE] Nook Color Installation Guide for CM7/CM9/CM10/CM10.1/CM10.2/CM11 on SD

Search This thread
D

Deleted member 4861160

Guest
Installing CM11 in 2019

Like some others in this thread, I have just bumped into an old Nook Color and decided I'd give it a spin. I picked it up at a Thrift Store for about $10 and thought it might make a decent weekend project to revive.

As others had mentioned, I installed CM11 M11 snapshot that I got from here. After this, I installed the last available nightly for this device from the CM archive. This worked like a charm, but gapps wouldn't install. What I ended up doing was using the tips thread linked in OP's signature and reading section B5 to install CWM as an alternate recovery. After this, I booted up to the recovery and flashed my gapps from there. This worked like a charm and got me the Play Store. No idea what's going on with the original install script that won't let it run.

FWIW, while CM11 does work, it seems to be unbearably slow with gapps installed. I may end up trying to find one of the earlier CM versions around the web and running that instead, but since CM is dead it seems that most (if not all) the mirrors only have the last CM version that was released for the device (CM11). In any case, it's nice to know that Android KK is at least runable on this old tablet!

Edit: After trying out all the CM builds for this device (except CM9, as I couldn't find any working links for it), I can confirm that practically any version of CM works reasonably well on this device without gapps. If you would like to use gapps and still have a reasonably good experience with this device, I would recommend the last nightly of the original CM10 release (cm-10-20130421-NIGHTLY-encore). If gapps isn't necessary for you, CM11 seems to run pretty well. CM7 is immaculate if you absolutely don't care about much app support, although it certainly is weird to use gingerbread in 2019. All in all, I'll probably stick with CM10 on this one, since having the play store is definitely convenient.

Edit 2: I stand corrected: trying to run any app from the play store on CM10 is extremely slow. Tried installing the ROM with no gapps and then installing the app and that worked much better. All in all, if you intend to use this tablet at all, I would recommend installing any of the CMs available for it and completely ignoring gapps. Do note that running CM7 with gapps is completely doable and usable, but it’s so old that you’ll have trouble getting anything to install.
 
Last edited by a moderator:
  • Like
Reactions: BreyonnaMorgan

psiphi

Senior Member
Jun 4, 2007
159
36
DC
www.stilltruth.com
Yeah, I bought the Nook Color when it came out especially because you could boot off the SD card. It was my first android tablet (that I actually used).

As I recall, the 2nd to last cm 10 build was the best one to use as a daily driver.

You want to use a an Sd card based install on a sandisk class 10 card because it is faster than the memory built into the nook.

At one point, you could buy the cards on ebay ready to boot, but no idea if anyone is still selling them.


Sent from my LGLS992 using Tapatalk
 

impala454

Senior Member
Oct 12, 2008
223
33
Webster, TX
I grabbed one of these and cannot for the life of me get anything to boot besides the stock firmware. Since the links are broken (yes even the ones two posts ago) I'm winging it getting files from wherever. Do I just grab that CM11 image and unzip it to the card? I've created the card w/a FAT32 bootable image and copied the files and the nook still just boots into the stock image. I've tried dding the boot.img file to the card, still nothing. Do I need a custom recovery on there first? Is there some button sequence I'm missing?
 

psiphi

Senior Member
Jun 4, 2007
159
36
DC
www.stilltruth.com
You dont copy the img file directly, you need a program that uses the img file to format and write many files hidden inside the img file. I believe i used win32diskimager but there are several available.

Sent from my LGLS992 using Tapatalk
 

aegrotatio

Senior Member
Sep 9, 2011
102
7
No matter how many times I try, the "cm.zip" that allegedly installs from this process never updates the version of CM on my Nook Color.

What am I doing wrong?
 

tbbj

New member
Jan 21, 2020
1
0
Found an old nook color from in law. Was hoping to make it run Clash of Clans for me as a couch device. Anybody have any advice on the minimal CM needed (with download links available) to run that (google play needed to d/l i assume) before I start to click links and hope to get lucky?
 

SephYuyX

Member
Mar 30, 2018
20
0
Found an old nook color from in law. Was hoping to make it run Clash of Clans for me as a couch device. Anybody have any advice on the minimal CM needed (with download links available) to run that (google play needed to d/l i assume) before I start to click links and hope to get lucky?

Any luck?
 

LesjaReva

New member
May 21, 2020
4
0
Saint-Petersburg
Installation problem

Hi!
I have downloaded the generic-sd image and wrote it to my 4gig sd card with win32imagewriter. I downloaded CM10.2 and the jb gapps files. First It show a little penguin and a bunch of scrolling text ( as was written in Installation Guide). When the installation completes - Nook shuts down. When I power it back up - I saw a little penguin again. And there was written:
mount: wrong fs type, bad option, bad superblock on / dev/ mmcblk0p2, missing codepage or other error. In some cases useful info is found in syslog- try dmesg Itail or so.

What should I do to solve the problem? I do not understand what am I doing wrong?
 

BreyonnaMorgan

New member
Sep 17, 2015
4
0
Barnes & Noble Nook Color
Installing CM11 in 2019

Like some others in this thread, I have just bumped into an old Nook Color and decided I'd give it a spin. I picked it up at a Thrift Store for about $10 and thought it might make a decent weekend project to revive.

As others had mentioned, I installed CM11 M11 snapshot that I got from here. After this, I installed the last available nightly for this device from the CM archive. This worked like a charm, but gapps wouldn't install. What I ended up doing was using the tips thread linked in OP's signature and reading section B5 to install CWM as an alternate recovery. After this, I booted up to the recovery and flashed my gapps from there. This worked like a charm and got me the Play Store. No idea what's going on with the original install script that won't let it run.

FWIW, while CM11 does work, it seems to be unbearably slow with gapps installed. I may end up trying to find one of the earlier CM versions around the web and running that instead, but since CM is dead it seems that most (if not all) the mirrors only have the last CM version that was released for the device (CM11). In any case, it's nice to know that Android KK is at least runable on this old tablet!

Edit: After trying out all the CM builds for this device (except CM9, as I couldn't find any working links for it), I can confirm that practically any version of CM works reasonably well on this device without gapps. If you would like to use gapps and still have a reasonably good experience with this device, I would recommend the last nightly of the original CM10 release (cm-10-20130421-NIGHTLY-encore). If gapps isn't necessary for you, CM11 seems to run pretty well. CM7 is immaculate if you absolutely don't care about much app support, although it certainly is weird to use gingerbread in 2019. All in all, I'll probably stick with CM10 on this one, since having the play store is definitely convenient.

Edit 2: I stand corrected: trying to run any app from the play store on CM10 is extremely slow. Tried installing the ROM with no gapps and then installing the app and that worked much better. All in all, if you intend to use this tablet at all, I would recommend installing any of the CMs available for it and completely ignoring gapps. Do note that running CM7 with gapps is completely doable and usable, but it’s so old that you’ll have trouble getting anything to install.
When you said "Tried installing the ROM with no gapps and then installing the app and that worked much better", what was the app that you were referring to?
 

Liptipiya

New member
Apr 18, 2022
2
1

Fixed my ten year old Nook Color (BNRV200) which was lying unused since 2018 with help from this guide. Thank you. CM11 with no gapps but I found few apps on F-Droid and old apks to suit my needs.

1. Download 'generic-sdcard-v1.3-CM7-9-10-10.1-10.2-11-largest-Rev8c.zip' from top post and extracted the img file.

2. Download 'cm-11-20141008-SNAPSHOT-M11-encore.zip' from here. (link fixed on 29 July 2022)

3. Using 'win32diskimager' burn the img file from Step 1 into SD card.

4. SD card will now have four files, namely MLO, u-boot.bin, uImage and uRamDisk. Copy the zip file from Step 2 to SD card among these four files.

5. Insert SD card to switched OFF Nook Color and power it ON.

6. You would see 'Loading…' message. Wait for Tux to do its stuff and let Nook Color power OFF on its own.

7. You can stop here and next time you power ON your Nook Color, it will boot with CM11 snapshot and you can set it up for use. To update it to latest CM11 Nightly follow these steps after Step 6.

8. Take out SD card and check it again it will now have MLO, u-boot.bin, uImage, uRamDisk, uRecImg and uRecRam files in its 'boot' partition.

9. Download 'cm-11-20160815-NIGHTLY-encore.zip' from this archive and place it into 'boot' partition of SD card among files mentioned in Step 8.

10. Insert SD card to switched OFF Nook Color and switch it ON.

11. Press and hold home () button to enter boot menu.

12. Using volume up/down buttons choose SD card recovery mode and press home () button to select it to apply update.

13. Let Tux do its stuff and wait for Nook Color to power down on its own.

14. Switch your Nook Color ON and set it up for use.

Few apps on F-droid and elsewhere found to be stable on it.
* AntennaPod (for finding and listening podcasts)
* Pretty Good Music Player (bare bones music player)
* ReadEra (ebook reader)
 
Last edited:
  • Like
Reactions: kozmo2k4

Helmut7

New member
Aug 19, 2012
1
0
Howdy, Anyone know how to uninstall GAPPS? I have the latest CM11 nightly from 2016 running on my old Nook Color but made the foolish mistake of flashing GAPPS. If I just wipe the cache/dalvik cache and reinstall the ROM will that get rid of GAPPS or is there another method needed? Cheers.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 89
    Now that CM10 (JellyBean) is in Alpha release (and now Beta and nightlies) for the Nook Color (see post here), I was requested to issue some up-to-date installation instructions to put it on SD.

    These instructions are based on using Verygreen's original size-agnostic SD image and installer which is explained here. I have modified his image so that it works for both CM9 (ics) and CM10 (jb) and attached it below (generic-sdcard... etc). It also is still valid for CM7.

    The CM10.1, CM10.2 and CM11 are official and on the CM site, get latest nightly here (you can get the CM7 ROMs at that site too). You can get the gapps zips here. CM10 needs gapps-jb-20121011 and CM10.1 needs gapps-jb-20130812 and CM10.2 needs gapps-jb-20130813 and CM11 needs gapps-kk and CM7 needs a gapps-gb version.

    Installing a ROM the first time

    Download the ROM, gapp and image files and temporarily store them on your PC. Unzip the image zip (generic-sdcard... attached below) and you should end up with a 300MB .img file that will be used to make the SD. Leave the other two files zipped.

    EDIT: (2/18/15) - If you want to install the newer versions of CM11 with a newly burned SD you must start with the Snapshot version M11. There is something in the newer CM11 zips that causes the installation to not work. Once you have M11 working you can upgrade to the newer versions. See bowguy's post in this thread here: http://xdaforums.com/showthread.php?p=56782698.

    EDIT: (6/8/14) - Updated image to rev8c to fix a minor script error that prevented installation of CM11 post 5/15 and removed a couple of gapp apps that interfered with installing kitkat gapps. This version may be used on all versions of CM. If you already made a prior rev8 SD, just use the uRecRam rev8c rar to update the SD as described below.

    EDIT: (12/10/13) - Updated image to rev8b to create a larger /system to accommodate the larger CM11 and kitkat gapps for 8 and 16GB SDs. If you are installing CM11 to an 8 or 16GB SD, I recommend you start fresh with this version so that a larger /system is created. If you are on a 32GB or larger SD, then the prior rev8a is ok. And CM11 cannot be run on a smaller than 8GB SD.

    EDIT: (12/9/13) - Updated the image again to rev8a to fix a permissions issue when installing the KitKat gapps. If you already made a rev8 SD, just use the uRecRam rev8a rar to update the SD as described below.

    EDIT: (12/6/13) - I just updated the image file to rev8 to make it compatible with CM11 and to make the boot partition 400MB instead of 300MB to accommodate the larger CM and gapps zips. And this version still works properly on all previous CM versions. But, if installing CM7, it is best to use rev7 or earlier.

    EDIT: (8/28/13) - I just updated the image file to rev7 to make it compatible with CM10.2. This version still works properly on all previous CM versions. If you were having trouble with the installer not creating the partitions or installing ROMs because of a poor SD, rev7 also has the revised kernel that is more tolerant of poor SD cards and seems to install smoother than rev5 or earlier versions. Also as of the 4/14/13 version of CM10, this same fix is included in the ROM kernel to help it run better with poor cards. Big thanks to bytte and steven676 for providing this new kernel.

    For those users that want to upgrade their existing SD without reburning with the new image, I have also attached an archive of the updated boot file needed to upgrade. Just extract the file (uRecRam) and copy it to your existing SD boot partition, replacing the file that is there. Then you can update your earlier CM10.1 installation with CM10.2. You must update the gapps too. You can also do the same for rev8a, rev8b and rev8c, but the boot partition will remain 300MB unless updating a rev8 SD.


    In Windows use Win32diskimager or WinImage to burn the image file to your SD (Sandisk Class 4 is the recommended brand). Win32diskimager is free on the web and WinImage is shareware but can be used free to burn images to SD. Be sure to use an external card reader rather than any built in reader in your PC. The built in reader may work but many have found them to be problematic for burning bootable SDs. And it is best to run the programs in administrator mode. In WinImage use the "Restore Virtual Disk Image to physical drive" rather than "write disk". In Linux or OSX, use the "dd" command to burn the image to SD.

    To use Win32DiskImager, find it on the web (here, it's free) and install it on your Windows PC. Open it (be sure to run it as administrator) and select the drive (device) that has your card reader with your SD inserted. Then in the image file box put the location where you have the extracted img file. Then when everything is set right, click on the write button. A warning will pop up asking if you want to proceed. When you have verified that you are going to write to the correct device, click on Yes. (One user overwrote their external USB hard drive by not verifying first). If you get an error message about access denied, it means you are looking at the drive with Windows Explorer. Close Windows Explorer and try again. In fact, it is a good idea to close all unnecessary windows when burning, even your browser.

    Once the SD is burned, temporarily remove the SD from the PC and then reinsert in your PC. Then copy the two other zip files (CM ROM zip and gapps zip) to the SD. Make sure the CM zip begins with cm- and the gapps zip begins the gapps- and both end in .zip. (Don't worry that the SD is now smaller than its original size. That is part of the process in making the SD usable as a bootable SD capable of running CM).

    Take the SD out of the PC and insert it into your powered off Nook Color. Power on the Nook and the SD will take over. It will show a little penguin and a bunch of scrolling text. It will first partition the SD into those partitions necessary to run a ROM. Then it will install CM followed by installing gapps. It will then power down. Power it back up and it should boot to your new CM. Follow the on-screen instructions to set up the Google apps.

    If you get stuck on any of the steps or you just want more information on installation, you can look at Taosaur's excellent blog on installing CM7 to SD. The principle is the same, just substitute CM9 or CM10 for CM7 in his blog and use the files from above. See his blog here.

    Adding some tools

    If you want to read some tips about how to make your SD install work a little better, look at my tips thread linked in my signature. In particular look at the tips in section B in my second post of that thread.

    I recommend that all users add the Alternate CWM for SD as explained in section B5 of my tips thread referenced above. That allows you to clear the dalvik-cache or fix permissions if you need to after a ROM install. It also has the added benefit of allowing you to make a Nandroid backup of the installation. But heed the warning that you CANNOT flash ROMs to SD with it. You must use the verygreen script installer as explained in the next section. You can get the Alternate CWM for SD here and installation is very simple.

    I also recommend that all users install my sdboot script from item B4 of my tips thread so they can use the CMUpdater, GooManager or CyanDelta to update their devices while the SD is still in their Nook as described later.

    Updating to a new ROM

    If you want to later flash an updated CM ROM or gapps zip, put the updated zip file(s) on the boot partition like you did originally and boot. But you need to be sure they are named properly or the installer script will not recognize them. They need to begin with cm-, update-, diiff_, or gapps and end in .zip. After the first tiny flash of the screen, hold the "n" button. The boot menu will come up and you can select the SD recovery and finish booting. The zip(s) will be automatically installed by the SD recovery (the script installer, a little penguin with scrolling text). Or, if you use sdboot as described later, you can just use the power off menu to select reboot and then choose recovery. It should boot automatically to SD recovery so the script installer can install the file you copied to sdboot.

    Ordinarily if you are updating the same ROM (eg, CM10 over a CM10) you do not need to wipe anything. But sometimes if the ROM does not boot properly, you may want to clear dalvik-cache with the Alternate CWM for SD that I talked about earlier. If you are installing a different ROM (eg, CM10 over CM9 or CM7) you should either re-burn the SD or wipe system, data and cache with the Alternate CWM for SD. If you re-burn, the SD will be clean, but you will also lose all files in your SDCARD partition (including any backups that you may have put there).

    Using CMUpdater, GooManager, or CyanDelta on SD installs

    You can use these tools as long as you have your Nook set up properly. For most SD users there is no easy way to copy a zip from the sdcard partition to the boot partition while the card is still in the Nook. And if you take the card out to put it in your PC, you can access the boot partition but not the sdcard partition where the file is stored. The solution is to go to my tips thread linked in my signature and look at item B4. It tells you how to install a script that mounts the boot partition as 'sdboot' under your root directory. Just use a file manager to copy the file from SDCARD to /sdboot. Then use the power off menu to boot to recovery. The script installer will install it as long as it is named properly as described above.

    CM has a new feature (CMUpdater) that makes it easy to download and install updated CM 10 ROMs for those users on emmc. Just go to settings, about tablet, CyanogenMod updates, and follow the prompts. But for SD users you need to be careful, as it may try update your emmc when you are wanting it to update the SD. It will boot to the SD recovery and do nothing, but the next time you manually boot to CWM or TWRP on emmc, it will install it on emmc. You can still use CMUpdater to download the zip, but when it finishes and asks if you want it installed, you have to choose cancel. The ROM zip is downloaded to /sdcard/cmupdater. You need to copy that file to your boot partition (sdboot) and boot to SD recovery and the script installer will install it.

    With GooManager you download a small zip that only has the changed files in it and you flash that. And that works on SD installs as long as you use the script installer. Just copy the diff_ file to the boot partition (sdboot) and boot to SD recovery. With GooManager you can choose which directory you want to download to, so you can tell it to directly download to sdboot. No need to copy later. GooManager does not currently host the CM10 zips. But they do host the Paranoid Android zips.

    With CyanDelta, you use an app installed from Play Store. That app reads, modifies and stores your current ROM zip on your SD for future use. Then, when an update is available, it downloads a small (about 5-10MB) delta file from their site and modifies and renames that stored zip so it has the changes in it. So what you flash is your complete previous ROM zip that has the changed files inserted into it, replacing the ones that were changed. You can use that modified ROM zip with the SD install. Just be sure to only download the delta and let the app modify the zip. Do not let it proceed with installation. The newly modified ROM zip will be in /sdcard/CyanDelta (with the new date). Copy that to the boot partition (sdboot) and boot to SD recovery. The only issue I see is, as part of their modifying they have obviously reduced the compression level of the zip and the normal 150MB zip becomes 250MB. That means you need that much space on your boot partition. If you used my new image file to make your SD in the first place, it should fit since I increased the boot partition size to 300MB.


    -------

    For questions or comments on the installation procedure comment on this thread. For comments or questions on the CM9/CM10 ROMs comment in the CM9/CM10 Discussion thread here or the CM10 General Discussion & Q&A thread here.

    EDIT 1 and 2 removed
    7
    Yes but if the installer script is in the SD image when it comes time to install gapps will I have to start from scratch or can the new script be copied over (and where will I find the new script)?

    OK Try this. Install CM11 but not gapps. Let it boot up and fire up the file manager. Go to settings->General Settings->Access Mode. Make sure you have Root access mode. Now navigate to /system/app and delete Hangouts.apk and GoogleHome.apk This should delete the symbolic links that are causing the problems. Now shutdown and remove the SD card. Copy Gapps to the SD card and reboot into recovery. This should install the gapps. I don't know for sure if this will work but it should and if it doesn't, you won't have wasted a lot of time.
    5
    I am having the same issue on a brand new CM11 SD install with cm-11-20140414-NIGHTLY-encore.zip

    Any help appreciated.


    Thanks !
    Check the OP, I posted rev8c of the image to fix those issues.

    Thanks to Steven676 for finding and posting the script error and to bowguy for finding the gapps apk issue and for testing the fixed image.
    3
    In CM10.1 and older, we set up the filesystems in /init.encore.rc as follows:

    Code:
    on fs
        # mount partitions
        mount vfat /dev/block/mmcblk0p2 /rom sync noatime nodiratime uid=1000,gid=1000,fmask=117,dmask=007
        mount ext4 /dev/block/mmcblk0p5 /system wait ro barrier=1
        mount ext4 /dev/block/mmcblk0p6 /data wait noatime nosuid nodev barrier=1 noauto_da_alloc
        mount ext4 /dev/block/mmcblk0p7 /cache wait noatime nosuid nodev barrier=1

    Note the block device names are written into the mount commands -- this implies that the SD card installer needs to change /init.encore.rc in the initramfs (ramdisk) when installing.

    For CM10.2, we do things differently:

    Code:
    on fs
        # mount partitions
        mount_all /fstab.encore

    Where did the device names go? They've all moved into that /fstab.encore file, which looks like this:

    Code:
    #######################
    #    
    # The filesystem that contains the filesystem checker binary (typically /system) cannot
    # specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
    ######################
    /dev/block/mmcblk0p5 /system ext4 ro,barrier=1 wait
    /dev/block/mmcblk0p6 /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc wait,check
    [...]

    Basically, where the installer previously had to change /init.encore.rc to refer to SD card partitions instead of eMMC ones, it now needs to change /fstab.encore in the same way.
    Ok, I will see what I can do.

    Edit 8-28: The OP has now been updated with rev7 of the image zip. It works now on CM10.2 and all previous CM versions.

    Sent from my Nook HD+ running CM10.1 on emmc.
    3
    It sounds like you are using a new SD card. You say the old ones work. It could the SD that is malfunctioning.

    Sent from my BN NookHD+ using XDA Premium HD app
    I can confirm this behavior. Brand new SD card and I have done this a few times. ;)
    11/14 nightly fails exactly as he describes. Trying to find a ROM that will work. Will report back.
    M12 fails (/tmp/updater syntax error No build image ?? Not sure - went by pretty fast.)
    M11 works !!!! Something happened between 10/08 and 11/12 (m11 - m12). I will now try to flash 11/14 nightly over M11. BRB
    11/14 showed the same error during install but booted up fine.

    Solution for new install - Initial ROM is M11 then the nightlies work fine....