Database Develop

[Q] Unable to Backup to SD in CWM on Nook HD

Hello,
First off, thanks to e.mote for the CyanogenMod 10.1 for Dummies guide and to the work put in by verygreen, leapinlar and bokbokan. The guide was simple and straightforward, I installed CM10.1 and CWM (seemingly) without a hitch.
However, when attempting to do a baseline backup, I'm running into some problems. I've searched the forum overall and gone through pages and pages in the Nook sections and not found any real solution. On my 8GB HD, when rebooting to recovery and attempting to backup to an SD card, I'm having the following issues:
When CWM loads, I get a "warning: no file_contexts" message. I've read mixed things about whether this is significant or not and what to do to correct it.
When I go to backup and restore>backup it seems to backup to the SD card without a hitch (although it has shown differing amounts of free space on the cards whenever I've attempted this). But when I insert the card into my computer to copy the backup, the only thing on the card is a folder called "LOST.DIR" and all the space but 3.1MB is free. I've done this 3-4 times so far, with two different microSD cards (one 4GB, one 32GB). I've both checked it and formatted the card (in FAT32) on a computer running Windows XP and one running OSX. Same results on both every time.
At some point when attempting to do the backup, the screen of the Nook begins to flash/flicker and doesn't stop until I restart it.
The first time I tried to do the backup, after I tried to restart, it didn't boot back up and the power button was unresponsive. Possibly this was due to overheating? I plugged it into the charger and it started up on its own after about 10 minutes.
Anyone else encounter this? Any solutions. Obviously I want to be able to back things up. I just rooted the device this evening, so I'd rather to not have to go through the install process all over again rather than have a proper backup.
Thanks!

You need to tell us which version of CWM you are running. And is installed to internal memory or SD?
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
You need to tell us which version of CWM you are running. And is installed to internal memory or SD?
Click to expand...
Click to collapse
Ah, of course! Sorry, that's what I get for doing this so late. Okay, so it's installed to the internal memory. The files I downloaded were this and this. When I reboot into recovery is says "EMMC CWM-based recovery v6.0.3.6".
Thanks

elcapitansmirk said:
Ah, of course! Sorry, that's what I get for doing this so late. Okay, so it's installed to the internal memory. The files I downloaded were this and this. When I reboot into recovery is says "EMMC CWM-based recovery v6.0.3.6".
Thanks
Click to expand...
Click to collapse
Ah, ok. That means you have the newest version which puts the backup on internal memory. If you look at the menu choices closely, you will see it says to internal sdcard and the other choice is to external sdcard. So you will not find the backup on your external card.
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
Ah, ok. That means you have the newest version which puts the backup on internal memory. If you look at the menu choices closely, you will see it says to internal sdcard and the other choice is to external sdcard. So you will not find the backup on your external card.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! That'll teach me to just blindly follow instructions rather than looking around and exploring on my own - I didn't even notice the "Backup to External SD" option. So, thanks for your patience, your work on this and your speedy replies. Seems like all is well now.

Stuck on cyanoboot, nothing helps

Hello everybody,
I have trivial problem with cyanoboot - I've bought used NOOK HD+ after someone tried to install cyanogenmod on it, and except holding cyanoboot at screen with an SD card (that I've prepared accordingly leapinlar's page), it has next issues:
1) there is absolutely no response, when I try to turn it on without an SD card;
2) when the SD was untouched by me, it had some other cyanoboot installed on it but with this version nothing in the cyanoboot menu worked: there was a menu and errors in the console every time I've done everything. But, at least, it loaded.
And, question ahead - is it some easy way to figure out whether my B&N is bricked?
I've already tried so many options not only from xda to get some from the tablet and now I'm nearly desperate.
Regards.

