[TOOL] Android Image Kitchen - Unpack/Repack Kernel Ramdisk [Win/Android/Linux/Mac]

Search This thread
By:
Advanced…
xinulhacker

xinulhacker

Member
Jul 19, 2022
24
10
osm0sis said:
What do you mean by alignment? Page size? Change the value in split_img/*-pagesize
Click to expand...
Click to collapse
This is what a friend said who is helping me with this project.

xinulhacker said:
The last two failed to boot.

Reply:
Repack image with the pack option /rmd4 - alignment of ramdisk in Android Boot image (pack option).
I think boot or not boot is random without this option, there is no logic between booting or not booting? It was a very small change in ramdisk to make twrp not work.

He is using carliv kitchen on Linux to repack and the images boot if he adds whatever this " /rmd4 " is ...
 
Last edited:
osm0sis

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
16,763
40,417
Halifax
GT-i9250
Google Nexus 4
xinulhacker said:
This is what a friend said who is helping me with this project.

xinulhacker said:
The last two failed to boot.

Reply:
Repack image with the pack option /rmd4 - alignment of ramdisk in Android Boot image (pack option).
I think boot or not boot is random without this option, there is no logic between booting or not booting? It was a very small change in ramdisk to make twrp not work.
Click to expand...
Click to collapse
Not seeing anything from Googling rmd4 ramdisk. What supports that pack option? Point me again to the .img which AIK repackimg --original doesn't result in a booting .img and supposedly needs "alignment" so I can compare what's different.
 
Last edited:
xinulhacker

xinulhacker

Member
Jul 19, 2022
24
10
xinulhacker said:
That's a great question. I will ask him. I thought it was some option known to those with more experience so I have not researched his recommendation myself.

I will look deeper.
Click to expand...
Click to collapse

osm0sis said:
Not seeing anything from Googling rmd4 ramdisk. What supports that pack option? Point me again to the .img which AIK repackimg --original doesn't result in a booting .img and supposedly needs "alignment" so I can compare what's different.
Click to expand...
Click to collapse
171 failed to boot
171aligned booted
"alignment option" used

Stock recovery being ported
If I unpack and repack the stock recovery using AIK without making any changes, it will not boot. Hangs on splash screen.
 

Attachments

  • twrp3.0_V1731.img
    13.3 MB · Views: 15
  • twrp3.0_V1731_aligned.img
    13.3 MB · Views: 6
  • rk3128.stockrecovery.img
    32 MB · Views: 7
  • Like
Reactions: osm0sis
xinulhacker

xinulhacker

Member
Jul 19, 2022
24
10
osm0sis said:
Interesting. I'll take a look when I have some time and see if I can figure out what alignment refers to... In the middle of setting my laptop up again after RMAing for the faulty SSD, and lost all of my dev setup, so will likely be awhile.
Click to expand...
Click to collapse
No problem. Thanks for taking the time to look into it.
I'm very appreciative. Sorry to hear you lost your setup! That sux.
I'll ask exactly what he means by alignment.
Thanks again.
 
  • Like
Reactions: osm0sis
xinulhacker

xinulhacker

Member
Jul 19, 2022
24
10
xinulhacker said:
Thanks again.Interesting. I'll take a look when I have some time and see if I can figure out what alignment refers to... In the middle of setting my laptop up again after RMAing for the faulty SSD, and lost all of my dev setup, so will likely be awhile.
Click to expand...
Click to collapse
Here are the Rockchip images that I unpack and repack without changing anything (with AIK mobile) and the boot hangs for some reason.
According to the person helping, he is using an imagerepacker option on windows to "align" the Rockchip images.
I'm still not certain what that means.
I'm guessing Rockchip image suites repack in some special way... (The images repacked with his tool are above.)
Thanks for your time and help.
 

Attachments

  • rk3128.stockrecovery_AIK_mobile_repack_No_mod_boot_fails.img
    9.5 MB · Views: 12
  • rk3128.stockrecovery.img
    32 MB · Views: 9
  • twrp3.0.rk3128_AIK_mobile_repack_no_mod_boot_fails.img
    13.2 MB · Views: 11
  • twrp3.0.rk3128.img
    13.2 MB · Views: 9
  • Like
Reactions: osm0sis and ipdev
xinulhacker

xinulhacker

Member
Jul 19, 2022
24
10
A quote from him--

I use this repack option as parameter for imgrepackerrk program, I have no source of this program, only binary exe file, don't know exactly what alignment is taking place.
 
  • Like
Reactions: osm0sis and ipdev
osm0sis

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
16,763
40,417
Halifax
GT-i9250
Google Nexus 4
Maybe he means "signing" when he says "aligning" 🤔

Please note the "Nibiru V05-A" Rockchip RK device listed as Not Supported in the OPs and follow the link, very likely that your device falls in this category.

You can find the closed-source imgrepackerrk tool by reading through the relevant thread posts I linked as well, but I have no plans to include it in AIK while it remains closed source and there's no documentation of what the different chipset variants require or how anything's calculated and patched.

Edit: I see you've posted on the imgrepackerrk thread, so I'm not sure why you're here acting like you've never heard of it... 🤨

What device are you using? I'll add it to the unsupported list.
 
Last edited:
  • Like
Reactions: ipdev, Aqq123 and galaxys
xinulhacker

xinulhacker

Member
Jul 19, 2022
24
10
osm0sis said:
Maybe he means "signing" when he says "aligning" 🤔

Please note the "Nibiru V05-A" Rockchip RK device listed as Not Supported in the OPs and follow the link, very likely that your device falls in this category.

You can find the closed-source imgrepackerrk tool by reading through the relevant thread posts I linked as well, but I have no plans to include it in AIK while it remains closed source and there's no documentation of what the different chipset variants require or how anything's calculated and patched.

Edit: I see you've posted on the imgrepackerrk thread, so I'm not sure why you're here acting like you've never heard of it... 🤨

What device are you using? I'll add it to the unsupported list.
Click to expand...
Click to collapse
Yes. Maybe he means signing.... Idk.
As for this device, it's a Pipo Max. Old device.
I actually didn't even realize I was "watching" imagepackerrk. Apparently I responded to a post saying to use Android Image Kitchen. Ha! Promotional fees not necessary.
Thanks for your help. I'll continue to research.
 
  • Like
Reactions: ipdev and osm0sis
fbalder18

fbalder18

Senior Member
Sep 28, 2021
50
29
Braunschweig
Samsung Galaxy S9+
Samsung Galaxy S10
I have a problem unpacking and repacking a recovery for Poco X3 Pro (vayu) installed firmware fw_vayu_miui_VAYUGlobal_V13.0.5.0.SJUMIXM and crDroidAndroid-12.1-20220818-vayu-v8.8 (now ota-updated to 20220828). The official TWRP 3.6.2 is maintained by Nebrassy, but he also has a development version for A12 that supports decryption (TWRP-3.6.2-vayu-Nebrassy-03-07-22.img), thats the one I use and it works fine. But I would like to modify twrp.flags so that the internal storage can be backed up.
I use Ubuntu 20.04 virtual machine because the recovery has files with matching names differing in upper/lowercase. AIK is 3.8. After unpack and repack without modifying anything there is the strange behaviour that the recovery startet with
fastboot boot image-new.img
boots fine, but after flashing it with
fastboot flash recovery image-new.img
the recovery doesn't start but falls back to bootloader (fastboot screen). Also the system can't be booted any more and also falls back to bootloader. Only way to use the system again is to flash Nebrassy's img, fastboot into that recovery and boot to system from there. Then everything is fine. But no backup of internal storage...
Downgrading cpio to 2.12 didn't solve the problem.
Does anyone has an idea whats going wrong?
 

Attachments

  • TWRP-3.6.2-vayu-Nebrassy-03-07-22.img
    128 MB · Views: 4
  • image-new.img
    66.8 MB · Views: 4
Last edited:
joenka

joenka

New member
Sep 7, 2022
2
0
When execute ./mboot boot.img.lz4
board : SRPTL16A001
kernel : kernel
ramdisk : ramdisk
page size : 2048
kernel size : 15492534
ramdisk size : 1475623
dtb size : 2
base : 0x40078000
kernel offset : 0x00008000
ramdisk offset : 0x11a88000
tags offset : 0x07808000
dtb img : dt.img
cmd line : bootopt=64S3,32N2,64N2 androidboot.tag=TabA7lite_Huaqin_BSP_20210408174009 loop.max_part=7
ramdisk is unknown format,can't unpack ramdisk
Unpack completed.
 

Attachments

  • boot.img
    16.3 MB · Views: 7
osm0sis

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
16,763
40,417
Halifax
GT-i9250
Google Nexus 4
joenka said:
When execute ./mboot boot.img.lz4
board : SRPTL16A001
kernel : kernel
ramdisk : ramdisk
page size : 2048
kernel size : 15492534
ramdisk size : 1475623
dtb size : 2
base : 0x40078000
kernel offset : 0x00008000
ramdisk offset : 0x11a88000
tags offset : 0x07808000
dtb img : dt.img
cmd line : bootopt=64S3,32N2,64N2 androidboot.tag=TabA7lite_Huaqin_BSP_20210408174009 loop.max_part=7
ramdisk is unknown format,can't unpack ramdisk
Unpack completed.
Click to expand...
Click to collapse
Why would you think that would work? mboot isn't for boot.img.lz4. That's not even the output from mboot. RTFM please.
 
Last edited:
  • Like
Reactions: Aqq123
fbalder18

fbalder18

Senior Member
Sep 28, 2021
50
29
Braunschweig
Samsung Galaxy S9+
Samsung Galaxy S10
fbalder18 said:
I have a problem unpacking and repacking a recovery for Poco X3 Pro (vayu) ...
the recovery doesn't start but falls back to bootloader (fastboot screen).
Click to expand...
Click to collapse
I solved the problem. After un-/repackimg I added an AVBv2 signature using avbtool. Now also the flashed recovery image boots fine. It looks like the Poco X3 Pro bootloader only accepts signed images.
 
  • Like
  • Love
Reactions: Daniel_47, ipdev, osm0sis and 1 other person
HassanMirza01

HassanMirza01

Senior Member
Jul 9, 2014
4,158
7,440
29
Islamabad
www.EliteDevelopment.com.pk
Xiaomi Poco F3
fbalder18 said:
I solved the problem. After un-/repackimg I added an AVBv2 signature using avbtool. Now also the flashed recovery image boots fine. It looks like the Poco X3 Pro bootloader only accepts signed images.
Click to expand...
Click to collapse

bro, am having same issue now in new roms, they dont boot recovery until booted from fastboot, seems like xiaomi updated bootloader for all devices, can u explain how you added signature using avbtool?
 
fbalder18

fbalder18

Senior Member
Sep 28, 2021
50
29
Braunschweig
Samsung Galaxy S9+
Samsung Galaxy S10
HassanMirza01 said:
bro, am having same issue now in new roms, they dont boot recovery until booted from fastboot, seems like xiaomi updated bootloader for all devices, can u explain how you added signature using avbtool?
Click to expand...
Click to collapse
You need Python (I think it will work on both Windows and Linux) and the Python script avbtool.py, e.g. from here. Then you call the script with
Code: 
avbtool.py add_hash_footer --image image-new.img --partition_size 134217728 --partition_name recovery
This will extend the image and add avb with the builtin default signature.
I also found a zip with avbtool for arm64 here. It should work on the mobilephone, it has the python interpreter included. But I didn't try it, I used my notebook where I had python anyhow.
 
Last edited:
  • Like
Reactions: HassanMirza01, Aqq123, osm0sis and 1 other person
You must log in or register to reply here.

Similar threads

capslock66
[Tool][Windows Only][Root] Android Reverse Tethering 3.19
Replies
2K
Views
2M
lenigma1too
lenigma1too
Chainfire
[Android 2.1+][03.10.2011][v3.2] Chainfire3D [ROOT][OpenGL ES 2.0+]
Replies
3K
Views
3M
rignfool
rignfool
Phil3759
[2015.10.09]CWM 6.0.5.1 - PhilZ Touch 6.59.0 (libtouch_gui 1.42)
Replies
6K
Views
4M
A
aminelove
N
[APP][ROOT] LMT Launcher v3.2
Replies
15K
Views
5M
H
hugozo
Chainfire
[2014.05.01][ROOT] Mobile ODIN v4.20
Replies
5K
Views
4M
Rukbat
Rukbat

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 788
    osm0sis
    osm0sis
    Android Image Kitchen -- Unpack/Repack Kernel+Recovery Images, and Edit the ramdisk.

    Windows ports of the necessary Linux utils for Android image (kernel/recovery) mod work:

    mkbootimg, unpackbootimg: https://github.com/osm0sis/mkbootimg
    pxa-mkbootimg, pxa-unpackbootimg: https://github.com/osm0sis/pxa-mkbootimg
    elftool: https://github.com/osm0sis/elftool
    unpackelf: https://github.com/osm0sis/unpackelf
    mboot: https://github.com/osm0sis/mboot
    dumpimage, mkimage: https://www.denx.de/wiki/U-Boot/WebHome
    mkmtkhdr: https://github.com/osm0sis/mkmtkhdr
    loki_tool: https://github.com/djrbliss/loki
    futility: https://github.com/osm0sis/futility
    boot_signer.jar (requires JRE 8+): https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606
    blobpack, blobunpack: https://github.com/AndroidRoot/BlobTools
    dhtbsign: https://github.com/osm0sis/dhtbsign
    rkcrc: https://github.com/linux-rockchip/rkflashtool
    sony_dump: https://xdaforums.com/crossdevice-dev/sony/tool-unpack-format-sony-kernel-image-t3530077
    bzip2, cat, chmod, cpio, cut, dd, file, find, gzip, hexdump, lzop, printf, tail, truncate, xz;
    cygbz2-1, cygcrypto-1.1, cyggcc_s-1, cygiconv-2, cygintl-8, cyglzma-5, cyglzo2-2, cygmagic-1, cygncursesw-10.dll, cygstdc++-6.dll, cygssl-1.1, cygwin1, cygz: https://cygwin.com/
    lz4: https://lz4.github.io/lz4/
    sudo: https://github.com/mattn/sudo
    magic: https://www.darwinsys.com/file/

    See the Mobile Edition (AIK-mobile) initial release notes for the specifics on the native Android version.
    Likewise for the Linux/macOS Edition (AIK-Linux) initial release notes.

    My original intent was to have this package dependency-free, but as you can see, I did have to include Cygwin. Initially just for mkbootimg since the huaixzk standalone version wouldn't work (it wasn't loading the kernel as binary, thanks trevd); then I discovered that using the GNUWin32 cpio to unpack somehow didn't play nice with repacking the ramdisk in a usable state, so at that point I decided I might as well go Cygwin across the board. As it is, I've included the latest Cygwin-dependent executables and required libraries from their repos and built my own custom Cygwin image and ramdisk utilities built from the latest sources.

    Originally only for Google Pixel/Nexus/AOSP standard boot.img files, built-in support has now expanded to Google Pixel/AOSP vendor_boot.img files, Android Verified Boot (AVBv1)/ChromeOS/SignBlob signed boot.img files, Barnes & Noble Nook "Green Loader" signed boot.img files, Samsung/Spreadtrum DHTB header signed boot.img files, the Samsung/Marvell PXA1088/1908 board boot.img variant (AOSP-PXA), Loki patched boot.img files, amonet patched boot.img files, Sony SIN signed/packaged kernel.elf extraction, Sony ELF kernel.elf files, Intel OSIP Android image files, DENX U-Boot uImage files, Rockchip KRNL signed ramdisk image files, MTK headers for kernel/ramdisk, and LG Bump/Samsung SEAndroid footers for boot.img.

    The main advantage here is you don't need Cygwin shell or PERL scripts. Other guides exist but none of them are universal for target device, compression and/or developed for Windows, Android ARM/x86/MIPS + ARM64/x86_64/MIPS64, and now macOS. With this universality in mind I've automated the whole process with batch/shell scripts.

    My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!


    Instructions

    1)     Unzip.
    2) Either use the command-line "unpackimg <image-filename.img>", 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 script requires no input and simply recombines the previously split kernel with the newly packed modified ramdisk using all the original image information (which was also split and saved).
    5) The cleanup 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; "--origsize", 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 attempt 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.

    Supported ramdisk compression formats in the *-ramdiskcomp file are gzip, lzop, lzma, xz, bzip2, lz4, lz4-l (for lz4 legacy), cpio (for uncompressed), and empty (for no ramdisk).

    Usage is similar for the Android and Linux versions, again, just review the release notes for them.

    Hopefully this is some help 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.

    Enjoy!
    Questions, comments and feedback welcome.


    If you are reporting a problem with your device, please clearly state your device name and model/variant, attach a log, as well as provide a link to the image file.


    Downloads

    Android.Image.Kitchen.v3.8-Win32.zip

    UPDATE-AIK.Mobile.Installer.v3.8-ALL-signed.zip

    AIK-Linux-v3.8-ALL.tar.gz


    Source Code
    https://github.com/osm0sis/Android-Image-Kitchen


    Credits & Thanks: All authors of the included binaries and libraries for their amazing work, as linked (or linked via GitHub) above. Peteragent5, alansj & iridaki for the general methods used in their PERL scripts and Linux guides. SuperR. & tobias.waldvogel for the general methods used in their kernel.elf unpacking scripts. _that and rayman for the general methods used to repack a working boot.blob. Chainfire for the ChromeOS and SEAndroid general methods. cybojenix for the Bump general method. xyz` & k4y0z for the amonet general method.

    Thanks to Goatshocker for testing out things for the HTC image issues, leading to the workaround and subsequent fix, avinashrocks1990 & tajimura for testing out compression support and the large pagesize fix, civato for testing out dtb support, talich for testing out the Linux version, shoey63 for testing out Linux + ELF support, moonbutt74 for testing out Android-x86 support, nathanchance for testing out the new AIK-mobile cpio method on his Pixel 2, leading to important fixes for its support, shakalaca for the great help with completing and testing Intel OSIP support, and Postman1year & CXZa for their help testing to find out the workaround for the Cygwin cut + symlink regression issues. Huge thank you to trevd and Modding.MyMind/SHM for all the contributing work they've each done and support they've provided.

    Disclaimer: Naturally, you take all the responsibility for what happens to your device when you start messing around with things.

    Download counts:
    AIK - v1.0: 1540; +HTCFix: 430. v1.5: 4718. v1.6: 3556. v1.8: 8678; +Lok2Img: 1629. v1.9: 2580. v2.0: 22886. v2.2: 20522. v2.3: 14524. v2.4: 84432; +LokiAddon: 20071. v2.5: 5004. v2.6: 9354. v2.7: 5442. v2.8: 6639. v2.9: 7672. v3.0: 2810. v3.1: 6502. v3.2: 27104. v3.3: 17736. v3.4: 25988. v3.5: 19051. v3.6: 32472. v3.7: 21457.
    Mobile - v1.0: 311. v1.1: 265. v1.2: 302. v1.3: 100. v1.4: 486. v1.5: 224. v1.6: 3303. v1.7: 7798. v1.8: 16286. v1.9: 3800. v2.0: 5444. v2.1: 2526. v2.2: 926. v2.3: 1346. v2.4: 18426. v2.5: 2586. v2.6: 6068. v2.7: 2936. v2.8: 3932. v2.9: 4181. v3.0: 1301. v3.1: 3300. v3.2: 3254. v3.3: 6824. v3.4: 10786. v3.5: 8624. v3.6: 14020. v3.7: 8951.
    Linux - v1.0: 75. v1.1: 208. v1.2: 233. v1.3: 112. v1.4: 421. v1.5: 173. v1.6: 1838. v1.7: 2596. v1.8: 4818. v1.9: 604; +v1.9.1: 1068. v2.0: 1836. v2.1: 1240. v2.2: 466. v2.3: 522. v2.4: 8126. v2.5: 1052. v2.6: 2018. v2.7: 1248. v2.8: 2486. v2.9: 5057. v3.0: 1455. v3.1: 2957. v3.2: 14508. v3.3: 10046. v3.4: 16294. v3.5: 12651. v3.6: 16478. v3.7: 12927.
    View
    159
    osm0sis
    osm0sis
    AIK should be universal for Android devices that accept AOSP, ELF, OSIP, U-Boot and KRNL format images in theory, but there is always a chance it doesn't work for your device due to image packing differences, etc. Here is a running list of confirmed working and questionably/confirmed not working devices. If your device isn't in either list odds are that it will still work fine.

    Known Working Devices

    Amazon Fire HD 10
    Asus Nexus 7 (2012, 2013)
    Asus Transformer Pad
    Asus Zenfone (2, 5)
    Auchan QiLive (Q5, Q7)
    Barnes & Noble Nook ( , HD+, 7)
    BQ Aquaris M8
    Coolpad Catalyst
    Essential PH-1
    Google Pixel (C, , XL, 2, 2 XL, 3, 3 XL, 3a, 3a XL, 4, 4 XL, 4a, 4a 5G, 5, 5a)
    Huawei Ascend Y300
    Huawei Mate 8
    Huawei Nexus 6P
    Huawei U8800 Ideos X5
    HTC Nexus 9
    HTC One (M7, M8, S, X)
    HTC Vivid/Raider 4G
    HP Slate 21
    LeEco Le Pro3
    Lenovo A706
    Lenovo K900
    Lenovo Vibe K5
    LG G(2, 2 Mini, 3, 3 Stylus, 5)
    LG GPad (7.0, 8.3, X 8.0)
    LG Nexus (4, 5, 5X)
    LG Optimus (3D, 4X HD)
    LG Stylo 3 Plus
    LG V(10, 20)
    Micromax Ninja/Bolt A27
    Motorola Moto G (2013, 2014)
    Motorola Moto X 2014
    Motorola Nexus 6
    Nextbit Robin
    OnePlus (One, 2, X, 3, 3T, 5, 5T, 6, 6T, 7, 7 Pro, 7T, 7T Pro, 8, 8 Pro, 8T, 9R, 9, 9 Pro)
    OnePlus Nord ( , N10 5G, N100)
    Pantech Vega Iron
    Pantech Vega Secret Note
    Samsung Galaxy A3 2016
    Samsung Galaxy Ace II X
    Samsung Galaxy Core Mini 4G
    Samsung Galaxy Mega
    Samsung Galaxy Nexus
    Samsung Galaxy Note (2, 3, 4, Pro 12.2)
    Samsung Galaxy S(3, 3 Mini, 4, 5, 6, 7, 8, 8+)
    Samsung Galaxy Star
    Samsung Galaxy Tab (2 7.0, 3 10.1, 4 7.0, 4 8.0, 4 10.1, A 7.0, A 10.1, Pro 8.4)
    Samsung Galaxy Victory
    Samsung Galaxy Xcover 3
    Samsung Nexus 10
    Sony Xperia (Arc S, M, Neo, Neo V, SP, Tab Z4, Z, Z1, Z5)
    Spice Mi-355 Stellar Craze
    Vodafone Smart Ultra 6
    Xiaomi Mi Pad
    Xiaomi Poco X2
    Xiaomi Redmi (6A, Note 3 Pro)


    Confirmed Not Working Devices
    • Blackview BV4000 - some newer MediaTek (MTK) devices use special image signing that adds a "BFBF" pre-header signature. While present on multiple MTK devices, it only appears to be enforced by the bootloader on some. See this post.
    • HTC Desire 326G, Huawei Honor Bee, Huawei MediaPad T1 7.0 - some newer Spreadtrum devices use special image signing that adds a "SPRD-SECUREFLAG" pre-header signature, so images will unpack/repack but most likely won't boot unless run through their internal signing tool. See this post.
    • Nibiru V05-A, Pipo Max - some RockChip (RK) devices use a variant of the AOSP image format with extra checksums and hidden sections with extra data. There is not currently an open source tool that can handle repacking these. See this post.
    • Samsung Galaxy S (Advance, Captivate, Vibrant), Samsung Galaxy S2, Samsung Galaxy Note & Samsung Galaxy Tab - contain zImage (kernel) + ramdisk (possibly within the zImage) but are the "headerless" Linux kernel blob format and require a full cross-compiler to repack correctly. See this post.
    • Samsung [various] - the image and SEANDROIDENFORCE footer are followed by a signature that, while present on many Samsung devices, only appears to be enforced by the bootloader on some. See this post.
    • Skyworth 50G2A TV - some newer MediaTek (MTK) devices use special image part signing that adds a 256-byte checksum/signature to both Image.gz-dtb/zImage-dtb (kernel) and ramdisk.cpio.gz, so images will unpack/repack but most likely won't boot unless run through their internal signing tool. See this post.
    • Xiaomi Mi Box 3S, ZTE B860H STB - some newer Amlogic devices use special image signing that adds an "AMLSECU!" signature within the header and appears to encrypt the ramdisk, so the image itself will unpack/repack but cannot be re-signed, and the ramdisk cannot be unpacked or modified.

    Note: For devices requiring Loki patched images (e.g. LG G2, AT&T Samsung Galaxy S4), your device's aboot.img dump must be in the script directory to Re-Loki. (Thank you to jeboo for the original one-way Lok2Img Workaround's binary source, used prior to the official Loki Tool gaining un-Loki support).


    Release Notes

    Windows:
    v1.0 - Dec 30, 2012 - Initial release.    
    v1.5 - May 6, 2013 - Linked.
    v1.6 - Sep 16, 2013 - Linked.
    v1.8 - Dec 9, 2013 - Linked.
    v1.9 - Jun 7, 2014 - Linked.
    v2.0 - Aug 3, 2014 - Linked.
    v2.2 - Mar 25, 2015 - Linked.
    v2.3 - Oct 11, 2015 - Linked.
    v2.4 - Feb 8, 2016 - Linked.
    v2.5 - Jan 26, 2017 - Linked.
    v2.6 - Feb 27, 2017 - Linked.
    v2.7 - May 1, 2017 - Linked.
    v2.8 - Jun 5, 2017 - Linked.
    v2.9 - Sep 14, 2017 - Linked.
    v3.0 - Dec 14, 2017 - Linked.
    v3.1 - Jan 7, 2018 - Linked.
    v3.2 - Mar 19, 2018 - Linked.
    v3.3 - Jul 23, 2018 - Linked.
    v3.4 - Oct 28, 2018 - Linked.
    v3.5 - Apr 17, 2019 - Linked.
    v3.6 - Sep 22, 2019 - Linked.
    v3.7 - May 22, 2020 - Linked.
    v3.8 - May 5, 2021 - Linked.

    Android:
    v1.0 - Mar 23, 2014 - Linked. (ARM only)
    v1.1 - Apr 19, 2014 - Linked. (ARM only)
    v1.2 - May 15, 2014 - Linked. (ARM only)
    v1.3 - Jun 7, 2014 - Linked. (ARM, x86 with emulation)
    v1.4 - Jun 17, 2014 - Linked. (ARM, x86 with emulation)
    v1.5 - Aug 3, 2014 - Linked. (32bit only)
    v1.6 - Aug 19, 2014 - Linked. (32bit only)
    v1.7 - Dec 26, 2014 - Linked. (32bit only)
    v1.8 - Mar 25, 2015 - Linked. (32bit only)    
    v1.9 - Oct 11, 2015 - Linked. (32bit only)
    v2.0 - Dec 7, 2015 - Linked.
    v2.1 - Feb 8, 2016 - Linked.
    v2.2 - Mar 16, 2016 - Linked.
    v2.3 - Apr 1, 2016 - Linked.
    v2.4 - Apr 20, 2016 - Linked.
    v2.5 - Jan 26, 2017 - Linked.
    v2.6 - Feb 27, 2017 - Linked.
    v2.7 - May 1, 2017 - Linked.
    v2.8 - Jun 5, 2017 - Linked.
    v2.9 - Sep 14, 2017 - Linked.
    v3.0 - Dec 14, 2017 - Linked.
    v3.1 - Jan 7, 2018 - Linked.
    v3.2 - Mar 19, 2018 - Linked.
    v3.3 - Jul 23, 2018 - Linked.
    v3.4 - Oct 28, 2018 - Linked.
    v3.5 - Apr 17, 2019 - Linked.
    v3.6 - Sep 22, 2019 - Linked.
    v3.7 - May 22, 2020 - Linked.
    v3.8 - May 5, 2021 - Linked.

    Linux/macOS:
    v1.0 - Apr 11, 2014 - Linked. (x86, Linux only)
    v1.1 - Apr 19, 2014 - Linked. (x86, Linux only)
    v1.2 - May 15, 2014 - Linked. (x86, Linux only)
    v1.3 - Jun 7, 2014 - Linked. (x86, Linux only)
    v1.4 - Jun 17, 2014 - Linked. (x86, Linux only)
    v1.5 - Aug 3, 2014 - Linked. (x86, Linux only)
    v1.6 - Aug 19, 2014 - Linked. (x86, Linux only)
    v1.7 - Dec 26, 2014 - Linked. (Linux only)
    v1.8 - Mar 25, 2015 - Linked. (Linux only)
    v1.9 - Oct 11, 2015 - Linked. (Linux only)
    v2.0 - Dec 7, 2015 - Linked. (Linux only)
    v2.1 - Feb 8, 2016 - Linked. (Linux only)
    v2.2 - Mar 16, 2016 - Linked. (Linux only)
    v2.3 - Apr 1, 2016 - Linked. (Linux only)
    v2.4 - Apr 20, 2016 - Linked. (Linux only)
    v2.5 - Jan 26, 2017 - Linked. (Linux only)
    v2.6 - Feb 27, 2017 - Linked. (Linux only)
    v2.7 - May 1, 2017 - Linked. (Linux only)
    v2.8 - Jun 5, 2017 - Linked. (Linux only)
    v2.9 - Sep 14, 2017 - Linked. (Linux only)
    v3.0 - Dec 14, 2017 - Linked.
    v3.1 - Jan 7, 2018 - Linked.
    v3.2 - Mar 19, 2018 - Linked.
    v3.3 - Jul 23, 2018 - Linked.
    v3.4 - Oct 28, 2018 - Linked.
    v3.5 - Apr 17, 2019 - Linked.
    v3.6 - Sep 22, 2019 - Linked.
    v3.7 - May 22, 2020 - Linked.
    v3.8 - May 5, 2021 - Linked.




    Everyone please let me know if AIK works for your devices or if you encounter any problems, so I can make these lists more comprehensive. 👍

    If you are reporting a problem with your device, please clearly state your device name and model/variant, attach a log, as well as provide a link to the image file.
    View
    63
    osm0sis
    osm0sis
    Android ARM/ARM64, x86/x86_64 + MIPS/MIPS64 version of Android Image Kitchen! Now you can easily modify ramdisks on the go! :D

    AIK-mobile:
    - Almost complete feature parity with the Windows/Linux version, including compression support, --original to repack with the original ramdisk, --origsize to pad the repacked image to the size of the original, --level to change the compression level of the repacked ramdisk, --avbkey to change the key used for Android Verified Boot (AVBv1) signing of the repacked image, and --forceelf to make an older unpacked Sony ELF file repack as an ELF. The only thing missing is --local since AIK-mobile's ability to unpack/repack while booted in Android is too complex to easily allow moving the unpack/repack directory around.
    - The flashable zip installs AIK for your Android architecture (ARM/ARM64, x86/x86_64, MIPS/MIPS64) to /data/local/AIK-mobile/ and a helper script created at /system/xbin/aik (alternately /su/bin/aik or /sbin/supersu/bin/aik if SuperSU systemless root is detected, or, /sbin/.magisk/img/aik-mobile/bin/aik or /data/adb/modules/aik-mobile/bin/aik if Magisk is detected).
    - Type "aik" in Terminal Emulator to automatically go to the install directory and get a root prompt, then use, eg. "unpackimg.sh boot.img" to get started.
    - Running su -c "/data/local/AIK-mobile/bin/aik --restore" will recreate the aik helper script in the appropriate place (see above), e.g. after a ROM flash with su.img SuperSU or magisk.img Magisk removed.
    - "aik --uninstall" should be self-explanatory, and "--help" is also available for all included scripts.

    Now also possible to run entirely from a file explorer app, see this post for details!

    To run from TWRP (recovery shell), follow the instructions in this post.

    mkbootimg, unpackbootimg: https://github.com/osm0sis/mkbootimg
    pxa-mkbootimg, pxa-unpackbootimg: https://github.com/osm0sis/pxa-mkbootimg
    elftool: https://github.com/osm0sis/elftool
    unpackelf: https://github.com/osm0sis/unpackelf
    mboot: https://github.com/osm0sis/mboot
    dumpimage, mkimage: https://www.denx.de/wiki/U-Boot/WebHome
    mkmtkhdr: https://github.com/osm0sis/mkmtkhdr
    loki_tool: https://github.com/djrbliss/loki
    futility: https://github.com/osm0sis/futility
    boot_signer-dexed.jar: https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606
    blobpack, blobunpack: https://github.com/AndroidRoot/BlobTools
    dhtbsign: https://github.com/osm0sis/dhtbsign
    rkcrc: https://github.com/rockchip-linux/rkflashtool
    sony_dump: https://xdaforums.com/crossdevice-dev/sony/tool-unpack-format-sony-kernel-image-t3530077
    busybox: https://busybox.net/; https://github.com/osm0sis/android-busybox-ndk
    file, magic: https://www.darwinsys.com/file/
    xz: https://tukaani.org/xz/
    lz4: https://lz4.github.io/lz4/

    GitHub: https://github.com/osm0sis/Android-Image-Kitchen/commits/AIK-mobile

    Originally all but busybox were compiled natively on my Nexus 7 2013 using a KBox2 build environment, now cross-compiled with the NDK on my PC and my own AIK Build Farm. :cowboy:

    Notes: You may delete /data/local/AIK-mobile/bin/busybox if you want to use your ROM's busybox instead.


    Linux will be next on the list, and should be pretty easy since I did all of the shell script leg work with the Android version. ;) (y)


    If you are reporting a problem with your device, please clearly state your device name and model/variant as well as provide a link to the image file.
    View
    34
    osm0sis
    osm0sis
    Another longtime request. New Linux version of Android Image Kitchen up in the OP! Bringing my updated binaries back home! ;)

    Now also supporting macOS out-of-the-box (i.e. no Homebrew or MacPorts addons needed) with v3.0+!

    AIK-Linux:
    - Complete feature parity with the Windows/Android versions, including compression support, --original to repack with the original ramdisk, --origsize to pad the repacked image to the size of the original, --level to change the compression level of the repacked ramdisk, --avbkey to change the key used for Android Verified Boot signing of the repacked image, and --forceelf to make an older unpacked Sony ELF file repack as an ELF.
    - Unpacks as root by default to maintain full control over all repacked ramdisk file ownership/permissions, --nosudo argument available to attempt unpack/repack as user if possible.
    - All scripts allow unpacking/repacking with the current directory instead of the AIK directory if --local is the first command-line argument.
    - "--help" is also available for all included scripts.
    - Unpack with "tar -xzvf AIK-Linux-*.tar.gz" in your home directory then you can go to AIK-Linux and use, eg. "./unpackimg.sh boot.img" to get started.

    mkbootimg, unpackbootimg: https://github.com/osm0sis/mkbootimg
    pxa-mkbootimg, pxa-unpackbootimg: https://github.com/osm0sis/pxa-mkbootimg
    elftool: https://github.com/osm0sis/elftool
    unpackelf: https://github.com/osm0sis/unpackelf
    mboot: https://github.com/osm0sis/mboot
    dumpimage, mkimage: https://www.denx.de/wiki/U-Boot/WebHome
    mkmtkhdr: https://github.com/osm0sis/mkmtkhdr
    loki_tool: https://github.com/djrbliss/loki
    futility: https://github.com/osm0sis/futility
    boot_signer.jar (requires JRE 8+): https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606
    blobpack, blobunpack: https://github.com/AndroidRoot/BlobTools
    dhtbsign: https://github.com/osm0sis/dhtbsign
    rkcrc: https://github.com/rockchip-linux/rkflashtool
    sony_dump: https://xdaforums.com/crossdevice-dev/sony/tool-unpack-format-sony-kernel-image-t3530077
    lz4: https://lz4.github.io/lz4/
    magic: https://www.darwinsys.com/file/
    cpio, dd, file, lzop, tail, truncate, xz; libiconv.2, libintl.8, liblzma.5, liblzo2.2, libmagic.1 (macOS): https://www.macports.org/
    gzip, bzip2, lzop, xz; awk, basename, bash, cpio, cut, dd, dirname, env, file, find, grep, hexdump, java, printf, rev, sed, stat, sudo, tail, truncate, wc (Linux): (required system packages/commands)

    GitHub: https://github.com/osm0sis/Android-Image-Kitchen/commits/AIK-Linux

    Most included binaries were compiled using my patched crosstool-ng i686 and x86_64 Cygwin to Linux cross-compiler toolchains, now as part of my own AIK Build Farm. :cowboy:

    macOS compiles built with osxcross. Instructions available via my Build Farm post.

    I'm not going to interfere with anyone's Linux installations, nor needlessly bundle a ton of commonly available binaries, so if you need extra compression support you need to have those packages installed. In my Ubuntu Server VM gzip, bzip2 and xz/lzma all seem to come pretty much by default, and "apt-get install lzop bsdmainutils" handles lzop and hexdump. Java depends on your setup, but openjdk-8-jre will be what most will want if not already included. lz4 would be the only one that would have to be built from source on many distros, so I have considered it an exception, built it and included it myself.

    Thanks to shoey63 and talich for testing. Cheers! :)


    If you are reporting a problem with your device, please clearly state your device name and model/variant as well as provide a link to the image file.
    View
    30
    osm0sis
    osm0sis
    It's been a busy few weeks!

    After a Herculean effort to get the DENX U-Boot utilities to build with the NDK, which required me firing up my Ubuntu VM (for more than testing for once) and then hacking both the NDK toolchains and tool sources, say hello to U-Boot support! It's a *nix standard, and pretty rare on Android but it does exist (e.g. LG Optimus 3D) and I'm extremely pleased to add support for this completely different type of image format to AIK! :cowboy:

    I then added support for the Samsung/Marvell variant of the AOSP standard for their pxa1088 board, which I've termed "AOSP-PXA", by updating a modified bootimg tools fork to continue the excellent work done by @ketut.kumajaya and @akuhak. There aren't a lot of known examples of these either (e.g. Samsung Galaxy Core Mini 4G, Samsung Galaxy Tab 4 7.0 & Samsung Galaxy Xcover 3) but it was pretty straightforward and removes another entry from the "Confirmed Not Working" list in the OPs. ;)

    Next up, Sony SIN packaging/signature unpack support, thanks to the brilliant research and development of @munjeni for his closed-source kernel_dump binary, of which he also supplied the builds.

    Last but not least, it turns out the signatures I identified on the Pixels last month almost immediately went into enforcement after my release.. and it turns out we misunderstood the nature of these signatures so I have reverted the unpackbootimg patch that was originally submitted to me for the Xioami Mi MAX where these signatures were first found; while reappending the original signature was reported to have worked for the Mi MAX, the Pixel bootloader appears to be enforcing it even more strictly and so they must be signed correctly. Luckily, thanks to the great and ongoing work of @Chainfire we've got a cross-platform working signing tool, but it does rely on a Java-like VM - Java Runtime Environment (JRE) 8+ for Windows/Linux to run correctly - and we can use the Dalvik VM on Android without any issues drawing in part from my previous experiments in this area.

    Since the original AVB signing OEM keys are naturally unavailable this presents a bit of a problem and there are numerous keys already floating around including SuperSU, ElementalX and a few custom Pixel ROMs. To be sensible we the modding community should all try to use the same keys for interoperability, to make sure different mods stack correctly and avoid any possible problems with encrypted devices, so I have generated the required extra certificate for AVB signing from the usual AOSP testkeys and would encourage all other boot image modifying projects to use them; they are available for use on my GitHub. They are the default for AIK, but a user may specify --avbkey on the repackimg commandline to force the use of other keys. The keys may be placed in the main AIK directory and specified without path with only the base name of the files (e.g. --avbkey supersu for supersu.pk8 and supersu.x509.der) or with a path, but still omitting the file extensions to keep it simple (e.g. --avbkey /path/to/ex for /path/to/ex.pk8 and /path/to/ex.x509.der). Hopefully that'll cover all the bases and some other projects will come around to using the testkeys.

    Per usual, the AIK Build Farm has been updated accordingly. Enjoy! :)

    NOTE: Downloads have switched to being hosted on the XDA DevDB Project Downloads page since AIK-mobile now exceeds the 20mb zip attachment size limit.

    I work on these projects in my limited time off, so if you like the progress I'm making, or enjoy anything else I've done on xda, please do hit the donate link from my profile. Thanks for your support!


    Android Image Kitchen v2.8:
    - general cleanup using if/else and absolute paths wherever possible and removing hidden hideErrors option for simplicity since it's no longer needed
    - add detection if running directly from a command prompt and do not pause if so
    - add error catching for unsupported/unrecognized formats on repack, and compression formats on unpack
    - update unpackbootimg and unpackelf binaries from my repos
    - add DENX U-Boot uImage detection and use dumpimage and mkimage to unpack/repack
    - add Samsung/Marvell boot.img variant (AOSP-PXA) and use pxa1088-unpackbootimg and pxa1088-mkbootimg to unpack/repack
    - add Sony SIN signature/packaging detection and use kernel_dump to extract the kernel.elf
    - add Android Verified Boot (AVB) signature footer detection and use BootSignature.jar to re-sign with AOSP testkeys
    - dump AVB type (boot/recovery) to -avbtype so that it may be changed for repack if desired
    - refactor repackimg commandline parameter parsing and introduce --avbkey to specify custom keys (accepts path and/or filename minus extensions) to use for AVB re-signing
    - update slimmed magic file (from file 5.31) with my own fixes
    - update to the latest Cygwin binaries and libraries

    AIK-mobile v2.8 + AIK-Linux v2.8:
    - general cleanup using absolute paths wherever possible
    - add error catching for unsupported formats on repack, and compression formats on unpack
    - fix unpack error output on some xz/lzma ramdisks by using included xz binary instead of busybox (AIK-mobile)
    - update unpackbootimg and unpackelf binaries from my repos
    - add DENX U-Boot uImage detection and use dumpimage and mkimage to unpack/repack
    - add Samsung/Marvell boot.img variant (AOSP-PXA) and use pxa1088-unpackbootimg and pxa1088-mkbootimg to unpack/repack
    - add Sony SIN signature/packaging detection and use kernel_dump to extract the kernel.elf
    - add Android Verified Boot (AVB) signature footer detection and use BootSignature.jar to re-sign with AOSP testkeys
    - dump AVB type (boot/recovery) to -avbtype so that it may be changed for repack if desired
    - refactor repackimg commandline parameter parsing and introduce --avbkey to specify custom keys (accepts path and/or filename minus extensions) to use for AVB re-signing
    - actually fix chromeos subfolder permissions during install (AIK-mobile)
    - fix unpackimg --help to show --sudo option (AIK-Linux)
    - update file binary (5.31) (AIK-mobile)
    - update slimmed magic file (from file 5.31) with my own fixes


    More on my own build changes in the commits here: https://github.com/osm0sis/mkbootimg; https://github.com/osm0sis/pxa1088-mkbootimg; https://github.com/osm0sis/unpackelf.

    Installation information and details on each edition can be found in the OP for Win32 or the AIK-mobile and AIK-Linux initial release notes.


    If you are reporting a problem with your device, please clearly state your device name and model/variant as well as provide a link to the image file.
    View

New posts