• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[ Windows / Linux / Mac ][DONATE] SuperR's Kitchen (v3.2.2.1 - 6-28-2021)

Search This thread

aidanmacgregor

Senior Member
Nov 19, 2011
1,164
321
Caithness
aidansrom.freecluster.eu
Cant Run the tool, any ideas? Thanks :)


Capture.JPG
 
  • Like
Reactions: kirbyNx

SuperR.

Recognized Developer
Mar 23, 2014
2,627
8,679
Invisible
Moto E 2015
LG Nexus 5X
hi friends. What compression level should I choose when creating a new.dat.br file? Which is the most suitable option?
This depends on your needs. A higher compression level will take longer to compress and be slightly smaller in size. I suggest level 5 or below :)

Cant Run the tool, any ideas? Thanks :)


View attachment 5313317

The same thing happens to me, I think it is a crash with the superr server
The kitchen server was down for a bit today (1 hour 28 minutes) getting a hardware upgrade. It is back up now and should be working properly. Sorry for the inconvenience :)
 

0xx07

New member
May 20, 2021
2
0
Google Pixel 3
Hi, I am using the kitchen to unpack a product.img file modifiy it and then repack it. However I keep getting a 'no valid slot to boot error' when flashing the modified image. What is the correct way to to use the kitchen to repack my product.img file or is there no possibility that I am repacking it incorrectly.
 

QuentinX5

Senior Member
I'm running into an issue when I am attempting to extract the system.img into the project. All it says is:

ERROR:
There was a problem extracting your ROM.

I was able to get the image mounted using mount, and extract all the files, and I can see some stuff missing from the directories compared to the one that the kitchen attempted to create. Is there some way I can use the files I extracted using mount and connect it to the project?

The ROM is a Treble LineageOS 18.1 image for A/B devices found here: https://sourceforge.net/projects/an...2-UNOFFICIAL-treble_arm64_bvS.img.xz/download

I've also attached a support.zip file, but the logs aren't very conclusive of any information from what I can tell.

Other information:

Kitchen version: v3.2.1.7
Environment: I'm currently running Ubuntu 20.04 LTS on WSL2, on Windows x64 (version 1909)
Device: BV9800 Pro (GMS version)
Source: Working with the ROM listed above. Eventually I'll be attempting to pull some dependencies from the stock ROM, but I've already got a project set up and extracted for it
Android Version: ROM is version 11

I think the rest of the information isn't relevant until I am able to attach a file to the project
 

Attachments

  • support_QuentinX5_05-20-2021-08_28_37.zip
    1.3 KB · Views: 3

SuperR.

Recognized Developer
Mar 23, 2014
2,627
8,679
Invisible
Moto E 2015
LG Nexus 5X
Unable to decompose erofs img file
Model: OnePlus 9
ROM:https://yun.daxiaamu.com/t/qLS4W5
The kitchen does not currently support unpacking or packing EROFS.

I'm running into an issue when I am attempting to extract the system.img into the project. All it says is:

ERROR:
There was a problem extracting your ROM.

I was able to get the image mounted using mount, and extract all the files, and I can see some stuff missing from the directories compared to the one that the kitchen attempted to create. Is there some way I can use the files I extracted using mount and connect it to the project?

The ROM is a Treble LineageOS 18.1 image for A/B devices found here: https://sourceforge.net/projects/an...2-UNOFFICIAL-treble_arm64_bvS.img.xz/download

I've also attached a support.zip file, but the logs aren't very conclusive of any information from what I can tell.

Other information:

Kitchen version: v3.2.1.7
Environment: I'm currently running Ubuntu 20.04 LTS on WSL2, on Windows x64 (version 1909)
Device: BV9800 Pro (GMS version)
Source: Working with the ROM listed above. Eventually I'll be attempting to pull some dependencies from the stock ROM, but I've already got a project set up and extracted for it
Android Version: ROM is version 11

I think the rest of the information isn't relevant until I am able to attach a file to the project
Please try renaming "lineage-18.1-20210512-UNOFFICIAL-treble_arm64_bvS.img" to "system.img" before unpacking with the kitchen. Hopefully this will solve your issues.
 

QuentinX5

Senior Member
The kitchen does not currently support unpacking or packing EROFS.


Please try renaming "lineage-18.1-20210512-UNOFFICIAL-treble_arm64_bvS.img" to "system.img" before unpacking with the kitchen. Hopefully this will solve your issues.

*facepalm*

Having correct syntax would make perfect sense. Guess I assumed that wasn't a problem since it was recognizing it. Thank you!
 
  • Like
Reactions: SuperR.

0xx07

New member
May 20, 2021
2
0
Google Pixel 3
Does anyone know whats causing this error when extracting for a new rom?

Extracting files ...
Traceback (most recent call last):
File "superr.py", line 55, in <module>
File "mainsrk.py", line 40, in mainsrk.main
File "<string>", line 101, in main
File "<string>", line 5882, in superr
File "<string>", line 2375, in extract_new
File "<string>", line 209, in __enter__
FileNotFoundError: [Errno 2] No such file or directory: ''
[3009] Failed to execute script superr

thanks.

Update: I only get this error when I try to extract a file that I previously repacked.
 
Last edited:

SuperR.

Recognized Developer
Mar 23, 2014
2,627
8,679
Invisible
Moto E 2015
LG Nexus 5X
Does anyone know whats causing this error when extracting for a new rom?

Extracting files ...
Traceback (most recent call last):
File "superr.py", line 55, in <module>
File "mainsrk.py", line 40, in mainsrk.main
File "<string>", line 101, in main
File "<string>", line 5882, in superr
File "<string>", line 2375, in extract_new
File "<string>", line 209, in __enter__
FileNotFoundError: [Errno 2] No such file or directory: ''
[3009] Failed to execute script superr

thanks.
Please send a link to the firmware you are trying to extract so I can take a look.
 
  • Like
Reactions: adil.amin820

jaing2

Member
May 1, 2013
5
0
Hi me that i managed to fix it and then i was throbbing super.img but it scrubbing can't be used please suggest how to pack samsung firmware to use with odin thanks
 
Last edited:

SuperR.

Recognized Developer
Mar 23, 2014
2,627
8,679
Invisible
Moto E 2015
LG Nexus 5X
  • Like
Reactions: adil.amin820

Verbato

Senior Member
Jan 1, 2007
370
180
Hallingdal
It would be nice if you added a feature to be able to turn on a beep at the end of making (and zipping) a new ROM.
I know it's not high on your list, but it's just a simple printf '\7' before the "would you like to sign the zip" after the ROM has been made and zipped.
It's a kitchen, after all. It needs a "bing", once the cooking is done.
 
Last edited:

SuperR.

Recognized Developer
Mar 23, 2014
2,627
8,679
Invisible
Moto E 2015
LG Nexus 5X
Support for .ext4 or .mg files, do you have any instructions on creating them? After all, I extract the files to repack
.ext4 files are just ext4 img files. You can rename system.ext4 to system.img, and system.img to system.ext4. Rename as needed.

It would be nice if you added a feature to be able to turn on a beep at the end of making (and zipping) a new ROM.
I know it's not high on your list, but it's just a simple printf '\7' before the "would you like to sign the zip" after the ROM has been made and zipped.
It's a kitchen, after all. It needs a "bing", once the cooking is done.
The next version will add the option to run a command/commands at the end of a Full ROM build. It will have a global configuration entry (kitchen/tools/srk.conf) and you can run any commands you want.

For example, I have MPV Player installed on my machine. I set the configuration to mpv "/home/user/music/my_favorite_song.mp3" and now it plays my favorite song at the end of the full ROM build.

In your case, you could just set the configuration to printf '\7' and your beep will play. FYI, the beep does not play for me. That is why the command is changeable. Anyone can make it do anything they want after the build. One could even extend the kitchen this way if they were so inclined :)
 

Pipedream420

Member
Oct 17, 2020
5
2
@SuperR.
Sorry to bug ya. I'm unable to download the busybox zip from the kitchen. Tried whatever I could think of to get it to work. I ended up putting the busybox magisk module zip in there with the hopes that it would work. Will it work? Also, is there any data I can provide that would give you what you need to help me fix the busybox download?
Another question...
In the srk.conf file it says "forcee=fileencryption", can this setting be used to completely disable force encryption?
If not, is that possible with the kitchen? How would I do that if it's possible? Can DM-Verity also be disabled?
I love your kitchen so far. Totally worth the money. I've been able to create and tinker with more firmware than any kitchen I've ever used.
I just wish there was a good tutorial, wiki, or manual out there that I could use for questions like mine.
Thanks for all your hard work. Keep it up.

