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

Search This thread

mbk17

Senior Member
Nov 16, 2011
163
10
I just received this phone today. Both A and B have bootloader version "bluejay-1.2-8893284" and is on Android 13 August 2022 (build TP1A.220624.021.A1). Am I safe to flash the November image and then follow the root guide process?
 

Bad Bimr

Senior Member
Dec 29, 2010
218
35
I think my phone bricked tonight because of this. Pixel 6a on 13 from a flash. Attempted a to take the OTA and it failed. Tried to flash the newest build on the inactive slot with PF and the phone is is 100% unresponsive. Black screen, can't hard reset nothing. I did notice if you connect to PC and press power, Vol Up and Vol down at the same time it chimes like it connects, releasing the power chimes again like it disconnected.
Called Google they told me to send it in but I am hoping for a quicker solution. Anyone have luck getting these phone working again?
Thanks
BB
 
Last edited:
I think my phone bricked tonight because of this. Pixel 6a on 13 from a flash. Attempted a to take the OTA and it failed. Tried to flash the newest build on the inactive slot with PF and the phone is is 100% unresponsive. Black screen, can't hard reset nothing. I did notice if you connect to PC and press power, Vol Up and Vol down at the same time it chimes like it connects, releasing the power chimes again like it disconnected.
Called Google they told me to send it in but I am hoping for a quicker solution. Anyone have luck getting these phone working again?
Thanks
BB
Nope, the tools and files necessary to recover the device are not publicly available, and Google's recommended fix is replacing the mainboard.

I had the same thing happen to my wife's Pixel 5a. Fortunately I still have my Pixel 2 laying around so that became her temporary phone; the repair took about a week because they didn't have the necessary parts.
 

walter79

Recognized Developer
Dec 18, 2006
4,116
4,628
This bootloader works with Android 12 if you have updated your Phone to Android 13.

It is from Android 12 beta firmware bluejay-sd2a.220601.004.x2 (bootloader-bluejay-bluejay-1.1-8927508.img)

Bootloader works with official Android 12 rom.

For flashing official Android 12 rom you have to edit android-info.txt inside the image-xxx--zip

"require version-bootloader=bluejay-1.1-8419703" change to "#require version-bootloader=bluejay-1.1-8419703"
 

Attachments

  • bootloader-bluejay-bluejay-1.1-8927508.img
    11.2 MB · Views: 7
This bootloader works with Android 12 if you have updated your Phone to Android 13.

It is from Android 12 beta firmware bluejay-sd2a.220601.004.x2 (bootloader-bluejay-bluejay-1.1-8927508.img)

Bootloader works with official Android 12 rom.

For flashing official Android 12 rom you have to edit android-info.txt inside the image-xxx--zip

"require version-bootloader=bluejay-1.1-8419703" change to "#require version-bootloader=bluejay-1.1-8419703"
You can also use the --force argument when flashing the system image, which ignores the bootloader/baseband requirement.
 

noobie2022

Member
Dec 15, 2022
29
5
I read about the scary bricking with Android 13 in the previous posts.

I'm going to do my 1st ever Magisk rooting of Pixel 6a that carries Android 13. Updated from Android 12 some time back.

Does this slot A slot B flashing apply to me?

Additionally, these guides do not mention slots A or B.

Any help appreciated thanks.
 

noobie2022

Member
Dec 15, 2022
29
5
I just received this phone today. Both A and B have bootloader version "bluejay-1.2-8893284" and is on Android 13 August 2022 (build TP1A.220624.021.A1). Am I safe to flash the November image and then follow the root guide process?

How did you check the bootloader version for both slots A and B? Curious!
 
I read about the scary bricking with Android 13 in the previous posts.

I'm going to do my 1st ever Magisk rooting of Pixel 6a that carries Android 13. Updated from Android 12 some time back.

Does this slot A slot B flashing apply to me?

Additionally, these guides do not mention slots A or B.

Any help appreciated thanks.
If you have updated at least TWICE via OTA since August, you should have the Android 13 bootloader in both slots.

How did you check the bootloader version for both slots A and B? Curious!
There's commands to do this in the OP, but if your bootloader is locked, you won't be able to switch slots. Since you're planning on rooting, I would recommend unlocking first, then follow the instructions to check versions on both slots.
 
  • Like
Reactions: noobie2022

noobie2022

Member
Dec 15, 2022
29
5
If you have updated at least TWICE via OTA since August, you should have the Android 13 bootloader in both slots.


There's commands to do this in the OP, but if your bootloader is locked, you won't be able to switch slots. Since you're planning on rooting, I would recommend unlocking first, then follow the instructions to check versions on both slots.

Thank you very much @V0latyle !

My bootloader is unlocked and shows Android 13 (bluejay-1.2-9152140) in the A and B slots.

Since both slots have the same Android version, do I still need to flash bootloader to both slots?

-----

Please advise.
 
Last edited:
Thank you very much @V0latyle !

My bootloader is unlocked and shows Android 13 (bluejay-1.2-9152140) in the A and B slots.

Since both slots have the same Android version, do I still need to flash bootloader to both slots?

-----

Please advise.
As long as they're both Android 13, no.
 
  • Like
Reactions: noobie2022
@V0latyle

I have done this below, but all I see is the Google logo on phone screen. Did something go wrong?

fastboot flash boot magisk_patched.img
fastboot reboot

Guide: https://www.xda-developers.com/how-...magisk-google-pixel-6a/#flashpatchedbootimage

How do I 'unflash' an image?
Overwrite it with a different image, like the unpatched boot image

This thread is specifically about the anti-rollback; if you have questions about flashing and root I ask that you pose those in my guide.
 
  • Like
Reactions: noobie2022

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hai i new here
    Abit abit confius abit.
    I just waiting for my pixel 6a to arrive.
    If i receive phone with android 13 rom and both slot is android 13. I will never roll back to rom android 12 because of anti roll back. This one only apply for official rom rite( stock rom google)
    My question is, if i use custom rom A13 and rollback to custom rom A12. I will get any issue?

    Sorry for by bad English
    You can use a custom A12 ROM, but I have no idea whether you'll have issues or not. It's worth a try as it won't break anything. Just make sure you wipe /data.

    Don't worry about your English, we have people all over the world on this site. We do appreciate you using English as is required by our forum policy. You are more than welcome to use Google Translate if you find it easier for you.
  • 13
    ***Note: THIS IS NOT A ROOT GUIDE. Please do not post questions concerning root here.***

    From the Pixel Images page:
    1668631439637-png.5763217


    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
    9
    That would be the scoped storage sucking up resources/battery to make you feel safe...
    Android 10 is ok, 11 so-so, 12 sucks and along comes 13 beta. Yeah that'll work.
    Blame Gookill for this fubar.
    I mean...I've kinda liked A12. But to each his own.

    You'd probably rather run command line Linux on your phone, you old bastard lol
    6
    This is such BS. Drama
    @blackhawk is entitled to his opinion, just as you are. Remember to keep your conduct civil and respectful:
    2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
    5
    1000% fake comment.