My method is just replace the init_boot.img inside the image-cheetah zip (Using 7-Zip, using Explorer causes it to fail to flash for some reason), then it flashes already-rooted in one pass.
(Edited to specify 7-Zip)
Last edited:
How To Guide Platform-Tools v34.0.3 has a different bug - May 1, 2023 TQ2A.230505.002 Global - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
- Thread starter roirraW "edor" ehT
- Start date
-
- Tags
- bootloader pixel 7 pixel 7 pro root
My method is just replace the init_boot.img inside the image-cheetah zip (Using 7-Zip, using Explorer causes it to fail to flash for some reason), then it flashes already-rooted in one pass.
(Edited to specify 7-Zip)
Tick it, although I believe it may be able to save that choice for you. Double check to make sure.
No, but if you decide to disable verity & verification again you will have to wipe.
I'll answer it here now, but in the future, please post your question in PF thread to keep this thread relevant to the topic it covers.
These settings in PF are remembered, so unless you change them, next time you load PF, it will select what you last had.
Keep Data will keep Data (basically remove -w)
Disable Verity and Disable Verification are used for custom Kernels / ROMs
These settings only apply when you flash.
Thanks. My question was a bit off maybe.
I like to know that if i update next month for example to a new version. Do i need to disable verity and verification AGAIN and will this wipe data AGAIN?
For me this question is not really pixel flasher specific thats why i asked here.
First time you disable them, it will wipe.
Subsequent flashing, if you don't want to wipe, then you have to make sure they remain disabled.
See it as a state, you change the state, it wipes.
Okay i think i got it thank you.
If i flash without:
fastboot update image-cheetah-buildnumber.zip --disable-verity --disable-verification
It would probably reenable verity/verification and result in a wipe.
But since i add --disable-verity --disable-verification the state will not change and there is no wipe.
English is not my native language so i needed clarification.
If you flash without disabling the verity and verification flags it won't cause a wipe in and of itself. What causes a wipe is when you go from an enabled state to a disabled state.
Correct, sort of. See first answer.
I've been getting this with my notifications on my lock screen. As far as I recall, starting yesterday. The notifications always start out minimized like this for at least several seconds, sometimes longer (the Google Voice notification):
Then it'll on its own switch to the expanded format I'm used to on the lockscreen (I obscured personal information):
Then it'll on its own switch to the expanded format I'm used to on the lockscreen (I obscured personal information):
Looks like a different (i.e. weird) attempt at competing with the iPhone dynamic island...?I've been getting this with my notifications on my lock screen. As far as I recall, starting yesterday. The notifications always start out minimized like this for at least several seconds, sometimes longer (the Google Voice notification):
Then it'll on its own switch to the expanded format I'm used to on the lockscreen (I obscured personal information):
Do you know what might've been recently updated? I imagine maybe Pixel Launcher...
Not that one, that's @Jawomo's [APP] dynamicSpot - iPhone 14 Pro Dynamic Island for android!. Sorry for not clarifying further. I mean in the middle of the screen, and Google Voice is just an example - all notifications were coming up minimized at first on my lock screen.
Then after a few seconds, they would maximize. In the last hour or two, the minimized lock screen notifications would no longer expand on their own, and not expand when I tried to manually expand them either, so I just checked, and my phone was set to hide sensitive content on my lock screen.
I can't swear which way I had it set most recently because there has been a time when I had sensitive content hidden, but I know my notifications had always used to come up as expanded on the lock screen - unless there were multiple notifications from the same app, that is.
Yesterday, I was fooling with BlueStacks Android emulator on my Windows PC, and I didn't set a lock screen or even fool with the lock screen settings, but I wonder if it synced some setting from there, but slowly in some strange way.
Either that or the whole thing is just some weird Google goings-on behind the scenes. So now I have it set to show sensitive content again, so the trouble should be over. Weird.
Edit: I don't use Pixel Launcher, I use Nova. I recently installed one 2FA app and a restaurant app, but I think that's all.
I have another strange problem with a manufacturer's app to control their device I have. The problem again didn't coincide with the March release. It only started happening in the last week or less.
Since shortly after I stared using the app, I set it to Unrestricted for battery usage, which then kept the connection alive (via Wi-Fi) 100% of the time, even if I left the area and came back, it would reconnect without me having to do anything. The remote app hasn't been updated since 2021, FYI.
All of a sudden this past week, the remote app would eventually lose connection, and I'd have to back out twice to its main menu and go back in to choose Remote Control. After a couple of days of this, I checked the Battery usage setting for the app again, and it was back to Optimized. I switched it back to Unrestricted, but it still loses connection, just like it used to before I set it to Unrestricted the first time.
I even wiped app cache and data, uninstalled and reinstalled, with no luck, it still loses connection. Bummer.
I don't pay attention to Google Play System updates, so I don't know what version I was on when the remote would stay connected, but I'm on the March 1, 2023, Play System update now.
TQ2A.230305.008.C1 Global firmware, not that it's likely to matter.
Since shortly after I stared using the app, I set it to Unrestricted for battery usage, which then kept the connection alive (via Wi-Fi) 100% of the time, even if I left the area and came back, it would reconnect without me having to do anything. The remote app hasn't been updated since 2021, FYI.
All of a sudden this past week, the remote app would eventually lose connection, and I'd have to back out twice to its main menu and go back in to choose Remote Control. After a couple of days of this, I checked the Battery usage setting for the app again, and it was back to Optimized. I switched it back to Unrestricted, but it still loses connection, just like it used to before I set it to Unrestricted the first time.
I even wiped app cache and data, uninstalled and reinstalled, with no luck, it still loses connection. Bummer.
I don't pay attention to Google Play System updates, so I don't know what version I was on when the remote would stay connected, but I'm on the March 1, 2023, Play System update now.
TQ2A.230305.008.C1 Global firmware, not that it's likely to matter.
FYI: Google Play System Updates are included in your monthly security patch.
Android Security Bulletin—March 2023 | Android Open Source Project
source.android.com
I don't know if this will resolve the issue -- or explain what the issue might be -- but if, somehow (if you are lucky), if you can enable the app in "device admin apps", it will force the app to be Unrestricted; Optimized and Restricted will actually be grayed out, so there's no choice but for the app to be Unrestricted. But I don't know what calls for an app to request/require device admin permissions, so I'm unsure if your app will be under that. But, if luckily it does, you can keep it at Unrestricted while you research the issue/problem and hopefully eventually not require it to have those permissions for it to stay.
I've noticed that I have to set some apps back to Unrestricted myself; but I wouldn't be able to recall what I had been doing when it had changed -- it was seemingly randomly me checking at any random time...
Not at all. If an app requests DEVICE_ADMIN_ENABLED it doesn't have the permissions to do all the actions of an admin. The requested permissions are defined in policies. Nova Launcher for example could change the lock screen as device admin and nothing else.
Are they always included in the regular monthly firmware updates? I recall at least on the Pixel 6 Pro, many users including me were not always on the same Play System Update as other users, even when running on the same firmware version.FYI: Google Play System Updates are included in your monthly security patch.
If your manufacturer doesn't provide any OTAs for your device then Google is still able to update core components via the Google Play System Updates (Project Mainline).Android Security Bulletin—March 2023 | Android Open Source Project
Also, there's a separate place to manually check for new Google Play system updates. At least once or twice, I was able to get an update to the Play system by manually checking for it, although I'm sure it would've updated automatically eventually, and I don't really pay attention to what version I'm on, normally.
This app doesn't appear among those available in the Device admin apps list, but a good idea to check. Thanks.
Yes, they have to. The Google Play System Update is updating
/system/apex/ which part of your firmware. These APEX files are special extended APK formats, but including a payload.img. For those users without the latest patch Google can download the APEX files through the Play Store. Then using the payload.img to update /system. APEX files are packed - like APKs - as ZIP archive.
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.
saw an article talking about this...am excited about it...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
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.android.com
bluetooth transfer is finicky and slower, and opening particular apps (going all the way back to SuperBeam) could get clumsy and tedious...
I constantly transfer stuff between phones and my pc/laptop...
Hi all,
Up untill the latest factory image update TQ2A.230305.008 there were no Canada version. I rooted my 7 pro to TQ1A.221205.011, Dec 2022 and haven't done any updates since then. I live in Canada, with Canadian carrier.
Should I grab the TQ2A.230305.008.A3, Mar 2023, WINDTRE/Canada or the Global, TQ2A.230305.008.C1, Mar 2023?
Would greatly appreciate your guidance.
Thanks
Up untill the latest factory image update TQ2A.230305.008 there were no Canada version. I rooted my 7 pro to TQ1A.221205.011, Dec 2022 and haven't done any updates since then. I live in Canada, with Canadian carrier.
Should I grab the TQ2A.230305.008.A3, Mar 2023, WINDTRE/Canada or the Global, TQ2A.230305.008.C1, Mar 2023?
Would greatly appreciate your guidance.
Thanks
I live in Toronto and I've tried the global and Canadian version and couldn't find any difference.
Top Liked Posts
-
6
For what it's worth, Mishaal Rahman said he tested it and the problem has been fixed.5Comparison of old and new 34.0.1 (utilities version changes)
Old:
ADB: 1.0.41 (34.0.1-9680074)
Fastboot: 34.0.1-9680074
Make_f2fs (casefold): 1.15.0 (2022-05-20)
Mke2fs: 1.46.6 (1-Feb-2023)
New:
ADB: 1.0.41 (34.0.1-9979309)
Fastboot: 34.0.1-9979309
Make_f2fs (casefold): 1.16.0 (2023-04-11)
Mke2fs: 1.46.6 (1-Feb-2023)55May update is now available: https://dl.google.com/dl/android/aosp/cheetah-tq2a.230505.002-factory-fe44ced0.zip -
60Pixel 7 Pro [Cheetah]
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).
The download links for 33.0.3:
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
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:
41Unlocking 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)
- CrazyBoyFeng's ACC Settings
- MatteCarra's 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:
