Is there a way, say at the time of flashing the ROM (I flashed back to a stock i9000) or from Recovery console, that the /system mount can be be repartitioned with more space?
Reason being that I need to move a new font in to replace the Fallback font that google includes since all the Chinese characters in it are simplified (annoying if you read mostly Japanese). Problem is my font is like 9mb and theres only 5mb free on system.
Thanks
i was gonna ask about this one, it would be awesome if some space from SD card can be partitioned to the internal memory.
Ok, so I found a way around reparitioning although I think I real need to repartition now or I might run into trougble.
I rolled an update.zip containing the font I wanted to swap in and simply replaced the old one. It took, but now my /system has 0.0mb free. So now I'm thinking I may have to roll my own system.img and reflash my droid with the new font already included in; assuming it is Odin3 that predetermines the partition size and sizes accordingly. This is ROM development question I know, but Where/How are the partition sizes for /system and /data determined? Is there a config file in each flash IMG that states the size it should be or is it like I already mentioned, does Odin3 determine it?
Thanks
Hello TeamEOS and modders!
thank you very much for your great work in the Xoom MOD! Its just amazing and i'm using it for several months now.
Recently I wanted to install an Android Port of TexLive (see code.google.com texlive-for-android/) on my Xoom. the problem occurs that a lot of TeX Binaries have to be copied to the /system/bin folder. Flashing your ROM leaves about 1MB free space on /system, even deleting unnecessary apps and bootanimation frees not enough space. The package uses about 80MB. The only solution would be to resize the /system partition, something I read is not possible.
Can I at least copy the files in the ROM image before flashing and would this allow the /system partition to resize automatically?
Thanks in advance!
I want my external sdcard to be ext2 (just want it for storing large files and a chroot). I was wondering if anyone has got this working. I've googled (and searched here) and it looks like most like split it up into multiple partitions and use another program to mount it. I have a stock jelly bean rom that has been rooted. I tried looking/messing with the vold.fstab but that doesn't work. Sadly android doesn't have a normal fstab file. *rolls eyse* I can mount it on the phone with CLI but android still complains and I want to automount it. I was curious if any one had any success or knowledge of editing the config/init files to do this.
Let me start with: I know that there have been many posts on this, but before you get mad, I was unable to find an answer to what I specifically want to do.
For reference: I am a software developer and sysadmin with a decent amount of Linux experience, but not a lot of android specific experience.
Now that the introduction is out of the way:
What I would like to do is completely remove the "USERDATA" partition (the "Internal SD card"), grow the "SYSTEM" partition to fill that space, and then mount my SD Card (external) as the SD Card that the system sees.
I'm currently on Cyanogenmod 10.1 but want to upgrade to 11 soon.
The reason I want to do this is because:
I have all if my apps that I can set to install to SD Card
Both "internal" partitions are full (only about 200MB is available for pictures/etc. and I can no longer update apps)
Camera (and pretty much everything else as well) stores to the Internal SD card by default
If the system partition was 1.1+1.4=2.5GB and all of my apps were "installed" to a real SD card, it would be a lot more comfortable.
So, here's what I am thinking *might* work (maybe not in the right order, though?):
Point the fstab entry for the internal SD card to the external SD card
I have the PIT file. I will delete the "USERDATA " and grow "SYSTEM" to fill the space
When I write it out in steps, it seems pretty simple...
My concerns:
Will a ROM update (to CM11) re-partition back to the old way (and, in the process, break a bunch of stuff)?
I don't ever plan to go back to stock android or change to another ROM (other than upgrades).
Thanks for reading this long post and for any insight you may be able to provide.
--mobrien118
It's a wonderful idea if it works.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Modifying partitions is a bit dangerous.
But I have to ask you why do you need another GB of /system storage?
There was a line you can put in the build.prop that flips your ext. SD with the internal one on cm10 I believe.
This'd interest me if I could get rid of usbdisk and sdcard0 merged.
It would need the phone to be repartitioned though, causing issues with the backups and ROMs.
You may even have to compile cm from source.
Its a lot of trouble
Sent from my SAMSUNG-SGH-T769 using Tapatalk
I just did so on S4 Mini with cm-11 Android 4.4.
First I was thinking of using symlinks and/or bind mounts to redirect to the the external sdcard, but that's a bit of a hassle because
1) Since 4.2: both emulated and external storage is mounted with a fuse layer on top not supporting symlinks
2) Since 4.4: no more global write access on external storage
So moving data was the simplest solution. Besides providing (much) more space my sdcard is also around 20% faster in sequential writes: 8.5 MB/s internal vs 10.5 MB/s external. Is it really 2014?
I haven't yet decided what to do with the original data partition, so for the moment I left it unused. Hence I haven't touched the internal partition table.
Quick summary
partition sdcard (gdisk)
I recommend using GPT, this lets you work with partition names rather than numbers. For the sake of still having an "official" external sdcard I made two partitions. Keep in mind that it's usually the first partition which gets automatically mounted as external sdcard. So I made the 2nd partition the new home for data. This partition however has to be manually specified in the ramdisks fstab which involves flashing the boot partition.
format the new partitions (mkfs.ext4)
copy the original /data directory tree to the new data partition
extract initrd from boot.img (abootimg)
extract files from initrd (gunzip & cpio)
replace the /data entry in fstab pointing at your new data partition
re-pack initrd and boot.img (gzip, cpio & abootimg)
flash boot.img onto the boot partition (dd)
If you use recovery, you also have to edit it's fstab (analog to boot.img mentioned above)
done
Alternatively has anyone tried an init.d script? I see those scripts get executed before the mounting of data & sdcard
Meanwhile the original userdata partition got replaced by 3 new partitions: system2, cache2 & userdata2 which are now used for a dual boot ROM.
I've only changed GPT, not PIT. ROMs and Recovery don't use PIT, so as long as Heimdall/Odin isn't involved it should not cause any issues.
Hey guys,
So after read all that, I am also vry interested in what the OP has suggested. I get that the pit doesn't need to be affected, but as the OP asked, when flashing a new rom or updating an existing, would the partition be reformatted back to the way android handles it, ie; back to the system and data seperate and the sdcard not being used as the internal partition?
I am no developer and only have minimal knowledge in linux and android programing, but I am a quick study and any guide to help me sort this would be greatly appreciated.
Also I am about to get a second S4 mini specifcally for doing things like this so if I brick I don't care?
My next question is could it be possible to code the PIT file to do this for you so that you can just flash that through odin, but again would flashing roms affect this.
Cheers,
Sora.
aguaz said:
I just did so on S4 Mini with cm-11 Android 4.4.
First I was thinking of using symlinks and/or bind mounts to redirect to the the external sdcard, but that's a bit of a hassle because
1) Since 4.2: both emulated and external storage is mounted with a fuse layer on top not supporting symlinks
2) Since 4.4: no more global write access on external storage
So moving data was the simplest solution. Besides providing (much) more space my sdcard is also around 20% faster in sequential writes: 8.5 MB/s internal vs 10.5 MB/s external. Is it really 2014?
I haven't yet decided what to do with the original data partition, so for the moment I left it unused. Hence I haven't touched the internal partition table.
Quick summary
partition sdcard (gdisk)
I recommend using GPT, this lets you work with partition names rather than numbers. For the sake of still having an "official" external sdcard I made two partitions. Keep in mind that it's usually the first partition which gets automatically mounted as external sdcard. So I made the 2nd partition the new home for data. This partition however has to be manually specified in the ramdisks fstab which involves flashing the boot partition.
format the new partitions (mkfs.ext4)
copy the original /data directory tree to the new data partition
extract initrd from boot.img (abootimg)
extract files from initrd (gunzip & cpio)
replace the /data entry in fstab pointing at your new data partition
re-pack initrd and boot.img (gzip, cpio & abootimg)
flash boot.img onto the boot partition (dd)
If you use recovery, you also have to edit it's fstab (analog to boot.img mentioned above)
done
Alternatively has anyone tried an init.d script? I see those scripts get executed before the mounting of data & sdcard
Click to expand...
Click to collapse
I just managed to replace my internal sd with the external sd following your ruff guide. thank you very much! At first I struggled a bit getting it to work, because I had encrypted my data partition before -.- this seems to change something in the fstab / mounting / boot-up process, I couldn't get my S4 mini to boot with just changing the fstab.qcom in boot.img. With my recovery (TWRP) it worked from the start editing recovery.img's fstab.twrp /data mount point.
After decrypting(formatting) /data and re-editing fstab.qcom in boot.img it finally works I'm so happy! Enjoying a lot of space on my sdcard now!
usefull threads / information I learnt from:
Partition structure of S4 Mini
Encryption of ExtSD & some fstab information
Editing initrd
abootimg ReadMe
(Links last tried 28.05.2015)
Hi all...
Just wandering if anyone new how to resize the system partition of a galaxy a53?
Need to make it larger to fit files onto it but not able to delete bloatware or anything for some reason using all the recommended processes. And to be honest having larger system partition would probably just be useful anyway.
My phone is rooted. I'm not fussed about having to refresh ect. And I have TWRP flashed and Stock Rom.
Please help lol
TWRP should automatically resize your system partition.
When you're installing the ROM, make sure you format /data then /system before installing.
It does, but i want to make the partition larger so i can add files to the system partition once the rom is flashed and phone is set up to be used.
At the moment it say 6GB partition and only the rom fits onto the partition and there isnt any room to add extra files. so im looking to make the partition say 10GB to give myself some wiggle room to play with.
i Have 128GB in total so can spare some extra GB's lol