Database Users

[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]help i soft bricked my phone

hi guys i am in a big mess
1)i tried installing official 2.3.5 final and my phone(u8800) started bootlopping after factory reset i managed to start it once.
2)i restarted my phone after rooting it and had again bootloops that i didnt ever manage to overcome.
3)so i desided that i should reflash official(and the desaster started)update failed on 99% and the worst bootloader locked .
4)i tried installing an official froyo also failed at 99% but bootloader unlocked
5)now i am on ubuntu able to see pink screen files but unfortunately i dont have dd back up but i have many back ups from cwm on my sd from custom roms is there any posibility to unbrick my phone?
ps for admin sorry for same thread but the other started writing in some unknown language to me

Can you access recovery?
So you downgraded to 2.2, which version B138?
can you try to access recovery? official will do for factory reset, if doesn't start again try to flash it again, and after that do wipe and factory reset from recocery...
I managed to downgrade like that also failed at 99% but with factory reset the phone started normally...

Atanasov Goran said:
So you downgraded to 2.2, which version B138?
can you try to access recovery? official will do for factory reset, if doesn't start again try to flash it again, and after that do wipe and factory reset from recocery...
I managed to downgrade like that also failed at 99% but with factory reset the phone started normally...
Click to expand...
Click to collapse
1)yes my 2.2 froyo is 138 from how to root ginerbred thread and after this flash i lost adb compatibility in windows so now i am in ground zero if ther is a way to flash something from ubuntu or backtrack in bootloader mode because even after that still no access to phone not even from pc on cwm to see my sd card
2)in simple boot my phone stacks on huawei logo,i can also get to recovery menu and finaly and i think the most helpfull i can get pink screen and mount my files on linux.
3)i have also try to recover in last saved working recovery (custom rom)
4)i think that something went wrong with my partitions but i realy need help from a developer because i dont know what to do

try this
try to wipe/factory reset from the official recovery, should start normaly after that, my phone did the same when i downgraded from 2.3 stoped at 99% and said that the update failed but after a factory reset booted normaly

Maybe a partition is damaged.
Try from linux on pink screen to check partitions for errors. Maybe you can fix it like this and after to successfully flash the update.

dancer_69 said:
Maybe a partition is damaged.
Try from linux on pink screen to check partitions for errors. Maybe you can fix it like this and after to successfully flash the update.
Click to expand...
Click to collapse
can you give some info how to do that i see 3 partitions of 105mb,235 and recovery partition only who auto mount and on gparted i see 4gb unreachable
do you mean just to check disk this partitions ?

I haven' t specific infos, I'm using linux very rear the last year. I think that you can use the fsck tool of linux. You can find a lot of info about how to check partitions for linux if you search on google. Just be careful to not format them or erase them.

Tranos said:
can you give some info how to do that i see 3 partitions of 105mb,235 and recovery partition only who auto mount and on gparted i see 4gb unreachable
do you mean just to check disk this partitions ?
Click to expand...
Click to collapse
You should see 13 partitions total if you look at the drive with parted or gparted etc.. And yeah you could run fsck on all the ext3/ext4/fat32 partitions. But if you don't see all the 13 partitions in parted / gparted then I think the partition table is damaged or some weird bootloader lock issue.

after some tries and stock reflashes i am now on official cwm recovery and trying to wipe data/factory resets returns me an error :
E:cant mount @(or /dev/block/mmcblk0p13) both wipe and format same error
can you candly send me the official recovery files and what should i have in(i think something after so many custom roms failed)
and this are the partitions i can see now

You could run gparted and note down all partitions which are ext3, ext4 or fat32. Then you can check the disks with "sudo fsck /dev/sdxx". Also I can post my partition table later when I'm on my comp so you could compare it to yours.
Sent from my u8800 using xda premium

thies are all partitions but i think there are too many anallocated
Code:
GNU Parted 2.3
Using /dev/sdd
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Error: Invalid partition table on /dev/sdd -- wrong signature 0.
Ignore/Cancel? i
Model: Qualcomm MMC Storage (scsi)
Disk /dev/sdd: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 252MB 252MB primary fat32
2 252MB 252MB 512kB primary boot
3 252MB 255MB 3072kB primary
4 255MB 3959MB 3704MB extended
5 268MB 281MB 12,6MB logical
6 336MB 472MB 136MB logical ext3
7 537MB 537MB 512kB logical
8 604MB 607MB 3146kB logical
9 671MB 678MB 7168kB logical
10 738MB 741MB 3146kB logical
11 805MB 808MB 3146kB logical
12 872MB 1103MB 231MB logical ext3
(parted)
2 partitions are missing

Here's how mine looks. I'm guessing you don't have a dd backup of the whole phone? Anyway if your partition table is messed up, it would be possible to clone my partition table. Only the partition table, and leaving all other data intact. It would probably be a good idea also to check with others if the partition table is always exactly the same on all phones, or if there are different flash mems or something with diff. tables. Also did you run fsck on 1,6,12 and 13?
Code:
$ [B]sudo parted /dev/sdc[/B]
GNU Parted 2.3
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) [B]p[/B]
Model: Huawei eMMC Storage (scsi)
Disk /dev/sdc: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 252MB 252MB primary fat32
2 252MB 252MB 512kB primary boot
3 252MB 255MB 3072kB primary
4 255MB 3959MB 3704MB extended
5 268MB 281MB 12.6MB logical
6 336MB 472MB 136MB logical ext4
7 537MB 537MB 512kB logical
8 604MB 607MB 3146kB logical
9 671MB 678MB 7168kB logical
10 738MB 741MB 3146kB logical
11 805MB 808MB 3146kB logical
12 872MB 1103MB 231MB logical ext2
13 1141MB 1770MB 629MB logical ext4
14 1812MB 3959MB 2147MB logical fat32
(parted)

do you know how ican fix my partitions again or should i sent it to service tbh it is huawei fault that my phone doesnt work now

I checked my partition table(I have 2.3 installed, not 2.2) and are same that ksata' s, except partition 12 which is in ext3, not ext2.
But I think that on 2.2 rom the partition table has 12 partitions and not 14(I've used command cat /proc/mounts some times when a was on 2.2 rom and always partitions count was until 12). So, I don' t think that it' s something wrong with the partition table.
But maybe some of the existing partitions is damaged and when update tries to write on it, gets an error and update stops.
You can check the ext2/3/4 partitions from gparted. First umount a partition end then check it(if you right click on a partition these options are available on the menu)

Looks like I have bricked mine too.. pretty badly. When updating to 2.3 if fails at step 2 (40 %) and shows "update failed" (same with 2.2). Can't access recovery either. In pink screen Windows and Ubuntu doesn't mount any partitions..
Looks like I have to send it in to change motherboard, but if any have suggestions how to fix it please tell me
ps. was on Cm7 before this happened.

skifyr123 said:
Looks like I have bricked mine too.. pretty badly. When updating to 2.3 if fails at step 2 (40 %) and shows "update failed" (same with 2.2). Can't access recovery either. In pink screen Windows and Ubuntu doesn't mount any partitions..
Looks like I have to send it in to change motherboard, but if any have suggestions how to fix it please tell me
ps. was on Cm7 before this happened.
Click to expand...
Click to collapse
Try to flash using internal SD card. Also, one user reported that removing battery worked.

Blefish said:
Try to flash using internal SD card. Also, one user reported that removing battery worked.
Click to expand...
Click to collapse
How to access internal when you can't boot (not even to recovery)? Tried to remove battery, but didn't work..

1)i managed to solve my problem by using the genokolars re-partition to stock from modaco and the partition zip that is at a reply of him not post start thank you everybody for the try .and after reflashed the chinese stock 162
2)but now i have nulled imei can i restor it by some clock works recoveries or ther is no way to restore it(i dont have dd back up)

skifyr123 said:
How to access internal when you can't boot (not even to recovery)? Tried to remove battery, but didn't work..
Click to expand...
Click to collapse
Have the same issue. Did you try to work it out somehow?
Try look at my thread here:
http://forum.xda-developers.com/showthread.php?t=1466953

Unable to to Boot after CM7 install

A friend of mine tried to install CM7 on his NookColor. Something went wrong and so he brought it to me. I've done dozens of these. I thought it would be an easy fix so I stuck in my trusty SD boot card with encore_CM72-MiRaGe-03042012. I booted into CWM and did a factory reset and installed encore_CM72-MiRaGe-03042012. I booted it up and expected it to be fixed.
It did the same thing this time which is to boot to the initial splashcreen and then go blank. You can tell the screen is still backlit, but it never changes. You have to hold the power button for 30 seconds to turn it off.
When I boot back into CMW I see some unexpected messages
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
I tried installing CM7 again and watched the messages closely. It says
Installeding update
Install from sdcard complete.
Reboots the same way
Can anyone point me in the right direction to fix this? Thanks

Well, I spent all day yesterday Googling and searching all the forums on XDA Of course I started with Dummies Guide to Fixing 'My Nook Won't Boot'. It is incredibly out of date and is likely to do more harm than good. I think that if it is going to be a sticky, then at least it should show current, relevant information.
I tried [HOW-TO] : Restore Nook Color back to stock EASILY!. I was unable to format several of the partitions specified, but proceeded anyway. It appeared to install OK, but now I am stuck at the N when it boots.
I am continuing to search but I keep running into dead links, downloads that say they will take 5 hours, and references to outdated files. I really would appreciate some knowledgeable help here guys. Thanks

I have the same deal. I think since the WIP clockwork update. I've tried most of the fixes from the links as I still have most. I tried everything you have as well as trying restoring and using different versions of clockwork and trying to get a cache up to no avail. The please keep me posted because this is the first replica of my situation. I am using an Asus t101 now so I'm in no hurry but I've had me NC forever and love the reading size.
Good luck.
How do you create or fix the cache for e:? I can you ADB into clockwork?

Just in case anyone ever reads this thread I thought I would give some more information regarding my problem.
I am able to get into CWM 3.2.0.1 internally. I stiil can't get any ROM loaded though. ( I have loaded several different ROMS to the NC previously including the CM7 nightlies from 75 to 130, so I am well versed in how to do it).
I'm thinking there is something wrong with my partitons. I'm not well versed in exactly what happens during the boot process and what is on each partiton.
I though it might be useful for those people who know about this stuff if I supplied more info (since my eyesight is giving out from reading so many threads)
If I go into the mounts and storage menu and do severals format, this is what I get.
Format system - Error formatting /system!
Format data- Error formatting /data!
Format cache- Error formatting /cache!
I was afraid to format emmc or boot.
Does this help anyone?

Have you tried creating a bootable CWM SD card? That always helps me out when things get screwy.
Tried the EMMC recovery repair?
p.s. - NEVER format Boot. You'll have many a difficulty if you do.

I do have a CWM SD card and can boot to that as well.
Neither one works. I tried installing
nookcolor_1_4_1_update.zip
update-nc-stock-1.3.zip
encore_CM72-MiRaGe-03232012.zip
All leave me where I am now

How old is the nook?
What happened when your friend tried to install cm7? What was going on with it prior to installation?

Don't really have much info.
I have no idea how old the NC is.
I believe that the guy had stock B&N running and tried to install CM7 (verson unknown) with a bootable microSD card, I don't know if he was using the latest CWM on the card.

Um........mail it to me. I'll fix it.
Minimum fees apply.

Here's another clue.
I have a dual boot SD card made based on the instructions in
[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [3/26].
If I use it on a stock B&N NC, the SD card works correctly.
If I use it in the borked NC, it still boots into a black screen.
I would prefer to try to resolve this mayself. I have 20+ years in PC support and feel if I can just get the right information, I can fix it.
If I can't get it done in the next 3 or 4 days, I may take you up on it. However, the frind would have to OK it and I don't know how he feels about sending it off. Thanks
BTW, I tried plugging in the USB cable to see if maybe I could try some ADB magic, but the laptop slings an error when trying to load the driver.

Let me amend that last post. I tried the dual boot (this time using the alternate boot image) and successfully got into CM9. Does this help me?

I am trying to find a way to fdisk or mount a way to change pemissions to rw,mode=0755 or but cannot find the usb yet. I will see what I can google.
Seems the emmc permissions are wrong possibly.
Edit: this is what my mount says about the nook when I mount it to linux:
/dev/sdb on /media/0838-AA8D type vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks)

Since I have thee NC booting to CM9 off the SD card, I thought I would load ADB and see if there was something I could do..
I went to [Ref] Nook Color Links |Guides|How To|Utilities| Etc. 12/26 Read FIRST =) in the developer's section and went to the referenced
•Nook Color USB Drivers and ADB Setup (WinXP&7)
The links in that thread are dead. Can someone point out a link to the current prefered method?

have you tried
[UPDATE ZIP] Stock 1.2 update.zip flashable from CWM
from showthread.php?t=1050520

This is nookcolor easy adb 3:
http://db.tt/b3XfztAY
And the USB files file NC:
nookcolor usb
http://db.tt/QRhksG2n

Hi there,
If you are able to boot to CM9 off the sDcard. Try opening up terminal emulator and enter the following commands:
Code:
$ su
# fdisk -l /dev/block/mmcblk0
and paste the output here. That should give you you're EMMC partition layout.
-Racks

Yeah, what racks said. Sounds like you formatted your emmc boot partition to me. In one of the old resurrected threads that you posted to, the OP flat out says they formatted boot.
Don't format boot, everyone.
Post the output of racks command, and we'll know for sure.
If you just formatted (read: erased) the boot partition, then your ROM partition should be intact. That means 8 failed reboot can load the stock firmware. It may be a last-ditch effort for many, but it doesn't require any adb knowledge our even a computer, so I tend to recommend it early.
Reboot as it is loading the cyanogen screen eight times while holding down power,n, and the volume keys. If it doesn't work the first time, do the entire sequence again. Of course, if you enter rack's command, you will see if your ROM partition is still intact which is required for this method to work.

[email protected]:/ # fdisk -l /dev/block/mmcblk0
Warning: invalid flag 0x00,0x00 of partition table 5 will be corrected by w(rite)
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
[email protected]:/ #

Bonnie_Raitt said:
[email protected]:/ # fdisk -l /dev/block/mmcblk0
Warning: invalid flag 0x00,0x00 of partition table 5 will be corrected by w(rite)
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
[email protected]:/ #
Click to expand...
Click to collapse
Yep, your missing the last 4 partitions which are /system, /data, /cache, /media. Which you would need to flash any rom. You're gonna have to re-create them by using fdisk from and SDcard ROM (eg. CM7 or CM9). There's a thread here somewhere that dealt with all that. I'll browse through and see if I can find it for you.
-Racks

This it?
http://forum.xda-developers.com/showthread.php?t=958748
Not sure how to rebuild the missing partitions yet. Appreciate the help fellas.

[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

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