yashsingh1/xdaforums huggingface dataset:
[Magisk] wfred:
Opposite of my experience.

My two credit union apps and three credit card apps work fine with just basic; although they do complain and restrict functions if they detect root. None of those apps have a direct NFC pay feature

I've also never had any issues using their websites on mobile browsers, even with root not hidden and basic integrity.

I don't use Uber or any streaming apps so I can't comment on them
[Magisk] SOCOM-HERO:
my question is why the latest versions of uber don't seem to work on second launch. the first launch of the app works, but if you close and reopen, it doesn't work. takes you to a web based environment that is basic functions only. old versions of the app do work. 4.489.10002 works for me.
[Magisk] Nergal di Cuthah:
Agree. The mods have already cleaned twice (at least), let's not have them have to do it full time or somewhat.

I've now spent 6 hours looking for working prints from stock roms on sketchy sites. Tadiphone was so nice because i wasn't downloading anything (those things which can infect my poor window machine). It can't be in PIG's interest for us to download from possible malware sites, files that are too large for virustotal's browser plugin.
[Magisk] wfred:
You're able to use Amazon Pay at point of sale NFC registers, gas pumps, restaurants, etc?

I've come across some places that accept PayPal's wallet, but haven't seen Amazon's in any store.
[Magisk] Fishawy:
@osm0sis @chiteroman This might be worth looking into. Any ideas?
[Magisk] mochamoo:
You've made your point. My point is you do your long way around method if you like. No need to continue to yuck it up for those here who choose not to do it that way. Google pay, play store and banking apps are all working great here without having to do all these alternative workarounds. Maybe you should try it sometime. Tap & pay takes less than 30 secs. Start your own thread and those interested can go read about it there. Thanks
[Magisk] vMAC:
I have your PIF module installed, and am currently using your autopif script. P8P is my phone.
[Magisk] FrogMaster-:
Are you suggesting that every single rom and relative fingerprint posted on Tadi is banned?
[Magisk] osm0sis:
Only ~95% of previously found working prints from tadi are banned, as has been stated a few times. 🤔
[Magisk] FrogMaster-:
Thanks for confirming that, I was not sure where that 95% figure was originally based off; despite reading the hundreds of pages that are present here. I just wrote a script to dump every single build.prop from Tadi, so I was mildly concerned my efforts would be in vain based off the previous comment.

5% is more than enough for me to continue. Haha. :)
[Magisk] Nergal di Cuthah:
5% of working prints, not every print in tadi was (pre 29 feb) viable. So your script will probably find 2-3% at most.
[Magisk] osm0sis:
Well the 95% actually includes those from all we found from all the sources I mentioned a page or so back, so tadi's proportion might be a little different, but it would be similar.

Edit: Just checked our notes, and tadi had about 14000 ROM builds, with about originally 700 working from that. I don't think it was disproportionately hit more with bans than any other place (except for maybe the chunk that was on pickaprint/PIFS which got pretty much completely banned), so with the 5% that remain... yeah, needle in a haystack a little bit, but they're there.
[Magisk] intel_core_i7:
Not always, especially banking and other old, region-locked obscure apks. I have stumbled upon such extremes

So you have to spend more time fiddling and giving up more of your privacy (in this case your whole hand) just to avoid PI. No thank you.

At least almost nothing here requires PI, unless you want to use a credit card on your phone. QR Pay via banking app is what people do here, and it's way better for your privacy because less parties know your identification, perhaps.
[Magisk] osm0sis:
You've been asked multiple times, by moderators even, to drop it.
[Magisk] krakout:
This is why I posted actually, from what I've read I shouldn't be having it so good so maybe something is going on that could help others...
[Magisk] mrjuniork:
A message from the friendly moderator in the neighborhood

Another day, another big cleansing...

Though most of it was due to some huge amount of spamming 😉

People, I can do this all day. Don't waste precious time by putting thoughts, accuracy and proper grammar into your posts, coz they will still be off topic and they will still get deleted!

Wanna talk about Aurora Store? Go find the thread.

Wanna talk about corporate entities? Go create a thread.

Wanna talk about other stuff that isn't somehow, even over a long shot, connected to this thread? Exactly, create a thread, join the proper thread!

Anyways, let's get back to the topic at glance.

Cheers and have a great one 👍🏻

mrjuniork
[Magisk] purgy:
It actually occurred to me that getting us all to use the same FP will probably make it a lot easier for g to differentiate between modders who want root, and those exploited devices who's owners are unaware they are rooted.

