yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] V0latyle:
He might be talking about this one, although I'd like to point out that using this is kind of pointless on A/B devices. Here's why:

If the system fails to complete boot from the active slot for whatever reason, whether it be a kernel panic, an expected version mismatch, verity failure, etc - it will immediately call a reboot and switch to the inactive slot as a "failover" to attempt to self-recover. Depending on what caused the failure, the system may go into Rescue Party (corrupted data screen that looks like recovery, has Try Again or Factory Data Reset as options).

Bootloop savers are only really effective if the device is stuck in a closed loop, where it continues to try to boot over and over and over again. This rarely happens on the Pixel and other A/B devices, so the script doesn't have time to intervene before the system loads Rescue Party.
[Google Pixel 6] catseyenu:
Thank you, probably save me a couple of hours in research.
[Google Pixel 6] pbsavages:
This might seem silly. I was under the impression that the March update was Android 12.1. I was rooted with magisk on Feb update on my Pixel 6. Had a hard time upgrading to March update. Wouldn't take the factory image update in fastboot. I installed previous magisk canary as suggested with a new patched boot image. Factory image fastboot update still didn't work. Auto OTA failed each time. Finally, side loading the march OTA from stock recovery updated, and magisk 24301 patched boot image flashed. Currently on sp2a.220305.013.A3 and Android 12 my system settings show but Google lists that build as Android 12.1 on their factory images and ota download pages.. Is it supposed to show as Android 12.1 or no? Am I overthinking it? Never been to 12.1 before..
[Google Pixel 6] V0latyle:
Yeah, SQ1A is 12.0, SP2A is 12.1

What error were you getting?

It's a bit confusing given Android history, but I think for the most part they've been sticking to major versions depending on significant changes such as API version. 8.0 on API 26 was distinct from 8.1 on API 27 but didn't incorporate enough significant changes to amount to a full new version. In the same way, 12L is basically still 12, just for larger screens, and 12.1 is the same as 12.0 with an ostensibly newer API. 13 on the other hand is a full new release.
[Google Pixel 6] Lughnasadh:
March is 12.1 (12L is their marketing name for it). They are calling it 12 in the system settings, presumably just to show the "overall" OS version number).
[Google Pixel 6] pbsavages:
I was able to flash the new bootloader and radio from 305 which was confirmed, but when I fastboot update blah.zip it said something like unable to find boot partition or something. The Auto-update would download but fail at 95% with the only message "installation failed". Not sure why the factory image didn't flash. I failed successfully I suppose as this is my first device without an SD card yet I'm rooted without ever having wiped this device on accident.. recovery update from SD card would have been much easier..
[Google Pixel 6] V0latyle:
Your Platform Tools is out of date. Current is 33.0.0
[Google Pixel 6] tom1807:
Small correction, the latest is 33.0.1 and seems necessary for A12.1

Cheers

Tom
[Google Pixel 6] badabing2003:
I did mine with Version 33.0.0-8141338 and had no issues.
[Google Pixel 6] Toronadian:
Just so I'm understanding it right, make sure the following before updating to March:

