[TOOL][WIN,LIN,AND,DARW] Super image tools | extract or make partitions RW in super partition

Search This thread

munjeni

Senior Member
Jun 2, 2011
9,273
21,908
I'm just compiled e2fsprogs excatly the same source code used in my tool, definitelly its not a source of problem. This is result:

Code:
[email protected] /media/hdd/sony/rom # ../android_external_e2fsprogs/e2fsck/e2fsck -fy -E unshare_blocks /dev/loop0
e2fsck 1.45.4 (23-Sep-2019)
Pass 1: Checking inodes, blocks, and sizes
Inode 3728 extent tree (at level 2) could be narrower.  Optimize? yes

Inode 6180 extent tree (at level 2) could be narrower.  Optimize? yes

Inode 6203 extent tree (at level 1) could be narrower.  Optimize? yes

Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/: ***** FILE SYSTEM WAS MODIFIED *****
/: 6478/7168 files (10.0% non-contiguous), 477547/494679 blocks
[email protected] /media/hdd/sony/rom # ../android_external_e2fsprogs/e2fsck/e2fsck -fy -E unshare_blocks /dev/loop0
e2fsck 1.45.4 (23-Sep-2019)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/: 6478/7168 files (10.0% non-contiguous), 477547/494679 blocks
[email protected] /media/hdd/sony/rom # ../android_external_e2fsprogs/e2fsck/e2fsck -fy /dev/loop0
e2fsck 1.45.4 (23-Sep-2019)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/: 6478/7168 files (10.0% non-contiguous), 477547/494679 blocks
[email protected] /media/hdd/sony/rom #

As you can see its clean. I have no idea right now why you getting that error, it might be your kernel related thing. Did you tried @lebigmac script -> https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/ ?
 
  • Haha
Reactions: lebigmac

munjeni

Senior Member
Jun 2, 2011
9,273
21,908
Can you please dump sustem partition this way and upload somewhere?

Code:
/data/local/tmp/losetup --offset=1648361472 --sizelimit=2895020032 /dev/block/loop9 /dev/block/sde26
dd if=/dev/block/loop9 of=/data/local/tmp/system.bin conv=notrunc
/data/local/tmp/losetup -d /dev/block/loop9

Give me please /data/local/tmp/system.bin dump file and I will check all the things localy and try find whats going on with it detaily
 
Last edited:

PEACH-PIT

Senior Member
Jan 22, 2018
74
16
I'll upload it.
I will contact you directly through "Conversations" as soon as the upload is complete.

Uploaded system.bin.
Please check it.
 
Last edited:
  • Like
Reactions: munjeni

munjeni

Senior Member
Jun 2, 2011
9,273
21,908
Hi, I have checked your system dump using excatly the same tools, it succed without any single error, see log! I realy have no idea why it fail on your device, I'm believing thats kernel related thing, did you see something about it inside dmesg? It might be other restrictions enabled on device! Try research about error "Could not allocate block in ext2 filesystem"! It can be that something need to be enabled in proc or sys entries, for idea look here https://01.org/linuxgraphics/gfx-docs/drm/admin-guide/ext4.html
 

Attachments

  • log.zip
    15.4 KB · Views: 7
Last edited:

PEACH-PIT

Senior Member
Jan 22, 2018
74
16
Can I just dump the kernel log?

I looked it up but couldn't figure it out.

Unfortunately, I can't get this script to work on my device.
 
Last edited:
  • Like
Reactions: munjeni

f1^ter

Member
Jan 8, 2016
45
40
32
Nadym
Sony Xperia 1 II
The device Xperia 1 II, I can't get the system_a section to write, I attach the log.

The mistake was mine, wrongly pointed out the path!
Code:
./superrepack /dev/block/bootdevice/by-name/super system_a rw
./superrepack /dev/block/bootdevice/by-name/super product_a rw
Everything works! Thanks!
 

Attachments

  • Logs_superrepack_v9.txt
    142.3 KB · Views: 14
Last edited:
  • Like
Reactions: munjeni

munjeni

Senior Member
Jun 2, 2011
9,273
21,908
The device Xperia 1 II, I can't get the system_a section to write, I attach the log.

