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

Search This thread

Hand76

Senior Member
Jul 1, 2010
929
168
Long Island N.Y.
Just got my new Pixel 6 Pro off swappa. On Android 13 October build.

Both slots (A&B) show the same: slider-1.2-8895132

So Im good to go? I can go ahead and root now?
 

Juuuuune

Member
May 23, 2021
33
6
Google Pixel 3
Google Pixel 4
This is not a root guide. The link for the guide is at the top of the OP.
Sorry, I replied to the wrong post, actually I want to ask: currently my pixel6Pro works in slot A is android 13, I don't know if slot B is android 12 (older bootloader version?), can I Prevent the pixel6Pro from dying by doing a full ota update on the 13 system to cover slot B?(translate form Google) appreciate!
 

V0latyle

Forum Moderator
Staff member
Sorry, I replied to the wrong post, actually I want to ask: currently my pixel6Pro works in slot A is android 13, I don't know if slot B is android 12 (older bootloader version?), can I Prevent the pixel6Pro from dying by doing a full ota update on the 13 system to cover slot B?(translate form Google) appreciate!
The instructions to check the other slot are in the OP as well.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Very informative, thank you!
    1
    Updated from A12 to A13 with PixelFlasher with "Flash both slots" option.

    Worked like a charm (y)
  • 24
    ***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.***

    From the Pixel Images page:
    1668631218213.png


    This applies to ALL Tensor devices, regardless of whether or not you're rooted!

    What this means:
    Once Android 13 Stable boots, it updates an anti-rollback counter in the device hardware to prevent rolling back the bootloader. This will prevent previous versions of the bootloader from starting.

    Why this is a problem: The OTA only updates one slot, then reboots into that slot. It does not update both slots at once. If there is a boot failure after updating to Android 13, the device may attempt to "recycle" back to the old slot. If this other slot has a previous version of the bootloader, the bootloader will not start, rendering the device a brick.

    How do I make sure this doesn't happen to me?
    If you updated via OTA, simply sideload the OTA again. Since you are currently on the Android 13 slot, this will overwrite your old Android 12 slot with the new bootloader.
    If you have an unlocked bootloader and prefer to update using the factory image, you can flash the bootloader to both slots:
    fastboot flash bootloader --slot=all <bootloader image> It's highly recommended you do this BEFORE updating, but if you didn't, do it as soon as possible.

    I've updated several times since the August 2022 update, am I still at risk?
    If you've updated via OTA at least once since August, you should be fine. Instructions to check bootloader versions are further down this post.

    What if I was on the Android 13 Beta? Same as above - the beta did not incorporate the anti-rollback, and the beta bootloaders are still considered "old".

    Will the new bootloader prevent me from flashing and running Android 12? The short answer is YES, for now. Contrary to what the warning above says, you CAN flash Android 12 on the Android 13 bootloader, and though it will boot, it will not run properly. See this post.

    How do I check my current bootloader version?
    Code:
    adb reboot bootloader #Reboots device to bootloader.
    
    fastboot getvar current-slot #Outputs current slot, should also be visible on the device screen: "Boot slot"
    
    fastboot getvar version-bootloader #Outputs current slot's bootloader version, should also be visible on device screen "Bootloader version"
    
    fastboot --set-active=a or b #Use this to switch to the inactive slot - if current slot is A, set to B or vice versa.
    
    fastboot getvar current-slot
    
    fastboot getvar version-bootloader
    
    fastboot --set-active=b or a (set to original slot) #Set active slot back to what it was before.  If you started on slot A, make sure you switch back to slot A.
    
    fastboot getvar current-slot
    
    fastboot continue #Commands device to resume boot, same function as selecting "Start" in the bootloader menu.
    
    #So as an example:
    fastboot getvar current-sot
    >current-slot: a
    
    fastboot getvar version-bootloader
    >version:1.3
    
    fastboot --set-active=b
    >Setting current slot to 'b'
    
    fastboot getvar version-bootloader
    >version: 1.3
    
    fastboot --set-active=a
    >Setting current slot to 'a'
    
    fastboot continue
    7
    Android 12 party is over, DRM APEX isn't functional when the Android 13 bootloader is installed.

    You won't be able to use WebView or browsers, and anything that wants to check DRM like streaming applications are going to crash.

    Maybe at some point a developer can look into cooking up a custom Android 12 ROM with Android 13 APEXs or patched ones.
    6
    Source? This would be nice. I still think Pixel Flasher is superior in most ways


    Screenshot_20220821-005234.png
    5
    FYI: Even though Android Flash Tool does not flash the whole image to both slots, they have added an option to flash the A13 bootloader to the inactive slot. This may be the easiest option when updating to A13 from A12.

    Just to be clear, when updating to A13 from A12 a prompt will show up asking whether you want to also flash the bootloader to the inactive slot as well. It doesn't show up in the regular tick boxes.


    Screenshot from 2022-08-24 14-39-11.png
    3
    understood. is it definitely confirmed that none of the betas had ARB?
    I don't know the answer to that. I also didn't participate in the Betas in any way at all other than sharing links for each new Beta version.

    personally I'm not willing to commit to no going back with a13 until I know all my critical apps are compatible.
    I haven't had any issues with any of my apps, but everyone's usage is different. Technically speaking, I can say that for a day or two after I flashed Android 13 Stable, the root/Xposed-based AOSP Mods only partially worked with Android 13, but it's since been updated to fully support all the features on Android 13 that I cared about, and then some.