yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] russel5:
[MENTION=5787964]SuperR.[/MENTION] i don't know what are do in the last free version, but now if i choose deodex rom with smali/baksmali, no one apps have classes.dex. Only framework jar files have classes.dex. With oat2dex method all works.

One more thing: with smali/baksmali method - we don't have any logs (deodex.log is empty). oat2dex - all normal.

And last: i have one app wheech have 34 classes.dex, but your script only add classes; classes2 and classes3 - this is not rhight.

Thats all. Anyway thanks for your hard work.
[SuperR Kitchen] enotar:
Please explain
[SuperR Kitchen] :
There's a file named disabled in /xposed directory. Delete it.
[SuperR Kitchen] SuperR.:
I will take a look at the smali/baksmali method when I get a chance.

34 classes? I have never seen more than 3. Please send the firmware that contains this apk and tell me which one it is so I can have a look. Thanks
[SuperR Kitchen] russel5:
Official Sony app "Support" have 34 classes.dex

HERE
[SuperR Kitchen] Ram121:
Samsung email is also having 34 Classes.dex
[SuperR Kitchen] SuperR.:
v2.0.9.8 (Donate version)

Changes:

Fixed deodexing M with smali/baksmali.

All deodex methods will now use all classes instead of only classes.dex, classes2.dex, and classes3.dex.

v1.0.8.7 (Standard version)

Changes:

Fixed deodexing M with smali/baksmali.

All deodex methods will now use all classes instead of only classes.dex, classes2.dex, and classes3.dex.

edit: I am seriously wondering if this classes*.dex problem was causing all the issues on Samsung devices. I am looking forward to some feedback :)
[SuperR Kitchen] enotar:
Now with new version Xposed plugin dont run:
[SuperR Kitchen] russel5:
Thanks man, all works on MM now, but not work in 5.1.1 :)

Some logs.
[SuperR Kitchen] SuperR.:
Did you read the error you posted? I would do what it says if I were you :p

The log says /home/russel5/develop/superrs-kitchen/superr_232/system/framework/arm/boot.oat is not found. Deodexing won't work without it on 5.1.1. I am not sure what could cause this, but I will check into it. In the meantime, please check to make sure that file exists. Thanks :)

edit: I only have one L rom to test with and it is working properly. If you continue to have issues, send me the exact firmware you are trying to deodex and I will have a look. Thanks
[SuperR Kitchen] russel5:
Yes you are right, it's my fault. All works now.

Last question: can we use smali/baksmali method of deodexing on Lollipop firmwares?
[SuperR Kitchen] SuperR.:
Unfortunately not. smali/baksmali specifically states it will not work on L roms. Last time I checked, it does not work on N roms yet either.
[SuperR Kitchen] enotar:
Yes I did redownload and place in the right directory.

---------- Post added at 04:02 PM ---------- Previous post was at 03:57 PM ----------

It was already in but after updating it did not work so I just verify and plugin was there. In case I redownload No go. Reinstall kitchen No go. Reinstall everything No go.

I will reinstall all one more time and try other plugin
[SuperR Kitchen] SuperR.:
Do you have systemless xposed or standard xposed in the plugin directory? The zip name must be xposed-*-systemless.zip. If the plugin does not see the word systemless in the zip name it will not use it. As I said before, the plugin is for systemless xposed only. If you want to try the standard xposed, you can rename it (ex. xposed-v85.7-sdk23-systemless.zip) to get the plugin to recognize it. If it works I will remove the systemless restriction.

edit: aroma_install plugin updated :)

Changes:

Will now keep changes made to the updater-script after removing Aroma.
[SuperR Kitchen] MM13:
[MENTION=5787964]SuperR.[/MENTION]

Donation confirmation #8XV03237BR260873S

Gitlab username MM13

Thanks for your hard work :)
[SuperR Kitchen] enotar:
This is my report after reinstalling everything on Samsung SM-P600 5.1.1

Cooking

Installed SuperSu systemless

Instaled Xposed systemless It looks Plugin works

Install /data

Install init.d

Deodex

at the end run Aroma plugins

Buid zip

Xposed is in the zip

SuperSu is in the zip

Busybox is in the zip

/data is not in the zip

Flashing

All ok and I save Aroma log

Running

Not root

No Busybox

No Xposed

Aroma Log final:

about to run program [/sbin/busybox] with 6 args

unzip: can't open /tmp/supersu/BETA-SuperSU-v2.74-2.zip[.zip]

run_program: child exited with status 1

about to run program [/sbin/busybox] with 6 args

unzip: can't open /tmp/xposed1/xposed-v85.7-sdk22-systemless.zip[.zip]

run_program: child exited with status 1

about to run program [/sbin/busybox] with 6 args

unzip: can't open /tmp/busybox/UPDATE-Busybox.Installer.v1.24.2-ALL-signed.zip[.zip]

run_program: child exited with status 1

It looks Aroma remove /data and there are some issues with extras like root, busybox and Xposed

I post my META-INF folder in case that can help
[SuperR Kitchen] SuperR.:
I will say it again... I don't know anything about Aroma. All the plugin does is make it easy to get it incorporated into your rom. Everything else is up to you to figure out. However, if you figure out that the plugin is doing something wrong, let me know what it is and I will fix it :)

edit: just looked at your META-INF directory, and SuperSU, Busybox, and Xposed are not being extracted to tmp before trying to unzip and the script is not set to run after extraction. Somehow your script ended up getting cut. I will look into it to see if the kitchen is cutting it at some point.

edit2: Just added root, busybox, and xposed, then added aroma and built the rom zip. None of my script was cut and looks good. I suggest you delete your META-INF directory, and choose set_metadata permtype again. This will create a new META-INF directory. Then try adding what you want again and see if the script looks good.
[SuperR Kitchen] JochenP:
is necessary to delete META-INF?

by choosing 'set_metadata permtype' again kitchen rebuilds my updater-script (i don't know before your post that 'set_metadata permtype' reruns if not changed and edit META-INF always by hand :o) :good:

[MENTION=2682152]enotar[/MENTION] SuperR is right:

package_extract_dir("supersu", "/tmp/supersu");

package_extract_dir("xposed", "/tmp/xposed1");

package_extract_dir("busybox", "/tmp/busybox");

is missing in your updater script

If you decide to integrate xposed then you may add by choosing >Extra Directory Menu/ 1)data/app and put 'XposedInstaller_by_dvdandroid.apk' into corresponding folder

always append twrp and aroma logs
[SuperR Kitchen] nitesh9:
[MENTION=5787964]SuperR.[/MENTION] I am not able to access ROM tools for deodexing in the latest version 1.0.8.7. Any way to fix it? I am using Ubuntu 14.04 with Java 8. Trying to deodex HTC Sense 7.0 MM ROM for Desire 820. It also has oat folders which contain .odex files.

Thanks in advance.
[SuperR Kitchen] SuperR.:
deleting META-INF may not be necessary, just wanted to be sure he was starting fresh :)

Can you be more specific? What happens when you choose option 8 from the main menu to enter ROM Tools? If it says there is no rom, did you extract it first? If you extracted it and it still says no rom, please send the firmware so I can take a look.
[SuperR Kitchen] nitesh9:
Nothing happens when I select the option 8 i.e. ROM tools. No new menu comes which used to contain functions for deodexing etc....

And yes I had extracted the ROM in appropriate project folder. It is working in older version of Superr Kitchen. The problem is in the latest version. :(

Please check once...
[SuperR Kitchen] SuperR.:
I am not having any issues, and nobody else has said anything either. I did not change anything in the latest version that would prevent ROM Tools from working. I suggest git cloning the kitchen fresh and allowing the kitchen to extract your rom again.
[SuperR Kitchen] nitesh9:
Ok bro. Now working. Thank you very much. :)
[SuperR Kitchen] IronMark10:
Tool Port ROM

Friend you could put in your tool an option for roms door as Cyanogenmod , Miui and more!
[SuperR Kitchen] SuperR.:
You need to mount the image as root, which is why it asks for your password (sudo password is your user password. same one you use to log in to your machine). If you don't enter it correctly it will not mount and will not extract.

as for the 7MB zips, if you are running 64bit Linux make sure you install the package from post #4
[SuperR Kitchen] reefuge:
ok cool - i have just changed linux to bbqlinux and guess thats why need the 32 bit

as for password im stumped as i always use the same password for this machine and type it 100% correctly and hit enter and still get permision dienied

I will read post 4 and try again

Im going back to ubuntu anyway so will clean install again
[SuperR Kitchen] SuperR.:
v0.9.1.8

Changes:

Fixed updater for non-cloned kitchens to remove smali, baksmali, and oat2dex before extracting the new version

Added root warning when choosing adb for system partition detection

NOTE: If you did not clone the kitchen, are running earlier kitchen versions, and did not delete the older smali/baksmali...you should.

If you are not sure how to do this, an easy way to get it all fixed is as follows:

1. Update to this version

2. Open README.md and change the version back to v0.9.1.7 and save the file.

3. Open the kitchen and update through the updater
[SuperR Kitchen] beefx:
How to odex deodexed rom? i am using galaxy note 4 with android 5.1.1

can i do this on my computer? i have flashable zip of custom deodexed rom. please help
[SuperR Kitchen] SuperR.:
This Kitchen does not support odexing a deodexed rom.
[SuperR Kitchen] beefx:
Can you help me with odexing odexed dedexed rom? Please
[SuperR Kitchen] bcrichster:
Try Lucky Patcher.apk, must use it from device.

Gratefully sent from my Rooted Tesla N9510
[SuperR Kitchen] PaulPizz:
Can you give the option to edit build display in build.prop?
[SuperR Kitchen] SuperR.:
I could, but I will make you work a little harder to remove my credit for all the work I have done to bring you this kitchen :)
[SuperR Kitchen] sefrcoko:
Best response I read in any thread this week lol [emoji106]
[SuperR Kitchen] hohassan444:
[MENTION=5787964]SuperR.[/MENTION]..

I tried last 3 versions to create sparse_dat...every time i get only 12 mb zip. I tried both manual and adb ( rooted device). in addition i already install package in post 4 on my ubuntu 64.

thanks in advance
[SuperR Kitchen] PaulPizz:
Awesome tool. Thank you!! [emoji2]
[SuperR Kitchen] SuperR.:
Any errors if you scroll up in your terminal several screens?
[SuperR Kitchen] hohassan444:
I get no errors...just the final build zip is always 12 mb and don't contain any system.new.dat.
[SuperR Kitchen] SuperR.:
I have no idea then. Can you try doing it manually following this guide and let me know where the error is? Thanks

edit: start in the middle of step 2 where it says "Now we need to compress it back to a raw ext4 image"

edit2: I am assuming you are still missing dependencies for make_ext4fs. An easy way to find out is to do the following in a terminal:

cd /kitchen/tools
ldd make_ext4fs

/kitchen/tools must be your actual tools directory wherever that may be

The 2 lines above require ENTER to be pressed after each. /kitchen/tools must be your actual tools directory wherever that may be.

Please paste the output here. May save you time testing if you just need dependencies met
[SuperR Kitchen] hohassan444:
This is the output

linux-gate.so.1 => (0xf7768000)

libstdc++.so.6 => /usr/lib32/libstdc++.so.6 (0xf7632000)

libm.so.6 => /lib32/libm.so.6 (0xf75e5000)

libgcc_s.so.1 => /usr/lib32/libgcc_s.so.1 (0xf75c8000)

libc.so.6 => /lib32/libc.so.6 (0xf7410000)

/lib/ld-linux.so.2 (0xf7769000)
[SuperR Kitchen] SuperR.:
Looks like all the dependencies for that binary are met. Back to my original suggestion to do it manually from the guide I posted above. I have no idea what is going on and this seems to be an isolated issue that only you are having.
[SuperR Kitchen] andreya108:
Today I've made another attempt with the same result.

system.img unpacking ok

deodexing without any error

system.img creation ok

fastboot flashing ok

rom when booting:

1) shows boot animation

2) shows "android is starting.." optimizing app 1 to 108

3) after optimization complete - "starting apps" appears for a half of second and then soft bootloop immidiately, goto 1)

What Kitchen version?

0.9.1.8

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

google nexus 5 hammerhead

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

stock mra58k firmware

What Android version?

6.0

What perm method (set_perm, set_metadata, sparse_dat)?

none

What did you do after extracting and before building?

deodex only

What have you tried that did not work?

deodex

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

no errors occured

Can you send a link to the files you started with (nandroid, system.img, boot.img, etc)?

https://dl.google.com/dl/android/aosp/hammerhead-mra58k-factory-52364034.tgz
[SuperR Kitchen] reefuge:
nope i've got it too and I done a complete reinstall of ubuntu 15/04 inc post #4 suggestion. and i get 7.6mb zips
[SuperR Kitchen] SuperR.:
What do you want this port option to do exactly?
[SuperR Kitchen] IronMark10:
have a redmi note 3 pro and lenovo k4 note , wanted roms port other devices to them, more n know how if you put The option roms door on your kitenchen tool would masi easy !
[SuperR Kitchen] bcrichster:
I think you are asking way more than you think..

Sent from CM12.1 *N9515*
[SuperR Kitchen] baloo30310:
superr hello's! since Version 1.0.8.7 I can no longer extract the system adb my Note 4 it leaves me a 500MB img then nothing extraction
[SuperR Kitchen] SuperR.:
The only thing that changed during 1.0.8.1-1.0.8.7 is deodexing. I did not touch any other code. Please follow the same advice as post #3624 as the part of the kitchen you say no longer works is exactly the same :)
[SuperR Kitchen] enotar:
Tried

Xposed systemless doesn't work. Posted error in xposed thread.

---------- Post added at 04:34 PM ---------- Previous post was at 04:34 PM ----------

No file in that dir

And Aroma plugin is more trouble than gain so I will try to get Xposed fixed first in the xposed thread and after come back to Aroma.
[SuperR Kitchen] marsapa:
Hello, I found a bug in deodex, virtually if deodex firmware mediatek 6.0 (I've tried several, and for several mediatek phones) do not receive text messages, tips? I tried several versions of the kitchen and entrabi methods but the result is always the same, the same bug sms
[SuperR Kitchen] nitesh9:
[MENTION=5787964]SuperR.[/MENTION] I am unable to deodex the HTC Sense 7 MM ROM (Desire 820). Kitchen is just deleting the .odex files without actually deodexing it. :(

I am using the latest Superr Kitchen. Please help me. Here is the HTC firmware: https://mega.nz/#!ooUBgBLR!lMR3ZUB8e1XDpqqvQh8bjsOp7AKnt0fTcGEn2RuTRTo.

Please look into it. The firmware has strange stucture - it has the 'arm' and 'arm64' folders inside a 'oat' directory!
[SuperR Kitchen] Captain_Throwback:
Most of the HTC Sense ROMs include a classes.dex inside of each APK, so deleting the odex files is all that's needed to "deodex" it. Did you try it after the deodex completes? Did you confirm that the APKs in fact include classes.dex?
[SuperR Kitchen] SuperR.:
No idea, sorry. Are you sure deodex is the problem? Do text messages work if you build the rom without deodexing?

[MENTION=1162986]Captain_Throwback[/MENTION] is correct. Your apps are already deodexed. Just the framework needs to be deodexed and it seems to work fine.

edit: the structure is not strange. That is the directory structure of M roms.
[SuperR Kitchen] nitesh9:
Thank you [MENTION=1162986]Captain_Throwback[/MENTION] and [MENTION=5787964]SuperR.[/MENTION] I will check for classes.dex in apks.

This is my first MM ROM Port that's why didn't know about new odex directory structure. [emoji14]

Thanks once again. :)
[SuperR Kitchen] SuperR.:
There is really no reason to check the apks for classes.dex. The kitchen does this for you :)
[SuperR Kitchen] fhem:
[MENTION=5787964]SuperR.[/MENTION] SuperSU 2.76 released.
[SuperR Kitchen] marsapa:
with option 1 does not receive any error the deodex goes through but using the rom you have this problem that unfortunately comes from deodex the Roma because I did all the tests and only after deodex you have the problem

with the second option I have an error with telephony in the framework
[SuperR Kitchen] bigrammy:
Hi marsapa,

I am not sure if this problem is 100% a kitchen one :confused:

I have the Infocus M808/ZM1 mt6753 and in both MM 6.0 Roms released they removed the MTKmms.apk and have replaced it with a already deodex messaging.apk so maybe they had issues with the MTKmms also. :rolleyes:

Infocus are very advanced/experianced compared to most far eastern manufacturers and produce very nice but very complicated roms. :eek:

Here are the stock unchanged service and messaging apk's to test or compare

mt6753-ZM1-Messaging-apks.zip :fingers-crossed:
[SuperR Kitchen] marsapa:
the problem comes with the new soc both the p10 and either x20, I did a thousand tests, with mtkmms and other apps, but the problem eventually comes exclusively from deodex, the great thing is that the SMS send but not receive them
[SuperR Kitchen] bigrammy:
Seems odd :confused:

Maybe check this sms issues miui MTK

Also check the MTK Engineer mode

/telephony/Misc Feature Config
/telephony/IMS/SMS
/telephony/IMS/Common/sms_support

for any changes between stock and deodex :fingers-crossed:
[SuperR Kitchen] DelKrm:
Hi

1 .SuperR's Kitchen v1.0.8.7

2. Linux Mint 17.3 64bit

3. Samsung G920R4

4. Stock Samsung Firmware G920R4TYU3CPB4 (6.01)

5. sparse_dat

6. Build Zip . Without any changes.

7. Bild full rom zip => Connect your phone....... (Root, no Root -No difference. usb debugging- ON) Error :

Something went wrong building the system image.

Make sure your system partition size is correct and

that the system directory is not too big to fit.

If you select item 4, the firmware is going, but the phone will not boot. Restoring stock boot.img of TWRP. Phone is loaded. WIFI not working.
[SuperR Kitchen] marsapa:
Tomorrow i see and know you
[SuperR Kitchen] SuperR.:
I suggest you try set_metadata. You are likely to have many issues with sparse_dat on M roms. You will not need system partition size for set_metadata.
[SuperR Kitchen] DelKrm:
When using "set_metadata". wifi not work.

When using "set_perm" wifi not worked.

Tried different options. Or WiFi does not work, or is not loaded. If not loaded, then restore the stock boot in TWRP. Phone is loaded, but WiFi does not work anyway.
[SuperR Kitchen] SuperR.:
I thought we fixed wifi not working on Samsung devices a while back. This sounds just like the issues people were having before. It turned out to be a permissions issue that was fixed by adding a set_metadata line in the updater-script. There is probably another one that needs to be added. I don't own a Samsung so hopefully someone else will chime in to help.
[SuperR Kitchen] asc1977:
Here is a working updater-script from Samsung device if you want to compare permissions. Android 6.0.1
[SuperR Kitchen] Ram121:
There is no issue with set_metadata for Samsung Note 4. My ROM working good with the script for Samsung Note 4 6.0.1. The updater-script is attached
[SuperR Kitchen] DelKrm:
Reinstalled kitchen.

Assembly - "set_metadata". All upheld

Build full ROM Zip

After flashing the phone is not loaded. Reloads in TWRP.

Restoring stock boot.img

Loading. WI-FI works fine.

It remains to deal with boot

