[ Windows / Linux / Mac ][DONATE] SuperR's Kitchen (v3.2.1.5 - 4-5-2021)

Search This thread
So I am a new owner of a Galaxy S20FE (G781B) and like others I am running into that the brick wall that is the lack of custom ROMs for this device.

I then came across this thread, but the issue I will have right off the bat, is that despite being a mac/pc engineer I have very little linux knowledge.

I have tried to find some beginner info on this ROM kitchen to try and learn what might be involved, but am not getting very far.

thanks.
 
Last edited:
  • Like
Reactions: rhewins2268

SuperR.

Recognized Developer
Mar 23, 2014
2,573
8,535
Invisible
So I am a new owner of a Galaxy S20FE (G781B) and like others I am running into that the brick wall that is the lack of custom ROMs for this device.

I then came across this thread, but the issue I will have right off the bat, is that despite being a mac/pc engineer I have very little linux knowledge.

I have tried to find some beginner info on this ROM kitchen to try and learn what might be involved, but am not getting very far.

thanks.
There are some fairly old tutorial videos here. There will be a few differences in the kitchen now, but for a general overview it should work for you :)
 

godofsalt

Senior Member
Oct 2, 2011
404
196
Southwest, Ohio
SuperR.
Hey there! I want to say it out load, in public too
Thank you for your help. Seems easy, only use 1 PC! so Should be good!
OK, hard part is all the catching up. Coming from Samsung Galaxy S5 (2012) to a more recent edtion... Galaxy S20 FE 5G !! So am am sure I will bother you more , later on that...
Again, I Thank you for your help today.
 
  • Like
Reactions: SuperR.

SuperR.

Recognized Developer
Mar 23, 2014
2,573
8,535
Invisible
Hi,

Has anyone tried to edit service.jar using SuperR's Kitchen tools? Please give the team info
Best Regards,
Thaks You.
I have done this many times, but probably not with the firmware you are using. The kitchen (apktools plugin) uses apktool.jar to unpack/repack apk/jar. If apktool.jar works with your firmware, the kitchen will work too.
I rebuilt the original rom, didn't change anything and it didn't work. I don't know where the cause isI rebuilt the original rom, didn't change anything and it didn't work. I don't know where the cause is

android 11
link : https://androidfilehost.com/?fid=17248734326145743746

I think there is a problem with packing .img android 11
I am sure there is a problem repacking Android 11 in the native Windows kitchen. This is why I have been relentlessly encouraging the use of WSL2. I suggest WSL2 to you as well considering support for the native Windows kitchen is ending and these build problems will not be fixed.
 

sasohan9

New member
Jan 18, 2019
4
0
Dhaka, BD
t.me
Dear sir, at first, thanks a lot for the tool.:love:

One of my friends has the paid tool of the latest version. He tried to unpack-repack the rom of device Xiaomi Redmi K30 Pro (codename: Lmi). The unpacking works without any issue, but the rom is not repacking on both Windows & Linux (by wsl2) system. He told me that, he did not change anything or any file into the system. But still the rom is not repacking, the error is on system capacity.
Here I am attaching a screenshot of the unzipped original rom.
IMG_20210302_122859_419~2.jpg


Sir, please do you know how to solve this?
 

SuperR.

Recognized Developer
Mar 23, 2014
2,573
8,535
Invisible
Hi,
Has anyone tried editing service.jar using SuperR Kitchen?
edit service.jar for the location is fake.

Greetings,
Thank you.
I answered you the first time you sent this message.
Dear sir, at first, thanks a lot for the tool.:love:

One of my friends has the paid tool of the latest version. He tried to unpack-repack the rom of device Xiaomi Redmi K30 Pro (codename: Lmi). The unpacking works without any issue, but the rom is not repacking on both Windows & Linux (by wsl2) system. He told me that, he did not change anything or any file into the system. But still the rom is not repacking, the error is on system capacity.
Here I am attaching a screenshot of the unzipped original rom.
View attachment 5237377

Sir, please do you know how to solve this?
Your friend should read the 00_project_files/logs/img_build.log. It contains all the suggestions I have for this issue.
Take a look at the suggestions in the log you sent.
 

bdunghd68

New member
Mar 2, 2021
4
0
I answered you the first time you sent this message.

Your friend should read the 00_project_files/logs/img_build.log. It contains all the suggestions I have for this issue.

Take a look at the suggestions in the log you sent.
I have tried to delete some files. Repack ok. Error when flashing
 

Attachments

  • IMG_20210304_094334.jpg
    IMG_20210304_094334.jpg
    513.4 KB · Views: 13

Sapiens

Senior Member
Jan 22, 2007
51
6
Hello everybody,

I need some help please. I have a Samsung Note 20 ultra (sm-n986b) and a Samsung Galaxy Tab S7 Plus (sm-t976b) with Android 10, both have TWRP.
I tried to use the kitchen to update to Android 11 by downloading the official Samsung firmware from Sammobile:



At first, I tried removing KNOX and injecting Magisk. Leaving the rest untouched. It built fine but TWRP stopped the installation just saying that there was an error installing the zip file. No more details about what the error was.

So I tried to simplify even more the modification of the built. I did the following:

I selected NOT to extract the extra partitions
NO chache, optics, product, vendor, prism, odm images extracted
Perm type set to raw_img (as per advice here)
Selected option 7-Boot/Recovery tools
There was no option to unpack boot.img, only to pack it.
Selected option 2 which unsecured the boot.img
Option 3-Add/remove dm-verity showed "disabled". After selecting that option it remained the same
Selecting option 4-Add/remove forceencrypt did nothing. It remained as N/A.
Selecting option 1-Pack boot.img did nothing
Went back to main menu
Selected option 8-Rom tools
Then selected option 7-Build menu
Chose option 1-Build full rom zip
Chose option number 4: To use the system.img for the partition size of system
Selected NOT to sign the zip

It built the zip with no errors, but once again when trying to flash on TWRP it stops says there was an error and the log shows no specific error.

I tried in both , the phone and the tablet, many times. Sometimes extracting all the partitions but with the same result. I just want the original firmware almost untouched, just rooted and without KNOX to be flash on TWRP.

I am using the kitchen in windows WSL2 ubuntu linux.

I have used the kitchen to build other simple roms like this without much of a problem. But I dont know if it is Android 11 or Samsung new firmware or the kitchen or just simple human error. In either case, I request your assistance please. Thanks in advanced.
 

dr.ketan

Recognized Developer / Recognized Contributor
Apr 9, 2011
34,784
68,477
Gujarat, India
drketanrom.com
Hello everybody,

I have used the kitchen to build other simple roms like this without much of a problem. But I dont know if it is Android 11 or Samsung new firmware or the kitchen or just simple human error. In either case, I request your assistance please. Thanks in advanced.
What is rom zip size?
If your image size is bigger than 4GB it won't flash by twrp. N20 have huge size. Also it have super.img and that need permission type dat.
Can you share your update-script from zip created?
 
  • Like
Reactions: SuperR.

