yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] vaindil:
I flashed with the Android Flash Tool like I always have, had to manually re-root boot.img after that. I used Magisk 24.3, tried both stable and the latest canary, but I'm still getting a bootloop. I can flash the non-root image and boot just fine, but the rooted image bootloops. The command provided above to force disable modules just makes the device crash immediately rather than waiting, and it doesn't fix the problem.

Anyone know if I just need to wait for Magisk to update, or is there some other way of disabling modules if that's actually my problem? Looks like the commenter before me reinstalled a Magisk module somehow, which I can't do because that tab in Magisk is not available unless you're rooted, so I'm not sure where to go from here.
[Google Pixel 6 Pro] jcp2:
Boot into safe mode. That will disable all the magisk modules. Odds are one of your modules is causing the bootloop.
[Google Pixel 6 Pro] vaindil:
How do I do this? I've been searching and can't find a way. It's bootlooping, so I can't tell it to reboot into safe mode from the UI, and there doesn't seem to be a way of doing it from adb or fastboot. I flashed a standard boot.img so I could access the UI, then rebooted into safe mode, then rebooted and flashed the Magisk patched boot.img again, but I'm still bootlooping.
[Google Pixel 6 Pro] jcp2:
Sorry, IDK what else for you to do. Hopefully someone else will be able to help you out. For now, just use your phone unrooted.
[Google Pixel 6 Pro] vaindil:
Okay, I manged to get into safe mode, and that seems to have properly disabled the modules, thank you! To get into safe mode, turn the phone off or restart it, then press and hold volume down the moment you see the logo appear. (It's described everywhere as "when the animation starts", but it's actually as soon as the logo appears, not once it starts animating.)
[Google Pixel 6 Pro] V0latyle:
Great question for the Magisk Discussion/Support Thread
[Google Pixel 6 Pro] pavelcheto:
Has anyone rooted the march update successfully? What version of the app are you using? I tried Magisk Stable and Canary and when I try to boot the patched image, the phone restarts. Then boots without root and runs normally.
[Google Pixel 6 Pro] krystiano:
I'm. 🤪

Magisk stable 24300

And lastest SDK.

Previous one not working for me to flash

(Latest r33.0.1)
[Google Pixel 6 Pro] roirraW "edor" ehT:
Ditto. Magisk Stable 24.3.
[Google Pixel 6 Pro] wezmeister17:
Same happened to me, I thought I did something wrong
[Google Pixel 6 Pro] pavelcheto:
So I managed to fix it by removing all magisk modules and creating a boot.img with Stable 24.3. In my case it was the module Addon Features for Pixel Devices.
[Google Pixel 6 Pro] Lughnasadh:
You likely have a module that is causing this.

EDIT: See you already found that out 👍
[Google Pixel 6 Pro] maverixz:
I have had the same problem since day one that the March update was released and used the canary and latest Magisk so it seems as you have said it is a module. How do i remove the module when I am not rooted as currently the modules button is grayed out
[Google Pixel 6 Pro] V0latyle:
Flash the patched image, but don't boot your device yet.

In your ADB terminal, type adb wait-for-device shell magisk --remove-modules

Now, select Continue in bootloader. As soon as the kernel starts, this command will disable all Magisk modules.
[Google Pixel 6 Pro] dilligaf56:
Just installed the March factory image. All went smoothly, but I had to create a new patched boot.img with the updated Magisk and flash it back - after the initial image.zip flash, booting with my old master-root.img did not give me root. All good now! Thanks very much for this guide!

Edit: By the way, the new image seems to have fixed the annoying issue I had previously with strong Wi-Fi causing the carrier's signal to drop. Have had both on all afternoon with no problems. And yes, the fingerprint sensor works a LOT better.
[Google Pixel 6 Pro] maverixz:
Thank you very much.
[Google Pixel 6 Pro] fil3s:
Hi

I just ran into into an issue with magisk on my p6pro. I have a feeling Google may make the rooting process a bit harder in the near future

I was rooted on a13 DP2 and I tried to fire up fox magisk module manager, it said I had no root. The magisk app said root N/A

I still had the option to direct install but the above error came up in magisk. Fixed it by flashing patched canary magisk in fastboot

fastboot flash boot /path_to_magisk.img

Just thought I'd raise it here for reference. Seems a lot of peoples root isn't working -_-
[Google Pixel 6 Pro] V0latyle:
Google doesn't really have any motive for making rooting harder. Most of the issues being had are incidental. If they wanted to prevent root, they would simply make it impossible to unlock the bootloader.
[Google Pixel 6 Pro] fil3s:
Yeah makes sense. If they didn't let ppl unlock bootloader and root their phones, what's the point of OEM unlock in dev options etc. 😆
[Google Pixel 6 Pro] herman1523:
So i followed all the steps, except when after patching the boot.img, i didn't rename it to 'master root.img'. I used the command to flash the img as it was named after the patch.

after the flash was complete I rebooted the device it went into a bootloop. So I thought I ****ed up by not renaming the file. I reflashed the image again, except this time I named the image master root.img like the instructions said. I thought this would fix the bootloop but it didn't.

to make matters even worse, now my device isn't being detected when I run the adb devices command

please help
[Google Pixel 6 Pro] V0latyle:
The name of the image doesn't matter. As has been discussed several times in the last few pages, the likely cause of boot loops is a Magisk module.

Again, the name of the image does not matter. You probably have a Magisk module causing the bootloop. You can remove modules with this command:

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

Then, boot your device.

ADB can't see the device in bootloader mode. This is not a problem. While in bootloader, you'd need fastboot devices. From your terminal readout above, platform tools does indeed see your device.
[Google Pixel 6 Pro] Markelijk:
So, i was wondering. I unlocked my bootloader and flashed the update via fastboot with the verity and verification disabled (not rooted yet but plan to do so). Is there a way to check if my verity and verification are indeed disabled? Is that displayed in the bootloader status or something?
[Google Pixel 6 Pro] Burt Squirtz:
I flashed this, and now my phone is so much smoother and snappier. Thanks so much Bangalore!
[Google Pixel 6 Pro] mko000:
What did you flash?
[Google Pixel 6 Pro] Ghisy:
Alright, I'm rooted! I did get the "corrupted" error but wiped again (phone has no data as of now anyway) and boom! Thanks!
[Google Pixel 6 Pro] ginfest:
When I do this step, it won't flash the update?

F:\platform-tools>fastboot --disable-verity --disable-verification F:\platform-tools\image-raven-sd1a.210817.036.a8.zip

unknown partition 'F:\platform-tools\image-raven-sd1a.210817.036.a8.zip'

fastboot: error: cannot determine image filename for 'F:\platform-tools\image-raven-sd1a.210817.036.a8.zip'

All files, img are in the Platform-Tools folder - latest platform tools and driver.

Phone is recognized and flashed the bootloader and radio images no issues.
[Google Pixel 6 Pro] ginfest:
Nevermind got it sorted-stupidity on my end! Works fine!
[Google Pixel 6 Pro] GivIn2It:
OK Why is this a better method than the very first post in this thread? is that post incomplete? Why a seperate step for the radio? What do you mean by "2. Root & also update + re-root:" when I dont see that you have rooted at all at this point? What do you mean by stating " #updating to latest version and (again) disabling verification." when I don't see where you have already disabled verification? The first post of this thread seems straightforward and easy to follow, where this seems extra complicated. I don't want to mess up, so please explain.
[Google Pixel 6 Pro] Lughnasadh:
What was the "stupidity" on your end? Just asking so others will see this and know what to do if they run into the same problem.
[Google Pixel 6 Pro] ginfest:
Bad syntax --

On the fastboot flash bootloader, radio and update lines, I left out the words bootloader, radio and update in front of the file names! I misread the instructions.

I was typing "fastboot flash"and the filename- no wonder the command line was confused! 😊
[Google Pixel 6 Pro] Lughnasadh:
Ah, lol. We've all been there 😜. Thanks for getting back with that.
[Google Pixel 6 Pro] Markelijk:
Has anyone updated to the latest Magisk Canary 23014 yet? If so, what are the steps to follow? Thanks in advance!
[Google Pixel 6 Pro] Lughnasadh:
Yes. Assuming you are already rooted and just updating, update the app to 23014, patch your boot image and flash the patched boot image in fastboot. Procedure is not different from previous versions.
[Google Pixel 6 Pro] js042507:
Sorry, dumb question. When updating magisk, I presume we don't have to flash the vbmeta.img, correct? That's only for system updates. The procedure for updating masigk only would be...update magisk app, patch boot.img, flash patched .img via fastboot mode. That's all, right??
[Google Pixel 6 Pro] jlokos:
If you have already vbmeta, you don't have to flash it again when you are just updating magisk.. Also, you can install magisk update by direct install. No need to flash patched image.
[Google Pixel 6 Pro] js042507:
See. That's what I thought too!! Thank you!
[Google Pixel 6 Pro] Lughnasadh:
Yes, assuming that you've already flashed the vbmeta.img with those 2 flags disabled. Think of it this way, whenever you update via flashing factory image or OTA update you are flashing a new vbmeta.img that has not has those 2 flags disabled so you need to flash it with those 2 flags disabled. Once you have done that you can flash boot images to your heart's desire, but once you update the OS via factory image or OTA then you must flash those new vbmeta images with those flags disabled.

You can also use direct install if you are already rooted, but if you go through the Magisk thread (and other threads) you'll notice some people have had problems with that method, e.g. root not sticking. I prefer to just flash the patched image via fastboot but the choice is yours.
[Google Pixel 6 Pro] coolbub76:
So.. if i'm updated to the most recent version of android 12 on my P6P, if I wait for the next update, can I flash it to the (updated) stock manually with the flash tool, and disable verification without having to wipe?
[Google Pixel 6 Pro] V0latyle:
I mean, you CAN do it that way...the easiest way honestly would just be to use Magisk to directly update the kernel patch, that way you don't have to flash anything.

Yes, refer to the OP, I have provided instructions to do this.
[Google Pixel 6 Pro] js042507:
Yep. I did a direct install and it stuck. Worked perfectly. Thanks. I just wasn't sure about this new vbmeta stuff.
[Google Pixel 6 Pro] V0latyle:
The only time you have to worry about vbmeta is when you update. I prefer to update via the factory image, and use the --disable-verity --disable-verification options when flashing it. As long as it's disabled and stays that way, you don't have to worry about it anymore. You can flash /boot as many times as you want, you can update Magisk, it's no big deal.
[Google Pixel 6 Pro] kevinkoo:
Exactly same here, just disable Addon Features for Pixel Devices, the bootloop stops and the phone could launch the system.
[Google Pixel 6 Pro] herman1523:
So I did this and its still looping
[Google Pixel 6 Pro] roirraW "edor" ehT:
Using Magisk Stable v24.3? There are known issues with using some more recent Magisk Canary versions with the March update on the Pixel 6 Pro.

Restore the stock kernel if you have to, first.
[Google Pixel 6 Pro] herman1523:
Yes i used the lastest stable version from github
[Google Pixel 6 Pro] roirraW "edor" ehT:
If this were happening to me, I would try starting from scratch. I would even dirty flash the latest update without wiping (Update and Root Factory Image method in OP), make sure everything works when 100% stock, unlock the phone, let it finish the update if necessary (give it 5 minutes), copy the new boot.img from the factory image zip to your phone, using the Magisk Stable 24.3 you already have installed: make sure all Magisk Modules are disabled, and use it to patch that boot.img, copy that Magisk'd boot.img back to your PC and flash the Magisk'd boot.img.
[Google Pixel 6 Pro] herman1523:
any commands i can run that can completely reset me back to ground zero and at least get booted into the UI? i don't even care if Im not rooted at this point. sorry if this is a noob question.

nvm, I will follow the update and root factory method and report back
[Google Pixel 6 Pro] Nergal di Cuthah:
This is what i do and it works flawlessly
[Google Pixel 6 Pro] herman1523:
Update: I used the update and root factory method and everything is now working fine. Thank you for helping me!
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're welcome! Sometimes all that's needed is starting from scratch and persistence.
[Google Pixel 6 Pro] V-Ripper:
Hello...

I use Google Translator, so sorry for some mistakes.

Hello from Germany...

To the question:

I have freshly installed the March update via flash.android.com. So with Wipe, Disable Verity, Disable Verification. After restarting, installed Magisk 24.3, created a boot image in Magisk, rebooted into Fastboot and flashed the patched boot image there. reboot. Everything OK

root is there

Tasker, SD Maid, Root Explorer running.

But I don't have write access to system. Means I can't uninstall any system apps. When I go to "system/App/BasicDreams" in Root Explorer and want to delete the APK, it says only read access. I can't delete any system apps via SDMaid either.

This worked before the reinstall. What did I forget?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hi @V-Ripper. I know there's a Magisk Module some people use that can, to my understanding, do what you need. I believe it simulates what you want to do - so to the system, such and such apps are uninstalled, or other files are written if that's what you decide to do. I don't know the name of the Magisk Module as I haven't used it myself, at least not in years, but hopefully, with the right search, you can find it.
[Google Pixel 6 Pro] V-Ripper:
Does that mean you can't uninstall gmail, for example? just freeze?

But why was I able to do that until yesterday???
[Google Pixel 6 Pro] roirraW "edor" ehT:
If you find and use the right Magisk Module, I'm under the impression that you can make the system think the GMail app, for example, doesn't exist.

Unfortunately, I don't have any guesses for that.
[Google Pixel 6 Pro] V0latyle:
Why did you disable dm-verity and vbmeta verification? It's not necessary.
[Google Pixel 6 Pro] exocetdj:
Great guide, rooted in first attempt.

This alone means the pixel already blows Samsung phones out of the water lol
[Google Pixel 6 Pro] V-Ripper:
I read it at the beginning of November that you have to deactivate it. After that I deactivated it with every update and had no problems...
[Google Pixel 6 Pro] Nergal di Cuthah:
Haven't needed to since January
[Google Pixel 6 Pro] Lughnasadh:
Here's my 2 cents, which is probably worth only half of that....

I continue to have verity & verification disabled due to so many people in so many different circumstances (updating OS versions with different methods, flashing kernels, flashing patched boot images, etc.) continuing to get corruption messages/errors. There are at least 6 threads in the 6 Pro forum alone opened due to corruption messages/errors.

Although it's true that Canary 23106 released in December addressed the known vbmeta problems at the time, thus allowing us to boot Magisk-patched boot images, I am of the belief that there is still something wonky going on with vbmeta, dm-verity and/or verification. Too many people still get the corruption message even after the release of Canary 23016 and that corruption message ("Your device is corrupt. It can't be trusted and may not work properly.") directly relates to a dm-verity corruption . Google even released a patch in the March 12.1 build for the 6/6 Pro addressing a corruption problem (Fix for issue causing inadvertent "device corrupt" error to appear in certain conditions *[2]), although I have no idea in what "certain circumstances" they were talking about.

Anyway, just from a general observation, it "seems" that most people who continue to have verity and verification disabled do not get the corruption message/error (including myself and a kernel developer who also keeps it disabled who have never gotten the corruption message/error). That's not to say if you don't have it disabled you will get the corruption message/error. I'm sure there are many people who don't have it disabled and have no problems. But the amount of people still getting the corruption message/error in so many various circumstances, even after the release of Canary Magisk 23016, leads me to believe that there is still something wonky going on. Whether it's with something Google has implemented that we may still not be aware of, or whether it's because of certain Canary versions of Magisk, or even a combination of these, I have no idea. And of course I could be completely wrong and all these corruption errors are rather a result of "user error" or something similar.

Anyway, a long-winded explanation of why I continue to keep verity and verification disabled... 🥱
[Google Pixel 6 Pro] V0latyle:
The red EIO corruption message doesn't explicitly mean there's a problem with dm-verity or vbmeta verification. I had the same thing pop up on my wife's 5a. I did what I tell everyone not to do and interrupted the OTA boot to flash the factory image (she had forgotten to install Magisk to the inactive slot) and subsequently got the EIO message as well as a boot failure. Sideloading the OTA fixed it.

To my knowledge the corruption issue has only been occuring when the OTA method is used, either automatic or sideload. It does not seem to be a problem with the factory image method...but I've also been wrong before :)
[Google Pixel 6 Pro] phaino00:
Unfortunately, I experienced the eio corruption message flashing a factory image.
[Google Pixel 6 Pro] V0latyle:
Then I'm wrong again
[Google Pixel 6 Pro] Lughnasadh:
It's been happening in a variety of scenarios in addition to the OTA method, including updating through the factory image method, flashing kernels, flashing kernels with certain Canary Magisk versions and even just flashing certain Canary Magisk versions beyond 23016. Here's just a few quotes from the developer of the Kirisakura kernel posted well after Canary 23016 was released and the last one was just a few days ago.

"Some users ran into the device is corrupted message for a quite a while now. It not only happens when flashing a kernel.zip, but in the end it seems related to a problem with verity/vbmeta and magisk. I think it´s related to keeping verity/verification enabled (not disabling the vbmeta flags via fastboot) and something just gets scrambled. Check the forums there are a few threads with plenty of cases."

"But given all the issues some people run into, when they end up with the device is corrupted message (seems also to happen when flashing/updating just factory images without the involvement of anything else, at least what I saw in the guide threads) there still seems to be something wonky."

"The issues some users are getting unfortunately have nothing to do with the kernel. It´s a mixture of google having some problems with the corruption thingy themselves as they revealed in the patchnotes (March 2022) and the other issues are due to magisk canary being experimental canary builds."

Also, if you glance through the Pixel 6 series threads where people have had the corruption problems, almost invariably the people that do have these problems have not kept verity and verification disabled. The above kernel developer (as well as myself) continues to keep verity and verification disabled to this day because of the continuing problems that those who don't keep it disabled may run in to.

Just my opinion, but I think something is still not right, otherwise people would not be getting these corruption problems in a variety of scenarios outside of updating via OTA even to this day.

But of course, I've been wrong before too 🙃
[Google Pixel 6 Pro] V0latyle:
It's known to be an issue with custom kernels...but stock?

Also I haven't been paying attention to the P6 forums. I have a P5 and wife's P5a, so I don't have any way to test anything on the P6.
[Google Pixel 6 Pro] Lughnasadh:
Yes, it's happened on stock kernels as well.
[Google Pixel 6 Pro] V0latyle:
Good to know. It seems like Google is still tinkering with the boot code, and some of the changes are breaking Magisk functionality. I imagine Magisk will catch up eventually. In the meantime, I'd encourage people having Magisk issues to post in the Magisk support threads.
[Google Pixel 6 Pro] Lughnasadh:
The thing is, I don't think it's strictly a Magisk issue, otherwise it wouldn't sometimes happen when people are just updating to a new build with Magisk not involved. Sure there are conflicts with some new Canary versions, but I think it goes deeper than that, as possibly evidenced by Google's corruption patch notes that came with the March update. Those patch notes, however, could just be referring to the problems people were having when updating to Android 13 on a locked bootloader. Don't think we really know what exactly Google was addressing with that patch.
[Google Pixel 6 Pro] thieftime1980:
why can't i install the patch boot magisk image file ,?
[Google Pixel 6 Pro] V0latyle:
Looks to me like you're using a third party ADB tool which is probably out of date. Use the latest official Platform Tools.
[Google Pixel 6 Pro] 5t4rC0m1337:
Hi Team,

I tried to "Update and Root Automatic OTA" with the last March update but it failed (update failed) [probably failed because I have a custom kernel].

Then I decided to reboot, since them I am in a bootloop.

Would you know a way to break the loop without wiping the phone please ?

EDIT:

I think it is because before updating OTA, I uninstalled Magisk via tap Uninstall, then Restore Images.

But before rebooting, forgot to install it back via Install at the top, then Install to inactive slot.

Is there a way to undo ?
[Google Pixel 6 Pro] roirraW "edor" ehT:
@5t4rC0m1337 since you already created a thread about this issue before posting here, you should keep all posts about it there -> Boot loop after march update failed
[Google Pixel 6 Pro] 5t4rC0m1337:
Hi Team,

I had to flash the last OTA March update via AFT which means I also lost root.

What is the correct way to root again ? I was thinking of Update and Root using the Android Flash Tool from the main page ?
[Google Pixel 6 Pro] Lughnasadh:
Patch the stock boot image in Magisk. Flash the patched boot image in fastboot as described in the Initial Root/Create Master Boot Image section.
[Google Pixel 6 Pro] lu_chengus:
I'm on android 12.1 with pixel 6 pro. I followed the guide and it returned an error "failed to flash partition (boot_b)" when flashing the patched magisk img. My platform tools are the latest. I also disabled verity and certification. Any ideas?
[Google Pixel 6 Pro] Nergal di Cuthah:
Which method did you follow there are a number in the op. First none of them say disable verity or cert so that sounds out of the guide already
[Google Pixel 6 Pro] lu_chengus:
It is an initial root. I disabled them because the most recent reply in this thread said someone encountered errors without doing so.

Edit: Reverted back to 12 instead 12.1 and it works
[Google Pixel 6 Pro] Dorisnov:
Having same issue here:

Sending 'boot_b' (0 KB) FAILED (File is too large to download)

Any way to flash the boot image without having to roll back to 12?