yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] SuperR.:
v3.1.4.8

Changes:

Menus with more than 10 options, less than 31 options, and 22 characters or less per option are now displayed in columns.

Allow extracting odm.img by itself.

Disable set_perm perm type for KitKat and above firmware.

NOTES: The samextras and xiaomi_patch plugins have also been updated to accommodate some internal changes. They must be updated to work with the new kitchen.
[SuperR Kitchen] SuperR.:
v3.1.4.9

Changes:

Fixed ramdisk errors, again.
[SuperR Kitchen] SuperR.:
v3.1.5.0

Changes:

Added support for extracting zips that include payload.bin.

Prepare kitchen updater for partial incremental updates, starting with the next update.

NOTES:

What makes the incremental updates partial? The incremental updates will only be used for consecutive updates. For example, if you are running v3.1.5.0 and updating to v3.1.5.1, the kitchen will download an update zip with only the changed files since v3.1.5.0. However, if you are running v3.1.4.8 and updating to v3.1.5.1, the kitchen will download a full kitchen zip. This way you will always get the latest files. It is too much work to make incremental updates from every old version to the latest version, so this is the compromise.

Why do incremental updates? As new features are added, more new libraries will be required making the zips larger over time. With the addition of payload.bin extraction, the zips are larger due to the Google protobuf library dependency. This will not be the last new feature, so steps are being taken to cut down on data transfer now. If you are a frequent updater, you will save some bandwith and so will my server :)

Thanks to @iuss - The kitchen implementation of payload.bin extraction is based on his payload_dumper.py. I only made a few modifications to allow running as a module and to extract specific img files (instead of all img files). Please thank his post :)

EDIT:

LINUX/MAC USERS: I just noticed the plugin updater has issues with the samextras and xiaomi_patch plugins. If you have used the plugin updater and have a problem running these plugins, remove them, re-install, and all will be good. The plugin updater will be fixed in the next update. This issue affects Linux and Mac users only.
[SuperR Kitchen] SuperR.:
v3.1.5.1

Changes:

Fixed plugin updater not updating plugins that modify ramdisk correctly.

Display file name and file size of all downloads while downloading.

Updated estimation of tools download size to be more acurate.

Hide lz4 output while decompressing img files.

Provide more progress information when extracting Samsung firmware.

EDIT: There was an issue on the server that may have caused a crash during the new incremental update. I believe it is fixed now. Sorry for the inconvenience if you were affected.
[SuperR Kitchen] SuperR.:
v3.1.5.2

Changes:

Fixed adb permission error when extracting img files from device booted to Android.

Pull img files directly to PC and skip the device storage when extracting from device booted to Android.

Busybox is no longer required on device to pull img files when extracting from device booted to Android.

Do not ask for by-name path unless it is needed for the operation you are performing.

Fixed crash when installing plugins in Windows.
[SuperR Kitchen] SuperR.:
v3.1.5.3

Changes:

Fixed kitchen updater not completing properly and saying it failed.

Fixed updater-script error about file_j.getprop.
[SuperR Kitchen] SuperR.:
v3.1.5.4

Changes:

Fixed rare bug where the file context list can become empty causing all files to use the general system_file context in set_metadata updater-script.

Use file_contexts file as fallback when extracting a system.img if the system.img does not have contexts set.

Fixed crash when reading file_contexts file if it contains unexpected characters or lines.

Do not allow building system.img from the build menu if Android API is 21 or higher and we can't find file_contexts.

Inform of plugin crashes instead of crashing the kitchen.

Log plugin crashes in plugin.log.

Updated configure.sh to work with more devices.

NOTES:

The Mac/OSX version will remain at v3.1.5.3 until further notice. It is a pain to build and literally 0 people are using it.

The kitchen updater should be working now if you are currently running v3.1.5.3. All previous versions...I have no idea. Sorry again for all the trouble transitioning to the new system. I appreciate all your patience :)

OTHER NEWS:

The xiaomi_patch plugin has been fixed and updated to work with Android 8.1 (hopefully lol)
[SuperR Kitchen] SuperR.:
v3.1.5.5

Changes:

Ask if you would like to save your kitchen password (hashed) so you don't need to manually log in every time you start the kitchen.

Samsung: When extracting firmware, ask if you want to extract extra partitions (recovery.img, aboot.mbn, sboot.bin, NON-HLOS.bin, modem.bin, sbl1.mbn, sdi.mbn, rpm.mbn, and tz.mbn if they exist).

