yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] SuperR.:
I discovered the problem. git-lfs needs to be installed. Do this in terminal and you will be good:

curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | sudo bash
sudo apt-get install git-lfs
git lfs install
git config --global credential.helper cache

Then clone the kitchen again

[MENTION=4395895]BeansTown106[/MENTION]

The older versions reside here :)

https://gitlab.com/superr/superrs-kitchen2-old
[SuperR Kitchen] BeansTown106:
awesome thanks :) and yep git-lfs seems to work its now downloading a bunch of tools which it didnt do the initial clone without git-lfs :highfive:

Edit: yep worked perfect succesfully extracted :)
[SuperR Kitchen] fhem:
That fixed things -- as always thanks much for your continued support and hard work.

SuperR's Kitchen FTW !!!!!! :good::good::good:
[SuperR Kitchen] luigimak:
[MENTION=5787964]SuperR.[/MENTION] I have a problem extracting fw with the latest update (2.1.6.6)

Check this error:

This zip does not contain anything the kitchen can extract.

With the previous version worked (2.1.6.5)
[SuperR Kitchen] nkk71:
[MENTION=5787964]SuperR.[/MENTION]

Was just looking at your configure script, shouldn't

if [ $(grep "boot_a" /etc/recovery.fstab 2>/dev/null) != "" ]; then
SLOT="_a"
fi

be with quotes:

if [ [B]"$(grep "boot_a" /etc/recovery.fstab 2>/dev/null)"[/B] != "" ]; then
SLOT="_a"
fi
[SuperR Kitchen] SuperR.:
Try the quoted code in the post directly before yours to install git-lfs, then clone the kitchen again. If you have already installed git-lfs, fresh cloned, and are still having issues let me know. The OP has been updated with new install instructions as well if you are not running Debian based Linux.

In this case the quotes are not needed
[SuperR Kitchen] nkk71:
Interesting, any particular reason they're not needed here? Just curious :o
[SuperR Kitchen] SuperR.:
Because we are not setting a variable and we don't care what the result of the command is. We only care if the test equals something or nothing.
[SuperR Kitchen] calebcabob:
This is the first time I've ever used a "kitchen"...Just amazing. Feeling grateful for such a kickass community and the extremely hard work that's shared. A BIG thanks to [MENTION=5787964]SuperR.[/MENTION]! This was recommended by another brilliant dev:)
[SuperR Kitchen] rezzo:
Awesome tool! Thx dev!
[SuperR Kitchen] SuperR.:
v2.1.6.7 (Donate version)

Changes:

Added support for sec_omc.zip files in newer cache.img like gs8.

Fixed cache.img not being extracted from tar.md5 when not contained in a zip.

Updated Android Image Kitchen by [MENTION=4544860]osm0sis[/MENTION] to v2.8.

v1.1.5.7 (Standard version)

Changes:

Added support for sec_omc.zip files in newer cache.img like gs8.

Fixed cache.img not being extracted from tar.md5 when not contained in a zip.

Updated Android Image Kitchen by [MENTION=4544860]osm0sis[/MENTION] to v2.8.
[SuperR Kitchen] boostermbkking:
I have some problem in this latest donate version, when I try to extract system.img of g935f, I have this error:

Preparing to extract ...

Checking/Converting if sparse ...

Mounting system.img ...
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.

Copying files to system ...
cp: impossibile eseguire stat di 'output/*': File o directory non esistente
umount: output/: not mounted

ERROR:
There was a problem extracting your ROM.

how to fix it?

I already try with this:

curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | sudo bash
sudo apt-get install git-lfs
git lfs install
git config --global credential.helper cache

but not work!!!
[SuperR Kitchen] SuperR.:
If you send a link to the firmware I can take a look.
[SuperR Kitchen] boostermbkking:
Whit this version of your kitchen it work

superrs-kitchen2-old

but not with the latest...

The firmware is any from sammobile, LINK
[SuperR Kitchen] SuperR.:
The firmware you linked extracted perfectly in v2.1.6.7.

After installing git-lfs, did you do a fresh clone of the kitchen? If not, please try and then extract your firmware again. If so, I have no idea because I can't reproduce the issue.
[SuperR Kitchen] boostermbkking:
yes, after cloning the kitchen again it work, thanks man
[SuperR Kitchen] luigimak:
thanks it works now
[SuperR Kitchen] fays91:
Hello a deodex error with smali / baksmali 2.2.1

ROM MIUI 8

Device: Omega

Android 6.0

ARM64

ERROR: No more files

/home/fayz/GitHub/superrs-kitchen/superr_omega/system/framework/miui.apk

System ERROR:

Erreur inconnue -2147024872

... Deodexing miui

ERROR: No more files

/home/fayz/GitHub/superrs-kitchen/superr_omega/system/framework/miuisystem.apk

System ERROR:

Erreur inconnue -2147024872

... Deodexing miuisystem
[SuperR Kitchen] SuperR.:
I can't do anything about smali/baksmali errors, but what you posted are not smali/baksmali errors. You can look in the deodex.log to see the smali/baksmali errors that caused the errors on your screen. Again though, I can't do anything about the errors you see in the deodex.log. You can submit a ticket at the smali repo, or you can use a different version of smali/baksmali by adding them to /kitchen/tools/smali/current. When you deodex it will ask which ones you want to use.
[SuperR Kitchen] jawee:
Hello,

Is there an option to install ADB in the system because the last rom I created with this kitchen did not allow me to log in (no notification "allow this PC" on my phone)

thanks

Ps : when i deodex the arm and arm64 files are deleted !! But without them the rom does not boot it seems to me !!

And when I replace them the rom is no longer deodex !!

thanks
[SuperR Kitchen] Macguyver1980:
I was not during 1 month using the Kitchen, but there were some updates since. I can't not update the kitchen to use it, and with new version I installed, I've now issue to unzip ROM files I want to use as based and always have this message:

WARNING:

This zip does not contain anything the kitchen

can extract.

Here's link by example of a ROM file page: https://xdaforums.com/oneplus-3/one...nt/rom-phoenix-aospextended-rom-v3-2-t3563765
[SuperR Kitchen] SuperR.:
The kitchen does not have an option to install adb in a device. Your device probably has what it needs already, but here may be permissions missing to enable it.

Yes, the arm/arm64 directories should be deleted after deodexing. Check your deodex.log to see what errors occurred while deodexing because that is most likely the issue. Try another deodex method. smali/baksmali is the most reliable currently for all roms except Lollipop.

You need to install git-lfs and clone the kitchen again. Check the OP for install instructions :)
[SuperR Kitchen] bcrichster:
Wow, man.. Try the spoiler button. [emoji41]
[SuperR Kitchen] SuperR.:
Can you try flashing the attached zip? It will not do anything to your device other than hopefully display the by-name path on the screen. Thanks
[SuperR Kitchen] russel5:
[MENTION=5787964]SuperR.[/MENTION] this zip is work
[SuperR Kitchen] SuperR.:
Would you mind replacing the config/configure.sh script in your project directory with the config/configure.sh in the test zip, build a new rom, and flash?
[SuperR Kitchen] russel5:
Later, I'm on work now.
[SuperR Kitchen] KaMyKaSii:
[MENTION=5787964]SuperR.[/MENTION] can you tell me which command in the updater-script do you use to install a raw system.img to system?
[SuperR Kitchen] SuperR.:
The kitchen uses

package_extract_file("system.img", file_getprop("/tmp/config", "byname") + "/system" + file_getprop("/tmp/config", "slotnum"));

If you are not using the configure.sh, it would be like this but with your device by-name path replacing the red text

package_extract_file("system.img", "[COLOR="Red"]/dev/block/bootdevice/by-name[/COLOR]/system");
[SuperR Kitchen] SuperR.:
v2.1.6.8 (Donate version)

Changes:

Added bc to the list of dependencies the kitchen installs if missing.

Changed some things that should help the kitchen run in Windows 10 Creators Edition WSL (still not supported).

Updated configure.sh to hopefully make it compatible with more devices.

v1.1.5.8 (Standard version)

Changes:

Added bc to the list of dependencies the kitchen installs if missing.

Changed some things that should help the kitchen run in Windows 10 Creators Edition WSL (still not supported).

Updated configure.sh to hopefully make it compatible with more devices.

NOTE: In order to use the new configure.sh, the easiest way is to change perm types to something else, and back to whatever you want to use.
[SuperR Kitchen] russel5:
[MENTION=5787964]SuperR.[/MENTION] still same error on new version...sad
[SuperR Kitchen] SuperR.:
v2.1.6.9 (Donate version)

Changes:

Make configure.sh world readable, writable, and executable.

v1.1.5.9 (Standard version)

Changes:

Make configure.sh world readable, writable, and executable.

The only thing I can think of that is different compared to the test zip I sent is this line in the updater-script:

set_metadata_recursive("/tmp", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);

Try replacing it with the following and try flashing again:

set_metadata("/tmp/configure.sh", "uid", 0, "gid", 0, "mode", 0777);

edit: [MENTION=4688377]russel5[/MENTION] - Update the kitchen, change perm types to something else, then back to whatever you want. Then try again. It includes the edit I mentioned above :)
[SuperR Kitchen] cavemandaveman:
[MENTION=5787964]SuperR.[/MENTION] I'm trying to cook up a custom rom from a stock image for an x86 device. I get issues flashing with doing even only the smallest changes and building (like only debloating). In CWM, it's error 255, not specific at all.

Earlier in this thread you mentioned that for x86 devices, an x86 update-binary is needed. I want to see if this fixes the issue, but idk where to get an x86 update-binary from...and ideas?
[SuperR Kitchen] russel5:
[MENTION=5787964]SuperR.[/MENTION] i don't think that permissions is not right, because this script is run.

All thing in this string

format("ext4", "EMMC", file_getprop("/tmp/config", "byname") + "/system" + file_getprop("/tmp/config", "slotnum"), "0", "/system");

Because after that i had an error

format: make_ext4fs failed (1) on [COLOR="Red"]/systemstdin[/COLOR]: Can't skipFormatting system ...
mount: failed to mount [COLOR="red"]/systemstdin:[/COLOR] Can't skip at /system: Block device required

And i can't flash anything in recovery after that, i need flash all firmware via Flashtool to repair my partitions.
[SuperR Kitchen] SuperR.:
Can you try the attached flashable? Same deal, will only display something on the screen. This one will print exactly what will be used in place of this part:

file_getprop("/tmp/config", "byname") + "/system" + file_getprop("/tmp/config", "slotnum")

By the way, does this work on your device? (replace the red text with your device by-name path)

format("ext4", "EMMC", "[COLOR="Red"]/dev/block/bootdevice/by-name[/COLOR]/system", "0", "/system");

If not, that's the problem. If so and if the below flashable displays the correct path, I am not sure what is going on.
[SuperR Kitchen] russel5:
[MENTION=5787964]SuperR.[/MENTION] i return to stock and can't check your new test script, but when i make my own zip i wrote like this

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

and all works and intalls
[SuperR Kitchen] SuperR.:
So it works when you replace with the actual by-name path. That's good.

Please let me know when you test the configure_2.zip on your device. Thanks
[SuperR Kitchen] Guizão BR:
I've upgraded the superr kitchen to last version today and now when i execute the ./supper i getting sintaxe error, i tried to edit but always get new error, someone can help me?

./superr: linha 1788: erro de sintaxe próximo do `token' não esperado `<<<'
./superr: linha 1788: `<<<<<<< HEAD'
[SuperR Kitchen] SuperR.:
Follow the instructions in the OP to install git-lfs, then clone the kitchen fresh.
[SuperR Kitchen] 2909luboy:
well I report that the new version 1.1.5.9 does not work, since it gives me error when unpacking the boot.img of a mediatek 6735m which in the previous version if it works
[SuperR Kitchen] cavemandaveman:
So it turns out all I needed to do was grab the update-binary from my stock rom and swap the one in the kitchen with it!
[SuperR Kitchen] russel5:
[MENTION=5787964]SuperR.[/MENTION] i found a problem. It was on my side, sorry for that.

I compiled lineage from official source code and TWRP i compiled with lineage source code. But lineage source code not using busybox anymore only toybox, that is the problem...was

Today i used TWRP what i compiled with official omni source code and it have busybox. All works. all installs. Sorry for this "issue" again. Great work and help. Thanks!
[SuperR Kitchen] kosmitchak:
Hi, why when i try to unpack boot.img it's stuck on "checking status"?

Thanks!
[SuperR Kitchen] Weedy0104:
hello I just donated 10 USD. the confirmation code for money transfer is: 8JT05163V2947032S

My username on gitlab.com is: Weedy0104

is you need more information pm me

thank you great project
[SuperR Kitchen] kozyy:
After extracting to create a new rom how can i get what i need to enter manually so i can try the manual option because from phone, recovery img and all others fail?
[SuperR Kitchen] SuperR.:
Please see post #4 for questions I need answers to in order to help you. I don't know what kind of thing you are trying to enter manually, or what manual option you are referring to, or what fails from phone and recovery img.
[SuperR Kitchen] cavemandaveman:
I have a stock rom and an OTA stagefright update (both zips). Is there anyway to combine these two into one flashable rom using the kitchen?

I put both zips in a new project, extracted the rom, then extracted the update. When I extraced the update, the kitchen said it's moving everything to a folder 'old_rom_files' and then extracting, so I'm not sure if it combined my two zips the way I was hoping...
[SuperR Kitchen] SuperR.:
It did not combine the 2 zips the way you were hoping. The stagefright update is likely to be patch files rather than full files. What you could do is flash the rom, then flash the update, then grab a system.img through adb or twrp to work with. This way the update is already patched and they will be "combined".
[SuperR Kitchen] kozyy:
Sorry, though I did read all of the post and search prior to asking. I wanted to try the option to manually enter your (partitions I believe?) what is detected from the recovery/boot img. Directly after you extract firmware for new rom. thought it'd be better to ask that, sorry again. I'll post everything else shortly (:
[SuperR Kitchen] goodman_east:
more time to boot to system after deodex

first of all, thanks for your excellent tools.

I met a problem and ask you for help.

superr kitchen: 1.1.5.5 standard

phone: HTC U Ultra

version: RUU 1.15.***

problem: It took less than 1min to boot to system when the rom is odex made by superr. But it took more than 3 min to boot to system after deodexed.

here is the logcat when deodex rom boots to system.

View attachment deodex.zip

If need test, please make me know. Thank you.
[SuperR Kitchen] SuperR.:
Deodexed roms always take longer to boot on first run. This is normal. Deodexed roms are also slower in general. This is not a kitchen problem.
[SuperR Kitchen] goodman_east:
not the first boot to system, but every bootup.
[SuperR Kitchen] _that:
Why should deodexed ROMs be slower in general? After dexopt has processed an app, there should be no difference.
[SuperR Kitchen] SuperR.:
I don't have evidence so I could be wrong about deodexed roms being generally slower. I have read in many places that deodexed roms are slower by a small amount, and significantly slower on first boot. All of this is not the point I was trying to make in the first place however lol. The issue [MENTION=5064339]goodman_east[/MENTION] is having is not a kitchen issue. It would be the same deodexed manually.
[SuperR Kitchen] goodman_east:
Yes, the issue I met on HTC U ultra didn't appear on HTC U ultra or HTC 10 using the same tools and the same Ubuntu system. I noticed many 'QC-NETMGR-LIB: netmgr_client_send_ping_msg(): netmgr_unix_send_msg failed' errors form logcat files of deodex system, but I don't know why.
[SuperR Kitchen] SuperR.:
If there are smali/baksmali errors in the deodex.log, you can create an issue on smali/baksmali github. I can't do anything about it unless they are fixed there.

If you used oat2dex, try smail/baksmali
[SuperR Kitchen] goodman_east:
The same situation both oat2dex and smali/baksmali.
[SuperR Kitchen] jordan_eliud:
In the donation version I throw this error when doing deodex and throw this error in all the applications by deodex
[SuperR Kitchen] SuperR.:
Try this in terminal, and then try deodexing again:

sudo apt-get install zlib1g
[SuperR Kitchen] jordan_eliud:
I need Help

That library if I have it installed, reinstall it for case but nothing, I still give that error I mention moments ago
[SuperR Kitchen] SuperR.:
Try this one:

sudo apt-get install zlib1g:i386
[SuperR Kitchen] addas4:
Dear SuperR

Can you check my thread https://xdaforums.com/apps/superr-kitchen/tb3-850m-stock-marshmallow-rom-t3623789 as deodexing fails in my TB3-850M device, everything required for troubleshooting is there!

Thanks in advance!
[SuperR Kitchen] Wonders_Never_Cease:
Latest revision will not extract boot images,previous build no issues
[SuperR Kitchen] elliwigy:
Question, does this kitchen support signing boot.img?
[SuperR Kitchen] SuperR.:
This kitchen uses Android Image Kitchen by [MENTION=4544860]osm0sis[/MENTION] for boot.img unpack/pack operations. I am not sure if it signs boot.img. This kitchen does not sign them on its own currently if AIK does not sign them.
[SuperR Kitchen] elliwigy:
thx for the response.. just noticed during install it had the appropriate jars for boot signing but didnt see it as a listed feature.. i suppose could be signed the old fashioned way :)
[SuperR Kitchen] osm0sis:
It's listed in AIK's features. Check the thread. ;)

It will sign if it detects it was AVB signed to begin with. :good:
[SuperR Kitchen] yshalsager:
please help, i'm faceing "getcap" problem in debian 9

how can i install it manually ?
[SuperR Kitchen] SuperR.:
Try this:

sudo apt-get install libcap2-bin
[SuperR Kitchen] Franzferdinan51:
is their a torrent for ubuntu4kitchen?
[SuperR Kitchen] SuperR.:
I have the vendor part completely finished, with one exception. rimg2sdat does not seem to deal with vendor.img. At least I can't figure it out. I used the same command I use for system swapping everything out with vendor and no go. It does not create a vendor.new.dat. I am testing with the Nexus 9 volantis Marshmallow factory images. If you get this figured out let me know the command you use so I can get it fixed in the kitchen. Otherwise, next release will at least have support for vendor.img using set_perm and set_metadata.
[SuperR Kitchen] Er. Aditya:
bro one thing i have rom installed but the carrier based apps still gets installed which are in hidden.img

how can i remove them ??
[SuperR Kitchen] SuperR.:
If you did not extract hidden.img, then they are not installed from a rom you made with the kitchen. If you extracted hidden.img and copied the files, try not doing that lol. My guess is that hidden is a partition and to remove the contents it will need to be formatted on flash.
[SuperR Kitchen] Androidwizzard:
Talking about hidden.img on Samsung devices is always to be skipped when building rom - only one time on special request for carrier specific custom rom I have included. Just system, cache and boot images will do.
[SuperR Kitchen] jesus183095:
I achieved to create a custom rom for my device but the wifi not turn on i try to turn on but automatically is turned off.. you know to fix or resolve this problem.? Anyone?
[SuperR Kitchen] Androidwizzard:
I have been following the progress of this project from the start, highly appreciate the way [MENTION=5787964]SuperR.[/MENTION] improves his work every day, sometimes even every hour.

Now is the time to interfer as things starting to spoil (more flood) the thread and efforts to create a good tool.

That's what it is supposed to be: A TOOL

By no means a cash cow for each and everyone who wants to run "HIS OWN" custom rom without any knowledge, any reading, any learning.

I don't think [MENTION=5787964]SuperR.[/MENTION] deserves such disrespectful treatment by getting demands to fix things not related to the kitchen, "afterkitchen" issues, where noobs are too lazy to search on their own to fix.

OK, finished from my side - now you can hit me in private messages - but that's how I feel about it.

Let [MENTION=5787964]SuperR.[/MENTION] concentrate on real topics of this kitchen.
[SuperR Kitchen] Er. Aditya:
cannot agree more to each word you have said here [MENTION=5787964]SuperR.[/MENTION] has brought us an amazing tool i guess after few days small kids can use it too with ease hats off dev
[SuperR Kitchen] SuperR.:
v0.9.2.9

Changes:

Added support for vendor.img to be extracted and included in rom if it exists in the project directory while extracting.

Initial test for vendor.new.dat when using sparse_dat option.

Fixed zip mmc.

Added support to extract vendor.new.dat if it exists in a sparse dat rom zip.

NOTE: vendor.new.dat is not created using rimg2sdat. Instead it uses img2simg and img2sdat.py by [MENTION=5132229]xpirt[/MENTION]. system.new.dat is still created with rimg2sdat. Not sure which works better, but I could not get rimg2sdat to deal with vendor at all. This is all experimental so keep that in mind and let me know how it goes :)
[SuperR Kitchen] Er. Aditya:
bro i noticed one thing today i never touched hidden and created the rom stll the rom install the apks present inside hidden.img
[SuperR Kitchen] SuperR.:
Not possible, sorry man. My guess again is that "hidden" is a partition on your device. If you don't format a partition when you flash the ROM, the data still exists in that partition on the device.

One thing is certain, the kitchen does not magically create a hidden.img, extract it, and add the contents to your rom ;)
[SuperR Kitchen] tjkhattak61:
SuperR in Boot/Recovery Tools Menu for both option 1 and 2 the Kitchen gives ramdisk deleted message. Check boot_repack and boot_repack_keep as both have same banner.
[SuperR Kitchen] SuperR.:
This has been fixed and will be in the next release. Thanks for pointing it out :)
[SuperR Kitchen] SuperR.:
v0.9.3.0

Changes:

Bug fixes with vendor stuff.

Changed the zip mmc to zip all devices. Since the files are really small we may as well have as many as possible.

Fixed the message when packing boot/recovery and keeping the ramdisk.
[SuperR Kitchen] Q9Nap:
This worked for me:

mhous33@mhous33-VirtualBox:~/android/sdat$ simg2img vendor.img vendor.raw
mhous33@mhous33-VirtualBox:~/android/sdat$ wc -c vendor.raw
260034560 vendor.raw
mhous33@mhous33-VirtualBox:~/android/sdat$ mkdir out
mhous33@mhous33-VirtualBox:~/android/sdat$ sudo mount -t ext4 -o loop vendor.raw out/
[sudo] password for mhous33:
mhous33@mhous33-VirtualBox:~/android/sdat$ sudo chown -R mhous33:mhous33 /home/mhous33/android/sdat/out
mhous33@mhous33-VirtualBox:~/android/sdat$ sudo ./make_ext4fs -T 0 -S file_contexts -l 260034560 -a vendor vendor.img.ext4 out/
Creating filesystem with parameters:
Size: 260034560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7936
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 63485
Block groups: 2
Reserved block group size: 15
Created filesystem with 470/15872 inodes and 47637/63485 blocks
mhous33@mhous33-VirtualBox:~/android/sdat$ ./rimg2sdat vendor.img.ext4
rimg2sdat tool, provided by Howellzhu@gmail.com
Data block: 44699 (178796 KBs)
Zero block: 18786 (75144 KBs)
Total block: 63485 (253940 KBs)
mhous33@mhous33-VirtualBox:~/android/sdat$

Although sdat format works great on L builds, I've pretty much abandoned it on M builds as it requires some funky methods to produce working files.

The ouput names "system.transfer.list" and "system.new.dat" are hard coded into the binary unfortunately.

Just need to rename the output files depending on input image.