yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] diabl0w:
yeah i should have phrased it better as will f2fs be preserved after creating the image. im still learning a lot and im having trouble with creating a rom based on samsung's note 10.1 2014. i was under the impression that samsungs stock firmware supported both f2fs and ext4 but im starting to think its only ext4. is there a way to confirm which it is somewhere in /proc/?
[SuperR Kitchen] hohassan444:
thanks [MENTION=718594]super[/MENTION]R for effort...however i noticed that the latest updates (v0.9.5.1 and later) break rom building for me ;

sparse_dat ...gives empty rom.zip

set_metadata...gives this error ;

Preparing updater-script ...

cat: /home/h/Desktop/ALL-COOKING/Kitchen/SuperRs_Kitchen_v0.9.5.6/superr_45/00_project_files/set_metadata_original: No such file or directory.

N.B.......version...v0.9.4.6...works fine for me.

thanks in advance.
[SuperR Kitchen] enotar:
Speed
[SuperR Kitchen] SuperR.:
The "mount" command will give you what you need from adb shell or terminal emulator.

Try this one. If it does not work, please send me a link to the rom.zip you are starting with.

edit: Are you on 32-bit Linux? If so, you will not be able to use sparse_dat. The rimg2sdat binary is 64-bit and there is no source to build from unfortunately.

v0.9.5.7

Changes:

Fixed error trying to read set_metadata_original when it does not exist.

Fixed symlinks including a [ to not have a \ in front of them.
[SuperR Kitchen] bcrichster:
My GOD man!! [emoji33] Do you ever sleep?! Lmfao. [emoji56] Phenomenal work, U Da Mann!!

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] diabl0w:
okay, yeah. it only told me ext4. only possible problem i see here is if it is only telling me how it is currently mounted in ext4 and not all of its possible file system types. ill have to do some more research to see if i can at least get the kernel to support f2fs so that i can mount /data and /cache this way
[SuperR Kitchen] sebastiandg7:
This is what I call an INSANE DEV!!! You are THE DEV! :highfive::highfive:
[SuperR Kitchen] kenzukie:
Please provide for windows too

-regards
[SuperR Kitchen] shoey63:
Just like that eh?

That would entail endless hours of coding and batch scripting. I think you had better learn to install Linux onto your machine.
[SuperR Kitchen] not-i:
Lol
[SuperR Kitchen] asc1977:
Hi

Can anybody please explain me for what is the folder csc_contents in roms. Theres a file inside enforceskipping.....

Sorry but i am new in rom building and here are the most devs for cooking inside

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] hohassan444:
thanks again...i am on ubuntu 15 64 bit....works fine now.
[SuperR Kitchen] bcrichster:
No. [emoji49] Read and reread. SuperR has repeatedly stated he doesn't use Windows or support it in any way, shape or form. Either use a virtual machine or install a Linux. Those are your two choices for this kitchen. Take it or leave it. If you have a problem with that, then there's other threads you could look into or code a Windows version urself. Sorry bro. [emoji53] SuperR is one of the most bad@$$ed and helpful Dev/ coders in here. All ur gonna do is upset ppl cuz windows is almost useless for Android development (as "tits on a Bull") and causes a ridiculous amount of extra & unnecessary troubleshooting. If ur bent on Windows only, then use a virtual machine with a Linux .iso. I'd recommend Linux Mint Cinnamon (17+) 64bit, since it's as close to a Windows friendly style as you'll find. SuperR uses Ubuntu (15.?.?) I think.. [emoji41]

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] kenzukie:
?? lol simple answers Yes or no there is no big deal with that. ?
[SuperR Kitchen] :
It really is very easy to run Linux from a virtual box. Try osboxes.org they are all set up ready to install. You can also boot into Linux from a flash drive. If you pick Linux mint or Ubuntu it is also ridiculously easy to install any dependcies you need
[SuperR Kitchen] slackerz_86:
guys, anyone knows how to unpack or extract every single file of stock rom downloaded from sammobile n910g 5.1.1?
[SuperR Kitchen] Androidwizzard:
Nearly everyone knows :p

Nearly everyone can :p

What's the summary? Is it really too difficult to ask Google instead of writing a post here which unveils a total unwillingness to think and search :confused:

This is a helpfull thread which is really hard to read and follow as so many posts have nothing to do with the project.
[SuperR Kitchen] Stephen:
[MENTION=5787964]SuperR.[/MENTION] hey I have just setup a duel boot on my PC between windows 10 and ubuntu. I have started learning how to use your kitchen. I must say I am very, very impressed with it. I noticed a small cosmetic issue with your method of building the updater script. I noticed you want to have blank lines in the script. Your code for this currently is:

ui_print("");

If you want to print a blank line, you would need to change it to:

ui_print(" ");

As I said very minor observation and I am really impressed at how detailed the kitchen is!
[SuperR Kitchen] slackerz_86:
i tried google and stuffs. Firstly, when i try unzipping the tar, it says no end record. after that, the file has system.img.ext4 which i cannot extract or unpack or even take a look at it using any softwares.

*i'm originally a windows user, but using vmware to run xubuntu
[SuperR Kitchen] asc1977:
I asked google but find no helping answer but never mind. I didnt ask anything anymore. Csc contents belonged to build a rom.

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] SuperR.:
This will be changed in the next version. Thanks for pointing it out :)

I tried hitting the thanks button but the 8 thanks limit is in effect (really annoying btw :p)
[SuperR Kitchen] sebastiandg7:
[MENTION=5787964]SuperR.[/MENTION] Im using the last version. In getting updater-binary error when installing a recently builded ROM.

When I try with an other project everything works perfectly, what can I be doing in the first project to have that error?

Edit: Reading about this. Found that the error "blkdiscard failed: Invalid argument" is related with the system partition sizes.... When I build the full ROM zip I choosed 4) System.img for determining the system partition size. Could this be the problem? What option (not usng adb) should I use?

Edit 2: Used option 2) and solved! :good:
[SuperR Kitchen] SuperR.:
You can use the enter manually option as long as you know the exact system partition size in bytes. Frequently a raw system.img is exactly that size, but not always.

edit: glad to hear you got it sorted out :)
[SuperR Kitchen] sebastiandg7:
After installation it reboots to bootloader mode :(
[SuperR Kitchen] hassann98:
Hello

I am using cygwin

In time I encounter the following message

please advice

Thank you

[IMG="7za"]http://www.shiaupload.ir/images/65775163401528270685.png[/IMG]
[SuperR Kitchen] bcrichster:
This kitchen is NOT designed for Cygwin, therefore incompatible. You need either a Virtual Box, live boot disk/USB, or just install a Linux 64bit of your choosing to get proper function. But.. I think ur msg is saying you need 7zip full

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] Er. Aditya:
this is the best kitchen totally amazing and getting better everyday
[SuperR Kitchen] bcrichster:
RIGHT?! We ALL needed this deal! [emoji41]

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] Er. Aditya:
and what makes it even better the kind of support its getting from its awesome dev

hats off my man :good::cowboy:
[SuperR Kitchen] SuperR.:
Thanks :)

I would thank your posts but I reached my limit so this is the best I can do.
[SuperR Kitchen] bcrichster:
No problem & Ty-. Tapatalk app hasn't any limit and not a resource hog if it's worth the effort

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] Er. Aditya:
your work is all we need :)
[SuperR Kitchen] SuperR.:
I had no idea, thanks :)
[SuperR Kitchen] bcrichster:
Just double & triple checked by thanking a lot of ppl in this thread and got up to about 12 thanks before I quit, just doesn't allow to "unthank". I apologize if my thanks offended anyone by not making sense

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] Stephen:
[MENTION=5787964]SuperR.[/MENTION] Hey, on the Nexus 6P we have the separate vendor partition. I want to try and stay clear of using block_image_update to extract the system and vendor partitions. This method works well on the 6P, but the limitation is, you have to do the initial boot with a permissive enabled kernel. I offer users the choice of two kernels using aroma installer. I was able to get aroma to work quite easily with your block_image_update, but for the above mentioned limitation.

My idea was to use your kitchen and extract the system and vendor images into standard folders and use the symblinks and set_metadada tags to sort permissions out. The ROM does boot, but I have issues with the camera, when I try to open it, the camera FC's on me.

I looked at your updater script am I correct in thinking it pulled the symblinks and set_metadada tags from my phone while it was connected via USB. I was wondering would you be able to do this for the vendor partition as well? I think that would sort out the issues I am having.

Edit: I see you have this line in your updater-script for permissions: set_metadata_recursive("/vendor", "uid", 1000, "gid", 1000, "dmode", 0755, "fmode", 0644, "capabilities", 0x0); but this is not enough, I looked at my working vendor folder and some files do have different permissions.

To test and check and make sure the vendor folder was at fault for the camera, I made no changes to the rom, simply flashed the vendor.img via fastboot and checked the camer again. It worked perfectly.

Cheers

Stephen
[SuperR Kitchen] albertmurcia:
Kitchen working for me perfect.

Thanks [MENTION=5787964]SuperR.[/MENTION]

Galaxy tab S t805

5.0.2

Enviado desde mi SM-T805 mediante Tapatalk
[SuperR Kitchen] bcrichster:
[MENTION=5787964]SuperR.[/MENTION] .. Would this be the time to add/implement ur Full Flash image pull script in Extraction menu?

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] fhem:
Two synblinks in the vendor image both for the camera. See linked tree of the vendor image
[SuperR Kitchen] SuperR.:
The symlinks are pulled from the system.img, nandroid.tar, or from an existing rom zip depending on what you are extracting. In this case, symlinks were extracted from your system.img. The kitchen finds all symbolic links in the img, and converts the link into an updater-script entry and deletes the symbolic link. The symbolic links are recreated and deleted again for tasks such as creating a system.img or a sparse dat rom. It should not be difficult to run the vendor.img through the same process. I should have some time to work on it tomorrow late afternoon/evening.

Regarding the set_metadata for vendor, it is a bit tricky. At the moment, there is a database file in the kitchen that has many lines for many files that not every device has or needs. The kitchen runs through that file checking if the files exist in the current project and then add it to the updater-script. Once added, the kitchen runs through the file_contexts file and adds context to the appropriate set_metadata line if it exists. If they do not exist in the file_contexts file, they are considered system_file. With all that said, I am not sure how to handle vendor set_metadata as I do not have a device to test with. If you can provide a "vendor database file" I am happy to add it to the kitchen. Here is the system database file for reference.

edit: The Nexus 9 has these contexts listed in the file_contexts file so we should find out the correct perms for these:

/vendor/bin/gpsd	u:object_r:gpsd_exec:s0
/vendor/bin/touch_fusion	u:object_r:touch_fusion_exec:s0
/vendor/bin/qcks u:object_r:kickstart_exec:s0
/vendor/bin/efsks u:object_r:kickstart_exec:s0
/vendor/bin/ks u:object_r:kickstart_exec:s0
/vendor/bin/qmuxd u:object_r:qmuxd_exec:s0
/vendor/bin/netmgrd u:object_r:netmgrd_exec:s0
/vendor/bin/tlk_daemon u:object_r:tee_exec:s0
[SuperR Kitchen] nelvinchi:
Dam fine work sir, dam fine! :cool:
[SuperR Kitchen] 31fahmi:
do we need to turn off the device when using this tools?
[SuperR Kitchen] bcrichster:
No. On with Root and USB debugging enabled

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] 31fahmi:
sorry if i'm asking such stupid question

i had made a system.img dump, but i don't have enough space on my internal memory

and then i had deleted the system.img file from my internal memory.

is it safe for deleting that file?

sorry it's my first for deodexing my rom
[SuperR Kitchen] Ram121:
[MENTION=5787964]SuperR.[/MENTION] first of all thanks for the tool

I have used the kitchen for Note 4 910G, but the ROM is not booting, I think it is related to kernel changes required

Also in updater script the supersu part comes before kernel flash, I think that should be after kernel flashing

Also in updater script symlink code doesn't appears
[SuperR Kitchen] bcrichster:
Yes, erase file just fine

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] Er. Aditya:
its been a while i am using this kitchen to make roms for 910G and nothing is better then this

absolute 0 problems and yes most i faced are my own stupidness
[SuperR Kitchen] Ram121:
Oh, so might be issue related to my computer, as I am using this kitchen on my laptop with windows 8 and running ubuntu 12.04 in virtual box. Can you suggest anything for this. Thanks
[SuperR Kitchen] Er. Aditya:
first up use any kernel available allready in place of the the boot img edited by kitchen

i am sure it will help
[SuperR Kitchen] bcrichster:
Maybe try a newer Ubuntu..?? v15+

Gratefully sent from my Rooted JollyRoger_B13
[SuperR Kitchen] 31fahmi:
alright

i almost done

what should i choose when i see these question

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

edit:

why i can't flash my deodexed rom on my twrp? i have do a factory reset
[SuperR Kitchen] Stephen:
Not a problem at all. I will have time to work on this, this afternoon for you. Tell me the commands you need me to run on my phone and I get everything you need. I'll push a completely stock factory image and vendor image on my phone first for testing purposes.
[SuperR Kitchen] bigrammy:
You could try this from adb shell

ls -lFR /system/vendor/

This will list all in the Vendor folders/contents and their associated permissions. :good:

I got 1 permission denied flag when I run it without adb shell/su maybe you will get more depending on manufacturer. I tested it on Sony xperia zl 5.1.1 (Rooted) :o

/system/vendor//bin:
lstat '/system/vendor//bin/slim_ap_daemon' failed: Permission denied
/system/vendor//bin/slim_ap_daemon: Permission denied

Just for any noobs reading this after the -

l = is a lowercase L

F = is a Uppercase F

R = is a Uppercase R
[SuperR Kitchen] Stephen:
I can certainly try that. The difference with the Nexus 6P is the Vendor folder is not in /system/vendor but actually located in /vendor that is what is causing the difficulty with the new ROMS!
[SuperR Kitchen] bigrammy:
LS via adb shell should work on the /vendor too unless they locked it down totally or created an file system type that is not readable by LS. Obviously if you have SU you should be able to get everything you need.

So you could just try.

adb shell
su
ls -lFR /vendor/

Skip su if you don't have it :(

PS: LS uppercase is just for clarity I am not shouting :D
[SuperR Kitchen] Stephen:
[MENTION=5787964]SuperR.[/MENTION] Here is a paste bin of the results:

http://pastebin.com/hsUHpXvS
[SuperR Kitchen] bigrammy:
Your welcome :laugh:
[SuperR Kitchen] Stephen:
Now we just need to convert them all into set_metadata tags!
[SuperR Kitchen] SuperR.:
Could you do the following instead so we get uid and gid as well?

ls -nFR /vendor/

Thanks :)
[SuperR Kitchen] fhem:
here you go
[SuperR Kitchen] bigrammy:
-n :good:
[SuperR Kitchen] russel5:
[MENTION=5787964]SuperR.[/MENTION] thanks for your kitchen and hard work.

But i have a little bug with z3c and latest firmware.

First, when unpack boot.img, kitchen allways shows that init.d already activated, but ramdisk is stock and not have this

And last, not install busybox, copy to /system/xbin, but not install (/system/xbin/busybox --install -s not work)

Can you see on this. Thanks again.
[SuperR Kitchen] Er. Aditya:
i just got this error

mv: cannot stat ‘KeyChain.apk-2’: No such file or directory
Zipaligning KeyguardWallpaperUpdator.apk ...
mv: cannot stat ‘KeyguardWallpaperUpdator.apk-2’: No such file or directory
Zipaligning LegacyInCallUI.apk ...
mv: cannot stat ‘LegacyInCallUI.apk-2’: No such file or directory
Zipaligning Maps.apk ...
mv: cannot stat ‘Maps.apk-2’: No such file or directory
Zipaligning mcRegistry.apk ...
mv: cannot stat ‘mcRegistry.apk-2’: No such file or directory
Zipaligning MDMApp.apk ...
mv: cannot stat ‘MDMApp.apk-2’: No such file or directory
Zipaligning MediaConverter_Trim.apk ...
mv: cannot stat ‘MediaConverter_Trim.apk-2’: No such file or directory
Zipaligning minimode-res.apk ...
mv: cannot stat ‘minimode-res.apk-2’: No such file or directory
Zipaligning MirrorLink.apk ...
mv: cannot stat ‘MirrorLink.apk-2’: No such file or directory
Zipaligning MobilePrintSvc_Samsung.apk ...

while making complete rom zip
[SuperR Kitchen] SuperR.:
Can one or both of you toss these lines in your updater script to make sure they work properly before I make all the changes to the kitchen? Thanks :)

symlink("/vendor/lib64/libimscamera_jni.so", "/vendor/app/ims/lib/arm64/libimscamera_jni.so");
symlink("/vendor/lib64/libimsmedia_jni.so", "/vendor/app/ims/lib/arm64/libimsmedia_jni.so");
set_metadata_recursive("/vendor", "uid", 0, "gid", 2000, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata_recursive("/vendor/bin", "uid", 0, "gid", 2000, "dmode", 0755, "fmode", 0755, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata("/vendor/bin/gpsd", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:gpsd_exec:s0");
set_metadata("/vendor/bin/touch_fusion", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:touch_fusion_exec:s0");
set_metadata("/vendor/bin/qcks", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:kickstart_exec:s0");
set_metadata("/vendor/bin/efsks", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:kickstart_exec:s0");
set_metadata("/vendor/bin/ks", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:kickstart_exec:s0");
set_metadata("/vendor/bin/qmuxd", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:qmuxd_exec:s0");
set_metadata("/vendor/bin/netmgrd", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:netmgrd_exec:s0");
set_metadata("/vendor/bin/tlk_daemon", "uid", 0, "gid", 2000, "mode", 0755, "capabilities", 0x0, "selabel", "u:object_r:tee_exec:s0");

edit: Add them after vendor is extracted but before vendor is unmounted and it should be good.

edit2: You may also need to do it after the rom is built by opening the zip and editing the updater-script. Sorry about this part but I am not certain the kitchen won't remove them until I make the changes.
[SuperR Kitchen] Er. Aditya:
What Kitchen version?

0.9.5.7

What Linux are you running?

linux mint 17

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

note 4 910G

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

system.img

What Android version?

5.1.1

What perm method (set_perm, set_metadata, sparse_dat)?

set_metadata

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

mv: cannot stat ‘KeyChain.apk-2’: No such file or directory
Zipaligning KeyguardWallpaperUpdator.apk ...
mv: cannot stat ‘KeyguardWallpaperUpdator.apk-2’: No such file or directory
Zipaligning LegacyInCallUI.apk ...
mv: cannot stat ‘LegacyInCallUI.apk-2’: No such file or directory
Zipaligning Maps.apk ...
mv: cannot stat ‘Maps.apk-2’: No such file or directory
Zipaligning mcRegistry.apk ...
mv: cannot stat ‘mcRegistry.apk-2’: No such file or directory
Zipaligning MDMApp.apk ...
mv: cannot stat ‘MDMApp.apk-2’: No such file or directory
Zipaligning MediaConverter_Trim.apk ...
mv: cannot stat ‘MediaConverter_Trim.apk-2’: No such file or directory
Zipaligning minimode-res.apk ...
mv: cannot stat ‘minimode-res.apk-2’: No such file or directory
Zipaligning MirrorLink.apk ...
mv: cannot stat ‘MirrorLink.apk-2’: No such file or directory
Zipaligning MobilePrintSvc_Samsung.apk ...

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

dint tried all latest release but everything was fine earlier
[SuperR Kitchen] SuperR.:
Are those the only apps that had errors or is that just a short example of what happened with all the apps?
[SuperR Kitchen] Er. Aditya:
happened to every single one of those bro
[SuperR Kitchen] SuperR.:
Only the ones you listed? Did all the other apps work ok?
[SuperR Kitchen] Er. Aditya:
this error occured for all the apps bro
[SuperR Kitchen] Stephen:
Not a problem. I'll test later this evening after I get home from work!
[SuperR Kitchen] russel5:
[MENTION=5787964]SuperR.[/MENTION] i found a bug why busybox not installed (about this issue -- > http://xdaforums.com/showpost.php?p=63958719&postcount=1183)

This is because you install supersu first and then busybox, but when supersu is installed he's umount /system and /data in the end and busybox not found.

If install busybox first all works perfect.
[SuperR Kitchen] fhem:
"Unspoorted script errors on host end" when I tried flashing. Let's wait for Stephen though --- he may have better luck.
[SuperR Kitchen] SuperR.:
v0.8.9.3

Changes:

Check for system/app and system/priv-app symlinks that need removing after deleting their location

Some cleanup

edit: FYI, if you delete the apps and put them back, the kitchen will add the symlinks back :)
[SuperR Kitchen] SuperR.:
v0.8.9.4

Changes:

Custom zip - Check for system/app and system/priv-app symlinks that need removing

Forgot this one on the last version :o
[SuperR Kitchen] SuperR.:
v0.8.9.5

Changes:

Some metadata additions

Some UI changes

[MENTION=1567974]Q9Nap[/MENTION] - No promises, but this might fix the metadata issue on the Nexus 6.
[SuperR Kitchen] Q9Nap:
Set_metadata functionality is getting better; SIM is detected and radio works!

With a stock build (removing only recovery-from-boot.p), Camera and Play Services crash on first boot.

Camera doesn't work at all, but no issues with Play Services once booted afaict.

The "checking connection" screen in the setup wizard took much longer than normal also fwiw.
[SuperR Kitchen] nghia0423:
Symlinks failed

So I manage to create a flashable zip but I get this error? Does the new update fix this problem?

[IMG="Symlink"]http://postimg.org/image/4umgtltvj/[/IMG]
[SuperR Kitchen] SuperR.:
Try wiping data in twrp, then reboot to recovery from twrp menu, then flash rom again. I have seen this behavior in twrp many times and those steps work most of the time.

edit: I believe it is because twrp does not unmount system and data after wiping properly, so when the flashable tries to mount it is already mounted. I have also seen it work to wipe data, go to mounts and uncheck data and system, then flash the rom and it works fine.
[SuperR Kitchen] SuperR.:
I will look into this more tomorrow. Glad to hear we are on the right path :)
[SuperR Kitchen] reefuge:
device moto G (2nd gen) XT1068 dual sim dual standby

on stock rom just extracted and made to flashable zip (no changes)

the only problem (Ive found so far is)

connecting to wi-fi just does not happen > if I skip past and use sim(s) rom boots fine, camera works etc
[SuperR Kitchen] Jamie_Bowen:
Thanks for the kitchen

Any chance one of you guys can point me toward a general tutorial?

I've had a few tries but cant seem to get going (cant unpack image, cant pull from device either and a few other bits) on several phones (Oneplus One/CM12.1, HTC One X/viperx, and Xperia s/stock rooted)
[SuperR Kitchen] SuperR.:
http://xdaforums.com/showpost.php?p=62845968&postcount=3