yashsingh1/xdaforums huggingface dataset:
[Magisk] Cryceratops:
Thanks for your help. Much appreciated.
[Magisk] Dante Enoshima:
Samsung Galaxy J7 Prime

samsung/on7xeltedd/on7xelte:7.0/NRD90M/G610FDXS1BRF5:user/release-keys
[Magisk] deepu458:
Hi [MENTION=4667597]Didgeridoohan[/MENTION],

Thanks for making this module, it helps a lot of people like us. I would like to add a new Fingerprint to the list as our device is not listed currently.

Device: Samsung Galaxy Note 10.1 2014 edition(SM-P600)

Official Fingerprint: samsung/lt03wifixx/lt03wifi:5.1.1/LMY47X/P600XXUDOJ3:user/release-keys

Current Fingerprint for RR-Rom (7.1.2) by 5.8.5

I have modified the service.d file on my device with this fingerprint and it made the ROM to pass safetynet check CTSProfile without any issue. So i would like to add it to the list, so many others in our rom thread can flash this mod and get it certified.
[Magisk] Didgeridoohan:
[MENTION=6409421]deepu458[/MENTION] Thank you, I will. I have just arrived back home after a couple of weeks abroad, and I'm planning on updating the fingerprints list after I'm a little less jetlagged...
[Magisk] deepu458:
Great Thanks. take ur time. No rush. hope u had a great fun.
[Magisk] Didgeridoohan:
Fingerprints list updated to v20

Didn't have anything better to do, so I decided to spend my time by updating and adding some fingerprints to the list.

New prints:

Motorola Moto G5S (7.1.1)

OnePlus 2 (6.0.1)

OnePlus X (6.0.1)

OnePlus 3 (8.0.0)

OnePlus 5 (8.1.0)

Samsung Galaxy J3 (5.1.1)

Samsung Galaxy Note 10.1 2014 (5.1.1)

Updated prints:

OnePlus 3T (8.0.0)

OnePlus 5T (8.1.0)

The fingerprints list will be updated when you run the props script, by selecting the update option in the Fingerprints menu, or running the props script with the -f option.

Thanks go out to [MENTION=4734391]Adamask[/MENTION], [MENTION=9245737]FPRSergio[/MENTION] and [MENTION=6409421]deepu458[/MENTION] for providing to the list.
[Magisk] VincentJoshuaET:
Only ctsProfile fails for me. I changed the fingerprint using your module but ctsProfile still fails. Any other ideas? Thanks.
[Magisk] Felix Siahaan:
Hi, I'm using same phone and MIUI version and also I passed ctsProfile & basicintegrity.

May I know what is your current fingerprint value?

Did you change it manually or using current fingerprint list?
[Magisk] Didgeridoohan:
Hello there! I've taken a look and compared props from the Global and China ROM's. There are a few props that may be the deciding factor, and I'd like you to try them out.

Place the attached file in your /cache folder, remove the .txt extension (it's just there so I could attach the file), and reboot your device. It'll set the fingerprint to a certified one and a few custom props that might be used to identify the ROM as the China ROM (note that it'll reset any other custom props or settings you might have set). If that works you can then disable those props one by one, reboot in between and see if you still pass SN, to see which one is the deciding prop so that I can update the module accordingly. If it doesn't work, I have a couple of more props that could be tested, but these are the most likely suspects.
[Magisk] Didgeridoohan:
Are you by any chance using the China ROM? I've been trying to figure why the Global ROM passes the ctsProfile check while the China ROM doesn't, together with [MENTION=5984070]kullurumanoj[/MENTION]. I just posted a module configuration file above that you could also try, and maybe help figure this out.
[Magisk] Didgeridoohan:
In the root of your internal storage (/sdcard). The file is named propslogs.tar.gz.
[Magisk] Bskendkk:
It wasnt creating the file :/ I gave up on this hopeless beta rom and went back to stock rom and guess what...

Can't even pass cts on stock ROM now, unrooted :|

Fk this man, im going to flash miuipro, that thing actually works rather than this flimsy MIUI garbage..

Anyway, thanks for your responses and your module. I'm sure it is helpful for most people :)
[Magisk] Bskendkk:
Hello again! i have reverted back to MIUI (miuipro is cool but i ultimately decided against it).

I am attaching the logs for my issue here (finally managed to find the file this time around xD , so noob)

If it is of any help, im on a Chinese device with a Chinese beta ROM for note 8 pro (20.2.27).

In terminal(termux) upon going into props menu, it says my new fingerprint has been applied (tried a few different phone models), but if i use a test service online, it still shows up as Note 8 Pro.

Been trying to fix this for 4 days and am exhausted. P.S. I have to use the beta build on this specific Chinese model to gain root, due to stable builds being a pain/risk to root for this particular version of the device.

Not sure if any of this helps, I'm really just a befuddled noob and am trying to provide as much as i know xD

Thanks again for your work :)
[Magisk] Sid220:
[MENTION=4667597]Didgeridoohan[/MENTION]

New fingerprint for Xiaomi PocoPhone F1

Android version 10

Security Patches 2020-02-01

Xiaomi/beryllium/beryllium:10/QKQ1.190828.002/V11.0.6.0.QEJMIXM:user/release-keys
[Magisk] jfarreola:
Today I woke up to my banking app detecting root and not working anymore :rolleyes:

Tried hiding the app in Magisk, and blacklisting the app in EdXposed... no go.

Tried this module, got a warning message refering to the props not loading properly.

The banking app is Banorte (Mexico-based). I'm flashing stock rom until a solution arises :( I'm attaching the log.

Another thing, my device is a bv9800pro and would like to contribute with fingerprint... how can I get this info and share here?
[Magisk] Some_Random_Username:
https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint
[Magisk] Didgeridoohan:
Logs look fine, but I'll take a closer look later, right now I have other commitments...

But, for now, you could try resetting the fingerprint props boot stage back to the defaults.

You won't see a device change by just changing the fingerprint, there are many other props that identify your device. If you want to make your device seem like another one you can try the device simulation feature. But that is not necessary for passing SafetyNet.
[Magisk] Didgeridoohan:
It is unlikely that this module can do anything about the app, unless it uses SafetyNet and you in turn can't pass that.

The reason the props script doesn't run is because the late_start service boot stage doesn't run, which in turn often is caused by EdXposed's live changing if sepolicy patches at boot. Or at least previous versions of EdXposed. Have you updated to the latest version (0.4.6.1 I believe)? That version is now using Magisk's new way to do sepolicy patches that shouldn't cause this issue anymore (in theory, I haven't seen any confirming reports yet).
[Magisk] jfarreola:
I tried with 0.4.6.1 and canary 0.4.6.2, none worked. I flashed stock again a few hours ago. Will try with Magisk only & fresh flashed rom and see if that does the trick. If not, guess I will just have to be patient :fingers-crossed:

Thanks!
[Magisk] ipdev:
It's that time, new monthly updates.

Poco F1, OnePlus have been given already.

So, March Pixel(s) 2, 3, 3a, 4.

Essential is officially done. (Supposed R beta might exist?)

Still have to look into the vendor image they released, it is marked as non-certified.

Google's Factory Images are a little odd this month but, all we want are certified prints and props.

Pixel 3 (blueline) and Pixel 3 XL (crosshatch)

10.0.0 (QQ2A.200305.002, Mar 2020, All carriers except T-Mobile, Google Fi)

Pixel 3a (sargo) and Pixel 3a XL (bonito)

10.0.0 (QQ2A.200305.002, Mar 2020, All carriers except Bouygues Telecom)

Pixel 4 (flame) and Pixel 4 XL (coral)

10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)

Cheers all. :cowboy:
[Magisk] wilsonhlacerda:
Your device may be "randomly" loosing root / Magisk Hide. This is observed since a long time by some people without a fix.

In fact seems that Magisk daemon gets killed by something (or itself) on some devices on certain circumstances, for instance due to extremely power optimization (be sure you set Magisk Manager as exception on your device settings) or memory filling after using some apps.

I myself was suffering with that.

THE WORKAROUND I found that FIX THE BUG: just after boot go to Magisk Manager settings and toggle Magisk Hide OFF/ON (you can automate that with a simple service.d script). This way Magisk will never get killed anymore, will never loose root / hide.

Latter I'll better write about that on the main Magisk thread. I could find a way to always reproduce the bug and thus found this workaround fix, at least for my Samsung S4, LOS16, Magisk 20.3, EdXposed 4.6.1 Sandhook. All working perfect with the new EdXposed / Magisk / workaround.

---------- Post added at 08:45 AM ---------- Previous post was at 08:37 AM ----------

See my comment above. May I suggest you to include in your good Magisk docs the workaround? You mention there the random loosing root bug....maybe add the workaround I found just by that.

In fact toggling Magisk Hide just after boot fix randomly loosing root + Magisk not/stop being detected by Magisk Manager + hide randomly stop working. At least on tests on my device.

Concerning boot scripts with new stable EdXposed, now working perfect (with Magisk 20.2+). Previously it was really a problem.
[Magisk] Bskendkk:
Thanks, perfectly understandable about life commitments! I will wait for your further replies :)

T
[Magisk] Didgeridoohan:
Update to v5.2.4-v80

After having released the latest string of updates I had some time to go over the module and found a few things not quite working as intended. Hopefully got everything fixed with this release. Also added in a function to disable the module by placing a file on your device (see the docs).

The fingerprints list has of course also been updated with the latest contributions. As always, thanks go out to those who help and this time around those are [MENTION=5264812]loco1911[/MENTION], [MENTION=4453960]swour[/MENTION], [MENTION=8234677]Some_Random_Username[/MENTION], [MENTION=4770208]Sid220[/MENTION] and [MENTION=7280276]ipdev[/MENTION].

Changelog

v5.2.4

Added a function for disabling the module by placing a specific file in /sdcard, /data or /cache (see the documentation for details). Useful if there are issues with booting the device after installing/setting up the module.

Fixed some issues with setting partition props in other boot stages than default.

Fixed an issue with boot scripts clashing if post-fs-data.sh script takes too long.

Fixed an issue with settings transfer overwriting the file backup at install.

Fixed an issue with log writing that came with the change to using getprop for retreiving prop values.

Added fingerprints for Xiaomi Redmi 7. Updated fingerprints for Google Pixel 2-4 (all variants), OnePlus 7 Pro NR, Samsung Galaxy A5 2017 and Xiaomi Pocophone F1. Fingerprints list updated to v80.
[Magisk] Didgeridoohan:
I don't really see anything in your logs that would explain why you're not passing CTS. I'm not sure if I've asked before, but you do pass basic integrity, right?

You could of course try the new release, but I don't think it'll do anything differently for you.
[Magisk] Scunkanełi:
Hello!

I am really sorry to bother you with my issue, but since yesterday I can't pass ctsprofile reliably anymore...

I was using the preconfigured fingerprint in PropsConfig for Xiaomi Mi 9 since months now without any issue. Yesterday, ctsprofile started to alternate between true and false. For example, it first reports false, then 2 seconds later true, then a little bit later false again, without me changing anything on the device.

Now today, ctsprofile reliably shows false. I have run the test almost 20 times now and it always shows false.

I thought maybe the preconfigured Mi 9 fingerprint got revoked, but there is only one option for Mi 9 in PropsConfig, I can't choose another one. Is it safe to use a fingerprint for a different model to test if it works then? (e.g. I choose Mi 9T fingerprint for my Mi 9)

A safetynet checker app reports "Advice: LOCK_BOOTLOADER". My bootloader is indeed unlocked, because I am using a custom-rom (xiaomi.eu, Android 9). basicIntegrity has stayed true the whole time. EdXposed is installed, but module is disabled in Magisk

I uploaded my log here: https://we.tl/t-jnR19hmGhn
[Magisk] amitaffright:
Just updated rom MI A3 to V10.3.13.0.PFQMIXM and CTS Fails even after doing everything it was working fine with old firmware Not working with firmware V10.3.13.0.PFQMIXM. Please fix this thank you.
[Magisk] Didgeridoohan:
The Mi 9 print passes CTS with flying colours... I tested right now to make sure.

I'm not sure what could be the issue on your device, but if that other SafetyNet checker reports that the unlocked bootloader is detected it might mean that Magisk isn't quite masking that on your device. Why? No idea...

I'll take a closer look at your logs later.
[Magisk] Didgeridoohan:
Not sure what you expect me to fix... Do you mean that you're using this module to pass CTS and that it doesn't work after that update?

Does basic integrity pass? Have you tried toggling MagiskHide off and on again? Etc...

Some troubleshooting tips:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] njtony:
After updating v5.2.4-v80, after updating the fingerprint, the ctsprofile is false. After refreshing v5.2.3, re-updating the fingerprint, the ctsprofile is still false. My phone is pixel 3a xl. How do I export the log? My English is not good, thank you！

Before updating to v5.2.4-v80 was true before yesterday，I suspect google changed the rules

[IMG="https://s2.ax1x.com/2020/03/06/3OFs6P.jpg"]https://s2.ax1x.com/2020/03/06/3OFs6P.jpg[/IMG]
[Magisk] Didgeridoohan:
Strange that all of a sudden all these reports of CTS failure start dropping in...

If you go back one step from the menu in your screenshot there's an option to collect logs (#7).
[Magisk] suvomania:
On stock rom miui 11 redmi k20pro. What ever i do, unable to fix ctsProfile : false. Please help. Only magisk installed. Nothing else. Please help.
[Magisk] njtony:
Logs uploaded,Thank you!

View attachment 4965581
[Magisk] sliding_billy:
There is definitely something going on with CTS profile failure. Pixel 3 XL running DU, Pixel 3 running stock rooted on March, 2 Huawei Mate SU stock rooted running Oreo all failing. Only device passing is Tab S2 T713 (WiFi only) running LineageOS 16 updated from nightly 3/5. All are on Magisk stable with no fingerprint changes and they were all passing Wed night/Turs morning. All are passing play certification at least.
[Magisk] Sid220:
[MENTION=4667597]Didgeridoohan[/MENTION] i have to report that also PocoPhone F1 from yesterday evening started failing CTS, me and all F1 users are speechless. I think it's not a module thing but a Google thing, what do you think?

I'll upload logs ASAP
[Magisk] Didgeridoohan:
If you're not passing CTS it's just a matter of time before the Play store gets uncertified.

It undoubtedly seems to be something going on. For now the only hint we have is the LOCK_BOOTLOADER advice posted about above. Could be that there's some additional prop check for an unlocked bootloader that's been added to the CTS profile test. No idea what that could be though, and it's just a guess.
[Magisk] Sid220:
AFAWK Probably Google added a check for unlocked bootloader on CTS, hope it's a matter of time to bypass that
[Magisk] Didgeridoohan:
The CTS check has always tested for an unlocked bootloader, but Magisk circumvents that by changing the relevant props.
[Magisk] hyborian:
Argh, indeed. it was ok 2 hours ago, now CTS profile is failing, on 2 Pocophones, 1 Note 7.
[Magisk] sliding_billy:
Agreed about it eventually failing Play Store certification unless it is actually a CTS glitch or something (I can dream). The unlocked BL makes some sense since the T713 doesn't actually need a BL unlock command.
[Magisk] hyborian:
Do you think it is related to this ?

