yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] Xennet:
[MENTION=5787964]SuperR.[/MENTION] Or anyone else who can help...

Can I use update binary file from the original stock os installer file and replace the one in the ROM zip cooked by the kitchen to get around the error unknown command till you fix the issue??? Somewhere in Google I found that if you cook a ROM via android kitchen (not your specific kitchen) it would be better to replace the update-binary by the device specific update-binary file.

Is it true? If so is the device specific update-binary file the one present in the full stock ROM zip?

One error that occured was when I tried to add the firmware files to the zip cooked in superrs kitchen. Twrp couldn't identify the command

msm.boot_update

So I just deleted the line and it flashed correctly

Is it due to the fact that the update binary that the kitchen produced doesn't contain the command

And will it be rectified if I use the update-binary from the stock os rom?

Stock Update binary file from the stock os rom zip attached of you need a look at it

Thanks in advance

Doing, getting errors and rectifying makes us more wise right?
[SuperR Kitchen] monleylord:
Any hint how to go back to an older donation Version?
[SuperR Kitchen] SuperR.:
It can't hurt to try using the stock update-binary. I am not working on fixing the one we have since it is not broken. The previous update-binary did not show an error, but it would not allow flashing zips over 2GB. [MENTION=1162986]Captain_Throwback[/MENTION] was kind enough to build us a binary that allows large files. If you want to build an update-binary that allows large files and does not show errors, you should :)

Use the following link, but replace the last 8 characters (after the =) with the commit ID you want to download.

https://gitlab.com/superr/superrs-kitchen2/repository/archive.zip?ref=c180987d

Keep in mind the updater will not work when downloading zips directly.
[SuperR Kitchen] Xennet:
I used the stock update binary.

No errors at all

Flashed smooth

But don't know whether it allows flashing of zips more than 2gb. My modded zip is only 1.1gb...
[SuperR Kitchen] Captain_Throwback:
[MENTION=5787964]SuperR.[/MENTION]

I just updated my WSL to Ubuntu 16.04, and successfully built TWRP in the 6.0 and 7.1 trees. So, I figured I'd give the Kitchen a try to see if things were working better. However, I'm getting a 7z dependency error. I saw you had fixed this a while back, but it seems to be back with the new version of Ubuntu in WSL.

------------------------------------------------------
SuperR's Kitchen
by SuperR
------------------------------------------------------

MISSING DEPENDENCY:
The following dependencies are missing:

7z

Would you like to install now? y/n

And saying y just brings me back to the same screen.

EDIT: There were actually a couple of other dependency errors as well, but manually installing those packages got rid of them. I think they were bc and adb. I installed p7zip to see if that would take care of the dependency, but apparently not :/.

EDIT 2: WSL apparently doesn't support running 32-bit binaries, so that's probably part (if not all) of the problem. Any way to only use 64-bit binaries on 64-bit systems?
[SuperR Kitchen] jesus183095:
Yes but the problem is thid remember? At time when i flash the rom the recovery says this

I create the zip but to flash when i choose install zip. the twrp recovery says:

installing '/externalsd/prueba.zip

checking md5 file...

skipping md5 check

this package is for "fortunave3g" devices;this is a samsung sm-g530h

E:Error executing updater binary in zip '/external_sd/prueba.zip

Error flashing zip '/external_sd/prueba.zip'

updating partition details.....

done

you can help me? ￼
[SuperR Kitchen] SuperR.:
Do what I said above, and add EXACTLY what it says your device is in the error when flashing. The problem is that your recovery reports your device as one thing, and your assert reports it as another. I have made it extremely easy to change it as I have explained. This is all the help I can offer. If you still don't understand, maybe someone else can help further :)
[SuperR Kitchen] jesus183095:
Ok thnx for your help and your time..
[SuperR Kitchen] Er. Aditya:
how about removing these top 3 lines and then try ??
[SuperR Kitchen] jesus183095:
I believe i erase this 3 lines the cell phone entry in blootop
[SuperR Kitchen] Er. Aditya:
i am using updater script without these device verification lines and works flawless for me
[SuperR Kitchen] jesus183095:
erase The first lines in the updater script?
[SuperR Kitchen] Er. Aditya:
send me your updater script
[SuperR Kitchen] SuperR.:
v0.9.2.8

Changes:

Fixed kitchen updater.

Added a check to be sure 00_project_files/logs exists, otherwise errors will occur in many places.

PLEASE READ CAREFULLY:

I broke the kitchen updater in the last version. If you are using v0.9.2.7 you will need to do one of the following.

