yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] kc7gr:
'getcap' is missing, but I already installed it...?

Got something odd happening here. I'm trying to get the Kitchen going on Debian 64-bit and I keep getting this error:

MISSING DEPENDENCY:

The following dependencies are missing:

getcap

Would you like to install now? y/n

Here's the weird part: No matter how many times I hit 'y', and it goes through its 'Installing' notice, it just keeps looping back to the same 'MISSING DEPENDENCY' error, always with getcap.

I've long since installed libcap2-bin, of which getcap is most definitely a part, so I can't understand why the Kitchen keeps saying it's not there.

Assistance, please?

Thanks much.
[SuperR Kitchen] JayZeppelin01:
SupeR's Kitchen Free and SupeR's Kitchen 2 error

1) Detect by-name from boot/recovery images (recommended)

and

4) Detect mmcblk partitions from recovery.img

3151 blocks

grep: fstab.mt6735

fstab.emmc.mt6735: No such file or directory

grep: fstab.mt6735

fstab.emmc.mt6735: No such file or directory
[SuperR Kitchen] SuperR.:
There are some logs in 00_project_files/logs, not sure if you will find anything useful. If you send a fast link to your firmware that does not require registration I will take another look. What OS are you running?

I only test on 64-bit Ubuntu 16.04 so I am not sure about Debian. What happens if you type "which getcap" in a terminal? I assume nothing which is why the kitchen does not know about your getcap.

Please send a link to your boot.img and recovery.img so I can take a look
[SuperR Kitchen] kc7gr:
You are absolutely correct! I will research installing getcap on Debian a bit further. If that doesn't work out, hey... It's a VM! I can change over to Ubuntu at the proverbial falling hat.

Thanks much.
[SuperR Kitchen] DragonXz:
New Problem Appeared :(

Thanks Superr Its Was My Fault I Had Problems with ubuntu

Now I Have Some Other Problem That Kitchen Sometimes Fails in Detecting mountpoints even by name

boot or recovery

or detecting mmc blocks by recovery

while browsing unpacked folders

it appears that some folders and files dont have permissions to view it

using Ubuntu4Kitchen and Tested Also On 14.04LTS With Same Error
[SuperR Kitchen] DragonXz:
---------- Post added at 10:44 PM ---------- Previous post was at 10:44 PM ----------

[/COLOR]

Same I Had:( Aslo Tested On MT6592 Wtih Same Error

It Was Working In Older Versions
[SuperR Kitchen] SuperR.:
Since you noticed your problem was the same as another user, I am surprised you did not think my answer would be the same lol. Please send a link to your boot.img and recovery.img so I can take a look
[SuperR Kitchen] levanhau03:
[MENTION=5787964]SuperR.[/MENTION] i used free version , i see not deodex vender fodel ( MIUI )

i think u convert python to exe , no need install python ( for windows )
[SuperR Kitchen] levanhau03:
tool not deodex vender folder ( MIUI ) ? , I just commented for you
[SuperR Kitchen] SuperR.:
The kitchen should be deodexing the vendor folder. If it is not, you can send a fast link to the firmware that does not require registration and I will take a look.
[SuperR Kitchen] levanhau03:
http://bigota.d.miui.com/7.8.31/miui_HMNote4X_7.8.31_1abfa639b1_7.0.zip

vender folder not deodex , can you add in tool ?
[SuperR Kitchen] CZ Eddie:
Thread newb alert.

Will this guide help me build KitKat for a device that has no TWRP/Clockwork recovery of any type?

The KitKat 4.4.4 source for my device is located here:

http://odroid.com/dokuwiki/doku.php?id=en:xu3_building_android

I ask because the guide kind of looks like it's only for Lollipop and newer?

If the answer is "yes" then let me ask one more.

Will it help me build CM11? The entire SuperR subforum only mentions CM11 once, so my search didn't help.
[SuperR Kitchen] SuperR.:
There is no vendor folder, vendor.img, or vendor.new.dat in that ROM. The kitchen can't deodex it if it does not exist. As I said, the kitchen already deodexes vendor but it needs to exist first :)

This tool can create a fastboot flashable system.img that could be used without custom recovery if your device has an unlocked bootloader. This tool is meant for modifying existing firmware/ROMs, and will not help in building CM11 from source.
[SuperR Kitchen] levanhau03:
extract system.new.dat > system/vender ( it is foldel , some app... in this )
[SuperR Kitchen] SuperR.:
I see the problem now. It will be fixed in the next update. Thanks for pointing it out :)
[SuperR Kitchen] levanhau03:
ok thanks sir
[SuperR Kitchen] CZ Eddie:
My device is an Odroid XU3/XU4 which is rooted but no custom recovery is available, nor is physical ADB interface.

I'm running the latest SuperR Kitchen.

[SUGGESTION] Add ability to extract image via "ADB Over Network".

It seems SuperR doesn't like my ROM image and errors when trying to extract it.
[SuperR Kitchen] SuperR.:
I will consider adding adb over network. I need to think about how it would work exactly. You would still need to be rooted to extract your system.img this way fyi.

If you send a fast link to your firmware that does not require registration I will take a look.
[SuperR Kitchen] SuperR.:
v1.1.6.8 (Free Bash version)

Changes:

Added support for plat/nonplat_file_contexts as found in Android Oreo.

Fixed apks not getting deodexed if system/app is in the path name but are not in /system/app.

Look for system/init.rc instead of system/default.prop for Pixel/XL firmware detection.

Pixel/XL updater-script: Added / in front of egl symlinks.
[SuperR Kitchen] CZ Eddie:
Many thanks for considering adding ADB Over Network!

Odroid stock firmware is rooted by default.

It uses Superuser though, not SuperSU.

Here is the link. Quick & easy download! :)

Direct link to install zip/firmware:

http://dn.odroid.com/5422/ODROID-XU...a-5.0-sd_installer-odroidxu4-20170621.img.zip

Link to source code:

http://odroid.com/dokuwiki/doku.php?id=en:xu3_building_android

Link to multiple install types:

http://odroid.com/dokuwiki/doku.php?id=en:xu3_release_android

If it's something you would only add to the donate, that is cool.

I'm likely going to buy it anyways.
[SuperR Kitchen] SuperR.:
The img included is not an ext4 file system, that's why the kitchen can't extract it. You can extract it using 7-zip to get the system.img out of it.

I will push an update tomorrow for both free and donate kitchens that will add at least partial support for your system.img (after it's extracted from the main img). It is a strange one actually. It is a bit like the Pixel/XL, but all the files are in the root directory instead of /system. The reason the kitchen complained about it is because it was treating it like a Pixel but did not find any of the files where it thought they should be.

Additionally, there is no boot.img. Instead there is a kernel, dtb, and ramdisk.img. Unless you point me to a tutorial on how to deal with this, it will remain ignored lol. For now the rom will be built without a boot.img.
[SuperR Kitchen] CZ Eddie:
My research so far on this----

It seems the boot partition does not contain boot.img. Instead it has uImage.

To pull, we would do:

$ dd if=/dev/<path/of/your/card> of=boot.bin bs=512 skip=1216 count=16384

Android file system on ODROID is different than most others. There is no boot.img or ramdisk at all.

Instead, ramdisk.img and system.img are merged into one image.

So you can modify init.rc directly on the partition itself and it will have changes permanently.
[SuperR Kitchen] SuperR.:
Thanks for the info. For now I will continue to ignore the boot.img, and set it up like the Pixel where going to boot/recovery tools will allow you to modify to the ramdisk files in the root partition.

I know I said I would push the update today, and I still hope to do that. I got pretty busy today and it might be tomorrow before I get it finished. I will do my best :)
[SuperR Kitchen] ZawZaw:
Hi...Sir SuperR,

This can support for Android Oreo 8.0.0 system img ( Nexus Devices )

Thank You.
[SuperR Kitchen] SuperR.:
v1.1.6.9 (Free Bash version)

Changes:

Added at least partial support for Pixel/XL Oreo.

Added at least partial support for devices such as Odroid where the root partition contains the system files and ramdisk.

Added mmc file for odroidxu3.

[MENTION=4274380]CZ Eddie[/MENTION] - Let me know how it goes :)

