yashsingh1/xdaforums huggingface dataset:
[Magisk] Liquidrocks:
Hello, since I've installed the latest pure nexus version on my Nexus5 I can't pass through SafetyNet no matter what i do, having false on Basic Integrity & CTS. Tried with Magisk root & Magisk Hide (with & without Core Root), turning it on&off, deleting Superuser files with a tool provided on this thread, SELinux on Enforcing, disabling USB debugging; and reinstalling everything again. Also I tried to go unroot and relock the bootloader, but the SafetyNet didn't change at all.

This is the log provided by my Magisk Manager:

** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
* Running post-fs-data.d
* Loading core props
* Preparing modules
* Stage 1: Mount system and vendor mirrors
* Stage 2: Mount dummy skeletons
* Stage 3: Mount module items
* Stage 4: Execute module scripts
* Stage 5: Mount mirrored items back to dummy
** Magisk late_start service mode running...
* Enabling systemless hosts file support
* Enabling BusyBox
* Linking binaries to /sbin
* Starting MagiskSU
* Running service.d
* Starting MagiskHide

Any help would be appreciated, thanks in advance.
[Magisk] Didgeridoohan:
I never had any issues with passing SafetyNet on my Nexus 6 with Pure Nexus (I used 7.1.1_r26 last, before moving on to new adventures).

You don't have any other mods (I'm thinking mainly of things like Xposed) installed?

Do you have verbose logging enabled in Magisk Manager settings (it lacks a few things I'd like to see)? If not, enable it, make sure Hide is enabled (toggle it off and on again if it's already set to on), make a SafetyNet check and save and post a new log after that.
[Magisk] Liquidrocks:
Hello, thanks for your reply. Only things installed (ignoring TWPR) besides pure nexus are gapps and Magisk. Here is the log /w verbose after turning Hide off&on and doing SafetyNet check:

** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
* Running post-fs-data.d
* Loading core props
* Preparing modules
* Stage 1: Mount system and vendor mirrors
* Stage 2: Mount dummy skeletons
* Stage 3: Mount module items
* Stage 4: Execute module scripts
* Stage 5: Mount mirrored items back to dummy
** Magisk late_start service mode running...
* Enabling systemless hosts file support
* Enabling BusyBox
* Linking binaries to /sbin
* Starting MagiskSU
* Running service.d
* Starting MagiskHide
MagiskHide: Moving and re-linking /sbin binaries
MagiskHide: Removing dangerous read-only system props
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.debuggable'='0'
Existing property: 'ro.debuggable'='1'
Recheck property: 'ro.debuggable'='0'
Done!
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Starting MagiskHide daemon
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
Zygote(0) ns=mnt:[4026534250]
[Magisk] Didgeridoohan:
For some reason Hide isn't unmounting as it should. The question is why... I don't know.

If you're feeling adventurous you could try the latest unofficial beta snapshot, built from the unify_daemon branch. There's been a lot of changes done recently. No guarantees that it'll even work though (unofficial and beta being the key words)...
[Magisk] Poolwizard:
hi,

so i have magisk v12.0, 8:magisksu, magisk manager installed, but still getting false on safetynet.

ONeplus one with cm13 installed with android 6.0.1.

previously had removed root with success and could play Pokemon go, but now no longer possible saying device,os is incompatable, and false safetynet

android usb debugging is turned off and tried various combos of hide off/on and systemless on/off and reboot etc, but no success.

any suggestions for this?

thanks!
[Magisk] Liquidrocks:
I just gave the beta version a shot (v170415 w/ Manager 5.0.170331), got a pretty different log, sadly SafetyNet still fails.

Here is the latest log obtained:

** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
* Running post-fs-data.d
* Loading core props
* Preparing modules
* Stage 1: Mount system and vendor mirrors
* Stage 2: Mount dummy skeletons
* Stage 3: Mount module items
* Stage 4: Execute module scripts
* Stage 5: Mount mirrored items back to dummy
** Magisk late_start service mode running...
* Enabling systemless hosts file support
* Linking binaries to /sbin
* Starting MagiskSU
* Running service.d
* Starting MagiskHide
MagiskHide: Moving and re-linking /sbin binaries
MagiskHide: Removing dangerous read-only system props
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.debuggable'='0'
Existing property: 'ro.debuggable'='1'
Recheck property: 'ro.debuggable'='0'
Done!
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Starting MagiskHide daemon
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
Zygote(0) ns=mnt:[4026541728]
MagiskHide: com.google.android.gms.unstable(PID=3147 ns=mnt:[4026541804])
MagiskHide: Unmounted (/sbin)
MagiskHide: Unmounted (/magisk)
MagiskHide: Unmounted (/system/etc/hosts)
MagiskHide: Stopping MagiskHide daemon
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Removing dangerous read-only system props
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Starting MagiskHide daemon
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
Zygote(0) ns=mnt:[4026541728]
MagiskHide: com.google.android.gms.unstable(PID=4773 ns=mnt:[4026541789])
MagiskHide: Unmounted (/sbin)
MagiskHide: Unmounted (/magisk)
MagiskHide: Unmounted (/system/etc/hosts)
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]

The last 2 lines keep repeating several times for some weird reason, any ideas?

(Maybe this isnt the proper thread since I'm rolling with a beta version and I should report the issue, sorry in advance if that's the case).
[Magisk] Didgeridoohan:
That's not the latest snapshot, actually, but don't worry... The only one newer at the time of writing this doesn't really work (as in: don't flash it). The snapshot you used doesn't have many changes from the latest official release, and it's apparent from the log that your device still has issues with Magisk Hide. My advice would be: wait. There'll be a new release soon enough, and considering how much work has been done on GitHub lately it might bring some big changes. Again, no promises... :p
[Magisk] dado82rm:
I did not read all the thread but as far as i know after many reserches on the web i understood that the problem is the selinux permission in the build.prop.

the installation of the magisk change the value ro.build.selinux=0 to ro.build.selinux=1

there are many ways to revert it back to ro.build.selinux=0 but for me (oneplus one) i managed to create a flashable file that do the changes.

i did not create the flashable file itself, i used this page to create the flashable file [ZIP] Dynamic automated build.prop editing and then edited the tweak.prop file

attached is the zip (do not flash this one) just extract on the phone and then flash the build.prop.editor.zip in recovery mode

this will change the value to ro.build.selinux=0 regardless of the version of magisk

do not even read what i wrote :o
[Magisk] Didgeridoohan:
What are you talking about!? This makes no sense...
[Magisk] dado82rm:
to make make the safety net work i had to change the ro.build.selinux= to 0

but now i just tried to put it back to 1 and actually is still working

for some reason before was not working and changing to 0 did the trick for me

i am not a developer but just a user

somehow i understood that the problem was this value.

i would say is better if i delete the previous post just in case

---------- Post added at 08:54 PM ---------- Previous post was at 08:43 PM ----------

May i ask also another think.

in google play>settings is showing Certificate Device not certificate

what cause this?

EDIT 2 i did clear data and clear cache on the google play app and it reverted back to certificated nevermind...
[Magisk] loquendomia:
I give up, I tried all the methods and I can not get the SafetyNet.

I have a Huawei P8, GRA-L09.

I tried disabling the USB Debug, activating Magisk Hide, activating Busybox, Hosts, returning them to disable, restarting, turning them on but nothing.

I also tried uninstalling the Magisk and flashing the unSU, reboot and with the phone unrooted the safetynet works (obviously), I flash the Magisk 12 again and safetynet stops working.

I tried using the V9 version because I read that maybe the latest version did not work with the EMUI, I installed the phh superuser, but the safety still does not work.

I went back to the Magisk12 and tried to hide the RootChecker but it did not work, RootChecker still detects root. This gives me to understand that to start the MagiskHide does not work.

I do not know what else to do.
[Magisk] xT-g-K:
Sultan's LineageOS 14.1, Oneplus 3 not passing safetynet. CTS profile mismatch. No idea what to do, didn't even pass after unrooting.
[Magisk] Didgeridoohan:
Sounds like a compatibility issue. Try running this command in a terminal emulator:

sh /magisk/.core/magiskhide/enable

It starts Hide manually, in case it doesn't work through the Manager.

Use an app like SafetyNet Playground and see if you can pass basic integrity. If basic integrity is true it's an issue with your ROM, not Magisk.
[Magisk] xT-g-K:
I passed all tests using safetynet playground. Still not good signing in to pokemon go
[Magisk] Didgeridoohan:
If SafetyNet passes now (what changed, by the way?) it's not an issue with Magisk.
[Magisk] xT-g-K:
I uninstalled magisk, reinstalled and reanbled magisk hide. That seemed to fix me passing safetynet although it is the exact same process I first used when I didn't pass.

