Question Not passing safetynet(Play Integrity API) on pixel 7

[manjaroid]

Here it is the screenshot

View attachment 5873515

For the Magisk binary you have stable 25.2, but for the app Canary 25210 is installed. They don't match and even if both were 25210 you'd still have problems. The app is likely configured to use the Canary update channel which would explain the Update button for the binary. So if you tap it and run the update you should end up with Canary 25210 for both, correcting the mismatch.

Stable 25.2 for both probably won't work out either. If you used it before and weren't passing integrity checks, you're not alone which is why Canary is recommended. It just needs to be the most stable Canary available which for now is 25206 and not 25210. On the other hand, if you're able to get stable working for you then go with that.

I suggest running the update to get the app and binary matched up. Then in the app uninstall Magisk along with restoring init_boot back to stock. i.e., Completely remove Magisk so that the phone is no longer rooted, then start over using Canary 25206. To ensure a clean installation, patch a fresh init_boot.img (from the factory zip of your running Android build) with the Canary 25206 app.

With 25206 the app's default update channel will be for Canary builds so you'll still see an Update button for the app because there are several releases after 25206 up to 25210. Don't touch that Update button and stick with what works until something better comes along. If you update to 25207 the app is known to crash and you'll be back to repairing Magisk. Releases after 25206 have an assortment of problems so avoid them. The only exception is 25209, maybe.

Edit:
Sorry, I messed up the two links. Better to get older Canary files from here:

Commits · topjohnwu/magisk-files

Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.

github.com

If your Pixel 7 runs Android build TQ2A.230305.008 (March), you can use the files attached to this post to get setup with Canary 25206. The zip contains the apk along with init_boot.img already patched by 25206. You just need to install the app and flash the img file with fastboot.

 

[andrea_x]

For the Magisk binary you have stable 25.2, but for the app Canary 25210 is installed. They don't match and even if both were 25210 you'd still have problems. The app is likely configured to use the Canary update channel which would explain the Update button for the binary. So if you tap it and run the update you should end up with Canary 25210 for both, correcting the mismatch.

Stable 25.2 for both probably won't work out either. If you used it before and weren't passing integrity checks, you're not alone which is why Canary is recommended. It just needs to be the most stable Canary available which for now is 25206 and not 25210. On the other hand, if you're able to get stable working for you then go with that.

I suggest running the update to get the app and binary matched up. Then in the app uninstall Magisk along with restoring init_boot back to stock. i.e., Completely remove Magisk so that the phone is no longer rooted, then start over using Canary 25206. To ensure a clean installation, patch a fresh init_boot.img (from the factory zip of your running Android build) with the Canary 25206 app.

With 25206 the app's default update channel will be for Canary builds so you'll still see an Update button for the app because there are several releases after 25206 up to 25210. Don't touch that Update button and stick with what works until something better comes along. If you update to 25207 the app is known to crash and you'll be back to repairing Magisk. Releases after 25206 have an assortment of problems so avoid them. The only exception is 25209, maybe.

Download Canary 25206

Download Canary 25209

If your Pixel 7 runs Android build TQ2A.230305.008 (March), you can use the files attached to this post to get setup with Canary 25206. The zip contains the apk along with init_boot.img already patched by 25206. You just need to install the app and flash the img file with fastboot.

I just wonna throw the phone out of the window!!!
I've done it all, but using your file Magick didn't even open.
I've downloaded the original ZIP from here, I've installed Magisk Canary 25206, I've patched the original init_boot.img, I've flashed it, but now YASNAC fails both, basic integrity and CTS profile match.

 

[simplepinoi177]

I just wonna throw the phone out of the window!!!
I've done it all, but using your file Magick didn't even open.
I've downloaded the original ZIP from here, I've installed Magisk Canary 25206, I've patched the original init_boot.img, I've flashed it, but now YASNAC fails both, basic integrity and CTS profile match.

I'm thinking you might be having problems executing certain things and/or sequence of events...

But it also seems that you are not resetting everything before continuing on. You should completely remove ALL traces of Magisk, patch the original init_boot.img (it might even be best flashing the Full Factory image flash-all; with "-w" removed of course) and start from very fresh scratch (in terms of Magisk and root; do not wipe your device). Then continue with installing Magisk Canary 25206, and then patching the stock boot.img, and further...

Have you thought of using Pixel Flasher. It works with Magisk canary builds, does all the extracting, patching, and flashing for you. And, if anything, the logs should be able to tell what may be flashing/going wrong where you might be able to get badabing2003 (OP/Dev/Creator) to tell you how/what/why it's going wrong (maybe with your specific device)....

 

[andrea_x]

I'm thinking you might be having problems executing certain things and/or sequence of events...

Have you thought of using Pixel Flasher. It works with Magisk canary builds, does all the extracting, patching, and flashing for you. And, if anything, the logs should be able to tell what may be flashing/going wrong where you might be able to get badabing2003 (OP/Dev/Creator) to tell you how/what/why it's going wrong (maybe with your specific device)....

Mmm...

 

[simplepinoi177]

Mmm...View attachment 5874169

It is safe -- 100s, maybe 1000s of people are using it. Anytime a program runs its own scripts and stuff, there's always risk at a false positives. If you check out his thread (in the link I gave), even for your device HERE, or his very active one in the Pro thread HERE, it is obvious that absolutely nothing malicious is going on by the program or the developer; only support and help through it. If you look at the the developer's responses, it's only on assistance (individual most of the times).
If anything, your concerns has been discussed HERE with assurances and responses by experts and by the developer himself.

You won't be able to find anyone that's used it to say that anything malicious (on their PC) has happened -- they might whine that it broke/hasn't fixed their Pixel devices, and that is subjective, but not malicious or "virus" in any way.

 

[andrea_x]

It is safe -- 100s, maybe 1000s of people are using it. Anytime a program runs its own scripts and stuff, there's always risk at a false positives. If you check out his thread (in the link I gave), even for your device HERE, or his very active one in the Pro thread HERE, it is obvious that absolutely nothing malicious is going on by the program or the developer; only support and help through it. If you look at the the developer's responses, it's only on assistance (individual most of the times).
If anything, your concerns has been discussed HERE with assurances and responses by experts and by the developer himself.

You won't be able to find anyone that's used it to say that anything malicious (on their PC) has happened -- they might whine that it broke/hasn't fixed their Pixel devices, and that is subjective, but not malicious or "virus" in any way.

Nothing, I gave it a try, but after it has done it's magic, YASNAC still fail the CTS profile match and I still can't install some apps. I'm lost!

 

[andrea_x]

Nothing, I gave it a try, but after it has done it's magic, YASNAC still fail the CTS profile match and I still can't install some apps. I'm lost!

I've factory resetted it, run Pixel patcher, but nothing...

 

[manjaroid]

I just wonna throw the phone out of the window!!!
I've done it all, but using your file Magick didn't even open.
I've downloaded the original ZIP from here, I've installed Magisk Canary 25206, I've patched the original init_boot.img, I've flashed it, but now YASNAC fails both, basic integrity and CTS profile match.

Assuming the phone is rooted, was Magisk configured?

- Install the modified safetynet-fix module discussed earlier
- In the Magisk app enable Zygisk & Enforce DenyList
- Configure DenyList (Play Store + other apps to deny)
- Reboot probably necessary

You'll also probably need to clear storage for Play Store and Play services in Settings/Apps and another reboot.

Sorry if my file(s) didn't work. I just installed it on another Pixel so no idea what went wrong.

 

[andrea_x]

Assuming the phone is rooted, was Magisk configured?

- Install the modified safetynet-fix module discussed earlier
- In the Magisk app enable Zygisk & Enforce DenyList
- Configure DenyList (Play Store + other apps to deny)
- Reboot probably necessary

You'll also probably need to clear storage for Play Store and Play services in Settings/Apps and another reboot.

I forgot about the Safetynet mod. I've installed and now YASNAC passes both the basic integrity and the CTS pofile match, but still, I can't install Data Transfer Tool (it says: Can's install Data Transfer Tool) and I can't even find some other (like CIEID) (I've added Google Play Store and Services to the deny list, clear cache and storage).
Other magic trick that I can try?

Sorry if my file(s) didn't work. I just installed it on another Pixel so no idea what went wrong.

Sorry??? For what? Are you kidding me? Thanks for all the tips you're giving me!

Edit: after another storage delete for Google Play Store and Services, I was able to find and install the app CIEID, but still not Data Transfer Tool

 

[simplepinoi177]

I forgot about the Safetynet mod. I've installed and now YASNAC passes both the basic integrity and the CTS pofile match, but still, I can't install Data Transfer Tool (it says: Can's install Data Transfer Tool) and I can't even find some other (like CIEID) (I've added Google Play Store and Services to the deny list, clear cache and storage).
Other magic trick that I can try?


Sorry??? For what? Are you kidding me? Thanks for all the tips you're giving me!

Edit: after another storage delete for Google Play Store and Services, I was able to find and install the app CIEID, but still not Data Transfer Tool

I knew it had to be something like that...It didn't quite make sense how yours was failing while most others were succeeding... USNF-Mod is vital...

At this point, since you got most everything you want, if the Data Transfer Tool is the only thing missing, why don't you just download it from APKMirror and call it a day; if it is truly the last thing.
But to my recollection, I don't think you could run the Google stock Data Transfer Tool unless you were initially setting up the phone (from factory or a wipe)...

 

[andrea_x]

At this point, since you got most everything you want, if the Data Transfer Tool is the only thing missing, why don't you just download it from APKMirror and call it a day; if it is truly the last thing.
But to my recollection, I don't think you could run the Google stock Data Transfer Tool unless you were initially setting up the phone (from factory or a wipe)...

It's not that I really need that app, but it was a check before I transfer everything from the other smartphone (Pixel 7 Pro...I know, but it's too big for me!) and be sure that everything works smoothly.
Maybe I'll give it a try!

 

[andrea_x]

In the end I switched to the newly rooted Pixel 7 and everything works.
Thanks @manjaroid and @simplepinoi177