Explanation and my thoughts:
There is official TWRP for Samsung Galaxy A20s, but it is not flasheable because doesn't allow it - hash mismatch.
Tried everything: empty vbmeta, google disable-verify vbmeta, some other vbmeta, nothing seems to stop it from mismatch error.
Are there any workaround for recovery partition? I know that you can flash null binaries to break binary checking but afaik it works only for system and vendor. Just some common sense - recovery gets overriden automatically and booting into the recovery on boot won't get anything because it is empty. Booting = overriden.
So there's my questions:
1) Is it possible to bypass that broken hash check?
2) Does Android 9 aboot + vaultkeeper bypass work?
There is official TWRP for Samsung Galaxy A20s, but it is not flasheable because doesn't allow it - hash mismatch.
Tried everything: empty vbmeta, google disable-verify vbmeta, some other vbmeta, nothing seems to stop it from mismatch error.
Are there any workaround for recovery partition? I know that you can flash null binaries to break binary checking but afaik it works only for system and vendor. Just some common sense - recovery gets overriden automatically and booting into the recovery on boot won't get anything because it is empty. Booting = overriden.
So there's my questions:
1) Is it possible to bypass that broken hash check?
2) Does Android 9 aboot + vaultkeeper bypass work?