General March 29, 2023 QPR3 Beta 2 T3B2.230316.003 - Pixel 7 Pro [Cheetah] - [thread also for future Android QPR Betas]

[Lughnasadh]

https://www.reddit.com/r/android_beta/comments/ye15ik

Notice anything missing from this survey?

 

[roirraW "edor" ehT]

Notice anything missing from this survey?

View attachment 5744417

DOH! Thanks. I've removed it from the OP and will do so from my post too. Maybe they'll make a do-over.

 

[fmotta61]

Question, anyone have root on official ROM and take the beta OTA and use magisk update root inactive slot feature, like a regular OTA? I noticed the OTA is mentioned but can't find if someone did do it that way. Thank you in advance.

I did it.
Phone updated and root retained

 

[dd805bb]

I did it.
Phone updated and root retained

I can confirm too, I did the update and kept root.

 

[Samuel Holland]

To clarify, you're talking about installing one of the custom kernels, not the rooted stock one, correct?

Yes sir, thank you.

 

[roirraW "edor" ehT]

Yes sir, thank you.

I see, in that case, if I understand your original post correctly, to go back to Stable you could just dirty flash the .031 factory image zip, or use the Official Google Android Flash Tool.

• If using the Android Flash Tool to update/dirty flash, you should have the following items not selected:
  • Deselect Wipe
  • Deselect Force Flash all partitions (which will also wipe)
  • Deselect re-lock bootloader

 

[Samuel Holland]

I see, in that case, if I understand your original post correctly, to go back to Stable you could just dirty flash the .031 factory image zip, or use the Official Google Android Flash Tool.

• If using the Android Flash Tool to update/dirty flash, you should have the following items not selected:
  • Deselect Wipe
  • Deselect Force Flash all partitions (which will also wipe)
  • Deselect re-lock bootloader

Yes, I didn't try dirty flashing from beta to stable, because I seen on Google page; it said, to go back to stable from beta required a wipe.
What I forgot about or didn't realize after installing October stable image was Google play system update going back to the orig July update the phone came with, so when I tried installing krisakura kernel it said, couldn't install, play service out of date.
Then when I tried to go to update and let install, it couldn't finish because, I had verity & verification disabled, so I had to flash vbmeta, wait for the update to install(significant amount of min), then disable verity, verification, wipe, and finally could go with the custom kernel. I just wanted to mention in case someone was in the same boat, it could save them a little time. Thanks

 

[Lughnasadh]

I did it.
Phone updated and root retained

Just to be clear:

-You were on the October stable build and rooted (Canary or Stable Magisk?)?
-In Magisk, you selected "Uninstall Magisk>Restore Images"?
-You then went into system settings (System Update) and installed the QPR1 Beta 3 OTA?
-Then, before rebooting, you went back into Magisk and selected "Flash to inactive slot" and then rebooted?

After reboot you were on QPR1 Beta 3 and still rooted?

I'm asking because I didn't think Magisk was restoring the stock init_boot.img, therefore after selecting "Uninstall Magisk>Restore Images" you should still be rooted. And if you are still rooted the OTA usually fails.

 

[roirraW "edor" ehT]

Yes, I didn't try dirty flashing from beta to stable, because I seen on Google page; it said, to go back to stable from beta required a wipe.
What I forgot about or didn't realize after installing October stable image was Google play system update going back to the orig July update the phone came with, so when I tried installing krisakura kernel it said, couldn't install, play service out of date.
Then when I tried to go to update and let install, it couldn't finish because, I had verity & verification disabled, so I had to flash vbmeta, wait for the update to install(significant amount of min), then disable verity, verification, wipe, and finally could go with the custom kernel. I just wanted to mention in case someone was in the same boat, it could save them a little time. Thanks

Ah, I see now. Thanks.

 

[donjamal]

I installed the OTA as well, did not reboot but installed magisk with after OTA option. Root is retained. All seems to be good so far, previously mentioned clock FC is not there either without any update (maybe my version was already updated beforehand). Did not notice any extraordinary so far.

 

[roirraW "edor" ehT]

Survey has P7, and P7P now.

https://www.reddit.com/r/android_beta/comments/ye15ik

Android 13 QPR3 Beta software survey

Hi Beta users, We'd like your feedback on the latest Beta version of Android 13 on your Pixel device. This *anonymous* survey should take you about 5-10 minutes to complete. Please only fill out this survey if your Pixel device is running Android 13 QPR3 Beta build. You can verify this by...

docs.google.com

 

[jejemc]

hello personally I always have this data problem which pumps 6% of battery every two hours even off it and as long as it updates

 

[hubono]

Hi
So i tried updating using the settings...... Update system menu, then magisk flash other slot, reboot.
Once it goes into the reboot, it crashes. I get a red notice in fast boot saying my bootloader is corrupt. Then im asked to press the power button to continue booting.
I press the power button, the screen moves to the google logo and stays there.
I force a reboot, it then reboots into my old active slot which has the unupdated rom.
I proceeded to try again but this time without doing the magisk, just a straight update from the settings. It finishes and at end im presented with a reboot option. Once i click that, i get a notice saying that installation had some errors and it present me with the option to reset the update and start over.
It seems im unable to update using the settings menu in android.
Im bootloader unlocked, and rooted.

 

[Lughnasadh]

Hi
So i tried updating using the settings...... Update system menu, then magisk flash other slot, reboot.
Once it goes into the reboot, it crashes. I get a red notice in fast boot saying my bootloader is corrupt. Then im asked to press the power button to continue booting.
I press the power button, the screen moves to the google logo and stays there.
I force a reboot, it then reboots into my old active slot which has the unupdated rom.
I proceeded to try again but this time without doing the magisk, just a straight update from the settings. It finishes and at end im presented with a reboot option. Once i click that, i get a notice saying that installation had some errors and it present me with the option to reset the update and start over.
It seems im unable to update using the settings menu in android.
Im bootloader unlocked, and rooted.

You need to unroot and then take the OTA update for it to be successful. You can also update via flashing the factory image with fastboot, Android Flash Tool or Pixel Flasher. The OP in this thread is full of information.

 

[dd805bb]

Hi
So i tried updating using the settings...... Update system menu, then magisk flash other slot, reboot.
Once it goes into the reboot, it crashes. I get a red notice in fast boot saying my bootloader is corrupt. Then im asked to press the power button to continue booting.
I press the power button, the screen moves to the google logo and stays there.
I force a reboot, it then reboots into my old active slot which has the unupdated rom.
I proceeded to try again but this time without doing the magisk, just a straight update from the settings. It finishes and at end im presented with a reboot option. Once i click that, i get a notice saying that installation had some errors and it present me with the option to reset the update and start over.
It seems im unable to update using the settings menu in android.
Im bootloader unlocked, and rooted.

If you have done any custom kernel yes u have to fastboot the image. I have never been able to get an ota and custom kernel on 12-13.

You need to unroot and then take the OTA update for it to be successful. You can also update via flashing the factory image with fastboot, Android Flash Tool or Pixel Flasher. The OP in this thread is full of information.

I and another took the OTA just fine. With root. You don't need to do that unless you put a custom kernel in before. Header sizes don't work right. And a few other things get messed with using a custom kernel since 12. I took the OTA just fine. To each their own. But saying above has to happen isn't right. Something else is going on if you can't take the OTA.

 

[hubono]

No custom kernel
I used pixelflasher and updated hoping volte will work, doesn't seem like it

 

[dd805bb]

What carrier do you have because mine works fine? T-Mobile. That could be a carrier thing. I also turned off DSDS, FYI. Not carrier.

No custom kernel
I used pixelflasher and updated hoping volte will work, doesn't seem like it

 

[piotrkruczek]

You need to unroot and then take the OTA update for it to be successful. You can also update via flashing the factory image with fastboot, Android Flash Tool or Pixel Flasher. The OP in this thread is full of information.

Did exactly that and it worked.

1. Disabled all modules in magisk
2. Flashed stock boot.img and init_boot.img
3. Sideloaded beta ZIP (full, not just update).
4. Patched init_boot.img in Magisk
5. Re-enabled all modules

Works flawless.

BTW. All banking apps, Google Wallet, fingerprint, face unlock - works without redoing, clearing cache etc.

 

[Lughnasadh]

Did exactly that and it worked.

1. Disabled all modules in magisk
2. Flashed stock boot.img and init_boot.img
3. Sideloaded beta ZIP (full, not just update).
4. Patched init_boot.img in Magisk
5. Re-enabled all modules

Works flawless.

BTW. All banking apps, Google Wallet, fingerprint, face unlock - works without redoing, clearing cache etc.

Glad everything worked out . Just to be clear, if you decide to sideload the full OTA zip (as you did), you don't have to unroot (flash stock init_boot.img) first. It's when you take the OTA through the system update (settings or notification) that you have to unroot beforehand so you pass the pre-OTA block verifications. Of course after sideloading you'll still have to re-root.

Also, if you do unroot you only need to flash the stock init_boot.img. You don't have to worry about the boot.img.


Groovy

 

[piotrkruczek]

Glad everything worked out . Just to be clear, if you decide to sideload the full OTA zip (as you did), you don't have to unroot (flash stock init_boot.img) first. It's when you take the OTA through the system update (settings or notification) that you have to unroot beforehand so you pass the pre-OTA block verifications. Of course after sideloading you'll still have to re-root.

Also, if you do unroot you only need to flash the stock init_boot.img. You don't have to worry about the boot.img.


Groovy

Ooh i see! Got it.
In my case - unfortunately system update didn't work - It kept showing, that my software is up-to-date (even I'm enrolled in betas). So I picked the long variant