yashsingh1/xdaforums huggingface dataset:
[Android Software Development] CalYorBro:
Yeah I don't think it is the official one. This is the fork I'm using:

hotdogb

If that's the official build most people might not even use microG. The whole point of Lineage OS (and also the reason I first switched) is to get rid of Google. Sadly the apps I needed don't work without some sort of it so here I am.

How do I configure that? The only good guide was for a Nexus phone and they had some settings I didn't have.

Yes I can try something like that. How should I configure the denylist and should it be on or of?
[Android Software Development] pndwal:
Ok... At least looks up to date... Any discussion thread to check if Dev adds spoofing etc?

True

Well not really, though some would say to remove OEM bloat / provide more vanilla Android...

The original CyanogenMod (Team reformed as LineageOS) bundled all proprietary GApps, and Steve Kondik thought his baby was dead when Google issued their infamous Cease And Desist... However Google quickly clarified that although custom OS's could not legitimately bundle GApps (though many small-fry ROMs still do), users were welcome to 'sideload' the same (as devices themselves are generally certified through CTS while custom ROMs are not)...

So OpenGapps was formed to offer legitimised seperate packages, Steve continued with CM project, users continued to use vanilla CM (and later LOS) with proprietary Google Apps, and all in the custom mod world was sweet again...

I believe Google realised they nearly shot themselves in the foot with that action... At least they scrambled to offer a solution / compromise that wouldn't result in the death of CM / custom ROMs as we know them...

So initial efforts were actually very much to retain use of GApps w/ custom ROMs!...

De-Googling efforts are actually a later trend, and LOS with MicroG or Gaël Duval's /e/ OS are examples.

Yup, cos the're using Google Play Services S/N API!...

So you cannot fully de-Google to use most bank apps; at least a modified Play Services 'GMS core' is needed to provide banks requisite S/N attestation!

Read the OP in MagiskHide Props Config thread!... Or extract / read readme.md from within MHPC zip archive!...

MHPC pretty much does nothing unconfigured (it will reset sensitive props by default, but Universal SafetyNet Fix does that anyway).

Basically, install a Terminal emulator, type 'props', wait for initialisation, select from config options offered...

Don't add anything to denylist w/ USNF module active ... It will remove Play Services processes on boot if added anyway as it uses its own hiding...

Denylist should be enforced unless Shamiko module is active. This also does its own Zygisk based hiding but hijacks the list for convenience... PW
[Android Software Development] CalYorBro:
Have not really found anything updated myself.

And yes it's very much up to date with updates coming in every two weeks. It's even more updated than Oxygen OS on hotdogb

Well that is a lot of info but it's all irrelevant because I can't pass basic integrity

I tried this last time I tried to fix SN but it does not work untill i pass basic integrity

Shamiko is still the only thing that works, or at least works good enough. I tied turning everything off except for USNF and MHPC like you said, but it still fails. This method also makes my apps break again.
[Android Software Development] pndwal:
You asked "How do I configure that? The only good guide was for a Nexus..."

How is this irrelevant???

You originally asked for advice on how to pass S/N... It's relevant as you will need CTS profile match... Of course, you also need Basic Integrity...

Well why did you ask how to configure it then? ... 🤔

That was to test if you have any modules that are breaking Basic Integrity... It's not a 'method'!... I didn't mean for you to use app w/ this disabled, clearly... but Skamiko does NOTHING for SafetyNet passing (it hides traces of 'root' that bank apps may detect independently or S/N API) and can be disabled for troubleshooting S/N ...

You should pass S/N with nothing more than correct ROM settings (eg special options for MicroG), Zygisk on, USNF 2.2.1 (unless your ROM integrates this), MHPC w/ working fingerprint configured (unless your ROM spoofs one)...

It seems that if all this is in order, the issue is with the ROM / Kernel / MicroG implementation... I already suggested that you find discussion thread for your ROM and "post there for help getting it passing now on this ROM"... Even it's dev may not have tried... Who knows? PW
[Android Software Development] RAMBO29:
Hi Guys, Is there a way to stop 'play store' and its related processes from updating? I am aware of the potential security risks, so leave that aside. I tried using the blocker app and disabling every thread with 'update' under google play and framework. This worked for few weeks but now it doesn't. Also messes up with the safetynet too when updated. Any way to do it on a rooted phone?
[Android Software Development] zgfg:
Sorry, just deleted my 'answer' - I missed the topic
[Android Software Development] vandyman:
This thread is for the safety net module.

And how to use it to achieve safety net.

Your question is not related to this.

Try asking your questions in your device thread or the general Magisk thread.
[Android Software Development] RAMBO29:
I am not sure about this. I had all safetynet passed and NFC working and then one day playstore updated and it failed from then on. Hence asked. But will try Masgisk thread.
[Android Software Development] mohammed.rqa:
I got confused. My phone is my Galaxy A6 Sprint. The root is not fully installed. I tried to install it via twrp and it was not provided. Root. Please help. Blogs are better
[Android Software Development] stephtban:
This thread is dedicated to safetynet and not root. You should seek help in magisk thread.

To read the threads titles is better.
[Android Software Development] Strephon Alkhalikoi:
Root questions need to be asked in the Magisk thread. This thread is about a Magisk module, not Magisk itself.

Oh, and blogs are not "better", just different.

يجب طرح الأسئلة الجذرية في سلسلة Magisk. هذا الخيط يدور حول وحدة Magisk ، وليس Magisk نفسها.

أوه ، والمدونات ليست "أفضل" ، مختلفة فقط.
[Android Software Development] ephemunch:
Is there a short explanation somewhere that tells you when to use Shamiko and when to use Universal SafetyNet Fix?

I don't get it between them.
[Android Software Development] VD171:
Shamiko hides root/magisk/xposed/lsposed and nothing else.

Universal SafetyNet fixes the safetynet and nothing else.

Hiding root is not same for fixing safetynet.
[Android Software Development] bananabandana:
Hello,

So I've been following this thread and I am facing some similar issues. I am running LineageOS 18.1 on OnePlus 5. Although I am passing the Basic Integrity, it keeps failing the CTS Profile. I have all the relevant modules running on Magisk 24.1 (MHPC v6.1.2, Shamiko v0.4.4 and USNF v2.2.1). I have tried changing the fingerprint but that has not really worked for me. Changed the fingerprint to OnePlus 5, android 10, but that didn't pass the CTS either so I reverted back to the default fingerprint. Also tried using the fingerprint for Pixel 5, android 11, as well as "vendor fingerprint" but that didn't work for me either. No matter what I do, with the deny list or whatever, the CTS profile hasn't passed since I have updated to Magisk 24.1.

Any help would be appreciated.

View attachment 5556361
[Android Software Development] pndwal:
My understanding is that devices launched with pre Android 8 versions don't support the strong Hardware Key Attestation Google is implementing... Seems OP5 LV is 7.1.1.

Did your device pass CTS profile match w/o USNF w/ stock ROM (24.0+ will need both Zygisk and Enforce DenyList enabled in the absence of MagiskHide, and Google Play Services com.google.android.gms.unstable process and, for Android 11+, com.google.android.gms process, manually added to DenyList)?

If so, you should only need MHPC & fingerprint set in addition to the above w/ official LOS. (Nb. some unofficial LOS builds spoof passing fingerprint in ROM.)

You should still be able to use Zygisk-USNF (2.2.1) instead of manually adding Play Services processes mentioned above if you wish; it hides these itself w/o using denylist... Nb. Either way Zygisk = Yes must appear on Magisk app home screen for SafetyNet process (com.google.android.gms.unstable) hiding to be active. Nb.2. If Shamiko is active, Enforce DenyList must be disabled to activate Shamiko hiding (uses denylist list only).

Shamiko will do nothing for SafetyNet pass, so, for testing purposes you can disable all modules except MHPC...

LOS ROM may be breaking S/N, but these are generally fine especially if official versions... A custom kernel, module or other mod could also be the culprit... PW
[Android Software Development] bananabandana:
Thank you for your prompt response!

I never did check if my device passed the CTS profile back when it shipped with the stock ROM. I think it's been a few months since I switched to LOS and before that my device was not rooted to begin with. It did pass the CTS with Magisk Hide in v23 and was working perfectly before the update to 24.1.

As for this, yeah I have done this also. Enabled Zygisk, manually added com.google.android.gms and com.google.android.gms.unstable to DenyList. Although I haven't enforced DenyList because Shamiko is running. CTS is failing still.

I am attaching the screenshots of different fingerprint sets. Any changes to fingerprint sets are met with the same response of the CTS failing. The first one is the vendor fingerprint set. the second one is the OP5, android 10 and the last one is OP8 India android 11.

For troubleshooting, I disabled all other modules and only have UNSF and MHPC running. The CTS is still failing. To be clear, I am using Zygisk-USNF v2.2.1 AND manually adding Play Services in the DenyList.

Zygisk = Yes is appearing on app homescreen and Enforce DenyList is disabled. I have also disabled Shamiko

I am using the official LOS without any mods. I am using some other modules but I don't see how V4A or Font Manager would affect any of this.

UPDATE: I was tinkering on my phone while typing this out and replying and I managed to get CTS profile to pass when I used OP8 India android 11 fingerprint set. Zygisk-USNF v2.2.1. The device is certified on Play Protect and I have no issues downloading new apps or updating existing ones.

Thanks for your help!

View attachment 5556515View attachment 5556511 View attachment 5556513
[Android Software Development] pndwal:
Zy-USNF will remove Play Services processes from denylist in boot / reboot to prevent GMS starting before it does in-house hiding...

When Shamiko is disabled you should enable Enforce Denylist; it's a choice of one or the other. 😜

Well done...

You could try substituting USNF (disable it) for manually added com.google.android.gms and com.google.android.gms.unstable processes (keep denylist disabled w/ Shamiko enabled but Zygisk enabled)... I'm interested to know if this is enough on OP5... Seems it should be... PW
[Android Software Development] VD171:
Just disable/uninstall magiskhidepropsconf.

View attachment 5556969
[Android Software Development] pndwal:
🤔 How will he pass without MHPC on official LOS? (Unless fingerprint they build with just happens to match Security Patch date by some fluke)?... PW
[Android Software Development] VD171:
Do you mean a custom rom?

So, yes., you are right. I'm not familiarized with custom roms, I'm sorry.

If you are on a custom rom, magiskhidepropsconf has very great contribution on system properties.

System properties in custom rom will always be inappropriate.
[Android Software Development] pndwal:
Yes, user is on 'official LOS'.

Well, in general 'fngerprint' is the only property not addressed by USNF that prevents S/N pass.

Actually, USNF did attempt to make needed fingerprint changes in it's early days, but this proved difficult and @kdrag0n began recommending @Didgeridoohan's elegant MHPC solution.* 😛

One (the?) main purpose of MHPC is:

Passing SafetyNet's CTS Profile by Spoofing device's fingerprint to pass the ctsProfile check.​

This is always needed with official LineageOS (except occasionally when the fluke conditions I mentioned are met) due to their strict policy not to break Google's / others licencing, or circumvent their Security model(s), therefore they never package GApps, or Include spoofing solutions.

Unofficial LOS and other custom ROMs (Havoc etc) often integrate spoofing for CTS pass as well as @kdrag0n's USNF keystore manipulation (based on his ProtonAOSP ROM - https://github.com/kdrag0n/safetynet-fix#rom-integration ) in ROM.

MHPC w/ configured fingerprint is also the go-to solution for passing S/N on many Google-uncertified stock devices (China region stock etc) w/ GApps installed like my Xiaomi Mi Pad 4 (no 'global' ROM available).

*Note that @kdrag0n addresses this also:

https://github.com/kdrag0n/safetynet-fix#universal-safetynet-fix

👀 PW
[Android Software Development] Kiwi8:
Hi Mr Dragon!

Are there any plans to include support for android 7 phones? Thank you!
[Android Software Development] pndwal:
https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86609615 PW
[Android Software Development] yogeshdixit007:
My fingerprint sensor has stopped working after flashing USNF. I have installed the latest version of USNF and I am running android 12 on my OnePlus 8t. Tried every possible solution but it has not worked yet. I uninstalled the module just to check whether my fingerprint sensor is broken or not and it's working fine without module.... Can anyone help me out?
[Android Software Development] wrongway213:
I can't comment on when kdrag0n will release a version with this fixed, but he's merged the commit that fixes the issue here: https://github.com/kdrag0n/safetynet-fix/commit/55f892fb8855a7867a186970e0bfc31e665ab183

If you're able to, you can likely build it right now with that commit. If not, wait for a new version to be released, as it should have that commit.
[Android Software Development] yogeshdixit007:
Since I don't have any experience in building apps or modules it's better for me to wait for the new version with the fixes. Just to be courios, is it possible that I can just replace the fix files in the module to solve my problem...
[Android Software Development] wrongway213:
Now that I look at the changes in said commit, you could probably manually make the changes and replace the files. I don't see why you wouldn't be able to, as the changes here is very simple and only in two files.
[Android Software Development] yogeshdixit007:
I tried the manual process and replaced the service.sh and system.prop files which was updated in the commit still the fingerprint sensor is not working. Is there any additional steps I am missing after updating the module files? Also, I am using a custom kernel, pref+ and not a stock one....do I have to change it to stock?
[Android Software Development] wrongway213:
Sorry, I don't know a thing about any of that. I only shared the fix commit because I happened to see it, I don't know any more about the issue as I'm a Pixel 4 XL user. I wish I could help ya further.
[Android Software Development] yogeshdixit007:
No problem 👍. I'll wait for the new version.

Thanks for the help though. Really appreciated.
[Android Software Development] adgob:
Anyone have issues with apps that tie into the camera getting blocked? The United app uses the camera to scan for documents and gets an authentication error when rooted. I've tried to hide google play services, the camera, and the United app itself, but still get stuck. I tried unrooting and it worked fine, so there's a module it's accessing that I think needs to be blocked. I can use banking/google pay no problem.
[Android Software Development] yogeshdixit007:
I am using OnePlus 8t with Android 12. I was able to fix my FP problem with this modified module... I have not editted the module... I found it on a group in telegram... My FP is working again with all safteynet checks.
[Android Software Development] yogeshdixit007:
I have hiden all my banking apps as well as Google play service & Google play store through magisk denylist. Also, I use hide my applist for extra protection.... No application has detected root yet
[Android Software Development] pndwal:
Interesting; seems someone has built USNF with official fix (still downstream from any official builds) here:

magisk: fix Oppo fingerprint reader issues …

- move ro.boot.vbmeta.device_state to late props since any earlier appears to break Oppo (ColorOS/OOS12) fingerprint readers

Thanks @MlgmXyysd

Fixes #157

Nb. This fixes same issue for OnePlus.

Nb.2. fix can also be applied by using ColorOSMagisk module and manually applying @osm0sis' prop changes as described in issue #157 thread above... PW
[Android Software Development] pndwal:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86638901 PW
[Android Software Development] bananabandana:
Sooo the new Magisk update dropped and the CTS profile mismatch is here to bother me once again. This time around I thought I'd try this before fixing it the way I fixed it last time and I am deeply saddened to report that it does not work.
[Android Software Development] pndwal:
Could actually be simply lack of a mod to adjust sensitive props....both USNF and MHPC do this by default... If you want to persue this avenue, just install MHPC and reboot to test. (No need to configure anything; this is the only function enabled by default). PW
[Android Software Development] gregsoir:
anybody managed to run it on oneplus 8 pro android 12 (stock)? my fingerprint reader is not working when 2.2.1 module is installed.
[Android Software Development] zgfg:
You can find a discussion in March (scroll back) with some hints for fix
[Android Software Development] gregsoir:
hmm, indeed. I flashed the modified .zip for 8T from post #1698 and it works, thanks!
[Android Software Development] gregsoir:
one more question though.

I pass all the safetynet cheks now but still cannot find netflix and revolut in the play store (I cleared the play store data), says app is not compatible with my device.

also magisk hide via zygisk unchecks after reboot for google services framework, android auto and some others.

any hints?View attachment 5595973
[Android Software Development] zgfg:
I never put any other Google app to DenyList than Google Play Services (GMS) - bcs they all use SafetyNet API from GMS.

And that is advised in the Magisk thread

But USNF removes Play Services bcs it takes care of itself

I also use Android Auto (and tweaks CarTube, Fermata, Screen2Auto) and never put AA to DenyList - and never saw an advise to do so

Generally, if you put to many (unnecessary) apps to DenyList it can results with performance and so issues
[Android Software Development] drasterlx:
Hello

i have a LG G4 with A11 Havoc..

Magisk app 24.3(24300) (27)

package fyhmut.go

Zygisk yes

Magisk hided

Added to the list

google play services for AR

google pay

google play store

google play services

universal safety fix module 2.2.1 active

removed data of google play services, google play store and google pay

restarted...

but no luck with google pay :(

something that i saw... every restart google play services go out of denied list.

Any suggestion or help?

Thanks
[Android Software Development] zgfg:
Hiding Magisk app is irrelevant for Google apps (it may help only to some banking apps - those apps try to explore various methods to find or even guess about the root, eg, you may have locked Bootloader with stock firmware but if you just install Magisk APK they will falsely guess that your phone is rooted bcs why otherwise would one install Magisk APK)

Google apps use SafetyNet where SafetyNet is the API provided by Google Play Services (aka GMS), hence no use of putting Services for AR or Playstore to DenyList - it's enough to put GMS, all Google apps use GMS

But finally, USNF takes care of the Google Play Services and it removes GMS from DenyList - that was discussed and mentioned many times here, in the USNF thread and in the Magisk thread (old Magisk thread and the new Magisk+Zygisk thread)

But cannot help you with Google Pay - check in the Magisk threads
[Android Software Development] drasterlx:
question:

what is USNF?

and do you think is not possible to use google pay with magisk?

thanks for your answer
[Android Software Development] pndwal:
This module. 😜

Perfectly possible.

Normally just need S/N pass (check using YASNAC) and Play Protect Device is certified result, also Google Pay in denylist, then clear it's data...

For custom ROMs, where these don't spoof a passing fingerprint property you'll also need to configure a passing one. Use MHPC module. 😉 PW
[Android Software Development] Fishawy:
Had the same problem - all of a sudden yesterday - with Google Pay on my OnePlus 9 Pro. Did everything you did and more, even installing older versions, no luck for 3 hours.

Finally, turns out it's the latest version of Google Play Services (I was naive enough to opt-in the beta testing program). Google Pay kept showing something like "Checking for updates, this may take few minutes".

Uninstall Google Play Services updates, opt out of beta program if you're in, then re-apply the Google Pay process, and you'll be good to go.

Oh, and don't worry about GPS getting out of deny list with every restart. This has been the default behavior for me since Magisk 24, but it works.
[Android Software Development] zgfg:
We usually rather call Google Play Services as GMS, due to it's package name (you see that package name when you add to DenyList):

com.google.android.gms

Disappearing from DenyList has nothing to do with Magisk v24 but this module USNF = Universal SafelyNet Fix removes GMS from DenyList (already mentioned in this thread couple of times)

Go to:

/data/adb/modules/safetynet-fix

(where USNF installs - open eg module.prop text file)

And open service.sh to find there:

# Remove Play Services from DenyList, otherwise the Zygisk module won't load
magisk --denylist rm com.google.android.gms
[Android Software Development] minimal35:
The denylist magisk does not work, I put a checkmark on "google services framework" leave the denylist, then go back and the checkmark is gone. Please help.​
[Android Software Development] drasterlx:
Hello

sorry...

what i need to do in module.prop?

and i dont found that line in service.sh... or need to add it?

Thanks
[Android Software Development] zgfg:
You don't need to do anything

I was just repeating (the same and the same, again and again) that USNF removes GMS from DenyList, why and how, and that nobody needs to worry about!

Hope that everybody understands what USNF and GMS refer to - who does not know should take time and read the posts in this thread
[Android Software Development] minimal35:
Hello! How can I hide the root from an app without adding it to Denylist? I just need to add an app through LSPosed for a module, and I can't do that anymore since I added it to Denylist, and if I remove it from Denylist, the app detects a root
[Android Software Development] pndwal:
Why hide Google stuff other than GPay?

Generally you can't, unless some module or sandboxing app can do this without denylist...

Are you saying you have LSP app in denylist?... But it has its own 'Parasitic' hidden manager solution that works well... use that... Or did you mean something else? PW
[Android Software Development] minimal35:
Thanks for the reply! I need to simultaneously hide root rights from the app and use a module in LSPosed to spoof phone data. But unfortunately I can only do one of these things. Either I substitute data with a LSposed module and root rights will be visible to the app or root rights will be hidden but I cannot use the LSposed module for spoofing :(

here's an example
[Android Software Development] pndwal:
So app is in denylist?... Still not clear... Do you really mean 'hide root rights' or hide the module?

Have you tried Hide My Applist LSP module to hide 'faker' module from your app specifically?... Or am I still not understanding your issue?... PW