yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] afaneh92:
tryed both java-9-openjdk-amd64 & java-8-openjdk-amd64

heres what done

The following dependencies are missing:

gawk

lzop

Would you like to install now? y/n y

****************************************

The following package is recommended:

default-jre

Would you like to install now? y/n

****************************************

ERROR:

You need the kitchen binaries.

Would you like to install the required binaries? y/n

****************************************

Import includes file: /home/mohammad/twrp2/out/target/product/dreamqlte/obj/STATIC_LIBRARIES/libc_openbsd_ndk_intermediates/import_includes

build/core/binary.mk:646: recipe for target '/home/mohammad/twrp2/out/host/linux-x86/obj/EXECUTABLES/checkpolicy_intermediates/policy_scan.cpp' failed

make: *** [/home/mohammad/twrp2/out/host/linux-x86/obj/EXECUTABLES/checkpolicy_intermediates/policy_scan.cpp] Aborted (core dumped)

make: *** Waiting for unfinished jobs....

Import includes file: /home/mohammad/twrp2/out/target/product/dreamqlte/obj/STATIC_LIBRARIES/libc_pthread_intermediates/import_includes

build/core/binary.mk:646: recipe for target '/home/mohammad/twrp2/out/host/linux-x86/obj/STATIC_LIBRARIES/libsepol_intermediates/cil/src/cil_lexer.cpp' failed

make: *** [/home/mohammad/twrp2/out/host/linux-x86/obj/STATIC_LIBRARIES/libsepol_intermediates/cil/src/cil_lexer.cpp] Aborted (core dumped)

it seems glibc (Ubuntu GLIBC 2.27-0ubuntu2) break

mohammad@mohammad-desktop:~/twrp2$ ldd --version

ldd (Ubuntu GLIBC 2.27-0ubuntu2) 2.27

Copyright (C) 2018 Free Software Foundation, Inc.

This is free software; see the source for copying conditions. There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Written by Roland McGrath and Ulrich Drepper.

will try to downgrade as mentioned here https://xdaforums.com/oneplus-2/help/policyscan-cpp-aborted-core-dumped-t3310773
[SuperR Kitchen] Alann200:
I tried to extract my firmware's system.img but it's showing error while extracting system.img!

My system.img size 1.3G

What's wrong with kitchen why it's not extracting it?

Here is rom!

http://www.mediafire.com/file/n824r3dqeelt3if/Symphony_P6_MT6582_5.0_2GB_RAM.zip
[SuperR Kitchen] SuperR.:
The system.img in the firmware you linked is not a valid ext4 system.img. Try mounting it manually. It will give you an error. The kitchen only works with valid ext4 img files.

GDrive is fine
[SuperR Kitchen] Miustone:
Hey, i'm having currently trouble with the kitchen. After doing "./superr" does it tells Me that Python isn't found. I checked My Python Version and it tells Me 3.6. Any Idea what could cause this? I just used "git clone https://bitbucket.org/superr/superrs-kitchen.git" and "cd superrs-kitchen" before (Including the Missing Dependencies Part before). I'm on Ubuntu 18.4 right now...

Thanks in advance!
[SuperR Kitchen] baloo30310:
What version are you in Nougat or Oreo ?

Envoyé de mon SM-N950F en utilisant Tapatalk
[SuperR Kitchen] baloo30310:
With Oréo, however, there is a problem with mounting the data partitions with TWRP.

I know the team is working on it.:laugh:

---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------

Look at here :https://xdaforums.com/galaxy-note-8/how-to/fix-twrp-data-mount-issue-oreo-t3768928;)
[SuperR Kitchen] baloo30310:
I do not know what to tell you check permissions..

FAST&FAMOUS TEAM_GNT
[SuperR Kitchen] SuperR.:
My guess is that there is no python3 command in Ubuntu 18.04 since Python 2 is no longer installed by default. I am still on 16.04 so I can't verify this. However, Ubuntu 18.04 is not even released yet so this is not a kitchen issue. For now you could try creating a symlink somewhere in your PATH named python3 linking to python.

This can be tested by typing "python3 -V" in a terminal. If the output shows 3.6 as you said earlier, my guess is wrong. If you get an error, my guess is right.

edit: [MENTION=4756773]Miustone[/MENTION] - just downloaded 18.04 beta 1, and python3 is installed by default. I ran the iso in live mode, installed git, cloned the kitchen, it installed dependencies/downloaded binaries, and ran perfectly the first try. Not sure what to tell you in this case.

This is not firmware, it is a ROM. I need the firmware package you are using as a base.
[SuperR Kitchen] Alann200:
I can't get it extracted can help?
[SuperR Kitchen] SuperR.:
Open a terminal to the project directory where your system.img is. Then run the following command:

truncate -o -s 332800 system.img

After this the kitchen should be able to extract the system.img
[SuperR Kitchen] Macguyver1980:
Problem with

Hello,

I customized this Resurrection Remix ROM for my MI6 with last version of the kitchen and when I tried to install it on the phone, here's joined screenshot of error I had. And when installed the original ROM was ok.

Link of the ROM: https://xdaforums.com/mi-6/development/rom-resurrectionremix-5-8-3-t3654879

If you've a solution... ;) Thanks and regards.
[SuperR Kitchen] sashokmc:
I get error 255 in Twrp, try install myself custom rom.

Samsung GT-P5200. CPU Intel.
[SuperR Kitchen] SuperR.:
I am not sure what is going on. It seems install/bin/configure.sh is not being run for some reason so there is no /tmp/config file to read. Please try flashing this zip on your device and post the output. It does not make any changes to your device. It will use the same configure.sh to display the partition paths that will be used when flashing.

The update-binary included in the kitchen is only for arm/arm64. You will need to replace the update-binary with one that works on your architecture. For example, you could try one from a LineageOS rom for your device if it exists. Everything else should work properly.
[SuperR Kitchen] SuperR.:
Change perm type to set_metadata, and replace the update-binary again.
[SuperR Kitchen] sashokmc:
What? I not developer. I want just fix error 6.
[SuperR Kitchen] narshi shukla:
This is the option when u build with supers kitchen
[SuperR Kitchen] bcrichster:
He just explained exactly HOW to fix your error, pay attention. Lmao
[SuperR Kitchen] sashokmc:
Now error 7.

file_getprop: failed to stat "/tmp/config": nu such file or directory.

Updater process ended with error 7.

Error installing zip file.

I send recovery.log
[SuperR Kitchen] amakuramio:
will it run with bash linux on windows or do I need to install virtual linux machine...?
[SuperR Kitchen] SuperR.:
Extract this zip into kitchen/tools/devices. Change perm type to something else, then back to set_metadata. Then replace the update-binary again.

Virtual machine. WSL is not supported. I recommend one of the distros linked in my signature as they are already set up for the kitchen.
[SuperR Kitchen] sashokmc:
I working in VirtualBox, ubuntu 17.10. all ok.
[SuperR Kitchen] amakuramio:
alright, thanks, will try. I tried to make nougat and oreo roms through assayeds kitchen but I got bootloop every time, hope this kitchen will work so I can donate windows ver :)
[SuperR Kitchen] sashokmc:
Thanks! Working and booting.! I try deodex rom and flash. later.
[SuperR Kitchen] sashokmc:
Deodex Samsung ROM not booting.

Stuck on Samsung animation logo.
[SuperR Kitchen] sashokmc:
I deodex ROM with smali 2.2.3 working and booting great.

