[ Windows / Linux / Mac ][DONATE] SuperR's Kitchen (v3.2.2.2 - 10-13-2021)

Search This thread

starbucks2010

Senior Member
Jun 30, 2010
3,236
2,022
Hello, @SuperR.

Is this project abandoned or just slow in adapting to the new devices?
As many users have reported, the repacking f2fs images that are present in this year devices is not working in v3.2.2.2.
Is it possible to have a look into this issue and adapt your nice kitchen?
Another good addition to kitchen would be to be able remove the read-only restriction on the f2fs images that we have now in samsung devices (possibly on other devices too).

Thank you in advance.
 
  • Like
Reactions: nguyenxuanhoa

SuperR.

Recognized Developer
Mar 23, 2014
2,644
8,778
Invisible
Moto E 2015
LG Nexus 5X
The project is not abandoned, but I do not have much time to work on it.
I have not looked into packing F2FS, but it is probably a large project like EXT4 was. I will probably not get to this any time soon. If you have knowledge to share about how to pack F2FS successfully, that would be another story.
I do not know how to remove the read-only restriction on F2FS images.
 

AnonVendetta

Senior Member
Apr 29, 2016
1,323
485
@SuperR.: After not using the Kitchen for months, I'd now like to try my hand at building another ROM with stock firmware as a base. The device I'm building for (which I own personally) is a Galaxy Tab S7+ SM-T970. It currently is running Android 11 BUJ3 firmware, which is the latest 11 firmware for it. I also have TWRP and Magisk installed.

I know for sure that it uses a super.img. I also believe it is system-as-root (not sure, but Magisk says it is). And I'm pretty sure it uses dynamic partitions. So far I have only built ROMs up to Oreo with the Kitchen, which have a far different partition layout. So for what I'd like to do now, I'm basically new to the game.

I just have a few questions before I do a test run:

1. The raw image format is what I should be using?

2. There is a configuration option called something along the lines of "extract all img's". Should I use this? Or is this just an option that does this automatically, rather than asking on a per img basis whether to extract/include img contents in the ROM?

3. I plan to deodex. I notice there's a "deodex patch for Oreo" in the unpack/repack boot.img options. Is this really just for Oreo, or is it needed on later deodexed ROMs too?

4. In the ROM building options, there are "build full ROM zip", which I'm assuming is meant to be flashed from TWRP. However, I also see an option to build super.img and ext4 img. What are those needed for?

5. Is there a way to build an Odin-flashable firmware after I've done my edits from the Kitchen?

Edit: I installed the Samsung Tools plugin, and found that there is a 2nd deodex patch there. Trying to run it gives the error "this is not a Samsung device". I'm not sure what criteria Kitchen uses to determine what is/isnt Samsung. But i can assure you that it is a Samsung tablet, and the Odin firmware zip is 100% original too.
 
Last edited:

AnonVendetta

Senior Member
Apr 29, 2016
1,323
485
@SuperR.: I just realized that providing you with a fast link to my firmware may be helpful. So:

Firmware link

Registration isn't required for the latter 2 options, and from my exp, the DL is fast/unthrottled as long as you have a decent Internet connection. The 1st DL option requires importing to your Google Drive.

The firmware comes in the form of a zip file, containing:

AP tar.md5
Bootloader tar.md5
CSC tar.md5
Home CSC tar.md5

CSC is for clean flashing, Home CSC is for upgrade/dirty flashing. I took the downloaded zip and repackaged it so that it only contains AP, BL, and CSC.

If you compare the contents of CSC/home CSC, you will see that the latter is redundant and not needed as long as the CSC file is present. And they both have files that would conflict with each other if unpacked together.

Thanks for your time and hard work!

Edit: Also attached is a support zip that i generated, after trying to run the deodex patch from the Samsung Tools plugin menu.
 

Attachments

  • support_AnonVendetta_07-08-2022-16_27_16.zip
    494.3 KB · Views: 20
Last edited:

firefds

Senior Member
Mar 23, 2011
1,474
2,014
Toronto
Hi Everyone! Got a small problem...
I'm extracting the S21 FE (SM-990E) firmware which works flawlessly, including extracting the super.img.
However, I can't find how I can build the rom zip with super.img instead of individual product.img system.img vendor.img odm.img.

