General 🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
- Thread starter V0latyle
- Start date
With Better Battery Stats you can issue adb commands to grant permissions, although I don't know if this will completely work for Android 13 since I'm rooted.
I think you can do the same with GSam Battery monitor although you may need root for additional stats.
- Feb 20, 2011
- 5,123
- 1
- 7,868
Not really the place for this kind of discussion. Gripes about Android 13 as well as questions unrelated to the bootloader rollback should be posted elsewhere.
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
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:
- Feb 20, 2011
- 5,123
- 1
- 7,868
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.
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"
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"
- Feb 20, 2011
- 5,123
- 1
- 7,868
You can also use the
--force argument when flashing the system image, which ignores the bootloader/baseband requirement.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.
www.xda-developers.com
Any help appreciated thanks.
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.
Here's how you can unlock the bootloader and root the Google Pixel 6a with Magisk
Looking to root your brand new Google Pixel 6a? Here's how to unlock the bootloader and root the latest mid-ranger Pixel smartphone!
Any help appreciated thanks.
- Feb 20, 2011
- 5,123
- 1
- 7,868
If you have updated at least TWICE via OTA since August, you should have the Android 13 bootloader in both slots.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.
Here's how you can unlock the bootloader and root the Google Pixel 6a with Magisk
Looking to root your brand new Google Pixel 6a? Here's how to unlock the bootloader and root the latest mid-ranger Pixel smartphone!
Any help appreciated thanks.
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:
- Feb 20, 2011
- 5,123
- 1
- 7,868
@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?
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?
- Feb 20, 2011
- 5,123
- 1
- 7,868
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.
@V0latyle
According to https://www.getdroidtips.com/root-pixel-android-13-magisk/
They recommend fastboot boot magisk_patched.img instead of FLASH. Which one should I follow?
According to https://www.getdroidtips.com/root-pixel-android-13-magisk/
They recommend fastboot boot magisk_patched.img instead of FLASH. Which one should I follow?
I'm on Magisk v25.2 and build TP1A.220905.004.A2.
I've tagged you in the How to Guide thread.
- Feb 20, 2011
- 5,123
- 1
- 7,868
Again, take these questions to the guide thread. Thanks
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
13***Note: THIS IS NOT A ROOT GUIDE. Please do not post questions concerning root 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 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 continue9
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 lol7
@blackhawk is entitled to his opinion, just as you are. Remember to keep your conduct civil and respectful:
