yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] mhrussell1:
Sorry, yes BL = bootloop. I did reflash the stock image after I realized it was communicating even though List of attached devices was empty. I did the initial flash with 33.0.2 and then I loaded the latest which is 35.0.0 and used that to reflash the stock image.
[Google Pixel 6 Pro] V0latyle:
You have to use the correct program for the correct mode. ADB can only communicate with a device with active ADB - such as recovery or Android system. Fastboot is used for devices in bootloader or fastbootd mode.

When the device is in bootloader use fastboot devices, it should show up.
[Google Pixel 6 Pro] mhrussell1:
Learn something new everyday and I have been rooting for a long time
[Google Pixel 6 Pro] mhrussell1:
Big goof on my part. I pulled an old magisk patched boot image that had a similar random string at the end of the filename. Pulled the right one an viola, it works.:eek:
[Google Pixel 6 Pro] auriken:
I need a little help, I updated my p6p to the last 13 update for risingos rom (November patch) and I'm unable to root with magisk 26.4 and 27 using the instructions here. I used the Rom's boot and the stock boot and still no luck. maybe I missed a step, any ideas?
[Google Pixel 6 Pro] V0latyle:
Ask in that ROM's thread. This is for stock firmware
[Google Pixel 6 Pro] chopwell20:
Great guidebook.

one thing i am going back and forth to find is to block update/ota on rooted devices ?

may be i missed it on forum but tried my best finding it using zygisk detach app but that works for apps to detach from app store..

would be kind if someone can point me to the guide. Thanks
[Google Pixel 6 Pro] bdr127:
There's the "Automatic system updates" option you can disable in Developer Options. However, it's widely known that it doesn't seem to always work. Across various Pixel devices and Android versions, lots of people report OTAs sneaking through and getting a "reboot now to update your device"....

If that does happen, you can use the "Cancel/Reset OTA" feature in PixelFlasher before you reboot to get rid of it.
[Google Pixel 6 Pro] Lughnasadh:
👍 I also brought the subject up in the Magisk thread.
[Google Pixel 6 Pro] fil3s:
Can you downgrade? 😮 I tried downgrading my 6pro and it failed. On December with no root
[Google Pixel 6 Pro] Dataman100:
Nope, no downgrading. People have tried and got into a bootloop. You can either flash the Dec image again and keep all your files, or Factory Reset and lose everything. Either way, you're on the Dec update without root until they fix Magisk.

Wish TWRP was ready. I'd have taken an image first and then restored it as soon as I realized root wasn't working. 🙁
[Google Pixel 6 Pro] fil3s:
Yeah twrp will be awesome 😢 I had root for one day..
[Google Pixel 6 Pro] mclarence:
The latest pull request on magisk github appears to fix the issue for the december update.

You can download the newest magisk manager apk (under artifacts) from https://github.com/topjohnwu/Magisk/actions/runs/1576410350

Use app-release.apk

Re patch boot.img with the new magisk manager and flash in bootloader as per usual.
[Google Pixel 6 Pro] fil3s:
Awesome :) thanks for the info!
[Google Pixel 6 Pro] liver20:
This magisk build have to rename magisk?
[Google Pixel 6 Pro] fil3s:
Here's the update :)
[Google Pixel 6 Pro] fil3s:
No if you want to go to original source sign in and download then extract it. The apk is there
[Google Pixel 6 Pro] Project_WHaT:
Currently in the System update page of the settings app, my phone says 'Installation paused' and that it will 'continue when the device isn't being used'. I was about to go to bed and I don't have time to correctly update my phone, but I'm now worried that it'll update while I sleep and therefore lose all my data. Is it going to update and restart by itself or do I not need to worry?
[Google Pixel 6 Pro] Enddo:
am still not seeing the magisk binary installed when using this update to patch the boot.img file. it patches fine, and flashes to the boot partitions fine

but magisk manager doesn't detect the binaries are installed when I check my pixel 6
[Google Pixel 6 Pro] arjunprabhu:
also, can't hide magisk. the option "Hide the Magisk app" is disabled
[Google Pixel 6 Pro] dr_rick13:
sideloaded update and rooted. EZ PZ
[Google Pixel 6 Pro] nummer:
yep, i did that as well and everything is up and running just fine.
[Google Pixel 6 Pro] bd177:
I noticed you have Zygisk = Yes, are we supposed to have that turned on?
[Google Pixel 6 Pro] Phascinate:
As far as I understand, yes!
[Google Pixel 6 Pro] bleez99:
Working - patched boot.img with the debug apk in 65e020f646ee5b2e9803d11059d2a70c57107316 (above link) then reverted the APK and was able to hide.
[Google Pixel 6 Pro] Phascinate:
Figured out the same. At first I was unable to hide the APK but I also had another problem. Zygisk wasn't turning on at all, so I decided to just go in Magisk settings and do a Direct Install. Rebooted, and Zygisk was working.

Then I downloaded the latest Magisk Canary and was able to hide the APK and root and everything works perfectly. Even passing SafetyNet.
[Google Pixel 6 Pro] Brisky86:
Okay, so this seems like I am missing something here.

I downloaded the OTA for US Carriers (I am unlocked on Tmobile) and inside the zip folder there is not a "boot.img" like there was with the November update. I am using 12.0.0 (SQ1D.211205.017, Dec 2021, US carriers). There is not even an image folder in the zip. I have redownloaded it several times and each time it is the same.

Any suggestions? Amy I not supposed to use the US Carrier option?

Thanks.
[Google Pixel 6 Pro] bleez99:
I'm using the US carriers version.

As I understand it - the "unlabeled" version is for Canada and others.

EMEA is self explanatory.

Only speculating, but the US carrier stuff is an update to frequencies used in the US and is probably modem related.

No idea why your zip file is empty, try again...

BTW, I do full flashes, not OTA.
[Google Pixel 6] V0latyle:
⚠️⚠️⚠️

WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME,

READ THIS FIRST

!

⚠️⚠️⚠️

Official updates for this device will end October 2024.

If you are looking for my guide on a different Pixel, find it here:

Pixel 3

Pixel 3XL

Pixel 3a

Pixel 3aXL

Pixel 4

Pixel 4XL

Pixel 4a

Pixel 4a (5G)

Pixel 5

Pixel 5a

Pixel 6 Pro

For best results, use the latest stable Magisk release.

Discussion thread for migration to 24.0+.

Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.

WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.

Prerequisites:

Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!

USB Debugging enabled

Google USB Driver installed

I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.

Make sure the Command Prompt is running from your Platform Tools directory!

Android Source - Setting up a device for development

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Points of note:

The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.

While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:

"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.

"App" simply shows the version of the app itself.

If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.

If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.

Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.

Credits:

Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!
[Google Pixel 6] Tomatot-:
This is very interesting but maybe a more accurate/calm title would be better :D
[Google Pixel 6] draymond1987:
I posted in another tread but I was on November's patch but used .15's vbmeta to root (before images were available for November)

Can I just flash vbmeta with the disable flags, and not worry about a wipe?
[Google Pixel 6] lackalil:
Confirmed working using Flash Tool method coming from 015 to 036. Used Magisk Alpha 23012 to patch boot image and pass SafetyNet on checker apps. GPay still doesn't work, though. It may be identifying that verity and/or verification is disabled. I don't use it, but it's generally what I confirm the SN fix with.
[Google Pixel 6] V0latyle:
To pass SafetyNet, you have to use Universal SafetyNet Fix 2.2.0, which is currently in beta on Patreon.
[Google Pixel 6] lackalil:
Ahh, I see that in the thread now. Not a big deal for me because I don't use any apps that need it—I've just been doing it as a matter of course for a good while. Nonetheless, I'm still passing attestation with USNF 2.1.1 according to Root Checker and YASNAC.
[Google Pixel 6] schalacker:
Confirmed root working on Magisk Alpha v23001 (then reverted back to MM 23.0 to keep the old module repository links). Also updated to Nov '21 bootloader and radio at the same time. GPay stopped working for me since the Sept '21 update and all the various requirements to re-enable. I'm not that interested in GPay functionality.
[Google Pixel 6] V0latyle:
In case anyone is, GPay is working for me on my Pixel 5 with the November build. Magisk 23001 + MagiskHide + Riru + Universal SafetyNet Fix 2.1.1.
[Google Pixel 6] miss:
where can i get magiskhide, riru universal safety, thanks
[Google Pixel 6] miss:
when you receive the pixel

