yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] JochenP:
yes you are faster :D but nevertheless there are Exceptions in terminal window if i scroll up and these errors occurs:

Decompiling SystemUI.apk ...

I: Framework installed to: /home/jogy/apktool/framework/2.apk

I: Framework installed to: /home/jogy/apktool/framework/1.apk

Exception in thread "main" brut.androlib.AndrolibException: java.io.FileNotFoundException: system/app/SystemUI.apk (Datei oder Verzeichnis nicht gefunden)

at brut.androlib.res.AndrolibResources.installFramework(AndrolibResources.java:647)

at brut.androlib.res.AndrolibResources.installFramework(AndrolibResources.java:592)

at brut.androlib.Androlib.installFramework(Androlib.java:643)

at brut.apktool.Main.cmdInstallFramework(Main.java:239)

at brut.apktool.Main.main(Main.java:87)

Caused by: java.io.FileNotFoundException: system/app/SystemUI.apk (Datei oder Verzeichnis nicht gefunden)

at java.util.zip.ZipFile.open(Native Method)

at java.util.zip.ZipFile.<init>(ZipFile.java:219)

at java.util.zip.ZipFile.<init>(ZipFile.java:149)

at java.util.zip.ZipFile.<init>(ZipFile.java:163)

at brut.androlib.res.AndrolibResources.installFramework(AndrolibResources.java:600)

... 4 more

I never see these errors if i use apktools on my windows 7 machine - i hope you can delimit this problem

---------- Post added at 11:42 PM ---------- Previous post was at 11:38 PM ----------

op = original post - read from scratch :eek:
[SuperR Kitchen] Danvdh:
donate version worked perfectly for me today :) very good work and thanks alot!
[SuperR Kitchen] SuperR.:
Try de/compile manually in Linux using apktool.jar. If you don't get the errors, I will try to figure out what the issue is. If you get the errors, there is nothing I can do but suggest you post in the apktool thread.
[SuperR Kitchen] bigrammy:
It would be cool if you could add a Plugin option so we can run our own little scripts within the Kitchen.

eg: I am working on a simple porting script for my mtk phones. Your kitchen does 98% of the job already so it's just a matter of my script making a "Ported" folder and copying over the various files folders libs boot.img stuff etc etc from the Port and Base projects already made using your kitchen. After my script is run it's then back to your kitchen to complete the task of rebuilding the "Ported" project with the usual options.

Once my theoretical super ace porting script is ready I could then share it and anyone wanting to use it could simply drop it in the plugins folder.

Anyone else who has a labour saving scripts could also share them.

I am thinking this feature would/could add more device specific options with your kitchen doing the bulk of the work and the plugins doing the shuffling things around.

I dont think this is anything really new but would be a nice little feature. :o
[SuperR Kitchen] SuperR.:
This sounds easy enough. Here are some things that would be nice to know:

1. At what point do you want the script in the plugin directory to run? At the end of extracting for a new rom perhaps? Or, do you want to choose to run it when you want using a menu option in the kitchen?

2. What variables do you think need to be passed to it (ROM directory location, device name, etc)?

3. Should it be set up so if there is more than one script in the plugin directory they all run one after another? Or, should it be set up so you choose which one to run if there are more than one?
[SuperR Kitchen] bigrammy:
"Choose to run it when you want using a menu option in the kitchen?" I think this option would be best.

Not so sure about this :confused:

I am sure there could be some scripts that may find this option useful but I was thinking more along the lines that the plugin is tailored to the kitchen so the plugin script should know and ask such question rather than the kitchen passing the info which may complicate the plugin script.

Me been a total dork at scripting I only need to view the kitchen code and I seem to break it so the less interaction with the kitchen script the safer it will be :laugh:

The idea is that you (the kitchen) needs to do very little or you could end up fixing plugin scripts and adding features to them which is not what you want.

"it be set up so you choose which one to run if there are more than one?" :good:

Maybe you could make a template plugin script which the kitchen could read for things like name of the script, display any required info, script author, what it does etc etc.

For the plugins people should contact the plugin author rather than you should they encounter any problems.

Plugins should stay within the Kitchen structure and not try to do anything the kitchen already does such as unpack a boot.img's eg: the plugin should jump back to the kitchen for this type of thing maybe you could add some sort of variables to the template for skipping to specific Kitchen functions :eek:

I hope all this kinda makes sense to you been wrote in layman's terms as I am still totally new to all this. :cowboy:
[SuperR Kitchen] SuperR.:
Unfortunately we won't be able to jump from the plugin to the kitchen and back to the plugin where it left off. The plugins will need to be more independent, meaning that once it is run it will need to do what it does and quit. The kitchen uses functions for everything and the plugin will not have access to those functions unless they are in the plugin itself.

However, you could write plugins that do anything you want to a rom if we pass variables to it when it is run. For example, if we pass "/home/user/kitchen/superr_projectname" and define it in the plugin "romdir=$1", you can "cd $romdir" within your plugin and make modifications to the current working rom directory.
[SuperR Kitchen] bcrichster:
Why is this asking me if I would like to convert the updater-script to an update-binary? I'm in build menu 'build full ROM'... Making a stock unmodified ROM..

Sent from a Dirty Unicorn's LolliPop! N9515
[SuperR Kitchen] SuperR.:
It is a new feature. The update-binary conversion eliminates the update-binary as a binary and uses a shell script named update-binary instead (same as what SuperSU and Busybox installer do). If you want the standard as before, just say no :)
[SuperR Kitchen] bcrichster:
I'm game.. Just need some info, Lol. Like, what are the pro's & cons? HOLY CRAP.. This laptop just deodexed the whole ROM in about 65 seconds!! Normally would have take 10-15 mins on my old one.. This kitchen just smokes stuff it's so fast, WOW!

Sent from a Dirty Unicorn's LolliPop! N9515
[SuperR Kitchen] SuperR.:
Pros: Works on all devices because there are no update-binary incompatibilities.

Cons: Does not work with sparse_dat roms. Has not been tested very much.
[SuperR Kitchen] bcrichster:
So.. Perfect for metadata ROMs then?

Sent from a Dirty Unicorn's LolliPop! N9515
[SuperR Kitchen] SuperR.:
Theoretically, yes :p
[SuperR Kitchen] bigrammy:
Yes I was just thinking out loud and I can see how that maybe a problem :silly:

I tried to follow your script to insert a boot.img functions in my script but to be honest I can't even see/follow how yours does what it does :laugh:

it's is not really problem as I just made sure I extracted both boot.img's in the superr_port and superr_base prior to running my script. :good:

Hmm I see what you mean but that's getting well above my pay grade but others may find it useful :confused:

If there is not much interest in this possible feature then please don't bother on my account I was just throwing it out there :o
[SuperR Kitchen] SuperR.:
v2.0.7.3 (Donate version)

Changes:

Updated the update-binary method functions with awk-less functions by [MENTION=4544860]osm0sis[/MENTION].

New Feature - Plugin support - Add your own script to the /kitchen/tools/plugins directory and the kitchen will run it for you.

NOTE: I have created an example plugin with some variables already defined. When you run it they will be printed on screen so you can see how it works. We can add more variables from the kitchen later if we want, but for now it passes the kitchen base directory, and the project name. This way we can determine the current working rom directory. You will have these variables immediately available in your script if you use the example script as a template:

$base = /path/to/kitchen
$romdir = /path/to/kitchen/superr_projectname

All the colors and the screen clear the kitchen uses are also in the example script if you want to use them. If not you can remove them from your template :)
[SuperR Kitchen] bigrammy:
THANKS SuperR :victory:

I am really looking forward to having a play with this feature :highfive:
[SuperR Kitchen] SuperR.:
v2.0.7.4 (Donate version)

Changes:

Updated SuperSU to v2.72.

Added plugins directory to gitignore.

Updated README.md.

v1.0.7.0 (Standard version)

Changes:

Updated SuperSU to v2.72.
[SuperR Kitchen] micky387:
[Hello man.

Can you look my stock Samsung MM note edge FW please for deodexing ??

Try again and again but dont work.

https://www.androidfilehost.com/?fid=24499762636004838

Many apk and jar file wont deodex ;)

best regards
[SuperR Kitchen] skoub2:
I have installed Ubuntu on a virtualbox vm without any gui, only the command line. When i start ./superr, it ask me to install the tools but it get stock in a loop. Like stated in the 4th post, i tried to install by myself the tools. Everything is installed but the SuperR's Kitchen always tell me "One or more tools could not be built". The only hint that i have is when i start the app, i have this error message "./superr: line 7385: depinstall: Permission denied" .

I tried to search the web for this kind of error but i didn't found anything.

thank you for all your help!

skoub
[SuperR Kitchen] SuperR.:
I just deodexed the zip you posted with no errors, and everything seems in place. However, there have been many Samsung users who have had trouble with the rom booting after deodexing with the kitchen. Unfortunately at this time I do not know how to fix it.

Not sure, but it works well in Ubuntu 16.04 desktop version installed native :) You could try downloading the appropriate binaries from the Bitbucket repo and extracting them into /kitchen/tools. If you do it correctly you should not get that error anymore. Otherwise, try a different setup.
[SuperR Kitchen] micky387:
Yes ,me too. Deodex with no error but some file are corrupted. for exemple,framework.jar do 125 ko and some apk FC when boot are finish.

No problem on 511 with your kitchen . Samsung dont make life easy when new android is out...
[SuperR Kitchen] bcrichster:
When I have issues like that, it's usually related to a corrupted Linux ISO installation.. [emoji28] Check &/or reDownload the ISO then try again. I know it isn't a "quick fix" but it will help make stuff right instead. [emoji41]

Sent from a Dirty Unicorn's LolliPop! N9515
[SuperR Kitchen] SuperR.:
v2.0.7.5 (Donate version)

Changes:

Fixed allowing you to run a plugin if there is no project selected.

Fixed Misc Tools menu to show no ROM instead of what the Main menu says when there is no ROM extracted.

Removed kitchen base directory arg from plugin command as it is not needed.

Fixed terminal background colors.

Updated the example plugin to reflect color and arg changes.

v1.0.7.1 (Standard version)

Changes:

Fixed terminal background colors.
[SuperR Kitchen] SuperR.:
v2.0.7.6 (Donate version)

Changes:

Plugin scripts must now be in a directory named the same as the plugin script.

New plugdir variable in example script.

NOTE: This update is big news for the plugin movement :) Having a dedicated directory for each plugin and a variable that defines the plugin directory allows developers to easily integrate existing tools into the kitchen plugin system. Inside the plugin directory for example, you could have more directories, binaries, and other scripts that are run from the plugin directory independent of the kitchen. Once the script exits you will be right back in the kitchen :)

NOTE2: Sorry for the overload of updates lately :p
[SuperR Kitchen] Er. Aditya:
NOTE2: Sorry for the overload of updates lately

u must be kidding man , thanks amillion , though i still havnt tested this feature but awesome
[SuperR Kitchen] bcrichster:
You're good man, progress is Beautiful!! [emoji41]

Sent a PM in AF

Sent from a Dirty Unicorn's LolliPop! N9515
[SuperR Kitchen] bigrammy:
This far far exceeds my request and expectation. :cool:

Lets hope I and others can make some meaningful kitchen/plugin contributions. :fingers-crossed:

This will be pretty slow on my part though as I have just spent 8 hours trying to make my plugin "look nice" & add a simple "Choice menu" and you have updated the kitchen twice while I was messing around :laugh:

This latest update means I will now have to do some more studying reading and goggling on bash script. :cowboy:

Massive Thanks SuperR. :highfive:
[SuperR Kitchen] :
I'm pretty certain you will add some exceptional plugins. Truly one of the nicest guys on xda, always helping us lesser Linux mortals
[SuperR Kitchen] bigrammy:
Thanks for the kind words and vote of confidence sawdoctor :o

Trust me I class myself as "total dork" on Linux :crying:

As for bash script I seem to take 1 step forward and 10 backwards which gets very frustrating but I will do the best I can. :fingers-crossed:
[SuperR Kitchen] skoub2:
I think my problem was that i had downloaded the git source with the sudo command. It now work!
[SuperR Kitchen] skoub2:
Hi everyone! When i want to extract the system.img, i get this error. How can i solve that?
[SuperR Kitchen] SuperR.:
Our first Plugin :)

Nexus DL

Features:

Choose a Nexus device from a list.

Download the newest firmware.

Copy it to your ROM directory for extraction.

Usage:

Download the plugin attached below

extract to /kitchen/tools/plugins

In the kitchen main menu, choose Misc Tools > Run a plugin > nexus_dl

Enjoy :)

NOTE: This plugin can help with learning how plugins work so if you are interested have a look :) I will be making more plugins in the near future and will find a way to organize them.
[SuperR Kitchen] störte:
Wow you are amazing.
[SuperR Kitchen] davidmueller13:
For the donate version: david.mueller1013 is my Gitlab username
[SuperR Kitchen] nightcervant:
Hello , first of all I wanted to thank you for your wonderful tool , but a couple of days I have this problem :

how do I fix ?
[SuperR Kitchen] SuperR.:
Probably an internet issue in your terminal, or Bitbucket is down when you try to update. Nothing I can do about either on this end.
[SuperR Kitchen] nightcervant:
Internet on my terminal works (I'm writing right now from there) the problem has gone on for a couple of days already, I can not get around it? The donation version has the same problem?

EDIT : Now work, i have delete tools and re install
[SuperR Kitchen] Er. Aditya:
Bro I am on 6.0.1 MM note 4 I added init.d support via kitchen but when I tested it ...it dsnt work
[SuperR Kitchen] SuperR.:
I have no idea what that app tests. Try adding a script and see if it runs
[SuperR Kitchen] Er. Aditya:
Took the script from here

http://xdaforums.com/showthread.php?t=1933849

Tested and don't work
[SuperR Kitchen] SuperR.:
Honestly I have not used init.d for quite a while. There may be some things that need to change for newer roms but I am not sure what. If you find another Linux tool that does the job properly you/I can create a plugin for it. Or if you find a Linux universal init.d tutorial that works on all roms I will take a look to see if there is something new I need to add. Aside from that you are on your own with this one :)
[SuperR Kitchen] skoub2:
I've solved my problem. It's because i had previously uncompressed the system.img_sparsechunk.0 files to have the full system.img. I thought it was the way to go since that the app ask for the system.img file.

So now, i'm using the system.img_sparsechunk.0 files directly and the extract can do his job without any problem.
[SuperR Kitchen] osm0sis:
Probably everyone should just use su.d since they're likely rooted with SuperSU anyway. :)
[SuperR Kitchen] Er. Aditya:
thankyou sir , so we can use su.d instead of init.d both serve the same purpose ?
[SuperR Kitchen] osm0sis:
Yup! And su.d is built into SuperSU so far more reliable across devices than most init.d mods. :)
[SuperR Kitchen] JochenP:
Hello SuperR,

i've today tested to manually de/compile with success:

jogy@ubuntu:~/Schreibtisch/superrs-kitchen2/tools/smali/apktool$ ./apktool if framework-res.apk

I: Framework installed to: /home/jogy/apktool/framework/1.apk

DECOMPILING:

jogy@ubuntu:~/Schreibtisch/superrs-kitchen2/tools/smali/apktool$ ./apktool d SystemUI.apk

I: Using Apktool 2.1.1-77d245-SNAPSHOT on SystemUI.apk

I: Loading resource table...

I: Decoding AndroidManifest.xml with resources...

I: Loading resource table from file: /home/jogy/apktool/framework/1.apk

I: Regular manifest package...

I: Decoding file-resources...

I: Decoding values */* XMLs...

I: Baksmaling classes.dex...

I: Copying assets and libs...

I: Copying unknown files...

I: Copying original files...

COMPILING:

jogy@ubuntu:~/Schreibtisch/superrs-kitchen2/tools/smali/apktool$ ./apktool b SystemUI

I: Using Apktool 2.1.1-77d245-SNAPSHOT

I: Checking whether sources has changed...

I: Smaling smali folder into classes.dex...

I: Checking whether resources has changed...

I: Building resources...

W: warning: string 'notifications_off_text' has no default translation.

W: warning: string 'notifications_off_title' has no default translation.

I: Building apk file...

I: Copying unknown files/dir...

jogy@ubuntu:~/Schreibtisch/superrs-kitchen2/tools/smali/apktool$

Please take a look and check what cause the issue when running apktool from kitchen - thank you
[SuperR Kitchen] SuperR.:
Looks like you only installed framework-res.apk before decompiling. You mentioned that you need to also install htc framework apks so the kitchen installs all framework apks, not just framework-res.apk. Not sure if that is the cause of the issue but if you send a link to the firmware you are using I will check it out.
[SuperR Kitchen] The Sickness:
Those warnings are obsolete. If it builds the apk then it's fine.
[SuperR Kitchen] SuperR.:
The thing that is interesting , is that he is using the apktool from the kitchen in both cases. When he uses the kitchen to decompile the apk he gets errors. When he decompiles manually using the exact same apktool and files he does not get errors. So far I am not understanding what is going on and I don't think I will without getting a hold of the files he is using.
[SuperR Kitchen] JochenP:
Here is the link : https://www.androidfilehost.com/?fid=24438995911967705
[SuperR Kitchen] hamed24:
Hi [MENTION=5787964]SuperR.[/MENTION] I read cygwin guide but I confused, I want use you're tools on windows 7 32bit and I don't know start where!!? and can I use your tools in offline mode,is it necessary internet connection always??

Thanks man for your amazing tool

sent from Xperia™ SP | Android 6.0.1
[SuperR Kitchen] bcrichster:
Need to upgrade to 64 bit to get full function, sorry.. [emoji28]

Sent from a Dirty Unicorn's LolliPop! N9515
[SuperR Kitchen] SuperR.:
v2.0.7.7 (Donate version)

Changes:

Removed apktools from main kitchen in favor of a plugin.

New plugin repo found here:

http://xdaforums.com/showpost.php?p=62845968&postcount=5

I have added all members of the donate version to this repo.

NOTE: I have fixed de/compile apk feature in the new plugin found at the repo above. The problem was that when the kitchen installed the framework apks it did not do it in the correct order.

Along with the new Apktools plugin, we also have a new RUU Decrypt plugin by [MENTION=1162986]Captain_Throwback[/MENTION] and [MENTION=2605798]nkk71[/MENTION] :)
[SuperR Kitchen] andy_zhang:
Delete

vs985 China user
[SuperR Kitchen] hamed24:
Thanks for replay,and I should always connected internet during use this tools

sent from Xperia™ SP | Android 6.0.1
[SuperR Kitchen] shoey63:
Where does it say you must always remain connected?

Also, you have basically no hope of running the tool on a 32 bit windows installation with cygwin.

Use Linux.
[SuperR Kitchen] Tk23:
For donate version my gitlab name Tk23
[SuperR Kitchen] civato:
donation

Hello m8

Donation Confirmation Number: 6J168820ME786943G via paypall 20$

My Gitlab ussername is "civato"
[SuperR Kitchen] joni2012:
Thank for this program. It is excellent

Team SkyDragon loving
[SuperR Kitchen] JochenP:
1. apktools works without problems now :good: but there is an error with the generated parth:

kitchen outputs old path ' ./superrs-kitchen2/name-of-the-rom/apkwork' but you have moved it to

' ./superrs-kitchen2/tools/plugins/apktools/apkwork'

Shure that this is a good idea to put apk to pluginpath and not in the Rompath - what if i work with more than one rom at the same time? I have not tested yet to change rom during apk is decrypted....

2. please do not quit teminal in the plugin menues - i think e for end is better to return to standatd kitchen menu

Thanks
[SuperR Kitchen] SuperR.:
You are right on both accounts. I used "q = Quit plugin" and put the apkwork directory back in the rom. Thanks for the feedback :)

Download the plugins again, delete the old and extract the new.
[SuperR Kitchen] SuperR.:
test
[SuperR Kitchen] bcrichster:
So plz help me understand the changes.. I can now take an init.d script and have it install as something called an su.d?

Sent from a Dirty Unicorn's LolliPop! N9515
[SuperR Kitchen] SuperR.:
I have not done anything to the kitchen regarding su.d yet. However, I am pretty sure it is very easy to set up. If I understand correctly, all you need to do is create a directory /system/su.d and put your scripts in it. When you flash SuperSU it does what it needs to do with that directory and those files. If someone knows differently please correct me as I have never used su.d. If su.d is the way to go, I will update the kitchen replacing init.d with su.d :)
[SuperR Kitchen] bcrichster:
Would that eliminate kernel modifications or No?

Hmm.. Throw me a PM and I'll use my Sync as a safe control test.. [emoji41]

Sent from a Dirty Unicorn's LolliPop! N9515
[SuperR Kitchen] Er. Aditya:
why not having both options ? initd or su.d
[SuperR Kitchen] SuperR.:
You can easily give it a try if you are running SuperSU. You can even do it in a root file manager. Create a directory /system/su.d and add a script. Reboot your device and see if it runs :)

I misspoke, both options are fine :)
[SuperR Kitchen] bcrichster:
What perms would should I give them.. Same as init.d?

Sent from a Dirty Unicorn's LolliPop! N9515
[SuperR Kitchen] Captain_Throwback:
I've actually suggested this before ;).

More info (including proper perms) here: http://su.chainfire.eu/#selinux-policies-supolicy
[SuperR Kitchen] Er. Aditya:
nothing less to be expected from the magician
[SuperR Kitchen] SuperR.:
New plugin - Carliv Image Kitchen by [MENTION=5186178]carliv[/MENTION]

You will find the download and installation/usage instructions in the new plugins repo on post #5

You will need to visit [MENTION=5186178]carliv[/MENTION] thread to get the latest copy of Carliv Image kitchen. Make sure to thank him for his work while you are there :)
[SuperR Kitchen] SuperR.:
v2.0.7.8 (Donate version)

Changes:

Added su.d support.

v1.0.7.2 (Standard version)

Changes:

Added su.d support.

edit: I am reconsidering where the su.d option is. Currently it is in the same place as init.d, but we don't need to do any kernel mods for su.d so it seems like a waste to unpack/repack boot.img. Expect another update soon lol
[SuperR Kitchen] bcrichster:
How about option for both / either, for in case one method doesn't work correctly we can use the other..??

Sent from a Dirty Unicorn's LolliPop! N9515
[SuperR Kitchen] SuperR.:
v2.0.7.9 (Donate version)

Changes:

Added Root Menu to ROM Tools.

Moved su.d from Boot Tools to the Root Menu.

Moved root and busybox add/remove to the Root Menu.

v1.0.7.3 (Standard version)

Changes:

Added Root Menu to ROM Tools.

Moved su.d from Boot Tools to the Root Menu.

Moved root and busybox add/remove to the Root Menu.

[MENTION=5297774]bcrichster[/MENTION] - Both options are still there :)