Android Magisk - SafetyNet check failed

[smileyhead]

Spoiler: Status

Installed Magisk v12.0 - Latest version of Magisk installed
Properly rooted - 8:MAGISKSU (topjohnwu)
SafetyNet Failed: CTS profile mismatch

Spoiler: Settings

Magisk Core Only Mode - Disabled
Enable BusyBox - Disabled
Magisk Hide - Enabled
Systemless hosts - Disabled

Superuser Access - Apps and ADB
Automatic Response - Prompt
Request Timeout - 10 seconds
Superuser Notification - Toast

is there anything I'm doing wrong?

 

[matpower]

What phone do you have? Did you have another root method before? What ROM are you using?

 

[smileyhead]

What phone do you have?

Huawei P9

Did you have another root method before?

No.

What ROM are you using?

Resurrection Remix. this one.

 

[Garro]

To be honest, MagiskManager always fails when checking for SafetyNet but I can play Pokemon Go and bypass Fire Emblem Heroes/Super Mario Run bans with it. Use an app that uses SafetyNet instead of MagiskManager to check if it's working.

Also, activate Magisk Core Only Mode if you still can't pass SafetyNet (Since enabling Xposed will make SafetyNet to fail).

 

[smileyhead]

To be honest, MagiskManager always fails when checking for SafetyNet but I can play Pokemon Go and bypass Fire Emblem Heroes/Super Mario Run bans with it. Use an app that uses SafetyNet instead of MagiskManager to check if it's working.

iirc Play Store hides SafetyNet apps automatically if the phone doesn't pass the test, and I can't see Mario Run in there.

Also, activate Magisk Core Only Mode if you still can't pass SafetyNet (Since enabling Xposed will make SafetyNet to fail).

didn't work :-/

 

[matpower]

To be honest, MagiskManager always fails when checking for SafetyNet but I can play Pokemon Go and bypass Fire Emblem Heroes/Super Mario Run bans with it. Use an app that uses SafetyNet instead of MagiskManager to check if it's working.

Also, activate Magisk Core Only Mode if you still can't pass SafetyNet (Since enabling Xposed will make SafetyNet to fail).

Basic Integrity Check is enough for games, but it isn't enough for Play Store for example (Netflix and Fire Emblem Heroes/Super Mario Run won't show up) or Android Pay.

Anyway, smiley, it seems that SELinux is in Permissive mode (unless they fixed that), that makes SafetyNet trigger itself. Check your "About this phone" and confirm this if you can.

 

[smileyhead]

Anyway, smiley, it seems that SELinux is in Permissive mode (unless they fixed that), that makes SafetyNet trigger itself. Check your "About this phone" and confirm this if you can.

it says Enforcing.

 

[Garro]

iirc Play Store hides SafetyNet apps automatically if the phone doesn't pass the test, and I can't see Mario Run in there.

You sure? I really couldn't tell since I live in Chile and Nintendo hates us so everything from them is hidden to me, so I'm used to just install the .apk.

Also, I believe I do have SELinux in Permissive mode and I can AT LEAST play the Ninty games just fine.

 

[smileyhead]

it also seems like the Magisk Core Only mode fucked the fingerprint sensor, I can't use it anymore.

 

[matpower]

Hmm, that's troublesome... if SELinux is Enforcing, it should be all good to go. (That contradicts the thread though, it seems that the ROM is stuck in Permissive mode. Guess it's outdated info)
In that case, you could try lifting the ro.build.fingerprint= from the stock ROM's build.prop and add it to the custom ROM's build.prop (It's a trick that I used in my Moto G 2015 to fully pass SafetyNet, it's also used on Xiaomi devices) or disable ADB/USB debugging if it's enabled.

Also just to be sure, uninstall Magisk with MagiskUninstall script and run this script in TWRP and then flash Magisk through TWRP again, maybe that ROM added Lineage's SU binary by default. As I can't find any info about that on the thread, I will assume that as a possibility.

QUICK EDIT: Here's some good info about SafetyNet and CTS mismatch with Magisk.

 

[smileyhead]

maybe that ROM added Lineage's SU binary by default.

doubt that to be honest, the ROM doesn't have a root access setting in developer options.

In that case, you could try lifting the ro.build.fingerprint= from the stock ROM's build.prop and add it to the custom ROM's build.prop (It's a trick that I used in my Moto G 2015 to fully pass SafetyNet, it's also used on Xiaomi devices) or disable ADB/USB debugging if it's enabled.

how do I get that? is there a possibility it's inside an official update package?


also, there's a switch in developer options that says "OEM Unlocking - Allow the bootloader to be unlocked". I haven't touched that yet (it was on by default), but could it be the problem?

 

[matpower]

doubt that to be honest, the ROM doesn't have a root access setting in developer options.

how do I get that? is there a possibility it's inside an official update package?


also, there's a switch in developer options that says "OEM Unlocking - Allow the bootloader to be unlocked". I haven't touched that yet (it was on by default), but could it be the problem?

If the official update package is packed like the average custom ROM, it should be:

After getting the official build.prop, just open it in Notepad++ and search for "ro.build.fingerprint" or something like that and add it to your custom ROM's prop by editing it directly or by creating a simple Magisk module.
As for the OEM unlock thing, I don't think it should mess with anything, and it might be risky to disable it if your device uses some weird bootloader check or something, I once soft-bricked a friend's Samsung with that option, even though it was fine in my Moto G.

 

[smileyhead]

If the official update package is packed like the average custom ROM, it should be

it's not...

Spoiler

/patch

/zdiffer

recovery2_bvrl.img.p
recovery2_bdy.img.p
recovery2_avrl.img.p
nzbalong_modem_bvrl.bin.p
nzbalong_modem_bdy.bin.p
nzbalong_modem_avrl.bin.p
nv.bin.p
dt_bvrl.img.p
dt_bdy.img.p
dt_avrl.img.p​

/META-INF

/com

/google

/android

updater-script
update-binary​

/android

otacert​

MANIFEST.MF
CERT.SF
CERT.RSA
blacklist.conf​

UPDATE.APP
system.transfer.list
system.patch.dat
system.new.dat
cust.transfer.list
cust.patch.dat
cust.new.dat

 

[matpower]

it's not...

Spoiler

/patch

/zdiffer

recovery2_bvrl.img.p
recovery2_bdy.img.p
recovery2_avrl.img.p
nzbalong_modem_bvrl.bin.p
nzbalong_modem_bdy.bin.p
nzbalong_modem_avrl.bin.p
nv.bin.p
dt_bvrl.img.p
dt_bdy.img.p
dt_avrl.img.p​

/META-INF

/com

/google

/android

updater-script
update-binary​

/android

otacert​

MANIFEST.MF
CERT.SF
CERT.RSA
blacklist.conf​

UPDATE.APP
system.transfer.list
system.patch.dat
system.new.dat
cust.transfer.list
cust.patch.dat
cust.new.dat

I have a feeling it's inside the "system.new.dat" file, you could try extracting it with this tool.

 

[smileyhead]

I have a feeling it's inside the "system.new.dat" file, you could try extracting it with this tool.

 

[matpower]

View attachment 89168

Did you install Python2? It seems that it wasn't able to find it.

 

[Deleted User]

Some Custom OSes will always throw SafetyNet fail.
If you would be on-stock, it wouldn't be an issue.

 

[Minox]

Custom OSes will always throw SafetyNet fail.
If you would be on-stock, it wouldn't be an issue.

Not true. I'm using LineageOS on my Moto X Play and it passes the SafetyNet checks just fine.

 

[Deleted User]

Not true. I'm using LineageOS on my Moto X Play and it passes the SafetyNet checks just fine.

I meant some. Let me edit that post again since my brain refuses to cooperate with me.

 

[Magical Sheep]

Do you have Magisk Hide enabled? I had the issue with SafetyNet, until I enabled it. (I'm also on RR, but I'm on the OnePlus3.)