yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] scrappy610:
OK, I experienced this last night when trying out the new update deodexing. It was a stock Samsung note 5 rom, if needed I can post the source. But it so far, has only happened when I use a Samsung rom. I know Samsung is a pain to deodex so I usually just use an outside tool for deodexing. Everything else seems to work fine except the samextra plug in doesnt seem to actually apply changes and the debloat script seems to have changed. Again neither are a big deal to me as I usually double check manually and use a custom debloat script.

But for the memory issue was curious if it was a Samsung rom? I'll try just building the zip without deodexing and see if it does the same.
[SuperR Kitchen] dbarrett480:
Does anyone know do I add a flashable zip such as viper4android to my rom?
[SuperR Kitchen] scrappy610:
That would be covered in the viper4android thread. Here's the link:

http://xdaforums.com/showpost.php?p=39156761&postcount=5
[SuperR Kitchen] Macguyver1980:
Regarding my link for files, nothing to enter in decryption request, there's no, don't know why it's asked even, but ok... thanks for help because it's really frustrating as there's nothing in logs even for me to understand where's coming from the problem... And even without modifying anything at the ROM extracted, same issue when I try to Build directly... that's why I suspect or something wrong with extraction of files from this format win000 and win0001 or missing files...
[SuperR Kitchen] SuperR.:
For the samextra plugin, you must unpack your boot.img before running the plugin, and pack it after running the plugin. It makes edits to the ramdisk so if you don't repack you are using the old boot.img

The debloat script has not changed in a while. If there are things that need to be added to it or knox please let me know.

I am happy to take a look at your firmware, but I can't download it without a decryption key. See attached screenshot. The kitchen is able to handle win files, but it possible there is something different about yours. If I can get the files I can take a look.
[SuperR Kitchen] scrappy610:
Thanks [MENTION=718594]super[/MENTION]r I figured it was user error. To update about the memory, at least in my Samsung case, it was the internal deodex causing the memory notification. Deodexed externally or not deodexed, just rezipped and its good everything works as expected. Not a big deal to me considering you already discussed Samsung being picky earlier in the thread.

I'll redo and extract boot image and compare the debloat to ensure nothing else is needed and if anything is updated I'll be sure to share. Thanks again.
[SuperR Kitchen] Macguyver1980:
Ok, here's a link that should directly work without any password to enter:;)

https://mega.nz/#F!O1REyaaD!1f7rXY2pi6wTVRfbpCjy3g

Thanks
[SuperR Kitchen] SuperR.:
The cpio error can be ignored as we are only unpacking the boot.img to get file_contexts at that stage of the extraction.

The error you got when trying to get the system partition size through adb will not get fixed unless you give me the adb shell commands to get this info from your device. You will need to figure out your system partition size in bytes and enter it manually if you want to use sparse_dat, raw_img, or create a system.img..

I did not get any errors when building the full rom zip in the kitchen. The only suggestion I can give is to try Ubuntu 16.04 if you are not currently using it. It is what I test on so I am certain things work on it. In theory it should work on all Linux system with all the dependencies met. However in practice this is not the case unfortunately. Ubuntu4Kitchen is Kitchen ready if you want to give it a try :)
[SuperR Kitchen] Frankbrazillian:
Yes! It's a Samsung rom. Stock marshmallow for the Note Edge. I already tried with an older version of the Superr kitchen without the oatdump option, but seems that are not full compatible with the Samsung Marshmallow version. After replacing with deodexed files, i got an bootloop. With the updated version (with oatdump option), full deodex and boot normally, but got the out memory issue. Do you know some tool to deodex Marshmallow on Linux? Thanks in advance!
[SuperR Kitchen] scrappy610:
For linux, no unfortunately only way I know of doing it is manually. For Windows there is a tool, you will have to run the 64 bit tool first then the 32 bit, it is two separate tools. And it works just fine. I usually end up just copying the system to a shared folder and open in Windows for deodexing. I'm sure there is a tool somewhere for Linux, I just honestly haven't looked very hard.
[SuperR Kitchen] Frankbrazillian:
Ok thank's! If are just for some app's, it's ok for deodex manually... But for an entire rom, take much time. I have tried to search for some tool for Linux to deodex Samsung Marshmallow rom's, but i was not able to find any . I'll keep searching and or trying to find what's the problem with the Kitchen. Honestly i'm not sure if the problem ocurr when deodex or when build the system.img. Searching in the XDA, i have found inumerous threads with the same problem! Still searching to try to figure it out. Thank's again!
[SuperR Kitchen] serch826:
Boot a Deodexed Rom

Hi, i'm testing almost all the Kitchens features and can say that every thing works fine, deodex, adding root, bussybox, extra Folder, debloat, Gapps and even adding user Apps rocks.

But because modding the SystemUI in Odex NPD90G Rom doesn't work for me:confused:, so i tested deodexing NPD90G and modding the SystemUI and everything went fine:good:

The problem is that i can't make it to boot it stuck on Android bootanimation, if someone have a possible solution for this i'll appreciate for helping me with this.

Thanks in advance!
[SuperR Kitchen] _that:
Doesn't baksmali work?

https://github.com/JesusFreke/smali/wiki/DeodexInstructions
[SuperR Kitchen] Frankbrazillian:
Hi buddy! To be honest, i doesn't even give an try on the Marshmallow version in this way... When i was on Lollipop, i have tried with the Baksmali, but i got a lot of errors. After that, i have searched in the XDA forum and i found the tool of the SuperR (deodex_lollipop), and have used this untill some time ago. I will search a little more and give an try again... Thank's for helping!
[SuperR Kitchen] jaylence:
Thank you so much [MENTION=5787964]SuperR.[/MENTION] [MENTION=4657272]scrappy610[/MENTION].

I've finally been able to compile my S6 Edge Deodexed Rom as per your suggestion.

Deodexing was done by external deodexer.

Thanks to [MENTION=6242674]svadev[/MENTION] for his svadeodexer tool.

Compiled Deodexed Rom flashed and booted successfully without any errors.

The "running out of memory" and "smartcard manager" errors were fixed.
[SuperR Kitchen] kasi5471:
Hi mate, for apk modding i Switch to Windows, TmA and apktool. Best way for me...
[SuperR Kitchen] serch826:
Yes, i know about TMA, but i don't have problem with modding, i just trying to boot a deodexed rom.
[SuperR Kitchen] dbarrett480:
I'm trying to use the magisk_mod plugin and it can't find the magisk_mod zip file that I put in the tools/plugins/magisk_mod directory.....this worked yesterday so I'm not sure what's up. I have reinstalled the kitchen....I am running kubuntu 16.04.1. any ideas?
[SuperR Kitchen] jaylence:
The problem is with internal deodex.

It also happened to me before when everything seemed to be successfully deodexed as the system didn't warn of any errors but when I tried to flash the compiled deodexed rom I got stucked at boot animation just like your case.

As suggested by [MENTION=4657272]scrappy610[/MENTION] in previous post using an external deodexer fixes everything.

I now have a fully working deodexed rom.

Deodex Tool I used: svadeodexer v4.1

You don't have to deodex your apps one by one because his tool supports batch deodex.

All you have to do is copy your /system folder (with app; priv-app; framework folders on it. You also need to include your build.prop).

Run the Deodexer Tool and direct it to where your /system folder is saved.

Just replace your Rom's odex apps with the newly deodex apps.
[SuperR Kitchen] wwj402:
thanks

thanks and mark.
[SuperR Kitchen] Macguyver1980:
After installation of the Ubuntu for Kitchen 16.04, starting from scratch and again copying files I wanted to include in media repository and new build.prop, again same error in beginning. By playing I was able to Build one version completely but when I tried to install it, had a message in TWRP that zip file is corrupted. I'm on ZUK Z2 Pro, with bootloader opened and 3.0.2 version of TWRP adapted...:confused:
[SuperR Kitchen] scrappy610:
Where are you getting your starting firmware?
[SuperR Kitchen] Macguyver1980:
I've downloaded the special Lenovo file format of last official update (as they give only this format of) .qsb ones and did the as called SD update. Then after patching the bootloader and installing the last TWRP recovery version, did a backup of system files with TWRP and I took as base for cooking (for the system, a win000 and a win001 files). In the kitchen, I chose to extract from win000 one wnd seems indeed everything was well extracted. Then I cooked a bit as rooting, busybox and overwrote after some text update the build.prop and added some ogg sounds. Then try to build and to flash the zip from TWRP.
[SuperR Kitchen] scrappy610:
Ok, have you tried just extracting, and building without any mods? That would be my first suggestion. My apologies if you have and already stated that. But if not, it may be worth it to see where your error is occurring exactly.
[SuperR Kitchen] SuperR.:
I agree with [MENTION=4657272]scrappy610[/MENTION]. Additionally, use set_metadata. It is the most stable option in my opinion.
[SuperR Kitchen] SuperR.:
v2.1.1.2 (Donate version)

Changes:

The kitchen is now translatable using language files.

Added language chooser if there are files other than english in the languages directory.

If there are new english language elements added after an update, the non-english active language file will be updated with the new english elements for easy translation.

Added language reset to the Misc Tools menu.

Updated SuperSU to v2.78-SR1.

v1.1.0.1 (Standard version)

Changes:

The kitchen is now translatable using language files.

Added language chooser if there are files other than english in the languages directory.

If there are new english language elements added after an update, the non-english active language file will be updated with the new english elements for easy translation.

Added Misc Tools menu.

Added language reset to the Misc Tools menu.

Moved Zip new devices to share to Misc Tools menu.

Added Extra Directory menu.

Moved /data/app support to Extra Directory menu.

Updated SuperSU to v2.78-SR1.

NOTE: There is a new directory, /kitchen/tools/languages. Inside that directory is a file named english-srk. If you would like to translate the kitchen, copy english-srk and rename to yourlanguage-srk (eg. spanish-srk). The standard version and the donate version share the same language file so please translate everything so everyone can benefit from your work. You will need to avoid editing or deleting any variables in the language file. I tried to keep them minimal, but there are some color variables in there (eg. $redt, $bluet, etc). You will also need to avoid deleting the line breaks (\n) as they are there to make the text more readable in the kitchen. Other than that, enjoy :)
[SuperR Kitchen] bcrichster:
[MENTION=5787964]SuperR.[/MENTION] Killing it again! Wow.. Bangin' :cool:

Sent from CM12.1 *N9515*
[SuperR Kitchen] Macguyver1980:
Hi, Yes sure I try directly after unpacking to build, same. And as no debug information, I don't know what is the problem neither how to solve...

But I tried to cook a Custom CyanogenMod ROM, and well working. But CyanogenMod hasn't any driver for the sensors of this phone and is consuming too much. More options that I like and got used to, but not usable for this phone.
[SuperR Kitchen] scrappy610:
Can you pm me a link to the stock firmware? I looked but unfotunately the translation sucks.
[SuperR Kitchen] Only4givenOnceOfficial:
Whats the odds of asking for someome to build me a custom rom from stock here? I have the sm-g530t1 need root access i have a twrp but i am trying to gain root access that can be hidden from pokemon go so I can still play the game. I want to remove all the bloatware and gapps. I have gapps I can flash if anything. Do not own my own pc so it is a bit annoying to see of something better can be done on linux than windows. I plan to run xposed and all that on the rom just need to be able to hode my root from pokemon go and do not know how on this phone. Lollipop 5.1.1. If this can be done using the linux kitchen then i know where i will be coming when i get my own pc. :)
[SuperR Kitchen] Macguyver1980:
Even with same distribution and version I've the problem, I'd like to understand where it's coming from. At that error moment I've, what is the script doing that cause the stop, I guess coming from extraction of original files. Do you have another tool to extract .qsb files directly for me to check content and what's missing or wrongly extracted? Thanks
[SuperR Kitchen] Omel:
Could you share the process of deodexing you went through

Thx
[SuperR Kitchen] jaylence:
1. Run the Kitchen and create your project

2. Kitchen will extract your sysmtem.img into your project's working folder.

3. From your project's working folder, copy SYSTEM folder to your shared folder.

4. Delete all the contents of that SYSTEM folder EXCEPT for the following folders/file.

app

framework

priv-app

build.prop

5. Download SVADEODEXER from this link:

http://xdaforums.com/showpost.php?p=65741469&postcount=574

6. Choose 64bit

7. After downloading, run SVADeodexerForArt.exe

8. In the "Select a path to stock/system directory", direct it to where your SYSTEM folder is saved.

9. The tool will use the build.prop to validate your files. After that, put a check mark on items in "folders for deodexing from /system"

10. Hit EXECUTE

You can find the newly deodexed files in your SVADeodexeeForArtx64 folder.

One more thing, when it asks you about 32bit apps, just confirm to include them to your output folder.

11. You can now copy your newly deodexed system apps to your Project's working folder (replacing the odex files) and build your deodexed rom.
[SuperR Kitchen] scrappy610:
Like [MENTION=4704453]jaylence[/MENTION] posted, thats how i also do it. Only difference is there is also a 32 bit that i use from the same guy. I run it after the 64.
[SuperR Kitchen] SuperR.:
v2.1.1.3 (Donate version)

Changes:

Fixed Nexus firmware not extracting since they changed the format from tgz to zip.

v1.1.0.2 (Standard version)

Changes:

Fixed Nexus firmware not extracting since they changed the format from tgz to zip.
[SuperR Kitchen] bcrichster:
What... Did they really?! Bahahahah

Are both formats readable now?

Sent from CM12.1 *N9515*
[SuperR Kitchen] SuperR.:
They sure did. The last time I downloaded firmware was when Nougat images were released. At that time, all the firmware was tgz. I downloaded firmware today, and they are all zip :confused:

Of course both are supported now ;)
[SuperR Kitchen] NYCHitman1:
[MENTION=5787964]SuperR.[/MENTION] Plans to update smali now that JF fixed the issue for deodexing N apk's?

Link
[SuperR Kitchen] bcrichster:
Yoy should Test out the new smali and let ppl know before ya try to get SuperR. To update the kitchen.. What if I t doesn't work right? [emoji41]

Sent from CM12.1 *N9515*
[SuperR Kitchen] NYCHitman1:
You do realize that he gets the smali bits from JF, right?
[SuperR Kitchen] SuperR.:
The CLI is different now so the scripts need to be updated as well. I will be working on it in the next couple days :)
[SuperR Kitchen] GraveDigger176:
gitlab.com GraveDigger176

2KY17448R57758718 for full kitchen :good: :good:
[SuperR Kitchen] GraveDigger176:
Thx for the add :good:

I would try to cook a Rom with Aroma I download the Plugin that you provided on this site http://xdaforums.com/showpost.php?p=62845968&postcount=5 but i get a Error :confused:
[SuperR Kitchen] SuperR.:
Go to the link stated in the error message and download Aroma Installer as it is not included in the plugin. Basically, do what the error tells you to do :)
[SuperR Kitchen] xunholyx:
Flash Magisk by [MENTION=4470081]topjohnwu[/MENTION]. I don't have a link handy, but searching the forums should bring it up.
[SuperR Kitchen] GraveDigger176:
I do it what the link says and still the same error :confused:
[SuperR Kitchen] SuperR.:
The plugin is looking for a zip file with either "aroma_installer" or "aroma-2" in the name. It needs to be inside the aroma_install plugin directory, the same directory as the aroma_install file.
[SuperR Kitchen] psyriccio:
my donation 0TG94127VY507313Y and my github profile: github.com/psyriccio
[SuperR Kitchen] SuperR.:
Thanks, but I need a gitlab.com username, not github :)
[SuperR Kitchen] SuperR.:
I was able to extract the twrp you linked without issue. Make sure you rename it to recovery.img
[SuperR Kitchen] 1xinfusion:
I'm fairly noob to this but pressing option one in 1.9.2.0 would throw an error on line 205, but 1.9.1.8 works. on ubuntu

EDIT: My mistake, there was a space in my directory path
[SuperR Kitchen] sebastiandg7:
[MENTION=5787964]SuperR.[/MENTION]

Everything is working with .dat Lollipop CM12.1 files since v0.9.2.0 but now I have got some problems when building deodexed rom...

I 'm using a 5.1 Lollipop ROM (Stock based) to deodex... and when building the updater script (or binary) an error related with gawk/awk appears but the building process keeps going and the rom works. Is there any problem with this?

If needed:

Device: Moto G XT1032

ROM link: LINK

perm: sparse_dat (however original ROM does not uses it).
[SuperR Kitchen] SuperR.:
Downloaded your zip, tested some things and there are some issues with this zip that I will have fixed tomorrow. If you could copy/paste the awk/gawk error it would be helpful. I am getting a grep error instead.
[SuperR Kitchen] andreya108:
About 6.0 deodexing...

Current version of oat2dex (0.83) has been built on top of old buggy version of smali/backsmali (pre 2.1.1), and fails to deodex telephony-common.jar.

Now current smali/backsmali sources in git contains all necessary fixes (and moreover can deodex without oat2dex!)
[SuperR Kitchen] fhem:
I asume you are following this.
[SuperR Kitchen] DarkHeart Z:
I did that . But I haven't seen any option in the boot/recovery tools for recovery unpacking . That's what I was exactly trying to say . And other thing why identifying by name from boot.img is stuck like that for a long time ? Is that a bug or i have to create superr_mmc like u said earlier ?
[SuperR Kitchen] SuperR.:
If you only have a recovery.img in the project directory, the recovery.img will be worked on. Same goes for boot.img. If you have both you will be given a choice of which to work on.
[SuperR Kitchen] SuperR.:
The kitchen is not using oat2dex v0.83. I compiled from source a few days ago. v0.84 was just released today as well and I will update in next version.

Thanks for pointing out that smali/baksmali are now supporting M. I will update the M deodex in the next version to use smali/baksmali instead of oat2dex. oat2dex is still required for L however.

I am now, thanks :)
[SuperR Kitchen] beefx:
no changes :(
[SuperR Kitchen] DarkHeart Z:
It doesn't extract my mt65xx boot.img's correctly . I haven't found any rc files under ramdisk . There is just split image and ramdisk folder . In ramdisk folder I just got nothing . split image had only few files which I don't need to edit . i tried several times it is just the same . And I have both boo.img and recovery.img under my project folder in the superr home directory but It only shows the boot.img and boot.img extraction is incorrect . please fix it :(
[SuperR Kitchen] SuperR.:
There must be something else wrong. You should not have a split image directory when unpacking MTK boot and recovery. This tells me that you have the wrong build.prop for that boot.img in your project directory. build.prop determines which method of unpacking the kitchen should use and yours does not appear to be for an MTK device but your boot.img is.
[SuperR Kitchen] DarkHeart Z:
It doesn't extract my mt65xx boot.img's correctly . I haven't found any rc files under ramdisk . There is just split image and ramdisk folder . In ramdisk folder I just got nothing . split image had only few files which I don't need to edit . i tried several times it is just the same . And I have both boo.img and recovery.img under my project folder in the superr home directory but It only shows the boot.img and boot.img extraction is incorrect . please fix it :(

(P.S : sorry wrong quote last time )

---------- Post added at 06:04 PM ---------- Previous post was at 05:59 PM ----------

Understood . Mine is a custom rom for mt6572 . Not only these . But a lot . Please give a fix for it . Custom rom has build.prop tweaks and mods also . Maybe you're right . If you gave an option for kernel header detection instead of build.prop . That would be great and It happened with my stock rom also . i was porting a rom but It didn't extract my totally unmodded stock boot.img either . Please help me I'm stuck here because of that . also I was creating some filters /devices for mt65xx devices for sending you the zip mmc devices . :(
[SuperR Kitchen] SuperR.:
The following line in build.prop

ro.board.platform=

needs to read

ro.board.platform=mt****

in your example the **** should be 6572

Make that change in your build.prop and you should be good. If the line does not exist at all, add it.
[SuperR Kitchen] DarkHeart Z:
Thank you so much for help . Please give me a fix for recovery extraction not showing in the options :)
[SuperR Kitchen] SuperR.:
The boot.img must be named exactly "boot.img" and recovery needs to be exactly "recovery.img". If both exist in your main project directory you will be given a choice of which to work on. Make sure there are no capitals, misspellings, or spaces in the names.
[SuperR Kitchen] morissio:
Sorry guys, what about my problem with deodex (#412) ? I tryied but the rom didn't start :( it stuck on samsung logo..... no problem with odex.
[SuperR Kitchen] SuperR.:
Unfortunately I have no control over deodexing errors. You could open an issue on the smali/baksmali github. The kitchen is using the newest versions of both 2.1.0.
[SuperR Kitchen] morissio:
Oh sorry, this is my first rom.. I'm try to learn this "world" :)

bye!!
[SuperR Kitchen] psyriccio:
gitlab: psyriccio
[SuperR Kitchen] SuperR.:
v2.1.1.4 (Donate version)

Changes:

Fixed a few missing UI elements.

Rewrite of the smali/baksmali M deodex method using the new 2.2b.

New deodex method for N using the new smali/baksmali 2.2b.

Added oatdump and smali/baksmali labels in the menu for N roms.

Added notification and question regarding deletion of META-INF directory within apk files after deodexing N roms (now you get to choose).

v1.1.0.3 (Standard version)

Changes:

Fixed a few missing UI elements.

Rewrite of the smali/baksmali M deodex method using the new 2.2b.

New deodex method for N using the new smali/baksmali 2.2b.

Added oatdump and smali/baksmali labels in the menu for N roms.

Added notification and question regarding deletion of META-INF directory within apk files after deodexing N roms (now you get to choose).

NOTE: I have deodexed Nexus 5X 6.0 and 7.0, Nexus 6P 7.0, Samsung GS7 6.0, Note 5 6.0. I did not get a single error on any of them. I hope the new smali/baksmali method works out for everyone :)