yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] SpasilliumNexus:
On a Pure here too and I've posted about it a few posts back. I've tried to do a checkout of a last known working version for me (0.9.2.5) but a ton of files don't recover (I get a bunch of DELETED.git-id files.)

Right now, the only option to have a bootable ROM is to use the custom zip menu. I forgot what it's labeled as as I'm not home to see, but it's the one with making a zip with app + framework + priv-app and some other combinations.
[SuperR Kitchen] :
Just made a new unrooted rom with the kitchen. Do you want me to just unpack and repack the boot.img or modify it by adding init then repack?
[SuperR Kitchen] SuperR.:
Just unpack and repack with no modification. I am trying to determine if the unpack/repack is causing your bootloop or if the mods I made to the test img simply did not work. Thanks :)
[SuperR Kitchen] :
When I try and build the rom I get an error message unless I remove the bootimg folder, the kitchen then deletes the ramdisk and repacks the kernel again. So i removed the boot.img and started again unpacked and repacked keeping the ramdisk and deleted the bootimg folder before building. Hope that all makes sense lol
[SuperR Kitchen] SuperR.:
It does make sense. The requirement to repack the boot.img before building is leftover from much earlier versions of the kitchen that zipped everything in the project directory to build a rom. I will remove that requirement since it is no longer needed. Thanks for reminding me :)
[SuperR Kitchen] Hamidreza2010:
[MENTION=5787964]SuperR.[/MENTION] Hi

i install linux mint.i want to run this kitchen but get this error

how can i solve this?

thanks
[SuperR Kitchen] ferbulous:
Using the latest one 64 bit linux (0.9.3.5)

Having some trouble compiling deodexed zip file, right after choosing system detection method (adb method)

I'm just getting a zip file around 7mb size without the system files

Anyway I can fix this?
[SuperR Kitchen] SuperR.:
It seems like the superr script does not have permission to execute. You can try starting with a git pull instead of the zip. Or, if you copied the files you extracted from one directory to another, try unzipping directly into the directory. One or both should sort out your issues.
[SuperR Kitchen] SuperR.:
Make sure you have installed the 32-bit core libs from post #4.
[SuperR Kitchen] :
Don't know if I'm being dumb here. I get error flashing with the assert check telling me I have a treltexx device and the rom is for a trelte device. If I remove or edit the assert check then I get an update binary error. I'm guessing I'm doing something dumb lol
[SuperR Kitchen] SuperR.:
This problem arises when the recovery says your device is one thing and the assert says it is another. If you add the device your recovery says you have to the asserts using the kitchen, it should work. If not, send me your updater-script so I can have a look.
[SuperR Kitchen] ferbulous:
Forgot to mention I've already done that, still getting 7mb file. I'll be trying the older version of the kitchen
[SuperR Kitchen] :
Changing the assert in the kitchen gives me the same update binary error I'm afraid, at least I know i edited the updater script correctly when I tried it I guess

https://www.dropbox.com/s/otra76gagp16nwt/META-INF.zip?dl=0
[SuperR Kitchen] SuperR.:
Your binary issue is because there is no block specified for formatting. For some reason it is using the byname file instead of the mmc file.

format("ext4", "EMMC", "mmc/system", "0", "/system");

Can you check to see if there is a superr_mmc file in the /tools/devices/treltexx directory? If not, that is the issue. I have no idea how this happened, but if you copy the superr_mmc file from /tools/devices/trelte to /tools/devices/treltexx it should work for you.

edit: this is assuming of course that the blocks are the same between trelte and treltexx

edit2: I think I know how it happened. If you created your device support from a recovery.img that says it is trelte and your device is treltexx, your mmc would go in trelte but a device would still be created in treltexx with the byname file including only "mmc". I am not sure how to deal with this yet and will need to think about it a bit. For now, the suggestion I mentioned above should sort you out.
[SuperR Kitchen] :
Treltexx is eynos and trlelte is snapdragon note 4. I know all the block paths are different. The partition tables are different,I can upload my portion table if you want .

