yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] cc_net:
Get new pixel 6 and OTA to 12.0.0 (SQ1D.220205.004, Feb 2022), then unlock bootloader.

Root steps:

1. install Magisk-v24.0

2. download 12.0.0 (SQ1D.220205.004, Feb 2022) rom and get the boot.img

3. convert boot.img to master root.img with magisk

4. flash master root.img

5. reboot

Device show "Your Device is corrupted and cannot be trusted" and stuck at "google" same with #498 . Then i can only flash the factory rom again.

need to execute first?

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
[Google Pixel 6] V0latyle:
Disabling verity/verification is not necessary. I'm not sure what's going wrong here.

Try the January update and see what happens.

Failing that, see if an older version of Magisk works, like Canary 23016.
[Google Pixel 6] capntrips:
It's interesting that you're running into similar issues to the people that have the failed OTAs, I wonder if there is some inconsistency with the way Magisk marks the boot partition's internal vbmeta image.

If you fastboot boot magisk_patched.img over stock, rather than fastboot flash, does it boot and give you (temporary) root?
[Google Pixel 6] vandyman:
LOL.. I was going to post the same thing.

fastboot flash magisk_patched.img

Then direct install via Magisk.

At least that was the way to root the P6 when it came out in Oct. 2021.
[Google Pixel 6] V0latyle:
This may also be a Pixel 6 / Pro specific issue. I just updated to March on my P5 and wife's P5a by manually patching the boot images in Canary 24102, and have had zero issues.
[Google Pixel 6] Yavia:
hello everyone, I was rooted on the 12L beta and decided to update to the new march beta and attempted to root it with the automatic ota root method here. Somehow that managed to bootloop my phone and after messing around a lot I made my phone say it was corrupt and could no longer boot. I eventually managed to fix it and root the march beta without any data loss but now every time I boot my phone there is a warning that the device is corrupt. anyone have any idea on how I can get rid of this message?
[Google Pixel 6] Lughnasadh:
Usually a factory reset/wiping data is needed to get rid of that warning message. I think last month when a few people who had that message updated to the February update the message was removed so possibly updating next time might do it as well.
[Google Pixel 6] V0latyle:
Are you talking about the red EIO screen that has replaced the orange Unlocked screen?
[Google Pixel 6] Yavia:
I get this followed by the usual bootloader unlocked warning and then my phone boots perfectly fine
[Google Pixel 6] V0latyle:
Means there's dm-verity corruption. Android Boot Flow Not sure exactly what needs to be done to fix it; the device will still boot and run without an issue, this just means that there was an issue verifying the integrity of the boot image; it could be the boot image itself, or it could be something with the vbmeta partition. I did get this error on my wife's 5a after applying the February update; sideloading the OTA fixed it.
[Google Pixel 6] Yavia:
so should I attempt to sideload the same version I already have installed or just wait until next month and hope it resolves on it's own
[Google Pixel 6] V0latyle:
Same version.
[Google Pixel 6] Newrooter22:
Hi everyone, was advised to post under one of the guides.

Has anyone got a patched boot.img for SQ1D.220205.004. the one Magisk is giving me just doesn't seem to work.

I've tried different versions of Magisk, renaming the patched boot.img like mentioned above but still doesn't work.

Wanting to try a patched img that works for someone else before I just have to revert back to Jan update thus factory reset.

Thanks in advanced for any help 👍👍
[Google Pixel 6] capntrips:
I attached the boot.img image from SQ1D.220205.004 patched with Magisk 24301.

Care to elaborate on what exactly doesn't work?
[Google Pixel 6] cc_net:
I had flashed SQ1D.220105.007 and patch the boot.img with 24200. It works fine.

So what should i do if i want to update to the SQ1D.220205.004 ?

If i update OTA automatic without Uninstall magisk ,what will happen ?
[Google Pixel 6] capntrips:
The updater will display an error message and the update will not be applied. System Update uses delta OTAs, so it does a hash check of all of the partitions in the active slot, and the modified boot partition will not match the expected hash.
[Google Pixel 6] V0latyle:
It will probably fail to update. As it is, the automatic OTA method doesn't seem to be working for everyone. My wife's Pixel 5a refused to install the update, and my Pixel 5 stubbornly insisted an update wasn't available.

My recommended and preferred method of update is to dirty flash the factory image. I did this on both phones with absolutely no problems.
[Google Pixel 6] Newrooter22:
Thanks I'll check it out tonight, basically every time I patched the stock boot.img using Magisk then flash it, the phone just goes into a bootloop.

