How To Guide September 18, 2023 TQ3A.230901.001 Global | .C1 T-Mobile | .C2 Verizon - Root Pixel 6 Pro [Raven]
- Thread starter roirraW "edor" ehT
- Start date
No update yet, but at least:
source.android.com
Edit: And looks like two different security patch levels, unless a typo:
Android Security Bulletin—June 2023 | Android Open Source Project
source.android.com
Edit: And looks like two different security patch levels, unless a typo:
What was the final decision on platform tools should we install latest? You changed the thread title for the "new bug" in platform-tools but i can't find the post text about it and whether we should stick with old reliable march version (also what command do i use to get platform tools version)
Yeah, that's normal. 01 contains Android Framework patches and 05 contains vendor and kernel patches.No update yet, but at least:
Android Security Bulletin—June 2023 | Android Open Source Project
Edit: And looks like two different security patch levels, unless a typo:
View attachment 5926403
I still use 33.0.3. There are links at the top of the OP to it.
Edit: You can use 34.0.3 - it's just that you may have to jump through some minimal hoops for it to work completely for you. They're not huge hoops, but it's just simpler to stick with 33.0.3.
Hands-free photos, SpO2 and more for the Pixel family
The June Feature Drop for Pixel phone, Pixel Watch and Fitbit is here.
There seems to be a new "feature" of having wallet show on lockscreen. For anyone who has a card in theirs but don't pay with it. Setting is default on and is in lockscreen settings to remove it. Not sure if that's the june feature release or an update to wallet, but i personally don't want my card available for the public (rhough it does look like you need a fingerprint to do anything but see the last 4 digits, but still)
T-Mobile June Factory Image:
No July Stable firmware yet, but this is updated:
source.android.com
Pixel Update Bulletin—July 2023 | Android Open Source Project
source.android.com
July 2023 Stable firmware:
Edit 3: NOW, the July page at this link is present:
source.android.com
Edit 3: NOW, the July page at this link is present:
Android Security Bulletins | Android Open Source Project
source.android.com
Last edited:
NOW, the July page at this link is present:
After this update, using any Gboard version other than the one that came with the phone (uninstall updates) will result in no search results in the app drawer search bar.
Did 2 factory resets.
Did 2 factory resets.
Is this problem still happening?
I'm not on the 6 Pro - I'm on the 7 Pro, and I use Nova Launcher Prime normally, but I just launched the Pixel Launcher, since I opt to have an app icon for it, and I was able to search the Pixel Launcher's app drawer fine with Gboard version 13.0.07.528826899-release-arm64-v8a, from June 7, and there are no Stable Gboard updates available.
Are you opted into Gboard's Beta program, by any chance?
I'm on July Global Stable, but as I said, on the 7 Pro, so I don't know if there could be a 6 Pro-specific issue.
I've opted out of the beta, tried multiple gboard apks but none works other than base version. Any other keyboard from the playstore also works.
I was Googling to find anyone else who might have the same issue, and I found your Reddit post about it.
I also found information about a similar issue from last year. About the only real applicable advice I see suggested there is:If you haven't already. Actually, I see you can do so directly from GBoard's settings, as well - click the 3-dot menu and you can choose "Help & feedback" from there, then "Send feedback" at the bottom of the next screen.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
6
13.0.0 (TQ3A.230901.001, Sep 2023) Flash Link 5917d34f251c8094b0db034127220a9244acf13559f16e929f83288de4545453 13.0.0 (TQ3A.230901.001.C1, Sep 2023, T-Mobile, T-Mobile MVNOs) Flash Link a309b3953d96b9c3c0c61282c195d36305a3a12a9542da3a2ddf88535f700e94 13.0.0 (TQ3A.230901.001.C2, Sep 2023, Verizon, Verizon MVNOs) Flash Link e7e2cf2e43dd986ee6afb4960badf452d5fc0bfc239c8a08a9e7cec643a10a63
Pixel Update Bulletin—September 2023 | Android Open Source Project
source.android.com
3Remember to unhide Magisk before you update. Sometimes not doing so has caused issues, and sometimes not.
Magisk (this time confirmed Stable) v26.3 released:
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to...
github.com
3The full changelog for Magisk since 26.2, as far as I know, never went Stable, only Beta:
3September Security Bulletin is up, but nothing else, yet.
Android Security Bulletin—September 2023 | Android Open Source Project
source.android.com
2Exclusive: Google Pixel 9 processor won't be the ambitious chip we hoped for
The Tensor G4 will be a more minor upgrade...www.androidauthority.com
-
62Pixel 6 Pro [Raven]
Updated July 13, 2023
Note that multiple users in several threads have said that 34.0.4 did not work correctly for them. I recommend sticking with 33.0.3 (below):
Google Pixel Update
Android Security Bulletins | Android Open Source Project
source.android.com
Regarding Developer Support Android 12 images, see @Lughnasadh's post here.
I am not linking directly to the Developer Support Android 12 images because I don't want them to be confused with Stable Android 12, and since the Developer Support images won't receive any OTAs...ever. They likely also will never be manually updated on the Developer Support images site, so they will forever be stuck with the security patch level they're currently on, which will become further out of date every month. You can Google searchDeveloper Support Android imagesif you want to find them.
TL;DR regarding the PSA. If you update one slot to Android 13, you canfastboot reboot bootloaderafter and thenfastboot --set-active=otherto change slots in order to flash Android 13 to the new slot, but IF you have Android 13 on one slot and still have Android 12 (including Android 12 bootloader) on the other slot and you try to fully boot into Android 12, you will be permanently bricked and have to seek repair from Google. No one has yet found a way to repair this on our own. I will update if there is any progress. At least a small handful, and probably more, people have done this already.
At a minimum, do this first:fastboot flash bootloader --slot all bootloader-devicename-slider-1.2-3456789.img(change the name of the bootloader file to the one for your device), then you *should* be much safer than without doing that first. Also note that the bootloader is NOT the same as boot.img (kernel). The bootloader image file has "bootloader" in the filename.
IF you have already bricked your phone and the screen is blank - there is likely nothing we can do to help. You should seek to get a repair from Google, possibly under warranty.
You CANNOT go back to Android 12 Stable. It *seems* as if you can, but Android 12 will not work 100% correctly after updating to the Android 13 bootloader.
My tiny, early, very mini-review of Android 13 is here.
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):
1515The 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.13
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.13Just 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