I think I know the problem, the treltexx folder isn't in tools/devices. I just used the option 5 in rom tools option
[SuperR Kitchen] SuperR.:
I just looked at the build.prop for the SM-N910C.

ro.product.name=treltexx
ro.product.device=trelte

The kitchen uses ro.product.device=trelte to create the device directory. Even if the blocks are different it should still populate the updater-script using the superr_mmc file from the trelte device. Are you missing the trelte superr_mmc file? I am confused
[SuperR Kitchen] :
Sorry the trelte file is there in devices but treltexx isn't
[SuperR Kitchen] SuperR.:
Moved to the free kitchen thread.

I am not sure what your issue is exactly, but the donate kitchen will certainly fix it assuming your system directory will actually fit in the system.img. It is far superior in many ways.

Alternatively, if you want me to check the firmware send a link.
[SuperR Kitchen] rcmpayne:
Thanks, Just donated and sent you a PM

Image

8.1.0 (OPM2.171026.006.C1, Jun 2018)

https://dl.google.com/dl/android/aosp/walleye-opm2.171026.006.c1-factory-1c0e0e5a.zip
[SuperR Kitchen] drzainzaffar:
Im sorry if this is been asked many time but i have been trying to deodex samsung 8.1.0 had tried everything but failing to succeed im stuck at samsung logo ... i know kitchen shows warning before deodexing ... but i can really apprecaite the help is there anything that supports samsung deodexing ?
[SuperR Kitchen] Cakzemprongzzz:
Hi.. Is this kitchen still work for Android 10 OneUI 2.0 Note 9?
[SuperR Kitchen] Fazri Arrashyi Putra:
Hi,This work deodex MIUI 11 Pie?
[SuperR Kitchen] Miustone:
So is it possible to edit GSIs like PHH AOSP and bring it back into a flashable system.img? That would be super killer since recoveries are dying...

Edit: Looks like i can't...

ERROR:
Something went wrong building the image.

Make sure your partition size is correct and
that the directory is not too big to fit.

Press ENTER to return to ROM Tools menu
[SuperR Kitchen] Cyterafle:
Hi,

First of all,thanks for the awesome Kitchen

And will the free version be updated to support Android 10 ROMs ?
[SuperR Kitchen] SuperR.:
I have been very busy with life, love, and work. All of my free time lately has been dedicated to maintaining/upgrading the donate kitchen.

The free kitchen will be updated when I have more time. Unfortunately I have no idea when this will happen.
[SuperR Kitchen] TheRealModder:
why the kitchen doesn't run on Windows Subsystem For Linux 2?

I really need this kitchen.

justine@DESKTOP-E27H15V:~/superr$ ./superr
Loading ...
Platform not supported

Press "q" to Quit, or "r" to Restart
justine@DESKTOP-E27H15V:~/superr$ neofetch

.-/+oossssoo+/-. justine@DESKTOP-E27H15V
`:+ssssssssssssssssss+:` -----------------------
-+ssssssssssssssssssyyssss+- OS: Ubuntu 20.04 LTS on Windows 10 x86_64
.ossssssssssssssssssdMMMNysssso. Kernel: 4.19.104-microsoft-standard
/ssssssssssshdmmNNmmyNMMMMhssssss/ Uptime: 1 hour, 16 mins
+ssssssssshmydMMMMMMMNddddyssssssss+ Packages: 707 (dpkg)
/sssssssshNMMMyhhyyyyhmNMMMNhssssssss/ Shell: bash 5.0.16
.ssssssssdMMMNhsssssssssshNMMMdssssssss. Terminal: /dev/pts/0
+sssshhhyNMMNyssssssssssssyNMMMysssssss+ CPU: Intel i7-8550U (8) @ 1.991GHz
ossyNMMMNyMMhsssssssssssssshmmmhssssssso Memory: 84MiB / 6249MiB
ossyNMMMNyMMhsssssssssssssshmmmhssssssso
+sssshhhyNMMNyssssssssssssyNMMMysssssss+
.ssssssssdMMMNhsssssssssshNMMMdssssssss.
/sssssssshNMMMyhhyyyyhdNMMMNhssssssss/
+sssssssssdmydMMMMMMMMddddyssssssss+
/ssssssssssshdmNNNNmyNMMMMhssssss/
.ossssssssssssssssssdMMMNysssso.
-+sssssssssssssssssyyyssss+-
`:+ssssssssssssssssss+:`
.-/+oossssoo+/-.
[SuperR Kitchen] Cyterafle:
Read the thread you can only use this Kitchen on Linux (You can use VirtualBox) otherwise buy the paid version
[SuperR Kitchen] digaogt:
Is it possible to fix the hardware id using the donation version

Hi, SuperR. Thank you so much for this amazing project!!!

i was wondering if the Donation version of your kitchen would be able to fix the hardware id in About Phone.

I've installed a custom Rom to my Android box and the hwid is null now, I tried to modify it via build.prop, but it seems that, for some reason, it's bypassed by the system after it boots. After some research, I realized it is normal that it happens, but the apps depend on this to operate. Is there any way to fix it? Thanks once again and looking forward for your answer.
[SuperR Kitchen] CG_Tech:
doesn't find python location

In linux mint 20, it seems cant find python location to run.

Edit - i have to run this command

now its working fine
[SuperR Kitchen] vdbhb59:
Per the attached snapshot, whenever I select 1, it does nothing. This is when I am trying to extract any fw file. I tried all files for Samsung, and does not work at all. The selection does not do anything at all. All downloads were completed. Nothing is present in the logs folder too. This is the current free version. Linuxmint 20.0, latest Python version.
[SuperR Kitchen] SuperR.:
The kitchen can unpack your firmware and allow you to modify what you need. It will also pack a ROM zip for you. It will not automatically fix a hardware id. I am not familiar with hardware id. If the hardware id is located in build.prop, you could edit it after unpacking.

This will be fixed in the next update. You could also fix it by simply changing the first line of the superr file in the main kitchen directory. add a 3 after the python "python3", save the file, and now it will work.

The kitchen will not show that screen if there is a firmware file in your project it can unpack. Try the full firmware zip in your project directory instead of manually extracting certain parts. The kitchen will not recognize tar.md5 files in your project for example, but it will handle them if they are inside a Samsung firmware zip.
[SuperR Kitchen] tarunpramod:
These are the error log,how do I fix that??
[SuperR Kitchen] tarunpramod:
This is my error log kindly fix
[SuperR Kitchen] bigrammy:
Someone has been busy :eek:

Thanks. :highfive:
[SuperR Kitchen] pieboots:
Not sure if anyone is able to help me here, I will try this thread as well since this applies to the free version also.

I have been trying for two+ days now to figure out what my problem is here, even with no modifications I can not seem to flash the zip it creates.

I am using a Google Pixel 2 XL Taimen Variant.

Steps I am doing:

I download & flash a stock Oreo 8.1 image from the official Google page using Flash_All.bat -- Boots and runs fine, so no issues here.

I extract the "image-taimen-opm1.171019.021.zip" zip file from the official image I downloaded, put it into my Kitchen project folder.

Select extract rom on Kitchen.

Select yes to extract vendor image, yes to include. I have also tried the no option and attempted to manually flash it.

For perm type, I have tried both Metadata and Raw Image.

No modifications, straight to build full rom.

For "Choose partition size detection method for system" I select "system.img"

Using both of the last 2 TWRP versions, directly after clean stock image installs and boots.

Wipe Data/System/Cache also tried without Wipe Data/System/Cache

Every single time I get "Your device is corrupt. It can't be trusted." before the bootloader unlock message screen. And TWRP sometimes says "No OS Installed, are you sure you want to boot?", after flashing. Then my device stays stuck on the google logo with a lock or reboots itself into a bootloop. I am not making any modifications to narrow down the problem but noting is working even with not making modifications...

Troubleshooting Steps I Have Taken:

Tried 3 different computers for each step below. Two are Intel laptops, one is a Ryzen desktop.

Tried 3 different Pixel 2XL devices.

Tried OTG USB drive to flash rom

Tried ADB sideload to flash rom

Tried ADB push to /sdcard/ to flash rom

Tried 2x different USB C - USB C cords

Tried 2x deiffernt USB A - USB C cord

Tried building rom on Ubuntu

Tried building rom on Windows (Donate Version)

Tried flashing vendor image seperatly

Tried removing DM-Verity

Tried removing force encrypt

Tried using each perm type, raw_img etc.

Tried all zip compression methods. 0-9

Tried to flash system and vendor images via fastboot seperatly.

I feel like there is a lot more I have tried but can't remember it all.

If it helps, if I manually flash just the original unedited system.img/vendor.img after flashing the bad zip, and it boots just fine. So it has to be something in the system.img/vendor.img that is causing my troubles.

SuperR asked me to try extracting and including vendor, choose raw_img perm type, remove dm-verity from the boot/recovery menu all together, and then build the full ROM zip. But same error, "Your device is corrupt" error, bootloop.

Any other ideas on what I can try? I have spent close to 30 hours trying to figure this out and feel like I have tried everything.

Thank you for any help here.
[SuperR Kitchen] Chrishdev:
Installation Error

Hi, in parrot security os, after running

./superr

it downloaded some .zip files and just after that during installation it says :-

Traceback (most recent call last):

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

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

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

File "<string>", line 138, in appendf

PermissionError: [Errno 13] Permission denied: 'install.log'

[57917] Failed to execute script superr

please help...
[SuperR Kitchen] TheRealModder:
why the file_contexts got invalid

this logs got spammed so many times

the example :

/home/justine/Downloads/SuperRs-Kitchen_Linux-64_v1.2.1.2/superr_Pure_Sparse/00_project_files/file_contexts: Multiple same specifications for /sys/module/pm_8x60/modes/cpu1/standalone_power_collapse/idle_enabled.

this logs got spammed twice

/home/justine/Downloads/SuperRs-Kitchen_Linux-64_v1.2.1.2/superr_Pure_Sparse/00_project_files/file_contexts: Multiple different specifications for /sys/class/devfreq/exynos5-busfreq-mif/time_in_state/mif_time_in_state (u:object_r:sysfs_time_in_state:s0 and u:object_r:sf_time_in_state:s0).

this is the end of the log

/home/justine/Downloads/SuperRs-Kitchen_Linux-64_v1.2.1.2/superr_Pure_Sparse/00_project_files/file_contexts: Invalid argument

I'm on 1.2.1.2
[SuperR Kitchen] SuperR.:
I do not know why this is happening, but it is a permissions error stating you do not have permission to write the install.log. Try granting write permissions to the kitchen directory recursively and try running it again.

Not sure how or why, but if you send a link to the firmware I will take a look.
[SuperR Kitchen] :
I'm currently using SuperR to extract an Android 10 GSI so I can slightly modify it. I'm then trying to build just the system image as raw. This is the error I'm getting for some reason

This Rom is

ArrowOS-10-a64-ab-vanilla.img

error: build_directory_structure: cannot lookup security context for /firmware

Creating filesystem with parameters:

Size: 2254856192

Block size: 4096

Blocks per group: 32768

Inodes per group: 8096

Inode size: 256

Journal blocks: 8601

Label: system

Blocks: 550502

Block groups: 17

Reserved block group size: 135

This is the info found in the context files of SuperR, which I assume is the issue?

system/firmware u:object_r:firmware_file:s0

system/firmware/radio u:object_r:firmware_file:s0

When I remove the firmware folder, the image will build but does not boot. Any idea what I could try to do to get it to build while retaining the firmware folder?

This Rom is

bliss-v221-200725-a64-bvN.img

error: build_directory_structure: cannot lookup security context for /dsp

Creating filesystem with parameters:

Size: 1717985280

Block size: 4096

Blocks per group: 32768

Inodes per group: 8080

Inode size: 256

Journal blocks: 6553

Label: system

Blocks: 419430

Block groups: 13

Reserved block group size: 103

So basically if you want to reproduce the error, I'd imagine download any arm-bvn rom, extract it with SuperR and then Build EXT4 Image option, select system, raw or sparse(same error for both)

Also, I notice that Android 10 GSI and SuperR have a weird relationship. Say my GSI image is 1.2gb. SuperR will extract it and the folder will then be 1.4gb, which means you have to look up the new size in bytes and manually input it. My suggestion would be to have an option to check the size of the folder as apposed to the system.img used, as it appears all Android 10 GSI extract with this behavior. This is a huge problem and issue for me and my current project since I am trying to add root to my GSI images. I hope you have time to take a look at it and hopefully point me in the right direction. I can't move forward with anything else at this point until I can get this figured out. FYI, Android 8 and 9 GSI images did not seem to suffer from this. Also I just checked, I am getting the same error when attempting to build a full rom as well.

More weird behavior. I extract Bliss. It complains about dsp folder when trying to build it. I look in the folder and there isn't even a dsp folder to begin with since intial extraction, so why is it complaining about a non-existent folder? So I then think I'm smart and add a dsp folder and try to build. Same error and now this time when I go to look in the folder, again dsp folder is not there. SuperR is not only throwing up an error, but then deleting the folder I added.
[SuperR Kitchen] hkdg009:
Hey guys, I got an error when packaging Android 11 version system raw_image. View log shows: error: build_directory_structure: cannot lookup security context for /cust

But I packaged the Android 10 version and there was no problem. Is the tool still not supported?
[SuperR Kitchen] chi1984:
Hi SuperR

May I ask your help to have a look on Nvidia Shield TV pro ROM?

It is Android9 userdebug build, already PM you with link, it can root & remount normally after unlock bootloader.

But my problem is: I can extract system.img normally, then edited a icon pic & build it as EXT4 img, I tried different type of system.img to create, but both of them can't boot up normally after flashed.

I also tried <fastboot --disable-verity --disable-verification flash system 'mybuild'.img>

& <fastboot --disable-verity --disable-verification flash bemeta vbmeta.img>, that doesn't work, only freeze on kernel boot logo.

Is there any way can let it boot up? Really appreciate it you can answer with your professional view, thanks a lot.
[SuperR Kitchen] danerrickcuba@gmail.com:
Is there a way to run this via Termux?
[SuperR Kitchen] HemanthJabalpuri:
I think, we can install some linux distributions with the help of some scripts and apps like Anlinux and then run it in that environment.
[SuperR Kitchen] elliwigy:
maybe andronix.. i run andronix frequently.. i use remote ssh tho for most lol
[SuperR Kitchen] danerrickcuba@gmail.com:
Thank you?.I'm aware of that, but was hopeful that this can simply be via command line in TERMUX, gui not necessary at all.

I'll look at the available distributions to use.
[SuperR Kitchen] :
Greetings SuperR.

I used free Linux version on Linux 18.04. I unpacked the firmware. Also vendor.img & cust.img & selected option yes for including them in ROM & used sparse_dat. Then i debloated using debloat_custom. Removed dm_verity. Build ROM-selected partition size (option 4) for system.img, vendor.img, cust.img. No error in flashing but it can't boot. [Device = raphael ---- Firmware used = https_//xiaomifirmwareupdater_com/miui/raphaelin/stable/V12.0.3.0.QFKINXM/][/url]

