TABLE OF CONTENTS
- 1 RELATED POSTS
- 2 Best Microsoft Office 2019 Professional Plus Preactivated [Latest]
- 3 Carliv Image Kitchen Tools v1.3 for Windows Free Download
- 4 Phoenix OS Toolbox v3 NB Edition for Windows Free Download
- 5 What’s Android Image Kitchen?
- 6 Which Platform Supported?
- 7 Features:
- 8 Changelogs:
- 9 Minimum System Required:
- 10 File Info:
- 11 Download Link:
- 12 Instructions:
Android Image Kitchen is able to completely unpack, create and repack kernel, ramdisk, and boot.img of Android and Android x86 operating systems. Android Image Kitchen is best for boot.img and recovery.img unpacking and repacking tool. Android Image Kitchen free download for windows 7/8.1/10 with x64 & x86 both bit version.
What’s Android Image Kitchen?
Android Image Kitchen is a tool used to unpack and repack Android kernel, ramdisk, & boot.img. Android Image Kitchen is capable of unpacking and repacking all types of Android boot images, it is able to unpack, crate and repack boot images of the Android x86 operating system.
Which Platform Supported?
Android Image Kitchen Tools are available for Android, Windows, and Linux operating systems. It performs very well on all three operating systems. Although Android Image Kitchen is a bit weak on the Android platform, it works very well on Windows and Linux operating systems. Moreover, if you want to use Android Image Kitchen on the Android operating system, it is not possible to use it without root permission.
– boot.img unpacker
– boot.img repacker
– recovery.img unpacker
– recovery.img repacker
– android x86 boot.img maker
Android Image Kitchen v3.6:
– add U-Boot RAMDisk uImage support
– extend missing sudo message to include adding it as an antivirus exception
– update BootSignature*.jar compiles to support AOSP boot image hdr v1 and v2
– add a faster footer magic search to attempt first
– add AVBv2 detection on unpacking to help differentiate between AVBv1 and AVBv2 for users
– fix Windows Sudo executable check
– fix ramdisk ‘Access Denied’ regression from the non-user-owned folder by granting permission to the current user
– update mkbootimg, unpackbootimg and mboot binaries from my repos
– update mkimage and dump image binaries (2019.07)
– update lz4 binary (1.9.2)
– update slimmed magic file (from file 5.37) with my own fixes
– update to the latest Cygwin binaries and libraries
Minimum System Required:
• Requires: Windows 7/8.1/10
• Bit: 32 bit or 64 bit (Both)
• Ram: Any Size
• Graphic: No need
• Name: Android Image Kitchen
• Version: v3.7
• Status: Stable
• Main Developer: osm0sis
• File Size: 7.18 MB
• File Type: zip
• Uploader: Tips Lab Team
• Language Supported: English
2) Either use the command-line “unpackimg “, or simply drag-and-drop the image. This will split the image and unpack the ramdisk to a subdirectory.
3) Alter the ramdisk as you like.
4) The repackimg batch script requires no input and simply recombines the previously split zImage with the newly packed modified ramdisk using all the original image information (which was also split and saved).
5) The cleanup batch script resets the folder to its initial state, removing the split_img+ramdisk directories and any new packed ramdisk or image files.
There are a few optional, advanced command-line arguments for repackimg: “–original”, which will cause it to repack using the original split ramdisk instead of repacking, this is useful for testing or trimming dumps; “–organize”, which will cause it to repack then pad it to the size of the original image, this is useful for repacking dumps to then be fastboot flashed; “–level” with 1-9 and possibly 0 allows changing the compression level used to repack to more closely match the original; “–avbkey” with (optionally path and) a keyname allows changing from the default AOSP verity key; “–forceelf” to make an older unpacked Sony ELF file repack as an ELF.
All scripts also allow unpacking/repacking with the current directory instead of the AIK directory if “–local” is the first command-line argument.
Usage is similar for the Android and Linux versions, again, just review the release notes for them.
Hopefully, this is helpful to someone. It’s been extremely useful for me in my messing around with kernel ramdisks, which is why I created it in the first place.