The mistake was mine, wrongly pointed out the path!
Code:
./superrepack /dev/block/bootdevice/by-name/super system_a rw
./superrepack /dev/block/bootdevice/by-name/super product_a rw
Everything works! Thanks!
Hi, thanks but unfortunatelly you have the same error as @PEACH-PIT , things is not done right!

clone_file: Could not allocate block in ext2 filesystem returned from clone_file_block

I'm curently without idea since I do not have device with super partition to do the true test. I'm tested things on my local linux machine, I'm used super partition from xperia 1 II rom version XQ-AT51 58.1.A.5.55-R15B and it succed, I have no idea why it fail on phone. I'm using excatly the same e2fsprogs version as in this tool, I'm believing that there need to be done something to the /proc/sys/.... or probably some more protections need to be disabled. Did anybody tried my tool in recovery mode?

It can be truly tested on dumped system image! E.g:

Code:
adb shell
su
stop
cd /data/local/tmp
dd if=/dev/block/bootdevice/by-name/super of=/data/local/tmp/super.bin conv=notrunc
/data/local/tmp/superrepack /data/local/tmp/super.bin system_a rw
sync

If it succed without errors than you probably can write it back it to the block device:

Code:
dd if=/data/local/tmp/super.img of=/dev/block/bootdevice/by-name/super conv=notrunc
sync
 
Last edited:

munjeni

Senior Member
Jun 2, 2011
9,273
21,908
Can I just dump the kernel log?

I looked it up but couldn't figure it out.

Unfortunately, I can't get this script to work on my device.
if you do dmesg right now it will not contain the possible things, It must be done in the moment till after my tool
 

munjeni

Senior Member
Jun 2, 2011
9,273
21,908
Tried right now latest rom from xperia 1 II, rom vesion XQ-AT52_Customized SEA_58.1.A.5.159-R2B, apsolutly no errors. So definitelly something inside phone need to be done to allow clone blocks. Did you guys doing "adb shell stop"? That command is important to stop all the activity on the phone before use our tool! I can suggest you try this first and let me know:

Code:
adb shell
su
stop
cd /data/local/tmp
dd if=/dev/block/bootdevice/by-name/super of=/data/local/tmp/super.bin conv=notrunc
/data/local/tmp/superrepack /data/local/tmp/super.bin system_a rw
sync

change /dev/block/bootdevice/by-name/super to your super partition location
 

PEACH-PIT

Senior Member
Jan 22, 2018
74
16
Tried right now latest rom from xperia 1 II, rom vesion XQ-AT52_Customized SEA_58.1.A.5.159-R2B, apsolutly no errors. So definitelly something inside phone need to be done to allow clone blocks. Did you guys doing "adb shell stop"? That command is important to stop all the activity on the phone before use our tool! I can suggest you try this first and let me know:

Code:
adb shell
su
stop
cd /data/local/tmp
dd if=/dev/block/bootdevice/by-name/super of=/data/local/tmp/super.bin conv=notrunc
/data/local/tmp/superrepack /data/local/tmp/super.bin system_a rw
sync

change /dev/block/bootdevice/by-name/super to your super partition location
Where is the super.bin?
It's not in the official stock rom.
Just renaming the dumped system.bin did not work.
 

f1^ter

Member
Jan 8, 2016
45
40
32
Nadym
Sony Xperia 1 II
Hi, thanks but unfortunatelly you have the same error as @PEACH-PIT , things is not done right!

clone_file: Could not allocate block in ext2 filesystem returned from clone_file_block

I'm curently without idea since I do not have device with super partition to do the true test. I'm tested things on my local linux machine, I'm used super partition from xperia 1 II rom version XQ-AT51 58.1.A.5.55-R15B and it succed, I have no idea why it fail on phone. I'm using excatly the same e2fsprogs version as in this tool, I'm believing that there need to be done something to the /proc/sys/.... or probably some more protections need to be disabled. Did anybody tried my tool in recovery mode?

It can be truly tested on dumped system image! E.g:

Code:
adb shell
su
stop
cd /data/local/tmp
dd if=/dev/block/bootdevice/by-name/super of=/data/local/tmp/super.bin conv=notrunc
/data/local/tmp/superrepack /data/local/tmp/super.bin system_a rw
sync

If it succed without errors than you probably can write it back it to the block device:

Code:
dd if=/data/local/tmp/super.img of=/dev/block/bootdevice/by-name/super conv=notrunc
sync
Unfortunately, it did not give the result, I attach the log.
But, if I enter the commands:
Code:
./superrepack /dev/block/bootdevice/by-name/super system_a rw
./superrepack /dev/block/bootdevice/by-name/super product_a rw
then it works. And you can delete folders (applications) from the product section. It turns out there is write access.
 

Attachments

  • Logs_superrepack_v9_2.txt
    142.1 KB · Views: 7

munjeni

Senior Member
Jun 2, 2011
9,273
21,908
Unfortunately, it did not give the result, I attach the log.
But, if I enter the commands:
Code:
./superrepack /dev/block/bootdevice/by-name/super system_a rw
./superrepack /dev/block/bootdevice/by-name/super product_a rw
then it works. And you can delete folders (applications) from the product section. It turns out there is write access.
You have the same problem like PEACH-PIT , reparation is not done right because clone blocks didn't suced, and filesystem have ton of problems, for example if you delete some file which use shared blocks you will delete a ton of files without knowing that! So wait until we figure out problem.
 
  • Like
Reactions: f1^ter

munjeni

Senior Member
Jun 2, 2011
9,273
21,908
How about this?
I realy want to help and make it fully working for everybody, but your dmesg didn't help since its probably dmesg long time ago after you executed my tool. You must catch dmesg in moment till after you use my tool e.g. in next 10 - 20 secconds after my tool finish! You can do booth dmesg and logcat e.g.

dmesg > /data/local/tmp/dmesg.log
logcat > /data/local/tmp/logcat.log
 

