Database Users

passing safetynet with magisk 10.2 on x727 or x720?

Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?

squandry said:
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
Click to expand...
Click to collapse
If it's in the context of getting pokemon go working, I think this might help get what you need: https://www.reddit.com/r/TheSilphRo...around_for_the_pokémon_go/?sort=new&limit=500

squandry said:
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
Click to expand...
Click to collapse
It's working for me with android pay.

Safetynet is passing for me using Magisk v9 & phh's Superuser r266-2, but a new version of each was released last week that chatter in other forums seem to suggest device-specific trouble with. I might try but first wanted to know if anyone else in the LePro3 world already has and had problems. My current interest in safetynet is for Android Pay and DirectvNow.

suhridkhan said:
It's working for me with android pay.
Click to expand...
Click to collapse
Thanks!

robertzas said:
If it's in the context of getting pokemon go working, I think this might help get what you need: https://www.reddit.com/r/TheSilphRo...around_for_the_pokémon_go/?sort=new&limit=500
Click to expand...
Click to collapse
Linked method is outdated ever since the introduction of November security patch.

Magisk V10 and phh SU r266 working fine for me on 20s

Upgrading worked for me too and I like how safety net check is part of the new status screen.
Seems like known issue but installing Xposed caused safetynet to fail, both before and after upgrade. Uninstalling Xposed caused safety net to pass again.

Root working and safetynet still passing on my x727 after taking the Magisk Manager upgrade to Magisk 11.1 and MagiskSu.

are all of you on a stock ROM and bootloader locked, I am using lineage OS 13, but safety net fails? do you have any idea how to fix this, just wanted to use ANDROID PAY, or do I need to be on STOCK ROM, just don't like the EUI and the status bar icons and the way they look(it's just me). Any help would greatly be appreciated=)

I am on stock ROM and unlocked bootloader. Magisk lets the unlocked bootloader stay. I don't see how safetynet could be expected to fully pass on a non-OEM supported ROM, especially over the longhaul of the cat-and-mouse game.
I don't like EUI either but changing out the launcher and even the notifications pulldown with Play Store apps helps immensely, along with using Titanium to freeze the bloatware. The main EUI remnants left after that is the lockscreen, the settings application, and the recents screen which I tolerate so as to have safetynet.

I could not pass safety net, got CM13, with MAGISK installed. Dang=)

squandry said:
I am on stock ROM and unlocked bootloader. Magisk lets the unlocked bootloader stay but I don't see how safetynet could ever pass on a custom ROM.
I don't like EUI either but changing out the launcher and even the notifications pulldown with Play Store apps helps immensely, along with using Titanium to freeze the bloatware. The main EUI remnants left after that is the lockscreen and the recents screen which I tolerate so as to have safetynet.
Click to expand...
Click to collapse
Hi, Did this but after installing MAGISK, everything passed, except FINGERPRINT got disabled, says hardware not supported. Android Pay works,just went to gas station and tried it, works flawlessly. FINGERPRINT is the problem I'm seeing now. Thanks for any help.
Sent from my LEX727 using XDA-Developers Legacy app

You mean you can't use the fingerprint sensor to unlock your phone? I am not sure, that works fine for me.

squandry said:
You mean you can't use the fingerprint sensor to unlock your phone? I am not sure, that works fine for me.
Click to expand...
Click to collapse
Yup, what boot image did you install? I think the problem was the boot image I used, are you on the 20's now? thanks

I am running the aboot from dr4stic's 19s unlocked bootloader zip, everything else is from the stock 20s OTA zip.

Ok, I have spent several hours trying to make it work and now time to ask for help. I got Leeco LePro 3 with custom Ron based on EUI, and trying to get Magisk working. First I tried installing system less SuperSU and Magisk, but it failed safety check multiple times, so I tried uninstalling SuperSU and use Magisksu, but not I am not able to move forward. I installed Magisk manager and when it try to install Magisk manager it downloads but doesn't show way to install it, I even try flashing Magisk 12 zip using TWRP, but it fails to update. Can someone please help me with getting Magisk working with safety check?

bocondo said:
I even try flashing Magisk 12 zip using TWRP, but it fails to update. Can someone please help me with getting Magisk working with safety check?
Click to expand...
Click to collapse
Flashing Magisk with TWRP should work. What do you mean by it fails to update?

Installing custom ROM without root issues

