yashsingh1/xdaforums huggingface dataset:
[Magisk] badabing2003:
Provide support file on PixelFlasher thread, and I'll take a look.

I suspect you haven't granted root access to shell.

And that Dropbox is the list of saved favorites.

You haven't saved anything yet.
[Magisk] Isa Daud:
Can I still get a device is certified if I use a a old custom ROM (android 12 below) whose kernel does not meet the requirements imposed by Google?
[Magisk] zgfg:
Meet Device Integrity (modules here) and you should get Device is certtified
[Magisk] Isa Daud:
Some say that in order for it to work, it needs a kernel that adapts the new algorithm in naming.

When I tried the MatrixX Android 14 ROM, Afterlife Android 13... the information still showed Device not certified.

After I replaced it with a kernel that had adapted the latest algorithm, then everything could run according to its function.

Then what about old custom ROMs whose kernels clearly don't follow Google's new algorithm? I want to use a custom Android 11 ROM. I doubt I can get a certified device.
[Magisk] zgfg:
It's not 'algirithm' but Google, by names, look for custom kernels

Anyway, kernels can be repacked and renamed (instructions in this thread)
[Magisk] Isa Daud:
So, can you be sure that using just any kernel i can get a certified device by installing this Play Integrity Fix module?

Previously I only used this module for Matrixx and Afterlife, but the device was not certified, Until I changed the kernel to support this.
[Magisk] :
If you meet basic attestation and your kernel string is not blacklistet or you can change the kernel name by extracting, renaming and repacking, you should succeed. See the top liked post below.

And if the current xiaomi fngerprint is still working. 😉
[Magisk] osm0sis:
What device do you have these ROMs for? I'd like to check their kernels to make sure there aren't any banned strings.
[Magisk] Vision:
Here we again 😂🤣

Probably is old news

Edit: too bad is old news

View attachment 6072955
[Magisk] :
(banned fingerprints)

user-, test- or release-keys?
[Magisk] Vision:
Xiaomi Poco X3 NFC (fresh flash A11)

Before unlock BL, test and pass 3/3

Official ROM (As i know) I extract from ROM the build.prop from system folder, i check inside and say this ro.build.keys=test-keys

The irony is, if I hadn't unlocked it the BL and pass 3/3, the some apps still work?

I have read some apps refusing to work if detect test-keys regardless of whether I passed 3/3
[Magisk] zgfg:
release keys

As I said, I tested them 2,5 months ago and already filtered out only those that were passing Device Integrity (and ten days ago I was only retesting from those)

So how would they pass Device Integrity previously with test keys?!
[Magisk] Nergal di Cuthah:
Why did you say exactly the same you did above. I thought i had deja vu
[Magisk] Vision:
Sorry, I thought I had deleted it
[Magisk] intel_core_i7:
They were probably the first to mass implement that strong bug using pixel 2's props
[Magisk] Legitsu:
is it possible to repalce the uname binary to spoof the kernel build name/string?
[Magisk] osm0sis:
Doesn't work like that at all. It's a syscall and we haven't found a way to hijack it.

Read everything here:

Some kernel strings are blocked by Goolag · Issue #236 · chiteroman/PlayIntegrityFix

For example Sultan kernel on Pixel 7/Pro/a is blocked from Goolag since it has a string named Sultan in it. They are checking for blocked words (case insensitive) in the uname kernel string, so I w...

github.com
[Magisk] Legitsu:
reading though the thread it does indeed look like droidguard has its own syscall wrapper..

blarggg

what a stupid waste of time by google I wish they would stop being so dam hostile using 'security` as an excuse is getting old ... even for that tired old horse trick
[Magisk] Isa Daud:
seem the hardest part for me to do it because my limitation regarding it. will look into your advice.

hi,, thanks for response my question. i used Mi A2 Lite, and plan to use older custom rom base on android 9,10 or android 11. i never confuse for android 13 or 14, because there are already kernel that already work to get certified device. just worried for older custom rom as i mention above. thanks in advanced.
[Magisk] Vision:
Yeah, so is old news, too bad
[Magisk] intel_core_i7:
That was long ago
[Magisk] osm0sis:
I don't see Matrixx or Afterlife for Mi A2 Lite (daisy) anywhere. Links?
[Magisk] Vision:
Yeah, now see it, too bad
[Magisk] ablak44:
Google Payments has stopped working. I always used Play integrity fix, next. The Google Store app is not certified. The test in the integrity application is successful. (meets device, meets basic). What needs to be done to fix this? OnePlus 11 oos14.0.501.
[Magisk] Captain_Throwback:
Clear Play Store data.
[Magisk] Umgak:
Both appear to be available from the jazzaosp repo on SourceForge.

