yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Cornloaf:
Has anyone had luck with the GPS patch that came out last week? I went through the steps to uninstall Magisk, install the OTA, install Magisk to the inactive slot, reboot... I get the corrupted image and it hangs on boot. There is no full image file to download and extract a new boot.img. I tried using the July 2022 boot.img, patched it, flashed it and the device rebooted without the GPS fix.
[Google Pixel 6 Pro] Nergal di Cuthah:
What do you mean all the released have a full image to extract the boot from. I just did it yesterday. The easiest wayvto update isnt the uninstall of magiisk. It often corrupts like you described. Use pixel flasher from google. Patch the boot (from the latest full image) and flash it in fastboot
[Google Pixel 6 Pro] Cornloaf:
The update that I got over OTA is not available to download. This was the extra fix outside of the August 2022 update. I normally uninstall Magisk, do the full update without wipe, patch the boot.img file with no issues. Since there is no OTA or Full Image released with this patch, I can't use this method.

GPS fix rolling out to Pixel 6 handsets, August security patch rolling out in coming weeks

Google is rolling out a GPS patch for the Google Pixel 6 phones. The firm will also roll out the August security update soon.

www.xda-developers.com
[Google Pixel 6 Pro] phaino00:
The GPS fix factory image is available. It has a suffix of .004

I believe it was uploaded last Thursday.
[Google Pixel 6 Pro] Nergal di Cuthah:
So it's newer than

Which was released july 20something?
[Google Pixel 6 Pro] phaino00:
Yes. Was released 8/4 I believe.
[Google Pixel 6 Pro] Pbond808:
Fastboot cannot load Master root?
[Google Pixel 6 Pro] Cornloaf:
Yes. The update was pushed August 4. This was the file that I used to patch the boot.img. I am still getting the OTA prompt. I am going to give it another try.
[Google Pixel 6 Pro] Cornloaf:
Downloaded 12.1.0 (SQ3A.220705.004, Jul 2022) and applied. Phone reboots and it gives me a warning that my system is corrupt. Phone will not boot. I attempted this two times and then went back to 12.1.0 (SQ3A.220705.003, Jul 2022) and it took that successfully. I will wait until the August update comes out.
[Google Pixel 6 Pro] V0latyle:
What error do you get?

What process did you follow?
[Google Pixel 6 Pro] Cornloaf:
I get the red text "OS is corrupted" screen, press power to continue and it shows the Google logo and stays there. I have to hold down power/vol for 30+ seconds to shut it off.

I have tried three methods on here and got the same results. First time OTA was bugging me to install the update so I uninstalled Magisk (restored images), ran the update, installed Magisk on inactive slot and rebooted. This was the first time I got the corrupt OS error. I only had the .003 image so I restored that on the device, reapplied root, etc.

The next time I tried to update I used the Update and Root OTA sideload method. Same error with OS corrupted.

The final time (which I tried twice) was the Update and Root Factory Image method. I removed the -w so it would not overwrite my data. This also resulted in the corrupt OS screen.

After the failure with the OTA method, I made sure to have the patched boot.img from both .003 and .004 available just in case I was not able to get the device booted and back into Magisk.
[Google Pixel 6 Pro] V0latyle:
OTAs can be pretty tricky. What version of Magisk are you using? There have bene issues with patching inactive slot prior to 25.2.

I had a similar problem on my wife's 5a when I tried to update via automatic OTA/patch inactive slot. Sideloading the OTA fixed the issue.

Most of the time, the reason why you'd get the Rescue Party screen is because system has detected a problem with the boot image - either the version doesn't match what you expected (like if you tried to boot an old boot image after updating) or there's a problem with the boot header.

You may be able to get running simply by flashing the boot image corresponding to the update. Don't use a patched boot image; focus on getting your device working again.
[Google Pixel 6 Pro] Cornloaf:
I did get the device working again by using the Update and Root Factory Image method and rolling back to 003. I think I will stick with this version until the true August update comes out.
[Google Pixel 6 Pro] V0latyle:
Oh okay, so maybe it's an issue with the .004?

I don't have a Pixel 6 so I can't test this
[Google Pixel 6 Pro] Cornloaf:
I will test again with .004 when the August update comes out so I can just jump forward with that if there are issues!
[Google Pixel 6 Pro] chinghaqa:
Hi V0latyle,i have some qustion by google pixel 6 pro

i come Taiwan my pixel 6 pro is unlock+ROOT

I have a few questions to ask

1. I swiped the SQ3A.220705.001.B1 card version. In this screen, the card has been stuck for a long time. Is it normal reading or really stuck. I updated it before.

I have a few questions to ask

1. I swiped the SQ3A.220705.001.B1 card version. In this screen, the card has been stuck for a long time. Is it normal reading or really stuck. I updated it before.
[Google Pixel 6 Pro] V0latyle:
It does take a while. The OTA package is transferred to the device, which then unpacks it and installs it to the inactive slot. This takes time.
[Google Pixel 6 Pro] chinghaqa:
ㄍ

○K Thanks !
[Google Pixel 6 Pro] chinghaqa:
Can I skip the 0705 OTA version and directly request the upgrade 0804?
[Google Pixel 6 Pro] TiZiO.Cover:
Sorry if I also ask, but despite the date, is

12.1.0 (SQ3A.220705.004, Jul 2022)

the latest Factory Image, i.e. the August update?
[Google Pixel 6 Pro] Lughnasadh:
That's the latest but it's not the August update. That hasn't been released yet.
[Google Pixel 6 Pro] V0latyle:
Yes

It's labelled July, what do you think?
[Google Pixel 6 Pro] fil3s:
I'm not sure if this is related to root or magisk modules, but does anyone experience extreme lag on their p6pro? The phone lagged badly on 12.1 and I thought I was free of it on a13 beta but after installing a few magisk modules, the phone can become unusable sometimes. Anyone else experienced this?
[Google Pixel 6 Pro] Lughnasadh:
Mine runs great with only 4 Magisk mods installed (Busybox, JamesDSP, Substratum & Systemless Hosts). Maybe uninstall your mods and install one by one to see if one of them is the culprit?
[Google Pixel 6 Pro] fil3s:
I uninstalled magisk the phone was really bugging out. Husky bootloop Saver might've been the issue. I'm back on magisk canary with no modules installed
[Google Pixel 6 Pro] heij20032003:
I would like to ask....

if I haven't sideloaded the June update, can I skip the June one and directly sideload the July update?

will this cause any problems? or loss of any function in June update?
[Google Pixel 6 Pro] Xeone221:
Hi everyone, here is the patched boot of the last update.

Build : SQ3A.220705.004

magisk_patched-SQ3A.220705.004.img

drive.google.com
[Google Pixel 6 Pro] Lughnasadh:
I think you mean July. The August update hasn't been released yet.
[Google Pixel 6 Pro] Xeone221:
oops i corrected !
[Google Pixel 6 Pro] V0latyle:
There's no need to share, not everyone is using the same version of Magisk. A mismatch generally won't cause problems, but it's best that everyone patch their own boot image.
[Google Pixel 6 Pro] heij20032003:
if I haven't sideloaded the June update, can I skip the June one and directly sideload the July update?

will this cause any problems? or loss of any function in June update?
[Google Pixel 6 Pro] Dragon Kumera:
Yes you can do that. I have done it multiple times even half a year later.
[Google Pixel 6 Pro] V0latyle:
Note:

However, it's usually possible to run older versions of Android on newer bootloaders.

To test this, if you're planning on updating anyway, download the factory image and update the bootloader only without updating system.
[Google Pixel 6 Pro] Dragon Kumera:
hmm good to know. Also, android 13 is out officially?
[Google Pixel 6 Pro] roirraW "edor" ehT:
https://xdaforums.com/t/android-13-...itory-of-relevant-links.4352027/post-87286923
[Google Pixel 6 Pro] Dragon Kumera:
just looked on google website and was surprised lol. Downloading now.

Side note has anyone elses phone been randomly black screen flickering after 70 hrs up time no reboot?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Not here. I rarely reboot.
[Google Pixel 6 Pro] Dragon Kumera:
It started this past week after updating apps from google play (system webview, carrier and whatever other important ones from android if any. I also updated firefox from v68.0.11 to the latest.

A simple reboot fixed the issue. I am not sure what is causing it though.
[Google Pixel 6 Pro] Kennyeni:
For anyone wondering, I was able to upgrade without issues using the "Stock image + Root" option. No difference from any other update I have done so far! :)
[Google Pixel 6 Pro] V0latyle:
Anyone willing to try to flash an older bootloader anyway? The worst that will happen is the device will reject it; if it succeeds, you can just reflash the new one.
[Google Pixel 6 Pro] Cornloaf:
I downloaded the Android 13 update for my Pixel 6 Pro. If you saw some of my posts from last week, I had issues with corrupted OS with the July 2022 update file (.004).