- disable all Magisk modules (including system less hosts

- use Magisk Canary 24301, not the latest Canary

- use stock kernel (haven't changed it personally)

Anything else I'm missing? I've been sideloading the OTA, then after the phone boots up, I flash the patched boot image from Magisk. Have been doing it this way with this phone.

Older pixels I use to do the flash.bat file with the "-w" taken out. With the issues earlier on with vbmeta, I switched to sideload OTA method, even after the vbmeta issue got fixed.
[Google Pixel 6] V0latyle:
I personally haven't had any issues even though I don't disable modules. YMMV because it depends on the module - I know for a fact that Systemless Hosts, Universal SafetyNet Fix, and MagiskHide Props Config shouldn't be a problem. That being said, better safe than sorry.

Or just use Stable 24.3. I can't speak to the latest Canary because I was on 24201 when I updated to March on my Pixel 5

Yep, a lot of the issues have been related to a custom kernel

I personally would recommend you continue to dirty flash the factory image, because the OTA is another common denominator for folks with bootloop issues. You may even consider adding the --slot=all argument to the fastboot update line.
[Google Pixel 6] Koehlix:
I used the latest canary, did not disable any modules (Viper, systemless hosts, universal saftynet fix, MagiskHide props, bootloop protector).

Downloaded the factory image, did a new boot.img and flashed with the "remove -w"- method (flash all.bat).

Did a reboot, back to bootloader, flashed the new boot.img and done.

Everything works fine for me.
[Google Pixel 6] Toronadian:
Thanks for the input both of you. Is it the same with the Pixel 5 as well? Need to update my wife's phone as well and back at the beginning of the month I was reading some issues Pixel 5 users were having with the March update.
[Google Pixel 6] Jeryhho:
After OTA and installing to inactive slot in magisk my pixel 6 boot into fastboot mode instead of normal boot how can I fix this without losing data?

EDIT:

Ok I am flashing with unchecked boxes
[Google Pixel 6] RashidAlawadi:
So on my Pixel 6 the "install to inactive slot" is missing in Magisk. It seems it was causing bootloop issues according to John Wu.

Is there any other way to take the OTA and keep root?
[Google Pixel 6] capntrips:
Do you mean this 1.5 year old tweet linked from the OTA guide? The issue referenced there was fixed with an updated bootctl and that link is pending removal.

That being said, people have been having issues with taking the March OTA, especially on the latest canary builds.

What version of Magisk are you running? If you aren't seeing the option to install to the inactive slot, is option to direct install also missing?

In any case, when I'm stuck, I personally use the flash tool, as it has yet to fail for me. The flash-all and sideload methods are hit and miss, in my experience. See "Update and Root using the Android Flash Tool" in the OP for instructions.
[Google Pixel 6] RashidAlawadi:
I'm running latest Magisk 23016. Direct install is available (I think I tried it a couple of months back to see if I will retain root but wasn't successful).

I have no issue with updating by extracting boot.img and patching it method, but I just wanted a more convenient way of updating.
[Google Pixel 6] capntrips:
Magisk 23016 was released in early December. Installation to the inactive slot wasn't enabled for Pixel devices until 23017. The latest release is 24304, though people have had issues (myself included) taking the March OTA with it. I've seen others recommending 24301, but I don't have any personal experience using it to take the March OTA.
[Google Pixel 6] RashidAlawadi:
Oh I see. I guess mine is not up to date. I will update to latest Magisk and try again next month since I already got the March OTA. Hopefully it won't have those issues.

Thanks a lot!
[Google Pixel 6] kornball:
I was able to successfully update to the March factory image using Magisk 24304. I did not disable USNF 2.2.0 or Systemless hosts.

Prior to flashing everything in fastboot, I patched the boot.img in Magisk and transferred patched_boot.img back to my computer.

Entered fastboot mode, flashed bootloader, rebooted bootloader, flashed radio, rebooted bootloader, flashed update.zip with --skip-reboot flag, then flashed patched_boot.img.

Let phone boot, and I have both root and passed safety net.
[Google Pixel 6] Hung0702:
I had a similar experience, though different install method.

I just download the factory image and remove the wipe flag from the flash-all batch/shell file. Then I unzipped the image_xxx.zip to grab the boot.img. I used Magisk 24304 to patch, then put that magiskboot.img on my PC. I removed my Tulsadiver mods (highly recommended, btw!), rebooted to confirm removal, and then reboot once more into fastboot to flash-all.bat

After flashing, my bootloader and radio were updated to March. I booted once and finish system update, then reboot to fastboot to flash the magisk boot.img. Everything up and running as usual.
[Google Pixel 6] go_roy:
So I didn't read this thread of course, tried updating to March with Magisk 24304 patched boot image using the OTA sideload, and didn't disable anything Magisk related beforehand. Didn't work, so I tried flashing the factory image. I'm now at a point where regardless of what slot I use, booting from a Magisk patched root (doesn't matter the version, I tried 24304, 24301 and 24102) shows the Google loading logo for a few seconds and then reboots into what I assume is the normal boot image, then boots into Android without root.

I even tried re-installing Manager in this state (24301 and 24304) and patching a clean boot.img, booting into it still doesn't work.

Do I have to factory reset now for root again? Not really sure what went wrong, though I'm still scared from the vbmeta stuff from earlier versions.
[Google Pixel 6] rbouza1:
I had same issue. Had to wipe data. Tried every version of magisk , different combos of boot imgs. Had modules disabled and everything. Don't know what happened but I wiped thru android flash tool and setup my phone. Now rooted with everything good.
[Google Pixel 6] kariem112:
yep, same here. Got out of the bootloop by flashing the unpatched current version of boot.img, but I am reluctant to try to root again.....
[Google Pixel 6] rbouza1:
Something weird happened with canary magisk. I'm ok with resetting my phone here and there .
[Google Pixel 6] badabing2003:
Before resetting your phone are you willing to try few things so that we can figure out the root cause of this issue.

FYI I used the canary magisk and did not have any issues, it looks like it is the combination of canary magisk and most likely the magisk modules you had enabled prior to the update.

Do you recall which magisk modules you had enabled?

Anything to do with audio?
[Google Pixel 6] kariem112:
In my case, no magisk modules where installed, except the systemless host for ad-away.
[Google Pixel 6] badabing2003:
So you were on Magisk Canary 24304 right? (3dc7d77e) and your update channel was set to canary right?

You only had systemless host, and you did dirty flashing?

What is your current state?
[Google Pixel 6] rbouza1:
I would've , I had systemless, right clock, magiskprop, and safety net fix modules with canary magisk. Oh and I did have viper audio !
[Google Pixel 6] badabing2003:
In Magisk General thread, people reported that they experienced this issue with Viper Audio and other audio modules.

Did you had to wipe to recover or managed to recover?

Would dirty flashing both slots have helped?
[Google Pixel 6] rbouza1:
I did everything at first . After several days i said f it and wiped via flash tool. Im good now same modules minus viper
[Google Pixel 6] kariem112:
No, i think I was on 24.3... I can check with the version you suggest. Do I get the boot.img from the current build installed on the phone? (factory image, extract, move to phone, let Magisk patch it, then flash with fastboot?)
[Google Pixel 6] badabing2003:
Assuming that you are already on the March release, yes get the boot.img from the current build and patch it with Magisk Canary version that I specified.
[Google Pixel 6] kariem112:
Tried, got a bootloop again. Double checked the magisk version, it is the one you suggested. used this command:

fastboot flash boot magisk_patched.img .... after boot loop, flashed the original boot.img and it was back online.
[Google Pixel 6] badabing2003:
Thanks for trying

Can you try dirty flashing to both slots?
[Google Pixel 6] kariem112:
sure, how would I do that?
[Google Pixel 6] badabing2003:
modify the flash.all script update line to this

fastboot.exe --slot all update image-marlin-qp1a.191005.007.a3.zip
[Google Pixel 6] kariem112:
Will do. And after that, try magisk again?
[Google Pixel 6] badabing2003:
yes please
[Google Pixel 6] mustardseeds:
This time I could flash the update OK

adb sideload ota.zip

Then

adb reboot bootloader
fastboot boot 'master root.img'

I saw no errors and everything works OK but there is no root. Now how can I get root back?
[Google Pixel 6] Lughnasadh:
1. There is a space between master and root. Unless that's a typo, remove the space.

2. Fastboot boot is only temporary and root will be removed on the next reboot. Need to do fastboot flash .... for permanent root.
[Google Pixel 6] mustardseeds:
Where is 'master root.img' supposed to come from exactly?
[Google Pixel 6] airtower:
The patched boot image from the version you are running
[Google Pixel 6] tom1807:
Happened again after the April update, that I had a bootloop to fastboot after "flashing to inactive slot". Wonder now, whether the modules "Universal SafetyNet Fix" and "MagiskHide Props Config" should be also removed before update, not only "Restore Images", despite stating in the pop-up "All modules will be disabled/removed".

Cheers

Tom
[Google Pixel 6] capntrips:
I did a complete wipe and took the April OTA with zero modules, and I still bootlooped with 24.3 stable. As with 24304 on the March update, I got the red eio screen with 24305 this month. I opened an issue on the Magisk Github.
[Google Pixel 6] Lughnasadh:
Am I understanding correctly that after you did a complete wipe and took the April OTA with zero modules using 24.3 Stable that you did not get the red eio corruption message even though it still bootlooped? And that you got the corruption message only when using Canary 24304/5?
[Google Pixel 6] capntrips:
Correct. To clarify, this was only on reboot after taking the OTA. After using the flash tool to install the April build, 24305 worked fine.
[Google Pixel 6] Lughnasadh:
Thanks for that.

Hypothetically speaking, and disregarding there is likely a problem with Canary 24304/5 as they relate to OTAs, do you think you would have still gotten the red eio corruption message if you had verity and verification disabled, even though you would have still likely bootlooped in those situations? In other words, do you think disabling verity and verification may have prevented getting the corruption message, although not necessarily prevented the bootloop itself?
[Google Pixel 6] Koehlix:
Latest Magisk, factory image flashed with "-w", new boot.img, based on latest image - no problem
[Google Pixel 6] devilsshadow:
So is it safe to update to the april security patch using this method? Using magisk 24.3 stable, with Zygisk. Have systemless hosts and universal safetynet fix modules installed.

Before you download the OTA, open Magisk, tap Uninstall, then Restore Images.

Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update

Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.

You should now be updated with root.
[Google Pixel 6] capntrips:
I have seen 3 reports of failure (including my own) and none of success using that method. You can try it. Worst case you'll have to use one of the other methods to recover. You'd have to use one of those methods to perform the upgrade, anyway.
[Google Pixel 6] Strephon Alkhalikoi:
I'm the fourth report of failure. For the second update in a row I had to flash the factory image, boot, then go through the steps to create and flash a modded boot image.
[Google Pixel 6] manjaroid:
I wonder about Magisk's module removal process too, although my glitches haven't gotten big yet. Normally I disable them and do a complete uninstall of Magisk before attempting OTA updates. But lately it seems something about the restored boot.img is preventing updates over the internet. The last two OTAs gave me "Can't update/Installation problem" but sideloading works out fine, and no problems after rooting again.
[Google Pixel 6] android_dan:
I'm the fifth. Took about 4-5 tries to get the phone to boot and lost root. That's three times I've used this method with success the first try and now two fails. Last time I attributed it to being such a large update but I guess not.
[Google Pixel 6] stankyou:
I had no success with this method. I always end up with adb commands to fix what this method 'broke'. I assumed it was just me not following the guide properly but it looks like I'm not alone then.

For May update, I'll probably wouldn't bother with this and go the adb route because that guide was on point.
[Google Pixel 6] Ictcreations:
Hi guys.

Soooo i've been very familiar with root in the past and have no problem whatsoever doing it again. infact im deffo wanting to do it. I just wish i had unlocked bootloader straight out of the box.

I am now in the difficult position in that to unlock the bootload it will wipe my device, which i dont want to do because i have things setup and installed exactly how i want them.. Is there any way first of all to either A) unlock the bootloader without a wipe or B:) take an actual backup of my phone in its current state that i can restore after. A bit like you can do with twrp.

I would rather not go through googles in house backup because its temperemental at best, and certainly wouldn't restore things just how they are now for me.

Any help would be greatly appreciated :)
[Google Pixel 6] phaino00:
You can't unlock bootloader without wiping data unfortunately. Concerning nandroid backups or something like it, there are some tools that others have used, but I can't recall which tool would work best for your situation. Hopefully, some others can share what they use.
[Google Pixel 6] Hooya:
I have yet to get the "after OTA" Magisk to work. Always boot loops.

This April update I can't even get root back at all. I installed (without wipe) the April images, and had Magisk patch the file. However the resulting patched file does not allow my device to boot at all. Gives me various corruption errors upon attempting to boot, and I have to re-flash the unpatched boot.img to get back into a working phone. No root access at all.

Anyone else having this issue?

I have the latest updated Magisk program on Canary (24305)
[Google Pixel 6] android_dan:
Mine finally booked after about 3 or 4 attempts with no root and the update failed. Retried the update and it booted with no issues. Downloaded the OTA, extracted the book image, patched it, flashed it and all is well. Sideloading from now on.
[Google Pixel 6] Hooya:
This is what isn't working for me. I have the OTA, extracted the boot image, patched in Magisk, flashed, no boot from patched boot image.

Might try a different update branch of Magisk.
[Google Pixel 6] tom1807:
I am not sure whether this could be cause, but after I had "Missing 5GB space after April update" I tried to set the active slot from slot_a to slot_b and tried to boot from there. Was just curious whether my missing space would be also there when I boot from slot_b.

To my surprise, I can't boot at all from slot_b. After 3 times booting, the Pixel went back to slot_a and booted fine.

Back to fastboot, command "fastboot getvar all" I had the following output:

I wonder now, whether this could be the root cause that the OTA updates fail after patching the boot image with Magisk to the inactive slot.

Also wonder now, whether flashing the original boot image to slot_b would fix that.

Cheers

Tom
[Google Pixel 6] Hooya:
The flash-all.bat file already flashes to both A and B, so for anyone that has used that (me included) we wouldn't have that problem, and I have always had it.
[Google Pixel 6] airtower:
no it doesn't, unless it's modified by the user to do so
[Google Pixel 6] tom1807:
I never did, before the March update, just did the OTA update, flashed Magisk to the inactive slot and rebooted. Since March update, this doesn't work anymore.

Cheers

Tom
[Google Pixel 6] badabing2003:
I second what @airtower said, unless you modified the file, it does not flash to both slots.
[Google Pixel 6] Hooya:
Sorry, I was going by the script posted in the OP of this thread, which definitely has "slot all" in it. Didn't realize that's not what is actually in the flash-all.bat file, even though the post says it should.

fastboot update bootloader <bootloader image name>

fastboot reboot bootloader

ping -n 5 127.0.0.1 > nul

fastboot update radio <radio image name>

fastboot reboot bootloader

ping -n 5 127.0.0.1 > nul

fastboot update --skip-reboot --slot=all <image-device-buildnumber.zip>

Also, I just realized I'm an idiot and have been patching an old boot.img file that was in a different directory than I thought I was in while finding the file in Magisk. I have things working now. OMG.....
[Google Pixel 6] capntrips:
Magisk 24306 (release notes) is now available on the canary channel, and I can confirm that the installation to the inactive slot OTA method is working for the April update.
[Google Pixel 6] V0latyle:
When updating via the factory image, I recommend flashing to both slots just in case something happens and the device decides to reboot to the other slot. This is not required, you don't have to mess with slots at all, this is just the way I do it.

You can use the Report button on your own post to request moderator action. I would do it for you, but Forum Specific Moderators such as myself only have permissions in certain forums.
[Google Pixel 6] Lughnasadh:
I'm curious if you (and others who ran into this problem) had to clean flash the factory image to remove the corrupt message or of if a dirty flash (removing the -w from the flash-all.bat update script if using that method) sufficed.
[Google Pixel 6] TheTabbingMan:
Dirty flash worked for me.
[Google Pixel 6] Lughnasadh:
Great. Thanks. That's all I needed to know.

Was curious because in the past when people ran into the corrupt message (for a variety of reasons), a clean flash was sometimes required to get rid of the message. Good to know a clean flash isn't required for this specific issue (April update via "Install to Inactive Slot", which I know was fixed with Canary 24306). 👍
[Google Pixel 6] devilsshadow:
Does this mean this method now works with Magisk Canary?

And if it does, will I have to disable all scripts before using it?
[Google Pixel 6] capntrips:
Yes.

There's no universal answer, unfortunately. With safetynet-fix and systemless hosts, I've never had an issue. I have seen several people mention issues with audio modules. If you want to be conservative, disable them all. If you're willing to put in the work to fix it if something goes wrong, leave them enabled.
[Google Pixel 6] devilsshadow:
Thanks! I only have safetynet fix and systemless as well so I'm good. Cheers!
[Google Pixel 6] Strephon Alkhalikoi:
Dirty flash with the -w flag removed was sufficient as I never got a corruption notice, just a bootloop.
[Google Pixel 6] Rebel7022:
what version of magisk should I use to root my 6, all I can find is 243 that can't out in March thanks
[Google Pixel 6] capntrips:
You can get the latest canary build by clicking the canary button on the Magisk GitHub readme page.
[Google Pixel 6] Rebel7022:
I'm not using 12.1

I'm using the stable build, which version should I get of magisk . thanks
[Google Pixel 6] badabing2003:
like @capntrips I also use the Canary version of Magisk, latest is 24306, which actually came out after I flashed mine with Magisk 24305.

Use the latest.
[Google Pixel 6] V0latyle:
The post you responded to answered your question. Use the latest Canary.
[Google Pixel 6] airtower:
Any idea what they changed? I didn't see anything seemingly relevant in the delta to 24.3 changelog.
[Google Pixel 6] capntrips:
The improvements to sepolicy hijack was the change that fixed it.
[Google Pixel 6] V0latyle:
The changelog for stable/beta will not reflect changes in Canary.

Commits to 24306
[Google Pixel 6] Mason_lee:
thank you for this update and information.