yashsingh1/xdaforums huggingface dataset:
[Magisk] sawdoctor:
I tried doing a Google search for build prop dumps and you know what i found a repository with Android firmware dumps. From there just pick the device you want and download the build prop for it. Then try using pixelflasher to edit the json file.

Finding build props and editing the json files is simple . What isn't as simple as finding a working fingerprint and obviously we can't share those
[Magisk] Claus….:
I saw one, let me check 50 last pages and see, if I understand u correctly.
[Magisk] GROOVYJOSHCLARK:
Without it, it fails, with it, I pass so I don't have any issues and am FULLY Play Certified with passing BOTH integrity checks and have bank apps, Hulu in Play, Netflix, etc, so do you what you want, but I work and FULLY ROOT'd!

No offense taken but I'd test using it seeing as it works for me but others have issues without using it properly.

I'm not sure how anyone can say it's unnecessary when they're not passing without it, while I am. I AM on an official pixel 6 pro device so maybe that's why I need, IDK but I'm good to go!! If it would help you or anyone, I can make a quick screen record video showing it's all good with it, then disable and reboot and it fails everything miserably without props. Remember to setup props configured using option 1 and 2 only (set to raven / pixel 6 pro). I'll enable and reboot and show all works again in one recorded video.

Let me know

View attachment 6039758
[Magisk] mumuli:
Yea i know that fingerprint cant share. I finally found that dump site, my firewall blocking all russian sites, thats why i even cant open that page first. But that is public site, i dont know how tard ppl here is. That site can share here, if google wanna block that, they already do that. Same thing if here someone says, "i cant share facebook page, it possible if google found and block that, im scary". Again, that page is public, matter what...
[Magisk] sawdoctor:
I found a gitlab link with android firmware dumps which is safe
[Magisk] mumuli:
That same site. I have set unifi firewall, block all russian in and out. When i open out, that gitlab url open
[Magisk] maxmax0:
Magisk HideProps is definitely not necessary for me - and as I understand also for most others. Using Pixel 8 Pro, just using PIF 14, passing 2/3 checks and wallet works.

@dmenezes
[Magisk] zgfg:
Not that's just not necessary but post-fa-data.sh script in the PIF module

HOWEVER, by manually unpacking the MHPC installation zip (or from its installation folder) you can take a list with few hundreds of prints for spoofing.

Ofc, most will not work but by following the other instructions from this thread, testing can be limited to the smaller number of more promising

Instead of googling around, downloading firmwares

It just needs to understand the table in the MHPC and how to parse values for your pif.json files to test from that - but hints were also posted here

And that parsing can be automated...

Then the trick with automated copying, killall and pause

One hand hitting Enter on PC, the other hitting TBChecker Run Play Integrity
[Magisk] Bladius:
In version 14.0 MEETS DEVICE INTEGRITY fails
[Magisk] maxmax0:
For anybody who either already gave up on this, or is expecting his fingerprint to stop working any moment (raises hand), I have created a thread to discuss our NFC payment options in the post-google-wallet world...

Please join in with your ideas/experiences, or bookmark for later when your fingerprint stops working

😅

Android NFC Payment Options & NFC Wearables (without Wallet/Pay)

Hi all! G is currently cracking down on Wallet users utilizing rooted/modded phones. A huge number people are currently having major issues getting wallet to work, and the outlook is quite negative right now, I fully expect to lose my wallet...

xdaforums.com
[Magisk] Bonoboo:
Obvious idea: if Google presumably checks some additional props (now for mass fingerprints only?) maybe just spoof for DroidGuard whole build.prop from suitable device?

"My ID? Here you are, read it all. See, I'm Nexus 6P, no BS"

There is left a lot time for enforcing hardware attestation (too much legacy devices) and I think it's possible to abuse basic attestation with stable result. Hope only on great devs and their passion.
[Magisk] makeyourself:
IIRC some of these props oddly do not work (i.e. PI fails) if only spoofed for Droidguard, which is why some props are set system-wide with service.sh. Although to be honest I remember that in the days of MagiskHide Props Config when all props were set system-wide this never caused any issues for me. Just on certain devices it breaks some stuff, apparently.
[Magisk] straightcore:
Incredibly :rolleyes: a bug in the Matrix?
[Magisk] ho0o0o11111:
Lucky me!!

I tried two fingerprints and the second one passes!!

A14, pixel 6 pro and pixel 7 pro, both are fine now.

I did spend more than a hour to read through recent 10 pages and instruction.

Thanks for the developers and the community here.
[Magisk] maxmax0:
Lucky Man! You should play the lottery! 😄
[Magisk] ELAD098:
Thanks, but I couldn't figure out how to do it I'll wait for a simpler fix I have OnePlus 6T Pixelexperience 13
[Magisk] zgfg:
Yes, nothing new

You need to figure out what's you HOMEWORK to make it passing

Toms of posts here about
[Magisk] tom1807:
Using a Pixel 6, A14, November update.

Of course, Wallet tells me that the device fails to meet the security check (or something like that)

Used the build.prop from my device, added to custom.pif, but still fails after a while.

Also TB Checker tells me, that I only pass Basic Integrity.

I am assuming because "DEVICE" : "generic",.

That's for now not so concerning.

What's more concerning is, if I use any other build.prop my developer options are gone, which means Developer Options are enabled, but I cannot access them anymore.

Which in return, lets my banking app complain, that USB debugging is still enabled, so I cannot use my banking app.

As soon I use the original build.prop, everything is fine.

Build Props I used.

Google A14 release from October - No developer options

An Asus build Prob - no developer options

Another build.prop from a device I never heard about - No developer Options

Google A14 release from November - Developer options are accessible

Needless to say, that all pass only Basic Integrity, Device Integrity fails

That's a vicious circle.

All modifications were done with Pixelflasher 6.3.1.0

I haven't seen anyone reporting this, so I am not ruling out, that the problem sits 60cm away from the notebook or one of the modules installed cause the problem.

View attachment 6039777

Cheers

Tom
[Magisk] PandarianFury:
Managed to get Basic Integrity and Device Integrity through using this program:

🔧 [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

All you need to do is find a build.img file from another device, online. Preferably an old android version.

Question now is, will Google Wallet work?

PS. Thanks for everyone involved in this.
[Magisk] Nicknoxx:
I've got the system.img file out of a ROM I think will work - can anyone tell me how to exctract the build.prop from it on a windows PC?

Thanks
[Magisk] SuperMaximus:
It's strange that after PlayIntegrity Fix v.14 with correct pif.json that allows to pass both Device & Basic Integrity the "naughty" banking app stopped working (seems to detect root again...). Before v.14 and when Google didn't use that aggressive fingerprint banning it worked like a charm. Besides, after clearing all cache and data of Google Play & Google Play Services I cannot see all location services that I used to have before the fingerprint spoofing. Can all these things be interconnected?

P.S. Using 26401 Magisk Delta with MagiskHide (Kitsune Mask)
[Magisk] tom1807:
I used he program ext2explore.

Cheers

Tom
[Magisk] straightcore:
7zip
[Magisk] PandarianFury:
Just to summarise, because this whole process is less complicated than it seems.

Correct me if I am wrong, but it seems that google is banning fingerprints of rooted phones, so we need to find fingerprints of an unrooted phone, and "spoof" it on ours.

1. Download PixelFlasher here.

2. Find a build.prop file from an older device (2020 and earlier). You can do this by searching google for the actual file, or extracting it from an existing phone, or getting it from an original ROM file. I found one online.

3. Follow the steps in the PixelFlasher thread linked above. Install android platform tools if you dont have it already.

It took me like 3 hours to figure this out. The trick is just to find a build.prop file that is valid.
[Magisk] xSnowLeopardx:
Went to search for A8 OTAs, got a random one, payload dumper, 7Zip, extracted build.prop, and it was the first one I did today = success. It's that easy.

Edit: now 2nd OTA, 2nd success.
[Magisk] straightcore:
It doesn't work that way, I have two same phones, one is rooted, the other is not.

I probably wouldn't have to deal with anything :LOL:
[Magisk] stereo007:
I have now finally found an fp that works. What happens if they are all blocked one by one? Will I still be able to use a rooted phone in the future?
[Magisk] DissCent:
I keep having issues finding a valid fingerprint. So far I encounter the following problems with most devices:

- system/build.prop doesn't contain a fingerprint at all

- system/build.prop is newer than March 2018 and requires vendor/build.prop, but this file isn't present (using that dump site everyone is talking about)

As far as I understand, the devices must be at least upgraded to Android 8 and must not have Android 9+ on release, but none of these that I've found have been working :/

Any more hints for finding a good fingerprint?

EDIT: lol, just after finishing this post I found a working fingerprint. So what I can share is that fingerprints for Xiaomi devices are generally not working, at least not those 20 I tried.
[Magisk] Nightshadow931:
A million dollar question
[Magisk] ipilcher:
Sure, but each one is a multi-hour process of figuring out where a ROM can be downloaded, figuring out what tools are needed to extract it, figuring out what format the filesystem images are in, figuring out how to process those, etc.

It's definitely doable, but it's not fast or easy. I spent 5 or 6 hours on this yesterday, and I only managed to successfully extract the build.prop files from 2 or 3 ROMs.
[Magisk] fkofilee:
I managed to get this working after attempt 2 - The 1st one - i couldnt extract the firmware for the relevant model. It was about the time Oneplus changed the method of updates OP5T to OP6.

Luckily i found a really obscuren vendor and model that fit right in. Good guide by Osmosis etc - All working :) Lets see what happens and how long it lasts.
[Magisk] dmenezes:
Mine's still working:

View attachment 6039820

But it's been only 20h40m45s (yes, I'm counting) so it's still too early.

I will start breathing easier when 72h have come and gone and it's still working.
[Magisk] xcl1pse:
Already two weeks. I'm using the one I got from searching the fp for PIF 13.1 and still working...
[Magisk] xSnowLeopardx:
Almost a day for the first one I found, still working.
[Magisk] chris.p.bacon_1:
I just got a working fp, when I test integrity in play store, I get Meets basic and device, however tried to pay online via Google Pay, and Revolut declined my transaction
[Magisk] Li2th:
Good afternoon, I have the following problem.

redmi note 9 pro with google pixel 13 android firmware, the module is installed, the check of play services and safetynet is passed, but contactless payments still do not work, I tried the method you mentioned, but it did not help, maybe someone knows a solution to this problem?
[Magisk] xSnowLeopardx:
Clear cache + data for GWallet (or the app you were using) maybe.
[Magisk] chiteroman:
View attachment 6039834

v14.1 will be incredible 🤭
[Magisk] gerard_f:
Got my working fingerprint after second try :)
[Magisk] zeus7777777:
If I check the integrity through play store and the result's fingerprint is still ROM's original one instead of the custom one I modified in /data/adb/pif.json, something gets wrong, right?
[Magisk] Li2th:
i do this, but still not work. so i try again, mb u hace right
[Magisk] gerard_f:
Google play services has a server side cache, you need to wait until expires (or clear datas and caches, which I do not recommend at all).
[Magisk] dmenezes:
No problem, mate.

It seems there are multiple factors at play (pun not intended) here, and different people are getting different results.

Eg, for me force-stopping Google Play Store/Services is not enough to refresh them, and I can't kill the ...unstable process as there's nothing with that name running on my phone -- I have to reboot; meanwhile, other people are having success without rebooting, and can indeed kill said process.

Whatever works, I guess -- I'm just happy I've found a workflow that works for me, and even better, I have a working fingerprint yet.
[Magisk] dmenezes:
I don't use Google Pay or Wallet, so I can't help you here.

But considering it was your credit card company that declined the payment, it might not have anything to do with Play Integrity whatsoever -- I would try contacting Revolut and asking them why your transaction got declined.
[Magisk] xSnowLeopardx:
Can't wait! 😄
[Magisk] dmenezes:
Thanks for tagging me, and glad to hear yours is also working without Magisk HideProps Config. And I agree, it does seem to be the case of most people here.
[Magisk] xSnowLeopardx:
Clearing data+cache should not be harmful for GPS, right? However, it really is annoying if it's done on GSF (which is not needed at all, but was recommended by people a long time ago).
[Magisk] Li2th:
it seems that google decided to leave us without payment, just deleted all this googlepay and the program itself, after installing all the cards were in place, it seems that now this information will be permanently on their servers and not locally or temporarily
[Magisk] dmenezes:
IIUIC, I think it could just accelerate Google's fingerprint bananaing and consequent exhaustion.

I do hope I'm wrong, tho.
[Magisk] gerard_f:
I read some people had problems with notifications after cleared the gplayservices data. And few years ago, if I remember correctly, some google engineer talk about that and said it's not recommended because can have unpredictable consequences.

While I'm not 100% sure about that, I prefer to wait some hours to get the cache expired.
[Magisk] jurluk:
I've fixed one error in script, thanks @straightcore. Updated script is at the bottom.

