Database Develop

Magisk Installing OTA on Pixel XL 1

Hi,
I own a Pixel XL 128GB, running 8.0.0 October FW. I have installed Magisk 14.3 beta 1437. Almost everything works, except for:
1. When installing Magisk using Magisk's internal installer it always downloads MAgisk 14.0 and tries to install this old, outdated version. Is this a bug?
2. I can't install OTAs, tried following john's installing instructions...
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
My steps were:
* Install stock boot loader - Magisk almost immediately confirms that it has installed the stock boot image. That's a bit surprising, I don't see any flashing dialog like when installing Magisk. Bug?
* trying to update using the internal OTA fails. It takes very long and suddenly stops.
Any idea what went wrong?

niko26 said:
Hi,
I own a Pixel XL 128GB, running 8.0.0 October FW. I have installed Magisk 14.3 beta 1437. Almost everything works, except for:
1. When installing Magisk using Magisk's internal installer it always downloads MAgisk 14.0 and tries to install this old, outdated version. Is this a bug?
2. I can't install OTAs, tried following john's installing instructions...
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
My steps were:
* Install stock boot loader - Magisk almost immediately confirms that it has installed the stock boot image. That's a bit surprising, I don't see any flashing dialog like when installing Magisk. Bug?
* trying to update using the internal OTA fails. It takes very long and suddenly stops.
Any idea what went wrong?
Click to expand...
Click to collapse
1. If you wan't the current beta to install, you need to change to the beta update channel in the Manager settings.
2. You've probably done something that messes with important partitions (/system, /vendor, etc). It's enough to just mount the partition rw to destroy the ability to update through OTA.
Restoring the stock boot image through the Manager is instantaneous...

Hi @Didgeridoohan,
thank you very much for the quick answers!
Didgeridoohan said:
1. If you wan't the current beta to install, you need to change to the beta update channel in the Manager settings.
Click to expand...
Click to collapse
Thanks - I didn't know that.
2. You've probably done something that messes with important partitions (/system, /vendor, etc). It's enough to just mount the partition rw to destroy the ability to update through OTA.
Click to expand...
Click to collapse
Hm, how do I find out what has been messed on /system, and/or /vendor?
Does installing and using AdAway tamper with /system or /vendor?
So reflashing the stock boot image is not sufficent, correct?
And most important.. how do I fix this?

niko26 said:
Hi @Didgeridoohan,
thank you very much for the quick answers!
Thanks - I didn't know that.
Hm, how do I find out what has been messed on /system, and/or /vendor?
Does installing and using AdAway tamper with /system or /vendor?
So reflashing the stock boot image is not sufficent, correct?
And most important.. how do I fix this?
Click to expand...
Click to collapse
If you let AdAway directly write to /system/etc/hosts, then yes, you have a compromised system partition. If you're using Magisk Systemless Hosts you should be fine though. Do you have TWRP installed? That'd be an issue as well...
If you want to make sure that you can update through OTA in the future, clean flash a factory image (you can leave data intact) and then make sure not to touch /system or /vendor at all.

* DELETED *

Didgeridoohan said:
If you let AdAway directly write to /system/etc/hosts, then yes, you have a compromised system partition. If you're using Magisk Systemless Hosts you should be fine though.
Click to expand...
Click to collapse
Yeah, I've been using Magisk's systemless hosts-file.
. Do you have TWRP installed? That'd be an issue as well...
Click to expand...
Click to collapse
TWRP has not been installed permanently.
If you want to make sure that you can update through OTA in the future, clean flash a factory image (you can leave data intact) and then make sure not to touch /system or /vendor at all.
Click to expand...
Click to collapse
There aren't a lot of apps I am granting root. One of them is Titanium Backup. It may have tampered the fs.
Is there any kind of diff against the original folders which I can run to find out what has been tampered to possibly identify which app is causing the issues?
One of the main reasons for installing Magisk was because I was tired of flashing the entire system when updates have been released.
I never couldn't get Flashfire working properly when it comes to install updates / OTAs.

niko26 said:
Yeah, I've been using Magisk's systemless hosts-file.
TWRP has not been installed permanently.
There aren't a lot of apps I am granting root. One of them is Titanium Backup. It may have tampered the fs.
Is there any kind of diff against the original folders which I can run to find out what has been tampered to possibly identify which app is causing the issues?
One of the main reasons for installing Magisk was because I was tired of flashing the entire system when updates have been released.
I never couldn't get Flashfire working properly when it comes to install updates / OTAs.
Click to expand...
Click to collapse
Since the OTA can check for a tampered system, I'm sure there's a way to check. Question is if it's worth the effort.
Any app that has root access can be the culprit... Could also be that you let TWRP mount system rw or something similar. Really hard to say...

Didgeridoohan said:
Since the OTA can check for a tampered system, I'm sure there's a way to check. Question is if it's worth the effort.
Any app that has root access can be the culprit... Could also be that you let TWRP mount system rw or something similar. Really hard to say...
Click to expand...
Click to collapse
Does TWRP mount system as rw by default? Because all I really do is.. boot to TWRP, flash the Magisk's zip. That's it. Nothing else.
Is there any other way I can install OTAs without using a computer with USB (and keeping root of course )?
As said... I never could FlashFire to work correctly. The documentation leaves a lot of questions open - BTW.. props to the Magisk's docs - much better.

niko26 said:
Does TWRP mount system as rw by default? Because all I really do is.. boot to TWRP, flash the Magisk's zip. That's it. Nothing else.
Is there any other way I can install OTAs without using a computer with USB (and keeping root of course )?
As said... I never could FlashFire to work correctly. The documentation leaves a lot of questions open - BTW.. props to the Magisk's docs - much better.
Click to expand...
Click to collapse
TWRP doesn't mount system as rw unless you let it.
I've never used Flashfire and haven't updated through OTA since, 2014-ish. :laugh: I'm mainly going on theoretical knowledge here... On my Nexus I used fastboot to flash the factory image (until I switched to ROM flashing in TWRP) and now I just flash the full update package that OnePlus provides in TWRP.
For a while there I also flashed the system.img and boot.img files in TWRP. If that months security update only had anything to do with those files it was just a matter of downloading the factory image and unpack those two files and flash them directly in TWRP. No computer needed (unless there was an update to the bootloader and/or radio). No idea if this is viable on a Pixel...
My main use for Magisk is that all my system modifications are still there after I update my phone. Drastically cuts down on the time it takes to set my phone up after an update.

Didgeridoohan said:
I've never used Flashfire and haven't updated through OTA since, 2014-ish. :laugh: I'm mainly going on theoretical knowledge here... On my Nexus I used fastboot to flash the factory image (until I switched to ROM flashing in TWRP) and now I just flash the full update package that OnePlus provides in TWRP.
Click to expand...
Click to collapse
I've tried installing TWRP permanently, but the moment I have installed an official patch, it got wiped - and I haven't found any docs how to prevent that.
My main use for Magisk is that all my system modifications are still there after I update my phone. Drastically cuts down on the time it takes to set my phone up after an update.
Click to expand...
Click to collapse
What settings are you referring to?

niko26 said:
I've tried installing TWRP permanently, but the moment I have installed an official patch, it got wiped - and I haven't found any docs how to prevent that.
Click to expand...
Click to collapse
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
What settings are you referring to?
Click to expand...
Click to collapse
I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.

Didgeridoohan said:
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
Click to expand...
Click to collapse
Well, TWRP is gone after an update - I can't boot into it.
[/quote]I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.[/QUOTE]
Hm, I am not sure if I get you right. If it is about apps, I use Titanium Backup to recover my old apps+settings.

system files
Most of the setting you mentioned are messing with the system files. "debloating" or removing and system applications with titanium backup will fail a system check with OTA update. You can freeze the apps i believe.
I changing the screen density and boot scripts. These are all system files locations.
I have had an ota work be re-installing the system apps from titanium backup and reverting all the other changes when it was failing before. Think this was back on android 6.0 though.
Didgeridoohan said:
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.
Click to expand...
Click to collapse

automattic said:
Most of the setting you mentioned are messing with the system files. "debloating" or removing and system applications with titanium backup will fail a system check with OTA update. You can freeze the apps i believe.
I changing the screen density and boot scripts. These are all system files locations.
I have had an ota work be re-installing the system apps from titanium backup and reverting all the other changes when it was failing before. Think this was back on android 6.0 though.
Click to expand...
Click to collapse
Since all of the things I mentioned are done with Magisk, none of them will cause an OTA to fail...
Reinstalling system apps will not work, since nowadays an OTA will fail just by mounting /system as rw.

Hi guys, trying to install latest OTA patch for Pixel 2. I am assuming process would be the same. I tried to follow the guide but hit the bump immediately. I can't see "Restore Stock Boot" when pressing uninstall. But there is restore images option. Hitting it does nothing, I receive the message that there are no backups. Where does the backup go so I can put the original file for it to be reinstalled?

i rooted my phone but it shows not rooted properly in the root checker

here are the steps i followed:
unlocked oem
installed twrp using my pc
then i flashed lineage os 16
i didnt install gapps because it failed for some reason. did i leave a step?

RahulDesai1999 said:
here are the steps i followed:
unlocked oem
installed twrp using my pc
then i flashed lineage os 16
i didnt install gapps because it failed for some reason. did i leave a step?
Click to expand...
Click to collapse
You have to flash Magisk zip via TWRP to root any ROM.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/amp/
Download latest stable from downloads section and reboot your phone into twrp and flash that zip. After rebooting into system again you'll have your ROM rooted.

I flashed the latest version but it still shows not rooted properly

RahulDesai1999 said:
I flashed the latest version but it still shows not rooted properly
Click to expand...
Click to collapse
Make sure you've got the latest version of TWRP, and if you don't, install the latest version.
Download the latest version of Magisk again, and put it on a Micro-USB USB stick.
Download the Magisk Remover zip and place it on the USB stick as well Magisk Remover
Boot into TWRP, and then flash the Magisk Remover zip.
Once that's done, flash the Magisk zip from the USB stick (don't remove it; the reason why I want you to flash from the USB stick, is that I've found it doesn't give any errors, rather than flashing from internal storage).
Reboot to system and install the latest version of the Magisk Manager app from XDA Labs Store.
If you use adoptable storage, then go to Apps & Notifications in System Settings, find Magisk Manager and see under Storage if it's installed on INTERNAL storage (if it isn't, move it there). Also while you're there, check that MM has got permission to access storage.
Launch MM and accept whatever it asks you to so it can complete the setup.
Then get & install this Root Checker app (I like it because it's free, the free version has got very little ads, and it just does the job for both root and safety net status checking).

Question Magisk OTA Update reboot directly

Hey Guys,
I don't found any similar thread about this topic, so I will create a new.
I have magisk installed and used OxygenOS 12.1 A.10. Today I got the first update to A.12. I did it the same way as I did on Android 11. Recover Image -> Download OTA -> Install OTA -> Install to inactive Slot in magisk.
But on Android 12 it downloads the OTA, then it extract and verify it. After Clicking on Install it will reboot directly. Does someone know how I do the OTA Updates on Android 12 correct?
Many thanks!

Android 12 it downloads the OTA, then it extract and verify it. When the Install Now button appears,switch to magisk and Install to inactive Slot in magisk.Don't restart phone in magisk,Switch to the system update interface and clicking on Install it will reboot directly.
Note the sequence of operations above,if you restart in magisk, the system will not be able to switch to the newly installed inactive Slot.

sunhao said:
Android 12 it downloads the OTA, then it extract and verify it. When the Install Now button appears,switch to magisk and Install to inactive Slot in magisk.Don't restart phone in magisk,Switch to the system update interface and clicking on Install it will reboot directly.
Note the sequence of operations above,if you restart in magisk, the system will not be able to switch to the newly installed inactive Slot.
Click to expand...
Click to collapse
The issue for the author is that the incremental OTA is being downloaded and installed instead of the full-OTA, which makes it impossible to Patch Magisk into inactive slot.
The correct way is to NOT uninstall Magisk in the first place (Do not Recover Image in Magisk) -> Try to update the incremental OTA (it'll fail three times), then the updater will offer you the full-OTA (4.xxGB) which you can install and then switch to Magisk and install into inactive slot.

CoinsClassic said:
The issue for the author is that the incremental OTA is being downloaded and installed instead of the full-OTA, which makes it impossible to Patch Magisk into inactive slot.
The correct way is to NOT uninstall Magisk in the first place (Do not Recover Image in Magisk) -> Try to update the incremental OTA (it'll fail three times), then the updater will offer you the full-OTA (4.xxGB) which you can install and then switch to Magisk and install into inactive slot.
Click to expand...
Click to collapse
This behavior is kind of weird from the OnePlus but I probably understand it. Anyway it will be better to offer full OTA straight forward. System can decide whether it's needed or not I think?
Anyway i reinstalled Magisk via fastboot when this happened.
Once twrp is available, there won't be those issues I assume.

CoinsClassic said:
The issue for the author is that the incremental OTA is being downloaded and installed instead of the full-OTA, which makes it impossible to Patch Magisk into inactive slot.
The correct way is to NOT uninstall Magisk in the first place (Do not Recover Image in Magisk) -> Try to update the incremental OTA (it'll fail three times), then the updater will offer you the full-OTA (4.xxGB) which you can install and then switch to Magisk and install into inactive slot.
Click to expand...
Click to collapse
sunhao said:
Android 12 it downloads the OTA, then it extract and verify it. When the Install Now button appears,switch to magisk and Install to inactive Slot in magisk.Don't restart phone in magisk,Switch to the system update interface and clicking on Install it will reboot directly.
Note the sequence of operations above,if you restart in magisk, the system will not be able to switch to the newly installed inactive Slot.
Click to expand...
Click to collapse
Thank you very much! I will try this for the next update

CoinsClassic said:
The issue for the author is that the incremental OTA is being downloaded and installed instead of the full-OTA, which makes it impossible to Patch Magisk into inactive slot.
The correct way is to NOT uninstall Magisk in the first place (Do not Recover Image in Magisk) -> Try to update the incremental OTA (it'll fail three times), then the updater will offer you the full-OTA (4.xxGB) which you can install and then switch to Magisk and install into inactive slot.
Click to expand...
Click to collapse
If oneplus offering the full update after this 3 times, will it reboot automatically after installation or is it there the same as in android 11 that I can reboot it over magisk?

paper88 said:
If oneplus offering the full update after this 3 times, will it reboot automatically after installation or is it there the same as in android 11 that I can reboot it over magisk?
Click to expand...
Click to collapse
Yes, you can. When the button to install now appears in the automatic update of the system, switch to magisk and install it to inactive Slot, then return to the system update, click the button to install now, and the phone will restart automatically. Remember not to click restart on the magisk interface

CoinsClassic said:
The issue for the author is that the incremental OTA is being downloaded and installed instead of the full-OTA, which makes it impossible to Patch Magisk into inactive slot.
The correct way is to NOT uninstall Magisk in the first place (Do not Recover Image in Magisk) -> Try to update the incremental OTA (it'll fail three times), then the updater will offer you the full-OTA (4.xxGB) which you can install and then switch to Magisk and install into inactive slot.
Click to expand...
Click to collapse
Do you know if this is also a possible way for the C.20 Update of Android 13? Would be helpful if someone tested this already

trying to update android version from 10 to 11. please help!

hello.
I'm look for a way to upgrade android version from 10 to 11.
build number: QKQ1.200419.002.WW_PHONE-17.0822.2005.11
-I can't use auto update
-I can't use manual update (transferring Raw file to internal storage and then install it from the os), it keeps giving my a fail error
thank you

blabla15rul said:
hello.
I'm look for a way to upgrade android version from 10 to 11.
build number: QKQ1.200419.002.WW_PHONE-17.0822.2005.11
-I can't use auto update
-I can't use manual update (transferring Raw file to internal storage and then install it from the os), it keeps giving my a fail error
thank you
Click to expand...
Click to collapse
You can't install RAW files from internal storage, you have to flash it from Fastboot. Auto updating should work if you update incrementally up to whatever version you're looking to end at, unless there is an issue that's not detailed in your post.

blabla15rul said:
hello.
I'm look for a way to upgrade android version from 10 to 11.
build number: QKQ1.200419.002.WW_PHONE-17.0822.2005.11
-I can't use auto update
-I can't use manual update (transferring Raw file to internal storage and then install it from the os), it keeps giving my a fail error
thank you
Click to expand...
Click to collapse
First update to WW-17.0823.2104.147 by putting the fw zip downloaded from asus site.
Then update to the A11 fw WW-18.0410.2106.138 by putting the fw zip downloaded from asus site.
Else you can use twrp latest build.
1. Just download the last A11 stable fw that is WW-18.0410.2203.201 from asus website.
2. Put the zip in Internal storage.
3. Boot to twrp recovery.
4. Click on Install > Select the zip file > Swipe to flash. (You will see in which slot the zip is flashing)
5. After flash done, (just don''t reboot). Go to Reboot Section of twrp> Change Slot to the other one via clicking on Slot name.
6. Now do same as 4.
7 After flash done. Just Reboot to system

Hello
I also recommend https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/
Regards

Automatic updates
Sagar Sharma01 said:
First update to WW-17.0823.2104.147 by putting the fw zip downloaded from asus site.
Then update to the A11 fw WW-18.0410.2106.138 by putting the fw zip downloaded from asus site.
Else you can use twrp latest build.
1. Just download the last A11 stable fw that is WW-18.0410.2203.201 from asus website.
2. Put the zip in Internal storage.
3. Boot to twrp recovery.
4. Click on Install > Select the zip file > Swipe to flash. (You will see in which slot the zip is flashing)
5. After flash done, (just don''t reboot). Go to Reboot Section of twrp> Change Slot to the other one via clicking on Slot name.
6. Now do same as 4.
7 After flash done. Just Reboot to system
Click to expand...
Click to collapse
Apologies for the delayed answer
Well, the first method you suggested worked perfectly
Thank you so much!!!

iS Anyone Have A12 Flash Raw File?

lvl0rde said:
iS Anyone Have A12 Flash Raw File?
Click to expand...
Click to collapse
I already told you i have A12 raw.
But you need to message me in my telegram id.
As i don't have enough internet to upload in a cloud storage and give you the link.

Sagar Sharma01 said:
I already told you i have A12 raw.
But you need to message me in my telegram id.
As i don't have enough internet to upload in a cloud storage and give you the link.
Click to expand...
Click to collapse
What Was Ur Telegram account?

Update lineageos OTA update and keep root access.

Hi
I installed LineageOS 20 on OnePlus 9 with the instructions on official wiki. Then I root my phone with Magisk. I install Magisk by sideloading the Magisk ZIP file and then install the apk as it's been explained in this video. Now I can't update the OS with updater in system settings. I find this guide that explained I need to uninstall and restore images in magisk then update my phone and reinsatall magisk before reboot. But magisk didn't create a backup during installation.
I followed this instructions to fix magisk stock backup does not exist
I create a backup with this guide and lineageos boot.img file and I can now restore images in magisk but I get the same error when trying to install the updates. I noticed that there is also dtbo in backup function and I did the same thing for backing up dtbo.img and it doesn't solve the problem. Is there anything I'm missimg. Should I use vendor-boot.img instead of boot.img?

mtuxz said:
Hi
I installed LineageOS 20 on OnePlus 9 with the instructions on official wiki. Then I root my phone with Magisk. I install Magisk by sideloading the Magisk ZIP file and then install the apk as it's been explained in this video. Now I can't update the OS with updater in system settings. I find this guide that explained I need to uninstall and restore images in magisk then update my phone and reinsatall magisk before reboot. But magisk didn't create a backup during installation.
I followed this instructions to fix magisk stock backup does not exist
I create a backup with this guide and lineageos boot.img file and I can now restore images in magisk but I get the same error when trying to install the updates. I noticed that there is also dtbo in backup function and I did the same thing for backing up dtbo.img and it doesn't solve the problem. Is there anything I'm missimg. Should I use vendor-boot.img instead of boot.img?
Click to expand...
Click to collapse
I just learned that Magisk doesn't work after an OTA update. What I do is I normally update, uninstall Magisk, boot into Lineage Recovery, sideload the Magisk .zip file via ADB, reboot, and finish setting up Magisk through the app. There are other ways to do this, but this method works well and doesn't need anything special. Works for me!
Alteratively, look here.

mtuxz said:
Hi
I installed LineageOS 20 on OnePlus 9 with the instructions on official wiki. Then I root my phone with Magisk. I install Magisk by sideloading the Magisk ZIP file and then install the apk as it's been explained in this video. Now I can't update the OS with updater in system settings. I find this guide that explained I need to uninstall and restore images in magisk then update my phone and reinsatall magisk before reboot. But magisk didn't create a backup during installation.
I followed this instructions to fix magisk stock backup does not exist
I create a backup with this guide and lineageos boot.img file and I can now restore images in magisk but I get the same error when trying to install the updates. I noticed that there is also dtbo in backup function and I did the same thing for backing up dtbo.img and it doesn't solve the problem. Is there anything I'm missimg. Should I use vendor-boot.img instead of boot.img?
Click to expand...
Click to collapse
ethical_haquer said:
I just learned that Magisk doesn't work after an OTA update. What I do is I normally update, uninstall Magisk, boot into Lineage Recovery, sideload the Magisk .zip file via ADB, reboot, and finish setting up Magisk through the app. There are other ways to do this, but this method works well and doesn't need anything special. Works for me!
Alteratively, look here.
Click to expand...
Click to collapse
I was exactly looking for this for my SM-T290, which also runs LineageOS 20. I think it is the most easy to deinstall Magisk root from the Magisk Manager, apply the update and then reinstall it. I think this also works with TWRP???

Minionguyjpro said:
I was exactly looking for this for my SM-T290, which also runs LineageOS 20. I think it is the most easy to deinstall Magisk root from the Magisk Manager, apply the update and then reinstall it. I think this also works with TWRP???
Click to expand...
Click to collapse
I'm installing an update right now. I would imagine it works with TWRP as well, but I only recently started using it.

I realize that this may be a late reply, however, there is no need to do any of these convoluted processes.
Here is what I do, flash the Magisk as a .zip in Lineage recovery once and set everything up. Once the Magisk install is working you can apply OTA updates normally without Magisk and root being removed. On my OnePlus 7 Pro which is an A/B device I just install the OTA and hit reboot with Magisk seamlessly persisting and nothing else being required to preserve or reinstall it. The reason that this works is because the Magisk.zip installs an addons.d script which automatically runs after OTA updates and takes care of Magisk for you.
I installed many Lineage OS 20 OTAs and I never had to touch Magisk at all, it is always installed and working with no intervention whatsoever. Keep in mind that this will only work on A/B devices with Lineage recovery (which you should all be using anyway).

droidman1992 said:
I realize that this may be a late reply, however, there is no need to do any of these convoluted processes.
Here is what I do, flash the Magisk as a .zip in Lineage recovery once and set everything up. Once the Magisk install is working you can apply OTA updates normally without Magisk and root being removed. On my OnePlus 7 Pro which is an A/B device I just install the OTA and hit reboot with Magisk seamlessly persisting and nothing else being required to preserve or reinstall it. The reason that this works is because the Magisk.zip installs an addons.d script which automatically runs after OTA updates and takes care of Magisk for you.
I installed many Lineage OS 20 OTAs and I never had to touch Magisk at all, it is always installed and working with no intervention whatsoever. Keep in mind that this will only work on A/B devices with Lineage recovery (which you should all be using anyway).
Click to expand...
Click to collapse
Well, I came to the fact I have a problem with TWRP. It uses OpenRecoveryScript for OTA updates and should also run addon.d scripts after it (Magisk uses this to survive an OTA). The only problem is that the scripts should run after the OTA flash, but for me, it doesn't. So I need to manually reflash Magisk and Gapps after installing an update. My data is encrypted, but I edited the addon.d script to flash the ZIP from the external SD card.