yashsingh1/xdaforums huggingface dataset:
[Magisk] Flr Power:
Get ready for a long time 🤣
[Magisk] osm0sis:
Arguably you not including the matching fields to the elements of a full fingerprint (i.e. what my default template json contains) would make any using yours, even with a custom print, quite obvious as well.

Spoofing more fields on our side should show less outliers in Google's data for them to ban from, which is why I chose to add more default fields on my fork... But it's all pretty futile considering they can look at literally anything that doesn't match what it should. 🤷‍♂️
[Magisk] dosbuddy:
I am still on Chits PIF 14.0.

But as with all others, all of my self mined prints did non work anymore.

So I switched to X.EU 2024.02.29 print. 😒
[Magisk] i5lee8bit:
Thanks for reiterating that hint. Took me about 30 min to find a new working custom print. ♥️
[Magisk] revengineer:
After 3 months my fingerprint failed, looks like many are in the same boat. I tried the pickaprint.sh script for an hour, but none of those seem to work. If there is an easier way to get back on track than reading the last 200+ pages of posts that I missed, please let me know.
[Magisk] osm0sis:
Updated autopif.sh one more time to add some basic error catching so people with bad connections are less confused if wget fails to download something. 👍
[Magisk] V0latyle:
The short version: Google implemented something that has broken prints for pretty much everyone, and very very few are still working.
[Magisk] osm0sis:
We can call it what it is: a mass ban of 95% of known working fingerprints. It's almost certainly the same way they banned specific prints before (presents as passing SafetyNet completely on YASNAC, but failing PI DEVICE verdict in any Play Integrity checker) but on a much larger scale.

Still, baffling that they didn't just ban them all. I wonder what's so prohibitive with the banning process that keeps them from doing that, or what the point of them leaving the 5% of working prints behind is... 🤔
[Magisk] HippoMan:
Just a wild guess, but perhaps one factor might be that they have now decided to banana fingerprints which they've detected as having been used more than N times since whenever they started counting ... where N is greater than 1 but a not huge number.

This might be in addition to other unknown factors which maybe only catch a smaller number of additional FP's.
[Magisk] asisandroid:
probably yes even though it sounds completely pointless. They probably have the tech to just ban it for all. Would be kinda sad tho, they would be at a "lower level" than ios / ipados then (there you still have some jailbreaking options on lower versions). In the end there is not really a difference in simply not being to modify the system at all or not being able to use half of the important apps. (Once it gets a completely "perfect" solution, even more apps will use it).
[Magisk] i5lee8bit:
I would like to add that there are some configs I found through intuition that I would bet my life savings on were NEVER used, let alone found, by anyone else. So for some banana'd configs, that N would equal 1 or 2 at most (i.e. from my my initial testing, which afterwards I then archived into a folder and never touched again).

I swear, there's something else at play we're missing here. Or, like @osm0sis said, it's just baffling and maybe they're just all around fk'ing with us...
[Magisk] asisandroid:
Doesn't a banned print still work on an unmodified device? Then it would simply be extra checks I guess
[Magisk] HippoMan:
A sudden, full-blown, 100-percent banana-ing might be something about which they are not sure of all the consequences and side effects.

Keep in mind that the Googlefrinchians support rooting in general. They also want to provide ways for app developers to detect this rooting.

This means that a "nuclear option" is not necessarily what they want, and they need to make sure that whatever integrity tightening that they put into effect doesn't cause any unforeseen negative edge cases to appear which might jeopardize security, nor to create unexpected issues for developers, nor to jeopardize their stated desire to allow rooting. A bit of a balance needs to be maintained.

So they might be slowly unleashing more and more restrictions and then observing the consequences for a while, before deciding what each next step might be.

Also, don't forget that we modders comprise an extremely small percentage of Android users, and I doubt that the Googlefrinchian powers-that-be are devoting very much time or effort to deal with us ... neither in positive nor negative ways. This might explain why the changes that they are unleashing only come piecemeal, every couple months or so.
[Magisk] Legitsu:
something weird is going down suddenly both SPIC and YASNC both return fail: yet Playstores own Integraity check report pass + google wallet is working at the time of this post:

I am wonder if they have started blocking/filtering api requests to make it harder to automaticly verify signatures or something because this makes NO sense @osm0sis @chiteroman som ting wvery wong here:

dm me if you need the fp I am using or something
[Magisk] i5lee8bit:
I'm starting to suspect the "5%" of remaining valid configs are ones used by the very same Google employees responsible for screwing us all over. Probably have their own devices rooted but wanna keep all the fun for themselves and/or getting off on a power trip. <bracket slash sarcasm but also a pinch of conspiracy 🙃>
[Magisk] SnOOpeRa:
My observations after the latest ban , I was using my own print taken from my own device build.prop ( original android 7 updated to 8.1 , not-very-known china brand that was sitting in the drawer for long time ) , checked back then and didn't find any public dumps of the firmware available except some ru sites links which do not worked anymore, so assume it was not commonly used, print was working ok since november - used only on my another devices , now with the latest bans 2days ago stopped working, but on that specific device , which is rooted with very old magisk v22.1 , bootloader unlocked, so no strong integrity, no zygisk cause of the old magisk, no other modules , PI is continue passing on it and wallet nfc working without issues on it ( setup it just to confirm ) , so it seems the new ban is something other missmatch check or so in my opinion

p.s: never checked pi in app , only in store dev options and the number of checks were small as i know it was working
[Magisk] Claus….:
Xeu public do not work anymore.

Edit: it works!
[Magisk] Nergal di Cuthah:
Does for me but maybe my DG is older than yours, I'll keep an eye on it.
[Magisk] 4sz0m:
Still works for me and reapplied an hour ago.
[Magisk] awarexda:
So on Monday (most probably) we will kiss goodbye the latest working FP....
[Magisk] zgfg:
You get overquota API error -8 (too many requests) or it really passes Basic but not Device?
[Magisk] pndwal:
With PI MEETS_DEVICE_INTEGRITY but S/N failing, please can you show the raw JSON attestation result for S/N?... 👍 PW
[Magisk] Claus….:
Sorry guys, I rebooted. It works.
[Magisk] chrbur:
Until yesterday no problems!! Today I took a OTA update concerning Android 14 February. First CTS failed. I Updated Play Integrity to 15.9.1 and CTS passed (!!!) - until yesterday I installed "Fork". I don't pass Device Integrity so I tried to change PIF by using /data/data/com.termux/files/usr/bin/curl "https://raw.githubusercontent.com/ptewee/PIFS/main/pickaprint.sh" | sh

Now I get an Error: Google Play Services API error -8: unknown status code: -8

Never change a running system :-/

Has anybody a solution concerning error? How can I pass CTS and (!) Device Integrity? Is the PIF method above still working? Only with Fork?
[Magisk] zgfg:
Too many requests - too many ppl testing

Current situation with TBChecker, SPIC and PI Checker

You will have to wait and try your slot tomorrow

Or test from Playstore, Settings, Debeloper options
[Magisk] Clasimodo:
I get the "I get an Error: Google Play Services API error -8: unknown status code: -8" in all integrity apps, but not if I test in Google Play Store itself.

EDIT: the behavior changed. Apps are working as expected again.
[Magisk] chrbur:
Right. Thx. Google still works. But I don't know why CTS fails. I used the last version of PIF and Fork. Has anybody the same problem? In the morning I passed CTS :-(
[Magisk] pythonimus:
autopif and pickaprint not working at all on my pixel 8 pro.
[Magisk] CityKev:
I posted by chance a few hours before the latest crackdown by Google that my impression was that a lot of less technically able people were probably giving up trying to find working FPs and so were choosing between having a locked bootloader and stock plus all apps and Google services working or unlocking the bootloader and accepting that certain things won't work.

