yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] roirraW "edor" ehT:
You can flash any of them, and there will be no damage. As always, I'd always have a backup of anything important first. The most common possible outcome you might have is not as good a signal, and the very worst possibility is you might have to factory reset. Especially right after the P6P came out, I remember reading about some users here trying some of the alternate versions and some of those having better luck with their signal using a version of the firmware that technically wasn't made for where they were using the phone.

Me, I would be wary of flashing one not made to work in my area or at least be prepared to factory reset if you flash the "wrong" one, then later re-flash the "right" one and if things behave wonky after that.
[Google Pixel 6 Pro] sjgoel:
Any guides? I had problem when I tried to do so last month. Had to start form zero.
[Google Pixel 6 Pro] roirraW "edor" ehT:
At the top of the list of threads in this section, click the yellow How To Guide quick filter, and there are several guides.
[Google Pixel 6 Pro] sjgoel:
Thanks, that helps !
[Google Pixel 6 Pro] elknetld2kil:
Hi, I'm having an issue, I did the update like I always do (the sideloading method) but when I went to flash the new patched image I made from the factory zip it bootloops. I ran the OTA update again and that time tried just booting the patched img file but it goes to boot but then reboots and goes back to the original unrooted image.

Am I missing something here? trying to see if I can do something else before I accidentally brick this device.
[Google Pixel 6 Pro] Nergal di Cuthah:
I had trouble with sideloading ota this update. Used the flasher tool, booted to system, patched the boot.img and fastboot flashed patched boot. Success. I wonder if something is off with the ota (i used the vzw one as i'm on vzw network)
[Google Pixel 6 Pro] elknetld2kil:
That's but I did but the OS just won't load with the patched boot flashed
[Google Pixel 6 Pro] hpower1:
Not sure if this is new to July update, I didn't notice it in June or on Beta 3.3 but you now have the choice to keep the vibrate icon up all the time if you want it. I keep on vibrate and like to see it, so this is a welcome option to have.
[Google Pixel 6 Pro] Forsh:
Hi everyone. I was wondering, does anyone know - does the A13 beta update roughly around the same time as the A12 stable? I.e. at the beginning on each month, and then throughout the month as necessary. While I'm here - I've found A13 to be very buggy and drain a lot of battery + have poor signal and dropped calls, for a couple months. It wasn't like this at first. I'm thinking of doing a factory reset on A13. Is there a guide for me to get my phone back to how it was before the reset as fast as possible? Anything I should do before the reset?

Thank you
[Google Pixel 6 Pro] roirraW "edor" ehT:
The first Beta 3 of Android 13 came out June 8th, which was a Wednesday. I don't really know if there is necessarily any typical release date of the Betas. 3.1 June 10th, 3.2 June 16th , and 3.3 on June 27th. Another source for this info.

Beta 4 is supposed to come out this month, and maybe someone knows when more precisely, but not me. :)

Mmmmm...no, I don't think there's really a guide for how to get it back as fast as possible.

My personal advice for it:

I use Nova Launcher Prime, so I do backups anytime I change my home screen or app drawer/tabs setup, so widgets and app icons and other Nova-specific configurations are easier to restore.

Go to Android Settings and use Settings' search box for Backup. Make sure that your Google account is set up to backup your apps (and app data for the apps that developers have configured to use Google's Backup API). Make sure things are backed up. Note, this doesn't backup the apps themselves, only the list of apps, so only applies to apps installed from the Play Store. As I said in parentheses, developers have to choose to integrate Google's Backup API into their app, and those apps only will get their app data backed up into Google's cloud.

If you're rooted also, then you could use something like Swift Backup to backup to the cloud. I do so, although I still restore as much as possible through Google's backup, and I only restore through Swift on a case-by-case basis, as needed when I discover an app that's tough to set back up doesn't have it's data restored by Google.

If you've used Google Photos to backup your photos to Google's cloud, then hit the button in Google Photos to free up space. This will automatically and only delete your local copies of photos and videos that it's already backed up.

