abootimg icon indicating copy to clipboard operation
abootimg copied to clipboard

Tool to read/write/update android boot images

Results 8 abootimg issues
Sort by recently updated
recently updated
newest added

@ggrandou I am not sure if this tool works for latest AOSP GKI boot images. While i tried on GKI boot images, i see below messages. `boot.img: ramdisk size is...

If cpio archive contains absolute filenames, files are unpacked relative to host root '/', not 'ramdisk' directory. If abootimg-unpack-initrd is run as root, that could break host system and make...

I unzipped boot.img ``` abootimg -x boot.img ``` 2) ``` admin BOOT cat bootimg.cfg bootsize = 0x415800 pagesize = 0x800 kerneladdr = 0x10008000 ramdiskaddr = 0x11000000 secondaddr = 0x10f00000 tagsaddr...

With newer AOSP devices, system can be used as rootfs, resulting in no initrd being used in the bootimg. Without this patch, 'abootimg -x' on such an image would result...

On Nexus 4, Lineage OS 15.1. Don't know why. Used https://github.com/cfig/Android_boot_image_editor instead, which worked fine.

With newer AOSP environments, the system partition is used as rootfs, and there is no initrd in the boot.img. Unfortunately abootimg -x seems to fail in this case: /home/jstultz/noinitrd-boot.img: ramdisk...

This adds support for header_version 1 and 2, including dtb and dtbo support. In addition it fixes various bugs and adds some tests. See the commits for details.

I have obtained image files from boot_a and boot_b. It doesn't extract anything. Magiskboot does extract only the Kernel and Ramdisk with errors: ``` HEADER_VER [3] KERNEL_SZ [36788736] RAMDISK_SZ [3448646]...