pndwal

Then please stop spamming this issue...

> What is your "spamming" definition? Things not relevant to the issue... However it is now clear that STRONG_INTEGRITY is not being used as yet by google apps or bypassed...

> use safetynet fix mod [safetynet fix mod]... Please see @Displax link for Play Integrity Api bypass #207 above; Pending fix for this and other issues per: https://github.com/kdrag0n/safetynet-fix/pull/207#issuecomment-1194661739

Playstore now uses new Play Integrity API. An extra triger is needed to bypass hardware keystore attestation for this for many devices, especially w/ A11+. With Android 10 and below...

Check: When Odin flashing - Flashing all 4 binaries? - transferring files using ADP pull, not MTP?

👍... Did you try the CI built? ... Symptoms don't have to be the same across devices for same issue... Canyie will have scrutinized your logs to see issue... Hers...

Same same... Continuous integration build... Click the link she gave, scroll to bottom, download artifacts zip, extract and try Magisk build in that... Use debug (for verbose logs etc and...

Key fixes merged are: topjohnwu pushed a commit that referenced this issue [9 days ago](https://github.com/topjohnwu/Magisk/issues/6095#ref-commit-52ba6d1) @canyie [Don't let remote errors crash Zygisk](https://github.com/topjohnwu/Magisk/commit/52ba6d11bca116008d8df0c53ffa4942f4f5dc5c) … [52ba6d1](https://github.com/topjohnwu/Magisk/commit/52ba6d11bca116008d8df0c53ffa4942f4f5dc5c) Fix https://github.com/topjohnwu/Magisk/issues/6095 and topjohnwu pushed a...

... just scanned your issue again... Noticed > Since 23 Magisk version with Android 10, I have trouble to install Magisk when following the [default instructions](https://topjohnwu.github.io/Magisk/install.html) , appear the version...

> > https://topjohnwu.github.io/Magisk/boot.html > > Is there a way to check in which type [1,2,3,4]category does my device belongs to Type III (A-only legacy SAR) in John's doc. I posted...