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
I have flashed MIUI Official Indonesian ROM on my Poco X3 Indian variant.
I unlocked the bootloader using MI unlock tool.
Flashed Indonesian ROM and relocked the bootloader through Fastboot using MI Flash Tool.
I have neither rooted my device even once nor used magisk.
Currently, the bootloader is locked and phone is unrooted but the SafetyNet test fails because of CTS Profile: False issue.
Can someone please help me to fix this?
You can just flash magisk and use safteynet fix module.
You may need to use magisk hide props module along with it.
Guys I managed to pass on Safetynet with Redmi 6 (cereus) Miui11.0.5.0 and ANDroid 9 Pie.
I did several tests and after months of research and errors (among them hard brick, boot loop, etc...) I finally managed to pass Safetynet de boa with a well structured configuration and now I can use the bank apps and Netflix de Boa. Follow the tutorial:
1st Stage
1_Always leave the option "usb debugging" enabled and checked in the developer settings.
------------------------------------------------- ------------------------------------------------- ------------------------------------------------- ---------------
2nd Stage
Install Magisk modules:
2_Busybox For Android NDK
3_Magisk Hide Props Config
4_Riru
------------------------------------------------- ------------------------------------------------- ------------------------------------------------- ---------------
3rd Stage
5_Install the terminal emulator app, open it and type "su" without quotes and hit enter.
6_Confirm the terminal root access request.
7_Type in the terminal "props" without quotes and press Enter.
8_Type in the terminal the number "1" without quotes and press Enter.
9_Type the letter "f" without quotes and press Enter.
10_Type the number corresponding to the brand of your device in the list and press Enter.
11_Type the number corresponding to your device model in the list and press Enter.
12_Type the letter "y" to confirm and press Enter.
13_Type the letter "y" again to confirm and press Enter.
14_Wait for the device to restart automatically.
------------------------------------------------- ------------------------------------------------- ------------------------------------------------- ---------------
4th Stage
15_Go to Google Chrome in your browser and search for "Universal Safetynet Fix 2.0.0 by kdrag0n GitHub" and download it, link here.
------------------------------------------------- ------------------------------------------------- ------------------------------------------------- ---------------
5th Stage
16_Open
the Magisk app and install the module "Universal Safetynet Fix_v.2.2.0" à
from the storage and choose the folder where you saved it (Usually
will be in the Downloads folder). Wait for the device to restart.
------------------------------------------------- ------------------------------------------------- ------------------------------------------------- ---------------
6th Stage
17_Now activate Magisk Hide in the Magisk app configuration
------------------------------------------------- ------------------------------------------------- ------------------------------------------------- ---------------
7th Stage
18_Hide the app and change the app name in the Magisk app settings
------------------------------------------------- ------------------------------------------------- ------------------------------------------------- ---------------
8th Stage
19_Now access the "Magisk Hide" module and hide all apps that don't need root including Google apps and some system apps (be careful if you don't know which ones only check "Google Services Structure" in system apps) os other that don't need root check everything don't forget to always check the new installed apps and be careful not to check the ones that need root.
------------------------------------------------- ------------------------------------------------- ------------------------------------------------- ---------------
9th Stage
20_Clean up the data from the "Google Play Store", "Google Play Services" and "Google Services Structure" apps.
------------------------------------------------- ------------------------------------------------- ------------------------------------------------- ---------------
10th Stage
21_Restart the device and check the Safetynet certificate.
If everything works out, it will be blue then it's just joy...
------------------------------------------------- ------------------------------------------------- ------------------------------------------------- ---------------
Note: This method has been successfully tested on Xiaomi Redmi 6 (Cereus) with MIUI 11.0.5.0 Andoid 9 Pie.
It should also work on Redmi 6A (Cactus).
It should also work on other devices in general but without warranty...
Do everything carefully and don't skip any of the steps above as they are all important, if you skip any of them it could result in a hard brick or boot loop on your device.
I am not responsible for damage caused to your device, do everything at your own risk and expense!
If copying this method to your Channel, Website or Blog please Indicate credits for GbyPass Droid from XDA Developers.
Hope I have helped once again! Big hug to everyone!
NerdSir said:
I have flashed MIUI Official Indonesian ROM on my Poco X3 Indian variant.
I unlocked the bootloader using MI unlock tool.
Flashed Indonesian ROM and relocked the bootloader through Fastboot using MI Flash Tool.
I have neither rooted my device even once nor used magisk.
Currently, the bootloader is locked and phone is unrooted but the SafetyNet test fails because of CTS Profile: False issue.
Can someone please help me to fix this?
Click to expand...
Click to collapse
I have the same problem with RN10s with Indonesia miui, you find the solution? I don,t want root
I have the same issue in my poco x3 pro. Anyone found solution without root. i dnt want't to root my device. Can some one help?
Same here,,any solution
I decided to create a module sharing thread here.
If Magisk is enabled, all modules will continue to work after the OTA update. (use "Install to Inactive Slot" method)
If Magisk is disabled, the module also loses its effectiveness.
Add official translations from Global ROMSince MIUI China ROM doesn't have translations other than English or China-related languages, I created Magisk module to add more languages.
I extracted official translations from MIUI Global ROM.
If there's no official translations, it will be showed in English (like search bar and some options only for China ROM).
This module also enables Google Location History & Nearby Share.
[MAGISK] Add languages to MIUI CN - Enables Google Location History & Nearby Share
I want to use the original MIUI Chinese version as it is, so I created a Magisk module to add the languages! The translation is extracted from MIUI Global ROM for Xiaomi 11T Pro. This module also enables Google Location History & Nearby Share...
forum.xda-developers.com
Global ROM Flag Patch
This Magisk module changes ROM flag to Global.
You can't change region, but some settings and VoLTE icons will become Global version.
Please note Global version has less features than China version, so you can't see some settings like enhanced keyboard.
This module doesn't contain translations and patch for Android Auto or location history.
You can install both translation patch and flag patch.
Please note this module can cause bootloops!
Releases · AndroPlus-org/magisk-module-miui-cn2global-lite
Change MIUI China ROM flag to Global. Contribute to AndroPlus-org/magisk-module-miui-cn2global-lite development by creating an account on GitHub.
github.com
--- If you want to use flag patch with MIUI optimization turned off (optional) ---
Please note if you disabled MIUI optimization, you'll get duplicate Package Installer (MIUI and AOSP) and it will cause bootloop.
Please don't disable MIUI optimization before installing this module, and disable one of the Package Installer to prevent bootloop.
So for installing flag patch module, you need to do:
1. Install above translation patch and reboot
2. Enable MIUI optimization and reboot
3. Install lite module and reboot
4. Disable MIUI optimization
5. Two "Package Installer" app will be available so disable one of them (I recommend non-Xiaomi logo one)
6. Reboot
-------------
If bootloop happens, run this:
adb wait-for-device shell su -c "touch /data/adb/modules/xiaomi-miui-conv-lite/disable;reboot"
Enable Android Auto
Here's the guide for enabling Android Auto.
You have to uninstall Android Auto first, then install Magisk module, and set permissions in AOSP settings (use "MIUI Hidden Settings" or something)
How to enable Android Auto on Xiaomi MIUI Chinese ROM [Magisk] - AndroPlus
I created a Magisk module that solves the problem of not being able to use Android Auto with MIUI Chinese ROMs, etc. Need Android Auto app in /system
androplus.org
Enable Google Assistant and hide dialog of Google Photo
You can activate Google Assistant with this Magisk module.
It also systemize Google Photo app so that you don't need to press Allow when you edit photos/videos.
Releases · AndroPlus-org/magisk-module-assistant
Contribute to AndroPlus-org/magisk-module-assistant development by creating an account on GitHub.
github.com
If my modules are helpful, I appreciate your donation.
Donate via PayPal
Donate via GitHub Sponsors
what do we need to do to get OK GOOGLE working after we install the module? I installed the module, now can activate assistant and trained the voice assistant on the phone. it still does not respond to ok google if you say it though on my phone with the screen on or off.
I have battery restrictions on google and assistant turned off.
also, I think the links to the first two modules point to the same place above? I can't find the correct link for the first module
Thank you for creating the Google Assistant module. Prior to installing the module with Magisk I had installed Google Assistant, but I could only activate voice commands by tapping on its icon. Now that I have installed the module, when I say "Hey Google" or "OK Google" the green microphone icon appears at the top left of my status bar, so I know Google Assistant is 'listening', but when I give it voice commands it doesn't respond. If I tap on the icon and then speak it obeys voice commands, but I could do that before the module. I am rooted with Magisk and have only installed the universal saftey net module, your (full, not the lite CN - Global) module, and your Google Assistant module. I have given the Google app and the Google Assistant app all permissions and unrestricted battery, and have set Google Assistant as the Mix Fold 2's default digital assistant. Am I missing some steps to get Google Assistant to respond to my voice? (I have MIUI optiminzations turned off)
@knives of ice @frcraig
It looks like "magisk-module-miui-cn2global-lite" is needed to make it work as MIUI China has Xiaomi's assistant (I was checking assistant with lite module).
For the OK google in lock screen, it seems we need more work...
The assistant seems to hear the command but does not appear in the foreground.
knives of ice said:
I think the links to the first two modules point to the same place above? I can't find the correct link for the first module
Click to expand...
Click to collapse
These two modules take different approaches to convert the China ROM into a Global ROM.
"-lite" one changes ROM's functionality to global.
Releases · AndroPlus-org/magisk-module-miui-cn2global
A Magisk module to add languages to Chinese version of MIUI. - AndroPlus-org/magisk-module-miui-cn2global
github.com
Releases · AndroPlus-org/magisk-module-miui-cn2global-lite
Change MIUI China ROM flag to Global. Contribute to AndroPlus-org/magisk-module-miui-cn2global-lite development by creating an account on GitHub.
github.com
@AndroPlus, thanks so much. I hope you can figure out how to get ok google working. almost there it seems. also, any chance we can get google smart lock working?
also, this is what confuses me on the 2 magisk modules you link
1.
magisk-module-miui-cn2global.zip
70 MB
2. "Lite"
magisk-module-miui-cn2global.zip
4.71 KB
Aug 15, 2022
when you download them they both have the same filenames as you can see above and when installed they appear as the same module in the magisk modules listing of installed modules. shouldn't there be 2 separate modules appearing when installed?
@knives of ice
hmm, something went wrong since I set different ID for the modules...
I reuploaded lite module with different file name:
Release v01 · AndroPlus-org/magisk-module-miui-cn2global-lite
Change MIUI China ROM flag to Global. Contribute to AndroPlus-org/magisk-module-miui-cn2global-lite development by creating an account on GitHub.
github.com
For the smart lock, you can enable it in "Trust agents" option and use "Activity Launcher" app to find and open smart lock options.
AndroPlus said:
@knives of ice
hmm, something went wrong since I set different ID for the modules...
I reuploaded lite module with different file name:
Release v01 · AndroPlus-org/magisk-module-miui-cn2global-lite
Change MIUI China ROM flag to Global. Contribute to AndroPlus-org/magisk-module-miui-cn2global-lite development by creating an account on GitHub.
github.com
For the smart lock, you can enable it in "Trust agents" option and use "Activity Launcher" app to find and open smart lock options.
Click to expand...
Click to collapse
yep, that fixed it. thanks so much got them all now
AndroPlus said:
@knives of ice @frcraig
It looks like "magisk-module-miui-cn2global-lite" is needed to make it work as MIUI China has Xiaomi's assistant (I was checking assistant with lite module).
For the OK google in lock screen, it seems we need more work...
The assistant seems to hear the command but does not appear in the foreground.
These two modules take different approaches to convert the China ROM into a Global ROM.
"-lite" one changes ROM's functionality to global.
Releases · AndroPlus-org/magisk-module-miui-cn2global
A Magisk module to add languages to Chinese version of MIUI. - AndroPlus-org/magisk-module-miui-cn2global
github.com
Releases · AndroPlus-org/magisk-module-miui-cn2global-lite
Change MIUI China ROM flag to Global. Contribute to AndroPlus-org/magisk-module-miui-cn2global-lite development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
So I went into Magisk manager and removed the full version module and installed the lite.zip, but when it prompted me to reboot I'm now stuck at the mi screen and my phone won't boot up.
frcraig said:
So I went into Magisk manager and removed the full version module and installed the lite.zip, but when it prompted me to reboot I'm now stuck at the mi screen and my phone won't boot up.
Click to expand...
Click to collapse
You can enable both full and lite module.
As I wrote in OP, duplicated Package Manager causes bootloop when you use lite module and MIUI optimization off.
You can enter into safe mode by pressing volume down key to disable all modules, or
adb wait-for-device shell su -c "touch /data/adb/modules/xiaomi-miui-conv-lite/disable"
to disable lite module.
So for installing lite module, you need to do:
1. Enable MIUI optimization and reboot
2. Install lite module and reboot
3. Disable MIUI optimization
4. Two "Package Manager" app will be available so disable one of them (I recommend non-Xiaomi logo one)
5. Reboot
I can boot to fastboot, but can't use adb commands because Windows no longer sees my device. Can you explain how to enter safe mode to disable all modules?
frcraig said:
I can boot to fastboot, but can't use adb commands because Windows no longer sees my device. Can you explain how to enter safe mode to disable all modules?
Click to expand...
Click to collapse
Boot it and when you see mi logo, press and hold volume down key.
OK, I tried that - now it is just stuck on the mi logo
frcraig said:
OK, I tried that - now it is just stuck on the mi logo
Click to expand...
Click to collapse
I think you couldn't enter into safe mode, maybe you have to try changing the timing of pressing.
You can try booting into recovery and press safe mode option too.
Full Guide for Xiaomi/Redmi Recovery Mode
You might have many questions about Xiaomi recovery mode, this blog will help show you how to enter and exit recovery mode in Mi phone. Plus, tips come with it.
itoolab.com
It won't boot into recovery mode (power + volume up).
frcraig said:
It won't boot into recovery mode (power + volume up).
Click to expand...
Click to collapse
Did you do it in unfolded state and right after you force-shutdown (not in mi logo screen)?
It's strange...
So I tried it in unfolded state and was able to get to the recover screen. However when I click "safe mode" the phone reboots to the mi logo and the bootloop continues. I must have done something wrong in replacing the full CN-Global module with the Lite version. Within Magisk manager I had "removed" the full version module, and it then had a rid line through it in the manager. I then installed and enabled the lite version at which time it prompted me to reboot. Perhpas next time I will reboot after revoving the full version and before I flash the light version.
End result is the same- I'm stuck in a bootloop.
frcraig said:
So I tried it in unfolded state and was able to get to the recover screen. However when I click "safe mode" the phone reboots to the mi logo and the bootloop continues. I must have done something wrong in replacing the full CN-Global module with the Lite version. Within Magisk manager I had "removed" the full version module, and it then had a rid line through it in the manager. I then installed and enabled the lite version at which time it prompted me to reboot. Perhpas next time I will reboot after revoving the full version and before I flash the light version.
End result is the same- I'm stuck in a bootloop.
Click to expand...
Click to collapse
been there, hope I never have to go back. at least you got to recovery with the folded screen. I don't know why your device isn't recognized in fastboot though. It would be horrible to have to wipe data but you might have to.
I let the battery drain completely (same effect as removing battery in older phones) and then plugged my phone in and immediately pressed power on plus volume up and was able to enter recovery mode. I had to wipe everything, but at least I'm still unlocked and rooted with magisk.
AndroPlus said:
@knives of ice
hmm, something went wrong since I set different ID for the modules...
I reuploaded lite module with different file name:
Release v01 · AndroPlus-org/magisk-module-miui-cn2global-lite
Change MIUI China ROM flag to Global. Contribute to AndroPlus-org/magisk-module-miui-cn2global-lite development by creating an account on GitHub.
github.com
For the smart lock, you can enable it in "Trust agents" option and use "Activity Launcher" app to find and open smart lock options.
Click to expand...
Click to collapse
Thank you for renaming the 'lite' module. Having the full version and lite version use the same file name was confusing. When you have time would you be able to update the translation in the lite version to match that of the full version (MIUI 13.1), because several of the settings options that are needed on the Mix Fold 2 don't appear.
frcraig said:
I let the battery drain completely (same effect as removing battery in older phones) and then plugged my phone in and immediately pressed power on plus volume up and was able to enter recovery mode. I had to wipe everything, but at least I'm still unlocked and rooted with magisk.
Click to expand...
Click to collapse
sucks to have to wipe data, but sometimes there is no choice. I still think it is insane that recovery only works in unfolded state. I can't believe i learned that an hour after paying $40 to get my phone to book with edl method cause I couldn't get into recovery but never tried it unfolded.