yashsingh1/xdaforums huggingface dataset:
[SuperR Kitchen] Dragon-snaff:
i want a kitchen for s5 g900h please help

tnx
[SuperR Kitchen] NewBieSS:
------------------------------------------------------
SuperR's Kitchen
by SuperR
------------------------------------------------------

ERROR:
The kitchen should not be run as root

Press ENTER to exit
root@ubuntu:~/superrs-kitchen#

please help. Thanks :)

edit: solved
[SuperR Kitchen] SuperR.:
This kitchen should work for all devices :)

Don't run the kitchen as root and you won't get a message telling you not to run it as root :)

edit: oh, just saw you solved it. Glad to hear it :)
[SuperR Kitchen] pendor24:
hellos

I have a little problem , I work with version 1. 0 . 79 and she will not accept the firmware files (original)

forced to work from a backup or extraction Adb . Ordinary ? but quite a hassle for me that was not all mobile where I made ​​Roma .

Samsung .
[SuperR Kitchen] rrd84:
Hello,

Noob here.. :(

My device is T2 Ultra Dual Sim D5322

I don't know much about Kitchen Tools.. nowadays checking tutors of various kitchen tools.

Currently I am using custom rom on my device & experimenting different ports, patches & mods.

I want to know, by using SuperR's Kitchen can I build working custom rom for my device D5322 ?

What else i have to download to make this tool to work?

As all other tools needs JDK & other stuff installed, but here nothing else is mentioned..

HELP PLEASE :)
[SuperR Kitchen] SuperR.:
Read post #4 to see what I need to be able to help you. Read my support policy (link in my signature) while you are at it.

Try it first, then ask for help if you need it. The kitchen will tell you what dependencies you are missing (if any) and install them for you if you are using a Debian based distro such as Ubuntu. You would already know that if you had tried to install it. I can't support you if you don't even know you have a problem.
[SuperR Kitchen] pendor24:
thank you

with the previous version , there was no need to rename the system . img . ext4 . . deodex planted smart card manager and SysCoP on note 4 910F .
[SuperR Kitchen] SuperR.:
v2.0.8.6 (Donate version)

Changes:

Fixed a few harmless typos in the ui.

Fixed a typo in the knox remove list.

Fixed system.img.ext4 not being found and renamed to system.img.

v1.0.8.0 (Standard version)

Changes:

Fixed a few harmless typos in the ui.

Fixed a typo in the knox remove list.

Fixed system.img.ext4 not being found and renamed to system.img.
[SuperR Kitchen] Sc4ryB3ar:
Either I'm dense, or the xda labs beta app, no longer has a thread search option......

So I'll ask, although I'm fairly certain it has been asked and probably answered already....maybe even by me :/

Is either of the free or donate version buildable/installable on an Arch Linux Distro?
[SuperR Kitchen] SuperR.:
Both can be used in any Linux that supports bash. You will need to manually install the missing dependencies (if any) since the kitchen only installs dependencies on Debian based distros at the moment. It will tell you what you are missing (if anything) so it should not be too hard :)
[SuperR Kitchen] Sc4ryB3ar:
Donation, with note & ID sent, please & thank you, kindly. :)
[SuperR Kitchen] pendor24:
Hello . still problems with the kitchen. smart card manager it is stopped , sheath , SysCoP . Yet I have a Roma (android 6) on the edge s7 and the s5 (with a previous verssion ) and no worries. and it does not work ( note 4 to 910F )

system , linux mint , Zorin 9 or 11 . an idea ?
[SuperR Kitchen] KreAch3R:
Hey guys and [MENTION=5787964]SuperR.[/MENTION]

The kitchen is an extremely great piece of code, and I congratulate you on that! :good:: highfive: I tried the search function but couldn't get any relevant info, I have one question. Can we automate the kitchen's work itself (kind of meta), like pushing multiple arguments into it? The only way I could find online was to use a "here document" and EOF etc, but it's more of a hack due to the insane amount of question setups of the kitchen.

Specifically, I would like to make it take a zip, extract the rom, deodex apks, and stop.
[SuperR Kitchen] bcrichster:
As in.. Deodexing on the phone itself?

Sent from CM12.1 *N9515*
[SuperR Kitchen] KreAch3R:
No, as in, don't pick manually what you want the kitchen to do ("create new project", "extract", "yes", "no", "4", "q"), and wait between the commands, but script the kitchen itself like:

./superr --new-project --name test --extract --deodex --sparse-image

etc etc etc
[SuperR Kitchen] bcrichster:
Umm.. I happen to like the kitchen the way it is, to keep people from having issues accidentally or otherwise

Sent from CM12.1 *N9515*
[SuperR Kitchen] SuperR.:
v2.0.8.7 (Donate version)

Changes:

New Feature - Unattended extraction aka AutoROM - Allows you to use a config file to choose options when extracting a ROM.

To go along with the new AutoROM feature, here is a new plugin :)

AutoROM Config

by [MENTION=5787964]SuperR.[/MENTION]

Creates an AutoROM config file to automate the extraction process and many other tasks.

Currently supports perm type, vendor.img, rom name, custom signature, deodexing, root, su.d, and Busybox

Usage:

In the kitchen main menu, choose Misc Tools > Run a plugin > autorom_config
[SuperR Kitchen] asc1977:
I updated to new version but after it it didnt runs anymore

Wrong fs type, bad option, bad superblock on /dev/loop0

Missing code page, helper programm or other error

If i do dmesg

Only one red entry

EXT4-fs (loop0): error loading journal

Additional i updated with superr also ubuntu

Anyone a idea??
[SuperR Kitchen] JochenP:
I have made a quick test of AutoROM Config.

Regardless of the preselection i have made for root method, script stops and i am asked again for root method. Plugin writes correct key to AR-config file. Please check this, thanks
[SuperR Kitchen] SuperR.:
This does not sound like a kitchen issue.

Please upload the AR-config so I can see what options are chosen. Are there errors on the screen if you scroll up in the terminal? How far does it get before stopping?

edit: Just updated the AutoROM plugin to check for vendor.img in ROM directory before asking if you want to include it and a few minor UI changes.

edit2: updated the AutoROM plugin again to not ask for su.d or Busybox if root was not selected.
[SuperR Kitchen] asc1977:
I read about the problem and i find out that superr kitchen cant mount. It works before i update but not after update to newest version. I choose extract system.img. than comes sudo passwort and than the error. I tried manual mount ext4/dev/sda6 and this works. So did you anything change for mounting?? I cant mount system.img with your tool

---------- Post added at 20:29 ---------- Previous post was at 20:22 ----------

Btw

How i can get a older version to test?
[SuperR Kitchen] SuperR.:
I did not change anything for mounting and everything mounts fine on this end. I did find an error I made though which prevents you from choosing Extract for new rom from the main menu if you don't have an AutoROM config file. Not sure if this is causing your problem. I would do a clean kitchen install with the new update below and see if it clears up for you. If not, try the standard version to see if it mounts there. Let me know how it goes :)

v2.0.8.8 (Donate version)

Changes:

Get by-name from boot.img/kernel.elf will now be used with AutoROM if by-name is not already in the database.

Fixed not being able to choose Extract for new rom if you don't have an AR-config file.

I don't maintain older versions anymore. We only move forward around here :)

edit: nevermind lol. Here is v2.0.8.6 as a zip :)
[SuperR Kitchen] asc1977:
Donate version i havent. Install free version new from github but same problem

Gesendet von meinem SM-G925F mit Tapatalk

---------- Post added at 20:43 ---------- Previous post was at 20:42 ----------

Gesendet von meinem SM-G925F mit Tapatalk
[SuperR Kitchen] SuperR.:
Sorry, but if the standard version does not work something else is wrong and it is not a kitchen problem. Not sure if you saw my last edit but I posted a zip for you of v2.0.8.6 for your testing. I bet you have the same problem with it as well but it is the same thing you were running before your Ubuntu update. Try a fresh Ubuntu install of 16.04 and I bet your problems go away :)
[SuperR Kitchen] asc1977:
Now i see zip but i cant download. I need to register. I think i must try with new install of ubuntu. But first i have to deinstall it because free diskspace i give my ubuntu partition is also to small. Thx anyway
[SuperR Kitchen] SuperR.:
Here is v1.0.7.9, which should be the one you were using before your Ubuntu update. I bet you have the same issue but it may be worth a try for your peace of mind :)
[SuperR Kitchen] stealthee:
Tried searching could not find the answer. On Ubuntu 64 im getting the error /home/joe2/superrs-kitchen/superr: Line 7541: depinstall: Permission denied ... when I try to let the kitchen install dependancy's. I did install all the ones its said to manually install and still get the same error. It was so fast I had to camstudio and slow mow to read it lol. Anyone got any ideas?

[IMG="error"]http://i1301.photobucket.com/albums/ag103/jose_rivera6/PlayerPlus_2016-06-15_17-06-38_zpszkp51gl8.png[/IMG]

Thanks

Stealthee
[SuperR Kitchen] SuperR.:
No clue why you are getting an error, but you can try running this command manually. It should install everything required for 64-bit Ubuntu 16.04:

sudo apt-get install binutils libc6-i386 coreutils cpio e2fsprogs findutils gawk gcc grep gzip libc-bin liblz4-tool lzop mount ncurses-bin perl-base sed tar util-linux vim-common wget xz-utils bison gperf build-essential zlib1g-dev zlib1g-dev:i386 g++-multilib libxml2-utils bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev libsepol1-dev dpkg-dev make ccache automake squashfs-tools schedtool

The command is long, but it will install only the things you don't already have installed. If you are not using Ubuntu 16.04, you may need to find the package equivalents for your distro.
[SuperR Kitchen] stealthee:
ran the command and looks like it added more dependancy's but still getting the . Error: one or more tools could not be built. :(
[SuperR Kitchen] SuperR.:
Let the kitchen try to install the dependencies, and then let it install the binaries after it does not work. If that still does not work, download the 64-bit_binaries and extract them all into /kitchen/tools.
[SuperR Kitchen] JochenP:
Cross-checked wit last kitchen v.2.0.8.8 and updated AutoROM plugin - still kitchen asks as last step for rooting-method.

No errors if i scroll up.

Here is my AR-config: https://www.androidfilehost.com/?fid=24591000424940358

Thank you for your creative ideas :good:
[SuperR Kitchen] asc1977:
Thx but i complete installed ubuntu new and work. Every time if i update ubuntu i get problems. I think i never update it. Thx anyway
[SuperR Kitchen] LAzY_kRAzY:
hello everyone..

I just created a stock deodexed rooted flashable zip for my G900H using latest build of kitchen.. but when I try to install it, I get the following error

script aborted: This package is for "k3g" devices; this is a "k3gxx".
This package is for "k3g" devices; this is a "k3gxx".
Updater process ended with ERROR: 7

My device is G900H.. it is rooted and I am using TWRP Recovery 3.0.0

I have installed other G900H Roms so I guess there is no problem of rooting or recovery.. cam anyone guide about whats the issue/solution ??

thanks
[SuperR Kitchen] jazzespresso:
picconv_tool

you know this picconv_tool , does not always works, in some cases, converter fails to convert. I know developer of this tool [MENTION=334644]sorg[/MENTION] did mentioned in his thread "this converter *MUST* be used on device originally supporting QMG, ASTC, etc", now question is how to find out if supported or not. So far, for theming purpose of course, I could not able to convert my .qmg files to .png and it is quite frustrating...

I wish there's another tool that drop all .qmg files and convert back to them .png!

However, don't take this post as not appreciated the tool, on the contrary I do appreciated, my complain just comes from my frustration.:(

hope someone here can give helping hand who can help me convert my res folder....if you will, pm me so I can upload my res folder!

---------- Post added at 09:55 AM ---------- Previous post was at 09:36 AM ----------

of course it will fail, take a closer look at your updater-script's assert piece. Also know that G900H has couple different versions; k3gxx and k3g.

to make it work, you may try update updater-script's assert as below

#ASSERT

assert(getprop("ro.product.device") == "k3gxx" || getprop("ro.build.product") == "k3gxx" ||

getprop("ro.product.device") == "k3g" || getprop("ro.build.product") == "k3g" ||

abort("This package is for "k3gxx,k3g" devices; this is a "" + getprop("ro.product.device") + ""."););
[SuperR Kitchen] SuperR.:
Fixed in new version below :)

Glad you got it sorted out :)

It seems someone has not read post #4 where the very simple solution is explained :)

As the plugin repo states, I have no idea if the picconv_tool will work. I don't even have a device that uses qmg files so I can't test it at all. If you find a solution that works in Linux, I am happy to make another plugin :)

v2.0.8.9 (Donate version)

Changes:

Fixed asking for root method when using AutoROM on M and above.
[SuperR Kitchen] LAzY_kRAzY:
sorry :D thanks for the Kitchen and all your effort :)
[SuperR Kitchen] asc1977:
I have a question

I am on latest free build of kitchen. All goes right. After deodexing i go to build menue and choose build rom.zip

Kitchen dont ask me like earlier versions how to name the zip so after build zip sucessfull there is no zip. After i do it again there is one zip but also no name only date and time as name. Did i do something wrong or its a bug?
[SuperR Kitchen] osm0sis:
This is pretty interesting stuff! Looks like this can repack the ramdisk and convert boot.img back to kernel.elf as well?

Does it work with the MM kernel.elf here? It was reported to not work with elftool.
[SuperR Kitchen] bigrammy:
On a Stag party weekend so I won't be able to check till Monday and that's if I feel up to it as it's been a while since I last did a weekender with the lads. :laugh:
[SuperR Kitchen] SuperR.:
I renamed the boot.img in the link you provided to kernel.elf and ran it through elf2boot. It creates a boot.img that seems ok visually and unpacks fine with AIK, but I have no way to test if it boots. Here it is in case you would like to take a look :)

elf2boot does not convert back to elf. It only converts from kernel.elf to boot.img.
[SuperR Kitchen] shoey63:
It unpacks the kernel.elf, and re-packs it as a boot.img. There is not much point in trying to repack as elf, as unpacking/repacking breaks the signature, so you need to unlock the bootloader to flash it. In that case, may as well flash a boot.img :cyclops:

Also, the tool needs the build.prop to make it work.

And you need to have access to the Donate version of the kitchen to access it. (Maybe [MENTION=5787964]SuperR.[/MENTION] can PM you the code?)
[SuperR Kitchen] osm0sis:
Thanks! Can't test it, since it's from another user however.

Ah, so the Sony bootloaders accept both kernel.elf and boot.img? I didn't know that. Cool! :)
[SuperR Kitchen] thijac99:
Hello ! Donation for the kitchen is sent, please thank you for the job. Sorry for my english.....
[SuperR Kitchen] pendor24:
Hello ! Donation for the kitchen is sent, please thank you.
[SuperR Kitchen] reefuge:
REF: MOTO G 2nd Gen (XT1068)

well metadata seems to be working correctly on stock rom made from TWRP (clean) back up, the wi-fi problem seems 'FIXED ....:D its locked on and allowed setup to continue, will try again with stock images and sparse chunks and report back on these ............OH ***** tried again and it stopped working..... lol - ALMOST GOT IT!!!

this makes perm redundant as metadata works so wont test further on perm (unless other request or i'm bored and want to try akitkat based rom) FAILED says turning wifi on and stops dead

again sparse.dat invalid blkdiscard - I know this method works as I install the nxus.rom via this method, so its just gonna be something that needs adjusting

note the sparse.new.dat is a massive 1.01GB (5.0.2)(but so are perm and metadata) compared to nxus.rom sparse.new.dat at 439mb ( and this is 5.1.1) perhaps they ultra compress or strip a lot out...!!
[SuperR Kitchen] hohassan444:
this is the recovery log
[SuperR Kitchen] SuperR.:
The thing is, we need to know your exact system partition size when building the system.img which is then converted to sparse dat. All I read points to that being the issue. So, I/we need to figure out a good method of gathering this info. Getting it from the device is the best way, but not everyone has the device to get it from. I will add an option to get it from the device when I get a chance and see where that gets us. I will also add an option to enter it manually (in bytes), so you can play around with the size.
[SuperR Kitchen] SuperR.:
This is your problem, not the symlinks

minzip: Error writing 8192 bytes from zip file from 0xffe5e0b4: No space left on device

It can't do anything else once you run out of space on your device.
[SuperR Kitchen] BeansTown106:
awesome work on the kitchen [MENTION=5787964]SuperR.[/MENTION] !! it is my new go to for extracting factory images and deodexing!! only issue i have noticed is after deodexing if for some reason an app has libs that are symlinked it gets removed, not a big deal though as i can just open the system.img and check. but figured id point it out :good: :highfive:
[SuperR Kitchen] SuperR.:
Glad you are enjoying it :)

Yes, the symlinks are removed from /system/* on extraction and added to the updater-script for creation on flash.

edit: they are also recreated when you build a system.img or sparse dat
[SuperR Kitchen] hohassan444:
ok thanks....i deleted some apps from vendor folder...it install now without problems.

but 2 problems now remaining

1 - cannot deodex PrebuiltGmsCore

2 - sparse_dat option not working....waiting for manual editing of image size.
[SuperR Kitchen] sparks15:
Hi, thanks for this awesome kitchen, i have a question, this works with marshmallow?
[SuperR Kitchen] bcrichster:
Theoretically? YES. Plz give it a try and let us know? :cool:

Gratefully sent from my Rooted Tesla N9510
[SuperR Kitchen] sparks15:
[MENTION=5787964]SuperR.[/MENTION]

Root, deodexing and init.d dont work on marshmallow.
[SuperR Kitchen] reefuge:
REF: MOTO G 2nd Gen (XT1068)

Well quite happy to root / install busybox etc for whatever you need to push / pull info from phone - the sparse chunks(x5) size are 256mb when we fastboot flash and I remember of top of head issues warning target-sparse-max size 256mb as it flashes system img in multiple parts.

added some screen shots of partitons via terminal from phone / can always push parted (later tonight when home) and get more info if needed?
[SuperR Kitchen] andreya108:
Yesterday, I've tried to deodex Stock MRA58K Hammerhead system image. And it does not boot. (Bootloop after ART compiling)
[SuperR Kitchen] SuperR.:
v0.9.1.6

Changes:

Added the ability to choose how the system partition size is determined when creating sparse dat roms.

m = Main menu on all menus.

All menu options that lead to other menus are now yellow and at the bottom of the menu list.
[SuperR Kitchen] dkionline:
Can u update to latest Smali/Baksmali?
[SuperR Kitchen] SuperR.:
I need more info. Please see post #4 for the type of questions I need answered.

Root is something I do not have control over. As soon as there is a SuperSU that works on Marshmallow it will be included in the kitchen. Deodexing should work on Marshmallow, but your device may have special needs.

I need more info. Please see post #4 for the type of questions I need answered
[SuperR Kitchen] SuperR.:
Yes but fyi, smali/baksmali are only used to deodex pre-lollipop roms. Oat2dex.jar is used for L/M
[SuperR Kitchen] dkionline:
Ok good, ill make a pull request if i find something.
[SuperR Kitchen] SuperR.:
You will need to be rooted. Give the new kitchen a try and when building the sparse dat zip, choose option 1 to get system partition size from device. Let me know how it goes :)
[SuperR Kitchen] SuperR.:
v0.9.1.7

Changes:

Updated smali/baksmali

Built oat2dex.jar from the newest source.

Added the system partition detection choices when building a system.img

edit: Just noticed an oversight on my part. Since the file names changed for smali/baksmali, those who did not git clone originally will need to remove the old versions from the /kitchen/tools/ directory or the kitchen might continue using the old ones. It will be fixed in the next version.
[SuperR Kitchen] reefuge:
tried v.9.1.6 and v9.1.7 wont extract from sparse_chunks keeps asking for sudo password the goes access denied........ seems to extract from .ext4.win though but only build 7.6mb zips

phone rooted and included some screen shots from terminal with partition info
[SuperR Kitchen] osm0sis:
This is pretty baffling. I just tore apart a few kernel.elf and found where it stores the pagesize and it doesn't match your test. :confused:

From your Xperia Z file elf header:

9D A3 8C 00 e_shoff

which is an offset that points to the section header, generally at the end of the file in our case, where the remainder of the bootimg info seems to get placed:

9D 93 8C 00 offset

00 10 00 00 size

offset points to the cmdline (add 8 to the offset and read until we hits all 00s, but shouldn't exceed 512 bytes per the usual Android image spec)

and size appears to directly be pagesize, but as you can see it's 1000=4096, not 0800=2048.

https://en.wikipedia.org/wiki/Executable_and_Linkable_Format#File_header

[MENTION=5787964]SuperR.[/MENTION], so theoretically "readelf -lS" should give us the section info to draw pagesize and the address that basically points to cmdline.

I also now know what's wrong with elftool for newer kernel.elf files, no 64-bit ELF support so it doesn't recognize the different magic or understand that it doubles the address length.

Also, there are apparently a few more variations on ELF kernels that haven't been tried with the plugin yet.. ones with RPM and IPL. :eek:

Judging from the "build" script there, Xperia S kernel would be a good one to test since it has an RPM. :good:

Edit

: Here's me working it all out in case it's helpful: http://xdaforums.com/showthread.php?p=67369702#post67369702
[SuperR Kitchen] shoey63:
Actually pagesize being 4096 isn't a problem. It works. I assumed 2048 was required as per this documentation https://github.com/sonyxperiadev/kernel-copyleft/blob/10.7.A.0.xxx/README_Xperia

It was the tags offset that was the issue. Must be 00000100 in the repacked boot.img for the Z or it won't boot.
[SuperR Kitchen] asuraaaa:
Hello,

I installed superr kitchen without problem. I pushed samsung firmware in folder superr_MyNameProject, i selected option 4, i selected option my firmware. But don't continue, never finish of this step:

Can you helpme?

Thanks
[SuperR Kitchen] osm0sis:
Ah, that's good news then! All is not lost! :D

So as to not reinvent the wheel, I've asked the author of the bootimg util the plugin originally used if he could fix it for older kernel.elf files without dtb's, and also if he could release the unpackelf source so it can be built for other architectures. :good:
[SuperR Kitchen] _that:
That seems to be only the size of the "SIN" section that is appended to the file that contains some header, the kernel command line, and the signature. ELF doesn't use pages so it doesn't have a page size.
[SuperR Kitchen] osm0sis:
I see.. would it still be safe to assume 4096? Or would 2048 be a better choice? That bootimg util reported 4096 for that Xperia Tab Z4 image I was testing so it got it somehow? :confused:
[SuperR Kitchen] _that:
This is how the bootimg tool determines page size - source code found here: http://xdaforums.com/showpost.php?p=65931376&postcount=52

printf("BOARD_PAGE_SIZE=\"%d\"\n", 4096);

:)

The page size in the boot image is only used for aligning parts of the boot image. It was originally meant for aligning the boot image with raw flash blocks (on MTD-type storage), but for eMMC devices is now only important that the chosen page size is supported by the bootloader.