webOS & CM7 - Adjusting/Premake CM7 custom size partitions

---

HOWTO for anyone interested: Updated on 2011 12-13
Update: resolved 'major:minor pair unavailable'
Update: Works for 32GB HP Touchpad and 16GB HP Touchpad

Credits to: 
webos-internals.org/wiki/How_To_Recover#Doctor_disconnects_at_8.25
for the 32GB HP Touchpad filesystem creation example

[FIRST]
1) THIS PROCESS WILL COMPLETELY WIPE YOUR TOUCHPAD! WEBOS, CM7,
    & ANYTHING ELSE YOU'VE INSTALLED!!
2) This process also assumes you can get functional terminal to your HP
    Touchpad already via novaterm, novacom open TTY://, or with putty.
3) This process also assumes you know how to install CM7 already.

YOU WILL ALSO NEED:
webOS Doctor version 3.0.0
webOS Doctor version 3.0.4
from All HP WebOS Doctor Versions:
webos-internals.org/wiki/Webos_Doctor_Versions 

[NOW START]
1) Put your HP Touchpad in webOS Recovery Mode:
   a. Power off the HP Touchpad or reset it with [Power Button] + [Home]
   b. Hold [Up Volume] + [Power Button] until you see a usb symbol on screen.
2) Start up taskmanager in Windows:
   a. [CTRL]+[ALT]+[DEL] and select task manager
3) Run webOS Doctor and let it run to 8% then use taskmanager to end task 
    on webOS doctor.
4) Open up windows command prompt and type in: novacom open TTY://
5) Run the following commands [CASE SENSITIVE] type it exactly as shown
    and make sure to get the numbers after --minor correct:

    [Note: Don't bother customizing webOS partitions because in this process
              webOS doctor will re-size them back to the following anyways.]

   a. lvm.static vgscan --ignorelockingfailure
   b. lvm.static vgchange -ay --ignorelockingfailure
   c. lvm.static vgremove store
   d. lvm.static vgscan --ignorelockingfailure
   e. lvm.static vgchange -ay --ignorelockingfailure
   f. lvm.static vgcreate -s 8M store /dev/mmcblk0p14
   g. lvm.static vgscan --ignorelockingfailure
   h. lvm.static vgchange -ay --ignorelockingfailure
   i. lvm.static lvcreate -l 71 -M y --major 254 --minor 0 -n root store
   j. lvm.static lvcreate -l 8 -M y --major 254 --minor 1 -n var store
   k. lvm.static lvcreate -l 2 -M y --major 254 --minor 2 -n update store
   l. lvm.static lvcreate -l 3 -M y --major 254 --minor 3 -n log store
   m. lvm.static lvcreate -l 32 -M y --major 254 --minor 4 -n mojodb store
   n. lvm.static lvcreate -l 17 -M y --major 254 --minor 5 -n filecache store

   NOTE: THE FOLLOWING --minor JUMPS to 7 from 5 above
   o. lvm.static lvcreate -l 64 -M y --major 254 --minor 7 -n swap store

   NOTE: THE FOLLOWING MAKES CM7 PARTITIONS, I specified a 5GB cm-data
             partition, you can do more or less. 1 Physical Extent (PE) is 8MB.
             The number after -l is the number of Physical Extents for
             the partition.
   p. lvm.static lvcreate -l 96 -M y --major 254 --minor 8 -n cm-system store
   q. lvm.static lvcreate -l 32 -M y --major 254 --minor 9 -n cm-cache store
   r. lvm.static lvcreate -l 640 -M y --major 254 --minor 10 -n cm-data store

   NOTE: The following creates the media partition used as SDCARD and sets
             it to --minor 6, make sure you set it to --minor 6, the SDCARD is
             specified as dm-6 in CM7. This will save you from having to edit
             /etc/vold.fstab in CM7.
   s. lvm.static vgscan --ignorelockingfailure
   t. lvm.static vgchange -ay --ignorelockingfailure
   u. lvm.static vgdisplay
      i. this command displays information on the Volume Group: store
         at the bottom you should see:
         Free PE/Size        X / XX
         where X is the number of Physical Extents free and XX is the size free.
      ii. write down the number of X (Physical Extents free) to use in the
         next command
   v. lvm.static lvcreate -l X -M y --major 254 --minor 6 -n media store
   w. lvm.static vgscan --ignorelockingfailure
   x. lvm.static vgchange -ay --ignorelockingfailure
   y. mkdosfs -f 1 -s 64 -F 32 /dev/store/media
   z. mkfs.ext4 /dev/store/cm-system or mkfs.ext3 /dev/store/cm-system
   za. mkfs.ext4 /dev/store/cm-cache or mkfs.ext3 /dev/store/cm-cache
   zb. mkfs.ext4 /dev/store/cm-data or mkfs.ext3 /dev/store/cm-data
   zc. run webOS Doctor 3.0.0 and let it complete and let it reboot to
        the language selection screen
   zd. reset the HP Touchpad with [POWER BUTTON] + [HOME] and put it into
        webOS Doctor recovery mode with [POWER BUTTON] + [VOLUME UP].
   ze. run webOS Doctor 3.0.4 and let it complete and let it reboot and
        complete webOS install and go into webOS.

If you did everything right, you now have an HP Touchpad tablet with a fresh
webOS 3.0.4 and pre-created CM7 partitions. Now, just follow the standard
CM7 install procedure after you boot into webOS 3.0.4 to install CM7.
ACMEInstaller will use the cm-system, cm-cache, and cm-data file system
you've already created. :) Enjoy.

webOS Doctor 3.0.0 is required. If you do not run this first, other webOS
Doctor version will fail. webOS Doctor 3.0.0 resizes and formats partitions
as needed, the other versions seem to no longer have this and fail when
the webOS partitions aren't perfect in format/size.

Thanks for the detailed response from my post on Xron Dev Thread.

Based on the following site...

http://www.webosbuzz.com/hp-touchpad...a2-1-here.html

saying the following

"One thing to know is that the space in the /boot partition is extremely limited at the moment, and cannot be easily re-sized, as it will freak out WebOS Doctor and may create other issues. Unless and until the /boot partition can be extended, this size limitation will affect the number of OSes that can be squeezed onto the TouchPad at one time."

How does this affect/react with your 5GB cm-data size?

There is a typo in line V.

It reads:

. lvm.static lvcreate -l X -M y --major 254 --minor 6 -m media store

but should read:

. lvm.static lvcreate -l X -M y --major 254 --minor 6 -n media store

Just a head's up for those who get stuck at that point with error messages.

Originally Posted by herrdude

There is a typo in line V.

It reads:

. lvm.static lvcreate -l X -M y --major 254 --minor 6 -m media store

but should read:

. lvm.static lvcreate -l X -M y --major 254 --minor 6 -n media store

Just a head's up for those who get stuck at that point with error messages.

You need to replace X with the number of Physical Extents obtained from the previous few lines of instructions. X is a variable.

Originally Posted by qwerty007

You need to replace X with the number of Physical Extents obtained from the previous few lines of instructions. X is a variable.

it would seem he is referring to last "-m". in his its "-n" before media store.

Originally Posted by havikx

it would seem he is referring to last "-m". in his its "-n" before media store.

lol. yeah i realized that after i posted, then it said you're new so you have to wait 5, min so i couldn't make a fix to my post. lol. then i had to go to work. anyhow, noted and fixed. thanks guys.

Originally Posted by flashypants

Thanks for the detailed response from my post on Xron Dev Thread.

Based on the following site...

http://www.webosbuzz.com/hp-touchpad...a2-1-here.html

saying the following

