Hey guys,
Here is the mountpoint information for Xperia M I am still figuring out which of these goes for which partitions I will update if I find
Code:
PERM UID GID DATE PATH
lrwxrwxrwx root root 1970-07-11 15:19 FOTAKernel -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-07-11 15:19 LTALabel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-07-11 15:19 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-07-11 15:19 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-07-11 15:19 alt -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-07-11 15:19 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-07-11 15:19 cache -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-07-11 15:19 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-07-11 15:19 modem -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-07-11 15:19 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-07-11 15:19 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-07-11 15:19 persist -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-07-11 15:19 ramdump -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-07-11 15:19 rpm -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-07-11 15:19 s1sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-07-11 15:19 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-07-11 15:19 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-07-11 15:19 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-07-11 15:19 system -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-07-11 15:19 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-07-11 15:19 userdata -> /dev/block/mmcblk0p27
Huge thanks to @mbc07
Code:
major minor #blocks name
179 0 3866624 mmcblk0
179 1 2048 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 128 mmcblk0p8
179 9 256 mmcblk0p9
179 10 256 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 512 mmcblk0p14
179 15 512 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 20480 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 3072 mmcblk0p19
179 20 3072 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 5120 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 1228800 mmcblk0p25
179 26 256000 mmcblk0p26
179 27 2183151 mmcblk0p27
179 32 7822336 mmcblk1
179 33 7821312 mmcblk1p1
Just use ls -l /dev/block/platform/msm_sdcc.1/by-name
Layout:
Code:
PERM UID GID DATE PATH
lrwxrwxrwx root root 1970-07-11 15:19 FOTAKernel -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-07-11 15:19 LTALabel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-07-11 15:19 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-07-11 15:19 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-07-11 15:19 alt -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-07-11 15:19 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-07-11 15:19 cache -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-07-11 15:19 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-07-11 15:19 modem -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-07-11 15:19 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-07-11 15:19 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-07-11 15:19 persist -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-07-11 15:19 ramdump -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-07-11 15:19 rpm -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-07-11 15:19 s1sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-07-11 15:19 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-07-11 15:19 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-07-11 15:19 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-07-11 15:19 system -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-07-11 15:19 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-07-11 15:19 userdata -> /dev/block/mmcblk0p27
Here you are a bit more information.
Also I have dumps of all these partitions and GPT backup.
If someone need to restore something – send PM (C1905 btw).
Code:
parted /dev/block/mmcblk0
print
Number Start End Size File system Name
1 131kB 2228kB 2097kB TA
2 2228kB 2359kB 131kB sbl1
3 2359kB 2621kB 262kB sbl2
4 2621kB 2884kB 262kB s1sbl2
5 2884kB 3408kB 524kB sbl3
6 3408kB 3932kB 524kB aboot
7 3932kB 4456kB 524kB tz
8 4456kB 4588kB 131kB alt_sbl1
9 4588kB 4850kB 262kB alt_sbl2
10 4850kB 5112kB 262kB alt_s1sbl2
11 5112kB 5636kB 524kB alt_sbl3
12 5636kB 6160kB 524kB alt_aboot
13 6160kB 6685kB 524kB alt_tz
14 6685kB 7209kB 524kB rpm
15 7209kB 7733kB 524kB alt_rpm
16 8389kB 25.2MB 16.8MB ext4 LTALabel
17 25.2MB 46.1MB 21.0MB boot
18 46.1MB 113MB 67.1MB fat16 modem
19 113MB 116MB 3146kB modemst1
20 117MB 121MB 3146kB modemst2
21 122MB 125MB 3146kB fsg
22 125MB 130MB 5243kB ramdump
23 130MB 147MB 16.8MB FOTAKernel
24 147MB 151MB 4194kB ext2 persist
25 151MB 1514MB 1363MB ext4 system
26 1514MB 1724MB 210MB ext4 cache
27 1724MB 3909MB 2185MB ext4 userdata
---------------
gdisk /dev/block/mmcblk0
p
Disk /dev/block/mmcblk0: 7733248 sectors, 3.7 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 27 entries
First usable sector is 34, last usable sector is 7733214
Partitions will be aligned on 256-sector boundaries
Total free space is 103902 sectors (50.7 MiB)
Number Start (sector) End (sector) Size Code Name
1 256 4351 2.0 MiB FFFF TA
2 4352 4607 128.0 KiB FFFF sbl1
3 4608 5119 256.0 KiB FFFF sbl2
4 5120 5631 256.0 KiB FFFF s1sbl2
5 5632 6655 512.0 KiB FFFF sbl3
6 6656 7679 512.0 KiB FFFF aboot
7 7680 8703 512.0 KiB FFFF tz
8 8704 8959 128.0 KiB FFFF alt_sbl1
9 8960 9471 256.0 KiB FFFF alt_sbl2
10 9472 9983 256.0 KiB FFFF alt_s1sbl2
11 9984 11007 512.0 KiB FFFF alt_sbl3
12 11008 12031 512.0 KiB FFFF alt_aboot
13 12032 13055 512.0 KiB FFFF alt_tz
14 13056 14079 512.0 KiB FFFF rpm
15 14080 15103 512.0 KiB FFFF alt_rpm
16 16384 49151 16.0 MiB 8300 LTALabel
17 49152 90111 20.0 MiB FFFF boot
18 90112 221183 64.0 MiB 0700 modem
19 221184 227327 3.0 MiB FFFF modemst1
20 229376 235519 3.0 MiB FFFF modemst2
21 237568 243711 3.0 MiB FFFF fsg
22 243712 253951 5.0 MiB FFFF ramdump
23 253952 286719 16.0 MiB FFFF FOTAKernel
24 286720 294911 4.0 MiB 8300 persist
25 294912 2957311 1.3 GiB 8300 system
26 2957312 3366911 200.0 MiB 8300 cache
27 3366912 7634910 2.0 GiB 8300 userdata
---------------
gdisk /dev/block/mmcblk0
x
o
Disk size is 7733248 sectors (3.7 GiB)
MBR disk identifier: 0x00000000
MBR partitions:
Number Boot Start Sector End Sector Status Code
1 1 7733247 primary 0xEE
---------------
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 3959 MB, 3959422976 bytes
95 heads, 61 sectors/track, 1334 cylinders
Units = cylinders of 5795 * 512 = 2967040 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1335 3866623+ ee EFI GPT
---------------
df
Filesystem Size Used Free Blksize
/dev 430.6M 128.0K 430.4M 4096
/sys/fs/cgroup 430.6M 12.0K 430.5M 4096
/mnt/asec 430.6M 0.0K 430.6M 4096
/mnt/obb 430.6M 0.0K 430.6M 4096
/mnt/fuse 430.6M 0.0K 430.6M 4096
/system 1.3G 374.4M 907.4M 4096
/data 2.0G 1.5G 555.2M 4096
/cache 197.0M 68.2M 128.8M 4096
/persist 3.9M 84.0K 3.8M 4096
/lta-label 15.8M 4.1M 11.7M 4096
/firmware 64.0M 44.1M 19.9M 16384
/mnt/shell/emulated 2.0G 1.5G 555.2M 4096
/storage/emulated/legacy 2.0G 1.5G 555.2M 4096
/mnt/media_rw/sdcard1 14.8G 11.6G 3.3G 8192
/storage/sdcard1 14.8G 11.6G 3.3G 8192
---------------
mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/LTALabel /lta-label ext4 ro,seclabel,nosuid,nodev,noexec,noatime,nobarrier,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:33 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,cod
epage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Here's the T-Mobile USA 10H Stock Rooted ROM that I'm porting to the H815 EU unlocked G4. I basically reversed the process of my previous port of H815 to H811.
Prerequisite:
**Be on H815 EU unlocked
**Want to use this for T-Mobile USA or any carrier. (Might have to add apn)
**Have TWRP installed to flash this.
Bugs: I haven't been able to test this as I don't own the H815 EU.
***????
Installation:
Step 1: Backup First
Step 2: Full Wipe
Step 3: Flash G4-H815-TMO-10H-STOCK-ROOTED-ROM.zip
Step 4: Flash G4-H815-TMO-PATCH.zip
Step 5: Reboot
Important to flash Step 3 and Step back to back.
Downloads:
Flash 1st:
G4-H815-TMO-10H-STOCK-ROOTED-ROM.zip
Flash 2nd
G4-H815-TMO-PATCH.zip
Optional to Flash if your on T-Mobile USA or US others :
G4-USA-APN.zip
XDA:DevDB Information
[ROM] LG G4 H815 T-mobile 10H Port, ROM for the LG G4
Contributors
MicroMod777
ROM OS Version: 5.1.x Lollipop
Version Information
Status: Testing
Created 2015-08-07
Last Updated 2015-08-06
ok thx, but why?
flooi said:
ok thx, but why?
Click to expand...
Click to collapse
It was asked for a while back for from the USA guys that bought the H815. It it works you'll be able to probaby wifi call on T-Mobile.
Sent from my LG-H811 using Tapatalk
Anybody with h815 tried it? Any difference between 10c to this one? I have the international version but afraid to install this..
Thanks dev for this port..i will flash it after some feedback from other users
Has it been debloated? Also, the end result might be easier if you just create a flashable wificalling.zip that has the necessary files for using tmous wifi calling on the H815.
galza said:
Anybody with h815 tried it? Any difference between 10c to this one? I have the international version but afraid to install this..
Thanks dev for this port..i will flash it after some feedback from other users
Click to expand...
Click to collapse
Are you in the USA with T-Mobile? If so, then this is for you.
barcodelinux said:
Has it been debloated? Also, the end result might be easier if you just create a flashable wificalling.zip that has the necessary files for using tmous wifi calling on the H815.
Click to expand...
Click to collapse
OP says stock rom, not debloated. Not sure if possible or what files to use for wifi calling as its integrated into settings. For me, doing whole rom is 10000x easier.
Will this work on a non-US H815? I'm in the UK currently running 10C, but if there are optimisations/ changes between 10C and 10H I'd be keen to get in on the magic
When flashing the ROM in step 3, I get:
"Extracting system & Boot
Updating partition details...
E:Unable to mount '/system'
...done
---------- Post added at 01:30 PM ---------- Previous post was at 01:02 PM ----------
I think the partitions might be different on each device. Here's the output of df of the H815:
Filesystem Size Used Free Blksize
/dev 1.37G 96.00K 1.37G 4096
/sys/fs/cgroup 1.37G 12.00K 1.37G 4096
/mnt/asec 1.37G 0.00K 1.37G 4096
/mnt/obb 1.37G 0.00K 1.37G 4096
/system 3.92G 3.00G 938.40M 4096
/cache 1.17G 32.62M 1.13G 4096
/data 22.70G 21.73G 994.51M 4096
/persist 27.48M 64.00K 27.42M 4096
/firmware 85.95M 74.77M 11.19M 16384
/sns 3.86M 60.00K 3.80M 4096
/persist-lg 3.86M 584.00K 3.29M 4096
/mpt 27.48M 9.26M 18.22M 4096
/cust 247.97M 7.64M 240.33M 4096
/mnt/shell/emulated 22.70G 21.73G 994.51M 4096
/storage/emulated/legacy 22.70G 21.73G 994.51M 4096
/storage/emulated 1.38G 0.00K 1.38G 4096
/mnt/media_rw/external_SD 119.05G 51.99G 67.06G 131072
/mnt/secure/asec 119.05G 51.99G 67.06G 131072
/storage/external_SD 119.05G 51.99G 67.06G 131072
/storage/emulated/0 22.70G 21.73G 994.51M 4096
/storage/emulated/0/Android/obb 22.70G 21.73G 994.51M 4096
/storage/emulated/legacy 22.70G 21.73G 994.51M 4096
/storage/emulated/legacy/Android/obb 22.70G 21.73G 994.51M 4096
---------- Post added at 01:37 PM ---------- Previous post was at 01:30 PM ----------
And from mount:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1437396k,nr_inodes=359349,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1437396k,nr_inodes=359349,mode=750,gid=1000 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=1437396k,nr_inodes=359349,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=1437396k,nr_inodes=359349,mode=755,gid=1000 0 0
/mnt/pstore /mnt/pstore pstore rw,relatime 0 0
/dev/block/bootdevice/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,resuid=1000,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/modem /firmware vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/sns /sns ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/drm /persist-lg ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/mpt /mpt ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/f9824900.sdhci/by-name/cust /cust ext4 ro,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,relatime,uid=1023,gid=1023,derive=legacy 0 0
/data/media /storage/emulated/legacy sdcardfs rw,nosuid,relatime,uid=1023,gid=1023,derive=legacy 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,size=1443540k,nr_inodes=360885,mode=050,gid=1028 0 0
/dev/block/vold/179:65 /mnt/media_rw/external_SD exfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro,discard,readahead_kb=512 0 0
/dev/block/vold/179:65 /mnt/secure/asec exfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro,discard,readahead_kb=512 0 0
/mnt/media_rw/external_SD /storage/external_SD sdcardfs rw,nosuid,relatime,uid=1023,gid=1023,derive=unified 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,relatime,uid=1023,gid=1023,derive=legacy 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,relatime,uid=1023,gid=1023,derive=legacy 0 0
/data/media /storage/emulated/legacy sdcardfs rw,nosuid,relatime,uid=1023,gid=1023,derive=legacy 0 0
/data/media /storage/emulated/legacy/Android/obb sdcardfs rw,nosuid,relatime,uid=1023,gid=1023,derive=legacy 0 0
barcodelinux said:
When flashing the ROM in step 3, I get:
"Extracting system & Boot
Updating partition details...
E:Unable to mount '/system'
...done
---------- Post added at 01:30 PM ---------- Previous post was at 01:02 PM ----------
I think the partitions might be different on each device. Here's the output of df of the H815:
Filesystem Size Used Free Blksize
/dev 1.37G 96.00K 1.37G 4096
/sys/fs/cgroup 1.37G 12.00K 1.37G 4096
/mnt/asec 1.37G 0.00K 1.37G 4096
/mnt/obb 1.37G 0.00K 1.37G 4096
/system 3.92G 3.00G 938.40M 4096
/cache 1.17G 32.62M 1.13G 4096
/data 22.70G 21.73G 994.51M 4096
/persist 27.48M 64.00K 27.42M 4096
/firmware 85.95M 74.77M 11.19M 16384
/sns 3.86M 60.00K 3.80M 4096
/persist-lg 3.86M 584.00K 3.29M 4096
/mpt 27.48M 9.26M 18.22M 4096
/cust 247.97M 7.64M 240.33M 4096
/mnt/shell/emulated 22.70G 21.73G 994.51M 4096
/storage/emulated/legacy 22.70G 21.73G 994.51M 4096
/storage/emulated 1.38G 0.00K 1.38G 4096
/mnt/media_rw/external_SD 119.05G 51.99G 67.06G 131072
/mnt/secure/asec 119.05G 51.99G 67.06G 131072
/storage/external_SD 119.05G 51.99G 67.06G 131072
/storage/emulated/0 22.70G 21.73G 994.51M 4096
/storage/emulated/0/Android/obb 22.70G 21.73G 994.51M 4096
/storage/emulated/legacy 22.70G 21.73G 994.51M 4096
/storage/emulated/legacy/Android/obb 22.70G 21.73G 994.51M 4096
---------- Post added at 01:37 PM ---------- Previous post was at 01:30 PM ----------
And from mount:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1437396k,nr_inodes=359349,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1437396k,nr_inodes=359349,mode=750,gid=1000 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=1437396k,nr_inodes=359349,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=1437396k,nr_inodes=359349,mode=755,gid=1000 0 0
/mnt/pstore /mnt/pstore pstore rw,relatime 0 0
/dev/block/bootdevice/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,resuid=1000,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/modem /firmware vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/sns /sns ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/drm /persist-lg ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/mpt /mpt ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/f9824900.sdhci/by-name/cust /cust ext4 ro,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,relatime,uid=1023,gid=1023,derive=legacy 0 0
/data/media /storage/emulated/legacy sdcardfs rw,nosuid,relatime,uid=1023,gid=1023,derive=legacy 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,size=1443540k,nr_inodes=360885,mode=050,gid=1028 0 0
/dev/block/vold/179:65 /mnt/media_rw/external_SD exfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro,discard,readahead_kb=512 0 0
/dev/block/vold/179:65 /mnt/secure/asec exfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro,discard,readahead_kb=512 0 0
/mnt/media_rw/external_SD /storage/external_SD sdcardfs rw,nosuid,relatime,uid=1023,gid=1023,derive=unified 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,relatime,uid=1023,gid=1023,derive=legacy 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,relatime,uid=1023,gid=1023,derive=legacy 0 0
/data/media /storage/emulated/legacy sdcardfs rw,nosuid,relatime,uid=1023,gid=1023,derive=legacy 0 0
/data/media /storage/emulated/legacy/Android/obb sdcardfs rw,nosuid,relatime,uid=1023,gid=1023,derive=legacy 0 0
Click to expand...
Click to collapse
Can you do this and post your partition table:
adb shell
su
ls -l /dev/block/platform/f9824900.sdhci/by-name
Sent from my LG-H811 using Tapatalk
MicroMod777 said:
Can you do this and post your partition table:
adb shell
su
ls -l /dev/block/platform/f9824900.sdhci/by-name
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
lrwxrwxrwx root root 2015-02-26 17:31 DDR -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-02-26 17:31 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-02-26 17:31 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-02-26 17:31 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-02-26 17:31 boot -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2015-02-26 17:31 cache -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 2015-02-26 17:31 cust -> /dev/block/mmcblk0p48
lrwxrwxrwx root root 2015-02-26 17:31 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-02-26 17:31 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-02-26 17:31 drm -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 2015-02-26 17:31 eksst -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-02-26 17:31 encrypt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-02-26 17:31 factory -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2015-02-26 17:31 fota -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2015-02-26 17:31 fsc -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-02-26 17:31 fsg -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-02-26 17:31 grow -> /dev/block/mmcblk0p51
lrwxrwxrwx root root 2015-02-26 17:31 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-02-26 17:31 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-02-26 17:31 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-02-26 17:31 laf -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-02-26 17:31 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-02-26 17:31 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-02-26 17:31 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-02-26 17:31 modemst1 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-02-26 17:31 modemst2 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-02-26 17:31 mpt -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2015-02-26 17:31 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-02-26 17:31 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-02-26 17:31 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-02-26 17:31 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-02-26 17:31 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-02-26 17:31 raw_resources -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 2015-02-26 17:31 raw_resourcesbak -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 2015-02-26 17:31 rct -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-02-26 17:31 recovery -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2015-02-26 17:31 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-02-26 17:31 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-02-26 17:31 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-02-26 17:31 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-02-26 17:31 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-02-26 17:31 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-02-26 17:31 sec -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-02-26 17:31 sns -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 2015-02-26 17:31 spare1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-02-26 17:31 spare2 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-02-26 17:31 ssd -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-02-26 17:31 system -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 2015-02-26 17:31 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-02-26 17:31 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-02-26 17:31 userdata -> /dev/block/mmcblk0p50
@MicroMod777
I guess I could flash the system.img and boot.img from fastboot just to see if they will boot on the H815 later tonight when I get home. But that doesn't fix the updater-script.
Thoughts??
barcodelinux said:
@MicroMod777
I guess I could flash the system.img and boot.img from fastboot just to see if they will boot on the H815 later tonight when I get home. But that doesn't fix the updater-script.
Thoughts??
Click to expand...
Click to collapse
I fixed rom but need to upload it.
Sent from my LG-H811 using Tapatalk
Here's rom with fixed script thanks to barcodelinux:
https://www.androidfilehost.com/?fid=24052804347793245
MicroMod777 said:
Here's rom with fixed script thanks to barcodelinux:
https://www.androidfilehost.com/?fid=24052804347793245
Click to expand...
Click to collapse
@MicroMod777 still waiting for any replies from you with regards to my post in 1 click root method... have spent 3 hours and got nowhere... any help is much appreciated....
When trying to flash the ROM, I get:
Delete Old System
Mounting system
Formatting system
Extracting System
Extracting Boot
E:Unable to mount '/system'
...done
When installing the patch file, I get:
Installing Patches...
Installation complete!
Updating partition details...
E:Unable to mount '/system'
...done
When installing the APN file, I get:
Installing files...
Installation complete!
Updating partition details...
E:Unable to mount '/system'
...done
Do get same error with camera mod?
http://forum.xda-developers.com/g4/themes-apps/root-60fps-camera-100-photo-quality-t3129460
Sent from my LG-H811 using Tapatalk
MicroMod777 said:
Do get same error with camera mod?
http://forum.xda-developers.com/g4/themes-apps/root-60fps-camera-100-photo-quality-t3129460
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
No. I flashed the 60fps mood over the H815 stock rom a few weeks ago.
barcodelinux said:
No. I flashed the 60fps mood over the H815 stock rom a few weeks ago.
Click to expand...
Click to collapse
Odd as I used the same info in the camera script for the patch.
Sent from my LG-H811 using Tapatalk
MicroMod777 said:
Odd as I used the same info in the camera script for the patch.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
I looked at autoprime's updater-script from here.
It uses the
Code:
package_extract_file("file.name", "/path/to/extract");
command instead of the
Code:
package_extract_dir("file.name", "/path/to/extract");
My takeaway is that since you are trying to flash system.img, which is a file, you have to use the package_extract_file command. If we had a .zip file with a compressed directory named "system", you would then use the package_extract_dir command.
Since I already have the files on my Linux lappy, I will edit the updater-script and let you know how it goes.
barcodelinux said:
I looked at autoprime's updater-script from here.
It uses the
Code:
package_extract_file("file.name", "/path/to/extract");
command instead of the
Code:
package_extract_dir("file.name", "/path/to/extract");
My takeaway is that since you are trying to flash system.img, which is a file, you have to use the package_extract_file command. If we had a .zip file with a compressed directory named "system", you would then use the package_extract_dir command.
Since I already have the files on my Linux lappy, I will edit the updater-script and let you know how it goes.
Click to expand...
Click to collapse
Let me know if works! Thanks
Sent from my LG-H811 using Tapatalk
Tried two offical Xiaomi fastboot Pie images, and system.img doesn't flash. Other smaller in size system images I flashed to see what would happen do go through, but they don't work. Pie image is 2.1 GB. Other partitions are all flashed.
Each attempt via Xiaomi flash tool ends with: Chunk data size exceeds partition size.
Log:
$fastboot -s 08f97d930705 flash system_a C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\daisy_global_images_V10.0.10.0.PDLMIXM_9.0\\images\system.img ||
[10:26:06 AM 08f97d930705]:target reported max download size of 534773760 bytes
[10:26:06 AM 08f97d930705]:sending sparse 'system_a' 1/3 (462332 KB)...
[10:26:06 AM 08f97d930705]KAY [ 59.062s]
[10:26:06 AM 08f97d930705]:writing 'system_a' 1/3...
[10:26:06 AM 08f97d930705]:error:FAILED (remote: Chunk data size exceeds partition size)
[10:26:06 AM 08f97d930705]:flashSuccess False
Fastboot flash_all.bat gives:
fastboot getvar product 2>&1 | findstr /r /c:"^product: *d
aisy" ||
The system cannot find message text for message number 0x8 in the message file f
or System.
Fastboot flash system sends sparse chunks and gives:
data too large
So, what gives? Any ideas greatly appreciated.
MarkR7 said:
Tried two offical Xiaomi fastboot Pie images, and system.img doesn't flash. Other smaller in size system images I flashed to see what would happen do go through, but they don't work. Pie image is 2.1 GB. Other partitions are all flashed.
Each attempt via Xiaomi flash tool ends with: Chunk data size exceeds partition size.
Log:
$fastboot -s 08f97d930705 flash system_a C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\daisy_global_images_V10.0.10.0.PDLMIXM_9.0\\images\system.img ||
[10:26:06 AM 08f97d930705]:target reported max download size of 534773760 bytes
[10:26:06 AM 08f97d930705]:sending sparse 'system_a' 1/3 (462332 KB)...
[10:26:06 AM 08f97d930705]KAY [ 59.062s]
[10:26:06 AM 08f97d930705]:writing 'system_a' 1/3...
[10:26:06 AM 08f97d930705]:error:FAILED (remote: Chunk data size exceeds partition size)
[10:26:06 AM 08f97d930705]:flashSuccess False
Fastboot flash_all.bat gives:
fastboot getvar product 2>&1 | findstr /r /c:"^product: *d
aisy" ||
The system cannot find message text for message number 0x8 in the message file f
or System.
Fastboot flash system sends sparse chunks and gives:
data too large
So, what gives? Any ideas greatly appreciated.
Click to expand...
Click to collapse
It could be an error from the tool or maybe you need to delete some logs that can cause a conflict anyway did you try using just fastboot command to flash just system? if not trying finding which is your current slot and then flash it directly to it.
I guess size image support is around 2,5GB.
SubwayChamp said:
It could be an error from the tool or maybe you need to delete some logs that can cause a conflict anyway did you try using just fastboot command to flash just system? if not trying finding which is your current slot and then flash it directly to it.
I guess size image support is around 2,5GB.
Click to expand...
Click to collapse
I direct fastboot flashed system multiple times, also flash all bat, I also restored Oeeo from TWRP backup multiple timea, Oreo working fine, now that I think of it, Mi Flash tool seems to be from 2017 and it seems old to me, I got it from their link somewhere, but could the newest one be that old? Need to check that.
MarkR7 said:
I direct fastboot flashed system multiple times, also flash all bat, I also restored Oeeo from TWRP backup multiple timea, Oreo working fine, now that I think of it, Mi Flash tool seems to be from 2017 and it seems old to me, I got it from their link somewhere, but could the newest one be that old? Need to check that.
Click to expand...
Click to collapse
This seems to be the latest stable version https://c.mi.com/thread-1329226-1-0.html and although this is newer use the tool from 2017 but ever worked for me https://xiaomifirmware.com/downloads/mif anyway you have too the option to flash through edl
I think someone had a problem due to fastboot being too old.
The partition should be 2.5Gb so unless you or someone else resized partitions, it should be large enough.
I can use fdisk from a running phone to print partition info. If you can't boot, perhaps you can check from twrp?
Code:
# fdisk /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Command (m for help): p
Disk /dev/block/mmcblk0: 122142720 sectors, 2296M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 60 entries
First usable sector is 34, last usable sector is 122142686
Number Start (sector) End (sector) Size Name
1 34 49 8192 fsc
2 50 65 8192 ssd
3 66 81 8192 dpo
4 82 113 16384 sec
5 114 145 16384 bk1
6 146 185 20480 bk2
7 186 249 32768 DDR
8 250 313 32768 limits
9 314 377 32768 config
10 378 505 65536 bk3
11 506 761 128K lksecapp
12 762 1017 128K lksecappbak
13 1018 1529 256K devcfg_a
14 1530 2041 256K devcfg_b
15 2042 2553 256K apdp
16 2554 3065 256K msadp
17 3066 4089 512K sbl1_a
18 4090 5113 512K sbl1_b
19 5114 6137 512K rpm_a
20 6138 7161 512K rpm_b
21 7162 8185 512K mota
22 8186 9209 512K keystore
23 9210 10233 512K syscfg
24 10234 12281 1024K cmnlib_a
25 12282 14329 1024K cmnlib_b
26 14330 16377 1024K cmnlib64_a
27 16378 18425 1024K cmnlib64_b
28 18426 20473 1024K keymaster_a
29 20474 22521 1024K keymaster_b
30 22522 24569 1024K misc
31 24570 26617 1024K aboot_a
32 26618 28665 1024K aboot_b
33 28666 30713 1024K dip
34 30714 32761 1024K bk4
35 32762 36857 2048K tz_a
36 36858 40953 2048K tz_b
37 40954 49145 4096K mcfg
38 49146 65529 8192K devinfo
39 65530 81913 8192K fsg
40 81914 98297 8192K modemst1
41 98298 114681 8192K modemst2
42 114682 131065 8192K bk5
43 131066 163833 16.0M splash
44 163834 196601 16.0M dsp_a
45 196602 229369 16.0M dsp_b
46 229370 262137 16.0M bk6
47 262138 327673 32.0M mdtp_a
48 327674 393209 32.0M mdtp_b
49 393210 458745 32.0M persist
50 458746 524281 32.0M persistbak
51 524288 655359 64.0M boot_a
52 655360 786431 64.0M boot_b
53 786432 917503 64.0M logdump
54 917504 1179647 128M modem_a
55 1179648 1441791 128M modem_b
56 1441792 6684671 2560M system_a
57 6684672 11927551 2560M system_b
58 11927552 13500415 768M vendor_a
59 13500416 15073279 768M vendor_b
60 15073280 122142686 51.0G userdata
Command (m for help): q
a1291762 said:
I think someone had a problem due to fastboot being too old.
The partition should be 2.5Gb so unless you or someone else resized partitions, it should be large enough.
I can use fdisk from a running phone to print partition info. If you can't boot, perhaps you can check from twrp?
Code:
# fdisk /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Command (m for help): p
Disk /dev/block/mmcblk0: 122142720 sectors, 2296M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 60 entries
First usable sector is 34, last usable sector is 122142686
Number Start (sector) End (sector) Size Name
1 34 49 8192 fsc
2 50 65 8192 ssd
3 66 81 8192 dpo
4 82 113 16384 sec
5 114 145 16384 bk1
6 146 185 20480 bk2
7 186 249 32768 DDR
8 250 313 32768 limits
9 314 377 32768 config
10 378 505 65536 bk3
11 506 761 128K lksecapp
12 762 1017 128K lksecappbak
13 1018 1529 256K devcfg_a
14 1530 2041 256K devcfg_b
15 2042 2553 256K apdp
16 2554 3065 256K msadp
17 3066 4089 512K sbl1_a
18 4090 5113 512K sbl1_b
19 5114 6137 512K rpm_a
20 6138 7161 512K rpm_b
21 7162 8185 512K mota
22 8186 9209 512K keystore
23 9210 10233 512K syscfg
24 10234 12281 1024K cmnlib_a
25 12282 14329 1024K cmnlib_b
26 14330 16377 1024K cmnlib64_a
27 16378 18425 1024K cmnlib64_b
28 18426 20473 1024K keymaster_a
29 20474 22521 1024K keymaster_b
30 22522 24569 1024K misc
31 24570 26617 1024K aboot_a
32 26618 28665 1024K aboot_b
33 28666 30713 1024K dip
34 30714 32761 1024K bk4
35 32762 36857 2048K tz_a
36 36858 40953 2048K tz_b
37 40954 49145 4096K mcfg
38 49146 65529 8192K devinfo
39 65530 81913 8192K fsg
40 81914 98297 8192K modemst1
41 98298 114681 8192K modemst2
42 114682 131065 8192K bk5
43 131066 163833 16.0M splash
44 163834 196601 16.0M dsp_a
45 196602 229369 16.0M dsp_b
46 229370 262137 16.0M bk6
47 262138 327673 32.0M mdtp_a
48 327674 393209 32.0M mdtp_b
49 393210 458745 32.0M persist
50 458746 524281 32.0M persistbak
51 524288 655359 64.0M boot_a
52 655360 786431 64.0M boot_b
53 786432 917503 64.0M logdump
54 917504 1179647 128M modem_a
55 1179648 1441791 128M modem_b
56 1441792 6684671 2560M system_a
57 6684672 11927551 2560M system_b
58 11927552 13500415 768M vendor_a
59 13500416 15073279 768M vendor_b
60 15073280 122142686 51.0G userdata
Command (m for help): q
Click to expand...
Click to collapse
I don't know what the hell is going on. Just tried to flash again with newer late 2018 Xiaomi Flash tool and included fastboot. This time the thing didn't run erase commands before flashing partitions and ended up with the same Chunk Size Data exceeds partition size error. I restored to Oreo from my TWRP backups. TWRP shows partition size as normal 2.5 GB. Never touched the partition table. Smaller GSI images flash in there. Oreo is 1.7 GB, I think, it restores. On Oreo everything works, encryption disabler, Magisk. Just can't flash the lousy official Pie system, tried 10.0.03.0 Whatever, tried 10.0.10 from June, same thing. Somebody suggested I convert to ext4 image, but why the hell does it not just work? Like it can't handle the size of the system image somehow. Will try your commands, thanks. Maybe even newer Xiaomi tool. Damn
Thanks for help.
What is really bloody funny is I have puny Redmi Go running Lineage 16 and all set up without any trouble. Just hilarious.
MarkR7 said:
I don't know what the hell is going on. Just tried to flash again with newer late 2018 Xiaomi Flash tool and included fastboot. This time the thing didn't run erase commands before flashing partitions and ended up with the same Chunk Size Data exceeds partition size error. I restored to Oreo from my TWRP backups. TWRP shows partition size as normal 2.5 GB. Never touched the partition table. Smaller GSI images flash in there. Oreo is 1.7 GB, I think, it restores. On Oreo everything works, encryption disabler, Magisk. Just can't flash the lousy official Pie system, tried 10.0.03.0 Whatever, tried 10.0.10 from June, same thing. Somebody suggested I convert to ext4 image, but why the hell does it not just work? Like it can't handle the size of the system image somehow. Will try your commands, thanks. Maybe even newer Xiaomi tool. Damn
Thanks for help.
What is really bloody funny is I have puny Redmi Go running Lineage 16 and all set up without any trouble. Just hilarious.
Click to expand...
Click to collapse
Try the latest rom http://bigota.d.miui.com/V10.0.12.0...0.PDLMIXM_20190717.0000.00_9.0_59368ef014.tgz and try it using edl, edl is a lower level than fastboot and probably might work better.
edl flash fail - identical to fastboot
SubwayChamp said:
Try the latest rom http://bigota.d.miui.com/V10.0.12.0...0.PDLMIXM_20190717.0000.00_9.0_59368ef014.tgz and try it using edl, edl is a lower level than fastboot and probably might work better.
Click to expand...
Click to collapse
This thing is impossible. EDL flash fails the same way, at about the same time in the flash process. Just says error and maybe the device got disconnected. It did not.
Since I got the phone recently, I never run any OTA updates on it and it's on the lastest Oreo 9.6.11 before 10.0.2.0 Pie. System partition is actually 2.4 GB and Vendor is also slightly smaller than a1291762's partition size. Could it be they increased partitio sizes during 10.0.2.0 Pie update and not applying/skipping that update causes the trouble? Honestly I have no idea, anybody who can make something out of this? Should I run 10.0.2.0 to see if it changes partitions? Or does skipping that update cause trouble for some other unfathomable reason? I will just try OTA sooner or later, I guess.
Here's the output:
daisy_sprout:/ $ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/block/mmcblk0p56 2.4G 1.6G 751M 70% /system_root
tmpfs 1.7G 1.4M 1.7G 1% /sbin
tmpfs 1.7G 712K 1.7G 1% /dev
/dev/block/mmcblk0p58 744M 555M 174M 77% /vendor
tmpfs 1.7G 0 1.7G 0% /mnt
/dev/block/mmcblk0p49 27M 2.7M 24M 11% /persist
/dev/block/mmcblk0p54 128M 81M 47M 63% /firmware
/dev/block/mmcblk0p44 12M 6.9M 4.5M 61% /dsp
/sbin/.magisk/block/data 50G 808M 49G 2% /sbin/.magisk/modules
/data/media 50G 808M 49G 2% /storage/emulated
/mnt/media_rw/0403-0201 29G 28G 712M 98% /storage/0403-0201
daisy_sprout:/ $ df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p56 2539312 1754068 768860 70% /system_root
tmpfs 1821960 1500 1820460 1% /sbin
tmpfs 1821960 712 1821248 1% /dev
/dev/block/mmcblk0p58 761776 567948 178100 77% /vendor
tmpfs 1821960 0 1821960 0% /mnt
/dev/block/mmcblk0p49 28144 2772 24720 11% /persist
/dev/block/mmcblk0p54 131008 82464 48544 63% /firmware
/dev/block/mmcblk0p44 12016 7072 4620 61% /dsp
/sbin/.magisk/block/data 52562448 827192 51718872 2% /sbin/.magisk/modules
MarkR7 said:
This thing is impossible. EDL flash fails the same way, at about the same time in the flash process. Just says error and maybe the device got disconnected. It did not.
Since I got the phone recently, I never run any OTA updates on it and it's on the lastest Oreo 9.6.11 before 10.0.2.0 Pie. System partition is actually 2.4 GB and Vendor is also slightly smaller than a1291762's partition size. Could it be they increased partitio sizes during 10.0.2.0 Pie update and not applying/skipping that update causes the trouble? Honestly I have no idea, anybody who can make something out of this? Should I run 10.0.2.0 to see if it changes partitions? Or does skipping that update cause trouble for some other unfathomable reason? I will just try OTA sooner or later, I guess.
Here's the output:
daisy_sprout:/ $ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/block/mmcblk0p56 2.4G 1.6G 751M 70% /system_root
tmpfs 1.7G 1.4M 1.7G 1% /sbin
tmpfs 1.7G 712K 1.7G 1% /dev
/dev/block/mmcblk0p58 744M 555M 174M 77% /vendor
tmpfs 1.7G 0 1.7G 0% /mnt
/dev/block/mmcblk0p49 27M 2.7M 24M 11% /persist
/dev/block/mmcblk0p54 128M 81M 47M 63% /firmware
/dev/block/mmcblk0p44 12M 6.9M 4.5M 61% /dsp
/sbin/.magisk/block/data 50G 808M 49G 2% /sbin/.magisk/modules
/data/media 50G 808M 49G 2% /storage/emulated
/mnt/media_rw/0403-0201 29G 28G 712M 98% /storage/0403-0201
daisy_sprout:/ $ df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p56 2539312 1754068 768860 70% /system_root
tmpfs 1821960 1500 1820460 1% /sbin
tmpfs 1821960 712 1821248 1% /dev
/dev/block/mmcblk0p58 761776 567948 178100 77% /vendor
tmpfs 1821960 0 1821960 0% /mnt
/dev/block/mmcblk0p49 28144 2772 24720 11% /persist
/dev/block/mmcblk0p54 131008 82464 48544 63% /firmware
/dev/block/mmcblk0p44 12016 7072 4620 61% /dsp
/sbin/.magisk/block/data 52562448 827192 51718872 2% /sbin/.magisk/modules
Click to expand...
Click to collapse
Eventually a failed update can do some weird things like this but is unusual or rarely heard.
Don´t wait that OTA comes to your device, choose one from the official site to be flashed through stock recovery if you have some hope that this help.
Also then to try this in TWRP there is an option to restore system partition (I´m not sure if this really works)
And as a last resource maybe you might to re-adjust the size partition http://en.miui.com/thread-183258-1-1.html
OTA ROM update
Thanks for all advice, really appreciated. I got a zillion backups thru TWRP and those not working fastboot ROMs. I am on a crappy limited mobile connection right now and need to get wifi to get all the ROMs, so preferred to store them locally on a laptop, but should have just run an OTA straight away. Anyway, am back on original stock Oreo, fully stock boot system everything. Have last August 10.13 OTA rom zip and wonder how the hell to try that one. Nothing under system update that would let me use locally stored OTA ROM. Renaming it to update.zip and putting in root of internal storage doesn't seem to work for stock recovery.
Never mind. found a way. Still craps out. Says error in package zip Status 1 whatever the hell that is. Thanks anyway.
MarkR7 said:
Thanks for all advice, really appreciated. I got a zillion backups thru TWRP and those not working fastboot ROMs. I am on a crappy limited mobile connection right now and need to get wifi to get all the ROMs, so preferred to store them locally on a laptop, but should have just run an OTA straight away. Anyway, am back on original stock Oreo, fully stock boot system everything. Have last August 10.13 OTA rom zip and wonder how the hell to try that one. Nothing under system update that would let me use locally stored OTA ROM. Renaming it to update.zip and putting in root of internal storage doesn't seem to work for stock recovery.
Never mind. found a way. Still craps out. Says error in package zip Status 1 whatever the hell that is. Thanks anyway.
Click to expand...
Click to collapse
Update from internal storage and from adb sideload are available on stock recovery. Unfortunately TWRP can´t flash stock updates like on other Xiaomi devices using Miui.
Probably you might try the Miui rom ported available in this forum https://forum.xda-developers.com/mi-a2-lite/development/9-miui-rom-t3960704, system image has almost 2,40GB (version 1.1)
Stocl Recovery
SubwayChamp said:
Update from internal storage and from adb sideload are available on stock recovery. Unfortunately TWRP can´t flash stock updates like on other Xiaomi devices using Miui.
Probably you might try the Miui rom ported available in this forum https://forum.xda-developers.com/mi-a2-lite/development/9-miui-rom-t3960704, system image has almost 2,40GB (version 1.1)
Click to expand...
Click to collapse
You don't unserstand. I DO have stock recovery om both slots, everything as stock as possible. Had Full backups and restored them, boot images also. It is stock recovery that gives the error. Supposedly Status 1 has sth to do with setting permissions, but thanks anyway.
EDL finally worked, many thanks for help
:laugh:
SubwayChamp said:
Update from internal storage and from adb sideload are available on stock recovery. Unfortunately TWRP can´t flash stock updates like on other Xiaomi devices using Miui.
Probably you might try the Miui rom ported available in this forum https://forum.xda-developers.com/mi-a2-lite/development/9-miui-rom-t3960704, system image has almost 2,40GB (version 1.1)
Click to expand...
Click to collapse
:fingers-crossed:
After some fails, EDL flash finally worked and the phone is now on Pie. Many thanks for the suggestion. For some seconds after flash I thought it was a total brick, but I think it must have been exiting EDL. Normal fastboot flash of system.img failed each time.
Again, many thanks for help and time you took.
WARNING
Code:
This process is extremely dangerous. You may brick your device.
Do it only if you know what you are doing!
I am not responsible of bricked devices or dead sdcards.
Hello guys,
I've decided to write this guide since this seems to be the only way to resize system partition to install larger GSIs.
Before starting remember to always make a backup since you will loose all your data.
Also DO NOT DO a simple copy-paste compare with yours first and if you have any doubts write in the comments before enter the doubtful command. Prevention is better than cure!!
This process has been tested on my own device but it has not been tested restoring stock firmware.
(You can also join the telegram group to ask for help https://t.me/MotorolaOneAction)
Requirements
Latest TWRP downloaded (to be booted through fastboot later)
Parted arm64 static binary (attached below)
Latest fastboot and ADB commands installed
Patience
Process
Boot to TWRP from fastboot
Run the following commands:
Code:
adb push /path/to/parted /sbin/parted
adb shell
chmod 777 /sbin/parted
parted /dev/block/sda
p free
Now parted will list your partition table which should be like this:
{
"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"
}
Save the output of the command above (this is very important to restore original partition table if you will run into issues in the next parts)
Now with extreme attention type
Code:
rm partition_number
replacing partition_number with the number of the partition following the reverse order until you reach system_b partition removing it too . In my case I'll type:
Code:
rm 42
rm 41
rm 40
rm 39
Once you removed these partition it's time to recreate them following the original order but increasing the target partition size, in our case system_b. Type
Code:
mkpart name fs_type start end
replacing name with the original partition name (refer to the command output you saved at point 5), fs_type with original file system type, start with the end value in MB of the previous partition, and end with start + size, where size will be the size of the target partition (size is the original size of the partition except for system_b which I've decided to change to 4221MB, 1000MB larger than original one). If it says that the partition isn't aligned, type Ignore. In my case I'll type:
Code:
mkpart system_b ext4 5630MB 9851MB
mkpart oem_a ext2 9851MB 9918.1MB
mkpart oem_b ext2 9918.1MB 9985.3MB
mkpart userdata ext4 9985.3MB 128GB
Now restore the partition flags typing
Code:
set partition_number msftdata on
replacing partition_number with the number of the partition. In my case I'll type:
Code:
set 39 msftdata on
set 40 msftdata on
set 41 msftdata on
set 42 msftdata on
Now type again
Code:
p free
and compare the output with the original table saved before, they should be quite identical.
Type:
Code:
quit
exit
Reboot to bootloader and boot again into TWRP
If in the logs you see lot of red lines saying it could not mount oem partition and userdata partition don't panic, it is normal since they have not been formatted yet (they are registered into fstab with a different file system type). Type:
Code:
adb shell
mkfs.fs_type /dev/block/sdapartition_number
replacing fs_type with original file system type, partition_number with the number of the partition. In my case I'll type:
Code:
adb shell
mkfs.ext4 /dev/block/sda39
mkfs.ext2 /dev/block/sda40
mkfs.ext2 /dev/block/sda41
mkfs.f2fs /dev/block/sda42
Now reboot to bootloader and again into TWRP. Logs now should be free of red lines and you should be able to mount all partitions again.
You have done it!! Now you are able to flash larger GSI (I suggest you doing it from TWRP since fastboot may have some problem recognizing the resized partition size, also remember to change the active slot to the resized one, in my case the slot b)
Reserved
Why this?
GSI running like Havoc, Dotos...
Is this for running Android 12?
Vanilla GSIs will work without this. But larger GSIs that include Gapps will not because they are larger than system partition (like Pixel Experience, dotOS with Gapps, etc.). You can still flash vanilla build and Gapps zip of course to avoid doing this.
Regarding Android 12 I have not tried it yet.
please someone port postmarketos to this device, kane has a lot of potential
edit: i'm talking about pmos, because this resizing process has sense only for postmarket, if any other roms are bigger than system part, than they are just bloated worthless ****s.
sorry to bother you.
i found your post after long time of searching. I'm noob for installing GSI,to do so i need to resize system partition.but i have zero idea about resizing and also seems like its very critical,and if i made any mistake to resizing it i may have to lost my phone forever.
I'm here to make a request to you that if you help me out to resize partition by a easiest way .i hope you won't reject me. I'm really fed up about resizing.here is my device details
phone: mi 8 pro
codename: equuleus
Rom : 128 GB
Default system partition size : 2.74GB
Hope you will help me
shahrair said:
sorry to bother you.
i found your post after long time of searching. I'm noob for installing GSI,to do so i need to resize system partition.but i have zero idea about resizing and also seems like its very critical,and if i made any mistake to resizing it i may have to lost my phone forever.
I'm here to make a request to you that if you help me out to resize partition by a easiest way .i hope you won't reject me. I'm really fed up about resizing.here is my device details
phone: mi 8 pro
codename: equuleus
Rom : 128 GB
Default system partition size : 2.74GB
Hope you will help me
Click to expand...
Click to collapse
what did you do wrong?
my device does not have /sda, any solution?
Sammm77 said:
my device does not have /sda, any solution?
Click to expand...
Click to collapse
it might be mmcblk0
lol.mam said:
it might be mmcblk0
Click to expand...
Click to collapse
Yep, but partitions like /system /vendor /system_ext and product do not appear, is it because of super partition?
Some phones also need system_a resized. I couldn't install a bigger GSI on One Action/troika and resizing system_a fixed it.
as partições ( parted /dev/block/mmcblk0 )e (parted /dev/block/sda) não contém partições, mas as
(parted /dev/block/sdb) (parted /dev/block/sde) (parted /dev/block/sdf) contém as partiçoes. posso trabalhar nelas??
SDF (parted) parted /dev/block/sdf
Number Start End Size File system Name Flags
1 131kB 655kB 524kB aop_b
2 655kB 4850kB 4194kB tz_b
3 4850kB 5374kB 524kB hyp_b
4 5374kB 5505kB 131kB storsec_b
5 5505kB 5636kB 131kB devcfg_b
6 5636kB 6160kB 524kB keymaster_b
7 6160kB 6685kB 524kB cmnlib_b
8 6685kB 7209kB 524kB cmnlib64_b
9 7209kB 7471kB 262kB prov_b
10 7471kB 8520kB 1049kB abl_b
11 8520kB 8602kB 81.9kB qupfw_b
12 8651kB 10.7MB 2097kB uefisecapp_b
13 10.7MB 10.8MB 32.8kB multiimgoem_b
14 10.8MB 10.8MB 32.8kB multiimgqti_b
15 10.8MB 10.9MB 65.5kB vbmeta_b
16 10.9MB 36.0MB 25.2MB ext2 fsg_b
17 36.0MB 183MB 147MB ext2 modem_b
18 183MB 216MB 33.6MB ext4 dsp_b
19 216MB 217MB 1049kB ext2 bluetooth_b
20 217MB 251MB 33.6MB logo_b
21 251MB 318MB 67.1MB boot_b
22 318MB 343MB 25.2MB dtbo_b
23 343MB 1149MB 805MB ext2 vendor_b
24 1149MB 4638MB 3490MB ext2 system_b
25 4638MB 4949MB 310MB ext2 oem_b
SDB parted /dev/block/sdb
Number Start End Size File system Name Flags
1 131kB 139kB 8192B ssd
2 262kB 33.8MB 33.6MB ext4 persist
3 33.8MB 42.2MB 8389kB ext4 prodpersist
4 42.2MB 43.3MB 1049kB misc
5 43.3MB 43.8MB 524kB keystore
6 43.8MB 44.3MB 524kB frp
7 44.3MB 44.8MB 524kB utags
8 44.8MB 45.4MB 524kB utagsBackup
9 45.4MB 45.5MB 131kB cid
10 45.5MB 62.3MB 16.8MB metadata
11 62.3MB 70.6MB 8389kB kpan
12 70.6MB 79.0MB 8389kB sp
13 79.0MB 95.8MB 16.8MB carrier
14 95.8MB 97.9MB 2097kB modemst1
15 97.9MB 100MB 2097kB modemst2
16 100MB 100MB 131kB fsc
17 100MB 100MB 32.8kB dhob
18 100MB 100MB 4096B devinfo
19 100MB 109MB 8389kB logfs
20 109MB 109MB 262kB apdp
21 109MB 117MB 8389kB spunvm
22 117MB 118MB 524kB uefivarstore
23 118MB 118GB 118GB userdata
SDE (parted) parted /dev/block/sde
Number Start End Size File system Name Flags
1 131kB 655kB 524kB aop_a
2 655kB 4850kB 4194kB tz_a
3 4850kB 5374kB 524kB hyp_a
4 5374kB 5505kB 131kB storsec_a
5 5505kB 5636kB 131kB devcfg_a
6 5636kB 6160kB 524kB keymaster_a
7 6160kB 6685kB 524kB cmnlib_a
8 6685kB 7209kB 524kB cmnlib64_a
9 7209kB 7471kB 262kB prov_a
10 7471kB 8520kB 1049kB abl_a
11 8520kB 8602kB 81.9kB qupfw_a
12 8651kB 10.7MB 2097kB uefisecapp_a
13 10.7MB 10.8MB 32.8kB multiimgoem_a
14 10.8MB 10.8MB 32.8kB multiimgqti_a
15 10.8MB 10.9MB 65.5kB vbmeta_a
16 10.9MB 36.0MB 25.2MB ext2 fsg_a
17 36.0MB 183MB 147MB ext2 modem_a msftdata
18 183MB 216MB 33.6MB ext4 dsp_a
19 216MB 217MB 1049kB ext2 bluetooth_a
20 217MB 251MB 33.6MB logo_a
21 251MB 318MB 67.1MB boot_a
22 318MB 343MB 25.2MB dtbo_a
23 343MB 1149MB 805MB ext2 vendor_a
24 1149MB 4638MB 3490MB ext2 system_a
25 4638MB 4949MB 310MB ext2 oem_a
My device: SM-A528B
Hello, I need to increase the partition for GSI. Could you please help me? Which section should I enlarge and what commands should I enter? (I tried to do everything according to the instructions, but I had questions and nothing happened)
1. I put the file (parted) in the root of the disk (C) and wrote (adb push C:/parted /sbin/ parted) is that correct?
2. What should I enter in (fs_type), (msftdata) if I have spaces here?
3. After the second input (p free), I lost the names of the modified sections.
4. The red lines in TWRP did not disappear anywhere and I could not boot into the system.
Sammm77 said:
Yep, but partitions like /system /vendor /system_ext and product do not appear, is it because of super partition?
Click to expand...
Click to collapse
Were you able to figure out how to expand the system partition with a super partition?
For fastboot to take the partition names use the following parted command:
Code:
name <partition-number> <partition-name>
On some devices this helps a lot, consider adding it to the main thread ^^
Some devices also use /dev/block/mmcblk0 instead of /dev/block/sda
Hi, how can i add partition like product and vbmeta, tried to add using "mkpart PRODUCT ext4 start end" then "mkpart VBMETA space start end" it added but cant flash using twrp, tried on fastboot "Fastboot flash product product.img" then same with vbmeta. but nothing works, zip files cant mount those. Please help