Database Develop

[UNOFFICIAL] next version Magisk and MagiskManager snapshots

MOD EDIT: PLEASE MIGRATE TO THE OFFICIAL CANARY BUILDS
THIS THREAD IS ABOUT UNOFFICIAL COMMUNITY BUILDS. OFFICIAL BETAS THREAD IS HERE: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589.
This thread is dedicated to the community-built next versions of Magisk and MagiskManager using latest source files posted by @topjohnwu. If you want to contribute in any way -- create a PR/issue on github.
These might be very unstable builds, especially in the early stages of development. You're highly advised to read the rest of this post and at least a few last pages of the discussion.
Downloads are here: https://github.com/TheComputerGuy96/MagiskFiles. Keep reading if this is your first visit to this thread or for the updates at the bottom of this post.
Current builds are courtesy of @kantjer. This project wouldn't have happened without @Deic's module to track the snapshot updates (which may be hindered by recent @topjohnwu changes in versioning) and his contributions to the build script, as well as major contributions in supporting fellow community members by @Captain_Throwback, @Didgeridoohan and @DodoGTA.
Installation:
Magisk: flash magisk snapshot from recovery, it should install over any previous version just fine.
Magisk Manager: The snapshot APK is signed with a different key than the release APK so you can't install snapshot magisk manager over magisk manager from Play Store. You will need to uninstall existing Magisk Manager and install the snapshot APK afterwards.
Commits Logs:
Magisk (master branch)
Magisk Manager (master branch)
IF SOMETHING DOESN'T WORK AND/OR CRASHING:
No support of any kind is implied, however it's a community forum so some users (including local experts) might be willing to help your and/or your report might be helpful to @topjohnwu, but please make sure to follow the below:
Magisk Manager crashing? Problem with Magisk module? Post installed versions of magisk, magisk manager, versions of all installed modules and the magisk log + logcat.
Downloads: https://github.com/TheComputerGuy96/MagiskFiles
Source code: https://github.com/TheComputerGuy96/Magisk (branch travisci-dev)
Travis-CI link: https://travis-ci.org/TheComputerGuy96/Magisk

That's nice of you. What is the change log?

Cool! I'm gonna give this a try and see if some of my issues are resolved.

Filip013 said:
That's nice of you. What is the change log?
Click to expand...
Click to collapse
We can check the commits log for now: https://github.com/topjohnwu/Magisk/commits/master and https://github.com/topjohnwu/MagiskManager/commits/master.

@topjohnwu, what's the reasoning for disabling MagiskHide when SuperSu is installed?

gamer765 said:
@topjohnwu, what's the reasoning for disabling MagiskHide when SuperSu is installed?
Click to expand...
Click to collapse
Because Magisk Hide don't work with SuperSU? Maybe...

Viper4android is working well S7 nougat
Verstuurd vanaf mijn SM-G930F met Tapatalk

Didgeridoohan said:
Because Magisk Hide don't work with SuperSU? Maybe...
Click to expand...
Click to collapse
I have MagiskHide working perfectly with SuperSu 2.79 on Nougat. I can use PoGo and AP. The latest Github commit breaks it.

gamer765 said:
I have MagiskHide working perfectly with SuperSu 2.79 on Nougat. I can use PoGo and AP. The latest Github commit breaks it.
Click to expand...
Click to collapse
Ok, cool... Did not know that was possible. Since topjohnwu himself have stated that Magisk Hide can NOT hide SuperSU, I assume he has a good reason to do what he does.

Think about saying stupid things, you should have respect for the guy. Just turn on magisk hide, do not tick supersu in gui
Verstuurd vanaf mijn SM-G930F met Tapatalk

afcaajax said:
Think about saying stupid things, you should have respect for the guy. Just turn on magisk hide, do not tick supersu in gui
Verstuurd vanaf mijn SM-G930F met Tapatalk
Click to expand...
Click to collapse
Not sure if you're directing that at me, but no one here is saying stupid things, except maybe you. Plus, I'm a dev/hacker myself so it doesn't really bother me, since I can always fix it myself.

gamer765 said:
I have MagiskHide working perfectly with SuperSu 2.79 on Nougat. I can use PoGo and AP. The latest Github commit breaks it.
Click to expand...
Click to collapse
If you haven't yet, please consider creating an issue for that on github and let @topjohnwu know.
AFAIK you can checkout the code one commit before the problematic one and build your own v10.
PS. Please don't feed the trolls.

gamer765 said:
I have MagiskHide working perfectly with SuperSu 2.79 on Nougat. I can use PoGo and AP. The latest Github commit breaks it.
Click to expand...
Click to collapse
That's unexpected, it never worked previously, I just added the detection I should have done in ages.
I'll try it myself when I got time, once confirmed working I'll revert this change

gamer765 said:
I have MagiskHide working perfectly with SuperSu 2.79 on Nougat. I can use PoGo and AP. The latest Github commit breaks it.
Click to expand...
Click to collapse
I'm not sure how you're accomplishing this, but it shouldn't be possible, unless you're also using some other hiding method (suhide, RootSwitch). Magisk Hide cannot hide SuperSU. I just installed it and tried it to confirm, since your post piqued my curiosity, but not surprisingly, SafetyNet came up all red, and my AirWatch app shows compromised.
Can you explain in detail what your setup is and confirm you're ONLY using SuperSU and Magisk Hide, and pass with green for SafetyNet?

Ah, well I am using suhide and rootswitch as well and everything works perfectly fine for me.
I've attached screenshots of SafetyNet passing for me. By all means, it's your project, you may do whatever you wish with it, I'll just fork it and make my own private builds where SuperSU does not disable MagiskHide..

gamer765 said:
Ah, well I am using suhide and rootswitch as well and everything works perfectly fine for me.
I've attached screenshots of SafetyNet passing for me. By all means, it's your project, you may do whatever you wish with it, I'll just fork it and make my own private builds where SuperSU does not disable MagiskHide..
Click to expand...
Click to collapse
Let me take a moment and just lay my palm against my forehead...
I'm gonna go out on a limb and guess what you're really using Magisk Hide for is hiding your unlocked bootloader with resetprop. There are other ways of doing that, you don't need Magisk Hide.

No, I do not. I use it for other stuff as well. All my mods are systemless. I'm on completely stock system with a custom kernel that does not pass bootloader unlock flags. I'm not a dumb person, but I see I'm being treated that way. I do things the way I do them for a reason. I will no longer partake in this conversation, I have better things to do. Maybe it's better to just stick to stock because ignorance is bliss. I need a break anyways from my work. Bye and thank you.

gamer765 said:
No, I do not. I use it for other stuff as well. All my mods are systemless. I'm on completely stock system with a custom kernel that does not pass bootloader unlock flags. I'm not a dumb person, but I see I'm being treated that way. I do things the way I do them for a reason. I will no longer partake in this conversation, I have better things to do. Maybe it's better to just stick to stock because ignorance is bliss. I need a break anyways from my work. Bye and thank you.
Click to expand...
Click to collapse
Well if you want to use SuperSU with Magisk Hide, just manually revert the change that disallowed it. That takes 10 seconds to do.

Captain_Throwback said:
Well if you want to use SuperSU with Magisk Hide, just manually revert the change that disallowed it. That takes 10 seconds to do.
Click to expand...
Click to collapse
His question still stands, if MagiskHide does work with SuperSu installed and there're viable use cases for that, why disable it?

stangri said:
His question still stands, if MagiskHide does work with SuperSu installed and there're viable use cases for that, why disable it?
Click to expand...
Click to collapse
I don't think @topjohnwu was considering those extended use cases when he disabled it. Maybe now that he knows, he'll revert that change. I think he was thinking that Magisk Hide can't directly hide it so it would always be detected. With several other tools, it's apparently possible to hide it, which is good to know. Personally, I'll just be sticking with the open-source solution anyway, so it doesn't really affect me.
EDIT: Besides the fact that there are many people who will enable it, not knowing that Magisk Hide can't hide SuperSU. I think the change was in an effort to prevent those types of questions.

Magisk Tez Users - Error recently due to Google

I am getting error on my tez app, due to my Google play I think so.. it has started recently... Please anyone help me

Tez App is not working Now... As i Have installed Magisk And the root is enabled,but the Tez App is showing my device is rooted. please help me..!! I Need a Solution Very Fast.. if anyone can help me ... please reply for this

gokulraj3 said:
I am getting error on my tez app, due to my Google play I think so.. it has started recently... Please anyone help me
Click to expand...
Click to collapse
Everyone facing this. Looks like we will have to wait for either magisk to update or some tez trick
Sent from my Redmi Note 5 using Tapatalk

gokulraj3 said:
Tez App is not working Now... As i Have installed Magisk And the root is enabled,but the Tez App is showing my device is rooted. please help me..!! I Need a Solution Very Fast.. if anyone can help me ... please reply for this
Click to expand...
Click to collapse
hey bro,
try using this module
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
and then, report if you still facing any problems. :good:
Happy to help

hackiee said:
hey bro,
try using this module
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
and then, report if you still facing any problems. :good:
Happy to help
Click to expand...
Click to collapse
That module won't do anything for fooling Tez. Unless the issue is that SafetyNet's ctsProfile is false while basicIntegrity is true...

Didgeridoohan said:
That module won't do anything for fooling Tez. Unless the issue is that SafetyNet's ctsProfile is false while basicIntegrity is true...
Click to expand...
Click to collapse
Which it is not
SN passes but tez is now detecting something

Didgeridoohan said:
That module won't do anything for fooling Tez. Unless the issue is that SafetyNet's ctsProfile is false while basicIntegrity is true...
Click to expand...
Click to collapse
Improved hiding - editing prop files
Often, it's easy to circumvent root detection, but in some rare instances apps (mainly banking apps) go that extra distance. These apps might look at the actual prop values written in build.prop and default.prop rather than the loaded values. This module can hide that. For more details, check out the documentation on GitHub.
quoted from the same module bro, Check it. :fingers-crossed:
I am using Tez successfully with magisk and even with Xposed.
Check SS.

hackiee said:
Improved hiding - editing prop files
Often, it's easy to circumvent root detection, but in some rare instances apps (mainly banking apps) go that extra distance. These apps might look at the actual prop values written in build.prop and default.prop rather than the loaded values. This module can hide that. For more details, check out the documentation on GitHub.
quoted from the same module bro, Check it. :fingers-crossed:
I am using Tez successfully with magisk and even with Xposed.
Check SS.
Click to expand...
Click to collapse
This module not working anymore. I already tested it on few roms. Tez Still not working. Safety net passes but tez doesn't work. Btw this module is for passing safetynet. Not to help with those apps which you are describing. It wil only help with those apps which just rely on normal safetynet passing. Other stuff or apps. We need to figure out ourselves
Sent from my Redmi Note 5 Pro using Tapatalk

hackiee said:
quoted from the same module bro, Check it. :fingers-crossed:
Click to expand...
Click to collapse
I have checked it. Hint: compare user names...
I am using Tez successfully with magisk and even with Xposed.
Check SS.
Click to expand...
Click to collapse
I seriously doubt it's because of the mentioned module above...
But, if you'd describe your method for using Tez I'm sure there are a whole bunch of users that would be interested to know.

Kapiljhajhria said:
This module not working anymore. I already tested it on few roms. Tez Still not working. Safety net passes but tez doesn't work. Btw this module is for passing safetynet. Not to help with those apps which you are describing. It wil only help with those apps which just rely on normal safetynet passing. Other stuff or apps. We need to figure out ourselves
Sent from my Redmi Note 5 Pro using Tapatalk
Click to expand...
Click to collapse
Bro, check my screenshots. I am with xposed framework. So, SN doesn't pass. But, my tez app and other apps are not detecting root coz of that module.
And I am saying this coz before that module, I was facing same problems in Paytm, Tez, etc. even though i had used magisk hide on those apps at that time. But, believe me or not after using this module's "Improved hiding" feature they are not detecting my root. :laugh:
Check out my Root beer's tests before and after magisk hide with that module's improved hiding.
I can't justify more, try yourself.

hackiee said:
Check out my Root beer's tests before and after magisk hide with that module's improved hiding.
I can't justify more, try yourself.
Click to expand...
Click to collapse
Seriously? That's the only thing you've done? Activated the "Improved hiding" of MagiskHide Props Config? Hm...

hackiee said:
Bro, check my screenshots. I am with xposed framework. So, SN doesn't pass. But, my tez app and other apps are not detecting root coz of that module.
And I am saying this coz before that module, I was facing same problems in Paytm, Tez, etc. even though i had used magisk hide on those apps at that time. But, believe me or not after using this module's "Improved hiding" feature they are not detecting my root. :laugh:
Check out my Root beer's tests before and after magisk hide with that module's improved hiding.
I can't justify more, try yourself.
Click to expand...
Click to collapse
Dude can you share more details pls..let's see if it works
What did you do? Just flashed the module? Any extra commands or change specific props?
Are you using the tez hider mod as well? Or in other words have you disabled telephone perms from play services?
Have you tried re registering? In the last 2 days or so? Does it work?

Didgeridoohan said:
I have checked it. Hint: compare user names...
Click to expand...
Click to collapse
Oh, sorry bro, I didn't noticed you are the developer of the same module I was boasting about
Didgeridoohan said:
I seriously doubt it's because of the mentioned module above...
But, if you'd describe your method for using Tez I'm sure there are a whole bunch of users that would be interested to know.
Click to expand...
Click to collapse
bro, I am not applying some magic tricks It's your module I am using for the purpose of improving of the hideness of magisk root. Hey, plus I am using 1 extra module also "TezHider4Mgisk". But, I really doubt that it is doing that job, coz I tell you what I am using this(TezHider4Mgisk) module like from months & didn't faced problems.
And recently, after the latest update of Tez app, I started facing issue of "Can't authorize app coz of root or custom rom" something like that warning.
Then, I came across your module and after applying your module my Tez was back to work. :laugh:
I don't have any special setup for Tez.
Using these the above mentioned modules as
"TezHider4Mgisk" & "Your module"'s only improved hiding option.
Using magisk hide to hide (I am mentioning only relevant apps)
Tez, Google play store, Google services framework,Phone, Phone & messaging storage, Phone services, & some other payment apps only.
And voila everything as Rock solid. :silly::silly:
And btw, I am on AEX custom rom with my beloved Lenovo P2 , magisk v16 & Tez app updated to latest.
I can provide any more information you want regarding this
Happy to Help :highfive:
---------- Post added at 12:13 AM ---------- Previous post was at 12:11 AM ----------
Didgeridoohan said:
Seriously? That's the only thing you've done? Activated the "Improved hiding" of MagiskHide Props Config? Hm...
Click to expand...
Click to collapse
yes bro, these SS are after magisk hide disabled and enabled for RootBeer.

Didgeridoohan said:
Seriously? That's the only thing you've done? Activated the "Improved hiding" of MagiskHide Props Config? Hm...
Click to expand...
Click to collapse
for me its not working, safetynet passed for my device.
but tez not working

TR!O said:
for me its not working, safetynet passed for my device.
but tez not working
Click to expand...
Click to collapse
I've seen lots of reports of the same nature, that's why I was surprised by @hackiee's claim... I'm still not convinced that it was the "Improved hiding" that did the trick for him, but I can't investigate any further since I don't have any practical way of testing and playing around with Tez.

Didgeridoohan said:
I've seen lots of reports of the same nature, that's why I was surprised by @hackiee's claim... I'm still not convinced that it was the "Improved hiding" that did the trick for him, but I can't investigate any further since I don't have any practical way of testing and playing around with Tez.
Click to expand...
Click to collapse
Pretty sure its something else. I have tried all that already. Not just me but other people as well. It doesn't work
Sent from my Redmi Note 5 Pro using Tapatalk

hackiee said:
I don't have any special setup for Tez.
Using these the above mentioned modules as
"TezHider4Mgisk" & "Your module"'s only improved hiding option.
Using magisk hide to hide (I am mentioning only relevant apps)
Tez, Google play store, Google services framework,Phone, Phone & messaging storage, Phone services, & some other payment apps only.
And voila everything as Rock solid. :silly::silly:
And btw, I am on AEX custom rom with my beloved Lenovo P2 , magisk v16 & Tez app updated to latest.
I can provide any more information you want regarding this
Happy to Help :highfive:
---------- Post added at 12:13 AM ---------- Previous post was at 12:11 AM ----------
yes bro, these SS are after magisk hide disabled and enabled for RootBeer.
Click to expand...
Click to collapse
Are you using xposed? Which modules in xposed? Any root cloak module?

Yeah I tried too. It's not working for me too

Not working here either. Hope someone finds what's actually breaking the tez app even though safety net passes.

It started working for me after disabling ADB.
Can anyone else also confirm that?

Comdirect photoTAN app detecting root

Since version 8.3.0 additional measures to detect root have been added, do not update as MagiskHide won't be able to prevent detection. Until a solution is found I would recommend staying on the previous version for as long as possible.
Finding out what exactly is causing the root detection is beyond my technical abilities but I would provide as much information needed to those willing to help.
---
Update: December 14th 2021 - Method no longer sufficient
---
The solution found by @pxrave appears to be working:
pxrave said:
Hey fellas I got it working and others apps detect magisk before.
Update to latest v23
Install modules riru and riru unshare
Remove data from tan app
Go to magisk hide and tick all process to hide included the isolated
Start the tan app and do the activation again.
Problem you need wait 2 days to activate because comdirect use new activation process for photo tan app.
Working fine all version 8.3
Click to expand...
Click to collapse
Link to the Riru Unshare module:
GitHub - vvb2060/riru-unshare
Contribute to vvb2060/riru-unshare development by creating an account on GitHub.
github.com

also stcpay yesterday is updated to 1.6 and started to detect my magisk canary (22105)

I can confirm what swour says.
on Android 9 and 11, my magisk root is recognized, magiskhide is active and the phototan app is added.

Yes this is a serious problem. I used xposed magisk and x privacy... Latest comdirect tan app detect all...

+1

+1 big issue for me

Only solution I found (for now): Go back to version 8.2.1 using a backup or any mirror, e.g. https://downloadapk.net/comdirect-photoTAN-App.html
Unfortunately you need to register again then

I have already applied the update. The easiest method is to wait few days for a magisk fix, right? I would can wait few days, no problem. I have an absolutly clean Android 8.1 build on the phone for banking. It's crazy that the bank is make it so difficult for us to use a save own build.

allrightlite said:
The easiest method is to wait few days for a magisk fix, right? I would can wait few days, no problem.
Click to expand...
Click to collapse
Perhaps that is too optimistic. I doubt that one app is of great interest

Asellus said:
one app is of great interest
Click to expand...
Click to collapse
Until the new root detection is also available for other apps, it will be fixed quickly.

Conan179 said:
Until the new root detection is also available for other apps, it will be fixed quickly.
Click to expand...
Click to collapse
Thanks, then I will easly wait. No need to reactivate hopefully.

Conan179 said:
Until the new root detection is also available for other apps, it will be fixed quickly.
Click to expand...
Click to collapse
Yes, of course, if other app developers find a similar way. So, congrats to the developers of the phototan app to find it.

Asellus said:
Yes, of course, if other app developers find a similar way. So, congrats to the developers of the phototan app to find it.
Click to expand...
Click to collapse
I don't think so, there is at least one other app that shows the same behavior.
new root dedction
i updated stc pay yesterday to 1.6 and it found my magisk canary (22105) the think i notes is the (isolated) is added to the app !!!
forum.xda-developers.com
I also noticed the (isolated) thing with me.

I tried with v23 this morning, w/o success :-(

Same here, got v23 and working safetynet-fix, no success. Downgraded photoTAN to v8.2.1 .

+1

I'm not surprised, there is nothing in the changelog that this has been fixed.

Downgrading to 8.2.0 or 8.2.1 doesn't work for me. Did you do something else than uninstalling 8.3.0 and installing 8.2.1?

muschi.muscholini said:
Downgrading to 8.2.0 or 8.2.1 doesn't work for me. Did you do something else than uninstalling 8.3.0 and installing 8.2.1?
Click to expand...
Click to collapse
I have a ZTE Blade L130 with the old photo tan app, that is my rescue. But you can't activate the old one. But it's keep working.

muschi.muscholini said:
Downgrading to 8.2.0 or 8.2.1 doesn't work for me. Did you do something else than uninstalling 8.3.0 and installing 8.2.1?
Click to expand...
Click to collapse
I had to unhide the app in magisk hide and hide it again, after that it worked.

[24.1] Magisk from User perspective - Safety check not working ??

Hi folks,
I got the new update 24.1 of my good old Magisk on top of my Lineage OS on payton device.
But I guess the safetynet check is gone and/or no more working since last update as of the banking app and also the game i.n.g.r.e.s.s is no more working..
What do I have to do in order to get back a positive safetynet check?
I have no much experiencies behind the scenes but all you are made a great job in your laisure time but please give me a chance to understand how and what must I configure to get working Magisk (MagiskHide and SafetyNet Check passed). Maybe there is a additional module that makes the SafetyNet check being passed.
Thank you
Tom

Tom_Scott said:
Hi folks,
I got the new update 24.1 of my good old Magisk on top of my Lineage OS on payton device.
But I guess the safetynet check is gone and/or no more working since last update as of the banking app and also the game i.n.g.r.e.s.s is no more working..
What do I have to do in order to get back a positive safetynet check?
I have no much experiencies behind the scenes but all you are made a great job in your laisure time but please give me a chance to understand how and what must I configure to get working Magisk (MagiskHide and SafetyNet Check passed). Maybe there is a additional module that makes the SafetyNet check being passed.
Thank you
Tom
Click to expand...
Click to collapse
Please consult this thread, especially first few posts:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com

Lord Sithek said:
Please consult this thread, especially first few posts:
Click to expand...
Click to collapse
Thank you for the answer, but I dont understand the thing being written in the discussion thread. Can you give a hint what do I have to do in order to solve the problem?
Thanks
Tom

Tom_Scott said:
Thank you for the answer, but I dont understand the thing being written in the discussion thread. Can you give a hint what do I have to do in order to solve the problem?
Thanks
Tom
Click to expand...
Click to collapse
Well... In short:
MagiskHide is gone now, replaced by Zygisk & DenyList. DenyList doesn't do any hide itself, but it can be used by additional modules to do it. SafetyNet check is also removed, but you can replace it by installing a checker from Play Store. Recommended one is YASNAC, search and install.
If you don't pass SafetyNet, first enable Zygisk & Enfoce DenyList, then go to Configure DenyList, tap on three dots in right upper corner and enable system apps. Then search for Google Play Services, expand the list of processes and mark com.google.android.gms and com.google.android.gms.unstable. [Additionally mark every app that search for root access]. Clear the data of Google Play Services and Google Play Store and check in YASNAC if you pass SafetyNet now. If not, download this module and flash in Magisk:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Then reboot and check SafetyNet again.
Usually this should be enough to pass SafetyNet, but if not, let me know, we can try another things. If you use official LineageOS, probably you will have to spoof the device's fingerprint, but... one thing at a time
As for bank apps (and some games too), it depends how much enforcements they use. If they rely only on SafetyNet, passing it will be sufficient to run them. But many bank apps use addtional measures to prevent running on rooted devices nowadays. But there are other workarounds which we can try if just passing SafetyNet isn't enough.

Thank you very much. Your guide enables passing the Safety Net check so I can use my special apps again.
In order to understand the new working principle: Please, can you explain what the DenyList denies? And do you know why the CTS check is gone?
Thank you very much
Tom

Tom_Scott said:
Thank you very much. Your guide enables passing the Safety Net check so I can use my special apps again.
In order to understand the new working principle: Please, can you explain what the DenyList denies? And do you know why the CTS check is gone?
Thank you very much
Tom
Click to expand...
Click to collapse
I think you should get familiar with the Topjohnwu statement on Magisk: https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458
Those changes were obviously well-thought and although they may look like a step back, they will allow to achieve much progress in time

[Discussion] How to bypass detections of rooting ?

Did you have problems with some app that detects the root ?
Here is your place.
We will try to help you.
Keep attention, this is just a help thread, nothing is guaranteed.
Be patient and cordial.
If there is acceptance of the community on the subject, certainly the thread will grow.
Before posting your reply, please describe some questions:
- What is the version of Android ?
- What is the name of the app, the package of the app and where can we download the app ?
- When does exactly the app crash ?
- Are you using a custom/modded ROM or a stock ROM ?
- Which magisk modules are enabled ?
- Which xposed modules are enabled ?
Don't forget to attach some screenshots.

Some Useful Content For Bypassing Detections:
Shamiko:
https://github.com/LSPosed/LSPosed.github.io
DenylistUnmount:
https://github.com/mywalkb/DenylistUnmount
XPrivacyLua:
https://repo.xposed.info/module/eu.faircode.xlua
https://github.com/M66B/XPrivacyLua
https://forum.xda-developers.com/t/app-xposed-6-0-xprivacylua-android-privacy-manager.3730663/
Universal SafetyNet Fix:
https://github.com/kdrag0n/safetynet-fix
https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
InitRcHider
https://forum.xda-developers.com/t/module-initrchider.4369285/
Magisk Hide Props Config:
https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf
https://forum.xda-developers.com/t/...safetynet-prop-edits-and-more-v6-1-2.3789228/
Hide My Applist:
https://github.com/Dr-TSNG/Hide-My-Applist
RootCloak:
https://repo.xposed.info/module/com.devadvance.rootcloak
https://repo.xposed.info/module/com.devadvance.rootcloak2
https://github.com/devadvance/rootcloak
https://github.com/devadvance/rootcloakplus
https://forum.xda-developers.com/t/...e-root-from-specific-apps-2014-01-14.2574647/
MomoHider:
https://github.com/canyie/Riru-MomoHider
RiruUnshare:
https://github.com/vvb2060/riru-unshare
XPrivacy:
https://repo.xposed.info/module/biz.bokhorst.xprivacy
https://github.com/M66B/XPrivacy
https://forum.xda-developers.com/t/xprivacy-the-ultimate-yet-easy-to-use-privacy-manager.2320783/
Some Useful Content For Checking Detections:
VD Infos:
https://forum.xda-developers.com/t/VDInfos.4097379/
Momo:
https://t.me/magiskalpha/517
XposedDetector:
https://github.com/vvb2060/XposedDetector
MagiskDetector:
https://github.com/vvb2060/MagiskDetector
ApplistDetector:
https://github.com/Dr-TSNG/ApplistDetector
NativeDetector:
https://github.com/LSPosed/NativeDetector
YASNAC - SafetyNet Checker:
https://github.com/RikkaW/YASNAC/releases

Reserved.

It appears July patch defeated Magisk Deny List and USNF.
No Netflix install/update
No Wallet/Pay

mingkee said:
It appears July patch defeated Magisk Deny List and USNF.
No Netflix install/update
No Wallet/Pay
Click to expand...
Click to collapse
hi, good idea! So I use magisk 25.2, denylist, zygisk, shamiko.
i'm on LOS 19.1 on samsung galaxy tab a (sm-t 550). Hiding root works, but MOMo detects 'abnormal' circumstances (see attachment). Banking apps (S pushTan und VR securego crashes.
i renamed TWRP folder, Magisk and TitaniumBackup, freezed magisk app, I deactivated Developer options and debugging - guess I tried everything Didgeridoohan advices. cleared cache and data - the banking apps won't work. What can I do further?

abagm said:
hi, good idea! So I use magisk 25.2, denylist, zygisk, shamiko.
i'm on LOS 19.1 on samsung galaxy tab a (sm-t 550). Hiding root works, but MOMo detects 'abnormal' circumstances (see attachment). Banking apps (S pushTan und VR securego crashes.
i renamed TWRP folder, Magisk and TitaniumBackup, freezed magisk app, I deactivated Developer options and debugging - guess I tried everything Didgeridoohan advices. cleared cache and data - the banking apps won't work. What can I do further?
Click to expand...
Click to collapse
Try NOT to use Shamiko (crashes in some/many apps), try this for an alternative

Stillhard said:
Try NOT to use Shamiko (crashes in some/many apps), try this for an alternative
Click to expand...
Click to collapse

abagm said:
okay. did so, loaded initRcHider as well - no luck. Denylist seems working, Momo does not mention magisk or zygisk or lsposed. Maybe SELinux permissive is the culprit? Seems that banking apps have got too strict - LOS 17 and pure old magisk hide did the job. Broken TEE, Seccomp???
Click to expand...
Click to collapse
Custom ROMs will always shown as abnormal because they are abnormal.
If they were not abnormal, they could not work.
About seliux permissive, this will always be a big red alert.

Hi @VD171
Thanks for creating this thread!
Please keep up the good work
abagm said:
Seems that banking apps have got too strict
Click to expand...
Click to collapse
If banking app is too intrusive then you can simply access your online banking website through browser app and do your transactions from there
Browser app will never check if you got root or if your selinux is permissive or other things! Because it's none of its business!

lebigmac said:
Hi @VD171
Thanks for creating this thread!
Please keep up the good work
If banking app is too intrusive then you can simply access your online banking website through browser app and do your transactions from there
Browser app will never check if you got root or if your selinux is permissive or other things! Because it's none of its business!
Click to expand...
Click to collapse
lebigmac said:
Hi @VD171
Thanks for creating this thread!
Please keep up the good work
If banking app is too intrusive then you can simply access your online banking website through browser app and do your transactions from there
Browser app will never check if you got root or if your selinux is permissive or other things! Because it's none of its business!
Click to expand...
Click to collapse
You're right- I can access the online banking via browser. But to do transaction, I need apps - that's why I complain 🫠

VD171 said:
Custom ROMs will always shown as abnormal because they are abnormal.
If they were not abnormal, they could not work.
About seliux permissive, this will always be a big red alert.
Click to expand...
Click to collapse

lebigmac said:
Hi @VD171
Thanks for creating this thread!
Please keep up the good work
Click to expand...
Click to collapse
Thank you, sir. I will help always as I can
lebigmac said:
If banking app is too intrusive then you can simply access your online banking website through browser app and do your transactions from there
Browser app will never check if you got root or if your selinux is permissive or other things! Because it's none of its business!
Click to expand...
Click to collapse
We need ways for distinguishing unexperienced users and users who assume full responsibility for their own use.
Apps delivers many new possibilities and services, banking through browser app isn't enough actually.

abagm said:
Thank you for this thread!
Yeah, that is true. i hoped there are ways to disguise the complaints of MOMo (for example such a thing like renaming addon.d in /system to disguise "running custom rom"). And LOS 17 did run the banking apps, so I wanted to understand the difference.
Click to expand...
Click to collapse
Are you having problem with any specific app?

VD171 said:
Thank you, sir. I will help always as I can
We need ways for distinguishing unexperienced users and users who assume full responsibility for their own use.
Apps delivers many new possibilities and services, banking through browser app isn't enough actually.
Click to expand...
Click to collapse
It's true - doing your financial transactions through the web browser feels a little bit prehistoric to say the least but it works and you don't need to waste your precious time trying to hide your root and other customizations from some intrusive apps that shouldn't be intruding on your privacy like that in the first place
I know it's not the perfect solution but the more solutions we have to avoid this annoying safetynet 'feature' altogether the better. I am so happy that I don't need to bother with this useless safetynet 'feature'

lebigmac said:
It's true banking through browser app is a little bit prehistoric but it works and you don't need to waste your precious time trying to hide your root and other customizations from some intrusive apps that shouldn't be intruding on your privacy like that
I know it's not the perfect solution but the more solutions we have to overcome these annoying safetynet requirements the better. I am so happy that I don't need to bother with all this useless safetynet this safetynet that
Click to expand...
Click to collapse
Any type of detection can be bypassed.
Even native methods can be bypassed, because Android app's run on java.
So, at sometime and somewhere, results are given to/from java.

VD171 said:
Are you having problem with any specific app?
Click to expand...
Click to collapse

abagm said:
Yes, those banking apps BestSign (it detects root immediatly but can be used), S-PushTAN and VR-SecureGo. these three worked on rooted 'unnormal' LOS 17.1 but don't work now in 19.1. Momo said magisk and LSPosed were hidden butcomplains about that unnormal enviroment.
Click to expand...
Click to collapse
When does exactly the app crash?
May you attach some screenshots?
I've tried all them.
All them are working fine for me.

VD171 said:
When does exactly the app crash?
May you attach some screenshots?
I've tried all them.
All them are working fine for me.
Click to expand...
Click to collapse

---throwing in the towel - can't get it work as I wanted to. WIll return to the working version of ROM - and be proud to be outdated ...