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.
I hope this is the right place to ask, pardon me if not:
Issue: After upgrading to Android 11, the patched boot image causes bootloop, when patched using Magisk Canary
Phone/setup: Pixel 4 XL, updated today to Android 11 using OTA, which strangely enough worked just fine. Previously used the usual Magisk build, but grabbed Canary for this stuff. I'm flashing using latest ADB tools via download straight from Google + using original Pixel cable which so far has worked great with fastboot. Fastboot devices -l reports the phone.
Approach:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Download latest Canary build straight from github front page, moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.
Approach two:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot_a modified-image, fastboot flash boot_b modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.
Any idea what I'm doing wrong?
EDIT: Solution here! https://forum.xda-developers.com/showpost.php?p=83499831&postcount=23
delanvital said:
I hope this is the right place to ask, pardon me if not:
Issue: After upgrading to Android 11, the patched boot image causes bootloop, when patched using Magisk Canary
Phone/setup: Pixel 4 XL, updated today to Android 11 using OTA, which strangely enough worked just fine. Previously used the usual Magisk build, but grabbed Canary for this stuff. I'm flashing using latest ADB tools via download straight from Google + using original Pixel cable which so far has worked great with fastboot. Fastboot devices -l reports the phone.
Approach:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Download latest Canary build straight from github front page, moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.
Approach two:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot_a modified-image, fastboot flash boot_b modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.
Any idea what I'm doing wrong?
Click to expand...
Click to collapse
Pixel 4a here, just tried to follow OTA instructions and ended up bootlooped until I paused it. After resuming it rebooted but the update didn't take and magisk was uninstalled. I did have the safetynet fingerprint module installed so probably this caused an issue? Not sure it relates exactly to your problem but thought I'd chime in with a similar problem and model.
EDIT:
After this reboot where I lost magisk I retried the OTA and it succeeded. I then tried to flash the patched boot.img in fastboot but it failed now I'm endlessly bootlooping.
EDIT 2:
tried a couple things but couldn't get 11 to boot so I flashed back to 10 but wiped my userdata so I'm done messing around for awhile I think 11 just is a no go for now.
ReservedName said:
Pixel 4a here, just tried to follow OTA instructions and ended up bootlooped until I paused it. After resuming it rebooted but the update didn't take and magisk was uninstalled. I did have the safetynet fingerprint module installed so probably this caused an issue? Not sure it relates exactly to your problem but thought I'd chime in with a similar problem and model.
Click to expand...
Click to collapse
On Android 10, when booting Magisk in the core only mode, I would still fail the ctsProfile. I would never complete safetynet 100%. I am not sure what should be possible, but it seems some ppl can make it pass safetynet on Android 10 by running Magisk in core only mode. When upgrading to Android 11, and before flashing any boot.img, but after installing Canary build, I would still fail the ctsProfile part of the satefy net. I wonder if that somehow impacts.
If wonder if the issue is linked to the fingerprint. I also have the fingerprint module (where it allows apps to believe it's using a fingerprint, but in fact it's my face). I will try and remove all the modules, then uninstall Magisk, then reinstall Canary build. Cheers mate.
delanvital said:
I hope this is the right place to ask, pardon me if not:
Issue: After upgrading to Android 11, the patched boot image causes bootloop, when patched using Magisk Canary
Phone/setup: Pixel 4 XL, updated today to Android 11 using OTA, which strangely enough worked just fine. Previously used the usual Magisk build, but grabbed Canary for this stuff. I'm flashing using latest ADB tools via download straight from Google + using original Pixel cable which so far has worked great with fastboot. Fastboot devices -l reports the phone.
Approach:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Download latest Canary build straight from github front page, moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.
Approach two:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot_a modified-image, fastboot flash boot_b modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.
Any idea what I'm doing wrong?
Click to expand...
Click to collapse
Same here, and after the Glogo, if I restart I get ""no valid slot to boot". Flashing unpatched boot.img gets me back in, but there doesn't seem to be a way to root 11 release build?
Works fine on my Pixel 4 xl. I'm using a patched boot img. Make sure you use the correct boot img
cgo72123 said:
...if I restart I get ""no valid slot to boot". Flashing unpatched boot.img gets me back in...
Click to expand...
Click to collapse
Google Store Pixel 4a here. I have the exact same experience. Tried:
2. Uninstall Magisk -> Install OTA -> Install Inactive Slot -> bootloops 3 times and settles on previous boot slot, Android 10, no Magisk
3. Patch Boot.img -> flash-all.bat -> fastboot flash boot magisk_patched.img -> fastboot bootloop with the message "no valid slot to boot"
Can confirm re-flashing stock boot.img or running the full update script successfully boots Android 11, no root of course
Pixel 4 XL user here. I updated to Android 11 last night. Same thing happened to me. Waiting for an update to Magisk for Android 11
ChocoboX said:
Pixel 4 XL user here. I updated to Android 11 last night. Same thing happened to me. Waiting for an update to Magisk for Android 11
Click to expand...
Click to collapse
I noticed a new buildof Magisk available in the manager. New modified boot image has a slightly different filesize. Tried fastboot boot magisk_patched.img but still stuck on G and the moving line below. I wonder what is different compared to the 4xl users who has no problems...
Just want to point out that a common cause for issues when updating from one Android version to another is incompatible mods.
Make sure that no Magisk modules are installed that could be causing issues. Uninstalling the modules before updating, uninstalling Magisk, manually deleting the module directories in /data/adb/modules (or the whole modules directory) or wiping /data would all be ways of accomplishing this...
This might not be true for everyone, but it's quite likely.
Edit: Oh yeah... And don't install TWRP. Only booting it seems to be fine though.
I got it to work !!! Pixel 4 XL user. Might work on other Pixel phones / non-Pixel phones as well.
You need to download Magisk Canary apk first.
Try this post https://www.xda-developers.com/latest-magisk-canary-release-adds-support-for-android-11/
Here is the trick, you need to set the update channel in the settings to Canary Debug. Just Canary won't work and won't show any updates!
Then you will see immediately that a new version is available for manager and Magisk. Update the manager first. Then install Magisk to boot.img. Flash and there you go. I even got modules working and GPay works and even the CTS profile works! previously that failed on me (despite trying the settings recommended and Terminus commands with Busybox)
does not work
ChocoboX said:
I got it to work !!! Pixel 4 XL user. Might work on other Pixel phones / non-Pixel phones as well.
You need to download Magisk Canary apk first.
Try this post https://www.xda-developers.com/latest-magisk-canary-release-adds-support-for-android-11/
Here is the trick, you need to set the update channel in the settings to Canary Debug. Just Canary won't work and won't show any updates!
Then you will see immediately that a new version is available for manager and Magisk. Update the manager first. Then install Magisk to boot.img. Flash and there you go. I even got modules working and GPay works and even the CTS profile works! previously that failed on me (despite trying the settings recommended and Terminus commands with Busybox)
Click to expand...
Click to collapse
i have the same versions but do not see the Canary Debug.
currently it is not working
There's only been one Canary channel for some time (and it's the debug release, even though it doesn't say so in the Manager). If anyone is using a Manager that has both a "Canary" and a "Canary Debug" channel they're using an old build of the Manager. And on such a build, the regular "Canary" channel won't work since it no longer exists.
chaim said:
i have the same versions but do not see the Canary Debug.
currently it is not working
Click to expand...
Click to collapse
Ok, I found the correct link to download Magisk Canary apk
https://forum.xda-developers.com/pixel-4-xl/how-to/android-11-beta-1-jun-2020-t4113249
It's an older version but once you switch to Canary Debug it should show correct updates. For there things worked for me.
Also, I'm attaching a link to download the Magisk boot image for Android 11 directly, in case you want to skip this whole process. Just flash it with Fast Boot
https://1drv.ms/u/s!Ark6wHh1kVRCg9NyWPCCeqtpfT4XUA?e=oRse0J
Does Soli work or do you need to download that module too?
rester555 said:
Does Soli work or do you need to download that module too?
Click to expand...
Click to collapse
What is Soli? Sorry for the dumb question. I can try and see.
It's the RF based motion sensor in the front of the phone that turns on active display and swipes in front of the display to control the phone.
rester555 said:
It's the RF based motion sensor in the front of the phone that turns on active display and swipes in front of the display to control the phone.
Click to expand...
Click to collapse
I'm in the US already so it works without a problem for me. I also tried to install Enable Soli from GitHub and it installed and phone booted. Not sure how to test it further for you.
Just so that there's no confusion...
The correct (and only) place to get the Magisk installation zips and Manager apks is always going to be on John's GitHub.
Here's the (current) link to the up-to-date Canary Manager:
https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
But, if in doubt, always go to the above linked GitHub to get the latest downloads.
Downloading from anywhere else might mean that you are installing an altered (possibly maliciously) root Manager. Don't take the risk...
magisk_patched.img
what command do you use to flash it
i use:
./fastboot flash boot magisk_patched.img
and i gets stuck in bootloop
chaim said:
can anyone upload the magisk_patched.img for pixel 4xl
Click to expand...
Click to collapse
While I don't mind sharing my patched.img, just remember that TJW always recommends that users should patch their own boot.img so as to avoid any potential problems. Having said that, here you go :good:
https://drive.google.com/file/d/15fWU492AQ3eBJCgMGWe2wgc5J2b4MSPu/view?usp=drivesdk
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:
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