Samsung: Extract odm.img by default if it exists in the firmware.

Samsung: When using AutoROM, do not stop to tell you there is no csc.zip in your cache.img.

Do not include modem.bin in rom.zip root if it exists in ROM directory.

NOTES:

Hopefully this update will make a few of you smile. I know the required password is irritating... now you have the option to save it so you don't have to enter it anymore! Internet is still required and credentials will still be checked, but at least you don't have to type it manually if you don't want to :)

You will be asked if you want to save your password exactly once. If you say no, you will always be asked for your password. If you say yes, you will never be asked for your password again until your next fresh install.

OTHER NEWS:

autorom_config plugin has been updated to include extracting the Samsung extra partitions mentioned above.
[SuperR Kitchen] SuperR.:
v3.1.5.6

Changes:

Samsung: Fixed vendor not being extracted.

Added support for HTC devices that use system_other.img.

Modified the error message when pulling system.img from your device booted to Android since we no longer use device storage.

Added permissions error message and link to the post with solutions when trying to modify ramdisk in Windows without proper access.

NOTES: I have built Mac/OSX v3.1.5.6 this time as many bugs have been worked out since v3.1.5.3. There is still very little interest in the Mac version so it will probably stay at v3.1.5.6 for a while.
[SuperR Kitchen] SuperR.:
v3.1.5.7

Changes:

Updated vdexExtractor to the latest commit.

Fixed data_new.img not being created or included in the rom if data perm type is set to raw_img.

Allow creating data.img from Build ext4 img menu.

Added option to choose Magisk root method in main kitchen, making the magisk_mod plugin obsolete.

Fixed root not being removed from the updater-script fully when choosing to remove root.

Removed unused language entries.

Added support for extracting firmware zips containing multi-part system_*.img.

Check for and fix ext4 img with a larger stored block count than actual blocks.

NOTE:

The autorom_config plugin has also been updated to reflect the Magisk root addition to the kitchen.
[SuperR Kitchen] SuperR.:
v3.1.5.8

Changes:

Cleanup project directory after failed img extraction.

Fixed java detection when getting an unexpected first line in the output.

Fixed java detection for newer versions of java.

Use separate fs_config for extracted partitions instead of sharing.

When building sparse_dat, fixed crash after error message if ext4 img was not created successfully.

Fixed crash when extracting Samsung extra parts if a tar.md5 file it is looking for does not exist.

If not already specified, add default context to the file_contexts file for all partitions before building ext4 img.

Fixed duplicate mount and unmount lines being added to the updater-script.

NOTE: The tools download location has changed. This means previous kitchen versions will fail to download the required tools automatically.
[SuperR Kitchen] SuperR.:
v3.1.5.9

Changes:

Check for avb flag during dm-verity check.

When removing dm-verity, remove avb flag if it exists.

Fixed strange lines being added to file_contexts during bin conversion causing ext4 img creation to fail.

Linux/Mac: Fixed runtime error on plugins that require root if your installed python3 version is different than the one included with the kitchen.

Updated md5 for Android Image Kitchen by [MENTION=4544860]osm0sis[/MENTION].

NOTE: If you are experiencing the Linux/Mac plugin runtime error, you will need to remove the problem plugins and reinstall them after this update to fix the issue.
[SuperR Kitchen] SuperR.:
v3.1.6.0

Changes:

Fixed crash in plugin install and plugin updater for all plugins that were not fixed in the last update.
[SuperR Kitchen] SuperR.:
v3.1.6.1

Changes:

Added support for Android Pie vendor_file_contexts.

Added support for extracting Pixel Android Pie firmware including the new system_other.img containing app and priv-app.

Added support for deodexing Android Pie (still need the updated vdexExtractor binary once it is ready).

NOTE: Deodexing Android Pie before vdexExtractor is updated will result in many errors!! To be clear, Android Pie deodexing WILL NOT currently work, but the kitchen is ready for it :)
[SuperR Kitchen] SuperR.:
v3.1.6.2

Changes:

Fixed SuperSU options not showing in some cases.

Separate system and vendor fs_config, file_contexts3, and symlinks files so all are finally separate.

Minor code refactoring.
[SuperR Kitchen] SuperR.:
v3.1.6.3

Changes:

Fixed priv-app/PrebuiltGmsCorePi/app_chimera apps not being deodexed in Android Pie.

Check for scripts inside the AIK/AIK2 directories instead of checking for the directory itself to see if AIK is installed.

Fixed crash when deodexing framework if one of the detected arch directories does not exist in framework.

Fixed crash when deodexing M/N.

Updated aapt and zipalign binaries from the Android Pie SDK.

Updated smali/baksmali to v2.2.5.

Windows: Fixed line endings in configure.sh causing it to fail when flashing.

NOTE: Android Pie deodex DOES NOT WORK. The updates for Pie deodex are just to be prepared when it is ready.

NOTE2: New installation of version 3.1.6.1 and earlier have been disabled. Please install the latest version to continue using the kitchen. This is more effort to stop the thieves. Sorry for the inconvenience and hopefully I won't need to do this again in the future.
[SuperR Kitchen] SuperR.:
v3.1.6.4

Changes:

Linux: Added support for Android Pie Deodex.

Updated vdexExtractor to the latest commit.

Rename odm.img.ext4 to odm.img when extracting newer Samsung firmware.

Windows: Fixed crash when deodexing KitKat and earlier roms.

Added update option if kitchen version is disabled in the future.

Changed all updater-script mount commands to conditional statements.

NOTE: Sorry Windows users. I have not found a way to convert cdex to dex in Windows which is required to deodex Android Pie. I still have hope but no timeline, or ideas, at all.

If you are a Windows user and would like to deodex Pie:

Windows 10 users can run the kitchen in WSL (Windows Subsytem for Linux).

Windows 7 users can run the kitchen in a virtual machine running Linux.

NOTE2: I take absolutely no responsibility for what happens after deodexing Android Pie. I have not done any on-device testing. Good luck :)

NOTE3: Mac was not updated this time due to time restraints. Nobody is using it anyway so it probably does not matter.

NOTE4: xiaomi_patch and sam_81deo_patch plugins have been updated to use smali/baksmali instead of apktool.
[SuperR Kitchen] SuperR.:
v3.1.6.5

Changes:

Windows: EXPERIMENTAL support for Android Pie deodex.

Fixed crash if matching jar file does not exist when deodexing O/P framework vdex.

Fixed unmount for extra partitions not being added to the updater-script before format.

Do not delete platform tools if AIK/AIK2 downloads fail.

NOTE: The Windows Android Pie deodex uses vdexExtractor to extract the cdex files. The Kitchen zips them and sends them to my server (Linux). The server converts the cdex files to dex and sends them back. Once received, they get packed in the apk/jar files as normal.

NOTE2: Why is this marked EXPERIMENTAL? I have no idea if my server can handle what has just been unleashed. It has worked perfectly during all my tests, but I was the only one using it. If there are 300 people converting on the server at the same time ... no clue :)

NOTE3: As a result of NOTE2, I have added a switch to the server API so I can disable it remotely. I may need to do this if the server starts freaking out. If disabled, you will see a message about it when you try to deodex Pie on Windows. I apologize in advance if this happens. Just remember, I tried :)

EDIT:

NOTE4: To help with server strain, the kitchen will store the converted dex zip in 00_project_files. If this zip exists when you deodex Pie, it will be used instead of sending to the server and converting again. If you extracted the same firmware and deodex again, this will not be a problem. If you extract a different firmware in the same project, you will have a problem. Always use a new project for new firmware. Reusing project directories is a bad idea unless you completely empty it first.
[SuperR Kitchen] SuperR.:
v3.1.6.6

Changes:

Windows: Move cdex upload zip to 00_project_files instead of deleting in case there is a problem uploading/converting.

Windows: Better error messages when deodexing Android Pie.

Linux: Fixed the broken bootimg binary responsible for sepolicy patching.

WSL: Fixed many issues installing and running.

OSX: Updated vdexExtractor to the latest commit.

OSX: Added support for Android Pie deodex.

NOTE: I am not able to test OSX Pie deodex due to my version of OSX. vdexExtractor cannot be compiled on Yosemite which is what I currently have available for testing. I had to compile on a friends Mac running High Sierra, and the resulting binary does not work in Yosemite. I hope it will work for El Capitan and newer.
[SuperR Kitchen] SuperR.:
v3.1.6.7

Changes:

Updated vdexExtractor to the latest commit.

Fixed the possibility of duplicate entries in the updater-script.

Minor code refactoring.

LINUX USERS: It has been brought to my attention that some users may get an error message using the latest kitchen. It is due to glibc mismatch, and happened because I updated my build machine to Ubuntu 18.04. Apparently the kitchen will not work in Ubuntu 16.04 anymore. The error message looks like this:

