[REF] LEX720 - 64GB - Partition infos - LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D
Hi!
As I haven't found this infos online yet, I decided to post this information for reference (maybe it might be useful for someone in the future).
I grabbed this data from a LEX720 (LeEco Le Pro 3, chinese version, dual-sim) with 6GB RAM and 64GB storage while running TWRP recovery.
At the time of the dump on the device the original (chinese/english) 5.8.017S (ro.build.fingerprint: "LeEco/ZL1_CN/le_zl1:6.0.1/WAXCNFN5801709271S/letv09271704:user/release-keys") firmware was installed.
(I attached the full output of "fdisk -l" with all partition details - including start and end sectors - also as a text file.)
Code:
#
# Dumped from LEX720, with 64GB storage:
#
Device Name Size Part Name Mounted Flashed_from
--- /dev/block/sda: ------------------------------------------------------------
/dev/block/sda1 8192 ssd
/dev/block/sda2 32.0M persist /persist/
/dev/block/sda3 256M cache /cache/
/dev/block/sda4 1024K misc
/dev/block/sda5 512K keystore
/dev/block/sda6 128K devcfg devcfg.mbn
/dev/block/sda7 128K devcfgbak
/dev/block/sda8 512K frp
/dev/block/sda9 4096K ramdump
/dev/block/sda10 54.1G userdata /data/
--- /dev/block/sdb: ------------------------------------------------------------
/dev/block/sdb1 4052K xbl xbl.elf
--- /dev/block/sdc: ------------------------------------------------------------
/dev/block/sdc1 4052K xblbak xbl.elf
--- /dev/block/sdd: ------------------------------------------------------------
/dev/block/sdd1 32768 reserve
/dev/block/sdd2 4096 cdt
/dev/block/sdd3 1024K ddr ddr.mbn
--- /dev/block/sde: ------------------------------------------------------------
/dev/block/sde1 512K rpm rpm.mbn
/dev/block/sde2 512K rpmbak rpm.mbn
/dev/block/sde3 2048K tz tz.mbn
/dev/block/sde4 2048K tzbak tz.mbn
/dev/block/sde5 512K hyp hyp.mbn
/dev/block/sde6 512K hypbak hyp.mbn
/dev/block/sde7 2048K fsg
/dev/block/sde8 1024K fsg_gap
/dev/block/sde9 16384 sec
/dev/block/sde10 512K pmic pmic.elf
/dev/block/sde11 512K pmicbak pmic.elf
/dev/block/sde12 110M modem /firmware/ NON-HLOS.bin
/dev/block/sde13 16.0M dsp /dsp/ adspso.bin
/dev/block/sde14 1024K dip
/dev/block/sde15 32.0M mdtp
/dev/block/sde16 1024K aboot emmc_appsboot.mbn
/dev/block/sde17 1024K abootbak emmc_appsboot.mbn
/dev/block/sde18 64.0M boot boot.img
/dev/block/sde19 4096M system /system/ system.* (several files)
/dev/block/sde20 64.0M recovery
/dev/block/sde21 4096 devinfo devinfo.bin
/dev/block/sde22 1024K bluetooth /bt_firmware/ BTFM.bin
/dev/block/sde23 512K keymaster keymaster.mbn
/dev/block/sde24 512K keymasterbak keymaster.mbn
/dev/block/sde25 256K cmnlib cmnlib.mbn
/dev/block/sde26 256K cmnlibbak cmnlib.mbn
/dev/block/sde27 256K cmnlib64 cmnlib64.mbn
/dev/block/sde28 256K cmnlib64bak cmnlib64.mbn
/dev/block/sde29 256K apdp
/dev/block/sde30 256K msadp
/dev/block/sde31 4096 dpo
/dev/block/sde32 100M splash splash.img
/dev/block/sde33 2048K sti
--- /dev/block/sdf: ------------------------------------------------------------
/dev/block/sdf1 2048K modemst1
/dev/block/sdf2 1024K modemst1_gap
/dev/block/sdf3 2048K modemst2
/dev/block/sdf4 1024K modemst2_gap
/dev/block/sdf5 4096 fsc
/dev/block/sdf6 4096 factory
/dev/block/sdf7 4096 bootconfig
/dev/block/sdf8 4096 rootconfig
/dev/block/sdf9 4096 recoveryconfig
/dev/block/sdf10 512K letvconfig
/dev/block/sdf11 512K letveui
/dev/block/sdf12 512K letvsecure
/dev/block/sdf13 512K letvreserve
/dev/block/sdf14 10.0M kernellog
At normal system runtime the mountpoints look like this:
Code:
rootfs / rootfs ro,seclabel,size=2843628k,nr_inodes=710907 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=2940160k,nr_inodes=735040,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,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=2940160k,nr_inodes=735040,mode=750,gid=1000 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=2940160k,nr_inodes=735040,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/bootdevice/by-name/system /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
/dev/block/bootdevice/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/dsp /dsp ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/modem /firmware vfat ro,context=u:object_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/bluetooth /bt_firmware vfat ro,context=u:object_r:bt_firmware_file:s0,relatime,uid=1002,gid=3002,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=2940160k,nr_inodes=735040,mode=755,gid=1000 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
I also dumped all partitions except the large ones (system, userdata, recovery) using "dd" (from within TWRP recovery) and did a first very simple content check by using the Linux "file" command:
Code:
[email protected] ~/D/_/A/L/0/dumps> file *
aboot: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped
abootbak: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped
apdp: ELF 32-bit LSB no file type, ARM, version 1 (SYSV)
bluetooth: x86 boot sector, code offset 0x3c, OEM-ID "MSDOS5.0", Bytes/sector 4096, sectors/cluster 4, root entries 512, Media descriptor 0xf8, sectors/FAT 33, heads 255, sectors 262144 (volumes > 32 MB) , serial number 0xbc614e, unlabeled, FAT (16 bit)
boot: data
bootconfig: data
cdt: data
cmnlib: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), statically linked, stripped
cmnlib64: ELF 64-bit LSB shared object, version 1 (SYSV), statically linked, stripped
cmnlib64bak: ELF 64-bit LSB shared object, version 1 (SYSV), statically linked, stripped
cmnlibbak: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), statically linked, stripped
ddr: data
devcfg: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, stripped
devcfgbak: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, stripped
devinfo: ASCII text, with no line terminators
dip: data
dpo: data
dsp: Linux rev 1.0 ext4 filesystem data (extents) (large files)
factory: data
frp: data
fsc: data
fsg: data
fsg_gap: data
hyp: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, stripped
hypbak: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, stripped
kernellog: data
keymaster: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), statically linked, stripped
keymasterbak: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), statically linked, stripped
keystore: data
letvconfig: ASCII text, with no line terminators
letveui: data
letvreserve: data
letvsecure: data
mdtp: data
misc: data
modem: x86 boot sector, code offset 0x3c, OEM-ID "MSDOS5.0", Bytes/sector 4096, sectors/cluster 4, root entries 512, Media descriptor 0xf8, sectors/FAT 4, heads 255, sectors 28160 (volumes > 32 MB) , serial number 0xbc614e, unlabeled, FAT (16 bit)
modemst1: data
modemst1_gap: data
modemst2: data
modemst2_gap: data
msadp: ELF 32-bit LSB no file type, ARM, version 1 (SYSV)
persist: Linux rev 1.0 ext4 filesystem data (extents) (large files)
pmic: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, corrupted section header size
pmicbak: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, corrupted section header size
ramdump: data
recovery: data
recoveryconfig: data
reserve: data
rootconfig: data
rpm: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped
rpmbak: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped
sec: data
splash: data
ssd: data
sti: data
tz: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, stripped
tzbak: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, stripped
xbl: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, corrupted section header size
xblbak: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, corrupted section header size
Also, the device can be easily brought into the "Qualcomm HS-USB QDLoader 9008" download mode via adb:
Code:
adb reboot edl
The phone will then show up as "Qualcomm HS-USB QDLoader 9008" in the device manager (if the Qualcomm drivers are installed) and the phone itself will stay totally dark (but running). To leave the Qualcomm download mode simply press the power button for around 10secs (until the device vibrates and reboots).
I personally don't have any experience yet with the Qualcomm Download mode, but this mode should allow a very low-level re-flash ("unbrick") of the device if for some reason the secondary bootloader (SBL) gets destroyed, but only if we have the correct files to flash in this mode!
(Here an unrelated blog post with some general infos about this qualcomm mode: http://www.androidbrick.com/ultimat...agons-are-unbrickable-qhsusb_dload_qpst_qfil/)
If somebody has any more knowledge in this area (i.e. how-to dump the needed files for a low-level SBL restore in the format as they are needed for the Qualcomm tools) then we might be able to unbrick devices in future (and help people like @amdtip who cannot boot anymore into fastboot or recovery).
john
androcheck said:
Also, the device can be easily brought into the "Qualcomm HS-USB QDLoader 9008" download mode via adb:
The phone will then show up as "Qualcomm HS-USB QDLoader 9008" in the device manager (if the Qualcomm drivers are installed) and the phone itself will stay totally dark (but running). To leave the Qualcomm download mode simply press the power button for around 10secs (until the device vibrates and reboots).
I personally don't have any experience yet with the Qualcomm Download mode, but this mode should allow a very low-level re-flash ("unbrick") of the device if for some reason the secondary bootloader (SBL) gets destroyed, but only if we have the correct files to flash in this mode!
(Here an unrelated blog post with some general infos about this qualcomm mode: http://www.androidbrick.com/ultimat...gons-are-unbrickable-qhsusb_dload_qpst_qfil/)
If somebody has any more knowledge in this area (i.e. how-to dump the needed files for a low-level SBL restore in the format as they are needed for the Qualcomm tools) then we might be able to unbrick devices in future (and help people like @amdtip who cannot boot anymore into fastboot or recovery).
john
Click to expand...
Click to collapse
Yeah I reckon they is how they made all the Qualcomm Recovery Tools for the OnePlus as they are a godsend.
@androcheck can you please post cat /proc/partitions aswell ?
thank you
darkobas said:
@androcheck can you please post cat /proc/partitions aswell ?
Click to expand...
Click to collapse
Sure:
Code:
[email protected]_zl1:/ $ cat /proc/partitions
major minor #blocks name
8 0 57073664 sda
8 1 8 sda1
8 2 32768 sda2
8 3 262144 sda3
8 4 1024 sda4
8 5 512 sda5
8 6 128 sda6
8 7 128 sda7
8 8 512 sda8
8 9 4096 sda9
8 10 56772300 sda10
8 64 5242880 sde
8 65 512 sde1
8 66 512 sde2
8 67 2048 sde3
8 68 2048 sde4
8 69 512 sde5
8 70 512 sde6
8 71 2048 sde7
8 72 1024 sde8
8 73 16 sde9
8 74 512 sde10
8 75 512 sde11
8 76 112640 sde12
8 77 16384 sde13
8 78 1024 sde14
8 79 32768 sde15
259 0 1024 sde16
259 1 1024 sde17
259 2 65536 sde18
259 3 4194304 sde19
259 4 65536 sde20
259 5 4 sde21
259 6 1024 sde22
259 7 512 sde23
259 8 512 sde24
259 9 256 sde25
259 10 256 sde26
259 11 256 sde27
259 12 256 sde28
259 13 256 sde29
259 14 256 sde30
259 15 4 sde31
259 16 102400 sde32
259 17 2048 sde33
8 80 32768 sdf
8 81 2048 sdf1
8 82 1024 sdf2
8 83 2048 sdf3
8 84 1024 sdf4
8 85 4 sdf5
8 86 4 sdf6
8 87 4 sdf7
8 88 4 sdf8
8 89 4 sdf9
8 90 512 sdf10
8 91 512 sdf11
8 92 512 sdf12
8 93 512 sdf13
8 94 10240 sdf14
8 48 131072 sdd
8 49 32 sdd1
8 50 4 sdd2
8 51 1024 sdd3
8 16 4096 sdb
8 17 4052 sdb1
8 32 4096 sdc
8 33 4052 sdc1
Related
[Q] Atrix internal storage partition question
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
[Q] need help partitioning Huawei Ascend G330 U8825-1
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
[Info] List of LG G2 D802 32GB devices and partitions
To run this commands you need a rooted device with BusyBox and parted.
Code:
[email protected]:/ #[COLOR="Blue"] [B]cat /proc/partitions[/B][/COLOR]
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 1 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1 mmcblk0p19
179 20 512 mmcblk0p20
179 21 8192 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 32768 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 512 mmcblk0p26
179 27 1024 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 8 mmcblk0p29
179 30 2834432 mmcblk0p30
179 31 622592 mmcblk0p31
259 0 81920 mmcblk0p32
259 1 16384 mmcblk0p33
259 2 49152 mmcblk0p34
259 3 26460160 mmcblk0p35
259 4 61423 mmcblk0p36
179 32 4096 mmcblk0rpmb
Code:
[email protected]:/ # [B][COLOR="Blue"]ls -l /dev/block/platform/msm_sdcc.1/by-num/[/COLOR][/B]
lrwxrwxrwx root root 1970-01-15 23:14 p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-15 23:14 p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-15 23:14 p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-15 23:14 p12 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-15 23:14 p13 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-15 23:14 p14 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-15 23:14 p15 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-15 23:14 p16 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-15 23:14 p17 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-15 23:14 p18 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-15 23:14 p19 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-15 23:14 p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-15 23:14 p20 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-15 23:14 p21 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-15 23:14 p22 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-15 23:14 p23 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-15 23:14 p24 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-15 23:14 p25 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-15 23:14 p26 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-15 23:14 p27 -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-15 23:14 p28 -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-15 23:14 p29 -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-15 23:14 p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-15 23:14 p30 -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-15 23:14 p31 -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-15 23:14 p32 -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-15 23:14 p33 -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-15 23:14 p34 -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-15 23:14 p35 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-15 23:14 p36 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-15 23:14 p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-15 23:14 p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-15 23:14 p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-15 23:14 p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-15 23:14 p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-15 23:14 p9 -> /dev/block/mmcblk0p9
Code:
[email protected]:/ # [B][COLOR="Blue"]ls -l /dev/block/platform/msm_sdcc.1/by-name/[/COLOR][/B]
lrwxrwxrwx root root 1970-01-15 23:14 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-15 23:14 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-15 23:14 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-15 23:14 cache -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-15 23:14 cust -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-15 23:14 dbi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-15 23:14 dbibak -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-15 23:14 drm -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-15 23:14 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-15 23:14 fota -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-15 23:14 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-15 23:14 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-15 23:14 grow -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-15 23:14 laf -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-15 23:14 misc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-15 23:14 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-15 23:14 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-15 23:14 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-15 23:14 mpt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-15 23:14 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-15 23:14 pad1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-15 23:14 pad2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-15 23:14 persist -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-15 23:14 rct -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-15 23:14 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-15 23:14 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-15 23:14 rpmbak -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-15 23:14 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-15 23:14 sns -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-15 23:14 spare -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-15 23:14 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-15 23:14 system -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-15 23:14 tombstones -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-15 23:14 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-15 23:14 tzbak -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-15 23:14 userdata -> /dev/block/mmcblk0p35
Code:
[email protected]:/ # [B][COLOR="Blue"]parted /dev/block/mmcblk0[/COLOR][/B]
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC 032GE4 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16.8MB 83.9MB 67.1MB fat16 modem
2 83.9MB 84.9MB 1049kB sbl1
3 84.9MB 85.5MB 524kB dbi
4 101MB 101MB 524kB DDR
5 117MB 118MB 1049kB aboot
6 118MB 120MB 1049kB rpm
7 134MB 151MB 16.8MB boot
8 151MB 152MB 1049kB tz
9 152MB 152MB 1024B pad
10 168MB 171MB 3146kB modemst1
11 171MB 174MB 3146kB modemst2
12 174MB 174MB 1024B pad1
13 185MB 201MB 16.8MB misc
14 201MB 235MB 33.6MB ext4 persist
15 235MB 252MB 16.8MB recovery
16 252MB 255MB 3146kB fsg
17 268MB 269MB 524kB fsc
18 269MB 269MB 524kB ssd
19 269MB 269MB 1024B pad2
20 269MB 270MB 524kB encrypt
21 285MB 294MB 8389kB ext4 drm
22 294MB 302MB 8389kB ext4 sns
23 302MB 336MB 33.6MB laf
24 336MB 369MB 33.6MB fota
25 369MB 403MB 33.6MB ext4 mpt
26 403MB 403MB 524kB dbibak
27 403MB 404MB 1049kB rpmbak
28 404MB 405MB 1049kB tzbak
29 405MB 405MB 8192B rct
30 419MB 3322MB 2902MB ext4 system
31 3322MB 3959MB 638MB ext4 cache
32 3959MB 4043MB 83.9MB tombstones
33 4043MB 4060MB 16.8MB spare
34 4060MB 4110MB 50.3MB ext4 cust
35 4110MB 31.2GB 27.1GB ext4 userdata
36 31.2GB 31.3GB 62.9MB grow
Code:
[email protected]:/ # [B][COLOR="Blue"]mount[/COLOR][/B]
rootfs / rootfs ro,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
none /dev/cpuctl cgroup rw,relatime,cpu 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,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 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
/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,noatime,noauto_da_alloc,resuid=1000,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/sns /sns ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/drm /persist-lg ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mpt /mpt ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,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/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 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/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb 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/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Code:
[email protected]:/ # [B][COLOR="Blue"]df[/COLOR][/B]
Filesystem Size Used Free Blksize
/dev 926.51M 128.00K 926.39M 4096
/sys/fs/cgroup 926.51M 12.00K 926.50M 4096
/mnt/asec 926.51M 0.00K 926.51M 4096
/mnt/obb 926.51M 0.00K 926.51M 4096
/system 2.66G 2.17G 495.23M 4096
/data 24.80G 20.77G 4.03G 4096
/sns 7.83M 4.03M 3.80M 4096
/persist-lg 7.83M 4.35M 3.48M 4096
/mpt 31.46M 12.96M 18.49M 4096
/cache 597.97M 9.59M 588.38M 4096
/persist 31.46M 4.05M 27.41M 4096
/firmware 63.95M 52.36M 11.59M 16384
/cust 46.22M 8.18M 38.04M 4096
/storage/emulated 926.51M 0.00K 926.51M 4096
/mnt/shell/emulated 24.80G 20.77G 4.03G 4096
/storage/emulated/legacy 24.80G 20.77G 4.03G 4096
/storage/emulated/0 24.80G 20.77G 4.03G 4096
/storage/emulated/0/Android/obb 24.80G 20.77G 4.03G 4096
/storage/emulated/legacy 24.80G 20.77G 4.03G 4096
/storage/emulated/legacy/Android/obb 24.80G 20.77G 4.03G 4096
Code:
[email protected]:/ # [B][COLOR="Blue"]find /dev/block/platform/msm_sdcc.1/ -name 'mmc*' -exec fdisk -l {} \;[/COLOR][/B]
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p36: 62 MB, 62897664 bytes
4 heads, 16 sectors/track, 1919 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p36 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p35: 27.0 GB, 27095203840 bytes
4 heads, 16 sectors/track, 826880 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p35 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p34: 50 MB, 50331648 bytes
4 heads, 16 sectors/track, 1536 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p34 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p33: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p33 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p32: 83 MB, 83886080 bytes
4 heads, 16 sectors/track, 2560 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p32 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p31: 637 MB, 637534208 bytes
4 heads, 16 sectors/track, 19456 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p31 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p30: 2902 MB, 2902458368 bytes
4 heads, 16 sectors/track, 88576 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p30 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p29: 0 MB, 8192 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p29 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p28: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p28 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p27: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p27 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p26: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p26 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p25: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p25 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p24: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p24 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p23: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p23 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p22: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p22 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p21: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p21 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p20: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p20 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p19: 0 MB, 1024 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p19 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p18: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p18 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p17: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p17 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p16: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p16 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p15: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p15 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p14: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p14 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p13: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p13 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p12: 0 MB, 1024 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p12 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p11: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p11 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p10: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p10 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0rpmb: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0rpmb doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p9: 0 MB, 1024 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p9 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p8: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p8 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p7: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p7 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p6: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p6 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p5: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p5 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p4: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p4 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p3: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p3 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p2: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p2 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p1: 67 MB, 67108864 bytes
4 heads, 16 sectors/track, 2048 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/msm_sdcc.1/mmcblk0p1p1 ? 12158374 29994462 570754815+ 72 Unknown
Partition 1 does not end on cylinder boundary
/dev/block/platform/msm_sdcc.1/mmcblk0p1p2 ? 2635774 32886216 968014120 65 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/platform/msm_sdcc.1/mmcblk0p1p3 ? 29216898 59467339 968014096 79 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/platform/msm_sdcc.1/mmcblk0p1p4 ? 1 56831664 1818613248 d Unknown
Partition 4 does not end on cylinder boundary
Partition table entries are not in disk order
Disk /dev/block/platform/msm_sdcc.1/mmcblk0: 31.2 GB, 31268536320 bytes
256 heads, 63 sectors/track, 3786 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/msm_sdcc.1/mmcblk0p1
Additional links:
[GUIDE] Making Dump Files Out of Android Device Partitions
parted from cyanogenmod repo
The 4 partitions modified by AutoRec are the following, so backup with dd before applying.
bender_007 said:
^ aboot, boot, laf + recovery
Click to expand...
Click to collapse
I had this question elsewhere as well - can we force our phone into QH-USB 9006 mode ? This shows all the other partitions like aboot, boot, recovery etc and is directly flashable using "dd" . I recovered my bricked phone through this method, but I was in QH USB 9008 mode... not sure how to get this for people who are stuck in LG boot screen (and can neither get to download mode or fastboot)
sandys1 said: I had this question elsewhere as well - can we force our phone into QH-USB 9006 mode ? This shows all the other partitions like aboot, boot, recovery etc and is directly flashable using "dd" . I recovered my bricked phone through this method, but I was in QH USB 9008 mode... not sure how to get this for people who are stuck in LG boot screen (and can neither get to download mode or fastboot) Click to expand... Click to collapse Didn't try either using dd to write a custom recovery being root either. Gor the QH USB 9008 mode here's a guide. [FIX] Unbrick LG G2 stuck in Qualcomm HS-USB QDLoader 9008 mode
so what's grow partition function? i managed to delete it to give some extra space on userdata.
hyperionx7 said: so what's grow partition function? i managed to delete it to give some extra space on userdata. Click to expand... Click to collapse You deleted a system partition that you don't know what's for to get 62.9MB more space?
Can't Boot after repartition internal memory using fdisk on Motorola Droid Razr
i was trying to flash lineageOS 13.0 on driod razr xt912 using safestrap 3.75 right after that flash open gapp but couldn't due to low storage error of system partition so i decided to increase system memory . After googling found two way of doing , 1st parted , 2nd fdisk. After getting in error in parted so i switch to fdisk . Below are the steps i did please correct me 1) connected phone in safetrap 3.75 recovery to pc. CONNECTION WAS SUCCESSFUL . took backup of /system and /data from safetrap 3.75. adb root adb shell # cat /etc/fstab /dev/block/mmcblk1p25 /sdcard vfat rw /sdcard-ext vfat rw /dev/block/mmcblk1p24-orig /data ext3 rw /dev/block/mmcblk1p21-orig /cache ext3 rw /dev/block/mmcblk1p20-orig /system ext3 rw /dev/block/mmcblk1p23 /osh ext3 rw /dev/block/mmcblk1p20-orig /systemorig ext3 rw /dev/block/mmcblk1p25 /ss vfat rw # cat /proc/partitions 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 128 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 655360 mmcblk1p20 system 179 21 1048576 mmcblk1p21 cache 179 22 622592 mmcblk1p22 preinstall 179 23 1364992 mmcblk1p23 webtop 179 24 3203072 mmcblk1p24 userdata 179 25 8401792 mmcblk1p25 emstorage 179 26 128 mmcblk1p26 179 64 2048 mmcblk1boot1 179 32 2048 mmcblk1boot0 # /sbin/fdisk /dev/block/mmcblk1 Disk /dev/block/mmcblk1: 15.9 GB, 15938355200 bytes 16 heads, 16 sectors/track, 121600 cylinders, total 31129600 sectors Units = sectors of 1 * 512 = 512 bytes u (unit to sector ) p Device Boot Start End Blocks Id System block/mmcblk1p1 * 256 511 128 83 Linux block/mmcblk1p2 1024 2047 512 83 Linux block/mmcblk1p3 2048 3071 512 83 Linux block/mmcblk1p4 3072 31105023 15550976 5 Extended block/mmcblk1p5 4096 5119 512 83 Linux block/mmcblk1p6 5120 5375 128 83 Linux block/mmcblk1p7 6144 14335 4096 83 Linux block/mmcblk1p8 14336 15359 512 83 Linux block/mmcblk1p9 16384 18431 1024 83 Linux block/mmcblk1p10 18432 22527 2048 83 Linux block/mmcblk1p11 22528 23551 512 83 Linux block/mmcblk1p12 23552 24575 512 83 Linux block/mmcblk1p13 24576 32767 4096 83 Linux block/mmcblk1p14 32768 49151 8192 83 Linux block/mmcblk1p15 49152 67583 9216 83 Linux block/mmcblk1p16 67584 501759 217088 83 Linux block/mmcblk1p17 501760 502783 512 83 Linux block/mmcblk1p18 502784 503807 512 83 Linux block/mmcblk1p19 503808 511999 4096 83 Linux block/mmcblk1p20 512000 1822719 655360 83 Linux block/mmcblk1p21 1822720 3919871 1048576 83 Linux block/mmcblk1p22 3919872 5165055 622592 83 Linux block/mmcblk1p23 5165056 7895039 1364992 83 Linux block/mmcblk1p24 7895040 14301183 3203072 83 Linux block/mmcblk1p25 14301184 31104767 8401792 83 Linux block/mmcblk1p26 31104768 31105023 128 83 Linux 2) i decide to make changes in (20-25)'s partition ( system to +3072M, cache to +1024M, preinstall to +1S, webtop to +1S, userdata to +3072M, emstorage to +8102M). But in order to make changes in (20-25)'s i had to delete 26's partitions but after creating new table starting and ending sector of 26's partitions remains the same . Also after i knew that safetrap 3.75 does not use preinstall, webtop for stock slot so i change them to +1S SECTORE. d 26 d 25 d 24 d 23 d 22 d 21 d 20 3) after creating the new partitions. Table as follows P Device Boot Start End Blocks Id System /dev/block/mmcblk1p1 * 256 511 128 83 Linux /dev/block/mmcblk1p2 1024 2047 512 83 Linux /dev/block/mmcblk1p3 2048 3071 512 83 Linux /dev/block/mmcblk1p4 3072 31105023 15550976 5 Extended /dev/block/mmcblk1p5 4096 5119 512 83 Linux /dev/block/mmcblk1p6 5120 5375 128 83 Linux /dev/block/mmcblk1p7 6144 14335 4096 83 Linux /dev/block/mmcblk1p8 14336 15359 512 83 Linux /dev/block/mmcblk1p9 16384 18431 1024 83 Linux /dev/block/mmcblk1p10 18432 22527 2048 83 Linux /dev/block/mmcblk1p11 22528 23551 512 83 Linux /dev/block/mmcblk1p12 23552 24575 512 83 Linux /dev/block/mmcblk1p13 24576 32767 4096 83 Linux /dev/block/mmcblk1p14 32768 49151 8192 83 Linux /dev/block/mmcblk1p15 49152 67583 9216 83 Linux /dev/block/mmcblk1p16 67584 501759 217088 83 Linux /dev/block/mmcblk1p17 501760 502783 512 83 Linux /dev/block/mmcblk1p18 502784 503807 512 83 Linux /dev/block/mmcblk1p19 503808 511999 4096 83 Linux /dev/block/mmcblk1p20 512016 6512016 3000000+ 83 Linux /dev/block/mmcblk1p21 6512033 8512033 1000000+ 83 Linux /dev/block/mmcblk1p22 8512050 8512052 1+ 83 Linux /dev/block/mmcblk1p23 8512069 8512071 1+ 83 Linux /dev/block/mmcblk1p24 8512088 14512088 3000000+ 83 Linux /dev/block/mmcblk1p25 14512105 31104751 8296323+ 83 Linux /dev/block/mmcblk1p26 31104768 31105023 128 83 Linux w (writing) recreating table successful q (quit) # mke2fs -t ext3 /dev/block/mmcblk1p20 # mke2fs -t ext3 /dev/block/mmcblk1p21 # mke2fs -t ext3 /dev/block/mmcblk1p22 # mke2fs -t ext3 /dev/block/mmcblk1p23 # mke2fs -t ext3 /dev/block/mmcblk1p24 # mkdosfs /dev/block/mmcblk1p25 #mount /dev/block/mmcblk1p20 /system/ #mount /dev/block/mmcblk1p21 /cache/ #mount /dev/block/mmcblk1p24 /data/ #mount /dev/block/mmcblk1p25 /sdcard/ # mount /dev/block/mmcblk1p25 /ss/ # mount /dev/block/mmcblk1p25 /and-sec/ 4) after that wiped cache, data , andriod secure, data, webtop, system. 5) restored backup of /system and /data / 6) reboot the system 7) after Motorola logo "M" got error ap fastboot flash mode [boot failure] 0A.77 eMMC Info: Size 16g to return to normal mode - first press power key to power down device is LOCKED, Status Code:0 battery ok ok to program Connect USB Data cable Invalid CG OTV [CG: system]: Invalid SP Data Invalid CG HAB [CG: system, status: 0X004E] Invalid CG OTV [CG: system] 8) i had to use RSD LITE to flash VRZ_XT912_9.8.2O-72_VZW-16-5_1FF.xml to boot normally. 9) after booting i check for changes i made , f**k system returns back to default partition table. QUESTIONS 1) where do i go wrong 2) does i have to also make change in "ebr" or "mbr" after changing partitions size 4) does it relate to preinstall and webtop which i left to +1S SECTOR 5)does lineageOS 13.0 need /osh (webtop partitions) because i was flashing saw it searching for /osh for mount 6)does to safe to left the preinstall and webtop to +1S SECTOR
Accessing /dev/block/dm-2 with write access
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?