mallniya said:
Hello everybody,
I have trivial problem with cyanoboot - I've bought used NOOK HD+ after someone tried to install cyanogenmod on it, and except holding cyanoboot at screen with an SD card (that I've prepared accordingly leapinlar's page), it has next issues:
1) there is absolutely no response, when I try to turn it on without an SD card;
2) when the SD was untouched by me, it had some other cyanoboot installed on it but with this version nothing in the cyanoboot menu worked: there was a menu and errors in the console every time I've done everything. But, at least, it loaded.
And, question ahead - is it some easy way to figure out whether my B&N is bricked?
I've already tried so many options not only from xda to get some from the tablet and now I'm nearly desperate.
Regards.
Click to expand...
Click to collapse
If your cyanoboot on the SD has a menu, that is the wrong one to be using if you want to do modify internal memory. Go to my HD/HD+ CWM thread linked in my signature and make a new bootable CWM SD per the instructions there. Then you can use it to flash stock back to internal or another ROM like CM.
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
If your cyanoboot on the SD has a menu, that is the wrong one to be using if you want to do modify internal memory. Go to my HD/HD+ CWM thread linked in my signature and make a new bootable CWM SD per the instructions there. Then you can use it to flash stock back to internal or another ROM like CM.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thank you for answer, but currently I have no menu on cyanoboot, just holded cyanoboot logo. Menu was at first in the cyanoboot on the SD card, that I have nothing to do with - it was configured by previous owner, was broken and cause error message on the console as the response on every step I take in that menu. And of course - because this menu was useless - I just rewrited new image on it, as it described at the forum.

mallniya said:
Thank you for answer, but currently I have no menu on cyanoboot, just holded cyanoboot logo. Menu was at first in the cyanoboot on the SD card, that I have nothing to do with - it was configured by previous owner, was broken and cause error message on the console as the response on every step I take in that menu. And of course - because this menu was useless - I just rewrited new image on it, as it described at the forum.
Click to expand...
Click to collapse
So what is your issue?
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
So what is your issue?
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
My issue is stucking on cyanoboot logo, menu never comes up whatever I do with the card. I've tried really many options from the forum, especially from this page:
http://forum.xda-developers.com/showthread.php?t=2317500
and nothing helps.
Without SD card tablet doesn't work at all.

mallniya said:
My issue is stucking on cyanoboot logo, menu never comes up whatever I do with the card. I've tried really many options from the forum, especially from this page:
http://forum.xda-developers.com/showthread.php?t=2317500
and nothing helps.
Without SD card tablet doesn't work at all.
Click to expand...
Click to collapse
Which image did you put on the SD?
Sent from my SCH-i705 using XDA Premium HD app

leapinlar said:
Which image did you put on the SD?
Sent from my SCH-i705 using XDA Premium HD app
Click to expand...
Click to collapse
I use Win32DiskImager to create SD (either 1GB and 8GB) both from NookHDplus-bootable-CWM-6028-for-stock-4GB-rev4-(05.15.13).zip and NookHDplus-bootable-CWM-6028-for-stock-small-rev4-(05.15.13).zip. Also tried just put NookHDplus-bootable-CWM-6028-for-stock-BOOTFILES-r4-(05.15.13).rar on the card with activated partition.

mallniya said:
I use Win32DiskImager to create SD (either 1GB and 8GB) both from NookHDplus-bootable-CWM-6028-for-stock-4GB-rev4-(05.15.13).zip and NookHDplus-bootable-CWM-6028-for-stock-small-rev4-(05.15.13).zip. Also tried just put NookHDplus-bootable-CWM-6028-for-stock-BOOTFILES-r4-(05.15.13).rar on the card with activated partition.
Click to expand...
Click to collapse
On that last one I hope you meant the extracted files from the BOOTFILES rar.
But it shows the cyanoboot logo when you boot with the SD inserted? And nothing when the SD is removed? That means it is trying to boot from the SD, just not completing. Have you tried the TWRP versions in my thread?
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
On that last one I hope you meant the extracted files from the BOOTFILES rar.
Click to expand...
Click to collapse
Exactly.
leapinlar said:
But it shows the cyanoboot logo when you boot with the SD inserted? And nothing when the SD is removed? That means it is trying to boot from the SD, just not completing. Have you tried the TWRP versions in my thread?
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Nope, but now I'm using both NookHDplus-bootable-SD-TWRP-2.6-for-emmc-4GB-rev0-(09.18.13).img and extracted NookHDplus-bootable-SD-TWRP-2.6-for-emmc-BOOTFILES-rev0-(09.15.13).rar - the only difference is other level of stucking - instead of holded cyanoboot logo it shows after cyanoboot logo some other logo and nothing is occurs, except for this recovery power down itself after about 5 minutes.

Any ideas what should I do next?

I also found out, that with TWRP tablet is recognized by adb. Is it possible use it to solve the problem?

Duplicate an SD card install.

Is there any way to duplicate an SD card install for my Nook Color? I have the latest Cyanogenmod nightly on an existing card but I can't seem to burn a new nightly starting from scratch. The new nightlies all update the existing card. I figure if I can just duplicate the existing, working card I can update it.
As a side note the new installations all give me an endless reboot at the cyanogen logo. I am using Win32Disk Imager, generic-sdcard-v1.3-CM7-9-10-10.1-10.2-11-largest-Rev8b.img, and can't get past this reboot loop. The cards all had working installs on them previously so I know there is not a compatibility issue with them.
Thanks in advance
f1jim

You can use win32diskimager to make an image of the existing card and write that image back to a new card. But be warned, depending on the size of the existing SD, the image can be quite big (same size as the card).
On writing the new 8b image, are you letting it boot first to set up the partitions before you add the CM zip? Also, you said those cards had working installs on those before writing the image. Did you format the card first using SDFormatter? You need to to clear the prior installation. Use size adjustment and overwrite options too.
Sent from my SCH-i705 using XDA Premium HD app

Thanks
I will try your suggestion on booting first without the zip file.
Thanks
f1jim
leapinlar said:
You can use win32diskimager to make an image of the existing card and write that image back to a new card. But be warned, depending on the size of the existing SD, the image can be quite big (same size as the card).
On writing the new 8b image, are you letting it boot first to set up the partitions before you add the CM zip?
Sent from my SCH-i705 using XDA Premium HD app
Click to expand...
Click to collapse

f1jim said:
I will try your suggestion on booting first without the zip file.
Thanks
f1jim
Click to expand...
Click to collapse
see my edit above. You need to format the sd first.
Sent from my SCH-i705 using XDA Premium HD app

I formatted the SD card, used Win32DiskImager, took the card out of the machine, reinserted it, inserted it in the Nook, It did it's thing till it got to the line that looks for the file starting with CM or ends in zip. It goes no further and just flashes a cursor. I take the SD card out of the nook and with it in the PC copy the nightly zip. I then insert it in the Nook and boot up. It appears to be installing everything then shuts down.
I reboot and it starts the reboot cycle over and over. Am I missing a step in the process?
Also I open Win32DiskImager and don't see a way to copy the working SD install. Seems like it only will read and write .img files.
Thanks
f1jim

Win32diskimager is not supposed to copy the install. It is supposed to create an image (read the card to an img file) of the existing SD. Then use it to write that img file back to a new SD.
And when you formatted you used SDFormatter with the options I suggested? If you did not, then you only changed the SD headers and did not erase the prior data and it is still there when the SD partitions itself.
Sent from my BN NookHD+ using XDA Premium HD app

I can't figure out how to get Win32DiskImager to make an image of the existing install. I see no menu selection to allow this. Are you sure you are not thinking of another program.
Or am I not seeing something obvious?
f1jim
leapinlar said:
Win32diskimager is not supposed to copy the install. It is supposed to create an image (read the card to an img file) of the existing SD. Then use it to write that img file back to a new SD.
And when you formatted you used SDFormatter with the options I suggested? If you did not, then you only changed the SD headers and did not erase the prior data and it is still there when the SD partitions itself.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse

f1jim said:
I can't figure out how to get Win32DiskImager to make an image of the existing install. I see no menu selection to allow this. Are you sure you are not thinking of another program.
Or am I not seeing something obvious?
f1jim
Click to expand...
Click to collapse
Yes the obvious thing you are missing is the read button. The read/write buttons mean read or write the card. When you press the write button with the 8b image file in the box, it writes that image to the card. When you select the read button, it reads the card and makes a new image file that you have typed into the name box. The new image file will be the same size as your whole SD. Then you can use that new image file to write to a new SD. It does not guarantee that the new card is bootable though. Just try it.
You did not answer my question about using SDFormatter.
Sent from my BN NookHD+ using XDA Premium HD app

When I run the program the box that opens says image file and a white box that's empty below it. To the right of that box is a blue navigation button that allows one to navigate to an .img file. Still farther right is a device box that only allows the selection of my removable SD drive. The read and write buttons are grayed out till I select an .img file in the white box. Since my current useable SD card had no .img file on it how do you propose I select the SD card to write an image of?
Honest, I have looked this over with a fine toothed comb but cant see how to select my SD card to write an image. The blue selection box will only look for .img files. Till that happens nothing else is an option.
I have been formatting the SD card with Mini Tool Partition Wizard. I format the SD card using Fat32. After that the PC sees it just fine. I will look for SDFormatter and use it.
Sorry if I am overlooking something that should be obvious to me. Your help is greatly appreciated.
f1jim
leapinlar said:
Yes the obvious thing you are missing is the read button. The read/write buttons mean read or write the card. When you press the write button with the 8b image file in the box, it writes that image to the card. When you select the read button, it reads the card and makes a new image file that you have typed into the name box. The new image file will be the same size as your whole SD. Then you can use that new image file to write to a new SD. It does not guarantee that the new card is bootable though. Just try it.
You did not answer my question about using SDFormatter.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse

What happens when you type a new file name in the box? Does the read button come ungreyed? Pick a location and type a name like mycard.img.
And as I told you, unless you use SDFormatter with the overwrite and size adjustment on, you are not really formatting, just writing new headers.
Sent from my BN NookHD+ using XDA Premium HD app

I used the name "test" and yes, the read button became ungreyed. I hit read and it continued for awhile until an error message popped up at 3%. It says "An error occurred when attempting to read data from handle. Error 1117: The request could not be performed because of an I/O device error. Tried it twice. Same outcome.
f1jim
leapinlar said:
What happens when you type a new file name in the box? Does the read button come ungreyed? Pick a location and type a name like mycard.img.
And as I told you, unless you use SDFormatter with the overwrite and size adjustment on, you are not really formatting, just writing new headers.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse

Since it is obvious you are going to continue to have issues with this method, I suggest you abandon that and use one of the two below.
1. Use SDFormatter with the size adjustment and overwrite options selected. This truly erases everything on the SD. Other methods, including Mini-Tool, just 'quick erase', leaving old data there when it re-partitions itself back to the old partition structure. So when CM tries to run it has the old data from your prior install and hangs.
Or
2. Go to my NC Tips thread linked in my signature and get the Alternate CWM from item B5. After you have burned the image and let it boot the first time to repartition itself and installed the CM zip, install the Alternate CWM and boot to it. Use that to do a wipe data/factory reset. That clears your old data from your old install so CM can boot properly. If it still hangs using this method, you may have to go to mounts and storage and format /system. Then re-install CM using the copy to boot partition method, not the Alternate CWM.
Sent from my BN NookHD+ using XDA Premium HD app

Once more......
I'll give this a try once again. There has to be something obvious I am overlooking. I have 2 SD chips that have previously worked with android installations on them. Following your advice this is what I have done with both of them and with no success:
I have formatted each chip with SDFormatter using the OVERWRITE and AUTO SIZE options turned on. I then use Win32DiskImager to burn the image generic-sdcard-v1.3-CM7-9-10-10.1-10.2-11-largest-Rev8b.img. I then copy the latest nightly to the root directory and boot the chip in the Nook Color. It appears to go through the setup process and shut down properly. Upon rebooting the nook color it comes up to the Cyanoboot Universal Bootloader and says loading. Then the screen goes dark and it reboots back to the Cyanoboot Universal Botloader screen and reboots yet again. It seems stuck in this loop. Same issue using both SD chips.
I'm utterly lost.
Thanks
f1jm
leapinlar said:
Since it is obvious you are going to continue to have issues with this method, I suggest you abandon that and use one of the two below.
1. Use SDFormatter with the size adjustment and overwrite options selected. This truly erases everything on the SD. Other methods, including Mini-Tool, just 'quick erase', leaving old data there when it re-partitions itself back to the old partition structure. So when CM tries to run it has the old data from your prior install and hangs.
Or
2. Go to my NC Tips thread linked in my signature and get the Alternate CWM from item B5. After you have burned the image and let it boot the first time to repartition itself and installed the CM zip, install the Alternate CWM and boot to it. Use that to do a wipe data/factory reset. That clears your old data from your old install so CM can boot properly. If it still hangs using this method, you may have to go to mounts and storage and format /system. Then re-install CM using the copy to boot partition method, not the Alternate CWM.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse

f1jim said:
I'll give this a try once again. There has to be something obvious I am overlooking. I have 2 SD chips that have previously worked with android installations on them. Following your advice this is what I have done with both of them and with no success:
I have formatted each chip with SDFormatter using the OVERWRITE and AUTO SIZE options turned on. I then use Win32DiskImager to burn the image generic-sdcard-v1.3-CM7-9-10-10.1-10.2-11-largest-Rev8b.img. I then copy the latest nightly to the root directory and boot the chip in the Nook Color. It appears to go through the setup process and shut down properly. Upon rebooting the nook color it comes up to the Cyanoboot Universal Bootloader and says loading. Then the screen goes dark and it reboots back to the Cyanoboot Universal Botloader screen and reboots yet again. It seems stuck in this loop. Same issue using both SD chips.
I'm utterly lost.
Thanks
f1jm
Click to expand...
Click to collapse
Nightly of what, CM11? And what date? A fresh download?
And as the text is scrolling past are there any error messages? Are you installing in two steps? In other words are you letting it boot first to make the partitions followed by copying the CM zip and booting again?
Sent from my BN NookHD+ using XDA Premium HD app

