Question 13 beta 3 - anyone tried it yet? - Google Pixel 6

How to download Android 13 for Google Pixel and other Android devices
Google has officially kicked off the Android 13 QPR2 rollout via the beta channel. You can download the release right now and give it a try!
www.xda-developers.com
Android 13 reaches Platform Stability milestone with Beta 3 release
Google today released the third beta build of Android 13. With Android 13 Beta 3, the new release had finally hit the Platform Stability milestone.
www.xda-developers.com
I am on 13 beta 2.1 but every time I upgrade my device gets wiped or corrupted.
I am rooted with no Magisk modules.
A simple upgrade process that will not require a wipe (and stay rooted if possible) will be appreciated. Thanks.

---

I'm waiting till someone's tires the ota method with new magisk before I update

---

I took 13 off on beta 1 because Verizon voicemail was lost. Can anyone confirm that voicemail does.qotk from Verizon now?

---

bturkel said:
I took 13 off on beta 1 because Verizon voicemail was lost. Can anyone confirm that voicemail does.qotk from Verizon now?
Click to expand...
Click to collapse
I was having issues with voicemail too but on TMobile. Latest beta fixed it for me. So far this update seems really solid

---

Inthonk when it comes to wipe you need to untick w to then not wipe not sure though just from what I read from others so take what I say woth pinch of salt

---

Im on beta 3.
So far im considering return to 12 stable , i dont have fast charge anymore.
It took 20 min to charge from 50 to 60%

---

I'm running it (unrooted) with no issues. Much another than 12/12L.

---

For me root does not work..
While flashing update , the phone does not enter fastbootd when I used from magisk (v25) patched boot.img
(using Pixelflasher or flashing with manual commands)
So I flashed without patched boot.img and flashing worked with loosing root.
Booting patched boot.img with fastboot does work... I get root and Magisk.
But: I cannot patch the boot.img of the device directly... I can do so, but it will never boot again...
(else I boot from fastboot again patched boot.img)
So I cannot get my Pixel 6 pro to boot with patched boot image...

---

All running fine for me.
Rooted straight away - I patched the boot.img with Magisk 25001 before dirty flashing the factory image (removed the -w flag on the flash.bat), then flashed the patched img
Had no issues whatsoever.

---

krs360 said:
All running fine for me.
Rooted straight away - I patched the boot.img with Magisk 25001 before dirty flashing the factory image (removed the -w flag on the flash.bat), then flashed the patched img
Had no issues whatsoever.
Click to expand...
Click to collapse
Tried also this way....
That´s what happens:
Spoiler
c:\Pixel 6 flash\raven>flash-all
< waiting for any device >
Sending 'bootloader_b' (13386 KB) OKAY [ 0.303s]
Writing 'bootloader_b' (bootloader) Flashing pack version slider-1.2-8552708
(bootloader) flashing platform gs101
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_b
(bootloader) Validating partition pbl_b
(bootloader) Validating partition bl2_b
(bootloader) Validating partition abl_b
(bootloader) Validating partition bl31_b
(bootloader) Validating partition tzsw_b
(bootloader) Validating partition gsa_b
(bootloader) Validating partition ldfw_b
(bootloader) Flashing partition ufs
(bootloader) Flashing partition ufs
(bootloader) Flashing partition partition:0
(bootloader) Flashing partition partition:1
(bootloader) Flashing partition partition:2
(bootloader) Flashing partition partition:3
(bootloader) Flashing partition bl1_b
(bootloader) Flashing partition pbl_b
(bootloader) Flashing partition bl2_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition bl31_b
(bootloader) Flashing partition tzsw_b
(bootloader) Flashing partition gsa_b
(bootloader) Flashing partition ldfw_b
(bootloader) Loading sideload ufsfwupdate
OKAY [ 3.362s]
Finished. Total time: 3.678s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
< waiting for any device >
Sending 'radio_b' (82740 KB) OKAY [ 1.870s]
Writing 'radio_b' (bootloader) Flashing pack version g5123b-101858-220505-M-8545669
(bootloader) Flashing partition modem_b
OKAY [ 0.109s]
Finished. Total time: 1.991s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
< waiting for any device >
--------------------------------------------
Bootloader Version...: slider-1.2-8552708
Baseband Version.....: g5123b-101858-220505-B-8545669
Serial Number........: 1C211FDEE003Y7
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.001s]
Setting current slot to 'b' OKAY [ 0.080s]
extracting boot.img (64 MB) to disk... took 0.191s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 1.482s]
Writing 'boot_b' OKAY [ 0.078s]
extracting dtbo.img (16 MB) to disk... took 0.028s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.375s]
Writing 'dtbo_b' OKAY [ 0.022s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.003s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.024s]
Writing 'pvmfw_b' OKAY [ 0.003s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.001s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.003s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_b' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.210s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 1.493s]
Writing 'vendor_boot_b' OKAY [ 0.076s]
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
So it reboots and reboots and reboots, but does not get into fastbootd
If i use volume down button I will only get into normal fastboot and so it exits installation:
Code:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Press any key to exit..

---

Found a solution for me....
I did as above...
flash bootloader and reboot to fastboot
flash radio and reboot to fastboot
And then before flashing the zip file I tried to enter fastbootd with: fastboot reboot fastboot
Then I was in fastbootd
Now I started the: fastboot update ..... (with the patched boot.img)
And it started to flash and does not try to enter fastbootd during the flash, because I am already there...
Mike

---

I'm on 13b3 rooted and it's working just fine, even better than 13 i find it faster with some extra features that I've find good

---

On latest beta not rooted, and visual voicemail is working for me, overall stability seems better and so far everything seems like the best this phone has been since launch.

---

Have they added the ability to connect to multiple bluetooth devices simultaneously yet?

---

J0nhy said:
I'm on 13b3 rooted and it's working just fine, even better than 13 i find it faster with some extra features that I've find good
Click to expand...
Click to collapse
How did you get yours running? Mine just sits at the "pixel is starting" indefinitely.

---

I'm a bit confused. Does 13 have other features than 12, or the same features plus more? Shouldn't 13 be a fork off 11 when 12 isn't even finished yet?

---

RobbyRobbb said:
I'm a bit confused. Does 13 have other features than 12, or the same features plus more? Shouldn't 13 be a fork off 11 when 12 isn't even finished yet?
Click to expand...
Click to collapse
12 was finished and released in October last year, 12.1 (with new features and fixes for big screen devices) released with march feature drop and 13 gonna release this summer/fall with new animations in various places, bug fixes and smaller tweaks etc.

---

I'll be sticking with 13 beta until it goes stable. FPR is much better and phone seems much smoother and faster.

---

I downgraded from 13 beta 3 because i thought i lost fast charge ( downgraded and it went on fastboot bootloop, had to flash ota through adb).
Now my phone seems slower , when taking a photo , the camera moves like in slow mo.
Beta 3 still have issues ( like when in landscape mode , to turn wifi on/off i had to scroll the notificaton panel down twice to be able to press the button) but android 12 is way more buggy

---

mitchst2 said:
I'll be sticking with 13 beta until it goes stable. FPR is much better and phone seems much smoother and faster.
Click to expand...
Click to collapse
I couldn't agree more. The only things I've noticed of course is what everyone's complaining about. Viper won't install. The Xbox app lags out really bad. Haven't noticed any other major problems.
But holy **** is it smoother and faster - with roughly equal battery life.