yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Yes. I also wrote "or with the inbuilt feature". Check the link...

But, honestly it doesn't sound like this module is the culprit if it broke your recovery. It's just a simple prop change that happens long (relatively) after your device has started booting. Of course, stranger things have happened I guess...
[Magisk] nikhilmanudhane:
how can it be checked via the inbuilt feature?

I don't know what went wrong, clicked on edit fingrprint, selected my device (Redmi K20 pro India - Sr. No. 73), flashed it and rebooted.

Now stuck in reboot mode. :(

M new to the rooting world, sorry if I am bugging you, but can you please help :)
[Magisk] Didgeridoohan:
Read the link, it's all described there...

But, here's a TL;DR (but there are more details on the linked docs):

Either use Safe Mode to disable all modules or disable Magisk by flashing your stock boot/recovery image. Then you can boot up the device, place a file called reset_mhpc in the root of your internal storage and lastly reenable the module or flash the Magisk patched boot/recovery image. The next reboot will reset the module and things should start working again.
[Magisk] nikhilmanudhane:
Hi, Thanks.

I somehow managed to get into recovery mode by flashing dtbo, vbmeta and twrp.

Now when I install ROM (evo X) and A11 firmware, click on reboot, it still enters into a fastboot loop.

Repeated the above process twice, but same result.

Any way i can delete entire data and perform a clean install?

I don't care about the data anymore, just want a working phone :(
[Magisk] Didgeridoohan:
If it's Magisk related (as in module) you can remove the module(s) manually in TWRP. They're in /data/adb/modules.
[Magisk] sabei:
@Didgeridoohan apologies as I know you have said you cannot pass without GAPPS but, ignoring that, can you suggest if it is worth trying to edit the device fingerprint below and if so which of the two options makes more sense?

Xiaomi Redni Note 8, magisk, Aesop Extended 7.3 Android 10. However the underlying firmware was 11.09.0 which was for 9.

Security patch is July 5 2020.

According to my settings Fingerprint set to google/coral/coral:10/QQ3A.200705 etc

The 2 listed fingerprints in your list are one for Android 9 11.0.11 190616 or 10, 12.0.1.0 200114 - I am guessing the last number is the security patch date but they seem a little old in each case?

I have also installed the safety net fix.

Should I even try and if so which one makes more sense?

Thanks.
[Magisk] Didgeridoohan:
@sabei The two fingerprints available in the module for the Xiaomi Redmi Note 8 both have a security patch date of 2020-09-01 (the numbers you mention are part of the build ID). So a year old, but that doesn't actually matter since the actual security patch date of the ROM won't change when you set a print, only the prop value.

If it's an Android 10 ROM I'd use the Android 10 print... But that's all a moot point if you don't have Gapps installed.
[Magisk] NOS_bzone:
Hi again dev,

I want to ask about is possible to make fingerprints Pixel 3 running Android 12 Beta 4 get certified? 😁

If yes i need your help.. 🙏

- Device Fingerprints: google/blueline/blueline:11/RQ3A.210805.001.A1/7474174:user/release-keys

- Security Patch Date: 5 Aug 2021

Thanks a lot..
[Magisk] Didgeridoohan:
I'm not sure what it is you're asking... What do you mean by "to make fingerprints"? As long as Google has certified the A12 beta 4 build you can use that builds fingerprint to pass CTS. But you can just grab that from the build in question.

The print you're posting here is just the latest A11 print available for the Pixel 3. It's already in the module...
[Magisk] sumitplall:
Hi there, I am running LOS18.1 on my essential ph1 with Magisk module.

The CTS safety net passes and so does the play store.

Till now the banking apps were also running all good on it. However one of the apps got updated and started detecting that it's a rooted phone and doesn't run.

Magiskhide and hiding Magisk app also doesn't work.

Hoping props module might just make it work by changing the device fingerprint.

My question is that can I use Android 10 PH1 fingerprint itself? Or do I need build a fingerprint for android 11?
[Magisk] Didgeridoohan:
If you pass CTS that LOS build is already using a certified fingerprint. Changing to another one will make no difference...

Most likely suspect these days is that it's detecting the Magisk app, even though it's hidden. Full app obfuscation is pretty much impossible at the moment (A11 remedies this, but since apps aren't required to use those changes yet nothing can be done).

Could of course be other stuff as well. Check my guide here for more tips:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] ipdev:
@NOS_bzone

@Didgeridoohan

Google did certified the spb4 builds.

spb4.210715.014-factory

My Pixel 5 (redfin), clean stock install with a locked bootloader.

Defaults to 'basic' evaluation type on spb4. :unsure:

SafetyNet passes and PlayStore is certified.

---

With a Magisk patched boot image (unlocked bootloader) I fail ctsProile.

Still only using 'basic' evaluation type.

Have some issues installing Magisk canary on redfin spb4.

Can only boot the patched image.

If installed it borks the device.

FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')

Magisk patched image or stock boot image, same error.

I had Magisk canary installed on spb3 using the direct install option (if failed cts also).

I have not tested much on SDK31.

I hope things calm down and/or get sorted so the official Magisk repo is updated to support SDK31.

Maybe another dev can be given Direct Access for the time being. [Ability to modify and commit updates into the official (and canary) repo(s)]

Cheers. :cowboy:

PS.

Why not. :D

Attached the Pixel spb4 prints and props.
[Magisk] sumitplall:
Thanks for the page. I didn't try anything else but as a first step I tried uninstalling the Magisk app itself which worked for me.

So turns out the Magisk app even after hiding it, is getting detected and hence the problematic app was not allowing.
[Magisk] Displax:
Pixel 5a

Google Pixel 5a (11):Google:Pixel 5a=google/barbet/barbet:11/RD2A.210605.007/7381860:user/release-keys__2021-06-05
[Magisk] Displax:
Actually not, just temporary whitelisted for testing period. All CTS procedure completely disabled here.
[Magisk] NOS_bzone:
Sory this the fingerprint A12 Beta 4.1 (codename:blueline):

- Fingerprint: google/blueline/blueline:12/SPB4.210715.014/7654839:user/release-keys

- Security Patch: 5 Agustus 2021
[Magisk] ipdev:
@NOS_bzone

As Displax noted.

The spb4 builds are passing temporarily until the beta testing is finished.

Then the prints will be invalid.

The spb4 fingerprints (matching security date) passed when I did a quick test the other night.

I tested a few on my Nexus 7 (2013)[Lineage 18.1] and a few on my Pixel 3aXL [abc rom].

Both are Android 11, August security patches.

You can use the spb4 prints while they are valid.

The file I attached in my previous post can be used as a custom printslist.

Just rename it to printslist and move it to /sdcard/

MHPC Documentation - Custom fingerprints list - GitHub - Link

When you runs props and choose to edit the fingerprint, a Custom option shows in the list of manufactures.

--

Are you running the Android 12 beta?

If so, then you already have the factory fingerprint and security date set.

In my brief playing on Android 12, I did not get SafetyNet to pass with Magisk active.

I had to disable verify boot (AVB) to install Magisk on redfin with spb4.​

I am not sure if you can pass SafetyNet on spb4 with Magisk currently. :unsure:

--

Have to wait until Android 12 is official before the prints get added.

I am sure Displax will be on top of it when it happens. ;)​

Cheers. :cowboy:
[Magisk] B1aster:
Hello everyone.

Help me figure it out.

After climbing on GitHub, I came across an article about magisk and a way to check SafetyNet. Everything, as I understand it, rests on a fingerprint.

MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf

This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com

GitHub - Magisk-Modules-Repo/MagiskHidePropsConf: This tool is now dead...

This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com

GitHub - Magisk-Modules-Repo/MagiskHidePropsConf: This tool is now dead...

This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com

That is, if you take the file build_fingerprint.txt from the firmware of a non-rooted phone and a verified one and throw it into a rooted phone, then the verification will be passed in SafetyNet?

The Samsung a10 phone costs India firmware and root, SaferyNet everything except CTS is passed. The same Basic certification shows. When installing the Universal SafetyNet Fix module, the phone hangs on loading and you have to sew again. There is no such phone model in the Termux emulator.

If I understood everything correctly, then I need to flash the phone, pass the SaferyNet check, pull out build_fingerprint.txt file from the firmware, then install root, and then replace build_fingerprint.txt file, so the CTS SafetyNet check will be passed, is it correct?
[Magisk] Didgeridoohan:
@B1aster If you're still on a stock Samsung ROM you will not need to mess with fingerprints. You will need to fool the keymaster though, which means you will need the Universal SafetyNet Fix...

There's a new version of that fix that will be released for everyone soon (currently only available as a pre-release for the devs Patrons). If you can't get the current release of USNF working wait for v2.0.0, it should have many issues like what you're describing fixed. If you need further help with USNF you should turn to that mods thread:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
[Magisk] B1aster:
When installing the module using your link, magisk returns an error.
[Magisk] Didgeridoohan:
That's because you're not using v2.0.0... It will fix all that. You just have to wait for it's release.

But like I said, this is not the thread for support for that module.
[Magisk] Chicada:
Hello,

Please add for J6

the fingerprint is "samsung/j6ltedx/j6lte:10/QP1A.190711.020/J600GDXUACUB3:user/release-keys"

Thanks.
[Magisk] Didgeridoohan:
No worries... What's the security patch date?
[Magisk] la0pe0Ue:
Is the systemless modification of props expected to survive even if Magisk Hide is dropped (https://www.xda-developers.com/magisk-development-continues-without-magiskhide/)?
[Magisk] Didgeridoohan:
Yes, it will.

And I'm currently working on implementing into this module those parts of MagiskHide that rely on changing prop values. Unfortunately I don't have the know-how to create a proper MagiskHide module, but once someone does that at least they won't have to bother with the sensitive props (unless they want to)...
[Magisk] nononymous:
HI, i wanted to add the fingerprint for Motorola Moto Z3 Play (android 9 version, security update to 1st july 2020)

Motorola Moto Z3 Play (9):Motorola:Moto Z3 Play=motorola/beckham/beckham:9/PPWS29.131-27-1-27/34b6d:user/release-keys__2020-07-01

i have already tested it on my phone and i have passed the checks
[Magisk] eternalvarka:
Hi guys. I have pixel experience A11 magisk installed. All modules activated, passes safetynet test.

When I try to change fingerprint in props config i start to fail safetynet test. when i get back to default fingerprint - safety net test passes. whats the problem? why cannot i change device id? safetynet universal fix installed and reinstalled. still the same. samsung a 40.
[Magisk] Didgeridoohan:
No idea... Post the logs that show your setup when SafetyNet is failing.
[Magisk] Fif_:
Reporting that I've been getting SN CTS profile mismatches today on a OnePlus 8T running stock OOS.

I didn't need this module yesterday to pass SN. I've tried using it but the latest certified signature it proposes for my device is the same it already has.
[Magisk] Didgeridoohan:
Google is working on things on their end... Check the main Magisk thread and you'll see that it's been discussed a bit already. You can use XprivasyLua or spoof the model prop with MHPC. There's also a small tweak to the USNF module that @Displax posted in there that should do it for you.

I'm in the middle of testing and working out some bugs for the next release of MagiskHide Props Config, and since I never really removed the code for forcing BASIC key attestation from the module that will also be included in that update. Will be an option for those that want it while Google is tinkering.

This is a reminder that we're living on borrowed time though and that Google eventually probably will be able to lock us out of SafetyNet for good... Or maybe someone finds a new way to circumvent whatever they throw our way. We'll just have to wait and see.

Fun fact: OnePlus devices, like your 8T, is the reason that Google haven't been able to fully enforce hardware backed key attestation yet. OnePlus managed to bork up their implementation of it so bad that Google have had to go back to the drawing board.
[Magisk] Ryano89:
Any idea what model prop should be used? I'm on 8t with Havoc Rom
[Magisk] ShaDisNX255:
That actually is a fun fact lol kinda funny.
[Magisk] eternalvarka:
anybody has props fingerprint change working on lineageos/another os? A11. thanks. galaxy a40
[Magisk] Fif_:
I've had success with this module:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-83028387

Or you can just drop this in post-fs-data.d:

resetprop ro.product.model BASIC
[Magisk] osm0sis:
Note that will make Google start referring to your device as "OnePlus BASIC" everywhere, so I came up with this solution: https://xdaforums.com/t/magisk-general-support-discussion.3432382/page-2379#post-85578747
[Magisk] Didgeridoohan:
If things continue as they did before, any prop value that doesn't match your actual device should work.
[Magisk] Didgeridoohan:
You can find tips on how to find a print in the docs:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] eternalvarka:
Sorry Im quite sure the problem is in not my approach. I used both devices A20, and A40 for checking this. Lineage OS custom rom lets to change fingerprints, however google pixel experience doesnt .
[Magisk] Didgeridoohan:
Sorry... I misunderstood. I thought you were looking for a print.

If something isn't working as expected, please post the logs from then the issue is present.
[Magisk] zulu88:
After installing the update, the phone screen was reduced to 2/3 of its normal size. I could not do anything. Uninstalling and installing the previous version of MagiskHide helped. Samsung Galaxy Note9.
[Magisk] Didgeridoohan:
The heck? I knew something was going to break (something always does once I start tinkering with new stuff), but that's a weird one.

Logs please (and I'll need those from when the issue is active)...
[Magisk] zulu88:
Logs sent.
[Magisk] Didgeridoohan:
Logs recieved. But, unfortunately there's pretty much nothing in there I can use... I have one thing that I know I'm going to change with this update that might be causing issues for some. It's a tiny thing and I'm probably gonna have that out there in just a short moment. But, would you mind testing a version with this fix before I release it, to see if that's the thing?
[Magisk] zulu88:
No problem ;)
[Magisk] zulu88:
The test version works fine. I have not noticed any errors (y).
[Magisk] Didgeridoohan:
Great. I'll whip something up and have a fix release out soon(-ish).
[Magisk] eternalvarka:
So as i said i checked it on lineage and everything works fine. On google pixel experience safetynet starts fo fail when changing the fingerprint. Applying 2 versions of logs, both failing safetynet check.
[Magisk] jaccydan:
Hi, I am attaching my issue here:

https://xdaforums.com/t/working-mag...s-of-gms-17-1-22-on-pie.3929950/post-85584223

As you can see I've updated MagiskHide Props Config to v.6.0.0.

Still no joy with SafetyNet. This has just occurred over the last couple of days.

Any help much appreciated in advance.
[Magisk] pndwal:
Actually, this is MagiskHide Props Config module thread, not Magisk General Discussion thread. 😉 Sorry I didn't give the link; it's here (early fixes and some notes on developments, but read last few pages. 🙂 ):

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85573141

Early fix

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85573473

Other notes

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85582201

👍 PW
[Magisk] gfrank227:
OK so I updated to the new version that includes all the MagiskHide props. SafetyNet still fails without MagiskHide, though. Am I correct in assuming that setting these props are NOT a complete substitute for MagiskHide?

I would love to fully divorce my device from MagiskHide while 23.0 is still installed so that I don't have issues but have been unable to completely do so.

Any insights would be greatly appreciated.
[Magisk] gfrank227:
OK, so I had the same problem. Safetynet started failing on Thursday night. The solution I found is posted here. Somebody created an awesome youtube video that explains how to use xposed module XPrivacyLua.

https://xdaforums.com/t/safetynet-suddenly-fails.4328253/#post-85584799
[Magisk] Didgeridoohan:
Only updating to v6.0.0 won't do anything to help with the new SafetyNet issues. You'd have to at the least (probably, YMMV) activate Forced BASIC key attestation, possibly in combination with USNF (but that varies).

It's also possible to use XPrivacyLua on Google Play Services, as mentioned above (and in quite a few places now).

The links @pndwal provided is a good summary of the current discussions in the general Magisk thread.

All this might change tomorrow though, as Google keeps tinkering...
[Magisk] Didgeridoohan:
XPrivacyLua is one of the ways of going about fixing the new SafetyNet issues, changing model props is another. For the latter you'd either have to create your own boot script (quite easy and mentioned a little earlier in the thread), use one of the modules that have been posted in the general Magisk thread or use the Forced BASIC key attestation feature of MHPC v6.0.0.

The MagiskHide sensitive props that was added to v6.0.0 is in preparation for the next Magisk release and any possible new MagiskHide modules that may or may not need to be created, it's not a substitute for MagiskHide.
[Magisk] jaccydan:
Thanks for the responses, you guys are great! This video posted by @gfrank227 looks to be the way for me to go. The guy in the video states that it should work for most devices - I am hoping it will work for my s20 Ultra?

He also says during the video that there's a possibility of bootlooping after installing these modules..wouldn't want that, but he did provide a link for a fix.

I'm going to try this now anyway. I will report back my results.
[Magisk] super_nooby:
what exactly does the module actually do and what do i need it for as a galaxy s9 user?
[Magisk] Didgeridoohan:
Short answer: it changes prop values and you might need it to help you pass SafetyNet or to change any props on your device systemlessly.

Long answer would take very long to type... And since I've already spent all that time creating the docs you might want to start by checking those out and then come back if you have any further questions after that.

Module docs can be found here:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md
[Magisk] jaccydan:
I've just followed the video posted by @gfrank227 and have found that:

1. Magisk SafetyNet passes. ☑️

2. Using 'SafetyNet Test' app, the test fails - coming back with the same 'Can't access Google Play Services' message. ❌

3. In Google Play app > Settings > About, the option of Play Protect Certification has disappeared; so can't see whether device is certified or not.❌

I have not had the opportunity to test the Google Pay app yet at a terminal or online to see if working, but the above errors are worrying.

However, he did mention at the end of the video that if there's any issues with 'banking apps' then go back into XPrivacyLua and hide them in there - so wondering if that would apply to Google Pay?

Wondering if anyone has a fix for the SafetyNet Test app, and the issue with the Google Play Certification issue described?

Many thanks in advance.
[Magisk] Didgeridoohan:
First of all, please note that this is the support thread for MagiskHide Props Config, not general SafetyNet/Magisk troubleshooting.

Second, that app you're using to check SafetyNet is probably just maxed out. There's a limit on how many SafetyNet checks an app can do per day without paying Google a fee. Try a different app...
[Magisk] jaccydan:
Just rebooted my device and now the 'SafetyNet Test' app passes as well as passing in Magisk - so that's a good result and I'm assuming my Google Pay will work again.

However, there's still that issue in the Google Play App where Play Protect Certification option is not appearing.

Does anyone know how to get that back? And will it cause any issues?

Thanks in advance.
[Magisk] jaccydan:
I apologize @Didgeridoohan if I've posted to the wrong place; I seem to have a habit of doing that on these forums as I find it difficult to narrow it down to the specific issue. Not sure If I search for the exact things correctly either. :confused:
[Magisk] Didgeridoohan:
There's both the general Magisk thread and a specific GPay discussion thread where this topic is much better suited.
[Magisk] jaccydan:
@Didgeridoohan - Thank you for your time and patience. 🙏
[Magisk] Didgeridoohan:
Quickfix v6.0.1 released

A small update pushed. See the previous release notes for details.
[Magisk] Didgeridoohan:
I'm not seeing anything that stands out in the logs. The print props are being set as expected.

What if you use a different fingerprint, one that more closely matches the ROM used (Android version, etc). If you could provide me with a newer fingerprint (Android 11) for the A20 I could add that to the list...
[Magisk] gfrank227:
That's what I figured. Thank you!
[Magisk] gfrank227:
if it hasn't come back already, clear your play store app data.
[Magisk] swour:
Updating from 6.0.0 to 6.0.1 upon starting the module in a terminal and while making changes the following line appears:

/system/xbin/props: /data/adb/mhpc/propsconf_late[24]: 2: inaccessible or not found

Another observation with the reintroduced option to force basic attestation. When choosing my device from the list, the entry will be "Pixel 2 XL" which has at least one side effect of a new device showing up in the Google device list. Changing that to "Google Pixel 2 XL" this entry disappears.
[Magisk] Didgeridoohan:
What changes? When does that error appear, and could you post the logs showing it?

And "Pixel 2 XL" is the model name for that device hence that's what will be used when spoofing the model props with the "Force BASIC key attestation" feature. Although, picking your own device when using that feature does nothing...
[Magisk] Tiemichael:
SafetyNet started failing for me with a 'CTS-fail'.

I am using a Poco F2 Pro with Stock Android 11 and Magisk 23.0 with MagiskHide Props Config v6.0.1 and Universal SafetyNetFix V1.20.)

Google Playstore says that my device is certified (not surprisingly)

The recommended installation of RIRU, LSPosed and XPrivacyLua seems the fix the missing certification of the device which is not my problem.

What is your recommendation to overcome this issue?

Thanks!
[Magisk] Didgeridoohan:
Play store certification will soon be your problem... If CTS fails, sooner or later (often sooner) you'll lose certification.

You can use "Force BASIC key attestation" that was reintroduced with v6.0.0 of this module to spoof the model prop to one other than your current device, or use another of the model prop modules that can be found in the general Magisk thread, or use XPrivacyLua. All or some of those options seems to work for most.