yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] bcrichster:
If you're using a laptop, I highly recommend using some kind of airpad (pad with fan in it). As SuperR. said, they can overheat badly.. Same with compiling ROMs - use an airpad or something to cool it down
[SuperR Kitchen] Mr Hassan:
but i,m using in PC
[SuperR Kitchen] bcrichster:
Then you'll need to

1. clean out the air vents and upgrade your cooling capability.

2. Open the side of the tower up (leave it open) and point a small fan at it..
[SuperR Kitchen] Mr Hassan:
brother its not giving anykind of error during making zip, even installation , fully flashed OK, but after that the ussd codes not working.

its the J327P models,

6.0.1 version, before that i used another one kitchen but in those kitchen after flash wifi not working, that,s for i come to linux for this and after flash wifi is OK, but now the ussd not working ,

i attech the update script and where i found other files?
[SuperR Kitchen] SuperR.:
[MENTION=7279408]Mr Hassan[/MENTION] - I moved your posts to the correct thread. Please post here when asking about kitchen1. The other thread is for kitchen3 only. Thanks :)

If your PC is under powered and/or you don't have a proper cooling system, many applications can make your pc heat up. There will not be a free Windows version, and if there was it would make your current PC heat up even more.

You will need to provide more information about your pc OS, android device, chosen perm type, send updater-script, tell me what does not work, show me error messages, send recovery.log....I cant help without any information.

Did you extract cache.img and include it in your rom? I think I have heard other Samsung users say this has something to do with the ussd codes. Make sure the cache.img is in your project directory when you extract the firmware and say yes when it asks if you want to extract cache.img, and when it asks if you want to include cache.img in your rom. If that is not the problem, hopefully another Samsung user can help out.
[SuperR Kitchen] Mr Hassan:
[MENTION=718594]super[/MENTION]R bro now i,m making again zip but giving us 4 kind of options

set_metadata kitkat+

set_perm

sparse dat

raw_img

may i know which one is for 6.0.1? if all so what,s the advantages of this options?.
[SuperR Kitchen] tanish2k09:
Here is the screenshot of the options briefed by the op in FAQ post.

Looks like you didn't even try using the search button. And also probably you didn't read the op's.
[SuperR Kitchen] NYCHitman1:
[MENTION=5787964]SuperR.[/MENTION] Any chance you plan on supporting the extraction of system.new.dat files in the future?
[SuperR Kitchen] SuperR.:
Extracting system.new.dat is already supported if it is in a zip with system.transfer.list and you let the kitchen extract the zip :)
[SuperR Kitchen] DragonXz:
Tried To Extract Official Samsung ROM /N920C

---------- Post added at 06:16 AM ---------- Previous post was at 06:13 AM ----------

Tried To Extract Official Samsung ROM /N920C / Nougat

first i copied the zip to directory (Kitchen Cannot Find Any files t be extracted)

Then i extracted TAR File With Archive Manager As A Try

when i try to extract System.img It Fails

Any Help To Extract Samsung ROM On Linux ?
[SuperR Kitchen] SuperR.:
What directory did you copy the zip into? It should be in a project directory inside the kitchen like this:

/path_to_kitchen/superr_projectname/firmware.zip
[SuperR Kitchen] Captain_Throwback:
Just install the Magisk plugin and put the Magisk zip of your choice in the folder.
[SuperR Kitchen] Captain_Throwback:
In the Donate version ;)
[SuperR Kitchen] Captain_Throwback:
You could always just rename magisk.zip to supersu.zip - did you try that? Personally I recommend the Donate version, though.

EDIT: If you look under "Root problems?" on the first page it tells you how to use a different zip for root.

P.S. I just woke up and apparently didn't read your original post clearly (totally missed the "How"). I don't use the free version of the Kitchen so I'm just guessing at this point, lol
[SuperR Kitchen] Captain_Throwback:
1. It's a ROM kitchen, so you use it to extract and build ROMs

2. Yes.

3. Yes.

4. I don't know.
[SuperR Kitchen] Captain_Throwback:
If you don't have a use for the Kitchen, what was the point of your initial question?

I typically use the Kitchen to extract APKs from stock system images from older devices so I can port those apps to newer devices where they've been removed.

And flashing a ROM to your device doesn't delete any user data. So I keep my data intact by not deleting it, lol.
[SuperR Kitchen] Captain_Throwback:
Well you're the one who said you didn't have a use for it...

