yashsingh1/xdaforums huggingface dataset:
[Magisk] dron39:
Ok, don't understand regarding configuration file and how to use it in this case, but custom prints list is look like what i need. Thanks!)

How to correctly add this "/DS" in device name?

And it showed in option 1 (edit device fingerprint) but it's blank in option 2 (Force basic key attestation).

Why?
[Magisk] Didgeridoohan:
You've got some permissions issues. Which is weird, because the files that there are issues with (according to the logs) are internal module files and that should not be a problem... I guess you've already tried uninstalling the module and installing it fresh (if not, do that)?

Here are a couple of things to check/try...

What's the output of this command in a terminal:

su -c ls -1l /data/adb/mhpc

You could also put this code in a file that you put in /data/adb/post-fs-data.d, and give it execution permission:

LOG=/cache/mhpc_test.log
ls -1l /data/adb/mhpc > $LOG
echo "" >> $LOG
getprop >> $LOG

Once you've rebooted you can post the mhpc_test.log file from /cache and hopefully this might give a hint as to what is going wrong.
[Magisk] Didgeridoohan:
Regarding "/DS", that depends on where you want to add it? This is what the line will look like in the module list once I update it:

Samsung Galaxy Note 20 Ultra 5G SM-N986B/DS (10):samsung:SM-N986B=samsung/c2sxxx/c2s:10/QP1A.190711.020/N986BXXU1ATJ1:user/release-keys__2020-10-01

I don't add the custom prints list values to the devices under "Force BASIC key attestation" (for reasons, but mainly because I don't have control over the custom prints list and that they actually contain the model value). If you do want to set a specific model value that isn't in the list, use the custom option, or if you have actually included the model value in the list string you can use "Device simulation" and enable the model prop simulation there.
[Magisk] dron39:
>>use the custom option.

Ok, should I type only this in custom option for force basic attestation

samsung:SM-N986B=samsung/c2sxxx/c2s:10/QP1A.190711.020/N986BXXU1ATJ1:user/release-keys

Or i can add this too?

__2020-10-01 too ?
[Magisk] Didgeridoohan:
"Force BASIC key attestation" only uses the model prop value. In this case "SM-N986B". But, if that's your device (and it uses Hardware backed key attestation) you shouldn't enter this value. To force basic attestation you need to use a

different

value from your own model. You might want to read the module docs: https://github.com/Magisk-Modules-R.../master/README.md#force-basic-key-attestation
[Magisk] dron39:
No, it's not my model. I have SM-N9860 and want to pick devise close to mine (N986B/DS) for force basic attestation.

So i have to put there SM-N986B and that's all? Or should I additionally enable fingerprint (option 1) of this model too?
[Magisk] Didgeridoohan:
If your device is using the stock ROM you do not need to change the fingerprint. And, if your device uses hardware backed key attestation so that you fail CTS, all you need to to is to enter SM-N986B as a custom value in "Force BASIC key attestation" and you should be good to go.
[Magisk] zgfg:
Nobody can tell you the winning combination until testing them

Hence suggesting you to try yourself (others can only guess but at the end it may not work for you - results depend on Mr. G.). You can easily enable only Force Basic, then add Fingerprint if you want, also to change the model under Force Basic and/or Fingerprint

These are two different options (working on different props). Hence test and try - you must reboot upon each change in MHCP

Eventually, you can also try the option Device Simulatiion - but if testing that option, disable Fingerprint and Force Basic to avoid conflicts

You can always look into /data/adb/modules/MagiskHidePropsConf/system.prop (textual file) to see which exact property changes will be enforced upon reboot:

prop name = new string value
[Magisk] nico22320:
I come-back for my pixel 5 and Connexion issue in module. When i'm french carrier connexion don't work but when i'm in WiFi it work for fingerprint update and check module update.
[Magisk] knojap:
...

su -c ls -1l /data/adb/mhpc

result

ls: unknown option '-1' Aborting

LOG=/cache/mhpc_test.log

ls -1l /data/adb/mhpc > $LOG

echo "" >> $LOG

getprop >> $LOG

result

2x mhpc_test.log

1 =0 byte

1 =1 Byte

Both are empty.
[Magisk] Didgeridoohan:
[MENTION=3974339]knojap[/MENTION] Skip the 1 then and just use -l. The 1 was just to make it pretty and easier to read.
[Magisk] knojap:
.

su -c ls -l /data/adb/mhpc

Result

127|root@klte:/data/data/com.termux/files/home #

su -c ls -l /data/adb/mhpc

-rw-rw-rw- root root 0 2014-03-27 21:00 defaultprops

-rw-rw-rw- root root 2503 2020-11-17 16:54 propsconf.log

-rw-r--r-- root root 3294 2020-11-17 09:18 propsconf_install.log

-rw-r--r-- root root 2195 2020-11-17 09:18 propsconf_late

-rw-r--r-- root root 34968 2020-11-17 09:56 propsconf_verbose.log

-rw-rw-rw- root root 114 2020-11-17 16:54 script_check
[Magisk] Didgeridoohan:
Exactly as I expected it to look. Good.

If you do the same modification to the boot script? Or rather, change it to this so that we also catch any errors (possibly):

LOG=/cache/mhpc_test.log
ls -l /data/adb/mhpc > $LOG 2>&1
echo "" >> $LOG 2>&1
getprop >> $LOG 2>&1
[Magisk] knojap:
dont understand.

which script?

where to find?

what to do?

thx
[Magisk] knojap:
Please can you tell me what do i have to do exactly? I don't understand your last comman?

Thx
[Magisk] cookieisland:
Please add Moto X (2013) XT1053 Fingerprint

[MENTION=4667597]Didgeridoohan[/MENTION] could you add Moto X (2013) fingerprint to the module? The following info is from the last official ROM provided by Motorola. It passes SafetyNet Test.

C:\>adb shell sh
shell@ghost:/ $ getprop ro.build.fingerprint
getprop ro.build.fingerprint
motorola/ghost_retail/ghost:5.1/LPA23.12-15/15:user/release-keys
shell@ghost:/ $ getprop ro.product.manufacturer
getprop ro.product.manufacturer
motorola
shell@ghost:/ $ getprop ro.product.model
getprop ro.product.model
XT1053
shell@ghost:/ $ getprop ro.build.version.security_patch
getprop ro.build.version.security_patch

shell@ghost:/ $ cat /proc/version
cat /proc/version
Linux version 3.4.42-g030aaa2 (dbbuild@ca88lnxdroid25) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Fri May 8 14:48:55 PDT 2015
shell@ghost:/ $

Device info:

Moto X (2013), XT1053, ghost

Android 5.1 Retail.en.US

Device passes when tested with "SafetyNet Test" App
[Magisk] Didgeridoohan:
I'll start by quoting my first post regarding this:

What I mean there is that you should create a boot script, a file that you place in /data/adb/post-fs-data.d. Make the file executable (chmod 755 is a classic) and put this in it (don't run the command separately in terminal, that was just for the first ls command):

LOG=/cache/mhpc_test.log
ls -l /data/adb/mhpc > $LOG 2>&1
echo "" >> $LOG 2>&1
getprop >> $LOG 2>&1

When you then reboot the log file will be saved and we might now a little bit more about what happens during boot. Maybe...
[Magisk] knojap:
Here it is
[Magisk] Didgeridoohan:
Yup... For some reason, your device is very limited during boot. Could you try to switch to the beta channel and install Magisk v21.1?
[Magisk] knojap:
When trying to install magisk 21.1 with magisk:

Unable to repack boot image!

Installation failed.

Than i downloaded the magisk zip and installed via TWRP.

That works and props also is starting.

Set my banking app to magiskhide.

But the banking app still chrashes at start :(
[Magisk] Didgeridoohan:
Great! So, possibly some kind of incompatibility with your device and and Magisk v20.4. Or maybe there was just something wrong with your installation and a new one was in order.

Regarding bank apps, just setting a new fingerprint and passing SafetyNet is not any kind of universal fix. Most bank apps utilise more detection techniques. I've gathered a bunch of tips on hiding root from from apps here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] alanz0r:
I cannot find my galaxy A70 in the samsung devices list, someone can help me please?
[Magisk] Didgeridoohan:
That's because there isn't one. So far, nobody have submitted a print for that device.
[Magisk] xunholyx:
Sharing is caring.
[Magisk] SykoraLukas:
Hey. If I use this on stock MIUI rom should I change fingerprint or just force basic?

Does this module really work or it just fakes safetynet status like edxposed module?
[Magisk] zgfg:
If SafetyNet test in Magisk Manager shows:

- Basic Integrity PASS

- CTS profile fails with HARDWARE attest

and if you don't have other things like Edxposed (story for itself) then you should be ok with only Force CTS BASIC in MHCP

Btw, you can set and test it in 5 minutes (reboots included)

Althogh Force Basic will change few props, only ro.product.model is important.

That change tricks the SafetyNet (you can also test it then with an independent SN tester app), i.e. Google Services to use Basic mode, and with that G will no more see that Bootloader is unlocked.

Hence no placebo or fake SN result

Btw, having Mi 9T, tested and worked with MIUI 12.0.2 and 12.0.3 EEA
[Magisk] Didgeridoohan:
That depends on if the stock ROM is certified or not:

https://github.com/Magisk-Modules-R...b/master/README.md#what-option-should-i-use-1

The module fakes how Google perceives your device and the SafetyNet check will therefore pass (for real) because Google's systems think you are using a device that they have certified/uses basick key attestation.

TL;DR: it works.

If you know what you're doing you don't need this module though... It's just a bunch of fancy scripts to make it easier for those that don't know how to use the resetprop tool/don't want to bother with it.
[Magisk] walkwitmeinhel:
My phone is zte nubia 5S btw can i use oneplus fp??
[Magisk] walkwitmeinhel:
Ok i used op8 fp and all working good cts true ..thanks
[Magisk] alanz0r:
What i do in the Galaxy A70 to pass safetyNET?
[Magisk] Haywireugg:
Redmi S2/Y2 not available in the list

As stated, Xiaomi Redmi S2/Y2 is not available in the list. I've owned this device for almost 2 years now but the annoyance continues cuz I can't use some local payment apps after due to the false cts profile.

Please let me know how can I help in the process. I want this device on the list. Please
[Magisk] zgfg:
CTS profile failing - you probably don't need fake device fingerprint but simply Force Basic attest (OP post #1, MHPC Guide on Github + repeating Q/A in previous posts)

Submitting device fingerprints - same hints (post #1, Guide, previous posts)
[Magisk] Pandemic:
Download safetynet check from playstore and see if it still pass, i tried but no go ;)
[Magisk] Didgeridoohan:
Not sure if you're asking for help, or just generally letting us know that you can't pass/don't care about passing SafetyNet...

But anyway, here's some info that might possibly be relevant:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] Haywireugg:
I'll try to submit the fingerprint myself tomorrow.

The 'Force Basic Attest' option is supposed to work if the device shows ' evalType Hardware' alongside the attestation error, according to the support doc, and most devices actually use 'Basic evalType' for attestation so it failed even after doing what you suggested. Thanks for the quick reply tho?.

I'm working to submit the fingerprint myself. So, thanks afterall ?
[Magisk] zgfg:
If CTS fails for you with Basic attest then you must have other issues like not certified firmware (needed to try by fakimg fingerprints), somethimg else like Edxposed (out-of-scope for Magisk/MHPC discussion)

However, many users just cry about SafetyNet failing ('suddenly', is their any solution or similar comments showing their degree of being up-to-date) and not providing details sometimes even upon being asked does Basic Integrity and/or CTS Profile fail, does CTS Profile show Hardware or Basic attest mode, do they use stock or custom ROM, what Magisk modules they have, etc

Hence it is first aid/suggesting them to try Forcing Bssic CTS

Btw, about stating that SN fails for most users with CTS Profile using Basic attest - I wouldn't agree, you probably don't count those who already solved their problem by forcing Basic CTS profile attest ?
[Magisk] mrhamed:
Can I hide bootloader-state on Nvidia Shield TV 2019 Pro to enable AI upscaling while unlocked bootloader? Does anyone do that?

Download Rom: https://fichiers.touslesdrivers.com/65830/nv-recovery-image-shield-atv-2019-pro-8.2.0.zip

I tried to

Force BASIC key attestation

but after NVidia-Logo, stuck on black screen (no remote control, no network)

=====================================
Force BASIC key attestation
=====================================
Edit device model to change bootloader state check from hardware based to basic.
Do you want to enable forced BASIC key attestation?
The currently loaded value is: [B]SHIELD Android TV[/B]

y - Yes (use default value, mdarcy)
n - No
d - Pick from device list
c - Custom value
e - Exit

This may disable some device specific features, like the Samsung Galaxy Store. YMMV.
See the module readme or the support thread @ XDA for details.
Enter your desired option: y
Working. Please wait...
Working. Please wait...
MagiskHide Props Config v5.3.6by Didgeridoohan @ XDA Developers

Any idea?
[Magisk] Didgeridoohan:
First of all: is the device using hardware backed key attestation (evalType = HARDWARE when you do a SafetyNet check in the Manager)? If so, the only known way to bypass that is to fake the model prop to a different value than your actual device (that's what "Force BASIC key attestation" does).

Haven't heard about anyone having issues booting after doing that though...

I would need to see the module logs to be able to say anything:

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

You could try some things though, as well, for example using the custom props function to only edit ro.product.model and setting it to a random value.
[Magisk] mrhamed:
Thank you for your reply.

As you know I've black-screen only but as I remember the red square with 2 errors on center of TV screen.

Did you mean Nvidia Shield 2019 Pro product?

Sure, can I run the props script from TWRP ? or where is the require log file ( I can try " adb pull " to copy)

I have no idea :o
[Magisk] Didgeridoohan:
[MENTION=5827138]mrhamed[/MENTION] If you're asking about how the get the device booting again you're in the wrong place... :D

Best I can give you is the built-in option to disable or reset the module:

https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module

If you need more than that you're better off asking for help from other Nvidia users...
[Magisk] mrhamed:
No, I didn't I want to share log file with you by using twrp (if possible and log file stored some where)
[Magisk] Didgeridoohan:
You'll find that info if you follow the link I posted previously. There's a "collection logs manually" section.
[Magisk] JKurtz87:
Galaxy Z Fold2?

Unlocked my bootloader on my z Fold2 was wondering if the module will get support?
[Magisk] Didgeridoohan:
As usual, I respond to that query with a link to the docs:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x

But, keep in mind that if your device is still using the stock ROM you won't be needing to change the device fingerprint, and if it's using hardware backed key attestation to detect the bootloader state you have to use a different device from your own... Possibly relevant parts of the docs:

https://github.com/Magisk-Modules-R...b/master/README.md#what-option-should-i-use-1

https://github.com/Magisk-Modules-R.../master/README.md#force-basic-key-attestation
[Magisk] renato1978:
Hello,

i have a Samsung A70 with Android 10.

i execute props command from terminal ... i selected option 1, and option f, i selected 26 for samsung, but my phone is not in the list.

What can i do?

thank you
[Magisk] mrhamed:
I got error evalType BASIC

Device is Nvidia Shield TV 2019 Pro v8.2-dev-root and I want enable AI upscaling while bootloader is unlocked.
[Magisk] Didgeridoohan:
See the post just before yours. I've replied to a very similar query there.
[Magisk] Didgeridoohan:
Enable MagiskHide (in the Manager settings)...
[Magisk] mrhamed:
Same result...
[Magisk] mrhamed:
I'v been spend 2 hours to bring back my device today, after install "MagiskHide Props Config" and enable "magisk hide" and reboot device, I got black screen after nvidia logo again!:crying::crying::crying:

The adb is working, the magisk command working too but props command does not works.

I'v to spend some times again to bring back device :crying:
[Magisk] Didgeridoohan:
I don't think you need this module. Your SafetyNet issue is likely casued by EdXposed or another of your modules. More on that here: https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet

The reason I told you to enble MagiskHide eariler is that it showed in the logs you posted that it wasn't. And if it isn't enabled it can't help you hide the bootloader state. And since your device is using basic attestation MagiskHide can actually do that...

Now that you have enabled MagiskHide, see if your AI upscaling works.
[Magisk] mrhamed:
- I bring back my device again and didn't install "MagiskHide Props Config"

- In magisk " enble MagiskHide" only (as you sad)

- I got black screen after nvidia logo again :'(
[Magisk] Didgeridoohan:
In that case this sounds like something you guys need to figure out in your device's community... This thread is not the place for it.

A small thought on where to begin though: If it's MagiskHide causing your issue, make sure that you haven't added a bunch of system processes to the Hide list. If that's not the problem it could be caused by one of the props that MagiskHide changes. You can find which those are here: https://github.com/topjohnwu/Magisk...0c0/native/jni/magiskhide/hide_policy.cpp#L12
[Magisk] zy54917118:
Hello, thank you very much for your previous help, I tried all the operations within the scope of my ability in the link you provided. (In the last reply, my phone can now fully pass the Google security verification, and the mask has the hidden function checked, and the magiskmanager has been re-Android with other package names) (now I tried to delete the magiskmanager, close the developer options, and use The island isolates the software, etc., which has no effect) I installed the magiskmanager on the unlocked phone. After the game program detects the magiskmanager, it crashes. After uninstalling the magiskmanager, the game can run normally. After deleting the magiskmanager on a rooted device and a mobile phone with a magiskhide installed, the game still crashes. Now it is suspected that the game can detect the magiskhide and rooted. Now I ask if there is any way to solve this problem.

I wonder if you can help me solve the crash problem of the OCTOPATH-TRAVELER game software for a fee?
[Magisk] mrhamed:
Thank you so much for your, reply.

Can you help me: How revert/disable "magisk hide" from adb-command or twrp?
[Magisk] Didgeridoohan:
Sorry, but no. While I would love the extra cash (I'm a piss-poor student), that is not something I have the time for (since I'm a piss-poor student with tons of schoolwork).

And, on top of that it is currently very easy for a developer that knows what they're doing to detect Magisk even with MagiskHide active (from what I've seen a current favourite is Isolated Processes) so it can be quite tricky to figure stuff like this out.
[Magisk] Didgeridoohan:
From TWRP it should just be a matter of deleting the magisk.db file in /data/adb (if I remember correctly, which I might not).
[Magisk] zy54917118:
Thank you for your reply. I will try to find a way again. I might ask you for help now and then. so grateful. Wish you success in your studies.
[Magisk] GtrCraft:
New device, POCO X3 NFC:

fingerprint: POCO/surya_global/surya:10/QKQ1.200512.002/V12.0.4.0.QJGMIXM:user/release-keys

security patch: 2020-10-01
[Magisk] daavve:
I have problem to run a SAP success Factory on Magisk Root. I used a magisk hide but aplication can't still open this aplication. Do you have some solutions?
[Magisk] zuelber:
Gpay

Hi there.

I have a Mi 9 Lite global running stock Miui 12 with android 10. My phone is failing to pass cts Profile. My goal is to use Gpay. (I am using Magisk for Gcam and to unlock Android Auto)

I have already tried to force basic attestation but cts still fail.

In the fingerprint list there's a Mi 9 Lite FP for Android 9 only. Can i try it using Android 10 or it's dangerous and not recommended?

I've ready something about sending to the dev the FP, I am not sure how to do that. If you experts could teach me, I'd be glad to help other users.

Thanks,
[Magisk] Didgeridoohan:
Generally there are no issues using an older print. If you want to submit a newer print than that's available you can find some info on that here:

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

But, since you are using the stock global ROM I would expect that you could pass CTS out of the box. Have you enabled MagiskHide?
[Magisk] zuelber:
So is it safe to use a fp from Android 9 even when phone is running Android 10?

Later on I will read carefully the link and try to extract Android 10 fp.

Yes, MagiskHide is enabled. Any other tip to try?

Thanks.
[Magisk] Didgeridoohan:
It should be perfectly safe.

More tips on passing SafetyNet can be found in the module docs and in my general Magisk troubleshooting guide.
[Magisk] Mew789:
Hi,

I wasn't able to pass saferynet due to false ctsprofile. With your help, I now can pass safetynet, but gpay is not working : your phone doedn't respect security...

Any Idea ?
[Magisk] zencooler:
You need to clear cache and data of GPay and GMS. Then restart the phone and set up permissions 440 for dg.db file and then set up your cards in GPay from the scratch. It should work for you.
[Magisk] Mew789:
Thanks for your help. What is GMS ?

---------- Post added at 05:12 PM ---------- Previous post was at 05:01 PM ----------

Google play services ?
[Magisk] zencooler:
Yes. Google Płay Services = GMS (not GPS [emoji6]).

And one more thing: turn on "Flight Mode" to turn off the radio during the clearing cache and data of GMS and GPay. After restart you can turn off "Flight mode" and then set up cards in GPay. Good luck.
[Magisk] geekborg:
Please add meizu m6note to the fingerprint list (FlymeOS)
[Magisk] Mew789:
It didn't work...

I closed "gpay" and "Google play services for AR", wiped data and cache for both, rebooted and changed chmod for dg.db to 0440 but no changes...

Edit : it's working ! I have to delete data from "Google play services" and not "Google Play Services for AR".

I have a OnePlus 8 with pixel experience 10. Some apps tell me I'm on a pixel 4A. Is it better to choose OnePlus 8 in2013 or Google pixel 4a as fingerprint ?
[Magisk] bartleby999:
Google Play Services for AR is the wrong one. That is for Augmented Reality.

You need to wipe Google Play Service
[Magisk] zencooler:
Doesn't matter but it's always better to choose the model closest to your real one.
[Magisk] zgfg:
AR = Augmented Reality, you needed (as you observed at the end) to clean Data for G P S, not G P S for AR
[Magisk] Mew789:
Thank you all for your help !
[Magisk] An68:
You can find GMS under app/show system