Cannot get Samsung device (b4q) dump

[angelwingsjp]

Device: Samsung Galaxy Z Flip4 (SM-F721B, b4q)

Log:

...
boot_kallsyms.txt generated
boot.elf generated
dtbo extracted
find: ‘/home/nio/dumpyara/working/SAMFW.COM_SM-F721B_EUX_F721BXXS5EXAB_fac/bootimg’: No such file or directory
Trying to extract system partition via fsck.erofs.
<E> erofs: cannot find valid erofs superblock
<E> erofs: failed to read superblock
Trying to extract system_ext partition via fsck.erofs.
<E> erofs: cannot find valid erofs superblock
<E> erofs: failed to read superblock
Trying to extract vendor partition via fsck.erofs.
<E> erofs: cannot find valid erofs superblock
<E> erofs: failed to read superblock
Trying to extract odm partition via fsck.erofs.
<E> erofs: cannot find valid erofs superblock
<E> erofs: failed to read superblock
Trying to extract product partition via fsck.erofs.
<E> erofs: cannot find valid erofs superblock
<E> erofs: failed to read superblock
Trying to extract vendor_dlkm partition via fsck.erofs.
<E> erofs: cannot find valid erofs superblock
<E> erofs: failed to read superblock
find: ‘/home/nio/dumpyara/working/SAMFW.COM_SM-F721B_EUX_F721BXXS5EXAB_fac/modem’: No such file or directory
find: ‘/home/nio/dumpyara/working/SAMFW.COM_SM-F721B_EUX_F721BXXS5EXAB_fac/tz*’: No such file or directory
No system build*.prop found, pushing cancelled!

[AntoninoScordino]

Samsung's 2022 devices employ the F2FS file system for logical partitions such as system.img and vendor.img, for which we presently do not have support. A potential workaround is the manual transfer of files from a mounted image using the loop option and the correct permissions, although various attempts at this method have not been successful in our case.