Why use an old outdated mod? 2.40 mod 1.2 works well
How To Guide Platform-Tools v34.0.3 has a different bug - May 17, 2023 TQ2A.230505.002.G Verizon/MVNOs - May 1 TQ2A.230505.002 Global - Root Pixel 6 Pro [Raven]
- Thread starter roirraW "edor" ehT
- Start date
If it's working fine why mess with it? That also leaves me an update if the one I'm using stops working for some reason.
Google Pixel adding 'Adaptive Charging' status notification with one-time off button
Pixel Adaptive Charging has been a contentious feature, and Google is now updating it with a notification to note when it's active...
9to5google.com
Running into a problem since updating to the March Update, and unable to rule out hardware damage or update damage because I hadn't used my DAC in a couple weeks. I have at least been able to rule out Magisk Modules (I use Audio Modification Library and Audio Compatibility Patch) as this started happening before I re-enabled root after updating (I even attempted an uninstall of the Modules). I have also ruled out the DAC and earbuds as I have other DACs and headphones and still get the issue. I also ruled out Media Player Apps as it's happening with multiple ones. This issue does not happen with any other outputs, only in the described below scenario.
When I plug in my USB DAC for my 3.5mm wired earbuds and hit play all is good, when I turn off the screen all is good, but when I rotate the phone 90deg (so the port and cable are pointing up) the Media App freezes. Once that happens I have to physically unplug the DAC and pause the Playback before it will allow me to unlock the screen..
When I plug in my USB DAC for my 3.5mm wired earbuds and hit play all is good, when I turn off the screen all is good, but when I rotate the phone 90deg (so the port and cable are pointing up) the Media App freezes. Once that happens I have to physically unplug the DAC and pause the Playback before it will allow me to unlock the screen..
Thank you that solved it! I'm a little irked by needing to make this change, I usually have it set to "File transfer / Android Auto" because I've had issues with system auto-detecting USB connection types in the past, but oh well Google is going to make the changes they want.
March update broke USB Audio?
After I did the update yesterday when I connect any of my USB DACs they stop playing after I turn the screen off. When I turn the screen back on it doesn't resume playing and other apps freeze up and it will even restart on its own until I...
forum.xda-developers.com
Google's Nearby Share Beta is heading to Windows making file transfers from Android a breeze
A year after its announcement, Nearby Share is finally making an appearance for Windows.
The New Nearby Share Beta App for Windows | Android
Wirelessly share photos, documents, and more between Android devices and Windows PCs by downloading the Nearby Share Beta for Windows App.
Wait so i won't need a ftpserver on my phone anymore. *mind blown*Google's Nearby Share Beta is heading to Windows making file transfers from Android a breeze
A year after its announcement, Nearby Share is finally making an appearance for Windows.www.xda-developers.com
Well, we'll see how well Google's solution works, or if it'll get just popular enough that Google retires it.
If I remember, I'll test it tomorrow when the monthly update comes out.
Also if it's not baked into "phonelink"/"link to windows" then I'm gonna have to install google ware of my Microsoft ware.Well, we'll see how well Google's solution works, or if it'll get just popular enough that Google retires it.
And we're off!
Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers
developers.google.com
| 13.0.0 (TQ2A.230405.003.E1, Apr 2023) | Flash | Link | 6cadf2983e910cb563dfa09b24b7e0817b808d2d5dd79a096a7664489c49f5d7 |
Android Security Bulletin—April 2023 | Android Open Source Project
source.android.com
Last edited:
And we're off!
developers.google.com
Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers
developers.google.com
Wonder if I should wait and see if Google's going to release an F1 - Canada like March?And we're off!
Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers
It seems to me that most of the time, if there are going to be alternate firmwares, they release them at the same time as Global. That might not be the case 100% of the time, but it has been usually that way since I've been closely monitoring for the last year and a half.
Edit: It definitely was the case in March, where they released both sets of firmwares at the same time.
What's the baseband for the April stable update? Is it different than the QPR 2.1? g5123b-116954-230330-B-9849771
For my P6P, I have to flash the version that says for T-Mobile, correct?And we're off!
Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers
I bought it from T-Mobile. So I assume I can't flash Global.
If your bootloader is unlocked, you can flash any version you want. Even I, on Global with a direct from Google unlocked Pixel, and I'm not using T-Mobile as a carrier, could flash the T-Mobile variant if I wanted to see if it would make any difference. Come to think of it, I am doing a free three-month trial of T-Mobile, but they're not my main carrier and I most likely won't switch.
Since there is no T-Mobile-specific variant for the April update, flashing Global is the only option if you want to update. You don't have to update, but you can. You won't be able to downgrade without wiping data if you do upgrade, so if you find the Global radio doesn't work as well for you on T-Mobile as your current firmware, and if you want to go back to your now old firmware, you'd have to wipe data, otherwise things might misbehave if you downgrade without wiping.
I hope that helps.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
4
Android’s May 2023 security patch prevents downgrades to infinitely old system app versions
May’s security patch fixes a potential...www.androidpolice.com
3
They changed the time stamp of the zip again, but it's the same file as earlier today.3
I understand! And you're welcome!
Next up: A new survey by Google.
How many times would you like to reflash your device per month?
- 1
- 2
- 10
3Google will soon let Pixel phones double as dashcams
Rather than needing to buy a (sometimes...
9to5google.com
-
62Pixel 6 Pro [Raven]
Updated May 13, 2023
Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes)
Someone reported it to Google (added a comment about 34.0.1 to the existing 34.0.0 report).
Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers
developers.google.com
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.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
12
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.
