Database Develop

[USER][PARTITIONS] Nook Color EMMC Partition Repair

Several users have complained that they get blank screens and cannot flash new roms to their Nook Color. And sometimes they end up in a recovery bootloop where it will do nothing but boot to recovery no matter what they choose in the boot menu. Sometimes this is due to corrupted partitions on internal memory.
DizzyDen has prepared some .img files that can be burned to emmc to repair some of these issues, and they work well. But some of the files are very large and it takes a little knowledge of adb commands on the part of the users. And some users cannot get adb working on their machines. So I started investigating other solutions, and I have made some tools that work that I hope are user friendly.
Dean Gibson has a thread that describes how to repartition emmc to set the partition sizes for data and media to the user's preference. He repartitions partitions p6 (data), p7 (cache) and p8 (media). In studying his zip, I figured out how to make his tool repair partitions p4 (extended), p5 (system), p6 (data), p7 (cache), and p8 (media). And I was able to add additional commands to also repair partition p1 (boot). I asked Dean's permission to post his tools as modified by me and he agreed. Thanks Dean!
So that takes care of partitions 1, 4, 5, 6, 7, and 8.
Partitions 2 and 3 are very special and one must be very careful with them. Partition 2 is 'rom', which holds information that is specific to the user's device (serial number, etc.), and it is used by the system to set flags for deciding whether to boot to recovery or not and set the boot count that is used to decide whether to do a reset to factory conditions (8 failed boots). Partition 3 is 'factory' and holds the factory.zip file used by the 8 failed boot reset (if you want to learn more about the 8 failed boot reset, go to my tips thread linked in my signature). It also holds a backup of the device information in partition 2. So it is possible to repair partition 2 if partition 3 is still intact.
A few users have somehow managed to flash Nook Tablet ROMs to their Nook Colors and really messed up partition 4. (Edit: and now I know how it happened, some idiot recommended that they remove the first line of the updater script. NEVER do that! That line is a safety check to make sure you are flashing to the right device. You can also defeat the safety check by using an old CWM that has the toggle, 'disable asserts'. Never do that either.) And since partition 4 is the extended partition that holds partitions 5, 6, 7, and 8, they get messed up too. To repair those partitions along with partition 1, use CWM recovery to flash the two zips attached below. Be warned that everything in emmc media (p8) will be wiped out, so you may want to back that up first if you still can. The first zip to flash is 'NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip'. It will recreate those partitions on emmc. As soon as you have sucessfully flashed that zip, you must reboot the Nook Color back to CWM so that the updated partition table is read by CWM. Then you need to flash 'NookColor-emmc-format-partitions-5-6-7-8.zip' (partitions 1 and 4 do not need formatting). It will format the newly created partitions to the correct structure. Now you can use CWM to restore an earlier nandroid backup or flash your favorite ROM (including stock, get version 1.4.3 that I have modified to be flashable with CWM here, or DizzyDen has posted some excellent 1.4.1 stock ROMs here). If you are going to flash a stock ROM, you must be sure to use the format zip or the stock ROM will not boot properly.
If you are in a recovery bootloop, the first thing I recommend trying is to use my CWM version 5.5.0.4 bootable SD that is discussed in my tips thread linked in my signature and has been modified to help get out of some kinds of recovery flag bootloops. If you are in a recovery bootloop that just hangs, it may get you out of it after exiting my CWM with the 'reboot' command in the menu. But if you are still in the loop after doing that, it may be because your device info is missing or corrupted in partition 2. It will not boot to a ROM without this info. (Specifically, it needs a file in /rom/devconf named DeviceID. It is a text file with your 16 digit serial number in it followed by a line feed, 17 bytes.) Try flashing with CWM my 'NookColor-emmc-repair-partition-2.zip' attached to this post to recreate that info. But I recommend this as a last resort, since messing with that partition is risky. That zip will recreate the partition, reset the flags and copy your device specific information from partition 3. But your partition 3 must be intact for this to work. If it is not, the zip will abort and do nothing.
Additionally, for those that do not want to use CWM, I have made a bootable SD that has an older version of TWRP here. Newer versions of TWRP will return an error message when trying to flash these zips. It also has been modified to get you out of some kinds of bootloops.
Two points of information. First, I have included a temporary copy of CWM 5.5.0.4 on the boot partition of my repair so that if tries to reboot to emmc before you put a ROM on it, it goes to CWM. It will be removed as soon as you restore a backup or flash a ROM. Second, the new partition scheme created with my zip is for the original Nook Color's 1GB data and 5GB media. If you want one of the other schemes (5GB data/1GB media or 2GB data/4GB media) go to Dean Gibson's thread and flash his zips after you have repaired your system with mine. See his thread here.
I'm adding a little extra information about emmc partition structure for those interested. With any MBR disk there can be a maximum of four primary partitions. So to have more than four partitions the last primary partition is created as an extended partition so multiple logical partitions can be made inside it. The emmc structure is: p1 (boot, fat, primary), p2 (rom, fat, primary), p3 (factory, ext3, primary), p4 (extended, going from end of p3 to end of the disk), p5 (system, ext2, logical, inside the extended), p6 (data, ext3, logical, inside the extended), p7 (cache, ext3, logical, inside the extended) and p8 (media, fat, logical, inside the extended).

You save my nook color
Thank you so much. My serial number and other information were recovered successfully. Without those information I could not boot into any rom. If you cannot boot into ROM after following the first 2 steps, try recover partition 2. It works for me.
:laugh::laugh::laugh::laugh::laugh:

Thanks
My nook has been stuck in a "will not boot" state for about a week. I could run CWM and cyanoboot, but when ever I tried to boot CM I would get stuck at the "loading..." screen. I tried loading both CM7 & CM9 but neither one would boot.
I ran both repair scripts, reloaded CM7.1 and success!
Thanks Leapinlar! :good:

THANK YOU!!!!!!
Right from my 1st install I couldn't get the bar at the bottom of the screen, which made using the Kindle app more than a little difficult. This finally cleared everything off so I could start with a clean slate, and BINGO! I know have the bottom bar on all the screens. I assume when I go in to the Kindle app it will be ok now also (I just have to format a 16gb microSD and put in the Nook Color 1st).
I can't thank you enough!!!!

Ugh! Tried this method too, and I still cannot get the nook to boot into CWR or CWM. I tried the 8 boots thing too, but I don't know if I ever did it right because I have cyanogen mod installed on emmc. Not sure how to repair the partition if I cannot even boot into anything that allows me to flash the zip to the chip. I thought it may be the sd, but the sd cards work on my other nook. I have now basically dissembled my nook color trying to find any other solution I wish I knew what happened in the first place.

czarofthefrozentundra said:
Ugh! Tried this method too, and I still cannot get the nook to boot into CWR or CWM. I tried the 8 boots thing too, but I don't know if I ever did it right because I have cyanogen mod installed on emmc. Not sure how to repair the partition if I cannot even boot into anything that allows me to flash the zip to the chip. I thought it may be the sd, but the sd cards work on my other nook. I have now basically dissembled my nook color trying to find any other solution I wish I knew what happened in the first place.
Click to expand...
Click to collapse
Did you try my version of the CWM bootable SD card? It is on my tips thread and has been modified to boot in certain types of recovery bootloops. Unless you get CWM running you cannot flash things to internal memory. And depending on where in the boot process it hangs, you may not be able to get adb working to put things there either. And the 8 failed boots will not work unless you have stock recovery still on emmc.
Sent from my NookColor using Tapatalk

leapinlar said:
Did you try my version of the CWM bootable SD card? It is on my tips thread and has been modified to boot in certain types of recovery bootloops. Unless you get CWM running you cannot flash things to internal memory. And depending on where in the boot process it hangs, you may not be able to get adb working to put things there either. And the 8 failed boots will not work unless you have stock recovery still on emmc.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Yup. Tried the card. I believe I replaced the emmc with cyanogenmod back in the day. Starts, goes to loading, turns black, then done. Cannot do anything after that. Bummer, sounds like it is actually toast.

czarofthefrozentundra said:
Yup. Tried the card. I believe I replaced the emmc with cyanogenmod back in the day. Starts, goes to loading, turns black, then done. Cannot do anything after that. Bummer, sounds like it is actually toast.
Click to expand...
Click to collapse
If you can get adb working while it is sitting there black, you can push the stock recovery files to partition one. Then you may be able to do the 8 failed boots. You can extract the stock recovery files from my zip in my tips thread.

leapinlar said:
If you can get adb working while it is sitting there black, you can push the stock recovery files to partition one. Then you may be able to do the 8 failed boots. You can extract the stock recovery files from my zip in my tips thread.
Click to expand...
Click to collapse
Worth a shot. Have nothing more to lose other than time. Maybe adb will work with you card in it. It didn't work with everything else I tried.

OMG OMG thank you soooo much for this thread , you saved my reading addict self from going insane ......

You've done a great job on collecting all of these useful things, especially for those who are stuck with their Nook Color boot looping. (I was once that guy) Dean helped me out with his data zips as well way back! Thanks for all this! :good: :victory:

Much thanks, leapinlar. Restored a nandroid with TWRP that was corrupted and lost my boot partition. I used your first 2 repair zips and I'm back in business. Your many contributions are greatly appreciated.
Mike T

OMG! Thank you so much for putting this up! Back at the beginning of the year I was having problems with my NC not going into USB Mode and only showing a black arrow when trying to load books and following this finally fixed it. Great write-up and instructions, thanks for the hard work.

I've been trying to restore my NOOK for about 2 weeks and this post has gotten me the farthest but i'm stuck at the point where my nook will start up, the "Read Forever" splash screen will come up and then it attempts to recover the system since i see an greenish Android screen come up for a second and then i get an error screen saying "Install Failed" with an image of a nook with an exclamation point in it's screen. I'm assuming i've really messed the nook up but here is where I am.
I've reformatted the partitions using your 1-4,5,6,7,8 zip
Rebooted to recovery
Formatted partiions 5,6,7,8 with your zip
Flashed your 1.4.3 stock rom
At this point I can't get any further since it appears something else is wrong and i didn't want to attempt the reformatting of partition 2 without asking if there is anything else i should try. Any help would be appreciated.
Thanks

jmiklus01 said:
I've been trying to restore my NOOK for about 2 weeks and this post has gotten me the farthest but i'm stuck at the point where my nook will start up, the "Read Forever" splash screen will come up and then it attempts to recover the system since i see an greenish Android screen come up for a second and then i get an error screen saying "Install Failed" with an image of a nook with an exclamation point in it's screen. I'm assuming i've really messed the nook up but here is where I am.
I've reformatted the partitions using your 1-4,5,6,7,8 zip
Rebooted to recovery
Formatted partiions 5,6,7,8 with your zip
Flashed your 1.4.3 stock rom
At this point I can't get any further since it appears something else is wrong and i didn't want to attempt the reformatting of partition 2 without asking if there is anything else i should try. Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
Do the partition 2 repair. That is what is messed up and causing the reboot.
Sent from my Nook HD+ using Tapatalk

leapinlar said:
Do the partition 2 repair. That is what is messed up and causing the reboot.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
I've tried the partition2 zip and received an error trying to mount the factory partition. Status 7 was the error code. Is there a way to fix this?

jmiklus01 said:
I've tried the partition2 zip and received an error trying to mount the factory partition. Status 7 was the error code. Is there a way to fix this?
Click to expand...
Click to collapse
Oh, that is really bad news. That means your partition 3 is corrupted and there is no way to retrieve your device info, like serial number, etc. PM me and maybe I can help you get it partly working, but much of the device info is lost if that partition is truly corrupted.
Sent from my BNTV600 using Tapatalk

Restore NC back to stock
View attachment 1500490
leapinlar said:
Oh, that is really bad news. That means your partition 3 is corrupted and there is no way to retrieve your device info, like serial number, etc. PM me and maybe I can help you get it partly working, but much of the device info is lost if that partition is truly corrupted.
Sent from my BNTV600 using Tapatalk
Click to expand...
Click to collapse
I've been trying to restore my daughter NC back to stock for couple months now and no success.
I did flash the P 1-4-5-6-7-8.zip and got this message after reboot:
"CWM-based Recovery v5.5.0.4
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
during the reboot, there is a menu option to hit "n" for reboot mode option. when i hit "n" it gives me (attachment).
but it won't let me move up or down to select except for the 1st option
Help would be very appreciated

big64dave said:
View attachment 1500490
I've been trying to restore my daughter NC back to stock for couple months now and no success.
I did flash the P 1-4-5-6-7-8.zip and got this message after reboot:
"CWM-based Recovery v5.5.0.4
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
during the reboot, there is a menu option to hit "n" for reboot mode option. when i hit "n" it gives me (attachment).
but it won't let me move up or down to select except for the 1st option
Help would be very appreciated
Click to expand...
Click to collapse
During reboot it should automatically go to CWM because everything else is wiped. The boot menu only lets you make the first choice because that is all that is there, everything else is wiped. You need to continue to use the CWM to flash the format zip next. Then you can flash a ROM. If the CWM that pops up is not working, use the bootable CWM SD.

leapinlar said:
During reboot it should automatically go to CWM because everything else is wiped. The boot menu only lets you make the first choice because that is all that is there, everything else is wiped. You need to continue to use the CWM to flash the format zip next. Then you can flash a ROM. If the CWM that pops up is not working, use the bootable CWM SD.
Click to expand...
Click to collapse
Thx for replied, the Nook just stock on loading and it won't let me do anything except for power up and down

[Q] nandroid backups failing

Hi all,
I run CM10.1 on my phone but am new to the Nook HD+. I have emmc-cwm-early2.1.img dd-ed to an SD card, and it boots just fine. I have cm-10.1-20130719-UNOFFICIAL-ovation-emmc.zip downloaded on the Nook. The problem I'm encountering is that backups are failing with "Can't mount /system!" after boot is backed up. It seems foolish to flash any ROM without an initial nandroid backup.
If I select advanced->show log I see this line:
W: failed to mount /dev/block/mmcblk1p2 (Invalid argument)
However, the Nook boots just fine into my unmodified stock if I remove the SD card.
Help? Thanks!

crazybikeperson said:
Hi all,
I run CM10.1 on my phone but am new to the Nook HD+. I have emmc-cwm-early2.1.img dd-ed to an SD card, and it boots just fine. I have cm-10.1-20130719-UNOFFICIAL-ovation-emmc.zip downloaded on the Nook. The problem I'm encountering is that backups are failing with "Can't mount /system!" after boot is backed up. It seems foolish to flash any ROM without an initial nandroid backup.
If I select advanced->show log I see this line:
W: failed to mount /dev/block/mmcblk1p2 (Invalid argument)
However, the Nook boots just fine into my unmodified stock if I remove the SD card.
Help? Thanks!
Click to expand...
Click to collapse
If you are trying to backup to the sdcard, there is not enough room there to hold a complete backup. It usually fails about the time it gets to /system. The solution is to backup to internal memory where it has plenty of room. That mmcblk1p2 failure is just not finding the sd-ext partition on SD. A normal error.
Sent from my Galaxy Tab 2 using XDA Premium

leapinlar said:
If you are trying to backup to the sdcard, there is not enough room there to hold a complete backup. It usually fails about the time it gets to /system. The solution is to backup to internal memory where it has plenty of room. That mmcblk1p2 failure is just not finding the sd-ext partition on SD. A normal error.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
"backup to internal sdcard" failed as well with "Can't mount /system!"

crazybikeperson said:
"backup to internal sdcard" failed as well with "Can't mount /system!"
Click to expand...
Click to collapse
Go to my HD/HD+ CWM thread linked in my signature and try one of my 6.0.2.8 CWM SDs from item one. Try backing up with it.
Sent from my Galaxy Tab 2 using XDA Premium

leapinlar said:
Go to my HD/HD+ CWM thread linked in my signature and try one of my 6.0.2.8 CWM SDs from item one. Try backing up with it.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
That seemed to work. I also flashed an sdcard version of CM10.1 and it boots. However, I forgot to install gapps. Now I can't seem to get the Nook to boot into recovery - it only wants to boot CM10.1. Sigh.

crazybikeperson said:
That seemed to work. I also flashed an sdcard version of CM10.1 and it boots. However, I forgot to install gapps. Now I can't seem to get the Nook to boot into recovery - it only wants to boot CM10.1. Sigh.
Click to expand...
Click to collapse
When the cyanoboot logo first comes up, hold the power and n button together for a few seconds and release. It should boot to CWM.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
When the cyanoboot logo first comes up, hold the power and n button together for a few seconds and release. It should boot to CWM.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Unfortunately that didn't work. What did work was replacing the bootfiles on the sdcard... but recovery can't find the gapps .zip file, or anything I downloaded while running CM. I reinstalled CM, and now I can't get back into recovery.
Ugh, this is hard. I'm starting to regret buying it, since the point was to put CM on it.

crazybikeperson said:
Unfortunately that didn't work. What did work was replacing the bootfiles on the sdcard... but recovery can't find the gapps .zip file, or anything I downloaded while running CM. I reinstalled CM, and now I can't get back into recovery.
Ugh, this is hard. I'm starting to regret buying it, since the point was to put CM on it.
Click to expand...
Click to collapse
You need to go to settings and about tablet. Tap the build number several times until developer options is activated. Then go to developer options and check off advanced reboot. Then when you choose reboot on the power off menu, recovery shows.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
You need to go to settings and about tablet. Tap the build number several times until developer options is activated. Then go to developer options and check off advanced reboot. Then when you choose reboot on the power off menu, recovery shows.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I tried that in the beginning. It just rebooted into CM.

crazybikeperson said:
I tried that in the beginning. It just rebooted into CM.
Click to expand...
Click to collapse
You have all your boot files all mixed up. I give up.
Sent from my Nook HD+ running CM10.1 on emmc.

[q] nook hd+ flashing failed

Hi guys so i was transferring movies to my nook, after that was done i removed the cable and my nook entered into a boot loop. Not being able to find my CWM backup i therefore decided to make a fresh install, i formatted my internal storage,cache and data. I loaded my ROM to my external sd card and booted to CWM, when i try to flash it brings up an error: E: Cant open /sdcard/Xperia-2.3.9-CARBON-JB-B11=-ovation.zip (bad) Installation aborted.
It gives this error for every ROM i try. Somehow i managed to find my CWM backup but when i try to restore it, it says: MD5 mismatch......Can anybody help?

Kubombelar said:
Hi guys so i was transferring movies to my nook, after that was done i removed the cable and my nook entered into a boot loop. Not being able to find my CWM backup i therefore decided to make a fresh install, i formatted my internal storage,cache and data. I loaded my ROM to my external sd card and booted to CWM, when i try to flash it brings up an error: E: Cant open /sdcard/Xperia-2.3.9-CARBON-JB-B11=-ovation.zip (bad) Installation aborted.
It gives this error for every ROM i try. Somehow i managed to find my CWM backup but when i try to restore it, it says: MD5 mismatch......Can anybody help?
Click to expand...
Click to collapse
When it says bad that usually means a bad download. And md5 mismatch means the backup is corrupted. Try using a different PC for downloads. Your antivirus software may be corrupting things.
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
When it says bad that usually means a bad download. And md5 mismatch means the backup is corrupted. Try using a different PC for downloads. Your antivirus software may be corrupting things.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
i dont think so, i have tried three diffrent laptops it still failed. I got the problem solved by writing a cwm boot image to my 2GB SD that allows you to run a bootable version of stock rom v2.1.1......i booted via the sd and with a custom rom loaded on my sd i flahed and it worked no problems same applies with gapps. When i boot into my rom under storage settings it shows my emmc as "read only", am not sure if this is what caused the initial problem. Maybe changing the emmc permissions with ES file manager to both read and write will fix the initial problem as booting via emmc and attempting a flash still fails, however it works while the sd is inserted and flashing via TWRP which is installed on my emmc. Advise with your opinion

[Q] Bricked Nook Restore standard boot logo

Hi all,
My Nook seems to have broken over night, more than likely the trim command was fired and broken my partition table.
I would return the item, but the Cyanogen Boot logo still appears. Is there anyway to remove it based on the nooks current bricked status?

smurfster said:
Hi all,
My Nook seems to have broken over night, more than likely the trim command was fired and broken my partition table.
I would return the item, but the Cyanogen Boot logo still appears. Is there anyway to remove it based on the nooks current bricked status?
Click to expand...
Click to collapse
If it shows that logo, it is not likely bricked by the trim command. Try making a bootable CWM per my HD/HD+ CWM thread and try flashing a plain stock zip from item 6.
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
If it shows that logo, it is not likely bricked by the trim command. Try making a bootable CWM per my HD/HD+ CWM thread and try flashing a plain stock zip from item 6.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the reply,
Ive now tried different SD cards and both ways of creating a bootable sd card. but nothing works. I cant get past the cyanogen boot screen.
The TWRP image did boot but didnt get passed the splashscreen.
Any advice?

smurfster said:
Thanks for the reply,
Ive now tried different SD cards and both ways of creating a bootable sd card. but nothing works. I cant get past the cyanogen boot screen.
The TWRP image did boot but didnt get passed the splashscreen.
Any advice?
Click to expand...
Click to collapse
I have this EXACT same problem, I would love to find a way to get the cyanoboot splash screen to go away so I can get it exchanged for a new one.

Both of you only have two choices.
If you left stock recovery on internal before it screwed up, you can do the 8 failed boot procedure and it will reset itself to stock.
If you replaced stock recovery with CWM or TWRP, you must boot to it or a bootable CWM SD so you can flash the plain stock zip I have in item 6 in my HD/HD+ CWM thread linked in my signature. To get to your custom recovery on internal, power up from the powered off condition and hold both the power and n button simultaneously for 5-8 seconds. Then first release power and then a couple of seconds later the n key. It should show the cyanoboot logo followed by the recovery.
If you cannot do any of those things, you are screwed.
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
Both of you only have two choices.
If you left stock recovery on internal before it screwed up, you can do the 8 failed boot procedure and it will reset itself to stock.
If you replaced stock recovery with CWM or TWRP, you must boot to it or a bootable CWM SD so you can flash the plain stock zip I have in item 6 in my HD/HD+ CWM thread linked in my signature. To get to your custom recovery on internal, power up from the powered off condition and hold both the power and n button simultaneously for 5-8 seconds. Then first release power and then a couple of seconds later the n key. It should show the cyanoboot logo followed by the recovery.
If you cannot do any of those things, you are screwed.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Looks like im screwed. It is strange though how the TWRP bootable image actually attempts to boot?
UPDATE: http://forum.xda-developers.com/showpost.php?p=44797803&postcount=73
I tried this and have managed to boot into cwm.
I then noticed a error that kept repeating. E:unknown volume for path [/cache/recovery/command]
So I then did the following
1. wipe data/factory reset
2. wipe cache partition
3. mounts and storage > format /boot
4. mounts and storage > format /system
5. mounts and storage > format /data
6. mounts and storage > format /emmc
7. mounts and storage > format /data and /data/media (/sdcard)
Alot of this did cause mounting problems. but I did notice I could mount /boot and browse sdcard from the "install zip" option. The only problem is the partion in the SD i can see isnt the partition that CWM can see.
I'm going to try and sideload the stock recovery using adb when I get in from work as I dont have the usb cable on me.

If you made a backup of stock prior to loading another ROM, you may have better luck restoring it than flashing the stock zip. That has been my experience. In addition to doing the restore, you may need to flash the stock recovery zip.
Sent from HD+ MAG2GA CM 10.2 from SD

Well I couldnt get ADB to work with my tablet. So I couldnt sideload the stock emmc. So I then used "Paragon ExtFS for Windows" to copy the files to the other correct ext3 partition on the MicroSD.. I then booted into recovery and attempted to flash the zip. It didnt work, I recieved a error stating
E: unknown volume for path [/cache/recovery/last_log]
E: cant mount /cache/recovery/last_log
Looks like the nooks dead.

Nook hd plus, Cm 10.2 stopped working. It keeps crashing and restarting.

I got nook hd+ and used cm version 10.2 something for a while.
The device keeps crashing and restarting like crazy.
1 out of 10 times, it launches, but before I do anything, it crashes. Hell.
It has been crashing and restarting quite often these days, but since last night, all it does is crashing and restarting.
To make matters worse, I tried to format the device and install cm again. It did not work.
I made booting SD card and chose 'wipe data/ factory reset'. And nook said it wiped /data /cache data wipe complete etc. However, files were still there in internal storage.
On top of that, I had to try 4 times to install newest cm-11. It aborted.
Next, I tried to installnookjdplus factory2.2.0 . It had error. (status 6) to ne specific.
So, I tried newest cwm recovery. It installed, but nook still crashed.
I persevered and tried to install cm 11. It installed, but still crash and restart.
Hell. I literally spent whole day doing this. I am confused and frustrated and angry and experiencing a few other negative emotions English language dows not have in words.
Please, some advice.

Venrun said:
I got nook hd+ and used cm version 10.2 something for a while.
The device keeps crashing and restarting like crazy.
1 out of 10 times, it launches, but before I do anything, it crashes. Hell.
It has been crashing and restarting quite often these days, but since last night, all it does is crashing and restarting.
To make matters worse, I tried to format the device and install cm again. It did not work.
I made booting SD card and chose 'wipe data/ factory reset'. And nook said it wiped /data /cache data wipe complete etc. However, files were still there in internal storage.
On top of that, I had to try 4 times to install newest cm-11. It aborted.
Next, I tried to installnookjdplus factory2.2.0 . It had error. (status 6) to ne specific.
So, I tried newest cwm recovery. It installed, but nook still crashed.
I persevered and tried to install cm 11. It installed, but still crash and restart.
Hell. I literally spent whole day doing this. I am confused and frustrated and angry and experiencing a few other negative emotions English language dows not have in words.
Please, some advice.
Click to expand...
Click to collapse
CM10.x, CM11, and stock ROM need different versions of CWM recovery.
See http://forum.xda-developers.com/showthread.php?t=2679899 for info/pointers on flashing CM11.
To go back to stock ROM, see http://forum.xda-developers.com/showthread.php?t=2062613(item #6).
When switching between CM10, CM11, and stock ROM, you need to do "wipe /data & factory reset".
If none of the above helps the your problem might be due to an unruly app or hardware related.

digixmax said:
CM10.x, CM11, and stock ROM need different versions of CWM recovery.
See http://forum.xda-developers.com/showthread.php?t=2679899 for info/pointers on flashing CM11.
To go back to stock ROM, see http://forum.xda-developers.com/showthread.php?t=2062613(item #6).
When switching between CM10, CM11, and stock ROM, you need to do "wipe /data & factory reset".
If none of the above helps the your problem might be due to an unruly app or hardware related.
Click to expand...
Click to collapse
Ok. At least I got my biggest problem now.
I think my roblem is wipe data/factory reset does not do job it is supposed to do.
I still see folders and files in internal memory after factory reset. I think that is why install aborts and crashes even after successful install.

I think my problem is that wipe data/factory reset does not do its job
It gives me message it is formatting data cache and stuff. And last day they gave me data wipe complete. But the problem is, in internal memory, I can still see old folders and old files.
I think he should be gone if it is formatted. Where do I get the meaning of factory reset wrong?
Its not what is wrong with me. And how can I make factory reset work
And second question is that I tried to install B&N original operating system from cwm-based recovery. I tried a few different versions of
nookHDplus-factory-2.1.1-plain-stock.zip
However it always fail to install. Install aborted for some reason.

Thanks. It seem helpful.
digixmax said:
CM10.x, CM11, and stock ROM need different versions of CWM recovery.
See http://forum.xda-developers.com/showthread.php?t=2679899 for info/pointers on flashing CM11.
To go back to stock ROM, see http://forum.xda-developers.com/showthread.php?t=2062613(item #6).
When switching between CM10, CM11, and stock ROM, you need to do "wipe /data & factory reset".
If none of the above helps the your problem might be due to an unruly app or hardware related.
Click to expand...
Click to collapse
Thanks a lot for your advice
Going back to stock Rom 6 explains error message and aborting of install.
However the problem is where do I get CWM V 60036 or eariler?
Googling does not work.9

Venrun said:
Thanks a lot for your advice
Going back to stock Rom 6 explains error message and aborting of install.
However the problem is where do I get CWM V 60036 or eariler?
Googling does not work.9
Click to expand...
Click to collapse
You can get v6036 on that same thread digimax referenced above (my CWM thread linked in my signature). And a data wipe does not wipe your media files. To do that, go to mounts and storage and select wipe "data and datamedia".
Sent from my SM-T707V using XDA Premium HD app

thanks
leapinlar said:
You can get v6036 on that same thread digimax referenced above (my CWM thread linked in my signature). And a data wipe does not wipe your media files. To do that, go to mounts and storage and select wipe "data and datamedia".
Sent from my SM-T707V using XDA Premium HD app
Click to expand...
Click to collapse
trying it. hope it works.

did not work
for about deleting internal data, I went to 'mounts and storage'. used 'format /sdcard' and 'format/ data and/ data/media (/sdcard), but still has stuff in internal memory.
and to my surprise , I have been using CWM-6028. so far. I thought its name was 'NookHDplus-bootable'.
hell. stupid me.
Anyhow, CWM-6028 has been giving me troule
so, I would try other versions.
So far, I have done
1. made boot sd by burning image.
2. copy 'NookHDplus-factory-2.1.0-plain-stock' files and other versions.
3. Insert SD in device and boot CWM.
4. choose zip from sdcard.
5. install factory plain stock.
then I get message 'Failed to retouch 'system/lib/libemoji.so' (WTF is libemoji? and it is always this same file.)
E: error in sdard/nookHDplus-factort-2.2.1-plain-stock.zip(status7)
Installation aborted.
hell. And I tried every factory zip.
Am I doing something wrong?

Failed tp retouch '/system/lib/libemoji' is error message I get
Everytime I tried to install factory stock.
I tried every version of stock files. And I tried all CWM. And even tried TWRP, but it is always the same message what the hell is that emoji?
And what can I do with it?
What frustrates me the most is the fact that it installed 99% in a minute without trouble and stays there 410 minutes until it fails to install. It's driving me crazy

Does CM makes Factory reset by power button and home button does not work either.
Because I am getting message factory reset failed.
If CM is not the reason for it, well, something is wrong. Very wrong.
I am suspecting Internal memory corrupted lr something.
I should seriously consider throwing it away now.

Venrun said:
Because I am getting message factory reset failed.
If CM is not the reason for it, well, something is wrong. Very wrong.
I am suspecting Internal memory corrupted lr something.
I should seriously consider throwing it away now.
Click to expand...
Click to collapse
It is possible you have a bricked emmc. When bricked it looks like it is writing but is really read only and nothing takes. If you still have media files after a successful format data and datamedia then it is bricked. Probably best to get rid of it. You can buy a refurbished unit very cheaply these days.
Sent from my SM-T707V using XDA Premium HD app

Venrun said:
Because I am getting message factory reset failed.
If CM is not the reason for it, well, something is wrong. Very wrong.
I am suspecting Internal memory corrupted lr something.
I should seriously consider throwing it away now.
Click to expand...
Click to collapse
Assuming that your EMMC is shot, you can try running off SD card this no-emmc version of CM11 ROM: https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/. It's best to use a card with fast randomized block read/write (which is what Class 4 cards are typically best at).

Thanks guys. By the way, what is emmc?
Is it part of CM software?
Does not sounds like hardware.
If I had factory resetted a day earlier, I would not have had problems.
Well. That is the way it is.

I finally kind of got nook working. I am running it on SD card now.
I got to thank you guys for your good advices.
Problem is that this ecmm free booting shrinks storage space.
No matter what is size of SD card, Internal storage is 900mb and SD card got 100mb. (I mean virtual Internal storage the file made in SD card) Not enough space to hold a movie.
I am happier to have tab working, but also wish to use full space of my SD.
At least I wish I can have a few Gs of storage.

Venrun said:
I got to thank you guys for your good advices.
Problem is that this ecmm free booting shrinks storage space.
No matter what is size of SD card, Internal storage is 900mb and SD card got 100mb. (I mean virtual Internal storage the file made in SD card) Not enough space to hold a movie.
I am happier to have tab working, but also wish to use full space of my SD.
At least I wish I can have a few Gs of storage.
Click to expand...
Click to collapse
Right after burning the ROM image to SDcard, it should be possible to use a disk partitioning tool such as MiniTool Partition Wizard to examine the SDcard ROM image's partitions and resize the /data partition to fill up the un-allocated space.

digixmax said:
Right after burning the ROM image to SDcard, it should be possible to use a disk partitioning tool such as MiniTool Partition Wizard to examine the SDcard ROM image's partitions and resize the /data partition to fill up the un-allocated space.
Click to expand...
Click to collapse
Thanks a lot. That sounds I can do it.

how you did it
Venrun said:
I got to thank you guys for your good advices.
Problem is that this ecmm free booting shrinks storage space.
No matter what is size of SD card, Internal storage is 900mb and SD card got 100mb. (I mean virtual Internal storage the file made in SD card) Not enough space to hold a movie.
I am happier to have tab working, but also wish to use full space of my SD.
At least I wish I can have a few Gs of storage.
Click to expand...
Click to collapse
Please tell how you made SD card work.
thanks.

rkgarg2000 said:
Please tell how you made SD card work.
thanks.
Click to expand...
Click to collapse
See http://forum.xda-developers.com/showpost.php?p=49007593&postcount=84 for some pointers on how to create a CM SD card with customized partition sizing for HD+. Although it was written for CM11, you should be able to adapt it for CM10.2 by using the appropriate ROM and GApps zip files corresponding to CM10.2.

Please confirm if my problem has any other solution
my NOOK HD+ I have CMW 10.2.1 with 6.0.4.6 recovery. Nook went to loop while booting. Now I can go to recovery and able to boot SD recovery CMW 6.0.2.8. But issue is:-
1. For any update even for Stock ROM it gives status 7 error.
2. With system recovery 6.0.4.6 when I try factory reset the TAB reboot same happen when i try to format DATA. While factory reset and DATA format happens with 6.0.2.8 position remains same.
3. When I try to make backup on internal storage both with 6.0.4.6 (TAB recovery) or 6.0.2.8 (From SD card) it makes boot,recovery and system image but give error as failed to backup /DATA.
4. I have done every thing right from various and latest ROM's ( error Status 7), Formatting boot,system but 6.0.4.6 on NOOK is intact and is in loop.
Please tell How I can over come this STATUS 7 error or DATA backup error.
thanks.
digixmax said:
See http://forum.xda-developers.com/showpost.php?p=49007593&postcount=84 for some pointers on how to create a CM SD card with customized partition sizing for HD+. Although it was written for CM11, you should be able to adapt it for CM10.2 by using the appropriate ROM and GApps zip files corresponding to CM10.2.
Click to expand...
Click to collapse

rkgarg2000 said:
my NOOK HD+ I have CMW 10.2.1 with 6.0.4.6 recovery. Nook went to loop while booting.
Click to expand...
Click to collapse
Does it boot-loop to recovery?
If so, see http://forum.xda-developers.com/showpost.php?p=55582281&postcount=1459 for potential causes and solutions.
Now I can go to recovery and able to boot SD recovery CMW 6.0.2.8. But issue is:-
1. For any update even for Stock ROM it gives status 7 error.
2. With system recovery 6.0.4.6 when I try factory reset the TAB reboot same happen when i try to format DATA. While factory reset and DATA format happens with 6.0.2.8 position remains same.
3. When I try to make backup on internal storage both with 6.0.4.6 (TAB recovery) or 6.0.2.8 (From SD card) it makes boot,recovery and system image but give error as failed to backup /DATA.
4. I have done every thing right from various and latest ROM's ( error Status 7), Formatting boot,system but 6.0.4.6 on NOOK is intact and is in loop.
Please tell How I can over come this STATUS 7 error or DATA backup error.
...
Click to expand...
Click to collapse
CWM v6.0.4.6 is not compatible with CM10.x, you need to flash back to the CWM version you previously used.