yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] roirraW "edor" ehT:
You shouldn't be patching the stock boot.img at all on the Pixel 7/Pro. Only the init_boot.img. It looks like maybe you were trying to flash the Magisk'd boot.img to the init_boot partition.

Extract the stock unrooted boot.img and init_boot.img out of the inner zip from the factory image, copy the stock init_boot.img to your phone, apply Magisk to the init_boot.img, copy that Magisk'd copy of init_boot.img (magisk_patched-xx.img) back to the PC, then do:

adb reboot bootloader
fastboot flash boot boot.img
fastboot flash init_boot magisk_patched-xx.img (Magisk'd init_boot.img)

Ah, cool. I'm glad the Android Flash Tool worked for you for that part at least. I'll have to think some more on the problem after dinner, although I understand you may not get back into the fray of things right away, and I understand needing to just let it be for now.
[Google Pixel 7 Pro] Bxperiaz3:
Thank you. Willing to try something else tomorrow but I'm not getting any of the flashing to slot a or any dialogue like the above user. It seems as if none of my commands are actually activating and I just don't know enough to troubleshoot at the moment. I'll do some more digging and report if I solve
[Google Pixel 7 Pro] collegencmc:
Thank you very very much!!
[Google Pixel 7 Pro] badabing2003:
good catch
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thank you! I've finally caught up enough to respond, and also to let you know I quoted your post in my instructions as the option #1 when re-enabling a Magisk Module causes a boot loop on a new update.

I had seen this before but forgot about it.

Cheers!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Heads up everyone regarding Swift Backup not working correctly on the Pixel 7/Pro:

Edit: I haven't tried it lately, but reports are that Swift Backup was updated a couple of days ago to support the Pixel 7/Pro.
[Google Pixel 7 Pro] Hondroid:
Thanks for all the hard work guys. My unlocked 7 Pro 512gb is now rooted with gpay working. I'm a happy camper :)
[Google Pixel 7 Pro] llin:
Success with Google Wallet and Bank of America. Added a card to Wallet and paid at a store. YASNAC passes basic integrity and fails CTS.

Magisk 25.2 with safetynet-fix-v2.3.1-MOD. DenyList is enabled although from other posts it appears this is unnecessary but since it's working I'm not touching anything!
[Google Pixel 7 Pro] JakeDHS07:
There's a new version of 2.0 uploaded by Displax that is corrected and working. No longer necessary to use test build. Verified myself a few moments ago 👍
[Google Pixel 7 Pro] bleez99:
Yup. Passing safety net and I just added my cards without issue. Didn't try to buy anything yet. @Displax Thank you!

Device is now certified in Play Store as well.
[Google Pixel 7 Pro] Fentadroid:
Is it safe to enable systemless host module? On my pixel 3a i need a custom kernel like EK Kernel to do that, otherwise system is not stable....
[Google Pixel 7 Pro] PurppleMonkey:
hello,

I received my pixel 7 (europe) yesterday. I rooted it without any problem, however I hadn't used the latest version of the system (TD1A.220804.031), so this morning I tried with that one but without success! I remained in version TD1A.220804.009.A2 (i used panther version not the cheetah one !)

I realized that the "flas-all.sh" command (on mac) didn't fully execute, it just flashed the bootloader. So I put "sleep 20" instead of "sleep 5".

it allowed to execute the whole script but then I ended up with an error message "Your device is corrupt. It cant be trusted and may not be working properly"

And now it won't turn on. I no longer turn it on or enter bootloader mode. it's a black screen :(

Any idea what I could do please?
[Google Pixel 7 Pro] AmyClaraRose:
If you can't get into bootloader best bet is to contact Google
[Google Pixel 7 Pro] PurppleMonkey:
No no, i have the regular 7 not the pro ! This thread is more active than the P7 thread !
[Google Pixel 7 Pro] AmyClaraRose:
Yeah I misread for a second and corrected my previous comment you going to have to contact Google
[Google Pixel 7 Pro] Bxperiaz3:
I fixed my issue late last night. My windows file system wasn't showing extensions so I renamed it.img and was attempting to flash a .img.img like a total spoofer 😬 all sorted now and passing play store certification and safety net. Thanks to all for your patience
[Google Pixel 7 Pro] roirraW "edor" ehT:
@i5lee8bit I'm going to have to take some time later when I'm awake to absorb the information you gave. I did quickly scan what you wrote and I wanted to let you know that you're not alone on the Google Chrome sync issue. Mine has also technically worked but still re-prompted me for my password multiple times.

I use a different password for Chrome sync than I do my general Google account.

Thanks for confirming! I'll re-change the instructions again in a bit.

Yes, I have it enabled.

I'm really sorry to hear you're in this situation, but @minidude2012 is correct. If you've tried everything under the sun to get the phone in bootloader mode including using the power and volume keys to force turn out off and to try to get into bootloader mode, then going to Google is likely the only way out of the situation.

This happened from time to time to users on the Pixel 6 Pro for various reasons or due to mistakes, and that's what they had to do. They would typically be sent a refurbished phone, which sucks, but this close to launch, Google might not have any refurbished phones to send.

I definitely have zero experience with doing these things on Mac as well.

Good luck!

Ah ha! So often it's just something simple. That's awesome to hear, congratulations for figuring it out.

I may add something to the OP about that aspect of file extensions.

@Lughnasadh you may want to be aware of what the fix was since I believe you too tried to help @Bxperiaz3, but it's all running together and I'm on mobile right now. 😁
[Google Pixel 7 Pro] V0latyle:
I would recommend mentioning the new Play Integrity API and why passing it is not possible on an unlocked bootloader, as well as the modded USNF module that forces a HKA fallback to register a fake keystore. Going forward, this is going to be a particular issue for users who are expecting to pass SafetyNet - and probably do - but don't understand why newer banking/payment apps don't work.
[Google Pixel 7 Pro] V0latyle:
It depends on the kernel. This is an issue that started with Android 12 and the introduction of the Boot Image Header v4. Earlier Magisk patched boot images as well as most custom kernels didn't present valid image headers, which the system would then reject as corrupt. Magisk has been fixed; as far as custom kernels, the responsibility is on the developer to ensure they're using the proper boot image header format and syntax. It continues to be an issue in Android 13, with any device that follows the Pixel-ish partition layout. I believe a similar issue exists with Android 13 on Samsung devices, but those don't follow the AOSP format.
[Google Pixel 7 Pro] Ghisy:
Is the new Play Integrity API only for Android 12 and up? I'm still using the modded safetynet module on Android 11 and I can pass SafetyNet and use banking apps.

I see. I'm probably gonna keep both disabled anyway, just in case. I don't want to have to wipe the device when everything has been set up.
[Google Pixel 7 Pro] Lughnasadh:
For custom kernels, you can probably get away with disabling just verity (if even needed). Disabling just verity doesn't require a wipe. Disabling both verity and verification does require a wipe.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'll take a look at adding that information, thanks!

The instructions already link to the modded USNF, although that reminds me - I meant to link to and credit @kdrag0n's original, too. Thanks!
[Google Pixel 7 Pro] V0latyle:
No, the mechanism on which Play Integrity relies on for STRONG_INTEGRITY was implemented in Android 8.0, and uses Hardware Key Attestation as well as the Trusted Execution Environment to certify that operations performed on the device can be trusted. More information here. The "turning point" is with app developers - some developers, such as Google, are implementing support for Play Integrity in their apps alongside the legacy SafetyNet API. There will likely come a time when they end support for SafetyNet, meaning applications that rely exclusively on Play Integrity will not work on modified/rooted devices, devices with broken keystores, or devices running Android versions older than 8.0.

The reason why the modded SafetyNet module works is because it forces the device to use a "legacy" attestation scheme, where it's able to register a fake keystore to trick Play Integrity into passing BASIC and DEVICE attestation.

It's basically a question of time and whether they're willing to enforce STRONG integrity for their apps. When that time comes, our only option will likely be using modded versions of the apps themselves - which likely won't work because of the authenticated server side - or just go without. It's pretty much impossible to hack Play Integrity STRONG attestation because of the mechanisms involved - you can "fix" your device in such a way that it will meet BASIC_INTEGRITY and DEVICE_INTEGRITY, but the only way to meet STRONG_INTEGRITY is by running a completely unmodified Android 8.0+ OS on a locked bootloader.
[Google Pixel 7 Pro] roirraW "edor" ehT:
@V0latyle With your assumed permission, I'll just link to this post from the second post. :)
[Google Pixel 7 Pro] Ghisy:
Wow, thanks for the detailed explanation!

Man, that sucks though! When that time comes, I'll just use my banking stuff in the browser or on my computer. No way I'm giving up root! 🙅‍♂️
[Google Pixel 7 Pro] roirraW "edor" ehT:
You and me both! :)
[Google Pixel 7 Pro] xdagee:
How will I know if the Pixel 7/Pro I'm buying bootloader is unlockable, especially when it comes to the online stores? I won't have a feeling to check the hardware and the model number and whether 5G mwave support or not.
[Google Pixel 7 Pro] roirraW "edor" ehT:
See Post #2 and then come back if you have any more questions. :)

Edit: I'm not really sure unless you're able to order directly from the Google Store where you're at. If the listing says "Factory Unlocked" (this means Carrier Unlocked), then it might mean the same version that the Google Store sells which besides being carrier unlocked, can freely be able to have it's bootloader unlocked.
[Google Pixel 7 Pro] V0latyle:
The only way to be sure is to order a non carrier device through the Google store. If you order one on a carrier subsidy (Verizon, TMobile, etc) it's likely the bootloader will not be unlockable. You'll have to pay full MSRP, but that's the price you have to pay in order to use the device to its full potential.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yeah, the Google Store even has the Verizon variant available with 512 GB this year - I think last year, it was only available on the unlocked variant. I could be wrong, though. To be fair, Best Buy lists some of the factory-unlocked models, so as long as they didn't make any big goofs in their listings, they should be fine. No idea about other retailers, or around the world, especially in places where the Google Store isn't available to order from without someone in the middle.
[Google Pixel 7 Pro] V0latyle:
Same.

A little more detail: SafetyNet already has the ability to report hardware backed attestation:

But, for some reason, Google never did this. The major difference is that Play Integrity doesn't just rely on the device to provide secure tokens; it also depends on authenticated servers to do so:

Therefore, even if someone did manage to hack Play Integrity to be able to obtain signed results, they'd then have to somehow inject a "man in the middle" attack to ensure the server side returns the same results as well.
[Google Pixel 7 Pro] Lughnasadh:
Not necessarily bad, if true, but a bit disappointing...

"We purpose-built Google Tensor G2 for real-world use cases. Our final architecture, which includes 5nm, helped us reach that goal while increasing both performance and power efficiency. This approach also allowed us to add new capabilities while taking a step forward on machine learning with our next generation TPU with G2."--Google Spokesperson (apparently).

Google Tensor G2 is a 5nm chip, despite what the internet might say

Google has confirmed that the Tensor G2 processor powering the Pixel 7 and Pixel 7 Pro is built on a 5-nanometer manufacturing process.

www.androidauthority.com
[Google Pixel 7 Pro] Namelesswonder:
They already have the timeline, I and anyone else that generated API tokens for SafetyNet got this email beginning of the month. Also details the new response that SafetyNet will have next month.
[Google Pixel 7 Pro] V0latyle:
Would you mind copying this post into this thread?
[Google Pixel 7 Pro] xdagee:
Thanks for this update. I will definitely be on the look out.

If I should get you right all factory unlocked models are bootloader unlockable. unless those whom you purchase from the carriers, that you can't unlock the bootloader. I also read also that you can request from a carrier to unlock the bootloader. Which carriers are those. I would love if you can have them listed so it could be a guide. In countries where the pixel is sold through the Google stores.
[Google Pixel 7 Pro] V0latyle:
This is only really guaranteed if you buy direct from the Google store. Retailers don't always get model numbers right. In fact Google themselves have sent locked devices as RMA replacements.

There's not really a hard and fast answer for this. I've heard rumors that TMobile will unlock your device if you tell them you're a developer, but the reality is most carrier CSR's (customer service representatives) won't know what you're talking about, nor do the carriers have any established process to do so.
[Google Pixel 7 Pro] xdagee:
That's the trickiest part right now, The truth is that, unlike us, most people don't really care about this, don't even know about it, or will probably never hear about it.

Who's responsible? Is it the OEMs or the Network Carriers for unlocking the bootloaders of a device?
[Google Pixel 7 Pro] Bxperiaz3:
Yes thanks also to @Lughnasadh for the tips, you guys got me there in the end. Really appreciate it. Already loving the phone much more now.
[Google Pixel 7 Pro] rage302:
...yes i can confirm this as well. Play Store showes Device as certified. Kudos to @Displax.

Displax releases can be downloaded from here:

Releases · Displax/safetynet-fix

SafetyNet & Play Integrity API workarounds for Magisk - Displax/safetynet-fix

github.com
[Google Pixel 7 Pro] Displax:
Both my source with releases (github and xda) MOD USNF was updated to final variant, so no matter where to download.

About internal update link, I consider to live it original so that the module is updated to the original final version when it is released.
[Google Pixel 7 Pro] Lughnasadh:
Glad you got it going! 👍 When I noticed the different date on your flash-all.bat file, I did notice that some of your files didn't have an extension (e.g. adb didn't have .exe., flash-all was missing the .bat, etc.). I had thought that maybe you had the "Hide extensions for known file types" enabled in Windows Explorer settings, so didn't mention it because I didn't think it would affect fastboot being able to detect those files. Although it sounds like that may not be the exact reason for your troubles, in hindsight I should have mentioned it as it was a clue to solving your problem. Glad you caught it and resolved it 👍
[Google Pixel 7 Pro] wpswpatester:
Hello everyone, I own Pixel 7 pro EU version (TD1A.220804.031) and my device does not pass the CTS profile match. I've rooted it successfully without problem and I also installed the latest MOD version of Universal SafetyNet Fix.

