[Tutorial] How to create a custom signed vbmeta.img for Unisoc using AVBtool
[Tutorial] How to create a custom signed vbmeta.img for Unisoc using AVBtool
(10-09-2020, 02:50 PM)Denny83 I'm managing with your tutorials to create my own vbmeta to flash a boot image...some questions:
1 if I unlock bootloader like you show in this post https://www.hovatek.com/forum/thread-32287.html - then i can sign vbmeta with the .pem key used to unlock bootloader?
2 I have a vbmeta image as in attached file vbmeta_info.txt; is it correct to make my vbmeta to run this command: python avbtool.py make_vbmeta_image --key denny2048.pem --algorithm SHA256_RSA2048 --flag 2 --chain_partition recovery:1:keys/recovery.bin --chain_partition vbmeta_sysstem:2:keys/vbmeta_system.bin --chain_partition vbmeta_vendor:4:keys/vbmeta_vendor.bin --chain_partition boot:3:keys/boot.bin --padding_size 12288 --output vbmeta-sign-custom.img
3 my vbmeta is Image Size: 46976 bytes ---how can i obtain vbmeta image with this size?
thanks for reply
>python vbmeta-custom.img
File "vbmeta-custom.img", line 1
SyntaxError: Non-ASCII character '\x91' in file vbmeta-custom.img on line 2, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details
(12-03-2020, 11:51 PM)hovatek ...
Code:python avbtool make_vbmeta_image --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096 --flag 2 --chain_partition boot:1:keys/key_boot.bin --chain_partition system:3:keys/key_system.bin --chain_partition vendor:4:keys/key_vendor.bin --chain_partition product:10:keys/key_product.bin --chain_partition dtbo:9:keys/key_dtbo.bin --chain_partition recovery:2:keys/hovatek.bin --chain_partition l_modem:5:keys/key_l_modem.bin --chain_partition l_ldsp:6:keys/key_l_ldsp.bin --chain_partition l_gdsp:7:keys/key_l_gdsp.bin --chain_partition pm_sys:8:keys/key_pm_sys.bin --chain_partition dtb:11:keys/key_dtb.bin --padding_size 16384 --output vbmeta-sign-custom.img
(05-12-2020, 11:07 AM)_Jaqb_(12-03-2020, 11:51 PM)hovatek
...
Code:
python avbtool make_vbmeta_image --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096 --flag 2 --chain_partition boot:1:keys/key_boot.bin --chain_partition system:3:keys/key_system.bin --chain_partition vendor:4:keys/key_vendor.bin --chain_partition product:10:keys/key_product.bin --chain_partition dtbo:9:keys/key_dtbo.bin --chain_partition recovery:2:keys/hovatek.bin --chain_partition l_modem:5:keys/key_l_modem.bin --chain_partition l_ldsp:6:keys/key_l_ldsp.bin --chain_partition l_gdsp:7:keys/key_l_gdsp.bin --chain_partition pm_sys:8:keys/key_pm_sys.bin --chain_partition dtb:11:keys/key_dtb.bin --padding_size 16384 --output vbmeta-sign-custom.img
I noticed that the flags in output vbmeta-sign-custom.img code are set to "2" while in stock vbmeta-sign.img to "0". What does it mean?
(05-12-2020, 11:07 AM)_Jaqb_ I noticed that the flags in output vbmeta-sign-custom.img code are set to "2" while in stock vbmeta-sign.img to "0". What does it mean?