yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] SuperR.:
I do not know what that error means without the log or the firmware for testing.

Thank you for the detailed post :)

This problem is likely due to file permissions, contexts, or capabilities. When building an ext4 img file, the free kitchen uses a default set of permissions and capabilities from AOSP (Android Open Source Project), and a file_contexts file generated from your firmware. The donate kitchen will likely solve this issue as it uses the exact file permissions, capabilities, and contexts from the original firmware you extracted.
[SuperR Kitchen] aidanmacgregor:
Thanks For Quick Reply, Thats Good To Know, Can See Myself Going For The Donate Version Soon, Probably Post Xmas :D
[SuperR Kitchen] Online Gravy:
hi, when attempting to unpack my boot image i get this error

There is no ramdisk in this boot.img.

any insight?

i attached the boot.img and build.prop to this post
[SuperR Kitchen] MdNaushad:
any one help me for building process of the rom with SuperR 1.2..1.2

i can't build in original image to flash with twrp
[SuperR Kitchen] enolovedays:
Hy @SuperR.

I've tried u'r kitchen using WSL and phyton 6.7 it gave me error "platform not supported"

it there any solution?
[SuperR Kitchen] SuperR.:
You are working on a system-as-root device, so the ramdisk is in the system partition. The boot.img is actually recovery on these devices.

It is likely the free kitchen does not have all the features you need to get your img to boot. The donate kitchen will probably fix this issue.

The free kitchen does not work in WSL, only in native Linux. If you want to run the kitchen in WSL, the donate kitchen will solve this for you :)
[SuperR Kitchen] Kartun:
Hello.

I've problem with signing image on LinuxMint 20

java --version

openjdk 14.0.2 2020-07-14

OpenJDK Runtime Environment (build 14.0.2+12-Ubuntu-120.04)

OpenJDK 64-Bit Server VM (build 14.0.2+12-Ubuntu-120.04, mixed mode, sharing)

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:602)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
... 2 more
[SuperR Kitchen] HemanthJabalpuri:
It is because Java 9+ does not have that Base64 of sun package.

feat: Add Java9+ support · appium-boneyard/sign@4fea0ee

Sign.jar automatically signs an apk with the Android test certificate. - feat: Add Java9+ support · appium-boneyard/sign@4fea0ee

github.com

or

Use third party Base64 · HemanthJabalpuri/signapk@d74e496

SignAPK for recovery flashable zip signing in Android too.(Only testkey) - Use third party Base64 · HemanthJabalpuri/signapk@d74e496

github.com

will fix that
[SuperR Kitchen] b1k3rdude:
Can some one point me to the post that explains in laymans terms, what this Kitchen does? After looking at several threads related to this I have been able to find a simple 'about' etc.
[SuperR Kitchen] Samir2298:
Hey guys this kitchen works fine if I deodex rom BUT with an odexed ROM it bootloops. What could be the problem? I am on Marshmallow.
[SuperR Kitchen] The_Muttster:
HI all,

So my tech goal for 2021 is to learn more about Android (I work in DFIR) and thought I'd take a look at learning how to create custom ROMs. Recently, I got a new phone (Ulefone Armor 10) and since the manufacturer releases the updates on their site, I thought that would be a good place to start.

I've watched the videos, I've installed the free version with the ubuntu kitchen ISO and getting stuck in. So the image I'm using is this one for Android 10. Extracting it seems easy enough but when I just try to rebuild it with no changes, I get the following error:

vendor.img build failed. Directory will not fit:
img size: 614MB, dir size: 629MB

Any ideas?
[SuperR Kitchen] XxshaokhonxX:
@SuperR. Hello I have been trying multiple times tonight and I am tired of it to install a slightly modifed kernel/ rom to my tablet, yes it is a very old tablet from 2013 and is running android 4.2.2.

The ROM I am using is a custom rom and it is an AOKP 4.2 ported to the HSG1279 hanspree tablet, it works fine, the recovery I am using is also ported over and it is CWM based recovery v6.0.3.3, but I have also tried a ported TWRP version. But I keep running into the same problem and searching it up proves no results, whenever I try to install a custom ROM that I have modified /kernel I keep getting the Status 0 error and I am stuck.

The kitchen version I am using is the free linux one which I am using on ubuntu 20, the perm method I am using is the set_perm one due to the tablet only having android 4.2.2 on it. All I did to the kernel is I made it not secure so I can use adb's sideload function in recovery. This is the zip file for the kernel which has been modified, if you need the original one please let me know and I will happily attach it. I hope this can be fixed as I am hoping to port some custom ROM's/ kernels to this old tablet to get better features on it. I have also looked in the edify scripts to see for anomalies and I have noticed that certain entries have set_metadata_recursive at the beginning when I chosen to use set_perms. This is all the information that I think relate to the problem but if you need anymore let me know.

Might I add that I am running the free version on an ubuntu virtual machine as my base operating system is windows and I unfortunately have no money to purchase the donator version, but whenever I can I might purchase the donator version if I do not give up trying to port roms and kernels to this old tablet
[SuperR Kitchen] io2345:
Tried it several times, but with all settings I made the installation process on the phone ends immediately with a red message "Updater process ended with ERROR: 7. The last line before says "file_getprop: failed to stat "tmp/config": No such file or directory".

There is no directory "tmp", not in the original ROM (which installs fine), nor in the "kitchened" ROM. Tried to remove ROOT from the ROM, if that information helps...

Maybe you can tell me, what the "Unroot" does in background, then I could do it manually.
[SuperR Kitchen] Fire1511:
can't set metadata permission on oreo samsung firmware
[SuperR Kitchen] Terrierrok:
Hi! I was trying to use your tool but sadly when im about to pack the rom in a zip i always get this error while packing system.img

error: build_directory_structure: cannot lookup security context for /cust

Creating filesystem with parameters:

Size: 4831838208

Block size: 4096

Blocks per group: 32768

Inodes per group: 8192

Inode size: 256

Journal blocks: 18432

Label: system

Blocks: 1179648

Block groups: 36

Reserved block group size: 287

Sorry, im newbie in this world of android and im trying tu customize a MIUI ROM. Thx for your help.

Heres the log attached (i did multiple attempts, hehe)
[SuperR Kitchen] SuperR.:
You will need to remove some files from the project "vendor" directory so it will fit. The donate kitchen will likely solve this issue and build without needing to remove files.

You should be able to use set_metadata perm type for KitKat 4.2.2. I believe this Android version uses file contexts, which is the main difference between set_perm and set_metadata. Unfortunately I am not a kernel expert, but if unpacking or packing boot.img is the problem you would need to post on the AIK (Android Image Kitchen thread). SuperR's Kitchen uses AIK for boot.img unpack/repack.

If you are building a ROM for Android 10+, building a full ROM zip in the kitchen will probably not work. I have not been able to figure this out yet because I do not have a device to test on.

Unroot will remove root files from the extracted firmware in the kitchen project you are wrking on. It removes the su binary, superuser.apk, SuperSU.apk, etc.

This is not enough information to help you.

The free kitchen uses make_ext4fs to build ext4 img files. make_ext4fs is out of date and may not work properly for Android 10+. The donate kitchen will solve this problem 100%.
[SuperR Kitchen] datecasp:
Hi @SuperR.

I'm using the kitchen (last version in Ubuntu 20.04) trying to modify a ROM from smg355H to smg355HN. It's crDroid 5.1.1 and I have modify the build.prop file to adjust some parameters to the device and the asserts.

When I go to install it with TWRP I get an error with file getprop /tmp directory doesn't exists

Any idea?

TIA!

**EDIT** Solved! I was a problem with the metadata. Must set to "set_metadata" and I was using "Sparse". Now I'm stucked in bootloop to recovery so I must still working in the port...
[SuperR Kitchen] troublebao:
如何学习制作定制的rom？需要了解哪些知识？
[SuperR Kitchen] _D.X.Y:
I can solve the problem of normally packaging the dynamic partition of Android 10-11 without WSL and wsl2. It is readable and writable. There is no problem with permissions. Can you send me a complete kitchen under windows for free?
[SuperR Kitchen] SuperR.:
No
[SuperR Kitchen] dataghost2014:
Dude, stop asking for free handouts, my friend here working on this project puts his heart and soul into, if only you knew the hours he has put into this stuff.... And no its not that easy, as soon as you make changes, the OS recognizes that and is blocked, things are being worked on, but its not the snap of a finger. If you want to do it, get your hands on SDK like I do, and build from the ground up. And please do not ask if we can give you SDK.... Does not work like that, talk to a manufacturer if you have one, it burns my ass, the people asking for free handouts all the time when a dev puts thousands of hours into stuff like this....
[SuperR Kitchen] dataghost2014:
Wrong person I am responding to, thanks for all you hard work brother.
[SuperR Kitchen] dataghost2014:
And FYI, you do not need a kitchen, lpmake... lpunpack, you can mount edit and repack, but it is going to fail.
[SuperR Kitchen] _D.X.Y:
Sorry to interrupt. It doesn't matter if you don't need help,
[SuperR Kitchen] dataghost2014:
Pay the donation for the kitchen, and honestly if you are a developer you don't need a kitchen to be able to mount and edit files.
[SuperR Kitchen] SuperR.:
v1.2.1.3

Changes:

Fixed downloads so kitchen can complete the install.

Fixed building some img files that were failing with the out of space error.

Fixed all symlinks going in symlinks-system file when using mount to extract a single partition that is not system.

Fixed extracting some newer img files that can only be mounted as read-only.

Unpack odm.img from payload.bin if it exists.

Store project forceencryption type in project srk.conf instead of main srk.conf.

Added support for extracting Samsung Beta firmware with AP_xxxx.tar in a 7z file.

Fixed some devices by-name paths not being found during the ROM flash.

Fixed Busybox download not working due to the change in the XDA website.

Allow boot.img to unpack in a new project even if there is no default.prop.

Fixed new.dat conversion on partitions with a period in the name.

Fixed mount extract adding rootfs context for /system on system-as-root firmware.

Fixed extracting 7z files that contain files/directories with spaces in the name.

Fixed regression where old ROM files/directories are not moved before extracting new.

Detect spaces in manually created project names and replace with underscore.

Use auto for mount filesystem type argument instead of ext4, which should allow extracting any filesystem type your kernel supports.
[SuperR Kitchen] furniturewinches:
Added support for extracting Samsung Beta firmware with AP_xxxx.tar in a 7z file.

Fixed some devices by-name paths not being found during the ROM flash.

Fixed Busybox download not working due to the change in the XDA website.

Allow boot.img to unpack in a new project even if there is no default.prop.

Fixed new.dat conversion on partitions with a period in the name.

Fixed mount extract adding rootfs context for /system on system-as-
[SuperR Kitchen] godofsalt:
Mr. SuperR

I Thank You for some major improvements and fixes!!

(Not truly aware of MS issues with win 11, I was forced to downgrade to Win10. Which means I had to wipe half my disc, and reinstall Win10- In doing so, this time around, I actually upgraded my Ubuntu to 21.10 at same time.)

After Ubuntu 21.10 was up and going properly, I add Kitchen back and was having major issues. thought it was all my end. I see that it's not!!!

Awesome.

I THANK YOU!!
[SuperR Kitchen] MinhaD:
@SuperR. SuperR's Kitchen Free Version : 1.2.1.3 can't mount system.img to extract files and can't do boot.img modification like disable dm verity and others on Ubuntu 21.10 with all the dependencies installed. I've used version 1.2.1.2 without any problem. Is it me or there are bugs in new update?
[SuperR Kitchen] el-sahef:
I want to add init.d support to my boot.img but the last SuperR Kitchen version that included this feature was v1.1.9.3 according to the changelog. Is this version still available for download somewhere? Why was this feature removed?
[SuperR Kitchen] AnonVendetta:
The feature was removed because both Magisk and SuperSU support script execution on boot, without needing

