Database Develop

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

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.

Problem with Magisk

Hello to all
I've a problem with the complete functions of magisk manager, I can't how to solve problem with safety control, someone can help me?

iaio72 said:
Hello to all
I've a problem with the complete functions of magisk manager, I can't how to solve problem with safety control, someone can help me?
Click to expand...
Click to collapse
From the settings, enable magisk hide

domsch1988 said:
From the settings, enable magisk hide
Click to expand...
Click to collapse
sorry, but i cant find in settings how and where i can enabled magisk manager...

You can enable it per app

And globally in settings

I've open the magisk hide, but safety control always still error
I wrong or missing something

Wipe cache and reboot

nothing, wiped cache and dalvik, but always error in safety control

Disable USB Debugging? Caused some problems for others
Might also be custom kernel or selinux status...

domsch1988 said:
Disable USB Debugging? Caused some problems for others
Might also be custom kernel or selinux status...
Click to expand...
Click to collapse
ive closed the usb debug, changed selinux status, always with error safety control
now i've ex kernel latest version, but this safety error i've with original rr kernel....

SOLVED
Was elemental kernel
I just reflash the ROM without wipe data
I don't know why ex kernel had this issue with magisk

OnePlus7ProOxygen_21.O.22_OTA_022

Amendments
System
• Optimized power consumption in standby mode
• Optimized advanced screen display
• Optimized Bluetooth connectivity in cars
• Improved overall interaction (network, phone calls, mobile data)
• Optimized charging performance with third-party chargers
• With blank screen
• Fixed animation problem with fingerprint icon
• Fixed volume AirPods problem
• Fixed issue with black stripe during charging or Play Video Denia
• Updated security patch for Android 2.019.10
• Improved system stability and fixes general errors
Camera
• Optimized performance of the Super Stable function in the Video for Camera application.
https://androidfilehost.com/?fid=4349826312261635544

Rooted and good to go

Does Call of Duty Mobile still crash?

Installed since morning. Still October patch but have noticed battery is not draining as fast in use or idle. Notify buddy was working in tandem with Google Assistant in beta 5 but not here. Think it's a cleanup of either beta 3 or 4 with updated security patch from 10.01. Quite happy with it overall.

before install it on 10.01 swiped factory reset , I installed the rom with twrp ,when finished install , I made again factory reset,and install twrp zip (-3.3.1-70-guacamole-unified-installer-mauronofrio.zip )again .
battery not drain as fast in use,no problem about notification and no problem with twrp and magisk

Installed, rooted, TWRP, ElementalX, Gravity Box - Sill passes safety net.

The live wallpaper Is no more working.
Anyone has this problem?

I have the OnePlus launcher constantly crashing with the screen flashing. I have to use another launcher. Any idea how to fix? Tried uninstalling etc. But to no avail.
Also lost TWRP functionality since now it doesn't ask for pattern and can't mount storage. So no flashing Magisk or another rom.
Came from OB5 by disabling all Magisk mods, flashing 10.0.2 in TWRP, flashing TWRP installer script, rebooting recovery and that's when I got stuck with the unusable recovery. Help?

Guys since I've flashed this the play store keeps wanting me to pay for apps I've already bought and doesn't show any apps under update..I've uninstalled my account and reinstalled, also wiped the play stor app itself

tech_head said:
Installed, rooted, TWRP, ElementalX, Gravity Box - Sill passes safety net.
Click to expand...
Click to collapse
How did you get gravity box installed......
I installed core and tried both sandhook and yahfa... They both left me in a bootloop

grinch247 said:
How did you get gravity box installed......
I installed core and tried both sandhook and yahfa... They both left me in a bootloop
Click to expand...
Click to collapse
avid_droid said:
Wondering the same. I have never got any to work and in another thread someone provided a link but that also left me bootlooping
Click to expand...
Click to collapse
There is a beta release for Android 10. That doesn't trip safety net
*See my next post*
Use 0.4.5.5 not 0.4.6.0

If anyone can help, greatly appreciated.
going from 9.5.11:
System update to 10.0.2. Did not reboot on completion.
Flashed TWRP 3.3.72 in Magisk. Did not reboot.
Installed Magisk via direct install. Did not reboot.
Installed Magisk via available slot. Reboot, all good. Still rooted, no data lost.
I just did this but can't boot, just the white circles around the red circle screen

avid_droid said:
Yahfa or sandhook? Riru core and what else?
Click to expand...
Click to collapse
Riru core 19.5
YAHFA 0.4.5.5
Edxposed framework v90
Gravitybox (Q)
It's the only way I got mine to work on any 10 releases
Better link for everything gravitybox with guide
https://forum.xda-developers.com/xp...0-0-0-beta-1-android-10-t3974497#post80381445

avid_droid said:
Twrp.72 is still causing issues. Use twrp.70 and it'll work perfectly fine
Click to expand...
Click to collapse
Recovery will affect booting?
So just flash the 7.0 installer? I can currently boot to 72 recovery.

avid_droid said:
I ran into that problem when flashing with twrp.72
What I had to do is:
flash twrp.70 and reboot back into slot A.
Flash OOS 10.0.2
Flash twrp.70
Format data (you can try a factory reset)
Repeat same sequence on Slot B
Rebooted into system and set everything up and let it finish.
Reboot back into recovery and made sure I was in slot A
Flashed magisk 20.2
Reboot into system
All is good to go.
---------- Post added at 02:09 AM ---------- Previous post was at 01:58 AM ----------
Isn't there anyway to flash a different TWRP to get boot rather than to have to do all that flashing that you did?
Click to expand...
Click to collapse

avid_droid said:
vibrantliker said:
Yeah, just flash twrp.70 and reboot to recovery and it'll be .70
Click to expand...
Click to collapse
Sorry for all the questions, I can boot to .72 recovery now. Should I flash the earlier version from there? If so, can it be the installer or does it have to be the .img.
After flashing the different recovery, should it boot or do I have to do all the flashing like in your post above?
Click to expand...
Click to collapse

tech_head said:
Installed, rooted, TWRP, ElementalX, Gravity Box - Sill passes safety net.
Click to expand...
Click to collapse
So u run Xposed? Do u use Snapchat?

avid_droid said:
vibrantliker said:
Flash twrp.70 and you won't have any flashing issues.
Flash the twrp.70 and if you can't boot into system, like what I experienced with .72, then unfortunately, a clean flash is recommended as I've posted above
Click to expand...
Click to collapse
The installer or the .img
Click to expand...
Click to collapse

avid_droid said:
vibrantliker said:
Installer.zip just flash it through twrp and reboot to recovery and it'll show twrp .70
Click to expand...
Click to collapse
Then try reboot to system?
Click to expand...
Click to collapse

avid_droid said:
vibrantliker said:
Yes. If it doesn't reboot to system, then you'd have to reflash it all like I explained earlier
Click to expand...
Click to collapse
Thanks!
Click to expand...
Click to collapse

[OXYGENOS] Android 10 Open Beta 1 for OnePlus 5

Changelog
System
• Brand new UI design brings light and fluid experience
• Updated to Android 10
Instructions
• Download the appropriate package - OnePlus 5
• Open the File Manager and move the downloaded .zip package from the Downloads folder to the root directory.
• Open Settings - System - System updates, press the cogwheel on the top right corner, choose the Local upgrade option, and select the rollback file.
Users who are still on OBT builds for 5/5T can update to this build only via update from recovery. For those, PLEASE NOTE, your entire data will be wiped.
• Turn off the device -> Press power and volume up key simultaneously until the device enters the Fastboot Mode
• Navigate to Recovery option using volume and power button -> Choose English -> Install from Internal storage -> Select the downloaded zip file -> Select 'Yes'
• Wait until the installation is complete -> Reboot
Note:
• Please keep in mind that this is beta software. These builds are not as stable as our official OTAs. By installing this update, you accept the potential risks.

https://forums.oneplus.com/threads/android-10-open-beta-1-for-oneplus-5-5t.1218721/
OnePlus 5 : https://oxygenos.oneplus.net/OnePlus5Oxygen_23_OTA_063_all_2004201835_a1de28fd0bda4c8b.zip
OnePlus 5T : https://oxygenos.oneplus.net/OnePlus5TOxygen_43_OTA_063_all_2004201837_eca63aa919a1477a.zip

Anyone dirty flashed the full zip through twrp and after that installed magisk for root? Does that work?
Im on latest stable.

PhoenixNLx said:
Anyone dirty flashed the full zip through twrp and after that installed magisk for root? Does that work?
Im on latest stable.
Click to expand...
Click to collapse
I don't think so... It's better to perform a clean install

Astur_Torque said:
I don't think so... It's better to perform a clean install
Click to expand...
Click to collapse
Offcourse its better. But just want to know if it works... If i dont have to install all of my apps again. I'll take a chance. So if anybody tried it allready.
Or clean install full zip and magisk after that maybe?

PhoenixNLx said:
Offcourse its better. But just want to know if it works... If i dont have to install all of my apps again. I'll take a chance. So if anybody tried it allready.
Or clean install full zip and magisk after that maybe?
Click to expand...
Click to collapse
I came here looking for this too. I guess I'll have to do a full backup just in case before updating.

Hi, I come from OOS Stable 9.0.11 root, I just uninstalled MAGISK via TWRP then I restarted and I went through settings then system and I did update locally and everything is fine past. I reflashed TWRP via Fastboot then root with Magisk the last via TWRP and it's all good !!!

Ssmiles said:
Hi, I come from OOS Stable 9.0.11 root, I just uninstalled MAGISK via TWRP then I restarted and I went through settings then system and I did update locally and everything is fine past. I reflashed TWRP via Fastboot then root with Magisk the last via TWRP and it's all good !!!
Click to expand...
Click to collapse
Did you dirty flash or?

yes dirty flash
kernel BluSpark OOS v193 error in TWRP
Recovery TWRP 3.3.1-x blu_spark v9.110
ctsProfil Magisk 20.4 false

Astur_Torque said:
I don't think so... It's better to perform a clean install
Click to expand...
Click to collapse
Yes it worked, for me except duo calls not working when google hotword is enabled, everything is working

duo it's desactived

I tried this method https://droidholic.com/fix-cts-profile-mismatch-errors/ but CHROME doesn't work afterwards so I uninstalled everything

I just dirty flashed it in bluspark.
Full zip install
Magisk 20.4
Clear cache
Done

@PierreVicquery02 Request you to please remove the "[OFFICIAL]" from the thread title. The official thread already exists (it is stickied). Thanks for understanding!

shadowstep said:
@PierreVicquery02 Request you to please remove the "[OFFICIAL]" from the thread title. The official thread already exists (it is stickied). Thanks for understanding!
Click to expand...
Click to collapse
My thread was published before the other one, but as you wish

PierreVicquery02 said:
My thread was published before the other one, but as you wish
Click to expand...
Click to collapse
The other one (official thread) was created on 25th November 2017 by Funk Wizard, when the first Open Beta was released. Ever since then, it has been used for announcing all subsequent Open Beta releases as well as gather feedback on them. Nonetheless, thanks for changing the thread title, I appreciate it!

Does any one have any idea how I can enable full screen gestures for OnePlus 5?
I flashed the open beta build and tries enabling on screen navigation buttons but it's giving me the old buttons
I tried using
adb shell settings put secure swipe_up_to_switch_apps_enabled 1
as it used to work on OOS 9, but this has no effect on the current open beta build
Thanks in advance

The wifi is randomly dropping for me then reconnecting. That happens quite often,anyone else experiencing it? I'm full stock with locked bootloader,haven't done a factory reset though.

this beta ROM can pass safety net with magisk?

fedex_742 said:
this beta ROM can pass safety net with magisk?
Click to expand...
Click to collapse
Somebody passes, somebody not. I don't know why.

Root miui 12 without custom recovery

Hi guys. I have a question.
I updated my Mi9T to miui 12 and now I want to grant root again. I did the same things that I've done with miui 11:
Downloaded the rom
Extract the boot.img
Let magisk patch the boot
flash the patched boot with fastboot
The problem is that I got a WiFi issue: I can't turn it on. I back my boot.img to default e now it work but without root. Any ideas?

Marco2701 said:
Hi guys. I have a question.
I updated my Mi9T to miui 12 and now I want to grant root again. I did the same things that I've done with miui 11:
Downloaded the rom
Extract the boot.img
Let magisk patch the boot
flash the patched boot with fastboot
The problem is that I got a WiFi issue: I can't turn it on. I back my boot.img to default e now it work but without root. Any ideas?
Click to expand...
Click to collapse
Maybe you have ACC installed - uninstall and try without ACC (people did report similar errors for AAC, not dure was it fixed later in the module)

zgfg said:
Maybe you have AAC installed - uninstall and try without AAC (people did report similar errors for AAC, not dure was it fixed later in the module)
Click to expand...
Click to collapse
Sorry, I don't know what is aac. I searched it but I don't understand what I need to uninstall. I deactivated all magisk module but there is still the issue.

Marco2701 said:
Sorry, I don't know what is aac. I searched it but I don't understand what I need to uninstall. I deactivated all magisk module but there is still the issue.
Click to expand...
Click to collapse
Sorry, mistake, I meant ACC, Advanced Charging Controller Magisk module

zgfg said:
Sorry, mistake, I meant ACC, Advanced Charging Controller Magisk module
Click to expand...
Click to collapse
Nope, I haven't this module. Any other ideas?