This article is all about the CTS Profile Mismatch Error and how to fix it.
Before starting with the steps to fix the Magisk CTS Profile False/Mismatch Errors, let’s first understand what is ‘SafetyNet.’ We all know that rooting our Android phones give us a lot of freedom and we can do some great things with a rooted smartphone like installing a custom ROM, a custom Kernel, overclocking the processor, etc.
But, if you have a device with which you use Google’s Android Pay, then it won’t work if you root your phone. SafetyNet is a thing that Google uses to detect whether your Android smartphone is rooted or not and if it detects that you have a rooted phone, certain apps can block you from accessing them. We have seen this with the Netflix app that users cannot even find the app to download from the Play Store if their devices are rooted.
Magisk, as most of you might know, is a Universal Systemless Interface, to create an altered mask of the system without changing the system itself. (Thanks, XDA). With Magisk and Systemless root, we can skip most of the SafetyNet tests, revert but the thing is that the Google’s Compatibility Test Suite (CTS) is still a problem.
So, you might get the ‘Magisk safetynet CTS Profile Mismatch Error’ even if you have the Magisk installed on your android phone. So, assuming that you have already installed the Magisk, let’s start with the steps to fix this error.
TIP – You can check your SafetyNet status from the Magisk Manager. You will find an option that says ‘Tap to start SafetyNet Check.’ Tap on that, and it will show you the status.
- 1 STEPS TO FIX THE CTS PROFILE MISMATCH ERRORS – FIX CTS PROFILE MATCH FALSE
- 2 CONCLUSION
STEPS TO FIX THE CTS PROFILE MISMATCH ERRORS – FIX CTS PROFILE MATCH FALSE
1. WHY NOT USE MAGISKSU?
So, the thing is that if you have rooted your smartphone and it is having any other root manager than the MagiskSU, then the chances are that it doesn’t hide from Google’s SafetyNet and you get the error. SuperSU, which is the most popular root manager app, is on almost every rooted device so, if you want to get rid of the CTS error, make sure that you are using the MagiskSU and not SuperSU. So, here is how to switch from SuperSU to MagiskSU –
- If you have the Xposed Installer installed, then uninstall it. No need to worry about all the modules you were using. You can install the systemless version of the Xposed using Magisk. To uninstall Xposed, go to Framework > Uninstaller and choose ‘Uninstall’ option. After the process completes, reboot your device by tapping on the ‘Reboot’ option.
- This step is a bit trickier, and if, you have made any changes in the system after rooting your phone, you need to revert them. For Example, let’s suppose you removed the bloatware apps via Titanium Backup. So, you need to install them again. Or, let’s assume that you used AdAway to remove ads. So, you need to remove that also. And we all know what’s the best way to revert all the changes – Flashing the Stock System Image of your phone.
- Now, you need to Unroot via the option in SuperSU and then, restore the Stock Boot Image of your phone. For that, Go to the SuperSU app and then settings. There, you will find an option called ‘ Full Root.’ Just tap on that and tap ‘Continue.’ Now, it will ask you if you want to restore the stock boot image. Here, make sure that you tap on ‘Yes’ option. Now, for installing Magisk, you need TWRP installed, so if you already have TWRP, you need to tap on ‘No’ when SuperSU asks if you want to restore the stock recovery image.
- Now, you need to install the Magisk zip. For this, head to the Magisk Manager app and go the Install section. Here, you will find an option named ‘Download.’ Tap on that and once downloaded, boot into recovery. Once you are in TWRP, tap on ‘Install’ and select the Magisk ZIP file from the Magisk Manager folder. To flash the ZIP file, slide the button to the right and when finished, tap on ‘Reboot System.’
- Now, got to Magisk Manager app, and go to settings. Here, make sure to enable Magisk Hide, BusyBox, and Systemless hosts options. Lastly, clear the data of the Play Store by going to Settings > Apps > Play Store > Manage Space > Clear Data.
Now, head to the Magisk Manager app and go to Magisk Hide. Make sure that this option is enabled and it will be used to hide additional apps like Google Play Store and Google Services Framework and other apps that you think are having the issues with SafetyNet.
2. WHAT ABOUT TRYING unSU?
If you are unable to fix the CTS Profile Mismatch error even after doing everything mentioned above, you can try unSU. We have to use this because, i.e., even after doing the ‘Full Unroot’ via the SuperSU, not all the data of the SuperSU is removed. The developer osm0sis has created a flashable zip that you can download and flash via TWRP. The flashing procedure is same as you flashed the MagiskSU ZIP.
3. IS USB DEBUGGING ON? TURN IT OFF!
So, we also don’t know why but the CTS Profile Mismatch error can occur even with Magisk installed if you have turned on the ‘USB Debugging’ Option. So, you need to head to the Settings? Developer Options and then, turn off the ‘USB Debugging.’ Lastly, do a reboot and check if the issue has been fixed or not.
4. SET SELinux BACK TO ‘ENFORCING’ MODE
This is a pretty simple step. So, back in time if you ever changed the SELinux mode to ‘Permissive,’ then you need to revert it to ‘Enforcing,’ i.e., the default mode. So, open the same app via which you change the SETLinux Mode to Permissive and change the mode back to ‘Enforcing’. Now, you need to reboot the phone. You can find the apps to do so on XDA easily.
5. TRY A CUSTOM KERNEL
Having a custom ROM? Well, then you can try installing a custom Kernel. Why are we saying this? Well, the CTS is used by Google to verify that the device and its firmware meet the certification standards. A phone with custom ROM won’t pass this test. But, there is still a way. You need to install a custom Kernel known as the ‘Franco Kernel’ and to install this, you need to buy an app called ‘Franko Kernel Updater’ or ‘FKU.’ Once you have installed it, open it and then tap on ‘Download’ option. Don’t wanna spend money? Well, head to XDA, and you can find the best ‘Franco Kernel’ ZIP file for your smartphone for free.
The Franco Kernel helps in such a way that the apps that use SafetyNet check the Basic Integrity don’t get any error.
6. ENABLE MAGISK CORE ONLY MODE
This is probably the best thing to do if all the things mentioned above aren’t working at all. See, when you head over to the settings of Magisk Manager, you will see an option that says ‘Magisk Core Only Mode’ under the ‘Magisk’ options. Many users have reported that turning this particular option ON fixes the magisk CTS Profile false error. Google has already updated its SafetyNet to check if there is Magisk on a particular device or not. So, enabling the Core Only Mode helps a lot in this case.
So, what this option does? Well, enabling Masigk Core Only Mode means that all the Magisk Modules currently active are disabled and so, the only thing your phone has is the Superuser from Magisk and the root access. This step helps because sometimes, there are certain Magisk modules that cause issues with the SafetyNet test. And yes, make sure to reboot once you enabled the Magisk Core only mode.
7. SOME USERS FIXED IT LIKE THIS
A lot of users have recommended some more ways to fix the CTS Profile Mismatch error on their device. First, you need to go into the Magisk Settings and there, check if the ‘Magisk Hide’ option is turned on or not. If it is turned on, then simply turn it OFF and again turn it ON. Check if the error is there or not. If it is, then turn off the Magisk Hide option, reboot the phone, open Magisk Settings and turn On the Magisk Hide again.
If this too doesn’t fix it, then there is one more method suggested by some users who faced this problem. In the Magisk Settings, you will find two options – ‘Systemless Hosts’ and ‘Enable Busybox’. Disabling these two options may also help in fixing the CTS Profile False error.
8. WELL, YOU HAVE TO DO IT NOW!
This is a step that no one would like to take if the CTS Profile False issue occurs. Well, if nothing works, then the only way you have left to fix that error is to install the stock ROM again, install the custom recovery again, then flash Magisk ZIP file to gain the root access and check if the issue persists now or not. If you are lucky, the issue will be gone completely.
If you have a Xiaomi phone with a custom ROM installed, you can use this Magisk Module to pass the CTS test.
So, this was a detailed guide about fixing the CTS Profile Mismatch Error or Magisk Basic integrity False error even with Magisk installed. If the steps mentioned above don’t work, you need to 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.
Rumor – Samsung Galaxy A90 launching with 8nm Snapdragon 7150
Recently, Samsung itself confirmed that the Galaxy A90 is coming with a notchless Infinity Display. We already know that it...
Motorola One Vision press render leaks, hole-punch display confirmed
Recently, the Motorola One Vision showed up on Geekbench with the Samsung’s Exynos 9610 chipset, but it wasn’t confirmed if...
Samsung confirms Notchless Infinity screen on the Galaxy A90
It looks like companies like to reveal details about their upcoming devices. Recently, Huawei accidentally made the page for the...
Huawei P30 & P30 Pro page accidently goes live on the official site
Huawei will launch the P30 series on March 26th, but it looks like the company doesn’t want to make us...
More details of the Motorola One Vision with Exynos 9610 surface
A few days back, Motorola One Vision showed up on Geekbench with Exynos 9610 processor, and since a lot of...
Moto G7 with Snapdragon 632 is launching in India on March 25th
Motorola isn’t doing great from the past couple of years when it comes to smartphones. The company does launch phones...
Samsung Galaxy A40 press renders reveal the design, launching soon
Samsung will unveil a few new ‘A’ series phones on April 10th, and there are rumors of the Galaxy A60,...