yashsingh1/xdaforums huggingface dataset:
[Magisk] Terrails:
Is it even worth it to play with the props at this point? From what I tried, its not related to them and it probably goes deeper. Can we still fix this that easily, or will we have to open a issue on github to get help from John? I really don't want us to give him more things to do than he already does, but if it really goes deeper, its going to be hard to figure this out.
[Magisk] TraderJack:
Personally I don't believe props is the issue. I've been reading up on some SafetyNet and while most of it is way above my pay grade, what comes out of it for me is that Google has been holding off implementing more severe checks (i.e. there have been loopholes) that they have steadily over the past few years been strengthening. My guess is part of being able to do this was actual checks/api/code in the software itself, which may be why this is an issue only on later versions of Android?

There is a SafetyNet jar file (snet.jar) that exists, or at least to on older versions - I think they've updated the framework, but there is an equivalent now. This file must contain within it the local calls that performs on a device. It then takes all the results of these checks and sends them to Google's servers where it is validated along with some cryptography and evaluated as to whether the test passes or fails.

So basically, while this is a "server-side" check, it is validating the "local" info that is gathered by the SafetyNet code. I personally believe they have gone beyond just checking the value returned by a "getprop", but rather have different native API calls they can use to query some other part of the OS or worse, the hardware directly (or at least as best they can through a HAL), to determine the status of the system. In this case it seems pretty clear most of us are getting this because SafetyNet is detecting an unlocked bootloader.

My belief is we are going to need to wait for a super-dev to determine what other methods can be used to directly query whether the bootloader is locked and then determine how we might return different results to SafetyNet. I am predicting that a solution is probably going to have to be in patching the boot image or kernel to return false results.

As to posting a bug for [MENTION=4470081]topjohnwu[/MENTION] - I don't know if he has time and if this is really something that he wants to devote time to (I'm sure he could figure it out given enough time, but it might not actually be his area of expertise). I suspect until this issue gets worse and starts effecting more users it won't get more attention. That could conceivable be several months (or more) - if it gets fixed at all.
[Magisk] Terrails:
Yeah, just along the lines of what I thought that they did. I guess my only option is to revert to stock ROM with locked bootloader until this situation gets resolved. This will most likely become a bigger problem soon-ish and some devs will hopefully jump in to help...
[Magisk] Some_Random_Username:
OnePlus 5 updated fingerprint: OnePlus/OnePlus5/OnePlus5:9/PKQ1.180716.001/2002242003:user/release-keys__2020-02-01

OnePlus 5T updated fingerprint: OnePlus/OnePlus5T/OnePlus5T:9/PKQ1.180716.001/2002242012:user/release-keys__2020-02-01
[Magisk] Ardacer:
My thoughts exactly. Was wandering if it makes sense to ask guys at xiaomi.eu to make a kernel patch. I've even pondered finding and installing software to see what's going on, but I probably don't have the skills.
[Magisk] imsaguy:
He's always shown an interest in the past with keeping up with Google. He was doing work on his Pixel 4 with regard to all of their new changes. My guess is that Google will start locking down all unlocked bootloaders, we're just the first to notice it because the other oems tend to lag behind on their updates a bit.

We just have to be patient and let John and the others work their magic.
[Magisk] alex.do:
Gosh..... why this happens just one week after i got root? one week? why? already gave up knox and now safetynet ?????
[Magisk] imsaguy:
At least we now know who to blame... :cool:
[Magisk] yazakachka:
Moto X Play XT1562 fingerprint submission

[MENTION=4667597]Didgeridoohan[/MENTION] could you add Moto X Play fingerprint to the module?

lux_uds:/ $ getprop ro.build.fingerprint
motorola/lux_retasia_ds/lux_uds:7.1.1/NPD26.48-24-1/1:user/release-keys
lux_uds:/ $ getprop ro.product.manufacturer
motorola
lux_uds:/ $ getprop ro.product.model
XT1562
lux_uds:/ $ getprop ro.build.version.security_patch
2017-09-01

Device info:

Moto X Play, XT1562, lux

Android 7.1.1 retasiaall

Kernel 3.10.49
[Magisk] wilsonhlacerda:
For you all know:

Play Store updated itself on 9/mar

I updated LOS16 now with March patch

SafetyNet and Certified Device continue all fine, all green.
[Magisk] alex.do:
nah cts still false on mine.
[Magisk] Didgeridoohan:
So, bit of an update on the whole CTS thing...