In your kitchen old smali 2.0.6
[SuperR Kitchen] SuperR.:
This kitchen includes smali 2.2.3 and 2.0.6. You must be deodexing KitKat or earlier, as these are the only versions that use 2.0.6. I did this a long time ago because older firmware was not deodexing properly with new smali. That may have changed now.
[SuperR Kitchen] sashokmc:
Thanks. How disable and remove automatic installation of apps at the first boot?
[SuperR Kitchen] bcrichster:
Use deBloat list
[SuperR Kitchen] ygecesefa:
Hi guys. I compiled note 8 sm 9500 snapdragon kernel from samsung sources. When When I try to unpack image or image. gz file from out/arch/arm64/boot/ kitchen gives error unrecognized format. What is wrong about my kernel.
[SuperR Kitchen] shoey63:
You can't just unpack the kernel (zImage). It has to be the whole boot.img, including ramdisk, kernel offsets etc.
[SuperR Kitchen] ashyx:
What are you trying to unpack it for? That is the kernel, just replace it with the one in the unpacked boot image.
[SuperR Kitchen] ygecesefa:
I tried that too, after modifying kernel dm, init. d etc all mods with kitchen phone boot to samsung odin screen with a I am trying to maka a kernel permissive but fstab modifications arent enough need to modify /security/selinux/selinuxfs. c from decompiled kernel. I modificated compiled but now trying to pack a kernel.

---------- Post added at 11:57 PM ---------- Previous post was at 11:52 PM ----------

by the way why zimage and gz form near the ram disk taking different names, I saw a custom kernels for my device it has different file names from stock kernel. It doesnt metter name of it? only file format?And can anybody help me add magisk module to ramdisk? Or show tip please?
[SuperR Kitchen] SuperR.:
Try without init.d. It causes a lot of issues and will be removed from the kitchen in the next update.

The donate version of the kitchen has a Magisk plugin :)
[SuperR Kitchen] bcrichster:
Can we set init.d to only be accessible for ROMs predating MM 6.0? Cuz they were sure useful in them JB, KK, LP ROMs. Lol
[SuperR Kitchen] SuperR.:
su.d works in all of them so I don't see the point honestly.
[SuperR Kitchen] bcrichster:
I.. don't think I can make further argument. [emoji854] Touché! Lmao
[SuperR Kitchen] ashyx:
Image is an uncompressed kernel, Image.gz is using Gzip compression.

Some devices can handle either.

However you need to ascertain which one your device uses.

Your kernel should be roughly the same size as the stock kernel and should be named the same as the unpacked stock kernel when replacing, usually zImage.

If I was you I'd test the kernel works before applying any mods to the ramdisk.

Simply unpack the stock boot.img, replace the kernel then repack.
[SuperR Kitchen] ygecesefa:
cool ? I wanna definetely donate how I can get donated version?But I am trying to boot. Tried with only insecure kernel options. Result is the same going to black samsung flash screen with sekernel enforced message . I thought this message have only old samsung s.

Do I must prefer CONFIG_ALWAYS_ENFORCE = false instead of new_value = 0? Without kitchen I got only bootloops.

I was also getting invalid lenght errors during compiling but compiled completed. Is it about that? or about compile platform I used that known custom one. By the way I am using 7.1.1 kernel rom version is the same but different release.
[SuperR Kitchen] SuperR.:
Donate version thread with instructions

kernel development is beyond the scope of the kitchen.

Regarding the kitchen however, I suggest to try without insecure boot. I was told recently it caused a problem for another Samsung user. Additionally, remove dm-verity and forceencrypt.
[SuperR Kitchen] SuperR.:
Please post a link or provide info on what changes need to be made to the ramdisk so I can include them when rooting the devices that require it. Is there a way to tell which devices need these changes? Thanks
[SuperR Kitchen] Androidwizzard:
I will try to provide additional information as soon as possible (after work).

In short: It may concern all new 5.1.1 firmwares for Samsung, like for Note 5, S6 edge plus, G750A Galaxy Mega 2, supposedly all other older devices which have recently received 5.1.1.
[SuperR Kitchen] SpasilliumNexus:
nvm. doesn't work.
[SuperR Kitchen] bcrichster:
Got my Linux kinda going and have this to say about the kitchen.. " I hate 64 bit!" Lmfao. What a pain, Lol. Keep up the awesome work tho, SuperR. I'll get Str8 soon enough and possibly say/do something useful again with the Kitchen. I'm impressed at the help the community is adding to the Kitchen and can't thank everyone enough for their responses. Way to go, Bros!!

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] SuperR.:
The log shows there is a problem building the system.img, which is why you don't get system_new.img and then no dat file.

Please try this modification to see if it clears up your issue.

From the main kitchen directory, open the following file for editing :

tools/scripts/build_rom_zip

Find and replace (starts at line 113):

${imgfile}size=$(wc -c $whatimg.img | awk '{ print $1 }')
#bsize=$(tune2fs -l $whatimg.img | grep "Block size" | awk '{ print $3 }')
#bcount=$(tune2fs -l $whatimg.img | grep "Block count" | awk '{ print $3 }')
#${imgfile}size=$(($bcount *$bsize))

with this

#${imgfile}size=$(wc -c $whatimg.img | awk '{ print $1 }')
bsize=$(tune2fs -l $whatimg.img | grep "Block size" | awk '{ print $3 }')
bcount=$(tune2fs -l $whatimg.img | grep "Block count" | awk '{ print $3 }')
${imgfile}size=$(($bcount *$bsize))

Save the file and try again. Let me know how it goes.
[SuperR Kitchen] SpasilliumNexus:
No go unfortunately. It skips "Preparing files for dat creation" like it doesn't find anything, and makes and incomplete zip with the output "Open raw image file system_new.img error: No such file or directory" in main.log.

Could it be something below lines 239 in that same file that could be causing the issue? I'm looking through it and see what I've mentioned above, but don't know how to read this stuff.
[SuperR Kitchen] hohassan444:
thanks for reply......

1 - I think the problem is in updater-script as if i replace it with another one ( extracted from another rom known to work on my device with set_metadata) , the wifi work without problem.

2 - the flashable SuperSU.zip is not flashed and updater-script is empty ( no entery for flashing SuperSU.zip).
[SuperR Kitchen] Androidwizzard:
[MENTION=5787964]SuperR.[/MENTION] HERE you get stock and root kernels, original and ramdisks unpacked to see the modifications as example.

Device Samsung Galaxy Note 5, Exynos 7420 - all N5 and S6 edge + have this processor and root will work the same way.

It is latest kernel with security update by Samsung for Samsung Pay.
[SuperR Kitchen] sefrcoko:
Just a note that the root issue also affects other devices on 5.1.1 such as my Note 4...which is not exynos-based like the Note5 is. Samsung increased selinux protection in 5.1.1 which causes bootloops when rooted (unless kernel patched as you mentioned and supersu 2.50 or later is used).
[SuperR Kitchen] SuperR.:
Would it be safe to say that if the device is Samsung and it is running 5.1.1, then the kernel needs to be patched? I ask because I need to figure out something in common with all of the devices that require these mods that is verifiable from the system or boot.img. Thanks for your help :)
[SuperR Kitchen] Androidwizzard:
Correct, I have mentioned this earlier so I think it could be common fix with this method in example I've given. Hopefully it will be implementable in kitchen.
[SuperR Kitchen] SuperR.:
The only difference in the example you provided that may be some trouble (at least until I figure it out), is the sepolicy binary. I am not sure how to deal with it, and I seriously doubt I can just use the modified one from your example in all Samsung devices lol. I will do some research and see if I can figure out how it was created. Thanks again for your help :)
[SuperR Kitchen] sefrcoko:
Yes to my knowledge this would apply to all 5.1.1 Samsung TW devices.

The original method was posted somewhere here on xda by chainfire. Originally for marshmallow but he said it also applies to Sammy 5.1.1. The fix required unpacking 5.1.1 stock kernel, pushing the sepolicy file to a 4.4 or 5.0.1 device rooted with supersu 2.50 or later, then eventually pulling the new file back and replacing it in kernel ramdisk then re-packing the stock kernel with the modified sepolicy. I'll share the link to that thread when I find it, but it seems unlikely this could be a vanilla solution as it could be device-specific (although I could be wrong).

EDIT: http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

Also, Phil's N910F kernel thread has relevant info in OP that might help too: http://xdaforums.com/showthread.php?p=62953277
[SuperR Kitchen] SuperR.:
It looks like the sepolicy binary is modified on the device itself, after the device is rooted with SuperSU 2.50+.

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

Not sure I can make all that happen with a button click lol. I will keep looking and if anyone finds a solution to modify sepolicy in Linux, please let me know.
[SuperR Kitchen] fhem:
IMHO. I would not do anything now- I would wait to see chainfire's final resolution. Right now it is all beta and wip.
[SuperR Kitchen] SuperR.:
He said he may automate the process when flashing SuperSU. If that is the case, the kitchen is already setup for it as soon as the new SuperSU comes out.
[SuperR Kitchen] fhem:
Yes he did and yes you are
[SuperR Kitchen] ferbulous:
Hi, is anyone else facing problem with sms getting rejected after flashing deodexed rom?

Apparently phones with mtk6735 chipset is having this issue (elite 5/vk6050s)

Here's a link to elite 5 deodexed rom if required

https://mega.nz/#!xpxDxRZS!BU_C71nzoyOoZqVoQUgfhurCeYGoDaiLCgtAxxKZ5rs

Or is there anything in the kitchen settings that I need to configure to avoid this problem?
[SuperR Kitchen] SuperR.:
I have found a way to modify sepolicy in Linux, without using supolicy on the device. I have made recovery, init, and init_shell permissive which may be enough to boot the rooted Samsung devices that require the ramdisk mods. However, there are 415 other changes in the modified sepolicy that will take an eternity to script. I am not even sure if the differences will be the same across all devices. For reference, here are the changed policies in the modified sepolicy.

http://hastebin.com/lonaqumugo.nginx

Need to do more testing and have a lot of hope that SuperSU automates this process with the zip lol

edit: I have scripted the other 415 changes, but as it turns out the tool I am using to add policies (sepolicy-inject) will not create new classes. So, we can only add rules for classes that already exist. This means I can only add 42 out of the 415 extra rules :( As I said before though, it may be enough to just make the recovery, init, and init_shell permissive along with the other ramdisk mods. At some point someone will need to test it. I may create an experimental kitchen for this purpose. Still strongly hoping SuperSU.zip will automate this process :p
[SuperR Kitchen] :
Can't thank you enough for the work you are doing especially as you don't even have a Samsung device. I'm running a note5 custom rom on a note4 and will gladly test anything
[SuperR Kitchen] SuperR.:
v1.1.9.4 (Free Bash version)

Changes:

Removed all code attempting to get the kitchen running properly in cygwin and WSL.

Added error message when running in cygwin and WSL.

Removed init.d support.

NOTE: cygwin and WSL have caused many issues with this kitchen. If you are looking for a kitchen that runs in Windows, please check out the donate version which runs in native Windows and Linux :)
[SuperR Kitchen] Coayer:
Edit: I might have found solution, apologies for the post.

Thank you for the kitchen Super R :)
[SuperR Kitchen] ygecesefa:
I did nothing changed and it have different size. Is that work if I edit img_info file or must I unpack stock file boot img from same version of source.?For example stock image is 7.1 but different version and booting my phone without problem. But my sources belongs to an older update it is 7.1 too.

will it cause problem?

Also I am getting 3 file after compile Image file image. gz and image. gz. dtb Only using image. gz. dtb doesnt kick phone to odin screen. After using image. gz. dtb now phone giving seandroid enforced error and stucked.
[SuperR Kitchen] ashyx:
Please upload your stock boot.img and your custom kernel images.
[SuperR Kitchen] albino71:
Is it possible to update a custom AOSP based ROM with this kitchen?

I mean, the ROM is no longer maintained, but I would like it to have the latest security patches.

If it is possible (and not to hard! :)), I will figure out how to use the kitchen.

