yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] baloo30310@gmail.com:
Hello i keep you updated

Superr. .
[SuperR Kitchen] Sh0X31:
[MENTION=5787964]SuperR.[/MENTION]

here is the log :)
[SuperR Kitchen] SuperR.:
I am not sure what is going on. There is an sh error in the recovery.log, so maybe try replacing configure.sh with the one attached. It seems all the info is getting passed to the updater-script correctly, but maybe it will help.

If not, you could try replacing the following in your updater-script:

run_program("/tmp/configure.sh");

with this:

run_program("/sbin/sh", "/tmp/configure.sh");

I also never got an answer if "/dev/block/platform/sdhci-tegra.3/by-name/system" is the correct by-name for your device. If not, that is the problem and we need to figure out what is going wrong.
[SuperR Kitchen] Mezabaru:
when i try to git clone the donate version I get repository not found, is a cleanup underway?
[SuperR Kitchen] SuperR.:
Somehow you were not on the list. Fixed now. Sorry for the inconvenience.
[SuperR Kitchen] Mezabaru:
Thank you and after 2 weeks I have a permissive kernel built. Safe to say I spent roughly 80 hours learning ?.
[SuperR Kitchen] tanish2k09:
[MENTION=5787964]SuperR.[/MENTION]

Which tool did you use in earlier versions for unpacking Boot images?
[SuperR Kitchen] SuperR.:
Until v1.1.42/2.1.5.2, the kitchen was using my own pack/unpack functions and the same mkbootimg/unpackbootimg binaries found in AIK.
[SuperR Kitchen] tanish2k09:
This is weird. I'm facing problems with images since my last clone. The last perfect version for me was 1.1.3.8

In the latest version at the time of posting, ie 1.1.4.3, some images get unpacked incomplete. And some others are good.

I just noticed that all nougat boot images unpack smoothly. But I face that incomplete unpack issue with all mm boot images. I'm having network problems in attaching the image. Will attach when speed is good.
[SuperR Kitchen] Sh0X31:
[MENTION=5787964]SuperR.[/MENTION] change the update-script and configure.sh but still the same error >.<
[SuperR Kitchen] baloo30310@gmail.com:
Hello superr! Well I launched a deodexation on the SM-N910F smali / basmali and it still does not work it's worse bootloops get to the language selection. It gets more and more locked after I do not see too much interest not to deodexer the rom cordially
[SuperR Kitchen] SuperR.:
I am not able to reproduce the issue with any boot.img I have.

Still never answered if the by-name line is correct for your device. Nothing else matters if it is wrong. If it is correct, I am not sure what else to do.

Maybe one of our Samsung experts can help you more.
[SuperR Kitchen] Mezabaru:
I've been having this issue with 5.1.1 if I do and perm type but the kitkat one, I did some edits based on what was posted trying to make raw_img work cause I'm bored, I'm doing this on an ssd, so I'll attempt a fresh build if this one doesn't flash.

Edit; sparse data and raw_img have not worked, doing set_metadata
[SuperR Kitchen] levone1:
Using TDA for Android, based on this tool, (https://xdaforums.com/android/software-hacking/mod-lollipop-t3339340), and have used it 3 or 4 times before with no problem with stock and custom rom, (Xperia Z1c), but now having a problem with error message 'sorry but this tool is only for Lollipop'. Using straight stock Sony 5.1 rom flashed with official Sony tool. I tried editing arm script and build prop, to change the sdk line, etc, with no change, and also deleted the sdk check from arm script, which gets me to the line where you're supposed to enter arch, but doesn't let me, it just ends suddenly.

Any ideas? Thanks
[SuperR Kitchen] Ammaar884:
hee is the link for the firmware https://www.androidfilehost.com/?fid=457095661767123330
[SuperR Kitchen] Swapnil Soni:
Does packing Sdk23 ,24, and 25 into flashable zip, supportable with this kitchen? :)
[SuperR Kitchen] SuperR.:
I am not sure I understand the problem. Why are you using such an old kitchen version?

