Database Develop

[GUIDE] OTA updates with Magisk

If you have managed to root your phone with Magisk, getting updates after that for the stock ROM isn't always a smooth thing. Here are some steps to be successful with updates.
1. Open Magisk Manager and disable all installed modules by unchecking the circle for each.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please note that steps 2-4 can be done with the stock 1+ updater so long as it senses that you are rooted and offers to download a full rom. So a note about magisk hide which is used to hide root. Make sure you haven't managed to hide root for any process related to the 1+updater or it won't know you are rooted and will offer incremental updates.
2. Install Oxygen Updater (This app may become abandoned in 2019 requiring the use of the stock updater which is slower or manually downloading roms.) https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
3. Open the app, verify that your device is identified correctly. Open it's settings and set Update Method to "Full Update"
4. Check for an update and download it. Make sure you end up with a full 2GB ROM image not an incremental small one. It will be in the root of internal storage.
DO NOT use Oxygen Updater to update the phone (unless you have TWRP and that is for a different GUIDE)
5. Open the built in OnePlus updater: Settings - System - System Updates - Gear - Local Upgrade and select the newly downloaded update. TAKE NOTE while it is installing which slot it is installing too. It will say something like "inactive slot a". Remember this as it is the "new" slot.
6. After it has installed DO NOT reboot the phone or you will lose root. Open Magisk Manager and install Magisk, even though it says "installed". Select the option when it prompts for "after OTA". This will install magisk in the boot partition of the new slot.
7. Reboot and If all went well you shouldn't boot loop and you'll be running the new slot. If you want TWRP (optional), install the zip now from Magisk->Modules->+ (sign) then select the TWRP zip file and install it. Do NOT reboot. Then do a "Direct Install" of Magisk again, then reboot.
8. Open Magisk Manager and go to the downloads section and reinstall the modules you want to use. Do this from the Downloads screen or using the + button on the Modules screen. This will install them in the current slot.
DO NOT simply reenable the modules with the check mark or you will boot loop. Some modules aren't listed in Magisk and can't be automatically moved from slot to slot. If you installed one of those previously, you must reinstall it with the plus button manually from the modules tab.
You should be done now.
Oh no I'm boot looping: Don't panic.
1. Make sure you have adb/fastboot 1.4.3 or newer on a PC https://forum.xda-developers.com/showthread.php?t=2317790
2. Boot the phone into Bootloader/fastboot either through the recovery menu or VolDn + Pwr
3. If in step 5 above the inactive slot was "a", issue the command from a PC command prompt:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
If you are not sure which to use try one or fastboot getvar current-slot
4. Then: fastboot reboot
This will allow the phone to boot into the last good ROM version. Now you figure out what went wrong.
Another option If your phone didn't retain root, you can stay in the unrooted slot. download a rooted boot image of your firmware version, place it in the your fastboot pc directory, reboot the phone to fastboot and issue the command: fastboot boot boot.img (or whatever the downloaded image is called.) this is a temporary root that is non destructive. Then do a direct install from Magisk manager even though it already says installed. That will permanently root your boot copy. Then install your modules.
Here is the 9.5.11 1917AA rooted boot image https://www.dropbox.com/s/6csxd9zaa4mihwk/boot_a_backup_2019-08-04_19-05-29.img?dl=0
If your phone looped right after flashing, you may not have disabled Magisk modules properly. You can still disable them from the good slot, swap active slots again using fastboot and see if it boots into the new ROM. If not, swap back to the good old slot again and start over flashing again from the beginning.
If you looped after reenabling your modules, it is possible you only enabled one but didn't install it into the new slot. Again swap back to the good slot and disable the modules. Swap back to the new slot and install the modules again even if Magisk thinks they are there.
If all else fails, you can stay in the good old slot until you sort things. If you are looping in both slots then something really went bad and you have to flash back a full ROM from fastboot. See this thread
https://buzzfire.de/xda/t3931424
Then root again using the rooted boot image above.
You may be able to boot into the old rooted slot and root the new slot with the ota option also.
If you have issues where stuff like Wifi doesn't work, then somewhere along the line or previously you flashed a (boot) image that didn't match the /system image in the slot you were working on. This error will persist in that slot every time you use that slot until it gets a fixed set of images.
Hope this helps!

I updated to 9.5.7 yesterday with following process, which was very simple (also used the same exact process to update to 9.5.6 last week):
Note: This assumes your device is already bootloader unlocked and has developer options enabled.
Download latest twrp.zip to your phone
Download latest magisk.zip to your phone
Download latest twrp.img to your pc
Allow oxygen updater to download/install OTA. It will say 'your device is rooted, a full image will be downloaded'. (If you're not already rooted, this process will still work)
After it completes the installation, do not select reboot. Instead, hold power button and press reboot to bootloader (make sure you enabled Advanced reboot in settings to see that option)
In fastboot and connected to pc, run from pc: fastboot flash boot twrp-3.3.1-3-guacamole.img (or whatever latest version is - you need to do this step because the OTA wipes out twrp if you already had it installed)
Reboot phone to twrp recovery
Flash install the twrp.zip you downloaded above
Flash install the magisk.zip you downloaded above
Reboot System
Done
Using this method, I haven't needed to change the slots at all, as the OOS updater takes care of that and the twrp/magisk flash installs each to both slots. This method preserves all data/settings/root (but I still do a twrp backup just prior to doing the update). I had tried the magisk install OTA to inactive slot option a few times but it never worked for me. This method also eliminates the need to download any patched boot images.

If you are on bootloop, just simply flash magisk_uninstaller.zip on twrp
boot into system > then flash magisk on twrp again.

Perfect manual and working great

gtelnet said:
I updated to 9.5.7 yesterday with following process, which was very simple (also used the same exact process to update to 9.5.6 last week):
Note: This assumes your device is already bootloader unlocked and has developer options enabled.
Download latest twrp.zip to your phone
Download latest magisk.zip to your phone
Download latest twrp.img to your pc
Allow oxygen updater to download/install OTA. It will say 'your device is rooted, a full image will be downloaded'. (If you're not already rooted, this process will still work)
After it completes the installation, do not select reboot. Instead, hold power button and press reboot to bootloader (make sure you enabled Advanced reboot in settings to see that option)
In fastboot and connected to pc, run from pc: fastboot flash boot twrp-3.3.1-3-guacamole.img (or whatever latest version is - you need to do this step because the OTA wipes out twrp if you already had it installed)
Reboot phone to twrp recovery
Flash install the twrp.zip you downloaded above
Flash install the magisk.zip you downloaded above
Reboot System
Done
Using this method, I haven't needed to change the slots at all, as the OOS updater takes care of that and the twrp/magisk flash installs each to both slots. This method preserves all data/settings/root (but I still do a twrp backup just prior to doing the update). I had tried the magisk install OTA to inactive slot option a few times but it never worked for me. This method also eliminates the need to download any patched boot images.
Click to expand...
Click to collapse
You Sir are the good damn man i have spent 3hrs trying to update to 9.5.9 cheers boss!!

Will this method work if I was a TMobile OnePlus 7pro which converted to international running 9.5.8 currently?

Yes if you are offered the aa rom in the updater

@larsdennert I guess you may well know about this:
https://forum.xda-developers.com/oneplus-7-pro/help/oxygen-updater-shutting-november-t3948339

I just start the update under settings, system, syst update
It found new update and tell me he need to download full ROM (I have rmagisk installed).
While it was downloading full ROM I uninstall magisk from magisk app.
After update finish before restart I installed magisk again (option after ota update) and restart.
Now I'm updated and with magisk installed
Inviato dal mio GM1913 utilizzando Tapatalk

SlyUK said:
@larsdennert I guess you may well know about this:
https://forum.xda-developers.com/oneplus-7-pro/help/oxygen-updater-shutting-november-t3948339
Click to expand...
Click to collapse
Yes I'm thinking, In the worst case it may be possible to use the stock updater as it senses root and downloads the full update now. Simply substitute the step where oxygen updater is used to download with the stock updater.
There may be a slightly longer delay before the stock updater offers an update as 1+ does it in waves. I have to hand it to 1+for even offering updates as most phones won't.

hi experts,
what and where to set or unset to make sure there is NO auto OTA update?
How do I control the update time on my op7p?
I'd like to avoid surprise of getting update in background that would / can remove root, magisk and etc that were manually added?
as example I use xXx over magisk and I's like to be prepared ahead of time to apply the OTA update
thanks for the education.

The 1+ updater has a setting to auto download updates or not. You can change it.

If we have TWRP installed could we get a guide for using the updater app?

kirschdog1 said:
If we have TWRP installed could we get a guide for using the updater app?
Click to expand...
Click to collapse
This is the method i use. Screenshot it from a thread here on XDA and unfortunately cannot remember the posters name to give credit. But it is the job!

kirschdog1 said:
If we have TWRP installed could we get a guide for using the updater app?
Click to expand...
Click to collapse
I used a method that didn't require uninstalling Magisk modules or even booting into recovery (unless you have issues):
1.) Download FULL OTA from 1+ updater (should be approximately 2gb)
2.) Disable all Magisk modules and substratum themes
3.) Install OTA manually via the system updater in Settings > System > System Updates > Gear in upper right > Local Upgrade **DON'T REBOOT!!!**
4.) Search for TWRP Retention Script in Magisk, install **DON'T REBOOT!!!**
5.) Re-install Magisk from the main page in Magisk Manager App (OTA Option) **REBOOT**
6.) Re-enable Magisk modules and any substratum themes **REBOOT**
If you get stuck in a bootloop due to a Magisk module causing issues (EdXposed did this to me) you can:
Boot Into Recovery (Volume Down + Power Button) > Advanced > File Manager > Navigate to data/adb/modules > Click module you want to disable / delete > Hit bottom right checkmark > Delete > Hit Home > Reboot System
Magisk modules I'm currently running in 9.5.10 with no issues:
- Google Dialer Framework
- Google Product Sans
- liboemcrypto disabler
- OnePlus Google Launcher
- Renovate Ice
- Substratum
- ViperFX
- xxxNoLimitsxxx

