yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] i42o:
I've been reading these threads non-stop since Android 13 dropped. I am sure that me as well as many other people are wondering what is the correct way to go about upgrading into Android 13, while maintaining a fully functioning fully development oriented device that can keep being a fully unlocked Google pixel device, that can be modded FULLY as was intended by purchasing a bootloader unlockable device.

I personally believe that something a little bit more definitive would give clarity to many of us users of the pixels 6 series. Anti-rollback can mitigate security vulnerabilities but that comes at the cost of our device freedom. I and many others are still on Android 12, and would love to know what's the best way to go about this.

Thanks In advance, have a great day.
[Google Pixel 6 Pro] roirraW "edor" ehT:
This will work (also in OP) or you can modify it to flash both slots at the same time - I just haven't had time to update the post/OP yet. Look back over the last two pages for the way to modify the fastboot flash commands to flash to both slots at the same time.

Effectively, update the normal full factory image way. Then change slots and update the normal way again.
[Google Pixel 6 Pro] V0latyle:
The only thing specific about the Android 13 update is that you should ensure you flash the bootloader to both slots...and the Patch Inactive Slot function in Magisk seems to be hit and miss.

Other than that, everything is the same, and does not limit what we can do with our devices. We've already established that older versions of Android will run on the new bootloader without a problem.
[Google Pixel 6 Pro] HipKat:
I haven’t read back in the thread yet but has anybody just gotten this as a pushed out update? For something that was released Monday, I haven’t gotten it yet. And I would sideload it but I have not done that with this device and not really paid attention to sideloading but reading the stuff makes it seem like it’s a pain in the ass
[Google Pixel 6 Pro] roirraW "edor" ehT:
I don't think I've heard of anyone actually getting the OTA (on the Pixel 6 Pro), and I believe I've seen several other users asking about it - the same as you. My wife's never rooted or even bootloader unlocked Pixel 6 Pro still doesn't see an update available when she manually checks.

Maybe Google is being more cautious? Let the more adventurous report back for a while?
[Google Pixel 6 Pro] HipKat:
Yeah, that’s fine plan. I’m not as much in a hurry as some people are to have the newest thing as soon as it comes out. The sideloading is something I was always on top of in the past but this double slut thing, I’ve never heard of before and frankly I don’t understand it. Like I said though, not being rude and I really don’t follow these types of threads very closely, until I get the P7P and get back into doing that
[Google Pixel 6 Pro] Lughnasadh:
Did you try just flashing the patched image to 1 slot instead of both at the same time?
[Google Pixel 6 Pro] Lughnasadh:
Apparently tulsadiver's mods (not sure all of them), and I believe the Pixel Tweaks mod (could be another mod) by eg1122, can't be updated to work with A13. They're experience bootloop problems with decompiling and compiling APKs (maybe other things as well), I believe. So there have been some changes to A13 that may affect some modding.
[Google Pixel 6 Pro] Homeboy76:
That was my first thought and I was going to do it. Untill I looked as the magisk_install..log, saw all the errors and became apprehensive. o_O
[Google Pixel 6 Pro] Lughnasadh:
I would try, just to eliminate that aspect of it. Also re-extract the boot image from the factory image (in case it was corrupted for some reason), re-copy it to your phone and repatch the image. Understandable if you're apprehensive though.
[Google Pixel 6 Pro] Lughnasadh:
For those who are wondering if we should or should not be worried, or how worried we should or should not be, here's a response from the Graphene dev who first tweeted about his colleague bricking his device due to the new ARB, for what it's worth...

So yes, at the minimum flash the A13 bootloader to both slots. May even want to flash all of A13 to both slots since we still are not certain what the outcome would be if the device reverted to a slot with the A13 bootloader and A12 everything else, since to my knowledge no one has tested that yet (being on A13 and flashing back to A12 with the A13 bootloader).

https://twitter.com/i/web/status/1559942170466975745
[Google Pixel 6 Pro] Homeboy76:
- re-extract the boot image from the factory image (in case it was corrupted for some reason)

* Did it

- re-copy it to your phone and

* Did it

- repatch the image

* Did it

- view magisk_install...log

* The same errors are present

- checked Apprehension level

* o_Oo_O
[Google Pixel 6 Pro] jcp2:
Best typo this year ;)
[Google Pixel 6 Pro] roirraW "edor" ehT:
I still say

Official Google Android Flash Tool

. :)
[Google Pixel 6 Pro] Namelesswonder:
It might be Magisk Canary is failing? I don't know if anyone has tested 25201 on the Android 13 release, but if Lycidias has a thread with prepatched Android 13 boot using Magisk 25200 then you should probably look to see if that works.
[Google Pixel 6 Pro] Lughnasadh:
What happened though? Bootloop?Just not rooted?
[Google Pixel 6 Pro] Lughnasadh:
Yeah, I'm on Canary 25201 on A13. Everything is fine. The latest Canary (25201) and Stable (25.2/25200) builds are actually the same as of present.
[Google Pixel 6 Pro] Lughnasadh:
Follow up, again, for what it's worth...

https://twitter.com/i/web/status/1559961288956051457
[Google Pixel 6 Pro] Ghisy:
I updated from the 2nd July update to 13 by using the usual factory image thing (minus the -w and keeping verity and verification disabled). I just made sure to flash the new bootloader to both slots beforehand, just in case.

Root works (Magisk 25.2 stable), AOSP mods work, face unlock works (the modded one using the Motorola apk) and Kirisakura fashed fine too. Everything seems OK so far!
[Google Pixel 6 Pro] roirraW "edor" ehT:
@Ghisy said:

There is nothing inherently wrong with flashing the bootloader to both slots. Now flash the rest of Android 13. Never mind, you already did, but did you flash Android 13 to both slots or just one? I personally did it one slot at a time but both ways should work fine.

@scloutkst Ghisy's next step is to flash the full Android 13, yes. Android 12 works just fine with the Android 13 bootloader - I tested that myself. I didn't downgrade, I flashed the Android 13 bootloader (to one slot) before upgrading fully to 13, and tested booting and unlocking the phone on Android 12 while on the 13 bootloader.
[Google Pixel 6 Pro] Ghisy:
Do you mind sharing the actual steps? If I already booted up to 13, am I screwed?
[Google Pixel 6 Pro] roirraW "edor" ehT:
The same steps you use to update any month that you update. In this case, if you only flashed the full Android 13 to one slot, change slots and flash-all (without -w again) Android 13, and then re-root the new slot with the Magisk's boot.img you already made.

On the Fastboot screen, change to the opposite slot with either:

fastboot --set-active=a

(If you're on slot b)

or

fastboot --set-active=b

(If you're on slot a)

Not at all. Just update the other slot as normal.
[Google Pixel 6 Pro] Ghisy:
Thanks, I'll try that.

Do I also need to flash the Kirisakura kernel again once I'm booted up? Because the system will boot to the newer flashed slot, right? (thanks Google for making something simple much more complicated...)
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yes. After booting up the first time with an unrooted boot.img, then flash the rooted stock boot.img, then once booted up with the rooted stock boot.img, flash the custom kernel.

You're welcome.
[Google Pixel 6 Pro] Homeboy76:
I think you may want to use

fastboot --set-active=other

it lowers the mistake threshold.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Finally updated the OP with:

How to flash both slots using the full factory image BOTH SLOTS at the same time

It's either/or, you can do one slot at a time or both slots. There's nothing wrong with either way. You *may* be safer at least flashing the bootloader to both slots at the same time, at least. I did one slot at a time with no problems. The first slot Monday, then the second slot Tuesday.
[Google Pixel 6 Pro] roirraW "edor" ehT:
There is always more for me to add to the OP! LOL! Thanks!
[Google Pixel 6 Pro] Spookymyo:
Need a little assistance.

I updgraded to Android 13 from rooted 12. I rooted 13 with no issues. Check root status and it was good. Started testing magisk modules and eveything was looking good. But it wouldn't retain root after a restart. So I thought I needed to disable AVB and DM verity. So I executed the standard command "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img". Then re flashed the magisk patched img. When the phone restarted I got a message saying the software was corrupt. It gave me either try again or factory reset. I clicked try again and was going to do a button combo to get back into the bootloader to reOTA to a clean boot image.

Problem is that now the phone will not power on. None of the buttons even work. No matter what button combo I try the phone will not power back on. It was fully charged. I tried seeing if the computer would recognize it by adb/fastboot devices and it wasn't recognized.

Have I truly hard bricked my phone?
[Google Pixel 6 Pro] Ghisy:
Worked like a charm! Thanks dude!

I actually used the command roirraW edor ehT posted without any problem. But yeah, I agree you need to make SURE which slot you're currently on.
[Google Pixel 6 Pro] roirraW "edor" ehT:
When you disable Verity and Verification, you need to wipe the phone. The only time you don't is when you keep them disabled each and every time you flash.

They shouldn't have anything to do with the cause of the original issue on your phone, however. I believe that might've been the problem I was having about 6-7 months ago and not even flashing the full factory image (with wipe!) to start fresh would help. The only thing that helped me was

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

Try holding the power and volume up or volume down button for a very long time (over 30 seconds). I always forget which volume button it is. See @Lughnasadh's answer below.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Great! You're welcome!
[Google Pixel 6 Pro] V0latyle:
My two pence...Between the Flash Tool and Pixel Flasher, I'd recommend the latter for those looking to update via the factory image. The only thing the Flash Tool can do that Pixel Flasher can't is force flash all partitions. However, Pixel Flasher can't patch a boot image without root.
[Google Pixel 6 Pro] Namelesswonder:
Can also drop the slot changing entirely when flashing the system image as fastboot --slot all update image.zip works fine on modern Pixels. Magisk step still holds.
[Google Pixel 6 Pro] Ghisy:
Unrelated to updating to 13, has anyone been able to use the new predictive back animations thing? I enabled it in the developer options but it doesn't seem to work?
[Google Pixel 6 Pro] Lughnasadh:
Try holding the power and volume down button for a long time, like at least a minute or 2. Hopefully during all this your phone did revert to the other slot which I assume still has A12 on it? Also, what happens when you connect phone to computer?
[Google Pixel 6 Pro] Lughnasadh:
It's dependent on apps supporting it and very few at this time do.
[Google Pixel 6 Pro] stalls:
Did you forget to direct install magisk? I would reflash with android flash tool and start all over without wipe if you want to save your data.
[Google Pixel 6 Pro] Ghisy:
Oh I see. Bummer... It looked interesting!
[Google Pixel 6 Pro] Namelesswonder:
Updated the steps in my post to make it a lot clearer, 2 steps if you're already on Android 13, 4 steps if you are still on Android 12, and 4.5 steps if using Magisk.
[Google Pixel 6 Pro] Spookymyo:
When I connect to my laptop (windows 11 pro insider) it makes a connection sound. The only place I see the phone is in the Devices and Printers section of control panel. Thing is, it shows as USB Root Hub (3.0). When I unplug the phone that disappears. I'm confused.

Edit: I held the buttons down over 2 minutes. I did just the power button, power + vol up, power + vol down, and power + vol up & down. I did it while attached to the computer too. After about a minute the computer made the disconnect reconnect sound on all the combos. But the screen never came on.

Edit 2: Could EDL mode work? If so what's the best tool for it?
[Google Pixel 6 Pro] cbomb1337:
Google's online flash tool works perfect for going to A12 to a13. I think it best to select wipes to.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thanks much, updated.
[Google Pixel 6 Pro] Lughnasadh:
Well, that's a good sign that at least your computer recognizes it. Still won't power on? Or display just won't come on? Did you hold those buttons down for a long time? What happens if you plug it into a charger?

Maybe if your computer recognizes it, Android Flash Tool will as well.
[Google Pixel 6 Pro] fyoory:
Anyone had a problem with patched magisk not adding zygisk? I used factory patching, ala unzip and run flash-all and also pixel flasher. Whatever reasons magisk 25201 doesnt seem to add zygisk for me so I cant do safetynet etc.
[Google Pixel 6 Pro] sas46:
I'm willing to flash from the latest SQ3A.220705.001.B2, Jul 2022, EMEA to A13 TP1A.220624.021, Aug 2022

Can I do it or I have to wait the EMEA version?

Also I'm rooted, the best way is still to patch the boot image, boot it and then directly flash it from magisk?
[Google Pixel 6 Pro] Spookymyo:
It recognizes it like I've seen mentioned in EDL articles. It doesn't recognize it as a phone. I've tried the flash tool and it doesn't work. I was just checking EDL instructions and looks like it only works on Qualcomm devices. The P6P is tensor, so I don't know if it'll be possible.
[Google Pixel 6 Pro] Lughnasadh:
Yeah, you won't be able to use the Qualcomm EDL on Tensor. I'm still curious if you tried to hold the power and volume down buttons for a long time. You haven't mentioned if you tried that yet or not.

Also, do you have these drivers installed? If not, wondering if it will make a difference in how your computer sees your phone.
[Google Pixel 6 Pro] roirraW "edor" ehT:
No problems here. Magisk (Stable v25.2, which is the same as Canary 25201) and SafetyNet working great. You've got Zygisk enabled in Magisk's settings?

Yes, you can do it. There's no knowledge or evidence that there will be split versions for different areas of carriers with this release. That doesn't mean it won't happen, but you can always change to a different build later if one appears. The "Global" one which is out works for everyone.

"Best" is subjective, so up to personal preference. If you're asking if it works with Android 13 Stable's kernel (boot.img), yes it does.
[Google Pixel 6 Pro] sas46:
You answers are crystal clear, I'll let you know if this goes alright then :ROFLMAO:
[Google Pixel 6 Pro] fyoory:
Thanks for the update. Tho i wonder if the factory reset is part of the problem. Forgot to edit the flash-all bat prior. bleh
[Google Pixel 6 Pro] roirraW "edor" ehT:
Awesome! Good luck.

You're welcome. I doubt it - a factory reset shouldn't cause that issue.

Did you see my question about if you have Zygisk enabled in Magisk's settings?
[Google Pixel 6 Pro] Bunnehbunn:
Since I'm reading stuff about this, a note when I first updated to Android 13, when the other slot still had Android 12 the phone REFUSED to stay on the Android 12 slot after "fastboot reboot-bootloader".

To describe it better, slot A was 12, slot B was 13, I was unable to reflash 12 bootloader on slot A even though slot A still had the 12 bootloader. Only after flashing 13 bootloader on slot A could I switch the slot to A and B freely.

A big part of experimentation before flashing 13 to both slots was to see if having the phone on 12 allowed the bootloader to be downgraded, short answer no. So if 13 bootloader is on 1 slot it needs to be on both or else the 12 slot will be unusable.

Fyi when I said 12 I meant Android 12L July and 13, Android 13 August

Edit: fixed grammar and errors when accidentally hit post

My main reason for posting this is maybe it could explain why some people are having bootloops.
[Google Pixel 6 Pro] fyoory:
You are the man! I totally forgot to check that one thing. The last update didnt load your complete update and I overlooked the last sentence.
[Google Pixel 6 Pro] roirraW "edor" ehT:
That's strange. Monday I manually flashed the full factory image of Android 13 Stable using flash-all.bat with the "-w" removed, and then Tuesday I switched slots (to the slot that still had Android 12) and did the flash-all.bat yet again.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Awesome. It's nice when it's a simple fix.
[Google Pixel 6 Pro] Bunnehbunn:
That's true, it will switch the slot when you type "fastboot --slot a" but if you were to do "fastboot reboot-bootloader" without flashing the 13 bootloader it would have switched back to slot b.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Okay, thanks. Now I understand.
[Google Pixel 6 Pro] Bunnehbunn:
I typed the other post before finishing it or double checking it so yolo. Or maybe I should say (you only post once), I tried to fix a few stuff but I'm not going to rewrite the whole thing now haha... Sorry for the confusion
[Google Pixel 6 Pro] roirraW "edor" ehT:
No sweat! :)
[Google Pixel 6 Pro] sas46:
Just updated smooth, no issues at all and safetynet pass!

View attachment 5688683
[Google Pixel 6 Pro] mko000:
Pixel Flasher has an option to "Flash on both slots". Isn't that what you mean/what is needed?

Never mind, I mixed up partitions and slots.
[Google Pixel 6 Pro] stalls:
I just flashed over to 13 with android flash tool and it was really smooth. Now that flashes both slots right?
[Google Pixel 6 Pro] roirraW "edor" ehT:
No. The Android Flash Tool site has an option to force flash all partitions (this also wipes your phone because your internal storage is a partition). That's unrelated to the two separate slots.

I believe so, that's my impression.
[Google Pixel 6 Pro] mko000:
Ah my bad, I mixed up partitions and slots. Thanks for clearing that up for me!
[Google Pixel 6 Pro] Spookymyo:
I've tried the flash tool. It won't recognize the phone.
[Google Pixel 6 Pro] Spookymyo:
I did mention how long I held the buttons down in post #1219. I held all the different combos for over 2 minutes. When I had the cable plugged in the computer did the disconnect reconnect sound but never recognized it as a phone.
[Google Pixel 6 Pro] Lughnasadh:
Yeah, I didn't go back to see you edited it. Running out of ideas.
[Google Pixel 6 Pro] Galaxy Princess:
I'm so embarrassed to post this, but I have to ask because I feel like I'm missing something... @roirraW "edor" ehT If you happen to read this, you might remember; I have a boring Verizon Pixel 6 Pro with the locked bootloader, so my first question is: is the OTA on the developers.google.com site also for my Verizon locked phone?

If so, I'm completely stumped as to why I can't sideload this OTA zip file with ADB. I tried two different new Windows 10 computers, four different new cables that all say they're data cables right on them, the latest drivers installed on the computer, etc.

So when I begin to side load, it begins verifying the zip file, but stops at around ~3 or ~4 and then... Nothing... absolutely nothing. No matter how long I wait or what I do. I've downloaded the OTA three separate times, I've checked to make sure the sha256 hash matches what's on the downloads page and all three of them did. So I'm hoping that someone with stronger brain cells than I, can tell me what I'm doing wrong and why this isn't installing for me. Thank you all so much!
[Google Pixel 6 Pro] Homeboy76:
I crossed my fingers, Knocked on wood, rubbed my lucky rabbits foot and fired up my computer

- Booted the bootloader

- Connected the computer and phone

- Opened a command prompt

- fastboot flash boot magisk_patched...img

- Pressed the enter key

- Took a deep breath, wiped the sweat from my forehead and pressed the pwr button on my phone.

- After, a few seconds had passed, I noticed there was no smoke coming from it, I looked at the screen.

- It had booted up and was rooted. :) :) :)

- I put the Flash Tool on hold untill the next crisis.

To all the XDA members and Staff that helped

get my problem resolved. (y)(y)(y)

Thank you!
[Google Pixel 6 Pro] ness151:
I actually have the OTA update (I hadn't installed it since people were saying on the forum that it "wasn't released" which confused me, since I've been sitting on it this entire time.) I wasn't sure to mention it because I have been waiting DAYS for the file to be released. It's been nagging me for 3 weeks so far (I got the prompt on like the 3rd of Aug) for this OTA.

After reading some of these posts though.. I'm not sure if I should update to 13 or not.
[Google Pixel 6 Pro] Lughnasadh:
There ya go!!! 😁
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hi, I think lots of people have been having trouble sideloading 13, so it's not just you. I really don't fool with sideloading, use the full factory image so I don't have the experience to attempt to help.

I would expect the same OTA to work for you normally, so I'm guessing it's just the general trouble a lot, although not necessarily all, people are having sideloading the OTA, from all the posts I've read since 13 came out Monday.

You may just want to hang in there and wait for an actual over the air update, or more news or yet another update from Google.

Sorry I don't have better advice.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'm confused. Android 13 Stable didn't come out until August 15th. The OTA from the beginning of the month was the second July update that no one was expecting.

I'm not saying you don't have the 13 OTA ready and waiting for you to install, I just don't understand how you would've received it two weeks ago.
[Google Pixel 6 Pro] Galaxy Princess:
Absolutely, that's fine. I can wait for it. I'd rather not do the full image because I really like the way I've got my apps right now, and it's a real pain in the you know what to load them all back. Maybe one day when I get a wild hair, I'll just do it for the heck of it. But you're right; I'm not in a rush for it, but I am very curious about it. But it's nothing that can't wait until Google gets around to us. Thanks so much RW! Hope all is well!
[Google Pixel 6 Pro] ness151:
I know i've had it since at least the 3rd because (I have the option to disable automatic updates enabled) and every other day I have a popup (that uses kind of strong language) that I should update, but I postpone it.

I know it was the 3rd because I made a twitter post about it (nobody replied :( )

If it helps, mine is the USCellular variant.

I'm terrified of messing this up. I've read all the relevant threads, I know how to use pixelflasher, and yet I still don't trust myself to NOT brick my device.
[Google Pixel 6 Pro] Lughnasadh:
What has worked for a lot of people who haven't gotten the OTA update yet is to join the A13 Beta program. You should then receive an OTA update to Stable A13. Once installed, unenroll from the Beta program.
[Google Pixel 6 Pro] Lughnasadh:
Has to be one of those A12 OTA's. One is 2.02 GB in size and because of the size people are mistaken it for the A13 OTA.

Here's more about it...

cc: @ness151

Some Pixel phones need another Android 12 update before Android 13, Google explains [U]

Some Google Pixel owners are seeing an Android 12 update in place of an Android 13 update, and there's no word on an official fix yet.

9to5google.com