yashsingh1/xdaforums huggingface dataset:
[Magisk] hadesflames:
So, I tried this. I have play protect saying "Device is certified" however after following those steps I just see "RCS chats aren't available for this device"
[Magisk] markfm:
Alternately, if you have a terminal app on your phone that's been granted root access, enter:

su -c killall com.google.android.gms.unstable

(I use termux, but other terminal shell apps should work the same)

The screenshot is from when I used the terminal method to test a couple of json files (doing a PI check between runs of the command). The up arrow to the right of "HOME" brings up previously entered commands.

View attachment 6079031
[Magisk] pershoot:
Give it a short time; it should become available for you to go in to.
[Magisk] Vision:
Yeah, a discussion for TEE/keybox/etc

That would the best, and if any of users try all this and can help the other, only in this discussion
[Magisk] hadesflames:
Still same message
[Magisk] pershoot:
Ensure you have an entry for your device on the 'phone' (myaccount), page. At any rate, if you do not see it become available (i observed it takes a few minutes after recovery has started), go back to square one, commencing at clear and try again.
[Magisk] markfm:
When you do a Play Integrity check, do you pass Device integrity?

I just installed Google Messages today. It went through setup, including RCS, cleanly.
[Magisk] pershoot:
You must ensure you pass DEVICE (I gave how to check in the initial reply). Please invoke a test prior to all of this.
[Magisk] hadesflames:
I do see the entry on my account and I can enable it from my device. I suppose I'll keep trying. One thing I might mention is I have messages installed as a system app (nikgapps) and when I clear data from messages and carrier services my messages don't actually go away. I mean, after opening the app it goes through the mini setup thing and my account gets selected but there's no period of waiting for messages to repopulate from backup.

Yeah it should be passing device integrity according to google play and the fact that google wallet is working just fine at the moment.
[Magisk] pershoot:
You should run a live test for validation, to ensure you are not seeing a cached result; enable developer settings and perform it.
[Magisk] markfm:
So you checked Play Integrity directly from Play Store?

View attachment 6079057
[Magisk] hadesflames:
This is what I get right now from play integrity:

View attachment 6079060
[Magisk] pershoot:
Looks good; try to clear things out again and re-try.
[Magisk] hadesflames:
View attachment 6079064

Finally, thanks for the help. I also noticed that carrier services never came back up after the force stop. So I also uninstalled updates and then reinstalled before opening messages again. RCS working :D
[Magisk] niko26:
Thanks! Have you seen my pm? I have sent you a question as a pm avoiding to clutter up this thread further.
[Magisk] markfm:
My s20+ is Android 13.

Hopefully the su... In a terminal window, to kill Play services, that I posted earlier would still apply up through at least A14.
[Magisk] wfred:
Strange that yours is grayed out. I can force stop my 1+ 11, it's what I was doing when I swapped out pifs (running A14)
[Magisk] GN-z11:
I'll come of as extremely nub on this one, but is the error below caused by PE having its own FP than the device should have?
[Magisk] fma388:
So, if I've followed the latest news correctly, Google has banned around 95% of known fingerprints. (Mine, which had been working for months, and all the others I'd kept secret... :cry:).

So I have several questions:

- Is it legitimate to play with Xiaomi's fingerprints while waiting to find one that works?

(Won't this contribute to the banning of more fingerprints than expected?)

- Won't this cat-and-mouse game completely block us in the near future, given Google's banning speed?

I don't even know where to look for valid fingerprints anymore, those from my old phones have been banned and those from the few websites I could find too.. :cry:

PS : I've been following the various projects for several months, and I'd like to be able to help, but I don't know anything about development. (I'm just a poor network & system admin :ROFLMAO:).
[Magisk] dmenezes:
Must have been what caught me too...

Today I noticed my custom FP that had been working since I mined it in 2023-12-02 has stopped working: no more MEETS_DEVICE_INTEGRITY, just MEETS_BASIC_INTEGRITY. Last time I checked it was in 2024-02-20 and it was working...

So I checked and my kernel doesn't have any of the banned strings, just version plus "qgki" and an hex string.

Then I upgraded to @osm0sis's PlayIntegrityFix-v8 (had been using @chiteroman's v14.0-resetprops) and moved my old pif.json file from /data/adb to /data/adb/modules/playintegrityfix, and then run `sh migrate.sh -i pif.json` which produced a custom.pif.json; killed gms and tried again, still only MEETS_BASIC_INTEGRITY.

Next step is to run @osm0sis autopif.sh to fetch the latest Xiaomi.EU and see if it gets me back MEETS_DEVICE_INTEGRITY; if it does, then I guess it's my old PIF that has been banned and I'm back to looking for build.props and trying to find another working print.

So I gotta ask: Am I on the right track? Is this the best practice as of today?

TIA!
[Magisk] 4sz0m:
Based on what you explained, yes get the xiaomi eu print, you will have device integrity until the print lasts.

Looking for other prints however has become a troublesome activity, with mostly failure. So unless you have a lot of time available, stick to the xiaomi eu print for now and join our anxiously waiting club.
[Magisk] jrotaetxe:
What are we waiting anxiously? I do not see light at the end of the tunnel. Without a clear change of strategy, our prints are going to fall one by one (or thousands by thousands). Now I feel like an anchovy swimming in the anchovy ball waiting a big mouth coming from the depths...

Today I am not the best company....
[Magisk] sawdoctor:
Short answer is nobody knows simple as that. As most of us haven't managed to find a working print we've 2 choices. Either use the one provided my xaiomi or unroot and relock bootloader if we want Google pay
[Magisk] blu.italia:
View attachment 6079246

I got a black screen after adding a credit card. Anyone know these problem? I tried all normal ways of delete cache and storage of Play Services and Play Store, nothing helps. Get both green signs. All is configured normally.

Device is Xiaomi Poco X3 Pro Vayu with latest CRDroid 10 (Android 14), Magisk 27 and latest Chiteroman Integrity Fix.
[Magisk] niko26:
Does anyone know why the Xiaomi FP still works and has not been banned? Do they know why they have not been banned? From where do they get their FP from?
[Magisk] Claus….:
Everyone would love a infinite solution, but it is not that easy. @chiteroman made huge progress with strong, so I will not say that there is no light in the end of the tunnel.
[Magisk] mrgbuzz:
Hi, trying to get my head around this process. I have a question that I hope its ok to ask here. I have an unlocked bootloader on my Poco X5 pro, I've tried a few different rom's and obviously have this wallet issue. My question being, If I try work on some of the solutions and come up with a blank, can I revert back to stock rom *was Miui 14, relock the bootloader and try from there that wallet works again?

Again, sorry for the noobish question. Thanks all.
[Magisk] blu.italia:
Solved by my way. Missing Android Web View app was the failure.
[Magisk] Vision:
I get this today, and I don't even know which of all the posts.

If i had say something wrong, I apologise.

View attachment 6079247
[Magisk] mrjuniork:
It's the one you edited as "deleted", hence I deleted it for you 😉
[Magisk] Vision:
Oh good. I appreciate

Thanks you for this (if i write as "deleted" again, you can hence deleted it for me)
[Magisk] dmenezes:
First of all, thank you for all the effort you put in for us, @osm0sis! Much appreciated!

Thanks specially for your autopif.sh, which now seems to be the quickest way out of the current Goolag-provoked mess...

I'm trying to run it under Termux, but it abends with an `Aborted` message -- and yes, I'm running the latest Termux from GitHub, and have just ran a successful `pkg update && pkg upgrade`, and I've looked through your script and manually set (with `export VAR=...`) every environmental variable that it used and couldn't be found under the `tsu` root shell.

`logcat | grep -i dalvik` (which is the command that seems to be printing that `Aborted` message) didn't seem to find anything useful.

Anyway, I then followed your previous recommendation and tried it under Connectbot, which was a pain(no TAB, CTRL etc helper 'keys' on its keyboard), but at least autopif.sh ran to completion and produced a nice custom.pif.json file, which when moved to /data/adb/modules/playintegrityfix, gave me MEETS_DEVICE_INTEGRITY back:

View attachment 6079251

Total time from the moment I noticed it was gone until recovery, about 4h -- most of it combing through this thread, and the rest trying to make autopif.sh work under Termux 😁

Thanks again and keep up the great work! 👍
[Magisk] Vision:
No because the FP read only from DroidGuard, all other apps see the original FP of your device

That called broke TEE (i think) if you have new device
[Magisk] dmenezes:
Just checking: if I understand things correctly, it would also mean dumping LineageOS and flashing the stock ROM back, right?

I could perhaps (with a lot of reluctance) bear losing root -- but there's no effing way in hell that I'm gonna lose LineageOS, I would stop using Android if it came to that.
[Magisk] dmenezes:
+1 to this.

And I'll say more: long-term, there's no way Goolag is going to win this fight. If it takes decapping the SoC with acid and then using microprobes to pull the TEE private keys from there, so be it -- it will eventually get done, it's just a matter of time and how many previously loyal users Goolag is going to piss off in the process (I've been on Android since the G1 days -- about 15 years ago -- and I'm now thoroughly pissed off with all this unnecessary drama).
[Magisk] V0latyle:
The only way to guarantee that your phone will always meet integrity requirements is to reflash the stock ROM (which reinstalls the OEM key) and lock the bootloader. Custom keys do not work as AVB reports whether the signature is OEM or custom.

The alternative is to live without whatever apps no longer work, while continuing to use LineageOS.
[Magisk] Vision:
You're on A14 and can force stop?
[Magisk] jrotaetxe:
.. And doing brute force (with probes in the uProcessor) would take you time enough to let the telepathy being evolved. All this key interchange is encrypted, so yo will not find a pattern in the behavior of the silica.

This seems not so straight...
[Magisk] sawdoctor:
Xaiomi fingerprint gets banned same as everyone else's. They've probably had more banned than anyone else due to the volume of people using it. Will thier latest print get banned yes at some stage. Where do they get the print from? The same places we have. Will they eventually run out of prints , yes. Xaiomi Devs probably had a much bigger pool of working prints than anyone else when the massacre came on 29th feb so are more likely to have a few working ones left
[Magisk] BunnyPig1:
It'll be interesting when the Xiaomi fp gets banned and if will be "the only" fingerprint that gets banned since almost everyone is using it.

Let's play with the idea that only Xiaomi's fp gets banned/blocked and nothing else since that fp is the most popular one, wouldn't it be a better solution if everyone starts using the same and we lose 1 fp per month (if it becomes a monthly thing) instead of like the massacre of 29/2 where thousands of prints died?

Just a train of thought
[Magisk] dmenezes:
It's not exactly "brute force" -- it's a very directed hardware-based attack.

It demands special resources and knowledge, yes -- but there's nothing 'magical' about it, much less impossible.

And it has been done before -- with simpler chips, even with amateur-level equipment and knowledge, eg: https://jcjc-dev.com/2020/10/20/learning-to-decap-ics/

You don't need to break the "key interchange" nor the encryption -- you just pull the keys directly from the flash part of the SoC, bit by bit.

I'm not saying it's easy -- it's certainly beyond my level of knowledge, available time, and patience. But there are people out there with plenty of that, and all it takes is for one of them to get pissed enough with Goolag to go ahead and do it

And once done, it only needs to be done once -- even if Goolag revokes the keys, the manufacturer will have to get another pair lest all their devices stop working -- and when it does, so does the guy who broke the first ones -- he just needs to update his decapped device and pull the keys again.
[Magisk] dmenezes:
or get a basic phone and keep it stock for the stupid apps that demand *_INTEGRITY, and keep using a fully rooted, custom-ROMed phone for everything else.

That's probably the way I would be going, if worst comes to worst.
[Magisk] Vision:
Yeah, exactly for that i have my old device Android 7.1.1 (only pass 2/3, is so old), the ironic is some apps need Android 8+ to work 😂🤣
[Magisk] dmenezes:
What took you so long? 🤣

Seriously, Telegram is such an unbearable cesspool of noise that I don't even have it installed on my phone. XDA is much, much better in terms of SNR and doesn't force me to install a Russia-linked, closed-source app on my phone.

> I will continue to update the module as much as possible.

Thank you for all your hard work. Without you and @osm0sis and the other developers, none of this would have been possible and Goolag would just have run over all of us custom-ROM users.
[Magisk] dmenezes:
This goes to show how much of a stupid security theater all this drama is: you can use a many-years old obsolete device missing tons of security patches and have all 3 the most necessary *_INTEGRITY checks, but can't use a fully patched, updated ROM with even DEVICE_INTEGRITY.
[Magisk] V0latyle:
While we share your frustration, let's keep the ranting to a minimum, please.
[Magisk] dmenezes:
Granted, just removed the most ranty part of my post 😁
[Magisk] Vision:
I forgot to say only pass 2/3, is so old 😂🤣
[Magisk] dmenezes:
That's a big "if"... there's nothing impeding Goolag from doing it everyday -- or even every microsecond.

That said, I find it auspicious that Xiaomi.EU's latest fingerprint is from 2024-02-29 -- and it's still working, so 12 days and counting.

If it can last a month and the next ones do the same, perhaps not only the current situation is endurable, but Xiaomi.EU might have enough fingerprints up its sleeve to tide us over until something better/more permanent comes along (like Chiteroman's work on STRONG, hopefully).
[Magisk] chiteroman:
Someone know the web which store fingerprints ? I remember one (it isn't Android-Dumps) but I can't find it :(
[Magisk] dmenezes:
Thanks for the clarification, just updated my comment to match.
[Magisk] Vision:
I know, i send you a PM, i hope is this
[Magisk] osm0sis:
This might jog your memory?

tadi... spec... mobi... MHPC...

I think Android-Dumps is mostly just a mirror of tadi.

And just a quick reminder to everyone that there's basically no way that Google is monitoring our conversation here, but I'll avoid full URLs to split the difference. 😛
[Magisk] Vision:
I have send to @chiteroman one link via PM, i hope does the job
[Magisk] dmenezes:
Agreed re: the good old Google -- there would be no way a "we are not evil" company would do anything like that.

Alas, that "good old Google" has been dead and buried for some time now, and has since been replaced by its totally evil Goolag twin -- which is the kind of company that's not only capable but willing to work overtime to eff all of us up to gain nothing except bad will.

So I urge everyone not to make Goolag's efforts any easier -- and not sharing that kind of information publicly goes a long way towards that.
[Magisk] fma388:
The locked bootloader is essential to pass BASIC and DEVICE integrity or not ?

@badabing2003 said that it's possible to have one rooted slot and another not by flashing the OTA twice with PixelFlasher (for Pixel Phone of course, for other phones I have no idea).

So if it works on an unrooted stock rom with unlocked bootloader, this can be a temporary alternative.
[Magisk] osm0sis:
It's nothing that hasn't already been shared in this thread many times, and will soon be buried once again. 😄
[Magisk] wfred:
Yep. Just tried again to make sure.

I can force stop Play Services under both Apps and Running Services in Developer Options. It shuts down for about 1 second and restarts.

I'm on the cph2449 (EU) software (converted from 2451 (NA) to get full OTA updates) if that makes a difference
[Magisk] dmenezes:
This sounds promising!

How would that operate in practice? Like, flash stock to partition A, then custom ROM to partition B, then lock bootloader and somehow get it to boot from partition B?

Wouldn't a locked bootloader simply refuse to load anything not stock?
[Magisk] Vision:
Interesting, because as i see lot of users say can't click the force stop button, and the one thing they have in common is use A13 and over
[Magisk] Vision:
Something similar discussion before months with @HippoMan, if can possible this

View attachment 6079285
[Magisk] fma388:
I haven't tested the solution given, all I know is that you need the same OTA update on both slots, so it's impossible to have a stock rom and a custom rom.

The only change between the two slots is root/unroot.

But i don't know if lock/unlocked bootloader is taken into account for the verification of BASIC et DEVICE integrity or it's just root.
[Magisk] sawdoctor:
Pretty sure i read it had been taken down again
[Magisk] osm0sis:
I'm on it right now. Some vendors are missing/empty (undergoing maintenance reportedly) currently, but otherwise it's all there.
[Magisk] wfred:
Maybe regional?
[Magisk] Vision:
Me to in the 1 of 3 you say before
[Magisk] Vision:
Maybe and the ROM, users say have A13 but not mentioned what ROM have (stock or custom)
[Magisk] osm0sis:
Custom ROMs/GApps usually let you FC GMS from Settings App Info. That's probably the difference.
[Magisk] Vision:
Because i have Xiaomi Poco X3 NFC A11 MIUI 12.5 with Stock ROM and unlock BL with Kitsune Mask, i can force stop GMS and the irony is can click in the disable 🤣😂

Maybe is MIUI thing ?!
[Magisk] osm0sis:
Yeah, it's at least a difference ROM to ROM thing, since Google Pixel stock ROM does not allow it.
[Magisk] Vision:
Useful info. Thanks

Because i write a mini guide to test if the FP work without reboot, only with force stop GMS, and few users say can't click and the only common have A13, and i write this step work until A12, now must change again and write depending on the rom the click maybe visible

Edit: Update my Guide

View attachment 6079297
[Magisk] V0latyle:
Sort of.

For devices launched with Android 8+, they rely on hardware backed attestation by default, so simply having the bootloader unlocked will result in failing 3/3

The PIF fix works by making Droidguard think the device isn't capable of hardware backed attestation, thereby falling back to basic attestation, from where we were able to trick it into passing 2/3

But, since Google threw a wrench the size of a Buick into things, there are very few working prints remaining, and they aren't easy to find. The Xiaomi.eu prints work for now but when they can't find working prints anymore, we will be "stuck" unless someone is able to find another workaround

So the bottom line is (and always has been) that if you want a guarantee that your device will ALWAYS pass, the only way to do it is run factory firmware with locked bootloader. No custom ROM. No root. No custom or self signed AVB keys.

See my first sentence - simply having an unlocked bootloader breaks the hardware certificate chain, and TEE (which is unbreakable) will always tell Droidguard the truth about the bootloader being unlocked - as well as the verified boot state. Therefore, modified device = failing Play Integrity. Even if you're on the factory firmware. Even if you aren't rooted. Even if you're locked on a custom key.

It's not, see above

Sort of - the bootloader lock enables Android Verified Boot, which will check the boot and system images against the installed key at boot time.

You CAN install a custom key, and as long as your firmware is signed by that key, lock the bootloader - as in AVBroot - but the Verified Boot state will be "SelfSigned", confirmed by TEE, so this won't help for our purposes.

Not entirely true, you CAN dual boot on A/B devices.

The problem is the bootloader lock, and the AVB key, are global - they apply to both slots. So, you can't have one slot locked + stock and the other unlocked + custom/modified/rooted.

The bootloader state and the AVB key apply to both slots. So, if the bootloader is unlocked, you can have whatever you want on either slot. If the bootloader is locked on the OEM key, both slots must be genuine OEM. If the bootloader is locked on a custom key, both slots must be flashed with images signed by that key.

As I pointed out above, the bootloader lock and the AVB key are part of the whole problem here. We can hide the bootloader state, but TEE will always tell the truth.
[Magisk] wfred:
How about trying under Developer Options/Running Services instead of Settings/Apps?
[Magisk] duzers:
I have been following the PIF topic from the beginning, so far I am using Poco x3 nfc PixelOS A13 as my main one, only basic integrity passes, because several of my previously found fingerprints have expired, so I am now paying with the watch and waiting for the strong integrity problem to be solved. I recently took my old Leeco le pro3 out of the closet. It has an unlocked bootloader, the old version of magisk v.22 installed and the old aicp rom with Android 9 loaded. Now attention!!! The play store has updates turned off, has the correct play protect certificate and passes BASIC and DEVICE integrity!!!! There is no PIF installed!!!

Can someone explain to me how it is possible that the wallet passes the security requirements check and two days ago, yesterday and today, as part of the test, I paid with my phone in the store? And my main Poco x3 PixelOS A13 only passes basic integrity because its fingerprint has expired... I don't understand something?
[Magisk] Vision:
Yeah, i have forgot about this, i add it to my Guide. Thanks.

The irony is i try to have low profile, I haven't enable it on the device I'm using the Developer Options, and only have enable it to test before flash ROM, i have try all the settings for test before flash fresh ROM, i know sounds silly 😂🤣.

P.S only in emulator do the test now
[Magisk] Iridule:
Just for laughs I asked Gemini how Google was detecting prints to restrict...

View attachment 6079304
[Magisk] niko26:
How about patching Droidguard?
[Magisk] V0latyle:
See this:

https://i.blackhat.com/Asia-22/Thursday-Materials/asia-22-Thomas-DroidGuard-A-Deep-Dive-Into-Safetynet-slides.pdf

I'll admit this is where my understanding of everything gets a bit fuzzy. But, this is my grasp of it:

Droidguard downloads and runs a virtual machine every time it is called. This ensures that 1) it is using the latest version and 2) that it is not tampered with.

Play Integrity also depends on Google side cryptographic verification - the token from GMS on the device is sent to the Google PI servers, which decrypt it and return a payload containing verification data:

View attachment 6079324

What this means is that to truly fool Droidguard, you'd have to hack Google's servers too. Good luck with that...

More interesting reading:

https://www.blackhat.com/docs/eu-17/materials/eu-17-Mulliner-Inside-Androids-SafetyNet-Attestation.pdf
[Magisk] badabing2003:
View attachment 6079321
[Magisk] V0latyle:
On a side note (and this may have been mentioned before), PI apparently had a problem a week ago:

Google Play Status Dashboard

status.play.google.com
[Magisk] Vision:
Interesting.

Google "child" is against