How To Guide March 20, 2023 TQ2A.230305.008.E1 Global | .F1 WINDTRE/Canada - Root Pixel 6 Pro [Raven] / all relevant links

[badabing2003]

Lol you quoted wrong post

oops sorry
@rocketj it was meant for you.

 

[rocketj]

Is it always at the same point that you got the error?
basically product_b 2/11 ?
If yes, the it could be that the image you downloaded is corrupted.
Always check the CRC to be certain.

If you still have the image, you can check the crc

Went to 3/11 one time. Yep checked out correctly.
Tried going back to the October image since it worked then and was the last one I had loaded.. same problem.
Tried pixelflasher with both also. same error.

 

[badabing2003]

Went to 3/11 one time. Yep checked out correctly.
Tried going back to the October image since it worked then and was the last one I had loaded.. same problem.
Tried pixelflasher with both also. same error.

I'm sure you have checked but have to ask, are you on the latest platform tools?
Have you tried PC reboot in case there are other processes interfering, straining the system.

 

[rocketj]

I'm sure you have checked but have to ask, are you on the latest platform tools?
Have you tried PC reboot in case there are other processes interfering, straining the system.

yes and reboot.
All good now after using AFT.
Thanks for all the suggestions.

 

[franco985]

Are you using Taptap magisk module?

 

[franco985]

More info on my issue with my phone not entering deep sleep. Usf_queue and usfsensorhalworker are the 2 wakelocks keeping my phone awake according to BBS

are you using Tap Tap?

 

[roirraW "edor" ehT]

If anyone hasn't seen this, there's a newer USNF mod by @Displax at XDA link or on GitHub.

 

[roirraW "edor" ehT]

@kdrag0n has some interesting work going on for the official Universal SafetyNet Fix (USNF) v2.4.0, that's now in testing.

 

[roirraW "edor" ehT]

Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers

developers.google.com

13.0.0 (TQ1A.230105.002, Jan 2023)

Flash

Link

924ad4baa13f6611a85bf3d1b2f26f8f61e4e90230b7b69618208323e47a94bb

Android Security Bulletin—January 2023 | Android Open Source Project

source.android.com

Android Security Bulletin—January 2023​

bookmark_border
Published January 3, 2022
The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 2023-01-05 or later address all of these issues. To learn how to check a device's security patch level, see Check and update your Android version.
Android partners are notified of all issues at least a month before publication. Source code patches for these issues will be released to the Android Open Source Project (AOSP) repository in the next 48 hours. We will revise this bulletin with the AOSP links when they are available.
The most severe of these issues is a high security vulnerability in the Framework component that could lead to local escalation of privilege with no additional execution privileges needed. The severity assessment is based on the effect that exploiting the vulnerability would possibly have on an affected device, assuming the platform and service mitigations are turned off for development purposes or if successfully bypassed.
Refer to the Android and Google Play Protect mitigations section for details on the Android security platform protections and Google Play Protect, which improve the security of the Android platform.
Note: Information on the latest over-the-air update (OTA) and firmware images for Google devices is available in the January 2023 Pixel Update Bulletin.

Android and Google service mitigations​

This is a summary of the mitigations provided by the Android security platform and service protections such as Google Play Protect. These capabilities reduce the likelihood that security vulnerabilities could be successfully exploited on Android.

• Exploitation for many issues on Android is made more difficult by enhancements in newer versions of the Android platform. We encourage all users to update to the latest version of Android where possible.
• The Android security team actively monitors for abuse through Google Play Protect and warns users about Potentially Harmful Applications. Google Play Protect is enabled by default on devices with Google Mobile Services, and is especially important for users who install apps from outside of Google Play.

2023-01-01 security patch level vulnerability details​

In the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-01-01 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID. Devices with Android 10 and later may receive security updates as well as Google Play system updates.

Framework​

The most severe vulnerability in this section could lead to local escalation of privilege with no additional execution privileges needed.

CVE	References	Type	Severity	Updated AOSP versions
CVE-2022-20456	A-242703780	EoP	High	10, 11, 12, 12L, 13
CVE-2022-20489	A-242703460	EoP	High	10, 11, 12, 12L, 13
CVE-2022-20490	A-242703505	EoP	High	10, 11, 12, 12L, 13
CVE-2022-20492	A-242704043	EoP	High	10, 11, 12, 12L, 13
CVE-2022-20493	A-242846316	EoP	High	10, 11, 12, 12L, 13
CVE-2023-20912	A-246301995	EoP	High	13
CVE-2023-20916	A-229256049	EoP	High	12, 12L
CVE-2023-20918	A-243794108	EoP	High	10, 11, 12, 12L, 13
CVE-2023-20919	A-252663068	EoP	High	13
CVE-2023-20920	A-204584366	EoP	High	10, 11, 12, 12L, 13
CVE-2023-20921	A-243378132	EoP	High	10, 11, 12, 12L, 13
CVE-2022-20494	A-243794204	DoS	High	10, 11, 12, 12L, 13
CVE-2023-20908	A-239415861	DoS	High	10, 11, 12, 12L, 13
CVE-2023-20922	A-237291548	DoS	High	11, 12, 12L, 13

System​

The most severe vulnerability in this section could lead to local escalation of privilege of BLE with no additional execution privileges needed.

CVE	References	Type	Severity	Updated AOSP versions
CVE-2022-20461	A-228602963	EoP	High	10, 11, 12, 12L, 13
CVE-2023-20904	A-246300272	EoP	High	12L, 13
CVE-2023-20905	A-241387741	EoP	High	10
CVE-2023-20913	A-246933785	EoP	High	10, 11, 12, 12L, 13
CVE-2023-20915	A-246930197	EoP	High	10, 11, 12, 12L, 13

Google Play system updates​

The following issues are included in Project Mainline components.

Subcomponent	CVE
MediaProvider	CVE-2023-20912

2023-01-05 security patch level vulnerability details​

In the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-01-05 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.

Kernel​

The most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed.

CVE	References	Type	Severity	Subcomponent
CVE-2022-42719	A-253642087 Upstream kernel [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]	RCE	Critical	mac80211
CVE-2022-42720	A-253642015 Upstream kernel [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]	RCE	Critical	WLAN
CVE-2022-42721	A-253642088 Upstream kernel [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]	RCE	Critical	Multiple Modules
CVE-2022-2959	A-244395411 Upstream kernel	EoP	High	Pipe

Kernel components​

The most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed.

CVE	References	Type	Severity	Subcomponent
CVE-2022-41674	A-253641805 Upstream kernel [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]	RCE	Critical	WLAN
CVE-2023-20928	A-254837884 Upstream kernel	EoP	High	Binder driver

Kernel LTS​

The following kernel versions have been updated. Kernel version updates are dependent on the version of Android OS at the time of device launch.

References	Android Launch Version	Kernel Launch Version	Minimum Launch Version
A-224575820	12	5.10	5.10.101

Imagination Technologies​

This vulnerability affects Imagination Technologies components and further details are available directly from Imagination Technologies. The severity assessment of this issue is provided directly by Imagination Technologies.

CVE	References		Severity	Subcomponent
CVE-2022-20235	A-259967780 *		High	PowerVR-GPU

MediaTek components​

These vulnerabilities affect MediaTek components and further details are available directly from MediaTek. The severity assessment of these issues is provided directly by MediaTek.

CVE	References		Severity	Subcomponent
CVE-2022-32635	A-257714327 M-ALPS07573237 *		High	gps
CVE-2022-32636	A-257846591 M-ALPS07510064 *		High	keyinstall
CVE-2022-32637	A-257860658 M-ALPS07491374 *		High	hevc decoder

Unisoc components​

These vulnerabilities affect Unisoc components and further details are available directly from Unisoc. The severity assessment of these issues is provided directly by Unisoc.

CVE	References		Severity	Subcomponent
CVE-2022-44425	A-258731891 U-2028856 *		High	Kernel
CVE-2022-44426	A-258728978 U-2028856 *		High	Kernel
CVE-2022-44427	A-258736883 U-1888565 *		High	Kernel
CVE-2022-44428	A-258741356 U-1888565 *		High	Kernel
CVE-2022-44429	A-258743555 U-1981296 *		High	Kernel
CVE-2022-44430	A-258749708 U-1888565 *		High	Kernel
CVE-2022-44431	A-258741360 U-1981296 *		High	Kernel
CVE-2022-44432	A-258743558 U-1981296 *		High	Kernel
CVE-2022-44434	A-258760518 U-2064988 *		High	Android
CVE-2022-44435	A-258759189 U-2064988 *		High	Android
CVE-2022-44436	A-258760519 U-2064988 *		High	Android
CVE-2022-44437	A-258759192 U-2064988 *		High	Android
CVE-2022-44438	A-258760781 U-2064988 *		High	Android

Qualcomm components​

These vulnerabilities affect Qualcomm components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.

CVE	References		Severity	Subcomponent
CVE-2022-22088	A-231156521 QC-CR#3052411		Critical	Bluetooth
CVE-2022-33255	A-250627529 QC-CR#3212699		High	Bluetooth

Qualcomm closed-source components​

These vulnerabilities affect Qualcomm closed-source components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.

CVE	References		Severity	Subcomponent
CVE-2021-35097	A-209469821 *		Critical	Closed-source component
CVE-2021-35113	A-209469998 *		Critical	Closed-source component
CVE-2021-35134	A-213239776 *		Critical	Closed-source component
CVE-2022-23960	A-238203772 *		High	Closed-source component
CVE-2022-25725	A-238101314 *		High	Closed-source component
CVE-2022-25746	A-238106983 *		High	Closed-source component
CVE-2022-33252	A-250627159 *		High	Closed-source component
CVE-2022-33253	A-250627591 *		High	Closed-source component
CVE-2022-33266	A-250627569 *		High	Closed-source component
CVE-2022-33274	A-250627236 *		High	Closed-source component
CVE-2022-33276	A-250627271 *		High	Closed-source component
CVE-2022-33283	A-250627602 *		High	Closed-source component
CVE-2022-33284	A-250627218 *		High	Closed-source component
CVE-2022-33285	A-250627435 *		High	Closed-source component
CVE-2022-33286	A-250627240 *		High	Closed-source component

Common questions and answers​

This section answers common questions that may occur after reading this bulletin.
1. How do I determine if my device is updated to address these issues?
To learn how to check a device's security patch level, see Check and update your Android version.

• Security patch levels of 2023-01-01 or later address all issues associated with the 2023-01-01 security patch level.
• Security patch levels of 2023-01-05 or later address all issues associated with the 2023-01-05 security patch level and all previous patch levels.

Device manufacturers that include these updates should set the patch string level to:

• [ro.build.version.security_patch]:[2023-01-01]
• [ro.build.version.security_patch]:[2023-01-05]

For some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2023-01-01 security patch level. Please see this article for more details on how to install security updates.
2. Why does this bulletin have two security patch levels?
This bulletin has two security patch levels so that Android partners have the flexibility to fix a subset of vulnerabilities that are similar across all Android devices more quickly. Android partners are encouraged to fix all issues in this bulletin and use the latest security patch level.

• Devices that use the 2023-01-01 security patch level must include all issues associated with that security patch level, as well as fixes for all issues reported in previous security bulletins.
• Devices that use the security patch level of 2023-01-05 or newer must include all applicable patches in this (and previous) security bulletins.

Partners are encouraged to bundle the fixes for all issues they are addressing in a single update.
3. What do the entries in the Type column mean?
Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.

Abbreviation	Definition
RCE	Remote code execution
EoP	Elevation of privilege
ID	Information disclosure
DoS	Denial of service
N/A	Classification not available

4. What do the entries in the References column mean?
Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.

Prefix	Reference
A-	Android bug ID
QC-	Qualcomm reference number
M-	MediaTek reference number
N-	NVIDIA reference number
B-	Broadcom reference number
U-	UNISOC reference number

