I followed the procedure you recommended. Thanks again!
How To Guide January 3, 2023 (TQ1A.230105.002 - Global / .A1 Telstra) - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
- Thread starter roirraW "edor" ehT
- Start date
-
- Tags
- bootloader pixel 7 pixel 7 pro root
@roirraW "edor" ehT Regarding Posts #1535-41...
I believe these problems occurred because this person had never flashed the firmware to slot b (e.g. in cases where it's a new phone), thus when they set their active slot to b and issued the
I would like to suggest that in the OP, Post #2, Section 11, OPTIONAL: If you want to flash both slots, after this first time, then after do the following:, that it be noted that if the user has never flashed the firmware to their inactive slot (via OTA, flashing factory image, etc.) that they skip the
EDIT: Apparently that person thinks they did successfully flash the firmware to both slots beforehand, so maybe this wasn't the case in this instance.
I believe these problems occurred because this person had never flashed the firmware to slot b (e.g. in cases where it's a new phone), thus when they set their active slot to b and issued the
fastboot reboot bootloader command, there was nothing to boot into so it bootlooped back to slot a.I would like to suggest that in the OP, Post #2, Section 11, OPTIONAL: If you want to flash both slots, after this first time, then after do the following:, that it be noted that if the user has never flashed the firmware to their inactive slot (via OTA, flashing factory image, etc.) that they skip the
fastboot reboot bootloader command, thus preventing what happened above from occurring.EDIT: Apparently that person thinks they did successfully flash the firmware to both slots beforehand, so maybe this wasn't the case in this instance.
Last edited:
I had flashed the previous firmware to both slots successully. Or at least I thought I did. Why this latest firmware misbehaved I'm not certain, but I think your advice to the OP holds merit since it has proven to resolve my issue. Appreciate everyone's help.
You could use either one. The main difference would be that the UK version would be optimized for your regions network/basebands. If you did flash the global version it would boot and work fine but you might sacrifice your network connectivity
simplepinoi177
Senior Member
Thank you for this clarification! I was going to follow the instructions from badabing2003 on post #1341 because I haven't installed an OTA nor flashed to both slots before, but didn't understand the reason why I was to skip rebooting to bootloader and was going to omit that, so I am very grateful you clarified this for me and saved me a whole lot of headache!
This is the only difference I think. The modem and confseq files are indentical on the o2 and the main firmware versions. Use the o2 one if you're their client.
I updated my phone from Nov to Dec. However, when I try to root the Dec update i get the error below. Any ideas on how to fix this?
"FAILED (remote: partition (init_boot) not found)"
"FAILED (remote: partition (init_boot) not found)"
Have you tried "fastboot flash init_boot" and then click on the patched image and drag and drop it in to cmd?
You could try flashing the slots directly.
"fastboot flash init_boot_a magisk_patched_boot.img"
"fastboot flash init_boot_b magisk_patched_boot.img"
Last edited:
I am on Dec pixel feature drop and still having 2 seperate Security and Privacy menu in settings. I have heard that this menu is now combined? Any idea why its different for me?
JakeDHS07
Senior Member
It's a server side rollout not in the actual update itself. Not sure if it's attached to the play system update or play services but it will eventually change. Idk anyone who has it yet.
JakeDHS07
Senior Member
Yesterday the Security and Privacy settings were combined on my phone. I rebooted during the day and it showed up.
Top Liked Posts
-
There are no posts matching your filters.
-
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.6@kdrag0n has some interesting work going on for the official Universal SafetyNet Fix (USNF) v2.4.0, that's now in testing.5
He's released it to his Patreon members. Hopefully it will be released to the general public in a week or two.
Highlights
- Play Integrity bypass without breaking device checks or causing other issues
- Disabled use of hardware attestation on Pixel 7 and newer (@anirudhgupta109)
Other changes
- Updated instructions for newer Android and Magisk versions
- Better debugging for future development
5
I would expect that once 2.4.0 is released publicly, we should probably go back to using the official release, but conversely, as long as something works for you, there's also not necessarily a need to fix what isn't broken. Personally, I plan on switching once it's made completely public.
Note that @Displax wasn't trying to replace the official version - they always kept it the same version as the most recent official along with "Mod", "Mod 2", or "Mod 2.1", so that suggests to me they were merely making temporary workarounds until/if the official was updated.
The methods used in 2.4.0 sound superior to the implementation used in the Mod versions. Some users had previously reported a Mod version making their device at least temporarily reported as a wrong (old) device, and 2.4.0 should prevent that.5Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers
developers.google.com
13.0.0 (TQ1A.230105.002, Jan 2023) Flash Link 34d676ff4d260f02d9ada1f16f24fd7995c9b9ca832410099950d9c510db8793 13.0.0 (TQ1A.230105.002.A1, Jan 2023, Telstra) Flash Link 6632344c9647b04bfce622b0decf3733dfb3bc5c3b2c068ea118f8631c1b39b8
Android Security Bulletin—January 2023 | Android Open Source Project
source.android.com
-
58
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 34d676ff4d260f02d9ada1f16f24fd7995c9b9ca832410099950d9c510db8793 13.0.0 (TQ1A.230105.002.A1, Jan 2023, Telstra) Flash Link 6632344c9647b04bfce622b0decf3733dfb3bc5c3b2c068ea118f8631c1b39b8
Android Security Bulletin—January 2023 | Android Open Source Project
source.android.com
The answer to life, the universe, and everything.(* I do not claim copyright to this image, nor do I benefit monetarily from it or these posts)
Just kidding (the answer is 42, by the way):
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 - Google Pixel Updates (more user-friendly to read than Pixel Update Bulletins) (nothing for the P7P yet)
- Old Google posts/updates
- Post #5 - Pixel Update Bulletins
- Old Bulletins
- 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:
39Unlocking 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.
- * 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. Unlock the phone.
- 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
- Apply Magisk Stable to it. 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. - 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 - 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:
New Official Universal SafetyNet Fix released by @kdrag0n v2.4.0 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:
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.17Other, 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:
