Allows to unpack and repack AMLogic Android images on Linux systems without using the Customization Tool - works for Android 7.
system
partitionlogo
partition (for bootup and upgrading logos)boot
image and initrd
ramdiskrecovery
(you can still replace the PARTITION
files by hand)zlib1g-dev
for simg2img
and img2simg
libblkid-dev
for abootimg
(unpacking and repacking boot image)i386
packages if needed (for the logo unpacking / repacking binary)./bin/build
to build the required tools./bin/unpack input.img
to unpack input.img
output/image
: raw image files (PARTITION
files)output/system
: system partition filesoutput/logo
: logo partition filesoutput/boot
: boot partition filesoutput
directory
output/image/system.PARTITION
output/image/boot.PARTITION
output/image/logo.PARTITION
output/boot/initrd.img
if using ./bin/extract_initrd
output/system
mounting point (after a reboot for instance), just run ./bin/remount
to mount it again./bin/unmount
initrd
ramdisk, use the ./bin/extract_initrd
and ./bin/recreate_initrd
scripts (output in output/initrd
)output/system
folder, because it will be replicated in the image and it won't boot !output/boot.img
initrd
ramdisk, its size will change and it will most likely break the boot image. To fix this, edit the bootimg.cfg
file in output/boot
to replicate the change in size (you can repack the image, let it fail and read the logs to see the new size)../bin/repack output.img
to repack the image to output.img
./bin/flash
to flash the image to a device through USB (you will need the udev rule, see https://github.com/Stane1983/aml-linux-usb-burn)
gxl
) is hardcoded into the flashing script, edit it if you're not using S905, S905X or S919file not found
error when trying to unpack and repack the logo partition, install the i386
libraries by following the accepted answer of this post : https://unix.stackexchange.com/questions/13391/getting-not-found-message-when-running-a-32-bit-binary-on-a-64-bit-systemaml_image_v2_packer
and logo_img_packer
binariessimg2img
toolabootimg
tool