README.md: Expand notes for Strong Integrity #551
Conversation
Better explanation for strong integrity
|
v18.6 already can pass new device verdict without tricky store |
Maybe actually provide accurate info?
|
@KOWX712, Cheers for picking up on that |
Thisisauser6443
changed the title
Do a better job of removing unnecessary stuff. (I mean seriously, I strive as best as I can for perfection, and I still make these errors anyway)
Perfection at the first attempt, as you can tell, is by no means easy. This should make it more prominent that the majority of folks don't need to follow this path
|
if you want, you can write and for the thread for Tricky Store, have many info about this, maybe not all in the OP, but in all others pages, useful info from @osm0sis and others users. |
Yeah if you like breaking people's Play Store... 🤔🙄 It's meant to be an undocumented experimental/testing feature, and should remain that way until someone has a solution for the breakage. Was hoping chiteroman might actually have something to offer in this regard, but instead he just hastily ported it from my fork and released it as a public feature, initially enabled by default until he force pushed and reuploaded a new build... 🤦♂️🤷♂️ |
In fact it can't, simply because new "improved" verdicts require HW attestation and PIF can only pass DEVICE using SW attestation... It can pass with legacy ("historical") verdict evaluations for devices running A13+ w/o TS at best when legacy Android (<A13) is spoofed. |
Yeah, forget about keeping things short and sweet. This really needed some explanation on the May 2025 verdict requirements
|
Right, I've tried my best to do a decent summary of the May 2025 verdicts' effects and the |
|
There is no room for the Tricky Store thread ? 🤔 |
Are you referring to the XDA thread? Or, am I way off? 😅 |
Yeah, sorry not mentioned that. 😅 |
Ah, gotcha now, lol. Didn't even realise you're the OP of the thread, lmfao I'll get that committed over, in a couple of minutes |
Stick in the XDA thread for TS, since it's not mentioned in the README
Yeah, sorry for not mentioned before. |
Well, as you wanted the other day, here's a better (but annoyingly lengthy, since my coherency in English likes to nosedive, for some reason) explanation for strong integrity
Hopefully this is up to scratch, because man I think I rushed this to absolute oblivion, lol