To unpack the images, you can use the phone with Android 5+.
The system make_ext4fs from the phone firmware is used, so on the phone with android 6+ (or better than 7), you can collect system.img images from android 5+.

Root rights are needed, busybox (needed before UKA version: 4.4 inclusive) and enough space for the images themselves and their unpacking in ./data.
Before firmware versions 4.6, 4.7, delete the old version and flash the corresponding archive through twrp.
In the kitchen there is a utilityВ®AIK - Android Image Kitchen (Post 1Senderman1 # 41149591)for repacking boot (recovery) .img.
If, for some reason, you do not want to flash AIK-mobile (or, for example: already installed), then delete the file "AIK.Mobile.Installer.v3.4.zip" from the archive, and flash "unpack-android_new_4.6. zip "without this file.
After flashing, set the terminal emulator (if not already installed):Android Terminal Emulator (Post CONTRA S # 4295285)And its settings tick to UTF-8.

To start the kitchen, in the terminal enter:


Go to the item: "Extract file_contexts", and select the sub-item: "Setting the configuration", if this is not done, then the file_contexts.bin conversion will not work ->file_contexts.
It is necessary to start installation of configuration only once.
In version 4.5 and above should work without the use of this item.

And then enter the numbers corresponding to the desired action.

To extract the file_contexts, put boot.img in the folder: / data / local / UnpackerContexts.
To unpack .img images, you need to put system.img or vendor.img in the folder: / data / local / UnpackerSystem, and select the .img file (no more than 5) for unpacking.
When unpacking, the folders will be deleted: "system", or "vendor"; Files: * _fs_config and * _pack.sh from the previous decompression.
To build an image, copy the resulting file_contexts to the folder: / data / local / UnpackerSystem, if for some reason it is not in the folder, then the assembly will be done with the file_contexts obtained when unpacking the image.
If files or folders were added to the disassembled image, then before assembling it is necessary, all added should be entered in fs_config, and only then be collected.
If there are spaces in the folder or file names in the unpacked image, then make_ex4fs will not build such an image until you rename the files and fix the entries in fs_config.
Therefore, it is also impossible to add folders and files with spaces to the unpacked image.
In version 4.6 a recording assistant has been added to fs_config.
If you just deleted something, you do not need to edit fs_config.
Also in the folder must be present symlinks.
Well, in contexts, selinux will also need to be watched, depending on what was added.
To unpack or convert .dat, .br and in other cases, you will be prompted to enter the path to the folder where the image is located (system (vendor) .transfer.list should be located in the same folder).
When converting and building in .dat, look behind the phone screen, because in some cases you need to enter a number corresponding to the version of the android of the image being assembled.

There is a choice of compression ratio for converting * .new.dat to br.
To reduce the conversion time, compression can be chosen 3-5 (maximum 7).

To unpack the boot (recovery) .img, put the file in the folder: / data / local / AIK-mobile, and select the file in the menu: "unpack boot"
For packaging, use the item: "pack boot".
The collected file will be located in the folder: / data / local / AIK-mobile named boot-output.img.
To clear the working folder, also use the corresponding item. Source and output files will not be deleted.
AIK-mobile can be completely removed from the phone directly from the menu.

To mount, use the corresponding menu item, and the raw image must be located in the folder: / data / local / UnpackerSystem.
Do not forget to unmount the image.

If the image is mounted and the mounted folder is empty, then with super su installed, in its settings we do this:

with magisk set like this:
В®Unpacker Kitchen for Android (UKA). (Post blackeangel # 82343910)

To remove the kitchen from the phone, go to the appropriate menu item and confirm the deletion,
after confirmation, the phone will be overloaded in twrp, and after the script has been worked out it will be loaded into the system.
Read also changes in versions.

For errors and suggestions, write to the topic or QMS.

Some changes in the scripts.
Now file_contexts is automatically created for an image that is unpacked, which means it can be used only to build the same image.
The system (vendor) _file_contexts and system (vendor) _fs_config files will be located in the folder: / data / local / UnpackerSystem / config, if necessary, they can also be edited, moved, and renamed is not necessary.
The image will be assembled with the file_contexts obtained during unpacking.
To build with file_contexts, obtained from boot.img, you need as before to put it in the folder: / data / local / UnpackerSystem.
After assembly or unpacking, the third-party file_contexts will be removed.
Files from: / data / local / UnpackerSystem / config, as well as the "system" or "vendor" folders from: / data / local / UnpackerSystem, are only deleted after unpacking the next image.

Some changes in the scripts.
Added system.img splicing from individual images (from Qfil firmware).
For splicing, put all system_xx and rawprogram0.xml or rawprogram_unsparse.xml in the folder: / data / local / UnpackerQfil.
Select "Menu: Unpacking .img">"Glue the image from the firmware under Qfil".
You will get "system.raw.img" in the folder: / data / local / UnpackerQfil. Then you can perform actions as with the usual .img.

Installed busybox is not needed (if there are problems without it, write to the topic).
Updated Aik-mobile to version 3.3.
Added unpacking payload.bin. For unpacking, put payload.bin in the folder: / data / local / UnpackerPayload, in the menu select: Unpacking .img ->Unpack payload.bin and wait patiently, because unpacking takes a long time.
Added selection of the assembly sparse.img or raw.img, and the choice of assembly with the original size of the image, or with the introduction of its size.
Changed the installation script.

Added entry assistant in fs_config. Updated Aik-mobile, broli, fewer items in some menus, changed some scripts.
В®Unpacker Kitchen for Android (UKA). (Post kory-vadim # 81677054)

Fixed bugs when unpacking, converting and other fixes in scripts.
Because of:

Added automatic replacement of spaces in file names (if there is of course), correction of records in fs_config, file_contexts with underscores when unpacking an image.
Just in case, paths to files with spaces are stored in /data/local/UnpackerSystem/config/xxx_space.txt
It is better to flash, after removing the installed one.

Universal version, ie without a difference there make_ext4fs or not.
To save space in the / data, added the ability to uncompress and mount * .img images from any folder (you need to enter the path), and while unpacking .dat, .br, .img image will be in the same folder as the files: .dat, .br.
Assembling sparse-image is produced directly in the sparse, without conversion, ie, as in the past in a version for phones with make_ext4fs.
Added symlinks recovery, ie at any time to restore the symbolic links that were in the way when unpacking. Menu item: Assembling .img ->Restoring symbolic links.
Updated AIK-mobile to version 3.6, it ramdisk.img 96mb.

Correction of image collection with android 9-10.

version: 4.2 unpack-android_4.2.zip (42.35 MB)
version: 4.3 unpack-android_4.3.zip (42.36 MB)
version: 4.4 unpack-android_4.4.zip (42.1 MB)
version: 4.5 unpack-android_4.5.zip (60.45 MB)
version: 4.6 unpack-android_4.6_new.zip (60.44 MB)
version: 4.7 unpack-android_4.7.zip (60.44 MB)
Version: 4.7_make_andr9 unpack-android_4.7_make_andr9.zip (61.88 MB)
version: 4.8 unpack-android_4.8.zip (63.11 MB)
version: 4.9 unpack-android_4.9.zip (63.95 MB)
version: 4.9.2 unpack-android_4.9.2.zip (66.06 MB)
version: 4.9.3 unpack-android_4.9.3.zip (66.06 MB)