5. What does an * next to the Android bug ID in the References column mean?
Issues that are not publicly available have an * next to the corresponding reference ID. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
6. Why are security vulnerabilities split between this bulletin and device / partner security bulletins, such as the Pixel bulletin?
Security vulnerabilities that are documented in this security bulletin are required to declare the latest security patch level on Android devices. Additional security vulnerabilities that are documented in the device / partner security bulletins are not required for declaring a security patch level. Android device and chipset manufacturers may also publish security vulnerability details specific to their products, such as Google, Huawei, LGE, Motorola, Nokia, or Samsung.

Versions​

Version	Date	Notes
1.0	January 3, 2022	Bulletin Published

 

[foobar66]

Thanks for the links. I have updated to January keeping root and data. I am still on the November Play-systemupdate though...

 

[roirraW "edor" ehT]

Google Pixel Update - January 2023 - Google Pixel Community

Kush M.

Community Manager•Original Poster

Google Pixel Update - January 2023​

Announcement
Hello Pixel Community,

We have provided the monthly software update for January 2023. All supported Pixel devices running Android 13 will receive these software updates starting today. The rollout will continue over the next few weeks in phases depending on carrier and device. Users will receive a notification once the OTA becomes available for their device. We encourage you to check your Android version and update to receive the latest software.

Details of this month’s security fixes can be found on the Android Security Bulletin: https://source.android.com/security/bulletin

This update also includes support for static spatial audio, which will provide surround sound for any connected headset. Another update will roll out to Pixel Buds Pro in the coming weeks that will enable spatial audio with head tracking.

Thanks,
Google Pixel Support Team


Software versions

Global

• Pixel 4a: TQ1A.230105.001
• Pixel 4a (5G): TQ1A.230105.001
• Pixel 5: TQ1A.230105.001
• Pixel 5a (5G): TQ1A.230105.001
• Pixel 6: TQ1A.230105.002
• Pixel 6 Pro: TQ1A.230105.002
• Pixel 6a: TQ1A.230105.001.A2
• Pixel 7: TQ1A.230105.001.A2
• Pixel 7 Pro: TQ1A.230105.002

Canada

• Pixel 4a: TQ1A.230105.001.B1

Telstra (AU)

• Pixel 7: TQ1A.230105.001.A3
• Pixel 7 Pro: TQ1A.230105.002.A1

What’s included

The January 2023 update includes bug fixes and improvements for Pixel users – see below for details.

Audio

• Add support for Spatial Audio with certain devices and accessories *[1]

Biometrics

• Additional improvements for fingerprint recognition and response in certain conditions *[2]

Bluetooth

• Fix for issue occasionally preventing certain Bluetooth Low Energy devices or accessories from pairing or reconnecting
• Fix for issue preventing audio from playing over certain headphones or accessories while connected in certain conditions

Camera

• Fix for issue occasionally causing captured photos to appear corrupted or distorted while zoomed in *[3]

Display & Graphics

• Fix for issue occasionally preventing display from waking or appearing turned off while device is powered on *[3]

User Interface

• Fix for issue occasionally causing UI to display in landscape layout while device is held in portrait mode

---------------------------------------------------------------

Device Applicability

Fixes are available for all supported Pixel devices unless otherwise indicated below.

*[1] Included on Pixel 6, Pixel 6 Pro, Pixel 7, Pixel 7 Pro
*[2] Included on Pixel 6a, Pixel 7
*[3] Included on Pixel 7, Pixel 7 Pro
Details
Other

 

[kevinireland11]

.

 

[roirraW "edor" ehT]

@kdrag0n's Universal SafetyNet Fix 2.4.,0 is official.

 

[david72262]

Google Pixel Update - January 2023 - Google Pixel Community

Still haven't got the update. Pushed to my phone on this. Pixel 6pro unlocked bought from Google on att. I Heard there are problems with T-Mobile and mvno using T-Mobile but I haven't got it yet either.

 

[Juuuuune]

If my pixel6Pro works in slot A and is Android 13, I don't know whether slot B is Android 12, so can I cover slot B through an OTA update （13）to avoid the above problems? (translate form Google)

 

[73sydney]

If my pixel6Pro works in slot A and is Android 13, I don't know whether slot B is Android 12, so can I cover slot B through an OTA update （13）to avoid the above problems? (translate form Google)

Read this, it includes a way to check which bootloader is in each slot "How do I check my current bootloader version?"

🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑

***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...

forum.xda-developers.com

Do this before you do anything else

 

[anawilliam850]

Thanks for the guidance

 

[roirraW "edor" ehT]

I've noticed this before but hadn't said anything. It's weird that at https://developers.google.com/android/images#raven, the Pixel 6 Pro is listed below the Pixel 6. For all the other devices where there was a regular and XL/Pro variants, the XL/Pro is listed above the regular device. Doesn't mean anything. Just a curiosity.

 

[roirraW "edor" ehT]

404 errors on new links for now, hopefully they'll work soon.

Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers

developers.google.com

13.0.0 (TQ1A.230205.001.D2, Feb 2023, T-Mobile, T-Mobile MVNOs)	Flash	Link	c407dfbcf91141020be919357fa161844296cb1e98ce027264240efde1c61abe
13.0.0 (TQ1A.230205.002, Feb 2023)	Flash	Link	0388bd905ed2f926a1b68779dda5f8a67f5ee0b395769a8fc60e6d82ef11a17e

 

[roirraW "edor" ehT]

Google Pixel Update - February 2023 - Google Pixel Community

https://support.google.com/profile/79501506

Kush M.

Community Manager•Original Poster
8 min. ago

Google Pixel Update - February 2023​

Announcement
Hello Pixel Community,

We have provided the monthly software update for February 2023. All supported Pixel devices running Android 13 will receive these software updates starting today. The rollout will continue over the next week in phases depending on carrier and device. Users will receive a notification once the OTA becomes available for their device. We encourage you to check your Android version and update to receive the latest software.

Details of this month’s security fixes can be found on the Android Security Bulletin: https://source.android.com/security/bulletin

Thanks,
Google Pixel Support Team


Software versions

Global

• Pixel 4a: TQ1A.230205.002
• Pixel 4a (5G): TQ1A.230205.002
• Pixel 5: TQ1A.230205.002
• Pixel 5a (5G): TQ1A.230205.002
• Pixel 6: TQ1A.230205.002
• Pixel 6 Pro: TQ1A.230205.002
• Pixel 6a: TQ1A.230205.002
• Pixel 7: TQ1A.230205.002
• Pixel 7 Pro: TQ1A.230205.002

Canada

• Pixel 4a: TQ1A.230205.001.B2

Telstra (AU)

• Pixel 7: TQ1A.230205.001.A2
• Pixel 7 Pro: TQ1A.230205.001.A2

T-Mobile, Google Fi (US)

• Pixel 4a (5G): TQ1A.230205.001.D2
• Pixel 5: TQ1A.230205.001.D2
• Pixel 5a (5G): TQ1A.230205.001.D2
• Pixel 6: TQ1A.230205.001.D2
• Pixel 6 Pro: TQ1A.230205.001.D2
• Pixel 6a: TQ1A.230205.001.D2
• Pixel 7: TQ1A.230205.001.D2
• Pixel 7 Pro: TQ1A.230205.001.D2

What’s included

The February 2023 update includes bug fixes and improvements for Pixel users – see below for details.

Accessibility

• Fix for issue preventing touch interaction with Braille keyboard in certain conditions

Audio

• Fix for issue occasionally causing instability while Clear Calling is enabled in certain conditions *[1]

Bluetooth

• Fix for issue occasionally preventing connection with certain Bluetooth devices or accessories

Framework

• Fix for issue occasionally preventing Work profile calendar information from updating in the background

---------------------------------------------------------------

Device Applicability

Fixes are available for all supported Pixel devices unless otherwise indicated below.

*[1] Included on Pixel 7, Pixel 7 Pro
Details
Other