While the bad guys are no doubt using similar techniques, they likely would avoid the xiaomi print as they can't afford to have the attestation suddenly fail like we put up with.
[Magisk] V0latyle:
I don't think any rootkits out there are trying to spoof fingerprints. Social engineering (phishing) is a much bigger problem than malware on Android devices, and the latter is generally more intent on stealing data and spying on users than attempting to construct an elaborate masquerade of "everything is fine"...

But, I'm not a malware/security professional.
[Magisk] jrotaetxe:
Hi, FrogMaster.

Would you mind sharing your script? I would like to have the bulk retrieved just to save the enormous ammount of clicks having to DL every build.prop. Then is my work to mine them....

Regards
[Magisk] ykjae:
I am messing around with default values in the custom.pif.json and seemed to get an old print passing again? I am not a developer by no means.. So I'm not sure if this is a mistake or not? Also haven't rebooted my device yet. I added some values into the custom.pif.json and at first lost integrity now I have 2/3 back with the asus print.

Again, I have not rebooted yet and it may be so simple of just editing the wrong pif file.

Not sure if I should share? Let me know what you think.
[Magisk] osm0sis:
Is it the exact Asus print that was already used (and banned) in PIF? Care to PM me so I can try to reproduce what you're seeing?
[Magisk] badabing2003:
Was this exact print (without your recent additions) passing device before the leap year mass banning?

Did you change modules since? Or even versions?

Did you change the device you're passing on?

If the field prop is not one of the fields / props that you see in templates or common prints, then you might have uncovered something.
[Magisk] ykjae:
I added some fields and passed on the asus print which was saved as a backup. I then added the same additional fields to the current print and also passed. Now I'm failing device again. So sorry I thought I had something. I'll send the fields to osm0sis as requested but it didn't continue to work. I was on home wifi network when I was messing around and then went to work where I'm not passing any more. So seems to be just a random case.
[Magisk] Vision:
Still interesting, if a block it FP work again in random, may this is Google side error and maybe unblock it again by accident older FP
[Magisk] Claus….:
@V0latyle @osm0sis @Iridule As I recall, you had plenty of working prints, did you ever re-testet them?
[Magisk] osm0sis:
That's where our 95% reduction in working prints stats came from.
[Magisk] Vision:
This i want to ask @osm0sis your FP from november, if i remember right, still pass ?
[Magisk] Claus….:
I was thinking re-testing from time to time? As there were rumors that "banned" prints were "unbanned".
[Magisk] osm0sis:
Nope, banned Feb 29 with the rest. Much lamented here by me. The FAQ was updated to reflect it.

Key word being rumors. I've seen zero actual instances of one that was truly banned becoming unbanned.
[Magisk] BesoC:
How can I extract build.prop from xiaomi.eu images? simg2img gives 'bad image' error for vendor_boot.img. Also, there is no system.img in downloaded rom
[Magisk] osm0sis:
Why would you? That's a custom ROM. Also vendor_boot isn't an simg (sparse image), and there's no point in looking at vendor_boot images at all for our purposes.
[Magisk] Vision:
I'm sorry to hear that, i hope you found another, and i wish, Google never block it
[Magisk] Vision:
if the same like original Xiaomi Rom, open cmd in the same folder have the simg in windows run command simg2img.exe super.img super.img.raw after open in with 7zip and go to

Depending which build.prop

1. /system extract the build.prop

2. /vendor extract the build.prop

3. /product extract the build.prop

4. /system_ext extract the build.prop
[Magisk] V0latyle:
I think there were one or two that had been previously used with USNF or even early iterations of PIF that we found to work some time after they'd initially been broken. We aren't likely to see the same thing happen after the Great Leap Day Ban.
[Magisk] BesoC:
Does it mean that official Xiaomi roms should have same build.prop?
[Magisk] makeyourself:
Hopefully not an error but the banning mechanism itself. There must be some way that Google is getting the FPs it has "banned" to still work on genuine devices but not spoofed ones. One option would be crosschecking props.
[Magisk] Iridule:
What fields did you add?
[Magisk] Matthew3955:
When using a custom pif.json, the play integrity check must show the original fingerprint or a custom
[Magisk] Claus….:
Can you elaborate on why it will not happen after the Great Leap Day?
[Magisk] Captain_Throwback:
Have you read the FAQ?
[Magisk] Jdbye:
Is there any reason to use PlayIntegrityFork over PlayIntegrityFIx, or vice versa?

I've installed PlayIntegrityFIx for now and my device is passing device integrity. Didn't have to mess with fingerprints.
[Magisk] Vision:
Yeah i get your point.

Just a thought.

Unfortunately this mechanism send the instructions what block it from the Google server and can't we skip it until now
[Magisk] osm0sis:
I have a new one in the remaining 5%, after using the Xiaomi.eu one for a few days, as also previously mentioned.

That's still just from hearsay. We have never actually verified one was ever unbanned.

Made up ones that don't exist. He didn't actually do anything, just had a random cached result or something.

"BOOTLOADER": "locked",
"RO_BOOTLOADER": "locked",
"RO_BOOT_VERIFIEDBOOTSTATE": "green",
"RO_BUILD_SELINUX": "enforcing",
"VERITY_STATUS": "enforcing",
"KNOX_STATUS": "0",
"SYSTEM_STATUS": "official",
"RO_BUILD_TAGS": "release-keys",
"RO_BUILD_TYPE": "user"

Only BOOTLOADER is a real field there, and that's not what it's for: https://android.googlesource.com/pl.../+/master/core/java/android/os/Build.java#157

For example on my Pixel 8 Pro, ro.bootloader is:

:/ $ getprop ro.bootloader
ripcurrent-14.1-11208047

Plus he was using chit's module instead of mine, so even adding real extra fields and properties wouldn't have functioned correctly for him anyway.
[Magisk] Vision:
That's is good.

Yeah i'm still with the Xiaomi.eu, i try more than 200+, I couldn't find a single one, some neither basic can't pass 😂🤣
[Magisk] traversone:
after some test

-hades

kernel string is also part of this list. thank you
[Magisk] pndwal:
Are you using contactless payments w/ BASIC_INTEGRITY only?... PW
[Magisk] markfm:
/

Afraid that's not what this thread is for, perhaps look in the Motorola section, https://xdaforums.com/c/motorola.11990/
[Magisk] osm0sis:
Another kernel/ROM from 5 years ago. 😄
[Magisk] Nergal di Cuthah:
Maybe the kernel ban is separate and just to clean the world of old kernels that may be insecure by google abusing PI.
[Magisk] krakout:
Actually yes, I do... But nobody seems to care😂
[Magisk] HippoMan:
The following isn't the most up-to-date news, but I just want to post that just now I updated from PIFork 7.0 to PIFork 8.0. I simply went through the standard module-update procedure in Magisk without any other work, and it all went perfectly.

My current working FP (one of the less-than-5%) continues to function and give me BASIC+DEVICE integrity.

I'm running stock A13 on my Nothing 2 phone with Magisk Alpha 27001.

Good work (as always!) from osm0sis!

Thank you.
[Magisk] pndwal:
I do... Very interesting... I knew that in lands where contactless isn't included in G Pay/Wallet other payments can be made with BASIC_INTEGRITY only, but hadn't heard of contactless working w/o DEVICE_INTEGRITY for more than a day or two after it's lost...

Please can you give app version?... 👍 PW
[Magisk] pndwal:
Still can be considered fair game for PI as it's a sure signal that any passing DEVICE_INTEGRITY must be spoofed...

We need to hide so many such signals from DroidGuard and GMS already; Security checks going back to SafetyNet days were performed to detect rooted device, Magisk, KingRoot, SuperSU, busybox, emulators, Xposed and even Pegasus... Doubtless more have been added and indications of custom kernels seems like low hanging fruit to me. 👀 PW
[Magisk] krakout:
You mean for Wallet?

version 24.8.612478558

com.google.android.apps.walletnfcrel
[Magisk] D1stRU3T0R:
Hey, my both my intensity checking is passing, GP is certified, I can delete gp services and wallet data, reboot, and Wallet will be certified, but once I add my Revolut card, it's automatically getting "not supported".

I tried with another work card but that one doesn't work :D Can Google wallet ban specific credit cards and thus bricking Wallet app by making it not secured?
[Magisk] pndwal:
We've heard that some banks block cards themselves when 'suspicious activity' is detected including host devices failing DEVICE_INTEGRITY, sometimes for a short period and sometimes possibly until you contact them...

AFAIK, Wallet itself should be good to go if you see "phone meets security requirements" in Pay contactless setup. 🤠 PW
[Magisk] D1stRU3T0R:
So it's just blocking my Revolut card and bricking wallet? I see "phone meets security equipments" but dies shortly after adding my Revolut card.
[Magisk] D1stRU3T0R:
Same issue with another card that i never added. So it's certified but once it's contacting bank, it goes off making it insecure...

Pictures in reverse order, I'm in office and can't redo them xd

