yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Nergal di Cuthah:
nope same error. tried --slot=all at end got a different error. added path to files same error and slot at end.

D:\android\platform-tools>fastboot flash bootloader --slot=all bootloader-raven-slider-1.2-8739948.img
Sending 'bootloader' (11554 KB) OKAY [ 0.352s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed

D:\android\platform-tools>fastboot flash bootloader bootloader-raven-slider-1.2-8739948.img8739948.img --slot=all
fastboot: error: cannot load 'bootloader-raven-slider-1.2-8739948.img8739948.img': No such file or directory

D:\android\platform-tools>fastboot flash bootloader d:\android\platform-tools\bootloader-raven-slider-1.2-8739948.img8739948.img --slot=all
fastboot: error: cannot load 'd:\android\platform-tools\bootloader-raven-slider-1.2-8739948.img8739948.img': No such file or directory

D:\android\platform-tools>

D:\android\platform-tools>fastboot flash bootloader --slot=all bootloader-raven-slider-1.2-8739948.img
Sending 'bootloader' (11554 KB) OKAY [ 0.376s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed

D:\android\platform-tools>fastboot flash bootloader bootloader-raven-slider-1.2-8739948.img --slot=all
Sending 'bootloader' (11554 KB) OKAY [ 0.363s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed

D:\android\platform-tools>
[Google Pixel 6 Pro] Namelesswonder:
It does not update both slots. If you are planning on modifying your device then you should update the bootloaders on both slots. If you aren't and are keeping your device locked then you don't have to worry because you won't be able mess up the device.

The original post has directions on how to do it in the middle and bottom.

It shouldn't matter, fastboot uses getopt_long which handles both cases.

fastboot/fastboot.cpp - platform/system/core - Git at Google
[Google Pixel 6 Pro] V0latyle:
Believe it or not, I think this is the anti-rollback protection kicking in.

The boot HAL marks a slot active post update, attempts boot, and once the boot reaches a certain point it marks the slot as successful.

When you manually switch slots, the system gets confused - no update had been performed so why are we now on the alternate slot? If the old slot happens to be an older version that adds to the confusion because the device thinks the update failed...but the boot was successful...but now we're old again...and gets stuck.

Has nothing to do with /data.
[Google Pixel 6 Pro] Namelesswonder:
I don't know why the bootloader keeps on kicking back and failing on the file. Can you run fastboot getvar version-bootloader and try a different USB cable and port? You are also typing in the wrong file name at the end.
[Google Pixel 6 Pro] V0latyle:
No bueno. You've already used the Android Flash Tool?

Hint: you don't have to type a filename, once you have your commands in, just drag and drop the file you want to flash into the command window
[Google Pixel 6 Pro] roirraW "edor" ehT:
Do this:

Whatever slot you're currently on (forget "--slot all", and you're not alone - slot all has failed to work for some other people as well, while working for still others):

adb reboot bootloader
fastboot flash bootloader bootloader-raven-slider-1.2-8739948.img

Once that successfully flashes, do:

fastboot --set-active=other
fastboot reboot bootloader

Then once it reboots into the other slot, one more:

fastboot flash bootloader bootloader-raven-slider-1.2-8739948.img

I would go one step further now, and Flash-All.bat (with the -w removed so doesn't wipe) so it flashes the whole Android 13 to this other slot. Then:

adb reboot bootloader

Once you're in fastboot again, then:

fastboot --set-active=other
fastboot reboot

Then you should be booting back into your original slot how you left it (rooted, I assume).
[Google Pixel 6 Pro] Nergal di Cuthah:
yes, but it seems undecided that AFT does both slots.

Yeah, I fixed the wrong file name (not sure how it got changed used copy name paste) see the strike out and edit

D:\android\platform-tools>fastboot getvar version-bootloader
version-bootloader: slider-1.2-8739948
Finished. Total time: 0.005s

but it doesn't confirm the inactive slot only the active (which has 13 running perfectly on it)
[Google Pixel 6 Pro] Nergal di Cuthah:
nope same failure. It seems I'm doing something wrong or there was a platform tools update that I missed
[Google Pixel 6 Pro] roirraW "edor" ehT:
From what I saw, you're using Platform Tools 33.0.2, which is the latest, but you can always download it again to be sure. (SDK Platform Tools)
[Google Pixel 6 Pro] Namelesswonder:
You didn't, you are on the latest platform-tools. The only things I can point to are bad USB cable, bad USB port, maybe the fastboot USB driver is out of date or from a different vendor so I guess try making sure that is set correctly. I guess one last thing which I'm sure isn't the issue, but the bootloader is unlocked right?

It's not undecided. I've tested it.

The Google Android Flash Tool does not flash to both slots. "Force Flash to All Partitions" only flashes the bootloader and radio again if they are already the same version.
[Google Pixel 6 Pro] V0latyle:
Don't miss my last comment, either - instead of typing the file name, just drag the file into your command window. Doesn't matter where it is - CMD will automatically populate the file path.
[Google Pixel 6 Pro] Nergal di Cuthah:
Didn't type copied the name (Rename Ctrl C arrow over the .img) Pasted (right click command window)
[Google Pixel 6 Pro] Nergal di Cuthah:
yes, bl unlocked. am on rooted 13 on active slot. used the same cable, port, driver to AFT 13 two days ago
[Google Pixel 6 Pro] banshee28:
SO i posted in the Pixel Flasher thread but I think I am runing into this same issue here. I was originally on A12 and dirty flashed A13 Beta on slot b . It has worked fine. However now I am unable to get Android flash tool or Flasher to flash even while using Wipe all data options and force flash all partitions. When I try to flash, it reboots to fastboot but hangs then says no device found! Both tools do the same.
[Google Pixel 6 Pro] Nergal di Cuthah:
reboot fastboot is sending me to fastbootd is that correct?
[Google Pixel 6 Pro] Namelesswonder:
Were you in fastbootd the entire time? You shouldn't be, you can't flash the bootloader or radio from userspace fastbootd, only regular fastboot can.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Edit: no. I didn't see the d on my mobile.

Fastboot reboot fastboot

Reboots into regular fastboot.
[Google Pixel 6 Pro] Nergal di Cuthah:
THIS WAS THE ISSUE !!! bootloader installed

Spoiler content hidden.
[Google Pixel 6 Pro] Nergal di Cuthah:
yeah, I don't know why adb reboot fastboot sent me to d but I suddenly realized fastboot looked different
[Google Pixel 6 Pro] roirraW "edor" ehT:
Glad you solved it!

Nice job @Namelesswonder!
[Google Pixel 6 Pro] Namelesswonder:
Because the proper name is reboot bootloader. fastboot is for userspace fastbootd.

[nameless@5900x:/tmp/redfin-sq3a.220705.003.a1]$ fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.018s]
< waiting for any device >
Finished. Total time: 16.216s
[nameless@5900x:/tmp/redfin-sq3a.220705.003.a1]$ fastboot flash --slot all bootloader bootloader-redfin-r3-0.4-8351081.img
Sending 'bootloader' (8762 KB) OKAY [ 0.041s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed

To set the record straight for other people, this is fastboot mode:

This is fastbootd, you are not in the bootloader or fastboot mode, you can't flash the bootloader:
[Google Pixel 6 Pro] Nergal di Cuthah:
So @roirraW "edor" ehT needs to change the OP?
[Google Pixel 6 Pro] Namelesswonder:
Well, looking at it now, I guess he does. ;)
[Google Pixel 6 Pro] roirraW "edor" ehT:
DOH me! 🤦‍♀️ Changed in the OP and one two of the most recent times I said it in posts.
[Google Pixel 6 Pro] Nergal di Cuthah:
Well if I'm going to be the Guinea pig then at least i didn't blow the fuse as my backup plan is a 2xl with no sim
[Google Pixel 6 Pro] Namelesswonder:
The anti-rollback counter was already permanently incremented for you once you booted stock Android 13. The issue with bricking stems from the fact that at some point in the boot process one of the bootloaders checks if the Android bootloader is the correct version, and if not then will try to switch the other slot. However if the other slot is marked unbootable, from a broken ROM, then the slot can't switch and you've got a brick.
[Google Pixel 6 Pro] Nergal di Cuthah:
@Jmoney55 before you liked my previous reply and miss the rest of what's happened. No the android flash tool does not write to both slots, run the commands in the original post of this thread under PSA
[Google Pixel 6 Pro] Utini:
This should be exactly and all that one has to do for the update:

Nothing more should be required. It worked just fine.

Why isn't this just added to the OP? Simple and easy.
[Google Pixel 6 Pro] Lughnasadh:
There are many ways to update from A12 to A13. One of the methods outlined in the OP is basically how you did it except encompasses flashing the whole image to both slots, not just the bootloader to both slots as you have done.

It's also outlined how to use flash-all to update to one or both slots.

There is no "this is the only way it should be done" method. With all the tools we have available to us, there's probably at least 10 ways to update in a manner that prevents the user from being vulnerable to bricking their device due to the new ARB. All depends on what the user wants (e. g. whole image to one or both slots) and what method the user is comfortable with.
[Google Pixel 6 Pro] bush911:
My take is that it is better to flash at least bootloader to the two slots while flashing via fastboot.

Am I correct
[Google Pixel 6 Pro] Lughnasadh:
Yes, having the A13 bootloader flashed to both slots is the minimum required to keep you safe from the new ARB.
[Google Pixel 6 Pro] CRXed:
FYI, Partition is NOT the same as a Slot. So don't confuse the two.

Each slot has multiple partitions.
[Google Pixel 6 Pro] Lughnasadh:
I know.
[Google Pixel 6 Pro] CRXed:
Okay, you know, but I see stuff like this being posted and it's hella confusing for people not in the know.
[Google Pixel 6 Pro] proac:
How to fully update both slots?thank
[Google Pixel 6 Pro] roirraW "edor" ehT:
See the top of the OP of this thread. Thanks.
[Google Pixel 6 Pro] proac:
Thanks
[Google Pixel 6 Pro] somethingsomethingroot:
Is this going to be a concern with every bootloader going forward or just this initial one for A13?
[Google Pixel 6 Pro] roirraW "edor" ehT:
We cannot tell the future. :)

Seriously, though, the only information we have is about what's currently available. The reason that Google did it was very specific, and I agree that it was justified. Since Android 12 runs just fine on the Android 13 bootloader, if you decide to downgrade everything but the bootloader (since the bootloader can't be downgraded), there's no real issue except for the users who, unfortunately, try to boot Android 12 (including Android 12 bootloader) on the other slot after the active slot is upgraded to Android 13, which is when a permanent brick is encountered.

Further in the OP are shared posts regarding the reasoning why Google did it.

Having said all that, it's fully expected that the answer to your question is "just the initial one for A13". The reason my explanation is complicated is that we have no way of knowing if, for example, a serious downgrade vulnerability will be found to exist in this build of Android 13's bootloader. If that is discovered eventually (days, weeks, months...years from now), then it won't surprise me if they implement the same non-downgradeable bootloader policy yet again.

I hope this all makes sense.
[Google Pixel 6 Pro] gpvecchi:
I did this: phone updated to A13 and booted, then I flashed full OTA via adb. Now I should have the full image on both slots, right?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Sounds right. I don't use OTAs at all though, I prefer full images so that I know what's being flashed where.
[Google Pixel 6 Pro] Lughnasadh:
@roirraW "edor" ehT Check out the new instructions on the factory image download page. Maybe a day late and a dollar short but at least it's there now.

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Google Pixel 6 Pro] :
I would like to think Google is learning the errors of their ways from this debacle and we will probally see the next ARB on A15. I can see them not doing it for A14. But we cannot see the future. It's ironic that Google is going after Apple over the whole "we need to make SMS between IOS and Android better"--as if it's come kind of closed vs open dichotomy, which it seems Google is becoming more like Apple every day in that respect.
[Google Pixel 6 Pro] roirraW "edor" ehT:
My wife's unlockable but locked, stock, and non-rooted Pixel 6 Pro is getting the Android 13 OTA right now. It's been taking a while, but our Wi-Fi has also been a little funky the last few hours, so I think it's been interrupted at least once.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thanks! Putting this in the OP (with a modified URL to point to the "Updating..." section).
[Google Pixel 6 Pro] roirraW "edor" ehT:
New news for you.

