yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
You can also collect logs manually. Check here:

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs-etc

Without logs, there's nothing I can do.
[Magisk] Athing13:
yes i have 10 thread but still can not tell picture
[Magisk] Didgeridoohan:
I don't want a picture... I want the Magisk log file. Or better yet, the file created when you run the Collect Logs option from the props script.
[Magisk] Athing13:
This my log,im sory im can't upload log via xda

https://www.dropbox.com/s/cvirwktlx1chw7u/Log.html?dl=0
[Magisk] Didgeridoohan:
Didn't show much, unfortunately.

As I said before, the reason you have issues with this module, the fingerprints option being disabled, is the Universal SafetyNet Fix module. It also changes the fingerprint, so I disable that option in my module if you have it installed, so as not to create conflict.

But, I think you're going about things in the wrong way. You mentioned earlier that you can't get either ctsProfile it basicIntegrity to pass, and then there's nothing this module can do. You need to figure out why SafetyNet isn't passing before you can do anything.

I'm a little curious as to what Rootbeer Sample reports, since I see that you have it on the Hide list. Can it detect Magisk, or are all the checks green? That's a good indicator of MagiskHide is working at all on your device.

Last question I have for you: do you have Xposed installed? If so you can forget about passing SafetyNet.

Go back to the guide I've linked you a couple of times. Read through it, make sure your device matches the basics for MagiskHide to work, and try the things written in there. If you can't get it working, go to the general support thread and continue your troubleshooting there. This is getting off-topic for this thread.

Here's the link to the guide again:

https://www.didgeridoohan.com/magisk/MagiskHide

Pay close attention to this part about SafetyNet:

https://www.didgeridoohan.com/magisk/MagiskHideSafetyNet

And if you still need help, follow the last part:

https://www.didgeridoohan.com/magisk/MagiskHideHelp
[Magisk] Jaiiiiiiiii:
Cts true but not certified

I jave safetynet tru both cts and integrity but in my playstore play protect is not certified.

Is there any other fix other than using this?

And if i use this , can i delete magisk prop? and will it destroy or delete what i set with it?

Thanks
[Magisk] zgfg:
If Google Playstore still shows Device not certified:

- Airplane mode On

- Settings, Apps, Manage apps, enable Show system services, search for Google

- For Google Play Store, Google Play Services and Google Services Framework, delete Cache and Data

- Reboot, Airplane mode Off and give it a time for Google Play to sync

If you remove MHPC, you will loose CTS Profile fix
[Magisk] textbook:
I am currently using a OnePlus 7 Pro with the latest open beta Oxygen OS... Can I use your module to copy my current fingerprint, then factory reset my phone to downgrade, then install one of the latest ROM's, then apply the old fingerprint?
[Magisk] Didgeridoohan:
If you want to use that fingerprint, use the getprop command to grab it:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#the-getprop-method

And don't forget that you need to match the security patch date as well:

https://github.com/Magisk-Modules-R...E.md#matching-the-android-security-patch-date

Once you've got your system up and running the way you want it you can apply the print manually or make a custom prints list.

But, it's also worth remembering that you don't actually need to use the absolutely latest fingerprint to pass SafetyNet, unless you really want to, and that there are prints for the OP7 Pro already available in the module list.
[Magisk] Sid220:
[MENTION=4667597]Didgeridoohan[/MENTION] new fingerprint for Xiaomi Pocophone F1 aka beryllium

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

MIUI version 11.0.9.0

Android 10

Security Patches 2020-06-01
[Magisk] xuxu1:
SafetyNet works with edxposed.

In EdXposed settings Enable "App list Mode" and "Pass safetynet" then activate at "Applications(Black list)": play store, play Services and Google framework. Then Download und Enable HiddenCore Module. Restart and it should work. :)
[Magisk] Didgeridoohan:
As far as I've seen, HiddenCore is mostly cosmetical and can't fool a proper SafetyNet check.
[Magisk] Qi Xuan:
Hi,

Redmi 6 Pro, Android 9

ro.build.version.security_patch=2019-12-01

ro.build.fingerprint=xiaomi/sakura/sakura:9/PKQ1.180917.001/20.1.9:user/release-keys

ro.product.model=Redmi 6 Pro

ro.product.manufacturer=Xiaomi

Thank you so much!
[Magisk] Didgeridoohan:
Thank you, but I cannot get this print to pass CTS on my end. Have you tested it yourself and does it pass for you?
[Magisk] 73sydney:
Devils avocado, [MENTION=4667597]Didgeridoohan[/MENTION]

But is it still best to try a valid fingerprint over Force BASIC key attestation? Or am i tring to equate/conflate two different issues?

Asking for a friend :)
[Magisk] zgfg:
Stock firmwares are certified and they have valid fingerprints. For them you must only force Basic CTS to hide that Bootloader is unlocked

You need to fake fingerprints for custom ROMs
[Magisk] Didgeridoohan:
If your device is using hardware attestation it doesn't matter what fingerprint you set, CTS won't pass. And if it isn't using hardware attestation there's no need to use the force BASIC option...
[Magisk] pndwal:
You can keep whatever fingerprint you like / used before. But you can now additionally select older model prop(s) automatically, or manually from devices already on fingerprint list, which give BASIC attestation if they aren't on Google's list of models with hardware for tee. Regards, PW

Edit: Wow- I see I'm no. three! You must be VIP!...
[Magisk] textbook:
Thank you, that was perfect info for walking me through my usage of your module. But yes I understand that I don't need the latest fingerprint to pass. Currently I don't need your module to pass, but the OxygenOS beta is preventing me from call recording, I want to switch to a ROM that will allow me to record calls. That is my only reason for changing my image really. I enjoy OxygenOS beta other than that one problem.

I read that switching to a ROM can cause safetynet failure even with the latest canary magisk/edxposed... But your module apparently fixes that issue for ROM's, and normally I would just use the fingerprint from your list because that is easiest, but when I tested your module it gave me a fingerprint for the Indian version of my phone and I didn't know how that would affect my interactions with Google, so I wanted to ask if it is possible to copy my own unique fingerprint and then just re-use it on myself.

Thank you again for the help.
[Magisk] 73sydney:
No, im just a slightly confused end user/grunt :) Youre more VIP than i am :)

---------- Post added at 12:19 PM ---------- Previous post was at 12:08 PM ----------

Thanks all, appreciate the clarification

For my old Note 4, it only does basic attestation, so option #2 has no effect, but next week ill be moving up to either an S8/9 or a Pixel 2/3 XL (havent decided which yet, still second hand shopping), so i'll revist the isuse when that happens...new device possible new challenges... :)

My poor old Note 4 has finally reached EOL (randomly working), turns out a 6 year old phone, which has more ROM's flashed to it than most people have had hot dinners drew the line at being used as a 24/7 hotspot because my landlord hired incompetent IT people to break our wifi system, and keep it broken for a month :) Suspect the added heat and the known issue with EMMC has finally done her in

Poor Note 4, she got me through many years for a massive AUD$150 investment (bought second hand with not a mark on it). Im not looking forward to buying a device with a non-removable battery though....

Back to my second hand Android phone hunt/safari....
[Magisk] hyborian:
When I run props, i am always getting "No Connection" while it is checking for connection, whether on wifi or mobile.
[Magisk] Didgeridoohan:
The only thing that log shows is that yes indeed, there's no connection.

--- google.com ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

Seems like the terminal emulator doesn't have an internet connection for some reason.
[Magisk] hyborian:
Ok, I'll check on that soon. It happens on 3 phones. It could be the app NetGuard which I just installed, which has a VPN causing some problems with apps using wget commands and others.

---------- Post added at 06:09 PM ---------- Previous post was at 05:47 PM ----------

Ok, thanks for confirming, it was Netguard and its VPN that caused the problem. Temporarily disabling it made props connection go through.
[Magisk] ipdev:
Guess I'll do anything to avoid writing and updating instructions. :p

While on my Asus fingerprint odyssey.

I stumbled across a ZenFone M1 for a price I could not pass on.

Great deal actually, turned out to be a new one. I expected a slightly used/refurbished one for the price. ;)

Android 8 is still the official.

Android 9 was in beta. (Development was refocused to 10.)

Android 10 is still in beta.

The beta prints are certified.

Had to use the vendor fingerprint with the rom security date for Android 9 build.

ZenFone M1

-An update to the Android 8 print.

-Add Android 9 and 10 print(s).

---

Question/suggestion about the fingerprint list.

Xiaomi is confusing to begin with.. ;)

With POCO and Redmi becoming their own brand(s), makes them a little confusing to find in the fingerprint list.

Users may not know to look under Xiaomi, when their device is not listed under the POCO or Redmi section.

What do you think about switching Xiaomi Pocophone F1 into POCO?

All the Xiaomi Redmi devices into Redmi?

Cheers. :cowboy:

PS.

I am not sure how you are splitting the prints into manufacture/brand categories.

I'm guessing this would require the prints to be renamed.

Xiaomi Pocophone F1 to POCO F1 and Xiaomi Redmi <NAME> to Redmi <NAME>
[Magisk] Didgeridoohan:
[MENTION=7280276]ipdev[/MENTION] Xiaomi is confusing, yes... What I've been doing so far is categorising the prints according to what brand is used in the actual fingerprint.

Xiaomi Pocophone F1:

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

POCO F2 Pro:

POCO/lmi_eea/lmi:10/QKQ1.191117.002/V11.0.6.0.QJKEUXM:user/release-keys

I have previously thought about how to categorise these prints, but since there are other parts of the module that use the brand extracted from the print I landed in this method.

For now I don't think I'll change it, but I'll run the idea through the little grey cells once more.

Thanks for the prints.
[Magisk] Displax:
Pixel`s update

Pixel 2=google/walleye/walleye:10/QQ3A.200805.001/6578210:user/release-keys__2020-08-05
Pixel 2 XL=google/taimen/taimen:10/QQ3A.200805.001/6578210:user/release-keys__2020-08-05
Pixel 3=google/blueline/blueline:10/QQ3A.200805.001/6578210:user/release-keys__2020-08-05
Pixel 3 XL=google/crosshatch/crosshatch:10/QQ3A.200805.001/6578210:user/release-keys__2020-08-05
Pixel 3a=google/sargo/sargo:10/QQ3A.200805.001/6578210:user/release-keys__2020-08-05
Pixel 3a XL=google/bonito/bonito:10/QQ3A.200805.001/6578210:user/release-keys__2020-08-05
Pixel 4=google/flame/flame:10/QQ3A.200805.001/6578210:user/release-keys__2020-08-05
Pixel 4 XL=google/coral/coral:10/QQ3A.200805.001/6578210:user/release-keys__2020-08-05
[Magisk] BlackVoltage:
Seems I have a problem which looks alike but needs a different solution.

=> MagiskHide Probs Config V5.3.0-v95 installed and shown in my magisk 20.4 /7.5.1. Manager.

=> "Only core mode" has never been activated.

=> I use Termux typed su (which worked) and "probs" (and tried also "Probs") with always the same output:

What can I do? My Phone is a Samsung Galaxy S9 Duo with lineage 17.1

Thanks a lot in advance!

Sammy
[Magisk] Didgeridoohan:
[MENTION=11006415]BlackVoltage[/MENTION] Hi there. The command is "props".
[Magisk] zgfg:
The module is called Magisk Hide Props Config, not Probs.

It is also Props in the title of the thread, not Probs

And the command for terminal is props, not probs
[Magisk] Lange_666:
Info:

Installed (upgraded) from MagiskHide Props Config V5.2.7-v94 to MagiskHide Props Config V5.3.0-v95 but then certain bankapps no longer work (Belgium: amongst them the KBC app).

Downgraded again to previous version V5.2.7-V94, all works again.

Latest version of Magisk and Manager.
[Magisk] Didgeridoohan:
Hm...

I don't see how any of the changes in v5.3.0 could trigger a detection. What features/settings do you have enabled/set up?
[Magisk] Lange_666:
You mean with(in) MagiskHideProps Config through the means of a terminal?

If so, none, i just install it in Magisk (and update it everytime there's an update available) and leave it as default.

When i first started using Magisk some of my banking apps didn't work, they always came up with a rooted device message.

After installing your module, all of them all passed without a hickup until the latest version. The apps that now detect root didn't get an update after i installed 5.3.0-V95 so i wondered…

Just had another try, updated again to 5.3.0-V95 and the KBC app came again with a rooted device message (and won't open any further).

Went back to the previous version 5.2.6-V93 again, KBC app passes without a problem.

If you need extra info, just let me know.

Thx in advance.
[Magisk] Didgeridoohan:
So you mean you haven't even activated any feature of the module? In that case you can uninstall it... It does nothing unless you at least set up a certified fingerprint (and that only helps with SafetyNet's CTS check).
[Magisk] Didgeridoohan:
[MENTION=7782412]Lange_666[/MENTION] Which app is this, and can I test the root detection without being a customer?
[Magisk] Lange_666:
No i didn't activate anything, never have.

Like i said, i just installed the latest, KBC detects root again, if i remove it and don't install the module in Magisk, it also detects root. If i downgrade back to anything older then 5.3.0. then root is not detected by the KBC app.
[Magisk] Didgeridoohan:
[MENTION=7782412]Lange_666[/MENTION] Apart from letting my know what precise app this is, could you post the logs for both v5.2.7 and v5.3.0? For comparison to see if there's anything that stands out...
[Magisk] Lange_666:
I'm a bit lost now, wanted to create the logs and ran the KBC app again, it came back with a root message now on 5.2.6. I never had that before. I only saw it pop-up for the first time in a long time after installing 5.3.0.

So i removed the module completely, rebooted and ran the KBC app without the module installed in Magisk, KBC passed without root message (Magisk Hide is used, and was also before).

So for the moment i don't have the module installed… something else must be triggering the root message, and not always either...:confused

---------- Post added at 12:48 PM ---------- Previous post was at 12:47 PM ----------

After discovering the above, i took another approach.

At that moment: no module installed, KBC app does not detect root (with Magisk Hide active).

Removed KBC app from Hide: KBC app detects root.

Put KBC app back under Magisk Hide: KBS app does not detect root.

Installation of 5.3.0 module --> reboot --> KBC detects root!!

Removed KBC app from Hide and rebooted (with the 5.3.0 module installed): KBC app detects root.

Put KBC app back under Magisk Hide and 5.3.0 installed, rebooted: KBS app does not detect root!!!

Ran props command in Terminal and installed correct fingerprint for my device again (39), rebooted: KBC app does not detect root.

Gonna leave it this way for now.

Must say that Magisk 20.4 with Manager 7.5.1 does not always runs stable. If i open it, sometimes it flickers like mad... only way to get out of this is closing and re-opening.
[Magisk] Didgeridoohan:
[MENTION=7782412]Lange_666[/MENTION] Sounds like your MagiskHide setting doesn't always survive a reboot.
[Magisk] Lange_666:
Yeah, it seems to have nothing to do with the module version. It only happened the first time after installing 5.3.0 and when i then went back to 5.2.5 or 6 or 7 it was all fine again.

Updated back to 5.3.0 and bang...same issue. Must have been bad luck. That's why i thought the module was the culprit. Turned out not to be.

Now still need to find out why the Hide setting does not always survive a reboot.

Just rebooted 3 times in a row, Hide setting is still OK (for now). Also found out that i don't need to reboot to make the KBC app work again if it detects root after a reboot, just unhide, leave Magisk, re-enter and rehide again does the trick.
[Magisk] 73sydney:
I have to say my life got very boring yesterday when i swapped from my old Note 4, to a Google Pixel 2 XL...

Because of the list of things i didnt have to do to get things working

Amongst them setting props using MHPC to get my Gear Buds + to work out of the box, set a fingerprint using MHPC to pass CTS

A little bit sad i no longer need to use this module [MENTION=4667597]Didgeridoohan[/MENTION] :(

Or run 2 app stores (official and Aurora - with spoofed device to update apps that werent presented to a Note 4 running Q) :)

Feeling spoilt with the low maintenance on day one of #PixelLife
[Magisk] Didgeridoohan:
On some setups/devices MagiskHide can be troublesome when rebooting. But that's usually quite consistent. It's possible that when doing a module the extra stuff that happens during boot has the potential to mess things up. I'm only guessing though...

Let's hope things work from now on.

And thank you.
[Magisk] knojap:
Hello, I've got an S5 G900F. on rooted stock and one device on LOS 17.1.

I can get the fingerprint on the stock device by: getprop ro.build.fingerprint

But now i don't know what to do with it? The documenary is to complicated for me.

What do i have to do with the fingerprint to get it on the LOS 17.1 device?

Thanks
[Magisk] Didgeridoohan:
You have a few options actually.

Submit the fingerprint to me and I'll include it in the next update.

Type it in manually in the "Edit device fingerprint" menu.

Create a custom prints list.

Use the configuration file.

Use the already included S5 fingerprint, even though it is for a G900H. You don't actually have to match either device or Android version for this method to work.

If there's anything specific you're wondering about any of the methods described above, don't hesitate to ask.
[Magisk] knojap:
1. Fingerprint: samsung/kltexx/klte:6.0.1/MMB29M/G900FXXU1CRH1:user/releasekeys

2. What do I have to put in manually? The whole Line? "samsung/kltexx/klte:6.0.1/MMB29M/G900FXXU1CRH1:user/releasekeys"

3. To complicated? Don't know exactly what to put in the prints list

4. To complcated for me??? Don't know exactly what to do

5. Have done the G900H Step on my LOS17.1 device. No my banking app is working. But safteynet still is red. But that don't bother me. Maybe it's abpout Xposed Framework. My Banking App is working and I'm happy :). Thanks

6. But it doesn't work for my rooted stock device. Maybe it depends on Step 2-4 thats to complicated for me.

After dooing terminal: su -> props

it tells me

the service.sh module script does not appear to have run doing boot.

tried to change boot stage and boot script. But doesn't change. Maybe it's because of Xposed Framework which i can't disable.

Thanks
[Magisk] Didgeridoohan:
Tested the print and it's passing CTS, so I'll add it to the list in the next update. There was a small typo in it though and it was necessary to change releasekeys to release-keys.

If you enter the print manually you'll have to do the full line, yes. Just remember to fix the above mentioned typo.

If you do want to use the custom prints list you simply create the file printslist (no extension) on your internal storage and put this in it:

Samsung Galaxy S5 G900F (6.0.1)=samsung/kltexx/klte:6.0.1/MMB29M/G900FXXU1CRH1:user/release-keys

Using the config file is similarly simple. Add the full fingerprint to the CONFFINGERPRINT variable in the configuration file, place the file on your internal storage and reboot.

CONFFINGERPRINT="samsung/kltexx/klte:6.0.1/MMB29M/G900FXXU1CRH1:user/release-keys"

Xposed will definitely cause you to fail SafetyNet, no way around it. You might be able to pass if you use EdXposed, but I cannot help with that since I have no experience with it.

Your stock rooted ROM will not need this module, since it already has the certified fingerprint. If you've got further issues with root detection you can find some tips here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] knojap:
This is confusing. Have got also an S7 Stock root / edxposed. Banking App doesn't work but after installing Magiskhide prop -> su -> props selecting Fingerprint fom the List the banking app is working. Without Hide and active edxposed. So why it ain't work on the S5 wit Android 6? Maybe because of Xposed instead Edxposed?
[Magisk] Qi Xuan:
Hi, u said the test is use terminal to set fingerprint?
[Magisk] zgfg:
You need terminal to set props.

To verify CTS, use SafetyNet checker apps, or simply Magisk Manager

Always study a documentation first - go to OP post #1, find a link there
[Magisk] Qi Xuan:
Hi, Yes I tried terminal to set props, but I can't found my phone model inside.
[Magisk] walkwitmeinhel:
My device is zte nubia red magic 3s but i dont find in fingerprint list ...my cts profile is false any help???
[Magisk] zgfg:
Install SetEdit, there you can see all props whatsoever:

https://play.google.com/store/apps/details?id=by4a.setedit22
[Magisk] Didgeridoohan:
I tested the fingerprint in the module, yes. You can do the same if you want, described in more detail in the docs. Some guidance here:

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

And regarding the print you provided, where did you get it?
[Magisk] Didgeridoohan:
Relevant parts of the documentation:

https://github.com/Magisk-Modules-R...ob/master/README.md#can-i-use-any-fingerprint

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] walkwitmeinhel:
What is this i dont understand plzz
[Magisk] Didgeridoohan:
If your device isn't on the list you have a couple of options:

Use another fingerprint (the first link I posted).

Find the fingerprint for your device and submit it to me for inclusion in the list (the second link I posted).
[Magisk] Didgeridoohan:
The fingerprint info from that build.prop passes CTS just fine (I just tested it).

Two things I can think of right of the bat that might be causing issues:

If you're using that fingerprint in your ROM you also have to make sure that the security patch date matches the print. For that particular print it'll need to be 2020-06-01.

Your device is using hardware backed key attestation and you need to use the model spoofing trick (while it still works).
[Magisk] enotar:
Sorry what I meant to say is that it pass when it is stock oem locked and not rooted but building the custom room with oem unlocked and rooted with magisk this is when I get ctsProfile=false.

Not sure if this is different now?
[Magisk] Didgeridoohan:
Custom ROMs have to spoof the device fingerprint to pass CTS. If you're not doing that you have to use the fingerprint from that build.prop instead of the one you get from your build.

That the kind of info you need?
[Magisk] enotar:
Ok Flashing Hardware Off module give ctsProfile to pass! Thanks

What I dont understand is that should raise the level of security or I am wrong?

Example netflix should be on Widewine L1 instead of L3 as it was with stock, sorry if this is off topic.
[Magisk] Didgeridoohan:
I don't think you'll get Widevine L1 by just passing CTS. Pretty sure it's more complicated than that... You're right though. It's not something you'll find in this thread, mainly because I know nothing about it. :laugh:
[Magisk] enotar:
Thanks so much, that help a lot.

So now I am set for ctsProfile.No need of anything else?
[Magisk] Didgeridoohan:
That should be it. Sounds like you're good to go... Good luck.
[Magisk] i_am_fresco:
How to extract fingerprint archives to apply in other devices (same model/android version but rooted)?