AOSP - Browse /daisy at SourceForge.net

sourceforge.net

EDIT:

AfterLife is using lineage kernel.

4.9.337-lineageos+

Matrixx should be fine though.

4.9.337-perf-g742a6fa7e89d
[Magisk] ablak44:
I cleared the data of the store, Google services, Google wallet, etc. Also added to the profit list, as always. I have done this many times successfully. But now Service framework is unchecked in the list. I select it and after a while it is deselected again.
[Magisk] Umgak:
The module automatically removes them from the list because otherwise the module would break. Please leave them unchecked, it is normal. For older methods, such as MagiskHide Props Config, this was a requirement since those modules worked via a different method, but PlayIntegrityFix will handle all hiding necessary by itself while it also spoofs the values we need to pass integrity.

@osm0sis may be worth adding to the FAQ regarding DenyList not being required, since this question is asked all the time.
[Magisk] dmenezes:
What capabilities exactly go missing in Uber Rider with an unlocked bootloader?

I ask because my bootloader is unlocked, I've done nothing to hide that, and I use Uber Rider and haven't noticed any missing functionality.
[Magisk] ablak44:
The store already has the certificate, but the payment is still not going through. I don't know what else I can do.....
[Magisk] Captain_Throwback:
Contact your bank, probably. If you have Device integrity and Play Store is certified, and Wallet shows as ready to Tap and Pay, then Play Integrity isn't your problem.
[Magisk] ablak44:
The wallet shows that the device does not meet security requirements. The banking application is not a problem because I can pay with BLIK contactless.
[Magisk] CZ.Kostra:
If the Google store says the device is certified, then just give Google Wallet time. Sometimes it takes a while to fix security requirements.
[Magisk] dmenezes:
Thank you for that! Must be the most complete overview of Android Security I've ever seen.
[Magisk] dmenezes:
That's the kind of thing that keeps me coming back to this thread... TIL! 😆🤪😁
[Magisk] zgfg:
uname is just an utility (provided on Android by toybox) that collects and prints some info (and not only about the kernel) about your system.

Run

uname -a

or

uname --help

There are other ways to read the Kernel info, like

cat /proc/version

Instead of cat you can use other similar utilities:

head

tail

or

less,

so eg:

head /proc/version

For less you will need BusyBox

(For Terminal Emulator use su, for ADB use adb shell su)
[Magisk] osm0sis:
Hmm, I guess, but I intentionally include enabling it (without GMS on it, and if not using Shamiko) in my instructions since it usually helps overall. I guess I can clarify the GMS part further.

Here's what I said last time it was talked about here:

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

Edit: Added it here for now: https://github.com/osm0sis/PlayIntegrityFork/blob/main/README.md#troubleshooting
[Magisk] Vision:
The irony is, in the official document for android from Google say this 2 things

1. Trusty is isolated from the rest of the system by both hardware and software. Trusty and Android run parallel to each other.

2. There are many other uses for a TEE such as mobile payments, secure banking, multi-factor authentication, device reset protection, replay-protected persistent storage, secure PIN and fingerprint processing, and even malware detection.

If TEE work parallel why not we unlock BL and have root and same time a secure environment like the document say ?!

View attachment 6073399

View attachment 6073400
[Magisk] zgfg:
The point is that when you kick DroidGuard to attest Strong Integrity, then TEE ('in parallel' with, 'independently of' - whatever we call) finds from the ALREADY (usually days or months ago) modified system files that the system WAS affected (that BL was unlocked, that custom ROM was flashed, that Magisk was patched, you name it)

And since it works 'in parallel' to Android, you cannot spoof the Strong Integrity (on TEE) from the (rooted) System
[Magisk] Vision:
Yeah exacly, if Android is so good that they say, why not let have unlock BL with root (or without root) and mod and TEE protect as in paralles from malware and theft of bank info

Or at least let us pass 2/3 without need some modules
[Magisk] zgfg:
Don't understand what you're saying

Anyway, TEE with its operating system provides only a limited number of built-in routines, services or 'apps" (biometry, etc). You cannot install your own 'apps' to TEE (you cannot nodify anything on TEE - if modifiable it wouldn't be trustworthy anymore).

You just use the Andrioid API that calls the given service from TEE and provides the results back

That much from my side (I will not continue debating about)
[Magisk] Vision:
Thanks for extra info, i appreciate
[Magisk] HippoMan:
What happens for me under Uber Ride is that when it first starts up, the screen flashes after a couple seconds, and I then get a very basic white screen which only offers the ability to request a ride.

Then, once I specify the data about the ride, I can indeed obtain the ride. However, on this low-functionality screen, I am not able to alter the ride, for example, to add another stop. I can only cancel the ride at that point.

I figured out a hacky way to get around this problem, however.

I use Tasker, and I created a task that does the following:

(1) Launch the Uber Ride app.

(2) Immediately kill the Uber Ride app.

(3) Run this in a root shell: /system/bin/pm clear --cache-only com.ubercab

This clears the Uber Ride cache

(4) Re-launch the Uber Ride app.

This then causes Uber Ride to come up normally with all features and capabilities enabled.

Tasker allows its tasks to be exported as normal apps, and so I did that with this task and changed its desktop icon to be the same as the standard Uber Ride icon, and I named it "StartUber". Now, I just run StartUber whenever I want to use Uber Ride.

Also, if when the Uber Ride app is running I go into one or more other apps, and if I then go to "Recents" and select Uber Ride again, it returns with the basic, low-functionality white screen, but with my current ride still active. In this case, I need to re-run that "StartUber" app that I created in order to get back to a fully capable Uber Ride app which also shows my current ride as still being active.

PS: I'm running stock A13 on a Nothing 2 device which is using Magisk Alpha 27001. I got this same behavior on this same device and OS under earlier Alpha versions, and also under recent TJW versions, and also under recent Kitsune versions.
[Magisk] Isa Daud:
Both are unofficial, now matrixx latest version for Daisy already device certified.

Now i used it. But i plan to use older android (maybe android 10/11), most of the status is Device not certified (such like havoc os by lupe, crdroid etc).

Unfortunately i didn't a coder who able to modify the kernel.
[Magisk] jrotaetxe:
Perhaps a little bit off topic, but think is the best place to ask...

I have a Xiaomi 10T Pro, on stock Fw, rooted and exposed. I value a lot the Wallet functionality (toghether with being rooted), thanks to Chiteroman and Osmosis (and others).I am keeping the whole set, but my safety patch is becoming old...

Could any of you adivice me a good custom with no kernel issues for my Xiaomi?

Thank you in advance
[Magisk] Isa Daud:
Yes, Latest matrixx's kernel has fixed with pif requirements. but no for Afterlife. I never confuse for latest android base giovani tree, because there's kernel dev who build kernel that support certified device.

I just curious for older android rom.
[Magisk] zgfg:
Sorry, but what do you mean by "old safetypatch" - do you pass Device Integrity or not?

You are ask for "good" but what - just Kernel or ROM?

You can consider Xiaomi eu custom ROM - it's not AOSP but customized MIUI
[Magisk] jrotaetxe:
Hi, zgfg

Looking for a custom ROM with a Kernel with no issues (so far) with PI.

Old, in my case is June 2023, the last (and final) update from Xiaomi. I am afraid Xiaomi EU ROM comes with the same patch, provided they use the Global ROM as the base from their work.

I am passing 2/3 using Osmosis fork, so I keep my wallet and all my other hobbies, but think the moment to migrate to a custom ROM is coming.

Thank you for your kind response
[Magisk] zgfg:
With Xiaomi.eu you can either use their injector - hence no Magisk, no PIF

or you disable their injector and use Magisk+PIF

Both PI Fix and Fork will automatically disable Xiaomi.eu injector, and there are no other issues since Xiaomi.eu uses the official Xiaomi stock kernel names that are not banned

