Modified partition table (16GB versions)

Modified partition table (16GB versions) - Xiaomi Mi 4C

Hello,
I received my second Mi4C 16GB yesterday. It came with some unofficial "global stable" MIUI rom preinstalled (ordered from geekbuying).
I noticed the total capacity of the storage is different from the original Mi4C I bought a while ago (11.19GB vs. 11.31GB on the previous phone). I also noticed some other users and youtubers own phones with wrongly indexed total capacity of the storage as well. I briefly checked the partitions of the phone and it turned out the partition table is different from the stock one (aka the one with the capacity of 11.31GB). I suspect the reseller modified the partition table to be able to flash their own modified unofficial rom.
I've tried a few solutions, but nothing has worked for me so far (nothing reverted the userdata partition to its stock state as indexed by CPU-Z/Antutu).
1.) MiFlash with flash_all.bat script (tried a few fastboot roms) - doesn't work
2.) MiFlash with modified flash_all.bat script (with this line - fastboot %* flash partition "%~dp0images\gpt_both0.bin) - doesn't work
3.) MiPCSuite and flashing the latest chinese stable rom via it - doesn't work
4.) Some partition fix adb script I found on Hungarian message board - doesn't work
5.) flashing multilang rom via TWRP - obviously doesn't work
This is the original topic from xiaomi.eu:
hxxps://xiaomi.eu/community/forums/xiaomi-mi4c.142/
Left one - modified partition table, right one - proper partition table"hxxps://farm6.staticflickr.com/5612/30369274744_d51a097fde_b.jpg
Do you the proper way to return the partition table of the phone to its genuine state, please?

Out of interest, I would be interested to see both your phones running df (open a terminal, run 'su', and then when you have a root shell type 'df -h') so that I can see where your partitions are bloated.
I also have the issue, except to a greater degree : I have under 8gb in the data partition!

InfinityIO said:
Out of interest, I would be interested to see both your phones running df (open a terminal, run 'su', and then when you have a root shell type 'df -h') so that I can see where your partitions are bloated.
I also have the issue, except to a greater degree : I have under 8gb in the data partition!
Click to expand...
Click to collapse
Hi, check this comparison:
hxxps://c2.staticflickr.com/6/5826/31305621321_0608b75a19_k.jpg
There is the exact same multilang MIUI 7 rom installed on both the phones.
I've seen some people on Chinese and Russian forums mentioning the same problem + a few other people responded on the local/eu miui forums.

Code:
[email protected]:/ # df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 889M 76K 889M 1% /dev
none 889M 0 889M 0% /sys/fs/cgroup
tmpfs 889M 0 889M 0% /mnt
/dev/block/mmcblk0p41 1.8G 1.1G 674M 64% /system
/dev/block/mmcblk0p44 9.4G 7.8G 1.6G 83% /data
/dev/block/mmcblk0p43 300M 173M 128M 58% /cust
/dev/block/mmcblk0p36 128M 72M 56M 56% /firmware
/dev/block/mmcblk0p14 64M 80K 64M 1% /bt_firmware
/dev/block/mmcblk0p42 372M 252K 372M 1% /cache
/dev/block/mmcblk0p39 27M 148K 27M 1% /persist
tmpfs 889M 0 889M 0% /storage
/dev/fuse 9.4G 7.8G 1.6G 83% /mnt/runtime/default/emulated
/dev/fuse 9.4G 7.8G 1.6G 83% /storage/emulated
/dev/fuse 9.4G 7.8G 1.6G 83% /mnt/runtime/read/emulated
/dev/fuse 9.4G 7.8G 1.6G 83% /mnt/runtime/write/emulated
[email protected]:/ #
Mine only has 9.4GB.

A shipped, bootloader-flashed official Firmware repartitions as necessary. All you have to do is flash an official rom (not the xiaomi.eu recovery-flashable roms but ACTUAL official roms flashed via fastboot). Im sure some of those would have a different partition table as per suited for ROM needs. Nothing to be alarmed of.

dark_prince said:
A shipped, bootloader-flashed official Firmware repartitions as necessary. All you have to do is flash an official rom (not the xiaomi.eu recovery-flashable roms but ACTUAL official roms flashed via fastboot). Im sure some of those would have a different partition table as per suited for ROM needs. Nothing to be alarmed of.
Click to expand...
Click to collapse
Doesn't work. I've tried flashing several different official Chinese fastboot roms via MiFlash - both the dev and stable ones - but the capacity of the storage remains the same.

A partial solution?
I managed to get my data partition from 7.7G
Code:
Filesystem Size Used Free Blksize
/dev 888.7M 88.0K 888.6M 4096
/sys/fs/cgroup 888.7M 0.0K 888.7M 4096
/mnt/asec 888.7M 0.0K 888.7M 4096
/mnt/obb 888.7M 0.0K 888.7M 4096
/sys/fs/cgroup 888.7M 0.0K 888.7M 4096
/system 1.8G 1.1G 734.9M 4096
/data 7.7G 7.6G 182.8M 4096
/cust 310.0M 18.2M 291.7M 4096
/cache 372.0M 332.0K 371.6M 4096
/persist 27.5M 112.0K 27.4M 4096
/firmware 127.9M 71.5M 56.4M 16384
/bt_firmware 64.0M 80.0K 63.9M 16384
/mnt/shell/emulated 7.7G 7.6G 182.8M 4096
/mnt/shell/emulated/0 7.7G 7.6G 182.8M
To 11G
Code:
Filesystem Size Used Avail Use% Mounted on
tmpfs 888M 572K 888M 1% /dev
tmpfs 888M 0 888M 0% /mnt
/dev/block/mmcblk0p41 1.8G 1.2G 594M 69% /system
/dev/block/mmcblk0p44 11G 5.1G 6.1G 46% /data
/dev/block/mmcblk0p42 372M 256K 372M 1% /cache
/dev/block/mmcblk0p39 27M 140K 27M 1% /persist
/dev/block/mmcblk0p36 128M 72M 56M 56% /firmware
/dev/block/mmcblk0p14 64M 80K 64M 1% /bt_firmware
tmpfs 888M 0 888M 0% /storage
/dev/fuse 11G 5.1G 6.1G 46% /mnt/runtime/default/emulated
/dev/fuse 11G 5.1G 6.1G 46% /storage/emulated
/dev/fuse 11G 5.1G 6.1G 46% /mnt/runtime/read/emulated
/dev/fuse 11G 5.1G 6.1G 46% /mnt/runtime/write/emulated
by opening twrp, going into format partitions, the advanced wipe this will destroy all data - nandroid it menu, then selecting the system partition and selecting format, then resize. I did the same thing for data and the partition gained ~3gbs! I'm not sure how reproducible this is, but it seems to work properly and stays cross-ROM
I know I didn't get the full 11.3G,but it worked somewhat...
Hope this helps you on your quest to downloading large files to your device!
-iO

InfinityIO said:
Hope this helps you on your quest to downloading large files to your device!
-iO
Click to expand...
Click to collapse
Or getting at least part of my music collection on it.

InfinityIO said:
I managed to get my data partition from 7.7G
Code:
Filesystem Size Used Free Blksize
/dev 888.7M 88.0K 888.6M 4096
/sys/fs/cgroup 888.7M 0.0K 888.7M 4096
/mnt/asec 888.7M 0.0K 888.7M 4096
/mnt/obb 888.7M 0.0K 888.7M 4096
/sys/fs/cgroup 888.7M 0.0K 888.7M 4096
/system 1.8G 1.1G 734.9M 4096
/data 7.7G 7.6G 182.8M 4096
/cust 310.0M 18.2M 291.7M 4096
/cache 372.0M 332.0K 371.6M 4096
/persist 27.5M 112.0K 27.4M 4096
/firmware 127.9M 71.5M 56.4M 16384
/bt_firmware 64.0M 80.0K 63.9M 16384
/mnt/shell/emulated 7.7G 7.6G 182.8M 4096
/mnt/shell/emulated/0 7.7G 7.6G 182.8M
To 11G
Code:
Filesystem Size Used Avail Use% Mounted on
tmpfs 888M 572K 888M 1% /dev
tmpfs 888M 0 888M 0% /mnt
/dev/block/mmcblk0p41 1.8G 1.2G 594M 69% /system
/dev/block/mmcblk0p44 11G 5.1G 6.1G 46% /data
/dev/block/mmcblk0p42 372M 256K 372M 1% /cache
/dev/block/mmcblk0p39 27M 140K 27M 1% /persist
/dev/block/mmcblk0p36 128M 72M 56M 56% /firmware
/dev/block/mmcblk0p14 64M 80K 64M 1% /bt_firmware
tmpfs 888M 0 888M 0% /storage
/dev/fuse 11G 5.1G 6.1G 46% /mnt/runtime/default/emulated
/dev/fuse 11G 5.1G 6.1G 46% /storage/emulated
/dev/fuse 11G 5.1G 6.1G 46% /mnt/runtime/read/emulated
/dev/fuse 11G 5.1G 6.1G 46% /mnt/runtime/write/emulated
by opening twrp, going into format partitions, the advanced wipe this will destroy all data - nandroid it menu, then selecting the system partition and selecting format, then resize. I did the same thing for data and the partition gained ~3gbs! I'm not sure how reproducible this is, but it seems to work properly and stays cross-ROM
I know I didn't get the full 11.3G,but it worked somewhat...
Hope this helps you on your quest to downloading large files to your device!
-iO
Click to expand...
Click to collapse
Tested this, no need to wipe anything. Just resize it and you're good to go.
No data loss too.
I got 11.3GB after resizing. Thanks!

Cozzmy13 said:
Tested this, no need to wipe anything. Just resize it and you're good to go.
No data loss too.
I got 11.3GB after resizing. Thanks!
Click to expand...
Click to collapse
Can you describe the whole process step by step, please? What is the exact value as indexed by CPU-Z or the similar app? Is it 11.31 GB?

Jatsa - Boot into TWRP (I assume you have it)
Select the 'wipe' menu
Click advanced wipe
Tick the box that says system
Click resize partiton
One it is done, tick the box that says data
Click resize partition
Once done, press the back button until you reach the main menu
Click reboot
Choose system
Enjoy

Jatsa said:
Can you describe the whole process step by step, please? What is the exact value as indexed by CPU-Z or the similar app? Is it 11.31 GB?
Click to expand...
Click to collapse
From TWRP Wipe->Advanced Wipe-> check Data ->Repair or change Filesystem->Resize.
Done.
Glad to help.

Well, it doesn't work. The size of the partition remains still unchanged (11.19 instead of "proper" 11.31).

Maybe there are 2 variants.
100MB don't matter that much.
Exact size: 11856888.

Related

[DISCUSSION] Sensation internal memory partition info

Hello Fellow Sensation Owners!
A couple of days ago someone asked about the Sensation's internal storage layout, which got me curious, as we get 1GB of storage to data partition, about 700MB for system, and where does all the rest go? boot is just a couple of megabytes, and firmware (combined), is 400MB.
When I searched google for it, I couldn't find any mention of the Sensation's partition layout, and barely found how to get it by myself. So here I am, creating this mention/guide (for future people who like me want to know what the partition layout is).
To get the layout and sizes, I used the df command in the shell, which gives a nice table with all (mounted) partitions, with information about them.
The results I got were:
Code:
Filesystem Size Used Free Blksize
/dev 271.7M 52K 271.6M 4096
/storage 271.7M 0K 271.7M 4096
/vendor/firmware/misc 199.8M 21.5M 178.3M 4096
/vendor/firmware/adsp 199.8M 5.7M 194.1M 4096
/mnt/secure 271.7M 0K 271.7M 4096
/mnt/asec 271.7M 0K 271.7M 4096
/mnt/obb 271.7M 0K 271.7M 4096
/mnt/fuse 271.7M 0K 271.7M 4096
/system 787.4M 388.8M 398.6M 4096
/data 1.1G 482.1M 693.9M 4096
/cache 118.1M 98M 20.1M 4096
/devlog 19.7M 14.8M 4.9M 4096
/storage/sdcard0 14.8G 13G 1.8G 32768
/mnt/secure/asec: Permission denied
/mnt/asec/com.quoord.tapatalkxda.activity-1 5M 3.2M 1.8M 4096
Note: I got this list on Cyanogenmod 10.1, a different ROM might bring
different results.
There are a few points of interest here:
1) There are 5 empty partitions, 271.7MB each.
2) Apps stored on the SD card are listed as individual partitions - in my case - XDA app (also tested on Sony Ericsson Live With Walkman - same result).
3) /mnt/secure/asec needs root access to be read, and after enabling, it seems to be mounted to the same space as the sdcard. this partition is actually the Android_secure foldier on the SD Card. This makes me suspect that some of the empty partitions are also mounts of the same partition from different directories inside it.
4) My suspition is most probably wrong, as the sum of all partition sizes amounts to about 4GB, which is what listed on the spec sheet.
5) /boot partition is not listed, which makes me believe some more are not actually mounted.
To know if there are double-mounted partitions, I checked the mount list on /proc/mounts by using this command:
Code:
[B]CAT /proc/mounts[/B]
I will post points of interest I found as It's quite long and mostly messy:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
/dev/block/mmcblk0p17 /vendor/firmware/misc vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p19 /vendor/firmware/adsp vfat ro,relatime,fmask=0000,dmask=00
00,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=re
mount-ro 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p22 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered
,noauto_da_alloc 0 0
/dev/block/mmcblk0p23 /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p24 /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p28 /devlog ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
We can see something interesting - /mnt/secure, /mnt/asec, /mnt/obb, /mnt/fuse, /storage and /dev are all mounted from tmpfs, which is not an adress on the mmc. I have no Idea what this means, but it explains all those partitions seen before - They are the same space (probably like /mnt/secure/asec - folders inside a bigger partition).
This thread is meant for me (and probably other curious users) to understand how the sensation is formatted.
Also, to keep a clean explanation of what each partition actually is (for begginers and to have it organized), here is a list of partitions with explanations about them (all those I know are included, some are basic knowledge, list will be updated).
/data - where your apps and basically all your data that is stored on the device is
/system - where system apps, frameworks, and the rest of the OS is (excluding kernel)
/boot (not listed) - kernel
/storage/sdcard - no need to be imaginative here - the SD card
/mnt/secure/asec - the android_secure folder on sdcard
/cache - app cache - where temporary data is stored to speed up apps
What I'm trying to do here is to create a clear and comprehensive explanation of the Sensation's NAND layout, so anyone looking for it could find it. For non-devs it's of not much use, but nice to know. Also to keep a clear way to check it on other devices (had to dive to linux websites to find some stuff here).
Would be glad if someone more knowledgeable than I am would add/correct me here, to make this helpfull.
To your Enjoyment/feeding your interest.

