yashsingh1/xdaforums huggingface dataset:
[Magisk] sawdoctor:
I believe it's because the file is too large for Magisk manager to download so you need to manually grab it from GitHub
[Magisk] majorfigjam:
Maybe, if it is suitable. I got my first one that way. If it's not, then read the first post, and go from there.

If we knew how exactly Google did it, we wouldn't all be here! We know there is a list of approved devices, so we can assume that there is also a table of devices that can't be hardware enforced, that fall back to matching fingerprints, with flags for dates etc. Maybe more, only Google knows for sure.
[Magisk] zgfg:
Previous apk were about 11 MB, v26402 Canary apk is now 28 MB.

I thought first it's debug build but Debug apk is even larger, 39 MB

I don't get this excuse (seeing everywhere) that apk is too big for Magisk app to download - no matter how big, upgrade should have been tested and fixed that it could download that big file😁

I think that Debug (chose instead of Canary) was always big but its automatic upgrade nevertheless worked. Also, ROM Updaters download and save OTA zips of several GB
[Magisk] dvhttn:
As I said, I used Magisk to download the update with no problems ...... 🤨
[Magisk] osm0sis:
Maybe it only fails when the Magisk app is hidden. Either way, it is a widespread problem, and they'll get to it eventually. The oversized APK is already fixed upstream.
[Magisk] zgfg:
Nope, I never use Hide Magisk app

Click on Update button and it will spin forever - see the screenshot

So I wrote this post, took the screenshots, edited, attached and it Download still spins
[Magisk] osm0sis:
I did say maybe. 😉
[Magisk] EuK_V:
What is the reason that a certain pif file is working on one device and not on another? I have three phones all of them are with los 20, and 18.1 and some pif files are working on one of them, some on two, some on all three..
[Magisk] magillos:
Same problem here with stock miui. I don't think uiautomator works as expected which can be seen in pixelflasher with debug option checked.
[Magisk] osm0sis:
What gets tested seems to vary based on underlying OS version or something, so some part of your PIF might be technically incorrect but only getting caught some places.

What module are you using? This could be where VNDK or other things come into it too.
[Magisk] badabing2003:
It's the cdn settings that need to be updated.
[Magisk] hassanhassan:
do i have to clear cache and reboot even if i use pixelflasher?
[Magisk] EuK_V:
I use 14.0, so no vdnk in my pifs
[Magisk] Vision:
Nice, this Bootloader Spoofer zygisk module is like your BootloaderSpooferV1.2.apk do the same but in zygisk module ? and when you release this module ?
[Magisk] Vision:
My old phone say this but in bootloader say unknown, and you say me this

View attachment 6042304

View attachment 6042295
[Magisk] Nekromantik:
I am using version 14 on pixel 7 pro and adding the pif.json with info from OTA file but I only pass basic integrity

cleared cache and storage on playtore and cache on play services
[Magisk] zgfg:
There could be diff factors but make sure that you test in parallel by using same module, same version - there are slight differences

Then, what is original FIRST_API_LEVEL.of your device

Also, that you fill all right properties in JSON - to have full control of what will be spoofed

Eg, PIF v14.0 will force hardcoded FIRST_API_LEVEL = 23 if missing in JSON file

PIFork will leave your phone's FIRST_API_LEVEL if missing in JSON (on one of your phone's your API could be eg 25, on the other 31), so put 23 to JSON if you want behavior as in PIF v14

Always inspect logcat to see which values were read/used from JSON and what the module will force hardcoded (API 23 in PIF v14) if missing in your JSON
[Magisk] zgfg:
Yeah, so devs should have reconfigured the settings on JSDeliver since Magisk download goes through

I didn't check if an issue was opened on Magisk GitHub but the problem must already be known and discussed elsewhere.

It's trivially reproducible (and easy to fix), no need for submitting Magisk logs etc

Nevertheless, it's still strange that apk size has been enlarged almost 3x times. Cannot be that code has grown dramatically. Either some new libraries are used or something is not compiled/linked with the same release settings as usually
[Magisk] xSnowLeopardx:
Yup. A9 and A10 in there as well, but also A7.
[Magisk] osm0sis:
Already fixed upstream, as I mentioned:

Fix native symbol strips · topjohnwu/Magisk@d47e70c

`ndkVersion` is also needed by app for striping native symbols. Set it in `setupCommon` instead.

github.com

Judging by the Actions CI build APK sizes, it was a build regression introduced by the new AGP:

Upgrade AGP · topjohnwu/Magisk@4e99997

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Magisk] Iridule:
I was able to update to 26402 in app when it was first released.
[Magisk] badabing2003:
Though not released yet on canary channel.
[Magisk] osm0sis:
Yes, upstream. 😉😛
[Magisk] pndwal:
If you have PI DEVICE_INTEGRITY and Play Protect Device is certified, Leo's Fortune behaves this way, but not Netflix...

I just uninstalled Netflix with DEVICE_INTEGRITY, BASIC_INTEGRITY and Play Protect Device certification failing, and checked apps... Netflix still appears as I expected... Leo's Fortune appears but gives 'your device doesn't meet requirements for this app'...

Fixed DEVICE_INTEGRITY and Play Protect Device certification and then LF will also install...

Nb. Play Store uses various criteria for app availability... When we first got PI DEVICE_INTEGRITY, while Google Pay was quick to migrate to the API, Google left Play Protect certification using S/N for many months so despite having S/N pass and Device is certified in Play store, many could no longer see G Pay or bank app in Play Store until they got new PI DEVICE_INTEGRITY fix (at least for devices requiring the fingerprint mismatch for HARDWARE_BACKED evaluationType enforcement bypassing at that time, which didn't affect S/N)... Some apps may be required to have BASIC_INTEGRITY, even STRONG_INTEGRITY, and others nothing... As Play Protect device certification is simply a reflection of DEVICE_INTEGRITY verdict (now), it's not a consistent indicator for apps availability in Store... I believe Devs set their criteria for device requirements in their Play Console developer accounts...

Nb. To reset Play Protect's cached integrity status and other measurements it may use for device compliance for app availability, users may need to clear Google Play Protect Service data in addition to Google Pay Services and Google Play Store in late devices...

Netflix is now apparently restricted in Play Store on the basis of Widevine DRM certification (L1 security is required for HD streaming/decoding in TEE OS).... It used to be SafetyNet dependant but policy changed with 5.0. Netflix said at the time:

Nb. Widevine certification is affected differently by PI attestations (not always independent) depending on OEM implementation... Generally Xiaomi and many other devices retain L1 certification regardless of DEVICE_INTEGRITY, some (OnePlus, Realme etc) need passing PI deviceIntegrity to pass L1 certification or even loose L1 until re-locked... As long as they have L1 Widevine most users can stream HD but Netflix still generally works fine W/ SD on L3 if L1 is absent...

You can use DRM Info app to check this device compliance spec...👀
[Magisk] peikojose:
Is this one ?

Release v1.2 · chiteroman/BootloaderSpoofer

Spoof locked bootloader on local attestations. Contribute to chiteroman/BootloaderSpoofer development by creating an account on GitHub.

github.com
[Magisk] trevtdogg:
i just wanted to post and say a huge thank you to everyone working on this.

up until now i had been using the generic shared pif fingerprints included by @chiteroman in their updates, and the thought of working out how to find my own custom print seemed too daunting - even after reading the great guide by @osm0sis which still seemed to go over my head a little.

but after 4 hours of trying i finally got a working fingerprint using the @osm0sis fork! both basic and device integrity passing.

for anyone else struggling to find their own custom print or not knowing where to start, what worked for me was searching for any build.prop files at all (or even just the text contents of the build.prop file) and first checking the api/sdk level. i'd only proceed to test it if it was between 23 and 27.

hopefully this print will last me a while before needing to be updated :)

has anyone had their custom fingerprint stop working yet?
[Magisk] xSnowLeopardx:
8 days in, no problems so far.
[Magisk] Vision:
This is a apk file, Spoof locked bootloader on local attestations the, this Bootloader Spoofer zygisk module like say is zygisk module flash it in Magisk but i think @chiteroman not release it yet
[Magisk] badabing2003:
See this post.

As for VNDK_VERSION

What version of the module are you using?

@osm0sis fork ignores it, so it shouldn't matter for that.

I don't know how the version of the module you're using handles that property when the value is empty string.

All PF is doing is extracting whatever values that are available from the property files you fed, nothing more nothing less, it's up to you to play with the values and combination of the properties to get a working print.

See this post as well, I can also tell you that uiautomator on some devices don't work well, I have one such device, I really can't do much about it, it's a bug of uiautomator itself.
[Magisk] rogers11:
Hello, I'm using @osm0sis fork. And the "empty" string really caused the described problems (latest Pixel Flasher on latest Debian with adb 34.0.5 - Pixel 7a with LOS 20).
[Magisk] Wolfcity:
1st one I found of some is still working well with Osm0sis fork.
[Magisk] magillos:
Pixelflasher works great otherwise and I was able to find 30 FPs with it (will I ever need them tho with the first finger print found still working?). It just takes a few seconds more to tap on the phone so it's all good.
[Magisk] badabing2003:
I don't know what to tell you, @osm0sis fork ignores that, unless you set the value to null it is totally irrelevant with that module, and I'm sure he can confirm that.

Are you editing the pif, are you sure you have no typos? additional comma or a missing comma?

I can tell you that I set that in empty string with osm0sis fork and it works just fine.

What device are you on?
[Magisk] simpleatom7:
Did try it again & got it fixed.
[Magisk] simpleatom7:
Even those custom prints are getting banned every day I guess?
[Magisk] dmenezes:
Please PLEASE delete that link ASAP
[Magisk] majorfigjam:
Not clear what you are asking - getting ' what' every day.

Getting used - mine definitely is.

Getting declined - no one has yet indicated that there's a problem.
[Magisk] Nekromantik:
anyone able to help?

i only baas basic integrity not device integrity with v14 reset props

running pixel 7 pro and I added p7 props into pif.json but still wallet does not work and dont pass device integrity
[Magisk] Nergal di Cuthah:
Don't use the same fp of your device, find a different fingerprint from the sdk range given in @osm0sis guide. By using a p7 fingerprint your telling pi to do a hardware backed result
[Magisk] D€INOS:
You mean this one?
[Magisk] Nergal di Cuthah:
Please delete you're going to get all fp banned
[Magisk] badabing2003:
That cat has been out of the bag a long time now.
[Magisk] D€INOS:
Stop posting you are leading Google to this thread 😳

Edit: you are posting again, please stop, Google is watching even more now. 😳
[Magisk] Nergal di Cuthah:
Yawn
[Magisk] majorfigjam:
Do you seriously think that Google doesn't know how to use their own search tool?
[Magisk] Nergal di Cuthah:
I hadn't seen it posted in this thread (and kept) until today.

Oh well, i guess I'll still pull from that repo looking for a fp that works.
[Magisk] xSnowLeopardx:
It's "reporting a user in here who ruins a lot of things for others" time, Fa la la la la, la la la la.
[Magisk] sawdoctor:
It's pretty much the 1st result in Google so I'm certain the play integrity team have already seen it. Let's face it thier smarter than most of us and can easily ban all fingerprints with or without any help from us
[Magisk] xSnowLeopardx:
None of my fingerprints are banned yet and sure, I used that site as well. But now that it's also posted here, it doesn't help either. Oh well, glad I have so many.

More users doing the same sh*t as KrazyKlown is not what we need?
[Magisk] Nergal di Cuthah:
I'm still not convinced there's a pi team. Much more likely a bot.

Not thinking google can find thinking too many people using same fp.

Also "1st result in google" completely misunderstands google search's bubbling. It's your first result (probably due to visiting), not everyone's.
[Magisk] Nekromantik:
thanks will try
[Magisk] Iridule:
If worse comes to worse you could buy a cheap android from Walmart get the build props and return it.
[Magisk] BIGWORM:
Exactly this. Absolutely no need for the back and forth. Let's keep it friendly in here. Thank you.
[Magisk] maxmax0:
Actually no, this would not help you at all, as you need devices from a certain period in time.
[Magisk] Iridule:
I'm not so sure what periods of time though I've got working prints from 2022.
[Magisk] dmenezes:
Hi everyone, spent most of the week away from that thread (real life -- what a concept! 🤣) and just came back to report my own self-mined fingerprint keeps working without any issues:

View attachment 6042433

That's 8 days and a few hours now, yay!

Meantime, how many fingerprints has @chiteroman burned through yet? 😞

(seriously, not a rethoric question -- would like to know and don't have the time nor the heart to read through the 100+pages that have been posted to this thread in the meantime).

TIA!
[Magisk] Nergal di Cuthah:
14.2 is still going well so less burned than you'd think
[Magisk] dmenezes:
AFAIK, 14.2 downloads the fingerprint from @chiteroman's repo automatically, so it can have burned through many fingerprints already without releasing a new version.
[Magisk] Nekromantik:
when you edit pif.json and do a api check in play store, does the play store result show the spoofed device or your device?

i cant seem to find one that works
[Magisk] xSnowLeopardx:
Thanks for using your brains, I wholeheartedly agree.
[Magisk] xSnowLeopardx:
You see your own device.
[Magisk] dmenezes:
You and me both, my friend! Thanks for standing on the side of reason.
[Magisk] osm0sis:
I was able to reproduce that issue just now actually, it seems to be another edge case with the json parsing/handling only when any unsupported entry is specifically last in the list.

I'll look into it!

@badabing2003 I guess a workaround for cross-compatible files for now would be to have any potentially unsupported entries be in the middle? Or leave them commented out by default?
[Magisk] dmenezes:
Thank you very much for your continued efforts, @osm0sis! I'm still on 14.0 from upstream, but if/when I have to upgrade I will definitely move to yours, it's a pleasure having a developer who cares and listens! 👍👍👍
[Magisk] manjaroid:
I passed a couple new prints after removing that line.
[Magisk] mike.s:
Because you think Google doesn't know about it? Hint: you can find it by searching with Google. LOL.
[Magisk] Iridule:
Was curious and tried to use logcat to see the print for 14.2 but it wouldn't reveal it? wonder why
[Magisk] Nergal di Cuthah:
This has already been settled by moderator asking all to stop the back and forth, please do not restir
[Magisk] majorfigjam:
So let's put this in perspective, and apply some reason or logic.

The list I have of Google approved devices has 41,412 different devices on it. Assume only 2% of those devices are usable, that's still 800 plus devices to work with. Many of those devices have multiple usable fingerprints, depending on the patch date and build number. Some US carriers have device specific builds - I won't link to it, but one of them helpfully lists out its multiple builds for each device, each security update, and all of them that I tried pass.

So, there are likely well over 5000 usable prints. Not all of them are on "that site" - mine for one is not. The site's existence has been well known for years - at least to anyone who previously looked into spoofing build.props over the years. Of course Google know that it exists, and keeping its existence "secret" only serves to hinder others still looking for that elusive working print.

The chances of Google spotting hundreds , maybe thousands, of identical old devices checking in from all over the world are high. The likely number of "real users" of those devices is tiny, so the risk of blocking a genuine user is low.

The chances of Google spotting your custom print from one location are minimal. Blocking a random print - which may still be in use by thousands of US GPay users on legacy devices - will not work out well for Google.

But when, and I mean when, Google decides to crack down on this fix, and check the actual hardware to the print, then we'll all have to find a new way of using our phones and watches.
[Magisk] Umgak:
I wrote a script to automatically dump props from an image. It's not ready to share (it's janky and has some hardcoded device-specific stuff) but it allowed me to quickly dump and test a total of 58 ROMs for a particular device.

Of them, a whopping 39 pass DEVICE, while only 19 were banned. I noticed that beta builds seem to have a much lower ban rate. Equal numbers of beta and stable builds were tested (29 of each) and only a single of the banned prints was a beta, while over 60% of stable builds were banned.

Worthwhile to expand your search if you haven't been looking in open beta program builds. And I guess I have 39 working prints now. Still haven't needed to actually switch after adopting one on the 1st.
[Magisk] Nergal di Cuthah:
I feel like, again, I've been called stupid lazy and ignorant, for not yet finding a fp that works (and not having the time to get one) and using 14.2 as a band aid.
[Magisk] dmenezes:
Thanks for the detailed, thoughtful post @majorfigjam.

That's an interesting number, and much much larger (by a couple of orders of magnitude) than what I'd expect.

Can you please share how you came to it?

Will hold on further comments until you do.

TIA!
[Magisk] dmenezes:
That was not my intention, and please notice that I didn't mention any names, much less yours. On the contrary, from your previous posts I think you're solidly on the intelligent/considerate camp, probably you just didn't had the leisure to spend the necessary time on this yet.
[Magisk] maxmax0:
OK, but I assume those are order phones that received an update last year? Not released 2022, right? Just so I understand you correctly.
[Magisk] Iridule:
I would assume so. There's some cheap phones at Walmart that are running older versions.
[Magisk] rogers11:
Thank you for looking at this. But why should the line be written at all if there is no associated value?
[Magisk] mkcs:
Can it be used on KernelSU without ZygiskNext? Zygisk would leave traces of tampering
[Magisk] majorfigjam:
Google "google play supported devices" . It's freely available as a list.
[Magisk] sawdoctor:
No one is calling you or anyone stupid or lazy and if you want help finding a fingerprint hit me up and I'll help you.

The point he was making is there's probably 100s maybe 1000s of users who just haven't even tried and haven't thought/don't care about the bigger picture. Yes Google can close this loophole anytime they want but it's still no reason to burn fingerprints willy nilly .

Xda is/was a place for people to come and learn and share ideas and knowledge but unfortunately it's become more and more a place for people to come and be spoonfed and get free stuff.
[Magisk] xSnowLeopardx:
Gonna be more productive in here:

Anyone who does not meet both integrities and wants some help,

Anyone who is stuck at whatever process and needs advice, and/or

Anyone who does not have a fingerprint working and does not know why

Reply and I/we will try to help.

I have 20 right now and just know that I will have a 21st within minutes. Just don't really need to go further, but since it is so easy, I want it to be easy for all of you guys - without giving out any site or prop immediately.
[Magisk] rseiler:
Has that actually been happening? Has anyone been keeping track, assuming the local print is even discoverable? I kind of doubt that it has, because wouldn't people have noticed it and/or needed to reboot for the new prints to take effect? It can't be so smooth a process that it wasn't even noticed here.
[Magisk] purgy:
Even with the guide, and all the tools, there's still a certain amount of luck involved in finding a working fp. Ofc you can narrow it down, but I found a few that "seemed" to meet all the requirements, but returned 0/3.

And I can totally see why a list of known to be no good / axed fps isn't a thing, but it does mean that there is a huge amount of duplicated effort going on...

All that's required is killing the gms unstable process, whether in fact that's what the mod does I'm not sure
[Magisk] Iridule:
I would think logcat | grep 'PIF' should reveal the print but I couldn't get it to work for 14.2 though it works on the fork
[Magisk] sawdoctor:
The latest none Dev version doesn't download from his GitHub it's "hardcoded" and can't easily be changed. So if/when the fingerprint gets burned in the none Dev version it will stop working until an update is released
[Magisk] Vision:
Yeah understand your point, I also learned a while ago, the basic knowledge and i try to learn more to can understand all this stuff
[Magisk] veloz46:
Good night. I have downloaded the dev1 version, I understand that I have to modify the pif.jason file inside with the information of the donor phone, is that right?

Thank you for your time and all the effort.
[Magisk] Badger50:
@chiteroman

Greetings. Would you please check your PM inbox for an important message. Thank you.

-Regards: Badger50
[Magisk] rseiler:
Release v14.2.1 · chiteroman/PlayIntegrityFix

OUTDATED, NOT WORKING. Improve code logic. Fix crash issues. Xiaomi.eu and EliteROMs auto remove inject app! Same fingerprint as v14.2

github.com

Improve code logic.

Fix crash issues.

Xiaomi.eu and EliteROMs auto remove inject app!

Same fingerprint as v14.2
[Magisk] asdxx:
I've had a strange but pleasant surprise with v14.2. I haven't attempted a custom FP ever, and not cleared cache or ran any terminal commands to prepare for new FP. Always been rooted with a custom rom, with Magisk with Shamiko and PIF (PIF since Google started playing games with PI). Google Wallet had been failing for many days with the dreaded "...security requirements" error because DEVICE INTEGRITY had been failing (only use a couple loose banking apps which have always worked and still do).

Flashed PIF 14.2 when it came out. Failed after flashing that but a day or so later, it started passing BASIC and DEVICE and Google Wallet started working for first time in many days and has been for a few days since. Wondering why?!
[Magisk] sawdoctor:
If you want to use the dev version you need to find your own fingerprint yes. There's plenty of guides for this check the op. If you are struggling then check back a few posts and a few of us have offered help
[Magisk] xantrk:
Is it resetprop only now? Resetprop version caused my photos to not show Pixel specific features on earlier builds (custom non-pixel fp)
[Magisk] xcl1pse:
It's normal version. No resetprop for now
[Magisk] wugga3:
Self explanatory?

Oh Google why this?
[Magisk] Compass Linux:
After almost 30+ pif.json's I've found one that is passing BASIC and DEVICE, combined with DEV-v2 now. 🥵

And I didn't change anything from my previous method either. I must've been extremely unlucky.

Compass.
[Magisk] Compass Linux:
I see a credit card number there (1234 5678 9012 3456). Will test! 💸

Compass.
[Magisk] wugga3:
Release v14.2.1 · chiteroman/PlayIntegrityFix

OUTDATED, NOT WORKING. Improve code logic. Fix crash issues. Xiaomi.eu and EliteROMs auto remove inject app! Same fingerprint as v14.2

github.com
[Magisk] Compass Linux:
I will when my current working PIF fails. Thanks for the tip!

Compass.