yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
I suspect that it shouldn't make a difference, but please report back with your findings.
[Magisk] ZellZoy:
Just tried this since my cts started failing recently. Is it supposed to start showing success for the test in Magisk if it worked correctly?
[Magisk] EVR_PR:
I know your fingerprints work, that's why I tried to use the February one again.

Before they re-uploaded the March AT&T build and you updated the fingerprints list, I was using the February fingerprint with the first March build that they pulled and CTS passed. The new build is what's broken even further because now the February fingerprint doesn't even work anymore.

?
[Magisk] hyborian:
Will report back after a few days. This problem of Magisk SafetyNet may take a long time to fix or never.

So far, this holds true :

" It will still appear as Uncertified, but doing this method will whitelist your device and bring back most of the functionality."

No problems downloading apps, or updating. And the Registration page of Google now shows all 3 of my 3 phones' Registered IDs, irregardless of phone used, as I use only one Google Play Store account for all my phones.
[Magisk] infamous_black:
I removed your module and registered my device and I can now use gpay but still says device is uncertifed and doesn't pass ctsprofile.
[Magisk] hyborian:
You must be talking to the dev ...

Anyway, that is what is to be expected when registering I guess, ctsprofile will not pass and still shows uncertified, but Google whitelisted our registered devices now.
[Magisk] eg1122:
First I'm going to state the following. I use edxposed, I know this tool will not hide edxposed. I was having the same issue passing ctsProfile as others have. I removed edxposed and same issue, figured it was an update to Safety Net or something else causing the issue. Now with that said, not sure if this will be helpful or not to those trying to figure out what is causing the ctsProfile false reading. I reinstalled edxposed and installed HiddenCore module and now I'm passing safetynet. This is in an unlocked pixel 4xl running March ota.

Just wanted to point out that previous to this I had safetynet passing by hiding everything I had hidden in magisk in edxposed as well. Maybe something in that module will help figure out what is causing the ctsProfile mismatch.

https://repo.xposed.info/module/com.cofface.ivader
[Magisk] wilsonhlacerda:
The main point is: how far can we trust HiddenCore? It is closed source, old thread on it here in XDA suggests it may be malware, or can be just a cosmetic thing by hooking magisk/system when reporting green SafetyNet.

I really don't know, but I prefer not to use it.

By the way, here SafetyNet and Certified Device is all ok, all green. At least yet ;)

Same for Rootbeer Fresh.

Samsung S4 Active I9295

LOS16, Android 9

February patch

Magisk stable 20.3

Magisk Hide Props Config 5.2.4-80, S4 Active fingerprint

EdXposed 0.4.6.1 (NO root / SafetyNet hide module)

Play Store last updated 29/feb

Play Services last updated 4/mar
[Magisk] djy:
Pixel 3XL ctsProfile: false after adb flash-all (no wipe) with Google March firmware. Patched boot.img with Magisk 20.3 on Beta channel. Never had an issue passing SafetyNet with this procedure until March firmware. Tried using this module but did not work.
[Magisk] ammmze:
I just did the same thing on my Pixel 3 XL. I had kept putting off the system updates, so did a flash all without wiping jumping from Oct or Nov 2019 to Mar 2020. And i'm seeing the same `ctsProfile: false`. But seems like pogo is still fine with it...for now. Haven't tried gpay, but usually I don't have issues with gpay since i use a wearOS watch thats not rooted or anything.
[Magisk] mizunomidori:
Yesterday I kept getting support 106 & connection error while playing a game called Dragalia Lost. I checked magisk and the ctsprofile is false, then I tried to find a way to solved it with modules, already tried most of working prints but cts still broken. Then I try the Xposed method and it works, all the safety net chek are true. I'm so happy but when I open the game I'm still getting connection error message. I'm no expert with magisk & modules so I tried to do my little experiment. I flashed to stockrom, install magisk manager on my unrooted device to do the safety net chek. Safetynet check is fine so I tried to install the game and connection error is gone. Then i do the same thing after unlocking my device, cts profile is false and the connection error is back when I open the game. So I guess there is a new unlocked bootloader check or something?
[Magisk] Scunkanełi:
Hm are you sure about it being closed source? Maybe someone skilled could take a look at this
[Magisk] wilsonhlacerda:
It used to be:

https://xdaforums.com/xposed/modules/hiddencore-module-doing-t3903984

Well, if it seems open now I'd suggest to better/deeper investigate its code and build from source before using it. At least by some recognized developer.
[Magisk] virags:
Hello I am using a Rooted S9+ , trying to resolve CTSProfile false flag on magisk. I installed Busybox for Android NDK ( from magisk downloads) and restarted my phone. Yet when i run the "props" command , i get a message saying "No Busybox installed". Any guidance is appreciated.

Below is the install log when installing busybox from magisk.

- Copying zip to temp directory

- Installing Busybox_for_Android_NDK-1.31.1(13112).zip

Busybox Installer Script

by osm0sis @ xda-developers

Mounting...

Extracting files...

Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip

creating: META-INF/

creating: META-INF/com/

creating: META-INF/com/google/

creating: META-INF/com/google/android/

inflating: META-INF/com/google/android/update-binary

inflating: META-INF/com/google/android/updater-script

inflating: README.md

inflating: busybox-arm

inflating: busybox-arm64

inflating: busybox-mips

inflating: busybox-mips64

inflating: busybox-x86

inflating: busybox-x86_64

inflating: install.sh

inflating: module.prop

Installing...

Using architecture: arm64

Using path: /dev/tmp/magisk/busybox-ndk/system/xbin

Cleaning...

Creating symlinks...

Unmounting...

Done!

Just wanted to add when i goto Magisk Module i see the below :

busybox-ndk

(No Info Provided)

(No Info Provided)

(No Info Provided)
[Magisk] MrBrady:
I question the accuracy of that article. The device isn't blacklisted. It just means that there was something that triggered a security warning, like CTS. I've had this happen before when not installing Magisk and having unlocked bootloader detected. This solution not longer works, but installing Magisk and clearing Play Store data fixed the certification for me in the past. The new CTS issue is something different.
[Magisk] Didgeridoohan:
Yes, certifying you device with Google will make it possible to use Google apps even though you can't pass CTS and as a result your Play Protect status will be uncertified. But that's about it. Other apps that truly on a certified device won't be affected.

HiddenCore, to my understanding, simply fakes the CTS test result on-device rather than letting Play services get the result from Google's servers. That's why you can pass CTS with that module no matter what.

That's what's been discussed a lot the last couple of days. Something has been updated, likely on the Google/server side and now a lot of devices can no longer pass CTS. It's got nothing to do with the device fingerprint, but possibly some other prop that Magisk isn't currently changing. Which prop? That's what someone needs to find out...

Did you install Magisk and make sure that MagiskHide was active after unlocking? If not that result would be expected since CTS should fail if the bootloader is unlocked.

MagiskHide changes a few props to hide the bootloader state, but there's a possibility that there's now some new prop that is checked that we haven't yet figured out. If you did that last test with MagiskHide active it's a good hint.

The install of the Busybox module failed... No idea why. You can try installing again.

You can test of Busybox is working by running the command busybox in a terminal emulator.

But, for now this module likely won't help with passing CTS since it seems like Google has updated their checks (and it probably isn't related to the device fingerprint). If you get Busybox up and running you can of course give it a go since there are devices that aren't affected. So far those devices seem to be a bit older though...

Actually, even if you can't get Busybox running you should be able to set the module up using a configuration file. Check the docs for details:

https://github.com/Magisk-Modules-R...nfig/blob/master/README.md#configuration-file
[Magisk] GTMoraes:
Oh man, I just completely wiped my phone thinking I've tripped something when messing with stuff.

However I do recall having it pass CTS when I first installed this ROM (Pixel Experience, March 5 2020 sec update) yesterday. Managed to even get a Certified on Play Store and activate some cards on Google Pay.

Maybe some kind of delayed check, somehow?
[Magisk] virags:
Ok thanks let me try without busybox, FWIW when I type busybox in the terminal I get the below

$ busybox

BusyBox vl . 31 . 1 (2020 -01 -30 13 : 05 : 53 UTC) multi - call bina ry

BusyBox is copyrighted by many authors between 1998-2015.

Licensed under GPLv2. See source di.std.bution for detailed

copyright nob.ces .

Usage: busybox ]function jarguments] . . . ]