Am I missing something here?

Thanks!
 

dr.ketan

Recognized Developer / Recognized Contributor
Hi Everyone! Got a small problem...
I'm extracting the S21 FE (SM-990E) firmware which works flawlessly, including extracting the super.img.
However, I can't find how I can build the rom zip with super.img instead of individual product.img system.img vendor.img odm.img.

Am I missing something here?

Thanks!
Practically you can't. Twrp can't handle zip bigger than 4gb. Super ઇમેજ is quite huge and even after zip you will have it bigger than 4GB.
Best way is to make system and other partition with br compression to reduce size to fit in zip
 
  • Like
  • Love
Reactions: jenneh and firefds

AnonVendetta

Senior Member
Apr 29, 2016
1,323
485
Hi Everyone! Got a small problem...
I'm extracting the S21 FE (SM-990E) firmware which works flawlessly, including extracting the super.img.
However, I can't find how I can build the rom zip with super.img instead of individual product.img system.img vendor.img odm.img.

Am I missing something here?

Thanks!
Good luck getting an answer from @SuperR. on this. I posted a question very recently in this topic, I think over 2 weeks ago, no answer yet. Guess I'll just have to be patient and wait.
 

zaphodbeeblebrox42

New member
Jul 13, 2022
1
0
Hi @superr,

I'm having some trouble with a Pixel 4. I'm using the latest compatible TWRP version for my device (3.6.2_11), but I suspect userspace fastbootd might not be working which would explain why it can't seem to mount system and vendor with r/w perms. Here are the details:
  • Kitchen version: 3.2.2.2 (Donate)
  • OS: WSL (Ubuntu 20.04 x64) on Windows 11
  • Device: Pixel 4
  • Android Version: 11
  • Perm method: set_metadata
  • Factory zip: flame-rq3a.211001.001-factory-2e1faa99.zip
  • Link to factory image used: https://dl.google.com/dl/android/aosp/flame-sp1a.210812.015-factory-0cfe1e42.zip
  • What did you do after extracting and before building? Nothing yet (but eventually, I'd like to add files to the system partition)
  • Were there errors on the screen if you scroll up in the terminal? Yes:
mount: failed to mount /dev/block/mapper/vendor_b at /vendor: Permission denied mount: failed to mount /dev/block/mapper/system_b at /system_root: Permission denied flame mod Installed script succeeded: result was [flame mod Installed] Updating partition details... ...done

I've attached the recovery log and support zip associated with the above errors.

I also used Kitchen to create sparse vendor and system images (again, I made no changes after the initial extraction) and tried to flash them individually in fastbootd mode after disabling dmverity with an empty vbmeta image in regular fastboot mode (bootloader mode). I tried this a lot of ways, but here is one example of the set of commands I used:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_disabled.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_disabled.img
fastboot reboot fastboot
fastboot flash system system_new.img
fastboot flash vendor vendor_new.img
fastboot reboot

I've been grabbing the boot logs via uart output and it always seems to look good at first:

Code:
[   11.283938] c4      1 e2fsck: /dev/block/by-name/metadata: 35/4096 files (0.0% non-contiguous), 1197/4096 blocks
[   11.296349] c4      1 EXT4-fs (sda11): mounted filesystem with ordered data mode. Opts: discard
[   11.305321] c4      1 init: [libfs_mgr]__mount(source=/dev/block/by-name/metadata,target=/metadata,type=ext4)=0: Success
[   11.357160] c4      1 init: [libfs_mgr]Created logical partition system_a on device /dev/block/dm-0
[   11.366944] c4      1 init: [libfs_mgr]Created logical partition system_b on device /dev/block/dm-1
[   11.377638] c4      1 init: [libfs_mgr]Created logical partition vendor_a on device /dev/block/dm-2

But then it always falls apart when SELinux loads:

Code:
[   11.676438] c6      1 init: Loading SELinux policy
[   11.695035] c6      1 SELinux:  policy capability network_peer_controls=1
[   11.702014] c6      1 SELinux:  policy capability open_perms=1
[   11.708017] c6      1 SELinux:  policy capability extended_socket_class=1
[   11.715006] c6      1 SELinux:  policy capability always_check_network=0
[   11.721898] c6      1 SELinux:  policy capability cgroup_seclabel=0
[   11.728332] c6      1 SELinux:  policy capability nnp_nosuid_transition=1
[   11.797906] c7      1 selinux: SELinux: Loaded policy from /vendor/etc/selinux/precompiled_sepolicy
[   11.816865] c7      1 selinux:
[   11.834466] c7      1 selinux: SELinux: Loaded file_contexts
[   11.840283] c7      1 selinux:
[   11.844922] c7      1 selinux: SELinux: Could not set context for /system/bin/init:  Read-only file system
[   11.854832] c7      1 selinux:
[   11.858082] c7      1 init: restorecon failed of /system/bin/init failed: Read-only file system
[   11.867244] c7      1 init: InitFatalReboot: signal 6

I'm not sure what to try at this point, but please let me know if you have any advice. Thanks!
 

Attachments

  • support_zaphodbeeblebrox42_08-01-2022-13_13_32.zip
    513.9 KB · Views: 5

peturbg

New member
Aug 2, 2022
3
0
hi guys im trying selinux injector. It find more than 600 selinux deny can you make this program export all them in separate files: adb.te file.te or show what to be added i will be add it by hand.
 

sbyn_0976

New member
Jun 29, 2021
2
0
Disclaimer: I am not responsible for anything bad that may occur from the use of this kitchen, but I will take all the credit you can give me if it works for you :D

View attachment 5339515

main_windows1.png


Please read the troubleshooting in post #4 of the standard kitchen thread before asking for help.
Please indicate your OS when asking for help.
Please send a fast link to your firmware that does not require registration when asking for help.


Donate Release Thread
Donate Changelog

Donate version Info
Access to the donate version of the kitchen requires a minimum donation of $20.00 US. See terms and conditions below.


Terms and Conditions for SuperR's Kitchen Donate version:

Allowed:
  • An active kitchen account grants usage privileges of the donate kitchen and the sr-code.com website.
  • One kitchen account provides kitchen access to one user, on one operating system, on one personal computer.

Not allowed:
  • Sharing your kitchen account and/or privileges.
  • Transfer and/or resale of your kitchen account.
  • Suspicious activity.

Definition:
Suspicious activity - Decided exclusively by SuperR at the time of an incident.

Resolution:
If anything from the not allowed list occurs, your kitchen account will be disabled.

See this post for more details on the Single PC license.

Donation Options:
1. Paypal through my website
2. US Amazon eGift card (email address found here)

Once you donate, register for a Kitchen account (free) and send a PM with your username and the email address used for donation. I will add you to the database and you will then have access to the donate version download section. Follow the steps below to get it downloaded and running :)

EXISTING DONORS: GitLab is no longer used. See this post if you previously had GitLab access and are unable to download/update/install.

NOTE: The Plugin Repo is included in the Donate kitchen. If you wish to see a description of the available plugins, they can be found here.

Dependencies:

WINDOWS:
LINUX/MAC:
  • Java 8 or higher
  • Python (to run the launcher (could be bypassed by running tools/source/superr in the terminal from the main kitchen directory))

Download/Install/Run:

Free version:

WSL2 (Windows 10):

Linux/Mac (Terminal):
  1. Download the kitchen.zip from the download page sent through PM. Extract to a new directory.
  2. Enter the following command where "/location/of/kitchen" is the directory where the kitchen lives:
    Code:
    /location/of/kitchen/superr

Windows:

NOTE: The native Windows version has reached end of life. Consider running the Linux kitchen in WSL2 using the guide above.​
  1. Download the kitchen.zip from the download page sent through PM. Extract to a new directory.
  2. Make sure Java listed above is installed and in your system environment PATH (Check Google for the many guides on this if you need help)
  3. Double click superr.exe in newly extracted kitchen directory.

NOTE: After you start the kitchen, it will ask you for your Kitchen username and password. Make sure you enter it correctly or it will not work. Thanks for the donation, enjoy :)

Known Issues/Limitations:
Does not unpack/repack f2fs file systems.

Linux:
  • None
WSL2:
  • None
