PSA: Seems at the moment people aren't able to root this beta on Pixel 6s.New
The Developer Preview QRP2 Beta Factory/OTA image links are in the OP, Part I, NEW.
PSA: Seems at the moment people aren't able to root this beta on Pixel 6s.New
The Developer Preview QRP2 Beta Factory/OTA image links are in the OP, Part I, NEW.
Apparently patching the Pixel 7 boot image and flashing it on the Pixel 6 will work for getting root as a temporary workaround.PSA: Seems at the moment people aren't able to root this beta on Pixel 6s.
Pixel 6a, Pixel 6, and Pixel 6 Pro
* * * * * Regular Users * * * * *
* * * * * No Downgrading * * * * *
![]()
PSA: Once you update to Android 13 on Pixel 6, you can't go back
Android 13 is out for Pixel devices today. But if you have a Pixel 6, 6 Pro, or 6a, you may want to make sure you're ready before updating.www.androidauthority.com
* * * * * This is why there is No Downgrading * * * * *
If you are referring to the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 3. Take the OTA Update and Maintain Root instructions. You rebooted to soon. Additionally, an upgrade for the Google Pixel 6/Pro/6a to Android 13 requires flashing the bootloader to the a and b slot to avoid bricking your phone.
Further, the instructions in the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 2. Install/Update Factory Image keep data, wipe data, or use @badabing2003 PixelFlasher are the instructions most people should use to upgrade to Android 13.
Yes. because the Google Pixel 6a have two slots:Hi there, I'm going to do my 1st ever Magisk rooting of Pixel 6a that carries Android 13. Updated non-rooted 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!www.xda-developers.com
Yes. because the Google Pixel 6a have two slots:
Active and Inactive or A and B slots.
Option 2., is the quickest and easiest way to flash the bootloader to the inactive slot.Thanks. I see.
Does that mean these guides have missing crucial steps?
![]()
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!www.xda-developers.com
-----
In other words, they're missing these steps from
https://developers.google.com/android/images/
"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."
If you have android 13 installed to your phone, and it is booting to Android 13. Do not flash Android 12 to any slot.@Homeboy76
Would it be safer to "install into inactive slot B" housing Android 12 before even installing into active slot A?
Option 2., is the quickest and easiest way to flash the bootloader to the inactive slot.
Magisk has nothing to do with flashing the bootloader. Magisk deals with the boot image. They are 2 different things. If you are trying to flash the A13 bootloader to your inactive slot (to make sure you have the A13 bootloader on both slots), just do as as @Homeboy76 alluded to:View attachment 5786201
Thanks @Homeboy76!
Using Magisk,
- Is this "direct install" == flash the bootloader to the active slot?
- Is "install to inactive slot (after OTA)" == flash the bootloader to the inactive slot?
My boot slot is B with Android 13. I wonder what's the Android version in the inactive slot A?
Can I avoid the below if I'm using Magisk? I presume there's more than 1 way to do option 2: using magisk on the phone OR using CMD on PC.
fastboot --slot=otherflash bootloader bootloader_filename.imgfastbootset_active afastboot reboot bootloaderfastbootset_active bfastboot reboot bootloaderfastbootreboot
fastboot flash bootloader --slot=other <bootloader image>
Are you rooted and trying to update Magisk?View attachment 5786201
Thanks @Homeboy76!
Using Magisk,
- Is this "direct install" == flash the bootloader to the active slot?
- Is "install to inactive slot (after OTA)" == flash the bootloader to the inactive slot?
My boot slot is B with Android 13. I wonder what's the Android version in the inactive slot A?
Can I avoid the below if I'm using Magisk? I presume there's more than 1 way to do option 2: using magisk on the phone OR using CMD on PC.
fastboot --slot=otherflash bootloader bootloader_filename.imgfastbootset_active afastboot reboot bootloaderfastbootset_active bfastboot reboot bootloaderfastbootreboot
Magisk has nothing to do with flashing the bootloader. Magisk deals with the boot image. They are 2 different things. If you are trying to flash the A13 bootloader to your inactive slot (to make sure you have the A13 bootloader on both slots), just do as as @Homeboy76 alluded to:
fastboot flash bootloader --slot=other <bootloader image>
Since you have A13 on slot b, use that same bootloader image when flashing.
Are you rooted and trying to update Magisk?
why do I ask?
The latest version of Magisk Beta/Stable is 25-2
The latest version of Magisk Canary is 25205.
Yes, the inactive slot is A.
@noobie2022@Lughnasadh thanks for enlightening!
I found out that I have the same bootloader version, i.e. Android 13 bluejay-1.2-9152140, on both slots A and B.
Do I still need to flash the same bootloader image on both slots A and B?
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?
What is the build #?Thanks! @Homeboy76 @Lughnasadh
Is there a link where I can verify if bluejay-1.2-9152140 is truly Android 13?
I made the assumption because my bootloader version has a larger number than @mbk17 's.
That is the September image.
That is the September image.
13.0.0 (TP1A.220905.004.A2, Sep 2022)
Just install the December factory image: Factory Images for Nexus and Pixel Devices
"bluejay" for Pixel 6a
13.0.0 (TQ1A.221205.011, Dec 2022)
FYI - You do not need to root to enable VoLTE/VoWIFI, check this thread for simple solutionHi, all
I bought a refurbished Google Pixel and imported to my (unsupported) country. While it arrived, I was searching for important info and found that I needed to root the device to make use of the VoLTE/VoWifi feature, nothing that really mattered to me anyway as I've been rooting devices most of the time I've been using an Android phone.
I gathered the required info and even downloaded the latest device specific factory images. My only question here is: do I need to first allow the phone to do the first-time boot and wizard and even OTA update to the latest and then root or may I boot directly the device in fastboot, flash-all (script) the latest factory image and then flash the patched boot, all at once, before the first boot?
It's just to avoid downloading and erasing and then flashing everything again. BTW, I wouldn't be rooting the phone if I wouldn't need this phone feature. Also I usually root phones I want or need but after some weeks of use, so that's why I raised this short and maybe stupid doubt above.
Regards,
It is ok to be apprehensive about trying something new: ...In searching for a way to regain root by patching and flashing even using PixelFlasher...Maybe I'm getting old, but the instructions in the first post in this thread are super confusing for me. So so so many options. I've accidentally touched "Upgrade to Android 13" in my notification bar and am now on 008.E1 and root has dropped off (no surprise there). In searching for a way to regain root by patching and flashing, even using PixelFlasher, I'm really scared to try anything in this guide in case I've missed a pre-requisite.
Google Pixel 6 series updates are up.From another thread : It seems like they are having some issues again, as a Google Support person has told on the chat that the March 2023 update for the Pixel 6 series devices will come on the 20th of March 2023. This from the Kirisakura-Kernel for the Pixel 6/Pro posting.
fastboot flashing unlock
and press enter.fastboot reboot
at the Command Prompt and press enter.fastboot flashing lock
fastboot reboot
adb wait-for-device shell magisk --remove-modules
fastboot Reboot
flash-all
at the Command Prompt and press enter.flash-all
at the Command Prompt and press enter.adb wait-for-device shell magisk --remove-modules
fastboot Reboot
fastboot flash boot --slot all boot.img
fastboot flash boot "name of patched boot".img
without the quote marks at the Prompt and press enter.fastboot reboot
at the Prompt and press enter.fastboot flash boot boot.img --slot all
adb wait-for-device shell magisk --remove-modules
fastboot devices
to verify communication with phone. It should return your phone's serial number.Yeah, sometimes flashing an old boot image (it will fail to boot) and then flashing a new boot image works. Sometimes sideloading an OTA works. Sometimes just waiting for the next monthly OTA works. It's a crazy thing with this Pixel 6 series and the changes that have come with it.Thank you both @Lughnasadh and @capntrips!
What's odd is I did reflash my boot image thinking that would fix but it didn't, had to reflash anew from sideload.
Thanks again for the info