[MENTION=7581611]ZawZaw[/MENTION] - It should, but there has not been much testing on Oreo as far as I know
[SuperR Kitchen] NYCHitman1:
Works fine on Oreo. Only thing is that Google removed set_metadata, so can't use that permission style in O any longer.
[SuperR Kitchen] bcrichster:
Sounds like now would be a perfect time for you other guys (especially those running Oreo), help SuperR nail those sparse_dat perms, considering set_metadata apparently got left behind. You guys are Awesome and any help you can provide will help everyone else and make things easier for you as well in the future. I think this project is worth your input [emoji41]
[SuperR Kitchen] SuperR.:
The only issue with sparse_dat is that it relies on make_ext4fs for the permissions and capabilities. I can't add all device support to make_ext4fs because it will break other devices. It may be that we need a custom version of make_ext4fs for each manufacturer, or even worse for each device. I have not thought of a good way to deal with this so far which is why I have not lol
[SuperR Kitchen] ZawZaw:
Thank You very Sir SuperR for your awesome update.

•••
[SuperR Kitchen] bcrichster:
I'm hoping the list won't need be any bigger than Mfgr.. That'll (hopefully) at least limit a few things needed. [emoji41]
[SuperR Kitchen] Albe96:
How to installl these? :confused:
[SuperR Kitchen] SuperR.:
The free kitchen is not supported in Windows. If you want to run the kitchen in Windows, check out the donate version found here.
[SuperR Kitchen] bcrichster:
Its been an honor, testing this out! This deserves to be stickied!!

I suppose it to work for many devices but are there any already tested for?

Zte Concord 2

Zte Warp4G

Moto E 2015

LG Exceed 2

LG Realm

Still waiting on results from:

MediaTEK VKworld (VS6050S)

MediaTEK VKworld (VK6050s) confirmed working 100%!!
[SuperR Kitchen] jtash01:
SGS4 (CDMA) OH1 extract gets stuck on detecting partition

Hi. I just installed the stock OH1 Lollipop 5.0.1 in my Samsung Galaxy S4. Used ODIN to install supersu 1.4.9beta, and twrp recovery. I verified root using root checker., then enabled USB debug.

I am trying to extract the rooted device using the kitchen, but the kitchen gets stuck in "Detecting partition info ..." after

* daemon started successfully *

Any ideas?

---------- Post added at 04:17 PM ---------- Previous post was at 04:04 PM ----------

Never mind.. I neglected to grant permission from the device to allow access from the computer. It is now extracting.
[SuperR Kitchen] berkantkz:
Would be great idea.

Following.
[SuperR Kitchen] bcrichster:
I do not understand this comment..
[SuperR Kitchen] berkantkz:
I liked this thread. I may need it in future so reserved. :)
[SuperR Kitchen] bcrichster:
OK, ppl.. We need list for a bunch of Carrier specific bloat so we can add to the main debloat script: Example -

* system/priv-app/whatever.apk *

&

* system/libs/whatever.libs *
[SuperR Kitchen] SuperR.:
v0.8.8.6

changes:

Added custom debloat file - /kitchen/tools/root/debloat_custom - where you can add your own apps to be debloated.

Fixed /data/app when the device uses mmcblk for partitions

When using custom debloat, make sure the files are listed in the same way they are listed in the regular bloat file located in the same directory. Otherwise you may get some unexpected results.
[SuperR Kitchen] SuperR.:
v0.8.8.7

changes:

Added ability to zip your mmc devices so they can easily be uploaded and added to the database
[SuperR Kitchen] jtash01:
Can the debloat_custom file use wildcards, or wild cards without the need to explicitly name the folderlocation, examples:

/system/fonts/SamsungGujara*

# delete all files in that folder beginning with SamsungGujara

YahooStocksPhone*.apk

# delete the apk without having to name either /system/priv-app/ or /system/app/

or does each file have to be explicitly listed with it's folder location?

Can one include folders in the debloat_custom, for example:

/system/vendor/pittpatt/

# this deletes the entire folder without having to list each file in that folder
[SuperR Kitchen] rcunningham:
Awesome work!

You have done a great job on this! You always do really good work and this is a awesome example of it. I really like not having to press enter when i make a selection from a menu. I wonder if there might be a way to port this to Windows...
[SuperR Kitchen] SuperR.:
v0.8.8.8

changes:

Added ability to update the kitchen when it was not cloned from the repo

Added bloat_custom to gitignore, and removed from kitchen. It will be generated when entering the debloat menu if it does not exist. This way we avoid overwriting and/or errors when updating.
[SuperR Kitchen] SuperR.:
Wildcards should work, but it would be nice if you tried the feature I included just for you and let us know if it suits your needs ;)
[SuperR Kitchen] rcunningham:
The LG Mobile drivers are only made for Windows. And also MS-DOS is fun to program.
[SuperR Kitchen] Q9Nap:
Nice work [MENTION=456243]SuperR[/MENTION]!

Have been testing it out on Nexus 6 build LYZ28K official fastboot images.

So far, I've noticed that I have to manually unsparse the ext4 system image with simg2img to be able to extract the contents with the kitchen; might want to add simg2img to your tools :)

Also noticed when selecting to zip only app, framework, and priv-app, symlinks and permissions are removed from the updater-script, which will cause issues with symlinked *.so files in app and priv-app.

Auto generation of symlinks, permissions, and metadata in updater-script format is really nice!
[SuperR Kitchen] reefuge:
guys a bit of help!

not used a kitchen since the days of dsixda's kitchen under cygwin (2010-2013) last rom(s) i cooked was htc cha cha (lol) and blade ....

anyway got titan (moto g 2nd gen xt1068) and have just set up a 2nd pc running ubuntu 14..04.3 LTS 64 bit or would i be better off with 15.04?

got the superr kitchen running fine and can load the rom as a boot.img and system.ext4.tar

its 5.0.2 and can extract it and rezip but guess i'm missing something as it wont flash via TWRP as a .zip

updater script error and syslink fail=1

Any pointers?
[SuperR Kitchen] SuperR.:
Thanks for the kind words :)

The kitchen includes simg2img so I am not sure what is going on. It should detect that the img is sparse and if so use simg2img to unsparse it, then mount it. If you send me a link to the img I will have a look to see what is going on.

Regarding the zip for app, priv-app, and framework, it should not mess with symlinks that already exist on the device at all which is why they are not in the zip. I have never seen symlinks to any of the files contained in any of those directories. Can you explain a bit further the problems you are having?
[SuperR Kitchen] reefuge:
boot.img recovery.img and system.ext4.tar LXB22.99-16.3

mega link mirror of above

I will get you the log for the .zip made by superr once i re install 15.04 - its doing the 10+ gb sync at moment so will be tomorrow

theres no rush as the 2nd pc (linux machine) awaiting 4gb more ram and a new wifi card - main pc is a windows 10 so cant do much till other is fully sorted

I do expect it to be idiot error my end..... been a while since i've played with linux so a bit rusty, hence want to use a kitchen before I even attempt to try building from source lol.

thanks for the help and I apologise in advance for any errors i've made in the images

Gary aka reefuge
[SuperR Kitchen] Q9Nap:
Ah, just noticed it does have simg2img; but yeah it doesn't work properly for me for some reason.

I'm using official LYZ28K boot and system image frome here (direct download): https://dl.google.com/dl/android/aosp/shamu-lyz28k-factory-665a20f2.tgz

As you're probably aware, lollipop has individual lib folders inside app and priv-app folders.

Most of these libs are full files, but some are symlinks to lib files contained in /system/lib.

These are the symlinked lib files from LYZ28K:

symlink("/system/lib/libbluetooth_jni.so", "/system/app/Bluetooth/lib/arm/libbluetooth_jni.so");
symlink("/system/lib/libchrome.2214.89.so", "/system/app/Chrome/lib/arm/libchrome.2214.89.so");
symlink("/system/lib/libchromium_android_linker.so", "/system/app/Chrome/lib/arm/libchromium_android_linker.so");
symlink("/system/lib/libcronet.so", "/system/priv-app/Velvet/lib/arm/libcronet.so");
symlink("/system/lib/libdefcontainer_jni.so", "/system/priv-app/DefaultContainerService/lib/arm/libdefcontainer_jni.so");
symlink("/system/lib/libdmengine.so", "/system/priv-app/DMService/lib/arm/libdmengine.so");
symlink("/system/lib/libdmjavaplugin.so", "/system/priv-app/DMService/lib/arm/libdmjavaplugin.so");
symlink("/system/lib/libfacelock_jni.so", "/system/app/FaceLock/lib/arm/libfacelock_jni.so");
symlink("/system/lib/libgoogle_speech_jni.so", "/system/priv-app/Velvet/lib/arm/libgoogle_speech_jni.so");
symlink("/system/lib/libgoogle_speech_micro_jni.so", "/system/priv-app/Velvet/lib/arm/libgoogle_speech_micro_jni.so");
symlink("/system/lib/libjni_latinimegoogle.so", "/system/app/LatinImeGoogle/lib/arm/libjni_latinimegoogle.so");
symlink("/system/lib/libjni_pacprocessor.so", "/system/app/PacProcessor/lib/arm/libjni_pacprocessor.so");
symlink("/system/lib/libnfc_nci_jni.so", "/system/app/NfcNci/lib/arm/libnfc_nci_jni.so");
symlink("/system/lib/libprintspooler_jni.so", "/system/app/PrintSpooler/lib/arm/libprintspooler_jni.so");
symlink("/system/lib/libvariablespeed.so", "/system/priv-app/GoogleDialer/lib/arm/libvariablespeed.so");
symlink("/system/lib/libvcdecoder_jni.so", "/system/priv-app/Velvet/lib/arm/libvcdecoder_jni.so");
symlink("/system/lib/libvorbisencoder.so", "/system/app/GoogleEars/lib/arm/libvorbisencoder.so");
symlink("/system/lib/libwebviewchromium.so", "/system/app/WebViewGoogle/lib/arm/libwebviewchromium.so");

I just did a basic build (extract system image, delete recovery-from-boot.p, full system zip using the set_metadata permissions option).

It boots, but my SIM is not detected.

Btw, I've made flashable fastboot files for the Nexus 6 here: http://xdaforums.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052

I used the sdat2img and rimg2sdat binaries from here: http://xdaforums.com/android/software-hacking/how-to-conver-lollipop-dat-files-to-t2978952

to make sdat format system images.

Just mentioning it in case you want to add this functionality as well...

Makes the updater syntax much easier; no bothering with symlinks or permissions at all :)
[SuperR Kitchen] SuperR.:
Thanks for the info. Just downloaded the files and will have time to check it out tomorrow.

I can add just the app/priv-app lib symlinks to the updater script if they exist for the flashables that contain those directories. This should sort out the symlink issue for you.
[SuperR Kitchen] Q9Nap:
Just did another build with set_perm option and it seems to be working fine...
[SuperR Kitchen] SuperR.:
v0.9.3.1

Changes:

Fixed symlink detection when extracting from a rom zip that has symlink blocks.

Some changes to the kitchen updater.

Fixed vendor not adding needed lines to the updater-script.

Misc bug fxes.
[SuperR Kitchen] SuperR.:
Guess: You are running 32-bit Linux and can't unpack boot.img with this kitchen.

If you are running 64-bit Linux, extract your boot.img, and look for a file called file_contexts. I suppose it is possible to be located somewhere else in your boot.img, but the kitchen currently checks for it in the ramdisk root. If it does not find it, selinux is assumed unsupported.

Let me know if you find it and where it is located.
[SuperR Kitchen] SuperR.:
It depends what version you are on. Not long ago, this kitchen started using Carliv Image Kitchen to pack/unpack boot and recovery images. It only works on 64-bit Linux.

If you can unpack now, make a copy of the file_contexts file and copy it into your 00_project_files directory. Then choose set_metadata from the change perm type menu :)
[SuperR Kitchen] SuperR.:
v0.9.3.2

Changes:

The kitchen updater will now save your bloat_custom file (if it exists) when not using git.

