[MODULE] Fix CTS Profile Match Fail – Play Integrity Fix

UPDATE – JANUARY 2024 – NEW ZYGISK MODULE BY CHITEROMAN

Thanks to chiteroman for this module, which can fix “ctsProfileMatch” (SafetyNet) and “MEETS_DEVICE_INTEGRITY” (Play Integrity). It is worth mentioning that this module cannot pass “MEETS_STRONG_INTEGRITY.” As per the developer, Zygisk is mandatory and Shamiko is not needed.

Choose one of the following recommended setups before you start using this module – 

DOWNLOAD MODULE BY CHITEROMAN

As mentioned on the “wiki” page of this module, for the Xiaomi EU Custom ROM, the developer recommends using the latest stable version and installing the latest APK which inbuild the fix. If you are rooted and are using Xiaomi EU Custom ROM, you have to uninstall the module by Chiteroman and add GMS main and unstable processes to the deny list to avoid DroidGuard detecting root.

If you still want to install this module on the Xiaomi EU Custom ROM, you have to uninstall the updates for the “XiaomiEUInject” app and then install this module.

We will highly recommend you to first go over this “wiki” page of the module before you install it.

You can read more about this module on this XDA Thread.

UPDATE – AUGUST, 2023 – ALTERNATE METHOD FOR CTS PROFILE MATCH FAIL ISSUE

Some users who followed our previous guide reported that the CTS Profile Match Fail issue still occurred with their devices. We explored more and found another way to fix the issue if the previous guides did not work. The credit goes to this thread on GitHub.

A user named “Displax” has created a modded version of the SafetyNet fix by kdrag0n. This mod works in almost all the devices on which the original fix doesn’t work.

DOWNLOAD SATEFYNET FIX MOD

As for the installation steps, simply install this modded module in the Magisk Manager and enable “Zygisk” in the settings.

Try the older mod version if the latest version is not working for your device.

UPDATE – JANUARY, 2023 – UPDATED SAFETYNET FIX BY kdrag0n (Magisk 24 and newer)

Kdrag0n released a new version at the beginning of 2023, and here are the highlights of the v2.4.0 – 

  • Play Integrity bypass without breaking device checks or causing other issues
  • Disabled use of hardware attestation on Pixel 7 and newer (@anirudhgupta109)
  • Updated instructions for newer Android and Magisk versions
  • Better debugging for future development

Kdrag0n mentioned that he wanted to ensure this module wouldn’t cause unnecessary breakage. The spoofing will happen dynamically at runtime and only when necessary, minimizing the adverse effects.

DOWNLOAD UNIVERSAL SAFETYNET FIX v2.4.0

UPDATE – JUNE 2022 – UPDATED SAFETYNET FIX BY kdrag0n (Zygisk only)

After almost six months, Kdrag0n has released the new version of the SafetyNet fix, and this one only supports Zygisk (Magisk 24 and newer). Here are the highlights of this new version – 

  • Fixed fingerprint on OxygenOS/ColorOS 12
  • Support for Magisk 24+ module updates
  • Restored support for Android 7

DOWNLOAD UNIVERSAL SAFETYNET FIX v2.3.1

UPDATE – DECEMBER 2021 – UNIVERSAL SAFETYNET FIX BY kdrag0n (Zygisk and Riru versions)

kdrag0n has released new versions of the Universal SafetyNet Fix, both Riru and Zygisk versions.  So what to choose?

Well, for those using Magisk Canary, go with the Zygisk Version

For those using the stable Magisk, go with the Riru version. Remember that if you go with the Riru version of this universal SafetyNet fix, you must install the Riru module through Magisk Manager.  

Here are the links to the two versions – 

DOWNLOAD UNIVERSAL SAFETYNET FIX v2.2.1 (Zygisk)

DOWNLOAD UNIVERSAL SAFETYNET FIX v2.2.1 (Riru)

Android versions 7–12 are supported, including OEM skins like Samsung One UI and MIUI.

CONCLUSION

This detailed guide was about fixing the CTS Profile Match Fail Error or Magisk Basic integrity False error even with Magisk installed. If the steps mentioned above don’t work, you must start from scratch, i.e., flash Stock ROM, install TWRP, flash Magisk ZIP, and do the same thing again. Did the steps work for you? Do let us know via the comments section.

What is CTS profile mismatch?

CTS means Compatibility Test Suite & CTS Profile Mismatch is an error that causes SafetyNet check to fail, even if you have Magisk on your device.

What is the SafetyNet Check?

Google Developed SafetyNet & it is an API (Application Programming Interface) that is used to detect if a certain device is in a good state or not.

How Do I Fix How do I fix Magisk SafetyNet?

1. Use MagiskSu2. Try unSU3. Turn OFF USB Debugging4. Set Selinux Back to Enforcing5. Try a Custom Kernel

How do I Enable Magisk Hide?

Open Magisk Manager App, then swipe from the left & select Magisk Hide. Now, you can turn on and off it for certain apps.

