chenxiaolong
commented
4 days ago Thanks for uploading the boot.img! It looks like it's a u-boot FIT image, not a standard Android boot image. I've never seen this combo of AVB 2.0 + non-Android boot image format before.
It's unlikely I'll add support parsing these boot images. The format is quite a bit more complex to parse than standard Android boot images and it's not very common. The best I could do is maybe add a --skip-ota-certs option, which in addition to --rootless, would make avbroot not touch the boot image at all (it would only do AVB and OTA signing).
❯ mkimage -l boot.img
Image contains unit addresses @, this will break signing
FIT description: U-Boot fitImage for Android 147456/4.9/auto2712m1v1-initramfs
Created: Mon Sep 11 03:51:55 2023
Image 0 (kernel@1)
Description: Linux kernel
Created: Mon Sep 11 03:51:55 2023
Type: Kernel Image
Compression: lz4 compressed
Data Size: 11582667 Bytes = 11311.20 KiB = 11.05 MiB
Architecture: ARM
OS: Linux
Load Address: 0x40008000
Entry Point: 0x40008000
Hash algo: sha256
Hash value: dfde18fbb1d1fee962eebad7a548de59ca95e6eaea403792496edbd8ded522a7
Image 1 (ramdisk@1)
Description: Ramdisk Image
Created: Mon Sep 11 03:51:55 2023
Type: RAMDisk Image
Compression: uncompressed
Data Size: 7961761 Bytes = 7775.16 KiB = 7.59 MiB
Architecture: ARM
OS: Linux
Load Address: 0x4a000000
Entry Point: 0x4a000000
Hash algo: sha256
Hash value: def3f7cee122d0951c070626c7ff1d17b6a6d36f06d959ed5aea172fde4f8019
Image 2 (fdt@1)
Description: Flattened Device Tree blob
Created: Mon Sep 11 03:51:55 2023
Type: Flat Device Tree
Compression: uncompressed
Data Size: 98058 Bytes = 95.76 KiB = 0.09 MiB
Architecture: ARM
Load Address: 0x44000000
Hash algo: sha256
Hash value: 1bb0072041178e90ad866eeffa7f6a08b4d57c94f777bec76b44f50e95167778
Default Configuration: 'conf@1'
Configuration 0 (conf@1)
Description: Boot Linux kernel with FDT blob
Kernel: kernel@1
Init Ramdisk: ramdisk@1
FDT: fdt@1
Sign algo: sha256,rsa2048:dev
Sign value: unavailable
Timestamp: unavailabledumpimage -T flat_dt -p 0 -o kernel boot.img
dumpimage -T flat_dt -p 1 -o ramdisk boot.img
dumpimage -T flat_dt -p 2 -o devicetree boot.img
lkernan
Hi, I'm doing some playing around with an OTA image for my cars infotainment unit. It's running Android 9.
avbroot had no problems extracting the boot image, but when I do a boot info command I get the error:
leon@cartman:~/Downloads/avbroot$ ./avbroot boot info -d --log-level trace --input boot.img 0.000s DEBUG cli=Cli { command: Boot(BootCli { command: Info(InfoCli { input: "boot.img" }), quiet: false, debug: true }), log_level: Level(Trace), log_format: Short } 0.000s ERROR Failed to read boot image: "boot.img"
Caused by: Unknown boot image format
I've verified it has extracted the boot image correctly.
My plan is to use the --rootless option since I mainly want to patch a file on the system partition.
The car manufacturer put some firewall commands in to block ADB port 5555 on all interfaces so at the moment we don't have ADB and I need to patch them out.
One thing we do know is that they signed everything with the test-keys so that part is not a concern.
A copy of the boot.img can be found here: https://www.dropbox.com/scl/fi/6edbvsk43gcv17j4kkh51/boot.img?rlkey=pbgktsrbnyidzm7jmh0j5tti3&st=nehlziw7&dl=0