Develop Bugs

Android System Update notice

Hello,
I have version D85130e installed on my phone and am rooted on the stock ROM. I received a System update notice this morning so i thought there was a new software version for the phone, but when I check on the T-mobile site for the LG G3, it says that D85130e is the latest version. (Cant post links because I am a new user).
I am confused, has anyone else received this update? I couldn't find anything about it. It is 133.0MB in size and says that it 'includes Android Security updates among other changes'.
I don't want to install it in case in breaks my root or worse. Does anyone here have any information about this?
Thank you!

received the update too
seleucid said:
Hello,
I have version D85130e installed on my phone and am rooted on the stock ROM. I received a System update notice this morning so i thought there was a new software version for the phone, but when I check on the T-mobile site for the LG G3, it says that D85130e is the latest version. (Cant post links because I am a new user).
I am confused, has anyone else received this update? I couldn't find anything about it. It is 133.0MB in size and says that it 'includes Android Security updates among other changes'.
I don't want to install it in case in breaks my root or worse. Does anyone here have any information about this?
Thank you!
Click to expand...
Click to collapse
tho i was disappointed it wasn't a 7.0 update, but i'm installing it right now and i would love to know: what's new?

Its a April security update. I will make a flashable zip with it. If anyone wants to try it pm me and I will share the link when its uploaded.
Link to try it: https://forum.xda-developers.com/showpost.php?p=72931940&postcount=98 Flash MagiskSU after flashing the zip.

from what I read yesterday, it's the D85130G update. https://goo.gl/ktuJMP
I don't want to chance unrooting my phone with this update. I'll wait till there is a rooted version to flash

jdmst77 said:
from what I read yesterday, it's the D85130G update.
I don't want to chance unrooting my phone with this update. I'll wait till there is a rooted version to flash
Click to expand...
Click to collapse
You can flash the update from the zip above and then flash magisk. That worked for me, I have v30G and root access. Thanks to MESA for suggesting it.
edit: MESA already said this above.

Stable update by MESA. No need to think about losing root access as MAGISK does the trick perfectly.
Everything is stable so far after 2 days of usage. I'll continue to give updates as and when I detect something unusual.

@eadumensah: is your safetynet working with MAGISK?

MESA said:
Its a April security update. I will make a flashable zip with it. If anyone wants to try it pm me and I will share the link when its uploaded.
Link to try it: https://forum.xda-developers.com/showpost.php?p=72931940&postcount=98 Flash MagiskSU after flashing the zip.
Click to expand...
Click to collapse
Thanks for keeping this old phone alive, it's running much better after the update. I just flashed it right over everything.

bluehacker007 said:
@eadumensah: is your safetynet working with MAGISK?
Click to expand...
Click to collapse
Not anymore. It worked on V12 but stopped after I upgraded to v13. Let me know in case you get a solution to that.

bluehacker007 said:
@eadumensah: is your safetynet working with MAGISK?
Click to expand...
Click to collapse
Ignore my earlier update. It does now after upgrading to v13.2

eadumensah said:
Ignore my earlier update. It does now after upgrading to v13.2
Click to expand...
Click to collapse
After a lot of testing it seems to me that safetynet works fine until I install xposed. Furthermore, installing systemless xposed from the magisk repository results in failure to boot. If I install systemless xposed from the xposed materialdesign app I am able to boot and use xposed modules but my safetynet check fails. I'm using magisk v13.2, magisk manager v5.0.6, material xposed installer v3.0.1 and systemless xposed v87.0 sdk 23 by topjohnwu.
Edited to add versions.

bluehacker007 said:
After a lot of testing it seems to me that safetynet works fine until I install xposed. Furthermore, installing systemless xposed from the magisk repository results in failure to boot. If I install systemless xposed from the xposed materialdesign app I am able to boot and use xposed modules but my safetynet check fails. I'm using magisk v13.2, magisk manager v5.0.6, material xposed installer v3.0.1 and systemless xposed v87.0 sdk 23 by topjohnwu.
Edited to add versions.
Click to expand...
Click to collapse
I got rid of xposed and deleted the play store data. Got into the magisk hide option and checked the following
1. Google play store
2. Google services framework
This is to hide it from detection by google. You can try it without deleting xposed first and let's see the outcome.

eadumensah said:
I got rid of xposed and deleted the play store data. Got into the magisk hide option and checked the following
1. Google play store
2. Google services framework
This is to hide it from detection by google. You can try it without deleting xposed first and let's see the outcome.
Click to expand...
Click to collapse
Tried that but it did not work. If I enable magisk core only mode (which disables systemless xposed) then I can pass security check. The only other magisk module I have is unified hosts adblock and I very much doubt that that is causing the safetynet failure.
Interesting side note: I've deleted apps from /system/apps and /system/priv-app from TWRP and I've changed the DPI using texdroider and these changes don't seem to trip safetynet.

lg g3 d851 30e MM not rooted
please help
i have an lg g3 d851 30e MM not rooted
i want to root(magisk systemless root) my lg g3 instal twrp and get the firmware v30G !!!!
what should i do
---------- Post added at 11:20 PM ---------- Previous post was at 10:43 PM ----------
MESA said:
Its a April security update. I will make a flashable zip with it. If anyone wants to try it pm me and I will share the link when its uploaded.
Link to try it: https://forum.xda-developers.com/showpost.php?p=72931940&postcount=98 Flash MagiskSU after flashing the zip.
Click to expand...
Click to collapse
lg g3 d851 30e MM not rooted
please help
i have an lg g3 d851 30e MM not rooted
i want to root(magisk systemless root) my lg g3 instal twrp and get the firmware v30G !!!!
what should i do

bluehacker007 said:
After a lot of testing it seems to me that safetynet works fine until I install xposed. Furthermore, installing systemless xposed from the magisk repository results in failure to boot. If I install systemless xposed from the xposed materialdesign app I am able to boot and use xposed modules but my safetynet check fails. I'm using magisk v13.2, magisk manager v5.0.6, material xposed installer v3.0.1 and systemless xposed v87.0 sdk 23 by topjohnwu.
Edited to add versions.
Click to expand...
Click to collapse
so you were able to get xposed to install and work correctly on 30G? Please confirm
whenever I tried, I could never boot up the device. If failing safetynet means that i can have xposed on 30G, I'm ready to upgrade from 30E

jdmst77 said:
so you were able to get xposed to install and work correctly on 30G? Please confirm
whenever I tried, I could never boot up the device. If failing safetynet means that i can have xposed on 30G, I'm ready to upgrade from 30E
Click to expand...
Click to collapse
I did get xposed to work but don't download and install the framework from the magisk app - use the xposed material design app to download and install the framework. I'm not sure why the magisk supplied framework doesn't work - it caused me to get stuck at boot as well.

bluehacker007 said:
I did get xposed to work but don't download and install the framework from the magisk app - use the xposed material design app to download and install the framework. I'm not sure why the magisk supplied framework doesn't work - it caused me to get stuck at boot as well.
Click to expand...
Click to collapse
I've been waiting for this info to upgrade. Thanks for all the details, including version, etc

[Magisk] SafetyNet Bypass Thread

First of all i think there is a need in common thread about Magisk.
I am on XT1685 with 137-35 ver. and exprerienced some Magisk issues. MagiskSU works well on 12.0, 13 beta and 13.3. But SafetyNet is not. My particular problem is not mountable magisk.img. And there is a suggestion that may be caused by f2fs issue on some Lenovo devices (or something else). In different threads there are a lot of different messages about working/not working SafetyNet so i think we need clarification. Most people don't even bother to point out OS version, stock, custom kernel, model etc. So let try to gather information about issue together.
SafetyNet status: not pass
Model: XT1685
OS: Stock 137-35
Kernel: Stock
Magisk: 13.3

Have you also tried the universal safetynet fix and it still doesn't pass?

That's peculiar, I'm on 13.3 with a 1687 running -35 with extended kernel by @attack11 and pass without universal safety net fix.

Dahenjo said:
Have you also tried the universal safetynet fix and it still doesn't pass?
Click to expand...
Click to collapse
Magisk modules don't work with stock kernel
For OP, you should try a custom kernel, probably this will fix your safety issue

atrac17 said:
That's peculiar, I'm on 13.3 with a 1687 running -35 with extended kernel by @attack11 and pass without universal safety net fix.
Click to expand...
Click to collapse
Same there. Yesterday flashed attack11 Extended Kernel V4 for NPN25.137-35 then flashed Magisk 13.3. All is green without USNF. Tried V5 but there was broken camera.

CaptPetrenko said:
Same there. Yesterday flashed attack11 Extended Kernel V4 for NPN25.137-35 then flashed Magisk 13.3. All is green without USNF. Tried V5 but there was broken camera.
Click to expand...
Click to collapse
V5 is for -67. That's why you had trouble.

atrac17 said:
V5 is for -67. That's why you had trouble.
Click to expand...
Click to collapse
Yeap.

Have you faced issue that folder binders or folder mounter not working of any kind. If you got a working then tell me. I am on 35

manjot7798 said:
Have you faced issue that folder binders or folder mounter not working of any kind. If you got a working then tell me. I am on 35
Click to expand...
Click to collapse
What do you exactly mean? In my case Magisk could not mount magisk.img into /magisk on system start

CaptPetrenko said:
What do you exactly mean? In my case Magisk could not mount magisk.img into /magisk on system start
Click to expand...
Click to collapse
I mean folder mount apps, the app in which you can free space, in which you have to mount the folder or can search it up on play store as folder mount or app2s all in one tool. It didn't seem to work on magisk 13.3 whereas it worked on magisk 11.6

manjot7798 said:
I mean folder mount apps, the app in which you can free space, in which you have to mount the folder or can search it up on play store as folder mount or app2s all in one tool. It didn't seem to work on magisk 13.3 whereas it worked on magisk 11.6
Click to expand...
Click to collapse
Can not say something about that. I never mounted folders. Use only Root Explorer for file managing. Do you have problems with SafetyNet? Could you send Magisk log? May be your mounting problem has common roots with stock kernel issue and read-only preferences

XT1687
NPNS25.137-33-5
Security patch level is May 1, 2017
I used this video as my guide: youtube[dot]com/watch?v=zUPTFnzAvSo
Root was successful with Magisk 13.3 (including installation of ElementalX-G5-1.01) but ctsProfile and basicIntegrity are false with Safety Net check. The creator of the video had us flash universal safety net fix v1.zip and updated safety net fix v2.zip which I did, but the SafetyNet check still fails. On his video, both items passed.
Not sure what went wrong for me.
He advised users (in the comments) to flash a different kernel, then flash the two safety net zip files again. Good advice or not? Can someone elaborate?

I can confirm all green via these steps: from stock, install extended kernel v4, install magisk v13.3, and all green. Updated to magisk v14 via Magisk manager, all remains green.
Quote:
Originally Posted by atrac17
That's peculiar, I'm on 13.3 with a 1687 running -35 with extended kernel by @attack11 and pass without universal safety net fix.

After updating to v. 14.0 ctsProfile error occured. I rolled back to 13.3 version but there was the same error. I flashed the latetst beta of universal fix and ctsProfile check went through. Don't know would it work with 14.0 ver.

brandonsisco said:
I can confirm all green via these steps: from stock, install extended kernel v4, install magisk v13.3, and all green. Updated to magisk v14 via Magisk manager, all remains green.
Click to expand...
Click to collapse
CaptPetrenko said:
After updating to v. 14.0 ctsProfile error occured.
Click to expand...
Click to collapse
Hi,
Most of the work regarding the cts check can be done with a custom kernel.
And one relevant factor is remove the parameters "androidboot.verifiedbootstate" and "androidboot.veritymode" from the command-line (patching the "/proc/cmdline" file).
See this post: http://forum.xda-developers.com/showpost.php?p=73712158&postcount=471
If you like to pass the SafetyNet, then first use a patched kernel or request to developers to include this patch!
Don't waste your time with other complex solutions!

Hi,
If you like to pass SafetyNet in stock and have full support for Magisk then install this kernel:
https://forum.xda-developers.com/showpost.php?p=73783900&postcount=483
Regards.

Lineage OS 14.1 & LOS kernel with Magisk 14 does not pass.

brandonsisco said:
I can confirm all green via these steps: from stock, install extended kernel v4, install magisk v13.3, and all green. Updated to magisk v14 via Magisk manager, all remains green.
Quote:
Originally Posted by atrac17
That's peculiar, I'm on 13.3 with a 1687 running -35 with extended kernel by @attack11 and pass without universal safety net fix.
Click to expand...
Click to collapse
I changed to the v4 extended kernel, Magisk V14.0, and also getting all green on the SafetyCheck with the 35 rom. BUT MagiskHide does not work: when I look at the logs I see
fopen:/magisk/.core/hidelist failed with 2: No such file or directory
Does MagiskHide work for you?

Yes working for me I suspect you have mounting error above that in log?
---------- Post added at 08:41 PM ---------- Previous post was at 08:39 PM ----------
I suggest install stock then extended kernel then magick fresh

snaggletooth1 said:
XT1687
NPNS25.137-33-5
Security patch level is May 1, 2017
I used this video as my guide: youtube[dot]com/watch?v=zUPTFnzAvSo
Root was successful with Magisk 13.3 (including installation of ElementalX-G5-1.01) but ctsProfile and basicIntegrity are false with Safety Net check. The creator of the video had us flash universal safety net fix v1.zip and updated safety net fix v2.zip which I did, but the SafetyNet check still fails. On his video, both items passed.
Not sure what went wrong for me.
He advised users (in the comments) to flash a different kernel, then flash the two safety net zip files again. Good advice or not? Can someone elaborate?
Click to expand...
Click to collapse
Hi, I came from the same video and I did all the steps he put in there. I did the root process with Magisk 13 then I updated to 14 version (a days ago) and everything is working ok.

v4A on magisk16.4 may update?

Has anyone been able to get a v4a module working on 16.4 and the may update? I tried installing the module by viper50 and ahirion that has worked so well in the past... Doesn't seem to be enabling for me this time around for some reason. Any ideas?
Or other mods to recommend?

V4a v2.5.05 working fine with magisk 16.4 and may update here.

EnIXmA said:
V4a v2.5.05 working fine with magisk 16.4 and may update here.
Click to expand...
Click to collapse
Same here, everything working smoothly with v4afx_v1.6.9.zip and magisk 16.4. Viper also works on P dp2.

Taebom said:
Same here, everything working smoothly with v4afx_v1.6.9.zip and magisk 16.4. Viper also works on P dp2.
Click to expand...
Click to collapse
Are you flashing in magisk or twrp? Which module are you using? Thanks!

I'm neither of the other posters, but flash V4A via Magisk using the module authored by Viper520, ZhuHang, Ahrion, and Zackptg5. Be certain that you select the new driver and the materialized version of the app for V4A to work properly.

Strephon Alkhalikoi said:
I'm neither of the other posters, but flash V4A via Magisk using the module authored by Viper520, ZhuHang, Ahrion, and Zackptg5. Be certain that you select the new driver and the materialized version of the app for V4A to work properly.
Click to expand...
Click to collapse
This ^^ : point upwards: ! Especially the underlined part; it took me a whole lot of trial and error to figure this last part out...
In any case, I used the latest Magisk module (if you check the details of the modules, it'll show when it was last updated). If anything, supposedly you could just install straight away, but V4A gave me errors. I had to uninstall the existing V4A, reboot, install via Magisk module, and reboot before it worked. You (@Cowbell_Guy) might, at the very least, have to walk through the same steps for whatever reason...
Hope this helps...

Viper4android for Redmi_Note_8_Pro

V4A Fx installation (Rooted with magisk required)
Download following modules:
https://drive.google.com/folderview?id=10Q_4QsFAe8cW63GH3VrM0jtuIOAPP8t1
1.Install magisk_selinux_manager_v1.0.zip magisk module in magisk manager and set selinux to permissive.
2.install ViPER4Android_FX-v2.7.1.0(2710).zip magisk module in magisk manager.(requires internet)
3.Reboot and open V4A it will ask for driver installation .Allow it
4.After installation of driver it will automatically reboot .
5.Enjoy V4A
Credits to @santoshhh000
If you like this post press thanks

No

Did you install from magisk? Not twrp. Follow the instructions as mentioned above

ariber14 said:
Did you install from magisk? Not twrp. Follow the instructions as mentioned above
Click to expand...
Click to collapse
Yes, from magisk.
I will try again when reinstall miui eu.

omerhodzic1 said:
Yes, from magisk.
I will try again when reinstall miui eu.
Click to expand...
Click to collapse
Hey, miui eu is working?

---------- Post added at 11:10 PM ---------- Previous post was at 11:08 PM ----------
[/COLOR]
Linkonlk said:
Hey, miui eu is working?
Click to expand...
Click to collapse
Found it on the telegram group.
Redmi Note 8 Pro | OFFICIAL
Redmi Note 8 Pro - Official Telegram Group
t.me/RedmiNote8ProOfficial

ariber14 said:
V4A Fx installation (Rooted with magisk required)
Download following modules:
https://drive.google.com/folderview?id=10Q_4QsFAe8cW63GH3VrM0jtuIOAPP8t1
1.Install magisk_selinux_manager_v1.0.zip magisk module in magisk manager and set selinux to permissive.
2.install ViPER4Android_FX-v2.7.1.0(2710).zip magisk module in magisk manager.(requires internet)
3.Reboot and open V4A it will ask for driver installation .Allow it
4.After installation of driver it will automatically reboot .
5.Enjoy V4A
Credits to @santoshhh000
If you like this post press thanks
Click to expand...
Click to collapse
Which miui you install?

omerhodzic1 said:
Which miui you install?
Click to expand...
Click to collapse
On miui 11.0.2.0 eu

ariber14 said:
On miui 11.0.2.0 eu
Click to expand...
Click to collapse
I tried multiple times, miui eu 11.0.2.0, with a clean install at the end, without an account and any backup, different versions of magisk, ect. 1 or 2 sim card.
With one, one sim card work, when I installed the Viper with 2 sim, stop working both.
Maybe I'll be lucky with some new version. The Viper is my favorite.

Search for a zip called clean+soundmod.zip.it will remove any audio mod that might create conflict.flash it ftom twrp then repeat the procedure again as mentioned

ariber14 said:
Search for a zip called clean+soundmod.zip.it will remove any audio mod that might create conflict.flash it ftom twrp then repeat the procedure again as mentioned
Click to expand...
Click to collapse
Can you post it here. I could not find it.

Here it is. Flash it from twrp then restart

ariber14 said:
Here it is. Flash it from twrp then restart
Click to expand...
Click to collapse
Thank you!!
Your phone is using xiaomi.eu rom, but Is it China version or Global version?
I have China one with same xiaomi.eu rom, but cant seem to make viper work

MarkLev said:
Thank you!!
Your phone is using xiaomi.eu rom, but Is it China version or Global version?
I have China one with same xiaomi.eu rom, but cant seem to make viper work
Click to expand...
Click to collapse
M1906G7G - Global 64mb - not working for now.

omerhodzic1 said:
M1906G7G - Global 64mb - not working for now.
Click to expand...
Click to collapse
Problem with magisk_selinux_manager_v1.0.zip
If use 2 SIM they stop working.
Viper working with setenforce 0 in terminal.
Found this on telegram group:
t.me/RedmiNote8ProOfficial

I have noticed . Selinux manager module when flashed through latest magisk .It Doesn't work ,so if possible flash it through older version magisk 20.0 or earlier version .After that you can update your magisk to latest.

santoshhh000 said:
I have noticed . Selinux manager module when flashed through latest magisk .It Doesn't work ,so if possible flash it through older version magisk 20.0 or earlier version .After that you can update your magisk to latest.
Click to expand...
Click to collapse
I tried with magisk 19 and the problem is the same.
I also have a problem with SIM cards, when install magisk_selinux_manager_v1.0.zip with permissive, only when I take out one SIM card GSM works, when two are not working, no registered cards in mob, if install with enforceing is ok, that's weird. It is no problem for me to use the terminal, it is also safer for the system, it may be safer not to be in permissive mode all the time.
Thank you for your help.
And most importantly, I have ViPER4A!
All the best,

omerhodzic1 said:
I tried with magisk 19 and the problem is the same.
I also have a problem with SIM cards, when install magisk_selinux_manager_v1.0.zip with permissive, only when I take out one SIM card GSM works, when two are not working, no registered cards in mob, if install with enforceing is ok, that's weird. It is no problem for me to use the terminal, it is also safer for the system, it may be safer not to be in permissive mode all the time.
Thank you for your help.
And most importantly, I have ViPER4A!
All the best,
Click to expand...
Click to collapse
1. Install SELinux Mode Changer app from here
2. Install lates viper4android app
3. Start SELinux Mode Changer and set to "permissive" then start viper4android and Enjoy!
you can set autostart for SELinux Mode Changer

MarkLev said:
1. Install SELinux Mode Changer app from here
2. Install lates viper4android app
3. Start SELinux Mode Changer and set to "permissive" then start viper4android and Enjoy!
you can set autostart for SELinux Mode Changer
Click to expand...
Click to collapse
That's it.
Thnx

I totally forgot Tasker.

Themes / Apps / Mods Dolby Atmos on A11

Redskull mods on tg has made a simple magisk module to do this now. Search on telegram for his modsmy method still works his module is simpler for users though
In order to get dolby atmos working on A11 you will need to download the apk, then open it. Next you will need to disable soundtuner service via adb like like in a10 or use service disabler app. Then reboot
ADB - "adb shell pm uninstall --user 0 com.oneplus.sound.tuner"
Service Disabler (Playstore) https://play.google.com/store/apps/details?id=com.kunkunsoft.rootservicedisabler
Also you will need edexpoaed and corepatch module activated

or else just flash this in Magisk:
[6.0-12.0][Magisk]Dolby Digital Plus[upd.20211005]
Dolby Digital Plus for 9.0-12.0 OS Need selinux permissive Hi. I present the mod Dolby Digital Plus (interface and functionality is the same as that of Dolby Atmos). Theoretically should work on OS 6.0-9.0. I checked only on Oreo and Pie...
forum.xda-developers.com

toolhas4degrees said:
In order to get dolby atmos working on A11 you will need to download the apk, then open it. Next you will need to disable soundtuner service via adb like like in a10 or use service disabler app. Then reboot
ADB - "adb shell pm uninstall --user 0 com.oneplus.sound.tuner"
Service Disabler (Playstore) https://play.google.com/store/apps/details?id=com.kunkunsoft.rootservicedisabler
Click to expand...
Click to collapse
doesn't the op9 pro already have dolby atmos? it's in my settings currently, or is this not the real thing?

thirtythr33 said:
doesn't the op9 pro already have dolby atmos? it's in my settings currently, or is this not the real thing? View attachment 5287753
Click to expand...
Click to collapse
No dolby with eq even if not wired different you are talking about stock oneplus dolby I'm talking about atmos picture added to help you

vibrantliker said:
or else just flash this in Magisk:
[6.0-12.0][Magisk]Dolby Digital Plus[upd.20211005]
Dolby Digital Plus for 9.0-12.0 OS Need selinux permissive Hi. I present the mod Dolby Digital Plus (interface and functionality is the same as that of Dolby Atmos). Theoretically should work on OS 6.0-9.0. I checked only on Oreo and Pie...
forum.xda-developers.com
Click to expand...
Click to collapse
It's a very old version that you suggest to flash. This is newer

It works thanks

Nice to see Dolby love here! kudos

toolhas4degrees said:
Also you will need edexpoaed and corepatch module activated
Click to expand...
Click to collapse
Is there any way to pass safetynet with edexposed?

HubertGT said:
Is there any way to pass safetynet with edexposed?
Click to expand...
Click to collapse
Magisk hide props, currently non for our device, I just got this phone need to play to wlsee which one works. And then safety net pass in edexpoaed will report back later if I figure out which prop

Mar-cel said:
It works thanks View attachment 5288267
Click to expand...
Click to collapse
Are you passing safety net with edexpoaed?

HubertGT said:
Is there any way to pass safetynet with edexposed?
Click to expand...
Click to collapse
I used magisk props and selected op8pro with my variant a10. Rebooted and wiped all google apps cache and data then rebooted again and went back into props and selected reset all option and rebooted again.(don't know if this partially fixed it or not. Then I downloaded the latest magisk canary and updated in magisk app. You have to delete old magisk apk before installing the canary apk. I then rebooted and went into magisk and hid the app (renamed it). Then I enabled magisk hide and selected all apps that contain google. Then here is proof it passed. Also I have core patch and Hidden core module enabled in exposed and in exposed settings I have these enabled.

Does this work on non-rooted phones?

Arrow79 said:
Does this work on non-rooted phones?
Click to expand...
Click to collapse
No

toolhas4degrees said:
It's a very old version that you suggest to flash. This is newer
Click to expand...
Click to collapse
I always liked this better than the Atmos app, and it still sounds good

vibrantliker said:
I always liked this better than the Atmos app, and it still sounds good
Click to expand...
Click to collapse
To each their own

toolhas4degrees said:
In order to get dolby atmos working on A11 you will need to download the apk, then open it. Next you will need to disable soundtuner service via adb like like in a10 or use service disabler app. Then reboot
ADB - "adb shell pm uninstall --user 0 com.oneplus.sound.tuner"
Service Disabler (Playstore) https://play.google.com/store/apps/details?id=com.kunkunsoft.rootservicedisabler
Also you will need edexpoaed and corepatch module activated
Click to expand...
Click to collapse
Please, can you post step by step how to get this done? I’m rooted, magisk and exsposed manager installed, adb command executed and dolby.apk installed. Everytime I try to run Dolby it crashes. Thanx

Arrow79 said:
Please, can you post step by step how to get this done? I’m rooted, magisk and edxsposed manager installed, adb command executed and dolby.apk installed. Everytime I try to run Dolby it crashes. Thanx
Click to expand...
Click to collapse
I did did you open the app before running command then reboot, also did you install the two exposed modules I posted?

I’m kinda new to magisk/exposed, don’t know which modules exactly to install.. when I opened the installed dolby before executing command it also crashes.

Can someone make a zip file that can be flashed with Magisk? It would be much appreciated

OK, the module Core Patch was missing. Now its working. Thanks
Edit: After 11.2.5.5 update the Dolby keeps crashing...