(I have Xiaomi.eu ROM with disabled injector and I'm using the PI Fork, albeit not the latest version but it should not matter)

Since I don't have your 10T Pro, I don't know what exact version Xiaomi.eu provides for your device and with what Security Patch (mine, for Mi 11 Lite 5G NE, alao EOL device is Nov 2023).

You can check on their Forum:

MIUI 14 - MIUI 14 STABLE RELEASE

Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...

xiaomi.eu
[Magisk] osm0sis:
Nah, chit's disabling is still broken, despite us telling him repeatedly why. Mine is well tested and works correctly on Xiaomi.eu from latest v7. :)
[Magisk] osm0sis:
Anybody in here on a ROM that has a /system_ext/overlay/config directory? If so, can you show me the contents of /system_ext/overlay and /system_ext/overlay/config (if it also exists) as well as the contents of any config.xml inside?
[Magisk] zgfg:
Mine has only /vendor and /product overlay folders and without the config
[Magisk] Vision:
Exactly the same, except more apps in /vendor/overlay
[Magisk] Vision:
What supposed must have this file inside? I have Xiaomi Poco X3 NFC with A11 (before A10,A12) and no one of 3 ROM have this config.xml inside
[Magisk] osm0sis:
Like I said, I'm interested to know how many ROMs have it and what's in there. If you don't it doesn't mean anything.
[Magisk] Vision:
Understand. Thanks for info
[Magisk] Some_Random_Username:
It doesn't exist on my devices (two running Android 14 and one running Android 11), but an exact match search for the first directory you named shows it exists in system/system/ of an Android 14 GSI build that was dumped on a famous website on July 2023.
[Magisk] osm0sis:
Ah, thanks for that! This definitely suggests it'll exist more places, for varying uses, so I've reverted hiding that config.xml and will have to come up with a more precise way to tackle ROM PI injector apks which use the overlay method. 🙌
[Magisk] ph03n!x:
This is with Oxygen OS 14, no config underneath though -

View attachment 6073924
[Magisk] dknight178:
Hi all. If I have my custom PIF, where should I place it after installing the latest version? Thanks
[Magisk] Saviolo:
I got the same problem as Shadowillusion on Samsung S20 FE.

Device and Basic Integrity are fine but some apps are triggering.

Magisk 26300

Play Integrity Fix 9.6

Shamiko 0.7.3

Android G780FXXSDFWI3 (API 33)

Using TB Checker only fail strong integrity and virtual integrity.

Before 9.6 same apps weren't triggered and falling back to 9.5 won't solve. Apps weren't updated or anything.

Spoiler content hidden.
[Magisk] tryigitx:
Latest version is good enough and everything works

The problem experienced by other people may probably be due to magisk and shamiko incompatibilities
[Magisk] shadowillusion:
Upon further testing on MIUI and PlayIntegrityFix 9.3, looks like following prop is being detected:

ro.boot.verifiedbootstate orange >> green

ro.boot.vbmeta.device_state unlocked >> locked

ro.boot.flash.locked 0 >> 1

If it is set as orange/locked/0, bank apps and Minotaur NativeTest will run normal without detection. But PlayIntegrity will fail.

If it is set as green/unlocked/1, bank apps will say it detects root and minotaur NativeTest will say "Property Modified". But PlayIntegrity passed.

This is on MIUI, it might behave different on AOSP/Realme/Oneplus.

Is it possible to modify prop only for certain apps like gms and fingerprint? I wish there is DR-TSNG/HideMyApps for properties variable.
[Magisk] chiteroman:
You give me an idea...

Yes, you can modify source code of my module to get that.
[Magisk] shadowillusion:
IMO, using just latest Alpha+Shamiko+Zygisk or Delta+Unmount+ZygiskOnKernelSU should be sufficed enough to bypass MOST bank app that tries to detect Zygisk.

If those app tries to detect app name, we can load LSPosed+HMA and most likely will still not get detected since Zygisk is already well hidden (with latest NativeBridge or fuse+ptrace).

The problem is that some apps is also trying to detect PlayIntegrity state AND watching some sensitive props being changed. This might be different with each brand (also if they used Displax/chiteroman module), which explains why some people in forum able to pass PlayIntegrity and bank app while other people does not.
[Magisk] chiteroman:
Check v9.7 prerelease and its changelog (updated again)

Release v9.7 · chiteroman/PlayIntegrityFix

All files that modify system properties have been removed. This is because each OEM makes a different Android system and uses the system properties in different ways, however as long as you have SE...

github.com
[Magisk] FluffyPants:
Works good
[Magisk] magaedy:
Still based on Shadowhook ?
[Magisk] chiteroman:
Using v9.7 (no Shamiko) I can open Starling bank app without issues.

But when I install Shamiko, Starling start detecting resetprop utility and "Your device hasn't passed our security checks" :(
[Magisk] chiteroman:
Yes, I can't use Dobby anymore due detection issues.
[Magisk] magaedy:
I'm using v9.2 and no detection issues for me, I think v9.2 is based on Dobby, Right ?
[Magisk] osm0sis:
I think some people need to remember that it's only for passing Play Integrity, not hiding root.
[Magisk] Lione2:
Its maybe not a lot but with 9.7 i dont have meets intégrity anymore ( pixel 7 Android 14 )

View attachment 6024125
[Magisk] shadowillusion:
I saw in 9.7 service.sh is discarded, that might be reason why @Lione2 no longer pass PlayIntegrity
[Magisk] Lione2:
For information, it was good on 9.6
[Magisk] osm0sis:
Best would be to figure out what specifically is needed, and only add back necessary items as they are found now.
[Magisk] boualemdz:
I Need help for uber driver
[Magisk] shadowillusion:
Newest zygisk have deployed new method of hiding to not trigger root detection.

However safetynet-fix and PlayIntegrity fix both deploys properties which triggers root detection.

While I understand that this module only aim to bypass PlayIntegrity status, the status itself does not convey its only true purpose.

I mean, think about it: in alternate reality if no app is checking Play Integrity status, then we would not be pursuing to bypass this status, and no module of this kind shall exist.

My point is that the true goal is so that those apps which checks the PlayIntegrity status should be able to be launched.

However, some of these apps not only checks PlayIntegrity status. They also checks for sensitive properties for signs of unlocked/rooted device.

Since this is mouse&cats game, more apps in the future might likely gets an update to do both checks. If this module only do one thing while neglecting the others, there is a chance that any safetynet/playintegrity fix might lose its true purpose. (I sincerely hope that it does not happen). At least it should not deploy sensitive props which triggers detection.

Sorry if what I say is wrong, I was just conveying my opinion. I know that it looks like I am asking too much. I can only say Thank you for the good work @chiteroman, really appreciate it.
[Magisk] osm0sis:
My point was this module is specifically for Play Integrity, and Shamiko is specifically for hiding root. Use what you need for what you need, be it one, the other, or both. I use both.
[Magisk] CZ.Kostra:
For PIFix from @chiteroman : /data/adb/pif.json

For PIFork from @osm0sis : /data/adb/playintegrityfix/custom.pif.json

A different JSON format is needed for each module. The migration script 'migrate.sh' is part of PIFork.
[Magisk] Antonio200:
Good morning. Probably silly question... How can I install osm0sis' module over chiteroman's one? I have several pif.json files tested and working, can I use the migrate script or it'll overwrite the existing custom.pif.json?

Thank you in advance
[Magisk] CZ.Kostra:
Rename 'pif.json' to 'custom.pif.json' and copy it to the module directory. Install PIFork via PIFix. During installation, a migration is performed and a BAK is created with the original data.
[Magisk] dknight178:
Thanks
[Magisk] zgfg:
It depends do you use PI Fix or PI Fork

Both have instructions on tgeir GitHub repos

Also, find and ead the FAQ post
[Magisk] zgfg:
Generally (to understand how things wirk), find and read the FAQ post
[Magisk] Antonio200:
I did, but I'm a final user, I'm afraid I didn't understand most of it. I have also read all the wikis and instructions references in github, but even then it wasn't clear to me if I could install one module over the other, tried to avoid breaking something that works for me...
[Magisk] osm0sis:
Says it pretty plainly right here:

GitHub - osm0sis/PlayIntegrityFork: Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com

Specifically:

(y)
[Magisk] Antonio200:
Maybe it's because I'm not a native English speaker. For me "upgrade" is not the same as change from one fork to the other (I see, "cross-fork"; ok, new word for me). In any case it was enought with CZ.Kostra's answer. By the way, thank you CZ.Kostra.
[Magisk] osm0sis:
It says upgrade because that suggests you're installing it overtop the old module via Magisk app. :)
[Magisk] MajicDroidPirate:
Any chance antone has a link to the fp_downloader apk thar used to be on github? It vanished and i cant find it anywhwhere
[Magisk] varunpilankar:
I'm on lineage 19.1, earlier I was able to pass safety net but not anymore.. How to pass it again? Help is appreciated. Thank you!
[Magisk] FrogMaster-:
Likely there was a built in fingerprint which has been banned. You'll want to review the information in this thread which will teach you how to source a new fingprint.

Take a look at the second most liked post

🔧 [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] rockman_x:
its now integrated in the magisk module... its either flash the module or extract the zip file to get the apk.

or if you have termux installed, switch to superuser then type fp
[Magisk] LuisNara28:
So chiteroman PIF is not working anymore?