yashsingh1/xdaforums huggingface dataset:
[Magisk] sawdoctor:
I honestly think they've been looking at play integrity checks and any print that's shown up for a few integrity checks they've just nuked. Every time Google have banned the bundle prints we've all gone and checked ours are still working with integrity checks.

Can't think of anything else as I've so far only seen 1 post claiming their print hasn't been banned. They seem to have banned every single one of us in one go
[Magisk] Samg381:
Posting this again - please vote and comment on this Google community forum issue if you are having RCS issues on your unlocked / rooted device!
[Magisk] V0latyle:
Yeah, and what's odd is that those of us using obscure prints have been affected too. I was using a print from my own device from a rather recent Android build that I'm 99% sure no one else was using.
[Magisk] manjaroid:
Stick to v7 fork, run autopif.sh as root, copy the generated json to the module's directory and reboot. The script was updated (yesterday?) to play nicer with Termux, otherwise the earlier one should work like it did for my older Pixel.

You need a time server connection to sync local time. If there's no network when the phone starts that could explain what you're seeing. Make sure your locale is correct and no need to disable networking before powering off.
[Magisk] Vision:
Again the play integrity checks hit 10k, i can't try the FP i found to check if pass (i know exist and other method but i like try this with app) 😂🤣
[Magisk] sawdoctor:
Pretty sure no one was using mine either as it was one that shouldn't have worked but did. To ban all of us in one go but not patch the mismatch is bizarre. Only other thing I can think of is the leap day some how was responsible and the extra day broke something?
[Magisk] pndwal:
Without Zygisk?...

I'd still be trying latest Magisk... Guess your using this 64bit Viper rebuild?:

https://github.com/AndroidAudioMods/ViPER4Android/releases

No more thoughts other than try... Noone will fix old Magisk anyway... All supposition till you try... May be no issues!...

@zgfg may have his finger on 64 bit Viper's pulse... And possible Magisk issues/regressions... PW
[Magisk] chiteroman:
This is what I discussed with @Displax the other time, there are devices that the first_api_level property should be 33 but in others, as is your case, this should be null. If you open the service.sh file you will see that it removes that property.
[Magisk] beeshyams:
Thanks for your advice. I use Zygisk and the same V4a you pointed to... Will try in a few....
[Magisk] Stillhard:
Tested this for you, compability problem for my device tho, failed Strong
[Magisk] chiteroman:
This is very strange... The hook is in GMS process. I don't know the cause.
[Magisk] Lughnasadh:
For what it's worth, I'm using Iscle's VIPER4Android-RE (v. 0.5.0) on two phones with Magisk 26.1+ with no problems:

Pixel 6 Pro

Magisk Canary 26104

Android 14 Beta 4

Pixel 7 Pro

Stable Canary 26.1

Android 14 Beta 4

Btw, also using the latest JamesDSP (5.0) (using PBone's Rootless app for root 1.6.4) and AML (5.1) on both phones as well and all working with the V4A mentioned above.

Back to on topic things...
[Magisk] Captain_Throwback:
At this point, it seems every version of the fix that includes the patch for strong integrity is breaking my lock screen/SystemUI. Going back to @Displax Mod 2.0 (not Strong) gets everything back to normal. I'll probably just stick to that.

Appreciate all the efforts/attempts to fix it. If I have some time to factory reset, I'll be curious to see if it works better from a clean, fresh install.
[Magisk] Displax:
Maybe you use some custom fonts?
[Magisk] tutibreaker:
Works great in redmi note 10s miui14 android 13 thanks!!
[Magisk] Captain_Throwback:
I do...but the UI for the custom fonts is part of the device Settings. Could this actually be the problem? That doesn't explain why it works fine when not patching for strong integrity, does it?
[Magisk] pndwal:
Do we know which device/ROM?... Lost track...

But shouldn't be fonts if inbuilt as I understand it... Modules are the problem... Details:

https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699/post-88723775

🤠 PW
[Magisk] Displax:
Yep, that is very old some sort of problem exists since the original module, still no one fix it. Some conflicts with zygisk and how are fonts applied.
[Magisk] chiteroman:
All Zygisk modules are affected by this? Or only safetynet-fix? Also, any idea which is the problem?
[Magisk] beeshyams:
Thanks, flashed Magisk 26.x and it seems fine @pndwal :)
[Magisk] Captain_Throwback:
Amazing. Uninstalled custom fonts and used one of the preinstalled ones, and now no more lock screen or SystemUI issue. Crazy that something simple like that would be the problem, completely unrelated to the module (outside of the Zygisk conflict you mentioned, of course). Thanks for the hint and all your hard work on these fixes! @chiteroman thanks to you too!
[Magisk] Displax:
Relevant issue: https://github.com/kdrag0n/safetynet-fix/issues/163#issuecomment-1066020819

