yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Phazed47:
Android flashtool kept failing to download, getting about 60% through and restarting.

So I just did it all with fastboot, which worked but of course wiped the phone. Not a huge problem but, going forward, is there a FAQ on exactly how to do an appropriate backup, factory wipe, restore to get all settings & files back?
[Google Pixel 6 Pro] V0latyle:
A full backup can only be done with root, using an app such as Swift Backup.

It's important to follow instructions. If you run into trouble while operating outside the scope of this guide - using a version of Magisk not compatible with Android 12 for instance - you're on your own.

The overall best way to update is by dirty flashing the factory image. Automatic OTA won't work with any version of Magisk older than 24310. This is why I included these specific notes in the OP.
[Google Pixel 6 Pro] Phazed47:
Note that I followed the instructions in the OP exactly, including latest SDK and the linked version of Magisk. The issue may have been that I was coming from an old release (Jan, I think). As upgrades are always high risk, I saw no point in risking a wipe until Dirty Pipes was patched.

I have backups of all my important stuff, it would just be nice to be able to say "just restore it all". I'll take a look into Swift once I get everything back the way I want it, thankx
[Google Pixel 6 Pro] V0latyle:
Unless root is an absolute must, I'm not aware of anything that will force a wipe. If a patched kernel fails to boot, you can just flash the unpatched image.
[Google Pixel 6 Pro] Morgrain:
I've been using your guide to update for months now. Never had a serious problem, thanks alot for writing it.
[Google Pixel 6 Pro] V0latyle:
Absolutely. It doesn't hurt that the Pixels are blessedly simple, too.
[Google Pixel 6 Pro] 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 Pro] roirraW "edor" ehT:
Also, a warning for anyone who uses a custom kernel, the kernel will likely have to be updated to work with the new Magisk Beta v25.0. Kirisakura has been updated and there are at least some reports of successfully using v25.
[Google Pixel 6 Pro] cmh714:
I bit the bullet and let v25 install direct while already on the Kirisakura kernel, and so far no issues.
[Google Pixel 6 Pro] pojr:
Question for you guys:

I tried to use the "Update and Root Automatic OTA" method of updating (where you uninstall & restore image in Magisk, then update, then reinstall), but when I try to actually update, I receive a "program failed" message and the update does not happen. I looked up an youtube video on how to Update and Root Automatic OTA, and I did the steps 100% correctly, but same error. Unfortunately I don't have logs (sorry). Has anyone had this issue? I looked through this entire thread but didn't find anyone with this problem.
[Google Pixel 6 Pro] Nergal di Cuthah:
Anything altered about your phone that might change system? Magisk modules? Kernel?
[Google Pixel 6 Pro] pojr:
my bad, i should have included this before.

i did have one magisk model, the systemless host one (that lets you hide apps). the first time i tried to update i forgot to uninstall the model, but the second time i remembered to do so, but it still failed to update for the same reason.

i have no custom kernel, just the default one.
[Google Pixel 6 Pro] TiZiO.Cover:
Updating with the Android Flash Tool does not work this time because the Flash Tool does not find a newer update than the already used 12.1.0 (SP2A.220505.002, May 2022).

The factory images "SQ3A..." provided by Google are not offered for installation.
[Google Pixel 6 Pro] jcp2:
I used Android flash tool this morning and it found and installed June's update, no problem.
[Google Pixel 6 Pro] TiZiO.Cover:
OK, i tried yesterday, i'll give it another go later.
[Google Pixel 6 Pro] V0latyle:
The only thing Systemless Hosts does is create a redirect for the hosts file (IP addresses and domain names) to a dynamic file contained in storage. This is used by ad blockers such as AdAway and has nothing to do with hiding apps.

When this happens, you can just update manually using the factory image...or sideload the OTA.

I would recommend the same for everyone else having issues with the automatic OTA.
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're not crazy. Yesterday when I was trying to fix a problem, the Android Flash Tool wouldn't list anything newer than the March firmware update (except it also listed Betas).
[Google Pixel 6 Pro] V0latyle:
I believe it does this if you've opted into the Beta program - the last factory image it shows is whatever was before the beta was released. Opting out of the beta program should show current packages.
[Google Pixel 6 Pro] roirraW "edor" ehT:
That makes sense, thanks. I haven't opted into a Beta program in years, though - and I haven't manually flashed any of the P6P Betas or Developer Previews. This leads me to believe that Google's assumed temporary bug was that at least for some users, they mistakenly thought they have opted into the Beta program.

@TiZiO.Cover see @V0latyle's response above.
[Google Pixel 6 Pro] TiZiO.Cover:
Sideloading the OTA worked like a charm.
[Google Pixel 6 Pro] pojr:
I do use AdAway so that explains that. But it was still under modules, so I think I did the right thing by uninstalling it before trying (and failing) to update.
[Google Pixel 6 Pro] js042507:
Yeah, I'm learning this. Thanks! I actually updated last time using the OTA method, and not the factory image. Worked just fine. But yeah, wasn't sure before how "permanent" the disable verify stuff was until now.
[Google Pixel 6 Pro] Golf c:
So with the taking out the -w and adding the disable flags when updating in the future, device won't wipe again?
[Google Pixel 6 Pro] V0latyle:
It's not permanent at all. Verity and verification are only disabled as long as /vbmeta has been flashed with those disabled; if at any point /vbmeta is flashed without the --disable options (such as during automatic OTA) then AVB is enabled again - and to disable again will require a wipe.

This means that Verity and VBMeta Verification MUST be disabled EVERY TIME /vbmeta is flashed.

Yes. Please refer to the OP.
[Google Pixel 6 Pro] js042507:
Yep. I understand that. I meant permanent, as in rebooting really.
[Google Pixel 6 Pro] coolbub76:
Sorry, should've mentioned -- I'm talking about coming from an unrooted device.
[Google Pixel 6 Pro] Oaklands:
Try being born in 1957!
[Google Pixel 6 Pro] V0latyle:
Right? Growing up with such novelties as color TV's, transistor radios and video tape!
[Google Pixel 6 Pro] Enddo:
so my bootloader is unlocked. on the latest update

I boot into fastboot mode, disable verity and verification

but when I reboot into Android I am sitting at the 'cannot load android system' message

what did i do wrong?
[Google Pixel 6 Pro] Lughnasadh:
Read the 2nd paragraph of the OP. If this is the first time disabling those 2 flags, you need to wipe/factory reset.
[Google Pixel 6 Pro] Enddo:
I did that (I had to). is there a way to confirm that verity/verification has been disabled? now that hte phone has booted back into android
[Google Pixel 6 Pro] Az Biker:
Follow the P6Pro detailed step by step guide linked in my sig.

I just used this and had zero issues. There are also links to other guides if further help is needed.
[Google Pixel 6 Pro] Lughnasadh:
If you are able to flash the patched boot image and subsequently boot into the OS (which is the whole reason to do this), you have successfully disabled those 2 flags.
[Google Pixel 6 Pro] Enddo:
heh, but if it wasn't disabled correctly then I'll be forced to factory reset (again)

so like wanting to run the 'fastboot devices' command to confirm that I have a connection to the phone, I'm curious if there's a way to confirm if verity/verification has been disabled without having to flash a modified boot.img

maybe an adb shell command? or something that I can do after booting back up from the initial factory reset
[Google Pixel 6 Pro] Lughnasadh:
I don't know the command to check. But if you followed the directions carefully you should be ok. If you didn't do it correctly you wouldn't have had to factory reset. The reason you needed to factory reset is because you did disable those 2 flags.
[Google Pixel 6 Pro] V0latyle:
There is indeed an adb shell command that was posted somewhere during a similar discussion. I'll update this post if I find it. I believe @capntrips might know.

If I were you I would just flash a patched boot image. If you get stuck in bootloader with "failed to load/verify boot images" then you did indeed forget to disable verity and verification. You can just flash the stock boot image, make sure everything is backed up, then factory reset, reflash vbmeta to disable verity and verification, and flash the patched boot image.
[Google Pixel 6 Pro] NippleSauce:
After updating to the .037 image, anyone else have the installed build number not change in the "About Phone" settings section...? I didn't notice any errors during the update over fastboot, however, my build number still ends with .036... I suppose I'll try again and see what happens.

*Update* - Never mind. I did it again and paid attention this time, haha. My phone never went into fastbootd when flashing the update zip. I noticed that I left the update files in an additional folder within my platform-tools folder and so the incorrect versions of adb and fastboot were being used lol. We're all good now =).
[Google Pixel 6 Pro] bosox284:
This might be a dumb question but I can't find an answer. Are there any effective differences between 'fastboot flash-all' (without -w), 'fastboot update xxx.zip', and 'adb sideload ota.zip'?

Quick edit: the reason I'm asking is that if you need to download the factory image to extract the boot.img anyway, it doesn't seem worth it to do adb sideload. Unless of course the OTA sideload is a cleaner installation, since it's theoretically only an update of things that have changed. Though it would seem that fastboot update would do effectively the same and is the easiest update method because you only have to download the factory image?
[Google Pixel 6 Pro] Lughnasadh:
No real difference in outcome, just in method. I prefer the flash-all method b/c I've been doing that since the Nexus 5. I find it simple. Others prefer whatever they are used to, makes them feel more comfortable or is easiest for them.
[Google Pixel 6 Pro] V0latyle:
That's why I recommend updating using the factory image, because it doesn't make sense to waste your time and bandwidth on both files. If you sideload the OTA, you either have to unpack the OTA, or you have to download the factory zip anyway.

If you dirty flash the factory zip, you don't have to reflash vbmeta if you use the disable options while flashing the update, and all you have to do is extract and patch the boot image.

Factory zip is technically the cleaner installation, as it installs to both slots. Sideloading the OTA only installs to the inactive slot, then switches slots when it reboots.
[Google Pixel 6 Pro] Lw00d:
i am a bit confused with this guide.

i want to flash factory image without having to wipe data.. do i need to edit flash all .bat file??

step 4 says apply update how do i do that?? just flash, flash all .bat file?
[Google Pixel 6 Pro] V0latyle:
I use Systemless Hosts for AdAway as well, and have never needed to disable it when updating. The module does not change anything in /system; instead, it "hijacks" where the kernel looks for the hosts file and redirects it to the custom hosts file managed by the ad blocker.

I also use Universal Safetynet Fix and MagiskHide Props Config; I haven't needed to disable either of these when updating.
[Google Pixel 6 Pro] sronweb:
I have a rooted and unlocked Pixel 6 Pro, with last alpha magisk and I'm going to install June's OTA update.

This is my first time I do it, so if I understand correctly would be just required to follow these steps?

Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.

Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update

Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device

I see other users need to patch the update before but it should not be required with these steps?

Thanks
[Google Pixel 6 Pro] V0latyle:
What do you mean "patch the update before"? These instructions are correct; Android system downloads and unpacks the OTA, then installs it to the inactive slot; when the system reboots, it switches to the updated slot.

When you use "Install to inactive slot" in Magisk, it patches the boot image in the inactive slot. So, the idea is, you install the update, but before you reboot to the updated slot, you use Magisk to patch the new boot image, so you should seamlessly boot into the updated slot with root.
[Google Pixel 6 Pro] sronweb:
Thank you for the reply. Now I understand what you mean, but something went wrong, in the last step, which is flashing of magisk, I have selected the canary version which was saved, and then, after flashing the phone stuck for while with Google logo. When I rebooted i see it shows that the device is corrupted.

I could reboot the device but actually I lost root, I'm checking if I can get it without wiping again from scratch the device....

If I try to flash Magisk.zip then I get the message "unsupported image format", I guess I messed up....
[Google Pixel 6 Pro] roirraW "edor" ehT:
There have been many cases where users have gotten the corruption problem. Sometimes flashing an old boot.img (for example, from May) will fix it. If trying to flash the full firmware zip (with -w removed so it doesn't wipe your phone) doesn't help, you can always try

Official Google Android Flash Tool

(OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).

Many, many others have found that site to fix things that even the full firmware zip didn't fix.
[Google Pixel 6 Pro] sronweb:
Thanks for the suggestion. I'm going to start flashing from Flash Tool and If I select June build, disabled Lock, then Flash
[Google Pixel 6 Pro] V0latyle:
Make sure you are following the instructions in the guide. Do not try to substitute your own ideas. The only way Magisk can be "flashed" is via a custom recovery such as TWRP, which to my knowledge has not been ported to Android 12 or the Pixel 6.

Also, if you're using an alpha version of Magisk, I suggest that you use the official Canary. Not all alphas have the necessary fixes and updates.
[Google Pixel 6 Pro] Lughnasadh:
Confirmed fixed with today's release of Stable 25.1 and Canary 25101. No problems updating via direct install.
[Google Pixel 6 Pro] roirraW "edor" ehT:
safetynet-fix v2.3.1 is released.
[Google Pixel 6 Pro] fil3s:
HuskyDG bootloop saver now allows you to patch the boot.img

Magisk modules will remain if you update your system and patch boot.img again

If you have any incompatible modules, this will trigger your device to not boot. Patching boot with Husky DG bootloop saver will survive a system update

GitHub - Magisk-Modules-Alt-Repo/HuskyDG_BootloopSaver: Protect your system from bootloop caused by Magisk modules.

Protect your system from bootloop caused by Magisk modules. - GitHub - Magisk-Modules-Alt-Repo/HuskyDG_BootloopSaver: Protect your system from bootloop caused by Magisk modules.

github.com
[Google Pixel 6 Pro] mcwups1:
Anyone been able to get V4A to work after June update? I keep getting a "No Driver Found" message and it DL's and reboots, but does it over and over.

TIA
[Google Pixel 6 Pro] punishermoose:
I just did the OTA sideload update method and I'm having an issue getting my P6P to boot from fastboot using the newly created patched boot.img. The boot sequence starts and the "G" spins up, progess bar is moving, but then it just goes back to the unlocked bootloader warning and then boots normally giving no root. After boot, opening Magisk Canary25101 only presents with "patch a file", which I already did to create the patched boot.img. I used the boot.img file found in the raven-sq3a.220605.009.b1-factory-157e2284.zip.

On another note

I would also like to know if this is a problem that others are having, otherwise rooting my phone is pointless; the only reason I bother is for V4A.
[Google Pixel 6 Pro] Lughnasadh:
Do you have any Magisk mods that may need disabling and updating to be compatible with the Junes security patch? You can flash the patched image and then boot into safe mode and then reboot and that will disable all your mods. If you can boot up after this with the patched boot image you likely have a mod that needs updating.
[Google Pixel 6 Pro] punishermoose:
I had usnf, acp, aml, v4a, systemless hosts (although I wasn't using adaway). All were disabled, and I can no longer see any of them through magisk, because it is not installed properly (no root).
[Google Pixel 6 Pro] Lughnasadh:
When you flashed the patched boot image in fastboot, are you using the latest Platform Tools?
[Google Pixel 6 Pro] punishermoose:
Yes, I just downloaded the latest set before beginning the process today.

Also, just to make sure I have my head around this, conceptually; I m not actually "flashing" the patched boot image, just using it as a placeholder to kickstart my device, right? Otherwise booting would just fail and not fall back to the non-patched boot image. Please don't be offended, it seems like I'm learning this all over again and want to make sure I get it right.
[Google Pixel 6 Pro] fil3s:
Read my post here 😃

Post in thread 'Android 12 (Viper4Android)' https://xdaforums.com/t/android-12-viper4android.4307163/post-87114613
[Google Pixel 6 Pro] mcwups1:
Does it work for Android 13 too?
[Google Pixel 6 Pro] fil3s:
No only 12x
[Google Pixel 6 Pro] mcwups1:
Thank you.

Unfortunately, I'm on 13 after the update. Appreciate your suggestion though.
[Google Pixel 6 Pro] Lughnasadh:
Well, you can temporarily root by using

fastboot boot <nameofpatchedbootimage>

and then do a direct install after you boot or you can flash it using

fastboot flash boot <nameofpatchedbootimage>
[Google Pixel 6 Pro] HolGORE:
Short question:

Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.

What means modify the system here? Don't all modules modify the system? I have basic call recorder, disable ipv6 and safetynet fix modules. Do they modify the system?

Thanks
[Google Pixel 6 Pro] roirraW "edor" ehT:
For what it's worth, you don't have to uninstall the Magisk Modules. Just disable them. It's good practice just to disable all Magisk Modules before you flash an update, and be prepared that after you re-enable them, the phone might boot loop if one of the modules needs updating to work with the latest OTA.

If the phone does boot loop, then use Safe Mode which will disable all Magisk Modules, then you can boot normally.

Practically speaking, it doesn't sound like you have any modules that would likely cause you a problem, but famous last words, so disable them all.
[Google Pixel 6 Pro] WhoIsJohnGalt1979:
Best advice that I have incorporated in my monthly update discipline. Manually flash the bootloader and radio and then flash rom.zip. This leaves you in the fastbootd screen. Boot back to bootloader and boot with patched .img and direct install from magisk.
[Google Pixel 6 Pro] punishermoose:
I will try that and report what happens. Thanks for the advice, all.
[Google Pixel 6 Pro] Cubox.:
Hi,

Are you guys getting L1 Widevine? Would the L1 Widevine stay if you stock flash and lock the bootloader back?

Thanks
[Google Pixel 6 Pro] State.of.mind:
Curious question. When it comes to updating the device, how do you know what Factory image to select? Do you select the factory image based on your current provider? For example, i am using an unlocked P6P (purchased through google), but I am a Verizon customer. Would I select the Factory Update that is compatible with Verizon ie (SQ3A.220705.003.A1, Jul 2022, Verizon, Verizon MVNOs)??
[Google Pixel 6 Pro] WhoIsJohnGalt1979:
Hear! Hear!

You can use any of them as they are all the same, but if there is a carrier specific version available, irrespective of whether you have purchased it from Google or the carrier, it makes more sense to go with the carrier specific version.
[Google Pixel 6 Pro] Nergal di Cuthah:
That

I'm on factory unlocked on vzw and, when there is one, use the vzw build
[Google Pixel 6 Pro] V0latyle:
Generally, the carrier named variants contain various fixes/improvements in the baseband image for that specific network, based on the carrier's infrastructure and channel scheme. AFAIK only the baseband is different; everything else is the same as the ROW firmware.

The best way to know for sure would be to compare the various images with a hash checker.
[Google Pixel 6 Pro] HolGORE:
so i disabled all modules.

rebooted the device

removed magisk, installed the new july update and installed magisk at the inactive slot, like described in the tutorial on first page.

im using magisk 25.1

now i'm stuck at the Google Logo.

any idea what i did wrong?
[Google Pixel 6 Pro] roirraW "edor" ehT:
I can't advise as to the OTA method, because I always flash the full factory image, which is what I would suggest (very important - follow the directions in this guide Spoiler: Update and Root Factory Image, and remove the "-w" from the flash-all.bat or flash-all.sh, depending on whether you're using Windows or Linux).

Alternatively, and often enough it's saved users' bacon when all else fails, use the Spoiler: Update and Root using the Android Flash Tool method.
[Google Pixel 6 Pro] HolGORE:
looks like it was the USB cable, that was connected. it was connected to a usb charger, not even to a pc.

after unpluging it the phone started, wtf...
[Google Pixel 6 Pro] V0latyle:
How'd you do that?!

@HolGORE I got a bootloop as well when I tried to use the inactive slot method on my wife's 5a. I'm not sure what's wrong with it. Until the problem is discovered, I'd recommend updating using the method of your choice, then manually patching and flashing the new boot image.
[Google Pixel 6 Pro] HolGORE:
my phone is starting again, but looks like root is gone.
[Google Pixel 6 Pro] roirraW "edor" ehT:
This doesn't work with every webpage, but for pages that it does work on like this thread, in Chrome (I'm sure in other Chromium-based, and other browsers as well), just highlight the text you want to create a link to, right-click on top of the highlighted text and choose "Copy link to highlight".
[Google Pixel 6 Pro] HolGORE:
i had to repack the boot image with the magisk app and flash it, now i have root again with the newest update
[Google Pixel 6 Pro] V0latyle:
Check your current system version, you can see it at the bottom of the notification windowshade. My guess is that when the system bootlooped, it reverted to the old slot. You will need to re-root by manually patching the boot image. Since you want to update, I suggest doing so using the factory image method. Looks like you already did that. Double check to make sure you are indeed on the newest update, since the system may have reverted to the old slot after bootlooping.

Neat trick!
[Google Pixel 6 Pro] HolGORE:
Just realized it reverted lol. I guess I try it with the factory method
[Google Pixel 6 Pro] almahix:
I don't know how I did it or how to restore the Pixel 6 pro 12 recovery. I can boot into recovery but pressing the buttons doesn't bring up the menu so I can side load. There is just no response. In deparationi used the Android tools to fresh install the new factory image, but it didn't restore the recovery. HELP!
[Google Pixel 6 Pro] V0latyle:
This thread is specifically for the Google Pixel 6 Pro.

Here is the OnePlus 6 subforum.
[Google Pixel 6 Pro] Nergal di Cuthah:
This is the pixel 6 pro forum not oneplus 6 pro, you'll receive better help posting to the correct board. Cheers