yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] micr0g:
Hello

I'm trying to build for Samsung s7 edge but everytime WiFi does not work for me,I mean I can't switch it on or off.

I tried the search option but with no success.

Does anyone have a fix for this?

Thanks in advance

I just made a donation can you add me to the gitlab ?

[MENTION=5787964]SuperR.[/MENTION] my donation ID: 6K958804RJ597623S

mail: 8alasa@gmail.com

nick xda / gitlab: micr0g

Purpose:	Donation from micr0g [5426648]
[SuperR Kitchen] _that:
1. Read the linked page

2. Call java with -Xmx and a large enough number

3. ???

4. Profit!!!!
[SuperR Kitchen] Hamidreza2010:
Hi

i used open suse.how can i download this kitchen ?

i dont know the terminal command

thanks
[SuperR Kitchen] ktmom:
Click the link, first result will probably help you.

http://lmgtfy.com/?q=GIT+openSUSE
[SuperR Kitchen] Hamidreza2010:
just onebody tell me the correct terminal command to download/update this kitchen
[SuperR Kitchen] ieatacid:
git clone <url>
[SuperR Kitchen] kaplya:
my donation ID:5CW24721PC683830N

gitlab:MrMen
[SuperR Kitchen] _that:
Have you tried reading the OP?
[SuperR Kitchen] ShinySide:
Kitchen version v1.0.8.8

So this is happening with the updater

ui_print("Formatting system...");
ui_print(" ");
format("ext4", "EMMC", "[COLOR="Red"]/dev/block/platform/msm_sdcc.1/by-name/boot/system"[/COLOR], "0", "/system");
set_progress(0.100000);
mount("ext4", "EMMC", "[COLOR="red"]/dev/block/platform/msm_sdcc.1/by-name/boot/system[/COLOR]", "/system");
set_progress(0.200000);
ui_print("Extracting system...");
ui_print(" ");

package_extract_file("boot.img", "[COLOR="red"]/dev/block/platform/msm_sdcc.1/by-name/boot/boot[/COLOR]");
[SuperR Kitchen] SuperR.:
How did you choose to get by-name? If you got it from the boot.img which is how i always do it, please send your boot.img and build.prop so I can have a look. If you got it from your device using adb, I will need you to run some commands to find the issue.
[SuperR Kitchen] TheLogicalGamer:
Hey [MENTION=718594]super[/MENTION] I just donated.

My gitlab name is the same as xda.

TheLogicalGamer.

Thanks for the great work!
[SuperR Kitchen] KbaB.BroS:
[MENTION=5787964]SuperR.[/MENTION]

Deodexing oat2dex on Xperia Z5 series worked fine on v2.0.9.8 so I can only assume something happened when you modified oat2dex according to your changelog. I've read here it has something to do with the java heap size being too small.
[SuperR Kitchen] FeyoMx:
Hi [MENTION=718594]super[/MENTION] I made ​​the donation(1CH959309S6858903). Thank you very much for the wonderful work. My gitlab name is elfeyo1980
[SuperR Kitchen] SuperR.:
The oat2dex change in 2.0.9.9 only affects N roms so if you are having trouble with M or below in 2.0.9.9 something else is going wrong. The next update will address the heap size issue. Just no time right now to get it finished.

Added, thanks :)
[SuperR Kitchen] SuperR.:
v2.1.0.0 (Donate version)

Changes:

Fixed Samsung csc files with spaces in the name not getting copied to system.

Switched back to oat2dex.jar v0.8.6 for M deodex.

Added cache.img.ext4 and cache.ext4 rename to cache.img before rom extraction.

Updated smali/baksmali to latest commit.

Updated 7z to v16.02.

Determine the largest java heap size for deodexing while keeping 500M for your system.

Improved the way files for extraction are detected in the ROM directory.

v1.0.8.9 (Standard version)

Changes:

Fixed Samsung csc files with spaces in the name not getting copied to system.

Added cache.img.ext4 and cache.ext4 rename to cache.img before rom extraction.

Updated smali/baksmali to latest commit.

Updated 7z to v16.02.

Determine the largest java heap size for deodexing while keeping 500M for your system.

Improved the way files for extraction are detected in the ROM directory.

[MENTION=5410058]KbaB.BroS[/MENTION] - I made a mistake telling you 2.0.9.9 was the same. I accidentally switched M roms to use the newest oat2dex instead of the older one. I have switched it back now. This only occurred on the donate version as you may notice in the changelog above. Sorry for the inconvenience.
[SuperR Kitchen] KbaB.BroS:
Thanks for the new version, everything works again.
[SuperR Kitchen] :
I'm having trouble with the latest version. I'm trying to extract a 6.01 system.img (samsung) but when I try and choose set meta data I get error this rom is not kit kat or beyond
[SuperR Kitchen] SuperR.:
If you link the firmware I will take a look. Alternatively, you could try a fresh git clone and see if the problem disappears.
[SuperR Kitchen] :
It's just a system img and boot.img it's the new s7 dump. It extracted fine before I updated to the latest version today. I'll do a fresh install of the kitchen first
[SuperR Kitchen] SuperR.:
The kitchen looks at build.prop for the line "ro.build.version.sdk=X". If X = 19 or higher it will let you choose set_metadata. If not you will get that error. If that line does not exist in build.prop, you would also get that error as the value of the api variable would be empty. You could check to see what the build.prop says. If it is 19 or higher, I have no idea why you get that error.
[SuperR Kitchen] :
It doesnt get that far it wont even extract the system img, if I set anything other than set permission it just says its not kitkat and beyond and doesnt extract. If I select set permission it still doesnt extract and sends me back to the same menu again. Trying fresh install now

Edit

done fresh install of kitchen and it's the same it just wont extract anything and keeps saying the rom isnt kitkat or beyond and selecting set permission still doesnt extract anything
[SuperR Kitchen] SuperR.:
The problem is the system.img not extracting, not the kitkat and beyond part. The extraction happens before you are asked about perm type. I will add a check to be sure the system.img actually extracts to the next update to avoid the confusion, but that will not help you now. Is there a link to the firmware somewhere so I can check it for you? All the system.img's I have are extracting without issue.
[SuperR Kitchen] :
Yes I will upload it now, it extracted fine before the update which is why I posted
[SuperR Kitchen] thereassaad:
Did u try to converted to system.img.ext4 ? I had same issues with the newer fw & only this way its solved the issue ,,
[SuperR Kitchen] :
Thanks will try it now, just weird it worked fine before the last update. I extracted the exact same system.img
[SuperR Kitchen] SuperR.:
Could you post a link for a how-to on this, or detail the process?

It is strange since I have not changed anything regarding extracting img files for several months. Once you post the link to it I will see how it goes here. At least we will know if it is a problem with your setup or a problem with the kitchen. Sorry, that is about the best I can offer at the moment :)
[SuperR Kitchen] :
You offer the best support of anyone I know on xda so never apologize my friend. It's just battering my head that's all haha
[SuperR Kitchen] thereassaad:
Sure i will & linked to tool that i use it almost all times

I used this tool

https://github.com/KinglyWayne/simg2img_win

I need just to put system.img on this tool folder then run convert.bat then its will take max 2 mins then new converted system.img to system.img.ext4 its will shown on same folder ..
[SuperR Kitchen] SuperR.:
This tool uses simg2img.exe (for windows) to convert sparse img to raw. The kitchen already does this using simg2img (for Linux) so I am not sure why you would need to do it first.

edit: Unless I need to update my sources for simg2img. Certainly possible.
[SuperR Kitchen] thereassaad:
Mate on newer fw for my Samsung Galaxy s6 & s7 & also latest Note5 i had the same issues so i ( we ) need to do this way by converting it to .ext4 by this tool ( yes its for windows ) then i can extracted without issue ,, ..
[SuperR Kitchen] :
This is the system.img I'm trying to extract

https://docs.google.com/uc?id=0B40ItdHKfkyQTE5kS200Wjg0bEk&export=download

I just redownloaded and the same, it maybe something my end I dont know but it extracted fine a couple of days ago, I guess I could have deleted some dependecies by mistake

Edit

I found the error just dont know why

mount: could not find any free loop device

Copying files to system directory ...

cp: cannot stat ‘output/*’: No such file or directory

umount: output/: not mounted

grep: /home/andy/Desktop/superrs-kitchen2/superr_do/system/build.prop: No such file or directory
[SuperR Kitchen] SuperR.:
This is not a kitchen issue. I am not sure what caused it on your machine but the system.img you uploaded extracted without issues here. simg2img worked perfectly as well to convert from sparse to raw.

give these commands a try. Should add a new loop device:

sudo losetup
sudo losetup -f

Let me know how it goes :)
[SuperR Kitchen] Ram121:
[MENTION=5787964]SuperR.[/MENTION] With V2.1.0.0 still problem of deodexing marshmallow firmware is there for Samsung ROM

It doesn't boot after deodexing by oat2dex method , with baksmali method it boots but major of apps are force closing

I have used it for latest firmware of galaxy note 4

Is there any way to get 2.0.9.8 version or a version which is working good.
[SuperR Kitchen] :
Not sure what has happened to my linux machine, I'm running linux mint 17.3

https://www.dropbox.com/s/kz18tm4iqg32rew/Screenshot%20from%202016-07-25%2011%3A41%3A17.png?dl=0

Sorry for all the bother , a simple reboot of my pc fixed the issue. Really wish I'd tried that first
[SuperR Kitchen] SuperR.:
Please link firmware the kitchen won't extract without the use of that tool so I can look into it. Thanks :)

As mentioned several times in this thread, in the FAQ, and soon to be a warning in the kitchen itself, deodexing may or may not work on Samsung ROMS. I have no idea why the kitchen does not do well with deodexing Samsung. I hope someone can help get it working properly at some point but I am at a loss. I seriously doubt v2.0.9.8 was any better but here is a link just in case.

No bother at all. Glad you got it sorted out :)
[SuperR Kitchen] devilmaycry2020:
@SuperR

It's would be good if have an option to zipaligning apk only. Thanks

p/s : why did you remove the option to choose which method to detect partition when set perm type ? See the pic below.

And i dont know why i can't deodex Z5 6.0.1 rom. always bootloop at animation screen.
[SuperR Kitchen] SuperR.:
v2.1.0.1 (Donate version)

Changes:

Added support for deodexing api level 24, Android Nougat.

Added check to be sure build.prop exists after extracting.

Added notice of possible failure before deodexing except when using AutoROM.

v1.0.9.0 (Standard version)

Changes:

Added support for deodexing api level 24, Android Nougat.

Added check to be sure build.prop exists after extracting.

Added notice of possible failure before deodexing.

NOTE: From this point forward I will ignore all posts about deodexing UNLESS you have a solution to your problem. This includes ROM not booting after deodexing, errors while deodexing, and force closes after booting. I do not have enough devices to test on, or the time to make changes and wait for testers. If you absolutely need your ROM deodexed and the kitchen does not do a proper job, use a different tool or tell me how to fix the issues.

Not sure what you mean about zipaligning apk only. The kitchen only zipaligns apks.

I did not remove the option to choose which method to detect by-name. Once you have detected it for a device it stays in the kitchen. You only have to detect each device once until you delete the device files from /kitchen/tools/devices.
[SuperR Kitchen] beefx:
Hey SupeR! How i can generate new updater-script for existing Rom.zip? After extracting existing rom appears folder meta inf with updater script, but i need new one
[SuperR Kitchen] SH1M4BD3:
I don't know even on donate version still canntot pass the bootanimation, even without deodexing, try so many times failed:D feel so stupid
[SuperR Kitchen] shoey63:
Don't feel stupid. I think the kitchen is not picking up the correct block path for /system and /boot on non Nexus devices. eg: on my Xperia Z, the updater script generates "/data/system " instead of "/dev/block/platform/msm_sdcc.1/by-name/system. I have to edit it manually. [MENTION=5787964]SuperR.[/MENTION] Shouldn't this be automated?
[SuperR Kitchen] SuperR.:
Create as many new projects from the main menu as you want and extract into the new project directories. Each project can only have one META-INF directory.

This was brought up and answered here but I never got a response. Yes it should be automatic and I have not seen a firmware that is not so far. Send me a link so I can take a look. If you are using adb method, I won't be able to test. I always use boot.img to get by-name.
[SuperR Kitchen] SH1M4BD3:
[MENTION=718594]super[/MENTION]R iam Hammerhead user, feel sick of custom out there so this why i use the tool, latest error was on latest factory nexus 5 please take a look sir
[SuperR Kitchen] SuperR.:
Please upload the kitchen generated updater-script and your recovery.log after flashing the problem rom and I will take a look.

edit: I downloaded the latest hammerhead and extracted it getting by-name from the boot.img and chose set_metadata perm type. The updater-script looks good to me. I have attached it to compare if you would like.
[SuperR Kitchen] devilmaycry2020:
Hi all

I added "/data/app support" in Rom tool menu then copy all apps to data/app but program didn't deodex these apps. please help. thank you all.

p/s: Are there anyone successful deodex Z5 6.0.1 rom ? i've tried and always got bootloop at animation screen.
[SuperR Kitchen] SuperR.:
The kitchen does not deodex apks in /data, it only deodexes apks in /system and /vendor. You could rename /data to /vendor before deodexing, then rename it back to /data after if you want the kitchen to deodex them. Or you could put the apps in /system/app before deodexing and move them to /data after.
[SuperR Kitchen] SH1M4BD3:
Retrying 1st set , Deodexing(oat2dex) found one error image attached, debloated (some google app removed manually- just removing i don't need), rooted (let su_decide), and sparse_dat set

#again it won't boot
[SuperR Kitchen] shoey63:
See what you can do withThis

Pure stock LP system.ext4 For Sony Xperia Z 10.7.A.0.222 (No official MM for such an old device) plus pure kernel.elf converted to boot.img.

boot.img method used.

I know you are completely over de-odexing issues, but try it, if you have the inclination. It has sqsh file system for odex.app and odex.priv-app.

Edit: Need to get /block path info from fstab.qcom for (old?) Sony devices, not just fstab
[SuperR Kitchen] SH1M4BD3:
Re-clone the kitchen and set it from boot.img as you did
[SuperR Kitchen] SuperR.:
v2.1.0.2 (Donate version)

Changes:

Added support for odex.app.sqsh and odex.priv-app.sqsh.

Fixed framework directory being moved to system/app if there is an odexed apk in framework while deodexing L.

v1.0.9.1 (Standard version)

Changes:

Added support for odex.app.sqsh and odex.priv-app.sqsh.

Fixed framework directory being moved to system/app if there is an odexed apk in framework while deodexing L.

sparse_dat may be causing your issues. Try set_metadata

These are not the type of deodex issues I was referring to. The kitchen was not dealing with odex.app.sqsh or odex.priv-app.sqsh at all. I had not seen these before so there was no support. Support has been added now. Thanks for pointing it out :)

I used your files, got the by-name from the boot.img you sent, and it seems to work fine.

in the device file (C6603):

\/dev\/block\/platform\/msm_sdcc.1\/by-name

in the updater-script:

format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");

I am not sure what is causing your issue with by-name
[SuperR Kitchen] SH1M4BD3:
[MENTION=718594]super[/MENTION]R come nd take alook mine

Recoverylog https://drive.google.com/file/d/0B1Vsltuww3UFbDdOalg3Y2wxWVU/view?usp=docslist_api

Boot https://drive.google.com/file/d/0B1Vsltuww3UFdTVaMklwaklidkU/view?usp=docslist_api
[SuperR Kitchen] SuperR.:
Your recovery.log does not include flashing the rom so it will not help me.

Your boot.img works fine to get by-name.

As I already said, try set_metadata instead of sparse_dat. I bet it solves your issues.
[SuperR Kitchen] Lightn1ng:
[MENTION=5787964]SuperR.[/MENTION] Thanks for the kitchen.

I have a question. I am trying to get a script of my own working and I took 2 lines of code from your kitchen:

# Next 2 lines are from SuperR's kitchen
byname1=$(adb shell "mount | grep by-name | grep system")
byname=$(echo "$byname1" | gawk '{ print $1 }' | rev | cut -d'/' -f2- | rev)

Can I post that? I will credit you properly :)

It's on my Github if you want to look for yourself.
[SuperR Kitchen] SuperR.:
No problem. FYI, the kitchen does what your script is doing. Create a new project and choose extract for new rom. You will be given the option to grab the files from your device and build the rom from there.
[SuperR Kitchen] Lightn1ng:
Thanks. I know the kitchen can do this, I just was bored and wanted to write something :)

also, off topic: do you know which forums I would post said script? thanks :highfive:
[SuperR Kitchen] DelKrm:
When creating deodex firmware has a bug telephony-common.jar. After the firmware have errors message, smarcard. I did deodex the firmware through the Batch ApkTool, folder and replaced framework. No error. Everything is working.

P.S: Sorry for bad english
[SuperR Kitchen] SH1M4BD3:
[MENTION=718594]super[/MENTION]R great asist try it now..hope it boot

#META_DATA failed too
[SuperR Kitchen] shoey63:
[MENTION=5787964]SuperR.[/MENTION] thanks for implementing de-odex of sqsh files. Works perfectly
[SuperR Kitchen] DeadSix17:
Running this on the stock OnePlus3 ROM without using any other tool/option except extracting and then building the zip results in a boot stuck on animation, any advice?

Device: OnePlus 3 | ROM Version: Android 6.0.1

Kitchen: CURRENT: v1.0.9.1

ROM File I started from: OnePlus3Oxygen_16_OTA_007_all_1606062247_8f031965d7db4420.zip

Perm method: set_metadata

I had no errors, and i just extracted then built and signed it.

Link to above ROM file: https://www.androidfilehost.com/?fid=24591020540823765
[SuperR Kitchen] SuperR.:
If you send me the updater-script and the recovery.log that includes flashing the rom I will take a look to see if there is anything obvious. Otherwise I have no clue.

Just extracted your firmware with the kitchen, and the only thing I see wrong with the result is that it does not extract all the partitions. It only extracts system and boot. Maybe you need to flash the included partitions along with the rom or it won't boot. Not really sure as I don't have a 1+3 to test on. Let me know if you come up with anything.
[SuperR Kitchen] bcrichster:
Add mmcblk0 tool to kitchen as plugin?

Sent from CM12.1 *N9515*
[SuperR Kitchen] DeadSix17:
You talking to me, SuperR or SH1M4BD3? I think you made a mistake in the quote, that's why I ask.
[SuperR Kitchen] bcrichster:
[MENTION=5787964]SuperR.[/MENTION] ..it would be awesome to be usable as a plugin or something for the kitchen.

Or you [MENTION=3367279]DeadSix17[/MENTION] , could try his mmcblk0 tool to get the other needed partitions.. And build a ROM zip to try like [MENTION=5787964]SuperR.[/MENTION] said

Sent from CM12.1 *N9515*
[SuperR Kitchen] DeadSix17:
Ah now I get ya, I'll take a look at it, been a while since I've used kitchen's and did anything android dev. related... back in the Droid 2 days...

EDIT: Isnt that feature built in the kitchen anyway? I tried it earlier and it gives me errors, but ill give the separate tool a try and then report back.

EDIT2: ye.. From TWRP:

Extracting mmcblk0 to PC ... remote object '/dev/block/mmcblk0' does not exist

From booted android:

xtracting mmcblk0 to PC ...

remote object '/dev/block/mmcblk0' does not exist

Extracting to /sdcard instead ...

dd: /dev/block/mmcblk0: No such file or directory

Pulling mmcblk0.img from your device ...

remote object '/sdcard/mmcblk0.img' does not exist

So that tool won't work, however I'm trying the internal kitchen function of pulling from booted android now, seems to work so far.

EDIT3: Unable to pull of booted android:

Disconnects my android and proceeds, but encounters probably a unsuccessful pull and thus:

Checking/Converting if system.img is 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 directory ...

cp: cannot stat 'output/*': No such file or directory
[SuperR Kitchen] SuperR.:
You don't need to extract any images from your device. The zip you linked has the system.img boot.img and all the other partitions included. The kitchen only extracts system and boot but the others are in there. I don't know if that is causing the boot issues or not but you can try flashing the stock zip which will update your partitions and then flash your ROM. Many devices will not work correctly with mix and match partitions and rom.
[SuperR Kitchen] DeadSix17:
I tried adding those partitions into the zip, unfortunately with even worse results, its stucked on the actual boot logo, not the animation. (see what i did below in the code block)

I will try flashing the standard rom then my rom next.

Those are the only things being installed that the kitchen doesn't extract, I added them to the zip myself and modified the script to extract them

ui_print("Writing static_nvbk image...");
package_extract_file("RADIO/static_nvbk.bin", "/dev/block/bootdevice/by-name/oem_stanvbk");
ui_print("Patching firmware images...");
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/pmic.elf", "/dev/block/bootdevice/by-name/pmic");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfg");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xbl");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");

package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64bak");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlibbak");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hypbak");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tzbak");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/abootbak");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfgbak");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymasterbak");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xblbak");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpmbak");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("firmware-update/adspso.bin", "/dev/block/bootdevice/by-name/dsp");
package_extract_file("firmware-update/BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");