Database Develop

Unsupported Magisk Version - Cannot Upgrade to 18.x from 6.x, but can't open Magisk 7

Rooted Pixel 2XL 9.0
No TWRP
Upgraded Magisk to 7.2 - get error, "Unsupported Magisk Version"
trying to upgrade to 19.x manually, but all guides say, "Then go open Magisk on your phone", which I can't do.
If I downgrade to 6.x, I cannot upgrade to 19.x. So what to do?
Apologies if this has been addressed, but I cannot find a solution

With your old version of Magisk and Manager installed, download the the update and flash it manually from the modules section (the "+" button).

Didgeridoohan said:
With your old version of Magisk and Manager installed, download the the update and flash it manually from the modules section (the "+" button).
Click to expand...
Click to collapse
did that, and ended up in a boot loop.
It would seem that with version 6.x, (or anything lower than 7.x), you can't upgrade to 18.x or higher. I tried this 2-3x and same result. Had to flash old patched_boot.img and was back where I started.

The Manager version shouldn't really matter when installing like that (it is a known working solution for your exact problem). You might have a module acting up and causing issues. Might be a good idea to uninstall Magisk and start out clean.
Booting TWRP and flashing the Magisk zip there could also be a thing to try.

Walsh_M said:
did that, and ended up in a boot loop.
It would seem that with version 6.x, (or anything lower than 7.x), you can't upgrade to 18.x or higher. I tried this 2-3x and same result. Had to flash old patched_boot.img and was back where I started.
Click to expand...
Click to collapse
I tried again, and it worked
1. I downgraded to 6.1 and when prompted to reboot, I just closed, and restarted.
2. I then upgraded to 18.1. Again, when prompted to reboot, I closed and then restarted manually.
There seems to be a bug with regard to rebooting straight from upgrading.

It's only a bug if you can consistently reproduce it, and preferably provide logs showing it happening. Until then it was just gremlins...

Keep root after update with Magisk and no TWRP

If you already have root with Magisk, and don't have TWRP on your otherwise stock ROM, it is easy to retain root after upgrade. I have done this the past 4 updates.
1) Install the update through system updates. Don't reboot.
2) Open Magisk Manager and select "Install to Inactive Slot (After OTA)." Press Magisk Reboot button to reboot.
If for some reason you don't get the choice in Magisk to install to inactive slot the first time, then do this:
1) Install the update through system updates. Don't reboot.
2) Open Magisk Manager and install Magisk. Don't reboot
3) Open Magisk Manager again and this time select "Install to Inactive Slot (After OTA)." Press Reboot button to reboot.

don't you have to restore first the stock boot image in Magisk, before downloading/installing the OTA?
https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
I haven"t done the procedure yet, but I"m gonna have to update soon before Q drops, I wanna stay in Pie

Nope. I just updated to android 10 (A6013_41_191214) using the same method, so that makes 5 updates. I am really glad I found this method that is so simple since I always used to dread updating and regaining root. Now it adds about 10 seconds to the process.
I did have to use the three-step process since I had not updated Magisk in a while and it wants to be on the latest version before it allows you to install to inactive slot. Unlike previous updates, I had to re-choose Nova as the default launcher.

This helped me after I hard bricked my phone trying to root android 10. Thanks!

H10N3 said:
This helped me after I hard bricked my phone trying to root android 10. Thanks!
Click to expand...
Click to collapse
No problem. When I said "I used to dread updating and regaining root" it was because i had bricked my phone trying to re-root after an update, too, so I was always on edge when doing it until I found this easy method.

It works for me from 10 oos to oos10.3

I did that, I'm now stuck on Bootloader warning screen, even after rebooting :/
Phone can't boot in fastboot, PC can't detect device anymore.
Edit: Managed to boot in fastboot mode (vol +/-/power), had to use MsmDownloadTool to unbrick.

Hi can anybody give me a hint how to procede?
- I was on 8.1 Oreo with my 1043 PL2
- did select System Update --> Android 10 (V4.16B)
- in magisk I selected "Install to Inactive Slot (After OTA)." + reboot
I just got a loop of white android one screens,
every third cycle "Android Recovery" is offering a selection of "Try again" or "Factory data reset".
Did I lose unlocked Boot loader?
Would some more retries help?
If I use "factory data reset" do I keep magisk - or would it be non rooted system?
Any hint to go to an android 10 rooted device is apreciated (preferrably with my data).
I id a TWRP BU of 8.1 system before update.
Would also a switch back to other "sltot" with 8.1 be possible?
cheers
lino
EDIT (29mar21):
since no answer,
- I selected "delete Data partition"
- Phone deleted all my data I had no BU (pictures, Download folder)
- installed MagiskManager, and at least I stayed rooted.
- now I have to setup may phone from scratch :'(
EDIT2: and I did not even realise that I that I stumbled in wrong thread (I was searching for Nokia 6.1 ... anyway)

woo that was close.
ok so, sorry, reviving from the future, hello!
for some reason, I followed this on a Nord. Bootloop.
A/B partitions!
fastboot --set-active=a

Is there a update guide for Magisk using LOS 19.1? This method does not work for LOS, only for OOS. It will give you a bootloop. I have been flashing Magisk's zip file under LOS recovery, but there should be another way to update Magisk without all that hassle. Magisk's direct install will not work.

Oneplus 7T bootloop for new magisk (with solution for booploop)

So, i updated magisk (version 21? EDIT: manager was set to upda te to beta, but 20.4 also bootloops :/ ). Before rebooting, also installed to inactive slot, cause.... If you can do it after a OTA update, why not doing it normally, right? Bootloop. Have to press both the power button and VOL up for it to turn off. Usually just the long press on power buttton would do the trick.
Oneplus 7T OOS 10.012 EU
SOLUTION for the bootloop:
- Installed TWRP 3.4.0.2
- Because it cannot access data partition nor transfer files via USB, i did adb push -p local-pc-file-here /tmp
- So, i installed OOS 10.0.13 from there and it booted fine, however without magisk even tough i installed it from /tmp as well right after the ROM install without reboot.
- Tried to reinstall magisk from TWRP (had to reinstall it too, as OOS deleted it), but it bootlooped again. So, i'll wait for a boot file with it.
Executing Magisk-uninstaller-20201003.zip on TWRP did NOT work, cause it couldn't mount the necessary partitions.
EDIT: I have no magisk modules, so i don't know why all of this mess :/

If magisk was already installed on the inactive slot before you patched it, the boot image gets corrupted (at least it always does on my 7T). Really shouldn't use the ota patch feature if you're not installing an ota

Allen77777 said:
If magisk was already installed on the inactive slot before you patched it, the boot image gets corrupted (at least it always does on my 7T). Really shouldn't use the ota patch feature if you're not installing an ota
Click to expand...
Click to collapse
Gotcha! All good now. BTW, if anyone needs, there's a patched boot file on 7T's forum for 10.0.13 EU.

I have the same issue with 10.0.13 HD65AA.
First I tried to do the full update like usual with installing Magis 21 into both slots before reboot but then I got stuck on the boot animation.
Tried a lot of things until I found this thread here. Once I got into TWRP I pushed the latest ROM over to the phone and installed it and I could get back into my phone again. But once I tried to install Magisk via TWRP or boot the patched image for 10.0.13 HD65AA from XDA I get stucked in the boot animation again. So I had to once again push the ROM to the phone and install it into the second slot and once again my phone boots again.
So for whatever reason there is an issue with Magisk and both 10.0.13 HD65AA and HD65BA. So at least for me for now no root.
Thank you very much for at least getting into my phone again without losing any data. :good:

Magisk v22.0 app does not patch boot image

I have been using Magisk for two years on my device (Moto G5S Plus). Some time ago I did an upgrade of the Magisk Manager app, unfortunately not knowing I should have unhidden it first. From that moment when I started the app, it would immediately stop. Today I finally had the time to dive into the problem. I uninstalled the Magisk app, and from TWRP uninstalled Magisk.
And now I am trying to install Magisk v22.0. I have downloaded and installed the latest Magisk app. When I start it, it shows my device has a boot ramdisk.
I downloaded the stock boot.img to my device, selected Install from the Magisk card, keep options as they are (keep AVB 2.0/dm-verity: off, keep enforced encryption: on).
At the Method step I selected the downloaded boot.img. When I tap "Go" (or whatever it would say with an English UI), nothing happend. I waited several minutes without anything happening.
The UI is responsive. I can go back and do it all over again, with the same result.
Why doesn't the app patch the image?
Is there anything else I can or should do eliminate traces of the old hidden Magisk manager app (besides a full restore, because without Magisk no root, without root no Titanium backup)?

gewe said:
I have been using Magisk for two years on my device (Moto G5S Plus). Some time ago I did an upgrade of the Magisk Manager app, unfortunately not knowing I should have unhidden it first. From that moment when I started the app, it would immediately stop. Today I finally had the time to dive into the problem. I uninstalled the Magisk app, and from TWRP uninstalled Magisk.
And now I am trying to install Magisk v22.0. I have downloaded and installed the latest Magisk app. When I start it, it shows my device has a boot ramdisk.
I downloaded the stock boot.img to my device, selected Install from the Magisk card, keep options as they are (keep AVB 2.0/dm-verity: off, keep enforced encryption: on).
At the Method step I selected the downloaded boot.img. When I tap "Go" (or whatever it would say with an English UI), nothing happend. I waited several minutes without anything happening.
The UI is responsive. I can go back and do it all over again, with the same result.
Why doesn't the app patch the image?
Is there anything else I can or should do eliminate traces of the old hidden Magisk manager app (besides a full restore, because without Magisk no root, without root no Titanium backup)?
Click to expand...
Click to collapse
It doesn't necessary to patch boot image. I had same problem.
Just install magisk 22 with TWRP, reboot...open magisk and install it.
You are ready and rooted.

Thanks for your quick reply. Problem solved!

Question Odd issue taking OTA update to Android 13 with Magisk (NE2217)

I have previously followed topjohnwu's guides to uninstall Magisk to install OTA updates but this one has me stumped.
The first time I took an OTA, I noted that the guide instructed not to select the update's reboot prompt--however, it did not prompt but rather just rebooted on its own. I lost root but the process of getting root again was not a big deal.
This time, however, I did get a prompt and ignored it, instead reinstalling the Magisk app first to an inactive slot and allowing Magisk to reboot the phone. I got into a bootloop and had to force the phone off. When I rebooted, it entered Android just fine, but it was as if the update never happened--I was still on Android 12 and the old security update. The Magisk app is still installed, but not Magisk itself and I lost root.
The strangest thing is that when I go back to the OTA update, it still says "Reboot", not install update, so it is clearly still wanting to do something on restart.
Any advice on the best way to proceed? Thanks.

icherub said:
I have previously followed topjohnwu's guides to uninstall Magisk to install OTA updates but this one has me stumped.
The first time I took an OTA, I noted that the guide instructed not to select the update's reboot prompt--however, it did not prompt but rather just rebooted on its own. I lost root but the process of getting root again was not a big deal.
This time, however, I did get a prompt and ignored it, instead reinstalling the Magisk app first to an inactive slot and allowing Magisk to reboot the phone. I got into a bootloop and had to force the phone off. When I rebooted, it entered Android just fine, but it was as if the update never happened--I was still on Android 12 and the old security update. The Magisk app is still installed, but not Magisk itself and I lost root.
The strangest thing is that when I go back to the OTA update, it still says "Reboot", not install update, so it is clearly still wanting to do something on restart.
Any advice on the best way to proceed? Thanks.
Click to expand...
Click to collapse
The phone storage where the OS resides is divided into two slots: A and B. Only one is active at a time. When you install an update it gets installed on the inactive slot (slot A if you're on slot B and slot B if you're on slot A). When you reboot after an update completed, the phone will mark the other slot as active and will boot from there. If the phone fails to boot for whatever reason it will revert to the previous active slot, effectively undoing the update. This is what indeed seems to have happened to you.
Now, there are two things I can't say why they happened:
- Why installing Magisk to the inactive slot made it unbootable.
- Why you lost root on the active slot.
You could try rebooting again to the inactive slot from the update prompt but it will probably fail and bring you back to the previous slot because I believe Magisk is still installed there and there is no option such as "uninstall from inactive slot". Anyway, I think it's something you should try, because in the worst case it will just repeated the same thing that happened the first time.

It sounds like you're in a pretty "dire" situation. Your phone has flipped its boot slot back to the safe one, and your other boot slot with the update is fried. For MAJOR Android updates, i.e. From Android 12 to Android 13, you must almost always FULLY Unroot and take the update, then reroot after the update.
I suggest safe updating all over again with a full zip using LocalUpdate apk from OPlus, fully unrooted, and just reroot when you're done.

the old way no longer works. because when updating to oos 13, the rom is flashed directly (this happens when the device writes extracting) and then the button appears with Install now (but if you click on it there, the cell phone restarts)
and if you don't click on Install now and go to magisk at this point and magisk into the inactive flash slot, the phone doesn't boot into the system but switches back to the non-updated slot in the background (you're then back in the old system) no idea if which is related to the virtual a/b.
That's why I do that I first do the update and restart and then simply patch the new boot.img (or init_boot.img for new devices) and flash it again.

Prant said:
It sounds like you're in a pretty "dire" situation. Your phone has flipped its boot slot bacl to the safe one, and your other boot slot with the update is fried. For MAJOR Android updates, i.e. From Android 12 to Android 13, you must almost always FULLY Unroot and take the update, then reroot after the update.
I suggest safe updating all over again with a full zip using LocalUpdate apk from OPlus, fully unrooted, and just reroot when you're done.
Click to expand...
Click to collapse
This is the correct (and most concise) answer

I just tried doing what you did and encountered the same thing. Wish I stumbled upon this post first.
Where can I get the A13 zip for NE2217 to do a local update? My slot b is A13 bootlooped with Magisk