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.
Related
I've installed a deodexed rom with Magisk but now I can't update past 15.x version of Magisk.
I tried to do it in the Magisk app, and trough TWRP both to version 16.0 and to version beta 16.1, but it always just hangs in the part "Flashing new boot image".
I've waited several hours in that part, but nothing.
I've also tried it with and without TWRP installed.
I think I'm missing some step here.
I always uninstall Magisk via TWRP and the latest official uninstaller prior to flashing an upgraded version. A bit cumbersome to once again configure all the settings in the modules, but it works for me.
I'm pretty sure i couldn't be the only one who recently updated from 16.0 to 17.0 (Stable Channel). I first updated the magisk manager and it prompted me to flash 16.0(1600) instead of a 17.0 version. Well since i flashed the 16.0(1600) version it prompted me to download, i got into a nasty bootloop and thankfully recovered with me having the stock ROM in my storage. I'm wondering if anyone else went through the bootloop i did this morning and if people should just flash the newer zips outside of the manager
HighOnLinux said:
I'm pretty sure i couldn't be the only one who recently updated from 16.0 to 17.0 (Stable Channel). I first updated the magisk manager and it prompted me to flash 16.0(1600) instead of a 17.0 version. Well since i flashed the 16.0(1600) version it prompted me to download, i got into a nasty bootloop and thankfully recovered with me having the stock ROM in my storage. I'm wondering if anyone else went through the bootloop i did this morning and if people should just flash the newer zips outside of the manager
Click to expand...
Click to collapse
I also got a bootloop but I flashed 17.0 through twrp. I had to go through the qualcomm drivers process to unbrick it because it was hard bricked lol
Flashed uninstall magisk and than magisk 17 and all worked well.
dracoboss said:
I also got a bootloop but I flashed 17.0 through twrp. I had to go through the qualcomm drivers process to unbrick it because it was hard bricked lol
Click to expand...
Click to collapse
That's horrible to have a hard bricked device. There's a hotfix that just got released right at this moment (17.1) so i'd recommend you to download that and continue the process to try getting root access back
Got the same problems as described here. Then I downloaded the latest Magisk uninstaller and Magisk 17 from the Magisk thread. The next step was to flash the uninstaller and afterwards Magisk 17 and the device booted well.
Running 17.1 and still getting the same thing with safety net check as before
The response is invalid
HighOnLinux said:
That's horrible to have a hard bricked device. There's a hotfix that just got released right at this moment (17.1) so i'd recommend you to download that and continue the process to try getting root access back
Click to expand...
Click to collapse
Yeah that's what I did and everything is fine... For now lol. Thanks
From Magisk 17.0 to Magisk 17.1, install it automatically. SafetyNet test successful
it's better and more secure deinstall first magisk manager clearing cache and data, install magisk 17.1 from twrp and if magisk manager doesnt be installed, install the apk
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.
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