Несовпадение профиля cts что делать. Что делать, если смартфон сообщает «Google Pay не поддерживается на этом устройстве»? Как воспользоваться программой Magisk

Last Updated on June 14th, 2017

Before we go into the guide on , first let’s know about SafetyNet . This is a feature which Google uses to determine whether your Android device is rooted or not and if its found rooted then certain apps will cease to work. For example, Android Pay wouldn’t work on a rooted device – courtesy SafetyNet. Nowadays, rooting an Android device is a normal thing as it gives you power over the OS. You can do many things with a rooted Android device which are otherwise not possible. With a rooted Android device, you can install a custom ROM, a custom Kernel, or overclock the processor etc.

Magisk is a systemless root utility which hides its presence from SafetyNet. Means, with Magisk installed, SafetyNet won’t be able to detect that your Android device is rooted. However, Google’s CTS is still a problem and even with Magisk installed you might get ‘SafetyNet Failed: CTS Profile Mismatch Error’. Anyhow, in this Android Tutorial we will guide you How to Fix CTS Profile Mismatch Errors. Before we start, we are assuming that Magisk is already installed on your device.

Switch From SuperSU to MagiskSU to bypass SafetyNet

CTS Profile Mismatch Error is, in majority cases, caused because of the root management app. SuperSU is one of the most popular root management app in the market. But unfortunately, it’s not systemless and doesn’t hide from SafetyNet. Therefore, it’s highly likely that you will face CTS profile mismatch errors. So, first thing you need to do is to switch from SuperSU to MagiskSU to Fix CTS profile mismatch errors. Follow below steps carefully to successfully switch from SuperSU to MagiskSU.

1. Uninstall Xposed Installer if it’s already installed on your device. To keep using Xposed modules, you can install systemless version of Xposed using Magisk. Once it’s uninstalled, reboot your device.
2. As you rooted your device so it’s obvious that you must have installed apps which changed the core system files. You need to uninstall all such apps, or undo any changes made in the system files. The easiest way to revert back all the changes is to Flash the Stock System Image of your phone.
3. Now you need to Unroot your Android Device. To do so, launch SuperSU and head towards Settings. In Settings, you will find an option called “Full Root”, tap on it and then tap on Continue. Here tap on “Yes” when it asks you that if you want to restore the stock boot image.
4. Next, it will ask if you want to restore the stock recovery image. Tap on “No” option as TWRP custom Recovery is required to flash Magisk.
5. Now open the Magisk Manager App and head towards the Install section. Here tap on the option named “Download”. Once the file is downloaded, reboot your device into recovery mode. Once you are in TWRP menu tap on Install and select Magisk.zip from the MagiskManager folder. To install the ZIP file, slide the button to the right and when finished, tap on ‘Reboot System.’
6. Now go to Magisk Manager App >> Settings >> here enable Magisk Hide, BusyBox , and Systemless hosts options. The last thing is to clear Google Play Store data, to do so go to Settings > Apps > Play Store > Manage Space > Clear Data.

This is it! This should fix CTS profile mismatch errors. If the error is still bothering you then head towards the next solution.

Flash unSU to Fix CTS Profile Mismatch Errors

If the above method failed to work and you are still getting CTS Profile Mismatch Errors then try a flashable zip called unSU developed by osm0sis, and XDA developer. You had to come to this step because doing “Full Unroot” via SuperSU didn’t work and not all the data of SuperSU is removed. Therefore, flashing unSU via TWRP will ensure that no bits of SuperSU are left behind.

Turn Off USB Debugging to Fix CTS Profile Mismatch Errors

For some reason, if your USB Debugging option is On with Magisk installed, there are high chances that CTS Profile Mismatch errors will occur. Therefore, turn off USB Debugging option by going to Settings >> Developer Options >> here turn off the USB Debugging Option.

Set SELinux Back To ‘ENFORCING’ Mode

If you are still facing CTS Profile Mismatch Errors then this rather simple step. If at some point you changed the mode of SELinux to “Permissive” then it’s time to change the mode back to “Enforcing” which the default mode. Open the same app via which you changed the mode to “Permissive” and revert it back to the default “Enforcing” mode.

Install a Custom Kernel

If you are using a Custom ROM then obviously your device won’t pass Google’s certification tests and as result might face CTS profile mismatch errors. However, to overcome this issue you need to install a custom kernel called “Franco Kernel”. And to install Franco Kernel you need to buy an app called “Franco Kernel Updater” or “FKU”. Once FKU is installed, open it and Tap on “Download” option.

By now you must have got ridden of the CTS Profile Mismatch Errors, but if, the error is still popping up then you must take the hard route. You will have to take things from scratch like flash Stock ROM, install TWRP, and flash Magisk ZIP. We hope it doesn’t come to this. Please let us know at which point you stopped facing CTS Profile Mismatch Errors.

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.

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.

Позволяющий осуществлять бесконтактные платежи. Но не успели владельцы Android-смартфонов порадоваться новым возможностям, как перед многими из них встала проблема. Приложение благополучно устанавливалось на устройство, но при попытке запуска смартфон выдавал сообщение следующего содержания: «Google Pay не поддерживается на этом устройстве. Нам не удалось проверить соответствует ли Ваше устройство стандартам безопасности, установленным для Google Pay. Причина может быть в том, что на нем настроен root-доступ, разблокирован загрузчик операционный системы или установлено неоригинальное ПЗУ».

Что интересно, пострадала, как обычно, та часть пользователей, которая предпочитает иметь при себе не просто телефон для общения, а удобный и производительный инструмент для решения разного рода повседневных задач. Как вы уже, вероятно, догадались, это те, кто получил Root-права на свой смартфон и установил модифицированные прошивки с качественным переводом на русский язык, разблокировав при этом загрузчик (ознакомиться ). Еще интереснее то, что, к примеру, у смартфонов Xiaomi даже официальная еженедельная сборка для устройств этого популярного бренда не проходит проверку в Google Pay - приложение согласно работать лишь со стабильными версиями MIUI , обновления которых происходят раз в несколько месяцев.

Как воспользоваться программой Magisk?

Решение проблемы с Google Pay:


** В случае, если Вы не хотите устанавливать Magisk и остальное стороннее ПО, существует более простой способ скрытия Root-прав и/или разблокированного загрузчика от Google Pay: необходимо заменить две строчки (имя производителя и модель смартфона) в файле build.prop (например, с помощью