Related
So i've seen a lot of viper/viper4arise ( + Dolby + etc ) on many threads...
with maybe way too many versions..
On 7.1.1 default OOS 4, I have mine worked just fine with the one coming from magisk repo.
I've tried the one from Magisk 14.5, processing says Abnormal..
and i can hear crackle sounds in the background when playing music.
Decided not to clutter my magisk modules with install/reinstall, i immediately restore from nandroid backup with clean magisk
( plus one google camera patch module only. )
So have anyone got anything worked on our new OOS 5.0 ?
preferably with Dolby atmos working ? i've never tasted this one on my 1+ device ever...
I also couln't get V4A to work with Magisk so I tried the one that I also have used in 7.1.1 and it seems to be working without any issues for now.
The link : https://androidfilehost.com/?fid=457095661767141554
Just flash it and you're good to go
Best Regards, Talpes
nicknacknuke said:
On 7.1.1 default OOS 4, I have mine worked just fine with the one coming from magisk repo.
I've tried the one from Magisk 14.5, processing says Abnormal..
and i can hear crackle sounds in the background when playing music.
Click to expand...
Click to collapse
If you're talking about the repo on the Magisk Manager, those V4A versions are horribly outdated.
Try the modules by ahrion, downloaded from the thread: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
I personally have v2.0 working perfectly with Magisk 14.3. But also needed SELinux permissive module to process properly. Yeah, I know, a of folks are not going to want to set SELinux to permissive. But I'm just sharing what worked for me.
v2.3 wouldn't work properly for me. But one of the devs told me that I should delete all V4A and AML (Audio Mod Libs) and try to install through TWRP. Haven't had a chance to retry it doing all that. If you still have troubles, you can post the TWRP recovery log on the above thread, and they will try to help you out.
Dolby Atmos does not work on Oreo. Do NOT flash, bootloop is a possiblity.
This is how I got V4A working with OOS oreo. I had to set SELinux to permissive.
1. Use Magisk v14.5
2. Install 'Magisk SELinux Permissive Script' module by jman420 from within magisk manager (Modules -> + button -> select file)
https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549
3. Reboot. Optional - Install 'Display SELinux status' module in magisk
4. Install 'Viper4Android FX for Magisk v14+' v4.0 by ShadySquirrel in magisk manager. You can get it from Magisk repo. (Other V4A modules might work too.)
5. Reboot and voila!
Okay... so far there are 3 alternatives to get this audio mod in Oreo
I will try them and test...
Let's say, this is my attempt to keep track of how to install in oreo..
Thank you guys for all the suggestions ( and warning ! )
talpes said:
I also couln't get V4A to work with Magisk so I tried the one that I also have used in 7.1.1 and it seems to be working without any issues for now.
The link : https://androidfilehost.com/?fid=457095661767141554
Just flash it and you're good to go
Best Regards, Talpes
Click to expand...
Click to collapse
did this version require any SELinux permissive trickery?
Brian
Yes it does but you don't have to install separate apps or magisk modules to archive that. After you flashed the whole thing, open Viper - Settings - Turn on developer mode and disable SELinux. That's it.
Talpes
redpoint73 said:
If you're talking about the repo on the Magisk Manager, those V4A versions are horribly outdated.
Try the modules by ahrion, downloaded from the thread: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
I personally have v2.0 working perfectly with Magisk 14.3. But also needed SELinux permissive module to process properly. Yeah, I know, a of folks are not going to want to set SELinux to permissive. But I'm just sharing what worked for me.
v2.3 wouldn't work properly for me. But one of the devs told me that I should delete all V4A and AML (Audio Mod Libs) and try to install through TWRP. Haven't had a chance to retry it doing all that. If you still have troubles, you can post the TWRP recovery log on the above thread, and they will try to help you out.
Click to expand...
Click to collapse
On my attempt with your method, It installs just fine with TWRP, but fail on running.
- Installed just fine with TWRP, no errors. (*)
- Reboot, but i can not find the V4A apps in drawer...
- So i opened up the zip file, extract the APK from v4afx-v2.3.zip/system/app/ViPER4AdnroidFX.apk.
- Install it manually, then it shows up in drawer.
- Everytime i try to run it.. it keeps asking to install drivers. I assume because it wasn't install in /system
( confirm install, reboot, then it asks to install again when i open it ).
So i decide your method does not works well on my device... or i may have missed something in the steps.
( Stock OOS 5.0, Bluspark's 8.54 TWRP, Magisk 14.5 )
fluster84 said:
This is how I got V4A working with OOS oreo. I had to set SELinux to permissive.
1. Use Magisk v14.5
2. Install 'Magisk SELinux Permissive Script' module by jman420 from within magisk manager (Modules -> + button -> select file)
https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549
3. Reboot. Optional - Install 'Display SELinux status' module in magisk
4. Install 'Viper4Android FX for Magisk v14+' v4.0 by ShadySquirrel in magisk manager. You can get it from Magisk repo. (Other V4A modules might work too.)
5. Reboot and voila!
Click to expand...
Click to collapse
Your method works OK on my device :good:
so we are only limited to v4A ? no Arise, or Dolby atmos ?
i see some OP3T users saying they got it working on their device with Oreo ..
talpes said:
I also couln't get V4A to work with Magisk so I tried the one that I also have used in 7.1.1 and it seems to be working without any issues for now.
The link : https://androidfilehost.com/?fid=457095661767141554
Just flash it and you're good to go
Best Regards, Talpes
Click to expand...
Click to collapse
It said aroma, i'm on stock ROM.. is it safe ?
I will take nandroid backup and try it...
EDIT:
My mistake for not understanding aroma installer.
Tried your method, only install v4a 2.5, and DD Plus..
No errors, when playing music, V4A says abnormal. Second tries, i can not even get the Driver Status to popup.
Dolby Digital seems to work, but it quit everytime i changed the mode, but sound does noticably change.
*rolling back to nandroid backup*
nicknacknuke said:
On my attempt with your method, It installs just fine with TWRP, but fail on running.
- Installed just fine with TWRP, no errors. (*)
- Reboot, but i can not find the V4A apps in drawer...
- So i opened up the zip file, extract the APK from v4afx-v2.3.zip/system/app/ViPER4AdnroidFX.apk.
- Install it manually, then it shows up in drawer.
- Everytime i try to run it.. it keeps asking to install drivers. I assume because it wasn't install in /system
( confirm install, reboot, then it asks to install again when i open it ).
So i decide your method does not works well on my device... or i may have missed something in the steps.
( Stock OOS 5.0, Bluspark's 8.54 TWRP, Magisk 14.5 )
Click to expand...
Click to collapse
You tried ahrion's module, v2.0 like I said (you listed all other version number details but that one)? Newer ones don't work for me; I tried 2.3 and 2.4, and same error you have - no V4A app in app tray.
Also, I'm on Magisk 14.3 (as mentioned) so another variable there.
redpoint73 said:
You tried ahrion's module, v2.0 like I said (you listed all other version number details but that one)? Newer ones don't work for me; I tried 2.3 and 2.4, and same error you have - no V4A app in app tray.
Also, I'm on Magisk 14.3 (as mentioned) so another variable there.
Click to expand...
Click to collapse
Could you upload v2.0?
redpoint73 said:
You tried ahrion's module, v2.0 like I said (you listed all other version number details but that one)? Newer ones don't work for me; I tried 2.3 and 2.4, and same error you have - no V4A app in app tray.
Also, I'm on Magisk 14.3 (as mentioned) so another variable there.
Click to expand...
Click to collapse
my bad for not paying attention
but i'm a bit reluctant to downgrade my magisk
i've managed to get mine working as per Post #5,
i saw there's a new version just came out from ahrion ( v4afx-v2.4.zip , 11/30/2017 ).
I might gonna give it a try also with magisk 14.5...
Phone: LG Aristo (LGMS210)
ROM / Android version: Android 7.0
Root (yes/no): Yes
Xposed, or any other modifications: no
Any physical damage prior to defect: no
Magisk Manager keeps stopping. I opened it today and I got the message "Magisk Manager has stopped, open app again" I can't open it without it crashing. I've tried clearing cache, clearing data, reinstalling the APK. What do I do? This is a very big problem as i cannot run any rooted apps without getting the message that magisk has stopped.
Logcat (use ADB)?
Have you tried uninstalling Magisk and then reinstalling?
Have you tried uninstalling Magisk and then reinstalling?[/QUOTE]
I have tried clearing data, clearing cache, and uninstalling and reinstalling. I am VERY new to this so any help is good help.
MMJv3 said:
I have tried clearing data, clearing cache, and uninstalling and reinstalling. I am VERY new to this so any help is good help.
Click to expand...
Click to collapse
When you say you've uninstalled and reinstalled, are you talking about Magisk or the Magisk Manager? I'm talking about completely uninstalling Magisk by using the uninstall zip.
And what about that logcat?
I've got a similar problem. Mgisk Manager keeps crashing, but If I'm not connected to the internet the APP runs fine,
dafreaking said:
I've got a similar problem. Mgisk Manager keeps crashing, but If I'm not connected to the internet the APP runs fine,
Click to expand...
Click to collapse
Likely caused by a bug with checking the Magisk repo. It's been fixed but not yet released.
Clear Repo Cache
Disconnect from internet, go to settings and clear the repo cache helped me to open it again
Didgeridoohan said:
When you say you've uninstalled and reinstalled, are you talking about Magisk or the Magisk Manager? I'm talking about completely uninstalling Magisk by using the uninstall zip.
And what about that logcat?
Click to expand...
Click to collapse
I am facing the same issue. Magisk Manager crashes as soon as I open it (precisely within 3-5 sec of opening the app). Though the root is working perfectly and all apps requiring root behave as intended.
I am attaching a magisk log taken from the magisk manager within the 3-5 seconds window.
Kindly let me know if it's the correct log. I am a noob and still learning the intricacies.
Any help/guidance will be greatly appreciated
Magisk Manager works for me when I wait for a few seconds after opening the app. Cool Tool shows high CPU activity right after starting MM. Once the CPU idles again, MM works without crashing.
This is not a fix, but it may help until a new version gets released.
Didgeridoohan said:
Likely caused by a bug with checking the Magisk repo. It's been fixed but not yet released.
Click to expand...
Click to collapse
v5.8.0 just released does fix this.
Didgeridoohan said:
Logcat (use ADB)?
Have you tried uninstalling Magisk and then reinstalling?
Click to expand...
Click to collapse
Hi, Magisk crash when I go to download and try to search any moudle under it as soon I type two three words it crashes , I tried to use 16.7, 17.1 fresh install but still it does the same
I dont have any xposed root works fine, Im on crDroid Oreo running on g900v unlock bootloader
zfk110 said:
Hi, Magisk crash when I go to download and try to search any moudle under it as soon I type two three words it crashes , I tried to use 16.7, 17.1 fresh install but still it does the same
I dont have any xposed root works fine, Im on crDroid Oreo running on g900v unlock bootloader
Click to expand...
Click to collapse
I encounter the same issue today !!
eric672913 said:
I encounter the same issue today !!
Click to expand...
Click to collapse
Enter this url in the Magisk Manager settings, update channel,custom:
https://bit.ly/2MPKGY5
zfk110 said:
Enter this url in the Magisk Manager settings, update channel,custom:
https://bit.ly/2MPKGY5
Click to expand...
Click to collapse
Great! Thanks a lot.
For those of you that remain stuck on this issue: Magisk Manger doesn't like being used from an external SD card. If that is the case (see app menu) move it back to internal memory. It will work properly then.
JoostA said:
For those of you that remain stuck on this issue: Magisk Manger doesn't like being used from an external SD card. If that is the case (see app menu) move it back to internal memory. It will work properly then.
Click to expand...
Click to collapse
Thanks for this! Was exactly my problem.
Phone: Sony Xperia Z3 Compact (D5803)
ROM / Android version: Android 7.1.2 (LineageOS)
Root (yes/no): Yes
Xposed, or any other modifications: AFwall+ 3.0.4 (IPv6 disabled)
Any physical damage prior to defect: no
After flashing new LineageOS + Magisk.zip and installing the Magisk Manager Apk, the app is also crashing with no internet connection for me. But if I make airplane mode on, then it does work for me.
Magisk not opening or crashing again and again.
First of all desable or uninstall your superuser app and then open magisk manager app again it's very simple. When you done all of magisk installation then you can again activate or install your superuser app.
If it is not working then please tell me i can help you.
Nexus 6, 7.1.1, Magisk root - Google play and Magisk Crashing
Making a long story as sort as I can my Nexus 6 running Magisk to hide the root from Google play, and a stock 7.1.1 ( 7.1.1 (N6F27M, Oct 2017 if it matters) google image, was working flawlessly a couple years ago when I stopped using it.
A few weeks ago I turned it on, clicked Google play and it never opens. Just hangs on the app loading screen unless I disconnect the internet from it. I read somewhere that this may be an issue from something that Google implemented since then In there play services to detect root.
Connected to the internet (WiFi) I opened Magisk and was able to update the Manager app before it quickly crashed. I opened it again and there seems to be a Magisk update but app crashes too fast for me to click update.
What is going on here and/or how do I fix this?
Nexus 6, 7.1.1, Magisk root - Google play and Magisk Crashing SOLVED
jhavron said:
Making a long story as sort as I can my Nexus 6 running Magisk to hide the root from Google play, and a stock 7.1.1 ( 7.1.1 (N6F27M, Oct 2017 if it matters) google image, was working flawlessly a couple years ago when I stopped using it.
A few weeks ago I turned it on, clicked Google play and it never opens. Just hangs on the app loading screen unless I disconnect the internet from it. I read somewhere that this may be an issue from something that Google implemented since then In there play services to detect root.
Connected to the internet (WiFi) I opened Magisk and was able to update the Manager app before it quickly crashed. I opened it again and there seems to be a Magisk update but app crashes too fast for me to click update.
What is going on here and/or how do I fix this?
Click to expand...
Click to collapse
Updated Magisk Manager and was able to download the updated apk using the manager. I then rebooted to recovery and installed the new APK, cleared delvik, & cache, rebooted. Bam! SOLVED
Again I face a problem, now if I hide any application the application doesn't work or open, every time it crashed.
My device: Honor 8
This is happening with me on LG G6. Hide is enabled in options and when I want to enter Magisk Hide to enable it then Magisk crashes.
Logs?
Aid777 said:
This is happening with me on LG G6. Hide is enabled in options and when I want to enter Magisk Hide to enable it then Magisk crashes.
Click to expand...
Click to collapse
I had that problem on LG V30. I reverted to 16.0 with Manager 5.9.1, and the problem persisted. I then downgraded Manager to 5.8.3, and it's working fine again with the older version of Manager.
MechanicaIMan said:
I had that problem on LG V30. I reverted to 16.0 with Manager 5.9.1, and the problem persisted. I then downgraded Manager to 5.8.3, and it's working fine again with the older version of Manager.
Click to expand...
Click to collapse
5.9.1 seems to be 17.0 zip. I assume you meant that
5.8.3 is 16.7
When you downgrade do you just flash the zip or do you need to uninstall the 17.1 Magisk then flash this downgraded one?
I'm getting this exact same issue, I've attached logcat and magisk logs after hiding the Play Store with Magisk Hide, then attempting to open it (and having it immediately crash). Magisk 17.1, latest Magisk Manager app, Pixel 2XL, Oreo 8.1 (July patch). Apps open again after deselecting them from Magisk Hide. Was working fine on 16.4, stopped working after 17.1, and a complete Magisk uninstall/reinstall did not fix it.
Magisk Log, Logcat.
Aid777 said:
5.9.1 seems to be 17.0 zip. I assume you meant that
5.8.3 is 16.7
When you downgrade do you just flash the zip or do you need to uninstall the 17.1 Magisk then flash this downgraded one?
Click to expand...
Click to collapse
I had the problem after updating from 16.0 with 5.8.3 to 17.1 with 5.9.1, but I also tried using the newest manager with 16.0, and that didn't work either. So there must be some kind of issue with the newest version(s) of the manager. I completely uninstalled 17.1, flashed 16.0, updated manager to 5.9.1 (crashing returned), then uninstalled 5.9.1 and installed the 5.8.3 apk without changing Magisk. If you have 17.1 installed now, then you might want to try just replacing manager with an older version before you bother with completely uninstalling/downgrading Magisk. You can simply uninstall the manager app without uninstalling Magisk, but I don't know if Magisk 17 will work okay with the older versions of manager, since I haven't tried that myself and don't really know anything about Magisk.
It is the same with me
Google Play Store crashed
Same here guys with LG g6, I installed the 17.1 by direct installation (within the app) and then when I go to magisk hide, it keeps crashing!
I've had the exact same experience as @mechanicalman on my V30+ (US998).
Any solution guys.
same with me, would appreciate somebody to have a look.
Magisk Hide tickboxes in Magisk Manager make Oreo crash
Hi, same with me: Oneplus3 with stock OOS 5.0.5 (oreo), dm-verity warning at boot since when I was a superSU user.
Everything was fine with Magisk 16. Since update to 17.1 and MagiskManager 5.9.1, the Magisk Hide menu keeps crashing. I've reflashed the stock ROM, reinstalled magisk 16 and 17.1, used the magisk deinstaller. The problem seems tied with MagiskManager 5.9.1
- In the MagiskHide menu, sometimes I can check 5 to 10 apps before it crashes.
- In the MagiskHide menu, sometimes only 1 check or 1 uncheck makes the phone crash.
When MagiskHide crashes it:
- blacks out the screen for a few seconds
- then starts a reboot (a soft reboot where I am not asked my device password, which I have set to be asked during boot)
- then it eventually launches Android after a very long time (usually OOS 5.0.5 opens after 20 cycles of the animation, but after a MagiskHide crash, it can take 200 cycles (from which I stop counting))
I attached the Magisk log immediately after reboot, which doesn't say much (some lines similar to previous and following ones removed).
MagiskManager: "Preserve force encryption" is on (default), "Preserve AVB 2.0/dm-verity" is off (default), Modulues are Busybox, MM for recovery, Xposed, YouTube Vanced, rest of settings are default.
I hope that helps narrowing down the problem.
I'm coming here with this issue occurring on my LG V30+ and Magisk 17.1
Hi, I'm having the same problem as a couple of people, magisk 17.1, newest Magisk Manager, then when I try to go into the magisk hide menu, the app crashes to home screen.
I enabled core only mode to see if it was any of my modules but the problem persists.
lenovo p2 same problem of manager crashing when entering hide menu
Same problem on my Nexus 5, Dirty Unicorn with Oreo 8.1
Same problem here on the V30+. Anyone able to confirm downgrading works?
Also, what do most of y'all use hide for? I was gonna try to use it to set up chase pay for that 5% rewards. lol
Didgeridoohan said:
Logs?
Click to expand...
Click to collapse
Magisk Manager v6.0.0, OOS9.0 OnePlus 6. App crashes while opening Magisk hide menu. Thanks
Guys I'm in a major fix here. Any help would be appreciated.
K20 Pro Global Version - Currently on MIUI Global 11.0.1.0(QFKMIXM)
Rooted via Magisk
Everything was perfectly fine until I noticed 'microG installer Revived' on Magisk and decided to install it.
After I rebooted, Youtube Vanced wouldn't open stating that it won't run without Google Play Services. Same issue with Gmail as well. I went into the microG settings and accepted all the missing permissions. Added my Gmail account, signed in and accepted all the other permission pop-ups that came after.
Despite this everything is still messed up. Gmail and Youtube still gives the same error msg and Chrome keeps crashing.
I tried uninstalling microG but that was an even bigger mistake as the Google Play Services I installed via apk kept crashing.
If someone could pls guide me on how to get the system to how it was prior to the microG installation :crying:
So I managed to fix it somewhat. Uninstalled microG then installed the right version of Google Play services as well as the calendar and contacts sync apks.
No more crash messages but the issue I'm having now is that some app notifications don't work and others (such as Whatsapp) work only sometimes.
And for some really weird reason my Gmail no longer is (or has the option) in dark mode.
Anyway to fix these issues guys?
I've the same problem with my Huawei Mediapad M5 tablet. I've tried to reflash the original "SYSTEM.img" from fastboot mode, but nothing changed. I don't want to do a full reinstall because of this mistake, is there any solution?
Messing with microG is a recipe for disaster because in and of itself it is disastrous, reflash the firmware from scratch and use the Vanced magisk version even though it isn't the last version it works just fine
heynando said:
Messing with microG is a recipe for disaster because in and of itself it is disastrous, reflash the firmware from scratch and use the Vanced magisk version even though it isn't the last version it works just fine
Click to expand...
Click to collapse
It's an absolute nightmare, not sure why the devs don't just update the Magisk version, and I agree the Magisk version works perfectly fine
MicroG works only on systems that don't have GAPPS. That should have been included in the documentation.
I had the same problem (I installed the microG installer revived on a cell phone that had google play services, which caused me that error; I installed the magisk module without knowing what it was for), I solved it by doing the following:
1. Uninstall micro-g and google play services and then restart the terminal.
2. Download and Install (install as system application with lucky patcher) the latest version of the google play services apk, restart.
3. Log out or remove google account from device, reboot device.
4. Login or add google account on the device again, restart the device for the last time; and voila problem solved.
I can't remove my account for some reason, and also I can't add a new google account
Hi Guys, have the same problem. has anyone found a solution? would hate to reset it
Trying to work out what it could be for the first post. It sounds like MicroG was installed while the Google Play services were already on the device.
I have actually manually removed Google Services using the debloater magisk module and run it via terminal.
I'm currently using CrDroid Android 12 and it's working fine with MicroG revived version. I have been testing the Android 13 with MicroG and have issues with the Play Store signing in
Hi. I recently updated my Moto G5s Plus(Sanders) from Android 10 to Android 11(PixelExperience). I used Magisk v21 while installation and everything worked fine. Then I installed the the v22 update through the app. However after downloading and opening the new Magisk, it shows that Magisk isn't installed and that there are updates for both Magisk and Magisk manager. Upon clicking install for manager, nothing happens, no downloading or anything. But on clicking for Magisk, it shows a select and patch method, which I don't know what to do with .
Attaching screenshot below.
Did you by any chance have the Magisk app repackaged with a random name before updating? When moving to v22+ from older releases you need to do that with the app unhidden.
If you did have the app hidden before updating you might now have two apps installed, but you should be able to fix that by uninstalling both and installing the v22.1 apk again manually.
Didgeridoohan said:
Did you by any chance have the Magisk app repackaged with a random name before updating? When moving to v22+ from older releases you need to do that with the app unhidden.
If you did have the app hidden before updating you might now have two apps installed, but you should be able to fix that by uninstalling both and installing the v22.1 apk again manually.
Click to expand...
Click to collapse
Oh my, I actually did have it hidden. I just noticed the dual apps( I think I didn't notice it before because the second one had the default android logo icon) l. Much thanks for the help