Show Comments (37)
  1. Hey Arvind, need some help here. I installed Resurrection Remix in my Moto G4 Play and don’t know what to do for passing the Safetynet. Do I have to change my rom or something? I only want to install Netflix.

  2. I am on a Samsung Galaxy Note 5. I have tried everything in your list except the Franco Kernel since it doesn’t work on the Note5. I am running the LineageOS 7.1.1 by RaymanFX. Still getting “ctsProfile: false” in Magisk Manager. Any suggestions?

  3. thanks for the guide. for me i think it was just a matter of enabling magisk hide, after an update and re-root that option was not enabled. I am not sure but i think it was enabled automatically the first root. I also cleared play store data.
    -all’s right with the world now.

  4. thanks for the post
    it works for me the old method used riru and edexposed

    should i uninstall all of this after make magisk work or not..?
    once again thanks for the effort

  5. Method at top of this page did not work. Pixel 2XL, latest build of 11.

    Magisk otherwise looking good

    ctsProfile still fails

    Phone is otherwise operational; root and Superuser App verified OK

  6. “Next, open Magisk Manager & swipe from the left side. From there, select the “Downloads” option.”

    Magisk doesn’t have a UI where swiping does anything.

  7. I have samsung galaxy s20 5g (sm-g981bd/s) 2020

    This site has been the best for instruction in order to make it SUCCESS in the Mariska safetynet.

    This worked brilliant followed instructions and valaaa.

  8. Pixel 2 on stock image on A10 was fixed by using the latest version – safetynet-fix-v1.1.1.zip. Thanks for posting your January update!

  9. Confirming that I was able to get a pass with Magisk 24.1 (8.0.7 Manager) on a Motorola G7 Power (ocean) running Revenge 4.0 (Android 11, Jan 24 2021 Build), with NikGapps-R Core (Also Jan 24 2021).

    My first attempt was to use the Magisk-Hide module, that didn’t work
    Second attempt was to use the SafetyNet Fix v1.11, that only passed Basic Integrity but not cts
    Third attempt (while keeping the last two) was to do the props config step just after, that passed completely (I picked 16 Motorola, then 16 again for Motorola G7 Power 9/10, and picked Android 10 for the final step, as only 9 and 10 were options).

    Nutshell : MagiskHide module, Safteynet Fix v1.11, Props with Termux (before the 2020 update), picking Motorola G7 Power 9/10 and Android 10.

    I cleared cache and data for the Google Play Store app, and it now starts showing and installing apps that would normally be hidden without passing SafteyNet such as Netflix, etc.

    1. Cheers…I’m running stock Android 10 on the same phone as you and I was able to pass safetynet using the terminal method cause the g7 is listed…no other method worked for me

  10. Bravo! SafetyNetFix 1.1.1 worked perfectly on fully-patched and updated Pixel 2XL. We’ll see if it “sticks.” Many thanks!!

  11. I did the first few steps (magical hide, safety net fix,BusyBox) I didn’t found Mi note 10 lite on list of fingerprints but I tried an Mi note 10 Europe, after reboot magisk didn’t looked liked it was fixed (got an error) but gPay is working just fine (I got custom ROM spice os and it has custom kernel called Vantom, don’t know what fixed it, just leaving comment if anybody got same phone 🙂

  12. Thank you so much!
    I tried so many things, which even broked my phone. And this worked, only after enabling this module and reboot.
    First time since yeqrs with safety net. THANKS!

  13. Hi,

    I installed the zip as recommended. After reboot, the phone (Samsung S9+) asked me for the pin on startup to enable the fingerprint unlock feature. So far, so normal.
    But then it locked itself within 1 to 2 seconds telling me to enter the pin to unlock the fingerprint feature RIGHT AFTER STARTUP. Startup again? Yes, the phone was running normal but “thought” it’s still right after bootup and it’s the first time to unlock the screen.
    It was not easy to disable the module again having a time frame of 1 to 2 seconds. Finally it worked. Before uninstalling I checked the Safety.net status which was passed. Now, after uninstalling the phone works as before: Safety.net check failed

    Anyone experiencing the same? Is there any cure for this?

  14. I spent 3 days trying to fix this issue, tried null byte patching the safety fix:
    https://github.com/kdrag0n/safetynet-fix/issues/6#issuecomment-764129632

    However in the end the fix was stupid simple – select a different fingerprint from MagiskHide Props Config. I selected Google Pixel 4 and it worked. I have a J730F phone so I always selected J730F, which didn’t work.

    Hope this helps someone.

  15. well…, for me the september fix doesn’t work on the galaxy S9 phone. But, if I want to start with fresh installation, could you please describe the steps?

  16. Thanks for the awesome help! In my case (this might be a coincidence) since I followed the steps (about 4 days by now) the moisture detected alert had been on and so I haven’t been able to charge my phone with a wire (I have cleaned the port thoroughly). Please let me know if anyone else has encountered this issue.

  17. I followed every step on the September 21 update precisely and found everything like a charm. But sadly after the last reboot, the ctsProfile still fails.

    bq Aquaris X Pro 128GB wirh Lineage 18.1 nightly-09-11-21 with openGapps Nano

    Any advice?

  18. I rooted my new OnePlus 8T with twrp and Magisk but safetynet keep failing. After following the instructions to install riru, it fixed the issue and it is now passing with flying colours.
    Great work!

  19. Hi,
    I did all with my OnePlus 5, Lineage 19.
    Magisk 25.2 and SafetyNet 2.4.0.
    But I still have issues.
    It passes and I configure apps like Wallet.
    After hours or if I restart the phone it resets all denylist and the apps stop working again and I have to perform the process another time.
    Did I miss anything? Do you know if it is normal behavior?
    Many thanks in advance!

  20. I tried following the steps exactly for Riru but the following steps:

    First, go to Magisk and install the Riru Module. Once the installation succeeds, come back to the modules page. Do not reboot yet!

    Next, install the LSPosed Module. Once that installs successfully, reboot your phone. This is important! Do not reboot in the first step.

    Once the phone reboots, you will see a new LSPosed app installed.

    I do not see LSPosed app at all.

    Please advise what now?

    Phone: oneplus A6003
    Android Version 13
    LineageOS 20-20230801-NIGHTLY-enchilada

Your email address will not be published. Required fields are marked *