A thing that I'm noticing is that every time I reboot the device, Google Play services is removed from the DenyList.

Any suggestions?

Edit: I pass it when the google play services is not on DenyList. But if it's not there, I can't download app like Netflix from Playstore. How can I fix it?

Edit 2: I 've fix it by myself : In zygisk DenyList instead of toggle all the packages under Google Play services, I've just toggled the `com.google.android.gms` in this way I was able to pass the safetyNet and also to download apps like Netflix on Google Playstore!
[Google Pixel 7 Pro] canibuz:
Mine is still saying device is not certified. I'm guessing I should clear data again on the play store?
[Google Pixel 7 Pro] JakeDHS07:
If you have everything setup and it's still happening then yes
[Google Pixel 7 Pro] bryan1854:
Happy Sunday All!

Looks like you all are making some great progress here. Don't hate me, but anything new for us Verizon folks?
[Google Pixel 7 Pro] JakeDHS07:
Not unless you've somehow managed to unlock your bootloader
[Google Pixel 7 Pro] kornball:
I am using the USNF test build and plan to install the MOD_2.0 sometime today. Pretty much everything seems to be working (YASNAC passes both basic/CTS and Integrity Checker meets all except strong integrity).

Only apps I can't get to seem to work are Netflix and Hulu. No matter what I do, I cannot install them from play store. I've cleared data for GPS and rebooted. Anyone have any suggestions? Should I clear data for both Play Store and GPS and reboot after I install the MOD_2.0?
[Google Pixel 7 Pro] JakeDHS07:
I would say yes. That should reset Play Store and make the apps available assuming all checks pass beforehand.
[Google Pixel 7 Pro] i5lee8bit:
Wow good to know (I guess) I'm not alone. Also sad to say that it started happening again this morning. Chrome won't stay logged in / sync'ed. Specifically, after rebooting, it'll offer me to sync to my account (that Android is signed into), and all I have to do is tap "I'm in". Seems fine. But then after a while (or just kill the app and open again), it'll act like sync isn't set up. The thing is, I CAN'T log back in. It just offers to add a new account. And if I type in my account email, it says I'm already signed in on this device (no sh!t!!). Is this the same thing that's happened / happening to you?