Top Liked Posts

  • 1
    Awww... :(

    Error1.jpg


    cat img_build.log yields:
    Error2.jpg


    Which is odd. This has worked before. This exact rom.
    I must have installed something or done something that has messed things up.
    And I have no idea...
    1
    Awww... :(

    View attachment 5280329

    cat img_build.log yields:
    View attachment 5280331

    Which is odd. This has worked before. This exact rom.
    I must have installed something or done something that has messed things up.
    And I have no idea...
    I think this is a new issue in v3.2.1.5. For now, you can try building in v3.2.1.4. If it works properly, I think it will be fixed in the next update.

    It turns out that the tune2fs binary included in the kitchen gives a segmentation fault on some machines, no idea why (thanks @edzamber for pointing it out). tune2fs in the kitchen is responsible for reading EXT4 information (including EXT4 features) from an img file. In v3.2.1.4, there was a backup in place to use default features if tune2fs was not able to complete its job for any reason. When I added the include/exclude features option in v3.2.1.5, somehow I broke the default features being used. Without tune2fs and without default features, the build will fail.

    You can check to see if tune2fs is giving you a segmentation fault by running the img_tools plugin option 6. If you see the segmentation fault, this is almost certainly your issue. I have eliminated tune2fs in the next update by writing a python implementation to accomplish the same functionality. I have also fixed the defaults to work again if required. This should solve the problem :)
    1
    So it did! v3.2.1.4 worked without a hitch. Thank you!
    The problem was even worse with another ROM I started out with. Because it just went belly up, told me there was an error making the image, told me to look in img_build.log, but img_build.log only said:

    [ERROR] Something went wrong while building system_new.img.

    And that wasn't very helpful... That's why I tried a ROM I knew compiled without a problem before.
    I tried targzipping the directory over to a laptop of mine, ran it there, and yup, noticed your new feature that means I can only use it on one computer. Don't worry, I understand. It's just, I tried a few things before getting here.

    But this worked. Thank you!

    Oh, but speaking of, if I format my computer some time in the future and need to install the kitchen all over again, on the same computer, can that be done if I message you?
    Next update will have better error logging during img build.

    Normally, formatting and reinstalling your OS will not cause a problem authenticating. Try the kitchen first. If it says not authorized, you can reset PC authentication on the kitchen downloads page. If you have trouble with authentication, you can always message me privately.
  • 4
    v3.2.1.4 has been released.

    Details in the release post :)

    NOTE_1:
    My apology once again, all versions before v3.2.1.4 are now disabled, with the exception of Windows v3.2.1.3. Security issues were found and fixed. I truly wish I did not have to do this, but it's better than quitting the project I guess :)

    NOTE_2:
    There is a new thread dedicated to the kitchen CLI. All features and example commands will be updated there as they become available. The syntax changed since the initial release so if you are using the CLI you should check out the thread.
    3
    is it possible to edit fastboot rom and flash it with mi flash tool
    Other users say they do this with the kitchen, but the kitchen will not automatically pack your firmware. You can unpack your firmware, make modifications, and repack the ext4 img files any way you would like.
    I tried to update to latest v3.2.1.4 (linux) but I get some checksum didn't match error and asking me to do a fresh install.
    2 out of last 3 updates asked me to reinput my credentials even I told it to save the password. This security/mistrust thing is a bit of overkill in my opinion.

    I hope you'll be able to improve this in the future releases.

    Thank you anyway for continuing the project.
    Thanks for the info. I now realize why the checksum error is happening and will get it fixed for the next update.

    The credentials issue was explained in the last update post. I have changed the way passwords are stored on your PC and on the server. Once all users have converted their passwords, I can change the login requirements back to how it was.

    I know the security stuff is annoying to you and other users. Imagine how annoying it is for me when I find out that someone has found a way to steal my software. Perhaps this is not important to you, but it is to me. If I am not able to continually prevent it I will discontinue the project. I hope you agree that entering your password more than you want is worth the continuation of this project :)
    2
    The new zips are on the kitchen downloads page sent to you after registration.

    Do a fresh install of v3.2.1.5 and you should be good. Everyone else that has not tried to update yet should also be good. Thanks for pointing out the problem :)
    1
    Unfortunately the kitchen server is currently down. The data center is having issues so there is nothing I can do except wait. My apologies for the inconvenience.

    edit: seems to be back up for now. Let's hope it stays that way 🙂

    edit2: down again 😔

    edit3: up again 🙂
    1
    So it did! v3.2.1.4 worked without a hitch. Thank you!
    The problem was even worse with another ROM I started out with. Because it just went belly up, told me there was an error making the image, told me to look in img_build.log, but img_build.log only said:

    [ERROR] Something went wrong while building system_new.img.

    And that wasn't very helpful... That's why I tried a ROM I knew compiled without a problem before.
    I tried targzipping the directory over to a laptop of mine, ran it there, and yup, noticed your new feature that means I can only use it on one computer. Don't worry, I understand. It's just, I tried a few things before getting here.

    But this worked. Thank you!

    Oh, but speaking of, if I format my computer some time in the future and need to install the kitchen all over again, on the same computer, can that be done if I message you?
    Next update will have better error logging during img build.

    Normally, formatting and reinstalling your OS will not cause a problem authenticating. Try the kitchen first. If it says not authorized, you can reset PC authentication on the kitchen downloads page. If you have trouble with authentication, you can always message me privately.
  • 156
    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_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 (email address for all options found here):
    1. Google Pay (Preferred method)
    2. Paypal through my website
    3. US Amazon eGift card

    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:

    Windows:

    NOTE: The native Windows version has reached end of life. Consider running the Linux kitchen in WSL2 using the guide below.​
    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.

    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

    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
    62
    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.
    42
    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 :)
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone