I'm running AospExtended-5.8, no Gapps installed and Xposed/FakeGapps, with microG.
From what I've read Xposed needs to be either uninstalled or disabled, so I disabled it, unchecked FakeGapps, and rebooted.
SafetyNet is enabled in microG and 'Use Offical Server'.
When I try to do a SafetyNet check in Magisk, I get a popup saying Magisk has stopped.
I have two different model phones, and each one does the same thing, running different versions of Magisk and different ROMs. I don't know why Magisk keeps stopping running the SafetyNet check?
I hope someone knows how to work this out?
Thanks
DoR3M3 said:
I'm running AospExtended-5.8, no Gapps installed and Xposed/FakeGapps, with microG.
From what I've read Xposed needs to be either uninstalled or disabled, so I disabled it, unchecked FakeGapps, and rebooted.
SafetyNet is enabled in microG and 'Use Offical Server'.
When I try to do a SafetyNet check in Magisk, I get a popup saying Magisk has stopped.
I have two different model phones, and each one does the same thing, running different versions of Magisk and different ROMs. I don't know why Magisk keeps stopping running the SafetyNet check?
I hope someone knows how to work this out?
Thanks
Click to expand...
Click to collapse
Because of Google have changed the SafetyNet api
Old safetynet check won't work at the time of this comment.
topjohnwu already have fixed SN check u have to wait until new version of magisk release or u can install unofficial magisk version from this developer
Link : https://github.com/ianmacd/MagiskBuilds
Actually since I don't have Gapps installed, that means no Play Services, I was told that's the problem and Magisk should of given me a message saying this...
Related
Has anyone managed to get the Intune Portal Hider to to work on the 6T. The version for Magisk 18.xxx gets detected in about 15 minutes. I cannot get Magisk 17.3 to pass Safetynet on the 6T, fails with "API error". The aggravating thing is that this worked without a hitch on the 5 with Magisk 17.3
Check which version of Magisk Manager you have installed. Flashing Magisk 17.3 automatically installs MM 6.0.1. Update it to 6.1.0. I ran into the same issue the other night when I updated to OOS 9.0.12. Magisk 18.1 kept failing SafetyNet checks. Uninstalled it and reinstalled 17.3. I got the same API error until I installed MM 6.1.0.
sharksfan7 said:
Check which version of Magisk Manager you have installed. Flashing Magisk 17.3 automatically installs MM 6.0.1. Update it to 6.1.0. I ran into the same issue the other night when I updated to OOS 9.0.12. Magisk 18.1 kept failing SafetyNet checks. Uninstalled it and reinstalled 17.3. I got the same API error until I installed MM 6.1.0.
Click to expand...
Click to collapse
If I could hit the thanks button 10x I would. interesting that I pass Safety Net without issues for 18
SafetyNet will initially pass on 18.x. But for me at least, after some time it will fail. Toggling Magisk Hide off/on will then allow it to pass SN again. I got a bit obsessive in checking it so it was just less to worry about using 17.3. Can't figure out where the problem is exactly since I can't forcibly reproduce it. But the other night after I updated OOS, Magisk 18.1 passed SN. I went to sleep & the next morning checked SN and it failed. I haven't had any such issues with 17.3.
sharksfan7 said:
SafetyNet will initially pass on 18.x. But for me at least, after some time it will fail. Toggling Magisk Hide off/on will then allow it to pass SN again. I got a bit obsessive in checking it so it was just less to worry about using 17.3. Can't figure out where the problem is exactly since I can't forcibly reproduce it. But the other night after I updated OOS, Magisk 18.1 passed SN. I went to sleep & the next morning checked SN and it failed. I haven't had any such issues with 17.3.
Click to expand...
Click to collapse
I have experienced exactly the same issue in both 18.0 18.1. My banking apps seem to detect root also. Got fed up with it and didn't experience any of these issues with 17.3, so just stick with this version as it does what I need it to do.
dj_ooms said:
I have experienced exactly the same issue in both 18.0 18.1. My banking apps seem to detect root also. Got fed up with it and didn't experience any of these issues with 17.3, so just stick with this version as it does what I need it to do.
Click to expand...
Click to collapse
Magisk 17.3 with Manager 6.1.0 so far is the most stable version you can get until v18 gets improved.
For me it's kinda weird. Intune Hider for 18.1 work for me. Hides what I need and all that. But my mobile data doesn't work. Disable the module and poof it's back.
Edit: Never mind. Got it by disabling a couple apps from Magisk Hide.
Hi,
im a little bit confused about this problem. From one day to another, G Pay stopped working with NFC. "This device cant be used because its rootet or modified."
I use Magisk with stock Rom severeal month now and gpay ran without any problems. The confusing thing is that I didn´t changed anything what could cause this behaviour.
What I already tried:
-GPay: Delete cache, uninstalled updates. Tried many times to activate NFC payment.
-Erased Cache in TWRP
-Installed complete offline OTA. (Root and TWRP was gone and it still wont work)
-Tried Magisk Hide and random app name.
Does anybody have an idea? I dont want to reset the whole phone for this or lock the bootloader.
Thanks for your help!
Did you update the Gpay app? Mine still works but I never installed the update
I've got the latest Google Pay version and it's been working fine.
What version of Magisk are you using? Do the SafetyNet checks pass? Does Google Play Store show that the device is certified? I've had issues with Magisk 18 & 18.1 where Magisk Hide would stop working and SafetyNet checks failing.
If you're on Magisk 18.x & SafetyNet checks fail for you, try uninstalling Magisk & Magisk Manager. Install version 17.3. Install Magisk Manager 6.1.0. Enable Magisk Hide and hide Google Pay and Google Play Store. Clear storage on Google Play Store. See if SafetyNet checks pass. Check that the device is certified. Try Google Pay again.
I don't know for sure that this will fix the problem with Google Pay, but it's what I've done after having issues with Magisk.
sharksfan7 said:
I've got the latest Google Pay version and it's been working fine.
What version of Magisk are you using? Do the SafetyNet checks pass? Does Google Play Store show that the device is certified? I've had issues with Magisk 18 & 18.1 where Magisk Hide would stop working and SafetyNet checks failing.
If you're on Magisk 18.x & SafetyNet checks fail for you, try uninstalling Magisk & Magisk Manager. Install version 17.3. Install Magisk Manager 6.1.0. Enable Magisk Hide and hide Google Pay and Google Play Store. Clear storage on Google Play Store. See if SafetyNet checks pass. Check that the device is certified. Try Google Pay again.
I don't know for sure that this will fix the problem with Google Pay, but it's what I've done after having issues with Magisk.
Click to expand...
Click to collapse
Magisk: 18.1 (worked with this version), Safety Net is passing (Thats why im so confused about it)
Playstore is showing me that it is certified.
I never had a failed SN check.
Probably because having a rooted phone, especially if you are using to send/receive money, opens up a SECURITY HOLE, even if you are using something to "bypass" google.
NOTHING is 100% safe, but, I for one, will never root my phone, if I am using it to spend money.
The days of rooting will be over one of these days. Google is locking down things more and more.
hlzocker said:
Magisk: 18.1 (worked with this version), Safety Net is passing (Thats why im so confused about it)
Playstore is showing me that it is certified.
I never had a failed SN check.
Click to expand...
Click to collapse
Make sure you have hide enabled for pay.
I'm on 18.1 and I don't have issues.
I fought with the same problem.
latest Magisk Canary build was the solution that worked for me:
https://forum.xda-developers.com/showpost.php?p=78946079&postcount=31551
Coumodo said:
I fought with the same problem.
latest Magisk Canary build was the solution the worked for me:
https://forum.xda-developers.com/showpost.php?p=78946079&postcount=31551
Click to expand...
Click to collapse
Yes, that solved the problem for me. Now the activation was successfull. Thanks!
Has anyone else had issues getting Netflix on their phone? Even if I sideload it it states its not compatible with my device. Any ideas?
Latest update installed
Magisk and edxposed installed. Have hidden magisk and edxposed from the app but still no joy. Contacted Netflix support and of course they told me to contact my device manufacturer
Haunt3r said:
Has anyone else had issues getting Netflix on their phone? Even if I sideload it it states its not compatible with my device. Any ideas?
Latest update installed
Magisk and edxposed installed. Have hidden magisk and edxposed from the app but still no joy. Contacted Netflix support and of course they told me to contact my device manufacturer
Click to expand...
Click to collapse
you have issues with netflix cause you are rooted. you need to make sure your phone passes safteynet. and make sure you hide netflix if that still dont work.
I dont know if it works on this phone but I search modules for fingerprint in the searchbar it should be the first thing that pops up to download you need to download a busybox module too and in google store download a terminal after all installed you need to type PROPS in terminal and fallow the instructions if the phone is not on there its not compatible
I am waiting for my unlock code so I can get my phone rooted so I not 100% sure but that is what fixed it on my moto g7 power.
Haunt3r said:
Has anyone else had issues getting Netflix on their phone? Even if I sideload it it states its not compatible with my device. Any ideas?
Latest update installed
Magisk and edxposed installed. Have hidden magisk and edxposed from the app but still no joy. Contacted Netflix support and of course they told me to contact my device manufacturer
Click to expand...
Click to collapse
It's probably edexposed that is tripping safetynet. Even with that xposed module, it's not a true safetynet hide. I am rooted and have Netflix working (from the play store). But I can pass safetynet. Try installing safetynet check app and see if it passes...don't check from magisk. https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Had to remove edxposed as well as use props. Magisk triggers safetynet currently. Everything's working good now. Thanks guys.
EDIT: For anyone using A51, use this method instead to preserve rom stability:
[A515x] SafetyNET PASS [Android 10 - 11] [Magisk]
UNIVERSAL SafetyNet FIX (A515x Edition) ABOUT THIS: This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on...
forum.xda-developers.com
Just this night, I managed to pass SafetyNet (mainly ctsProfile) and got a successful attestation result. When I first unlocked the bootloader and flashed Magisk, I was stuck with attestation failure, but basicIntegrity was already true, and only ctsProfile was false. This nighr I did some researching and came to a final way fixed SafetyNet fully.
EDIT: ENSURE YOU PASS basicIntegrity FIRST! I only tested this on my devicr which already passed basicIntegrity (but not ctsProfile)
Steps:
1. Enable MagiskHide and enable hiding for everything in Google Play Service.
2. You need to install MagiskHideProp, so install that first as a Magisk module, then go to a terminal, enter superuser mode, and type "props" without the quotes, now select "Edit device fingerprint", select Google, find and select "Pixel 3a", and then select Android 9, confirm the changes and then reboot. (This may cause the system to think that Android got updated, this behaviour is normal, if your wallpaper is black and nothing shows at the notification quick settings then wait several minutes)
3. Now install Universal SafetyNet Fix v1.1.1 as a Magisk module, and reboot again.
4. Finally, disable Google Play Store, use an app to fully force stop GPlay and Google Play Service, and then clear data for Google Play Store and Google Play Service, and then re-enable Google Play Store. (Required for device to pass "Play protect device certification")
5. Now check SafetyNet and see if attestation success and the type is basic.
SEVERAL NOTES:
- NETFLIX STILL DOES NOT WORK!! I was able to search Netflix in GPlay and update it, but when I try to play something I was stuck at the loading screen. (Using Magisk DRM Disabler causes Netflix to crash with error code 503 -1019 as the DRM library is gone)
- Changing the device fingerprint to Pixel 3a is required as it's the last device to use basic attestation
- You still need Universal SafetyNet Fix as GMS still uses hardware attestation despite reporting basic attestation, the Magisk module solves this problem.
Please pardon me for the bad English as my native language is not English.
I do not exactly know if this is only happening tk me, however do NOT try to do something intensive with the SystemUI (such as putting your phone to sleep mode, waking it up, and then repeating this multiple times), it will crash the SystemUI and force your phone into a soft reboot.
UPDATE: This fix can slowly destroy SystemUI/Zygote (frequent soft reboots, unable to get out from lockscreen), make sure to revert the changes as soon as possible if this happens to you. (my phone straight crashed 6 times just right now, I have reverted the changes and it seems to be fine)
This seems to happen with Samsung phones, but I can't be sure about that.
i have failed to understand your point of why use this method for A51
where as on the latest firmware may update one ui 3.1 Android 11 with hiding things from magisk hide on Magisk V23. I have safetynet working just fine posted in this thread by BlassGO here
[A515x] SafetyNET PASS [Android 10 - 11] [Magisk]
UNIVERSAL SafetyNet FIX (A515x Edition) ABOUT THIS: This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on...
forum.xda-developers.com
And by the way i am using edxposed manager as well as Riru module and after hiding things in edxposed hide even then safety doesnot break for me
kingwicked said:
i have failed to understand your point of why use this method for A51
where as on the latest firmware may update one ui 3.1 Android 11 with hiding things from magisk hide on Magisk V23. I have safetynet working just fine posted in this thread by BlassGO here
[A515x] SafetyNET PASS [Android 10 - 11] [Magisk]
UNIVERSAL SafetyNet FIX (A515x Edition) ABOUT THIS: This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on...
forum.xda-developers.com
And by the way i am using edxposed manager as well as Riru module and after hiding things in edxposed hide even then safety doesnot break for me
Click to expand...
Click to collapse
That module did not work for me at all before, however I will try again using it if you say it works, and I am using Riru EdXposed aswell and Magisk v23
kingwicked said:
i have failed to understand your point of why use this method for A51
where as on the latest firmware may update one ui 3.1 Android 11 with hiding things from magisk hide on Magisk V23. I have safetynet working just fine posted in this thread by BlassGO here
[A515x] SafetyNET PASS [Android 10 - 11] [Magisk]
UNIVERSAL SafetyNet FIX (A515x Edition) ABOUT THIS: This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on...
forum.xda-developers.com
And by the way i am using edxposed manager as well as Riru module and after hiding things in edxposed hide even then safety doesnot break for me
Click to expand...
Click to collapse
Weird, it now works for me (I had to reboot 2 times), I'll update thread then. However this method still works if you're using GSM roms/Treble that normally has failed attestation aswell
device info:
Oneplus 8 Pro IN2025
Oxygen OS 11.0.99.IN11AA
Recently rooted and I was not passing SafetyNet basic Eval and I tried Riru Lxposed and still the same thing. Somewhere online I saw someone said to install Magisk Canary and it should have Denylist which should help hide apps from the root and I don't have to worry about Safetynet with Denylist. So right now I am using Zygisk with Denylist and even with that, some apps are not working like Amazon and eBay. Can't figure out any way to pass even the basic Eval for SafetyNet. I just want all my apps to work anyone figure out a way around safetynet checks or know how to make Denylist work on all apps?
Didn't think this would work but I just fixed it.
[2023 FIX] Fix Magisk CTS Profile False Error - Bypass Safetynet
Magisk CTS Profile False Error is now popping up on almost everyone's device since Google made some changes in March. To Bypass Safetynet...
droidholic.com
The Dec 23rd 2021 update was what fixed it for me. I downloaded the Zygisk fix and put it in my Magisk and was able to pass safetynet and all my apps were working!
Bump! Oddly enough I am passing safetynet but Huntington banking app is still detecting root and Amazon is not working again. Ebay app works though.
Amazon app was working but now I guess its not?
Edit: uninstalling and reinstalling the fix module lets amazon temporary for a couple minutes and then it stops working but huntington app still detects root too.
I'm still rocking a Pixel 2 XL running stock rooted 9.0.0. I've got Magisk 23.0 Stable installed and the following modules installed:
Busybox for Android NDK 1.34.1
Systemless Hosts 1.0
Riru 26.1.4.r552(etc)
Universal SafetyNet Fix 2.1.3
If it matters, I do still have TWRP installed.
I installed Riru, rebooted, installed Universal SafetyNet Fix, rebooted again, and when SafetyNet check failed, I toggled Magisk Hide off then on.
Does anyone know what might be wrong? Suggestions are very welcome!