Database Users

[Guide] Bypass Safetynet on MM with Custom ROM & Kernel

(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.)
__________________________________​
*UPDATED*
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
- Samsung Galaxy S7
*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+/7.0+
- 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 V11.1 & Magisk Manager 4.1
- SafetyNet Checker
- Phh Super User APK. PlayStore or 2.0 Beta
- Root File Explorer. I suggest Root Browser
- Kernel Adiutor
- Root Checker
(If you cannot bypass with Xposed, use Root Switch!)
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 4.2.6, SafetyNet Helper Sample, PHH Super User APK, Root Browser and Kernel Adiutor.
Step 4:
Flashing MagiskV11.1
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 V11.1, 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. (Useless now as Magisk-V11+ has MagiskSU built into the main file and the Super User manager is built into Magisk Manager.)
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 "policy", change the permissions of the file from "444" to "440". If MagiskSU 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 V11.1. 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!
If you're still not passing, try disabling USB Debugging in Developer Options!
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.

Great tutorial by the home looks of it! Will try tomorrow morning

RandomUsername02 said:
Great tutorial by the home looks of it! Will try tomorrow morning
Click to expand...
Click to collapse
Thanks. Been using this way to bypass for 2 months now and when I realized not a lot of people knew how to do it, I knew I needed to write a tutorial. It has only not worked with one ROM I tried but worked with a variety of other roms. XtreStoLite, Alexis, CoreUi, MIUI Port etc. Note, I did not originally "find" it but there is no real guide to follow it like how I have written it above.

Thank you for this it works great! Pokémon Go here we come ?

You could also make a "stock" kernel with only the bypass by SultanXDA to make it easier for users
https://github.com/sultanxda/androi...mmit/abc05b16bbd33521c2fffaf491c5657a94bfcfc5
Goodluck

I've managed to get this and pass safetyNet - any news on Xposed?

Quintz said:
You could also make a "stock" kernel with only the bypass by SultanXDA to make it easier for users
https://github.com/sultanxda/androi...mmit/abc05b16bbd33521c2fffaf491c5657a94bfcfc5
Goodluck
Click to expand...
Click to collapse
I'll look into it. I'm fairly knew to the whole Android rooting area but I will see if I can do this.

Pedroc1999 said:
I've managed to get this and pass safetyNet - any news on Xposed?
Click to expand...
Click to collapse
I'll have me and a small group of members try to test Xposed and see if it bypasses soon.

xJovs said:
I'll have me and a small group of members try to test Xposed and see if it bypasses soon.
Click to expand...
Click to collapse
Count me in, please DM me if you require testers

Pedroc1999 said:
Count me in, please DM me if you require testers
Click to expand...
Click to collapse
I suggest you join the Telegram group. It's for CoreUi but the members are very helpful in testing. (Link is under credits.)

Worked well for me on Galaxy S7 SM-G930F with SuperMan-Rom 1.18.1
I'll try with Xposed later.
Thanks for sharing this great tutorial!
EDIT : This method with Magisk 10.2 + Xposed does NOT work

very interested to see if xposed can be bypassed

Quintz said:
You could also make a "stock" kernel with only the bypass by SultanXDA to make it easier for users
https://github.com/sultanxda/androi...mmit/abc05b16bbd33521c2fffaf491c5657a94bfcfc5
Goodluck
Click to expand...
Click to collapse
Would this be the only thing needed to pass SafetyNet? In other words, no need to hide root?

xJovs said:
I'll have me and a small group of members try to test Xposed and see if it bypasses soon.
Click to expand...
Click to collapse
Any luck?

PokemonTotalWar said:
Any luck?
Click to expand...
Click to collapse
Haven't really went and tried it yet. However I don't think it is currently possible. Been busy recently etc etc.
Also, there 'is' supposedly a bug where settings would crash and that would cause issues. If that is the case, I suggest try flashing Magisk V9 as it worked for me as well before.

not work with stock kernel. Any guide with stock kernel?

Hmmm... Twisted Kernel is only for G920F... what is F? Sorry for my ignorance. Tried googling it. Still unclear.
I have Sprint G920P. Anyone know if this would be devastating and irreversible to my phone if I tried it?
Every other method has failed for me and/or is incompatible with my Sprint phone. I'd love to try this and not brick my phone. Thanks!

F is the international variant of the s6, mainly European, might be wrong.

On my Note 4 I am currently running DevBase 3.8 rom, Enforcing RamKernel V5 R1 and Magisk 10.2.
When I enable "Magisk Hide" I don't have to fiddle with any file permissions at all, SafetyNet is passed "out of the box". :good:

Thanks you so much!
Works perfect on Nexus 6p and 5x running latest 7.1.1 stock with Elementalx kernel.
Just had some problems with changing permissions but it passes anyway. Danke!

Viper4Android Pixel 2 XL stereo speaker optimization profile (Android Q working)

Updated: OP contains instructions for Android Pie and below, post #5 has current instructions for Android Q.
Saw a couple Viper4Android threads, did not see much in terms of profiles for the 2 XL specifically. Just got the 2 XL coming from a 6P and there was a great profile to optimize it's internal speakers so decided to try out the mod for the 2 XL's speakers. Working very nicely.
Not sure if this will work with every ROM but works nice on Bootleggers (should work on any Pie ROM including stock) and thought I would share so more people could enjoy much improved sound quality. Makes rooting the phone well worth it.
Instructions:
After installing Magisk 18.1
Install BusyBox and run the set-up
Download the Viper4Android V4.1 (used Material theme) via Magisk manager
run the install process, select 2.5.0.4 material theme, install as system app, grand root access then reboot
Load the DorianX profile taken from the 6P. Just unzip then look over the extracted files.
Edited to explain further: You will probably need to individually place the "SRS Audio HD" IRS file in the Viper4Android Kernel folder and put the Profile folder in the Viper4Android Profile folder (using a file explorer to copy/paste the files). Once that's done, in the Viper4Android app under "Convolver", tap it and choose "impulse response file", You should see the "SRS Audio HD" IRS file that you placed in the Kernel folder, select it, tick the box next to Convolver to enable it. Under the main app settings you should be able to select and load the profile. If you did it correctly the DorianX profile folder should be visible to select it. It depends which version of Viper4Android you install. If you do materialized (2.5.0.4) the above should work. Let me know if any problems
Play some music. Toggle Viper4Android master power on and off under the phone speaker tab within the app then back to on once to enable it. Usually you have to do this to "officially" enable Viper4Android. If it's working you will hear the difference. Under the app settings you can verify that the app is processing as well under "driver status". Working with the latest Poweramp, Youtube, etc.
Credit to DorianX who made the profile. There are 4 profiles included to optimize specific bluetooth devices, headphones,etc but just using the internal speaker one (for now). Unable to locate the past post in the 6P forum containing the profile and which other devices were optimized to link to it.
Works very well and thought it was worth posting and making a small contribution so for now enjoy! Profile attached.

Have Viper4Android working nicely on Android Q Beta 4.
Those that downloaded this profile if you don't mind posting the Dorian profile speaker settings (all of them for each tab and whether enabled or disabled) would appreciate it. Profiles no longer can be loaded in this version of Viper.
Looking at the speaker xml file can see some of the settings but probably not all.
Magisk 19.3, Adaway works, viper now works all on today's beta 4. Tried all versions and combos. Getting the driver to install and stick was a big pain.Can post some instructions if anyone is interested. I'm sure plenty of people would like to get viper working.
Now if only Google apps like Gmail and Google play would be themed. Can see the force dark toggle is broken in this beta. Not sure if the Google apps were theming in Beta 3 or not.

powerserge1 said:
Have Viper4Android working nicely on Android Q Beta 4.
Those that downloaded this profile if you don't mind posting the Dorian profile speaker settings (all of them for each tab and whether enabled or disabled) would appreciate it. Profiles no longer can be loaded in this version of Viper.
Looking at the speaker xml file can see some of the settings but probably not all.
Magisk 19.3, Adaway works, viper now works all on today's beta 4. Tried all versions and combos. Getting the driver to install and stick was a big pain.Can post some instructions if anyone is interested. I'm sure plenty of people would like to get viper working.
Now if only Google apps like Gmail and Google play would be themed. Can see the force dark toggle is broken in this beta. Not sure if the Google apps were theming in Beta 3 or not.
Click to expand...
Click to collapse
a lot interesting of this, this is a reason why I am rollback to custom on pie while like q beta

libracez said:
a lot interesting of this, this is a reason why I am rollback to custom on pie while like q beta
Click to expand...
Click to collapse
See below

Ok I got it. No need to PM me the profile. Took most of the night but done now.
Would be unable to stay on Q without Viper4Android as well...
Make sure to uninstall all previous versions of Magisk and modules to start fresh.
Install Magisk 19.3 via twrp, install latest Magisk manager and then Busybox (make sure to set up busybox). Some are having problems with this Beta and Magisk so YMMV. Working well for me and no app lag.
On Pie in Magisk you should see Viper4Android 2.7.1 module as available
On Q it's not listed (for me at least) so get it from XDA labs.
Install Viper4Android:
https://labs.xda-developers.com/store/app/download/com.pittvandewitt.viperfx (link to direct download, must be signed in)
Or use this link: https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
The installer will install it as a magisk module. Grant supersu permissions, install driver, phone will reboot.
Install the magisk audio modifications library module. Reboot. After rebooting disable this module (do not uninstall). Reboot again.
Open up Viper4Android. If it asks you to install driver again do so and phone will automatically reboot. Repeat if needed. If driver install remains unsuccessful try enabling and disabling the audio modifications module then try again. What worked for some worked the opposite for others in past threads on previous Android versions and various devices. Here is the thread for reference: https://forum.xda-developers.com/pixel-2/help/viper4android-driver-installation-fails-t3766362
Once driver is installed the app will load properly and under driver status it will probably say "unsupported" and "abnormal". Close the app
Go back into Magisk manager. Now toggle to re enable the audio modifications module. Reboot. (This is the module that allows Viper4Android to process and can help to install the driver)
Upon reboot, Viper4Android should work. Play some music, check the driver status to verify, you may need to toggle off/on master limiter to finally enable it.
For this profile, put the SRS file in OP above in the Viper4Android Kernel folder. Under the apps speaker tab manually input these settings:
Master limiter: On
Playback gain: moderate or 2, max gain 4x, output threshold -1.9db
FIR Equalizer: On. EQ is flat
Convolver: On. Tap convolver then select the SRS inpulse file you placed in the Kernel folder. Cross channel set to 0
Profit.
You can set or disable the viper4android notification icon in the statusbar within the app's settings.
Let me know how the 2 XL's speakers sound Post updated, instructions should be clear enough. Some having problems will need to wait for the updated Magisk. Moving forward, we do have viper4android working on Q. Fully tested on my 2xl and stable with beta 4.
Thanks to @Team_DeWitt
And Dorianx for his profile originally created for the 6p

powerserge1 said:
Ok I got it. No need to PM me the profile. Took most of the night but done now.
Would be unable to stay on Q without Viper4Android as well...
Make sure to uninstall all previous versions of Magisk and modules to start fresh.
Install Magisk 19.3 via twrp, install latest Magisk manager and then Busybox (make sure to set up busybox). Some are having problems with this Beta and Magisk so YMMV. Working well for me and no app lag.
On Pie in Magisk you should see Viper4Android 2.7.1 module as available
On Q it's not listed (for me at least) so get it from XDA labs.
Install Viper4Android:
https://labs.xda-developers.com/store/app/download/com.pittvandewitt.viperfx (link to direct download, must be signed in)
Or use this link: https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
The installer will install it as a magisk module. Grant supersu permissions, install driver, phone will reboot.
Install the magisk audio modifications library module. Reboot. After rebooting disable this module (do not uninstall). Reboot again.
Open up Viper4Android. If it asks you to install driver again do so and phone will automatically reboot. Repeat if needed. If driver install remains unsuccessful try enabling and disabling the audio modifications module then try again. What worked for some worked the opposite for others in past threads on previous Android versions and various devices. Here is the thread for reference: https://forum.xda-developers.com/pixel-2/help/viper4android-driver-installation-fails-t3766362
Once driver is installed the app will load properly and under driver status it will probably say "unsupported" and "abnormal". Close the app
Go back into Magisk manager. Now toggle to re enable the audio modifications module. Reboot. (This is the module that allows Viper4Android to process and can help to install the driver)
Upon reboot, Viper4Android should work. Play some music, check the driver status to verify, you may need to toggle off/on master limiter to finally enable it.
For this profile, put the SRS file in OP above in the Viper4Android Kernel folder. Under the apps speaker tab manually input these settings:
Master limiter: On
Playback gain: moderate or 2, max gain 4x, output threshold -1.9db
FIR Equalizer: On. EQ is flat
Convolver: On. Tap convolver then select the SRS inpulse file you placed in the Kernel folder. Cross channel set to 0
Profit.
You can set or disable the viper4android notification icon in the statusbar within the app's settings.
Let me know how the 2 XL's speakers sound Post updated, instructions should be clear enough. Some having problems will need to wait for the updated Magisk. Moving forward, we do have viper4android working on Q. Fully tested on my 2xl and stable with beta 4.
Thanks to @Team_DeWitt
And Dorianx for his profile originally created for the 6p
Click to expand...
Click to collapse
succesfuly, ty
for my 2xl It was
1. installation from xda lab - reboot
2. install audio modification library - reboot
3. open viper (still asking to install driver - just close app, don't choose nothing)
4. go to Magisk switch off audio modification library - reboot
5. viper successfully load, status normal and working (media) with just my favorite profile no custom settings

libracez said:
succesfuly, ty
for my 2xl It was
1. installation from xda lab - reboot
2. install audio modification library - reboot
3. open viper (still asking to install driver - just close app, don't choose nothing)
4. go to Magisk switch off audio modification library - reboot
5. viper successfully load, status normal and working (media) with just my favorite profile no custom settings
Click to expand...
Click to collapse
Our 2 XL's can be temperamental, lol.
Glad you got it working. Not sure how the driver installed and the viper app fixed itself with the audio modifications module switched off. It's like you didn't need that module at all. Whatever works.
Just happy we have viper for Q. Played games, music, youtube and running stable here.

powerserge1 said:
Ok I got it. No need to PM me the profile. Took most of the night but done now.
Would be unable to stay on Q without Viper4Android as well...
Make sure to uninstall all previous versions of Magisk and modules to start fresh.
Install Magisk 19.3 via twrp, install latest Magisk manager and then Busybox (make sure to set up busybox). Some are having problems with this Beta and Magisk so YMMV. Working well for me and no app lag.
On Pie in Magisk you should see Viper4Android 2.7.1 module as available
On Q it's not listed (for me at least) so get it from XDA labs.
Install Viper4Android:
https://labs.xda-developers.com/store/app/download/com.pittvandewitt.viperfx (link to direct download, must be signed in)
Or use this link: https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
The installer will install it as a magisk module. Grant supersu permissions, install driver, phone will reboot.
Install the magisk audio modifications library module. Reboot. After rebooting disable this module (do not uninstall). Reboot again.
Open up Viper4Android. If it asks you to install driver again do so and phone will automatically reboot. Repeat if needed. If driver install remains unsuccessful try enabling and disabling the audio modifications module then try again. What worked for some worked the opposite for others in past threads on previous Android versions and various devices. Here is the thread for reference: https://forum.xda-developers.com/pixel-2/help/viper4android-driver-installation-fails-t3766362
Once driver is installed the app will load properly and under driver status it will probably say "unsupported" and "abnormal". Close the app
Go back into Magisk manager. Now toggle to re enable the audio modifications module. Reboot. (This is the module that allows Viper4Android to process and can help to install the driver)
Upon reboot, Viper4Android should work. Play some music, check the driver status to verify, you may need to toggle off/on master limiter to finally enable it.
For this profile, put the SRS file in OP above in the Viper4Android Kernel folder. Under the apps speaker tab manually input these settings:
Master limiter: On
Playback gain: moderate or 2, max gain 4x, output threshold -1.9db
FIR Equalizer: On. EQ is flat
Convolver: On. Tap convolver then select the SRS inpulse file you placed in the Kernel folder. Cross channel set to 0
Profit.
You can set or disable the viper4android notification icon in the statusbar within the app's settings.
Let me know how the 2 XL's speakers sound Post updated, instructions should be clear enough. Some having problems will need to wait for the updated Magisk. Moving forward, we do have viper4android working on Q. Fully tested on my 2xl and stable with beta 4.
Thanks to @Team_DeWitt
And Dorianx for his profile originally created for the 6p
Click to expand...
Click to collapse
Please forgive me for sounding like a complete tool ..lol but i cant seem to find viper4android app on my phone in the file explore to be able to put the srs file from the dorian zip to the folder in my phone , any help would be greatly appreciated

Mr. Blanco said:
Please forgive me for sounding like a complete tool ..lol but i cant seem to find viper4android app on my phone in the file explore to be able to put the srs file from the dorian zip to the folder in my phone , any help would be greatly appreciated
Click to expand...
Click to collapse
No problem. You are looking for the viper4android folder not the app. See attached screen

powerserge1 said:
No problem. You are looking for the viper4android folder not the app. See attached screen
Click to expand...
Click to collapse
I figured that and searched and searched through internal storage and root directory and i cannot find that app anywhere in my file explorer ..lol this is crazy im using Mixplorer and have attached pics , not sure if i should erase everything and start from scratch again ..lol
Edit: Okay after multiple reboots it magically showed up and was able to put file in correct place but now Driver Status Enabled = no (message) strange ....gonna start over and see if i can get everything working ..lol Thank you for your help @ powerserge1
Edit: Everything up and running and working ... Profit

Mr. Blanco said:
Edit: Everything up and running and working ... Profit
Click to expand...
Click to collapse
Good stuff. To anyone else installing viper just to note if you click on driver and see it as processing = no this does not mean you did anything or the install went wrong. Play a video or music, driver should show as processing yes. When nothing is playing then processing will be no.

Does this enable dual speaker for calls/message alerts?

How did you guys get magisk working on Q beta 4? For me it makes systemui not start on boot and it skips the lock screen entirely. And if it does boot normally, apps take over 10 seconds to launch. I have tried to wipe system data cache and then ran the flash-all bat and still have the issue. A lot of others have the issue on the magisk canary thread. Some don't have it. Someone suggested after a full wipe with -w it fixed it.

joedajoester said:
How did you guys get magisk working on Q beta 4? For me it makes systemui not start on boot and it skips the lock screen entirely. And if it does boot normally, apps take over 10 seconds to launch. I have tried to wipe system data cache and then ran the flash-all bat and still have the issue. A lot of others have the issue on the magisk canary thread. Some don't have it. Someone suggested after a full wipe with -w it fixed it.
Click to expand...
Click to collapse
Looks like I found a solution that is working for several members (and it was purely by accident because installing Magisk threw an error). Uninstall Magisk in TWRP first then:
https://forum.xda-developers.com/showpost.php?p=79682444&postcount=477

powerserge1 said:
Looks like I found a solution that is working for several members (and it was purely by accident because installing Magisk threw an error). Uninstall Magisk in TWRP first then:
https://forum.xda-developers.com/showpost.php?p=79682444&postcount=477
Click to expand...
Click to collapse
It's not working for me. I had to reboot about 4 times because systemui wasn't starting up and I was getting a black wallpaper with no status or nav bar. Finally rebooted normally and at times apps refuse to open but it's slightly better than it was. This is just so weird. Do I really need to wipe my phone or is it magisks fault?

joedajoester said:
It's not working for me. I had to reboot about 4 times because systemui wasn't starting up and I was getting a black wallpaper with no status or nav bar. Finally rebooted normally and at times apps refuse to open but it's slightly better than it was. This is just so weird. Do I really need to wipe my phone or is it magisks fault?
Click to expand...
Click to collapse
Someone in the Android Q discussion thread might be able to help better. Google pulled the beta so it's tough to say whether in your case it's a magisk or android issue. Or both.

I love this post for real, I have a Pixel 3 with Android P, viper v2.7.1.
I had to port the userprofile to the new version, if someone want it, PM me

zxspectrun said:
I love this post for real, I have a Pixel 3 with Android P, viper v2.7.1.
I had to port the userprofile to the new version, if someone want it, PM me
Click to expand...
Click to collapse
Feel free to post it as well. Curious how you were able to port the profile. Looked everywhere but couldn't find any info to convert the old profile to the new preset format.

powerserge1 said:
Feel free to post it as well. Curious how you were able to port the profile. Looked everywhere but couldn't find any info to convert the old profile to the new preset format.
Click to expand...
Click to collapse
I just installed the viper4android mod showed on the screenshot and it ported all my old profiles
attached dorian ported to v2.7.1.0

zxspectrun said:
I just installed the viper4android mod showed on the screenshot and it ported all my old profiles
attached dorian ported to v2.7.1.0
Click to expand...
Click to collapse
Yes it did the same for me. The first time, almost forgot. I did not find the sound to be the same, not even close. Ultimately I still had my Nexus 6p and was able to retrieve the settings and input them manually. Then the sound was as it should be.
Do you find the sound identical with the ported profiles? It might be hit and miss.

V4A OOS10

Anyone having trouble with getting V4A to work on OOS10? Everytime I open it up after a reboot, it keeps asking to re-install drivers. Any solutions?

This steps works for me
Uninstall ViPER4Android and Audio Modification Library if you have them installed in Magisk. Reboot after uninstalling.
Download the latest ViPER4Android FX apk from XDA Labs.
Install the downloaded APK.
Open the ViPER4Android application but do not install the driver yet. Click on cancel when prompted.
Close the application and then open Magisk Manager.
Install Audio Modification Library from the downloads section and do not reboot once the installation is complete.
Go back to ViPER4Android and now install the driver. The device will reboot automatically.
Once booted, go to Magisk Manager and disable Audio Modification Library (not uninstall).
Open ViPER4Android and install the driver again. The device will reboot automatically.
Once the device finished booting, go check if the ViPER4Android is installed. If yes, congrats! You’re done! If not, there’s a few more steps you need to take. Do not install the driver, click on cancel.
Close ViPER4Android and go back to Magisk Manager to re-enable Audio Modification Library.
Go back to ViPER4Android and then install the driver again. The device will reboot.
Credits to this website source: V4a on Android 10

Viper4Android On Stock 8.0 Rom

Hi guys!
This is my first thread so sorry if i make any mistakes, so let me know if i did any!
So as the title says, We can get viper4android on stock rom but we need to
-Have unlocked bootloader
-Magisk
-Big brain, and focus to not f. it up!
-Back up your rom and data, just in case :silly:
So, we need magisk to install Viper4android module
-Magisk: https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
-Viper4Android magisk module:
https://zackptg5.com/downloads/v4afx_v2.7.1.6.zip
-App Uninstaller:
https://redirect.viglink.com/?key=e...uninstaller-remove-package-t3423910/amp/&ref=
So first we need to install app uninstaller and give it root and memory premissions, after that we need to find any app that is associated with miusic enchacments, like in my case: MiusicFX and Sound settings/Enchacments, And uninstall them!
After it uninstalls we refuse to automaticly reboot, then we launch magisk and install viper4android module either from Modules sections and selecting Viper4Android file or just searching it in Download section
After it downloads and installs we, again not reboot and just launch the viper4android app, give it root premisions after we click to accept the messange that tells us that it will intall an driver for itself let it istall.
After the viper installs itself phone will reboot automaticly.
Viper can not work on first boot, like in my case just open the app if it not works reboot the phone and it should work fine.
And Viola, You have Viper4Android on your stock Sony rom :laugh:
If you have any problems let me know. I will try to help you :silly:

[Question] How to fake 'Official' Device Status on SM-T350

Hello, I have an SM-T350 rooted with Magisk, how can I fake the Device Status to show Official under settings?
(Right now it says Custom)

Using an Edxposed Module named "Firefds Kit" To install edxposed YouTube or Google Search "How to Install edxposed on Android (Version Goes Here)" then once installed, go to the hamburger menu of the exposed manager app and select downloads, then search Firefds Kit, then select the one for your android, for example, the one for Android Pie would be Firefds Kit [P], then install the latest version, select modules in the hamburger menu, and turn on Firefds Kit, restart, then open the firefds kit app, then go to the hamburger menu, tap security, then turn on "fake official status", restart, and check settings, THIS WILL NOT MAKE APPS LIKE SECURE FOLDER AND S HEALTH (If you sideload it since your on a tablet) THINK YOUR ON OFFICIAL BINARY. to do that, you need to patch one of the system files using a text editor in a root browser and restart, and for secure folder, it is under security in firefds kit, turn on enable secure folder, restart, try to enable it, restart, then hopefully the icon in apps should be there, tap it and set it up.

CaptainChris2018 said:
Using an Edxposed Module named "Firefds Kit" To install edxposed YouTube or Google Search "How to Install edxposed on Android (Version Goes Here)" then once installed, go to the hamburger menu of the exposed manager app and select downloads, then search Firefds Kit, then select the one for your android, for example, the one for Android Pie would be Firefds Kit [P], then install the latest version, select modules in the hamburger menu, and turn on Firefds Kit, restart, then open the firefds kit app, then go to the hamburger menu, tap security, then turn on "fake official status", restart, and check settings, THIS WILL NOT MAKE APPS LIKE SECURE FOLDER AND S HEALTH (If you sideload it since your on a tablet) THINK YOUR ON OFFICIAL BINARY. to do that, you need to patch one of the system files using a text editor in a root browser and restart, and for secure folder, it is under security in firefds kit, turn on enable secure folder, restart, try to enable it, restart, then hopefully the icon in apps should be there, tap it and set it up.
Click to expand...
Click to collapse
Thanks but I have Android 7.1.1 which only works with Xposed not Edxposed so will this work with Xposed? Also what about passing safetynet? I thought safetynet wouldn't pass with Xposed installed? Also when you said "to do that, you need to patch one of the system files using a text editor in a root browser and restart" which system file were you talking about? What do I need to patch? Can I do it without a module?

JJcoder said:
Thanks but I have Android 7.1.1 which only works with Xposed not Edxposed so will this work with Xposed? Also what about passing safetynet? I thought safetynet wouldn't pass with Xposed installed? Also when you said "to do that, you need to patch one of the system files using a text editor in a root browser and restart" which system file were you talking about? What do I need to patch? Can I do it without a module?
Click to expand...
Click to collapse
The system file patch is only if you have s health and want it to work. since you are on a tablet you must likely have notsideloaded it, I don't know if you can do it without a module, the process should be the same with xposed

CaptainChris2018 said:
The system file patch is only if you have s health and want it to work. since you are on a tablet you must likely have notsideloaded it, I don't know if you can do it without a module, the process should be the same with xposed
Click to expand...
Click to collapse
Well, I can't really do it with Xposed because safetynet won't pass plus when I go into Xposed installer (Magisk version) after installing the Xposed Framework Magisk module it still says "Xposed framework is not installed" when I open Xposed installer. So, I may just have to try this on my S8 which runs Android Pie

JJcoder said:
Well, I can't really do it with Xposed because safetynet won't pass plus when I go into Xposed installer (Magisk version) after installing the Xposed Framework Magisk module it still says "Xposed framework is not installed" when I open Xposed installer. So, I may just have to try this on my S8 which runs Android Pie
Click to expand...
Click to collapse
Did you install it properly or turn on Magisk Hide? Since it makes safteynet pass

CaptainChris2018 said:
Did you install it properly or turn on Magisk Hide? Since it makes safteynet pass
Click to expand...
Click to collapse
Yes, MagiskHide was on but I don't think MagiskHide can hide Xposed even if it is system-less. Also, yes I installed Xposed correctly by first installing the Magisk module and then by installing the Magisk compatible Xposed installer app. I don't really know how to solve these two problems

JJcoder said:
Yes, MagiskHide was on but I don't think MagiskHide can hide Xposed even if it is system-less. Also, yes I installed Xposed correctly by first installing the Magisk module and then by installing the Magisk compatible Xposed installer app. I don't really know how to solve these two problems
Click to expand...
Click to collapse
you need a special xposed apk made for the magisk xposed

elliwigy said:
you need a special xposed apk made for the magisk xposed
Click to expand...
Click to collapse
I know, that's what I meant by the "Magisk compatible Xposed installer"