ViPER4Android 2.7.1.0 + Dolby Atmos + DDPlus
{
"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"
}
Here's the proof
Device: OnePlus 7 Pro
Android Version: 10 and up
*Unlock BL and Rooted Only
*Any OnePlus running Android 10
Steps to Install ViPER4Android on Android 10
1.Download the latest ViPER4Android v2.7.1.0 APK
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
2.Install the downloaded APK on your Android 10 device using a file manager app.
3.Launch the ‘ViPER4Android’ app but do not install the drivers right now.
4.Open ‘Magisk Manager’ and go to the ‘Downloads’ section of the app.
5.Search and find the “Audio Modification Library” module and press the download icon next to it.
6.Tap on the ‘INSTALL’ button to install the module on your device.
7.Magisk module installer will prompt you to reboot but do not reboot your phone yet.
8.Now go back to the ViPER4Android app, tap on “OK” to install the required V4A drivers.
9.Grant the Superuser permissions to the app when prompted.
10.After the drivers are installed, the device will automatically reboot.
11.Once the device reboots, go to ‘Magisk Manager’ → ‘Modules’ and uncheck the ‘Audio Modification Library’ to disable it.
Now head back to ViPER4Android, repeat the driver installation process, and let the device reboot.
Once the device boots, launch the ViPER4Android app. Now, if the drivers are installed properly, you’re done! If not, only then follow the steps further.
Go to ‘Magisk Manager’ → ‘Modules’ and re-enable the ‘Audio Modification Library’ module.
Open ViPER4Android, install the drivers when prompted, and let the device reboot.
Viper4android 2.7.1.0 profiles
https://mega.nz/#!bZgEjKYJ!RJNhRUnKMmZx-7be77An9oOhlrK-H5ASgGe8uZlmGgg
DDPlus
Install via Magisk Manager
DDPlus Magisk Module
Download Here in the 2nd post
*for DDPlus
1. Press DDPlus app and choose music/movie/or game (gives error or force close but it's ok)
2. Open again the DDPlus and turn on Volume Lever (gives error or force close but it's ok)
3. Open again the DDPlus and turn on Dialogue Enhancer (gives error or force close but it's ok)
4. Open again the DDPlus and turn on Surround Visualizer (gives error or force close but it's ok)
5. Open again the DDPlus and choose your Intelligent EQ (gives error or force close but it's ok).
6. Now open DDPlus without Error and force close.
Dolby Atmos (Stock)
Just choose Music..
Enjoy
Thanks to the XDA Community
@repey6
@Team_DeWitt
@zhuhang
@viper520
@topjohnwu
1.Thank you.
2.Dolby Atmos not working on Oos ob7 OnePlus 7 pro. Instaled like a module with Magisk Manager.
I follow the guide. FC on anything i touch in the app. All the time. It stuck on "MOVIE" settting. Does not take other settings. Does not set the Eq at all. FC :crying:
I use/test this: [Q-10]Dolby Digital Plus_v.6.8-[UNiTY][Light]_by_repey6-20191212.zip
This method didn't work because you must disable with titanium backup the default dolby integrated with oos 10 first, then install the magisk dolby mod.
Other way it's installing xxx_nolimits and set dolby in his script profile, the mod disables the integrated dolby in oos for you.
I followed your steps to install Viper without problem but DDPlus shows error after installed it. One key step you have forgotten to write it down: Need to install "magisk_selinux_manager" in magisk, then DDPlus will be working !
https://drive.google.com/file/d/10-Vgme3lxF0e5jVU3-gK95btUsh5Rhx1/view?usp=drivesdk
Kris
Does anyone know how to get rid of all this creap ? Uninstall on reboot not working.
Happy new year !
null0seven said:
Does anyone know how to get rid of all this creap ? Uninstall on reboot not working.
Click to expand...
Click to collapse
try uninstalling mods and upgrade magisk, if you have the latest install canary build.
The Dolby app stops continuously (even with SeLinux Permissive and BusyBox installed)...
Toni Moon said:
try uninstalling mods and upgrade magisk, if you have the latest install canary build.
Click to expand...
Click to collapse
Has i wrote, uninstalling + reboot not working. I try one at the time, all at once. I'm on the latest Magisk Canary 27.12.2019.
Dragoș2200 said:
The proximity sensor will not work.
Click to expand...
Click to collapse
null0seven said:
Has i wrote, uninstalling + reboot not working. I try one at the time, all at once. I'm on the latest Magisk Canary 27.12.2019.
Click to expand...
Click to collapse
It's working mate.. here's the proof
Maybe you can share step by step how did you make it work.
Today we got new Magisk Canary update and with that i manage to clean up the dirt in my Magisk modules.
After checking my OP7P Proximity sensor by app "Proximity sensor test", My phone without proximity issue after testing it even I install Magisk Selinux manager" !
My system is OOS 10.3.0 with stable magisk 20.2 !
Dragoș2200 said:
The proximity sensor will not work.
Click to expand...
Click to collapse
i don't have issues with proximity sensor, but i read in xxx_nolimits thread that some users have this issue after install dolby plus.
Kris Chen said:
After checking my OP7P Proximity sensor by app "Proximity sensor test", My phone without proximity issue after testing it even I install Magisk Selinux manager" !
My system is OOS 10.3.0 with stable magisk 20.2 !
Click to expand...
Click to collapse
If you're still on pie, this mod is a better alternative to viper. It works great and settings can be changed via xml file. I use it together with Dolby digital. It's a little known port but I've used it for a while now.
https://www.google.com/amp/s/forum....udio-engine-samsung-galaxy-s8s9-t3904527/amp/
https://forum.xda-developers.com/showpost.php?p=81493535&postcount=3684
I test next week end on One plus 7
DolbyAtmos-axon9-A10-0.64
Works fine on One plus 7 Havoc OS 3.1
just disabled Dolby Atmos stock
Magisk v20.3
Thanks !!! Guitardedhero the legend of Dolby Atmos port
tropical cactus said:
If you're still on pie, this mod is a better alternative to viper. It works great and settings can be changed via xml file. I use it together with Dolby digital. It's a little known port but I've used it for a while now.
https://www.google.com/amp/s/forum....udio-engine-samsung-galaxy-s8s9-t3904527/amp/
Click to expand...
Click to collapse
Greetings @tropical cactus,
I'm interested in this module, will you please guide the steps to properly install it on Oneplus 7(Non-Pro), Android Pie.
Regards.
haris_94 said:
Greetings @tropical cactus,
I'm interested in this module, will you please guide the steps to properly install it on Oneplus 7(Non-Pro), Android Pie.
Regards.
Click to expand...
Click to collapse
Hi, I have the 7 pro but it should work on your device. Do NOT flash on Android 10. You will end up with a crash dump. If you move to 10, ensure you uninstall it using the uninstaller. Removing module is not enough. Flash module in twrp. I've moved back to the 4.2 version. More choices to edit. Reboot and flash corresponding xml zip. Wipe cache and reboot. Go to system/etc and find soundalive folder. In it, you will find xml. Use text editor to change values. When first opened, it will be incomplete. Change a Bluetooth setting, save and exit. When you go back in, the xml will be fully loaded. Follow the instructions in the thread on how to change values. It really is a good mod. Together with Dolby digital and ice sound, my 7pro sounds louder and clearer than a Note 10. Good luck.
tropical cactus said:
Hi, I have the 7 pro but it should work on your device. Do NOT flash on Android 10. You will end up with a crash dump. If you move to 10, ensure you uninstall it using the uninstaller. Removing module is not enough. Flash module in twrp. I've moved back to the 4.2 version. More choices to edit. Reboot and flash corresponding xml zip. Wipe cache and reboot. Go to system/etc and find soundalive folder. In it, you will find xml. Use text editor to change values. When first opened, it will be incomplete. Change a Bluetooth setting, save and exit. When you go back in, the xml will be fully loaded. Follow the instructions in the thread on how to change values. It really is a good mod. Together with Dolby digital and ice sound, my 7pro sounds louder and clearer than a Note 10. Good luck.
Click to expand...
Click to collapse
Thanks for the immediate response,
Please correct me if I'm wrong @tropical cactus
first I need to flash 4.2 version via twrp then reboot to system
then again reboot to recovery and flash corresponding xml but this time wipe cache & dalvik cache before rebooting to system.
I'm going to use default settings and I'm not have any plan to upgrade to Android 10.
Do I also need to install sound alive apk? If yes, then please provide the link for the same.
Regards.
haris_94 said:
Thanks for the immediate response,
Please correct me if I'm wrong @tropical cactus
first I need to flash 4.2 version via twrp then reboot to system
then again reboot to recovery and flash corresponding xml but this time wipe cache & dalvik cache before rebooting to system.
I'm going to use default settings and I'm not have any plan to upgrade to Android 10.
Do I also need to install sound alive apk? If yes, then please provide the link for the same.
Regards.
Click to expand...
Click to collapse
Yes, flash both in twrp. Doesn't work if flash in magisk. Download 4.2 and soundalive _r6_son.zip. The xml will give you control over the sound, like on a Samsung phone. There's tube amp effect, bass and treble control, surround, concert hall. If you don't want that, just flash 4.2 or the latest 4.3.1. Remember to flash old version to uninstall before flashing new one. Forgot, no uninstaller. Just flash same zip to uninstall.
Related
Hi guys! now i show to work magisk safatynet pass
Thanks @xJovs for your tutorial!
Link for your post Click Here!
Let's go
All rights reserved @xJovs for this tutorial
(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
- SamSung Galaxy S7 EDGE
__________________________________
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.)
- Magisk V11.1 & Magisk Manager 4.1
- 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.)
Step 1:
Clean Install
The first step install your custo rom, i installed SuperRom 1.2 MM and custom Karnel SuperStock 1.6 on installation.
Step 2: (For no MagiskSU users!)
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, 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.
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.[/QUOTE]
Thanks man!
This actually worked on my S6 Edge SM-G925I.
I was just hoping if you could also figure out a way to use Samsung Pay despite having the Knox triggered.
TIA.
Shrey14 said:
Thanks man!
This actually worked on my S6 Edge SM-G925I.
I was just hoping if you could also figure out a way to use Samsung Pay despite having the Knox triggered.
TIA.
Click to expand...
Click to collapse
You are welcome!
On Android N you have update your Karnel for SuperStock 2.3 for work safetynet.
ClaudioJuniorBR said:
You are welcome!
On Android N you have update your Karnel for SuperStock 2.3 for work safetynet.
Click to expand...
Click to collapse
Currently I'm on Android M and safetynet is working. Please see the attachment.
Close this topic please!
I am stuck on stage 5 because I cannot see the check boxes on magisk manager 4.2.7. How to proceed?
Wow can't belive this actually worked!I spended so many times trying to make it work thanks OP.
However i can't make it work with xposed, the Safetynet check fails, it was strange because the first time it worked but as soon as i rebooted it was not working anymore.
There is a way to make Xposed work?I used Root Switch but it says is not fully supported for Magisk because it says that Magisk have it's own switch, i don't think it's referring to Magisk Hide because i have already enabled it so maybe i'm missing something here?
Help needed with Step 4
Hi guys,
I have been trying to flash Magisk v12 on my S7 edge (SM-G935FD) without super su, in hopes of using Magisk Su but I keep receiving ERROR: 1 in TWRP when it is trying to mount SU.
I am using a stock Rom and have performed a clean wipe in TWRP, but still cannot get Magisk v12 zip to install without the error 1 message. Appreciate if someone can enlighten me on how to over come this issue.
Sandiramogan said:
Hi guys,
I have been trying to flash Magisk v12 on my S7 edge (SM-G935FD) without super su, in hopes of using Magisk Su but I keep receiving ERROR: 1 in TWRP when it is trying to mount SU.
I am using a stock Rom and have performed a clean wipe in TWRP, but still cannot get Magisk v12 zip to install without the error 1 message. Appreciate if someone can enlighten me on how to over come this issue.
Click to expand...
Click to collapse
Error 1 can mean several things, post a recovery log from the installation.
And this guide is a bit outdated... Magisk performs step 6 and 7 automatically since v11.5.
Edit: answer my post in the support thread instead.
With magisk v12.. Any idea?
Didgeridoohan said:
Error 1 can mean several things, post a recovery log from the installation.
And this guide is a bit outdated... Magisk performs step 6 and 7 automatically since v11.5.
Edit: answer my post in the support thread instead.
Click to expand...
Click to collapse
Thank you for your reply. I managed to install Magisk v12 after performing a completely clean wipe and flashing the stock ROM from ODIN. I immediately attempted to install Magisk after flashing the latest version of TWRP and everything works like a charm, even passing Safety Net. However on the other hand, I'm now trying to figure out how to fake Knox 0x0 as mentioned in the changelog. If you do have any idea, please do share and let me know.
Cheers and have a great weekend.
Sandiramogan said:
Thank you for your reply. I managed to install Magisk v12 after performing a completely clean wipe and flashing the stock ROM from ODIN. I immediately attempted to install Magisk after flashing the latest version of TWRP and everything works like a charm, even passing Safety Net. However on the other hand, I'm now trying to figure out how to fake Knox 0x0 as mentioned in the changelog. If you do have any idea, please do share and let me know.
Cheers and have a great weekend.
Click to expand...
Click to collapse
Since you're passing SafetyNet it's a pretty sure bet that you have Magisk Hide enabled. That's all you need to do since the KNOX counter is masked by Magisk Hide. It doesn't work?
Do you know if Google changed something? Today I noticed that I can't see Fire Emblem and Mario Run in the Playstore. Days ago it was working fine but now it seems they are not compatible again.
I don't know why but I can't add new scripts in Kernel Adiutor.
Everything else worked. Any idea?
things i do to play super mario run
Works well when disable xposed in module section in magisk manager then reboot.
Any fix for work safetynet pass with enable xposed ?
koko115 said:
Any fix for work safetynet pass with enable xposed ?
Click to expand...
Click to collapse
Nope...
935V user here: I get "Custom Binary Blocked by Secure Boot". I flashed using Flashfire instead of TWRP. I used the root method described here: https://forum.xda-developers.com/verizon-s7-edge/how-to/root-method-nougat-t3566978
Should I have rooted a different way as to utilize TWRP?
some one can help me?
imgur.com/a/4cufj
Does anyone know if this works on any of the US models?
{
"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"
}
*** I'M NOT RESPONSIBLE IF YOUR DEVICE IS NOT BOOTING UP, DEVICE IS BRICKED, GOT BOOTLOOPED OR WHATEVER ****** DO AT YOUR OWN RISK ****** READ AND UNDERSTAND EACH AND EVERY STEPS CAREFULLY BEFORE PROCEEDING ***
The most commonly used Audio modification tool among the Android users is ViPER4Android. It has been making audio clearer and more perceptible on millions of Android devices out there. Today here, I will be guiding you on how to Install ViPER4Android on any ROM in your devices.
After months and months of no activity, the Viper4Android developer zhuhang has finally announced the official 2.5.0.5 update. While primarily, the update aims at enabling users to install ViPER4Android on Nougat 7.x.x, it also incorporates some new features.
Code:
CHANGELOG:
New App icon, package name, and UI
Added cross-channel (“quad channel”) convolver support.
This allows faithful reproduction of sound-field effects requiring such cross-channel convolution, such as simulation of speaker soundfield on headphones, or crosstalk cancellation (stereo widening) on stereo speakers.
Added FET compressor (new compressor / limiter simulating operation of FET circuits)
Support for custom settings storage path (no more looking everywhere in the phone for the settings directory!)
Miscellaneous bug fixes.
Code:
BUILD INFORMATION:
Version: FX version 2.5.0.5 (active)
Codename: (FX version) Beautiful
Compiled date: September 1,2016 / September 4,2013 – Official Release
Operating environment: Android 2.3 / 4.0 / 4.1 / 4.2 / 4.3 / 4.4 / 5.0 / 6.0 / 7.0/7.1/7.1.2
CPU platforms: ARM (ARM CortexA8 or higher), x86(Atom/i3/i5/i7)
Language: English (US) / Simplified Chinese / Traditional Chinese / more
Warning -
Installing incorrect/incompatible mods on your Android device could be harmful. Please make sure that you are aware of the outcome and don’t forget to take a Nandroid backup of your current ROM before proceeding. DroidOrigin or any of its members shall not be held liable for any damage to your device. However, if you’re stuck, we will still try to pull you out of any troubles.[/CENTER]
Installing Viper4Android is pretty simple, given that you meet the requirements pre-hand. If you have found yourself in a sticky situation, then the steps below could be of help too.
Requirement -
Rooted Device.
TWRP recovery.
BusyBox 1.26.2
ES File Explorer or Any Root File Browser.
NOTE :There are two files provided in the download section below. One is for manually installing and another one is for directly flashing through twrp. Please download any one file whichever you want and then follow the correct steps for that file only. Before proceeding, please check whether you have downloaded the manual installation file or flashable file. If you have downloaded the manual installation file then follow the procedures for manually installing the app & drivers and if you have downloaded the flashable zip file then follow the procedures for flashing the zip file through TWRP and then installing the driver.
Steps For Manually Installing ViPER4Android in your device-
1. Now that you have everything setup correctly, download the official ViPER4Android for Nougat (FX 2.5.0.5) from below.
2. Extract the downloaded zip and it will contain two apks –
ViPER4Android_FX_v2505_A4.x-A7.x.apk
ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk
3. Since we are going to install Viper4Android on Nougat, we will just need the “ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk” file.
4. If you have downloaded it to your PC instead, just transfer the apk to your phone’s storage.
5. Before we head to the installation, open the ES File Explorer and grant it root permissions when prompted.
6. Open ES File Explorer and browse to the location where the apk is present. Copy the “ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk” file and move it to “/system/priv-app“.
7. We are not done yet. Long-press the file, tap on the 3-dot overflow button, and select Properties. And set its permission to -rw-r–r–, and select APPLY.
8. Reboot your device now.
9. Now go to the app drawer and run the ViPER4Android FX app. When you are asked for storage permissions, make sure to grant them.
10. A prompt will display for driver installation. Select Yes to confirm the driver installation process. You will also need to allow Superuser (root) permissions to the app.
11. Your phone’s screen may freeze, don’t worry just wait and do not exit the app. Your android system will popup that app is not responding, just press wait button. Let the app finish it's driver installation, so don't exit the app now. When the installation is successful, you will get a message. Tap OK and reboot your device.
When your device reboots, you will have completely functional ViPER4Android on Nougat and other Android versions.
If you have trouble in driver installation, read the troubleshooting section below or comment right away.
Steps For Installing ViPER4Android through TWRP in your devices
1. Download the flashable zip file from below (Filename - ViPER4Android_2.5.0.5 (Flashable))
2. Reboot to recovery.
3. Flash the ViPER4Android_2.5.0.5 (Flashable).zip file.
4. Reboot system.
5. When device is booted up properly, then open the ViPER4Android app.
6. If it will ask root permission then grant the root permission.
7. It will popup a message for installing the driver. Just tap ok and wait for installing the driver.
8. Your phone’s screen may freeze, don’t worry just wait and do not exit the app. Your android system will popup that app is not responding, just press wait button. Let the app finish it's driver installation, so don't exit the app now. When the installation is successful, you will get a message. Tap OK and reboot your device.
When your device reboots, you will have completely functional ViPER4Android on Nougat and other Android versions.
NOTE : PLEASE DISABLE YOUR DEFAULT MUSICFX OR AUDIOFX IN ORDER TO USE ViPER4AndroidFX
Credits -
zhuhang for developing the ViPER4Android
ViPER4Android Team
and many more.
(If I have missed anyone's name then please PM me for that)
You can download the ViPER4Android FX_version2.5.0.5 from below. Please follow the steps properly otherwise you will end up with problems.
Troubleshooting -
If your driver installation has failed, then there could be few reasons behind it. Follow the simple steps below and check if anything helps.
Getting “Driver instal failed: I/O error, please reboot and try again”? Then read step again.
Uninstall the current busybox and switch to a different app to install busybox on your Android.
The most reliable and widely used method to root and manage permissions is SuperSU. If you’re using any other root method, uninstall that and opt for SuperSU.
Driver installation was successful, but V4A is still not working? The most common reason behind this is that your device may have other sound mods or tweaks installed. Disable them and completely remove them if possible.
On some devices, you may require to change your SELinux status from “Enforcing” to “Permissive”. You can do that by using the SELinuxToggler.
If nothing above has worked for you, then you may try switching to a different ROM as your last resort.
If you still have problems, comment below and don’t forget to mention your device model, ROM, and Android version.
reserved
reserved 2
do we still need busybox?
emirfahimi said:
do we still need busybox?
Click to expand...
Click to collapse
Without busybox you can't install viper4android. You have to install the latest busybox.
Hey bro , i use lineage os rom and i get driver install failed eventhough i change different busybox ..
not working it says cannot detect root and failed to install driver
emirfahimi said:
not working it says cannot detect root and failed to install driver
Click to expand...
Click to collapse
First root your device, then install the busybox. After that install the viper4android.
raven001 said:
Hey bro , i use lineage os rom and i get driver install failed eventhough i change different busybox ..
Click to expand...
Click to collapse
Please check the troubleshooting post.
Otherwise try this busybox which is shown in the screenshot below -
juyel92 said:
First root your device, then install the busybox. After that install the viper4android.
Click to expand...
Click to collapse
i did exactly as the step my phone is already rooted
emirfahimi said:
i did exactly as the step my phone is already rooted
Click to expand...
Click to collapse
Please check in devloper menu whether the root access is enabled for both adb & apps.
juyel92 said:
Please check the troubleshooting post.
Otherwise try this busybox which is shown in the screenshot below -
Click to expand...
Click to collapse
Still not work bro ,,
juyel92 said:
Please check in devloper menu whether the root access is enabled for both adb & apps.
Click to expand...
Click to collapse
yes it is adb and apps but its working other app such as free dom or lucky patcher can be used and i'm pretty sure root is working on my zenfone 5
raven001 said:
Still not work bro ,,
Click to expand...
Click to collapse
What error you are getting?
emirfahimi said:
yes it is adb and apps but its working other app such as free dom or lucky patcher can be used and i'm pretty sure root is working on my zenfone 5
Click to expand...
Click to collapse
Can you please share the screenshot of that error ?
juyel92 said:
What error you are getting?
Click to expand...
Click to collapse
This
juyel92 said:
Can you please share the screenshot of that error ?
Click to expand...
Click to collapse
View attachment 4131491
raven001 said:
This
Click to expand...
Click to collapse
I will check this issues.
Please give me some time. I will soon update/fix this issues.
I will soon fix these issues. Till then please wait and be patient.
{
"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"
}
Latest Stable Magisk Version : v14.0 [2017.9.6]
Latest Magisk Manager Version : v5.3.0 [2017.9.6]
Hello, welcome to the official Magisk Release For Zenfone 2 Z00A/Z008 taken from 4pda.ru forum!
Magisk can ROOT your device, along with standard common patches.
It packs with a super powerful Universal Systemless Interface, allowing unlimited potential!
Magisk modifies boot image and add files to /data and /cache
It touches your /system partition only if root installed in /system is detected!
Features
100% fully open source and easy to build!
Magic Mount :
Allow you to do any system (vendor) modification without actually tampering the partitions.
Anything can be loaded with Magisk systemless-ly!
MagiskSU : Open Source Root Solution
Root your device with MagiskSU, based on phh's Superuser, which is based on CM Superuser.
Magisk Manager :
MagiskSU Root Management, Upgrade Magisk in-app,
Manage, Upgrade, Download, Install Magisk Modules from the community driven online Magisk Module Repo.
Magisk Hide :
Hide Magisk from detection, mainly targeting Google's SafetyNet
Resetprop :
Allow you to do any modifications to system props (build.prop), including read-only props.
It is also used along with magiskhide for tricking various device states
Multiple Entry Points :
Provide several entry points to developers, reliably pausing the boot process before everything is done.
Include post-fs (cache) mode, which happens even earlier than data is mounted (used to replace Boot Animation etc.)
Standard Stuffs :
Remove dm-verity, forceencrypt, unlock partitions blocks to support remount to rw
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager Through TWRP Recovery
For installing Magisk the first time!
(never update magisk through application it will caused bootloop)
(If you have Xposed safetynet won't work)
Install Lastest Magisk Manager Apk
Reboot To TWRP Recovery
Select Lastest Magisk ZIP, then flash it
Reboot To Systems (wipe cache and dalvik is'nt needed if you want it then go for it)
Downloads
Lastest Magisk : https://drive.google.com/file/d/0B_t_ymFu4cH4eDNaYkhjU3lJb28/view
Lastest Magisk Uninstaller : https://drive.google.com/file/d/0B_t_ymFu4cH4bktMb2xTdk10Yzg/view
Lastest Magisk Manager Apk : https://drive.google.com/file/d/0B_t_ymFu4cH4dkpNUHh3NXVuOWc/view
Credits & Specials Thanks To All Developer XDA Forum & 4PDA Forum!
where to get uninstaller?
Arerive said:
where to get uninstaller?
Click to expand...
Click to collapse
haha forget to add it, wait bro
nice, thanks you so much, btw i had Magisk 13.3 installed, do i need to remove my module before flashing the new Magisk?
sushuguru said:
nice, thanks you so much, btw i had Magisk 13.3 installed, do i need to remove my module before flashing the new Magisk?
Click to expand...
Click to collapse
no just reflashed is ok bro no problem, same source.
mine from 12.0 to 14.0 without anyproblem
FYI : if you have xposed installed, safetynet won't work or gone
Thanks for the update! just relating here a mess i did:
You noticed the update today 2:15am XDA time, so i did wrong, opened Magisk Manager, and did the update.
what do i did to fix it:
1 -Once having Viper OS 3.0 on pc, i downloaded magisk installer, plus last HoloN kernel i was using. Taking advantage of that I was doing a dirty flash, i also down'ed last Gapps (but down'ed wrong version . . .)
Turned off phone, toke SD & plug on PC, put all downloadeds in external SD card;
2 - My Z00AD was in bootlop, so i reboot it in recovery and:
3 - Advanced Wipe > Wipe DAlvik/art cache + System + cache (JUST IT ONES!);
4 - Install ROM > Install last HoloN 6s0 version > flash Gapps and ... I downloaded x86-x64 version. Stopped here. . .
. . . So i had a previous Gapps version on PC, then . . .
Turn off Phone > pull out SD card & place x86pico 7.1 gapps version on SD
reboot ZF2 in recovery > did all step by step again:
1 - Advanced Wipe > Wipe Dalvik/art cache + System + cache (JUST IT ONES!);
2 - Install ROM > Install last HoloN 6s0 version > flash Gapps > flash Magisk > reboot.
So, i hope no other ones pass thrught that, keep attention with root stuffs . . .
El Cruz said:
Thanks for the update! just relating here a mess i did:
You noticed the update today 2:15am XDA time, so i did wrong, opened Magisk Manager, and did the update.
what do i did to fix it:
1 -Once having Viper OS 3.0 on pc, i downloaded magisk installer, plus last HoloN kernel i was using. Taking advantage of that I was doing a dirty flash, i also down'ed last Gapps (but down'ed wrong version . . .)
Turned off phone, toke SD & plug on PC, put all downloadeds in external SD card;
2 - My Z00AD was in bootlop, so i reboot it in recovery and:
3 - Advanced Wipe > Wipe DAlvik/art cache + System + cache (JUST IT ONES!);
4 - Install ROM > Install last HoloN 6s0 version > flash Gapps and ... I downloaded x86-x64 version. Stopped here. . .
. . . So i had a previous Gapps version on PC, then . . .
Turn off Phone > pull out SD card & place x86pico 7.1 gapps version on SD
reboot ZF2 in recovery > did all step by step again:
1 - Advanced Wipe > Wipe Dalvik/art cache + System + cache (JUST IT ONES!);
2 - Install ROM > Install last HoloN 6s0 version > flash Gapps > flash Magisk > reboot.
So, i hope no other ones pass thrught that, keep attention with root stuffs . . .
Click to expand...
Click to collapse
as I said on the post, dont update magisk from apk stuff you will get bootloop hehe
I installed it and reboot but my phone stuck at the Oneplus - Powered by Android Logo. Can someone help me? Im using Oneplus 5 btw
Andy1N said:
I installed it and reboot but my phone stuck at the Oneplus - Powered by Android Logo. Can someone help me? Im using Oneplus 5 btw
Click to expand...
Click to collapse
Try flashing Uninstaller zip first, and then flash the proper magisk package for your mobile... If you look at the title, you will see here "... for Zenfone" [emoji52]
Inviato dal mio ASUS_Z00AD utilizzando Tapatalk
Andy1N said:
I installed it and reboot but my phone stuck at the Oneplus - Powered by Android Logo. Can someone help me? Im using Oneplus 5 btw
Click to expand...
Click to collapse
bro its for zenfone 2 hahaha ??
Does it work with BORETS rom? And can i just flash it via recovery with borets rom?
@indunrise bro., i think the zip missing a file when installed.,the "busybox" file should be in /data/magisk/ since the newest magisk module uses that file to run.,but its absent.,so im keep getting error 1 when flashing any new v14.0 modules through twrp...it works fine now after i've put the "busybox" file at the proper place i've mentioned above...can u include the busybox file into the zip n give it proper permission ? Thanks
Here u go @indunrise
sushuguru said:
Does it work with BORETS rom? And can i just flash it via recovery with borets rom?
Click to expand...
Click to collapse
yes you can, im using borets roms
Luq4dmin said:
@indunrise bro., i think the zip missing a file when installed.,the "busybox" file should be in /data/magisk/ since the newest magisk module uses that file to run.,but its absent.,so im keep getting error 1 when flashing any new v14.0 modules through twrp...it works fine now after i've put the "busybox" file at the proper place i've mentioned above...can u include the busybox file into the zip n give it proper permission ? Thanks
Click to expand...
Click to collapse
thanks for report bugs, if i have some time will add it soon
Luq4dmin said:
Here u go @indunrise
Click to expand...
Click to collapse
if you guys needed module on magisk download and copy this to data/magisk
I've installed this, root working and satefynet passing. How can install xposed now? I've tried with app and xposed-v87.3-sdk23-topjohnwu.zip file, neither worked.
I flash magisk on lineageos and success, work fine.
But then I switch to XOSP rom of nilac and can't flash magisk. I did the same steps.
Do you know how to make it work? Thanks in advance @indunrise
ketrooo said:
I've installed this, root working and satefynet passing. How can install xposed now? I've tried with app and xposed-v87.3-sdk23-topjohnwu.zip file, neither worked.
Click to expand...
Click to collapse
Which version of Android are you using
Sent from my Z00A using XDA Labs
(Problems I had when attempting a "dry" flash and patch:)
Just got the phone today (November 18) then attempted to flash the boot.img after patching it with magisk manager (after magisk patches the boot.img it renames it to "magisk_patched.img"). Got the usb debugging authorized after updating my adb drivers. If you want to make sure your phone is authorized you may need to run commands: adb kill-server and adb devices to check and stop/restart adb.
Anyone able to get it flashed? Getting error:
Code:
FAILED (remote: Failed to write to partition Not Found)
after running
Code:
fastboot flash boot magisk_patched.img
from fastboot, bootloader is unlocked. Running version
Code:
bramble-rd1a.200810.022.a4 (October)
I'd recommend patching up to the November update: Settings, System, System Update to the newest November update (11.0.0 (RD1A.201105.003.C1, Nov 2020).
EDIT: I'd recommend installing 15 second ADB https://forum.xda-developers.com/showthread.php?t=2588979, then overwriting it with the newest adb tools from google. 15 second ADB will add the ADB folder to your system's PATH (ENVIRONMENT VARIABLES) allowing you to run adb commands from any folder (not just the folder adb resides in).
Ok, updating to usb_driver_r13-windows.zip and platform-tools_r30.0.5-windows.zip and updating the build to the Nov RD1A.201105.003.C1 will report back lol
EDIT 2: So yeah, update your drivers and platform tools, successfully patched it:
Code:
fastboot flash boot magisk_patched.img
OUTPUT:
Code:
Sending 'boot_b' (98304 KB) OKAY [ 2.310s]
Writing 'boot_b' OKAY [ 0.480s]
Finished. Total time: 3.122s
How to flash and patch:
https://www.xda-developers.com/google-pixel-4a-how-to-unlock-bootloader-root-pass-safetynet/
Prerequisites:
Download the applicable factory image https://developers.google.com/android/images The Pixel 4A 5G is codenamed "Bramble" (Pull down your shade or look in Settings, "About phone" for Build number) and extract the boot.img from factory image, then transfer it to phone and patch it with magisk manager:
Open Magisk manager -> select ‘Install’ -> ‘Select and Patch File’ -> select your boot.img file
The patched boot image should be found inside your Download folder
After magisk patches it, mount your phone's storage, copy to your computer and flash it from fastboot. Hold down the Power and Volume Down buttons to enter fastboot.
Run command
Code:
fastboot flash boot magisk_patched.img
Platform Tools (includes ADB)
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Usb Drivers
https://dl.google.com/android/repository/usb_driver_r13-windows.zip?hl=ru
Magisk
Direct Link https://github.com/topjohnwu/Magisk/releases/download/v21.1/Magisk-v21.1.zip
Direct Link https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.3/MagiskManager-v8.0.3.apk
Magisk Releases page (in case of an update to magisk or magisk manager) https://github.com/topjohnwu/Magisk/releases/
VIPER4Android (great Digital Signal Processor)
I have been struggling with getting Viper4Android installed.
Stop-gap here:
I flashed this one, but it's distorting my external speakers and is buggy, but it does process...so BE CAREFUL. This will get you there until a more stable version is out. And the video was just taken down. All you have to do is flash it with Magisk here's a link:
https://drive.google.com/file/d/17-NTL0miBYzk4o4v26MstAL9lOPXF3GN/view?usp=sharing
AdAway (system-wide ad blocking)
tried version 5.10 with no luck, let me know if it works for you.
AdAway 4.34 working for me on Android 11.0.0 (RD1A.201105.003.C1, Nov 2020)
Here: https://f-droid.org/repo/org.adaway_40304.apk
AdAway 4.36 (haven't tested)
https://f-droid.org/repo/org.adaway_40306.apk
Make sure to enable "Systemless Hosts" in Magisk Manager before attempting to enable ad-blocking. It's under Settings (the cog/gear in the top right) in the Magisk section.
Good luck all!
Good to see someone working on this. My phone won't be here until tomorrow.
The last time I had trouble flashing, I wasn't running the canary build of Magisk.
Thanks for info and reply on other thread...long time I use this stuff haha
I'm seeing install fail from magisk when I try to patch image .I'm on latest November build
View attachment 5138555
After successfully fastboot unlocking, when I try to patch my boot.img I get the following error from Magisk:
Code:
-Device platform: arm64-v8a
- Copying image to cache
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
! Installation failed
- Repacking boot image
! Unable to repack boot image!
I first tried using the Australian factory image, labelled "11.0.0 (RD1A.201105.003.A1, Nov 2020, AU carriers)" and got the above error.
Then I tried with the Australian + Japan factory image, labelled "11.0.0 (RD1A.200810.020, Oct 2020, AU & JP carriers)" and got the same error.
What fixed it was switching to the BETA update channel in Magisk manager.
Once I changed to the BETA channel I saw in the changelog that they added support for a new boot.img format used by Pixel 5 and Pixel 4a 5G.
Anyone who ends up here from Google, swap to the beta update channel in Magisk manager .
andrew207 said:
After successfully fastboot unlocking, when I try to patch my boot.img I get the following error from Magisk:
Code:
-Device platform: arm64-v8a
- Copying image to cache
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
! Installation failed
- Repacking boot image
! Unable to repack boot image!
I first tried using the Australian factory image, labelled "11.0.0 (RD1A.201105.003.A1, Nov 2020, AU carriers)" and got the above error.
Then I tried with the Australian + Japan factory image, labelled "11.0.0 (RD1A.200810.020, Oct 2020, AU & JP carriers)" and got the same error.
What fixed it was switching to the BETA update channel in Magisk manager.
Once I changed to the BETA channel I saw in the changelog that they added support for a new boot.img format used by Pixel 5 and Pixel 4a 5G.
Anyone who ends up here from Google, swap to the beta update channel in Magisk manager .
Click to expand...
Click to collapse
Thanks for info ..I changed to beta but still having issues patching boot IMG..is this correct Magisk
{
"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"
}
Do you have a custom recovery installed? I'm trying to figure out how to install Magisk, but I can't find a custom recovery, neither TWRP nor ClockworkMod.
WhiteAsIce said:
Do you have a custom recovery installed? I'm trying to figure out how to install Magisk, but I can't find a custom recovery, neither TWRP nor ClockworkMod.
Click to expand...
Click to collapse
There's no custom recovery. You need to fastboot flash a patched boot.img as described in this guide: https://www.xda-developers.com/googl...ass-safetynet/ using the links from the OP.
Just make sure you're using the latest platform tools, download the matching factory image and change magisk manager to "beta mode" before patching the boot.img.
Android 10 and TWRP
Simma said:
There's no custom recovery. You need to fastboot flash a patched boot.img as described in this guide: https://www.xda-developers.com/googl...ass-safetynet/ using the links from the OP.
Just make sure you're using the latest platform tools, download the matching factory image and change magisk manager to "beta mode" before patching the boot.img.
Click to expand...
Click to collapse
WhiteAsIce said:
Do you have a custom recovery installed? I'm trying to figure out how to install Magisk, but I can't find a custom recovery, neither TWRP nor ClockworkMod.
Click to expand...
Click to collapse
More information on Android 10 and TWRP, though there are some devices slowly getting support for TWRP. Haven't heard clockworkmod in a long time.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
lmt1979 said:
[...]
Adaway (system-wide ad blocking)
tried version 5.10 with no luck, let me know if it works for you.
Adaway 4.34 working for me on Android 11.0.0 (RD1A.201105.003.C1, Nov 2020)
Here: https://f-droid.org/repo/org.adaway_40304.apk
Adaway 4.36 (haven't tested)
https://f-droid.org/repo/org.adaway_40306.apk
Make sure to enable "Systemless Hosts" in Magisk Manager before attempting to enable ad-blocking. It's under Settings (the cog/gear in the top right) in the Magisk section.
[...]
Click to expand...
Click to collapse
Got v5.1.0 (from F-Droid) working properly with Magisk running with systemless hostfile. Try installing BusyBox (i have v1.32.0 installed) to '/system/bin', which will be used by Adaway (instead of running native commands on root level, which apparently cause the issue).
I can't seem to flash version of Viper in Magisk, it won't let me. I've also tried every combination of the latest viper versions, and their settings, and nothing will run. Perhaps it will on the next version of Magisk. I had posted in the Magisk forum, and none of the suggestions helped.
If anyone has any luck, let us know!
mmarcz said:
I can't seem to flash version of Viper in Magisk, it won't let me. I've also tried every combination of the latest viper versions, and their settings, and nothing will run. Perhaps it will on the next version of Magisk. I had posted in the Magisk forum, and none of the suggestions helped.
If anyone has any luck, let us know!
Click to expand...
Click to collapse
The linked version worked for me after trying the magical downloaded version. I had the audio modification library and audio compatibility modules installed. I don't remember the exact sequence bit all I have now is the posted module l.
It does have some odd issues with file storage. I can save a new preset but putting my old one in the viper folder in internal storage doesn't work. I also can't rename or delete presets. I ended up having to go to /root/storage/self/primary which seems to be internal storage by another path. Pasting my presets in that viper folder worked. No idea how systemless works so can't even guess what's going on.
mmarcz said:
I can't seem to flash version of Viper in Magisk, it won't let me. I've also tried every combination of the latest viper versions, and their settings, and nothing will run. Perhaps it will on the next version of Magisk. I had posted in the Magisk forum, and none of the suggestions helped.
If anyone has any luck, let us know!
Click to expand...
Click to collapse
Just flash the https://drive.google.com/file/d/17-NTL0miBYzk4o4v26MstAL9lOPXF3GN/view?usp=sharing with Magisk. Choose "Modules" the right option on the bottom https://drive.google.com/file/d/1BWLVPtypCjCiqUSEHiRc8sCuMtjqKdY5/view?usp=sharing
lmt1979 said:
Just flash the https://drive.google.com/file/d/17-NTL0miBYzk4o4v26MstAL9lOPXF3GN/view?usp=sharing with Magisk. Choose "Modules" the right option on the bottom https://drive.google.com/file/d/1BWLVPtypCjCiqUSEHiRc8sCuMtjqKdY5/view?usp=sharing
Click to expand...
Click to collapse
Thank you!!!!! Works as advertised!!!!
This was 75% of the reason I bought a pixel!!!
I'm so happy this morning, you have no idea.
It was even processing Amazon music, which didn't work before, so far so good. I only had a chance to listen in the car for 5mins this morning.
mmarcz said:
Thank you!!!!! Works as advertised!!!!
This was 75% of the reason I bought a pixel!!!
I'm so happy this morning, you have no idea.
It was even processing Amazon music, which didn't work before, so far so good. I only had a chance to listen in the car for 5mins this morning.
Click to expand...
Click to collapse
If it stops processing, long press on the icon on the desktop, select App info, Force Stop and reopen and it'll usually start up again. I had to do this much more often on my Pixel 3 than I have on the 4A 5G.
I've followed the steps posted above. Flashed the Drive file in magisk but I'm still getting abnormal status, audio format unsupported. Tips?
VerneVerne said:
I've followed the steps posted above. Flashed the Drive file in magisk but I'm still getting abnormal status, audio format unsupported. Tips?
Click to expand...
Click to collapse
If you're sure you're rooted, some people have noted they needed to use/install Audio Modification Library and possibly Busybox. I'd attempt to clear the cache on Magisk and Viper4Android, as well.
I am on the November build and did not need Audio Modification Library, audio compatibility module (Magisk) or Busybox. I'm using Magisk 21.1 (21180) and Magisk Manager 8.0.3 (314)(14). There's a "puzzle piece" on the far right of the new Magisk Manager menu that has "Install from Storage", this is where I pointed to the Viper.zip and flashed it.
lmt1979 said:
If you're sure you're rooted, some people have noted they needed to use/install Audio Modification Library and possibly Busybox. I'd attempt to clear the cache on Magisk and Viper4Android, as well.
I am on the November build and did not need Audio Modification Library, audio compatibility module (Magisk) or Busybox. I'm using Magisk 21.1 (21180) and Magisk Manager 8.0.3 (314)(14). There's a "puzzle piece" on the far right of the new Magisk Manager menu that has "Install from Storage", this is where I pointed to the Viper.zip and flashed it.
Click to expand...
Click to collapse
Tried all the above. No luck though. I remember it being very finicky on my pixel 3. I'll try again when I'm not actually at work. Thanks for the help though
VerneVerne said:
Tried all the above. No luck though. I remember it being very finicky on my pixel 3. I'll try again when I'm not actually at work. Thanks for the help though
Click to expand...
Click to collapse
I've been glhaving issues too after it worked for awhile. Couldn't deal with no presets thing so tried different Magisks, etc with no luck and now it won't process. I'll update if I find something.
EDIT: the module at https://zackptg5.com/android.php#viper works if run in legacy mode.
EDIT AGAIN: can't save presets for some reason with above module but the ViperFX XDA Labs release before the most current one works in legacy mode https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
VerneVerne said:
I've followed the steps posted above. Flashed the Drive file in magisk but I'm still getting abnormal status, audio format unsupported. Tips?
Click to expand...
Click to collapse
You need to go into the settings for the app force stop it and then reopen it.
lmt1979 said:
You need to go into the settings for the app force stop it and then reopen it.
Click to expand...
Click to collapse
I've already tried. Started from scratch. Still unsupported status.
Edit: after reading somewhere on here that if you use legacy mode it will process. Followed all steps, set it to legacy and now it works. Thank you everyone
{
"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"
}
Polar Star Pure Edition This ROM is unified for Edge S Pro / Edge 20 Pro.
Custom ROM based on Global Stock firmware
Android 13 RETAIL_T1RA33.55-15-10-1
Android 12 RETAIL_S1RA32.41-20-16-11
Android 11 RETAIL_RRA31.Q3-19-86-6
This custom ROM uses stock kernel without modification.
>>> Preliminary requirements <<<
Only unlocked bootloader
>>> What's done <<<- Root permissions via Magisk v.26.1 (26100) Stable (Android 12 - Magisk v.25.2 (25200) Stable) ;
- Removed the restriction on writing to the system, which in Android 11 is in Read Only (r/o) mode by default, which eliminates the possibility of modifying it. In this firmware it is possible to mount the system in Read Write (r/w) mode. Encryption is preserved in this case.
- System passes SafetyNet test, device is certified;
- NFC and GPay with unlocked bootloader and Root worked!
- Cleaned and lightened the system;
- Built in additional system color accents (only Android 11);
- Updated Moto and some Google applications; Android Auto is integrated into the system;
- Removed the pill (bar) at the bottom of the desktop under the dock + made a small distance from the bottom edge of the display to the dock icons and under the keyboard. Especially good on NovaLauncher. In the Android 13 version of the firmware, this feature is implemented systematically.
- YouTube removed, because I use YouTube Vanced;
- Installed apps AdAway ad blocker, Audio Recorder, File Manager, Gallery;
- Ringtones, notifications, alarms sounds have been replaced;
- Mod Logo and Bootanimation;
- The button for calling Google Assistant is reassigned to the: Android 12 - camera shutter and use it to activate the lockscreen; Android 13 - camera launch;
- Beginning with the PStar_PE_A12-41-20-16-5-01 build, I slightly increased the volume of the ear speaker.
How can I turn down the speaker volume?
Use RootExplorer or similar app to delete the mixer_paths.xml file from /vendor/etc. Rename the mixer_paths.bak file to mixer_paths.xml. Restart the device.
Click to expand...
Click to collapse
- No Warez!
What was done in the latest update (Dec, 05, 2022) :
- Updated ROM base to stock firmware version S1RA32.41-20-16-9;
- New logo & bootanimation;
- Updated Magisk to v25.2;
- Updated applications to the latest versions at the time of ROM build;
- Updated Moto Display;
- Updated Moto Widget;
- Updated Moto Audio Recorder;
- Updated Asus File Manager;
- Completely removed Google Assistant and reassigned its button to the camera shutter;
- Removed Google location history and telemetry apps;
- Removed Turbo and Wellbeing apps;
- Slightly increased the volume of the hearing speaker.
>>> Installation Instructions <<<1. Extract the system partition images from the archive (see the Download tab) and copy them to any convenient location on your PC.
2. Reboot the device into bootloader mode and:
- If you are installing the ROM for the first time or if you want to install the firmware with all data from the previous firmware removed, then use the _flash_custom.bat executable file;
- If you want to install the ROM as an update to its previous build, then use the _update_custom.bat executable file. Then all your data and applications will be saved and the system will be updated.
3. Phone will reboot into fastbootd mode and flash installation will start automatically. When the installation is completed the phone will automatically boot into the system.
4. When the boot is complete perform the initial settings.
Spoiler: Magisk v.23001(21)
Don't update Magisk and Magisk Manager! Build Magisk (d7e7df3b) (23010) (may be and laters builts) breaks Magisk Hide and SafetyNet.
5. Do not update Magisk Manager, but install this version Magisk Manager 23001(21) in the attached files.
Then you will be asked to configure the working environment. We agree. The phone will automatically reboot after the setup is complete.
6. In the Magisk Manager Settings, disallow "Check Updates". In "Update Channel" select "Custom channel" and in the opened window indicate the link:
Code:
https://raw.githubusercontent.com/topjohnwu/magisk-files/fde0bddfc5683cc8524e323e95f6c8432fbd11da/canary.json
If you are still updating, you can rollback to a working version of Magisk using the following instructions.
-= Rollback Magisk to version 23001 (21) =-
a) Uninstall Magisk with Magisk Manager - click "Uninstall Magisk" button, select "Complete Uninstall".
b) The phone will automatically reboot at the end of the uninstall process.
c) During the rebooting process, press and hold the "volume down" button until the phone enters the fastboot mode. Connect the phone to PC with a USB cable.
d) Extract the boot_magisk.img image from the archive to the folder with the drivers adb:
Android 12 S1RA32.41-20-16_boot_magisk
Android 11 RRA31.Q3-19-86-6_boot_magisk
e) Install boot_magisk.img with the command:
Code:
fastboot flash boot boot_magisk.img
f) Boot into the system and follow steps 5-6 of the basic Instructions for installing the firmware.
>>> Notes <<<
With the update Stock base to RRAS31.Q3-19-86 the problems described below are corrected.There is a hang-up when entering the connection settings of the NFC and Bluetooth settings. Don't worry about this. You just need to wait a little while.
There is no hang-up when you enable/disable NFC and Bluetooth via the icon from the Notification bar. This happens due to uninstalling any system applications.
>>> Download <<<
Please, don't put the ROM, or links to it, on other sites without the author's permission!
Android 13 PStar_PE_A13-55-15-10-1-02
Android 12 PStar_PE_A12-41-20-16-11-02
Android 11 PStar_Pure_Edition-19-86-6-01
If you have requests, I can make the same ROM for Moto Edge 20 Pro.
Now the ROM is the same for both modifications.
ROM update S_Pro_Pure_Edition. Added ROM 20_Pro_Pure_Edition.
Updated the ROM for both devices.
What's done:
- replaced the CommandCenter_2 widget with a slightly larger one;
- updated Moto and some Google applications;
- remapped the Google Assistant button to the camera shutter button;
- removed the pill (bar) at the bottom of the desktop under the dock + made a small distance from the bottom edge of the display to the dock icons and under the keyboard. Especially good on NovaLauncher.
Thanks for the ROM.
I was wondering if widevine was L3 or L1 on this.
Updated the ROM to the base RRA31.Q3-19-50.
Since 11.10.21 the firmware is unified for both versions of the phone.
Hello, @ilia3367 do you happen to have any links where I can download your custom rom aside from mega.nz. Would really appreciate if you do, thanks.
rendmazues said:
Hello, @ilia3367 do you happen to have any links where I can download your custom rom aside from mega.nz. Would really appreciate if you do, thanks.
Click to expand...
Click to collapse
Nvm my request, I just have additional question. Does this rom supports OTA? When I searched online, they said that OTA will be downloaded thru playstore so I think it is possible to be supported if that is the case.
do you happen to have any links where I can download your custom rom aside from mega.nz.
Click to expand...
Click to collapse
No. I don't have any free space on my other file stores.
rendmazues said:
Does this rom supports OTA?
Click to expand...
Click to collapse
No. This ROM only supports its own updates, which will be released as Stock firmware updates become available.
Hello
Can you add "Task lock" function in recent apps screen?
I want to keep apps I often use in task list, even if I push "all clear".
Attention users of Custom ROM or users of Root Magisk on Stock firmware!
Starting with version Magisk (d7e7df3b) (23010) the structure of this utility has changed - now Zygisk is used, but Magisk Hide was removed from the utility, SafetyNet test fails.
Read more in the Magisk thread.
For whom these features are important, but accidentally updated Magisk, I offer instructions in the first post of this thread.
ilia3367 said:
Attention users of Custom ROM or users of Root Magisk on Stock firmware!
Starting with version Magisk (d7e7df3b) (23010) the structure of this utility has changed - now Zygisk is used, but Magisk Hide was removed from the utility, SafetyNet test fails.
Read more in the Magisk thread.
For whom these features are important, but accidentally updated Magisk, I offer instructions in the first post of this thread.
Click to expand...
Click to collapse
Thanks for the tut on how to downgrade, I accidentally updated mine. I'll do the downgrading later.
ilia3367 said:
If you have requests, I can make the same ROM for Moto Edge 20 Pro.
Click to expand...
Click to collapse
Yeah Sir, We need a custom rom for edge 20 pro and also how to root this mobile.
hello I just did the steps to be root, I succeeded. install root explore and link2sd to be able to remove apps they give me per, isos, but when I want to uninstall I can't.
root explore does not let me change to r / w and uninstallation fails and link2sd removes but reboot and this is the app.
tarshar01 said:
Yeah Sir, We need a custom rom for edge 20 pro and also how to root this mobile.
Click to expand...
Click to collapse
Now the ROM is the same for both modifications.
Naza1879 said:
root explore does not let me change to r / w and uninstallation fails
Click to expand...
Click to collapse
Are you getting Root on the Stock firmware or on this Custom ROM?
Did Root Explorer ask Magisk for permission the first time it started up?
hello, everyone! I want to know this ROM's back main camera whether support longer than 1/4s exposure by Gcam?
Now I'm using Chinese Rom. It has a serious touch screen issue, and doesn't support longer than 1/4s exposure by Gcam.
Sir, Can you make a video on how to install this on moto edge 20 pro, On YouTube and share link
Updated the ROM to the base RRA31.Q3-19-50-1 - - - PStar_Pure_Edition-19-50-1-02