[4627] Error loading Python lib '/home/username/superrs-kitchen3/tools/source/libpython3.6m.so.1.0': dlopen: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /home/username/superrs-kitchen3/tools/source/libpython3.6m.so.1.0)

Upgrading your OS to Ubuntu 18.04 (or another distro with glibc 2.25) will fix the issue. If needed, I can set up a VM with Ubuntu 16.04 for compiling the kitchen. I do not know how widespread this problem will be. So far only one user has mentioned it.
[SuperR Kitchen] SuperR.:
v3.1.6.8

Changes:

Fixed typo when extracting a ROM that uses an update-binary script which caused META-INF to end up misnamed and in the wrong place.

Linux: Compile the kitchen in Ubuntu 16.04 VM for compatibility with older glibc versions.

Let's kill this glibc issue before it becomes a real problem :)
[SuperR Kitchen] SuperR.:
v3.1.6.9

Changes:

Windows: Local cdex to dex conversion without upload/download, finally.

Windows: Fixed ext4.img corruption during creation on some firmware.

Linux: Added configuration option to use tput instead of ascii escape codes to clear the screen.

Updated md5 for Android Image Kitchen v3.4 by [MENTION=4544860]osm0sis[/MENTION].

Updated md5 for Busybox Installer v1.29.3 by [MENTION=4544860]osm0sis[/MENTION].

Fixed extraction of rom.zip that includes payload.bin.

NOTES:

Linux: To use the new tput screen clearing (not recomended if you are not having issues):

open kitchen/tools/srk.conf in a text editor

add the following line:

use_tput=1

Save and close the file.

Restart the kitchen

All plugins have been updated for the new tput screen clearing option in Linux. The new plugins will crash in kitchen v3.1.6.8 and earlier, and the old plugins will crash in kitchen v3.1.6.9 and later. Update the kitchen first, then update all the plugins and everything will be ok :)

Windows: Building a system.img will fail on new installs of v3.1.6.8 and older. The tools have changed. New tools will be downloaded in old installs and they are not compatible.

xiaomi_patch plugin has been updated to fix the slow boot issue in deodexed MIUI Android Pie (untested).

There are 2 semi-new plugins (sorry for the late announcement):

lg_rctd_remove - Removes rctd, ccmd, and triton from LG init (thanks [MENTION=5297774]bcrichster[/MENTION] for info and testing).

omc_decode - Decodes encoded omc in Samsung devices (thanks [MENTION=3931450]dr.ketan[/MENTION] for info).

mount() argument cannot be empty:

If you are getting this error when flashing your ROM, you can try replacing superr_project/install/bin/configure.sh with this one (right-click, save link as). Thanks [MENTION=4688377]russel5[/MENTION] for pointing out this workaround until I figure out what is going on with the existing one. You can replace kitchen/updater/install/bin/configure.sh if you want a more permanent switch. It will be replaced during an update if that file changes, otherwise it will survive an update.
[SuperR Kitchen] SuperR.:
v3.1.7.0

Changes:

Better exception handling when Busybox.zip does not download properly from xda link.

Fixed deodex regression from last version.

Another attempt at configure.sh.
[SuperR Kitchen] SuperR.:
v3.1.7.1

Changes:

Updated vdexExtractor by [MENTION=407497]anestis[/MENTION]b to the latest commit.

Windows: Administrator privilege is no longer required to run the kitchen.

Windows: Do not move system directory when building a system.img, only rename it temporarily.

Windows: Properly handle exceptions when you don't have permission to rename the system directory.

Another attempt at configure.sh.

Added support for extracting Samsung firmware with HOME.md5 and lz4 compression.
[SuperR Kitchen] SuperR.:
v3.1.7.2

Changes:

Fixed crash if vdex file exists but jar file does not when deodexing.

Windows: More attempts at fixing system rename after building system.img.

Linux: Updated kitchen updater to work with the launcher/installer found in the new *4kitchen Linux distros.

Show update menu even if there is no update when checking for updates.

Fixed regression with file contexts in set_metadata updater-script.
[SuperR Kitchen] SuperR.:
v3.1.7.4

Changes:

Check if apk is already aligned before zipaligning.

Allow to continue when checksums do not match for less important files after kitchen update.

Added odm to configure.sh to fix flashing errors on Samsung devices when odm is included in the ROM.

