yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] sean222:
Correct. I didn't do the Day 1 update. You need the boot.img from that update to patch it with Magisk.

You can probably google ways to extract the boot.img from an OTA, but it's probably not worth the time and effort.
[Google Pixel 6 Pro] HereticBG:
What's your build number? Mine just took OTA and it's on the "SD1A.210817.019.C2" build which has the factory image on their website.

Edit: I see now people talking about a .036 which isn't on the factory images site. Nevermind
[Google Pixel 6 Pro] Nekromantik:
you can still flash patched boot from older firmware if you taken the OTA
[Google Pixel 6 Pro] Zilla0617:
So let me understand, I can flash the old firmware's boot image, reboot into fastboot and flash the magisk-patched image. Will I lose data or encounter a bootloop?
[Google Pixel 6 Pro] hrdc69:
Does anyone know if you get the Pixel 6 Pro directly from T-Mobile does is come with the ability to unlock the bootloader like if you buy directly from the Google store?
[Google Pixel 6 Pro] Zilla0617:
Their unlock policy includes paying off the device and having the device on their network for 40 days. At that time, they will sim unlock your phone enabling you to unlock the bootloader. I've heard people reaching out to customer service to bypass the 40 day rule.

I have TMobile as well and decided to go thru the Google store to avoid the situation.
[Google Pixel 6 Pro] plasticarmyman:
You can always tell them you're travelling internationally and will be needing to use another SIM for service on the phone, they will usually SIM unlock at least temporarily so you can do so.
[Google Pixel 6 Pro] allenjthomsen:
Can you tell me if this command works

adb shell

then type or copy this line below

pm uninstall --user 0 com.qualcomm.qti.uim

then go into developer options and oem unlocking should be togglable

If it doesnt let me know
[Google Pixel 6 Pro] allenjthomsen:
if you have the device that is

im curious if it will work like on other tmobile devices @Zilla0617
[Google Pixel 6 Pro] Zilla0617:
I have TMobile as a carrier but purchased my P6P from Google
[Google Pixel 6 Pro] Ghisy:
If you used the factory image, it's really odd. Guess your Pixel 6 is temperamental...
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'm guessing that most or all of our P6Ps are temperamental, but that some (many?) of us have been luckier than others. I forget when exactly - December? February? - I had the corruption problem after using the full factory image. I had done nothing unusual although at the time, it could've been related to flashing the custom kernel I used. In my case, the corruption was merely an inconvenient message and didn't keep me from using my phone normally - just that I got the additional corruption prompt when I rebooted, and had to manually press the power button again to continue booting.

Other people that month had no issues at all using the same factory image and same custom kernel. My problem was solved after the next full factory image came out - flashing it (and the new monthly custom kernel) solved everything.

But I was still lucky, since I didn't get the corruption issue that actually prevents even using the phone at all until it's fixed.

Technology. There are so many variables, no one including the manufacturer can keep track of them all.
[Google Pixel 6 Pro] Megakuma:
Can I still unlock the bootloader if oem unlock is greyed out?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Android 13 looks to be OUT!

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

developers.google.com
[Google Pixel 6 Pro] V0latyle:
I don't know if this applies with a locked bootloader, but...

View attachment 5686519
[Google Pixel 6 Pro] Lughnasadh:
Weird it has a June 24 date with an August security patch when we thought it would have a September date. That was the same date as the last beta. Looks like the A13 betas have also been taken down.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Wow! Has this occurred on any previous Pixel that anyone knows? Of course, I never, ever downgraded my Pixel 1 that I recall.

Thanks for the warning!

Indeed. I'm not a betting person because I can never tell what Google will do, but nothing would surprise me, like if they pull the factory image. :D
[Google Pixel 6 Pro] V0latyle:
I think this just means you won't be able to downgrade the bootloader itself. Don't take my word for it but I suspect that one could still run older versions on the new bootloader.

To test this, just download the factory zip and update the bootloader only.
[Google Pixel 6 Pro] LLStarks:
That's a new one. Never expected Pixels to go down that path. But at least we'll avoid people trying to downgrade.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thanks! I'll consider testing that theory if no one else does first, when I have some more tech time to kill.
[Google Pixel 6 Pro] LLStarks:
If Android is supposed to be rolling release, are we going to see QPR1 Beta 1 on Wednesday?
[Google Pixel 6 Pro] Namelesswonder:
Yes I believe this is a first. I thought they would've done something like this previously with exploits like dePixel8 but they never did.

I can only assume they are doing this given the Black Hat talks that were given recently about compromising the Titan M2. I'm guessing walling off earlier firmwares due to another compromise found.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Just guessing that QPR1 Beta 1 won't come out until next month, at the earliest. They'll probably have their hands full of bug reports from Stable 13. :D
[Google Pixel 6 Pro] LLStarks:
It'll be interesting to see how it goes, considering that Android 12 QPR1 was essentially lost in all the initial bugs and prep for 12L/QPR2.

Whatever Google wants to release in September, they might need to retarget it based on critical bugs that are found today.
[Google Pixel 6 Pro] Ghisy:
It's cray!! I wasn't expecting Google to release Android 13 randomly in the middle of August!

Maybe it's time to make a new thread with mod compatibilities (Magisk modules and such) maybe?
[Google Pixel 6 Pro] LLStarks:
Pixel 7 on 9/9 doesn't seem that crazy now.
[Google Pixel 6 Pro] Lughnasadh:
I can't imagine a whole lot has changed since the last beta and today's stable. They both have the same date, just today's has the August patch instead of the July. The last beta has been super stable for me so hopefully there won't be too many bugs. Famous last words... 🙃
[Google Pixel 6 Pro] phillymade:
So I can install this stable and then opt out of the Beta, is this correct
[Google Pixel 6 Pro] Nergal di Cuthah:
Ok, i know it is advised to do a fresh wipe for android version updates but is it absolutely necessary?
[Google Pixel 6 Pro] Lughnasadh:
PSA:

"Android 13 is rolling out to Pixel devices starting today.

If you’re currently enrolled in the Android Beta program, you’ll get the Android 13 final release and remain enrolled to receive ongoing Beta updates for Android 13 feature drops, starting later this year. If you’d like to opt out of ongoing Beta updates without needing to wipe your device, just visit the Android Beta site and opt out after you get the Android 13 final release and before taking the first beta for Android 13 feature drops."

In other words, you won't be unenrolled automatically.

ADDENDUM: A13 QPR1 Beta due out in September.

Android 13 is in AOSP!

News and insights on the Android platform, developer tools, and events.

android-developers.googleblog.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
Android 13 Security Release Notes | Android Open Source Project

source.android.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
I rarely wipe my phone for any update at all. OTAs don't wipe the phone. Sure, it's possible that it'll run better if you wipe your phone, but not necessarily, and you can always wipe later if you must.
[Google Pixel 6 Pro] Lughnasadh:
FYI:

Android 13 QPR1 Beta in September

You can unenroll from Android 13 Beta without wiping after stable update, QPR1 preview in Sept.

The stable version of Android 13 is rolling out to Pixel today, and those on the Android Beta Program can unenroll their phones after...

9to5google.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
You are correct.

I did:

adb reboot bootloader
fastboot flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot reboot

And I'm booted into Android 12 still just fine. Below is the command prompt output:

Note to anyone, if after upgrading to 13 you want to downgrade to 12 using a full factory image's flash-all.bat, you'll at minimum have to either remove Android 12's bootloader flash line from the file, or replace it with fastboot flash bootloader bootloader-raven-slider-1.2-8739948.img (and have the right bootloader file in the same folder). Either should work fine.
[Google Pixel 6 Pro] p51d007:
I've NEVER done a wipe, for an update from one version to the other. I guess it's "better", but I don't want to spend the time setting it all back up again.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Update 2: Different USB cable and port worked 100%

Spoiler content hidden.
[Google Pixel 6 Pro] elknetld2kil:
Noob question: If I upgrade from 12 to 13, do I need to re-root it?
[Google Pixel 6 Pro] Lughnasadh:
Depends on how you update it, but for the more conventional update methods, yes, you'll have to re-root.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Just as @Lughnasadh said, and to add: only just as much as you have to re-root every month's update when you flash it, depending on your method.

^
[Google Pixel 6 Pro] V0latyle:
The real trick will be if you can still flash the old factory image. Try to re-flash the July image (just the system image) and see if the bootloader rejects it.
[Google Pixel 6 Pro] jcp2:
For those of you that updated to A13 - Has Google removed the ability in A13 to sideload non GP apps?
[Google Pixel 6 Pro] Lughnasadh:
No, but they've restricted a few permissions for sideloaded apps (e.g. Notification Listener and Accessibility permissions). But those restrictions can be disabled by going to the app info page and clicking on the 3 dot menu on top right.
[Google Pixel 6 Pro] jcp2:
Thank You for the quick reply :)
[Google Pixel 6 Pro] roirraW "edor" ehT:
There's no way I'll test that. Downgrading without wiping (because of updated app data, especially for system apps) is too much risk for me. I don't have the time to recover from. 😁

