Database Users

partition sd card?

Hi all, I've noticed lately that most of the new roms coming out require you to partition your sd card. a couple of questions;
Why?
is it perminent?
wich partition to add new files too?
can i still use stock sd card?
how big to make partition?
Thanks in advance

dca1970 said:
Hi all, I've noticed lately that most of the new roms coming out require you to partition your sd card. a couple of questions;
Why?
is it perminent?
wich partition to add new files too?
can i still use stock sd card?
how big to make partition?
Thanks in advance
Click to expand...
Click to collapse
Memory size on the phone is not adequate to handle the size of certain ROMs.
No its not permanent
Ext3 for apps
Yes
As big as you want, 2gigs is what's recommended and 32 mb swap

phatmanxxl said:
Memory size on the phone is not adequate to handle the size of certain ROMs.
No its not permanent
Ext3 for apps
Yes
As big as you want, 2gigs is what's recommended and 32 mb swap
Click to expand...
Click to collapse
Thanks! .

Upgrading from ext2-ext3
On a side note, I have been attempting to partition my SDcard with the 2G on my 16G C6 card. When I use AR1.8 everything goes quickly, but it will not upgrade from ext2-ext3 and says to use adb to do this (adb does not see the partition)...partition seems to be made when checking the card. On AR2.3 the partitioning goes on forever and have to do a battery pull to get it to stop. When I check the size with this version it also seems to have done the partition even with the endless process stated earlier. It however gives me the message 'opps, something went wrong' when trying to upgrade from ext2-3.
When checking from either method in TB, it shows an ap2sd partition of around 400mb and have yet to actually upgrade to ext3 from either recovery version.
Any ideas?

Use RA recovery to partition, it makes it simple.

What ROMs require this?
I guess I've been in the AOSP world for too long...

Just the virus gingersense and the virus kingdom that I know of. The virus kindom does not require it but you wont be left if much room for apps.

phatmanxxl said:
Just the virus gingersense and the virus kingdom that I know of. The virus kindom does not require it but you wont be left if much room for apps.
Click to expand...
Click to collapse
Why not just http://forum.xda-developers.com/showthread.php?t=855424 ?
Better performance on NAND than SD-EXT.

phatmanxxl said:
Use RA recovery to partition, it makes it simple.
Click to expand...
Click to collapse
Sorry, AR was my intention of RA. Have used both the initial version 1.8 (my first anyway) and 2.3 with no success.
Have been attempting to do it within ADB and keep getting this message when attempting to make the ext2 partition:
Input/Output error during write on /dev/block/mmcblk0
This is the process I'm using:
within adb shell
# parted /dev/block/mmcblk0
(parted) mkpartfs primary fat32 0 13991
(parted) mkpartfs primary ext2 13991 16039
this is where I get the error mentioned above and can not continue to the swap.
(parted) mkpartfs primary linux-swap 16039 16071
HOWEVER....
If I use mkpart primary ext2 13991 16039 it takes, but does not show that it is an ext2 in the files system under the partition information.
Does this even make sense..lol
EDIT:
Never mind..erased my edit until I really screw up my card...now it won't mount...back to the drawing board
Gave up after reading about Transcend cards and just partitioned to the single 16G. Going to get a different card/mfg and give it a go. At least I learned a bit more about ADB today...so not a total loss.

OK..after looking through many options, may have my issue as to why RA won't perform the partition and I can't do it through ADB.....MY CARD. Apparantly there have been issues with Transcend and making an ext partition. Guess it's time to go C10 and get a new one.
Anyway...found this thread and thought it might help?
http://forum.xda-developers.com/showthread.php?t=534714

Got a new C10 card today from a different mfg and that fixed the problem!

I use gpart on ny ubuntu OS. It is NVIDIA to keep a Linux OS around guys. I can do the wholebpartitioning without erasing any files or data. soo I'm good to go. Also its fast as well.
Sent from my PC36100 using XDA App

[Q] Internal Memory Low Space on ICS 2.4.27-HWA

I have installed MIUI.us-Leo-2.4.27-HWA.ZIP in to my HTC HD2. Everything is working fine except Camera and phones internal memory is very low, only 25MB resulting cannot update any existing applications.
My phones total internal memory memory is 151MB and available is only 25MB.
SD card total space is 15GB and available is 9GB which is fine.
Total downloaded applications are 26 only, so it is not that I have too many application downloaded.
I moved most of the downloaded and other applications to SD card by using titanium backup. Few could not be moved for unknown reason as it does not give me option to move.
Can anyone please help me to increase my internal memory to at least at 70 or 60MB please.
Would appreciate your help.
Ronju Khan.
Dhaka, Bangladesh

i have used a few MIUI roms & did not have that problem
what is the data.img that you used?
are you using NAND rom? in that case what was the size of the partition you used, did you follow the recommended size?

Internal Space Low
mengfei said:
i have used a few MIUI roms & did not have that problem
what is the data.img that you used?
are you using NAND rom? in that case what was the size of the partition you used, did you follow the recommended size?
Click to expand...
Click to collapse
Yes, it is NAND ROM. The recommended partition was above 200mb and I used 250mb, so it was okay.
All I need to increase my internal space at least to 60 or 70mb so that application update can be done.
Many thanks

The ROM suggested 200, but you installed 250. You just lost 50 worth o internal storage.
You'll need to install an A2SD script, in order to be able to use your sd card as an internal storage. (of course, after making an ext2 partition )

Marvlesz said:
The ROM suggested 200, but you installed 250. You just lost 50 worth o internal storage.
You'll need to install an A2SD script, in order to be able to use your sd card as an internal storage. (of course, after making an ext2 partition )
Click to expand...
Click to collapse
Why ext2 he will face a lot of problems use ext4 for best speed
Sent from my HTC HD2 using XDA

Reply Internal Space is Low
Thealshear said:
Why ext2 he will face a lot of problems use ext4 for best speed
Sent from my HTC HD2 using XDA
Click to expand...
Click to collapse
I have A2SDGUI installed but don't know how to use this to increase internal space .Please advise me in details how do I perform ext4. I will be very much grateful to you. Will wait for your response.
Many thanks.

Reply to Marvlesz
Marvlesz said:
The ROM suggested 200, but you installed 250. You just lost 50 worth o internal storage.
You'll need to install an A2SD script, in order to be able to use your sd card as an internal storage. (of course, after making an ext2 partition )
Click to expand...
Click to collapse
Marvlesz, I looked for 200MB partition but could not find anywhere. That's why I installed 250MB. There are only 3 options they gave which is 150MB, 250MB & 400MB. Please suggest me in details how I would be able to do ext2 or ext4 using A2SD

[Q] Memory Problem with [JB] [4.1.2] Pixeldroid Jelly Bean V2.4[AOKP]

Hey there,
first, thank for this really great ROM - [17/02/2013] [JB] [4.1.2] Pixeldroid Jelly Bean V2.4[AOKP] [BeatsAudio] [720p]
its running a few weeks absolutly fine, fast.
but today, i needed to reboot the phone and then i got the welcome screen (that one after a clean install).
the problem is the memory, i followed exactly the installation steps but it seems, it uses the internal memory for apps (~55 MB are full, nothing left)
the actual memory status is shown in the attachment.
seems, the ext4 partition on the 8 GB SD isn't used, but why ?
and - how can i free the internal, no chance to install any app
TheRealLuke

therealluke said:
Hey there,
first, thank for this really great ROM - [17/02/2013] [JB] [4.1.2] Pixeldroid Jelly Bean V2.4[AOKP] [BeatsAudio] [720p]
its running a few weeks absolutly fine, fast.
but today, i needed to reboot the phone and then i got the welcome screen (that one after a clean install).
the problem is the memory, i followed exactly the installation steps but it seems, it uses the internal memory for apps (~55 MB are full, nothing left)
the actual memory status is shown in the attachment.
seems, the ext4 partition on the 8 GB SD isn't used, but why ?
and - how can i free the internal, no chance to install any app
Click to expand...
Click to collapse
You need to install something to switch data usage to the sd card. There are many scripts & apps to accomplish this but I couldn't tell you which would be best for your rom.
Alternately, you can ask whoever published the rom to add a DataOnExt install option.
---
Be careful about reading health books, you may die of a misprint...

NYLimited said:
You need to install something to switch data usage to the sd card. There are many scripts & apps to accomplish this but I couldn't tell you which would be best for your rom.
Alternately, you can ask whoever published the rom to add a DataOnExt install option.
The DataOnExt comes with the ROM and i activated it within the install routins.
At this Point i can't install any app.
any chance to clear something with QtADB from the internal mem to get a a2SD or smth. else working ?
Click to expand...
Click to collapse

therealluke said:
NYLimited said:
You need to install something to switch data usage to the sd card. There are many scripts & apps to accomplish this but I couldn't tell you which would be best for your rom.
Alternately, you can ask whoever published the rom to add a DataOnExt install option.
Click to expand...
Click to collapse
The DataOnExt comes with the ROM and i activated it within the install routins.
At this Point i can't install any app.
any chance to clear something with QtADB from the internal mem to get a a2SD or smth. else working ?
Click to expand...
Click to collapse
How big is your ext partition?
EDIT: I hate it when people can't quote properly ..

Marvlesz said:
How big is your ext partition?
Click to expand...
Click to collapse
around 1,5 GB ext4 but it seems like android uses the 5 GB fat32 part

therealluke said:
around 1,5 GB ext4 but it seems like android uses the 5 GB fat32 part
Click to expand...
Click to collapse
I don't understand the language in the picture so I can't make anything out of it, but if you really have a 1.5gb ext partition and you chose dataonext during installation you shouldn't have any problems.

Marvlesz said:
I don't understand the language in the picture so I can't make anything out of it, but if you really have a 1.5gb ext partition and you chose dataonext during installation you shouldn't have any problems.
Click to expand...
Click to collapse
I Think i will do a full reinstall and check again the option with dataonext, and restore my saved data,
thanks for your help

therealluke said:
around 1,5 GB ext4 but it seems like android uses the 5 GB fat32 part
View attachment 1766202
Click to expand...
Click to collapse
Marvlesz is right - it should work if you have DataOnExt. The picture shows "Available" space if I am not mistaken. What is your "Internal" space indicate? Look in Titanium Backup if you can.

NYLimited said:
Marvlesz is right - it should work if you have DataOnExt. The picture shows "Available" space if I am not mistaken. What is your "Internal" space indicate? Look in Titanium Backup if you can.
Click to expand...
Click to collapse
Above, the "internal" Available Space is 0,0 GB
56,83 MB used from apps
i used the configuration in the rom description:
★ install Recovery with 300 MB System and 5 MB Cache
★ 2 GB EXT4 cluster default / SWAP 256 MB / the rest FAT32 cluster default
the "USB Speicher" (5,31 GB at all) ist the fat32 part on the SD Card
QtADB says :
/data: nothing shown
/system : 292,97 MB at all with 51,41 MB free
/sdcard : 5,16 GB at all with 4,89 free
/ext: grey (empty)

therealluke said:
Above, the "internal" Available Space is 0,0 GB
56,83 MB used from apps
i used the configuration in the rom description:
★ install Recovery with 300 MB System and 5 MB Cache
★ 2 GB EXT4 cluster default / SWAP 256 MB / the rest FAT32 cluster default
the "USB Speicher" (5,31 GB at all) ist the fat32 part on the SD Card
Click to expand...
Click to collapse
Something is definitely very wrong but I cannot yet see what or where. Marvlesz, any ideas yet?
Your memory display should look something like this one - this is with 3 GB of ext4 partition:
You might want to take a look at this post about formatting. You may spot something that you did differently which could help.
Not knowing your ROM I can only guess what it is expecting.
Your ext4 partition is the second one on the card, marked as primary, yes?
What does DF report?

The data part. was corrupted end not write or readable, after a recovery reinstall i got "internal" size of 1,65 GB with 1,21 GB free
Thanks for your help !! you helped me to indicate the lost data partition

[Q] Resizing /system and /cache to gain space?

Hello everyone and thank you for having me on your wonderful forum. I have learned so much in such a short time by reading everything I could whether I was intending to use it or not.
I got my 16gb Nexus on Monday and immediately prepped it for ROMs, settling on CM10.1 RC2, Prior to that I had an Optimus V running CM7. On my Optimus, after flashing CM7 for the long haul I was able to move all excess /system space back into /data using terminal emulator and the fdisk command, but I followed a guide of some sort that is long lost now.
Everything is fantastic so far except one thing, there seems to be quite a lot of space reserved in the /system and /cache partitions, and I am not sure if I am able to re-partition this space back to /data or how exactly to do this.
right now /system is reading at 395.8 / 827.8 MB used, and /cache is at 68.4 / 551.7 MB. I would like to repartition 200 MB away from /system and 300-400 MB away from /cache, and put it back into /data. This will leave me some space to integrate or convert a few apps to system apps, and enough cache space to be safe (why does it need 550 MB to begin with?) and give back another half gig of storage that I paid so much to have.
I have three issues with this, one being that I can find almost no information on this topic directly mentioning the NExus 4, and any relatable information from other devices talking about device specific toolkits to do the job.
The only thread I found on XDA about this is below, and it only gave me a vague "this is not possible"
http://forum.xda-developers.com/showthread.php?t=2248400
The second issue is I do not recall the command switches/flags that go with the fdisk command, only that I had to use some things to set file permissions or remount the partition or some such (I know, i'm a noob, forgive me).
Lastly, I am rather confused by the multiple partitions of /data and /storage/emulated all showing a partition size of 13231.8 MB. Obviously they are all the same physical space, but I am afraid to mess with the partitions and break what I assume are a ton of symlinks that trick apps into believing there is an external SD card in play. Can any of you shed some light on this for me?

I3ig Al said:
Hello everyone and thank you for having me on your wonderful forum. I have learned so much in such a short time by reading everything I could whether I was intending to use it or not.
I got my 16gb Nexus on Monday and immediately prepped it for ROMs, settling on CM10.1 RC2, Prior to that I had an Optimus V running CM7. On my Optimus, after flashing CM7 for the long haul I was able to move all excess /system space back into /data using terminal emulator and the fdisk command, but I followed a guide of some sort that is long lost now.
Everything is fantastic so far except one thing, there seems to be quite a lot of space reserved in the /system and /cache partitions, and I am not sure if I am able to re-partition this space back to /data or how exactly to do this.
right now /system is reading at 395.8 / 827.8 MB used, and /cache is at 68.4 / 551.7 MB. I would like to repartition 200 MB away from /system and 300-400 MB away from /cache, and put it back into /data. This will leave me some space to integrate or convert a few apps to system apps, and enough cache space to be safe (why does it need 550 MB to begin with?) and give back another half gig of storage that I paid so much to have.
I have three issues with this, one being that I can find almost no information on this topic directly mentioning the NExus 4, and any relatable information from other devices talking about device specific toolkits to do the job.
The only thread I found on XDA about this is below, and it only gave me a vague "this is not possible"
http://forum.xda-developers.com/showthread.php?t=2248400
The second issue is I do not recall the command switches/flags that go with the fdisk command, only that I had to use some things to set file permissions or remount the partition or some such (I know, i'm a noob, forgive me).
Lastly, I am rather confused by the multiple partitions of /data and /storage/emulated all showing a partition size of 13231.8 MB. Obviously they are all the same physical space, but I am afraid to mess with the partitions and break what I assume are a ton of symlinks that trick apps into believing there is an external SD card in play. Can any of you shed some light on this for me?
Click to expand...
Click to collapse
nexus4 doesn´t have a fix size for partitions, you can use the whole memory for everything... no need to re-partition anything

75markus said:
nexus4 doesn´t have a fix size for partitions, you can use the whole memory for everything... no need to re-partition anything
Click to expand...
Click to collapse
I'm not sure if you are misunderstanding or not reading my whole post, or if I am not understanding you or the situation I am posting about, so please don't take offense to this reply.
It appears to me that the /system partition is reserving 827 MB space for the ROM, and CM10.1 is only using 400 MB of it
It also appears that 552 MB is reserved for the /cache partition, and only 70 MB is being currently used.
This is ~900 MB of storage space that is reserved and unused. I would like to know if it is possible to reallocate ~500-600 MB of this back into the /data partition for user space.
Please explain to me how this space is part of the whole memory that can be used for anything.
After posting I have thought some more about it and decided to NOT mess with the partition sizes, mainly because I do not know what effect it would have if I were to flash another ROM in the future, which is almost a given when Key Lime Pie is released. However I would still like to understand what I have asked about in case I do want to do this in the future, and also just for the sake of expanding my knowledge.

I like this. The only "issue" is that if more space were ever to be reallocated to /system or /cache, it'd require wiping /data obviously. Small price to pay. 500MB isn't too small a chunk for 8GB users.

75markus said:
nexus4 doesn´t have a fix size for partitions, you can use the whole memory for everything... no need to re-partition anything
Click to expand...
Click to collapse
Actually it does. System data cache and boot, plus like 30 other ones, same as any other phone with no micro SD card
Sent from my Nexus 7 @1.60 GHz on Stock 4.2.2

I3ig Al said:
I'm not sure if you are misunderstanding or not reading my whole post, or if I am not understanding you or the situation I am posting about, so please don't take offense to this reply.
It appears to me that the /system partition is reserving 827 MB space for the ROM, and CM10.1 is only using 400 MB of it
It also appears that 552 MB is reserved for the /cache partition, and only 70 MB is being currently used.
This is ~900 MB of storage space that is reserved and unused. I would like to know if it is possible to reallocate ~500-600 MB of this back into the /data partition for user space.
Please explain to me how this space is part of the whole memory that can be used for anything.
After posting I have thought some more about it and decided to NOT mess with the partition sizes, mainly because I do not know what effect it would have if I were to flash another ROM in the future, which is almost a given when Key Lime Pie is released. However I would still like to understand what I have asked about in case I do want to do this in the future, and also just for the sake of expanding my knowledge.
Click to expand...
Click to collapse
i think N4 uses FUSE (Filesystem in Userspace) file system
noobdeagle said:
isnt this what they were saying was the reason for no SD card and use of MTP ?; basically if i recall correctly the nexus devices do not truly assign partitions instead there is a storage 'pool' that anything can use dynamically.
so i guess there is no partitions its just all 1 volume.
source: http://www.androidcentral.com/why-nexus-devices-have-no-sd-card
Click to expand...
Click to collapse

That is for the sdcard.
The other partitions such as /system still have fixed amounts of space allocated
Sent from my Nexus 4 using xda app-developers app

Data Partition Size Changer CWM ZIPS

Here's my contribution,
A Friend has a TP that I 'keep upto date' for him, He wanted to get to 4.3, so I've done that, however resizing partitions in HP world just seems a pain. So here's some flashable ZIP's to do the hard lifting for you.
4 versions I'm uploading (shout if you want a different sizing).
First add's 8gb to the data size (ontop of what you have already, just look in the storage system setting option for that info) the second adds 12gb, then 16gb and finally 24gb.
UPDATE - As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
Just pick the one that matches what you want (obviously don't try the 16 / 24 on the 16gb device! and make sure you have enough 'clean' space before you start)
What I recommend doing is moving everything you can off the old 'SDCard' partition, using Recovery in the tether mode (int the storage menu), once you have removed as much as you can (remember the 'hidden' .???? folders and don't go deleting anything that's WebOs based!)
Then just flash the ZIP you think meets your requirements.
UPDATE - Uploaded the revert scripts, I've not tested them but they should be fine.
Hope that helps.

Two way trip
Edit: To revert these changes users can do a full uninstall using the ACMEUinstaller2. This will remove all partition changes and files added when installing Android:
How to Uninstall Android or CyanogenMod on the HP TouchPad (All versions)
In addition Gradular The Ape have created flashable zips that can reverse the partition changes the previous Android state . Find these in the above post and in Gradular's second post in his thread here: How to guide for changing your system, data, and cache partition sizes to whatever you want.

RolandDeschain79 said:
This is great thank you! A few people have run into problems when moving around data with the tailor, this should totally get around that:good:
I've got to ask, would it be possible to create a reverse of these files? The problem with this setup is that it's a one way trip. If users don't like, or have problems, they'd have to go through the pain of using tailor to rearrange their space again. Being able to add and remove the space with a zip would be a lot more convenient and give users a round trip pass for changing the partition sizes.
Cheers:highfive:
Click to expand...
Click to collapse
Shouldn't be an issue, I've obviously not got a TP to play with here, so can't test, and I don't like to put stuff out there that I've not at least done a once over of.
I'll have a look at it tomorrow when I've got access to the device and post a few ZIP's. I'll just do an 'inverse' of the four I've already done so you can undo a change.

the_ape said:
Here's my contribution,
A Friend has a TP that I 'keep upto date' for him, He wanted to get to 4.3, so I've done that, however resizing partitions in HP world just seems a pain. So here's some flashable ZIP's to do the hard lifting for you.
4 versions I'm uploading (shout if you want a different sizing).
First add's 8gb to the data size (ontop of what you have already, just look in the storage system setting option for that info) the second adds 12gb, then 16gb and finally 24gb.
Just pick the one that matches what you want (obviously don't try the 16 / 24 on the 16gb device! and make sure you have enough 'clean' space before you start)
What I recommend doing is moving everything you can off the old 'SDCard' partition, using Recovery in the tether mode (int the storage menu), once you have removed as much as you can (remember the 'hidden' .???? folders and don't go deleting anything that's WebOs based!)
Then just flash the ZIP you think meets your requirements.
Hope that helps.
Click to expand...
Click to collapse
the_ape said:
Shouldn't be an issue, I've obviously not got a TP to play with here, so can't test, and I don't like to put stuff out there that I've not at least done a once over of.
I'll have a look at it tomorrow when I've got access to the device and post a few ZIP's. I'll just do an 'inverse' of the four I've already done so you can undo a change.
Click to expand...
Click to collapse
Great... Guess it would reverse to the ACMEInstaller3 default partitions... If u'r flash resizes the (system) to 512 MiB... I would leave that one alone instead of making it go back to 400 MiB...
What is the breakdown for a 32GB TP using the data_plus_24576mb-signed... Is this about right ???
USB (media) - Depends what size TouchPad u have... (Decreases 112 MiB to be added to the Android (system) partition & Decreases about 23076 to be added to the 1.5 GiB already in the (data) partition)
Android (system) - 512 MiB (Increase of 112 MiB from ACMEInstaller3 400 MiB size OR do u leave it at the 400 MiB size ??? OR does it assume we used the update-cm-tenderloin-system_resize_512-0.4 already ???)
Android (cache) - 200 MiB (Stays at ACMEInstaller3 size)
Android (data) - 24576 MiB​
Plan to so some testing how ACMEInstaller3 would handle an update-data_plus_24576mb-signed thru the CMInstall when reconfiguring or coming from a stock TP (before Android & any Recovery is install on the TP)... Any thoughts on this ??? Doesn't work from ACMEInstaller3... Although I did see it run... It didn't change the size of the default partitions that ACMEInstaller3 creates...
Update: Was able to play with the 24576 file... This was the break down of the partitions now..
USB (media) - 1.539 GiB
Android (system) - 400 MiB
Android (cache) - 200 MiB
Android (data) - 25.5 GiB
Unused Space - 16 MiB
So we will need to increase the (system) partition separate using the update-cm-tenderloin-system_resize_512-0.4 file if u'r still @ 400 MiB...

Y314K said:
Great... Guess it would reverse to the ACMEInstaller3 default partitions... If u'r flash resizes the (system) to 512 MiB... I would leave that one alone instead of making it go back to 400 MiB...
What is the breakdown for a 32GB TP using the data_plus_24576mb-signed... Is this about right ???
USB (media) - Depends what size TouchPad u have... (Decreases 112 MiB to be added to the Android (system) partition & Decreases about 23076 to be added to the 1.5 GiB already in the (data) partition)
Android (system) - 512 MiB (Increase of 112 MiB from ACMEInstaller3 400 MiB size OR do u leave it at the 400 MiB size ??? OR does it assume we used the update-cm-tenderloin-system_resize_512-0.4 already ???)
Android (cache) - 200 MiB (Stays at ACMEInstaller3 size)
Android (data) - 24576 MiB​
Plan to so some testing how ACMEInstaller3 would handle an update-data_plus_24576mb-signed thru the CMInstall when reconfiguring or coming from a stock TP (before Android & any Recovery is install on the TP)... Any thoughts on this ??? Doesn't work from ACMEInstaller3... Although I did see it run... It didn't change the size of the default partitions that ACMEInstaller3 creates...
Update: Was able to play with the 24576 file... This was the break down of the partitions now..
USB (media) - 1.539 GiB
Android (system) - 400 MiB
Android (cache) - 200 MiB
Android (data) - 25.5 GiB
Unused Space - 16 MiB
So we will need to increase the (system) partition separate using the update-cm-tenderloin-system_resize_512-0.4 file if u'r still @ 400 MiB...
Click to expand...
Click to collapse
I've only tested it using cwm 6, and no, my zips dont touch the system size. Forgive my ignorance, but what is ACMEInstaller?

the_ape said:
I've only tested it using cwm 6, and no, my zips dont touch the system size. Forgive my ignorance, but what is ACMEInstaller?
Click to expand...
Click to collapse
Using CWM6_tenderloin-20121215 here...
We've all used ACMEInstaller @ the initial setup of Android... It creates the Android partitions & it installs moboot, recovery & rom & gapps... It was the double penguin screen that installed them.. Most of u have not used it since then... You just use the recovery to change things... I've been reconfiguring my TP lately so I've been using it a few times.... More of the exception & not the norm...
U'r flash files only increase size right... It doesn't format anything... Can u do a version of the 24576 file that also changes the (system) partition to 512 MiB... I can test it if u like.. Thanks.. :good:

Y314K said:
Using CWM6_tenderloin-20121215 here...
We've all used ACMEInstaller @ the initial setup of Android... It creates the Android partitions & it installs moboot, recovery & rom & gapps... It was the double penguin screen that installed them.. Most of u have not used it since then... You just use the recovery to change things... I've been reconfiguring my TP lately so I've been using it a few times.... More of the exception & not the norm...
U'r flash files only increase size right... It doesn't format anything... Can u do a version of the 24576 file that also changes the (system) partition to 512 MiB... I can test it if u like.. Thanks.. :good:
Click to expand...
Click to collapse
I'll put some that do system together in the morning, I didn't bother as it was already done that way on my friends. And no, it doesn't delete anything, just shunts partitions around.
Oh and yes I do remember ACME now, back in he early days was all done via scripts and terminal, so never played with it as such, think used it once for cm9. But doubt my scripts will run under that as they make use of a lot more than just pure recovery, hats why I recommend at least cwm6

the_ape said:
I'll put some that do system together in the morning, I didn't bother as it was already done that way on my friends. And no, it doesn't delete anything, just shunts partitions around.
Click to expand...
Click to collapse
Great... Thanks.. Should help for when some CM9 or CM10 folks upgrade to the 4.3 options... Or for those still with just 400 MiB (system)... I myself feel comfortable with Tailor... Which lets u squeeze out every bit of space out of our TP's...

Y314K said:
Great... Thanks.. Should help for when some CM9 or CM10 folks upgrade to the 4.3 options... Or for those still with just 400 MiB (system)... I myself feel comfortable with Tailor... Which lets u squeeze out every bit of space out of our TP's...
Click to expand...
Click to collapse
UPDATE - As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
See the OP

the_ape said:
UPDATE - As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
See the OP
Click to expand...
Click to collapse
Thanks... Gonna try the two largest one's right now... I am guessing if we ever need a special size... We can just manually change the data_plus_24576mb-signed/update/update_script.sh for the data & data_plus_24576mb-signed/update/system_script.sh for the system...
Code:
CHANGE_SIZE=24576
EXTPART="cm-data"
Code:
CHANGE_SIZE=512
EXTPART="cm-system"

Looking good!
the_ape said:
UPDATE - As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
See the OP
Click to expand...
Click to collapse
Thank you for these very helpful packages, great work! This will help a lot of people change their partitions easily. I will test them out once you also post the reverse files so I can try the round trip experience cheers:good:

the_ape said:
UPDATE - As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
See the OP
Click to expand...
Click to collapse
Think I found something... Or maybe not...
I had already used the data_plus_24576mb-signed yesterday...
I tried to use the sys_512mb_data_plus_24576mb-signed patch just to resize the (system) partition... I thought it would recognize that the (data) partition was already 24576 MiB or that the (media) partition didn't have 24576 to give again...
Got the following:
DO NOT DO ANYTHING ELSE!
REBOOT NOW!!!
Resizing the Data Partition ...
=== Reallocating 24576MB from media to cm-data
Preparing tools...
Checking media...
media:1464=>23112 cm-data:26112=>50688
media_fs tot=1575 sz=628 free=947
cannot resize media
>>FAILED<<
Lets tidy up ...
All Done ...
Click the thanks button
if you found this useful
The_Ape
Install from sdcard complete.
Click to expand...
Click to collapse
Guess the FAIL part of it is the safety check...
Went back to WebOS... And Tailor is telling me my new partition break down is as follow...
USB (media) - 1.539 GiB => 1.43 GiB
Android (system) - 400 MiB => 512 MiB
Android (cache) - 200 MiB => 200 MiB
Android (data) - 25.5 GiB => 25.5 GiB (This includes the 24576MB + 1.5GiB that ACMEInstaller3 created the (data) partition with)
Unused Space - 16 MiB => 16 MiB
So everything worked fine... Wonder if the FAIL message can be specific enough when it's due to not having enough space in (media) to move over or if it's due to (data) already being the requested size... The part that said cm-data:26112=>50688 made me think it was forcing the mod... Also the media:1464=>23112 looks weird to me... Like it's shifting space from (data) to (system) to send back to (data)..

Y314K said:
Thanks... Gonna try the two largest one's right now... I am guessing if we ever need a special size... We can just manually change the data_plus_24576mb-signed/update/update_script.sh for the data & data_plus_24576mb-signed/update/system_script.sh for the system...
Code:
CHANGE_SIZE=24576
EXTPART="cm-data"
Code:
CHANGE_SIZE=512
EXTPART="cm-system"
Click to expand...
Click to collapse
Yup, that's the one, you can change the other partitions that way too if you wanted too, but the sizes here should be pretty close for most people.
However if your a bit more confident with what your doing then help yourself, after all, your device, you should know best what sizes are right for you.

Y314K said:
Think I found something... Or maybe not...
I had already used the data_plus_24576mb-signed yesterday...
I tried to use the sys_512mb_data_plus_24576mb-signed patch just to resize the (system) partition... I thought it would recognize that the (data) partition was already 24576 MiB or that the (media) partition didn't have 24576 to give again...
Got the following:
Guess the FAIL part of it is the safety check...
Went back to WebOS... And Tailor is telling me my new partition break down is as follow...
USB (media) - 1.539 GiB => 1.43 GiB
Android (system) - 400 MiB => 512 MiB
Android (cache) - 200 MiB => 200 MiB
Android (data) - 25.5 GiB => 25.5 GiB (This includes the 24576MB + 1.5GiB that ACMEInstaller3 created the (data) partition with)
Unused Space - 16 MiB => 16 MiB
So everything worked fine... Wonder if the FAIL message can be specific enough when it's due to not having enough space in (media) to move over or if it's due to (data) already being the requested size... The part that said cm-data:26112=>50688 made me think it was forcing the mod... Also the media:1464=>23112 looks weird to me... Like it's shifting space from (data) to (system) to send back to (data)..
Click to expand...
Click to collapse
There is very little error checking/reporting built in, it 'shouldnt' cause any issues if your sizes are not able to be changed, but the output has not been friendlied up, after all I knocked it up so I didnt have to use WebOS, it does however have a quick look to see if it's possible to do the command it's meant to be doing before it tries (as you can see)

RolandDeschain79 said:
Thank you for these very helpful packages, great work! This will help a lot of people change their partitions easily. I will test them out once you also post the reverse files so I can try the round trip experience cheers:good:
Click to expand...
Click to collapse
Damn! I forgot all about the revert ones, could anyone let me know what the 'original standard' partition sizes are for the 32gb and the 16gb and I'll knock a zip for each together.

the_ape said:
Damn! I forgot all about the revert ones, could anyone let me know what the 'original standard' partition sizes are for the 32gb and the 16gb and I'll knock a zip for each together.
Click to expand...
Click to collapse
Neve mind about WebOS partition sizes since most won't want to have to rerun ACMEInstaller3..
My 32GB after a reconfig & without any Android part install shows...
USB (media): 27.663 MiB (Partition Size 28296 MiB)
Unused Space: 8 MiB
My 32GB after a reconfig & first Android Installation shows..
USB (media): 25.539 GiB (Partition Size: 26152 MiB)
Android (system): 400 MiB
Android (cache): 200 MiB
Android (data): 1.5 GiB
Unused Space: 16 MiB
U would want a reverse flash that would only shift the 24576 MB back from (data) to (media)... Keeping the (system) @ 512 MB seems like a must thing to do now.. RolandDeschain79 probably has a better idea of what would be best for most...
Not sure about 16GB models...

That's the info I would need. What would be best for the 16GB models?

can we resize the partition from windows ?

HashTagHell said:
That's the info I would need. What would be best for the 16GB models?
Click to expand...
Click to collapse
:good: I want to try it also

the_ape said:
As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
Click to expand...
Click to collapse
Thansk for your work. Now, pardon my newbines on the touchpad, but here it goes.
I have my TP with CM7, very old and unstable.
1) Can I use your ZIPs to repartition before moving to CM9 or CM10?
2) Can I just boot to recovery and flash this no matter what I have today?
3) I have a 32GB TP. If I use for example, sys_512mb_data_plus_16384mb-signed.zip I would have used about half meg for system, and 16GB for data, what happens with the remaining 15.5 GB?
Thanks!