yashsingh1/xdaforums huggingface dataset:
[Magisk] awesomeo3000:
Ah, well now that you say that, it might make some sense! When rooting, I didn't want to fully install a recovery cause it's screwed me in the past, so I just used the TWRP image to get the phone to boot into recovery so I can install from the Magisk-vXX.zip, but without fully installing a recovery (I documented my rooting procedure here). This workaround got Magisk to install and give me root, and on Android 8 and 9 I was able to just

mount -o rw,remount /system

and then

echo "net.tethering.noprovisioning=true" >> /system/build.prop

. Whatever Google did with Android 10 prevents you mounting /system as rw, but following your workaround for using the propsconf directly does the trick! I'm not sure how I'd uninstall Magisk at this point. Do you think it's worth it to continue messing with it? Perhaps I'd have to do a factory reset and then do the whole rooting thing from scratch? And I don't know how I'd even install Magisk any other way besides how I did it the last time. I thought that was a full install of Magisk without the full install of TWRP. Finally got the logs zipped up and attached.
[Magisk] Didgeridoohan:
You've been given a very complete and comprehensive answer by [MENTION=7280276]ipdev[/MENTION] in the general support thread on how to install Magisk without TWRP:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post82087567

I just wanted to add that there should be no need to do a factory reset. The only thing you really need to be careful with is that if you've previously unencrypted your device it will be encrypted again if you uninstall Magisk and boot up without installing it again (this happens automatically when doing a full uninstall from the Manager). But, it might not be necessary to do a full reinstall of Magisk. See more below...

There's nothing to note in the logs unfortunately, everything appears normal. The only thing that's off is what we've already seen in the Busybox NDK installation log, and that turns out it might be caused by a bug in the Magisk cleanup code. You should be able to fix that easily yourself.

Go to /data/adb and delete the magisk.img file (that should be there according to the Busybox install log). After that you should be able to install the Busybox module and hopefully the module should start working as expected.
[Magisk] Didgeridoohan:
[MENTION=6733904]akerenyi[/MENTION] The above, about simply deleting the magisk.img file in /data/adb might fix your issue as well.
[Magisk] chooks06:
Thanks for the link!

[MENTION=7280276]ipdev[/MENTION] - thanks for the info!
[Magisk] SystemDoctor:
I've been trying to get this working for some time now but with no success. Attached is my log. If any more info is needed, I'd be happy to provide!
[Magisk] Didgeridoohan:
It's not an issue with this module, but rather that something is wrong with the Magisk boot process on your device. The late_start service mode triggers way to early so no scripts in the boot stage runs.

You could try disabling one module after another and see if it's one of your installed modules that is causing it.
[Magisk] SystemDoctor:
Thanks! Disabled a few and it works now! Turns out it was the CloudFlare DNS Module.
[Magisk] Didgeridoohan:
Great. The issue was triggered right after that modules post-fs-data script, so it makes sense.
[Magisk] John D J:
Hi since magisk updated I can't get my banking apps to open. I'm on lineage nightly os 25.03.20. Am I doing something wrong?
[Magisk] Some_Random_Username:
OnePlus 7 Pro NR GM1920 updated Android 10 fingerprint: OnePlus/OnePlus7ProNR_EEA/OnePlus7ProNR:10/QKQ1.190716.003/2003171325:user/release-keys__2020-03-01

OnePlus 7 GM1901 and 1905 updated Android 10 fingerprint: OnePlus/OnePlus7/OnePlus7:10/QKQ1.190716.003/2003131900:user/release-keys__2020-03-01
[Magisk] Didgeridoohan:
[MENTION=10666379]ThuchDara[/MENTION] That's an exceptionally large post to quote. Especially since you seem to have forgotten to post anything.

Would you mind editing your post and remove that quote? And possibly let us know what it was that you where intending to post.
[Magisk] John D J:
Hi I have galaxy s4 running optilos 16. For some strange reason all of a sudden my banking apps have awoken to the fact my phone is rooted even with magisk. They work when first installed, but after a reboot they will not open. Any suggestions please? Many thanks in advance
[Magisk] Didgeridoohan:
That's not really the topic for this thread. But, it sounds like you need to toggle MagiskHide off and on after a reboot. If this is the case you could do this with a script that runs:

magiskhide disable
magiskhide enable

More details in my guide:

https://didgeridoohan.com/magisk/MagiskHide#hn_MagiskHide_fails_after_rebooting

If it's another issue I suggest you look at this part of the guide and then post in the general support thread if you need further assistance:

https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] John D J:
Thank you, and sorry for putting it in the the wrong thread. But thank you. I really do appreciate it.
[Magisk] thenotonly:
Hi,

Please add the fingerprint for LG G7 ThinQ

judyln:/ $ getprop ro.build.fingerprint

lge/judyln_lao_com/judyln:9/PKQ1.181105.001/1917215300e03.FGN:user/release-keys

judyln:/ $ getprop ro.build.version.security_patch

2019-06-01

LG G7 ThinQ (9):LG:G7=lge/judyln_lao_com/judyln:9/PKQ1.181105.001/1917215300e03.FGN:user/release-keys__2019-06-01

Tested and working
[Magisk] Some_Random_Username:
OnePlus 7 GM1903 updated Android 10 fingerprint: OnePlus/OnePlus7_EEA/OnePlus7:10/QKQ1.190716.003/2003131900:user/release-keys__2020-03-01

OnePlus 7 Pro GM1911 and 1917 updated Android 10 fingerprint: OnePlus/OnePlus7Pro/OnePlus7Pro:10/QKQ1.190716.003/2003131900:user/release-keys__2020-03-01
[Magisk] oslo83:
Google raised its new security again.

Now both CTS and basicintegrity checks are failing :/

edit: Check post #3112 to know why :)
[Magisk] TraderJack:
Still passing on my Pixel 3 XL with March update. I did have the issue with failing last month when they switched it last time, but as of now I'm still passing with Magisk 20.3.
[Magisk] pndwal:
BasicIntegrity fail indicates problem unrelated to Google's key attestation detection, but ctsProfile will fail without basicIntegrity.

Are you using SafetyPatch module? This and a few other modules are now causing conflict with other new (basicIntegrity) SafetyNet checks due to bind mount mechanism used, etc.

Solution is to remove and find alternatives for these modules. Eg MagiskHide Props Config (this thread) still works fine.

Read from page 3916 here: https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/ PW
[Magisk] gius0161:
i've use "props" command in terminal, and i've use "LG G7 ThinQ (9):LG:G7=lge/judyln_lao_com/judyln:9/PKQ1.181105.001/1917215300e03.FGN:user/release-keys__2019-06-01"

but it's not working. I've ctsProfile:false. Can you help me?

Edit: I've re-flash stock and locked bootloader. If i write in terminal "getprop ro.build.fingerprint" i've got this:

lge/judyln_lao_com/judyln:9/PKQ1.181105.001/200350248e04d.FGN:user/release-keys

I need to use this last instead your?

So the complete string will be

LG G7 ThinQ (9):LG:G7=lge/judyln_lao_com/judyln:9/PKQ1.181105.001/200350248e04d.FGN:user/release-keys

(also tried with LG G7 ThinQ (9):LG:G7=lge/judyln_lao_com/judyln:9/PKQ1.181105.001/200350248e04d.FGN:user/release-keys__2020-01-01)

right?

edit: still not working... (i'm at stock 9.0 rom.. i never had this problem with stock rom (never use this module in stock rom with magisk).. i've tried lineange and when i come back to stock i've this problem
[Magisk] oslo83:
You're right, thanks.

My safetynet checks were now failing because a custom module I used, mostly cosmetic, about spoofing userlock states in /proc/cmdline. It did with post-fs-data.sh :

mount -o bind /data/local/tmp/cmdline /proc/cmdline

which is now detected somehow...

Thanks again for pinpointing that !
[Magisk] ipdev:
Please also run

getprop | grep manufacture

getprop | grep model

Manufacture should be LGE

Google lists four G7 ThinQ models on their certified list.

LG-G710 | LM-G710 | LM-G710N | LM-G710VM

LG G7 ThinQ (9):MANUFACTURE:MODEL=FingerPrint__SecurityDate

Not sure what the differences between models are (haven't searched that far yet) but, if you want to make it work with the simulation option, probably best to get the matching one.

Your last edit made me change my response again.

So I'll ask you also, what do you get when you run the following ?

(Doing this a little dirty should show all occurrences of these.)

getprop | grep fingerprint

getprop | grep security

getprop | grep manufacture

getprop | grep model

Cheers all. :cowboy:
[Magisk] Didgeridoohan:
[MENTION=4766699]gius0161[/MENTION] Apart from the info [MENTION=7280276]ipdev[/MENTION] is asking for above I'd like to add the following:

I've tested both of those ThinQ prints and they both pass the CTS check. Since you say that you can't pass CTS even on stock it's likely that you have something else going on. Can you pass basic integrity?

If both checks are failing it could be another module or other mod you have installed:

https://didgeridoohan.com/magisk/MagiskHide#hn_Check_your_modules_and_mods

If you do pass basic integrity we're going to need more info. If so, could you start with providing the module logs please:

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs
[Magisk] thenotonly:
I guess proper string would be

LG G7 ThinQ (9):LGE:LM-G710EMW=lge/judyln_lao_com/judyln:9/PKQ1.181105.001/1917215300e03.FGN:user/release-keys__2019-06-01

Manufacturer: LGE

Model: LM-G710EMW

Fingerprint: lge/judyln_lao_com/judyln:9/PKQ1.181105.001/1917215300e03.FGN:user/release-keys

Security Date: 2019-06-01

---------- Post added at 12:15 PM ---------- Previous post was at 12:13 PM ----------

put the string i provided in a file called printslist in /sdcard

then run

props, 1, f, 3 ,1

then apply and reboot

also check if your SN is still present in stock, if not, you will need to recover your sn to get things working
[Magisk] Didgeridoohan:
Fingerprints list updated to v83

Quick prints list update with the recently submitted fingerprints. Thank you [MENTION=5680977]thenotonly[/MENTION], [MENTION=4766699]gius0161[/MENTION] and [MENTION=8234677]Some_Random_Username[/MENTION] for your contributions.

As a side note I noticed that I had forgotten to update the version number in the prints.sh file last update, so it wasn't technically possible to update to v82. :D Everything's good with v83... :good:

As usual the list will update when you run the props command, or (if you've disabled automatic updates) by using the -f option or directly from the "Edit device fingerpint" menu.

New

LG G7 ThinQ

Updated

OnePlus 7 (GM1901, GM1903 and GM1905)

OnePlus 7 Pro (GM1911, GM1917 and GM1920)
[Magisk] gius0161:
finally i understand why this ctsprofile:fail happening.. it does not depend on the ROM change as I previously wrote but it depend from google updates (i've this same problem now with my LG G4 H815)

I've tried also the new v83, but still not working for me. I think because i've got G710EM (European model of LG G7 Thinq)

Some other information: I'm running stock firmware 20i Italian ITC (no brand) with security patch 2020-01-01

Now i've also unlocked bootloader with magisk.

I've resetted all option of the module so now "device simulation" is disabled.

$ getprop | grep fingerprint
[init.svc.vendor.lge-biometrics-fingerprint-hal-2-1]: [running]
[ro.boot.vendor.lge.fingerprint_sensor]: [1]
[ro.bootimage.build.fingerprint]: [lge/judyln_lao_com/judyln:9/PKQ1.181105.001/200350248e04d.FGN:user/release-keys]
[ro.build.fingerprint]: [lge/judyln_lao_com/judyln:9/PKQ1.181105.001/200350248e04d.FGN:user/release-keys]
[ro.product.build.fingerprint]: [lge/judyln_lao_com/judyln:9/PKQ1.181105.001/200350248e04d.FGN:user/release-keys]
[ro.product.lge.biometric.fingerprint.antispoofing]: [false]
[ro.vendor.build.fingerprint]: [lge/judyln_lao_com/judyln:9/PKQ1.181105.001/200350248e04d.FGN:user/release-keys]
$ getprop | grep security
[persist.product.lge.wlan.sys.security]: [2]
[ro.build.version.security_patch]: [2020-01-01]
[ro.vendor.build.security_patch]: [2018-06-05]
[security.perf_harden]: [1]
$ getprop | grep manufacture
[ro.product.lge.display_manufacture_sn]: [1]
[ro.product.manufacturer]: [LGE]
[ro.product.vendor.manufacturer]: [LGE]
$ getprop | grep model
[ro.boot.vendor.lge.model.name]: [LM-G710EM]
[ro.model.name]: [LM-G710EM]
[ro.product.model]: [LM-G710]
[ro.product.vendor.model]: [LM-G710]
$

I've make propslogs.tar file (i've resetted all module configs before do it)

On magisk i've passed basicIntegrity, i fail ctsProfile
[Magisk] Didgeridoohan:
It is of course possible that Google just flipped the switch again and all modern devices with an unlocked bootloader can't pass CTS. But, I think we'd see more reports of that if this was the case so I don't think that's your issue. Especially since you say you have the same issue on your G4. That device is old enough to likely not be affected by the change to SafetyNet's CTS profile check (only devices that shipped with Android 8+ are required to have the hardware for the key attestation).

I'm not seeing anything apparent in your logs, so I unfortunately can't help you.

As a side note, it does not matter if you use a fingerprint not meant for your exact device. As long as the print is certified it will help you pass CTS (if all other basic requirements are also fulfilled).
[Magisk] gius0161:
[MENTION=4667597]Didgeridoohan[/MENTION] with LG G4 I checked before I started updating the play store and i've pass safetynet. After play store update, I fail it.

So I don't know why it doesn't work on my LG G7:

the things to do are:

command props in terminal

type:

1 (for edit device fingerprint)

f (for pick a certified fingerprint)

9 (LG)

7 (LG G7)

reboot

is there anything else to do?

also if i use a different model or a different phone, I don't solve the problem

thanks for your help
[Magisk] Didgeridoohan:
Like I said, it's perfectly possible that Google did their thing again, but then I would have expected it to be a Play services update rather then the Store.

That should be everything that's needed.

But, as stated, for now there's not much more I can help with I believe. Either Google has flipped the switch and you're the first to notice or you've got something else about your setup that's causing it.
[Magisk] sliding_billy:
5 devices (including Pixel 3 and Pixel 3 XL) rooted with unlocked BL still passing all Magisk CTS checks as of 3 hours ago. I don't think Google did anything.
[Magisk] gius0161:
i don't know... i've got 2 LG G4 and with play store update 19.4.14 i've got the same problem

with 19.3 before the update, it works well.

Can you try to see what play store version have you on your phones?
[Magisk] Didgeridoohan:
See the attached screenshot (that's from this app).

But just because things work on one device it doesn't mean it'll work on another. There are many variables...
[Magisk] njtony:
Today ctsprofile and basicintegrity are both false, ctsprofile is false in early March, and false in early April. Google estimates that some adjustments have been made at the beginning of each month, which is too evil
[Magisk] Didgeridoohan:
If both checks are failing it's possibly caused by some mod you have installed:

https://didgeridoohan.com/magisk/MagiskHide#hn_Check_your_modules_and_mods
[Magisk] njtony:
It is indeed a problem caused by the module. I have n’t updated any modules in the past half month. Yesterday everything was normal. Today is false. I thought it was tested by Google again. I was testing each module.

---------- Post added at 03:42 PM ---------- Previous post was at 03:31 PM ----------

Riru core v19.7 causes false. . .

Disabled Riru core will not work with Edxposed

This is a dilemma, only to wait for riru to update
[Magisk] sliding_billy:
I just checked the 3 XL (that is the only one with me), and it has 19.4.14 and definitely has not got an update since the checks I made.

The modules on each device vary, but this on has everything on the others. On this one, I have Audio Modification Library, Busybox for Android NDK, MagiskHide Props Config, Systemless Hosts and ViPER4Android FX. No Google Pay modules (I use the manual SQL attestation edit method) and of course no Exposed.Magisk is latest stable (20.4) and Magisk Manager is the same (7.5.1). Hidden are Google Pay, Google Play Services, Google Play Store, Google Services Framework (all sub-processes hidden on all). I just checked CTS again, and both are OK.
[Magisk] nri_tech1183:
Freshly installed custom rom 2 days ago and everything passing in magisk and all apps reporting normal functionality.
[Magisk] Some_Random_Username:
OnePlus 7T HD1901 and 1905 updated Android 10 fingerprint: OnePlus/OnePlus7T/OnePlus7T:10/QKQ1.190716.003/2003271900:user/release-keys__2020-03-01

OnePlus 7T Pro HD1911 and HD1917 updated Android 10 fingerprint: OnePlus/OnePlus7TPro/OnePlus7TPro:10/QKQ1.190716.003/2003271900:user/release-keys__2020-03-01
[Magisk] GtrCraft:
Can you please add POCO X2 (phoenixin) to the list?

fingerprint: POCO/phoenixin/phoenixin:10/QKQ1.190825.002/V11.0.6.0.QGHINXM:user/release-keys

security patch: 2020-03-01
[Magisk] pndwal:
Please let me know the name of the problem module (for my list of Magisk Modules recently causing SafetyNet check basicIntegrity fail - https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post82166469 ). Thanks, PW

Edit: I understand this is a private / unreleased module. Thanks.
[Magisk] nri_tech1183:
Can we have a list of all problematic modules so we can avoid them for the time being...
[Magisk] wingbat:
Moto g7, US, Google Fi variant, XT1962-1, Android 9.0, changed/updated for Feb patch:

motorola/river/river:9/PPOS29.114-134-10/ca814:user/release-keys__2020-02-01
[Magisk] Didgeridoohan:
Keeping a list of

all

modules that now trigger SN would be a momentous task... [MENTION=7550078]pndwal[/MENTION] have started to put together one in the Magisk general support thread though.
[Magisk] Didgeridoohan:
PSA

This thread has a tendency of attracting SafetyNet discussions, which is natural considering what the module does.

But now that we've identified that Google have toughened up SafetyNet somewhat, and that some modules and modifications now trigger both CTS and basic integrity, let's try to keep discussions on that particular topic in those modules' threads or in the general support thread.

Cheers! :good:
[Magisk] Itachizero:
Max pro 2

Please next update for Max pro M2, I'm waiting for this :crying:
[Magisk] Didgeridoohan:
I would love to:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] rickmec:
I need it too please!

Help!

Can't update my phone...
[Magisk] Didgeridoohan:
Did you see my reply to that post? It still applies:
[Magisk] rickmec:
I just saw that note 8 fingerprint doesn't pass cts... But I need a way to revert to mi original fingerprint and can't find the option...

I think I'll flash the original rom again

Thanks!
[Magisk] Didgeridoohan:
If you've used the module to set a fingerprint you can just pick the "Reset fingerprint" option under the "Edit device fingerprint" menu.
[Magisk] xiangnan:
I have extracted the fingerprint code from the xiaomi6 ROM package that can pass cts authentication as follows:

$ getprop ro.product.manufacturer

Xiaomi

$ getprop ro.product.model

MI 6

$ getprop ro.build.fingerprint

Xiaomi/sagit/sagit:9/PKQ1.190118.001/V11.0.6.0.PCAMIXM:user/release-keys

Security program patch is 2019-09-01

What other information do you need？

At the same time, there are several issues that need to be explained. This rom package that can pass cts authentication needs to lock back the BL lock. And this is the miui international package and not the Chinese version of miui (and I need to use a lot of localization features of the domestic version of miui, I do n’t know if it can be applied to the domestic version of miui after the module is updated). The most important thing is that Google has updated the safetynet detection Way (seems to have to lock the BL lock to pass).

Thank you for developing this module！

It has been confirmed that unlocking the BL lock brush into the mask and pulling the black paly store can pass the CTS certification.
[Magisk] Didgeridoohan:
That is all. Thank you.

There are many things I don't understand about MIUI...

Google did update SafetyNet recently to use hardware key attestation, making it virtually impossible for Magisk to hide the bootloader state. It doesn't like they currently have it active, but that's just a matter of time. If it is possible to (relatively) safely look the bootloader on your device that is one solution. But locking the bootloader with a modified device is always risky.

There was also another update recently where SafetyNet now triggers with both checks when certain modifications are made.

A few more words about the above can be found here:

https://didgeridoohan.com/magisk/MagiskHide#hn_Unlocked_bootloader_3

https://didgeridoohan.com/magisk/MagiskHide#hn_Check_your_modules_and_mods
[Magisk] blackxxx15:
anyone fingerprint for:

Samsung Galaxy S10 ?

maybe with 1.04. Security Patch?

:D
[Magisk] sobhan06:
cts profile false issue

CTS profile false. Trying to figure this out but whatever I do it is showing false only. on Lineage OS 17.1, Magisk 20.4, tried busybox module, hide props module. through terminal emulator used original fingerprint of Oneplus 3T. Not sure what are the other options to rectify CTS profile. Safetynet is True.
[Magisk] pndwal:
In 20.4 MagiskHide is off by default. Have you enabled it? PW
[Magisk] sobhan06:
Yeah, I got the solution. Thanks, its working.
[Magisk] heineken78:
Real safetynet checks.

For CTS check responsible only two props.

For another check responsible real selinux state and green state prop, possible another one from cmdline. Both are replaced in kernel anyway.

All other is bull****.

Thanks, hope google will not fix it after my post.

cheerz.
[Magisk] Didgeridoohan:
¿Que?

Google is very well aware of the shenanigans we are up to. They're not stupid.
[Magisk] th3legend:
Hey so I am on Samsung a20 and I had the fingerprint working and all that good...then I upgraded to the new version and it gets stuck at Boot...I'm also on lineage 16.1...I tried things:

Default with the fingerprint__security patchdate...

Just fingerprint

Set into post fs or w.e

Tried setting fingerprint and set the sec patch in set custom prop.

..

Same results for all stuck at boot loop...and I notice that when I do enter the fingerprint...it states something like ..../data/media/0/prints list no such file PR directory...not sure if that is an important error

Attached the mhpc log files in case that helps
[Magisk] Didgeridoohan:
If the issue of that you're getting stuck at boot I would need the Magisk log(s) also. And preferable a boot logcat.
[Magisk] Itachizero:
It was very difficult for me, I was a beginner in this section, and now I am using a LOS nightly official costume ROM no longer stock ROM, I hope there are members here who want to help this for Max pro M2
[Magisk] th3legend:
I am trying to find these logs - places say to look for /data/cache/ i copied everything over from the cache folder and then some additional logs i could get from twrp but i am going to try and get the logcat - just working on doing that right now thanks for the help!

edit: found the magisk logs attached!