yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
You mean like this?

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint
[Magisk] phenixiou:
Galaxy S10 (SM-G973F): samsung/beyond1teeea/beyond1:10/QP1A.190711.020/G973FXXI8CTG4:user/release-keys
[Magisk] Didgeridoohan:
Thank you. What is the security patch date for the build where that print is from?
[Magisk] phenixiou:
The security patch date is 1 august 2020

Print is from my clean android
[Magisk] Didgeridoohan:
Just like pretty much ever other S10 print that's been submitted, I can't get this one to pass CTS. Are you sure there are no typos in the print and that 2020-08-01 is the correct security patch date? And it does pass CTS on your device?

Edit: I took a quick peek over at AndroidDumps and found a S10 fingerprint that passes. I'll add that instead.
[Magisk] denkmaster5:
Hello, sorry if this has been resolved before, the search wasn't very useful.

I have a unlocked Samsung Galaxy S8+ and am running twrp 3.4.0.0, BlissRoms v12.10 (Official), Android 10, with latest pico OpenGApps.

Magisk alone fails all SafetyNet checks.

Magisk Hide passes basicIntegrity

and MagiskHide PropsConfig with standard S8+ fingerprint passes ctsProfile

After rebooting, play store allows me to view and download Netflix. I can log in and browse, however video playback doesn't start. It gets stuck on "Loading..." similarly to how it was when it was failing SafetyNet.

I've checked Netflix in MagiskHide and installed it from APKMirror as well. I've also cleared cache and storage

I still can't get it to work. Any help is very much appreciated.
[Magisk] Didgeridoohan:
[MENTION=11022763]denkmaster5[/MENTION] If you can find and install Netflix, your Play Store should be "certified". But it's worth a check just in case (you didn't mention anything about that).

Other than that it sounds more like a ROM issue than a SafetyNet issue... Don't think there's more that I can help with here.
[Magisk] enotar:
Unfortunately thats break Samsung Store
[Magisk] Didgeridoohan:
That's known and expected when changing the model props.

You can try using my module instead of hardware off. That way you can pick a model that still leaves the Galaxy Store working. Try leaving it at the default value, or change manually (pick from the list) to S4 or S9. I've had reports those two work.
[Magisk] pndwal:
Are you still using Hardware Off module to spoof Basic Attestation?

If so, I'd remove it and try new "Force BASIC attestation" in this module:

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228/post83146179

https://github.com/Magisk-Modules-R.../master/README.md#force-basic-key-attestation

This is more likely to keep Galaxy Store and OEM features working, and offers flexibility to try alternative props that may work easily too. PW

Edit: Haha, redundant repetition! See post above too. ?
[Magisk] 73sydney:
Hehe youre supremely helpful, but by now id have thought you would know The Man always seems to be on top of things :)

In other news i have a feeling i might get to venture back to MHPC again as after 2 weeks on stock Google on my Pixel 2 XL im starting to get that custom ROM flashing bug...this is the longest ive ever been on a stock ROM...who knew pure Google Android was so good (after all the crud Samsung puts on devices it was like a breath of fresh air, maybe i should have parted with Samsung sooner) i really didnt need to fiddle, until now :)
[Magisk] pndwal:
Thanks, I'll take the complement, but it's true I forget which thread I'm in sometimes... sorry OP!

Yeah, when modules like this finally fail to do their thing, it seems Pixel may well be worth the extra bucks.

You may be in good company too. Another 'The Man' said:

More to the point, he said recently:

I'm equally annoyed by Xiaomi's MIUI bloatware, popup ads and surveys in apps, file cleaner apps who's notification can't even be dismissed without entering the app, etc, etc, and when I can no longer beat them with excellent mods from folks like John, Didg and yourself, I'm sure I'll need a Pixel too... or an IPhone ? ... But I'll probably last LESS than 2 weeks...

Its depressing to think post MagiskHide, post MHPC, post SQlite GPay fix... or post COVID19. Looks like nothing will be the same again. ☹️

If only Joe Average was less tolerant of the software abominations running on his shiny new hardware...

But I think there'll still be people thanking coders like you guys for whatever custom innovations you can create to unlock hardware potential for a good while yet... even if it's just to satisfy the urge to fiddle. (Essentially, I'm hoping that Open Source Android remains relevant...) ?

Meanwhile, happy modding your perfectly good Pixel. PW
[Magisk] Temujin38:
Hello,

I have a Samsung Note9 and i cant figure how to set the security patch date

Cause I tried to pass ctsProfile only with changing the fingerprint but it doesnt work, and I saw that I need to match the security patch date but I dont know how. I tried to go on Custom props but when I'm in the menu I dont know where to go and what to write

Thx
[Magisk] Didgeridoohan:
The easiest way is to just pick the Note 9 fingerprint from the included list. The security patch date is then altered to match automatically.

If you still can't pass after that you might have to also enable "Force BASIC attestation".

More:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] Temujin38:
Thx a lot, it works
[Magisk] dimon222:
Few questions

1. If I force Basic attestation, can I still simulate the other device's fingerprint? Is it possible to simulate "old" device while also keep the basic attestation?

2. Does device simulation also impact on modules that are being installed in Magisk itself? Like lets say AML/ACP that do specific driver tuning/installations based off type of device.
[Magisk] Didgeridoohan:
If you simulate an "old" device you'll likely force basic attestation by doing that... But yeah, it's still possible to use the device simulation option with basic attestation active. There'll be some discrepancies though, so if you're doing an "old" device it's likely better to just do that.

Depends on how the module checks your device. It's very likely they're using one of those props, in which case they will be affected. Might be better to install those modules with simulation disabled.
[Magisk] Didgeridoohan:
Update to v5.3.1-v97

So, considering that the CTS passing feature of the module might die any day now (or in a year or two, knowing Google :silly:), I've instead spent some time on other parts of the module. Have had this as an idea for a while, but never bothered committing the throught processes to it...

Apart from a few bugfixes and an updated fingerprints list (thank you [MENTION=4770208]Sid220[/MENTION], [MENTION=7758532]pepote666[/MENTION], [MENTION=7280276]ipdev[/MENTION], [MENTION=6345368]Displax[/MENTION], [MENTION=3974339]knojap[/MENTION] and [MENTION=2682152]enotar[/MENTION] for the prints), this update mainly adds a new feature to the custom props part of the module. I don't foresee many users actually having a need for it, but why not? You can now set a delay for when a custom prop is set (check the docs for details). Might be useful in a few edge cases, but more importantly it makes the module more "complete". :laugh:

Changelog

v5.3.1

Release notes

Added a feature to enable a delay for when custom props to be executed (during the late_start service boot stage). See the documentation for details.

Fixed a possibly longstanding bug where props couldn't be set using the ui on some devices (would get stuck on "Working. Please wait...").

Fixed some of the settings in an exported settings file not being set correctly.

Minor adjustments and bugfixes (mainly stupid bugs introduced in the last update).

Added fingerprint for Nokia 6.1, Samsung Galaxy S5, S10 and Tab S4 and Xiaomi Mi 10 Lite 5G. Updated fingerprints for Asus ZenFone Max M1, Google Pixel 2-4 (all variants) and Xiaomi Pocofone F1. List updated to v97.
[Magisk] Sid220:
I haven't followed deep the "CTS pass funeral" thing but i think that when it will happen it will be the death of rooting and modding for Android. I modded nearly every Android phone passen on my hands and gets me extremely angry that i could not be doing it in a year or two. My phone, my rules, my rooting and modding, period.
[Magisk] pndwal:
[MENTION=9317193]73sydney[/MENTION]

Yeah, will no doubt need to raise budget, and I'd be going for Pixel over iPhone for sure also, but I'm biased like most Android users. John may not be biased, but he has a vested interest... Let's not go there. ;)

But I have to say, in addition to support, it seems to me iPhone does have security sewn up also. Hate to say it, but I believe Google is playing catch-up with Apple here, as many developers, banks, businesses, corporations and government departments view iOS as the mobile platform of choice for security concious entities due to Apple's closed source and in house code and encryption techniques. Some even require members to ditch their Android devices and use company issued iPhones because of the lack of confidence in Android ecosystem security along with increasing concerns about scamming, hacking, cyber espionage, cyber warfare etc etc. Realistically, Google is pretty much forced to play catch-up considering the stakes, including stemming an increasing tide of customer opinion and loyalty changing as these threats inevitably increase.

All this said, fixed CTS and SafetyNet can be seen to be in the interests not only of security concious corporations and their customers, but clearly in the interests of Google themselves, and therefore (and I hate to say it) also of most of us, who want to see Android remain not only viable, but also a major player in the foreseeable future. (This rant may also stem the tide of Google's Naysayers if they ponder a little.)

Apart from Pixel, I think Android One devices may offer a similarly pure Android experience. - I'm a bit disappointed to hear rumours Xiaomi may be ditching participation in the program after only 3 models as I would be seriously considerering their A series. They polled users once re favourite OS ('skin') but decided to delete the results when 57% of users voted for the Android One experience which left their own MIUI 9 skin with only 43%. Go figure.

It seems Nokia are not so bent on spruiking their own OS flavour, and have a great range of Android One devices, so I may go back to Nokia in future. Hope they add great camera and ir blaster as I'll miss these Xiaomi strengths.

All you coders have followed in the tradition of Steve Kondik and Jorrit Jongma, and have contributed greatly to custom Android, especially the mods and fixes that can be applied across the (broad) range of devices. I hope end users / beneficiaries like me, are not about to let you forget it. Enough said.

I'm off to play Whack a Mole and maybe try Swap Torpedo. Hope to see you in a Sydney cafe somewhere with your full cream milk and Gear Buds in, not annoying the PFY too much...

(Promise I won't make this a habit OP :D ) PW
[Magisk] Didgeridoohan:
[IMG="I'll allow it."]https://i.imgur.com/ehUtz.gif[/IMG]
[Magisk] 73sydney:
To avoid any further and ongoing derail of The Mans thread, ill say this:

* I agree with all you have said.

* Nokia make some good Android devices.

* You've just made me remember i no longer have an IR blaster like i had in my Note 4 - so no more easy way to turn off the tele from the bed if i forgot to take the remote to bed with me (i live in one room), so ill have to get back out of bed and find the remote like a caveman again :)

* The PFY have everything to fear from me :)
[Magisk] Displax:
Xiaomi Mi A2

xiaomi/jasmine/jasmine_sprout:10/QKQ1.190910.002/V11.0.12.0.QDIMIXM:user/release-keys__2020-07-05

Xiaomi Mi A2 Lite

xiaomi/daisy/daisy_sprout:10/QKQ1.191002.002/V11.0.9.0.QDLMIXM:user/release-keys__2020-07-01

Xiaomi Mi A3

Xiaomi/laurel_sprout/laurel_sprout:10/QKQ1.190910.002/V11.0.20.0.QFQMIXM:user/release-keys__2020-08-05
[Magisk] GtrCraft:
Update for Poco X2:

fingerprint: POCO/phoenixin/phoenixin:10/QKQ1.190825.002/V12.0.1.0.QGHINXM:user/release-keys

security patch: 2020-07-01
[Magisk] knojap:
On my S7 Stock /Magsik / Edxposed / Magicprops my Bankingapp is working without Magisk Hide. Just have set a fingerprint for the S7 in props.

On my S5 Stock Magsik / Xposed / Magicprops my Banking app is warning me about a rooted phone. Safety Check also is not working. Tried to deinstall Xposed and set a fingerprint with props but still the same.

Any suggestion?

thanks
[Magisk] Didgeridoohan:
If it's just CTS that isn't passing:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check

If it's basic integrity as well:

https://github.com/Magisk-Modules-R...EADME.md#i-cant-pass-the-basicintegrity-check
[Magisk] knojap:
Ah sorry. On my S5 props isn't starting. It says the skricpt couldn't be loaded- tried to change the Bootstage without luck.
[Magisk] Didgeridoohan:
If you need help with that it would be best if you posted the module logs.

Most likely it's one if your modules causing issues with the Magisk boot stages.
[Magisk] Gymcode:
[Help] Unable to load module scripts

Help, I am unable to load the module scripts after running <su> and <props> command :crying::crying::crying:

Tried PetNoires SafetySpoofer, and SafetyPatch as well, but ctsprofile is still false.

Am on S10e, LineageOS17.1, Android 10
[Magisk] Didgeridoohan:
To be able to help properly I need those logs mentioned in the first screenshot.

Edit: nevermind, there they are.

And it's likely that the other modules can't help because you also need to force basic attestation for the bootloader state (once you get the module up and running you can do that too).
[Magisk] Gymcode:
May I know how can I implement a force basic attestation for the bootloader state? Is it a module that I can obtain in Magisk or somewhere?

Am running custom ROM , LineageOS, so it does not have the module :/
[Magisk] zgfg:
By using the option (2) in MHPC, use the latest version
[Magisk] Gymcode:
Yup I'm on the latest version, v5.3.1-v97.

As <props> does not work for me, I can only navigate by <props -s>

Number 2 on my screen is displayed as "Script Colors"
[Magisk] Didgeridoohan:
There's nothing apparent from your logs why the boot scripts aren't running, they simply aren't. You could try removing Safetypatcher and Petnoir's module and see if that helps. If it doesn't remove the other modules and see if things start working. If they do you can install your modules again, one by one until you find the one that breaks your device.

And yes, the force basic attestation is a feature in this module. There are also another module posted in the general Magisk thread by [MENTION=6345368]Displax[/MENTION]. I believe I have a link to that in my Magisk troubleshooting guide (see my signature).
[Magisk] Gymcode:
I tried to remove the other 2 hide modules but they didn't work too.

May I know if this is the module that you are referring to? Can I attempt to install it?
[Magisk] Didgeridoohan:
That is the one I was talking about (but you'll also likely have to change the device fingerprint, since you're running a custom ROM).

But before you do that, I would really appreciate if you could keep testing and try to get this module running. It would help for future reference and troubleshooting.

Please remove all other modules and see if the boot scripts starts working. Worst case you might have to install Magisk and install it again.
[Magisk] Gymcode:
Alright, I will remove all modules and see if it works.

If it still don't, will install the module.

Lastly if it all didn't work, I will flash my Magisk patched boot.img again and retry

Edit: Just tried all and didn't work, will reinstall Magsik now...

Do I need to uninstall Magisk by flashing the uninstaller, or can I just flash the Magisk-patched-boot.img again? :(
[Magisk] Didgeridoohan:
Yeah, autocorrelation did a number on my last post. I meant to write "

un

install Magisk and install it again"... So yes, first uninstaller and then reflash.
[Magisk] Gymcode:
Ouch! Have to uninstall it over again :crying:

I'll do it in a few hours time, 4 hours to wake for work. Will update again if there is any, on my progress.

Thank you Didgeridoohan :cool:
[Magisk] Didgeridoohan:
Hey... Don't do anything that is too cumbersome or that could mess up your device. It's not that important.

But, if boot scripts aren't running for you there is something very wrong with your Magisk installation.
[Magisk] nos1609:
Here is a certified fingerprint for Xperia 5 DSDS J9210

Sony/J9210_RU/J9210:10/55.1.A.9.52/055001A009005201481357772:user/release-keys

Security patch: 1 July 2020
[Magisk] Gymcode:
View attachment 5081345

I would prefer to have it right, in the long run :victory:

I suddenly remembered what I may have did wrong.

During my installation of Magisk, I patched my boot.img with Magsk, and flash it, but it didn't install Magisk after opening Magisk Manager.

I then search and downloaded beyond0lte-boot-magisk.img provided by Ivan_Meler, for Lineages.17.1 (but the build version that I am on is different, of 3 days). I then flash it to boot. After that Magisk was installed.

https://xdaforums.com/showpost.php?p=80962373&postcount=3

https://drive.google.com/drive/folders/1b8Q-BnbqdR-VxPxm4HheQNO3YDtf90qn

I will reinstall my ROM, and re-flash the magisk-patched boot img again :fingers-crossed:
[Magisk] Gymcode:
Oh man, I reinstalled everything with the ROM and magisk-patched boot.img in the Drive, but the same issue still occured :crying:

I am checking with Ivan_Meler as well on this, hopefully there is a solution to it :(

EDIT: I'm ashamed, it was actually caused by me not flashing magisk-patched boot.img immediately, but only after a reboot after flashing the ROM.

SOLVED!
[Magisk] Didgeridoohan:
That actually sounds pretty weird, and device specific. But I'm glad you got things up and running. :good:
[Magisk] amk316:
hi

the s10 probs did not work for me!!!
[Magisk] Didgeridoohan:
Take a look here:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] Didgeridoohan:
Fingerprints list updated to v98

A few fingerprints have been updated and one new addition. Thank you [MENTION=6345368]Displax[/MENTION], [MENTION=5293805]GtrCraft[/MENTION] and [MENTION=1575315]nos1609[/MENTION] for your submissions.

New

Sony Xperia 5

Updated

POCO X2

Xiaomi Mi A2, A2 Lite and A3
[Magisk] novalis01:
After changing the fingerprint on my Mi 10 Note Lite I still have the ctsProfile false.

I also cannot run any banking Apps.

Is there anything else I can try?
[Magisk] bouyhy01:
Hello

I nées fingerprint for redmi note 9s miui 10.10.00
[Magisk] ipdev:
Did you try the suggestions in the documentation?

I still can't pass the ctsProfile check GitHub - Link

The supported device (fingerprint) list is mostly user supported.

You can normally use a different device if yours is not in the list.

Can I use any fingerprint? GitHub - Link

If you need a fingerprint for a specific device for some reason, you can try to find it and submit it for the supported list.

Please add support for device X GitHub - Link

Finding a certified fingerprint GitHub - Link

How do I submit a fingerprint? GitHub - Link

Cheers all. :cowboy:
[Magisk] Doligem:
Please add my device fingerprint

Samsung A7 2018 (SM-A750GN)

samsung/a7y18ltedx/a7y18lte:10/QP1A.190711.020

I can't change fingerprint because my device doesn't in the list..

Please help. Thanks
[Magisk] zgfg:
You don't need to choose from the predefined values, you can redefine to any string you want
[Magisk] Doligem:
Yes I did, but my device didn't change fingerprint after that. I dont know how
[Magisk] Didgeridoohan:
You picked menu 1 (Edit device fingerprint), entered the fingerprint and then rebooted? And it didn't change? How did you check? With the getprop command? If you checked the build.prop file there'll be no difference, since Magisk doesn't actually touch the system files.

I'd love to add the device to the list, but what you posted earlier isn't the full fingerprint string. And I would also need the security patch date. Take a look here for details on submitting a print:

https://github.com/Magisk-Modules-R...aster/README.md#how-do-i-submit-a-fingerprint
[Magisk] zgfg:
1)

Huawei Mate 9 MHA-L29 (9.0.1)

-Not in your database

ro.product.manufacturer=

HUAWEI

ro.product.model =

MHA-L29

ro.build.fingerprint =

HUAWEI/MHA-L29/HWMHA:9/HUAWEIMHA-L29/9.1.0.275C432:user/release-keys

ro.build.version.security_patch =

2020-05-01

2)

Xiaomi Mi 9T European /Android 10

- Instead of your outdated:

Xiaomi/davinci_eea/davinci:10/QKQ1.190825.002/V11.0.1.0.QFJEUXM:user/release-keys

ro.product.manufacturer =

Xiaomi

ro.product.model =

Mi 9T

ro.build.fingerprint =

Xiaomi/davinci_eea/davinci:10/QKQ1.190825.002/V12.0.2.0.QFJEUXM:user/release-keys

ro.build.version.security_patch =

2020-07-01
[Magisk] Betrox:
please add support for Xiaomi redmi note 5 pro (whyred) android 10 security patch 5th August 2020.

(running EvolutionX rom)
[Magisk] Ryder.:
Device simulation (which i need for dark theme toggle and ar core services for my poor zenfone 5Z) makes asus camera force close when i press the button to take picture. Is this normal? Can't do anything?
[Magisk] Didgeridoohan:
https://github.com/Magisk-Modules-R.../master/README.md#please-update-fingerprint-x
[Magisk] Didgeridoohan:
Device simulation can very easily break a lot of things. Not much to do except revert the simulation changes whenever you need that particular feature of your device.

In your case, using a different camera app sounds like the easiest solution...
[Magisk] Valiante:
After installing this module, my "ok google" or "hey Google" assistant hotwords only work with the screen on.

Anyone have a solution for this? Super weird
[Magisk] Didgeridoohan:
Only by installing? You didn't set anything up (fingerprint, custom prop values, device simulation, etc)?
[Magisk] Valiante:
I followed this tutorial but this issue did not pop up until I installed this module. I did nothing else and passed SafetyNet whereas I was not passing it before.
[Magisk] Didgeridoohan:
Then I don't know that to tell you... If you haven't set anything up the module does pretty much nothing.

I don't see how it could be affecting anything unless you've activated something. But, if you send me the module logs I could at least take a look and see if there's anything obvious in there.
[Magisk] pndwal:
Could try Open Camera if you decide to keep simulating another device. May not have some Asus features, or fully utilise the hardware, but it's worth a try... Great app.

https://opencamera.org.uk/ PW
[Magisk] bouyhy01:
Hello

I tried every xiaomi device fingerprint for my note 9s but still not passing cts profile
[Magisk] Didgeridoohan:
https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] zgfg:
If you are on stock ROM you don't need to change fingerprint (full name: ro.build.fingerprint) but to leave the stock fingerprint and to use instead the option to force CTS Profile Basic mode attestation (option no. 2, must use new MHPC).

It will change four or five ro.product.* props, but in fact for MIUI you only need one of them: to redefine ro.product.model to something like "Undefined" (without quotes). That's it - you can even use the option to manually edit a particular prop, pick up ro.product.model, instead of "Note 9s" or whatever (real/meaningful) you find there, redefine to "Unknown" or so.

And reboot

PS: Ofc, Magisk hide option in Magisk Manager must be enabled (no more by default)
[Magisk] bouyhy01:
Thank you so much it worked after forcing the basic key , now google playstore is certified .
[Magisk] padraigdoran:
Hi,

I can pass SafetyNet with "Samsung Galaxy S10 Plus SM-G975F" but not "Samsung Galaxy S10 SM-G973F". It seems the signature isn't valid. This is when set in different ways using option 1 and 2.
[Magisk] Didgeridoohan:
Hi there.

I just did a double check and the SM-G973F print passes without issue on my devices. Not all prints pass on all devices, unfortunately. No idea why...