Related
Hi, thanks for reading.
I've used Magisk 17.3 with all my bank apps perfectly, with Magisk hide and Magisk manager hidden.
After update to 18.0 and update manager to 6.1, the bank apps start detecting root status, and stop working.
So, I've flashed back to 17.3 and old manager 6.0.1, and everything's back to working normally.
My system:
Poco F1
LineageOS 16.0 built 27/11/2018
The apps are from Thai's banks:
SCB EASY: detected root, still working
TMB Touch: detected root, stop working
KTB Next: detected root, working partially
If you'd want any log or anything, please also tell me how to get them.
Adios2nd said:
Hi, thanks for reading.
I've used Magisk 17.3 with all my bank apps perfectly, with Magisk hide and Magisk manager hidden.
After update to 18.0 and update manager to 6.1, the bank apps start detecting root status, and stop working.
So, I've flashed back to 17.3 and old manager 6.0.1, and everything's back to working normally.
My system:
Poco F1
LineageOS 16.0 built 27/11/2018
The apps are from Thai's banks:
SCB EASY: detected root, still working
TMB Touch: detected root, stop working
KTB Next: detected root, working partially
If you'd want any log or anything, please also tell me how to get them.
Click to expand...
Click to collapse
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Sent from my Nexus 6P using Tapatalk
Can confirm that this works, thanks.
For me, it started getting detected on 17.x even before updating to 18, right after the banking app (Sparkasse) was updated.
LG G6.
hsiehboss said:
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This didn't work for me. I had to downgrade back to 17.1 to get my banking app working again. Appears that the root detection prevention is a regression in this latest version.
-- SSS
hsiehboss said:
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Click to expand...
Click to collapse
This doesn't work for me.
Did all of these...still got detected.
I have the same problem. Magisk says: ctsProfile: False and Google Pay don't work. Also my Banking App detects root.
I flashed today the latest Los 15 build and the crt false error is till there after flashing magisk 18. The same error is also with 17.4...
Tell me if I'm wrong but I believe we have two different reports: the original report where root is detected, and the ctsProfile/basicIntegrity failing. The second one is a regression fixed by rebooting device (however, it is annoying to reboot 10 times a day because suddenly SafetyNet fails for no reason).
I am using Magisk Hide Props module, and after 18.0 update Santander App detects root, even with Magisk Manager says I pass safetynet
It's happened with my bank app as it detected root & saftynet false and have to downgrade to ver.17.2
Sent from my SM-C900F using Tapatalk
See in install app delete old magisk manager, after install magisk 18.0 new magisk manager rename to manager.
I have same problem. After install v18 magisk, same bank app can detect the system is rooted. Downgrade to v17.2, all bank app become normal.
Same here since Magisk 18 my BankApp (Intesa Sanpaolo) start and says that there is a safety problem and it close, if I choose Magiskhide it doesn't start at all.
SafetyNet check spin without an end.
With Magisk 17.1 and 17.3 no problem at all.
Same problem here, after upgrading to Magisk 18 claiming to better hide root in the history, apps now suddenly detect root.
This affects also the Safety Net check and Google Pay... so far, Root Hiding in 18.0 seems COMPLETELY broken.
A solution would be great.
Later... after downgrading to Magisk 17.2, MagiskHide is working for me again and Safetynet checks succeed. The dev is aware of the problem, an issue is open on the Magisk Github (#907)
After uninstalling and reinstalling my bankapp now works without any problem and doesn't detect root even if is not under Magisk hide
I can confirm the v18 update breaks something and BOTH safety net checks fail. So all apps detect you are rooted, especially bank apps and Get Pay. Downgrading back to v17 restored everything to normal.
The only thing I could think of is the installation method. I did the direct install rather than installing the zip via recovery. Not sure if it makes a difference but I will wait for next release.
I am on a Pixel 2 with Android Pie updated to the Aug 2018 release.
---------- Post added at 12:47 PM ---------- Previous post was at 12:43 PM ----------
Harlock1978 said:
After uninstalling and reinstalling my bankapp now works without any problem and doesn't detect root even if is not under Magisk hide
Click to expand...
Click to collapse
I did not uninstall but tried clearing bank app data and cache and the problem persisted. Magisk still showing all red for safetyNet. Just sharing testing feedback.
@Djtrip83 Did you try just toggling MagiskHide off and on once after updating to v18? Sometimes MagiskHide simply needs a restart after an update...
I did that too. Toggled Hide on and off for all apps. Repackaged Magisk. Turned off USB debugging. Removed modules installed. Tried everything I thought would work. Even restored hosts in case Ad Away affected something on /system.
The only thing I did not do was remove root apps and re-install them to re-grant permissions after the Magisk update. And I wonder now if uninstalling Magisk completely and make a brand new clean install with v18 would work rather than upgrading.
I was at a loss so I downgraded. Sorry I don't have a log to share. However, v17 works fine.
Djtrip83 said:
I did that too. Toggled Hide on and off for all apps. Repackaged Magisk. Turned off USB debugging. Removed modules installed. Tried everything I thought would work. Even restored hosts in case Ad Away affected something on /system.
The only thing I did not do was remove root apps and re-install them to re-grant permissions after the Magisk update. And I wonder now if uninstalling Magisk completely and make a brand new clean install with v18 would work rather than upgrading.
I was at a loss so I downgraded. Sorry I don't have a log to share. However, v17 works fine.
Click to expand...
Click to collapse
We might be misunderstanding each other, but what I'm talking about is simply to go to the Manager settings and change the toggle for MagiskHide to off and then on. No need to do anything to the Hide list or anything else... Did you do that? As I said, that's sometimes something you the to do after an update, but it's rare.
I'm running, on a Huawei Mate 10 PRO, an official Huawei ROM BLA-L29 8.0.0.157 (C432) with no custom kernel or script installed via TWRP. I only have Magisk 18 running with a couple of modules such as Android Pie Fonts, Busybox, DNSCrypt-Proxy 2, Pixel Experience, Youtube Vanced. Root works perfectly on the device with many applications. Now I'm struggling with two things that don't work at all:
- SafetyNet check: it takes many minutes to complete and at the end I get an "Invalid answer"
- Magisk Hide: as soon as I register an application in Magisk Hide I can no longer launch it. Clicking on the icon doesn't do anything.
FYI: On Magisk I have the "Keep forced encryption" set and "Keep AVB 2.0/dm-verity" unchecked. I tried with "Keep AVB 2.0/dm-verity" set and re-installed Magisk but problem is still there.
I looked at Magisk's log but can't see any outstanding issue or error message.
Can someone help me to solve this issue since some banking applications are now blocking me? Thanks a lot.
PS: I tried to use an alternativel fingerprint via the MagiskHide Props Config module but that didn't help.
SafetyNet with Magisk 18.0
alphazo said:
- SafetyNet check: it takes many minutes to complete and at the end I get an "Invalid answer"
- Magisk Hide: as soon as I register an application in Magisk Hide I can no longer launch it. Clicking on the icon doesn't do anything.
Click to expand...
Click to collapse
Hi alphazo,
I had the same problem with my Huawei Mate 10 Pro since I went from 17.3 to 18.0.
I tried several solutions like you, but nothing worked. The only thing that worked was to downgrade to version 17.3, there, everything was functional.
For my part, I completely uninstalled Magisk from my phone and then reinstalled it. After that, everything works perfectly and I have no problems with SafetyNet.
You just have to reconfigure the Magisk Manager application and choose which applications you want to hide.
I hope it will work for you too ! :good:
Thanks a lot for your pointers. I finally got it working and thus even with Magisk 18
It was a combination of many factors.
Here is what I did first:
Fully uninstalled Magisk 18
Installed Magisk 17..3
Selected applications lilke a simple Safetynet checket app under Magisk Hide
Started the Safetynet checker app and it worked.
Then I started to re-install my Magisk modules including Pix3lify (former Pixel Experience module) for an alternate launcher and found out that this was causing the issue.
I uninstalled this module and then decided to upgrade to Magisk 18. Magisk Hide didn't work at first since a simple Safetynet checker app wouldn't pass.
I had to go back to Magisk Hide panel and unselect all the apps that were previously registered before selecting them again and this time it worked.
Thanks again for your pointers and I hope the above will help other people.
PhilippeSX4 said:
Hi alphazo,
I had the same problem with my Huawei Mate 10 Pro since I went from 17.3 to 18.0.
I tried several solutions like you, but nothing worked. The only thing that worked was to downgrade to version 17.3, there, everything was functional.
For my part, I completely uninstalled Magisk from my phone and then reinstalled it. After that, everything works perfectly and I have no problems with SafetyNet.
You just have to reconfigure the Magisk Manager application and choose which applications you want to hide.
I hope it will work for you too ! :good:
Click to expand...
Click to collapse
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.
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.
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