yashsingh1/xdaforums huggingface dataset:
[Android Software Development] pndwal:
I also suspect something has changed with a bank app update, but your changes aren't clear; if you are still on public Magisk nothing should have changed as yet with that AFAIK.

If you have moved / intend to move to new debug canary or upcoming public beta / stable Magisk builds, check this Changelog as well as Johns linked blog post to get the current picture:

https://github.com/topjohnwu/magisk-files/blob/9537c5d8cedfc09ca723ae0392b1219e75d9b636/notes.md

Access later changelogs here:

https://github.com/topjohnwu/magisk-files/commits/canary

If on a new canary build you'll need USNF (this module) ver. 2.2.0 to pass SafetyNet. If still on current stable but no longer passing SafetyNet, ver 2.1.2 + Riru (core) module will be your best bet... PW
[Android Software Development] ElBerretin:
I updated to the latest Magisk (23.0 (23000) to be specific), and Magisk Manager app version 23.0 (21). No idea what Canary is, even though I've read the name a couple times now (is it like a "different" Magisk? What's the benefit?).

Despite the update, my phone isn't passing SafetyNet, which brings me to my issue (doesn't pass either basicintegrity nor ctsProfile, apparently).
[Android Software Development] ElBerretin:
Yeah, it's weird, because for the longest time it worked without problem (and I know for a fact that it passed SafetyNet, because I originally installed Magisk to my phone to bypass Pokemon GO's restrictions, and I haven't played the game in a couple years now, yet still had it rooted).

Interestingly, now I can't pass either check of SafetyNet. Basically: I have root on my phone (checked with a Root Checker app, which detects it but also doesn't detect it once I apply MagiskHide to that specific app, which would mean both root and Hide work correctly; yet the banking app still detects my device as "altered", even though I've applied Hide to it as well).

To your suggestions - I can't rename Magisk! Every time I try, any name I give it, it just gives me a "Failed!" popup message.

But your other suggestion was great! I renamed the .zip files and voilá, they suddenly weren't greyed out. Currently installing the Riru module, whatever it may do, and I'll be trying the SafetyNet fix next. Will report back. Thanks for the help so far!
[Android Software Development] Brandon.Bissonnette:
Universal SafetyNet should be all you need. Just make sure if you're on Magisk 23 to use the Riru version as Riru doesn't work with the canary builds. And to answer your other question, think of Canary like beta only more unstable. However that's not to say the canary Magisk is unstable, that's just typtically what Canary builds are.

The reason it worked for you years ago and doesn't now is because google is constantly upgrading their detection abilities. In fact I don't know if you're aware but there is talk that hardware attestation will be forced in the future and Basic won't be considered valid. When that happens it will be very difficult to pass SafetyNet if at all.
[Android Software Development] Brokecurley:
I agree with you
[Android Software Development] ElBerretin:
I don't know exactly what changed, because to my eyes, nothing changed! I use my phone as normal, I'm the kind of user that doesn't really dab in "techie things" beyond having had to root my phone to install a custom ROM (I loathe MIUI) and used Magisk since, at the time, I played Pokémon GO and had to bypass SafetyNet. I haven't played the game in a couple years now, but still like my phone rooted, even though I don't really "do much" with it. So basically, not much that I have touched, it's strange.

Anyways... As far as I can tell, I'm on "stable" Magisk, v23. I don't know whether I should "move to Canary", I have no idea what Canary is or if it's "better" than good ole Magisk.

Lastly - following people here's advices, I managed to install both the Riru module, and the USNF (ver. 2.1.2), both are currently working.... Yet I'm still not passing either check of SafetyNet that Magisk allows you to check, and still can't get my banking app to work. It's disillusioning, I was certain that installing this module would do the trick, but alas....

So what's the next "best bet"? I don't really see what I'm doing wrong. My root works, my MagiskHide works (checked with a Root Check app as the troubleshooting guide advised), I have this module and Riru installed and running... What gives?
[Android Software Development] ElBerretin:
Sadly, I've now managed to install both the Riru module and Universal SafetyNet Fix module, and even with both working, my phone doesn't pass either stage of the SafetyNet test built into Magisk. So weird... I feel like I'm missing something really obvious here, but I've tried everything suggested so far, without luck.

Interesting, that about Canary. Doesn't sound too enticing to me - I'm far too much of a non-techie user to be dwelling into a basically alpha program. Maybe if it turns out to be the only chance I have to pass SN, I could give it a try... But I'd much rather stay in regular Magisk for now, tbh.

And yeah, I imagined it had something to do with Google updating SN or something like that. And yes, sadly, one of the main things I was reading up on is how the "root scene", or at least the root-hiding scene, is coming to an abrupt ending with these hardware verification methods, and now Magisk creator going over to the "dark side" and working with the enemy. Sad times, I guess.

I know for a fact, though, that Magisk is working (or should be working) right now, and I'd love to use it as long as I possibly can...
[Android Software Development] Philnicolls89:
Have you tried this version of USNF? 2.1.1
[Android Software Development] smegbat:
Hi,

Having issues getting safety net to pass on OnePlus 8T with Carbon ROM (Android 11). I installed version 2.2.0 of USNF and unfortunately that hasn't worked. I have attached screenshots of the modules I have installed in Magisk ver 23. Any help gratefully received. TIA
[Android Software Development] Brandon.Bissonnette:
You're using 2.2.0 with magisk 23. Use version 2.1.2
[Android Software Development] Brandon.Bissonnette:
Read my previous post, forgot to reply
[Android Software Development] smegbat:
Many thanks will give it a try👍
[Android Software Development] smegbat:
Hi,

Installed Ritu and USNF 2.1.2 and unfortunately it's still the same
[Android Software Development] Brandon.Bissonnette:
Did you use props config? Or just install it because just installing it does nothing.View attachment 5472243
[Android Software Development] smegbat:
Many thanks for your help. Props Config is just installed so I haven't changed anything. I'll have a read of the attachment to see what to do unless you have any tips? Thanks again 👍
[Android Software Development] pndwal:
For ROMs that don't include certified fingerprint or spoof one (many Custom ROMs, China region stock etc) you need only MHPC module option to set certified fingerprint configured in addition to USNF module... PW
[Android Software Development] Jimjimbo:
I am using Magisk 23

Beyond Rom S20 ultra

Riru

Lsposed

I have flashed USN 2.2 but still fail integrity and profile Evaltype basic.

Am I missing something?

I must admit I have not read all 75 pages however I have scanned a lot of comments.
[Android Software Development] zgfg:
Again (handful of similar posts earlier) - old Magisk 23 and new USNF 2.2 for Zygisk?!

USNF 2.1.2 is for Riru
[Android Software Development] Brandon.Bissonnette:
Yes.... Your problem is you didn't read the previous page or just a few posts up really.

Magisk 23 = 2.1.2

Magisk canary = 2.2
[Android Software Development] Jimjimbo:
Thanks for the reply.

I should have added sorry, that I had already tried 2.1.2 still the same failed response.

I expect I am missing a component somewhere along the line.
[Android Software Development] Jimjimbo:
Yes you are right. I have seen that now 🤦 the problem is I got confused with reading so many posts. That said 2.1.2 did not work for me.
[Android Software Development] Brandon.Bissonnette:
Oh I didn't even see what your problem is, if you're failing basic integrity this can't help you. That means your system partition has been altered or there is evidence of tampering going on. As for eval type basic, that is what you want. If I had to guess a Xposed module altered /system or it's doing something obvious and easy to detect.

Also should mention if you're using an Xposed module like HiddenCore you're actually failing both ctsProfile and Integrity even if ctsProfile claims it's passing.
[Android Software Development] pndwal:
Beyond Rom is custom?

So you likely need MHPC w/ passing fingerprint configured in addition to USNF 2.1.2 + Riru modules as I said here:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-86029605

Nb. Users / punters should read main GitHub page (linked from OP here) and release notes (click Releases, read all of them) to avoid confusion / understand additional out-of-scope fixes needed. The OP itself is not up to date... PW

Edit:

I see Beyond Rom may be set up to pass on its own (incorporate USNF / spoof passing fingerprint) so you may have other issues.

Could be ROM only bundles older USNF (Nb. newer fix addresses post September Google server end changes), ROM manipulates props (eg in pre-built utils) and this is incompatible with later USNF, incompatible modules as mentioned above, or other issue...
[Android Software Development] ReservedName:
just got the notification my device isn't ok to use NFC but Google pay still loads the cards. checked and failed safety net, I have no idea when that started. I haven't updated anything in a while and avoided updating magisk because it was going to lose magiskhide. no idea why this suddenly changed but I decided to update magisk after anyway just to see. still no good. I have riru and lsposed so maybe I have to tweak that. what changed? should I upgrade to Android 12 and then try fixing this after? pixel 4a here.

edit: seems like I don't have lsposed now. probably because of the update to magisk
[Android Software Development] pndwal:
Lite on detail.

Assume you have public (stable) Magisk 23.0. MagiskHide changes have only hit debug (Canary) TJW builds as yet, but this fix addresses new builds W/ Zygisk / denylist also.

So current stable Magisk should be no different; Google made new server end changes in September however, and many devices now need 2.1+ USNF to pass.

You need 2.1.2 for current stable Magisk & Riru is required also. 2.2.0 is for current canary + builds with Zygisk going forward... PW
[Android Software Development] ReservedName:
so I got 23015 the alpha apk and uninstalled the other magisk apk. I got 2.2.0 usnf and flashed that. I enabled zygisk and denylist. I can pass safetynet and use biometrics on my banking app. the legacy Google pay app still warns me about my device but the newer gpay app doesn't and the NFC payments still work. Lsposed and privacylua don't load now so I guess I can remove them?

I'm a little concerned about the legacy Google pay app warning and I don't think I need it so I just uninstalled it. YASNAC app says I pass safetynet (integrity, cts pass, basic eval).
[Android Software Development] Brandon.Bissonnette:
Did you clear cache/data from google play store, gpay and google play services? Sometimes if you don't pass safetynet it'll remember that until you do, check play store settings then about and at the bottom see if your device says it's certified or not. Clearing cache/data once safetynet passes should fix it.
[Android Software Development] zgfg:
Instead of Riru-LSPosed, you need to use Zygisk-LSPosed because Riru is not compatible with Zygisk.

Go to the Modules tab in Magisk app and Riru itself should dynamically show there some error (when working ok it says that it is loaded and displays how many Riru modules are loaded, like Riru-LSPosed)

Not sure can you download:

LSPosed-v1.6.3-6267-zygisk-release.zip

from Github, but you can from LSPosed-Arcives TG channel (however, posting URLs to TG channels are not allowed here on XDA).

With Zygisk-LSPosed you should be able to continue using LSPosed modules like XPrivacyLua, etc

PS: From the Github LSPosed page you can find a link to LSPosed TG channel. In that channel you will find the link to LSPosed-Archives TG channel where they daily (and sometimes more ofthen) push Riru and Zygisk, Release and Debug LSPosed builds
[Android Software Development] ReservedName:
I'm on the regular lsposed tg I don't know where that archive is. last post says they won't release the zygisk lsposed yet
[Android Software Development] zgfg:
Just updated my previous post. Read the PS there to solve the TG labyrinth - actually see the screenshot below
[Android Software Development] ReservedName:
thanks I was able to find and flash it. only thing is I didn't place the shortcut on reboot, where can I find the APK? (ok so on reboot I got another chance to place the shortcut, but I don't know where else to find it)

I rebooted to get systemless hosts going for AdAway which is working again now. do I even need lsposed anymore? the only module I had was privacylua and I think I don't need it now?

(thanks for all the help by the way)
[Android Software Development] zgfg:
Look under:

/data/adb/lspd

I have (albeit using Riru-LSposed) the manager.apk there

They call that parasitic manager. You can uninstall the apk but still use shortcut (you must create it).

If you uninstalled the manager and didn't/couldn't create the shortcut, you can still open the LSPosed manager by dialing a secret code:

*#*#LSPosed#*#*

L=5, etc

You can even create a shortcut for the dialer, for that 'number' on the Home screen
[Android Software Development] zgfg:
Interesting - you needed LSPosed/XLua for AdAway?

Maybe something specific for a particular phone with 12 - sorry I was not aware of, maybe you could elborate
[Android Software Development] ReservedName:
no I needed the systemless hosts module for AdAway. it's been awhile since I installed xprivacylua but I'm sure it must have been for fixing the Google pay issue. I really only need to tweak my phone for ad blocking in apps, wifi tether, and getting around root/safety net related issues. oh and YouTube vanced
[Android Software Development] glaedr:
Hi, thanks for help! Everything seems OK (like screenshot posted by you) except for "init.rc has been modified by magisk"
[Android Software Development] osm0sis:
vvb's Magisk Detector has been replaced by Momo: https://www.coolapk.com/apk/io.github.vvb2060.mahoshojo

The init.rc thing was unreliable so it's gone now.

Reference: https://github.com/topjohnwu/Magisk/issues/2406#issuecomment-963166974
[Android Software Development] glaedr:
I already have Riru, momohider, usnf. Is it compatible with these modules?
[Android Software Development] osm0sis:
It's a root detector. No idea what you mean.

Momo detects only USB debugging and Zygisk on mine, but I don't have any real apps which do the same, so best to just go on living your life.
[Android Software Development] zgfg:
You listed tools to hide. Momo is detector. Install and try what 'root' components Momo will detect on your phone

In the Magisk General thread there were posts about what and how to hide from Momo (e.g., I posted one pretty comprehensive post two or three weeks ago, but since Search in XDA is again unusable, it might be hard to find)
[Android Software Development] glaedr:
Here's the output: if I hide momo in Magisk hide, "found Magisk" disappear.
[Android Software Development] glaedr:
I wasn't able to find anything. Can you help me please? Banking app doesn't work, error provided "exiting on root"
[Android Software Development] aLcaTr4z:
Hey guys, ill stuck too on get this working. Running Magisk 23, Riru, USNF 2.1.2 but it wont do anything.

Need halp, need my bank account app to get f00d. :D

Edit: Fixed it, by running "props" on terminal. :whistle:
[Android Software Development] zgfg:
Sorry, no idea (even what is your particular banking app and how that app/their devs detect or guess about root)

From Magisk app, main window, bottom, there is a link to Guthub Wiki pages with instructions if certain apps detect root - maybe it can help
[Android Software Development] eeeemc:
[ HELP SEEK]

My Redmi 9T ( aka Redmi 9 power ) banking apps kicked me out saying detected system has modified/rooted.

I've some little knowledge and already have installed what I know necessary Magisk Module , Magis Props Config , Riru , Riru-LSPosed, Universal SafetyNet Fix, SafetyNetfix 2.2.0, LSPosed & XPrivacy

( XPrivacy check mark the Google play service and those banking apps )

Magisk hided., Check SafetyNet is in Blue ( success )

Termux choose Google Pixel 6 fingerprints

Still no luck to get it work. Trying to see if any brothers here have new methods.

Thank you very much., edmond
[Android Software Development] pndwal:
You may have other issues, but Riru and Zygisk are not (now) compatible. You need USNF 2.1.2 for Riru... 2.2.0 is a Zygisk mod...

Which Magisk version?

... You don't need MHPC / fingerprint spoofing on your device unless have custom or China region ROM... doubtful you need XPrivacy lua either... Need to have bank app in hidelist / dentist and clear it's data after you see Google Play Protect passed (Device is Certified in Play Store settings). Clear Play Store and Google Play Services data after passing SafetyNet if not certified...

These are the basics. If 'root' is still detected after achieving above, say Which bank app!...

There are different hiding methods for various apps... PW
[Android Software Development] ecvarts:
I'm not sure anybody mentioned it here already, so I'll say it:

The developer dropped support for hiding root from apps, after being hired by Google.
[Android Software Development] osm0sis:
Wow, newsflash over here. 🤣
[Android Software Development] j1gga84:
I just installed V2.2.0 for Zygisk because I am using latest Magisk Canary build (23016) but with rootbeer fresh I still do not pass all tests. Therefore the fingerprint for my banking app and the wireless pay app from my bank crashes when trying to open.

I checked safety net status with YASNAC and I pass both tests, also play store shows my decide as certified.

I am using a Samsung Galaxy S9 running AlexisROM, an android 10 based stock ROM.

So any ideas how I can get the rest of tests green (pass)?

Thanks in advance
[Android Software Development] Qnorsten:
Have you added rootbeer and your bank app to the deny list in magisk manager app?
[Android Software Development] j1gga84:
That worked for the rootbeer app but my banking app and mobile pay app from my bank still do not work..

The mobile pay app crashes when trying to open and in my bank app I cannot use fingerprint for login and some functions are missing from the banking app (typical when root is detected). I set both apps to deny list.

Any other ideas?

Regards
[Android Software Development] Slim2none4u:
Make sure anything that detects root is in the deny list. Then clear the cache and maybe even the storage of said apps and reboot the phone.
[Android Software Development] wrongway213:
This is Universal SafetyNet Fix and you're passing SafetyNet. I'm not sure if a solution to your problem exists or not, but it's definitely outside the scope of this module, given you're passing SafetyNet and that's all this module is meant to do is make you pass SN.
[Android Software Development] pndwal:
If anyone has an app failing due to detecting broken TEE after both achieving "Device is certified" Play Protect result in Play Store, adding the app to denylist / hidelist and then clearing the apps data, advice will be app-specific as many security centric apps are using various custom detection methods rather than the (currently); flawed SafetyNet API...

No-one can help w/o much unnecessary guesswork if you don't state what app you / we are dealing with...

I just put some general information about customised detection and solutions here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86111153

😝 PW
[Android Software Development] zgfg:
Ok, any 'advice' for Momo detecting Bootloder unlocked 😍

I had that with MagiskHide, Riru-Momohider; now with Shamiko, USNF 2.2 - you name it (with various Magisk versions over time)

SafetyNet easily passes (it checks in the first place if Bootloder is unlocked but with some flaws) but Momo must be going under the hood and still detects

And as the detection says, it's not detecting root or some artefacts (su, LSPosed, TWRP folder, whatever) but simply that Bootloder is unlocked

But I have no real problem with that, with any real app. Only a 'problem' in Momo
[Android Software Development] pndwal:
You and me both; but I note we both have Xiaomi / forms of MIUI...

Yup, seems to hide bootloader unlock for SafetyNet purposes; my guess is also that vvb2060 uses different / more reliable flags to detect... May need to bribe him to reveal!...

And note those guys have 2 favourite sports: 1) Provide custom fixes, 2) Mock dumb foreigners! 🤪

... but I guess that's why you're asking me! 😜

Yup... but further on the Xiaomi/ MIUI point, all those with Unlocked B/L in Momo, or Blissfully happy Momo seem to have devices other than Xiaomi. Leads me to believe something may be more difficult to hide for us...

However I'm not sure if app Devs will be very interested in the form of detection vvb2060 uses if it is demonstrably easy to circumvent for many devices, and might only be better than SafetyNet API for catching Xiaomi modders! ... I reckon this goes for Art Parameters and other forms of detection that will only catch a small subset of modders or of Magisk users... I'm guessing they want to invest in methods that work at least more universally...

Now, if these same Devs start applying all the methods, eg are able to run Momo as a utility for their purposes, I guess their app users who customise are in trouble...

So I gave a long answer first... Short answer:

Not much really... Sorry! 😝 PW
[Android Software Development] yohanleafheart:
Phone: Redmi Note 9 PRO (joyeuse)
ROM: LOS 18.1 nightly (build 20211217)
Magisk: 23.0
Riru: 26.1.4.r522.8b379cedb5
Universal SafetyNet Fix v2.1.2
Magisk Hide enable and active for com.google.android.gms

Hey everyone, above we have the info for my build. I still can't make it pass the ctsProfile check. Any ideas what I am missing?
[Android Software Development] zgfg:
For the beginning:

Depemding on your ROM you will need or not (hence keep) com.google.android.gms but you MANDATORY need com.google.android.gms.unstable

For SafetyNet itself you never need Riru (hence better disable anything that is not needed and play with them only once you pass SN)

Try as that and if not passing you will also need MHPC module, and you will need to study in its XDA thread how to spoof fingerprints for your custom/not certified ROM
[Android Software Development] yohanleafheart:
Greetings ma

Installing MHPC and spoofing with a random redmi worked, I should have tried more fingerprints before posting. Thanks for the help. Now to discover why Telegram can't send compressed images/video/audio messages anymore on LOS 18.1
[Android Software Development] eeeemc:
I'm Magisk 23.0 ...............

where I can reach & download USNF 2.1.2 to try if it can help ? Is it a module of Magisk ?

Thanks
[Android Software Development] pndwal:
This whole thread is for USNF module... Go to OP, then GitHub link. Read notes there. Go to Releases. Read notes there. Download... PW
[Android Software Development] eeeemc:
Oh Oh , Safetynetfix 2.20 , I had that.

Which other method of Magisk HIde you mentioned earlier for different apps ?

My Banking apps is not able for you to download as region restrict.

** anyway , I guess it is about the Redmi Android Global 12.5.5 make Magisk hide not working.

Thanks
[Android Software Development] pndwal:
But you need to consider what you've already been told first! If you have Riru working, why would USNF 2.2.0 (Zygisk) work??? It IS NOT COMPATIBLE with Riru!

You need USNF 2.1.2 (Riru) for Stable Magisk w/ Riru! DON'T click 'Latest'! Click 'Releases'!

If you have Canary with Riru this solution WON'T CURRENTLY work either as it REQUIRES WORKING MagiskHide!...

You need to READ Release Notes! 🤪 PW