init.d. However, if you know how to unpack/repack boot.img manually, you can try adding it yourself.

Grab the files from this page (including the contents of the sbin folder).

Init.d Github files

Unpack your boot.img. Put the files in the proper places, doing edits if necessary (probably will also need to edit init.rc to call the init.d script). You may also need to patch sepolicy to allow init.d to work. Repack boot.img and flash it. I cant remember the exact specifics, but that's the gist of it, i've done it before.

Other things you can try:

1. init.d injector by @Zackptg5

2. Kernel init.d support injector by @osm0sis (Kernel init.d support injector)

You can also use busybox's run-parts to execute init.d scripts on boot.
[SuperR Kitchen] lieuliau:
I have this problem when try to extract this rom https://androidfilehost.com/?fid=6006931924117893521. Please help me fix it! Thank you! I'm using v1.2.1.3, copy this zip file to folder and choose 4 to extract rom.
[SuperR Kitchen] stranger75:
SuperR's Kitchen Free Linux Version : 1.2.1.3 can't mount system.img to extract files :

ext4_extract.log

Extracting system.img with Mount ...

[12002] Failed to execute script superr

Traceback (most recent call last):

File "superr.py", line 35, in <module>

File "mainsrk.py", line 59, in mainsrk.superr

File "mainsrk.py", line 18, in mainsrk.superr.mfunc

FileNotFoundError: [Errno 2] No such file or directory: '--otherfile'
[SuperR Kitchen] alexp1289:
Trying to extract a stock Motorola A11 firmware zip from lolinet and I keep getting this.

Extracting images from zip ...

Traceback (most recent call last):

File "superr.py", line 35, in <module>

File "mainsrk.py", line 34, in mainsrk.superr

File "<string>", line 4803, in superr

File "<string>", line 2304, in extract_new

File "<string>", line 2344, in imgextract

File "<string>", line 2963, in sparse_chk

FileNotFoundError: [Errno 2] No such file or directory: 'system.img'

[17349] Failed to execute script superr
[SuperR Kitchen] SuperR.:
v1.2.1.4

Changes:

Fixed ext4 img files not mounting and crashing the kitchen.

Updated to Python 3.8.

Fixed kitchen updater for future updates.

Happy New Year!!!

NOTE:

This build may not work on older Linux. It was compiled in Ubuntu 20.04, so it will work in 20.04 and newer.

NOTE_2:

It seems that updating from v1.2.1.3 will not work. A fresh install will be needed. The updater has been fixed in v1.2.1.4 so future updates should go well. Sorry for the inconvenience.
[SuperR Kitchen] ShevT:
Kubuntu 21.10. On boot:

Verifying file checksums ...
tput: /home/qqq/AndroidTools/SuperRs-Kitchen_v1.2.1.4/tools/source/libtinfo.so.6: version `NCURSES6_TINFO_6.2.current' not found (required by tput)
[SuperR Kitchen] xdadevc:
The OP said it was compiled with 20.04. I'd suggest statically compiling the tool, but until then, you're better served off with ubuntu 20.04.
[SuperR Kitchen] xdadevc:
I'm trying to extract a Motorola One (codename: deen) image of Android 10. The tool will start well (ubuntu 20.04) and extract some parts of system.img.

It fails after a while with this error:

Extracting system.img with Mount ...

Extracting system.img with Mount ...
mount: /home/void/t/superr/superr_deen/output: wrong fs type, bad option, bad superblock on /dev/loop3, missing codepage or helper program, or other error.
ERROR: system.img is not a valid ext4 img.

The console shows instead this:

system.img: Converting sparse img ...
FileNotFoundError: [Errno 2] No such file or directory: 'system/' -> 'system1/'
[1076] Failed to execute script 'superr' due to unhandled exception!

Press "q" to Quit, or "r" to Restart

In system1 I can see some files were extracted. perhaps not all. The contents of few of them I checked seem legit.

EDIT:

Here's the contents of the unpacked zip file.

drwxrwxr-x 4 void void 4096 Jan 5 16:25 00_project_files
-rw-r--r-- 1 void void 67108864 Sep 22 18:31 boot.img
-rw-r--r-- 1 void void 186845192 Sep 23 12:20 oem.img
drwxrwxrwx 22 void void 4096 Jan 5 16:25 system1
-rw-rw-r-- 1 void void 2684358656 Jan 5 16:17 system.img
-rw-rw-r-- 1 void void 2684489728 Jan 5 16:18 system_other.img
-rw-rw-r-- 1 void void 536875008 Jan 5 16:17 vendor.img
-rw-r--r-- 1 void void 1650726763 Jan 5 16:05 XT1941-4_DEEN_RETEU_10_QPKS30.54-22-13-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

The vendor image is extracted without problems. I'm guessing an issue in handling the system and system_other renaming stuff.

EDIT2: The system_other.img when extracted by itself gives an immediate error. Extracting system.img seems to extract all then gives the system->system1 error. Extracting vendor.img works. The other that does NOT work is oem.img

Let me know if you need more info/debug on my image.

Thanks.
[SuperR Kitchen] SuperR.:
Please send a link to the full firmware so I can do some testing (please no login required for the download). Thanks.
[SuperR Kitchen] xdadevc:
Yes, naturally. You can download the last official image from this mirror

Thanks for the tool btw.
[SuperR Kitchen] SuperR.:
v1.2.1.5

Changes:

Fixed non-sparsechunk img files in Motorola firmware not getting the header fix.

Fixed crash on a failed payload.bin unpack.

@xdadevc - Your firmware should unpack properly now :)
[SuperR Kitchen] xdadevc:
Indeed, it works now. Thank you!
[SuperR Kitchen] :
Does it also provide a version that can run on WINDOWS 10-11 that is automatically updated upon donation?
[SuperR Kitchen] leonardo223:
S10 Android 12 trying to make the final zip fails in

Choose partition size detection method for system

with this error only on system, vendor img is not affected and the choices will not make any difference its the same error

[INFO] Building system_new.img

error: build_directory_structure: cannot lookup security context for /audit_filter_table

Creating filesystem with parameters:

Size: 5976883200

Block size: 4096

Blocks per group: 32768

Inodes per group: 8112

Inode size: 256

Journal blocks: 22800

Label: system

Blocks: 1459200

Block groups: 45

Reserved block group size: 359

@SuperR.
[SuperR Kitchen] dataghost2014:
This is a piece of art. Well done on this.
[SuperR Kitchen] gcrutchr:
Error deodexing Samsung S22 ultra ROM: see attached

additional info:

[INFO] Processing 1 file(s) from core-icu4j.vdex

[ERROR] [3131] 2022/02/28 07:39:23 (vdex_api.c:58 vdexApi_initEnv) Unsupported Vdex version

[WARNING] [3131] 2022/02/28 07:39:23 (vdexExtractor.c:235 main) Invalid Vdex header - skipping 'core-icu4j.vdex'

[INFO] 0 out of 0 Vdex files have been processed

[INFO] 0 Dex files have been extracted in total

[INFO] Extracted Dex files are available in '.'
[SuperR Kitchen] MinhaD:
Hey @SuperR. Can you address this prblm?
[SuperR Kitchen] akrox:
Kitchen version: 3.2.2.2

Running on: WSL 2

Device: S906B - Samsung S22+

Started from: AP.tar

Android version: 12

ROM: https://www.sammobile.com/samsung/g.../SM-S906B/MEO/download/S906BXXU1AVA7/1614073/

Problem:

Log in file ext4_extract.log:

Extracting system.img with Mount ...

mount: /home/fernando/kitchen/superr_s906b/output: unknown filesystem type 'f2fs'.

ERROR: system.img is not a valid ext4 img.

Use the support option in the Misc Tools menu and attach the support.zip to your post.

Uploaded directly through Misc Tools.

Tomorrow gonna try in full linux env.
[SuperR Kitchen] Whosondephone:
Firstly thank you for this.

The Computer is intel core 2 quad, Debian 11 amd64

Kitchen Version v1.2.1.5

The phone is a LG V20 running TWRP 3.2.3.1

The OS is Oreo 8.0

I'm getting an error when flashing the zip in TWRP 3.2.3.1

"location argument to mount() can't be empty"

Spoiler content hidden.

The Verizon variant of the LG V20 received and OTA update that isn't available anywhere else. In order to obtain this update the phone has to be completely stock and unrooted. The reason I'm interested in this update is because I believe that it is the only way to enable wifi calling on a fresh ROM install. This is my first attempt at creating a ROM. I used the dump feature of LGUP to pull the images off the unmodified system.

I looked inside a stock rom zip made by NotYetADev as a template for what partitions/disk images would be needed to create a zip. [VS995][Oreo][Stock][Rooted] Verizon LG V20 Stock Oreo rooted flashable zip First I actualy just replaced the *.bin files in his zip with the ones from the dump and it seemed to work. However perhaps incorect/original OS from the zip shows in settings. I'm guessing the old build.props was flashed.

In the kitchen I created a new project.

Added the *.img files to the project folder.

4) Extract system.img for new ROM

Added all the *.img files from my dump that i saw inside NotYetADev's zip to the ROM EXCEPT cache.img

First attempt I tried set_metadata for Perm Type

Second attempt raw_img Perm Type

The boot img was patched with Magisk24.3 however in the root menu it showed not rooted. Even though I figured the program didn't check I opted to patch it again for magisk.

I don't remember what i did initially for Asserts. I believe the menu was diferent for a new project. I'm stuck with this Elsa option now, don't know what it means. But I added us996 and vs995 to the list. It shows now: elsa,us996,vs995

Then i built it without signing. The program warned I didn't have enough RAM for sighning. 8GB

List of images added to the ROM:

abootbak.img (i'm assuming dirty santa from NotYetADev)

aboot.img (dirty santa from NotYetADev )

apdp.img

boot.img (Magisk Patched 24.3)

cmnlib64bak.im

cmnlib64.img

cmnlibbak.img

cmnlib.img

devcfgbak.img

devcfg.img

factory.img

hypbak.img

hyp.img

keymasterbak.img

keymaster.img

lafbak.img

laf.img

modem.img

msadp.img

persist.img

pmicbak.img

pmic.img

raw_resourcesbak.img

raw_resources.img

rct.img

recoverybak.img (TWRP3.2.3.1)

recovery.img (TWRP3.2.3.1)

rpmbak.img

rpm.img

sec.img

system.img

tzbak.img

tz.img

xbl2bak.img

xbl2.img

xblbak.img

xbl.img

If someone could give me some pointers I'd really appreciate it! Thank again If this ends up working I'll definitely pick up the paid version.
[SuperR Kitchen] russel5:
please add wsl support

i can compile full rom (like crdroid) on wsl, but your kitchen is not working.
[SuperR Kitchen] dataghost2014:
His kitchen works fine on WSL/WSL2
[SuperR Kitchen] dataghost2014:
Then it's your setup or it's your permissions one of the two, make sure it's set to executable, but it works fine. Use the donate version.
[SuperR Kitchen] russel5:
:)

i'm can compile a full rom from sources, but can't grand some permissions to the kitchen *facepalm*

and this is FREE thread support
[SuperR Kitchen] dataghost2014:
I understand it's the free support but sending the guy like 20 bucks or something to get the paid version is worth it, I don't know how much he's supporting of the free stuff anymore I have no clue all I know is the guy puts in countless hours and sending somebody 20 bucks as a thank you to get a premium version as a drop in the bucket.