Database Develop

SafetyNet CTS profile match false

This thread is dedicated to understanding what is causing the SafetyNet to report the CTS profile match as false.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried unrooting and flashing a new kernel, but the error remains.
Anyone knows what does it check?
@Tesla
@xstahsie

What I can tell you, Busybox is not the problem in my case. Fully unrooted und un-busyboxed my Note3 (see sig) by modding the ROM I use pre-flash, wiped /system and put it on there with TWRP. Nope. I am close to think that there's some thing custom ROMs pass to Google by SafetyNet and are being detected as not official by that. The fingerprint (In my case "samsung/hero2ltexx/hero2lte:6.0.1/MMB29K/G935FXXU1APEK:user/release-keys") compared to H/W maybe...

I have the same problem with a unroot cyanogenmod 13. Pokemon Go die.

sakis_the_fraud said:
This thread is dedicated to understanding what is causing the SafetyNet to report the CTS profile match as false.
View attachment 3902690
I tried unrooting and flashing a new kernel, but the error remains.
Anyone knows what does it check?
@Tesla
@xstahsie
Click to expand...
Click to collapse
Assuming you have made a NANDROID backup via TWRP when the phone was unrooted, simply restore "boot" from your backup. If you don't have a copy, you'll need to reflash your ROM. And if you have to do that, just flash boot and system.
Sent from my Nexus 6P using Tapatalk

I'm on the same boat as you guys. Exact same error, CM13 with su removed, nothing else modified. No idea why CTS is now false.

xstahsie said:
Assuming you have made a NANDROID backup via TWRP when the phone was unrooted, simply restore "boot" from your backup. If you don't have a copy, you'll need to reflash your ROM. And if you have to do that, just flash boot and system.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Phone was rooted on second boot.
I will try to flash a stock kernel when i return home, but i don't expect much.
Flashing stock system is definitely not an option, do you think dirtyflash will work?
Sent from my Xperia Z5 using Tapatalk

sakis_the_fraud said:
Phone was rooted on second boot.
I will try to flash a stock kernel when i return home, but i don't expect much.
Flashing stock system is definitely not an option, do you think dirtyflash will work?
Sent from my Xperia Z5 using Tapatalk
Click to expand...
Click to collapse
I've dirty flash system on LG G3 many times without any issues. Just wipe cache afterward.
Sent from my Nexus 6P using Tapatalk

@AbiDez , @Boosik , @asdone001 check here, we all have the same problem!
anyone here tried switching SELinux mode as phhuson suggested?
phhusson said:
For people for which SafetyNet fails, is /sys/fs/selinux/enforce or policy readable by an application?
On standard Android it's not readable, but perhaps that's the difference on your devices.
Click to expand...
Click to collapse
here is a guide:
koron393 said:
Code:
$ getenforce
This prints SELinux mode. (Permissive or Enforcing)
Code:
$ su
# setenforce 1
This will set SELinux mode Enforcing.
or try
Code:
# setenforce Enforcing
Click to expand...
Click to collapse
my kernel is set to permissive and I can't switch it, i will try to flash stock and report back.

sakis_the_fraud said:
@AbiDez , @Boosik , @asdone001 check here, we all have the same problem!
anyone here tried switching SELinux mode as phhuson suggested?
my kernel is set to permissive and I can't switch it, i will try to flash stock and report back.
Click to expand...
Click to collapse
Already tried it, but not with those commands. I switched from an unofficial CM13 ROM with SElinux set to permissive to an official CM13 nightly with SElinux set to enforcing. I removed root and bam, Safety Net check passes all checks now.

@sakis_the_fraud
My kernel is
.
On pure stock rom with stock recovery without root - SafetyNet is all green, PoGo works.
On stock rom with TWRP without root - SafetyNet is all green, PoGo works.
On stock rom with TWRP and superuser-r266-hidesu - SafetyNet is red (CTS profile match: false), PoGo doesn't work.
My superuser-r266-hidesu config is "eng noverity crypt hidesu".
But as phh asked "/sys/fs/selinux/enforce" is readable on my device, I can open it in SE File Explorer (contains 1). "/sys/fs/selinux/policy" gives me access denied.
---------- Post added at 01:38 PM ---------- Previous post was at 12:39 PM ----------
Fixed it by setting my superuser-r266-hidesu to verity (was using noverity to be able to mount /system as rw).

Boosik said:
My superuser-r266-hidesu config is "eng noverity crypt hidesu".
Fixed it by setting my superuser-r266-hidesu to verity (was using noverity to be able to mount /system as rw).
Click to expand...
Click to collapse
great info, we are getting somewhere. :good:
could you tell me how to change this setting?
Also, you could try with "noverity setting" to use the "root switch" from shakalaca.
You can find the latest version here at post no: 263.

