yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] bcrichster:
it updated just fine but still says another version, didn't know if i needed to repull from scratch to ensure proper functions
[SuperR Kitchen] SuperR.:
If it does not say v0.9.5.0 after updating then something is wrong for sure. I suggest a new clone.
[SuperR Kitchen] bcrichster:
reClone it is! Ty- Sir
[SuperR Kitchen] bcrichster:
devices

here's my few devices collection

LG Realm

LG Exceed 2

ZTE Concord 2

Kyocera Hydro Icon
[SuperR Kitchen] enotar:
Anyway you could fix set_metadata permissions for wifi not turning on on Samsung?
[SuperR Kitchen] sparks15:
[MENTION=5787964]SuperR.[/MENTION]

Not working deodex, no errors, rom install fine but fails google play services on adding account. any idea?

With odexed runs fine.

What Kitchen version?

0.9.4.6

What Linux are you running?

Ubuntu 15.10 x64

What device are you working on (make/model)?

Nexus 6

What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)

system.img and boot.img

What Android version?

6.0 MRA58R

What perm method (set_perm, set_metadata, sparse_dat)?

set_metadata

Were there errors on the screen if you scroll up in the terminal?

None
[SuperR Kitchen] SuperR.:
Not sure if you got this reply and I am still interested if you have the time. Here is the reply again :)

"Which boot.img are you using that is working, the chainfire method or the kitchen? If you are using the chainfire modded boot.img, please try the kitchen modded boot.img along with your new updater script or just flash the kitchen created boot.img to see if everything still works. Just trying to track down the issue, whether it is the boot.img or the updater-script.

Can you send me the updater script that is working for you and the kitchen generated one for comparison?

Thanks"

Absolutely. Just as soon as someone tells me why it is not working ;)

No idea. If I had one I would have answered you the first time you asked :p
[SuperR Kitchen] fhem:
I have sucessfully used this great kitchen to build deodexed (sparse_dat) roms for both the Nexus 9 and the Nexus 6P. I always replace the core gapps w/ the latest apps from banks, apkmirror or other sources. I also always use a permissive a K which I build from source to assist w/ rooting. I have tried many different times to build a deodexed version for the N6 ---- No go --- I always get the rom to boot but can never get thru the google signin w/o getting play services f'c. I have given up for now. Hope you can work it out.
[SuperR Kitchen] asc1977:
Please i need help again

I downloaded a 5.1.1 S6edge stock Firmware. Unpack and get a tr.md5 file.

I work on newest Ubuntu.

Now i select point 1 to create a new rom and put tar file ( renamed from tar.md5 tp tar) in working folder. Kitchen sayas this is no namdroid tar file.

Ok now i unpack tar file and put this files in working folder and start with point1 to create new rom but kitchen cant unpack system.img.

What do i wrong? In moment i use kitchen from dxdias and create working folder and put this one in your kitchen to work on it.

Please help for the first steps

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] PaulPizz:
Right click on your "tar.md5" file and hit rename. Remove the ".md5" so your file is only a ".tar" file. Then extract that ".tar" file and inside that folder you will find the files you need. [emoji1]
[SuperR Kitchen] asc1977:
Yes that is what i done. But kitchen cant work with system.img i give him if i choose create rom. The kitchen dont unpack the img

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] bcrichster:
Do you have all dependencies met from post #4? And newest one a page or two back?

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] asc1977:
yes downloadet newest one. on first start the kitchen told me what missing. i installed from ubuntu store the 7zip gawk and one other and also write me to things with sudo wich i must type in terminal to install. i think all is set right because all work only not the first step to build rom. i put my boot.img and system.img in working folder. some files the kitchen unpack but not the files from system.img like app, priv-app, framework ......

i really dont know whats the problem.
[SuperR Kitchen] bcrichster:
Are you possibly running a 32 bit OS?

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] asc1977:
Yes its the 32bit ubuntu version. Bit now please dont tell me i meed the 64bit version [emoji1]

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] AenieE:
Update

I have a small problem updating from 0.9.1.5 to current version:

neither outside nor in kitchen itself it does although in terminal it's running through but when I launch -> nothing changes.

thx in advance for a small hint :highfive:
[SuperR Kitchen] xdadroidabc:
Error

"sepolicy-inject could not be built."

Installed both missing dependencies

sudo apt-get install p7zip-full gawk

sudo apt-get install lzop bison gperf build-essential zlib1g-dev zlib1g-dev:i386 g++-multilib libxml2-utils bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev libsepol1-dev dpkg-dev make

Java 7 installed

Ubuntu 12.04 LTS

64bit

Thank you.
[SuperR Kitchen] asc1977:
I am right with these:

If i use ubuntu 32bit i must use 32bit binarys and if i use ubuntu 64bit i must use 64bit binarys?

And if i installed without binarys the kitchen download by itself if i am right but which binarys?

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] sefrcoko:
Sorry been a crazy week! Yes I saw your message and have been trying to find some time to test. Should have a moment in the next day or two and will definitely post back here with the results! :) Thanks for all your help with this!
[SuperR Kitchen] dr.manoj_n:
Realy super

Very simple
[SuperR Kitchen] SuperR.:
There have been many changes since v0.9.1.5. It would be best to delete the kitchen and start over.

I am not sure why it won't build. You could do some research about compiling binaries in Ubuntu 12.04, or you can grab the pre-compiled binaries from post 4 and unzip them to the tools directory. If you choose to do research, you can start by opening a terminal in /kitchen/tools/source/sepolicy-inject and running "make". You will get errors that may tell us what is going on.

You are correct that if you are using the pre-compiled binaries you need the 32-bit for a 32-bit system. However if you don't use the pre-compiled binaries, the kitchen does not download them it builds them from source

Excellent, thank you :)
[SuperR Kitchen] DarkHeart Z:
yes unless you have a multiarch kernel ( google for more info ) . 32 bit binaries are only for 32 bit and 64 is only for 64 bit in a regular case . And no kitchen won't start working unless you compile the binary for kitchen . Though it does it automatically . all binaries are listed in the the changelogs check 0.9.4.x for all binary info .
[SuperR Kitchen] Alan-B:
Hello, Good Kitchen, thanks ...

But some problems for SM-P605 in 5.1.1 with the updater-script which is very sensitive to the modifications!

The assembly of partitions does not pass always well!

The slightest modification and nothing more goes!

Has you he of particular options there to have of best ?
[SuperR Kitchen] SuperR.:
v0.9.5.1

Changes:

Converted all external scripts to functions.

Removed 500+ lines of code.

Added more info to some of the error pages.

Improved some of the CURRENT: status messages for clarity.

Fixed system.img partition size detection for by-name/APP and by-name/SYSTEM devices.

Removed unmount /data from updater-script unless user app support is enabled.

Added devices from [MENTION=5297774]bcrichster[/MENTION] and SM-G360T1.

NOTE: Under the hood, this is a big update and it is possible that something got broken along the way. Let me know if you find anything wrong so I can get it fixed asap. Thanks :)
[SuperR Kitchen] DarkHeart Z:
can't change device asserts anymore . cyanogenmod 12.1 rom has device asserts under projects folder . init.d support in boot.img not displays anything . just blank like init.d support : ) . no yes or no . if i choose it ; it says you already have init.d support that's confusing kinda .
[SuperR Kitchen] SuperR.:
This works for me, so I am not sure what is going on. Are there errors you can see if you scroll up in the terminal?

I don't understand what you mean

Fixed. Thanks for pointing it out :)
[SuperR Kitchen] DarkHeart Z:
it's the same as init.d . it doesn't show anything . it's like change device asserts : ) . and whenever I choose it . it shows errors like no device asserts found when under project folder there is device asserts . And it happened with cyanogenmod rom . Though it's my first test and I got this error . It worked before . but now it doesn't .
[SuperR Kitchen] SuperR.:
I am not able to reproduce the problem. The device asserts (adding/changing/status) are working perfect for me. I even extracted a cm 12.1 rom for testing. Would you mind downloading v0.9.5.0 again from the downloads section of the kitchen repo and trying exactly the same steps with exactly the same source to be sure?

Anyone else having this issue? Please check under ROM Tools menu if you see the asserts listed, and then try to add one even if it is fake just to see if it works. Thanks
[SuperR Kitchen] xdadroidabc:
Thank you very much.

By the way I have updated OS to 14

and here is output after 'make'

root@office:~/Desktop/SuperRs_Kitchen_v0.9.5.1/tools/source/sepolicy-inject$ make

make -C libsepol/src

make[1]: Entering directory `/home/root/Desktop/SuperRs_Kitchen_v0.9.5.1/tools/source/sepolicy-inject/libsepol/src'

cc -Werror -Wall -W -Wundef -Wshadow -Wmissing-format-attribute -O2 -I. -I../include -D_GNU_SOURCE -I../cil/include -fPIC -c -o ../cil/src/cil.o ../cil/src/cil.c

../cil/src/cil.c: In function ‘cil_get_symtab’:

../cil/src/cil.c:1515:2: error: comparison of unsigned expression < 0 is always false [-Werror=type-limits]

cc1: all warnings being treated as errors

make[1]: *** [../cil/src/cil.o] Error 1

make[1]: Leaving directory `/home/root/Desktop/SuperRs_Kitchen_v0.9.5.1/tools/source/sepolicy-inject/libsepol/src'