or : bu sybox - -]i.st ]- fu]]]

or: busybox --i.nsta]] ]-s] IDIR]

or: functi.on jargumentsl . . .

BusyBox is a multi.-call bi.nary that combines many c

ammon Unix

uti.li.ti.es into a single executable. Most people wi

11 create a

li.nk to busybox for each function they wi.sh to use

and BusyBox

will act like whatever it was invoked as.
[Magisk] mizunomidori:
Ah I see, at that time I only unlocked my device without rooting it just to check if I could run Dragalia Lost on unlocked device or not, and the result is fail. Somehow the game server won't let me in after unlocking my device. Knowing the only way to hide unlocked device status is Magiskhide I decided to root my device again, actived Magiskhide and nothing changes, ctsprofile still false and I'm still getting error message when I open Dragalia. Now here I am, back at the first state of error can't decide wether to gave up on Magisk or Dragalia. :/
[Magisk] zyokuro:
Having the same "support code 160" error here too. This is only a speculation on my part but the only way of being able to access Dragalia Lost server again is probably by relocking bootloader of your phone which would essentially factory reset the phone and wipe all current data. Not worth the hassle to test it out. We can wait it out till the ctsProfile issue gets any fixes (IF there's even a chance to fix it) even though we'll miss out on current events and login bonuses.
[Magisk] ZellZoy:
Unfortunately not no matter what, it has stopped working too. It's what I used to use and I came across this thread when it stopped working a few days ago.
[Magisk] fgprodigal:
I'm also playing this game, this game will check safetynet every time you login, it's insance. I can't play this game for several days because of cts profile :crying:
[Magisk] OhioYJ:
[MENTION=4667597]Didgeridoohan[/MENTION] I believe this is what you need for new devices? If I missed something let me know. I updated both these fully and pulled this data.

--------------

Samsung Tab S2

--------------

getprop ro.build.fingerprint:

samsung/gts210vewifixx/gts210vewifi:7.0/NRD90M/T813XXS2BSJ3:user/release-keys

getprop ro.build.version.security_patch:

2019-08-01

getprop ro.product.manufacturer:

samsung

getprop ro.product.model:

SM-T813

---------------

Samsung Tab S5e

---------------

getprop ro.build.fingerprint:

samsung/gts4lvwifixx/gts4lvwifi:9/PPR1.180610.011/T720XXS1ASL3:user/release-keys

getprop ro.build.version.security_patch:

2020-01-01

getprop ro.product.manufacturer:

samsung

getprop ro.product.model:

SM-T720
[Magisk] Khep:
SafetyNet CTS Profile: false

Hello everyone,

Have a Xiaomi Mi A2 rooted with TWRP and Magisk and everything was fine. I actually used Google Pay (via web) to add some money to my account, and since 2-3 days ago, the phone no longer certified. Magisk SafetyNet report CTS Profile = false (the other is OK), so installed both Busybox + MagiskHide Props Config + Smali Patcher, and even run PROPS via terminal to update the fingerprint, but it didn't work

I even downgraded from Pie to 8.1 and retried everything, but still it's failing.

Some things I have already done:

1. Downgraded to stock 8.1 (V9.6.17.0.ODIMIFE_8.1), installed the aforementioned modules, rerun props.

2. Disabled USB debugging

3. Cleaned up Google Store data

4. Added Google, Google Store and Service Framework to the HIDE list in Magisk.

5. Deleted TWRP directory, as well as the google.gsm one

6. Turned OFF/ON Magisk Hide, as well as tried Magisk Core

7. Enabled the Systemless Host option

7. Tried the 2 extra modules mentioned in: //magiskroot.net/bypass-safetynet-issue-cts/

(not sure if it's OK to have all those modules installed in tandem, though)

I also noticed that one of those extra modules disabled Option 1 of the PROPS, and I think it assigned a Huawei value in the fingerprint, so decided to remove both

and rerun Option 1 to reapply the MiA2 fingerprint. Also, changed the BOOT stages for the finger print, but neither made any change.

The documentation of this one, says something about updating the ro.build.version.security_patch value if was created after March 2018.

But still not sure how it is done. I'm using a stock image. Should I directly change the file where that value is stored??

Checked the logs, but the only odd line was (not sure how to attach the file):

2020-03-07 21:50:07:515956664 - No configuration file.

Any help is very much appreciated
[Magisk] MrMundy:
oddly, safetynet passes with google pay working on my essential phone (feb update, magisk 20.3)

but on my brand new pixel 4 that i got just 2 days ago (march update, magisk 20.3), CTSprofile is false and i cant add any cards to google pay.

im not an AT&T user by the way so the AT&T update that broke google pay is out of the question.
[Magisk] fgprodigal:
safetynet passed on my OnePlus 7 Pro, but failed on my new Xiaomi Mi 10 Pro
[Magisk] virags:
Does having an encrypted device halt androids ability to use busybox or magisk modules? I am thinking maybe that is why this module is not able to detect my busybox?

My main problem is starting yesterday , only my outlook and microsoft apps are not working stating a Google Safety issue.. everything else is working as expected. I can install new apps from play store no issues.
[Magisk] Harmonics:
Curiously this app tells to lock the bootloader, not to remove root or anything else. I'm using magisk hide on it. Perhaps it's only the typical response of the app and can only be taken with a grain of salt, but then it could just show something that more people are familiar with, like root?

The app in question is:

https://play.google.com/store/apps/details?id=com.flinkapps.safteynet
[Magisk] Didgeridoohan:
Locking the bootloader with Magisk still installed could in theory (DON'T) help rule out if it is the bootloader that is triggering the CTS profile check.

BUT! You should never lock your bootloader when you've modified your device in any way. There's more than a good chance that you won't be able to boot again...

Hi there.

With the current SafetyNet issue where many users can't pass CTS, none of the modules that change the device fingerprint will help. It's something else that's causing it...

Some devices pass, some don't. As soon as I have a moment I'm going to sit down and analyse the prop files some users have posted recently, to see if I can find something related to this.

If you two actually could post the module logs for both the device that passes and the one that doesn't I will have a little more to work with. :good:

That's curious that you do seem to have a Busybox installed somehow... Judging from you last post it's not the one from the Magisk repo though. What happens if you run the following command:

which busybox

Yes, there was a similar report earlier in the thread, which is why I'm going to at least investigate a little further into the possibility that the there's a new prop check for the unlocked bootloader. Could be a red herring though...
[Magisk] MrMundy:
im only using youtube vanced and system hosts on my essential and safetynet passes without a hitch, so im not sure if im able to help:angel:

i have no idea how to use this module anyway so i've never installed this before. :silly:
[Magisk] Didgeridoohan:
Well, if you could run the following command on both devices then and post the file (pleases name them according to the device) that would be great:

su -c getprop > /sdcard/<file name>.txt
[Magisk] zyokuro:
Leaving the prop data for my Pocophone F1 here

getprop ro.build.fingerprint:

Xiaomi/beryllium/beryllium:10/QKQ1.190828.002/V11.0.4.0.QEJMIXM:user/release-keys

getprop ro.build.version.security_patch:

2020-01-01

getprop ro.product.manufacturer:

Xiaomi

getprop ro.product.model:

POCOPHONE F1

---------- Post added at 07:50 AM ---------- Previous post was at 07:38 AM ----------

Here's the logs pulled using the props command

drive(dot)google(dot)com/file/d/1XDwiVo_W9xqB1mzyAPNPCfRUB-OpClrW/view?usp=drivesdk
[Magisk] oslo83:
+1 with CTS check failing on Honor10, HuaweiMediapadT5 and HuaweiMate20pro

:/
[Magisk] Harmonics:
It could be...

I just booted up my old Redmi 4X which is on Android 7. SafetyNet is passing completely fine there, with updated play store and google apps and magisk and everything. I compared the getprop of my Redmi Note 8 Pro (Android 9) with it and the latter has a way longer list? The Redmi Note 8 Pro has 1334 lines and the Redmi 4x only 563. I doubt that it's solely related to the Mediatek processor in RN8 Pro, so does google maybe check for more things on newer versions of android only? That could explain why some devices still work.
[Magisk] nanangallail:
Hi I know there is something problem with ctsprofile. I just want add an information from devices I have, btw all my phones are manufactured by Xiaomi.

1. Mi 9T Pro (Latest Miui, android 10, no magisk, unlock): Fail

2 Redmi Note 7 (Latest Miui, android Pie, Magisk, Unlock) : Fail

3 Redmi note 5/redmi 5 plus ( Latest Miui, android Oreo, No magisk or root from very beginning I purchased it, Unlock bootloader because it is from unofficial mi distributior) Fail

4. Redmi Note 4 (Latest Miui, Android N, Magisk, unlock) : Pass !!!

5. Mi 5 (miui 9, Android N, no magisk, Lock): Pass!!!
[Magisk] Didgeridoohan:
1, 3 and 5 is expected. Unlocked bootloader will cause a failed CTS, unless you have something like Magisk or a kernel that hides it.

2 and 4 is consistent with the current situation where some devices fail and some pass.

I haven't taken a tally, but it seems like older devices pass while newer devices fail...
[Magisk] Terrails:
Is it worth it to take a look at the props before and after the google update? After that just find something that doesn't match and try to set the prop.
[Magisk] Ridianod:
Hi. I have mi 9t global on miroom v11.0.4.0 stable and I cannot pass cts anymore. I update my rom today from v11.0.2.0 to v11.0.4.0.

View attachment 4966853

View attachment 4966855
[Magisk] ZellZoy:
I'm gonna throw in that mine started failing a few days ago without me changing anything except updating Mario Kart (it not working was how I noticed something was wrong and started investigating). I'm still on the 12/1/19 security patch
[Magisk] zencooler:
It's not a question of security patch. It's the result of Google Services updates and/or Google Play Store. You can go back to backup before these updates but it's really difficult to stop auto updates of GMS. The other thing is that if you avoid GMS updates some other apps will ask to do it one day...
[Magisk] Khep:
Thanks for the response. You likely already know this, but:

This was a special weekend for Pokemon Go, and just before it started (I think Thursday/Friday), not only a lot of people started to have the CTS Prop failure, but also the emulator VMOS, stopped working. So, there is a good chance that Google released an update recently, and the devs of PGo (whom may be in the Beta program of Android), worked in tandem with them.

Notice that I managed to actually play the game even with the CTS failure, but stopped to to avoid a Ban. But after using other images, the CTS fail then prevented me to start the game (like it should). Not sure why it failed even with 8.1 (Sys updates disabled), though. For reference the Xiaomi Mi A2 is part of Android ONE program, so it does not uses Miui.

EDIT: IF helpful, I can provide the STOCK props from 8.1. You just need to run the command: getprop
[Magisk] Terrails:
Is it possible to get the list of all the props without root (adb or something else)? If it is, it would be great if someone who has locked bootloader and successful safetynet to share their props. We could probably get something from that... right?
[Magisk] fgprodigal:
It's easy to get it from a stock rom
[Magisk] virags:
[MENTION=4667597]Didgeridoohan[/MENTION] - when i hit "which busybox" it says "/data/data/com/termux/files/usr/bin/busybox
[Magisk] LXT145:
My friend passed safetyNET through a locked bootloader and his device is Mi 9T Pro.

We all play a game called Dragalia lost, but since March 7th, ctsProflie: false, resulting in the game "support code 160". After my friend locked the bootloader, the game returned to normal.

My device is Xiaomi Mi 9(cepheus).
[Magisk] Khep:
LOCK status is the main element Google security checks, so it make sense it works. Point is, we need to have it unlocked, and still pass the CTS profile test. Specially when the other check already passes. Google definitively did something in the last 3-5 days.
[Magisk] Ridianod:
:good: I agree
[Magisk] Khep:
Interesting:

I installed the oldest STOCK 8.1 version of the Mi A2, with OEM unlocked and USB debugging (No Magisk, nor TWRP though).

The Play Store version is: 8.9.22-all[0] 296488958

Play Protection Status = Device not certified.

I registered the Framework ID in this page: //www.google.com/android/uncertified/

And I can enter into Ingress game, even though the status is still not certified.

I assume you would eventually get a ban, but that was curious.
[Magisk] virags:
I finally got this module and busbox to work, updated the latest S9+ fingerprint from the mod and still CTSPROFILE is false.. Still everything other than microsoft apps is working for me.. I dont get why outlook has a problem with safetynet failing if i can install apps from google store just fine.. beats me!