Database Info

Couldn't install system update (november security patch)

I have just received the OTA and it is failing to install...
Anybody else facing this issue? Any ideas on how to fix it?
I have my Pixel 2 rooted right now, not sure if this can affect OTA?

luizffgarcia said:
I have my Pixel 2 rooted right now, not sure if this can affect OTA?
Click to expand...
Click to collapse
Being rooted is your issue

krelvinaz said:
Being rooted is your issue
Click to expand...
Click to collapse
What is the easiest way around it then? Do i have to download the factory image and flash it losing everything i have configured? Or is there another way?

https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Follow them steps
Nothing seems to work for me though i cant install ota no matter what but hopefully it should work for you.
It has for everyone else!

UpGrad3 said:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Follow them steps
Nothing seems to work for me though i cant install ota no matter what but hopefully it should work for you.
It has for everyone else!
Click to expand...
Click to collapse
Thanks but this also does not work for me, it starts step 1 but then the installation fails...
Any other options?
EDIT: LOL and now i lost magisk and root

luizffgarcia said:
Thanks but this also does not work for me, it starts step 1 but then the installation fails...
Any other options?
EDIT: LOL and now i lost magisk and root
Click to expand...
Click to collapse
I'm in the same boat...dies at step 1. Look familiar?
https://forum.xda-developers.com/showpost.php?p=74518728&postcount=53
Only I didn't lose root, as I re-installed Magisk before rebooting.

JayBlack_686 said:
I'm in the same boat...dies at step 1. Look familiar?
https://forum.xda-developers.com/showpost.php?p=74518728&postcount=53
Only I didn't lose root, as I re-installed Magisk before rebooting.
Click to expand...
Click to collapse
Yeah i sideloaded the OTA and it worked, but now i am struggling to put back snoke and magisk...
Every time i try i get stuck in the google logo, not sure whats going wrong

luizffgarcia said:
Yeah i sideloaded the OTA and it worked, but now i am struggling to put back snoke and magisk...
Every time i try i get stuck in the google logo, not sure whats going wrong
Click to expand...
Click to collapse
That happened the first time I tried to root. Had to flash the factory image and start over. Guess I could do that...but seems there has to be an easier way. I'm really curious why the method in that guide doesn't work for me.

Does flashfire work to install the OTA?

luizffgarcia said:
Thanks but this also does not work for me, it starts step 1 but then the installation fails...
Any other options?
EDIT: LOL and now i lost magisk and root
Click to expand...
Click to collapse
JayBlack_686 said:
I'm in the same boat...dies at step 1. Look familiar?
https://forum.xda-developers.com/showpost.php?p=74518728&postcount=53
Only I didn't lose root, as I re-installed Magisk before rebooting.
Click to expand...
Click to collapse
Download the full factory image. Open the flash all bat file with notepad and edit out the -w and save it. Then run it. That will flash the full factory image but leave apps and data in place.
Then you reroot it.

TonikJDK said:
Download the full factory image. Open the flash all bat file with notepad and edit out the -w and save it. Then run it. That will flash the full factory image but leave apps and data in place.
Then you reroot it.
Click to expand...
Click to collapse
Thanks. When I re-root, do I need to do the whole patch boot image process again? Or should I reuse the patched_boot.img that I used when I rooted the first time?

JayBlack_686 said:
Thanks. When I re-root, do I need to do the whole patch boot image process again? Or should I reuse the patched_boot.img that I used when I rooted the first time?
Click to expand...
Click to collapse
Redo it, otherwise you are a month behind on the boot IMG.

TonikJDK said:
Redo it, otherwise you are a month behind on the boot IMG.
Click to expand...
Click to collapse
Thank you. One last question: when I rooted, I used the snoke kernel and pointed to that .img file when patching the boot image (no reason, other than that's what everyone seemed to be using when root first happened). It sounds like this time, I should get the full factory image, extract, grab the boot.img from within that and patch THAT to be up to date. Correct?

JayBlack_686 said:
Thank you. One last question: when I rooted, I used the snoke kernel and pointed to that .img file when patching the boot image (no reason, other than that's what everyone seemed to be using when root first happened). It sounds like this time, I should get the full factory image, extract, grab the boot.img from within that and patch THAT to be up to date. Correct?
Click to expand...
Click to collapse
Correct, you can use whatever boot IMG you want. Snoke may be updated to November... don't know...bit if it is and you like it use it.

Waiting for answers. I finally succeeded with rooting my xiaomi mi a2 lite, everything works perfect, I was so excited to install Xposed but then my phone started to lag AF. I uninstalled it and then the update show up in the notification bar, great but "couldn't install system update". Is it because of the root or TWRP?

update to 5.1.7

hi guys i am on 5.1.6 oos rooted twrp installed now i want to update to 5.1.7 so can i update just like that in updater app or should i have to do any prerequisites

Don't do it. 5.1.8 will be released end of next week and you will be doing this all over again. I was going to myself but I'm waiting until the next release until someone pushes full writeup and review

You can install it via the update manager. But yes, you are going to lose twrp and root, which is not a problem at all since it took me only like 5 minutes to get it all working again.
I followed this guide: https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558

memocatcher said:
You can install it via the update manager. But yes, you are going to lose twrp and root, which is not a problem at all since it took me only like 5 minutes to get it all working again.
I followed this guide: https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
Click to expand...
Click to collapse
Thanks

dgunn said:
Don't do it. 5.1.8 will be released end of next week and you will be doing this all over again. I was going to myself but I'm waiting until the next release until someone pushes full writeup and review
Click to expand...
Click to collapse
Lol... And after that there will be a new build in another week...

The more updates, the better. We won't complain, do we? I'm glad, we don't suffer for updates like SAMEsung-users do.

Manivannan9444 said:
hi guys i am on 5.1.6 oos rooted twrp installed now i want to update to 5.1.7 so can i update just like that in updater app or should i have to do any prerequisites
Click to expand...
Click to collapse
Updating via twrp and then (before reboot) re flashing twrp.zip and magisk will grant you to maintain twrp and root

Manivannan9444 said:
hi guys i am on 5.1.6 oos rooted twrp installed now i want to update to 5.1.7 so can i update just like that in updater app or should i have to do any prerequisites
Click to expand...
Click to collapse
Did you successfully do it? If yes please tell what procedure you followed.
Do I need to backup internal? Or my apps?
Thanks.

sarthak kumar said:
Did you successfully do it? If yes please tell what procedure you followed.
Do I need to backup internal? Or my apps?
Thanks.
Click to expand...
Click to collapse
if u update through the OS like updater app or anything, u will have to re-flash twrp using the fastboot method, if you already have twrp installed then just update via twrp with full zip, install twrp installer zip, and then magisk (i usually reboot back to recovery after i install twrp installer then flash magisk). Then you are done, u do not lose anything and do no wipe anything either

Bradl79 said:
if u update through the OS like updater app or anything, u will have to re-flash twrp using the fastboot method, if you already have twrp installed then just update via twrp with full zip, install twrp installer zip, and then magisk (i usually reboot back to recovery after i install twrp installer then flash magisk). Then you are done, u do not lose anything and do no wipe anything either
Click to expand...
Click to collapse
Should i have to change slot after twrp flash of full rom

The easiest way is to download and install the update through the settings app then BEFORE you reboot open Magisk, click install then install to second slot.
No flash or worrying

sarthak kumar said:
Did you successfully do it? If yes please tell what procedure you followed.
Do I need to backup internal? Or my apps?
Thanks.
Click to expand...
Click to collapse
Download the ota.zip, reboot to TWRP, flash ota, flash TWRP.zip, reboot to OS, reboot to recovery again if you want magisk and install magisk zip. Done. No data loss or changing settings.

October image is up

I've always wanted to post one of these
https://developers.google.com/android/images

How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates

Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.

kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
I was looking thru that post and didnt wanna risk wiping the device. I just had to wipe a few days ago due to Edxposed bootloop issue lol

Ha, yeah, I feel your pain there, wiping is way too much of a pain to do that frequently

Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
You can also flash the OTA file in stock recovery and not lose data.

spotmark said:
You can also flash the OTA file in stock recovery and not lose data.
Click to expand...
Click to collapse
Will it retain root or do you mean - https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

Androider4Life said:
Retain root or have to re-root
Click to expand...
Click to collapse
Have to re-root using the Magisk method. Put stock boot on phone, patch boot with Magisk, put modded boot back on computer, and flash in fastboot. AFAIK, there is no way to retain root. Every time you flash the latest monthly patch, it flashes a new stock boot. Therefore, no root.

kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
There's a way with taking the ota through settings I found out how from a user on here which is:
Once received the ota , go to magisk first uninstall/restore images then download/install ota then DONT REBOOT, go back to magisk install magisk to inactive slot from the app then reboot and all should work with new ota update and have root still.

What is this update 4.3mb

Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML

gettinwicked said:
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
Click to expand...
Click to collapse
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117

gm007 said:
What is this update 4.3mb
Click to expand...
Click to collapse
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.

Jiggs82 said:
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Click to expand...
Click to collapse
You missed the part where I did try flashing the image. I've done this a hundred times, so, I did it right.
Anyway, I got it. I didn't realize my work computer had a USB-C port, so, I grabbed one and tried flashing the image with that. Worked! Thank God... I guess sdk tools doesn't like a USB 1 to C cable, and my phone doesn't like going into recovery...

Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'

Homeboy76 said:
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Click to expand...
Click to collapse
I am starting to feel more and more like a lot of the bootloop issues are being caused by OTAs swapping slots on install. Besides the --slot all patched boot, it might help to run the OTA twice to get it to install to both slots completely. Preferably though, quit using OTAs and work with -w removed flash-all installer (and even then possibly installing to both slots with an active slot swap in between and before rooting). The double install is common when installing custom ROMs, and the process for OTA sideloads is pretty similar.

Performance improvement, feels smooth and responsive. Glad i dont need to root this phone, ppl are having so many problems.

boe323 said:
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Click to expand...
Click to collapse
My download was 1.3 gb and took forever to install. That's more than just the security patch.. Build number is different too.
Sent from my Pixel 3 XL using Tapatalk

Worked exactly the same as the 10 and .C3 builds for me. Flash-all (minus -w) and patched boot in Magisk. No issues. It was not just security this month. See the functional patches in the bulletin.
https://source.android.com/security/bulletin/pixel/2019-10-01

is there new platform tools too?

[Guide] Update and Retain Root

*Note* Some people have had success with this, while some others have not. You do this at your own risk.
Prerequisites:
Magisk Manager might need to be unhidden based on reports from some users.
Magisk needs to have a backup of stock boot.img.
Preserve AVB 2.0/dm-verity must be enabled. (Have gotten mixed reports on this it might or might not be needed)
Check the following post if you don't meet the prerequisites
https://forum.xda-developers.com/showpost.php?p=81186247&postcount=73
Update Process
When phone detects update
1. Disable any desired Magisk modules, ex. Edxposed (I usually disable all modules just to be safe)
2. Reboot
3. In Magisk, select Uninstall, press Restore Images
4. Do NOT Reboot
5. Install OTA Update via Settings -> System -> System Updates
6. When prompted to reboot, Do NOT Reboot
7. In Magisk Manager press Install
8. Select Install to Inactive Slot
9. Reboot
10. Enable the Magisk modules one by one
In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.
One requires ADB
While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.
adb wait-for-device shell magisk --remove-modules
adb reboot
This will remove all modules and you should be able to boot.
The second way is via fastboot. More information in this thread.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
Some information that might help some people.
eg1122 said:
I know some users flash patched boot.img that someone else patched, thus bypassing the creation of a backup. I think choosing or not choosing to preserve avb 2.0/dm-verity also affects if phone will take OTA. I always preserve mine and always patch my own boot.img so I haven't ran into any issues. I'll just have to wait and see what happens on my end once I get the update. This reminds me of some issues some people where getting early on when rooting. Some people had to flash the patched boot.img to both a/b slots and some people didn't. Having both slots with a patched boot will also break the restoring of stock boot.img as Magisk only restores the active slot.
Click to expand...
Click to collapse

If you do it this way you'll be using the patched boot image from the previous update and not the current one.

airmaxx23 said:
If you do it this way you'll be using the patched boot image from the previous update and not the current one.
Click to expand...
Click to collapse
No it doesn't. When you select install to inactive slot it patches the newly installed boot.img that has been installed to the inactive slot. Only reason phone promts you to reboot after an update is to switch slots.

For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.

pdfruth said:
For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.
Click to expand...
Click to collapse
Yeah, there needs to be a backed up stock boot img for this to work. Being able to restore images the way stated in the issue would solve this as you could just restore a stock boot.img then continue doing the steps.

So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!

DemonicMurderer said:
So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!
Click to expand...
Click to collapse
Yes, it has worked for me all the time. These are the exact steps recommended by topjohnwu, I just made them more readibly available to users. Here is a link to his tutorial.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

This work for the Verizon Pixel 4 XL???

SAMCR02018 said:
This work for the Verizon Pixel 4 XL???
Click to expand...
Click to collapse
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.

Badger50 said:
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.
Click to expand...
Click to collapse
Ok the can the Verizon version get the BL unlocked?

SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
Nope. Unless you got lucky and they sold you a google version by mistake.

SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
There is a write up for that.

Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?

Donric13 said:
Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?
Click to expand...
Click to collapse
Yes this method works with custom kernel. Magisk removed custom kernel when it restores stock boot.img

When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?

in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
I wouldn't do it until the Dec ota comes out and that may be later today or sometime this week. Which is weird since all the other Pixels got it but hey it's Google

in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
Since it's not out yet, just do a direct install in Magisk to re-install it

Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.

mkpansare said:
Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.
Click to expand...
Click to collapse
The other way I update is using full factory images. Once you download the zip, extract it and find and open (via Notepad++ or similar advanced text editor) the flash-all.bat or flash-all.sh (depends on your system), find this line
fastboot -w update
replace with
fastboot update
Basically remove the -w, this will prevent a factory reset (wipe) on your device. Once it is done you will need to patch new boot.img via magisk and flash the newly patched boot.img via fastboot.
Hope this helps!
ps. I recommend to always disable Magisk Modules before updating as they could cause FC

eg1122 said:
Since it's not out yet, just do a direct install in Magisk to re-install it
Click to expand...
Click to collapse
Thanks that worked perfect... Was gonna be a long week without adblocker and lmt pie lol

Question [Solved] Update 11.2.10.10 AA fails when using local upgrade. Fix?

Hello All,
Attempted to update to 11.2.10.10 AA two days ago via full update zip through Oxygen Updater app and Local Upgrade, only to receive Installation Failure. When I check system update in settings it tells me only the incremental update is available.
Rooted OP9 (Magisk v23015 canary), Arter R2 Kernel, and only 5 magisk modules (hideprops, BusyBox, wifibonding, opperfdisabler, and James DSP).
Any ideas?

I also have a rooted global op9. Updated through local upgrade in oxygen updater . Full 3.0 gb zip installed and rebooted to new build! Since your using magisk you need to restore stock boot img. Probably why installation fAils.

mattie_49 said:
Since your using magisk you need to restore stock boot img.
Click to expand...
Click to collapse
How would i do that? Uninstall Magisk? Using Arter Kernel touches vendor and another partition so i believe if i restore stock boot and kernel goes down then i might have an issue. Not sure, this is the first time ive had a problem with an update. Usually its pretty seamless and same, simple process.

Porquiplane said:
How would i do that? Uninstall Magisk? Using Arter Kernel touches vendor and another partition so i believe if i restore stock boot and kernel goes down then i might have an issue. Not sure, this is the first time ive had a problem with an update. Usually its pretty seamless and same, simple process.
Click to expand...
Click to collapse
If you update ota through g-ota you for sure have to restore untouched boot,vendor_boot, dtbo prior to installing 11.2.10.10. Yes uninstall in magisk and it should restore boot image. And since you flashed a kernel you did take a stock backup of these partitions before flashing kernel?

https://android.googleapis.com/packages/ota-api/package/580d47a7dde5862a306c07ff939cc4fe1520860f.zip
Here is 11.2.10.10 ota incremental zip. All images I mentioned above must be restored before you install this. Global op9

mattie_49 said:
If you update ota through g-ota you for sure have to restore untouched boot,vendor_boot, dtbo prior to installing 11.2.10.10. Yes uninstall in magisk and it should restore boot image. And since you flashed a kernel you did take a stock backup of these partitions before flashing kernel?
Click to expand...
Click to collapse
I am not sure if i did. Unless Franco Kernel Manager does it for you, i didnt.

Porquiplane said:
I am not sure if i did. Unless Franco Kernel Manager does it for you, i didnt.
Click to expand...
Click to collapse
Updating locally through oxygen updater and it being a full zip only boot img shouldn't matter if any.

mattie_49 said:
Updating locally through oxygen updater and it being a full zip only boot img shouldn't matter if any.
Click to expand...
Click to collapse
Then not sure why i throws an installation failure message.

Well, i went to Franco Kernel to reflash the stock, and now im bootloop. Stuck on the spinning screen.

As an update, I had to reflash vendor_boot and dtbo after bootloop. Then the phone allowed me to update to the new OOS. Troubles resolved!

The question is, can I flash incremental instead of full if I'm rooted and using oxygen updater?

Moe2003 said:
The question is, can I flash incremental instead of full if I'm rooted and using oxygen updater?
Click to expand...
Click to collapse
Don't do it. Just use the full install. It's safer. I made a magisk'd boot of 11.2.10.10 if you need one after the full update.

Porquiplane said:
Don't do it. Just use the full install. It's safer. I made a magisk'd boot of 11.2.10.10 if you need one after the full update.
Click to expand...
Click to collapse
Edit: problem solved.
​

aTorda said:
Edit: problem solved.
​
Click to expand...
Click to collapse
If needed here is 11.2.10.10 magisked boot:
https://drive.google.com/file/d/1It8uS5kfWXK0Imhu1vX66jUBEMUlxqAh/view?usp=drivesdk

Porquiplane said:
If needed here is 11.2.10.10 magisked boot:
https://drive.google.com/file/d/1It8uS5kfWXK0Imhu1vX66jUBEMUlxqAh/view?usp=drivesdk
Click to expand...
Click to collapse
Thank you! I was going to ask you for a copy cuz I ran into error trying to extract from payload, but I figured out where I gone wrong and fixed it. Still thank you for offering much appreciated.

@Porquiplane
I have the same problem trying to update and I also have Arter R2 Kernel and Magisk. Could you explain to me how I do to update. Now I get an error.

Partigiano0105 said:
@Porquiplane
I have the same problem trying to update and I also have Arter R2 Kernel and Magisk. Could you explain to me how I do to update. Now I get an error.
Click to expand...
Click to collapse
4th post...

TheKnux said:
4th post...
Click to expand...
Click to collapse
and if i uninstall magisk. How do I root the phone back? I'm sorry I don't understand much of this

Partigiano0105 said:
and if i uninstall magisk. How do I root the phone back? I'm sorry I don't understand much of this
Click to expand...
Click to collapse
Patch the stock boot image using Magisk then flash the magisk_patched.img through fastboot.