yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Koss4c:
Just wanted to say thanks for your time and effort on this @V0latyle - Very Cash Money
[Google Pixel 6 Pro] straumli:
Upgrade fastboot did the trick, thank you!
[Google Pixel 6 Pro] hpower1:
Another successful update via sideload of Jan update. Updated magisk to 23017 first. Also updated the play store to Dec after I did the sideload. Thanks again for all the help in here.
[Google Pixel 6 Pro] Kris Chen:
I want to ask about OTA: Whether can I update OTA but won't lose Magisk root ?

I have another phone - Oneplus8pro. I can OTA and won't lose the magisk root.

1. Donwload full OTA file and flash it ... BUT DON'T REBOOT phone after

finishing it;

2. Open Magisk manager to install Magisk to another inactive slot;

3. Then rebooting phone...

Whether it works at Pixel6 pro OTA ?
[Google Pixel 6 Pro] hpower1:
i followed the steps in OP for OTA sideload. Did that the last few times, didn't do anything with slots. Works good.
[Google Pixel 6 Pro] V0latyle:
Magisk 23017 is supposed to work that way, not sure if it's working for the P6 though. Until we know it's working for sure, the best way to update is by dirty flashing the factory image.
[Google Pixel 6 Pro] Koss4c:
Edit : If your having google pay issues or other random google issues/ bank app issues follow this:

Just wanted to throw in, as V0latyle did'nt cover it: the google services: Zygist, Magisk Hide Props Config Module, Universal Safetynet Fix module

A Brilliant video going through installation:

Maybe you could pin this so people can easily follow :)
[Google Pixel 6 Pro] cmh714:
I didnt deal with all that and everything is working....curious if others had to do this....
[Google Pixel 6 Pro] Koss4c:
yeh i had to. unsure why. But the video is very good. ez to follow and working now (google pay issues)
[Google Pixel 6 Pro] roirraW "edor" ehT:
Those things aren't necessary for root proper. They're only necessary for Google Pay, some banking apps, and probably a very few non-banking apps. It's also covered at a high-level in the OP. Just click on the "Spoiler: Pass SafetyNet" in the first post.

I never fooled with those steps before a few months ago but they work perfectly for me to get working Google Pay and a few bankings apps I use.

If you need more detail than @V0latyle gives in the OP, at the top of the list of Pixel 6 Pro threads, click the How To Guide filter:

Then look for (or Control-F to search/find for) the thread by @Pekempy called "Working SafetyNet with Pixel 6 Pro Android 12". That first post will give you the detail you need. Please ask any questions if necessary in that thread.
[Google Pixel 6 Pro] cmh714:
Yeah I didnt run any su commands like the video does....my banking app and gpay works as advertised :) so I am good there. I need to rewatch when I am less buzzed...now I need to get my google work profile working without failing its checks... :)
[Google Pixel 6 Pro] dilligaf56:
Just curious -

I recently rooted my new unlocked Pixel 6 Pro using the January update, Magisk 23016, Zygisk, etc. Everything worked fine until I tried to activate it with the eSIM on Verizon. There was no second IMEI number available, and I was unable to activate it through the usual routine of scanning the eSIM QR code provided by Verizon. Their level 2 tech worked with me for a couple of hours off and on, then punted and contacted Google tech support without any luck. Does rooting by flashing the factory image kill the eSIM capability? Just curious.

I finally got it activated by using a physical SIM and all is working well - but I would like to have the capability to use it if possible.
[Google Pixel 6 Pro] wrlu:
We must connect to Internet first then the OEM Unlocking will come available. (except carrier devices)
[Google Pixel 6 Pro] V0latyle:
You didn't read the OP. I absolutely did cover this under "Pass SafetyNet". Don't hijack my thread. I tried to keep instructions relatively simple. I am passing SafetyNet on my Pixel 5 using the modules I mentioned, and did not have to run any commands.

No

Unfortunately I can't provide any insight to that issue.

Doesn't work for anyone, and problems with unlocking the bootloader are outside the scope of this thread.
[Google Pixel 6 Pro] analyst783:
I tried to apply the Jan update using the android flash tool. There was no 'skip reboot' option (yes, I looked at the 'advanced' options) but I proceeded anyway (prob a very bad decision). Now I cannot boot successfully with a magisk-patched boot image. (Phone evetually winds up in recovery with a 'try again' choice) Did the vbmeta flag get re-enabled? Do I have to wipe to get root back? Finally... how did others use the flash tool? Was 'skip reboot' missing for others?

UPDATE: in the meantime, will try w/flashing the update via fastboot

UPDATE2: back in business w/root. Booting immediately after the flash tool update didn't do any lasting damage (data is intact and readable). I tried the fastboot update as well. The key to getting root back was re-creating my 'master magisk patched' boot image using the latest boot image from the Jan factory image.

I reallllllly thought a 'recent' patched boot image (from Dec in this case) would be sufficient. I still plan to go back and retry the flash tool update (despite the missing 'skip reboot') and see if the updated patched boot image allows root after that.
[Google Pixel 6 Pro] crypticc:
thanks very much for this guide. FYI
[Google Pixel 6 Pro] V0latyle:
This has been confusing for a lot of people.

There is no "manual" enabling of verity/verification. They are enabled by default when /vbmeta is flashed. They can only be manually disabled. The point is moot, as disabling verity/verification is not necessary as of Magisk 23016.

No. If this happens again, you can always reflash the unpatched boot image to get back to system. You won't have root. But, you can get temporary root by live booting the patched image:

fastboot boot <patched boot image>

It's been a little while since I used it; the skip reboot option is not available with the Android Flash Tool. My mistake. After the device boots, just reboot to bootloader and flash the patched image.

Glad you got it straightened out. There's been some weird things going on back and forth with the December and January updates on the P6/P6Pro.

Regardless, if you're having trouble booting the "old" patched image, just download the factory zip and patch the new boot image.

It should.
[Google Pixel 6 Pro] Dragon Kumera:
that a lot of tinkering when it is not needed. But maybe they just had bad luck or are on an older magisk version.

Google pay worked fine on me once google play said certified.
[Google Pixel 6 Pro] cmh714:
In one of the unlocking threads it stated it had to do with the date on the P6. Setting the date a month back removed the greyed out OEM lock....thats what I did and no issues...fwiw
[Google Pixel 6 Pro] V0latyle:
Interesting!
[Google Pixel 6 Pro] cmh714:
Yeah it was the first I read about anything like that IIRC, it said something about the phone needing to be alive for a week....so if you set the date back further than that you should get OEM Unlock to be un-greyed.....wish I could find that again to link but havent yet :) Again IIRC when I did this it took an hour or two while on the wrong date, but it did un-grey for me....
[Google Pixel 6 Pro] CPngN:
My P6P is locking up 2 minutes after booting! I rebooted today because I thought I had lost a widget and was hoping Nova 7 was just acting up. (After rebooting I found the widget 1 page over - need to lock the destop icons down!) Just after my Calengoo app loaded and popped up my reminders for the day, everything froze. ...except the clock. After about 1 minute it reboots. During that minute I cannot do anything on the screen, nor does it respond to holding the power button down for a solid 15-20 seconds! Rinse repeat.

After it boots up, I have about 2 minutes to do things. I paused Adaway, turned off modules in Magisk and then tried to apply the update. Which went all the way through and rebooted when I tapped the button, but... never applied. Oh, I also disabled the blacklist in Magisk in case I had "gone too far" hiding things.

I'm hoping I can just reflash and get out of this.. it's very strange how far it gets before it freezes. As if there's "one last app" or service that executes and gets stuck. Anyone know how to diagnose?
[Google Pixel 6 Pro] CPngN:
I booted and flash booted the original boot.img. Magisk acknowledges that it can't load, no root. No change.. meaning even on stock it is rebooting. Anyone have ideas or seen this yet on their P6 ?? T.I.A.
[Google Pixel 6 Pro] CPngN:
Interesting to note:

While frozen for 60-90 seconds, I can plug it into my Mac again and issue "adb reboot bootloader" and can then flash things. So someone underneath everything, it's running enough to respond to this, and to keep the seconds ticking in the clock. But I can't imagine reflashing everything else will change much, but I suppose it won't hurt either. Going to try, as I was hoping to use the camera tonight. Grrr
[Google Pixel 6 Pro] CPngN:
More fun facts: If I play media before it freezes, the music or video keeps playing. I just reflashed everything (without the "-w" on last command) and rebooted. Started music. It still froze, but played music right until the quick reboot.

I'm still rebooting. It stays "frozen" (unresponsive) longer than it takes to reboot (which is like < 10 seconds).

After that, the first boot had the original colors on the G boot animation. But after that... I've noticed the faded color which I assume means it's acknoledging that it has been "altered" or rooted. Perhaps I should push to both banks, but am I just wasting time flashing the same content that's already there?

This is frustrating!
[Google Pixel 6 Pro] Koss4c:
Super interesting how different people are getting different results :S i would have thought it was be universal. Glad ur is working "off the bat"
[Google Pixel 6 Pro] Koss4c:
Just confirming you have "canary" magisk -> when it downloads, it downloads as app-debug. if u dont have that it wont work (that was my issues)
[Google Pixel 6 Pro] splinterededge:
I would consider flashing back to stock to see if these problems continue to occur, if you still see crashing you can do a log dump and look for why the device is crashing, my first pro was experiencing phy errors when I was watching videos outside, it was really cold here, did and RMA and my new device does not crash. Currently experimenting on the original phone before I return it.
[Google Pixel 6 Pro] CPngN:
Yep, had that one after trying alpha and failing early. The fact that my phone boots and works perfectly fine but only for maybe 2 minutes makes me think that there's something loading that comes near the end or just takes longer than everything else, and then it crashes and boom. I've disabled Tasker, and I had recently set up Greenify again and probably should not have. So since I saw that notification icon show up late one of my reboots, just before it "soft froze", I thought that may be the culprit. Seems logical given what it can do. But I can't uninstall it until I remove it from Device Admin Apps. Which I have tried to do, but it doesn't stick! If I boot, jump in real fast and disable that setting, back out, and hold power+up -> Power Off so that things should definitely save before restarting.... it still comes back as a Device Admin.

I have a bad feeling that it may be faster to jump in and try to do a full reset and just restore everything yet again. At least I can get enough time to save my Nova setup and other configs.

Can I grab logs from an adb shell to review on the computer? I'm not sure where to look on Android 12 or what to grab with the short period of time I have under a normal boot. (Can one pull files from fastboot or recovery?) Thanks all!!!
[Google Pixel 6 Pro] CPngN:
Yeah I have put stock back on. Then I switched to the other slot and repeated everything including the zip file push which takes a while. It booted and runs.... just as it has all day. I have definitely lost root; verified in 3 apps.

During a reboot in one part of that attempt, I noticed the usual faded G logo was back in full rich colors, like I had relocked the bootloader?! But since then it's been back to that faded look. Maybe that was related to the first time booting on slot_a.

So yeah, I think logs would be key before wiping everything. How can I grab the right ones? I'd say between the time I boot and can get in with adb and the time it finally reboots itself I have 4-5 minutes.

Thx guys
[Google Pixel 6 Pro] Koss4c:
Sorry mate you did cover it.

Just wanted to give people the easy version *hands the floor back to you* its all yours
[Google Pixel 6 Pro] Lycidias:
New magisk update 😊
[Google Pixel 6 Pro] Dragon Kumera:
Have you tried flash full factory image no modifications and try safe mode? (do not restore anything or sign into google account). Let it sit stock as bare bones as can be.
[Google Pixel 6 Pro] Dragon Kumera:
just launched my magisk app and wow hey there is an update. Where would I download an offline version? (or can I save the download from magisk app itself).
[Google Pixel 6 Pro] V0latyle:
Magisk Canary 23018

If you go to the main Magisk page, there's a small easy to miss button:

When you update from within the app, it does download the apk file to /storage/Downloads
[Google Pixel 6 Pro] roirraW "edor" ehT:
Oops, I didn't refresh and see @V0latyle's answer. LOL!

You can download Magisk Canary 23018 at Magisk Downloads on GitHub, or direct download link https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk.

Unhide the Magisk app before updating.
[Google Pixel 6 Pro] V0latyle:
Yes, Magisk Stable has not been updated with the Canary commits. Stable is still at 23000, Canary is currently at 23018. 23010+ is Zygisk and is not compatible with some pre-Zygisk modules such as those that depended on Riru.

This is why in the OP, I advise against using Magisk Stable, especially on the Pixel 6 / 6 Pro.
[Google Pixel 6 Pro] Dragon Kumera:
ya i defiantly missed it. i tried looking on github page but only saw v23.

thx!

Also I never hide magisk app so everything went smoothly
[Google Pixel 6 Pro] CPngN:
I was closing in on that decision when I decided to look up how to read logs. ("adb logcat" btw). I had to reroot and then I was able to see a couple of noisy apps in the logs, greenified being one of them as I suspected. Using su, I was able to uninstall greenify and everything has been fine since then! Today I've just been restoring all the things I disabled hoping that something would make it stable (lots of permissions to redo). Thanks all.
[Google Pixel 6 Pro] NippleSauce:
I just noticed the update and pushed it through via the app. Leaving it hidden didn't affect the update for me. Now I just gotta find the changelog =)

*Edit* - Thank you so much @V0latyle ! Quick question, but do you know if un-hiding Magisk before updating it would only be a requirement with specific modules installed and active (and depending on the Magisk changes)?
[Google Pixel 6 Pro] V0latyle:
- [Zygisk] Show warning in app UI to indicate incompatible Zygisk modules

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

Commits to 23018
[Google Pixel 6 Pro] 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 Pro] Lughnasadh:
Changelog for Stable 24 is up so just a matter of time before Stable is released.

Magisk Changelog

The Magic Mask for Android

topjohnwu.github.io
[Google Pixel 6 Pro] V0latyle:
Good catch!
[Google Pixel 6 Pro] Dragon Kumera:
nice! looking forward to finally updating my ancient pixel xl gen 1 magisk from v23 to v24.

Why do I feel like I have seen that change log a day or few ago.
[Google Pixel 6 Pro] almahix:
I don't know if it has been previously posted but something that saved me a lot of time and made it easier to root is the following link to Magisk. Scroll down the page and you,'ll find a link to download the most recent version of Magisk Canary. Unfortunately it does name the download file with the version number.

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
[Google Pixel 6 Pro] V0latyle:
Yes, this was included in the OP.
[Google Pixel 6 Pro] Lycidias:
Magisk v24.0 has been released 😊
[Google Pixel 6 Pro] 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
[Google Pixel 6 Pro] Lughnasadh:
Thanks for posting the link to the new Magisk thread. This was so needed and having an active OP is just what the doctored ordered. ipdev is the perfect person to run that thread as well, imo.
[Google Pixel 6 Pro] V0latyle:
Absolutely, I also updated the OP of all my Pixel guides.
[Google Pixel 6 Pro] sas46:
I'm on 23016, which of the 3 update way is the safest? Patching boot.img or direct?

Considering that there's no twrp I would opt for patching boot.img but correct me if I'm wrong
[Google Pixel 6 Pro] V0latyle:
Direct is best. Least chance of breaking root.
[Google Pixel 6 Pro] sas46:
Updated with direct without any issue, thank you
[Google Pixel 6 Pro] V0latyle:
Magisk Stable is now at version 24.1, so I will no longer be providing any Magisk updates.

You can use any version of Magisk now - Stable, Beta, or Canary. as long as it is 23016 or newer.

Once again, if you want to switch versions of Maagisk, it is HIGHLY RECOMMENDED that you "Complete Uninstall" within Magisk before installing the new version. Multiple instances of Magisk can break root.

If you simply want to update Magisk, the best way to do so is from within the app.

Once the February update is out, I will perform some testing with installing to inactive slot, and if it works, I will update this guide.

Given the low activity on this thread, I will probably close it if everything goes well with the next update.

Thank you all for your testing and contributions.
[Google Pixel 6 Pro] Dragon Kumera:
Thanks! Ya it been a rough ride with p6p but I am so excited these updates have been made and magisk improvements.
[Google Pixel 6 Pro] Dragon Kumera:
side note.

I noticed Verizon app tried to gain root access but was denied. (If anyone knows why this happened, please let me know).
[Google Pixel 6 Pro] Nergal di Cuthah:
If you mean "my verizon", I denied mine too. I read an article about how verizon was using the app to monitor more so i denied it. Hasn't effected the app so not sure what is wanted to do either
[Google Pixel 6 Pro] roirraW "edor" ehT:
A cheap way for them to find out your phone's rooted, even though there are probably other ways. It's either always or for a very long time done this. I haven't been with Verizon for five years and I remember it did back then too. Think of it as a quick-change artist. Minimum and cheap effort to fool ya into giving them what you probably shouldn't want to give them. :)

Or just looking for stats. :D

Anything that asks for root that I don't want it to know I have root, I have root denied to in Magisk's DenyList.
[Google Pixel 6 Pro] Nergal di Cuthah:
I think it was this and better service of advertising but can't find the article for the life of me
[Google Pixel 6 Pro] V0latyle:
Yeah, this app has always requested root for as long as I've been aware, pretty much since the beginning. Creepy af.
[Google Pixel 6 Pro] Dragon Kumera:
The weird thing is I have magisk to always grant root access yet verizon app was denied.

I made sure it was turned off in magisk app. Prob should hide it but why did it request now all of a sudden when I have had it installed for a week or 2 with it never doing it?
[Google Pixel 6 Pro] V0latyle:
Dunno. Personally, I don't use any Verizon apps on my device; I pay my VZW bill, so that's as close as a relationship I'm willing to have with them. I don't use their messaging or cloud services, and if I need to access my account I can do so through a web browser. As it is, I use a VPN almost constantly.
[Google Pixel 6 Pro] Dragon Kumera:
Ya I agree with you there. I only installed verizon app because I needed to setup google play pass from my plan. I have not used it since lol. But it's there if I need to ever go to verizon and need to login.
[Google Pixel 6 Pro] jcp2:
Got my P6P today and Following the OP instructions, was able to OTA update to Jan., unlocked bootloader and installed magisk v24.1 and I'm rooted and passing safetynet. Then I installed Franco kernel Manager and flashed Kirisakura Raven v1.5.0.zip ..... No corrupt data issue :)

PS...

I didn't touch boot verify or disable vbmeta flags. Platform Tools is v32.0.0
[Google Pixel 6 Pro] Dragon Kumera:
What does this kernal do?
[Google Pixel 6 Pro] roirraW "edor" ehT:
The OP in the thread for the kernel gives the details of features:
[Google Pixel 6 Pro] Dragon Kumera:
thx. Ya I was just looking at it and reading but seems people having issues with verify not disabled and also it does not say if system root can be modified to allow bootanimation changes.
[Google Pixel 6 Pro] Rescue9:
If I choose to update via the OTA then reflash, there is no reason to disable modules prior to update correct? Is this the case even with mods that modify SystemUI files?
[Google Pixel 6 Pro] Lughnasadh:
@Rescue9

The manner in which you choose to update should not affect whether you should disable mods beforehand. The reason for disabling mods is because they may need updating to be compatible with the new monthly build, and if they are not it could lead to a bootloop.

Therefore you should still disable any mod that modifies SystemUI, Android Framework, etc., including Substratum overlays, before updating to a new monthly build.

Then find out from the mod dev, other users, or even test yourself if you don't mind potentially getting into a bootloop, whether the mod is compatible with the new monthly build.
[Google Pixel 6 Pro] V0latyle:
Agreed with @Lughnasadh - an update will overwrite /system, so anything that modifies system files should probably be disabled before an update, just to be safe.
[Google Pixel 6 Pro] ginfest:
Hi, I got the phone , unlocked and it updated to 220105.007. Magisk 025 is installed and used to patch the boot.img

Then following this --

Install Magisk on your device.

Download the factory zip for your build.

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>

After I tried flashing the Magisk_Patched.img I got this error message--

Fastboot Error: Boot Partition is Smaller than Boot Image​

What did I do wrong? Fastboot shows device using slot a - do I need to add this to the command in Line 8?

Or should I Flash-all the whole January update as per the instructions in the first post - removing the "-w" and adding the verity lines to Flash-all.bat?
[Google Pixel 6 Pro] Lughnasadh:
What is Magisk 025? The latest Stable Magisk is 24.1 and the latest Canary Magisk is 24.102. You should be using one of those.

Also, are your Platform Tools up-to-date? The latest is 32.0.0 .

The instructions you used should work. No need to specify a slot.
[Google Pixel 6 Pro] ginfest:
Magisk Version is Canary 24.102, Platform tools are 31.02. I'll try with platform tools 32.00
[Google Pixel 6 Pro] Nergal di Cuthah:
I think they mean this
[Google Pixel 6 Pro] Lughnasadh:
Ahh... Using different nomenclature 🙃