Исправить в Magisk «SafetyNet не пройден: несовпадение профиля CTS»
В данной статье мы попытались собрать абсолютно все способы решения проблемы в Magisk «SafetyNet не пройден: несовпадение профиля CTS».
Большинство пользователей которые ранее пользовались SuperSU переходят на новый Magisk, так как он имеет довольно множество плюшек, о которых мы говорили ранее.
Одной из главных достоинств Magisk — это возможность прятать от банковских и других приложений наличие Root прав, так как при их обнаружение, они останавливают свою работу.
Но многие пользователи, что установили Magisk Manager, столкнулись с проблемой «SafetyNet не пройден: несовпадение профиля CTS» и в этой статье мы предложим вариантов как ее исправить.
Инструкция как исправить:
«SafetyNet не пройден: несовпадение профиля CTS»
в Magisk
Ниже будут представлены 6 шагов для исправления «SafetyNet не пройден».
Шаг 1 — Избавиться от SuperSU
Если вы получали Root права с помощью ZIP файла SuperSU или CF Auto Root, который установил SuperSU на ваш Android, а после решили поменять на Magisk, то это может быть первой проблемой с SafetyNet.
Удалите SuperSu из вашего смартфона или планшета, а после прошить в Recovery файл UPDATE-unSU-signed.zip чтобы полностью вычистить все из системы.
Шаг 2 — Изменить режим SELinux
Попробуйте установить режим работы SELinux в «Permissive», а после вернуть обратно «Enforcing» и перезагрузить Android.
Шаг 3 — Отключить «отладку по USB»
Если у вас до последнего момента у вас была включена «отладка по USB«, тогда перейдите в меню «Настройки»-> «Для разработчиков» и отключить «отладку» и перезагрузить Android.
Шаг 4 — Используете другое ядро
Поищите в сети интернет стороннее ядро для своего Android, после чего проверьте не исчезла ли проблема в Magisk «SafetyNet не пройден: несовпадение профиля CTS».
Шаг 5 — Другие проблемы
Перейдите в меню настроек Magisk и отключите Busybox и Systemless hosts и перезагрузите Android.
Шаг 6 — включить режим Magisk Core Only Mode
Если все предыдущее шаги вам не помогли, тогда попробуйте включить режим работы Magisk Core Only Mode, который отключает дополнительные возможности Magisk.
Шаг 7 — добавить строки build.prop
С оригинальной прошивки (если вы используете кастом) в файле build.prop, который находиться в разделе /system, скопируйте поля со значения:
И добавьте их в файл build.prop установленной прошивки.
Шаг 8 — ввести команду в терминале
Установите приложение терминал на Android и введите в него следующие команды:
su
sh /magisk/.core/magiskhide/disable
sh /magisk/.core/magiskhide/enable
Шаг 9 — Начать все с начала
Если вам ничего не помогло, тогда попробуйте переустановить прошивку на вашим Android, а после получить Root с помощью Magisk, чтобы избавиться от проблемы «SafetyNet не пройден: несовпадение профиля CTS».
Остались еще вопросы? Пишите их в комментариях, рассказывайте, что у вас получилось или наоборот!
Вот и все! Больше статей и инструкций читайте в разделе Статьи и Хаки Android. Оставайтесь вместе с сайтом Android +1, дальше будет еще интересней!
Magisk 101: Как исправить ошибки SafetyNet CTS Profile Mismatch ‘
Не могу войти в Call Of Duty Mobile из-за ошибки авторизации
Простые шаги для удаления родительского контроля PS4 | 2020 | НОВЫЙ учебник!
Лучшие настройки ПК для Call Of Duty Warzone для увеличения FPS
Из-за новой системы SafeNet от Android некоторые приложения теперь могут блокировать укоренившихся пользователей или не позволять вам вообще обращаться к ним — но по крайней мере на данный момент все еще существуют ограничения.
Вы можете передать большинство проверок SafetyNet с помощью Magisk и без системного корня, но в некоторых случаях тестовый комплект Google Compatibility Test Suite (CTS) остается препятствием.
Если это произошло с вами, существует ряд потенциальных причин: от несовместимых приложений управления корнями до проблем с Magisk Hide.
Прежде чем вы начнете
В этом руководстве предполагается, что вы уже установили Magisk, который представляет собой бессистемную утилиту root, которая может скрыть свое присутствие в SafetyNet.
Когда дело доходит до фактической проверки вашего статуса SafetyNet, самый простой способ сделать это — открыть приложение Magisk Manager и нажать кнопку «Проверка безопасности» в нижней части экрана.
Проверка статуса SafetyNet в Magisk Manager.
Шаг 1: Избавьтесь от SuperSU и используйте MagiskSU с Magisk Hide
Наиболее вероятной причиной несоответствия профиля CTS является приложение для управления корнями, которое не скрывает себя от SafetyNet.
Скорее всего, вы изначально использовали ваш телефон, используя SuperSU ZIP или CF Auto Root, которые устанавливают SuperSU в качестве приложения для управления корнем по умолчанию.
Поэтому, если это является причиной ваших проблем с CTS, вам нужно будет удалить бинарные файлы SuperSU и заменить их встроенным корневым приложением Magisk.
После того, как вы это сделали, убедитесь, что опция «Магическая Hide» включена в вашем приложении «Магистр».
Для этого перейдите в навигационное меню в приложении Magisk Manager и выберите «Скрыть Magisk». Здесь может быть полезно отметить галочки рядом с Google Play Store и Google Services Framework, а также с любым другим приложением
Шаг 2: все еще нет хорошего?
Если вышеупомянутое руководство не устранило проблемы несоответствия профиля CTS, и вы уверены, что вы отменили какие-либо системные моды, возможно, что у вас все еще есть несколько бит данных, оставшихся от SuperSU.
Поэтому, чтобы убедиться, что вы полностью уничтожили SuperSU и его двоичные файлы, вы можете использовать flashable ZIP, созданный разработчиком osm0sis.
Оттуда нажмите кнопку «Установить» в главном меню TWRP, затем перейдите в папку «Загрузить» и выберите UPDATE-unSU-signed.zip.
Шаг 3: Измените SELinux на принуждение
Если вы все еще застряли, этот следующий шаг довольно прост, хотя это применимо только в том случае, если вы ранее использовали приложение, чтобы установить режим SELinux в «Permissive». «Magisk пытается скрыть ваш статус SELinux от SafetyNet
Итак, откройте какое-либо приложение SELinux mode changer, которое вы использовали для установки режима «Permissive», в первую очередь, затем переключите настройку на «Enforcing» и перезагрузитесь.
Шаг 4: Отключение USB-отладки
По какой-то странной причине довольно распространенная причина проблем SafetyNet с Magisk — это настройка «USB Debugging» в настройках разработчика.
Шаг 5: Пользовательское ПЗУ?
Как я уже упоминал ранее, CTS означает «Комплект тестирования совместимости». Это процесс, который Google использует для проверки того, что устройство и его прошивка соответствуют стандартам сертификации, и, проще говоря, пользовательский диск никогда официально не пройдет этот тест.
Тем не менее, некоторые пользовательские ядра могут помочь с этой проблемой.
Для некоторых пользовательских ПЗУ (особенно ОС Lineage) эта опция может не полностью решить проблему.
Наконец, для пользователей Xiaomi, которые запускают пользовательский ПЗУ, есть еще один вариант.
Шаг 6: Обращайтесь к другим потенциальным проблемам
Во-первых, возможно, что демон Magisk Hide не запускается правильно на вашем телефоне.
Некоторые пользователи также сообщили, что опции Magisk «Systemless hosts» и «BusyBox» заставили их столкнуться с проблемами с SafetyNet.
Шаг 7: Включить режим Core Core
Как последнее усилие, вы можете попробовать включить параметр «Только основной режим» в настройках Magisk Manager.
Возможно, это не идеальное решение, но после того, как Google обновил SafetyNet для обнаружения Magisk, включение режима «Только Core» кажется единственным исправлением, которое помогает большинству пользователей проходить тест CTS.
Шаг 8: Если все остальное не работает, начните с нуля
Мы сохранили этот шаг для последнего, потому что это универсальное решение, но это больная пилюля для глотания.
Процесс восстановления вашей прошивки будет варьироваться в зависимости от устройства, но если ваш телефон имеет меню загрузчика, которое поддерживает команды Fastboot, мы рассмотрели этот процесс в этом руководстве.
Итак, вы наконец решили проблемы с несоответствием профиля CTS?
[SEPTEMBER FIX] Working Fix for Magisk SafetyNet/CTS Profile FAILED
UPDATE – SEPTEMBER 13, 2021 – UPDATED UNIVERSAL SAFETYNET FIX BY kdrag0n
So, kdrag0n has released the latest version of the Universal SafetyNet Fix and the biggest highlight of the new version is that the SafetyNet failed issue of September is now fixed with this new update. So, the steps remain the same as before –
CHANGELOG OF VERSION 2.1.0 –
UPDATE – SEPTEMBER 2, 2021 – NEW FIX FOR SAFETYNET FAILED ISSUE
So recently, for some reason, SafetyNet has started failing even after installing the below-mentioned Universal Fix by kdrag0n. Well, thanks to TeamFiles on Telegram., we have another fix now that works for this new issue. This fix requires you to first download a few files. Here are the ones you need to download and keep on your phone before starting with the steps –
You can also download a Zip file that has all these three files included in it. Here is the link to that.
Now, before starting, make sure you backup everything as this fix has not been tested for all the devices, so it may cause some issues in your phone. Also, make sure the latest Stable version of Magisk is there on your phone. We won’t be responsible for any damage happening to your phone.
Here are the steps –
And that’s it! If everything goes well, you will no longer have the SafetyNet Failed Issue on your phone, and the Play Store will show Device is Certified. If Banking apps are not working even after fixing the SafetyNet with this method, then you need to check “Use Tracking” for those apps in “XPrivacyLua.” Just like what we did with Play Services. And then the same steps, i.e., clear data and reboot. For a better understanding, here is the full video tutorial by Munchy –
UPDATE – JULY 4, 2021 – UNIVERSAL FIX FOR SAFETYNET (ALL THANKS TO kdrag0n)
kdrag0n has shared a Universal Fix for Google SafetyNet on Android devices with hardware attestation and unlocked bootloaders. You can now install a Magisk Module that will fix the ctsProfile Failed issue. On the official Github page, kdrag0n has mentioned that –
This Fix defeats both hardware attestation and the new CTS profile updates, without any changes to device or model names, as long as you can pass basic attestation (i.e. fingerprints). No device-specific features (such as the Pixel-exclusive Google Assistant design) will be lost. MagiskHide is required if the device is rooted. Android versions 8–11 are supported. Heavy OEM skins are not officially supported, but they may work depending on your luck and the particular ROM in question.
Anyways, here are the steps –
PREVIOUS VERSIONS OF THE FIX –
UPDATE – HERE IS ANOTHER METHOD THAT WILL HOPEFULLY HELP YOU FIX THE CTS PROFILE FALSE ISSUE
NOTE – TRY THESE STEPS ON YOUR OWN RISK. WE WON’T BE RESPONSIBLE IF ANYTHING GOES WRONG.
Here are the steps –
After all these steps, you will see that in the Magisk Manager, it no longer says “false” in front of the ctsProfile option. Also, in the play store, it’ll say “Device in Certified.” Hopefully, now you will also be able to use Payment apps like Google Pay on your device (Hopefully).
Thanks to Crazy Customization (YouTube) for the video tutorial.
UPDATE: 2020 – IN MARCH 2020, GOOGLE MADE SOME CHANGES WHICH RESULTED IN MAGISK, NOT ABLE TO PASS SAFETYNET. HERE IS A WORKAROUND FOR THAT TO FIX THE CTS PROFILE FALSE ERROR (SAFETYNET FAILED).
We will use Xposed Framework for the Workaround, but you need to have your device rooted via Magisk and have the Magisk Manager installed on your phone since we need the Magisk Modules. Now, there is no way to know if Xposed Framework will be working on all the devices, so this means there are chances of it not working on your device.
First of all, here are all the files that you need to download on your device –
HERE ARE THE STEPS TO FIX MAGISK CTS PROFILE FALSE ERROR WITH THE NEW METHOD
Well, that’s it! Now, go to Magisk Manager, tap to start the SafetyNet Check, and you will now see that the ‘ctsProfile’ shows as True! This means we successfully did the SafetyNet Bypass.
NOTE THAT IF THIS METHOD ALSO DOESN’T WORK, THEN WE WILL HAVE TO WAIT FOR THE DEVELOPERS TO FIND ANOTHER FIX FOR THIS.
Props to ‘Munchy‘ to share this method on his YouTube Channel.
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. 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 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. 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, 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 MagiskSU and not SuperSU.
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 issues with SafetyNet.
2. WHAT ABOUT TRYING unSU?
If you cannot 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 the same as you flashed the MagiskSU ZIP.
3. IS USB DEBUGGING ON? TURN IT OFF!
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,’ 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? 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 away. 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 so 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. 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, certain Magisk modules 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
Many 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 turn it OFF and again turn it ON. Check if the error is there or not. If it is, 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 the 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.
[SEPTEMBER FIX] Working Fix for Magisk SafetyNet/CTS Profile FAILED
UPDATE – SEPTEMBER 13, 2021 – UPDATED UNIVERSAL SAFETYNET FIX BY kdrag0n
So, kdrag0n has released the latest version of the Universal SafetyNet Fix and the biggest highlight of the new version is that the SafetyNet failed issue of September is now fixed with this new update. So, the steps remain the same as before –
CHANGELOG OF VERSION 2.1.0 –
UPDATE – SEPTEMBER 2, 2021 – NEW FIX FOR SAFETYNET FAILED ISSUE
So recently, for some reason, SafetyNet has started failing even after installing the below-mentioned Universal Fix by kdrag0n. Well, thanks to TeamFiles on Telegram., we have another fix now that works for this new issue. This fix requires you to first download a few files. Here are the ones you need to download and keep on your phone before starting with the steps –
You can also download a Zip file that has all these three files included in it. Here is the link to that.
Now, before starting, make sure you backup everything as this fix has not been tested for all the devices, so it may cause some issues in your phone. Also, make sure the latest Stable version of Magisk is there on your phone. We won’t be responsible for any damage happening to your phone.
Here are the steps –
And that’s it! If everything goes well, you will no longer have the SafetyNet Failed Issue on your phone, and the Play Store will show Device is Certified. If Banking apps are not working even after fixing the SafetyNet with this method, then you need to check “Use Tracking” for those apps in “XPrivacyLua.” Just like what we did with Play Services. And then the same steps, i.e., clear data and reboot. For a better understanding, here is the full video tutorial by Munchy –
UPDATE – JULY 4, 2021 – UNIVERSAL FIX FOR SAFETYNET (ALL THANKS TO kdrag0n)
kdrag0n has shared a Universal Fix for Google SafetyNet on Android devices with hardware attestation and unlocked bootloaders. You can now install a Magisk Module that will fix the ctsProfile Failed issue. On the official Github page, kdrag0n has mentioned that –
This Fix defeats both hardware attestation and the new CTS profile updates, without any changes to device or model names, as long as you can pass basic attestation (i.e. fingerprints). No device-specific features (such as the Pixel-exclusive Google Assistant design) will be lost. MagiskHide is required if the device is rooted. Android versions 8–11 are supported. Heavy OEM skins are not officially supported, but they may work depending on your luck and the particular ROM in question.
Anyways, here are the steps –
PREVIOUS VERSIONS OF THE FIX –
UPDATE – HERE IS ANOTHER METHOD THAT WILL HOPEFULLY HELP YOU FIX THE CTS PROFILE FALSE ISSUE
NOTE – TRY THESE STEPS ON YOUR OWN RISK. WE WON’T BE RESPONSIBLE IF ANYTHING GOES WRONG.
Here are the steps –
After all these steps, you will see that in the Magisk Manager, it no longer says “false” in front of the ctsProfile option. Also, in the play store, it’ll say “Device in Certified.” Hopefully, now you will also be able to use Payment apps like Google Pay on your device (Hopefully).
Thanks to Crazy Customization (YouTube) for the video tutorial.
UPDATE: 2020 – IN MARCH 2020, GOOGLE MADE SOME CHANGES WHICH RESULTED IN MAGISK, NOT ABLE TO PASS SAFETYNET. HERE IS A WORKAROUND FOR THAT TO FIX THE CTS PROFILE FALSE ERROR (SAFETYNET FAILED).
We will use Xposed Framework for the Workaround, but you need to have your device rooted via Magisk and have the Magisk Manager installed on your phone since we need the Magisk Modules. Now, there is no way to know if Xposed Framework will be working on all the devices, so this means there are chances of it not working on your device.
First of all, here are all the files that you need to download on your device –
HERE ARE THE STEPS TO FIX MAGISK CTS PROFILE FALSE ERROR WITH THE NEW METHOD
Well, that’s it! Now, go to Magisk Manager, tap to start the SafetyNet Check, and you will now see that the ‘ctsProfile’ shows as True! This means we successfully did the SafetyNet Bypass.
NOTE THAT IF THIS METHOD ALSO DOESN’T WORK, THEN WE WILL HAVE TO WAIT FOR THE DEVELOPERS TO FIND ANOTHER FIX FOR THIS.
Props to ‘Munchy‘ to share this method on his YouTube Channel.
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. 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 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. 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, 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 MagiskSU and not SuperSU.
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 issues with SafetyNet.
2. WHAT ABOUT TRYING unSU?
If you cannot 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 the same as you flashed the MagiskSU ZIP.
3. IS USB DEBUGGING ON? TURN IT OFF!
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,’ 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? 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 away. 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 so 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. 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, certain Magisk modules 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
Many 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 turn it OFF and again turn it ON. Check if the error is there or not. If it is, 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 the 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.