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

Search This thread

Riggles27

New member
Feb 23, 2015
3
1
Philadelphia
Ah okay I see ill read them then work on it more tomorrow. Ill let ya know how it goes. Thanks.

Solved: I had to do a second format on the SD card through windows after the one on SDformatter or what would end up happening is it would install but go into a boot loop and none of the other fixes would work. But when I did the second format M11 installed and worked fine. I still cant update beyond M11 or I get the syntax error but I'm not worried about it.
 
  • Like
Reactions: p.chi

Kflathau

Member
Nov 22, 2013
6
0
No hope for my nook color I've tried several different roms and variation of ways to get this done. I have 10.2 on my nook and it is super laggy. No matter what I try I get the same result. New sd card. New recovery. New Rom. Different gapps. Nothing to seems to work properly I'm starting to think this doesn't work
Sent from my HTC6435LVW using XDA Free mobile app
 

brwntree

Senior Member
Aug 21, 2014
64
5
Hello - amazing these old devices still have some life due to so many peoples tireless efforts. I recently got a nook color 1.4.3 and thought I might try to put cm on it and have read thru so many articles here and have gone thru so many trials of my own but can never boot on the sdcard. I am lost now and was wondering if anyone might have any advice. I'm just into trying it out for first time on an sdcard and not wanting to touch any aspect of the stock emmc for now - no root nor recovery on emmc - this is a fully ok stock unit. I have a 2gig class-4 kingston card which the nook recognizes but wont boot up on it. I am using win32diskimager9 (as admin) to burn generic-rev8c image and this works fine. I place sdcard into usb-adapter and then into usb slot and PC (win7) sees it in drive J: and burns it fine - when done there is a 400M "boot" partition created and chkdsk sees it ok with 4k byte allocations. Next I place cm11-snap-M11.zip on it and the gapps-kk-20140105.zip that go with it by copy from PC to sdcard - left with 150M on orig 400M boot partition. Move sdcard over to nook and no boot ever (about 33 times so far) on sdcard - just goes to "forever read" stock boot each time and then writes some std android files to the sdcard but def can read the card at this point as a simple external sdcard with files on it. While I realize cm11 may be too recent to run "fast" on this old device I just wanted to see it boot up from sdcard and then take it from there without messing with orig stock emmc. I have also tried other older cm-roms but the prob seems to be booting first not rom. I've tried every diff usb port on my PC (don't have external card reader) and both 2G and 16G (patriot) sdcards and even placing into reg size sdcard adapter and SD slot in internal multi card reader (burns much slower here) all to no avail. Can anyone offer any advice what I might try next to see this ever boot on sdcard? TIA
 

leapinlar

Senior Member
Oct 18, 2006
8,873
3,878
Hello - amazing these old devices still have some life due to so many peoples tireless efforts. I recently got a nook color 1.4.3 and thought I might try to put cm on it and have read thru so many articles here and have gone thru so many trials of my own but can never boot on the sdcard. I am lost now and was wondering if anyone might have any advice. I'm just into trying it out for first time on an sdcard and not wanting to touch any aspect of the stock emmc for now - no root nor recovery on emmc - this is a fully ok stock unit. I have a 2gig class-4 kingston card which the nook recognizes but wont boot up on it. I am using win32diskimager9 (as admin) to burn generic-rev8c image and this works fine. I place sdcard into usb-adapter and then into usb slot and PC (win7) sees it in drive J: and burns it fine - when done there is a 400M "boot" partition created and chkdsk sees it ok with 4k byte allocations. Next I place cm11-snap-M11.zip on it and the gapps-kk-20140105.zip that go with it by copy from PC to sdcard - left with 150M on orig 400M boot partition. Move sdcard over to nook and no boot ever (about 33 times so far) on sdcard - just goes to "forever read" stock boot each time and then writes some std android files to the sdcard but def can read the card at this point as a simple external sdcard with files on it. While I realize cm11 may be too recent to run "fast" on this old device I just wanted to see it boot up from sdcard and then take it from there without messing with orig stock emmc. I have also tried other older cm-roms but the prob seems to be booting first not rom. I've tried every diff usb port on my PC (don't have external card reader) and both 2G and 16G (patriot) sdcards and even placing into reg size sdcard adapter and SD slot in internal multi card reader (burns much slower here) all to no avail. Can anyone offer any advice what I might try next to see this ever boot on sdcard? TIA
Get an external SD card reader. The NC is very finicky how the image is burned to the SD. Go to my NC tips thread linked in my signature and read item A9.

Sent from my SM-T707V using XDA Premium HD app
 
  • Like
Reactions: brwntree

brwntree

Senior Member
Aug 21, 2014
64
5
>Get an external SD card reader. The NC is very finicky how the image is burned to >the SD. Go to my NC tips thread linked in my signature and read item A9.
>Sent from my SM-T707V using XDA Premium HD app[/QUOTE]

hi - two diff external card readers later and a new 32G sandisk brand c4 uSD card and still no joy :eek: I guess I also tried moving the 8c image file to the main C: dir on my PC (jic - from where to burn it from to the uSD) and tried diff vers of disk-imager (.95, .90, .60) and so far nothing seems to help it boot off the uSD card. Any ideas? TIA!
 

wileysam

Member
May 17, 2013
6
1
Linden
To do updates requires upload to Nook

I have a Nook with CM11 on the removable SD card, runs fine but slow with many programs. When I first installed it, I failed to follow the advice given on this forum for installing the recovery/update plug to the Nook BEFORE CM11. So, can't do update - it requires another install.
Also, at the time of CM11 install, the file was over 400MB (I think 435MB) which required a larger partition than the stock one. The post on installing CM11 gave another partioning code.
As much as I have enjoyed the Nook, for daily use I have purchased a NextBook at Walmart for $78 that runs Android 5.0 with 2GB RAM and standard equipment. It also has an SD card slot, so it might be interesting to hack it in the future!!
 

leapinlar

Senior Member
Oct 18, 2006
8,873
3,878
>Get an external SD card reader. The NC is very finicky how the image is burned to >the SD. Go to my NC tips thread linked in my signature and read item A9.
>Sent from my SM-T707V using XDA Premium HD app

hi - two diff external card readers later and a new 32G sandisk brand c4 uSD card and still no joy :eek: I guess I also tried moving the 8c image file to the main C: dir on my PC (jic - from where to burn it from to the uSD) and tried diff vers of disk-imager (.95, .90, .60) and so far nothing seems to help it boot off the uSD card. Any ideas? TIA![/QUOTE]The only advice is to keep trying different options, sdcards, card readers, software and lastly PCs.

Sent from my SM-T707V using XDA Premium HD app
 
  • Like
Reactions: brwntree

brwntree

Senior Member
Aug 21, 2014
64
5
Continuing with this trial have now tried diff burner as in winimage (using restore virtual etc...) and dd from a linux platform (ubuntu) but none of these work either - won't ever boot on sd card. I am wondering now if the assumption that the nook color (or at least the one I'm on) is indeed set to boot off sd card first. It has model number BNTV250 ver 1.4.3 (from device info page) and I read somewhere that this means it's a tablet? and locked from booting on the sd card first? Not sure of this but it might explain the inability to boot on uSD. On the back it has model# BNTV250 (China) but als has fcc# XHHBNTV250-A & ic# 8961A-BNTV250A (not sure if these help or make a diff). Is it poss I'm just wasting my time because this particular model is locked - or if indeed locked, would anyone know is there a way to poss unlock it so it can attempt boot on uSD first? TIA....

PS - this NC also seems to keep repeatedly FC'ing on twitter via toast message which won't work at all to start Twitter in main OS and if uSD is inserted it also messages FC about device.android.com - just wondering if these might be preventing uSD boot first? I've also tried looking up how to resolve these constant FC's but consensus seems getting it back to B&N may be only solution.
 

leapinlar

Senior Member
Oct 18, 2006
8,873
3,878
Continuing with this trial have now tried diff burner as in winimage (using restore virtual etc...) and dd from a linux platform (ubuntu) but none of these work either - won't ever boot on sd card. I am wondering now if the assumption that the nook color (or at least the one I'm on) is indeed set to boot off sd card first. It has model number BNTV250 ver 1.4.3 (from device info page) and I read somewhere that this means it's a tablet? and locked from booting on the sd card first? Not sure of this but it might explain the inability to boot on uSD. On the back it has model# BNTV250 (China) but als has fcc# XHHBNTV250-A & ic# 8961A-BNTV250A (not sure if these help or make a diff). Is it poss I'm just wasting my time because this particular model is locked - or if indeed locked, would anyone know is there a way to poss unlock it so it can attempt boot on uSD first? TIA....

