I am unable to boot the /e/ Recovery image “recovery-e-0.18-r-20211003138900-dev-d2s” after successful download. Error is “recovery: Public key used to sign data does not match key in chain partition descriptor.” as shown in the image.
Trying the latest 3 versions of TWRP “twrp-3.5.2_9-5-d2s”, I get “recovery: error validating footer.” and “recovery: Error verifying vbmeta image: invalid vbmeta header”.
Have you flashed the proposed vbmeta before or when flashing TWRP ?
According from twrp
If you wish to install TWRP without rooting, there are numerous pitfalls to consider. For example, a stock device is protected by Android Verified Boot. This is implemented as a vbmeta partition that contains cryptographic digests for verifying the integrity of boot.img, recovery.img and other partitions/images. Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot.
Ok, so I moved past this issue and encountered what is hopefully the last part to getting this working.
In summary, the latest boot verification mechanism includes checking the signature on the vbmeta.img, regardless of whether boot image verification is disabled therein. There are ways to generate new or copy existing certificates for this, or ways to bypass the signing altogether.
I’m glad you mentioned that. I have tried probably 7 or 8 different vbmeta.img files for the 975F from various sources, including the official TWRP (which I was sure would have the correct key) with no success. Perhaps I’m doing something else wrong.
So I started again from scratch, and I still get the “HASH_MISMATCH”. I wonder if there is a possibility that one of these files was updated and the keys were never updated to match.