yashsingh1/xdaforums huggingface dataset:
[Magisk] borygo77:
Ever since Google started messing with integrity I do have a problem with passwords in my Chrome. Is that related to this I got no access to windowed passwords like on screenshot?

Everytime I type login and pass it's asking me to save it 😡View attachment 6042821
[Magisk] fbirraque:
Do have a Pixel Device (hardware) mandatory?

Could be used with other brands like Xiaomi?
[Magisk] Nergal di Cuthah:
Works on any fastboot device, not sure if Xia is fastboot though
[Magisk] sawdoctor:
Just a heads up for pixel users, there's reports of QPR 2 beta 2 breaking zygisk which means if you flash it PIF won't work
[Magisk] rom-g:
QPR = Queens Park rangers ?
[Magisk] Nergal di Cuthah:
Is it breaking stable/beta's zygisk or canary's (i believe it is native bridge but maybe @pndwal can correct me) or both
[Magisk] sawdoctor:
From what i read in the pixel 8 pro forums it's both stable and canary so don't think native bridge is the issue. Not heard anyone trying zygisknext yet
[Magisk] zgfg:
@Iridule

Please,

please,

please

(and thousand of more times/lines)

When posting thousand of log lines please use [Spoiler]:

Spoiler content hidden.

instead of [Code]:

Thousand of lines
Always visible but how many want to read
For the others, it takes time to scroll down till the end

Or even better, attach the zipped log

And analyze the log to postt only the relevant lines😁
[Magisk] Lughnasadh:
Both. Seems to be a signature problem.
[Magisk] xcl1pse:
Already happening since PIF 13.6 after back and forth shadowhook and dobby. And yes I'm using zygisknext. Another reason I stay with older version 🙃
[Magisk] Nergal di Cuthah:
Did you just confirm you're on beta os and say that's why "i stay with old version" in the same sentence? 😅
[Magisk] xcl1pse:
Just to confim I'm using zygisknext and this module already broken since 13.6, but fix in next version and the cycle continues. For Pixel OS Beta, maybe can try magisk debug/CI version...
[Magisk] Nergal di Cuthah:
13.6is old and burned, you need either 14.0 with custom print, 14.3, Osmosis fork 3 with custom print , or dev 2 with custom print. Otherwise you'll not pass device.

So you aren't on pixel beta? If not your issue is not what @sawdoctor was asking about zygisknext.
[Magisk] intel_core_i7:
Some people will try their best to get wallet working because apparently their banks' cards added google pay have more relaxed restrictions, than using the plastic card. Higher transaction limit, no PIN required, no transaction/maintenance fee, etc. That's according to some in this thread.

I have 2 debit/credit cards, one is a virtual card that you can only see its details in the bank app (No PI required) and because you have same capabilities as a physical card when added to apple/google/samsung pay, it's a waste of money to make a plastic version which has annual management fee (virtual is 100% free).
[Magisk] xcl1pse:
Well I already did some note of this module which version works best and not. Since Pixel OS Beta is QPR so theres no source code. I just recommend test new version magisk CI since I tired switch between magisk and KernelSU to test them. And yes I'm on Pixel OS Beta. This new issue related to zygisk because new argument in QPR. Maybe I can test them later but from now not
[Magisk] Iridule:
I'm aware. I've got 30 other prints I'm not too worried. Was just curious. Yes it's a real device.
[Magisk] xxlakis:
Yesterday I rerooted my phone and flushed 14.2.1 just out off curiosity. After clearing wallet, play services and play I passed play integrity and managed to add 2 cards to wallet. I used phone to 2 transactions. First one passed but second denied from bank. No custom fp no nothing, just the module. My 2 cents.
[Magisk] purgy:
You'll need 14.3, as the fp in previous version is no longer working as of a few hours ago.

I'd still advocate searching for your own fp, but if you want a flash and forget (till it breaks again) solution.
[Magisk] tinhsoftware:
I followed instructions to search for build.prop and test on pixelflasher, but i see this errors to test the printView attachment 6042907
[Magisk] osm0sis:
Read what it says...
[Magisk] Nergal di Cuthah:
That error means too many people are using Play integrity tester.

Enable developer options in playstore (not android settings PLAYSTORE) and use the built in checker, or wait til the rest of the world is sleeping and try integrity checker again (do the first not the last)
[Magisk] javier87gav:
I'm using v14.3 and device is certified. Google wallet is working perfectly, however Microsoft apps are not working, "device health" is not met, any suggestion?
[Magisk] Nergal di Cuthah:
Are they in your deny list. I assume you mean teams and ? as 365, onedrive, SwiftKey and defender all run fine on my rooted device.
[Magisk] javier87gav:
Teams and Outlook. I'm using kernelsu so no need to use deny list
[Magisk] xSnowLeopardx:
Why use kernelsu? I thought it was only for temporary root? Could be wrong of course.
[Magisk] rseiler:
What is your history of success/failure with them to put what you're saying now in context?

I think it must be because your M365 admin has dialed up some of the settings on their end to do some serious checks, of which several are possible. I doubt you're talking about consumer Outlook and Teams (at least I hope you're not) since I think it's part of Intune's device compliance capabilities. There is probably a separate thread around here about it.
[Magisk] javier87gav:
It's a corporate account. It was working flawlessly on Pif 14.1
[Magisk] javier87gav:
I've been able to make it work, I needed to downgrade company portal to a version prior to November.
[Magisk] frasca61:
Today he stopped working 14.2, after reading and studying all the pages of this forum I managed to find my first work footprint (about half an hour of work thanks to Pixelflasher and with great luck). I immediately stopped at the first. I imagine, however, that many people will use the same imprint !!!

Thanks to all the developers, OSM0Sis and Badabing for everything they made available, but also to Chiteroman who allowed me to use the phone until I managed to use the personalized imprint method and for me who are a simple user was not easy ...
[Magisk] frasca61:
I don't speak English and the Google translator worked a lot
[Magisk] Imnoa:
You can use it with other brands
[Magisk] rocketda7331:
I've installed pif 14.3 and it works, but I wanted to find my own custom fingerprint.

I have managed to create the json file and put it in /data/adb/pif.json,

There wasn't pif.json in /data/adb for me after installing module, fair enough. Looking at code(chiteromans) I can only find hardcoded values in spoofDevice(), the nvidia shield ones. I don't see a reference to custom json being used anywhere and I can't find a way to test if it is used.

edit: nevermind, I need the dev version apparently!
[Magisk] FERRARI81:
But if this FP are online, if Google Ban them, the legitm owner are banned too?
[Magisk] Imnoa:
No, only if the print doesn't match the actual device
[Magisk] V0latyle:
This has been covered many times before, although I can't really blame you since there's no FAQ in the OP...

The prints only get blacklisted in mismatch situations. We are still working to determine what triggers the mismatch detection. The prints still work on the original devices. For example, the Google Pixel 2 XL print @chiteroman used for v14.3 doesn't work only if your device is not a Taimen. If you'are using a stock Pixel 2 XL, you are unaffected.
[Magisk] FERRARI81:
Yeah it's so difficult to stay updated with 3 hundred forum pages
[Magisk] Claus….:
Is anyone working on finding out what is triggering the ban?
[Magisk] V0latyle:
Sorta. We are trying to find a long term semi-permanent solution. If we can figure out how PI detects a mismatch, we should be able to spoof those processes too so that PI doesn't know there's a mismatch - without breaking everything else on the device.
[Magisk] sawdoctor:
At the moment the best guess is too many people using the same print or Google watching this thread/downloading chiteromans fix.

AFAIK no one who has used a fingerprint they found themselves has had it banned which is a good sign.

Your best chance of not being embarrassed by wallet being refused at the checkout is to use your own fingerprint for now
[Magisk] Nekromantik:
Are people having more luck with fingerprint from older phones? Like ones that shipped with Oreo?

Also does the pixel flasher testing work if you got KSU instead of magisk?
[Magisk] Imnoa:
No you'll need Magisk. And the sweet spot for fingerprints is ROMs released somewhere between 2018-2019 is my experience.
[Magisk] HippoMan:
Exactly.

And also, don't forget that some of the things that the Googlefrinchians almost certainly use to trigger the banana-ing of fingerprints is to follow this forum, the TG group, and the published source code of the recent @chiteroman PIF releases to see the working fingerprints that are being made publicly available.

So, an easy way to thwart these particular Googlefrinchian efforts is to avoid publicly posting fingerprints that work.

If you have found one or more working fingerprints and you want to help others, then you could teach them how to find fingerprints in the same ways that you did, and possibly help them do so.

And if you really want to share any of your working fingerprints, you could invite people to contact you privately, so you could then provide prints to those individuals whom you trust to be equally responsible with those prints.
[Magisk] thesingular:
I believe I saw one person saying the fingerprint they found by themselves was banned on this thread. Should be around 40 pages back lol.
[Magisk] Imnoa:
Any idea what device the fingerprint was? Might have been a print used by this module or shared somewhere online
[Magisk] pndwal:
I think the question relates to what extra cross-checks allow Google to determine that device is not authorised to use a print, unlocked etc* to prevent its use ("ban") in this case and not when device is stock/locked rather than how Google decides to add such cross-checks to ab individual print/prop set (ie. effectively 'banning' its use for passing DEVICE_INTEGRITY when unlocked)...

* This is the burning question as answering it properly (prop-erly... Sorry... Not intended...) = "Un-banning" "banned" print/prop sets... And there's no reason is shouldn't happen... 😉

Of course we have no real rights to do this (effectively subvert Google's security model) so it's Game On!... Google have it all sewn up for STRONG_INTEGRITY but thankfully this is still a big white elephant for banks...

This doesn't mean Google won't try to prevent userspace spoofs however, nor (equally) that modders won't succeed in discovering how preventions work and in bypassing them... We can, after all, spoof anything in userspace.

... Been a thrilling test match so far!... (If you're one for following and appreciating tactical moves in Test cricket rather than just enduring a Twenty20 International that is... May require rare breeding...) 😆 PW
[Magisk] V0latyle:
This.

We keep emphasizing this.

Whether you find your fingerprints yourself, or someone else finds them and shares them, we should all be trying to ensure we aren't using the same ones.

Should be anything Android 5 to Android 8.1. Look for devices that shipped between 2014 and 2017. They must have been updated to at least Android 8 in their lifetime.

Even better, give each person a different print. This way, if one gets burned, a minimal number of people are affected, and you'll know who you shouldn't give another print to.
[Magisk] sawdoctor:
Totally agree. I certainly don't think it's coincidence though that the pre supplied fingerprint has started to last longer since more of us have started to use our own
[Magisk] houmik71:
Hi, I would like to ask something, don't know if it was answered already, but it is kinda hard to find an answer in 300 pages without FAQ,

I am using A13 version of Evolution X, which no longer gets any updates. I don't know how this really works, but I suspect that the SafetyNet updates itself anyway? Because every week or so, my Google Wallet stops working and I need to update the safetynet fix and delete data of services, wallet, etc. It is starting to get annoying but I want to stay rooted since there are many pros to it.

Is there any permanent solution to this? So my wallet doesn't stop working out of a sudden and as such no more awkward situations in stores happening anymore?

Thanks for any help!
[Magisk] Imnoa:
Not really "permanent" but spoofing your own fingerprint via pif.json is the best solution for now.

How? I guess you need to read some of those 300 pages
[Magisk] xSnowLeopardx:
And we advice to always start with the first page of this huge thread. It contains a lot of information already.
[Magisk] thesingular:
Unfortunately, no. If I recall right, they never shared which device it was. And with how the search on this forum doesn't sort the in-thread search results by post number, it's a bit of a pain to search by myself right now, so I'll take a look at it later.
[Magisk] Imnoa:
Don't worry lol, I was just curious if you knew. If you don't, don't wast your time on it
[Magisk] BROKEN1981:
Someone asked ChainFire on Twitter for help. He said he predicted this 8 years ago ( which he did) and doesn't want to even try.

Can't blame him.
[Magisk] beardedwonder:
Is there any reason why I would be getting no device integrity but still able to use google wallet?
[Magisk] Imnoa:
Luck or some kind of caching, I've had the same but that only lasted less than a day
[Magisk] Vision:
For anyone who asks, The new Bootloader Spoofer mentioned by @chiteroman is a zygisk module not a apk like already he have BootloaderSpoofer_v2.1.apk, and i think is in development mode and not released yet
[Magisk] beardedwonder:
I installed osm0sis PIF last week, and it's still working today. I have the other issues like no Netflix in Google Play.
[Magisk] Imnoa:
Is Play Services etc on your deny list?
[Magisk] beardedwonder:
No, I have wallet and a couple of other apps that complain about root, and my banking app.
[Magisk] Imnoa:
Well there's your problem.

Try adding Play Services and the Play Store to the deny list.
[Magisk] V0latyle:
He's been largely out of the scene for a good while. Even @topjohnwu himself said he wasn't going to seek to actively defeat GMS attestation in Magisk because he didn't see the point:
[Magisk] quasyl:
Until now, thanks to Play integrity, I had always obtained the 2 integrity (basic and device) and certified device. Since yesterday, for no apparent reason, except perhaps that I updated xiaomi.eu to the latest version (14.06), my device (Redwood) is no longer certified and I only get basic integrity. Currently the version of the Play integrity module is 14.3. Is there a way to solve?
[Magisk] xSnowLeopardx:
Solve it by looking for a custom print and using a different version of PIF.
[Magisk] beardedwonder:
Do I enforce deny list?
[Magisk] zgfg:
Nothing remains locally on your phone. Everything is on Google side. Your Play Serviced just provide API to start PI attestation through

Documentation, flowcharts, everything was discussed in this thread

Btw, m second phone had the last update in 2021, not even receiving security patches since then. However, PI updatws the same way as on any new phone

Just check in your:

/data/data/com.google.android.gms/app_dg_cache

Go inside the subfolders - each one contains the.apk (droidGuard)

Check their dates - how often they are pushed from Google to you (you were not aware of)?

And that's only the part that is pushed to the phone. Verdict logic is purely on the Google servers
[Magisk] tom1807:
I am not ruling out that the problem sits 60cm in front of my notebook, but I tested last night roughly 15 FPs incl. the one from my locked Nokia 6.1+ and found only 2 working FPs.

Both were A8, all A8.1 showed only Basic Integrity passed and some earlier <8 showed only an empty bracket [ ] in PlayStore Developer options or an error message.

For me are the 2 working ones are enough, one is just a backup.

Cheers

Tom
[Magisk] beeshyams:
It

I too couldn't see Netflix till yesterday (not that I use it), but just checked after seeing your post and I can see it

No clearing of any cache of any thing. Maybe it gets fixed after some time
[Magisk] quasyl:
I will try. It's not easy but I will try. Thank you for your suggestions.
[Magisk] rodken:
I would agree that vulnerabilities are only covered that Google is aware of and has patched in Play Services. Not to mention that Play Services is not the silver bullet from such attacks as 0-days, but at least we know that Google tries to extend it's protection by patching within its framework.
[Magisk] Tamsta_T:
Would firewall "solve" those updates?
[Magisk] tom1807:
Out of interest I checked, last time was December 7, but I found 3 entries alone from December 6, 3 from November 30, 1 from November 29 and the final 3 from November 16.

2 weeks Google didn't bother my phone with that.

Cheers

Tom
[Magisk] zgfg:
I didn't mention or discuss vulnerabilities, neither I want to

I just said that my second phone is EOL for two years and does not even receive Security Updates sincere then.

But nevertheless, I have to update PI spoofs on that phone just as everybody else, but with the bright new modded phone

And that was the answer to the guy who contemplated that since he could no more upgrade the ROM may 'protect' him from being subject to Play Integrity cat and mouse game and the spoofs we are discussing here

And the answer is (again) not, bcs PI is not carved in stone in someone's ROM, his last Security update, etc. It's not carved on the phone side
[Magisk] Depressed T.Bear:
I can totally understand both of them. Honestly, when I think about why I still root my devices, the only reason (besides installing custom roms to get the latest security updates and features after EOL) is to block ads.

In particular, the installation of a (root) certificate to intercept advertising that is delivered via HTTPS.

I don't want to start a discussion here about how useful or reprehensible it is to block advertising in general.

In fact, I deliberately allow advertising on certain websites or in certain apps. Personally, I am only concerned about very intrusive or questionable advertising.

However, since advertising is the main source of income for Google, for example, I can certainly understand and respect their efforts to take action against it.

It will be an eternal cat-and-mouse game in which every developer will lose out at some point unless they make it the center of their life. And even then, developers who make their source code publicly available would always be at a disadvantage compared to the countermeasures of large(r) corporations that do not publish their development.

With regard to the mismatch situations, I think that obfuscation/spoofing might have to be extended to other apps or services. I could well imagine that if suddenly many identical fingerprints are transmitted to the Google servers for verification, this triggers further verification by other Google (related) apps/services on the devices in question. If the device then transmits the fingerprint spoofed by the module together with the "real" fingerprint, a mismatch occurs, and the identical fingerprint transmitted only by GMS gets flagged aka. "banned". Which means, in this context, that an additional check is always triggered for everyone as soon as this "flagged" fingerprint is checked.

Accepting my incomplete knowledge of this subject, that would at least be my theory.
[Magisk] titomax82:
An idea could be this one:

If @chiteroman or @osm0sis or whoever else has a large pool of working fingerprints, someone collects them all and there could be a magisk module that every time is installed for the first time, or manually updated, takes a "random" fingerprint from the pool collection. So the problem of too much people having the same fingerprint would be limited.

Am I mad?
[Magisk] V0latyle:
In this particular case, advertising isn't the issue. They already block apps from the Play Store that implement ad blocking, such as the NordVPN APK with Threat Protection

True, but as I've said before, never underestimate a forum full of hackers who refuse to be told "no".

Correct, although we aren't sure what other apps or services may be involved. It's research in progress.

I did suggest this before.

The only issue I have with it is that such a solution would invariably mean exposing that pool to whoever has the time and desire to find it. I wouldn't be surprised if Google's "white hats" are trolling this forum as well as the projects involved.
[Magisk] Vision:
View attachment 6043122
[Magisk] me_droid:
Well, I finally got the hang of using PixelFlasher to test build.props and found a few fp that work. I'm using the v2 Play Integity Fix (DEV). What's the next step - if I've edited the pif.json in PixelFlasher, am I good to go?
[Magisk] andrey-seo:
I disabled more modules and rebooted the phone but this is not help
[Magisk] acwcanada:
I am seeing that you are using the Experimental 2.4.0 mod 2.0 which is broken for phones launched with A13, use 2.4.0 mod 1.3 or @chiteroman's PIF.

Also you have some rare modules both in Magisk and Lsposed, if changes according to the above doesn't help, suggest to uninstall all of your modules and start from scratch, sometimes disable is not enough especially for those in lsposed. With Magisk installed and rooted, just install 2.4.0 mode 1.3 or @chiteroman's PIF, you should pass device and basic integrity, then reinstall those of your modules one by one to find out which is the culprit.

By the way, your modules in lsposed beside AOSP Mods is not familiar to me, but they looks suspicious to me base on their description. You mentioned that yours is a Pixel 6 with official A13, then why you need module such as "pixelify"? Too many modules can complicate your issue as some of them may conflict with each other.

My wife has the Pixel 6 on A13 and I myself have the Pixel 6 Pro and 7 Pro on A14 beta 5.2, I rooted all them and never have your problem. Hope my suggestion can help you sort out the issue.
[Magisk] zgfg:
I asked you to uninstall Lucky Patcher

You must also uninstall XPrivacyLua and not just uninstall but manually clean the garbage it leaves, because that garbage will still cause detections

Please take your time and scroll about the older posts (and search on XDA, there are other similar threads and similar things are asked and answered here and there), eg XPrivacyLua was already mentioned several times when the other users had problems with, what to do, how, etc

And you could test yourself. Remove everything else, have only Magisk, Zygisk, Shamiko, DenyList properly configured (there are posts end threads describing that) and this module and then test

Then later you will see if you add your things like LP, Lua how they badly affect

So you will see what you can have and what not
[Magisk] andrey-seo:
I removed all the magisk and lsposed modules, cleaned the phone through Sdmaid, I rebooted my phone but it didn't help.

I need for unlimited storage