astar26 said:
Hello Fellow Sensation Owners!
A couple of days ago someone asked about the Sensation's internal storage layout, which got me curious, as we get 1GB of storage to data partition, about 700MB for system, and where does all the rest go? boot is just a couple of megabytes, and firmware (combined), is 400MB.
When I searched google for it, I couldn't find any mention of the Sensation's partition layout, and barely found how to get it by myself. So here I am, creating this mention/guide (for future people who like me want to know what the partition layout is).
To get the layout and sizes, I used the df command in the shell, which gives a nice table with all (mounted) partitions, with information about them.
The results I got were:
Code:
Filesystem Size Used Free Blksize
/dev 271.7M 52K 271.6M 4096
/storage 271.7M 0K 271.7M 4096
/vendor/firmware/misc 199.8M 21.5M 178.3M 4096
/vendor/firmware/adsp 199.8M 5.7M 194.1M 4096
/mnt/secure 271.7M 0K 271.7M 4096
/mnt/asec 271.7M 0K 271.7M 4096
/mnt/obb 271.7M 0K 271.7M 4096
/mnt/fuse 271.7M 0K 271.7M 4096
/system 787.4M 388.8M 398.6M 4096
/data 1.1G 482.1M 693.9M 4096
/cache 118.1M 98M 20.1M 4096
/devlog 19.7M 14.8M 4.9M 4096
/storage/sdcard0 14.8G 13G 1.8G 32768
/mnt/secure/asec: Permission denied
/mnt/asec/com.quoord.tapatalkxda.activity-1 5M 3.2M 1.8M 4096
Note: I got this list on Cyanogenmod 10.1, a different ROM might bring
different results.
There are a few points of interest here:
1) There are 5 empty partitions, 271.7MB each.
2) Apps stored on the SD card are listed as individual partitions - in my case - XDA app (also tested on Sony Ericsson Live With Walkman - same result).
3) /mnt/secure/asec needs root access to be read, and after enabling, it seems to be mounted to the same space as the sdcard. this partition is actually the Android_secure foldier on the SD Card. This makes me suspect that some of the empty partitions are also mounts of the same partition from different directories inside it.
4) My suspition is most probably wrong, as the sum of all partition sizes amounts to about 4GB, which is what listed on the spec sheet.
5) /boot partition is not listed, which makes me believe some more are not actually mounted.
To know if there are double-mounted partitions, I checked the mount list on /proc/mounts by using this command:
Code:
[B]CAT /proc/mounts[/B]
I will post points of interest I found as It's quite long and mostly messy:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
/dev/block/mmcblk0p17 /vendor/firmware/misc vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p19 /vendor/firmware/adsp vfat ro,relatime,fmask=0000,dmask=00
00,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=re
mount-ro 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p22 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered
,noauto_da_alloc 0 0
/dev/block/mmcblk0p23 /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p24 /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p28 /devlog ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
We can see something interesting - /mnt/secure, /mnt/asec, /mnt/obb, /mnt/fuse, /storage and /dev are all mounted from tmpfs, which is not an adress on the mmc. I have no Idea what this means, but it explains all those partitions seen before - They are the same space (probably like /mnt/secure/asec - folders inside a bigger partition).
This thread is meant for me (and probably other curious users) to understand how the sensation is formatted.
Also, to keep a clean explanation of what each partition actually is (for begginers and to have it organized), here is a list of partitions with explanations about them (all those I know are included, some are basic knowledge, list will be updated).
/data - where your apps and basically all your data that is stored on the device is
/system - where system apps, frameworks, and the rest of the OS is (excluding kernel)
/boot (not listed) - kernel
/storage/sdcard - no need to be imaginative here - the SD card
/mnt/secure/asec - the android_secure folder on sdcard
/cache - app cache - where temporary data is stored to speed up apps
What I'm trying to do here is to create a clear and comprehensive explanation of the Sensation's NAND layout, so anyone looking for it could find it. For non-devs it's of not much use, but nice to know. Also to keep a clear way to check it on other devices (had to dive to linux websites to find some stuff here).
Would be glad if someone more knowledgeable than I am would add/correct me here, to make this helpfull.
To your Enjoyment/feeding your interest.
Click to expand...
Click to collapse
i have serious bootloops, ppl are saying my nand is faulted, how do i repair it, as what ever ruu or rom i install i end up with bootloop

dxbboy said:
i have serious bootloops, ppl are saying my nand is faulted, how do i repair it, as what ever ruu or rom i install i end up with bootloop
Click to expand...
Click to collapse
Nobody can repair Nand memory's, probably your entire motherboard needs to be replaced.

All the tmpfs filesystem mounts are temporary ones and are on ram..
Sent from my HTC Sensation using XDA Premium 4 mobile app

I remember the HTC Desire, you could actually change the partition sizes to however you see fit using thalmus HBOOT patcher. It's a shame nobody managed to do it on here as I use AOSP which hardly uses any internal memory

Filesystem Size Used Free Blksize
/dev 271.7M 52K 271.6M 4096
/storage 271.7M 0K 271.7M 4096
/vendor/firmware/misc 199.8M 21.5M 178.3M 4096
/vendor/firmware/adsp 199.8M 5.7M 194.1M 4096
/mnt/secure 271.7M 0K 271.7M 4096
/mnt/asec 271.7M 0K 271.7M 4096
/mnt/obb 271.7M 0K 271.7M 4096
/mnt/fuse 271.7M 0K 271.7M 4096
/system 787.4M 388.8M 398.6M 4096
/data 1.1G 482.1M 693.9M 4096
/cache 118.1M 98M 20.1M 4096
/devlog 19.7M 14.8M 4.9M 4096
/storage/sdcard0 14.8G 13G 1.8G 32768
/mnt/secure 271.7M 0K 271.7M 4096
/mnt/asec 271.7M 0K 271.7M 4096
/mnt/obb 271.7M 0K 271.7M 4096
/mnt/fuse 271.7M 0K 271.7M 4096
THIS IS ONLY ONE 271Ç7M AND IT IS SHARED BY secure, asec, obb, fuse.
I can not find /storage 271.7M 0K 271.7M 4096 in sensation. it is missing.
I sum up and find 3GB.
somhow still missing 0.8gb

sokomind said:
Filesystem Size Used Free Blksize
/dev 271.7M 52K 271.6M 4096
/storage 271.7M 0K 271.7M 4096
/vendor/firmware/misc 199.8M 21.5M 178.3M 4096
/vendor/firmware/adsp 199.8M 5.7M 194.1M 4096
/mnt/secure 271.7M 0K 271.7M 4096
/mnt/asec 271.7M 0K 271.7M 4096
/mnt/obb 271.7M 0K 271.7M 4096
/mnt/fuse 271.7M 0K 271.7M 4096
/system 787.4M 388.8M 398.6M 4096
/data 1.1G 482.1M 693.9M 4096
/cache 118.1M 98M 20.1M 4096
/devlog 19.7M 14.8M 4.9M 4096
/storage/sdcard0 14.8G 13G 1.8G 32768
/mnt/secure 271.7M 0K 271.7M 4096
/mnt/asec 271.7M 0K 271.7M 4096
/mnt/obb 271.7M 0K 271.7M 4096
/mnt/fuse 271.7M 0K 271.7M 4096
THIS IS ONLY ONE 271Ç7M AND IT IS SHARED BY secure, asec, obb, fuse.
I can not find /storage 271.7M 0K 271.7M 4096 in sensation. it is missing.
I sum up and find 3GB.
somhow still missing 0.8gb
Click to expand...
Click to collapse
MMC
Manufacturer: Samsung Electronics
Model: MLL00M
Size: 2416 MB
Manufacture Date: Jun 2011
SDIO
Manufacturer: Broadcom
Model: BCM4329
Whoever said this device is 4GB was drunk.

can you tell me please witch mmcblk is hboot?

[Q] Vanir last nightly calculating wrong discspace

Hello,
I am not allowed to post into the developer-thread http://forum.xda-developers.com/showthread.php?t=2689519 -- I installed latest nightly http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/skomer/vanir_skomer_4.4.4.092614.zip wiped user/cache afterwards, installed pa_gapps-modular-pico-4.4.4-20140923-signed.zip -- and wiped user/cache afterwards.
When booting (before and after flashing gapps) the device tells me, I am running out of disk-space. But there is still plenty of it. It is about 1.18 GB available, but only 10 MB displayed as unused. Although the bar shows the real situation. In shell I get
Code:
1|[email protected]:/ $ df
Filesystem Size Used Free Blksize
/dev 401.8M 172.0K 401.7M 4096
/sys/fs/cgroup 401.8M 12.0K 401.8M 4096
/mnt/asec 401.8M 0.0K 401.8M 4096
/mnt/obb 401.8M 0.0K 401.8M 4096
/mnt/fuse 401.8M 0.0K 401.8M 4096
/dev/shm 401.8M 0.0K 401.8M 4096
[B]/system 1.2G 398.0M 783.1M 4096[/B]
/modemfs 15.7M 4.4M 11.4M 4096
/cache 728.3M 12.5M 715.8M 4096
/efs 15.7M 4.6M 11.1M 4096
/data 1.2G 1.2G 11.0M 4096
/mnt/.lfs: Function not implemented
/mnt/shell/emulated 1.2G 1.2G 11.0M 4096
/mnt/media_rw/sdcard1: Permission denied
/storage/sdcard1 1.8G 553.0M 1.3G 32768
As you can see, there is enough space on SystemPartition. I am inclined to consider this a bug, but I am not sure. If so, where do I post it?
Thanks for any help
greetings
Karl
Edit: The former version also shows this behaviour. It is not very likely that this is a bug

full data partition
Okay, its not the system but the data-partition, which is out of space.
Code:
/data 1.2G 1.2G 11.0M 4096
How can this be even when I wiped the user partition? I already formated it via cwm but same result. /data/app is empty /data/app-lib/ as well.
Greetings
Karl

solved
Well that's really, really strange. Although I wiped the data partition several times and did a "format /data" via cwm about 2 times, there was an old backup in /data/media/clockworkmod. That folder plugged the partition.
Greetings
Karl

Can you resize any partitions on the MI 4C?

About a week ago, I first ran out of (aka hit 90%) space, and have been forced to let go of some games. Only after doing this, I noticed that my (16GB) phone had just 7.7G total for the data partition.
So, I ran df:
Code:
[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 888.7M 88.0K 888.6M 4096
/sys/fs/cgroup 888.7M 0.0K 888.7M 4096
/mnt/asec 888.7M 0.0K 888.7M 4096
/mnt/obb 888.7M 0.0K 888.7M 4096
/sys/fs/cgroup 888.7M 0.0K 888.7M 4096
/system 1.8G 1.1G 734.9M 4096
/data 7.7G 7.6G 182.8M 4096
/cust 310.0M 18.2M 291.7M 4096
/cache 372.0M 332.0K 371.6M 4096
/persist 27.5M 112.0K 27.4M 4096
/firmware 127.9M 71.5M 56.4M 16384
/bt_firmware 64.0M 80.0K 63.9M 16384
/mnt/shell/emulated 7.7G 7.6G 182.8M 4096
/mnt/shell/emulated/0 7.7G 7.6G 182.8M 4096
Is it possible to modify any of the 4 empty 888M partition sizes to give me an extra 3gb of space?
Running xiaomi.eu MIUI 7 (dev) final, have TWRP, xposed and full root.
Thanks.
Any reply is appreciated.

Extending vendor partition

How can I extend the vendor partition?
I am building the ROM from AOSP. Can I increase the partition size of vendor in the AOSP somewhere?
Code:
Filesystem Size Used Avail Use% Mounted on
/dev/root 2.4G 1.0G 1.4G 43% /
tmpfs 1.7G 572K 1.7G 1% /dev
tmpfs 1.7G 0 1.7G 0% /mnt
/dev/block/sdd3 27M 3.4M 24M 13% /persist
/dev/block/sda41 492M 345M 147M 71% /vendor
/dev/block/sda28 80M 59M 21M 74% /firmware
/dev/block/sda45 52G 145M 52G 1% /data
/data/media 52G 145M 52G 1% /mnt/runtime/default/emulated
I need a couple of 100M more in /vendor to store a debug version of a library.
Thanks for any help!

jocken said:
How can I extend the vendor partition?
I am building the ROM from AOSP. Can I increase the partition size of vendor in the AOSP somewhere?
Code:
Filesystem Size Used Avail Use% Mounted on
/dev/root 2.4G 1.0G 1.4G 43% /
tmpfs 1.7G 572K 1.7G 1% /dev
tmpfs 1.7G 0 1.7G 0% /mnt
/dev/block/sdd3 27M 3.4M 24M 13% /persist
/dev/block/sda41 492M 345M 147M 71% /vendor
/dev/block/sda28 80M 59M 21M 74% /firmware
/dev/block/sda45 52G 145M 52G 1% /data
/data/media 52G 145M 52G 1% /mnt/runtime/default/emulated
I need a couple of 100M more in /vendor to store a debug version of a library.
Thanks for any help!
Click to expand...
Click to collapse
Messing with partition size is risky business. I'm not sure how to do it with a dual slot device and it may not even work. I have only done it once on an old device. Look for Gparted and do a lot of research. I'm not a developer but pretty sure you can't do it within aosp.

[Android10 / Samsung] Partitions messed up?

Hi there,
after giving up on rooting my Samsung Galaxy XCover Pro (No TWRP / Magisk ending in Bootloop/All other tools failing) I reinstalled stock firmware with december security update on the phone and began with setting up stuff, deleting bloatware etc. for the last hours.
Now, before installing new apps, I wanted to copy back the files I previously saved from user directory (as far as it is exposed on Windows in Debug mode) and had to see, that my 64GB devices shows only 2GB available (from 4GB total), which is of cource far too low for my backuped files.
In system settings it says there are 14.1GB of 16GB in use. 12.1GB are marked as used for system memory.
Deleting logs with *#9900# didn't do anything remarkable.
Because I have no root and can't get root, I have limited options to see what went wrong, but if I look at 'df -h' on adb shell I get the following output:
Code:
xcoverpro:/ $ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/block/dm-4 4.3G 4.2G 22M 100% /
tmpfs 1.7G 0.9M 1.7G 1% /dev
tmpfs 1.7G 0 1.7G 0% /mnt
tmpfs 1.7G 0 1.7G 0% /apex
/dev/block/dm-5 500M 497M 2.6M 100% /vendor
/dev/block/dm-6 648M 647M 0.9M 100% /product
/dev/block/dm-7 3.9M 32K 3.9M 1% /odm
/dev/block/dm-8 533M 428M 105M 81% /prism
/dev/block/dm-9 19M 1.6M 18M 9% /optics
tmpfs 1.7G 0 1.7G 0% /mnt/sde
/dev/block/sda29 16M 24K 16M 1% /omr
/dev/block/sda28 193M 4.8M 188M 3% /cache
/dev/block/sda2 16M 452K 15M 3% /efs
/dev/block/sda32 3.9G 1.9G 1.9G 51% /data
/dev/block/loop2 21M 5.1M 16M 25% /apex/[email protected]
/dev/block/loop3 21M 21M 32K 100% /apex/[email protected]
/dev/block/loop4 114M 96M 18M 85% /apex/[email protected]
/dev/block/loop5 17M 1.5M 15M 10% /apex/[email protected]
/dev/block/loop6 5.2M 5.2M 32K 100% /apex/[email protected]
/dev/block/loop7 836K 808K 28K 97% /apex/[email protected]
/dev/block/loop8 232K 36K 196K 16% /apex/[email protected]
/data/knox/secure_fs/enc_media 3.8G 1.9G 1.9G 52% /mnt/shell/enc_emulated
/data/media 3.8G 1.9G 1.9G 52% /storage/emulated
Summing everything up I end with only about 25GB of partitioned space for my 64GB device.
Something is very wrong I guess, but I don't know what exactly and how to fix it.
Can you help?
Thanks/regards,
rund3
Btw. Please don't tell me that I have to do all setup/configuration stuff again ;(

Database Info

welcome