FORUMS
Remove All Ads from XDA

[MOVED] SuperR's Kitchen (See last post)

2,832 posts
Thanks Meter: 4,662
 
By SuperR., Recognized Developer on 16th September 2015, 06:19 AM
Thread Closed Email Thread
Disclaimer: I am not responsible for anything bad that may occur from the use of this kitchen, but I will take all the credit you can give me if it works for you

SuperR's Kitchen

Please read the usage instructions in post #3 and the troubleshooting in post #4 below before asking for help. Thanks

Source
Standard Changlog (file download)
Donate Changlog (file download)

Download/Install
Open your terminal to the location where you want the kitchen to reside. Enter the following commands one by one pressing ENTER after each line:
Code:
git clone https://bitbucket.org/superr/superrs-kitchen.git
cd superrs-kitchen
./superr
Download zips here
NOTE: You will not be able to use the kitchen updater if you download zips

Credits:
@osm0sis - For Busybox Installer and Android Image Kitchen
@Chainfire - For SuperSU
@JesusFreke - For [Bak]smali
@nkk71 - For creating the TWRP minzip patch
@Captain_Throwback - For providing a pre-compiled update-binary with the minzip patch and squashing bugs
@_riddle - For oat2dex
@iBotPeaches - For Apktool
AOSP - For zipalign, adb, img2simg, simg2img, make_ext4fs, oatdump
@xpirt - for img2sdat
@bcrichster - For extensive testing

XDA:DevDB Information
SuperR's Kitchen, Tool/Utility for the Chef Central

Contributors
SuperR.

Version Information
Status: Stable

Created 2016-01-30
Last Updated 2017-05-03
Attached Thumbnails
Click image for larger version

Name:	boot1.png
Views:	8364
Size:	19.2 KB
ID:	3890127   Click image for larger version

Name:	boot2.png
Views:	8248
Size:	24.5 KB
ID:	3890128   Click image for larger version

Name:	boot3.png
Views:	8122
Size:	40.2 KB
ID:	3890129   Click image for larger version

Name:	buildzip.png
Views:	7566
Size:	24.9 KB
ID:	3890130   Click image for larger version

Name:	customzip.png
Views:	7370
Size:	26.8 KB
ID:	3890131   Click image for larger version

Name:	debloat.png
Views:	7180
Size:	33.8 KB
ID:	3890132   Click image for larger version

Name:	deodex.png
Views:	6926
Size:	18.9 KB
ID:	3890133   Click image for larger version

Name:	perm.png
Views:	6738
Size:	24.3 KB
ID:	3890134   Click image for larger version

Name:	recovery.png
Views:	6450
Size:	25.3 KB
ID:	3890136   Click image for larger version

Name:	recovery2.png
Views:	6266
Size:	23.4 KB
ID:	3890137   Click image for larger version

Name:	rom.png
Views:	6120
Size:	31.1 KB
ID:	3890138  
The Following 293 Users Say Thank You to SuperR. For This Useful Post: [ View ]
 
 
16th September 2015, 06:19 AM |#2  
SuperR.'s Avatar
OP Recognized Developer
Invisible
Thanks Meter: 4,662
 
Donate to Me
More
Features:

*Extract and create ROM from:
  • Rooted Device
  • Custom Recovery
  • Existing ROM zip
  • system.img/boot.img (and cache.img on Samsung devices)
  • system.ext4.tar/boot.img
  • system.ext4.win/boot.emmc.win (including multi-file *.win000, *.win001, etc)
  • Moto and other factory firmware zips containing sparsechunk files
  • cm12 + roms with sparse dat files
  • Zips that contain system.img and boot.img
  • Samsung firmware zips that contain tar.md5 file
  • Official Nexus firmware tgz
  • Official Nexus preview tgz
  • system directory that contains symlinks and boot.img
*Create flashable zips of many varieties including:
  • Full ROM
  • Switch between set_perm, set_metadata (KitKat+), raw_img, and sparse_dat (Lollipop+)
  • Kernel (including init.d if you added it with the kitchen)
  • Recovery
  • Media
  • app, priv-app, and framework
