yashsingh1/xdaforums huggingface dataset:
[Magisk] CityKev:
I've thought for a while that Google could make Strong integrity a requirement for sensitive applications such as banking, payment and ordering a McFlurry from McDonald's. I wonder why they don't just do that instead of playing around and banning spoofed fingerprints?

The choice then would be locked bootloader with everything working or unlocked with custom ROMs, root etc but no access to sensitive applications.
[Magisk] knoedelcc:
(Official) Magisk Canary (26404) + PIFork v7 + Shamiko 1.0.1 works for me and this kind of initial check.

(Play Integrity: Basic + Device obligatory)

Adding the app to the DenyList (both checkmarks) and clearing data/cache of that app should suffice.

Edit: No xiaomi.eu-Apps whatsoever
[Magisk] S1yRuleZ:
Update: it was the Xmlpak RE module that failed CTS check for me, or maybe conflicts with PIF in some ways. Removed and now I pass both checks again. My setup works if anyone wants to try it. Stock kernel of course.
[Magisk] matfcb:
15.4 passed Basic and Device on Xiaomi Mi 9 Pro 5G but only after installing Fp_downloader and playcurl for stock module from PlayIntegrityNEXT site. I used FP_downloader and copied json to adb/magisk modules/playintegrityfix. Then it passed Basic and Device.
[Magisk] bakaekze:
By educating yourself by reading this thread
[Magisk] V0latyle:
Because then any devices that did not support hardware backed key pairs at launch - i.e., those launched with <Android 8 - would no longer be able to run those apps. While Google has spoken out against fragmentation in the Android ecosphere and has been supporting things like Project Treble to try to reduce it, they've also sort of accepted it as the status quo, and they aren't ready to abandon those devices yet.
[Magisk] xSnowLeopardx:
Dec 2 2023 FP still working brilliantly with v14.4.
[Magisk] blu.italia:
View attachment 6061147

Testing FPs with new 15.4 version and PIFS. Click on retry helps. But perhaps Google use this information too, to block a user or that we couldn't get device integrity 🤔
[Magisk] osm0sis:
See my FAQ, #10

PIF FAQ

PIF FAQ Abbreviations DG = DroidGuard (SafetyNet/Play Integrity) GMS = Google Mobile Services (Google Play Services) PIF = Play Integrity Fix Frequently Asked Questions Q: What is a fingerprint and where does it come from? A: A fingerprint...

xdaforums.com

Edit: Oh wait, yours is different. That's just too frequent checks. Slow down. 😛
[Magisk] g1b50n:
On 15.4 i can still use own Custom PIF.json?
[Magisk] tom1807:
Sure, it will work. I did this in the past. But not sure whether Netflix implemented more checks since then, like when you start the app, that it checks for root.

One thing for sure is, you lose your L1 Widevine certification. So, you could try, you have nothing to lose.

And any reason to test another kernel?

Or you could try a similar approach like below.

Cheers

Tom
[Magisk] tom1807:
Use TB Checker, SPIC has this issue from time to time.

Yup, should work.

Cheers

Tom
[Magisk] rumia2802:
Already passed meet device integrity and device is certified on play store but for some reason this app https://play.google.com/store/apps/details?id=mypoin.indomaret.android

cant passed secure environment, idk what wrong with eu
[Magisk] tom1807:
Maybe the app has additional checks implemented.

For example, my first bank worked with Magisk and Hide Magisk, but the second didn't. Adter installing Shamiko my seond bank passed, but not the first one anymore. 🤪

Cheers

Tom
[Magisk] Slim2none4u:
Want a medal? Or a chest to pin it on?
[Magisk] sawdoctor:
View attachment 6061161
[Magisk] nicoco19:
Hello everyone and @simplepinoi177

It's not too difficult and can be quite easy, once you get the hang of it. Please take a look at the OP in this post I linked above. It's very wordy and not very concise (to cater to non-technical Android readers), but it is as useful as possible for complete understanding at all levels; then check out the workflow guide below (which is also the method used in the OP [Section 3]) and see how simple it is...

xdaforums.com

📳🔥 PixelFlasher, a GUI tool to flash/update/root/manage Pixel phones.

DESCRIPTION As the name suggests, this is an application for flashing (updating) Pixel™ phones (possibly all phones/tablets made by Google™, YMMV.) PixelFlasher at its core is a layer of UI (with bells and whistles) on top of adb/fastboot. orders, so...

xdaforums.com xdaforums.com

Unfortunately I don't really know at which stage I should start in the tutorial if you can help me please.

When I use Pixel Flasher, what file do I put in browse? And it does not detect my phone even though it is connected via USB-C to my computer, when I click on SCAN nothing happens and it remains grayed out.

1) Click on Browse button and select the location where platform tools are installed on your computer or phone system?? (What do I put as a file in Browse??)

2) Connect your phone to PC and press Scan button to find your phone?? (The SCAN button is gray and I cannot search for a phone)

Knowing that my phone is a Samsung Galaxy S23 Ultra rooted under the latest version of Android 14.

Thank you in advance for your help and have a good evening.

Nicoco19
[Magisk] Fentadroid:
That is really wierd.

I have a Pixel 3a.

Play Integrity Fix 15.4 installed with a custom FP.

If I flash a custom kernel (elementalx), Basic Integrity passes, but Device Integrity fail.

If I use the stock kernel, Both basic and device integrity will pass.

The problem is I cannot use the stock kernel with systemless hosts module enabled, otherwise the phone will freeze after reboot (it's a well known issue: https://github.com/topjohnwu/Magisk/issues/3171 )

Any solution.....?
[Magisk] justDave:
Have you tried Kirisakura? I know it works with systemless hosts and it's rumored that it's not causing Device Integrity to fail.
[Magisk] Fentadroid:
I will try!! Thank you, I will let you know.
[Magisk] droidman1992:
I wonder what the future holds now that kernel strings and build identifiers are being blacklisted. I still pass for the time being one Lineage OS 20, however, I feel that our days may be numbered.

Even if we keep up for now, it will be game over once MEETS_STRONG_INTEGRITY is enforced, Google is waiting until older pre TEE devices are retired and are probably keeping an eye on the version metrics. There will not be any workaround with a properly working hardware attestation and it is then that custom ROMs become useless to most people.
[Magisk] badabing2003:
It means that you haven't specified platforms tools.

You have to select the folder where platform tools is.

Not a file.

It's in the OP of the thread you referenced.
[Magisk] matfcb:
Error when checking Integrity on 9.1 version.

View attachment 6019145
[Magisk] shoey63:
Maybe @Displax realised, as @chiteroman is now discovering, that a universal fix is well nigh impossible. Particularly when ROMs with their own fix baked in are thrown into the mix🤔
[Magisk] chiteroman:
Send logs
[Magisk] mcreuter83:
V9.1 works with A52s A13 without USNF.. thanks
[Magisk] matfcb:
How can I generate logs?
[Magisk] mcreuter83:
@matfcb See first Post
[Magisk] mcreuter83:
@matfcb

logcat | grep 'SNFix'

You can do it with termux

Or PC with adb shell
[Magisk] matfcb:
Nothing happens in Thermux when I enter this command.
[Magisk] mcreuter83:
First enter: su
[Magisk] matfcb:
I entered su first.
[Magisk] mcreuter83:
@matfcb

You can test this... If you are in PC use: adb shell "logcat | grep 'SNFix'"
[Magisk] matfcb:
Now it works after I closed and opened Thermux again. View attachment 6019260
[Magisk] mcreuter83:
Send it to @chiteroman
[Magisk] matfcb:
I've sent DM to him.
[Magisk] Snakeforhire:
Have you installed the "root tools" termux package beforehand ?
[Magisk] matfcb:
I have root access in Thermux now. I didn't have first but I chose OFF in Magisk permissions to Thermux, then set it to ON and Thermux runs as administrator.
[Magisk] Phoebus89:
9.1 crashing play services on xiaomi EU rom on xiaomi 13 ultra. Dropped back to 9.0, all good again :) I have USNF installed too.
[Magisk] originalul:
I confirm that only Basic integrity and Device integrity is working on my samsung S21FE (g990b), with custom rom A13, last magisk canary zygisk activated, lsposed 1.9.1(7011). Last version of Google Wallet works perfectly. As long as Google Wallet works, I would not need to use the Bank application:) I worship you guys @chiteroman , @kdrag0n , @Displax . i wish you a lot of health!
[Magisk] pndwal:
Well it may be less of a priority now that @chiteroman builds are available, but with targeted spoofing already set in his mod 2.0 (despite shipping level set to exploit fake STRONGINTEGRITY for Pixel 2 -'nul' value - that no longer works for API 33+ devices) it should have been trivial to change mod 1.3's proper value spoofing (simply sets shipping API level to 32 if 33+) from global to targeted and supply an updated release... (I never understood why this wasn't done in the first place since the other two required/established prop based mismatches, ie. model and fingerprint, had already required changing from global to targeted spoofing to overcome issues with device specific functionality, and this worked well.)

This may not have fixed/overridden XiaomiEU custom ROM settings to exploit fake STRONGINTEGRITY for Pixel 2 or other strange/outdated custom ROM integrations which is the challenge @chiteroman refers to, but it should have been a universal fix for 'clean' ROMs and others that don't introduce bad or outdated spoofs (ie. break stuff) themselves. 🙃 PW
[Magisk] chiteroman:
Updated to v9.2

Should fix all problems in xiaomi.eu builds. I don't know if this also fix Elite.
[Magisk] xSnowLeopardx:
One medal, please.
[Magisk] arkzok:
In the installation process in Magisk I saw that I need to go to XDA and search how to download a certified fingerprint, but I can't find anything about it neither here, nor on GitHub. Help pls
[Magisk] Nergal di Cuthah:
Please read the last few days of posts, all your questions are answered in them.

Edit: Ok i'll cave.

How to search & find your own fingerprints [noob friendly]: A Comprehensive Guide w/ tips & Discussion for Complete Noobs (from one)

It seems Google has banned more than 95% of custom fingerprints, so this thread/guide has kind been laid to the wayside. But it's still a great resource to understanding the foundations of fingerprints and all that... This is for any/all utterly...

xdaforums.com
[Magisk] GabbyWC:
"Useless" because of a disabled tap to pay feature which is not essential or the inability to download streaming apps through Google Play for services that I don't care about? I'll stick with a rooted custom ROM and its benefits even after strong integrity checks are more common.
[Magisk] BillGoss:
Same here. My main reason for rooting my phone is to be able to back it up effectively using Swift Backup and (if available) a custom recovery (TWRP, Orange Fox). Also to customise my phone the way I like it.

Having Google Wallet work is nice, but optional.

But I also don't use/need any apps that want a secure device (banking, Netflix, etc).
[Magisk] sawdoctor:
Pretty much the only thing I can't achieve on my phone without root is perhaps the only thing we shouldn't need root for and that's theming. It's impossible to get amoled background without root. The monet engine is pretty much useless without root. I really can't get my head round why Google would bake in the monet engine and then cripple it.
[Magisk] EuK_V:
Do you mean recompile the kernel without "lineageos" in localversion name?
[Magisk] zgfg:
For me, rooting is fueled by a number of reasons

One of them (less important but anyway) just happened few minutes ago and kicked me to share this comment now

I've been in my old schoolmates WA chat. An old but a shy friend shared our valuable old time photo but protected by a View once. Hence I opened, took a screenshot and shared the screenshot back with greetings and comments

However, on the other side I'm not akin to carry around two phones - a rooted and a stock one. Hence things like Wallet NFC payments (IMO, safer and more comfortable than carrying around plastic cards), Teams and NFC Secure office entrance are among my musts. Therefore the needs for sine qua non root hiding
[Magisk] osm0sis:
If they wanted to end it today they'd have ended it today, but instead they added another fairly low effort check, though interestingly outside of the infinite Build fields and system properties that my fork of the module can already spoof. I'm both impressed and not worried at all.
[Magisk] tom1807:
Honestly, no idea, I don't use an alternate ROM.

But I guess this string can be found in the boot.prop or one of the other files on the mobile.

Cheers

Tom
[Magisk] tom1807:
Or USB Debugging not enabled.

Cheers

Tom
[Magisk] badabing2003:
That was my first reaction as well,

But then I saw this

So must have turned on adb at some point to root the device.

And this gave it away.

With platform tools, for sure it will be disabled.
[Magisk] TotallyAnxious:
I just had my first possibly burned print (very obscure) so I switched and rebooted. I passed again. So I switched back and rebooted. And I'm passing on the original print again.

So to anyone who is facing a possibly burned print. Don't forget to try rebooting!

I guess they changed somethings that might break something without a reboot. I don't bother with killing gms. Rebooting seems more "complete" when it comes to troubleshooting.
[Magisk] Nergal di Cuthah:
Custom Kernel? Pif flavor and version?
[Magisk] TotallyAnxious:
Kiri, osmosis fork v7
[Magisk] HippoMan:
Mostly the same here also: rooting so I can perform useful backups and so I can configure my device in the ways I prefer.

I use a hardware wallet (leather), and I only participate in these integrity discussions because of technical interest and to increase my knowledge about what the Googlefrinchians are up to.
[Magisk] Nergal di Cuthah:
Not sure if kiri is one of the "vanity" kernels that now trigger failures, but something to look into
[Magisk] TotallyAnxious:
You might have misread my initial post or I'm currently misreading your post lol.

But I said I was failing. I switched prints, rebooted, passed, switched back to original print, rebooted and was still passing.

Kiri is NOT triggering failures and there has not been a report of that made to the dev of the kernel. I have frequent conversations with the dev.
[Magisk] bakaekze:
Kernel name changer script is back (requires Linux or WSL on Windows)

PlayIntegrityNEXT/Kernel name changer at main · daboynb/PlayIntegrityNEXT

Contribute to daboynb/PlayIntegrityNEXT development by creating an account on GitHub.

github.com
[Magisk] osm0sis:
That's a terrible idea. What if Sultan named his default governor Sultan-ondemand or default scheduler Sultanfq? That script would fully break the kernel, if it would boot at all.
[Magisk] purgy:
Is there an idiots guide (or something close to it) on how to go about editing the kernel name?

As I'm running on A13 idk if I can expect any updates on that branch of sultan, if any are made at all.
[Magisk] mohamedabdalla798:
I am new here

I have s9 plus with noble 3.9

I am using pixel flasher to find working fingerprint

Do I need to reboot and clear gms data every time i update the pif.json , or should just check using PI checker after updating the fp ?
[Magisk] Nergal di Cuthah:
Pixel flasher will restart gms when applying the fingerprint, you may need to give shell root permission
[Magisk] Fentadroid:
I've found pixelbuilds kernel boot image for pixel 3a can be flashed over the stock ROM.

I've downloaded the boot.img from here

PixelBuilds | sargo

PixelBuilds

pixelbuilds.org

Patched with Magisk and then flashed via fastboot.

Basic and Device integrity correcty passes.... I know that is just a workaround but it works.
[Magisk] bakaekze:
You can try the following in Termux . You'll need to replace both occurrences of "KERNEL.zip" with the zip filename, and will need to replace "Sultan" with the banned name/word and "Slutan" with something appropriate.

1. pkg install zip

2. pkg install lz4

3. unzip KERNEL.zip Image.lz4 && lz4 -c -d Image.lz4 | sed 's/Sultan/Slutan/g' | lz4 -c -l -12 --favor-decSpeed - > Image-patched.lz4 && mv Image-patched.lz4 Image.lz4 && zip -u KERNEL.zip Image.lz4 && rm Image.lz4
[Magisk] anthonnyb98:
@osm0sis hi bro, is pif next playcurl compatible with your fork of the module?
[Magisk] osm0sis:
Technically probably yes since my fork can migrate a json file, but I don't recommend using anything by the Next developer. If you want to use the Xiaomi print then use my autopif.sh script.
[Magisk] osm0sis:
I literally just told you that's a terrible idea. 🤨

The real answer is open a hex editor and search for the keyword you need to replace, and make sure you only replace occurrences of it that are safe.
[Magisk] bakaekze:
Yeah, take precautions, backups, etc
[Magisk] badabing2003:
That's not helping at all.

The original script, which is already bad enough for the reasons stated above, at least it had few checks in place, you stripped those out and presented that as an idiot guide solution.

This doesn't help the community, he's better off with the original script, and that's interactive, and has gif guide.

Sorry if this sounds harsh, but we want to help out people.
[Magisk] Vision:
For quick and easy test (if you have already installed this module, test it only in past with v14 by @chiteroman) if FP working, send the new pif.json file to /data/adb and replaced the existing, go to setting/apps, found the Google Play Services and click force close (no need close the internet etc.) (i try it this with Total Commander the replace) after do the test if pass 2/3
[Magisk] Slim2none4u:
Got my big bib on! Anyone wanna hand feed me all the info so i dont have to read?
[Magisk] badabing2003:
As of this post, currently there are at least two people waiting to help out.

🎣 Pif Game Theory 🎣

Cooperate or Defect? This is an experiment to test if cooperation truly works (I personally believe that it does, but let's put it to test) What does this have anything to do with PIF? Well, I'm glad that you asked. In the spirits of holiday...

xdaforums.com

But there are rules, you'd have to carry the torch once you get it.
[Magisk] blu.italia:
View attachment 6061512

I don't have a good feeling with the newest changes on Google sides. So I test and test and test with PIFS but until now I don't find a working FP and after each change of FP I get the result above or the error message that I've posted yesterday. So Google made it harder and harder to get a working FP and to test the FPs.
[Magisk] V0latyle:
Wipe Play Services data and try again.
[Magisk] CZ.Kostra:
Does FP from Xiaomi.eu work for you?
[Magisk] blu.italia:
Where can I find it?
[Magisk] CZ.Kostra:
https://raw.githubusercontent.com/daboynb/autojson/main/pif.json
[Magisk] V0latyle:
Pixel Flasher can pull it for you
[Magisk] blu.italia:
8

Doesn't work.

PlayIntegritynext also doesn't work.
[Magisk] V0latyle:
Did you wipe Play Services data and start over as I recommended above?
[Magisk] CZ.Kostra:
Turn off all modules in Magisk. Install PIFork v7 and use FP from PM (FP Xiaomi.eu formatted for PIFork v5+).
[Magisk] Emmes:
🔧 [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

double check!
[Magisk] badabing2003:
What Kernel / ROM are you using?

What module are you using

What other modules do you have
[Magisk] Iridule:
Same print since Dec 4th...still going didn't even need to dig into my cache of 50 yet. 💯
[Magisk] Aldenar:
Despite updating PIF and adding a KERNEL key from the same ROM who's build.prop values I'm using (Not sure if matching these is required), I'm now still failing device.

In logcat, I can see the module returning the spoofed value correctly:

Spoofing kernel release! Original value: 4.19.282-lineageos+
DroidGuard got kernel name: 3.18.71-perf-gd30d7f9

Though both, uname -r and cat /proc/version still contain the original kernel version (Running LineageOS, so the "-lineageos" string is probably blacklisted), could that be an issue somehow?
[Magisk] osm0sis:
It wouldn't change how it shows in those commands, but yeah it's still broken. We're still working on it. He released it untested I guess.

Some kernel strings are blocked by Goolag · Issue #236 · chiteroman/PlayIntegrityFix

For example Sultan kernel on Pixel 7/Pro/a is blocked from Goolag since it has a string named Sultan in it. They are checking for blocked words (case insensitive) in the uname kernel string, so I w...

github.com
[Magisk] Aldenar:
Ah, apologies, got a little lost in the flood of "Halp it no work anymore!" issues on github. Will keep an eye out on the thread, thank you!

64×64 png

2.8 kB 🤦‍♂️
[Magisk] sawdoctor:
Same thing has just happened to me as well, getting 3 red crossess in play integrity checker as well. Google has definitely changed something
[Magisk] Umgak:
Come to think of it, why does PlayIntegrityNext require you to flash a second module at all? The main purpose of the playcurl module is just to install a curl binary, but Android comes with Toybox, which has wget, and Magisk itself ships with a full feature complete copy of Busybox within /data/adb/magisk/busybox, which can be used to run curl without installing anything else. The two scripts it drops could just be downloaded and run normally without having to throw them in /system/bin. I guess maybe slight convenience?
[Magisk] sawdoctor:
Google has changed something, they must have as i fail all 3 checks now

Edit running stock kernel on the pixel fold with latest osmosis fork
[Magisk] V0latyle:
One more time.

Did you wipe Play Services data?

Yes or no?
[Magisk] osm0sis:
Nobody should have to wipe Play Services data unless they were messing around in the app_dg_cache files.
[Magisk] V0latyle:
Ah. Fair enough
[Magisk] sawdoctor:
The fact the exact same thing has happened to more than one of us today is extremely worrying. Im stock kernel so it's not that and my play store is still certified. All I've done today is reboot
[Magisk] majorfigjam:
I noticed earlier today that my Pixel 6P (with Kiri kernel) was downloading a play services security update of its own accord. I don't recall the exact words as it flashed by when I pressed the "downloading" icon to see what was going on. I checked both Play Services and Play Store for updates, but nothing showing as updated, and Play System still shows 1 November. No new folders in app_dg_cache either.

However, I'm still passing 2/3 on my early December print after a quick reboot, so whatever it was didn't affect me.
[Magisk] V0latyle:
I have to wonder: Have all these sudden failures been with prints from specific builds of Android? Like, Android 7.1 for example?
[Magisk] Emmes:
i guess it still works because you are using a custom kernel. test if it still works with stock kernel
[Magisk] sawdoctor:
I've tested every working fingerprint I have and even the current xaiomi print and unfortunately all of them fail all 3 checks
[Magisk] majorfigjam:
Too hard, as I'd need to reflash stock images, and I don't have time right now.

I'll wait for full Feb updates to come through.
[Magisk] Emmes:
i ve read a lot of comments (telegram, sorry) that it happens to a lot of Pixel devices. Flashing a custom kernel fixes it.
[Magisk] V0latyle:
What version of Android are they from? Have you tried prints from older/newer builds?

Is this something that seems to be happening specifically for newer Pixels? I'm on a Pixel 5, and I haven't had any problems.
[Magisk] Nergal di Cuthah:
Pixel 6 pro and still passing basic and device with my found on xda fingerprint. So i don't think it's newer pixel phones.
[Magisk] purgy:
I'm still on stock A13 rom on my pixel 7a, and going back to stock kernel was enough to get 2/3 again, so I guess it's more likely a software than hardware thing?