https://xdaforums.com/showpost.php?p=81919307&postcount=38567
[Magisk] zipsu:
On Mi9 xiaomi.eu rom, everything was fine for months as well, but suddenly today CTS no longer passes, tried everything, different fingerprints, settings, other safetynet modules, nothing worked. (feb 2 2020 security patch)
[Magisk] Didgeridoohan:
Those of you who are failing CTS, what security patch date do you have? Just wondering if it could be something about the s March update...
[Magisk] sliding_billy:
March for the P3, February for the P3XL, November 2018 for the Mates.

---------- Post added at 11:56 AM ---------- Previous post was at 11:54 AM ----------

I'd say no since only one of the failing devices would have been impacted. Others are not updated for various reasons..
[Magisk] Scunkanełi:
The patch level of my ROM is 2019-07-01 and it shows this patch level in settings on the device
[Magisk] Sid220:
February 2020 patches here
[Magisk] njtony:
pixel 3a xl

View attachment 4965657
[Magisk] rafaeldamasceno:
Hey there, POCO F1 user here. Feb 5, 2020 Android security patch and Jan 1, 2020 vendor security patch. I'm also attaching logs. I know this won't make a difference in the current issues, but the latest fingerprint for Android 10 is for a version which isn't yet fully rolled out to the public. The previous version is still the stable release and the only one people can actually download. Do you have any criteria in when you update these? I imagine it doesn't really make a difference, however.
[Magisk] Didgeridoohan:
The criteria I have is that the fingerprint needs to pass CTS on my devices. And it did.
[Magisk] rafaeldamasceno:
I expected that to be the case ? Well, looking forward to see this issue solved, eventually. Thanks for all your great work.
[Magisk] ipdev:
Not sure if it helps but, my bonito fails today also.

Running a signed abc rom that passes SafteyNet on its own.

Well, at least it did last night.

I'm at work so I can not check too much right now.

Magisk debug, core (safe) mode used to pass on this device.

Now, it fails.

Same note about the bootloader so maybe a new way of checking bootloader status?

Edit:

Also, the Poco F1 print worked two days ago when I tried it.
[Magisk] hyborian:
I don't think it is this module's issue, but any help from didgeridoohan is welcome. I have 2 Pocos running MIU Android 10, both passed CTS without having to use MagiskHide. Only today that both didn't pass.

So for one Poco, I chose Android 10 fingerprint in MagiskHide and it passed. I checked the other one, and it is passing again, so I didn't have to use MagiskHide on it.

Now, a few hours later, CTS doesn't pass for both Pocos. My Note 7 is still Pie, and it doesn't pass as well. Must be something with Safetynet app.
[Magisk] Didgeridoohan:
Unfortunately, right now there's not much I can do. I'm not seeing this issue on my devices and that always makes it difficult to troubleshoot. Best guess I can come up with is that there is a new bootloader check, but that is pure guesswork and may be 100% incorrect.

I could take the logs that have been posted today and manually go in and analyse the device props that are saved when the module exports logs. If there is a bootloader kind of prop in there that MagiskHide isn't taking care of, that might be it. Might, I say. It'll take a bit of work to confirm or deny...

Currently I don't have that kind of time until sometime next week (maybe), so anyone's welcome to get their hands dirty and dig in.
[Magisk] jiraianam:
https://www.androidcentral.com/google-pulls-march-update-att-pixel-4-after-google-pay-breaks
[Magisk] Didgeridoohan:
Yes, that update was pulled a few days ago, but that doesn't quite explain why other devices that hasn't had an update suddenly start failing.

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post81919307
[Magisk] EVR_PR:
New update for AT&T build is still broken and with your update to the Magisk Module, the fingerprint used doesn't allow SafetyNet to pass.

Is there a way to use the previous fingerprint on this new module update or do I have to go back to v5.2.3 to use the fingerprint for the February build?
[Magisk] ipdev:
It doesn't seem to matter.

