Congrats to all who figured out the rooting process on NT. The NT has a measly 1gb media partition and over generous 11gb data partition. Can more experienced developers look into gparted-live-0.10.0-3.iso and e2fsprogs-1.41.14.tar.gz to use as tools to repartition the NT? I do not have a NT yet. I have a rooted emmc CM7.1 NC oc'd to 1.225gHz. I appreciate and respect all the effort that goes into this project. I used the develop financial apps for a big US bank.
Repartition media and data partitions on Nook Tablet
- Thread starter hwong96
- Start date
At best, repartitioning will give you an additional 1GB of space, and probably break the ability to ever do a factory restore or load additional updates when they are released by B&N.
I think we need to wait for an unlocked bootloader or at least an accessible CWM with bootable workaround (like on the Droids) before we start messing with the filesystem.
Current configuration allows 11gb for purchased apps, movies, books, music from Amazon app store, BN app store or Google market. Only 1gb is allowed for end user loaded music, books, movies etc. If you have over one thousand song music collection (5gb) you want loaded to NT you will need to use a microSD card. You cannot load an HD movie in the 1gb media partition. The old NC partition scheme had 5gb media and 1gb data. The newer NC partition scheme (blue dot) has 1gb media and 5gb data. Most users will not utilize the 11gb for purchased apps.
You can add custom search paths to some media players to scan /data/media (or whatever you want to call it). You might even be able to setup a symlink. You can also open the files (large movies, etc) directly from a file manager like Root Explorer.
I do see your point, though, how the layout is different from the NC. I'm using a 32gb memory card so I guess this isn't an issue for me.
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.
B
bx19
Guest
What about in a linux distribution like ubuntu? I know that windows doesn't read ext4 (unless 3rd party drivers are installed) nor the first partition (if the nook tablet is really partitioned, that is).
You can store files on the EXT4 partition and access them through a file manager, but it won't appear as a drive on your computer when you connect it. You would have to copy files to an SD card, then from the SD card (plugged into the Nook) to the /data partition.
I'm working on a way to create a "virtual" FAT filesystem within /data that would be mounted to /media instead. This would allow you to use around 10GB for media (while leaving 1GB for /data). The best part is that it doesn't require any repartitioning or reformatting and can be easily undone.
I'm working on a way to create a "virtual" FAT filesystem within /data that would be mounted to /media instead. This would allow you to use around 10GB for media (while leaving 1GB for /data). The best part is that it doesn't require any repartitioning or reformatting and can be easily undone.
If you can't wait for that virtual mount to work (which sounds super cool, by the way; would a different approach be to look at the smb.conf in the Samba server for Android and share /data via Samba over the network? I've read the 'stock' samba server can't share linux filesystems, but I can't help but wonder if that can't be overridden in .conf) you can do some fugly hacking like I did on the NST:
On the NC and NST, /data is an android-only vanilla filesystem
/mnt/media is the filesystem that is swapped out of Android for copying in from Windows.
On a rooted device where /data is not full, you can use fdisk (or busybox fdisk in case you have not symlinked busybox to the commands it supports) to shrink /data. I would do this over a wireless connection, so that you don't get involved in both partition editing and unmount/remount at power on.
If the /data partition is the LAST partition listed by /mount, you can delete it and resize it hot very easily.
delete it.
hit n
create the 'new' partition as a smaller size.
w to write your changes.
You get an error about the kernel still using the old partitioning. You don't care. Reboot, and your /data partition has shrunk. Now might be a good time to run fsck on that new, smaller paritition. You'll get a warning about running fsck on a mounted disk. On a device with a resized partition and no actual filesystem damage, this has not been an issue for me. YMMV.
Then you would need to delete and recreate /mnt/media to the desired size, toggle the partition label to make it a fat filesystem, reboot, confirm that those boundaries worked also, and then run mkfs.vfat (if I'm remembering correctly) on your new partition.
The tricky bit is getting the partition order correct in a complicated filesystem like this one.
On the NST, you don't actually have to get everything just right.
I found that out by happy accident - I wanted to resize /data and /media there, and they are partition 6 and 8 respectively.
The first time I did it, I was confused about which set of notes described what. When the device failed to start 8 times, it looked at the world and realized a reimage was needed, and formatted the available ext fileystems as /data and /cache, and the fat filesystem as /media.
I did not realize this until quite recently, when I needed to reimage my NST to apply update 1.1, and lo and behold: the partition table after reimaging from stock was not in the order I'd ultimately imposed on it the first time.
I do not know how robust the recovery on the NT is.
Seems to me this is a great time to find out - but I would only muck around with the /data and /media and not touch anything below those, and I don't have one of the NTs so my money's not at risk.
On the NC and NST, /data is an android-only vanilla filesystem
/mnt/media is the filesystem that is swapped out of Android for copying in from Windows.
On a rooted device where /data is not full, you can use fdisk (or busybox fdisk in case you have not symlinked busybox to the commands it supports) to shrink /data. I would do this over a wireless connection, so that you don't get involved in both partition editing and unmount/remount at power on.
If the /data partition is the LAST partition listed by /mount, you can delete it and resize it hot very easily.
delete it.
hit n
create the 'new' partition as a smaller size.
w to write your changes.
You get an error about the kernel still using the old partitioning. You don't care. Reboot, and your /data partition has shrunk. Now might be a good time to run fsck on that new, smaller paritition. You'll get a warning about running fsck on a mounted disk. On a device with a resized partition and no actual filesystem damage, this has not been an issue for me. YMMV.
Then you would need to delete and recreate /mnt/media to the desired size, toggle the partition label to make it a fat filesystem, reboot, confirm that those boundaries worked also, and then run mkfs.vfat (if I'm remembering correctly) on your new partition.
The tricky bit is getting the partition order correct in a complicated filesystem like this one.
On the NST, you don't actually have to get everything just right.
I found that out by happy accident - I wanted to resize /data and /media there, and they are partition 6 and 8 respectively.
The first time I did it, I was confused about which set of notes described what. When the device failed to start 8 times, it looked at the world and realized a reimage was needed, and formatted the available ext fileystems as /data and /cache, and the fat filesystem as /media.
I did not realize this until quite recently, when I needed to reimage my NST to apply update 1.1, and lo and behold: the partition table after reimaging from stock was not in the order I'd ultimately imposed on it the first time.
I do not know how robust the recovery on the NT is.
Seems to me this is a great time to find out - but I would only muck around with the /data and /media and not touch anything below those, and I don't have one of the NTs so my money's not at risk.
Here is how you repartition /data and /media partitions using Gparted and e2fsprogs as done by a Kindle Fire owner. Methodology is same for Nook Tablet.
http://xdaforums.com/showthread.php?t=1388996
http://xdaforums.com/showthread.php?t=1388996
Partitioning seems different as that Extremely Well done set of instructions for a fire only seems to use GParted which I don't believe understands the partitions on th NT???
I could very easily be wrong and if you tried and were successful doing this on an NT then I apologize and want to buy you a case of beer for your efforts to help us all on the NT.... just I'm skeptical as NT doesn't use traditional FS layout or format as far as I believe...
If this worked for you PM me with some proof and your paypal and I'll pay up with thanxs added... else I just felt obliged to question and put my money where my mouth is to save others from at a min. soft bricking their NT...
I still haven't picked up an NT yet so I did not try this yet.
For discussion only.
I would think the repartitioning process is simpler than the Kindle Fire since the /media(vfat) and /data(ext4) partitions are at the end of the SD. Gparted does not create ext4 partitions. Gparted can create ext2 partitions and e2fsprogs changes ext2 to ext4 if I follow the logic correctly. My first step would be to make a backup of the /data partition. Then I would delete /data partition. Then I would increase the /media partition using GParted. Then I would create the /data partition as ext2 using GParted. Then using commands in e2fsprogs to convert format to ext4. Then restore the /data backup from the first step.
Here is the NT partitions from NookDevs
http://www.nookdevs.com/Dump_NookTablet_Partitions
For discussion only.
I would think the repartitioning process is simpler than the Kindle Fire since the /media(vfat) and /data(ext4) partitions are at the end of the SD. Gparted does not create ext4 partitions. Gparted can create ext2 partitions and e2fsprogs changes ext2 to ext4 if I follow the logic correctly. My first step would be to make a backup of the /data partition. Then I would delete /data partition. Then I would increase the /media partition using GParted. Then I would create the /data partition as ext2 using GParted. Then using commands in e2fsprogs to convert format to ext4. Then restore the /data backup from the first step.
Here is the NT partitions from NookDevs
http://www.nookdevs.com/Dump_NookTablet_Partitions
Last edited:
Not yet! An update to it today actually has gparted displaying the partition correctly (it wasn't before? I thought it had ok support for ext4 partitions before, or since 2009ish), so pretty sure they're working on it. I'd be inclined to wait for official support over making ext2 partitions tbh
Last edited:
Has anyone tried it? I wish to try, but don't understand how to make those binaries work, coz KF used CWM, which we don't have yet! Can anyone direct me?
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
29Since 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.2
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.2
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 Tablet2
No, I typed 15.6 but it extended to 15.9 (the end of the drive) automatically.