Once that ^ is done, look at your internal storage with your favorite File Manger and see if there's anything left that you want to back up manually, since a factory reset will wipe everything. Copy them to your computer or a flash drive.

When you're just starting the out of the box setup after the reset, when it asks you if you want to use a cable to restore things from an old phone, choose No, and that will lead you to Google's cloud backup where you can choose to restore everything, or you can select what you want to restore.

I think you can figure out the rest.

I've now added this to my guide thread since I went to the trouble of typing it out. :D
[Google Pixel 6 Pro] Forsh:
You're the best!
[Google Pixel 6 Pro] stryver:
I don't understand why it's suddenly a problem, I always update and restore root no problem. This update somehow failed and lost my root access.

View attachment 5660355
[Google Pixel 6 Pro] roirraW "edor" ehT:
We would need to know what method you use. An OTA method? It seems a third or a quarter of the time, OTA methods have problems.

I always flash the full factory image, then go back and flash the Magisk'd boot.img once everything non-root is working 100% after the update.
[Google Pixel 6 Pro] roirraW "edor" ehT:
This may be posted elsewhere too but it's important enough. Time to deep-freeze archive Nova Launcher version 7 (and the Prime activator, and even the Nova Google Companion) APKs just in case!

I had talked to Kevin (at)teslacoil / developer of Nova possibly even before Nova was released - I don't remember. At the time I was using his WidgetLocker back on Android 2.1.

Nova Launcher

The premier custom launcher for Android, loved by over 50 million.

novalauncher.com

I also un-opted out of their Beta program and deselected both apps from auto-updating.
[Google Pixel 6 Pro] Ghisy:
Oh come on! Not Nova! 😢
[Google Pixel 6 Pro] Ghisy:
View attachment 5663289

I expressed my concerns on their Discord and they are being reassuring about it. I just hope they're being honest.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thanks for sharing the information. I'll withhold judgment, but I'll also likely keep Nova from being updated give or take a year unless there's some overriding need to update due to new behavior or bugs when using it with future Android versions. It's a little paranoid, but I've never yet seen good come out of this. Sure, it makes me feel better Kevin and the other one are still in charge and involved, but in the end, they are now not their own bosses, so it may look good initially but we'll see how it does in practice.

I'm sure no one is lying. I'm sure Chainfire wasn't lying about what was expected from the company that bought SuperSU, and I know it was a different situation but we'll just see. I hope for the best but expect the worst.
[Google Pixel 6 Pro] Ghisy:
Yeah. Same. I updated to 8.0.1 to give it a try. In the worst case, I have a backup of v7.

But so far, things seem OK.
[Google Pixel 6 Pro] TotallyAnxious:
Mx player was bought by a media company and they still update the pro version without putting in any ads or doing anything unsavory.
[Google Pixel 6 Pro] roirraW "edor" ehT:
That's good to hear. Thanks!
[Google Pixel 6 Pro] TotallyAnxious:
The pro version remains a video player only. Though in India, my understanding is the free version of mx player is now a streaming service. Idk if the Indian market gets access to the ad supported free app or pro app.

MX Player Success Story

All you need to know about India's leading OTT Platform, MX Player. MX Player Founder, Funding, Revenue Model, Competitors, Growth

startuptalky.com
[Google Pixel 6 Pro] Lughnasadh:
From Nova's Discord chat, for what it's worth...

View attachment 5663541
[Google Pixel 6 Pro] Lughnasadh:
Here's some other news...

"DNS-over-HTTP/3 (DoH3) support was released as part of a Google Play system update, so by the time you’re reading this, Android devices from Android 11 onwards1 will use DoH3 instead of DoT for well-known2 DNS servers which support it."​

*Hope it's ok to post this in this thread Rode Warrior.

DNS-over-HTTP/3 in Android

Posted by Matthew Maurer and Mike Yu, Android team To help keep Android users’ DNS queries private, Android supports encrypted DNS. I...

security.googleblog.com
[Google Pixel 6 Pro] MrBelter:
Bugger, i have used Nova for longer than i care to remember, I'll be keeping a close eye on what people are saying about it now :(
[Google Pixel 6 Pro] hello00:
As if your privacy and data is not already shared by other apps like Facebook, WhatsApp, Instagram, etc. What are they gonna share? Texts and pictures of my friends. Share the pictures and texts for all I care
[Google Pixel 6 Pro] MrBelter:
It is the principal of it though, people bought / used the app in good faith. If you use Facebook, WhatsApp or Instagram you know exactly what you are letting yourself in for (or you should).
[Google Pixel 6 Pro] roirraW "edor" ehT:
Magisk Stable v25.2 is out.

Release Magisk v25.2 · topjohnwu/Magisk

Maintenance release fixing various issues. [MagiskInit] Fix a potential issue when stub cpio is used [MagiskInit] Fix reboot to recovery when stub cpio is used [MagiskInit] Fix sepolicy.rules syml...

github.com

Direct link to downlod: https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk

2022.7.20 Magisk v25.2

The Magic Mask for Android

topjohnwu.github.io

Magisk Changelog

The Magic Mask for Android

topjohnwu.github.io
[Google Pixel 6 Pro] Utini:
Just updated without any problems.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Magisk v25.2 marks the beginning of the project's Rust-ification

The latest version of Magisk stable release (v25.2) comes with a plethora of bug fixes for MagiskInit and a Rust-powered logging interface.

www.xda-developers.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
Google Camera 'temporarily disabled' Frequent Faces on the Pixel

With the Pixel 4, Google Camera gained a "Frequent Faces" feature to "identify and recommend better shots of the faces you photograph...

9to5google.com
[Google Pixel 6 Pro] Lughnasadh:
Since this topic was posted and discussed in this thread last week, I'll leave this here for those who may be interested...

https://twitter.com/i/web/status/1552004647921016834
[Google Pixel 6 Pro] The MAZZTer:
So with June 2022 and Magisk 24.1 and previous on my Pixel 6 Pro I have been using --disable-verify and --disable-verification as I thought they were needed (and I have had MULTIPLE factory resets needed when I thought I had done everything correctly).

For some reason with July 2022 and Magisk 25.2 if I disable verify and verification my phone does NOT boot with either Magisk patched or stock kernel. Probably something changed in July 2022 Android?

Anyway I kept them enabled as per the suggestion in the first post of the thread and everything is fine and dandy now. Still not sure what changed.
[Google Pixel 6 Pro] biTToe:
See the second post in this series

---

Disabling Verity and Verification isn't required except for use with some custom kernels, but just rooting those custom kernels with the latest Magisk Stable v24.1 or higher should make them not require disabled Verity and Verification anymore.

A reminder that disabling Verity and Verification, at least if you've never disabled them before, will cause you to need to factory reset the device otherwise there will be corruption.

The usefulness of having Verity and Verification enabled

(now that it's not needed for root but IS still required for some custom kernels):
[Google Pixel 6 Pro] Lughnasadh:
When you updated to 25.2 were you on the Android 12 July stable build with verity and verification disabled?
[Google Pixel 6 Pro] Utini:
Yes, disabled.
[Google Pixel 6 Pro] Lughnasadh:
The user in the post above this had no problems using Magisk 25.2 on the July build with verity and verification disabled, and I haven't seen anyone else have problems when verity and verification were disabled on the July build (or Android 13 betas for that matter), so the problem you encountered may have stemmed from something else.

It would also seem kind of strange that Google would change something on the July build (likely last build of Android 12) that would affect being able to boot with verity and verification disabled but not have those same changes incorporated in the Android 13 betas.

I think something else unrelated to disabling verity and verification was going on.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Update not quite here yet, but here's the Pixel Update Bulletin—August 2022:

Pixel Update Bulletin—August 2022 | Android Open Source Project

source.android.com
[Google Pixel 6 Pro] Lughnasadh:
Android Security Bulletin for August as well...

Android Security Bulletin—August 2022 | Android Open Source Project

source.android.com
[Google Pixel 6 Pro] Lughnasadh:
Also, regarding Android 13, there's this...

https://twitter.com/i/web/status/1554154942050537472
[Google Pixel 6 Pro] roirraW "edor" ehT:
Now they're just messing with us. 😂 "What do you mean, you didn't click the 'Publish' button?"
[Google Pixel 6 Pro] hpower1:
I'm going to keep trying these updates, and A13 when it drops but for now I have finally had to move off my pixel 6 pro. I lose connectivity every time I leave my house, at least once, and one place I do some work 2x per week my phone doesn't work there at all. I have moved back to my pixel 4 XL but also got a One Plus to use too. I really want to love my pixel 6 but it just doesn't work for me. I even bought a regular pixel 6 to try, same thing.
[Google Pixel 6 Pro] roirraW "edor" ehT:
That is too bad. Hopefully, Google will surprise us all positively in the next year or two.
[Google Pixel 6 Pro] hpower1:
I agree, I hope so too. I will watch the 7, but I probably won't buy at launch again. I hate that I have issues, as I really love the phone otherwise.
[Google Pixel 6 Pro] MArtyChubbs:
Wish I never sold my 4XL. This phone frustrates me a few times every week. Mainly, voice dictation.

Looking forward to A13
[Google Pixel 6 Pro] LLStarks:
The 6a beta modem is the same version as the 6 beta modem. Guess they'll share a dev track.

And yes, I'll probably buy a 7.
[Google Pixel 6 Pro] MArtyChubbs:
Love it or hate it, me too. I've had every non a pixel but the 5...
[Google Pixel 6 Pro] Amd4life:
Yep uninstalled and will consider different apps moving forward. Hey it was a good run.
[Google Pixel 6 Pro] Ghisy:
To be honest, I'm having a hard time moving on from my 4 XL. My 6 Pro has been sitting in its box since I got it months ago. I can't seem to make the switch 😅 (mainly because I'm not the biggest fan of Android 12)
[Google Pixel 6 Pro] roirraW "edor" ehT:
The Pixel's August update looks to have been delayed [U: New July patch for 6/Pro]

Google usually rolls out the latest Android security patch to Pixel phones on the first Monday of every month. The Pixel August update...

9to5google.com

(even Verizon published details minimal information about an expected update yesterday)
[Google Pixel 6 Pro] spotmark:
It's out. Mine's installing now. Doesn't look like images are available yet, though.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Woah! Not August but two new July images here. (not saying that @spotmark isn't getting the August OTA)

12.1.0 (SQ3A.220705.003.A3, Jul 2022, Verizon, Verizon MVNOs)	Flash	Link	5651ee94a61222e2c03ca55b76f4aa452c5eed9e43ad8aabb7060739177e1689
12.1.0 (SQ3A.220705.004.A1, Jul 2022, Softbank)	Flash	Link	6b60f5a6401b35c635408494b54323825a8bcf5c85384a7cc2c241849a2d7413
[Google Pixel 6 Pro] Lughnasadh:
This makes total sense 🙃
[Google Pixel 6 Pro] Nergal di Cuthah:
Does anyone have a diff between these and the previous july

Also what the heck is with the Softbank version?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Google Search for Softbank - looks like a Japanese carrier. Maybe? Ah, here they are - Googled for softbank carrier:

Also interesting if this is up-to-date:
[Google Pixel 6 Pro] Nergal di Cuthah:
Don't know that I'd use a financial organization's mobile carrier but i guess someone does lol
[Google Pixel 6 Pro] roirraW "edor" ehT:
Check my edited post. :D But yeah, probably still related to the financial business somehow.

Maybe some mouse-clicks got stuck in Google's cache and they're just now starting to catch up from last month. Queue up for the left mouse-button!
[Google Pixel 6 Pro] Ghisy:
Yeah, Softbank IS a Japanese carrier. I don't know why Google is pushing a July update now for this carrier.

Meanwhile, the August patch is nowhere to be found... Sometimes I wonder who's in charge of Android updates at Google because, yeah. 🙄
[Google Pixel 6 Pro] roirraW "edor" ehT:
Can you confirm the update you got was an August one?
[Google Pixel 6 Pro] spotmark:
It just got done rebooting. Still says, July 5, but it downloaded and installed something.
[Google Pixel 6 Pro] hpower1:
I'm gonna try the newest July update for verizon, see what that does for me.
[Google Pixel 6 Pro] Utini:
And where is the update for the rest of the world besides JP and Verizon? :S
[Google Pixel 6 Pro] roirraW "edor" ehT:
The Japan and Verizon updates aren't "the" August updates, only new July updates, so I'm ambivalent.
[Google Pixel 6 Pro] swieder711:
I am not going to bother with the second July update. Hopefully the August update will be here soon. My guess is that it will arrive on Monday Aug 8.
[Google Pixel 6 Pro] roirraW "edor" ehT:
And...a THIRD new July update:

12.1.0 (SQ3A.220705.003.A3, Jul 2022, Verizon, Verizon MVNOs)	Flash	Link	a9bb77503e16c760e0da4291c6b02c70ecfb7310fdf85a22792b521dbb16583e
12.1.0 (SQ3A.220705.004.A1, Jul 2022, Softbank)	Flash	Link	1fb143dda098f1a391eca4ce9c137e2d32f27d3a197beeb580c669753ad80865
12.1.0 (SQ3A.220705.004, Jul 2022)	Flash	Link	b6f37423ff23a90021942d3bfd9d1e9605ab13431613fffc15375f3db5ec6c53
[Google Pixel 6 Pro] Lughnasadh:
“August 2022 update for all supported Pixel devices will begin rollout in the coming weeks.”

Google rolling out GPS fix for Pixel 6/Pro and 6a, August update coming [U: More builds]

This month's odd Pixel update situation continues, with Google announcing a small update for the Pixel 6, 6 Pro, and 6a to address...

9to5google.com
[Google Pixel 6 Pro] Ghisy:
So the global version is SQ3A.220705.004 I guess? Has anyone flashed it on top of the EMEA July build?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yes.

I have not. I'll just wait for the proper August - or September.

Google Pixel Update - August 4, 2022 - Google Pixel Community
[Google Pixel 6 Pro] Utini:
Worked for me.
[Google Pixel 6 Pro] Ghisy:
Seems like Google is planning an EMEA build as well but images haven't been published yet.

I found the build numbers on 9to5Google :

Global (Unlocked)

Pixel 6: SQ3A.220705.004

Pixel 6 Pro: SQ3A.220705.004

EMEA (DE, ES, FR, IE, IT, UK)

Pixel 6: SQ3A.220705.001.B2

Pixel 6 Pro: SQ3A.220705.001.B2

Softbank (JP)

Pixel 6: SQ3A.220705.004.A1

Pixel 6 Pro: SQ3A.220705.004.A1

Verizon (US)

Pixel 6: SQ3A.220705.003.A3

Pixel 6 Pro: SQ3A.220705.003.A3

AT&T, T-Mobile (US)

Pixel 6: SQ3A.220705.004

Pixel 6 Pro: SQ3A.220705.004
[Google Pixel 6 Pro] roirraW "edor" ehT:
Fourth new July image (EMEA) is out:

12.1.0 (SQ3A.220705.003.A3, Jul 2022, Verizon, Verizon MVNOs)	Flash	Link	5651ee94a61222e2c03ca55b76f4aa452c5eed9e43ad8aabb7060739177e1689
12.1.0 (SQ3A.220705.004.A1, Jul 2022, Softbank)	Flash	Link	6b60f5a6401b35c635408494b54323825a8bcf5c85384a7cc2c241849a2d7413
12.1.0 (SQ3A.220705.004, Jul 2022)	Flash	Link	112d4f32aeaac5352596837b2b71cb94ffd57b4c515264d776921c42fd9164be
12.1.0 (SQ3A.220705.001.B2, Jul 2022, EMEA)	Flash	Link	2ee23ef4941d11d37edfeb0d7a4c60a7298385307b24b157642c8353da8edb26
[Google Pixel 6 Pro] Nergal di Cuthah:
to be sure, only emea is new for fourth, correct?
[Google Pixel 6 Pro] Cornloaf:
I have flashed 12.1.0 (SQ3A.220705.004, Jul 2022) on my phone twice and I get the corrupted system warning. Went back to the .003 update and that fixed it. I will wait on the August update before trying again. I am still getting bugged about installing the OTA for the GPS fix.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Correct. :D
[Google Pixel 6 Pro] Ghisy:
The best practice to update is to use the factory image and remove the -w in the flash-all.bat so your device doesn't get wiped.

Never had a problem so far updating this way.
[Google Pixel 6 Pro] Nekromantik:
if august build not out in 2 weeks then will probably flash the updated July build but why release new July build if August is "coming weeks"
[Google Pixel 6 Pro] Nergal di Cuthah:
Gps is a vital aspect of the device (think if your gps is off and you call emergency (911, 999 or what ever)) so they pushed it. That's my guess at least
[Google Pixel 6 Pro] Cornloaf:
I detailed my steps in the main Magisk Pixel 6 root post. I did the OTA, OTA Sideload, and Factory Image (with -w removal) and all three methods caused my device to say the OS was corrupted. I have never had root issues like this before.
[Google Pixel 6 Pro] snovvman:
I've seen similar with past Pixels as well, though I don't recall if it updated to the VZ flash or just downloaded VZ specific apps.

There was also belief that the Verizon "locked" versions had slight hardware differences and that was the reason for the VZ-specific image. When I flash the non-carrier-specific version and use a VZ SIM, it did download VZ system apps (carrier, etc.) but did not update the firmware to the VZ version. At least that is what I recall.
[Google Pixel 6 Pro] buschris:
leave out the #. Don't know why anyone would type that
[Google Pixel 6 Pro] rester555:
Will patching the boot image of the P6 and Pro binaries work on devices that took the security OTA Day 1?
[Google Pixel 6 Pro] Cares:
I'm coming from a 4XL so I never had to deal with disabling verity and verification. Will this automatically wipe my device if I do it? I really want to avoid that.
[Google Pixel 6 Pro] sean222:
Well that was fun. Not. Had my Pixel 6 Pro up and running with unlocked bootloader yesterday.

Factory images dropped today and I figured I didn't have to wipe again, but I had to, damn verity step.

So from only unlocked bootloader, I did the vbmeta and verity disable and flashed the patched boot, rebooted and got an error that I had to factory wipe, so I did so. After that boot, there was no root........

So I did the flash-all and completely wiped my device. Then did steps all over again, and it worked.

I'm now up and running, fully rooted. So happy to restore my backups with root :D
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hopefully someone in the other thread who knows will answer.

I know that unlocking the bootloader wipes your device. As far as disabling verity etc, you'd be best asking in the root-specific thread (no sense in that OP and myself duplicating efforts): Firmware is out! Get your root on!

I haven't rooted yet, I am on the OTA, and I'm curious about this as well. I figured I'd just wait until the firmware is up for the same version I'm running. I have unlocked the bootloader.
[Google Pixel 6 Pro] Zilla0617:
Are you running the Day 1 update or the previous firmware version?
[Google Pixel 6 Pro] sean222:
Previous firmware, which I believe is what is on it straight out of the box. When I unboxed it (just 2 hours ago), I did NOT install any OTA updates. I'm on Telus in Canada, so maybe no OTA update was pushed to me?
[Google Pixel 6 Pro] rester555:
Since he did flash-all my guess is he does not have the Day 1 update.
[Google Pixel 6 Pro] Zilla0617:
Oh ok, that means I can't root because I did the day 1 update and there are no images for it yet