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?

Xposed won't enable in PureFusionOS (13NOV2017)

I finally found a ROM for this GD phone that fully connects to my Bluetooth deck. Yay! All other ROMs besides stock and PureNexus would say "Connected (no phone). However Xposed is not working. The Xposed Installer (v3.14) says that Xposed version 89 is installed, but not active. This is my first time trying Xposed on Nougat. I've used Xposed on all previous Android versions (since the inception of Xposed). Never had this issue. The installer says to check the logs. When I tried it says that it can't read the log (no such file or directory). I'm so sick of effing with this phone. I'm still using my OnePlus One because I can't find a ROM that has fully working Bluetooth that isn't the crappy stock ROM or PureNexus (PureNexus is unfinished and abandoned). Somebody, anybody...how the eff do I get Xposed to work?
What I did:
-Full wipe (dalvik, system, data, cache)
-Flash latest PureFusion (13NOV2017)
-Flash SuperSu v2.82
-Flash OpenGapps (pico)
-First boot
-Install Xposed installer v3.14
-Reboot to recovery
-Flash Xposed v89
I've also tried using the install option from within the installer. No joy. Changed SuperSu options to be more compatible and less safe (namespace speration, trust system user, enable su during boot). No Joy.
I'm about to smash this phone with a hammer. Finally found a ROM that sorts Bluetooth and now Xposed doesn't work. Next time I'll check XDA first before buying a phone to check the current status of development.
Edit: I'd like to avoid using Magisk if possible. I can't remember which root apps, but there are some that don't work with Magisk (last I checked).
Edit 2: Tried the following without success. Exact same results. A msg on the status screen saying Xposed is installed but not active:
-Unity version of Xposed
-Magisk 14.0 + systemless Xposed framework
-Probably something else I'm forgetting
I created the missing log file and gave it the appropriate permissions but nothing ever got written to it. I suppose I could do a logcat but I can't be bothered. If Xposed doesn't work out of the box for this particular ROM I'm not going any further with it. I posted this question in the ROM thread as well.

Doc Ames said:
I finally found a ROM for this GD phone that fully connects to my Bluetooth deck. Yay! All other ROMs besides stock and PureNexus would say "Connected (no phone). However Xposed is not working. The Xposed Installer (v3.14) says that Xposed version 89 is installed, but not active. This is my first time trying Xposed on Nougat. I've used Xposed on all previous Android versions (since the inception of Xposed). Never had this issue. The installer says to check the logs. When I tried it says that it can't read the log (no such file or directory). I'm so sick of effing with this phone. I'm still using my OnePlus One because I can't find a ROM that has fully working Bluetooth that isn't the crappy stock ROM or PureNexus (PureNexus is unfinished and abandoned). Somebody, anybody...how the eff do I get Xposed to work. $20 to whoever provides me with the solution.
What I did:
-Full wipe (dalvik, system, data, cache)
-Flash latest PureFusion (13NOV2017)
-Flash SuperSu v2.82
-Flash OpenGapps (pico)
-First boot
-Install Xposed installer v3.14
-Reboot to recovery
-Flash Xposed v89
I've also tried using the install option from within the installer. No joy. Changed SuperSu options to be more compatible and less safe (namespace speration, trust system user, enable su during boot). No Joy.
I'm about to smash this phone with a hammer. Finally found a ROM that sorts Bluetooth and now Xposed doesn't work. Next time I'll check XDA first before buying a phone to check the current status of development.
Edit: I'd like to avoid using Magisk if possible. I can't remember which root apps, but there are some that don't work with Magisk (last I checked).
Click to expand...
Click to collapse
Try Magisk 14.0, install the module, download the modified apk from the module download tab, install the app, see if it works
Edit: I just read the last line, sorry
that is the only thing that i've thought about. Stock is the other way around, normal method works but topjohnwu's module doesn't. But Magisk xposed worked on every custom ROM I've used.

Choose an username... said:
Try Magisk 14.0, install the module, download the modified apk from the module download tab, install the app, see if it works
Edit: I just read the last line, sorry
that is the only thing that i've thought about. Stock is the other way around, normal method works but topjohnwu's module doesn't. But Magisk xposed worked on every custom ROM I've used.
Click to expand...
Click to collapse
I would have ultimately tried Magisk anyways if all else failed. I will try later. Probably tomorrow. If it works I'll call it solved and you get the prize.

