Database Info

Bypassing SafetyNet

Hey guys...
So as some of you may know, Pokemon GO recently released in India. I wish to play the game, but am unable to do so due to the SafetyNet checks it uses...
I read somewhere that the SafetyNet API uses a feature called "Verified Boot" in order to check whether the bootloader is unlocked or not. Obviously my device has an unlocked bootloader and I'm running CM14.1 as of now.
Any ways to get Pokemon GO working?

Adrao123 said:
Hey guys...
So as some of you may know, Pokemon GO recently released in India. I wish to play the game, but am unable to do so due to the SafetyNet checks it uses...
I read somewhere that the SafetyNet API uses a feature called "Verified Boot" in order to check whether the bootloader is unlocked or not. Obviously my device has an unlocked bootloader and I'm running CM14.1 as of now.
Any ways to get Pokemon GO working?
Click to expand...
Click to collapse
* After flashing, delete the su directories (/system/bin/su or /system/xbin/su).
* Then flash supersu in systemless mode (echo SYSTEMLESS=true>>/data/.supersu command)
* Then flash suhide
* Then flash Xposed Framework, the systemless version.
* Install rootswitch, then toggle "stop all SU daemons" on, then disable root.
http://forum.xda-developers.com/apps/supersu/suhide-t3450396
http://www.asus.com/zentalk/tw/thread-173542-1-1.html

moralesnery said:
* After flashing, delete the su directories (/system/bin/su or /system/xbin/su).
* Then flash supersu in systemless mode (echo SYSTEMLESS=true>>/data/.supersu command)
* Then flash suhide
* Then flash Xposed Framework, the systemless version.
* Install rootswitch, then toggle "stop all SU daemons" on, then disable root.
http://forum.xda-developers.com/apps/supersu/suhide-t3450396
http://www.asus.com/zentalk/tw/thread-173542-1-1.html
Click to expand...
Click to collapse
The Xposed Framework does not support SDK25 yet...

Adrao123 said:
The Xposed Framework does not support SDK25 yet...
Click to expand...
Click to collapse
Sorry, I didn't pay attention to the CM version.
You have to go back to CM13 or another 6.x equivalent at least

moralesnery said:
Sorry, I didn't pay attention to the CM version.
You have to go back to CM13 or another 6.x equivalent at least
Click to expand...
Click to collapse
It still does not work... suhide is facing issues flashing
it says something about /system/xbin/su still being present... when I try to manually rm -rf it, /system is a ro mounted directory... even if I mount it manually with rw it still doesnt delete

you can use magisk with phhs superuser, works fine with that

aldanopolis said:
you can use magisk with phhs superuser, works fine with that
Click to expand...
Click to collapse
Flashed it... still not working... I flashed with phh superuser... any chance it is conflicting with CMs inbuilt root system. If so, how can I disable CMs root...
Also are there any AOSP 7.1.1 ROMS out there?

Adrao123 said:
Flashed it... still not working... I flashed with phh superuser... any chance it is conflicting with CMs inbuilt root system. If so, how can I disable CMs root...
Also are there any AOSP 7.1.1 ROMS out there?
Click to expand...
Click to collapse
you need to remove su binary from /system/bin and /system/xbin
sorry for the late answer

In CM14 you have two choises
* After fresh install download SuperSU and do a full unroot
* Download and install iSu to hide root
Both of those options work as I have used them before.

[Guide] Bypass Safetynet on MM with Custom ROM & Kernel (Looking for testers)

