Hovatek Forum DEVELOPMENT Android Alldocube iplay 20 (Unisoc) - Signing Custom Vbmeta/partitions
Can't login? Please, reset your password.
Hovatek is recruiting! Apply Now


Alldocube iplay 20 (Unisoc) - Signing Custom Vbmeta/partitions

Alldocube iplay 20 (Unisoc) - Signing Custom Vbmeta/partitions

natureboy
natureboy
natureboy
Newbie
1
10-09-2020, 03:37 PM
#1



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.
This post was last modified: 12-09-2020, 09:56 AM by natureboy.
X3non
X3non
X3non
Recognized Contributor
22,062
11-09-2020, 01:44 PM
#2
(10-09-2020, 03:37 PM)natureboy ...
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.

1. yes, you need to replace the partitions and arrange them just as they appear in your original vbmeta
2. fastboot flash vbmeta your_custom_vbmeta.img
3. yes, your custom vbmeta must have all partitions exactly like in the the same order as the original vbmeta. notice that dtbo is different from the rest, the argument for adding dtbo
Code:

--include_descriptors_from_image path_to_your_dtbo.img

see e.g in the command under Extra @ https://www.hovatek.com/forum/thread-35862.html
This post was last modified: 11-09-2020, 01:46 PM by X3non.
JamesAt15
JamesAt15
JamesAt15
Newbie
4
25-09-2020, 03:19 AM
#3
Natureboy, were you able to sign a custom vbmeta for the iplay 20?

I recently bought an iplay 20 as well, and I have unlocked the bootloader. I would like to do the same as you were planning, so if you have any suggestions I would very much like to hear them.
X3non
X3non
X3non
Recognized Contributor
22,062
25-09-2020, 02:39 PM
#4
(25-09-2020, 03:19 AM)JamesAt15 Natureboy, were you able to sign a custom vbmeta for the iplay 20?

I recently bought an iplay 20 as well, and I have unlocked the bootloader. I would like to do the same as you were planning, so if you have any suggestions I would very much like to hear them.

while waiting, why don't you make an attempt yourself
and if you have problems then be sure to create a new thread for it
JamesAt15
JamesAt15
JamesAt15
Newbie
4
25-09-2020, 02:45 PM
#5



Okay, I'll give it a try sometime soon. Cheers.
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram