This user have a device with the original keybox banned, Google revoked it. He didn't touch persist neither reprogrammed the TEE:

https://t.me/playfixnext/1/56815
https://t.me/playfixnext/1/56856

Now, using stock rom with locked bootloader, he can only pass BASIC verdict, no DEVICE neither STRONG.

What is the solution? Replacing motherboard? No, the keybox is the original one, you will need to buy a new phone.

Welcome to 1984! Google now decides what device is secure or not.

That device keyboxes are leaked...

That OEM really likes to leak keyboxes holy sh*t

All pubic keyboxes are banned now, including mine. RIP 💀

It looks like Lava mistakenly put kkb_pri (decryption key) files next to mtk's EncSW binary keybox in some of their ROM packages. This is most likely why the keys became compromised.

abount EncSW keyboxes on mtk see https://blog.csdn.net/weixin_42135087/article/details/106761192 (in Chinese)

As an OEM you should not put kkb_pri, etc... files next to the bin keybox in your ROM packages, otherwise you will compromise your keys.

in other words: kkb_pri + kb.bin = key compromise

DroidGuard will ignore some checks if you use old fingerprints, like Magisk one. That's why he's passing Strong with Magisk (and unbanned keybox)

Also few new fingerprints have this checks disabled like husky beta

Key Attestation Demo app updated!

Now it includes Secret Mode! Certificate serial numbers and dates will be hidden when it's enabled.

Also I disabled (by default) attest device ids, strongbox...

Commit: https://github.com/chiteroman/KeyAttestation/commit/34bf394db19bd70b3e507a186a4e6ed15d53b927

Stop asking me about an unbanned keybox, Google banned all my working keyboxes few days ago. No more Strong for me 🥲

It's difficult to find one, also, don't buy them, it's 99% a scam.

v16.6 stable release!

https://github.com/chiteroman/PlayIntegrityFix/releases/tag/v16.6

Changelog:
- Change fingerprint to fix RCS
- Misc improvements

v16.7 released!

https://github.com/chiteroman/PlayIntegrityFix/releases/tag/v16.7

Changelog:
- Unsigned custom ROMs (signed with test keys) should pass Device verdict. Thanks to @uid_6193534835
- Fix bootloops on PixelOS custom ROM

v16.9 released!

https://github.com/chiteroman/PlayIntegrityFix/releases/tag/v16.9

New fingerprint to pass Device 👍

I think Google banned husky fingerprint for RCS (same issue like sailfish)

If you want RCS -> search a private fingerprint