the ascend G330 waste 2GB for an internal SD-card, which nobody needs, but /data is just 655 MB, small, if you
like to have lots of apps.
researching on the phone - where partions are mounted i found in /init.rc these lines:
Code:
#/*resize data system cust cache partitions to max size*/
exec /sbin/e2fsck_s -p /dev/block/mmcblk0p15
exec /sbin/resize2fs_s /dev/block/mmcblk0p15
exec /sbin/e2fsck_s -p /dev/block/mmcblk0p16
exec /sbin/resize2fs_s /dev/block/mmcblk0p16
exec /sbin/e2fsck_s -p /dev/block/mmcblk0p17
exec /sbin/resize2fs_s /dev/block/mmcblk0p17
exec /sbin/e2fsck_s -p /dev/block/mmcblk0p18
exec /sbin/resize2fs_s /dev/block/mmcblk0p18
As i understand, if you change the size of a partition and reboot, the filesystem will be adapted!
So someone has just to delete part 18, 19 and recreate 18 and 19 with the desired size, give data up to 2,6 GB!
It would be take just 10 mins!
this is the layout (18 is /data, 19 is internal SD-Card):
Code:
Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes
1 heads, 16 sectors/track, 477184 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 3 20 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 3 41 300 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 41 16681 133120 c Win95 FAT32 (LBA)
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 16681 477184 3684031+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 16897 18432 12288 6a Unknown
/dev/block/mmcblk0p6 18433 18944 4096 46 Unknown
/dev/block/mmcblk0p7 18945 19456 4096 63 GNU HURD or SysV
/dev/block/mmcblk0p8 19457 19840 3072 58 Unknown
/dev/block/mmcblk0p9 19969 20352 3072 4a Unknown
/dev/block/mmcblk0p10 20481 20864 3072 4b Unknown
/dev/block/mmcblk0p11 20993 21504 4096 47 Unknown
/dev/block/mmcblk0p12 21505 22528 8192 48 Unknown
/dev/block/mmcblk0p13 22529 25088 20480 60 Unknown
/dev/block/mmcblk0p14 25089 25600 4096 6c Unknown
/dev/block/mmcblk0p15 25601 50176 196608 83 Linux
/dev/block/mmcblk0p16 50177 60416 81920 83 Linux
/dev/block/mmcblk0p17 60417 125952 524288 83 Linux
/dev/block/mmcblk0p18 125953 207872 655360 83 Linux
/dev/block/mmcblk0p19 207873 477184 2154496 6b Unknown
expert mode:
...
10 00 0 0 0 0 0 0 60794 6144 4b
11 00 0 0 0 0 0 0 68985 8192 47
12 00 0 0 0 0 0 0 77176 16384 48
13 00 0 0 0 0 0 0 93559 40960 60
14 00 0 0 0 0 0 0 134518 8192 6c
15 00 0 0 0 0 0 0 142709 393216 83
16 00 0 0 0 0 0 0 535924 163840 83
17 00 0 0 0 0 0 0 699763 1048576 83
18 00 0 0 0 0 0 0 1748338 1310720 83
19 00 0 0 0 0 0 0 3059057 4308992 6b
so i tried:
Code:
Command (m for help): d
Partition number (1-19): 19
Command (m for help): d
Partition number (1-18): 18
Command (m for help): p
Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes
1 heads, 16 sectors/track, 477184 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 3 20 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 3 41 300 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 41 16681 133120 c Win95 FAT32 (LBA)
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 16681 477184 3684031+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 16897 18432 12288 6a Unknown
/dev/block/mmcblk0p6 18433 18944 4096 46 Unknown
/dev/block/mmcblk0p7 18945 19456 4096 63 GNU HURD or SysV
/dev/block/mmcblk0p8 19457 19840 3072 58 Unknown
/dev/block/mmcblk0p9 19969 20352 3072 4a Unknown
/dev/block/mmcblk0p10 20481 20864 3072 4b Unknown
/dev/block/mmcblk0p11 20993 21504 4096 47 Unknown
/dev/block/mmcblk0p12 21505 22528 8192 48 Unknown
/dev/block/mmcblk0p13 22529 25088 20480 60 Unknown
/dev/block/mmcblk0p14 25089 25600 4096 6c Unknown
/dev/block/mmcblk0p15 25601 50176 196608 83 Linux
/dev/block/mmcblk0p16 50177 60416 81920 83 Linux
/dev/block/mmcblk0p17 60417 125952 524288 83 Linux
Command (m for help): n
First cylinder (16682-477184, default 16682): 125953
[COLOR="Red"]Sector 2015232 is already allocated[/COLOR]
First cylinder (125954-477184, default 125954): 125953
[COLOR="red"]Value is out of range[/COLOR]
First cylinder (125954-477184, default 125954): 125953
[COLOR="red"]Value is out of range[/COLOR]
First cylinder (125954-477184, default 125954):
so I could not recreate part18 with same starting offset - i would loose data.
Any idea why? fdisk is from busybox 1.19. What can i do to archieve my goal?
P.S. when i look to the expert output and recalculate, partitions seem to overlap one block:
expr 699763 + 1048576
1748339
expr 1748338 + 1310720
3059058
Related
Hello:
Here'smy understanding of the internal partitioning scheme (mmcblk0px):
p12 - system
p13 - osh
p14 - cdrom (windows motorola drivers)
p15 - cache
p16 - data
p17 - prebuilt
p18 - emmc/sdcard
Since CM7 doesnt have osh, I thought I'd add destructively add the space on 13 to my data partition. Booted into recovery, loaded up fdisk, and in order to not muck around with the partition scheme, I thought I'd create a 1k partition for 13, and add the space to 16. So i deleted p13-16 and recreated them in fdisk.
Here's my problem: fdisk said it altered the partition table successfully. So I rebooted back to recovery. However, the partition table changes are not showing. It shows the same old table.
So: - can you repartition the internal storage/flash? Is fdisk the tool to use?
Thanks in advance.
i have this question too
i think i messed up my partition table
when I type fdisk -H 1 /dev/block/mmcblk0 it shows:
/dev # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.9 GB, 15914762240 bytes
1 heads, 16 sectors/track, 1942720 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 512 3584 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 513 576 512 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 577 832 2048 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 833 1937856 15496192 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 897 1024 1024 83 Linux
/dev/block/mmcblk0p6 1025 1088 512 83 Linux
/dev/block/mmcblk0p7 1089 1152 512 83 Linux
/dev/block/mmcblk0p8 1153 1280 1024 83 Linux
/dev/block/mmcblk0p9 1281 1536 2048 83 Linux
/dev/block/mmcblk0p10 1537 2560 8192 83 Linux
/dev/block/mmcblk0p11 2561 3584 8192 83 Linux
/dev/block/mmcblk0p12 3585 44544 327680 83 Linux
/dev/block/mmcblk0p13 44545 142848 786432 83 Linux
/dev/block/mmcblk0p14 142849 145408 20480 83 Linux
/dev/block/mmcblk0p15 145409 227328 655360 83 Linux
/dev/block/mmcblk0p16 227329 489472 2097152 83 Linux
/dev/block/mmcblk0p17 489473 533632 353280 83 Linux
/dev/block/mmcblk0p18 533633 1937856 11233792 83 Linux
---------- Post added at 02:11 AM ---------- Previous post was at 01:55 AM ----------
can anyone paste the partition table with the command above?
fdisk -l /dev/block/mmcblk0
not sure if this will help, i've just installed gentop2
atrix adas # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.9 GB, 15914762240 bytes
1 heads, 16 sectors/track, 1942720 cylinders, total 31083520 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1024 8191 3584 83 Linux
/dev/block/mmcblk0p2 8192 9215 512 83 Linux
/dev/block/mmcblk0p3 9216 13311 2048 83 Linux
/dev/block/mmcblk0p4 13312 31005695 15496192 5 Extended
/dev/block/mmcblk0p5 14336 16383 1024 83 Linux
/dev/block/mmcblk0p6 16384 17407 512 83 Linux
/dev/block/mmcblk0p7 17408 18431 512 83 Linux
/dev/block/mmcblk0p8 18432 20479 1024 83 Linux
/dev/block/mmcblk0p9 20480 24575 2048 83 Linux
/dev/block/mmcblk0p10 24576 40959 8192 83 Linux
/dev/block/mmcblk0p11 40960 57343 8192 83 Linux
/dev/block/mmcblk0p12 57344 712703 327680 83 Linux
/dev/block/mmcblk0p13 712704 2285567 786432 83 Linux
/dev/block/mmcblk0p14 2285568 2326527 20480 83 Linux
/dev/block/mmcblk0p15 2326528 3637247 655360 83 Linux
/dev/block/mmcblk0p16 3637248 7831551 2097152 83 Linux
/dev/block/mmcblk0p17 7831552 8538111 353280 83 Linux
/dev/block/mmcblk0p18 8538112 31005695 11233792 83 Linux
Hi
On Huawei U8950D - G600 the interal storage should show as 4GB. However my phone only show 1GB? Is anyone able to confirm if they have experienced the same issue and how they have resolved?
Thank you
I'm interested in the question as well. I also get only 1GB shown.
it has 4 gb of internal memory, but it divided between user and system, so it has 4 gb, but 3 of it belongs to system, you can't use it. info from our russian forum:
Code:
Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes
1 heads, 16 sectors/track, 477184 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 3 20 4d Unknown
/dev/block/mmcblk0p2 3 41 300 45 Unknown
/dev/block/mmcblk0p3 41 16681 133120 c Win95 FAT32 (LBA) /sys_boot
/dev/block/mmcblk0p4 16681 477184 3684031+ 5 Extended
/dev/block/mmcblk0p5 16897 18432 12288 6a Unknown
/dev/block/mmcblk0p6 18433 18944 4096 46 Unknown
/dev/block/mmcblk0p7 18945 19456 4096 63 GNU HURD or SysV /misc
/dev/block/mmcblk0p8 19457 19840 3072 58 Unknown
/dev/block/mmcblk0p9 19969 20352 3072 4a Unknown
/dev/block/mmcblk0p10 20481 20864 3072 4b Unknown
/dev/block/mmcblk0p11 20993 21504 4096 47 Unknown
/dev/block/mmcblk0p12 21505 22528 8192 48 Unknown /boot
/dev/block/mmcblk0p13 22529 25088 20480 60 Unknown /recovery
/dev/block/mmcblk0p14 25089 25600 4096 6c Unknown
/dev/block/mmcblk0p15 25601 50176 196608 83 Linux /cache
/dev/block/mmcblk0p16 50177 60416 81920 83 Linux /cust
/dev/block/mmcblk0p17 60417 191488 1048576 83 Linux /system
/dev/block/mmcblk0p18 191489 338944 1179648 83 Linux /data
/dev/block/mmcblk0p19 338945 477184 1105920 6b Unknown Internal card
bekolya said:
it has 4 gb of internal memory, but it divided between user and system, so it has 4 gb, but 3 of it belongs to system, you can't use it. info from our russian forum:
Code:
Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes
1 heads, 16 sectors/track, 477184 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 3 20 4d Unknown
/dev/block/mmcblk0p2 3 41 300 45 Unknown
/dev/block/mmcblk0p3 41 16681 133120 c Win95 FAT32 (LBA) /sys_boot
/dev/block/mmcblk0p4 16681 477184 3684031+ 5 Extended
/dev/block/mmcblk0p5 16897 18432 12288 6a Unknown
/dev/block/mmcblk0p6 18433 18944 4096 46 Unknown
/dev/block/mmcblk0p7 18945 19456 4096 63 GNU HURD or SysV /misc
/dev/block/mmcblk0p8 19457 19840 3072 58 Unknown
/dev/block/mmcblk0p9 19969 20352 3072 4a Unknown
/dev/block/mmcblk0p10 20481 20864 3072 4b Unknown
/dev/block/mmcblk0p11 20993 21504 4096 47 Unknown
/dev/block/mmcblk0p12 21505 22528 8192 48 Unknown /boot
/dev/block/mmcblk0p13 22529 25088 20480 60 Unknown /recovery
/dev/block/mmcblk0p14 25089 25600 4096 6c Unknown
/dev/block/mmcblk0p15 25601 50176 196608 83 Linux /cache
/dev/block/mmcblk0p16 50177 60416 81920 83 Linux /cust
/dev/block/mmcblk0p17 60417 191488 1048576 83 Linux /system
/dev/block/mmcblk0p18 191489 338944 1179648 83 Linux /data
/dev/block/mmcblk0p19 338945 477184 1105920 6b Unknown Internal card
Click to expand...
Click to collapse
Many thanks for looking into this, however I still wonder why they Huawei done like this?
Thanks again!
Yeah!
bekolya said:
it has 4 gb of internal memory, but it divided between user and system, so it has 4 gb, but 3 of it belongs to system, you can't use it. info from our russian forum:
Code:
Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes
1 heads, 16 sectors/track, 477184 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 3 20 4d Unknown
/dev/block/mmcblk0p2 3 41 300 45 Unknown
/dev/block/mmcblk0p3 41 16681 133120 c Win95 FAT32 (LBA) /sys_boot
/dev/block/mmcblk0p4 16681 477184 3684031+ 5 Extended
/dev/block/mmcblk0p5 16897 18432 12288 6a Unknown
/dev/block/mmcblk0p6 18433 18944 4096 46 Unknown
/dev/block/mmcblk0p7 18945 19456 4096 63 GNU HURD or SysV /misc
/dev/block/mmcblk0p8 19457 19840 3072 58 Unknown
/dev/block/mmcblk0p9 19969 20352 3072 4a Unknown
/dev/block/mmcblk0p10 20481 20864 3072 4b Unknown
/dev/block/mmcblk0p11 20993 21504 4096 47 Unknown
/dev/block/mmcblk0p12 21505 22528 8192 48 Unknown /boot
/dev/block/mmcblk0p13 22529 25088 20480 60 Unknown /recovery
/dev/block/mmcblk0p14 25089 25600 4096 6c Unknown
/dev/block/mmcblk0p15 25601 50176 196608 83 Linux /cache
/dev/block/mmcblk0p16 50177 60416 81920 83 Linux /cust
/dev/block/mmcblk0p17 60417 191488 1048576 83 Linux /system
/dev/block/mmcblk0p18 191489 338944 1179648 83 Linux /data
/dev/block/mmcblk0p19 338945 477184 1105920 6b Unknown Internal card
Click to expand...
Click to collapse
Yeah this guy is right..since you have 4gb internal memory..it is divided to you (user) and to the system..so that some of those softwares and apps on your phone can be downloaded
Does anyone know how to resize this factory setting of internal memory? Some kind of linux script like on other mobile phones.
Or even better, some script that says to system that use mnt/sdcard2 storage (external sd) instead of mnt/sdcard (internal sd)...
lord_mrchi said:
Or even better, some script that says to system that use mnt/sdcard2 storage (external sd) instead of mnt/sdcard (internal sd)...
Click to expand...
Click to collapse
Did you try to change this option in settings? I really don't have problems with memory...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bekolya said:
Did you try to change this option in settings? I really don't have problems with memory...
Click to expand...
Click to collapse
I totally forgot to change that option again after I rooted the phone . Silly me . Tnx mate, who knows for how long will it be before I'll remember to try this again
ps. sorry for my english.
Huawei G6 U10
On Huawei U8950D - G600 the interal storage should show as 4GB. However my phone only show 1GB? Is anyone able to confirm if they have experienced the same issue and how they have resolved?
Thank you[/QUOTE]
In Huawei G6 U10 also facing the same problem....the internal storage showing 4GB,but it is only 1 GB,I think they are cheating costomers...
Thanks and regards
Hi,
can somebody post me internal SD info via fdisk in ADB shell for HTC Desire X? I need partition sizes list.
Only for Desire X with ICS for HBOOT 1.24.
I need output from following commands in adb shell:
Code:
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 473088.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: deleting partitions after 60
Command (m for help):
then type 'u'
Code:
Command (m for help): u
u
Changing display/entry units to sectors
then type 'p'
Code:
Command (m for help): p
p
Disk /dev/block/mmcblk0: 3875 MB, 3875536896 bytes
1 heads, 16 sectors/track, 473088 cylinders, total 7569408 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 40 20 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 41 1128 544 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 1129 10128 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 10129 7569406 3779639 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p6 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p7 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p8 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p9 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p10 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p11 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p12 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p13 131073 139264 4096 4a Unknown
/dev/block/mmcblk0p14 139266 147457 4096 4b Unknown
/dev/block/mmcblk0p15 147459 149506 1024 74 Unknown
/dev/block/mmcblk0p16 149508 163326 6909+ 75 Unknown
/dev/block/mmcblk0p17 163328 163839 256 76 Unknown
/dev/block/mmcblk0p18 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p19 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p20 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p21 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p22 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p23 196096 196607 256 73 Unknown
/dev/block/mmcblk0p24 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p25 200704 2162686 980991+ 83 Linux
/dev/block/mmcblk0p26 2162688 4685822 1261567+ 83 Linux
/dev/block/mmcblk0p27 4685824 5210110 262143+ 83 Linux
/dev/block/mmcblk0p28 5210112 5258606 24247+ 19 Unknown
/dev/block/mmcblk0p29 5258608 5258749 71 90 Unknown
/dev/block/mmcblk0p30 5258751 5259262 256 23 Unknown
/dev/block/mmcblk0p31 5259264 7569407 1155072 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p32 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p33 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p34 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p35 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p36 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p37 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p38 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p39 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p40 131073 139264 4096 4a Unknown
/dev/block/mmcblk0p41 139266 147457 4096 4b Unknown
/dev/block/mmcblk0p42 147459 149506 1024 74 Unknown
/dev/block/mmcblk0p43 149508 163326 6909+ 75 Unknown
/dev/block/mmcblk0p44 163328 163839 256 76 Unknown
/dev/block/mmcblk0p45 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p46 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p47 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p48 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p49 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p50 196096 196607 256 73 Unknown
/dev/block/mmcblk0p51 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p52 200704 2162686 980991+ 83 Linux
/dev/block/mmcblk0p53 2162688 4685822 1261567+ 83 Linux
/dev/block/mmcblk0p54 4685824 5210110 262143+ 83 Linux
/dev/block/mmcblk0p55 5210112 5258606 24247+ 19 Unknown
/dev/block/mmcblk0p56 5258608 5258749 71 90 Unknown
/dev/block/mmcblk0p57 5258751 5259262 256 23 Unknown
/dev/block/mmcblk0p58 5259264 7569407 1155072 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p59 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p60 70131 95130 12500 50 Unknown
Partition table entries are not in disk order
Thats all, just close command with CTRL+C
Please I need that output from working android.
When I look inside /dev/block, I see a lot of partitions on mmcblk0 (and I have confirmed, just to be certain, the combined size of all partitions almost exactly equals the size of mmcblk0 on its own):
Code:
~ # ls mmcblk0*
mmcblk0
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p2
mmcblk0p20
mmcblk0p21
mmcblk0p22
mmcblk0p23
mmcblk0p24
mmcblk0p25
mmcblk0p26
mmcblk0p27
mmcblk0p28
mmcblk0p29
mmcblk0p3
mmcblk0p30
mmcblk0p31
mmcblk0p32
mmcblk0p33
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
What is even more bizarre is I get even more partitions listed when I use fdisk:
Code:
~ # fdisk -l -u /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 2432 MB, 2432696320 bytes
1 heads, 16 sectors/track, 296960 cylinders, total 4751360 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 1000 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1001 1128 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 1129 10128 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 10129 4751358 2370615 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p6 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p7 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p8 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p9 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p10 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p11 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p12 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p13 131073 139264 4096 4a Unknown
/dev/block/mmcblk0p14 139266 147457 4096 4b Unknown
/dev/block/mmcblk0p15 147459 149506 1024 74 Unknown
/dev/block/mmcblk0p16 149508 163326 6909+ 75 Unknown
/dev/block/mmcblk0p17 163328 163839 256 76 Unknown
/dev/block/mmcblk0p18 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p19 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p20 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p21 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p22 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p23 196096 196607 256 73 Unknown
/dev/block/mmcblk0p24 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p25 200704 1835006 817151+ 83 Linux
/dev/block/mmcblk0p26 1835008 3833854 999423+ 83 Linux
/dev/block/mmcblk0p27 3833856 4095998 131071+ 83 Linux
/dev/block/mmcblk0p28 4096000 4452350 178175+ 83 Linux
/dev/block/mmcblk0p29 4452352 4456446 2047+ 33 Unknown
/dev/block/mmcblk0p30 4456448 4504942 24247+ 19 Unknown
/dev/block/mmcblk0p31 4504944 4505085 71 90 Unknown
/dev/block/mmcblk0p32 4505087 4505598 256 23 Unknown
/dev/block/mmcblk0p33 4505600 4702191 98296 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p34 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p35 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p36 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p37 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p38 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p39 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p40 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p41 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p42 131073 139264 4096 4a Unknown
/dev/block/mmcblk0p43 139266 147457 4096 4b Unknown
/dev/block/mmcblk0p44 147459 149506 1024 74 Unknown
/dev/block/mmcblk0p45 149508 163326 6909+ 75 Unknown
/dev/block/mmcblk0p46 163328 163839 256 76 Unknown
/dev/block/mmcblk0p47 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p48 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p49 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p50 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p51 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p52 196096 196607 256 73 Unknown
/dev/block/mmcblk0p53 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p54 200704 1835006 817151+ 83 Linux
/dev/block/mmcblk0p55 1835008 3833854 999423+ 83 Linux
/dev/block/mmcblk0p56 3833856 4095998 131071+ 83 Linux
/dev/block/mmcblk0p57 4096000 4452350 178175+ 83 Linux
/dev/block/mmcblk0p58 4452352 4456446 2047+ 33 Unknown
/dev/block/mmcblk0p59 4456448 4504942 24247+ 19 Unknown
/dev/block/mmcblk0p60 4504944 4505085 71 90 Unknown
Partition table entries are not in disk order
The thing is, those extra partitions don't seem to be in use. Running mount only lists the following partitions as mounted somewhere (irrelevant mounts excluded from the output)
Code:
/dev/block/mmcblk0p25 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p28 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p30 /devlog ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
What are all these extra partitions for?
Is this specific to my particular device (HTC One V, with firmware for Cricket Wireless), or do all Android devices have this sheer number partitions?
I'm using a Xiaomi Redmi Note 9S with MIUI 11.0.10 which is Android 10. There seems to be some bug with root that can soft-brick your phone. When you boot into TWRP, it can no longer mount the System partition - pressing it, will do nothing.
So I connect via adb to the phone. It's root adb and I am root according to "whoami".
cat /proc/partitions output:
Code:
~ # cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
8 0 120479744 sda
8 1 8 sda1
8 2 32768 sda2
8 3 1024 sda3
8 4 512 sda4
8 5 512 sda5
8 6 131072 sda6
8 7 1048576 sda7
8 8 131072 sda8
8 9 131072 sda9
8 10 64 sda10
8 11 64 sda11
8 12 16384 sda12
8 13 393216 sda13
8 14 393216 sda14
8 15 16384 sda15
259 0 8192 sda16
259 1 8388608 sda17
259 2 109786956 sda18
8 16 8192 sdb
8 17 7168 sdb1
8 18 128 sdb2
8 64 4194304 sde
8 65 512 sde1
8 66 4096 sde2
8 67 512 sde3
8 68 262144 sde4
8 69 1024 sde5
8 70 4096 sde6
8 71 32768 sde7
8 72 8192 sde8
8 73 32768 sde9
8 74 512 sde10
8 75 512 sde11
8 76 512 sde12
8 77 128 sde13
8 78 64 sde14
8 79 2048 sde15
259 3 2048 sde16
259 4 512 sde17
259 5 4096 sde18
259 6 512 sde19
259 7 262144 sde20
259 8 1024 sde21
259 9 4096 sde22
259 10 32768 sde23
259 11 8192 sde24
259 12 32768 sde25
259 13 512 sde26
259 14 512 sde27
259 15 512 sde28
259 16 128 sde29
259 17 64 sde30
259 18 2048 sde31
259 19 2048 sde32
259 20 4 sde33
259 21 1024 sde34
259 22 256 sde35
259 23 8192 sde36
259 24 33424 sde37
259 25 4 sde38
259 26 1024 sde39
259 27 8192 sde40
259 28 2048 sde41
259 29 65536 sde42
259 30 128 sde43
259 31 32 sde44
259 32 32 sde45
259 33 512 sde46
259 34 28 sde47
259 35 512 sde48
259 36 1024 sde49
259 37 64 sde50
259 38 131072 sde51
259 39 24576 sde52
259 40 64 sde53
259 41 24576 sde54
259 42 131072 sde55
8 32 8192 sdc
8 33 7168 sdc1
8 34 128 sdc2
8 80 131072 sdf
8 81 104 sdf1
8 82 2048 sdf2
8 83 2048 sdf3
8 84 10240 sdf4
8 85 128 sdf5
8 48 131072 sdd
8 49 104 sdd1
8 50 128 sdd2
8 51 1024 sdd3
253 0 934804 dm-0
253 1 1403780 dm-1
253 2 2356452 dm-2
df -h output after flashing new .EU ROM - this is how it should look like:
Code:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 2.7G 752.0K 2.7G 0% /dev
tmpfs 2.7G 0 2.7G 0% /mnt
tmpfs 2.7G 0 2.7G 0% /apex
tmpfs 2.7G 6.4M 2.7G 0% /tmp
/dev/block/sda18 104.7G 14.5G 90.2G 14% /data
/dev/block/sda18 104.7G 14.5G 90.2G 14% /sdcard
/dev/block/dm-1 1.3G 1.2G 33.4M 97% /vendor
/dev/block/sda13 356.0M 428.0K 328.7M 0% /cache
/dev/block/dm-2 2.2G 2.1G 109.5M 95% /system_root
/dev/block/dm-2 2.2G 2.1G 109.5M 95% /system
df -h output - what it actually looks like after soft-brick:
Code:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 2.7G 752.0K 2.7G 0% /dev
tmpfs 2.7G 0 2.7G 0% /mnt
tmpfs 2.7G 0 2.7G 0% /apex
tmpfs 2.7G 2.6M 2.7G 0% /tmp
/dev/block/sda13 356.0M 1.1M 328.0M 0% /cache
/dev/block/sda18 104.7G 15.3G 89.4G 15% /data
/dev/block/sda18 104.7G 15.3G 89.4G 15% /sdcard
Trying to mount the "dm" devices, you can mount dm-0 and dm-1, but dm-2 (which should be system) fails:
Code:
~ # mount -r /dev/block/dm-2 /fufu/ -v -t ext4
mount: mounting /dev/block/dm-2 on /fufu/ failed: Read-only file system
DM-verity is disabled:
Code:
adb enable-verity
verity not enabled - ENG build
e2fsck fails because it claims to have no write access:
Code:
~ # e2fsck /dev/block/dm-2
e2fsck 1.44.4 (18-Aug-2018)
e2fsck: Operation not permitted while trying to open /dev/block/dm-2
You must have r/w access to the filesystem or be root
~ # whoami
root
File system is still intact. You can "dd" the dm-2 partition to some other place and access it via Linux or an ext4 viewer on Windows (https://www.diskinternals.com/linux-reader/ for example). You can also do it via adb: "adb pull /dev/block/dm-2"
When mounting (see above) and then looking in the log (dmesg):
Code:
<6>[ 1057.614782] EXT4-fs (dm-2): INFO: recovery required on readonly filesystem
<3>[ 1057.614797] EXT4-fs (dm-2): write access unavailable, cannot proceed
tune2fs for dm-1 and dm-2:
Code:
~ # tune2fs -l /dev/block/dm-1
tune2fs 1.44.4 (18-Aug-2018)
Filesystem volume name: vendor
Last mounted on: <not available>
Filesystem UUID: 6d16bab1-58d9-3c5d-8f14-f608f924affd
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode filetype extent sparse_super large_file uninit_bg
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem OS type: Linux
Inode count: 87824
Block count: 350944
Reserved block count: 0
Free blocks: 12643
Free inodes: 84860
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 87
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 7984
Inode blocks per group: 499
Last mount time: n/a
Last write time: Thu Jan 1 08:00:00 1970
Mount count: 0
Maximum mount count: -1
Last checked: Thu Jan 1 08:00:00 1970
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
~ # tune2fs -l /dev/block/dm-2
tune2fs 1.44.4 (18-Aug-2018)
Filesystem volume name: /
Last mounted on: /
Filesystem UUID: bbcb9ad2-245d-035f-a549-7d500312efe1
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode filetype needs_recovery extent sparse_super large_file uninit_bg
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem OS type: Linux
Inode count: 147456
Block count: 589113
Reserved block count: 0
Free blocks: 32124
Free inodes: 142168
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 143
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Last mount time: Sun Aug 2 03:07:27 2020
Last write time: Thu Jan 1 08:00:00 1970
Mount count: 4
Maximum mount count: -1
Last checked: Thu Jan 1 08:00:00 1970
Check interval: 0 (<none>)
Lifetime writes: 692 kB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
-> dm-2 has a flag called "needs_recovery" set.
- I can run e2fsck on the dd exported image of dm-2 which recovers it fine, but I cannot dd it back to dm-2 - again no write access:
Code:
~ # dd if=/sdcard/systemfile.img of=/dev/block/dm-2
dd: writing '/dev/block/dm-2': Operation not permitted
1+0 records in
0+0 records out
0 bytes (0B) copied, 0.000131 seconds, 0B/s
Ideas how I can write anything to /dev/block/dm-2 (I also cannot change anything via tune2fs to the other dm devices).
Thank you
@herlgl You should take a look at this or this. Good luck!
have you solved? how?