PS - this NC also seems to keep repeatedly FC'ing on twitter via toast message which won't work at all to start Twitter in main OS and if uSD is inserted it also messages FC about device.android.com - just wondering if these might be preventing uSD boot first? I've also tried looking up how to resolve these constant FC's but consensus seems getting it back to B&N may be only solution.
Yes that model number means it is a Nook Tablet, not a Nook Color. They are completely different devices. That is why it will not boot using the Nook Color files. Go to the Nook Tablet forum to get the files necessary to boot from SD.

Sent from my SM-T707V using XDA Premium HD app
 
  • Like
Reactions: brwntree

brwntree

Senior Member
Aug 21, 2014
64
5
Leapinlar - many thanks. This indeed lead in the right direction and not long after I have the uSD booting cm11-kk-444 w/pico-gapps - TY! - :eek:)

Sent from my Nook Tablet
 

gdeiss

New member
Feb 1, 2016
1
1
north-central Idaho
Success!

After a LOT of reading (and rereading) I finally took the plunge and installed CM11 snapshot M11 on an microSD card for my 8gb Nook Color. Couldn't have been smoother, but would have been impossible without leapinlar's wonderful instructions and the many posts and replies by so many others who were doing pretty much doing the same thing I was.

A few years ago I had created a dual-boot card for the NC using CM 7.2 and was not terribly impressed with the result. CM11 is so much better! I'm staying with it for the time being, but sooner or later will undoubtedly be drawn into later incarnations of CM11.
 
  • Like
Reactions: bowguy

maxxum23

New member
Jan 11, 2013
4
0
Infinite boot loop

I have a Nook Color, the first one to come out, I think. The 8GB one. Previously I have used a CM7 on a 4GB SD card and it still works fine. It just isn't smooth. I am trying to get CM11 so I got a 16GB SD card.

Hardware: Patriot 16GB Class 4 SDHC card. A laptop with built in SDHC reader. Another Apple Mac Mini with a Dell monitor that has a card reader. I have tried to follow the steps as best as I could.

1) Using Win32DiskImager, I installed generic-sdcard-v1.3-CM7-9-10-10.1-10.2-11-largest-Rev8c.img

2) Safely unmounted the card, reinserted. Then copied these three files on it.
cm-11-20150831-SNAPSHOT-XNG3CAO3FN-encore.zip
cm-11-20150831-SNAPSHOT-XNG3CAO3FN-encore-recovery.img
gapps-kk-20140606-signed.zip

3) Inserted and booted up the Nook. The Cynoboot starts and installs it all fine. No errors, it says it is going to shut down and does. It finds the gapps and then deletes it as part of the cleanup (I assume it installs it)

4) When I boot it up, the same boot splash image comes up and it attempts to boot but it is stuck in an infinite boot loop.

5) I can boot into the emmc by pressing the n button and also again back to the recovery. It cannot boot the SD-normal.

I tried the same steps using the Mac Mini (Dell monitor acting as the external card reader). Same problem.
Another issue is that the SD card is formatted as only 408MB "boot". The Disk Management does see 3 more partitions, a 902MB, a 1.86GB and a 11.48GB which is probably empty unformatted space.
Any pointers are much appreciated.
 
Last edited:

leapinlar

Senior Member
Oct 18, 2006
8,873
3,878
Did you see the warning that with cm11 you must start with snapshot m11 or older?

And the disk partitioning is correct.

Sent from my SM-T707V using XDA Premium HD app
 
Last edited:

maxxum23

New member
Jan 11, 2013
4
0
Did you see the warning that with cm11 you must start with snapshot m11 or older?

And the disk partitioning is correct.

What I understood from that was that I should not use a Nightly build. Hence I used:
cm-11-20150831-SNAPSHOT-XNG3CAO3FN-encore.zip and
cm-11-20150831-SNAPSHOT-XNG3CAO3FN-encore-recovery.img

Did I miss something?

EDIT: Yes I did!
Looking at the older ROMs, I now see what M11, M10 etc mean. I got the M11 one and it worked. It boots but the issue is that I cannot set up anything because the Google keyboard and some other google stuff crashes immediately.
EDIT2: Tried again with pico sized Open gapps and was able to configure it. Can't find Google Play though.
 
Last edited:

panamamike

Senior Member
Jan 27, 2011
203
9
SD Card boot loop.

Looking for help from the experts.

I've installed the CM 11 M11 snapshot on a 32 GB class 4 Sandisk SDCard:confused:. I burned the generic image, generic-sdcard-v1.3.img, that starts you off with 179MB partition. I use minitool partition to make it a larger to copy the additional zip files. One for the M11 snapshot one for the open_gapps-arm-4.4-nano-20160531. I was not able to find the gapps-kk, looks like this site replaces that, I'm assuming this is the right version as it installed.

It installs fine if I rename files to start with update-. However, when the sdcard boots, it boots into an infinite loop. I see the cyanomodgen screen and again. I tried using the boot menu to boot the emmc, but that doesn't work either, it goes to a black screen. If I remove the SDCard the nook boots fine. I was previously using Nookie which left the Nook pretty much stock.

Any help would be much appreciated.

Regards,

Mike
 

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://forum.xda-developers.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....