So, I've been reading posts about the Magisk version that is safer to install with OOS 5.1.8. A lot of them say that Magisk 16.0 stable is safe, some other say that you need the 16.6 version cause it creates less problems. So, my question is: which one do I use?
Also, if for some reason I use a version that creates problems, does using the Magisk uninstaller remove all the problems?
rickyjumb said:
So, I've been reading posts about the Magisk version that is safer to install with OOS 5.1.8. A lot of them say that Magisk 16.0 stable is safe, some other say that you need the 16.6 version cause it creates less problems. So, my question is: which one do I use?
Also, if for some reason I use a version that creates problems, does using the Magisk uninstaller remove all the problems?
Click to expand...
Click to collapse
I used 16.0 on 5.1.8 without any Problems.
I've been using 16.42(1642) beta up until 16.6 was released a week or so ago. It flashed just fine in the Magisk app and have had zero issues. Works well with ex kernel as well.
16.4 until last week, now 16.6 here, no problems at all
(started with OOS 5.1.6 - 5.1.8 now)
rickyjumb said:
So, I've been reading posts about the Magisk version that is safer to install with OOS 5.1.8. A lot of them say that Magisk 16.0 stable is safe, some other say that you need the 16.6 version cause it creates less problems. So, my question is: which one do I use?
Also, if for some reason I use a version that creates problems, does using the Magisk uninstaller remove all the problems?
Click to expand...
Click to collapse
Uninstaller will remove any problems unless you used something to debloat something. Then you would have to reflash system.
Lol
hi all
sorry if this post is off topic
i am having a problem with the latest magisk 17.1 ,where my banking app is not working as it triggered thaf the phone was rooted.
i do not have this problem with 16.1 stable version
my question is how can i install back the old version without twrp?
Related
Hi guys! I am having some issues when trying to install magisk. I am currently running the latest twrp-3.2.2-0-enchilada. When trying to install magisk I'm currently having a constant error. Attached are the recovery log and a screenshot.
Magisk Error 1 fix
Hi, it looks as though you are trying to install an unsupported version of magisk you need to use the 16.4 installer not the 16.0 installer this will most likely fix your issue, I hope this helped. PS it is a beta version of magisk not the latest stable build.
16 is the stable build and SHOULD work!
Did for me.
It looks like the problem was a bad install of magisk. I went to the forums of magisk and found an uninstaller. I flashes it and then flashes the stable version. It looks like it worked. I have root back.
I was thinking of trying to fix a few minor things like won't boot with charger plugged in and Google Pay getting screwed up every once in a while...but figured I would ask first.
To be safe I was going to nandroid backup, TWRP Magisk Uninstaller, TWRP Magisk 18.1 installer and try it out later on....it seems people have reported bootloops on other phones upgrading from the Magisk Manager app...
MW
I am in 9.0.3 but under xxx no limits magisk rom.
It works well
0xPraeT0Rian said:
I am in 9.0.3 but under xxx no limits magisk rom.
It works well
Click to expand...
Click to collapse
Using the new magisk 18.1 or 18?
You asked about 18.1.
I am on 9.0.3 with 18.1 magisk and the new magisk manager
Hi to all,
I am on OB12, and I'm no longer able to root since I tried to upgrade from Magisk 18 to 18.1
I already tried the 2 last versions of Magisk uninstaller and also to reflash OB12, but still impossible to root.
What is very strange is that if I flash Smurfkernel it says that I'm rooted, but after booting, no Magisk APK and impossible to install it !
Any suggestions?
Thank in advance for any help.
I have already had Magisk 18.1 on stock 9.0.3 and it was fine. I upgraded from Magisk 18 through Magisk manager.
No problems here.
b.huss2 said:
I have already had Magisk 18.1 on stock 9.0.3 and it was fine. I upgraded from Magisk 18 through Magisk manager.
Click to expand...
Click to collapse
This is the first think I did, but unsuccessfully: Magisk Manager gave an error message installation unsuccessful like if not rooted.
It's why I flashed the Magisk uninstallers in order to clean all previous installations that could create problems, but whatever I do, rooting is missing after booting.
Really strange...(and annoying)
OP here -- I updated and am having no issues, but I did it all through TWRP by uninstalling Magisk 18.0 first and then re-installing 18.1 before rebooting. I had already updated Magisk Manager from the app.
Only thing I noticed was I had to reset up all my settings (Magisk hide for Direct TV Now, and re SU authorize all root apps). First reboot everything was slow with root apps waiting for SU access before the request came through, but then everything was fine once it was granted.
michelD said:
This is the first think I did, but unsuccessfully: Magisk Manager gave an error message installation unsuccessful like if not rooted.
It's why I flashed the Magisk uninstallers in order to clean all previous installations that could create problems, but whatever I do, rooting is missing after booting.
Really strange...(and annoying)
Click to expand...
Click to collapse
You might could try dirty flashing your ROM and then try Magisk again. You could have something jacked up.
(of course don't forget about TWRP if you go dirty flashing your ROM)
b.huss2 said:
You might could try dirty flashing your ROM and then try Magisk again. You could have something jacked up.
(of course don't forget about TWRP if you go dirty flashing your ROM)
Click to expand...
Click to collapse
Yes I tried this too, but unsuccessfully !
And I'm even not sure that a full wipe will help, because it concerns another partition.
I've been dealing with this for a few months now. I'm currently on OxygenOS 9.0.7 stable, i updated today. I noticed a while back in OxygenOS 5.8.5 (oreo) that when i opened the magisk app it said that i had magisk installed, after some seconds the app crashed and said that magisk (19.1 at the time) wasn't installed so i decided to update to pie (oos 9.0.4 iirc) and flashed magisk 19.1 but yet again, i got the same results. I flashed magisk 17 and it did the same thing so i decided to flash magisk 18 and disable magisk updates and that worked but only on pie. Now i updated today to OOS 9.0.7 and when i flash magisk 18 right before the boot animation completes the phone shuts off so i can't use magisk 18. I flashed 19.3 and the app didnt crash but it uninstalled itself after a few hours after the first boot on 9.0.7. I noticed the same behavior with custom kernels and with oos beta.
This only happens with OxygenOS and not in custom roms, i don't want to use a custom rom because of high idle battery drain.
Also, this wasn't happening when i bought the phone. It started occurring in may after i returned to OOS from a custom rom.
I don't know what to do now, i guess i'll roll back to 9.0.6 untill i find a solution.
If someone has had or has the same problem please let me know.
People had this issue a long time. Many reports on 9.0.6 aswell (and prior tho this). Customs saved me from this, I'm on latest oos now and doesn't have any issues (yet I suppose) . I did a format tho when 9.0.7 got released.
Ever since I started to flash Magisk to both slots, I haven't encountered this issue.
For me just uninstall it full, flash full rom(optional but I did)
Reboot then install magisk again, hide all app in magisk hide, hide magisk manager and enable core magisk mode only for 1 day and use it after that it become stable
loque036 said:
I've been dealing with this for a few months now. I'm currently on OxygenOS 9.0.7 stable, i updated today. I noticed a while back in OxygenOS 5.8.5 (oreo) that when i opened the magisk app it said that i had magisk installed, after some seconds the app crashed and said that magisk (19.1 at the time) wasn't installed so i decided to update to pie (oos 9.0.4 iirc) and flashed magisk 19.1 but yet again, i got the same results. I flashed magisk 17 and it did the same thing so i decided to flash magisk 18 and disable magisk updates and that worked but only on pie. Now i updated today to OOS 9.0.7 and when i flash magisk 18 right before the boot animation completes the phone shuts off so i can't use magisk 18. I flashed 19.3 and the app didnt crash but it uninstalled itself after a few hours after the first boot on 9.0.7. I noticed the same behavior with custom kernels and with oos beta.
This only happens with OxygenOS and not in custom roms, i don't want to use a custom rom because of high idle battery drain.
Also, this wasn't happening when i bought the phone. It started occurring in may after i returned to OOS from a custom rom.
I don't know what to do now, i guess i'll roll back to 9.0.6 untill i find a solution.
If someone has had or has the same problem please let me know.
Click to expand...
Click to collapse
Keep magisk out of battery optimization.
°Washy said:
Keep magisk out of battery optimization.
Click to expand...
Click to collapse
That will not keep it from uninstalling. Needs to be installed to both slots and the issue is gone
qbanlinxx said:
Ever since I started to flash Magisk to both slots, I haven't encountered this issue.
Click to expand...
Click to collapse
I will install it in both slots to see what happens. Thanks for the advice.
°Washy said:
Keep magisk out of battery optimization.
Click to expand...
Click to collapse
That doesn't work
qbanlinxx said:
That will not keep it from uninstalling. Needs to be installed to both slots and the issue is gone
Click to expand...
Click to collapse
For me, keep magisk out of battery optimization solved my issue.
loque036 said:
I will install it in both slots to see what happens. Thanks for the advice.
Click to expand...
Click to collapse
How's it been working for you?
qbanlinxx said:
How's it been working for you?
Click to expand...
Click to collapse
No issues so far
So I just updated my pixel to Android 10. And besides the issue with getting TWRP to work, I've been trying, and failing, to get Magisk installed.
I havn't tried the newer Magisk beta yet. Does anyone know if this would work instead?
Thanks
it works with me with the latest TWRP and Magisk
henk-jan said:
it works with me with the latest TWRP and Magisk
Click to expand...
Click to collapse
Okay, so with TWRP 3.3.0 with the no-pin workaround, I wasn't able to install magisk 19.3. However, I was able to get the Beta 19.4 to work.
Does anyone know how to get Viper4Android working on 10.3.7?
I updated from 10.3.5 and I remember I had problems installing it on there too and I had to force stop the app before it would work each time. I've updated V4A to the 2.7.2.1 version through magisk and it just says Status: Abnormal, am I supposed to use a different one or?
If anyone knows, thanks
Use magisk for v4A
"I've updated V4A to the 2.7.2.1 version through magisk"
Has anyone managed to make it work? I'm installing it for the first time on 10.3.7 using magisk and I'm also getting the Status: Abnormal message.
Juwapa said:
Does anyone know how to get Viper4Android working on 10.3.7?
I updated from 10.3.5 and I remember I had problems installing it on there too and I had to force stop the app before it would work each time. I've updated V4A to the 2.7.2.1 version through magisk and it just says Status: Abnormal, am I supposed to use a different one or?
If anyone knows, thanks
Click to expand...
Click to collapse
Julortiz said:
Has anyone managed to make it work? I'm installing it for the first time on 10.3.7 using magisk and I'm also getting the Status: Abnormal message.
Click to expand...
Click to collapse
Hello guys,
So what I think that might prevent V4A to be working is having the latest version of Magisk installed. I had the same issue as you guys till I reverted back to Magisk v21.0 from v21.1.
Mr.FREE_Bird said:
Hello guys,
So what I think that might prevent V4A to be working is having the latest version of Magisk installed. I had the same issue as you guys till I reverted back to Magisk v21.0 from v21.1.
Click to expand...
Click to collapse
Thanks for the shout, Mr. Freebird. So yeah I guess it is a problem with new versions of Magisk. I tried on the newest update as well, 21.2, and still couldn't get it to work.
For Julortiz and anyone needing help getting it to work again, the exact steps I did were
- Downgrade Magisk to 21.0
- Download V4A 2.7.2.1 from Magisk and open the app but do not install driver yet
- Go back to Magisk and install Audio Modification Library but do not let Magisk reboot
- Go back to V4A and let it install the driver and reboot
- After reboot, open V4A, go to settings and check Legacy Mode
- Enjoy
Also this is probably really obvious, but make sure you screenshot or take note of all other modules you have installed because downgrading will delete all modules. Again this is probably obvious, just don't be dumb like me and lose all your other modules lol