Database Develop

[GUIDE] Install CM7 or CM10 + Recovery to EMMC - ALL NOOK COLORS! (Updated:11/19/12)

***Nook Colors manufactured after May 2011 shipped with a different partition scheme, see post 2 for information about it, or just go ahead with the guide since it doesn't affect much! You can identify these nooks as they have a blue dot sticker on the box***
A gentle reminder, this thread should only be for discussion related to the guide itself. Any CM7/10 related issues should be discussed in the appropriate threads either in General or the Development forum. Thanks!
On with the good stuff:
Prologue
This guide is intended to take you through the (mostly windows-based) steps needed to replace your internal nook color rom with CM7/CM9, gapps and clockworkmod or TWRP recovery all on EMMC. This will work coming from any previous rom, including the latest stock software (excluding dual boot set ups, not supporting that here), no previous rooting is needed for a new nook, however don't forget to boot stock and register the device before flashing to CM7/10.
At this point in CM7 development I am recommending installing a CM7.2 build by mrg666 from this thread or an official nightly/stable 7.2 directly from CyanogenMod: http://get.cm/?device=encore
CM10 is based on Android 4.1 (Jellybean) and builds can be found here: http://get.cm/?device=encore or mirrored here: http://techerrata.com/browse/cm/encore/nightly
If you want to run CM7/10 from the sdcard.. you're in the wrong place! Go check out verygreen's thread here for CM7 or here for CM10.
ALWAYS check the md5 hash for the files you are downloading to make sure you don't have corrupted files. This is a great windows utility to do that: http://code.kliu.org/hashcheck/
On with the guide:
Download 1gb TWRP image from here OR 1gb CWM 3.2.0.1 sdcard image from here. MD5 of .zip: 1319739d33642ed860e8044c3d55aa56. (I made this based on work in this thread. credit: to cmstlist and DizzyDen, and kevank for hosting). You really only need the 1gb image for this guide, no matter what the size of your card is. A smaller image will burn faster, and when you're done with the guide you can reformat the card anyway.
Extract the twrp or clockworkmod .img (if you can't open the file use 7zip)and burn to sdcard using win32diskimager (free). These apps will need to be "run as administrator." If you're not sure how to do this see step 3 here. ***Some internal laptop/desktop readers will not work to do this, you may need an external USB reader if you run into problems.***
While that's burning:
Download CM7 or CM10 from the links above.
Download either CWM 3.2.0.1 flashable .zip from here or TWRP 2.x flashable zip from here.
For CM7 -Download the latest gapps gingerbread needed for market/google services) from http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip
For CM10 download gapps-jb-20121011-signed.zip from here or here
Once your sdcard is done, copy all those files to the sdcard - DO NOT unzip them
Power off your nook. Put the sdcard in, and power on, the nook will boot from sdcard into TWRP or clockworkmod depeding on which you used. TWRP is touch based and easy to use. Navigate in CWM using the vol up/down keys, N button to accept, power button to go back.
Optional: At this point if you want to make a backup of your current EMMC rom (stock or whatever else you're running) you can. Just go to backup.
Go back and navigate to Install .zip from sdcard/Choose .zip
Flash the files in this order:
1. cm .zip
2. gapps
3. Clockworkmod or TWRP .zip
Once you've flashed the files; in the clockworkmod main menu select "wipe data/factory reset" or in TWRP choose factory reset from the wipe menu.
Go back to the main menu, remove the sdcard
Format the sdcard in your computer as fat32 (or use another sdcard) and put it back in the nook and then press reboot system. (CM7 requires the use of an sdcard for storage - thanks pmilford for the tip)
Once you boot into CM7/10, you'll be presented with a welcome screen and you can add your google acct. You need to have wifi access here (obviously..) so hit menu on the status bar and you can set up wifi.
DONE!
Epilogue:
Now you can format the sdcard to use as a storage card in your nook.
To boot into recovery in the future (in order to update to a newer cm7 build/new kernel or make backups) simply hold down power and then choose reboot - recovery from the menu.
If you want to *gasp* restore to stock 1.2.0 flash nemith's stock image (update-nc-stock-1.2-signed.zip) from here using a recovery sdcard.
In CM7: For those looking to get a honeycomb feel to their Nook, I'd recommend this theme. Download the .apk and install it with file manager (or another of your choice), then go to the Theme Chooser app and scroll all the way left and select the theme (name/picture is broken but theme works). Once you've applied it, reboot. (Credits mad-murdock, Bawb3, haxzamatic and joenathane)
In CM7: To set your CPU/Overclock options go to Menu-Settings-CyanogenMod Settings-Performance.
CM7 for the nook color includes mad-murdock's tablet tweaks, so be sure to set up your preferences in the tablet tweak settings also found in the CM settings menu. Some apps, or you, will hide the status bar (eg watching a full screen video) so I like to set "unhide key" to home so that the N button will show the status bar again.
If you're having market problems see this thread for fixes. (Thanks jalexishg)
Want to say thanks? Hit the thanks button below
For more information on CM7 and latest issues/fixes/workarounds please check out the Nightly discussion thread here.
For more information on CM10 and latest issues/fixes/workarounds please check out the Nightly user discussion thread here and the development thread here.
Updating to a newer nightly build
Download latest nightly from CM and put it on the sdcard that's in the nook. Easiest way is to either download it directly on the nook itself, or download on pc and use usb drive mode to copy it to the nook sdcard.
Reboot to recovery (from power menu)
Wipe cache
Install zip from sdcard, flash the new nightly .zip
Reboot
I will try to maintain this guide with new information when needed. If anyone has any comments/suggestions feel free to suggest them below or PM me.
For additional help or just Nook Color related chat join us in #nookcolor on Freenode IRC. (if you have no idea what IRC is click here)

Information for new nook partitions
B+N have made a change as to how they partition the internal storage space on the nook. New nooks are now shipping with new partitions and you can identify these as they have a blue sticker on the box.
Old partitions: 1GB for data (i.e. apps), 5GB for media (books/music/whatever else)
New partitions: 5GB for data, 1GB for media (if you need more media space you use your sdcard)
Clockworkmod 3.2.0.1 (released 6/5/11) is now able to flash roms on the new partition scheme, however you may prefer to restore the old partition method if you like more onboard space for your own files and don't need 5GB for data (apps)
Current options for installing CM7 on the newer partitioned nook are:
1) Just follow the guide above with cwm 3.2.0.1, keep 5GB /data and 1GB /media
2) Follow this guide http://forum.xda-developers.com/showthread.php?t=1094371 to repartition your nook into the older 1GB data/5GB media, and then go back to the top and follow my guide. If you want to repartition using the .zips in DeanGibson's thread, you can flash them using the CWM SD you make in steps 1+2 of my guide above, then go on and flash CM7.