View attachment 6080358View attachment 6080359
[Magisk] miho171:
Not the case for Revolut, I have added (in Gwallet) the base card first and then the virtual one, other than another bank.
[Magisk] osm0sis:
Doesn't appear banned to me.

I tried -hades- -hades hades -Hades- -Hades Hades

And all were fine.

Edit: Ah! Specifically -hadesKernel is what's banned. (y)
[Magisk] ashish1989:
I have a mobile with Android 7. What are my options to pass device integrity to make banking apps work in it?

Playintegrity fix not working below android 8.0
[Magisk] osm0sis:
Upgrade your ROM.
[Magisk] ashish1989:
No upgrade available. Plz suggest
[Magisk] osm0sis:
No other suggestions.
[Magisk] Tirofog:
I'm trying to pinpoint a problem with my Pixel 7 airplane mode not switching on or off without rebooting, even in safe mode.

So I flashed stock factory image to eliminate root, but now I'm unable to add cards to Wallet, even though this was possible two days ago in the same scenario. Bootloader is unlocked but that's it; integrity check shows basic only. Surely it should pass device also?
[Magisk] ananskom:
15 March 2024 at 9 PM UTC+7

Google updating their security, this module is need update, current Device Status is no Certified.
[Magisk] Nergal di Cuthah:
If bootloader unlocked then fail device without PIF this has always been so
[Magisk] Tirofog:
Thanks, I incorrectly thought unlocked bootloader without root would give 2/3 pass..
[Magisk] V0latyle:
Nope. With Play Integrity it's all or nothing. To pass any of the labels without a fix or spoof you must have bootloader locked on factory ROM.
[Magisk] GohanBurner:
Randomly today my work apps (Teams, Office) are no longer "healthy". Tried reupping my fingerprint, didn't work. I went as far as to completely reflash both slots with a factory image and re-root and try again, still failing. Can this be fixed or did Google just break it for good?

✅ MEETS_DEVICE_INTEGRITY

✅ MEETS_BASIC_INTEGRITY

❌ MEETS_STRONG_INTEGRITY
[Magisk] pndwal:
You likely don't need PIF. Is it running stock ROM?

Try adding Google Play Services com.google.android.gms.unstable process in denylist (to hide root from DroidGuard/GMS) and installing old MHPC module (to set 'sensitive props' to non-suspicious values; the module does that by default, no need to configure)...

This method was all that used to be needed for devices running stock ROMs and launched with Android 7 or earlier (pre Keymaster 3) and still should work if Google's new spoof-banning/cross checking algorithms don't find anomalies with your device (we don't know exactly how they're checking yet)...

Can others running Android 7 or earlier report if you can still meet DEVICE_INTEGRITY? 👍 PW
[Magisk] FrogMaster-:
I'm assuming your company also uses an application called company portal. This is the application actually performing the root detection. When I found a valid fingerprint I have to completely clear all data for the company portal app before teams will function properly again.
[Magisk] GohanBurner:
Yep, Company Portal too. Have you found a fingerprint that greenlights all 3 of those checks? I haven't found one yet and I've tried many.
[Magisk] V0latyle:
Please read the first post in this thread.

The only way to get STRONG is locked bootloader on stock ROM.
[Magisk] GohanBurner:
Ok, then that means it was working without it previously. So then something else is going on. No matter what I do it keeps showing up as unhealthy. Cleared cache on Google Play Store, Google Play Services, and Framework, made sure that every microsoft app I have in addition to the Google ones are on the DenyList. Not sure what else I can do.

Are we supposed to still be using Shamiko and keeping Enforce DenyList disabled? Or is that no longer necessary?
[Magisk] Chrisch_91:
I have basic integrity and can use contactless payment. But since android 14 banking app detecting root and crashes. How can i fix it?
[Magisk] FrogMaster-:
You will not find a fingerprint that passes strong with your bootloader unlocked. You'll only ever be able to pass basic and device unless you reprogram your TEE losing your original certificate and keys in the process.

All you need to pass is basic and device for company portal to function properly. Try clearing the data for company portal and then restarting teams.

My set-up includes Shamiko, though I'm doubtful that it's entirely necessary as I had company portal working without Shamiko previously.
[Magisk] chiteroman:
Updated first post to clarify few things.
[Magisk] Captain_Throwback:
Perhaps you could also include a link to the PIF FAQ?
[Magisk] pndwal:
IIRC Portal users needed to manually add unchecked processes in denylist so that may help...

