yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] rajatgupta1998:
Hi, [MENTION=5787964]SuperR.[/MENTION] , I have been using your kitchen for the past few months and till now my experience has been super great. Thanks :good:

Today I face a new problem when I create a ROM for Moto G4 Plus (Marshmallow firmware) using the TWRP backup of stock MM. VoLTE breaks when I de-odex the ROM using any of the available methods. (oat2dex and smali/baksmali) No modifications made at all. While it works when I keep the ROM odexed. Same result with the factory firmware (fastboot). It works fine for Nougat though. Any help possible? :)

I'm using the latest version of the standard kitchen on Ubuntu-Gnome 16.04.2 LTS 64-bit.
[SuperR Kitchen] SuperR.:
Have you checked the deodex.log? It might show errors if there are any. I can't do anything about the errors, but at least you can see what the problem is and create an issue on smali/baksmali git. Additionally, if you are not using set_metadata I suggest trying it. If you are using sparse_dat or raw_image, the kitchen uses make_ext4fs to build the images and may be missing some permissions or capabilities that are required for VoLTE.
[SuperR Kitchen] jazzespresso:
Hi, i am donated users...have not updated it for quite long time as I have been away...I can't get git clone to update.

do you mind give me download link, so I can just download it and replace it...

thanks!!
[SuperR Kitchen] SuperR.:
Bash Donate version:

https://gitlab.com/superr/superrs-kitchen2/repository/archive.zip?ref=master

Python donate version:

https://gitlab.com/superr/superrs-kitchen3/repository/archive.zip?ref=master

Keep in mind you will not be able to use the kitchen updater if you download the zips instead of git clone.

I also deleted you and added you back to the repos so maybe git clone will work now. Gitlab is a little strange occasionally.
[SuperR Kitchen] jazzespresso:
never able to get Gitlab to make it work!!

ok I am running Ubuntu (Oracle VM Virtual Box on Windows 10), so Bash version? or Python version?
[SuperR Kitchen] SuperR.:
You can run either in Ubuntu, or you can run the Python version in Windows and ditch the VM :) Eventually support will end for the Bash donate version, but there are still some bugs getting worked out in the Python version. Personally, I like the Python version but it's your choice :)
[SuperR Kitchen] gh0st85:
I can't get it to work. Tried adding the ROM zip, pulling from the device and recovery.

My device is rooted (with magisk) and recovery is TWRP.

You can find the ROM here: https://xdaforums.com/devdb/project/dl/?id=23576

The log only has this line: "adb: error: remote object '/sdcard/recovery.img' does not exist"
[SuperR Kitchen] doulc:
First of all I want to thanks you to develop such amazing huge compilation of tool together, a magnificent work. [MENTION=5787964]SuperR.[/MENTION] for samsung device, octa core need to convert sparse to 32bit check this: https://github.com/Chainfire/sgs4ext4fs

Do SuperR's able to pack rom/.img to be flash via (Samsung's Odin) ? Because I have tried few combination for a few times but no luck to even get it flashed.

I have no idea what's wrong with that

1. Perm type I tried: "raw_IMG" and metadata

2. Build Menu I use: "2. Build system.img"

3. 'Choose partition detection method for system' I use: "4) system.img"

Which selection is wrong? Inside the firmware structure:

it could be due to the header [MENTION=5787964]SuperR.[/MENTION] "There are 4 bytes padded to both the file header as well as every chunk header."

Hope you add it to your tool and make update to make it more complete.
[SuperR Kitchen] bcrichster:
I believe making a .tar will do ya right for ODIN
[SuperR Kitchen] SuperR.:
Just downloaded the firmware you linked and it extracted perfectly. What does not work exactly?

If you can tell me how to determine if a device needs it by looking at any of the files that exist in a rom, then I can add it. Keep in mind while you are explaining it that I don't know much about Samsung devices.
[SuperR Kitchen] doulc:
Of course that is what I do but can't get it work. Please tell honestly are you using Samsung device and did it success to flash and boot up? Please help this community, if you really did, share the configuration you used and extra tool/step involved.

[MENTION=5787964]SuperR.[/MENTION] no need all that hustle to check for user, go to build.prop search for word if contain "samsung" then display message inform user -

"Samsung device need header converted to either 28bit or 32bit. If you flash both using Odin, one of them will show error, reboot your device to Odin mode to reflash another one. All Octa core cpu = 32bit. The rest is 28. Select your option: "

"Default = convert to 28bit"

"1. Convert to 32bit"

"2. Create both"

Credits: I happen to see it from russian forum mention Chainfire discovered that.

Changing sparse img header size from 28bit to 32bit (for Samsung Exynos Octa)

sgs4ext4fs --bloat system_new.img system_32bit.img

To make it more awesome and automatic, one thing I can think of is modified the C code. It has checking function available, before unpack the Rom, we check it for user. When repack we add back that same header for that so we don't need display message. C coder do help.

edit: after using sgs4ext4fs it started to allow me to flash, after boot to android the wifi can't scan network anymore
[SuperR Kitchen] ankk98:
[IMG="not starting"]file:///home/ankk98/Pictures/Screenshot%20from%202017-05-13%2015-11-21.png[/IMG]

i have tried installing all dependencies, java, jdk

but still kitchen cannot be started

i am running ubuntu 16.04lts
[SuperR Kitchen] SuperR.:
Your image does not show up for me.

What error is on the screen? If it says you need the binaries, download the appropriate binaries and extract them into your kitchen directory

64-bit_binaries

32-bit_binaries

Try replacing the make_ext4fs binary in the tools directory with the one attached and build your system.img again. I added /system/bin/netcfg and it's permissions. Hopefully it will sort out your wifi issue. I will add sgs4ext4fs to the next update along with this make_ext4fs if it works.
[SuperR Kitchen] doulc:
Unfortunately it still don't work, also I want to mention the cellular data is not working too

https://s4.postimg.org/iyzynssrx/Screenshot_20170514-104903.png it just go like this until it turn off
[SuperR Kitchen] hiep_hv:
Please, give me access to the donate version of the kitchen. I have made the 10$ Donation.

My Gitlab user is hiep_hv. From paypal : vinhtan_mobile@hotmail.com
[SuperR Kitchen] ale8530:
[MENTION=5787964]SuperR.[/MENTION]

On ubuntu 16.04 i have this bug attached not install tools
[SuperR Kitchen] SuperR.:
Do the following in terminal, then run the kitchen again

sudo apt-get install bc
[SuperR Kitchen] doulc:
[MENTION=5787964]SuperR.[/MENTION] Is it because of permission? When repack system.img did the Kitchen restore all permission?
[SuperR Kitchen] SuperR.:
The kitchen does not restore permissions when creating a system.img. That job is left to make_ext4fs as I mentioned before. If you figure out what permissions are missing, I can add them to make_ext4fs binary.
[SuperR Kitchen] doulc:
Hey [MENTION=5787964]SuperR.[/MENTION] I got an idea, I don't know the syntax to write a bash of linux.

Try to write a script for compare each permission of file of the image after mount pack.img and before_pack.img

I see the directory has "file_contexts" which did a good job record all permission, however maybe missing one package (removed one app) or adding one will cause it to mess with permission. Wonder if it handle error by skipping to the next one or would it attempt to set the permission. In App and Priv-app directory the permission structure should be all same.

I found this perl script

#!/usr/bin/perl

use File::Find;

my $directory1 = '/tmp/temp1';
my $directory2 = '/tmp/temp2';

find(\&hashfiles, $directory1);

sub hashfiles {
my $file1 = $File::Find::name;
(my $file2 = $file1) =~ s/^$directory1/$directory2/;

my $mode1 = (stat($file1))[2] ;
my $mode2 = (stat($file2))[2] ;

my $uid1 = (stat($file1))[4] ;
my $uid2 = (stat($file2))[4] ;

print "Permissions for $file1 and $file2 are not the same\n" if ( $mode1 != $mode2 );
print "Ownership for $file1 and $file2 are not the same\n" if ( $uid1 != $uid2 );
}

Oh Crap no wonder some won't work fully, that list is not created base on current editing Rom. It's a list generated by someone mean if you have new package or device manufacturer introduce new name, the device will fail due to permission error

Oh man.. If I was a programmer I would do this

//Generate FIle_Context in small size and base on pattern
For i = 0 to NumberOf(Folder in Root_Directory_of_Rom)
If EachFolderInsideSamePermission then //currently checking folder, check inside app, priv-app, framework etc
If AllFileHasSamePermission = TRUE then //all files type .odex .apk .su etc
WriteToTextFile("Easy;" + Root_Directory_of_Rom(i) + ";" + FilePermission) //Write directory name and File permission
else
dim ext() as Array = getAllExtensionTypeInsideFolder()
For e = 0 to NumberOf(ext)
//Now check if all files within the same extension ( .odex .apk .su etc) has same permission
If AllPermissionCheck(ext(e)) = TRUE then
//moderately easy the “；” is marker for separation
WriteToTextFile("Mod;" + Root_Directory_of_Rom(i) + ";" + Ext(e) + FilePermission) //current extension
end if
Next e++
else
//we got to record whole folder and file structure with name and permission
WriteToTextFile("All;" + Root_Directory_of_Rom(i) + ";" + AllFilePerssion)
end if
Next i++

So during restore just restore permission by pattern or one by one for those don't follow pattern.

We can do it manually example we know app and priv-app always has same permission type (correct me if I'm wrong) then we can skip and only check and record the rest of the folder

Too bad I'm not familiar to linux and it's syntax
[SuperR Kitchen] ale8530:
Very thanks now work :)
[SuperR Kitchen] Mumang:
Problem with wi-fi not connected after repack in system.img not solved and 3 last version kitchen this bug. I'm try repack another kitchen (assayed, Mogu Rom Helper) and problem solved.

Bug in binary or errors code in last release.

I'm testing on image without changes Vivo X6 Plus and Oppo R9S factory rom.

Please check changes version in kitchen and repair error)
[SuperR Kitchen] SuperR.:
What was the last version of this kitchen that worked for you? Can you send a link to your firmware?
[SuperR Kitchen] Mumang:
I'm manually update kitchen - 2.1.5.1 good repacking all img and after flashing wi-fi working, after update last version 3 release any phones not connect wi-fi freezing on ip adress . Samsung G930U repack for flashfire 2.1.5.9, but may be bug flashfire and i'm repack apk on fly.

G930P on 2.1.6.0 and wi-fi not connect. Oppo R9S and Vivo X6Plus on last release repack and wi-fi not work.

May be only Qualcomm platform bug?

I'm try tomorrow MTK 2 phones repacked and reported for all.

Program donate version Linux Mint 18.1.
[SuperR Kitchen] SuperR.:
I don't see any changes from 2.1.5.1 until now that would affect the building of a system.img. make_ext4fs creates the system.img and the source did not change at all.
[SuperR Kitchen] sokkoban:
This issue is present from me only on LM 18.1. So I think this is may be from Cinnamon. Try Ubuntu and you will see problem solved.

My ROM's created on Mint 18.1 all have this issue not working Wi-Fi :o
[SuperR Kitchen] bcrichster:
I've already stated that Mint 18+ is not suitable for building yet. Try Mint 17.3 and just manually install java 8
[SuperR Kitchen] Paulo Narley:
[MENTION=5787964]SuperR.[/MENTION]

Please, give me access to the donate version of the kitchen. I have made the 10$ Donation.

My Gitlab user is paulonarleyfc. From paypal : paulonarleyfc@gmail.com

Thank you.
[SuperR Kitchen] SuperR.:
v2.1.6.3 (Donate Version)

Changes:

Do not use fstab with nodata in the name.

Removed duplicate /system/vendor/firmware set_metadata line.

v1.1.5.3 (Standard Version)

Changes:

Do not use fstab with nodata in the name.

Removed duplicate /system/vendor/firmware set_metadata line.
[SuperR Kitchen] Haltek143:
Hi,

After installed last version 1.1.5.3, i tried to unpack boot.img through menu option "Boot/Recovery Tools", but just after sudo mode, the error message below display :

grep: fstab.samsungexynos8890

fstab.samsungexynos8890.fwup: No such file or folder

After checking, bootimg/ramdisk/fstab.samsungexynos8890.fwup is a present file in my project folder

Thank you
[SuperR Kitchen] SuperR.:
v2.1.6.4 (Donate version)

Changes:

Do not use fstab with .fwup in the name.

v1.1.5.4 (Standard version)

Changes:

Do not use fstab with .fwup in the name.

Should be fixed now
[SuperR Kitchen] Haltek143:
It works, thanks :)
[SuperR Kitchen] Mumang:
All update system and kitchen last version.

Oppo R9S testing - deodexing+repack apk for more language+build system.img ext4 by kitchen.

Small log flashing.

Operation Write Memory [ v1.12 ]

Write selected partitions [1]

[0] Write partition : SYSTEM

Write from : H:\Oppo_R9S\CM2QLM\Repack_Superr_Last\system_new.img

Write partition Ok!

Operation finished!

Wifi working,may be only Samsung and build.prop security string Wifi crashed... Boot samsung dm-verity without SuperSu patching may be too.

Any phone with wifi problem i'm repack and uploading firmware later.

Any screen R9S.
[SuperR Kitchen] enotar:
Sorry for the question but any progress on Bash under Windows 10?

Thank you
[SuperR Kitchen] SuperR.:
Are you reporting a problem with the kitchen or trying to help others with their wifi issues? Sorry, confused

I am not working on the Bash kitchen in Windows any further. The new Python donate version works in Windows and Linux however.
[SuperR Kitchen] Mumang:
Trying to help for others users with wifi problems after repacking.

Small test on other brand for report working repack.
[SuperR Kitchen] Mumang:
And... Solution find for below 5.1.1 android version oat2dex crashed wi-fi connect after deodexing in Vivo BBK phones,SuperR please add change options for deodex with smali/backsmali. Automatically offered oat2dex in kitchen ,it's bug deodex method - not kitchen) Other brand no time for testing,may be 1-3 days try.
[SuperR Kitchen] SuperR.:
smali/baksmali do not support Android 5.x. It is the only Android version not supported. oat2dex is the only option for Lollipop.

see here:

https://github.com/JesusFreke/smali/wiki/DeodexInstructions
[SuperR Kitchen] Mumang:
But deodexing another kitchen(Assayed,Batchapk) not crashed wifi connect,testing in stock rom without changes. May be jar oat2dex version problem? Or donate v2 kitchen version need change to v3?
[SuperR Kitchen] jawee:
Hello,

Is there a particular procedure to follow to create a rom or the choice of options is random?

If possible, give me the chronological steps to follow.

thanks in advance

Galaxy edge 6+

Rom Nougat
[SuperR Kitchen] SuperR.:
You can try v3.x kitchen. Many big problems were fixed in the update today so most things should be good now.

Unfortunately I have no control over how oat2dex deodexes or which versions it supports. You are welcome to try a different version of oat2dex. Just copy it into kitchen/tools/smali/current and it will give you a choice of which to use.

In general:

create new project

copy fimware package into new project directory

extract for new rom

rom tools > build full rom

Beyond that, there are many other options and you will need to decide which ones you want or need for your project :)
[SuperR Kitchen] mrpascal:
Please help me , i have installed it but it still shows me this !!! :(
[SuperR Kitchen] bcrichster:
Have you tried manually installing with using sudo apt-get or pacman?
[SuperR Kitchen] SuperR.:
Download and extract the appropriate binaries for your system

32-bit https://bitbucket.org/superr/superrs-kitchen/downloads/32-bit_binaries.zip

64-bit https://bitbucket.org/superr/superrs-kitchen/downloads/64-bit_binaries.zip
[SuperR Kitchen] Eliminater74:
[MENTION=5787964]SuperR.[/MENTION] I just updated today, and now everytime I go to unpack boot img, I get checking status, then grep: fstab.<device>

then fstab.foto: no such file or directory.. when its there.

and it does this with even roms I knew worked before the update............

So I am lost on this...........

any idea?
[SuperR Kitchen] jawee:
ok thanks
[SuperR Kitchen] SuperR.:
Can you send boot.img and build.prop?
[SuperR Kitchen] Eliminater74:
https://www.androidfilehost.com/?w=files&flid=184781

I uploaded them 2 things there for you.. it was easier for me then to go about any other way.. If you cant get it from there let me know and ill just put it on one of my many clouds......

thanks man...............
[SuperR Kitchen] mrpascal:
Well , I am extracting Android O developer preview (for Nexus 5X & Pixel ) , kitchen shows me can't extract system.img

why this problem occurs ??

help please [MENTION=5787964]SuperR.[/MENTION]

Thanks
[SuperR Kitchen] nicholaschum:
[MENTION=5787964]SuperR.[/MENTION] Donated!

GitLab username: nicholaschum
[SuperR Kitchen] SuperR.:
v2.1.6.5 (Donate version)

Changes:

Updated smali/baksmali to v2.2.1.

Do not use fstab with .fota in the name.

v1.1.5.5 (Standard version)

Changes:

Updated smali/baksmali to v2.2.1.

Do not use fstab with .fota in the name.

[MENTION=5687366]Eliminater74[/MENTION] - This should sort you out :)
[SuperR Kitchen] boswelja:
I have the same issue, was it ever solved?
[SuperR Kitchen] SuperR.:
I am no longer working on the Bash kitchen in Windows. However, The new Python donate version works in Windows and Linux.
[SuperR Kitchen] srgrusso:
Great Stuff :)

Please add me to the donate version.

Gitlab username: sergrusso

Thanks!
[SuperR Kitchen] Haltek143:
[MENTION=5787964]SuperR.[/MENTION]

Hello,

Thanks to add me to the donate version :)

Gitlab username: Haltek
[SuperR Kitchen] SuperR.:
I just cleaned up the gitlab repo for superrs-kitchen2. I am not sure what will happen when you try to update in the future. You might need to do a fresh clone. The reason for this was to enable git lfs so the repo won't keep growing so much every time I update SuperSU, Busybox, smali/baksmali, oat2dex, etc. When I cloned last night it downloaded around 150MB :eek:

I also removed building binaries from source. The kitchen will now download the appropriate binaries if they are missing. I don't think the benefit of building from source outweighs the issues that come from it.

I will be doing the same on superrs-kitchen repo soon as well.

Edit: superrs-kitchen bitbucket repo has now been cleaned up, and no longer builds binaries from source.

Edit2: The following files/directories have been moved to lfs:

tools/7z

tools/7z.so

tools/aapt

tools/adb

tools/adb64

tools/boot/AIK/*

tools/root/busybox/UPDATE-Busybox.Installer.v*-ALL-signed.zip

tools/root/root_zips/SuperSU*.zip

tools/signapk/signapk.jar

tools/smali/*

tools/updater/META-INF-DAT/META-INF/com/google/android/update-binary

tools/updater/META-INF/com/google/android/update-binary

tools/zipalign

The advantage is when I update any of these files in the repo, the repo size will not change. The disadvantage is that we don't get these files when downloading the repo as a zip. I will continue providing full zips here for the standard version. It is still recommended to git clone the repo if possible.
[SuperR Kitchen] travis82:
I am running linux and when I run a fresh clone of the repo it asks if I want to update the 64bit binaries. I say Y, and it downloads a zip sais they are installed than repeats to ask If I want to update 64-bit binaries.

Need any other information?
[SuperR Kitchen] SuperR.:
I am not able to reproduce this issue. I only test on 64-bit Ubuntu 16.04.

You can try manually downloading the appropriate binaries and extracting them in your kitchen directory.

64-bit : https://bitbucket.org/superr/superrs-kitchen/downloads/64-bit_binaries.zip

32-bit : https://bitbucket.org/superr/superrs-kitchen/downloads/34-bit_binaries.zip
[SuperR Kitchen] Hamidreza2010:
[MENTION=5787964]SuperR.[/MENTION] bro i cant see last version of kitchen in http://srk.ddayweb.com

please update that site

thanks
[SuperR Kitchen] SuperR.:
The last version is 1.1.5.5. It is there
[SuperR Kitchen] Hamidreza2010:
No bro
[SuperR Kitchen] toknitup420:
Yes bro. :D
[SuperR Kitchen] jawee:
Hello super,

I cooked a rom (nougat 7.0 for edge s6 +) and when the flash at this level it blocks:

Supersu install:

- mounting / system / data and rootfs

Extracting files

- detecting system compatibility

- system-less mode boot support required

- creating image

After creatiting image, the intallation blocks, (installation animation but no progress)

You would have an idea because I am lost

thanks in advance
[SuperR Kitchen] KingRaheel:
Looks like supersu problem to me. Try replacing with older version of supersu.zip and check or simply delete the lines of root zip from updater script, flash the rom and then flash supersu.zip manually. Hope this solves your problem.

Good luck
[SuperR Kitchen] jawee:
ok thank
[SuperR Kitchen] Hamidreza2010:
:confused: :confused:

its strange

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

Edit:

now problem was fixed :good:
[SuperR Kitchen] jawee:
Hello,

Here is how my concern was solved :

You must include in update-script, this line just before the SuperSu flash command :

run_program("/sbin/busybox", "mount", "-o", "bind", "/dev/urandom", "/dev/random");

thanks again
[SuperR Kitchen] travis82:
Manual extraction of the 64-bit binaries worked.
[SuperR Kitchen] celoxocis:
I just had the exact same issue. Fresh 16.04.02 install fresh repo clone. Keeps saying 64-bit binary's were installed but keeps asking to install them again and endless loop.
[SuperR Kitchen] SuperR.:
v2.1.6.6 (Donate version)

Changes:

Fixed failing to get directory contexts from system.img.

Included binaries in repo to fix install binary loop.

v1.1.5.6 (Standard version)

Changes:

Fixed failing to get directory contexts from system.img.

Included binaries in repo to fix install binary loop.
[SuperR Kitchen] fhem:
I just cloned your latest (2.1.6.6) and it I am getting this error when I try to extract images for project.

ERROR:
There was a problem extracting your ROM.

I have tried fresh clones and diff system images --- nothing seems to help. Never had this issue before --- this is new one to me.
[SuperR Kitchen] Paulo Narley:
[MENTION=5787964]SuperR.[/MENTION] Same mistake here in v2.1.6.6 Donate version bash.
[SuperR Kitchen] SuperR.:
Just did a fresh clone myself and extracted with no issues.

What OS/architecture are you running? The simg2img and make_ext4fs binaries included in the kitchen are compiled for x86 and x86_64. If you are running something else, I can add them. You need to upload from an older version of the kitchen when it was building from source. Grab make_ext4fs and simg2img.

The other thing is if they are not executable they can't do their job. They should be executable though.

These are the only things I can think of that could cause your issues.

By the way: If anyone has issues where it asks you to enter your username and password 100 times when cloning, do this in terminal:

git config --global credential.helper cache

You only have to do it once and it should be fixed after that :)
[SuperR Kitchen] moriel5:
I am running Ubuntu 17.04 x64 (Fully updated), and I can say that I have the same issues. Furthermore, if I manually extract the zip, Superr is unable to extract the kernel from boot.img, preventing it from setting the symlinks.

I have tested this with the 6/5/17 build of LOS14.1 for the Nexus 7 2017 (4G), and with the 6/3/17 build of LOS13 for the Nexus 10 (I simply want to extract a few APKs).

If I may ask (and I mean no offense), what distro (and what architecture is it) are you running?

I have checked thoroughly, and all of the executibles have permission to be run.
[SuperR Kitchen] BeansTown106:
same issue here fresh clone, and newest system and boot image from shamu ERROR: There was a problem extracting your ROM.

even worse u cleaned git history so i cant backtrack to an older version lol :crying: