yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] gazdajezda:
Yes, I read about bootloops here after normal (classic) root process (flash factory image without -w and patched boot.img). That works now?

So, if I disable Magisk modules (have only Systemless hosts and USNF, i can actually do OTA update (restore org image, patch inactive...) and system will reboot normally? Last 2 times i do it, phone won't boot normally.
[Google Pixel 6] V0latyle:
I am using those two modules and have never disabled them. The modules that should be disabled are those that modify /system.

You should in theory be able to use the automatic OTA method. I personally haven't bothered, because my Pixel 5 never gets the notifications and doesn't download the update, so I just use the factory image.
[Google Pixel 6] gazdajezda:
Ok. Thanks.
[Google Pixel 6] lame.exe:
Big issue here after updating to May release.

What I did was:

1. Update magisk to latest canary 24314

2. Download factory update, extract boot.img and patch with magisk -> magisk_patched-24314_zg1Qw.img

3. Download OTA and adb reboot sideload

4. adb sideload ota.zip

5. Reboot to system and let it do it's job

6. Reboot to bootloader

7. fastboot boot magisk_patched-24314_zg1Qw.img

Thats when the issues started.

The phone restarted after fastboot boot and tried to boot from magisk_patched-24314_zg1Qw.img, but bootlooped. Then it restarted again and booted from unpatched system boot.img.

I tried to boot from magisk_patched-24314_zg1Qw.img several times, same result.

Then I flashed the magisk_patched-24314_zg1Qw.img with fastboot flash boot which was successfully. But still bootlooping until a new message appeared:

your device is corrupted it cannot be trusted and may not work properly

The I tried to flash the original system boot.img, which I kept after extracting but the corrupt message remains and boot isn't possible.

Please help me, I don't know what to do next and I'm not sure what went wrong at all.

EDIT:

I was able to start recovery and flash OTA again. Now I can access the system again and will try so patch the boot.img with magsik, maybe the file was corrupted.

EDIT 2:

Same result after patching boot.img with canary 24314, still bootloop :(

I will try with canary 24310 and let you know.

EDIT 3:

Also bootloop after patching boot.img with canary 24310...

Does anyone know what is the issue here?

I came from Januar release oriole-ota-sq1d.220105.007-0e8d793c, could this be the reason?
[Google Pixel 6] capntrips:
I would try Magisk 24.3 stable, first, just to rule out verity issues. I personally have had better luck with the flash-all script (after removing the -w flag, if you don't want to wipe your data) or the flash tool (with wipe and lock unchecked) than sideloading the OTA, if you want to see if one of those methods gives you better results.
[Google Pixel 6] lame.exe:
Thanks for your reply. I never had such issues before by using the OTA method and the system is running fine, but I can't get back root since the patched boot.img isn't booting.

I could try to use the magisk stable 24.3, but in the first post it's highly recommended to use canary 24310.

EDIT:

I tried 24.3 stable, but I still cannot boot the patched boot.img. I have no idea what's going on. Bootloader is still unlocked, everything seems fine for root.
[Google Pixel 6] ylallier:
Nevermind
[Google Pixel 6] capntrips:
There was a change to avb handling in 24303 that results in bootloops in several situations, which is why I typically try that first, since it can be done in a few minutes.

Also, do you get the animated G logo when you bootloop? or do you immediately reboot at the Google logo? If the former, you might have a previously installed module causing an issue, see here.
[Google Pixel 6] lame.exe:
Same problem with stable 24.3, so it must be sth else, e.g. magisk modules like you mentioned.

The phone starts booting normaly after fastboot, first comes the unlocked bootloader warning, then the coloured "google" and then the big grey G with the loading bar animation fpr some seconds. Then the screen gets black and the phone bootloops and starts again with the bootloader warning.

I tried to disable the modules by "adb wait-for-device shell magisk --remove-modules" directly after sending the fastboot command, but the adb command is ignored and the bootloop comes again.

What am I doing wrong?
[Google Pixel 6] lame.exe:
I think the remove-modules isnt working because magisk isnt installed at the moment. When I tried when the phone is turned on I get the message:

adb shell magisk --remove-modules

/system/bin/sh: magisk: inaccessible or not found

I tried to install the factory image with even bootloader and radio, but it's always the same bootloop after the big G and the loading animation for about 10 seconds.

I have no idea how to proceed besides wiping the phone and starting from scratch...
[Google Pixel 6] Lughnasadh:
That command will still work even if you're not rooted.

Removing or disabling Magisk Mods when in a bootloop

Method 1: (Removing Mods)

1. Turn off device

2. adb wait-for-device shell magisk --remove-modules in command prompt

3. Connect your phone to computer and turn it on.

4. Phone tries to boot and the command should be accepted

5. Wait until the command worked and the phone boots up without issues

Method 2: (Disabling Mods)

1. Boot into Safemode

If Phone is On:

Press and hold your phone's Power button.

On your screen, touch and hold Power off .​

After you see "Safe mode" at the bottom of your screen, wait to see if the problem goes away.​

If Phone is Off:

Press your phone's power button.​

When the animation starts, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.​

You'll see "Safe mode" at the bottom of your screen.​

2. Reboot

3. Disable or remove mods

If none of this works, you might want to try Android Flash Tool without wiping first.
[Google Pixel 6] badabing2003:
The latest canary magisk is 24315, use that.

Make sure you also use the latest platform tools.

Don't transfer through MTP, use adb to transfer to phone and back to your PC (optionally you can use the program from my sig if you don't want to do it manually), I've seen reports where MTP transfer gets corrupted.

I would do full factory image of May without -w just to make sure all parts are from May, and probably on both slots.

If it still bootloops, you can try the Magisk key combination (I don't recall the exact combination, something like volume down) while booting, that disables the modules.

It's possible that as soon as root is enabled your modules are also enabled and one of them is causing a bootloop, by any chance what modules did you have?
[Google Pixel 6] lame.exe:
Finaly, method 2 worked :love:

But I had to boot from patched boot.img first, when I just started the phone I wasn't able to disable the modules.

Therefore method 1 didn't work, since the bootloop was before the adb wait-for-device shell magisk --remove-modules command could be sent from console.
[Google Pixel 6] ibrahim52:
I will try to be here every month, just to say THANK YOU to original poster.
[Google Pixel 6] V0latyle:
You're welcome.
[Google Pixel 6] V0latyle:
Reboot is not necessary between update of bootloader and radio. However, bootloader must be rebooted before attempting update, so that the phone loads the new bootloader image. The update process checks both bootloader and radio versions.
[Google Pixel 6] t-ryder:
flash-all batch script by Google does a bootloader reboot plus a pause of 5 seconds between flashing the new bootloader and the new radio, so I thought I'll do it that way too.
[Google Pixel 6] chuppito:
Hi, how do you update while being root? The system does not offer me the update.
[Google Pixel 6] jaggy989:
Does Pixel 6 retain Widewine L1 after rooting?
[Google Pixel 6] t-ryder:
I'm rooted and got security level L1.
[Google Pixel 6] V0latyle:
Magisk Canary was updated to 23016 last night. This includes a fix for the vbmeta header issue, meaning that disabling verity/verification should no longer be required, and we should be able to root as we did before. This needs testing, make sure you back up your data and photos before you do this!

Additionally, for the Pixel 6 and 6 Pro, fstab will now load from /system/etc which should fix the root issue many of you were having.

Q: "If verity/verification are disabled, do I need to enable them now?"

A: No. The only thing you have to do is update to Magisk 23016.

Q: "Will enabling verity/verification wipe my data?"

A: No.

I will be updating the OP to reflect this.
[Google Pixel 6] pa.pn2:
Means we just flash the Monthly Updates Dirty without the -w and we are fine?

Did you test it?

I accidently upgraded to December Update recently and lost root, im not able to boot with patched kernel anymore.

I set the flags in the flash-all.bat before, but everytime i try to boot with patched kernel i get the message to try again, or factory reset now.

I guess something messed really bad up...
[Google Pixel 6] V0latyle:
Ostensibly, yes.

I have not.

Restore the stock boot image (just flash it as you would the patched image). Boot Android, download and install Magisk 23016. Patch the boot image with the new Magisk version and see if it will boot.
[Google Pixel 6] pa.pn2:
Did that already, no success.

It always bootloops and rebeoots to the point where i can try again or factory reset.

I dont know what happend exactly...
[Google Pixel 6] pa.pn2:
after i choosed try again it boots up normally with stock kernel i think, because i just used fastboot boot patched kernel, not fastboot flash
[Google Pixel 6] V0latyle:
I wish I had a better answer but you may end up having to wipe data. There's a few things we can try first.

If you're able to boot the stock kernel, make sure your photos and data are backed up.

Once you're done with that, extract vbmeta.img from the same zip the boot.img is in, and reflash it:

fastboot flash vbmeta vbmeta.img --slot=all

Now, flash the 23016 patched image:

fastboot flash boot magsik_patched-23016_xxxxx.img --slot=all

Attempt to boot and see what happens.
[Google Pixel 6] pa.pn2:
will do soon, means verification will be enabled again, correct? And the new magisk disables it?

Shouldnt i first boot up patched kernel instead of flashing?

So we dont need to set the disable flags anymore in future?

Sounds good
[Google Pixel 6] V0latyle:
That's the idea. Again, make sure everything is backed up, in case you have to disable verity/verification again and wipe data.
[Google Pixel 6] pa.pn2:
I backed up everyhting already. Fingers crossed, hope it works....

But if i enable the vbmeta again, am i not prompted to do a factory reset again?
[Google Pixel 6] V0latyle:
Shouldn't be. Only when disabling if not previously disabled.
[Google Pixel 6] pa.pn2:
shall i boot up after flashing vbmeta or can i instantly boot the patched kernel?
[Google Pixel 6] V0latyle:
We already know that it's possible to boot a patched boot image if verity/verification are not disabled. The problem was getting it to load from /boot, so after you reflash vbmeta, flash the patched image to /boot, then reboot to system.
[Google Pixel 6] pa.pn2:
You know what?

It worked, many many thanks for that.

Do you have any explanation for that?
[Google Pixel 6] tom1807:
I am not sure whether you meant by OTA the OTA package or the full update.

You should never use OTA update when you are rooted, only the full package.

Cheers

Tom
[Google Pixel 6] badabing2003:
Great! Did the corrupt message disappear as well or you're still getting that?

And for the benefit of others, what Magisk modules you had active? obviously one of those was causing the bootloop.
[Google Pixel 6] lame.exe:
The corrupt message disappeared already after the second sideload installation.

Your second question is hard to answer, since I disabled some modules before the update (zygisk lsposed, universal safetynet fix) and some I left enabled (air music, addon features by typhus, screencam).

The screencam module was the only active module that wasnt installed druing my last update in january, but I also hadnt installed lsposed either.
[Google Pixel 6] Lughnasadh:
It was probably the Addon mod by Typhus. That mod usually needed to be updated each month to be compatible with new monthly builds. It's EOL now so you probably shouldn't use it. The AOSP mod has taken its place.

Not familiar with the other 2 mods you still had enabled so not sure if those caused problems as well.
[Google Pixel 6] badabing2003:
I know in the past audio related modules had caused bootloops, so it could (or not) possibly also be air music.
[Google Pixel 6] V0latyle:
This is why I generally advise dirty flashing the factory image rather than using the OTA. OTA does something weird with boot parameters and ramdisk that can cause problems when you're trying to boot or flash an external image.

Also, if you're using any modules that modify /system, you must disable these before updating.

I personally only use 3 modules:

Systemless Hosts

Universal SafetyNet Fix

MagiskHide Props Config

I have never needed to disable these when updating.
[Google Pixel 6] capntrips:
Other than March and April, when Magisk was working through the 12L changes, OTA upgrades via System Update have been working for Pixel devices since November using the method described in the Magisk docs.
[Google Pixel 6] V0latyle:
Yes. However, updating via OTA seems to be one of the common denominators for people having problems, the other being some Magisk modules.
[Google Pixel 6] tom1807:
Correct, I experienced also issues since March, when the OTA update was applied, that it was in a bootloop with Magisk 24.3. It should be fixed wit current Canary builds, however I am fine with stable and flash with Pixel Flasher.

Cheers

Tom
[Google Pixel 6] V0latyle:
That's another thing. Using out of date ADB tools can cause problems as well. I personally don't like using third party tools because they don't always use the updated ADB libraries, but to each his own.
[Google Pixel 6] badabing2003:
FYI, If you're referring to PixelFlasher, It does not include adb libraries, you have to select your own.

And it would display the version you're using with handy link to download the latest.
[Google Pixel 6] V0latyle:
I wasn't referring to any particular one; I do know other tools use MinimalADB. But it looks like you've done a great job of keeping everything up to date with yours :) I may just have to try it out, even though I usually do everything the old fashioned way!
[Google Pixel 6] badabing2003:
I'm with you 100% though, I avoid tools if I can do it manually, if I understand the manual steps, I can get myself out of trouble, If I rely on a tool, then it becomes harder unless the tool is well supported.

In fact, in the credits section of the documentation I explicitly encourage people to first learn and use the manual methods.

It's a balancing act that we always do, convenience always comes at some cost, after years of doing the manual steps I got lazy and wanted to automate some of the steps, which grew into the program it is now.

Some aspects of it is truly convenient, like automated patching and single flashing without losing root.
[Google Pixel 6] LLStarks:
Don't use Minimal ADB. Extremely outdated.
[Google Pixel 6] V0latyle:
That's exactly my point here.
[Google Pixel 6] miss:
pixel 6 update with ota june through pixel flasher and working correctly and rooted in less than 10 minutes thanks
[Google Pixel 6] miss:
thanks for you work
[Google Pixel 6] V0latyle:
Magisk Beta 25.0 is out. For those of you who don't like using Canary, this should incorporate all previous fixes.

As a reminder, do not use Stable 24.3 if you update via OTA.
[Google Pixel 6] gazdajezda:
OTA update? Does that work now? On rooted P6?
[Google Pixel 6] V0latyle:
I have not tested this myself (I have a Pixel 5, and I don't update via OTA) but my understanding is that Canary 24306 fixed OTAs, while 24310 includes some vbmeta fixes and support for Android 13.

I would suggest updating to the latest public beta (25.0) and following the instructions for OTA update here; note that the Pixels are A/B devices so the "Non A/B Devices" section does not apply.
[Google Pixel 6] gazdajezda:
Hour ago i updated Magisk to latest (25001 (31)), so far all good. I will also do classic update to latest (june) system update (flash without -w, re-patch boot image, flash, reboot). That is still rock solid way for my P6.
[Google Pixel 6] shoey63:
Sure does.

Just did it on the latest canary before 25.0 beta was released.

Usual disclaimer - no fancy modules and not running a custom kernel. Just plain rooted stock with USNF and Zygisk Lsposed.
[Google Pixel 6] V0latyle:
If you're only using USNF, why Lsposed? USNF 2.2.1 works with Zygisk.
[Google Pixel 6] shoey63:
Lsposed (Zygisk version) is for a couple of basic Xposed modules I use. And yes, USNF will pass SafetyNet with or without Lsposed.
[Google Pixel 6] V0latyle:
Oh okay, makes sense. It originally sounded like the only two modules you were using were Lsposed and USNF.
[Google Pixel 6] gazdajezda:
I don't know what I'm doing wrong then. I tried it 2 times and ended with boot loop and need to re-flash/re-root again. I do not had any 'strange' modules installed, just classic ones (USNF, systemless hosts...). I forget what Magisk version was installed at that time (it was canary last version at that time). Now I have 25001, maybe I will try tommorow if I will have time. But I doubt it will work. 🤣
[Google Pixel 6] V0latyle:
Which method have you been using to update?
[Google Pixel 6] gazdajezda:
Nothing special. In short version, i do:

1. Magisk uninstall / Restore images

2. Start/complete OTA install, without restart

3. Magisk install to inactive slot / after OTA

4. Restart

5. Did not work, so flash factory image without -w

6. Magisk patch boot image and flash it to get root again
[Google Pixel 6] capntrips:
If you're already flashing the factory image, you may as well flash the June update that way. If you're just doing some testing to figure out why the OTA isn't working for you, maybe see if you can revert to the previous slot and grab the ramoops file after the bootloop (booting into fastbootd or recovery will wipe the file, so you would have to set the previous slot in the bootloader). If it isn't something easily fixed on your end, you can post it to the Magisk issue tracker to hopefully help get it fixed for others, as well. Note that they only accept submissions from the latest canary build (which I see you are now using).
[Google Pixel 6] gazdajezda:
Ok. Will try tommorow or some other time (now going to sleep).
[Google Pixel 6] r00tcracker:
You guys still maintaining root and passing Safetynet with latest June update and latest canary magisk?
[Google Pixel 6] V0latyle:
I use a Pixel 5, but no issues here. Updated using factory image as I always do, then shortly after the update, updated Magisk Canary to 25001. Everything passes in YASNAC.
[Google Pixel 6] kafisc:
Yes. Magisk Canary and Universal SafetyNet Fix will do the trick.
[Google Pixel 6] r00tcracker:
Legends!!!!!

Thank you!
[Google Pixel 6] soodz:
I did the slot b trick with magisk for the June update and everything was smooth as usual for me... Passing safetynet, modules still working, all systems go
[Google Pixel 6] V0latyle:
Magisk 25.1 was released yesterday. If you aren't already, please ensure you use this version from now on. This incorporates multiple fixes related to image patching, OTA updates, as well as 13 Beta support.
[Google Pixel 6] C5Longhorn:
I'm about to update to the June release. I would appreciate any feedback on the steps I plan to update:

1) Download stock June image .zip

2) Move .zip to Android_adb location on computer

3) Unzip the file in Android_adb folder where I will flash from

4) Open Command line to Android-adb folder

5) Flash June image file with -w removed from script using fastboot flash-all command

6) Device will reboot

7) Install latest Magisk (25.1) on device

8) Patch stock Boot image with Magisk on device

9) Copy patched file back over to computer

10) Flash patched boot image to device

11) Reboot and hopefully enjoy my P6 on June release

I last tried to do this with the March update and bootlooped the phone. I ended up having to use the flashing tool and install the entire image with data wiped. I'm hoping to avoid that this time around.

Do my steps seem correct?

Thanks,

Rick
[Google Pixel 6] V0latyle:
Looks good to me. I personally don't use the flash-all script and do the commands manually, but to each his own. You can also install Magisk now and patch the boot image before you update; then, you can copy the patched image back to the folder, and change the last lines in the script like this:

fastboot update --skip-reboot image-oriole-buildnumber.zip
fastboot reboot bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot <name of patched image>
fastboot reboot
[Google Pixel 6] itamargs:
Yes. Just one thing,

"flash-all.xxx" is a script file and not a fastboot command so just write in the command line:

"flash-all.batch" (for Windows) OR "flash-all.sh" (for Linux) and it will do the work for you.

EDIT: for making sure no one will accidantly wipe his device. need to remove the -w flag from the script in use

tnx @badabing2003 and @V0latyle
[Google Pixel 6] V0latyle:
Not quite correct...

flash-all.sh is a shell script for a Linux terminal and won't work on Windows.

flash-all.bat is a batch file that contains scripts for the Windows command line.

Simply typing flash-all in the command line should load and execute the correct script, regardless of what you're using. You are correct in that it's not a fastboot command in of itself; the script contains the fastboot commands used for flashing the device.

@C5Longhorn if you wanted to flash manually, here is the correct sequence to dirty flash the factory image to both slots:

Download and extract factory package. Extract boot.img from image-oriole-buildnumber.zip. Patch boot.img in Magisk and copy back to the factory package folder. This can be done before or after the update; I personally prefer to do it before.

Reboot to bootloader:

adb reboot bootloader

Compare bootloader and baseband versions on device screen to the radio and bootloader files in the factory package. If different, or if you just want to be safe, update them:

fastboot flash bootloader --slot=all <drag and drop bootloader.img>

Wait for flash to complete.

fastboot flash radio --slot=all <drag and drop radio.img>

Wait for flash to complete

fastboot reboot bootloader

Observe updated bootloader and baseband versions

Dirty flash the factory image:

fastboot update --slot=all --skip-reboot <drag and drop image-oriole-buildnumber.zip>

Wait for update to complete; watch command line. Device will reboot to fastboot mode during the process.

When update completes, reboot to bootloader:

fastboot reboot bootloader

Flash patched boot image:

fastboot flash boot --slot=all <drag and drop patched boot.img>

Wait for flash to complete.

Reboot to system:

fastboot reboot

Your device should boot into updated system with root.
[Google Pixel 6] badabing2003:
And wipe the phone if done blindly without first editing it.

@itamargs just follow the guide or better yet what V0latyle said here

https://xdaforums.com/t/guide-pixel...ate-root-pass-safetynet.4356233/post-87059395
[Google Pixel 6] V0latyle:
True. My assumption was that he'd already edited the script. One can always perform the commands manually, or use your tool! (I still haven't tried Pixel Flasher yet)
[Google Pixel 6] phaino00:
Do you have a specific reason for flashing to both slots, adding '--slot=all' to the fastboot update command? Or is it just a habit from past flashing/updating, thus don't fix what's not broke?
[Google Pixel 6] V0latyle:
It's not a necessity, but because I always update with the factory image, I flash both slots to ensure a failover if there's a problem with one.