yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] blueberry60:
I couldn't install 1.6.9 version only 1.6.6 works and I've been getting some errors while installing below that:

unzip: cannot find or open srk_linux_tools.zip, srk_linux_tools.zip.zip, srk_linux_tools.zip.ZIP
g.zip: st.din: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
mv: 'AIK-Linux' .......
[SuperR Kitchen] SuperR.:
Starting with v1.1.6.7, the kitchen does not include binaries. You need to be connected to the internet at least the first time you run the kitchen after cloning or downloading the zips.
[SuperR Kitchen] blueberry60:
I've tried starting with 1.6.7 but same errors, how can I clone it?
[SuperR Kitchen] SuperR.:
Follow the instructions in the OP :)
[SuperR Kitchen] SuperR.:
It turns out you can already use adb over network with the kitchen. Open the terminal to the kitchen directory, as you normally do when running the kitchen. Instead of running it, run the following command first to connect your device:

tools/linux_tools/adb64 connect 192.168.1.100:5555

After this, the kitchen will use adb over network :)

NOTES:

Replace "adb64" with "adb" if you are running 32-bit Linux.

Replace 192.168.1.100 with your device IP as shown in the adb over network app you linked.

I did not test with the app you linked, only the built-in adb over network on my Nexus 5X. As long as the app does it's job, it should work just fine.

The command to disconnect is

tools/linux_tools/adb64 disconnect 192.168.1.100:5555
[SuperR Kitchen] levanhau03:
bug sign zip

after sign zip , it zip signed is 0 byte

[/url]
[SuperR Kitchen] blueberry60:
[MENTION=5787964]SuperR.[/MENTION]

I've tried both "git clone" method via terminal and downloaded zips, but kitchen couldn't install binaries and gives same errors that were above stated except 1.6.6 version.

Thanks again for your support.
[SuperR Kitchen] SuperR.:
You might be running out of ram.

I have no idea what is going on with your setup. I am not able to reproduce it and it seems to be working for everyone else too. Maybe try Ubuntu4Kitchen?
[SuperR Kitchen] CZ Eddie:
How awesome is that!

Thank you.

The Odroid is on hold till next early next week.

I did try an initial build and some things worked, some things didn't.

I got further than before.

I have to start over from scratch to find out what needs fixing and will do that Tuesday/Wednesday. :)
[SuperR Kitchen] levanhau03:
My ram is 4gb , why ??
[SuperR Kitchen] SuperR.:
4GB is not very much, and it all depends how big the ROM zip is. The signing is done completely in ram, then written to disk all at once. There is nothing I can do about this as I did not write signapk.jar.

You don't have to sign the ROM so there is no need to worry. On the other hand, if you get more ram it will probably sign properly :)
[SuperR Kitchen] bcrichster:
With how fat the Android OS's have gotten, I recommend somewhere between 8-16GB of RAM.. 4GB was ok for stuff like KK, last I remember
[SuperR Kitchen] KingOfMezi:
si
[SuperR Kitchen] cla1966:
use 'debian'

when run <superr> got "The following dependencies are missing: bc

getcap " and don't find solution (try to install don't work !)

somebody can help me, please ???

THX
[SuperR Kitchen] SuperR.:
Try in terminal:

sudo apt-get install libcap2-bin bc

If that does not work, you will need to find the equivalent Debian packages that provide the getcap and bc commands. I only test in 64-bit Ubuntu 16.04.
[SuperR Kitchen] cla1966:
THX for reply !

'bc' could be installed, but 'getcap' wouldn't found - anyhow it is in ./sbin ! tryed also your other tip....but become allways redirected to 'will you install now ?' and i'm too stupid do set the correct path....... :silly::rolleyes:

please could anybody help me ones again ???
[SuperR Kitchen] SuperR.:
If you have getcap installed in ./sbin and "which getcap" does not produce a path, then try adding ./sbin to your PATH.
[SuperR Kitchen] PaulPizz:
Is it just me or does deodexing android O not work. Pixel XL doesn't boot. It seems it's a framework issue..??
[SuperR Kitchen] SuperR.:
I have no idea about deodexing Oreo for Pixel/XL. When I tested on the firmware it does seem to deodex, but that's all I know. You may need to experiment with removing META-INF or leaving it. If there are smali/baksmali errors, you can submit an issue on the smali/baksmali github.
[SuperR Kitchen] fanchcho:
how can i use it in mac
[SuperR Kitchen] SuperR.:
It does not work on Mac currently. It can work on mac if somebody wants to compile all the required binaries, but I don't have a mac :)
[SuperR Kitchen] fanchcho:
when I use it on mac, but it does not work well because missing dependencies. getcap and ldd.
[SuperR Kitchen] SuperR.:
I just realized you were posting in the wrong thread so I moved the conversation to the right place.

This tool is for Linux. If you get it working on a Mac, that's great but I don't support Mac since I don't own one. Good luck :)
[SuperR Kitchen] partcyborg:
The kitchen itself works just fine if you have all the gnu tools installed. I mean it's shell it's the definition of portable.

[MENTION=8595039]fanchcho[/MENTION] check out Homebrew if you aren't already aware, it's Linux oriented gnu/oss package manager for osx that enables you to install almost anything you can generally install on a Linux machine. It will get you either all of the way or really close, but when you hit problems with support on macos they are more like brick walls.

Your best bet is to use parallels (or VMware or whatever) to install Ubuntu and run it there. Parallels has a one click Ubuntu install for the brand new or feignt of heart. I use parallels to run a Windows 7 VM for my Odin flashing :)

---------- Post added at 02:47 AM ---------- Previous post was at 02:21 AM ----------

Ok I give up, I've been trying to figure this out for hours. I have files inside my rom that I added outside of the kitchen and not on the phone (using mounting image and making changes) which worked fine until I needed a new executable (as in shell executable) and much to my dismay I added the files and chmod/chowned them correctly but after being turned into a sparse image they magically went from permissions 700 to 644.

After googling I learned this was likely selinux context and that let me here but after many hours of banging on the context file and as many approaches I can think of the files stay 644 no matter what I do. Rather than giving up and doing it with the rom running on my phone is there something I'm missing? The added files even get selinux contexts according to the rom image but I can't make permissions stick.

In fact, if I edit a executable after building the image it too loses its execute bits! This sounds like some tamper proofing but my phone is in permissive mode and I'm free to set things executable on the device. Any idea what's going on? Thanks in advance.

PS mad props for building something of this size and complexity in shell :). It's been a long time since I've seen something of this size in shell and it's awesome. Having it in bash makes it a lot more manageable than the days of old but it's still got a lot going on. Love it
[SuperR Kitchen] SuperR.:
The reason your permissions change is because you are building a system.img. If you choose sparse_dat or raw_img perm type, or if you just build a system.img, make_ext4fs is used. make_ext4fs sets default AOSP permissions for all files when it builds the system.img. None of the local permissions you set will stick because make_ext4fs will change them in the ext4 file system it creates.

If you want more control over how the permissions are set, you can use set_metadata perm type which sets all the permissions in the updater-script and you can change them to whatever you wish.

Alternatively, the donate kitchen has major advancements regarding system.img creation. It overrides the defaults and uses the permissions and capabilities from the base system.img you extracted. Furthermore, you can change them before you build the image to whatever you want. Did I mention it all works in Windows too? :)
[SuperR Kitchen] partcyborg:
I was wondering if permissions were being managed somewhere else, but I poked around and didn't find them outside of the contexts file you pass to make_ext4fs but that's just selinux it doesn't have posix permissions in it. Where is the source of Truth for each files permissions?

The donate kitchen sounds very interesting and given how much time this crap takes to do by hand likely it's priced way below actual value. I will definitely look into it in a moment.

Although I'm a Linux (wrapped in an osx shell for the purdy hardware) user so your ploys of windows support have no effect :)
[SuperR Kitchen] SuperR.:
The permissions are coded in the make_ext4fs binary.

https://github.com/superr/make_ext4fs/blob/master/core/include/private/android_filesystem_config.h

Feel free to clone the repo, change the permissions, and compile it. You can swap it with the existing make_ext4fs binary, just be sure to rename it to make_ext4fs_32 or make_ext4fs_64 depending on whether you compile a 32 or 64-bit binary.
[SuperR Kitchen] partcyborg:
Ohhhhh now I see. Wow that is .... Non intuitive :). Although I suspected something like that but what threw me off was apparently stuff can be like, grandfathered in with more or different permissions? That explains why touching files resulted in them losing permissions.

I'm guessing from the lack of my system partition following these rules that either they aren't an Android wide thing, or TouchWiz unsurprisingly ignores it?

So basically I can put a magic script somewhere else where it so be +x due to its path. I can figure something out on that note, or I'll keep cheating and doing it from inside the phone lol.

Thanks for the help man it would have taken me a bit more banging of head on this before I broke down and read make_ext4fs so you saved me a ton of headache
[SuperR Kitchen] tdhite:
VirtualBox, load up the Ubuntu image. Works just fine on a Mac. Who actually throws all the necessary prereqs on the main OS anyway? Run all dev ops in a VM. Keep your host / laptop clean.
[SuperR Kitchen] partcyborg:
Install parallels or VMware and run Linux in that.

The parallels I snagged and installed has a built in option for Ubuntu that was dead simple to install
[SuperR Kitchen] shan9656:
How can I run this as root?

I am using Debian
[SuperR Kitchen] SuperR.:
You can't and you shouldn't :)
[SuperR Kitchen] kpirnie:
maybe thats where ive been going wrong ;)
[SuperR Kitchen] partcyborg:
If you don't know how to edit the shell code to remove that check then you probably shouldn't be running much of anything as root.

I suggest looking into a tool called sudo it is a much better way to handle things you need to run as root
[SuperR Kitchen] blueberry60:
[MENTION=5787964]SuperR.[/MENTION]

I think there might be a problem on extractring from framework in system.img directory, framework files,especially jar extensions are very small (eg am.jar =318 B), it was 29,948 B in previous SuperrKitchen builds, the sizes of other jar files are also very small, so rom zip file that created for HTC10 causes hanging boot issue.

View attachment 4295287
[SuperR Kitchen] SuperR.:
The first pic is deodexed framework, the second is odexed. The deodexed jar files contain classes.dex so the files are larger.

The boot hanging is probably unrelated to the jar file size. It could be many things. If you provide more information about what you have modified, what perm type you are using, etc someone may be able to help better. A support zip would also be helpful.
[SuperR Kitchen] haqanguven:
Thank you for adding this nice software and Turkish language :)
[SuperR Kitchen] blueberry60:
I haven't used any modified process, completely stock, only removed bloated apk files ( Google Duo,Hangout, Demo, google videos.. ) after extracting system.img process.

Used set_metadata perm type

Never touched stock boot.img

Deodexed with smali/baksmali method, also framework and jar files ( very strange, it seems that kitchen couldn't make odex jar files into deodexed jar files)

Rooted with SuperSU that is existing in Kitchen

Zipaligned all apk and framework apk files

And finally building zip process.
[SuperR Kitchen] Captain_Throwback:
You need to touch the boot.img, specifically by disabling dm-verity, if you expect the device to boot after modifying system with the kitchen. While including a root zip *should* take care of this, you really should disable it yourself just to make sure.

You should try creating a ROM without deodexing first to determine whether the issue is with the kitchen or the deodexing process.

Did you upload the support zip like [MENTION=5787964]SuperR.[/MENTION] asked for?
[SuperR Kitchen] blueberry60:
I tried boot.img as disabled dm-verity but same result ended with stucking boot issue.

I don't know how to make support.zip but I can share rom zip file with you.

I have been building Stock Deodexed Roms for M9 and HTC10 with SuperRKitchen and sharing them in XDA since March 2016 and I haven't confronted with such a problem until new 2.51.617.21 stock build with September Blueborne Security Patch.

Thanks for your efforts.

https://androidfilehost.com/?fid=817906626617936395
[SuperR Kitchen] :
Did you make the boot.img insecure also? I know being left secure sometimes causes a bootloop on stock roms.
[SuperR Kitchen] blueberry60:
No I make always secure boot.img because I faced boot issue previously, when I researched some boot images in custom roms that have been builded by some HTC developers all of them were secure especially in new high-end HTC devices.
[SuperR Kitchen] SuperR.:
Please try the updater-script linked below. It's probably easier to manually replace it in the existing rom.zip than to build again. Let me know how it goes :)
[SuperR Kitchen] blueberry60:
Sorry to get back to you. It took time to have feedback from my rom tester, same result. Do you know main reason of boot issue? How do I follow a road map to build a proper zip for HTC10?
[SuperR Kitchen] Captain_Throwback:
I'm going to try and build the exact same ROM you did and I'll upload it for you to test. What exactly did you remove from the ROM? Is it only those 4 apps, or were there more? I think on this first try I'll keep all of the apps in there, and if it boots, then we'll know it's something that was removed that's preventing it from booting.

Also, I'm using the donate version of the kitchen, so it's possible that the ROM I'm building is slightly more accurate than what the free version is producing. I haven't downloaded your ROM to diff it, but you can do that if you'd like, once it's complete.
[SuperR Kitchen] Captain_Throwback:
When you deodexed, you didn't remove the META-INF folders, right? That would definitely prevent the ROM from booting.
[SuperR Kitchen] blueberry60:
I never remove META-INF folders, ony removed some system/app files (google duo, google music, hangout, google videos) and demoflopackage from system/priv-app) you can research HTC M9 and HTC10 Development threads in XDA I have builded many stable stock deodexed roms for M9 and HTC10 devices until now, I never have such a problem until now.
[SuperR Kitchen] Captain_Throwback:
My ROM is in the process of uploading now. It'll be here when it's complete. Please let me know if it boots for you. Upload is currently at 40%. The only things I did differently from you (besides using the donate version of the kitchen) is to disable dm-verity, leave all apps intact, and I signed the zip (not sure if you did that or not).
[SuperR Kitchen] blueberry60:
When I display updater-script line numbers it says 548 with SuperRKitchen v1.1.6.9, but the other updater-script that [MENTION=5787964]SuperR.[/MENTION] sent displays 627 lines.
[SuperR Kitchen] Captain_Throwback:
There are some extra (unnecessary) lines in the updater-script produced by the donate kitchen. They are likely for the symlinks, and those won't have any effect on the ROM one way or another. The file upload is complete. Please try the ROM I posted and let me know if it boots.
[SuperR Kitchen] blueberry60:
It might be helpful. I got some errors while deodexing and building process:

