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

[HOWTO] flash stock rom without internal sd (Movinand chip damaged and removed)

This guide for GTP1000 internal SD damaged and removed
This link is guide how to remove movinand chip:
http://forum.xda-developers.com/showthread.php?t=1877585
How to flash Overcome Stock ROM
- to prepare you must have
Overcome gb_Stock_save_v5.tar (modem.bin needed),
overcome_kernel_v4.0.0.tar or CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
and root explorer.apk,
- make 3 partition on microSD, 1st fat32, 2nd ext4, 3th ext4,
example : 16 gb -> 13.6gb fat32, 2gb ext4, 0.4gb ext4
use gparted on linux or MiniTool Partition (Windows)
- remove hidden.rfs, movinand.mst from GB_Stock_Save_v5.tar
- copy root explorer.apk to microSD, then plug to gtp1000
- turn on download mode, flash by odin, DON'T CHECK REPARTITION
- after finished, auto restart and will showed error MBR bla bla
(because movinand doesn't exists anymore), ignore it,
if doesn't boot but cwm recovery then wipe factory reset/data, wipe partition,
reboot system
- wait for about 5 - 10 minute, then turn off
- download mode, Flash kernel your choose (must be suport ext4), restart automaticaly when finished. wait until everyting done.
- Unplug usb from PC, on your gtab go to setting, application,
check mark -> Unknown source
development,
check mark -> USB debugging
- connect usb to PC, use adb from PC, and follow this code:
c:\adbtool\adb shell
~$
if your access not root then type
~$ su
take a look your GTP1000 superuser message, then tab allowed
~# mount -t vfat /dev/block/mmcblk0p1 /sdcard
- run my files on your gtab, explore and install root explorer.apk
- open root explorer, tap mount R/W, tap and hold vold.fstab on /system/etc,
select "open in text editor" edit follow this:
# internal sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = disable
discard = disable
format_option = -r 1558
}
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.2/mmc_host/mmc1
# externel sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
asec = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
save, exit from root explorer, restart gtab, and profit
Edit:
If overcome kernel fail then try CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar

One think i wanna know..
Why internal-sd broken??
I dont know is corrupt is similar with broken or not but overcome kernel (now with my personal kernel) on recovery mode with parted command can solve my internal-sd problem..

I don't know why
May be oc then over heating or else, but last i use is wifi theater for a long time then turn off by self, stuck on samsung logo when i turn on again
So i restock with overcome, nothing happen, restock samsung firmware, nothing happen too, edit some rc not work too, edit file on /system/etc/init.d and vold.fstab not fully function.
Google it, and found someone (CrhisCTX)with the same problem and he fix by removed movinand chip.
http://forum.xda-developers.com/showthread.php?t=1877585
Sent from my GT-P1000

Would you share your personal kernel for me or us
Sent from my GT-P1000

Btw,
Remove partition and recreate it by parted, doesn't work for me, when i restart partition will back as it, and data still there, some kind read only partition, i don't know
Sent from my GT-P1000

goofey2012 said:
Btw,
Remove partition and recreate it by parted, doesn't work for me, when i restart partition will back as it, and data still there, some kind read only partition, i don't know
Sent from my GT-P1000
Click to expand...
Click to collapse
Im sorry my english is not good enough but can u give 'mount' and 'parted /dev/block/mmcblk0 print' result ?
If internal-sd broken so which partition u use for /data ? As long as i know /data use mmcblk0p2 and if internal-sd broken i thing u can use that partition too..

Yes it is, thats why i create 3 parition. Fat32,ext4,ext4
After remove movinand chip from main board, mmcblk1 automaticaly known as mmcblk0, but the blocks still on /sys/devices/platform/s3c-sdhci.2/mmc_host/mmc1
mmcblk0p3 mount as /preload (note: on gb)
mmcblk0p2 mount as /data
mmcblk0p1 not automaticaly mount as /sdcard
So thats why i need edit vold.fstab manualy
Sent from my GT-P1000

Mmm i see maybe internal-sd is realy broken not only corrupt.. coz if only corrupt parted, fat.format, mkfs.ext2 or other command can solve it..

savie said:
Mmm i see maybe internal-sd is realy broken not only corrupt.. coz if only corrupt parted, fat.format, mkfs.ext2 or other command can solve it..
Click to expand...
Click to collapse
Can you share the code how to mount external sd like your pic attach in other thread.
savie said:
How about this one...
Click to expand...
Click to collapse
Sent from my GT-P1000

mounting script
Sorry for late respon.. I only add that script to init.d folder.. Make sure mmcbkl1p2,3,4 as ext4 if that partition as rfs so need edit ext4 to rfs on script file..
I use that script to check/modify my 2ndRom on 1stRom..

savie said:
mounting script
Sorry for late respon.. I only add that script to init.d folder.. Make sure mmcbkl1p2,3,4 as ext4 if that partition as rfs so need edit ext4 to rfs on script file..
I use that script to check/modify my 2ndRom on 1stRom..
Click to expand...
Click to collapse
I think your script doesn't change /data to mmcblk1p2
Sent from my GT-P1000

goofey2012 said:
I think your script doesn't change /data to mmcblk1p2
Sent from my GT-P1000
Click to expand...
Click to collapse
Yupz its doesnt as i say before it only help me to know my 2ndRom is exsist when i use my 1stRom..
Dont confuse with double mount /system (thats bugs on my kernel till now) in fact its /system running on mmcblk1p2

i would to thank you
so i've try it but i know nothing about android system files so i 'm a big noob )
but :
i 've flashed like you say just the rom i ve used overcome 7 4.10
How to flash Overcome Stock ROM
- to prepare you must have
Overcome_7_Series_v4.1.0_Wipe
overcome_kernel_v4.0.0.tar or CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
- make 3 partition on microSD, 1st fat32, 2nd ext4, 3th ext4,
example : 16 gb -> 13.6gb fat32, 2gb ext4, 0.4gb ext4
use gparted on linux or MiniTool Partition (Windows)
and edit vold.fstab with note pad with
- open Overcome_7_Series_v4.1.0_Wipe in winrar "windows users",vold.fstab on /system/etc,
select "open in notepad ++" edit follow this:
# internal sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = disable
discard = disable
format_option = -r 1558
}
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.2/mmc_host/mmc1
# externel sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
asec = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
save your new file in the overcome zip and boot your gtp1000 tab in recovery mod and go to install zip from internal and let do it the gtp1000 will reboot , it's take time so and you will see your fat 32 partition as internal sd ))) i hope taht answer will help
thank too all develloppers

why only this stock ROM can be flashed ? I want arabic stock ROM how can I flash ? I tried but with no success

Weird ! I followed all steps but I don't see my FAT partition ( 13gb ) in phone Storage ! what's wrong ?
what's working vold.fstab I have to use to solve that ?

bump !

psytr0nic said:
Weird ! I followed all steps but I don't see my FAT partition ( 13gb ) in phone Storage ! what's wrong ?
what's working vold.fstab I have to use to solve that ?
Click to expand...
Click to collapse
yes
mine too
please help..
what to do ...

im not sure this thing work really ... I tried about 3 times on 3 different phones! best seem to change emmc chip

I'm curious as to feasibility of either swapping this Chip for a larger 32GB Chip, or simply replacing it if need be.
Seems to me the hard part would be finding the correct kind of Glue to use though. I can't imagine that getting hold of these Chips would be any more harder then any other Part of the P1000...

cocomeoo said:
yes
mine too
please help..
what to do ...
Click to expand...
Click to collapse
let me see your vold.fstab

[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