*Deodex the following:
  • N Preview ROMs
  • Marshmallow ROMs
  • Lollipop ROMs
  • KitKat and earlier ROMs
*Root features:
  • Root/unroot
  • Choose SuperSU zip (add other versions to /tools/root/supersu directory)
  • Choose system OR systemless root for M+ and Samsung 5.1.1 roms
*Boot features:
  • Unpack/repack boot/recovery img (Big Thanks to @osm0sis for mkbootimg source!!!)
  • Add/remove init.d support
  • Add/remove su.d support
  • Add/remove insecure boot
  • Remove dm-verity
  • Remove forceencrypt
  • open_bump.py compatible (download it and add to the tools directory)
*By-name auto-detection from:
  • Device
  • Existing ROM
  • boot.img
  • kernel.elf
  • **OR**...manually enter it
*mmcblk auto-detection from:
  • recovery.img
*Kitchen updater:
  • View the last 3 changelogs when an update is available.
  • git pull if the kitchen was cloned
  • wget zip and extract if kitchen zip was downloaded
  • Option to check for updates when the kitchen starts
*Create system.img
*Device database for mmcblk devices (currently very small, but will grow over time)
*Add devices to the assert
*Add custom asserts
*Zipalign apks
*Debloat ROM
*Custom Debloat list support
*Remove Knox
*Add/remove busybox (Big thanks to @osm0sis for his Busybox Installer)
*Add/remove user app support (/data/app)
*Sign zips
*Translatable with language files

*Donate version additional features:
  • Does not say Built with SuperR's Kitchen in the updater-script
  • Does not replace ro.build.display.id with Built.with.SuperRs.Kitchen
  • Allows you to create a custom entry in the updater-script below the ROM name
  • Removes all the Place holders (#ASSERT, #SYM, #PERM, etc) from the updater-script before zipping.
  • Custom ro.build.display.id
  • Option to convert updater-script to update-binary for all rom zips EXCEPT sparse_dat.
  • Add custom directory to be included in and flashed with rom zip to location of your choice.
  • Plugin support - Add your own script to the /kitchen/tools/plugins directory and the kitchen will run it for you. Available plugins list here.
  • AutoROM - Unattended ROM development using a config file.
The Following 62 Users Say Thank You to SuperR. For This Useful Post: [ View ]
16th September 2015, 06:19 AM |#3  
SuperR.'s Avatar
OP Recognized Developer
Invisible
Thanks Meter: 4,662
 
Donate to Me
More
Usage:
  1. Run "superr" from it's location in terminal
  2. Create new project using the menu
  3. Copy ROM zip into the superr_NAME directory of this tool (NAME = the name of your new project).
    OR
    Copy system.ext4.tar and boot.img into the superr_NAME directory of this tool.
    OR
    Copy system.ext4.win and boot.emmc.win into the superr_NAME directory of this tool.
    OR
    Copy system.img and boot.img into the superr_NAME directory of this tool.
    OR
    Copy official Nexus tgz into the superr_NAME directory of this tool.
    OR
    Copy Samsung firmware zip into the superr_NAME directory of this tool.
    OR
    Copy Moto firmware zip into the superr_NAME directory of this tool.
    OR
    Leave superr_NAME directory empty to extract from rooted device or custom recovery
  4. Extract for new ROM from the Main menu.
  5. Enjoy!

Example:

In your terminal, type the following where "/home/user/kitchen/" is the directory where the kitchen lives:

Code:
cd /home/user/kitchen/
./superr
NOTE: the above code is 2 separate commands and requires ENTER to be pressed after each command

OR

Double-click the superr file and choose "Run in Terminal" if your OS supports it.

Add your own device support:
  1. Create a new project in the kitchen.
  2. Add your files to the project directory (system.img/boot.img, system.ext4.tar, win, zip, etc.)
  3. Extract for new rom from the menu
  4. When asked how to get your partitions, choose detect by-name from boot.img. If it gives you an error, put a recovery.img in your project directory and choose detect mmc from recovery.img.
  5. Enjoy
The Following 74 Users Say Thank You to SuperR. For This Useful Post: [ View ]
16th September 2015, 06:20 AM |#4  
SuperR.'s Avatar
OP Recognized Developer
Invisible
Thanks Meter: 4,662
 
Donate to Me
More
Troubleshooting/FAQ:

When asking for help, please provide as much of the following info as possible so I can help as easily as possible. I am a busy person and would prefer not to ask all of these questions every time someone has a problem. Thank you for understanding.

What Kitchen version?
What environment are you running the kitchen in (OS, 32/64-bit, cygwin, Bash on Windows, etc.)?
What device are you working on (make/model)?
What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)
What Android version?
What perm method (set_perm, set_metadata, sparse_dat, raw_img)?
What did you do after extracting and before building?
Were there errors on the screen if you scroll up in the terminal?
Send a recovery.log after flashing if you have problems flashing the ROM.
Send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)
Use the support option in the Misc Tools menu and attach the support.zip to your post.


Donate version Info
Access to the donate version of the kitchen requires a minimum donation of $10.00 US

I have chosen Gitlab.com as the host for the donate version after running into a roadblock with the number of users Bitbucket allows in the free private repositories. Once you donate, set up a Gitlab account (free) and post your Gitlab username in this thread. I will add you to the private repo and you will then have access to the donate version of the Kitchen. Follow the steps below to get it downloaded and running

**Alternate donate option here for users that can't use the "Donate to Me" feature of xda**

Open your terminal to the location where you want the kitchen to reside. Enter the following commands one by one pressing ENTER after each line:
Code:
git clone https://gitlab.com/superr/superrs-kitchen2.git
cd superrs-kitchen2
./superr
NOTE: After you enter the first line and press enter, it will ask you for your Gitlab username and password. Make sure you enter it correctly or it will not work. Thanks for the donation, enjoy

NOTE2: The Plugin Repo can be found here.

Ubuntu4Kitchen
An Ubuntu 16.04 distro with all the things you need to get the kitchen working easily.

This was created using the official Ubuntu 16.04.1 iso. It is basically an updated and repacked version of the original iso image.

Here are the changes from standard Ubuntu:
  • All dependencies are met for easy kitchen install
  • SuperRs-Kitchen installer/launcher script is on the desktop
  • Unity panel shortcuts are Nautilus, Chrome, Synaptic Package Manager, and Show Desktop
  • Nautilus File Manager asks what to do when you double-click an executable text file (bash script) by default
  • Nautilus uses list view by default
  • App menus are in the app window by default
  • The system notification popups are click-to-close and higher on the screen
  • Chrome and Synaptic package manager are installed
  • Firefox, Thunderbird, and LibreOffice have been removed
It should work in VM, usb live boot, or dvd. Just double-click SuperRs-Kitchen on the desktop and choose "Run in Terminal" to get started

Download:
Ubuntu4Kitchen-16.04.1-amd64.iso

Language Files (translations)
English - Default/Included in the kitchen
Italian - Translated by @luigimak
Chinese - Translated by @曦颜XY

Download language files here

Once the language zip has been downloaded, extract to /kitchen/tools/language and restart the kitchen.

Does this kitchen support Windows CYGWIN?
The last I heard, most things should work. CYGWIN is not officially supported.

WSL (Bash on Ubuntu on Windows)
Not sure how this will work at this point. If your version of WSL supports OS interoperability (can run Windows apps from WSL shell), you might have success. WSL is not officially supported.

Missing Dependencies/One or more tools could not be built.:
Paste into terminal, press enter, type your user password and press enter:
Code:
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
There are probably more packages here than you need, but this should cover just about everything on 64-bit Ubuntu 16.04. The kitchen will offer to install them for you if you are on a Debian based system. If not, you will need to find the package equivalents for your system.

If you give up on getting the binaries compiled, you can let the kitchen install the appropriate binaries. It will ask you if you want to install them after trying to build, then installing the dependencies and trying to build again. If it still fails that is when it will offer to install prebuilt binaries.

Which perm type should I choose?
Here is a very brief summary of set_perm, set_metadata, sparse_dat, and raw_img.

set_perm : The oldest of the 4. Sets file/directory permissions when flashing a rom. Not recommended for KitKat and above.

set_metadata: Also sets file/directory permissions when flashing a rom, but also adds file contexts. It was introduced with selinux in KitKat. Recommended for KitKat and above.

sparse_dat: The newest of the 4, and only works on Lollipop +. The permissions, symlinks, and file contexts are all added inside a sparse image. A sparse image is an image with a more efficient space usage. Only for Lollipop and above. May or may not work as expected on Marshmallow and above because the rimg2sdat binary has not been updated and it is closed source.

raw_img: This is literally raw images that are flashed to your device. The permissions, symlinks, and file contexts are all added inside the raw image. Works for all Android versions.

Flashing error:
This package is for "xxxxx" devices; this is a "yyyyy"

The problem is the asserts and it is easy to fix. In the kitchen menu, go to ROM Tools > Asserts > Add/Remove device asserts. At the bottom it will say "xxxxx". Edit the line to say "xxxxx,yyyyy" and press enter. Build your rom again and flash.

stat: failed to get security context
The problem is that your system is not selinux enabled so the stat utility does not have the required libs to check the file_context.

Solution: Download and install stat_alt. It bypasses your system stat utility in favor of the one in /home/username/bin. This stat however is a bash script that runs /home/username/bin/stat1 with the required selinux libs. There is a README file in the zip with installation instructions.

Why is my ROM zip so small?
blkdiscard failed: Invalid argument
These are generally due to the partition size detection method. You need the correct partition size for ALL partitions you are creating sparse dat and raw_img images for. The kitchen will ask for each one that is included in your rom when you choose to build the full rom zip. If none of the provided auto-detect methods work, you will need to find the partition size on your own and enter it manually in the kitchen.

Root problems?
You can replace the SuperSU.zip in the kitchen with any flashable SuperSU version you want. It is located in /kitchen/tools/root/supersu. Delete the one that is there and add yours. Then, unroot, re-root and your replacement will be used.

Auto check for updates when kitchen starts
To enable the auto update check, go to "Check for updates" in the main menu. After it checks, you will be asked if you want to enable it.

If you change your mind later, you can navigate to the /kitchen/tools directory and rename the updatecheck-yes or updatecheck-no files accordingly. Alternatively, you can delete the updatecheck-yes/no file and you will be asked again next time you check for updates.

I added root and busybox but there is no su or busybox in my project. Why?
The kitchen does not add Busybox or SuperSU files to the project. Instead it adds flashable zips inside the rom.zip. There are many variables to deal with (Android version, device architecture, manufacturer, system/systemless, etc.). Flashing the zips with the rom accounts for all of these variables and there is no reason to re-invent the wheel.

Debloat and custom debloat
There are 2 options in the debloat menu (besides knox which is self explanatory):

1) Debloat ROM
This option removes all files included in the kitchens standard bloat list file - /kitchen/tools/root/bloat

2) Custom Debloat
This option removes all files included in the bloat_custom file - /kitchen/tools/root/bloat_custom
This file is empty by default and is there for you to add whatever you want to remove. You can either add everything you want to remove and use only option 2, or you can add new files here and use option 1 and 2.

I suggest you take a look at /kitchen/tools/root/bloat to see the format of the listed bloat files. Use the same format for the bloat_custom file.

When you use either option, the files are not deleted. Instead they are moved to the 00_project_files directory in case you want to restore them later.

Deodexing
If you want to use the M deodex method from v1.0.2.6, choose smali/baksmali when it asks what method. If you want to use the M deodex method from v1.0.2.7 and later, choose oat2dex. If one does not work properly, try the other.

Deodexing Samsung roms may or may not work. If your rom does not boot after deodexing, try it without. If it works and you must deodex your rom, try a different tool. I hear svadev deodex tool works well for Samsung roms.

boot.img errors
If the kitchen gives you errors about unpacking boot.img, there is a good chance I will not be able to help. I suggest you figure out how to unpack it using Linux commands/binaries and let me know how you did it. You may also find a tutorial about how to unpack your boot.img. If so, please send a link. It does not help me to know another tool works. I need the commands/binaries used in order to update the kitchen.

Feel free to upload your boot.img AND the build.prop from the same rom so I can check to see if I can fix it. I will ignore you if you don't upload both mentioned files

Plugins
The donate version has plugin support. This means you can integrate your own script into the kitchen. Each plugin must have its own directory inside the kitchen plugin directory, and it must be named the same as the plugin script.

Example:
/kitchen/tools/plugins/example/example

The first "example" is the directory, the second "example" is the script. You can check the example plugin in the kitchen for more details and use it as a template for your own plugin.

There are 3 variables set in the example plugin to take note of:
$base = /path/to/kitchen
$romdir = /path/to/kitchen/superr_projectname
$plugdir = /path/to/kitchen/tools/plugins/pluginname

The current plugin repo can be found here.
The Following 127 Users Say Thank You to SuperR. For This Useful Post: [ View ]
16th September 2015, 06:20 AM |#5  
SuperR.'s Avatar
OP Recognized Developer
Invisible
Thanks Meter: 4,662
 
Donate to Me
More
SuperR's Kitchen2 Plugin Repo

Installation:
  1. Download the plugin of choice
  2. Extract to /kitchen/tools/plugins
  3. Enjoy!
NOTE: The usage instructions in each plugin description below assume you have already installed it

NOTE2: If you would like to contribute a plugin, please read the info found here.


SuperR Maintained Plugins:

Add/Remove Files
by @SuperR.
  • Add all apk files from a directory
  • Choose apk to import
  • Choose directory structure to import
  • Delete files from your ROM based on directory structure
NOTE: To use "Choose directory structure to import" and "Delete files from your ROM based on directory structure", your directory must be set up as the following example:
Code:
your_directory_name/system/anything_you_want
your_directory_name/vendor/anything_you_want
your_directory_name/cache/anything_you_want
your_directory_name/hidden/anything_you_want
your_directory_name/boot.img
The above is only an example. You can add anything you want as long as there is a "system" directory inside another directory. When choosing the directory, choose your_directory_name instead of system or it won't work. Think of the directory structure exactly like the kitchen ROM directory. When you import directory structure, your directory will be copied into your ROM directory and files will be overwritten if they already exist. When you remove a directory structure, you will choose your_directory_name again and the plugin will remove the same files it finds from your ROM directory.

Usage:
  1. In the kitchen main menu, choose Misc Tools > Run a plugin > add_remove_files

AndroidImageKitchen
by @osm0sis
  • Has sudo support for M+ roms
  • Runs Android Image Kitchen unpackimg.sh and repackimg.sh on existing boot/recovery.img in rom directory.
  • If unpacking, the unpacked ramdisk will be copied to the rom directory where you can modify it with the kitchen
  • If repacking, the ramdisk will be copied back over to the plugin directory, the original image will be backed up in the 00_project_files directory, and the new image will replace the old in the rom directory.
More info and downloads can be found in the original thread here.

Usage:
  1. Download the newest Linux version of Android Image Kitchen at the link above.
  2. Extract it into the plugin directory so the files, unpackimg.sh and AndroidImageKitchen, are in the main plugin directory.
  3. Place a boot.img or recovery.img in your rom directory.
  4. In the kitchen main menu, choose Misc Tools > Run a plugin > AndroidImageKitchen
  5. Do what you want in the kitchen to the ramdisk using the boot/recovery tools menu.
  6. Run the plugin again to repack.
  7. Now your new image is in the rom directory ready to go

Apktools
by @SuperR.
  • Choose an apk from your current rom directory.
  • Decompile the apk.
  • Build apk.
  • Sign apk with 3 options (use signapk.jar, copy original META-INF to new apk, or copy new classes.dex and resources.arsc to original apk).
  • Move apk back to where it came from.
USAGE:
  1. In the kitchen main menu, choose Misc Tools > Run a plugin > apktools

Aroma Install
by @SuperR.
  • Install Aroma in your existing ROM.
  • Create aroma-config using a menu.
  • Choose apk files to add to the option menu.
Usage:
  1. Extract your ROM normally using ONLY set_metadata or set_perm.
  2. Download the Aroma Installer of your choice from this link into /plugins/aroma_install directory (DO NOT EXTRACT OR RENAME)
  3. In the kitchen main menu, choose Misc Tools > Run a plugin > aroma_install

AutoROM Config
by @SuperR.
  • 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:
  1. In the kitchen main menu, choose Misc Tools > Run a plugin > autorom_config

Carliv Image Kitchen
by @carliv
  • Copies boot.img or recovery.img from current rom directory to the plugin directory
  • Runs Carliv Image Kitchen with those those images in the correct place
  • If unpacking, the unpacked ramdisk will be copied to the rom directory where you can modify it with the kitchen
  • If repacking, the ramdisk will be copied back over to the plugin directory, the original image will be backed up in the 00_project_files directory, and the new image will replace the old in the rom directory.
More info and downloads can be found in the original thread here.

Usage:
  1. Download the correct version of Carliv Image Kitchen for your pc at the link above.
  2. Extract it into the plugin directory so both files, carliv and CarlivImageKitchen, are in the main plugin directory.
  3. Place a boot.img or recovery.img in your rom directory.
  4. In the kitchen main menu, choose Misc Tools > Run a plugin > CarlivImageKitchen
  5. Use the menu to navigate to the image you are working with and unpack it.
  6. Return to the kitchen by exiting Carliv Image Kitchen (Q to main menu, then E to exit)
  7. Do what you want in the kitchen to the ramdisk using the boot/recovery tools menu.
  8. Run the plugin again and choose repack and exit out again.
  9. Now your new image is in the rom directory ready to go

elf2boot
by @SuperR.
  • Creates a valid boot.img from most kernel.elf files
Usage:
  1. Place kernel.elf and build.prop in your rom directory. build.prop can be in system/build.prop or in current working rom directory.
  2. In the kitchen main menu, choose Misc Tools > Run a plugin > elf2boot

Gapps Installer
by @SuperR.

WARNING: I have no idea if gapps will flash properly. I have not tested the actual flashing. Let me know how it goes if you are brave enough to try it
  • Download and include Open Gapps with your ROM.
  • Choice of aroma, super, stock, full, mini, micro, nano, or pico
  • Detects Android version and architecture from ROM to download the latest available version for your device.
  • If there is no ROM, it will allow you to choose Android version and architecture.
  • Remove gapps if it already exists.
Usage:
  1. In the kitchen main menu, choose Misc Tools > Run a plugin > gapps

Magisk Mod Installer
by @SuperR.
  • Add Magisk Mod to your rom
  • Remove Magisk Mod if it already exists.
Usage:
  1. Download the Magisk Mod zip of your choice into the magisk_mod plugin directory.
  2. In the kitchen main menu, choose Misc Tools > Run a plugin > magisk_mod

Mods Install
by @SuperR.
  • Add any flashable zip to your ROM that uses an update-binary script instead of a updater-script
  • Remove mods
  • Shows the kitchen added mods you currently have installed
Usage:
  1. Download the mod zip of your choice into the mod_zips directory inside the plugin.
  2. In the kitchen main menu, choose Misc Tools > Run a plugin > mods_install

Nexus Firmware Downloader
by @SuperR.
  • Choose a Nexus device from a list.
  • Download the newest firmware.
  • Copy it to your ROM directory for extraction.
Usage:
  1. In the kitchen main menu, choose Misc Tools > Run a plugin > nexus_dl

Partition Zip
by @SuperR.
  • Create a flashable zip of one or more image files as long as you know the partition name where it should be flashed.
Usage:
  1. Copy the partition images you want in the zip into your rom directory.
  2. In the kitchen main menu, choose Misc Tools > Run a plugin > partition_zip
  3. Choose a partition img from the list.
  4. For by-name devices, type the partition name from your device where it should be flashed (ex. aboot)
  5. For mmcblk devices, choose your block from the list (add it to the device superr_mmc file if needed first).

picconv_tool
by @sorg

WARNING: I have absolutely no idea if this plugin will work
  • Pushes picconv and picconv.dex to your device.
  • Pushes res directory from the apkwork directory created by the apktools plugin.
  • Converts QMG, ASTC, etc images to PNG.
  • Pulls the converted images back to apkwork/out
  • Deletes all the new files from the device
Usage:
  1. Visit the original thread to download the newest version of the tool (be sure to thank @sorg while you are there).
  2. Copy the zip into the picconv_tool plugin directory.
  3. Run apktools plugin to decompile an apk
  4. In the kitchen main menu, choose Misc Tools > Run a plugin > picconv_tool
NOTE: If you try the plugin while connected to Android and it does not work, try again while connected to your custom recovery.

RUU Decryption Tool
by @Captain_Throwback and @nkk71
  • Decrypt ruu.exe and ruu.zip files stored in your current rom directory.
  • Extract system.img & boot.img to the current rom directory for extraction.
**This plugin can also be used as a standalone tool**
More info can be found here about the original tool.

Usage:
  1. Copy ruu.exe or ruu.zip to current rom directory (ruu.zip must be named exactly ruu.zip).
  2. In the kitchen main menu, choose Misc Tools > Run a plugin > decrypt_htc

samextras
by @SuperR.
  • Asks one-by-one if you want to add ro.config.tima=0, ro.config.knox=0, ro.securestorage.knox=false, ro.securestorage.support=false, ro.security.mdpp.ux=Disabled, and wlan.wfd.hdcp=disabled to ramdisk default.prop
Usage:
  1. Unpack your boot.img
  2. In the kitchen main menu, choose Misc Tools > Run a plugin > samextras

tar.md5 Create
by @SuperR.

NOTE: The plugin creates a tar.md5 file in alphabetical order. This may cause issues with some devices.
  • Create tar.md5 from all img, mbn, ext4, and bin files in your ROM directory.
  • Create tar.md5 from all the above except system.img, system.img.ext4, boot.img, and recovery.img
Usage:
  1. Add images to your ROM directory
  2. In the kitchen main menu, choose Misc Tools > Run a plugin > tar.md5_create

UPDATE.APP Extractor
by @SuperR.
  • Extract firmware.zip that contains UPDATE.APP
  • Extract system.img and boot.img from UPDATE.APP
This plugin uses splitupdate by JoeyJiao and updated by marcominetti. The source can be found here.

Usage:
  1. Place a firmware.zip or UPDATE.APP in your rom directory.
  2. In the kitchen main menu, choose Misc Tools > Run a plugin > updateapp

Xposed Systemless Installer
by @SuperR.
  • Add Xposed systemless to your rom
  • Remove Xposed systemless if it already exists.
Usage:
  1. Download the Xposed systemless zip of your choice into the xposed_systemless plugin directory.
  2. In the kitchen main menu, choose Misc Tools > Run a plugin > xposed_systemless


User Contributed Plugins:

KERNEL-ELF-UNPACK
by @bigrammy

A very simple kernel.elf unpack plugin.
Needs zenity to work. (Standard in Ubuntu)(Auto dependency check will be added soon)
  • Choose any kernel.elf from any directory in the popup window. (If you have a boot.elf simply rename it to kernel.elf)
  • The kernel.elf will be unpacked in a new superr_elf directory.
  • In superr_elf you will find /bootimg with: cpio-ramdisk, packed-ramdisk, kernel, kernel.elf files and the extracted /ramdisk.
  • You can move the /bootimg folder to any project so the kitchen can do any ramdisk edits you may wish.

Usage:
  1. In the kitchen main menu, choose Misc Tools > Run a plugin > kernel-elf-unpack
The Following 96 Users Say Thank You to SuperR. For This Useful Post: [ View ]
16th September 2015, 06:21 AM |#6  
SuperR.'s Avatar
OP Recognized Developer
Invisible
Thanks Meter: 4,662
 
Donate to Me
More
I do not answer support questions through PM. There are no exceptions. Post in the thread if you want help so others can give suggestions and learn from your solution

I will not answer questions if it is clear that you have not read the OP, the info posts after the OP, and searched the thread for answers. I do not have time to answer the same questions over and over. Many questions are already answered in this thread and if you want help, I expect you to try and solve it on your own before posting. If your question has not been answered in the thread, I am happy to assist in any way possible.

If I ask you to upload files, they need to be uploaded on a server that does not require registration for full speed downloads, or registration for downloads at all. Drive, Dropbox, AFH, and Mega are examples of acceptable servers. There are many other good ones, but I hope you get the point.

Thanks for understanding
The Following 67 Users Say Thank You to SuperR. For This Useful Post: [ View ]
16th September 2015, 08:29 AM |#7  
Androidwizzard's Avatar
Recognized Contributor
Thanks Meter: 6,290
 
More
Looks promissing, gonna try it asap

I suppose it to work for many devices but are there any already tested for?
The Following User Says Thank You to Androidwizzard For This Useful Post: [ View ] Gift Androidwizzard Ad-Free
16th September 2015, 09:51 AM |#9  
bcrichster's Avatar
Senior Member
Thanks Meter: 510
 
More
Its been an honor, testing this out! This deserves to be stickied!!

Sent from my N9510 using Tapatalk

---------- Post added at 04:51 AM ---------- Previous post was at 04:48 AM ----------

Quote:
Originally Posted by Androidwizzard

Looks promissing, gonna try it asap

I suppose it to work for many devices but are there any already tested for?

Zte Concord 2
Zte Warp4G

Moto E 2015

LG Exceed 2
LG Realm

Still waiting on results from:
MediaTEK VKworld (VS6050S)

[QUOTE=SuperR.;62845957]Disclaimer: I am not responsible for anything bad that may occur from the use of this tool, but I will take all the credit you can give me if it works for you




Sent from my N9510 using Tapatalk
The Following 4 Users Say Thank You to bcrichster For This Useful Post: [ View ] Gift bcrichster Ad-Free
16th September 2015, 09:58 AM |#10  
Mr Impossible's Avatar
Senior Member
Flag 305
Thanks Meter: 1,202
 
Donate to Me
More
Nice and finally something for Linux. To bad I'm out of town can't wait to test this...

Nice work

Sent from my SM-G928T using Tapatalk
The Following User Says Thank You to Mr Impossible For This Useful Post: [ View ] Gift Mr Impossible Ad-Free
16th September 2015, 10:17 AM |#11  
sawdoctor's Avatar
Forum Moderator
Thanks Meter: 9,517
 
More
[QUOTE=bcrichster;62847913]Its been an honor, testing this out! This deserves to be stickied!!

Sent from my N9510 using Tapatalk

---------- Post added at 04:51 AM ---------- Previous post was at 04:48 AM ----------


Zte Concord 2
Zte Warp4G

Moto E 2015

LG Exceed 2
LG Realm

Still waiting on results from:
MediaTEK VKworld (VS6050S)

Quote:
Originally Posted by SuperR.

Disclaimer: I am not responsible for anything bad that may occur from the use of this tool, but I will take all the credit you can give me if it works for you




Sent from my N9510 using Tapatalk

Think it needs to be in xda portal as well

Sent from my SM-N920C using Tapatalk
The Following 6 Users Say Thank You to sawdoctor For This Useful Post: [ View ] Gift sawdoctor Ad-Free
Thread Closed Subscribe to Thread

Tags
build rom, deodex marshmallow, deodex nougat, flashable zip, kitchen
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes