[Android10 / Samsung] Partitions messed up? - General Questions and Answers

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 ;(

Related

[Q] Where's the mount point for the root file system?

On my G1, I know that the internal flash memory is divided into several partitions used by the system. Running the busybox shell on a terminal emulator on the phone or through adb, I can run df and get the following:
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 48852 0 48852 0% /dev
tmpfs 48852 0 48852 0% /mnt/asec
/dev/block/mtdblock3 92160 89048 3112 97% /system
/dev/block/mtdblock5 91904 77792 14112 85% /data
/dev/block/loop0 4096 4096 0 100% /system/xbin
/dev/block/mtdblock4 30720 1160 29560 4% /cache
/dev/block/vold/179:1
15541688 12742232 2799456 82% /mnt/sdcard
/dev/block/vold/179:1
15541688 12742232 2799456 82% /mnt/secure/asec
But strangely there's no mount point for /, the root file system. Yet there are lot of other files and directories directly in the root file system, like init scripts. Could anyone explain to me how this is? Is the root file system hidden somehow from df?

Modified partition table (16GB versions)

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.

'huge' storage usage - s7 g930fd upgraded to oreo

i've got pretty much a rather 'new' (i.e. started with only the base rom pretty much) sam s7 930fd, after i upgraded it to oreo gets it rooted, install titanium backup, i started removing some bloaware apps (e.g. facebook et.al.)
However, after i've removed the bloatware, i'm rather surprised that under settings > device management it shows 10.5 GB used out of 32 GB available. i.e. one third of the storage is 'gone' while i hardly had any other apps installed other than the base rom and upgrade to oreo
hence i go about doing an adb shell from the pc and start checking
Code:
# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1660424 15752 1644672 1% /
tmpfs 1806128 1292 1804836 1% /dev
/dev/block/sda18 25723972 3158848 22565124 13% /dev/block/supersu/daemonsu
/dev/block/sda18 25723972 3158848 22565124 13% /dev/block/supersu/su
/dev/block/sda18 25723972 3158848 22565124 13% /dev/block/supersu/sukernel
/dev/block/sda18 25723972 3158848 22565124 13% /dev/block/supersu/supersu
tmpfs 1811384 0 1811384 0% /mnt
tmpfs 1811384 0 1811384 0% /mnt/secure
tmpfs 49258992 1764944 47494048 4% /mnt/secure/asec
/dev/block/vold/public:179,1 49258992 1764944 47494048 4% /mnt/secure/asec
/data/media 25723972 3158848 22565124 13% /mnt/runtime/default/emulated
/data/media 25723972 3158848 22565124 13% /mnt/runtime/read/emulated
/data/media 25723972 3158848 22565124 13% /mnt/runtime/write/emulated
/dev/block/vold/public:179,1 49258992 1764944 47494048 4% /mnt/media_rw/5C52-6601
/mnt/media_rw/5C52-6601 49258992 1764944 47494048 4% /mnt/runtime/default/5C52-6601
/mnt/media_rw/5C52-6601 49258992 1764944 47494048 4% /mnt/runtime/read/5C52-6601
/mnt/media_rw/5C52-6601 49258992 1764944 47494048 4% /mnt/runtime/write/5C52-6601
/dev/block/dm-0 7180 5360 1820 75% /mnt/asec/org.brandroid.openmanager-1
/dev/block/sda14 4299884 3778936 520948 88% /system
/dev/block/sda15 197472 23428 174044 12% /cache
/dev/block/sda18 25723972 3158848 22565124 13% /data
/dev/block/mmcblk0p2 13671512 34224 13637288 1% /data/sdext2
/dev/block/sda3 16048 2468 13580 16% /efs
/dev/block/sda13 5032 44 4988 1% /persdata/absolute
/dev/block/sdd1 1936 552 1384 29% /cpefs
tmpfs 1806128 1292 1804836 1% /sbin
/dev/block/sda18 25723972 3158848 22565124 13% /sbin/daemonsu
/dev/block/sda18 25723972 3158848 22565124 13% /sbin/su
/dev/block/sda18 25723972 3158848 22565124 13% /sbin/sukernel
/dev/block/sda18 25723972 3158848 22565124 13% /sbin/supersu
tmpfs 1811384 0 1811384 0% /storage
/data/media 25723972 3158848 22565124 13% /storage/emulated
/mnt/media_rw/5C52-6601 49258992 1764944 47494048 4% /storage/5C52-6601
tmpfs 1811384 0 1811384 0% /storage/self
as it turns out, only 25 GB is allocated to /data, the rest seemed to be distributed elseswhere e.g. root partition mount point
/mnt/media_rw/5C52-6601 is an external sd card, so is /dev/block/mmcblk0p2 i think which i use for link-to-sd.
and out of that 25 GB allocated to data about 3GB is used (pretty reasonable, i think gapps lives here, i kept most of the gapps dispite the bloat)
however, 32 GB - 25 GB is 7GB and this 'missing' 7GB didn't really seem to be found anywhere. i.e. after adding up the storage ex of data it didn't seem to add up to this 7GB i.e. the root partition etc only consume a portion of this 7GB
i'm finally tempted to purchase a bigger (newer) device given this situation. link-to-sd still works with oreo just that the 2nd slot is used for either micro sd card or a sim card, you can't have both. This may be a big limitation given the storage capacity limits and possibly the need to use the 2nd sim slot.
is it the same for your device or any comments about the storage etc?
thanks in advance

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.

Space missing after DotOS installing

Recently I installed DotOS on my Samsung SM-J320F. All good but internal space was reduced. This phone have 8 GB but I receive this when I run df:
~ # ←[6ndf
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 696068 204 695864 0% /dev
tmpfs 696068 28 696040 0% /tmp
/dev/block/mmcblk0p27
5027508 4601436 409688 92% /data
/dev/block/mmcblk0p27
5027508 4601436 409688 92% /sdcard
/dev/block/mmcblk0p24
197472 276 193100 0% /cache
/dev/block/mmcblk1p1 24862304 13880880 10981424 56% /extSdCard
~ # ←[6n
Also Windows says I have only 4.79GB
How can I recover 3GB of space?
No one know to solve my problem ?

Categories

Resources