"One thing to know is that the space in the /boot partition is extremely limited at the moment, and cannot be easily re-sized, as it will freak out WebOS Doctor and may create other issues. Unless and until the /boot partition can be extended, this size limitation will affect the number of OSes that can be squeezed onto the TouchPad at one time."

How does this affect/react with your 5GB cm-data size?

i think /boot is a webOS partition and not a CM partition. i haven't tried it, but increasing the size of the partitions shouldn't kill webOS. The problem is that when you use 3.0.0 doctor, it resizes partitions back to their original size. resizing CM partitions is safe, CWM restore, etc... isn't partition size specific. resizing the media partition that's the SDCARD, common between webOS and CM, doesn't do anything either. but all the other webOS partitions seem to be picky about size when webOS Doctoring. but i'm pretty sure you could upsize a partition after you webOS doctor and it'd be just fine and webOS wouldn't throw a fit or anything. i think the main developers just won't do it because it'll cause a headache since a lot of people trying to install CM/android with webOS don't really know what we're doing until we've done it. lmao.

the only reason I even bothered with resizing CM partitions in the first place is because of the SDCARD issue that occurs when you've moved too many apps onto your SDCARD. it starts remounting at random. then it doesn't mount at all once you reached the high limit which a lot of folks have said 30/50 not sure which is it. But i ran into this issue, and i was like WTH. You have a 32GB SDCARD why can't you just have a 5-8GB /cm-data partition so you can just simply not need to move any apps to SD and avoid the whole friggen problem. it's not like there's actually "internal" storage. it's all just partitions on the same physical SD anyways. so I started playing with file system. and came up with this. 8GB seemed to be too much for the /cm-data for me cause i still had way too much space free after I installed all my apps and games. 5GB seems to be the perfect number for me. Allows for all apps to be installed and still have space for temp web storage/cache on the /cm-data partition.

Originally Posted by qwerty007

i think /boot is a webOS partition and not a CM partition. i haven't tried it, but increasing the size of the partitions shouldn't kill webOS. The problem is that when you use 3.0.0 doctor, it resizes partitions back to their original size. resizing CM partitions is safe, CWM restore, etc... isn't partition size specific. resizing the media partition that's the SDCARD, common between webOS and CM, doesn't do anything either. but all the other webOS partitions seem to be picky about size when webOS Doctoring. but i'm pretty sure you could upsize a partition after you webOS doctor and it'd be just fine and webOS wouldn't throw a fit or anything. i think the main developers just won't do it because it'll cause a headache since a lot of people trying to install CM/android with webOS don't really know what we're doing until we've done it. lmao.

the only reason I even bothered with resizing CM partitions in the first place is because of the SDCARD issue that occurs when you've moved too many apps onto your SDCARD. it starts remounting at random. then it doesn't mount at all once you reached the high limit which a lot of folks have said 30/50 not sure which is it. But i ran into this issue, and i was like WTH. You have a 32GB SDCARD why can't you just have a 5-8GB /cm-data partition so you can just simply not need to move any apps to SD and avoid the whole friggen problem. it's not like there's actually "internal" storage. it's all just partitions on the same physical SD anyways. so I started playing with file system. and came up with this. 8GB seemed to be too much for the /cm-data for me cause i still had way too much space free after I installed all my apps and games. 5GB seems to be the perfect number for me. Allows for all apps to be installed and still have space for temp web storage/cache on the /cm-data partition.

Cheers for even more fine detail! I might venture into this if the new ROMs get any bigger. currently I'm just deleting unnecessary apps and have enough free space.

Sent from my Desire HD using XDA App

Hey,

I followed all the steps and everything went fine. I have my 5Gb for internal memory but I've just noticed that under Android the external Sdcard has about 21-22Gb. It's Ok but when I plug it,my computer only show me about 13-14Gb

Has anyone encountered same problem ?

Thanks

Thanx for this will give it a go when I'm a bit more sober ....


Sent from my Touchpad using xda premium