yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Ultimoose:
Try using auto complete in the shell? i.e. type fastboot flash init_boot mag [hit Tab]

Or drag and drop by typing fastboot flash init_boot[space] and then drag the file from the folder into the shell.

If none of that works then yes it makes no sense. :(
[Google Pixel 7 Pro] WorldOfJohnboy:
Already did the data/cache wipe. Camera app at version 8.6.263.471358013.15 continues to blow up, but if I go back to 8.6.263.459370420.10 it's fine (complete with all the P7P features). Guess I'll have to just pause auto-updates until new Firmware is out and try again.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Apologies if already asked, but you're using the latest Platform Tools (ADB / Fastboot), correct? And you killed any ADB session that's still listed in task manager, in case that was using an old version?
[Google Pixel 7 Pro] WorldOfJohnboy:
I had to run through MagiskHide Props Config to get CTS to go Green... (Used Pixel 6 Pro).
[Google Pixel 7 Pro] roirraW "edor" ehT:
From what I read, MagiskHide Props Config is not needed any more (even on the Pixel 6 Pro, at least with @Displax modified version of USNF available from their XDA post or GitHub (v2.3.1-MOD). I just tried it and cleared the data and cache for both Play Protect Service and Play services, and rebooted yet again, but CTS profile match still fails on the Pixel 7 Pro in YASNAC.

Thanks, though.
[Google Pixel 7 Pro] ScottIsMyName:
Can anyone confirm that you're able to use Google Pay/Wallet with your phone in a rooted state? Looking to make the plunge today. Not really worried about integrity checks if mobile payments are working
[Google Pixel 7 Pro] roirraW "edor" ehT:
There have been several users who reported yesterday in this thread that GPay and Wallet were working, even with our limited SafetyNet mitigation, but I don't know if they've been working for every single person.
[Google Pixel 7 Pro] daridima2:
I did those same things, but on mine it doesn't work, but I no longer have pixel 6 pro like you, but pixel 7 pro and the new build released yesterday
[Google Pixel 7 Pro] hochoch:
I have it installed on my 6a which is a13. Setting up my p7 now... Should I skip this? I'm showing version 1.8.1 for the boot loop protector module
[Google Pixel 7 Pro] Gordietm:
Yes, GPay and Wallet are working for me.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I would skip it permanantly. :) Just use Safe Mode when you absolutely have to, and always disable all Magisk Modules before each firmware update.
[Google Pixel 7 Pro] hochoch:
Good advice... I usually leave all enabled and yolo it! 😋
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks for yet another confirmation. This has now been reported frequently enough, I added a note to my Post #2 instructions that despite the certification issues, those at least are still working.
[Google Pixel 7 Pro] ScottIsMyName:
Awesome....so you actually used it in a store, and not just setup the cards right? Just double checking since I use this feature a LOT :)
[Google Pixel 7 Pro] Gordietm:
Yes, I used one of my credit cards at Starbucks and no problem. Your bank might be different, I'm in Toronto, Canada.
[Google Pixel 7 Pro] Ultimoose:
Just a data point in case it helps anyone else -

Unlocked the bootloader first thing last night

Came here to check rooting steps this morning

While reading let it try to get the OTA update just out of curiosity, it failed as it always did for me on the p6p with an unlocked bootloader.

DL'd 031, extracted as usual, extracted init_boot per new guidance.

Ran Flash all but it failed due to a 'unsupported version' error, I didn't capture the error unfortunately.

Updated ADB tools. Same error.

Didn't feel like troubleshooting more, went to flash.android.com and had it push 031 to me, no problems but made sure to uncheck the Lock Bootloader button. Let it go ahead and wipe again, no reason not to as I hadn't set anything up yet. Note if you had an active ADB session make sure to do an adb kill-server or the google browser tool can't connect.

Still unlocked, verified 031 successfully installed, got dev mode again after the wipe.

Installed magisk 25.2 with adb install

Patched init and installed it.

Turned on magisk settings, hid magisk, installed current safety net fix as of today even though it's not 100% working, added google stuff to deny list as usual.

Ran the set up/restore by connecting the two phones together. Mildly interesting the cable I've used to connect to my pc didn't work to connect the two phones together but another one worked fine. Cut bad cable and tossed it.

Play store shows Netflix as not compatible with my device as expected.

Play Protect is showing not certified.

Wiped Playstore, no effect.

Now I guess we wait for a SN fix. :)

Overall happy with the phone. Not a major updgrade from the 6 but they practically paid me to take one in exchange for a 6 so why not.
[Google Pixel 7 Pro] WorldOfJohnboy:
I have Pixel 7 Pro. CTS would not go green until I ran MagiskHide props config steps and changed the key to be Pixel 6 Pro. Everything (but my camera) is now working for Magisk and CTS is green in YASNAC
[Google Pixel 7 Pro] roirraW "edor" ehT:
I think I see what you're saying. I'll have to check it out in a bit. Thanks.
[Google Pixel 7 Pro] NCVol:
I rooted and installed the modded USNF and wallet will not let me set up cards. Says "this phone can't be set up to tap to pay". YASNAC fails all checks.

Just wanted to provide another data point. If anyone has ideas I'd be happy to try them.
[Google Pixel 7 Pro] simplepinoi177:
This is a good thing to confirm...

My experience with Google Pay on my rooted Pixel 5 early-on was I was able to run the app and successfully add and activate cards in my digital wallet (which I was not able to do in the past on rooted devices before mods were patched; i.e. Google Pay would detect root or it wouldn't let me add cards because of root/security issues or it would let me add cards but enabled for in-store purchases), but when I went to pay, the card reader would detect my Google Pay and info was exchanged through the NFC, but for whatever reason, an error would pop up on Google Pay that would make the transaction not go through.

So, tl;dr, it's good to confirm that it actually can make transactions at a store location, because I've had it where it can successfully open the app, add the card, activate the card for in-store purchases, everything looks perfect, and it still crap out in the end...
[Google Pixel 7 Pro] badabing2003:
I wonder if instead of using init_boot.img you actually use the ramdisk.cpio extracted by Magisk, if that would work.
[Google Pixel 7 Pro] Namelesswonder:
@roirraW "edor" ehT

Magisk already supports init_boot, and has supported it since v24.3. There is no need to file an issue, it's been possible since March 3rd.

And it does work on the Pixel 7.

[nameless@5900x:~]$ adb shell ls -l /dev/block/by-name/init_boot_a
lrwxrwxrwx 1 root root 16 2022-10-14 12:19 /dev/block/by-name/init_boot_a -> /dev/block/sda11

As for doing OTAs, installing to the inactive slot should work.

I already covered that in my original post. You can't use ANY boot.img with a ramdisk, fastboot can't do anything with a ramdisk if it is expecting the boot.img to already have a ramdisk. You can only use a ramdisk if you are passing in a raw kernel binary, ramdisk, dtb, and second stage. I tried everything from concatenating together the various ramdisks to using gzip/xz/lz4/lz4_legacy, the phone doesn't want to boot the crafted boot.img by fastboot.

After looking in the Magisk code it appears that if it is patching an image that contains the kernel (boot.img) it will also patch the kernel to force it to load a ramdisk, so I'll have to look at that next.
[Google Pixel 7 Pro] Annie the Eagle:
Okay cool so for OTA we just install to inactive slot as usual?
[Google Pixel 7 Pro] WorldOfJohnboy:
To be clear, I follow the steps from this post: CTS profile match Fix

Specifically:

So on the second to last step, I chose Pixel 6 Pro as I knew that one had Android 13 and closely matched (the P7P is not available yet I guess). I'm wondering if that's why my Camera app is FC'ing, but I have a workaround and my Company's Microsoft apps are no longer saying my P7P isn't compliant...
[Google Pixel 7 Pro] Namelesswonder:
Yes, the only addendum to be made is that a script will need to be made to backup/restore the init_boot partition so update_engine doesn't fail when it is checking if partitions have been modified. Kernel Flasher could be updated (if it hasn't already) to perform the same function.
[Google Pixel 7 Pro] Annie the Eagle:
So we shouldn't try to do any OTA if there is one because magisk install to inactive slot might cause problems? Or am I missing something. Sorry, I've only just gotten back into the rooting scene recently :)
[Google Pixel 7 Pro] Namelesswonder:
No problems are going to be caused, if the Magisk patched init_boot isn't restored with a stock one then when the OTA update tries to start it will just stop and tell you it can't perform the update.

If Google were to drop an OTA today then no, you can't take the OTA, because it just won't let you until you restore the stock init_boot.

Luckily just backing up and restoring a partition is extremely simple, so a script could very easily be made to do it, or an app like Kernel Flasher could be updated to do it, once you have root it can all be done while running inside Android.
[Google Pixel 7 Pro] LLStarks:
Magisk Canary, USNF, Shamiko, Zygisk enabled. GPay and Chase fingerprint work. Basic Play Integrity passes but Device Integrity fails.

Good enough, I guess. What do I need Device Integrity for?

I've also dived into the modem with Network Signal Guru. Looks like we can lock 5G modes and bands now. Locking 4G bands above B39 is still broken.
[Google Pixel 7 Pro] stroke55:
BTW I factory reset my P7P today and rerooted it using the unmodded USNF 2.3.1 without Shamiko. It was the same result as with using @Displax modded version (device_integrity and CTS profile both fail, Wallet working, Netflix showing up in the Playstore). So at the moment it doen't seem to make a difference if you use the modded or the original version.

The Paypal app seems to recognize CTS or device integrity failure and is asking for a SMS code whenever I open the app. Also some banking apps are failing but some of them work.
[Google Pixel 7 Pro] LLStarks:
One thing to do is clear data/cache and force stop Play Store to make the "device is not certified" go away. Could help with apps that read that status.
[Google Pixel 7 Pro] stroke55:
Your phone is certifed in Playstore?

Edit: Are you using the modded USNF?
[Google Pixel 7 Pro] LLStarks:
No, I should. I forget about it.
[Google Pixel 7 Pro] 96carboard:
Maybe. Give it a try?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Something is indeed wrong if YASNAC fails all checks. It should at least pass Basic Integrity. Try wiping data and cache of Play Store and Services apps, then reboot.
[Google Pixel 7 Pro] badabing2003:
I wish, I don't p7 or p7p.
[Google Pixel 7 Pro] swieder711:
Can you let us know what edits you made with MagiskHide Props Config to get CTS to go green?

I am at this point
[Google Pixel 7 Pro] Namelesswonder:
I already covered it in my post, it doesn't work.
[Google Pixel 7 Pro] ZerkerEOD:
I can't get Netflix to show. I cleared cache and storage on the play store but when I open it again, I am already logged in.
[Google Pixel 7 Pro] swieder711:
I did the following

Restart your Phone!

- Launch a Terminal of your choice (e.g. Termux, Android Terminal Emulator, ...).

- Type 'su' (enter) and agree to the root dialog.

- Now type 'props' (enter) ...

... select '1' for Edit device fingerprints

... select 'f' for Pick a certified fingerprint

... select a vendor of your phone, picked Google

... select your phone (if available) or a phone which is next to your phone with your installed Android version, picked Pixel 6 Pro

- After selecting the fingerprint for your device, and when the program ends, reboot your device

I still get CTS profile match failure. (sad face).

EDIT: To undo the device fingerprint change, do I need to reflash the .31 release or is there an easier way?

EDIT: I use the "reset all" option which hopefully reverted back to the original fingerprint.
[Google Pixel 7 Pro] ScottIsMyName:
I'm also not able to add cards to Google Wallet. Play store seems to not say uncertified for a little bit and then goes back to uncertified after a while.

Not sure what I'm doing differently than others.

I have tried clearing play store, play services, play protect services data/cache a million times, rebooting, etc.

I have all of the apps configured with zygisk on my deny list and I'm using the displax mod.

Any suggestions would be welcome.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Same result here.
[Google Pixel 7 Pro] simplepinoi177:
it seems it's not working for some people...

just wondering, are you on the newest .031 ota update (as opposed to .009 OOTB)? If not, I wonder if that's why, and might explain some things as well as it might be something good (as a warning) to put up on the OP (again, if in the end that's the reason...)
[Google Pixel 7 Pro] ScottIsMyName:
I'm on .031 and can't get it to work :(

edit: I re-read the original post and realized I didn't have Google Services Framework checked in Magisk Hide. I checked that, cleared all data again for all of the google apps and then rebooted. I was then able to add all of my cards
[Google Pixel 7 Pro] swieder711:
I'm on .031 too and cant pass CTS
[Google Pixel 7 Pro] roirraW "edor" ehT:
Actually, I think that one's my bad. It won't stay checked. When you back out of the DenyList and go back in, it'll be unchecked again. Adjusting OP now.
[Google Pixel 7 Pro] ZerkerEOD:
That's a known bug happened in my last phone too. It is still denied but for some reason it just uncheckes itself.
[Google Pixel 7 Pro] davidgro:
I have a guess about these last few posts: Maybe the modded USNF is overriding the selection in MHPC? Try a not modded USNF (or none at all?) perhaps?
[Google Pixel 7 Pro] ScottIsMyName:
No, that's Google Play Services that won't stay checked (at least for me). Mine is Google Services Framework (com.google.android.gsf). Might just be a coincidence, but that shows checked for me even after a reboot, and wallet and stuff is working as expected
[Google Pixel 7 Pro] johnha:
I also forgot to check this. For system/google apps, I have these checked now:

- Google Play Services

- Google Play Store

- Google Services Framework

- GPay

Are there others that I should check as well? Like Google Support Services or any others?
[Google Pixel 7 Pro] WorldOfJohnboy:
Yes, I flashed the full .031 after unlocking. Then I rooted and ran into my CTS problem, which wouldn't let me into my corporate (Mostly Microsoft) apps.
[Google Pixel 7 Pro] simplepinoi177:
Thanks for responding...

Then that can't be the reason/difference why your CTS is green checked while others isn't...
[Google Pixel 7 Pro] ScottIsMyName:
Those are the ones I have checked....after you checked those, wipe the app data for Google Play store, google play services, and then reboot....see if you can get Wallet to work now.

I STILL can't get Netflix to install or show in the play store. Sideloading it results in Netflix stalling on the splash screen.
[Google Pixel 7 Pro] WorldOfJohnboy:
I have no Idea, to be honest. I basically installed Magisk (normal, not Canary, btw) and copied all of my settings and modules and deny lists from my Pixel 6 Pro. I have MagiskHide Props Config, Shamiko, Systemless Host and Universal SafetyNet Fix modules all turned on and I followed the same exact steps as @swieder711 did in Post #442 and got Green on CTS.
[Google Pixel 7 Pro] ScottIsMyName:
Can you possibly screenshot your module list?

Are you spoofing a device fingerprint in props config?

Are you using displax safetynet fix mod?

In magisk hide, I assume you have your list, but not enforcing it since you're using Shamiko?
[Google Pixel 7 Pro] LLStarks:
There should be nothing in your denylist and it should be disabled. Only add if you are using Shamiko, and only for your banking apps.
[Google Pixel 7 Pro] mcj108:
Just an FYI I think the modified SaftyNet module breaks setting up Wear OS devices. You can set it up but copying Google accounts to the watch does not work, which can really limit what it can do. This is made worse by the fact that clearing data on Play Services also unpairs Wear OS devices, which means a factory reset on the watch.

You can get both working, you just need to set up the watch after clearing Play Services but before opening Wallet/enabling the module.
[Google Pixel 7 Pro] WorldOfJohnboy:
Yes I am "spoofing" a Pixel 6 Pro fingerprint via props config as per my earlier comment. Here's my modules screenshot.

Also not enforcing the denylist. That shouldn't have a bearing on the CTS passing though.
[Google Pixel 7 Pro] shiftr182:
Has anybody tried patching the init-boot.img & the actual boot.img? I wonder if patching both would have any effect on how USNF works within the system? I would try, but haven't received mine yet.
[Google Pixel 7 Pro] LLStarks:
You don't need to spoof.
[Google Pixel 7 Pro] V0latyle:
Not a bug:

^^^^ USNF overrides the DenyList selections.
[Google Pixel 7 Pro] ScottIsMyName:
He seems to be the only one that is getting a checkmark on CTS profile match though, so?
[Google Pixel 7 Pro] WorldOfJohnboy:
Pixel 7 pro is not a choice in the props edit, so I had no choice
[Google Pixel 7 Pro] canibuz:
Shamiko and the USNF + Spoofing might be the key here. Just got my phone in and will be testing soon. I think it's been asked before but I didn't see an answer.

For USNF are you using the standard version or modded?
[Google Pixel 7 Pro] WorldOfJohnboy:
I don't honestly remember, but I think I was standard.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes, that's standard. This is the modded one.
[Google Pixel 7 Pro] Namelesswonder:
I have tried every combination of modules and even gone so far as to use newer fingerprints from a Pixel 6 Pro, along with wiping the phone 5 times, and I still can't get CTS profile to pass.

Do you mind running the commands here and attaching the file or putting it on pastebin?
[Google Pixel 7 Pro] swieder711:
Attached is the props file from my P7P which is rooted.
[Google Pixel 7 Pro] swieder711:
Gotcha. My bootloader is unlocked. Does my props file show as locked?
[Google Pixel 7 Pro] davidgro:
I wasn't referring to the DenyList - although I guess it does that too. I meant the fingerprint spoofing - as I understand it, the modded USNF specifically spoofs the fingerprint to the Google Play Services process (which contains SafetyNet and its successor) overriding the global spoofing that MHPC does.

So when selecting the Pixel 6 Pro in MHPC, I think if using the modded USNF, that's not what SafetyNet specifcally sees, so an unmodified USNF is needed.

If I'm right, then what would be nice to have is a new version of the mod that spoofs P6P for now, and maybe later some working fingerprint of P7P, but in the meantime, just using unmodified USNF seems to have worked for at least one of us. And I'll try it for myself when I have a chance (was waiting on setting up my phone until this was worked out)
[Google Pixel 7 Pro] Namelesswonder:
It does

[ro.boot.vbmeta.device_state]: [locked]
[ro.boot.verifiedbootstate]: [green]
[vendor.boot.vbmeta.device_state]: [locked]
[vendor.boot.verifiedbootstate]: [green]

But this does confirm that the init_boot partition is checked.

[ro.boot.verifiedbooterror]: [ERROR_VERIFICATION]
[ro.boot.verifyerrorpart]: [init_boot]
[Google Pixel 7 Pro] V0latyle:
I'm not sure if the USNF module affects the fingerprint. I do know that it forces a sort of "legacy mode" that bypasses hardware key attestation, so that it's possible to pass device and basic integrity.

You can indeed try the unmodded USNF but I don't think it will do any better. Part of the reason is because SafetyNet is going away, and now Play Integrity, which implements some stricter hardware checks, has to be fooled in a different way.

The "old" USNF worked just fine for SafetyNet alone, but not Play Integrity.
[Google Pixel 7 Pro] Namelesswonder:
And in case anyone wants to know, it doesn't matter. Magisk doesn't touch the kernel inside boot.img and it slipstreams a small ramdisk. However, Magisk doesn't hijack the init process when trying to boot this patched boot.img, which means this ramdisk inside boot.img doesn't get loaded.

What this means is that in it's current state, fastboot boot won't ever be able to boot the phone with a custom supplied ramdisk, as the phone will just ignore any ramdisk included in boot.img. You can still boot custom kernels, but only if they can be consolidated entirely to just the kernel binary inside boot.img, and most don't.
[Google Pixel 7 Pro] NCVol:
I get basic to pass after wiping the data from those apps but CTS profile check still fails. I think that's the same boat everyone is in.

But wallet let me set my cards up again, which was my main issue.
[Google Pixel 7 Pro] bigknowz:
Why is there so much focus on CTS? More important to be able to use gpay.

Also seems like overkill and maybe conflicting setups with USNF and other modules. Is there a consistent setup that has gpay working?
[Google Pixel 7 Pro] manueltimz:
is the lsposed working on A13 P7/7pro?
[Google Pixel 7 Pro] Namelesswonder:
Small transcript from a post I've just made.

I've dug into the files and I've found that 32-bit libraries are still included with the phone. And not just the libraries, but even zygote32 is still on the phone, which is what starts 32-bit processes.

Turns out that ro.zygote is set to zygote64 which only launches zygote64, so no 32-bit processes can be started. If ro.zygote were to be set to zygote64_32 then zygote32 will be launched alongside zygote64.

I haven't tested changing it yet, as I've got things to do tomorrow and I need actually set up my phone now, but if the property were to be set before the init scripts start then it's possible that 32-bit support was just one change away. Unless Google made changes to the package manager, will have to test at some point.
[Google Pixel 7 Pro] MetroWestMA:
I would also add that recent phones like he OP 10 Pro were not able to overcome DRM Blocking, so Netflix, Peacock and other streaming services can't be installed and / or won't run, so that is also a priority too. The Pixel 6 Pro rooted has no issues running anything.
[Google Pixel 7 Pro] Displax:
Please test this UNSF build. Should be passing basic/device integrity.

Use updated version from main post instead
[Google Pixel 7 Pro] whatsisnametake2:
now this is encouraging!! hope it works!
[Google Pixel 7 Pro] rrusek:
Working!
[Google Pixel 7 Pro] NCVol:
It's working for me and has CTS profile match
[Google Pixel 7 Pro] simplepinoi177:
Amazing! Thank you for your continued work on this...

I have a feeling this post might become the new UNSF-MOD build that will be referenced just like your infamous post #1,820 had become!
[Google Pixel 7 Pro] canibuz:
Talk about an epic turn around time. 👏👏👏
[Google Pixel 7 Pro] Namelesswonder:
Do you have anywhere to donate something to you? You really deserve it for the effort you've been putting in the past several months.