Btw, did you mean you use a different password or different account for Chrome sync? The first doesn't make sense to me lol.

And of course the other weird thing is how Google Pay (and I'm sure I'll find other things as time goes on) goes into a half-disconnected state as soon as the Chrome thing happens. The two are definitely related, no doubt about that.

One last thing to note is that all my passwords and addresses stay on the device, but my stored payment methods disappear. When i first reboot and *supposedly* sync Chrome to my account again, my saved payment methods all show up. But once the sync seemingly breaks, they're gone.

I've had weird issues before with background Google services, even after factory reset, and setting up 100% from scratch (no backup restore / data transfer) fixed it. But the fact I did that last night and the problem came back is driving me to insanity 😢

Edit: it may be worth mentioning, my Pixel 4 XL hasn't been wiped and is still set up. Nearly identically with the mods and setup (except Android 12 still). Also my Galaxy Tab S8 Ultra is heavily modded. Neither of them have this problem. I got to wondering, crap, what if my Google account is somehow messed up? But thankfully no issues with my Google account or Chrome on my laptops or desktop. So I'm pretty sure it's not my Google account itself. Something weird is going on specifically with this device it would seem.. just thought that may be worth mentioning 🤷‍♂️
[Google Pixel 7 Pro] kornball:
Thank you! In order to install the newer USNF version, I can simply install over previous in Magisk? No need to uninstall the test version first?
[Google Pixel 7 Pro] JakeDHS07:
Correct it will simply overwrite it
[Google Pixel 7 Pro] roirraW "edor" ehT:
As @JakeDHS07 said, no news for Verizon. Near the very top of my Post #2, I detail what anyone on particular U.S. Carrier variants of Pixels can expect including the following:

Verizon variants:

This sounds like delivering the news roughly, but rest assured there's no hate involved. Also, if there ever happens to be some widespread / not one-off (and free and legal) Verizon bootloader unlocking method, I will update the thread title, the top of the first post, and the Verizon entry in the second post because it will be hot news. Just don't expect there to be a change.

The only newsworthy item is that, from memory (it's been crazy busy in this Pixel 7 Pro section), exactly one person reported finding a fluke and being able to unlock the bootloader of their Verizon phone, but don't get excited - it wasn't a reproducible sequence of steps, and I could even be confusing it with a recent event for the Pixel 6 Pro - I can't recall for sure device forum I saw it in.

Before I forget to mention, I still need to look at the rest of your previous two detailed posts. I'm making progress but I have a bunch of real-life stuff to get done too, so I might not be able to read those in detail until later today or even tomorrow, but I will.

About the Chrome sync, maybe I'm not experiencing the exact same issue after all. Chrome itself has never indicated to me that it's not syncing. There have just been a couple of handfuls of instances where I went to use my auto-fill login information on an app I hadn't set back up yet on the P7P, and I get prompted for the sync password. I'm sure Google will fix it sooner or later. I haven't seen anything prompting me to tap "I'm in", although I know what you're referring to as that happens from time to time with my work account, which uses Google enterprise for everything.

Not a different account. This is a screenshot from Windows desktop Chrome which may make it clear what I'm talking about:

i.e. When I sign into Chrome / GMail for the first time on any new device whether it's desktop or mobile, that alone doesn't enable my Chrome/Google sync. I have to enter a different password for the sync to start working. That way if anyone does ever manage to bypass all my 2FA on my Google account, that alone won't enable them to access my passwords.

You're probably right. I hardly ever use Google Pay, so I can't report on that aspect.

I think I would just chalk it up to a Google bug/bugs, leave things alone for now and wait for Google to rollout a fix. I'm sure you're not alone, based on the steps you've taken to try to eliminate the issue.

That's correct, can just install over. It never hurts to hit the Remove button on the old and go ahead and install the new version, and then reboot, but it'll be the same result.
[Google Pixel 7 Pro] PurppleMonkey:
Thanks a lot !

There's something weird about the phone: it's hot like the processor is still running but no display! Do you think there is still hope? Wait until there is no more battery for it to turn off then load it to try to enter bootloader mode?

To be precise, before having a black screen I had the google logo and I managed to enter Fastboot mode. Then I came back and nothing, black screen!

I don't really understand what I did wrong.

I followed the tutorial, the only thing is that I'm on MAC and I have to change a few lines in the "flash-all.sh": I have to put "./" in front of the commands and for the flash the "Sleep 5" lines do not seem appropriate: The process stops at the first reboot. so I have to lengthen the time.