yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Lughnasadh:
That message often means:

1. You are not patching the correct boot image, or

2. You are not flashing the correct patched boot image, or

3. Something went wrong when patching the boot image. Make sure it is around 64 MB in size.

Of course, also make sure you are using the latest Platform Tools.
[Google Pixel 6 Pro] aButterKnif3:
Thank you for the detailed guide. I'm brand new to rooting (first time) So I'm not sure, for the update sections, are those options? Like I can update by auto OTA or by sideloading? Currently trying to do the auto OTA, but the security update keeps failing to install. So I'm hoping the sideloading is another option. Thank you!
[Google Pixel 6 Pro] Nergal di Cuthah:
Yes each different method is stand alone :)
[Google Pixel 6 Pro] aButterKnif3:
Thank you! Having a second issue now, After rooting seemingly successfully the manager keeps staying Magisk is not installed after rebooting. Not a clue what could be the issue.
[Google Pixel 6 Pro] Nergal di Cuthah:
Did you direct install after booting the master root? Or did you reboot without? (or neither cause like me you use fresh boot from factory each time i sideload)
[Google Pixel 6 Pro] V0latyle:
Did you have the Magisk app hidden before you started? Are you flashing the patched image?
[Google Pixel 6 Pro] rafapadilla93:
Hello,

First of all, thanks for this guide to root Google Pixel 6 pro, It has been very helpful.

I have a problem, I have got root and I pass SafetyNet correctly but Google Play marks the device as "not certified". With this "device not certified", I can't find several applications, netflix for example (this is not the most important thing), but the most important for me is that Google Pay doesn't work. I can't add my cards.

I have DenyList options enabled and I have added Google play, Google Pay, Google play Services (and more) to the list. I have also cleared the Google Play and Google Play Services cache.

After all this, it keeps telling me that it's not certified.

Does anyone know what else I can do?

I'm going to try rooting with the April update and see if that fixes it or not....

Thank you! (Sorry for my English).
[Google Pixel 6 Pro] phaino00:
Clear both storage and cache in play store app. This has helped me in the past.
[Google Pixel 6 Pro] sandman255:
some thing is strange here. I have the 6 pro, (raven) but the the fastboot screen (on the phone) says ProductRevision : oriole. Help??
[Google Pixel 6 Pro] roirraW "edor" ehT:
Did you somehow flash the wrong firmware? Does it boot and you can get into Android? If you go to Settings, does "About phone" say "Pixel 6 Pro" or just "Pixel 6"?

I would be tempted to download the full firmware image (this is the one you want). You can try it after removing the -w so it doesn't wipe, although if you had flashed the wrong firmware before, then I have no idea if you can expect it to work without wiping.

Edit: I've confirmed mine says what it should on the April firmware for Product revision: raven MP1.0
[Google Pixel 6 Pro] heij20032003:
I am using Magisk Stable 24.3 and done all the steps for "Update and Root Automatic OTA".

However, after reboot, the system is not updated and the button in "Settings > System > System Update > Check for Update" is still "Restart Now" .

What should I do to complete the OTA update?

Does it matter if I hide the Magisk app?
[Google Pixel 6 Pro] V0latyle:
I would recommend against hiding the Magisk app unless you specifically need to.

If you performed Install to Inactive Slot in Magisk, which reboots the device to the alternate slot, it should boot into updated system with root. If you get a single bootloop, this means that the update failed and the system has reverted back to the original slot.

You can try either sideloading the OTA, or dirty flashing the factory image.
[Google Pixel 6 Pro] heij20032003:
I have sideloaded it and updated to April update...thanks

Shall I use the 'master boot.img' that i created for my fist root done in March?

or should I make another boot.img?? if yes, how should I make it?
[Google Pixel 6 Pro] V0latyle:
Don't flash the old boot image. You can temporarily boot it for temporary root, then use Direct Install in Magisk. Otherwise, you can just make a new patched image the same way you made the March one.
[Google Pixel 6 Pro] Lughnasadh:
PSA: Would suggest not to use the "Install to Inactive Slot" method to update to the April build, even if on Stable Magisk. People are having problems using this method for the April build. Issue tracker and possible PR fix in the works below...

OTA triggers red `eio` screen then bootloops on Pixel 6 · Issue #5685 · topjohnwu/Magisk

Device: Pixel 6 Android version: 12.1 Magisk version name: 704f915 Magisk version code: 24305 The red eio screen issue has existed since the March update on 24304. While falling back to 24301 worke...

github.com

New way to mock sepolicy: by controlling seclic by yujincheng08 · Pull Request #5690 · topjohnwu/Magisk

Fix #5685

github.com
[Google Pixel 6 Pro] Radon7:
will I lose some functionality when I root my pixel?
[Google Pixel 6 Pro] sandman255:
I don't think so..... I followed the instructions up to flashing the patched MAGISK file. Then it went into a boot loop. Since I still had (and even now do) fastboot available I decided to flash it back to stock, using the flash-all.bat. But I noticed at the end it complained that a couple of files could not be found. That leads me to where I am now. Thanks. I will try another stock flash using the file your message points to. BTW, the attached screen shots are the "log" of the flashing operations : Upper Left -- Page 1.

Upper Right - Page 2 etc
[Google Pixel 6 Pro] roirraW "edor" ehT:
No, unless you count the ability to rely on taking an OTA update. There is a way to, but sometimes it doesn't work, and IMHO, it's not worth the trouble. I just always update using the full firmware zip, modified to note wipe, then I manually re-root.

Very strange. I also suggest:

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)

It has fixed some things that everything including the full firmware zip haven't fixed for at least a dozen users over the last five months.
[Google Pixel 6 Pro] abdane:
Last time I rooted my phone, I had to factory reset, how can I prevent factory reset when rooting? I have the patched boot.img ready but I don't want to lose all my data.
[Google Pixel 6 Pro] roirraW "edor" ehT:
You only have to endure a full wipe of the phone when you unlock the bootloader (or re-lock it). This is necessary and unavoidable.

Rooting, itself, does not wipe your phone.
[Google Pixel 6 Pro] abdane:
Yes I know, but when I first rooted my phone, I got stuck in a bootloop and phone asked to do a factory reset, which I did to fix it, then I booted rooted just fine. But now I updated to the April firmware and lost root, want to root again, would like tips to avoid another bootloop and factory reset
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hopefully you already had all Magisk modules disabled before you updated. If you didn't, it's possible once you re-apply a rooted kernel that the phone will bootloop, but it shouldn't require a factory reset to fix, just safe mode.

That all said, I always try to be prepared for a full wipe in case I do something wrong or I just experience a hiccup.
[Google Pixel 6 Pro] abdane:
I uninstalled magisk before updating to the April firmware... Will try to root it now, hopefully nothing goes wrong
[Google Pixel 6 Pro] heij20032003:
does it mean that what I need to do is to do all the steps in "Initial Root / Create Master Root Image" once again?

thanks a lot for all the replies.
[Google Pixel 6 Pro] V0latyle:
No, just patch the new boot image and flash it.

This really isn't that complicated. If it seems to be, you're probably overthinking it.
[Google Pixel 6 Pro] sandman255:
Well I feel pretty stupid.... but my device is NOT a 6 PRO but just a Pixel 6. My order was screwed up. Then instead of manually trying fastboot I went to Android Flash Tool webpage and my problems cleared right up. Thanks to all who commented.
[Google Pixel 6 Pro] heij20032003:
Sorry to ask the following questions as i am a newbie for root.

So are these following steps what I need to do now after sideloading the OTA?

Go to https://developers.google.com/android/images to download the latest factory image zip

- raven 12.1.0 (SP2A.220405.004, Apr 2022)

Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img

Copy boot.img to your device.

Patch boot.img with Magisk: "Install" > "Select and Patch a File"

Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.

Reboot your device to bootloader.

Flash the patched image:

Code:

fastboot flash boot <drag and drop master root.img here>

Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>

One more question, at point 5, it is mentioned that "Rename this to "master root.img" and retain it for future updates." Actually, in what scenario will I need to use this "master root.img" for updates?

Million thanks for your help.
[Google Pixel 6 Pro] Lughnasadh:
Update on this issue: Taking the April OTA via "Install to Inactive Slot" has been fixed with the release of Canary 24306. However, May is another month 🙃
[Google Pixel 6 Pro] V0latyle:
Yes, this process is correct. You don't have to keep a 'master root image'; instead, you can simply patch the new boot image every time there is an update. My thinking on this is that older kernels will typically boot without a problem on newer system versions, so you could keep a "master" patched image that you simply boot every time you need to re-root. You would never flash this image; you'd just live boot it: fastboot boot <master root image>

Android would then boot with root, and you could use Magisk to directly patch the kernel image in /boot (Direct Install). The caveat here is that if you update via OTA, anti-rollback protection may prevent the older boot image from booting.
[Google Pixel 6 Pro] V0latyle:
I'm going to add this comment to the OP:

If you flash the patched image to both slots, Magisk will not be able to restore the factory image for OTA. This is why I have suggested booting a patched image, then using Direct Install, as Magisk will ensure an unpatched backup is retained for future restoration.
[Google Pixel 6 Pro] marekm69:
Hello.

I updated to april, I did what was in two post higher (fastboot boot master_root img), but it doesn't boot, stack no google logo and after few seconds reboot to original boot.img. How can I got root, can somebody help me?
[Google Pixel 6 Pro] V0latyle:
What version of Magisk are you using?
[Google Pixel 6 Pro] marekm69:
Magisk canary 24306.
[Google Pixel 6 Pro] V0latyle:
How did you update to the April build?
[Google Pixel 6 Pro] marekm69:
I flashed april update by flash-all with no "-w", but I can flash it again, if You tell me how to do it referent way, to get later root.

I used this way -

https://xdaforums.com/t/pixel-6-pro-easy-step-by-step-unlock-root-update.4361847/
[Google Pixel 6 Pro] V0latyle:
There's nothing wrong with the way you updated.

Did you patch the April boot image to create your "master root" image? Note: You don't actually need a "master root" image, you can just title the boot image relevant to the version, i.e., "April patched.img"

Make sure you're using the April boot image for this. Older boot images may not work, although I believe the kernel version is still March. It's odd that it won't live boot. Just try flashing the patched image.
[Google Pixel 6 Pro] marekm69:
Should I flash patched boot, or boot only and later use Magisk directly?

Other question flash patched boot to all-slot or not?

OK, I got it. Thank for help.
[Google Pixel 6 Pro] V0latyle:
Just flash the patched boot image.

The whole idea with the "master root image" is that you wouldn't have to re-patch the new boot image every time; instead, after updating, the idea is to live boot the patched image;

fastboot boot <master root image>

This loads the patched boot image directly into RAM but does not flash it. In theory, one could use this after every update, then use Direct Install in Magisk to patch the resident boot image.

It hasn't been working for everyone, though.
[Google Pixel 6 Pro] marekm69:
Yes, I booted patched boot image, later patched directly by magisk, then reboot, add modules and reboot again. It looks crazy, but works for my. Thank You for help.
[Google Pixel 6 Pro] ginfest:
Hi All,

Up until the March update I was adding the line "-disable-verity --disable-verification vbmeta.img" to Flash-all.bat. I read that it was no longer necessary so I flashed March w/o it and had no issues. Now I'm reading it may cause issues? Should i add that line back when I flash April? Or will that wipe my phone?

Thanks
[Google Pixel 6 Pro] Lughnasadh:
Disabling verity & verification was originally needed due to the fact that the phone would not boot if you had (in general) a modified boot image, e.g. magisk patched or custom kernel. This was fixed back in December with Canary Magisk 23016 and most, if not all, custom kernels now have updated the magiskboot binaries to also prevent this problem.

However, in various situations people are still getting the "Your device is corrupt" eio message. Disabling verity & verification will likely prevent you from getting this message, but this isn't to say that you need to disable those flags. Earlier in the device's history, when you got the corrupt message the only way to get rid of it was to wipe data or clean flash. Now it appears that there are several other methods to get rid of the message without having to do a full wipe/clean flash (depending on what you were doing to cause the message to appear), although there still may be some circumstances where a wipe may be needed.

Having the corrupt eio message does not appear to cause any harm and people have used their phones just fine with this message present, as far as I can see. It seems to be more of an annoyance.

If you don't currently have those flags disabled and do decided to disable them again, a wipe will be required.

So it's up to you whether or not to disable those flags. Most people today don't and have had no problems for the most part, but a few of us (myself included) still do, just to prevent getting the corrupt message in the first place and possibly having to wipe to get rid of it. As I said above, though, there now appears to be other ways besides wiping to get rid of that message if you do run into it, although there still may be some instances where a wipe may be required. But with Magisk and magiskboot binaries being updated, the original need to do this is no longer required.

Hope that helps...
[Google Pixel 6 Pro] V0latyle:
I'd like to point out that there are two corrupt messages.

First is the red eio message:

This indicates that while a valid Android system has been found, a dm-verity mismatch has occured. It is not a fatal error, and the device can continue to be used. More information here.

What exactly causes it, as well as how to fix it is unclear at this time; I have encountered this error before, and sideloading the OTA fixed it. I personally have never encountered this when using the factory image method.

Second, there is the Rescue Party:

This means the system has detected that core system components are stuck in a crash loop; this may be the kernel or a persistent system app. More information here

This is a fatal error; we encountered this when we first disabled verity/verification if /data was not clean; the user could either reflash the unpatched boot image and vbmeta without the disabling options, or wipe data to continue.
[Google Pixel 6 Pro] Dragon Kumera:
I believe I have seen these error messages before to. I think it relates to the boot image being flashed and not the correct version. Like if an outdated one gets flashed over the updated version.
[Google Pixel 6 Pro] V0latyle:
Yeah, that can be the case as well. It just means that the boot image didn't pass verification.
[Google Pixel 6 Pro] Dragon Kumera:
yup and is easily fixable with bootloader being unlocked.
[Google Pixel 6 Pro] Lughnasadh:
Ironically, flashing an old boot image and then updating to the current boot image is one method to get rid of the "Your device is corrupt" message if you get it while flashing a custom kernel 🙃 (May be specific to Kirisakura. See Kirisakura kernel thread and it's F.A.Q.).
[Google Pixel 6 Pro] fil3s:
I've gotten this before on my p6pro. Sideload seemed to be the only way to fix. I'm facing a problem , that's probably unrelated, but just thought i'd bring it up, my phone isn't accessible from windows file explorer , I double click it, but the phone storage won't open in file manager , I literally have to use 'pushbullet' , an app for transferring files from phone to PC, and vice versa, to access my patched boot.img from the downloads folder. Probably irrelevant
[Google Pixel 6 Pro] V0latyle:
So you're saying that your device appears under My Computer/This PC, but you're unable to actually open the storage? Sounds like a computer problem, or maybe an iffy USB cable.
[Google Pixel 6 Pro] fil3s:
Yeah. I flash this phone a lot with the cable, so I don't think it's that. I may try formatting my SSD
[Google Pixel 6 Pro] Lughnasadh:
Do you have the latest of this installed? Also, is your USB connection still set to File Transfer in Dev. options?
[Google Pixel 6 Pro] fil3s:
Yes I do bro. Too late anyway setting up my PC after format
[Google Pixel 6 Pro] V0latyle:
I would say make sure you're using the latest version of Platform Tools, but if you're setting everything back up you'll be using the latest anyway.
[Google Pixel 6 Pro] mcwups1:
I'm not sure what I'm doing wrong, because it seems so straight forward, but this method has yet to work for me the past 3 updates. I just install the whole thing and delete "-w" now, but THIS way posted, seems easier, if it would work.
[Google Pixel 6 Pro] roirraW "edor" ehT:
From what I've observed over the years, that way has always been at least a little bit hit and miss, although I think it misses more often recently.

I've always been a fan of just using the full firmware image with the -w removed, as you said, and I don't have any plans on doing it any other way.
[Google Pixel 6 Pro] Lughnasadh:
Several reasons this method could fail:

1. For the April build, Canary 24306 is needed for the "Install to Inactive Slot" OTA method (for the March build I believe Stable 24.3 worked but not Canary 24304/5?)

2. Any modification of any read-only partitions (e.g. /system, /vendor), etc., will cause it to fail (pre-OTA block verifications fail)

3. Being on a custom kernel without restoring all 4 stock images beforehand (boot.img, dtbo.img, vendor_boot.img & vendor_dlkm.img) will cause it to fail.

4. Google Ghosts...

As with @roirraW "edor" ehT , I'm a flash-all type of person, although Android Flash Tool and the new Pixel Flasher are good alternatives as well.
[Google Pixel 6 Pro] State.of.mind:
Sorry if I missed this, but is there a problem with the latest version of Magisk on the April update?
[Google Pixel 6 Pro] roirraW "edor" ehT:
See the post above yours.

Since I use the "flash-all with -w removed" method, I stick with Magisk Stable (v24.3) and all is fine.
[Google Pixel 6 Pro] Hand76:
Hey guys I want to pull the trigger on a Pixel 6 Pro. Still on a Pixel 2 XL.

Ive read through the post but I like to always follow very detailed guides when rooting.

Can I still follow this January update guide from Youtube if the phone has been updated to March/April? Also should I substitue magisk 24.1 for 24.3 if it has been updated to the latest?

Thanks again in advance for any help
[Google Pixel 6 Pro] Lughnasadh:
I'll be honest, I didn't watch the video you posted so can't tell you if you can follow it. However, the instructions in the OP will work just fine.

I would use Stable Magisk 24.3 unless you decide to update via the "Install to Inactive Slot" method. If that's the case you will want to use Canary 24306.
[Google Pixel 6 Pro] fil3s:
Note this guy is using 'minimal ADB and fastboot'. I personally would use platform tools directly from the google android developers website.

This is a very careful guide that you've linked. It's really not hard. You can either live boot the magiskboot.img ;

fastboot boot <path_to_magiskboot.img>

then direct install from the magisk app, or you can just as easily flash it.

fastboot flash boot <path_to_magiskboot.img>

It might be safer to live boot it if you're rooting the device for the first time.
[Google Pixel 6 Pro] dmerillat:
e: wrong thread, sorry.
[Google Pixel 6 Pro] crypticc:
Hi there everyone

I'm hoping someone can help me pick apart some errors that I'm getting after updating to the 220405 OTA FW.

These screenshots above are

exactly the error.

First

i got red EIOI error after following the "uninstall Magisk... Imstall OTA... Install magisk to inactive slot" method.

And then the other error comes up

Slot B boots with SP2A.220405 albeit with those errors.

My original intent was then to install raven-sp2a.220405.004 over the top of the working slot B but that was giving the errors. My aim was to get Slot A (old version) and Slot B (new version) as if I had completely stock ROM

So in an attempt to fix I downloaded raven-sp2a.220305.013.a3 stock image, changed current slot to the other slot "A" and then modified the flash-all.bat to remove the "-w" and then ran.

But during the install of slot A I got this error when it got to flashing dbto.img

"Writing sparse 'product_a' 1/11 (bootloader) failed to write chunk #0"

The script then terminates without completing. Full list below

Spoiler content hidden.

Any ideas what that is? Is this a USB cable issue?

For now my phone is still booting to Slot B but with those error messages.

As an aside .

Before I tried to flash-all to Slot A the slot-unbootable:a said "no", (but then I had those errors when booting slot B)

Verity is not disabled

Fastboot screen UART says "disabled".

Typically I;ve needed to use the sideload method to clear the orange "Rescue Party" error. But this is the first time I got this EOIF error.

Here's my fastboot getvar all....

Thanks for any help anyone can give me.

Spoiler content hidden.
[Google Pixel 6 Pro] V0latyle:
Ich verstehe nur Bahnhof. I couldn't tell you what the problem is by looking at this.

When you attempted to patch the OTA, were you using Canary 24306?

Are you using the latest ADB Platform Tools?

What Magisk modules did you have installed?
[Google Pixel 6 Pro] crypticc:
Hi

Magisk 2403 from here.

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

Latest ADB (I think d/l a few months ago now). I can recheck tonight

Just zygisk.

Thanks,

Chris
[Google Pixel 6 Pro] V0latyle:
Do you mean 24.3? You should be using Canary 24306. If you are running Stable or Beta

Current is 33.0.1, March

Not a module.
[Google Pixel 6 Pro] crypticc:
Thank you.

I didn't spot this...

OTA triggers red `eio` screen then bootloops on Pixel 6 · Issue #5685 · topjohnwu/Magisk

Device: Pixel 6 Android version: 12.1 Magisk version name: 704f915 Magisk version code: 24305 The red eio screen issue has existed since the March update on 24304. While falling back to 24301 worke...

github.com

So now accepting I should've used magisk 24306 any ideas how to recover the other partition? Or just try to reflash with flash-all with -w flag removed again using latest March fastboot?

Incidentally does that keep both internal storage and apps? (I have banking apps that rely upon old device and are a right pain if installing to a new / blank device)

Thanks

Chris