Database Info

[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

Root Call SMS Manager

The program allows to block undesirable incoming and outgoing calls and SMS. There is a support Dual SIM phones. The rights of root are necessary for full functioning.
Blocking is carried out at system level, the program doesn't miss the first call, the screen isn't lit and there is no window of a dialer.
Features:
- Blocking incoming SMS and MMS on Android 4.4 above without appointment as its program for SMS processing.
- Blocking of outgoing calls and SMS.
- Support the Dual SIM phones with opportunity to set various parameters of blocking for everyone
SIM.
- Private conversation. Possibility of replacing the incoming call number.
Screenshots:
{
"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"
}
To use the program on Android 7.x with the latest versions of SuperSU, you need to put file radio.sh https://goo.gl/BhjW3J to folder /su/su.d, set permission to read and execute and restart the phone.
When using MagiskSU before Oreo, use Magisk-module magisk-radiofix-script https://goo.gl/e7usCV or you can to put the file radio_magisksu.sh https://goo.gl/jsTSvQ to /magisk/.core/service.d(/sbin/.core/img/.core/service.d for Magisk 16.3+) folder, set permission to read and execute and restart the phone.
You do not need any magisk module and the radio.sh file for Android 8+.
If you have any ideas, suggestions or you found a bug/mistake, let me know.
Email: [email protected]
Downloads:
Google Play https://play.google.com/store/apps/details?id=com.mdnsoft.callsmsmanager
Google did not allow to use permissions for SMS and CallLog in version of the program from Google Play.
You can download the full version or RCSMModule for the version from Google Play.
Full version
1.23 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.23.apk
-Fixes for Android 12
-Improvements and fixes
1.22 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.22.apk
1.21 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.21.apk
1.20 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.20.apk
1.19 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.19.apk
1.18 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.18.apk
1.17.2 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.17.2.apk
1.17.1 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.17.1.apk
1.17 https://www.mdnsoft.ru/Files/RootCallSMSManager/CallSMSManager1.17.apk
RCSMModule for version from Google Play https://www.mdnsoft.ru/Files/RootCallSMSManager/RCSMModule1.0.apk

No issues with 8.1.0 a root call\sms blocker that works well,
thanks mdn80.

This program works great. I did support Root call Blocker and Private space but neither support Magisk and I don't think the developer has any interest in so. Root Call Manager is the perfect replacement for both and works great with Magisk on my Mi Note 2 with the new Global Rom 9. Just needs a good online English manual to describe all of the settings.

Hello
I have a rooted galaxy s9 but i dont have the option To bo answer method block

I dont understand why the app works only the first time I receive call. Reject method (blacklist) for calls.
I have to delete app datas and reconfigure it each time...
App use with xposed and magisk modules, lineageOs 14.1
Thanks
Envoyé de mon GT-I9506 en utilisant Tapatalk

I Could not get it to work on Lineage 15.1 z00t,
tried with latest SU (2.82) and Radio.sh the same way which worked perfectly on same devices with 14.1 lineage ,
then Tried as Beta Tester, and later with latest Xposed Framework installed on device.
under About "Xposed" is mentioned in red, am i missing a module or any install process?
i've noticed that if i changed Reject on blacklist to anything else such as "kill" or "mute" the call is answered automatically upon receiving it.
also missing the functionality for restarting and disabling service which was great with earlier version.
Great APP- the only one that works on Qualcomm dual sim, hopeful i'll get it to work on Lineage 15.1 so i can permanently update to Oreo.

jeepcook said:
I dont understand why the app works only the first time I receive call. Reject method (blacklist) for calls.
I have to delete app datas and reconfigure it each time...
App use with xposed and magisk modules, lineageOs 14.1
Thanks
Envoyé de mon GT-I9506 en utilisant Tapatalk
Click to expand...
Click to collapse
You added program to energy saving exceptions? Write please to [email protected] if you have any problems with program, I need logs.

z00tme said:
I Could not get it to work on Lineage 15.1 z00t,
tried with latest SU (2.82) and Radio.sh the same way which worked perfectly on same devices with 14.1 lineage ,
then Tried as Beta Tester, and later with latest Xposed Framework installed on device.
under About "Xposed" is mentioned in red, am i missing a module or any install process?
i've noticed that if i changed Reject on blacklist to anything else such as "kill" or "mute" the call is answered automatically upon receiving it.
also missing the functionality for restarting and disabling service which was great with earlier version.
Great APP- the only one that works on Qualcomm dual sim, hopeful i'll get it to work on Lineage 15.1 so i can permanently update to Oreo.
Click to expand...
Click to collapse
You need Xposed for full work app with Oreo. You must enable program module in Xposed Installer.
Write please to [email protected] if you have any problems with program or questions.

RBJ26 said:
No issues with 8.1.0 a root call\sms blocker that works well,
thanks mdn80.
Click to expand...
Click to collapse
how did you get it to work, mine is not working on Oreo 8.1

zaffar.mughal said:
how did you get it to work, mine is not working on Oreo 8.1
Click to expand...
Click to collapse
You need Xposed for full work app with Oreo.
Write please to [email protected] if you have any problems with program or questions, I need logs.

mdn80 said:
You need Xposed for full work app with Oreo.
Write please to [email protected] if you have any problems with program or questions, I need logs.
Click to expand...
Click to collapse
Yeah, this is pretty broken on 8.1 (Google Pixel). Xposed is activated and green text.

YandereSan said:
Yeah, this is pretty broken on 8.1 (Google Pixel). Xposed is activated and green text.
Click to expand...
Click to collapse
Also try to put daw "Process Voip calls" in program settings.

So to have it work with Oreo 8.1 (with Magisk), you need to install Xposed systemless. Do you need any additiaonl Xposed modules? Do you also have to install the Magisk module that's mentioned for Android 7 (magisk-radiofix-script_v1)?

solara1973 said:
So to have it work with Oreo 8.1 (with Magisk), you need to install Xposed systemless. Do you need any additiaonl Xposed modules? Do you also have to install the Magisk module that's mentioned for Android 7 (magisk-radiofix-script_v1)?
Click to expand...
Click to collapse
You do not need any additiaonl Xposed modules, Xposed module is built into the program. You do not need to install any Magisk modules for Oreo.

mdn80 said:
You do not need any additiaonl Xposed modules, Xposed module is built into the program. You do not need to install any Magisk modules for Oreo.
Click to expand...
Click to collapse
So you mean we just check the 'Xposed' checkbox under System settings for the app? That's it? I think you meant I do not need any additional Xposed module, but I still need to install Xposed via its installer or through the Magisk Xposed module (I am using Magisk), right?

solara1973 said:
but I still need to install Xposed via its installer or through the Magisk Xposed module (I am using Magisk), right?
Click to expand...
Click to collapse
Yes, you need to install Xposed and activate program Xposed module in Xposed Installer.

mdn80 said:
Yes, you need to install Xposed and activate program Xposed module in Xposed Installer.
Click to expand...
Click to collapse
Well tried to install systemless Xposed from within Magisk but got bootloop. I probably didn't do it right. Formatted my data and reloaded all my app. Side note: Remove phone password before rebooting after installing anything that might cause bootloops! TWRP can't decrypt if you use a Pattern. So I couldn't disable Xposed easily since I couldn't ADB or manually create that Disable file. I also couldn't get it to disable itself by pushing buttons during the boot process.
Turns out Root Call SMS works fine as it was! Oreo 8.1 rooted with Magisk with latest security updates through May on Moto x4. No other modules installed, no Xposed installed and is unchecked in settings. I tested calling and texting via online websites and it blocks them fine. I set it so I get no notifications but it does show up logged in the Journal.

solara1973 said:
I set it so I get no notifications but it does show up logged in the Journal.
Click to expand...
Click to collapse
You can set deleting calls from system journal in program settings.

solara1973 said:
So to have it work with Oreo 8.1 (with Magisk), you need to install Xposed systemless.
Click to expand...
Click to collapse
Really? So Magisk + Xposed via TWRP on Oreo 8.1 doesn't work? It has to be Systemless Xposed? @mdn80
I guess it might be worth a shot, because right now Root Call SMS Manager is behaving like it doesn't register Xposed at all, even though it's clearly working with my other modules.

YandereSan said:
Really? So Magisk + Xposed via TWRP on Oreo 8.1 doesn't work? It has to be Systemless Xposed? @mdn80
I guess it might be worth a shot, because right now Root Call SMS Manager is behaving like it doesn't register Xposed at all, even though it's clearly working with my other modules.
Click to expand...
Click to collapse
Write please to [email protected] if you have any questions or problems with program.

[Guide] EdXposed - Xposed Framework for Android 9 & 10

||| Why this guide? |||
Since the "EdXposed" project doesn't reveice the attention it should get in our device section, I decided to make a quick guide for you how to get a Xposed Framework on your OnePlus 6 running Android 9 and 10! :highfive:
I'm not the developer of EdXposed or Riru, nor in any way related to them. Just an ordinary user, who can confirm that it's working on the latest stock OOS 9.x-x with Magisk >18.1 and OOS 10 with a custom Magisk build (20), though not all available Xposed modules work. The list of known working and non-working apps can be found here (spoiler alert: Greenify (beta) and Xprivacylua (beta) are fully working :good - better check that thread before you complain afterwards
If you're asking yourself now, what EdXposed actually is, here's the description of the developer solohsu:
EdXposed: A Riru module trying to provide a ART hooking framework (initially for Android Pie) which delivers consistent APIs with the OG Xposed, leveraging YAHFA hooking framework.
Click to expand...
Click to collapse
But what is Riru?
Riru is a very simple but useful thing. Only requires to replace one system file, it will provide the ability to Riru modules to run their code in apps' or system server's process.
Click to expand...
Click to collapse
Got it? :fingers-crossed:
||| Notes |||
EdXposed is still in beta stage. Not all modules work and some bugs might occur, so please, make backups! At least take a full nandroid backup and save your important data (photos, documents, etc.) from your internal memory in a safe place.
Even though you don't need TWRP for the installation and usage of EdXposed, I'd highly recommend to have it in place for two reasons: 1. To take backups and 2. To be able to flash the EdXposed Uninstaller zip in case something went wrong.
On Android 10, SafetyNet does not pass! I'll update this thread as soon as a fix is available! Also, if you upgrade from 9 to 10, make sure to deactivate or uninstall all Magisk and Xposed modules. Some of them might not be support Android 10 right now, activate them one by one (with reboot), after the whole upgrade process is done. For example: "Audio Modification Library" and/or "Audio Compatibility Patch" *work", but make recording of Whatsapp voice messages fail. Be aware that those issues might occur until all modules are updated to support Android 10.
||| Requirements |||
Android 9:
rooted with Magisk >18.x
optional: TWRP (blu_spark TWRP >3.2.3+ highly recommended)
Android 10:
rooted with custom Magisk 20 by soloshu
unlike on pie, TWRP for Android 10 is needed (blu_spark >=v9.107 recommended)
||| Installation |||
Android 9:
It's quite simple, just follow those steps:
(I flashed everything in magisk, since EdXposed and Riru Core are technically magisk modules)
Download the files mentioned in the downloads for Android 9 section on your phone
Have you done your backup(s)? If not, do it now -just in case!
Flash the (latest) Riru Core zip in Magisk or TWRP (magisk-riru-core-vXX.X.zip)
Flash the (latest) EdXposed zip in Magisk or TWRP (magisk-EdXposed-vX.X.X.X_beta-release.zip; YAHFA highly recommended!)
reboot
Install the EdXposed Installer (EdXposedInstaller_vX.X.X-release.apk)
Done!
Open up the EdXposed Installer and check if the Xposed Framework status is active and "green".
Android 10:
If you had EdXposed on your device on Android 9 and now just want to upgrade to 10, you don't have to install Riru Core and EdXposed Manager if the latest versions were already installed.
Download the files mentioned in the downloads for Android 10 section on your phone
Have you done your backup(s)? If not, do it now -just in case!
reboot to TWRP (blu_spark >=v9.107)
Flash the (latest) custom Magisk build by soloshu in TWRP (>= v20.0(20001); Magisk-v20.x.zip)
reboot
Flash the (latest) Riru Core zip in Magisk or TWRP (>= 19.5; magisk-riru-core-vXX.X.zip)
Flash the (latest) EdXposed zip in Magisk or TWRP (>= v0.4.6.0_beta; magisk-EdXposed-vX.X.X.X_beta-release.zip, YAHFA highly recommended!)
reboot
Open Magisk Manager, go to settings->update channel and paste the this custom path: "https://raw.githubusercontent.com/solohsu/magisk_files/master/custom_builds/release.json"
Install the EdXposed Installer (EdXposedInstaller_vX.X.X-release.apk)
Done!
||| Downloads |||
Android 9:
Riru
EdXposed Installer, Uninstaller and flashable zip
(at the date of publishing this thread, the latest Riru version is v17.1, EdXposed is v0.3.1.2_beta)
Android 10:
Riru
EdXposed Installer, flashable zip
Custom Magisk Build
TWRP blu_spark v9.107
||| Source code / Github links |||
EdXposed
Riru
||| Screenshots |||
{
"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"
}
||| Thanks & Credits |||
@rovo89 - who made all this possible with his Xposed Framework
@topjohnwu - for his awesome Magisk root environment
@solohsu[Github] - for his EdXposed and customized Magisk builds
@Rikka apps[Github] - for their Riru Core
@eng.stk - for his blu_spark TWRP and awesome kernels
@Uraniam9 - for his list of working modules

reserved

Does it pass Safetynet unlike the previous Xposed Magisk modules?
Sent from my OnePlus 6 using XDA Labs

kunalgupta1 said:
Does it pass Safetynet unlike the previous Xposed Magisk modules?
Click to expand...
Click to collapse
Yes
Sent from my OnePlus 6 using XDA Labs

Have xposed on pie since last week and running well.
App running is gravitybox 9.0 beta 2
And no problems with safetynet.

Very interesting indeed. Thanks man! Gonna check it out over the weekend.

No problem on oos 9.04

How are some of the root sensitive apps working, like Android Pay? Will we be able to update some sensitive apps like Netflix and Mario Run in the Play Store?
I just came from the Axon 7 where it was either Xposed or passing SafelyNet, but not both. I'm gonna look into this for sure! Thanks!

HallOfPromise said:
How are some of the root sensitive apps working, like Android Pay? Will we be able to update some sensitive apps like Netflix and Mario Run in the Play Store?
I just came from the Axon 7 where it was either Xposed or passing SafelyNet, but not both. I'm gonna look into this for sure! Thanks!
Click to expand...
Click to collapse
Take a look at the screenshots I posted. SafetyNet passes! And even better, you can "blacklist" specific apps, which means that they're not touched/hooked in any way. Very useful for banking apps or sensitive apps like password-manager :good:
I'm quite sure that you can use Android Pay, though I can't tell for sure since I don't use it. The Xposed gets hardly detected because it "basically" isn't the "pure" XPosed, but a module of Riru. Simply spoken: Riru is a module of Magisk. And EdXposed is a module of Riru

Depressed T.Bear said:
Take a look at the screenshots I posted. SafetyNet passes! And even better, you can "blacklist" specific apps, which means that they're not touched/hooked in any way. Very useful for banking apps or sensitive apps like password-manager :good:
Click to expand...
Click to collapse
I totally missed the screenshots the first time around. Awesome! After I get my OTG extra storage and make a new backup (large backup) I'm gonna jump on this!
Do we have a thread for GravityBox P on our OnePlus 6 and all the things working and not working? I would start one but I'm working and technically shouldn't be doing this haha

HallOfPromise said:
I totally missed the screenshots the first time around. Awesome! After I get my OTG extra storage and make a new backup (large backup) I'm gonna jump on this!
Do we have a thread for GravityBox P on our OnePlus 6 and all the things working and not working? I would start one but I'm working and technically shouldn't be doing this haha
Click to expand...
Click to collapse
Don't worry I added them just recently
Not for our device specifically. In fact I made this guide here because most people didn't even know that there's a Xposed solution for Pie . But according to the thread I mentioned, it's reported to work. And since OxygenOS is quite close to vanilla Android, I'd assume it will work flawlessly
Sent from my OnePlus 6 using XDA Labs

sakerhetz said:
Have xposed on pie since last week and running well.
App running is gravitybox 9.0 beta 2
And no problems with safetynet.
Click to expand...
Click to collapse
In my case i am running amplify, greenify, ... without any problems. But gravitybox throws me startup error "framework not responding" and quits. Do you use an specific vetsion of gravitybox?
(Moderator Edit: reference to Warez removed - as per XDA's Forum Rules)

elmarian756 said:
In my case i am running amplify, greenify, ... without any problems. But gravitybox throws me startup error "framework not responding" and quits. Do you use an specific vetsion of gravitybox?
(Moderator Edit: reference to Warez removed - as per XDA's Forum Rules)
Click to expand...
Click to collapse
Did you enable the module gravitybox in xposed?
And which version of gravitybox do you use?

sakerhetz said:
Have xposed on pie since last week and running well.
App running is gravitybox 9.0 beta 2
And no problems with safetynet.
Click to expand...
Click to collapse
sakerhetz said:
Did you enable the module gravitybox in xposed?
And which version of gravitybox do you use?
Click to expand...
Click to collapse
Wiped dalvik cache and now it works like a charm! I am using version 9.0.0 beta 4

can i
i once flashed aosip 9.0 on my honor 5x(kiwi),and flashed edxposed 0.3.1.2,it works well.
but the rom lag,so i want flash back to 8.1,but failed.
when i reflash the aosip then flash edxposed,i got a "screenshot" --only one shot on screen,and the screen flash of status bar and back key in navibar for every 30seconds.
i tried 0.3.1.7 the same issue,
i tried edxposed uninstaller,it says not detect magisk, flash end with error 1
i don't want to give up this
what can i do

sakerhetz said:
Have xposed on pie since last week and running well.
App running is gravitybox 9.0 beta 2
And no problems with safetynet.
Click to expand...
Click to collapse
hello, Where can i find this module ?

rhabhab said:
hello, Where can i find this module ?
Click to expand...
Click to collapse
https://www.google.nl/amp/s/forum.x...vitybox-v9-0-0-beta-1-android-9-t3908768/amp/
---------- Post added at 09:42 AM ---------- Previous post was at 09:27 AM ----------
booykean said:
can i
i once flashed aosip 9.0 on my honor 5x(kiwi),and flashed edxposed 0.3.1.2,it works well.
but the rom lag,so i want flash back to 8.1,but failed.
when i reflash the aosip then flash edxposed,i got a "screenshot" --only one shot on screen,and the screen flash of status bar and back key in navibar for every 30seconds.
i tried 0.3.1.7 the same issue,
i tried edxposed uninstaller,it says not detect magisk, flash end with error 1
i don't want to give up this
what can i do
Click to expand...
Click to collapse
I assume that you flashed a custom ROM and that doesn't work well with gravitybox for pie.

i have no gravitybox installed
sakerhetz said:
https://www.google.nl/amp/s/forum.x...vitybox-v9-0-0-beta-1-android-9-t3908768/amp/
---------- Post added at 09:42 AM ---------- Previous post was at 09:27 AM ----------
I assume that you flashed a custom ROM and that doesn't work well with gravitybox for pie.
Click to expand...
Click to collapse

gravitybox is available for Android Pie, can someone please test with edxposed https://forum.xda-developers.com/xposed/modules/app-gravitybox-v9-0-0-beta-1-android-9-t3908768

JerryGoyal said:
gravitybox is available for Android Pie, can someone please test with edxposed https://forum.xda-developers.com/xposed/modules/app-gravitybox-v9-0-0-beta-1-android-9-t3908768
Click to expand...
Click to collapse
Been using for a few weeks, works great op6t.. so should be fine on op6, it's the same phone..

[Solved for now] Unable to install Edxposed

I just upgraded to Oxygen OS 10.0.1.GM57AA from 9.5.8 (if I remember rightly, from India ).
I tried the following with Magisk 19.3 and 20:
1. No other Magisk modules only Riru Core - no problems.
2. Install Riru latest Ed xposed YAHFA. Device didn't get booted. Booted into TWRP side loaded Magisk Manager, set to core only mode Magisk and rebooted into system and uninstall YAHFA.
3. Tried step 2 with latest Sandhook. Same result
4. Uninstalled all Magisk modules and From EdXposed manager installed Riru core. No problem. Installing YAHFA or Sandhook from Manager, same result - device doesn't boot and spinning dots continue
Has anybody got it working? I searched the forum and elsewhere but couldn't find anything related to our device.
Please explain how you did it
Edit 1
1. Flashing Riru Core and Riru YAHFA/ Sandhook from TWRP (this worked for One Plus 7 Pro) didn't help. Same story of stuck at boot animation.
2. Flashing YAHFA from GravityBox for 10 also had the same problem.
3.. Flashing Canary version of YAHFA (v0.4.5.5_beta(4470) worked and I am able to use Xposed modules ! I don't know how stable this would be but at least I have got the modules I need like XPrivacy Lua installed and working. I didn't try Sandhook because I always found YAHFA to be stabler though slower.
Edit2
Canary version above created drag and gravitybox had a lot of issues. Credit to @C3C076 who pointed out to use YAHFA modified from here https://forum.xda-developers.com/showpost.php?p=80392829&postcount=30 and use the installer 2.2.4 from here https://github.com/solohsu/XposedInstaller/releases/tag/Ed_v2.2.4.
ALL fine
Please update what method you used and which modules used to help others . Thanks

[GUIDE]Magisk, SuperSU and Xposed for MEmu 7.3.2 or LDPlayer 4.0.45

A new tool is available which can install Magisk in emulators. See Delta Magisk​
This tool is depreciated. No support will be provided.​
Magisk
Note:- This is a experimental feature. I made this guide only for SuperUser management in MEmu. If you want modules then don't expect it to work. Modules like MigiskHideProps are not working. So don't expect much.
As of now there is no working way for passing SafetyNet for playing games and apps that use it.​
For someone who want to install Magisk in emulators MEmu v7.3.2/LDPlayer v4.0.45 which is based on Android-x86, follow below guide.
What is this method?
-This method is used by exploits like mtk-su, qu1ckr00t without patching boot.img. I used this method because I don't know how to modify .vmdk as seen in here. Drawback of this method is that, many modules like MagiskHideProps are not working.
If you are using MEmu then follow https://forum.xda-developers.com/t/...-3-2-or-ldplayer-4-0-45.4222919/post-84574053
If you are using LDPlayer then follow https://forum.xda-developers.com/t/...-3-2-or-ldplayer-4-0-45.4222919/post-84580333
Reference:-
-https://forum.xda-developers.com/t/...diatek-armv8-2020-08-24.3922213/post-82081703
-https://github.com/grant-h/qu1ckr00t/blob/master/app/src/main/res/raw/magisk_install
Credits:-
@topjohnwu
@diplomatic
Enjoy!
SuperSU
If you want SuperSU instead of Magisk, then follow below guide
Enable Root mode
Download SuperSU zip from here
Download and install BusyBox from here
Download update-binary script from here. We can save this with CTRL + S if using browser in Windows OS
In Terminal Emulator run below commands
Code:
su
export PATH=/system/xbin:/system/bin
cd /sdcard/Download
sh update-binary 2 1 $PWD/SR5-SuperSU-v2.82-SR5-20171001224502.zip
Restart MEmu. Enjoy!
Credits:-
@Chainfire
Xposed
I have modified youling257's xposed at Github. Since it is not flashable zip by default, we have to do it our own. Made it x86_64 flashable zip like x86 one. Nothing is changed. Just added x86_64 files to x86 system folder after deleting its contents, changed `arch` to x64 and signed.
We can also install Xposed in MEmu/LDPlayer Android 7.1.2(25) by below
Download last version of Xposed from
x86 => https://dl-xda.xposed.info/framework/sdk25/x86/xposed-v89-sdk25-x86.zip
(Tip:- 32bit users can directly install Xposed from Xposed Installer app without this manual flashing)
x86_64 => https://forum.xda-developers.com/attachments/xposed-v89-sdk25-x86_64-signed-zip.5197651/
copy it to /data/local/tmp
extract only META-INF/com/google/android/update-binary from the zip to /data/local/tmp
Run below commands in Terminal Emulator app with root.
Code:
su
cd /data/local/tmp
chmod 777 update-binary
if your arch is x86, then run below one
Code:
NO_UIPRINT=1 ./update-binary 2 1 xposed-v89-sdk25-x86.zip
rm update-binary xposed-v89-sdk25-x86.zip
if your arch is x86_64, then run below one
Code:
NO_UIPRINT=1 ./update-binary 2 1 xposed-v89-sdk25-x86_64-signed.zip
rm update-binary xposed-v89-sdk25-x86_64-signed.zip
Download Xposed apk from https://forum.xda-developers.com/attachments/xposedinstaller_3-1-5-apk.4393082/ and install it and restart.
Reference:-
XposedInstaller/app/src/main/java/de/robv/android/xposed/installer/installation/FlashDirectly.java at 8f8f2d7072d1f7b02f237e4ac864e767b7aa6e4c · rovo89/XposedInstaller
Contribute to rovo89/XposedInstaller development by creating an account on GitHub.
github.com
Credits:-
@rovo89
@youling257
@Camlin3 for initial thread.
Enjoy!

Deprecated Guide
Spoiler
Start MEmu/LDPlayer and enable Root mode in Settings
Download and install latest Magisk Manager from here
Download Magisk.zip from here and take magiskinit file from it according to your architecture and place it like /sdcard/init.d/bin/magiskinit.
Download the script from here. We can save this code with CTRL + S in Browser in Windows OS.
Install Terminal Emulator app and run below code in it
Code:
su
sh /sdcard/Download/magisk-boot.sh
Now, you have successfully installed Magisk.
You have to execute the script on every boot. We can use 'Termux:Boot' or 'init.d scripts support'(don't forget to turn off battery optimization for the app)

please, would it be possible for you to record a step by step video?

rickkarpov said:
please, would it be possible for you to record a step by step video?
Click to expand...
Click to collapse
I can't do that, because of my Internet issues to upload. You can message at Telegram with username 'HemanthJabalpuri', so that I can guide you.
Thanks

after running script, it says magiskinit not found. I followed all steps, please help.

Anubhav001 said:
after running script, it says magiskinit not found. I followed all steps, please help.
Click to expand...
Click to collapse
Ok, tell me if /storage/emulated/0 is there or not.
If it is there, then make sure that magiskinit in placed in /storage/emulated/0/init.d/bin
Thanks

Nice guide.
Thank you very much

This is cool magisk was installed and everything was fine... I expected it to be
But the Modules are the issue, can't make them to work..... any help??
I have installed the magisk hide module and its shown activated but can't bypass safteynet, is that because of the superuser within the emulator?

rushi12565 said:
This is cool magisk was installed and everything was fine... I expected it to be
But the Modules are the issue, can't make them to work..... any help??
I have installed the magisk hide module and its shown activated but can't bypass safteynet, is that because of the superuser within the emulator?
Click to expand...
Click to collapse
I have also tried that, but failed. But some modules like Busybox are working. But it does not work along with MagiskHideProps.
@VD171 suggested to use HiddenCore module from Xposed to pass SafetyNet. I didn't tested it. May or may not work. Give it a try.
Thanks

HemanthJabalpuri said:
I have also tried that, but failed. But some modules like Busybox are working. But it does not work along with MagiskHideProps.
@VD171 suggested to use HiddenCore module from Xposed to pass SafetyNet. I didn't tested it. May or may not work. Give it a try.
Thanks
Click to expand...
Click to collapse
I'm using HiddenCore-module with Android 6.0, Android 7.0, Android 8.1, Android 9.0 and Android 10.0.
It is working perfectly on all them.
MagiskHideProps has a FANTASTIC intention, but a poor execution.
It has conflicts inside itself.
Unhappy, I can't suggest it to anybody.
Certainly, HiddenCore-Module will work for you.
HiddenCore Module | Xposed Module Repository
repo.xposed.info

HemanthJabalpuri said:
I have also tried that, but failed. But some modules like Busybox are working. But it does not work along with MagiskHideProps.
@VD171 suggested to use HiddenCore module from Xposed to pass SafetyNet. I didn't tested it. May or may not work. Give it a try.
Thanks
Click to expand...
Click to collapse
Oh ok.
abt the exposed doesn't it just show that safetynet is passed and not actually fix the safetynet right?

rushi12565 said:
Oh ok.
abt the exposed doesn't it just show that safetynet is passed and not actually fix the safetynet right?
Click to expand...
Click to collapse
If the app see that safetynet is passed, what does matter if it is fixed or not?
If you've rooted your device, your safetynet will be broken forever, until you unroot it.
That's simple.
Just fake it and everything will works perfectly.

Umm i'll try then

rushi12565 said:
Umm ill's try then
Click to expand...
Click to collapse
Don't forget to share result after trying.

Yea so i was trying to see if by passing saftey net on emulator I could play pokemon go on it (was just curious) and i failed xposed doesn't help. it's shown that safetynet is passed but it isn't i guesss.

rushi12565 said:
Yea so i was trying to see if by passing saftey net on emulator I could play pokemon go on it (was just curious) and i failed xposed doesn't help. it's shown that safetynet is passed but it isn't i guesss.
Click to expand...
Click to collapse
Did you try to check safetynet on magisk app?
Can you try on others app too?
Are you sure xposed is properly working?
Are you sure hiddencore is activated in modules tab?
Try checking logs too

VD171 said:
Did you try to check safetynet on magisk app?
Can you try on others app too?
Are you sure xposed is properly working?
Are you sure hiddencore is activated in modules tab?
Try checking logs too
Click to expand...
Click to collapse
Yea i've checked that hidden core is activated in the modules tab
The safteynet test in magisk is passed but it couldn't pass the test from a normal safteynet test app
this one https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest&hl=en_IN&gl=US

rushi12565 said:
Yea i've checked that hidden core is activated in the modules tab
The safteynet test in magisk is passed but it couldn't pass the test from a normal safteynet test app
this one https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest&hl=en_IN&gl=US
Click to expand...
Click to collapse
Did you rename magisk app?
Did you enable magisk hide?
Did you select the desired app for hiding by magisk hide?
There are many steps for hiding root, magisk, xposed or anything on android.
You need to try everything you can.

VD171 said:
Did you rename magisk app?
Did you enable magisk hide?
Did you select the desired app for hiding by magisk hide?
There are many steps for hiding root, magisk, xposed or anything on android.
You need to try everything you can.
Click to expand...
Click to collapse
Hided magisk
Enabled magisk hide when I tried to hit the reboot the emulator just struck so I had to close and restart the emulator itself and when I checked the modules in magisk the magisk hide props was toggled(was shown working)
The thing is when I did this the safety net was not passed, xposed hidden core module was not activated. so now I will try and see if activating both hidden core module and magisk hide will help or not

Yea I have tried it and the results are the same
Safety net is shown passed in magisk but in the actual test it fails
Xposed and magisk modules are activated
(logs in the next msg)