Database Users

[Q] Cannot Format /Data

Whenever I try to format /data through CWM 3.0.2.8, it returns the message.
error while formatting /data
Click to expand...
Click to collapse
Also when I try to restore a backup, CWM cannot format /data.
I've also tried to install CM7. It says it completed its install in CWM but when I reboot, it retains the OS (rooted stock 1.2) I was currently on.

Me too. I just updated to MR1 and I am trying to restore the /data directory and I can't.

There's one thing I noticed about this refurb'd nook color. The space available in the device info is 1GB. Shouldn't it be higher or did they change the file structure with the latest models?
Also, I went into ADB and mounted EMMC. The last modified date for the files in there is May 4th.
Edit
Not sure if this would help.
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 789 5421906 83 Linux
/dev/block/mmcblk0p7 790 834 361431 83 Linux
/dev/block/mmcblk0p8 835 965 1052226 c Win95 FAT32 (LB
A)
~ #
Click to expand...
Click to collapse
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7937MB 7477MB extended
5 461MB 938MB 477MB logical ext2
6 938MB 6490MB 5552MB logical ext3
7 6490MB 6860MB 370MB logical ext3
8 6860MB 7937MB 1077MB logical fat32 lba
(parted)
Click to expand...
Click to collapse

Someone responded back to me on this forum.
http://androidforums.com/b-n-nookcolor/333668-format-internal-partition.html#post2672750
Barnes & Noble has started shipping new NOOK Color devices that are partitioned to allow only 1 GB of "user sideloaded" storage. The remaining 7 GB are partitioned for the OS, apps from the new B&N Apps store, and items downloaded directly from B&N. For the typical (non-rooted) device, the user would have to use the microSD slot for additional storage. I suspect you got one of the newly partitioned devices, which is why you are now seeing only 1 GB instead of the previous 5 GB of storage available.
Click to expand...
Click to collapse
Is there anyway to repartition the new devices or I'm stuck with this? If not, it's going to prevent me from dualbooting. This might also be the cause of my second problem, installing CM7 and still ending up with the original OS.

Oh man am I glad I found this thread. I was freakin' out when I couldn't load phiremod onto my newly purchased NC. Turns out I can only see 1GB of storage like the others in this thread. Hopefully some one will find a way to repartition the newer devices otherwise I am stuck with a rooted NC running the stock ROM with no way to return it.

You can just "Reset to factory default" and it'll remove the root. Then you can try to return it or exchange it. I'd probably say this if they ask for a reason...
"It's showing 1GB space as opposed to 8GB space as advertised"
Though I'm wondering why install CM7 doesn't change anything. After installation, it still boots up the stock OS.

jb7038 said:
You can just "Reset to factory default" and it'll remove the root. Then you can try to return it or exchange it. I'd probably say this if they ask for a reason...
"It's showing 1GB space as opposed to 8GB space as advertised"
Though I'm wondering why install CM7 doesn't change anything. After installation, it still boots up the stock OS.
Click to expand...
Click to collapse
Trying to load new ROMS fails because I can't do a data wipe as instructed.

I wonder if they made it so that outside sources can't write or modify /data now but it's still rootable with manualnooter.. I can format the other partitions through CWM and restore them easily.
EDIT
http://www.barnesandnoble.com/nookcolor/features/index.asp?cds2Pid=35583
*1GB = 1 billion bytes; Actual formatted capacity may be less. Approximately 5GB available to store content, of which up to 4GB may be reserved for content purchased from the Barnes & Noble NOOK Store.

I am not sure what kind of security they could have on the actual partitions, but the dual boot ROMS show that resizing the partitions should not be to hard, though it does mean you may lose data (possibly).

I don't mind losing my /data. I rather be able to install CM7 or something on the EMMC as opposed to running it on the SD.
I'd be grateful if someone could show me how to partition it so it's back to the original partition, 4gb/4gb as opposed to 7gb/1gb I think.

I hope something is figured out soon.

Here's the solution to anyone following this thread.
http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110

I had this problem too.. bought a brand new nook color... this is what i did using CWM 3.0.2.8 to boot off SD...
1. used manual nooter 4.5.6
(after applying had all types of popup force close messages about /media this /media that)
2. changed my patitions to match this post
http://forum.xda-developers.com/showpost.php?p=13003431&postcount=166
(Note: Although it said that it didnt write the partitions it actually did)
3. did the 8 boot reset and nook button reset...
(This didn't reset the partitions actually and I had 5.sumthin GB free space not 1GB as before)
4. Manual nooted again then installed Phiremod 6.2 and Dalingrin's Kernel 042411 for cm7....

Sparks1641 said:
I had this problem too.. bought a brand new nook color... this is what i did using CWM 3.0.2.8 to boot off SD...
1. used manual nooter 4.5.6
(after applying had all types of popup force close messages about /media this /media that)
2. changed my patitions to match this post
http://forum.xda-developers.com/showpost.php?p=13003431&postcount=166
(Note: Although it said that it didnt write the partitions it actually did)
3. did the 8 boot reset and nook button reset...
(This didn't reset the partitions actually and I had 5.sumthin GB free space not 1GB as before)
4. Manual nooted again then installed Phiremod 6.2 and Dalingrin's Kernel 042411 for cm7....
Click to expand...
Click to collapse
I did this too and it scared the crap out of me when it kicked me out of fdisk. I thought I hosed it for good. Then when I did the 8 resets it kept going into CWM on the 8th reset. It wasn't until I rebooted it from CWM did it go and reflash itself.
Man that was scary. I thought I had a $250 paper weight.

I was a little freaked out when the fdisk said it didn't work... But reading around I seen that its almost impossible to break it as long as you don't mess with the first 3 partitions so what was the worse case I figured... This must be an issue with the CWR though.. Probably just updating the CWR to format different sizes of the partitions... A format with offset and length feature in an advanced menu... then we can change the sizes to what we want.. But going forward until CWR gets updated every new nook probably gonna have to do the partition change... Not like that's a big deal...

I bought a Nook Color used off craigslist cus they "bricked" it. I thought, no prob, through in the CWM uSD card, erase the data and system, and throw 1.2 on to root.
Can't erase the Data!
They said it was only a few weeks old. I'm guessing it was a refurb with new partition, they tried to root it somehow, and messed it up, then gave up.
Let's hope this fixes it!

Let us know if the partition thing works.. that would be cool.. GL.....

Sparks1641 said:
Let us know if the partition thing works.. that would be cool.. GL.....
Click to expand...
Click to collapse
I did the repartition here:
http://forum.xda-developers.com/showthread.php?t=1094371
and it worked like a charm - finally have CM7 on my 4th Nook!
Thanks to DeanGibson.

[Q] How do I partition the eMMC to support Custom ROMs?

I bought my NC last week and immediately rooted it with out a hitch using ManualNooter for stock 1.2. In the process of trying to flash Phiremod my NC locked up in CWM when doing a wipe data/factory reset as instructed. I did a hard reset and tried to load Phiremod any way, which failed. I ended up using the backup I made of the rooted clean stock OS and it is working.
I read this thread
http://forum.xda-developers.com/showthread.php?t=1077973
and mine has the same issue of a partitioned eMMC that only reports 1GB. This prevents me from loading custom ROMs and side loading any applications.
One of the posts on that last thread mentions how dual booting essentially repartitions your eMMC to allow for the said dual booting, so I tried the "Step 1" in the repartition process here...
http://forum.xda-developers.com/showthread.php?t=959461
And it failed, but did boot back into my stock rooted OS.
My question is...
Is there a way to repartition my NC with what seems to be a new partition scheme that B&N moved to so that I can load custom ROMs, sideload programs, and/or dual boot off of eMMC?

Would like to see this answered as well.

grab your oars....
I'm in the same boat.... I have the 1 gig partition on my new Nook.
I can boot from SD ok but I would rather blow out the stock and save my SD.
Help?
MBK

Anyone out there can help us repartition the newer nooks?

side load partition 1 gb on newer NC's
guys check this out. I am doing it now and will report back after I get this done.
http://forum.xda-developers.com/showthread.php?t=914690
boot repartition with stock 1.0.0 or 1.0.1, then side load 1.2 update from b&n site:
http://www.barnesandnoble.com/u/nookcolor-support-software-update/379002520/
If I read all this correctly.. this should do the trick. as well as re-enabling apk installs correctly with rooted stock?

Already tried that.
You'll get a 1.0.0 or 1.0.1 with 0 Space available and you cannot sideload because of that. All that does is re-write the folders and not partition it.
I even tried changing the factory.zip with an older version in the /emmc and did a system/data wipe through the 8 boot fails and power + n reset.

One possibility
jb7038 said:
Anyone out there can help us repartition the newer nooks?
Click to expand...
Click to collapse
If you are familiar with fdisk and mkfs.ext2 or are willing to learn, and can boot a rooted OS from the SDcard, it should be trivial to delete, resize, repartition, and reformat /data (0p6 -- ext3), /cache (0p7 -- ext3) and /media (0p8 -- vfat). Do note the size of the partitions (especially 0p7/cache) before deleting them.
Then, when you restart the NC, it should recreate the contents of /data and /media to virgin content (meaning you better have backed up any non-B&N content). You will have to reregister with B&N, so you should probably do this on an UNROOTED Nook.
This is an experiment that I have wanted to try, but have not had the time; I've been too busy doing other experiments, like having B&N do the intentional repartitioning. I was using internal dual boot before, but uninstalled it before the repartitioning, because I knew there would not be enough space for dual boot afterwards.

I'm just unfamiliar with the block sizes and the commands to partition/change it.
/dev/block/mmcblk0p6 115 789 5421906 83 Linux
/dev/block/mmcblk0p7 790 834 361431 83 Linux
/dev/block/mmcblk0p8 835 965 1052226 c Win95 FAT32 (LBA)
Click to expand...
Click to collapse
6 938MB 6490MB 5552MB logical ext3
7 6490MB 6860MB 370MB logical ext3
8 6860MB 7937MB 1077MB logical fat32 lba
Click to expand...
Click to collapse
____________________________________________
I do have the NC I'm suppose to send back that's fully wiped.
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
4 heads, 16 sectors/track, 242432 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
~ #
Click to expand...
Click to collapse
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
(parted)
Click to expand...
Click to collapse
I'd be willing to partition it myself before I send it back if someone could walk me through it.

DeanGibson said:
If you are familiar with fdisk and mkfs.ext2 or are willing to learn, and can boot a rooted OS from the SDcard, it should be trivial to delete, resize, repartition, and reformat /data (0p6 -- ext3), /cache (0p7 -- ext3) and /media (0p8 -- vfat). Do note the size of the partitions (especially 0p7/cache) before deleting them.
Then, when you restart the NC, it should recreate the contents of /data and /media to virgin content (meaning you better have backed up any non-B&N content). You will have to reregister with B&N, so you should probably do this on an UNROOTED Nook.
This is an experiment that I have wanted to try, but have not had the time; I've been too busy doing other experiments, like having B&N do the intentional repartitioning. I was using internal dual boot before, but uninstalled it before the repartitioning, because I knew there would not be enough space for dual boot afterwards.
Click to expand...
Click to collapse
Dear God I would love to try but honestly I don't know a think about command line linux. Also, mine is already rooted, but I can always take it back to stock.
If someone gets this to work please document the process. I would really like to be able to use the internal memory for custom ROMs and be able to side load programs.

Anyone that can help us?

[Q] "Install failed" - partition broken?

Hi all,
I've got NST (with 1.1.0 software initially). After trying to root it properly I decided to restore original image and try again, because some added reader apps didn't start.
I tried to format NST as disk (deleting partition) and to write the ISO image I had (with my first backup).
After all, NST started as usual with "Read forever" screen and than after 10-15 second got "Install failed" screen.
Tried several recovery tools, they work from MicroSD, but after starting without memory card NST runs into the same screen.
Also tried "Touch-Formatter v2" CWM from this post
http://forum.xda-developers.com/showthread.php?t=1475613
Everything goes as expected, excepts strings appear such as:
"Can't mount /cache/recovery/last_log"
"Can't mount /emmc/"
etc.
But after reboot I have the same screen - "Install failed".
Also NST is not recognized in Windows as a mounted drive, just "unknown drive" appears for a second and then green light on NST turns yellow, and it goes for reboot.
If I use "mount USB storage" in CWM, connected NST is recognised as "bad disk" by Partition Manager.
Could anybody help?

dfche said:
I tried to format NST as disk (deleting partition)...
Click to expand...
Click to collapse
Why? Why do people do this?
dfche said:
... and to write the ISO image I had (with my first backup).
Click to expand...
Click to collapse
Ok, how big was the image and how did you try to write it?
It sounds like you trashed your partitions.
Why not use ADB on CWR, go to a shell and see what's left of your internal flash.
Code:
# busybox fdisk -l /dev/block/mmcblk0
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 47 141 194560 83 Linux
/dev/block/mmcblk0p4 142 926 1607680 5 Extended
/dev/block/mmcblk0p5 142 285 294896 83 Linux
/dev/block/mmcblk0p6 286 405 245744 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p7 406 525 245744 83 Linux
/dev/block/mmcblk0p8 526 926 821232 83 Linux

Renate NST said:
Why? Why do people do this?
Ok, how big was the image and how did you try to write it?
Click to expand...
Click to collapse
Mine was ~76MB. I used WinImage to write it.
Renate NST said:
Why not use ADB on CWR, go to a shell and see what's left of your internal flash.
Code:
# busybox fdisk -l /dev/block/mmcblk0
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 47 141 194560 83 Linux
/dev/block/mmcblk0p4 142 926 1607680 5 Extended
/dev/block/mmcblk0p5 142 285 294896 83 Linux
/dev/block/mmcblk0p6 286 405 245744 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p7 406 525 245744 83 Linux
/dev/block/mmcblk0p8 526 926 821232 83 Linux
Click to expand...
Click to collapse
My Windows PC doesn't see it at all. I tried "adb shell" command - "error: device not found"

dfche said:
Mine was ~76MB
Click to expand...
Click to collapse
Uh-oh.
You just made a backup of your boot partition, 1 of 8 partitions.
A full backup is on the order of 1.9 Gigs.
I hope that your formatting didn't destroy all your data.
You need to get ADB working with CWR and see what the damage is.
Try not to dig a bigger hole for yourself.
Take a look around these forums, there is tons of stuff about people who did the same as you.

Renate NST said:
Uh-oh.
You just made a backup of your boot partition, 1 of 8 partitions.
A full backup is on the order of 1.9 Gigs.
I hope that your formatting didn't destroy all your data.
You need to get ADB working with CWR and see what the damage is.
Try not to dig a bigger hole for yourself.
Take a look around these forums, there is tons of stuff about people who did the same as you.
Click to expand...
Click to collapse
Fortunately, I succeded writing backup image (shared by somebody on these forums) on NST with Noogie. It was almost 2 GB in size.
Thanks a lot for support!

Mmm, if you just duplicate somebody else's credentials you'll have a hard time registering for things.
You need the stuff out of your own /rom partition.

Renate NST said:
Mmm, if you just duplicate somebody else's credentials you'll have a hard time registering for things.
You need the stuff out of your own /rom partition.
Click to expand...
Click to collapse
I don't think I'll buy books from the B&N shop, but...
I found only one file that may be related to ROM - "romrestore.zip" in the very first image of my device.

dfche said:
Mine was ~76MB. I used WinImage to write it.
Click to expand...
Click to collapse
I´ve made the same mistake... your backup is useless... the correct file are bigger.
To correct this you will need to recover the ROM partition (have unique informations about your device) and replace this partition in a nook backup.
You can try this tutorial: http://forum.xda-developers.com/showthread.php?t=2104145
But the backup image available is for NSTG.

dfche said:
"romrestore.zip" in the very first image of my device.
Click to expand...
Click to collapse
romrestore.zip sounds good but it actually contains no personalized data.
You need stuff like in /rom/devconf:
DeviceID
SerialNumber
MACAddress
PublicKey
HashOfPrivateKey
There is /factory/rombackup.zip which does have what you want.
You can mount the /factory partition with CWR.

Renate NST said:
romrestore.zip sounds good but it actually contains no personalized data.
You need stuff like in /rom/devconf:
DeviceID
SerialNumber
MACAddress
PublicKey
HashOfPrivateKey
There is /factory/rombackup.zip which does have what you want.
You can mount the /factory partition with CWR.
Click to expand...
Click to collapse
The problem is that I have erased my own partition with everything excepts that small 76Mb part... It seems that "factory" sector has gone too.
But I think it's generally not a problem, if I don't need any service that checks some unique ID.

i have theoretical method
boot with noogie image , and use recovery programs to recover format files ,but the main problem is (u had overwrite the exist partition) and i think u cant recover it anymore
last thing ..... try to write ur backup (the corrupt 78 MB) to an sd card and hope that will share the Rom partition
PS : i was have same problem& mistake .... but i was lucky that my backup was with rom partition i from my corrupt backup
good luck

Like I said in my another post, try this:
http://forum.xda-developers.com/showthread.php?t=2104145
Specially this part:
-Recovering Partitions of a NSTG Accidentaly Formated:
Write noogie.img in a SD Card with WinImage (run as Administrator)
Insert SD in Nook and Boot ("Root Forever")
Open as Administrator MiniTool Partition Wizard.
Select Nook drive and click in "Partition Recovery Wizard".
Do a copy of "rom" partition to another SD card (or format noogie card and paste rom)
Click in "Apply" (top bar in the left) and wait complete the modifications​

ipedro3 said:
Like I said in my another post, try this:
http://forum.xda-developers.com/showthread.php?t=2104145
Specially this part:
-Recovering Partitions of a NSTG Accidentaly Formated:
Write noogie.img in a SD Card with WinImage (run as Administrator)
Insert SD in Nook and Boot ("Root Forever")
Open as Administrator MiniTool Partition Wizard.
Select Nook drive and click in "Partition Recovery Wizard".
Do a copy of "rom" partition to another SD card (or format noogie card and paste rom)
Click in "Apply" (top bar in the left) and wait complete the modifications​
Click to expand...
Click to collapse
the main idea of recovery is that repair the MBR for the formatted/deleted partition , so ...... if u overwrite , all data will gone
anyway try and wish to u good luck

[Q] In need of a BOOT.IMG dump

Long story short, I screwed up my internal memory partition table and believe I've got it back.
Problem: I need a dump of /dev/block/blkmmc0p1 (and p5) if at ALL possible from anyone that has a working Nook.Color.
My problem is similar to this one: http://forum.xda-developers.com/showthread.php?t=918772
If only the files on this page were still active on Mediafire: http://forum.xda-developers.com/showthread.php?t=919353
That's the long and short of it. If you guys want some additional info I can provide any information, but as I said, a dump of someones boot partition would definitely help.
Thanks all!
-Josh

Your PM to me says you flashed my 3 zips. I generally don't respond directly to PMs, I prefer the forums. I assume you meant my three zips in my partition repair thread. The repair 145678 zip has a dump of that partition built onto it. So if that flashed successfully, and it still will not let you boot, finding another dump file will not help. If you want one, extract the one from there.
You may need to describe more what you have done and how it is acting now.
Sent from my Nook HD+ running CM10 on Hybrid SD

OK, I'll just start from the beginning with what I've done:
I have a Nook Tablet (not talking about it, just saying... I'm in the right forum lol) and a friend got a Nook Color and wanted to know if I could soup it up the same way.
Well I had it working and like an idiot, I accidently used the Nook Tablet "swap storage" routine to make /sdcard1 <-> /sdcard0 instead of the one for the Nook Color. It took the flash fine and upon reboot it claimed that the SD Card needed to be prepared so I let it format the "card"
That's all she wrote so far. I rebooted it again and it wouldn't even come on. It was at 30% power when I told it to reboot, so I figured it was plagued by the sleep of death so I let it charge all night.
Woke up, still nothing.
I made a CWM bootable SD card and LO AND BEHOLD, it started up without a hitch!!! But it complained constantly of "/cache" not mounting to store its log files (that was earlier today and it has been a LONG day so I cant recount the exact error message). When I tried to install the ROM again, however it failed all around.
Your partition 2 repair file failed at first for me, that's how bad it was.
After many different attempts, I setup a bootable SD card with Nookie and get a little further.
With Nookie, I was able to FINALLY adb into the device and fdisk -l /dev/block/mmcblk0 which revealed an empty table and with wrong cylinder, head, and sector count, which I fixed by using the information found here: http://forum.xda-developers.com/showthread.php?t=942324
After that, I remade my CWM bootable SD card and got better results. /cache errors are gone and I was able to use all three of your zip files for repairing partitions (forgive me for not having the file names handy).
That has gotten me a little further, but now I keep getting errors about /boot not mounting.
Also, I haven't just been using CWM, but also TWRP (which thinks my serial number is all 0s), but when I manually mount /rom I can see in the devconf folder that my serial number has been restored (before I recreated partition table and ran your 3 zips, that wasn't even the case).
I'm sorry this is so scatter brained. I've been at it for a solid 10 hours all while laid up in bed with walking pneumonia, so..yeah...fun times..

It could also be that I didn't partition it properly because partition 1 (the only 1) seems to lose it's file system type every time, while the other 7 remain intact.

If it did not have the proper cylinder head count, how did you repartition it? That quoted thread just says what the proper layout should be, not how to repartition it.
Sent from my Nook HD+ running CM10 on Hybrid SD

Well, I'm not EXACTLY a total n00b. I looked up the busybox/fdisk syntax.
First I did fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0 (as it was reporting nothing right)
That command got me the proper size of the disk and I, with help of the "m" help command" recreated it to this (now that I have adb working in TWRP, I'm back to my preferred parted, so this is not an fdisk printout, but a parted printout):
Number Start End Size Type File system Flags
1 32.3kB 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7937MB 7477MB extended
5 461MB 938MB 477MB logical ext2
6 938MB 1941MB 1003MB logical ext3
7 1941MB 2311MB 370MB logical ext3
8 2311MB 7937MB 5626MB logical fat32 lba
In the past 5 minutes I have used mklabel to wipe partition table (shown above) again and am recreating them... again.
----EDIT-----
Here is that redone partition table:
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7944MB 7483MB extended lba
5 461MB 938MB 477MB logical ext2
6 938MB 1941MB 1003MB logical ext2
7 1941MB 2311MB 370MB logical ext2
8 2311MB 7944MB 5633MB logical fat32 lba

I'm not exactly a noob either and I could not find that -c -h -s command. I've been looking for that forever because I have a device that is showing the wrong count. So thanks.
Let me know how that new repartition comes out. I'll help if I can. I have all the images if you need them.
Sent from my Nook HD+ running CM10 on Hybrid SD

New layout:
Number Start End Size Type File system Flags
1 512B 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7944MB 7483MB extended lba
5 461MB 938MB 477MB logical ext2
6 938MB 1941MB 1003MB logical ext2
7 1941MB 2311MB 370MB logical ext2
8 2311MB 7944MB 5633MB logical fat32 lba
Of your 3 zips, 1, 4, 5, 6, 7, 8 repair seemed to work without error, but I'm back to partition 2 repair not working. ARGH, talk about a step backwards LOL.

jmh363905 said:
New layout:
Number Start End Size Type File system Flags
1 512B 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7944MB 7483MB extended lba
5 461MB 938MB 477MB logical ext2
6 938MB 1941MB 1003MB logical ext2
7 1941MB 2311MB 370MB logical ext2
8 2311MB 7944MB 5633MB logical fat32 lba
Of your 3 zips, 1, 4, 5, 6, 7, 8 repair seemed to work without error, but I'm back to partition 2 repair not working. ARGH, talk about a step backwards LOL.
Click to expand...
Click to collapse
I hope you saved an image of p3. That is critical.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
I hope you saved an image of p3. That is critical.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Hope of backing up any partitions went bye bye when I had to recreate the partition table the first time.
Now, is that the partition with devconf files or the factory.zip partition?
I'm still a bit unclear on that.

jmh363905 said:
Hope of backing up any partitions went bye bye when I had to recreate the partition table the first time.
Now, is that the partition with devconf files or the factory.zip partition?
I'm still a bit unclear on that.
Click to expand...
Click to collapse
P2 is the one with the devconf files. P3 has the factory.zip, but more importantly it has the rombackup.zip which was the backup of p2 when it was manufactured. That is what my p2 repair zip uses when it reconstructs p2. If you don't have that info, you will never be able to boot to stock again. But we can make dummy info so it can boot to CM. If you got a backup of the p2 before it died, you will be ok.
BTW, I just used your fdisk commands to fix my bad cylinder count. Thank you.
Sent from my Nook HD+ running CM10 on Hybrid SD

BTW, I just used you fdisk commands to fix my bad cylinder count. Thank you.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
No prob. That file is LOOOONG gone, but my only hopes are running CM10. Stock is for lusers. I have the serial number and wifi mac address written down so if we need to fake a few things, ANY help you can offer to get this thing working will be great.
I DID forget to mention that I have a TWRP backup of the Boot, Cache, System, and Data, but it won't restore :-/ I'm sure they're filled with all kinds of goodies.
Again, ANY HELP would be so great.
You tell me what you need me to submit and I'll be more than happy.

assert failed: (getprop("ro.product.device:") == "zoom2" || get prop("ro.build.product") == "zoom2") || getprop("ro.product.overallname:" == "NOOKcolor")
^^^ an error I'm getting trying to "install" the romrestore.zip file from my TWRP backup files. I'm not an expert, but is that saying my device and product name have been changed to something they shouldn't be?

jmh363905 said:
No prob. That file is LOOOONG gone, but my only hopes are running CM10. Stock is for lusers. I have the serial number and wifi mac address written down so if we need to fake a few things, ANY help you can offer to get this thing working will be great.
I DID forget to mention that I have a TWRP backup of the Boot, Cache, System, and Data, but it won't restore :-/ I'm sure they're filled with all kinds of goodies.
Again, ANY HELP would be so great.
You tell me what you need me to submit and I'll be more than happy.
Click to expand...
Click to collapse
You need to make three files to put in the devconf folder.
DeviceID has your 16 digit serial number
SerialNumber has the same info
MACAddress has your 12 digit MACaddress with no spaces or colons.
Also BootCnt should automatically get made by the system. It will not hurt to have a dummy one there. 4 bytes with nothing in it. That is the one that triggers an 8failed boot reset if it ever gets up to 8 in that file.
Also in the main folder should be a file call BCB (which means Boot Control Block). That should get created automatically by TWRP or CWM.
You get all that in there and flash a CM ROM and it should boot.
P3 does not matter unless there is a problem and stock recovery needs it. As long as you make sure that the DeviceID file is intact, you will never need p3.
Sent from my Nook HD+ running CM10 on Hybrid SD
---------- Post added at 06:50 PM ---------- Previous post was at 06:47 PM ----------
jmh363905 said:
assert failed: (getprop("ro.product.device:") == "zoom2" || get prop("ro.build.product") == "zoom2") || getprop("ro.product.overallname:" == "NOOKcolor")
^^^ an error I'm getting trying to "install" the romrestore.zip file from my TWRP backup files. I'm not an expert, but is that saying my device and product name have been changed to something they shouldn't be?
Click to expand...
Click to collapse
No, it is because the original device name was zoom2. You do not want to flash that anyway, since you do not have a working p3. It does the same as my repair p2 zip.
Sent from my Nook HD+ running CM10 on Hybrid SD

OK from ADB Shell, here are my commands so far:
cd /
mkdir rom
mount /dev/block/mmcblk0p2 rom
cd /rom
mkdir devconf
echo 2011460062572006 > DeviceID
echo 2011460062572006 > SerialNumber
echo 58671A19B85F > MACAddress
Do I need to chmod these files as well?

jmh363905 said:
OK from ADB Shell, here are my commands so far:
cd /
mkdir rom
mount /dev/block/mmcblk0p2 rom
cd /rom
mkdir devconf
echo 2011460062572006 > DeviceID
echo 2011460062572006 > SerialNumber
echo 58671A19B85F > MACAddress
Do I need to chmod these files as well?
Click to expand...
Click to collapse
Nope, once you verify those files are really there, just flash a CM ROM.
edit, well now that I think about it you might want to set it for 644. I usually flash those and that is what CWM sets them as.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
Nope, once you verify those files are really there, just flash a CM ROM.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
-- Install /sdcard/cm-10-20130324-NIGHTLY-encore.zip ...
Finding update package....
Opening update package....
Installing update.... (a couple minutes like it's doing something)
*Verifying filesystems....
* Verifying partition sizes...
E: Unable to mount '/boot' (tw_mount)
E: Unable to mount '/emmc' (tw_mount)
E: Unable to mount '/emmc' (tw_mount)
E: Failed to mount /emmc (Invalid argument)
E: Failed to mount /emmc (Invalid argument)
E: Failed to mount /emmc (Invalid argument)
Rebooting system after that yields in the same ole same ole: First, using the software reboot failes.....always.. I'm taken to a blank (not backlit) screen that I have to press and hold Power + Nook. If I press both of these and an SD card is present, I'll get recovery again. If an SD card isn't present, it just sits there with a blank screen. (not backlit)
Ready to put a hole through it. LOL

jmh363905 said:
-- Install /sdcard/cm-10-20130324-NIGHTLY-encore.zip ...
Finding update package....
Opening update package....
Installing update.... (a couple minutes like it's doing something)
*Verifying filesystems....
* Verifying partition sizes...
E: Unable to mount '/boot' (tw_mount)
E: Unable to mount '/emmc' (tw_mount)
E: Unable to mount '/emmc' (tw_mount)
E: Failed to mount /emmc (Invalid argument)
E: Failed to mount /emmc (Invalid argument)
E: Failed to mount /emmc (Invalid argument)
Rebooting system after that yields in the same ole same ole: First, using the software reboot failes.....always.. I'm taken to a blank (not backlit) screen that I have to press and hold Power + Nook. If I press both of these and an SD card is present, I'll get recovery again. If an SD card isn't present, it just sits there with a blank screen. (not backlit)
Ready to put a hole through it. LOL
Click to expand...
Click to collapse
Two things, look at my edit above. And did you format those partitions after creating them? You need to. flashing my repair zip and format zips will take care of 145678. You still need to manually format p2 as fat32.
Edit: It looks to me like TWRP is doing some more checking that CWM does not do. You might try using CWM while trying to fix this. Also the new TWRPs do not like my zips.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
Two things, look at my edit above. And did you format those partitions after creating them? You need to. flashing my repair zip and format zips will take care of 145678. You still need to manually format p2 as fat32.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
I verified that the files were still present after a reboot and they were (plus a Lost+Found directory indicates that there's an active, formatted partition), but I am going to go ahead and format both boot and rom with FAT32 file system:
ADB Shell Commands:
mkfs.vfat /dev/block/mmcblk0p1
mkfs.vfat /dev/block/mmcblk0p2
Then attempted restoring again. Same process as before, except NO errors AT ALL this time, so seeing it as a ray of hope, I followed it up with the GApps package (in hopes that THIS IS IT....)
Good news, PROGRESS has been made:
Now, WITHOUT an SD card, the unit will power on and give me the Cyanoboot Bootloader, but just hangs at loading from EMMC 01
What do you suggest now? ( and when this is all said and done with I'm gonna be needing your PayPal account so I can thank you)

Those other partitions need formatting too. Use my 5678 format zip.
Sent from my Nook HD+ running CM10 on Hybrid SD

E:Unable to mount '/data'

Working on my Mom's Nook Color. Rooted at one time, restored to stock. I believe something got nuked in the 1.4.1 to 1.4.3 update and because of it's age, B&N won't do a thing about it. So it's up to me. I'd like to restore it to stock if possible but even repairing the EMMC enough for a ROM would be fine as my mom has resorted to a SD ROM. I personally would like to fix this because I've never seen an Android device I couldn't fix (yet). I've tried both CWM and TWRP with the repartition zips, installing ROMs and stock files, etc. Only thing I haven't tried to manual creating partitions through ADB. Issue I'm getting is that no matter if I'm wiping or installing, I'm getting an "E:Unable to mount '/data'" error. Oddly enough, when booted into CM7 on the SD card, I can see the 5gb of user data partition and can even place the Nook update file on it (from B&N) but Nook recovery never sees it when I boot into it manually. The 8 failed boots recovery method is the only thing I haven't been able to try and I can't imagine it would do anything more than the partitioning zips. Anyone here have an insight on how to manually partition this thing or how to fix this NC through any other method?

Did you use my format zip after you ran my repartitioning zip? That would give that error if you forgot.
Yes, you can repair the emmc partition manually with fdisk in terminal emulator (TE) in CM7 on SD. First thing to do is to enter in su mode in TE by typing su enter. Then run this command:
fdisk -l /dev/block/mmcblk0
It should list the configuration of the partitions. I suspect your cylinder/head/sector (CHS) settings are wrong. It should say 965 cylinders, 255 heads, 63 sectors. If it does not say that, you need to repair it. Type:
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Then type the earlier command to make sure it is right.
Then you should be able to run my emmc repair zips and they should work.
Sent from my Nook HD+ running CM10 on Hybrid SD

Deleted upon request

40Glock said:
Well my heads are certainly off. Came up with 965 cylinders, 255 heads, 63 sectors. however, when I type in the fdisk commands you listed, it tells me "-:Unknown Command"
I tried running the 3 zips from your thread prior to posting this and I was still getting the data error. Guessing the heads are what's throwing it off so bad.
My partition list looks like this:
# busybox fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 935 7060567+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 236 979933+ 83 Linux
/dev/block/mmcblk0p7 237 281 361431 83 Linux
/dev/block/mmcblk0p8 282 935 5253223+ c Win95 FAT32 (LBA)
Click to expand...
Click to collapse
You are right, it should be 255, I was going from memory. I will correct the above post. (Also can you either remove my quoted post from your above reply or edit it so users do not see my incorrect post?) Your partition table is ok. But from looking at the print out, you have not successfully run my partition zips. If you had run it successfully, p4 would end on 965, not 935. But I still think you need to run my format zip.
Sent from my Nook HD+ running CM10 on Hybrid SD

May have a culprit though I'm not quite familiar with it. Getting a status 2 error when trying to flash, then it gives me the unable to mount data. So I'm not able to successfully flash the files. Must have missed it because I was focusing on the mount error. Going to see what I can track down about status 2 in TWRP unless you know off the top of your head.

40Glock said:
May have a culprit though I'm not quite familiar with it. Getting a status 2 error when trying to flash, then it gives me the unable to mount data. So I'm not able to successfully flash the files. Must have missed it because I was focusing on the mount error. Going to see what I can track down about status 2 in TWRP unless you know off the top of your head.
Click to expand...
Click to collapse
It is because you are using a new TWRP. It does not like my old zips. Either use CWM or use the older TWRP I have in my repair thread.
Sent from my Nook HD+ running CM10 on Hybrid SD

Nope, created a bootable SD using the TWRP in your thread. Gave me the same /data error after installing each of the zips. Tried installing 1.2 from the SD card, seemed to go fine but still gave me the /data error. I starting to think this is truly just a nuked Nook.

40Glock said:
Nope, created a bootable SD using the TWRP in your thread. Gave me the same /data error after installing each of the zips. Tried installing 1.2 from the SD card, seemed to go fine but still gave me the /data error. I starting to think this is truly just a nuked Nook.
Click to expand...
Click to collapse
Ok first, please remove my incorrect post you quoted above.
Second, it sounds like the recovery is needing a valid /data partition before it will let you flash. You can repair it manually using fdisk. I will send you the commands via PM so noobs do not try this and muck things up.
Sent from my Nook HD+ running CM10 on Hybrid SD

Corrected the quote, will be looking for the PM. Thanks for all your help man! I'm good with repairs generally but not to this depth.

40Glock said:
Corrected the quote, will be looking for the PM. Thanks for all your help man! I'm good with repairs generally but not to this depth.
Click to expand...
Click to collapse
It needs more correction than that. I suggest you just delete it. PM very shortly.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
It needs more correction than that. I suggest you just delete it. PM very shortly.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Done.

Well I'm booting to the N logo and freezing. When I was trying to flash a rom over it before, it would not mount /data in SD recovery. Cannot get to EMMC recovery. When I flash from the dual boot SD with CWM, it doesn't give me the /data mount error but it still doesn't boot past the N logo. Beginning to wonder if my EMMC bootloader is damaged.
Click to expand...
Click to collapse
Back from the PM exchange.
Let me explain how the booting works. A lot of this is explained in my NC Tips thread linked in my signature in item A12. There is more detail there.
When the nook boots, it looks at p2 to make sure everything is ok there. If it is not ok not it tries to boot to stock recovery to repair itself. If stock recovery is not there or corrupt it hangs on the N logo. Obviously yours is messed up. So yes, your emmc bootloader files are messed up. Usually flashing a ROM to emmc fixes that. My emmc partition repair zip also fixes that. But you have had no success with that.
Also, usually when it tries to boot to stock recovery and the SD is inserted, it will boot only to SD recovery, not an SD ROM which yours does. So that confuses me.
I personally don't like or trust TWRP. You said earlier you tried to use one of my bootable CWM cards and it gave the same can't mount /data error. Yet you say the dual boot CWM did not. That dual boot CWM has been modified to put things on SD, so I recommend trying my bootable CWM again.
Sent from my Nook HD+ running CM10 on Hybrid SD

Well I tried with CWM 5.5.0.4 and it was addressing mmcblk1p2 for some reason so now I'm writing 3.0.2.8 to an SD. If that doesn't work, I'll switch to an older CWM. If THAT doesn't work, it seems a vat of acid is in store...

40Glock said:
Well I tried with CWM 5.5.0.4 and it was addressing mmcblk1p2 for some reason so now I'm writing 3.0.2.8 to an SD. If that doesn't work, I'll switch to an older CWM. If THAT doesn't work, it seems a vat of acid is in store...
Click to expand...
Click to collapse
You need to explain these statements. How do you know it was addressing 1p2? You know that is normal for any CWM to do that? It is looking for a possible /sd-ext on SD. It has nothing to do with your issue. You know just enough to info to make bad assumptions. I'm just about to give up on you.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
You need to explain these statements. How do you know it was addressing 1p2? You know that is normal for any CWM to do that? It is looking for a possible /sd-ext on SD. It has nothing to do with your issue. You know just enough to info to make bad assumptions. I'm just about to give up on you.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
We're done here

40Glock said:
We're done here
Click to expand...
Click to collapse
I'm done too. Just one more comment. I'm not sure why you are concerned so much about getting emmc working when SD works for you. If it is because you want stock for your Mom, you can try my stock on SD in my B section of my NC tips thread. It may not work if your p2 is messed, but it might be worth a try for her.
Done.
Sent from my Nook HD+ running CM10 on Hybrid SD