Thanks. Afterwards, Play System update remains as of 2/1/2023. Weirdest re-locking bootloader experience
13.0.0 (TQ3A.230901.001, Sep 2023) Flash Link 6b946f4db4b28d04ff436924f9e9dbf18f989df22c2298bbf7889f1a7db9d515 13.0.0 (TQ3A.230901.001.C2, Sep 2023, Verizon, Verizon MVNOs) Flash Link 5f2b98dc82b80b7f2753ecb2ed02d08689c3ccf53ceae6542b183da8f19e1e36
Pixel Update Bulletin—September 2023 | Android Open Source Project
source.android.com
How To Guide September 18, 2023 TQ3A.230901.001 Global | .C2 Verizon - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
- Thread starter roirraW "edor" ehT
- Start date
-
- Tags
- bootloader pixel 7 pixel 7 pro root
Mine's on August 1, 2023 Play System update, both before and after flashing the September update. I believe it updates independently, or at least partially.
I hope stable 14 or QPR1 are the same. Google has a nasty habit of breaking various combos of root, Safetynet, and Play Integrity with final releases and new branches.
I updated using platform tools 33.0.3. No issues. I'm to chicken too try 34.0.4.
Same. Used 34.0.4 for the August update with no issues, but then later on there were posts here from people facing fastboot problems, so I played it safe and used 33.0.3 for September.
...same story here... flashed August update with PF using PFT 34.0.4 (most recent version) without any troubles. But this time (september update), I was playing safe as well and used PFT 33.0.3 -> all good, no problems.
greetings rage
The thing is I changed from root to unroot. Upon relocking and reflash and wipe, it now shows 2/1/2023 with no sign of update
Yeah, the Play System updates are definitely weird. Give it a month.
For those who might ask.
Magisk 26.3 patched image works fine.
I recommend using Pixelflasher to update. Why do all the steps manually when it do them for you?
Magisk 26.3 patched image works fine.
I recommend using Pixelflasher to update. Why do all the steps manually when it do them for you?
The weird thing is I don't know if it handles bootloader locked devices. When I use flash.android.com, checking the lock box or unchecking would both cause a wipe. So I ended up just using OTA update thru the phone's menu.For those who might ask.
Magisk 26.3 patched image works fine.
I recommend using Pixelflasher to update. Why do all the steps manually when it do them for you?
It is absolutely hilarious to me how broken the Google play system updates are. I did a clean install of the September update usually do a clean install every 6 months or so to improve performance. But now it thinks February is the most recent update upon multiple check attempts. Despite being on August before I did the clean install 
Attachments
It is absolutely hilarious to me how broken the Google play system updates are. I did a clean install of the September update usually do a clean install every 6 months or so to improve performance. But now it thinks February is the most recent update upon multiple check attempts. Despite being on August before I did the clean install
Google do be funky like that.
You are not alone. I recently wiped and re-locked bootloader in order to use Google One VPN and tackle intune company portal detecting root and this is what I experience too. Waiting for miracleIt is absolutely hilarious to me how broken the Google play system updates are. I did a clean install of the September update usually do a clean install every 6 months or so to improve performance. But now it thinks February is the most recent update upon multiple check attempts. Despite being on August before I did the clean install
allenjthomsen
Senior Member
What app is that? Im curiousIt is absolutely hilarious to me how broken the Google play system updates are. I did a clean install of the September update usually do a clean install every 6 months or so to improve performance. But now it thinks February is the most recent update upon multiple check attempts. Despite being on August before I did the clean install
Not sure what you mean. It's not an app it's built into the OS. It's the decoupled modules they rolled out awhile back. They get grouped together as the play system updates
allenjthomsen
Senior Member
If you go to Settings, and type Play System in the search bar, you should find the option to check for updates there, although I don't really pay attention to it. It updates itself when it feels like it, and as far as I know, I haven't had any problems.
How the hell is there a Android 14 QPR1 Beta 1 if there hasn't been a stable Android 14 release?!?!?!?!?
www.droid-life.com
Android 14 QPR1 Beta 1 Released for Pixel Phones!
In what truly is an odd set of circumstances, Android 14 QPR1 Beta 1 is now available for select Pixel devices. Looking back, we’re relatively certain this has never happened, where a QPR (quarterly platform release) build is launched for an Android version that isn’t yet released as stable...
Top Liked Posts
-
There are no posts matching your filters.
-
12
13.0.0 (TQ3A.230901.001, Sep 2023) Flash Link 6b946f4db4b28d04ff436924f9e9dbf18f989df22c2298bbf7889f1a7db9d515 13.0.0 (TQ3A.230901.001.C2, Sep 2023, Verizon, Verizon MVNOs) Flash Link 5f2b98dc82b80b7f2753ecb2ed02d08689c3ccf53ceae6542b183da8f19e1e36
Pixel Update Bulletin—September 2023 | Android Open Source Project
source.android.com
6
Betas for Android OS versions are released before the stable versions, but these are separate from the QPR betas, which they started with the Pixel 6 series being released. The A14 QPR1 betas (there should be 3 of them, at least, one in each month) are to test the stable release of A14 QPR1, which will be released in December. Then they will start the A14 QPR2 betas, which will test the A14 QPR2 stable release in March. Finally, there will be the A14 QPR3 betas which will test the stable release of A14 QPR3 in June. Of course, all of this assumes they will continue with what they have been doing.
Then, sometime in February of 2024 they will also release the 1st A15 beta (Developer Preview 1), assuming they abide by their earlier history.
This year was different, however, with the first A14 QPR1 beta being released before the stable version of A14 will be released. The stable version of A14 was originally scheduled to be released with the September monthly build, but was delayed. Google then decided, for whatever reason, to release the first A14 QPR1 beta now instead of waiting for the first stable A14 build to be released first (Oct. 4).4Remember 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
4
DO.NOT.TEMPT.MEGoogle's Pixel 8 and Watch 2 launch event set for October 4
Google's started sending out invites for its...www.xda-developers.com
10 AM
No, I don't yet know if I'll go for the 8 Pro, but it's a possibility. -
64Pixel 7 Pro [Cheetah]
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
Here there be dragons.
I am not responsible for anything at all. 
VERY IMPORTANT - On the Pixel 7/Pro, we use Magisk to patch
Thanks to @edcsxz, @Lughnasadh, and @AndyYan for news about that and confirming it.init_boot.img, NOT boot.img AND we flash the patched init_boot to the init_boot partition - do not flash it to the boot partition.
Moved @mariusnoor's provided zero-day OTA.zip to Post #8 - Old news from the OP.
INDEX:
- Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:
- How to Root the first time / aka How to unlock the Bootloader
- Unlocking Bootloader (required in order to root)
- How to update each month (and also how to root)[requires an unlocked bootloader for updating via this factory image method]
- OPTIONAL: If you want to flash both slots, after this first time, then after do the following
- SafetyNet
- Optional steps when updating - flashing custom kernels
- The two schools of thought on disabling Verity and Verification
- ADB/Fastboot and Windows USB Drivers - direct download links and the most recent changelog
- Post #3 - Other, most important resources:
- A list of other important apps
- TWRP [not made for the Pixel 7 (or 6) Pro yet - will update when or if ever it has - don't hold your breath]
- Factory Images (requires an unlocked bootloader)
- Full OTA Images(doesn't require an unlocked bootloader - you can ask questions in this thread, but I won't be providing the steps necessary, as I always use the factory image)
- @mariusnoor's provided official URL to download the zero-day OTA to
TD1A.220804.031.
- @mariusnoor's provided official URL to download the zero-day OTA to
- Check warranty status
Official Google Pixel Update and Software Repair(reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro - no idea if it has yet now, or if it will be for the 7/Pro)- 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 - if it's anything like the Pixel 6 Pro: if you have the screen replaced, then you *must* have the fingerprint reader replaced as well.
- Find problem apps, Magisk, and LSposed Modules by (three different methods)
- Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you do not have to manually unlock the bootloader - their site will do that on its own)
- How to determine if you already have Verity and Verification disabled (required for custom kernels for now)
- How to unroot
- Post #4 - Build ID definitions
- Post #5 - Blank
- Post #6 - Regarding P7P 5G model numbers and capabilities, and how to determine your hardware version
- Post #7 - My personal advice for how to get your device back up and running as you had it before a factory reset
- Post #8 - Old news from the OP
Thank you to the following users who have all contributed greatly to my knowledge of Pixels since I came back to XDA a year ago after a few years of mostly inactivity. Apologies if I miss anybody. In alphabetical order:
44Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers
Unlocking Bootloader / Rooting / Updating:
How to Root the first time / aka How to unlock the Bootloader:
Unlocking the bootloader will factory reset your device. There is no way around this. I highly suggest never re-locking your bootloader once you unlock it. If you do ever re-lock the bootloader, only do so after restoring the phone to 100% stock by using the latest Pixel 7 Pro Factory Image or Official Google Android Flash Tool.
Verizon variants:
T-Mobile and AT&T variants:
The direct-from-Google (or other retailers who aren't U.S. Carriers), the factory Carrier Unlocked Pixels:
The rest of the world's carriers:
Other than trying the things I mentioned above, there is nothing else that anyone on XDA can do to help get OEM unlocking to be ungrayed.
Unlocking Bootloader (required in order to root)
How to update each month (and also how to root) [requires an unlocked bootloader for updating via this factory image method]
- These three instructions only apply if you're already rooted and updating from one firmware version to another:
- Made sure all Magisk Modules have been updated.
- Disable all Magisk Modules.
- UNhide Magisk!
- If you are going to use the Official Google Android Flash Tool, then skip the steps I indicate with FAB(Flash-All.Bat).
- If using the Android Flash Tool to update/dirty flash, you should have the following items notselected:
- Deselect Wipe
- Deselect Force Flash all partitions (which will also wipe)
- Deselect re-lock bootloader
- If using the Android Flash Tool to update/dirty flash, you should have the following items notselected:
- Always use the latest ADB/Fastboot (SDK Platform Tools) and Windows USB Drivers.
- Unzip the Platform Tools.
- Download the latest Pixel 7 Pro Factory Image (at the bottom of the "Cheetah" section).
- Unzip the factory image to the same
platform-toolsfolder, i.e. so that flash-all.bat and all other files are in the same folder as ADB and Fastboot from the platform-tools. - * FAB VERY important - Edit the
flash-all.bat(on Windows) orflash-all.sh(on Linux) and remove the-wfrom thefastboot update image-cheetah-etcetera.zipline. This will keep the script from wiping your phone when you run it. - Extract only the
init_boot.imgfile from theimage-cheetah-etcetera.zipto the sameplatform-toolsfolder. - Copy the init_boot.img from the PC to the phone's internal storage.
- On the phone: Apply Magisk Stable to the new stock
init_boot.img. NOTE: It is always possible that an Android Update (Monthly, QPR [Quarterly Platform Release], new major Android versions, and Beta versions) might need a new version of Magisk Stable, Beta, or Canary from GitHub to work correctly. XDA forum for Magisk is here.- Launch the Magisk app.
- Beside "Magisk", click "Install".
- Click "Select and Patch a File", and choose the init_boot.img that you just copied to the phone's storage.
- Copy the Magisk'd init_boot.img (filename similar to
magisk_patched-25200_1a2B3c.img)back over to the computer. - * FAB Run commands:
Code:adb reboot bootloader flash-all.bat (on Windows) or flash-all.sh (on Linux) (Note: At least two Apple Macintosh users had trouble using the flash-all.sh - at least one of those users, everything went smooth once they used a Windows PC for this part of the process)IMPORTANT - The flash-all will take several minutes and reboot on its own several times including to a mode called "FastbootD", and finally reboot into full Android when it's done. Do not interrupt this process. On the FastbootD screen on the phone, do not use any of the manual selection options - let the flash-all script do it's work. Do not unplug your phone until it has fully booted into Android.
Thanks to @PurppleMonkey and @xgerryx for suggesting a warning about this. Thanks to @simplepinoi177 for suggesting the "FastbootD" clarification. - On the phone:
- Wait for the phone to boot normally.
- OPTIONAL: If you want to flash both slots, after this first time, then after do the following:
Code:adb reboot bootloader fastboot --set-active=other flash-all.bat
- On the computer:
- Open a Command Prompt and navigate to the
platform-toolsfolder. - Run command:
Code:adb reboot bootloader - After phone has rebooted into Bootloader (Fastboot) mode, run command:
Code:fastboot flash init_boot magisk_patched-25200_1a2B3c.img fastboot reboot
- Open a Command Prompt and navigate to the
- Unlock the phone.
- Confirm that the phone boots completely normally.
- Cautiously re-enable Magisk Modules.
- Reboot.
- Confirm everything worked fine.
- If the phone won't boot correctly after having enabled Magisk Modules, see either of the two solutions below:
-
- Find problem apps, Magisk, and LSposed Modules by (three different methods) section in my next post. After following that link, you may have to scroll up a little bit and the section title will be highlighted.
-
SafetyNet:
Use whichever of these is newer than the other:
- @Displax Universal SafetyNet Fix Mod on XDA.
- Official Universal SafetyNet Fix released by @kdrag0n available at XDA.
Optional steps when updating - flashing custom kernels:
ADB/Fastboot & Windows USB Drivers:
Platform Tools was updated in August 2022 to v33.0.3 (don't use the newer v34.0.0 - it has issues):
23Other, most important resources
A list of other important apps: - be sure to thank the respective OPs:
- OpenHashTab for Windows
- Hash Checker for Android
- Here's the Magisk section of XDA's forums, for rooting. Magisk on GitHub.
- @kevin@TeslaCoil's section for Nova Launcher / Nova Launcher Prime - been using this since early 2012!
- @capntrips' thread [DEV] Kernel Flasher
- [KERNEL] CleanSlate |S2S|AdBlock|VIB|BatterySvr - Thanks @tbalden!
- [Kernel] [Android Stable]Kirisakura for Pixel 7/Pro aka "Pantah" - thanks @Freak07!
- [KERNEL]Despair Kernel - Thanks @DespairFactor!
- Multi Timer StopWatch - this multiple timer app is the bomb. Got widgets, customization like crazy, you name it.
- See my review with screenshots about Multi Timer StopWatch here.
- @Chainfire's thread [APP][5.0+][2020.12.22] CF.lumen v3.74 - I used to use this app to enable my phones to go extra dim before Android developed the better native capability for that, and the app has been confirmed to work on the Pixel 7 Pro for color control, too
- @jorrik98's thread [Themes / Apps / Mods] Better Internet Tiles - Bring back Wi-Fi and mobile data toggles! (non-root)
- @VR25's thread Advanced Charging Controller (ACC)
- CrazyBoyFeng's ACC Settings
- MatteCarra's AccA (Advanced Charging Controller App)
- @ayush.gl's thread LSPosed Xposed Framework [8.1-13.0]. Simple Magisk Module
- @siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+. This is a big one for me, personally.
- @Quinny899's thread [APP][ROOT][11+][19/07] Classic Power Menu - Power Menu Replacement w/ Wallet, Controls on Android 11, 12, 13+
- Swift Backup
- @j4velin's thread [APP] Wallpaper Changer - been using this since mid-2011!
- @Jawomo's thread [Themes / Apps / Mods] aodNotify - Notification Light / LED - see my post in that thread here for the proper offsets to use the front camera notification circle on the Pixel 7 Pro.
- @Jawomo's thread [APP] dynamicSpot - iPhone 14 Pro Dynamic Island for android!
- @huskydg's Magisk_OverlayFS, which has the effect to make /system r/w - not compatible with Android 14 yet, as of July 7, 2023
GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
Make system partition become read-write (it is...
github.com
How to unroot
One of these two options:
- Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you do not have to manually unlock the bootloader - their site will do that on its own).
Select the options to:- Wipe
- Force flash all partitions
- Re-lock bootloader
- Flash the completely stock init_boot.img from the same firmware version that you're on:
Code:adb reboot bootloader fastboot flash init_boot init_boot.img
TWRP [not made for the Pixel 7 (or 6) Pro yet - will update when or if ever it has - don't hold your breath]
Factory Images (requires an unlocked bootloader)
Full OTA Images (doesn't require an unlocked bootloader - you can ask questions in this thread, but I won't be providing the steps necessary, as I always use the factory image)
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 - no idea if it has yet now, or if it will be for the 7/Pro)
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 - if it's anything like the Pixel 6 Pro: if you have the screen replaced, then you *must* have the fingerprint reader replaced as well.
Find problem apps, Magisk, and LSposed Modules by (three different methods):
- 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 re-enable 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.
- You can also follow @Jon8RFC's advice:
Worked for me yesterday when I accidentally tried some old version of a Magisk Module. You have to reinstall your Magisk Modules, but if you're using a third-party widget, it won't disable them like Safe mode does. - (May only be for mis-behaving LSposed modules):
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you do not have to manually unlock the bootloader - their site will do that on its own)
How to determine if you already have Verity and Verification disabled (required for custom kernels for now)
Alternative two more manual ways of checking:I keep seeing this asked, so I added a Magisk module for it to the linked Github release. With the module installed, you can just run:
Code:su avbctl get-verity avbctl get-verification
I spent way more time debugging that I downloaded Github's HTML of theupdate-binaryscript rather than the raw file than I care to admit.
Off to bed.
22
Indeed. My MOD is a temporary solution until kdrag0n release accurate fix.
I didn't change the update channel in the module on purpose so that everyone can upgrade to the new official version automatically without any problems. - Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:
