Related
So I wont say I tried everything but have been reading and trying solutions and they havent worked for me. Maybe someone can point me in a different right direction. So far I clean installed 3.2.8(twice btw), I'm fastbooting into twrp 3.0.2-1, flashed supersu 2.78 SR4 and flashed xposed framework v87.
Sometimes xposed framework v87 flashes in twrp and when I open xposed installer it says xposed framework is not installed. I attempt to then unintstall and try again and sometimes it fails in twrp with this message "cp: cant create '/system/xposed.prop':Read-only file system". I attached a screenshot. I'm also running xposed installer 3.1.1, also tried 3.0.1 by dvdandroid. Any suggestions?
Have you tried Magisk and Systemless Xposed?
mznk said:
Have you tried Magisk and Systemless Xposed?
Click to expand...
Click to collapse
Are you asking if I tried it in the past on my onplus3? I didnt see anyone trying it now with 3.2.8 so I didnt think of it.
SysAdmNj said:
Are you asking if I tried it in the past on my onplus3? I didnt see anyone trying it now with 3.2.8 so I didnt think of it.
Click to expand...
Click to collapse
I'm using it on 3.2.8 currently and all works well so far.
Here's how I did it: Clean flashed 3.2.8 using sideload with official recovery, then booted twrp-3.0.2-1 (from twrp.me), flashed Magisk v9 and flashed the phh-superuser. After booting into android, installed phh's SuperUser from Playstore, and installed Magisk Manager, then installed Xposed systemless arm64 sdk23 using the inbuilt downloader (or use the zip on the thread).
mznk said:
I'm using it on 3.2.8 currently and all works well so far.
Here's how I did it: Clean flashed 3.2.8 using sideload with official recovery, then booted twrp-3.0.2-1 (from twrp.me), flashed Magisk v9 and flashed the phh-superuser. After booting into android, installed phh's SuperUser from Playstore, and installed Magisk Manager, then installed Xposed systemless arm64 sdk23 using the inbuilt downloader (or use the zip on the thread).
Click to expand...
Click to collapse
Thanks it all worked and went green except when I tried to download the systeless arm64 sdk23 from within magisk manager. I ended using a test1 version and it went through. Now I wasnt even planning on using magisk but how are you using magisk? When I used it before it was for android pay but I thought that all broke.
Installing xposed breaks SafetyNet anyways and I have no use of Android pay or Pokemon Go etc.
But, with magisk I can install and mod system files without making changes in the system partition like dpi, Viper, SystemUI mods etc. I really like it for the ease of that.
I have installed Xposed on 3.2.8 with a success from the beginning. Steps I've taken:
1. Dirty flashing full zip OOS 3.2.8.
2. Flashing systemless SuperSU from Chainfire (you have to:
Code:
echo SYSTEMLESS=true >> /data/.supersu
for systemless).
3. Flashing Xposed v87-test version, which now disappeared from dl-xda.xposed.info/framework/sdk23/arm64/
4. Flashing ElementalX 0.28.
I was upgrading from 3.2.6.
mznk said:
I'm using it on 3.2.8 currently and all works well so far.
Here's how I did it: Clean flashed 3.2.8 using sideload with official recovery, then booted twrp-3.0.2-1 (from twrp.me), flashed Magisk v9 and flashed the phh-superuser. After booting into android, installed phh's SuperUser from Playstore, and installed Magisk Manager, then installed Xposed systemless arm64 sdk23 using the inbuilt downloader (or use the zip on the thread).
Click to expand...
Click to collapse
OxygenOS 3.2.7 with v87.1 Magisk version installed. Got stuck at boot animation when dirty flashing to oos 3.2.8. Any ideas? Is there compatibility problem with xposed modules?
I would use a newer recovery, twrp-3.0.2-23-oneplus3 is the latest and I've had zero issues with it. I uploaded it to drive vs searching for it. Next, as stated, install Xposed via the app, version 3.0.1 by dvdandroid is what I'm using and after selecting arm64 api23 , granting root, it installs, reboot and done.
Hi,
I currently have my HTC One M9 with the following installed:
TWRP v3.0.2-0
Magisk v10.2
Magisk Manager v4.1
phh's SuperUser 2.0 [Beta 11]
And it's running: Android 6.0 (Marshmallow)
Now, I've received the OTA update notification for Android 7.0 (Nougat) - 4.14.401.7. I'm assuming that if I do the update, it will overwrite both my boot and recovery partitions, and therefore my phone will return to a stock status.
My question now is: Has anyone tried installing TWRP + Magisk v11.1 on this phone, running Android 7.0 (Nougat) - 4.14.401.7 (Stock)?? And, has it worked fine??
phen0m2016 said:
Hi,
I currently have my HTC One M9 with the following installed:
TWRP v3.0.2-0
Magisk v10.2
Magisk Manager v4.1
phh's SuperUser 2.0 [Beta 11]
And it's running: Android 6.0 (Marshmallow)
Now, I've received the OTA update notification for Android 7.0 (Nougat) - 4.14.401.7. I'm assuming that if I do the update, it will overwrite both my boot and recovery partitions, and therefore my phone will return to a stock status.
My question now is: Has anyone tried installing TWRP + Magisk v11.1 on this phone, running Android 7.0 (Nougat) - 4.14.401.7 (Stock)?? And, has it worked fine??
Click to expand...
Click to collapse
I have the developer edition (4.23.617.1) but Nougat works fine with TWRP (3.0.3-0_unofficial) and Magisk 11.1. The new MagiskSU has worked fine as a root solution and within Magisk Hide - but some users have reported that it is necessary to disable/enable Magisk Hide, or even reboot to pass a SafetyNet check. For me, disabling & re-enabling after install worked fine - and was necessary only immediately after install.
computerslayer said:
I have the developer edition (4.23.617.1) but Nougat works fine with TWRP (3.0.3-0_unofficial) and Magisk 11.1. The new MagiskSU has worked fine as a root solution and within Magisk Hide - but some users have reported that it is necessary to disable/enable Magisk Hide, or even reboot to pass a SafetyNet check. For me, disabling & re-enabling after install worked fine - and was necessary only immediately after install.
Click to expand...
Click to collapse
Hey computerslayer. Thanks for the reply!
So in order to do a clean install of the Nougat Update (4.14.401.7) + Magisk v11.1, I should do the following:
1.- Uninstall phh's SuperUser using Magisk Manager > Modules
2.- Unistall Magisk Manager using TWRP > Magisk Uninstaller
*.- (Unistalling TWRP wouldn't be necessary as the Update rewrites the Recovery Partition)
3.- Apply the Nougat Update
4.- Reinstall TWRP
5.- Reinstall Magisk
6.- Finished
Is this procedure OK??
phen0m2016 said:
Hey computerslayer. Thanks for the reply!
So in order to do a clean install of the Nougat Update (4.14.401.7) + Magisk v11.1, I should do the following:
1.- Uninstall phh's SuperUser using Magisk Manager > Modules
2.- Unistall Magisk Manager using TWRP > Magisk Uninstaller
*.- (Unistalling TWRP wouldn't be necessary as the Update rewrites the Recovery Partition)
3.- Apply the Nougat Update
4.- Reinstall TWRP
5.- Reinstall Magisk
6.- Finished
Is this procedure OK??
Click to expand...
Click to collapse
Honestly, I'm not sure. I don't know if it is possible to upgrade between Android versions via OTA with TWRP installed - I vaguely remember some limitations on OTAs and TWRP. Best to check the official TWRP thread and the readme thread to be sure.
Similarly, I'm not sure about a clean install of Magisk. I've only been using it for about a month so I'm not confident in offering advice about uninstalling - especially since giving bad advice could end up with you not passing SafetyNet because I missed some basic step. I recommend checking out the Magisk forums.
I'm sorry I can't be of more help.
I tried to install magisk v12 zip but it always fails but says to install supersu soon after. I did that but when i installed magisk manager it said there's no MagiskSU installed and Safety net did not pass as well! Then i tried to uninstall supersu and magisk and flash magisk v12 again but same result again. I tried find how to install MagiskSU online but i can't find any thread about this issue. My aim of installing Magisk is to use MagiskHide for snapchat. Can someone help me pls.:crying:
Are you on SuperSU at the moment?
You will need to unroot using the SuperSU app (That's what I did) before flashing magisk zip.
Secondly, I had trouble with SuperSU + Magisk so I used phh superuser to get it working. I also needed magisk to hide root from snapchat and another banking app and I am able to do so easily.
So, in short,
1. Uninstall SuperSU
2. Flash magisk zip in recovery
3. Flash phh superuser in recovery (People say its optional but I do it anyway)
4. Reboot and benefit
Can you send me a link to download the phh superuser file you used please. When you say uninstall do you mean full unroot? What did you use to uninstall supersu? https://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
Magisk v12 will auto install root when no root is detected, so u can just clean flash ur rom and install magisk v12 after it, it will auto root
@mharis05 nowadays Phh's Superuser is not "optional": it's unsupported and replaced by the integrated MagiskSU since Magisk v10: look at the official thread, it's declared obsolete.
It would get device in trouble, even if MagiskSU is disabled.
@Bradl79 neither the clean flash is a right way, because:
1) If you're intending a system wipe, it's not resolutive because Magisk is OTA-survival.
2) If you're intending a data wipe, it's an useless waste of time... and data!
You have to run the following zip files: Magisk official uninstaller and UnSU to be sure you've not rooted device in any way.
Then to stay quiet, do a Cache and Dalvik/ART wipe.
At this point, try to reflash Magisk.
I tried that but time and time again when i try to uninstall that SUPERSU it says to flash default boot.img to complete the process. AND Installation "FAILED" Flash Supersu immediately. I did that but still no magiskSU.
At this point try to wipe system and cache/ART, then reflash OOS.
After doing that, go with Magisk.
How to install Magisk & Xposed? I keep getting bootloops.. "no digest file found"
So I have a Pixel XL, stock, nougat 7.1.2 (Aug NHGE47Q).
I have tried the following steps:
Boot TWRP 3.1.1-1
Flash TWRP 3.1.1-1
Flash Elemental 7.1.2 kernel
Flash newest Magisk 14.5 beta (since 14.0 doesn't support pixel, right?)
Flash TWRP 3.1.1-1
What am I doing wrong?
I tried it a few times and no good. I did notice it says something about "no digest file found", which I assume is the problem.. ? I tried a combination of things like with and without wiping cache/dalvik. Or not flashing TWRP at the end. I search around and couldn't find updated instructions on this process. Help will be appreciated!
P.S. Also, if I update to Oreo, I can't get Xposed, right? (as in the systemless version via Magisk) because that's the only reason why I haven't updated yet.
smithilberry said:
So I have a Pixel XL, stock, nougat 7.1.2 (Aug NHGE47Q).
I have tried the following steps:
Boot TWRP 3.1.1-1
Flash TWRP 3.1.1-1
Flash Elemental 7.1.2 kernel
Flash newest Magisk 14.5 beta (since 14.0 doesn't support pixel, right?)
Flash TWRP 3.1.1-1
What am I doing wrong?
I tried it a few times and no good. I did notice it says something about "no digest file found", which I assume is the problem.. ? I tried a combination of things like with and without wiping cache/dalvik. Or not flashing TWRP at the end. I search around and couldn't find updated instructions on this process. Help will be appreciated!
P.S. Also, if I update to Oreo, I can't get Xposed, right? (as in the systemless version via Magisk) because that's the only reason why I haven't updated yet.
Click to expand...
Click to collapse
I'm not sure about Oreo I think you can but you can't get certain modules or things like Xposed but double check that cuz I'm not sure
Secondly if you wanna flash 14.2 or 14.3 at the bottom of the magisk post where you download it will have the different versions to choose from any version after 14.0 supports the pixel
try flashing magisk by itself and see if that helps I know when I flash it with anything else it just doesn't show up and doesn't work but if you want when it bootloops flash the uninstaller and flash your boot image and that will fix the bootloop but do it again copy the log from twrp and put it on your computer and upload it here it will say exactly where it fails and what's wrong with it so we can help better
smithilberry said:
So I have a Pixel XL, stock, nougat 7.1.2 (Aug NHGE47Q).
I have tried the following steps:
Boot TWRP 3.1.1-1
Flash TWRP 3.1.1-1
Flash Elemental 7.1.2 kernel
Flash newest Magisk 14.5 beta (since 14.0 doesn't support pixel, right?)
Flash TWRP 3.1.1-1
What am I doing wrong?
I tried it a few times and no good. I did notice it says something about "no digest file found", which I assume is the problem.. ? I tried a combination of things like with and without wiping cache/dalvik. Or not flashing TWRP at the end. I search around and couldn't find updated instructions on this process. Help will be appreciated!
P.S. Also, if I update to Oreo, I can't get Xposed, right? (as in the systemless version via Magisk) because that's the only reason why I haven't updated yet.
Click to expand...
Click to collapse
According to elementalx.org/devices/pixel/ the right elemental kernel is 1.15.
I've done this exact process too and ran into many issues, I would recommend as follows, I've had a lot of success with this. I got Magisk working under 14.2 , twrp 3.1.1-1 , and elemental 1.15. I could not get any of them working correctly with any other versions or in any other order - this worked for me.
reflash stock with flash_all and factory reset
fastboot boot twrp 3.1.1-1
check "never show" and swipe
adb sideload twrp-3.1.1-1.zip
adb sideload VerifiedBootSigner-v8.zip
reboot recovery
sideload again
adb sideload your new ROM here if you want that
adb sideload twrp-3.1.1-1 again, had to do this for PureNexus, cause recovery was overwritten
adb sideload VerifiedBootSigner-v8.zip again
reboot recovery
adb sideload ElementalX-P-1.15.zip
reboot recovery (might not be necessary)
adb sideload Magisk-v14.2(1420).zip - I got this from the Arise Aroma installer package in another thread
adb sideload VerifiedBootSigner-v8.zip again
reboot system, enable systemless hosts and magisk hide on google services framework and play store. magisk hide only works with a kernel that supports it so if your elemental is working you should be fine.
reboot again, then install busybox, I used stericsons from play store. I also installed the selinux switcher for permissive mode. I installed these to get Arise / Viper to work and I think they are required for xposed too.
Magisk modules should work from there, including the xposed installer, but xposed will cause safetynet to fail. I could not get magisk modules to work with 14.3, have not tested other versions, but 14.2 worked.
I did not let twrp install it's apk from recovery mode, or let magisk download it's update, I downloaded both APKs separately.
I remember having many issues with the order of install for magisk versus elemental. I'm pretty sure what worked for me is elemental, then magisk as I put here. but if you run into issues it might have to be magisk then elemental.
blanken_ship said:
According to elementalx.org/devices/pixel/ the right elemental kernel is 1.15.
I've done this exact process too and ran into many issues, I would recommend as follows, I've had a lot of success with this. I got Magisk working under 14.2 , twrp 3.1.1-1 , and elemental 1.15. I could not get any of them working correctly with any other versions or in any other order - this worked for me.
reflash stock with flash_all and factory reset
fastboot boot twrp 3.1.1-1
check "never show" and swipe
adb sideload twrp-3.1.1-1.zip
adb sideload VerifiedBootSigner-v8.zip
reboot recovery
sideload again
adb sideload your new ROM here if you want that
adb sideload twrp-3.1.1-1 again, had to do this for PureNexus, cause recovery was overwritten
adb sideload VerifiedBootSigner-v8.zip again
reboot recovery
adb sideload ElementalX-P-1.15.zip
reboot recovery (might not be necessary)
adb sideload Magisk-v14.2(1420).zip - I got this from the Arise Aroma installer package in another thread
adb sideload VerifiedBootSigner-v8.zip again
reboot system, enable systemless hosts and magisk hide on google services framework and play store. magisk hide only works with a kernel that supports it so if your elemental is working you should be fine.
reboot again, then install busybox, I used stericsons from play store. I also installed the selinux switcher for permissive mode. I installed these to get Arise / Viper to work and I think they are required for xposed too.
Magisk modules should work from there, including the xposed installer, but xposed will cause safetynet to fail. I could not get magisk modules to work with 14.3, have not tested other versions, but 14.2 worked.
I did not let twrp install it's apk from recovery mode, or let magisk download it's update, I downloaded both APKs separately.
I remember having many issues with the order of install for magisk versus elemental. I'm pretty sure what worked for me is elemental, then magisk as I put here. but if you run into issues it might have to be magisk then elemental.
Click to expand...
Click to collapse
Thanks for the directions!
However, before I try this, I have one question... what is "VerifiedBootSigner-v8.zip"?
After searching, I see a bunch of information on the May security patch, but nothing talking about the August security patch (which is what I'm on). That being said, does it still apply?
You don't need Xposed, magisk has plenty of modules, but after rooting, flash the verified boot signer to allow for stock boot. It patches the boot image. Android 8 methods fixed this issue
Here is how you flash a kernel with the stupid 2 slots LOL...
Rom installed and ALREADY BOOTED INTO the OS That rom.
Reboot to TWRP 3.2.1-0
Flash Kernel and Flash TWRP 3.2.1-0.ZIP followed by rebooting recovery (i usually hit reboot system hold volume down until i get to bootloader and then choose recovery (reboot recovery doesnt always work))
Flash Magisk 15.0 or 15.1 on Oreo and i believe 14.3 and down will work better for Nougat.
Reboot buddy!!! All is good in the world.
Mikkey81 said:
Here is how you flash a kernel with the stupid 2 slots LOL...
Rom installed and ALREADY BOOTED INTO the OS That rom.
Reboot to TWRP 3.2.1-0
Flash Kernel and Flash TWRP 3.2.1-0.ZIP followed by rebooting recovery (i usually hit reboot system hold volume down until i get to bootloader and then choose recovery (reboot recovery doesnt always work))
Flash Magisk 15.0 or 15.1 on Oreo and i believe 14.3 and down will work better for Nougat.
Reboot buddy!!! All is good in the world.
Click to expand...
Click to collapse
WAAAAAAIIIIIT!!!! you need to be on Magisk 15.0 just failed multiple times and realized that was the last thing I Updated to 15.1..
Make sure you're flashing 15.0.
Can we get Xposed yet on Oreo with Magisk? I see it says there are 4 different options available in the module section of Magisk. One is labeled "Xposed framework". All the others are labeled "Xposed Framework SDK 25" down to 19. Which one should be used for Oreo?
Hello,
As i have read and tried that current ARISE is not workable at the moment with latest 8.1.0 factory images, I am trying to stick to 8.0.0 for the while and utilize the guides where it is successfully installed.
I have installed the factory image 8.0.0 (OPR3.170623.013, Nov 2017) af0b6564 . Afterwards I am trying to follow this guide https://forum.xda-developers.com/pixel-xl/how-to/guide-android-8-oreo-root-stock-rooted-t3660591/.
When I try to fastboot in TWRP 3.2.1-1.img , it boots and loads correctly , and I am able to install
twrp-pixel-installer-marlin-3.2.1-1.zip. However when I try to reboot into recovery it goes into bootloop for once and directly boots into main system, instead of recovery.
To check I tried downloading TWRP 3.1.1-1.zip/img and tried flashing the zip, however the ZIP installation fails within the recovery with ERROR code=1.
Can someone please inform which is the correct working TWRP and Magisk version with Android 8.0.0, so I can finish the root process and proceed with ARISE installation.
Thanks for your guidance.
They have a 3.2.1.2 version with fixes posted. Maybe that will help.
HyperEscape said:
Hello,
As i have read and tried that current ARISE is not workable at the moment with latest 8.1.0 factory images, I am trying to stick to 8.0.0 for the while and utilize the guides where it is successfully installed.
I have installed the factory image 8.0.0 (OPR3.170623.013, Nov 2017) af0b6564 . Afterwards I am trying to follow this guide https://forum.xda-developers.com/pixel-xl/how-to/guide-android-8-oreo-root-stock-rooted-t3660591/.
When I try to fastboot in TWRP 3.2.1-1.img , it boots and loads correctly , and I am able to install
twrp-pixel-installer-marlin-3.2.1-1.zip. However when I try to reboot into recovery it goes into bootloop for once and directly boots into main system, instead of recovery.
To check I tried downloading TWRP 3.1.1-1.zip/img and tried flashing the zip, however the ZIP installation fails within the recovery with ERROR code=1.
Can someone please inform which is the correct working TWRP and Magisk version with Android 8.0.0, so I can finish the root process and proceed with ARISE installation.
Thanks for your guidance.
Click to expand...
Click to collapse
Android 8.1.0 + Magisk 16 + Magisk's Arise Module works.
harihacker said:
They have a 3.2.1.2 version with fixes posted. Maybe that will help.
Click to expand...
Click to collapse
Thanks, tried it today, same behavior, dont know what am I doing wrong, have started from a clean wiped flash of 8.0.0.
Homeboy76 said:
Android 8.1.0 + Magisk 16 + Magisk's Arise Module works.
Click to expand...
Click to collapse
Can you please give steps as how does it work. I have tried with latest image 8.1.0 (OPM1.171019.021, Mar 2018) by following your guide and trying to install ARISE+Deuteronomy+2.94+Modular+AROMA+Installer afterwards flashing the Arise+Magisk+Compatibility+Module+v4.0
When I boot afterwards, I get an Arkamys has stopped notification in a loop and the mobile goes to boot in recovery automatically, I dont select Arkamys audio, then when I open Viper4Android for driver installation, the installation fails with an I/O error. I have tried with both scripts installed in the latest Magisk v16, script for BusyBox and Permissive linux.
Any guidance would help.
Thanks.
HyperEscape said:
Can you please give steps as how does it work. I have tried with latest image 8.1.0 (OPM1.171019.021, Mar 2018) by following your guide and trying to install ARISE+Deuteronomy+2.94+Modular+AROMA+Installer afterwards flashing the Arise+Magisk+Compatibility+Module+v4.0
When I boot afterwards, I get an Arkamys has stopped notification in a loop and the mobile goes to boot in recovery automatically, I dont select Arkamys audio, then when I open Viper4Android for driver installation, the installation fails with an I/O error. I have tried with both scripts installed in the latest Magisk v16, script for BusyBox and Permissive linux.
Any guidance would help.
Thanks.
Click to expand...
Click to collapse
If you are try to get this 'ARISE+Deuteronomy+2.94+Modular+AROMA+Installer' to work on Android 8.0.0 or Android 8.1.0. I could be wrong, but I do not think it is possible. If that's what you want to install Google it.
There are options for Sound mods. take a look at the "Audio mod" in the 8.1.0 Guide or Do # 7 or 8 in the 8.1.0 Guide and install Viper4AndroidFX 1.5.2 and BusyBox modules using Magisk Manager.
Your choice.
Homeboy76 said:
If you are try to get this 'ARISE+Deuteronomy+2.94+Modular+AROMA+Installer' to work on Android 8.0.0 or Android 8.1.0. I could be wrong, but I do not think it is possible. If that's what you want to install Google it.
There are options for Sound mods. take a look at the "Audio mod" in the 8.1.0 Guide or Do # 7 or 8 in the 8.1.0 Guide and install Viper4AndroidFX 1.5.2 and BusyBox modules using Magisk Manager.
Your choice.
Click to expand...
Click to collapse
Yeah well i meant installing ARISE as a package with all additional audio libraries and effects and Sony Music apps. The Audio Mod 8.1.0 guide is only for installing Dolby Atmos and Viper4Android.
As of now I am not able to search a working method to install ARISE on 8.1.0 with March 2018 update.
To give it a try , I made the effort of following your guide with 8.1.0 (OPM1.171019.021, Mar 2018) flashed clean on my Pixel XL. After following your guide and the Audio guide to the dot, I installed Viper4Android FX-v1.5.2 (by ahrion/zackptg5) which worked, however Dolby Atmos did install successfully by but crashing on every app start.
Now I am looking for a way to install Sony Music and other apps to the mix, any guidance for a working method and version for it.
Thanks.
HyperEscape said:
Yeah well i meant installing ARISE as a package with all additional audio libraries and effects and Sony Music apps. The Audio Mod 8.1.0 guide is only for installing Dolby Atmos and Viper4Android.
As of now I am not able to search a working method to install ARISE on 8.1.0 with March 2018 update.
To give it a try , I made the effort of following your guide with 8.1.0 (OPM1.171019.021, Mar 2018) flashed clean on my Pixel XL. After following your guide and the Audio guide to the dot, I installed Viper4Android FX-v1.5.2 (by ahrion/zackptg5) which worked, however Dolby Atmos did install successfully by but crashing on every app start.
Now I am looking for a way to install Sony Music and other apps to the mix, any guidance for a working method and version for it.
Thanks.
Click to expand...
Click to collapse
Question, did you install the BusyBox module? Some modules need it. I do not know if Dolby Atmos is one that needs it.
I am not an expert on Viper4. Maybe, this thread will help: [3/1/18] ViPER4Android FX 2.5.0.5/2.3.4.0 [Unity] by ahrion
Homeboy76 said:
Question, did you install the BusyBox module? Some modules need it. I do not know if Dolby Atmos is one that needs it.
I am not an expert on Viper4. Maybe, this thread will help: [3/1/18] ViPER4Android FX 2.5.0.5/2.3.4.0 [Unity] by ahrion
Click to expand...
Click to collapse
I did install Permissive SE and Osmosis Magisk Busy Box modules before installing Dolby Atmos and Viper4Android Magisk modules.
Viper4Android installs and is working OK, however when I install Dolby Atmos, either in TWRP recovery or as a Magisk Module, the mobile goes in an infinite boot screen the google "G" logo. Since I already took a golden backup of the phone using TWRP, I have to boot in recovery by hard power off and then restore the backup.
I have also installed Sony Apps Enabler Magisk module and now I am able to directly install Sony Apps from the Play Store.
Any ideas how to make Dolby Atmos work. I will ask in the Dolby Atmos original thread as well.
Thanks.
HyperEscape said:
I did install Permissive SE and Osmosis Magisk Busy Box modules before installing Dolby Atmos and Viper4Android Magisk modules.
Viper4Android installs and is working OK, however when I install Dolby Atmos, either in TWRP recovery or as a Magisk Module, the mobile goes in an infinite boot screen the google "G" logo. Since I already took a golden backup of the phone using TWRP, I have to boot in recovery by hard power off and then restore the backup.
I have also installed Sony Apps Enabler Magisk module and now I am able to directly install Sony Apps from the Play Store.
Any ideas how to make Dolby Atmos work. I will ask in the Dolby Atmos original thread as well.
Thanks.
Click to expand...
Click to collapse
Go to this thread:
[GUIDE] Ultimate audio and battery guide by kingbri
Post your Question there.
@kingbri
HyperEscape said:
I did install Permissive SE and Osmosis Magisk Busy Box modules before installing Dolby Atmos and Viper4Android Magisk modules.
Viper4Android installs and is working OK, however when I install Dolby Atmos, either in TWRP recovery or as a Magisk Module, the mobile goes in an infinite boot screen the google "G" logo. Since I already took a golden backup of the phone using TWRP, I have to boot in recovery by hard power off and then restore the backup.
I have also installed Sony Apps Enabler Magisk module and now I am able to directly install Sony Apps from the Play Store.
Any ideas how to make Dolby Atmos work. I will ask in the Dolby Atmos original thread as well.
Thanks.
Click to expand...
Click to collapse
Go to this thread: [GUIDE] Ultimate audio and battery guide by kingbri and Post your Question there.
Did Kingbri's post solve your problem?