Anyone else?
[Google Pixel 6 Pro] Lughnasadh:
Leaving the past in the rear view mirror, sir... 😜
[Google Pixel 6 Pro] vibrantliker:
Anyone have Viper working on A13?
[Google Pixel 6 Pro] Lughnasadh:
Haven't seen anyone get V4A working on A13 on the Pixel 6 series. JamesDSP, however, does work.
[Google Pixel 6 Pro] MicroMod777:
Anybody get the auto 13 OTA update?
[Google Pixel 6 Pro] ttle54:
I flashed the Android 13 Factory Image on my Pixel 6 Pro. Everything is great so far aside from I can't roll back to Android 12. It's fine, no need to go back
[Google Pixel 6 Pro] LLStarks:
T-Mobile carrier config is now at 7/20.
[Google Pixel 6 Pro] LLStarks:
You have got to be kidding me...

T-Mobile config regressed!

<boolean name="vonr_enabled_bool" value="false" />

NSA and fallback to LTE isn't working. Wtf.
[Google Pixel 6 Pro] General_Mayhem:
Noice.

Quick dumb question: Is upgrading from 12 to 13 the same OTA flash method as the monthlies? I assume it is but..
[Google Pixel 6 Pro] V0latyle:
Yes. However I wasn't able to update via automatic OTA on my Pixel 5.
[Google Pixel 6 Pro] General_Mayhem:
Yeah I updated to the last 12 build and then tried seeing if it would OTA to 13 but wouldn't so I just re-rooted. I already pulled the 13 zips but wanted a definitive answer before I tried that. Will likely do it sometime tomorrow.
[Google Pixel 6 Pro] ttle54:
Yes it is the same way, just pick the Android 13 image for your Pixel 6 model. Then click flash and follow the instructions
[Google Pixel 6 Pro] NippleSauce:
Is this config stored within the radio image?
[Google Pixel 6 Pro] LLStarks:
No, in the product or data partition, I think.

I had to wipe my phone and follow my own VoNR guide to get a functioning connectivity again.

At least I always do a backup right before so it's no sweat.
[Google Pixel 6 Pro] Lughnasadh:
Uh oh...

https://twitter.com/i/web/status/1559398190574714881
[Google Pixel 6 Pro] Lughnasadh:
More info...

https://twitter.com/i/web/status/1559410066993938432
[Google Pixel 6 Pro] Lughnasadh:
Let's just hope that ARB is only tied to downgrading to the A12 bootloader and not other parts of the OS as well.

Google's statement wasn't exactly clearcut in my mind. I think a bad result could potentially lead to a more than undesirable outcome, if you know what I mean. Of course, I could just be overly paranoid 🙃
[Google Pixel 6 Pro] rester555:
So when factory installing through flash-all, the default installation of A13 is to one slot and not both?
[Google Pixel 6 Pro] Lughnasadh:
Correct, according to this Dev...

https://twitter.com/i/web/status/1559410066993938432
[Google Pixel 6 Pro] KHANrad_SIN:
Quick question, do you know if JamesDSP automatically switches audio profiles when you connect to different audio devices like V4a does? Currently using V4A and contemplating trying out JamesDSP just so I can update to Android 13 lol
[Google Pixel 6 Pro] CRXed:
So what is the correct way to install it to BOTH slots, before booting into the system?
[Google Pixel 6 Pro] roirraW "edor" ehT:
After flashing to your active slot, just change slots and flash again.

Unrelated device, but with A/B slots:

You can see which slot you were already active on after adb reboot bootloader (on the Fastboot screen) three items from the very bottom it will say:

or

The change slot command reflects immediately on that screen.

I just did all this.
[Google Pixel 6 Pro] Lughnasadh:
This is correct. I actually did this when updating to A13 stable so I would have A13 on both slots in case things got funky. Confirmed 👍
[Google Pixel 6 Pro] roirraW "edor" ehT:
Cool. I might try to remember to do this for every update from now on, just 'cause.
[Google Pixel 6 Pro] radekmazur:
I'm sorry. I don't want to screw it up.

Do I use the official android flash tool? Is there an option there to reboot into inactive slot or do I need to use fastboot/adb to update to A13.

I only used adb to update monthly. Thanks.
[Google Pixel 6 Pro] Lughnasadh:
I actually can't say for sure since I really don't use any profiles, but I think it does.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I use the full Pixel 6 Pro Factory Image to update each month. Use the same official latest ADB/Fastboot (SDK Platform Tools) you normally use. Edit the flash-all.bat (if on Windows - if on something else, edit the appropriate flash-all script file) and remove the "-w" and re-save it. If you want to keep the flash-all.bat from rebooting automatically after the update so that you can change slots and flash again, add fastboot --skip-reboot in the flash-all.bat after the fastboot update image-raven-xyNz.YYMMDD.BBB.zip line. Thanks, @Homeboy76 and @Lughnasadh!

Re-open the script file and confirm that you saved it with the "-w" removed, so it doesn't wipe your device.

From running Android:

adb reboot bootloader
(Let it reboot into Fastboot mode. Make note of which active slot is listed on the Fastboot screen, third item from the bottom.)

flash-all.bat
(WITH "-w" removed. Let it flash everything, will take several minutes.)

Let it boot up (and check the notifications for the update process to finish while Android is running)

adb reboot bootloader

On the Fastboot screen, change to the opposite slot with either:

fastboot --set-active=a
(If you're on slot b)

OR

fastboot --set-active=b
(If you're on slot a)

OR

[QUOTE="Homeboy76, post: 87298957, member: 4810220"]
I think you may want to use
[ICODE] fastboot --set-active=other[/ICODE]
it lowers the mistake threshold.
[/QUOTE]

flash-all.bat
(again)
[Google Pixel 6 Pro] Lughnasadh:
I used the flash-all method. I was on slot b so I flashed A13 on it and let it boot up (I removed the -w from the flash-all.bat script beforehand to preserve data) Then went into fastboot and switched slots and flashed the factory image again and booted. Now booted on slot a with both slots having A13 on them. That's it.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Oh okay, thanks. I assumed you went straight from flashing the one slot to flashing the other slot. :)
[Google Pixel 6 Pro] Lughnasadh:
I let it boot after the first flash-all. See post above.
[Google Pixel 6 Pro] Homeboy76:
fastboot --skip-reboot
[Google Pixel 6 Pro] swieder711:
What is the fastboot command to switch slots?

I thought when upgrading to a major release like 12.1 to 13 that is it was recommended to do a full wipe/fresh install.
[Google Pixel 6 Pro] Lughnasadh:
No problem. Wanted to ensure everything booted up fine on one slot before doing the other just as a precaution.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thanks! When in the process do you do that? Before running the flash-all.bat? Cheers.

https://xdaforums.com/t/android-13-...itory-of-relevant-links.4352027/post-87291469

Recommended by who? I would only do that if you have problems doing the normal way, without a wipe. I haven't (purposefully) wiped a running and rooted device in 4-5 years.
[Google Pixel 6 Pro] Lughnasadh:
fastboot --set-active=a (or b)

Yes, it is wise to do a full wipe when upgrading OS versions, imo. I had cleaned flashed the latest A13 Beta so that is why I didn't clean flash to A13 stable since there was not much change between the two.
[Google Pixel 6 Pro] LLStarks:
Need a sticky telling people not to touch their phone for manual updates unless they've unlocked their bootloader (or at least set the toggle) and are comfortable working with fastboot for hours at a time before they even begin to think about restoring their Google backups.
[Google Pixel 6 Pro] Lughnasadh:
Add it to the flash-all.bat script (after the update line)
[Google Pixel 6 Pro] roirraW "edor" ehT:
Ah, interesting. Thanks!
[Google Pixel 6 Pro] Homeboy76:
It was me that recommended (in my threads) wiping your phone before doing an Android upgrade.

Why?

Something went, horribly, wrong during one of my upgrade to a new Android version. I don't remember which Android version it was. I just remember "recommending" members wipe before upgrading an Android version.

After, reading your post, I will be editing my threads. :)
[Google Pixel 6 Pro] roirraW "edor" ehT:
Ah, I see. Years ago, I used to wipe before every single update, but that was on other OEM's devices, so didn't happen every month. I was often using someone's modified stock ROM, but not long after I started using the Pixel and stopped experimenting with ROMs, I no longer would wipe at all unless something catastrophic happened, or I goofed up the process.

I think the last time I purposefully wiped (not counting bootloader unlocks or disabling Verity/Verification) was on Android 8.0. That would've been back when I was still experimenting with ROMs - or trying to troubleshoot a weird problem I used to have that ended up being my own fault.
[Google Pixel 6 Pro] Homeboy76:
Now, you have officially earned the dual title Fast Fingers/Keyboard Operator :)
[Google Pixel 6 Pro] radekmazur:
I updated the flash-all.bat to reflect the changes mentioned above but have this error:

error: failed to load image-bluejay.....zip

What is that?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Do you have a Pixel 6A? That's what "bluejay" is. If you have a Pixel 6 Pro, then you downloaded the wrong factory image. Correct one for the Pixel 6 Pro.

Do you have all the necessary files extracted into the same folder with the latest SDK Platform Tools (ADB/Fastboot)?
[Google Pixel 6 Pro] radekmazur:
I'm first updating my 6a. I'm using the correct image. But can't figure out what that error is.
[Google Pixel 6 Pro] Sneakyghost:
Just FYI , those who haven't come across this issue: I was updating to 13 by means of adb sideload because google decided to push Android 12 again (Germany/EU), mistake on their end. Sideload failed at "verify update package", just sat there doing nothing for an hour before i killed it. I found this neat info on this thread that was a straight forward fix. using the only USB 2.0 port on my machine it worked right away. Not even 5 minutes. Thread author might point this out at the start of the thread? pretty general info though. Fastboot and ADB both appear to be working on USB-C to C, just not sideload. Dunno were this info could be posted best to save people hours of searching.
[Google Pixel 6 Pro] radekmazur:
Ok, I fixed it.
[Google Pixel 6 Pro] roirraW "edor" ehT:
That's good information to share, and I've seen others share that same information independently, but just FYI everyone, that information definitely isn't true for everyone.

I use the USB-C (3.2 Gen 1 and Gen 2) ports on my desktop computer to flash my Pixel 6 Pro and my Samsung Galaxy Tab S8 Ultra 100% fine.

I have even done it through a USB-C port on the desktop, with a long cable going to a USB hub, where I then use a USB-A cable. I have done it all those ways without issue. I did have to change USB-C cables yesterday, but still used a USB-C port.
[Google Pixel 6 Pro] roirraW "edor" ehT:
What fixed it? Different USB cable or port?
[Google Pixel 6 Pro] Sneakyghost:
There is a high probability it is not actually USB-C to C. It might be the active cables many use now (those with integrated chip), it might be the platform, and lastly, you also said "flash" but did you mean sideload or fastboot? Because i verified both ADB and Fastboot on that connection first and most functions returned no errors. Only when i went into recovery and there into sideload mode, that connection was bad.

I could do some more digging like I used to back in my HTC days, grab my top tier notebook and run the sideloading again there to see if it still applies, swap cables from active to passive, etc, but on the one hand i really dont have the nerves for that anymore and on the other hand it should suffice for readers to know they should consider the connection when things fail.
[Google Pixel 6 Pro] radekmazur:
I forgot to extract the contents of image file (.zip) into the ADB folder, so ADB had trouble locating the needed files. Once I extracted the files into the ADB folder, it all started working.
[Google Pixel 6 Pro] Lughnasadh:
Eh, the more I read about it the more I think it is just bootloader version related :)

Btw...

https://twitter.com/i/web/status/1559537708959154177
[Google Pixel 6 Pro] roirraW "edor" ehT:
None of my USB-C (or USB-A -> USB-C) cables are active cables. They're just normal, inexpensive but quality basic cables. Or do you mean yours?

I never sideload, but that would indeed be strange if actually flashing a full factory image would work 100% but sideloading wouldn't. I wouldn't accept basic ADB and Fastboot commands as being enough indication that the connection definitely works for flashing a full factory image, either.

That's okay. I accept that the same solution isn't necessary for everyone, I just wanted to put it out there that what caused the issue for you and for some people might not necessarily be a problem for others. And absolutely, the particular hardware involved can be the issue. A long time ago, I used to run into more finicky flashing issues where using particular ports mattered. My latest self-built desktop from a year and three-quarters ago has had much better luck flashing no matter what USB port I use.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Awesome! Glad it was something simple. Happens to all of us from time to time. :)
[Google Pixel 6 Pro] Homeboy76:
@Lughnasadh @roirraW "edor" ehT

:unsure: What if you edited the flash-all.bat file this way (see bold information below). Would it flash the new factory image to boot slots?

If yes, that would eliminate the need to add

--skip-reboot

or the need to

switch slots

.

...PATH=%PATH%;"%SYSTEMROOT%\System32"

fastboot flash bootloader bootloader-bramble-b5-0.5-8633619.img --slot-all

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot flash radio radio-bramble-g7250-00208-220623-b-8759277.img --slot-all

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot update image-bramble-tp1a.220624.014.zip... --slot-all