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.
Hi friends i'm Dhinesh. Now i'm currently using the redmi 5 plus/note 5 vince mobile. And now i'm using Pixel experience Pie version. My problem is non-rootable. I tried magisk and supersu zip and flashed. But it doesn't works. I tried many times to root. But forever the Root checker app says "Sorry! Root access is not properly installed on this device. I don't know what i do to root my device. So friends Please help to root my device successfully.
Thank you,
Dhinesh TP
Install magisk manager apk manually after flashing magisk 18.1 zip and booted into system.
It's a known problem in pie.
jes0411 said:
Install magisk manager apk manually after flashing magisk 18.1 zip and booted into system.
It's a known problem in pie.
Click to expand...
Click to collapse
Ok brother. I will try
Since I'm having a lot of issues with Magisk in realme xt (not that Magisk is bad, I'm not figuring out how to install it correctly), is there another way of acquiring root privileges in Resurrection remix (or any other custom ROM)?
I really need it.
Great! I've figured it out. I'm posting it here for anyone else that might land here.
Although Magisk installation instructions at Github recommend the patched boot.img method, it doesn't seem to work with the realme xt. So, you must use the "legacy method", which is also stated in every ROM installation instructions here: just install magisk.zip from TWRP., after your first boot to system (anyway, that's how I did it). There is no need to patch anything.