yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] foobar66:
After having upgraded to A13 (retaining root and data), I flashed the bootloader to both slots (--slot=all).

Then, using fastboot, changed the active slot (from B to A) and 'updated' (full update) the 'other' (nonactive) slot (A) as well.

All went fine.

Then I changed the active slot back to B.

Then I rebooted ... Google logo appeared ... few seconds later phone rebooted into bootloader (without any warning).

Reboot again ... same ... Google logo appears and a few seconds later reboot to bootloader.

Sigh ... I was slightly in panic ;-)

Then re-updated the (original) B slot again with A13.

After that upgrade to B (which already contained a working A13) all was fine.

Really weird, I don't think I did anything wrong or in the wrong order, so I don't understand why it did not want to boot into a previously working slot (B).

Anyway ... now all is fine again.
[Google Pixel 6 Pro] Lughnasadh:
Yeah, that's normal when doing it like that. Think you need to actually boot into the new slot first.
[Google Pixel 6 Pro] foobar66:
Oh ... OK ... I was not aware of that ... learned something new today ;-) ... thanks.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Don't feel bad, I only just learned this yesterday as well. :)
[Google Pixel 6 Pro] V0latyle:
I'm not sure what's behind this...I wonder if it's something to do with update_engine or something else expecting to see an "updated" slot after forcing a slot change.
[Google Pixel 6 Pro] V0latyle:
Humor my brotha. We good. I was just trying to explain myself better, it's just the way my brain works, I didn't think you didn't understand.

And my last comment was just an attempt at being funny by being redundant
[Google Pixel 6 Pro] Yoru2647:
Hey! i have a problem, im trying to install/update my phone to android 13 but i keep getting this message (you will see it in the image)! it may be beacuse i left my bootloader unlocked but idk what to do! Beacuse i cant update i thonk my phone is slow! now im trying to update with files from browser!
[Google Pixel 6 Pro] V0latyle:
Please refer to the Guide linked at the top of the OP.
[Google Pixel 6 Pro] card13:
@V0latyle If you don't reboot after changing slots then it doesn't finish the swap. Noticed this on the OP6T (first A/B Scheme phone I had to support). Not sure if that was your situation since you didn't mention a reboot after slot switches.
[Google Pixel 6 Pro] whatsisnametake2:
I have only ever updated my phone via fastboot with factory images, to the default slot a. is there actually anything in slot b in that scenario?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yes, the originally version of Android (first version of 12) that came with the phone.
[Google Pixel 6 Pro] whatsisnametake2:
ok cheers.

so my current understanding, using factory image:

use the flash-all.bat

boot into 13 once

go back to fastboot and flash 13 bootloader to both slots

does the command to flash the bootloader to both slots mess with the setting of the current active slot in any way?
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're welcome.

Personally, I would flash-all one slot, then switch slots and flash-all the new slot, but that's fine too.

No.
[Google Pixel 6 Pro] card13:
@whatsisnametake2 I took the path you were mentioning, this Thread wasn't out when I did it. I haven't seen any ill effects on using the flash-all Script to get to A13 then flashing just the Bootloader to both slots.
[Google Pixel 6 Pro] whatsisnametake2:
ok cheers for the info
[Google Pixel 6 Pro] V0latyle:
@roirraW "edor" ehT did someone already test running Android 13 on the 12 bootloader?
[Google Pixel 6 Pro] roirraW "edor" ehT:
I can't remember for certain. I'm thinking that maybe someone - either in your thread or my thread, did report testing that, but it's only a vague notion that it might have been reported. :) So much has been talked about regarding Android 13 in the past week+!

Edit: Well, actually, maybe not. I think this by @Bunnehbunn is what I'm thinking of.
[Google Pixel 6 Pro] Namelesswonder:
Only confirmation we have so far is this person that ran Android 13 on the April Android 12 bootloader, no other person has tested on a newer bootloader or at all.

https://xdaforums.com/t/has-anyone-...ootloader-i-have-tried.4481347/#post-87312899
[Google Pixel 6 Pro] whatsisnametake2:
if the last 13 beta didn't have ARB, how about using that bootloader with 13 main release?
[Google Pixel 6 Pro] roirraW "edor" ehT:
I know the idea has been mentioned either in this thread or one of the other threads where we talk about Android 13, but I have no idea if anyone has already tested the idea. Even if the 13 Beta 1, 2, 3, 4, or 4.1 bootloaders did work with Android 13 Stable, there's no guarantee that future updates of Android 13 will continue to work on the old bootloader.
[Google Pixel 6 Pro] whatsisnametake2:
understood. is it definitely confirmed that none of the betas had ARB? personally I'm not willing to commit to no going back with a13 until I know all my critical apps are compatible.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I don't know the answer to that. I also didn't participate in the Betas in any way at all other than sharing links for each new Beta version.

I haven't had any issues with any of my apps, but everyone's usage is different. Technically speaking, I can say that for a day or two after I flashed Android 13 Stable, the root/Xposed-based AOSP Mods only partially worked with Android 13, but it's since been updated to fully support all the features on Android 13 that I cared about, and then some.
[Google Pixel 6 Pro] Lughnasadh:
People on the A13 betas were allowed to unenroll from the beta program and downgrade to A12 (with a wipe) so it would make sense that none of the beta bootloaders had the ARB implemented.

Plus I've seen people on another, not to be named, platform, downgrade from the A13 betas to A12.
[Google Pixel 6 Pro] whatsisnametake2:
so it seems pretty certain then that the betas are ARB free. before going to main release that's definitely what i'll do first. are the links to the last 13 beta still available?
[Google Pixel 6 Pro] roirraW "edor" ehT:
In my thread. I haven't checked if the links still work, but it wouldn't surprise me if they do.
[Google Pixel 6 Pro] Lughnasadh:
Looks like the Beta links have been removed.
[Google Pixel 6 Pro] roirraW "edor" ehT:
The download links in my thread still work. I've consolidated them here for convenience. I've put an extra copy of the links at the top of post 2 in my Android 13 Beta thread, also:

Spoiler content hidden.
[Google Pixel 6 Pro] Lughnasadh:
Nice. I just went to their Beta page and noticed it was gone. Good thing you have those 👍
[Google Pixel 6 Pro] whatsisnametake2:
cheers dude. much appreciated.
[Google Pixel 6 Pro] mcwups1:
Do I reboot after doing this, or just continue to update like normal after, without rebooting?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Since the flash-all.bat reboots after updating the bootloader:

I would say, yes, reboot, but only if you're skipping the regular flash-all.bat and manually doing the rest of the steps. There's no harm to just:

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

(with the "-w" removed from the flash-all.bat, as always) since the flash-all.bat will reboot after once again updating the current slot's bootloader. Again, no harm.

Alternatively, you could modify the flash-all.bat's flash bootloader line to:

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

in which case, the flash-all.bat will reboot after, anyway, because it's already in the script to reboot after.

I hope this helps.
[Google Pixel 6 Pro] mcwups1:
A

Absolutely. Just wanted to be 100% sure. Thank you.
[Google Pixel 6 Pro] V0latyle:
If you're updating to 13 for the first time, you will need to reboot to bootloader after updating for the change to take effect. It's kind of like the boot image - changes to the partition don't take effect until the next time it's loaded.
[Google Pixel 6 Pro] whatsisnametake2:
am I correct in thinking that there is minimal difference between beta 4.1 and main release of a13?
[Google Pixel 6 Pro] 96carboard:
The piece you are missing is that the ARB counter is incremented by the system, not the bootloader. The bootloader just goes into brick mode if the ARB counter is too high.
[Google Pixel 6 Pro] whatsisnametake2:
so what you're saying is that flashing the system partition of A13 main release and booting into it is what causes the ARB trigger? and not the bootloader itself? do we have confirmation of this?
[Google Pixel 6 Pro] roirraW "edor" ehT:
I've seen it said several times that the bit doesn't flip until Android 13 Stable successfully boots the first time. As long as the bootloader supports ARB, then once you boot into Android 13 Stable successfully, the bit is flipped.

So two things in total are required:

A bootloader that supports ARB - we don't know if the 13 Stable bootloader is the only bootloader that supports ARB. We've had reason to suspect that the 12 Stable bootloader supports ARB for some months, but not sure. No idea about if the 13 Betas 1 through 4.1 bootloaders support it.

Booting into Android 13 Stable at least once successfully.
[Google Pixel 6 Pro] 96carboard:
I wonder if there are any bootloaders that don't implement ARB? If so, it might be possible to downgrade to one of those.
[Google Pixel 6 Pro] Lughnasadh:
From the GrapheneOS dev whose colleague 1st bricked their device because of the ARB and having A12 on 1 slot instead of A13 on both slots...

Btw @roirraW "edor" ehT , that's you Lugo is talking about 😁

https://twitter.com/i/web/status/1559381635799425025
[Google Pixel 6 Pro] whatsisnametake2:
cheers fellas all good information. still looks like flashing beta 4.1 is my best option at the moment for avoidiung ARB.
[Google Pixel 6 Pro] V0latyle:
The ability to blow the ARB counter has always existed in Android on Pixels...they've just never had a good reason to do it before.
[Google Pixel 6 Pro] 96carboard:
No.

All you need to do is make sure that the new bootloader is written to BOTH SLOTS before you do ANYTHING ELSE.

fastboot flash bootloader --slot=all bootloader-raven-slider-1.2-8739948.img
[Google Pixel 6 Pro] whatsisnametake2:
yes, and then there's no going back to 12 if i want to. hence beta 4.1 being my best option to test drive 13 and check it works for my use cases.
[Google Pixel 6 Pro] 96carboard:
Of course you can go back to 12. Just don't write the old bootloader back if you do so.
[Google Pixel 6 Pro] V0latyle:
You CAN go back to Android 12, it just doesn't run properly.

@roirraW "edor" ehT I noticed that Developer Options has a section for WebView implementations. Maybe that would be the ticket to being able to run stable 12?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Interesting! Where are our trusted experimenters when you need them? :)

Definitely curious, though.
[Google Pixel 6 Pro] whatsisnametake2:
yes that's the point. currently 12 on 13 bootloader is known to be unstable. so in practice no go.
[Google Pixel 6 Pro] whatsisnametake2:
yes would be great to have a solution for it.
[Google Pixel 6 Pro] card13:
Was about to test wiping my phone and running A12, however got a red warning from SwiftBackup that they can no longer backup Google Authenticator. When I went to Export my codes it wanted me to scan the QR Codes (which might be a problem, will have to pull devices out of retirement temporarily). Does anyone have a good way to back up Google Authenticator now?
[Google Pixel 6 Pro] V0latyle:
Completely off topic for this thread, please post your question in a relevant thread.
[Google Pixel 6 Pro] stoph8n24:
Hello, unsure if this is the right place to ask but my phone downloaded the Android 13 update, but it is asking to restart to install. Is there anywhere in the phone (rooted) that I can delete the downloaded update? My last ditch effort is to do a wipe and reinstall July update.
[Google Pixel 6 Pro] roirraW "edor" ehT:
It's never been clear to me on any of my Pixel devices if there was somewhere that an already downloaded update could be deleted from. I used to do that kind of thing on LG devices, but that was years ago and it was very well known where the OTAs were kept when downloaded. I don't think you can do the same thing on Pixels.

Be very careful what you do to try to avoid it because some users ended up with a black screen that required sending back to Google to repair.

If you wipe and reinstall the July update, it'll just attempt to install the 13 OTA yet again, even with automatic updates turned off in Developer options. There have been at least 2-3 users who had rooted their phone and had automatic updates turned off, but they still received the OTA to 13 Stable, and it successfully updated, although, of course, they didn't have root again until they manually re-rooted it.

Good luck!

Edit: FYI, in case you haven't seen the posts about this, although you can technically upgrade to Android 13, then re-flash everything but the bootloader to Android 12 (because 13 blocks from downgrading the bootloader because of a known bad exploit in the old bootloader), Android 12 will boot, but it will noticeably not work correctly once you start using various apps.

Edit 2: If it starts the actual Android 13 installation process, don't bother trying to get around it or stop it, or you'll likely end up with a truly hard-bricked phone.
[Google Pixel 6 Pro] Lughnasadh:
FYI: Even though Android Flash Tool does not flash the whole image to both slots, they have added an option to flash the A13 bootloader to the inactive slot. This may be the easiest option when updating to A13 from A12.

Just to be clear, when updating to A13 from A12 a prompt will show up asking whether you want to also flash the bootloader to the inactive slot as well. It doesn't show up in the regular tick boxes.
[Google Pixel 6 Pro] mcwups1:
Just getting this done this weekend. Just wanted to make sure, after your suggestion, that this is okay to just run? Updating without wipe, so -w is gone, and the bootloader will update both slots like this, if I edited correctly, right?

Thanks again.

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

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot flash radio radio-raven-g5123b-102852-220720-b-8851166.img

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot update image-raven-tp1a.220624.021.zip
[Google Pixel 6 Pro] V0latyle:
Yep.
[Google Pixel 6 Pro] MadMan29729:
seems to me that google just wants to enforce the new DRM crap since its mainly what doesn't work if you install android 12 after updating!
[Google Pixel 6 Pro] Zaxx32:
Damn...I should of had added something to where I'd be able to tell if they had to crack it open to fix this 'eFuse = blown' issue from the ARB getting tripped. I assume it'd call for a reset of the ARB counter itself. OH WAIT! My 6a was/is waiting for the prepaid RMA return box. Hmm...I'm thinking the age old candle wax seal and making a note of the serial # I should have same where. So if the box gets here monday, it'll go back tues. prolly. Any other/better ways to know it was opened, lemme know cuz wax isn't very durable...just a piece of clear tape across an edge is better. Do doubt we'll learn mote over time, but it's a start! I also wanna know more about this alleged vulnerability/exploit crap.
[Google Pixel 6 Pro] Zaxx32:
Wow...just seen this... https://xdaforums.com/t/mod-xposed-...t-for-downgrading-apps-on-android-13.4485153/