Top Liked Posts

  • 1
    So yeah, it doesn't work. My device is again stuck at the Sony logo.
    I executed the script till I saw no change in the log/ cmd window. I attached the logs.
    1
    I already did that, i have the superrepack file, with that exactly name, but still, i get that error
    /system/bin/sh: /data/local/tmp/superrepack: No such file or directory mean that superrepack is not inside /data/local/tmp directory or your android missing some libraries. Libraries needed for our tool is:

    Interpreter '/system/bin/linker64'
    Needed Library 'libcrypto.so'
    Needed Library 'libc.so'
    Needed Library 'libm.so'
    Needed Library 'libdl.so'

    if you have missing any of those I can't help. If you can't get it to work you should try https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
    1
    I don't see any error in your logs, is your device bootloader unlocked?
    Yes, it is.
    1
    So I reflashed stock rom, booted one time, flashed the patched image to boot_a and boot_b. Im getting a "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds." screen. Flashing the normal Magisk img works and the device boots with Magisk 22.1. If I reflash your patched img it shows me the "Your device is corrupt." screen again.
  • 3
    Pixel 4a, working. V13
    2
    Tried it out, kinda doesn't work.
    The script.log doesn't get filled out.

    My Device is an Sony Xperia 5ii on Android 11 with the currently latest version EEA_58.1.A.5.159.

    Here's the log from my cmd window (I did run that tool several times, I don't know which run is this):
    2
    Explained allready 3-4 times, last one is inside post 152! If you compare it with first post and changelog you will notice that resize & repair is inplemented inside version 5 and up, all version before version 5 is bad because partitions get damaged and dangerous since resize & repair feature is not implemented before version 5. If you folow more posts yo can see that even latest version fail to e2fsck on some phones. Inside post 152 is clean instructions and explanation.
    1
    Hello.
    Thanks for the great tool.
    This tool did not work on my device (Moto G 5G XT2113-3).
    The partition it is used on shows "Error, no free loop device!"

    kiev:/ $ su
    su
    kiev:/ # chmod 755 /data/local/tmp/superrepack
    chmod 755 /data/local/tmp/superrepack
    kiev:/ # setenforce 0
    setenforce 0
    kiev:/ # /data/local/tmp/superrepack /dev/block/sde26
    /data/local/tmp/superrepack /dev/block/sde26
    ---------------------------------------------------------
    Super image repacker v_7 by munjeni @ xda 2021)
    ---------------------------------------------------------

    Removing shared_blocks and making RW on all partitions!

    LpMetadataGeometry magic = 0x616c4467
    LpMetadataGeometry struct size = 0x34
    LpMetadataGeometry sha256 = 12FF55F0ABA7B506F25CB5DA5DCA09344234E8DF1D9C93AE82A499D98019467E
    LpMetadataGeometry metadata_max_size = 0x10000
    LpMetadataGeometry metadata_slot_count = 0x3
    LpMetadataGeometry logical_block_size = 0x1000

    LpMetadataHeader magic = 0x414c5030
    LpMetadataHeader major_version = 10
    LpMetadataHeader minor_version = 0
    LpMetadataHeader header_size = 0x80
    LpMetadataHeader header sha256 = F66EEAAA572D08E442CD5AC309590C182A4716582C8AC66BFCFF9B5EE1EF82BC
    LpMetadataHeader tables_size = 0x268
    LpMetadataHeader tables sha256 = 968E2E2AAEF7A8389AFCD94A2269A8DD00123C158643757570F00E008E44BBC3
    LpMetadataHeader partitions offset = 0x0
    LpMetadataHeader partitions num_entries = 0x6
    LpMetadataHeader partitions entry_size = 0x34
    LpMetadataHeader extents offset = 0x138
    LpMetadataHeader extents num_entries = 0x4
    LpMetadataHeader extents entry_size = 0x18
    LpMetadataHeader groups offset = 0x198
    LpMetadataHeader groups num_entries = 0x3
    LpMetadataHeader groups entry_size = 0x30
    LpMetadataHeader block_devices offset = 0x228
    LpMetadataHeader block_devices num_entries = 0x1
    LpMetadataHeader block_devices entry_size = 0x40

    Partitions = 4 used, 2 not used, total 6

    partition_1_name = system_a
    attributes = 0x1
    first_extent_index = 0x0
    num_extents = 0x1
    group_index = 0x1
    partition_group = mot_dp_group_a
    extent num_sectors = 0x19afe8 (0x335fd000 bytes total)
    extent target_type = 0x0
    extent target_data = 0x800 (dumping offset = 0x100000)
    extent target_source = 0x0
    sh: ./busybox: inaccessible or not found
    Partition: system_a | EXT4 | 0x328f1000 | 4729639D-B5F2-5CC1-A120-9AC5F788683C | 0x0000407B | Error, no free loop device!

    partition_2_name = system_b
    attributes = 0x1
    first_extent_index = 0x1
    num_extents = 0x1
    group_index = 0x2
    partition_group = mot_dp_group_b
    extent num_sectors = 0xb388 (0x1671000 bytes total)
    extent target_type = 0x0
    extent target_data = 0x19b800 (dumping offset = 0x33700000)
    extent target_source = 0x0
    sh: ./busybox: inaccessible or not found
    Partition: system_b | EXT4 | 0x1603000 | F5CFDC49-271C-5243-83DA-4FED7A45C3EA | 0x0000407B | Error, no free loop device!

    partition_3_name = vendor_a
    attributes = 0x1
    first_extent_index = 0x2
    num_extents = 0x1
    group_index = 0x1
    partition_group = mot_dp_group_a
    extent num_sectors = 0x16ad48 (0x2d5a9000 bytes total)
    extent target_type = 0x0
    extent target_data = 0x1a7000 (dumping offset = 0x34e00000)
    extent target_source = 0x0
    sh: ./busybox: inaccessible or not found
    Partition: vendor_a | EXT4 | 0x2ca20000 | 2B96C597-1E2F-5EE1-9851-C4A9FA9DE36E | 0x0000407B | Error, no free loop device!

    partition_4_name = vendor_b (unused)
    attributes = 0x1
    first_extent_index = 0x3
    num_extents = 0x0
    group_index = 0x2
    partition_group = mot_dp_group_b
    extent num_sectors = 0x564740 (0xac8e8000 bytes total)
    extent target_type = 0x0
    extent target_data = 0x312000 (dumping offset = 0x62400000)
    extent target_source = 0x0
    sh: ./busybox: inaccessible or not found
    Partition: vendor_b | EXT4 | 0xa9d43000 | 453968FF-B43C-54B7-A506-A6A88682C128 | 0x0000407B | Error, no free loop device!

    partition_5_name = product_a
    attributes = 0x1
    first_extent_index = 0x3
    num_extents = 0x1
    group_index = 0x1
    partition_group = mot_dp_group_a
    extent num_sectors = 0x564740 (0xac8e8000 bytes total)
    extent target_type = 0x0
    extent target_data = 0x312000 (dumping offset = 0x62400000)
    extent target_source = 0x0
    sh: ./busybox: inaccessible or not found
    Partition: product_a | EXT4 | 0xa9d43000 | 453968FF-B43C-54B7-A506-A6A88682C128 | 0x0000407B | Error, no free loop device!

    partition_6_name = product_b (unused)
    attributes = 0x1
    first_extent_index = 0x4
    num_extents = 0x0
    group_index = 0x2
    partition_group = mot_dp_group_b
    extent num_sectors = 0x746c7561666564 (0xe8d8eac2cccac800 bytes total)
    extent target_type = 0x0
    extent target_data = 0x0 (dumping offset = 0x0)
    extent target_source = 0x0
    Partition: product_b | UNKNOWN | U | U | U | skipping
    kiev:/ # /data/local/tmp/superrepack /dev/block/sde26

    I followed the tutorial.

    I am not good at English.
    You must go to the /data/local/tmp !!! And you must do excatly the same as from tutorial from first post and it will work than!

    How to use superrepack:

    adb push superrepack.arm64_pie /data/local/tmp
    adb shell
    cd /data/local/tmp
    mv superrepack.arm64_pie superrepack
    chmod 755 superrepack
    stop
    ./superrepack /dev/block/bootdevice/by-name/super system_a rw
    sync
    reboot
    1
    So I reflashed stock rom, booted one time, flashed the patched image to boot_a and boot_b. Im getting a "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds." screen. Flashing the normal Magisk img works and the device boots with Magisk 22.1. If I reflash your patched img it shows me the "Your device is corrupt." screen again.
  • 24
    Disclaimer:

    Super image tools was made for testing and educational purposes, ME is not responsible for what you do on/with your device using our tools, you must agree that you using our tools on your own risk, I am not responsible for anything else!


    How to use superunpack:

    - First step, unpack super.sin using my tool or use @IgorEisberg unsin tool
    - Step two, Superunpack. On windows just drag and drop unpacked super image onto our exe to start extraction. Also you can use it from command line, from script or from etc. On Linux use it from command line. No need to set slot like it was a case on lpunpack, our tool will auto extract all slot images for you, enjoy!
    - If you need to unpack partition images in RW mode add parameter 1 at the end of command line e.g. "superunpack super.img 1", than resize partition using resize2fs, repair and unshare blocks using e2fsck. Or if you unpack without rw you no need to resize or repair it, just mount it ro.

    Note that, superunpack is a tool for extract all logical partitions from super image or directly from super partition.

    How to use superrepack:

    adb push superrepack.arm64_pie /data/local/tmp
    adb shell
    su
    cd /data/local/tmp
    mv superrepack.arm64_pie superrepack
    chmod 755 superrepack
    stop
    ./superrepack /dev/block/bootdevice/by-name/super system_a
    sync
    reboot

    Note that, superrepack is a tool to convert logical RO partitions iside your phone super partition to RW mode. In this example system_a partiton is converted to the rw mode, if you need other partitions to rw just change system_a argument. Or if you need all partitions to rw mode do it without partition rw argumet e.g: "./superrepack /dev/block/bootdevice/by-name/super". YOU MUST RUN TOOL 4-5 TIMES UNTIL ALL ERRORS DISAPEARS!!! One of the well known errors is: "Couldn't clone file: Could not allocate block in ext2 filesystem". Look at /data/local/tmp/script.log each time and make sure it not contain any error otherwise you are not done things right and partition is not repaired yet!!! More info -> https://forum.xda-developers.com/t/...s-rw-in-super-partition.4120963/post-84966715

    Platform:

    - Superunpack is working on Windows, Linux, Android, Darwin11, just chose right binary.
    - Superrepack is working only under android


    Changelog:

    - version 1 (21.Jun.2020), initial version
    - version 1.1 (22.Jun.2020), dump file format detection, partition size correction in case ext4, partition group detection, have extraction progress bar, improvements
    - version 2 (03.04.2021) implemented possibility to extract partition images to rw mode using Superunpack & I have made new tool called Superrepack
    - version 2 (04.04.2021) implemented arguments so you would do conversion on single partition instead of doing it on all partitions
    - version 3 (04.04.2021) implemented return codes and implemented output logs to be more scripting friendly
    - version 4 - not released
    - version 5 (08.04.2021) implemented resize and repair partitions after switching to rw mode. Implemented build script for building resize2fs, e2fsck, simg2ims, img2simg, lptools
    - version 6 (08.04.2021) better loop device detection and setup
    - version 7 (08.04.2021) fix selinux status detection
    - version 8 (15.04.2021) fix loop device setup in superrepack
    - version 9 (16.04.2021) make losetup android compatible
    - version 10 - not released
    - version 11 (01.05.2021) simplified, removed needs for parameter rw, implemented dm-verity disabler
    - version 12 (05.05.2021) make old logs always deleted before fresh log is created, this prevent concentation with old logs
    - version 13 (06.05.2021) make linux version so you should do the things on your super partition dump in linux machine
    - version 14 (07.05.2021) fix compilation mess between linux and android
    - version 15 (08.05.2021) use libselinux to determine and set selinux to permissive mode instead of popening getenforce-setenforce tools

    Credits:

    - me and me :)


    Source code:

    - source code -> https://github.com/munjeni/super_image_dumper
    12
    I'm not one of those who make paid software and promote on xda, my work is always free. Even I'm always providing source code for free, source code of this tool is here -> https://github.com/munjeni/super_image_dumper , enjoy! ;)
    3
    Version 7 is out! V6 had error detecting slinux status. I do not have device with super partition for test my tool but I have only hope that all is ok. Let me know! :)
    3
    Pixel 4a, working. V13
    2
    New version is out, v11, it now detect file format, partition size correction in case ext4, partition group detection, have extraction progress bar, and it looks like:

    Code:
    ---------------------------------------------------------
    Super image dumper v_11 (by expert :) munjeni @ xda 2020)
    ---------------------------------------------------------
    
    LpMetadataGeometry magic = 0x616c4467
    LpMetadataGeometry struct size = 0x34
    LpMetadataGeometry sha256 = 12FF55F0ABA7B506F25CB5DA5DCA09344234E8DF1D9C93AE82A499D98019467E
    LpMetadataGeometry metadata_max_size = 0x10000
    LpMetadataGeometry metadata_slot_count = 0x3
    LpMetadataGeometry logical_block_size = 0x1000
    
    LpMetadataHeader magic = 0x414c5030
    LpMetadataHeader major_version = 10
    LpMetadataHeader minor_version = 0
    LpMetadataHeader header_size = 0x80
    LpMetadataHeader header sha256 = CCF4F5D07842AAAE7C1B87F0E025512CF7AEA426D477B1E5175DA3D74F9B1C8C
    LpMetadataHeader tables_size = 0x2e8
    LpMetadataHeader tables sha256 = 52578668F89D8BCDA1BD1F748F2F69ED874C10A7062C85EF9970EE05D90161B1
    LpMetadataHeader partitions offset = 0x0
    LpMetadataHeader partitions num_entries = 0x8
    LpMetadataHeader partitions entry_size = 0x34
    LpMetadataHeader extents offset = 0x1a0
    LpMetadataHeader extents num_entries = 0x5
    LpMetadataHeader extents entry_size = 0x18
    LpMetadataHeader groups offset = 0x218
    LpMetadataHeader groups num_entries = 0x3
    LpMetadataHeader groups entry_size = 0x30
    LpMetadataHeader block_devices offset = 0x2a8
    LpMetadataHeader block_devices num_entries = 0x1
    LpMetadataHeader block_devices entry_size = 0x40
    
    Partitions = 5 used, 3 not used, total 8
    
      partition_1_name = system_a
        attributes = 0x1
        first_extent_index = 0x0
        num_extents = 0x1
        group_index = 0x1
        partition_group = somc_dynamic_partitions_a
        extent num_sectors = 0x336390 (0x66c72000 bytes total)
        extent target_type = 0x0
        extent target_data = 0x800 (dumping offset = 0x100000)
        extent target_source = 0x0
          Filetype EXT4. EXT4 size = 0x6526c000
          Dumping system_a.ext4 ...
          ....................................................
          ....................................................
          ....................................................
          ..............................................
      partition_2_name = system_b
        attributes = 0x1
        first_extent_index = 0x1
        num_extents = 0x1
        group_index = 0x2
        partition_group = somc_dynamic_partitions_b
        extent num_sectors = 0xab178 (0x1562f000 bytes total)
        extent target_type = 0x0
        extent target_data = 0x337000 (dumping offset = 0x66e00000)
        extent target_source = 0x0
          Filetype EXT4. EXT4 size = 0x150b3000
          Dumping system_b.ext4 ...
          ..........................................
      partition_3_name = product_a
        attributes = 0x1
        first_extent_index = 0x2
        num_extents = 0x1
        group_index = 0x1
        partition_group = somc_dynamic_partitions_a
        extent num_sectors = 0x2b62b8 (0x56c57000 bytes total)
        extent target_type = 0x0
        extent target_data = 0x3e2800 (dumping offset = 0x7c500000)
        extent target_source = 0x0
          Filetype EXT4. EXT4 size = 0x5565b000
          Dumping product_a.ext4 ...
          ....................................................
          ....................................................
          ....................................................
          ..............
      partition_4_name = product_b (not unused)
        attributes = 0x1
        first_extent_index = 0x3
        num_extents = 0x0
        group_index = 0x2
        partition_group = somc_dynamic_partitions_b
        extent num_sectors = NULL
        extent target_type = NULL
        extent target_data = NULL
        extent target_source = NULL
          Skipping dump.
    
      partition_5_name = vendor_a
        attributes = 0x1
        first_extent_index = 0x3
        num_extents = 0x1
        group_index = 0x1
        partition_group = somc_dynamic_partitions_a
        extent num_sectors = 0x186d58 (0x30dab000 bytes total)
        extent target_type = 0x0
        extent target_data = 0x699000 (dumping offset = 0xd3200000)
        extent target_source = 0x0
          Filetype EXT4. EXT4 size = 0x30141000
          Dumping vendor_a.ext4 ...
          ....................................................
          ............................................
      partition_6_name = vendor_b (not unused)
        attributes = 0x1
        first_extent_index = 0x4
        num_extents = 0x0
        group_index = 0x2
        partition_group = somc_dynamic_partitions_b
        extent num_sectors = NULL
        extent target_type = NULL
        extent target_data = NULL
        extent target_source = NULL
          Skipping dump.
    
      partition_7_name = odm_a
        attributes = 0x1
        first_extent_index = 0x4
        num_extents = 0x1
        group_index = 0x1
        partition_group = somc_dynamic_partitions_a
        extent num_sectors = 0xa60 (0x14c000 bytes total)
        extent target_type = 0x0
        extent target_data = 0x820000 (dumping offset = 0x104000000)
        extent target_source = 0x0
          Filetype EXT4. EXT4 size = 0x132000
          Dumping odm_a.ext4 ...
    
      partition_8_name = odm_b (not unused)
        attributes = 0x1
        first_extent_index = 0x5
        num_extents = 0x0
        group_index = 0x2
        partition_group = somc_dynamic_partitions_b
        extent num_sectors = NULL
        extent target_type = NULL
        extent target_data = NULL
        extent target_source = NULL
          Skipping dump.
    Press any key to continue . . .

    If you need to mount ext4 partition on Linux you need to mount partition RO or it will not mount!
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone