• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[LINUX][FREE] SuperR's Kitchen (v1.2.1.2 - 7-24-20)

Search This thread

SuperR.

Recognized Developer
Mar 23, 2014
2,630
8,685
Invisible
Moto E 2015
LG Nexus 5X
hi, when attempting to unpack my boot image i get this error

Code:
There is no ramdisk in this boot.img.

any insight?

i attached the boot.img and build.prop to this post
You are working on a system-as-root device, so the ramdisk is in the system partition. The boot.img is actually recovery on these devices.
any one help me for building process of the rom with SuperR 1.2..1.2
i can't build in original image to flash with twrp
It is likely the free kitchen does not have all the features you need to get your img to boot. The donate kitchen will probably fix this issue.
Hy @SuperR.

I've tried u'r kitchen using WSL and phyton 6.7 it gave me error "platform not supported"
it there any solution?
The free kitchen does not work in WSL, only in native Linux. If you want to run the kitchen in WSL, the donate kitchen will solve this for you :)
 

Kartun

Member
Mar 4, 2008
32
4
Moscow
Hello.

I've problem with signing image on LinuxMint 20

java --version
openjdk 14.0.2 2020-07-14
OpenJDK Runtime Environment (build 14.0.2+12-Ubuntu-120.04)
OpenJDK 64-Bit Server VM (build 14.0.2+12-Ubuntu-120.04, mixed mode, sharing)


Exception in thread "main" java.lang.NoClassDefFoundError: sun/misc/BASE64Encoder at com.android.signapk.SignApk.addDigestsToManifest(SignApk.java:182) at com.android.signapk.SignApk.main(SignApk.java:468) Caused by: java.lang.ClassNotFoundException: sun.misc.BASE64Encoder at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:602) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522) ... 2 more
 

HemanthJabalpuri

Senior Member
It is because Java 9+ does not have that Base64 of sun package.
or
will fix that
 

Samir2298

Senior Member
Apr 3, 2015
210
20
Hey guys this kitchen works fine if I deodex rom BUT with an odexed ROM it bootloops. What could be the problem? I am on Marshmallow.
 
Last edited:

The_Muttster

New member
Mar 19, 2013
1
0
Edinburgh
HI all,

So my tech goal for 2021 is to learn more about Android (I work in DFIR) and thought I'd take a look at learning how to create custom ROMs. Recently, I got a new phone (Ulefone Armor 10) and since the manufacturer releases the updates on their site, I thought that would be a good place to start.

I've watched the videos, I've installed the free version with the ubuntu kitchen ISO and getting stuck in. So the image I'm using is this one for Android 10. Extracting it seems easy enough but when I just try to rebuild it with no changes, I get the following error:


Code:
vendor.img build failed. Directory will not fit:
img size: 614MB, dir size: 629MB

Any ideas?
 
Last edited:

XxshaokhonxX

New member
Apr 1, 2015
2
0
@SuperR. Hello I have been trying multiple times tonight and I am tired of it to install a slightly modifed kernel/ rom to my tablet, yes it is a very old tablet from 2013 and is running android 4.2.2.

The ROM I am using is a custom rom and it is an AOKP 4.2 ported to the HSG1279 hanspree tablet, it works fine, the recovery I am using is also ported over and it is CWM based recovery v6.0.3.3, but I have also tried a ported TWRP version. But I keep running into the same problem and searching it up proves no results, whenever I try to install a custom ROM that I have modified /kernel I keep getting the Status 0 error and I am stuck.

The kitchen version I am using is the free linux one which I am using on ubuntu 20, the perm method I am using is the set_perm one due to the tablet only having android 4.2.2 on it. All I did to the kernel is I made it not secure so I can use adb's sideload function in recovery. This is the zip file for the kernel which has been modified, if you need the original one please let me know and I will happily attach it. I hope this can be fixed as I am hoping to port some custom ROM's/ kernels to this old tablet to get better features on it. I have also looked in the edify scripts to see for anomalies and I have noticed that certain entries have set_metadata_recursive at the beginning when I chosen to use set_perms. This is all the information that I think relate to the problem but if you need anymore let me know.

Might I add that I am running the free version on an ubuntu virtual machine as my base operating system is windows and I unfortunately have no money to purchase the donator version, but whenever I can I might purchase the donator version if I do not give up trying to port roms and kernels to this old tablet
 

Attachments

  • AOKP-kernel.zip
    5.3 MB · Views: 2

io2345

Senior Member
Sep 10, 2014
188
92
Tried it several times, but with all settings I made the installation process on the phone ends immediately with a red message "Updater process ended with ERROR: 7. The last line before says "file_getprop: failed to stat "tmp/config": No such file or directory".
There is no directory "tmp", not in the original ROM (which installs fine), nor in the "kitchened" ROM. Tried to remove ROOT from the ROM, if that information helps...
Maybe you can tell me, what the "Unroot" does in background, then I could do it manually.
 
Last edited:

Terrierrok

New member
Apr 29, 2018
2
0
Hi! I was trying to use your tool but sadly when im about to pack the rom in a zip i always get this error while packing system.img

error: build_directory_structure: cannot lookup security context for /cust
Creating filesystem with parameters:
Size: 4831838208
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 18432
Label: system
Blocks: 1179648
Block groups: 36
Reserved block group size: 287

Sorry, im newbie in this world of android and im trying tu customize a MIUI ROM. Thx for your help.

Heres the log attached (i did multiple attempts, hehe)
 

Attachments

  • img_build.log
    2 KB · Views: 1

SuperR.

Recognized Developer
Mar 23, 2014
2,630
8,685
Invisible
Moto E 2015
LG Nexus 5X
HI all,

So my tech goal for 2021 is to learn more about Android (I work in DFIR) and thought I'd take a look at learning how to create custom ROMs. Recently, I got a new phone (Ulefone Armor 10) and since the manufacturer releases the updates on their site, I thought that would be a good place to start.

I've watched the videos, I've installed the free version with the ubuntu kitchen ISO and getting stuck in. So the image I'm using is this one for Android 10. Extracting it seems easy enough but when I just try to rebuild it with no changes, I get the following error:


Code:
vendor.img build failed. Directory will not fit:
img size: 614MB, dir size: 629MB

Any ideas?
You will need to remove some files from the project "vendor" directory so it will fit. The donate kitchen will likely solve this issue and build without needing to remove files.
@SuperR. Hello I have been trying multiple times tonight and I am tired of it to install a slightly modifed kernel/ rom to my tablet, yes it is a very old tablet from 2013 and is running android 4.2.2.

The ROM I am using is a custom rom and it is an AOKP 4.2 ported to the HSG1279 hanspree tablet, it works fine, the recovery I am using is also ported over and it is CWM based recovery v6.0.3.3, but I have also tried a ported TWRP version. But I keep running into the same problem and searching it up proves no results, whenever I try to install a custom ROM that I have modified /kernel I keep getting the Status 0 error and I am stuck.

The kitchen version I am using is the free linux one which I am using on ubuntu 20, the perm method I am using is the set_perm one due to the tablet only having android 4.2.2 on it. All I did to the kernel is I made it not secure so I can use adb's sideload function in recovery. This is the zip file for the kernel which has been modified, if you need the original one please let me know and I will happily attach it. I hope this can be fixed as I am hoping to port some custom ROM's/ kernels to this old tablet to get better features on it. I have also looked in the edify scripts to see for anomalies and I have noticed that certain entries have set_metadata_recursive at the beginning when I chosen to use set_perms. This is all the information that I think relate to the problem but if you need anymore let me know.

Might I add that I am running the free version on an ubuntu virtual machine as my base operating system is windows and I unfortunately have no money to purchase the donator version, but whenever I can I might purchase the donator version if I do not give up trying to port roms and kernels to this old tablet
You should be able to use set_metadata perm type for KitKat 4.2.2. I believe this Android version uses file contexts, which is the main difference between set_perm and set_metadata. Unfortunately I am not a kernel expert, but if unpacking or packing boot.img is the problem you would need to post on the AIK (Android Image Kitchen thread). SuperR's Kitchen uses AIK for boot.img unpack/repack.
Tried it several times, but with all settings I made the installation process on the phone ends immediately with a red message "Updater process ended with ERROR: 7. The last line before says "file_getprop: failed to stat "tmp/config": No such file or directory".
There is no directory "tmp", not in the original ROM (which installs fine), nor in the "kitchened" ROM. Tried to remove ROOT from the ROM, if that information helps...
Maybe you can tell me, what the "Unroot" does in background, then I could do it manually.
If you are building a ROM for Android 10+, building a full ROM zip in the kitchen will probably not work. I have not been able to figure this out yet because I do not have a device to test on.

Unroot will remove root files from the extracted firmware in the kitchen project you are wrking on. It removes the su binary, superuser.apk, SuperSU.apk, etc.
can't set metadata permission on oreo samsung firmware
This is not enough information to help you.
Hi! I was trying to use your tool but sadly when im about to pack the rom in a zip i always get this error while packing system.img

error: build_directory_structure: cannot lookup security context for /cust
Creating filesystem with parameters:
Size: 4831838208
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 18432
Label: system
Blocks: 1179648
Block groups: 36
Reserved block group size: 287

Sorry, im newbie in this world of android and im trying tu customize a MIUI ROM. Thx for your help.

Heres the log attached (i did multiple attempts, hehe)
The free kitchen uses make_ext4fs to build ext4 img files. make_ext4fs is out of date and may not work properly for Android 10+. The donate kitchen will solve this problem 100%.
 

datecasp

Member
Apr 5, 2021
35
8
Hi @SuperR.
I'm using the kitchen (last version in Ubuntu 20.04) trying to modify a ROM from smg355H to smg355HN. It's crDroid 5.1.1 and I have modify the build.prop file to adjust some parameters to the device and the asserts.
When I go to install it with TWRP I get an error with file getprop /tmp directory doesn't exists
Any idea?
TIA!

**EDIT** Solved! I was a problem with the metadata. Must set to "set_metadata" and I was using "Sparse". Now I'm stucked in bootloop to recovery so I must still working in the port...
 
Last edited:

_D.X.Y

New member
Jul 16, 2021
2
0
I can solve the problem of normally packaging the dynamic partition of Android 10-11 without WSL and wsl2. It is readable and writable. There is no problem with permissions. Can you send me a complete kitchen under windows for free?
 

dataghost2014

Member
Jan 20, 2016
35
8
I can solve the problem of normally packaging the dynamic partition of Android 10-11 without WSL and wsl2. It is readable and writable. There is no problem with permissions. Can you send me a complete kitchen under windows for free?
Dude, stop asking for free handouts, my friend here working on this project puts his heart and soul into, if only you knew the hours he has put into this stuff.... And no its not that easy, as soon as you make changes, the OS recognizes that and is blocked, things are being worked on, but its not the snap of a finger. If you want to do it, get your hands on SDK like I do, and build from the ground up. And please do not ask if we can give you SDK.... Does not work like that, talk to a manufacturer if you have one, it burns my ass, the people asking for free handouts all the time when a dev puts thousands of hours into stuff like this....
 
  • Like
Reactions: CrashTestDroid

_D.X.Y

New member
Jul 16, 2021
2
0
伙计,别再要求免费施舍了,我在这个项目上工作的朋友全心全意地投入其中,只要你知道他在这些东西上投入的时间......发生变化,操作系统识别出并被阻止,事情正在处理中,但这不是弹指之间。如果您想这样做,请像我一样使用 SDK,然后从头开始构建。并且请不要问我们是否可以给你 SDK .... 那样不行,如果你有的话,和制造商谈谈,它烧伤我的屁股,当开发人员投入数千个时,人们总是要求免费讲义几个小时到这样的事情......
Sorry to interrupt. It doesn't matter if you don't need help,
 

Top Liked Posts

  • There are no posts matching your filters.
  • 113
    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
    smile.gif


    main_free.png




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

    Free Changelog

    Download/Install

    Donate version for Windows/Mac/Linux/WSL:
    Dedicated thread found here

    Free Kitchen (Linux terminal):
    **NOTE: The free kitchen will not work in WSL**
    1. Download the kitchen.zip from here. Extract to a new directory.
    2. Enter the following commands one by one pressing ENTER after each line where "/location/of/kitchen" is the directory where the kitchen lives:
      Code:
      cd /location/of/kitchen
      ./superr

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

    Video tutorials by @chevycam94

    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, aapt, img2simg, simg2img, make_ext4fs
    @xpirt - for img2sdat
    @bcrichster - For extensive testing


    XDA:DevDB Information
    SuperR's Kitchen, Tool/Utility for the XDA Community Apps

    Contributors
    SuperR.

    Version Information
    Status:
    Stable

    Created 2017-04-27
    Last Updated 2020-07-24
    33
    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 :)
    32
    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.


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

    Language Files (translations)
    English - Default/Included in the kitchen

    Download additional 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?
    CYGWIN is not supported and will not work. Try the donate kitchen for Windows, Linux, and Mac.

    WSL (Bash on Ubuntu on Windows)
    WSL is not supported in the free kitchen and will not work. Try the donate kitchen for Windows, Linux, and Mac.

    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. The free kitchen uses AOSP permissions/capabilities when building system.img. If your device requires different permissions, this method will not work for you in the free kitchen.

    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. The free kitchen uses AOSP permissions/capabilities when building system.img. If your device requires different permissions, this method will not work for you in the free kitchen.

    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.

    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 and Magisk.zip in the kitchen with any flashable SuperSU/Magisk version you want. It is located in kitchen/tools/root/root_zips. Delete the one that is there (if it exists) 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.

    I added root and busybox but there is no su or busybox in my project. Why?
    The kitchen does not add Busybox or SuperSU/Magisk 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 OR kitchen/superr_project/00_project_files/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
    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 :)
    29
    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 Pixel/Nexus firmware tgz
    • Official Pixel/Nexus preview tgz
    • SpreadTrum firmware that includes a pac file
    • 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
    • Recovery
    • Media
    • app, priv-app, and framework
    *Deodex the following:
    • Pie ROMs
    • Oreo ROMs
    • Nougat ROMs
    • Marshmallow ROMs
    • Lollipop ROMs
    • KitKat and earlier ROMs
    *Root features:
    • Root/unroot
    • Choose SuperSU or Magisk zip (add other versions to /tools/root/root_zips directory)
    • Choose system OR systemless root for M+ and Samsung 5.1.1 roms (SuperSU only)
    *Boot features:
    • Unpack/repack boot/recovery img (Big Thanks to @osm0sis for mkbootimg source!!!)
    • Add/remove su.d support
    • Add/remove insecure boot
    • Remove dm-verity
    • 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.
    • Incremental update for updating the most recent previous version
    • 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:
    • Cross-platform - Windows, WSL, Macos, Linux
    • tarfs - Get original permissions, contexts, and capabilities from tar/win backups.
    • Create system.img with identical permissions, contexts, and capabilities as the original system.img or tar/win backup.
    • Plugins - Probably the best part! Currently over 20 extra features and growing
    • Root - Use a custom root zip (not the included Magisk or SuperSU)
    • Custom directory - can be included in your ROM and flashed to a specified partition
    • Custom Signature - No Built with SuperR's Kitchen, anywhere, plus add your own
    • Custom Build Display in About Phone, or leave it as default
    • AutoROM - Automation for ROM creatiion using a congig file (there's a plugin for that)
    • Convert updater-script to an update-binary script
    • No mounting img files. One less thing requiring your password and interrupting extraction.
    • Upload support.zips and device.zip directly from the kitchen for review
    • Download language files directly from the kitchen
    • Restore original boot.img after modifying and repacking
    • Remove asserts from the updater-script
    • Configurable compression level for packing zips
    • Remove all placeholder tags (#ASSERT, #SYM, #PERM, etc.) before packing the ROM
    • Create ext4 img file from any partition you include in your ROM.
    • zipalign without building ROM
    • Fix ext4.img files automatically if block count is higher than actual blocks
    15
    v1.2.0.8

    Changes:
    • Fixed crash if a file does not exist when validating kitchen files.
    • Fixed deleting projects from the main menu.
    • Fixed crash if smali.zip does not download properly.
    • Create new apk including the deodexed classes if apk does not exist when deodexing.
    • Added screen_clear config option that will use either no screen clearing, or tput clear.
    • Removed use_tput config option in favor of the new screen_clear config option.
    • Automatically fix geometry errors in ext4 img files during extraction.
    • Fixed Samsung devices pulling img files from the device through adb (hopefully).
    • Fixed lag during extraction after entering your rom name and after choosing the perm type.
    • Fixed kitchen updater for future updates.
    • Many other small fixes.

    Screen Clearing
    If you do nothing, the default is ascii escape codes that clear the screen. This has been the default since v1.2.0.0. The Bash version uses tput clear. If you are not having screen clearing issues, it is recommended that you do nothing.

    In kitchen/tools/srk.conf, you can add a line to change the screen clearing behavior:
    • Use "tput clear"
      Code:
      screen_clear=1
    • Do not clear the screen at all and display a new page below the old page
      Code:
      screen_clear=None
    • "use_tput=1" is no longer available, as "screen_clear=1" does the same thing.
    There is no need for a restart. After saving srk.conf with the new line, the change will be seen immediately.