SafetyNet Check in magisk failing - OnePlus 6 Questions & Answers

I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?

quantumcity said:
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
Click to expand...
Click to collapse
I had the same problem I uninstalled Xposed framework rebooted now the the safetynet check is Ok

airdi1 said:
I had the same problem I uninstalled Xposed framework rebooted now the the safetynet check is Ok
Click to expand...
Click to collapse
As I mentioned in the post, I do not have Xposed framework

quantumcity said:
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
Click to expand...
Click to collapse
What version of Magisk did you flash? Flash Magisk 16.4 only. Older versions don't support the OnePlus 6 and flashing newer versions has caused many weird problems. Flash Magisk uninstaller, reboot to TWRP, then flash Magisk 16.4. Once it gets going it will tell you that it can update the Magisk version. Let it update that way. Flashing newer versions causes many weird problems bit letting it update always seems to work.

run the uninstaller magisk .zip then check if safety net passed, might be something unrelated?
im on 5.1.9 with SN passing with TWRP and Magisk

tabletalker7 said:
What version of Magisk did you flash? Flash Magisk 16.4 only. Older versions don't support the OnePlus 6 and flashing newer versions has caused many weird problems. Flash Magisk uninstaller, reboot to TWRP, then flash Magisk 16.4. Once it gets going it will tell you that it can update the Magisk version. Let it update that way. Flashing newer versions causes many weird problems bit letting it update always seems to work.
Click to expand...
Click to collapse
I have magisk 16.7

virtyx said:
run the uninstaller magisk .zip then check if safety net passed, might be something unrelated?
im on 5.1.9 with SN passing with TWRP and Magisk
Click to expand...
Click to collapse
How do I do that? Do you have a link to this zip?

quantumcity said:
I have magisk 16.7
Click to expand...
Click to collapse
Google "Magisk uninstaller". Flash that file in TWRP. Then reboot to recovery. Then flash Magisk 16.4

quantumcity said:
How do I do that? Do you have a link to this zip?
Click to expand...
Click to collapse
its in the magisk official thread.

virtyx said:
its in the magisk official thread.
Click to expand...
Click to collapse
Yes

So for me, the safety net check passes in the Magisk app but I am not able to access Google tez which tells me that my device is rooted or custom ROM has been changed. Using Magisk v 16.0

16.4... notice the 4

Just fyi I'm on 5.19 and using Magisk 16.0 and safety net passes just fine. Use Google pay daily and play store shows certified.
I hide everything Google related in magisk hide just to be sure

Eric214 said:
16.4... notice the 4
Click to expand...
Click to collapse
I know. What I meant is safety net passes everywhere except for Google Tez app. Don't know why!

I have attached the screenshots below. And I understand that I'm using Magisk 16.0

skr975 said:
I know. What I meant is safety net passes everywhere except for Google Tez app. Don't know why!
Click to expand...
Click to collapse
Do you have it hidden in Magisk? Google Pay works here if you hide it.

Okay, so I have uninstalled magisk, don't have root, and I still can't use google pay, install netflix, use my bank's app, etc.
No root, no magisk, no xposed, no custom recovery.
How can I figure out why all these apps won't work?

quantumcity said:
Okay, so I have uninstalled magisk, don't have root, and I still can't use google pay, install netflix, use my bank's app, etc.
No root, no magisk, no xposed, no custom recovery.
How can I figure out why all these apps won't work?
Click to expand...
Click to collapse
In playstore / settings are you uncertified? After unlocking bootloader I was and couldn't use Google pay. I flashed magisk and it was still uncertified so I cleared playstore app data. Now the phone says certified and Google pay works for me.
I suggest you flash 16.4 magisk and clear app data in playstore to see if you can get them working. Also you will need a different app than magisk manager to check safety net ATM as it will come back with "invalid response"
Sent from my OnePlus6 using XDA Labs

Related

SafetyNet false all the time...

I've installed LineageOS 15.1 with Magisk 19.3 (tried 19.4 also) and my SafetyNet is all the time False. I even tried to install LineageOS 14.1 with Magisk 18 - it didn't work. I also flashed GApps (nano/pico versions). Any idea how to fix it? I already tried hiding Magisk and all typical stuff
kamieniarz said:
I've installed LineageOS 15.1 with Magisk 19.3 (tried 19.4 also) and my SafetyNet is all the time False. I even tried to install LineageOS 14.1 with Magisk 18 - it didn't work. I also flashed GApps (nano/pico versions). Any idea how to fix it? I already tried hiding Magisk and all typical stuff
Click to expand...
Click to collapse
status of selinux?
CriGiu said:
status of selinux?
Click to expand...
Click to collapse
Enforcing
EDIT: I've noticed that SafetyNet is true when I revoke all SU privilages... But I need them so it's not a solutions for me
Hi, I was facing the same problem. I am running an Android 9 ROM (crDroid), though, so I don't know if my solution will work for you. Anyway, what seems to have fixed this for me is flashing ROM and Gapps first, let the device boot fully and then flash Magisk on its own. If you want to avoid clean flashing the ROM etc. again, you could try unistalling Magisk by flashing the official uninstaller, reboot, then flash it anew. That also worked for me.
I used to get this erratic behavior from Magisk when dirty flashing ROM updates, so each time I uninstall it and re-install it. It's a bummer, but it works in the end... I haven't yet figured out if this "SafetyNet fail" is either ROM or Magisk related. I hope I helped!
My condition was android pie/custom rom,magisk 19.3 stable,selinux permissive,device uncertified in playstore,safetynet false cts and basic integrity.
How is your device certified or uncertified?
However,this was my fix.
In magisk hide i ticked all apps,even system's ones.
In settings/apps i deleted all cache/data of playstore and google play services.
I rebooted in twrp and i cleaned cache and dalvik cache.
I rebooted system.
I waited until my device was fully booted,it depends on your settings,apps etc.
Then i checked magisk,safetynet passed and in playstore my device was correctly recognized as certified.

SafetyNet Fail

I installed edxposed to check if SafetyNet will pass, but unfortunately it failed. Then i removed the riru core and edXposed modules from magisk, removed the edXposed manager and restarted.
But still the SafetyNet is failing.
How to get the SafetyNet to pass again?
Try this. Mine failed too. Latest Magisk Canary. Enabled this and it passed.
TheKnux said:
Try this. Mine failed too. Latest Magisk Canary. Enabled this and it passed.
Click to expand...
Click to collapse
MagiskHide ? its already Enabled on my device always.
I'm using latest Magik Canary on my IN2010 OOS 10.5.9 Everything dine. Safety pass
HDTzenfone2 said:
I'm using latest Magik Canary on my IN2010 OOS 10.5.9 Everything dine. Safety pass
Click to expand...
Click to collapse
Hi, by default the SafetyNet will pass with Magisk, my issue is post installation and uninstallation of edXposed. Can you verify this?
I am already having latest Canary build
I re installed the last update again using local update amd applied magisk, but still SafetyNet fails.
Some suggestions please
same issue here
Finally solved.
Just needed to clear the CACHE of play services
Suggested solution here:
https://forum.xda-developers.com/apps/magisk/installed-uninstalled-edxposed-t4114139/post82811925
Hello all I'm having trouble getting SafetyNet to pass. Yesterday SafetyNet passed fine however today I am failing attestation (cts profile) and cannot understand what changed.
I believe the only app I installed was BusyBox from the play store. I also used the magisk debloater module to freeze some system apps (Facebook stuff).
I am running OOS 10.5.9IN21AA
Yesterday SafetyNet passed, today it fails. Would debloating the system cause this? Thanks to anyone who can share some insight to this.
I have tried clearing app cache for Google Play Services with no luck.
Edit:. I've managed to fix safety net by removing root and uninstalling magisk canary then installing magisk manager 7.5.1 and flashing magisk 20.4 via TWRP!

Just Unlocking the Bootloader breakes safety net and make device unverified..