In any case, you did a great tool. Thank you.

Thank you. I will watch.
[SuperR Kitchen] SuperR.:
What did you do to the boot.img to make it different than stock? Did you add root (if so which option did you choose), init.d, insecure boot, dm-verity, or forceencrypt? If so, try to build roms without each of those things one by one to find out what is causing the issue. Once we know what is causing the issue, I can probably fix it.
[SuperR Kitchen] DelKrm:
There is not any change.. Just the original firmware for TWRP.

Unpacking => Build full ROM Zip.
[SuperR Kitchen] shoey63:
You can't use TWRP as a boot.img. It will (obviously) always boot into TWRP recovery.
[SuperR Kitchen] marsapa:
In engineer mode there IMS ..... while for the SMSC method I had tried without success
[SuperR Kitchen] pendor24:
Hello ,

I cook on , S5 and Note 4 ( marshmallow )

the only solution for a kitchen with no problem rom is compile raw img . Once the file img fact, I copy it in a new project and exstract for obtenire a metainf , (something the kitchen refuses to do without partition size indiquation ) while she generates no problem , then I copy (For me the last functional version of the 100 cuisinne it was free verssion 1 . 59) since nothing works as indicated
[SuperR Kitchen] bigrammy:
Hmm sorry bro dont totally understand what you're saying. :o

Go to your MTKmms.apk or Install the messaging.apk I uploaded for you If you do not see the following options. If it installs without issue open it and goto the settings (top right 3 dots) in there you will see SIM 1 Service Center & SIM 2 Service Center tap on them & check that your cell providers service numbers are in the box if not then enter it. The number should start with a plus sign (+)

You can test it by sending a text from your number to your number you should then get a message sent and a message received within a few seconds.
[SuperR Kitchen] DelKrm:
1. Flash zip.

2. Phone is not loaded

3. Go TWRP

4. restore boot.img from backup.

5. Phone is loaded. Later it works normally.

6. No need to use TWRP every restart.

P.S: Sorry for bad english.
[SuperR Kitchen] Ram121:
[MENTION=7575242]DelKrm[/MENTION] answer questions asked by [MENTION=5787964]SuperR.[/MENTION] In his post you will get result as for Samsung you should not modify anything in boot.img and only select the option of let supersu decide for rooting then only the ROM would boot

Otherwise any change in boot.img would mostly result into bootloop
[SuperR Kitchen] kc6wke:
Not booting

I was on version 1.0.8.0 and all was working fine, I updated to current version and now roms will not boot.

just hangs at splash screen and then reboots after a few minutes.

Building for HTC 10, deodexed, system root and BusuBox only

Any ideas, or how can I revert back to 1.0.8.0?
[SuperR Kitchen] DelKrm:
Samsung Galaxy S6 G920R4 (G920R4TYU3CPB4 6.01)

Build full ROM Zip

Assembly - "set_metadata" +Root +No Knox

flashing in TWRP => Everything works!!!

Thank you all for help
[SuperR Kitchen] SuperR.:
If you are saying v1.0.5.9 is the last version that worked, it is simply not true. Clone the kitchen fresh and extract your rom fresh. If you are having problems, upload the firmware you are using and give detailed instructions on how to reproduce the issue. Otherwise I can't help

Clone the kitchen fresh and extract your rom fresh.

Just in case, here is v1.0.8.0 but you won't be able to use the kitchen updater with it.
[SuperR Kitchen] pendor24:
Hello

does not mean it is not true ( I 'm everything you want, but not a liar )

I tried on all Android 6 note 4 Roma and s5

any permissions that offers cooking

all build methods

and no permit is my rom to start normally ( always the message of the SD card is corrupted )

I make several manipulations ( unconventional ) using the kitchen for my ROM to boot normally. while on the version 1 . 59 I did a rom s5 and s7 following the instructions tutorials (AC worked nickel)

and since nothing works, he even brought me to pay for donor version, which changed nothing. even now in oats deodex not deodex any apk