CTS is broken on some devices period.

My Nexus 7 and 9 (Both WiFi) still pass using the current Magisk debug and current or old prints.

Edit: March Pixel (s) and others pass SafetyNet both devices.

As noted earlier, this is a kind of a WTF? at the moment. :confused:
[Magisk] Lfly:
my Xiaomi Mi 10’s fingerprint

ro.build.fingerprint=Xiaomi/umi/umi:10/QKQ1.191117.002/V11.0.10.0.QJBCNXM:user/release-keys
ro.build.version.security_patch=2020-02-01
[Magisk] ipdev:
This is OT but, the only thing I can add at the moment.

Using RootChecker to test SafetyNet started to fail periodically on my older devices.

Safety Net Request fail(Can't access Google Play Services)

Magisk's SafetyNet check would show pass.

Now I get the same error with RootChecker on all devices. If I unhide com.google.androidgms.unstable then RootCheck can connect to check SafetyNet on newer devices (Still failed CTS currently) but, the older devices still give the same connection error.

I was also wondering if there was a change in SafetyNet like the last time.

Year ago (maybe two?) there was a change to SafetyNet checks and until the apps checking were updated, it would show fail when the device actually was passing. ?
[Magisk] BreadOnToast:
This might just be me not reading deep enough into the documentation, or being ignorant, but how are you meant to back up your current device fingerprint before replacing it?
[Magisk] Didgeridoohan:
You don't.

That's the nature of Magisk and it's systemless modifications: the original fingerprint isn't touched and the new one is merely loaded into memory in its place.
[Magisk] Didgeridoohan:
For me, Magisk Manager can check and show that I pass SafetyNet just fine. But, other checker apps fail to contact the Google servers.

This might simply be caused by the restrictions put in place by Google when they made the changes you're talking about. They limited the number of SafetyNet checks an app can make (s higher limit can be given by Google) so if there's suddenly a huge number of people that are checking SafetyNet (because it this CTS issue) it might mean that they're reaching their cap. I'm regard to the Manager still being able to check I'll just quote [MENTION=4470081]topjohnwu[/MENTION]: "we are root, we are not limited".

As always, just guessing and I might be completely wrong...
[Magisk] hyborian:
If I go to Play Store, under settings, it says my device is Certified (even if CTS in SafetyNet failed). I guess it's fine then.

* Edit : Spoke too soon, now it says Not Certified, argh
[Magisk] Didgeridoohan:
Some apps will disappear from the Play store once the Play Protect certification is updated and apps that do use SafetyNet might not work.
[Magisk] hyborian:
Thanks for the info. I just did Step No. 2 in this guide with success, hope it will help whitelist my device for now :

https://www.saintlad.com/fix-device-not-certified-by-google-error/
[Magisk] bagdas:
Xiaomi/perseus/perseus:10/QKQ1.190828.002/V11.0.3.0.QEEMIXM:user/release-keys

Xiaomi Mix 3 MIUI 11 / Android 10.

Now in list exist this device only on Android 9
[Magisk] EVR_PR:
My March Pixel does not pass SafetyNet with either of March build's fingerprints. Using February's will fix the issue. This new March build doesn't seem to have fixed this issue at all.

Edit: It doesn't matter which fingerprint I use now, CTS is completely broken. What a shame.
[Magisk] sliding_billy:
Answered the question of Play Store passing certification. Just lasted until a new install. I recompiled DU and dirty flashed. Normally Play Store certification holds through a dirty install and doesn't even need cache and data cleared. This time it came back not certified and clearing cache and data made no difference. Looks like whatever the kernel was obscuring isn't still hidden.
[Magisk] Didgeridoohan:
Yes, that's what we've been discussing in this thread the past day. It's got nothing to do with the fingerprints, but something might have changed on the Google/server side.

For future reference, I never put a fingerprint in the list unless I've tested it myself that it does pass CTS.