i.Design said:
I used a method that didn't require uninstalling Magisk modules or even booting into recovery (unless you have issues):
1.) Download FULL OTA from 1+ updater (should be approximately 2gb)
2.) Install OTA manually via the system updater in Settings > System > System Updates > Gear in upper right > Local Upgrade **DON'T REBOOT!!!**
3.) Disable all Magisk modules and substratum themes
4.) Search for TWRP Retention Script in Magisk, install **DON'T REBOOT!!!**
5.) Re-install Magisk from the main page in Magisk Manager App **REBOOT**
6.) Re-enable Magisk modules and any substratum themes **REBOOT**
If you get stuck in a bootloop due to a Magisk module causing issues (EdXposed did this to me) you can:
Boot Into Recovery (Volume Down + Power Button) > Advanced > File Manager > Navigate to data/adb/modules > Click module you want to disable / delete > Hit bottom right checkmark > Delete > Hit Home > Reboot System
Magisk modules I'm currently running in 9.5.10 with no issues:
- Google Dialer Framework
- Google Product Sans
- liboemcrypto disabler
- OnePlus Google Launcher
- Renovate Ice
- Substratum
- ViperFX
- xxxNoLimitsxxx
Click to expand...
Click to collapse
Question. How do you know it was edxposed module? I'm currently trying to track down. Why I'm still getting SOD after updating from 9.5.9 to 9.5.10

Pvt WhoOkid said:
Question. How do you know it was edxposed module? I'm currently trying to track down. Why I'm still getting SOD after updating from 9.5.9 to 9.5.10
Click to expand...
Click to collapse
I assumed it was and disabled it first, did a reboot and booted up fine. It was a good guess
Best bet would be to delete all modules and start from scratch if you're not sure. It depends what kinds of modules you run.
I had issues of bootloop where I would get past the unlocked message and boot up animation but then would freeze with my background showing only (no launcher, no status bar, etc).

i.Design said:
I assumed it was and disabled it first, did a reboot and booted up fine. It was a good guess
Best bet would be to delete all modules and start from scratch if you're not sure. It depends what kinds of modules you run.
Click to expand...
Click to collapse
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.

Pvt WhoOkid said:
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Click to expand...
Click to collapse
I was running Riru Core, edXposed and ended up dropping both, it wasn't worth the hassle for me since I run Renovate Ice and it does most of the tweaks I want from GravityBox (reason I was running Xposed).

Pvt WhoOkid said:
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Click to expand...
Click to collapse
Try disabling all the modules and see if you can boot into 9.5.10 slot. If it does, reinstall them (then reenable them)

[Guide] Keep root after OTA update on 6T - no PC required!

Hey everyone, sorry if this has been covered already but I don't recall seeing these instructions anywhere. After doing the standard tethered re-root every time there was an OTA update I discovered that you don't need to tether. I've been doing it this way for the past several updates and it has worked perfectly every time. Not sure if this will work for major version updates though. As usual, YMMV, back up your data, I'm not responsible for data loss, bricks, etc. etc.
Install TWRP and Magisk the usual tethered way the first time you root. There's no way around this.
When an OTA update comes out, allow it to download but do not let it install itself.
Download the latest TWRP Fajita zip to your device if you don't already have it. https://dl.twrp.me/fajita/
Reboot to recovery and decrypt if necessary.
Back up your data if you don't feel like living on the edge.
Hit the install button and browse to /sdcard/.Ota and select the latest zip, which was downloaded automatically earlier.
Tap the button to add another zip, and select the TWRP zip that you downloaded earlier.
Swipe to install, reboot when done. It is crucial to install both zips without rebooting in between, otherwise you'll have to tether.
After the post-boot update process completes, open the Magisk Manager app and hit the Install button for Magisk (not Magisk Manager). Choose to download zip only.
Reboot to recovery and decrypt if necessary.
Hit the install button and browse to /sdcard/Download and select the Magisk zip that you just downloaded. Swipe to install, then reboot.
Magisk app should now show Magisk is installed again.
Profit.

If we have twrp retention script we simply can retain magisk and twrp, i think everyone knows that

what is the twrp retention script? have you a link?

Open Beta 10 Available

Open Beta 10 Out.
Direct link for Full Zip: https://otafsg1.h2os.com/patch/amaz....W.27_OTA_027_all_2003061929_bad6dc784e81.zip
Changelog: Screenshot

Mine says installation failed at 79% using incremental update from oxygen updater app ?

rootSU said:
Open Beta 10 Out.
Direct link for Full Zip: https://otafsg1.h2os.com/patch/amaz....W.27_OTA_027_all_2003061929_bad6dc784e81.zip
Changelog: Screenshot
Click to expand...
Click to collapse
Downloading now, I'm rooted with twrp and decrypted so should install with no problems through twrp, will report back, thanks for sharing my friend, cheers.

vtec303 said:
Downloading now, I'm rooted with twrp and decrypted so should install with no problems through twrp, will report back, thanks for sharing my friend, cheers.
Click to expand...
Click to collapse
Sounds good. Are you currently on OB9?

AndroidRooterKev said:
Sounds good. Are you currently on OB9?
Click to expand...
Click to collapse
No, 10.0.4, cheers.

hoseth0711 said:
Mine says installation failed at 79% using incremental update from oxygen updater app ?
Click to expand...
Click to collapse
Update: I had to download and install it through built in updater function as a full update. But I'm now on beta 10

Can someone tell me how to update without loosing root? Last time I did it (with magisk retention script) I ended up in bootloop and had to reset my whole device.

Baldesarra said:
Can someone tell me how to update without loosing root? Last time I did it (with magisk retention script) I ended up in bootloop and had to reset my whole device.
Click to expand...
Click to collapse
I just follow this steps and I safely update with keeping my root and twrp. (Thanks to @HippoMan)
To be clear and complete, these are the steps that I followed (there are a couple of minor clarifications here to what I wrote in my earlier message on this subject) ...
1. Download the ROM and copy it onto the top-level directory of your sdcard. I got OB10 via the Oxygen Updater app, and it also can be found elsewhere.
2. Uninstall all Magisk modules
3. Reboot
4. Go to Settings->System->System Updates and click on the little gear on the upper right. Then, select Local upgrade, select the ROM on your sdcard, and start the installation
5. After the installation is complete, *** DO NOT REBOOT ***
6. Run Magisk Manager, go to Downloads, and then search for, download, and install the TWRP A/B Retention Script.
7, After this module installation is complete, *** DO NOT REBOOT ***
8. Immediately go to the main page of the Magisk Manager, and in the "Magisk is up to date" section, select INSTALL->INSTALL->Install to inactive slot(After OTA)
9. After this completes, reboot.
10. Your device should come back up rooted and with OB10 shown in Settings->About phone->Build number
11. If you have been using Smurf, boot into recovery and flash it again. Then, reboot back to System (I'm not sure whether reflashing Smurf is actually necessary, but it doesn't do any harm).
12. Reinstall all your formerly installed Magisk modules. You'll notice that the A/B Retention Script is not showing as "installed", and this is correct. It is just used as a one-time setup before the Install to inactive slot step, described above.
Steps 1 through 11 took less than 30 minutes, with steps 1 and 4 taking the longest. I have a number of Magisk modules, so step 12 took maybe 10 minutes more, because I rebooted after each individual Magisk module was reinstalled, in order to make sure that its installation was successful.
Sent from my GM1913 using Tapatalk

sudanking said:
I just follow this steps and I safely update with keeping my root and twrp. (Thanks to @HippoMan)
To be clear and complete, these are the steps that I followed (there are a couple of minor clarifications here to what I wrote in my earlier message on this subject) ...
1. Download the ROM and copy it onto the top-level directory of your sdcard. I got OB10 via the Oxygen Updater app, and it also can be found elsewhere.
2. Uninstall all Magisk modules
3. Reboot
4. Go to Settings->System->System Updates and click on the little gear on the upper right. Then, select Local upgrade, select the ROM on your sdcard, and start the installation
5. After the installation is complete, *** DO NOT REBOOT ***
6. Run Magisk Manager, go to Downloads, and then search for, download, and install the TWRP A/B Retention Script.
7, After this module installation is complete, *** DO NOT REBOOT ***
8. Immediately go to the main page of the Magisk Manager, and in the "Magisk is up to date" section, select INSTALL->INSTALL->Install to inactive slot(After OTA)
9. After this completes, reboot.
10. Your device should come back up rooted and with OB10 shown in Settings->About phone->Build number
11. If you have been using Smurf, boot into recovery and flash it again. Then, reboot back to System (I'm not sure whether reflashing Smurf is actually necessary, but it doesn't do any harm).
12. Reinstall all your formerly installed Magisk modules. You'll notice that the A/B Retention Script is not showing as "installed", and this is correct. It is just used as a one-time setup before the Install to inactive slot step, described above.
Steps 1 through 11 took less than 30 minutes, with steps 1 and 4 taking the longest. I have a number of Magisk modules, so step 12 took maybe 10 minutes more, because I rebooted after each individual Magisk module was reinstalled, in order to make sure that its installation was successful.
Sent from my GM1913 using Tapatalk
Click to expand...
Click to collapse
Shouldn't be that difficult.
Download the full zip from OP
Remove all the current Magisk Modules just to be safe
Boot into TWRP
Flash the OTA zip
Flash TWRP 76 zip
Reboot into Recovery
Flash Magisk Canary Zip
Boot to system
That's what I always follow, and it has never failed me.

With each update icons, fonts and whole UI seems to be larger and larger. It looks awful.

1- uninstall Magisk modules.
2- install Oos stable/open beta with Settings > Local upgrade . DON'T reboot!!!
3- back to Magisk > Downloads. Install TWRP A/B Retention Script. DON'T reboot!!!
4- back in Magisk. Touch install. Choose (Install to inactive slot after' OTA)
5- reboot to system.
Now you have latest Oos ob10, twrp 3.3.1_79 & Magisk Canary root. I updated this way from ob5...
I was on Oos 10.0.4, twrp 3.3.1_76, Magisk Canary form 12.02.2020.

using the LIV DARK substartum theme on oneplus 7 pro after the update on oxygem beta 9 and beta 10 when i apply the theme to the call dialer the theme is applied to the contacts and when i open the call dialer it does not open the failure message. .

No thanks , I will stick with Open Beta 8 all day long
until they bringing Back the One-Handed Mode

Except Feb patch I don't see anything new but... It seems snappier! Good update!
Sent from my OnePlus7Pro using XDA Labs

Thank you for sharing this with us.

You now have two functions Tap once to wake ambientscreen, tap twice to wake the lockscreen. Love it.

i6rb said:
No thanks , I will stick with Open Beta 8 all day long
until they bringing Back the One-Handed Mode
Click to expand...
Click to collapse
Are you using the dialer beta version? I had to change to normal/stock dialer and it works fine. Same theme, Liv dark
Also make sure to uninstall all layers and then reboot. Then you should try to apply the layers

When you boot or reboot your phone you too have a bug that the display won't turn on and you need to press tge power button to make the screen turn on?

preference said:
Are you using the dialer beta version? I had to change to normal/stock dialer and it works fine. Same theme, Liv dark
Also make sure to uninstall all layers and then reboot. Then you should try to apply the layers
Click to expand...
Click to collapse
can you pass me the stock dialer please

Svid said:
When you boot or reboot your phone you too have a bug that the display won't turn on and you need to press tge power button to make the screen turn on?
Click to expand...
Click to collapse
I have had this issue for a while. Don't know what is the cause and didn't see reports on it. Also, I can tap on the screen while it is still black (after reboot) and PIN would be pressed!

Question How to Install OTA update on rooted device with magisk installed.

I have rooted and installed magisk in my note 10 pro and even though I see the update in the settings and can download it. The update doesn't get installed and opens the TWRP recovery which then just fails and restarts without installing the update. Is there any way that I can install the OTA update?

XDA_chron said:
I have rooted and installed magisk in my note 10 pro and even though I see the update in the settings and can download it. The update doesn't get installed and opens the TWRP recovery which then just fails and restarts without installing the update. Is there any way that I can install the OTA update?
Click to expand...
Click to collapse
Previously, updates were downloaded to the / sdcard / downloaded_rom folder (if you look at the path from the phone) in the phone's memory, check in TWRP, if there is no firmware file there, then download the update from the website, load it into the phone's memory or a flashcard and update. After updating, without booting into the system, flash the archive using magisk and then boot into the system.

Dron74 said:
Previously, updates were downloaded to the / sdcard / downloaded_rom folder (if you look at the path from the phone) in the phone's memory, check in TWRP, if there is no firmware file there, then download the update from the website, load it into the phone's memory or a flashcard and update. After updating, without booting into the system, flash the archive using magisk and then boot into the system.
Click to expand...
Click to collapse
Instead of doing all of these things I was thinking of waiting a month or two and installing the pixel experience rom

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.