So as the title says safety net breaks just by unlocking the bootloader and doing nothing else, no twrp no magisk and even if i flash magisk it doesnt fix it even with magiskprops module.
I flashed stock rom 10.3.1 with msmtool and booted the phone and everything was fine until i unlocked the bootloader and rebooted. I lost all oneplus wallpapers and even then play store says device not verified and netflix shows as unsupported app.
Even with 10.3.4 the issue is same and cant be fixed with magisk. Previously i was using 10.3.2 with unlocked bootloder and magisk and safety net was fine so how it is now not working with factory rom i flashed with msmtool
https://forum.xda-developers.com/on...etynet-magisk-edxposed-tests-failing-t4077527
Manu11 said:
So as the title says safety net breaks just by unlocking the bootloader and doing nothing else, no twrp no magisk and even if i flash magisk it doesnt fix it even with magiskprops module.
I flashed stock rom 10.3.1 with msmtool and booted the phone and everything was fine until i unlocked the bootloader and rebooted. I lost all oneplus wallpapers and even then play store says device not verified and netflix shows as unsupported app.
Even with 10.3.4 the issue is same and cant be fixed with magisk. Previously i was using 10.3.2 with unlocked bootloder and magisk and safety net was fine so how it is now not working with factory rom i flashed with msmtool
Click to expand...
Click to collapse
Don't think so. I'm on a rooted 10.3.4 and I don't see such issues with playstore or safetynet.
hallo dare said:
https://forum.xda-developers.com/on...etynet-magisk-edxposed-tests-failing-t4077527
Click to expand...
Click to collapse
safetynet fails even without the magisk, so i dont think its a magisk problem
Manu11 said:
safetynet fails even without the magisk, so i dont think its a magisk problem
Click to expand...
Click to collapse
What'd u do ?
jaggillararla said:
What'd u do ?
Click to expand...
Click to collapse
There's nothing you can do about safetynet. The moment you unlock the bootloader, you have tripped the safetynet. Why do you need safetynet btw unless you are using bank apps or secure stuff, safetynet really doesn't help much
amirage said:
There's nothing you can do about safetynet. The moment you unlock the bootloader, you have tripped the safetynet. Why do you need safetynet btw unless you are using bank apps or secure stuff, safetynet really doesn't help much
Click to expand...
Click to collapse
Bro as i told already in my post i was yesterday using unlocked bootloader + magisk+ twrp with passing safety net. The problem started when i clean flashed stock rom with msmtool and unlocked bootloader.
ANYWAYS GUYS AFTER SO MANY USELESS ATTEMPS I SOLVED IT..
Older version of magisk worked and safety net passes, i dont know how new version failed me :/ Device is certified again
That's why I don't update anything if not have to
Config below
Sent from OnePlus 7 Pro, OxygenOS 10.0.3, TWRP 3.3.1-75, Magisk 20.4, TaiChi Xposed 6.1.8, Modded Play Store 16.5.15, android core.java patched and SafetyNet pass OK
Install magisk
Go to magisk settings
Enable magisk hide(if you're getting problems with banking apps or games that detect root just hide magisk manager too)
Enable it for google play services and enjoy!
Playstore uncertified status appeared to me when I flash stock rom through TWRP but it solves flashing new firmware via OTA
Sent from my OnePlus7Pro using XDA Labs
The reason an older version of Magisk worked is because newer versions of Magisk turn MagiskHide off by default, which is needed to pass SafetyNet.
Also, SafetyNet is not an e-fuse like Knox is. You don't "trip" it, you can only fail it when it checks your device.

Magisk 24.1 no Zygisk option available

I had rooted my Samsung Galaxy Note 8 using TWRP (latest version) and Magisk version 23.0. Everything worked well until 2 days ago when magisk auto updated to version 24.1.
After this, all the options available on 3home page disappeared except option to install magisk 24.1 and magisk app.
I was expecting gydisk OP to be available as seen in various screenshots from internet about magisk 24.1 but unfortunately, didn't see any option to enable it (Screenshot attached).
Thinking the magisk update may gone haywire, reinstalled the stock firmware for my Galaxy Note 8 phone, flashed TWRP, RMM_Bypass_v3_corsicanu.zip, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip, Magisk 24.1, successfully.
However when rebooted into system, the magisk app still showed no option for Gydisk or any other option except previously mentioned above I.e Install magisk or magisk app.
Have checked & found OEM unlocking and USB debugging is still open.
Now I am lost and wondering where could I be going wrong.
Appreciate very much if someone can guide me in right direction in getting Gydisk option si that I can pass the safety check and hide magisk.
Your screenshot shows that Magisk is not installed.
You only installed the app. Try install in the upper right corner and choose for direct install without patching.
Prof_Shekhar said:
I had rooted my Samsung Galaxy Note 8 using TWRP (latest version) and Magisk version 23.0. Everything worked well until 2 days ago when magisk auto updated to version 24.1.
After this, all the options available on 3home page disappeared except option to install magisk 24.1 and magisk app.
I was expecting gydisk OP to be available as seen in various screenshots from internet about magisk 24.1 but unfortunately, didn't see any option to enable it (Screenshot attached).
Thinking the magisk update may gone haywire, reinstalled the stock firmware for my Galaxy Note 8 phone, flashed TWRP, RMM_Bypass_v3_corsicanu.zip, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip, Magisk 24.1, successfully.
However when rebooted into system, the magisk app still showed no option for Gydisk or any other option except previously mentioned above I.e Install magisk or magisk app.
Have checked & found OEM unlocking and USB debugging is still open.
Now I am lost and wondering where could I be going wrong.
Appreciate very much if someone can guide me in right direction in getting Gydisk option si that I can pass the safety check and hide magisk.
Click to expand...
Click to collapse
xabu said:
Your screenshot shows that Magisk is not installed.
You only installed the app. Try install in the upper right corner and choose for direct install without patching.
Click to expand...
Click to collapse
Thank you xabu for your reply.
I had tried to install it numerous times using the direct install method as suggested by you but it gives me a "installation failed" message (Screenshot attached).
Also, presuming that my previously installed magisk v 23.0 may not have been uninstalled during the process of auto update to magisk version 24.1 (only 24.1 app installed but not magisk itself not upgraded due to unknown reasons), I reinstalled the app v 23 and uninstalled magisk completely. Frustrated, I installed the stock firmware again, reinstalled TWRP and flashed magisk 24.1. However, the result appears to be same. No magisk installation.
It appears to me that magisk v 23 is not yet completely uninstalled as if I delete this 24.1 app, reinstall app for 23.1 most of the functionality comes back though not all. I still can't hide magisk but it passes safety check.
Also I have tried to uninstall any previous version of magisk using renamed magisk app as uninstall.zip via TWRP. Also I get following message:
"cannot find vbmeta partition, patch vbmeta in boot image.
Removing magisk files."
Now when I go to Magisk app, I get only option to "select and patch a file."
Appreciate if anyone can suggest me a way forward.
Also, I get the vbmeta partition not found error while trying to install Magisk via TWRP (screenshot attached)
I have selected and installed Magisk patched boot image file using ODIN3. Removed TWRP. Tried to install using Magisk app 24.1 but get installation failed due to unable to check signature (screenshot attached).
Request some guidance.
Start here ....
Magisk - The Age of Zygisk.​Your questions are very interesting but too difficult for me to answer. Magisk 24.1 normally replaces the 23 almost automatically .... By uninstalling the module the situation becomes completely different and you should probably start from scratch. In my link "start here" you'll find the place where real specialists are.
Wishing you all the best !
Appreciate your advice.
However, I have reinstalled the stock firmware 3 times since this morning just as to ensure that I start from a clean slate. Also used Adb commands to uninstall any remanants of the previous Magisk manager if at all left there.
However, still stuck with the puzzling question as to where am I going wrong.
Prof_Shekhar said:
Also I have tried to uninstall any previous version of magisk using renamed magisk app as uninstall.zip via TWRP. Also I get following message:
"cannot find vbmeta partition, patch vbmeta in boot image.
Removing magisk files."
Now when I go to Magisk app, I get only option to "select and patch a file."
Appreciate if anyone can suggest me a way forward.
Click to expand...
Click to collapse
Exact same issue for me!
Also for me....same tests that @Prof_Shekhar have done
Prof_Shekhar said:
I had rooted my Samsung Galaxy Note 8 using TWRP (latest version) and Magisk version 23.0. Everything worked well until 2 days ago when magisk auto updated to version 24.1.
After this, all the options available on 3home page disappeared except option to install magisk 24.1 and magisk app.
I was expecting gydisk OP to be available as seen in various screenshots from internet about magisk 24.1 but unfortunately, didn't see any option to enable it (Screenshot attached).
Thinking the magisk update may gone haywire, reinstalled the stock firmware for my Galaxy Note 8 phone, flashed TWRP, RMM_Bypass_v3_corsicanu.zip, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip, Magisk 24.1, successfully.
However when rebooted into system, the magisk app still showed no option for Gydisk or any other option except previously mentioned above I.e Install magisk or magisk app.
Have checked & found OEM unlocking and USB debugging is still open.
Now I am lost and wondering where could I be going wrong.
Appreciate very much if someone can guide me in right direction in getting Gydisk option si that I can pass the safety check and hide magisk.
Click to expand...
Click to collapse
The same thing happened to me so i tried and tried and tried for like 4-5 hours after reinstalling multiple times the firmware so i gave up and came to the conclusion that its not supported yet for a few phones like the Note8 (SM-N950F ~ my version of the phone).So the only thing you can do rn is to stick to version 23.0 then go to settings and change the channel to custom channel and paste this link "https://raw.githubusercontent.com/t...304e59f631280cc26ccc6d40a7cf04f7f37/beta.json" in there so the magisk version doesn't update itself or you update it by accident
Beast-chan said:
The same thing happened to me so i tried and tried and tried for like 4-5 hours after reinstalling multiple times the firmware so i gave up and came to the conclusion that its not supported yet for a few phones like the Note8 (SM-N950F ~ my version of the phone).So the only thing you can do rn is to stick to version 23.0 then go to settings and change the channel to custom channel and paste this link "https://raw.githubusercontent.com/t...304e59f631280cc26ccc6d40a7cf04f7f37/beta.json" in there so the magisk version doesn't update itself or you update it by accident
Click to expand...
Click to collapse
@Beast-chan
Hope you were able to install Magisk 24.1 Canary version without any further issues.
Prof_Shekhar said:
@Beast-chan
Hope you were able to install Magisk 24.1 Canary version without any further issues.
Click to expand...
Click to collapse
tbh i didnt try the Canary version...does it work or why do you ask?
Beast-chan said:
tbh i didnt try the Canary version...does it work or why do you ask?
Click to expand...
Click to collapse
@Beast-chan
Definitely. I have installed Magisk 24.1 Canary using patched AP file from stock firmware, and then reinstalled the Magisk 24.1 Canary version. It has been working without any issues since then.
Don't forget to install universal safetyNet Fix.
Let me know if you run into any issues.
Prof_Shekhar said:
@Beast-chan
Definitely. I have installed Magisk 24.1 Canary using patched AP file from stock firmware, and then reinstalled the Magisk 24.1 Canary version. It has been working without any issues since then.
Don't forget to install universal safetyNet Fix.
Let me know if you run into any issues.
Click to expand...
Click to collapse
ok ty i will try it

Magisk 23 on Oneplus 8t oxygenos 12

Hi guys,
After I upgraded to Oxygen OS 12, I installed magisk by patching boot.img as usual. but when I boot it shows that bootloader and recovery are corrupted. is there any way I can install magisk23 on Oxygen OS 12.1? I need the magisk hied function.
Thanks,
zhihuiyuze said:
Hi guys,
After I upgraded to Oxygen OS 12, I installed magisk by patching boot.img as usual. but when I boot it shows that bootloader and recovery are corrupted. is there any way I can install magisk23 on Oxygen OS 12.1? I need the magisk hied function.
Thanks,
Click to expand...
Click to collapse
Try using Magisk 25.2 (latest stable).
BillGoss said:
Try using Magisk 25.2 (latest stable)
Click to expand...
Click to collapse
Hi,
Thanks for the reply. I will try but does magisk23 doesn't support oxygenos12 of android 12? I want to keep it because I want to use magisk hide.
Thanks
zhihuiyuze said:
Hi,
Thanks for the reply. I will try but does magisk23 doesn't support oxygenos12 of android 12? I want to keep it because I want to use magisk hide.
Thanks
Click to expand...
Click to collapse
25.2 can hide too.
Just enable zygisk and configure denylist.
For safetynet you can use universal_safetynet_fix and magiskhide_props_config modules.
Don't worry and have a try.
Just remember to backup before proceed.
IAAxl said:
25.2 can hide too.
Just enable zygisk and configure denylist.
For safetynet you can use universal_safetynet_fix and magiskhide_props_config modules.
Don't worry and have a try.
Just remember to backup before proceed.
Click to expand...
Click to collapse
Hi,
I have successfully installed magisk 25 on it. But if I use zygisk for some apps, a model such as xprivacyLua will not work. Using zygisk will disable all of models for the app that we enable zygisk right?
zhihuiyuze said:
Hi,
I have successfully installed magisk 25 on it. But if I use zygisk for some apps, a model such as xprivacyLua will not work. Using zygisk will disable all of models for the app that we enable zygisk right?
Click to expand...
Click to collapse
Check also article.
How to pass SafetyNet on Android after rooting or installing a custom ROM
It is possible to pass SafetyNet, even after extensive modding like rooting or installing a custom ROM. Check out how to do that here!
www.xda-developers.com
zhihuiyuze said:
Hi,
Using zygisk will disable all of models for the app that we enable zygisk right?
Click to expand...
Click to collapse
Nope, not likely... As someone is already doing that: [ https://forum.xda-developers.com/t/...android-privacy-manager.3730663/post-87416749 ].
In short, enable zygisk deny list means, hide root from those apps while keeping magisk modules functional.
But I'm not familiar with xprivacyLua... Sorry can't provide a detailed guide.

Categories

Resources