Related
Hi all.
Is anyone using Viper4Android with SElinux enforcing mode?
I was able to make V4A run in SElinux enforcing but found out that doing so, breaks the microphone during a call.
Example:
1. Perform a call
2. Switch from handset to Speaker mode <- so far so good
3. Switch back to handset <- the other party can't hear you anymore.
4. Switch back to speaker mode <- the other party can hear you again
The way I made V4A work in SElinux enforcing is by adding these lines to the '50Viper.sh' file under the 'su.d' folder.
Code:
#! /system/bin/sh
/su/bin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { execute };"
supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
If you are running V4A in SElinux enforcing, do you encounter the issue I described?
gil80 said:
Hi all.
Is anyone using Viper4Android with SElinux enforcing mode?
I was able to make V4A run in SElinux enforcing but found out that doing so, breaks the microphone during a call.
Example:
1. Perform a call
2. Switch from handset to Speaker mode <- so far so good
3. Switch back to handset <- the other party can't hear you anymore.
4. Switch back to speaker mode <- the other party can hear you again
The way I made V4A work in SElinux enforcing is by adding these lines to the '50Viper.sh' file under the 'su.d' folder.
Code:
#! /system/bin/sh
/su/bin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { execute };"
supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
If you are running V4A in SElinux enforcing, do you encounter the issue I described?
Click to expand...
Click to collapse
I'm using V4A from this thread
http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
I'm using ViPERAudio 4.7.1 Stock.zip (COS13.1.2 + SuperSU) but you can use any of them in Enforcing mode. The only caveat is that it works in Enforcing mode only when you use SuperSU, if you use SuperUser such as in CM13 Nightlies you have to change SELinux to Permissive. There is no configuration required just SuperSU. Flash the zips and enjoy V4A but read info in that thread if you have any questions, have never had any issues so far
Renosh said:
I'm using V4A from this thread
http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
I'm using ViPERAudio 4.7.1 Stock.zip (COS13.1.2 + SuperSU) but you can use any of them in Enforcing mode. The only caveat is that it works in Enforcing mode only when you use SuperSU, if you use SuperUser such as in CM13 Nightlies you have to change SELinux to Permissive. There is no configuration required just SuperSU. Flash the zips and enjoy V4A but read info in that thread if you have any questions, have never had any issues so far
Click to expand...
Click to collapse
I know, I use SuperSU as well.
The OP of the thread you gave, has actually incorporated the code I've posted in my OP to his ZIP files.
See my post here: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137/post66027160#post66027160
After my post he used this to apply this fix on the rest of the V4A variants.
But I'm not taking credit for the fix. I found it elsewhere.
Have you tried to make a call and switch back and forward with speaker mode and handset?
Did you do any change to your mixer_path.xml or build.prop?
gil80 said:
I know, I use SuperSU as well.
The OP of the thread you gave, has actually incorporated the code I've posted in my OP to his ZIP files.
See my post here: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137/post66027160#post66027160
After my post he used this to apply this fix on the rest of the V4A variants.
But I'm not taking credit for the fix. I found it elsewhere.
Have you tried to make a call and switch back and forward with speaker mode and handset?
Did you do any change to your mixer_path.xml or build.prop?
Click to expand...
Click to collapse
Zero changes to the mixer_path.xml
Completely stock except for root, removing ModioFX from system and using a different hosts file (Adaway) and installing V4A.
I haven't had a single issue with calls via speaker phone or handset for the past couple of days on current ROM. I've used a similar set up for months in various ROMs and never noticed or received reports of issues either
can you please see if you can find your 50viper.sh file under system/su.d and post it?
Thanks!
I take no credit for this amazing equalizer. All credits go to @zhuhang and the people from his thread for the convolvers.
If you don't know what V4A is check here for more details.
But basically it's an audiophiles dream that can cause serious hearing loss and such audio enjoyment at the same time!
The Zip has all the files included to enable "neon" support for convolvers, which are also included.
The feedback I've received so far is 100% success.
INSTRUCTIONS:
1) DOWNLOAD THE ZIP
2) FLASH IN RECOVERY (no need to uninstall if you already have viper installed)
3) open the app and you will be prompted to install the drivers. (I always choose the top one, although it does consume more batter, we'll worth it)
The EQ can be either super simple with just the basic adjustments or can get really technical in "expert" mode.
To activate the convolvers hit the 3 dots in the top right and click click the "ui settings" and change it to expert
Current version Download and discussion starts here
UPDATE VERSION 2.4.0.1 Neon Enabled + Convolvers
If using my previous zip version a simple flash of the new zip will update your V4A.
If you are running any version other than the one in my previous zip you will need to follow the steps below to ensure a smooth update to 2.4.0.1.
1) uninstall current driver from Viper by selecting the option is the app or use file manager and delete "libv4a_fx_ics.so" from system/lib/soundfx.
2) wipe data app with application manager or TiBackup
3) uninstall your current V4A
4) Flash to new zip
5) boot up and enjoy
6) hit the thanks button.
old version
Viper4Android neon enabled including convolvers
Thanks to @SammyTRK for confirming it works for this device!
Enjoy!
With permissive enabled kernel, just install v4a as normal app, neon also enable.
Sent from my SM-N920P using XDA-Developers mobile app
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
If you are someone like me who encountered countless problems while installing Viper4Android on your Android 10 or 11 device and have no idea what to do then you are in the right place. Just download and install the apk from the attachment below.
You need to be rooted with magisk but you can still give it a try if you don't have magisk on your device.
Steps -
* Disable MusicFX or any other sound mod you are using either from Setting/App Manager/Apps or by installing Ainur Narsil magisk module
* Reboot
* Now remove Ainur Narsil magisk module from magisk and install Audio Modification Library (This is required in case you have leftovers from last sound mod)
* Reboot
* Now download the app from the attachment
* Install and open the apk. The app will ask you to install drivers. HIT OK
* The phone will automatically reboot and install Viper4Android magisk module
* Open the app and check. It should be working by now.
If it doesn't work -
* Install Audio Compatibility Patch magisk module. By now you will have two magisk module installed. (Audio Modification Library and Audio Compatibility Patch)
* Reboot
* Open the app. It should work now
* Still no? - Turn on legacy mode from app setting
* Still no? - Turn on compatibility mode from app setting
V4A should totally work by now
Edit : On one plus phones you need to change your seLinux mode to permissive first and then install viper4android.
Use seLinux Mode Changer for that.
Edit: All files are attached at the bottom of the post
Edit 2 -
If none of the above solution is working for you.
Download Viper4Andrpid app from here
Download latest Magisk 21.4 from here
- Flash magisk from recovery
- Then open the Viper4Andrpid app and it'll ask you to update the drivers (or won't, depending on if you already have the drivers installed)
- If phone reboots then open the app again and turn on legacy mode from options
- If phone doesn't reboot, go to options and turn on legacy mode
It should be working now
Edit 3-
If the above two methods don't work and you have enforcing SELinux, try this.
• Disable MusicFX
• Install magisk 22.1
• Install Ainur Narsil magisk module
• Reboot
• Go to magisk and remove Ainur Narsil magisk module
• Download Viper4Android 2.7.2.1 from here
• Open it. It will ask you to install drivers. Click Ok and the phone will reboot. Don't panic.
• Open Viper4Android. Turn on Legacy mode. You will see the Viper4Android app icon on your status bar.
• Go to magisk. Install Audio Modification Library magisk module.
• Reboot
• Go to magisk again and install Audio Compatibility Patch magisk and select the options mentioned below -
- Patch Audio Policy : Vol- (no)
- Patch method : Vol+ (new logic)
- Remove notification helper : Vol- (no)
- Patch USB policy for USB dacs? : Vol- (no)
- Use lib workaround: Vol- (no)
• Reboot
• Open your music player and play a song to check if Viper4Android works now
• If you have never used V4A before, just turn on Master Limiter and Speaker Optimization
If that fails too -
• Unistall Viper4Android app
• Remove Audio Compatibility patch
• Reboot
• Install Viper4Android app and open it
• Enable Legacy mode from top right
• Play a song from your Music Player and turn on Master Limiter in the Viper4Android app
• Now turn on speaker optimization
If Viper4Android doesn't process in the Youtube app or Spotify, install the Audio Compatibility patch like I mentioned above and reboot
Fix 6:
If none of the methods above works then it's likely you messed up somewhere in the process. Unistall all the modules and Viper4Android.
Download the SeLinuxMode Changer app and set your SELinux to permissive. (If you want that)
App link :
Release v11.0 · MrBIMC/SELinuxModeChanger
updated to the latest libs and tools implemented app shortcuts to quicktoggle between permissive and enforcing modes new icons and notification styles adaptive icons (including shortcuts) for 8.0+ ...
github.com
Reboot and go to the top of the post. Follow the very first method.
Fix 7: (May 11, 2022)
I have added Aosp Soundfx remover and V4a fx 2.7.2.1 in the attachment.
Flash Aosp Soundfx remover
Reboot
Turn on mobile data/wifi
Flash v4a fx 2721
Reboot
Open Viper4Android app and install the drivers (if the app is asking you to install)
Reboot
Edit : If you encounter distorted/buggy/laggy audio, clean install viper4android again. But this time keep Ainur Narsil and Audio Modification Library magisk module installed
In OnePlus devices or OxygenOS roms you might need to install the driver twice or thrice.
Credit -
Team De Witt and Viper Acoustic
I did not create the app. I just found a way to get it working in some complicated Android 10 - 12 roms
Thanks for reading and have a nice day!
Edit 69:
If the audio isn't loud enough, go to master limiter, drag that output gain slider to right(6db).
If it's still not loud enough, turn on playback game control, tap on it and customize gain and threshold to your liking.
For others,you can test Wavelet from Wit,its awesome app,same dev.
thank you very much it worked perfectly
Monkeysss01 said:
thank you very much it worked perfectly
Click to expand...
Click to collapse
Hit thanks if it helped
@ Ryan Cr 7
I've followed all of your steps but still no driver installation. (CR Droid, Oneplus 8 pro)
ichbinsauch said:
@ Ryan Cr 7
I've followed all of your steps but still no driver installation. (CR Droid, Oneplus 8 pro)
Click to expand...
Click to collapse
In one plus phones you need to change your seLinux mode to permissive first and then install viper4android.
RyanCr7 said:
In one plus phones you need to change your seLinux mode to permissive first and then install viper4android.
Click to expand...
Click to collapse
OK, Thanks .
thank you very much it worked perfectly
I'm SOOOOOO CLOSE to getting it working. Followed your instructions to the letter, and I get everything looking good in the driver status EXCEPT for PROCESSING. It's still a no and that's with tweaking compatibility and legacy. Any final tips?? Thanks.
Can confirm this works on the OnePlus 8 Pro running Android 11, on the xxx no limits magisk module. Thanks so much.
drewman521 said:
I'm SOOOOOO CLOSE to getting it working. Followed your instructions to the letter, and I get everything looking good in the driver status EXCEPT for PROCESSING. It's still a no and that's with tweaking compatibility and legacy. Any final tips?? Thanks.
Click to expand...
Click to collapse
Never mind... I got it....
drewman521 said:
I'm SOOOOOO CLOSE to getting it working. Followed your instructions to the letter, and I get everything looking good in the driver status EXCEPT for PROCESSING. It's still a no and that's with tweaking compatibility and legacy. Any final tips?? Thanks.
Click to expand...
Click to collapse
For some phones you need to change SeLinux to permissive to get V4A to work.
But changing seLinux to permissive is unhealthy for your phone cause it might open backdoor for some apps to take advantage of your root access.
I am updating the app and magisk now. Come back here 30 minutes later and see if the new solution works.
not working on my google pixel 3 xl android 11. installed both Audio patch and still no luck
Evender99 said:
not working on my google pixel 3 xl android 11. installed both Audio patch and still no luck
Click to expand...
Click to collapse
Play a song in your device music player.
Then open Viper4Android app, Go to that CPU lookalike icon on the top right, it will show you the driver status.
Take a screenshot and share it here.
Don't forget to keep the music player running while taking the screenshot.
Not working on OnePlus 7t Pro on Oxygen OS 11 Beta 2, set selinux to permissive, and followed all steps... Any suggestions?
L4WL13T said:
Not working on OnePlus 7t Pro on Oxygen OS 11 Beta 2, set selinux to permissive, and followed all steps... Any suggestions?
Click to expand...
Click to collapse
Have you tried the second apk and magisk?
Is one plus 7t pro and 7 pro similar?
Cause a few days ago I've set up Viper using this method on 7 pro A11 OOS beta.
RyanCr7 said:
Have you tried the second apk and magisk?
Is one plus 7t pro and 7 pro similar?
Cause a few days ago I've set up Viper using this method on 7 pro A11 OOS beta.
Click to expand...
Click to collapse
Just gave it a go, and still no luck
I'm not too sure on the differences between the two devices, though I wouldn't imagine they'd be vast. Once OOS11 comes out of beta I intend on doing a clean install, so perhaps then is the time to give this another shot.
L4WL13T said:
Just gave it a go, and still no luck
I'm not too sure on the differences between the two devices, though I wouldn't imagine they'd be vast. Once OOS11 comes out of beta I intend on doing a clean install, so perhaps then is the time to give this another shot.
Click to expand...
Click to collapse
Sorry it didn't work. Does your rom comes with a pre-installed equalizer/sound system like Dolby?
You guys should just flash the magisk viper 2.7.2 module it usually works and if it doesn't flash the other sound mods and audio sound mod lib. I found that trick back in oreo. However the samsung oneui devices are the hardest because they only come with enforcing kernel unless a dev makes a permissive kernel. I prefer 2.3.4 with the super driver but you have to have a permissive kernel on samsung. You also need to have busybox installed in magisk. With android 11 one ui 3.1 on samsung you need to use legacy mode again unless you have a permissive kernel than just busybox and viper 4.4 module installed with 2.3.4 as a user app that's my favorite. Right now I'm stuck on 2.7.2 because no permissive kernel for oneui 3.1 yet
Perfect, thanks for sharing.
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)