For git cloners:

do a manual git pull this time

For people that downloaded the zip and extracted it:

replace this file

/kitchen/tools/scripts/kitchen_update

with the file in the zip attached here. Once the file is replaced, use the kitchen updater as you normally do.

Sorry for the inconvenience.
[SuperR Kitchen] jesus183095:
Is this https://mega.nz/#!MdkxCAzA!Rk00Q6GlayBF33PT7TjxKB3Ur_-186AFO6gdFhVoLu4
[SuperR Kitchen] SuperR.:
1) The kitchen provides a very easy fix for this, so problem solved ;)

2) It is dangerous to build roms without asserts because the rom will flash on any device, not only the one it was intended for. If you are building this rom only for yourself, no problem. If you are going to make it available for download, it really should have asserts.

3) Could you have the rest of this conversation through PM instead since it is not kitchen related?

Thank you both for your understanding :)
[SuperR Kitchen] Er. Aditya:
great .... will be concentrating on improvements day by day ...thanks man ;)
[SuperR Kitchen] SuperR.:
Should it be extracted and copied to the system directory? Should it remain in the vendor directory and be flashed with the rom? If so, which partition does it get flashed to?

I am not sure what the ideal solution for vendor.img would be. Let me know your thoughts :)
[SuperR Kitchen] jesus183095:
ok i understand my device says SM-G530H. I have to put in capital letters or lowercase? and write for example SM-G530H or G530H only. and the script is this SM_G530H or SM-G530H?

Very thnx for your time
[SuperR Kitchen] SuperR.:
If the flashing error says your device is exactly "SM-G530H", then type exactly "SM-G530H".
[SuperR Kitchen] jesus183095:
Thnx for your help men.. you're very humble.. really very thnx for your helpful and comprension.. :D
[SuperR Kitchen] Q9Nap:
On the 5x, vendor is its own partition and image, so vendor.img should be extracted to the vendor directory and flashed along with system and boot.

It also contains symlinks that need to be added to the updater-script.

As an ext4 image, it is possible for it to be converted to sdat format also.

However, in my experiments with M builds, converting the stock Nexus 6 MRA58K system image to sdat format doesn't work (boots to blank screen iirc).

Interestingly, the only way I've been able to get sdat format to work on 6.0 is by using a dd system image and running rimg2sdat on it directly (without mounting, making changes, and remaking).
[SuperR Kitchen] SuperR.:
Thanks for the info. Will work on that next :)

I have no idea how to convert vendor.img into sdat or if it is possible.

I wish I knew more about sdat. If someone figures out why it is not working I will gladly include the fixes :)
[SuperR Kitchen] Q9Nap:
You convert it the same way as system.img...

Convert to raw format with simg2img

Mount raw image and make any desired changes

Make new ext4 image with make_ext4fs

Convert to sdat with rimg2sdat

Create 0 byte file x.patch.dat

It has something to do with both the data structure of the system.new.dat and the instructions in system.transfer.list.

These .dat and .list files are very different depending on methods used to create the ext4 system image prior to converting.

Sorry, that's the sum of my knowledge on the matter lol.
[SuperR Kitchen] jesus183095:
Hi [MENTION=5787964]SuperR.[/MENTION] I achieved to create a custom rom for my device but the wifi not turn on i try to turn on but automatically is turned off.. you know to fix or resolve this problem.?
[SuperR Kitchen] SuperR.:
Jump on IRC, too much to say lol :)
[SuperR Kitchen] Xennet:
[MENTION=5787964]SuperR.[/MENTION]

The last rom on one plus 2 cooked well. Extracted stock oxygen os with perm data, debloated, repacked with partition detection method as system.IMG and flashed

Everything was fine booted and worked fine.

But the same method I used for OnePlus 3t, cooked and booted. Everything was fine. Booted well. The welcome screen came. Selected the SIM for calls and sms. And then the next screen tells 'just a second" and immediately the screen goes black and reverts to welcome screen again. Whatever I do I cant pass the screen after "just a second" it reverts back to welcome screen again.

Then I tried building rom with metadata. But still the screen cant get passed the just a second screen.

Any suggestions what you do??
[SuperR Kitchen] SuperR.:
You should probably avoid set_perm on everything above Android 4.3. set_metadata is the most stable choice right now for Android 4.4 and above. If you are not starting from a system.img, I strongly recommend doing so. When extracting a system.img, the kitchen grabs all the metadata from the actual file system rather than guessing.

