Repartition media and data partitions on Nook Tablet

Search This thread
By:
Advanced…
H

Hamington

Member
Feb 5, 2012
9
1
tselling said:
Since I had a second NT to repartition, I wrote up the how I did it this time. Hopefully it is useful to someone. USE AT YOUR OWN RISK. You are responsible if you mess up your tablet.

Repartitioning your Nook Tablet requires ADB drivers on your PC and CWM installed either to EMMC or SDCARD. Here, I resized my userdata partition to approximately 4GB and my media partition to approximately 9GB. NOTE: ONLY MESS WITH Partitions 10 & 11 (media and userdata). I assume you know or can lookup how to install and use CWM and adb.

Parted complains about the partition table.... I let it fix the two errors. I don't know if that is good or not but hasn't seemed to hurt my NT. I think you can just ignore the errors... but they are very annoying throughout the process, if you don't fix them.

Install CWM either SDCARD or EMMC. Make sure you can use adb to connect to your Nook Tablet. If not, fix that first. Boot into CWM. In CWM mount /data and /sdcard and do a backup so you can restore /data since we are going to delete and recreate it. After the backup, unmount /data.
Use "adb shell" while CWM is running on the Nook Tablet and the USB cable is plugged in.

Note: Once done with the the resizing, have CWM reboot back to recovery (advanced option) and restore your /data partition data. Then reboot your system.

Here is a quick summary: Start parted on mmcblk0 from adb shell. Fix the errors. Delete partition 11 (userdata). Resize partition 10 (media) to make it larger... use the original start position and change the end position to make it the size you want. Recreate partition 11... use the end position from partition 10 as the new start position and use the original end position. Name partition 11 "userdata". Print the partition table along the way to make sure that its what you want. Exit parted. Use tune2fs and e2fsck to convert the ext2 partition back to an ext4 partition. Reboot back into CWM, restore your data partition and then reboot.


The commands I used while in the adb shell, along with the responses are below. Note that the bold text is the prompt and commands. The non-bold parts are screen output.

~ # 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
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? f
f
f
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
continue with the current setting?
Fix/Ignore? f
f
f
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB fat32 media
11 2684MB 15.6GB 12.9GB ext4 userdata

(parted) rm 11
rm 11
rm 11
(parted) resize
resize
resize
Partition number? 10
10
10

Start? [1611MB]?



End? [2684MB]? 11.6GB
11.6GB
11.6GB
(parted) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres

(parted) mkpartfs primary ext2
mkpartfs primary ext2
mkpartfs primary ext2
Start? 11.6GB
11.6GB
11.6GB
End? 15.6GB
15.6GB
15.6GB


(parted)
(parted) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
11 11.6GB 15.9GB 4326MB ext2

(parted) name 11 userdata
name 11 userdata
name 11 userdata
(parted) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
11 11.6GB 15.9GB 4326MB ext2 userdata

(parted) quit
quit
quit
Information: You may need to update /etc/fstab.

~ # tune2fs -j /dev/block/mmcblk0p11
tune2fs -j /dev/block/mmcblk0p11
tune2fs 1.41.6 (30-May-2009)
Creating journal inode: done
This filesystem will be automatically checked every 30 mounts or
0 days, whichever comes first. Use tune2fs -c or -i to override.

~ # e2fsck -fDp /dev/block/mmcblk0p11
e2fsck -fDp /dev/block/mmcblk0p11
/dev/block/mmcblk0p11: 11/529056 files (0.0% non-contiguous), 49429/1056092 blks

~ # tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p11
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p11
tune2fs 1.41.6 (30-May-2009)

Please run e2fsck on the filesystem.

~ # e2fsck -fDp /dev/block/mmcblk0p11
e2fsck -fDp /dev/block/mmcblk0p11
/dev/block/mmcblk0p11: Group descriptor 0 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 1 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 2 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 3 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 4 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 5 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 6 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 7 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 8 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 9 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 10 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 11 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 12 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 13 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 14 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 15 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 16 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 17 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 18 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 19 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 20 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 21 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 22 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 23 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 24 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 25 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 26 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 27 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 28 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 29 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 30 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 31 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 32 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Adding dirhash hint to filesystem.

/dev/block/mmcblk0p11: 11/529056 files (0.0% non-contiguous), 49429/1056092 bl
ks
~ # 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) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
11 11.6GB 15.9GB 4326MB ext4 userdata

(parted) quit
quit
quit

*****
Now reboot back into recovery (advanced option). Restore your data partition and reboot system.
Click to expand...
Click to collapse

Where would you get the ADB drivers?
 
T

tgraves

Member
Jun 15, 2010
39
34
Los Altos, CA
ms2003 said:
Thank you very much, I used your script to repartition, it's perfect!

but when I do a factory reset in CMW, it will raise an error:
format_volume: make_extf4fs failed on /dev/block/mmcblk1p2
is this normal?
Click to expand...
Click to collapse
Yes, the error is normal.

Reboot out of CWM to Nook OS (Nook will act like new tablet, because data is gone). Then reboot back into CWM(power+N button if internal CWM), and perform an advanced restore of your data partition, after restoring data, reboot again and you should be good to go.

I had to mess with my keyboards to get them back and running OK.
 
M

ms2003

Senior Member
Jan 22, 2010
163
19
ShangHai
yes, CM7 is better except video issue

---------- Post added at 02:06 AM ---------- Previous post was at 01:50 AM ----------
tselling said:
Since I had a second NT to repartition, I wrote up the how I did it this time. Hopefully it is useful to someone. USE AT YOUR OWN RISK. You are responsible if you mess up your tablet.
.......................
(parted) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres

(parted) mkpartfs primary ext2
mkpartfs primary ext2
mkpartfs primary ext2
Start? 11.6GB
11.6GB
11.6GB
End? 15.6GB
15.6GB
15.6GB


(parted)
(parted) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
11 11.6GB 15.9GB 4326MB ext2
.................
Click to expand...
Click to collapse

I see when create partition 11, you typed ends at 15.6GB, but after that, it shows end at 15.9GB, is that a type mistake?
 
Last edited:
M

meghd00t

Senior Member
Jul 13, 2011
111
141
Bangalore
ms2003 said:
yes, CM7 is better except video issue

---------- Post added at 02:06 AM ---------- Previous post was at 01:50 AM ----------



I see when create partition 11, you typed ends at 15.6GB, but after that, it shows end at 15.9GB, is that a type mistake?
Click to expand...
Click to collapse

NO, it is using all the space till the end of the disk, if you look further up when parted is fixing the layout it finds space at the end of the disk which is unused.
 
  • Like
Reactions: ms2003
U

uouo521

New member
Dec 8, 2010
1
0
filename problem

everything works fine after I repartitioned media with @tselling ‘s script
Thanks him
but I have some problem with filename
If I named file with Chinese or Japanese. the filename all become "?" when I try to find them on the device.
p.s I can see the correct file name on the computer when I connected the USB
any helps?
 
E

esmith1359

Member
Feb 26, 2012
8
1
Sorry to pester, I'm a total noob to this site and only somewhat familiar with rooting and android hacking. I just rooted my wife's NT last night using the liliputing article titled "How to install CyanogenMod 7 alpha on a NOOK Tablet"

Now I want to use the method shown in this thread to fix the partitions for the same reasons everybody else does this.

Can someone help me understand this?

I am assuming that:

1) I will need to install special drivers/software on my laptop and possibly on the NT before I begin
2) I will be entering these shell type commands on my PC and they will get injected via USB and into the NT using said software
3) This will need to be done while the NT is booted into the CWM main menu, but that's only to make sure that certain partitions aren't being used while we re-size them, NOT because we'll be using the CWM to actually do anything...

My questions:
What is ADB?
How do I check to see if this CMV7 I installed last night already has ADB and everything else I need to run the commands?
Also, what extra software should I have on my PC to get started and where should I get it?

Thanks again for your patience, hard work, and anything further you can tell me
 
  • Like
Reactions: fyrmd
L

lavero.burgos

Senior Member
Mar 5, 2011
2,836
1,392
esmith1359 said:
Sorry to pester, I'm a total noob to this site and only somewhat familiar with rooting and android hacking. I just rooted my wife's NT last night using the liliputing article titled "How to install CyanogenMod 7 alpha on a NOOK Tablet"

Now I want to use the method shown in this thread to fix the partitions for the same reasons everybody else does this.

Can someone help me understand this?

I am assuming that:

1) I will need to install special drivers/software on my laptop and possibly on the NT before I begin
2) I will be entering these shell type commands on my PC and they will get injected via USB and into the NT using said software
3) This will need to be done while the NT is booted into the CWM main menu, but that's only to make sure that certain partitions aren't being used while we re-size them, NOT because we'll be using the CWM to actually do anything...

My questions:
What is ADB?
How do I check to see if this CMV7 I installed last night already has ADB and everything else I need to run the commands?
Also, what extra software should I have on my PC to get started and where should I get it?

Thanks again for your patience, hard work, and anything further you can tell me
Click to expand...
Click to collapse

1)you will need to install drivers and setup ADB only if you used the sdcard method to boot into cwm and flash CM7 directly and you did not use your PC to root stock.
2)yes
3)exactly

http://xdaforums.com/showthread.php?t=1474956

That link will explain to you how to use ADB so you get familiar and I also include the necessary drivers to make it work. As for how to install the drivers you need to watch a video made by AlbertWertz, you can find it in my FAQ here in general section 2ND post or google free how to root nook tablet part 1 by AlbertWertz.

~ Veronica

Sent from XDA premium using my Nook Tablet :p
 
Last edited:
  • Like
Reactions: esmith1359 and fyrmd
E

esmith1359

Member
Feb 26, 2012
8
1
lavero.burgos said:
1)you will need to install drivers and setup ADB only if you used the sdcard method to boot into cwm and flash CM7 directly and you did not use your PC to root stock.
2)yes
3)exactly

http://xdaforums.com/showthread.php?t=1474956

That link will explain to you how to use ADB so you get familiar and I also include the necessary drivers to make it work. As for how to install the drivers you need to watch a video made by AlbertWertz, you can find it in my FAQ here in general section 2ND post or google free how to root nook tablet part 1 by AlbertWertz.

~ Veronica

Sent from XDA premium using my Nook Tablet :p
Click to expand...
Click to collapse

Thanks :) I used the sd card method but I had some issues. When I used indirect's method I could create a bootable sd card to load CWM, but I couldn't add the zip for flashing CMV7 to the sd card because the free space had magically vanished or something. I tried using a bigger card but no luck. I assume this is related to the "specific geometry" he was describing in his instructions.

Anyway, I just connected my NT to my laptop before I started and copied the CMV7 zip file to the NT's internal (measly 1gb I might add) memory so that CWM could find it there. It worked out.
 
A

ag94

Member
Nov 13, 2011
20
2
esmith1359 said:
I could create a bootable sd card to load CWM, but I couldn't add the zip for flashing CMV7 to the sd card because the free space had magically vanished or something. I tried using a bigger card but no luck. I assume this is related to the "specific geometry" he was describing in his instructions.
Click to expand...
Click to collapse

you can create a bootable card with 2GB partition (instead of 50 MB, as described in manual).
 
E

esmith1359

Member
Feb 26, 2012
8
1
how would you reverse this operation?

Ok, so There's a decent chance I'll do this soon. I've been thinking about it for awhile now. How hard is it to repartition the drive back to the crummy 1gb stock configuration so I could reflash stock rom without errors and shamelessly seek any needed warranty service? What would be the script to reverse this?
 
M

meghd00t

Senior Member
Jul 13, 2011
111
141
Bangalore
First off you will be able to use the stock recovery to upgrade B&N firmware, the upgrade process does not reset the partition tables

or

use cwm recovery and adb to reverse the changes it is very easy.
 
CRE

CRE

Senior Member
Feb 24, 2008
300
52
tselling said:
Parted complains about the partition table.... I let it fix the two errors. I don't know if that is good or not but hasn't seemed to hurt my NT. I think you can just ignore the errors... but they are very annoying throughout the process, if you don't fix them.


......

(parted) print
print
print
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? f
f
f
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
continue with the current setting?
Fix/Ignore? f
f
f
Click to expand...
Click to collapse

Is everyone opting to fix these GPT complaints? Does everything work fine if they're left intact?

I'm just wondering if this is something B&N may use as a red flag should a device come in under warranty... I'm probably just being overly paranoid (as usual). I'd just like to be sure I could get it back as close to stock as possible, if desired.
 
M

meghd00t

Senior Member
Jul 13, 2011
111
141
Bangalore
yes, you will need to fix the gpt errors otherwise parted will not go ahead and create the new partitions. From what I can see, very soon (one we have fastboot working - thanks to fattire & cyanoboot) we can fastboot oem format to fix the partitions back
 
C

css771

Member
Aug 26, 2010
31
3
For some reason I did not get the initial gpt errors. As a result the userdata partition ends at 15.6GB and does not extend to 15.9GB. But the repartitioning worked. I just have this ~300MB "missing"? Just curious why this is. Anyone have any ideas about this?
 
Last edited:
M

meghd00t

Senior Member
Jul 13, 2011
111
141
Bangalore
I just discovered that there is a 4EXT recovery which contains mkfs.ext4 mkdosfs If someone can pull that apart and stuff the mkfs.ext4 into cwm then the extra steps to make the filesystems can be simplified a whole lot.
 
You must log in or register to reply here.

Similar threads

I
[Blocks OTA's!] Full root for Nook Tablet. [11/20/11] [Permanent root!]
Replies
975
Views
836K
Modded Darts
Modded Darts
CelticWebSolutions
[ROM] CM7 8GB &16GB Compatible Beta for the Nook Tablet.., Updated 7th July to Beta
Replies
1K
Views
643K
nmyshkin
nmyshkin
C
[DEV] [ROM] CM9 for Nook Tablet Alpha 0.06
Replies
846
Views
456K
Drebin 894
Drebin 894
K
[KERNEL][3.0.21+][HD video working now on 16Gb NT] Nook Tablet ICS kernel development
Replies
843
Views
343K
C
chrmhoffmann
malloneem
Nook Tablet 1.4.3 complete root guide for 8or16gb to GB and JB
Replies
144
Views
180K
T
TurtlJ

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 29
    T
    tselling
    Since I had a second NT to repartition, I wrote up the how I did it this time. Hopefully it is useful to someone. USE AT YOUR OWN RISK. You are responsible if you mess up your tablet.

    Repartitioning your Nook Tablet requires ADB drivers on your PC and CWM installed either to EMMC or SDCARD. Here, I resized my userdata partition to approximately 4GB and my media partition to approximately 9GB. NOTE: ONLY MESS WITH Partitions 10 & 11 (media and userdata). I assume you know or can lookup how to install and use CWM and adb.

    Parted complains about the partition table.... I let it fix the two errors. I don't know if that is good or not but hasn't seemed to hurt my NT. I think you can just ignore the errors... but they are very annoying throughout the process, if you don't fix them.

    Install CWM either SDCARD or EMMC. Make sure you can use adb to connect to your Nook Tablet. If not, fix that first. Boot into CWM. In CWM mount /data and /sdcard and do a backup so you can restore /data since we are going to delete and recreate it. After the backup, unmount /data.
    Use "adb shell" while CWM is running on the Nook Tablet and the USB cable is plugged in.

    Note: Once done with the the resizing, have CWM reboot back to recovery (advanced option) and restore your /data partition data. Then reboot your system.

    Here is a quick summary: Start parted on mmcblk0 from adb shell. Fix the errors. Delete partition 11 (userdata). Resize partition 10 (media) to make it larger... use the original start position and change the end position to make it the size you want. Recreate partition 11... use the end position from partition 10 as the new start position and use the original end position. Name partition 11 "userdata". Print the partition table along the way to make sure that its what you want. Exit parted. Use tune2fs and e2fsck to convert the ext2 partition back to an ext4 partition. Reboot back into CWM, restore your data partition and then reboot.


    The commands I used while in the adb shell, along with the responses are below. Note that the bold text is the prompt and commands. The non-bold parts are screen output.

    ~ # 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
    Error: The backup GPT table is not at the end of the disk, as it should be.
    This might mean that another operating system believes the disk is smaller.
    Fix, by moving the backup to the end (and removing the old backup)?
    Fix/Ignore/Cancel? f
    f
    f
    Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
    used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
    continue with the current setting?
    Fix/Ignore? f
    f
    f
    Model: MMC SEM16G (sd/mmc)
    Disk /dev/block/mmcblk0: 15.9GB
    Sector size (logical/physical): 512B/512B
    Partition Table: gpt

    Number Start End Size File system Name Flags
    1 131kB 262kB 131kB xloader
    2 262kB 524kB 262kB bootloader
    3 524kB 16.3MB 15.7MB recovery
    4 16.8MB 33.6MB 16.8MB boot
    5 33.6MB 83.9MB 50.3MB fat32 rom
    6 83.9MB 134MB 50.3MB fat32 bootdata
    7 134MB 522MB 388MB ext4 factory
    8 522MB 1164MB 642MB ext4 system
    9 1164MB 1611MB 447MB ext4 cache
    10 1611MB 2684MB 1074MB fat32 media
    11 2684MB 15.6GB 12.9GB ext4 userdata

    (parted) rm 11
    rm 11
    rm 11
    (parted) resize
    resize
    resize
    Partition number? 10
    10
    10

    Start? [1611MB]?



    End? [2684MB]? 11.6GB
    11.6GB
    11.6GB
    (parted) p
    p
    p
    Model: MMC SEM16G (sd/mmc)
    Disk /dev/block/mmcblk0: 15.9GB
    Sector size (logical/physical): 512B/512B
    Partition Table: gpt

    Number Start End Size File system Name Flags
    1 131kB 262kB 131kB xloader
    2 262kB 524kB 262kB bootloader
    3 524kB 16.3MB 15.7MB recovery
    4 16.8MB 33.6MB 16.8MB boot
    5 33.6MB 83.9MB 50.3MB fat32 rom
    6 83.9MB 134MB 50.3MB fat32 bootdata
    7 134MB 522MB 388MB ext4 factory
    8 522MB 1164MB 642MB ext4 system
    9 1164MB 1611MB 447MB ext4 cache
    10 1611MB 11.6GB 9989MB fat32 media msftres

    (parted) mkpartfs primary ext2
    mkpartfs primary ext2
    mkpartfs primary ext2
    Start? 11.6GB
    11.6GB
    11.6GB
    End? 15.6GB
    15.6GB
    15.6GB


    (parted)
    (parted) p
    p
    p
    Model: MMC SEM16G (sd/mmc)
    Disk /dev/block/mmcblk0: 15.9GB
    Sector size (logical/physical): 512B/512B
    Partition Table: gpt

    Number Start End Size File system Name Flags
    1 131kB 262kB 131kB xloader
    2 262kB 524kB 262kB bootloader
    3 524kB 16.3MB 15.7MB recovery
    4 16.8MB 33.6MB 16.8MB boot
    5 33.6MB 83.9MB 50.3MB fat32 rom
    6 83.9MB 134MB 50.3MB fat32 bootdata
    7 134MB 522MB 388MB ext4 factory
    8 522MB 1164MB 642MB ext4 system
    9 1164MB 1611MB 447MB ext4 cache
    10 1611MB 11.6GB 9989MB fat32 media msftres
    11 11.6GB 15.9GB 4326MB ext2

    (parted) name 11 userdata
    name 11 userdata
    name 11 userdata
    (parted) p
    p
    p
    Model: MMC SEM16G (sd/mmc)
    Disk /dev/block/mmcblk0: 15.9GB
    Sector size (logical/physical): 512B/512B
    Partition Table: gpt

    Number Start End Size File system Name Flags
    1 131kB 262kB 131kB xloader
    2 262kB 524kB 262kB bootloader
    3 524kB 16.3MB 15.7MB recovery
    4 16.8MB 33.6MB 16.8MB boot
    5 33.6MB 83.9MB 50.3MB fat32 rom
    6 83.9MB 134MB 50.3MB fat32 bootdata
    7 134MB 522MB 388MB ext4 factory
    8 522MB 1164MB 642MB ext4 system
    9 1164MB 1611MB 447MB ext4 cache
    10 1611MB 11.6GB 9989MB fat32 media msftres
    11 11.6GB 15.9GB 4326MB ext2 userdata

    (parted) quit
    quit
    quit
    Information: You may need to update /etc/fstab.

    ~ # tune2fs -j /dev/block/mmcblk0p11
    tune2fs -j /dev/block/mmcblk0p11
    tune2fs 1.41.6 (30-May-2009)
    Creating journal inode: done
    This filesystem will be automatically checked every 30 mounts or
    0 days, whichever comes first. Use tune2fs -c or -i to override.

    ~ # e2fsck -fDp /dev/block/mmcblk0p11
    e2fsck -fDp /dev/block/mmcblk0p11
    /dev/block/mmcblk0p11: 11/529056 files (0.0% non-contiguous), 49429/1056092 blks

    ~ # tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p11
    tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p11
    tune2fs 1.41.6 (30-May-2009)

    Please run e2fsck on the filesystem.

    ~ # e2fsck -fDp /dev/block/mmcblk0p11
    e2fsck -fDp /dev/block/mmcblk0p11
    /dev/block/mmcblk0p11: Group descriptor 0 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 1 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 2 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 3 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 4 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 5 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 6 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 7 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 8 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 9 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 10 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 11 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 12 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 13 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 14 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 15 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 16 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 17 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 18 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 19 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 20 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 21 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 22 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 23 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 24 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 25 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 26 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 27 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 28 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 29 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 30 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 31 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Group descriptor 32 checksum is invalid. FIXED.
    /dev/block/mmcblk0p11: Adding dirhash hint to filesystem.

    /dev/block/mmcblk0p11: 11/529056 files (0.0% non-contiguous), 49429/1056092 bl
    ks
    ~ # 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) p
    p
    p
    Model: MMC SEM16G (sd/mmc)
    Disk /dev/block/mmcblk0: 15.9GB
    Sector size (logical/physical): 512B/512B
    Partition Table: gpt

    Number Start End Size File system Name Flags
    1 131kB 262kB 131kB xloader
    2 262kB 524kB 262kB bootloader
    3 524kB 16.3MB 15.7MB recovery
    4 16.8MB 33.6MB 16.8MB boot
    5 33.6MB 83.9MB 50.3MB fat32 rom
    6 83.9MB 134MB 50.3MB fat32 bootdata
    7 134MB 522MB 388MB ext4 factory
    8 522MB 1164MB 642MB ext4 system
    9 1164MB 1611MB 447MB ext4 cache
    10 1611MB 11.6GB 9989MB fat32 media msftres
    11 11.6GB 15.9GB 4326MB ext4 userdata

    (parted) quit
    quit
    quit

    *****
    Now reboot back into recovery (advanced option). Restore your data partition and reboot system.
    View
    2
    T
    tselling
    bigbug2428 said:
    my Nook raise same error: format_volume: make_extf4fs failed on /dev/block/mmcblk1p2, when i reboot, my Nook still boot in CWM again and again (with or without sd card). Do i have a chance to fix it?
    Click to expand...
    Click to collapse

    Not sure why it is giving that error. mmcblk1 would be the sdcard and you shouldn't have been messing with that. You should have been changing mmcblk0 and only partitons 10 & 11. I would boot back into CWM and use ADB to recheck the partitions and be sure they look right. If partition 11 is not ext4 and labeled userdata then you didn't do something right and you might want to redo it.
    View
    2
    L
    lavero.burgos
    esmith1359 said:
    Sorry to pester, I'm a total noob to this site and only somewhat familiar with rooting and android hacking. I just rooted my wife's NT last night using the liliputing article titled "How to install CyanogenMod 7 alpha on a NOOK Tablet"

    Now I want to use the method shown in this thread to fix the partitions for the same reasons everybody else does this.

    Can someone help me understand this?

    I am assuming that:

    1) I will need to install special drivers/software on my laptop and possibly on the NT before I begin
    2) I will be entering these shell type commands on my PC and they will get injected via USB and into the NT using said software
    3) This will need to be done while the NT is booted into the CWM main menu, but that's only to make sure that certain partitions aren't being used while we re-size them, NOT because we'll be using the CWM to actually do anything...

    My questions:
    What is ADB?
    How do I check to see if this CMV7 I installed last night already has ADB and everything else I need to run the commands?
    Also, what extra software should I have on my PC to get started and where should I get it?

    Thanks again for your patience, hard work, and anything further you can tell me
    Click to expand...
    Click to collapse

    1)you will need to install drivers and setup ADB only if you used the sdcard method to boot into cwm and flash CM7 directly and you did not use your PC to root stock.
    2)yes
    3)exactly

    http://xdaforums.com/showthread.php?t=1474956

    That link will explain to you how to use ADB so you get familiar and I also include the necessary drivers to make it work. As for how to install the drivers you need to watch a video made by AlbertWertz, you can find it in my FAQ here in general section 2ND post or google free how to root nook tablet part 1 by AlbertWertz.

    ~ Veronica

    Sent from XDA premium using my Nook Tablet :p
    View
    2
    T
    tselling
    ms2003 said:
    yes, CM7 is better except video issue

    ---------- Post added at 02:06 AM ---------- Previous post was at 01:50 AM ----------



    I see when create partition 11, you typed ends at 15.6GB, but after that, it shows end at 15.9GB, is that a type mistake?
    Click to expand...
    Click to collapse

    No, I typed 15.6 but it extended to 15.9 (the end of the drive) automatically.
    View
    1
    hwong96
    hwong96
    The data partition is ext4 formatted whereas the media partition is vfat formatted. When the NT is connected to a computer via USB, the vfat system is what the user sees for loading his own content. I do not think the ext4 partition shows up as a drive on the computer.
    View

New posts