Doc Ames said:
I would have ultimately tried Magisk anyways if all else failed. I will try later. Probably tomorrow. If it works I'll call it solved and you get the prize.
Click to expand...
Click to collapse
Nah don't want any price. a thank is enough
Which are the apps that don't work with Magisk?

@Doc Ames: it's probably just the ROM you've chosen. I've tried lots of Lineage/AOSP ROMs for the A7, Xposed has worked flawlessly in all of them.
My setup:
Vertex Carbide
Hellsgate EAS kernel, with data and cache formatted as F2FS
Phh's Superuser, for root
Busybox 1.27.2 by YashadSaraf
Xposed v89 official
No GApps, except MicroG and Play Store
I try to avoid Magisk, it's a nice concept, but systemless is more trouble than it's worth. Magisk has caused me tons of issues. I've tried it off and on for months but I keep switching back to good ol reliable Phh. I stopped using SuperSU ever since it was bought by an Asian (Chinese?) company.
Good luck!

Choose an username... said:
Nah don't want any price. a thank is enough
Which are the apps that don't work with Magisk?
Click to expand...
Click to collapse
I don't remember. If for some reason I have to use Magisk maybe I can find replacement apps.

AnonVendetta said:
@Doc Ames: it's probably just the ROM you've chosen. I've tried lots of Lineage/AOSP ROMs for the A7, Xposed has worked flawlessly in all of them.
My setup:
Vertex Carbide
Hellsgate EAS kernel, with data and cache formatted as F2FS
Phh's Superuser, for root
Busybox 1.27.2 by YashadSaraf
Xposed v89 official
No GApps, except MicroG and Play Store
I try to avoid Magisk, it's a nice concept, but systemless is more trouble than it's worth. Magisk has caused me tons of issues. I've tried it off and on for months but I keep switching back to good ol reliable Phh. I stopped using SuperSU ever since it was bought by an Asian (Chinese?) company.
Good luck!
Click to expand...
Click to collapse
Thank you for the suggestion. The issue is that there is no other ROM for the A7 (save PureNexus and stock ROMs) that will properly connect to my Bluetooth deck. I was trying to pursue a solution to the Bluetooth issue with custom ROMs for the A7 but it affects such a small number of users that nobody seems to think it's an issue. I tried the ROM you are using and had the above mentioned Bluetooth issue. I've tried a ton of ROMs. I'd rather get a fix to the Bluetooth issue so I can use whatever ROM I want. However, I posted a question about my Bluetooth issue and everybody just gave me the whole, "It's working on my machine. Must be your deck."

@Doc Ames: Well sorry to know that you're essentially forced to used a specific rom just to get your Bluetooth deck working. I don't use Bluetooth for anything but transferring files, that's worked in every ROM I've tried. But I have had issues in the past where a certain device would work on one ROM but not on another. It could be a ROM issue, or maybe an issue with the Bluetooth device you're using. Maybe a combo of both. I'm not a dev so there's nothing I can do except be sympathetic. Maybe you can elevate your issue with A7 devs so they can maybe look into whether there are underlying Bluetooth issues in their ROMs that need to be resolved. If the deck didn't cost too much, you might want to look into selling it and getting a more known, compatible deck that works with most ROMs. I guess it all just depends on how much it's worth to you to be able to run whatever ROM you want without worrying about whether your deck will work.
Good luck!

@Doc Ames,
If you haven't yet, give the UNITY Xposed package (by @ahrion) a try. On my G3 I had nothing but troubles trying to get Xposed and ParanoidAndroid working. With UNITY everything came together to my surprise.
Also just flashed it tonight on the Axon B32 stock. Far as other ROMs go I've used both unofficial and official Xposed on various ROMs like VertexOS and Dark ROM without issue.
I too stay away from Magisk so I can't speak to any of the systemless installers.
http://forum.xda-developers.com/showthread.php?t=3697756
[12/18/2017] Xposed Framework v88.9 [UNITY]
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5

marcdw said:
@Doc Ames,
If you haven't yet, give the UNITY Xposed package (by @ahrion) a try. On my G3 I had nothing but troubles trying to get Xposed and ParanoidAndroid working. With UNITY everything came together to my surprise.
Also just flashed it tonight on the Axon B32 stock. Far as other ROMs go I've used both unofficial and official Xposed on various ROMs like VertexOS and Dark ROM without issue.
I too stay away from Magisk so I can't speak to any of the systemless installers.
http://forum.xda-developers.com/showthread.php?t=3697756
[12/18/2017] Xposed Framework v88.9 [UNITY]
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
Click to expand...
Click to collapse
Thank you for the suggestion. I tried the UNITY Xposed. No joy. Same result.

