Develop Bugs

installing Dec OTA w magisk?

For those of us that have not installed a custom recovery, will be below method work of restoring stock boot image for installing updates to the o t a? I see that a few people have already gotten the December OTA.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

is the dec update already 8.1 or just the security update?

pa.pn2 said:
is the dec update already 8.1 or just the security update?
Click to expand...
Click to collapse
8.1
Factory images are up as well.

Cowbell_Guy said:
For those of us that have not installed a custom recovery, will be below method work of restoring stock boot image for installing updates to the o t a? I see that a few people have already gotten the December OTA.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
I've been asking this question since the November OTA and have yet to get a confirmation either way whether it works or fails.
I'd love to try myself but I'm currently traveling for work and I can't risk bootlooping my phone or being without WiFi tethering.

Jexx11 said:
I've been asking this question since the November OTA and have yet to get a confirmation either way whether it works or fails.
I'd love to try myself but I'm currently traveling for work and I can't risk bootlooping my phone or being without WiFi tethering.
Click to expand...
Click to collapse
What worked for me was,
Download Nov factory image
Unzip
Edit flash-all. Bat and remove the - w at the end
Reboot into bootloader
Run flash-all
Reboot
Download Dec ota zip
Reboot recovery
Update from adb
Choose Dec ota zip
Reboot
From there i installed twrp and magisk everything working fine on 8.1

Has anyone tried this yet?

I just went to try this method, and it's getting hung up?

Its not working for me. I flashed stock Dec 2017 build, and then I install Magisk Manager and told it to "install," patched the boot file from the Dec 2017 factory build, copied it to computer, then fastboot flash boot patched_boot.img. On boot, magisk manager says "Magisk not installed," safetynet is failing, and root checker says I have no root.
Anyone having any luck? What are ya'll doing differently?

Jdban said:
Its not working for me. I flashed stock Dec 2017 build, and then I install Magisk Manager and told it to "install," patched the boot file from the Dec 2017 factory build, copied it to computer, then fastboot flash boot patched_boot.img. On boot, magisk manager says "Magisk not installed," safetynet is failing, and root checker says I have no root.
Anyone having any luck? What are ya'll doing differently?
Click to expand...
Click to collapse
did you enable the beta channel within magisk? That will get you the newest version?

CyberpodS2 said:
did you enable the beta channel within magisk? That will get you the newest version?
Click to expand...
Click to collapse
Thanks! That did it!

CyberpodS2 said:
did you enable the beta channel within magisk? That will get you the newest version?
Click to expand...
Click to collapse
I didn't do that initially but will try now

Jdban said:
Thanks! That did it!
Click to expand...
Click to collapse
Really? Nice. Mind positing your exact steps? (

Jdban said:
Thanks! That did it!
Click to expand...
Click to collapse
Really? Nice. Mind positing your exact steps? (

Cowbell_Guy said:
Really? Nice. Mind positing your exact steps? (
Click to expand...
Click to collapse
What I did:
Install Dec 2017 factory build (without the -w flag so it doesn't wipe)
Install latest Magisk Manager
Enable beta channel in Magisk Manager
Copy the boot.img file from the factory build onto the phone
In Magisk, click install -> Patch boot image file
Copy patched boot file from phone to computer
reboot to bootloader
flash patched boot.mg via
Code:
fastboot flash boot patched_boot.img

Jdban said:
What I did:
Install Dec 2017 factory build (without the -w flag so it doesn't wipe)
Install latest Magisk Manager
Enable beta channel in Magisk Manager
Copy the boot.img file from the factory build onto the phone
In Magisk, click install -> Patch boot image file
Copy patched boot file from phone to computer
reboot to bootloader
flash patched boot.mg via
Click to expand...
Click to collapse
Ah, okay. Thanks for sharing I take it though you didn't use the Top John Woo method, Lincoln the original post oh, that supposedly doesn't require the use of a computer.

Root pie Dec update (v10.0.2)

I got update from oero to pie via OTA today,
I tried many patched boot.img and root maunally by patching stock img but its stuck on boot screen.. Any idea??

Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.

Hakkinan said:
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Click to expand...
Click to collapse
What's mean " in both slots " ?
I tried to patch boot.img maunally but my device stuck on boot animations, So I flashed back stock boot.img into fastboot without root agian..

This is an A/B device which means that it has two slots for every partition (A and B). You need to flash the stock boot in the same partirion that it currently being used, flashing It in both is just to be safe in future updates.

Oh hey try this one: https://drive.google.com/file/d/1dBX2dZV_wWgSip8d9lk0lrO_JHfxGdKU/view?usp=sharing

Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.

FRibeiro1400 said:
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
Click to expand...
Click to collapse
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).

Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?

FRibeiro1400 said:
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
Click to expand...
Click to collapse
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"

Hakkinan said:
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Click to expand...
Click to collapse
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?

HaN5aR said:
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
Click to expand...
Click to collapse
Wait, did you try to flash the whole OTA?

Hakkinan said:
Wait, did you try to flash the whole OTA?
Click to expand...
Click to collapse
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations

Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?

HaN5aR said:
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Click to expand...
Click to collapse
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
FRibeiro1400 said:
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
Click to expand...
Click to collapse
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.

Hakkinan said:
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Click to expand...
Click to collapse
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.

FRibeiro1400 said:
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
Click to expand...
Click to collapse
Doesn't matter if you had 10.0.1.0 previously or not. You can download it and install it without losing data.

December update not rootable?

I just flashed the full image (flashall removed the -w) and attempted the magisk boot.img patch that I've been doing since the phone was released for months now. I'm on Magisk canary up to date (7.4.1-72edbfc4 (260)). When I patch the boot.img and reflash it as magisk_patched.img I just get a bootlooping Google logo. I flashed back to stock boot.img and tried again...... Same thing.
Is anyone else able to root via Magisk patching the boot.img file?

DriveEuro said:
I just flashed the full image (flashall removed the -w) and attempted the magisk boot.img patch that I've been doing since the phone was released for months now. I'm on Magisk canary up to date (7.4.1-72edbfc4 (260)). When I patch the boot.img and reflash it as magisk_patched.img I just get a bootlooping Google logo. I flashed back to stock boot.img and tried again...... Same thing.
Is anyone else able to root via Magisk patching the boot.img file?
Click to expand...
Click to collapse
Hello could u give me boot.img plz already installed but via OTA so i dont have the file i want to patch it wih magisk for root :crying:

rafik25 said:
Hello could u give me boot.img plz already installed but via OTA so i dont have the file i want to patch it wih magisk for root :crying:
Click to expand...
Click to collapse
https://developers.google.com/android/images
Download the factory image from here. Extract out the boot.img file.

DriveEuro said:
https://developers.google.com/android/images
Download the factory image from here. Extract out the boot.img file.
Click to expand...
Click to collapse
Bro for december ? i see only November

rafik25 said:
Bro for december ? i see only November
Click to expand...
Click to collapse
10.0.0 (QQ1A.191205.011, Dec 2019)
Listed right at the bottom for bonito section.

DriveEuro said:
10.0.0 (QQ1A.191205.011, Dec 2019)
Listed right at the bottom for bonito section.
Click to expand...
Click to collapse
Thx boot.img already patched :good:

I ended up wiping my device and flashing stock Dec image. :-/

DriveEuro said:
I just flashed the full image (flashall removed the -w) and attempted the magisk boot.img patch that I've been doing since the phone was released for months now. I'm on Magisk canary up to date (7.4.1-72edbfc4 (260)). When I patch the boot.img and reflash it as magisk_patched.img I just get a bootlooping Google logo. I flashed back to stock boot.img and tried again...... Same thing.
Is anyone else able to root via Magisk patching the boot.img file?
Click to expand...
Click to collapse
I've had this happen to me before. However it was always when I moved the wrong file patched file from the phone to the computer and therefore I flashed the wrong file to the phone which obviously causes a bootloop.
For some reason when this happened, the patched file didn't immediately show up in the Android. I know this because I checked the file and it had a modified date of a month earlier (from the last update). After a while (perhaps a reboot), the new file showed up (overwriting the old file), but with the correct modified date. I took that file and moved it to the computer and flashed it without any issues.
I can't tell you why this occurred, but I am 95% positive you experienced the same thing. You followed the directions correctly and thought you were flashing the latest modified boot image, but I bet it was really the old file.

sic0048 said:
I've had this happen to me before. However it was always when I moved the wrong file patched file from the phone to the computer and therefore I flashed the wrong file to the phone which obviously causes a bootloop.
For some reason when this happened, the patched file didn't immediately show up in the Android. I know this because I checked the file and it had a modified date of a month earlier (from the last update). After a while (perhaps a reboot), the new file showed up (overwriting the old file), but with the correct modified date. I took that file and moved it to the computer and flashed it without any issues.
I can't tell you why this occurred, but I am 95% positive you experienced the same thing. You followed the directions correctly and thought you were flashing the latest modified boot image, but I bet it was really the old file.
Click to expand...
Click to collapse
I checked the time/date stamps each time and they were definitely from today. Doesn't matter much at this point because I already flashed back to stock rom. Was able to room there. Have no clue why I had this problem. I've been on the 3a since the week it came out and I've been flashing pactched boot images nearly just as long too. Oh well.

DriveEuro said:
I checked the time/date stamps each time and they were definitely from today. Doesn't matter much at this point because I already flashed back to stock rom. Was able to room there. Have no clue why I had this problem. I've been on the 3a since the week it came out and I've been flashing pactched boot images nearly just as long too. Oh well.
Click to expand...
Click to collapse
Weird. At least you got it fixed. That's why I love the Pixel phones. They are virtually impossible to brick (as long as the bootloader is unlocked).

DriveEuro said:
I just flashed the full image (flashall removed the -w) and attempted the magisk boot.img patch that I've been doing since the phone was released for months now. I'm on Magisk canary up to date (7.4.1-72edbfc4 (260)). When I patch the boot.img and reflash it as magisk_patched.img I just get a bootlooping Google logo. I flashed back to stock boot.img and tried again...... Same thing.
Is anyone else able to root via Magisk patching the boot.img file?
Click to expand...
Click to collapse
Patching the boot IMG with magisk worked for me no problem

I am having the same issue. I was able to root with a magisk patched boot.img from the November update, but I go into a bootloop when using a magisk patched boot.img from the December update. I have reverted back to the non patched root.img for December. I would love to have it patched though.
Can someone share a patched boot.img for december?

Not sure if youre interested in a custom kernel but youre welcome to to my latest build which is pre-rooted.

mxrodriguez said:
I am having the same issue. I was able to root with a magisk patched boot.img from the November update, but I go into a bootloop when using a magisk patched boot.img from the December update. I have reverted back to the non patched root.img for December. I would love to have it patched though.
Can someone share a patched boot.img for december?
Click to expand...
Click to collapse
You must be doing something wrong because it worked for me no problem. I have the December boot.img patched on my computer. I can upload it if you want?

thatsupnow said:
You must be doing something wrong because it worked for me no problem. I have the December boot.img patched on my computer. I can upload it if you want?
Click to expand...
Click to collapse
That would be great.
I can give it a try and flash your patched boot.img.
Im using Magisk 20.1 right now but it doesnt seem to be working

mxrodriguez said:
That would be great.
I can give it a try and flash your patched boot.img.
Im using Magisk 20.1 right now but it doesnt seem to be working
Click to expand...
Click to collapse
Here you go https://drive.google.com/file/d/1253hD26lHFQMhUJZ5_Fu6rLZLr1tLq7k/view?usp=drivesdk

I was able to root the December update but I wipe and flash the whole image, not just the ota

thatsupnow said:
Here you go https://drive.google.com/file/d/1253hD26lHFQMhUJZ5_Fu6rLZLr1tLq7k/view?usp=drivesdk
Click to expand...
Click to collapse
Tried my patched file and yours still getting the looped google logo. Been sitting there for about 10 minutes and nothing. Reflashing the stock boot allows the phone to boot but its unrooted and with TWRP unsupported this is the only method.
I had no idea the android Q update downloaded and would automatically install when I rebooted my phone. I just want my root back. Looks like I'll have to flash stock and retry. Since I dont have root and can't use Titantium Backup any one know any decent alternatives?

thatsupnow said:
Here you go https://drive.google.com/file/d/1253hD26lHFQMhUJZ5_Fu6rLZLr1tLq7k/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks @thatsupnow
I finally got around to trying your patched file and I continue to get into the G-logo bootloop.
Not sure why I cant patch the December update. I was able to patch the Nov update and get root so hopefully it will work on the the Jan update. At least I know Im not crazy since I dont seem to be the only one with this problem. I have not tried wiping everything and trying to apply the patched boot img since it shouldnt be needed.
Im back to stock non-root on this December patch.
Hopefully the next one will work for me.
Thanks

mxrodriguez said:
Thanks @thatsupnow
I finally got around to trying your patched file and I continue to get into the G-logo bootloop.
Not sure why I cant patch the December update. I was able to patch the Nov update and get root so hopefully it will work on the the Jan update. At least I know Im not crazy since I dont seem to be the only one with this problem. I have not tried wiping everything and trying to apply the patched boot img since it shouldnt be needed.
Im back to stock non-root on this December patch.
Hopefully the next one will work for me.
Thanks
Click to expand...
Click to collapse
Yes its quite frustrating I think I may also wait.

Is there an easy way to update an unlocked/rooted Pixel 3a XL?

I unlocked my bootloader and rooted my Pixel 3a XL as soon as I got it. But I've been unable to install the OTA and security updates since (September 2019). I've been digging around in the forum trying to figure out how to load the updates. I was really hoping Flashfire would work, but it gives me errors - something about the root not being available or right... but my root works for everything else I've tried (maybe its an issue with Magisk)...
Anyway, I was hoping to find a simple way to install the updates. Help!
Thanks in advance,
Tom

Tom2112 said:
I unlocked my bootloader and rooted my Pixel 3a XL as soon as I got it. But I've been unable to install the OTA and security updates since (September 2019). I've been digging around in the forum trying to figure out how to load the updates. I was really hoping Flashfire would work, but it gives me errors - something about the root not being available or right... but my root works for everything else I've tried (maybe its an issue with Magisk)...
Anyway, I was hoping to find a simple way to install the updates. Help!
Thanks in advance,
Tom
Click to expand...
Click to collapse
I have seen postings about people fastboot flashing back the original boot.img, then taking the ota then repatching the new boot image and flashing it via fastboot. Not as simple as you hoped i am sure but it works.
The other way is to download the full image, remove the -w option in the flashsall.bat and then run the modded flashall file. You then need to patch the new boot image as above and fastboot flash that to regain root. I have not found any other ways to get updates besides doing one of the 2 above every month

Thanks, adm1jtg! I appreciate the help.
Unfortunately, I tried the second method you mentioned on my own... but I missed the part about removing the -w from the flashall.bat. Faaaaaaaaaaaqqqqqqqq!!! And ended up wiping my phone.
But now I think I'll remember that -w trick! I love learning things the hard way. LOL
I'm still going to hold out hope that someone will come along and make an app like FlashFire to script the process for us.

Tom2112 said:
Thanks, adm1jtg! I appreciate the help.
Unfortunately, I tried the second method you mentioned on my own... but I missed the part about removing the -w from the flashall.bat. Faaaaaaaaaaaqqqqqqqq!!! And ended up wiping my phone.
But now I think I'll remember that -w trick! I love learning things the hard way. LOL
I'm still going to hold out hope that someone will come along and make an app like FlashFire to script the process for us.
Click to expand...
Click to collapse
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing

thatsupnow said:
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing
Click to expand...
Click to collapse
Sideloading the ota would be a great option EXCEPT he said he was on a much older version... Like sept.
My understanding is that the ota for dec would only contain changes implemented for the month of December, this in this scenerio he would not get the patches for October and November with your method and i am not even sure if it would boot after that mismatch
It's really not saving much work if any over flashing the full version, and with the full version they're is no potential for bootloop due to missing some patches or updates. It's just much safer.

thatsupnow said:
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing
Click to expand...
Click to collapse
Um... prolly because I'm dumb... and maybe a little because I couldn't find instructions on how to do it properly. I don't suppose you happen to have a link to how to do the OTA sideload thing properly?

Tom2112 said:
Um... prolly because I'm dumb... and maybe a little because I couldn't find instructions on how to do it properly. I don't suppose you happen to have a link to how to do the OTA sideload thing properly?
Click to expand...
Click to collapse
https://developers.google.com/android/ota

The most simple way to update while keeping root would be to follow the instructions for "Devices with A/B Partitions" at the following link in the Magisk documentation:
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Basically, Magisk allows you to restore the original boot image to the current partition so you can take the OTA when it arrives on your phone. Before rebooting you install Magisk to the inactive slot so that when the phone restarts you retain root without having to mess with Fastboot.

Delete Me!
Think all you have to do is click uninstall magisk, dont reboot... Take ota, but before reboot click install magisk/ install to empty slot...
Oops didnt see the reply above

OK, so when this month's security update came out, I tried to following the Magisk instructions (uninstall Magisk, restore stock boot, flash OTA, etc...) but when I went to uninstall Magisk and restore the stock boot, it tells me there is no stock boot image to restore! Dammit. Now what?

Tom2112 said:
OK, so when this month's security update came out, I tried to following the Magisk instructions (uninstall Magisk, restore stock boot, flash OTA, etc...) but when I went to uninstall Magisk and restore the stock boot, it tells me there is no stock boot image to restore! Dammit. Now what?
Click to expand...
Click to collapse
This should be a one time issue. One of the latest versions of Magisk changed the default location of the boot.img backup. They released it in December after most of us had already upgraded to the December Pixel update. This means we used the older version of Magisk when we installed the Dec update and it saved the backup to the old/original location. We then updated Magisk sometime later in December, but the Magisk update doesn't move the backup file to the new location (a poor execution from the Magisk team IMHO). Because we are now on the updated version, it expects the boot.img backup to be in the new location, but it is still in the old location and Magisk doesn't check that old location (again, a poor execution from the Magisk team IMHO).
To fix this you have several options.....
Option one is to find the original backup location that Magisk used for the boot.img and move it to the new backup location that Magisk uses. Unfortunately, I don't know where those backup locations are and didn't feel like researching it, so I used one of the other methods.
Option two is to "reinstall" Magisk (choose the patch file option and select the stock boot.img that may still on the phone from whatever the last update was (if you sideloaded the update and then had to rerooted the phone)- or download it from the applicable factory image and move it to the phone) to force Magisk to backup the current boot.img file to the new location. Stop after this initial step (ie you don't actually need to flash the patched file because it has already been done). Then you should be able to follow the normal Magisk update process to move to the January update.
That being said, I have horrible success being able to take the updates OTA (they usually fail) and usually end up sideloading the update. That is the final option - sideload the Jan update and then reroot the phone using the normal root method (ie getting Magisk to patch the stock boot.img file and then flashing the patched file).

Question OTA OOS 1.2.3.3 AA Boot Image Needed

Just curious if anybody has been able to get the boot image from the incremental update of OOS 1.2.3.3 AA from Magisk ?
I recently got the boot image for 1.2.2 AA from someone using magisk so just wondering if anybody has gotten the latest.

oos 11.2.3.3 AA boot.img，you can patch it in magisk 22.0, then flash it via fastboot.

xls654 said:
oos 11.2.3.3 AA boot.img，you can patch it in magisk 22.0, then flash it via fastboot.
Click to expand...
Click to collapse
how did you get the image? You lose root after updating, since you need a stock boot image to update, and global is not updated on the website

Andrew8578 said:
how did you get the image? You lose root after updating, since you need a stock boot image to update, and global is not updated on the website
Click to expand...
Click to collapse
Im pretty sure he was able to get it through magisk and installing an inactive slot to the latest OOS. and then got the stock boot image of 1.2.3.3 but i could be wrong lol

For what it is worth, I ended up not needing this, this time. I was able to use Magisk's Uninstall/Restore function and install the OTA. This OTA did not force a reboot, so I was able to go back into Magisk and reinstall to active and inactive slots before rebooting and all was good.

dmarden said:
For what it is worth, I ended up not needing this, this time. I was able to use Magisk's Uninstall/Restore function and install the OTA. This OTA did not force a reboot, so I was able to go back into Magisk and reinstall to active and inactive slots before rebooting and all was good.
Click to expand...
Click to collapse
I did something similar, which is to restore the image in magisk manager, which requires a reboot to take effect. And after rebooting, I lost root, however, the update worked.
How am I suppose to reinstall magisk after that?

Andrew8578 said:
I did something similar, which is to restore the image in magisk manager, which requires a reboot to take effect. And after rebooting, I lost root, however, the update worked.
How am I suppose to reinstall magisk after that?
Click to expand...
Click to collapse
You do not need to reboot after the restore.

dmarden said:
You do not need to reboot after the restore.
Click to expand...
Click to collapse
I did not know that. That is good to know.
Did you just restore the image, install the update, and then reinstall magisk with the OTA feature? or did you use another method

Andrew8578 said:
I did not know that. That is good to know.
Did you just restore the image, install the update, and then reinstall magisk with the OTA feature? or did you use another method
Click to expand...
Click to collapse
Yeah this happened to me.
All you have to do is update to the latest os and then download the boot image that's in this post and then go into magisk
And select file and patch
then move it to your pc
flash the patched boot image.
and then go into magisk and direct install

wooo000 said:
Yeah this happened to me.
All you have to do is update to the latest os and then download the boot image that's in this post and then go into magisk
And select file and patch
then move it to your pc
flash the patched boot image.
and then go into magisk and direct install
Click to expand...
Click to collapse
Yes, the image provided sure works. But I want to figure out how you can get the boot image yourself.
I tried to set my active slot to the inactive one, but I get nothing and it just reboot to the previous slot after a while.

Andrew8578 said:
I did not know that. That is good to know.
Did you just restore the image, install the update, and then reinstall magisk with the OTA feature? or did you use another method
Click to expand...
Click to collapse
Something is weird with the process this time, IMO... so after the OTA installs, I use Magisk to install to both the current and inactive slot.

Great information and useful site.

Hey guys, just to be sure.
Would I be on the right track for installing OTA 11.2.3.3LE15AA on 11.2.2.2LE15AA OP9P AA:
Place OTA 11.2.3.3LE15AA on root storage
Fastboot boot 11.2.3.3 "Root lost"
Install local upgrade of OTA 11.2.3.3LE15AA no reboot
Magisk patch Direct Install then Magisk patch inactive slot, reboot.
Can anyone let me know.
Tx guys!

My question is how did someone get the boot.img from the OTA 11.2.3.3AA? I tried 3 different payload dumper and none extract the images.

schmeggy929 said:
My question is how did someone get the boot.img from the OTA 11.2.3.3AA? I tried 3 different payload dumper and none extract the images.
Click to expand...
Click to collapse
Get the full update zip from Oxygen updater and patch that.

Droidzone said:
Get the full update zip from Oxygen updater and patch that.
Click to expand...
Click to collapse
I know that, I'm talking about the incremental OTA. The incremental OTA 11.2.3.3 AA is out. The full OTA isn't, how did someone pull the boot.img from the incremental OTA?

Andrew8578 said:
how did you get the image? You lose root after updating, since you need a stock boot image to update, and global is not updated on the website
Click to expand...
Click to collapse
I coyped it from magisk backup, before incremental OTA reboot, At that time I still in rooted

xls654 said:
I coyped it from magisk backup, before incremental OTA reboot, At that time I still in rooted
Click to expand...
Click to collapse
that makes sense actually. It's still weird that you don't need to reboot to get the boot image. But i'll keep that in mind. Thank you!