I am in the process of putting together a ROM based on a Mediatek device and the scatter file I have lists the userdata partition with a size of only 1.3 GB or so. It is the last partition that is downloaded onto the device (the flashinfo and sgpt partitions come after that but are not set to be downloaded as they have the is_download: false entry). Hence, this partition is expected to extend to the full available space on the device (userdata is set to be located at around 3 GB and the total size of the device is 12 GB, so it can be extended much further)
Now I was wondering in what part of the installation process the userdata partition gets extended to take up the remainder of the space of the EMMC. Does this happen during the first run? Or does it need a separate factory reset? Anyone with some expert knowledge care to explain?
Related
Sick of the separate userdata and fakesd partitions and familiar with Nexus 4's way of doing things (only userdata), I've tried to repartition my device.
The way I went about it was by booting a recovery (twrp), and, via adb shell, sharing the whole mmcblk0 via usb_mass_storage. It is a GPT partition table, so I used gparted, got rid of the "media" partition and then resized the userdata partition to cover all the gained space.
However, the whole partition layout resets (ouch) when I reboot at all. I do not know who if it's the bootloader or recovery's fault, only that any changes I make to the GPT partition table go away after I reboot.
I'd appreciate some intel if any of you know what's actually going on.
Sick of the separate userdata and fakesd partitions in NexusS and familiar with Nexus 4's way of doing things (only userdata, ext4), I've tried repartitioning my device.
So I booted a recovery (twrp), then connected via adb shell and made the kernel share the whole mmcblk0 via usb_mass_storage.
The block device seems to have a GPT partition table, so with the help of gparted, I got rid of the "media" partition and then resized the userdata partition to cover all the gained space.
However, the whole partition layout resets (ouch) when I reboot at all. I do not know who if it's the bootloader or recovery's fault, only that any changes I make to the GPT partition table go away after I reboot.
I'm sure someone here knows exactly what's happening, please tell us.
li_suna said:
Sick of the separate userdata and fakesd partitions in NexusS and familiar with Nexus 4's way of doing things (only userdata, ext4), I've tried repartitioning my device.
So I booted a recovery (twrp), then connected via adb shell and made the kernel share the whole mmcblk0 via usb_mass_storage.
The block device seems to have a GPT partition table, so with the help of gparted, I got rid of the "media" partition and then resized the userdata partition to cover all the gained space.
However, the whole partition layout resets (ouch) when I reboot at all. I do not know who if it's the bootloader or recovery's fault, only that any changes I make to the GPT partition table go away after I reboot.
I'm sure someone here knows exactly what's happening, please tell us.
Click to expand...
Click to collapse
Is there nowadays a real solution for repartitioning and make a bigger userdate partition ?
skorzo said:
Is there nowadays a real solution for repartitioning and make a bigger userdate partition ?
Click to expand...
Click to collapse
Why don't you try this guide:
http://forum.xda-developers.com/nexus-s/general/howto-combined-emulated-storage-nexus-s-t2848752
Hi,
before I brick my smartphone: is the internal storage a real GPT partitioned thing which can be changed by gdisk, parted and friends? I'll change only the things starting with cache - and only sizes & partitions, not the overall layout. I would like to squeeze the unused cache-partition to a few MBs and reduce the cdrom-partition, move the system-partition at top and increase the userdata partition.
Best regards,
mifritscher
Any infos on this one? Could I recover from a completely broken flash via fastboot, qdload or sdboot?
Ok, I tried - and failed *g*
I partitioned with parted - and the kernel accepted the new partition table as well. But it seems that the phone either blocks write access to the GPT, or has its own internal version. Because after a reboot, I got the old partition table again.
Luckily I had a backup (with I needed for repartitioning anyway), and both fastboot and recovery worked. TWRP was only a bit refused regarding the broken partitions, but it could both reformat the partition and fire the backup (with I did with dd and gzip) before).
So the big question is: How can I unlock the emmc to write to the GPT?
I have 16GB phone and wanted to do a full backup but it's size is 11768MB which I think should be more, look at the calculation:
it's 16GB phone (in decimal) which in binary is 14.9GB. (16000/1074) so main internal storage in digital computation is 14.9GB.
my system partition+data partition (shown in TWRP backup) are 11768MB. (9500 /data and rest is /system)
my internal storage: 868MB free + 1.36GB used (=2228MB)
all other partitions are 167MB (excluding data and system and sdcard)
so far it's 11768+2228+167=14,163MB
but my whole internal storage is 14,900MB and now whole things on my phone is 14,163MB, so where is that 737MB?
also apps cache and system cache are almost nothing and dalvik cache is 629MB (which I think is included in TWRP's /data calculation)
do you have any idea of missing 737MB? does TWRP exclude anything or am I wrong?
TWRP saves only those partitions that may change due to flashing custom ROM.
An example is the vendor partition.
ze7zez said:
TWRP saves only those partitions that may change due to flashing custom ROM.
An example is the vendor partition.
Click to expand...
Click to collapse
yes I know and I calculated whole partitions and SDCARD and TWRP system and data and free storage and everything but the size isn't same as device internal storage space (you can look at my calculation above)
If you want you can always save a disk and not the partitions.
You won't be able to flash it with fastboot (I don't think), but if you have EDL or its equivalent you can.
Renate said:
If you want you can always save a disk and not the partitions.
You won't be able to flash it with fastboot (I don't think), but if you have EDL or its equivalent you can.
Click to expand...
Click to collapse
it's not about backing up, it's mostly because of my curiosity that why when I have root and calculated whole stuff (partitions) plus cache plus free space, altogether they don't fit my internal disk space (14.9GB) and are 737MB less!!! can you test it on your phone and see what will be the result.
I really have no idea what we are discussing.
Code:
Poke3:/ # dd if=/dev/block/mmcblk0 of=/dev/null
61071360+0 records in
61071360+0 records out
31268536320 bytes (29 G) copied, 209.698476 s, 142 M/s
I don't use TWRP.
I have a miscellaneous brand phone with root access. Its system comes with lots of junk apps pre-installed, so I unpacked the system image and deleted them. As a result, the system partition which was originally 2GB now only uses 1GB. I then used the parted tool to shrink the system partition and enlarge the userdata partition. However, when I tried to flash the system partition with the "fastboot flash" command, it still required 2GB of space and showed "sparse image size span overflow" error. Is there any way to pack the system partition while reducing its actual occupied size, or force flash the system image?