That's all I have for now, hope it helps. If you figure out what the problem is and can tell me how to fix it in the kitchen, I would be happy to do so.
[SuperR Kitchen] Xennet:
Just a doubt

Is it while extracting the system.new.dat that I should use metadata and while packing also other than set_perm?

The same problem occured for a user named [MENTION=6324159]tywinlannister7[/MENTION] and you were discussing with him on page 565. He used stock fastboot firmware and set metadata. Can you explain the procedure so that I can test?
[SuperR Kitchen] SuperR.:
If you are extracting a rom with system.new.dat, then you are already starting from a system.img. Just extract it normally, and when it asks you to choose perm type choose set_metadata. If you already extracted it, you can change perm type to set_metadata since the metadata was already collected when you extracted the system.img. If this method does not work for you, you can try sparse_dat or raw_img. If those don't work, I am out of suggestions other than it is always good to try without any modification first.
[SuperR Kitchen] Xennet:
I extracted with sparse dat then changed perm type to metadata and rebuild and still same error.

How can I rebuild using raw Image and do you have any idea about using stock firmware and setting metadata that the other user used?
[SuperR Kitchen] bigrammy:
No offence mate but.

Look at the menu options to use raw image.

Also use adb logcat to give you some clues as to why the ROM was crashing.

You should not constantly ask SuperR about such trivial things bro unless your 100% sure it's something in his code :rolleyes:
[SuperR Kitchen] 曦颜XY:
My dear SuperR，I saw you updated before the last language file was removed from the kitchen update and i updated today.

This time I uploaded to github, you can easily move to your library.

LINK: htt "deleteme" ps://github.com/Waitlan/ "deleteme" SuperR-Kitchen-Language-File, "deleteme" means that you should delete it so that you can download it.
[SuperR Kitchen] janjan:
SuperR​ we really appreciate your effort and your time for making this kitchen better and better. Is it possible to add a feature of making/built custom recovery TWRP in future?
[SuperR Kitchen] bcrichster:
Probably Not, that's a Source compiling job
[SuperR Kitchen] ShinySide:
Why not just build it properly by following Troy's very informative post about building/porting twrp? Lol

https://xdaforums.com/showthread.php?t=1943625

Trying to do it automated in a kitchen would be a disaster of bricked phones (no offense Superr lol) most likely since no one ever reads.

Follow that post, do it the right way and actually learn something lol
[SuperR Kitchen] Sh0X31:
[MENTION=5787964]SuperR.[/MENTION] can you add Magisk for alternativ rooting method?
[SuperR Kitchen] SuperR.:
There is a Magisk plugin for the donate version :)
[SuperR Kitchen] zengfu94:
All you would have to do is add in root using whatever option available and replace that zip with the magisk one and name it the exact same thing if you don't know how to edify.
[SuperR Kitchen] anoop.skumar:
Hi super

I am using bbqlinux whenever I try use option in kitchen to pull system from phone it shows "most likely you don't have permission or space left" when I run kitchen as root it shows "kitchen should not​ be run as root" . My sdcard is almost 3gb free so space is not the issue.

P.s: normaly I cannot start adb server without root in bbq
[SuperR Kitchen] SH1M4BD3:
i'm experiencing issues, 1000% registered as donate user but cannot get access how???
[SuperR Kitchen] SuperR.:
I test on 64-bit Ubuntu 16.04 only. If you figure out the issue, let me know and I will try to accommodate.

This happens occasionally and I have no idea why. I deleted and re-added you. This normally solves the problem :)
[SuperR Kitchen] SH1M4BD3:
Thanks its working fine now thanks sir

---------- Post added at 09:14 AM ---------- Previous post was at 09:03 AM ----------

Gapps plug-in seems need to be updated its just support 6.0??
[SuperR Kitchen] anoop.skumar:
Is there any way to run kitchen as root?, I think it might solve the issue with adb
[SuperR Kitchen] SuperR.:
Glad the longin is sorted out :)

gapps plugin has been updated for all versions past 6.0. Download and install again :)

It is not safe to run the kitchen (or any other script for that matter) as root and adb does not need root to run. However, your device must be rooted to pull system.img using adb.

Again, if you figure out the issue I will try to accommodate.
[SuperR Kitchen] theimpulson:
Could you give some instructions on how to port a Android N ROM? I having bootloops while following guides on XDA. Also kindly advice me for porting O. My device is Asus Zenfone 2 Laser. It is a famous device and is having many offical ROMs and Recovery.
[SuperR Kitchen] dilnix:
Hi SuperR,

i have a trouble with my x600 using the latest kitchen version.

when build process is finished (set_metadata type) the ROM installs normally but not starts as expected... hangs on LOGO.

i tried to find out why is this so and found that contexts of the files that is wrote to generated

updater-script

is wrong...

almost all contexts are set as "system_u:object_r:unlabeled_t:s0":

View attachment 4125888

but in the

file_contexts2

from ROM project folder there is another contexts written:

View attachment 4125889

and in the same version ROM build by another developer with another kitchen there is similar contents:

View attachment 4125890

i will waste my day and manually find a correct values for my ROM version,

but PLEASE FIX this trouble to me just use your kitchen fully and not be forced to make manual editions.

Thanks.
[SuperR Kitchen] dkionline:
[MENTION=7655945]dilnix[/MENTION] Thats the normal process, nothing wrong. It can be another cause by false packing or false deodexing. Or simple wait a little longer on boot.
[SuperR Kitchen] dilnix:
Sorry, but my stock ROM that i using as a source is fully deodexed by developer and nothing is needed to deodex more.

Also a packing process what you meen? All modifications i do for my version is: custom deBloat, adding SuperSU, BusyBox, su.d suuport and just coping into /system folder few of Gapps APKs... Nothing more. So i don't understand what is "packing" process is going... Zipping all without signature within newly generated updater-script is finishing always good and installation process always goes good without any errors.

Trouble is not in files of zipped ROM.

I figured out what exact is the source of problem and wrote about it. So please, let SuperR to see it and find a bug to fix it and don't waste our time with advises "to wait more". Because i fully remember how i made similar simple modifications (mentioned above) to older releases at summer and autumn of 2016 and the finished ROMs without any manual editions had a correct contexts for system files inside a updater-script.

Now this is incorrect. Developer, please fix this.
[SuperR Kitchen] zoko:
Donate method 2:10USD

GitLab user zoko
[SuperR Kitchen] mauronofrio:
[MENTION=5787964]SuperR.[/MENTION] i'm having some problems when i try to extract rom; the tool extract only the boot.img and nothing else. The rom have only a system folder and not a system image
[SuperR Kitchen] SuperR.:
v2.1.6.0 (Donate version)

Changes:

Remove all dm-verity flags from fstab instead of only /system.

Small change to allow running in OSX.

Updated Busybox installer by [MENTION=4544860]osm0sis[/MENTION].

Get file context from file_contexts if ls -Z produces "unlabeled" output.

v1.1.5.0 (Standard version)

Changes:

Remove all dm-verity flags from fstab instead of only /system.

Small change to allow running in OSX.

Updated Busybox installer by [MENTION=4544860]osm0sis[/MENTION].

Get file context from file_contexts if ls -Z produces "unlabeled" output.

Wrong thread. The kitchen dose not port ROMs

This is not a bug. It is a new feature and it should be working now. The problem is that your Linux does not have selinux support so you are not able to read selinux contexts. I have now added a fallback for this situation but I can't test it since my system does have selinux support. Let me know how it goes :)

Added, thanks :)

Send a fast link to your firmware that does not require registration and I will have a look
[SuperR Kitchen] mauronofrio:
this is the link rom: https://mega.nz/#!1kJFkQqa!KOHiL9P5IoI150Iv1Eur3QcsF114w92D9BirUAhm1dQ

There is no a system image but there is a system folder
[SuperR Kitchen] dilnix:
Very big thanks for your fast answer.

I'm sure 100% that my Fedora Linux have selinux support, furthermore i'm using it on laptop not in permissive but in forced mode and sometimese making manual changes in cofigs for modules of SELinux. May be there is needed some research to add support???

But anyway, thank you for a fallback function. I will try and bit later write you here about results.
[SuperR Kitchen] dilnix:
So results.

[MENTION=5787964]SuperR.[/MENTION] thank you one more time. A fallback that you added is working good. My new try of unpacking stock ROM and building my version was good. NO unlabled context was used more. All system files in "file_contexts" and in generated "updater-script" was labeled good. And my ROM version booted properly. Good job! Nice to have a deal with you =)

Another little thing i found in generated "updater-script"...

It's not a trouble, just simply not nice =) If you will have time to make order, please make:

View attachment 4127937

View attachment 4127938
[SuperR Kitchen] ShinySide:
n920g/7.0/arch

Havent used the kit in probably 2-3 months so dont know when it started lol but running into this for cache.img

of course "system" is there and then auto deletes the extracted cache folder. I just c&p the folder before it deleted and added it manually tho
[SuperR Kitchen] SuperR.:
I found the problem, and I will update as soon as I get a chance. If you are curious, there is a file with "chunk" in the name and the kitchen treated it as a sparsechunk rom.

Glad the fallback worked for you :)

The lines you refer to in the updater-script are on single lines intentionally. Sorry you think it's not nice.

I did a quick search and downloaded firmware with these numbers "N920GDDU3CQC7".

No errors extracting cache.img or copying the contents to /system. The error you see is not referring to /system though. It is referring to the unpacked version of cache.img/recovery/sec_csc.zip/system

If you send a fast link that does not require registration to the actual firmware you are using I can take a look.
[SuperR Kitchen] Valkiry:
How do i donate to get the donate version is it $10USD? Thanks dude id love to help support
[SuperR Kitchen] SuperR.:
All the info for the donate version can be found in post #4 :)
[SuperR Kitchen] Fedroid:
Please, give me access to the donate version of the kitchen. I have made the 10$ Donation.

My Gitlab user is Fedroid

Thanks
[SuperR Kitchen] Er. Aditya:
Can option to choose between super su and magisk root be added ? Thanks dev
[SuperR Kitchen] SuperR.:
There is a Magisk plugin for the donate version. Check the plugin repo here :)
[SuperR Kitchen] Er. Aditya:
Sorry for not reading dev and thanks a million for tremendous support
[SuperR Kitchen] bcrichster:
PM sent
[SuperR Kitchen] Mumang:
Bug report: Samsung SM-A7000 after repacking in update.zip or raw.img without changes in rom don't connect Wi-Fi.

FW - Last version from Samfirm - A7000ZCU1BQB1/A7000CHC1BQB1/A7000ZCU1BQB1/A7000ZCU1BQB1.

Wi-fi worked and trying connect,but freezing on ip address.

I'm flash with TWRP and create Tar for Odin but no sucessfull.

May be need logs created zip or raw.img?
[SuperR Kitchen] SuperR.:
There are problems in your updater-script. Try going to the root menu in the kitchen, remove root, then add it again. Gapps is not in the updater-script at all. Do the same for gapps in the plugin menu. The way it is currently I agree that neither will flash.

make_ext4fs is probably missing something you need to make wifi work and I don't know what it is. Try selecting set_metadata perm type when extracting your firmware. It will probably fix your issues.
[SuperR Kitchen] bitpushr:
Good stuff
[SuperR Kitchen] SuperR.:
v2.1.6.1 (Donate version)

Changes:

Better detection of the correct fstab file when there are several.

Fixed extracting rom zips that contain files with chunk in the name but are not sparsechunk.

v1.1.5.1 (Standard version)

Changes:

Better detection of the correct fstab file when there are several.

Fixed extracting rom zips that contain files with chunk in the name but are not sparsechunk.
[SuperR Kitchen] SuperR.:
Introducing the new donate version of SuperR's Kitchen :)

v3.0.0.0 (Donate version)

Changes:

Written in Python3 with native support for Windows and Linux

Plugin manager to run, download/install, and delete plugins directly from the menu

Plugins download their own dependencies

Binaries are downloaded rather than compiled locally

Other dependencies are downloaded rather than included

The Python version and info are located in a separate thread here. Please direct all discussion regarding the Python version to the new thread. Thanks and enjoy :)

NOTE: Please continue posting about the Bash donate version in this thread until support for it ends.

NOTE2: Most plugins have been rewritten in Python. If one is missing that you require, let me know and I will try to get to it asap.
[SuperR Kitchen] bcrichster:
Woooww.. You Da Mann!! [emoji41]
[SuperR Kitchen] rabidy:
donated

just donated, my gitlab acount name is rabidy

thank you
[SuperR Kitchen] rabidy:
Wow that was fast you rock
[SuperR Kitchen] TheLogicalGamer:
Is this a continuation of the orginal donate version? Does it require a new donation?
[SuperR Kitchen] SuperR.:
See the bottom of this post in the new Python thread. Please post all questions regarding the Python version to the new thread. Thanks :)
[SuperR Kitchen] SuperR.:
v2.1.6.2 (Donate version)

Changes:

Updated Android Image Kitchen by [MENTION=4544860]osm0sis[/MENTION] to v2.7.

v1.1.5.2 (Standard version)

Changes:

Updated Android Image Kitchen by [MENTION=4544860]osm0sis[/MENTION] to v2.7.