Develop Bugs

Couldn't install system update

I am unlocked and was rooted with Magisk and the OTA OPM1.171019.013 tried to install and failed. I uninstalled Magisk thinking it might resolve the problem. It didn't. I have OPM1.171019.011 and would really like the update and reinstall Magisk to be rooted. Is there a way to get this update to install?

ranlil said:
I am unlocked and was rooted with Magisk and the OTA OPM1.171019.013 tried to install and failed. I uninstalled Magisk thinking it might resolve the problem. It didn't. I have OPM1.171019.011 and would really like the update and reinstall Magisk to be rooted. Is there a way to get this update to install?
Click to expand...
Click to collapse
Look over this thread for problems with OTA's and rooting :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

I've got the same issue. it said failed a few days ago, now it just stays on step 1 of 2. read duce's thread but it's about his script, is there any way to get the ota to take?

kellybrf said:
I've got the same issue. it said failed a few days ago, now it just stays on step 1 of 2. read duce's thread but it's about his script, is there any way to get the ota to take?
Click to expand...
Click to collapse
Were your rooted or had custom recovery before you started?

Badger50 said:
Were your rooted or had custom recovery before you started?
Click to expand...
Click to collapse
rooted, twrp, magisk

kellybrf said:
rooted, twrp, magisk
Click to expand...
Click to collapse
Then that's why you can't take the ota. Need to be unrooted and on stock recovery for OTA's.

Badger50 said:
Look over this thread for problems with OTA's and rooting :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Thanks!! Worked as described.

Badger50 said:
Look over this thread for problems with OTA's and rooting :good:
Click to expand...
Click to collapse
I had a look over there, and it looked a bit scary. I don't want to do the critical unlock. (I still have the stock bootloader) Instead I found another way that involved patching a factory image.
My steps where:
Download the latest factory image
Checked the SHA256, then unpacked the zip
Extracted the boot.img file from the image-taimen-<version>.zip
Copied the boot.img onto my device (adb push or drag and drop)
Used Magisk to patch it. (Install button, then "patch boot image file") (NB: The patched boot image is about half the size of the original. This is normal)
Copied the patched_boot.img back to my PC, and renamed it back to boot.img
Put the patched boot.img back into the image-taimen-<version>.zip replacing the original
Once I had modified system image, I then flashed my device in the usual way using flash-all.sh (NB: You need to remove the -w switch from the last fastboot command so that it does not wipe the user data).
The end result is that my phone is updated to the latest November firmware, and I still have root with Magisk.
Next month, I will try again with an OTA, but if that does not work, then the above process should be easy and reliable.

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.

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!

Question {CLOSED} March update

Just got the march security update. 490mb.

Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.

swieder711 said:
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
Click to expand...
Click to collapse
My phone went into bootloop today after updating Magisk (magisk update prompt), BEFORE march update. That was a bit odd. Maybe your bootloop has nothing to do with March update, but with the new magisk version being flashed is incompatible to certain modules.

Well hell, I am failing.....and understand the message, but dont understand why or what transpired....and not sure what bootloader the message refers to.....this is a factory flash....
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'slider-1.0-8062051'.
Update requires 'slider-1.1-8118264'.
fastboot: error: requirements not met!

Hmm, now not exactly sure what to do....8062051 is the bootloader from the 2nd February image, so not sure where to get 8118264 so I can update.......very odd.
***EDIT: OK I see thats the bootloader from A12L not from A12.......wtf!!!!
****RE-EDIT: PEBCAK here on my end.....doh! Working now

Same here, just checked and it showed up.

I was running into issues flashing the Factory image via Fastboot so I decided to try the FLASH method from the Android Flash Tool. That worked. But when I try to install the Magisk patch file, it fails and then I get stuck in a bootloop. So there you have it. I'm going to have to deal with no root until someone figures out what's going on.

swieder711 said:
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
Click to expand...
Click to collapse
Once I disabled the Typhus ROM Control module in Magisk then my phone booted with root enabled with 24.304. Magisk stable probably works too.

TimFlex said:
Just got the march security update. 490mb.
Click to expand...
Click to collapse
This in more in line with the following thread which is where you need to bring this discussion. We really don't need another misleading thread that is merely a Magisc "how do I...?"
April 10, 2023 TQ2A.230405.003.E1 Global - Root Pixel 6 Pro [Raven] / all relevant links
Pixel 6 Pro [Raven] March 9, 2023 I recommend sticking with 33.0.3. Note that two users in my Pixel 7 Pro thread have said that 34.0.1 did not work correctly for them. Someone reported it to Google (added a comment about 34.0.1 to the existing...
forum.xda-developers.com

Same issue here. Flashed March factory image. No wipe flag. Flashed Magisk patched file. Stuck in bootloop.
Reflashed factory image and didn't flash boot image and I can boot up. I guess no root until this is fixed.

I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to Platform TooIs Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. Now on March build with no data loss I then fastboot flashed the patched boot.img and have root
I had the same problem with Feb v2 OTA sideload (Maybe because I had a custom kernel?) anyway, I think the Android Flash Tool will be my go to for future updates

jcp2 said:
I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to Platform TooIs Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. Now on March build with no data loss I then fastboot flashed the patched boot.img and have root
I had the same problem with Feb v2 OTA sideload (Maybe because I had a custom kernel?) anyway, I think the Android Flash Tool will be my go to for future updates
Click to expand...
Click to collapse
Can you upload your patched file by any chance?

tonyfiore75 said:
Can you upload your patched file by any chance?
Click to expand...
Click to collapse
This is for Magisk Stable - Not Canary!!

Thesis so much @jcp2 !

Does the uninstall Magisk, OTA, and then reinstall Magisk work with this update? If so, what version of Magisk do we know that works?
Last time I lost everything on my phone. Not trying to do that again.

mkhcb said:
Does the uninstall Magisk, OTA, and then reinstall Magisk work with this update? If so, what version of Magisk do we know that works?
Last time I lost everything on my phone. Not trying to do that again.
Click to expand...
Click to collapse
Edit>>>> As long as you're on stock kernel, Canary is fine.

jcp2 said:
IDK but 100% sure to stay on Magisk Stable and not Canary --- Canary will cause bootloops!
Click to expand...
Click to collapse
I rolled back to Stable and still cannot gain back root....

I sideloaded the March OTA then rooted successfully with 24.3, but I didn't do the magisk uninstall.

jcp2 said:
IDK but 100% sure to stay on Magisk Stable and not Canary --- Canary will cause bootloops!
Click to expand...
Click to collapse
Not accurate. Using latest Canary (24304) and updated fine. Sideloaded ota in recovery, reboot to let system update complete, reboot to bootloader and flashed patched boot.img. All is fine.

did you try the patched boot.img I uploaded a few posts back? Make sure you're on March update with Magisk 24.3 stable before flashing.