I have installed Custom recovery and rooted my phone to install Viper4android . But After installing viper it's not working in my phone. Turning on viper doesn't change sound quality or anything in my phone. So alternatively I tried using dolby atmos app but that app force closes itself. Plz help if any knows a walkaround for this issue.
Ty in advance.
Do you checked your root status ?
if it wasn't root ,just use the Magisk to root and in magisk modules , install viper and dolby magisk modules and restart your device ,this will works.
In root checker app its shown that the phone is rooted.
I havnt installed magisk yet. Should i install it and try?
Can u please share instructions to install magisk.. Ty.
Check your Selinux mode. It must be permissive
Okay when I got my phone the agreement with my parents was that I was not allowed to root my phone. I'm trying to install Viper4Android but I keep having problems with Busybox or installing the driver. Can/does anyone make/have a zip that can install Busybox, Viper4Android, and the Viper4Android Driver?
I have managed to get Dolby Atmos but nothing more.
Phone: LG Stylo 2 Plus
Android Ver: 6.0.1
Recovery: TWRP
Root: No and not allowed.
there is one in the viper fx forum, just use search button
Hi guys,
Just got notified that new magisk is available for install. Is it stable and working with the v30 (running Oreo v21a)?
I had a magisk update soft brick some phones before that's why I'm asking...
Cheers
clouds5 said:
Hi guys,
Just got notified that new magisk is available for install. Is it stable and working with the v30 (running Oreo v21a)?
I had a magisk update soft brick some phones before that's why I'm asking...
Cheers
Click to expand...
Click to collapse
See the last few pages of WTF thread. 17.0 boot loops. 17.1 fixes boot loops, but best to uninstall 16 Magisk in TWRP before installing 17.1. Run the uninstaller.
However, there's problems with Magisk Hide on 17.x right now. It crashes for a lot of people.
Thx, I'll stick with 16.0 for the moment. No issues with it and I'm not missing anything so...
17.0 made my stock rom bootloop.
17.1 works fine for me.
It probably makes no difference how you install it, but I used the patch boot image option then flashed the patched boot.img using fastboot.
use dd to get an image of your currently working boot partition
patch that boot.img with magisk manager to 17.1 and copy to PC
use fastboot to flash that patched_boot.img and then reboot (or fastboot boot TWRP.img then reboot from there to be extra safe)
I'm on 21B and that works for me. I have not tried a different way so I can't confirm/deny any other method yet
Sent from my LGE V30 using XDA Labs
21a here i just clean flashed with 17.1 ._.
I'm getting issues with 17.1 and magisk hide.. Is there any fixes? Thanks in advance
So just want to make sure.. can I run the magisk Uninstaller by flashing the zip in TWRP and the flashing 17.1 in TWRP to reinstall magisk?
Hi All,
Just to let people know. I believe the issue is with the Magisk Manager App. I'm currently still using Magisk 17.1. However, I've uninstalled the Magisk Manager and re-installed Magisk Manager 5.8.3 instead. I can now use Magisk Hide without crashing. Maybe others can give this a try as well.
silver311 said:
Hi All,
Just to let people know. I believe the issue is with the Magisk Manager App. I'm currently still using Magisk 17.1. However, I've uninstalled the Magisk Manager and re-installed Magisk Manager 5.8.3 instead. I can now use Magisk Hide without crashing. Maybe others can give this a try as well.
Click to expand...
Click to collapse
This worked for me as well.
1. Uninstall Magisk 16 in TWRP using the latest MagiskUninstaller.
2. Flash Magisk 17.1
3. Boot up and un-install MagiskManager 5.9.1
4. Install MagiskManager 5.8.3.
As expected, the SafetyNet check doesn't work but some of the modules I use are being updated to the new template which prevents them from running on Magisk 16.0.
Anyone know how to get rid of the pop-up to update MagiskManager every time the app is opened?
The lastest pop-up on MagiskManager shows the 6.0 version and the changelog shows that it is designed for Magisk 17.2
Anyone has tried with these new modules?
trekminal said:
The lastest pop-up on MagiskManager shows the 6.0 version and the changelog shows that it is designed for Magisk 17.2
Anyone has tried with these new modules?
Click to expand...
Click to collapse
Yes, discussed over in WTF thread.
https://forum.xda-developers.com/showpost.php?p=77687418&postcount=1798
Thanks.
I updated to MagiskManager 6.0 but it shows me the option to update to Magisk 17.1, not the 17.2
I will wait some days until 17.2 will be available through the main app.
Any else have magisk manager crashing when using selecting #magisk hide from the magisk manager menu?
running 20d us998
with magisk 17.1
magisk manager 6 (although 5.9.1 did the same thing)
and root checker remover
someone on the magisk support thread recommended deleting the hidelist file which didn't really do anything. Problem is still occuring even with the new hidelist.
I tried to root my umidigi a1 pro by patching the boot.img . The installation fine and after flashing the boot.img using fastboot i rebooted and opened magisk manager. When i opened magisk manager it said magisk was not installed but after i refreshed it said magisk was installed and that i need to install a additional setup. When i try to download the additional setup it says setup failed. I used a root checker which also says my phone is not rooted. What can i do about this?
umidigi a1 pro running stock firmware with custom recovery (twrp)
Hello all!
Code:
Standard disclaimer, don't blame me if your house catches fire, you're choosing to mod your device.
Device must (obviously) be bootloader-unlocked.
Steps (do them in order):
Magisk 19.3
Download magisk and flash in TWRP, then reboot.
riru-core 19.5
Download riru-core and either flash from Magisk Manager or flash in recovery, and then reboot again.
EdXposed 0.4.6.0 and EdXposed Manager
This version of EdXposed is the only one that supports Android Q, even the beta doesn't yet. So you have to use this specific version. Install the manager apk, then flash the zip in either magisk or TWRP. Reboot to apply changes.
Now you can use any xposed module that you wish.
https://forum.xda-developers.com/Mi-9/help/edxposed-xiaomi-eu-9-8-29-android-q-t3963437
safety net passing?
gryffynmp said:
Hello all!
Device must (obviously) be bootloader-unlocked.
Steps (do them in order):
Magisk 19.3
Download magisk and flash in TWRP, then reboot.
riru-core 19.5
Download riru-core and either flash from Magisk Manager or flash in recovery, and then reboot again.
EdXposed 0.4.6.0 and EdXposed Manager
This version of EdXposed is the only one that supports Android Q, even the beta doesn't yet. So you have to use this specific version. Install the manager apk, then flash the zip in either magisk or TWRP. Reboot to apply changes.
Now you can use any xposed module that you wish.
Click to expand...
Click to collapse
Why magisk 19 3? 19.4 not working?
smohanv said:
safety net passing?
Click to expand...
Click to collapse
SafetyPatch-v3.zip, it's a magisk module.
g_seva said:
SafetyPatch-v3.zip, it's a magisk module.
Click to expand...
Click to collapse
Hi, Thank you so much.
I was trying MagiskHide Prop (https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228) and failed flashing on my Android Q (Xiaomi Mi 9, MIUI 11 running). I flashed the patch you shared here. I flashed in Magisk and it passed safety net (CTS Profile pass).
I am now able to use Google Pay.