WSL1:
  • Crashes with xattr not defined error when unpacking some img files due to a bug in the Python ext4 module.
Mac:
  • Does not use e2fsdroid for building img files as I am not able to compile it for Mac so far.
Windows:
  • No longer being updated. v3.2.1.3 is the last version. The Linux kitchen runs perfectly in WSL.
  • Does not use e2fsdroid for building img files as I am not able to compile it for Windows.
  • Crashes with xattr not defined error when unpacking some img files due to a bug in the Python ext4 module.
  • If you run Windows as administrator and have issues with the Boot Menu, please see this post.
  • If superr.exe gets removed by your antivirus program, whitelist the kitchen directory in your antivirus program.
  • If the kitchen can't find an internet connection, try whitelisting sr-code.com in your antivirus browsing security. If it still does not find a connection, try using a VPN.
  • The colors are not perfect due to Windows not supporting ASCII escape codes by default. If you want it to look more like Linux, you can run the Linux version in WSL (formerly known as "Bash on Ubuntu on Windows").

Video tutorials by @chevycam94

Credits:

@osm0sis - For Busybox Installer and Android Image Kitchen
@Chainfire - For SuperSU
@JesusFreke - For [Bak]smali
@nkk71 - For TWRP minzip patch, and make_ext4fs improvements
@Captain_Throwback - For providing a pre-compiled update-binary with the minzip patch and squashing bugs
@cubinator - For Python ext4 module
@_riddle - For oat2dex
@iBotPeaches - For Apktool
@AOSP - For zipalign, aapt, adb, img2simg, simg2img, make_ext4fs
@xpirt - for img2sdat & sdat2img
@yoanf_26 - For French translation
@anestisb - For vdexExtractor
@iuss - For payload_dumper.py


Contributors
SuperR.

Version Information
Status:
Beta

Created 2018-11-16
Exelent tool...
 
hi guys im trying selinux injector. It find more than 600 selinux deny can you make this program export all them in separate files: adb.te file.te or show what to be added i will be add it by hand.
you can take logcat | grep avc | grep denied from termux or from adb shell
copy all text to new txt file and use audit2allow to read and patch
 

toss...

Member
Sep 7, 2017
7
0
It is hoped that erofs can be supported in the future. Coloros has already used the erofs file system
 