The current situation is that I reckon Google have diminished the pool of people who will customise to those who are willing and technically able to do whatever it takes to continue to do so. A hard-line, No Surrender faction if you like :)
[Magisk] pershoot:
Going after RCS is quite an issue; all in the name of 'spam and abuse' (referencing that 9 to 5 google article) and has me questioning my own longevity in this 'cat / mouse game', if you will. It gives me a double-take and a bit of a pause to reflect on all this. I do not like that we all ended up in this position, but here we are.
[Magisk] pershoot:
Its taking longer then expected this go-around (even RCS refreshed faster for me, which is surprising), when compared to the previous instances (has usually been ~8-12h as of late). However, Wallet seemed ok when I last tested some hours ago (I used an app which uses Wallet to submit payment(s) (this inter-connection breaks if there is an issue with Wallet)).
[Magisk] Adrianer:
Yes, me. Device integrity: pass. Google Wallet security requirements: fail...
[Magisk] Adrianer:
BTW. I found one more problem: when the script is renamed to e.g. "a", it stops working, as "DIR" is empty then:

*) DIR="$(lsof -p $$ 2>/dev/null | grep -o '/.*autopif.sh$')";;

I've workarounded the problem by completely removing the code regarding DIR up to and including "cd "$DIR";" (it simply writes everything to current dir now anyway) and it works for me now.
[Magisk] aygul12345:
Updated the last update on my xiaomi 13 pro, it solves the problem gets pip but after a reboot the phone can't boot into the rom.

I don't know if it has something to do with this update yes or no
[Magisk] pershoot:
<deleted>
[Magisk] GabbyWC:
If things get to the point where RCS becomes unusable on unlocked devices, it won't change my habits because I prefer Telegram which is far more versatile for instant messaging and related features. Sure, large Telegram groups can be annoying to read through but for normal one-on-one conversations, I think it's the best option. I have not used WhatsApp in years but in 2023, they finally added the ability to edit sent messages so maybe I'll reinstall that app for the contacts who don't use Telegram. If Google wants fewer people to use its Messages app, they're making that scenario more likely with their recent actions. I can easily switch back to Chomp SMS for texting and picture messaging without any ridiculous integrity checks.
[Magisk] m00n3:
No, apologies. I'm not complaining about your (or anyone's!) work – I followed this thread almost religiously when the whole thing started unraveling and only came back. My frustration came from coming back and seeing the exactly same posts about "banana'd" FPs over and over.

I don't think they're adding blanket checks to EVERY device, that's the thing – that seems like insane levels of grunt work. I assume their database is essentially a map of device to known good state, or even a hierarchy of device groups and devices. While all info must be gathered locally and potentially even all sent to Google, not every check may be done for every device, if they don't have the data of what the correct info is (or if the device is all over the place). For sure they have a way of accepting *. We must have been riding on all those *s.

I'm glad you (and perhaps others, but just in the background) did the work of spoofing all properties – just blindly checking if there's any more properties being checked was one of my first ideas even back when this whole thing started, as it seemed such low hanging fruit. Honestly I just didn't build something for myself out of your or chiteroman's PIF just due to sheer laziness, so thank you for performing that. Again, if people did explore those avenues, just not necessarily announcing it here, we're on the same page.

Even if the checks happen serverside, the PI bytecode has to run locally to fetch information – GMS is obviously not uploading the entirety of your filesystem to Google's servers. Romain figured out what SN was gathering locally at that one point in time when he performed his investigation. Unfortunately it seems security researchers with that level of skill are uninterested, afraid of Google, hired by Google outright or see the exercise as pointless.

If you mean that Google can change that bytecode at will – yes. But adding new sources of info is a lot more work than just whatever they were doing every week. At least up until whatever happened recently, which was an actual, proper change.

I don't mean to poo-poo on anyone's head. Full prop spoofing always seemed like the low hanging fruit and I wondered why no one had seemingly tried it (get a real device that can pass PI, do getprop on it, spoof the full props and the uname, see if it passes PI). I now see @osm0sis not only tried it himself, but also made his work available to others, which is great. I also see that most likely other people did this independently, but just didn't announce it as it didn't go anywhere.