Awesome! I was *just* starting to look for a guide for getting up to 3.0 now that school is done You rock! Perfect timing.

This needs to get pinned if it isn't! Thank you so much!
Can you include instructions how to revert to stock for those "just in case" moments?
Also, maybe include a step if a person wants to install tweaks?

detonate said:
This needs to get pinned if it isn't! Thank you so much!
Can you include instructions how to revert to stock for those "just in case" moments?
Also, maybe include a step if a person wants to install tweaks?
Click to expand...
Click to collapse
Added a link which covers that. Thanks.

goodwork.. and with the bot too.. now we dont have to search for links everytime a noob needs help!
Sent via Cyanogenmod7 Encore RC4 n37/Tapatalk Pro

Mind if I post this guide over on Android Central forums? The one I have posted over there has gotten kind of unwieldy and I was wanting to start from scratch, but these are good!

KitF said:
Mind if I post this guide over on Android Central forums? The one I have posted over there has gotten kind of unwieldy and I was wanting to start from scratch, but these are good!
Click to expand...
Click to collapse
Go for it

Thanks for the clear and concise step by steps. Running off SD right now but tagging just for the day when I decide to go eMMC.

eyeballer said:
DONE!
Click to expand...
Click to collapse
The link to Muffinworld.net does not work. Do you know of another place we can go?