I used to have an LG G3 which I rooted and installed custom ROMs on. I stopped doing this for my LG G5 when my bank app and Pokemon Go started checking for root and would refuse to run on rooted devices.
I see that it is possible to install TWRP without rooting my LG G6.
Does this mean that I can install custom ROMs on my phone without the root detection causing me issues for these apps?
Thank you

PentagonVS said:
I used to have an LG G3 which I rooted and installed custom ROMs on. I stopped doing this for my LG G5 when my bank app and Pokemon Go started checking for root and would refuse to run on rooted devices.
I see that it is possible to install TWRP without rooting my LG G6.
Does this mean that I can install custom ROMs on my phone without the root detection causing me issues for these apps?
Thank you
Click to expand...
Click to collapse
Just use Magisk (Fulmics has it included in the aroma installer) and you can hide root to the apps with MagiskHide and pass the safetynet.

Killua96 said:
Just use Magisk (Fulmics has it included in the aroma installer) and you can hide root to the apps with MagiskHide and pass the safetynet.
Click to expand...
Click to collapse
Thanks. I looked up Magisk. If this app would keep itself up-to-date that would be awesome.
I guess for now I'd rather not have to rely on Magisk, since I might have to wait for updates to it, when my my banking app updates it's safetynet code.

PentagonVS said:
Thanks. I looked up Magisk. If this app would keep itself up-to-date that would be awesome.
I guess for now I'd rather not have to rely on Magisk, since I might have to wait for updates to it, when my my banking app updates it's safetynet code.
Click to expand...
Click to collapse
Didn't understand nothing. Magisk allows to hide root from the app you choose and doesn't break safetynet at all, and safetynet is not app-related but system-related so you should wait for updates only in case of android updates that break some function of magisk.

Killua96 said:
Didn't understand nothing. Magisk allows to hide root from the app you choose and doesn't break safetynet at all, and safetynet is not app-related but system-related so you should wait for updates only in case of android updates that break some function of magisk.
Click to expand...
Click to collapse
I assumed safteynet is built into the applications, such as my banking app. I thought that they can update safteynet within the app and thus break the hiding of root.

PentagonVS said:
I assumed safteynet is built into the applications, such as my banking app. I thought that they can update safteynet within the app and thus break the hiding of root.
Click to expand...
Click to collapse
Don't know if it's built in Android or in the GServices but it's a google thing, not an app one =)

Still, with magisk your device could stop passing safety net any when Google decides to raise the standards. You would then have to wait for magisk to update and pass the safety net test again, or decide to (temporarily) uninstall magisk.

Magisk 17.3 and/or Intune portal hider on the 6T

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.

Banking app crashing on rooted Android 11

Hey, all
Successfully upgraded and rooted my phone on Android 11 and have now discovered my banking app isn't working; it's crashing within seconds of trying to start.
I have Magisk itself hidden and my banking app, Navy Federal, checked under the MagiskHide section but it's not making a difference.
Anyone else having this issue and/or figured a way to resolve it?

Magisk hide isn't always going to work.
You could try hiding the magisk name but beyond that there isn't a lot you can do

@PassingInTime Are you passing the Safetynet check?

Yeh, see if magisk mgr is passing safety net...

XxSUPRAxX said:
@PassingInTime Are you passing the Safetynet check?
Click to expand...
Click to collapse
Magisk shows all pass. Firefox is actually crashing on launch now as well. Not sure what's going on yet, but I'm hoping to avoid resetting...again.

PassingInTime said:
Magisk shows all pass. Firefox is actually crashing on launch now as well. Not sure what's going on yet, but I'm hoping to avoid resetting...again.
Click to expand...
Click to collapse
What banking app has the issue? Ill test it out on my device.

Sometimes it's bank sided, when I rooted my device after updating to A11, my bank app didn't work and I thought it had something to do with root.
I ended up calling them, it turned out that they didn't update the app and after a couple of days I received an update and it's working again.
If it worked for you before root, try to hide Magisk, does it pass safetynet anyway?
EDIT: Just noticed that it passes safetynet, I'd suggest to restore stock boot and see if it works, if so, try rooting again.
Are you using beta canary?

roote3 beta 3 NFCU app works for me. magisk hidden and magisk name changed.

Enable USB debugging and use ADB logcat ... Start the app ... Stop the logcat and check for errors in the log ... Maybe you'll find why in there

cali310 said:
roote3 beta 3 NFCU app works for me. magisk hidden and magisk name changed.
Click to expand...
Click to collapse
Finally works for me too - took them awhile.

SM-A515F/DSN SafetyNet Pass (One UI 3.1), may work for other devices aswell!

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