I would first like to say that I cannot guarantee if this works on ALL devices. I was able to get this to work on the Galaxy S6 and posted it on the Galaxy S6 forums, however I am looking for people with other devices to see if it works for them as well (because why not share the bypass love to everyone ) If it works, please post a screenshot to confirm so I can post it on the thread here. Thanks.
(Please note that I am not responsible if your phone bricks etc. Please use at your own risk! Myself and others who have also tested this bypass have had no reported issues of this bypass causing some sort of brick etc., but I cannot guarantee anything.)
*This is a copy and paste of a thread I made on another forums and I felt like sharing it here. If there is any mistakes in the post, please tell me so I can fix it. Thanks.*​__________________________________​
Since October 2016, Google has (yet again) changed their way on how SafetyNet works and how they can now easily figure out if your phone is rooted or not. This caused many issues for rooted Android users who wanted to play games such as PKMNGO and use apps such as Snapchat. However, there is still ways to bypass SafetyNet.
Tested Devices:
- Samsung Galaxy S6
- Samsung Galaxy S5
*Looking for people with other devices to try and see if it works for themselves so I can add the device to the list.*
__________________________________​
Requirements:
- Basic Understanding on how to use Custom Recovery, flashing zip files etc.
- Running on Android 6.0 (Looking for anyone with Android 7 to see if this works for them as well.)
- Phone has a custom recovery (I suggest TWRP) and on a Custom ROM. (Stock roms "should" work too.)
- Rom should have November 1st Security update or older updates. (Have not tested with roms with November 5th Security update and higher.)
- Magisk V10.2 & Magisk Manager 3.0
- SafetyNet Checker
- Phh Super User APK. PlayStore or 2.0 Beta
- Root File Explorer. I suggest Root Browser
- Kernel Adiutor
- Root Checker
(I have had issues trying Xposed on Magisk V9, however it may work on V10.2)
Tutorial
**WARNING: BIG IMAGES** (Had no time to resize them, but will soon.)
Before we begin, I suggest that you make a Nandroid backup through your preferred Custom Recovery. I suggest you use TWRP however CWM "should" work, but I have not tried myself.
Step 1:
Clean Install
The first step 'is' optional, however it is recommended that you do a clean install. I will be using Alexis Rom 8.0 Beta 2 for my Galaxy S6, but any rom should work. (Other than certain GraceUX ports, but am able to get it to work with other ported rom like CoreUi (a MIUI port) for the Galaxy S6). You should also flash a kernel now as well. I use to personally use Arter97 as SuperSU is not installed in this kernel, however Arter97 is slowly starting to become unstable as it hasn't been updated and there is better kernels out there. For this tutorial, I will be using Twisted Kernel.
Step 2:
Removing SuperSU
This step is 'also' optional, but ONLY if your rom/kernel does not automatically install SuperSU for you. In my case, it is automatically installed.
What you will need to do is to go to the SuperSU app, go to settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Scroll down until you see "Full unroot" and click it.
A popup will come up and click "Continue", then followed by another popup and click "NO".
Once you click no, your phone will freeze and then reboot. You should then install Root Checker to verify if your phone is unrooted.
(If for some reason, you are unable to use the SuperSU app but you know SuperSU is installed, I'd suggest you download UPDATE-unSU-signed.zip and flash it as it will manually remove SuperSU.)
Step 3:
Installing required APKs.
You will now need to install MagiskManager 3.0, SafetyNet Helper Sample, PHH Super User APK, Root Browser and Kernel Adiutor.
Step 4:
Flashing MagiskV10.2
You will need to reboot into your custom recovery and flash "Magisk-v10.2.zip", followed by rebooting. If you receive ERROR: 1 in TWRP when it is trying to mount SU, I suggest reflashing a kernel (and re-remove SuperSU), uninstalling Magisk with MagiskUninstaller (in Magisk thread) and reinstall Magisk V10.2, or reinstalling your rom.
Once you have flashed the file, reboot into System and open Magisk Manager to verify you have installed Magisk. A little pop up will open to allow Magisk to have root. Make sure to click allow and set it so it has root for "Forever".
If it states that root isn't properly installed, manually flash PHH Super User V266-2.
Step 5:
Enabling Magisk Hide
In Magisk Manager, go to the side menu and go to "Settings." You will see an unchecked box that says "Enable Magisk Hide." Select it and reboot. Re-open Magisk Manager and verify that it is now check marked. If the App crashes when you select "Enable Magisk Hide", reboot your phone and retry.
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow."
Once you are done, open up SafetyNet Helper Sample and it 'should' pass. If you are getting "Response Validation Failed" and the background is blue, uninstall Magisk by flashing Magisk Uninstaller, flash UPDATE-unSU-signed.zip, then reflash Magisk V10.2. Then, go back to Step 5 and enable Magisk Hide.
Step 7:
Use Kernel Adiutor to automatically set permissions in init.d
This last step is 'optional', however it automates the permission setting as every time you reboot your system, the file permissions will reset. Open up Kernel Adiutor, go to the sidebar and scroll down until you see 'Init.d'. Click it and make sure "Emulate Init.d" is enabled.
Then click the plus button, set the name to "Permissions" and then add the following script:
"chmod 640 /sys/fs/selinux/enforce" and "chmod 440 /sys/fs/selinux/policy" and save the files.
Also allow root access to Kernel Adiutor!
Step 8:
Reboot
Reboot your device, let Kernel Adiutor do its countdown (you will see in the notifications drop down) and once it says "Applying settings completed!", open up Safetynet and you should be passing!
Credits:
topjohnwu - Main developer of Magisk and Magisk Supported Phh Super User
This XDA thread - Helped me figure out how to do this bypass in the first place.
CoreUi Telegram Chat - Helped me test this bypass to see if it worked on different S6 models. Join here!
If I forgot to credit anyone, please tell me.
__________________________________​
If there is any mistakes I made, spelling, phrasing etc., please tell me so I can fix it. Thanks.

Finally I can play again since they added the SafetyNet check! It's been way too long.
Worked perfectly on my Galaxy S5! I'm using the Resurrection Remix KLTE 6.0 for my Galaxy S5 so it came with it's own root. I just searched Root in settings, disabled it, flashed the unroot zip and then I was unrooted. Except for that everything worked the way you described! I forgot to reboot after Magisk Hide so I unrooted and reflashed Magisk but I'm not sure that was needed to be honest. Is SafetyNet Checker really needed? Magisk Manager also has a SafteyNet checker.
When I get more time I will do a backup and flash the 7.1.1 rom too and test if it works.
Complete package with everything needed in the guide for the lazy:
https://mega.nz/#!R18XRZQB!pgGx2LgNV8aqfwhsutmUnC4jay-FTGVR3-a9r3TJaEA

Martan404 said:
Finally I can play again since they added the SafetyNet check! It's been way too long.
Worked perfectly on my Galaxy S5! I'm using the Resurrection Remix KLTE 6.0 for my Galaxy S5 so it came with it's own root. I just searched Root in settings, disabled it, flashed the unroot zip and then I was unrooted. Except for that everything worked the way you described! I forgot to reboot after Magisk Hide so I unrooted and reflashed Magisk but I'm not sure that was needed to be honest. Is SafetyNet Checker really needed? Magisk Manager also has a SafteyNet checker.
When I get more time I will do a backup and flash the 7.1.1 rom too and test if it works.
Click to expand...
Click to collapse
There 'is' a Safetynet checker in Magisk Manager, however it will always say 'CTS Profile error', while SafetyNet Checker will say if its either a CTS error, Response Validation error, Play Store error etc. Maybe it's just a bug in Magisk Manager but if it gets fixed; I'll remove SafetyNet Checker from the tutorial.

xJovs said:
There 'is' a Safetynet checker in Magisk Manager, however it will always say 'CTS Profile error', while SafetyNet Checker will say if its either a CTS error, Response Validation error, Play Store error etc. Maybe it's just a bug in Magisk Manager but if it gets fixed; I'll remove SafetyNet Checker from the tutorial.
Click to expand...
Click to collapse
Can confirm that this works on 7.1.1 roms too! As I mentioned in my other post I use the Resurrection Remix rom.
By the way, you could mention that instead of using root browser to change permissions you could skip that step all together and just add the modification to Kernel Auditor. And instead of rebooting to test it you can just click the "Permissions" addition to execute the script right away just to make sure it works and then do a reboot to confirm.

Thank you so much. it worked

help plse plse give steps by step for 7.1.1(RR)
---------- Post added at 02:58 AM ---------- Previous post was at 02:54 AM ----------
i tried but cts profile mismatch becomes false
Sent from my MotoG3 using Tapatalk

Running a Mi Max here and have to say: Not working!
If i fully unroot the phone (magisk uninstaller / unSU script) then safety net helper gives me a red screen (CTS profile mismatch) but after installing Magisk 10.2 i only get a blueish screen in safetynethelper saying "response validation: fail"

naveenfre said:
help plse plse give steps by step for 7.1.1(RR)
---------- Post added at 02:58 AM ---------- Previous post was at 02:54 AM ----------
i tried but cts profile mismatch becomes false
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
1. Open the Settings app, and go About phone tab and spam click on Version to enable Developer Tools.
2. Do a search in the settings for "Root" and disable Root access.
3. Reboot to Recovery mode and flash this unroot https://forum.xda-developers.com/showpost.php?p=63615067
4. Reboot phone and follow xJovs' guide from step 3
Note: I also used the flashable zip file from the guide to get root and did not install the APK. https://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921
g_BonE said:
Running a Mi Max here and have to say: Not working!
If i fully unroot the phone (magisk uninstaller / unSU script) then safety net helper gives me a red screen (CTS profile mismatch) but after installing Magisk 10.2 i only get a blueish screen in safetynethelper saying "response validation: fail"
Click to expand...
Click to collapse
It might be because of the Kernel but I'm just speculating. Try flashing a new one to see if it helps!

g_BonE said:
Running a Mi Max here and have to say: Not working!
If i fully unroot the phone (magisk uninstaller / unSU script) then safety net helper gives me a red screen (CTS profile mismatch) but after installing Magisk 10.2 i only get a blueish screen in safetynethelper saying "response validation: fail"
Click to expand...
Click to collapse
It will always return blue right after installing Magisk. You need to follow through with the whole tutorial to work. If you have, then it's probably your rom. It happened with me on GraceUX roms.

Latest version of PoGo doesn't appear in magisk hide menu

It works
Thanks! Editing the permission of SElinux files works for me
Nexus 5X
GooglePixelROM v7.0.1
Android 7.1.2
NPG05D
Using Magisk 11.1
Now I can pass SafetyNet and use AndroidPay on a custom ROM

Galaxy Note 3 (N9005) MagmaNX with Magisk v11.1 + MagiskSU
CTS profile match: false
Basic Integrity: false

xJovs said:
I would first like to say that I cannot guarantee if this works on ALL devices. I was able to get this to work on the Galaxy S6 and posted it on the Galaxy S6 forums, however I am looking for people with other devices to see if it works for them as well (because why not share the bypass love to everyone ) If it works, please post a screenshot to confirm so I can post it on the thread here. Thanks.
(Please note that I am not responsible if your phone bricks etc. Please use at your own risk! Myself and others who have also tested this bypass have had no reported issues of this bypass causing some sort of brick etc., but I cannot guarantee anything.)
*This is a copy and paste of a thread I made on another forums and I felt like sharing it here. If there is any mistakes in the post, please tell me so I can fix it. Thanks.*​__________________________________​
Since October 2016, Google has (yet again) changed their way on how SafetyNet works and how they can now easily figure out if your phone is rooted or not. This caused many issues for rooted Android users who wanted to play games such as PKMNGO and use apps such as Snapchat. However, there is still ways to bypass SafetyNet.
Tested Devices:
- Samsung Galaxy S6
- Samsung Galaxy S5
*Looking for people with other devices to try and see if it works for themselves so I can add the device to the list.*
__________________________________​
Requirements:
- Basic Understanding on how to use Custom Recovery, flashing zip files etc.
- Running on Android 6.0 (Looking for anyone with Android 7 to see if this works for them as well.)
- Phone has a custom recovery (I suggest TWRP) and on a Custom ROM. (Stock roms "should" work too.)
- Rom should have November 1st Security update or older updates. (Have not tested with roms with November 5th Security update and higher.)
- Magisk V10.2 & Magisk Manager 3.0
- SafetyNet Checker
- Phh Super User APK. PlayStore or 2.0 Beta
- Root File Explorer. I suggest Root Browser
- Kernel Adiutor
- Root Checker
(I have had issues trying Xposed on Magisk V9, however it may work on V10.2)
Tutorial
**WARNING: BIG IMAGES** (Had no time to resize them, but will soon.)
Before we begin, I suggest that you make a Nandroid backup through your preferred Custom Recovery. I suggest you use TWRP however CWM "should" work, but I have not tried myself.
Step 1:
Clean Install
The first step 'is' optional, however it is recommended that you do a clean install. I will be using Alexis Rom 8.0 Beta 2 for my Galaxy S6, but any rom should work. (Other than certain GraceUX ports, but am able to get it to work with other ported rom like CoreUi (a MIUI port) for the Galaxy S6). You should also flash a kernel now as well. I use to personally use Arter97 as SuperSU is not installed in this kernel, however Arter97 is slowly starting to become unstable as it hasn't been updated and there is better kernels out there. For this tutorial, I will be using Twisted Kernel.
Step 2:
Removing SuperSU
This step is 'also' optional, but ONLY if your rom/kernel does not automatically install SuperSU for you. In my case, it is automatically installed.
What you will need to do is to go to the SuperSU app, go to settings.
Scroll down until you see "Full unroot" and click it.
A popup will come up and click "Continue", then followed by another popup and click "NO".
Once you click no, your phone will freeze and then reboot. You should then install Root Checker to verify if your phone is unrooted.
(If for some reason, you are unable to use the SuperSU app but you know SuperSU is installed, I'd suggest you download UPDATE-unSU-signed.zip and flash it as it will manually remove SuperSU.)
Step 3:
Installing required APKs.
You will now need to install MagiskManager 3.0, SafetyNet Helper Sample, PHH Super User APK, Root Browser and Kernel Adiutor.
Step 4:
Flashing MagiskV10.2
You will need to reboot into your custom recovery and flash "Magisk-v10.2.zip", followed by rebooting. If you receive ERROR: 1 in TWRP when it is trying to mount SU, I suggest reflashing a kernel (and re-remove SuperSU), uninstalling Magisk with MagiskUninstaller (in Magisk thread) and reinstall Magisk V10.2, or reinstalling your rom.
Once you have flashed the file, reboot into System and open Magisk Manager to verify you have installed Magisk. A little pop up will open to allow Magisk to have root. Make sure to click allow and set it so it has root for "Forever".
If it states that root isn't properly installed, manually flash PHH Super User V266-2.
Step 5:
Enabling Magisk Hide
In Magisk Manager, go to the side menu and go to "Settings." You will see an unchecked box that says "Enable Magisk Hide." Select it and reboot. Re-open Magisk Manager and verify that it is now check marked. If the App crashes when you select "Enable Magisk Hide", reboot your phone and retry.
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow."
Once you are done, open up SafetyNet Helper Sample and it 'should' pass. If you are getting "Response Validation Failed" and the background is blue, uninstall Magisk by flashing Magisk Uninstaller, flash UPDATE-unSU-signed.zip, then reflash Magisk V10.2. Then, go back to Step 5 and enable Magisk Hide.
Step 7:
Use Kernel Adiutor to automatically set permissions in init.d
This last step is 'optional', however it automates the permission setting as every time you reboot your system, the file permissions will reset. Open up Kernel Adiutor, go to the sidebar and scroll down until you see 'Init.d'. Click it and make sure "Emulate Init.d" is enabled.
Then click the plus button, set the name to "Permissions" and then add the following script:
"chmod 640 /sys/fs/selinux/enforce" and "chmod 440 /sys/fs/selinux/policy" and save the files.
Also allow root access to Kernel Adiutor!
Step 8:
Reboot
Reboot your device, let Kernel Adiutor do its countdown (you will see in the notifications drop down) and once it says "Applying settings completed!", open up Safetynet and you should be passing!
Credits:
topjohnwu - Main developer of Magisk and Magisk Supported Phh Super User
This XDA thread - Helped me figure out how to do this bypass in the first place.
CoreUi Telegram Chat - Helped me test this bypass to see if it worked on different S6 models. Join here!
If I forgot to credit anyone, please tell me.
__________________________________​
If there is any mistakes I made, spelling, phrasing etc., please tell me so I can fix it. Thanks.
Click to expand...
Click to collapse
i have HTC Desire 820 d820u running 6.0.1 mm stock.
is this will be ok to try?????

yo_honey said:
i have HTC Desire 820 d820u running 6.0.1 mm stock.
is this will be ok to try?????
Click to expand...
Click to collapse
Could but I have no idea.

I have tried latest magisk
xJovs said:
Could but I have no idea.
Click to expand...
Click to collapse
Here is full guide https://forum.xda-developers.com/desire-820/general/guide-bypass-safetynet-magisk-t3592508

Doesn't this work for Lollipop or is it just that you haven't tested?

xJovs said:
I would first like to say that I cannot guarantee if this works on ALL devices. I was able to get this to work on the Galaxy S6 and posted it on the Galaxy S6 forums, however I am looking for people with other devices to see if it works for them as well (because why not share the bypass love to everyone ) If it works, please post a screenshot to confirm so I can post it on the thread here. Thanks.
(Please note that I am not responsible if your phone bricks etc. Please use at your own risk! Myself and others who have also tested this bypass have had no reported issues of this bypass causing some sort of brick etc., but I cannot guarantee anything.)
*This is a copy and paste of a thread I made on another forums and I felt like sharing it here. If there is any mistakes in the post, please tell me so I can fix it. Thanks.*​__________________________________​
Since October 2016, Google has (yet again) changed their way on how SafetyNet works and how they can now easily figure out if your phone is rooted or not. This caused many issues for rooted Android users who wanted to play games such as PKMNGO and use apps such as Snapchat. However, there is still ways to bypass SafetyNet.
Tested Devices:
- Samsung Galaxy S6
- Samsung Galaxy S5
*Looking for people with other devices to try and see if it works for themselves so I can add the device to the list.*
__________________________________​
Requirements:
- Basic Understanding on how to use Custom Recovery, flashing zip files etc.
- Running on Android 6.0 (Looking for anyone with Android 7 to see if this works for them as well.)
- Phone has a custom recovery (I suggest TWRP) and on a Custom ROM. (Stock roms "should" work too.)
- Rom should have November 1st Security update or older updates. (Have not tested with roms with November 5th Security update and higher.)
- Magisk V10.2 & Magisk Manager 3.0
- SafetyNet Checker
- Phh Super User APK. PlayStore or 2.0 Beta
- Root File Explorer. I suggest Root Browser
- Kernel Adiutor
- Root Checker
(I have had issues trying Xposed on Magisk V9, however it may work on V10.2)
Tutorial
**WARNING: BIG IMAGES** (Had no time to resize them, but will soon.)
Before we begin, I suggest that you make a Nandroid backup through your preferred Custom Recovery. I suggest you use TWRP however CWM "should" work, but I have not tried myself.
Step 1:
Clean Install
The first step 'is' optional, however it is recommended that you do a clean install. I will be using Alexis Rom 8.0 Beta 2 for my Galaxy S6, but any rom should work. (Other than certain GraceUX ports, but am able to get it to work with other ported rom like CoreUi (a MIUI port) for the Galaxy S6). You should also flash a kernel now as well. I use to personally use Arter97 as SuperSU is not installed in this kernel, however Arter97 is slowly starting to become unstable as it hasn't been updated and there is better kernels out there. For this tutorial, I will be using Twisted Kernel.
Step 2:
Removing SuperSU
This step is 'also' optional, but ONLY if your rom/kernel does not automatically install SuperSU for you. In my case, it is automatically installed.
What you will need to do is to go to the SuperSU app, go to settings.
Scroll down until you see "Full unroot" and click it.
A popup will come up and click "Continue", then followed by another popup and click "NO".
Once you click no, your phone will freeze and then reboot. You should then install Root Checker to verify if your phone is unrooted.
(If for some reason, you are unable to use the SuperSU app but you know SuperSU is installed, I'd suggest you download UPDATE-unSU-signed.zip and flash it as it will manually remove SuperSU.)
Step 3:
Installing required APKs.
You will now need to install MagiskManager 3.0, SafetyNet Helper Sample, PHH Super User APK, Root Browser and Kernel Adiutor.
Step 4:
Flashing MagiskV10.2
You will need to reboot into your custom recovery and flash "Magisk-v10.2.zip", followed by rebooting. If you receive ERROR: 1 in TWRP when it is trying to mount SU, I suggest reflashing a kernel (and re-remove SuperSU), uninstalling Magisk with MagiskUninstaller (in Magisk thread) and reinstall Magisk V10.2, or reinstalling your rom.
Once you have flashed the file, reboot into System and open Magisk Manager to verify you have installed Magisk. A little pop up will open to allow Magisk to have root. Make sure to click allow and set it so it has root for "Forever".
If it states that root isn't properly installed, manually flash PHH Super User V266-2.
Step 5:
Enabling Magisk Hide
In Magisk Manager, go to the side menu and go to "Settings." You will see an unchecked box that says "Enable Magisk Hide." Select it and reboot. Re-open Magisk Manager and verify that it is now check marked. If the App crashes when you select "Enable Magisk Hide", reboot your phone and retry.
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow."
Once you are done, open up SafetyNet Helper Sample and it 'should' pass. If you are getting "Response Validation Failed" and the background is blue, uninstall Magisk by flashing Magisk Uninstaller, flash UPDATE-unSU-signed.zip, then reflash Magisk V10.2. Then, go back to Step 5 and enable Magisk Hide.
Step 7:
Use Kernel Adiutor to automatically set permissions in init.d
This last step is 'optional', however it automates the permission setting as every time you reboot your system, the file permissions will reset. Open up Kernel Adiutor, go to the sidebar and scroll down until you see 'Init.d'. Click it and make sure "Emulate Init.d" is enabled.
Then click the plus button, set the name to "Permissions" and then add the following script:
"chmod 640 /sys/fs/selinux/enforce" and "chmod 440 /sys/fs/selinux/policy" and save the files.
Also allow root access to Kernel Adiutor!
Step 8:
Reboot
Reboot your device, let Kernel Adiutor do its countdown (you will see in the notifications drop down) and once it says "Applying settings completed!", open up Safetynet and you should be passing!
Credits:
topjohnwu - Main developer of Magisk and Magisk Supported Phh Super User
This XDA thread - Helped me figure out how to do this bypass in the first place.
CoreUi Telegram Chat - Helped me test this bypass to see if it worked on different S6 models. Join here!
If I forgot to credit anyone, please tell me.
__________________________________​
If there is any mistakes I made, spelling, phrasing etc., please tell me so I can fix it. Thanks.
Click to expand...
Click to collapse
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow." Which file gets which perms bud you mention the same file twice.

savvy1968 said:
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow." Which file gets which perms bud you mention the same file twice.
Click to expand...
Click to collapse
Yeah I had to change it on my other thread in the GS6 forums. However I'm stopping maintenance of these threads as MagiskHide deals with all that permission stuff automatically now.

Seems to not working on leeco le max 2

Magisk Root: XZ

Hi, Does anyone know if Magisk root is supported on the Xperia XZ (F8331)?
The reason I ask is I want to be able to hide root from some apps that will not work with root otherwise i'd use SuperSU.

rasseru16 said:
Hi, Does anyone know if Magisk root is supported on the Xperia XZ (F8331)?
The reason I ask is I want to be able to hide root from some apps that will not work with root otherwise i'd use SuperSU.
Click to expand...
Click to collapse
Yes V12 works great so far

dillalade said:
Yes V12 works great so far
Click to expand...
Click to collapse
Perfect thanks. Now rooted with Magisk

rasseru16 said:
Perfect thanks. Now rooted with Magisk
Click to expand...
Click to collapse
I have had boot loops twice now.
First time I had to do a reinstall.
2nd time I ran the magisk uninstall from TWRP.
Booted up after that
Just a heads up.
I'm researching how to resolve this. Not to sure

rasseru16 said:
Perfect thanks. Now rooted with Magisk
Click to expand...
Click to collapse
I'm rooted with magisk too but unable to hide root from apps like 8ball pool and other apps. Hide root functionality don't work at all.

Have no problems with Magisk V12 so far had it running for several days now. Hiding root from Snapchat, My EE and some other apps without issue. I dont have TWRP installed though.

rasseru16 said:
Perfect thanks. Now rooted with Magisk
Click to expand...
Click to collapse
How do you hide root? With me it just doesn't work. I enable hide root and select app.

Has anyone faced any bootloops with magisk.
Some research has shown it's perhaps when using viper4android together with magisk that can cause a bootloop. But that was on a Nexus 6p from my research.
Has anyone set up magisk and also viper4android, that can let me know if they have faced this bootloop?

I have found that I can use Magisk Root with 'AndroPlus Kernel' but not 'Sony Stock Patcher for Xperia XZ by AdrianDC'. Installing MAGISK under the Sony Stock Patcher Kernel caused TWRP to create an error "Unable to repack boot image!"

latest update working without any hiccups

pw1nce said:
I'm rooted with magisk too but unable to hide root from apps like 8ball pool and other apps. Hide root functionality don't work at all.
Click to expand...
Click to collapse
yes it works, u need to enable magisk core only to make safetynet work and magisk hide too

fastbooking said:
yes it works, u need to enable magisk core only to make safetynet work and magisk hide too
Click to expand...
Click to collapse
Can you prove that or do you mind writing a little guide how to get past safetynet?
I literally tried everything I could find to get Magisk Hide working with unlocked bootloader yesterday after the change to pass Safetynet for Pokemon Go. No chance. Before I could at least remove Magisk to run Go but now that's over. What I tried was latest A.35 with Stock + Patcher or AndroPlus with twrp and then Magisk 13.2 (plus fixes). But I always failed CTS and Basic Integegrity.
Even with Magisk Hide turned on and Core Modules only activated. No chance.

Delvius said:
Can you prove that or do you mind writing a little guide how to get past safetynet?
I literally tried everything I could find to get Magisk Hide working with unlocked bootloader yesterday after the change to pass Safetynet for Pokemon Go. No chance. Before I could at least remove Magisk to run Go but now that's over. What I tried was latest A.35 with Stock + Patcher or AndroPlus with twrp and then Magisk 13.2 (plus fixes). But I always failed CTS and Basic Integegrity.
Even with Magisk Hide turned on and Core Modules only activated. No chance.
Click to expand...
Click to collapse
How to fix this:
1. This fix is only a temporary fix. You will have to apply it after every reboot.
2. Use a Terminal emulator app or adb to enter these commands.
3. Use resetprop to delete the properties - again: I have no idea how this interferes with magisk behavior!!!! Do this at your own risk:
Code:
su
resetprop --delete init.svc.magisk_pfs
resetprop --delete init.svc.magisk_pfsd
resetprop --delete init.svc.magisk_service
resetprop --delete persist.magisk.hide
Using Magisk Core mode? also execute this command:
Code:
resetprop --delete ro.magisk.disable

smellz said:
How to fix this:
1. This fix is only a temporary fix. You will have to apply it after every reboot.
2. Use a Terminal emulator app or adb to enter these commands.
3. Use resetprop to delete the properties - again: I have no idea how this interferes with magisk behavior!!!! Do this at your own risk:
Code:
su
resetprop --delete init.svc.magisk_pfs
resetprop --delete init.svc.magisk_pfsd
resetprop --delete init.svc.magisk_service
resetprop --delete persist.magisk.hide
Using Magisk Core mode? also execute this command:
Code:
resetprop --delete ro.magisk.disable
Click to expand...
Click to collapse
Does it work for you? It doesn't for me. As I worte I did exactly this - no chance.
If it works for you, which firmware, kernel and twrp do you use?

Delvius said:
Does it work for you? It doesn't for me. As I worte I did exactly this - no chance.
If it works for you, which firmware, kernel and twrp do you use?
Click to expand...
Click to collapse
Yes it works with me.
Fw: 41.2.A.7.8
Kernel: AndroPlus kernel v27
Twrp: twrp-3.1.1-20170523-boot-kagura (DL: https://mega.nz/#F!bg9QhDzC!TTkhy2Fi6cNTZ1ojlmobRQ )
Magisk: v13.2 and 5.0.6 Manager

Delvius said:
Can you prove that or do you mind writing a little guide how to get past safetynet?
I literally tried everything I could find to get Magisk Hide working with unlocked bootloader yesterday after the change to pass Safetynet for Pokemon Go. No chance. Before I could at least remove Magisk to run Go but now that's over. What I tried was latest A.35 with Stock + Patcher or AndroPlus with twrp and then Magisk 13.2 (plus fixes). But I always failed CTS and Basic Integegrity.
Even with Magisk Hide turned on and Core Modules only activated. No chance.
Click to expand...
Click to collapse
You need to know that Google updated safetynet for magisk 13.2 so for the moment it's pretty random to get it working, the team is aware of that and they're making the necessary to fix this

smellz said:
Yes it works with me.
Fw: 41.2.A.7.8
Kernel: AndroPlus kernel v27
Twrp: twrp-3.1.1-20170523-boot-kagura (DL: https://mega.nz/#F!bg9QhDzC!TTkhy2Fi6cNTZ1ojlmobRQ )
Magisk: v13.2 and 5.0.6 Manager
Click to expand...
Click to collapse
Thanks a lot! You give me hope.

Delvius said:
Thanks a lot! You give me hope.
Click to expand...
Click to collapse
V13.3 fix safetynet
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Code:
v13.3
- [MagiskHide] Update to bypass Google CTS (2017.7.17)
- [resetprop] Properly support removing persist props
- [uninstaller] Remove Magisk Manager and persist props

Still not working for me even with latest version. I'm still waiting silently for any help here.

boydzethuong said:
Still not working for me even with latest version. I'm still waiting silently for any help here.
Click to expand...
Click to collapse
What kernel are you using?
Here is a small guide which definitely works:
1.Flash firmware 4.2.A.7.8
2. Uses tobias.waldvogel tool for fido_keys
Code:
-.ftf with WinRAR open,
-Kernel.in unpack,
-Open Flashtool,
-Select Top Tools,
-Sin Editor and in the next window
-Extract data.
-Now the extracted kernel.elf in the folder of the waldvogel its tool,
-There open the WinKonsole,
-Enter this command:
-Rootkernel kernel.elf boot.img,
-Disable sony_ric => YES
-Disable ... verity => YES
-DRM-Fix => YES
-TWRP => NO
-BusyBox => NO
-
NOW THE KERNEL FLASH
3. Flash TWRP: twrp-3.1.1-20170523-boot-kagura (DL: https://mega.nz/#F!bg9QhDzC!TTkhy2Fi6cNTZ1ojlmobRQ )
4. Flash Kernel via TWRP - AndroPlus kernel v27 and Reboot
5. Flash Magisk v13.3 via TWRP
Finished and safetynet should work

LineageOS + Magisk SafetyNet

Hello,
can anybody help me for my Problem with my Galaxy S4 GT-I9506
i have do the following
1. TWRP install the actual version
2. flash lineage-16.0-20190609-UNOFFICIAL-ks01ltexx https://forum.xda-developers.com/galaxy-s4/i9506-develop/rom-lineageos-16-0-unofficial-galaxy-s4-t3848597
3. flash open_gapps-arm-9.0-pico-20190612 TWRP
4. flash Magisk-v19.3 mit TWRP
But i have problems with them
https://prntscr.com/o7onem
https://prntscr.com/o7oneu
https://prntscr.com/o7oner
i have no idea what i can do can anybody help me please?

Does the ROM come rooted? It may have system root inside still, my s5 ROMs always did I think. I always had to use adb shell or flash a zip inside twrp. Usually did both.
Search XDA for osm0sis tool called unsu, it should be a .zip. Flash in twrp after installing gapps and booting once. This should clear system root, and allow you to pass once magisk is installed.
The other issue I can think of is maybe signature verification or something with the playstore. I don't remember what it is, my phones and ROMs have always worked after magisk. If the above steps don't work maybe that's related. We will have to look around if that's the case

I had a look at the device tree and I can see a couple of things for your dev @kyasu to possibly add
- we had safetynet start failing a few weeks back on i9505 and these were the fixes I found
- Product_name - Samsung never released a product called full_ks01ltexx - will need to be set to correct product that google recognises by a build_prop_override ("GT-I9506" or similar).
- Change build fingerprints to pixel3 versions.
- hide permissive with init script.
these 2 commits here show what needs done:
https://github.com/JDCTeam/android_...mmit/ea27cf29e4084d860fb8549be2e3cdb1599a6d08
https://github.com/PixelExperience-...mmit/045dc32219172a288c10f503478deb3eb3b2aee5

andrew2432 said:
Does the ROM come rooted? It may have system root inside still, my s5 ROMs always did I think. I always had to use adb shell or flash a zip inside twrp. Usually did both.
Search XDA for osm0sis tool called unsu, it should be a .zip. Flash in twrp after installing gapps and booting once. This should clear system root, and allow you to pass once magisk is installed.
The other issue I can think of is maybe signature verification or something with the playstore. I don't remember what it is, my phones and ROMs have always worked after magisk. If the above steps don't work maybe that's related. We will have to look around if that's the case
Click to expand...
Click to collapse
is this tool correct? https://forum.xda-developers.com/showpost.php?p=63615067
is the rom correct what i use?

OK i have unSu the device and have reinstall Magisk ..
https://prnt.sc/o929eu
but i have the same problem

tuvok1981de said:
OK i have unSu the device and have reinstall Magisk ..
https://prnt.sc/o929eu
but i have the same problem
Click to expand...
Click to collapse
- have you tried changing fingerprint with Magiskhide?
- has it worked previously and just recently stopped working or is this your first attempt?
- do other users on the same ROM have similar results?
I incidentally also checked DT if the ROM is rooted and doesn't look like it. Kernel also has namespace commits too, so it's not that.

Buff99 said:
- have you tried changing fingerprint with Magiskhide?
- has it worked previously and just recently stopped working or is this your first attempt?
- do other users on the same ROM have similar results?
I incidentally also checked DT if the ROM is rooted and doesn't look like it. Kernel also has namespace commits too, so it's not that.
Click to expand...
Click to collapse
- yes i have make with MagiskHidePropsConf-v.4.0.3 and terminal props S4 and S4 Active variante but it will not do this
- it will not work all the time where i have flash my S4
- i have no idea iam not the developer from the rom iam only a User

1. Flash twrp
2. Full wipe, system data internal
3. Flash ROM, boot
4. Flash gapps, boot
5. Flash magisk, should pass
6. If not, change selinux to enforcing
Let us know?

andrew2432 said:
1. Flash twrp
2. Full wipe, system data internal
3. Flash ROM, boot
4. Flash gapps, boot
5. Flash magisk, should pass
6. If not, change selinux to enforcing
Let us know?
Click to expand...
Click to collapse
Point 1. is on the Phone
ähm where must i make Point 6 ?

andrew2432 said:
1. Flash twrp
2. Full wipe, system data internal
3. Flash ROM, boot
4. Flash gapps, boot
5. Flash magisk, should pass
6. If not, change selinux to enforcing
Let us know?
Click to expand...
Click to collapse
OK i have make flash new all 5 Points
but ctsProfile: false / basicIntegrity: false on Magisk Manager

tuvok1981de said:
-
- i have no idea iam not the developer from the rom iam only a User
Click to expand...
Click to collapse
Yeah, well this is a developer forum. There is a thread for the ROM you use. It is assumed you have already seeked advice there from other users of the same rom...?
Being aware of whether others have this working or not shows whether you are wasting your time or not.

Buff99 said:
Yeah, well this is a developer forum. There is a thread for the ROM you use. It is assumed you have already seeked advice there from other users of the same rom...?
Being aware of whether others have this working or not shows whether you are wasting your time or not.
Click to expand...
Click to collapse
in this forum say the users i must go in the Samsung S4 Forum and ask my Question!

tuvok1981de said:
in this forum say the users i must go in the Samsung S4 Forum and ask my Question!
Click to expand...
Click to collapse
I searched safety net inside the ROM forum, it said to change selinux to enforcing. I am not sure how. Maybe with a magisk module
Edit: credit for these instructions goes to @DiamondJohn
The user only installed magisk and safety net passed. Are you installing xposed or anything?
stecko said:
Can you guide me how to switch selinux to enforcing?
Click to expand...
Click to collapse
in a terminal, or part of a boot script
Code:
su;
setenforce 1;
or you could try the app I built, where you will find it under the menu
Code:
Current State>SELinux>Set SELinux Enforcing.
https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260

andrew2432 said:
I searched safety net inside the ROM forum, it said to change selinux to enforcing. I am not sure how. Maybe with a magisk module
Edit: credit for these instructions goes to @DiamondJohn
The user only installed magisk and safety net passed. Are you installing xposed or anything?
in a terminal, or part of a boot script
Code:
su;
setenforce 1;
or you could try the app I built, where you will find it under the menu
Code:
Current State>SELinux>Set SELinux Enforcing.
https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260
Click to expand...
Click to collapse
Very Nice .. this part have help ..
Code:
su;
setenforce 1;
https://prnt.sc/o9gchi
thank you!

FingerFace and Android 11

Hi,
I'm thinking of upgrading to android 11 but I won't do it without the option of using FingerFace for those apps I have that are not using the newer api's for biometric authentication. Has anyone got FingerFace working on Android 11?

yes it does work. I'm on 11 beta 3 and fingerface works, but you have to install the prereleased Riru-edxposed for android R or else you'll bootloop when you install edxposed and reboot. That's what I experienced unless there's a fix I don't know about. However, you might not need xposed or fingerface anymore. I found that the 2 apps I needed fingerface for - Lastpass and Chase app - they've since updated so that you can use face authentication.

neo_lithic3K said:
yes it does work. I'm on 11 beta 3 and fingerface works, but you have to install the prereleased Riru-edxposed for android R or else you'll bootloop when you install edxposed and reboot. That's what I experienced unless there's a fix I don't know about. However, you might not need xposed or fingerface anymore. I found that the 2 apps I needed fingerface for - Lastpass and Chase app - they've since updated so that you can use face authentication.
Click to expand...
Click to collapse
You have the links for riru edxposed for Android R?

You'll need to install Edxposed manager first. Then Go to the third tab called Canary. Select the v0.5.0.6 for android r option and click install. It'll download a file to your phone that you install as a module in magisk. That's how I did it; don't know if there's an easier way
Jiggs82 said:
You have the links for riru edxposed for Android R?
Click to expand...
Click to collapse

This worked for me for release Android 11.
It's pretty hit and miss on what Xposed modules work properly, but FingerFace works.
PSA, do not enable Xposed functionality for MaxLock by Maxr1998... you'll never get to your lockscreen until you somehow disable it.

neo_lithic3K said:
You'll need to install Edxposed manager first. Then Go to the third tab called Canary. Select the v0.5.0.6 for android r option and click install. It'll download a file to your phone that you install as a module in magisk. That's how I did it; don't know if there's an easier way
Click to expand...
Click to collapse
I updated to 11 via fastboot and factory images & magisk. You know, the usual process. But when I went to edxposed it said framework not active. Using latest canary magisk & canary edxposed v0506. I figured it wasn't working for 11 yet (I didn't try and of the 11 Betas) so I rolled back to the July update any help?

I tried Sandhook because I was experimenting... it never worked. Normally I use YAHFA hooking and it worked fine here.

This worked for me on both 11 beta 3 and 11 stable. After you downloaded canary edxposed v0.5.0.6., did you manually install it into magisk using "Install from storage?" Basically:
1) Open Magisk manager canary and go to the Modules page.
2) Click Search and look for: Riru - core. Install it once you find it. Don't reboot.
3) While you're still in Magisk Manager's Modules page, click on "Install from storage" at the top. Select and install the 0.5.0.6. file you downloaded from edxposed earlier.
4) Riru-Edxposed v0.5.0.6. android_r will appear as an installed module. (I installed the sandhook version.)
5) On the safe side, you should probably uninstall any unactivated xposed modules ... if you're able to. This way you're rebooting without any xposed modules installed. I've had a few times where the module wasn't compatible and I was bootlooped.
6) Reboot phone. and both magisk and edxposed should be active.
Suavie103 said:
I updated to 11 via fastboot and factory images & magisk. You know, the usual process. But when I went to edxposed it said framework not active. Using latest canary magisk & canary edxposed v0506. I figured it wasn't working for 11 yet (I didn't try and of the 11 Betas) so I rolled back to the July update any help?
Click to expand...
Click to collapse