I update it with the latest update and then unlock booloader and root.

is this correct?
[Google Pixel 6] V0latyle:
Magisk 23001, MagiskHide is in the options

Riru is in the module repo

Universal SafetyNet Fix 2.1.1

This would probably be the best way to do it, yes.
[Google Pixel 6] sic0048:
Great write up! Thanks for putting it together.

You talk about booting the patched boot.img as an option instead of flashing it just to make sure everything is working correctly before they flash the patched file. I just want to really suggest to people that they do this anytime they are rooting after an update.

Sure it's an extra step (because you will have to flash the modified boot.img to make root permanent), but being able to simply reboot the phone if something goes wrong to get back to a working OS is priceless. You might think the odds are very low of something going wrong and causing a bootloop if you flash the boot.img before booting it, but experience has taught me this isn't the case. It's possible that there is a Magisk module that doesn't work with the update, or it's possible that user error will cause an issue (I have copied over the wrong patched boot.img from the phone before as an example). Whatever the case, if something goes wrong you will be glad you are only booting the patched boot.img file instead of flashing it!
[Google Pixel 6] vandyman:
Exactly, I was guilty of not removing a Magisk module on my P5 when installing an update. And learned the hard way.

You really never know if there is some sort of residue left from your previous setup.
[Google Pixel 6] V0latyle:
You don't actually have to flash it. If you boot the patched image and it works, you should be able to use Direct Install in Magisk to patch the image in /boot. Then, next time you reboot, the device loads that image, which should be exactly the same as what you live booted.

But yes, it's very useful to be able to test.
[Google Pixel 6] capntrips:
I was able to take the SD1A.210817.019 to SD1A.210817.036 delta OTA via System Update by restoring my boot (via Magisk) and vbmeta (via dd) partitions back to stock, then patching vbmeta in both slots (again via dd) before rebooting. No data wipe required. To simplify that process, I made a tool to patch and restore the vbmeta partitions:

Release v1.0.0-alpha01 · capntrips/VbmetaPatcher

initial commit

github.com

The process should be considered experimental until a few other people have tested it. Should anyone attempt it, I would suggest backing up any critical data.

I'm also considering making a tool to restore the stock boot backup image, in case anyone fastboot flashed, rather than doing a direct install in the Magisk app. It could also be used to download the newly installed boot image from the inactive slot after an OTA, to avoid having to download the full factory image.

Unfortunately, patching boot in the inactive slot in Magisk was disabled for Pixel devices a while back, since it caused issues with starting back up. When the December OTA comes out, I'll probably take the plunge to see if I can figure out a way to make it work.

On a related note, a fix that will allow Magisk to properly detect the current slot on Pixel 6 devices has been approved. Hopefully it'll get merged before the next mainline canary build, so we can stop using custom builds (or having to fastboot flash boot_b when on slot B).
[Google Pixel 6] KedarWolf:
So, if I use this tool after rooting OTA updates will work and I'll still have root?

Edit: And can you explain more clearly the process on how to do this?
[Google Pixel 6] capntrips:
No, the tool does nothing to maintain root. It simply allows you to take the OTA. You will still need to reboot into fastboot and flash or boot from a patched boot image.

The steps would be:

Restore boot in the Magisk app

Restore vbmeta in Vbmeta Patcher

Take the OTA in System Updater

Patch vbmeta in Vbmeta Patcher

Patch the new boot image in the Magisk app and copy it to your computer

Reboot into fastboot

Boot from the new patched boot image

Direct Install Magisk in the Magisk App

As I noted the quote post, this process should be considered experimental until it has been more thoroughly tested. You should consider backing up any critical data before attempting it, in case something goes wrong.

I'm working on another tool to make it a bit easier to acquire the new boot image in step 5, but that will likely be a few days. Hopefully we'll be able to install Magisk to the inactive slot on Pixel devices again in the future, which would consolidate steps 5-8.
[Google Pixel 6] V0latyle:
Patch vbmeta how? What does patching the image accomplish?

This is good news. Would the same thing be accomplished by flashing the boot image to both slots using --slot=all?
[Google Pixel 6] dadoc04:
did the flash tool make you wipe when disabling verity and verification? I noticed it allows you to uncheck the wipe device option.... just curious thx
[Google Pixel 6] lackalil:
If the build you're currently on has verity and verification disabled, you don't have to wipe when you update using the flash tool.

I haven't tried it without wiping from unrooted/stock vbmeta. It could well be possible despite a wipe being required when flashing using adb.
[Google Pixel 6] scepz:
Was thinking of switching to a pixel 6 from a s20. Both on Xfinity Mobile (Verizon parent company). I've heard pixels were good for unlocking but would this still apply to Verizon pixels?
[Google Pixel 6] bobbarker2:
@V0latyle I've had the same config as yours in OP for passing safetynet. Now it's passing safetynet but no IAPs work and device is not certified in play store.. I don't understand it. No other modules than USNF and Magiskhide Props.

I'm on November firmware, have done complete flash without erasing /data and still same result.

Do you have any specific config for Magiskhide Props?

I also have a problem where my denylist hides system apps by default and when I reboot, Google play services is no longer selected in the denylist.
[Google Pixel 6] V0latyle:
I don't have any other settings. Please note I'm on the Pixel 5, and also on the December release.

I believe USNF disables some of the DenyList settings automatically.
[Google Pixel 6] bobbarker2:
USNF removes com.google.android.gms otherwise zygote won't work according to notes in the source. Thanks for the tip. Passing safetynet again by deselecting it and reboot.

P5 vs P6 shouldn't matter since it's the same protection scheme but who knows.

I'm waiting til the late January release for P6 since the December one broke the radio, Wi-Fi calling and more. So going to sit on November till then.
[Google Pixel 6] V0latyle:
Well, you -should- be able to run the December system update on the November baseband. It will take a bit of doing because to update system you have to have the latest baseband, so you'd have to downgrade baseband after updating system.

Also, there are 4 different basebands to choose from.
[Google Pixel 6] bobbarker2:
Yes it can be done but I rather just wait until everything is on the same version. Especially now that I have a working device. Turns out after I stopped messing with the denylist and gms, everything fell into place... NFC payments work, safteynet passes, etc. Thanks again for the tip. And thanks to kdrag0n for writing USNF!
[Google Pixel 6] tensux:
this is my first pixel phone. I was able to get it rooted pretty easily as the steps were similar to others. I can't seem to be able to get magisk hide option to show up under superuser. Can anyone point me in the right direction?

one item that was different for my phone was that is that it has an A/B partition so the directions in the OP would not work. I needed to use the following commands:

fastboot flash boot_a patched_boot.img

fastboot flash boot_b patched_boot.img

can anyone explain the significance in this difference? I bought the phone used on ebay.

thanks
[Google Pixel 6] V0latyle:
MagiskHide has been deprecated for DenyList as of Magisk 23010. It's under Magisk settings and is only available with Zygisk enabled.

All Pixels have A/B partitions; flashing the slots separately is not necessary, but if you want, you can use --slot=all to flash both slots of /boot.

What device are you using? This forum is specifically for the Pixel 6.
[Google Pixel 6] tensux:
thank you. I just found the denylist setup. I will use it for my banking apps.

I am using a pixel 6. I believe its the global version.

it passes safetynet and had DMR L1, but I had to install several apps like Netflix and Hulu from mirror apk. I haven't had to do that in a long time on other phones and tablets I am currently using.

I was tempted to try using lygisk which I do use on another device. Unless you can recommend another solution?
[Google Pixel 6] V0latyle:
I've been using DenyList on Google Play Store. My device passes and I'm not blocked from installing any apps.
[Google Pixel 6] tensux:
thanks i will try that
[Google Pixel 6] deusfaux:
thanks to the OP for the OP, but also it could be improved by not direct linking to Magisk Canary, instead link to the github page it is from, as that's placing a little too much faith in a stranger on a forum to link to the right file directly.

