General 🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑

[V0latyle]

I've read all the posts and watched some youtube videos and hope I have the procedure right, this time, Could someone please confirm the following is correct?

-Extract the contents of the factory ROM .zip file for the Android 13 build in the current slot
-Copy the bootloader image in the extracted file to Platform-Tools

Don't really have to copy anything, you can drag and drop the file into your command window. Useful for keeping files segregated to keep your platform tools folder clean.

(This would be the img file 'bootloader-oriole-slider-1.2-8895132.img', not 'boot.img' in image-oriole- tp1a.221005.002.zip, correct?)

Correct. The boot image contains the recovery and system kernel. The bootloader image is completely separate and is in the root folder.

-With USB debugging on connect phone to PC
-Initiate CMD prompt in Platform-Tools folder
Execute the following commands:

adb reboot bootloader(enter)
fastboot --slot=other flash bootloader bootloader-oriole-slider-1.2-8895132.img(enter)

Yep, or type fastboot flash bootloader --slot=other <leave a space, then drag and drop the bootloader image into the command window>

fastboot set_active other(enter)
fastboot reboot bootloader(enter)
fastboot set_active other(enter)
fastboot reboot bootloader(enter)

I'm not sure what you're trying to do here. All you should need is
fastboot flash bootloader <bootloader image> #Flashes current bootloader slot fastboot flash bootloader --slot=other <bootloader image> #Flashes inactive slot fastboot reboot bootloader #Reboot to ensure the version shown on the screen is updated

fastboot reboot(enter)

You can also use fastboot continue which instructs the bootloader to continue normal boot.

 

[Lughnasadh]

Can someone try this and see if it works to check the bootloader version on the alternate slot without having to change slots?

fastboot getvar version bootloader_a fastboot getvar version bootloader_b

🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑

***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...

forum.xda-developers.com

 

[in_dmand]

Quick question... So if I want to update to android 13 couldn't I just Uninstall magisk and reboot (to basically make it factory android 12 again without root) then I could go through the official update that is default on my phone. After that I could simply root android 13 correct? I would have an unlocked bootloader the whole time

 

[V0latyle]

Quick question... So if I want to update to android 13 couldn't I just Uninstall magisk and reboot (to basically make it factory android 12 again without root) then I could go through the official update that is default on my phone. After that I could simply root android 13 correct? I would have an unlocked bootloader the whole time

If you're asking about updating and re-rooting, please ask this question in the guide I linked at the top of the OP.

This thread specifically concerns the anti rollback. If you are updating to Android 13 for the first time, you want to ensure you flash the new bootloader to both slots.

 

[in_dmand]

If you're asking about updating and re-rooting, please ask this question in the guide I linked at the top of the OP.

This thread specifically concerns the anti rollback. If you are updating to Android 13 for the first time, you want to ensure you flash the new bootloader to both slots.

Thanks, I guess that's my question... Why would I need to flash the new bootloader to both spots, shouldn't that happen naturally when doing the native Android 13 update?

 

[V0latyle]

Thanks, I guess that's my question... Why would I need to flash the new bootloader to both spots, shouldn't that happen naturally when doing the native Android 13 update?

No. Please read the OP again. This has been explained ad nauseam.

 

[in_dmand]

No. Please read the OP again. This has been explained ad nauseam.

Thanks, ok I did and followed the instructions. Now I'm basically just trying to follow instructions you posted on verifying that it's been updated on both slots, but when I use ADB to reboot the bootloader into fastboot mode and get to the correct fastboot screen (red triangle w/ an exclamation point in the middle and says 'Fastboot Mode' w/ info underneath) the fastboot commands don't work. such as when I enter 'fastboot getvar current-slot', it just keeps saying 'waiting for any device'.

Any ideas? maybe I need to update my platform tools or something.

*Edit* nvm I'm good I just updated my USB drivers for the Pixel 6 and it's working now so I'm all set

 

[2Wires]

I was on 0905 and wanted to update to 1205 with the Pixel Flasher. I patched the boot.img and let it do its magic.
After the update my P6 was boot looping. Since that happened before with the Pixel Flasher, I decided to manually flash 1205 again. I think it got interrupted at some point and couldn't finish. I tried flashing 0905 again but no luck. I got some corrupted data errors and after a while the phone didn't boot anymore.
It's a brick now. I've tried all kinds of button combinations for different amounts of time, up to hours. With USB, without USB, no change. No sign of life.
Could that have happened because slot A and B may have different bootloaders?
I assume the device can't be recovered? I don't live for from Google, maybe I should visit them

 

[V0latyle]

I was on 0905 and wanted to update to 1205 with the Pixel Flasher. I patched the boot.img and let it do its magic.
After the update my P6 was boot looping. Since that happened before with the Pixel Flasher, I decided to manually flash 1205 again. I think it got interrupted at some point and couldn't finish. I tried flashing 0905 again but no luck. I got some corrupted data errors and after a while the phone didn't boot anymore.
It's a brick now. I've tried all kinds of button combinations for different amounts of time, up to hours. With USB, without USB, no change. No sign of life.
Could that have happened because slot A and B may have different bootloaders?
I assume the device can't be recovered? I don't live for from Google, maybe I should visit them

If both bootloaders are Android 13, it shouldn't matter. But yes, if the bootloader screen doesn't even come up, you're going to have to have it repaired.

 

[kiwigi]

***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.***

From the Pixel Images page:
View attachment 5763217
How do I check my current bootloader version?

I had an error when I wanted to change slot; "Setting current slot to 'b' FAILED (remote: 'command (set_active is not allowed when locked')"
Does it mean that I would have to unlock before checking the bootloader version?

 

[V0latyle]

I had an error when I wanted to change slot; "Setting current slot to 'b' FAILED (remote: 'command (set_active is not allowed when locked')"
Does it mean that I would have to unlock before checking the bootloader version?

Bootloader version is displayed on the bootloader screen. Since you are locked, the only way to update is via OTA, so if you have updated at least once since the August update, both slots should be OK.

 

[kiwigi]

Bootloader version is displayed on the bootloader screen. Since you are locked, the only way to update is via OTA, so if you have updated at least once since the August update, both slots should be OK.

Thanks @V0latyle
The P6 updated itself last week during a try of GrapeneOS. I only own this phone for approx 3 weeks.
Its on TQ1A.221205.011
Eventually I like to root and stay with stock. Just have to get knowledgeable around the 2 slots and if and what image needs to be flashed to the non active one.

 

[V0latyle]

Thanks @V0latyle
The P6 updated itself last week during a try of GrapeneOS. I only own this phone for approx 3 weeks.
Its on TQ1A.221205.011
Eventually I like to root and stay with stock. Just have to get knowledgeable around the 2 slots and if and what image needs to be flashed to the non active one.

You don't have to have anything in particular flashed to the inactive slot; just make sure the inactive bootloader slot is Android 13.

If you go back to a stock ROM from a custom ROM it would be wise to flash both slots simply to avoid any weirdness should a boot failure occur and the device tries to reboot to custom software

 

[anawilliam850]

Thanks for the recommendation and warning.

 

[V0latyle]

If you're asking about updating and re-rooting, please ask this question in the guide I linked at the top of the OP.

Did you mean to quote my post and ask a question?

 

[xabier-bo]

Hi @V0latyle

What would be the best way to proceed in this situation...?

- Rooted Xiaomi Mi 11 5G NE (A/B)
- I've accepted upgrade to Android 13, thinking I was only downloading OTA, that is, expecting a confirmation before the 2 phases. But it has started automatically to install it...
- So I've decided the best I could do was to follow the standard procedure about Magisk & OTA (uninstall Magisk-restore stock images / wait until installation finishes / install Magisk inactive slot)
- And I've stopped here...

Is there anything that can be done before restarting?
I mean how could I flash A13 bootloader in both slots, before upgrading?

 

[V0latyle]

- Rooted Xiaomi Mi A2 Lite (A/B)

Your device is not a Pixel 6, your question does not belong here. You've been a member of XDA long enough to know better, my friend.

The anti-rollback discussed in this thread applies ONLY to the Google Pixel 6, 6 Pro, and 6a.

 

[xabier-bo]

Your device is not a Pixel 6, your question does not belong here. You've been a member of XDA long enough to know better, my friend.

The anti-rollback discussed in this thread applies ONLY to the Google Pixel 6, 6 Pro, and 6a.

I missed at some point the ONLY clause
Said that, thanks for your answer, I was on the move, I broke out in a sweat , and I didn't check anymore.

 

[alexdownar]

Pixel 6. Help me figure out how to solve the problem. I installed the latest February version of your firmware to the January official one. All the works, but there is no menu for turning on Volte and Vowifi, and there is also no call recording option.

 

[V0latyle]

Pixel 6. Help me figure out how to solve the problem. I installed the latest February version of your firmware to the January official one. All the works, but there is no menu for turning on Volte and Vowifi, and there is also no call recording option.

It's stock Google firmware, if you don't see those options they probably aren't available in your region