I did the Update and Root Factory Image method but patched with the flash-all script (removed -w). As soon as I rebooted, it told me that the OS was corrupted. I attempted to boot and it just showed the Google logo and then went dark and showed the battery charging icon even though it was not plugged in. I had to hold down power for 30+ seconds before it would shut off. I was not able to get into Recovery mode (no broken Android icon came up).

I was still able to boot into bootloader and try flashing again. This time I did the Update and Root Factory Image method manually. I flashed the bootloader and the radio even though they both showed as being updated. I did the image update and it immediately gave me an error that the OS was corrupt and it would not boot.

I figured I was screwed because I just read the article that said I could not revert to Android 12. I used the Update and Root Factory method with July 2022 (version .003) and it downgraded the bootloader, radio, and Android image and booted up fine.

Somewhere in all this mess, I tried the Android Flash Tool to upgrade to Android 13 and it kept complaining that it couldn't detect the phone even though I had the drivers and allowed ADB access from Chrome. Tried in bootloader and USB debug.

At this point I tried the Update and Root OTA Sideload method and it worked 100%. I can confirm I am running the Android 13 bootloader and radio.
[Google Pixel 6 Pro] Lughnasadh:
👀👀👀

https://twitter.com/i/web/status/1559398190574714881
[Google Pixel 6 Pro] V0latyle:
So you're running Android 13? Since you had a boot failure before, see if you can flash the July bootloader. If what @Lughnasadh posted is true, it should fail.
[Google Pixel 6 Pro] Dexer125:
Has anyone tried updating with "Update and Root Automatic OTA" method? What is the best way to update to A13 if I use Magisk also with modules installed?
[Google Pixel 6 Pro] V0latyle:
I was not successful on my Pixel 5. The factory image method worked fine.

Depends on the modules. If you use any modules that change system operation or appearance, disable them first. I only have systemless hosts and USNF Displax mod and have never needed to disable those prior to an update.

If you want to be on the safe side, disable all modules anyway.
[Google Pixel 6 Pro] Dexer125:
Oh okay. With Factory image method you will loose data, am I right? I was thinking to flash stock boot image to remove Magisk. Then install OTA and then flash new patched boot image. That should be safe right?
[Google Pixel 6 Pro] V0latyle:
Not to be rude, but most of your questions have been answered in the OP. Please read the instructions for the method you intend to follow, then if you don't understand something, feel free to ask a question.

The factory image method will only wipe data if you use the flash-all script without editing it, because by default it includes the -w argument to wipe data. I personally do not use the script. The update package itself does not wipe data; that has to be commanded either manually or via a script.

If you're unfamiliar with using ADB and the various arguments, I suggest you use PixelFlasher.

You do not have to flash anything if you're going to update via OTA. Simply restore images in Magisk. Follow the instructions under "Update and Root Automatic OTA".
[Google Pixel 6 Pro] Cornloaf:
Read my post a few back and you will see that was the only way I was successful in updating my Pixel 6 Pro to Android 13.
[Google Pixel 6 Pro] crisco654:
I was just about to ask this question lol. Been using the "Update Root and Facotry image" method for every update so far and wanted to know if this was feasible going to Android 13. Glad to know. Thanks
[Google Pixel 6 Pro] chaco81:
I am on A13 with root. All good so far.

-Downloaded factory image. extracted boot and patched it with Magisk.

-Flashed the factory image with the -w removed on the active slot

-without rebooting into system, switched the slots

-Flashed the factory image with the -w removed on the active slot (second slot)

-flashed the patched boot image to both slots

-reboot & profit. Root working as expected.
[Google Pixel 6 Pro] V0latyle:
You can use the --slot=all argument to flash both slots at the same time.

Example:

fastboot update --slot=all --skip-reboot image.raven.buildnumber.zip

Once that finishes you can flash both boot slots at the same time using the same argument:

fastboot flash boot --slot=all <patched boot image>
[Google Pixel 6 Pro] chaco81:
@V0latyle Yes, thats option

i do use the slot=all argument when flashing the patched boot image every month,

never used it for the image update, ill try it on Sept when that security update comes out.

Thanks
[Google Pixel 6 Pro] V0latyle:
Personally that's how I prefer to update, but using the factory image every month kind of makes flashing both slots pointless. The whole purpose is seamless updates: while July is running on slot A, the system can download and extract the August update to slot B, then once complete, reboots to slot B, makes sure it boots, and marks it active. Then, when the September update comes, August is running on slot B and installs the September update to the "other" slot, slot A.
[Google Pixel 6 Pro] Cornloaf:
It sounds like if I put the old bootloader on the device, it will blow the efuse based on these posts. Wouldn't that brick my device?
[Google Pixel 6 Pro] V0latyle:
The e-fuse is blown by a successful boot on the Android 13 bootloader. See this post

Once it's blown, I assume the bootloader will simply reject older bootloader images - meaning you just won't be able to flash an older bootloader.
[Google Pixel 6 Pro] Cornloaf:
Since I am successfully booted into A13 (and rooted), I should be able to attempt to flash the old bootloader and it will fail since the efuse should show as "blown" right now. What should I do to protect myself from bricking my device since I still have A12 on the inactive slot?
[Google Pixel 6 Pro] V0latyle:
Flash the A13 bootloader to the inactive slot. That way if it bootloops back to that slot for whatever reason, there won't be a bootloader conflict. If you want to be extra safe just use --slot=all:

fastboot flash bootloader --slot=all <drag and drop bootloader image>
[Google Pixel 6 Pro] proac:
Is it possible to "refresh two boot slots at the same time with the same parameters" by editing the script? For example, the script is edited as: fastboot flash bootloader --slot=all bootloader-bramble-b5-0.5-8633619.img.
[Google Pixel 6 Pro] proac:
Sorry, the example here is 4A (5G) img
[Google Pixel 6 Pro] V0latyle:
Yes, you could do that.

I have a similar thread in the Bramble forum. This thread is specifically for the Pixel 6 Pro. While the instructions are the same, I'd like to keep support questions in the relevant threads.
[Google Pixel 6 Pro] proac:
link please, thanks
[Google Pixel 6 Pro] V0latyle:
It's at the very top of the OP...

Much easier than that....
[Google Pixel 6 Pro] Az Biker:
You edit the FLASH-ALL (bat) file with the editor on your PC.

Remove the -w and replace it with --disable-verity --disable-verification (leave one space before and after the new text), make sure you SAVE the newly edited FLASH-ALL file.

Then in fastboot type FLASH-ALL

Then follow step 5 of the instructions for patching the boot.img file in Magisk.
[Google Pixel 6 Pro] V0latyle:
You can edit the flash all.bat, or you can use the command I provided in your fastboot command line.

You don't flash the batch file. The batch file is just a command script; if you want to use it, make sure you edit the commands.

If you prefer to type the commands manually, like I do, then type them exactly as I provided.

If this is confusing, I would recommend you use the Android Flash Tool.
[Google Pixel 6 Pro] dr_rick13:
@V0latyle hey man, thanks for putting the guides together, especially the sideload one. I just followed your directions and updated to .037 and I'm rooted again without any issues. Appreciate your work :)​
[Google Pixel 6 Pro] Lw00d:
will using your guide wipe the data? because flash all batch file was not edited?
[Google Pixel 6 Pro] bosox284:
Only if you use the flash-all command. There are two methods using a factory image:

Using flash-all.bat

Using fastboot update

Using flash-all without removing the -w will wipe. Fastboot update will not wipe

@V0latyle - what's the significance of this step? I.e. why do you need to patch the boot image post-update
[Google Pixel 6 Pro] Az Biker:
Using Magisk to patch the boot.img is what allows you to keep root, after you've installed the factory image. Otherwise, flashing the stock boot.img would remove root.
[Google Pixel 6 Pro] bosox284:
No I know that, but V0latyle bolded the patching after the update is completed. I'm trying to understand why patching it after you run fastboot update is of significance. What's the difference compared to if you patched the boot image before updating?
[Google Pixel 6 Pro] Az Biker:
The stock boot.img from the factory image you're updating to must already be installed for it to be compatible when you patch it with Magisk.

You couldn't patch .37 boot.img with Magisk that's currently on build .36...

The .37 build must already be installed in order for Magisk to patch a .37 boot.img.

At least that's how I understand the process.

Hope that answers your question 👍
[Google Pixel 6 Pro] mac796:
Thanks for the guide. I used the ota sideload method and I'm good to go. Had to clear data in play store a couple times but finally took.

Edit. I had to uninstall systemless hosts then I got play store back. Man I hope I can get my AdAway.

Ok edit 2 wasnt able to enable systemless hosts in magisk. Play store won't work for me. I had to install a different version from GitHub now I can run AdAway again. Anyone's else have this problem?
[Google Pixel 6 Pro] V0latyle:
Two reasons:

1. It's a good idea to let the system have a "clean boot" post update

2. It's best to patch the boot image AFTER updating to minimize compatibility issues; some users have experienced boot loops and/or root not working when trying to use a boot image they patched prior to the update

Side note: I understand a lot of folks are using mobile, so you may not be able to read my signature, but I would like to make something abundantly clear. People like me are here providing support on our own time, and very few of us like being messaged directly, nor do we provide any sort of private support.

If you are having trouble with something within the context of this thread, post your question here.

If you are having trouble with a different problem, post your own thread.

DO NOT directly message forum members with your questions; you're either going to get an unpleasant message in response, or you're going to get ignored completely.

@pa.pn2 this means you.
[Google Pixel 6 Pro] mac796:
I'm having some trouble with play store since I updated tonight. I did the sideload method using the safety net module 2.2. It's saying I'm not connected. At first I cleared data in play store and it worked for a bit now it's back to no signal found. I thought it might be addaway but I uninstalled it. Anyone experience this? Also says I'm passing.

Edit. I had to uninstall systemless hosts in magisk. Find a different version so I could use AdAway. Play store wouldn't work otherwise.
[Google Pixel 6 Pro] Cares:
That's not accurate. I patched .37 boot.img while on .36 so that I can flash factory image and magiskpatchedboot in 1 restart. No issues so far.
[Google Pixel 6 Pro] Az Biker:
I'll try this with December update. Would be smoother to do it all in one flash.
[Google Pixel 6 Pro] belair56:
I also did it in one step.

Added --skip-reboot at the end of the flash-all.bat.

Rebooted to bootloader and flashed patched boot.img
[Google Pixel 6 Pro] galaxys:
Nice 👍! That's my go-to way! 😎
[Google Pixel 6 Pro] foobar66:
In OP, 3 methods are listed to upgrade:

1) via OTA

2) via factory image

3) via Google flash tool

Is the result of these 3 methods the same? Why would you prefer one over the other?
[Google Pixel 6 Pro] s3axel:
My understanding is that all will render the same result, the need for just another tool in 3) makes me avoid this - I'd rather use ADB or fastboot.....

On a sidenote: When updating to .037 I tried 2), failed due to some errors and went ahead with 1).... so I am very glad that there were alternatives described ;)
[Google Pixel 6 Pro] mko000:
Just for clarification and because I didn't know at first either: The Android Flash Tool is actually just a website that can connect to your phone using a Chromium browser. So nothing to download or install. Except the platform-tools and drivers, you need those either way.
[Google Pixel 6 Pro] V0latyle:
OTA not recommended, because you either have to download the factory image anyway, or use a separate unpacker to extract the boot image AND vbmeta image from the OTA payload.

Factory image is a better option because you can perform the update and disable verity/verification in the same go - plus you don't have to mess with vbmeta.

Android Flash Tool is the best option for inexperienced users - you don't have to use any fastboot commands or mess with scripts; you just start your phone in bootloader mode, connect to the website, and use the GUI to flash the update. However, you'd still need to download the factory image so as to patch the boot image, at least the first time you root.

Correct. While it does dues temporary storage on your PC, everything is performed via web, so you don't have to download, install, or configure anything else.
[Google Pixel 6 Pro] Superxdaer:
I'm using method 3 and at the flash tool site. My phone is plugged in, it is detected. but the only option available is to "select a build" and there is no way to go to that screen where you disable verity etc. What is going on?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yeah, but they can't count on every thread having the convenience. :)
[Google Pixel 6 Pro] V0latyle:
Can't be bothered to read the OP, either.
[Google Pixel 6 Pro] Dragon Kumera:
So, I found out why i was having black screen glitching on my phone after 50 hr up time.

Seems firefox accessibility setting to auto font enlarge based on phone settings caused the issue.
[Google Pixel 6 Pro] Divine Bicycle:
and i got the same error.
[Google Pixel 6 Pro] V0latyle:
Hmm....How much of your storage have you used up? If you don't have enough free space this could be an issue.

Unfortunately I don't know of a way to fix this other than use the Android Flash Tool to force flash all partitions, which will completely wipe the device
[Google Pixel 6 Pro] Divine Bicycle:
Ok, sorry I didn't update this comment. Here's the thread I opened: https://xdaforums.com/t/urgent-i-ge...hrough-the-factory-zip.4481511/#post-87302245
[Google Pixel 6 Pro] Divine Bicycle:
Apparently, aaccording to DevCheck pro, which I found through Kirisakura's twitter haha, /data has 131 gigs free, and /system has 0 bytes free. Is that normal?
[Google Pixel 6 Pro] V0latyle:
I believe so..../system is supposed to be read only, so the partition is exactly the size of the system image.