[ Windows / Linux / Mac ][DONATE] SuperR's Kitchen (v3.2.1.7 - 5-5-2021)

Search This thread

Sakura

Senior Member
Dec 25, 2013
327
60
IdF
Please send a fast link to your firmware that does not require registration and I will take a look.
Are you extracting anything manually or are you allowing the kitchen extract the full firmware package?

Hello
With the v3.1.6.6 I have put the firmware.zip in my project and in the Kitchen made extract.
link Mega

Thank you very much for the video link. That have very well help me :)

I have tried with v3.1.6.5 is ok.
This day I have made a new Rom N910F. I have test and I remove something in the updater-script manually because error 7 during installation.
Now is ok.

I will try to update the KitchenRs v3.1.6.6 and I tell you if I have the same problems.

Now I must try how debloat and how to remove the apk. I want a light Rom.

Thank you very much :)
 
Last edited:

SuperR.

Recognized Developer
Mar 23, 2014
2,594
8,575
Invisible
Moto E 2015
LG Nexus 5X
Hello
With the v3.1.6.6 I have put the firmware.zip in my project and in the Kitchen made extract.
link Mega

Thank you very much for the video link. That have very well help me :)

I have tried with v3.1.6.5 is ok.
This day I have made a new Rom N910F. I have test and I remove something in the updater-script manually because error 7 during installation.
Now is ok.

I will try to update the KitchenRs v3.1.6.6 and I tell you if I have the same problems.

Now I must try how debloat and how to remove the apk. I want a light Rom.

Thank you very much :)
I was able to extract your firmware in v3.1.6.6 without issue in Ubuntu 18.04.

What did you remove from the updater-script? Can you send the kitchen generated updater-script and the one that works for comparison?
 

ea3aitjr

Senior Member
Aug 30, 2008
540
850
Barcelona
Good night, @superR, first of all, thanks for your wonderful kitchen. There is a lot of work inside it.
I have the donation's windows version,and I have succesfully compiled an Oreo rom with my personal especifications without problem.
Now I'm trying to compile a pie aosp rom. All goes well, but when I get created the rom and start to flash it, I get this errors messages:

Checking config ...
location argument to mount ( ) can't be empty
process Updater finished with error: 7
Error installing file zip\' /sdcard1/xxxxx.zip\'

May be you could help me with this first chance with Pie roms.
Good work !
 

SuperR.

Recognized Developer
Mar 23, 2014
2,594
8,575
Invisible
Moto E 2015
LG Nexus 5X
Good night, @superR, first of all, thanks for your wonderful kitchen. There is a lot of work inside it.
I have the donation's windows version,and I have succesfully compiled an Oreo rom with my personal especifications without problem.
Now I'm trying to compile a pie aosp rom. All goes well, but when I get created the rom and start to flash it, I get this errors messages:

Checking config ...
location argument to mount ( ) can't be empty
process Updater finished with error: 7
Error installing file zip\' /sdcard1/xxxxx.zip\'

May be you could help me with this first chance with Pie roms.
Good work !
It seems like configure.sh is not detecting your partitions correctly. Will you send a recovery.log after flashing the ROM along with the kitchen generated updater-script from the ROM?

In the meantime, will you flash the attached zip? No need to wipe anything, this zip does not make changes. It only displays the detected by-name path for the partitions on your screen. Please let me know the on-screen output after flashing. Or, you could flash it before or after the ROM (without a reboot) and it should be in the recovery.log.
 

Attachments

  • detected_byname_display_14.zip
    365.7 KB · Views: 18

ea3aitjr

Senior Member
Aug 30, 2008
540
850
Barcelona
It seems like configure.sh is not detecting your partitions correctly. Will you send a recovery.log after flashing the ROM along with the kitchen generated updater-script from the ROM?

In the meantime, will you flash the attached zip? No need to wipe anything, this zip does not make changes. It only displays the detected by-name path for the partitions on your screen. Please let me know the on-screen output after flashing. Or, you could flash it before or after the ROM (without a reboot) and it should be in the recovery.log.

Ok, thank you @superR, for answering so fast. By the moment, i'm at work and I can't taste anything. By the way, I have tried your zip, and I leave you with screenshots, the results of it.
 

Attachments

  • Screenshot_2018-10-19-04-52-34.png
    Screenshot_2018-10-19-04-52-34.png
    100.4 KB · Views: 120
  • Screenshot_2018-10-19-04-52-43.png
    Screenshot_2018-10-19-04-52-43.png
    119.1 KB · Views: 114

MysteryIII

Senior Member
Nov 7, 2012
514
257
First of all thanks superR for your kitchen, I recently started to use it.
Is it possible to make the gapps plugin detect and use already downloaded gapps zip?
Why - Because the default download from Open Gapps is very slow, but using a download manager like JDownloader allows you parallel/chunk downloads, which in the end speeds up the download speed from 0,6 MB/s to 10 MB/s (my limit). For a 700 MB file it's a very big difference.
Right now the plugin detects current gapps zip and asks if you want to delete it. However it won't use it and always download the file again.
 

Sakura

Senior Member
Dec 25, 2013
327
60
IdF
I was able to extract your firmware in v3.1.6.6 without issue in Ubuntu 18.04.

What did you remove from the updater-script? Can you send the kitchen generated updater-script and the one that works for comparison?

Hello
Uptdater-script PJ
I have suppress #Unmount perhaps it is not necessary ?
Is it better to install the kitchen with Ubuntu. I have LinuxMint 19 ?

I have already done several installation of Roms Customs XDA and I have never had this problem before.

When I made the installation with normal updater-script error 7 "This package is for a "trlte" devices this is a "trltexx"
My phone N910F single SIM see PJ
How you made spoiler ?

Thank you for your help
 

Attachments

  • photo_2018-10-19_10-51-04.jpg
    photo_2018-10-19_10-51-04.jpg
    72.6 KB · Views: 96
  • updater-script.txt
    2.5 KB · Views: 32

SuperR.

Recognized Developer
Mar 23, 2014
2,594
8,575
Invisible
Moto E 2015
LG Nexus 5X
Ok, thank you @superR, for answering so fast. By the moment, i'm at work and I can't taste anything. By the way, I have tried your zip, and I leave you with screenshots, the results of it.
Looks like configure.sh is detecting the partitions properly. I have no idea why the mount command was empty. I will wait to see the updater-scripts.

First of all thanks superR for your kitchen, I recently started to use it.
Is it possible to make the gapps plugin detect and use already downloaded gapps zip?
Why - Because the default download from Open Gapps is very slow, but using a download manager like JDownloader allows you parallel/chunk downloads, which in the end speeds up the download speed from 0,6 MB/s to 10 MB/s (my limit). For a 700 MB file it's a very big difference.
Right now the plugin detects current gapps zip and asks if you want to delete it. However it won't use it and always download the file again.
It should be saving and using saved gapps. I will take a look.

EDIT: @MysteryIII - I have updated the gapps plugin, but I did not change the part that you referred to. That part seems to be working properly. I did notice that when I tried to download gapps for Android Pie it downloaded the wrong file. This is now fixed. It was due to the version syntax of Android vs OpenGapps. Android uses version 9 while OpenGapps uses 9.0.

If you create a new directory kitchen/tools/gapps and add the correct gapps zip in that directory, the gapps plugin will use it instead of downloading a new one. It must be the correct arch (arm, arm64, etc) and the correct version for your ROM or it will ask you to download a new one.

Hello
Uptdater-script PJ
I have suppress #Unmount perhaps it is not necessary ?
Is it better to install the kitchen with Ubuntu. I have LinuxMint 19 ?

I have already done several installation of Roms Customs XDA and I have never had this problem before.

When I made the installation with normal updater-script error 7 "This package is for a "trlte" devices this is a "trltexx"
My phone N910F single SIM see PJ
How you made spoiler ?

Thank you for your help
Your issue is device asserts. All you need to do is add "trltexx" in the kitchen asserts menu.
Mint 19 is good.

@SuperR. I made some fix for the italian translation, please use it, the goole translation is really bad
Thank you :) Italian language updated on the server.

I have added you as the Italian language maintainer. When you log in to the downloads page, you will now see "Language upload".
 
Last edited:

Sakura

Senior Member
Dec 25, 2013
327
60
IdF
Your issue is device asserts. All you need to do is add "trltexx" in the kitchen asserts menu.
Mint 19 is good.

How add trltexx in the kitchen asserts menu ?
Thank you for your help

---------- Post added at 07:12 PM ---------- Previous post was at 07:06 PM ----------

Your issue is device asserts. All you need to do is add "trltexx" in the kitchen asserts menu.
Mint 19 is good.

Hello
Can you tell me how I must make to add "trltexx" in the kitchen asserts menu. ?
Please, can you give me exemple :)

Thank you for your help
 

Sakura

Senior Member
Dec 25, 2013
327
60
IdF
ROM Tools > Asserts Menu > 1) Add/Remove Device (CURRENT: trlte)

Then add "trltexx" as shown in the screenshot below. Press ENTER and you are ready to go.

assert_example.png

Thank you very much for your help. I add this in the kitchen and test.

I have made a new rom and it is ok to add trltexx in Asserts ! See PJ

  • I have a probleme selection Root
    I choice SuperSu , add Busybox
    but when after reboot system I have not SuperSu and busybox in my application. Why ?
  • Is it possible to add twrp in the kitchen when I make a Rom ? and how I can ?
  • I have try debloat to suppress application that I don't want but is not good. I must finder why
  • If I go in recovery , normal recovery and my SD Ext is not available ?
  • I must install via odin : cf-root and twrp to continue

Thank you very much :)

Good day to you :)
 

Attachments

  • updater-script.txt
    2.6 KB · Views: 6
Last edited:

filipepferraz

Member
Oct 17, 2010
33
44
It's possible to force write in both _a and _b partitions? I'm trying to generate a zip to update 4 partitions (boot, logo, vendor and system). When I recover the partitions with twrp works, but if I flash from zip get boot loop or is not installed.

Any tip for Motorola a/b partitions flash procedure?
 

SuperR.

Recognized Developer
Mar 23, 2014
2,594
8,575
Invisible
Moto E 2015
LG Nexus 5X
Thank you very much for your help. I add this in the kitchen and test.

I have made a new rom and it is ok to add trltexx in Asserts ! See PJ

  • I have a probleme selection Root
    I choice SuperSu , add Busybox
    but when after reboot system I have not SuperSu and busybox in my application. Why ?
  • Is it possible to add twrp in the kitchen when I make a Rom ? and how I can ?
  • I have try debloat to suppress application that I don't want but is not good. I must finder why
  • If I go in recovery , normal recovery and my SD Ext is not available ?
  • I must install via odin : cf-root and twrp to continue

Thank you very much :)

Good day to you :)
No idea why SuperSU is not installed after flashing it. Did it actually flash? A recovery.log after flashing might show what is happening. However, you may want to use Magisk. SuperSU does not seem to be maintained anymore.

It is possible to add TWRP to your ROM, but I don't recommend it. How are users flashing your ROM if they don't already have a custom recovery?

No clue why your debloat is not good. I don't know what you removed. Furthermore, what you remove from your ROM is beyond the scope of this thread. I only support what the kitchen does.

The kitchen does not do anything with recovery besides unpack/repack and create a flashable recovery.zip.

I don't know anything about odin or cf-root.

It's possible to force write in both _a and _b partitions? I'm trying to generate a zip to update 4 partitions (boot, logo, vendor and system). When I recover the partitions with twrp works, but if I flash from zip get boot loop or is not installed.

Any tip for Motorola a/b partitions flash procedure?
If logo.img is an ext4 image file, you can include it the same way you include vendor. If not, you can do one of 2 things:
  1. Manually add logo.img to your updater-script and rom.zip
  2. Use the partition_zip plugin to create a flashable zip with logo.img (convert to update binary: YES). Then use the mods_install plugin to add it to your ROM.
As far as I know, the kitchen handles a/b devices properly. However, I have never owned one so I have no personal experience.
 

omeh2003

New member
Apr 18, 2015
3
0
Saint-Petersburg
Network connect

Sorry if this is a known "issue". During program updates. Sometimes it apparently loses connection to the network and does not handle this situation.
kitchen-Update.png


Hanging until you interrupt her CTR-C. Not very nice :)
kitchen2.png


Maybe some timeouts to make or check that the download really is?


I have another question about another.
Situation:
1) I unpacked the boot.img.
2) Made that wanted to. Made changes.
3) And I want when packing used my keys for signing. Is it possible to make existing functionality?
If possible, is it possible to specify different keys for boot, system etc partitions.?
Thanks. Excuse me for my English ;)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    v3.2.1.7 has been released :)

    Details in the release post.
    3
    It happens just opening the plug-in
    It does not crash for me on a fresh v3.2.1.7 kitchen install with a fresh img_tools plugin install. Please try this. If it still crashes, please try again on v3.2.1.6. As far as I can remember, nothing changed with this plugin or the way the kitchen runs it since then.

    Scratch that, just found the problem. It happens when using offline authorization. I will look into this and update as needed.

    edit: Unfortunately, this fix needs a kitchen update, not a plugin update. For now, you can use the plugin if you disable offline authorization before running the plugin. It will be fixed in the next update, sorry for the inconvenience :)
    3
    It does not crash for me on a fresh v3.2.1.7 kitchen install with a fresh img_tools plugin install. Please try this. If it still crashes, please try again on v3.2.1.6. As far as I can remember, nothing changed with this plugin or the way the kitchen runs it since then.

    Scratch that, just found the problem. It happens when using offline authorization. I will look into this and update as needed.

    edit: Unfortunately, this fix needs a kitchen update, not a plugin update. For now, you can use the plugin if you disable offline authorization before running the plugin. It will be fixed in the next update, sorry for the inconvenience :)
    After messing around I figured out it was the offline authorization as well. Its not a big deal its an easy fix just disabling offline authorization. I dont really use it anyways Im always connected to internet. Thank You for checking into it I appreciate your work alot!
    2
    Awww... :(

    View attachment 5280329

    cat img_build.log yields:
    View attachment 5280331

    Which is odd. This has worked before. This exact rom.
    I must have installed something or done something that has messed things up.
    And I have no idea...
    I think this is a new issue in v3.2.1.5. For now, you can try building in v3.2.1.4. If it works properly, I think it will be fixed in the next update.

    It turns out that the tune2fs binary included in the kitchen gives a segmentation fault on some machines, no idea why (thanks @edzamber for pointing it out). tune2fs in the kitchen is responsible for reading EXT4 information (including EXT4 features) from an img file. In v3.2.1.4, there was a backup in place to use default features if tune2fs was not able to complete its job for any reason. When I added the include/exclude features option in v3.2.1.5, somehow I broke the default features being used. Without tune2fs and without default features, the build will fail.

    You can check to see if tune2fs is giving you a segmentation fault by running the img_tools plugin option 6. If you see the segmentation fault, this is almost certainly your issue. I have eliminated tune2fs in the next update by writing a python implementation to accomplish the same functionality. I have also fixed the defaults to work again if required. This should solve the problem :)
    2
    Haha, that's made me chuckle for a few mins :)

    If you wouldn't mind, could you load dde up in a VM and give it a test for me as I can't use the kitchen for it and now have normal ubuntu set up again?

    Here's a link to dde....
    And here's a link to my FW...

    Thanks again for your help mate,
    Nathan
    This took way too long lol. I probably should have said no to this request ;)

    However, I did install ubuntuDDE 20.10 in a VM, and everything works perfectly. No issues building ext4 img files after extraction. Here are the steps I took to prepare the new OS for kitchen use:

    Installed the OS in a VM with a 20 GB drive mounted on /. Attached an extra 50 GB drive for the kitchen. Both are formatted EXT4. During install, it told me I was running in a VM and gave me 2 options for the display, Effects mode, and Normal Mode. I chose Effects mode.

    Once installed, I switched over to dark mode immediately. All that white was killing me :D I also moved the panel to the left like it is in Ubuntu. I know these details probably don't matter at all, but I want to be thorough.

    I opened a terminal to update the OS.
    Code:
    sudo apt update
    sudo apt dist-upgrade
    I rebooted the VM, and opened the terminal again to install Java
    Code:
    sudo apt install default-jre
    I downloaded a fresh v3.2.1.6 kitchen zip into the 50 GB drive, and opened a terminal there.
    Code:
    unzip SuperRs-Kitchen_Linux-64_v3.2.1.6.zip
    ./superr
    I downloaded your firmware into a new project, and chose menu option 4 to extract for new ROM.

    Once completed, I went into the build menu and chose build ext4 img, chose raw, chose #4 partition.img for the size.

    Final thoughts:
    The only thing I can suggest is make sure you are NOT using make_ext4fs. The binary being used to build is visible when building in the kitchen. It will either say "(make_ext4fs)" or "(e2fsdroid)". You want it to say e2fsdroid. Otherwise, I have no idea what is going on with your machine. Two things are certain, it is not a Kitchen or OS issue. I hope you get it figured out :)
  • 158
    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 :D

    main_linux.png


    main_windows1.png


    Please read the troubleshooting in post #4 of the standard kitchen thread before asking for help.
    Please indicate your OS when asking for help.
    Please send a fast link to your firmware that does not require registration when asking for help.


    Donate Release Thread
    Donate Changelog

    Donate version Info
    Access to the donate version of the kitchen requires a minimum donation of $20.00 US. See terms and conditions below.


    Terms and Conditions for SuperR's Kitchen Donate version:

    Allowed:
    • An active kitchen account grants usage privileges of the donate kitchen and the sr-code.com website.
    • One kitchen account provides kitchen access to one user, on one operating system, on one personal computer.

    Not allowed:
    • Sharing your kitchen account and/or privileges.
    • Transfer and/or resale of your kitchen account.
    • Suspicious activity.

    Definition:
    Suspicious activity - Decided exclusively by SuperR at the time of an incident.

    Resolution:
    If anything from the not allowed list occurs, your kitchen account will be disabled.

    See this post for more details on the Single PC license.

    Donation Options:
    1. Paypal through my website
    2. US Amazon eGift card (email address found here)

    Once you donate, register for a Kitchen account (free) and send a PM with your username and the email address used for donation. I will add you to the database and you will then have access to the donate version download section. Follow the steps below to get it downloaded and running :)

    EXISTING DONORS: GitLab is no longer used. See this post if you previously had GitLab access and are unable to download/update/install.

    NOTE: The Plugin Repo is included in the Donate kitchen. If you wish to see a description of the available plugins, they can be found here.

    Dependencies:

    WINDOWS:
    LINUX/MAC:
    • Java 8 or higher
    • Python (to run the launcher (could be bypassed by running tools/source/superr in the terminal from the main kitchen directory))

    Download/Install/Run:

    Free version:

    WSL2 (Windows 10):

    Linux/Mac (Terminal):
    1. Download the kitchen.zip from the download page sent through PM. Extract to a new directory.
    2. Enter the following command where "/location/of/kitchen" is the directory where the kitchen lives:
      Code:
      /location/of/kitchen/superr

    Windows:

    NOTE: The native Windows version has reached end of life. Consider running the Linux kitchen in WSL2 using the guide above.​
    1. Download the kitchen.zip from the download page sent through PM. Extract to a new directory.
    2. Make sure Java listed above is installed and in your system environment PATH (Check Google for the many guides on this if you need help)
    3. Double click superr.exe in newly extracted kitchen directory.

    NOTE: After you start the kitchen, it will ask you for your Kitchen username and password. Make sure you enter it correctly or it will not work. Thanks for the donation, enjoy :)

    Known Issues/Limitations:

    Linux:
    • None
    WSL2:
    • None
    WSL1:
    • Crashes with xattr not defined error when unpacking some img files due to a bug in the Python ext4 module.
    Mac:
    • Does not use e2fsdroid for building img files as I am not able to compile it for Mac so far.
    Windows:
    • No longer being updated. v3.2.1.3 is the last version. The Linux kitchen runs perfectly in WSL.
    • Does not use e2fsdroid for building img files as I am not able to compile it for Windows.
    • Crashes with xattr not defined error when unpacking some img files due to a bug in the Python ext4 module.
    • If you run Windows as administrator and have issues with the Boot Menu, please see this post.
    • If superr.exe gets removed by your antivirus program, whitelist the kitchen directory in your antivirus program.
    • If the kitchen can't find an internet connection, try whitelisting sr-code.com in your antivirus browsing security. If it still does not find a connection, try using a VPN.
    • The colors are not perfect due to Windows not supporting ASCII escape codes by default. If you want it to look more like Linux, you can run the Linux version in WSL (formerly known as "Bash on Ubuntu on Windows").

    Video tutorials by @chevycam94

    Credits:

    @osm0sis - For Busybox Installer and Android Image Kitchen
    @Chainfire - For SuperSU
    @JesusFreke - For [Bak]smali
    @nkk71 - For TWRP minzip patch, and make_ext4fs improvements
    @Captain_Throwback - For providing a pre-compiled update-binary with the minzip patch and squashing bugs
    @cubinator - For Python ext4 module
    @_riddle - For oat2dex
    @iBotPeaches - For Apktool
    @AOSP - For zipalign, aapt, adb, img2simg, simg2img, make_ext4fs
    @xpirt - for img2sdat & sdat2img
    @yoanf_26 - For French translation
    @anestisb - For vdexExtractor
    @iuss - For payload_dumper.py


    Contributors
    SuperR.

    Version Information
    Status:
    Beta

    Created 2018-11-16
    62
    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
    • Zips that contain payload.bin
    • Samsung firmware zips that contain tar.md5 file
    • Official Nexus/Pixel firmware tgz/zip
    • Official Nexus/Pixel preview tgz/zip
    • 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:
    • Android 10 ROMs
    • Pie ROMs
    • Oreo ROMs
    • Nougat ROMs
    • Marshmallow ROMs
    • Lollipop ROMs
    • KitKat and earlier ROMs
    *Root features:
    • Root/unroot
    • Choose Magisk
    • Choose SuperSU
    • Add other root zips to /tools/root/root_zips directory
    • Choose system OR systemless root for M+ and Samsung 5.1.1 roms
    • Add/remove su.d support
    *Boot features:
    • Unpack/repack boot/recovery img (Big Thanks to @osm0sis for Android Image Kitchen!!!)
    • Add/remove insecure boot
    • Remove dm-verity
    • Add/remove forceencrypt
    *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.
    • Update to the latest version
    • Option to check for updates when the kitchen starts
    *Pack/Unpack super.img
    *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
    *Cross-platform: Windows and Linux are fully supported
    *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.
    *Ability to choose an apk, decompile, modify it manually, recompile, sign, and move it back to where it came from.
    *Plugin support - Add your own script to the /kitchen/tools/plugins directory and the kitchen will run it for you.
    *AutoROM - Unattended ROM development using a config file.
    43
    USAGE:

    1. Run the kitchen (instructions in OP)
    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!
    10
    Update on Android Pie deodex:

    anestisb has finished Android P support for vdexExtractor. Android Pie introduced a new dex format, Compact Dex (cdex). anestisb created a new tool to convert cdex to standard dex which is required for Android Pie deodex. Unfortunately, the new tool will not currently work on Windows as it requires many AOSP dependencies and Google does not support compiling AOSP on Windows. It will only work on Linux and Mac. There are many Windows kitchen users, and I have no idea what to do about it.

    More information can be found here.

    If anyone can help, please do. Thanks :)

    EDIT: The Windows aapt.exe binary was not functioning properly. I have reverted to the previous aapt.exe that works. The win_tools package has been updated on the server. Sorry for the inconvenience.

    If you are on Windows and have already updated to v3.1.6.3, you can find the working aapt.exe here. Replace kitchen\tools\win_tools\aapt.exe with the one in the zip.
    9
    Hello everyone :)

    The kitchen is moving to a new server. There could be some strange behavior if you reset a PC or register a new account right now. The DNS can take up to 48 hours to propagate globally. If you reset your PC now, it may result in failing authentication after the DNS is propagated. You can reset again if this is the case.

    I do not expect any problems or downtime, but this information serves as a warning just in case :)
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone