yashsingh1/xdaforums huggingface dataset:
[Magisk] Wolfcity:
No, I was using pixelflasher.exe from here:

Releases · badabing2005/PixelFlasher

Pixel™ phone flashing GUI utility with features. Contribute to badabing2005/PixelFlasher development by creating an account on GitHub.

github.com

PixelfFlasher_Win_2019.exe seems to work now, I've updated the platform tools, haven't tested all features but at least it's starting and mainly working.

Haven't seen that there's a source for another version (2019).

Thx for now!😉
[Magisk] switchem:
Good to know!

I'll switch from 14.4 to the osm0sis fork.

So if I'm using PixelFlasher, I should manually edit the json to lower the api level number before pushing to the device?
[Magisk] arda99:
Now that's interesting:

I'm using a private fingerprint. From an A11 ROM the phone was released with A10 thus I set FIRST_API = 29. This used to work fine for the past 2 weeks and suddenly fails for device today. Still pass Safetynet with evaluation type "BASIC", lower the FIRST_API to 25 pass PI again.
[Magisk] simplepinoi177:
That seems to be a lot of the experiences here....

It might be just me being hopelessly hopeful, but what if all it took was simply changing FIRST_API each time it gets burned/banned? That might mean that we wouldn't need to panic about the finite number of fingerprints as we could just keep using the same ones, just adjusting the FIRST_AP_LEVEL by one level and we have from level 34 down to 23...!

**~sigh~** if only.....
[Magisk] arda99:
I think this specified model is targeted. Tried another working FP from it same issue, need to lower FIRST_API. However, a sister model(as unlocked vs carrier) still works with FIRST_API = 29, but it might fail anytime.
[Magisk] purgy:
That was me in the pixel flasher thread and win 7, @badabing2003 added a Win 7 compatible build, it's named pixel flasher 2019 vs the other variants.

The directions on the readme are straightforward enough that I could manage to make my own build without too much hassle, if the 2019 version doesn't work
[Magisk] djcsurf:
It seems Google have updated PS in last couple of days and today I noticed a mod app I use show up in updates which was strange, this made me think to check netflix which now shows as not available for my device. So I checked wallet and it now doesn't meet device requirement. Thought I'd try the other pif I searched out, replaced the old one cleared GPS cache, rebooted and same thing with netflix not available. So either the update has broke it or my 2 mined pifs have burned out. Using v14 from chiteroman
[Magisk] Iridule:
Change API to 00 in my experience every print I've tested that API can be changed. 00, 0-25 ... All will work. I've got about 50 working prints many with API 30 changed to 00 causes device pass.
[Magisk] simplepinoi177:
maybe, but I had an experience where I was testing other prints, and when I went back to the single working one I found, it suddenly wouldn't pass DEVICE. I also couldn't get netflix or Turo as well with Google Wallet not "meeting security requirements". After rebooting, the pif.json ended up being blank, had to paste in the values once again, passed but things still didn't work until I cleared data on the 4 requisite Play services (Store, Protect, Services, Framework).

look at this guy bragging ;)

I thought putting it to 00 was almost the same as putting it to "null"/blank and it just passed as the default value of the phone (which usually wouldn't allow it to pass), Good info to know. I will add it to my thread.
[Magisk] Iridule:
TBH, I'm not sure. Though I know if left blank or written "null" it failed. I got bored one day and just went backwards from one API all the way to single digits and tried 00 and all of them worked to pass. I'm not sure why for those devices, but every device I find in which API can be changed it seems this will work. Wish I knew more as to how it works...also when devices get no integrity, changing any line of the fingerprint such as remease-keys to "dev-keys" causes basic integrity to pass but not device... Again not sure why...
[Magisk] chiteroman:
View attachment 6044870

Completly destroyed hardware attestation security.

But I can't pass Strong, maybe I need to spoof debug keymaster values.

There is an easter egg in verified boot key 🤭
[Magisk] osm0sis:
Yep, that much we know.

https://twitter.com/i/web/status/1735097916199416099
[Magisk] ugene1980:
Some light at the end of the tunnel for people with device that has broken TEE once unlocked...?

OP11 and Redmagic phones~~~
[Magisk] intel_core_i7:
Haven't you guys talked about this few days ago?
[Magisk] switchem:
From my understanding, I'm in this broken TEE boat with my Lenovo Legion Y700 2023 w/ SD Gen+ 1. Does this affect my ability to use this module to pass device integrity? Am I wasting my time finding and testing FPs?
[Magisk] beeshyams:
I am not affected by broken TEE but I am also keen to know the answers

Edit:

I know

1. You can't pass strong (which you shouldn't be able to with UL BL anyway

2. Widevine may not work
[Magisk] switchem:
Hi, thanks. Yes, I'm aware that I can't pass strong with UL BL. I'm just asking about the ability to pass device integrity. At the moment I'm only able to pass basic.

And then I'm hoping I'll be able to use netflix if/when I am able to pass device integrity. Or will the DRM issue still exist?
[Magisk] switchem:
EDIT: *RESOLVED*

I'm testing the HDMI over USB-C for the first time since unlocking and rooting, and it's not working. Also, I'm unable to turn off the "charge connected device" option. It just says "couldn't switch". Says same when i try to change the "controlled by" setting. Could this be related to integrity? I feel like it's an android or lenovo bug, but I thought I'd ask here to be sure. Device: Lenovo Legion Y700 tablet, 2023 model, Snapdragon Gen+ 1.

EDIT: It seems that my 2022 Y700 works just fine with the "controlled by connected device" setting on, as well as the "charge connected device" setting on when using a USB-HDMI cable. So, for some reason, my new tablet just isn't triggering the "Projection Screen" video out. This makes me think it's due to the same device-integrity/DRM issue that is preventing netflix, etc from working.

EDIT #2: Okay, I got it to work. The issue was the dock I was using. It's a dock for the Steamdeck, and it worked fine for my 2022 Y700 supplying power and handling video out via the one USB port. But the 2023 Y700 does not like this dock. Plugging it in seems to bug things out because I have to reboot the tablet to get the normal USB-to-HDMI cable to work. But not that cable works fine! And I can supply power to the device using the short-side port, so all is good.
[Magisk] beeshyams:
That's what I want to know too 😂
[Magisk] switchem:
Haha, I really hope I can find out for us! 😆
[Magisk] pndwal:
Can either of you achieve DEVICE_INTEGRITY If you have only PIF 14.4 module active (w/ no pif.json file in /data/adb/ directory and w/ nothing Google in denylist) and Zygisk=Yes? PW
[Magisk] Nekromantik:
so turns out ksu is reason i was not passing device.

switched back to magisk and passed it on 14.4
[Magisk] beeshyams:
My TEE is fine, I was just curious
[Magisk] switchem:
Oh, I don't know. Should I try that? Are you saying it should/might work?
[Magisk] pndwal:
Should try / should work if DEVICE_INTEGRITY is possible AFAIK... PW
[Magisk] ugene1980:
Not them but

My device, redmagic 8 pro has a broken TEE when bootloader unlocked

Using KSU + pif1.44

I can get device and basic integrity passed

Problems occur when apps need a working tee :( which my national identification app is such an app
[Magisk] switchem:
Is netflix one of those apps?
[Magisk] switchem:
I tried this and it didn't work. :( Same results as I was getting before I tried a custom FP – it takes a long time (up to a minute) to process the check, and then it times out or I fail all integrity checks, even basic. Is this a symptom of a different/bigger issue?
[Magisk] pndwal:
Don't think it's detecting bad key attestation... If Key Attestation is required that's foolproof and I don't know of apps implementing that yet...

Guess we're talking Singpass... I had it (v18.2.0) working in July w/ Alpha (native bridge loaded Zygisk):

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-88714867

... Now TJW has merged NB-Z, but it's no longer working... I suspect they simply updated (v20.1.0 now) and detect resetprop, other Zygisk traces etc...

... @rushiranpise had it working in October w/ Zygisk for KernelSU, now ZygiskNext, + Delta:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-89116233

...If still working, Delta probably isn't necessary although it moved from old Maru NB-Z POC to ptrace+fuse loaded Zygisk (from ZygiskNext) for its inbuilt Zygisk...

TJW Magisk w/ ZygiskNext module may also work, but I note the only current success stories for some apps (notably Starling Bank) are to use KernelSU root + ZygiskNext to defeat resetprop detection... PW
[Magisk] pndwal:
Bad OEM keymaster implementations or other AVB chain of trust component issues differ, and it could be that the device is incapable of DEVICE_INTEGRITY especially if its a China region device, but this is doubtful...

Some OnePlus devices show "broken TEE" (really just broken key attestation, TEE OS is fine so biometric scanners, Widevine DRM decryption etc still work) only when unlocked, others (many) fall back to BASIC-only attestation due to bad keystore or other issues causing an exception, and can pass DEVICE_INTEGRITY locked or unlocked with spoofing...

So it's hard to say what issues a particular device may have exactly...

Please post screenshots of YASNAC raw JSON results with PIF loaded and without... I'm interested particularly in the evaluationType attestation from that API, but also if you pass ctsProfileMatch despite no PI DEVICE_INTEGRITY... PW
[Magisk] Klappp:
OnePlus Nord custom fp with Kernelsu. Only windvine doesn't work
[Magisk] Nekromantik:
yup sadly ksu is only way to make starling work however on my phone device integrity does not pass with ksu so im back to using magisk and turning zygisk off once every 14 days lol
[Magisk] Bxperiaz3:
Hey guys, last ditch attempt to get my device integrity working. I'm using the Generate PIF script using termux which is working great but I cannot for the life of me find a fingerprint that works. I've done over 18 different builds/phone without a single match whilst trying to follow the guidelines for what makes a good fingerprint. I'm aware it takes time but I've given this over 12 hours of work without a pass to the point where I'm wondering if I'm just not doing something correctly. The device integrity pass I got was before chitheromans 14.4 got banned.

Everytime I replace the . Json file I've been clearing play store data reinstalling v2 dev through magisk and rebooting. Are these necessary steps?

The killall command doesn't work on my phone. I feel like I need another xiaomi eu release just so I can sanity check that it actually does work,albeit briefly.

Any help would be greatly appreciated as the telegram channel is carnage and trying to get help is providing difficult.
[Magisk] switchem:
Gladly! I appreciate you taking a look. When I don't have PIF loaded with a custom FP, I fail everything and YASNAC times out with an error "Attestation response timeout", but I can post the JSON responses from Google Play and a couple other checker apps.

FYI, for what it's worth, even when failing everything, the DRM Info app says i have Widevine L1 and the Youtube TV app works fine (although I have no idea what that app requires to work).

Will post screenshots soon. Thanks again.
[Magisk] Wolfcity:
You don't need to reboot. If the killall command isn't working for you just go to settings,apps, choose GPS and force quit.
[Magisk] osm0sis:
Are you on my Fork v4 or on PIF v14.4? Usually the timeout or bad token responses mean GMS received a null somehow and may be crashing in the background (sometimes foreground).

I believe I fixed this in v4 on my Fork, so I'm curious about what exactly you mean by your setup of "don't have PIF loaded with a custom FP". 🤔

Edit: Yep, must be v14.4, since I can confirm mine doesn't do anything in the logcat, and checks fail correctly with no custom.pif.json present. 👍
[Magisk] Bxperiaz3:
Ok thank you. Even though I have a custom pif file the momo app and play integrity checker still just show my Pixel 7 pro keys. Is this normal behavior or should it show the device I spoofed?
[Magisk] Wolfcity:
Normal. PIF only spoofs for droidguard ,not the whole device.
[Magisk] xSnowLeopardx:
Still curious if there are people who had to use one of their other FPs because their first died...
[Magisk] osm0sis:
A few people have had to because their FP was used by a ROM or chiteroman, but none that haven't had theirs otherwise published that I know of.
[Magisk] simplepinoi177:
Don't lose heart, @Bxperiaz3! If I, as a completely utterly total noob, was able to get it working, I believe anyone can! Are you making sure you are following osm0sis' guidelines? Apparently messing with API_FIRST_LEVEL (or whatever is called) really helps. In any case, check out my thread below (particularly Section 2; or testing portion in Section 3) [noob friendly space to receive help] Also, I emphatically urge you to employ using PixelFlasher to process, implement, and test fingerprints -- it's very automated and straightforward (as you seem to be doing it in a very manual and tedious fashion; can be read further in my experience/guide below)

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

The only person I've seen is the one below (not quite use their other ones, but their first one had failed and it had to be modified and/or replaced [in a certain way of looking at it])
[Magisk] HippoMan:
There seem to be an increasing number of reports lately of people getting their erstwhile rejected fingerprints accepted simply by lowering the value of FIRST_API_LEVEL in the JSON file.

I wonder how long it will take before the Telephone Sanitizers catch on to the fact that people are starting to use this technique.
[Magisk] ArzZenic:
Mine also still works, since 02/12. Good luck to us all :) (through your Fork v3)
[Magisk] xSnowLeopardx:
Same with 02/12. Very happy I can finally worry less while paying at the canteen haha
[Magisk] ArzZenic:
Yeah, but you know, I still have my physical card with me, just to be sure. Also checking Wallet every time before even trying the payment.. oh the paranoia :D

Atleast we can see in the source code of Chiteroman's versions which FP is he using for wide public, so we can check, if our FP is getting fu*ked in like next 48hrs since his new release :D
[Magisk] xSnowLeopardx:
I keep an updated .zip of my folder with all FPs on my phone. If I ever see that my main is RIP, I will just change it on the go.
[Magisk] ArzZenic:
Thats a good idea. I'm just kinda lazy rn to check for backup FPs, sice mine is still working. After this one is gone, I'll get FP's same way as you, so I have more backups in internal storage and I'll only have to reset and kill GMS.

The ordeal that I had through 50 tries was quite exhausting.. :D
[Magisk] simplepinoi177:
I'm fairly paranoid as well! Saw this great tool (below)! It hasn't triggered for me yet (just found my own personal fingerprint last week), but seems promising (I use the Tasker option [don't want the "on-zero theoretical possibility" of flagging Google on my spoof fingerprint]) because I see the Magisk toast everytime I unlock the screen....

GPay Checker: monitor of Google Pay availability

Google Play Protect now triggers onto app (that's honor for me), but here nothing criminal. You can safely skip warning. There is non-zero theoretical possibility, that using this app increases risk of banning your personal fingerprint. There...

xdaforums.com
[Magisk] ArzZenic:
Thank you & Bonoboo (kudos Dev)! Seems like a great tool! I'm going to try it.
[Magisk] sawdoctor:
I have about 4 working json files on my phone but not enough for a zip lol
[Magisk] chiteroman:
A bit of spam about my Xposed module: https://xdaforums.com/t/spoof-locked-bootloader-bypass-tee-check.4586251/post-89223662

😋
[Magisk] awarexda:
Monday is coming, time for new fp....
[Magisk] Iridule:
Can we start a poll of who's first custom print is still working? I'm curious. I got mine on December 5th... Still good.
[Magisk] hamooz92:
Thanks a lot for that module
[Magisk] osm0sis:
Don't be afraid to update to v4! 😛

My first print that I'm still using is from Nov. 19th when PIF v13.1 first added pif.prop support.
[Magisk] ArzZenic:
I'll update, when my first FP stops working. Is there anything with an huge impact (I've read changelog, but since I just want to spoof the FP), why I should be updating to v4 right now if everything works?

Thank you and kudos once more osm0sis, great work! :)
[Magisk] osm0sis:
More future proof, more stable.
[Magisk] aerotox:
In the github, which file can you see the currently used FP in the public fix? I'm just curious, using private myself
[Magisk] stanley321:
Our current FP lottery winner is here

PlayIntegrityFix/app/src/main/java/es/chiteroman/playintegrityfix/EntryPoint.java at main · chiteroman/PlayIntegrityFix

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com

My first FP still works, so I am here just to make sure I didn't win the FP lottery.
[Magisk] xSnowLeopardx:
Still safe 🥰
[Magisk] simplepinoi177:
apparently, if/when does fail, so many users are reporting that simply changing the FIRST_API on that same exact fingerprint should get you passing once again...

so, if true, did it count as "still working" of it's basically the same fingerprint? or not because it failed at one point...?
[Magisk] Iridule:
I've found only some prints work by changing API. most that can be changed can be changed to 00 even. The ones that can't be changed any API change will break the print.
[Magisk] Dragon Kumera:
my p8p is working! But need to see how my pixel xl gen 1 works with this
[Magisk] me_droid:
Currently using @chiteroman DEV-v2 with found fp. Are there any advantages to using v14.4 or @osm0sis Play Integrity Fork v4? So far everything's working fine with DEV-v2.
[Magisk] trevtdogg:
I'm also still using v3, will update to your v4 when I need to use a different print.

but since it's not broken yet, I'm not fixing it!

nfc payment is working very reliably for me so I'm not gonna rock the boat until I need to.
[Magisk] simplepinoi177:
my personal intention is to ride mine for as long as it passes and "leave well enough, alone".

@osm0sis says his v4 is just more future proof; so when i need to find another fingerprint, i will def use and "proof" it in the "future"; it will stick better, i predict.
[Magisk] tupu4545:
So I rooted my galaxy m34 with latest magisk

Note: everything was working fine in android 13

When I upgraded to android 14 with Magisk and performed a factory reset no matter what I do I cannot pass safety net

Basically if I flash the play integrity fix I pass the test. Goood! But if I restart my phone I fail the test even if I reflash it no matter what safety net fixer I try I can't pass the test this wasn't a problem in android 13 any solutions?
[Magisk] sga999:
I think 14.4 print has now been banned?
[Magisk] Claus….:
Omg, no sense to keep going with it
[Magisk] fbirraque:
Confirmed PI 14.4 R.I.P.
[Magisk] supermansaga:
Is the v4 from @osm0sis supposed to be able to work on Windows Subsystem for Android (WSA) with KernelSu? Could he please enlighten us? I thought I updated in the right order. Still YASNAC would say all fails. I recall that was the case for Magisk, but I was hoping against hope that KernelSu is much stronger, but I guess not in the case of WSA? Many thanks

SafetyNet - osm0sis Play Integrity Fork

Ooops. Indeed unable. According to FAQ at https://GitHub.com/MustardChef/WSABuilds

Can I pass SafetyNet/Play Integrity?

No. Virtual machines like Windows Subsystem For Android™ cannot pass these mechanisms on their own due to the lack of signing by Google. Passing requires more exotic (and untested) solutions like: <https: 145#discussioncomment-2170917="" discussions="" github.com="" kdrag0n="" safetynet-fix="">

So exactly how do I access the untested solution? Thanks
[Magisk] chiteroman:
v14.5 released to fix Google latest update.

Release v16.5 · chiteroman/PlayIntegrityFix

Update hook framework: Dobby Fix Device not passing in few devices Improve code Reduce Zygisk libs size

github.com

REMOVE /data/adb/pif.json if you want to use default json.
[Magisk] sawdoctor:
Not going to flame you or anything don't worry but is the bundled fingerprint the same one as the xaiomi Devs again? Be interesting to know if it is an algorithm banning the prints just what the threshold is.
[Magisk] osm0sis:
Do you have a custom json? My module requires one.
[Magisk] stanley321:
Where can we check the Xiaomi.edu lottery winner?

New lottery winner for 14.5:

PlayIntegrityFix/module/pif.json at main · chiteroman/PlayIntegrityFix

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com
[Magisk] xcl1pse:
Yes its same
[Magisk] sawdoctor:
So the last 2 have been from devices starting with A (one before was an android TV). So if using a custom fingerprint safest to start at ZTE and work back?
[Magisk] xcl1pse:
Actually matters on how much users use the same fps. I dont know if all Asus one already burned. Also dont know how Xiaomi EU Dev and chiteroman pick a fps, maybe a random guess or as alphabetical. Pick a rare brand and model can help to prolong fps before getting banned. Maybe using ZTE can help but I cant promise how long it can survive
[Magisk] beeshyams:
A lot of people would be thinking on same lines. I'd go for some brand you've never heard of
[Magisk] osm0sis:
Happy Monday! 😛
[Magisk] miimaa:
Noob here. Finally trying to make my custom fingerprint.

I've downloaded several ROM's. Those are all zip-files. When I extract those zip-files, I get img-files. Am I suppose to open those img-files somehow or where do I get the values to copy and paste?
[Magisk] Klappp:
Use MTK extractor or any ext4 extractor application to open it
[Magisk] sawdoctor:
I'm using one that shouldn't work but did by changing the 1st API level so hopefully it will last longer. 2 weeks now and still working fine

If you Google android firmware dumps you'll find a link with all the firmwares extracted already and you can just grab the buildprops.
[Magisk] purgy:
Look for Android dump sites, some of them you can browse the file structure online, then just download the ~4kb file you need (build.prop) rather than a 2gb+ zip.

Build.prop is usually found in the system folder, sometimes system/system
[Magisk] GabbyWC:
ZArchiver supports IMG files. Open one IMG file at a time in that app, then copy / extract only the build.prop files from the system and vendor directories to a folder on your phone and use those files to obtain the data for your custom JSON. See the helpful guide from osm0sis here and use his shell script from here to make things much easier. If the downloaded ROM zip files don't contain .br or .dat files to extract first, that's a good thing.
[Magisk] miimaa:
I DID IT!

Thank you guys for your help. First try and success. FY Google!
[Magisk] kingpeppermint:
What i don't get about the banning of signatures, as these are all from real devices, aren't there people out there who own those granted slightly dated devices? Wouldn't they be blocked then aswell?
[Magisk] wfred:
I started using this print as a pif.prop in v13.3 Converted it to a json when the fork came out.

So since 11/23ish