Database Info

how to ota with root

I am rooted with custom kernel and recovery. What's the best way to take the ota?

What ota??

Before you create a thread here, please be more specifice. And use the SEARCH button.
I think you are trying to upgrade from 5.1.8 to 5.1.9.
There is a official thread here on xda. And everything is there explained, about how to update to the new version.
The way I did:
1. Flash full 5.1.9.zip
2. Flash twrp.zip
3. Reboot to recovery.
4. Flash Magisk.
5. Clear dalvik cache.

There is a dedicated thread for questions like this.
https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232

I just took the ota, then flashed WRP followed by Magisk

Ghost123NL said:
Before you create a thread here, please be more specifice. And use the SEARCH button.
I think you are trying to upgrade from 5.1.8 to 5.1.9.
There is a official thread here on xda. And everything is there explained, about how to update to the new version.
The way I did:
1. Flash full 5.1.9.zip
2. Flash twrp.zip
3. Reboot to recovery.
4. Flash Magisk.
5. Clear dalvik cache.
Click to expand...
Click to collapse
Hi, I'm planning to root my op6. Im not sure how the A\B partition thingy works so just trying to clear some doubts. After you flash the full zip in twrp in 2nd step by "flashing twrp" you mean flashing the twrp installer or you lose twrp and flash it using fastboot?

mohdfahad47 said:
Hi, I'm planning to root my op6. Im not sure how the A\B partition thingy works so just trying to clear some doubts. After you flash the full zip in twrp in 2nd step by "flashing twrp" you mean flashing the twrp installer or you lose twrp and flash it using fastboot?
Click to expand...
Click to collapse
just flash the installer right after rom and you are good to go

If u don't need TWRP and happy with magisk, u can install ota with official updater and after that (before reboot) go into magisk and do --> install--> install to inactive slot (after ota). That's all.
After reboot you have updated system with magisk installed. I do this all the time.

OTA after root

Simple question. Will I be able to do OTA updates if I root and install twrp? If yes, will I need to root and install twrp again after each update?

vaggosgr said:
Simple question. Will I be able to do OTA updates if I root and install twrp? If yes, will I need to root and install twrp again after each update?
Click to expand...
Click to collapse
Yes, you are able to use ota. (full roms must be flashed, os knows if you have root so it will download it.
Yes, updates will replace boot img with stock so you need to get twrp and root again. You have two options:
1. Download full rom zip (Funk has links for both stable and betas here on xda in the guides section)
2. Boot to recovery, flash full rom. (DO NOT REBOOT)
3. Flash twrp (use Blu spark latest, it always works)
4. Reboot to twrp, flash magisk.
Option two:
1. Install OTA from system, when it tells you install is complete, reboot to finish DON'T DO IT
2. Open magisk app, go to downloads and search for a/b twrp and install it ( there is only one module) after install is done DON'T REBOOT.
3. Go to main screen of magisk, press install, install, install to inactive slot (after ota) and after that install is complete, it's done.
Things to think about when updating: some Magisk modules may not be up to date when you update, this can cause bootloop. Some modules can cause system UI to force close. If you get this, use magisk uninstaller and see if you can reboot, if it works, then atleast you know it's modules.
There is also a possibility that substratum and swift installer can cause system UI force close aswell. Before install uninstall so you can install again after all is done.

whizeguy said:
Yes, you are able to use ota. (full roms must be flashed, os knows if you have root so it will download it.
Yes, updates will replace boot img with stock so you need to get twrp and root again. You have two options:
1. Download full rom zip (Funk has links for both stable and betas here on xda in the guides section)
2. Boot to recovery, flash full rom. (DO NOT REBOOT)
3. Flash twrp (use Blu spark latest, it always works)
4. Reboot to twrp, flash magisk.
Option two:
1. Install OTA from system, when it tells you install is complete, reboot to finish DON'T DO IT
2. Open magisk app, go to downloads and search for a/b twrp and install it ( there is only one module) after install is done DON'T REBOOT.
3. Go to main screen of magisk, press install, install, install to inactive slot (after ota) and after that install is complete, it's done.
Things to think about when updating: some Magisk modules may not be up to date when you update, this can cause bootloop. Some modules can cause system UI to force close. If you get this, use magisk uninstaller and see if you can reboot, if it works, then atleast you know it's modules.
There is also a possibility that substratum and swift installer can cause system UI force close aswell. Before install uninstall so you can install again after all is done.
Click to expand...
Click to collapse
Good write up.

vaggosgr said:
Simple question. Will I be able to do OTA updates if I root and install twrp? If yes, will I need to root and install twrp again after each update?
Click to expand...
Click to collapse
Simple reply.
No, you need full roms to flash manually.
And yes, you need to reflash TWRP after each update.
Ok filarako?
Sent from my ONEPLUS A6003 using Tapatalk

*system error* said:
Good write up.
Click to expand...
Click to collapse
Works like a charm :good:
used option 2
Thank you very much Whizeguy !

On a CONVERTED T-Mobile OP7 and currently on Android 10 with Magisk but no TWRP

Was thinking about downgrading to 9.5.13 and re-flashing TWRP and upgrading through the common "flash to inactive slot" from magisk method. On the fence cause i figure TWRP for Android 10 will come out. To recap. I have a Converted Tmobile OP7 running android 10. I am rooted with magisk but stock recovery (No TWRP) just wanting to see what you guys think i should do. and if you comment for me to downgrade... would i just go through MSM tool and revert back to 9.5.13? and would it REVERT my OP7 back to TMOBILE? Thanks in advance

TimmyLe7 said:
Was thinking about downgrading to 9.5.13 and re-flashing TWRP and upgrading through the common "flash to inactive slot" from magisk method. On the fence cause i figure TWRP for Android 10 will come out. To recap. I have a Converted Tmobile OP7 running android 10. I am rooted with magisk but stock recovery (No TWRP) just wanting to see what you guys think i should do. and if you comment for me to downgrade... would i just go through MSM tool and revert back to 9.5.13? and would it REVERT my OP7 back to TMOBILE? Thanks in advance
Click to expand...
Click to collapse
There is TWRP for OxygenOS 10.
Check the thread. It's a -70 release.
If you already have root you can flash TWRP then do a direct flash of Magisk.
I keep both my slots at the same OS revision and rooted the same way, so if something gets messed up I can boot to thew other slot and not even notice.

tech_head said:
There is TWRP for OxygenOS 10.
Check the thread. It's a -70 release.
If you already have root you can flash TWRP then do a direct flash of Magisk.
I keep both my slots at the same OS revision and rooted the same way, so if something gets messed up I can boot to thew other slot and not even notice.
Click to expand...
Click to collapse
Oh I saw that and wasn't sure on it! Thanks man. And is there a tutorial to flash on both slots? And how do I check to know what firmware is on each slot?

TimmyLe7 said:
Oh I saw that and wasn't sure on it! Thanks man. And is there a tutorial to flash on both slots? And how do I check to know what firmware is on each slot?
Click to expand...
Click to collapse
I don't know of a tutorial.
The process I use is the following:
1. Download latest or firmware later than what you have installed. Youcannot use this method to roll back.
2. Local install. Don't reboot yet.
3. Install Magisk using the option to root after OTA upgrade in Magisk Manager.
4. Reboot.
5. You will now have the OS installed in the current booting slot.
6. Local install again. Yes, it fails. Local install again, it will work the second time. -> Don't reboot
7. Use Magisk Manager to flash TWRP. Do not reboot.
8. Using Magisk Manager, install Magisk into the current slot. When that is done, se the install after OTA option.
9. You can now reboot.
You can use TWP to switch slots if you like, but both slots now have same OS and are rooted.

tech_head said:
There is TWRP for OxygenOS 10.
Check the thread. It's a -70 release.
If you already have root you can flash TWRP then do a direct flash of Magisk.
I keep both my slots at the same OS revision and rooted the same way, so if something gets messed up I can boot to thew other slot and not even notice.
Click to expand...
Click to collapse
tech_head said:
I don't know of a tutorial.
The process I use is the following:
1. Download latest or firmware later than what you have installed. Youcannot use this method to roll back.
2. Local install. Don't reboot yet.
3. Install Magisk using the option to root after OTA upgrade in Magisk Manager.
4. Reboot.
5. You will now have the OS installed in the current booting slot.
6. Local install again. Yes, it fails. Local install again, it will work the second time. -> Don't reboot
7. Use Magisk Manager to flash TWRP. Do not reboot.
8. Using Magisk Manager, install Magisk into the current slot. When that is done, se the install after OTA option.
9. You can now reboot.
You can use TWP to switch slots if you like, but both slots now have same OS and are rooted.
Click to expand...
Click to collapse
Thanks for the help man! I just flashed TWRP -70 and I got everything up and running. Gonna do the second "boot" when I got some time. And to recap.. you just have two boots setup as a precaution right? I'm not doing too much with my rom except for viper and that's it!

[SOLVED] OTA with ROOT...

I ask before in "guide to root motorla g stylus":
really is no way to work OTA while Magisk installed? i mean some Magisk Hide Props Config, or not install TWRP or anything? i actualy have Nokia 7 Plus (unlocked via unoficial method) and last year while not installed TWRP is possible check system update, install over air (while Magisk is installed), before reboot run MagiskManager, install Magisk to other slot, reboot, started from updated slot with Magisk installed, without need flash stock boot img before ota and flash manualy patched boot img after OTA... sure have Moto G Pro additional check or limitation and this not work? thanks...
Click to expand...
Click to collapse
without reaction, then try make separated thread, i actualy have one week "Motorola Moto G Pro" (XT2043-7), rooted, and wait for OTA, UpdateCheck in Settings not show me, try LMSA Rescue/Download and show me same version as have installed QPRS30.80-109-2-7...
Questions:
- Have any user of same phone, without root, already showed Octorber OTA?
- Is on rooted posible UpdateCheck with show if OTA avaiable?
- Have any working solution for OTA update on rooted phone without need connected with PC? Similar or same as i write about Nokia7Plus?
(i mean without flash back stock img, make ota, patch new boot.img file in MagiskManager, flash it via TWRP booted...
i think without PC be sure posible flash back stock boot.img to boot partition, before OTA, maybe download zip of full "rom" and extract boot.img, patch via MagiskManager, but not flash patched
EDIT: Sollution here

The answers to your first two questions are yes. When on stock I successfully updated. And while rooted there was a notification for ota update, it would download, but fall to install. I came across a way to do it without having to connect to pc. Some said it was successful but I was not able to try. It has something to do with placing your original boot.img into a a folder on one of the root directories but I had no idea how in the hell they came up with the system path to the file (encrypted??) Because I didn't have any of the folders on my phone and was to lazy at the time to ask for help. It was also an older thread so I didn't feel like bringing up a thread that old.

without root you updated system to higher (with Ocrober security patches) version than QPRS30.80-109-2-7 (this version have September security patches) ?
second part of you answer i think not understand, with rooted phone, put boot.img in "a" directory in one (which?where?) root folder and OTA services flash it before upgrade/reboot???

please, anyone with "Motorola Moto G Pro" (XT2043-7), channel "reteu", have already displayed update notification for "QPRS30.80-109-2-8" ?

Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...

Very nice writeup. With respect to step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image? With respect to step 5, how do I get to that point? Is it a prompt after rebooting?

flroots said:
[...] step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image?
Click to expand...
Click to collapse
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
flroots said:
[...] step 5, how do I get to that point? Is it a prompt after rebooting?
Click to expand...
Click to collapse
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7

k3dar7 said:
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
Click to expand...
Click to collapse
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
k3dar7 said:
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
Click to expand...
Click to collapse
Thanks

flroots said:
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
Click to expand...
Click to collapse
Understand, but as i write, you must have installed Magisk via TWRP, with this method, Magisk make backup of boot image to "/data/magisk_backup_SomeRandomStrings/boot.img.gz", this file is used when you doing step 3, but if you only patch stock boot file, then ofcourse this backup is not created... i sugest you:
- revert boot to stock via same way as you flash patched before, but using stock boot.img
- boot TWRP (NOT flash, use command is section "Boot") and install Magisk.zip oficial release
- if on your phone/touchscreen variant not work touchscreen in TWRP, then (while still is booted TWRP) install it using adb

Thanks.

I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?

flroots said:
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
Click to expand...
Click to collapse
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
2. not sure, i not use LMSA

k3dar7 said:
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
Click to expand...
Click to collapse
Thanks, that sounds great. Would you mind elaborating the steps involved? I have TWRP and Magisk installed now.

k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Do these steps cause loss of data? Thanks

flroots said:
Do these steps cause loss of data? Thanks
Click to expand...
Click to collapse
i ofcourse not garant ;-) but for me nothing lost, also installed magisk modules is preserved...

k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?

flroots said:
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
Click to expand...
Click to collapse
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)

k3dar7 said:
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
Click to expand...
Click to collapse
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?

flroots said:
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
Click to expand...
Click to collapse
maybe magisk backup boot.img have already twrp inside if you install twrp before magisk?
anyway, if you flash stock boot.img, then step 6&7 is not applicable, because this need booted rooted system

btw: method above work for me also while i upgrade from Android10 to Android11 ;-)

Question OOS13 - How to update rooted phone? LE2115 F.18 - No full ROM?

I'm new to OnePlus again, had a Pixel as my last phone. Got the notice there's a new update for OOS13. I am rooted and, if possible, want to stay on stock ROM.
I checked the process and it seems the two ways to update are applying the full image or temporarily deinstalling Magisk, running the OTA, then reinstalling Magisk to other slot. Well, OxygenOS Updater and the OnePlus website show no full image for this latest update, so I tried the second method and that did not work at all, it went straight to the Qualcomm bugcheck screen on boot and then basically wouldn't start until I went back to fastboot and got back to Slot A.
So, am I missing something or is there just a lag before the full ROM gets posted? Or will OnePlus just never post it and I need to go to a third party ROM?

thx1200 said:
I'm new to OnePlus again, had a Pixel as my last phone. Got the notice there's a new update for OOS13. I am rooted and, if possible, want to stay on stock ROM.
I checked the process and it seems the two ways to update are applying the full image or temporarily deinstalling Magisk, running the OTA, then reinstalling Magisk to other slot. Well, OxygenOS Updater and the OnePlus website show no full image for this latest update, so I tried the second method and that did not work at all, it went straight to the Qualcomm bugcheck screen on boot and then basically wouldn't start until I went back to fastboot and got back to Slot A.
So, am I missing something or is there just a lag before the full ROM gets posted? Or will OnePlus just never post it and I need to go to a third party ROM?
Click to expand...
Click to collapse
Uninstall magisk restore images only. Don't reboot ,start ota let it install. Don't reboot. Go into magisk install and apply to ota . Boots into other slot. Qualcomm crash dump is probably because you left modules enabled. Disable and reboot before you start all of this. All your doing is supplying an apparent stock boot.img to allow ota to install. I just did process going to F-18 and all is well. Actually I msm back to A10 patch boot there. And carry it all the way to latest update. !! Pm me if you have any questions and gl.

mattie_49 said:
Uninstall magisk restore images only. Don't reboot ,start ota let it install. Don't reboot. Go into magisk install and apply to ota . Boots into other slot. Qualcomm crash dump is probably because you left modules enabled. Disable and reboot before you start all of this. All your doing is supplying an apparent stock boot.img to allow ota to install. I just did process going to F-18 and all is well. Actually I msm back to A10 patch boot there. And carry it all the way to latest update. !! Pm me if you have any questions and gl.
Click to expand...
Click to collapse
I did everything except disable modules. Do I disable modules first, then do "restore images?" Is there a reboot after disabling modules? [EDIT: nevermind, i see you did say to reboot after disabling modules]
How do I start over? Right now the other slot doesn't boot and in the OS the system update just says "reboot to apply update" as in it won't reinstall it. I've also tried flashing the boot image over with stock so I've sort of already messed up the inactive slot, probably.

thx1200 said:
I did everything except disable modules. Do I disable modules first, then do "restore images?" Is there a reboot after disabling modules? [EDIT: nevermind, i see you did say to reboot after disabling modules]
How do I start over? Right now the other slot doesn't boot and in the OS the system update just says "reboot to apply update" as in it won't reinstall it. I've also tried flashing the boot image over with stock so I've sort of already messed up the inactive slot, probably.
Click to expand...
Click to collapse
https://onepluscommunityserver.com/list/Unbrick_Tools/
If it was me I'd start fresh. Run msm tool will take you back to Android 10. 11.2.4.4 patch boot here and carry all the way through. Won't have modules to disable. In A10 you just use 23.1 magisk version . Patch boot.img. fastboot boot patched.img direct install then it backs up stock properly. You really need working msm tool handy anyway.

In order to update through A13/f18 you need magisk 25.2 stable to carry it through. Just start with 23.1 to patch . Then update magisk version.

I want to avoid wiping and starting over if possible. My Slot A boots fine, has root (I reflashed the Magisk modified boot image and it came right back), and everything is working on OOS13 F17. I just need to get the new update into Slot B which the updater seems to think is already applied.
Can I just redo the OTA or flash the full OOS13 F17 through OOS Updater?

thx1200 said:
I want to avoid wiping and starting over if possible. My Slot A boots fine, has root (I reflashed the Magisk modified boot image and it came right back), and everything is working on OOS13 F17. I just need to get the new update into Slot B which the updater seems to think is already applied.
Can I just redo the OTA or flash the full OOS13 F17 through OOS Updater?
Click to expand...
Click to collapse
Have you tried updating to build through system updates ? Instead of third party app.

mattie_49 said:
Have you tried updating to build through system updates ? Instead of third party app.
Click to expand...
Click to collapse
I'm sorry, I don't understand what you are asking. I have only used system updates so far. About -> Update. Currently that is saying it's installed and to reboot.

OK, I dug myself out of the hole. Here is how I fixed my situation and successfully updated to F.18 without any data loss.
Beginning state:
SLOT A: OOS13 F.17, rooted, working
SLOT B: OOS13 F.18, broken, will not boot
1. Disabled all Magisk Modules
2. Reboot
3. Used Oxygen Updater to download the FULL rom, which is currently at F.17, which matches the level I was operating under currently.
4. Installed this ROM, which went into SLOT B.
5. Tested booting. Worked, but no root (as expected). Double checked I was in SLOT B. I was.
6. Boot back to SLOT A.
7. Use Magisk to patch the inactive partition.
8. Boot back to SLOT B.
9. Tested root. Working.
10. Magisk uninstall, Restore Images Only
11. Using Oxygen Updater, downloaded the F.18 OTA incremental.
12. Install incremental.
13. Use Magisk to patch the inactive partition.
14. Reboot.
15. Success!
16. Re-enable Magisk Modules.
17. Reboot.
18. Still success!

thx1200 said:
OK, I dug myself out of the hole. Here is how I fixed my situation and successfully updated to F.18 without any data loss.
Beginning state:
SLOT A: OOS13 F.17, rooted, working
SLOT B: OOS13 F.18, broken, will not boot
1. Disabled all Magisk Modules
2. Reboot
3. Used Oxygen Updater to download the FULL rom, which is currently at F.17, which matches the level I was operating under currently.
4. Installed this ROM, which went into SLOT B.
5. Tested booting. Worked, but no root (as expected). Double checked I was in SLOT B. I was.
6. Boot back to SLOT A.
7. Use Magisk to patch the inactive partition.
8. Boot back to SLOT B.
9. Tested root. Working.
10. Magisk uninstall, Restore Images Only
11. Using Oxygen Updater, downloaded the F.18 OTA incremental.
12. Install incremental.
13. Use Magisk to patch the inactive partition.
14. Reboot.
15. Success!
16. Re-enable Magisk Modules.
17. Reboot.
18. Still success!
Click to expand...
Click to collapse
Very nice. Glad you got it. Very frustrating these devices and their A& B partitions.

thx1200 said:
Beginning state:
SLOT A: OOS13 F.17, rooted, working
SLOT B: OOS13 F.18, broken, will not boot
1. Disabled all Magisk Modules
2. Reboot
3. Used Oxygen Updater to download the FULL rom, which is currently at F.17, which matches the level I was operating under currently.
4. Installed this ROM, which went into SLOT B.
5. Tested booting. Worked, but no root (as expected). Double checked I was in SLOT B. I was.
6. Boot back to SLOT A.
7. Use Magisk to patch the inactive partition.
8. Boot back to SLOT B.
9. Tested root. Working.
10. Magisk uninstall, Restore Images Only
11. Using Oxygen Updater, downloaded the F.18 OTA incremental.
12. Install incremental.
13. Use Magisk to patch the inactive partition.
14. Reboot.
15. Success!
16. Re-enable Magisk Modules.
17. Reboot.
18. Still success!
Click to expand...
Click to collapse
way to complicated, is there an easy way?
mattie_49 said:
In order to update through A13/f18 you need magisk 25.2 stable to carry it through. Just start with 23.1 to patch . Then update magisk version.
Click to expand...
Click to collapse
does you mean downgrade magisk to 23 will help?

Nobody ever was able to install F.18 on a rooted phone?

Suncatcher16 said:
Nobody ever was able to install F.18 on a rooted phone?
Click to expand...
Click to collapse
Its not hard as I have done it. Just use latest canary magisk.

Suncatcher16 said:
Nobody ever was able to install F.18 on a rooted phone?
Click to expand...
Click to collapse
I transfered root from f17 to f18 with 25.2 not canary. It works sir..you uninstall magisk only restore images. Start internal ota . Use install feature on magisk to install to inactive. Real simple.

This is how I have been doing it, not the quickest though.
1. Download OOS update from Oxygen Updater.
2. Disable all Magisk modules.
3. Flash stock boot.img
4. Flash OOS update via Local OOS System Update app.
5. Reboot
6. Extract boot.img using MSM readback
7. Patch boot.img through Magisk
8. Flash patched boot.img
9. Turn all Magisk modules back on.
When I was on OOS 12, I did try using the restore image option in Magisk but it never worked for me, this is why I had to do it this way. However, I have not tried on OOS 13 so I will give this another crack on the next update. If it does work, its way easier.

Z-Blade said:
This is how I have been doing it, not the quickest though.
1. Download OOS update from Oxygen Updater.
2. Disable all Magisk modules.
3. Flash stock boot.img
4. Flash OOS update via Local OOS System Update app.
5. Reboot
6. Extract boot.img using MSM readback
7. Patch boot.img through Magisk
8. Flash patched boot.img
9. Turn all Magisk modules back on.
When I was on OOS 12, I did try using the restore image option in Magisk but it never worked for me, this is why I had to do it this way. However, I have not tried on OOS 13 so I will give this another crack on the next update. If it does work, its way easier.
Click to expand...
Click to collapse
That is because you did not let magisk make the backup in the first place. After you patch the img, you are supposed to fastboot boot patch img not flash.

MrSteelX said:
That is because you did not let magisk make the backup in the first place. After you patch the img, you are supposed to fastboot boot patch img not flash.
Click to expand...
Click to collapse
Ahhhh... I take it after you boot into the patched image, you go into Magisk and do a direct install?

Z-Blade said:
Ahhhh... I take it after you boot into the patched image, you go into Magisk and do a direct install?
Click to expand...
Click to collapse
Yes

mattie_49 said:
I transfered root from f17 to f18 with 25.2 not canary. It works sir..you uninstall magisk only restore images. Start internal ota . Use install feature on magisk to install to inactive. Real simple.
Click to expand...
Click to collapse
Did you do any additional steps after you restored images and saw "restoration done" message? I tried several times and installation fails anyway. I did all according to these steps
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io

MrSteelX said:
Just use latest canary magisk.
Click to expand...
Click to collapse
Where did you download it? Could you drop the link please?