How To Guide April 2, 2024 AP1A.240405.002 Global - Root Pixel 6 Pro [Raven]
- Thread starter roirraW "edor" ehT
- Start date
You have got to be kidding me...
T-Mobile config regressed!
<boolean name="vonr_enabled_bool" value="false" />
NSA and fallback to LTE isn't working. Wtf.
T-Mobile config regressed!
<boolean name="vonr_enabled_bool" value="false" />
NSA and fallback to LTE isn't working. Wtf.
Last edited:
General_Mayhem
Senior Member
Noice.
Quick dumb question: Is upgrading from 12 to 13 the same OTA flash method as the monthlies? I assume it is but..
Yes. However I wasn't able to update via automatic OTA on my Pixel 5.
General_Mayhem
Senior Member
Yeah I updated to the last 12 build and then tried seeing if it would OTA to 13 but wouldn't so I just re-rooted. I already pulled the 13 zips but wanted a definitive answer before I tried that. Will likely do it sometime tomorrow.
Yes it is the same way, just pick the Android 13 image for your Pixel 6 model. Then click flash and follow the instructions
No, in the product or data partition, I think.
I had to wipe my phone and follow my own VoNR guide to get a functioning connectivity again.
At least I always do a backup right before so it's no sweat.
I had to wipe my phone and follow my own VoNR guide to get a functioning connectivity again.
At least I always do a backup right before so it's no sweat.
Let's just hope that ARB is only tied to downgrading to the A12 bootloader and not other parts of the OS as well.
Google's statement wasn't exactly clearcut in my mind. I think a bad result could potentially lead to a more than undesirable outcome, if you know what I mean. Of course, I could just be overly paranoid
So when factory installing through flash-all, the default installation of A13 is to one slot and not both?Let's just hope that ARB is only tied to downgrading to the A12 bootloader and not other parts of the OS as well.
Google's statement wasn't exactly clearcut in my mind. I think a bad result could potentially lead to a more than undesirable outcome, if you know what I mean. Of course, I could just be overly paranoid
Correct, according to this Dev...
Quick question, do you know if JamesDSP automatically switches audio profiles when you connect to different audio devices like V4a does? Currently using V4A and contemplating trying out JamesDSP just so I can update to Android 13 lol
So what is the correct way to install it to BOTH slots, before booting into the system?
After flashing to your active slot, just change slots and flash again.
Unrelated device, but with A/B slots:
You can see which slot you were already active on after
adb reboot bootloader (on the Fastboot screen) three items from the very bottom it will say:or
The change slot command reflects immediately on that screen.
I just did all this.
Last edited:
This is correct. I actually did this when updating to A13 stable so I would have A13 on both slots in case things got funky. Confirmed
Cool. I might try to remember to do this for every update from now on, just 'cause.This is correct. I actually did this when updating to A13 stable so I would have A13 on both slots in case things got funky. Confirmed
I'm sorry. I don't want to screw it up.
Do I use the official android flash tool? Is there an option there to reboot into inactive slot or do I need to use fastboot/adb to update to A13.
I only used adb to update monthly. Thanks.
Top Liked Posts
-
There are no posts matching your filters.
-
32Platform-Tools is updated to 35.0.1:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for...
developer.android.com
22
I did go through and successfully flashed my PX6 pro to AP1A.240405.002 with KSU using PixelFlasher 6.8.3.0 -
66Pixel 6 Pro [Raven]
April 2, 2024:
Android Security Bulletins | Android Open Source Project
source.android.com
Here there be dragons.
I am not responsible for anything at all. 
Check warranty status - *may* reveal if a phone is refurbished, only if the phone was refurbished through Google - thanks to @Alekos for making me aware of the site.
Official Google Pixel Update and Software Repair(reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro yet)
Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen
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)
ADB/Fastboot, Windows Drivers, and unlocking the bootloader (thanks @sidhaarthm for confirming unlocking the bootloader works as intended, be sure to thank him in his post)
Rooting-related
No longer applies -Things that make rooting more complicated on Android 12
A list of the other important guides - be sure to thank the respective OPs
For all relevant guide threads just click the yellow "How To Guide" quick filter above the list of threads in the Pixel 6 Pro section.
- Here's the Magisk section of XDA's forums, for rooting. Magisk on GitHub. The most recent Magisk Stable is what's recommended these days.
- @sean222's thread Restore WiFi and Cellular Data in Quick Settings (Root Required)
- @rickysidhu_'s thread HBM (High Brightness Mode)
- @gururoop's thread Probable method to upgrade every month, without wiping data and retaining root
- @rickysidhu_'s thread Limit Charge
- @Typhus_' thread [MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Pro Thread
- @siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+ - a mod that compliments @Typhus_' mod above, and may eventually completely replace it.
- @TotallyAnxious' thread [MOD] Collection of "Anxious" Modules for Pixel 6/Pro Series
- Every single one of @foobar66's posts.
TWRP (not made for the Pixel 6 Pro yet - will update when it has)
Custom kernels for stock ROM(s)
Factory Images (requires an unlocked bootloader)
Full OTA Images (doesn't require an unlocked bootloader)
The usefulness of having Verity and Verification enabled (now that it's not needed for root) - post #2 below.
Regarding P6P 5G model numbers and capabilities - post #3 below.
List of all Pixel monthly security bulletins and Play System Updates - post #4 below.
How I root and update (which is identical whether rooting the first time or updating):
16The unlock process works like this;
1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on.
2) When it starts harassing you to join google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
3) Settings --> About --> Build number. Tap it until it says you're a developer.
4) Back --> Network --> Wifi and connect it.
5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize when requested.
6) # adb reboot-bootloader
7) # fastboot flashing unlock
Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.16
Used a factory image and booted into Android 13. Auto OTA and a sideload of the full OTA will end in the same result as both useupdate_engine. I did boot into Android 13 so the ARB counter did get incremented.
Downgraded by just forcing Android 12 system image with a wipe, switched slots, and did it again. It might be able to be done with a full OTA, but I didn't test it because of the following issue:
Android 12 doesn't work properly on the Android 13 bootloader.
It boots up just fine, appears to work just fine, made and received calls and texts, however the issue @bush911 had with WebView crashing is true. It's more than just WebView, the media DRM APEX immediately crashes. WebView crashes sometime after launch when it tries to find out if ClearPlay or WideVine are functional, and DRM Info crashes immediately when I try to launch it. Without DRM working that means you won't be able to play some music or movies and won't be able to use Netflix or any other streaming app.
There might be more systems or modules nonfunctional, but without working browsers your smartphone isn't going to be more useful than a dumbphone.
@roirraW "edor" ehT
So I guess it's time to retract that you can revert to Android 12, because until a modder comes along to cook up a custom Android 12 ROM with Android 13 APEXs or patched ones it won't work.1513Just to let everyone know, updating to .037 and re-rooting (without wiping anything) worked with no problems. My method is to just replace -w with --disable-verity --disable-verification in the flash-all.bat file and run the flash-all command. I then let it reboot, patch the boot image, return to bootloader and flash the patched boot image.
Canary 23014
EDIT: Thank you @ipdev for confirming my inquiry that this method would work back on Nov. 4
