[SuperR Kitchen] SuperR.:
v3.2.1.0

Changes:

All platforms: Fixed building some img files that were failing with the out of space error.

Linux/WSL/WSL2: Use e2fsdroid for building ext4 img files.

Linux/Mac/Wsl2: Default to using mount for extraction instead of Python (Misc Tools > Extract Options > Use mount extract for img files).

Linux/Mac/WSL2: Fixed all symlinks going in symlinks-system file when using mount to extract a single partition that is not system.

Linux/Mac/WSL2: When using mount for extraction, fixed extracting some newer img files that can only be mounted as read-only.

Added option to turn on/off the case insensitive files fix on all platforms; default is Yes for native Windows, WSL, and WSL2, and default is No for Mac and Linux (Misc Tools > Extract Options > Case insensitive file names fix).

Added option to extract and include all img files without stopping to ask (Misc Tools > Extract Options > Extract and include all img files).

Do not clear username and password during update from disabled version screen if authorization passes.

Hopefully fixed pulling img files from rooted system-as-root devices using adb, and from recovery (may not work in WSL1/2 due to USB connection issues).

Unpack odm.img from payload.bin if it exists.

Added option to create individual dat/dat.br files from the Build EXT4 img menu.

Store project forceencryption type in project srk.conf instead of main srk.conf.

Check for dynamic_partitions_op_list file in firmware package and include it in sparse_dat ROM zip and updater-script.

Remember original file extension for img files and use it when building tar.md5 files from the samsung_tools plugin.

Added support for extracting Samsung Beta firmware with AP_xxxx.tar in a 7z file.

Do not offer to build img files if there is no directory to build from.

Fixed some devices by-name paths not being found during the ROM flash.

Fixed Busybox download not working due to the change in the XDA website recently.

Allow boot.img to unpack in a new project even if there is no default.prop.

Minor security improvements.

The long awaited e2fsdroid update is finally here for Linux, WSL1, and WSL2! e2fsdroid replaces make_ext4fs for building ext4 img files.

I have not been able to compile e2fsdroid for Mac or native Windows so far. However, I was able to fix the out of space issue for many vendor/product.img on these platforms using make_ext4fs.

Native Windows and WSL1 still have issues unpacking vendor.img that crashes with the xattr not defined error. To fix this, the Python ext4 module must be updated. Unfortunately the issue I posted on their github repo has not been answered since June. I strongly recommend native Windows 10 users switch over to WSL2. Here is a thread on how to install WSL2 and the kitchen. I will likely drop support for the native Windows kitchen at some point, so now is a good time to get WSL2 up and running. Regarding kitchen authorization, the native Windows kitchen and WSL1/WSL2 are normally seen as the same PC. Try running it before resetting authorization. It will probably work as it is :)

NOTE:

There is a new plugin, img_tools. It replaces the super_build, ext4_build, and raw2sparse plugins. In addition to those features, it adds resize img and sparse2raw.

THANKS and CREDITS:

@sac23, @Captain_Throwback, and @edzamber for testing and input.

@LonelyFool for separating e2fsdroid source from AOSP.

@superceleron for pointing me to the e2fsdroid source and help with usage.