[Magisk] [ARM] [+ViPER] Dolby Atmos r6.5 - Magisk

Systemless Dolby Atmos r6.5​
Requirements:
Magisk 11+
Remove any other audio modules you have installed
Using Magisk's inbuilt superuser for root access (no phh/supersu)
Instructions:
Just flash Module zip through Magisk Manager or TWRP.
To use ViPER4Android, install APK from here.
Download from Magisk manager
Port of Dolby Atmos r6.5 by worstenbrood on Magisk.
Github
Credits: worstenbrood (for original Dolby Atmos port) & topjohnwu (for V4A module and Magisk)

Can it work simultaneously with Viper?

A_Random_Guy said:
Can it work simultaneously with Viper?
Click to expand...
Click to collapse
I don't think so. You can try. Most probably I'll have to create a separate zip with Dolby+Viper.

A_Random_Guy said:
Can it work simultaneously with Viper?
Click to expand...
Click to collapse
Same problems on LeeDroid.
Wysłane z mojego HTC 10 przy użyciu Tapatalka

Tried this module on my Nexus 6P, stock ROM (7.1.1) with Magisk 11.1. went into bootloop.

Thanks so much!!!! I had to give up on Atmos a while back when SafetyNet ramped up its security and I was hoping a magisk module would show up eventually.

How about the Collective Dolby ATMOS, https://forum.xda-developers.com/android/software/soundmod-axon-7-dolby-atmos-t3412342/, which are newer versions. Did you ever tried on that? I adapted these Collective Dolby ATMOS into Magisk modules since v7, but they failed on v10 and v11. Any ideas?
https://github.com/laggardkernel/magisk-module-template/tree/leeco_lemax_2
Update: sorry, my fault. The problem is that I used multirom to test these modules but Magisk v10 and v11 aren't compatible with multirom anymore.

@Yash98 r6.5 Magisk module causes a black screen immediately after stock moto splash screen.
My steps:
1. Download and install r6.5 through Magisk Manager.
2. "Installation successful" dialogue
3. Tap reboot
4. Device starts to reboot but screen goes black after stock moto splash screen
I had to boot into recovery and delete the mod for my phone to boot up.
My current device info is in my signature

JERW28 said:
@Yash98 r6.5 Magisk module causes a black screen immediately after stock moto splash screen.
My steps:
1. Download and install r6.5 through Magisk Manager.
2. "Installation successful" dialogue
3. Tap reboot
4. Device starts to reboot but screen goes black after stock moto splash screen
I had to boot into recovery and delete the mod for my phone to boot up.
My current device info is in my signature
Click to expand...
Click to collapse
Where do you find the mod to delete? I have the same problem but I don't find what I have to delete (Nexus 5X).
Thanks.

@kartikb @Plonkyplonk @boutsism
The module is called Mount-Magisk.zip. I found it here in the first post: https://forum.xda-developers.com/apps/magisk/collection-magisk-modules-t3445257
1. Flash in twrp
2. Using twrp file manager, go to /magisk
3. Choose mod and tap delete
The phone should reboot normally

laggardkernel said:
How about the Collective Dolby ATMOS, https://forum.xda-developers.com/android/software/soundmod-axon-7-dolby-atmos-t3412342/, which are newer versions. Did you ever tried on that? I adapted these Collective Dolby ATMOS into Magisk modules since v7, but they failed on v10 and v11. Any ideas?
https://github.com/laggardkernel/magisk-module-template/tree/leeco_lemax_2
Click to expand...
Click to collapse
Never tried magiskifying that as they never worked on my devices.

JERW28 said:
@Yash98 r6.5 Magisk module causes a black screen immediately after stock moto splash screen.
My steps:
1. Download and install r6.5 through Magisk Manager.
2. "Installation successful" dialogue
3. Tap reboot
4. Device starts to reboot but screen goes black after stock moto splash screen
I had to boot into recovery and delete the mod for my phone to boot up.
My current device info is in my signature
Click to expand...
Click to collapse
I'll need a logcat of this @boutsism

I see that the original post was updated this morning, does that mean it works correctly with Magisk 11.1 now, without causing bootloops?

Jinded said:
I see that the original post was updated this morning, does that mean it works correctly with Magisk 11.1 now, without causing bootloops?
Click to expand...
Click to collapse
Nope I'm getting a bootloop on magisk v11.1, Nexus 6, Stock Android 6.0.1.

Working fine on Nexus 6, Pure Nexus 7.1.1_r13 (01/21), Magisk v11.1 and MagiskSU.

Why is the APK supposed to use just the old version of the module's zip file? Are we supposed to extract it?

Just a heads up, I'm using on a HTC 10 and it's all good.

PartyPlease said:
Nope I'm getting a bootloop on magisk v11.1, Nexus 6, Stock Android 6.0.1.
Click to expand...
Click to collapse
Do you have any other audio modules installed?

Yash98 said:
Do you have any other audio modules installed?
Click to expand...
Click to collapse
Nope, fully stock everything.

Lost root after flash this module. I used magisk 11.1 and supersu 2.79.

Related

Systemless SuperSU + suhide

I used SuperSU included in TWRP from http://forum.xda-developers.com/showpost.php?p=67791618&postcount=10 to root my device. In this thread, it is said that only this modified version of SuperSU is working.
Is it possible to flash the included SuperSU systemless and then flash suhide from http://forum.xda-developers.com/apps/supersu/suhide-t3450396?
Just in case someone else also wants to try this - I got SuperSU + suhide working.
What I did:
- Unrooted from SuperSU app
- Rebooted system (happened automatically)
- Rebooted into TWRP and systemless flashed SuperSU 2.78-SR1 from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
- Rebooted system
- Rebooted into TWRP and flashed suhide
-> SuperSU is working, Pokemon Go 0.39.1 is also working
Hi zendertrick,
thanks for the heads up!
It worked fine so far, but now I have a major issue with vibration: a few seconds after I unlock my SIM, my phone doesn‘t vibrate anymore.
Is this also happening to you?
Thanks and best regards
Tek
zendertrick said:
Just in case someone else also wants to try this - I got SuperSU + suhide working.
What I did:
- Unrooted from SuperSU app
- Rebooted system (happened automatically)
- Rebooted into TWRP and systemless flashed SuperSU 2.78-SR1 from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
- Rebooted system
- Rebooted into TWRP and flashed suhide
-> SuperSU is working, Pokemon Go 0.39.1 is also working
Click to expand...
Click to collapse
Do you have xposed installed?
Sent from my SM-G930F using Tapatalk
Tek5 said:
It worked fine so far, but now I have a major issue with vibration: a few seconds after I unlock my SIM, my phone doesn‘t vibrate anymore.
Is this also happening to you?
Click to expand...
Click to collapse
No, vibration works for me, but I don't have a SIM lock.
madhero said:
Do you have xposed installed?
Click to expand...
Click to collapse
No, i don't have xposed installed.
I have sound bug with SuHide, when i install it, the speaker don't working with Mokee Rom on Zuk Z2 Pro and i have somes popup who advertise me somes Apk Qualcomm crash after system start.
If i dont install it, Systemless SuperSu and Systemless Xposed works very well.

Magisk Modules on OOS 5.0? (Official OREO OTA)

I've just clean flashed latest official from Oneplus (wiped everything and sideload from stock recovery) Using Magisk 14.3 with the bundled latest Magisk Manager 5.4.0, bluspark TWRP. Root and root apps work fine with SafetyNet pass.
It gets stuck at boot animation if I reboot after load a Magisk module. OP3T A3003.
Anyone managed to get working Magisk modules in OOS? And how? OOS Oreo is really snappy I like it
Thanks
I have the exact same setup as you, so I suspect it may be the module you're trying to use that is incompatible with OOS 5.0.
I am currently using "iOS 11.1 Emoji" and "HEVC+SM" Google Camera modules, working perfectly.
huilun02 said:
It gets stuck at boot animation if I reboot after load a Magisk module. OP3T A3003.
Anyone managed to get working Magisk modules in OOS? And how? OOS Oreo is really snappy I like it
Thanks
Click to expand...
Click to collapse
Which module isn't working? As said above, depending on what it does it may not be compatible.
I'm using iOS 11.1 emoji aswell, iYTBP, Extended Volume Steps and Display SELinux Status without any issue.

Magisk 15.2 successfully flashed but Magisk is not installed error on Magisk Manager

I am using Asus Zenfone Max Z010D (ZC550KL).
I have TWRP-3.2.0-Z010D-20171205 on my phone, currently using stock rom Version WW 8916-13.8.26.92.
When flashing Magisk 14 thru twrp and reboot, Magisk is detected in the system and is installed correctly.
But Collective Dolby (https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342)
and Viper (https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058) is not working and not installing thru TWRP with error saying that Magisk v15+ is needed.
When flashing magisk 15.2, it is done successfully but upon reboot and checking in magisk manager it is stated that Magisk is not installed.
So I want to be able to use magisk 15 and up so i can use dolby and viper by sir ahrion.
I hope you can help me guys.
Thanks in advance.
griffynix said:
I am using Asus Zenfone Max Z010D (ZC550KL).
I have TWRP-3.2.0-Z010D-20171205 on my phone, currently using stock rom Version WW 8916-13.8.26.92.
When flashing Magisk 14 thru twrp and reboot, Magisk is detected in the system and is installed correctly.
But Collective Dolby (https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342)
and Viper (https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058) is not working and not installing thru TWRP with error saying that Magisk v15+ is needed.
When flashing magisk 15.2, it is done successfully but upon reboot and checking in magisk manager it is stated that Magisk is not installed.
So I want to be able to use magisk 15 and up so i can use dolby and viper by sir ahrion.
I hope you can help me guys.
Thanks in advance.
Click to expand...
Click to collapse
Same here when installing magisk 15.2 but magisk manager for me is stuck at the splash screen, only magisk 14.x works.
Zenfone 2 ZE551ML / Stock 6.0.1
guys, i got error on installing magisk manager apk. its say "app not installed". how to solved it? thank you

Can't update magisk to v17

I try and install directly from magisk but when I go and flash the zip through app it says installation failed. Am I doing something wrong?
Me too
I try unistall magisk in recovery but non success
I'm blocked
Edit: i'm return at v16.6 and work
I don't update for Now Walt for more info
Ty for now I'll wait
same here
Edit:- can't go back to v16.0 either,i'm getting "updater process ended with ERROR: 1
Any suggestions?
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
If I don't have TWRP I just install it? Sorry for noob question but i'm new here
Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
Thanks mate,worked for me.
Hi,
I'm running a HTC 10 with Lineage OS 15.1 (8.1.0). I came from Magisk 16 and an update message appeard. I downloaded Magisk 17 and tried to install it via TWRP as usual. The installation stopped with an Error 2. After that I had a boot loop and had to reinstall the Lineage OS. After that it booted again. But I still get this error message when trying to install Magisk 17.
Very odd. Besides of that, GREAT WORK!
Cheers
lmrcarneiro said:
If I don't have TWRP I just install it? Sorry for noob question but i'm new here
Click to expand...
Click to collapse
Magisk uninstaller will not works without custom recovery so i think my instruction is not applicable in this situation.
chaos_since_78 said:
Hi,
I'm running a HTC 10 with Lineage OS 15.1 (8.1.0). I came from Magisk 16 and an update message appeard. I downloaded Magisk 17 and tried to install it via TWRP as usual. The installation stopped with an Error 2. After that I had a boot loop and had to reinstall the Lineage OS. After that it booted again. But I still get this error message when trying to install Magisk 17.
Very odd. Besides of that, GREAT WORK!
Cheers
Click to expand...
Click to collapse
Double check if the package is not corrupted, MD5 should be: 6237bfaf7dcf516b60922b5b26f2dca8.
Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
Thanks for this
but now i can't install universal fix for safetynet check
I'm not sure if Magisk v.17.0 is fully backward compatible. Maybe this is preventing the module from installing?
Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
thank you very much i installed twrp and followed your steps worked great
Karls0 said:
I'm not sure if Magisk v.17.0 is fully backward compatible. Maybe this is preventing the module from installing?
Click to expand...
Click to collapse
ok so wait for new fix thanks
On my pixel 1 it claims to install, but causes a bootloop. AND updating to the most recent manager breaks using v16. So I'm stuck with an old manager and v16
Yes, the new manager seems to not fit to Magisk v16. In my case it also broke something so I updated to v17.
Karls0 said:
Magisk uninstaller will not works without custom recovery so i think my instruction is not applicable in this situation.
Double check if the package is not corrupted, MD5 should be: 6237bfaf7dcf516b60922b5b26f2dca8.
Click to expand...
Click to collapse
I got it solved by uninstallion the former Magisk package with the uninstaller. After reboot I could reinstall version 17 and until now it works fine. Thanks.
uninstaller for me does not flash for me. error 255 v16 same error and 17.1 wont flash either error 2
Thanks.
I'm able to do the steps without error. But then it is in bootloop. Using redmi note 4g (dior) Dot os
adz63 said:
uninstaller for me does not flash for me. error 255 v16 same error and 17.1 wont flash either error 2
Click to expand...
Click to collapse
Have you tried rebooting TWRP when the errors appear, and where are the logs?
barathrr96 said:
Thanks.
I'm able to do the steps without error. But then it is in bootloop. Using redmi note 4g (dior) Dot os
Click to expand...
Click to collapse
Is this on a clean install of Magisk v17.1? Also, logs...
Didgeridoohan said:
Have you tried rebooting TWRP when the errors appear, and where are the logs?
Is this on a clean install of Magisk v17.1? Also, logs...
Click to expand...
Click to collapse
Thanks.. the device does not belong to me..
for the time being I have installed magisk v16.7 and did installed viper and removed it ..
so when I get the device next time in my hand I will try to flash and take logs..

Any Soundmod for android 10.0

Im running Pixel experience on my Xiaomi Mi 8 and viper just causes my phone to get stuck on the Mi Logo (before boot animation) any ideas?
For viper4android use this method :
install apk from this link https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
don't open the app yet
download zip file from this link and flash it through twrp https://zackptg5.com/downloads/v4afx-rootless_08.18.2019.zip
if viper4android isn't processing then uninstall any audio modification library in your rom and reboot
Wow! This actually worked. Thank you.
Whoa! Finally! Thanks a lot, this worked. Although, there was some weird stuff going on at first.
It got stuck at manufactur logo like usual, after flashing from twrp and installing the driver. I thought this also failed, like my attempts through magisk.
Then I went into magisk manager for recovery, saw a v4a magisk module installed and removed it.
After booting up, v4a was still there, and processing, lol.
Zip file?
Zip file has been removed from the link
I'm on pixel experience android 10
singh44 said:
Zip file has been removed from the link
I'm on pixel experience android 10
Click to expand...
Click to collapse
https://zackptg5.com/downloads/v4afx-rootless_01.15.2020.zip
Just found by navigating on zackptg5's website
https://zackptg5.com/android.php

Categories

Resources