Top Liked Posts

  • There are no posts matching your filters.
  • 175
    Disclaimer: I am not responsible for anything bad that may occur from the use of this kitchen, but I will take all the credit you can give me if it works for you :D

    main_donate_linux.png


    main_windows1.png


    Please read the troubleshooting in post #4 of the standard kitchen thread before asking for help.
    Please indicate your OS when asking for help.
    Please send a fast link to your firmware that does not require registration when asking for help.


    Donate Release Thread
    Donate Changelog

    Donate version Info
    Access to the donate version of the kitchen requires a minimum donation of $20.00 US. See terms and conditions below.


    Terms and Conditions for SuperR's Kitchen Donate version:

    Allowed:
    • An active kitchen account grants usage privileges of the donate kitchen and the sr-code.com website.
    • One kitchen account provides kitchen access to one user, on one operating system, on one personal computer.

    Not allowed:
    • Sharing your kitchen account and/or privileges.
    • Transfer and/or resale of your kitchen account.
    • Suspicious activity.

    Definition:
    Suspicious activity - Decided exclusively by SuperR at the time of an incident.

    Resolution:
    If anything from the not allowed list occurs, your kitchen account will be disabled.

    See this post for more details on the Single PC license.

    Donation Options:
    1. Paypal through my website
    2. US Amazon eGift card (email address found here)

    Once you donate, register for a Kitchen account (free) and send a PM with your username and the email address used for donation. I will add you to the database and you will then have access to the donate version download section. Follow the steps below to get it downloaded and running :)

    EXISTING DONORS: GitLab is no longer used. See this post if you previously had GitLab access and are unable to download/update/install.

    NOTE: The Plugin Repo is included in the Donate kitchen. If you wish to see a description of the available plugins, they can be found here.

    Dependencies:

    WINDOWS:
    LINUX/MAC:
    • Java 8 or higher
    • Python (to run the launcher (could be bypassed by running tools/source/superr in the terminal from the main kitchen directory))

    Download/Install/Run:

    Free version:

    WSL2 (Windows 10):

    Linux/Mac (Terminal):
    1. Download the kitchen.zip from the download page sent through PM. Extract to a new directory.
    2. Enter the following command where "/location/of/kitchen" is the directory where the kitchen lives:
      Code:
      /location/of/kitchen/superr

    Windows:

    NOTE: The native Windows version has reached end of life. Consider running the Linux kitchen in WSL2 using the guide above.​
    1. Download the kitchen.zip from the download page sent through PM. Extract to a new directory.
    2. Make sure Java listed above is installed and in your system environment PATH (Check Google for the many guides on this if you need help)
    3. Double click superr.exe in newly extracted kitchen directory.

    NOTE: After you start the kitchen, it will ask you for your Kitchen username and password. Make sure you enter it correctly or it will not work. Thanks for the donation, enjoy :)

    Known Issues/Limitations:
    Does not unpack/repack f2fs file systems.

    Linux:
    • None
    WSL2:
    • None
    WSL1:
    • Crashes with xattr not defined error when unpacking some img files due to a bug in the Python ext4 module.
    Mac:
    • Does not use e2fsdroid for building img files as I am not able to compile it for Mac so far.
    Windows:
    • No longer being updated. v3.2.1.3 is the last version. The Linux kitchen runs perfectly in WSL.
    • Does not use e2fsdroid for building img files as I am not able to compile it for Windows.
    • Crashes with xattr not defined error when unpacking some img files due to a bug in the Python ext4 module.
    • If you run Windows as administrator and have issues with the Boot Menu, please see this post.
    • If superr.exe gets removed by your antivirus program, whitelist the kitchen directory in your antivirus program.
    • If the kitchen can't find an internet connection, try whitelisting sr-code.com in your antivirus browsing security. If it still does not find a connection, try using a VPN.
    • The colors are not perfect due to Windows not supporting ASCII escape codes by default. If you want it to look more like Linux, you can run the Linux version in WSL (formerly known as "Bash on Ubuntu on Windows").

    Video tutorials by @chevycam94

    Credits:

    @osm0sis - For Busybox Installer and Android Image Kitchen
    @Chainfire - For SuperSU
    @JesusFreke - For [Bak]smali
    @nkk71 - For TWRP minzip patch, and make_ext4fs improvements
    @Captain_Throwback - For providing a pre-compiled update-binary with the minzip patch and squashing bugs
    @cubinator - For Python ext4 module
    @_riddle - For oat2dex
    @iBotPeaches - For Apktool
    @AOSP - For zipalign, aapt, adb, img2simg, simg2img, make_ext4fs
    @xpirt - for img2sdat & sdat2img
    @yoanf_26 - For French translation
    @anestisb - For vdexExtractor
    @iuss - For payload_dumper.py


    Contributors
    SuperR.

    Version Information
    Status:
    Beta

    Created 2018-11-16
    64
    Features:

    *Extract and create ROM from:
    • Rooted Device
    • Custom Recovery
    • Existing ROM zip
    • system.img/boot.img (and cache.img on Samsung devices)
    • system.ext4.tar/boot.img
    • system.ext4.win/boot.emmc.win (including multi-file .win000, .win001, etc)
    • Moto and other factory firmware zips containing sparsechunk files
    • cm12 + roms with sparse dat files
    • Zips that contain system.img and boot.img
    • Zips that contain payload.bin
    • Samsung firmware zips that contain tar.md5 file
    • Official Nexus/Pixel firmware tgz/zip
    • Official Nexus/Pixel preview tgz/zip
    • system directory that contains symlinks and boot.img
    *Create flashable zips of many varieties including:
    • Full ROM
    • Switch between set_perm, set_metadata (KitKat+), raw_img, and sparse_dat (Lollipop+)
    • Kernel (including init.d if you added it with the kitchen)
    • Recovery
    • Media
    • app, priv-app, and framework
    *Deodex the following:
    • Android 10 ROMs
    • Pie ROMs
    • Oreo ROMs
    • Nougat ROMs
    • Marshmallow ROMs
    • Lollipop ROMs
    • KitKat and earlier ROMs
    *Root features:
    • Root/unroot
    • Choose Magisk
    • Choose SuperSU
    • Add other root zips to /tools/root/root_zips directory
    • Choose system OR systemless root for M+ and Samsung 5.1.1 roms
    • Add/remove su.d support
    *Boot features:
    • Unpack/repack boot/recovery img (Big Thanks to @osm0sis for Android Image Kitchen!!!)
    • Add/remove insecure boot
    • Remove dm-verity
    • Add/remove forceencrypt
    *By-name auto-detection from:
    • Device
    • Existing ROM
    • boot.img
    • kernel.elf
    • **OR**...manually enter it
    *mmcblk auto-detection from:
    • recovery.img
    *Kitchen updater:
    • View the last 3 changelogs when an update is available.
    • Update to the latest version
    • Option to check for updates when the kitchen starts
    *Pack/Unpack super.img
    *Create system.img
    *Device database for mmcblk devices (currently very small, but will grow over time)
    *Add devices to the assert
    *Add custom asserts
    *Zipalign apks
    *Debloat ROM
    *Custom Debloat list support
    *Remove Knox
    *Add/remove busybox (Big thanks to @osm0sis for his Busybox Installer)
    *Add/remove user app support (/data/app)
    *Sign zips
    *Cross-platform: Windows and Linux are fully supported
    *Does not say Built with SuperR's Kitchen in the updater-script
    *Does not replace ro.build.display.id with Built.with.SuperRs.Kitchen
    *Allows you to create a custom entry in the updater-script below the ROM name
    *Removes all the Place holders (#ASSERT, #SYM, #PERM, etc) from the updater-script before zipping.
    *Custom ro.build.display.id
    *Option to convert updater-script to update-binary for all rom zips EXCEPT sparse_dat.
    *Add custom directory to be included in and flashed with rom zip to location of your choice.
    *Ability to choose an apk, decompile, modify it manually, recompile, sign, and move it back to where it came from.
    *Plugin support - Add your own script to the /kitchen/tools/plugins directory and the kitchen will run it for you.
    *AutoROM - Unattended ROM development using a config file.
    43
    USAGE:

    1. Run the kitchen (instructions in OP)
    2. Create new project using the menu
    3. Copy ROM zip into the superr_NAME directory of this tool (NAME = the name of your new project).
      OR
      Copy system.ext4.tar and boot.img into the superr_NAME directory of this tool.
      OR
      Copy system.ext4.win and boot.emmc.win into the superr_NAME directory of this tool.
      OR
      Copy system.img and boot.img into the superr_NAME directory of this tool.
      OR
      Copy official Nexus tgz into the superr_NAME directory of this tool.
      OR
      Copy Samsung firmware zip into the superr_NAME directory of this tool.
      OR
      Copy Moto firmware zip into the superr_NAME directory of this tool.
      OR
      Leave superr_NAME directory empty to extract from rooted device or custom recovery
    4. Extract for new ROM from the Main menu.
    5. Enjoy!
    10
    Update on Android Pie deodex:

    anestisb has finished Android P support for vdexExtractor. Android Pie introduced a new dex format, Compact Dex (cdex). anestisb created a new tool to convert cdex to standard dex which is required for Android Pie deodex. Unfortunately, the new tool will not currently work on Windows as it requires many AOSP dependencies and Google does not support compiling AOSP on Windows. It will only work on Linux and Mac. There are many Windows kitchen users, and I have no idea what to do about it.

    More information can be found here.

    If anyone can help, please do. Thanks :)

    EDIT: The Windows aapt.exe binary was not functioning properly. I have reverted to the previous aapt.exe that works. The win_tools package has been updated on the server. Sorry for the inconvenience.

    If you are on Windows and have already updated to v3.1.6.3, you can find the working aapt.exe here. Replace kitchen\tools\win_tools\aapt.exe with the one in the zip.
    9
    Hello everyone :)

    The kitchen is moving to a new server. There could be some strange behavior if you reset a PC or register a new account right now. The DNS can take up to 48 hours to propagate globally. If you reset your PC now, it may result in failing authentication after the DNS is propagated. You can reset again if this is the case.

    I do not expect any problems or downtime, but this information serves as a warning just in case :)