[Samsung Galaxy Watch 4] adfree:
Seems old Tools not help with new Firmware... to extract files...

Any ideas how to solve this problem?

asus@asusEEE:~$ cd imj
asus@asusEEE:~/imj$ cd newimj
asus@asusEEE:~/imj/newimj$ ./imjtool boot.img extract
boot.img: Android Boot image v4 for OS ver 0x1a000176 (13.128 Patch Level 2023-6)
Found GZ Magic at offset 6107556
gzip: extracted/kernelimage.gz: unknown method 0 -- not supported
Unable to locate device tree
asus@asusEEE:~/imj/newimj$ ./imjtool recovery.img extract
recovery.img: Android Boot image v2 for OS ver 0x1a000176 (13.128 Patch Level 2023-6)(1660 byte header)
Device Tree(@0x3ce4000): 112328 55 0x10000000
Recovery DTBO/ACPIO: 1048576
AVB0 (@0x3e00000): 2112
AVBf (@0x5ffffc0):
Tags: 0x10000000
Flash Page Size: 2048 bytes
ID: 4329bf1d997cd4d8208ab39c2b0bce56ff2afaa000
Found GZ Magic at offset 6107556
gzip: extracted/kernelimage.gz: unknown method 0 -- not supported
Searching for DT at 0x3ce4000
- exists so renaming to ./_dtboasus@asusEEE:~/imj/newimj$ ./imjtool init_boot.img extract
init_boot.img: Android Boot image v4 for OS ver 0x1a000176 (13.128 Patch Level 2023-6)
Can't find GZ, LZO *or* LZ4 signature here... won't decompress
Unable to locate device tree
asus@asusEEE:~/imj/newimj$ ./imjtool vendor_boot.img extract
Vendor boot image version 4 detected (2128 bytes)
Page Size: 0x800
Kernel loaded to: 0x10008000, Ramdisk loaded to 0x10000000
Vendor ramdisk: 10519088 bytes
Name: SRPWC10F001
Tags: @0x10000000
DTB: 112328 bytes loaded to 0x11f00000
Cmdline: bootconfig loop.max_part=7
Ramdisk table - 2 entries x 108 bytes, (216 bytes total)
0: (Type: 1, 0x2388a3 bytes @0x0)
1: dlkm (Type: 3, 0x7cf98d bytes @0x2388a3)
Boot Config: 28
buildtime_bootconfig=enable

Didn't get to support extraction yet, but with offsets dd can be a quick workaround in the interim
asus@asusEEE:~/imj/newimj$ ./imjtool super.img extract
super.img: Android Sparse Image v1.0 - 1392640 blocks of 4096 bytes compressed into 83 chunks (15% compressed)
0 - Extracted image is in extracted/image.img
asus@asusEEE:~/imj/newimj$ ./imjtool image.img extract
MMapped: 0x7f820f97a000, imgMeta 0x7f820f97b000
liblp dynamic partition (super.img) - Blocksize 0x1000, 2 slots
LP MD Header @0x3000, version 10.0, with 4 logical partitions @0x0 on block device of 5440 GB, at partition super, first sector: 0x800
Partitions @0x3080 in 2 groups:
Group 0: default
Group 1: group_basic
Name: system (read-only, Huawei EROFS Filesystem Image, @0x100000 spanning 1 extents of 4 GB) - extracted
Name: vendor (read-only, Huawei EROFS Filesystem Image, @0x101400000 spanning 1 extents of 137 MB) - extracted
Name: product (read-only, Huawei EROFS Filesystem Image, @0x109e00000 spanning 1 extents of 422 MB) - extracted
Name: odm (read-only, Huawei EROFS Filesystem Image, @0x124500000 spanning 1 extents of 1 MB) - extracted
asus@asusEEE:~/imj/newimj$ ./imjtool odm.img extract
Huawei EROFS (not handled yet)

First hint seems this...

Huawei EROFS Filesystem Image

Best Regards

Edit 1.

Okidoki...

Seems Android 13 Feature...

[UPDATE: Not Necessarily] Android 13 Devices Will Use Huawei's EROFS File System Format

UPDATE: It seems like Google changed its mind. EXT4 and F2FS will also be allowed, according to Mishaal Rahman. ORIGINAL ARTICLE: All devices intending to

www.androidheadlines.com

Now I need only Tools to extract super.img...

I mean system.img etc...

As first step seems not changed... IMHO...

Edit 2.

Home of imjtool... memo to me:

imjtool - A tool for unpacking Android boot and system images