There are indications that Google might be using hardware key attestation now. Which would be bad news, since that is unbreakable (unless there are serious flaws in the implementation).
[Magisk] Biggest_Noob:
Some new devices are still certified and some not
[Magisk] Biggest_Noob:
Realme 3 pro

Lineage os 17 Feb security patch
[Magisk] Didgeridoohan:
Could be that those that pass doesn't have the hardware properly implemented...

Like I said, it's just an indication so far.
[Magisk] TraderJack:
Not like we haven't known this was coming for 2 years (Nougat). I'm pretty sure you're right and I'm also pretty sure no fix is forthcoming, perhaps ever.

I'm still trying to read up about this. Wondering if possible that the entire API response could be spoofed by intercepting the app calls... But that's another can of worms.

Going to be interesting to see what more starts leveraging the ctsProfile checks....and more and more stuff stops working...:sigh:
[Magisk] Scunkanełi:
John confirms that SafetyNet now uses key attestation

https://twitter.com/topjohnwu/status/1237656703929180160?s=19
[Magisk] PixelPro:
Wow! This is bad news! Very, very bad news!!! If properly implemented, hardware backed cryptography is virtually UNBREAKABLE!!!
[Magisk] nri_tech1183:
I have unrooted my phone aka removed magisk completely but seems safetynet check fails on root checking apps.

Seems this time google fked it very hard this time....

Can Unlock bootloader also trigger safetynet check?

All apps working fine except Ola cab app. It keeps saying since this week:

FAILURE! SORRY SOMETHING WENT WRONG PLEASE TRY AGAIN.

or

THE OLA APP IS NOT AVAILABLE FOR USE ON THIS DEVICE.

Its a sheer shame that Gpay and banking apps are working without issues and this Ola apps refuses to. I tried clear data, uninstall reboot bla bla and even tried Dec 2019 version but same issues.

Can someone comment on some help here....
[Magisk] Micdu70:
Hello, yes SafetyNet checks Bootloader state...

No solution (actually, maybe never...). If you want to use some annoying apps based on SafetyNet "ctsProfile" security check, you will need to relock your bootloader... :(
[Magisk] nri_tech1183:
I got an update via GitHub then even re-locking bootloader wont help now..
[Magisk] crok.bic:
After you unlocked the bootloader I presume you installed a custom recovery, right? More than likely TWRP.. Some developers like Niantic (Pokemon Go and Ingress Prime) are actually looking for "suspicious" files and folders that are indirectly telling them that something has been modified on the phone, one recent thing is to look for a directory called TWRP.. if you have it more than likely your phone is "not intact" in terms of "cleanness" if you know what I mean.. try to rename that folder to something else and retry.

Did you ever run RootBeer Sample with the same settings as you try to run Ola app (I mean Magisk Hide is enabled and you already hide Magisk Manager) to check what it says about the phone's settings?

Just my two cents..
[Magisk] nri_tech1183:
Here is rootbeer along with root checker etc. evidences..

I found twrp folder in Internal memory and renamed it still no go!

But if the root has gone why will such folders even bother? Any more folders to look for?
[Magisk] siroga825:
I just did relock bootloader on poco f1 yesterday and it passes everything without issue.

But i quickly remember why i hate xiaomi phones so much, UI is just trash so i unlocked bootloader again and its failing again..
[Magisk] GizmoTheGreen:
Hey thanks for mentioning this app.

My phone clears this apps test. Banking works. Google pay works. Pokemon go works.

But McDonald app stopped working saying I'm probably rooted and won't let me use my points anymore :(
[Magisk] nri_tech1183:
By relock you meant you flashed stock rom right and didnt relock on ac custom rom?
[Magisk] siroga825:
As far i know you will brick your phone is if lock bootloader with not stock rom,recovery,..

So yes, i did flash stock rom combo (rom,vendor, recovery,....) And lock bootloader, and its working just fine, passing safetynet without issue.
[Magisk] imsaguy:
Does relocking trigger a data wipe or just the unlocking?
[Magisk] siroga825:
Yes, it wipes everything. Basically reset phone to "from the box" state.
[Magisk] imsaguy:
Installing the March update caused my phone to only boot fastboot until I factory reset. I just now got everything set back up. Another reset is going to suck. :(
[Magisk] hyborian:
My solution is to just buy another low cost but good performance locked phone for problem apps that I cannot live without, like banking apps. Then the fun continues with my rooted phones. Fortunately, for now at least, my banking and other financial/payment apps all work, unless I don't put them inside Magisk Hide. They probably don't check CTS, but something else, for now.
[Magisk] alex.do:
Uh oh this hurts so bad :(
[Magisk] pbanj:
here is the newest fingerprint for the nexus 5x

google/bullhead/bullhead:8.1.0/OPM6.171019.030.E1/4805388:user/release-keys
[Magisk] VincentJoshuaET:
I'm using the Global Beta 8.7.5 ROM.

---------- Post added at 05:12 AM ---------- Previous post was at 05:10 AM ----------

I flashed the Universal SafetyNet Fix and ctsProfile passed. I decided I don't want to go into the hassle of custom software so I just went back to full stock and relocked the bootloader, and stop caring about SafetyNet
[Magisk] VincentJoshuaET:
The one from the MagiskHide Props Config module. Did you flash the Universal SafetyNet Fix?
[Magisk] Okutue:
Hello, I updated to the latest version via Magisk Manager and after rebooting, props can't be found from terminal emulator.

And I lost both safetynet and integrity test.

I'm running LineageOS 15.1 June build on my Lenovo K6
[Magisk] Didgeridoohan:
Start by providing everything mentioned here (manually of course, since you can't run the props script):

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs-etc
[Magisk] Okutue:
Here are the logs

https://drive.google.com/file/d/12LDGN5GfCDnY5fLALDj6jugQ9aviDb6_/view?usp=drivesdk
[Magisk] Okutue:
I have attached the Logs.

Things to note, my phone is encrypted and SELinux is set to permissive, if it helps.
[Magisk] Kywrosaki:
No pass safety
[Magisk] VincentJoshuaET:
Weird: I wiped data and started from the beginning, flashed Magisk 16.6. After the first reboot (after setting the fingerprint), ctsProfile passed. But after some time (didn't even reboot), ctsProfile fails again. A reboot didn't fix it.

---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------

I see that the build description isn't changed. Is that normal?
[Magisk] Ramzir1:
s5 g900h

s5 g900h Why is there no brother?
[Magisk] kullurumanoj:
Heyy man I tried the steps..still CTS is failing, Do you want me to attach Logs?
[Magisk] Okutue:
Never mind I figured it out.

It was caused by my data being encrypted as well as my internal storage.
[Magisk] Ramzir1:
s5 g900h

samsung/k3gxx/k3g:6.0.1/MMB29k/G900HXXU1CPF2:user/release-keys

---------- Post added at 02:24 PM ---------- Previous post was at 02:18 PM ----------

I'm installed Rom LineageOS 14.1 android 7.1.2

I can not find my phone on the model MagiskHide Props Config

samsung/k3gxx/k3g:6.0.1/MMB29k/G900HXXU1CPF2:user/release-keys

s5 g900h

Who knows the solution
[Magisk] VincentJoshuaET:
I tried the Universal SafetyNet Fix. It makes Magisk not detected as installed, but ctsProfile passes. Maybe you can implement some other things from there? Thanks!

---------- Post added at 03:07 PM ---------- Previous post was at 02:45 PM ----------

Update: just tried this - https://xdaforums.com/apps/magisk/xiaomi-safetynet-fix-t3600431/post76776696

Works great. MIUI 10 Global Beta 8.7.5
[Magisk] Felix Siahaan:
I didn't flash Universal SafetyNet Fix.

MagiskHide Props Config is enough and worked great for me.
[Magisk] LinuxPanda:
Could you please add support for moto c series fingerprints. Thanks.
[Magisk] Didgeridoohan:
Ok, so you've got it solved then... Strange that /data and the internal storage being encrypted would cause this. In your log there's an issue with mounting the system mirror, and therefore Magisk has issues mounting the props script to /system/xbin.

06-23 01:28:48.679 434 1938 E Magisk : mount /dev/block/platform/soc/7824900.sdhci/by-name/system->/sbin/.core/mirror/system failed with 16: Device or resource busy
06-23 01:28:50.094 434 1938 E Magisk : opendir: /sbin/.core/mirror/system/xbin failed with 2: No such file or directory

That should not have anything to do with /data encryption... Ah well, you got it sorted. Gift horse, mouth, and all that... :good:

From your log, you are currently not using a certified fingerprint from the module. You did, but then you reset the module and everything's back to stock. Did you at any point pass the ctsProfile? What is your device and ROM details? Are you by any chance using MIUI China ROM? Etc...

That is interesting... I'm intrigued by how MIUI works. It is not an easy OS to work with... Trying to figure a few things out about it, but it isn't easy. Not changing the build description is normal. So far it is not necessary for passing the ctsProfile check.

I'm not interested in implementing the solution used in that module. I'm more inclined towards figuring out why it sometimes has success, when MagiskHide doesn't and thereby making Magisk more robust. But that's a future project...

Logs would be awesome. One more thing you could try before we continue on is to change the boot stage to post-fs-data in the prop settings and then reboot, to see if that makes a difference.

The reason why there's no Samsung Galaxy S5 in the fingerprints list is quite simple. No-one has provided me with a working certified fingerprint yet... Is that one certified (I'll test it when I get a chance, but you might already have the answer)?

If you could provide me with a certified fingerprint I'd be happy to include it.
[Magisk] kullurumanoj:
[MENTION=4667597]Didgeridoohan[/MENTION] I do remember ... Safety net passed with some version of miui china rom and the problem is I don't remember it which version it is!! I will try to find the version...so that it would be easier for you to fix the issue..In b/w I will be waiting for your custom props list...I mean you said you will provide some more custom props to know which one is causing the issue.

Thanks

Manoj
[Magisk] Didgeridoohan:
I've got a couple of more props to test, but the logs and a report if changing boot stage to post-fs-data first would be very helpful.
[Magisk] kullurumanoj:
I have attached the logs before n after changing the boot stage to post-fs-data
[Magisk] nri_tech1183:
I know that very well, was just confirming as these days anyone can come up with any weird ideas surprisingly working out of nowhere...
[Magisk] siroga825:
Thats really sad news from topjohnwu, but there is exposed solution for pass it, so how do it work? It just fake screen or it really make device pass test?

//Edit

Nvm, just look up to topic again and it seems like it dont work anymore (or on some devices) and ones that pass are just fake-reporting
[Magisk] Harmonics:
Out of curiosity, couldn't you redirect the safetynet call to a patcher instead, like you can do with IAPs? (I hope mentioning it vaguely won't cause any troubles, just wanted to give an example.)

Or would that require a lot of work or rather make it near impossible, due to having to decrypt the data first?
[Magisk] crok.bic:
Oh heck, just realised that you have a Pixel phone and it seems that the March sec. patch introduced a new way of working of SafetyNet - so that's why your device is considered rooted/failed..
[Magisk] eg1122:
The March security update didn't cause the failure. It was a switch on Google's end. Older devices have a buggy or incompatible implementation of the new detection so that's why they still pass.
[Magisk] crok.bic:
Sorry, I did just mean it happened at the same time, you are right.
[Magisk] tech_head:
An unlocked BL triggers a fail.

A custom kernel can hide the BL unlock status. ElementalX hides the status.

---------- Post added at 01:13 PM ---------- Previous post was at 01:09 PM ----------

I guess, I won't be updating my OnePlus 7 Pro anytime soon.

Root is more important than an update.
[Magisk] sliding_billy:
I have Elemental on my wife's Pixel 3 and Unicorn Blood on my Pixel 3 XL, they do not hide these new checks. CTS fails.
[Magisk] pndwal:
Yes. And since making SafetyNet reliable (read useable) for security purposes is clearly G's goal, more and more Apps (banking etc) will surely switch to using this, rather than their own custom methods, to detect customised devices in short order. PW
[Magisk] Iceman248:
Does the OnePlus 6T still pass SafetyNet?
[Magisk] WsaENoTsoCK:
Does this no longer works for Xiaomi Mi8????
[Magisk] Professor:
I have a question, I am using pixel3xl props, in magisk manager, as a module.. can I use this module to pass CTS ?? My playstore is not certified.. will this make it certified?
[Magisk] alex.do:
my samsung s10+ was getting cts fail just couple days ago. also got device not certified in play store settings.

just now flashed the latest march firmware update. the device not certified in play store settings gone. maybe google moved it to somewhere.

cts still fail no matter what.

its true guys. google just makes sure of that.

no. more. green.
[Magisk] Harmonics:
There is no way to pass safetynet check in the playstore at present time. The only way is to completely remove root and everything and lock the bootloader.
[Magisk] Marco89989:
does "re-locking" force a complete wipe? or only "un-locking"?
[Magisk] biikman:
It will wipe phone.
[Magisk] aleMarvel:
is terrible... mario kart, home alarm and mc donald don't work for me.. terrible
[Magisk] garylawwd:
Ehm what are you trying to achieve with a post like that?

Blame Google for that. They changed safetynet so it will detect an unlocked bootloader, so unless you are completely stock you won't pass safetynet anymore and probably never will again in the future according to the magisk Dev himself.

Hiding root is no more unfortunately
[Magisk] virags:
Do i have to unroot and relock bootloader? Or only relocking bootloader is enough? I am ok for a full wipe.
[Magisk] siroga825:
You need to go full stock and relock bootloader.
[Magisk] OhioYJ:
He did list some other possibilities, so nothing is impossible. Guess at the moment I will enjoy my OnePlus that still passes (unlocked, LOS 17, using this module) I'm guessing someone will come up with some other work around. Give it some time. Either way, I don't see any app worth running stock software for personally.
[Magisk] aagha:
Curious if you've tried to uninstall this module and if you still past SafteyNet.
[Magisk] OhioYJ:
I've never checked without it, I've always used the module as if I don't there are apps that don't show up in the play store for me. Same for my other devices, which aren't OnePlus devices. I also still use Samsung and Hauwei devices as well. Have to check those when I get back home and see if there has been any change.
[Magisk] mr3p:
Correct, it no longer works to pass CTS on Mi8 just as most other devices.
[Magisk] Nothex:
Sorry for the noob question: but is it possible to use this module to edit default build prop settings, for example the default Wi-Fi scan interval? I've read through the documentation and don't see a way how to do this, am I missing something? Thanks in advance.
[Magisk] pndwal:
Well yes, but not quite true re hiding root. Your phone won't pass rooted or not, and root can still be hidden. New SafetyNet hardware attestation is returning bootloader status, not root status. This according to the magisk Dev himself:

https://mobile.twitter.com/topjohnwu/status/1237830559365136384

It occurs to me that if someone can find a universal way to lock bootloader but keep custom ROM and root (apparently possible on a few devices), we'd be sweet. I'm no expert, and this will probably prove to be wishful thinking. But we can dream.... :) PW
[Magisk] hyborian:
Yes, you can. su, props, select no. 4, then follow instructions on the screen.

in my case, i have to put wifi_scan_interval at late_start boot stage to stick, YMMV.
[Magisk] hyborian:
At Telegram Pocophone channel, someone has found a way, for now at least. Specifically for Pocophone, we just flash a zip and voila, Magisk Safety Net shows true. No exposed or anything.
[Magisk] hyborian:
I just read more about it, it was simply flashing stock persist.img to regain ctsprofile: true, a temporary solution which is holding up so far.

"A blessing in disguise. A guy got his storage corrupted, flashed stock persist.img and passed ctsProfile :yum:

This zip will backup your current persist partition to /sdcard/persist_backup and flash stock V11.0.6.0 persist.img. That's all. Use at your own risk!

This fix is disabling L1 cert, it's L3 after flashing. If that is more imp to you than SafetyNet, do not flash. We're looking for a fix."

Looks like L3 does not go through TEE cryptography, so safety net passes.

What are these certificates - https://www.google.com/amp/s/www.androidauthority.com/widevine-explained-821935/amp/

Video how to flash it, and uses props too to change fingerprint - https://www.youtube.com/watch?v=uIQEgnl3y0E
[Magisk] Nightf0x_007:
Pixel 2 xl here

If i returned back to feb. Update from march update will i pass safetynet or its now in general for all unlocked bootloader devices?
[Magisk] hyborian:
won't pass
[Magisk] unknownz:
tested and confirm that this method works in passing ctsProfile check running on Pocophone with PE rom
[Magisk] siroga825:
You did backup? I dont see this partitions on my phone.. using last twrp

//Edit

So i just flash it without backup, and ctsprofile is true, but no other changes, mcdonalds still write same msg like before and everything else seems to work just the se as with ctsprofile fail

//Edit

Ok, i did take few restarts and clearing cache and it seems fine
[Magisk] aleMarvel:
i not understand, what is L3 ?
[Magisk] pndwal:
Widevine Digital Rights Management certification (explained in the reference you quoted!):

So flashing older persist solution may be a catch-22.

I'd be interested if the solution works across a range of devices however. It may be that persist images that allow L1 as well as CTS pass exist. PW
[Magisk] unknownz:
did not do any backup and McDonald's app work just fine for me

Edit 1: Magisk Hide was enabled for the Magisk app itself and McDonald's app. After enable, the McDonald's app Storage and Cache was cleared
[Magisk] hyborian:
L3 - you only get 720p resolution when watching netflix for example

L1 - 1080p

---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------

Did you hide mcdonalds in magisk hide ? Other than that, i dont know why.

---------- Post added at 11:31 AM ---------- Previous post was at 11:00 AM ----------

It's not an older persist, but a persist with a lesser certification, which google still has to accept since some phones dont have the Hardware for L1.

It should work beyond pocophones, in theory.