Cheers
[SuperR Kitchen] ygecesefa:
Here: https://drive.google.com/file/d/1KlwoewdRJrytXy7h6P5KXYmmU7UzEpmP/view?usp=sharing
[SuperR Kitchen] ashyx:
Repacked the boot.img with your kernel. If it doesn't boot then you have an issue with your kernel.

http://s000.tinyupload.com/?file_id=56381354415701481098
[SuperR Kitchen] ygecesefa:
Did not boot. But not give seandroid enforced error too. I used mkboot to repack what did you use? Also do I must charge my compiler? For my kernel problem
[SuperR Kitchen] kevintm78:
If you're using AIK you can add a file in the split image to remove the red SEAndroid message. Create a file and name it "boot.img-tailtype" and open that file and type "SEAndroid". After that you'll just see the yellow "set warranty bit: kernel" message. I know that doesn't help with you're overall problem but I thought I would mention it just in case Superr might want to add an option for that. I uploaded the file in my split image if you want to use that, just rename it and remove the .txt extension from the end.
[SuperR Kitchen] ygecesefa:
Will I put that near ZImage?Also I saw length error during the compiling.Is it overall problem or Must I change compiler.I was using popular custom one.
[SuperR Kitchen] ashyx:
Use the same tool chain as Samsung use until you get a working image.
[SuperR Kitchen] ygecesefa:
Thank you very much. You are the best. I am trying this over three weeks. I am new for this stuff. But nobody tend to help except you.Thanks to all. At least I found source of the problem. Definetely will mention if I succed.
[SuperR Kitchen] bcrichster:
Which toolchain would that be? I ask for the learning portion of us
[SuperR Kitchen] ashyx:
See the text that comes with the source code. It will tell you which one to use.
[SuperR Kitchen] bcrichster:
Hey that's really cool, thanks.
[SuperR Kitchen] sashokmc:
I try deBloat ROM, still apps install at the first boot.
[SuperR Kitchen] ygecesefa:
repacked with change compiler, also used samsung 's compiler result is the same.Is it about mkboot version?

What is wrong about my kernel?
[SuperR Kitchen] sashokmc:
I have Samsung Galaxy j7 SM-J710FN. Android 7.0

Kitchen cannot disable force-encrypt in kernel.
[SuperR Kitchen] ygecesefa:
Guys Is there any telegram group thatI can get help about compile problems? I dont wanna bother you. Sorry.
[SuperR Kitchen] SuperR.:
If you provide a fast link to the firmware that does not require registration I will take a look.

Please try the attached updater-script. It was created from your firmware using the donate kitchen.
[SuperR Kitchen] archie9211:
Cannot use this in arch linux

its showing the error that it can't find the java :

MISSING DEPENDENCY:
You need at least Java 8 to use this kitchen.

The following package is recommended:

default-jre

which: no dpkg in (/usr/local/bin:/usr/local/sbin:/usr/bin:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/lib32/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)

Press ENTER to exit^C

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

but i have installed java openjdk10-jre

[archie@Antergos superrs-kitchen]$ java --version
openjdk 10 2018-03-20
OpenJDK Runtime Environment (build 10+46)
OpenJDK 64-Bit Server VM (build 10+46, mixed mode)
[SuperR Kitchen] mdiaz33685:
I have always used 32 and 64 bit of Java 8, I uninstalled them both and installed Java v10, and redid the steps in Windows 10 without any issues.

Just wanted to inform that it does work, that's all.

Edit.. that is why I used to install both 32 and 64 versions because of the errors I would get, way back in the days..

I uninstalled all jdk and jre version 8 1st, then installed version 10.
[SuperR Kitchen] SuperR.:
This is due to openjdk 10 version not including a decimal or dash so the kitchen sees 10 as 1.0 which is less than the required 1.8 (java 8). This will be fixed in the next update. Java 8 or 9 will work for now.

I will look into it some day when I get some time. The donate kitchen takes priority so things move quicker over there.