yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] SuperR.:
That is quite a list of apps you have there, and they are all repeated in app and priv-app. It may help if you look for the apps in your ROM so you know what to remove as I am sure you don't have YouTube in both app and priv-app. Also take a look in vendor/app and other sneaky places they like to hide apps you don't want.

If you send your boot.img and build.prop I will take a look.
[SuperR Kitchen] celoxocis:
thanks! here are both files: https://drive.google.com/open?id=0B0bAICq7NVq1OWxwNnV1ZzNrWm8
[SuperR Kitchen] hohassan444:
[MENTION=5787964]SuperR.[/MENTION]..please can you give a look into this system.img....this for lenovo k4 note lollipop.

as the kitchen is unable to extract it and gives empty system folder.

https://cloud.mail.ru/public/2RJ5/s8iUhuRph
[SuperR Kitchen] Has.007:
[MENTION=5787964]SuperR.[/MENTION] Thanks sir for this amazing tool, so far so good! I just have one query it might be dumb but I'm new to your kitchen nd I couldn't find the option to Zipalign the ROM. So can you guide me please.

Thanks. :)
[SuperR Kitchen] JochenP:
If you install a debloated rom these apps stays in app and priv-app folder (device). Rom install will not delete, only overwrite anything (device). You have to delete those apps manually on your device
[SuperR Kitchen] Er. Aditya:
At thr final stage before repacking the rom it will ask you to ziplign

you sure bro ??
[SuperR Kitchen] SuperR.:
You are correct. There is no dt.img in that boot.img. That does not mean you can't build TWRP though :)

I have no idea how to unpack that system.img. It is not standard, possibly encrypted. If you find a way to unpack it in Linux let me know.

As mentioned by [MENTION=5750672]Er. Aditya[/MENTION] you will be asked if you want to zipalign when you build your rom if it is deodexed.
[SuperR Kitchen] bcrichster:
Yes, very sure. Not sure if VIP status is required (as I have, from purchasing the paid Tapatalk back in the day) but I brought the same information to [MENTION=5787964]SuperR.[/MENTION]'s attention for the same purposes. [emoji6]

Sent from CM12.1 *N9515*
[SuperR Kitchen] holofractal:
Did you ever find a version that works? Also I can't seem to find 1.0.2.5 anymore.
[SuperR Kitchen] JochenP:
that version (1.025) was a little buggy.

Kitchen version 1.033 works fine. Since version 1.068 i'm using the donate version and now i'm happy :good:

---------- Post added at 10:59 AM ---------- Previous post was at 10:06 AM ----------

Hi,

corresponding output is in #AROMA section:

if file_getprop("/tmp/aroma/mods.prop","item.0.3") == "0" then
delete_recursive("/system/priv-app/Instagram_SN_Plugin");

that seems correct but rom won't flash :eek:

Now testing with Aroma 2.70RC2... same - still no luck
[SuperR Kitchen] Has.007:
Thanks to you nd [MENTION=1382603]Er.[/MENTION]Aditya for quick replies. :)

But now I'm getting a new problem, I'm using Ubuntu 14.04 32bit. I deodexed the ROM nd everything went well, I even zipaligned the ROM nd framework. But when I flash the ROM it is just stuck on the boot animation.

Just to let you know, I got some error in the deodexing of Maps nd services.jar. I guess it was that the classes.dex was not found.

Also when I made a signed zip, All I could find was the non signed zip nd the signed zip was 0 bytes.

Thanks for your help, means alot. :)
[SuperR Kitchen] SuperR.:
Can you link me to an Aroma ROM that works? Maybe I will be able to see some difference that will help. I have never used Aroma so I am clueless about how to get it working.

services.jar is important so if you had errors your ROM will probably not work. Why are you deodexing? Do you plan to modify apk files? If not, don't deodex and problem solved. Otherwise, you can try another tool for deodexing as several devices seem to have issues with the kitchen methods. Several people have said SVA Deodexer is good but it is only for Windows so I have not used it. It is also possible that zipaligning the framework apks causes issues so you could try without that as well.