The Lollipop deodex tool I created was abandoned a long time ago in favor of this kitchen. Additionally, I don't support derivative tools I did not create.

Your firmware extracted perfectly. I let the kitchen extract the zip instead of manually extracting the img files.

Yes
[SuperR Kitchen] Mezabaru:
I was referencing the problem from that post, I ended up using sets meta data and dhcpcd was fine.
[SuperR Kitchen] levone1:
Thanks for answer. I didn't necessarily expect official support, just thought someone here might have insight. I figured the scripts are probably the same... I guess I'm mainly wondering what the script is looking at that's making it think it's not LP.

Incidentally, I also got errors with another deodexer on PC, so I'm thinking it's something about the ROM, but not sure what...

Thanks for your work, maybe I'll just try the kitchen after all.
[SuperR Kitchen] bcrichster:
I solved my busybox issue by adding "android_external_busybox" pkg to the repo, and all is well. But out of curiosity I took the compiled ROM zip(sparse) from the build and extracted it in kitchen, made no changes and repacked the ROM... getting a 6MB smaller zip in process... Is that normal? No, I didn't flash it but have uploaded the Kitchen generated updater-script with the Original compiled in ROM since MELD says there's some differences. I am not complaining at all, just trying to do my part in help getting sparse-dat perms found and processed correctly.

Here is my ROM source file: https://www.androidfilehost.com/?fid=529152257862702731
[SuperR Kitchen] SuperR.:
Looking back at the code, I am not sure why I did it the way I did lol. The Lollipop deodex tool I created looked at ro.build.version.release in build.prop. If the value is greater than or equal to 5.0it will work. If build.prop does not exist, it asks you which api to use. My suggestion of course is to use the kitchen. If you must continue on your path you could add/edit the prop mentioned above with a value corresponding to your api level:

21 = 5.0 or 5.02

22 = 5.1 or 5.1.1

example:

ro.build.version.release=5.0.2

The zip size is not relevant, as the compression levels are likely to be different. You won't know if everything works properly until you flash it :)

The updater-script is completely replaced when unpacking a sparse_dat rom so there are sure to be differences compared with the original.
[SuperR Kitchen] bcrichster:
Meld showed differences but I honestly don't know what I'm looking at with these yet.. Just trying to help with data
[SuperR Kitchen] Ammaar884:
Ok but I tried it but it was showing same error
[SuperR Kitchen] SuperR.:
Scroll up in your terminal and see if there are any other errors on the screen.

I am not able to reproduce the issue so it is either user error, or something going on with your machine.
[SuperR Kitchen] Ammaar884:
No nothing no error and is there a 32 bit version of ubuntu4kitchen?
[SuperR Kitchen] SuperR.:
If you are running 32-bit Linux, there may be issues I am not aware of. I only test on 64-bit Ubuntu 16.04. Ubuntu4Kitchen is only 64-bit.
[SuperR Kitchen] Ammaar884:
Ok thank you
[SuperR Kitchen] Ammaar884:
Yes there is an error look sorry didn't find it the first time and did it extracted for you how do you did it? Do you placed the firmware zip into the project folder or the files in the firmware such as AP BL CP HOME_CSC?
[SuperR Kitchen] SuperR.:
Looks like mount is your problem but i am not sure why. You could try "dmesg | tail" as the error suggests. It might provide useful info.

As I mentioned before, I downloaded the firmware zip into the project directory and let the kitchen extract the zip. It extracts all the needed parts automatically. Your firmware worked perfect for me so if you still have trouble I don't know what to tell you.
[SuperR Kitchen] Ammaar884:
So how to try dmesg |tail I tried to do same as you did that put firmware zip in project folder but the same Mount error?

---------- Post added at 06:13 PM ---------- Previous post was at 05:56 PM ----------

This firmware is android 6.0.1 I tried 5.0.2 it worked perfectly
[SuperR Kitchen] ShinySide:
Reboot your pc lol

I just had this issue on arch. A reboot fixed it lol
[SuperR Kitchen] Ammaar884:
rebooted but still same error
[SuperR Kitchen] Captain_Throwback:
Your reply made me think of this:
[SuperR Kitchen] ShinySide:
? it's always on my step list when something isn't working correctly since I'm lazy and have pacman set up to auto update via systemd hourly and never see what's updated/etc lol but definitely lol
[SuperR Kitchen] Ammaar884:
Any ideas to fix it?
[SuperR Kitchen] blueberry60:
I want to port HTC10 2.41.401.4 Deodexed Rom to my M9 Device. I created a HTC10 Port afp.zip that includes app,framework,META-INF and priv-app from HTC10 Deodexed Rom, but I don't know to follow a proper "Road Map" with SuperR's Kitchen Tool.
[SuperR Kitchen] ShinySide:
Tried searching the thread but havent found anyone say "oh yeah this fixed it, but has anyone figured out the deodex FC issue with the SetupWizard.apk?

Error as I havent seen anyone post it lol

E AndroidRuntime: FATAL EXCEPTION: AsyncTask #5
02-17 05:17:30.477 7077 10432 E AndroidRuntime: Process: com.google.android.setupwizard, PID: 7077
02-17 05:17:30.477 7077 10432 E AndroidRuntime: java.lang.RuntimeException: An error occurred while executing doInBackground()
02-17 05:17:30.477 7077 10432 E AndroidRuntime: at android.os.AsyncTask$3.done(AsyncTask.java:309)
02-17 05:17:30.477 7077 10432 E AndroidRuntime: at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
02-17 05:17:30.477 7077 10432 E AndroidRuntime: at java.util.concurrent.FutureTask.setException(FutureTask.java:223)
02-17 05:17:30.477 7077 10432 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:242)
02-17 05:17:30.477 7077 10432 E AndroidRuntime: at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
02-17 05:17:30.477 7077 10432 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
02-17 05:17:30.477 7077 10432 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
02-17 05:17:30.477 7077 10432 E AndroidRuntime: at java.lang.Thread.run(Thread.java:818)
02-17 05:17:30.477 7077 10432 E AndroidRuntime: Caused by: java.lang.VerifyError: Rejecting class com.google.android.setupwizard.util.GooglePlaySetupHelper because it failed compile-time verification (declaration of 'com.google.android.setupwizard.util.GooglePlaySetupHelper' appears in /system/priv-app/SetupWizard/SetupWizard.apk)
02-17 05:17:30.477 7077 10432 E AndroidRuntime: at com.google.android.setupwizard.update.EarlyUpdateFragment$EarlyUpdateTask.doInBackground(EarlyUpdateFragment.java:198)
02-17 05:17:30.477 7077 10432 E AndroidRuntime: at com.google.android.setupwizard.update.EarlyUpdateFragment$EarlyUpdateTask.doInBackground(EarlyUpdateFragment.java:196)
02-17 05:17:30.477 7077 10432 E AndroidRuntime: at android.os.AsyncTask$2.call(AsyncTask.java:295)
02-17 05:17:30.477 7077 10432 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:237)
02-17 05:17:30.477 7077 10432 E AndroidRuntime: ... 4 more
[SuperR Kitchen] TheLogicalGamer:
I'm having an issue with custom zips. If I create and flash a zip the rom won't boot. But those same apps built into a whole rom with the kitchen will flash, and boot just fine. I'll post more details later if needed. I'm about to start work. Just wanted to see if anyone had any ideas. The phone I'm working on is a lg g3 d851 tmo varient. Thanks guys.
[SuperR Kitchen] blueberry60:
I think custom zips are used to get apps, framework and priv-app (can be added libs) , so you can use these files a wide range of building rom process (eg. porting rom).
[SuperR Kitchen] TheLogicalGamer:
So to make it actually flashable. I would have to build it like a rom? And just delete everything I didn't need?
[SuperR Kitchen] SuperR.:
The custom zips should be flashable as they are. I am not sure why it won't boot after. Maybe the permissions are not getting set correctly? If you figure out the cause let me know.

The kitchen does not port roms, it only creates them from what you provide. There are many porting guides on xda :)

I have no idea, but if you get it sorted out please let me know :)
[SuperR Kitchen] TheLogicalGamer:
[MENTION=5787964]SuperR.[/MENTION] How could I test that with out the rom booting. Could I try building it like a rom, and just deleting everything, but what I need? As in without a boot.img. if I did that though would I need to make changes to the updater-script?

Edit: I've found the lines

Delete_recursive("/system/app");

Delete_recursive("/system/priv-app");

So those would wipe system/app and system/priv-app correct? If that would explain the issue as I just have the one apk I've modded for a test in the zip. So that would definitely explain why it's not booting.

Edit 2: I removed those lines,a d it flashed and booted fine. However my changes didn't take. I don't if that's because you can't theme an app via color xml edits or it didn't overwrite the original apk though.
[SuperR Kitchen] bcrichster:
Delete the old app before inserting a new one into the zip
[SuperR Kitchen] ShinySide:
App theme'n isn't as easy as just changing code in color.xml. you'll find value all thru out layout etc (and images of course). Just run grep -r "#" and you'll find them all.
[SuperR Kitchen] TheLogicalGamer:
So it can be done just by value changes alone? Instead of png edits? As long as color changes is what you're after? I do all my editing of apk's on windows so what would I search for with notepad ++?

---------- Post added at 01:44 AM ---------- Previous post was at 01:41 AM ----------

Eventually I would like to make my theme's flashable seperately from my main rom. Oh sorry just now seen. I just copied the project and changed the superr_project_name_here to keep them seperate. So it wasn't because I had the orginal apk in the app priv-app zip.
[SuperR Kitchen] ShinySide:
No. It's going to be a mix of xml and images and if you wanted to get really fancy (if it's a system app) use setting observers, etc for on the fly color and image changing via smali. But that's extremely off topic for this thread. Lol but was just letting you know it's not going to be a kitchen/updater script issue but your edits lol
[SuperR Kitchen] TheLogicalGamer:
The issue with the script. I was reffering to was that even though there is only one app in the zip. It was deleting all apps in system app, and priv-app. Instead of overwriting the one apk already there. Could I pm you on the other issue perhaps?
[SuperR Kitchen] Svan987:
#5142 to #5146 with the great help of Captain_Throwback

Tested only custom zip "app, priv-app". System folder was missing. Is it fixed ?

"Boot/Recovery tools" then "Add/Remove forceencrypt" with false status "disabled". Using the option does nothing and the status not changing.

Would be great if one day you can check (take your time no emergency). Can you tell me for manual check what is modified when I disable "dm-verity" ?

MEGA stock rom link : T813XXU2APK6_T813OXX2APJ1_TPH

Cheers.
[SuperR Kitchen] :
Couple of issues/bugs

What Kitchen version?

v1.1.4.3

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

Arch Linux, 64bit

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

T705 Galaxy Tab S LTE

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

system.img . Extracted from Odin flashable from updato

What Android version?

6.0.1

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

set_metadata

What did you do after extracting and before building?

debloat_custom and debloat knox only

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

yes

1st issue i had was when the script tries to extract the image. Here's a partial output

stat: failed to get security context of 'output/bin/androidshmservice': Operation not supported
stat: failed to get security context of 'output/bin/apaservice': Operation not supported

Happens to all the executable in /system/bin .

2nd issue is the script assumes the contents in /dev/block/platform/dw_mmc.0/by-name

to be in lowercase. At least on the tab S the symlink in that dir is in uppercase.

Here's the excerp of the updater-script created

format("ext4", "EMMC", file_getprop("/tmp/config", "byname") + "/system" + file_getprop("/tmp/config", "slotnum"), "0", "/system");
set_progress(0.100000);
mount("ext4", "EMMC", file_getprop("/tmp/config", "byname") + "/system" + file_getprop("/tmp/config", "slotnum"), "/system");

Back then I was on v1.1.0.5 of your script, it worked fine.

It parsed the selinux context properly as well, so I'm not sure which part of the update that is messing up.
[SuperR Kitchen] SuperR.:
I will add a question when creating a custom zip asking if you want to delete existing first.

Will take a look when I get a chance.

1st issue: Try this:

https://xdaforums.com/showpost.php?p=70840791&postcount=5237

2nd issue: /SYSTEM should still be detected and used. Please send the firmware so I can take a look. In the meantime, just change the part of the lines you posted from + "/system" + to +"/SYSTEM"+ and leave the last "/system" the way it is.
[SuperR Kitchen] :
The library you bundle solved the issue. What's causing it exactly?

Here's the firmware, but should be the same for any other region.

http://updato.com/firmware-archive-select-model?record=E488BA16D7EC11E69215FA163EE8F90B
[SuperR Kitchen] SuperR.:
Glad to hear it worked :) The problem is that your system is not selinux enabled so the stat utility does not have the required libs to check the file_context. When you install the stat_alt.zip, it bypasses your system stat utility in favor of the one in /home/username/bin. This stat however is a bash script that runs /home/username/bin/stat1 with the required selinux libs.
[SuperR Kitchen] :
Hi. I tried your kitchen but it tells me that i dont have symlinks. Basically this is the rom structure:

system folder

boot.img

in system folder its a Stock TouchWiz 5.1.1 ROM with debloating and some modding. Changes are in app,framework,priv-app and also media( deleted some ringtones) What could be causing the problem? I want to make an updater script for my rom.
[SuperR Kitchen] SuperR.:
The problem is that your rom does not contain symlinks. Your rom needs symlinks for many files, and the kitchen does not invent symlinks since they are different for all devices.

If you post your device model maybe someone else with the same device will upload their symlinks file for you. In the meantime, you can try the one attached. It is from an SM-G531F running 5.1.1. Unzip the file into your 00_project_files directory and try again. WARNING: some things may be broken since these symlinks are not from your device.
[SuperR Kitchen] :
Hm, i found another way of making the rom that is better (no data loss) but thanks anyway, i will take it as a note. Your kitchen is great though, gonna press the magical button!
[SuperR Kitchen] Captain_Throwback:
Why not share so [MENTION=5787964]SuperR.[/MENTION] can improve the kitchen?
[SuperR Kitchen] :
just used the installer template from this thread https://xdaforums.com/sprint-galaxy-s5/general/how-to-deodex-lollipop-rom-t3065596

basically it installs app,framework and priv-app, its a more effective way of doing it.
[SuperR Kitchen] The Sickness:
Add the lib folder in with the apk.
[SuperR Kitchen] SuperR.:
v2.1.5.4 (Donate version)

Changes:

Allow extracting zips with the word recovery in the file name.

Possibly fixed pulling system.img from some devices.

Fixed custom zips not being packed properly.

Added question asking if you want custom zips to delete the existing directories when flashing.

Fixed updater-script not using capitalized partition names when required.

v1.1.4.4 (Standard version)

Changes:

Allow extracting zips with the word recovery in the file name.

Possibly fixed pulling system.img from some devices.

Fixed custom zips not being packed properly.

Added question asking if you want custom zips to delete the existing directories when flashing.

Fixed updater-script not using capitalized partition names when required.
[SuperR Kitchen] bassbounce:
This works great thank u.

I have one problem, if i install Flashfire it stays on getting root queries and Flashfire got root and supersu is working.

On stock rom and root is it working, but not if I make a stock rom with ur kitchen.
[SuperR Kitchen] Hamidreza2010:
[MENTION=5787964]SuperR.[/MENTION] for sony device in ftf rom , there isnt system.img and has system.sin

did you add code into kitchen for silently rename system.sin to system.img ?

i think you want to added before
[SuperR Kitchen] shoey63:
Try this tool by [MENTION=4120742]munjeni[/MENTION] to extract system.sin to system.ext4

https://xdaforums.com/showthread.php?p=70348611

You can rename to system.img after that if needed.
[SuperR Kitchen] ts_firehawk:
I think I have a problem. I'm running on Elementary OS 0.4 and no matter what I do or install, the kitchen doesn't run. It sticks on the following screen:

Every single package it lists is installed. I've even used the command from the FAQ section (it returns me that all the packages are installed and up to date). What I'm doing wrong?

EDIT: nevermind. It was a permission issue.
[SuperR Kitchen] raul.lopez1958:
After kitchen a custom rom:

When flashing opengapps pico or nano -> Error 70 ... insufficient system space available ¿?

Lineageos okeys rom

XeonHD Kernel

Used TWRP_3.0.3-2-TugaPower
[SuperR Kitchen] Hamidreza2010:
thanks bro

i know that and i did it always but i reported this idea to [MENTION=5787964]SuperR.[/MENTION] before ( some month ago ) but i donw know he add this code (silently rename system.ext4 to system.img ) to kitchen or not

for this i ask him ;)
[SuperR Kitchen] SuperR.:
I don't understand the problem. If you figure out what needs to change in the kitchen, let me know.

I am pretty sure system.sin can't just be renamed to system.img. You need to extract it first.

Sounds like an opengapps issue.

I am pretty sure system.ext4 is silently renamed to system.img. Let me know if not :)
[SuperR Kitchen] STEVE_MARS:
Hi, [MENTION=5787964]SuperR.[/MENTION]

I have a LeEco LePro3 X720. With last update, I extract system.img from TWRP and then only build a new ROM for test, without any modification (well, setup dualsim in build.prop) and in setupwizard when configure fingerprint say "fingerprint hardware not avaliable". All rest of ROM works fine, but fingerprint not.

In stock ROM FP works OK.

What do you think? I am testing all but I dont found how to solve this.

Many, many thanks in advance.

P.D. Sorry for my awful english, I am spanish.
[SuperR Kitchen] SuperR.:
If your perm type is set_metadata, try raw_img or sparse_dat.

If your perm type is raw_img or sparse_dat, try set_metadata.

When extracting system.img, set_metadata is the most reliable choice since all the original permissions, contexts, and capabilities are used. sparse_dat and raw_img rely on make_ext4fs to set permissions, contexts, and capabilities. If your device needs something set that is not included in make_ext4fs, it will not get set.
[SuperR Kitchen] STEVE_MARS:
Ok, I try it. Thanks for reply ¡¡¡ :highfive:
[SuperR Kitchen] nightcervant:
ehi [MENTION=5787964]SuperR.[/MENTION] I upgraded to the latest version, but unfortunately I can not extract the system.img to P9 Plus, I am attaching the screen...
[SuperR Kitchen] Saarliner:
Hi, is it possible to set the selinux status to permissive on stock kernel with superr-kitchen?

Greetz Dirk / Saarliner
[SuperR Kitchen] bcrichster:
Possible after unpacking the image, I think.. You can edit and repack. Is it automatic? No.
[SuperR Kitchen] SuperR.:
Are you able to pull system.img from your device manually? If so, what command are you using? Are you trying to pull from Android or TWRP? Do earlier kitchen versions work?

The kitchen does not do this, but as [MENTION=5297774]bcrichster[/MENTION] said there are ways to achieve permissive status. Look into su.d/init.d permissive scripts.