How to sign boot.img and vbmeta.img by my given PEM keyrings?
How to sign boot.img and vbmeta.img by my given PEM keyrings?
[hd_scania@artixlinux split_img]$ locate -i twrp|grep 125|grep home/data/terminal/Android|grep -Ee 'img|pem'
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/recovery.img
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/recovery.img
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/repackimg.sh
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/unpackimg.sh
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/bin/androidbootimg.magic
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/bin/avb/verity.x509.pem
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/bin/linux/aarch64/mkbootimg
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/bin/linux/aarch64/pxa-mkbootimg
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/bin/linux/aarch64/pxa-unpackbootimg
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/bin/linux/aarch64/unpackbootimg
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/bin/linux/x86_64/mkbootimg
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/bin/linux/x86_64/pxa-mkbootimg
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/bin/linux/x86_64/pxa-unpackbootimg
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/bin/linux/x86_64/unpackbootimg
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/ramdisk/publiccert.pem
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-base
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-board
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-cmdline
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-dtb
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-dtb_offset
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-hashtype
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-header_version
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-imgtype
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-kernel_offset
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-origsize
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-os_patch_level
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-os_version
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-pagesize
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-ramdisk.cpio.gz
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-ramdisk_offset
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-ramdiskcomp
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-recovery_dtbo
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-second_offset
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-tags_offset
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/outputs/split_img/recovery.img-zImage
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/prebuilt/dtb.img
/home/data/terminal/Android/recoveries/TWRP-Samsung-A12-SM-A125F/SM-A125F/samsung/a12/prebuilt/dtbo.img
(13-05-2021, 04:36 AM)hd_scania ...
(19-05-2021, 05:38 AM)hd_scania Yes i’m asking a question.See @ https://www.hovatek.com/forum/thread-32674.html
(19-05-2021, 05:38 AM)hd_scania Yes i’m asking a question.
(22-05-2021, 08:13 AM)hovatek(19-05-2021, 05:38 AM)hd_scania Yes i’m asking a question.
For a Samsung device? I doubt this will work unless you have their keys (which I doubt you do).
% sudo python avbtool info_image --image vbmeta.TWRP.SM-A125F.AOSP11.hd_scania.img
Minimum libavb version: 1.0
Header Block: 256 bytes
Authentication Block: 0 bytes
Auxiliary Block: 7168 bytes
Algorithm: NONE
Rollback Index: 0
Flags: 2
Rollback Index Location: 0
Release String: 'avbtool 1.2.0'
Descriptors:
Chain Partition descriptor:
Partition Name: recovery
Rollback Index Location: 5
Public key (sha1): dd09a73809857f69ede842d26cfc9a405376b092
Chain Partition descriptor:
Partition Name: prism
Rollback Index Location: 10
Public key (sha1): 42a98eff97ac1681b78d4eb9537e2c1cb8a713a5
Chain Partition descriptor:
Partition Name: optics
Rollback Index Location: 11
Public key (sha1): 9fb2834ee7157e3a1a56eeae2f9e7009fdc83421
Chain Partition descriptor:
Partition Name: boot
Rollback Index Location: 1
Public key (sha1): 3f5036b58fe19ce5a4e114cb43bc559e5b8e551c
Chain Partition descriptor:
Partition Name: bootloader
Rollback Index Location: 2
Public key (sha1): 5378c0544d923494c71135a00bc0ad6a1aff136d
Chain Partition descriptor:
Partition Name: lk
Rollback Index Location: 3
Public key (sha1): 21aca3ad57f377072e2e37e315f1976d7d2c2bb5
Chain Partition descriptor:
Partition Name: tee1
Rollback Index Location: 4
Public key (sha1): dac56424ec71cb51a3cacff00c3a1483c91f1c37
Chain Partition descriptor:
Partition Name: odm
Rollback Index Location: 6
Public key (sha1): c3c3473008a42459f797909a39cbd78fb25d01a5
Chain Partition descriptor:
Partition Name: product
Rollback Index Location: 7
Public key (sha1): 73b2bfaf62ac731e38b363c9a7f6dba83c36eefc
Chain Partition descriptor:
Partition Name: system
Rollback Index Location: 8
Public key (sha1): cad59e4b2cebe32dfc86c4c166f7e4c1364932ac
Chain Partition descriptor:
Partition Name: vendor
Rollback Index Location: 9
Public key (sha1): b7b90caccbfbd91a0752d0325d33afe468ac68e1
%
(02-06-2021, 12:04 PM)hd_scania No doubts that i dunno where to get the Samsung keys for my device, either from online or firmware extracts