Once again
Yes, the nightly CM11. cm-11-20140510-NIGHTLY-encore.zip to be exact. Yes, fresh downloiad. I will try to boot to the chip before copying over the nightly this time.
Fingers crossed.
f1jim
leapinlar said:
Nightly of what, CM11? And what date? A fresh download?
And as the text is scrolling past are there any error messages? Are you installing in two steps? In other words are you letting it boot first to make the partitions followed by copying the CM zip and booting again?
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse

No luck.
This time I started from scratch again. Formatted the chip with SDFormatter(4.0), Used a fresh downloaded copy of the generic img file. Botted it in the Nook. No error messages and it stopped at the place where it looks for the zip file. Pulled the chip, copied a fresh download of the CM11 nightly. Popped in the chip and started up the Nook. It went through the installation process with no error messages and properly shut itself down. Rebooted the Nook only to have it load the Cyanoboot universal bootloader page, says it's loading....then it goes black and reboots to the same bootloader page.
Any more ideas that don't involve dynamite?
f1jim

f1jim said:
This time I started from scratch again. Formatted the chip with SDFormatter(4.0), Used a fresh downloaded copy of the generic img file. Botted it in the Nook. No error messages and it stopped at the place where it looks for the zip file. Pulled the chip, copied a fresh download of the CM11 nightly. Popped in the chip and started up the Nook. It went through the installation process with no error messages and properly shut itself down. Rebooted the Nook only to have it load the Cyanoboot universal bootloader page, says it's loading....then it goes black and reboots to the same bootloader page.
Any more ideas that don't involve dynamite?
f1jim
Click to expand...
Click to collapse
Before doing anything drastic, read this.
http://forum.xda-developers.com/showpost.php?p=52506409&postcount=283.

Once again....
I most definitely have a Nook color. I think I mentioned early on I have a chip with the latest nightly on it and it works beautifully. The other chips used to as well. I just can't figure out why they stopped working when I tried to start from scratch with them.
I do appreciate your efforts in helping. It's not the end of the world if I can't get them to work. I'll keep trying.
f1jim
hwong96 said:
Before doing anything drastic, read this.
http://forum.xda-developers.com/showpost.php?p=52506409&postcount=283.
Click to expand...
Click to collapse

f1jim said:
This time I started from scratch again. Formatted the chip with SDFormatter(4.0), Used a fresh downloaded copy of the generic img file. Botted it in the Nook. No error messages and it stopped at the place where it looks for the zip file. Pulled the chip, copied a fresh download of the CM11 nightly. Popped in the chip and started up the Nook. It went through the installation process with no error messages and properly shut itself down. Rebooted the Nook only to have it load the Cyanoboot universal bootloader page, says it's loading....then it goes black and reboots to the same bootloader page.
Any more ideas that don't involve dynamite?
f1jim
Click to expand...
Click to collapse
What are the sizes of these two chips you have used previously? You know CM11 requires larger chips.
Sent from my BN NookHD+ using XDA Premium HD app

Once again....
Both chips are 8Gb. The one that is working properly is 16Gb.
f1jim

[Q] Need to return Nook HD+ to Stock ROM

Hello,
I have 2 weeks to return my Nook HD+ to B&N for a warranty replacement
due to a charging issue (it randomly reports the battery strength at 1% and
then shuts down even though the battery has a charge). I've read and re-read
various threads but haven't been able to figure out how to return the Nook to
the stock rom. I have CM11 installed on emmc with TWRP. It's been nearly
a year since I installed it and can't find a back-up recovery or even remember
if I made one. For the most part, the guides I've found refer using to CWM
rather than TWRP. Any help or guidance would be much appreciated.