Since there were mentioned in this thread some sites where you can find build.prop files (I won't mention them here), you can use this script to generate pif.json without too much hassle.

In first post I gave last example where you can use any file.

# expects build.prop in the same folder
./pifgen.sh

# custom path
./pifgen.sh /some/path/build.prop

# custom file
./pifgen.sh /some/path/example.txt

I didn't want to explicitly mention that, but someone experienced could see the potential.

I've uploaded to pastebin one build.prop example. You can change that url to any you want and run the following commands:

curl -Ss "https://pastebin.com/raw/W5sWi7rH" | tr -d '\r' > output.txt
./pifgen.sh output.txt
[Magisk] ipilcher:
A couple of questions ...

For the various dump sites, how do you correlate the model of a device to its "name" (which is often used to identify it on the sites)? By "name," I mean OnePlus One -> bacon, Motorola Moto X4 -> payton, Samsung Galaxy S9 -> starlte, etc. Is there a list of these somewhere?

Also, I haven't found a working fingerprint yet (obviously), but I did find one that passed the SafetyNet CTS profile match, where the others don't. Does that indicate anything?

Thanks!
[Magisk] frank93:
hadn’t noticed this, but can confirm (anecdotally, i mean, for me only - same here). spoofing the fingerprint somehow seems to make developer options "invisible" in settings. weird.
[Magisk] jurluk:
Just google "<device> codename"?
[Magisk] xSnowLeopardx:
You remember it incorrectly, since it was about GSF (Google Services Framework). You can delete the data of GPS (Google Play Services) as many times as you want, but if you touch GSF, then you will have notification problems.

How do I know this? Experience + research.
[Magisk] xSnowLeopardx:
If you have 1 of the 2 passing, then it's either an inproper build.props or it's a newer device. With, for example, 0 of the 2 passing, it means that the build.props is severely inproper and the method of finding/editing is incorrect usually as well.
[Magisk] Vision:
New exciting Feature ? WE waiting for this
[Magisk] Claus….:
For me this solution seems very short term and as a dead-end. Btw, tried 20 phones, none fp worked. Anyone that has other ideas on how to bypass?
[Magisk] xSnowLeopardx:
Other ideas? This is the current one we have...

Either you wait for what @chiteroman will tell us in 14.1 or you keep on searching. I searched less than 20 and have 7 working ones.
[Magisk] straightcore:
What can I add, today I have about 30 of them tested and work :D
[Magisk] downhere:
That's the proper display. Your spoofed FP is just "under the hood" and not shown.

You just have to check there if you get MEETS_BASIC_INTEGRITY and MEETS_DEVICE_INTEGRITY.
[Magisk] Gilg@mesh:
if someone who found many would like to share one, please PM, I'm not G*****, check my history haha, thanks :)
[Magisk] cmstlist:
I too would appreciate any fingerprint PM, as it seems the Telegram app won't let me in, so I can't get at the discussion group.
[Magisk] G5-User7080:
I heard people say I have to clear data from play services, but is that safe to do?

I don't want it to log me out of my google account and reset my settings, so I'd have to sign back in and spend the next 30 minutes going through all the google settings again...

what about play store? do I need to reset it's data as well?

also, I took a fp from my old oreo devices' firmware that I still had lying around, tho if taking any firmware works, why can't we use our current devices' firmware?
[Magisk] xSnowLeopardx:
Most I have had to do was:

- Change updating to not automatically

That's it. If I miss something besides this, correct me, but deleting data for Play Store and GPS is not something scary or destructive.
[Magisk] Mthw:
Thank you @badabing2003 for Pixel Flasher, you just made my life so much easier. I just found a working fingerprint and hopefully payments will work too next time I use them.
[Magisk] makeyourself:
Think this is probably every device out there that Play Services will accept...

https://storage.googleapis.com/play_public/supported_devices.html

The "name" you speak of (e.g. bacon) is listed in the "Device" column, what the phone is marketed as (e.g. OnePlus One) is under "Retail Branding" and "Marketing Name".
[Magisk] PoorMalone:
Working fingerprint, anyone? 🙃
[Magisk] xSnowLeopardx:
Search yourself. This thread has given us all the tools to do so.
[Magisk] redcodefsu:
I have a Samsung Note Pro 12.2 SM-P900 and have the pif 14.0 module installed. I'm on Android 10. It still won't pass CTS profile match. Any suggestions?
[Magisk] xSnowLeopardx:
You need to fill the .json of pif with a working fingerprint of an older device. There are tips in the OP of this thread.
[Magisk] fedeoliv89:
Just a tip that was helpful for me: remember to start your json file with a { and close it with a }.

Double check it if you are generating your json fingerpring through a script.
[Magisk] zgfg:
Playstore is not DroudGuard

Playstore displays what it sees, for PI it calls DroidGuard as all other apps, and droidGuard sees spoofed prints

TBChecker will also show you real device/ROM, and for the dame reason

Answered already dozen of times last days
[Magisk] D€INOS:
Why test 30, you just increased the probability of G banning them through missmatch 😡
[Magisk] straightcore:
advanced paranoia?
[Magisk] okotzak:
Sorry but i didn't understand.

My google pay two days now stop working .

Last time i had this problem i installed last update of play integrity fix and the problem was solved.

Now i installed pif ver14 but the problem is still there.

What steps do i have to do to fix this ?
[Magisk] xSnowLeopardx:
Read first post in this thread. You need to edit the .json file in data/adb to an older device's fingerprint.
[Magisk] D€INOS:
No just stating the obvious, mentality like this is bad. What the point of checking 30?! 🤬
[Magisk] arda99:
Please stop some BS....G is definitely not using mismatch for now, it makes no sense for them to cross check some fingerprints not others. It's either all or none.
[Magisk] okotzak:
And how can i do this if i have no other phone ?
[Magisk] Claus….:
Amazing, this is why I can’t find any. You took them all :) please do not share them in public. So they don’t get blocked.
[Magisk] straightcore:
I really don't feel like explaining the reasons, obviously you wouldn't understand them anyway.

Have a nice evening.
[Magisk] matrix200200:
Guys I need help.

After several attempts I have made I am getting now

OR-TAPSH-08 error which means my account has been flagged

Any ideas?
[Magisk] D€INOS:
Because you have no explanation except ignorance.

If you dont think that was a bad thing then I guess you won't mind if I post and attach a zip of the 76 build props I dl within the proper Android versions? I bet most if not all of the 30 prints are included in those 76 props. Because according to you there is no issues, G won't banned those anyway. 😡
[Magisk] flobo09:
First phone fingertip i tried did not work, second did.

Thank you @osm0sis for the forked fix, very clear explanation of the situation & instructions !
[Magisk] straightcore:
You forgot to take your medication sir.

"How do you know you have 76 working?" :D :D
[Magisk] D€INOS:
I don't, because I see the difference between collecting and activating fingerprints. And I don't want to destroy things, unlike you.

And you didn't answer my question, would it be okay with you if I attach those prints here in a zip?
[Magisk] straightcore:
Never mind, go for it ;)
[Magisk] D€INOS:
That speaks volumes about what kind of a person you are. 🙄
[Magisk] xSnowLeopardx:
Why are you even replying to him lmao
[Magisk] straightcore:
Thanks,

Yes, more demons like me!!!
[Magisk] simpleatom7:
Man u r great man. Bcz of u i got yono running!!!!! I'm so thankful to u.. Can't thank u enough!
[Magisk] simpleatom7:
At last it did with shamiko, Hide my app(HMA), integrity fix module, along with enforce deny list not enabled just select google and google play services (ist & 8th process).

Dammm guys thanks :)
[Magisk] simpleatom7:
Happened with me also. Remove all safety net modules, then reinstall this latest 7.something update & hide magisk app. Clear data of google play store, check if it's certified & reboot.
[Magisk] simpleatom7:
Yep! Just realised u don't need strong integrity fix to make bank apps run, u need HMA & shamiko
[Magisk] simpleatom7:
Yes using HMA & Shamiko
[Magisk] simpleatom7:
Yep did that. Thanks bro. We need more people like u in the community!
[Magisk] simpleatom7:
I got yono & CIN bank running however "Madhaar" app is not working & force closing like what happened earlier to yono. I did add it in deny list & from HMA however not working. Can u test this🙏
[Magisk] intel_core_i7:
"Replaced" is quite incorrect, it's literally MagiskHide but renamed to match the function's actual purpose. "Renamed" is the word you're looking for.
[Magisk] simpleatom7:
Yeah but finally Bank app yono worked however "Madhaar" Doesn't work it crashes whenever I open it. Can u check what's happening? Here is the link to the app.
[Magisk] pndwal:
Moved answer here as may be more appropriate for General Magisk audience:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-88905745

🤠 PW