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

In the latest version of the kitchen, you have the wrong version of SuperSU. The version with the fix for installing as part of a ROM zip is here: http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post64921761

Just found out in my new ROM zip :/
[SuperR Kitchen] Captain_Throwback:
[MENTION=5787964]SuperR.[/MENTION]

Just had another idea. Could you make it possible to add custom asserts to the ROM? i.e. an option to add the prop name, then the prop value and have it automatically added to the updater-script? I can obviously do it manually but figured I'd ask if it was possible to do it via magical scripting :).

If not, no worries. Thanks again for supporting all of us with this fantastic tool!
[SuperR Kitchen] bcrichster:
It's already possible because I asked him about that when he first started designing the kitchen and that's why there are so many empty UI print "." Sections in updater-script. Just pull script, fill/modify/replace and reinsert into META-INF folders to flash. [emoji41]

If I Help, just hit the Thanks button! :cool:

Sent from my Xper!m3nt - ZTE N9515
[SuperR Kitchen] SuperR.:
Can you paste an example of a full assert that you are trying to accomplish? By full assert I mean what the kitchen already produces plus the additions you are making manually. I think I know what you are looking for but it will be helpful to have an example to be sure. Thanks :)
[SuperR Kitchen] :
Test. Ignore please.
[SuperR Kitchen] goodman_east:
init.d support needed for my rom, can you add option for this please?
[SuperR Kitchen] Captain_Throwback:
This is already an option . . . you have to unpack boot.img to see it.
[SuperR Kitchen] SuperR.:
Would this work for you?

assert(getprop("ro.product.device") == "bullhead" || getprop("ro.build.product") == "bullhead" ||
getprop("ro.product.brand") == "google" ||
abort("This package is for \"bullhead\" devices; this is a \"" + getprop("ro.product.device") + "\"."););

In this example you would have entered "ro.product.brand" and "google" to create your custom assert.

edit: we could make it even easier and just enter ""ro.product.brand=google" to get the above assert.
[SuperR Kitchen] Captain_Throwback:
Certainly!

For example, the kitchen produces this as a device assert:

assert(getprop("ro.product.device") == "htc_m8whl" || getprop("ro.build.product") == "htc_m8whl" ||
abort("This package is for \"htc_m8whl\" devices; this is a \"" + getprop("ro.product.device") + "\"."););

In addition to that, I want to add an assert that checks the baseband of the user's device, to ensure they're running the proper firmware prior to installing the ROM. So my assert section becomes this:

assert(getprop("ro.product.device") == "htc_m8whl" || getprop("ro.build.product") == "htc_m8whl" ||
abort("This package is for \"htc_m8whl\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
[B]assert(getprop("ro.boot.baseband") == "1.09.20.1112" || ui_print(" "); abort("This ROM requires Marshmallow firmware. Based on your device's current baseband (" + getprop("ro.baseband") + "), you do not have this firmware installed. Please update your firmware prior to installing this ROM."););[/B]

I added a custom abort message and a blank line in there too, but you get the idea. The custom assert and abort message can follow the standard format that you already use. I did notice that when I added a custom assert below the one the Kitchen provided, that when I went to build the ROM, it got removed :(.
[SuperR Kitchen] bigrammy:
Does the Kitchen strip it out if you just add all that to the first assert(getprop instead of creating a new ones :confused:
[SuperR Kitchen] Slim2none4u:
Having a problem signing roms.

Fails every time. The rom still flashes fine though.

Any idea what could cause this?

Q&A section would be a great idea.

Thanks guys

Great work!
[SuperR Kitchen] Captain_Throwback:
That's not an option - it's a separate assert. Thus the reason for the different abort message. I'd have to do several combinations of and/or to capture all possible options.
[SuperR Kitchen] bigrammy:
Not sure if the Kitchen will kick this out or if the update binary will but I seen this used. ;)

#Ensuring your ROM only gets flashed to the intended device!!
file_getprop("/system/build.prop", "ro.build.fingerprint") == "[COLOR="blue"]Your build fingerprint here from build.prop[/COLOR]" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "[COLOR="blue"]This allows you to add another fingerprint version[/COLOR]" ||
abort("Package expects build fingerprint of [COLOR="Blue"]Your First Fingerprint version goes here[/COLOR] or [COLOR="blue"]Your Second Fingerprint version goes here[/COLOR]; this device has " + getprop("ro.build.fingerprint") + ".");
getprop("ro.product.device") == "Your device from build.prop" || abort("This package is for \"Your device\" devices; this is a \"" + getprop("ro.product.device") + "\".");

You could expand the file_getprop and aborts as much as you like. :fingers-crossed:
[SuperR Kitchen] Captain_Throwback:
That doesn't work when /system is wiped.

I don't understand what this has to do with the asserts from the kitchen? I wasn't looking for an alternative - I do have it working despite the kitchen deleting it . . . :rolleyes:
[SuperR Kitchen] SuperR.:
You probably don't have enough ram to sign the zip. Roms flash fine without signing, it is just an extra precaution.

The kitchen will delete all asserts from the updater-script many times through the process of completing all the things you ask the kitchen to do. If you want your assert edits to stick, edit the /kitchen/superr_device/00_project_files/assert file instead of the updater-script :)

This will all be irrelevant soon since I am almost finished adding the custom assert option. Not sure if I will get it finished tonight though.
[SuperR Kitchen] bigrammy:
What! :confused:

I don't know you lost me now :laugh:

Sorry for trying to help. :(
[SuperR Kitchen] SuperR.:
v1.0.2.3

Changes:

Replaced SuperSU with the embedded fix version.

Zipalign will now find all apk files in the project directory.

Added option to zipalign framework apk files.

Added option to include custom asserts.
[SuperR Kitchen] SuperR.:
v1.0.2.4

Changes:

Added option to reset asserts to default.

Avoid zipaligning files in the 00_project_files directory.
[SuperR Kitchen] bcrichster:
What does that mean and what is the difference between what we've been currently using?

If I Help, just hit the Thanks button! :cool:

Sent from my Xper!m3nt - ZTE N9515
[SuperR Kitchen] SuperR.:
It is the same SuperSU version, it just has the fix included that lets SuperSU display its own output when flashing from inside a rom zip. [MENTION=1162986]Captain_Throwback[/MENTION] pointed out I used the wrong one originally when I removed the "Installing SuperSU" text from the updater-script.
[SuperR Kitchen] bcrichster:
Excellent. This thing has certainly come a long way from the start! You work wonders, bro! [emoji41] PROPS

If I Help, just hit the Thanks button! :cool:

Sent from my Xper!m3nt - ZTE N9515
[SuperR Kitchen] asc1977:
hey guys

i build my rom for s6edge with marshmallow beta for s6edge. if i deodex my systemfiles i get one error but i have no idea what it means. can anybody help me please
[SuperR Kitchen] thereassaad:
Sorry but SuperR kitchen not deodexing tw mm full this from our testing so u need to deodexing it fully with sva tool v4.0
[SuperR Kitchen] asc1977:
Ok. Thx for answer. On lollipop this tool work great. Will it work in future?

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] SuperR.:
No guarantees, but maybe this will help.

v1.0.2.5

Changes:

Updated smali, baksmali, and oat2dex to the latest commits.
[SuperR Kitchen] asc1977:
I will try now and report

Gesendet von meinem SM-G925F mit Tapatalk

---------- Post added at 13:54 ---------- Previous post was at 13:03 ----------

Is there anywhere a log file where i can see deodexing worked fully or worked with x misstakes and what are the misstakes?

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] bcrichster:
Just scroll up in terminal after deodexing completes. [emoji41]

If I Help, just hit the Thanks button! :cool:

Sent from my Xper!m3nt - ZTE N9515
[SuperR Kitchen] asc1977:
Work also not but thx for helping. I tried with BatchApkTool and it worked. I dont know why. If you can look in this tool how it works there it was great.

Batch ApkTool 3.4.2 by BurSoft

I hope you get it to work because your kitchen is the best

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] bcrichster:
I'm loving the new Kitchen design and have a Request:

* Since the kitchen doesn't copy the extracted images to SD when extracting images from recovery, can you possibly add the "pull full flash" option to extraction menu while device is booted in recovery?

If I Help, just hit the Thanks button! :cool:

Sent from my Xper!m3nt - ZTE N9515
[SuperR Kitchen] SuperR.:
Didn't I make a tool for you for this specific purpose :p It is not really kitchen related.

However, I updated the one I made for you and put it on Bitbucket. Now it asks if you are booted to Android or custom recovery just like the Kitchen :)

https://bitbucket.org/superr/mmcblk0_extractor

http://xdaforums.com/chef-central/android/tool-mmcblk0-extractor-t3306883
[SuperR Kitchen] bcrichster:
Yes Sir, you did. ..but it copies the full flash to internal SD and I most certainly don't have that space on a massively debloated ROM. While I didn't see and img vs SD related issues when working from recovery and was hoping for taking advantage of that deal.. But still, Ty- again Sir for your excellent work as always! [emoji56]

If I Help, just hit the Thanks button! :cool:

Sent from my Xper!m3nt - ZTE N9515
[SuperR Kitchen] SuperR.:
I am not sure what you mean, but I started a thread for the mmcblk0 extractor tool so please post there for questions/problems with it. Thanks :)

http://xdaforums.com/chef-central/android/tool-mmcblk0-extractor-t3306883
[SuperR Kitchen] andy_zhang:
Can deodex Android MM?

vs985 China user
[SuperR Kitchen] SuperR.:
Yes, but it seems to have trouble with Samsung TW Marshmallow roms.
[SuperR Kitchen] fhem:
[MENTION=5787964]SuperR.[/MENTION] I'm using v 1.0.2.5 w/ latest N9 factory images. I put boot, sys, and vendor images in the project. Using meta data no problems. When I tried to use sparse-dat it will not finish zipping up everthing. Builds all the dat files but just sits and doesn't finish. I tried reclone 2 times and clean images but no go. So not sure what's up. I hope it's not me again. :D:confused::cool: or maybe I do hahaha.

Thanks for your continued support.
[SuperR Kitchen] asc1977:
Yes on marshmallow beta 6.0.1 problems with deodexing telephony-common.jar

All other works

Hope you can fix it any time for us.

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] andy_zhang:
Look forward to your program run weller

vs985 China user
[SuperR Kitchen] The Sickness:
[MENTION=5787964]SuperR.[/MENTION] Very nice work. I usually don't use kitchens, but yours may change my mind to make my building process a bit faster.

Thank you for sharing your work with us and your support
[SuperR Kitchen] SuperR.:
Please try this test version. I just deodexed the Note 5 6.0.1 with no errors. Before reporting back, please make sure it boots and works properly. I don't have a Samsung device to test on. Thanks

SuperRs_Kitchen_v1.0.2.5-test.zip

@ everyone - This test version uses oat2dex.jar to deodex M. All the other versions use smali/baksmali. I hope everyone tests this with M roms to make sure it works on all the roms that were already working. Thanks
[SuperR Kitchen] asc1977:
Thx. Great news. I will test asap and report but now i must go work :(

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] Androidwizzard:
Just wandering where you've got that firmware before official rollout - atm only beta testings on AT&T and a tmobile leak afaik.

Would be highly appreciated if you share your source ;)
[SuperR Kitchen] SuperR.:
I must correct myself. I deodexed Note 5 6.0, not 6.0.1. Someone sent a link to it at some point. The file name is ALL_N920TUVU2DOK5-M_CL6256935.zip if that helps. Sorry for the confusion.
[SuperR Kitchen] Androidwizzard:
No worry, it is the leaked one for tmobile USA, thx for explanation :highfive:
[SuperR Kitchen] asc1977:
I have a question before testing new build. If i use your tool for 5.1.1 roms my content of zip file is different as the content of my 6.0.1 zip file. Can someone explain me why please. Se attached screenshots. I miss the folder system which is now in system.new.dat and i cant add or change files easy with drag and drop in zip file like before. Sorry if it is a noob question [emoji3]

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] SuperR.:
Change perm type to set_metadata if you want the system folder.
[SuperR Kitchen] Mentalmuso:
[MENTION=718594]super[/MENTION]R i have been trying to build a rom with your tool for a while for the Galaxy S6, predominantly a MM 6.0.1 build. Ive tried all forms of Perm, like sparse dat, set_perm etc. but the rom doesnt boot after flashing. My original rom was a simple system.img dump. Imported into your tool and simply rebuilt without any mods. Do you have any insight for the S6 and Marshmallow?

Thanks!

--->
[SuperR Kitchen] asc1977:
Some posts above he posted a update for testing exactly for that problem. I have the same problem. But i didnt tested the new version

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] SuperR.:
I am trying to keep up, but I am not a Samsung guy so I don't have a clue :(

There are many knowledgeable Samsung users that swing by this thread so maybe they can help. They are the only reason this kitchen works for Samsung devices at all :)

The only things I would suggest is to try using the kitchen to extract your system.img and boot.img from the device. If the device has root, use the kitchen to remove it and re-add it after extracting. If the device has xposed, make sure to remove it before extracting the system.img from the device. Otherwise, I hope someone else can chime in and help out.

The test kitchen back a few posts is for testing M deodexing. He did not mention he deodexed with the kitchen.
[SuperR Kitchen] killer23d:
Bug Report.

Tried to use 1.0.2.5-test to deodex this: http://g3.letv.cn/186/21/81/letv-hd...3S-5.5.010S.zip?b=123456&platid=5&splatid=500

I see a lot of error during mv, cannot stat command. All files in Framework only shows 309 bytes

Used your old EOL batch deodex script, worked.
[SuperR Kitchen] SuperR.:
Just downloaded your zip, extracted, and deodexed without issue. There were a few harmless errors that will be fixed in the next version but I did not see any of the errors you mentioned. There must be something else going on with your setup.
[SuperR Kitchen] andy_zhang:
Thanx, in will try

vs985 China user
[SuperR Kitchen] Androidwizzard:
In my opinion it is very (too) early to make any conclusion about kitchen working properly for Samsung MM firmware.

Official releases are only available for S6 in Korea (G920 + G925).

Even if the building process through kitchen will succeed there's still no guarantee it can be flashed through existing custom recovery and/or with included kernel. Moreover flash should fail without MM bootloader too.

Conclusion: Samsung MM rom building is experimental atm and bug reports speculation (except deodexing process maybe).
[SuperR Kitchen] asc1977:
[MENTION=5787964]SuperR.[/MENTION]

V1.0.2.5-test deodex without problems on 6.0.1 samsung rom

Thx and hope you integrate this in your official project.

Edit: one bug is written by deodexing:

cat: /home/schwenn/Schreibtisch/SuperRs_Kitchen_v1.0.2.5-test/superr_test/00_project_files/logs/extramv.txt: file or folder not found

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] SuperR.:
Thanks for the feedback. The error you posted is completely harmless but has been fixed for the next release :)

Did you flash the deodexed system and boot it? Everything working properly?

I will integrate this into the main project once I get feedback from more people with other M devices.
[SuperR Kitchen] asc1977:
You get all feedbacks you want from me. Love your tool

Yes it boots nice but some aps fc. Syscope and smartmanager and something like com.android....... i forgot the name. But its from the 925k model and i didnt know the problems related to that. I cant go thrue the setup process because the last app com.android...

It has something to do with antivirus

I will do now a second try with the beta release 6.0.1 for 925f model

Gesendet von meinem SM-G925F mit Tapatalk

---------- Post added at 17:01 ---------- Previous post was at 16:57 ----------

[MENTION=5787964]SuperR.[/MENTION]

One more little bug

If i extract rom files from a backup all files in system/system and not in system

You understand my meaning?

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] thereassaad:
Some korean Apps its need to replace with international one ok

SuperR mate im really sorry as i can't test ur tool as im not Linux friendly as my latest Linux installation damaged everything on my laptop [emoji17][emoji17] so if i need anything related to Linux i ask my some friends to do it for me [emoji16][emoji16]
[SuperR Kitchen] SuperR.:
v1.0.2.6

Changes:

Fixed some harmless but ugly errors when deodexing.

Fixed an issue where some odex files in priv-app were not deleted if the apk is already deodexed.

Fixed issue when extracting from backup the system directory could end up in /system/system.

Some code cleanup.

The new test version below has the same changes but also has the test deodex M method from 1.0.2.5-test

SuperRs_Kitchen_v1.0.2.6-test.zip

edit: FYI, the test versions are available in the downloads area of this thread. You will see "Downloads" in the black bar if you scroll to the top.
[SuperR Kitchen] asc1977:
Will try asap. But now like yesterday on work :(

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] Speedo.thc:
Hi , thx for your job , very good.

- I have sucessfully built rom for :

- Huawei Y330 (System.tar) Jelly Bean

- Moto G4G (extract from device) Lollipop

- Huawei G620 S (extract from device) kitkat

All these with old version v0.9.6.7

today i did update to last version v1.0.2.6 ,and try it for Honor 7 project

- everything was OK for extract from TWRP backup

- but just when i want to built a full rom.zip , i have "something gone wrong ... check zip.log" message

- but no zip.log nowhere ???

- I did back to old version , ( only for the superr file and i keeped all the rest ) , it work.

I saw something about Java error when i did update , but i don't know what version to install to fix that.

Have you got a idea of what go wrong ??

Best regards

Edit : Ubuntu 14.04LTS on acer Aspire 11
[SuperR Kitchen] SuperR.:
The zip.log is located at /kitchen/superr_projectname/00_project_files/zip.log. If you paste the contents on pastebin or similar I will have a look.
[SuperR Kitchen] SuperR.:
v1.0.2.7

Changes:

Combined oat2dex and smali/baksmali methods for deodexing M roms.

Added error check while deodexing M roms- if oat2dex fails, try baksmali/smali.

Added separate log for deodex.

After extensive M deodex testing, I have determined that neither oat2dex nor smali/baksmali methods work for all files. However, they fail on different things. The result is the best of both worlds. For each file, we try to deodex with oat2dex first. If it fails, then we try smali/baksmali. If you get an error on your screen while deodexing, please know that both of the only two known methods have been attempted and there is nothing else I can do.

I have also determined that the test zips are completely useless as I don't get enough feedback. The new plan is to release my tests in the main branch and fix things that get broken.

The good news here is that I deodexed many M firmwares without a single error :)
[SuperR Kitchen] ambasadii:
Hi [MENTION=5787964]SuperR.[/MENTION]

what about corrupted symlinks and set_metadata while unpack Android M system.img ?

for example there are some differences with the openGl and openGles .so files and symlinks inside the system/vendor folder.

have any idea ?
[SuperR Kitchen] :
I think part of the problem is the lack of devices with mm at the moment. Not many Sammy people have mm yet and the ones that do are only test release. Personally I can't thank you enough for everything you've done for the community
[SuperR Kitchen] SuperR.:
I am not sure what you mean. There should not be any symlinks in your rom directories after extracting. The kitchen converts existing symlinks in the rom directories to symlink lines in the updater-script, then removes the symlinks from the rom directories. When you build a system.img or use sparse_dat or raw_img as the perm types, the symlinks are recreated in the rom directories and removed again after the process is complete.
[SuperR Kitchen] ambasadii:
ok but there is a problem becouse i try it many times to create new system.img form android m bulid and always wifi won't work after flash i think beacouse kitchen make a bad symlinks so new system.img is corrupted.
[SuperR Kitchen] SuperR.:
I am curious...of all the things that could cause wifi to not work, why guess the kitchen creates bad symlinks? I ask because it is highly unlikely unless the original system.img you extracted had bad symlinks to begin with. If you have some verifiable evidence the kitchen is creating bad symlinks, please post it and I will take a look :)
[SuperR Kitchen] ambasadii:
ok mate i will ;) thanks for tips
[SuperR Kitchen] JochenP:
hallo and many thanks for your work first.

I've worked through all posts but i have no idea how to use 'debloat Rom' and 'custom debloat menu'.

I thought i can simply remove or add files but they have to be registered, right? (media files no problem)

Please give me a hint for removing and adding files.

Thanks in advance
[SuperR Kitchen] mjraogr:
Nice work, thanks
[SuperR Kitchen] asc1977:
Hi [MENTION=5787964]SuperR.[/MENTION]

i haded now time to test your new test build from yesterday with a system dump from 925F marshmallow. but i have always problems. the rom is only deodexed what is working finde but after installation of rom also like before some things fc and didnt let the phone setup

unfortunately....

syscope

samsungsetupwizard

smartcardmanager

...has stopped

if i take it from a original firmware of samsung odin file al works and boots without wifi working

i read anywhere also that there are problems with permissions

i post you here the part of my updaterscript what was created of your tool and hope it helps with analyse sym and permissios
[SuperR Kitchen] SuperR.:
There are 2 options in the debloat menu (besides knox which is self explanatory):

1) Debloat ROM

This option removes all files included in the kitchens standard bloat list file - /kitchen/tools/root/bloat

2) Custom Debloat

This option removes all files included in the bloat_custom file - /kitchen/tools/root/bloat_custom

This file is empty by default and is there for you to add whatever you want to remove. You can either add everything you want to remove and use only option 2, or you can add new files here and use option 1 and 2.

I suggest you take a look at /kitchen/tools/root/bloat to see the format of the listed bloat files. Use the same format for the bloat_custom file.

When you use either option, the files are not deleted. Instead they are moved to the 00_project_files directory in case you want to restore them later.
[SuperR Kitchen] SuperR.:
First, don't use set_perm unless your rom is Jelly Bean or earlier. Try set_metadata.

Second, use kitchen v1.0.2.7 just posted today. It might help with your issues (if they are deodex related).

Third, try all of this without deodexing first and make sure everything works properly. Then deodex so you know what is causing the problem.