You probably ran out of ram when signing your zip. Signing is just an extra protection, so you can skip it if your pc does not do it properly.
[SuperR Kitchen] :
[MENTION=5787964]SuperR.[/MENTION]

Aroma ROM that works.

https://www.androidfilehost.com/?fid=24352994023705971
[SuperR Kitchen] sziraqui:
[MENTION=5787964]SuperR.[/MENTION]

Thanks a ton for your tool.

As you might have noticed, I have made 5 ROMs using your kitchen, 2 for each Asus Z00L, Asus Z00T and 1 for Micromax Canvas A1 (sprout4). Except for sprout4, In all other ROMs, headphones are not detecting. ROMs were made from sparse dat of stock 5.0.2 and 6.0.1 Asus FOTAs (Zip contained file_contexts, system.new.dat, system.patch.dat, system.transfer.list files)

I have tried the following workarounds-

1. Rebuilt but used "Detect from adb" instead of "system.img" when asked for partition size

2. Rebuilt and used set_metadata instead of sparse_dat

3. Made an unmodified stock ROM from the FOTA using sparse_dat

4. Made an unmodified stock ROM from twrp backup of my Z00L device which was running stock rom and was detecting headphone.

5. Made an unmodified stock ROM from system.img (again a system.img that was detecting headphones)

One user reported that headphones were detecting using "Soundabout App" by manually forcing audio to route to hreadphones but it has to be done everytime you insert the headphone jack.

I also checked the inbuilt app that handles headphones. For Android 6.0.1, the app is "HardwareStub". It is working normally in both deodexed and unmodified ROM in the same manner as it is working on official FOTA.

I guess this issue has something to do with symlinks, maybe kitchen doesn't detect all symlinks properly?You are the dev, you know things better. I hope you can help

Link to deodexed ROM https://drive.google.com/open?id=0B74rDxjfUA2ZTmxIOW9uUXo1Vlk

Link to base ROM (stock fota) http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-21.40.1220.1615-user.zip

Link to above ROM's thread http://xdaforums.com/zenfone-2-laser/development/rom-smoothified-stock-rom-t3404050

Attached 00_project_files for the ROM above
[SuperR Kitchen] bigrammy:
On my Infocus ZM1 stock ROM's a lot of the audio and audio config stuff is contained on the hidden/custom (could be named something else) partition.

I think this is set up by a .sh script Asus may do the same sort of thing. :confused:
[SuperR Kitchen] JochenP:
if i prepare an aroma installation, after aromainstaller has finished, i expect that in /tmp/aromafiles there are type.prop and mods.prop but they do not exist.
[SuperR Kitchen] tdunham:
You mean afterwards?

The /tmp folder contents should get deleted after use as it is a temporary work folder.

If it is not, a deletion routine should be manually added to the installer-script.

Edit: That last part is just a general comment about the use of a temporary folder because we see it used in lots of different ways.

Temporary work folders should always get removed after use.
[SuperR Kitchen] JochenP:
tmp folder (temporary partition) is deleted automatically on device-reboot. I do a search after aroma-routine ends (and gives control back to twrp) from internal twrp-file-manager for these files. AOMA should not delete these files by itself
[SuperR Kitchen] tdunham:
I have been using aroma for some time and it has never been an issue for us.

Let me ask someone that may know more as I am not familiar with the purpose of leaving /tmp files would be under any circumstance. You must realize that many different scripts use the same path as temporary workspace and the files and folder always get removed as standard practice once the routine has been completed.
[SuperR Kitchen] _that:
I think debugging is the main purpose of leaving temp files alive.
[SuperR Kitchen] SuperR.:
Thanks for linking this, but I am not seeing any differences from this aroma-config/updater-script vs the ones the plugin generates.

Since you are familiar with adding Aroma manually, please look over the aroma-config and updater-script to see why it is not working. Keep in mind that I am totally ignorant about aroma. I have never flashed a rom that uses it nor added it to a rom. I followed the instructions on the Aroma thread and made the plugin do what it says. Unfortunately someone with more experience will need to help out with this.
[SuperR Kitchen] :
I'm very familiar with Aroma and use it in all my projects and I seen no issues in the script. Its weird how it doesn't recognize 'set_metadata'.
[SuperR Kitchen] Captain_Throwback:
Have you tried a different update-binary-installer?
[SuperR Kitchen] tdunham:
Just for the sake of testing, I created a tmp folder in root, gave it 0755 permissions just for the heck of it and rebooted.

My touchwiz MM 6.0x build wacked it anyway so I'm at a loss for that, just thought I'd share the outcome. :rolleyes:

Edit:

Also, created a different foldername with the same result. The android OS must clean what it sees as not belonging...
[SuperR Kitchen] SuperR.:
No, is this needed? The plugin uses the update-binary-installer that is included in the Aroma package.
[SuperR Kitchen] Captain_Throwback:
Ah, that might be the problem.

You should be using the update-binary you include by default in the META-INF folder, just renamed to update-binary-installer. The one in the AROMA package might not be new enough to support the commands you're using.

I bet that'll fix it.
[SuperR Kitchen] SuperR.:
Aroma Install plugin updated :)

Changes:

Use kitchen update-binary instead of Aroma update-binary-install

Thanks [MENTION=1162986]Captain_Throwback[/MENTION] for the advise :)

edit: This is slightly misleading so to clarify, it uses the update-binary you have before running the Aroma plugin. If you have changed it then it won't be the kitchen update-binary.
[SuperR Kitchen] JochenP:
AROMA installer works now :good:

Big thanks all

[MENTION=1162986]Captain_Throwback[/MENTION] do you have a solution for xposed installer integration?
[SuperR Kitchen] :
[MENTION=1162986]Captain_Throwback[/MENTION] that's what I was thinking but I thought he had the plugin take the updatebinary from original zip and rename. Glad you mentioned it :good:
[SuperR Kitchen] Captain_Throwback:
Have you tried integrating the systemless Xposed as a custom_dir? It may work, since it uses a shell-type update-binary which is different than the standard Xposed installer.
[SuperR Kitchen] :
I use it in my Aroma as an option, actually both Xposed's, I do the update-binary install thing like for SuperSU or Busybox and they work fine.
[SuperR Kitchen] Captain_Throwback:
The standard installer works? It doesn't install via update-binary, it uses a separate flash script, so how do you include it?
[SuperR Kitchen] :
It uses update binary.
[SuperR Kitchen] Captain_Throwback:
Not exactly - it uses an additional script for flashing. I've tried including it and it has never worked. Unless you're using a modified zip not distributed by [MENTION=4419114]rovo89[/MENTION].

EDIT: For reference, added screenshot.
[SuperR Kitchen] _that:
In TWRP there is already a /tmp directory. And since it's in a ramdisk its contents are lost when you reboot, same as with all other modifications in the root directory.
[SuperR Kitchen] _that:
Edify has a run_program function to run arbitrary programs. So it should suffice to extract the script somewhere and run it.
[SuperR Kitchen] Captain_Throwback:
It should....but it doesn't work, for some reason. Never cared enough to look into why, and now I'm confused because [MENTION=6320543]RatchetPanda[/MENTION] is saying it works :confused:.
[SuperR Kitchen] :
Extract the latest xposed zip you'll see that it uses update-binary.
[SuperR Kitchen] _that:
I found out that Xposed uses a special build of busybox as update-binary. Here is the main commit for that:

https://github.com/rovo89/android_external_busybox/commit/939c39ff312e3be1120aef3ed1893f7217383225
[SuperR Kitchen] JochenP:
exact my problem of xposed framework installer:

# this is a dummy file, the magic is in update-binary and flash-script.sh

thanks - i will test systemless xposed zip :)

---------- Post added 28th June 2016 at 12:17 AM ---------- Previous post was 27th June 2016 at 11:21 PM ----------

systemless xposed works great but how to substitute in kitchen?

I have added 'xpose/xposed_systemless' into a full rom zip after adjustment of the updater-scripts analog #ROOT section and AROMA crashes brilliant :eek:

#XPOSED
package_extract_dir("xposed", "/tmp/xposed");
run_program("/sbin/busybox", "unzip", "/tmp/xposed/xposed-v85.7-sdk23-systemless.zip", "META-INF/com/google/android/*", "-d", "/tmp/xposed");
run_program("/sbin/busybox", "sh", "/tmp/xposed/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/xposed/xposed-v85.7-sdk23-systemless.zip");

hmm - i want to edit custom directory path /xposed to /tmp/xposed and kitchen does not change anything in current - if i want to edit this entries i have to edit custom_dir-file and updater-script? :confused:

EDIT: it was no good idea by me to extract xposed to /tmp/xposed because update-binary contains:

rm -rf /tmp/xposed 2>/dev/null
mkdir /tmp/xposed
unzip -o "$ZIP" -d /tmp/xposed

and deletes that folder :crying:

now i ectract xposed to /tmp/_xposed and all is fine :)

please where can i add within kitchen these updater-script lines to automatically add these 2 startlines analog root or busybox?

I would prefer it if in the Extra Directory Menu another point would be introduced to expand the updater-script to launch these zips. :cool:
[SuperR Kitchen] SuperR.:
New plugin :)

Xposed Systemless Installer

by [MENTION=5787964]SuperR.[/MENTION]

Add Xposed systemless to your rom

Remove Xposed systemless if it already exists.

Usage:

Download the Xposed systemless zip of your choice into the xposed_systemless plugin directory.

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

v2.0.9.3 (Donate version)

Changes:

Rewrote all deodex functions for efficiency.

Added a few things for the xposed_systemless plugin.

v1.0.8.1 (Standard version)

Changes:

Rewrote all deodex functions for efficiency.
[SuperR Kitchen] pendor24:
Hello

are what the Xposed plugin also works for the root / xbin ? thank you
[SuperR Kitchen] SuperR.:
I am not sure I understand your question, but the plugin is only for systemless xposed, not for standard xposed.
[SuperR Kitchen] pendor24:
thank you

you just answer has my question. (Sorry for the dumb question , but I can not stand the new kitchen that verssion to Friday)

thank you
[SuperR Kitchen] HiM@L:
I tried making stock Android N flashable zip for Shamu with just debloated and rooted....but It stays in boot animation for like 5-10 minutes. is it normal....has anyone build N?
[SuperR Kitchen] SpasilliumNexus:
I'm getting errors upon deodex attempt.

----------------------------------------------------
Deoptimizing boot.oat ...
----------------------------------------------------

Error: Unable to access jarfile oat2dex-0.8.6.jar

Followed by an attempt with every file coming back as

... Deodexing 3c_main

Error: Unable to access jarfile oat2dex-0.8.6.jar
mv: cannot stat '/home/amplihelix/Development/superkitchen/superr_moto_x_pure_edition_stock_6.0_may_update/system/app/3c_main/oat/arm64/3c_main.dex': No such file or directory

And wiping out the oat folders and files in each directory.
[SuperR Kitchen] SuperR.:
v1.0.8.2 (Standard version)

Changes:

Fixed jar files not found while deodexing.
[SuperR Kitchen] JochenP:
since yesterday v2.0.9.3 i have the same issue (no errors) - my A9 does not boot into 6.01 :confused:

i have checked it twice: after 25 minutes stuck on boot - my 'special-xposed-ROM' from yesterday boots after flashing in 5 min.

please check this last update. i will check further later today

i could not find a previous version to do a compare - where can i find this on github?

edit1:

a) please have a look at Extra Directory Menu: 1) /data/app display changes only after leaving and reentering this Menu.