Several small fixes that may have caused crashes.

Code refactoring for performance improvements.
[SuperR Kitchen] SuperR.:
v3.1.7.5

Changes:

Windows: Use rm.exe to delete files and directories, fixing deodex hanging on some pre-Oreo firmware.

Plugin and tools download locations moved to new server (plugin and tools downloads on previous kitchen versions will no longer work).

NOTE: Sorry about the server change. I hope I do not need to do this again :)
[SuperR Kitchen] SuperR.:
v3.1.7.6

Changes:

Fixed relative path symlinks being converted into absolute path.

Fixed kitchen crashing when trying to install future disabled versions after v3.1.7.6.

Added redundancy server (for kitchen authentication only) that will be used in case the main server is unreachable.

Fixed system_image.emmc.win being treated like a tar backup.

Added support for extracting TWRP win (tar) backups other than system (data may work now but is not supported).

Added support for extracting TWRP win (tar) backups that are also gzipped.

Added new option in Misc Tools > Flashable zip options for long set_metadata updater-script that removes most of the recursive lines and expands the permissions added.

Many other small fixes, too many to name.

NOTE:

About the option to choose short or long set_metadata updater-script:

Misc Tools > Flashable zip options > Short/Long set_metadata updater-script (global) > Short/Long

This is a global choice, meaning it affects all projects. The default is short. Short is what the kitchen has been doing since v3.1.3.7. If you choose long, the extra recursive lines in the updater-script will be removed and the permissions expanded.
[SuperR Kitchen] SuperR.:
v3.1.7.7

Changes:

Fixed crash if a file does not exist when validating kitchen files.

Fixed possibility of kitchen thinking the install is corrupt when it is not.

Fixed deleting projects from the main menu.

Fixed crash if smali.zip does not download properly.

Added option to choose which authentication server you would like to use as primary, New York or California USA.

Create new apk including the deodexed classes if apk does not exist when deodexing.

Added screen_clear config option that will use either no screen clearing, tput clear for Linux, or cls for Windows.

Removed use_tput config option in favor of the new universal screen_clear config option.

NOTES:

Primary Authentication server

There are 2 authentication servers now due to the outage that happened recently. One is in New York, USA (NY) and the other is in California, USA (CA). As of v3.1.7.6, the kitchen tries to access the NY server first, and if it fails tries to access the CA server.

In v3.1.7.7 there is a new menu option, Misc Tools > Primary server location, that allows you to choose which server is tried first. No matter which one you choose, the other server will be the backup

I hope this will help users that currently require a VPN start the kitchen. If you do not have issues connecting to the server when starting the kitchen, there is no need to change it from default.

Screen Clearing

If you do nothing, the default is ascii escape codes that clear the screen. This has been the default for a long time. If you are not having screen clearing issues, it is recommended that you do nothing.

In kitchen/tools/srk.conf, you can add a line to change the screen clearing behavior:

Use "tput clear" in Linux, and "cls" in Windows

screen_clear=1

Do not clear the screen at all and display a new page below the old page

screen_clear=None

"use_tput=1" is no longer available, as "screen_clear=1" does the same thing but on all platforms instead of only Linux.

There is no need for a restart. After saving srk.conf with the new line, the change will be seen immediately.
[SuperR Kitchen] SuperR.:
v3.1.7.8

Changes:

Fixed kitchen updater for future updates.

Fixed kitchen updater from a future disabled kitchen version.

Windows: Use the same superr.exe and ramdisk.exe when possible hoping to eventually eliminate anti-virus issues.

Fixed ramdisk function not recognizing WSL properly.

NOTES:

I hope this update fixes all future updater issues. Unfortunately the updater was broken in several recent versions so you will probably need to do another fresh install. I know it is annoying and I apologize. If everything goes well, the next update will go smoothly if you are running v3.1.7.8.

Regarding anti-virus in Windows, it appears [MENTION=7901411]RawMain[/MENTION] has worked miracles for us. I have been monitoring the VirusTotal link and they are dropping off like flies. Great Work :D

Since the anti-virus programs seem to only dislike superr.exe and ramdisk.exe in the source directory, I have rewritten my build script to use the same files in future kitchen releases. I hope this means once these files are in the anti-virus database future kitchen versions will also pass. Fingers crossed and thanks again RawMain :)
[SuperR Kitchen] SuperR.:
v3.1.8.0

Changes:

Windows: Fixed system.img build for system-as-root devices.