Can't enforce SELinux for SafetyNet (LineageOS 14.1, N910C)

Good evening everybody. Could anyone please assist me in a nuisance I'm currently facing?
You see, what I'm trying to do is to succesfully pass the Safetynet check on my device. As of now I fail both Integrity and CTS profile checks.
I've got Lineage OS installed from here https://forum.xda-developers.com/note-4/orig-development/n910c-n190h-lineageos-14-1-t3720964 and the latest TWRP as a Recovery.
Now, let me list all the attempts I've made so far:
I tried the console method. The "setenforce 1" command changes nothing (no, I did not forget to type "su" first). "Getenforce" always returns with 0.
I tried editing /sys/fs/selinux/enforce manually. The file instantly reverts back to 0. I tried to glue it with "chattr +i" command, but it returned with some nonsense about typewriters.
I tries iSU. Neither "Change SELinux state" nor "Fake Enforce" options help.
I tried Magisk. Did not help either.
I tried setenforce and the manual change of selinux/enforce from the terminal in TWRP. Good news: at least the getenforce command returns 1 after setenforce 1. Bad news: when I boot into the system I still get Permissive mode and 0 from getenforce.
I tried editing /proc/cmdline. It was already set to enforce, but the system did not care apparently.
I tried SELinuxModeChanger.
I tried SELinux Switch.
It feels like the only thing I did not try at this point is to throw my phone into the toilet, but I would like to keep it as a last resort.
If anyone has any ideas, I would be tremendously grateful.

Unofficial builds of LineageOS are not digitally signed to prove they don't contain any malicious code. That means they will never pass SafetyNet. Hopefully that all will change when (if) we get official support. Sorry mate ?

oddbehreif said:
Unofficial builds of LineageOS are not digitally signed to prove they don't contain any malicious code. That means they will never pass SafetyNet. Hopefully that all will change when (if) we get official support. Sorry mate
Click to expand...
Click to collapse
Oh. Well, thanks for the reply.

Passing safety net
This might not be helpful, but I've had some issues passing safety net on unofficial lineage builds before, but I've found a couple ways around it (keep in mind I'm using a different device). I added petnoire's safety net spoofer to magisk, used magisk hide that hides the magisk repo files, and made sure that no apps were granted root access, and now my phone is working perfectly fine with safety net apps.

Not hiding root

Hello, I've recently installed the newest version of LineageOS17.1 on my beloved S5. I'm using Magisk (latest version) and I tried hiding my root via 1st - changing the package name and 2nd - Magisk Hide. I used to play a lot of Pokemon GO and it was working perfectly fine on LineagesOS 15, back then. Sadly, it's no longer working - this time, however, I'm using my phone not only for Pokemon GO (that inflicts a problem with rooted phones) but also a bank app. It's crucial for me to use the bank app as it has a limit and whenever I'd like to spend >50$, I have to enter a code which is generated on the app only. So, is there a way to properly hide my root?
I'm on LineageOS17.1, with mod for increased speaker volume and custom kernel (Tuned Kernel by fbs).

inc0n3ck said:
Hello, I've recently installed the newest version of LineageOS17.1 on my beloved S5. I'm using Magisk (latest version) and I tried hiding my root via 1st - changing the package name and 2nd - Magisk Hide. I used to play a lot of Pokemon GO and it was working perfectly fine on LineagesOS 15, back then. Sadly, it's no longer working - this time, however, I'm using my phone not only for Pokemon GO (that inflicts a problem with rooted phones) but also a bank app. It's crucial for me to use the bank app as it has a limit and whenever I'd like to spend >50$, I have to enter a code which is generated on the app only. So, is there a way to properly hide my root?
I'm on LineageOS17.1, with mod for increased speaker volume and custom kernel (Tuned Kernel by fbs).
Click to expand...
Click to collapse
Did you try toggling Magisk hide off/on as per Magisk support thread?
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
@Didgeridoohan has a good article on the matter here:
https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Principially Magisk Hide is working in this state and e. g. my banking app was, too.
Other users have full support, but i don't know what's wrong here.
Everything Magisk was special when i tried Los17. Bootlooping after a Magisk update with successful reboot after the umpteenth time.
Endless boot after installation of the Youtube Vanced module. Entering TWRP at boot also was impossible(but you could access Fastboot), but there seemed to be some watchdog timer and after about 30min Twrp came up instead of the os.

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