From @Lughnasadh's update linked below:

You did exactly right (according to Option 1 at the link):
[Google Pixel 6 Pro] :
Wow. They (Google) wrote a whole essay on this **CENSORED**. Yeah that's good and all for those with good attention spans. This is NOT going to go well for Google. I see way more bricks to come unfortunately. What google should do is take the firmware links off that page. Then force the user to read ALL the steps and their essay then click button to go to the image downloads. Help try to minimize people who may have their own way of flashing things but not how Google wants/needs you to do on ARB builds. Yeah this is gonna bite them. Most people will be on A13 ok. But I think you will have a larger than usual percentage with bricked devices. Not just from rooters/modders but just everyday users. I think google F'd this one up on their lack of communication. The fact they had to update the steps and include that essay speaks volumes. Just my $0.02.

*Thank you to the moderator for NOT even giving me a chance to edit my post to conform to your questionable policies. Proof: You remove the 'CF' but not the 'F'd" up. I expect you to further edit this against my will. As you can see I censored the previously censored "CF".Why? to prove my poiint. Have a good day.
[Google Pixel 6 Pro] Namelesswonder:
@roirraW "edor" ehT @Lughnasadh @V0latyle

So after reading some threads of people failing to flash their devices with --slot all update I decided to update as I'll probably be getting a Pixel 7 before the disclosure on the vulnerability in the bootloader is released. After trying it I found that the Pixel 6 can't have update use --slot all.

Extremely weird, because on every other Pixel device they can flash all partitions to all slots no problem.

Well it turns out this is what is causing the issue:

Sending 'super' (4 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 0.015s]
Resizing 'product_a' OKAY [ 0.003s]
Resizing 'product_b' OKAY [ 0.002s]
Resizing 'system_a' OKAY [ 0.003s]
Resizing 'system_b' OKAY [ 0.002s]
Resizing 'system_ext_a' OKAY [ 0.002s]
Resizing 'system_ext_b' OKAY [ 0.003s]
Resizing 'vendor_a' OKAY [ 0.003s]
Resizing 'vendor_b' OKAY [ 0.003s]
Resizing 'vendor_dlkm_a' OKAY [ 0.003s]
Resizing 'vendor_dlkm_b' OKAY [ 0.004s]

The super partition holding the sizes of each partition is used, however the opposite slot for each partition is being resized to the same size and this isn't leaving enough space left. With several opposite slots being larger than they should be, like the system slot, or other slots being included when they shouldn't is messing things up.

A proper dynamic partitioning should be these:

Sending 'super' (4 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 0.013s]
Resizing 'product_a' OKAY [ 0.005s]
Resizing 'system_a' OKAY [ 0.004s]
Resizing 'system_ext_a' OKAY [ 0.002s]
Resizing 'system_b' OKAY [ 0.002s]
Resizing 'vendor_a' OKAY [ 0.002s]
Resizing 'vendor_dlkm_a' OKAY [ 0.002s]
Resizing 'vendor_b' OKAY [ 0.002s]

So with this in mind the proper instructions would be to update from Android 12 with fastboot:

adb reboot bootloader

fastboot --slot all flash bootloader bootloader.img

fastboot --slot all flash radio radio.img

fastboot reboot bootloader

fastboot --skip-reboot update image.zip

fastboot --set-active=other

fastboot reboot bootloader

fastboot update image.zip

If using Magisk instead use fastboot --skip-reboot update image.zip

fastboot reboot bootloader

Use the flash or boot method on your Magisk patched boot image.

Or with adb sideload:

adb reboot sideload

adb sideload ota.zip

adb reboot sideload - can be done from within the recovery

adb sideload ota.zip

The directions for if you are already on Android 13 are still steps 1-4 for fastboot or just steps 1-2 for adb.

There's actually one minor issue with Google's steps for option 2:

>adb reboot fastboot

They're having people reboot into fastbootd which can't flash the bootloader, so if the people try to continue from within fastbootd they'll have that issue.
[Google Pixel 6 Pro] Nergal di Cuthah:
So they're following the unfixed instructions and putting everyone where i was yesterday ?
[Google Pixel 6 Pro] Namelesswonder:
Yep.

And they didn't even correctly write the essay. :LOL:
[Google Pixel 6 Pro] crescentmage:
In the past with T-Mobile devices from Google and OnePlus, you will need to get a permanent SIM unlock for your phone from T-Mobile in order to unlock the bootloader. Certain devices had alternate shortcuts with ADB mentioned earlier in this thread, but there is no guarantee it will work for the Pixel 6, particularly as it has a new chipset.

The most reliable way was for the phone to be paid off completely and on a line for at least 40 days, though many people have convinced reps to wave the 40 day requirement if the phone is paid off (see 2nd and 3rd link below). Of course, there is no guarantee that this will work for the Pixel 6 as it is a new phone, but based on past behavior it seems likely.

See the following threads for more information:

https://xdaforums.com/t/how-to-unlock-the-t-mobile-bootloader.4256319/

https://xdaforums.com/t/how-to-unlock-t-mobile-phone-bought-online.4051567/post-81783317

