yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Did you uninstall LP as asked - with LP you will never pass

Did you uninstall XPrivacyLua and manually cleaned its remaining files - without, you will not pass.

I don't believe that SDMaid could clean XLua remaining files because those files are not the type of files (and not stored to the standard folders) what the 'normal' apps leave and what SDMaid then knows to clean .

Bit if you think that your methods are better, then please don't quote and ask me.

XLua GitHub page provides clear instructions how to manually clean the XLua remaining files

Not sure about that module for unlimited online photo storage, but please be aware that that kind of modules spoof.the props for the phone model and ROM, while the same (but in the other 'direction' and among other things) is also needed to spoof Play Integrity,. Hence who knows what you could obtain as a mixed result and how it then works or not

Also, some people have better results with the Play Integrity Fix module (from this thread!) than with the USNF module (from the other thread) that you apparently use per your screenshot. Btw, if you use that USINF module, it would make more sense to ask about in the USNF thread

Last but not the least, you will not spoof Play Integrity if your ROM or Kernel enforces SELinux Permissive mode. I'm just saying that, I don't know anything about your potentially a custom ROM (needless to say, ROM must have GApps built-in, I don't know is it still possible to spoof Play Integrity with MicroG or so or what additional tricks it requires)
[Magisk] andrey-seo:
.I already tested this module - it did not help. I have a playmarket mod, although I then installed the original - it did not help.

I will try that too..

Yes, I know, I have already deleted all the modules and cleaned the data more than once. No result yet
[Magisk] andrey-seo:
Yes,I uninstalled lp

It's not help me...
[Magisk] andrey-seo:
.What modules do you use?
[Magisk] pndwal:
Something to try (especially if you haven't done this since running a custom kernel, installing any flashed mods eg via TWRP, messing with system apps etc): Dirty flash your ROM and root again... 😶 PW
[Magisk] andrey-seo:
I updated the firmware, it didn't help, probably only a clean installation is needed
[Magisk] acwcanada:
I rooted my phones to enable that I can use call recorder because I need it for my business so I only have a couple of modules which PIF is one of them and AOSP Mods and JamesDSP are the others.

You have a few of very suspicious modules and you have LP which means you properly have some pirated apps, one or more than one of them may have ****ed your system, as you said eat the bullet and have a clean installation may be your only option.

Just my two cents: if your phone is your daily drive then don't treat it like a toy! The principle is that if a feature or function can be achieved by an apk then don't get it with a module; never use LP to get pirated apps, pay for people's hard working to get you the app you want. You told me that you use the " Pixelify" module to have unlimited storage!!! How in the world that you think that's a smart idea? You relay on a module to crack one of Google's feature? Did you ever consider that somehow someday that module may not work again or Google just fixed the hole then you would lose everything you have stored there? Anyway if the phone to you is just another toy and you don't mind from time to time you may have similar situation again which you need to clean reinstall system, then just ignore what I said and do what is in your pleasure.
[Magisk] pndwal:
You mean complete rom, not just firmware drivers right? (I'm used to Xiaomi where firmware generally means only the hardware drivers...)

... Try this:

Uninstall USNF/PIF

Reboot

Clear Google Play Services data

Install USNF Displax 2.4.0 mod 1.3 or 2.0

Reboot and check again...

Try factory reset if that doesn't work...

Nb. Integrity verdicts can also be broken even after relocking B/L w/ stock ROM when /persist (partition) has been messed up by custom ROMs or other mods... If you think this may have happened, please see comments/links I put in a thread reporting a this issue in a poco device (and note the thread title):

- https://xdaforums.com/t/cts-fail-even-with-locked-bootloader.4613007/post-88837771

- https://xdaforums.com/t/cts-fail-even-with-locked-bootloader.4613007/post-88839819

... If needed, I'd try the second suggestion before flashing /persist (unless you have a backup from your device as this will include unique numbers for IMEI, S/N, BT, WiFi, MAC etc unlike the generic /persist image in ROM), especially if you've never actually messed with that... (Nb. Seems issue can occur simply due to downgrading directly from A13 to A11 or similar... Go A13, A12, A11 etc).

🤠 PW
[Magisk] Yeedatoy:
Once you install lucky patcher, if You've done things like patch to android, even if you use the magisk module and remove it, things still remain. Even if you delete them manually it usually takes a full wipe and reflash to get all traces removed
[Magisk] rodken:
Lucky Patcher can and will modify the system files on your device. This means that if something goes wrong, you could end up with a soft bricked device [if your lucky]. Of course, this means that you could potentially damage your device if you’re not careful.

-- Usually, formatting the data/factory resetting can help.
[Magisk] andrey-seo:
Перепробовал все, кроме сброса настроек и чистой прошивки. У меня есть подозрение, что возможно это произошло из-за установки мода маркета, но это не точно, так как когда я вернул оригинал, ситуация не изменилась.

Mod translation: Tried everything except factory reset and clean firmware. I have a suspicion that this may have happened due to the installation of the market mod, but this is not certain, since when I returned the original, the situation did not change.
[Magisk] philidor:
Maybe you need a clear installation
[Magisk] FIERA03:
After all, it's not clear for me whether Google Wallet checks STRONG or not.

I don't believe it does, but has it been changed to only check DEVICE? Or is the PI Fix still the same and just bypassed?
[Magisk] philidor:
Don't think it check strong. It works flawless with just device and basic integrity
[Magisk] Bladius:
with Lucky Patcher it is so that until the application itself is turned on, the tests pass. Only after turning on Lucky Patcher from the icon level is a negative result. Surprisingly, not always immediately and not on every phone. The same thing happens after updating Google Play Services. The strange thing is that my daughter, who has the same ROM and the same phone, even with Lucky Patcher on, the tests pass
[Magisk] ykjae:
I've always passed every device with lucky patcher. Android faker and xlua caused me to not pass several times. Also watch with any xposed module what apps you hook into.
[Magisk] zgfg:
And you (not you or me but) make a bot who connects to the same address, every time as a 'new' user and pulls one more custom json.

Not the one bot but several bots crawling in parallel.

Over time they will pull a significant part of them

You should have a sophisticated backend and not the open source module to prevent that kind of fraud'
[Magisk] rseiler:
Isn't that only recommended for one particular line of phones (I forget which)? I didn't see that he specified what he has.
[Magisk] sawdoctor:
If you are passing basic and device integrity with the json file you created then that's it your good to go
[Magisk] EasyDeath:
Is there a way to "unban" blocked fingerprints if they still work on original devices?

Also someone knows which apps are using MEETS_STRONG_INTEGRITY?

Let's say in 2024 or 202X all big companies decide to use "MEETS_STRONG_INTEGRITY" for all their apps, Video, Social, Messagging, Keyboard, Browser, Banking, etc

What will be our options then?
[Magisk] Iridule:
Prepare to reset wallet, just got the new update. It now does not go through GPS. I added wallet to deny list and had to reset everything.

View attachment 6043139View attachment 6043142
[Magisk] Iridule:
Lock bootloader and not root or figure a way to spoof that bootloader is locked.
[Magisk] me_droid:
Excellent, yes after reboot still passing!
[Magisk] hassanhassan:
I have a working fingerprint, it appears some banking apps are still detecting root even though prior to this, it was working fine.

I'm running magisk 26.4, play integrity fix 14.2 only. Was able to add my cards to wallet, although haven't had an opportunity to purchase something yet.

I had the banking app on the deny list and it worked before all this craziness with fingerprints. Magisk is also hidden.

Edit: I HAD a working fingerprint, its been burned :(
[Magisk] zgfg:
Not root - must be understood broader, not just not to install Magisk but to stay or go back to the stock/official firmware

Install the Bootloader Spoofer and you'll see that it does not help

Or, there are specific phones where you can have a custom ROM with lockedvBL, but you will not pass Strong Integrity

Strong Integrity requires everything, locked BL AND stock firmware

On 'normal' phones (whatever that 'normal' means but by far, most of our phones are 'normal') and with 'normal' tools you cannot have locked BL with custom ROM/Recovery/Kernel/modified Boot, etc - hence it is usually shortly mentioned as 'locked BL' and some ppl may then wrongly think that just hiding the unlocked BL will make it to pass Strong
[Magisk] Depressed T.Bear:
I think you're getting something mixed up here. A functioning fingerprint has nothing to do with hiding root.

If you have an additional self-found fingerprint, use it. Otherwise, you can always switch to the official version of PIF with integrated working fingerprint.

You can use apps such as Momo, TB Checker etc. to find out how your root is being detected. You will then find many methods of hiding roots here or elsewhere. If you have found out what the problem is and still need help, you are welcome to reach out to us here again :)
[Magisk] xSnowLeopardx:
10 days -> first found fingerprint still working with v14.
[Magisk] wugga3:
Hi

I've read this entire thread on the past week or two... Gone through a mountain of popcorn...

Thanks

Now I'm still far from any expert and probably more confused than ever......

Question is:

Is any Android device capable of having a so called spoofed fingerprint suitable to try and use... Yeah I'm guilty of just using the one provided as is thanks.

So can a fingerprint be used from and Android TV box? Any Android automotive radio?

Or does the print specifically have to come from a mobile cellular only???

I'm itching to take the time to experiment ...

But I'm also interested in my line of thinking had any validity. Cause if it's valid... Then the potential list of doner prints should be numerous to choose from?

Thanks
[Magisk] majorfigjam:
Current default is a TV box.
[Magisk] zgfg:
In one of the latesr versions of PIF module, spoofed fingerprint from the NVidia Android TV was built-in
[Magisk] glennza:
I have also had two fingerprints banned that I found myself. Gone in less than 24 hours! I have been on the third one for about a week now and it is still working
[Magisk] purgy:
Which brand were you using fps from?

There was someone using an Asus print which got blocked, but they didn't confirm if it was the same fp being used in the mod.

As Asus is a) fairly well known and b) close to the start of the alphabet, so it makes sense that they would be being used more.
[Magisk] glennza:
I think the two that stopped working were a ZTE Axon7 and a OnePlus7 Pro
[Magisk] Nergal di Cuthah:
Out of interest, how often do you think api calls from your phone happens. both ones by you checking via app and apps you use that make the call (like wallet or if your bank makes the check)
[Magisk] Iridule:
I have found 50 prints. and a few I consider rare as they are from very hard to find sources and Have noticed one with API level 30 that would not pass device yet when API was changed to 0 or 00 or anything below 26 It will pass device, if API was blank "" it would not pass either. I've about 5 prints out of 50 working ones that I would consider very rare with API 30 that work as is and took days to find. Though I am still on my first print I found last week with no issue.
[Magisk] glennza:
I have no idea!
[Magisk] Nekromantik:
i give up lol

tried 10 fingerprints and some dont work at all and others just pass basic
[Magisk] Umgak:
13 days with osm0sis fork, first print still good.
[Magisk] Nergal di Cuthah:
Even an estimate? Or a lots/not much

Can i ask the same question of you?

How many (estimate of course) calls to the api is your device making?
[Magisk] Iridule:
I just went back and checked 30 of my found prints they all still pass.

If the API level is 30 or 28 and it does not pass changing API to 00 worked every time for the ones I have found. I am not sure why.
[Magisk] Nekromantik:
so you found ones at 28 or 30 and changed to 00?
[Magisk] Iridule:
yes. often I have found these that will work by changing API can pass basic first then if API is changed to 00 or 0 they will pass device. Every one that works by changing API can all have 00 as API and they all pass.
[Magisk] Hutch MD:
Anyone else having trouble checking Play Integrity through any app? TB Checker and Integrity Checker are giving my API Token errors...

Asking because even though I can use GPay, my McDonalds app suddenly stopped working, along with a few other apps I have that try to use location services...
[Magisk] Nergal di Cuthah:
Use playstore developer options, its api limit is higher
[Magisk] Hutch MD:
Thanks, the funny thing is that it's supposedly passing Play Integrity and can use GPay, but some apps are still not working as of today. Perhaps it's because the fingerprint I'm using is too old?
[Magisk] Umgak:
Hard to know precisely but not many - I don't use the integrity checker unless I get an error, I just buy drinks at work for the most part.

Edit: not to mention, PI verdict is cached for Wallet so even buying things doesn't generate more PI calls. It's just whatever it's doing passively in the background - none of my other regularly used apps use PI.
[Magisk] purgy:
I did get a weird message from my bank app after using my own fp, something about it "being updated for Android 8", and needing to set up tap to pay in the app again (I have never set it up).

So I guess my bank app at least is getting some info re my device from the PI service, even though it doesn't care about BL status or root lol.
[Magisk] Iridule:
Not sure if anyone would find this useful but I was just trying to understand more about how API integrity works. I found this... Much of it is irrelevant but it does link out to a developer page where it explains there is a beta for people making programs using the integrity checking API... Could this be how fps are getting banned?

"Recent device activity (beta)

You can also opt-in to recent device activity, which tells you how many times your app requested an integrity token on a specific device in the last hour. You can use recent device activity to protect your app against unexpected, hyperactive devices that could be an indication of an active attack. You can decide how much to trust each recent device activity level based on how many times you expect your app installed on a typical device to request an integrity token each hour."

Integrity verdicts | Google Play | Android Developers

developer.android.com

How to configure the Google SafetyNet check

The Google integrity check (Play Integrity API) for Android devices is now available in the Cortado administration portal, where it replaces the Google SafetyNet verification. You can use the integrity check, for example, to detect rooted devices...

support.cortado.com
[Magisk] beeshyams:
Thanks for the find

Yet, something is missing. I tend to collect around 30-40 prints to test and test in one sitting maybe an hour. Finally, switch back to the working custom FP and check.

So, going by this logic I should have got banned? Maybe missing something
[Magisk] Iridule:
I'm not sure which apps may be using that feature or even enforcing it. I wonder if Droid guard can see the real device making so many requests from spoofed prints? I'm not sure...might be a good idea to limit daily integrity checks.
[Magisk] Gilg@mesh:
still works with custom one found about 2 weeks ago.
[Magisk] sga999:
For 14.3, I can see info in the logcat about the current pif.json being used as default. Then I change to DEV-v2 and put corresponding lines into pif.json and do the Integrity check with Play Store. It fails both basic and device security. I'd like to see this work out of curiosity mostly. Also I might learn interesting things about Security Patch and First API level.

I cannot find a dump of that rom anywhere, so I can't get the build.prop. If I could, I would input it into Pixel Flasher so that it could create a "good" pif.json. The logcat does not show me the 2 fields that I mentioned, so I'm putting values that I think are correct. But they must not be! When "DroidGuard detected!" appears after a logcat line, does that mean it is invalid? I do see that warning after those 2 fields in the logcat. (The first 6 lines of my pif.json are easy to choose. I think Build_ID is easy also. I think VNDK_version should match First_API_Level?).

I tried different values for API and VNDK based on osm0sis' advice in other posts, but it didn't fix it.

Has anyone gotten that specific pif.json to work? If so, and you don't feel like writing it here, I hope you can PM me. But I would imagine that mentioning the values for Security Patch and First API level (and Build ID and VNDK) are not that revealing. I guess the source code or Telegram might give me the answer, but I hoping to avoid that.
[Magisk] Umgak:
No. It's just a log showing that PIF has detected a PI attestation attempt. DroidGuard detected doesn't speak anything to whether the json is valid.
[Magisk] sga999:
@purgy pointed me to the code where it lists the correct lines (thanks). They matched my first 7. And those 7 make it pass both. I had 3 extra, which must have been causing the problem...no idea if it's one of them or all 3 that need to be removed. I'll probably figure that out soon. I was under the impression we needed more lines to complete it rather than less.
[Magisk] Imnoa:
Try lowering the api level to 24(~ish) for the ones that only pass basic
[Magisk] hakkitarion:
For those who have problems with banking apps where the root is recognized, I can only recommend renaming the file /system/addon.d/99-magisk.sh to "something.sh".

But after every update of Magisk a new file with the name 99-magisk.sh is created. Then you have to delete the old renamed file and rename the new file again.
[Magisk] xSnowLeopardx:
Would be neat if that was also done automatically when the user toggled to hide Magisk. That the name of the file (and other names where magisk is used maybe?) would be changed to something arbitrary as well.
[Magisk] woody4165:
Strangely, even if the app Play Integrity API Checker return me device and basic ok, when I use Google Wallet there are no error message, but it does not let me pay
[Magisk] Imnoa:
Remove the cache of google wallet, play services and the google app (iirc) and reconnect your card to the wallet
[Magisk] woody4165:
Thanks

Just done.

I will try as soon as I will do a payment
[Magisk] trevtdogg:
insufficient funds? ;p
[Magisk] bombadier:
Keep grinding away, its a numbers game, I spent an afternoon at the coal face and have about 6 that are working as of yesterday
[Magisk] xSnowLeopardx:
Don't wanna annoy you with this, but with the right set up, 10 is like done in 5-10 minutes. Did you read my tips mentioned here?

🔧 [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] kolouch.petr:
I ordered pixel watch to prevent problems with google wallet. Yesterday I was not able to pay in shop. It is not reliable
[Magisk] Nekromantik:
Yes I used the dumps link but I can't use pixel flasher as I have kernel su and not magisk. So it's more time consuming as I have to use script to create pif and then push to phone and test.
[Magisk] xSnowLeopardx:
Ah, I see. Alright then.

May I ask why you chose to root via KSU? Just out of curiosity.
[Magisk] Dj Telo:
The watch is just an extension of your phone. If Wallet does not work on the phone, it won't work on the watch.
[Magisk] intel_core_i7:
Some claimed that wallet on their watch works normally when their phone's PI fails, so who knows? At least you always have an option to return the pixel watch if your statement is right if you're living in the US.
[Magisk] awarexda:
Today I decided to start FP hunting...

But it didn't start well:

Avast detects FileRepMalware when trying to install pixelflasher downloaded from github...
[Magisk] krakout:
Is this possible? 14.3 installed, have paid successfully over the past weeks with no issues... View attachment 6043411
[Magisk] sawdoctor:
If you have a watch with built in LTE in can be used without a phone at all. I regularly use my pixel watch to pay and leave my phone at home, not 💯 certain it would pass if phone fails PI but can't see how it can check if phone is at home
[Magisk] osm0sis:
Even on watches with only Wi-Fi/BT, it's got its own Wallet app and its setup is independent of Wallet on the phone. Since the watch is locked bootloader it always works.
[Magisk] badabing2003:
What is it that it's not working with kernelsu?

What are you doing, what outcome are you expecting, and what are you getting instead?
[Magisk] badabing2003:
Please read the OP of PixelFlasher
[Magisk] beeshyams:
That's a known false alarm

Either turn off avast or force it to allow running Pixel Flasher, if it has such an option

This was discussed many times in the Pixel Flasher thread
[Magisk] beeshyams:
A random thought.. While I was harvesting FPs, it struck me that it could be an exercise in futility if Google decides to match Droid Guard with device properties
[Magisk] pndwal:
Seems that's what they've been doing, but not universally and now print by print... That's the interesting thing for me... I can see several ways they could make things fairly impossible for us, but looks like they're playing with us... Probably taking bets about how quickly we can bypass their blocks and having a few laughs!...

If Google hasn't killed this thing by now I doubt it's their intention somehow... PW
[Magisk] Nekromantik:
Pixel flasher has magisk option where you can test the pif files but this requires magisk to be installed. When I press it nothing is displayed as there is no magisk app on my phone
[Magisk] beeshyams:
That's the only hope :)
[Magisk] Dj Telo:
This is not the behaviour that I've been observing with my setup. In fact, most of the times that I've seen Wallet fail after a period without issues, it's been when trying to pay with my watch. Payment with watch fails, I open wallet in phone, Wallet complains about not meeting requirements. If I replace my fingerprint, then Wallet works again in phone and so does in watch.
[Magisk] HippoMan:
Whether or not the Googlefrinchians ever end up matching the FP with device properties, once they switch to requiring STRONG integrity, we'll be hosed anyway.
[Magisk] HippoMan:
Just like the cat toying with the mouse for a while before finally pouncing and devouring it.
[Magisk] badabing2003:
The window does not open? or it opens but you have things disabled or not doing anything?

These are the rules that dictate enabling / disabling that Magisk button

['device_attached', 'device_mode_adb']

You have a device connected and in adb mode and you granted root rights to shell process?