yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] swieder711:
My phone is from Google. My carrier is Verizon. Guess that I install the A1 version for the June update.

I wonder why last month there was one version for all carriers and this month there is a separate version for VZ.
[Google Pixel 6 Pro] roirraW "edor" ehT:
More than likely there were more changes to the Verizon radio.img (modem) than they had time to integrate into the universal factory image's radio.img. I'm sure it'll go back down to one image per month in the near future.
[Google Pixel 6 Pro] LLStarks:
There is a difference between subversions for the modem firmware for Verizon compared to the global. But the modem itself looks like it's the same major version as the latest betas.

It's never been clear what the subversion even means. I'm guessing it's just a carrier modem config update and not a core modem config update. I always thought subversion bumps were just timestamp bumps.

It's also not clear how to effectively diff the modems without actually testing them and checking logs. If there's anything beneficial in the Verizon firmware, I wouldn't be able to identify it.
[Google Pixel 6 Pro] hpower1:
i saw those rumor posts, and I didn't get excited, I thought no way. Maybe some day.

I can't remember what I did last time, as I have phone from google but running on VZW. I have been having a ton of network issues lately, so I'm gonna try the VZW variant first this time and see. I hope it helps.
[Google Pixel 6 Pro] Nergal di Cuthah:
Let us know how that goes, i too am on factory unlocked on vzw network
[Google Pixel 6 Pro] hpower1:
I'll be updating today, probably wait for a bit to see if any issues arise with what version of magisk to run
[Google Pixel 6 Pro] Nergal di Cuthah:
Yup that's why I'm waiting a couple of days (i was caught by the initial unrootable December update so i hold off even though i use magisk canary)
[Google Pixel 6 Pro] roirraW "edor" ehT:
I, too, don't have time to be a guinea pig for root, so I wait until multiple other reports come in of successfully updating, rooting, and all being well. :)
[Google Pixel 6 Pro] mystery007:
Magisk 24310, updated by adb, rooted - all is fine
[Google Pixel 6 Pro] Hecke92:
Can anybody upload boot.img? Thanks
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thank you for your report!

Howdy @Hecke92! You can find it by clicking on the blue "General" quick filter at the top of the list of threads in this section:

View attachment 5631843
[Google Pixel 6 Pro] murphyjasonc:
I have an unlocked phone from the Google store. My service is through Spectrum which uses Verizon's towers. I've always flashed the Universal/US firmware version except for once. The one time I flashed Verizon's it seemed like it made my signal a lot worse. I'm still confused about which one I should be flashing though. 🤷🏼
[Google Pixel 6 Pro] cmh714:
I have NEVER flashed the VZW version on any phone and dont have any plans to do so now. Been with VZW for nearly 30 years....my .02
[Google Pixel 6 Pro] roirraW "edor" ehT:
In the end, whatever works best for you is the correct one, so you're good no matter which. Neither one will "break" your phone, you can always switch to the other if you don't like one. In theory, the Verizon one is the one you would want, but only you can determine which one works best, just as you had previously.
[Google Pixel 6 Pro] jcp2:
Pardon my ignorance but is 'sq3a.220605.009.b1-factory-157e2284' for the beta program? I'm on May 12L stable (rooted/ custom kernel) and don't want to be enrolled in the betas.
[Google Pixel 6 Pro] Attinderkahlon:
Is this the stable release update for the QPR ?

I'm asking because I want to opt out of the qpr beta program without a data wipe.
[Google Pixel 6 Pro] Lughnasadh:
Yes, today's June release is the stable release of QPR3.
[Google Pixel 6 Pro] hpower1:
I just updated to June. I have unlocked phone from google, used the verizon build this time as I have been having a lot of network issues. Updated magisk to 24310, did update using factory image. All good!
[Google Pixel 6 Pro] Lughnasadh:
Just so there's no confusion...

Android 12 Beta Program ends with QPR3, Pixel phones will automatically be unenrolled

With the launch of QPR3 today, the Android 12 Beta Program is ending with Google Pixel users not needing to take any further action...

9to5google.com
[Google Pixel 6 Pro] Lughnasadh:
Also looks like the QPR betas will continue with Android 13...

"Android 13 beta program ends in June 2023 with the public release of the Android June QPR and Pixel Feature Drop."--Google

Android Beta Program

Android Beta Program allows you to enroll your Android device for beta releases.

www.google.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'm guessing that yes, that's the Beta. See the top of the first post in this thread for the links to the Verizon and Global Stable June factory images.

Also, see the following:
[Google Pixel 6 Pro] roirraW "edor" ehT:
Magisk Beta v25 is out. BEWARE if you're going to flash a custom kernel on the June stock firmware without Verity and Verification disabled, and use Magisk v25, you may have to jump through hoops to get the custom kernel working. So either stick with Stable v24.3 for now, or look out for info from your favorite custom kernel developer for a modification to their custom kernel package to make it work with Magisk v25.

Releases · topjohnwu/Magisk

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Google Pixel 6 Pro] Lughnasadh:
Kiri has made the adjustments with his new release today (incorporating catntrips hashtree patcher work) and "should" work but hasn't been tested on Magisk 25. He still recommends using Stable 24.3 or Canary pre-24303 at this time to avoid potential conflicts.
[Google Pixel 6 Pro] Paz9:
not sure what happened

flashed the factory image with the -w removed

now it boot loops.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Did you disable all Magisk Modules? Search the OP of this thread for the word "safe" for how to boot into safe mode, which will disable all Magisk Modules, then you can reboot as normal and make sure it works, and the modules will remain disabled until you re-enable them.
[Google Pixel 6 Pro] Paz9:
i thought flashing stock gets rid of the modules?

regardless, i cant enter safemode...
[Google Pixel 6 Pro] roirraW "edor" ehT:
If you don't wipe, it doesn't get rid of anything except root. Did you re-root the new boot.img with Magisk Stable v24.3 and flash the rooted new boot.img? If you didn't re-root, then ignore that part. The modules would still exist but shouldn't do anything at all if the kernel isn't rooted.

If you did re-root you could always reflash the factory image (with -w removed again) and don't re-root if you have to, or just flash the stock boot.img if you hadn't flashed a custom kernel.

It's not easy to get into safe mode, but it can take multiple tries to get used to how to do it.

If all else fails you can search the OP for the link to the official Android Flash Tool (Google's website). This has fixed things that flashing the full factory image didn't fix for many, many users. You can even check/uncheck the option to wipe to try a dirty flash using the flash site first.
[Google Pixel 6 Pro] Paz9:
tried both patched boot image and unpatched.

neither work... will try the android flash tool.. really hope i dont need to wipe.

re-flashed may, and it boots... ill re-download the june zip incase it was corrupt.

edit: the flash tool worked, now im on june, rooted.

not sure why it didnt work with the flash all zip...
[Google Pixel 6 Pro] roirraW "edor" ehT:
Spoiler content hidden.

Edit 2: Solved.

I uninstalled Samsung's driver (which I use for my tablet) even though it worked fine for the April and May Pixel updates. I haven't checked to see if there's an updated Samsung driver yet, but I'll likely just swap back and forth between official Google and Samsung drivers depending on which device I'm flashing, from now on. There definitely isn't an updated Google driver.

I then turned the phone off and back on into Fastboot mode manually.

Then I used one of my other USB-C connections although the one I was trying and failing with earlier I had used at least last month just fine.

None of these things individually would solve the issue. All is good and June just now flashed and booted fine.

Note to everyone (and for myself to remember). The first time launching my hidden Magisk it said I needed to restore the app, but by clicking Cancel and then launching it again, Magisk loaded fine.

I decided to wait to see if Magisk v25 or higher goes Stable, so I'm still on Stable v24.3.
[Google Pixel 6 Pro] jcp2:
Just wanted to say, used Android flash tool (kept verity enabled / kept data / kept bootloader unlocked) rebooted, let phone finish android update, rebooted to fastboot (platform tools 33.0.2) and flashed patched boot.img (slot all) supplied here (big thank you to @Lycidias ) all went smooooth! Easy peasy, light and breazy :) :) Rooted Magsik 24.3 stable with new custom kernel. Thanks @Freak07 kirisakura kernel 3.0.0.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'm surprised (but glad) it works fine with the old Platform Tools (v33.0.1 is the latest, but is also a few months old).
[Google Pixel 6 Pro] jcp2:
Oops. Typo fixed. platform-tools - link for windows (downloads v33.0.2.zip v33.0.2
[Google Pixel 6 Pro] Lughnasadh:
*33.0.1 🙃
[Google Pixel 6 Pro] jcp2:
I clicked on the windows download link, and it came up to save the file as 33.0.2 :unsure: Maybe I'm just lucky ;) Try it direct link . hover over the hyperlink and you can see the address.
[Google Pixel 6 Pro] Lughnasadh:
So it does, but the revision section has it as 33.0.1. Hmm...
[Google Pixel 6 Pro] Forsh:
I'm signed up to the 12.1 QPR beta and currently on the May release. I still don't have the prompt to update to June. Do I need to opt out of the beta to get it or just wait a bit longer for my turn to update? I'd like to update and go back to stable releases without wiping.
[Google Pixel 6 Pro] Lughnasadh:
You don't need to opt out to get it. You should get it in time. With the June Stable QPR3 release, the QPR Beta program for Android 12 has ended. You will automatically be unenrolled in the coming weeks or you can unenroll manually. Thus, once on the June build you will be on the Stable releases.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Interesting, thanks for letting us know. Indeed, they haven't updated their changelog yet.

I now also have Aignes Website-Watcher set correctly to look out for a new version of the zip file, even without an updated changelog.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Platform Tools is updated to v33.0.2 everyone! No updated changelog yet, and 33.0.1 worked for me (and others) for the June update. And thanks to @jcp2 for the discovery.

You'll need this if you're going to unlock the bootloader on your Pixel 6 Pro: SDK Platform Tools (download links for Windows, Mac, and Linux). Note that you can find links to download the tools elsewhere, but I wouldn't trust them - you never know if they've been modified. Even if the person providing the link didn't do anything intentionally, the tools could be modified without them being aware. Why take a chance of putting your phone security further at risk?

You can alternately use the tools from the SDK Manager, but most of us will want to stick to the basic tools-only without the complications of the full development manager.

For Windows, get Google's drivers here Get the Google USB Driver (ADB will likely work while the phone is fully booted, but if you're like me, you'll need these drivers for after you "adb reboot-bootloader", to be able to use ADB and Fastboot.
[Google Pixel 6 Pro] vibrantliker:
wondering if anyone would know why with this update, after rooting, I can't tap to read the notifications in my pull down window? Never happened before.
[Google Pixel 6 Pro] roirraW "edor" ehT:
No idea. Working here. Try disabling all Magisk Modules and see if it still happens.
[Google Pixel 6 Pro] shiftr182:
Same issue here
[Google Pixel 6 Pro] shiftr182:
It was font magisk module :) Updated the zip and it works now
[Google Pixel 6 Pro] Lughnasadh:
Just a PSA for those on Android 13 Beta 2.1:

Starting with Canary 24314, updating to a new Magisk version via direct install results in a bootloop. This behavior has continued with the latest Beta 25/Canary 25001. Patching the boot image, however, allows the phone to boot as expected.

An issue was opened but unfortunately closed as "not planned". So for those on Android 13 Beta 2.1 (and beyond most likely), when updating Magisk you'll want to avoid the direct install method and patch and flash the boot image instead to avoid a bootloop until they decide to resolve this issue.

Patching an already patched img result in a bootloop · Issue #5938 · topjohnwu/Magisk

When patching a stock image and booting it's working fine, When patching an already patched image the device bootloop. Here's what I tested Working: patching a stock file manualy, then booting with...

github.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
See @shiftr182's post for the solution.
[Google Pixel 6 Pro] LLStarks:
That's what that bull**** was? Had to deal with that a few times and eventually figured it out.

Looks like the other issue was closed for a more official one.

`magiskboot` cannot repack boot.img without ramdisk TWICE · Issue #5944 · topjohnwu/Magisk

Device: Pixel 6P Android version: 13 Beta 2.1 Magisk version name: debug Magisk version code: 25001

github.com
[Google Pixel 6 Pro] Lughnasadh:
Yep. Even though she closed that initial issue as "not planned", her and Canyie seem to be working on it, so that's good news. At least she won't close her own issue without fixing it first, you would think.
[Google Pixel 6 Pro] vibrantliker:
figured it out, it was 2 of Tulsadiver's mods (font and no battery icon)
[Google Pixel 6 Pro] Lughnasadh:
Looks like the issue may have been fixed with these commits...

Don't skip backup even if original does not exist · topjohnwu/Magisk@7bf9c74

Close #5945, fix #5944

github.com

Don't backup ramdisk created by Magisk · topjohnwu/Magisk@89ff3c6

Fix topjohnwu#5938, fix topjohnwu#5944

github.com
[Google Pixel 6 Pro] Nekromantik:
are people sticking with 24.2 Magisk instead of updating while still on stock A12 firmware?

or is Magisk 25 fine and does not need you to disable verity and vbmeta?
[Google Pixel 6 Pro] roirraW "edor" ehT:
I've stuck with Magisk Stable 24.3. Others have updated to Magisk Beta 25 and they wrote they updated to June and flashed at least the Kirisakura custom kernel just fine without disabling Verity and Verification. Personally, I'm going to continue sticking with Stable over Beta (or Canary).
[Google Pixel 6 Pro] Lughnasadh:
Depends on your reason to disable verity and verification. Magisk no longer strips avb from fstab so custom kernels had a problems booting on Canary 24303+, including Beta 25, but that has been fixed and incorporated into the kernels/AK3 themselves now so you can use Beta 25 with custom kernels, even though Magisk continues to strip avb from fstab.

There may be other reasons you want to disable verity and verification, such as avoiding the corrupt message issue, although there are now ways to overcome that as well.

Also, it has been discovered that disabling verity alone, without disabling verification, avoids the problems of the current Magisk version as it relates to custom kernels (or modifying any of the avb partitions in fstab) without having to wipe.

I'm one of those who continue to disable verity and verification just because Magisk and Google are continuously changing things, but whether you do or not is up to you. It's not required.
[Google Pixel 6 Pro] Nekromantik:
thanks both

i will wait a while before updating to 25
[Google Pixel 6 Pro] LLStarks:
Beta 3 modem is new: g5123b-101858-220505-b-8545669
[Google Pixel 6 Pro] cmh714:
Since new does not equal better, please let us know your thoughts on that as well! Your insights have been excellent thus far!
[Google Pixel 6 Pro] LLStarks:
Only thing I've spotted so far is the n71_n71 combo being back again. Not very useful.

Vo5G is still present for T-Mobile, Metro, and Assurance. Other T-Mobile MVNOs like Simple, Red Pocket, Tracfone, etc might not be far behind with references like the below.

ims.ims_user_agent_string > T-Mobile VoNR-ePDG-IR94-RTT-ussd #MANUFACTURE#/#MODEL# #BUILD#
[Google Pixel 6 Pro] roirraW "edor" ehT:
Any wagers yet on how soon this new feature will get the axe? Let's see...we have to wait long enough for it to start to become popular, so maybe two years or so, then they can kill it. 😜

Or maybe it will be just unpopular enough that it sticks around forever and Google just never updates it.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Finally the changelog for the SDK Platform Tools 33.0.2 (May 2022):
[Google Pixel 6 Pro] roirraW "edor" ehT:
Magisk Stable v25.1 is out.
[Google Pixel 6 Pro] EastonCo:
What you do in this case is call your provider and tell them you need to unlock the phone for an international sim as you are traveling. Make all the temporary things they do, such as tmobile's app, not work (Just tell them its not working). Eventually they will just unlock it fully.
[Google Pixel 6 Pro] roirraW "edor" ehT:
https://twitter.com/i/web/status/1542633717495083008
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'm guessing we won't have July's update until tomorrow. :)
[Google Pixel 6 Pro] Lughnasadh:
Yep, holiday today so no update.
[Google Pixel 6 Pro] roirraW "edor" ehT:
...Wait for it...wait for it...

Wah. Next Monday?
[Google Pixel 6 Pro] hpower1:
BOOOOOO! :)
[Google Pixel 6 Pro] Lughnasadh:
Oh no! They "usually" release it the next day, or sometimes the next day or two.

Important: The Android Security Bulletins are published on the first Monday of each month unless that Monday falls on a holiday. If the first Monday of the month is a holiday the bulletins will be published on the following work day.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thanks! I didn't realize they ever mention when the next update will come out in those bulletins.
[Google Pixel 6 Pro] Lughnasadh:
I think they only do it when it will be off schedule, like when it's a holiday or for some other reason.
[Google Pixel 6 Pro] LLStarks:
As long as we get the beta tomorrow.
[Google Pixel 6 Pro] Lughnasadh:
Per Mishaal, Beta 4 may be on July 14 when they are scheduled to release NDK r25.
[Google Pixel 6 Pro] DespairFactor:
this is 2021...
[Google Pixel 6 Pro] roirraW "edor" ehT:
You are correct! Thanks for noticing. I don't see any reference to July in June 2022's.
[Google Pixel 6 Pro] Lughnasadh:
Oh crap, lol.

Well, they still usually release it the day or two afterwards. We'll see...
[Google Pixel 6 Pro] DespairFactor:
It will come July 11th, the security bulletin is usually dated the 5th of the month. This could come at any point, which does not indicate the actual release date of the update.
[Google Pixel 6 Pro] Lughnasadh:
Isn't it the security patch levels that are dated on the 5th of each month (and sometimes the 1st as well), but they can be published before that date? For example, May had security patch levels of 05-01 and 05-05 I believe, but they were published on the 2nd and the factory images were rolled out on May 2nd as well.
[Google Pixel 6 Pro] DespairFactor:
no one cares about security patch bulletins, they don't matter. They are always dated the 5th, they usually have one for the 1st and the 5th.

The update is always the first Monday of the month that is not a US holiday.
[Google Pixel 6 Pro] Lughnasadh:
Yes, I know the update is always on the first Monday of the month, except when it is a holiday. When there is a holiday the updates "usually" come out the next day, maybe the next day or two.

I have been flashing monthly updates since the Nexus 5, so around 9 years, and my experience is that most often the update will be released the day or two after the holiday. Not always, but most often.
[Google Pixel 6 Pro] DespairFactor:
that is actually wrong, I have never seen it come out the day after the holiday. I have been doing this since Nexus 4. I have owned every Google device since Nexus 4 except the Pixel 5
[Google Pixel 6 Pro] Nergal di Cuthah:
Agree to disagree and love one another :)
[Google Pixel 6 Pro] Lughnasadh:
Actually I said a day or two, usually,

Last year, 2021, the first Monday of the month in July was July 5th. July 5th was a federally recognized holiday since July 4th fell on a Sunday. Google released their update on July 7th, 2 days afterwards.

Not trying to argue, but this has been my experience. As Negal said, we can agree to disagree. Peace...

July 2021 Android security update is now rolling out to Pixel phones

Google has published the Android Security Bulletin for July 2021, and they've also started rolling out the security update to Pixel phones.

www.xda-developers.com
[Google Pixel 6 Pro] DespairFactor:
yeah we can agree to disagree, one time occurrence
[Google Pixel 6 Pro] Lughnasadh:
July images are up.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yes!!!! Yay.

For some reason, the links all give 404 error. I'll update when they start working. Links are working now!

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Pixel Update Bulletin—July 2022 | Android Open Source Project

source.android.com

Google Pixel Update - July 2022 - Google Pixel Community
[Google Pixel 6 Pro] cmh714:
Thus far, the links are 404's.....hopefully they update soon.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Whoops! You are correct. I wonder if

Official Google Android Flash Tool

at least works to get the latest update? Although I'll still wait for the zip file.
[Google Pixel 6 Pro] LLStarks:
The Pixel bulletin says this is a connectivity update as well. Should add more VoLTE for European, Asian, and Middle Eastern users.

I'll try to examine all three versions later today.

Google Pixel Update - July 2022 - Google Pixel Community

Edit: If you guys know of a better way to examine product partition files without de-sparse and ripping them open, please let me know. It takes up a lot of space just to grab a file or two.
[Google Pixel 6 Pro] Ghisy:
July links are working now!
[Google Pixel 6 Pro] LLStarks:
Whatever changed in this build, it might not have been in the modem. This is a modem from May and no difference between the July versions.

Looks like I really will have to go into those product partitions. Fun.
[Google Pixel 6 Pro] Nekromantik:
3 different versions again

Im in UK so may just try the version without country in it
[Google Pixel 6 Pro] roirraW "edor" ehT:
Technically, you're supposed to flash the EMEA one, but of course, for practical purposes, a different image might actually be better for anyone on a case-by-case basis.

https://www.google.com/search?q=EMEA/APAC&sourceid=chrome&ie=UTF-8
[Google Pixel 6 Pro] kiekan:
If it helps at all, I manually flashed the A13 Beta 3.3 radio firmware (its a far newer radio firmware) and have seen a pretty dramatic improvement in performance. Might want to give that a try yourself.

For clarification, I was using it on A12 in June and just tried flashing it with the new July (since the radio firmware with the July update was identical to the June one) update and seems to be working well.
[Google Pixel 6 Pro] biTToe:
So, Can I flash the the EMEA image on my US P6P without serious repercussions, just to give it a try? Or will it not likely work with Google Fi?
[Google Pixel 6 Pro] foobar66:
Updated and kept root/data...