1.5 hours later and still not working. That's weird!
How To Guide March 13, 2023 TQ2A.230305.008.C1 Global | .A3 WINDTRE/Canada - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
- Thread starter roirraW "edor" ehT
- Start date
-
- Tags
- bootloader pixel 7 pixel 7 pro root
It happened several months ago as well. They're actually available on Android Flash Tool, so hopefully we get them soon.
I'm not in hurry as I won't update today. I was just noticing how weird it is. I didn't remember that this happened a few months ago. Oh well.
Mine is updating OTA....albeit very slowly as is common with these Pixel devices.
I did try the links of the OTA's and they were not working but a few minutes later the OTA came through the settings on the phone.
I did try the links of the OTA's and they were not working but a few minutes later the OTA came through the settings on the phone.
I also have unlocked phone and T Mobile e-sim (Croatia)on beta T2B3.230109.002 . What to flash,also T Mobile or normal beta ? What is the difference between builds?
Yep, all the new links were giving a 404 error up until about 15 minutes ago. All working now.
If you're using T-Mobile, then use the T-Mobile firmware. Usually the difference is just optimization to work on that carrier. It's likely the others would work, too, but since the T-Mobile is made to work for those using T-Mobile, there's no reason not to use it unless for some reason it didn't work well for you.
Oh! You're on the QPR2 Beta 3? Did you opt into the beta or only manually flashed it? If you flash the Stable firmware over top the Beta, you must factory reset your device, and yes, you'd want to flash the T-Mobile version.
If you opted into the Beta, you should opt out first.
Sorry about the multiple posts in a row.
You shouldn't have to factory reset if flashing today's stable over QPR2 Beta 3.Oh! You're on the QPR2 Beta 3? Did you opt into the beta or only manually flashed it? If you flash the Stable firmware over top the Beta, you must factory reset your device, and yes, you'd want to flash the T-Mobile version.
If you opted into the Beta, you should opt out first.
Sorry about the multiple posts in a row.
Thanks for your quick response, I manually flashed beta. I just thinking is it builds made for T mobile for locked phones and as I see from your post it was not . I can try to flash it and see what happens.If you're using T-Mobile, then use the T-Mobile firmware. Usually the difference is just optimization to work on that carrier. It's likely the others would work, too, but since the T-Mobile is made to work for those using T-Mobile, there's no reason not to use it unless for some reason it didn't work well for you.
Oh! You're on the QPR2 Beta 3? Did you opt into the beta or only manually flashed it? If you flash the Stable firmware over top the Beta, you must factory reset your device, and yes, you'd want to flash the T-Mobile version.
If you opted into the Beta, you should opt out first.
Sorry about the multiple posts in a row.
You're welcome! Heed @Lughnasadh's post above your response:
But things do happen, so be prepared for the worst just in case.
I see a lot of people with the same complaint on that Chase Banking app. No solution the last time I looked.
It worked fine for me once I signed in (and enabled biometrics, but that's optional) while not rooted - before re-rooting. I had been trying to remember to do it after a new firmware update when I first got my P7P, but didn't remember until December to do it before I re-rooted. It's at least mostly been fine since then. The only possible side effect I have is that even though the app lets me sign in/use my fingerprint, and it does sign in, it gives me a quick pop-up as if I just signed in for the first time, with some newbie advice.
I installed the Global version (using T-Mo PSim) and everything is working except for Google Pay =/. Phone service is fine and seems normal - but I also have an esim that isn't from T-Mo....but I might try flashing the T-Mo factory image to see if GPay works.
Flashed in 152s. Lucky me i forgot that we are on February already, and only check this thread just now, just when the link was fixed. Lol.
Thank You again
Thank You again
Battery is eating up even with the latest KiriSakura kernel installed, and Wallet does not work, but January Patch it did work woth SafetyNet. Can i flash both slots back to January firmware?
Last edited:
have you try using shamiko magisk module? combine with enforce deny list unchecked?
Flashed latest build T-mobile on unlocked phone and wipe data,5G not working so must root and install Network guru to enable it. Google wallet not pass not working but bank app work.
Google wallet and google play was on deny list,play was certificed. I noticed bad quality when speaking with someone. No volte . Maybe must turn back to flash global build and see .
Google wallet and google play was on deny list,play was certificed. I noticed bad quality when speaking with someone. No volte . Maybe must turn back to flash global build and see .
Top Liked Posts
-
2
The ability it brings to turn it off for just one time sounds good, and users can probably long press it just like most any other notification and customize it, make it "silent" while still keeping it handy enough if you do wish to access it.
Of course, I know or imagine that most users aren't even aware of the ability to customize notifications, but they'll either find out or they won't.
2
I only remembered that, when I first set up my P7P, I had to choose to enable it....Oh... It looked like it would be active by default (with compatible multi-voltage charger) with option to turn off once (until a reboot?) and that user is simply notified now... Am I wrong?
PW
1Google Pixel adding 'Adaptive Charging' status notification with one-time off button
Pixel Adaptive Charging has been a contentious...9to5google.com
1
saw this last night...kinda freaked me out...Google Pixel adding 'Adaptive Charging' status notification with one-time off button
Pixel Adaptive Charging has been a contentious...
I mean, i guess it's good to know and all, but since it's not on/enabled by default, I wonder how much it really needs to be notified -- as the user would surely know it's on because they turned it on.
Then again, it might be good to suggest if the user doesn't have it enabled and might be interested in it....1
Oh... It looked like it would be active by default (with compatible multi-voltage charger) but with new option to turn off once (until a reboot?) and that user is simply notified now... Am I wrong?
Other devices normally have adaptive charging on by default when available... PW -
9
https://source.android.com/docs/setup/about/build-numbers#build-ids-defined
First character is the version code of the release of Android, in this case Tiramisu (T) which is Android 13.
The second character is the branch of device platform that the build is from.
- D: Device specific branch, what the device launches with until the next branch merge.
- P: Primary branch, designates release branch for a successive version of Android for the device.
- Q: Quarterly platform release, the feature drops that happen every quarter.
The date roughly corresponds to when it was branched, but is mainly used to distinguish what the security patch level for release builds. Developers builds are closer to the true time it was branched.
The next three digits relate to versions based on that dated branch, and differ when a telecom needs a larger change, for example in the radio firmware or other larger change.
The last two characters are hotfixes, which usually include small changes for telecoms that need something like their APN changed after the date branch.
In this case TQ1A.230205.002 is Android 13 QPR1 that includes security patch 2023-02-05, and TQ2A.230305.008 is Android 13 QPR2 that includes security patch 2023-03-05.7Did my usual prep for the March update and everything went fine.
- Unhid Magisk
- Patched init_boot
- Edited Flash-all.bat by removing -w and adding -disable-verity and -disable-verification.
- Ran edited Flash-all
- Flashed modified init_boot
- Restored AOSPmod
- Hid Magisk
Just waiting for an updated kernel from Kiri6
So, here is the commit with fix. Waiting to merge.
5
Have a look at your bootloader.img + radio.img. The device's name of a Pixel 7 Pro is "cheeta" and "bramble" (like yours) is the Pixel 4a 5G.5
tried to flash the latest build of AncientOS with it, did not work. Back to r33.0.3 and it worked fine -
59Pixel 7 Pro [Cheetah]
Note that more than three users have said that 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).
The download links for 33.0.3:
March 13, 2023
Download links working now, and thanks to @Ghisy for making me aware the links were up:
Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers
developers.google.com
13.0.0 (TQ2A.230305.008.A3, Mar 2023, WINDTRE/Canada) Flash Link da1d99156fa03162ee8216277a8ff06b626f16efbc7e8b5d12096c5a10ede1ef 13.0.0 (TQ2A.230305.008.C1, Mar 2023) Flash Link cefc4e564cb920af510a44a9cdb982ba4e8af879f6796490e03128f12f92189e
https://support.google.com/profile/79501506
(revised v1.1 March 8, 2023)Android Security Bulletin—March 2023 | 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
- TL;DR - for the seasoned repeat users
- 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:
40Unlocking 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):
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.21Other, most important resources
A list of other important apps: - be sure to thank the respective OPs:
- Here's the Magisk section of XDA's forums, for rooting. Magisk on GitHub.
- @[email protected]'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)
- AccA (Advanced Charging Controller App)
- @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!
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.
- Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:
