yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] SuperR.:
First, the kitchen does not automatically add SuperSU. You must have unrooted and rooted again in the kitchen menu if you ended up with a supersu directory in your project. Either that or the rom zip you are extracting has a supersu directory and you did not notice.

Second, your recovery is not seeing whatever root is there (assuming it is actually rooted). This is common with older TWRP versions that do not recognize systemless root, and may also be the case for CM based root. If you are sure your rom is rooted, I suggest saying NO to your recovery installing SuperSU for you. Saying yes breaks systemless root and may also break CM based root.
[SuperR Kitchen] :
I tried again, same thing.

Now i'll explain every passage:

1)Created Project

2)Imported ROM -> no errors, doesn't ask anything

3)It shows is rooted (i didn't unrooted and rooted again, didn't touch anything)

4)Went to "change perm type" -> actual permission is set to "set_metadata"

5)Changed to "Sparse dat" (cause i read is recommended)

6) Looked at project folder, and superSU + busybox drawers are created (there weren't before changing the perm type)

My twrp is the last version anyway
[SuperR Kitchen] SuperR.:
Send a link to the base rom so I can have a look
[SuperR Kitchen] :
Sure, here's the link: https://www.androidfilehost.com/?fid=24269982087021276

If i don't change the permission type (so i keep the metadata one) no busybox+supersu drawer is created.

And if i flash it, everything is ok, phone is rooted and CM superuser works.
[SuperR Kitchen] jaylence:
Update for Galaxy A5 (SM-A510Y)

Bootloop after deodex solved.

Galaxy A5 2016

Lollipop 5.1.1

Solution:

replaced oat2dex.jar with the latest one.
[SuperR Kitchen] xdadroidabc:
Yes that was it. Already updated to 14.4 LTS and trying to deodex one. Thank you very much sir.
[SuperR Kitchen] :
In the meantime i wait your answer SuperR i ask:

While modding a rom, is there a way to put an apk in data/app and not in system/app|system/priv-app?

i tried creating the directory data/app but when flashing the rom, it doesn't install it.

Am i missing something or simply you can't and you need to flash any ".zip data/app apps" after you flash a rom?

Cause i would like to install boeffla kernel configurator app, but it advices to not install it in system drawer, but in user data/app
[SuperR Kitchen] SuperR.:
I found the issue and will fix it in the next release.

Could you be more specific? What is the newest oat2dex.jar in your opinion? The one included in the kitchen is built from source and contains the latest commits as of March 15th, 2016.

In the ROM Tools menu, choose "4) User app support". It will create the /data/app directory and add the needed lines to the updater-script.
[SuperR Kitchen] SuperR.:
v1.0.4.6

Changes:

Fixed removing existing root and adding kitchen root methods when changing perm type.

Changed User app text to /data/app in the Rom Tools menu for clarity.

Fixed /data/app showing support added when you just got an error saying it won't work because you don't have data partition info.

Fixed data directory being left behind after getting the previously mentioned partition info error.

NOTE: If you unroot and root again, the kitchen root method will be used from that point on.

NOTE2: This is also your first chance to check out the changelog from the last 3 versions (assuming you are currently running v1.0.4.5) :)
[SuperR Kitchen] :
Great now it works :D

---------- Post added at 10:55 PM ---------- Previous post was at 10:47 PM ----------

Just a little thing:

when changing permission type from "metadata" to "Sparse dat" the "3) Busybox add/remove text string" now shows by default [CURRENT:Enabled]and not Disabled, but indeed there is no busybox drawer created that's the important thing.

For the rest, everything works
[SuperR Kitchen] SuperR.:
This is not an error. It says enabled because you have busybox pre-installed in that rom. Check /system/xbin/busybox. If you want it to say disabled, you must remove busybox. Choosing the busybox option will ask if you want to remove it if it is there.
[SuperR Kitchen] bcrichster:
Here's the ZTE Speed by-name files..
[SuperR Kitchen] jaylence:
I'm really having a hard time deodexing my Rom.

I mean, deodexing works.. phone boots up...

but as soon as I enter the Initial setup, "google services / google apps / com.google... stopped working"

Even tried wiping cache/dalvik before and after flashing, same result.

I'm still using v 1.0.4.4

Lollipop 5.1.1

Samsung A510Y

What could be causing those warnings?

This is my first time building a custom rom so I'm pretty sure I did something wrong.

I just don't know what it was.

For now, this method seems to work:

1. leave the rom odexed, rooted, with app support and busybox

2. build and then flash

3. make a separate flashable zip containing the deodexed system apps and flash
[SuperR Kitchen] SuperR.:
Are you modifying apks? If not, why deodex? If you are doing it for performance, think again. Deodexed roms are not faster, in fact just the opposite especially during first boot. Just tossing it out there for someone creating their first rom ;)
[SuperR Kitchen] jaylence:
Odexed & Debloated rom,.. runs very smooth on my A5. :)

Yes, I want to try modding apk's. I can see there's a lot of tutorials here in xda.

I've already started with android.policy.jar. So far, I've succeeded implementing the 5-way reboot options. :)

Although my A5 supports Theme Store, I want to theme my phone based on my own preferences.
[SuperR Kitchen] fitosanitarium:
Same here with:

6.0.1 nexus 6 stock
[SuperR Kitchen] :
Understood, anyway i said everything works because "graphically speaking" the program now show "Rooted", but didn't try a zip build because it was too late yesterday.

Today i've builded a rom and flashed, everything went ok, boot went ok.

Checked developer options and switched on root, opened various app that requires root and all of them showed my phone isn't rooted (superr, as said before, was showing "Rooted").

It seems it still delete the integrated root?

When cooked the rom, as before, i didn't unroot/root again and didn't touch busybox.

Builded with set_metadata perm type and still works, phone is still rooted.
[SuperR Kitchen] SuperR.:
The kitchen is not removing root anymore so there is something else going on. Feel free to figure it out and let me know. However, if set_metadata works for you why not use it?
[SuperR Kitchen] :
Simply because it's your recommended perm type :D

I see it packs everything in .dat images, and i see that as a more "clean" .zip
[SuperR Kitchen] ROBERT CM:
[MENTION=5787964]SuperR.[/MENTION]

A question I have a moto g 2014 with MM 6.0 after extracted the system.img the kitchen detects that the system this deodexed, but in reality it isn't deodexed..

How I can deodexed my rom?

thanks advanced

and great work with your kitchen
[SuperR Kitchen] SuperR.:
Well, that is a good point lol. Even so, I recommend it because a) It is newer and what AOSP and CM have gone to since Lollipop and b) It has some advantages getting things working correctly if you don't have/know the metadata for your device. However, the kitchen has a very nice metadata database at this point so set_metadata should work for most devices very nicely. If it works for you, stick with that. There is a reason the kitchen offers 4 perm type options. Not every option works for every device.

Please send me a link to the firmware so I can have a look.
[SuperR Kitchen] Captain_Throwback:
[MENTION=5787964]SuperR.[/MENTION]

Is there a way for the Kitchen to deodex a single odexed APK when the rest of the ROM is already deodexed? I have a deodexed ROM, and added an odexed app, so the Kitchen detected my ROM as odexed (as I'd hoped), so I could deodex that single app. However, when I went into the deodex menu, it couldn't detect my arch, and then I got stuck at that screen, because it wouldn't accept my input. Shouldn't I be able to input the parameters manually for the ktichen (or can it read them from build.prop, maybe?) so it can process the odexed app that it finds?
[SuperR Kitchen] tdunham:
Just an update on my experience with the kitchen...

Searched the thread and saw the loss of wifi issue which I had as well. The issue turned out to be my 6.0.1 rom didn't like using sparse perms and when I switched to metadata, everything worked perfectly.

The other issue was with deodexing, got lots of force closing apps. I realize this is going to be an ongoing issue for [MENTION=5787964]SuperR.[/MENTION] since there are so many variants to deal with and support for the newer builds is always a bit spotty so no worries there. ;)

To resolve this, I used svadev's batch deodex tool on the 3 odex folders (app/priv-app/framework) and replaced those folders in the kitchen and re-built the rom.

Everything turned out perfect. Tnx again for the ongoing support.

Info:

Galaxy Note 5 SM-N920P (Sprint U.S. Variant)

Android 6.0.1 Touchwiz
[SuperR Kitchen] SuperR.:
This is not really possible with Lollipop+ roms. If your rom is deodexed you don't have the boot.oat files required for deoptimization. Additionally, the apk must be from the same rom as the framework you are using to deodex it.
[SuperR Kitchen] Captain_Throwback:
Understood. There should still be a way to get out of the deodex menu though, if I enter it by accident, right?

I guess the Kitchen should be looking for boot.oat in Lollipop+ ROMs to determine if it's deodexed or not, even if it detects an odex file at some point?
[SuperR Kitchen] SuperR.:
You are correct. I will add a check for the next release :)
[SuperR Kitchen] ROBERT CM:
[MENTION=5787964]SuperR.[/MENTION]

I think that the kitchen detected by error the system as deodexed is because the system does not have .odex (after extracted from System.img)

but when installing apps in data/app the apk have file .odex

for example:

data/app/com.xxxxxx.xxxx-1/oat/arm/base.odex

Link firmware MM 6.0 Titan

http://www.filefactory.com/file/41gthahi3xd5/XT1063_TITAN_RETLA_6.0_MPB24.65-34_cid12_CFC.xml.zip

Regards.. :)
[SuperR Kitchen] SuperR.:
v1.0.4.7

Changes:

Added a check for boot.oat before allowing you to deodex.

Added a check for boot.oat before deciding the rom is deodexed.

Added support to extract sparse chunks and boot.img from Moto firmware zips.

Added ZTE Speed to device database.

[MENTION=6947871]ROBERT CM[/MENTION] - The firmware you linked is completely deodexed. Every apk and jar contains classes.dex and there are no odex or oat files. The kitchen has nothing to do with /data/app containing odex files. The Play store is responsible for this.
[SuperR Kitchen] Er. Aditya:
was just trying to setup kitchen on virtual box and i am getting this error can someone using virtual box guide me

------------------------------------------------------

SuperR's Kitchen

by SuperR

------------------------------------------------------

Copying files to system directory ...

cp: cannot stat ‘./output/*’: No such file or directory

umount: output/: not mounted
[SuperR Kitchen] JochenP:
please check if you have installed openJDK Java 7 and java 8 via software-center...
[SuperR Kitchen] Er. Aditya:
i did but now when i checked for version it shows this error

bhuvi@bhuvi-VirtualBox ~ $ java –version

Error: Could not find or load main class –version

i installed a 64 bit Linux Mint 17.3 on virtualbox
[SuperR Kitchen] The Sickness:
Don't use Mint....try Xubuntu XFCE. It will run smother....once you have done that I will post a script that will install all the dependencies including java.
[SuperR Kitchen] Er. Aditya:
currently i dont have access to internet but i have ubuntu 15.10 downloaded can i use that sir ?
[SuperR Kitchen] The Sickness:
Yes, that's fine too
[SuperR Kitchen] Er. Aditya:
started i guess will take around 20 mins :o:o:)

---------- Post added at 09:33 PM ---------- Previous post was at 09:11 PM ----------

yes sir i am ready for your guidance :)
[SuperR Kitchen] The Sickness:
Give me about 10 minutes

EDIT:

Here is the script. First extract it to your desktop. You then need to open it up with whatever editor you use...

Toward the bottom of the script you will see where it says "sick:sick".....you need to replace that with your username.

Once you have done that open up a terminal and type ./installs

The script will start....when it comes to Java you will have to select OK and on the next screen as well. It will also install apktool and all

of the needed android environment dependencies.......

Any issues or something you dont understand let me know.....

If anyone has issues or questions concerning my script please contact me via PM. This thread is about a kitchen not Linux scripts.

Sorry [MENTION=5787964]SuperR.[/MENTION] for off topic.
[SuperR Kitchen] Er. Aditya:
sorry to [MENTION=5787964]SuperR.[/MENTION] ax well and a huge thanks to you sir

lemme give it a shot

Edit : [MENTION=4921688]The Sickness[/MENTION] ,sir the script worked like a charm... if you ever make changes or update this please let me know :D
[SuperR Kitchen] SuperR.:
The next release should stop this issue from happening in the future.

It appears as though you are not using the correct "-" in your command. Not sure where it comes from but yours is longer than normal.

yours:

java –version

correct:

java -version

While I am happy you were able to help him get sorted out, his issue was not dependency related (aside from java and I am not sure he did not already have that installed based on my comment above).

I looked at your script and would like to know if it includes all the dependencies required to build the source included in the kitchen for the required binaries. The kitchen intends to install the required dependencies, but obviously I have missed some because many people are still downloading the prebuilt binaries. If your script contains everything required I may steal your list if you are ok with it. Thanks for your help with this :)
[SuperR Kitchen] noax20:
hi! thanks for your works!! it´s possible change the name of rom.. id name?

Thanks
[SuperR Kitchen] The Sickness:
You can use it in any way you need bro....

The script installs all the required packages with apt-get... which you know is only 4 Ubuntu based distros. It won't work on any Arch based distros.

But feel free to use it as you need
[SuperR Kitchen] SuperR.:
v1.0.4.8

Changes:

Added support for creating ROM from a system directory and boot.img copied to a project directory as long as it still includes symlinks.

Changed all ./ directory references to absolute paths to avoid ./output/* error and other similar errors on some systems.

Added some build dependencies thanks to [MENTION=4921688]The Sickness[/MENTION].
[SuperR Kitchen] xxRaynexx:
Thanks for the reply. I'm not trying to keep root. I only rooted to allow the kitchen to set the symlinks via adb.

I am working with MMB29V, which is 6.0.1. I have tried extracting the factory image using set_metadata, set_perm, and Sparse dat.

Every time I try to flash the system_new.img to a fresh device, it sticks at the Google boot screen.

Any ideas what I'm doing wrong?
[SuperR Kitchen] tdunham:
You have to use modified kernel from source or modify kernel via systemless root or it will not boot.
[SuperR Kitchen] mwilky:
Awesome work superr:

On s7 edge, if we flash as a standard rom zip with set metadata for permissions, we lose vr functionality.

Its like its not loading a lib, the motion detection doesnt work at all and the view is all distorted.

If we flash as .DAT files it fixes VR.

Got a feeling we arent setting something correctly in the updater or we are completely missing something out, any ideas?
[SuperR Kitchen] SuperR.:
Yes, we are probably missing metadata for some files. Take a look at your file_contexts file which should be in your 00_project_files directory. You may find something related to vr libs or binaries in there. Check the file permissions on your device for those files and we can add them to the database.
[SuperR Kitchen] mwilky:
Will do bud, I'll check and post back once I find something
[SuperR Kitchen] jinconstantine:
That is super true when you deodexed roms you are obliged to zipalign it as well just to achieve almost same speed as odexed roms :)
[SuperR Kitchen] elxufas:
Hi good morning, I am with cywin but fail to run the kitchen.

some can tell me how to do that boot, where you have to put the cywin binary.

I put them on their route unemployment can't starting
[SuperR Kitchen] mwilky:
[MENTION=718594]superR[/MENTION]

Few things ive spotted in the permissions side:

Galaxy s7 edge:

[B][COLOR="Lime"]set_metadata_recursive[/COLOR][/B]("/system/bin/dhcpcd", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:dhcp_exec:s0");

should be

[B][COLOR="lime"]set_metadata[/COLOR][/B]("/system/bin/dhcpcd", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:dhcp_exec:s0");

set_metadata_recursive("/system/etc/firmware", "uid", 0, "gid", 2000, "dmode", 0755, "fmode", 0644, "capabilities", [B][COLOR="lime"]"0x0"[/COLOR][/B], "selabel", "u:object_r:system_file:s0");

should it be saying?

set_metadata_recursive("/system/etc/firmware", "uid", 0, "gid", 2000, "dmode", 0755, "fmode", 0644, "capabilities", [B][COLOR="lime"]0x0[/COLOR][/B], "selabel", "u:object_r:system_file:s0");

I checked the other 0x0's in the generated ones and they are all without the speech marks.

Same goes for

set_metadata_recursive("/system/etc/ppp", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0555, "capabilities", [B][COLOR="lime"]"0x0"[/COLOR][/B], "selabel", "u:object_r:ppp_system_file:s0");

should be

set_metadata_recursive("/system/etc/ppp", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0555, "capabilities", [B][COLOR="lime"]0x0[/COLOR][/B], "selabel", "u:object_r:ppp_system_file:s0");

Other stuff that I think is missing completely:

set_metadata("/system/bin/fsck.exfat", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:fsck_exec:s0");
set_metadata("/system/bin/mkfs.exfat", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:fsck_exec:s0");

Without these exfat sdcards report as corrupt.

And finally:

set_metadata("/system/bin/epmlogd", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:epmlogd_exec:s0");
set_metadata("/system/bin/IPSecService", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:IPSecService_exec:s0");
set_metadata("/system/bin/lpm", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:lpm_exec:s0");
set_metadata("/system/bin/surfaceflinger", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:surfaceflinger_exec:s0");
set_metadata("/system/bin/vpnclientd", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:vpnclientd_exec:s0");

Hopefully this might help a few other devices as well, apart from the exfat ones i'm not 100% if the other make a lot of difference if any difference at all.

I've still not managed to find the VR related things, if anyone else knows please let me know as it is bugging the hell out of me

Once again thank you for the excellent kitchen
[SuperR Kitchen] tdunham:
Awesome stuff, cant wait to try it, users are complaining about corrupt SD on my end like crazy on MM.

For Gear VR, are you using a custom kernel yet? I know many issues with the VR early on were related to the kernel and if you're using stock modified by systemless root, I feel that might be our common problem at the moment.

We do have source for ours but I'm waiting for someone to do it for us (still something I never learned how to do) and will report back too once I know one way or the other.
[SuperR Kitchen] mwilky:
Yeah it was doing my head in lol, many sleepless nights!

The vr is weird, if I flash as .DAT files created through superrs kitchen it works fine, so something that is getting set when flashing it through .Dat is getting missed in our set metadata part of updater script.

Just a real ***** to track down lol
[SuperR Kitchen] tdunham:
Ah, that's right I remember now.

Do me a favor and see if you lost battery charging while powered off please.

On Note 5 MM, we no longer get battery level while OFF, just the symbol with lightning bolt and the phone locks up solid; the only way to power it back on is the warm reset key combination.

---------- Post added at 01:56 PM ---------- Previous post was at 01:52 PM ----------

Disregard my previous ^^^

Your metadata permissions fixes took care of this as well. :D
[SuperR Kitchen] mwilky:
No worries, you got any ideas about the vr? I've checked numerous s6/s6 edge threads that have it working and I can't spot anything
[SuperR Kitchen] tdunham:
Same here. Are you systemless rooting on both builds, dat and regular?
[SuperR Kitchen] mwilky:
Yup, dat flash then busybox and supersu.

Other build: system extract then busybox and supersu.
[SuperR Kitchen] noax20:
[MENTION=718594]super[/MENTION]R

Please ask me, it´s possible change id name "Built.with.SuperRs.Kitchet"

thanks!!!
[SuperR Kitchen] edzamber:
Deleted
[SuperR Kitchen] SuperR.:
Please send your file_contexts file and I will have a look.

Not unless you figure it out on your own :)

If this conversation goes further, it will become more difficult to change in the future ;)

v1.0.4.9

Changes:

Fixed changelog to display apostrophe instead of the html code equivalent.

Added/fixed some metadata entries thanks to [MENTION=3699616]mwilky[/MENTION].
[SuperR Kitchen] mwilky:
Will do, give me a few till I'm home from work
[SuperR Kitchen] noax20:
Hi

I modified build prop but when it builds the rom name appears Superr Built with kitchen in the build number of the phone

I looked at the script updater but not see it.

thaks!""
[SuperR Kitchen] SuperR.:
This is changed intentionally thanks to all the people that believe they are ROM developers after using this kitchen. This kitchen does not make anyone a ROM developer, and thus I deserve credit for building roms for hundreds of devices. Since I rarely get that credit, I must give it to myself. On the other hand, if you are a developer you will be able to figure out how to change it on your own.

I sincerely hope that nobody explains how to remove the credit I deserve for all the hard work I have put into this kitchen. As previously mentioned more than once, it will become more difficult to remove in the future if they do. Let's not ruin it for everyone by continuing to discuss it. Thanks :)
[SuperR Kitchen] edzamber:
You're right !

One thing is sure for me is that i always give credits in all my Rom threads for all people, Devs and Tools that helped me [emoji6]

http://www.phonandroid.com/forum/post2065584.html#p2065584
[SuperR Kitchen] :
If they do and they post it then it will be deleted don't worry ?
[SuperR Kitchen] noax20:
You're right sorry and thanks for your help.
[SuperR Kitchen] mwilky:
[MENTION=718594]superR[/MENTION] here you go bud, need anything else give me a shout

file_contexts
[SuperR Kitchen] SuperR.:
Here is a list of all the files and contexts that are defined in your file_contexts, but are not defined in the kitchen. Most of them will not matter but I bet at least one of them is your vr stuff. I was hoping the list was shorter, but hopefully this will help narrow down where the problem is.

http://hastebin.com/ugecutikiy.sm
[SuperR Kitchen] mwilky:
Your a star mate thank you, will let you know how i get on so you can add it to your kitchen!
[SuperR Kitchen] mwilky:
The only one present in our system directory is

/system/bin/rpmbd u:object_r:rpmbd_exec:s0

set it correctly in updater script and still no luck :(

edit: hold on think i have something