yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Dracarys321..:
I am trying sideloading the ota again...been following every step....device do show up on adb devices command but on next step when try to sideload file.zip..it says cannot read file.zip....please help a noob here
[Google Pixel 6 Pro] V0latyle:
Try this:

Reboot your device into sideload mode:

Use adb reboot sideload via your ADB command window

Or, if you are already rooted, open Magisk, tap the Reboot button at the top, and select Reboot to recovery

Or, hold Volume Up while booting to enter recovery

If you used steps 2 or 3 above, once you see the green Android with "No command", hold Power and click Volume Up, then select Apply update from ADB

Connect via USB and open a command window in your ADB Platform Tools folder

Your screen should read Now send the package you want to apply to the device using "adb sideload <filename>"...

In the ADB command window, type adb sideload, then drag and drop the OTA package into the command window. Make sure you leave a space after "sideload".

The update should apply and reboot the device.
[Google Pixel 6 Pro] RetroTech07:
I have no idea what you just said...
[Google Pixel 6 Pro] sarabraj.singh:
be careful with the new bootloader process.

i tried wiping my partitions and slots with

fastboot --set-active=a -w
fastboot --set-active=b -w

before updating to the September release and it bricked my phone. Luckily I was able to get a replacement device from Google because there's no fix to this brick yet (as of writing this, October 2nd).

just a FYI for everyone
[Google Pixel 6 Pro] V0latyle:
Why are you using the -w argument when switching slots? You probably wiped your bootloader partitions.

This is why it's important to ask questions before you try things when you don't know what the potential outcome is.
[Google Pixel 6 Pro] sarabraj.singh:
this used to be the canonical way to wipe everything and flash a new image prior to A13. it even worked when upgrading from A12 -> A13_beta -> A13.
[Google Pixel 6 Pro] V0latyle:
Since when? I have never heard of using the -w arguments when switching slots. Some use fastboot erase <partition> while others use the -w argument when flashing the system image (which does not flash bootloader) but never since the Nexus devices have I ever seen a full wipe combined with a slot switch.
[Google Pixel 6 Pro] surej_84:
First of all thanks to all for this info. I received my new pixel 6 pro yesterday. I am not planning to root or unlock the bootloader for the first 6 months. Iam currently updating the device to A 13 via OTA. Please advise me if I should sideload the factory image to the second slot once the OTA installation is over ( iam a noob and this is my understanding of the issue...apologies if it's illogical) . Or should I wait for the next months OTA update ? ( I think I read somewhere that the next OTA will install in the second slot). I hope iam making sense. Thanks again
[Google Pixel 6 Pro] V0latyle:
The factory image cannot be sideloaded; only the OTA image can.

But to answer your question, yes, you would simply sideload the OTA again.
[Google Pixel 6 Pro] AlexAuran:
Alright, I'm dumb. I read through this thread, thought I understood, then did the following:

1) Was on A12.

2) Flashed A13 bootloader only from the factory image to slot a and b.

"fastboot flash bootloader -slot=all bootloader-raven-slider-1.2-8895132.img"

The thought was I don't care if A12 runs properly, just want to get the bootloader unbrickable, then clean install A13 factory. Both slots return "fastboot getvar version-bootloader version-bootloader: slider-1.2-8895132"

3) Booted into A12 just fine.

4) Flash-all without -slot=all

5) Device boot loops as corrupt. Flash Tool will not detect phone. Fastboot detects from bootloader, adb from recovery and rescue.

6) Flash-all both slots, still corrupt.

Any ideas?
[Google Pixel 6 Pro] V0latyle:
You have to be in bootloader to use the Flash Tool.

Have you tried reflashing the A13 image?
[Google Pixel 6 Pro] AlexAuran:
I have access to the bootloader and fastboot detects the phone just fine, but AFT doesn't connect at all. I have flashed the A13 factory image several times with no success.
[Google Pixel 6 Pro] V0latyle:
If fastboot sees the device, Android Flash Tool should work. Make sure you allow ADB permissions in your browser; Google Chrome is recommended as not all browsers have WebADB capability.

To explain a little bit what's going on, I assume you're seeing a screen similar to this on boot:

This has nothing to do with the bootloader, and just means that Android has crashed enough times that the device thinks neither slot is bootable.

If you don't care about losing data, just perform factory reset; your device should boot fine.