https://xdaforums.com/t/can-anyone-...my-t-mobile-pixel-4a-5g.4198489/post-84461809

https://www.t-mobile.com/support/devices/unlock-your-mobile-wireless-device
[Google Pixel 6 Pro] mkhcb:
Thanks!
[Google Pixel 6 Pro] Cares:
You have to patch boot.img with 23011 and then use 23001. Either way, I tried it and it didn't work for me. Still fail Basic and CTS with his combination.
[Google Pixel 6 Pro] allenjthomsen:
The whole point is not to wait to sim unlock and unlock bootloader so people can flash custom roms/root ,that being if the command works to unlock oem unlock in dev options. I am currently waiting for my P6P or id test myself.
[Google Pixel 6 Pro] Pekempy:
Yep I've had the patched boot.img with 23001 apk, but magisk hide just unticked itself so I couldn't hide root from anything. Probably going to just wait for USNF to be updated for non riru
[Google Pixel 6 Pro] Cares:
No patch with the newer one 23011...then full uninstall 23011. Install older one 23001 and flash modified boot.

Either way, I did it and it didn't work for me. He's on a P5 though so maybe there's a difference with P6.
[Google Pixel 6 Pro] crescentmage:
Sure, and I would try that first, but the ADB command may or may not work. I was giving the next best thing by noting that people have succeeded in getting the 40 day waiting period waved from T-Mobile in the past (typically using @TMobileHelp on Twitter), hence the links I posted. I ordered an unlocked Pixel 6 Pro, but if I had a T-Mobile version I would reach out to them on Twitter if the ADB command failed.
[Google Pixel 6 Pro] smartymcfly:
It would be for all of them. If you have an unlocked pixel, and use T-Mobile as your provider, then TMobile is the one you use. What it is referring to about TMobile is only the radio partition. The system stuff is all the same as the other version.

This carrier versions are not the updates that carriers send out to users, so if you are on T-Mobile with a pixel purchased from TMobile, any of these will not work that pixel.

Some months there will only be the ones without a carrier specific version. You would just use that version even if there was one with your carrier in previous months.
[Google Pixel 6 Pro] The MAZZTer:
It sounds like a few people have a fundamental misunderstanding of how Magisk works.

The APK is just the interface to configure Magisk with and install/uninstall it. Patching the boot.img and then flashing it is what actually installs magisk. So swapping out the APK does not change that you are still using 23011, which DOES NOT have SafetyNet features any more, nor MagiskHide. 23001 APK will show the old UI with these features, but as others have confirmed, these options don't function properly since you aren't actually running 23001 in boot.img.

Since 23001 can't patch the boot.img there's no way to get 23001 magisk installed on a P6.
[Google Pixel 6 Pro] PriMieon:
Does anyone know what I'm doing wrong? I've got a 256gb p6p, unlocked the bootloader, installed the latest magisk, downloaded the factory image file (compared build numbers. Phone and downloaded version are both SD1A.210817.015, i extracted the boot.img file, patched it through magisk (the new patched img file had 23011 in the name) flashed it with the following two adb commands:

fastboot flash boot_a X.img

fastboot flash boot_b X.img

Both are successful, press start on the fastboot screen and it reboots into fastboot mode saying enter reason: Boot failure

I know i patched the right image because flashing the unpatched image with the two above mentioned commands fixes my phone.
[Google Pixel 6 Pro] bosox284:
Did you do the flash vbmeta and disable verity/verification and steps?
[Google Pixel 6 Pro] PriMieon:
I only did what i wrote. How do i do all that other good stuff?

Where do i find the vbmeta? I am assuming it is in the factory build
[Google Pixel 6 Pro] bosox284:
Check out this thread:

https://xdaforums.com/t/firmware-is-out-get-your-root-on.4353565/
[Google Pixel 6 Pro] PriMieon:
With that i can get it to at least work until i reboot. I know the thread says it is temporary but to open Magisk manager and then to direct install Magisk make it permanent. But it does not stay permanent. If i understand it correctly you can bypass this whole thing and install it permanently but you have to wipe your data which I'm 125% okay with. I just don't know how that works either haha

I figured out the wipe method. I think it's working now. Thx so much ❤️
[Google Pixel 6 Pro] wera750:
Anyone tried to unlock a VZW variant by pulling the SIM card out on initial boot up to get to the unlock toggle in dev settings?