If you break, blow up, brick, or neutralize your device in any way, shape, or form, I am not responsible for the damage
Install ARISE Magnum OPUS on android 8.0 with Magisk
Hi XDA, I have recently put a thread online about installing ARISE deuternomy on magisk. I have installed magnum OPUS on magisk and it is relatively easy! So here it is
Prerequisites:
This zip file contains all of the resources you'll need
In case you are curious what is inside the zip
Magisk v14.2(14.3 does not work due to incompatibility)
ARISE magnum OPUS zip (latest)
ARISE magisk module by zackptg5 and shadowghoster
Magisk permissive script
CHDLOC stereo mod (if you want it)
Steps:
Root using Magisk, follow Homeboy76's guide. Post #9
Extract the zip file you downloaded
Open Magisk manager and install the following modules...
Busybox for android NDK (found in download section)
Universal deep buffer remover (also found in download section)
SE linux permissive module (in zip file)
Reboot (if it does not boot properly, hold vol down and power and reboot, it works 2nd time)
Customize ARISE customize.prop (here is a video on how to do this)
Reboot to TWRP recovery
mount system, data, vendor from mount menu
Flash Magnum OPUS zip
Flash ARISE magisk module
Reboot
DONE!!! Enjoy your new sound experience!
tip: if you want to install the stereo speakers mod by chdloc, here is the link...
I would like to thank the ARISE team, zackptg5, shadowghoster, TopJohnWu, osm0sis, ahiron, and Jman420 for making this possible!
Hi brother
I am very interested in your guide for arise magnum opus on rom oreo.
on rom nougat I've always been successful using supersu.
in step 1: do you need to install magisk root using the zip you posted?
from twrp initially?
cuciu70 said:
Hi brother
I am very interested in your guide for arise magnum opus on rom oreo.
on rom nougat I've always been successful using supersu.
in step 1: do you need to install magisk root using the zip you posted?
from twrp initially?
Click to expand...
Click to collapse
Not anymore, the recent update made it so that magisk v 14.3+ works.
I apologize for my bad english, I use google translator. I've always used supersu, magisk I know him very little. anyway: do you need to install the new magisk 14.3 from twrp to root the phone? I have a redmi note 4 snapdragon 625 with bootloader unlocked. I'm trying various ROM hours or on this phone. I do not understand the steps of your guide.
Has anyone tried this on 8.1 DP2?
airmaxx23 said:
Has anyone tried this on 8.1 DP2?
Click to expand...
Click to collapse
Until now found no way to make it work on dp2. Still looking for a solution. Maybe we have to wait for official sources from 8.1.
The permissive module fails to install for me.
dirac control service has stopped. :\
Does this work for 8.1.0 also?
universal deep buffer remover was gone for now, is that ok?
Related
The Magisk Universal Systemless Interface by XDA Recognized Developer @topjohnwu has received an update that bumps it up to version 7. There are a bunch of notable changes that follow in the changelog:
Fully open source
Remove supolicy dependency, use my own sepolicy-injection
Run everything in its own selinux domain, should fix all selinux issues
Add Note 7 stock kernel hex patches
Add support to install Magisk in Manager
Add support for image merging for module flashing in Manager
Add root helpers for SuperSU auto module-ize and auto upgrading legacy phh superuser
New paths to toggle busybox, and support all root solutions
Remove root management API; both SuperSU and phh has their own superior solutions
Downloads:
1)Official MM OOS STOCK 3.1.3 - https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
2)Official MM H2OS Stock 2.0 - http://download.h2os.com/oneplus_x/mp/OnePlusH2OS_14_OTA_001_all_201609270726_5aa42273def7431b.zip
3) Use this recovery to Flash Magisk (TWRP by Bluespark) - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4)Magisk Manager.apk - http://forum.xda-developers.com/attachment.php?attachmentid=3893660&d=1475527472
5)Latest Magisk Zip File - http://forum.xda-developers.com/attachment.php?attachmentid=3893659&d=1475527472
6)Systemless Superuser (use this Systemless superuser) - http://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921
7)Magisk Uninstaller (if anything goes wrong) - http://forum.xda-developers.com/attachment.php?attachmentid=3893658&d=1475527472
Before Flashing:
1) If you are already on MM with stock recovery and no root,then wipe your data and cache,flash full MM rom pack, flash provided TWRP and follow the instruction below
2)If you are in MM with rooted system,do wipe data and cache,flash full rom pack, flash twrp and follow the instruction
MOST IMPORTANT:
BEFORE FLASHING MAGISK,YOU NEED TO HAVE UNMODIFIED SYSTEM
USE TWRP TO FLASH MAGISK
FLASHING INSTRUCTION:
1)Flash your rom pack
2)Flash magisk zip file
3)Flash systemless root
4)Flash systemless xposed
Ooh laa... Got unmodified system with root access
what is this used for?
meraj99 said:
what is this used for?
Click to expand...
Click to collapse
Systemless Benefits
OTA:
The system partition will not be modified or mount r/w, thus your Android devices are capable of applying OTA updates even if ur mobile s rooted
Safety Net:
Android Pay is confirmed working!
With Magisk 11.5 came many bug fixes including for devices that have a separate vendor partition. We can now use Viper4Android systemlessly with the magisk module. This will not affect the lockscreen visualizer or the audio fx tile visualizer. So we can have viper4android without sacrificing these features.
1. Install magisk 11.5 in twrp recovery, reboot to system.
2. Install latest magisk manager from playstore or apk
3. Open magisk manager and select "downloads" option in menu pane.
4. Search for "Viper4Android FX" and click the download button then click install.
5. Reboot.
6. Open magisk manager and select "downloads" again.
7. Search for "Viper4Android FX" under "Installed."
8. Tap the tile (not the download arrow)
9. Click the link that says "download the latest apk here."
10. Install apk you just downloaded.
11. Enjoy Viper4Android systemlessly on Redmi Note 3.
Links:
Magisk 11.5 - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Viper4android FX Systemless apk - https://www.androidfilehost.com/?fid=312978532265364193
installed and working, thank you any recommended settings for viper?
Barnir said:
installed and working, thank you any recommended settings for viper?
Click to expand...
Click to collapse
It all depends on what headphones you are using and what quality the music is, i.e. lossy or lossless etc. Just play with the settings and find something you like (our ears aren't all the same).
Hey buddy,
I'm on MIUI global stable 8.1
I want to have systemless root nd xposed. Could you please explain me with corrct procedure to follow. Have unlocked bootloader nd got custom recovery too
hasan4791 said:
Hey buddy,
I'm on MIUI global stable 8.1
I want to have systemless root nd xposed. Could you please explain me with corrct procedure to follow. Have unlocked bootloader nd got custom recovery too
Click to expand...
Click to collapse
I went directly to aosp based roms as soon as I got this phone. Sorry I can't help.
It shows driver installation failed due to busybox. But I have installed the recommended Busybox.. Please help
i know magisk is to hide root. but i didnt know about it has viper capability. now my speaker sound louder. thanks.
Thank you for the guide, followed it step by step and it works perfectly!
I just had a question
I am on XenonHD so if I flash an update, I only have to flash magisk again right? Or must I do something special for V4A
UPDATE 1-07-18, This guide is now OUTDATED, for android 8.1, please reference this guide https://forum.xda-developers.com/pixel-xl/how-to/guide-ultimate-audio-battery-guide-t3727124#post75100735
Install ARISE on android 8.0 oreo passing safetynet
I am not responsible if you break or damage your device in any wayHi XDA, this is how to install ARISE on google pixel/XL using Magisk
Safetynet is passed on this installation, V4A drivers are working
Prerequisites:
https://androidfilehost.com/?fid=457095661767141554"]Arise aroma installer
Magisk v14 or greater
Arise magisk compatibility module
SE linux permissive Magisk module
Steps
Root your device using Magisk using HOMEBOY76's Guide step 9
Open Magisk Manager and install osm0sis's Busybox. It should be in the downloads repo
Reboot
Go into TWRP
Install the SE Linux permissive module zip (installing Magisk modules works on TWRP)
Install ARISE aroma (install any audio mods you want V4A 2.5.0.5 is recommended) (ICE sound breaks Android O's speakers, so skip all of the ICE sound profiles)
Make sure you skip the SE Linux permissive script, remove Deep audio buffer and repair SDCARD permissions
Install the ARISE Magisk module zip
Reboot and enjoy a better sound quality
I want to thank TopJohnWu, Jamesoolee, HOMEBOY76, the ARISE team, Jman420, Zack, and Ghost for making this possible
Great! Can confirm. V4a working with magisk! Had to install the permissive script through magisk. In twrp gave me error mounting system.
Check out my ultimate audio guide if you want stereo speakers
kingbri said:
Check out my ultimate audio guide if you want stereo speakers
Click to expand...
Click to collapse
Link?
Donric13 said:
Link?
Click to expand...
Click to collapse
oops, here is the link https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-make-pixel-pixel-xl-t3692855
Has anyone experienced a lost of sound system wide when using custom kernel, Gov, and I/O sched?
Thanks for this. Do you know if the Magisk permissive script passes safety net?
If not, can it be toggled easily?
Thanks!
kingbri said:
Check out my ultimate audio guide if you want stereo speakers
Click to expand...
Click to collapse
For magisk systemless root and passing safetynet?
Donric13 said:
Had to install the permissive script through magisk. In twrp gave me error mounting system.
Click to expand...
Click to collapse
Same issue here using latest TWRP.
djide said:
For magisk systemless root and passing safetynet?
Click to expand...
Click to collapse
Yes. Safety net checker shows green. So it should work (i don't use it).
Screenshot....
The permissive module does pass safetynet, mine is intact
kingbri said:
The permissive module does pass safetynet, mine is intact
Click to expand...
Click to collapse
Great, thanks!
Does this install still require you to delete apps from system/app in order to get to at least 400mb of free space?
Sent from my Pixel XL using XDA-Developers Legacy app
Donric13 said:
Great! Can confirm. V4a working with magisk! Had to install the permissive script through magisk. In twrp gave me error mounting system.
Click to expand...
Click to collapse
Followed the steps and installed v4a but its not working. No sound difference and the status says it's abnormal.... Any help would be appreciated
djide said:
Followed the steps and installed v4a but its not working. No sound difference and the status says it's abnormal.... Any help would be appreciated
Click to expand...
Click to collapse
Before installation i deleted some apps with filemanager in twrp (gmail, chrome, hangout, talkback) to get more system space. Then i followed exactly the steps of kingbri. Must say i only installed minimum of arise mod (core and deep buffer remove, nothing else). Before installation i dirty flashed stock image and deinstalled supersu.
Donric13 said:
Before installation i deleted some apps with filemanager in twrp (gmail, chrome, hangout, talkback) to get more system space. Then i followed exactly the steps of kingbri. Must say i only installed minimum of arise mod (core and deep buffer remove, nothing else). Before installation i dirty flashed stock image and deinstalled supersu.
Click to expand...
Click to collapse
I am using Magisk not supersu but still that shouldn't matter. Oh well
I have a ton of system space, so I dunno
djide said:
I am using Magisk not supersu but still that shouldn't matter. Oh well
Click to expand...
Click to collapse
Before i had supersu. That is why i deinstalled supersu before installing magisk.... With supersu v4a was only working in full permissive mode.... Thought maybe you took the same way...
If you are having any problems, feel free to dm me. I will try to solve them (not always a guaranteed fix)
Hi guys, just some hours ago i got into a problem (at least for me).
I switched today from LineageOs 14.1 to AospExtended Oreo and since i can't use LineageOs root and i don't trust SuperSu anymore (because CodingCode), the only root available for me is Magisk.
Now i have flashed Magisk and set up some modules and the root itself is working, but i cannot delete system apps and modify /system in general. I haven't faced this problem in LineageOs (also with magisk).
And yes, i have tried "reboot disemmcwp" and it didn't work.
I am on A2017G, TWRP 3.2.1.7 (Nfound's build).
Thanks in advance for the answers.
EDIT: I FOUND A SOLUTION (KIND OF)
The situation, however turned out a bit different. At first i thought it was magisk messing with zte's system write protection, but it turned out that the culprit was actually SdMaid. Yep. It has a bug, so when you install a module that REPLACES a system app, like Vanced Youtube, it cannot recognize all the links and tricks that Magisk does and screws up everything, showing /system as read only and if you try to uninstall any system app with its inbuilt app manager, it makes Android crash.
There are 2 possible causes:
1. Magisk
2. You're on the B35 bootstack
I had your issue with Magisk before. Personally, I still think SuperSU can be trusted. But if you're willing to try it again, you should know that it will cause a bootloop with Oreo. It's because of the dtb patching. But I figured out how to make it work anyway. Download the SuperSU 2.72 SR5 zip. Unzip the file into a folder. Then open /meta-inf/com/google/android/update-binary in a text editor. Search for all instances of dtb, and change true to false. Save the file, and create a new zip. Then get the Aroma SuperSU Config zip. In TWRP, flash the config zip first. Select sbin mode on the first page, on 2nd and 3rd pages just use default options or whatever you want. Then flash your modded SuperSU zip. You should be able to boot. All works fine for me.
The 2nd possibility is that you are using the B35 bootstack. There is an issue with it where root appears to work but system partition can't be changed no matter what you do. You need to find a B32 bootstack zip and flash that instead.
I personally am using AOSP Extended Oreo, with B32 bootstack and SuperSU, all is fine so far. I can modify system partition too. If you need more clarification then just ask.
Good luck!
I've used the "disemmcwp" option in nfounds twrp options and it worked for me.
AnonVendetta said:
There are 2 possible causes:
1. Magisk
2. You're on the B35 bootstack
Click to expand...
Click to collapse
Wow, thanks for the fast answer!
I am currently using the B32 bootstack (also from Nfound), so the culprit must be Magisk (unfortunately).
I think i will try your method in the next days, meanwhile i will post this in the Magisk thread, maybe they have some clues about this.
Sent from my ZTE Axon 7 using XDA Labs
Modded SuperSU zip is attached.....
Modded B32 bootstack:
https://forum.xda-developers.com/attachment.php?attachmentid=4427264&d=1519249436
Aroma SuperSU config:
http://download.chainfire.eu/1121/SuperSU/AROMA-SuperSUConfig-v1.00.zip
Magisk uninstaller:
http://tiny.cc/latestuninstaller
Flash Magisk uninstaller, B32 bootstack, Aroma SuperSU config, then modded SuperSU, in that order. Go to /system/xbin and delete the su file, it will interfere with SuperSU. Wipe cache/dalvik cache and reboot. And run the "reboot disemmcwp" (as root, or with ADB), for good measure. You should be able to modify /system now.
Thanks, really.
Sent from my ZTE Axon 7 using XDA Labs
Ok, i did exactly what you said, but i ended up with a bootloop :/
But after dirty flashing my rom and Magisk and reboot disemmcwp in twrp, guess what? I got complete access to /system. That's wizardry my friend.
wannaskoo said:
Ok, i did exactly what you said, but i ended up with a bootloop :/
But after dirty flashing my rom and Magisk and reboot disemmcwp in twrp, guess what? I got complete access to /system.
Click to expand...
Click to collapse
Just for the sake of knowledge i should report that, after many tries, i discovered something interesting (at least for me). Magisk IS actually messing with system write protection, but only if you have any modules enabled. I have Ainur Sauron, Deep_buffer remover, Dolby Atmos for Oreo, AudioModLib, Youtube Vanced and Syspatch as Magisk modules, and i can't touch system in any way after booting into AEX, but if i enable Magisk Core mode and reboot i get complete access to /system.
I hope this thread will be useful for someone having problems with Magisk, because it is a great tool for modding and rooting, but i do really care to have /system access, that's the point of custom roms (for me).
Sent from my ZTE Axon 7 using XDA Labs
wannaskoo said:
Just for the sake of knowledge i should report that, after many tries, i discovered something interesting (at least for me). Magisk IS actually messing with system write protection, but only if you have any modules enabled. I have Ainur Sauron, Deep_buffer remover, Dolby Atmos for Oreo, AudioModLib, Youtube Vanced and Syspatch as Magisk modules, and i can't touch system in any way after booting into AEX, but if i enable Magisk Core mode and reboot i get complete access to /system.
I hope this thread will be useful for someone having problems with Magisk, because it is a great tool for modding and rooting, but i do really care to have /system access, that's the point of custom roms (for me).
Sent from my ZTE Axon 7 using XDA Labs
Click to expand...
Click to collapse
Thanks. I would recommend you report this on the Magisk Thread
Yep, i will do that.
Sent from my ZTE Axon 7 using XDA Labs
Hello Everyone.
The first beta version of OxygenOS 12 was released, and as usual I ventured to install V4A, unfortunately I was not successful.
I tried several ways to make it work. I believe that I'm not getting it because of the Dolby Atmos that already comes in the Rom system. If anyone has a solution for this it will be of great help. thank you for the attention.
[GUIDE] Viper4Android Driver Installation Error Fixed on A11/12/12.1 AOSP/OOS/COS ROMs
1. Method 2. Method Use Latest Unofficial Magisk Delta (if only 3. method didn't work.) and continue with 3. Step. 3. Method Found this thread. First install V4A apk, let it install the module and reboot once and then, basically copy these...
forum.xda-developers.com