Tested I wonder?
[Google Pixel 6 Pro] bush911:
Any chance to disable this DRM service, which makes Chrome and audio playing almost not workable on Pixel 6 with Android 12 on A13 bootloader
[Google Pixel 6 Pro] .:Crack:.:
Hi guys!

I think I have bricked my P6P. Stupidly, I hadn't read this thread before.

I was on A12 (locked bootloader), updated to A13 via OTA (through the OS). I was not happy with the battery life and decided to flash Kirisakura kernel 4.1.

So I unlocked my bootloader via fastboot. I started up the phone, set it up and everything was working fine. I then rooted the device according to this link. The phone started fine and I gained root access in Magisk. Then, I flashed the custom kernel via EXKM, which seemed to have worked fine. After rebooting, I was stuck in a bootloop and eventually the phone just stayed black and does not react to anything at all. Is this now completely bricked, or can I save it somehow?
[Google Pixel 6 Pro] shoey63:
100% hard brick unfortunately
[Google Pixel 6 Pro] roirraW "edor" ehT:
Unfortunately with the screen completely black, if your computer doesn't recognize it with ADB and Fastboot (and it probably won't), it's likely you'll have to send the phone to Google for repair.

Good luck! Sorry to give you the bad news.
[Google Pixel 6 Pro] krak3n77:
Would blocking google's OTA servers via hosts work?
[Google Pixel 6 Pro] roirraW "edor" ehT:
No idea. I've never attempted to block OTAs on either of the Pixel phones (1 and 6) I've owned.

The user I was replying to: their phone already downloaded the Android 13 OTA - so blocking a server after the OTA is already downloaded, wouldn't help.
[Google Pixel 6 Pro] Dave Lister:
The new "Developer Support" images are A12 on the A13 bootloader. https://xdaforums.com/t/guide-pixel...ate-root-pass-safetynet.4356231/post-87361855
[Google Pixel 6 Pro] lasha117:
updated on 13, phone lags, heats, battery is dead, need to charge phone twise a day... factory reset didnt helped
[Google Pixel 6 Pro] roirraW "edor" ehT:
It's probably one or more particular apps you use. No problems here. I haven't factory reset my phone since last December or so.
[Google Pixel 6 Pro] lasha117:
nope, i use same apps i was using on android 12
[Google Pixel 6 Pro] roirraW "edor" ehT:
The same was the case for several other users. The problem was with a few particular apps that likely need updated by the author of those apps in order to better support use on Android 13. A Samsung Health app was one example that would cause issues on 13 but not on 12.

This is one of the reasons Developer Previews and Betas exist - to give app authors a chance to test their apps on a new version of Android. Sometimes they don't test enough, or at all, or it's just not high priority for them until they implement the new Android version on their own (non-Pixel) devices.
[Google Pixel 6 Pro] TheDevil2vrzr:
I like that, but if I flash to 13 from downloaded by Verizon, can I some how install a bypass app or progge that will make it root during the install? Please be advised.
[Google Pixel 6 Pro] roirraW "edor" ehT:
If you have a Verizon variant of any phone, there is no possibility of rooting the phone since you can't unlock the bootloader.
[Google Pixel 6 Pro] AlDollaz:
Thanks for this post, new P6P will be here Tuesday and will most likely have 12 on it. Great to know before upgrading it to 13. ❤️
[Google Pixel 6 Pro] RetroTech07:
The new P7 comes out next month. I would have waited until then as the device might have better performance improvements over the P6P. If it doesn't I'm almost tempted to switch back to Apple temporarily until Google can make a phone that doesn't overheat from light usage and has a battery that lasts a reasonable amount of time.
[Google Pixel 6 Pro] AlDollaz:
I hear you, but my current phone (OP8) is busted and I didn't want to wait + on sale.
[Google Pixel 6 Pro] samteeee:
Hi everyone;

I wanna stay on 12 but my P6P has downloaded the 13 stable already!

Can I go the "Developer Support Images" route using the official Android flash tool

and be reasonably safe until the 13 stable gets fixed?! If that makes sense.

Any suggestions is much appreciated.
[Google Pixel 6 Pro] Lughnasadh:
You should be fine with that since those builds (Developer Support Images) don't receive OTA security updates, which presumably would include not receiving a A13 OTA update.
[Google Pixel 6 Pro] samteeee:
Thanks a lot.
[Google Pixel 6 Pro] samteeee:
Hi everyone ;

Would the A13 Bootloader work with A12 and boot it up to OS?!

Thank you.
[Google Pixel 6 Pro] V0latyle:
This has been answered in the OP.
[Google Pixel 6 Pro] cultofluna:
Developer support Android 12 images working properly on A13 bootloader
[Google Pixel 6 Pro] acidspider:
anyone know if the flash tool has been updated to flash teh bootloader to both slots yet?
[Google Pixel 6 Pro] Lughnasadh:
It has, at least when you are updating from A12 to A13. It will ask you if you want to flash the bootloader to the inactive slot as well.

Not sure if you get that prompt if already on A13 and just updating to a new monthly build. Someone who has used Android Flash Tool to update from Aug. A13 to Sept. A13 will be able to tell you.
[Google Pixel 6 Pro] Twiggy000b:
Quick question! I got my replacement 6 pro today and upgrade to 13 via ota, now like the og post says gotta sideload both. buuuuut. can i unlock bootloader and install "raven-tp1a.220905.004" via fastboot and not have it get hard bricked again xD
[Google Pixel 6 Pro] V0latyle:
Why would it? If you sideloaded to both slots, then both slots have the new bootloader, so you aren't at risk of a brick.

I'm not sure I understand your question.
[Google Pixel 6 Pro] Twiggy000b:
i just wanted to be clear before i do anything else to my replacement phone and then boom black screen again xD
[Google Pixel 6 Pro] V0latyle:
Nope, should be fine. If you installed the OTA twice, the new bootloader should be flashed to both slots.

If you aren't sure, read back through this thread (or the Pixel 6/6a ones) to find the commands that will tell you the bootloader versions.
[Google Pixel 6 Pro] Twiggy000b:
im only on the augusta patch. not september. my dumbass flashed barbet on my old pixel 6 pro -.-
[Google Pixel 6 Pro] roirraW "edor" ehT:
All you have to do to be safe is:

adb reboot bootloader
fastboot flash bootloader --slot all bootloader.img

using the bootloader image from the inner zip in the latest Android 13 Stable (September) full factory image. Then Flash-All.bat (after removing "-w" unless you don't mind wiping) and you'll be golden.
[Google Pixel 6 Pro] samteeee:
Hi guys;

I finally decided to take the on device A13 OTA and after the successful boot to OS,

I let it sit and do its things for a while and finally rebooted to Recovery and sideloaded

the September OTA zip and happy to report that my P6P booted to OS successfully!

I wanna thank all the good people here at XDA forum for reporting & sharing this problem

and its solution so that people like me can keep their devices intact for a bit longer.
[Google Pixel 6 Pro] domhall012N8:
New to the P6P... Haven't touched it "yet" beyond taking the Aug A13 Update... Does the Sept A13 Update, which will flash to the now inactive-A12 partition, not contain the A13 bootloader?

Or should I still sideload the Aug A13 Update to the inactive-A12 partition, then take the Sept A13 update?
[Google Pixel 6 Pro] V0latyle:
The September update will have AT LEAST the August bootloader, if not a newer version.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Every month's update has a bootloader. Whether it's changed or not, or to what degree it has changed can vary. You don't need to flash the September bootloader to both slots if you are, for example, currently on the August Android 13 release right now, and you take the September OTA, which will provide you with an Android 13 Stable bootloader in each slot - albeit the August one in one slot, and the September one in the other slot. This is normal and perfectly acceptable, and there is no danger.

I wouldn't bother. Just take the September OTA, and that'll get you what you need - an Android 13 bootloader on both slots. For that matter if you want a "just in case", you don't have to flash the August bootloader. Download the September factory image and do:

adb reboot bootloader
fastboot flash bootloader --slot all bootloader-devicename-slider-1.2-3456789.img

Using the filename of the bootloader.img file that's within the inner zip that's in the factory image zip.
[Google Pixel 6 Pro] samteeee:
I apologize not making it clearer as I have a "locked bootloader"by choice, hence the only method to prevent a Bricked Pixel was to sideload a full OTA image, but as mentioned by @roirraW "edor" ehT, you can just flash the September bootloader to both slots and be safe!

Good Luck