yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] SuperR.:
It is probably the deodexing causing your bootloop. As stated many times in many places in this thread, deodexing some Samsung devices does not work properly in the kitchen. Try without deodexing and it will probably work for you.
[SuperR Kitchen] minz1:
nah, i made a twrp backup, restored it, then the bootlooping started. i believe this will work fine, though. thanks, i can take it from here.
[SuperR Kitchen] SuperR.:
v2.1.0.7 (Donate version)

Changes:

Updated smali, baksmali, and oat2dex to the latest commits.

Added additional checks for set_metadata in case we need to set contexts for symlinks that only exist after the flash.

All contexts in file_contexts will now be added to the updater-script as long as the files exist in the rom, even if we don't have the correct uid/gid for the files.

Changed the order of the get by-name menu, making boot/recovery images recommended.

Added updater for the Installer/Launcher in case you are using Ubuntu4Kitchen or added the kitchen launcher manually.

v1.0.9.6 (Standard version)

Changes:

Updated smali, baksmali, and oat2dex to the latest commits.

Added additional checks for set_metadata in case we need to set contexts for symlinks that only exist after the flash.

All contexts in file_contexts will now be added to the updater-script as long as the files exist in the rom, even if we don't have the correct uid/gid for the files.

Changed the order of the get by-name menu, making boot/recovery images recommended.

Added updater for the Installer/Launcher in case you are using Ubuntu4Kitchen or added the kitchen launcher manually.

edit: The addition of the remaining file contexts may help with a lot of issues (ex. wifi not working). Previously, the kitchen used a database to check against with the uid/gid already filled in. It still does this, but now any contexts that are not in the database will be added at the end of the list. Unfortunately, I can't guess what the uid/gid should be for these files so we only set the context, not the permissions. If nothing else, this should give you a short list of the most likely files you need to figure out to get everything working in your rom. Let me know how it goes :)
[SuperR Kitchen] up.ssd:
oat2dex deodexing causing bootloop, SM-G900M.
[SuperR Kitchen] Mumang:
Thank you for the extended version, is to deal with plug-ins. There is a proposal to add the latest version of MTK SPFlashtool plugins in order to save time in order not to reboot for the firmware Windows.

It is much more convenient to collect TWRP and immediately flash and test.
[SuperR Kitchen] raheelkhattal:
Successfully made a marshmallow rom for moto g. When I flashed the rom for the first time, it was stuck on boot animation for almost 20 mins...so I reflashed the rom after which the rom booted in 15mins...can I reduce that time? I mean 15 mins is too long lol
[SuperR Kitchen] SpasilliumNexus:
Literally 3 damn posts above yours and in post #4...
[SuperR Kitchen] bcrichster:
If ya can't read, then don't post

Sent from CM12.1 *N9515*
[SuperR Kitchen] SuperR.:
I am not sure how this tool would work as a plugin. It is a stand alone application with no command line options as far as I can tell. There is a Linux version available so you don't need to reboot to Windows to use it.

Deodexed roms can take a long time to boot. You could reduce the boot time by leaving the rom odexed. If you are not modifying apks, there is no reason to deodex.
[SuperR Kitchen] luigimak:
[MENTION=5787964]SuperR.[/MENTION] I made a donation

Transaction ID: 1BS19691604035437

Gitlab account: blumak2000

Your kitchen is really "super" :D
[SuperR Kitchen] SuperR.:
Added, thanks :)
[SuperR Kitchen] Hard_Rock83:
why i am getting this

rroshan@L-MAA-25004925 MINGW64 ~/superrs-kitchen (master)

$ ./superr

ps: unknown option -- A

Try `ps --help' for more information.

ps: unknown option -- A

Try `ps --help' for more information.

is it only for unix and not windows
[SuperR Kitchen] bcrichster:
Have you tried at least reading the first few posts on this thread..??

Sent from CM12.1 *N9515*
[SuperR Kitchen] Hard_Rock83:
great...now what is this if i run its on linux...

[rroshan@userstage114288 superrs-kitchen]$ ./superr

-bash: ./superr: /bin/bash^M: bad interpreter: No such file or directory

[rroshan@userstage114288 superrs-kitchen]$
[SuperR Kitchen] bcrichster:
Every Linux OS needs dependency packages installed prior to running this software in order to make everything perfect. I don't know if you're trying to use Windows10 bash, Cygwin or Virtual Machine with this tho.. Or is this the new open source MS Linux?

Sent from CM12.1 *N9515*
[SuperR Kitchen] nightcervant:
Ohhhhhhhhhh good news my friend, you are the best.... I love your new version...
[SuperR Kitchen] not-i:
[MENTION=5787964]SuperR.[/MENTION] love to try the donate version mate. Haven't cooked a rom for ages.

Transaction ID: 78D6968020708934R

Gitlab username: not-i

Thanks and looking forward to giving this a spin :D
[SuperR Kitchen] dkionline:
Is it possible to unpack system.patch.dat or cust.patch.dat? would it be possible anytime?
[SuperR Kitchen] SuperR.:
It must be possible, but I have not tried. This link might help you. sdat2img is the tool the kitchen uses to decompress system.new.dat.
[SuperR Kitchen] not-i:
Not sure if I did something wrong but doing a test run I couldn't extract from the system.img (Note 4 N910C 5.1.1).

I've extracted it another way and copied he extracted system files into the system folder now to test the rest of the kitchen.

Deodexing seems to work so far.
[SuperR Kitchen] not-i:
Yeah that's what I did but no go for me unfortunately. I have previously extracted from same image no issues with archi kitchen (linux) and this time with img extractor in windows which I copied across

Also haven't been able to get the by_name partitions from boot.img so it seems like it hasn't been able to open the .img’s in this case.

As I said trying with Samsung Note 4 N910C 5.1.1 exynos firmware.

Maybe I will try delete the images and try again, who knows it may work
[SuperR Kitchen] not-i:
You can grab the firmware from here mate http://xdaforums.com/showthread.php?p=58800901 probably the quickest download.

It's the COH1 5.1.1 which is the first one
[SuperR Kitchen] Androidwizzard:
Short report about my yesterday's attempt on Note 5, 5.1.1 SM-N920I

Deodexing worked except for GsmCore.apk :confused:

and Knox apps, which is convenient as they got to be removed.

Re-packing kernel seemed to work but make it flashable didn't (something about by_name), anyway no big deal.

Final thoughts as soon as my rom is ready and flashed for the first time.
[SuperR Kitchen] SuperR.:
strange, this extracts with no issues for me. Could you please provide some system info for me?
[SuperR Kitchen] not-i:
Running this http://xdaforums.com/showthread.php?p=48848649 in latest VB.

4th gen i7 with I think 12gbs ram. Might be more can't remember I'm out at the moment

I have 4 cores and 10gb ram set for it in VB
[SuperR Kitchen] not-i:
Mate I just had another look at the file and I feel really dumb. The system.img that I had copied over was too small so looks like the full .img didn't get copied which would explain a few things. I'll try it again and see how I go. Thanks for your help though
[SuperR Kitchen] bcrichster:
..everyone keeps trying to give us Firmwares. Bad idea. Just give us the boot.img & system folder instead. With OEM firmwares, it BUILDS the build props upon installation. We need the prebuilt build props ..
[SuperR Kitchen] Androidwizzard:
You can have everything you want from me in case you are interested in Note 5 support for the kitchen.
[SuperR Kitchen] bcrichster:
Do you have a custom recovery on ur Note5?
[SuperR Kitchen] Androidwizzard:
Tonight yes, I will flash TWRP or Philz
[SuperR Kitchen] not-i:
I was out and wasn't able upload anything and the link for firmware was the best i could get at the time. He ask for system.img by the way not folder as my problem was extracting from .img. Anyway all good now as it was just a silly mistake i had made and not the kitchen
[SuperR Kitchen] SuperR.:
For some reason, Maps and related apps have had some issues being deodexed in 5.x.x. I have still not found a solution. This problem exists in all Lollipop deodex tools including the ones for Windows. Will keep trying

Based off the note 4 boot.img I got from not-i, it seems Samsung is still using the older /dev/block/mmcblk style in their fstab which will cause problems detecting from the boot.img. Have you tried detecting by-name from your device?
[SuperR Kitchen] SuperR.:
Just pushed a bunch of changes and added a new zip to the downloads.

Changes:

Added the beginning of a device repo for the non-by-name devices of the world (Note 4 I am looking at you...and many others lol). You will find one example of the format that file should be in once you update the kitchen to v0.8.8.3. It is located in /kitchen_root/devices/trelte/superr_mmc. This one happens to be for the Note 4, but the directory/file structure should be the same"

kitchen_root/devices/device_codename/superr_mmc

The device codename is found in build.prop under "ro.product.device". In the example case, that line says "ro.product.device=trelte"

Unfortunately, you will also need to rename the current devices/device_codename/projectname directories. They must now be appended with "project_".

Sticking with the Note 4 example above, previously the directory structure was: /kitchen_root/devices/trelte/projectname

Now it needs to be

/kitchen_root/devices/trelte/project_projectname

Alternatively, you could delete all your projects and devices, update the kitchen, and start over. I apologize for the inconvenience.
[SuperR Kitchen] bcrichster:
Then this is a Beautiful "pain"
[SuperR Kitchen] not-i:
With the Note 4 there are multiple versions plus exynos and Snapdragon versions which is a pain in the you know what.

I have cooked roms for exynos versions N910U (trhplte), N910C (trelte) & N910H (tre3g) and have been using the following mount script which works across all of them -

run_program("/sbin/mount", "-t", "auto", "/system");

run_program("/sbin/mount", "-t", "auto", "/preload");

run_program("/sbin/mount", "-t", "auto", "/cache");

run_program("/sbin/mount", "-t", "auto", "/data");

All three of the different versions of exynos have worked with this script and have been able to be flashed on each other. (They do have some differences biggest one is modem & some radio related files but for example I can flash N910C firmware on my N910U and all works except for carrier 3g/4g signal until I mod some files & change modem & kernel to device specific).

With your line below it was unable to flash across the devices as was device specific (obviously) -

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

Maybe it would help to use my code or is there some issues with it? I'm no great developer or anything but I haven't found any problems so far.

Or perhaps is there a way to include the 3 models in the getprop("ro.product.device") code?

Boot image though is still this for all the exynos Note 4 models -

package_extract_file("boot.img", "/dev/block/mmcblk0p9");

Hope this helps especially with the multiple version Samsung phones

EDIT: At the moment though I will just add the different models to my devices folder. If you want to add them in a future version the ro.product.device for these models is as I have written above
[SuperR Kitchen] SuperR.:
Thanks for the info. The following assert should work for all 3 devices.

assert(getprop("ro.product.device") == "trhplte" || getprop("ro.product.device") == "trelte" ||
getprop("ro.product.device") == "tre3g" || abort("This package is for \"trhplte,trelte,tre3g\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
[SuperR Kitchen] not-i:
Thanks mate.

Also notice with the knox option could you use -

system/app/KNOXAgent

instead of -

system/app/KNOXAgent.apk
system/app/KNOXAgent.odex

then you will also remove the folder?

I've notice some more knox libs in 5.1.1 you could add to the removal script too

libknox_encryption.so
libknox_km.so
libknox_legacy_ode_km.so
libknox_migration.so
libknoxvpnfdsender.so

Cheers mate its looking great :)
[SuperR Kitchen] SuperR.:
Moving on to v0.8.8.5

Changes:

Added ability to add devices to and completely change the asserts.

Added some knox files to the bloat list per the post from [MENTION=4503214]not-i[/MENTION]
[SuperR Kitchen] jtash01:
Is there a way to add a custom debloat list to the kitchen?
[SuperR Kitchen] morissio:
Thanks SuperR you are too fast :D

I installed the lib lib32stdc++6 and the now the error is disappear. Sorry!.

Thanks for all!!
[SuperR Kitchen] SuperR.:
v0.9.1.9

Changes:

Added dependency check for lib32stdc++6.

Changed sdat2img from .py to binary to avoid the python dependency

Some other things I can't remember
[SuperR Kitchen] DarkHeart Z:
I meant to say how do I use my devices mountpoints which I have set under devices directory ? So that I would not have to edit the updater-script again ? some request , please add aroma support and root kernel feature . Would love to try those . your tool is so easy to use :)

edit : Sorry , I understood now how to use it .
[SuperR Kitchen] SuperR.:
If your device uses by-name, you will not need to modify anything in the devices directory. If your device does not use by-name, you will need to create a superr_mmc file for it. You can use the warp2 and trelte devices (included in the kitchen) as guides. Make sure you have it set up exactly like those examples and the kitchen will use it automatically.

edit: REMINDER TO EVERYONE, if you create superr_mmc files for any devices, you can use the "Zip mmc devices" option on the main menu to zip them and send them to me to add to the kitchen. It only zips the config file so the file will be very small :)
[SuperR Kitchen] DarkHeart Z:
I am creating mine right now and also creating zip_mmc and sending them right to you . i would love to help you with your kitchen providing info's as much as I can . :)

---------- Post added at 09:28 PM ---------- Previous post was at 08:59 PM ----------

I started a project and it automatically created a device folder , but problem is it only showing superr_byname . and I only seen one entry inside it /dev/block/mmcblk0p4 . Can I know why ? It's only the system mountpoint . why the rest haven't writen inside it automatically ?
[SuperR Kitchen] SuperR.:
Well, your device probably supports by-name and you don't need to make an mmc file. There is only one entry for by-name devices in the superr_byname file and it would not be the one you posted. It would be something like "\/dev\/block\/platform\/msm_sdcc.1\/by-name". By-name takes care of all the other partitions so there is no need for a superr_mmc file if your device supports by-name.
[SuperR Kitchen] DarkHeart Z:
I am in . I have an mt6572 phone which has very few support from it's vendor . And my carrier is symphony . I can provide the lists I have and I will . But how ?

---------- Post added at 10:11 PM ---------- Previous post was at 10:05 PM ----------

It's been a priviledge . Thanks!!!! working on a cm 12.1 rom . With your kitchen , the work will be finished much faster than I expected . And something more I wanted to specify . My device doesn't use direct links to the block files like /dev/block/mmcblk0p4 or mmcblk0p5 . It uses emmc@android , emmc@usrdata , emmc@cache etc which is a link to the specific block file . I don't know if it will create a problem . :rolleyes:
[SuperR Kitchen] sebastiandg7:
SuperR, thanks for this INCREDIBLE tool!

I am having a little problem (I'm using v0.9.1.9): I create a project, then copy a cm12.1 zip to the folder, select sparse dat when extracting but it says "This ROM is NOT Lollipop or beyond".

Can you help with that?

Thanks, awesome work!
[SuperR Kitchen] SuperR.:
Can you send a link that does not require registration to the cm12.1 zip you are starting with?
[SuperR Kitchen] sebastiandg7:
Here it is:

https://mega.nz/#!Y4cWBaAK!DGrQ3eGyEt9v1K2NhitN84ap7pgp65_XvveEituxrRo
[SuperR Kitchen] SuperR.:
v0.9.2.0

Changes:

Changed back to sdat2img.py because the binary is not working properly

Some other minor changes

[MENTION=5764293]sebastiandg7[/MENTION] This should sort out your problem
[SuperR Kitchen] sebastiandg7:
Sir, I have got no words to describe how thankfull I am with you due to this work. Thanks a lot for this, for the support given, not only to me but to all other users. Your kitchen inhales hours of hard work and exhales perfection.

I will let you know how things are doing after using this monster!
[SuperR Kitchen] bcrichster:
Thank his posts.. [emoji41]

Gratefully sent from my Rooted Tesla N9510
[SuperR Kitchen] binhdb:
good like
[SuperR Kitchen] beefx:
https://mega.nz/#!4IAVGBjC!XGRPBqUSXpuX1Si39zCmz6iBgdmMQXHHiFPPkGGMlsk
[SuperR Kitchen] SuperR.:
Your device does not support by-name which is why you are having problems. I created the mmc file for you. Go to /kitchen/devices and delete the existing tre3g directory. Unzip this and copy the tre3g directory into the /kitchen/devices directory. Then try again :)

This will be included in the next version for everyone else that has this device.
[SuperR Kitchen] DarkHeart Z:
no recovery extraction support

I can't extract recovery.img using this tool . please add support for it .
[SuperR Kitchen] SuperR.:
Please link recovery.img in a place that does not require registration.
[SuperR Kitchen] DarkHeart Z:
All these are for mt6572 socs . I was trying to port them .

cwm 6.0.4.5

CWM-6.0.4.6

CWM-5.5.0.4

PHILZ-mt6572

TWRP-mt6572

Also bug report by name detection stuck at 'detecing by name from boot.img' . couldn't use from device because my phone is in running a custom rom now . please fix it too . Incase you need here is the boot image . After getting it fixed I will send you some zip mmc of some mt65xx devices for adding . Just where do I send them let me know . :)

Edit : my device has/dev/block/platform/mtk-msdc.0/by num instead of name and also /mtk-msdc.1/by-num also

---------- Post added 12th October 2015 at 12:29 AM ---------- Previous post was 11th October 2015 at 11:40 PM ----------

I hope you got the bug reports . I am stuck here because of this bugs .
[SuperR Kitchen] bcrichster:
Is it possible to do with kitchen or is it better as a standalone app?

Sent from CM12.1 *N9515*
[SuperR Kitchen] dkionline:
Yes right, but its a patch and locked. Cant open or unpack.
[SuperR Kitchen] SuperR.:
The kitchen currently only deals with system.new.dat which is a system image. patch.dat files are for OTA updates according to the link I posted earlier. Generally, patch files are useless other than their intended purpose of patching existing files. Is there a use case for extracting patch.dat files in the kitchen?
[SuperR Kitchen] bcrichster:
In that context, no Sir. [emoji16] I still don't know how you were able to take apart our Warp(s) update.zips and discern whatever their intentions Since I only got a jumble of symbols when I tried a year or so ago..

Speaking of the Warp Sync: there is another update to check out to make sure your update.zip doesn't need any modification. There were apparently two updates from B05 to B07 and all the changes we done were meant for B05 - B06. We never checked out that next B06 - B07 update zip, so those who Rooted, TWRP'd, & ROM'd while on B05 are running on B06 partitions instead of B07. It's not causing any known issues yet but now my curiosity is peaked. As well, how do I open update.zips with files that can explain what the heck they did? Lmao [emoji41]

Sent from CM12.1 *N9515*
[SuperR Kitchen] haije:
Every time I cook a rom, I get: kernel is not seandroid enforcing and it keeps running in bootloop... I use the donated version of the rom. My device is Galaxy s6 Edge.

What I do is: I get the firmware from sammobile, extract it using the kitchen. Unpack boot.img, root, dm-verify repack kernel with ramdisk. Furthermore I debloat, deodex and I putted in note portes apps. Also tried to wipe everything and flashed arter97 kernel, but nothing works, device wont boot... does someone know what the problem is?
[SuperR Kitchen] dkionline:
[MENTION=5787964]SuperR.[/MENTION] the main part is, directly integrate that in the ROM. The problem is, every time an ota update comes, it needs to flash stock recovery and if its a fullrom instead it locks the bootloader and need a full wipe after unlock.
[SuperR Kitchen] bcrichster:
As in: make an OTA into modifiable (to remove signature requirements &/or stock recoveries) zips flashable with TWRP?

Sent from CM12.1 *N9515*
[SuperR Kitchen] SuperR.:
I will reply on the stock B07 sync thread :)

I suggest trying to build an unmodified rom first. Extract the firmware and build the rom. If it works, then you know one of your modifications is causing the issue. Then add each mod individually and build the rom until you find the one that breaks it. I also suggest set_metadata perm type in case you are using something else. set_metadata is currently the most stable option in my opinion.

Back when I was active making roms for various devices, this is exactly what I did. Return the device to factory, take the update, and create a new rom from the updated system. It is a necessary evil. On the bright side, you can make a data backup in twrp before wiping the data so it is pretty easy to recover.
[SuperR Kitchen] Mentalmuso:
You're deodexing Samsung. Try without deodexing first, see if it boots

? --->
[SuperR Kitchen] not-i:
Hi guys, cooked a rom for Galaxy Note 7 N930F. I haven't deodexed or anything just pretty much a basic rom. Got this error when flashing which I haven't had before and can't find on google search -

"updater process ended with error 3 twrp"

Anyone know what error 3 is? Cheers guys
[SuperR Kitchen] bcrichster:
[MENTION=5787964]SuperR.[/MENTION] , I think you're being observed & studied without knowledge so I have also included the findings which lead me to that assumption: [emoji41]

Sent from CM12.1 *N9515*
[SuperR Kitchen] SuperR.:
I have not heard of this before either. If you post the recovery.log after flashing and the updater-script maybe we can get a better view. Thanks

edit: I found this post with the same error. Maybe [MENTION=4835387]OvrDriVE[/MENTION] found the problem and can shed some light
[SuperR Kitchen] minz1:
Hey [MENTION=5787964]SuperR.[/MENTION], have you heard about the whole deal with CCMT and SuperSU? Not many people really trust the app anymore.. have you considered replacing the SuperSU root option with phh's Super User?
[SuperR Kitchen] OvrDriVE:
i know exactly what the problem is. you havn't deodexed the rom. the rom is to big for twrp and it doesn't know how to handle it. twrp seems to have a 2gig filesize limit. anything bigger then that and you will get an error 3 exit code. either deodex rom or debloat it below 2gig and it should flash fine

btw thanks for an awesome tool superr. i used it the other day to build a 930f rom for a friend and it worked great.
[SuperR Kitchen] SuperR.:
I have heard about it and I have not considered changing it yet. I am willing to hear both sides of this argument and possibly put it up for a vote.

I have never used phh superuser personally so it would need to be tested with the kitchen. This can be done very easily. Add the new superuser.zip to the /kitchen/tools/root/supersu/ directory. In the kitchen, you will be given a choice of which zip to use. Choose the new one. If you are asked which root method you would like to use, choose "let supersu decide". The kitchen will use the new superuser.zip in your rom. Let me know how it goes :)
[SuperR Kitchen] minz1:
Okay. I will test it out and give you the results soon. I'll edit it in this post.
[SuperR Kitchen] SuperR.:
Thanks for the good advise :)

I had no idea twrp had a 2GB file size limit. I understand why they might have a 4GB file size limit (fat32), but 2GB is small for a rom these days. Oh well, at least we have our answer. Thanks again :)

edit: I will add a check to determine if the zip will be over 2GB and if so, provide a warning before building the rom.