If you want to try to keep data, see if you can sideload the OTA.
[Google Pixel 6 Pro] AlexAuran:
AFT doesn't see the device with ADB Permission granted on both MacOS and Windows Chrome Stable.

If I boot into recovery, I see the no command android, but pressing up+power doesn't show this menu.

I don't ever see the recovery menu. I can boot into the bootloader without issue. If I do a system boot, "Start", I get the Google Logo for about 5 seconds, then looped back to the bootloader.

If I flash-all, it completes successfully but then shows the red corrupt error screen, if I don't touch it at all, it loops and reboots until it ultimately shows the charging icon.

I'm fully backed up and don't care about any data. I'm completely stumped.
[Google Pixel 6 Pro] V0latyle:
First, make absolutely sure you are using the latest ADB Platform Tools.

You have to be in bootloader mode. If you're in bootloader, and fastboot devices shows the device, Android Flash Tool should work. But, it probably won't help unless you force flashed all partitions which would require a data wipe.

To enter the recovery menu, hold Power, and click Volume Up. Don't click them at the same time; you have to be holding Power when you click Volume +.

Please post a picture of this screen. Is it like the one I posted above?

If it's this one, we have a different problem:

Well, let's see if sideloading works. Boot your device into recovery, get into the menu as I described above, and select Apply update from ADB. Connect to your PC, and download this file (OTA, Raven TP1A.221005.002).

In your ADB command window, type adb devices to ensure ADB sees your device, then type adb sideload <drag and drop the OTA package you just downloaded>. This will update the alternate slot, and once complete, should reboot into that slot.

If this doesn't work, boot to bootloader and try fastboot -w which will wipe both data and cache.

Alternatively, you can boot to recovery and select Factory Reset.
[Google Pixel 6 Pro] AlexAuran:
@V0latyle I switched to a stock windows 10 VM that didn't have any adb or drivers installed. Downloaded everything fresh, got it booted. Turns out I mixed up .zip files on the original machine, so I didn't have the latest ADB Tools on the machine. I didn't look into it closely because I thought the if/then in the flash-all.bat would check that requirement since it's coded right there and all the commands seemly worked. Yes, I know that's a basic step. Admitting it publicly in case it helps someone else. Sorry for wasting your time, but thank you for your help. Can I buy you coffee?
[Google Pixel 6 Pro] V0latyle:
I don't have any way to accept donations, and I wouldn't if I did. You can help me by helping everyone else here on XDA.
[Google Pixel 6 Pro] NexusPenguin:
Why ?

Why ?

Why ?

Why do manufacturers do such things ?

What is the harm in rolling back a device ?

You know what : SCREW GOOGLE.

I thought the Pixel devices would be "open to development" devices.

They are not.

What if I do not like the new stupid Android UI after I tested it ?

So I assume even if I flash the A12 factory image to both slots after upgrading to A13, I'm screwed...

Does this also applies to A13 custom ROM ?
[Google Pixel 6 Pro] V0latyle:
Wrong place. I don't appreciate any sort of trash talking in my threads.

This has not changed. The bootloader update (as well as subsequent anti-rollback) was done for security reasons to close a major exploit in the previous bootloader. This update has little effect on development for Tensor devices. The only thing this changes is the ability to roll back factory firmware.

You can flash an Android 12 Developer GSI image, or you can use custom ROMs.

You cannot roll back the bootloader. You -can- force flash the Android 13 system image without updating the bootloader but it may not work properly. You can also force flash the Android 12 system image on the new bootloader but it's also unstable. If you are concerned about any of this, don't update.

Once again, this has little to do with the OS. Bootloaders are always proprietary, and there are many OEMs that restrict or prevent development altogether - such as Samsung (newer bootloaders will refuse to boot custom OS). Google is not one of these, and the bootloader update does not prevent or restrict the use of custom ROMs. It is possible, given the fact that the stock Android 12 system doesn't work properly on the 13 bootloader, that developers may have to make more changes for their builds to be stable, but the fact remains that the new bootloader does not prevent flashing or using custom software.
[Google Pixel 6 Pro] NexusPenguin:
Hi,

Sorry...

But that anti-rollback thing is such a restriction and such a potential risk to brick the device (so far, I managed to brick 3 devices, and one of them was a Google device, one of the early Google devices made by LG some 5/6 years ago).

And you wrote that flashing back A12 over an A13 bootloader may cause a bricking of the device.

As I know I will probably play with the device some day, I was somewhat irritated to see that for some devices Google is less nice to play with than an unlocked device of some other brands.

So please accept my apologies.

Regards.
[Google Pixel 6 Pro] V0latyle:
No...

As far as I know, the bootloader will refuse to downgrade, so if you attempt to flash an older bootloader on the new one, it will simply fail.

The bricking issue is what I consider a poor rollout; since Pixels are A/B slot devices, the problem arises from when one slot is updated to Android 13 - as it would with an OTA - and the other slot isn't. If the device fails to boot from the Android 13 slot and attempts to "recycle" to the Android 12 slot, the bootloader won't load, rendering the device a brick.

So, it's fair to say that they probably could have implemented this better, with a solution that updates both slots at once.

That being said, bootloaders are almost always proprietary code and are NOT open source, so Google has the prerogative to roll out updates and make changes as they see fit. The update did NOT restrict development or prevent running older/alternative software, although the stock Android 12 software doesn't run properly on the 13 bootloader.

Either way, they essentially had the right to do this, and while we can agree that how they did it could definitely have been better, I don't see the point of arguing about why, as it's already been done, or ranting about how this makes it a little harder to do one specific thing - reverting to the previous factory builds of Android 12. I doubt this was their intent - all they were trying to do was close a security vulnerability; they've always had the ability to implement anti-rollback in previous devices but have apparently never had a critical issue that necessitated its use until now.

Keep calm and chive on.
[Google Pixel 6 Pro] pojr:
Hi,

Forgive me for asking a dumbass question. I'm on Android 12 (SQ3A.220605.009.B1) which is from June 2022. Looking to update to 13 but I have a question about updating the bootloaders for both slots.

I checked slot a and b, and here are the bootloader versions I'm on:

Current Bootloader Version (Slot B): slider-1.2-8318357

Current Bootloader Version (Slot A): slider-1.2-8318357

My questions:

I downloaded the latest factory image (TP1A.221105.002, Nov 2022), extracted the boot.img file and then patched with Magisk. Now it's back on my computer. Is this what I use to update the bootloader version on both slots?

If flashing the magisk patched boot.img isn't the way to update the bootloader version, how would I do this?

I notice the instructions say I should type in

fastboot flash bootloader --slot=all <bootloader image>

however whenever I flash the magisk patched boot.img file, I type in

fastboot flash boot_a magisk_patched.img

Is there a difference between these two statements (other than one flashing for both slots, and the other flashing for one slot)? I'm mainly talking about "flash bootloader" vs "flash boot". Is one completely diffferent from the other?

Again, I apologize for the dumb question. I would rather ask ahead of time than try a bunch of random **** and **** up like I usually do lmao.
[Google Pixel 6 Pro] V0latyle:
Slider? This seems odd....Are you sure you have the right firmware for your device?

No - boot.img is not the same as bootloader.img. Getting this wrong can brick your device. The image you need to update bootloader is in the root of the factory package, and is titled bootloader-raven-1.x-xxxxxxx.img

Here is an example using firmware for my Pixel 5:

See above. The boot image only contains kernel and ramdisk, and is contained in the image-device-buildnumber.zip. This is what you patch in Magisk.

Yes, once again, the bootloader and boot image are distinctly separate, and mixing up the two can permanently brick your device. ONLY flash bootoader images to /bootloader.

Tensor devices do not seem to permit using --slot all so the proper way to update bootloader on the Pixel 6 series is thus:

fastboot flash bootloader_a <bootloader image>
fastboot flash bootloader_b <bootloader image>
fastboot reboot bootloader

Well, given your evident confusion between the bootloader image and the boot image, it's good that you're asking questions.

For more questions on updating and rooting, please ask in one of the update + root guides, such as here. I encourage you to read other guides, such as this one written by my colleague @roirraW "edor" ehT .

Also, I encourage you to use PixelFlasher as it makes everything pretty foolproof.
[Google Pixel 6 Pro] silocybin:
How to Bypass Anti Rollback Mechanism in Pixel 6A/6/6 Pro

This guide will show you how to bypass Anti Rollback Mechanism while doing a downgrade from Android 13 to Android 12 on Pixel 6A/6/6 Pro.

www.droidwin.com

How legitimate is this guide? I'm willing to try it if it means I can use Viper again
[Google Pixel 6 Pro] V0latyle:
I have serious doubts. The guide describes using the Android 12 factory image, and either removing the Android 12 bootloader, or replacing it with the Android 13 bootloader. In either case, it isn't actually a downgrade, and would not work because Android 12 will not flash on the 13 bootloader without the --force argument. As described in the OP, this has been done before, and the result was very unstable.

TL;DR: the author of that article doesn't know what he's talking about, and seems to be drawing on limited experience with the Pixel series while being ignorant of the circumstances surrounding the anti-rollback.
[Google Pixel 6 Pro] silocybin:
Appreciate the reply guess I'm stuck with 13 because of Google.
[Google Pixel 6 Pro] V0latyle:
Well...Not entirely. Android 12 GSI images are available as well as Developer Support Builds although I don't know how usable they are as daily drivers. I think the DSB would be the better option, although you'll need to spoof a valid device profile using USNF/MHPC.
[Google Pixel 6 Pro] silocybin:
This is a daily driver phone can't risk it unfortunately
[Google Pixel 6 Pro] V0latyle:
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
[Google Pixel 6 Pro] Lughnasadh:
No it doesn't. Need to :

fastboot getvar version-bootloader for current slot, then switch slots.
[Google Pixel 6 Pro] V0latyle:
Okay, thanks
[Google Pixel 6 Pro] Hand76:
Im getting a secondary Pixel 6 Pro in the coming days. Going back to the original post:

"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."

So does this mean the first ota is installed on the active slot and the second ota will push the first one to inactive? Ending up with the same new bootloader for each?
[Google Pixel 6 Pro] Lughnasadh:
OTAs are never installed on your active slot. Every time you update via OTA the build is installed on your inactive/opposite slot. Once you initially update to A13 you will have the A13 bootloader installed on that one slot, which becomes your active slot after installation. The next time you update via OTA you will have the A13 bootloader (and everything else of course) installed on the inactive/opposite slot, therefore both slots at this time will have the A13 bootloader. This inactive/opposite slot now becomes your active slot.
[Google Pixel 6 Pro] Hand76:
Ok so kinda what I thought but in reverse. And I learned something. Thank you!
[Google Pixel 6 Pro] V0latyle:
Exactly. So, regardless of how someone updates to Android 13 in the first place, sideloading the OTA (or taking automatic OTA) will update the "other" slot.

Yeah. The idea here is Seamless System Updates, where the device can be running on one slot while updating the other slot. This is contrary to single slot devices, which have to reboot into recovery and are unusable during the update process. It also provides a failsafe - if the updated slot fails to boot, the device can recycle back to the good slot. This failsafe combined with the anti-rollback is what presents the risk for bricking on the Pixel 6; if a user is running Android 12, updates via OTA, and the initial boot is successful (or gets far enough into the boot process that the anti-rollback is triggered), a boot failure can cause the device to attempt to boot from the "old" slot, which if it still has Android 12, can result in the bootloader failing to load.
[Google Pixel 6 Pro] Hand76:
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?
[Google Pixel 6 Pro] Lughnasadh:
Yes, you have the A13 bootloader on both slots.
[Google Pixel 6 Pro] anawilliam850:
thank you! i will read this before update to this version
[Google Pixel 6 Pro] Juuuuune:
How do I get root access to my pixel 6 Pro, do I just need to do it like pixel4？（translate form Google）Android13 version
[Google Pixel 6 Pro] V0latyle:
This is not a root guide. The link for the guide is at the top of the OP.
[Google Pixel 6 Pro] Juuuuune:
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！
[Google Pixel 6 Pro] V0latyle:
The instructions to check the other slot are in the OP as well.
[Google Pixel 6 Pro] Meo15:
Very informative, thank you!
[Google Pixel 6 Pro] AnyNameYouWish:
Updated from A12 to A13 with PixelFlasher with "Flash both slots" option.

Worked like a charm (y)
[Google Pixel 6 Pro] Guzzlor:
Sorry guys, I am back to the rooting world after many years. I have a magisk Android 12 - is there a way to go up to 13 without losing my data? Or should I start from scratch?

Thanks if you can help.

Can you point me to a guide? Did you lose your data?

Thanks.
[Google Pixel 6 Pro] AnyNameYouWish:
V0latyle's guide and Pixelflasher'guide are the ones I used. You'll have to turn on expert mode in Pixelflasher to see the Flash both slots options (File -> Configuration).

Beside that, I won't be able to explain better than original guides do.
[Google Pixel 6 Pro] adamf663b:
I've had enough troubles with magisk on ota updates that I cut to the chase and always do a full factory install, with the sd wipe disabled.
[Google Pixel 6 Pro] Olesya13:
Thanks for the tip, it really came in handy!
[Google Pixel 6 Pro] Barrel Titor:
Sorry.. But i'm a bit confused.. Normally i know my way around rooting and stuff but i honestly don't know what to do in this situation right now.

I just bought a brand new google pixel 6 pro.. It is still on android 12 and i have only toggled the "enable OEM unlocking" switch in the settings, not yet unlocked it via fastboot.

Should i unlock the bootloader now on A12, then upgrade to A13 (i believe not but i'm not sure)

Should i upgrade to A13, then unlock the bootloader

Or something completely different?

I'm a bit confused here, sorry..
[Google Pixel 6 Pro] V0latyle:
Unlock the bootloader, then flash the latest bootloader version to both slots before you do anything else.

Reboot to bootloader

Unlock bootloader

Reboot to bootloader again

Download latest factory image for your device (this one for Pixel 6 Pro)

Unzip the factory image package

Flash the new bootloader to both slots: fastboot flash bootloader --slot=all <bootloader image path or drag and drop file>

Bootloader is bootloader-raven-slider-1.2-9465321

Verify the flash was successful in the CMD print

Reboot to bootloader again, then continue updating everything else
[Google Pixel 6 Pro] Nergal di Cuthah:
All correct (of course) except they have a p6p not 6a ;)
[Google Pixel 6 Pro] V0latyle:
Whoops. Fixed.
[Google Pixel 6 Pro] Nergal di Cuthah:
Almost one more fix. name of bootloader still points to bluejay (sorry with all my heart. You do great work and your tutorial gets me through each month)
[Google Pixel 6 Pro] V0latyle:
Goddamnit lol
[Google Pixel 6 Pro] Barrel Titor:
@V0latyle @Nergal di Cuthah

Thank you so much!!

It's honestly a bit scary xD

I've been rooting since the LG Optimus G E975 (Released Nov. 2012), pretty much written the guide on how to root the Huawei P20 Lite after they changed their partitioning layout around, yet it still feels scary rooting a totally new device haha.
[Google Pixel 6 Pro] Barrel Titor:
"then continue updating everything else", meaning what exactly?

updating the system via fastboot or updating "everything else" via android 12/OTA?
[Google Pixel 6 Pro] Barrel Titor:
Okay, so. Thank you VERY MUCH again @Nergal di Cuthah for the help.

I've (or rather we've) figured out how to proceed..

I must say, this entire process was entirely different to any device i've ever dealt with! Really feeling like a noob again.

But looks like everything is working fine now and i no longer need assistance :)

Thanks again to everyone who helped
[Google Pixel 6 Pro] V0latyle:
Either/or. The most important thing is to ensure you update both bootloader slots at the same time.

Totally get it, I came from Samsung to Pixel so it was a learning experience for me, too...but Google actually does things the "right" way by following the AOSP model. A lot of OEMs don't. The "Pixel way" is blessedly simple once you understand how everything works.
[Google Pixel 6 Pro] TheTrueJayTwenty:
Oh, this sucks I just got a P6P on A13. But I wanted to run an A12 custom ROM. Oh well hopefully development catches up for A13
[Google Pixel 6 Pro] V0latyle:
This won't prevent you from running a custom ROM.
[Google Pixel 6 Pro] TheTrueJayTwenty:
I could be mentally slow but would I not have to stick to A13 custom roms?
[Google Pixel 6 Pro] V0latyle:
Not necessarily.

We have only established that the factory Android 12 image won't run properly on the Android 13 bootloader.

I cannot say for certain whether this would cause problems with aftermarket Android images. I don't think it would, but I could be wrong.
[Google Pixel 6 Pro] TheTrueJayTwenty:
Has anyone tried flashing a custom A12 ROM on a P6P after device was updated to anti rollback A13 boot image?
[Google Pixel 6 Pro] mmddzzjj:
Hello, moderator, I don’t know what to call you, right? I just bought this phone and it’s already Android 13. I can’t understand your text, so I don’t understand the meaning. I want to ask you if I update Android 14 with ota and then repair the boot to get root Will it cause bricking?