Oh one more question...
Would you ever consider (if possible) adding makesysrw or superunpack to your kitchen? Maybe with increased functionality?

makesysrw

superunpack
 

SuperR.

Recognized Developer
Mar 23, 2014
2,627
8,679
Invisible
Moto E 2015
LG Nexus 5X
Sorry to bug ya. I'm unable to download the busybox zip from the kitchen. Tried whatever I could think of to get it to work. I ended up putting the busybox magisk module zip in there with the hopes that it would work. Will it work? Also, is there any data I can provide that would give you what you need to help me fix the busybox download?
Busybox download issue is leftover from when XDA moved to the new site. The kitchen parses the page to find the download, but the format changed so it was not being found. It will be fixed in the next update.
In the srk.conf file it says "forcee=fileencryption", can this setting be used to completely disable force encryption?
If not, is that possible with the kitchen? How would I do that if it's possible? Can DM-Verity also be disabled?
As far as I know the kitchen already removes forceencryption and dm-verity. The line in srk.conf is keeping track of what it removed so it can add it back if you want.
Would you ever consider (if possible) adding makesysrw or superunpack to your kitchen? Maybe with increased functionality?
I reviewed the code from both projects you linked. It seems like all they do is remove the shared_blocks ext4 feature. I believe you can accomplish the same in the kitchen by building the ext4 img file without the shared_blocks feature. In the file kitchen/tools/srk.conf, add the line shared_blocks=No and save the file. Now when you build your img file it will not contain the shared_blocks feature.

If you have a problem running out of space when building, you can enter the img size manually and increase the size by any amount you need to make it build.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    ok got it, now other "issue" i fully moved to manjaro, but everytime i repack a rom i have to set partitions size for vendor and product manually plus the rom dont boot up is stuck in device logo and keep restarting, even i just unpack a repack the rom without changes ( android 11 rom )
    It is pretty likely the reason you are stuck on the device logo is because you did not make any changes. I realize you were trying to explain that since you did not change anything it should work. However, I have not met an Android 11 firmware so far that does not require changes to work properly. I do not know what most of these changes are because I do not own these devices for testing. I rely on users to tell me what I need to do make things work. Samsung is pretty well covered right now with the Multidisabler option in the samsung_tools plugin, but other devices are still a mystery to me. One thing is certain, the kitchen builds perfect ext4 img files, so if you are having an issue it is somewhere else.

    Regarding the manual partition size input, after you enter it once for each partition in a project, the next time you choose manual it will ask if you want to use the same size. Beyond this, you can add your manual partition sizes to your project config (00_project_files/srk.conf) and they will be available when you choose manual or when building from the CLI.

    Code:
    img_size_partition=1234567
    3
    that the odd thing, in windows version everything was fine no need to set size manually and the rom boots fine without changes
    The windows kitchen uses make_ext4fs. You can use make_ext4fs in the Linux kitchen too. Add use_make_ext4fs=Yes to the main configuration (kitchen/tools/srk.conf). Save the file, and build again.
    2
    even adding different sizes manually keep failing to compile vendor and product and yes my device in a samsung A30
    You need to make your partitions larger. If that does not help, I hope someone familiar with the Samsung A30 can help.
    2
    please when I want to sign an error appears


    Exception in thread "main" java.lang.NoClassDefFoundError: sun/misc/BASE64Encoder
    at com.android.signapk.SignApk.addDigestsToManifest(SignApk.java:182)
    at com.android.signapk.SignApk.main(SignApk.java:468)
    Caused by: java.lang.ClassNotFoundException: sun.misc.BASE64Encoder
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
    at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
    at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
    ... 2 more
    1
    @Kocot1: There are tutorials on XDA, sniff around a bit. don't think the Kitchen covers what you're after. What you basically need is a neutralized vbmeta, you should be able to do it yourself.

    I recently encountered the same issue after buying a Galaxy Tab S7+ a few months ago.
  • 164
    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:

    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
    63
    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 :)