neo_lithic3K said:
yes it does work. I'm on 11 beta 3 and fingerface works, but you have to install the prereleased Riru-edxposed for android R or else you'll bootloop when you install edxposed and reboot. That's what I experienced unless there's a fix I don't know about. However, you might not need xposed or fingerface anymore. I found that the 2 apps I needed fingerface for - Lastpass and Chase app - they've since updated so that you can use face authentication.
Click to expand...
Click to collapse
Thank you! For some reason I just saw this post had replies now ?
Just installed and it's working great ?

neo_lithic3K said:
This worked for me on both 11 beta 3 and 11 stable. After you downloaded canary edxposed v0.5.0.6., did you manually install it into magisk using "Install from storage?" Basically:
1) Open Magisk manager canary and go to the Modules page.
2) Click Search and look for: Riru - core. Install it once you find it. Don't reboot.
3) While you're still in Magisk Manager's Modules page, click on "Install from storage" at the top. Select and install the 0.5.0.6. file you downloaded from edxposed earlier.
4) Riru-Edxposed v0.5.0.6. android_r will appear as an installed module. (I installed the sandhook version.)
5) On the safe side, you should probably uninstall any unactivated xposed modules ... if you're able to. This way you're rebooting without any xposed modules installed. I've had a few times where the module wasn't compatible and I was bootlooped.
6) Reboot phone. and both magisk and edxposed should be active.
Click to expand...
Click to collapse
What edxposed mods do you use. I use gravity box. But I don't think it's supporting 11 yet.

Yeah, GravityBox for 11 hasn't been released yet. I use fingerface, AFwall+, and Root calll sms manager.
Suavie103 said:
What edxposed mods do you use. I use gravity box. But I don't think it's supporting 11 yet.
Click to expand...
Click to collapse

Any chance you have a link to the 5.0.6? i cannot seem to find it
EDIT: Figured it out
neo_lithic3K said:
This worked for me on both 11 beta 3 and 11 stable. After you downloaded canary edxposed v0.5.0.6., did you manually install it into magisk using "Install from storage?" Basically:
1) Open Magisk manager canary and go to the Modules page.
2) Click Search and look for: Riru - core. Install it once you find it. Don't reboot.
3) While you're still in Magisk Manager's Modules page, click on "Install from storage" at the top. Select and install the 0.5.0.6. file you downloaded from edxposed earlier.
4) Riru-Edxposed v0.5.0.6. android_r will appear as an installed module. (I installed the sandhook version.)
5) On the safe side, you should probably uninstall any unactivated xposed modules ... if you're able to. This way you're rebooting without any xposed modules installed. I've had a few times where the module wasn't compatible and I was bootlooped.
6) Reboot phone. and both magisk and edxposed should be active.
Click to expand...
Click to collapse

Just curious what everyone's safetynet status is after having edxposed active on 11? I have it with fingerface and I'm failing CTS profile and basic integrity. If I remove edxposed, I'm back to passing everything. I have the "Pass SafetyNet" option enabled in edxposed manager also.

1dopewrx05 said:
Just curious what everyone's safetynet status is after having edxposed active on 11? I have it with fingerface and I'm failing CTS profile and basic integrity. If I remove edxposed, I'm back to passing everything. I have the "Pass SafetyNet" option enabled in edxposed manager also.
Click to expand...
Click to collapse
I found a flashable magisk mod that allows my pixel 4 xl to pass safety net and cts profile. However my eval type comes back "BASIC" forgot what it means but I'll post the forum link where I found it as well.. Running Android 11, September security patch, stock root & also Gpay works. The mod gives me no issues, try it out. I'll post it in a drive link.
https://forum.xda-developers.com/ap...systemless-t3432382/post83028387#post83028387
https://drive.google.com/file/d/152l4_qIQ7VzSzUpFnNc3Eh61GV7Hgrj4/view?usp=drivesdk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Suavie103 said:
I found a flashable magisk mod that allows my pixel 4 xl to pass safety net and cts profile. However my eval type comes back "BASIC" forgot what it means but I'll post the forum link where I found it as well.. Running Android 11, September security patch, stock root & also Gpay works. The mod gives me no issues, try it out. I'll post it in a drive link.
https://forum.xda-developers.com/ap...systemless-t3432382/post83028387#post83028387
https://drive.google.com/file/d/152l4_qIQ7VzSzUpFnNc3Eh61GV7Hgrj4/view?usp=drivesdk
Click to expand...
Click to collapse
That's extremely strange for me, I use this module as well (have been even before trying edxposed) and as soon as I install the 2 edxposed modules to get xposed set up, I fail safetynet. With the hardware bypass module installed or not installed, I automatically fail safetynet when edxposed is installed on my phone.

I have Magisk (21.3), EdXposed (0.5.0.6), Fingerface (1.1.0) enabled, however I cannot see it working in an application whatsoever, everyone informs me that my device does not support fingerprint Android 11, November update ... Could someone tell me how to adjust?

Haylander Landim said:
I have Magisk (21.3), EdXposed (0.5.0.6), Fingerface (1.1.0) enabled, however I cannot see it working in an application whatsoever, everyone informs me that my device does not support fingerprint Android 11, November update ... Could someone tell me how to adjust?
Click to expand...
Click to collapse
I have the same problem, I think it is the November update :crying:

It's not the November update alone. Fingerface still can work with the coral-rp1a.201105.002 update.

Haylander Landim said:
I have Magisk (21.3), EdXposed (0.5.0.6), Fingerface (1.1.0) enabled, however I cannot see it working in an application whatsoever, everyone informs me that my device does not support fingerprint Android 11, November update ... Could someone tell me how to adjust?
Click to expand...
Click to collapse
Got it!
I removed EdXposed, Magisk and restored the boot.img.
That done:
Installed:
Magisk (Canary 21101)
** restarted the device
MagiskHide Props Config (Latest version)
Systemless Hosts (Latest version)
** restarted the device
Riru (Riru - Core) (21.2)
** restarted the device
Riru - EdXposed (0.5.0.6-android_r (4561) (YAHFA)
** restarted the device
HiddenCore Module (Latest version)
Fingerface (1.1.1)
In MagiskHide I selected, all the way around, Google apps, searching for "google" in the search field
In EdXposed I enabled App List Mode and Pass SafetyNet
At the moment Fingerface works perfectly and SafetyNet has passed!
Video