I believe others on this ROM have got no issues playing
[Magisk] EkimDaGr3at:
I have Galaxy S5 (Verizon) and finally passed Safteynet with MagiskSU but what did the trick was installing Kernel Adiutor from the play store. I didn't make any adjustments but after installing, I went through the app to review it and kind of felt like I was swimming in deep waters, and for giggles just opened MAgisk and the app showed all green. Even double checked with Root Checker. All apps accessible as well. Using LinageOS 14.1
[Magisk] visceralpsyche:
Mine recently started passing as well. I never associated it with installing Kernel Adiutor but I just installed that too! Nice find :)
[Magisk] justjr:
Mine don't pass but I can play Pokemon and log in Snapchat, go figures!

I just wanted that my credit card "googlepay like" app also worked, but it detects root.
[Magisk] justdidit:
After reading through this thread and conducting my own experiments I can point out to the "Enable Busy Box" setting in Magisk Manager as the reason for SafetyNet failure (CTS profile mismatch) in my case.

My setup (Nexus 5x): clean install of purenexus_bullhead-7.1.1-20170317-OFFICIAL with ElementalX 4.07 and Magisk 12.

Flash procedure: ROM -> Kernel -> Magisk.

Each time after a clean installation of the above mentioned setup I have tested various options and fixes suggested in this thread. Each time SafetyNet failed until I have realized that I was turning on "Enable BusyBox" in Magisk Manager settings. The thing is that after it was turned on it could brake SafetyNet immediately or after a reboot. Additionally, turning it off does not seem to revert whatever changes it makes - CTS profile mismatch will occur. Clean install of the ROM is required to pass the SafetyNet again. Since I have left the BusyBox setting at default "off" I am passing the SafetyNet check without any problems. All apps restored and root privileges granted (EXKM, Titanium Backup and Greenify). I will test this for a longer period of time and report back.

P.S. "Systemless hosts" setting also breaks the check for me but it can be fixed by turning it off - clean ROM flash is not required. Android debugging (on/off) seems to not matter in my case.
[Magisk] Didgeridoohan:
Nice find. Pure Nexus has busybox pre-installed, maybe that has something to do with it...

[MENTION=2808286]xNotta[/MENTION] Something to try.
[Magisk] origitat:
Also, I was failing SafetyNet and realized I also had BusyBox checked but I could uncheck and reboot and started passing again. Definitely better than a clean install thats for sure.
[Magisk] hennymcc:
[MENTION=4176888]reversegear[/MENTION], [MENTION=5188092]justjr[/MENTION]: same for me, I get "1970-01-01 01:00:00.000" with safetynet helper and magisk safety check hangs.

Can you tell me what (exact) ROMs you use? Are you using a stock ROM or a custom ROM like LineageOS and which phone and ROM version do you use?

My phone is a Samsung Galaxy S5 mini and I am on LineageOS 14.1.2.
[Magisk] reversegear:
I'm using custom ROM lineage and RR

Actual issue was in kernel after the update from developer issue is fixed. :)

You can ask for ur device developer to fix it ?
[Magisk] justjr:
What was the problem fixed? Please details so I can ask dev.
[Magisk] hennymcc:
Can you tell me the device (you seem to have two devices: Moto G , LeEco Le 1S) and also the dev?

Thanks in advance.

Edit: [MENTION=4176888]reversegear[/MENTION]: is it WisniaPL from LeEco-Le1S? Then the fix might be somewhere in this kernel repo.
[Magisk] reversegear:
Yes. My device is LeEco 1S

WisniaPL is the developer u can contact him :)
[Magisk] RandomAccount123:
Very Confused ATM

Nexus 5 user here on android 6.0.1 with magisk v12, magiskhide, and magisksu. Using either the magisk manager safetynet checker or SafetyNet Helper Sample, produces similar results. About 50% of the time both the CTS profile test and the Basic integrity test pass, but the other 50% of the time magisk manager will report that a CTS profile mismatch, and SafetyNet Helper Sample reports a basic integrity failure and a CTS profile mismatch. This happens seemingly at random. I can sit there and test it 10 times and have it come up as passing half the time and failing the other half, which is extremely frustrating. I have tried enabling and disabling both systemless host and busybox as was suggested with no difference regardless of whether they were off or on. The worst part of this is honestly the inconsistency, since it makes this much more confusing. Any ideas would be much appreciated.
[Magisk] origitat:
Came here to report this exact thing! Suddenly I found myself being unable to play Fire Emblem heroes and the error code pointed towards SafetyNet failure. Running the test in Magisk Manager will yield a FAIL 50% of the time and a PASS the other times. It is so random. Ive tried enabling CORE only mode, toggling USB debugging, togging busy box, toggling Magisk Hide.

I started to wonder if something funky was going on with SafetyNet. Running S7 Edge
[Magisk] calvinerico:
hey guys.. im using a Sony Xperia Z5, Lineage OS 7.1, Flashed Magisk from recovery and flashed phh's supersu from http://www.theandroidsoul.com/systemless-root-magisk-android/ and i've tried magisk hide test it on a root checker and it worked, but i still get SafetyNet Failed CTS Profile mismatch error.. can anyone explain me? thanks
[Magisk] Bigfella_69:
Samsung Galaxy S5

Lineage OS 14.1 Android Nougat 7.1.2

Magisk says rooted (SuperSu 2.79), but MagiskHide stares not rooted. SuperSu 2.79 not installed. Have tried method listed in thread.

Any new ideas?
[Magisk] Didgeridoohan:
In terms of how Magisk have developed, that guide is ancient. You should not use phh's anymore... Might be a good idea to uninstall and start over with the Magisk zip from the release thread.

Further tips on how to get SafetyNet to pass can be found in the troubleshooting link in my signature.

I'm not sure what you're asking? You haven't installed SuperSU, but the Magisk Manager reports you're rooted with SuperSU? Or? Clarification necessary...

If you're trying to get Magisk Hide to work and pass SafetyNet with SuperSU you can stop. You'll need MagiskSU for that. If this is the case, unroot your device (there's an option for that in the SuperSU app, just make sure to restore your stock boot image when it asks) and reinstall Magisk.

That's not a solution... It's just enabling Magisk Hide. I want my minute back. :p
[Magisk] irahul:
lol some new people dont know this and they think they have problem with magisk hehe :P
[Magisk] nikitis:
OMFG! This worked for me!!!!!!!!! Why the hell wasn't this explained when I installed it?

Do you have any idea what I went through trying to get this **** to work?

I reinstalled my rom like 4 times, then factory image flashed it, Reinstalled my custom rom again!

This should be in HUGE BOLD with 56 pt FONT on the front page!!!!
[Magisk] irahul:
haha dude m glad it solved your problem i know where new people are getting problems of simple solution :P coz i am new too so i made that video :D too many are like us who doesnt knw that and think its some big issue :P
[Magisk] thaianhpsp:
i can't pass Magisk Safetynet although magiskHide, systemless hosts and systemless busybox are all enabled.

how to fix it, thanks all <3
[Magisk] Didgeridoohan:
Details, details, details...

Device? ROM? Root method? Other mods? Upload a Magisk log.
[Magisk] thaianhpsp:
Galaxy S7 g930l superman ROM v2.5

https://xdaforums.com/galaxy-s7/development/rom-s7-rom-v1-0-t3356197

I install Magisk 12 + Root method: Magisk SU in Aroma
[Magisk] Didgeridoohan:
And where's that Magisk log?

Looks like that ROM has busybox pre-installed. Enabling Magisk busybox might cause a conflict that breaks Magisk Hide. Try disabling Magisk busybox.
[Magisk] thaianhpsp:
i disabled Magisk busybox and freezee busybox by titanium backup but it not working :(
[Magisk] Didgeridoohan:
Ouch! Large images hurts my eyes... :( Better to upload the log as a text file or to pastebin or similar (that way we'll be able to see the whole thing as well).

Did you try reboot after disabling Magisk busybox? And why did you freeze busybox?
[Magisk] thaianhpsp:
Yes, i did

but still not working :((
[Magisk] Didgeridoohan:
Could you at least post the entire Magisk log?
[Magisk] thaianhpsp:
I uninstalled and reinstalled magisk but still not working. :(

** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
* Running post-fs-data.d
* Loading core props
* Preparing modules
* Stage 1: Mount system and vendor mirrors
* Stage 2: Mount dummy skeletons
* Stage 3: Mount module items
* Stage 4: Execute module scripts
* Stage 5: Mount mirrored items back to dummy
** Magisk late_start service mode running...
* Enabling systemless hosts file support
* Linking binaries to /sbin
* Starting MagiskSU
* Running service.d
* Starting MagiskHide
MagiskHide: Moving and re-linking /sbin binaries
MagiskHide: Removing dangerous read-only system props
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.boot.warranty_bit'='0'
Existing property: 'ro.boot.warranty_bit'='1'
Recheck property: 'ro.boot.warranty_bit'='0'
Done!
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.warranty_bit'='0'
Existing property: 'ro.warranty_bit'='1'
Recheck property: 'ro.warranty_bit'='0'
Done!
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.debuggable'='0'
Existing property: 'ro.debuggable'='1'
Recheck property: 'ro.debuggable'='0'
Done!
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.secure'='1'
Existing property: 'ro.secure'='0'
Recheck property: 'ro.secure'='1'
Done!
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Starting MagiskHide daemon
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
Zygote(0) ns=mnt:[4026535685] Zygote(1) ns=mnt:[4026535684]
MagiskHide: com.google.android.gms.unstable(PID=6530 ns=mnt:[4026535767])
MagiskHide: Permissive detected
MagiskHide: Unable to set to enforce, hide the state
MagiskHide: Unmounted (/sbin)
MagiskHide: Unmounted (/magisk)
MagiskHide: Unmounted (/system/etc/hosts)
MagiskHide: com.google.android.gms.unstable(PID=6989 ns=mnt:[4026535779])
MagiskHide: Permissive detected
MagiskHide: Unable to set to enforce, hide the state
MagiskHide: Unmounted (/sbin)
MagiskHide: Unmounted (/magisk)
MagiskHide: Unmounted (/system/etc/hosts)
MagiskHide: com.google.android.gms.unstable(PID=12941 ns=mnt:[4026535762])
MagiskHide: Permissive detected
MagiskHide: Unable to set to enforce, hide the state
MagiskHide: Unmounted (/sbin)
MagiskHide: Unmounted (/magisk)
MagiskHide: Unmounted (/system/etc/hosts)
[Magisk] DLloyd:
Ok, so I'm rooted with MagiskSU with Magisk V12 installed. Magisk hide is enabled but I'm still seeing CTS Profile mismatch error...
[Magisk] Didgeridoohan:
https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828

---------- Post added at 11:12 ---------- Previous post was at 11:10 ----------

Everything looks fine in the logs, so you're gonna have to do some troubleshooting. Check my troubleshooting thread if you haven't already:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] Marcuss4:
Hi guys,

I had the same problem and somehow managed to get it working.

Go to developer settings and disable the oem unlock.

After this try the safetynet check again.. it should work (on my phone it did)

Now enable oem unlock in developer settings and you should be fine now.

Hope this helps
[Magisk] UserNamist:
I get this error in the magisk safetynet check but I can download and use netflix just fine.. is it just a visual bug then? (Cant check android pay because i dont have it)
[Magisk] Dentora:
I had this issue on my s7 with superstock rom or superman rom. I fixed it by going back to my carriers current stock firmware installed superstock kernel then magisk. I think it has to do with custom roms based on firmware that doesn't match your model as I have a Canadian S7(W8) all the roms are based of the 930f not W8. But that's just my guess based on my experience.
[Magisk] udinbutuk:
fix safetynet on my xiaomi marsmallow

i just install magisk v.12

and i install supersu 2.76

than i install suhide.zip

i get fix safetynet on my xiaomi miui 8. room marsmallow
[Magisk] Slypnslyde:
For some reason checking for safetynet just keeps going on and on. It never did this before and I have data.
[Magisk] Didgeridoohan:
It's possible that Play services have crashed. Clearing data and force stopping might work (possibly also a reboot).

Could also be some other issue with your setup. Posting a Magisk log is usually a good idea when troubleshooting.
[Magisk] freaky2xd:
i also get the safetynet error :(

what is the problem with my Xperia Z5 E6653?

Android 6.0.1

Magisk 12.0

patched stock kernel (dm verity off, dmr patch, recovery)

deodexed rom

Magisk hide ON

busybox OFF

usb debugging off

still the same errror, even though it was a clean installation....
[Magisk] Didgeridoohan:
Does Magisk Hide work? Add a root app to the Hide list.

Does basic integrity report true? Use a SafetyNet checker from the Play store.

Where's your Magisk log?

And here's some reading:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] freaky2xd:
could it be because of the kernel?
[Magisk] freaky2xd:
ok I reinstalled Android 6.0.1 and flashed a stock based kernel which only difference is that it has a dmr fix and a recovery

then I flashed magisk 12.0

developer options off

magisk hide on (I tested it with Titanium Backup, works just fine!)

so now my phone:

Sony Xperia E6653

Android 6.0.1 rooted via Magisk 12.0

unlocked Bootloader

TWRP recovery

dmr patched kernel

no deodex etc, but it still fails when checking SafetyNet!
[Magisk] Didgeridoohan:
Ok, cool. Now, what about my other two questions?