swapdotavi said:
The link to Muffinworld.net does not work. Do you know of another place we can go?
Click to expand...
Click to collapse
Updated OP with a mediafire mirror for now.

Nice guide.

awesome clean strait forward guide! =D thanks!

So this updates to 2.3? I thought this CM7 image was for 3.0? Is there another one I can use to get the 3.0 features?

swapdotavi said:
So this updates to 2.3? I thought this CM7 image was for 3.0? Is there another one I can use to get the 3.0 features?
Click to expand...
Click to collapse
CM7 has always been 2.3, not sure where you read otherwise. There's some honeycomb ports available built from the sdk as source isn't out, feel free to try them, although IMO CM7 is the most stable rom for the nook.

I tried to install CM7 on my nook color and i didnt follow the proper method and instead saved the CM7 file to the root of my sd card and installed the zip through clockworkrecovery without wiping or cache and now im stuck at the android boot screen. It isnt the CM7 skateboard android boot but rather the plain android root boot screen. If anyone could help it would be helpful thank you! IM crying right now about it

ikryptic said:
I tried to install CM7 on my nook color and i didnt follow the proper method and instead saved the CM7 file to the root of my sd card and installed the zip through clockworkrecovery without wiping or cache and now im stuck at the android boot screen. It isnt the CM7 skateboard android boot but rather the plain android root boot screen. If anyone could help it would be helpful thank you! IM crying right now about it
Click to expand...
Click to collapse
This isn't really the place for this post, but if you go back to the first post and look under Epilogue no.4, there's a link to the restore thread.

I've been trying to make a backup of my froyo system in recovery and it keeps on saying that the /system cannot be mounted. Any help would be appreciated.

eyeballer said:
This isn't really the place for this post, but if you go back to the first post and look under Epilogue no.4, there's a link to the restore thread.
Click to expand...
Click to collapse
Thanks a lot!

I'm currently auto-nooted, which leaves the default Nook reader software intact. Will installing CM7 also leave the default Nook reader intact?

[Q] Getting From CM7 to CM10.x

Hi all,
What is the best way to take the TP from CM7 to one of the latest bleeding edge 4.2 or 4.3 builds?
I've been pouring over the forum for three days now and am unsure how to proceed.
I have so many tabs open I'm waiting for Chrome to crash and tell me to go pound sand.
CM7 has been on it since I got ahold of way back in December of 2011. (time for an update, ya think?)
My idea to to fully wipe it but I haven't found a definitive method to do this.
All my data is backed up and I did a nandroid also. So a complete full wipe is very doable.
Current versions: Moboot 0.3.2, CWM v5.0.2.6, and I think that the ACME is at the first release.
WebOS is at whatever version came on it, never used it.
I've read most of RolandDeschain79's "How-to's" and understand the need for re-partitioning for JB,
I'm just not yet sure what's the best path.
(BTW, kudos to Roland for some very informative info and great videos!)
I've got some time on my hands due to lack of work and thought I could give JB some serious testing.
Thanks Gang,
_mr

I'm on the same boat.