Since DenyList is not proper hiding (built only to revert/deny root modifications rather than hide them) I'd be using Shamiko (which actually properly uses hidelist mode, just hijacks list from DenyList). 🤠 PW
[Magisk] yeswap:
I have a rooted Galaxy S6 runing Android 7. It passes Device Integrity with the old Universal SafetyNet Fix Magisk module. However none of the US banking apps I tried (Citi, Chase, CapOne) are availble on Android 7.
[Magisk] osm0sis:
Oh?

safetynet-fix/magisk/customize.sh at dev · Displax/safetynet-fix

SafetyNet & Play Integrity API workarounds for Magisk - Displax/safetynet-fix

github.com
[Magisk] yeswap:
Although the code comment seems to indicate that Universal SafetyNet Fix doesn't do anything on Android 7, without it the rooted bootloader unlocked Android 7 device doesn't pass Basic or Device, with it both pass.
[Magisk] pndwal:
Yeah, USNF was made compatible with A7, then only 8+, then from 7 again with 2.3.1 with Zygisk parts disabled as fallback to BASIC-only is obviously not needed (already BASIC-only) and no prop mismatches (targeted with Zygisk) to bypass HARDWARE_BACKED evaluationType were needed either... Only hiding root and sensitive prop resets (and possibly a globally set fingerprint + security patch level for custom/China region ROMs) are needed...

Thanks for reminding me and confirming basic hiding and sensitive prop solution still works!... Method I described above should also work for you and A6 users too.

Please say which build/fork you use... 👍 PW
[Magisk] yeswap:
I'm using V2.4.0 by kdrag0n.
[Magisk] osm0sis:
Exactly, so all that should be needed is Shamiko on those devices.
[Magisk] pndwal:
Ah yes... That could work for Galaxy S6 assuming Zygisk refactoring for native bridge did actually fix the Zygisk problem with old (crippled) Samsung kernels... So Zygisk works on S6 now? (Haven't seen confirmation)... MHPC is a non-Zygisk alternative for sensitive props.

Of course, aside from Shamiko's sensitive prop fixes, user must add GMS DroidGuard/attestation process in denylist... 🤠 PW
[Magisk] osm0sis:
Well, avoiding Zygisk altogether someone could just use the updated boot scripts from my fork I suppose, or possibly the last USNF MOD would still work.
[Magisk] pndwal:
Yeah, I guess... I think both late @kdrag0n and @Displax builds should work, and @Displax mod version may have some non-Zygisk compatibility improvements although I don't think there'd be much difference for pre A8 LV device purposes... Clearly @kdrag0n's 2.4.0, while broken for most A8+ LV device users (Zygisk parts), is still good for devices not needing to spoof lack of a working hardware key implementation...

What's more interesting is that evidently Google's new spoof-banning/cross checking doesn't find issues even with a Nexus 6P (angler) fingerprint... This means that using USNF unaltered may work for pre A8 LV devices accross the board, including those running custom, China region or other uncertified ROMs... [Edit: see following posts]

I'm assuming (may be wrong) that (without USNF) root hiding + sensitive prop fix + devices native (not spoofed) fingerprint should also work for stock ROMs.

Also, assuming @Didgeridoohan's security patch aligned print sets are likewise not affected by Google's new spoof-banning/cross checking when used for devices not needing to spoof lack of a working hardware key implementation, root hiding + sensitive prop fix + a MHPC set fingerprint/security patch date should work (without USNF) for custom, China region or other uncertified ROMs... 🙂 PW
[Magisk] osm0sis:
Didn't we find all of MHPC was banned on Feb 29, along with all the arm arches on PIFS?
[Magisk] menuisier3:
Hello, since this morning, RCS chat no longer works. is there a solution ? THANKS
[Magisk] pndwal:
'Banned' for spoofing lack of a working hardware key implementation and allowing server side passes, but I thought you found all Nexus prints were banned for that purpose?... Maybe angler print wasn't banned?... PW
[Magisk] osm0sis:
No, I have always been clear that it was Shamu and older only that were 3x fail, which is different from a ban.
[Magisk] pndwal:
Do you have MEETS_DEVICE_INTEGRITY? PW
[Magisk] pndwal:
Maybe a spoofed print is needed even for stock devices running pre A8 then... Maybe the 2.3.1/2.4.0 anger print was just never banned at all... [Edit: see following posts] 🙂 PW
[Magisk] osm0sis:
Pre-A8 it isn't doing any device spoofing at all on USNF... Just the global props in the scripts. 🙄
[Magisk] pndwal:
Haha... Of course, thanks... I'll go back and edit my errata later... 😬 👍 PW