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.
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.
Saw an update, thought cool finally out of beta, but upon upgrading, safetynet fails.
I didn't take a look too much into it, I did see on github that at least some users also had failing safetynet, but this was right at the same time as the google update to safetynet for magisk, so I couldn't rule that out for other users.
I've reverted back to v0.4.5.1 and edxposed installer and safetynet passes. I *think* it might be because edxposed installer has blacklist functionality. I couldn't find the equivalent setting on edxposed manager.
anonxlg said:
Saw an update, thought cool finally out of beta, but upon upgrading, safetynet fails.
I didn't take a look too much into it, I did see on github that at least some users also had failing safetynet, but this was right at the same time as the google update to safetynet for magisk, so I couldn't rule that out for other users.
I've reverted back to v0.4.5.1 and edxposed installer and safetynet passes. I *think* it might be because edxposed installer has blacklist functionality. I couldn't find the equivalent setting on edxposed manager.
Click to expand...
Click to collapse
Latest Xposed Manager try in settings menu scroll down to framework options enable:
App List mode
Pass Safetynet
To enable blacklist function - App List mode has to be enable. Then from main menu select Applications.
thanks, after some testing and restarting that did the trick.
I didn't see that the 'app list mode' is the blacklist and only turned on 'pass safetynet' thinking that was the only think I needed to do
I updated lineage and I can't get safetynet to pass again.
I verified that with edxposed disabled, it passes safetynet. I tried uninstalling/reinstalling edxposed and tried both sandhook and yahfa versions and it doesn't pass.
Scratching my head on how it doesn't working work anymore because from lineage update (my only guess).
anonxlg said:
I updated lineage and I can't get safetynet to pass again.
I verified that with edxposed disabled, it passes safetynet. I tried uninstalling/reinstalling edxposed and tried both sandhook and yahfa versions and it doesn't pass.
Scratching my head on how it doesn't working work anymore because from lineage update (my only guess).
Click to expand...
Click to collapse
In Edxposed Manager try downloading the canary release and flash through Magisk.
Also note that Google is starting to tighten it's grip in regards to Safety Net. Very basically it will fail with an unlocked bootloader.
https://mobile.twitter.com/topjohnwu/status/1237830555523149824
spawnlives said:
In Edxposed Manager try downloading the canary release and flash through Magisk.
Also note that Google is starting to tighten it's grip in regards to Safety Net. Very basically it will fail with an unlocked bootloader.
https://mobile.twitter.com/topjohnwu/status/1237830555523149824
Click to expand...
Click to collapse
I'm aware of that, but in my case, phone passed safetynet (with magisk, edxposed, and all modules the same) before updating lineage.
I should note that this is lineage 15.1 (A8.1) if it matters.
And that phones pre-pie are currently immune to that safetynet check because of old security hardware.
this work: https://repo.xposed.info/module/com.cofface.ivader
anonxlg said:
I'm aware of that, but in my case, phone passed safetynet (with magisk, edxposed, and all modules the same) before updating lineage.
I should note that this is lineage 15.1 (A8.1) if it matters.
And that phones pre-pie are currently immune to that safetynet check because of old security hardware.
Click to expand...
Click to collapse
On my spare S8 I've reinstall unofficial lineage 17.1 ( Android 10 ).
Using latest:
Stable version of magisk / manager
Edxposed manager - 4.5.7
Edxposed canary - 0.4.6.3 ( 4545 ) - Yahfa
Riru core - 19.8
This combination at the moment is passing safety net. Checked using magisk manager + two other apps from playstore. Also have Device is certified through play store. The latest play store version is 19.5.13 for my region.
Edxposed modules installed at moment
Xprivacylua
Minminguard
Resolver Activity Tweaks
installing HiddenCore Module did the trick, but i'm still curious why updating lineage broke safetynet or that using the older rirucore + edxposed passes safety net
I might have figured this problem, let me know if it helps you pass safetynet too as it did work on my device ( OP6T ):
Install everything just as the above steps,
-config magiskhide, install the fingerprints
-Install riru etc, install the canary version of sandhook
-put in airplane mode as soon as you reboot
-enable applist and blacklist google framework and services and playstore (also assuming you have done hidden these in magisk too)
-clear data from services, framework, playstore
- open playstore and check if youre logged in and its working
- Go check safetynet
Gpay is working for me flawlessly
As of april 25 this solution seems to work for me.
nousernamesorry said:
I might have figured this problem, let me know if it helps you pass safetynet too as it did work on my device ( OP6T ):
Install everything just as the above steps,
-config magiskhide, install the fingerprints
-Install riru etc, install the canary version of sandhook
-put in airplane mode as soon as you reboot
-enable applist and blacklist google framework and services and playstore (also assuming you have done hidden these in magisk too)
-clear data from services, framework, playstore
- open playstore and check if youre logged in and its working
- Go check safetynet
Gpay is working for me flawlessly
As of april 25 this solution seems to work for me.
Click to expand...
Click to collapse
I followed your order, but in magisk I have passed safetynet, but CTS and basicIntegrity is false
This the screenshot... S9 rooted + custom rom android 10 + kernel custom
Without xposed I had both positives
bmw320cd said:
I followed your order, but in magisk I have passed safetynet, but CTS and basicIntegrity is false
This the screenshot... S9 rooted + custom rom android 10 + kernel custom
Without xposed I had both positives
Click to expand...
Click to collapse
Sorry man, this solution no more works. It broke after April 27th.
So is there no current method to have edxposed/ru working while passing safetynet? Thanks
djjohnnyblaze said:
So is there no current method to have edxposed/ru working while passing safetynet? Thanks
Click to expand...
Click to collapse
At the moment still passing safety net using latest Riru core module + latest canary release of Edxposed.
System Crashes
nousernamesorry said:
I might have figured this problem, let me know if it helps you pass safetynet too as it did work on my device ( OP6T ):
Install everything just as the above steps,
-config magiskhide, install the fingerprints
-Install riru etc, install the canary version of sandhook
-put in airplane mode as soon as you reboot
-enable applist and blacklist google framework and services and playstore (also assuming you have done hidden these in magisk too)
-clear data from services, framework, playstore
- open playstore and check if youre logged in and its working
- Go check safetynet
Gpay is working for me flawlessly
As of april 25 this solution seems to work for me.
Click to expand...
Click to collapse
My system UI is crashing sometimes. Is it because of edxposed? I followed these steps and successfully passed the SafetyNet check. But my system is crashing sometimes!
I'm using sudohide module only!
romee_ahuja said:
My system UI is crashing sometimes. Is it because of edxposed? I followed these steps and successfully passed the SafetyNet check. But my system is crashing sometimes!
I'm using sudohide module only!
Click to expand...
Click to collapse
Hey, it could be that, maybe you have a module like gravitybox installed which is conflicting with your system configurations.
If not that, try disabling edxposed modules from magisk itself. If that fixes the solution, then it might be edxposed
One solution is disable module like gravitybox or update gravitybox
This is a weird one.
To start, my phone has latest magisk, and passed safety net.
I once again am trying out edxposed (seeing if the game I'm playing still detects, and yes it does).
So, I managed to install edxposed (with hiddencore), magisk working and passing safetynet (check screenshot), however, as mentioned, game still detects something and refuses to start (another note is that the game starts without issues with just magisk and safetynet passed).
Because game doesn't work, I uninstalled hiddencore, edxposed, and riru core (in that order) and somehow magisk cannot pass safetynet anymore.
I've tried everything over again plus countless restarts to get a screenshot of my phone with edxposed and safetynet passed.
-edit-
clearing playstore data did the trick
Hi,
Did u fix your problem ?
Thanks!
Just to be clear, you have only Magisk and Edxposed WITHOUT HiddenCore module installed, and you're passing SN and your game runs fine without detecting root?
I'm a little confused about the order of events and the steps you took, because it reads like you installed edxposed and HiddenCore at the same time (HiddenCore will merely mask SN success test in magisk, it doesn't actually fix the issue as other tester apps more accurately fail to pass SN with edxposed installed. Then you describe you uninstalled all of riru/edxposed framework and hiddencore and then a screen shot of edxposed with Magisk SN test passing??? Okay so, did you reinstall hiddencore? Did you run the test after several reboots to confirm reliability? The game you mentioned, did that quit detecting edxposed? What did you do here exactly?
1. don't consider Magisk's SafetyNet as trustable. Test with other apps like org.freeandroidtools.safetynettest (SafetyNet Test 1.2.1). Or open google play and search for Netflix, and see in Setting at the bottom should say Device is/not certified. Before that clear the Google Play Store Cache и Data Storage because it will remember the previous state and will show an old state.
2. Dont need to uninstall the whole EdXposed and frameworks. Just go in Magisk and turn off the Riru Core framework. Restart. And the SafetyNet should work again. But then GravityBox (and other apps using edXposed) will stop working
3. Yes, recently it stop working for me too, coz Google did next dirty thing. Before I was passing SafetyNet. I had Riru Core 21.3 + EdXposed YAHFA v0.5.0.6 Canary + EdXposedManager v4.5.7 + GravityBox
4. I solve the problem, now I pass SafetyNet again, my GravityBox is working, Google Play show device is certified, all good, so I am happy again. What I did is:
5. Restored my old backup. If I have installed EdXposed-SandHook-v0.5.0.6 Canary I am not able to uninstall it preperly and restore the phone, so whatever I do after it always break SafetyNet. Somehow SandHook mess the phone in irreversible way so the only way out is to flash old backup. That's why I was using EdXposed YAHFA v0.5.0.6 Canary which dont mess the phone and after uninstall phone can pass SafetyNet. So maybe is was not necessary to restore the old backup...
I use LG V20 with LineageOS 17.1 Android 10
6. installed the taichi-v6.2.2.zip framework in Magisk.
https://magiskroot.net/download-xposed-for-android-10/
https://magiskroot.net/taichi-magisk-module/
https://github.com/taichi-framework/TaiChi/releases
https://virtualxposed.com/tai-chi/
https://taichi.cool/download.html
https://github.com/taichi-framework/TaiChi/issues/1153
installed TaiChi 6.4.0.apk
in Modules I enable GravityBox only. Do NOT enable HiddenCore Module because it is detected and if I enable it fail the SafetyNet
in /system/etc/hosts I put this to block connections:
127.0.0.1 techavenue.net
127.0.0.1 www.techavenue.net
127.0.0.1 chinatelecom.com.cn
127.0.0.1 www.chinatelecom.com.cn
127.0.0.1 alibaba.com
127.0.0.1 www.alibaba.com
Click to expand...
Click to collapse
I dont advice you using TaiChi blindly. I just share what I did to have GravityBox with SafetyNet working. You can Thanks me if you find my tips helpful.... But choosing TaiChi is your decision, you can take a look some controversial topic about TaiChi here https://forum.xda-developers.com/xposed/warning-taichi-t4012681
I have Redmi Note 7.
It was running on xiaomi.eu_multi_HMNote7_V11.0.6.0.PFGCNXM_v11-9. I had magisk installed, there were no problems with root detection.
I installed xiaomi.eu_multi_HMNote7_V11.0.7.0.PFGCNXM_v11-9 using OrangeFox Recovery.
Then my problems with Magisk began. I uninstalled magisk completely via orangefox recovery and install again v21.4 as zip. Finally I updated magisk manager and magisk module with success and now it is latest version 25.2. I can't check safetynet via magisk app, cuz there is no option, so I used app called YSNAC. It shows: Basic integrity: failed, CTS profile match: failed. I perform hide Magisk app, named new app as "Settings", but the old Magisk icon did not disappear (I don't know if it's ok).
I activate Zygisk and enforce deny list and set deny list (banking apps, play services, google play store).
I installed modules like MagiskHide Props Config and Universal SafetyNet Fix.
BTW. Why there is no more online searching modules via magisk manager?
Root working ok.
I don't know what can I do more. My banking apps detects that I have root.
mcichy10 said:
I have Redmi Note 7.
It was running on xiaomi.eu_multi_HMNote7_V11.0.6.0.PFGCNXM_v11-9. I had magisk installed, there were no problems with root detection.
I installed xiaomi.eu_multi_HMNote7_V11.0.7.0.PFGCNXM_v11-9 using OrangeFox Recovery.
Then my problems with Magisk began. I uninstalled magisk completely via orangefox recovery and install again v21.4 as zip. Finally I updated magisk manager and magisk module with success and now it is latest version 25.2. I can't check safetynet via magisk app, cuz there is no option, so I used app called YSNAC. It shows: Basic integrity: failed, CTS profile match: failed. I perform hide Magisk app, named new app as "Settings", but the old Magisk icon did not disappear (I don't know if it's ok).
I activate Zygisk and enforce deny list and set deny list (banking apps, play services, google play store).
I installed modules like MagiskHide Props Config and Universal SafetyNet Fix.
BTW. Why there is no more online searching modules via magisk manager?
Root working ok.
I don't know what can I do more. My banking apps detects that I have root.
Click to expand...
Click to collapse
I have the same issue since today on Galaxy s21 Ultra!
I decided to uninstall completely Magisk. Unfortunately SafetyNet still doesn't pass, banking aps not working. Only thing I can do is wipe all data, format to factory and install MIUI again. Maybe I'll try MIUI 12.
mcichy10 said:
I decided to uninstall completely Magisk. Unfortunately SafetyNet still doesn't pass, banking aps not working. Only thing I can do is wipe all data, format to factory and install MIUI again. Maybe I'll try MIUI 12.
Click to expand...
Click to collapse
try using Shamiko together with Zygisk and without forcing the denylist
I tried this before with zero success
With the MagiskHide Props config, you need to open a terminal, enter "su" and then "props". Then set the fingerprint to the certified one.
neelchauhan said:
With the MagiskHide Props config, you need to open a terminal, enter "su" and then "props". Then set the fingerprint to the certified one.
Click to expand...
Click to collapse
yup, I did that. Didn't work for me.
I performed "Format Data", flashed latest MIUI for my device, installed Magisk, Hided Magisk, activated Zygisk, Forced deny list and it's working well.
i tried like 4 different ways and NONE work
Universal SafetyNet Fix (didnt work)zydisk (didnt work)
denylist (didnt work)
magiskhide proops config (didnt work)
i have a mi 9 with miui 13+android 12
EDIT: it just takes trial and error, had to try a couple of different devices and one that worked for me was mi 9 europe
I can pass safety net on magisk 25.2 . I don't install magisk hide props. I have few things installed and a modified Verison of universal safety fix and I am using zygisk.
Alot times I forget about messages on here . Telegram me if I don't get back to u on @Assassin4Hire
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
Flash this.
Enjoy.
yot2703 said:
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
Flash this.
Enjoy.
Click to expand...
Click to collapse
I tried this workaround in my Samsung SM-G531H with Android 7.1 and I tested it with the previously mentioned YASNAC app, and the SafetyNet Attestation tests (Basic Integrity and CTS profile match) PASSED!
Now, I'm able to use my bank app (BBVA) Thanks.