I have some difficulties understanding partitions' layout of my phone. (Huawei G6-U10 ***NOT*** rooted yet)
As spec:
4 GB Internal Memory
|__ 2 GB reserved
|__ 2 GB Internal Storage
|__ Memory android option menu shows ~2 GB total (1,91 GB) but only ~1 GB (1,03 GB) available.If I connect my phone through MTP it shows as internal memory just a partition of ~ 1 GB (994 MB)
32 GB external SD
Code:
major minor #blocks name
7 1 9387 loop1
7 2 16664 loop2
7 3 10427 loop3
7 4 15624 loop4
253 0 196608 zram0
179 0 3866624 mmcblk0
179 1 512 mmcblk0p1
179 2 32 mmcblk0p2
179 3 32 mmcblk0p3
179 4 500 mmcblk0p4
179 5 500 mmcblk0p5
179 6 5592 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 65536 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 98304 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 1 mmcblk0p13
179 14 8 mmcblk0p14
179 15 32768 mmcblk0p15
179 16 65536 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 12288 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 262144 mmcblk0p20
179 21 196608 mmcblk0p21
179 22 4096 mmcblk0p22
179 23 1048576 mmcblk0p23
179 24 1048576 mmcblk0p24
179 25 974831 mmcblk0p25
179 32 2048 mmcblk0rpmb
179 64 30748672 mmcblk1
179 65 30744576 mmcblk1p1
254 1 9387 dm-1
254 4 15624 dm-4
254 2 16663 dm-2
254 3 10426 dm-3
Then I listed partition symlink by name
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p6
bkbootup -> /dev/block/mmcblk0p16
boot -> /dev/block/mmcblk0p18
cache -> /dev/block/mmcblk0p21
cust -> /dev/block/mmcblk0p20
fsc -> /dev/block/mmcblk0p13
fsg -> /dev/block/mmcblk0p12
grow -> /dev/block/mmcblk0p25
log -> /dev/block/mmcblk0p15
misc -> /dev/block/mmcblk0p22
modem -> /dev/block/mmcblk0p11
modemst1 -> /dev/block/mmcblk0p9
modemst2 -> /dev/block/mmcblk0p10
oeminfo -> /dev/block/mmcblk0p8
pad -> /dev/block/mmcblk0p7
persist -> /dev/block/mmcblk0p17
recovery -> /dev/block/mmcblk0p19
rpm -> /dev/block/mmcblk0p4
sbl1 -> /dev/block/mmcblk0p1
sdi -> /dev/block/mmcblk0p2
ssd -> /dev/block/mmcblk0p14
system -> /dev/block/mmcblk0p23
tz -> /dev/block/mmcblk0p5
userdata -> /dev/block/mmcblk0p24
Assuming a blocksize of 1024, I can see that sizes of mmcblk0p23 (/system) and mmcblk0p24 (/userdata) are 1 GB each.
1) The space unavailable from internal storage, is the /userdata partition?
2) Of the 2 GB Android doesn't show at all, 1 is obviously occupied by /system, but if the sum of all the other partitions on the first block device (except /userdata and /system) is equal to ~1,67 GB, how can it resides on the 1 GB remaining space?
3)What's the /grow mountpoint?
1 Day, 30 views, 7th page and no reply.
Have I made any mistake? Wrong category? Questions are unclear?
Bump.
Another bump.
I fear people stop reading this thread after the title, because they think it's the same old "I don't know what partitions and mountpoints are and don't want to document about it".
Please read the questions.
Related
Does anyone know the partition which stores the baseband?
cat /proc/partitions doesn't give me the required information:
Code:
major minor #blocks name alias
7 3 314624 loop3
179 0 15564800 mmcblk1
179 1 128 mmcblk1p1
179 2 512 mmcblk1p2
179 3 512 mmcblk1p3
179 4 1 mmcblk1p4
179 5 512 mmcblk1p5
179 6 512 mmcblk1p6
179 7 4096 mmcblk1p7 pds
179 8 512 mmcblk1p8 utags
179 9 1024 mmcblk1p9
179 10 2048 mmcblk1p10
179 11 512 mmcblk1p11
179 12 512 mmcblk1p12
179 13 4096 mmcblk1p13
179 14 8192 mmcblk1p14 boot
179 15 9216 mmcblk1p15 recovery
179 16 217088 mmcblk1p16 cdrom
179 17 512 mmcblk1p17 misc
179 18 512 mmcblk1p18 cid
179 19 4096 mmcblk1p19 kpanic
179 20 793600 mmcblk1p20 system
179 21 737280 mmcblk1p21 cache
179 22 9216 mmcblk1p22 preinstall
179 23 1364992 mmcblk1p23 webtop
179 24 3989504 mmcblk1p24 userdata
179 25 8401792 mmcblk1p25 emstorage
179 26 128 mmcblk1p26
179 64 2048 mmcblk1boot1
179 32 2048 mmcblk1boot0
179 96 31166976 mmcblk0
179 97 31162880 mmcblk0p1
[email protected]:/ #
THX!
dmesg and search for kernel boot line, it contains association with partition number and name
Before
Code:
major minor #blocks name
7 0 48888 loop0
7 1 16664 loop1
7 2 5229 loop2
7 3 2111 loop3
253 0 409600 zram0
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1
179 2 52764 mmcblk0p2
179 3 128 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16896 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 780 mmcblk0p15
179 16 2826240 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 2119680 mmcblk0p18
179 19 6144 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 8 mmcblk0p25
179 26 9216 mmcblk0p26
179 27 20480 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 10219520 mmcblk0p29
179 32 31166976 mmcblk1
179 33 31162880 mmcblk1p1
254 0 48888 dm-0
254 1 16663 dm-1
254 2 5229 dm-2
254 3 2110 dm-3
After
Code:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 4190 loop0
7 1 16664 loop1
7 2 2111 loop2
7 3 8348 loop3
7 4 19782 loop4
7 6 5229 loop6
7 7 5229 loop7
253 0 409600 zram0
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1
179 2 52764 mmcblk0p2
179 3 128 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16896 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 780 mmcblk0p15
179 16 2826240 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 2119680 mmcblk0p18
179 19 6144 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 8 mmcblk0p25
179 26 9216 mmcblk0p26
179 27 20480 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 10219520 mmcblk0p29
179 32 31166976 mmcblk1
179 33 31162880 mmcblk1p1
254 0 4189 dm-0
254 1 16663 dm-1
254 2 2110 dm-2
254 3 8347 dm-3
254 6 5229 dm-6
254 7 5229 dm-7
7 8 48888 loop8
254 8 48888 dm-8
254 4 19782 dm-4
Surge1223 said:
Before
Code:
major minor #blocks name
7 0 48888 loop0
7 1 16664 loop1
7 2 5229 loop2
7 3 2111 loop3
Click to expand...
Click to collapse
These are loopbacks. What that means is that a file somewhere is mapped by /dev/loop0 to look like a disk.
Between earlier and now, something changed in what's loopback mounted.
The important partitions - those on your internal MMC memory, are unchanged.
Surge1223 said:
Code:
254 0 48888 dm-0
254 1 16663 dm-1
254 2 5229 dm-2
254 3 2110 dm-3
Click to expand...
Click to collapse
The dm-0, -1, -2 are purchased applications, mounted on /mnt/asec if I remember right. Where they're mounted will tell you the app name.
Hi,
i've checked out the partition list of my watch, using adb and parted.
Code:
D:\Handy\LG_G_Watch\ota>cmd.exe
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle Rechte vorbehalten.
D:\Handy\LG_G_Watch\ota>adb shell cat /proc/partitions
major minor #blocks name
179 0 3817472 mmcblk0
179 1 1024 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 2048 mmcblk0p10
179 11 512 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 22528 mmcblk0p14
179 15 22528 mmcblk0p15
179 16 22528 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 262144 mmcblk0p19
179 20 262144 mmcblk0p20
179 21 3182592 mmcblk0p21
179 22 495 mmcblk0p22
179 32 4096 mmcblk0rpmb
D:\Handy\LG_G_Watch\ota>
[email protected]:/ # ls /dev/block/platform/msm_sdcc.1/by-name
ls /dev/block/platform/msm_sdcc.1/by-name
DDR
aboot
abootb
boot
cache
grow
imgdata
laf
metadata
misc
persist
recovery
rpm
rpmb
sbl1
sbl1b
sdi
ssd
system
tz
tzb
userdata
Model: MMC H4G1d♦ (sd/mmc)
Disk /dev/block/mmcblk0: 3909MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 1573kB 1049kB sbl1
2 1573kB 2097kB 524kB rpm
3 2097kB 2621kB 524kB tz
4 2621kB 3146kB 524kB sdi
5 3146kB 3670kB 524kB aboot
6 3670kB 4719kB 1049kB sbl1b
7 4719kB 5243kB 524kB rpmb
8 5243kB 5767kB 524kB tzb
9 5767kB 6291kB 524kB abootb
10 6291kB 8389kB 2097kB imgdata
11 8389kB 8913kB 524kB metadata
12 8913kB 25.7MB 16.8MB misc
13 25.7MB 42.5MB 16.8MB ext4 persist
14 42.5MB 65.5MB 23.1MB laf
15 65.5MB 88.6MB 23.1MB boot
16 88.6MB 112MB 23.1MB recovery
17 112MB 112MB 524kB ssd
18 112MB 113MB 524kB DDR
19 113MB 381MB 268MB ext4 system
20 381MB 650MB 268MB ext4 cache
21 650MB 3909MB 3259MB ext4 userdata
22 3909MB 3909MB 507kB grow
(parted)
regards
starbase64
How exactly do I interpret this now? Do the numbers on the first block correspond to the numbers on the third one? So, as example, boot is mmcblk0p15?
I installed CM 12.1 (Android 5.1.1) on my Meizu MX4 Ubuntu (16GB internal storage)
Internal storage (User) in CM is shown as 775MB (Used: 617M, free: 158.0M), but DiskInfo indicates: Data (userdata) mmcblk0p16, Used: 11,7GB, free 131MB
Diskinfo seems to show the right size (16GB minus Android-data etc), but I cannot access this space within my internal storage in cm to check the 11,7GB used (could be some ubuntu files or zip-files from flashing).
Anyone an idea how I can access the full userdata partition and how i can tell cm to show/use it?
Partition results from terminal:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 3136 loop0
179 0 15388672 mmcblk0
179 1 3072 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 256 mmcblk0p5
179 6 384 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 6144 mmcblk0p9
179 10 512 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 10624 mmcblk0p13
179 14 2113536 mmcblk0p14
179 15 720896 mmcblk0p15
179 16 12439040 mmcblk0p16 => (userdata -> /dev/block/mmcblk0p16)
179 17 16384 mmcblk0p17
179 96 4096 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
253 0 3136 dm-0
[email protected]:/ # du -hs /
1.2G /
: df
Filesystem Size Used Free Blksize
/dev 946.1M 64.0K 946.0M 4096
/sys/fs/cgroup 946.1M 20.0K 946.0M 4096
/mnt/asec 946.1M 0.0K 946.1M 4096
/mnt/obb 946.1M 0.0K 946.1M 4096
/storage/emulated 946.1M 0.0K 946.1M 4096
/system 1.2G 479.3M 791.6M 4096
/data 774.9M 616.9M 158.0M 4096 (=> userdata)
/cache 681.9M 808.0K 681.1M 4096
/protect_f 4.8M 56.0K 4.8M 4096
/protect_s 4.8M 52.0K 4.8M 4096
/mnt/secure/asec 774.9M 616.9M 158.0M 4096
/mnt/shell/emulated 774.9M 616.9M 158.0M 4096
/mnt/asec/mz.guitar 3.0M 1.8M 1.2M 4096
I have exactly the same issue with my MX4 and a CM13 image.
Did you find a solution ?
cm_ubu said:
I installed CM 12.1 (Android 5.1.1) on my Meizu MX4 Ubuntu (16GB internal storage)
Internal storage (User) in CM is shown as 775MB (Used: 617M, free: 158.0M), but DiskInfo indicates: Data (userdata) mmcblk0p16, Used: 11,7GB, free 131MB
Diskinfo seems to show the right size (16GB minus Android-data etc), but I cannot access this space within my internal storage in cm to check the 11,7GB used (could be some ubuntu files or zip-files from flashing).
Anyone an idea how I can access the full userdata partition and how i can tell cm to show/use it?
Partition results from terminal:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 3136 loop0
179 0 15388672 mmcblk0
179 1 3072 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 256 mmcblk0p5
179 6 384 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 6144 mmcblk0p9
179 10 512 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 10624 mmcblk0p13
179 14 2113536 mmcblk0p14
179 15 720896 mmcblk0p15
179 16 12439040 mmcblk0p16 => (userdata -> /dev/block/mmcblk0p16)
179 17 16384 mmcblk0p17
179 96 4096 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
253 0 3136 dm-0
[email protected]:/ # du -hs /
1.2G /
: df
Filesystem Size Used Free Blksize
/dev 946.1M 64.0K 946.0M 4096
/sys/fs/cgroup 946.1M 20.0K 946.0M 4096
/mnt/asec 946.1M 0.0K 946.1M 4096
/mnt/obb 946.1M 0.0K 946.1M 4096
/storage/emulated 946.1M 0.0K 946.1M 4096
/system 1.2G 479.3M 791.6M 4096
/data 774.9M 616.9M 158.0M 4096 (=> userdata)
/cache 681.9M 808.0K 681.1M 4096
/protect_f 4.8M 56.0K 4.8M 4096
/protect_s 4.8M 52.0K 4.8M 4096
/mnt/secure/asec 774.9M 616.9M 158.0M 4096
/mnt/shell/emulated 774.9M 616.9M 158.0M 4096
/mnt/asec/mz.guitar 3.0M 1.8M 1.2M 4096
Click to expand...
Click to collapse
Solved
I deleted all, played around with adb parted and formatting (fastboot and adb), installed android, deleted all again, installed CM and now it works. I dont know exactly where the error was, but this way you probably can also solve the problem. Good luck!
PS: I am really disappointed from ubuntu phone. CM is exactly what I expected from ubuntu, it is great!!
here is the proc/partition output
126|NS-P11A8100:/ $ cat /proc/partitions
major minor #blocks name
254 0 485312 zram0
179 0 30310400 mmcblk0
179 1 3072 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 49152 mmcblk0p5
179 6 256 mmcblk0p6
179 7 384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 6144 mmcblk0p10
179 11 512 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 10240 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 5120 mmcblk0p15
179 16 5120 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 36224 mmcblk0p19
179 20 2621440 mmcblk0p20
179 21 434176 mmcblk0p21
179 22 27049472 mmcblk0p22
179 23 16384 mmcblk0p23
179 96 4096 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 128 7776256 mmcblk1
179 129 7775232 mmcblk1p1
253 0 2580508 dm-0
253 1 27049472 dm-1
thanks guys.
Which device?
Scatter file is different for each device, even if they have the same SOC.
Which model is?. It's best if someone has the scatter file for your tablet.
Also, it is possible, but dangerous, take the scatter and a preloader file for a similar device and perform an memory EMMC_BOOT1 & EMMC_USER backup with SP Flash Tool. But it is easy to make a mistake and brick the tablet. This trick only works to make a backup, but as the preloader and scatter file does not correspond to the device, you have to be very careful with using them only to perform the backup and once acomplished, delete these files.
Then with the backup and the Wwr MTK tool you can generate an scatter file for your device.
The EMMC_BOOT1 partition is the device preloader.
Best Regards