yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] V0latyle:
Try sideloading the OTA and see if that gets you running again.

If you follow my instructions, dirty flashing the factory zip won't wipe data or apps. However, since you are having trouble with the OTA, I wouldn't use the factory image quite yet - the system has detected a failure or mismatch with the OTA process, and reflashing the factory image won't correct the EIO issue. As far as I know no one has yet figured out how to manually reset the verity mode.

So, again, sideload the OTA for the update you attempted to install. Do not modify it or attempt root until it is running correctly. When it is, you should be able to extract the boot image from the matching factory zip, and patch that boot image to get root. I'd recommend against flashing with the factory image in this particular case because of the OTA error.
[Google Pixel 6 Pro] crypticc:
Full background might help:

1) I was travelling on plane and when I turned phone back on phone attempted to install the OTA and then failed.

(even though autoupdates disabled from Developer options I think it tried to install before I'd uninstalled Magisk. as I'd temporarily disabled developer options as an app was spotting it and deciding to not work as assuming developer options = root)

2) Phone booted but failed-back to the previous Slot A running 220305.

3) The slot B I am running now has the latest OTA and is rooted. Was achieved by sideloading the OTA after the previous attempt.

The issue was that Slot B was booting but with the EIO error etc.

4) My thought was that if I could return Slot A back to Stock I could then re-do the 220405 OTA that failed before from scratch. So I did flash_all with the -W removed applying to the

other

slot A.

5) Flashing slot A FW 220305 failed during that "product_a" step making that slot inoperable.

(phone failed back to slot B with 220305 albeit still booting with the EIO error and tamper warning, and additionally now with Slot A marked as non bootable)

I think my challenge/question now is if there's any way I can get SlotA back up and running using any means possible.

Then

I can try OTA again or something to get the EIO error removed. Should I try flash_all (without -w ) again?
[Google Pixel 6 Pro] crypticc:
Update / (fully) resolved :

Long story short up and running with no errors and both slots now active

Thanks for the suggestion to use the Canary. Clearly the issue and re-doing from scratch both seems to have fixed the earlier problems with EIO and getting the other Slot up and running.

I did :

Repair slot A

Updated Magisk to Canary 24306

Fastboot set_active other (switches from slot B that boots with errors to A that doesn't boot at all)

Fastboot reboot-bootloader (confirmed slot now the faulty slot A)

Extract 220405 FW and edit the flash-all.bat script to remove the -w

flash-all.bat

Booted phone (no errors, confirmed in android setting FW now 220405)

adb reboot-bootloader (confirm in bootloader that slot is still A)

fastboot getvar all (confirm in bootloader that slots A and B are both

not

marked as unbootable)

turned off phone (rebooted again as the red error only occurs from cold boot. No red EIO errors, just the orange warning that bootloader unlocked. so problem solved)

fastboot boot magisk_patched-24306_Dlmwt.img (the 220405 boot.img that I'd previously patched. This time I opted direct install instead of Fastboot flash)

No errors and root obtained

In Magisk, I selected install and direct-install to cement the root obtained by booting from the modified boot.img

Rebooting. No errors and root obtained

The phone now powers off, boots and reboots without the red EIO error. I do get the orange bootloader unlocked / tamper warning but that's fine of course.

I'm now going to repair slot B in the same way. (so both slots on FW 220405, but I think I'm going to leave slot B as unrooted)

Repair slot B

[update 2: - repairing slot B which booted okay albeit with errors using identical steps failed. The phone went to the Google text, but didn't make it to the "G" logo. then failed-back to slot A and Fastboot getvar all confirms that the previously working Slot B is now marked as unbootable. Slot A boots fine and still without the red error. Clearly more to be done to get both slots working)

[update 3: - tried repairing slot B again. This time it worked. The only thing that I did differently was that before doing flash_all, this time I did "Fastboot flash boot boot.img" (using the

unpatched

boot.img). and then after that doing flash_all worked and booted successfully)

Getvar all confirms both slots bootable
[Google Pixel 6 Pro] V0latyle:
Honestly I wouldn't worry about Slot B, unless you wanted to insert --slot=all into the factory script. If you were able to update and boot on Slot A with root, and intend to take the OTA in the future, then Slot B would be overwritten when the OTA unpacks and installs.

I don't use the OTA at all and just update using the factory image, but that's just me.

Can you please post the variable that shows whether a slot is bootable? I'd be interested in seeing if we could potentially use setvar to force the device to ignore EIO errors.
[Google Pixel 6 Pro] fil3s:
Anyone else randomly losing root on their p6pro? I thought it only happened to me on A13 but even on stable 12 , I just lost root. Fastboot booted the magisk image then direct installed. This has happened even when flashing the magisk image 😕

Edit. It happened frequently with canary on A13 and it just happened on stable 24.3
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hasn't happened to me at all, although I've been on stable Magisk for months and I've stayed on stable 12 - haven't tried any developer previews or betas.
[Google Pixel 6 Pro] fil3s:
I've attached a magisk log for reference in case there are others with the same problem or want to look into it. I can't see any errors 😕
[Google Pixel 6 Pro] crypticc:
1) This is the status when A wouldn't boot.

(bootloader) slot-successful:a:no

(bootloader) slot-successful:b:yes

(bootloader) slot-unbootable:a:yes

(bootloader) slot-unbootable:b:no

Then I flashed A, and that worked.

2) And then on the first attempt to re-flash B using the flash-all script which completed I got this.

(bootloader) slot-successful:a:yes

(bootloader) slot-successful:b:no

(bootloader) slot-unbootable:a:no

(bootloader) slot-unbootable:b:yes

The phone failed to boot and then failed-back to slot A.

3)

and then when I re-flashed B again

after

having first manually flashed Fastboot flash boot boot.img I got this

(bootloader) slot-successful:a:yes

(bootloader) slot-successful:b:yes

(bootloader) slot-unbootable:a:no

(bootloader) slot-unbootable:b:no

In case I missed anything here's steps 2 and 3 in spoiler below.

Spoiler content hidden.
[Google Pixel 6 Pro] crypticc:
Did u by any chance have two slots,? One rooted and one not? Asking only because fresh in my memory as I was attempting that.
[Google Pixel 6 Pro] fil3s:
No I just flashed to one slot, I didn't install to inactive slot.
[Google Pixel 6 Pro] crypticc:
Hi sorry for delay. Was travelling

Just seen your statement "stable 24.3"

Are u sure that when it booted that it actually booted the correct spot and not failing back? I used stable 24.3 initially and per above u can see it had issues with p6pro FW beyond March. It corrupted the partition for that slot making device fallback to the alternative slot. Canary 24306 however was okay for me.
[Google Pixel 6 Pro] fil3s:
No idea.. this was the 1st time it's happened to me on A12. Do you think I should use canary? Mind you, I should note the 'direct install' option was still available, but when I tried it it failed , can't remember the error.
[Google Pixel 6 Pro] crypticc:
See post above and I think there's a note a page or two back too. 24.3 doesn't work for the later April FW
[Google Pixel 6 Pro] V0latyle:
Correct, you should be using Canary 24306 if you want to update via out of band OTA.
[Google Pixel 6 Pro] Hand76:
Wanted to thank everyone here. Rooted easily about a week ago and so far so good.

Today I woke up to a notification that a system update failed to install. Which is fine and understandable. Im on April 12.1

But i have automatic system updates turned off in developer options and when I click system update (under setting) there is an option to resume.

How can I completly disable this? I don't want the phone to keep trying
[Google Pixel 6 Pro] roirraW "edor" ehT:
I've never gotten an update notification while having automatic system updates turned off in developer options. I don't think there's anything more you can do to try to keep automatic updates away than that option. The best and maybe only way to keep it from trying now that it's notifying you is to manually update to May's firmware.
[Google Pixel 6 Pro] metomsky:
Hello,

I'm stuck in a boot loop.

I managed to update to the march ota by "Update and Root Automatic OTA"

When April can out, I tried updating April the same way and it got stuck in a bootloop for 4 or 5 loops. then stuck on the google screen. after 20mins of waiting it out, I then forced rebooted it, that fixed it but I lost root.

that was a couple of weeks ago now.

today I tried to get root back by "fastboot flash master root.img"

now I'm just looping.

Yes, I now see that I didn't need to use "flash" as well as I should have just patched the May boot.img instead.

My number one enemy is me, I over thing things, then I mix my self up, and no phone.

I'm not sure what steps I should take, now that I cant figure out how to get the OS running

Any help is greatly appreciated,
[Google Pixel 6 Pro] Nergal di Cuthah:
If I'm not mistaken, you should not flash master root.img especially if following these directions and master root is an older boot. You should have, i believe, use fastboot boot master root.img and then direct install in magisk
[Google Pixel 6 Pro] Lughnasadh:
The reason you got stuck in a bootloop while updating to April via the "Install to Inactive Slot" method (sounds like this is what you were doing?) is that updating to April via that method required using Canary Magisk 24306+.

Confused if you are currently on the April or May build? You should patch the boot image to the corresponding month. If you can get into fastboot mode, flash either the correct patched boot image or the stock boot image. If you did flash the correct patched boot image, do you have any modules enabled? Some need updating when a new monthly build comes out and will cause a bootloop if you don't disable them.
[Google Pixel 6 Pro] metomsky:
I did not use the Canary Magisk 24306+,

I am on the April build.

I did have Modules installed. I didn't update them.

I do not have a patched version of may or April.

I just flashed the stock April boot.img and now I'm getting "your device is corrupt." I press the power button to start and it is stuck on the google screen.
[Google Pixel 6 Pro] Lughnasadh:
I think you may be best off to update to May via Android Flash Tool.
[Google Pixel 6 Pro] hello00:
Were you guys successful rooting the latest SQ1D.220205.004 build with Magisk? I had a bootloop
[Google Pixel 6 Pro] metomsky:
Android Flash Tool got me back into the OS. I patched the May boot.img then flashed it. I'm good and rooted.

thank you very much for the help
[Google Pixel 6 Pro] fil3s:
Use the flashtool

Android Flash Tool

flash.android.com

Edit: didn't see the replies. Disregard that
[Google Pixel 6 Pro] Sonoo:
Hi guys, has anyone experienced the magisk canary app not loading from install? Mine is stuck on the splash screen. I am currently completely stock with an unlocked bootloader on the May update. Downloaded the magisk canary from Github, installed it and stuck on the magisk app splash screen. Any help would be appreciated. Have already tried reinstalling apk and clearing storage/data of the app from app info.
[Google Pixel 6 Pro] Lughnasadh:
Install Canary 24306 and then update to 24307.
[Google Pixel 6 Pro] Sonoo:
Many thanks for the prompt reply. Tried it, 24306 installs fine. 24307 updates from within the app but again gets stuck on the splash screen. Is there any issue in using 24306 for May update root?
[Google Pixel 6 Pro] Sonoo:
Successfully rooted with 24306
[Google Pixel 6 Pro] Lughnasadh:
There shouldn't be. I was using it fine. However, 24308 was just released.
[Google Pixel 6 Pro] KHANrad_SIN:
Just updated to magisk canary 24308 (via patching the boot.img and flashing in bootloader) on the May security update and everything seems to be working fine for anyone wondering.
[Google Pixel 6 Pro] Nergal di Cuthah:
I had this issue, i switches to magisk beta, patched my boot so i was rooted on may then switch magisk to canary and update magisk and boot. Now magisk canary works
[Google Pixel 6 Pro] tgice:
Hi guys, I rooted my Pixel 6 back in January I think first, following the pretty thorough instructions at the beginning of this thread.

I've pretty much had to resort to OTA sideloading for each monthly security update since then though, despite trying the automatic OTA approach each time.

I'm currently using Magisk canary 24306 (I know there's another more recent one, but I don't think that's the answer for what's going on with my problems) and I just updated to the May update last night (again having to use OTA sideload).

The main reason I'm interested in getting the automatic OTA method to work is it just saves having to cable up to a PC and use adb, etc. Even though it'd probably actually take longer in the end (because the OTA install process (with "optimizing" step or whatever it says when it's scrolling through the long progress bar) takes a good 45-60 minutes for me), I still think I'd prefer being able to run it in the background without fussing with a PC.

So each time I've followed the steps in the original post here as closely as I can but I must be missing something because each time it fails in some way or another (most recently it does what I've heard others report, hangs on the Google screen indefinitely -- last time I let it sit for 1 hour+ [the phone was pretty warm when I got back to it], where I'm sure it shouldn't take more than a minute at that point).

So I'm wondering what preliminary steps you all take before running the automatic OTA, other than what's mentioned in those instructions.

Do you uninstall Magisk modules? I at least partially did that this time, but did not reboot after doing that.

Just wondering firstly if anyone is reliably getting automatic OTA updates to work, what Magisk version you're on, and what prep steps you take before doing the OTA.

Thanks!
[Google Pixel 6 Pro] android_dan:
Have magisk stable 24.3. Have updated the phone the last four time via OTA. Afterwards it took multible boots but would boot without root. Simply patched a boot image, flashed it, and all was good. This time I sideloaded a factory image, patched a boot image, and flashed it but... now it tries three or four boots and then goes to a "android is corrupt, wipe your phone". I get it back by booting to recovery and reloading the factory image, Anyone have any idea why I can't get root back? Thanks
[Google Pixel 6 Pro] roirraW "edor" ehT:
If nothing else will fix it, this should

Official Google Android Flash Tool

(OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
[Google Pixel 6 Pro] android_dan:
Thanks for the reply. Maybe 'm being dense but not sure how the flash tool is going to help. The problem isn't recovering from the bootloop. That's just a matter of flashing an unpatched boot image. The problem is what could be causing the patched file to bootloop the phone. I've updated this rooted phome 3 or 4 times now by flashing a patched boot file with no issues and have changed nothing on the phone
[Google Pixel 6 Pro] fil3s:
Sounds like you need to backup and wipe the phone, followed by flash with Android flashtool then fastboot flashing canary magisk boot image if you're getting the 'device is corrupt' message. I'd definitely use the flashtool. Make sure 'lock the bootloader' is unchecked
[Google Pixel 6 Pro] android_dan:
I'm not sure I need root that bad at this point. The phone is perfectly fine until I flash a patched boot image. Thanks
[Google Pixel 6 Pro] fil3s:
Have you tried live booting followed by a direct install? :) This way if it fails , android will just boot the stock boot image
[Google Pixel 6 Pro] roirraW "edor" ehT:
That's an excellent idea for @android_dan.

Edit/add-on:

I suggested the Official Google Android Flash Tool site because it has fixed things that manually flashing the factory image hasn't, in at least a dozen examples I've read about in this section alone in the six months the P6P has been out.

I know that it doesn't sound necessarily rational, but it's happened often enough and almost every time it's been suggested to someone to do that instead of manually flashing the factory image zip, that the online tool fixed their issue.
[Google Pixel 6 Pro] android_dan:
As I've never needed to do that step by step please. I'll give it a try. Thanks.
[Google Pixel 6 Pro] fil3s:
Ok so just fire up platform tools and reboot into bootloader

fastboot boot /path_to_boot.img

Sorry if you already knew this. It's 5:38am here, been awake all night. Hope this helped 🤗
[Google Pixel 6 Pro] android_dan:
Thank you for the help but no joy. The first phone I rooted was a Moto X 2nd gen, Many more since then, This has been one of the most stubborn issues I've ran into. No reason this shouldn't work, just doesn't. Also, I'm using magisk 24.3 and it doesn't have an uninstall option. ???
[Google Pixel 6 Pro] android_dan:
I'll try this next tomorrow. Thanks.
[Google Pixel 6 Pro] V0latyle:
While the Pixel devices follow AOSP's recommended boot flow and partition layout, not all manufacturers do, so if you're coming from another OEM to Google, never assume the same things will work the same way.

The Tensor platform seems to be especially troublesome. I highly recommend using Magisk Canary 24306 or newer; 24.3 Stable (24300) does not have some of the necessary fixes.

If you don't see an Uninstall option in Magisk, that means you don't have root. Please review the notes at the bottom of the OP.
[Google Pixel 6 Pro] android_dan:
Like I said, I've rooted this phone 3 or 4 times the flashed patched boot file method with stable magisk with no issues. This time, with no major alterations to the phone, it will not boot no matter what I try. That said someone else mentioned canary so I'll try that. I have however went back on my vow to not go the custom ROM route and installed EvolutionX so different set of conditions.

As to uninstalling magisk, I can't ever recall having the need to, so now I know.
[Google Pixel 6 Pro] android_dan:
Canary would not boot. On EvolutionX now. Downloaded stable and patched a file and got root and all is good.
[Google Pixel 6 Pro] V0latyle:
Magisk Canary 24309 is out with support for the Pixel 6 Android 13 beta.

Download
[Google Pixel 6 Pro] Lughnasadh:
May need verity and verification disabled. So far the only ones I've seen to successfully flash and root with 24309 on A13Beta2 are those of us that have those flags disabled.
[Google Pixel 6 Pro] chinghaqa:
┤Mod Edit├┤Adding automated English translation├

Sorry, I updated the OTA today. Open OTA RAR and find no boot.img. I lost ROOT after the update was done. How to ROOT Pixel 6 Pro?
[Google Pixel 6 Pro] V0latyle:
Read the OP. The boot.img is not in the OTA package; it is only in the factory image. Follow the instructions under Initial Root.

Additionally, please note that XDA is an English only forum.
[Google Pixel 6 Pro] Pekempy:
Confirm - mine failed until I disabled those flags (with a full wipe for good measure). After using the following, I can boot magisk_patched and have root with 24309

fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
[Google Pixel 6 Pro] V0latyle:
This is on the 13 beta, yes? Please be specific, this shouldn't be necessary on Android 12.
[Google Pixel 6 Pro] Lughnasadh:
Yes, on A13B2 when using the required Canary 24309 on Pixel 6 series. A13B1 and using pre-Canary 24309 does not require disabling verity and verification just to root.
[Google Pixel 6 Pro] Lughnasadh:
Just saw a report, the first I've seen so far, where a user successfully flashed Canary 24309 on A13B2 without having to disable verity and verification. All the other reports I've seen, which is a lot, users had to disable verity and verification. Take what you will from this... 🙃
[Google Pixel 6 Pro] acwcanada:
Can you tell where you saw such a report? I am watching this closely as I want to try the A13B2 but do not want wipe my data.
[Google Pixel 6 Pro] LLStarks:
One of the more annoying root experiences in recent memory. Had to wipe a few times. The threat of verity checks is not fun. Like remembering to protect your persist and reserve partitions on a OnePlus phone. Didn't disable verity though.
[Google Pixel 6 Pro] Lughnasadh:
Someone on Telegram in one of the Pixel 6 groups.
[Google Pixel 6 Pro] kleptonez:
I just tried a normal patch process using the canary 24309 downloaded today and it works without disabling anything. The changelog mentions support for A13B2 so it seems dev has fixed it! great work.

steps are as per usual: patch the original boot, bootloader patch boot magisk.img
[Google Pixel 6 Pro] acwcanada:
Did you ever disable verity when you were in A12/A12.1? My understanding is that you only need to do it once. Perhaps it is the reason why you are not facing similar problem as others are facing.
[Google Pixel 6 Pro] kleptonez:
I have never disabled them. Canary updated 18hrs ago has support for B2. Could have been fixed.
[Google Pixel 6 Pro] Lughnasadh:
https://twitter.com/i/web/status/1525034917670756353
[Google Pixel 6 Pro] Lughnasadh:
https://twitter.com/i/web/status/1525040362544254978
[Google Pixel 6 Pro] Lughnasadh:
https://twitter.com/i/web/status/1525077358893445121
[Google Pixel 6 Pro] chinghaqa:
sorry i didn't notice i sent in chinese

Is there a video you can refer to about this method you mentioned?
[Google Pixel 6 Pro] V0latyle:
I'm sure there may be videos available, however the instructions I provided are quite clear.
[Google Pixel 6 Pro] V0latyle:
Confirmed, Canary 24310 now available

Download
[Google Pixel 6 Pro] Phazed47:
Phone was rooted and running Magisk just fine but on old code.

Followed instructions in top post to update using OTA. On reboot, I got "Your device is corrupt It cant be trusted". Continued, which hung on the Google screen forever.

Power button for 30 seconds, rebooted, was back on old code but no longer rooted.

Followed instructions to sideload instead. On reboot, I got "Your device is corrupt It cant be trusted". Continued, which hung on the Google screen forever.

Powered off again, now I always get the "Corrupt" message. Continuing always brings up the Google screen and hangs forever.

Unplugged phone. Now it shows a battery symbol. Should be fairly well charged.

Could use some suggestions on how to proceed.
[Google Pixel 6 Pro] fil3s:
I had to sideload to get back into system when getting the 'corrupted' message. If you can get into fastboot , run this link with the device in fastboot mode. Uncheck the 'lock bootloader' and check 'force flash' and 'wipe device'

Android Flash Tool

flash.android.com
[Google Pixel 6 Pro] Phazed47:
My choices are

The "corrupt" screen. If I go past that I get

The warning screen with orange arrow "The bootloader is unlocked..." where I can pause with the power button. If I go past that I get

The Google logo on a black background than seems to hang forever
[Google Pixel 6 Pro] fil3s:
So in recovery mode you're typing 'adb sideload /path_to_ota.zip' is that correct?
[Google Pixel 6 Pro] Phazed47:
Yes, that is what I did. Followed by

adb reboot bootloader

fastboot flash boot /path_to_patched_master.root.img
[Google Pixel 6 Pro] Nergal di Cuthah:
Did you jump straight into bootloader or did you let the device start system and finish booting/updating
[Google Pixel 6 Pro] Phazed47:
The system updated.

Phone is sitting at fastboot mode right now
[Google Pixel 6 Pro] fil3s:
Android flashtool saves bricks, especially in fastboot. 😌