[omuitk]

avbtool add_hash_footer --image boot.img --partition_name boot --partition_size 36700160 --key testkey_rsa4096.pem --algorithm SHA256_RSA4096
After using the above command to sign boot.img, the official brush tool cannot be brushed. As far as I know, officials use public keys, but the boot.img I generated is completely different from officials. What's the question?

The official on the left of the picture, the one on the right is generated by me, but it is different from the boot.bin extracted by vbmeta. Isn't the official testkey_rsa4096.pem used?

QQ图片20200715205128.png Size: 211.87 KB  Downloads: 15

[X3non]

avbtool add_hash_footer --image boot.img --partition_name boot --partition_size 36700160 --key testkey_rsa4096.pem --algorithm SHA256_RSA4096
After using the above command to sign boot.img, the official brush tool cannot be brushed. As far as I know, officials use public keys, but the boot.img I generated is completely different from officials. What's the question?

The official on the left of the picture, the one on the right is generated by me, but it is different from the boot.bin extracted by vbmeta. Isn't the official testkey_rsa4096.pem used?

this testkey_rsa4096.pem ; is it the same private key you used when creating your custom vbmeta?
you should use the same private key you use when creating vbmeta to sign the boot.img then flash the vbmeta first before attempting to flash the signed boot

[hovatek]

avbtool add_hash_footer --image boot.img --partition_name boot --partition_size 36700160 --key testkey_rsa4096.pem --algorithm SHA256_RSA4096
After using the above command to sign boot.img, the official brush tool cannot be brushed. As far as I know, officials use public keys, but the boot.img I generated is completely different from officials. What's the question?

The official on the left of the picture, the one on the right is generated by me, but it is different from the boot.bin extracted by vbmeta. Isn't the official testkey_rsa4096.pem used?

You should be using fastboot to flash this self-signed boot.img, not research download tool for many reasons.
BTW, you need to have signed the boot partition (when creating vbmeta) with a public key that corresponds to the private key used to sign the boot.img in your command above.
Read https://www.hovatek.com/forum/thread-32674.html and take note of the requirements part

[omuitk]

avbtool add_hash_footer --image boot.img --partition_name boot --partition_size 36700160 --key testkey_rsa4096.pem --algorithm SHA256_RSA4096
After using the above command to sign boot.img, the official brush tool cannot be brushed. As far as I know, officials use public keys, but the boot.img I generated is completely different from officials. What's the question?

The official on the left of the picture, the one on the right is generated by me, but it is different from the boot.bin extracted by vbmeta. Isn't the official testkey_rsa4096.pem used?

this testkey_rsa4096.pem ; is it the same private key you used when creating your custom vbmeta?
you should use the same private key you use when creating vbmeta to sign the boot.img then flash the vbmeta first before attempting to flash the signed boot

this testkey_rsa4096.pem,Using the public key，Because I see that vbmeta is also generated by the public key

[omuitk]

avbtool add_hash_footer --image boot.img --partition_name boot --partition_size 36700160 --key testkey_rsa4096.pem --algorithm SHA256_RSA4096
After using the above command to sign boot.img, the official brush tool cannot be brushed. As far as I know, officials use public keys, but the boot.img I generated is completely different from officials. What's the question?

The official on the left of the picture, the one on the right is generated by me, but it is different from the boot.bin extracted by vbmeta. Isn't the official testkey_rsa4096.pem used?

You should be using fastboot to flash this self-signed boot.img, not  research downloadtool for many reasons.
BTW, you need to have signed the boot partition (when creating vbmeta) with a public key that corresponds to the private key used to sign the boot.img in your command above.
Read https://www.hovatek.com/forum/thread-32674.html and take note of the requirements part

fastboot should unlock bootloader，but research download Is not needed

[hovatek]

fastboot should unlock bootloader，but research download Is not needed

In theory, yes but have you considered that the phone might get bricked when you force-flash a modified file on a locked bootloader?