yashsingh1/xdaforums huggingface dataset:
[Magisk] HippoMan:
Literally hundreds of FP spoofs have been unearthed so far, but @chiteroman's efforts only end up getting one or two spoofs banana-ed every week. His are widely used by hundreds of people and are therefore easily noticeable by the Googlefrinchians.

Furthermore, it takes just one Googlefrinchian operative maybe 5 minutes once or twice a week to see which spoof is being used in the latest PIF release and to then get it banana-ed, thereby affecting those hundreds of PIF users.

The use of the unearthed spoofs is spread out among other users, and none of that spoofing causes any kind of flood that would be easily noticed by the Telephone Sanitizers. Nor do these other spoofs get publicized like the @chiteroman spoofs that are used in each new PIF release.

So, those of us who are using unpublicized spoofs that we have uncovered have a much greater chance of spoof longevity.
[Magisk] beeshyams:
In theory yes. I have also read about some devices (not sure if it one plus or Xiaomi) that don't

This may not be the definitive answer you want but unless you try it yourself, you can't be sure
[Magisk] dmenezes:
Amen to that, brother! 👍
[Magisk] vamteusz:
I installed this fix and everything worked correctly but I have an issue once a week or two weeks that my google wallet says the device doesn't meet requirements. how to fix that to have a working version without further surprises?
[Magisk] sawdoctor:
Find your own fingerprint from one of the guides instead of using the included one

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

Edit

ATM you have 3 options

1. Carry on as you are and every time a fingerprint gets banned (at least 1 a week) flash the update from chiteroman

2. Read the release notes and wiki in @chiteroman release section and use your own fingerprint

3. Unroot lock bootloader
[Magisk] Nekromantik:
i cant figure out why i cant pass device on the 14.4 fp

i installed it 1 hour after it came out and did not pass device.

my set up is as follows

pixel 7 pro stock rom

ksu

zygisknext

pif 14.4
[Magisk] HippoMan:
4. Keep your device modded and rooted, and don't use the device for contactless payments. I use a hardware wallet (made of leather) which contains plastic bank cards.
[Magisk] beeshyams:
I see on some Tg channel that 14.4 is banned but only a few reports
[Magisk] simplepinoi177:
decided to check out the main channel, just to see this...

there's someone that put up a fingerprint they found/tested....I'm curious how fast that ends up being banned -- if it's any faster or not than PIF as PIF updates...
[Magisk] switchem:
I'm really confused about how to find a fingerprint. All of the documentation says "you can find a stock rom from your favorite search engine". But what exactly am i even looking for? Are we downloading a 3+ GB file for every build.prop we want to try? I understand we can't publicize where to get these, but I'd really appreciate some help on what i'm even looking for. Maybe someone can share an example of a known bad ROM and/or website?

EDIT: Sorry, I missed a secion of simplepinoi177's great guide. Looks like they answered this. I'm reading it closely now.
[Magisk] switchem:
I installed yesterday and I can't pass even basic integrity. But I'm new to this, and am not sure if I'm even doing it right. If the FP is banned, should basic be failing?
[Magisk] beeshyams:
That one somebody put it up for testing and apparently doesn't work. That channel is is like a noisy crowded airport..hard to track...the one I was referring to (banned) is from the same channel
[Magisk] beeshyams:
That's the hardway, easy way is to search for android dumps
[Magisk] beeshyams:
I really don't know...
[Magisk] switchem:
Thanks. I just realized I missed a section of simplepinoi177's great guide. Looks like they answered this, so I'm reading it closely now.
[Magisk] ipilcher:
Add Marriott hotels to the (bizarre) list.

Is there a thread somewhere where these apps are tracked/discussed?
[Magisk] Tirofog:
Just to understand, is there any point trying different API levels if both device and basic integrity fail.. in other words is it best to just move on and find another print which at least passes basic?
[Magisk] osm0sis:
If Basic fails there's either something incorrect/missing from what you entered, or the device is too old (like old Nexus 6, etc.)

Check out my post in the simplepinoi177 help thread re: DEVICE_INITIAL_SDK_INT/FIRST_API_LEVEL and my preferred testing methods nowadays:

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] simplepinoi177:
Oh that's right! I did read that in some places! The whole dedicated thread to it....like only keeping with certain older versions and what not....dunno what Marriott's deal is; do they think rooting will somehow lead to opening doors?!?! I mean, that's true like-the-movies hacker shizz, I'm sure "root detecting" would be the least of their worries...
[Magisk] dmenezes:
And what do we do for banking apps, Netflix, Uber, etc? Keep a physical bank branch, a TV+VCR, and a car also on us? 😞

unfortunately physical cards only solve the Google Wallet problem, which many of us (eg myself) don't even use.
[Magisk] xSnowLeopardx:
I know this sounds crazy, but I almost want my first FP to get banned, so I can finally use one of my other 19 lol. I thought it would be a thrill, for me to go through my stock and the hunt for more to be there, but it's boring haha.
[Magisk] beeshyams:
Publish it here and on some selected Tg channels.. Wish fulfilled.

I only grant one wish fulfilment per day for random strangers
[Magisk] xSnowLeopardx:
Not gonna publish anything. Would rather not use them than see them banned.
[Magisk] sawdoctor:
What device and firmware? If you are running android 14 beta then we know the issue. If not no clue unfortunately
[Magisk] simplepinoi177:
I think he meant publish your one that is working but

Unless you truly want to "hunt for more", then publish all of them -- or better yet give them to chiteroman to burn through in the next couple of weeks (you have, like, 19!); that would lead them to be banned for sure!😅
[Magisk] beeshyams:
I was kidding and neither do I approve of it and therefore won't share my stash
[Magisk] xSnowLeopardx:
Ah yeah, gotcha.
[Magisk] xSnowLeopardx:
Ouch :z
[Magisk] switchem:
Okay, I think I'm getting the hang of this thanks to the great documentation by osm0 and simplepinoi177. I found a place for dumps, and am trying things out with build props with API levels between 23 and 32. Holy cow, the PixelFlasher tool is such a life saver! What an amazing tool for this.

Question...in the Play Integrity test ran from the Play Store dev options, should the "Build Fingerprint" always remain that of my device? Or should it match that of the build props device/pif.json? Just making sure I'm doing it properly.

Also, I know it's random and depends on how we're vetting the tries, but how many tests does it usually take to find a working one? A few dozen? few hundred?

Btw, I'm finally passing Basic Integrity tests. I was failing with the default v14.4 FP.
[Magisk] simplepinoi177:
Mine stayed to my device, not the spoofed one in the pif.json.

It took me about 30 tests to find a working one, but then again I couldn't find one working from those sites and only found one from an extracted ROM image...
[Magisk] switchem:
Okay, good to know! I was a little afraid I've been wasting my time, haha.

Hmm...extracted rom image, meaning you downloaded a full 3+ GB rom and extract the build.props yourself from one of the img files?
[Magisk] switchem:
Before I get too deep into testing build props... which apps do I need to have on the DenyList in Magisk?

Also, I don't need to manually clear any data from settings > apps between tests, right? I just process a build prop, run integrity check, and move on to the next one, yeah?
[Magisk] wfred:
For the most phones if you go back to straight stock & relock then yes

However; I've read that there are some brands (Samsung?) that won't
[Magisk] simplepinoi177:
most likely the KNOX trip...
[Magisk] Wolfcity:
@badabing2003 : I'm searching for the post of a user running Windows7 and not being able to use pixelflasher but this thread get's more and more overwhelming....

As my Windows machine has gone to where computers go when they die I'm using an old laptop (W7) and have the same problems (missing DDL). Anyway to come around this?

I'm using @osm0sis 's script ATM which is ok for me (found about 10 fp's and the first one is still working....)but I'm interested in pixelflasher .

And sorry for not posting in a related thread but you've got a lot of PF threads...😉

Edit:

Related post was from @awarexda :

I decided today to find a FP...

What a nightmare

First, I couldn't install PixelFlasher (python errors and missing dll)

Then I just made 2 of them but I couldn't find ro.build.id at all or vndk

I tried them anyway and of course they failed

I am not so happy with this
[Magisk] Depressed T.Bear:
That is actually not true. Most people who complain about the fingerprint being "banned" have previously used their own fingerprint. With version 14.4, the template for the pif.json has been extended by Build ID and VNDK version. As these are missing in their old pif.json, the values of the pif.json that ships with 14.4 are internally added.

For some people, this means that the fingerprint as a whole is no longer valid. The fix for the problem is therefore simple, people just need to read and understand.

---

My first fingerprint, which I found over a week ago and have been using ever since, is still working properly.

Even if I understand the frustration of some people that chiteroman "burns" fingerprints, I find this criticism absolutely inappropriate. He helps us and, above all, those people who have a less in-depth technical understanding.

I have already seen people trying to sell their found custom fingerprints, as soon as the current fingerprint was no longer valid. Fortunately, his approach currently prevents such "business models".

The mere fact that Google is gradually banning fingerprints and that there is no replenishment means that sooner or later it will be over for all of us. This is a fact that we have to accept as things stand at the moment.

In my opinion, however, this does not mean that it will really be over at some point. It just means that other new "ways" have to be found. The sooner this happens, the better for us all.

At least that's my view of the current situation. Of course, everyone can see it differently ;)
[Magisk] badabing2003:
I'm assuming that you're using PixelFlasher_Win_2019.exe and not PixelFlasher.exe

Provide a support file and let me see what is happening.
[Magisk] simplepinoi177:
Unless we (as a community, not me; I have no idea what I'm doing) figure out what measures Google takes to discern the difference between devices that are spoofing vs. the actual device...
[Magisk] Klappp:
Don't look down on yourself like that. I believe in you. Go and figure out what Google is doing and bring us the good news.
[Magisk] simplepinoi177:
lol I could just barely figure out how to get a single working fingerprint....yea...let's trust me to break down all of what Google is doing and bring this good news....😅🥴
[Magisk] HippoMan:
BASIC may or may not fail in this case, depending on your device and OS.
[Magisk] Depressed T.Bear:
Correct. I'm not an expert in this field either. However, as I have written before, my simplified theory is as follows:

1) Thousands of identical fingerprints query their validity at Google within a very short time. --> 2) Google/the algorithm says: Wait a minute! Something is not quite right here! --> 3) Google/the algorithm requests the fingerprint again on all affected devices via another app/service --> 4) The other app/service, which is not spoofed by the module, sends the original fingerprint back to Google --> 5) Google/the algorithm detects a mismatch for all devices in question and bans the common denominator: the identical (spoofed) fingerprint.

According to my theory, the app/service must therefore be identified and the spoof accordingly extended.

Maybe I'm completely wrong - but at least that's how I imagine it. 🤷‍♂️
[Magisk] sawdoctor:
Some brands work better than others and it's always a good idea to set 1st api slightly lower. Also as others have been saying the latest 14.4 takes missing fields and adds them from the included print i think which has messed a lot of people up.

I'd recommend usind an earlier version (I'm still using v14.0) or @osm0sis fork
[Magisk] simplepinoi177:
Yeah, when I fortunately got mine working, I was on osm0sis' V3 fork, so maybe I got lucky. I did notice something weird when trying to include the ro.build.id and it wouldn't pass even though when I did it originally PF didn't include the field and I passed, so once I removed the line it started passing again!

But thanks for the advice! When my fingerprint finally gets banned/burned, I'll keep that all in mind...

A thought....you suggest to do this even if the FIRST_API is already as low like at 24 or 23?
[Magisk] Vision:
pif.json from 29 (original) to API_LEVEL=28
[Magisk] HippoMan:
It's certainly a reasonable scenario.

And the Googlefrinchians know the inner details of their software much better than anyone else, and so if we could figure out such a scenario, I have no doubt that the Googlefrinchians knew about this method (or something similar) long before any of us.
[Magisk] sawdoctor:
Mine was 30 to 27 and then it worked. Fingers crossed neither of us need to go fingerprint hunting again. If we do i have a large collection of build props you can gave to hunt through
[Magisk] DougMG:
The very real potential downside of expanding the use of the spoof to other areas is it starts causing things to quite working as they now think you're using an older device which doesn't have the specs that are needed to run the app and it then refuses to run or won't install in the first place.
[Magisk] simplepinoi177:
This is sort of what I feel is going to happen for the Pixelify Unlimited GPhotos.... they're going to start wondering why so many 8 year old phones are still uploading to Google Photos in droves....
[Magisk] Iridule:
I found that if basic ever fails any edit to the fingerprint valid or not will cause it to pass ... For example change " release-keys to dev-keys" I can get to pass basic but not device.
[Magisk] mates21:
I really understand that it is difficult for some people to make their own print and the creator wants everyone to be able to have 2 green ones. However, I appeal to stop sharing the fingerprint because in the end, people who have tried for a long time and have their own fingerprint will also have a problem because Google will ban them. I'm afraid that my fingerprint will be used in a fix and will soon be blacklisted.
[Magisk] Klappp:
Tbh I don't think I'll ever own a phone that will last 8 years let alone 5, and when the time comes to upgrade, I will most likely pick up a pixel phone because I will miss the unlimited photos backup. I like to think of it as a free trial of owning a pixel phone and I like to think that that doesn't bother Google.
[Magisk] simplepinoi177:
That's probably the general consensus (and most logical conclusion), but because of that logic, it should put up a flag to Google wondering how all these 8 year old phones are "supposedly" still "utilizing" (exploiting) that feature...

You do know that pixel phones no longer offer unlimited photos after Pixel 5, right? I'm sorry if I misunderstood what you're saying, but "pick[ing] up a pixel phone", unless it's a Pixel 5 or older, wouldn't give you that regardless....
[Magisk] sawdoctor:
Chiteroman has already stopped supplying his own fingerprints he is now only using the ones that xaiomi Devs supply when they update. Yes i totally agree with you but until the custom ROM devs stop supplying prints nothing is going to change
[Magisk] Klappp:
They don't? What a shame
[Magisk] BunnyPig1:
Do we know how often custom roms get updated with new fingerprints?

Read some pages ago that it was 1-2 per week, but don't know if that was a guess or real information. Just curious at the rate the fingerprints are being banned.
[Magisk] simplepinoi177:
Right!?!?!?! Was a total bummer when I found out when getting my Pixel 7 Pro too! Just like when my mom upgraded from a S20 to a S22 and found out they withdrew having external storage!

But WTH Google! With as big as HDR 10-bit 4K videos and Ultra HDR photos, if you're not going to offer an external storage option.....

Well....I guess it mattered more when their phones were maxing out at 256GB, but still.....
[Magisk] simplepinoi177:
On top of that, are them Xiaomi custom ROMs getting their custom fingerprints burned as fast/at-the-same-rate as chiteroman's?

I mean, now that he's using their fingerprints, I imagine the rate is higher/faster now, but then compared to before chiteroman picked up that practice...
[Magisk] bentree:
A big thank you to @osm0sis and @simplepinoi177 for their detailed guides and thank you to @badabing2003 for the creation of Pixel Flasher. Without you 3 I would not have been able to find my first custom FP.

I think @chiteroman deserves a big thank you too! Without his constant FP fixes, I probably would not have had the time and patience to get this far.

I know some people don't agree with @chiteroman way of doing things but please understand that for a lot of people this process is very daunting and it can take some time to build up the confidence to try finding our own FP. Let alone finding the time between work, family and other unexpected life commitments that show up.
[Magisk] kocsogfax:
Did any of you find a working fingerprint for Android 8.1?

I have found fingerprint for Android 8.0, but none for 8.1...
[Magisk] Umgak:
Using an 8.1 print since the 1st. No issues with it.
[Magisk] pndwal:
Doesn't detect root with my setup... Did you check the links?... I even double checked for you...

Hint:

TJW Canary Magisk is official Magisk with official Zygisk... It may get NB-Z with bump to 27.0... 😜 PW
[Magisk] chrbur:
First: Thx for your help :-) !! There was a mistake in my last Message. I installed not Canary but Delta. But maybe I installed the wrong version? I do not understand anymore :-D At least i know it's not allowed to install official Magisk. Sorry (really for that stupid question) what Magisk is now the right one? Do you have a direct link?

Thank u so much :-)
[Magisk] rekids:
V8.4 passes all but strong as expected, but I still can't get 8 ball pool to load (don't laugh) and this kind of bad want for me since its one of the few things I can do with my son who is in another state. Used to be able to get it to load using Magisk alpha (not official) and older Saftynetfix 2.4 mod 2 some time would have to load a banking app or our state fishing license app that pulls the current fishing licensing information instead of having to carry them all the time on you. Either way don't think the game as updated in the last week but I have tried both current Magisk Canary and Official releases to no avail. Any ideas? Was hoping this is one of those things that fixes that works for everything I use. The other app i do use that does work is Matterport that used to be a pain to get it to load unless you had all but strong. Does 8 ball check for Strong?
[Magisk] westruk:
Nope
[Magisk] suloku:
I've been looking around and can't find anything to make device integrity pass on an android 7 device with magisk v26.3.

Safetinet basic ans cts passes, but on playintegrity only basic integrity is a pass.

Is there any way to make it pass device integrity?
[Magisk] zgfg:
For A7, ie, for your old device, you should probably use the old MHCP methods (instead of USNF or Play Integrity modules). And try (with and) without Shamiko - ie, if you use Shamiko, then check does Shamiko display an error in the Magisk app, modules page.

If not using Shamiko, you have to enforce DenyList
[Magisk] latamboy:
Shamiko doesn't work on android below than 8.

I'm on A7 with xposed but i don't even pass basic
[Magisk] chiteroman:
I have updated the main post to better explain what my module does and how DroidGuard works, in a very summarised way.
[Magisk] chiteroman:
Failing BASIC -> DroidGuard detects abnormal system and/or injections into process.
[Magisk] Hausemaster:
Might be unrelated, I too have an Android 7.0 device,I've noticed that Play integrity check always returns basic true and nothing else, the twist here is that apps like Netflix that need both basic and device to be pressed appear in Google Play.
[Magisk] ykjae:
Probably also very unrelated - I have been running play integrity fix 8.4 instead of usnf for a while. Suddenly a few days ago company portal says device is unhealthy. With a lot of tinkering I couldn't figure out what else to hide/change. I reverted back to usnf mod and device is now "healthy" I also think I bypassed company portal anyways now.
[Magisk] supermansaga:
You on company portal 5.0.5981?
[Magisk] WhoIsJohnGalt1979:
Am on it and teams and Outlook and o365 works just fine. I can give you a small tip. Usually when company portal updates, in the past I have seen, there is an extra line item that gets added to the magisk drill down of the app in deny list. Now if you open the app right after the update it will detect root. But if you just select that extra line so that the entire app is checked in deny list and then open the app all will be well. Just something to notice in deny list after updating some of these pesky apps if there is any additional line items are added. In your case I would suggest you to first properly log off all Microsoft entities, remove them from deny list, delete data and uninstall them, reboot phone, install them back, add to deny list, delete data from all apps (preferably in air plane mode) reboot and then go about logging back

View attachment 6002751

And yes as @spida_singh noted Shamiko is an absolute yes for if you want to use all the bouquet of microsoft products. Company portal and outlook might go through just using usnf/integrity fix, but for o365/teams/one drive, meh you would need Shamiko.
[Magisk] spida_singh:
You need Alpha and Shamiko if it trips again. I was on delta and nothing worked for me

https://xdaforums.com/t/tutorial-ro...h-magisk-update-q3-2023.4402273/post-88996973
[Magisk] WhoIsJohnGalt1979:
move to magisk alpha if playing 8 ball is a priority. support is limited though. so kindly adjust accordingly
[Magisk] Johnn78:
Any trick to pass strong integrity ?
[Magisk] ykjae:
Yes I'm on 5059810.0 using magisk canary. I couldn't get past device is healthy no matter what.

I ended up using app manager and disabled alot of services/activities/receiver's and now I don't even seem to bred the app enabled in admin mode.

I will use magisk alpha once this fails. Thank you for the suggestion.
[Magisk] ykjae:
Already patched. Not passing SI unless you revert to stock and lock bootloader.
[Magisk] Johnn78:
Others says that flashed UNSF test4 and passed SI but it didn't work for me. I am on stock OS but locked bootloader.
[Magisk] pndwal:
Find another exploit/bug then develop an exploit (and DON'T tell anyone!)... Or restore stock images and re-lock bootloader...

Oh... you already have stock OS and locked bootloader! (Oh well, device must have a broken Keymaster implementation etc and/or Google has revoked keys for strongIntegrity on your device)...

Possible you lost unique values in /persist partition while unlocked, and you may be able unlock and restore from backup or other means per device, but if not you'll need a new device! 😜 🙃 PW