yashsingh1/xdaforums huggingface dataset:
[Magisk] flobo09:
Thanks a lot for your answers.

I'll do that ( Griffin print) but before, i'd like to try to do some groceries later this morning.

Because RCS is still working and google pay was still working yesterday as well. On my other phone with another print, when there was the great ban, i seem to remember losing them both (RCS a few days / weeks later though). (I didn't care to fix fast because i didn't need google pay on 2 phones, i only fixed it when i Lost RCS and now both phones are running my same old November print and both are failing DEVICE).

I guess it could always be cache but after 24h, it should have expired so i'll check anyways.

I have also caught back on the last few weeks worth of stuff happening this morning.

I'm in France & the french new ID app requite STRONG, which is annoying as i wanted to use it for remote voting (giving voting rights to a third party in the EU election next month).

If strong gets more uses over time, if i understood it all correctly, our only hope will eventually be that enough keyboxes get leaked so that they can't easily be massbanned, right ?

No idea if it's a likely scenario or not but seeing the amazing work done by chiteroman, osm0sis & hex3l over the last few weeks, i'm now thinking that "maybe" the community still has a chance of beating all this and and letting android modding / rom / root alive for a bit longer at least.

And also old phones ! My mom is still using my perfectly working Pixel 3 on the latest Lineage and it's become a mess to 'remote fix' her every time google does something. I feel like a Pixel 3 on lineage ought to still be more secure than a plastic card in a purse but whatever.

(I really thought we were ****ed for good with Play Integrity so it's a bimmer of light)

I'm mostly a lurker over here with a basic understanding of it all, but just an GREAT thank you to all the people i mentioned and those i probably forgot for doing their AMAZING best trying to keep the dream alive and making the tools understandable for all !

(A bit like those heroes bypassing new ads system on youtube every single week, amazing than community can sometime win against giant corporations).
[Magisk] flobo09:
Well interestingly, 24 hours after losing Device, Google pay is still up & running :

I'll ride it on and see how long it lasts :

View attachment 6099208View attachment 6099209
[Magisk] zgfg:
If you can't pay by phone, you can try payment options with your car

Xiaomi SU7 latest Q&A session: Braking system, Payment Options, Sound simulation and more - XiaomiTime

Xiaomi's automotive division has released its 36th Q&A session, tackling various user concerns and questions surrounding the SU7 model. The Chinese tech

xiaomitime.com

🚓🚗🚕🚔 🛻🚖🚙🚘🏎️
[Magisk] RubberGooseGuy:
I can no longer pass device integrity.

{
"accountDetails": {
"appLicensingVerdict": "UNEVALUATED"
},
"appIntegrity": {
"appRecognitionVerdict": "UNRECOGNIZED_VERSION",
"certificateSha256Digest": [
"sa9mHiX8Y4dxrkBF81QtSkedJ4ghVjxLbaGd2MBXdoQ"
],
"packageName": "com.henrikherzig.playintegritychecker",
"versionCode": "7"
},
"deviceIntegrity": {
"deviceRecognitionVerdict": [
"MEETS_BASIC_INTEGRITY"
]
},
"requestDetails": {
"nonce": "VFNWWGF3SXBhUWliUUY1cmJzREU1OFNFVTd3RjRqdk5mZ2hNZmxmbHhqMVZwdFhEaDQ\u003d",
"requestPackageName": "com.henrikherzig.playintegritychecker",
"timestampMillis": 1714820582010
}
}
[Magisk] zgfg:
What phone, module, prints you use.

With the same you passed before, did you change/upgrade anything?

Did you try to reinstall PIF module and prints

Did you check logcat PIF prints
[Magisk] Vision:
@chiteroman can you change the Title of your TEE hacking thread, according to this ? or similar title you want

Post in thread '🔧 [MODULE] Play Integrity Fix (SafetyNet fix)' https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89486022
[Magisk] RubberGooseGuy:
I changed my rom.

I have tried Omosis forks as well as this one.

I had to reflash my firmware I don't think it should effect anything.

Im using a redmi note 12 4g
[Magisk] ashish1989:
Well this problem is now widespread, changed another rom and kernel on my android 8 device, using latest PIF Fork, Shamiko with custom griffin fingerprint, but only can pass basic integrity. I am also searching for solutions for many days, but couldn't find one
[Magisk] Vision:
Have you try to disabled others modules if exist, except the PIF? To see if pass again
[Magisk] RubberGooseGuy:
The only modules I have are pixelify, lsposed, Revanced Extended, xmlpak, Iconify and Systemless hosts but i had these before (except pixelify) and it was working fine.
[Magisk] Vision:
Maybe something, updated itself under the hood, I think you don't lose anything, disabled all and give it a try only PIF enable
[Magisk] RubberGooseGuy:
It actually worked do you have any idea what module could be causing it?

EDIT: it was xmlpak.
[Magisk] Vision:
I'm not sure, maybe the pixelify (you say not have it before) and if not is this, try one by one to see what cause the PIF not working properly.

EDIT: So the xmlpak, cause the problem, check if recently updated by itself, I think cause problem because change important stuff for have vendor app and this interaction somehow with PIF module.

View attachment 6099284
[Magisk] RubberGooseGuy:
xmlpak hasn't updated for 2 years all the other roms where on andriod 13 not 14 so it might have something to do with it.
[Magisk] Vision:
Oh yeah, on Android 14, lot changes
[Magisk] shuoyue:
I can't pass integrity check ,it works well before I update my system

my phone is oneplus 12,using colorOS 14 ,I'm using the latest playintegrityFix by Chiteroman and playcurl to dowoload the latest PIF

I try to reinstall the PIF module ,still not work
[Magisk] Lord Sithek:
I face the Play Integrity breakdown recently when I changed ROM on one of my devices. I couldn't pass PI with the previous setup, both PIFork with griifin print nor official PIF. What worked for me was to download latest autopif.sh, generate print once again and use it with PIFork v8. No idea what has changed or why it was failing before 🤔
[Magisk] zgfg:
With Cith module you don't need custom PIF - besides, it will be the same Griffin from Xiaomi.eu

Did you check with Osmosis Fork (but then you must use the custom PIF) - results might be slightly different, so worth to try

Does it correctly read prints - what do you have in logcat:

su -c killall com.google.android.gms.unstable

su -c logcat -c

< Test Play Integrity >

su -c logcat -d | grep PIF

For Fork you don't need to use that second module to take the prints, you can use the same Griffin prints from autopif or so, but use the full-blown Json file as attached (you can use that - the attached file also extends logcat with "verboseLogs": "100")
[Magisk] Spartacus500:
I try new version Play integrity fix but not working integrity devices 😔 & also test framework.jar path & this same not working 🤷
[Magisk] Vision:
For more info about frameworkpatch and to share info write here if you can

TEE hacking

Post about hacking TEE on Android devices. I will post here some useful resources: https://github.com/chiteroman/Reprogram-TEE-on-Qualcomm-devices https://github.com/chiteroman/FrameworkPatch And leaked keyboxes...

xdaforums.com
[Magisk] ashish1989:
Done all steps as mentioned, still passing basic integrity only
[Magisk] Nergal di Cuthah:
What kernel
[Magisk] ashish1989:
Oxygen Kernel
[Magisk] zgfg:
What about the mentioned logcat?
[Magisk] ashish1989:
Where can I find it?
[Magisk] westruk:
su -c killall com.google.android.gms.unstable

su -c logcat -c

< Test Play Integrity >

su -c logcat -d | grep PIF
[Magisk] ashish1989:
Already done this, I am asking about the logcat location
[Magisk] zgfg:
Commands for logcat were in my post you quoted when you said you did everything I mentioned

You need to have Terminal Emulator installed and root granted to TE. Google about using Terminal Emulator if needed. And if not familiar with using TE, please DO NOT use Termux - usually, novice users have troubles to install. There are other TE apps on Playstore

You could also use ADB, in that case for every xommand I mentioned:

su - c ...

use instead

adb shell su -c ...
[Magisk] ashish1989:
Bro I have used all the commands which you have mentioned earlier. I am asking about the logcat directory i.e. where it is saved?
[Magisk] zgfg:
last command logcat -d displays logcat to the TE screen (like on the screenshot). Then select all, copy/paste:

Spoiler content hidden.

You could also dump directly to file, eg logcat.txt on Inrernal memory, Download by appending the last xommand like:

... logcat -d ... > /sdcard/Download/logcat.txt
[Magisk] osm0sis:
What's the release string?

uname -r
[Magisk] ashish1989:
3.18.138-Oxygen-Kernel-v6.0.138
[Magisk] chiteroman:
Flash stock kernel and try again, maybe that string is banned 🤔
[Magisk] osm0sis:
I'll check it later today if nobody gets to it first. 👍
[Magisk] ashish1989:
Spoiler content hidden.
[Magisk] Vision:
@ashish1989

Maybe is simply, like the problem the others users had, have you try disabled all other modules (if existing) except PIF?
[Magisk] zgfg:
Thanks. PIF Logcat looks ok, 19 Griffin fields read from JSon and injected.

From "Couldn't determine '_COMMENT' class name" I see you indeed used the JSon I attached you earlier :)

Somebody will check your Kernel release string

As suggested, disable all other modules and reboot, test with only Zygisk, DenyList (not enforced), Shamiko and this PIF

Btw, from the log, your phone was Samsung, on7xelte with A 8.1.0 ROM - haven't you previously asked (here or in another thread) also for PIF, for the same phone or was that then an older, A7 phone
[Magisk] Vision:
Yeah, you have right, we try to help and have discussion about this again lot pages ago, and still not pass.

A7 had old xposed and for this cause problem with PIF as i remember.
[Magisk] intel_core_i7:
Troubleshooting playback issues in YouTube and YouTube Music · ReVanced revanced-discussions · Discussion #1037

Setup ImportantIf you have recently started to experience playback issues, you may have been put in an A/B bucket by YouTube, for which the following troubleshooting steps will not work. The issue ...

github.com

Bringing up this question once more since the previous has details removed due to reddit link contains swearing comments, and this issue is popping up for some recently.

Is SN/PI actually required for YouTube playback (in this case Revanced) to work? Seems like it was some sort of coincidence when someone fixed the issue after installing some sort of PI fix module, because there's no way this can become a thing. Another forum (won't tell since it may violate xda rules) saying disabling PI spoof in MicroG settings and few more options may fix the playback issue.

The head developer in my opinion have no clue and just draw to conclusions too quickly.
[Magisk] ashish1989:
It was my other phone with android 7.

Except shamiko, PIF, I have Zygisk-Lsposed module only on my android 8.1 device
[Magisk] zgfg:
Ok, does Shamiko correctly report (in the Magisk Module page): "Shamiko is working as blacklist mode..."?

LSPosed per-se shouldn't cause a problem but certain LSPosed modules can spoil PI (like the infamous LP whose full-name is prohibited to mention here)- so which LSPosed modules do you have installed?
[Magisk] ashish1989:
Yes

Bootloader spoofer and XinternalSD
[Magisk] beeshyams:
I saw in some Tg that this hides Revanced. I didn't try as I use Rex YT and that doesn't have any problem
[Magisk] zgfg:
BootloaderSpoofer should not affect - but you must not spoof GSM/DG but only KeyAttestation app (and some 'banking' apps - if they really need.).

IMO, IDK do you really need the Spoofer - only if you really enjoy looking in KeyAttestation app to see that your BL is 'locked'

Frankly, I don't know about XinternalSD (btw, do you really need on A8 - if you really have low Storage but it could also slow down, etc)

Anyway, I'd suggest to disable them, reboot and test again - to make sure they don't interfere. Btw, that's general how-to-help DIY approach:

- Disable all other modules and retest. If that would help, enable one by one to find the culprit

- Reinstall PIF and prints, inspect logs (done in your case)

- If things stop working, check what was lately changed or upgraded and maybe try to revert ToDo: Your kernel ID to be inspected and you may test with the stock Kernel (Kernel only - it must not not affect Magisk/root)
[Magisk] ashish1989:
I have not spoofed GMS with it

I only have 16GB internal memory, that's why I need XinternalSD xposed module. I want to try Apps2SD to format my external SD card to work as internal, but I couldn't find any working tutorial to do it with ease, so that I can get rid of the Xposed module
[Magisk] osm0sis:
I hope you mean LSPosed, because I don't know how many times we've told you Xposed triggers a verdict fail and there's no way to make Xposed work with a PIF module...
[Magisk] Vision:
At least have you try disabled to see if PIF working? just for test and after enabled again
[Magisk] osm0sis:
He can't. It'll break his installed apps.
[Magisk] Vision:
Yeah, unfortunately the only way to test it, if PIF working is this.

I had some similar in my older Android 7, and i did the same just to test it, i know is time consuming and need data transef, but at least i found what cause the problem
[Magisk] ashish1989:
Ya, its Lsposed

Will try
[Magisk] intel_core_i7:
Then the SN requirement seemingly still a myth. I wish someone will do the mythbusting job, but after 2 posts it seems like nobody is really interested into it
[Magisk] osm0sis:
I tried Oxygen, Kernel, Oxygen-Kernel and v6 and none of it is banned, so something else is the problem with the device setup here.
[Magisk] zgfg:
Sorry, I don't recall now (and too much to search back now). Did you previously ask for spoofing PI with MicroG, ie, without GMS

If so, then it makes sense. But if you have GApps, and supposedly you do have root, then why don't simply use RV root (without MicroG) and you'd have no troubles with SN or PIF due caused by RV (I use RV root, actually still a few months old RVX module - since it stopped updating, it still works fine, no buffering or other troubles I read users now complain) and over a year or so I never had any problem with SN/PI due to RVX YT or RVX YT Music
[Magisk] neonblind:
well, there is no reason to use pif in android 7 or below. just good old magisk v23 and hide gms. done. it still works and pass device intergrity with an old BQ Aquaris M4.5 with stock android 6 and a Sony X Compact with stock android 7 as i'm writing this.

and for @ashish1989 and his android 8.1 device. he don't need to disable anything. it wont pass. my lenovo tab with stock 8.1 don't pass device intergrity since months, except that one week where google decide to whitelist the griffin print for A8, 8.1 and A9 devices.

🔧 [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
[Magisk] ashish1989:
You are absolutely right, for android 8, 8.1 and 9.0 there are some issues which nobody can rectify it until now
[Magisk] Vision:
Yeah, right.

Useful info.

Thank you.

So it seems can't pass whatever he try 😕

EDIT: The first safety net had support for Android 7

View attachment 6100029View attachment 6100030
[Magisk] zgfg:
Interesting but do we have more users with A8-9 here to confirm
[Magisk] neonblind:
lets highlight the 2 i know :)

@miXOnIN

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

@maxim.a.petrov

🔧 [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
[Magisk] osm0sis:
Is it only the griffin print that is restricted on older Android? Last time I tested on my OnePlus devices (~Mar 22) I was able to get stock OOS passing with only the shell scripts, hence me reimplementing (and improving!) USNF's Scripts-Only Mode for the next PIFork release:
[Magisk] zgfg:
Are you planning to release. with scripts-only-mode (seeing fresh scripting commits today)

Spoiler content hidden.
[Magisk] osm0sis:
Well yeah, I said "next PIFork release", didn't I? 😛

Check the PM.
[Magisk] zgfg:
https://www.pinterest.com/pin/i-lov...ay-teacher-gift-pie-fork--149463281366869536/
[Magisk] intel_core_i7:
The PI spoofing in MicroG was in the revanced tutorial in the github issue that I left here. I asked if PI was really required for playback to work because I currently don't have any Keymaster 3+ devices with OEM Unlocking option, so probably my bad for not disclosing this beforehand. I use official Revanced, but not on the latest version of both the Youtube and MicroG (Revanced GMScore) app and don't have the playback issue, couldn't really help that my devices are on stock rom and locked.

After seeing you and @beeshyams using some sort of revanced fork and doesn't have any playback issue around a week till now, I would probably say it's because of something else going wrong within official Revanced's microG implementation
[Magisk] LAwLB15:
I'm on LGV20 Android 8.0.0 magisk 24.3 and yes I haven't been able to pass device integrity since march now no matter what I try. Last time it did work it worked for about a week then stopped.
[Magisk] pndwal:
If stock ROM, try this:

Uninstall any USNF/PIF solution.

Install Shamiko (disable DenyList; Shamiko will use the list as a Hidelist)...

Add com.google.android.gms.unstable (DroidGuard/attestation) GMS (Google Play Services) process to DenyList...

If custom ROM try the same, but if not working please say which ROM... You may simply need to spoof a matching fingerprint/security patch date combo if it has recent security patches...

Let us know if it works. 🤠 PW
[Magisk] LAwLB15:
I'm on stock rom

Can’t install Shamiko as it only works with Magisk v26

I have Magisk 24.3

Is there any way to install Shamiko with Magisk v24.3 or is it possible to get Magisk v26 on Android 8 without bootlooping?
[Magisk] shuoyue:
Hey ,I check the Fork version and use the attachment, but still the same result: can't pass integrity check.

logcat info in attachment, I don't know if it's because I updated the Security Path, because before that everything was fine

Maybe some useful info:

uname -r

6.1.57-android14-11-o-g55db199191cb
[Magisk] Vision:
If you can try this, maybe no bootloop https://github.com/HuskyDG/magisk-files

Have Magiskhide and zygisk, and no need shamiko, or you can try a old version of shamiko, to just see if work

https://github.com/LSPosed/LSPosed.github.io/releases/download/shamiko-126/Shamiko-v0.6-126-release.zip

I think this version need v24.2+ (24200+)
[Magisk] pndwal:
Looks like you can try Shamiko 0.6...

Recommend updating Magisk however... Which have you tried?... Please say why Magisk 27.0 or 27002 might not work or might bootloop in your device... If experienced bootloops, have you tried upgrading after disabling all modules?... Tried patching unpatched (stock) boot.img (rather than direct install to upgrade... Some previous Magisk iterations have been incompatible with refactored injection methods or functions meaning that direct install won't work)... 🤠 PW
[Magisk] zgfg:
Do you have stock Kernel (on your stock ROM) - hence no Kernel issue

PIF log looks ok.

Your ROM is A14 (hence not the case like for the users with A9 or earlier), I think that Osm0sis (successfully) tested on OnePlus A14 like yours (check his posts?)
[Magisk] zgfg:
You and others on A9 or earlier - have you tried with the latest Osm0sis Action builds (GitHub acc required - since not released yet), Scripts only mode..

(Mine is A13, cannot test)
[Magisk] LAwLB15:
Managed to get Magisk 27.0 installed (actually surprised it worked because the other versions after 24.3 was causing bootloops)

Tried to install Shamiko but it failed… says that it can only be installed with Android 8.1+ (i'm on 8.0 which is the latest stock rom for the LG V20)
[Magisk] osm0sis:
Try with my latest PIFork Actions build (GitHub account required to see the zip), install the zip, reboot, run su -c touch /data/adb/modules/playintegrityfix/scripts-only-mode then reflash the zip and reboot again.
[Magisk] ashish1989:
Yes, I have tested it, and currently on the same, but still same, can not pass device integrity

I also have added gms and gms unstable processes in denylist.
[Magisk] ashish1989:
Have done this too now, still passing basic integrity only. Module is now working in scripts only mode

Cleared play store and services data too and rebooted, still same result
[Magisk] osm0sis:
I was going to wait a little longer while we tested it more internally, but since everyone here already seems to be testing it out anyway...

#219 #221 #222 #223 is the new PIFork v9 Release Candidate! Especially needs some attention from those using stock ROMs Android 9 and less for my reimplemented/improved USNF Scripts-Only Mode, activated by su -c touch /data/adb/modules/playintegrityfix/scripts-only-mode and reflashing the module zip (after the module was previously fully installed). You should also Enforce DenyList with Scripts-Only Mode if not also using Shamiko. It was tested and working on my OnePlus 5 on Android 7-9.

There have also been a number of migrate script improvements, and this officially adds my updated autopif.sh and killgms.sh scripts to make it easier for people to get up and running though there's intentionally still no pif.json in my fork by default.

Note: If upgrading from cross-fork (i.e. chit's PIF), and not using Scripts-Only Mode, see the section of the README here: https://github.com/osm0sis/PlayIntegrityFork/blob/main/README.md#about-custompifjson-file

Commit diff log:

https://github.com/osm0sis/PlayIntegrityFork/compare/v8...main

Build (GitHub account required): https://github.com/osm0sis/PlayIntegrityFork/actions/runs/9145817676
[Magisk] zgfg:
What about a faster/easier switch between scripts-only and full mode - by use of the JSON file field.

For A8.1 and up - Magisk must allow Zygisk to run the PIF native part and read custom.pif.json (and user will need to use Shamiko as with the full JSON mode)

I just tested with an 'empty' custom.pif.json file:

{
// Advanced fields
"verboseLogs": "4"
}

As expected, there was no spoofing except:

PIF/Java: Spoof KeyStoreSpi and Provider done!

PIF/Native: [sys.usb.state]: mtp,adb -> mtp

Spoiler content hidden.

So what if custom.pif.json would support an additional Advanced field like:

"disableSpoofs": "yes"

to suppress (if it still makes a difference when there are no further spoofs):

PIF/Java: Spoof KeyStoreSpi and Provider

MTP spoofing shall remain as useful anyway (similar to the script spoofs)

PIF/Native: [sys.usb.state]: mtp,adb -> mtp

I suppose, there should be no harm of DEX and SO just being left
[Magisk] osm0sis:
No.. there is by definition no Zygisk requirement nor Zygisk components and thus no field processing for Scripts-Only Mode. No point in complicating that part further or increasing the requirements. It's an advanced opt-in only feature for older stock ROMs.