yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] Captain_Throwback:
[MENTION=5787964]SuperR.[/MENTION]

Actually I have a similar request. Can you allow us to add custom folders to the setup, that will automatically get included in the ROM zip? For example, when I included Xposed in my ROM, I had the necessary files in a folder called xposed, and manually added the necessary section to the updater-script. However when building the ROM, that folder would never get included. I ran into a similar issue when trying to include phh's Superuser in a build instead of SuperSU. There must be a way to add custom folders to get included in the ROM zip?

I agree that this would be a great feature.
[SuperR Kitchen] SuperR.:
This is possible, as long as /sdcard is a symlink to wherever it actually is. This directory name changes per device so without the /sdcard symlink I would not know where to copy the files. Most devices have it, but I have run into several that use other naming conventions.

This is possible, but only for zips that use an update-binary script like SuperSU and Busybox.

Where would you want the custom directories to be extracted on the device? In the updater-script you would just do something like:

package_extract_dir("custom_dir", "/wherever/you/want");
[SuperR Kitchen] blueberry60:
[MENTION=5787964]SuperR.[/MENTION]

I couldn't find 1.0.6.0 version download link.Could you possibly to upload this file ?
[SuperR Kitchen] Captain_Throwback:
Well in the case of my "xposed" folder, it extracts to /system. I have it separated out so it's easy to include xposed (or other mods) in future zips without touching the ROM base. This is especially helpful for ROMs that use AROMA or that only have minor updates to the base (like monthly security updates). So I can keep my mods in a single folder while leaving the base untouched.

But allowing the custom extract folder to be configurable would also be nice, as it would also meet the need of the /sdcard folder for apps to be extracted there, if desired.
[SuperR Kitchen] SuperR.:
v1.0.6.6 (Standard version)

Changes:

Added ability to extract rom zips created with the new update-binary method.

Fixed an issue where the kitchen might close occasionally when you first start it.

v2.0.6.7 (Donate version)

Changes:

Added ability to extract rom zips created with the new update-binary method.

Function changes for the update-binary script to allow two arguments instead of one for package_extract_dir.

New Feature - Custom directory to be flashed with the rom zip and extracted where you choose.
[SuperR Kitchen] Er. Aditya:
cant appreciate more of your amazing hard work , thanks a million mate
[SuperR Kitchen] bcrichster:
Wow! Ok Bro.. Where u staying @? [emoji41] I may be going on a vacation next month and may need to come by & shake your hand a million times for everything you've done. Damn great work! Ur "Tha Mann!!"

Sent from a Dirty Unicorn's LolliPop! N9515
[SuperR Kitchen] Romm_:
Help me, please. I want to try SuperR's Kitchen, but when I start it on Ubuntu 16 (WMware Workstation on Widows 10) as ./superr - permission denied.

When I try:

bash superr

- superr: line 1776: /home/romm/Desktop/superr-kitchen/tools/source/img_tools/extras/chkstatd: Permission denied.

How I can start SuperR's Kitchen? What I must do with chkstatd?
[SuperR Kitchen] SuperR.:
Start it just like the OP says.

cd /path/to/kitchen
./superr
[SuperR Kitchen] Romm_:
I started same it:

cd /home/romm/Desktop/superr-kitchen

./superr

and have "permission denied"
[SuperR Kitchen] SuperR.:
Sounds like an issue with your setup. There are hundreds of people using this kitchen without issues. You could try VirtualBox, or the best option is native Linux :)
[SuperR Kitchen] Romm_:
I reinstalled Linux and SuperR's Kitchen works. Thank you!
[SuperR Kitchen] tdunham:
I'm stuck at the jre java check, I still get the missing dependency.

At first attempt it looked like it downloaded and was applying but now it just keeps coming to 'You need at least Java 8 to use this kitchen.'

Edit:

Had to manually update to current version using a guide I found (I'm a little Ubuntu challenged ;) ).

Just wanted to report the problem I had updating java with the kitchen.
[SuperR Kitchen] glennsamuel32:
Wow...never had this before :)

Created a new VM and it works fine :)
[SuperR Kitchen] raulx222:
When building the ROM, in /system folder is generated an empty file (named like "sedMmA6BA" with no read no write properties)..also this file is included in the ROM zip. Does this file have a purpose?

EDIT: Also when packing an bigger ROM using set_metadata the packing process hangs.
[SuperR Kitchen] Lightn1ng:
Very easy to use, but some of the wording could be a bit more simple (what do you mean "build boot flashable??")
[SuperR Kitchen] SuperR.:
I have no idea what the sedMmA6BA file is. I have never seen or heard of it.

