SafetyNet checks (CTS and basic) both failing - LOS16 w/ microG - Magisk

Hi, can someone please help? I can't get SafetyNet check to pass in Magisk Manager, not even basicIntegrity.
I have tried everything here:
https://www.didgeridoohan.com/magisk/MagiskHideSafetyNet
... and here (in addition to digging around XDA forums)
https://www.didgeridoohan.com/magisk/MagiskInstallationIssues
I have a oneplus One running LineageOS 16 with microG pre-installed (https://lineage.microg.org/)
Specific troubleshooting steps taken, each step taken with TWO device restarts after:
1) Magisk Manager is hidden (via Magisk Hide in the Manager)
2) I am only using Magisk modules i.e. no BusyBox, xposed, etc.
3) After having issues I tried disabling all Magisk modules and rebooting twice
4) I tried the osm0sis unSU script, I flashed it in TWRP then deleted Dalvik/cache and rebooted twice, only Magisk was found
5) Developer options/USB debugging are both disabled
6) I froze in Titanium Backup any app needing root then hid Titanium Backup in Magisk (do I need to fully uninstall Titanium Backup and/or other apps with root?)
7) I tested magiskHide with a root checker app - it works, the root checker reports successful root then I hide the root checker with MagiskHide and when re-checking root then fails as expected.
8) I tried to reset fingerprint props but I reverted the settings back when this didn't help. Does anyone have any more info about this please? Unfortunately I already altered the props on my OPO and I don't have stock Cyanogen ROM available to me (it's spyware anyway!!)
A few related question please:
1) I don't need to use Systemizer plugin anymore, correct? As MagiskHide can handle this now? Or do I?
2) I tried a few SafetyNet fixes/modules but none worked... should I try more i.e. PetNoire's SafetyNet Spoofer? https://forum.xda-developers.com/apps/magisk/universal-safetynet-fix-magisk-17-t3840680/page5
Unfortunately I am not sure that I can attach a logcat output file as I am brand-new to XDA and have <10 posts.
Thank you all so much!

ertrink3n said:
I have a oneplus One running LineageOS 16 with microG pre-installed (https://lineage.microg.org/)
Click to expand...
Click to collapse
I believe this might be the key to your problem. I'm not entirely sure, but I think there might be issues passing SafetyNet on MicroG.
Try looking through MicroG threads/forums for info and help rather than Magisk.

Didgeridoohan said:
I believe this might be the key to your problem. I'm not entirely sure, but I think there might be issues passing SafetyNet on MicroG.
Try looking through MicroG threads/forums for info and help rather than Magisk.
Click to expand...
Click to collapse
Micro G can't pass safety net no more cause the Droid helper hasn't been updated....
([emoji3590]09-09-18[emoji3590])

Thank you for the confirmation @PoochyX, that's what I thought, but since I don't use or keep track of MicroG I wasn't sure.
@ertrink3n That's your answer.

Related

Cant find Enable Busybox in Magisk settings and ctsProfile not succesfull

Hello.
After many many reinstall of magisk I still cant find "Enable Busybox" in Magisk settings
I have "magisk core only mod" , "Magisk Hide" and "Systemless Host" BUT "Enable Busybox" is missing/not visible in my settings of Magisk.
I also got error when Safety Net check. Only bacisintegry is successfull. ctsProfile do not pass the test.
But, I can still download and update payed and free apps from Google Play Store.
Anyone what to do for getting "Enable Busybox" to be visible in my Magisk settings?
And, since ctsProfile not pass safetyscheck..can that be because for that missing "Enable Busybox" in settings?
Running lineageOS 14.1 and samsung J5 ( 2016 ) , SM-J510FN
Magisk 14.0
Regards
Rolf
Busybox: There is no toggle like that (hasn't been for some time). There's a Busybox module in the Downloads section of the Manager. Use that.
The failed ctsProfile check doesn't have anything to do with Busybox. Take a look here for more info on passing SafetyNet: https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
You don't need to pass SafetyNet to be able to download and install most apps. There are a few who use the Certified status in the Play store (Netflix) and some that won't function if you don't pass SafetyNet (Android Pay).
Didgeridoohan said:
Busybox: There is no toggle like that (hasn't been for some time). There's a Busybox module in the Downloads section of the Manager. Use that.
The failed ctsProfile check doesn't have anything to do with Busybox. Take a look here for more info on passing SafetyNet: https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
You don't need to pass SafetyNet to be able to download and install most apps. There are a few who use the Certified status in the Play store (Netflix) and some that won't function if you don't pass SafetyNet (Android Pay).
Click to expand...
Click to collapse
Thanks for responding and a celearly anwer Didgeridoohan
I will check that link about safetynet. Thanks
Anyway, I guess there are no point/neccesary installing Busybox module in Magisk when I already have Bysybox Pro installed on my device?
I have noticed that my Netflix will not load so hope I got that safetyNet up running in Magisk.
Regards
Rolf
[email protected] said:
Thanks for responding and a celearly anwer Didgeridoohan
I will check that link about safetynet. Thanks
Anyway, I guess there are no point/neccesary installing Busybox module in Magisk when I already have Bysybox Pro installed on my device?
I have noticed that my Netflix will not load so hope I got that safetyNet up running in Magisk.
Regards
Rolf
Click to expand...
Click to collapse
SafetyNet Fixed by doing this:
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
BUT, still Netflix Error/not compatibel vs my device when download from Google Play. Got a message in that error message downloading Netflik from Netflix's site. Doing that..and Netflix up running
Thanks again Didgeridoohan for pointing me in the right direction
Regards
Rolf
I thought with the newest version of magisk, busy box is integrated already? I ran a test and it states I have it and it's active but certain apks tell me it's not present in device when installing. Should I setup module in magisk also? Don't want to double stack anything.
SlimPickens89 said:
I thought with the newest version of magisk, busy box is integrated already? I ran a test and it states I have it and it's active but certain apks tell me it's not present in device when installing. Should I setup module in magisk also? Don't want to double stack anything.
Click to expand...
Click to collapse
There is a busybox integrated into Magisk, for use by Magisk...
If you wan't busybox for the rest of your system, install the busybox module from the Magisk repo.
Didgeridoohan;73790549There's a Busybox module in the Downloads section of the Manager. Use that.
The failed ctsProfile check doesn't have anything to do with Busybox. Take a look here for more info on passing SafetyNet: [url said:
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417[/url]
You don't need to pass SafetyNet to be able to download and install most apps. There are a few who use the Certified status in the Play store (Netflix) and some that won't function if you don't pass SafetyNet (Android Pay).
Click to expand...
Click to collapse
Actually, in my case, the ctsProfile check does correlate with the busybox module. I am trying a new ROM on my galaxy s7 which doesn't contain a busybox, thus Viper4Android does not want to install its driver (and Busybox checker says "no"). ctsProfile did pass. After I downloaded the BusyBox module in Magisk Manager, cts doesn't pass, but basic integrity still does.
Peter.1997 said:
Actually, in my case, the ctsProfile check does correlate with the busybox module. I am trying a new ROM on my galaxy s7 which doesn't contain a busybox, thus Viper4Android does not want to install its driver (and Busybox checker says "no"). ctsProfile did pass. After I downloaded the BusyBox module in Magisk Manager, cts doesn't pass, but basic integrity still does.
Click to expand...
Click to collapse
If you only need busybox for Viper4Android, try the awesome ViPER4Android FX module (available in the Magisk repo). It doesn't need busybox...
Yup, only vor Viper. I already installed this module (and also the seperate one for Magisk 14.0+), but the Viper app always wants to install the driver on its own again..
Peter.1997 said:
Yup, only vor Viper. I already installed this module (and also the seperate one for Magisk 14.0+), but the Viper app always wants to install the driver on its own again..
Click to expand...
Click to collapse
Judging from your two posts, I'd say something's wrong with your Magisk installation... Magisk log and magisk_debug.log (from /data) might show something interesting.
Jumping onto that thread as it seems to fit quite well.
If a Moderator feels the need for a new topic pls let me know.
Facts:
Android 6 with Magisk 12 and SuperSu 2.79/2.82 and Xposed 87 running fine for quite a time.
Only Magisk manager was updated inbetween a few times
Now with a few free days after christmas and all the new releases out, i went for an update session.
- cleaned supersu with 0smosis unSu
- TWRP flashed clean stock boot.img
- TWRP flashed Magisk 15.1. All good and seemed to work
Then i wanted to update to xposed v89.
The installer failed with "updater process ended with error 1"
Dug into the TWRP-Logs and found the following:
Code:
/tmp/updater: line 91: /data/adb/magisk/busybox: not found
! Unable to extract zip file!
Now it was time to inspect the Magisk-Log:
Code:
12-29 23:56:59.699 269 269 I Magisk : * Setting up internal busybox
12-29 23:56:59.700 273 273 E Magisk : execvpe failed with 2: No such file or directory
Interesting.
As i knew about the changes from 12->15 regarding internal busybox, i cleaned the Magisk Manager Cache as recommended somewhere
and wanted to go for the official module "Busybox for Android NDK 1.27.2".
After installing it showed up as "not available - please reboot"
I went for the logs again and found the following:
Code:
Installing Busybox_for_Android_NDK-1.27.2.zip
Busybox Installer Script by osm0sis @ xda-developers
Mounting...
Extracting files...
update-binary[109]: unzip: not found
Also a quick check of /data/magisk showed no signs of busybox.
Any hints where to dig deeper to get busybox (and unzipping in TWRP back ??
Time, a few Skills and Tools available.
Didnt attach the logs, cause those above are imho the only relevant facts.
If somebody needs sth specific to rule sth out, i will of course happily deliver them.
Thank everybody and keep up the good work !!
Sebastl said:
Jumping onto that thread as it seems to fit quite well.
If a Moderator feels the need for a new topic pls let me know.
Facts:
Android 6 with Magisk 12 and SuperSu 2.79/2.82 and Xposed 87 running fine for quite a time.
Only Magisk manager was updated inbetween a few times
Now with a few free days after christmas and all the new releases out, i went for an update session.
- cleaned supersu with 0smosis unSu
- TWRP flashed clean stock boot.img
- TWRP flashed Magisk 15.1. All good and seemed to work
Then i wanted to update to xposed v89.
The installer failed with "updater process ended with error 1"
Dug into the TWRP-Logs and found the following:
Code:
/tmp/updater: line 91: /data/adb/magisk/busybox: not found
! Unable to extract zip file!
Now it was time to inspect the Magisk-Log:
Code:
12-29 23:56:59.699 269 269 I Magisk : * Setting up internal busybox
12-29 23:56:59.700 273 273 E Magisk : execvpe failed with 2: No such file or directory
Interesting.
As i knew about the changes from 12->15 regarding internal busybox, i cleaned the Magisk Manager Cache as recommended somewhere
and wanted to go for the official module "Busybox for Android NDK 1.27.2".
After installing it showed up as "not available - please reboot"
I went for the logs again and found the following:
Code:
Installing Busybox_for_Android_NDK-1.27.2.zip
Busybox Installer Script by osm0sis @ xda-developers
Mounting...
Extracting files...
update-binary[109]: unzip: not found
Also a quick check of /data/magisk showed no signs of busybox.
Any hints where to dig deeper to get busybox (and unzipping in TWRP back ??
Time, a few Skills and Tools available.
Didnt attach the logs, cause those above are imho the only relevant facts.
If somebody needs sth specific to rule sth out, i will of course happily deliver them.
Thank everybody and keep up the good work !!
Click to expand...
Click to collapse
Sounds like your TWRP isn't up to the job... It's probably too old (info which would have been in the log ) or otherwise missing some features...
Updating TWRP or letting the Manager patch a boot image that you then flash manually are two possible solutions.
Thank you very much for the quick reply Didgeridoohan.
That is of course water on the mills of the "always include logs" - people. Apparently for a reason
TWRP Version is/was 3.02.
After you suggested patching the image from Magisk Manager, i tried that and got a quick and dirty "Failed".
But i realized that now the option "Direct Install (recommended)" was available.
It wasnt when i did the initial setup.
As i had nothing to loose, i tried that to reinstall and after the next reboot -
Bingo! Now the busybox binary is/was available and therefore the Busybox Module and consequently also Xposed respective everything which depends on unzipping/busybox works.
Strange - but somehow problem solved.
I didnt see anything in the TWRP changelogs from 3.02 up to 3.2.1 - but hey...
Hope that helps someone.
Greetings and a nice 2018 !

[Help] Magisk hide works only when retoggled

Details: Huawei P20 Pro running 9.0. Magisk Manager v7 (latest), Magisk v18.2 (latest canary) original package name. Safety net passed.
I tested to make sure that magisk hide is working properly on my device. https://play.google.com/store/apps/details?id=com.revolut.revolut&hl=en_GB. This app does not have fingerprint login enabled without magisk hide. Hence when I turn off magisk hide, you can't use fingerprint to login into the app. When I turn it back on, fingerprint login works. Also my bank app works.
Here is the problem. https://play.google.com/store/apps/details?id=com.starlingbank.android&hl=en_GB. This app does not seem to run even when magisk hide is on. Here's the kicker, even though magiskhide has been toggled and confirmed working, upon opening this app it will show the usual "device not secure/rooted" message. After this it somehow disable magiskhide as my revolut app no longer prompts for fingerprint and my bank app stops working.
I have to go back into magisk and retoggle magisk hide for it to work again. (However the starling bank app still fails the root check)
I'm really really frustrated now and will appreciate any help.
UDPATE: I did some stuff from https://forum.xda-developers.com/apps/magisk/how-to-bypass-lloyds-root-detection-t3837206, the adaway host list. Added MagiskHide Props Config. I also set tasker to toggle magiskhide whenever I turn on my screen. Seems to work more consistently for now
Check the Magisk main thread and Github, there is a known problem with Magisk Hide in the 18.x. I went back to 17.x which work for me without any problems.
lambstone said:
Details: Huawei P20 Pro running 9.0. Magisk Manager v7 (latest), Magisk v18.2 (latest canary) original package name. Safety net passed.
I have to go back into magisk and retoggle magisk hide for it to work again. (However the starling bank app still fails the root check)
I'm really really frustrated now and will appreciate any help.
Click to expand...
Click to collapse
If Magisk Hide Of Magisk 18.x Is Working Intermittently (Which Means Also The Device Will Not Pass The SafetyNet Sometimes), Try To Use The Module Of Microsoft Intune Company Portal Hider Which Includes Also The Functionality Of Re-Enabling Magisk Hide Every 5 Min. For Magisk 18.x From This Thread https://forum.xda-developers.com/apps/magisk/module-microsoft-intune-company-portal-t3780451. Awaiting Your Feedback.
Dreamer(3MF) said:
The Functionality Of Re-Enabling Magisk Hide Every 5 Min
Click to expand...
Click to collapse
Doesn't this cause battery drain?
akxak said:
Check the Magisk main thread and Github, there is a known problem with Magisk Hide in the 18.x. I went back to 17.x which work for me without any problems.
Click to expand...
Click to collapse
Hi, some questions. Do I have to install also the Manager v6.10 to install Magisk v17.3? Or can I leave the last Manager? Then, I uninstall Magisk from the app and them I flash the v17.3 from (temporary) TWRP, is it correct?
Simone_ASR said:
Hi, some questions. Do I have to install also the Manager v6.10 to install Magisk v17.3? Or can I leave the last Manager? Then, I uninstall Magisk from the app and them I flash the v17.3 from (temporary) TWRP, is it correct?
Click to expand...
Click to collapse
The latest Magisk Manager dropped support for Magisk 17 or older, you need the matching Manager..
akxak said:
The latest Magisk Manager dropped support for Magisk 17 or older, you need the matching Manager..
Click to expand...
Click to collapse
Thank you so much for your fast reply!
In the exact same situation as OP P20 Pro (maybe except im on LOS 16)
Magisk seems to be working fine passing safteynet and Root Beet finding nothing but yet the Starling Bank app and the Arriva Ticket app both figure out my phone is rooted after a while and lock out.
Had exact problem with Starling app with magisk hide and app on hide list. Turned out to be a direct build.prop modification so after resetprop -p all good now.
gkornaks said:
Had exact problem with Starling app with magisk hide and app on hide list. Turned out to be a direct build.prop modification so after resetprop -p all good now.
Click to expand...
Click to collapse
Can you expand on this a bit?
I've downloaded Magiskhide props config, and what do I have to do now?
For me, starling always works for couple of days and then it locks me out via the root screen.
republicj said:
Can you expand on this a bit?
I've downloaded Magiskhide props config, and what do I have to do now?
For me, starling always works for couple of days and then it locks me out via the root screen.
Click to expand...
Click to collapse
I modified a build.prop directly before magisk install so compromised the system partition. I've used resetprop to mask it. Like you I'm occasionally getting root warning as well and have to re-authorise so magisk hide in 18.1 not perfect as mentioned a lot in a forum.
Hi,
it seams that the problem is still there. I have to retoggle Magisk Hide at every reboot of the phone.
Is there any workaround or any ETA on the fix?
Thank you.
No one?
Never ask for ETAs...
https://github.com/topjohnwu/Magisk/issues/1654
Didgeridoohan said:
Never ask for ETAs...
https://github.com/topjohnwu/Magisk/issues/1654
Click to expand...
Click to collapse
Ok, I'm sorry about that , I just needed a confirmation that the problem was still there. Thank you for the reply!
Yes it's till here. I cannot login to Arriva bus app with Magisk 20.1.

Many app detecting root even saftynet pass

I am using oneplus 6 with latest oos magisk 19.3
Banking app like sbi anywhere, icici detecting root can't use upi.
Also adadhar app detecting root event safety net pass already done magisk hide
Can some help me there or use other versions of magisk
Please help
android_smater said:
I am using oneplus 6 with latest oos magisk 19.3
Banking app like sbi anywhere, icici detecting root can't use upi.
Also adadhar app detecting root event safety net pass already done magisk hide
Can some help me there or use other versions of magisk
Please help
Click to expand...
Click to collapse
Use Hide Magisk manager in settings or Core only mode.
Sent from my MI 8 using Tapatalk
Dexer125 said:
Use Hide Magisk manager in settings or Core only mode.
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
Didn't work either. I guess will have to wait for an update. I have tried so far:
Settings > Magisk Core Only More - On
Magisk Hide - Check against the banking app
Clear app cache
Reboot
Also - Magisk v19.3, Magisk Manager v7.3.1(222)
gagan007 said:
Didn't work either. I guess will have to wait for an update. I have tried so far:
Settings > Magisk Core Only More - On
Magisk Hide - Check against the banking app
Clear app cache
Reboot
Also - Magisk v19.3, Magisk Manager v7.3.1(222)
Click to expand...
Click to collapse
disable developer mode?
and you need to hide magisk manager itself.not just magisk hide.
Try executing
Code:
su -c chmod 000 /proc/net/unix
in a terminal. Several banking apps now use a very stupid and shaky root detection heuristic that is circumvented in this way.
(see https://github.com/Ingan121/UDSBypass).
A banking app on my phone (keytradebank, belgian bank) worked fine with Magisk Hide but after an update stopped working.
Disabling read access to /proc/net/unix did the trick for me!
Looked it up, this rootbeerFresh code is really brain-dead, even the presence of busybox will make isRooted() return true
No concern for false positives at all.
el_perro said:
A banking app on my phone (keytradebank, belgian bank) worked fine with Magisk Hide but after an update stopped working.
Disabling read access to /proc/net/unix did the trick for me!
Looked it up, this rootbeerFresh code is really brain-dead, even the presence of busybox will make isRooted() return true
No concern for false positives at all.
Click to expand...
Click to collapse
Remember that app says it COULD be root.
If anyone is paying attention to it yet.
Also
https://www.didgeridoohan.com/magis...and_other_apps_wont_install_or_doesnt_show_up
Busybox
Some apps detect Busybox and see this as a sign of your device being compromised (rooted). Magisk should be able to hide any Busybox installed as a Magisk module. osm0sis has a great Busybox module available in the Magisk repo (install from the Magisk Manager, under "Downloads").
Figuring out if an app has dependencies, looks for "sensitive props", Busybox, etc
It can be tricky figuring out if an app is dependent on another app or process for detecting root, expects certain prop values, doesn't like Busybox or whatever is triggering a root warning within the app. Apart from trying one thing/prop at a time, finding this out could mean you have to decompile the apk to look at the source code (use search), grab a logcat when the app is detecting root, etc.
Detecting apps requiring root
There are apps that detect known apps that require root and refuse to work properly or even start if that is the case. Usual suspects include (but aren't limited to) busybox apps, Xposed installer, root hiding apps, etc.
This can be worked around by uninstalling or possibly freezing (Titanium Backup can do this, among others) the offending root app when you need to use an app detecting root apps and reinstalling/unfreezing it afterwards. Cumbersome, but it might work. There are also some Xposed modules that can hide apps from other apps, but having Xposed installed might cause other issues with tampering detection...
@mrspeccy Thank you for pointing out that workaround. Works for me too for the Keytrade app
el_perro said:
A banking app on my phone (keytradebank, belgian bank) worked fine with Magisk Hide but after an update stopped working.
Disabling read access to /proc/net/unix did the trick for me!
Looked it up, this rootbeerFresh code is really brain-dead, even the presence of busybox will make isRooted() return true
No concern for false positives at all.
Click to expand...
Click to collapse
How did you do that?
su -c chmod 000 /proc/net/unix didn't work for me.
robuser007 said:
How did you do that?
su -c chmod 000 /proc/net/unix didn't work for me.
Click to expand...
Click to collapse
yes, in a terminal on your phone or using 'adb shell'
be aware it's not a permanent fix, a reboot will restore the old permissions on /proc/net/unix
so you have to remove read access after every reboot.
Quite clumsy.
To make this easier on the go, I installed termux, created in the home directory a small file 'hide' with the one-liner,
Code:
su -c chmod 440 /proc/net/unix
Note: 000 works just as well, but 440 is closer to the original permission and works too.
so after a reboot i open termux terminal and type the command
Code:
. hide
gagan007 said:
Didn't work either. I guess will have to wait for an update. I have tried so far:
Settings > Magisk Core Only More - On
Magisk Hide - Check against the banking app
Clear app cache
Reboot
Also - Magisk v19.3, Magisk Manager v7.3.1(222)
Click to expand...
Click to collapse
Thanks it work...
Got that app working successfully today. Hiding Magisk itself worked I guess. I locked bootloader also.
android_smater said:
I am using oneplus 6 with latest oos magisk 19.3
Banking app like sbi anywhere, icici detecting root can't use upi.
Also adadhar app detecting root event safety net pass already done magisk hide
Can some help me there or use other versions of magisk
Please help
Click to expand...
Click to collapse
Try these...
1. From your magisk, install these 2 modules: Riru - Core, and Riru - EdXposed (Sandbox or Yahfa is okay]
2. Reboot your device to activate both modules.
3. Install Xposed Installer APK by DVDandroid. You can get it here: https://dl-xda.xposed.info/modules/d...v33_36570c.apk
4. Reboot to activate the Xposed Installer app
5. Inside Xposed Installer app, go to downloads and install the HiddenCore Module.
6. Reboot and go back to Magisk, and hide.
7. Test to see if everything is now okay.
wittymav said:
Try these...
1. From your magisk, install these 2 modules: Riru - Core, and Riru - EdXposed (Sandbox or Yahfa is okay]
2. Reboot your device to activate both modules.
3. Install Xposed Installer APK by DVDandroid. You can get it here: https://dl-xda.xposed.info/modules/d...v33_36570c.apk
4. Reboot to activate the Xposed Installer app
5. Inside Xposed Installer app, go to downloads and install the HiddenCore Module.
6. Reboot and go back to Magisk, and hide.
7. Test to see if everything is now okay.
Click to expand...
Click to collapse
Nope! It Doesn't Work With SBI YONO Or BHIM.
My Cofidis app also keeps detecting root.
Have latest version magisk, latest version of magiskmanager and renamed it. Magisk is hidding. App is in magisk hide list.
chmod suggestion did not work
Running latest version of lineageos on my htc u11. I think the issues started when I installed the latest build (11/08).
Any suggestions to fix this?
Same issue here with this app:
https://play.google.com/store/apps/details?id=eu.mobeepass.nfcniceticket
Is there any way to troubleshoot what triggers the root detection?
Ps24u said:
Same issue here with this app:
https://play.google.com/store/apps/details?id=eu.mobeepass.nfcniceticket
Is there any way to troubleshoot what triggers the root detection?
Click to expand...
Click to collapse
Using my app VD INFOS you can see every detectable thing. (Root/Magisk/Xposed/Riru/and others.)
And then you can fix what needs to be fixed.
[APP][v1.10] VD Infos (Package: com.vitaodoidao.vdinfos)
(Para quem fala PORTUGUÊS, o próximo post está totalmente traduzido !) VD Infos v1.10 As we all know, Android is a super powerful and super versatile operating system. What nobody tells you is that all your personal details and confidential...
forum.xda-developers.com

Banking app detects root on multiple devices.

My banking app (PermataMobile X) is detecting root with Safetynet passed and Magisk Manager hidden. I asked some other people to install and see if they can pass the root detection to no avail.
I've tried some little things to narrow down the culprit like:
1. Installed Magisk Manager without flashing the magisk 20.4 zip file (unrooted). Detected as root. Uninstalling the manager immediately allows bank app to work.
2. Flashed Magisk 20.4 without installing Magisk Manager. Detected as root, obviously.
3. Went back to previous versions of Magisk and Magisk Manager. Still detected as root.
Anyone can give any tips on what else I can try to do?
IcY~ said:
My banking app (PermataMobile X) is detecting root with Safetynet passed and Magisk Manager hidden. I asked some other people to install and see if they can pass the root detection to no avail.
I've tried some little things to narrow down the culprit like:
1. Installed Magisk Manager without flashing the magisk 20.4 zip file (unrooted). Detected as root. Uninstalling the manager immediately allows bank app to work.
2. Flashed Magisk 20.4 without installing Magisk Manager. Detected as root, obviously.
3. Went back to previous versions of Magisk and Magisk Manager. Still detected as root.
Anyone can give any tips on what else I can try to do?
Click to expand...
Click to collapse
If you can pass SafetyNet (cts profile) try to hide :
Magisk Manager with a random name (mandatory) ... and "Your banking app" must be hidden too along with Google Services of course !
There are currently several ways of detecting Magisk that MagiskHide can't circumvent.
If the app isn't using one of those (if it is you'll just have to wait for a possible update to Magisk), you can find some tips and tricks here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Magisk cannot hide:
Other known root apps (see "Detecting apps requiring root"). (Shouldn't be a problem since even with a renamed manager and magisk unflashed it still works.)
Remnants of previous root method, including any root management apps (a good way to remove most remnants of root is osm0sis unSU script). (Magisk is unflashed and app immediately works.)
Unlocked bootloader (see Unlocked bootloader). (Magisk is unflashed and bootloader unlocked, app still works. I also tried custom rom and the stock rom.)
A tripped Samsung Knox counter. (Not a samsung phone.)
Xposed (deactivate it or uninstall). It doesn't matter if it's systemless, Magisk can't hide it. (Never used.)
EdXposed. Detection of EdXposed can sometimes be worked around with newer release of EdXposed and/or features like the EdXposed Manager blacklist. (Never used.)
USB/ADB Debugging (disable under Developer options in Android settings). (Magisk unflashed and debugging on, app works.)
Developer options. (Magisk unflashed and developer options is on, app works.)
Some Magisk modules - Depending on what the module does, it may not be able to be hidden by MagiskHide. (Tried core only mode which should disable all modules, still don't work.)
Some modifications to /system. Make sure to use Magisk modules... (I'm not sure what this means :c)
From that list it looks like it's something from Magisk itself that's tripping the detection :/
Im going bald from this.
IcY~ said:
From that list it looks like it's something from Magisk itself that's tripping the detection :/
Im going bald from this.
Click to expand...
Click to collapse
If you've tested and confirmed everything else, it is very likely that the app is using a detection method that Magisk currently can't hide from.
Solution? Wait for @topjohnwu to possibly update Magisk/MagiskHide (alternatively, don't install Magisk). When? Whenever he feels like it...
Didgeridoohan said:
If you've tested and confirmed everything else, it is very likely that the app is using a detection method that Magisk currently can't hide from.
Solution? Wait for @topjohnwu to possibly update Magisk/MagiskHide (alternatively, don't install Magisk). When? Whenever he feels like it...
Click to expand...
Click to collapse
https://github.com/topjohnwu/Magisk/issues/2406
Looks like someone posted a potential fix. Will wait for it to reach the master branch!
Have you find the workaround? I am using the same app and face same problem. This app last update gives headache
I am hidding root and edxposed using Island and installing intune inside the sandbox. Maybe the same will be with bank apps.
@kubis111
i'm happy for you, but please...this isn't your thread so do not OOT, OP problem isn't solving yet
---------- Post added at 11:46 AM ---------- Previous post was at 11:03 AM ----------
Tomek0000 said:
I am hidding root and edxposed using Island and installing intune inside the sandbox. Maybe the same will be with bank apps.
Click to expand...
Click to collapse
can you share the apps link?
Any updates on this banking app? I've tried many TaiChi Magisk, Sudohide and Zuper module but no success.
ctsProfile all green, Rootbeer Fresh all green.
citi app also detected my rooted device( Mi 8 Pro) after update , even hide the App ..useless....
Heatexplorer said:
citi app also detected my rooted device( Mi 8 Pro) after update , even hide the App ..useless....
Click to expand...
Click to collapse
Had the same problem. Updated magisk manager and fixed it (even before updating my modules).
Anyone lucky on it? What about BBVA Spain app?
IcY~ said:
My banking app (PermataMobile X) is detecting root with Safetynet passed and Magisk Manager hidden. I asked some other people to install and see if they can pass the root detection to no avail.
I've tried some little things to narrow down the culprit like:
1. Installed Magisk Manager without flashing the magisk 20.4 zip file (unrooted). Detected as root. Uninstalling the manager immediately allows bank app to work.
2. Flashed Magisk 20.4 without installing Magisk Manager. Detected as root, obviously.
3. Went back to previous versions of Magisk and Magisk Manager. Still detected as root.
Anyone can give any tips on what else I can try to do?
Click to expand...
Click to collapse
Have you found a solution? With latest Permata and Magisk (23) the banking app still does not work...
timofonic said:
Anyone lucky on it? What about BBVA Spain app?
Click to expand...
Click to collapse
For me work
IcY~ said:
My banking app (PermataMobile X) is detecting root with Safetynet passed and Magisk Manager hidden. I asked some other people to install and see if they can pass the root detection to no avail.
I've tried some little things to narrow down the culprit like:
1. Installed Magisk Manager without flashing the magisk 20.4 zip file (unrooted). Detected as root. Uninstalling the manager immediately allows bank app to work.
2. Flashed Magisk 20.4 without installing Magisk Manager. Detected as root, obviously.
3. Went back to previous versions of Magisk and Magisk Manager. Still detected as root.
Anyone can give any tips on what else I can try to do?
Click to expand...
Click to collapse
Found a solution, but can't publish yet. Excuse me
Spartacus500 said:
Found a solution, but can't publish yet. Excuse me
Click to expand...
Click to collapse
Why?
hallo dare said:
Why?
Click to expand...
Click to collapse
So I ran the test quickly and it turns out that it works, for those who are interested, I will provide a solution, but a little later.
I managed to make it work,
Spartacus500 said:
For me work
Click to expand...
Click to collapse
Spartacus500 said:
For me work
Click to expand...
Click to collapse
No idea how. I'm worried about that Knox logo these days, but we'll..
Thanks!
IcY~ said:
My banking app (PermataMobile X) is detecting root with Safetynet passed and Magisk Manager hidden. I asked some other people to install and see if they can pass the root detection to no avail.
I've tried some little things to narrow down the culprit like:
1. Installed Magisk Manager without flashing the magisk 20.4 zip file (unrooted). Detected as root. Uninstalling the manager immediately allows bank app to work.
2. Flashed Magisk 20.4 without installing Magisk Manager. Detected as root, obviously.
3. Went back to previous versions of Magisk and Magisk Manager. Still detected as root.
Anyone can give any tips on what else I can try to do?
Click to expand...
Click to collapse
Sorry to be just now, but to the point of solution to this,
1. Install the disable services app and disable a process called "S17"
2. Done

What is the go-to replacement for MagiskHide & the central module repo?

I just realized there was a new public Magisk release yesterday, v24, and reading through the changes I see there are two that kind of impact me: MagiskHide and the central module repository removals.
So far I had been using MagiskHide because of its ease of use, list apps, tick box, and that's it (I haven't encountered apps that detected Magisk or root status, although I know it's insufficient for some). For modules, for example, the one that moves user certs to the system store, I just searched directly from the Magisk app and it was all good as well.
But things change from now on with those things being deprecated and removed and because there isn't much to go about in the release notes I was wondering if someone could direct me to the way of doing things now.
- What's the most apt, prevalent, or recommended replacement for MagiskHide? From the release notes I gather its a module, but I'm clueless as to which one or whether there are more than one option.
- If searching for mods and directly installing them is not available through the app, is there anything like it? Or is it all manual now? I.e. look for a module around the net, download it, copy it / decompress it somewhere in the device and install it.
Thanks for everything!
KaoDome said:
I just realized there was a new public Magisk release yesterday, v24, and reading through the changes I see there are two that kind of impact me: MagiskHide and the central module repository removals.
So far I had been using MagiskHide because of its ease of use, list apps, tick box, and that's it (I haven't encountered apps that detected Magisk or root status, although I know it's insufficient for some). For modules, for example, the one that moves user certs to the system store, I just searched directly from the Magisk app and it was all good as well.
But things change from now on with those things being deprecated and removed and because there isn't much to go about in the release notes I was wondering if someone could direct me to the way of doing things now.
- What's the most apt, prevalent, or recommended replacement for MagiskHide? From the release notes I gather its a module, but I'm clueless as to which one or whether there are more than one option.
- If searching for mods and directly installing them is not available through the app, is there anything like it? Or is it all manual now? I.e. look for a module around the net, download it, copy it / decompress it somewhere in the device and install it.
Thanks for everything!
Click to expand...
Click to collapse
[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
Here. First 5 post and you should know all you need
So, I read through that thread. It certainly solved a few issues for me. Like getting safety net, getting a repository, etc.
But it didn't have anything I see to replace magisk hide, even in the Fox Magisk Module Manager.
Do I just need to know other terminology now? Or is there something else I'm missing?
Quantumrabbit said:
So, I read through that thread. It certainly solved a few issues for me. Like getting safety net, getting a repository, etc.
But it didn't have anything I see to replace magisk hide, even in the Fox Magisk Module Manager.
Do I just need to know other terminology now? Or is there something else I'm missing?
Click to expand...
Click to collapse
I don't get it, Magisk Hide is good for passing SafetyNet and you said you got it. Anyway, for SafetyNet you can use the Universal SafetyNet Fix module.
If you meant the hide list, there's now the Deny list. To quote:
The Deny list is similar but instead of hiding Magisk from the process, Magisk is unloaded so there is nothing to hide.
Click to expand...
Click to collapse
Porpet said:
I don't get it, Magisk Hide is good for passing SafetyNet and you said you got it. Anyway, for SafetyNet you can use the Universal SafetyNet Fix module.
If you meant the hide list, there's now the Deny list. To quote:
Click to expand...
Click to collapse
Yes, it's for some banking apps, Concur, and others, none of which have any business checking for root, but all check for Magisk and such in other ways, and prevent usage.
If the deny list is how to do that now, I'll give that a go. Thank you
Quantumrabbit said:
Yes, it's for some banking apps, Concur, and others, none of which have any business checking for root, but all check for Magisk and such in other ways, and prevent usage.
If the deny list is how to do that now, I'll give that a go. Thank you
Click to expand...
Click to collapse
And where did you find the deny list?
fusk said:
And where did you find the deny list?
Click to expand...
Click to collapse
Settings enforce deny list. You need to enable zygisk and reboot prior also in settings.
Also there is an add on module shamiko that has more hide features after you configure denylist
H
toolhas4degrees said:
Settings enforce deny list. You need to enable zygisk and reboot prior also in settings.
Also there is an add on module shamiko that has more hide features after you configure denylist
Click to expand...
Click to collapse
How to add modules shamiko & how to more hide features
Spartacus500 said:
H
How to add modules shamiko & how to more hide features
Click to expand...
Click to collapse
Shamiko is a flashable only need to slash magisk module. You can find it in the magisk alpha thread on telegram. You need to configure denylist first and reboot then turn off the enforce denylist toggle and flash the shamiko module.
If you are using lsposed download hide my applist xposed module and search how to use it if you want more coverage
Pm me if you want links
I'm having a lot of trouble. Duo Mobile (a 2FA app) is still able to detect that I'm rooted. Here's what I've done:
1) Installed Magisk & Manager app version 24.1 (24100)
2) Enabled Zygisk (and rebooted of course)
3) Enabled Enforce DenyList
4) Added com.duosecurity.duomobile and ALL Google Play Services submodules to the DenyList
5) Installed Universal SafetyNet Fix v2.2.1 from https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
6) Hidden the Magisk app
7) Completely uninstalled & reinstalled Duo Mobile (and verified that it's still on the DenyList
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.
Drakinite said:
I'm having a lot of trouble. Duo Mobile (a 2FA app) is still able to detect that I'm rooted. Here's what I've done:
1) Installed Magisk & Manager app version 24.1 (24100)
2) Enabled Zygisk (and rebooted of course)
3) Enabled Enforce DenyList
4) Added com.duosecurity.duomobile and ALL Google Play Services submodules to the DenyList
5) Installed Universal SafetyNet Fix v2.2.1 from https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
6) Hidden the Magisk app
7) Completely uninstalled & reinstalled Duo Mobile (and verified that it's still on the DenyList
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.
Click to expand...
Click to collapse
This is quite weird and definitely shows how different devices handle root detection. I a Samsung S10+ and just installed Magisk 24 with enforce DenyList earlier this week. Today I just installed Duo Mobile and it works fine. I do not have it in the DenyList, and Magisk is not hidden. I use a custom SafetyNet fix that was installed when I originally installed an AIO TWRP/Magisk/SafetyNet fix after unlocking my bootloader. I also fail SafetyNet checks.
Have you tried Shamiko? It didn't help me pass SafetyNet so I removed it.
Unfortunately I don't have any other fixes for you but you can check SafetyNet with apps from the play store, I use YASNAC and SafetyNet 'attest'.
What phone are you using?
Drakinite said:
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.
Click to expand...
Click to collapse
There are SafetyNet checker apps you can download from the Play Store or F-Droid such as YASNAC.
danbest82 said:
Have you tried Shamiko? It didn't help me pass SafetyNet so I removed it.
Unfortunately I don't have any other fixes for you but you can check SafetyNet with apps from the play store, I use YASNAC and SafetyNet 'attest'.
What phone are you using?
Click to expand...
Click to collapse
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
anonymous-bot said:
There are SafetyNet checker apps you can download from the Play Store or F-Droid such as YASNAC.
Click to expand...
Click to collapse
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.
Drakinite said:
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.
Click to expand...
Click to collapse
Get VD Infos and use it to scan your files. You can find it on XDA.
Drakinite said:
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
Click to expand...
Click to collapse
Hmm ok. Like I said shimako didn't work for me either. I'm not sure why Duo is still detecting root. For reference this is what is on my DenyList:
Drakinite said:
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.
Click to expand...
Click to collapse
YASNAC is the replacement for Momo it looks like since Momo is Riru based (https://github.com/canyie/Riru-MomoHider)
simplydat said:
Get VD Infos and use use to scan your files. You can find it in XDA
Click to expand...
Click to collapse
Ok so this one is more helpful, but I'm not sure how to hide these that appeared. Any idea what ro.kernel.qemu.gles is? I looked through my list of installed apps and nothing like that showed up.
Should we switch to private messages to not spam the thread? Or perhaps staying in here can be helpful for those with the same problem?
Drakinite said:
Ok so this one is more helpful, but I'm not sure how to hide these that appeared. Any idea what ro.kernel.qemu.gles is? I looked through my list of installed apps and nothing like that showed up.
Should we switch to private messages to not spam the thread? Or perhaps staying in here can be helpful for those with the same problem?
Click to expand...
Click to collapse
OMG WAIT, it finally worked! I don't know what changed, but Duo is now no longer detecting root. Gotta love when things magically start working when you don't know what changed.
Drakinite said:
OMG WAIT, it finally worked! I don't know what changed, but Duo is now no longer detecting root. Gotta love when things magically start working when you don't know what changed.
Click to expand...
Click to collapse
Awesome. Hope it stays that way!
Hi,
I've switched to the new method with the DenyList & Shamiko (v0.5.0) on OnePlus 6 recently - Magisk (v24.3), however it doesn't seem to hide root from Google Pay. Can it still be a bug with Magisk, when it can't hide system apps? In the changelog of Shamiko it mentioned that it was fixed in Magisk "24102+", I'm not sure what version is this, but I imagine it's not released yet. If so, is there a way of installing this version early?
Thank you!
antivirtel said:
Hi,
I've switched to the new method with the DenyList & Shamiko (v0.5.0) on OnePlus 6 recently - Magisk (v24.3), however it doesn't seem to hide root from Google Pay. Can it still be a bug with Magisk, when it can't hide system apps? In the changelog of Shamiko it mentioned that it was fixed in Magisk "24102+", I'm not sure what version is this, but I imagine it's not released yet. If so, is there a way of installing this version early?
Thank you!
Click to expand...
Click to collapse
Version 24102 would be v24.102. So your Magisk 24.300 is newer.

Categories

Resources