yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] SuperR.:
v2.1.0.9 (Donate version)

Changes:

Completely new Nougat deodex method using AOSP oatdump and dexrepair by [MENTION=407497]anestis[/MENTION]b.

Already deodexed files will now show in green during all deodex methods.

Updated package_extract_dir function used in update-binary conversion.

v1.0.9.8 (Standard version)

Changes:

Completely new Nougat deodex method using AOSP oatdump and dexrepair by [MENTION=407497]anestis[/MENTION]b.

Already deodexed files will now show in green during all deodex methods.

NOTE: The new Nougat deodex method requires an additional 70MB download. The kitchen will take care of downloading and installing, just letting you know. Nothing will be downloaded or installed until you try to deodex your first Nougat ROM. Then you will be asked.

I know I have made it clear to not say deodexing does not work, but in this case I would like some feedback about the new Nougat deodexer.

Thanks to [MENTION=407497]anestis[/MENTION]b for permission to use his prebuilt binaries (oatdump and dexrepair) which he worked very hard on and makes this possible :)

Thanks to [MENTION=2915683]BaNkS[/MENTION] for bringing this option to the table. He went out of his way to point it out, send me a link, and test early kitchen versions.
[SuperR Kitchen] serch826:
Works fine. thanks!
[SuperR Kitchen] TheLogicalGamer:
As far as the moving the files issue I had. It was because the boot.img was unpacked. Repacked the boot.img and it moves fine.
[SuperR Kitchen] oak:
Hello superr,

I donated again (and will continue to do so), can you please try to grant me access to the donation version again - we had trouble last time. I am user [MENTION=333246]oak[/MENTION] on GitLab.

I don't really need the donation version, but would like to give it a try. I also want to support your great kitchen. I use it a lot and it is just awesome. Thanks in advance.
[SuperR Kitchen] SuperR.:
Wow, thank you :) Unfortunately I am still not able to find your gitlab user. Please PM the email address associated with your gitlab account. Hopefully that will work to find you.
[SuperR Kitchen] oak:
Thanks. I'm all set.
[SuperR Kitchen] nightcrow:
Thank you for this amazing kitchen, donated! My Gitlab username is [MENTION=838787]nightcrow[/MENTION]
[SuperR Kitchen] skaggmuff:
Hi!

I tested the free version and trying to deodex latest marshmallow .291 for xperia z2, but it won't work.

I created a new project and moved the system.ext4 and kernel.elf to the working directory.. unpacked it and then i tried deodex but it doesn't work.. i get a message that some thing's can't be deodexed.. i looked in the fail log and it seems like every odex file in app and priv-app can't be found.

Am i doing something wrong?

I run linux mint 18 x64
[SuperR Kitchen] SuperR.:
The odex files are probably compressed in a way the kitchen does not recognize. Send a link to your firmware and I will take a look.
[SuperR Kitchen] SuperR.:
v2.1.1.0 (Donate version)

Changes:

Completely new Marshmallow deodex method using AOSP oatdump and dexrepair by [MENTION=407497]anestis[/MENTION]b.

v1.0.9.9 (Standard version)

Changes:

Completely new Marshmallow deodex method using AOSP oatdump and dexrepair by [MENTION=407497]anestis[/MENTION]b.

NOTE: The new Marshmallow deodex method is based on the new Nougat deodex method introduced in the last kitchen version. Since the oat version is different from N, I had to compile oatdump from M AOSP source and it appears to be working great. The one thing I did not do was flash an oatdump deodexed M rom. Please let me know how it goes. I was able to deodex Samsung gs7 with no errors so I am very hopeful :) Choose option 3 when deodexing M to give it a try. Like the N oatdump method, there is an additional download (about 105MB) the kitchen will take care of.
[SuperR Kitchen] skaggmuff:
Okay, I downloaded the firmware with xperifirm so i don't have a link.

It's the swedish version that called Telenor 23.5.A.1.291_R11D in xperifirm.
[SuperR Kitchen] ShinySide:
Rule one to firmware help- upload your firmware to a decent site.
[SuperR Kitchen] dbarrett480:
Donated! My gitlab name is "dbswoot". Thanks!
[SuperR Kitchen] SuperR.:
Sorry, but I can't do anything to help you without the firmware.

Added, thanks :)
[SuperR Kitchen] Mysteryagr:
What is missing?

Hello all, I need a little help if someone can help me.

I have lubuntu linux running on a 32 bit machine, I installed kitchen and all dependencies it asked me to install, and kitchen is working fine hoowever I have one problem; I can't unpack system sparse image using kitchen and it doesn't create symlinks, I have to unpack system using any other tool.

Could someone point me to the missing dependencies?
[SuperR Kitchen] kyledowling:
What are the dependencies needed? I`m running bash on windows and the Kitchen force closes before it shows any sort of GUI. I am also fairly new this and open to any help.
[SuperR Kitchen] Mysteryagr:
I think I read on the OP that this kitchen isn't for windows xD
[SuperR Kitchen] SuperR.:
I can't troubleshoot all Linux, so I suggest trying Ubuntu 16.04 since that is what I test/develop on. 64-bit is highly recommended as there are now several features that will only work on 64-bit systems. 32-bit support is dropping very quickly everywhere. For example, Chrome is no longer developed for 32-bit systems.

If 64-bit Linux is not an option for you, 32-bit Ubuntu 16.04 will be able to run the 32-bit binaries from the kitchen repo without issue. It will probably fix your symlink issue as well, since you seem to be the only one with these issues.
[SuperR Kitchen] Tulsadiver:
Hi, I have a dual boot computer with the main part windows 7 and the other Linux Mint. I've used superR kitchen for quite a while for deodexing Roms mainly. I installed your latest version so I could get Nougat deodexed. Everything seemed like it was working fine. Extra files downloaded like the should and it seemed like it worked. However, Meta-inf was left out of all the apk's. Any idea what I did wrong? I tried twice. Once pulling everything from my phone. The other with the firmware update file. I have a Nexus 5x.
[SuperR Kitchen] SuperR.:
META-INF is removed on purpose when deodexing N ROMs. Apparently, N uses a newer signing method (V2) and apps will crash if there are any changes. Removing META-INF should solve this problem and leave the apps unsigned. META-INF remains in the jar files in framework however.
[SuperR Kitchen] Mysteryagr:
Okay, thanks a lot :D

---------- Post added at 10:03 PM ---------- Previous post was at 09:28 PM ----------

@SuperR

If someone has a problem similar to mine, I just converted Huawei sparse image to normal image using simg2img.exe on windows

Then I unpacked it using your kitchen on lubuntu, it worked fine, it unpacked the rom and generated symlinks.

I'm posting this to let you know a solution for this problem....

Thanks a lot for your perfect kitchen :D
[SuperR Kitchen] kyledowling:
With the Bash on Ubuntu on Windows thing I want to give it all possible ways to succeed. I've had it working before but I had to wipe my computer.
[SuperR Kitchen] scrappy610:
I haven't gotten the bash windows thing to work. For simplicity, you could dual boot or use virtual box. That being said, with virtual box you would need to pm myself or someone else using it for help. The only ways I know the dev supports is linux via dual boot or stand alone os as stated in the op.

Please don't take that as being rude, I was just trying to give some info to try to help in the event that you get no response and/or a response you don't like. [emoji4]
[SuperR Kitchen] bcrichster:
Win10 bash will not (currently) build Android yet

Sent from CM12.1 *N9515*
[SuperR Kitchen] kyledowling:
Thank you for the response. My computer has the new uefi and doesn't want to boot from the only USB port. To make it even worse there's only 32gb of storage.
[SuperR Kitchen] scrappy610:
I went through the same, had to turn off fastboot and secure boot in the uefi menu. Then use Rufus to make your bootable USB. 32gb is not a lot at all.
[SuperR Kitchen] SuperR.:
v2.1.1.1 (Donate version)

Changes:

Added support for deodexing Xperia Z2 Marshmallow ROMS.

Removed all Windows Subsystem for Linux (WSL) restrictions.

v1.1.0.0 (Standard version)

Changes:

Added support for deodexing Xperia Z2 Marshmallow ROMS.

Removed all Windows Subsystem for Linux (WSL) restrictions.

Possibly made the kitchen more friendly to WSL and CYGWIN (I do not support these in any way and have not tested).

[MENTION=5929125]skaggmuff[/MENTION] - This should sort out your deodexing issues

[MENTION=7288467]kyledowling[/MENTION] - No promises or support will be provided, but there is a better chance of success now with Windows Subsystem for Linux (formerly known as Bash on Ubuntu on Windows). You may need to install all the dependencies the kitchen lists manually. I am not sure if the auto-installer will take care of it. I read recently that you can use openjre in WSL now so you may have some luck. As far as I know you will not be able to extract img files at all, but I removed the restriction anyway and post a warning message. Even though I won't support WSL at the moment, I am curious about your results so please let us know :)
[SuperR Kitchen] shoey63:
Extracting a system.ext4 image with 7zip as administrator will unpack the image nicely, including symlinks. Other types of images could be more problematic...
[SuperR Kitchen] luigimak:
[MENTION=5787964]SuperR.[/MENTION] full deodex OxygenOS 3.5.2 runs on OnePlus3 :victory:

Great, great job!!!!
[SuperR Kitchen] kyledowling:
Will update and report back!

Edit: Had to exit the Kitchen and install 7zip and jre through sudo apt-get install. Then had to to add Java 8 repo and install java-8 using this linkhttp://tecadmin.net/install-oracle-java-8-jdk-8-ubuntu-via-ppa/. Went back into the kitchen and it built and installed binaries. Successfully got to new project screen. Will test more later.
[SuperR Kitchen] Mysteryagr:
There are always tools to convert system.img

People can deal with this :D
[SuperR Kitchen] skaggmuff:
Okay, thank you, i will try it when i have some time over :)
[SuperR Kitchen] syztemlord:
I've just tried making some changes to a Marshmallow rom but when I flash it I get the error:

system partition has unexpected contents after ota update

Any ideas what I may of done wrong?
[SuperR Kitchen] TheLogicalGamer:
What's your perm type?
[SuperR Kitchen] Tulsadiver:
It crashes no matter what. Even if you just decompile and recompile with no changes. There was no problem with doing changes to it before it was deodexed.
[SuperR Kitchen] serch826:
I have also seen that , for example, before I could change the stock Android N SystemUI with kitchen , but after 2 or 3 updates back this apk crash or works bad (no Statusbar and Navbar) after flashing the ROM, have to mention that no errors with APKTOOL and no matter what signing method I use.

I'm not saying it's wrong with kitchen, just leave my experience of that issue.
[SuperR Kitchen] Mysteryagr:
New deodexing method doesn't work on 32 bit machine :(
[SuperR Kitchen] jaylence:
New deodexing method works on my Galaxy S6 Edge (G925F).

Built Rom also flashed and booted successfully.

I just ran into one problem. After finishing the initial setup, there is this popup telling me that I'm running out of memory.
[SuperR Kitchen] SuperR.:
See post #4 for some answers I need to be able to help you

If you are comfortable making a simple edit in the kitchen script, you could try skipping the step where we delete META-INF from the apks. Make sure you use a Linux text editor such as gedit to make the changes.

Add a "#" to the front of this this line in the superr file located in the main kitchen directory:

$p7z d $deoappdir/$app/$app.apk META-INF >> $logs/zip.log

so it looks like this:

# $p7z d $deoappdir/$app/$app.apk META-INF >> $logs/zip.log

Save the file, restart the kitchen, and try deodexing again. Honestly I am not familiar at all with the new signing method so we may need to try some things before we get it working properly.

Regarding apktool, I am not sure what you mean. Are you saying that apktool makes the apks work after deodexing if you decompile/recompie/sign? If so, did you use the apktools kitchen plugin to do it?

That is correct. the oatdump binaries are 64-bit only. You should have gotten a message telling you it will not work before proceeding.

Deodexing Samsung M roms has been a struggle for a while now. I am very happy to hear it is working :)

Regarding the out of memory popup, did it show in the terminal as a kitchen message or was it a system message? The kitchen checks for memory before deodexing to make sure you have enough, but that was primarily for oat2dex and smali/baksmali methods since they use a ton of memory. If the message was in the terminal, you can ignore it for now if you use oatdump. The oatdump method does not use so much memory and I may remove all other methods at some point if the oatdump method proves to work for all devices.
[SuperR Kitchen] jaylence:
Sorry, I wasn't very clear earlier. I had no problem with deodexing using the new oatdump.

The "running out of memory" popup was on my phone's.

After finishing the Custom Deodexed Rom's initial setup on my phone, I got a notification that my phone is running out of memory despite the fact that I still have 14gb of free memory.

I gave it a second try. Re-built the custom deodexed rom, reflashed and got the same result.

I never had this kind of popup with Odex Rom built using your kitchen.
[SuperR Kitchen] SuperR.:
This is a new one for me too. I am not certain it is because of the deodexing. Is there any way to try the exact same rom without deodexing? When it says out of memory, I assume it refers to ram so your 14GB of free space would be irrelevant. What happens after the popup is closed? Does the system work? If so check out your memory usage in Android settings.
[SuperR Kitchen] serch826:
I mean Apktool with the Kitchen. recompile and compiling works fine
[SuperR Kitchen] jaylence:
I currently have 2 versions of the same Rom (Odex, and Deodexed).

The "running out of memory" only appears in Deodexed version. The popup message can't be closed. It just resides in the notification bar (status bar). Pulling down the notification bar and swiping on the message doesn't help.

The popup message appears to have no effect on the performance, everything works great.
[SuperR Kitchen] SuperR.:
Unfortunately I can still only suggest that you try the edit I suggested before so the kitchen does not delete META-INF. It is worth a try. You could also try signing the apks to see if that helps, but that is a lot of work since the kitchen does not currently automate it. If re-signing all the apks works, I will automate it in a future version. However I don't know if the current signapk.jar will handle N apks, or if N will handle apks signed with the current signapk.jar. I guess we will find out one way or another :)

I have no idea why that is happening. I hope somebody can help you figure it out. If you do get it figured out, please let me know the solution.
[SuperR Kitchen] serch826:
Thanks SuperR, i've tested with your suggestion (# ...) but didn't helped, otherwise i will continues to test with signing, thanks agin:good:
[SuperR Kitchen] :
Do you know the size of your system partition? And what is the size of your deodexed rom unzipped?
[SuperR Kitchen] jaylence:
Details are as follows:

Zipped Deodexed Rom : 1.4gb

Unzipped Deodexed Rom : 2.32gb

S6E Alotted System Memory: 7gb

For the the system partition, I'm unable to get its exact size using Terminal emulator.
[SuperR Kitchen] :
Hmm it's not your system partition is too small then. I've had that with the American variants in the past, thier system partition was smaller than the international variants and rom wouldn't boot because of it
[SuperR Kitchen] SuperR.:
I compiled signapk.jar that includes Scheme V2 using AOSP Nougat sources and created a plugin to sign all unsigned apk files in N roms. It will only work on 64-bit Linux. It will skip any files that have a META-INF directory, so make sure you do a fresh N deodex and then run this plugin to sign the apks. Again, I don't know if this will help but it might.

If re-signing the apks after deodexing N fixes the issues, I will include it in the deodexing process. Let me know how it goes :)

signapk_v2.zip
[SuperR Kitchen] matamata15c:
Hello friend [MENTION=718594]super[/MENTION]R you could add the Spanish language to this excellent program? thanks

Enviado desde mi hi6210sft mediante Tapatalk
[SuperR Kitchen] bcrichster:
This is an English forum, sorry. [emoji41]

Sent from CM12.1 *N9515*
[SuperR Kitchen] serch826:
SuperR, first thank you for your patience when you help os , I tested the following: deodexed a NPD90G Rom and used your Signapk plugin , after this decompile and modded SystemUI , then compiled without problems, flashed modded apk in a Stock NPD90G , but it did not worked , no statusbar and navbar .

Tested with a SystemUI from a Deodexed AOSP ROM (from XDA) decompiled, moded and compiled back, that worked well w/o any issue after flashing in the Rom.:good:

So I do not know what to say , it seems that there is nothing to do with Kitchen, but before you could do that too with Odex Rom, that is very stranger.:confused:

Thanks a lot again.
[SuperR Kitchen] matamata15c:
If it would be a good idea but would have to ask the creator who thinks

Enviado desde mi hi6210sft mediante Tapatalk
[SuperR Kitchen] Macguyver1980:
Issue when building

I'm customizing a ROM for ZUK Z1 Pro from TWRP backup I did, I did all without problems but when I start building I've error:

ERROR:

Something went wrong. Check the zip.log for errors.

Press ENTER to return to ROM Tools

and in zip.log file only:

"7-Zip [32] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21

p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,32 bits,8 CPUs Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (206A7),ASM,AES-NI)

Scanning the drive:"

Don't know if permission issue or...?
[SuperR Kitchen] bcrichster:
Need more detail to assist, read post #4

Sent from CM12.1 *N9515*
[SuperR Kitchen] Macguyver1980:
To give more details, apart of rooting actions, adding Busybox and standard functions applied, I modified build.prop file, overwrite some media sound files and add some others, changed the bootanimation... Then when trying to build have this error... nothing more. Does it come from the 7-Zip version? From an access write property of some files or...? Were there anyone having already this issue? How solved? Thanks for help

PS: from extract in beginning I had this possible list:

Extract Options:

1) system.ext4.win001

2) system.ext4.win000.md5

3) system.ext4.win001.md5

4) data.ext4.win.md5

5) system.info

6) data.ext4.win

7) system.ext4.win000

8) data.info

And was choosing 7 option, it's Android 6.0.1 ROM version for ZUK Z2 Pro, and from parameters it seems to have found, it gives name z2_row model... 64 bits. Was choosing metadata way.

Edit: I tried again from beginning and had once choosing metadata method these quick message:

Preparing updater-script ...

cpio: .subackup/0000_charger.fstab.qcom: Cannot open: Permission denied

cpio: .subackup/0001_file_contexts: Cannot open: Permission denied

cpio: .subackup/0002_fstab.qcom: Cannot open: Permission denied

cpio: .subackup/0003_init.environ.rc: Cannot open: Permission denied

cpio: .subackup/0004_init.rc: Cannot open: Permission denied

cpio: .subackup/0005_sepolicy: Cannot open: Permission denied

cpio: .subackup/0006_verity_key: Cannot open: Permission denied

cpio: .subackup/index: Cannot open: Permission denied

...

Then I tried with RAW mode and connected to ADB the phone when building for parameters and had this error:

* daemon started successfully *

./superr: line 5124: #blocks

98304

524288

4096

4052

120602624

8

32768

262144

1024

512

128

128

512

393216

119912140

4096

4052

131072

32

4

1024

32768

2048

2048

4

4194304

512

512

2048

2048

512

512

2048

16

512

512

97280

16384

1024

32768

1024

1024

65536

3145728

65536

4

1024

512

512

256

256

256

256

256

256

4

33424

2048 * 1024: syntax error: operand expected (error token is "#blocks

...

Make sure your system partition size is correct and

that the system directory is not too big to fit.

I had also when extracting in beginning this message but I think without relation with problem when building...

Extracting to zukv140 ...

mv: cannot move '/home/michael/Desktop/superrs-kitchen/superr_zukv140/system/system/app' to '/home/michael/Desktop/superrs-kitchen/superr_zukv140/system/app': Directory not empty
[SuperR Kitchen] SuperR.:
I am working on the possibility to add language files. It is a lot of work since I did not start this way so it will take some time. No guarantees.

It was suggested to look at post #4 for the info I need to help you. I suggest you look again so you can provide the answers I need. The main ones you left out are OS, 32 or 64-bit, and firmware upload.
[SuperR Kitchen] matamata15c:
Enviado desde mi hi6210sft mediante Tapatalk
[SuperR Kitchen] SuperR.:
If I get the work finished on the English language file, you will be able to translate it and create a Spanish language file. This will be true for all languages that can be written in a standard text file. I will not be doing any of the translations, I am only setting up the framework for the use of language files. That is of course if I ever get it finished. Unfortunately, it is a lot of tedious work since I did not start writing the kitchen with this in mind.
[SuperR Kitchen] matamata15c:
It is correct this is not easy and ever growing all with new features

Enviado desde mi hi6210sft mediante Tapatalk
[SuperR Kitchen] serch826:
ERRORS with update and Oatdump dowload

No problem at all
[SuperR Kitchen] kasi5471:
The kitchen works without Problems i build my 3rd rom with it. NOTE 4 and S7 ALL WORKS great [emoji106] [emoji106] [emoji106]
[SuperR Kitchen] Driver007:
Hi, I have big problem whit my 5x, motherboard was changed and now I can't unlock bootloader after reboot it locks again, it's some hardware problem, only fastboot flashing is working...

I was guessing is it possible to root system.img that it would boot? tried whit kitchen but it reboots to stock recovery.
[SuperR Kitchen] bcrichster:
You were supposed to use a custom recovery (like TWRP)

Sent from CM12.1 *N9515*
[SuperR Kitchen] orgulloso4202:
Sorry for the dumb question, but if I pull a rom from my phone with kitchen to use as base, wouldn't it include all the apps, script and mods I have on the phone? Trying to learn if that's the way to add apps, script, xposed when building a rom. (newbee) thanks
[SuperR Kitchen] Driver007:
I known, not dumb... My bootloader relocks itself after restart and twrp not working because of permissions or something it bootloops, only stock recovery works..

Nevermind, found a solution to insall whitout twrp.
[SuperR Kitchen] Macguyver1980:
Related to my problem and extra info I posted, there is no idea of solution for me...?

Link to the source files I'm using: https://mega.nz/#F!O1REyaaD
[SuperR Kitchen] Frankbrazillian:
Thank you very much Superr, for this wonderful tool. I already deodexed an entire Marshmallow rom, with your kitchen. But like one guy who have posted 2 pages before, i'm getting the same notification on status bar, saying Storage space running out. I already donate to you! My username is the same as XDA (Frankbrazillian). Thank's again!
[SuperR Kitchen] SuperR.:
A system dump includes things in system. If you have mods in system they will be in the system dump. Apps installed from the Play Store are in data so they will not be included.

I will take a look when I get a chance.

edit: looks like the link needs a decryption key

Added, thanks :)

Regarding your out of memory issue, as I said before, I have no idea. If you figure out how to fix it please let me know.
[SuperR Kitchen] Frankbrazillian:
Ok Thank's! I will try with another rom, to see if i got the same problem. :)
[SuperR Kitchen] orgulloso4202:
Thanks. I was just surprised not to see any when I flashed the rom just to see if it loaded.