yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] SuperR.:
v0.9.2.2

Changes:

Updated SuperSU to v2.52 BETA. May help with Marshmallow root issues.

Fixed Marshmallow deodex script.

Currently, it deodexes the nexus 6 (shamu) stock Marshmallow rom completely with the exception of 2 apps:

/system/app/EditorsSheets

/system/app/EditorsSlides

These apps have classes3.dex which [MENTION=1299419]JesusFreke[/MENTION] is working to get fixed. Huge thanks to him for smali/baksmali and all of the support he has given to myself and many others :)
[SuperR Kitchen] Er. Aditya:
some help needed , last night i moved to gnome and started facing package issue .... the thing is the 2 package it shows missing 1 is installed and other is unable to locate , any help guys
[SuperR Kitchen] SuperR.:
Try uninstalling mawk to sort out the gawk issue.

7za comes from the pz7ip-full package.
[SuperR Kitchen] Er. Aditya:
i think thats about it :D

i had installed full package via

p7zip-full p7zip-rar

still it shows thi..il try uninstalling mawk

thanks again dev for your work

edit : sudo apt-get --purge remove mawk tried this and again tried to install gawk but still same
[SuperR Kitchen] SuperR.:
The kitchen is using "which" to check for dependencies. Try typing the following in a terminal:

which gawk
which 7za

Maybe which is not installed or functioning properly. I may need to adjust the kitchen to use a different method under certain circumstances.
[SuperR Kitchen] Er. Aditya:
thankyou so much but i got this result i dont know if they are correct or what

bhuvi@bhuvi:~/kitchen$ which gawk
/usr/bin/gawk
bhuvi@bhuvi:~/kitchen$ which 7za
/usr/bin/7za

edit : its fixed now there are 2 things that could have caused it

1. i renamed the kitchen's name to simple kitchen before installing the required packaged

2. i removed the folder from home and now copy pasted again

so either renaming the name was at fault or some other issue
[SuperR Kitchen] bcrichster:
edit : its fixed now there are 2 things that could have caused it

1. i renamed the kitchen's name to simple kitchen before installing the required packaged

2. i removed the folder from home and now copy pasted again

so either renaming the name was at fault or some other issue[/QUOTE]

Good catch!

Gratefully sent from my Rooted Tesla N9510
[SuperR Kitchen] jodge:
i just found this awsome prog :) thx nice work.

I want to root and deodex my noname MTK cpu rom 4.4.2 just for fun. But it seems just the busybox installed coorectly. No su binary in the xbin no Superuser.apk...etc

If re-run the app it say rooted but nothing :(

any idea?

ps. deodex worked
[SuperR Kitchen] SuperR.:
The kitchen does not add root files to the system directory. Instead it adds the SuperSU.zip to the supersu directory found in your project directory. Root is added when you flash.
[SuperR Kitchen] SuperR.:
v0.9.2.3

Changes:

Marshmallow deodex should be fixed now. [MENTION=1299419]JesusFreke[/MENTION] got everything sorted out so now the Nexus 6 (shamu) completely deodexes. Just need someone to test it since I don't have a Nexus 6.

You will be asked if you want to extract the cache.img if it exists in the project directory and you are extracting from a system.img.

Fixed delete project - Will now ask if you want to delete the corresponding devices/device/project_.

Regarding the hidden.img, I have no idea where to put the included files in the ROM. If someone can shed some light I will make the change.
[SuperR Kitchen] jodge:
thx for the reply.

My main goal is root this little x$* :D bcose i'v tried every other root, prog, solution, apk... literally everthing but no success. No available custom reco. Just the spt tool and the system.img. I'm able to read and write back the raw system.img via service port without root. Do you have any idea for this case?

thx
[SuperR Kitchen] Er. Aditya:
you my man...are my hero :D
[SuperR Kitchen] brainvision:
mmm... so what about deoxing? Should I go straight on or should I first remove the arm ones?
[SuperR Kitchen] Thorvic777:
You should try both methods... if it works just with the 64 would be fine.. but if there are dependencies better not to remove them.. test and let us know

Enviado desde mi SM-G800H mediante Tapatalk
[SuperR Kitchen] SuperR.:
There is no need to remove anything before deodexing. In your case, the kitchen will use arm64 if it exists and arm if it doesn't.
[SuperR Kitchen] brainvision:
thanks..

So I debloated the system and then tried to deodex: with the latest SmaliEx commit it failed as with my other device, so services.jar, framework.jar and a few apks; with SmaliEx oat2dex v0.86 it works fine and gives no errors; I also flashed a custom zip (app. priv-app and framework) and it booted; seems to work nice but I did not deeply tested it.

I have btw suggestions and a question, if you please, both related to custom zip feature..

This tablet I'm working on has a CPU from MediaTek: I noticed they put some apps in

/system/vendor/operator/app/

and in

/system/plugin

(the other tablet I deodexed - except framework dir 'cause it always failed - uses

/system/app/dataapp/

for add a few apps, often bloatware but sometimes not, so still needed). Those apps are deoxed but we have no way to put it in custom zip, we have to manually do that after the zip is created; maybe it could be useful to add support to custom directories (not only

/data/app

)..

Also when creating custom zip I think we should have a choice to add in the updater-script file lines to delete original directories that we are going to flash, otherwise - to make an example - if we remove from SuperR's project an app from

/system/priv-app

and then we flash the custom zip, we will still have that app once we boot!

Hope I was able to explain, if not I mean something like

ui_print("Deleting Folders..");
delete_recursive("/system/app");
delete_recursive("/system/framework");
delete_recursive("/system/priv-app");

Last but not least, my question about what I think could be a little bug..

I choose set_metadata as permission type in this project, but the custom zip has set_perm in the updater-script, as you see

ui_print("Setting Permissions...");
ui_print(" ");
set_perm_recursive(0, 0, 0755, 0644, "/system/app");
set_perm_recursive(0, 0, 0755, 0644, "/system/framework");
set_perm_recursive(0, 0, 0755, 0644, "/system/priv-app");

Don't know if your force this for some reason, so I will not manually change it
[SuperR Kitchen] bluflight:
Combination of smali/backsmali + zipalign solved memory issue, all work fine now :good:
[SuperR Kitchen] bcrichster:
This kitchen already does a lot.. I don't think it should hold the hand on every single thing, so updater-script editing/Modz shouldn't kill ya to type a few words & place back in zip. At least you know what changes you need, that's how you make it yours. No offense, but try putting in a bit more effort to make your customized zip. The Kitchen isn't A.I. and shouldn't have to act like it can read minds.. I apologize for any offense but If I am out of place in my post, someone will tell me. [emoji41]

Sent from my N9515's cm12.1
[SuperR Kitchen] brainvision:
no offense at all, don't worry!

I wanted to share the issue I found and those two suggestions that would had been useful in that case, if the dev wants or doesn't want to add, not a problem at all!

but - on a side note - the delete folder is already available in other kitchens, when creating flashable zip for unique directories, the reason why is indeed pretty obvious ;)
[SuperR Kitchen] bcrichster:
WOOOWW.. this Kitchen has come a long way from the 12Mb it started with, [MENTION=5787964]SuperR.[/MENTION] ! It's now 75Mb and the improvements continue. Nice work, bro.. been a while since I done a fresh pull
[SuperR Kitchen] KaMyKaSii:
Hello, I had already tested deodex my rom but always with bootloop. Now I tried it again and it worked partially, I believe thanks to the change from 7-zip apk compression to aapt, thanks for that. I tried oatdump, smali and oat2dex (Just official, last commit had some errors that discouraged me from making zip and test), all with zipalign, but with all I'm suffering with the problem "com.android.phone stopped working". This app package refers to "/system/priv-app/TelephonyProvider/", right? Should I trim it from the workbook before making the deodex and paste it after it's done? Is it okay to have a single app continue odexed? And I also read the post from someone who was having trouble receiving SMS and the OP suggested moving the "/system/plugin/" folder before deodex and restoring it shortly after. Does this also apply to my problem? And which deodex method do you think is best for Marshamallow (6.0)? Thanks for the great tool and the support

Latest free version of Kitchen, Linux Mint 18 'Sarah' MATE 64-bit, Quantum Go 4G (a mediatek device), Android 6.0
[SuperR Kitchen] SuperR.:
v2.1.3.2 (Donate version)

Changes:

Updated SuperSU to v2.78-SR4.

Added delete existing directories to updater-script when creating a custom zip.

cygwin - Added notice on first run about cygwin being slower than native Linux.

cygwin - Do not allow zip signing until it gets fixed.

v1.1.2.2 (Standard version)

Changes:

Updated SuperSU to v2.78-SR4.

Added delete existing directories to updater-script when creating a custom zip.

cygwin - Added notice on first run about cygwin being slower than native Linux.

cygwin - Do not allow zip signing until it gets fixed.

Custom directories are supported in the donate version.

I used set_perm for the custom zips because to my knowledge those directories do not need anything other than permissions. If I am not mistaken, last I checked we don't even need to set the perms because recovery will set them to 0, 0, 0755, 0644 if they are not defined. set_perm is there just in case recovery does not set them correctly.

This has been added in the new version above :)

It has come a long way indeed. However, it is not really 75MB. The repo is 75MB but it contains all the past revisions including all the SuperSU, smali, baksmali, oat2dex, etc updates. It can get pretty big over time. I will clean it up at some point :)

I have been told you can run partially deodexed, but I have not tried it. I am not sure if moving those directories will help you. You will have to try it.

Right now I would say smali/baksmali is the best option for everything except Lollipop. Next best would be oatdump.
[SuperR Kitchen] SuperR.:
v2.1.3.3 (Donate version)

Changes:

Do not deodex framework files that are already deodexed in M and N using oatdump and smali/baksmali.

v1.1.2.3 (Standard version)

Changes:

Do not deodex framework files that are already deodexed in M and N using oatdump and smali/baksmali.
[SuperR Kitchen] TheLogicalGamer:
Hi have a quick question. I've created my rom & signed and flashed well. However I need to remove a couple of init.d scripts, and replace the build prop file.

So the question is if I place them in the zip and set correct permissions would the rom flash properly with signature verification on in twrp? Only reason I ask is I would like to go ahead and upload to try to get some beta testing done, but I don't wanna upload a dead rom. Thanks guys.
[SuperR Kitchen] SuperR.:
Changing anything inside the zip after signing will almost certainly result in an error when flashing. However, you can always disable signature verification and flash it anyway. If you want it signed properly, I suggest making your mods and signing again.
[SuperR Kitchen] Guizão BR:
[MENTION=5787964]SuperR.[/MENTION] Now the original meta-inf worked ;)

Other quick question hahaha, I deodexed my ROM with smali/baksmali and I ziplling the ROM but now the substratum themes are not working :(

Somenone know why?

Edit: After deodexing the ROM still buged, my google apps dosent work very well on this deodexed ROM :(
[SuperR Kitchen] CZ Eddie:
Hi folks, new Kitchen user here. Trying to build my first ROM ever and having an issue.

I did not do any options here. I just wanted to build a stock ROM without options for my first test.

But I'm having an issue creating the zip to flash the ROM?

It says it's missing these items, but they are all clearly in the directory.

What am I doing wrong, do you know?

Please see attached screenshot.

Here is my support zip:

https://www.dropbox.com/s/nphlr774f4ti9c1/support.zip?dl=0

Here are my system and boot IMG files:

https://www.dropbox.com/s/0n9t20osblyqulg/marlin-nde63v.7z?dl=0

What Kitchen version? ---1.1.2.3

What environment are you running the kitchen in? ---Using the Ubuntu4Kitchen-16.04.1-amd64.iso in the OP as a Vmware VM.

What device are you working on? --- Google Pixel XL North America (non-verizon)

What was the source you started from? --- system.img

What Android version? --- Nougat 7.1

What perm method? --- raw_img

What did you do after extracting and before building? --- No errors seen.

Were there errors on the screen if you scroll up in the terminal? --- No errors seen.

Send a recovery.log after flashing if you have problems flashing the ROM. --- n/a

Send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc) ---

Use the support option in the Misc Tools menu and attach the support.zip to your post. ---
[SuperR Kitchen] Sh0X31:
[MENTION=5787964]SuperR.[/MENTION] can you please add kexec-hardboot patch to "Boot Option"? Will be realy great and I can test the Rom without flashing
[SuperR Kitchen] ShinySide:
Would do no good. That's a kernel patch applied to kernel source then the kernel is compiled. Unless there's some new version of it that doesn't apply to the actual kernel
[SuperR Kitchen] xtremelora:
Hey guys, I start using this kitchen yesterday in Debian, everything working excellent after installing all dependencies.

I just have 1 question: Is it normal that this kitchen is taking about to 4 -5 hours to BUILD the flashable .zip of my rom??

I have no errors, I have checked the final .zip file and is was growing in MB but right now is stuck at 314MB of size, I use top -d 5 -p superr-pid to see if it was working and the top command reports activity (so I guess superr is still working).

i just kill the process yesterday at night cuz it was taking to much time and I tough it was frozen or something but the same is happening today.

So is that normal? How long it takes with you guys?

I have a AMD A10 processor at 2.4Ghz and 8 Gb of RAM, no virtual machine, working on my installed Debian 8 amd64, Java 8 installed and all the dependencies.
[SuperR Kitchen] ShinySide:
4-5 hours??? To zip? Holy sh!t! No there's something seriously wrong lol what I have no idea but I'd check your hardware and make sure you don't have dead cores or dead ram lol
[SuperR Kitchen] manuelmagix:
What error 11??
[SuperR Kitchen] xtremelora:
I remember now... Yesterday when I killed the process in superr's terminal (the one it was running with Ctrl-c) and superr was giving a message of SUCCESS and then ask me if i want to sign but gave me error...
[SuperR Kitchen] SuperR.:
Try a different deodex method.

There are probably many things broken for Pixel devices. Unfortunately I have not had the time to figure it all out and I don't have a Pixel. If you figure out what we need for the Pixel please let me know.

Not normal. My guess is that you have files in your ROM with no r/w permission or no owner. I have seen it before but not often. Check the zip.log to see if you can pinpoint where it is hanging.

I have no idea what this picture is.
[SuperR Kitchen] xtremelora:
I was using now Ubuntu4Kitchen in VB on Windows 10 and it was the same problem.

You were right, I changed all the permissions and the .zip rom was created may be in 5-10 minutes. Success.

If some one have the same problem like me just use this: chown -R youruser:yourgroup /path/to/your/files and go ahead to create the rom.

Now I'm facing another problem, something went wrong at the signing of the .zip file. I will keep playing around.

Thank you for pointing me in the right direction.
[SuperR Kitchen] xtremelora:
Ok, as of right now, I can not sign the zip rom, it gives me a half second error message that I am not able to read and it doesn't appear in the log file. Any idea?
[SuperR Kitchen] manuelmagix:
sorry,

this

Enviado desde mi Aquaris X5 Plus mediante Tapatalk
[SuperR Kitchen] Sh0X31:
Hey guys,

I get always force close in Setup after flashing the the new Developer Preview (npf26f). I really try everything like Download the Factory Image again, cook it again but always getting force close. It boot up, but I can't continue the Setup.

What I do:

1. Downloading Image & extract it with SuperR's Kitchen

2 Set per type to sparse_dat

3. Boot Option: 2 (pack boot.img with ramdisk), 3 (init.d), 4 (insecure boot.img), 5 (remove dmverity), 6 (remove forceencrypt)

4. Rom Tools: 3 (SuperSU, su.d support & Busybox), 6 (custom debloat)

5. Plug: add_files and added AdAway

6. Custom bootanimation

7. Build it & flashed
[SuperR Kitchen] SuperR.:
You might be running out of ram. You can try changing the heapsize, assign more ram to your VM, or get more ram.

Send your recovery.log after flashing so we can see what it going on.

I am not sure if sparse_dat works on N roms due to rimg2sdat not being updated since L. Try set_metadata. If that does not work, try full stock no mods, and see how it goes. Then add mods and see what breaks it.
[SuperR Kitchen] Sh0X31:
But in twrp no error and it boots up to the setup, only its crashes
[SuperR Kitchen] xtremelora:
You were right, it was the Ram, I select 4gb for Ubuntu4K but doesn't work, but in Debian it works.

---------- Post added at 01:45 PM ---------- Previous post was at 01:37 PM ----------

I feel dumb. I got the rom .zip signed and not signed, I put it in my sdcard, went to twrp and I did flash it to my device, I notice that the message it was different from most zip I have flashed (it only show me formatting System-Extracting System-Updating Something-Done), after I reboot my device it get stuck at T-Mobile screen (very bright) and the sound of the boot animation it gets cut at half with the signed zip but it is played complete with the unsigned one, but I can no go further than that screen with both zips.

All what I did was extract from system and boot, give it a name, create meta-inf folder from boot (I don't remember the name of this step), add metadata for permissions, I didn't add anything else cuz I want a stock flashable rom.

Do am I missing something? Do I need another step before create .zip?

Sorry guys, I don't want to bother you all. Thank you for your time.
[SuperR Kitchen] jazzespresso:
I need to download it manually for donated version since I can not get it thru git clone because my ubuntu acting weird and no time to figure out why - I am donated user. Please let me know where I can download it.
[SuperR Kitchen] manuelmagix:
Error because "system file transfer" is empty and that because my HD is Full

Sorry!!!!!

My current V2..1.3.3
[SuperR Kitchen] SuperR.:
I have already given my suggestion. You don't have to do it :)

That sounds about right. Not sure what is going on. If you send a support.zip (found in the Misc Tools menu) and a recovery.log after flashing I can take a closer look.

This link will always download the latest version as a zip. You will need to be logged in to gitlab to be able to download it.

https://gitlab.com/superr/superrs-kitchen2/repository/archive.zip?ref=master
[SuperR Kitchen] xtremelora:
Than you for your help, I just send you a PM with the Support.zip and Recovery.log.
[SuperR Kitchen] blueberry60:
Why do all SuperSU files over 2.65 version cause to boot issues or getting stuck on HTC Logo in my M9 device? How can I solve this problem?
[SuperR Kitchen] bcrichster:
Replace SuperSu.zip in Kitchen with whichever version you wish and retry making ROM. Should be good to go! [emoji41]

Sent from my N9515's cm12.1
[SuperR Kitchen] blueberry60:
I can create Rom with SuperSU v2.65 as you told,but I want to do it with last 2.78 SR4, could it be a solution to use adb and run this command in TWRP before flashing rom below that:

adb shell "echo KEEPFORCEENCRYPT=true>>/data/.supersu
[SuperR Kitchen] Captain_Throwback:
No. 2.65 is the latest version that will boot on the M9. You just have to live with it. Either way, it has nothing to do with the Kitchen.
[SuperR Kitchen] xtremelora:
Fixing zipping process

Hello, as you already know I was facing trouble creating the final .zip file, at first SuperR told me that it could be the permissions and he was right, at first I fixed the problem but it happen again, the first time I fixed with GUI tools but the second time I tried to use the shell and I was testing what exactly was causing the problem so I discovered.

In my case it was not enough to change the owner and group of my working files I also need to add more extensive permission, here is what worked for me:

1.- Change the owner and group of all my files and folders (especially systems and meta-info folders):

sudo chown -R myuser:mygroup /path/to/kitchen/project

2.- Depending on your default mask in your distro you need to extend permissions to your self and your group:

sudo chmod -R ug+rwx /path/to/kitchen/project

------ I tried just giving my user all the permissions but for some reason I have to give the same permission to my group if not the kitchen wasn't able to create the zip.
[SuperR Kitchen] bcrichster:
[MENTION=5787964]SuperR.[/MENTION] Your work is awesome as ever! BTW, I sent you a PM ..AF style

Sent from my N9515's cm12.1
[SuperR Kitchen] KaMyKaSii:
Can anyone show me the contents of /data/dalvik-cache/ folder in an odexed rom (Preferably marshmallow)? Run the command below in a terminal with super user permission and post the resulting file here. Thank you

su
ls -R /data/dalvik-cache/ > /sdcard/lsdalvik.txt
[SuperR Kitchen] brainvision:
You would see a lot of .dex files, also of system apps, if this is your doubt. It's normal..

Inviato dal mio P80h(D4C5) utilizzando Tapatalk
[SuperR Kitchen] KaMyKaSii:
Even in an odexed rom are there dex files in /data/dalvik-cache/arm(64)? If so, my stock rom has problems, there are no such files. When I was in Lollipop, I remember that Facebook had dalvik-cache of +/- 200MB, and now in Marshmallow it does not even exist. It's as if my system were virtualizing the apps in real time, rather than precompiling, this would explain the lack of memory and some lags. Since my device is still supported by the manufacturer, should I complain about this and require an update correcting ART?

When capturing a logcat you can see errors like these:

E/dex2oat (3287): Failed to create oat file: /data/dalvik-cache/arm64/system@priv-app@DownloadProvider@DownloadProvider.apk@classes.dex: Permission denied

E/dex2oat (3371): Failed to create oat file: /data/dalvik-cache/arm/data@app@com.google.android.apps.translate-1@base.apk@classes.dex: Permission denied
[SuperR Kitchen] brainvision:
Well maybe Marshmallow differs don't know that, I have no time now to check my marshmallow device.

Also in this case it makes no difference if the ROM is or it is not deodexed. Only stock apps and framework files are affected by that..

All apps you install will have the same behaviour whatever the ROM odex system uses. Hope someone will be able to clarify you soon better than what I did, I just thought you were worried by seeing dex files of system apps in a deodexed rom, sorry..

EDIT: also I'm not sure this is the right place where you should ask this question, I guess.. ðŸ‘

Inviato dal mio P80h(D4C5) utilizzando Tapatalk
[SuperR Kitchen] dxzdxz1:
Hey [MENTION=5787964]SuperR.[/MENTION] thanks for this awesome tool! I just made a $10 donation: 01974755GX569303W

Could you please include me on your gitlab list? My user is dxzdxz1
[SuperR Kitchen] TheLogicalGamer:
Quick question. Will SuperSU not flash with the rom if you convert the updater script to an update binary?