Closed hamjin closed 10 months ago
I tried the boot.img under Windows with PowerShell, "pack" works fine. Can you manually try the command below?
cp boot.img.clear boot.img.signed2
python aosp/avb/avbtool.v1.2.py add_hash_footer --image boot.img.signed2 --flags 0 --partition_size 67108864 --salt fee26850765b9f55f73e2848f5253596918e1cc23012ee0cf22d635c76fe5709 --partition_name boot --hash_algorithm sha256 --algorithm SHA256_RSA2048 --rollback_index 0 --key aosp/avb/data/testkey_rsa2048.pem --prop com.android.build.boot.os_version:13 --prop com.android.build.boot.fingerprint:Xiaomi/hal_mgvi_64_armv82_mt6985_cn/mgvi_64_armv82:13/TP1A.220624.014/V816.0.9.0.UMLCNXM:user/release-keys --prop com.android.build.boot.security_patch:2024-01-01 --internal_release_string "avbtool 1.2.0"
hi,
I'm getting the same error when trying to work on a samsung vendor_boot. Even trying the 2 commands from above (adapted to my details). I tried both, wincmd and powershell.
thanks
cp boot.img.clear boot.img.signed2 python aosp/avb/avbtool.v1.2.py add_hash_footer --image boot.img.signed2 --flags 0 --partition_size 67108864 --salt fee26850765b9f55f73e2848f5253596918e1cc23012ee0cf22d635c76fe5709 --partition_name boot --hash_algorithm sha256 --algorithm SHA256_RSA2048 --rollback_index 0 --key aosp/avb/data/testkey_rsa2048.pem --prop com.android.build.boot.os_version:13 --prop com.android.build.boot.fingerprint:Xiaomi/hal_mgvi_64_armv82_mt6985_cn/mgvi_64_armv82:13/TP1A.220624.014/V816.0.9.0.UMLCNXM:user/release-keys --prop com.android.build.boot.security_patch:2024-01-01 --internal_release_string "avbtool 1.2.0"
Tried and found that openssl
is still missing after choco install openssl
. After choco install openssl --force
the problem is solved
Failed when original image doesn't have AVB footer
Original boot is extracted from Redmi K60 Ultra Xiaomi HyperOS OS1.0.9.0.UMLCNXM boot.img.gz