yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] Lughnasadh:
No. That's is the recommended method according to Google.

"To avoid hitting this state, if you are flashing a Pixel 6, Pixel 6a, or Pixel 6 Pro device with an Android 13 build for the first time, please flash the bootloader partition to the inactive slot after successfully updating and booting into Android 13 at least once. This can be done by following these steps:

Option 1 (recommended): After a successful boot into Android 13 for the first time, sideload the full OTA image corresponding to that build and reboot the device to ensure that both slots have a bootable image."
[Google Pixel 6] kylechen:
Can we run A13 system on an A12 bootloader?

Is there any way / anyone / any research on the bootloader code to stop the "fuse" trigger?

Does it break any law in any country that software update secretly activates a hardware trigger that stops the user from using any good old systems?
[Google Pixel 6] V0latyle:
Hasn't been tested yet. If you want, you can try by using the same --force argument; just be aware that if it doesn't work, you may need to wipe data.

Don't know, doubt it.

This seems like something you could research yourself. I highly doubt it - many OEMs implement some form of anti-rollback on their devices to prevent downgrading to previous firmwares. Samsung is especially notorious for this.
[Google Pixel 6] tom1807:
No, and you shouldn't. It has a vulnerability in the Android 12 bootloader.

I see no reason to downgrade the bootloader, you still can run A12 with the newer bootloader.

Cheers
[Google Pixel 6] V0latyle:
Not as a daily driver.
[Google Pixel 6] tom1807:
Can't comment on this, no idea what would be the side effects.

My active slot is A and has Android 13, I only updated the ootloader to the latest one on slot B but there should be still A12.

Cheers

Tom
[Google Pixel 6] V0latyle:
The whole point of this thread is that if only one slot is updated and the device switches/is switched to the Android 12 slot after updating and running Android 13, it will brick.

The side effects of running 12 on the 13 bootloader have been established. See the OP. WebView and DRM Apex constantly crash.
[Google Pixel 6] Lughnasadh:
But if you flash back to A12 using the A13 bootloader you'll have a bunch of apps, webview, browers, etc. crashing.

Which actually makes me wonder about something...

@roirraW "edor" ehT When you were on A12 and flashed the A13 bootloader, did you experience apps crashing or other negative side effects? I don't remember you mentioning so which makes me curious if there is a difference in how well the OS runs when you are on A13 and flash back to A12 with the A13 bootloader vs. being on A12 and flashing the A13 bootloader???
[Google Pixel 6] roirraW "edor" ehT:
I didn't, but I didn't even both trying to launch anything, that I recall. I merely unlocked the phone - I might have swiped right to display "Google Discover" aka whatever it's called now via Nova Companion, and I might've swiped up to check out the app drawer, and swiped down to check out the notifications.

I didn't test texting, chatting, phone calls, web browsing, watching videos, harassing my fellow moderators LOL!, or anything when I had only upgraded the bootloader and still running my original, never upgraded Android 12 (first) July "global" update - 12.1.0 (SQ3A.220705.003, Jul 2022).
[Google Pixel 6] V0latyle:
Beat you to it :D bet you won't find the Easter egg
[Google Pixel 6] Lughnasadh:
Ah, ok. Makes sense now. I had thought you stayed on it for a while and used it. Thanks...
[Google Pixel 6] Nightf0x_007:
Updating via google pixel flashing website flashes both slots ? Or should i do it manually
[Google Pixel 6] Lughnasadh:
Do you mean Android Flash Tool? If so, no, it doesn't flash to both slots. However, the latest version of the Pixel Flasher does.
[Google Pixel 6] eagledipesh:
Can someone list steps to manually update Google pixel 6?

My phones bootloader is locked.

EDIT : I was just worrying, did manual update VIA sideloading OTA, worked well, now I need to figure out how to update the bootloader.
[Google Pixel 6] V0latyle:
Sideload the OTA again. It always installs to the inactive slot.
[Google Pixel 6] Sui77:
I've updated by using the factory image (batch-installation), overloaded unblocked.

Can I flash the bootloader to both slots manually again without any issues?
[Google Pixel 6] V0latyle:
Should be able to, yes.
[Google Pixel 6] sic0048:
Thanks for posting this. I manually flashed the OTA update from Google' site and there is no warning listed there (I just double checked to see if it was added since I flashed). I knew you wouldn't be able to roll back to the old bootloader, but I had no idea the recommendation was to flash both bootloaders.

EDIT - actually after looking at the warning on the factory image page (and not seeing it on the OTA image page), I have to wonder if the OTA image flashing process actually flashed both bootloaders. I would think Google would add the same warning to the OTA image site if this was a potential problem.
[Google Pixel 6] V0latyle:
No - the OTA, whether done through system or sideload, only updates one slot at a time, the "inactive" slot.

The only way to flash both bootloaders at the same time is via the factory image method.

Otherwise, after updating and while running on the updated slot, the recommendation is to simply sideload the OTA again.

To clarify this: Say you're running on Slot A. You took the automatic update to Android 13, which installs to Slot B and switches the device to that slot. Since you still have Android 12 on slot A, all you have to do is sideload the OTA, which will install to slot A because it's now the inactive slot.
[Google Pixel 6] Sui77:
worked like a charme
[Google Pixel 6] Ictcreations:
so here is where im confused... I got bored of waiting to be told android 13 was out.. so i manually downloaded and installed android 13 OTA via sideload. It flashed, no errors and works fine..

Now this may be the stupid part of my brain coming out but....

with the install going through fine without issue, and now im on A13, why would there be an issue and why would i need to flash bootloader to bother slots? one would automatically assume that everything that is needed to be done is all within the sideloaded file? I am now just waiting for the 1st over the air update for android 13 to come through.

I'm still confused where the issue is here, and why not having the bootloader on both slots matters? BTW i'm not rooted and my bootloader is locked... Again, its not something im going to change.

Thanks in advance
[Google Pixel 6] V0latyle:
This has been discussed at length, including in the OP.

The OTA update only updates one slot. So, you currently have an updated slot running Android 13, with the new bootloader, and the previous slot you were on when you installed the update, which still has Android 12.

If for whatever reason you experience a boot loop, your device might recycle back to the old slot. Due to the anti-rollback mechanism involved with the Android 13 bootloader, this could cause your phone to brick because it won't load the Android 12 bootloader.
[Google Pixel 6] Ictcreations:
Right ok... Tahnks for the clear response. If i had understood all the detail, i would not have asked what you think is a pointless question.

I'm by no means stupid, i just could not fathom why it would made a difference because i couldnt see any situations where that would arise.

You have given me an example as to when it could cause an issue so now i understand fully. There was no need to be short with the "this has been discussed at legnths" bla bla bla..

Some people just need things explaining in a different way for them to click.

Thats not wrong by any means.

Some people have difficulties and hidden disabilities that are not seen or communicated because they dont have to be. What they dont need is people getting frustrated with responses because that isnt fair or nice.

But i digress.... Thankyou for the response, it is appreciated.

If i were to leave it and take that possible risk onboard, when the next OTA is pushed to system update, will it then flash the inactive slot with the A13 bootloader so they are both updated?
[Google Pixel 6] V0latyle:
Your question was answered in the OP, in almost exactly the same way I explained it. Aside from item 1 of the Forum Rules - Search before Posting - the unwritten rule is to always read the entire OP.

That being said, I do understand that sometimes things just need to be explained a little differently. I'm by no means a quick study.

Yes...unless there's a new bootloader version too, in which case it'll flash that.

I would highly recommend updating the other slot anyway, just to be safe. Costs you exactly nothing to do it, and could prevent bricking your device. Note that in this context, "brick" means completely unusable and unrecoverable.
[Google Pixel 6] Ictcreations:
Great stuff. Thanks for that. One more question if i may please... Again, my appologies if this has been covered...

Is there an app or adb command that will tell me what version of bootloader is present on active/inactive slot?

When im advised to do something, i always want to be able to verify that what is advised has actually worked or needed if that makes sense?

Thanks in advance
[Google Pixel 6] Lughnasadh:
adb reboot bootloader

fastboot getvar current-slot

fastboot getvar version-bootloader

fastboot --set-active=(a or b, choose the slot you are not on)

fastboot getvar current-slot

fastboot getvar version-bootloader

fastboot --set-active=(a or b, choose your original slot)

fastboot reboot bootloader

Then reboot
[Google Pixel 6] dizzota:
Thanks for the heads up! I ended up sideloading the Android 13 OTA update to both slots entirely, which...I wasn't exactly successful at first because I forgot how sideloading worked.

Legitimately, I updated the same slot...twice, and when I swapped to the other slot in Fastboot and checked Recovery for the version, I shat myself when reading 12/SQ3A.220705.004.

Pay attention to what boot slot you're updating. Don't do what I did. 😐
[Google Pixel 6] V0latyle:
Nothing wakes you up quite like soiling yourself
[Google Pixel 6] dinuka_haxxor:
Hi so I updated to android 13 by using PixelFlasher. I used the factory image and flashed is as usual (new version of PixelFlasher have a option to flash to both slots now .. but I didn't had that option) so should I flash to inactive slot ?should I mist be worried?
[Google Pixel 6] dinuka_haxxor:
soo i tried google method and this happened :/

PS F:\torrentz\platform-tools_r33.0.3-windows\platform-tools> fastboot --slot=other flash bootloader D:\oriole-tp1a.220624.021-factory-4bd6cec7\oriole-tp1a.220624.021\bootloader.img

Warning: bootloader does not support slots, and slot b was requested.

Sending 'bootloader' (11554 KB) OKAY [ 0.419s]

Writing 'bootloader' FAILED (remote: 'No such file or directory')

fastboot: error: Command failed
[Google Pixel 6] V0latyle:
That's weird. Try this:

fastboot flash bootloader --slot=all <bootloader image>

That will flash them both at the same time.
[Google Pixel 6] dinuka_haxxor:
Hey before executing fastboot flash bootloader I must run adb reboot fastboot right ? Which takes me to fastbootd mode ?
[Google Pixel 6] Lughnasadh:
No, just the opposite. You should be in fastboot to flash the bootloader. You can't flash the bootloader in fastbootd and adb reboot fastboot will take you to fastbootd. So you want the command adb reboot bootloader to get into fastboot.
[Google Pixel 6] hh11bbaacchh11:
By my understanding of this post, if and when I update to A13 OTA, then I have to sideload the OTA again. If coming from A12, can I just sideload the OTA once and both slots be updated to the latest bootloader, or do I have to first update OTA then sideload the same OTA?
[Google Pixel 6] Lughnasadh:
Yes, that is one way of doing it. You will then have A13 on both slots.

Sideloading the OTA to update to A13 will only put the A13 bootloader on one slot. As you mentioned earlier, you can update via OTA and afterwards sideload the OTA to put it on the other slot as well. Or if your bootloader is unlocked you can flash the bootloader to both slots as described in the OP.
[Google Pixel 6] Frankenscript:
Question: for someone who is on A12 stock/unrooted, is there some way to block the update until I'm satisfied enough kinks are worked out. My phone is working just fine right now on A12, and while I will eventually update it to keep up with security issues, I want to put the update on hold for a while. I keep getting notifications that don't like to be turned off. I'm worried I'll accidentally tap and start the upgrade.
[Google Pixel 6] stevew84:
Sideloading the OTA right now, stuck at 2% for like 15 minutes now. Phone says Verifying Update Package...
[Google Pixel 6] roshan2989:
Hi Guys ,just receive P6 today and updated to a13..and how sideload to 2 slot?no root
[Google Pixel 6] Lughnasadh:
Android Basics: How to sideload OTA updates on your Google Pixel [Video]

We show you how to sideload OTA updates on your Google Pixel on Windows and Mac in our step-by-step Android Basics guide and tutorial.

9to5google.com
[Google Pixel 6] V0latyle:
When you sideload the OTA, it updates the "other" slot, regardless of which slot you're on. So, if you're on slot A, sideloading the OTA will update slot B, and reboot to that slot when finished. Likewise, if you're already on slot B, sideloading the OTA will update slot A. Does this make sense?

You don't have to be rooted to sideload the OTA.
[Google Pixel 6] roshan2989:
Thanks for the guide, came from Xiaomi.

one last question, currently using japan version, is there any region specific OTA image to flash or just this one site for everything (https://developers.google.com/android/ota)
[Google Pixel 6] V0latyle:
All the Pixel images are on that site (and the factory images here). Most of the time, the images are "one size fits all", appropriate for all variants. The images will be labelled appropriately if there are differences between carriers/regions:

As you can see, these are all the July 2022 update, but there are several different versions for where the device is being used. You can't really go wrong by using the vanilla "global" variant (in this case, the 220705.003 and 220705.004) but if you see your region/carrier listed, you should generally use that version because the baseband firmware is generally best suited to your circumstances.

However, for the Android 13 update, there have been no carrier specific variants:

And, the only Japan specific firmware I see for any of these phones is the 6a "bluejay":
[Google Pixel 6] roshan2989:
Thanks bro,just flash the build and booted

is there any way to check if the both slot bootloader updated?

able to check one for now

C:\ADB>fastboot getvar current-slot

current-slot: b

Finished. Total time: 0.001s

C:\ADB>fastboot getvar version-bootloader

version-bootloader: slider-1.2-8739948

Finished. Total time: 0.002s

cant check another, since its locked

C:\ADB>fastboot --set-active=a

Setting current slot to 'a' FAILED (remote: 'command (set_active:) is not allowed when locked')

fastboot: error: Command failed.
[Google Pixel 6] V0latyle:
Yeah, you can't change slots manually with a locked bootloader.

Simply sideload the OTA again, it will always flash the "other" slot.

Example: You're running on slot B, and sideload the OTA. The OTA flashes to slot A, then reboots to slot A. If you sideload the OTA again, it will now flash to slot B, then reboot to slot B.
[Google Pixel 6] happynexuss:
I had a weird upgrade path and I just want to confirm I'm safe :) I tried OTA update and that seemed to crash my phone so I had to do a factory reset. Then I sideloaded Android 13 and got root again. I'm not 100% sure if both my slots are Android 13 or not and would like some confirmation. I tried a method someone posted earlier and my results are below, can you all let me know if I'm safe?

C:\Users\xxxx\Desktop\platform-tools>fastboot getvar current-slot

current-slot: a

Finished. Total time: 0.001s

C:\Users\xxxx\Desktop\platform-tools>fastboot getvar version-bootloader

version-bootloader: slider-1.2-8739948

Finished. Total time: 0.001s

C:\Users\xxxx\Desktop\platform-tools>fastboot --set-active=b

Setting current slot to 'b' OKAY [ 0.101s]

Finished. Total time: 0.102s

C:\Users\xxxx\Desktop\platform-tools>fastboot getvar current-slot

current-slot: b

Finished. Total time: 0.002s

C:\Users\xxxx\Desktop\platform-tools>fastboot getvar version-bootloader

version-bootloader: slider-1.2-8739948

Finished. Total time: 0.001s
[Google Pixel 6] V0latyle:
If you want to make sure, simply open the factory update package and compare the bootloader version to what you posted above.
[Google Pixel 6] Lughnasadh:
Yep, you're all set. A13 bootloader on both slots 👍
[Google Pixel 6] happynexuss:
lol my dumb luck :) I was cursing at having to factory reset but that seems to have prevented something even worse from happening so I'm smiling about it now. Thank you for confirming Lughnasadh!
[Google Pixel 6] x3sed:
Hello guys ! Since there was 2 Android 13 OTA updates, do we still need to sideload please ?

The first OTA installed the Android 13 upgrade which I did and I got a message afterward to install the new Android 13 update (done too).

(I'm pretty sure it's a dumb question, sorry)
[Google Pixel 6] V0latyle:
I would still check both slots for the new bootloader to be safe, but I don't remember off the top of my head the commands to do that.
[Google Pixel 6] Lughnasadh:
adb reboot bootloader

fastboot getvar current-slot

fastboot getvar version-bootloader

fastboot --set-active=a or b (set to inactive slot)

fastboot getvar current-slot

fastboot getvar version-bootloader

fastboot --set -active=a or b (set to original slot)

fastboot getvar current-slot

fastboot reboot bootloader

fastboot reboot

(There are a couple of redundancies in there just as a failsafe)

P.S. You'll need to have an unlocked bootloader to switch/set slots.
[Google Pixel 6] mrwattz405:
Is this still a current issue? I just got my p6 from at&t and phone says in 2 days it will install automatically. I don't want my phone to be a paperweight and I don't have access to a computer and adb like I used to since the Nexus days.
[Google Pixel 6] V0latyle:
This issue is relevant to all Pixel 6 devices upgrading from Android 12 to Android 13. It's not likely that your device will brick - but in the off chance that the update fails for whatever reason, and you still have an Android 12 bootloader on one of the slots, it might.
[Google Pixel 6] kjeasan:
Hi,my pixel 6 build is TP1A.220905.004. SO do i have to sideload same TP1A.220905.004 OTA.zip build again on my device ?
[Google Pixel 6] V0latyle:
If you updated via OTA in August, then you should be fine.
[Google Pixel 6] Lughnasadh:
If that is your real IMEI number you posted, you really ought to delete that photo, for your privacy and security.
[Google Pixel 6] kjeasan:
So is my bootloader unlocking safe now?
[Google Pixel 6] thermomonkey:
Morning all. Would also like to know if I still need to do this with the latest OTA update. I keep telling my phone I don't want to upgrade but it keeps annoying me; it really wants me to upgrade to 13!
[Google Pixel 6] V0latyle:
What do you mean? Unlocking your bootloader has never been "unsafe". It will wipe data however.

If you have not yet updated to Android 13, then yes - you will need to make sure the new bootloader is on both slots.
[Google Pixel 6] kjeasan:
Soory for my bad english, What i meant to say that if there was any risk involving my device being bricked while trying to unlock my phone.since i'm not familiar with A/B boot slot system,

i have unlocking experiance with xiaomi redmi 8,so there was no A/B boot system.this is kinda new to me. my phone got 1 OTA update after updaing to android 13.

is there any way to check if bootloader is on both slots on locked bootloader .

i appologize for asking too many question. have a good day
[Google Pixel 6] V0latyle:
If you updated via OTA for both August and September you should be fine.

Just go back one page, @Lughnasadh posted it here
[Google Pixel 6] Yakov5890:
Какова вероятность того, что обновление пойдет не так?

Mod translation: What is the probability that the update will go wrong?
[Google Pixel 6] V0latyle:
Fairly low, but because Android is designed to "recycle" back to the original slot if the OTA fails, it's better to be safe than sorry.

If you updated via OTA in both August and September, you're not at risk.
[Google Pixel 6] Yakov5890:
I just bought the device yesterday. It came with Android 12 out of the box. I decided to update with fastboot.
[Google Pixel 6] roshan2989:
Hi all, currently on QPR Beta 2,i want to do a full reset and flash back QPR Beta 2

can i flash the same existing image after full reset? Saw this at QPR Google page

need to unlock bootloader to flash beta?
[Google Pixel 6] V0latyle:
Many people have been able to flash the beta without unlocking their bootloader; still, I would strongly recommend you do so, just because beta software may be unstable, and an unlocked bootloader makes it a lot easier to recover your device if something goes wrong.
[Google Pixel 6] Erecik:
So if I flashed OTA package through recovery, rebooted into system, then back into recovery and flashed OTA again, should I be good?
[Google Pixel 6] V0latyle:
Yes.
[Google Pixel 6] namitutonka:
My Pixel 6 automatically updated from Android 12 to Android 13. With the last recent OTA update, I noticed this thread. I downloaded the identical OTA (oriole-ota-tp1a.221105.002-e727d382.zip) from Developers.Google..... I'm writing this as my Pixel screen (following the OP instructions) has been reading: "Verifying update package", while my (fast) Windows 11 machine reads: "serving: "ota.zip" (~10%). It's been this way for a solid hour. Is this normal?

It makes me wonder if either the phone or the USB is bad., I'm wondering if it should take this long, but don't want to unplug it. The SHA for the file checked out.
[Google Pixel 6] namitutonka:
Second try also resulted in failed/aborted sideload operation. Guess I'll continue without slot B.
[Google Pixel 6] Lughnasadh:
Make sure your Platform Tools are up to date. Try using an A to C cable using USB 2.0 port.
[Google Pixel 6] namitutonka:
Good advise Lughnasadh. My platform tools are definitely older. I'll wait to post next attempt until I get that cable. I did switch a different C to C cable while changing from the front to back panel.
[Google Pixel 6] namitutonka:
I updated my platform tools. Used a USB A to C cable from my PC's USB 2.0 backpanel port.

The "Update package verification" took 4567.4 seconds = 1hour 16minutes. A boolean zero means false while a number one means true. No errors were reported, but the final message on the phone was: "Install from ADB completed with status 0." Am I correct in guessing that 'status 0' means that the ADB sideload install was successful?
[Google Pixel 6] Lughnasadh:
You should be good.
[Google Pixel 6] V0latyle:
OTA sideload should only take 5 min or so. Sounds like a bad cable to me although there's the possibility of a dirty USB connector on your phone...