b) please 'ui_print' each app-name that is extracted out of /data/app for user information what is installed on his device for example something like

ui_print("Extracting data..."); ui_print(" ");
ui_print("Installing XposedInstaller_by_dvdandroid.apk.."); ui_print(" ");
package_extract_dir("data", "/data");
[SuperR Kitchen] SuperR.:
Here is v2.0.9.2

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

Fixed

v2.0.9.4 (Donate version)

Changes:

Fixed Extra Directory menu not showing /data/app status right away.

This is not a priority for me. Maybe in the future but no guarantees.
[SuperR Kitchen] nightcervant:
Sorry man, but plugin work to free version?
[SuperR Kitchen] JochenP:
only Donate version -> OP
[SuperR Kitchen] JochenP:
[MENTION=5787964]SuperR.[/MENTION]

thanks for the link to v2.0.9.2.

I have checked with same settings v2.0.9.2 against v2.0.9.4 and result is: HTC A9 boots with old deodexed (smali/baksmali) rom but not with the new changes in v2.0.9.3/4.

Updater scripts are identical
[SuperR Kitchen] SuperR.:
It is very possible I made 1 or more typos in the deodex functions. I will look it over as soon as I get a chance. Thanks for pointing it out :)
[SuperR Kitchen] jazzespresso:
do I have to care about this option in MM build ROM? currently I did not enable it...I was just wondering about it

3) Add/Remove su.d support (CURRENT: Disabled)
[SuperR Kitchen] bcrichster:
No, it's just an option for those that want it

Sent from CM12.1 *N9515*
[SuperR Kitchen] SuperR.:
v2.0.9.5 (Donate version)

Changes:

Fixed deodexing that broke in v2.0.9.3.

v1.0.8.3 (Standard version)

Changes:

Fixed deodexing that broke in v1.0.8.1.
[SuperR Kitchen] JochenP:
Deodexing - boot - problem is gone :good:

Big thanks.
[SuperR Kitchen] SuperR.:
v2.0.9.6 (Donate version)

Changes:

Fixed issues deodexing Lollipop roms since v2.0.9.3.

v1.0.8.4 (Standard version)

Changes:

Fixed issues deodexing Lollipop roms since v1.0.8.1.
[SuperR Kitchen] enotar:
Deodex doesnt work on 1.0.8.4.

Just finished and show some error and delete all deodexed files. Yes all deodexed fie are gone during the final of the deodexing process.

Deodexing complete

/home/enotar/Desktop/superr: line 2632: exit_deo: command not found

