yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] sefrcoko:
FYI I tried the test-1 version today but it bootlooped at the Samsung splash screen. Was just a debloated/rooted build of our latest COK3 5.1.1 firmware Note 4 -- N910W8. Also tried with a rooted but not debloated build and had the same result. I see test-3 is out now though with supersu 2.61, so hoping that does the trick! Will install, test and provide feedback tomorrow. Thanks for all your work superr, this kitchen is constantly improving and it was already awesome to begin with :)
[SuperR Kitchen] theincognito:
Thanks. I will let you know the results. :)
[SuperR Kitchen] jazzespresso:
[MENTION=5787964]SuperR.[/MENTION]

Nice one. I installed Oracle VM Virtual Box, and about to install Ubuntu onto VM, but missing details how to setup SuperR's Kitchen after I install Ubuntu.

I hope you may or someone able to put some instructions for the people who run virtualbox ubuntu on Windows 10 machine..
[SuperR Kitchen] Rydah:
literally extract the zip, run terminal to the location where you unzipped it, run ./superr and it'll walk you through installing dependencies. I made a folder in my home directory named SuperR with the kitchen files inside. Also, from the Ubuntu store, I installed Java runtime 8 which was needed to deodex files.
[SuperR Kitchen] :
I used the latest test kitchen to make a rom for the n910c exynos n4. I unpacked the kernel to make it permissive. The rom boot's but superuser didn't get flashed and WiFi doesn't work. I used set metadata and it was a 5.1.1 rom as requested.

If there's anything else I can do just let me know
[SuperR Kitchen] sefrcoko:
Installing test-3 now and will post results shortly for n910w8...
[SuperR Kitchen] SuperR.:
Did you start with a fresh project directory and extract a stock img? If not, please try that and then add root with the kitchen. There should not be a need to make it permissive. That is pretty much the point of the new supersu so you can be root and enforcing. The repack is also an extra variable that can break WiFi.
[SuperR Kitchen] sefrcoko:
Ok I tried test-3 but unfortunately i'm still getting bootloops at the Samsung splash screen on N910W8 5.1.1 COK3 firmware.

Here's what i tried... I extracted the boot.img and system.img.ext4 files from the official sammobile package, renamed the ext4 to img, ran the test kitchen on 64-bit virtualbox debian, and built a basic rom (used set_metadata for permissions and also added root). So far so good.

Next i tried flashing the rom through twrp (v2.8.7.0) but it caused bootloops. So I tried combinations of wiping cache/dalvik/system/data and then flashing the rom again but it still bootlooped. Finally I tried flashing official COK3 firmware through odin, followed by twrp and then the rom, but...bootloops.

I can test further or provide more info if needed...

Also, when rebooting after flashing the rom, twrp says that the supersu binary isn't installed and offers to install it for me. I remember Chainfire saying to skip that when using supersu 2.60+, so I just rebooted without letting twrp install it. Not sure if this part helps but I figured I should mention it lol.
[SuperR Kitchen] SuperR.:
That's a bummer but thanks for testing. I am sure Chainfire will come out with more releases to fix these issues at some point. I guess we will wait :)
[SuperR Kitchen] mcqaissi:
yes

on terminal if i wrote ( mcqaissi@ubuntu:~$ cd /home/mcqaissi/SuperRs_Kitchen_v0.8.9.3/./superr

bash: cd: /home/mcqaissi/SuperRs_Kitchen_v0.8.9.3/./superr: Not a directory

but when i swap icon superr on terminal its work
[SuperR Kitchen] SuperR.:
If you have this directory:

/home/mcqaissi/SuperRs_Kitchen_v0.8.9.3

do the following:

cd /home/mcqaissi/SuperRs_Kitchen_v0.8.9.3

press enter so the terminal will be running in that directory.

now do the following:

./superr

and press enter to start the kitchen

edit: even easier since you are running Ubuntu, use Nautilus file manager to navigate to the following directory:

/home/mcqaissi/SuperRs_Kitchen_v0.8.9.3

Double-click the superr file, and choose run in terminal
[SuperR Kitchen] mcqaissi:
hm

ya its Work now I'm too glad:)
[SuperR Kitchen] Jamie_Bowen:
Yeah thanks..

I know how to run the program, what I'm saying is that parts of it are not functioning for me...

I'm on windows 10, in case anyone else is having the same issue?
[SuperR Kitchen] nghia0423:
Well this program is made for linux
[SuperR Kitchen] SuperR.:
v0.8.9.8

Changes:

Will no longer allow less than api level 21 to use sparse dat

removed the dat file in project dir.

Regarding sparse dat...it may work fine with KitKat as well since it supports selinux, but I don't think it will work on anything below KitKat. Any thoughts on this? Should I let it work for KitKat roms as well as Lollipop? Am I wrong altogether about where it will work? lol
[SuperR Kitchen] bcrichster:
Plz allow KK

---------- Post added at 03:34 PM ---------- Previous post was at 03:34 PM ----------

The more options, the better
[SuperR Kitchen] SuperR.:
The question is not based on desire unfortunately. I am unsure of the compatibility with lower Android versions. Sparse dat images only started with Lollipop. Hoping to get some insight from people that know more about it than I do :)
[SuperR Kitchen] Q9Nap:
I don't think it will work on Kit Kat...

Based on this op: http://xdaforums.com/android/software-hacking/how-to-conver-lollipop-dat-files-to-t2978952

The first line in system.transfer.list is version number; 1=5.0.x, 2=5.1.x.

Just a guess, and unfortunately I don't have a kit kat device to test on.
[SuperR Kitchen] SuperR.:
v0.8.9.9

Changes:

Fix the things I broke on the last version. Sorry to anyone who updated. Please update again :)

edit: v0.9.0.0 - fixed more broken stuff. I think that is all :eek:
[SuperR Kitchen] SuperR.:
After reading the post you linked, I agree with you. Sparse dat will stay Lollipop only. Thanks for your input :)
[SuperR Kitchen] not-i:
Awesome mate. Can't wait to give it a try :)
[SuperR Kitchen] SuperR.:
I am more curious about what parts ARE working on Windows 10
[SuperR Kitchen] SuperR.:
v0.9.0.1

Changes:

Fixed the updater-script for sparse dat when root is added. It was unmounting system before installing root which may cause a root failure.

Sorry for the many updates today, but I think things should be good now :)
[SuperR Kitchen] ferbulous:
[KITCHEN][LINUX] SuperR's Kitchen (v0.9.0.1 - 9/26/15)

Hi, so I apparently I can't seem to get adb devices installed on linux for my mtk device. Only on windows I was able to get the driver installed properly.

Can I just just start deodexing the rom by manually extracting the twrp backup then proceed to repack into a flashable zip using your new kitchen tool?
[SuperR Kitchen] SuperR.:
You can create a new project from the menu, and place system.ext4.win and boot.emmc.win (from twrp backup) in the project directory and choose extract for new rom. Then you can do anything you want :)
[SuperR Kitchen] ferbulous:
[KITCHEN][LINUX] SuperR's Kitchen (v0.9.0.1 - 9/26/15)

Ok, so no need have my phone connected to the pc

Btw, my previous mtk device was deodexed successfully with some help from [MENTION=5297774]bcrichster[/MENTION]

So I guess you can add mtk devices to the list now
[SuperR Kitchen] bcrichster:
Correct, SuperR. That was his MediaTEK we were working on. VKworld (VK6050s)

---------- Post added at 10:10 PM ---------- Previous post was at 09:15 PM ----------

@ferbulous would you happen to have a debloat list for your device/carrier to share yet?
[SuperR Kitchen] nghia0423:
Using the new sparse dat method I only get a zip that is only about 11mb compared to 569mb. Is that supposed to be right?

Edit: Made another zip without sparse and it came out to be 629mb. I'm no developer but is the sparse zip suppose to be that small? If so, then holy moly.

Edit: Open the archive and system.patch.dat is 0 bytes
[SuperR Kitchen] bcrichster:
Holy crap!! WHOO!!
[SuperR Kitchen] :
I started with a fresh system img I downloaded from Sammobile just to test the kitchen. I unpacked the kernel as Sammy roms need a permissive kernel to obtain root. I will do a fresh project without unpacking kernel and report back
[SuperR Kitchen] jazzespresso:
I don't see Java 8 in Ubuntu store, it only list Java 7 runtime...any idea how to get that installed?
[SuperR Kitchen] Ram121:
If you are on latest ubuntu then java 8 is visible, if you want on older version then you need to add repository for that, you can search on Google for adding repository
[SuperR Kitchen] sefrcoko:
Fyi with supersu 2.60+ the idea is that it will root our Sammy roms without needing to make the kernel permissive.