You will now get an error message if you are on 32-bit Linux and try to unpack boot.img. You will also get info on how you can still use the kitchen if you can't unpack img's.
[SuperR Kitchen] morissio:
Hi [MENTION=5787964]SuperR.[/MENTION] only a question for understand. I see that every time that i create a zip file I find a copy of edited files (updater-script, build.prop).

Like this:

[IMG="message"]http://fs5.directupload.net/images/user/151024/be7ndbfk.png[/IMG]

Is it normal?

Thanks, bye!! :good:

M.
[SuperR Kitchen] Er. Aditya:
i just tried to deodex note 5 rom and only GMS CORE and RNB apps dont get deodexed
[SuperR Kitchen] Er. Aditya:
that i also sorted out as well but why dint it deodex ...
[SuperR Kitchen] SuperR.:
No it is not normal and I have no idea why it is happening.

Please send links that do not require registration to the firmware that is causing issues.
[SuperR Kitchen] morissio:
I can upload on Mega the system.img, the firmware is on sammobile that need the registration.
[SuperR Kitchen] Er. Aditya:
here http://live.samsung-updates.com/details/54597/Samsung_SM-N920I/SM-N920I/MM1/N920IDVU2AOJ4.html
[SuperR Kitchen] SuperR.:
This download will take 12 hours and I would like to check the code in the meantime. There are 3 different deodex scripts so I need to know what Android version it is to know which one to check. Thanks
[SuperR Kitchen] morissio:
5.1.1 for me but i think even for Aditya

Bye ;)

Inviato dal mio SM-G925K utilizzando Tapatalk
[SuperR Kitchen] Er. Aditya:
exactly 5.1.1 , thanks mate for putting time into this :)
[SuperR Kitchen] SuperR.:
I will test on the SM-N910C 5.1.1 firmware since I already have it and hope the problem exists so I can track it down faster. If not, I will test the firmware [MENTION=5750672]Er. Aditya[/MENTION] posted tomorrow.
[SuperR Kitchen] Er. Aditya:
i assume it will work on note 4 , i have been deodexing note 4 roms allready with this awesome kitchen
[SuperR Kitchen] SuperR.:
You are correct :) The only error on the Note 4 firmware was Facebook. Guess I will wait another 10 hours for the other firmware lol

edit: If you can upload the 2 untouched app directories that are not deodexing, the untouched framework directory, and build.prop I may be able to see what is going on.
[SuperR Kitchen] Er. Aditya:
oexed framework ??
[SuperR Kitchen] SuperR.:
Yes. Just extract from img and zip the things I mentioned. Make sure they have not been through deodex at all. Thanks
[SuperR Kitchen] Er. Aditya:
great m on it , will take some time to upload :)

not a very fast internet here

---------- Post added at 03:22 AM ---------- Previous post was at 02:42 AM ----------

here you go dev

SuperRs_Kitchen_v0.9.3.2.zip	210.1 MB

https://mega.nz/#!2wx2UBhY!u__zjt2CMyJG1RN8kB8D0n3HFv1_CTexowCxAvnJDkU
[SuperR Kitchen] ZawZaw:
Hi...Sir,

I want to use that permission "set_perm"

This is working for Oreo 8.0.0 System img ( Nexus 5X )?

Thank You.

•••
[SuperR Kitchen] SuperR.:
You probably want to use sparse_dat or raw_img actually. set_perm is very old and does not set any file contexts or capabilities.

The link below is an Oreo updated version of the make_ext4fs binary included in the kitchen. It is pure AOSP (no capabilities or permissions added or changed) so it should work well for Nexus devices on Oreo. I have not gotten around to pushing the source yet. This is for 64-bit Linux only.

make_ext4fs_64_Oreo_test_2.zip

Replace the make_ext4fs_64 binary in /kitchen/tools/linux_tools with the one from the zip, change the name to make_ext4fs_64, and change perm type to either sparse_dat or raw_img. When you build your rom the new binary will be used to create the system.img/system.new.dat. Let us know how it goes :)
[SuperR Kitchen] ZawZaw:
Thanks Sir. :good:
[SuperR Kitchen] Albe96:
How much to pay? :confused:
[SuperR Kitchen] bcrichster:
You can pay as much as you want, the minimum is $10 for the Donate version of the Kitchen tho [emoji41]