The phone is fine again when I flash the stock boot.img. So I'm guessing it's either something going wrong when Magisk is doing it's thing or it might be a case of me having to go back to the Jan update and going from there.

But hopefully that file you attached will do the trick 👍
[Google Pixel 6] V0latyle:
It's entirely possible that Google broke something with the latest update. This happened back in December, too - whereas Canary 23015 incorporated the fixes for the boot image header, 23016 addressed an fstab issue.
[Google Pixel 6] V0latyle:
For those of you having boot loops after updating, try disabling Magisk modules. You can do this through adb while booting the patched image (even if it bootloops)

adb wait-for-device shell magisk --remove-modules

Some updates break Magisk modules, so it's important to be aware of this. I personally only use Systemless Hosts, Universal SafetyNet Fix, and MagiskHide Props Config, and have never had issues with a bootloop after updating.
[Google Pixel 6] gazdajezda:
Ok, did you disable those modules when updating?
[Google Pixel 6] V0latyle:
No. None of them change system as far as I know.

As a general rule of thumb it's probably a good idea to always disable them, because it's hard to really say which ones might cause problems.
[Google Pixel 6] stabip:
I uninstalled Magisk (Retore images), OTA, reboot to inactive and it boots in fastboot.

Is this fastboot "loop" what you mention?

should I try the adb command?
[Google Pixel 6] V0latyle:
Bootloop in this context generally means a looping pattern - as in, the device loads the boot image (Google logo), but fails and restarts and loads it again. Sometimes this happens endlessly, but with most modern devices, two failed boots will result in the device going into Rescue Party, the fastboot screen where you get the corrupted message. You should not get stuck in bootloader.

Did you have any Magisk modules installed? If yes, you can try the ADB command while trying to boot; you can either hold down the power button until your device restarts, or you can select Try Again in the Rescue Party screen.

For everyone else who's reading, please specify what Magisk modules you had installed, and which ones did not cause a bootloop when not disabled. For my Pixel 5, I have had no issues with Systemless Hosts, MagiskHIde Props Config, and Universal SafetyNet Fix.
[Google Pixel 6] stabip:
So I rooted again by creating a new img patched from the last 12.0.0 (SQ1D.220205.004, Feb 2022).

No the phone reboots and stucks at the google logo, without loops.

I tried the , "adb wait-for-device shell magisk --remove-modules " , by restaring the phone and it hangs at " * daemon started successfully "
[Google Pixel 6] V0latyle:
You probably didn't have the ADB server running.

Boot your device into bootloader

In your ADB terminal, type fastboot devices, you should see your device with its ADB ID

Now, in ADB terminal, type adb wait-for-device shell magisk --remove-modules

Select Start on the bootloader screen (Volume up/down to change option, Power to select)

When your device boots the kernel (Google logo) the ADB terminal should show activity.
[Google Pixel 6] stabip:
Everything ok until step 4

Then a message appears your system is corrupt and again the google logo
[Google Pixel 6] stabip:
I fastboot flash boot the patched magisk again

Now I am in a google logo loop

Still I followed the steps and the terminal does not seem to respond, althought I see my ADB ID
[Google Pixel 6] V0latyle:
Flash the unpatched boot image, but you won't have root
[Google Pixel 6] V0latyle:
For those of you running custom kernels: DO NOT attempt to update via OTA, and DO NOT try to reflash the custom kernel after OTA.

The best way to update while running a custom kernel is by dirty flashing the factory image. The OTA process checks to make sure the kernel matches the system; a custom kernel won't match, and you'll get the corrupted error.
[Google Pixel 6] stabip:
This is eventually what I kind of did, but with flash-all.bat removing -w. My data and apps everything saved :)

I messed up with boot.img files, flashed the wrong one therefor I got the loops and problems. Now understood how this all work and patched again the boot.img from calyxos version which is already installed on the phone and it's rooted again.
[Google Pixel 6] torsti:
Update is available :)
[Google Pixel 6] V0latyle:
Don't forget to check your Magisk modules before updating. Also, if you're running a custom kernel, make sure you restore the stock kernel before updating.
[Google Pixel 6] sakerhetz:
Does magisk work on march 2022 android 12.1 update?? mine is stucked in bootloop.
[Google Pixel 6] torsti:
After installing the update, I installed magisk on 2nd partition. Phone bootet correctly, but now I have lost root. Magisk allows only patching file
[Google Pixel 6] sakerhetz:
We have to wait for the updated version of magisk i assume.
[Google Pixel 6] TheTabbingMan:
I was able to successfully install magisk on march 12.1 using the direct install method

Edit: and the Magisk version is 24.3
[Google Pixel 6] Lughnasadh:
Yes, but would recommend either using the Stable version or Canary 24301. Canary 24302+ is causing bootloops on some custom kernels. Also, Canary 24304 is not playing nice with several mods and causing bootloops.
[Google Pixel 6] kornball:
Probably a stupid question, but if my Magisk manager is on 24304, any idea how I patch boot.img using the previous stable version or Canary 24301?
[Google Pixel 6] badabing2003:
I understand why you might see it that way, and am sorry you felt that way, I was just trying to help out a fellow xda member.

It would be a promotion if I had anything to gain from it, it's an open source tool, to give back a little to the community that has given me a lot over the years.

Please delete the post, it looks like I can't delete it (don't know why).
[Google Pixel 6] Lughnasadh:
Uninstall Magisk Manager app and then install either the Stable version or the Canary 24301 version of the app, then patch. Conversely, you can just do a direct install after downgrading the Magisk Manager app.
[Google Pixel 6] tom1807:
Didn't work for me, installed the March update, after "Restore Images" in Magisk 24.3, installed the update, went Magisk selected "Install to inactive slot", rebooted, showed the bootlogo and then stuck at Fastboot Mode. that happened 2 times, then it rebooted and the system stayed on February update. Magisk says, not installed (not surprising, because probably boot from the other slot) but seems something is has been changed that I can't root the Pixel with Magisk 24.3 (Stable) and Android 12.1 on the Pixel 6.

Cheers

Tom
[Google Pixel 6] Lughnasadh:
Since you are having problems, I would suggest using Android Flash Tool to update to March.

Not sure what you mean by "can't root". You boot up and it's not rooted? You get into a bootloop after flashing the patched image? You can't patch the boot image?
[Google Pixel 6] tom1807:
I meant as conclusion that there is a problem with P6 March Update and Magisk 24.3 Stable, that it can't be rooted.

Because the February update and previous worked fine. In fact, back to February update and back to rooted after patching the boot image file

Cheers

Tom
[Google Pixel 6] Lughnasadh:
Hmm, I'm rooted fine on the March update using Canary 24301, which is the same as Stable 24.3.
[Google Pixel 6] airtower:
Not true. March and 24.3 stable working fine here after factory image flash. OTA has never worked for me.
[Google Pixel 6] capntrips:
I was unable to take the March OTA with Magisk 24304. I ended up at the red corrupt verity screen, but after one bootloop, it rolled back to the previous slot on the Feb update. After allowing it to install the March update without root, I was able to fastboot boot and direct install Magisk 24304. I had previously been able to take all of the OTAs since Magisk 23017.
[Google Pixel 6] bilrage:
I got difficulties to reactivate some module after the update, what's the folder to delete their cache? In exemple there was lawnchair that i can't use anymore, everytime i activate it my screen keep blinking till i reboot... :S
[Google Pixel 6] nutzfreelance:
i have no devices listed in fastboot when i "adb devices", but i do in android.. what is going on?

custom kernel? ( blu spark) maybe?

(bootloader is unlocked, usb debegging is on, tried many reboots etc)
[Google Pixel 6] Lughnasadh:
If you are in fastboot, use "fastboot devices".
[Google Pixel 6] V0latyle:
I recommend updating via dirty flash factory image. It's the safest way so far.

For Magisk support, please post in the Magisk General Support thread.

I'm not sure what you mean "I do in Android" but you probably don't have the fastboot USB driver installed. See OP.
[Google Pixel 6] nutzfreelance:
dont know how i forgot that.

im going to have to read the manual one day... or stop drinking.

thank you.
[Google Pixel 6] biglo:
I sideloaded the OTA and wasn't able to root afterwards. I then went and updated again using the factory image and rebooting but once again I was unable to root. I patched the boot .img file and fastboot boot patched.img and it just boorup and restarted.
[Google Pixel 6] Lughnasadh:
Did you disable your mods before rooting? What version of Magisk? Don't use Canary 24304. It's causing problems with some mods.
[Google Pixel 6] V0latyle:
Life is a waste of time,

Time is a waste of life.

Get wasted all the time,

And you'll have the time of your life!
[Google Pixel 6] tom1807:
Yeah, used the Android Flash Tool and rooted then. Works fine.

Nice side effect, it's faster than OTA and then waiting for "Optimize device"

Cheers

Tom
[Google Pixel 6] Lughnasadh:
Yeah, you'll save an hour of your life that way 🙃

Glad everything is good 👍
[Google Pixel 6] biglo:
You know what, I think I forgot to uninstall magisk after it failed to uninstall the first time before running the updates. I didn't disable anything 🤦🏽‍♂️. We so impatient to get rid of these annoying bugs. Looks like I got a factory restore coming my way.
[Google Pixel 6] andreipaval:
How to downgrade Magisk from 24304 to 24301 without losing my DenyList ?
[Google Pixel 6] capntrips:
DenyList is kept in a table in /data/adb/magisk.db, so as long as you don't do a Complete Uninstall with the Uninstall Magisk button within the app, you won't lose it. To downgrade, just uninstall the newer Magisk app like you would any other app, then install the downgraded version. You'll want to Direct Install the downgraded Magisk to your boot partition, as well.
[Google Pixel 6] devilsshadow:
Hey folks, was too stupid to read the comments in this thread before flashing, so I followed the OTA root steps in the OP, uninstalled magisk, disabled modules, downloaded the OTA and now I'm stuck in fastboot. What should I do as to avoid data loss if possible? Will I lose root if I dirtyflash using the android flash tool? Can I root again if I dirtyflash without losing data? Any help would be appreciated, thanks! PS, was on the latest magisk stable.
[Google Pixel 6] capntrips:
Uncheck all of the boxes before clicking Install Build, and the flash tool won't wipe your data. After that, fastboot boot with the patched boot image then Direct Install in the Magisk app.
[Google Pixel 6] devilsshadow:
Hey! Thanks for the quick reply! For some reason the android flash tool refused to detect my phone after it went into fastboot mode, so I ended up using the pixel flasher application.

Downloaded the Pixel 6 — SP2A.220305.013.A3 — Global Factory Image

Downloaded Platform Tools

Selected "Patch boot.img"

Selected "Keep Data"

Hit "Flash Pixel Phone"

app did it all by itself, I'm now updated, rooted again and all data intact

Hopefully I can just do future OTA's regularly via the OTA instructions in the OP while retaining root.
[Google Pixel 6] rbouza1:
Which magisk is working ? 24.3 will boot rooted but when I flip modules on and reboot it bootloops.
[Google Pixel 6] devilsshadow:
My google pay says "not set up" above every card after the update. Anyone else with this issue?
[Google Pixel 6] capntrips:
same here

Edit: Nvm, I did have a warning about my device no longer being up to security standards, but when I went to actually use a card, it worked.
[Google Pixel 6] Velcorn:
Make sure modules are comptaible, f.e., Pixel Addon Features and afaik Font Manager are not - install bootloop protection module and it'll automatically disable the incompatible one upon bootloop.
[Google Pixel 6] devilsshadow:
Could be just a visual bug, as when using the lockscreen shortcut then unlocking the phone, the message says "hold to reader".

Tried clearing app cache, uninstalling, reinstalling, hiding root via magisk from google pay then launching the app again (with device restarts inbetween) but it still says "not set up" when entering the gpay app itself. Very weird.

EDIT: just saw your edit, thanks for the update!
[Google Pixel 6] rbouza1:
Yeah pretty sure the systemless hosts or the right clock module are to blame. Never heard of the bootloop protection module .
[Google Pixel 6] phaino00:
Both Font Manager and Systemless Hosts modules are working fine for me. I'm using 24.3 stable magisk.
[Google Pixel 6] rbouza1:
So im gonna boot flash magisk and try just systemless first. If It works I'll flash it. Tulsadiver always updates his packages for monthly so I'll wait for clock mod, and I'll try the bootloop module for future.
[Google Pixel 6] pa.pn2:
I also patched with latest beta magisk the march kernel.

Flashed the factory image without -w, but when i flash the patched kernel im aslo stucked in bootloop.

Even just booting the patched kernel caused a bootloop

Flashing stock kernel, works, how can i remove all modules? i have no root now...

how am i able to enter magisk save mode without modules loaded
[Google Pixel 6] V0latyle:
One of your modules is the problem. Use the Magisk General Support/Discussion thread for Magisk support.

Odd bug that does seem to happen from time to time. Does not seem to affect NFC.

It's not Systemless Hosts. I use that module with no issues. Modules that alter system, such as those that change UI, are most likely to cause problems.

When booting the patched image, use this command:

adb wait-for-device shell magisk --remove-modules
[Google Pixel 6] pa.pn2:
ok that did the trick, now we have to check each module which causes the bootloop....

systemless host is working for me,als safetynetfix 2.2.1

i had viper, substratum and a font installed, so i guess it might be one of these

edit:substratum and the font module work both
[Google Pixel 6] V0latyle:
I can confirm that Systemless Hosts, Universal SafetyNet Fix, and MagiskHide Props Config are all safe.
[Google Pixel 6] pa.pn2:
i also had busybox as module, did someone tested this?
[Google Pixel 6] badabing2003:
Magisk 24304 canary

With the following modules,

No issues to report.

Axet's call recorder

Built-in BusyBox

SQlite for arm

Systemless hosts

Universal safetynet fix
[Google Pixel 6] devilsshadow:
Hey man, used your pixelflasher software to get me out of a bind when I ran into a bootloop. Thank you for your work!

And just to add to the conversation, only had systemless hosts and universal safetynet fix as enabled modules.

I did have the volte fix module installed too but I disabled it before completing the OTA.

Using magisk 24.3 stable.
[Google Pixel 6] catseyenu:
May I ask what/where is this "bootloop module"?
[Google Pixel 6] rbouza1:
Another user mentioned it to me
[Google Pixel 6] Ens0:
I didn't relock it hehe I was desperate in getting over the bootloop that's why lol. I got it back though to root on latest update
[Google Pixel 6] Aulgreg38:
N

O it bootloop u into recovery which requires a factory rest to boot
[Google Pixel 6] Aulgreg38:
O

Nice unlocked the bootloader stays unlocked as long as u sideload the OTA ur good😁
[Google Pixel 6] Aulgreg38:
But in order to receive OTA from Google bootloader must be locked
[Google Pixel 6] capntrips:
The bootloader doesn't need to be locked. Assuming you mean the delta OTA via System Update, the partitions of the active slot simply need to be stock when the system checks the hash during installation.
[Google Pixel 6] Aulgreg38:
Ok Ic gotchya thanks
[Google Pixel 6] RadioActivPngwn:
This thread's title should really be updated to say "ROOT USERS:"... there's been some chatter that looks like it's referring to the standard updates.
[Google Pixel 6] V0latyle:
I would recommend you do not sideload the OTA to update. Dirty flash the factory image using Android Flash Tool.

Or, if you absolutely have to do things yourself, dirty flash the factory image via ADB.

Good idea, I'll change the title.
[Google Pixel 6] Ntress:
So if I'm on .036 build rooted and want to update to 0.37

will my data got wiped after I update ?
[Google Pixel 6] t-ryder:
LINK
[Google Pixel 6] V0latyle:
No, as long as you follow the directions to the letter.
[Google Pixel 6] t-ryder:
I tinkered a bit and made some wrapped updater script for Windows. Makes the update process of the Pixel 6 a bit more convenient ... I made it just for fun. It's pretty self explanatory, but there's a how-to included anyway.

EDIT: Updater outdated, will update 0riole_Flasher soon

>>>UPDATES<<<
[Google Pixel 6] cbomb1337:
I followed the Android flash tool method in page 1 thanks. I didn't use the same flash code though for flashing magisk patches boot img to the phone. I think I just did fastboot flash boot magiskxxxxxxx.img. It worked out. Wonder why the OP says to flash all slots.
[Google Pixel 6] t-ryder:
Updated post #52 ... new version
[Google Pixel 6] t-ryder:
I guess because the online flash tool flashes both slots, so you flash the Magisk patched boot image to both slots too.
[Google Pixel 6] norman00037:
So to sum up for newbie:

1. Flash stock boot.img got from image.zip

2. Reboot bootloader and flash stock radio.img from image.zip

3. Boot system, run Magisk, patch boot.img

4. Flash patched boot.img

Is that correct sir?
[Google Pixel 6] t-ryder:
Wait. December update destroys root.

Maybe if root is fixed just use my updater from post #52 ...
[Google Pixel 6] norman00037:
Im holding my breath now...
[Google Pixel 6] t-ryder:
To answer your question;

1. Flash latest stock bootloader and radio image from the factory image package (reboot bootloader between flashing)

2. Flash latest image ZIP from the factory image package using the correct flags so your device does not get a wipe

3. Boot system, run magisk and patch the stock boot image from the image ZIP

4. Reboot to bootloader and flash the patched boot image

My little updater does exactly that but automated if you gave it the needed files as shown in the screenshot (post #52). The only thing different is that the boot image has to be patched first (and renamed + copied like the other files) by the user before starting the process.
[Google Pixel 6] chuppito:
MThank you I test it as soon as I update. Apparently there is a fix for MagiskThank you I test it as soon as I update. Apparently there is a fix for Magisk
[Google Pixel 6] catseyenu:
Have you found it?
[Google Pixel 6] TheTabbingMan:
I got it on Fox's Magisk Module Manager