make: *** [libsepol.a] Error 2

root@office:~/Desktop/SuperRs_Kitchen_v0.9.5.1/tools/source/sepolicy-inject$
[SuperR Kitchen] DarkHeart Z:
Ok . onto that right away . looks like device asserts are something else . or kitchen can't read the project file asserts for some unknown reasons .
[SuperR Kitchen] asc1977:
Sorry if it is offtopic or hope the tool can do. I want to build additional a flashable odin file for flash sboot.bin modem.bin and cm.bin

Is there a way in tool or how can i do

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] Androidwizzard:
search for tar and/or md5 tool and you will find very small and easy to use programs

EDIT: SEARCH RESULT
[SuperR Kitchen] asc1977:
Very very very thankfull for this

[emoji120] [emoji120] [emoji120] [emoji120] [emoji120] [emoji120] [emoji120] [emoji120] [emoji120]

I searches the hole day and tested a lot but this works like a charm

THX

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] SpasilliumNexus:
Sparse creation is borked again with 0.9.5.1.

Applying the changes from this commit into ./superr fixes it again.
[SuperR Kitchen] SuperR.:
v0.9.5.2

Changes:

Fixed init.d status.

Fixed partition size detection.

Added option to install missing packages on debian-based systems.
[SuperR Kitchen] Alan-B:
hi,

Why this command prevents the flash ?

***

#ASSERT

assert(getprop("ro.product.device") == "lt03lte" || getprop("ro.build.product") == "lt03lte" ||

abort("This package is for "lt03lte" devices; this is a "" + getprop("ro.product.device") + "".")

***

this line also

format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");

***

And why twice the commade ? (The first one does not works , the second yes !! it is a problem for Aroma, apk in data erasure )

ui_print("Extracting data..."); ui_print("");

package_extract_dir("data", "/data");

There is not a more complete glossary of steps Page 1 ??

thank you in advance
[SuperR Kitchen] SuperR.:
v0.9.5.3

Changes:

Improved the package installer for missing dependencies.
[SuperR Kitchen] pendor24:
hello Hello

always a problem with the boot unpack repack img

it will not work ( erreure line 72 and 83) unpack MTK
[SuperR Kitchen] SuperR.:
I do not understand the problem. Please read post #4 and answer as many questions with detail as possible.

MTK unpack/repack is done with MTK Tools. If MTK Tools does not support your device, neither will this kitchen.
[SuperR Kitchen] pendor24:
I've created for the SM- 3 rom N910f = trlte ( I created the folder devices ) with your kitchen

I find other tools to unpack repack . thanks anyway
[SuperR Kitchen] sefrcoko:
It looks like samsung just pushed a security policy update a few days ago that kills root and causes bootloops when using a modded enforcing kernel on 5.1.1. Still investigating to see if there is another workaround, but for now it seems like we'll need a selinux permissive custom kernel like Emotion, AEL, or Beastmode to avoid bootloops on rooted 5.1.1 roms. I was hoping to try my previously-working updater-script with the kernel built through your kitchen like we talked about, but it seems like that won't work now either way due to samsung plugging the vulnerability. Chainfire is away but might hopefully have some news when he gets back... damn Samsung!
[SuperR Kitchen] asc1977:
I am on my newest rom 925FCAM..K6 with this security patch and without problems. With unikernel and vindicator kernel no bootloops or reboots or loosing root. Hope this is what you mean and i can help

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] sefrcoko:
Pretty sure that security policy is different...the one i mentioned was for another device (Samsung N910W8) and only pushed out a few days ago. Chainfire's modded selinux enforcing kernel workaround might still work on other devices but multiple users reported that it breaks root and causes bootloops on 5.1.1 Sammy devices like mine, N910F, etc. Not much more info at the moment because chainfire is away...
[SuperR Kitchen] SuperR.:
v0.9.5.4

Changes:

Fixed custom zips and boot/recovery zips for by-name/APP devices.

Fixed the text entry fields adding strange characters when using the arrow keys to edit.

Code optimization.
[SuperR Kitchen] Alan-B:
Re...

Everything works without errors to Ubutu 64, it is not the problem.

It is the generator of 'updater-script' that is not well adapted!

It puts twice extract data under extact System and at the end before the installation of SuperSu.

What is the reason?

Add of Aroma give many problems! The superuser does not settle down any more and data them either!

SAMSUNG Note 2014 SM-P605 rom 5.1.1

PS: Which choice is best for the 'updater-script'

Set-metadata or set-perm ?

my updater-script:

https://mega.nz/#!RtIDHaDI (Key) !EC6TeYYcjxcLAN7dRY2klTIXhfIFcfoePGeKPlrWBD8
[SuperR Kitchen] SuperR.:
Update your kitchen. The double unmount /data was fixed a few versions ago.

set_metadata is generally better for KitKat and above as it includes selinux contexts.

edit: This kitchen does not support Aroma. Check their support threads for help.
[SuperR Kitchen] xdadroidabc:
[MENTION=5787964]SuperR.[/MENTION]

sir i have posted output of make here too.

http://xdaforums.com/showpost.php?p=63885478&postcount=1075

Again did it on latest base and selected option yes when asked me to install package but still same

It is possible to skip this check when kitchen requires to push sepolicy inject so I can use tool to make deodexed ROM just. I don't need stock kernel but just want to use deodexer tool if possible please sir.

Thank you in advance.
[SuperR Kitchen] Er. Aditya:
please bro also add option to add init.d support
[SuperR Kitchen] Androidwizzard:
BTW: You have 9 files in your N5 rom V2 which aren't deodexed correctly - just in case you've done it with this kitchen, nothing important but I'd like to have mentioned.
[SuperR Kitchen] SpasilliumNexus:
Did you at least go through every menu in the kitchen?

It's even in the second post
[SuperR Kitchen] Er. Aditya:
thanks bro and yes i used this kitchen to deodex the note 5 but i remember correctly it showed rom status deodexed

sorry my bad and thanks bro
[SuperR Kitchen] Alan-B:
Re Hi,

With the new version, .ext4 do not pass to extract ! It is necessary to delete .ext4 and to leave .img!!

PS: There is always twice 'package_extract_dir("data", "/data");' !!!

And the first lines of the script prevent the flash .................
[SuperR Kitchen] DarkHeart Z:
the previous problem I stated exists . whenever tried add/remove asserts option from rom tools it says there is no asserts to amend . Everytime it kept happening . Only with cyanogenmod 12.1 rom . the assert file remains under projects directory . I checked it .
[SuperR Kitchen] fhem:
N9 and N6P vendor images

[MENTION=5787964]SuperR.[/MENTION]

Ok -- I'm testing your rebuilt kitchen w/ Nexus 9 (MRA58N) and Nexus 6p (MDB08M) factory images. Both of these devices have separate vendor images that are not part of the /system partition -- these vendor images need to flashed to the /vendor partition.

Nexus 9

block_image_update("/dev/block/platform/sdhci-tegra.3/by-name/VNR", package_extract_file("vendor.transfer.list"), "vendor.new.dat", "vendor.patch.dat");

Nexus 6P

block_image_update("/dev/block/platform/soc.0/f9824900.sdhci/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat", "vendor.patch.dat");

I have tried including the vendor images when building (odexed just to test) roms for both these devices. The kichen unpacks the vendor image but it does not build the vendor sparse dat files ............ So I am not sure what is going on. What am I missing????? FYI - I had the same issue before the rebuild.

Thanks for your continued support and great work.
[SuperR Kitchen] SuperR.:
Try the new version I mention at the bottom of this post :)

The kitchen never supported *.ext4 img files

Your flashing issue is with asserts. Go to ROM Tools, Asserts, and add "lt03ltexx" to the list.

Send a link to the ROM. I am not able to reproduce your issue.

How are you detecting the vendor partition size? When I tested, I used the vendor.img and it builds the vendor.new.dat without issue for the Nexus 9 at least.

v0.9.5.5

Changes:

Added option to install the binaries if you have tried installing the recommended packages through the kitchen and they still fail to build.
[SuperR Kitchen] enotar:
For assert, you need to add xx to the end of lt03lte or do lt03lte,lt03ltexx in the kitchen, I had the same problem and it works for me
[SuperR Kitchen] DarkHeart Z:
I think the beginning line when starting a new project from a rom zip ( cyanogenmod 12.1 ) there is always an error like this : grep: Invalid regular expression

grep: Unmatched [ or [^

when checking updater script this line pops up at very first . maybe it has to do something with the assert . And Here is the link to the rom .
[SuperR Kitchen] xdadroidabc:
Thank you very very much sir. I have not tried ROM but got kitchen menu now.

Thanks a lot sir.
[SuperR Kitchen] fhem:
Looks like something not right not sure what. Please take a look. Thanks thats still the Nexus 9. Recloned and I used clean images.
[SuperR Kitchen] SuperR.:
I fixed all the issues for your rom and found some other things to improve along the way. Will be a new release as soon as I fix whatever is going on with the problem below.

I do not get these errors on the N9 :( Can you paste the resulting updater-script after these errors occur so I can see what is not being accomplished? Thanks

edit: It might be your version of gawk now that i think of it. inplace was not available until gawk 4.1.0. You can check by opening a terminal and issuing "gawk -V". Let me know if that is the problem.
[SuperR Kitchen] fhem:
Yep that may be it I got gawk 4.0.1 on both my linux builds. That is the latest version shown on Synaptic Package Manager from Ububtu. I will find another source if I need later version.
[SuperR Kitchen] SuperR.:
v0.9.5.6

Changes:

Properly extract symlinks if [ character is included.

Properly create a new mmc or by-name device from extracted rom zip if it does not already exist.

Don't mess with set_metadata in existing rom zip if it is /tmp.

Fixed assert status display if there is more than one abort line in the updater-script.

Removed gawk inplace for portability.
[SuperR Kitchen] fhem:
Thanks I already updated to gawk 4.1.1 from a ppa and its working great --- you are much too quick for me LOL :good::good::D
[SuperR Kitchen] diabl0w:
does the kitchen break roms that are in f2fs format?
[SuperR Kitchen] SuperR.:
There is not specific support for f2fs. The updater-script and system.img creation will not work properly since they are set to ext4 only. This may change in the future, but no promises.
[SuperR Kitchen] diabl0w:
archkitchen did a great job with its updaterscript not interfering with filesystem type if you want to check out how that developer did it
[SuperR Kitchen] bcrichster:
[emoji33] Ur barking up the wrong tree, bro! [emoji12] Lmao. Believe me, he knows ArchiKitchen pretty in depth and refers to it IF necessary. SuperR Kitchen is written from scratch but IMPROVED ideas/tools from ArchiKitchen, dsixda kitchen, Android Image Kitchen, ect, All rolled into one.. You get the point. Archi was strictly a Samsung deal for one, Samsung has made MANY changes since Archi's inception also. You can't and WON'T beat the SuperR Kitchen in any way. If ArchiKitchen works better for ya somehow, then by all means use it but that Dev won't even try to update that kitchen. So.. Good luck! [emoji23]

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] DarkHeart Z:
looks like the grand master finally fixed the issues thanks a lot lot more man today turned out to be a lucky day for me :D
[SuperR Kitchen] diabl0w:
lol im not barking up a tree and to put it bluntly not having f2fs support is not an improvement from having f2fs support. tjat being said, obviously im not trying to come at superr with negativity but just offering another idea and route to solution for that idea. that also being said i think [MENTION=5787964]SuperR.[/MENTION] could speak for himself and doesnt need you to do it for him

p.s dont wink at me.. its weird and rude. and also rude to laugh at people
[SuperR Kitchen] bcrichster:
Touché, but I'm sure the idea was already churning in his head when you expressed the need..? I was also only referring to the trees when you mentioned Archi's project... [emoji6]

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] SuperR.:
We are all friends here. Thank you both for the support :)
[SuperR Kitchen] bcrichster:
Ur being haha-funny so I can't help but crack up. No rudeness intended tho. :cool:

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] :
I've never seen a rude post from you, anything Linux/kitchen related you are both knowledgeable and helpful, especially to us that really need your knowledge
[SuperR Kitchen] enotar:
This is getting better everyday. Thank you for that.

Btw i use F2fs with CM 12 and no gain at all so no need to bother.
[SuperR Kitchen] bcrichster:
Thank you Sir, [MENTION=1097804]sawdoctor[/MENTION]. You have been there helping many a lost soul, yourself. Always good to see you helping ppl out as well. Nothing but respect too. [emoji41] We're all here for help

Gratefully sent from my Rooted JollyRoger_B13

---------- Post added at 06:24 PM ---------- Previous post was at 06:21 PM ----------

What do you mean by "no gain"? Real question [emoji1]

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] SuperR.:
Back to the original question, I don't think the kitchen will break roms that are in f2fs format, but it currently will not create them in f2fs format. If you extract a rom that is already in f2fs, it should work fine. Building the rom after modification should still work fine. Sparse dat and system.img creation are only ext4 at the moment. I guess those would be the only limitations.