I wasn't attempting to "bestow" any major revelation, I was just surprised the discourse was still "how is google banning FPs". Again, if everything I said seemed obvious, that is, everyone that has thought about this rationally for a bit reached the same conclusions, why not a FAQ?
[Magisk] GabbyWC:
There is a relevant FAQ from osm0sis at https://xdaforums.com/t/pif-faq.4653307/.
[Magisk] purgy:
The real mystery to me is why google have so little faith in STRONG_INTEGRITY that they are even bothering looking at anything else.

The fact that they are still playing whack-a-mole (albeit with a recently upgraded whacker) like this instead implies some issues with strong integrity itself.
[Magisk] Vision:
What happens? Google make tough game.

I try yesterday 50+ FP and today again 50+ and only basic pass
[Magisk] CityKev:
Further to my post above, I still think there will be lots of unlocking of bootloaders and customisation but not so much on primary devices (in effect phones). I have two tablets on different custom ROMs and up until two days ago one passed device integrity but the other only had basic. They both only pass basic now but that isn't a problem as I don't carry them around to make payments or try to order a McFlurry on the McDonalds app with them either. My phone has the bootloader locked and on stock but I will unlock and customise when it becomes a secondary device.
[Magisk] pershoot:
Try an amendment to this (however, retain the case structure / syntax for the proceeding and end of it (i.e. *) and ;; )):

DIR="$(lsof -p $$ 2>/dev/null | echo "/$(grep -w $(basename $0) | cut -d/ -f2-)")"

Snip:

$ cat cat.sh && sh cat.sh && mv cat.sh hi.sh && sh hi.sh

DIR="$(lsof -p $$ 2>/dev/null | echo "/$(grep -w $(basename $0) | cut -d/ -f2-)")"

echo $DIR

/home/pershoot/test/cat.sh

/home/pershoot/test/hi.sh

<Edit> Add tag: @osm0sis
[Magisk] locolyric:
so confuse now , is google pay stop working even met device integrity?

it still show that my phone is not safe.

using magisk alpha, play integrity +shamiko(black list)
[Magisk] GabbyWC:
It's not a matter of faith but one of compatibility and support. If or when Google implements strong integrity checks as a requirement for tap to pay and RCS features, then older devices which are incapable of hardware-backed key attestation would be shut out of apps or features that require it.
[Magisk] Adrianer:
...which means, it is only a question of time until this happens (probably, when Google cuts access to the Play Store to this old Android version)
[Magisk] 4sz0m:
Would you mind sharing your setup?
[Magisk] pershoot:
Refresh complete (Wallet).
[Magisk] mumuli:
Fp bans @ Here to stay
[Magisk] zgfg:
I wonder, the proponents of 'temporary baning', do we still have theories that in a week or two all those hundredths will work again😀
[Magisk] pershoot:
As long as you pass DEVICE (alongside BASIC), all should be ok. Wallet will refresh in due time (~22+ hours from this current iteration (up from ~8-12+ previous)).
[Magisk] Vision:
I wish, because we need it 🥺
[Magisk] mafiatw:
The same problem as yours.

After update of PIF (v.15.9.1) in Magisk Delta and a reboot, my POCO X5 5G can't boot into the ROM (hyperos 1.0.3.0)

I have no idea what's wrong in this latest PIF. Now, any idea how to solve it? Thanks a lot.
[Magisk] pershoot:
I caught myself thinking about switching to iOS for a bit (if I need to relock BL to restore critical native services, might as well!). I just snapped out of it!! hehehe. Soldier on! :)
[Magisk] GabbyWC:
Try using the PlayIntegrityFork module instead. You may need to use the autopif.sh script to generate a valid public fingerprint.
[Magisk] Vision:
Google really make tough game.

Google is blocking RCS on rooted Android devices

Google says it’s taking measures to prevent spam and abuse.

www.theverge.com
[Magisk] GabbyWC:
It's funny to me when people say that they'll switch to iOS if Android keeps heading in this direction. I'll never become that desperate. Apple devices are locked down and dumbed down. 🤦🏻 I wouldn't accept an iPhone even if someone offered it to me for free. 📵 It's no coincidence that my avatar is what it is. ☝🏻
[Magisk] pershoot:
I've been with Android since the very beginning (G1). Although I don't perform development work for it any longer, its suited me fairly well (barring its standard quirkiness / janky behavior, at times).
[Magisk] Tamsta_T:
Should we all leave 1 star feedback for Messages app on play store?
[Magisk] rogers11:
If Google had a decent backup, I'd think again about rooting. Google Pay and RCS are not important to me but some Tasker scripts would need changes without being rooted.

In any case, it's my last Pixel. I won't spend that much money again if I can't do what I want with it.
[Magisk] GabbyWC:
I like your idea but if enough people do this, maybe Google Play will have those reviews immediately disappear without warning, RCS-style. 🙄
[Magisk] Adrianer:
Latest Kitsune Canary + PlayIntegrityFork v7 + autopif.sh - on LineageOS 20
[Magisk] arkzok:
I don't wanna reboot my device each time I try new random fingerprint. But when I try 'killall com.google.android.gms.unstable' in Termux, without su it says 'no process found', with su I get 'No such process'. What am I doing wrong?
[Magisk] GabbyWC:
Enter su -c killall com.google.android.gms.unstable instead. The "no such process" error means that DroidGuard wasn't running when you tried to kill its process. If you enter the command shortly after doing a Play Integrity check, you shouldn't see that particular message.
[Magisk] mafiatw:
Thanks for your help. But sad to say I can't get into my HyperOS to try the fork...

What's even worse, I found my TWRP is overwritten by stock recovery after I updated my phone from MIUI14 to HyperOS.

What makes matter worst, there is no 3rd party recovery for HyperOS on POCO X5 at present.

Now I can't get into 3rd party recovery to delete the PIF to make my device boot properly. :cry:
[Magisk] carlese:
How do you use autopif? I am using pifs copying the commands now, how to use this?
[Magisk] pershoot:
🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Magisk] arkzok:
/system/bin/sh: -c: inaccessible or not found
[Magisk] GabbyWC:
If the device is recognized in fastboot mode (hold the volume down & power buttons for a few seconds to get there), you should be able to flash or at least boot into a custom recovery. If you can't access a custom recovery, fastboot mode will allow a clean flash of the Poco X5 (moonstone) custom ROM from Xiaomi.eu by running their first_install_with_data_format script on your PC. This will erase your phone's data and start things over. It's not a quick solution but at least you'll be able to use your phone again.
[Magisk] GabbyWC:
Try it without the -c and see if that works. The command that I provided in my previous message works with the Material Terminal app.
[Magisk] arkzok:
I already told you what happens when I try it without -c
[Magisk] Vision:
Yeah, if Google is smart enough like say, must let us have those apps (with root) unfortunately we need it this days
[Magisk] aygul12345:
How did you managed to solve this issue?
[Magisk] GabbyWC:
... and I already told you that the "no such process" error is normal if you haven't done a Play Integrity test just before it. Aside from that, be aware that your custom fingerprint tests will likely end in disappointment now that about 95% of the previously working ones no longer pass device integrity.
[Magisk] arkzok:
Oh, I just now realized that you're talking about Play Integrity TEST, not pif.json update... Btw, do you know whether the 'Reload pif.json' button in Pixel Flasher does the killall thing?
[Magisk] GabbyWC:
I don't use PixelFlasher so I'm not familiar enough with it to answer that question.
[Magisk] aygul12345:
Do you know how to solve this issue?
[Magisk] 4sz0m:
Same + same (@osm0sis I finally switched to your PIF v7 ;) ) + PixelFlasher imported xiaomi print + 4.14.313-KewL kernel

But I guess I restarted my Wallet-waiting clock as I performed the switch 5 hours ago, after trying out (without success) a large number of various prints.
[Magisk] GabbyWC:
Scroll up to post #12,105 on this page for my reply which has a couple of possible solutions.