Hovatek Forum DEVELOPMENT Android How to sign boot.img and vbmeta.img by my given PEM keyrings?
Can't login? Please, reset your password.
Hovatek is recruiting! Apply Now


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?

Pages (2): 1 2 Next
hd_scania
hd_scania
hd_scania
Junior Member
18
13-05-2021, 04:36 AM
#1



Those boot.img and vbmeta.img i sign by the given PEM keyrings are for my own TWRP
Code:

[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
hovatek
hovatek
hovatek
Administrator
49,570
15-05-2021, 03:00 PM
#2
(13-05-2021, 04:36 AM)hd_scania ...

Are you asking a question or what?

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
hd_scania
hd_scania
hd_scania
Junior Member
18
19-05-2021, 05:38 AM
#3
Yes i’m asking a question. Smile
Abdulakeem14
Abdulakeem14
Abdulakeem14
Senior Member
1,757
19-05-2021, 09:11 AM
#4
(19-05-2021, 05:38 AM)hd_scania Yes i’m asking a question. Smile
See @ https://www.hovatek.com/forum/thread-32674.html
hovatek
hovatek
hovatek
Administrator
49,570
22-05-2021, 08:13 AM
#5



(19-05-2021, 05:38 AM)hd_scania Yes i’m asking a question. Smile

For a Samsung device? I doubt this will work unless you have their keys (which I doubt you do).
This post was last modified: 22-05-2021, 08:13 AM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
hd_scania
hd_scania
hd_scania
Junior Member
18
02-06-2021, 12:04 PM
#6
No doubts that i dunno where to get the Samsung keys for my device, either from online or firmware extracts
(22-05-2021, 08:13 AM)hovatek
(19-05-2021, 05:38 AM)hd_scania Yes i’m asking a question. Smile

For a Samsung device? I doubt this will work unless you have their keys (which I doubt you do).
This post was last modified: 02-06-2021, 12:05 PM by hd_scania.
hd_scania
hd_scania
hd_scania
Junior Member
18
03-06-2021, 09:50 AM
#7
But for sure i have my own public keys from the RAM disk extracts when building my own TWRP by the stock recovery for my Samsung A12 whose chipsets are MT6765.
Hope this helps.
hd_scania
hd_scania
hd_scania
Junior Member
18
03-06-2021, 09:57 AM
#8
Code:

% 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
%
X3non
X3non
X3non
Recognized Contributor
22,062
03-06-2021, 10:24 AM
#9
(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

replied to @ https://www.hovatek.com/forum/thread-390...#pid214578
hd_scania
hd_scania
hd_scania
Junior Member
18
03-06-2021, 01:18 PM
#10



But my TWRP isn’t starting yet, instead a boot loop is still being triggered, even with everything vbmeta and TWRP appearing normal.
Pages (2): 1 2 Next
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram