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
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
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.I'm running into an issue when I am attempting to extract the system.img into the project. All it says is:
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.
Kitchen version: v188.8.131.52
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 send a link to the firmware you are trying to extract so I can take a look.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: ''
 Failed to execute script superr
Will it be supported in the future?
I am not sure.
I am not a Samsung user and have never used odin, but I think you need to create tar.md5 files to flash in odin. You can use the samsung_tools plugin for this.
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.
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.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.
mpv "/home/user/music/my_favorite_song.mp3"and now it plays my favorite song at the end of the full ROM build.
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
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.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?
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.
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=Noand save the file. Now when you build your img file it will not contain the shared_blocks feature.
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.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 )
The windows kitchen uses make_ext4fs. You can use make_ext4fs in the Linux kitchen too. Add
use_make_ext4fs=Yesto the main configuration (kitchen/tools/srk.conf). Save the file, and build again.
please when I want to sign an error appears
Exception in thread "main" java.lang.NoClassDefFoundError: sun/misc/BASE64Encoder
Caused by: java.lang.ClassNotFoundException: sun.misc.BASE64Encoder
... 2 more