View attachment Documents.zip
[SuperR Kitchen] SuperR.:
You are missing a dependency for aapt and zipalign so you are getting errors. This will probably not fix your rom, but it should fix the errors you posted in the zip

sudo apt-get install zlib1g

For the future, the kitchen will create a support.zip for you to upload. Go to Misc Tools > Support, then just attach the zip to your post. It contains all the logs so you should always create the zip after you do all the things you have trouble with. That way I can see all the logs from when the problem happened :)
[SuperR Kitchen] oF2pks:
Great tool, works fine on H2 oneplus5: https://xdaforums.com/showpost.php?p=73627595&postcount=10 , then when deodex-ed & re-zipped, microG can be injected to H2 (7.1.1 Deodexed - smali/baksmali sparse_dat + twrp nanomod).

Maybe [MENTION=5627087]ale5000[/MENTION] has a python script "~ready" to perform microG's injection directly into kitchen's deodex-ed framework.jar (straight to directory's project) ?

https://xdaforums.com/android/development/tingle-fork-needle-t3438764

Also great to confirm it works on i386 latest Backbox (xenial 16.04) with (very) old CentrinoDuo; it's amazing how [SuperR' Kitchen] "could" fit into Backbox/Auditing/MobileAnalysis/Android (attached screenshot).
[SuperR Kitchen] afby:
help

Hi, I would like to make a customized rom for my phone (A3 2017). At the time it was simpler, I arrived very well with the kitchen of dsixda for another phone.

There I do not get it, I have an error message just after the attempt to mount system.img and that's it. There is no log to know the problem !?

I have attached the support zip!

Thank you for your help and for your kitchen
[SuperR Kitchen] SuperR.:
The zip.log shows 7-zip throws an error while extracting A320FLXXS1AQG1_A320FLXEF1AQD1_XEF.zip. Make sure the zip archive is not corrupt. It's also possible you ran out of disk space or ram. Additionally, 64-bit Linux is highly recommended. If dsixda kitchen works for you, feel free to use it :)
[SuperR Kitchen] ViperXvenom8888:
I'm trying to make A LineageOS ROM for my OnePlus 3T. I extracted the ROM, chose set_metadata, Build full ROM Zip. I keep getting error 7 when trying to flash the ROM. (Tried raw_img as well)
[SuperR Kitchen] SuperR.:
Send a recovery.log after flashing and a support.zip
[SuperR Kitchen] ViperXvenom8888:
How can I do it??? I'm using TWRP.

Edit: Had to change the Assert from oneplus3 to OnePlus3 :laugh:

Thanks for the Awesome Tool!!! :D
[SuperR Kitchen] afby:
dsixda works with my old phone not the A3!

I find the problem, it's simg2img, i have bluid the last version and replace simg2img_32 and it's works!! super kitchen ;)
[SuperR Kitchen] Blackball:
[MENTION=5787964]SuperR.[/MENTION]

Any plans for update to Oreo?

With Huawei we have not only a boot image. We have a kernel image (zimage I think) and ramdisk image.

And apk come now with three files (apk, odex and vdex)
[SuperR Kitchen] dkionline:
Share the firmware and he take a look.
[SuperR Kitchen] SuperR.:
Oreo and vdex are already supported. I don't know to deal with zimage and ramdisk separate from boot.img in Huawei roms. If you send a link to a working Huawei rom that incorporates the zimage and ramdisk I will try to add support.
[SuperR Kitchen] Blackball:
You need a original firmware or custom rom?
[SuperR Kitchen] bcrichster:
Whichever one boots properly..
[SuperR Kitchen] Blackball:
[MENTION=5787964]SuperR.[/MENTION]

You got a PM
[SuperR Kitchen] mrpascal:
Hey [MENTION=5787964]SuperR.[/MENTION] Why don't you add small aroma option in your kitchen like assayyed kitchen ?

It will be the best thing , and developers love it !
[SuperR Kitchen] SuperR.:
Aroma option is available along with many other additional features in the donate version :)
[SuperR Kitchen] NTchrist:
Any tips for compiling a pixel 2 xl rom? I'm literally at this point just trying to flash a stock rom (to see what configurations are required for the tool to work before I make any changes)

1. feed it a stock system.img (I have verified it works by flashing boot superrs-kitchen/superr_dumbroot/system.img and booting)

2. perm type (have tried metadata, set_perm, and raw_img) (I have also tried replacing make_ext4fs_64 from a few pages back as a suggested fix to oreo problems)

3. build system.img (partition detection through both project directory and system.img)

4. building both sparse and raw images (interesting note, raw builds a file exactly the same size as the stock img)

however, none of the combinations I tried resulted in a system_new image. I have made no changes at all, just extract and then build. Any ideas what I'm missing?
[SuperR Kitchen] SuperR.:
2. I think you should be using raw_img for Pixel2, along with the make_ext4fs binary you got from a few posts back. I have not looked at Pixel2 firmware but the original Pixel reportedly works in the donate kitchen using raw_img so that would be my best guess.

3. You should not use the project directory option if you can avoid it. The system.img option is your best bet.

4. The raw system.img should be exactly the same size as the original raw system.img

Are you saying you are not able to build system_new.img? Or are you saying after building a rom it does not boot? If you are not able to build a system_new.img you may be missing a dependency. If the rom is not booting, you may need to disable dm-verity. Adding SuperSU to your rom should take care of this for you, or you can use the boot/recovery menu.
[SuperR Kitchen] akky26:
after building rom, while flashing via twrp getting error "Zip file is corrupt"

device:mt6753 coolpad note 3

recovery: twrp 3.0.2-1

any suggestions?
[SuperR Kitchen] SuperR.:
Maybe try building the ROM on a different PC? Sorry, I am not sure about this one.
[SuperR Kitchen] SuperR.:
v1.1.7.0 (Free Bash version)

Changes:

Updated make_ext4fs for Oreo.

make_ext4fs now uses pure AOSP permissions and capabilities.

Added /system/vendor/etc to fstab check locations.

Look for device name in ro.build.description as a last resort.

Updated img2sdat by [MENTION=5132229]xpirt[/MENTION] to version 1.5.

Added link to the Donate version thread in the main menu.
[SuperR Kitchen] NTchrist:
sorry, it does produce a system image, said image does not boot (it just hangs at the boot logo forever) I recently compiled a kernel with verity disabled, however, I have observed that even with verity off and the vendor fstab setting the system mount with verity off, it still has verity on leading me to believe the bootloader is passing it on somehow

---------- Post added at 04:37 AM ---------- Previous post was at 04:36 AM ----------

I'll report back with the new version, thanks :)
[SuperR Kitchen] ddpanku:
getting this error while trying to get partition information

by-name could not be detected.

Try detecting mmc partitions from recovery.img:confused::confused::confused::(:(
[SuperR Kitchen] NYCHitman1:
The kernel passes verity too -- just an FYI.
[SuperR Kitchen] NTchrist:
does not boot on the p2xl, once again it just hangs at the google logo forever. I do get the "your software is corrupt" message too, even with verity off at the kernel, and /vendor/etc/fstab.taimen levels. It's definitely the bootloader passing verity, so I'm going to have to look at the way /vendor/init boots android and see if there's any way I can bypass it.

I think at this point it's probably safe to say your tool works as advertised; sorry to bother you
[SuperR Kitchen] SuperR.:
v1.1.7.1 (Free Bash version)

Changes:

Fixed extraction on devices that have spaces in the device name.

Fixed getting mmc partitions from recovery.img.

Removed a single blank line from the top of all screens.

[MENTION=8692606]ddpanku[/MENTION] - This should fix your issue. Extract system.img, boot.img, and recovery.img from your firmware zip into your project directory. Then use the kitchen to extract system.img. When it asks for partition info, choose to get mmc from recovery.img :)