And also linking to the github page for USNF would be helpful.

instructions for unlocking the bootloader like the sticky thread for so many past pixels would also be appreciated. Yes, this is XDA, but plenty of noobs come wandering in here and it doesn't hurt to not skip key steps in getting their phone to the state they'd like.

edit:

this emotionally weak user and the mods that are buddy buddy with him are a joke. deleting replies wholesale to manipulate the way the dialogue appears to others. take the criticism and stop trying to own this microcosm of a digital space like it's key to your existence:

"deusfaux also said:

The point is one should direct people to trust that button, not any direct link off a forum. Best practices.

It's not a dev's *process*, it's a community how-to guide. Any every past Nexus and Pixel de facto guide to root also included how to unlock the bootloader.

At a minimum linking to an existing guide on XDA for doing that on another phone, thereby demonstrating it's the same process as for a Pixel 6, goes a long way and costs you next to nothing."
[Google Pixel 6] V0latyle:
No - Magisk Canary is REQUIRED for Android 12. Since a specific file is required, I linked Canary directly. The link I used is the same target as the Canary button on the Magisk GitHub page.

Done, but this is not a guide for passing SafetyNet - this is only a guide for root.

Again, this is only a guide for root. That's it. An unlocked bootloader is a prerequisite, as per the OP. It is the user's responsibility to ensure they have the necessary knowledge, information, and tools to follow these instructions. Anyone who does not should not attempt this - again, per the OP.

Ideas for improvements or simplifications are welcome, but you aren't going to get very far telling developers and contributors they should modify their process to accommodate your own preferences.
[Google Pixel 6] Goem:
I was getting the same error as @khatidaal, FAILED (remote: partition (boot) not found). Make sure to place t he master root image into the same folder as the platform tools
[Google Pixel 6] sic0048:
No. As a general rule, Verizon permanently locks all their bootloaders. It doesn't matter what the manufacturer does. So while Google offers Pixel models with unlocked bootloaders, the Verizon variants will be permanently locked.

The good news is that you can use the unlocked version on the Verizon network. That model doesn't have mmWave 5G like the Verizon model has, but Verizon and AT&T are moving away from that technology and it isn't going to ever be their primary mode for 5G.
[Google Pixel 6] V0latyle:
That should not matter. What causes this problem is usually platform tools being out of date. You can send a file from anywhere on your PC; you just type the command then drag and drop the file into the command window instead of naming the file explicitly.

I believe as long as you buy the US unlocked model, it still supports mmWave 5G. Just make sure you're using the US carrier firmware as the international basebands do not support mmWave.

I have an unlocked P5 that I'm using on Verizon; I haven't yet gone into downtown to see if mmWave works.
[Google Pixel 6] co9:
Sorry for the stupid question. But where can i download the december image as it isn't available anymore?
[Google Pixel 6] V0latyle:
You should be able to downgrade to November without a problem. I see that both December and January have been pulled.

Otherwise someone who already downloaded the file is going to have to host it.
[Google Pixel 6] Slim2none4u:
December Image For Pixel 6. Give 20 minutes for upload.

Dropbox - File Deleted - Simplify your life

www.dropbox.com
[Google Pixel 6] co9:
Edit: Solved
[Google Pixel 6] co9:
Thank you very much
[Google Pixel 6] Koehlix:
Any chance to get SQ1D.211205.016.A4 as a download?
[Google Pixel 6] MattP410:
I'm showing that I have an update available, but there's an installation problem. Do I need to remove the master boot.img before I can update via OTA?
[Google Pixel 6] V0latyle:
Shouldn't have to. Automatic OTA doesn't work properly when rooted. You can either:

Keep trying until it succeeds, might take 2-3 attempts

Restore the stock boot image then take OTA

Sideload the OTA (instructions in OP)

Dirty flash the factory image (instructions in OP)
[Google Pixel 6] MattP410:
Okay, thanks. Looks like my best bet will be to restore the stock boot image. Do I need to do that from fastboot, or can I just remove the patched image via Magisk? The option is there, but will that leave me without a boot.img?