Even though I got bootloops with the test-1 and test-3 kitchens I suspect the updater-script is key, as the latest stable kitchen's (i.e. pre supersu 2.60) builds also bootlooped at first but eventually managed to boot using the script/supersu method in alexandr's N910F dev base rom (albeit with a consistent camera fc that I can't seem to figure out). The latest Sammy security policy had killed that method, but it seems that deleting the policy updates makes it work again.

Anyhow, that method may be outdated now that we have a new supersu, but I'll keep an eye on his thread and post findings if I manage to get the script to boot the test-kitchen builds. I'm convinced something is up with the script, it seems extra picky with Sammy's 5.1.1 and recent supersu releases. I could be wrong though lol
[SuperR Kitchen] jazzespresso:
thanks I got it installed...

I extracted stock firmware (samsung sm-t350), and see bunch of files, but got copied system.ext4.tar and boot.img, but not quite sure about modem.bin file should also copied to superr_kitchen folder or not...
[SuperR Kitchen] Ram121:
Not required to copy modem.bin , only system.ext4.tar and boot.img is sufficient and recovery.img might be required if you don't want to flash partitions by by-name method
[SuperR Kitchen] jazzespresso:
thanks...I am windows guy, so not very familar with Ubuntu, but it is running on my Oracle VirtualBox fine...

I will copy system.ext4.tar, boot.img, and recovery.img and see if I can get extracted and able to deodexed first before I start doing more customization..

does this superr tool creates CWM flashable zip or TWRP flashable zip?
[SuperR Kitchen] Androidwizzard:
rom.zip = rom.zip no matter which custom recovery
[SuperR Kitchen] Ram121:
This creates zip which can be flashed by both recoveries
[SuperR Kitchen] :
Just built another 5.1.1 rom for the exynos note 4 (n910c) without unpacking the kernel. This time root works fine but unfortunately wifi is still broken. If there's anything else I can do to help don't hesitate to ask. Really hope we can iron out this wifi bug as the kitchen is now pretty much perfect now
[SuperR Kitchen] dkionline:
Please remove "Build with Superr Kitchen" add-in for build.prop.

Can u explain what by-name check does? Is it a check for Kernel Path? I'd like to fill the list with other devices cause i dont want to look everytime for the path.
[SuperR Kitchen] oak:
Just edit the superr.sh script.
[SuperR Kitchen] sefrcoko:
Superr has answered this before... it can easily be changed yourself, but he won't make it easier than it already is to remove his name from his work ;). Totally fair in my opinion, especially considering all the work he puts into this kitchen for us.
[SuperR Kitchen] SuperR.:
Sweet :) Have you tried sparse_dat with the new root method? It will probably fix your wifi problem, and if it does we know there is something wrong in the metadata the kitchen is producing when using set_metadata.

no

There is no need to look for a path when using this kitchen. Only rare instances the kitchen will not find it for you. The kitchen looks for your by-name directory in several ways. If it does not find it, you can get your mmc blocks from a recovery.img for your device. It really could not be easier
[SuperR Kitchen] :
I'll try sparse_dat but I've never managed to get sparse_dat to boot on a stock Sammy rom before. Fingers crossed it will work now
[SuperR Kitchen] SuperR.:
I hope nobody ruins my fun and posts how to remove it. If they do it will certainly become more difficult in future releases :p
[SuperR Kitchen] :
Just rebuilt the rom using sparse_dat and it booted with working wifi Yeah, but unfortunately supersu didn't get flashed again. Not sure why it didn't get installed as watching twrp it said it flashed superuser. Hopefully its an easy fix

Edit just read the updater script and it doesn't seem to include super user but according to the kitchen the rom is rooted. Last line of the updater script is extracting boot image
[SuperR Kitchen] SuperR.:
That is completely my fault and i have no time to update the kitchen right now. Here is the fix.

In your file manager, navigate to and open /kitchen/tools/updater/META-INF-DAT/META-INF/com/google/android/updater-script

Change the above mentioned file starting at #ROOT so it goes from this:

#ROOT
unmount("/system");
ui_print("Extracting boot image...");
ui_print(" ");
show_progress(0.050000, 5);
package_extract_file("boot.img", "#BYNAME/boot");
show_progress(0.200000, 10);
ui_print("#SIGNATURE Installed");

To this:

unmount("/system");
ui_print("Extracting boot image...");
ui_print(" ");
show_progress(0.050000, 5);
package_extract_file("boot.img", "#BYNAME/boot");
#ROOT
show_progress(0.200000, 10);
ui_print("#SIGNATURE Installed");

All you are doing is moving where the "#ROOT" line is. Save the file and extract your project again using sparse_dat. My apologies, I just missed that one :o

edit: well, I did not miss it in the kitchen test 3 at least. If you are using that version I need to do more investigation.

edit2: If you are using kitchen test 3, maybe you need to add mount/unmount commands before and after #ROOT. SuperSU should take care of the mounting but I can't think of anything else it could be.
[SuperR Kitchen] RyTekk:
Will this kitchen work on Mac OSX? Or I have to install a Linux distro?
[SuperR Kitchen] bcrichster:
Linux Only

---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------

Or VirtuaBox/Virtual Machine
[SuperR Kitchen] :
I'm using the latest test kitchen. The only thing I did was change permission type from set meta to sparse_dat rather than building the rom from scratch. Hope that helps
[SuperR Kitchen] SuperR.:
Did you say the updater-script does not have the SuperSU flashing part? If so that's why it is not working. If it does have it and it happens after the boot.img is flashed, then the only thing I can think of is mounting /system and /data before root and unmounting after. I hope you have some time to tinker :)
[SuperR Kitchen] :
Yes sorry for the confusion when I opened the updater script super user wasn't in it, not sure why it wasn't added. I'll try rebuilding from scratch see if it gets added to the updater script rather than just changing permission type

Edit

Removing root then reapplying root adds super user to the updater script. Looks like the issue was when changing perm type from set meta to sparse_dat it didn't notice that root and data app were already added and just created the updater script without them. Soon as they were removed and readded they appear in updater script. Hope that all makes sense
[SuperR Kitchen] jazzespresso:
thanks [MENTION=5564860]Androidwizzard[/MENTION] appreciated your response

but so far I have no success getting it work on Samsung Galaxy Tab A SM-T350 (5.0.2). It did not able to de-odexed correctly, messed up framework dedodexing (android-policy.jar zero bytes after deodexing??, kinda tells me deodexing did not fully work)

during the deodexing, several google apps thrown Java out of memory error..anyway with all the errors, I went thru entire process (just to see how entire process works from start to end), obviously selecting perm type did not work, no matter what I choose...thus created blank updater-script file, I could not able to identify the device (By-name auto-detection) using any options (get the info from boot, or recovery, etc...)

anyway, it has been good experience, but I wish it was worked OK..
[SuperR Kitchen] Macguyver1980:
Issue when building ROM

Hello,

I imported an Original ROM and almost not customize it, for test as with all other kitchen till now was never working...

When building, I choose the adb used method and had this error:

Determining data partition size ...

/media/michael/15D959AC4EED37BB/Superrs/superr: ligne 3737: 33152

13399552 * 1024 : erreur de syntaxe dans l'expression (le symbole erroné est "13399552 * 1024")

I had also this error:

Creating data sparse dat image ...

mv: impossible d'évaluer «system.transfer.list»: Aucun fichier ou dossier de ce type

mv: impossible d'évaluer «system.new.dat»: Aucun fichier ou dossier de ce type

And during installation error no file "data.new.dat" in package...

Can you help me? I begin to believe this Ulefone has a really different and strange ROM structure that no kitchen is able to do anything with...:crying:
[SuperR Kitchen] sefrcoko:
Interesting...On a related note, I wonder if the issues you described regarding root permissions on the boot.img could also explain why using the kitchen's set_metadata is not booting for me on N910W8 with Sammy 5.1.1...will try sparse later tonight to compare and post back...
[SuperR Kitchen] bcrichster:
Ok..

ZTE Warp Sync N9515

KK _4.4.2

Linux Mint 17.2 Cinnamon x64

Perms: metadata

Deodexing is breaking something, it causes indefinite hang on bootanimation. No Deodexing and Rom boots normal. Oh! Set_perms causes hang on green Andy, doesn't even bootani

Edit: did not try set-perms on undeodexed ROM..
[SuperR Kitchen] sefrcoko:
Ok, more feedback on 5.1.1 Sammy COK3 for the N910W8 (Snapdragon)... I ended up rebuilding the rom (still using the test-3 kitchen) but this time I selected sparse_dat instead of set_metadata. I also replaced supersu 2.61 with 2.62 and then edited the updater_script's references to those filenames. Flashed through TWRP and it boots! Everything seems to be working well so far. Wifi, 4g, root, etc. I'm guessing something must be off with set_metadata but not sure what. Either way, happy to have a 5.1.1 zip with both root and a bootable stock kernel again :).
[SuperR Kitchen] Macguyver1980:
And When I install kitchen, I've Error: sepolicy-inject could not be built.

Should I then choose to install the 64-bit binaries proposed?

Thanks for help.
[SuperR Kitchen] ANDjROID:
blu studio6.0 hd.

let me start by saying SUPERR- YOU DA MAN!!!!

just wanted to let you know.that i was finally able to build my rom (from stock base.5.0.2) and get it o flash with no flash errors. no failed binaries. although i think it may be a lil heavy on the debloating i am up and running for the day now with no fc's. only problem i am having is wifi. doesnt seem to want to connect. i think one of the debloat aps culprit.as soon as i, and if i can, narrow it down i will update. i am going to attempt to recall exactly the options i chose to get it to flash. using a stock 5.0.2. on ask of use dat images , chose no. root, debloat, add init.d. add insecure. chose option 1. for perm type. zip alligned. then built full rom zip. no problems flashing clean flashh, lol or dirty. oooppppps. hope everyone can understand this. sorry am on the run and doing all this while working so...... any questions and if i left any details out you may need feel free to ask n if i can i will give info.

only other info i can think of: using (superR 9.6.6 (latest ver.)correct me if im wrong.) also i am going to wrap device and send. had to fix partition on update script before build. both the superr by name file, and the superr mmc. when doing the first test build i used the by device option but for some reason it was still wrong. it might look a lil strange as its listed....... but it works. havent been able to test bluetooth yet.

any questions , ANYONE, feel free to ask. will answer as soon as i can get on line again. also had no problems super su. installed while flashing and checks on root checker. guess the biggest give away is my basebnd now says built by superR kitchen and so does android version.

superR, thanks again, u da man!!! :highfive:

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

i think u need to go back to op and read about 3rd post down. has list of prerequisit dependencies listed to make sure u have all programs and tools to build. forgive me if i miss understood your post.
[SuperR Kitchen] Macguyver1980:
Then, yes I checked and all preriquisit dependencies were there. Finally, with older version of Kitchen, in beginning when not touching anything was working the produced file and once I cooked a bit more, again as with all other kitchen Error: Corrupted file!

No way to use any of the kitchen existing till now for my phone... And no detail on what happens, like with others... It was my last solution regarding kitchen. I've to do the change of each file manually seams, fun...;(
[SuperR Kitchen] bcrichster:
Ok.. Tried a partial Deodexing (app & priv-app only) and at least got it to boot with a repetitive F/C and metadata perms.. I there a str8 up issue with deodexing??
[SuperR Kitchen] ANDjROID:
ok. new update. (blu studio6.0 hd. mtk-6582) tried it using sparse dat. and building full rom zip. started with stock 5.0.2. debloated, made "custom list" out of the auto debloat list(just coppied the files i wanted to remove over to custom from the auto debloat) then when asked to auto debloat i chose no. then used custom debloat. everything is working. even wifi this time. for some reason, and maybe its because lollipop uses oat2dex, but it said my rom was already deodexed. will find out in next test build if it will make any difference. Anyways, flashed fine with no errors. all flashing seems to be going fine after i made adjustments to my device info in the device data in devices directory. and now even using data base to search for mmc_byname part works. All apps.(ones that are left anyways.)seeming to run flawlessly. no fc's, no faulty wifi, and no dead bluetooth, and the radio works fine. before i checked the superr mmc_byname i was using get from device, and it, for some reason, was wrong. i was getting the blk discard error, could not execute binary, no new list error, and a cpl others cant recall atm. but after changing the mmc by_name it flashes perfectly. in 2 forms so far. first test was a lil too heavy on the debloat, lost wifi, bluetooth, and radio didnt come in clear(even on known to be clear stations before mods.) and i went with auto debloat on first test build. so may i suggest, anyone having the flash errors. just check the data base for your device and make sure its right. i spent 2days trying to get my rom to flash and the whole time it was because of that. (or it seams anyhow). going to deodex then custom debloat on next build. will keep updated.
[SuperR Kitchen] bigrammy:
I thought I explained all that to you HERE as said the BLU Rom's are very weird so some kind of manual adjustments are inevitable as don't think any Kitchen on earth can be that intuitive. :silly:

The by-name/system equivalent in this ROM will be something like emmc@system etc etc ;)

It took some of the best mtk guys to figure out what was going on with this ROM so the fact that the Kitchen managed to make a working build at all is a real testament to it's dev [MENTION=5787964]SuperR.[/MENTION] :good:
[SuperR Kitchen] ANDjROID:
just a thank you

you certainly have to give credit where credit is due! and i give superR ALL THE CREDIT. i would never criticize someones work.(especially when its something i could NEVER DO.) and please dont be mistaken by my comment about it being wrong. i have no idea why. it was just stated so anyone else having trouble could maybe double check theres and make sure its right.(as i was seeing a lot of binary and blkdiscard errors) havent yet gotten to do a third test (debloat AND deodexed together.) but soon as i do im sure i will be back to give praise. (no pun intended) and thank YOU again bigrammy, without you i would still be stumbling around the archi thread!!!!! :good::highfive: