10-09-2020, 03:37 PM
Hello,
after successfully unlocking the bootloader using the guide in this forum, and with the goal of rooting the device, I'm now at the stage of signing a custom vbmeta.img. This is a Unisoc device btw.
Now having run the avbtool with the info_image option I get the following:
Code:
Minimum libavb version: 1.0
Header Block: 256 bytes
Authentication Block: 576 bytes
Auxiliary Block: 13568 bytes
Algorithm: SHA256_RSA4096
Rollback Index: 0
Flags: 0
Release String: 'avbtool 1.1.0'
Descriptors:
Chain Partition descriptor:
Partition Name: boot
Rollback Index Location: 1
Public key (sha1): ea410c1b46cdb2e40e526880ff383f083bd615d5
Chain Partition descriptor:
Partition Name: dtbo
Rollback Index Location: 10
Public key (sha1): ea410c1b46cdb2e40e526880ff383f083bd615d5
Chain Partition descriptor:
Partition Name: recovery
Rollback Index Location: 2
Public key (sha1): d9093b9a181bdb5731b44d60a9f850dc724e2874
Chain Partition descriptor:
Partition Name: socko
Rollback Index Location: 11
Public key (sha1): bc688cacacd959cfaafbf0549d080d6fc2d50a08
Chain Partition descriptor:
Partition Name: odmko
Rollback Index Location: 12
Public key (sha1): 425215859f49f31809f16491c2a67e04df79baaf
Chain Partition descriptor:
Partition Name: vbmeta_system
Rollback Index Location: 3
Public key (sha1): e2c66ff8a1d787d7bf898711187bff150f691d27
Chain Partition descriptor:
Partition Name: vbmeta_vendor
Rollback Index Location: 4
Public key (sha1): 9885bf5bf909e5208dfd42abaf51ad9b104ee117
Chain Partition descriptor:
Partition Name: l_modem
Rollback Index Location: 6
Public key (sha1): e93e7d91ba1a46b81a5f15129b4dc5769bf41f26
Chain Partition descriptor:
Partition Name: l_ldsp
Rollback Index Location: 7
Public key (sha1): e93e7d91ba1a46b81a5f15129b4dc5769bf41f26
Chain Partition descriptor:
Partition Name: l_gdsp
Rollback Index Location: 8
Public key (sha1): e93e7d91ba1a46b81a5f15129b4dc5769bf41f26
Chain Partition descriptor:
Partition Name: pm_sys
Rollback Index Location: 9
Public key (sha1): e93e7d91ba1a46b81a5f15129b4dc5769bf41f26
The hash of the public keys are similar to the ones posed here: https://www.hovatek.com/forum/thread-32666.html, but some partitions are named differently. So I several questions:
1 - Do I just replace the partition names in the avbtool make_vbmeta_image command to match the names of my partitions?
2 - What is the command to flash the vbmeta to the device using fastboot?
3 - I have additional partitions (socko, odmko), do they need to be included in the above command? Do I have to extract ALL the public keys for each partition, therefore I can't use the generic keys provided despite them being the same for the other partitions?
Device is running Android 10.
Thanks for the help.