There may be a file in your rom that can't be zipped due to file permissions so it hangs. You can check the zip log to see where it is hanging. If it always hangs at the same place check the permissions of the file.

Build a flashable boot.img zip
[SuperR Kitchen] raulx222:
Every time when I start building my ROM, a file with a random name(but first 3 letters are always "sed") is generated. I tried to clear everything an decompress again the firmware zip and build the ROM again, that random file is still generated. Also I tried to decompress and build a CyanogenMod and that random file was NOT generated.

Here's a SS: http://imgur.com/eMUIi4w

As base I'm using this firmware: http://downloads.oneplus.net/2016-04-20/opx/OnePlus_X_OxygenOS_2.2.1-X/

You should be able to reproduce my issue using it since it occurs only with it.

EDIT: That file is generated between zipalign and system partition detection. After the zipaling was done, the file was generated.
[SuperR Kitchen] Lightn1ng:
Alright I've run into an issue.

I tried debloating my ROM manually (by deleting files in superr-supernova/system/app and superr-supernova/system/priv-app) and built it, and it won't flash. Upon further inspection, the updater-script is trying to package_extract the system folder from the ZIP into /system, but the ZIP does not contain /system, only image files!

Either I have made a stupid mistake or this is a bug. Thinking the former is more likely.

Any help?
[SuperR Kitchen] SuperR.:
Thanks for the link and info. I will check it out.

Please describe the steps you took in the kitchen. What options did you choose?
[SuperR Kitchen] Lightn1ng:
I found the problem. I accidentally chose custom zip. Solved by recreating the ROM completely. Thanks.

---------- Post added at 01:02 PM ---------- Previous post was at 12:43 PM ----------

Just to confirm, I am allowed to remove the SuperR kitchen branding from the updater-script, right?
[SuperR Kitchen] SuperR.:
v2.0.6.8 (Donate version)

Changes:

Fixed device name not being found on OnePlus.

Fixed by-name from boot.img not being detected on OnePlus.

v1.0.6.7 (Standard version)

Changes:

Fixed device name not being found on OnePlus.

Fixed by-name from boot.img not being detected on OnePlus.

[MENTION=4964524]raulx222[/MENTION] - There were several issues, all fixed now. I did not ever get the sedxxxx file probably because I fixed the above before trying a build. I am pretty sure that sedxxxx file was also causing your build to hang. Hopefully all is good now :)
[SuperR Kitchen] Lightn1ng:
Other post was confusing, so I will put it this way:

Am I allowed to, using the standard version, remove the "built.with.superr.kitchen" from the about device using my own method? Or should I put "Supernova ROM built with Superr's kitchen"
[SuperR Kitchen] raulx222:
I've reinstalled the whole kitchen, that file still appears :/. How weird.
[SuperR Kitchen] nowheel:
there is a error with stock rom by samsung in system.img.ext4, include in your script, after unzip the stock rom, the reneame of system.img.ext4 in system.img
[SuperR Kitchen] SuperR.:
If I wanted my credit for all the hard work I have done on this kitchen removed, I would not have added it in the first place. If I were in your position, I would want to support the developer either by keeping his credits, or by donating.

How are you choosing to get your by-name directory? I chose to get it from the boot.img. What is inside the /kitchen/tools/devices/OnePlus/superr_byname file?

The kitchen should be renaming system.img.ext4 to system.img. Please post the firmware so I can have a look.
[SuperR Kitchen] Lightn1ng:
I did the former.
[SuperR Kitchen] SuperR.:
v1.0.6.8 (Standard version)

Changes:

Fixed the random sedxxxx file appearing when building rom zip on OnePlus.

[MENTION=4964524]raulx222[/MENTION] - Never mind on my last post. I fixed the issue :)
[SuperR Kitchen] AbA2L:
hello, this kitchen version is it compatible with my HTC OneM8_UL_CA?
[SuperR Kitchen] SuperR.:
Most things will work on most devices. I am pretty sure the M8 has been tested.
[SuperR Kitchen] AbA2L:
ok thinks guy :)
[SuperR Kitchen] sebastiandg7:
[MENTION=5787964]SuperR.[/MENTION] man, not mostly a bug but you may want to fix it:

When deodexing 6.0.1 CM13 (With both methods) it appears this:

----------------------------------------------------

Start deodexing /system/framework ...

----------------------------------------------------

/home/sduque/Downloads/Android/superr-superrs-kitchen-4c9374c4ed63/superr: line 3587: cd: /home/sduque/Downloads/Android/superr-superrs-kitchen-4c9374c4ed63/superr_Others/system/framework/oat/arm: No such file or directory

You should validate if the directory exists ( [[ -d $framedir/oat/$arch ]] or whatever you want to do it) before the 'cd' command.
[SuperR Kitchen] cebs:
[MENTION=718594]superR[/MENTION] if you could add decompile/compile apk feature to your kitchen it would be really awesome ??
[SuperR Kitchen] bcrichster:
I tried asking that in the beginning but he's actually got his hands a bit overloaded with everything the kitchen already does.. Plus, decompiling apps is an extensive process of upkeep and changes. That would give him more questions than it would be fair to deal with, much of which won't be his fault as someone else builds the deodexing jars

Sent from a Dirty Unicorn's LolliPop! N9515
[SuperR Kitchen] SuperR.:
Please link the firmware you are using so I can have a look. Thanks

[MENTION=1360974]cebs[/MENTION] and [MENTION=5297774]bcrichster[/MENTION] - There might be a surprise soon :)
[SuperR Kitchen] Er. Aditya:
f5 f5 f5 ... :D:highfive::silly::eek:
[SuperR Kitchen] bcrichster:
[emoji41] [emoji86] [emoji87] Whoo!! Awesome! [emoji16]

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

Changes:

New Feature - Ability to choose an apk, decompile, modify it manually, recompile, sign, and move it back to where it came from.

NOTE: Please keep in mind that I will not support smali edits, app fc's, or anything else other than making sure the kitchen does its job decompiling/recompiling/signing/moving the apks. Thanks for understanding :)
[SuperR Kitchen] bcrichster:
Whoo-Hoo!

Sent from a Dirty Unicorn's LolliPop! N9515
[SuperR Kitchen] The Sickness:
Boy, you just opened up a big can of worms lol....
[SuperR Kitchen] bcrichster:
Deleted. No intention of disrespect to anyone, only props.

Sent from a Dirty Unicorn's LolliPop! N9515
[SuperR Kitchen] fhem:
This kitchen and [MENTION=5787964]SuperR.[/MENTION] are the very very best but I feel like I'm missing something here????? It will definately open a big can of worms.
[SuperR Kitchen] cebs:
Whhoowwwww... Thank you so much ??
[SuperR Kitchen] SuperR.:
The apktool in the kitchen is the newest dirty version. I compiled it from source today. There should not be many worms in the can. I will only support what the kitchen is responsible for. All apktool issues still need to be directed somewhere else :)
[SuperR Kitchen] fhem:
It was just a heads-up for you. I follow that thread and have used that tool quite a bit. I also know [MENTION=3924617]iBotPeaches[/MENTION] fields many, many problems/issues maintaining that tool. I just don't want to see your thread get bogged down with those issues. I very much respect the effort and support you both provide to this community.

Thanks again and please keep it going.
[SuperR Kitchen] SuperR.:
v2.0.7.0 (Donate version)

Changes:

Install all framework apk files with apktool each time we de/compile instead of just framework-res.apk.

Remove all installed framework files when finished so we don't accidentally use the wrong framework.
[SuperR Kitchen] tdunham:
Dirty version?

2.1.1 official was posted by ibotpeaches 2 or 3 days ago, in case you missed it.

[UTIL][May 7 2016] Apktool v2.1.1 - a tool for reverse engineering apk files
[SuperR Kitchen] SuperR.:
The kitchen has exactly 2.1.1 since it was compiled today and there have not been any commits since 2.1.1 was released :)

edit: FYI, it is just as easy to swap apktool.jar as it is to swap everything else in this kitchen so feel free to use any version you want.
[SuperR Kitchen] Danvdh:
Long time no talk SuperR

PM sent to you in regards to donation access

cheers!
[SuperR Kitchen] JochenP:
v2.0.7.0

minor bug in '5) Asserts Menu':

if i cancel action with 'm'-key then 'CURRENT' clears and disappears in 'ROM Tools Menu'

Edit 1: signing within apktool does not work for me. My HTC A9 is ignoring these files so i have to copy, for example, 'classes.dex' within 7zip (pached to original file). Is there anyone who has success with apk-signing?
[SuperR Kitchen] bcrichster:
PM's are shut down

Sent from a Dirty Unicorn's LolliPop! N9515
[SuperR Kitchen] störte:
Send you a donation. Thanks for your hard work

Gitlab username stoerte
[SuperR Kitchen] :
Can we install systemui as well as framework apks? I know it can help with Samsung roms. Thanks again for another great feature
[SuperR Kitchen] SuperR.:
v2.0.7.1 (Donate version)

Changes:

SystemUI.apk will now be installed with apktool before de/compiling apk.

Fixed assert issues.

Removed current assert display from ROM Tools.

Added device assert display to the Asserts menu.

Added custom assert display to Asserts menu.

Added ROM Tools menu option to Asserts menu.

Changing asserts will now return you to the Asserts menu instead of ROM Tools menu.

v1.0.6.9 (Standard version)

Changes:

Fixed assert issues.

Removed current assert display from ROM Tools.

Added device assert display to the Asserts menu.

Added custom assert display to Asserts menu.

Added ROM Tools menu option to Asserts menu.

Changing asserts will now return you to the Asserts menu instead of ROM Tools menu.
[SuperR Kitchen] SuperR.:
It has been a while. Hope you are doing well. I added you to the private repo, thanks for the support :)

The asserts should be fixed now.

If there is a general consensus on this, I am happy to change it. It can be done a few ways, but would like to know the general best practice as I have not modified apk files in a while lol. Options are (as far as I know):

1. sign apk as the kitchen does now

2. copy classes.dex and resources.arsc from new apk into original apk

3. copy META-INF directory from original apk into new apk

You have been added. Thanks :)

Added in latest version :)
[SuperR Kitchen] SuperR.:
v2.0.7.2 (Donate version)

Changes:

Added signing options when recompiling apk - use signapk.jar, copy META-INF from original apk to the new apk, or copy classes.dex and resources.arsc from new apk to original apk.

edit: Let me know if there are other options I need to add. These are the only ones I know about but we can add as many as we need :)
[SuperR Kitchen] JochenP:
It would be a good idea to choose option when going to rebuild an apk. :good:

During framework installation the apktool/framework/ folder remains empty and therefore occur exceptions

Installing the correct framework is in my case HTC specific - framework files location differs:

/system/framework/framework-res.apk and /system/framework/framework-res-htc/framework-res-htc.apk

HTC, Samsung, Sony etc. uses their own framework and for decompiling manufactorer apks it is required.

So if i want to use this function i have first to point these two files.

Thank you

P.S. is it possible to store username and pass to update directly?
[SuperR Kitchen] SuperR.:
The latest version should work for you. It installs ALL apk files located in /system/framework with apktool regardless of their name. It also gives you the options you were requesting above. I guess you did not see that I pushed another update before you posted :)

You can store the password if you are sure it is secure. It will be stored in a plain text file so anyone that has access to your machine can read it if they want. Here is how.

1. Open the file /kitchen/.git/config.

2. Edit this:

[remote "origin"]
url = https://gitlab.com/superr/superrs-kitchen2.git

to this:

[remote "origin"]
url = https://username:password@gitlab.com/superr/superrs-kitchen2.git

3. Save file

4. Enjoy :)

edit: The /home/user/apktool/framework directory is cleaned out immediately after de/compliling the apk. I did this to avoid using the wrong framework if you change roms etc. It is not remaining empty during the framework installation.
[SuperR Kitchen] baloo30310@gmail.com:
Update

Hy !! from my Version 1.0.46 impossible to put the kitchen in updates .:crying:

sorry for my english I'm french !!:D
[SuperR Kitchen] SuperR.:
A lot has changed since then. You will need to do a fresh install. Instructions are in the OP. After that you will be able to use the kitchen updater again :)
[SuperR Kitchen] fhem:
The two I personally use the most are: apktool options

apktool d -s <name.apk>
apktool b -c <name>

My smali sux. :D:good: although it's about as good as my java haahh :confused:
[SuperR Kitchen] baloo30310@gmail.com:
what's the op into indiscretion ?

and above all this or is there if you like it ..:crying:
[SuperR Kitchen] hohassan444:
[MENTION=718594]super[/MENTION]R ,please help me,I cannot built ROM using set_metadata or sparse_DAT...give me error ( your kernel don't support selinux . please use normal ROM zip)...I use ubuntu 15 64bit
[SuperR Kitchen] SuperR.:
It says that because your boot.img does not contain a file_contexts file. set_perm should be sufficient.
[SuperR Kitchen] hohassan444:
Thanks for reply....but with with that option, it gives me error during install...some symlinks fail. In addition I see many cwm flashable zip posted on forums ( based on my stock ROM) use set_metadata and sparse_DAT .

NB ..I have mtk 6752 device...lollipop 5.1
[SuperR Kitchen] fhem:
Thanks for the changes --- the M/6.0 deodex seems to be working. I haven't tried flashing N6 M3 preview deodex rom yet. I will let you know how that works.
[SuperR Kitchen] SuperR.:
Please link me to the files you are starting with so I can have a look.
[SuperR Kitchen] edzamber:
Hi,

First many thanks for this great work :)

Just a question : does it or will be compatible with Cygwin for Windows ?

Many thanks :)
[SuperR Kitchen] SuperR.:
I have no idea if it will work with cygwin, and I will not be making a Windows version. If you get it working in cygwin, please post a guide :)
[SuperR Kitchen] edzamber:
Thanks [MENTION=5787964]SuperR.[/MENTION] for your answer :)

Testing and report :)

Edit :

Its runs [emoji6]

Go to test functions now ;)

---------- Post added at 06:15 PM ---------- Previous post was at 05:39 PM ----------

Option 4 not working, message : system folder missing.

I have past system.img.ext4 and cache.img.ext4 into my Name_superr folder...
[SuperR Kitchen] sefrcoko:
Thanks for your help, yes I used the latest kitchen to deodex but your reply made me think to try again and take a closer look for errors. Seems like most apps deodexed fine but a few had java heap exception errors. Made me think it was a memory issue, so i checked my virtualbox setup and found that i had only allocated 512mb of ram lol. I increased that to 2gb and ran the kitchen again. No more deodex errors and the rom now boots! Thanks again :)

---------- Post added at 12:39 PM ---------- Previous post was at 12:33 PM ----------

Yes I actually had that issue as well.
[SuperR Kitchen] edzamber:
Ok :)

Thanks ;)

Trying like that :)

Anyway it seems to works with Cygwin...

I had to install p7zip package for Cygwin then kitchen loaded :)
[SuperR Kitchen] hohassan444:
[/COLOR]

thanks again ;

http://www.needrom.com/download/17-09-android-5-1-for-the-jiayu-s3/
[SuperR Kitchen] SuperR.:
It requires login, and I will not sign up. Any other link?
[SuperR Kitchen] bcrichster:
[emoji317] Hahahahah! [emoji322] Got it kickin' with Cygwin!! [emoji335] Sweet [emoji56] Rock on! [emoji450]
[SuperR Kitchen] hohassan444:
spflash version

https://mega.nz/#!OVhUHYzB!68RWYhZPH-TtcUQLoIfXc0exAZuFbh8ll-hmK6tI6lA

Recovery version

https://drive.google.com/file/d/0B4G2ME5qKczxNmhXYXBQWVVRcUk/view?usp=sharing
[SuperR Kitchen] Dior DNA:
Great tool!

Perhaps you can add support for extra (configurable) directories.

I have a ROM with a /system/plugin directory containing apk files to deodex.
[SuperR Kitchen] SuperR.:
I am going to redo this part of all the deodex tools at some point, but for now system/plugin is already supported when deodexing as well as /system/vendor/app.
[SuperR Kitchen] mcqaissi:
hi

i have this problem

elabel u:object_r:su_exec:s0

>> WARNING: Command "set_metadata" not recognized by script

446/452: show_progress 0.020000 10

447/452: run_program PACKAGE:tmp/install/bin/backuptool.sh restore

>> WARNING: tmp/install/bin/backuptool.sh not found in working folder

448/452: show_progress 0.050000 5

449/452: set_perm 0 0 06755 SYSTEM:xbin/su

450/452: symlink /system/xbin/su SYSTEM:bin/su

451/452: write_raw_image PACKAGE:boot.img BOOT:

452/452: show_progress 0.200000 10

108 issue(s) found. Please review the update-script to ensure it is correct.

Number of symlink conflicts resolved: 2

need help pleas
[SuperR Kitchen] Dior DNA:
perfect then
[SuperR Kitchen] SuperR.:
v0.9.1.2

Changes:

Added support for MTK boot/recovery img thanks to [MENTION=455439]bgcngm[/MENTION] for MTK-Tools.

Fixed a couple typos in deodex scripts

[MENTION=4355438]hohassan444[/MENTION] - This should sort out your problem :)
[SuperR Kitchen] reefuge:
just reporting my findings for Motorola G 2014 2nd gen (xt1068) dual sim

sparse .dat not working so using metadata method makes a flashable rom tried deodexing , debloating , rooting , user apps etc this all seems to work ok

always have to rename titan_umtsds to titan or add ,titan to allow rom to flash

So it seems making rom via kitchen works 99% but one problem is the Wifi on the rom made by kitchen- rom flashes ok but on set up even though wifi sets up accepts passkey and obtains ip address, it never locks and allows me to proceed further - I have to skip wifi setup and use sim(s) to finish setup

if you could fix this i would say working for moto g 2nd gen

absolutely no rush or if more info needed please contact me- really impressed with your effort and updates so far:D