sakis_the_fraud said:
great info, we are getting somewhere. :good:
could you tell me how to change this setting?
Also, you could try with "noverity setting" to use the "root switch" from shakalaca.
You can find the latest version here at post no: 263.
Click to expand...
Click to collapse
Open the superuser-r266-hidesu.zip archive and there is config.txt file. Open it and there are some words "eng verity crypt hidesu" I had it set to "noverity" it has to be "verity". Also root switch app doesn't seem to work with phh's superuser.

Boosik said:
Open the superuser-r266-hidesu.zip archive and there is config.txt file. Open it and there are some words "eng verity crypt hidesu" I had it set to "noverity" it has to be "verity". Also root switch app doesn't seem to work with phh's superuser.
Click to expand...
Click to collapse
thanks!
I see that the default option is verity, but it isn't passing the CTS profile match for me.
have you tried with chainfire's root and hidesu, maybe got some luck with that!

sakis_the_fraud said:
thanks!
I see that the default option is verity, but it isn't passing the CTS profile match for me.
have you tried with chainfire's root and hidesu, maybe got some luck with that!
Click to expand...
Click to collapse
Unfortunately chainfires su 2.78-SR1 has huge performance hit on my phone for some reason and makes it nearly unusable, so that is no option for me.
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
Are you using Magisk?
I do not use it.
I have stock rom and flashed superuser-r266-hidesu.zip nothing else. Everything works fine now.

Boosik said:
Unfortunately chainfires su 2.78-SR1 has huge performance hit on my phone for some reason and makes it nearly unusable, so that is no option for me.
Click to expand...
Click to collapse
i haven't tried it yet, reading about systemless install and the rest procedure.
what device are you using?
Boosik said:
Are you using Magisk?
I do not use it.
I have stock rom and flashed superuser-r266-hidesu.zip nothing else. Everything works fine now.
Click to expand...
Click to collapse
no.
here are the setups I have tried

sakis_the_fraud said:
i haven't tried it yet, reading about systemless install and the rest procedure.
what device are you using?
no.
here are the setups I have tried
View attachment 3903539
Click to expand...
Click to collapse
My device is Huawei Mate 8 (NXT-L29C432)
AFAIK "dm verity" has to be on for CTS to pass.
---------- Post added at 02:39 PM ---------- Previous post was at 02:35 PM ----------
Is your current phone Sony Z5?
On the Magisk page, there is something about Sony kernels being unpatchable, maybe that is the problem why your phone does not boot while trying it with dm verity on?
Sony devices generally: Sony devices seems to use ELF kernel that is unpatchable, or some has two ramdisks (inner + outer), both requires different workarounds, if you know any addition quirks about Sony boot image modifications, please contact me
Click to expand...
Click to collapse

Boosik said:
AFAIK "dm verity" has to be on for CTS to pass.
Click to expand...
Click to collapse
If yes, I'm screwed! I have no clue why it doesn't boot with that on!
Boosik said:
Is your current phone Sony Z5?
On the Magisk page, there is something about Sony kernels being unpatchable, maybe that is the problem why your phone does not boot while trying it with dm verity on?
Click to expand...
Click to collapse
yes, but there is a tool that can patch the kernel and edit those kind of things such as dm verity, sony ric, root, twrp etc.
also, magisk was working fine on my phone, i was using it before turning to phh's v266.

What does it mean if its says this and my phone is still vanilla.as in never been rooted or used thirdparty apps or that sort of stuff
Sent from my Elite 5 using Tapatalk

javaxcore said:
What does it mean if its says this and my phone is still vanilla.as in never been rooted or used thirdparty apps or that sort of stuff
Click to expand...
Click to collapse
something is tipping cts, we are searching to find it.

@Jayster06 check here
Something is tripping CTS, if it was on /system, why it isn't reported with stock kernel?
If you are rooted, the checker reports that the response validation failed, so it's not the root.
here are the configurations I have tried so far...
please report back if you found a solution.

[Q] Can't really activate any modules

Hi all,
I have a problem. I'm using an OnePlus 5 and I can't use Xposed. I have just tried those 2 things. I have magisk updated to 14.0
1) I installed the version 09-09-2017 by dvdandroid, then I installed 26-07-17 v87 sdk25 by PurifyOs, all seems OK xposed tells that is installed and working, so I try to download some modules, activate them, reboot, but when I try to use them they tell me "please activate the module", I tryed clearing cache and dalvik, reinstalling so many times but nothing.
2) So I removed the PurifyOs one, and wanted to try to install the systemless one. I open Xposed, press install, it auto flashes from TWRP but there is a message error "dev/magisk/mirror/bin is not setup properly". So I try to download it as a module from magisk, try to install but gives the same error.
Can you help me? Thanks

Up...

Up...

Uppppppppp

Having the same issue on Oneplus 5 running android 7.1.1.
Any solutions?

Up....

same issue oneplus 3t stock

Uppppp

I couldn't activate any modules either, even though framework was green/good.
I re-installed my ROM and re-did the Xposed setup, ensuring I was using the CORRECT files.
Such as for Magisk Xposed vs. non-Magisk Xposed.
It's working now.

CZ Eddie said:
I couldn't activate any modules either, even though framework was green/good.
I re-installed my ROM and re-did the Xposed setup, ensuring I was using the CORRECT files.
Such as for Magisk Xposed vs. non-Magisk Xposed.
It's working now.
Click to expand...
Click to collapse
Thanks for your answer, I already did but nothing changed..

If ur on oos with encryption, you need to soft reboot the phone before the modules work.

8monochrome said:
If ur on oos with encryption, you need to soft reboot the phone before the modules work.
Click to expand...
Click to collapse
Already tried, nothing happened

I'm not sure how the OnePlus works in comparison to my Moto G4, but I had the same problem with 7.1.x. I couldn't get Xposed to work on any roms running Nougat. Went and installed an AOSP marshmallow rom and Xposed is working very well. My advice would be to downgrade to marshmallow. It's definitely worth the Xposed compatibility because even if you do get that aspect of it going, many modules don't support nougat yet. I was reluctant when I first heard this, but I' don't regret my decision at all. I'm running 12 modules right now with no issues at all and loving it. Hope this helps.

Not able to Install Magisk Modules

I have successfully installed Magisk on my device Root works but when I try to install a magisk module I get an error about not being able to mount magisk.img. When I try to install through recovery the module is flashes without any errors but once you open the app It displays "no modules installed". Before the G5s plus that I have a had the Moto G5 Plus. It had the same problem I just had to install another kernel over stock one and Magisk would work as expected. Is there a kernel for stock room that would support Magisk. Anyone else had this problem or is it just me?

ive no issue installing modules through magisk. Theres a lot of factors here. You didnt mention but id presume you installed magisk through recovery. Also, I presume you installed xposed. Maybe the modules your using require xposed to work. I forgot the exact steps to install xposed through magisk, but its not hard, and Id assume anyways you tried all of that. Have to flask xposed through recovery if I remember, then you can install xposed app apk too through recovery, then open magisk and install the latest xposed there. Im not using a stock rom, however Im fully confident if you properly rooted, and unlocked your phone of course, (I assume you did, just saying) its not a kernel issue. Sorry if I wasnt any help, its all i can think of right now.

When I got the phone I unlocked the bootloader and installed TWRP. When I set up my device I went back to recovery to install Magisk 14.3. It installed correctly and I got root using Magisk but when I try to install any module through the Magisk app I get an error. If I got you right should I try to install Xposed too? I was planning to install Xposed, Magisk version. But when I try that I get an error. I have attached a screenshot of when I try to install Xposed by topjohnwu and Greenify for Magisk. I get the same error.

well, xposed may not be your issue if you cant install any module with magisk manager. The modules, majority of them, if not all of them, i dont know, do not require xposed. Some do, most do not. Now please keep in mind, i could be wrong. I would say this, no harm in installing xposed, its basically a must get anyways for many awesome apps/modules. How you install, first install the xposed manager, youll have to look around for it, its not on the play store. Then downkoad magisk xposed through magisk. Once you download that zip file boot into twrp and install xposed through twrp.
This is a youtube on it: https://www.youtube.com/watch?v=MCcvsOp83A4 Now thing is, this may not fix any of your problems. But theres a chance it may. Like i said either way you want xposed on rooted phones anyways.

Patched kernel for stock. I have no problem running modules on Magisk. Flash in recovery.
https://forum.xda-developers.com/showthread.php?p=73930507
Sent by way of magic

if youre using stock rom, try this kernel. i just compiled it today from geneticengineers git. last updated hours ago.

Ae3NerdGod said:
if youre using stock rom, try this kernel. i just compiled it today from geneticengineers git. last updated hours ago.
Click to expand...
Click to collapse
UPDATE, just found out wifi doesnt work, sorry, been traveling and didnt think to test. everything else seems to work tho.
heres an older version of the kernel not compiled by me until i figure this out

Ae3NerdGod said:
UPDATE, just found out wifi doesnt work, sorry, been traveling and didnt think to test. everything else seems to work tho.
heres an older version of the kernel not compiled by me until i figure this out
Click to expand...
Click to collapse
Is there a thread for these kernels or any for G5S Plus?

THERAJ12 said:
Is there a thread for these kernels or any for G5S Plus?
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g5s-plus/development/kernel-t3707143/post74562730#post74562730
wifi fixed btw

Magisk V16 can't install on Android 5.0

Has anyone has success in installing this on Android 5.0 samsung S4 ? I followed the instructions and the manager just says not installed.

Unless you provide more details and installation logs it's gonna be hard to help...

Didgeridoohan said:
Unless you provide more details and installation logs it's gonna be hard to help...
Click to expand...
Click to collapse
What details would you like to know? I flash it and then later restart but the manager was not there so I tried to install it from saving the apk file that I downloaded. But it just said it was not installed and later I found out I lost root from trying to flash Xposed on my phone.
I am very new to this and tried to follow the tutorials and videos but its not working cause I thought using Magisk I can install the seamless Xposed.

Those recovery/installation logs would be a good start.
You're muddling up the details a bit...
Was the Manager not installed or did it report that Magisk wasn't installed? And you lost root? But you said you couldn't install Magisk... Are you already rooted? That might cause issues.
Being nice and clear and detailed (what is being flashed, version numbers, what's already done, what works, what doesn't work, with logs, etc) in your descriptions would help.

Didgeridoohan said:
Those recovery/installation logs would be a good start.
You're muddling up the details a bit...
Was the Manager not installed or did it report that Magisk wasn't installed? And you lost root? But you said you couldn't install Magisk... Are you already rooted? That might cause issues.
Being nice and clear and detailed (what is being flashed, version numbers, what's already done, what works, what doesn't work, with logs, etc) in your descriptions would help.
Click to expand...
Click to collapse
I hope this is clearly for you!
1. I flash the file with TWRP with success
2. The phone got stuck on samsung logo
3. Root was removed.
4.I had to re flash stock and it is working again.
5. How do I get the logs of Magisk if my phone keeps looping?
I wanted to use Magisk to see if Xposed would work but it looks like i can't even get Magisk to work on my samsung i9500 with original rom. This same thing happens with Xposed where everything goes smoothly with flashing it in recovery and then a boot loop on the logo. Others on this forum have been complaining about this too and perhaps the developer might have not considered odexed rom like samsung for these wonderful apps to work?
I am going back to Kitkat where i don't have these issues and I can use Xposed.

Viper4Android Pie Compatible???

As the title states ...v4a is it compatible with pie? Im rooted running a custom rom rooted with magisk. Installed v4a thru magisk manager it installs but i get the install driver /re-install driver message everytime. Is it an workaround to get it working?

recepo1 said:
As the title states ...v4a is it compatible with pie? Im rooted running a custom rom rooted with magisk. Installed v4a thru magisk manager it installs but i get the install driver /re-install driver message everytime. Is it an workaround to get it working?
Click to expand...
Click to collapse
working fine here. maybe a root/magisk issue.

bober10113 said:
working fine here. maybe a root/magisk issue.
Click to expand...
Click to collapse
What rom are you on and which version of magisk are you running?

recepo1 said:
What rom are you on and which version of magisk are you running?
Click to expand...
Click to collapse
infinity rom.
magisk v18 and also newer test canary builds.
but prety sure its an issue where you don't wait 3 minutes after rebooting before doing actions that require root.
and not sure to which extent you tried to make magisk work with various files and mods but maybe you should just factory wipe and try and get magisk working before anything else. also mayke sure busybox is installed. and dont forget that 3 minute rule after a reboot.

bober10113 said:
infinity rom.
magisk v18 and also newer test canary builds.
but prety sure its an issue where you don't wait 3 minutes after rebooting before doing actions that require root.
and not sure to which extent you tried to make magisk work with various files and mods but maybe you should just factory wipe and try and get magisk working before anything else. also mayke sure busybox is installed. and dont forget that 3 minute rule after a reboot.
Click to expand...
Click to collapse
Thanks im sure it maybe an magisk issue im running 17.3 because i kept losing root on v18. I acquire root with v4a but it freezes and then keeps telling me to reinstall driver after reboot. I will try the 3 minute rule though..thank you. You installed v4a directly thru magisk or flashed a different version?

recepo1 said:
Thanks im sure it maybe an magisk issue im running 17.3 because i kept losing root on v18. I acquire root with v4a but it freezes and then keeps telling me to reinstall driver after reboot. I will try the 3 minute rule though..thank you. You installed v4a directly thru magisk or flashed a different version?
Click to expand...
Click to collapse
v3.3 on magisk dated of jan. 16th.
use aroma option. it will reboot on its own from magisk console and the just follow the automated steps in recovery

bober10113 said:
v3.3 on magisk dated of jan. 16th.
use aroma option. it will reboot on its own from magisk console and the just follow the automated steps in recovery
Click to expand...
Click to collapse
Thank you appreciate your help i will give it a try

I have tried everything for hours to get viper4android to work with no avail until now. Go to the xda download page and select the beta version. Boom. It works. I know you might have long forgot this or already figured it out but I had to share

old legacy magisk module has been working for months and months.