Same happens with SystemUI, I think.
[Magisk] m0han:
I wrote and indicated that in my screenshot here. But, I got 'Strong Integrity' pass result with TB Checker app.
[Magisk] chiteroman:
Thanks <3
[Magisk] aygul12345:
I missed the note in the early builds. I can't find it anywhere, you mentioned something about "Shenko" module to pass bankapps. But can't find it anywhere, what was you mentioned?
[Magisk] shadowillusion:
Do you mind to also release the zip of 9.7.1? I am just curious.

How to recompile (which package to install) and what environment setup do you use?
[Magisk] spida_singh:
Thanks, I simply want to use your module alone with kernel su. I don't use any other modules
[Magisk] solar666:
Shamiko you should look for
[Magisk] aygul12345:
I missed the note in the early builds. I can't find it anywhere, you mentioned something about "Shamiko" module to pass bankapps. But can't find it anywhere, what was you mentioned?

What note was that?
[Magisk] tremalnaik:
All tests passed on my Asus Zenfone 8 with Android 13 with MicroG installed.😁😁😁

View attachment 6024256
[Magisk] solar666:
Releases · LSPosed/LSPosed.github.io

Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.

github.com
[Magisk] zgfg:
v9.7.2 ok for me, cheers
[Magisk] chiteroman:
Check v9.7.3

I reduced libs size (forgot to remove STL 😂) and included a new bypass. Now only touch one prop from Zygisk: https://github.com/chiteroman/PlayI...fba/app/src/main/cpp/main.cpp#L155C61-L155C61

But still gets detected by Starling :(

Seems like DroidGuad checks "ro.boot.flash.locked" prop with other way, so I can't modify it like others.
[Magisk] tryigitx:
Service.sh and system.prop files seem to be missing. I wanted to say this because a lot of users will complain.

Ok
[Magisk] pndwal:
Apparently it doesn't (unless someone changed very recently; it worked without STRONGINTEGRITY in September)...

What good will that do?

With root you can spoof props anyway, and hardware key based attestations incl. device integrity API verdicts like STRONGINTEGRITY will still fail as green (Verified) boot state is required...

Simply going from orange (Unverified, unlocked) to yellow (SelfSigned) won't cut the mustard...

Respectfully, please say why you think this has changed (or is it an assumption?)... Details:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89008523

@FredMontteiro, if you're still around, please say if your fixes are still allowing Uberdriver to work on Samsung Galaxy A5 2017 and Xiaomi Mi A3... 👍

😬 PW
[Magisk] pndwal:
You probably already know this, but as main GMS process (in addition to Droidguard process) detects root in A11+, it's probably checking the props... PW
[Magisk] shadowillusion:
9.7.3 removes service.sh, I guess the props is now inside zygisk right?
[Magisk] oled65cxpua:
I'm getting this error using Magisk Delta 26.1 on Nox Emulator with Android 9 64bit:

View attachment 6024331
[Magisk] oled65cxpua:
What am I doing wrong here?
[Magisk] zgfg:
Check on the opening/main Magisk app screen, on top, does it say Zygisk Yes

If it says No, then you didn't enable Zygisk in Magisk app Settings, or Zygisk does not work

Btw, I have no idea if Zygisk works or not on emulators. Besides, Delta 26100 is pretty old - why don't you use latest 26301 (I know, 26301 is Delta Canary, not Delta 'Stable' but what does 'Stable' mean when you already opted for unofficial/experimental Magisk fork - I always use latest Canary version, I just sometimes wait a day or two are there negative comments upon the update release)
[Magisk] wolfsoft81:
Hello ! In TB Checker Still not bypass line3 and line4

View attachment 6024562
[Magisk] zgfg:
So what?

Please read the post #1
[Magisk] wolfsoft81:
please quote link please
[Magisk] Vision:
Yeah exactly (my third FP R.I.P 16/2/24 - 1/3/24), Something changed again :alien:
[Magisk] V0latyle:
Leap Day did break some self service gas pumps in New Zealand

We don't know what Google did, but they definitely did something, and I don't think they went after specific prints. I'm not really sure though.
[Magisk] Lurxs:
Incase you didn't already figure it out, I assume you're using Termux. try a different terminal app. I used connectbot and it worked straight away.

Edit: on second look, you're not using Termux. Your error is different to mine, you seem to be unable to connect to the servers to download the apk needed. Are you using an adblocker that could be blocking the connection?

@osm0sis There seems to be a problem with the autopif.sh script and Termux, if this has already been mentioned or explained, I apologise.
[Magisk] bombadier:
Already fixed

🔧 [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] aerotox:
Had same issue tried clearing G services, wallet etc. no luck on 15.9. Suddenly started working just now after ~30hrs after installing 15.9
[Magisk] Lurxs:
Ah, my bad. I was using an old version. apologies.
[Magisk] rogers11:
Why, they won't change their decision. Users should uninstall the Messages app and stop using Google Pay, which is more effective in the long run.
[Magisk] pershoot:
Refresh complete (RCS). RCS is now connected, end to end encryption is on, no denials of a test message being sent to an RCS recipient and a message over RCS has been successfully received. Wallet should follow a bit later (as per usual from previous experience).
[Magisk] Nergal di Cuthah:
My P6P is 10k seconds ahead on all reboots. I use clocksync (which i can't find the apk to on any site/store and won't work on P8 because it's a 32 bit app) at boot up instead of carrier time, but the boot up time is always wrong.
[Magisk] zgfg:
Yesh, that's fine. But if you clrar that DG, you will not see anything v'vsible':

- next time you attempt PI or SN testing (manually or an app like Wallet asking for), G will push the new DG

- and if no connection, getting DG will fail but even with DG attestation would later also fail when contacting server

- if he doesn't attempt to test PI or SN, he will specially not see anything (with DG cache cleared or not)

So I don't see how clearing DG cache folder could affect him if he has now has issues pass PI.

IMO, he meant/wanted to ask something else (televant to how to pass PI), not about 'resetting DG'
[Magisk] mates21:
My print worked for 3 months. he died today. I had 3 other "emergency" ones, but they don't work anymore either :( do you manage to find your own fingerprint?
[Magisk] bakaekze:
It's very hard now
[Magisk] Adanaliisot:
Dear developer ,can you fix this problem in nex version of pif ?
[Magisk] Flr Power:
I find it so ironic that all the top guys here were pushing for using a private FP only to find out that it did not go that way. So much time and effort spent... It's a slow kill by Google and a new way to spoof will need to be found. :unsure:
[Magisk] Masterrel:
today the wallet stopped working. i updated the module. Everything worked. But the print disappeared. Now where to insert it if it stops working?View attachment 6074936
[Magisk] mates21:
If there is no new method yet, there is probably no other option :(
[Magisk] bakaekze:
In /data/adb/pif.json
[Magisk] V0latyle:
It's still the most logical answer. It would be foolish to think that PI doesn't collect any telemetry from devices, so everyone using a common print just leads to that print getting broken sooner. There's a few people whose mined prints are still working; it seems Google did something that affected the vast majority of us, but that doesn't mean we were wrong.
[Magisk] Masterrel:
thank you friend.

but as you can see from the screenshot, I don't have anything there. Although it was before. but the test passes and the store pays. do you have your fingerprint there?
[Magisk] guniens:
Hi!

Just did the first part and now everything's good! Thanks.

That never happed before, not even on my P6 which was rooted too.

Like sometime it boots 1h or so behind and as soon as I connect to internet it corrects.

Now is 2 days that boots up fine.

AFAIK time is synced without internet but with a cellular signal, if I turn off auto sync time is correct or some seconds behind on boot but not 1h behind.
[Magisk] guniens:
Can you explain more? I had a P6 before and was absolutely fine.
[Magisk] Nergal di Cuthah:
What more is there to explain. My p6p gains 10k seconds ahead (from ntp server). My nexus 6 always got the wrong tine from Verizon's network so i got in the habit of using clocksync instead of network time (i also have passwords that are sync'd with device time so it's more important to have the right time).

I don't know where to get clocksync, it's not in fdroid or playstore so i couldn't link it. But your P8 is 64bit apps only so it wouldn't run on your device anyway.

Tldr: my p6p starts a boot minutes ahead of actual time always. And until clocksync is run (or in your case network time) the clock is wrong. nothing to do with root or pif.
[Magisk] acwcanada:
Wrong is wrong! Since yesterday, I only see a person here mentioned that his private print is still working so definitely not "a few people". And actually whether that person is really has a working print can't be verified, I personally doubt it! Chiteroman's TG has over 20 thousand messages since he released his PIF 15.9 and I have not seen anyone prove another working print existing. I personally have two prints which I got them from my own old phones (they are still sitting there in one of my drawers) and 99% sure that they are not available in the public, they just got "banned" also on yesterday. You guys' assumption if not totally wrong at least definitely has it's hole. Right now almost 100% of the rooted phones which PI are needed are using the Xiaomi print. I believe there is never a situation that so many phones are spoof with the same print and couldn't come up with a "logical answer" why Google doesn't get it "banned" now.
[Magisk] zgfg:
Module did not install the pif.json bcs the currently working prints (originating from Xiaomi eu Injectot) are hard-coded into the latest PIF

Btwy it has been mentioned here in the thread couple of tines here since yesterday when v15 9 was released
[Magisk] rodken:
[Off-topic] Clocksync 1.2.6
[Magisk] Nergal di Cuthah:
Bookmarking though my next phone is likely to be 64bit only
[Magisk] V0latyle:
Ok, think of it from the other side of the coin.

With most of us using "private" prints, there was no way for Google to know which prints we were using, because there's simply so many potential device+build combinations out there that they would have to target all of them. Before yesterday, private prints continued to work while those in common use were frequently detected and subsequently made useless.

This is what we DO know after yesterday:

Some private prints DO work. I'm using one of them. So, that seems to discredit the "mass mismatch detection" theory.

Certain known collections, such as @TheFreeman193's "random" PIFS repo, now seem to have a 100% failure rate, at least on common architectures - arm, arm7, arm64v8.

Several of us are currently testing private collections; a certain member had over 6,000 confirmed working prints, out of which we are now seeing less than 5% passing, and there does not appear to be any commonality between working/broken prints - source, manufacturer, device, build, etc. It does appear that a significant concentration of working prints share a common API level, but even that isn't really anything new since that particular API seemed to be the "magic number" anyway.

So. There are still working prints out there, but something Google did made that pool get a lot smaller. We don't know how and we don't know why.
[Magisk] zgfg:
To catch-up, please read the FAQ post (look for the most liked posts here)
[Magisk] bentree:
I never cleared the DG cache. It seems that for me there is a delay of about 30mins on startup before playstore will allow me to check device integrity. If I try to check before then it just simply returns a blank <> result. Must be some sort of time/load delay thing.

Cheers, Bentree
[Magisk] zgfg:
You test Play Integrity from Playstore Dev options?

Can you please share your 'blank result' (cut-of your sensitive data) to better understand

And you say that after booting (?) you havevto wait 30 minutes to be able to test?

After each (re) booting?
[Magisk] D€INOS:
What is the api level for you print?
[Magisk] badabing2003:
What you say is mostly correct, with a minor detail to point out.

If you clear DG cache, running PI does not fix it.

But running SN fixes it, so does rebooting, or waiting an extended time.

And when I say fixes it, I don't mean passing with banned print, I know you know, but for others' benefit, when DG is cleared, even a good print fails (including basic).
[Magisk] Antonio200:
Just wondering... Could it has to do with Google Wallet version installed? Mine failed after Google Wallet updated itself (I swear I didn't... I saw the update and never clicked on it). The previous update on February the 14th forced me to start using Google Wallet (before I used my bank app)
[Magisk] Nergal di Cuthah:
No because it happen on devices without wallet and even without Gpay. It's all based on DroidGuard (DG)
[Magisk] GabbyWC:
No, the current version of the Google Wallet app works if the phone passes the basic and device integrity checks.
[Magisk] Antonio200:
Thank you, you both are right. Just wondering...

Regards
[Magisk] zgfg:
Google Wačlet just uses Play Integrity API from Google Play Services (which calls then Droid Guard app) and attests result on the Googke server

Not vice-versa!!!

When you test Play Integrity, you don't need to have Wallet installed and testing Play Integrity does not depend on your Wallet version

Only the other way - Wallet internally calks Play Integrityattestibg and requires Device Integrity to pass (and it caches the result, so you can still use Wallet up to half a day upon your Device Integrity starts to fail)

Please read the FAQ post in this thread
[Magisk] TotallyAnxious:
Mixplorer's execute function works fine with autopif script FYI. For those who are lazy.
[Magisk] 4sz0m:
I'm 27+ hours on xiaomi print with constant device integrity, but Wallet still not green. It seems Wallet/DG is checking something else now, not just the print... (?)

I'm on PIF 14.0 still with no access to a computer since before the 29th, so I had to update my print manually on my phone. Maybe I've done something wrong, but got device integrity back straight away, so it doesn't seem to be the case.

Is there anyone else with a similarly weird behaviour?
[Magisk] zgfg:
Interesting - that seems to be a new behavior (just tested and yes)

Three months ago it worked differently - if I deleted the folder/it's content, next PI and SN testing would install two DG versions, one for SN and one for PI

And PI would not fail nor it needed to wait or testing to be preceeded by SN to reinstall DG

But yeah, things change...

Btw, before I wiped them now, I found FOUR (4) new DG versions that were pushed/installed today, three of them this afternoon, every few hours a new one - it makes me nervous
[Magisk] osm0sis:
I switched to the Xiaomi.eu print on my device using my fork before Wallet caught the failure, and have now switched to a different private print. No issues with Wallet at all.

Usually the wait is up to 24-48h. So your options are either to keep waiting or to wipe Play Services data.
[Magisk] Fishawy:
Oh, so you found a private print that actually works aside from the Xiaomi.eu one?

This is interesting since all my old and new ones are failing.
[Magisk] 4sz0m:
Thanks, I'll wait then - to be able to confirm how long it will take 😊

From the past 2 times I had to switch prints, I had the impression it was around 12 hours.
[Magisk] osm0sis:
Yeah, like we've been saying, the pickings are pretty slim. Basically ~5% of previously known working prints still work.

Looking for a new one I'd say Android 6-8 with first API 23-26 should be people's focus. Which is basically the same advice as before, just a lot fewer work now.
[Magisk] chiteroman:
Banning fingerprints is very easy for Google, just check if the device sends an empty certificate chain and done.

That's why I will include a valid certificate chain with valid certificate extensions.

I don't know if it will help but who knows... 🤔
[Magisk] TotallyAnxious:
If you use Wear OS I strongly suggest you avoid wiping play services. It was a nightmare to get my PW2 back up and running.

(General advice, not a direct message to osmosis)
[Magisk] chiteroman:
My device still pass Strong with no hard-secured fingerprint

View attachment 6075007
[Magisk] osm0sis:
Yep, as usual, it's all either in the FAQ or the README. 😜

PlayIntegrityFork/README.md at main · osm0sis/PlayIntegrityFork

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com
[Magisk] TotallyAnxious:
I don't read anything I haven't already read before.
[Magisk] casouzaj:
I have a Sony Xperia 1 II (XQ-AT52 variant) running the official LineageOS 21 (latest) release. I use Kitsune Mask, with Zygisk, MagiskHide and SuList enabled, and, regarding PI, I had Play Integrity v15.9 and Shamiko v0.7.5 (newer versions dislike Kitsune). Well, like virtually everybody else, yesterday I lost the device integrity. I switched to @osm0sis' Play Integrity Fork, and, with the FP suggested by autopif.sh, my device integrity is back to business. Thank you very much, @osm0sis!
[Magisk] tom1807:
Do me a favor, please stop "educating" me, I read all the FAQs and if you would read my previous posts, you would know that I am not so "stupid" as you think I am.

Cannot recall that I made any whining post that my FP is not working, "demanding" a new FP, that I am clueless or show any signs of "panic".

It was an honest mistake, that I didn't pay attention when opening Yasnac that it still uses Safetynet and not PlayIntegrity Check, that's why I uninstalled the previous TB Checker.

Mistakes happen.

Cheers

Tom
[Magisk] cmstlist:
When the "pif" stuff started I mined one print and got lucky, and that print worked for months. It just failed. Removed my custom pif and upgraded to latest chiteroman and I'm working again - Wallet not complaining, RCS working. Pixel 6a.

I don't have the bandwidth to process all the chatter about a more sustainable solution so I guess this is the train I'm staying on for now.
[Magisk] miho171:
15.9.1 gives me a valid fp for Device Integrity and Gwallet back to work again, just all my previously farmed 10 fps are useless now, 9 of them never used before, it must to be something else.
[Magisk] V0latyle:
Well, the short answer is we don't have a "more sustainable solution" - yet. Maybe Chit's on to something with his certificate chain, but no one knows how Google managed to bork everyone's working prints this time around.
[Magisk] cmstlist:
I guess I'll just stay on this ride to the bitter end, and then when root life becomes fully unsustainable I'll get a new phone to never root.