Yes, data wiping is optional. If you're flashing a ROM using a similar base as the currently installed version, then there will be no conflict. However of changing Android versions or going from stock to AOSP or vice versa, then incompatible data may be an issue and wiping is recommended.
[SuperR Kitchen] Captain_Throwback:
Not sure what a patched boot image has to do with data compatibility?
[SuperR Kitchen] Captain_Throwback:
Okay. That has nothing to do with the Kitchen, though.
[SuperR Kitchen] baloo30310:
Hi super's there is there busybox 1.27 built-in?
[SuperR Kitchen] nclwz:
del
[SuperR Kitchen] AnonVendetta:
I'm getting the error "There was a problem unpacking your boot.img" when working with 2 different boot images. I am using the donate repo and the Kitchen is up to date. My 2 boot images are from a Resurrection Remix 7.1.1 ROM, and another from a CMRemix 7.1.3 ROM. I have a T-Mobile Note 4. I made sure to supply the respective build.prop with each img, by placing it in the same folder as the img. The Kitchen correctly detects the Android version and ROM name of each. So I know that all files are in the right place. I havent supplied a system image because I dont want to mod that.

The Kitchen doesn't specify what the error is, and boot.log is 0 bytes. So I have no clue here. I am merely trying to make some changes to default.prop and init.rc inside the ramdisk, and I would also like to enable adbd insecure. I have been able to unpack several other Marshmallow and Nougat boot images in the past (different devices), so this is new to me.

I would also like to note that Android Image Kitchen can unpack the boot images just fine, not sure why the Kitchen can't now. At first I thought that maybe the ramdisk might be using some kind of lesser used compression like LZMA (had issues with boot images patchers not being able to mod that before), but it turns out that isn't the case. Both appear to use standard gunzip/gzip. I also checked to be sure that the permissions and ownership of the files are fine, they are 0777, so should be readable by anything on the PC.

I would appreciate some help here, thanks!
[SuperR Kitchen] SuperR.:
It will be soon :)

I am not sure what reply you would like from me. I don't understand the problem.

Since you are posting in this thread, I assume you are running the Bash donate version (v2.x.x.x). If you are, the problem is almost certainly that you need to install git-lfs and clone the kitchen fresh. There are instructions in the OP.

On a side note, I suggest switching to the Python donate version as support for the Bash donate version will end soon :)
[SuperR Kitchen] AnonVendetta:
[MENTION=718594]super[/MENTION]R: Yeah I guess I have the Bash version, I'm booting from a USB stick the custom Ubuntu ISO you posted. I had no idea there was a Python Kitchen. Can I git-clone the Python version from that (instead of the default bash version that seems to be included)? I just want to keep the Kitchen separate from my SSD-installed Windows 10 and Fedora OSes.

But honestly, the images I'm using are packed with plain gzip, I don't see why the Kitchen can't unpack them now, even though I was able to before. I tried with both the free and donate versions. Another tool I've tried (Android Image Kitchen) can unpack them. I'll see if the Python Kitchen yields the same issue.

As a suggestion, you might look into using ImDisk/ImDisk Toolkit or Arsenal Image Mounter for mounting images on Windows. I'd also imagine that something like the Ext2Fsd driver would need to be installed if Windows users want to work with ext4 images. I'm a member of a little known but tightly knitted PC booting methods forum (best way I can describe it) that is especially fond of ImDisk in particular, the guys who created it are regulars there. Forum name ishttp://reboot.pro Just a suggestion.

Thanks again!
[SuperR Kitchen] SuperR.:
If you want to use either of the Bash kitchens, you need to follow the instructions in the OP to install git-lfs and clone the kitchen fresh or many things will not work. This kitchen uses Android Image Kitchen for all boot.img operations, and it will work perfectly if you install git-lfs before cloning.

The Python kitchen runs in Windows and in Linux so use it wherever you like. It already deals with ext4 images :)
[SuperR Kitchen] KaMyKaSii:
Have you tried running Kitchen on Android? The Termux app has python support, I'm curious about this (I don't have the donation version to test myself).

And a request: would it be possible to add a option to odex roms?
[SuperR Kitchen] SuperR.:
Yes, and there is partial support already built-in. Some things already work, some things can work but are completely broken and will crash the kitchen, and other things can't work at all. Java8 is the reason I stopped working on it. Termux does not have a java8 package, and Android's dalvik/ART only supports java7. smali/baksmali require java8. Beyond that, I do not have a binary package set up for Android so many things will not work until that happens. If people want to run the Python kitchen on Android, I can get everything working except java stuff (deodex, sign, and maybe more will have to check).

No option for odexing roms, sorry.
[SuperR Kitchen] nclwz:
thanks
[SuperR Kitchen] AnonVendetta:
[MENTION=5787964]SuperR.[/MENTION]: So I installed git lfs in Ubuntu and recloned the repo from scratch. Both of my boot images decompile/recompile fine now. I guess whatever came included in your custom ISO is really out-of-date.

A few questions though:

1. If I make changes to any of the files in the ramdisk (after unpacking img), like making some changes in a text editor, will those changes make it into the new boot.img when I recompile it with the Kitchen?

2. I was asking earlier if it was possible to use the Python donate Kitchen with the custom Ubuntu ISO from you that I already have. I know it has the Bash version of the Kitchen bundled already. So I can just continue using the ISO, but follow the instructions from the Python thread, it will work? Python works fine in Linux so I don't see why it wouldn't. I just don't want to install Ubuntu on my SSD just for Android stuff, I would rather run it from a large USB 3.0 flash drive, or in a virtual machine. Maybe later I'll look into working with Android stuff on my installed Fedora, but I'm still a Linux newbie. For now it's better to keep this kind of thing isolated.

3. Since you're eventually shutting down the Bash version, will we need to donate again to get access to the Python version? I don't mind donating again, but I'm at a point in life where I'll be strapped for cash for awhile.

Thanks again!
[SuperR Kitchen] SuperR.:
As I said before, I have no idea why your default theme is being replaced. If you send me the updater-script from the rom that works I will try to see the difference.

1. Yes

2. I recently updated the Ubuntu4Kitchen ISO :) If you have been allowing the kitchen to update the desktop launcher after updating the kitchen, you should have the latest version of it. Just rename your existing kitchen directory to something else. If you did not rename it in the beginning, it should be named superrs-kitchen2. Rename it to something like superrs-kitchen-old. Don't just remove the 2 or change it to 3, because the script looks for those too. When you run the script on the desktop, it will ask which you want to install and the Python version should be there. Before you do that though, do this in the terminal:

sudo apt-get install python3-pip

That should be the only package you need for the original Ubuntu4Kitchen to work with the Python kitchen :)

3. I am only shutting down the donate Bash version, not the free Bash version. The Python version is better and I don't want to maintain 3 kitchens lol. You do not need to donate again. All donors have been members of the Python repo since the very beginning :)
[SuperR Kitchen] nclwz:
resolved

thanks
[SuperR Kitchen] JonnyTech:
squashfs

Hello, I am new to SuperR Kitchen

My system.img contains a squashfs file system:

$ file system.img
system.img: Squashfs filesystem, little endian, version 4.0, 1692327377 bytes, 3036 inodes, blocksize: 131072 bytes, created: Thu Jul 27 10:31:44 2017

But kichen cannot use it:

------------------------------------------------------
SuperR's Kitchen
by SuperR
------------------------------------------------------

ERROR:
There was a problem extracting your ROM.

Press ENTER to return to the Main Menu

Is there anything that I can do?

Specifically can I convert it to another format, but especially want to deodex it.
[SuperR Kitchen] SuperR.:
I am sorry, but I still have no idea what I need to fix.

This is a new one for me. I am sure we can unpack your system.img, but I am not sure how to repack a squashfs system.img. I am also not sure how to deal with mounting and flashing to a squashfs file system. If you send a fast link to your firmware that does not require registration I will take a look, but no promises :)
[SuperR Kitchen] SuperR.:
v1.1.6.5 (Free Bash version)

Changes:

Properly handle new java -version output.

Skip app when deodexing if there is an app directory but no apk.

Updated Busybox Installer by [MENTION=4544860]osm0sis[/MENTION] to v1.27.1.

ATTENTION DONORS: Since I did not receive feedback about the Donate Bash version, support for it has now ended. Feel free to keep using it as long as you like, but it may be time to consider switching to the Python version :)
[SuperR Kitchen] MatthiasHGW:
Thank you for this great tool! Without it I would not even attempt to deodex my ROM.

I try to deodex a (rooted) stock Nougat ROM from my Xperia Z5 compact. During the process (when changing the perm type) I received the following message:

You will need to enter the partition info in the updater-script manually.

I have to admit that I have no idea how to obtain the partition info and how to enter it into the script. Accordingly, I managed to build a full ROM zip, but my phone is stuck at boot logo.

Could somebody in this thread explain to me how to find the correct partition info and where to enter it in the script? Do I have to run the script afterwards?

Thank you - Matthias
[SuperR Kitchen] SuperR.:
You should use set_metadata with by-name if possible. Seems you are using the mmc blocks from a recovery.img. If you need to use mmc blocks, you need to find your device file:

/kitchen/tools/devices/devicename/superr_mmc

and edit the file to add your partitions
[SuperR Kitchen] nclwz:
repack boot.img error

log：

Packing ramdisk (as root)...

Using compression: gzip

Getting build information...

kernel = boot.img-zImage

cmdline = console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlyprintk

board =

base = 80000000

pagesize = 2048

kernel_offset = 00008000

ramdisk_offset = 01000000

second_offset = 00f00000

tags_offset = 00000100

hash = sha1

Building image...

Using format: AOSP

Signing new image...

Using signature: AVB boot

Error!
[SuperR Kitchen] SuperR.:
Looks like an Android Image Kitchen issue. If so, it will need to be addressed on the AIK thread found here. If you send your boot.img I can take a closer look.
[SuperR Kitchen] nclwz:
After the error

It will produce an unsigned-new.img，no image-new.img

It is in SuperRs_Kitchen_v1.1.6.5 / tools / boot / AIK

Use Android Image Kitchen (pc) no problem（2.8）

boot View attachment boot.zip
[SuperR Kitchen] SuperR.:
I did not have any trouble with your boot.img. Attached is my boot.log after unpacking/repacking.

You could try cloning the kitchen fresh, and be sure to have git-lfs installed and initialized per the instructions in the OP. I am running 64-bit Ubuntu 16.04 and it is the only Linux I test on.

The 0 in the make_ext4fs command is the value of the -T parameter (timestamp). I am not sure what the difference between -1 and 0 are in this case.
[SuperR Kitchen] nclwz:
thank you

resolved
[SuperR Kitchen] SuperR.:
Try the Linux version of AIK by itself, then report on the AIK thread if you have trouble. You might be missing a dependency or something because it works on this end.

The kitchen has no way of knowing when to use "-T 0" or "-T -1" with make_ext4fs. If you figure out a way for the kitchen to know, please let me know. Glad you sorted out your issue :)
[SuperR Kitchen] nclwz:
resolved
[SuperR Kitchen] SuperR.:
One more test. Can you try using AIK from /kitchen/tools/AIK directly? Add your boot.img to the AIK directory and run it like the standalone version. Technically it is is the standalone version. I think it is not being cloned properly for you for some reason. You could also try downloading the full kitchen as a zip from here. This will eliminate the possible clone issue for you. The only problem is you will not be able to use the kitchen updater if you don't clone.

-T is timestamp, 0 and -1 are the values of -T. I assume 0 and -1 are increments of time, but as I said I do not know what they mean in this case.

Choose sparse_dat perm type if you want to create system.new.dat. There have been mixed results with this method and I recommend set_metadata perm type.
[SuperR Kitchen] say55:
Firmware Sony and Samsung does not work, large images also does not work
[SuperR Kitchen] russel5:
Sony Z3 Compact, official firmware 291 and latest concept firmware works perfect
[SuperR Kitchen] SuperR.:
v1.1.6.6 (Free Bash version)

Changes:

Added fileencryption to the forceencrypt removed list.

Add boot.img to updater-script and ROM.zip when building for Pixel/XL devices.
[SuperR Kitchen] z3r0c00l_2k:
Cannot unpack boot.img..

ERROR:
There was a problem unpacking your boot.img

What Kitchen version?

v1.1.6.6

What environment are you running the kitchen in (OS, 32/64-bit, cygwin, Bash on Windows, etc.)?

64bit Ubuntu 17.04

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

Lenovo P1m

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

rom.zip

What Android version?

7.1.2

What perm method (set_perm, set_metadata, sparse_dat, raw_img)?

set_metadata

What did you do after extracting and before building?

nothing

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

yes

./unpackimg.sh: 1: ./unpackimg.sh: version: not found
./unpackimg.sh: 2: ./unpackimg.sh: oid: not found
size: '7588': No such file
[SuperR Kitchen] SuperR.:
Follow the instructions in the OP to install git-lfs and clone the kitchen fresh. If that does not fix the issue, send a link to the boot.img.
[SuperR Kitchen] smaiarif:
Cannot extract Samsung firmware zip..
[SuperR Kitchen] SuperR.:
Follow the instructions in the OP to install git-lfs and clone the kitchen fresh. If that does not fix the issue, send a fast link that does not require registration to the firmware.
[SuperR Kitchen] smaiarif:
I have used your kitchen before but it was a pure Ubuntu x64 system. And now am running Ubuntu in vmware . . So is this the issue with vmware...
[SuperR Kitchen] SuperR.:
I don't specifically support vmware, but there should not be any issues with the kitchen running in a VM. It is possible you are running out of disk space or ram. Samsung firmware is large, and many parts need to be extracted taking up a lot of resources during firmware extraction.
[SuperR Kitchen] z3r0c00l_2k:
Thanks it worked.....:good::good: :fingers-crossed::fingers-crossed:
[SuperR Kitchen] minhcanh97:
Firmware Samsung Note FE can not extract
[SuperR Kitchen] SuperR.:
Follow the instructions in the OP to install git-lfs and clone the kitchen fresh. If that does not fix the issue, send a fast link to the firmware that does not require registration.
[SuperR Kitchen] Препод:
Ubuntu and Debian based systems

Ubuntu and Debian based systems:

1.

curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | sudo bash

h@h-VirtualBox:~$ curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | sudo bash

[sudo] пароль для h:

Detected operating system as Ubuntu/zesty.

Checking for curl...

Detected curl...

Running apt-get update... done.

Installing apt-transport-https... done.

Installing /etc/apt/sources.list.d/github_git-lfs.list...done.

Importing packagecloud gpg key... done.

Running apt-get update... done.

The repository is setup! You can now install packages.

h@h-VirtualBox:~$

2.

sudo apt-get install git-lfs

h@h-VirtualBox:~$ sudo apt-get install git-lfs

Чтение списков пакетов… Готово

Построение дерева зависимостей

Чтение информации о состоянии… Готово

Уже установлен пакет git-lfs самой новой версии (2.2.1).

обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 0 пакетов не обновлено.

h@h-VirtualBox:~$

3.

git lfs install

h@h-VirtualBox:~$ git lfs install

Error: Failed to call git rev-parse --git-dir --show-toplevel: "fatal: Не найден git репозитоий (или один из его каталогов): .git\n"

Git LFS initialized.

h@h-VirtualBox:~$

What error?

[COLOR=Red][COLOR=Black]git config --global credential.helper cache[/COLOR][/COLOR]

h@h-VirtualBox:~$ git config --global credential.helper cache

h@h-VirtualBox:~$

Nothing happens
[SuperR Kitchen] neonnau:
Donation

Can't send PM,

Made a donation via PayPal, receipt number is: 2117-6655-8632-5199.

Please add me to the Bitbucket, my username is: neonnau

Cheers
[SuperR Kitchen] SuperR.:
I can't fix errors for git-lfs. If you have trouble installing it you can submit an issue in the git-lfs github repo

You can try continuing after the error. If that does not work you can download full kitchen zips here.

Added, thanks :)
[SuperR Kitchen] bamzzz:
Does not support extract MIUI OFFICIAL ROM :(
[SuperR Kitchen] SuperR.:
v1.1.6.7 (Free Bash version)

Changes:

Goodbye git-lfs nightmare, download zips instead.

Updated SuperSU to v2.82-SR3.

Added option to Update all tools in the Misc tools menu.

NOTE: You may need to do a fresh install. There are a lot of files that moved around and I am not sure how the updater will do. I hope I can stop repeating myself about git-lfs now :)
[SuperR Kitchen] stanislavskiy:
Hello. I can't use your tool becausei'm getting this error when unpacking boot image:

grep: fstab.mt6735

fstab.swap: No such file or directory

grep: fstab.mt6735

fstab.swap: No such file or directory

Those file exist. Until June everything was fine until i updated... Now i can't even find old working version.
[SuperR Kitchen] SuperR.:
Do a fresh clone of the kitchen as mentioned in the update post. If that does not fix the issue, send a link to the boot.img you are having trouble with.
[SuperR Kitchen] stanislavskiy:
Boot.img:

dropmefiles.com/lFtzE
[SuperR Kitchen] SuperR.:
I just did a fresh clone of the kitchen, created a new project, and unpacked your boot.img with no issue. Unfortunately since I can't reproduce it I can't fix it. I only test on 64-bit Ubuntu 16.04.
[SuperR Kitchen] stanislavskiy:
Is debug option exist? How can i help you to find the bug?

Another issue.

Syntax error on lines (see below) when i try to get settings via adb:

Which perm type would you like to use?

./superr: строка 6011: [[: 26

22: синтаксическая ошибка в выражении (неверный маркер «22»)

1) set_metadata (KitKat+)

2) set_perm

./superr: строка 6017: [[: 26

22: синтаксическая ошибка в выражении (неверный маркер «22»)

3) Sparse dat (Lollipop+ but not Pixel)

4) raw_img