yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Interesting

So did you test and what does G1 report to you?

Btw, I wouldn't do that for Privacy reasons, Google (with agencies that have free doors open to Google data) already knows too much about us, no need to put all traffic into the Google hands
[Magisk] fbirraque:
At least for me on Poco F3 (alioth), Android 13, MIUI.eu 14.0.7.0 (Stable), Magisk Canary (26301), LSposed 1.9.1 (6997), HMA 3.2 the BootloaderSpoofer 1.2 works flawlessly.

The Key Attestation 1.5.0 confirms Locked Bootloader. (annex)

But could you please explain what is the advantage (necessity) in using this module since both YASNAC and Protect Integrity attestation remains only BASIC?

Thanks in advance,
[Magisk] zgfg:
That module has nothing with SN or PI - different things

It helps to spoof that BL is unlocked from KeyAttestation - not much use of that but it can make users happy

You can also spoof that Bootloader was unlocked from Momo - but then you trigger Momo to detect Zygisk, hence better don't (or who cares)

Theoretically, you could spoof the same way that Bootloader is unlocked from other apps (again, don't mix that with Strong Identity - btw, Strong Identity is not just that Bootloader is locked but that the whole Firmware was not modded, and that being digitally signed by Trusted Equipment Environment), but AFAIK there is no app that checks for unlocked Bootloader that way

Btw, both Momo and Key Attestation apps are from the same nest
[Magisk] fbirraque:
Thank you very much for sharing your knowledge.

I didn't know that!
[Magisk] supermansaga:
Google One VPN will simply keep being disconnected if the root hasn't been hidden perfectly. I am not among the lucky few
[Magisk] hanschke:
Can anyone please give me the url for latest test build please?
[Magisk] zgfg:
v8.6 is attached to a post from the OP couple of days ago
[Magisk] hanschke:
I have looked the last 10 pages and dont see anything.
[Magisk] Homeboy76:
Page1, post 1
[Magisk] sawdoctor:
The op and github link to 8.4. I don't know if there's an 8.6 or not though
[Magisk] Homeboy76:
I should have looked at the OP before posting.:(
[Magisk] chiteroman:
Someone on Github post an issue about Wifi calling not working:

bootloader unlocked can not hide · Issue #2 · chiteroman/PlayIntegrityFix

Momo tips bootloader unlocked, cannot be hidden Universal SafetyNet Fix v2.4.0_MOD Can be hidden

github.com

Very strange, but I think I know where is the problem, so I uploaded a new test build. Hope this works and can pass BASIC and DEVICE.

EDIT: Check OP.
[Magisk] GoblinHero:
It was me, and this build fixes the problem. Thank you once again!
[Magisk] chiteroman:
New version released! v8.5
[Magisk] ykjae:
Hey with bootloader spoofer besides hooking to key attestation app, which apps should we hook to if we want to spoof a locked bootloader?
[Magisk] chiteroman:
Apps which requires a locked bootloader like CIB.
[Magisk] zgfg:
I don't use WiFi calling but Device and Basic are ok
[Magisk] latamboy:
I returned to v8.4 because v8.5 removed MHPC and I've lost the way of change my device fingerprint
[Magisk] chiteroman:
Why you want to change your device fingerprint ?
[Magisk] CZ.Kostra:
adb shell "logcat | grep 'PIF'"

or Termux:

logcat | grep 'PIF'
[Magisk] intel_core_i7:
We have to pay to get our plastic cards. You want free cards? Then use your phone.

Nice country you're living in.
[Magisk] safelock1:
Ok I run working integrity on realme 8. to run you must change pif.json on working pif
[Magisk] Spartacus500:
14.9 error download...

Download from site ok, but 14.9 only MEETS_BASIC_INTEGRITY 😔
[Magisk] EuK_V:
Some glitch happened to my pif module or magisk or something - idk, but all my working fp jsons stopped working. I tried literally all versions of pif module - nothing. Three red crosses. No integrity..

Luckily I made nandroid backup in early december - I restored the system. Backup containd pif module of 13.4 version with pif.prop file and it's still working with my very first fp! (y)
[Magisk] xSnowLeopardx:
Still 2/3 on v14.4 - merry Xmas everyone btw!
[Magisk] miho171:
Same error trying download from magisk, since I already meet device integrity I didn't risk updating.
[Magisk] litaninja:
Was just about to give up thinking I must be doing something wrong & unable to get Device Integrity to pass, finally found a working FP on 14.9 running on OnePlus 6 Lineage OS, whew.

But after going through at least 20 FPs to get this, I have to wonder, why on earth with Google ban / be able to get away with banning so many devices?

Doesn't make any sense.

Thanks for all the help and good work!
[Magisk] TheRomRooster:
Because the sad reality is, most phones they ban are so old that they are only used by:

little kids as toys who only use it to play ****ty mobile games or watch tiktok

elderly people who only use them for phonecalls and whatsapp

people with low income who can not afford new phones and consequently also lack the funds to take google to court over it
[Magisk] Vision:
Merry Christmas🎄. I remember say you have v14 and all work good, eventually you update, how come ?
[Magisk] litaninja:
**sigh**
[Magisk] gpvecchi:
I'm struggling to find a working fingerprint; can you please tell me if I understood?

I have to be sure that it comes from Android 8, right?

Anything else? Thank you!
[Magisk] Some_Random_Username:
"Banned" fingerprints still work on the original device they're borrowed from, see below.
[Magisk] Vision:
Not exactly, you can use and from 7.1
[Magisk] Umgak:
The term "ban" isn't really accurate to what Google is doing. Users of the original, unmodified device are not affected - what's happening is Google is enforcing a stricter set of checks that we do not yet fully understand on the "banned" props, that the original device will pass, but a spoofed device will fail. This has nothing to do with old handsets given to children, the elderly, or low income as others have suggested.

It does not have to come from Android 8, but rather a device which was at some point upgraded to Android 8 during its lifespan. Prints from before and after the 8.0 versions still work from these devices. Some prints work from as early as Android 6. The most comprehensive understanding of what makes them work can be found here.
[Magisk] TheRomRooster:
ahhhh thats good to know, ive always heared that people said getting a pif banned will also **** over people who run the vanilla device on that specific os version
[Magisk] TheRomRooster:
just went through my PIFs

Oldest:

API 23

Launch OS: Nougat

Newest:

API 28

Launch OS: Oreo

try looking for anything in between those, just went through another bulk of 40 PIFs and managed to get 2 working ones out of it
[Magisk] eugenwollekneul:
i tried to install the aur over the garuda packetmanager octopi but it didnt work. dont know why.
[Magisk] TheRomRooster:
Just installed Pixelflasher on Garuda KDE Lite via pamac and it boot up fine and is working without any problems
[Magisk] badabing2003:
What doesn't work?
[Magisk] sawdoctor:
Remember it doesn't need to be from a phone, chiteroman has used 2 Nvidia TV boxes and an android camera. Pretty sure a few android tablets have been used as well, i know at least one android car stereo works. The more obscure the device the less likely others are using it and less likely to be banned.

If you try a fingerprint and it fails try changing the 1st API level before discarding it
[Magisk] xSnowLeopardx:
Wanted to try and keep up a tad. Will do this in the future as well: sit on the version that works until it doesn't, then update, or if it still works but I am more then 4-7 sub versions late, try to update as well.
[Magisk] Wolfcity:
My wife was sitting next to me when the Asus print of her device got "banned'. She's not rooted and nothing changed for her. We don't know exactly what Google is doing but locked devices have no problems when the associated FP get's banned.

Next time you may give @osm0sis PIF v4 a try. Very stable.
[Magisk] bigknowz:
Wasn't able to compile for Chromebook, error when running Ubuntu version:

penguin:~/Android$ ./PixelFlasher_Ubuntu_22_04

[374] Error loading Python lib '/tmp/_MEILNbOEq/libpython3.11.so.1.0': dlopen: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /tmp/_MEILNbOEq/libpython3.11.so.1.0)
[Magisk] eugenwollekneul:
i think i have the problem with the ssl certificate.

i tried to follow your instruction with "Download this file: https://codeload.github.com/TheFreeman193/PIFS/zip/refs/heads/mainOpen" but it endet with a 404 error, so i had to edit your link to "https://codeload.github.com/TheFreeman193/PIFS/zip/refs/heads/main"

after extracting the JSON folder and edited to "TheFreeman193_JSON" i had to find the working directory of the PF.

i followed your instruction "In PixelFlasher, under Help Menu, click on Open PixelFlasher Working Directory" but i ended with the following error:

2023-12-25 17:21:11 ERROR: Encountered an error while opening a folder.

Traceback (most recent call last):

File "runtime.py", line 1226, in open_folder

File "subprocess.py", line 1026, in __init__

File "subprocess.py", line 1950, in _execute_child

FileNotFoundError: [Errno 2] No such file or directory: 'nautilus'

i looked with the support function in to my logs and found the right working directory. in my garuda linux the working directory is "~/.local/share/PixelFlasher/"

i copied the TheFreeman193_JSON in to my above mentioned working directory and now the button works and gives me a random pif.

maybe you can add the function to edit the working directory in the PF settings, i think that was the problem for my ssl certificate because the working directory was wrong or is made for ubuntu tree.

the second problem with the xiaomi.eu print. is it only me who dont get the FIRST_API_LEVEL? no one else reported that issue?

this is the output i get if i hit the button:

{

"MANUFACTURER": "Acer Inc.",

"BRAND": "acer",

"DEVICE": "acer_c01",

"PRODUCT": "c01_ww",

"MODEL": "C01",

"FINGERPRINT": "acer/c01_ww/acer_c01:7.1.1/NMF26F/1521514970:user/release-keys",

"SECURITY_PATCH": "2018-04-01"

}

there is not even a "FIRST_API_LEVEL": "null" nor "FIRST_API_LEVEL": ""

btw: thx for all of you guys for your work for the community!
[Magisk] Vision:
Oh understand your point, I'm still in v14, work good for me
[Magisk] xSnowLeopardx:
Nothing against @osm0sis but I don't really care whose PIF I am using. If it works, it works, and if it doesn't, I'll update. If for some reason nothing of @chiteroman works and @osm0sis lets us know his fork works, then I'll migrate.
[Magisk] badabing2003:
The links I gave you was bad because before I gave it to you, I wanted to check if it was still working.

Which worked, but if you notice, it redirects to a link with Open appended at the end, which I copied and gave it to you without realizing.

Glad you figured it out.

The reason opening the folder did not work, is not because of the path, but rather the file explorer setting.

by default PF on linux will try nautilus, but you probably don't have it or the full path is not set.

Set the full path to your favorite explorer in PF's settings configuration and it should work.

Same goes for the shell.

Lastly, regarding xiaomi.eu, PF tries not to interfere with what is fetched from the xiaomi.eu apk, under the assumption that it is supposed to be functional.

It just happens that with the print they are not including the FIRST_API_LEVEL, but it should still work, if it doesn't just add it.

With the next version of PF, you would be able to reprocess a given json to fill in the blanks or set / unset fields that correspond the version of the module you're using.
[Magisk] TheRomRooster:
still some working TV Box PIFs out there, have a TV Box PIF in my backup PIFs folder in case my current one gets banned
[Magisk] osm0sis:
Mine's more future proof, so it's not just that mine works, it's that it'll work basically forever regardless of what extra checks Google adds for Build fields/properties without needing a new build.

So barring issues with the hooking ABI like we're currently seeing with ShadowHook on QPR2, it's basically one build to rule them all. Might just make it do builds with both Dobby and ShadowHook and then we're indefinitely good on even more fronts.
[Magisk] DwidPL:
Hello, since the latest two Play Integrity updates I cannot use the McDonald's application or contactless payments, I suspect fingerprints. I cleared the data of the Google Play, Google Services, Google Services Framework applications, and there were no changes. I would like to know when this will be fixed, hopefully in the next module update 😇
[Magisk] TheRomRooster:
u need to provide ur own PIF
[Magisk] DwidPL:
Sorry, but I don't know how to get it, where or how
[Magisk] Nergal di Cuthah:
There are three tutorials. Two listed in the most liked for this thread and 1 at the top of the magisk board. I linked all three in a message about 5-8 pages ago

Here https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89236566
[Magisk] Wolfcity:
Thanks to @osm0sis for clarification. I'm not so good in coding but what makes me confident is the fact that @osm0sis made two builds(ok,forks) of the module (incl. a very helpful script to be used directly on the device) and it's working until now. @chiteroman changed his stuff with each and every release (maybe that's why some people have problems?).

No annoyance but that's the reason why I prefer @osm0sis stuff.

Thanks for your work.😉
[Magisk] TheRomRooster:
Can confirm, been on osm0sis shortly after it released and im still on my first PIF without even having had to update to v4, just did it at some point just for the sakes of it even though v3 was still working fine. unless something unexpected happens, i think osm0sis fork and my 13 PIFs should last me till i get a new phone lol
[Magisk] xSnowLeopardx:
And while I respect @osm0sis and I am happy people enjoy his stuff, I am more of a "if it works with what I have, I am happy" guy. I am not gonna update with every release but also won't stay 6 releases behind. That also means that I don't really want/need to change to another module. It can be futureproof, it can be changed less times and therefore be more reliable, but I won't repeat myself anymore xd it just works for me.

I am already grateful I have more than 0 FPs. That is the big deal for me, not which module is sustainable.
[Magisk] DwidPL:
Hi im used https://github.com/daboynb/PlayIntegrityNEXT,

I would like to ask if this module and apk is safe because it DOES WORK and it is quite suspicious
[Magisk] majorfigjam:
Use at your own risk, you rooted your phone so you're taking a risk anyway.

Minimise risk by using Osm0sis fork, and your own print. Read up on how to do that, then step off the treadmill. If you're confident enough, grab the current print from NEXT, and use that in the Osm0sis fork.
[Magisk] TheRomRooster:
its really not difficult, its a bit of a learning curve at first but once you learn what to look for, youll have a decent little vault of PIFs in no time and can plug and play swap them out in case one gets banned. i even have a little gms killer script handy so if im at the store trying to pay, all i need to to is copy 1 file, execute the script and im gucci
[Magisk] Vision:
Merry Christmas🎄to everyone!!!
[Magisk] miho171:
Can someone repeat me the "gms killer script" posted few days ago? Tried to find in the latest pages with no luck.
[Magisk] choantet:
I had used @chiteroman v14 using @osm0sis guide to find fp. From December 2 to 19th, everything worked perfectly. On the 19th I changed to @osm0sis v4 simply because it seemed to be a more robust approach; and found another fp using @TheFreeman193 and all's well... PS certification, Device Integrity, Wallet, and bank app rock solid. Thanks again for everyone's help.
[Magisk] iwearthebelt:
Thanks to everyone who worked on this fix!!! Finally something that is working! Thanks for taking the time to get this up and running and Happy Holidays!
[Magisk] majorfigjam:
The Holy Grail?

View attachment 6048064

We can all live in hope.
[Magisk] chiteroman:
Locked bootloader or "hacked" it ?
[Magisk] Claus….:
Still on the first fp?
[Magisk] Vision:
The Miracle Of Christmas🎄🕊️
[Magisk] Vision:
I start to confused again with Strong 🤔. Maybe The Miracle Of Christmas 🎄🕊️
[Magisk] xSnowLeopardx:
You know it.
[Magisk] Vision:
I don't know about that but for quick test (if you have already installed this module) if FP working, send the new pif.json file to /data/adb and replaced the exist, 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] majorfigjam:
Once upon a time long ago, when I was very young, we were told to believe in Santa Claus, Papa Noel, Pere Noel, der Weinachtsmann, or whatever in the local tradition.

Are you a believer?
[Magisk] HippoMan:
Yes, and I'm sure that Santa will be bringing me my desired gift soon! ...
[Magisk] miho171:
killall com.google.android.gms.unstable

found it at the bottom of pickaprint.sh file
[Magisk] dmenezes:
You must be messing with us... STRONG is indeed the holy grail, but supposedly just as unobtainable.

If you're not just pulling our collective leg, can you tell us (or at least give us a hint) about how you achieved it?
[Magisk] dmenezes:
Same here, still on my first, hard-earned fingerprint (23 days and counting!) and @chiteroman's v14.0-resetprops module.

When (I'm starting to think, perhaps "if") it gets bananaed, I will upgrade to the latest from @osm0sis and a new FP using @TheFreeman193's pickaprint.sh script.

I wish you, our developers @chiteroman, @osm0sis, @TheFreeman193 and @badabing2003, and all our brothers and sisters here in XDA a merry Christmas and a great new year!
[Magisk] kodein:
I'm not sure, but I read somewhere that they tried this on the pixel phone: https://github.com/chenxiaolong/avbroot
[Magisk] sawdoctor:
Or photoshopped it?
[Magisk] eac5:
Nope, avbroot will have a SelfSigned boot state in the root of trust, strong integrity requires it to be Verified
[Magisk] kodein:
Okay. Thanks for the explanation. I wasn't sure about that...
[Magisk] kodein:
But I wonder if it's possible, or how he got there.
[Magisk] eac5:
Possible – I'm sure it is, but not trivial at all. That screenshot doesn't indicate anything on its own though. I could easily run the check on my locked unrooted tablet that passes strong and post the same result. Probably just some light trolling. Though it may be possible that some unorthodox fingerprint just passes strong automatically due to a Google misconfig like what happened with the Pixel 2 one from a few versions back, but I wouldn't bet on them repeating the same mistake twice.
[Magisk] xSnowLeopardx:
High chance of the former, low af chance on the latter imo.
[Magisk] BROKEN1981:
Out of curiosity, link to pick a print?
[Magisk] Umgak:
Here. None of my prints are in the repo, surprisingly.
[Magisk] BROKEN1981:
That's interesting
[Magisk] asisandroid:
anyone knows how many prints per week get banned? like so we know how long (if they keep the current strategy) we are able to use this method
[Magisk] TheRomRooster:
The public ones included in modules: Instantly

Private ones only you and the select few who happened to find it too use: Weeks-possibly months

My first private PIF is 3 weeks old and still good
[Magisk] TheFreeman193:
Yes, the export command simply sets an environment variable (FORCEABI) and my script looks for this to override the directory it picks from.

If you find profiles from another directory work for you, you can make the variable persistent in Termux with:

echo 'export FORCEABI="arm64-v8a,armeabi-v7a,armeabi"' > /data/data/com.termux/files/home/.bashrc
[Magisk] dmenezes:
Just had a look, and while the particular phone my fingerprint is from *is* there, the fingerprint itself is *not* (that is, the version in the repo has a different Build ID and Incremental).

Interesting, and to me shows the superiority of getting one's own print: even if Google scans his repo tomorrow and bans everything there, the fingerprints you and I mined ourselves would still likely survive.
[Magisk] beeshyams:
That's not surprising

@TheFreeman193 himself said in one of his posts that the repo has only 5% of the publically available prints

Thanks again for your awesome tool #TheFreeman193 🙏
[Magisk] BROKEN1981:
GitHub - daboynb/PlayIntegrityNEXT

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

github.com

So I did a Google after taking a better look at that link. Wanted to see if anything else like it was out there. Saw a reddit post. People in that reddit link are mad. LoL

We are all screwed.
[Magisk] BROKEN1981:
Mine got banned after Chit released an Acer print. I was told he released a camera print. Mine was a smartphone. Bit of a coincidence that mine got banned.
[Magisk] dmenezes:
Thanks for pointing it out, I somehow missed it.
[Magisk] TheFreeman193:
The collection is, by intention, a subset of profiles based on widely available data. It represents roughly 5% of device profiles collected so that in the event the repository is crawled for a mass-block, users can still create their own pif.json files from the other 95%. 🙂
[Magisk] dimak2103:
Is it possible to somehow make a list of exceptions for applications from Play Integrity Fix? There is an application that in no way wants to work with it, it says that there is a root, although it works without Play Integrity Fix
[Magisk] osm0sis:
You could just comment out the changes in the module boot scripts until you figure out which the app dislikes. Test that theory to start by renaming the scripts and rebooting to disable them.
[Magisk] dimak2103:
Which file should I make changes to?
[Magisk] Homeboy76:
It is possible, but it also would be time consuming. I don't think XDA members are willing or able to invest that much time creating a list of exceptions for applications from Play Integrity Fix that they do not use.

"...There is an application that in no way wants to work with it, it says that there is a root, although it works without Play Integrity Fix"

What application is that?
[Magisk] dimak2103:
Приложения в Google Play – Swoo: цифровой кошелек

Ваше приложение для удобного шопинга и хранения документов. Просто магия!

play.google.com

or

Swoo: цифровой кошелек - 4PDA

Swoo: цифровой кошелек, Приложение для бесконтактной оплаты смартфоном

4pda.to

I would make changes just for myself, but I doubt that somewhere you can just enter the package name)

On some older versions of Play Integrity Fix (for example 14.1), it was partially possible to pass the verification in the application, but not completely, only what happens when the application starts. And it works not just like that, but by manipulating application versions (since the application has introduced additional verification in new versions)
[Magisk] stefaca:
Hi, I need some help/check. I'm using Poco F3 with PixelExperience. Magisk is installed, Zygisk is enabled. Play Integrity Fix is added as module but Google Wallet is still not working.

Should I do anything else?
[Magisk] TheRomRooster:
did you provide a PIF?
[Magisk] stefaca:
Can you, please, help me with that? What does it mean? Sorry, I'm new in this problem.
[Magisk] dimak2103:
It works with shamiko, but doesn't work with Zygisk
[Magisk] trevtdogg:
maybe start here: https://xdaforums.com/t/how-to-sear...scussion-for-complete-noobs-from-one.4645816/
[Magisk] Vision:
You must found your own Fingerprint and write the info inside in the /data/adb/pif.json between in the " "

View attachment 6048232
[Magisk] Homeboy76:
Have you tried using @osm0sis Play Integrity Fork?
[Magisk] dimak2103:
Yes, and also PlayIntegrityNext. Even if I pass the play Integrity and safety net checks, the problem remains. Also some people said that it works with KernelSU. I tried a clean install of the firmware, and it worked without a single module, but not with Play Integrity Fix

GitHub - daboynb/PlayIntegrityNEXT

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

github.com
[Magisk] xcl1pse:
There, I remove shamiko, delete swoo data and I can still login