yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] SuperR.:
I extracted your firmware in the free kitchen and the updater-script is considerably different and much larger than the one in your support zip. Please try the one attached below. It was created using your firmware in the free kitchen.
[SuperR Kitchen] AL_IRAQI:
Hi again buddy, many stock based zips has fw update of some kind backed in, when we exact the zip, it doesn't get copied to project folder, having it in there would save an extra step, also having an option to rezip those fw files in a sperate zip or bake it in ROM zip would be great also, if you want i can link some stock ROMs worth fw in
[SuperR Kitchen] bcrichster:
The plugins in the donate version works with update zips
[SuperR Kitchen] Coayer:
Hello everyone,

Been struggling to get anything to boot.

I was originally making an 8.0 ROM for my S8, but couldn't get past the Samsung splash screen before the boot animation. Even using someone else's ROM.zip (which worked fine when directly flashed in TWRP) would not boot after being opened in the kitchen and then built into a full ROM zip without any modifications whatsoever. I've since tried the same for my LG G3, using LineageOS 15.1. The same thing happens, with the ROM not able to boot after being opened in the kitchen and immediately built into a zip despite it working perfectly before.

All of the dependencies are installed, and no errors occur in the kitchen or in TWRP when flashing.

Using latest version, with the recommended settings by the kitchen.

So far I've tried Solus Project and Ubuntu on different machines with the same result.

I've attached the support.zip.

Would really appreciate any help, I really want to make a ROM!

Thank you :)
[SuperR Kitchen] SuperR.:
There are no capabilities in your updater-script. I am not sure why, but this is likely the issue. Can you send a link to the firmware you extracted to get the updater-script included in the support.zip? I would like to see if I get capabilities when extracting the same.
[SuperR Kitchen] Coayer:
Hi,

Here is the firmware I tried for the G3:

https://xdaforums.com/lg-g3/development/rom-lineageos-15-0-alpha-t3689278
[SuperR Kitchen] SuperR.:
I get a very different updater-script when I extract this firmware. It is attached below. My guess is there is some dependency missing but I don't know what it is. You could try Ubuntu4Kitchen or Mint4Kitchen which have everything needed to run the kitchen. They are linked in my signature.
[SuperR Kitchen] Coayer:
Sure, I'll do it right now. I forgot to mention that when I looked around the storage using the TWRP file explorer nothing seemed to be in the /system folder so that would make sense.
[SuperR Kitchen] Coayer:
Just tried again with Mint4Kitchen on a liveUSB, the updater-script it made is only 545 lines whereas the one you sent is 978 :confused:

Edit: same with Ubuntu4Kitchen :(
[SuperR Kitchen] SuperR.:
I don't understand how this is possible. Here are the steps I took to get the updater-script I sent.

Download the firmware you linked to a new project directory

Run the kitchen selecting this project

Choose option #4 to extract

Choose the full firmware zip

choose set_metadata perm type.

That's it.
[SuperR Kitchen] bcrichster:
There has to be another variable somewhere
[SuperR Kitchen] SuperR.:
v1.1.9.5 (Free Bash version)

Changes:

Fixed openjdk 10 being detected as java 1.0 due to new version output without decimal or dash.

Fixed api not being detected during extraction when system/build.prop and system/vendor/build.prop exist causing the updater-script to use default permissions.

[MENTION=7508322]Coayer[/MENTION] - This should sort out your issues :)
[MENTION=9113250]archie9211[/MENTION] - Let me know if this fixes the Java 10 issue.
[SuperR Kitchen] Coayer:
Works perfectly now, thank you so much! :laugh:
[SuperR Kitchen] gaganbajwa:
Hey superr

When i deodex amy rom with superr in deodex stopped in service.jar and hang full pc why plz help me

I m use this in ubuntu 18.04
[SuperR Kitchen] bcrichster:
∆ This right here may be your reason ∆

- It is extremely new and untested, bugs galore.. Backpedal an OS or 2 and your problems will likely go away. Keep using your new distro and you can basically EXPECT oddball problems for awhile.. No hate involved, just the way it happens. My personal opinion due to my own trial & error: Give every new distro about a year to work most the bugs for reliability in building cuz sometimes they change names of needed pkgs and you can have a monster of a time figuring out the changes..
[SuperR Kitchen] softwaresmaker22:
I'm having issues creating updater-script with this kitchen again, Could you try to do it again with donate version?

drive.google.com/file/d/13yj-pzLoSTktw3EFbuYreUXU4lHlcEUi/view?usp=sharing

Device: Galaxy S9+ G965F

Android 8.0

Stock ROM download^^

The problem is it seems like the updater-script file it's very small and some of it is missing. I'm using Ubuntu4Kitchen.

If you could try to build me a updater-script I would be very grateful, And possibly donate and get Donatekitchen.
[SuperR Kitchen] bcrichster:
To be honest, the Donate kitchen has like 20 things/capabilities/ & plugins that the free Kitchen does not, plus better Oreo support. His donate kitchen is constantly updated and improved. I'd recommend getting that one, try your project, and THEN say something if it doesn't work..
[SuperR Kitchen] softwaresmaker22:
That is why I am requesting him to try it for me in the donate kitchen and give me that file to try it out myself and if it works I will get donate kitchen :D
[SuperR Kitchen] SuperR.:
The updater-script is attached below :)

Keep in mind that there are many other things that can make a ROM not work besides the updater-script.
[SuperR Kitchen] softwaresmaker22:
You are so helpful, Yes I know that. We will see if this works :D
[SuperR Kitchen] davy4475:
Hi, I'm having trouble installing the kitchen on linux. When I come to the last step ./superr I keep getting /usr/bin/env: 'python': no such file or directory. I'm trying to install the free version. Thanks
[SuperR Kitchen] googlebleh:
Looks like you need to install Python 2. On Ubuntu, this can be done by opening a Terminal and typing the command:

sudo apt-get install -y python
[SuperR Kitchen] khb8255@gmail.com:
hi~!

Is Android 8.1 available?
[SuperR Kitchen] SuperR.:
I need some help compiling a binary for Mac...

the CONTEST:

Be the first to deliver a functional Mac bootimg binary using source code 1 or source code 2

The binary must be verified working (by me) before registration is approved.

You must provide any source code changes you made to get it compiled.

Hopefully it can work on Yosemite+ (this way I can test it)

Be willing to consider help with compiling binaries on Mac in the future (Optional but would be greatly appreciated)

the BOUNTY:

One free Donate Kitchen registration :)

Good Luck :)

EDIT:

THE CONTEST IS NOW OVER.

Congratulations [MENTION=5617466]Andmoreagain[/MENTION] :)
[SuperR Kitchen] AL_IRAQI:
Hi Everyone, did anyone of you came across system.new.dat.br

i know it was added before, but it didnt extract it XD

Edit:

i double checked, it did extract it when i run it again :p
[SuperR Kitchen] joshuab227:
[MENTION=5787964]SuperR.[/MENTION] Thank you for creating and maintaining this awesome kitchen.

I am facing an issue while modifying the system image of Lava Z50 (which is an Android GO device running Android 8.1)

I have extracted and modified the system image successfully and it is flashed properly as well on the device using the Mediatek flashing tool.

However on booting up , the device will not proceed past the Google Setup Wizard.

It does not give me an option to skip Wifi configuration , and when I connect to a Wifi Network , it gets stuck at the "Checking for updates" screen.

I have tried to disable / skip the Wifi configuration of Google Setup Wizard using various build prop modifications but that did not help.

Also removing the Setup Wizard apk from the system image and using another app for provisioning lets me proceed to the launcher but the Google apps do not function properly and force close (Maybe due to improper initialisation due to lack of Google Setup Wizard)

I have done similar modifications using your kitchen on many devices but have never faced this problem.

Could you let me know if you have any insight into what may be causing this and how I could fix it ?

Thanks again.
[SuperR Kitchen] SuperR.:
This is most likely due to file permissions and capabilities. The free kitchen creates system.img with default AOSP permissions and capabilities. If your device requires different ones you will have issues. The donate kitchen creates system.img with the same permissions and capabilities from the original system.img you extracted.

Try a set_metadata ROM. It is the best option in the free kitchen for getting permissions and capabilities properly set.
[SuperR Kitchen] joshuab227:
Hi [MENTION=5787964]SuperR.[/MENTION]

I tried building the system.img with set_metadata option but faced the same problem.

Was planning to get the donation version anyways to support your work so will try it with that soon.
[SuperR Kitchen] bcrichster:
That's the best idea, really.. The Donate version is SuprR supreme
[SuperR Kitchen] khb8255@gmail.com:
miui 9 oreo 8.1 deodex ....bootloop....
[SuperR Kitchen] bcrichster:
I think the donate version has a special patch for that..
[SuperR Kitchen] khb8255@gmail.com:
Donation done ... Approved! please...
[SuperR Kitchen] aleksgrayvoron:
SuperR Kitchen

Hello. Thank you for the useful program.:good: Faced with difficulty. I unpack the firmware for the fastboot.

Pre-repackaging the firmware folder in zip.

The program gave an error:

https://yadi.sk/i/kC40zlnI3YFThD

Operating system-Linux Mint

SuperR Kitchen is the freshest.

Tell me what to do.:confused:

Screenshots of the composition of the folder Firmware:

https://yadi.sk/i/lpD5sUlv3YFTxV

https://yadi.sk/i/1UKO8zsc3YFU7u
[SuperR Kitchen] SuperR.:
I moved your post to the correct thread as this is not a Mint4Kitchen question. Please send a fast link to your firmware that does not require registration and I will take a look.
[SuperR Kitchen] Suvorik1969me:
Here a link for download what you were asking for from aleksgrayvoron.

He asked me to do it because he has not enough posts in his active to do it himself.

http://www.mediafire.com/file/9tch2z9qpsgbnnw/Vivo_X9_PD1616_D_1.23.14_China_6.0.1.zip
[SuperR Kitchen] celoxocis:
is it possible with SuperR kitchen to merge an OTA package to a base image?

let's say im working on a device. which i physically don't have but im interested on the devices latest binary blobs.

therefore i would take the base image and apply the OTA package on top.

it's pretty straight forward when you own the device. just apply the OTA and dump images with DD or TWRP.

but is it possible with the kitchen or any other tool?
[SuperR Kitchen] SuperR.:
The kitchen does not currently support this type of firmware. That is why you got the message that the kitchen could not find anything to extract in your zip.

This firmware is tricky. It comes in 23 parts (system_1.zip etc.). I concatenated all the parts into a system.img, but the geometry was off and did not mount. I truncated the system.img to the correct size and now it is mounting without issue. Here is a link to the new system.img. Extract it to your project directory along with the boot.img from your firmware. Then use the kitchen to extract the new system.img :)

The kitchen does not do this. I have not heard of a tool that does, but I don't get out much :)
[SuperR Kitchen] KaMyKaSii:
https://github.com/erfanoabdi/imgpatchtools

No? I was pretty sure that you had previously posted the link to this project
[SuperR Kitchen] SuperR.:
I probably did and have forgotten. Getting old :p Thanks for posting it now. It seems to be exactly what [MENTION=2494638]celoxocis[/MENTION] is looking for :)
[SuperR Kitchen] celoxocis:
thanks for this guys! exactly what i was looking for.

i was just about to start and merge the system image but it seems a simple binary merge isn't the way to go.

my system image is split like this (see attachment)

i've tried a simple binary merge as the kitchen didn't know how to process this split system image.

what's the proper way to merge this split system image?

i can upload a zip to my cloud drive if required.
[SuperR Kitchen] SuperR.:
This is the 3rd time this type of firmware has popped up, so I have written a binary to deal with it.

concatimg_4_linux64.zip

Usage:

Extract all system_*.img files into a new directory.

Extract the concatimg binary into the same directory

open a terminal to the same directory

To concatenate and fix the ext4 img:

./concatimg -cf system

To only concatenate and not fix the ext4 img:

./concatimg -c system

To only fix an existing system.img for mount/extract without concatenating:

./concatimg -f system

This will create a working system.img from your files. Enjoy :)

If you want to use the rawprogram0.xml file from your firmware to detect the starting sectors, just add it to the directory with all the system_*.img files. In my testing, this was not needed but the option is there.
[SuperR Kitchen] celoxocis:
Thanks for the great effort!

Here is some feedback. I've tested concatimg and it does work.

However as i tried to apply the first OTA patch it failed with the cause of the wrong checksum at the base system.img

I came across this tool which works with the split system image files and it seem's to output the proper checksum which the OTA expected.

Just an idea. Maybe you want to run a diff on both merged system images and see why the checksum differs?
[SuperR Kitchen] SuperR.:
I tested the tool you linked, and it does not produce a valid ext4 img. Try mounting it in Linux or extracting in the kitchen for testing.

I agree the checksum will not match the original when generated by concatimg, but it will mount and extract which is what I am interested in for kitchen use. Either way, I am glad you found what you needed :)

Here is a new version with -f to fix the img for mounting and/or extracting (if it is broken). With this flag, the img file will work in the kitchen. Without this flag the checksum will match but it will not work in the kitchen.

DOWNLOAD LINK 2 POSTS UP :)

I noticed in the other project the rawprogram0.xml is used for retrieving the starting sector of each img part. I have added this capability, although it does not seem to matter as the checksum is identical with or without it. If you want concatimg to use the rawprogram0.xml file just add it to the directory with all the system_*.img files.

Additionally, I have added the option to fix an existing system.img for mount/extract without concatenating. This way you can create the system.img so the checksum matches, and later fix it for mounting. Usage updated 2 posts above.

EDIT: Removed links, and updated the original post 2 above this one found here

EDIT2: Another new version with -f (fix) flag instead of asking a question and stopping for a response. Original post edited again.
[SuperR Kitchen] jhenrique09:
Would be good if the size of system and vendor partition get saved when entered manualy, it's annoying to type the size every time when generating a block based zip file.
[SuperR Kitchen] bcrichster:
I think the Donate version may..
[SuperR Kitchen] SuperR.:
I think both versions used to do this, and I think I removed it (old and forgetful). If you change the firmware in a project directory and keep the 00_project_files directory for example, then build a block based zip... you will have problems. I guess we could save it in the device directory, but what if you enter the wrong number by accident? Seems like I would be asking for a bunch of posts from unhappy people. I will think about it more.

In the meantime, did you know you can paste in the terminal with ctrl+shift+v ? I also recommend option #4 to get the size from the system.img if available.
[SuperR Kitchen] OutS:
Hi! Can I deodex android 8.1 in free version??
[SuperR Kitchen] inspired55:
": mount: failed to mount /dev/block/platform/155a0000.ufs/by-name/userdata at /data: device or resource busy " I'm getting this error and rom will not boot. Hangs on splash screen.What does this mean and how does one fix it.
[SuperR Kitchen] omeh2003:
Something went wrong building the image.

Hi. Faced such problem when using the utility. I can unpack and package system.img But I can't make any changes inside. While trying to pack up this bug

"

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 the Main Menu"

Please. Help me.

P.S. Repack Android 8.1
[SuperR Kitchen] exilada:
i got this error how can i run it compabilty with pacman?
[SuperR Kitchen] AL_IRAQI:
Hi there, latest Huawei/Honor devices has a/b prefix without having an actual a/b layout, which causes problems while trying to make a flashable ROM with the kitchen, can you please do something about it ? Or maybe let's us choose device layout before making the

Thanks
[SuperR Kitchen] ashyx:
Think about it, it's pretty obvious.

The system partition is a set size. Some are only JUST big enough to fit the stock rom.

If you make changes that increase the size of the rom bigger than the actual partition then its going to fail.
[SuperR Kitchen] SuperR.:
yes

send a recovery.log

install lzop and cpio

I am happy to do something about it. What is the kitchen ROM zip using as your system path? What should be used instead? How can the correct path be determined from the shell?

Offering a choice does not seem like a great option, as many users will choose the wrong one and complain about it.
[SuperR Kitchen] inspired55:
": mount: failed to mount /dev/block/platform/155a0000.ufs/by-name/userdata at /data: device or resource busy " I'm getting this error and rom will not boot. Hangs on splash screen.What does this mean and how does one fix it.. I've tried several builds all with the same results. attached is the recovey log.
[SuperR Kitchen] SuperR.:
Please try replacing kitchen/superr_project/install/bin/configure.sh with the one in the attached zip. Build your ROM again and let me know how it goes.
[SuperR Kitchen] inspired55:
replaced configure.sh as advised sorry but i'm having the same results as before see attached log
[SuperR Kitchen] bcrichster:
Did you reboot PC after file change?
[SuperR Kitchen] celoxocis:
[MENTION=5787964]SuperR.[/MENTION] a big thanks to you! i found myself using the concatimg lately quite often.

especially when there is no rawprogram0.xml around to merge and fix the system.img's.

i do have a question which is unrelated to the system.img but more to the boot.img.

what i usually do is. i use the qfil_unsparse tool or your concatimg on qfil packages. (when lucky) and apply available ota's on to those and then use your _amazing_ kitchen to extract those and hunt for blobs that were updated or relevant in another's phones project. like taking one phones camera blobs and make it work on another phone, etc.

so far patching boot.img and system.img with ota patches has worked fine.

but i found myself with a perfectly fine, working and mountable/extractable boot.img when used in your kitchen.

but when i apply i try to apply an ota patch on top of it the crc's is wrong. (sha1sum taken from updater-script)

i noticed the available boot.img coming from an qfil package is 1408 bytes shorter then what the ota patcher expects.

would you by any chance know where the difference in those 1408 bytes are coming from? has it something to do with the sparse size? is it simply padded to a specific sector boundary?

the boot.img is also perfectly flashable via fastboot and works without issues.

I've uploaded the zip file to my mega drive here.

it contains the boot.img which is 1408 bytes to short

the updater-script file which contains the proper size information, such as sha1sum's and the patch file (just in case)
[SuperR Kitchen] SuperR.:
I am glad concatimg is working for you :)

If you are unpacking/repacking the boot.img in the kitchen, then AIK (Android Image Kitchen) probably changes the size of the resulting boot.img and absolutely changes the crc.

In either case, you could try truncating the boot.img to the correct size:

truncate -s 23944458 boot.img

Beyond this, I have no idea. Good luck :)

EDIT: This seems to work

$ sha1sum boot_S251.img
22fdd91a97f177150c6b3e298960939d1871d5ed boot_S251.img
$ truncate -s 23944458 boot_S251.img
$ sha1sum boot_S251.img
df68d47825f5c4745b3640c13c03934e61a687b9 boot_S251.img

From the updater-script:

23944458:df68d47825f5c4745b3640c13c03934e61a687b9
[SuperR Kitchen] celoxocis:
thanks! *bowsbeforethemaster* :good:
[SuperR Kitchen] xiaowei666:
I tried to unpack the system.img in the millet 6-line brush package with the super kitchen superr and added some apps to the priv app. But when I packaged it back and flashed successfully, the phone card was in the mi sign. The card is on the first screen of the boot. And after trying the system.new.dat in the rom zip, it is also stuck in the first screen. Can anyone help me thank you.

The system version of Xiaomi 6 is 8.0.0
[SuperR Kitchen] DoR3M3:
[MENTION=5787964]SuperR.[/MENTION] looking at the readme it doesn't look like the Linux version will Deodex Oreo 8.1.0?

Anyone know about this?

Thanks
[SuperR Kitchen] Mixterix Se7en:
Zipalinging no work in lubuntu
[SuperR Kitchen] bcrichster:
Might be missing dependencies..??
[SuperR Kitchen] DoR3M3:
Any support for Oreo 8.1.0 to Deodex coming?

Thanks
[SuperR Kitchen] SuperR.:
Error message? support.zip? Firmware link?

I think it already works on 8.1 but I have not tested in a while. Have you?
[SuperR Kitchen] AL_IRAQI:
Deodexing & Zipalinging 8.0/8.1 works fine, tested by me like a week ago, on two different bases EMUI & TW
[SuperR Kitchen] DoR3M3:
[MENTION=4648515]AL_IRAQI[/MENTION] hmm ok thanks, I can't figure out how to do this, any docs explaining this?

I was doing this in the wee hours of the morning, either sleepy, or blind, LOL, but I can't seem to find any docs on how to go about this, is there something that can show me what steps to take to Deodexing?

Thanks
[SuperR Kitchen] Mixterix Se7en:
when I opened the superr and unzipped a nougat ROM it did not work the zipaling

but the ROM is compressed and I tried the zip, no problem so far

Sorry muy bad english
[SuperR Kitchen] DoR3M3:
[MENTION=5787964]SuperR.[/MENTION] I have some PATH issues here.

I'm running the latest version from Git on Linux x64

Working on Essential PH-1

Working with system.img vendor.img boot.img

perm method raw_img

When I first ran superr as it was installing the binaries, it came back telling me there was no 7z...

tools/source/superr: line 4545: /home/foo/Build/superrs-kitchen/tools/linux_tools/7z: No such file or directory

When I tried to Build full ROM Zip with either y/n using zipalign I'm also getting this in the zip.log;

tools/source/superr: line 2343: /home/foo/Build/superrs-kitchen/tools/linux_tools/aapt: No such file or directory

tools/source/superr: line 2741: /home/foo/Build/superrs-kitchen/tools/linux_tools/aapt: No such file or directory

Do we need to set up some sort of work ENV PATH for this to work? I didn't read anything on this...

There seems to be some PATH issues going on here...

I reset the tools and it installed the binaries over, but it didn't help, still all the same...

hmm