yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yep, I understand. I absolutely loath the idea of starting from scratch if I can help it too. Things are well, thank you, I hope you are too.

I take your word for it. Like I said, it's just confusing since that's when the second round of July Android 13 updates came out (instead of an August Android 12 update everyone thought we were getting), and Android 13 Stable didn't come out until two days ago.

I don't know what to tell you. 🤷‍♂️

For what it's worth, I have the option to disable automatic updates enabled too, but I was surprised before I updated to Android 13 manually that I had received an update notification (for one of the tiny second July OTAs - it was just over 1 MB) at least a few days before 13 came out.

But I know I've read from others where they randomly got update notifications despite that setting being enabled in Developer options.
[Google Pixel 6 Pro] roirraW "edor" ehT:
That's a great idea! Nice.
[Google Pixel 6 Pro] ness151:
My luck with Android and Rooting has been... strange.

Without derailing the topic, just so we're clear: It is strongly recommended to flash at LEAST the bootloader to both partitions because, if the phone does boot into slot B (on my device) as long as it's on the newer bootloader, it wont loop, correct? However, doing this DOES blow the efuse, right? (the last device I used that a knowingly blew an efuse on was not a $1k+ phone and so I'm a little more scared of doing it here)
[Google Pixel 6 Pro] pysklona:
Rip v4a with this update. Don't update if you use it regularly.
[Google Pixel 6 Pro] Galaxy Princess:
Thank you for your suggestion. I'll try it. 😊
[Google Pixel 6 Pro] zebulun69:
I have a rooted pixel 6 pro, and I have been updating my phone with full factory image using the adb/fastboot method (without losing root) by monthly basis. Maybe I missed it, but can I safely update my phone to Android 13 using the same method?
[Google Pixel 6 Pro] Spookymyo:
Is there not a comparable thing to EDL for tensor?

Or maybe a deep flash cable?

And barring that how much luck would I have sending it in for warranty repair? I've had it less than a month.
[Google Pixel 6 Pro] Lughnasadh:
No, not that I'm aware of.
[Google Pixel 6 Pro] Spookymyo:
Well then I guess I'll try warranty return for a software upgrade issue.
[Google Pixel 6 Pro] ipdev:
Both I and @pndwal have been called a lot of names. 🙃

I think this is the first time either of us have been accused of being a "Magisk Guru". 😜

Cheers all. :cowboy:
[Google Pixel 6 Pro] Strawhatfluffy:
Any of you guys on tmobile upgraded to android 13 and not getting a bunch of text messages? My wife who has a pixel 6 and me with the pixel 6 pro, after upgrading we were missing group messages and messages not from tmobile. Spent an hour talking to tmobile and they were useless. Decided to try swapping sim cards with another phone not on android 13 and all the text messages came thru. This was a bandaid fix if anybody else has this issue.
[Google Pixel 6 Pro] bush911:
My phone is currently like you said:

Slot a is android 12

Slot b is android 13

Is there any chance I can roll back to Android 12 by a full flash-all but skip the bootloader flashing.

Thank you in advance

I
[Google Pixel 6 Pro] bush911:
Could you please share more details on how to rever back to android 12?

-------

add: it works well. thank you very much
[Google Pixel 6 Pro] HipKat:
Dang, how’d I miss that? Lol
[Google Pixel 6 Pro] Namelesswonder:
fastboot --slot all flash bootloader android-13-bootloader.img

Optional fastboot --slot all flash radio android-13-radio.img

fastboot reboot bootloader

fastboot --force --slot all -w update android-12-image.zip

You will need the factory image for Android 13 to use the bootloader image and optionally the newer radio image.

This will wipe your phone.
[Google Pixel 6 Pro] roirraW "edor" ehT:
For the record, Android 12 boots just fine with the Android 13 bootloader, so yes, go ahead and flash the bootloader to both slots. I would go ahead and flash the full Android 13 update to both slots.

The "efuse" doesn't blow until the phone successfully boots into Android 13.

Yes. Just update both slots this time. I only did my initially active slot on Monday, and then Tuesday I switched slots and updated the other slot. You can do both slots at the same time. See the OP for instructions.

Sounds like possibly a SIM card issue. That sometimes happens, and you just might need a new SIM card.
[Google Pixel 6 Pro] zebulun69:
thank you. Successfully flashed both slots and running Android13 now. Rooted it and all the modules I used before still working.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Awesome, you're welcome!
[Google Pixel 6 Pro] Strawhatfluffy:
I thought it might be a sim card issue too when it was only my phone. The annoying part was I went to the T-Mobile store to do a sim swap, but couldn't because I wasn't getting text messages to confirm my account. When I came home and noticed my wife's phone was having the same issue, figured it wasn't a sim card issue.
[Google Pixel 6 Pro] roirraW "edor" ehT:
My bad, I misunderstood. For some reason, I thought it was only your wife's phone that was having the issue even though later in your post you said "we". My mistake!

Strange issue. I'll do some tests between my brother and/or sister and myself. I'm not on T-Mobile, but worth checking anyway. I almost exclusively use Google Voice when I'm not using Google Chat, so I don't do proper text messages often enough to notice.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Tests to and from both my brother and sister worked fine on my Android 13 Stable test. One using Android and Google Messages, and the other using iPhone and whatever they use. :D None of us on T-Mobile, two of us on AT&T, and the third on Verizon.
[Google Pixel 6 Pro] whatsisnametake2:
updating to 13 using factory image flash via fastboot as I always do, I'm unclear about this flashing the bootloader to both slots thing. why do I need to do that? if I flash the whole factory image with wipe to the default slot (i've never messed with or changed slots), why is there any risk in that? and my understanding is we now know we can definitely flash 12 back with the 13 bootloader using the force command. what am I missing?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Check out the information in the OP of this thread regarding not being able to downgrade from 13 to 12, so you should have the 13 bootloader, and indeed the whole Android 13 OS, on both slots.

Because if there is any problem, it's remotely possible you could brick your phone.

Yes, you can use Android 12 with the Android 13 bootloader. What you cannot and can never do reliably is use two different major versions of Android such as 12 on slot A, and 13 on slot B, because the apps and app data will be shared between them, and at least one, or eventually both will not work correctly because the app data has been "updated" for the newer version of Android.
[Google Pixel 6 Pro] gpvecchi:
Thanks, so with OTA even bootloader is flashed to both slots, right?
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're welcome!

Actual Over The Air update you receive and install automatically, or sideloading?

Actual Over The Air automatic update definitely flashes to both slots. The nature of how two slots works is the OTA updates the slot you're not using first, then when you reboot you're booting into the newly updated slot, and then the OTA applies to the slow you're no longer using.

I don't sideload so I have no idea if there's any difference in behavior. Plus some people haven't had success with sideloading the OTA and have to use another method (either full factory image and/or the

Official Google Android Flash Tool

.
[Google Pixel 6 Pro] V0latyle:
No. OTA is an "out of band" update - it's installed to the inactive slot, regardless of whether you use the automatic system OTA, or you sideload the update package.

The only way to ensure bootloader is flashed to both slots is to do it manually.
[Google Pixel 6 Pro] V0latyle:
Not sure this is the case...I don't believe the system does anything to the "old" slot until the next OTA.
[Google Pixel 6 Pro] roirraW "edor" ehT:
It was definitely the case with the Pixel 1 with the first a/b system. It did this so if for example, you're running slot A before the OTA, the OTA updates slot B while you're running slot A, then you reboot, it boots automatically into slot B, then it updates slot A while you're running slot B. This way, if slot B fails for some reason, it'll boot into slot A (which is already updated) with no issues...hopefully.
[Google Pixel 6 Pro] V0latyle:
I mean, I've been wrong before. The Android documents don't mention this but it makes sense to me.
[Google Pixel 6 Pro] Lughnasadh:
This is the case. The current slot is unaffected in case there is an error in updating the inactive slot or the inactive slot fails to boot. In such cases, the device will revert to the unaffected current slot. Only on the next OTA will the former current slot be updated.
[Google Pixel 6 Pro] Lughnasadh:
Interesting. I've never heard of that. Always thought the current slot was unaffected until the next OTA update.
[Google Pixel 6 Pro] V0latyle:
Easy way to test this...Someone who updated via OTA can boot into bootloader and use fastboot set_active other to switch to the other slot. However - I do not recommend doing this on the Android 13 update until the next OTA.
[Google Pixel 6 Pro] Lughnasadh:
"...no partition used by the current slot should be updated as part of the OTA update (including partitions for which there is only one copy)."

I don't see anything in the documentation about updating the former current slot after the device has booted into the new slot. Maybe need to dig deeper...

Eh, I never use OTA's anyway 🙃

A/B (seamless) system updates | Android Open Source Project

source.android.com
[Google Pixel 6 Pro] whatsisnametake2:
so, change active slot, flash 13 bootloader, change active slot back, flash entire factory 13 image. that should about do it right?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Who knows. I could be remembering wrong. I swear I thought that's what I read about it when I first got my Pixel, and I thought it made sense - once the initially updated Slot B boots successfully, Slot A gets updated to match. After all, I always thought Google wanted both slots to be on the same software as a backup to boot to just in case.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'd fully update both slots, not just the bootloader.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Maybe I'll test it on my unlocked Pixel 1. First I'll flash the full firmware to both slots, then take the OTA and after all success, make comparisons between each slot's Software in Settings. Yeah, I think I'll do that. I don't mind fooling with the old phone.

Edit: Triple posting, self! Shame on me! :)
[Google Pixel 6 Pro] V0latyle:
Yeah this would be a pretty safe idea. I still have my old Pixel 2 that I can try this on as well.
[Google Pixel 6 Pro] exocetdj:
rooted on 12l stock - the method i used to update to a13 was

1 - completely nuke magisk via the app

2 - the device initiated a reboot so as soon as the screen went black i held power and down for fastboot mode - i then connected the device to PC

3 - in "flash-all.bat" i changed "fastboot -w update image###.zip" to "fastboot update --skip-reboot image###.zip"

4 - closed "flash-all.bat" and then i launched it - when finished i was in fastbootd mode - i then rebooted device to fastboot mode

5 - in CMD i typed and enter "fastboot set_active other" and then relaunched "flash-all.bat" -

WIN!! as i was booted with all my data previously on A12 intact

6 - i then installed stable magisk 25.2 and patched boot image from A13 and then rebooted to fastboot mode

7 - i then opened CMD once more and typed and entered "fastboot boot magisk-patched.boot.img" which booted the device rooted - finally i directly installed magisk via the app
[Google Pixel 6 Pro] Namelesswonder:
I don't remember it being that way back then, because I remember the pain when LineageOS 14 was testing update_engine on the Pixel and I had to take up to modifying both vendor slots to have persistent modifications as each nightly update would be swapping system slots. Worked for the time as files on /vendor would supersede those on /system. Would need to be redone every time the monthly update was flashed, but ultimately had to stop doing it as LineageOS started including the vendor partition in the update payload as users would get vendor-system mismatch warnings because the vendor partition could be stale as update_engine doesn't update both slots at once. Users moving from stock Android to LineageOS would have the other slot be stale unless they --slot all the factory image at the time. Easily solved by LineageOS just bundling in the vendor partition with the update payload.

I could test if this is still true, but I'm still using my Pixel XL and have LineageOS 18.1 set up just the way I like. I did test on a Pixel 5, and update_engine still only updates one slot at a time.

[nameless@5900x:/tmp/redfin-sq3a.220705.003.a1]$ fastboot --slot all flash bootloader bootloader-redfin-r3-0.4-8351081.img 1>/dev/null 2>&1
[nameless@5900x:/tmp/redfin-sq3a.220705.003.a1]$ fastboot --slot all flash radio radio-redfin-g7250-00202-220422-b-8489468.img 1>/dev/null 2>&1
[nameless@5900x:/tmp/redfin-sq3a.220705.003.a1]$ fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.016s]
Finished. Total time: 0.066s
[nameless@5900x:/tmp/redfin-sq3a.220705.003.a1]$ fastboot getvar version-bootloader
version-bootloader: r3-0.4-8351081
Finished. Total time: 0.023s
[nameless@5900x:/tmp/redfin-sq3a.220705.003.a1]$ fastboot --slot all -w update image-redfin-sq3a.220705.003.a1.zip 1>/dev/null 2>&1
[nameless@5900x:/tmp/redfin-sq3a.220705.003.a1]$ fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.012s
[nameless@5900x:/tmp/redfin-sq3a.220705.003.a1]$ adb sideload ~/Downloads/redfin-ota-tp1a.220624.014-3301931b.zip 1>/dev/null 2>&1
[nameless@5900x:/tmp/redfin-sq3a.220705.003.a1]$ fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.012s
[nameless@5900x:/tmp/redfin-sq3a.220705.003.a1]$ fastboot getvar version-bootloader
version-bootloader: r3-0.5-8633620
Finished. Total time: 0.017s
[nameless@5900x:/tmp/redfin-sq3a.220705.003.a1]$ fastboot -aa
Setting current slot to 'a' OKAY [ 0.314s]
Finished. Total time: 0.324s
[nameless@5900x:/tmp/redfin-sq3a.220705.003.a1]$ fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.013s]
Finished. Total time: 0.063s
[nameless@5900x:/tmp/redfin-sq3a.220705.003.a1]$ fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.018s
[nameless@5900x:/tmp/redfin-sq3a.220705.003.a1]$ fastboot getvar version-bootloader
version-bootloader: r3-0.4-8351081
Finished. Total time: 0.016s

The Android 12 slot did become unbootable, but it's possible that the full OTA did that and the incremental OTA wouldn't.
[Google Pixel 6 Pro] Markelijk:
Hi, so I updated my P6P via OTA and rebooted succesully to A13. However I tried to change the slot from Slot B to A and restarted the phone. Now my screen is black and doesn't react to any button presses. Is there something I could do? Many many many thanks in advance!!
[Google Pixel 6 Pro] roirraW "edor" ehT:
Check out the suggestions in this thread:

https://xdaforums.com/t/android-13-bad-flash-cannot-start-the-phone.4481709/

It eventually got the user to Fastboot, and from there you should be able to use

Official Google Android Flash Tool

(OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
[Google Pixel 6 Pro] Markelijk:
Thanks. The only thing is that OP does actually see something on his screen, and I see nothing. Windows does make a 'device connected/disconneced' sound when I'm pressing the power button in combination with volume buttons.
[Google Pixel 6 Pro] Lughnasadh:
Oooh, sounds like you changed the slots and booted into the slot that still had A12 on it before flashing the A13 bootloader??? If so, you might be in trouble. Follow @roirraW "edor" ehT advice first.
[Google Pixel 6 Pro] Markelijk:
Yeah.. I think I did. Is there any hope for me? I feel so stupid by even tring to boot that way.
[Google Pixel 6 Pro] CRXed:
So you changed slots, but you didn't flash anything to that slot (as everyone is saying: also update the other slot!) and then you booted that slot?

I think you are in trouble to be fair.
[Google Pixel 6 Pro] roirraW "edor" ehT:
My bad, for some reason I thought they had a black screen too. There have been several (many?) others in this section in the exact same situation as you. The only thing I can think of is to hold the power and (I always forget which volume button) for over 30 seconds to try to force a reboot or off. Argh. I'm getting old. :) Thanks for your faith @Lughnasadh, but other than that vague suggestion of mine, I'm not sure what else to suggest.
[Google Pixel 6 Pro] Lughnasadh:
If that's what indeed happened, then your phone may be bricked by the new ARB. I've seen it (apparently) happen to a few people so far and did not see any resolutions to their situation.

Try warranty/RMA.
[Google Pixel 6 Pro] Namelesswonder:
The system partition being flashed to the other slot is system_other.img, and it is still in use today. However it's practically vestigial at this point as Google has made many improvements to the size of ART caches and to ART itself so it is only 23MB on the Pixel 6, and if it doesn't get flashed to the other system slot it doesn't matter because ART will just JIT if there isn't a cache. This is why you can --slot all as it was never necessary, just held some precompiled ART caches to speed up the first boot. This is why a --slot all update takes slightly longer to boot compared to a normal update can use them. This is also why you can't boot the other slot if you use fastboot, the Android system on the other slot was mangled.
[Google Pixel 6 Pro] Markelijk:
Thanks for your answer. I will follow this thread and I think I'll contact Google (bought it directly from them) for RMA if no one finds a solution..
[Google Pixel 6 Pro] Lughnasadh:
Hey, if I remember correctly I'm around a decade older than you...so THANK YOU for having faith in ME 🤣😅😂
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'm old enough to forget what everyone's ages or age difference (or age direction) is, including my own. Don't make me do addition and subtraction! 😂

So you have a better memory than me! Every time I have to remember something new, I have to shove something old out of my brain first.
[Google Pixel 6 Pro] Nergal di Cuthah:
I think this was already answered , but i couldn't find the answer, and i also am the old. If i used google's flasher (default settings) were both slots flashed or am i in danger from this evil brick. If danger do i just follow the psa instructions ?
[Google Pixel 6 Pro] roirraW "edor" ehT:
I *believe* the Android Flash tool flashes both slots. If there is any doubt at all, you can adb reboot bootloader, then fastboot --slot all flash bootloader bootloader-raven-slider-1.2-8739948.img (or change the name of the bootloader file to the one for your device if not Pixel 6 Pro), then you *should* be much safer than without doing that first.
[Google Pixel 6 Pro] Nergal di Cuthah:
uh oh

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

img is in root platform tools folder
[Google Pixel 6 Pro] Namelesswonder:
I just tested on a Pixel 5, it does not.

So as far as any method of updating your phone, the only one that updates both slots is to manually use fastboot to flash both slots.
[Google Pixel 6 Pro] Namelesswonder:
What fastboot version are you using? fastboot --version

And is bootloader-raven-slider-1.2-8739948.img in the directory with the fastboot binary? If not you can just put the path to it if you've extracted it elsewhere.
[Google Pixel 6 Pro] Lughnasadh:
Out of curiosity, did you select "Force flash all partitions"?

EDIT: By the way, I believe the Pixel Flasher does flash to both slots.
[Google Pixel 6 Pro] Nergal di Cuthah:
D:\android\platform-tools>fastboot --version
fastboot version 33.0.2-8557947
Installed as D:\android\platform-tools\fastboot.exe

Yes in same folder as exe
[Google Pixel 6 Pro] Namelesswonder:
Yes.

Android 12 bootloader still on the other slot.

[nameless@5900x:~]$ fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.013s
[nameless@5900x:~]$ fastboot getvar version-bootloader
version-bootloader: r3-0.4-8351081
Finished. Total time: 0.016s
[nameless@5900x:~]$ fastboot -aa
Setting current slot to 'a' OKAY [ 0.313s]
Finished. Total time: 0.325s
[nameless@5900x:~]$ fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.013s]
Finished. Total time: 0.063s
[nameless@5900x:~]$ fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.033s
[nameless@5900x:~]$ fastboot getvar version-bootloader
version-bootloader: r3-0.5-8633620
Finished. Total time: 0.020s
[Google Pixel 6 Pro] Lughnasadh:
Thanks for the response. Don't know if you saw my edit, but I believe the Pixel Flasher flashes to both slots.
[Google Pixel 6 Pro] Namelesswonder:
I can't test, PixelFlasher on Linux keeps on segfaulting when I try to browse for a firmware image and if I manually give it the path then it segfaults when I click ok to start the fastboot script.

Edit: After reading the source PixelFlasher does have the option to flash both slots, however it is behind the advanced mode toggle, so it won't be shown to the average person. I still can't test if it is functional and flashes properly, or if it might do it incorrectly and try booting the other slot.
[Google Pixel 6 Pro] Lughnasadh:
Yeah, it supposedly adds --slot all to the fastboot command.
[Google Pixel 6 Pro] Namelesswonder:
That it does, so it is safe and works.

PixelFlasher/modules.py at main · badabing2005/PixelFlasher

Pixel™ phone flashing GUI utility with features. Contribute to badabing2005/PixelFlasher development by creating an account on GitHub.

github.com
[Google Pixel 6 Pro] Jmoney55:
If you flash the 13 update (full image not oat) using googles chrome flasher which is just one click wait and done, do I need to worry about the partition issue. does google chrome flasher automatically flash the right partitions when using a full image and not an oat?

thanks
[Google Pixel 6 Pro] Nergal di Cuthah:
The going belief, outlined about one page ago, is that google's tool does both. To be assured it did i tried the psa instructions but got a failure (see above). So I'm in a holding pattern on whether they are or are not.

Sorry for the quotes @Nameless and @lug i couldn't renove them
[Google Pixel 6 Pro] V0latyle:
Syntax is wrong, it thinks you're trying to flash a partition named "--slot all"

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

AFAIK the Android Flash Tool DOES NOT flash both slots unless you check "Force flash all partitions" which requires a wipe

Hard to tell because there's no log output
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thank you!

Thank you for both of those!