My guess is, because of the old version.

Will it work on v3.2.0.9(donate) if i follow the same steps ??? or am i missing something. ??

I am ready for donation by the way !!
[SuperR Kitchen] SuperR.:
The donate kitchen will not give you the security context error because it uses the contexts from the original img file you extract. The free kitchen looks for file_contexts files in the img files you extract and uses them. If you did not extract vendor with system, you could try that as vendor normally contains file_contexts files that system needs.

The kitchen extracts the files that are in the img files. If the extracted files are larger than the img, they must be compressed in the img. I believe this problem will be fixed with the eventual switch from make_ext4fs to e2fsdroid. You can also use the "Project Directory (BETA)" option when choosing partition size. I think this is what you are looking for.

No clue about the dsp directory issue, but the kitchen does not delete directories that are not empty. You could try to add an empty file to prevent deletion.

See the first part of the answer above.

It is possible the donate kitchen will work better for you as it uses the exact permissions, contexts, and capabilities from the original firmware you extract.

No clue

See my response above to chi1984
[SuperR Kitchen] ezzony:
[/COLOR]

I am out of the blue getting this error when extracting system.img. It worked fine for me many times with the same image and other images. What could cause this issue thanks.

edit: It does extract a lot of it I see but I don't know if it extracted it all.
[SuperR Kitchen] aidanmacgregor:
Hi SuperR. Thanks For The Tool!

I Seem To Have A Strange Issue, I'm Trying To Modify Vendor.img (RAW), when i make changes to system.img everything works when replacing system.partition in the ROM but when i edit the vendor.img and replace vendor.partition it breaks Wi-Fi (Tried Unpacking and repacking with no changes & the vendor_new.img when replaced still breaks Wi-Fi) Im Not Sure Why Repacking vendor with no changes breaks Wi-Fi

What Kitchen version?

-1.2.1.2

What environment are you running the kitchen in (OS, 32/64-bit, cygwin, Bash on Windows, etc.)?

-Linux Ubuntu 64 Bit (Clean Install https://releases.ubuntu.com/18.04/ubuntu-18.04.5-desktop-amd64.iso)

What device are you working on (make/model)?

-My Custom Android 9 Mi Box S905X Firmware Port

What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)

- http://aidansrom.freecluster.eu/android-9/ (Version: [v2] AP6212a & Maybe More)

What Android version?

-Android 9

What perm method (set_perm, set_metadata, sparse_dat, raw_img)?

-Raw IMG

What did you do after extracting and before building?

-Before extract - Removed System,Boot,Recovery & Vendor .partition files and renamed to .img

-After Extract - Edit system.img & Vendor .img (De Bloat Be Removing Chromecast, YT Ect... from Sys/App, & Vendor/app remove File Browser, Video Player)

-Build - Using Raw Img, Using Detect Size From Img (file Is Exact Same Size) Copy new IMG Files Into amlupdate.img Repack & Flash Using USB Burn Tool, (Boots But Wi-Fi Broken Bluetooth Still Works Even With No Edits To Vendor.img)

Were there errors on the screen if you scroll up in the terminal?

-No

Send a recovery.log after flashing if you have problems flashing the ROM.

-ROM Flashes & Boots Sucsessfully

Send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)

- https://mega.nz/folder/tsoUwRCY#A_Mbde5TvTd_HwloV4W1uA/file/x4o2QBhI (Unpack To Level1 Rename .partition to .img)

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

- https://drive.google.com/file/d/1TY4oSxSeAb27Qi0PVuBPSRW0Fuogmk7O/view?usp=sharing

Also My Wi-fi Is AP6212a (The A Variant Is Different From ap6212) Hopefully Gave You All The Right Information still learning a lot and as i go, Any Advice Would Be Greatly Appreciated