Success!
Well, finally got it, not properly sequenced and a boot loop at first, but installed and running. Very smooth so far...
I most definitely did not get the sequence correct, mostly due to not fully understanding how to use CWM6.
Moboot to v0.3.5 from 0.3.2
CWM to v6.0.3.6 <-- Datamedia version 20130926 per milaq's post.
CM 10.2 Nightlies <-- I used "cm-10.2-20131009-UNOFFICIAL-tenderloin.zip"
GApps - JB - 20130813
Here's what I came away with. (Keep in mind I was going for a total wipe of CM7 and had everything backed up.)
1.) The absolute need to re-partition per milaq's post.
I used 'Tailor' with the help of RolandDeschain79's great videos. Thanks Roland!
I set system @ 640MB, re-sized ../media to 8GB, and the remainder went to ../data. (Had to do this twice due to a misstep on my part.)
Tailor is a great app, gotto go find a donate button for that one...
2.) Copied the following to SDCard via WebOS:
update-cm-10.2-20131011-UNOFFICIAL-tenderloin.zip
update-gapps-jb-20130813-signed.zip
update-moboot_0.3.5.zip
update-recovery-clockwork-datamedia-6.0.3.6-20130926-tenderloin.zip
I added/renamed all with the "update-" prefix out of habit. (Perhaps I should have left out CM10.2 until after ACME3 and Tailor.)
2a.) Rebooted to CWM5 recovery.
3.) Flashed CWM6 from v5.0.2.6. This didn't go right. Complained about 'no root' until I reflashed it again later under v6.
Formatted /cache, /data, /system. I did not perform a 'wipe data/factory reset'.
4.) Tried flashing Moboot v0.3.5 with CWM6. Kept aborting. (Didn't take until I ran ACMEInstaller3.)
5.) Ran ACMEUinstaller via Novacom. (Maybe I didn't need to???)
The ACME files I used came from JCSullins goo.im section - Thanks JC!
6.) Ran ACMEInstaller3. Oops. Wiped out all the partitioning I did with Tailor and then installed all the zips in ../cminstall.
At least Moboot v0.3.5 took.
7.) Re-partitioned with Tailor again.
8.) Re-flashed CWM6 - No Root message went away.
8a.) Rebooted to CWM6 recovery.
9.) Formatted /cache, /data, /system again - just for grins.
Re-flashed cm-10.2-20131011-UNOFFICIAL-tenderloin.zip
Rebooted, letting CM load.
9a.) Bootloop...
10.) Booted to WebOS and copied over cm-10.2-20131009-UNOFFICIAL-tenderloin.zip
Rebooted into CWM6.
11.) Flashed the 20131009, rebooted and Viola! it took. Setup the accounts, tested the Wi-Fi. and went to bed...
As you can see I definitely had the sequence wrong, but it was way late for me but like a dog with a bone.
I wasn't going to bed until I had CM10.2 on this puppy.
_mr

[Q] Newbie stuck trying to upgrade from CM9 to CM11. Cannot access ROM Zips in CWM?!

Hello all - I am trying to upgrade from CM9 to CM11 using [ROM] [NIGHTLY] [KitKat] [4.4] CyanogenMod 11.0 nightlies [3.0 kernel],
I repartitioned the drive with Tailor as suggested, and upgraded my CWM to (6.0.4.7)
My problem now is how do i get access the ROM/GAPPs zips? I can copy them over USB on my Win7 Machine to this folder, but CWM doesnt see them/cant access them.
I only have access to this folder in Win7. tried doing a clean install, and still no look.
Computer\cm_tenderloin\SD Card\rom.zip
the only options i have under "choose zip" in CWM are
/sdcard/0/clockworkmod - how do i get the rom zips there? i am totally stumped. i tried ADP to sideload a rom but the device isnt found. thanks in advance!!

Complete install of Android on the device
HI
I was in the same position I'd tried everything. In the end I decided to start from the beginning. What I did was pretty hardcore. I completely uninstalled Android. You need to erase the usb drive in Webos. you do this by booting into WebOS, going to settings/device info/reset options/erase USB drive. Remember before you do any of this get all you data of your device to you PC. Once this is done you are ready to install Android again. Now I found it was easier to upgrade from CM10.2 Data/Media build to CM11. So I installed Android on the device using these four files;
- moboot_38
- CM10.2,update-cm-10.2-20140126-UNOFFICIAL-tenderloin.zip
- update-gapps-jb4.3-20130813-signed.zip
- update-recovery-clockwork-no_metadata-6.0.3.6-20130926-tenderloin.zip
These files are available as a package at rootzwiki.com. There you will also find instructions on how to install android again and how to unistall android as well. Once android is installed now you need to resize the media and data partitions with tailor in webos. Now that this done you are ready to upgrade to CM11. So then booted up my device into Android. Then I connected it to my PC. enable USB conductivity on the device. I created a folder on the device on the now larger data partition (I used the same cminstall name for the folder).Transfered the CM11 (milaq version), Gapps and CMW 6.04.7 to this folder.
I would then boot into recovery. Now were going to update the CMW. choose install from zip find the folder and the CMW 6.0.4.7 file. install it.
once installed boot back into recovery. Now were going to inst CM11. First you need Perform a factory/data reset and wipe/format cache partition. Once this is done your ready to install CM11 and the Gapps. Choose install from zip. Find the cminstall folder you made install. then do exactly the process with the Gapps.
Android CM11 Milaq should work. This worked for me.
Hope this helps.
cheers

Data media install guide
Here is my full guide for installing Data Media Builds:
[ROM GUIDE]How to install Android 4.4.2 Data Media builds on the HP TouchPad

I have this problem
tgg05 said:
HI
I was in the same position I'd tried everything. In the end I decided to start from the beginning. What I did was pretty hardcore. I completely uninstalled Android. You need to erase the usb drive in Webos. you do this by booting into WebOS, going to settings/device info/reset options/erase USB drive. Remember before you do any of this get all you data of your device to you PC. Once this is done you are ready to install Android again. Now I found it was easier to upgrade from CM10.2 Data/Media build to CM11. So I installed Android on the device using these four files;
- moboot_38
- CM10.2,update-cm-10.2-20140126-UNOFFICIAL-tenderloin.zip
- update-gapps-jb4.3-20130813-signed.zip
- update-recovery-clockwork-no_metadata-6.0.3.6-20130926-tenderloin.zip
These files are available as a package at rootzwiki.com. There you will also find instructions on how to install android again and how to unistall android as well. Once android is installed now you need to resize the media and data partitions with tailor in webos. Now that this done you are ready to upgrade to CM11. So then booted up my device into Android. Then I connected it to my PC. enable USB conductivity on the device. I created a folder on the device on the now larger data partition (I used the same cminstall name for the folder).Transfered the CM11 (milaq version), Gapps and CMW 6.04.7 to this folder.
I would then boot into recovery. Now were going to update the CMW. choose install from zip find the folder and the CMW 6.0.4.7 file. install it.
once installed boot back into recovery. Now were going to inst CM11. First you need Perform a factory/data reset and wipe/format cache partition. Once this is done your ready to install CM11 and the Gapps. Choose install from zip. Find the cminstall folder you made install. then do exactly the process with the Gapps.
Android CM11 Milaq should work. This worked for me.
Hope this helps.
cheers
Click to expand...
Click to collapse
I am starting from a cm10.2 rom and i am encountering the same problem that the original poster is.

[Q] Switching the default moboot option to AOKP

Hello everyone, recently i switched my Main Android to AOKP from the build at RootzWiki for Kitkat and choose to remove WebOS. At the first flash i tried Pacman rom but the sound problem was the main reason i tried AOKP. When i flashed pacman, i was using the Touchpad Toolbox and removed the WebOS stuff tried the roms for some stuff and decide to revert to a stable Kitkat one.
So my main problem was the default boot option was Cyanogenmod, as i know, i just need to go to the boot menu and erase the two file for cm based build. After rebooting, the main option was the recovery... I tried to switch recovery and between the 3 recommended in TP Toolbox OP and always the same result, recovery by default... Is there any tool in Android for doing this ? I know there is one in WebOS and if i wanted to keep it i could have used it.
Also, is there any utility to the media partition used for sharing between WebOS and Android in non data/media build ? It is a good 800mb partition wasted in my mind, idk if this was used for the boot menu or anything for recovery. If in result i need to use the toolbox again for reflashing the AOKP build, will it erase my personal data ? I don't mind for doing a partial data erasing (android app) or doing a dirty flash but i just don't want to transfert all my data back from my computer.
Thank for your answer guys.

Atari-San said:
Hello everyone, recently i switched my Main Android to AOKP from the build at RootzWiki for Kitkat and choose to remove WebOS. At the first flash i tried Pacman rom but the sound problem was the main reason i tried AOKP. When i flashed pacman, i was using the Touchpad Toolbox and removed the WebOS stuff tried the roms for some stuff and decide to revert to a stable Kitkat one.
So my main problem was the default boot option was Cyanogenmod, as i know, i just need to go to the boot menu and erase the two file for cm based build. After rebooting, the main option was the recovery... I tried to switch recovery and between the 3 recommended in TP Toolbox OP and always the same result, recovery by default... Is there any tool in Android for doing this ? I know there is one in WebOS and if i wanted to keep it i could have used it.
Also, is there any utility to the media partition used for sharing between WebOS and Android in non data/media build ? It is a good 800mb partition wasted in my mind, idk if this was used for the boot menu or anything for recovery. If in result i need to use the toolbox again for reflashing the AOKP build, will it erase my personal data ? I don't mind for doing a partial data erasing (android app) or doing a dirty flash but i just don't want to transfert all my data back from my computer.
Thank for your answer guys.
Click to expand...
Click to collapse
1)Go back to the boot folder open moboot.default and change CM to AOKP.
2)Jcsullins TPToolbox can see the media partition and access it, so can his CM11 rom or the Evervolv rom. Take a look at this video and thread, it should clear up most of the info for you.
New Super Easy Way Guide and video available
[ROM GUIDE]How to use the TouchPad Toolbox to install Android "The Super Easy Way"(DM & Non-DM)

RolandDeschain79 said:
1)Go back to the boot folder open moboot.default and change CM to AOKP.
Click to expand...
Click to collapse
Thank you, i did not know we could open this file as a plain text file. Thank you. ^_^
Gonna watch the video too. Thank. ^_^

So, after watching your video and mounting the media partition from the TP Toolbox (because my rom cannot open it), it seem there is not anything worth in this partition and it seem there is no delete option while resizing it. So i guess the old commandline recovery could help me to delete the media partition and i could use the toolbox for resizing it to the max. I still don't know if it is safe to delete but seem there's only android stuff in the partition. Thank Rolland for the info again. :highfive:

[Q] Move from CM-11 to CM-13

I have CM-11 (2016-08-15 nightly) installed on my HD+, along with CWM recovery "6046", and am happy with it. However, my other Android devices have Android 6.0, so I thought I'd consider CM-13. Questions:
Is moving to TWRP a requirement? I see statements that CWM recovery is no longer in active development. So what? Are changes being made (see next item) just for the sake of change (a popular activity in software development), or are there real advances that TWRP enables?
In preparation, I downloaded the cm_ovation-ota-MOB31K.161125.zip and open_gapps-arm-6.0-nano-20170117.zip files. I was astounded by the sixe of the latter. What is with the "Open Gapps" files??? I note that the pico one for v4.4 is 2.5 times the size of the one I have been using ( pa_gapps-modular-pico-4.4.4-20141110-signed.zip ). I thought these were supposed to be basic, minimal files.
I'm looking for an install procedure from CM-11. I assume that just means upgrade to TRWP if necessary, and then just use that to install the above zip. I see no discussions of this in this subforum; is it all over in the "Development" forum?
What is the performance of CM-13 like, and is it now stable enough for daily use? I see a long thread peppered with "thank you"s that started two years ago, and I'm wondering if there's anything more succinct.

DeanGibson said:
I have CM-11 (2016-08-15 nightly) installed on my HD+, along with CWM recovery "6046", and am happy with it. However, my other Android devices have Android 6.0, so I thought I'd consider CM-13.
Click to expand...
Click to collapse
FWIW -- I had enjoyed good performance CM11 until about mid last year when many commonly used apps started to become unresponsive and oftentime crashed (force-closed). So over the holidays break I took the plunge and upgraded to Amaces' LN14.1 experimental build lnos_ovation-ota-NMF26Q.170104, so far the performance is as good as it used to be with CM11.
Questions:
Is moving to TWRP a requirement? I see statements that CWM recovery is no longer in active development. So what? Are changes being made (see next item) just for the sake of change (a popular activity in software development), or are there real advances that TWRP enables?
Click to expand...
Click to collapse
Every major release of CM, starting from CM7 -> CM9 -> CM10 to CM11, has required a new and non-backward compatible version of CWM.
I don't believe that CWM 6.0.4.6 can flash CM12 and CM13, and you can find pointers on what recovery versions are needed and are available at https://forum.xda-developers.com/nook-hd/development/boot-sd-external-recoveries-twrp-2-8-3-t3314870.
In preparation, I downloaded the cm_ovation-ota-MOB31K.161125.zip and open_gapps-arm-6.0-nano-20170117.zip files. I was astounded by the sixe of the latter. What is with the "Open Gapps" files??? I note that the pico one for v4.4 is 2.5 times the size of the one I have been using ( pa_gapps-modular-pico-4.4.4-20141110-signed.zip ). I thought these were supposed to be basic, minimal files.
Click to expand...
Click to collapse
I used the minimalist pico package, and then added afterward a couple of missing essential apps like Google Maps.
I'm looking for an install procedure from CM-11. I assume that just means upgrade to TRWP if necessary, and then just use that to install the above zip. I see no discussions of this in this subforum; is it all over in the "Development" forum?
Click to expand...
Click to collapse
The most straightforward route which I found and used is to create a SD-based recovery using the pre-packaged SD image available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778, just unzip and burn the image to SD then add to the card the ROM, GApps, and (EMMC) TWRP zip files you wish to flash. Then boot up the SD card into TWRP, (optionally backup your CM11 ROM system & data), do "wipe /data & factory reset", and flash the 3 zip files and you are set to go.
Alternatively you can try to use a similar approach as outlined at https://forum.xda-developers.com/nook-hd/general/how-to-updating-hd-hd-internal-emmc-to-t2863171 -- i.e., use CWM 6.0.4.6 to flash new TWRP then boot into the new TWRP to wipe and flash new ROM and GApps. This was the route I took when I upgraded to CM12.1 to try it out.

digixmax said:
... Alternatively you can try to use a similar approach as outlined at https://forum.xda-developers.com/nook-hd/general/how-to-updating-hd-hd-internal-emmc-to-t2863171 -- i.e., use CWM 6.0.4.6 to flash new TWRP then boot into the new TWRP to wipe and flash new ROM and GApps. This was the route I took when I upgraded to CM12.1 to try it out.
Click to expand...
Click to collapse
Thanks very much for the info! That's what I did, and it was simple and (reasonably) quick. I note that CM wants to go ahead and install the CWM recovery. I assume I should not let it do so.
Now, to get Titanium Backup to think it's got root. This appears to be a bit of silliness. I tried several "superuser" apps (including the "phh" one), to no avail so far ...
Edit: OK, here it is ...
belfastraven said:
There is still a "bug" I believe, in that when the cm/ln rom is first installed on a device with a clean data partition (after a wipe or factory reset), even though developer options will say you have root, you actually don't. Changing the root selection to something else and then changing it back causes the necessary system file to be created. As long as you don't wipe data, you will not have to do this again on dirty flashes. What is new in the last few months is that, accessible through developer options, there is a rudimentary root manager available in the rom, where you can determine how root requests from various applications should be handled and see which apps have requested root access.
Click to expand...
Click to collapse