yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] V0latyle:
Both effectively do the same thing. Restoring the stock boot image from fastboot is just reflashing the stock boot image. Restoring it from Magisk means the app removes the patch from the boot image, essentially restoring it to stock.

In both cases you lose root. No big deal; take the OTA, let the update complete, then live boot your master boot image, open Magisk, and select Direct Install to patch the updated boot image.
[Google Pixel 6] MattP410:
That's what I was thinking. Thanks for the affirmation.
[Google Pixel 6] V0latyle:
Folks, this thread is specifically for the Pixel 6. Here are my threads for other devices:

Pixel 4a (5G):

https://xdaforums.com/t/guide-root-pixel-4a-5g-with-magisk.4356117/

Pixel 5:

https://xdaforums.com/t/guide-root-pixel-5-with-magisk.4356219/

Pixel 5a:

https://xdaforums.com/t/guide-root-pixel-5a-with-magisk.4356221/

Pixel 6 Pro:

https://xdaforums.com/t/guide-root-pixel-5a-with-magisk.4356221/
[Google Pixel 6] bobby janow:
Ok I followed your rooting tutorial and I'm rooted. Running Proton but cannot pass SN. Any suggestions? I denied all the apps in the deny list but still no go.
[Google Pixel 6] V0latyle:
The ROM or the kernel?

This is probably a better question to ask in the Magisk General Support thread. I don't provide support for Magisk or its modules.
[Google Pixel 6] bobby janow:
I did ask there and I had to install the SN fix under modules. Now all is working, thanks. Great guide too.
[Google Pixel 6] andreipaval:
Hi, I have a question, I see in the Pixel 6 Pro sister thread:

that on the Update and Root OTA Sideload section, there is the additional step

"When the OTA completes, you will be in recovery mode. Select "Reboot to system now".

-----Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.

Reboot to bootloader."

to allow the system to boot before proceeding with re-rooting the boot.

This step is missing in this Pixel 6 thread. Is it really not necessary for P6 and only for P6Pro ?

Why is there a difference ? Thanks.
[Google Pixel 6] dilruk:
Just updated to the January build via Automatic OTA. However, I'm not able to boot from the previously patched boot image. Phone just goes to a black screen and restart with no root. Did anyone try this?
[Google Pixel 6] Strephon Alkhalikoi:
I didn't. I extracted the January boot.img from the factory zip I downloaded and patched it using Magisk before updating. Then I flashed it to the unit after updating. More annoying than simply taking an OTA, but I retain control this way.
[Google Pixel 6] dilruk:
I guess I got lazy. Do you mind sharing the stock boot.img? I'm remote with limited bandwidth at the moment.

TIA
[Google Pixel 6] V0latyle:
The instructions are supposed to be the same, I'll fix it.

Edit: Fixed
[Google Pixel 6] dilruk:
Using the master boot image to live boot didn't work for me after the January update.
[Google Pixel 6] V0latyle:
Odd.

You did use Magisk 23016 to patch it?
[Google Pixel 6] dilruk:
Yes. Tried with both parched images from November and december builds
[Google Pixel 6] V0latyle:
I don't normally host files, so don't ask me to, but here's the untouched January Oriole boot image

Edit: Upload keeps breaking for some reason
[Google Pixel 6] dilruk:
Thanks for going out of the way. Maybe it's a XDA issue. Do you use mega or Google Drive?
[Google Pixel 6] V0latyle:
As I'm not a developer, and these files are already hosted by Google, I'm not exactly enthusiastic about using my Google Drive quota for hosting
[Google Pixel 6] dilruk:
Understood
[Google Pixel 6] V0latyle:
Oriole January boot image
[Google Pixel 6] andreipaval:
Is it important to let it fully boot the first time after OTA sideload, and only after this to flash the patched boot image ?

I did not do this, after OTA sideload, I rebooted to bootloader and flashed the January patched boot (patched it before updating). Everything worked fine, did not run into any issues, root was available.
[Google Pixel 6] kornball:
This may be a stupid question, so I apologize in advance. I understand that with Magisk 23016 the disable verity and verification flags are no longer necessary, but is there any harm/downside to including them in the update command like so:

fastboot update --skip-reboot --disable-verity --disable-verification image-xxxxxx-xxxxxxxx.zip

My main concern is making sure my data isn't wiped during the update.
[Google Pixel 6] gnarkills:
could you kindly post a patched boot image too?
[Google Pixel 6] dilruk:
Very easy to patch it through the latest canary magisk manager. Please try.
[Google Pixel 6] dilruk:
Don't think there will be any issues. Also dont see why you should bother
[Google Pixel 6] gnarkills:
I stupidly forgot to copy the patched image back to my computer and now I'm stuck in boot loop with no patched image to boot... I would gladly appreciate if someone could post one. thanks!
[Google Pixel 6] Slim2none4u:
Dropbox - File Deleted - Simplify your life

www.dropbox.com
[Google Pixel 6] dilruk:
Try flashing or live booting using the stock image.
[Google Pixel 6] kornball:
So as far as you're aware, there's no chance my device will be wiped during the update process on Magisk 23016?
[Google Pixel 6] dilruk:
Yes I've done it few times with no issues
[Google Pixel 6] gnarkills:
edit : sorted :)

thanks for the patched img!
[Google Pixel 6] SMMmmm:
I can't seem to install the OTA update, every time I try I am getting this.

Can anyone help me with this? I have it rooted following the instructions in this thread with SafetyNet check passed.
[Google Pixel 6] DNAblue2112:
I had the same issue. I side loaded the ota via recovery
[Google Pixel 6] V0latyle:
As long as you're using the same version boot image as the update. The OTA process will check the boot image version, and if it doesn't match, it decides the update failed. So, if you're using the "master image" method, you'd want to let it boot the updated image first.

The factory update itself does not wipe data, and none of the options you included would prevent a data wipe. Just make sure you don't use the -w option. And there is absolutely no point to disabling verity/verification if unnecessary. I recommend you don't.

I already went out of my way to link the file to begin with. Don't be lazy.

Reflash the stock boot image.

Pretty common on rooted devices. Sideload the OTA.
[Google Pixel 6] airtower:
This seems like it could greatly simplify updates when rooted, but is there a reliable method to get the OTA? I tried the January update ~10 times with no luck. I'd love to be able to stay up to date without needed abd each time.
[Google Pixel 6] V0latyle:
Download and sideload it.
[Google Pixel 6] airtower:
Guess I'm still not seeing the immediate benefit. Sideload requires adb, and will boot back into an updated, unrooted OS. Meaning you'd still need to extract, patch, and flash the new boot.img. Or is there something I'm missing here?

Apologies if I'm being ignorant, I recently came to the P6 from a OnePlus 6 and haven't really kept current with new security/update methods over the past 4 years. The process on the OP6 was install OTA, flash Magisk to inactive, reboot and done.
[Google Pixel 6] SMMmmm:
I tried sideloading the OTA (downloaded from: https://developers.google.com/android/ota), and that failed as well!! I got an error like this:

"Error applying update: 7 (ErrorCode::kInstallDeviceOpenError) E:Error in /sideload/package.zip (status 1)"

I don't know what's wrong! Please help!
[Google Pixel 6] V0latyle:
That's the point of having a patched boot image that you can use to temp boot so you have root and can directly patch the updated boot image with Magisk.

Might be corrupted, make sure you have the right file and try again
[Google Pixel 6] SMMmmm:
Redownloaded the OTA and tried it again, but it failed again!

This is the exact error:

Finding update package...
Verifying update package...
Update package verification took 66.3 s (result 0).
Installing update...
Step 1/2
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
E: Error in /sideload/package.zip (status 1)

Install from ABD completed with status 1
Installation aborted.

At the top of the screen, it says in red, but I have selected 'Reboot system now' and the phone works fine as before.

WARNING: Previous installation has failed.
Your device may fail to boot if you reboot or power off now.

How do I get the new OTA? I don't know what to try, please help!
[Google Pixel 6] V0latyle:
I'm not sure why the OTA isn't working. Follow the instructions in the OP for the factory image.
[Google Pixel 6] SMMmmm:
Will that do a factory reset of the phone? I really don't want to setup everything again...

Thanks for your replies!
[Google Pixel 6] airtower:
Not if you follow them as written. Remember you need to reboot the bootloader several times.
[Google Pixel 6] SMMmmm:
Thanks a bunch guys! Finally could update the phone with the factory image.
[Google Pixel 6] V0latyle:
Why do people keep asking if the factory update will wipe their device? Where did this idea come from? It needs to be squashed.

If you're reading this, and you have questions on whether something could be an issue...if it was, I would mention it in the OP instructions. Put your presumptions aside and simply follow the instructions. That's all you have to do.
[Google Pixel 6] biglo:
When I try to sideload the OTA from recovery when I try the adb devices command I keep getting unauthorized but when the phone is on its shows the device and I'm able to use adb to reboot the phone to recovery. I unauthorized it from developer options and deleted the key from my folder in windows and re-authorized and ran the reboot to recovery command again and its still unauthorized.

Not sure what I'm going wrong here.
[Google Pixel 6] Strephon Alkhalikoi:
They probably manually installed full factory images in the past, which WILL wipe the device if the -w flag isn't removed from flash-all.bat.
[Google Pixel 6] bobby janow:
It's because they don't read and just post their questions in threads that have nothing to do with root. I can be reading a thread about fixes and features and then all of a sudden the whole thing is about Magisk, OTA with root, bricked when I unrooted etc. If their questions were put into your thread they'd have an answer almost immediately.

edit: for instance here: https://xdaforums.com/t/january-full-ota-image-available.4388437/page-3 It starts on post 41 and continues on at post 61 and now the thread about OTA available has become a root doesn't work thread.
[Google Pixel 6] V0latyle:
These are fairly basic questions, though, and as I pointed out, I wouldn't write instructions that would wipe the device without explicitly pointing that out. If someone wants to use the batch file or the shell script, that's up to them. If they can't figure out what commands they need by reading my instructions, they shouldn't be doing this anyway.

I made it clear on the OP that this is NOT a basic, dummy proof guide.
[Google Pixel 6] airtower:
If it says no command, press vol+down and it will bring up the normal recovery options including ADB sideload
[Google Pixel 6] kornball:
I appreciate you clarifying. Before Magisk 23016 came out, I thought there was an issue with possible data corruption if verity and verification weren't disabled. This would then require a data factory reset.

Dating back to my Pixel 3, I would update using monthly factory images. Get to fastboot, flash bootloader, flash radio, flash update with --skip-reboot flag, and then flash Magisk patched boot.img before booting back into Android. You have this exact procedure outlined in your OP, so that's what I will follow. Thank you!
[Google Pixel 6] kemikalman:
Hello, I don't know if this is normal but, yesterday I sideloaded the january ota via adb, after that install the given magisk on the first page, get the boot.img from the zip file in the latest update, patched it through magisk and flashed it, I have root on the first boot after flashing but everytime I reboot my device the root is gone.
[Google Pixel 6] V0latyle:
The only version of Magisk that supports flashing to inactive slots on Pixels is the alpha. Canary does not yet support it.

Please read the OP. There are several methods by which you can update your Pixel and reroot. That's the whole point of this guide; all you have to do is read and follow the instructions.
[Google Pixel 6] biglo:
Thanks, I still screwed up everything thanks to a crappy USB C cable.
[Google Pixel 6] airtower:
It wouldn't work for me with a C-C cable. Only A-C.
[Google Pixel 6] Oberbergler:
Same problem. Followed the installation process from the description. It's exactly the same how I did it on my Pixel 3 the past 3 years.

Have you found a solution? I absolutely cannot install the update. Tried Nov, Dec and Jan OTA via ADB and system OTA update.
[Google Pixel 6] co9:
I used the Android Flash Tool method. Worked for me.
[Google Pixel 6] Oberbergler:
But you had to wipe all data, right?
[Google Pixel 6] Nightf0x_007:
can someone point me to the easiest way to update to jan. update without losign my data or my root setup TIA
[Google Pixel 6] Slim2none4u:
I disable all magisk modules.

Reboot to bootloader.

fastboot flash-all (with -w removed)

Reboot phone

Transfer boot.img to phone.

Patch with magisk

Transfer patched.img to PC

fastboot flash boot --slot all magiskpatched.img

reboot

re-enable mods one at a time with reboots in between.

Thats my method.

YMMV
[Google Pixel 6] SMMmmm:
Yes, I could finally update it to the Jan release.

Follow the 'Update and Root Factory Image' in the OP. That worked for me, follow that exactly and that method doesn't wipe data.
[Google Pixel 6] V0latyle:
Why would using the Flash Tool require wiping data? Who started that rumor?

There are several ways in the OP. Read it.

Disabling modules or removing Magisk is not necessary.

Exactly. It's rather frustrating to see the same question asked repeatedly: "Will the factory method wipe my data?"

No. Just follow the directions exactly as I wrote them.

I am not a fan of having to restore after a data wipe, and I'm not a fan of anyone else having to wipe data. I don't have any tricks up my sleeve that I'm not sharing.

The bottom line, for everyone who keeps wondering if your data will be wiped:

If you read the OP, and did not see any mention of a data wipe being required, then why are you asking?
[Google Pixel 6] Nightf0x_007:
while in bootloader executing flash-all it fails to update and says boot partition not found and just updates the radio and the bootloader only
[Google Pixel 6] Nightf0x_007:
after flashing magisk patched boot img i get boot failure cant boot system up
[Google Pixel 6] Nightf0x_007:
Now my device when reboots i get your device is corrupted before the bootloader unlocked warning is this new in jan update or ials sowmthing screwed on my phons
[Google Pixel 6] V0latyle:
Your Platform Tools are probably out of date. Go back and read the OP.

Reflash the stock boot image.

You didn't disable verity/verification, did you?

Also, please post only ONCE. If necessary, edit your post to contain more information, but multiple posts is unnecessary.
[Google Pixel 6] Nightf0x_007:
Already disabled dm verity/verification when i eas updating from nov. To dec.

Now my phone is working and updated to jan., I would like to reflashed it again as i feel the phone is not on a stable ground and at any moment it will bootloop
[Google Pixel 6] V0latyle:
They don't need to be disabled. Go back and read the OP. You must use Magisk Canary 23016. Don't ask for help if you won't follow instructions.
[Google Pixel 6] Nightf0x_007:
I have magisk 23016 already and i disabled them when i 1st got the phone and updated it from nov. To dec.
[Google Pixel 6] V0latyle:
I think you misunderstand. Magisk 23016 precludes the need to disable verity/verification; disabling only happens when the /vbmeta partition is flashed. If it is reflashed at any point without the disable options, they are enabled by default. So, if you did not disable verity/verification when you updated to January, they are now enabled. It doesn't matter anyway.

Do this::

Download factory image and extract its contents

Extract boot.img from image-oriole-buildnumber.zip

Manually patch boot image in Magisk, copy patched image to PC

Reboot device to bootloader

Apply update:

fastboot update <drag and drop image-oriole-buildnumber.zip here> --skip-reboot

When update finishes, reboot to bootloader

Flash new patched image:

fastboot flash boot <drag and drop magisk_23016-patched_xxxxx.img here>

Reboot to system.
[Google Pixel 6] biglo:
Had the same issue.
[Google Pixel 6] thaitan:
Is there somewhere a video tutorial...i cant update my rooted pixel 6 to the january update..need some help pls
[Google Pixel 6] V0latyle:
What specifically are you having trouble with?

Did you read the ENTIRE OP, and have you followed the instructions to the letter?
[Google Pixel 6] mailistman:
hello ..

thanks to OP for the instructions. i don't mean to derail this topic but i believe my issue is much related here. i am using P6 oriole. i was able to root on november build .037 and still have copy of my patched boot img on november build. i updated to january build .007 following guide here using update & root factory img method. update was success, but i lost root. i might have made mistake at some point.

now in no rooted state, when i tried to patch my boot.img using magisk 23016, i can't go to the next step because "Let's go" button greyed out. see attached. i tried to google it before i come here but same issue(s) were from different phone model & different magisk version, and worse, no resolutions either.

1. has anyone here experience the same issue ? and how did you overcome it ?

2. can someone please upload their P6 oriole patch boot .img from january build for me to try to flash on mine so i can get root ? or is the patch file specific for each phone ?

thank you !
[Google Pixel 6] V0latyle:
Please resize your screenshot or put it in a spoiler.

Did you have the Magisk app hidden before you updated?

You should still be able to manually patch and flash the new boot image.

The boot image is not device specific; if someone wants to post a patched Oriole boot image, any Pixel 6 can use it.
[Google Pixel 6] V0latyle:
Magisk Canary has been updated to 23017. Installing to inactive slot now supported.

Download it here or update through the Magisk app.

Note: If you have the Magisk app hidden, MAKE SURE you only update through the app! Multiple instances of Magisk will break root.
[Google Pixel 6] mailistman:
thanks for replying. sorry about attachment. on november build, i had magisk visible on app drawer as i run root explorer & few modules. hopefully someone will post copy of patched boot img on january build.

dumb question : can i use patched boot img from november build to flash in fastboot to get root on this january build ? or i will get bootloop ?

thank you.
[Google Pixel 6] V0latyle:
You can temporarily boot an older boot image for root. Don't flash it. Instead, when you boot the older patched image, open Magisk, tap Install, then Direct Install to patch the new boot image.

Alternatively, if you're using the factory image update method, you can just extract and manually patch the new boot image.
[Google Pixel 6] mailistman:
can you please teach me how do i manually patch the boot image ? am i going to need magisk to patch ? the "let's go" button still inactive.
[Google Pixel 6] V0latyle:
Please read the Initial Root / Create Master Root Image section in the OP.
[Google Pixel 6] airtower:
Are you being prompted to select a file? "Let's Go" remains greyed out unless a file is selected.
[Google Pixel 6] mailistman:
yes sir. boot.img has been selected (my post #281, see the radio button where you ticked option is highlighted), but "let's go" button remains greyed out.

this where i hit the wall sir :

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

thank you.
[Google Pixel 6] airtower:
Sounds like an issue with your magisk install. Have you cleared data or un and reinstalled?
[Google Pixel 6] mailistman:
i did un & reinstalled canary 23016 few times but getting same issue. later i will try with the new 23017.

if issue remains with 23017, i am thinking to downgrade back to november build. but it sounds too much work just to get the magisk do the magic 🙈.

wondering so far nobody posts january boot.img patched for me to try. should i open a new thread ?
[Google Pixel 6] V0latyle:
I don't think it's a problem with your firmware. Downgrading most likely won't help.

Try this:

In Magisk, tap Uninstall > Complete Uninstall. Let Magisk reboot your device. You will reboot without root.

Install Magisk Canary 23017

Copy the January boot image to your device's root storage folder (make sure there's no others)

In Magisk, tap Install > Select and Patch a File; select the boot image you just copied, then Let's Go

Copy patched boot image back to your PC; rename it something easy like "patched January.img"

Reboot to bootloader and flash the patched image:

fastboot flash boot <drag and drop patched image here>

Select Start on your device, you should boot with root; confirm in Magisk (Installed should not say N/A)
[Google Pixel 6] mailistman:
followed your advice with 23017 till point 4 but still no go.

FYI, on my 23016 i didn't have the restart button nor uninstall option on magisk app, so i removed it from Apps setting.

attached screenshots.

what else can i possibly try ? thank you.
[Google Pixel 6] capntrips:
Someone already posted a patched image a few pages back, fyi.
[Google Pixel 6] V0latyle:
I think you're assuming the "Let's Go" button is inactive simply because it is gray. Tap on it after selecting the boot image. It looks exactly the same on my device. It should work.

You won't see the Restart option if Magisk doesn't have root access, as is shown in your first screenshot: Installed: N/A
[Google Pixel 6] proac:
Is it possible to update to Magisk Canary 23017? There is an option to install into an inactive slot after all.
[Google Pixel 6] mailistman:
thank you to poster #232. i got my root back using the patched boot.img s/he provided.
[Google Pixel 6] V0latyle:
At the top of the page...
[Google Pixel 6] mailistman:
true.. i wasn't rooted

update : solved my own problem about the greyed out "Lets Go" button : i toggled OFF System > Developer options > Don't keep activities.

you can try to toggle it on or off followed by reboot and see for yourself when you try to select & patch a file.

thank you for all your help over here !
[Google Pixel 6] V0latyle:
Magisk Canary 23018 is out.

Changes:

[Zygisk] Show warning in app UI to indicate incompatible Zygisk modules

[App] Allow modules to specify an update URL for in-app update + install

Update from within Magisk to prevent problems like breaking root.

If you do not already have Magisk installed, Download it here
[Google Pixel 6] V0latyle:
Magisk Canary updated to 23019

Changes:

- [Zygisk] Skip loading modules into the Magisk app to prevent conflicts

- [MagiskBoot] Change `zopfli` to a more reasonable config so it doesn't take forever

- [General] Several `BusyBox` changes

Preferred method of update is from within Magisk app.

If installing for the first time, here is the APK Download
[Google Pixel 6] V0latyle:
@topjohnwu has been busy. He doesn't get nearly enough appreciation for all his hard work.

Magisk Stable is still 23.0.

Magisk Beta is now 24.0

Canary is now 24001

Magisk 24.0 discussion thread