/home/enotar/Desktop/superr: line 6948: return: can only `return' from a function or sourced script

enotar@enotar-Lenovo-IdeaPad-Yoga-11S:~/Desktop$

I tried other older version of Superr and still deleting deodex files, last week I succeed but this week things are not working, only change Ubuntu updates
[SuperR Kitchen] SuperR.:
What Android version are you deodexing? If M, which option did you choose?
[SuperR Kitchen] lonegolfs15:
Hi [MENTION=5787964]SuperR.[/MENTION]r, radio.img and bootloader.img will can be extracted with your kitchen someday?
[SuperR Kitchen] SuperR.:
v1.0.8.5 (Standard version)

Changes:

Fixed exit_deo errors, and hopefully the other issues along with it.
[SuperR Kitchen] enotar:
LL 22 arm and kitchen did not ask for anything I choose metadata as usual.

What I find out with an old Kitchen I have to reboot to see the content of app or priv-app what is kind of strange. Now I am testing 1.0.8.5. I advise on result.
[SuperR Kitchen] enotar:
Tried 1.0.8.5 and no error messaje but /app and ,/priv-app are wipe out. Left over only few files.
[SuperR Kitchen] SuperR.:
v2.0.9.7 (Donate version)

Changes:

Fixed L deodex deleting all apps after deodexing.

v1.0.8.6 (Standard version)

Changes:

Fixed L deodex deleting all apps after deodexing.

edit: I am very sorry for all the issues I caused with the deodex rewrite. I must have been half asleep when I did it :eek: Hopefully all is good now :)
[SuperR Kitchen] JochenP:
I have played with AdAway-plugin (analog your xposed-plugin) and found, that kitchen need some extra changes to add the adaway- folder into the zipped ROM. A separate file with these infos, generated from the plugin seems for me makeable.

To edit kitchen is no solution but there may be better ideas?
[SuperR Kitchen] enotar:
Hey man, no problem. We love your work.

---------- Post added at 11:58 AM ---------- Previous post was at 11:57 AM ----------

Would be nice to have xposed installer also include Maybe only a directory where we could drop the zip file and it get flash after rom install automaticaly. Or maybe put anything to flash in this directory?

Where is the Aroma?
[SuperR Kitchen] SuperR.:
I edited the kitchen for Xposed and for gapps plugins to include the directories in the rom.zip. Let me know what your plugin names the directory and I can edit the kitchen to include it as well.

I could not think of a better way to do it other than include all directories in the rom directory in the zip. This would be fine if I was sure nobody has extra directories in their rom directory, but I can't be sure of that.

We already have an Xposed plugin :)

We also have an Aroma plugin :)

Plugins are only for the donate version of the kitchen and can be found in post #5
[SuperR Kitchen] enotar:
Hey SuperR

Can you add me to Gitlab: enotar2

Donation: 3DE59705C3653082P
[SuperR Kitchen] JochenP:
That is okay. It is not too hard to drag and drop a folder on a zip.

AdAway is not easy to integrate because it starts not from binary an i had to integrate his script and adapting the path.

I'm not sure if i blame myself [emoji5]
[SuperR Kitchen] enotar:
So first try with 2.0.9.7 Samsung SM-P600 5.1.1 sdk 22

1-All ok and nice but Aroma disable installation of Supersu, Busybox and Xposed

Aroma start and flash everything but these 3......

Log give this

2-Now I disable aroma and flash

SuperSU and BusyBox are ok but Xposed is not installed. I check Updater script and the install of Xposed is missing after extraction in the script.

This part:

So add the missing script to the updater but xpsed is not installed after flashing.

Following the trace I manualy flash 85.7 and it install but cannot be activated. I suspect system- less version to be the problem so I tried to flash 85.1 that is not system-less and on this case it works so tomorrow firt thing I replace on the rom but I am not sure that will work.

So long night. Reviewing the updater script it looks the addition of xposed is not include. Maybe my error. Need to verify tomorrow. No the Folder has the right info but the final script in the zip file is different missing the Xposed part......

Btw: SuperSU 2.75 works. I add the apk in data.

Other. Can you explain what is the option for a regular root install, not system-less?
[SuperR Kitchen] SuperR.:
I don't know anything about Aroma actually. Maybe someone else can help figure out why Supersu, Busybox and Xposed are not flashing when using Aroma.

I suspect the reason for this is that you added xposed after adding Aroma. When you add Aroma, the existing META-INF directory is moved to 00_project_files. When you remove Aroma, it is moved back. If you make changes after adding Aroma, they will be lost when you remove it. The best option is to add everything you want and add Aroma last. This way everything you add will still be there after removing Aroma.

I am not certain, but it has been discussed that the regular Xposed will not flash properly when included in the rom.zip. That's why the plugin is only for the systemless Xposed. Let me know how it goes for you.

If you choose system install, SuperSU will be flashed as it used to be in KK and below. All the files will be in the /system partition instead of /data.
[SuperR Kitchen] :
It can't open them so maybe [MENTION=5787964]SuperR.[/MENTION] a set_perm_recursive on /tmp? Ive never seen this when using Aroma.

:highfive:
[SuperR Kitchen] enotar:
thanks for the answers, finaly i redo all and xposed is installed but not active, not sure why as the log is not present in data/data.

I am trying to find the next move.
[SuperR Kitchen] :
Delete the disabled file in /xposed