Go to my HD/HD+ CWM thread linked in my signature and make a new bootable CWM SD per item 1a. An alternate to that is to go to item 5 and flash the v6036 CWM to internal memory replacing your TWRP. Use the CWM to flash the plain stock zip from item 6. Follow that with a factory reset with CWM. You cannot use the TWRP you now have on internal memory to flash the stock zip. It will fail.
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
Go to my HD/HD+ CWM thread linked in my signature and make a new bootable CWM SD per item 1a. An alternate to that is to go to item 5 and flash the v6036 CWM to internal memory replacing your TWRP. Use the CWM to flash the plain stock zip from item 6. Follow that with a factory reset with CWM. You cannot use the TWRP you now have on internal memory to flash the stock zip. It will fail.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for your reply. Prior to posting my question, I've tried to follow your guide.
Please take a look at the the steps I took and let me know what I should have done differently.
I only had a 2gb SD card on hand. Anyway, here are the steps I took:
Formatted a 2gb SD card with SD Formatter. Then with MiniTool Partition wizard the partition was set as "active".
Next Win32DiskImager was used to write NookHDplus-bootable-CWM-6027-for-emmc-stock-small-rev3-(02.03.13) to the SD
card. At that point, the card had a capacity of something like 110 MB so I used MiniTool Partition Wizard again to extend
the volume using the remaining unallocated space on the card. I then copied NookHDplus-factory-2.2.0-plain-stock to the SD card.
When I put the card back in the Nook and hit the start button, the Nook boots right into the Cynoboot Universal Bootloader and loads
CM11.
Since I already have TWPR, is there a way to install a Stock Rom with TWRP and then remove TWRP?
Thanks,
JDK

You combined two different methods to make the SD and messed it up.
No, you cannot use that internal TWRP to flash the stock.
You should do what I said earlier. Download the v6036 CWM zip from item 5 and boot to internal TWRP and flash it. It will replace TWRP with CWM. Then boot to internal CWM and flash the stock zip as I earlier instructed.
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
You combined two different methods to make the SD and messed it up.
No, you cannot use that internal TWRP to flash the stock.
You should do what I said earlier. Download the v6036 CWM zip from item 5 and boot to internal TWRP and flash it. It will replace TWRP with CWM. Then boot to internal CWM and flash the stock zip as I earlier instructed.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
It makes much more sense to me now. My mistake was that I did combine both methods. Since these steps can all be done from within the Nook, to keep it simple for a simple guy such as myself, , I don't need to be writing any files to an SD card. I'll give your revised instructions a try and let you know how it works out. I've used CWM on my phones, so I feel like I have of pretty good chance of getting it right this time! I guess I just needed to be walked through this, step by step. Thanks for giving me some more detailed instructions.

leapinlar said:
You combined two different methods to make the SD and messed it up.
No, you cannot use that internal TWRP to flash the stock.
You should do what I said earlier. Download the v6036 CWM zip from item 5 and boot to internal TWRP and flash it. It will replace TWRP with CWM. Then boot to internal CWM and flash the stock zip as I earlier instructed.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
It worked flawlessly this time. Thanks again for your help.

hd+ dual bootable stock/CM11-not mess w/stock

I want to install CM11 onto my external SDcard, not touching the B&N stock OS or rooting it in any way , so as not to void the warranty. #1 is this possible?
I built the SDcard, creating partitions: BOOT (0x0c FAT32 LBA & set Active),SYSTEM, DATA partitions.
I downloaded Succulent's "cm_ovation_11.0_02JUL2014_HD_SDC" file, unzipped it and copied the 6 files from it (MLO first)
Booted the HD+ but it didn't boot to sd,-- only did the normal Nook boot and hung at 99% loading the nook OS.
I then saw something about needing to install CWM Recovery first and boot that, so I located a download for CWM, but found it contains the same files as Succulent's "cm_ovation......" file (MLO, etc.). So if I were to extract that to the BOOT partition, I'd overwrite what I extracted from his zip.
So I'm missing some pieces to the trick....

Try using bokbokan's version and instructions here:
http://forum.xda-developers.com/showthread.php?t=2583952
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
Try using bokbokan's version and instructions here:
http://forum.xda-developers.com/showthread.php?t=2583952
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thank you, but I had customized my partitions, and was hoping to stay with them, versus overwriting them with an image someone made that has pre-picked partitions. That is, unless somehow I can resize the partitions he made (and at which point in the process?) On mine I had 4 partitions. the last one was just an NTFS one, 6GB, I was hoping to keep available for just general storage, not necessarily for KitKat's use.

See http://forum.xda-developers.com/showpost.php?p=49007593&postcount=84 for pointers on creating CM11 SDcard with customized partition sizing. You should be able to create and maintain a 4th partition (but you'd need to figure out how to mount the partition so as to make it accessible to Android and/or your PC OS).

cm11 boot to sd
Ok, I must be missing some simple step.
In that link Digimax sent me, I believe I followed all steps. I ended up with these files on the BOOT partition (as seen in windows):
The 6 files extracted from sdcard-ovation-cm11.0-v1.img
pa_gapps-modular-mini-4.4.4-20141121-signed
cm-11-20140804-UNOFFICIAL-bok-ovation
a folder called LOST.DIR (not sure what that's from)
I choose "Boot to CWM Recovery" and I first did a backup. Then I selected "Install ZIP" then "Choose zip from sdcard" & I see
/sdcard/
- 0/
- clockworkmod/
That's it. Nothing else. Selecting either one of these displays no zip files. What am I doing wrong? In that post, step 4 it mentions "pair" of zip files. I assume though the 2nd item in the "pair" is the Gapps zip. Cuz for HD+ all I see is one file: cm-11-20140804-UNOFFICIAL-bok-ovation. (it doesn't have "sgt7" in the name anymore.) I assume I don't need the one for the regular HD model.

baytee said:
Ok, I must be missing some simple step.
In that link Digimax sent me, I believe I followed all steps. I ended up with these files on the BOOT partition (as seen in windows):
The 6 files extracted from sdcard-ovation-cm11.0-v1.img
pa_gapps-modular-mini-4.4.4-20141121-signed
cm-11-20140804-UNOFFICIAL-bok-ovation
a folder called LOST.DIR (not sure what that's from)
I choose "Boot to CWM Recovery" and I first did a backup. Then I selected "Install ZIP" then "Choose zip from sdcard" & I see
/sdcard/
- 0/
- clockworkmod/
That's it. Nothing else. Selecting either one of these displays no zip files. What am I doing wrong?
Click to expand...
Click to collapse
It does not appear that you've made any mistake. It's possible that bokbokan's CWM recovery has changed since I wrote up that guide nearly a year ago (and shortly thereafter have gone onto flashing/running CM11 on emmc and thus would have missed any such change).
One possible solution you might consider trying is to download or copy the ROM and Gapps zip files to your HD+ user-media partition, then while in CWM recovery menu select "... zip files from emmc" and browse to where the ROM/Gapps zip files are located.
In that post, step 4 it mentions "pair" of zip files. I assume though the 2nd item in the "pair" is the Gapps zip.
...
Click to expand...
Click to collapse
Yes, that's correct.

bok build install behaves super flaky for me
One possible solution you might consider trying is to download or copy the ROM and Gapps zip files to your HD+ user-media partition, then while in CWM recovery menu select "... zip files from emmc" and browse to where the ROM/Gapps zip files are located.
I got the sdcard to boot after many reboots and had to keep hard powering off (cutting it off) if the NOOK name displayed too long, (where I knew it was going to boot Nook OS) It booted to CWM, I did a backup, then installed the zips (had to put on internal memory as you said, but even this wasn't easy, It gave some weird error I don't recall,maybe about something "has stopped", so I ended up having to copy it from ES File Explorer after booting to Nook OS) Then I repeated the boot trick as mentioned, backed it up, then installed the 2 zips. I rebooted, got walkthrough of 1st time setup. This is where it got weird. Screens would advance on their own, be shifted halfway off the screen, had a long delay or else wouldn't respond to my clicks, would power off (and wouldn't power on until MANY presses of the power button) or reboot on it's own during the setup. I finally got thru setup and then after booting to Android, it would still be very sluggish, and still powering off on it's own and being difficult to turn on. And it continued to be unreliable to boot to Android, sometimes booting to Nook OS still (even though some in forums say once they got it to boot to Android it would forever after.)
Maybe I need to try a different build. Who else has a well-known, reliable? build besides Succulent? (even though with his it wouldn't boot to CWM but hang at 99% forever on Nook OS loading). If there's no others, maybe I'll give his another try since I had some luck getting CWM to boot with the above trick.

baytee said:
...
This is where it got weird. Screens would advance on their own, be shifted halfway off the screen, had a long delay or else wouldn't respond to my clicks, would power off (and wouldn't power on until MANY presses of the power button) or reboot on it's own during the setup. I finally got thru setup and then after booting to Android, it would still be very sluggish, and still powering off on it's own and being difficult to turn on. And it continued to be unreliable to boot to Android, sometimes booting to Nook OS still (even though some in forums say once they got it to boot to Android it would forever after.)
Click to expand...
Click to collapse
What brand and class of SD card are you using to run CM?
...
even though with his it wouldn't boot to CWM but hang at 99% forever on Nook OS loading
...
Click to expand...
Click to collapse
FWIW, every time that I have had the problem of stock ROM boot-up stuck at 99% it was always because the stock ROM got corrupted due to some unexpected errors in the creation/update of the SD-based CM ROM image, and the only way I was able to recover was to restore stock ROM from backup copy.

I have a PNY 16gb class4 (C16G china 1308PW3599P)
The problem of it hanging at 99% only happened with Succulents, not Bokbokans. As far as the Nook OS being corrupt , I have doubts of that since without the SDcard it ALWAYS boots fine to the nook OS.

baytee said:
I have a PNY 16gb class4 (C16G china 1308PW3599P)
The problem of it hanging at 99% only happened with Succulents, not Bokbokans. As far as the Nook OS being corrupt , I have doubts of that since without the SDcard it ALWAYS boots fine to the nook OS.
Click to expand...
Click to collapse
The problem of stock booting to 99% and hanging with an SD inserted has to do with the properties of the SD, not corruption of stock. Stock will always hang if the SD has more than 3 partitions. Most of Bokbokan's SDs are set up to only have 3 just for that reason. I don't know how many the succulent SD has, I would bet more than 3.
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
...
Stock will always hang if the SD has more than 3 partitions. Most of Bokbokan's SDs are set up to only have 3 just for that reason. I don't know how many the succulent SD has, I would bet more than 3.
Click to expand...
Click to collapse
Succulent's CM SD image for the HD+ only has 3 partitions.

I WAS creating a 4th partition & was unaware it was an issue so thanks. I was doing customized partition (not using their premade sd image). But my whole goal is booting to sdcard, not to nook os.....and the 99% Id assumed was after it failed to boot to sdcard & instead had gone on to boot nook os. But Just in case it helps me boot CM11 on sdcard, I'll try it with 3. Thanks for that tip.

actually I WAS creating a 4th partition & was unaware it was an issue so thanks. I was doing customized partitions (not using their premade sd image). But my whole goal is booting to sdcard, not to nook os.....and the 99% Id assumed was after it failed to boot to sdcard & instead had gone on to boot nook os. But just in case it helps me boot CM11 on sdcard, I'll try it with 3. Thanks for that tip

baytee said:
actually I WAS creating a 4th partition & was unaware it was an issue so thanks.
Click to expand...
Click to collapse
FWIW, I took succulent's pre-made SD image for CM11 (https://goo.im/devs/succulent/ovation/cyanogenmod/image/cm_ovation_11.0_24DEC2013_HD_SDC_IMG.7z), burned it to a (Sandisk class 4) 8GB SD card. The image has 3 partitions which succulent had sized to fit a 2GB SD card; I added a 4th partition (type: FAT32, name: /media) to fill the leftover space of my 8GB card (and reset the boot (1st) partition's type/flag to ensure that it's still bootable). The resulted CM11 card with the extra 4th partition booted up just fine on my HD+.
So, having an extra 4th partition (or, in general, more than 3 partitions) does not prevent a SD-based CM image for the HD+ from booting successfully -- just as one by virtue of logics would have expected.

digixmax said:
FWIW, I took succulent's pre-made SD image for CM11 (https://goo.im/devs/succulent/ovation/cyanogenmod/image/cm_ovation_11.0_24DEC2013_HD_SDC_IMG.7z), burned it to a (Sandisk class 4) 8GB SD card. The image has 3 partitions which succulent had sized to fit a 2GB SD card; I added a 4th partition (type: FAT32, name: /media) to fill the leftover space of my 8GB card (and reset the boot (1st) partition's type/flag to ensure that it's still bootable). The resulted CM11 card with the extra 4th partition booted up just fine on my HD+.
So, having an extra 4th partition (or, in general, more than 3 partitions) does not prevent a SD-based CM image for the HD+ from booting successfully -- just as one by virtue of logics would have expected.
Click to expand...
Click to collapse
No it does not prevent it from booting to the SD, but it does prevent stock from booting successfully if the SD is inserted in the slot. It will hang at 99%.
Sent from my BN NookHD+ using XDA Premium HD app

Verygreen's CM 11 SD build of 11/29/2014 for the HD+ works very well for me. First boot does take awhile so don't give up too fast.
Sent from my BN NookHD+ using Tapatalk