yashsingh1/xdaforums huggingface dataset:
[Magisk] Displax:
Xiaomi Mi A3

Xiaomi/laurel_sprout/laurel_sprout:10/QKQ1.190910.002/V11.0.19.0.QFQMIXM:user/release-keys__2020-07-05
[Magisk] ipdev:
Hi.

I tried the print and security date from the stock rom available on Asus's website.

Asus Download-Center Asus Website - Link

Asus ZenFone Max Pro M2 (ZB631KL) (WW) / Max Pro M2 (ZB630KL) (IN) (9):asus:ASUS_X01BD:=Android/sdm660_64/sdm660_64:9/PKQ1/16.2017.2007.094-20200705:user/release-keys__2020-07-05

I could not get it to pass CTS.

Tested on Android 10, Nexus 7 (2013) (aex), Pixel 3a XL (abc) and Poco F1 (Lineage).

At-least it did not break Basic Integrity. (I have had that happen when testing prints.) ;)

Had the same results awhile back with factory roms for a ZenFone 5Z and a Moto G6.

Recovery flashable roms that do not include a recovery image.

I do not have a M2, 5Z or G6, so I could not test it further.

If you have a stock device that is passing SafetyNet, you could pull the active prop values from that and compare.

I'm not sure if the end resualt will be a working fingerprint on a custom rom or a different device.

To grab the active props, use the getprop command in a terminal app or adb shell.

To send the output to a file use getprop > NameOfOutPutFile

Make sure you are in a directory that has read/write access /sdcard/Download/ for example.

When I pull the props from an active device with getprop, I also use sed to format the output to be the same as a regular prop file.

getprop | sed 's/\]: \[/=/g; s/\[//g; s/\]//g' > getprop.props

The above getprop command will send the output to a file called getprop.props.

Cheers. :cowboy:

PS.

If anyone is interested, Max Pro M2 from UL-ASUS_X01BD-WW-16.2017.2007.094-user.zip

system/build.prop PasteBin - Link

vendor/build.prop PasteBin - Link

META-INF/com/android/metadata PasteBin - Link

Let me know if I missed something. :)
[Magisk] oslo83:
Any more info ?
[Magisk] Didgeridoohan:
On a Play Store certification fix? Not really.

If you're not familiar with it, the GPay fix edits a database file so that Pay doesn't recognise that Magisk is installed (or something along those lines). My thinking is that maybe there's a similar file for the Play Store that can be edited to make it always appear certified.

Not something I'm going to be looking closer at though...
[Magisk] kayamokid:
the problem is i dont have a stock certified fingerprint of my device....... that's why im using other device build fingerprint....
[Magisk] ipdev:
Stock factory image/update did not work.

Neither of us have access to a stock device.

Time for option 3. Check custom roms.

Remember to give credit where credit is due.

There is an official LineageOS build for Zenfone Max Pro M2.

The currently used fingerprint can be found in lineage_X01BD.mk GitHub - Line-49

LineageOS official builds do not support security date patching so, a little trial and error testing needs to be done.

The security date will be YYYY_MM_01 or YYYY_MM_05

You need to figure out the year month and day, the print was certified with.

Testing on my Nexus 7, this one passed SafetyNet.

Asus ZenFone Max Pro M2 (9):=asus/WW_X01BD/ASUS_X01BD_1:9/PKQ1/16.2017.1910.071-20190920:user/release-keys__2019-10-05

I'll test a little more tomorrow and make sure it works on other devices..

Cheers. :cowboy:
[Magisk] :
I just found out that by renaming the device to another name worked to pass again.

I tried renaming the device to Galaxy S20

failed.

Then i renamed it to Galaxy A70

passed

it seems to be targeting certain models.

anyway, it worked for me and my comment is just a theory..
[Magisk] Didgeridoohan:
Yes, from that I've seen it seems that you can change the model prop to whatever and you'll get a basic attestation check, as long as you don't use a model name for a device on Google's list.

I'm gonna add a small extra feature for forcing basic attestation to the module in the near future.
[Magisk] pndwal:
Great news!

I'm SURE it occurred to you, but menu options to select model to spoof for this prop from a list of models that give basic attestation in addition to 'unknown' value, would be useful for many.

Eg it now seems spoofing Galaxy S4, S9, A70 can allow Galaxy Store to work for Samsung users.

... Sorry to state the obvious. :D

And who knows, this may be a viable fix for... quite a few days! :p PW
[Magisk] Didgeridoohan:
What I've implemented is a script that simply scans through the fingerprints in the module list and picks the model from a device that is old enough to not have the necessary hardware, but since it'll be from the same OEM any specific features like the Galaxy Store should still work (in theory). Much less work for me than trying to keep up with a list of known working models...

And of course the user can set a custom value as well.

I'm currently on a small roadtrip and working on this while mobile is a bit more time consuming. I got the scripts all sorted just a few minutes ago though, so unless I discover something catastrophic I should be able to push an update tonight (CET). I hope.
[Magisk] pndwal:
Sounds great!

Perhaps user will be able to alter the model your script defaults to within existing list of models by OEM for easy trialing?

Looking forward to trying new improved module, and thanks for your diligence. PW
[Magisk] ipdev:
Part 2.

Since I borrowed a stock fingerprint from LineageOS and figured out the corresponding security date.

Time to Compare.

Asus uses a slightly different print than that in the stock downloads.

Not sure where or when it is set (installation or boot?) but, it is different.

Since xda is as big as it is, I found official links to multiple version of the stock rom instead of just the newest offered by Asus.

Including the one that matched the fingerprint used by the Lineage build.

xdaThread - Link

By comparing them to the working print, I was able to adjust the fingerprints from the stock downloads to work.

I am now in favor of dumping prop values from a stock device. Unless the manufacture offers a proper stock fastboot version.

Back to the current (newest) available from Asus.

UL-ASUS_X01BD-WW-16.2017.2007.094-user.zip

Original fingerprint for Asus ZenFone Max Pro M2 from the downloaded zip prop files.

ro.build.fingerprint=Android/sdm660_64/sdm660_64:9/PKQ1/16.2017.2007.094-20200705:user/release-keys

Adjusted fingerprint for Asus ZenFone Max Pro M2.

ro.build.fingerprint=asus/WW_X01BD/ASUS_X01BD_1:9/PKQ1/16.2017.2007.094-20200705:user/release-keys

The adjusted fingerprint compatible with a MagiskHide Props Config printslist file.

Asus ZenFone Max Pro M2 (9):asus:ASUS_X01BD:=asus/WW_X01BD/ASUS_X01BD_1:9/PKQ1/16.2017.2007.094-20200705:user/release-keys__2020-07-05

The adjusted print passes SafetyNet on Nexus 7 (2013), Pixel 3a XL, Poco F1.

Android 10, AEX, abc, LineageOS

Cheers. :cowboy:

---------- Post added at 11:03 PM ---------- Previous post was at 10:31 PM ----------

Some fingerprints to add to the list.

LG V30 LG-LS998 (8.0)

LG-H930 is the V30 model on the fingerprint list.

Guessing LS998 is Sprint (US) from the fingerprint.

Samsung

- A3 (2016) SM-A310F (7.0)

- A3 (2017) SM-A320FL (8.0)

- Tab4 7.0 SM-T230NU (4.4.2)

- Tab4 8.0 SM-T330NU (5.1.1)

- Tab4 10.1 SM-T530NU (5.0.2)

* - Galaxy S10 [SM-G973F] (9) Did not work for me.

Asus ZenFone Max Pro M2 (9)

Cheers all. :cowboy:
[Magisk] Some_Random_Username:
[MENTION=4667597]Didgeridoohan[/MENTION] Just a fyi that since I posted fingerprints for 8-series, OP released new updates shortly after.

Updated fingerprints are as follow

OP8

IN2011 OnePlus/OnePlus8_IND/OnePlus8:10/QKQ1.191222.002/2007160015:user/release-keys__2020-07-01

IN2013 OnePlus/OnePlus8_EEA/OnePlus8:10/QKQ1.191222.002/2007160015:user/release-keys__2020-07-01

IN2015 OnePlus/OnePlus8/OnePlus8:10/QKQ1.191222.002/2007160015:user/release-keys__2020-07-01

OP8PRO

IN2021 OnePlus/OnePlus8Pro_IND/OnePlus8Pro:10/QKQ1.191222.002/2007160011:user/release-keys__2020-07-01

IN2023 OnePlus/OnePlus8Pro_EEA/OnePlus8Pro:10/QKQ1.191222.002/2007160011:user/release-keys__2020-07-01

IN2025 OnePlus/OnePlus8Pro/OnePlus8Pro:10/QKQ1.191222.002/2007160011:user/release-keys__2020-07-01

Additonally I got some fingerprints for OnePlus Nord (both EU and Indian variants) that I extracted from OxygenOS 10.5.2 zips https://otafsg1.h2os.com/patch/amaz..._OTA_003-004_patch_2007170000_28efe3fce61.zip and https://otafsg1.h2os.com/patch/amaz...n_14_OTA_003-004_patch_2007170032_b1aea92.zip but I can't get them to pass ctsprofile, could you check on your device as well?

EU variant (AC2003): OnePlus/Nord_EEA/Nord:10/QKQ1.200412.002/2007162338:user/release-keys__2020-07-01

Indian variant (AC2001): OnePlus/Nord_IND/Nord:10/QKQ1.200412.002/2007170006:user/release-keys__2020-07-01
[Magisk] Didgeridoohan:
Come on guys... I'm trying to finish an update here. :D

[MENTION=7550078]pndwal[/MENTION] keeps giving me ideas that need to be implemented and [MENTION=7280276]ipdev[/MENTION] and [MENTION=8234677]Some_Random_Username[/MENTION] keep throwing new prints at me...

[MENTION=7280276]ipdev[/MENTION] The S10 print did not pass for me either. [MENTION=8234677]Some_Random_Username[/MENTION] Both Nord prints passed for me.

Looks like everything is tested and working now. I'm hoping to get an update out later today.
[Magisk] Didgeridoohan:
Module update to v5.3.0, fingerprints list to v95

Since Google haven't rolled out hardware based key attestation universally yet, it seems like we can spoof a different model with a simple prop change to force the use of basic attestation (thank you [MENTION=6345368]Displax[/MENTION]). It's actually possibly to pick whatever value for the model props, but using a real model prop value (one that's not on Google's list) can have it's advantages (mainly to possibly keep device specific features working). This update adds an option to the module to help with this.

With the "Force BASIC attestation" option you can let the module pick a value automatically (from the extensive included list of fingerprints), you can pick a value manually (from the extensive included list of fingerprints) or you can use a custom value of your choosing. See the module docs for details.

There are also a large number of new and updated fingerprints with this release. Thank you [MENTION=6032361]xuxu1[/MENTION], [MENTION=8234677]Some_Random_Username[/MENTION], [MENTION=6345368]Displax[/MENTION], [MENTION=6231115]mohitanchalia[/MENTION], [MENTION=7083216]amrithaathmaram[/MENTION], [MENTION=4189162]mikko3024[/MENTION], [MENTION=4429095]DreamFlasher[/MENTION], [MENTION=5790692]timjosten[/MENTION], [MENTION=7280276]ipdev[/MENTION] and [MENTION=5064652]rafaelbrunner[/MENTION] for your submissions.

Note: This release was mainly created while mobile, and even though I've tested everything there's an increased possibility that I have screwed something up. Please let me know if you find anything not working as expected...

Changelog

v5.3.0

Added a new feature to force SafteyNet's bootloader check to use basic attestation rather than hardware. See the documentation for details.

Added fingerprints for Asus ZenFone Max Pro M2, Fxtec Pro 1, Huawei Honor 6X BLN-L22, Lenovo Tab 4 8 Plus, LG V30, OnePlus 7, 7 Pro, 7T, 7T Pro, 8 and 8 Pro (Chinese variants), OnePlus Nord, Redmi Note 9 Pro, Samsung Galaxy A3 2016 and 2027 and Galaxy Tab 4 7.0, 8.0 and 10.1 and Xiaomi Redmi K20 Pro India. Updated fingerprints for OnePlus 7 Pro NR and 7 Pro NR Spr, 8 (almost all variants) and 8 Pro (all variants), Redmi Note 8 Pro and Xiaomi Mi A1, Mi A3 and Redmi 8. List updated to v95.
[Magisk] cbendot:
wohoo. .new feature let's start and enjoy cherrs dev?
[Magisk] pndwal:
Nicely implemented! - especially option f, 'Pick from fingerprints list', which provides for dead easy setting / trialing alternative prop values where device specific features may not work with default forced prop value as expected.

Question: Some users reported having no 'ro.product.model' line in props, but were able to force BASIC attestation by adding it. Will the new "Force BASIC attestation" option add this line where missing?

In any case, this is the difinitive all-in-one systemless solution for custom props, and your new option has got to be the most elegant solution for forcing BASIC (non hardware backed) SafetyNet attestation to date! ;) Ta, PW
[Magisk] Didgeridoohan:
Yeah, I thought you'd like that one. The inspiration for that came from your suggestion...

Yes, that prop will be added. And any other model props that already exist will also be altered.

Thank you. Somehow I knew you'd say that... :p
[Magisk] mohitanchalia:
Thanks for the update. Works flawlessly.

However, there's a small typo with the ro.product.manufacturer prop for the Indian Xiaomi Redmi K20 Pro. It's misspelt as "Xiamoi."
[Magisk] Didgeridoohan:
Thank you for the heads-up. Fixed.
[Magisk] knojap:
SM-G900F Galaxy S5 with LOS 17.1!

Tried it on this device.

2. Force Basic key attestation

But doesn't work.

SafetyNet:

cts: false

basic: false

Is there more to do, than installing this module. su - props and 2.?

Thanks
[Magisk] Didgeridoohan:
Since you're failing both CTS and basic integrity you've got more issues than hardware or basic attestation. Take a look here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] knojap:
Tested Magisk Hide: It's working!

i have EDXPOSED. Will it never work with this?
[Magisk] Didgeridoohan:
EdXposed is outside the scope of this thread...

You can always test by disabling it (and you might have to clear Play Services cache after). If SafetyNet starts working after that you know that the issue is. From what I understand, the Canary releases of EdXposed sometimes have fixes to pass SafetyNet. I would check their Github if I were you.
[Magisk] knojap:
Deactivated Edexposed and cleared cache. Wow, it's working.

So now i will test the canary edxposed.

thanks so far...

---------- Post added at 11:58 AM ---------- Previous post was at 11:15 AM ----------

Ok tested the canary version. Doesn't work.

But now i can deactivate Edxposed and working with my banking app and after that reactivate edxposed.
[Magisk] pepote666:
add xiaomi mi 10 lite 5g

Xiaomi/monet_eea/monet:10/QKQ1.191222.002/V12.0.1.0.QJIEUXM:user/release-keys

ro.vendor.build.security_patch]: [2020-06-01]

ro.product.manufacturer]: [Xiaomi]

ro.product.model]: [M2002J9G]
[Magisk] pndwal:
Just wondering why Force BASIC Attestation is changing all the following:

ro.product.model

ro.product.system.model

ro.product.vendor.model

ro.product.odm.model

The documentation seems to mention only the first prop, and it seems that this is the one Google is checking at present.

Could changing more than necessary cause any problems, or be an advantage in fact?

Just curious. :cyclops: PW
[Magisk] Didgeridoohan:
That the module changes all those props (only if available though) is what was meant when I in the docs used the text "ro.product.model prop

s

" (plural). As usual when you're writing documentations it is very easy to know exactly what you mean yourself, but for some reason whomever is going to read it can't read your mind... So annoying. :laugh:

I've added a small clarification.

My reasoning is that if the partition props are available it is better to make them match the main prop. And originally [MENTION=6345368]Displax[/MENTION] only had to change the odm prop to get basic attestation.
[Magisk] zgfg:
It depends on vendor.

For Xiaomi only ro.product.model is relevant to force Basic attestation (if that one is left intact and the other four are changed, CTS Profile will still use Hardware and fail to pass) - and changing only that single one is safe for OTA and System apps updater.

Actually, ro.product.product.model is not even originally defined on Xiaomi

Who doesn't like all to be changed can edit in /data/adb/modules/MagiskHidePropsConf/system.prop

Btw for the predefined values list, e.g. on Huawei Mate 9 (Android 8, 9) is MHA-L29
[Magisk] Didgeridoohan:
Exactly. Which is another reason to change them all. I'm not gonna try to keep track of what every single vendor uses, for what ultimately is going to be a temporary solution.

Or just use the custom props feature of the module to change whatever prop you want with full control.

If that's meant for inclusion in the list, that's not how it works. I'm picking the model values from the fingerprints list, so if you want me to include the Mate 9 (not currently in the list) you could follow my submission instructions. :good:
[Magisk] pndwal:
Thanks - I had wondered about the initial plural reference, but hadn't got it...

Reasoning makes sense, and solution leaves scope for user intervention when desired as noted in any case. Thanks for clarification. :good: PW
[Magisk] Didgeridoohan:
I do enjoy a goofy sci-fi reference now and then... :silly:
[Magisk] orifori:
Updated to latest Magisk 16.7 on my Samsung Galaxy S9+ but Magisk Hide still not working (cannot use Samsung Health, Secure Folder, etc. - despite SafetyNet check success). I thought that S9+ was now officially supported from Magisk 16.6 on...
[Magisk] Didgeridoohan:
You're a bit lost. That's got nothing to do with this module...

But if you can pass SafetyNet, that means MagiskHide

is

working on your device. The apps you mention rely on your Knox status, I believe. And that it's not something Magisk (or any other method as far as I know) can do anything about.
[Magisk] teddy0209:
[MENTION=4667597]Didgeridoohan[/MENTION]

Props for Mi5 8.0 if you haven't added it,

Xiaomi/gemini/gemini:8.0.0/OPR1.170623.032/V9.6.1.0.OAAMIFD:user/release-keys
[Magisk] Didgeridoohan:
Update to v2.3.3-v22

A quick update. Nothing major for the module (just some things I'd forgotten about), but I was provided a whole bunch of new Sony Xperia fingerprints, so I thought I'd kill two birds with one stone...

The fingerprints list is becoming quite large (100+ prints), so I might have to think about rewriting the list retrieval in the script. It's getting to be a bit slow... :D

Changelog

v2.3.3

Tiny update for installation logic and documentation.

Also added and updated a whole bunch of fingerprints (Huawei Honor 6X, Sony Xperia X Dual, X Compact, X Performance Dual, XZ Dual, XZ Premium, XZ Premium Dual, XZ1, XZ2, XZ2 Dual, XZ2 Compact, XZ2 Compact Dual and Xiaomi Mi5/5 Pro), list v22. Thank you to [MENTION=6906968]rikeury097[/MENTION], [MENTION=3615867]teddy0209[/MENTION] and a huge shoutout to alviteri @ GitHub for all the Sony prints.
[Magisk] orifori:
OK, but in such case - what can MagiskHide be used for on Samsung devices (having in mind that they all have tripped KNOX)?! I think the idea of MagiskHide is exactly to hide KNOX status from different apps like Samsung Health, etc.

And also on my old Galaxy S7 MagiskHide is perfectly doing this job - I can use absolutely all apps, incl. Samsung Pay, Secure Folder, etc. So why would MagiskHide work on S7 but won't work on S9 - especially since S9 is already officially supported...
[Magisk] Didgeridoohan:
MagiskHide hides many things, but not a tripped Knox counter. There was a feature introduced for faking Knox to 0x0 in Magisk v12.0, but it turned out to not being able to hide it from most apps. Knox is just too good...

I have no idea why things would be working on your S7, but not the S9. I don't do Samsung... If I were you I'd head over to the Samsung forums and see if anyone there have figured it out.
[Magisk] Notonlyeyes:
Thanks for all your work...

Here is my key fingerprint forum SafetyNet is ok...

Huawei P8 Lite 2017

FW Oreo PRA-LX1 8.0.0.366(C432)

fingerprint=HUAWEI/PRA-LX1/HWPRA-H:8.0.0/HUAWEIPRA-LX1/366(C432):user/release-keys
[Magisk] tres_linguas:
[MENTION=4667597]Didgeridoohan[/MENTION] thanks for your work

I have a banking app that does not work even though I have magisk hide on (and tested) and your module activated. I also tried deactivating systemless hosts support, but still no change.

I am using redmi note 4 and lineageos 15.1.

Any tipps how it could be possible to fool this app to make it work? My other two banking apps do work

Thanks for any help

EDIT solved by renaming magisk package - seems like the app detected the presence of magisk, but now not any more :cool:
[Magisk] Didgeridoohan:
You're a bit off topic... But:

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

Apart from that you can also try uninstalling the Magisk Manager. Some apps have started looking at the app names to detect Magisk. There will be a function to circumvent that detection in a future Manager update...

Edit: Never mind... I had missed your edit...
[Magisk] Athing13:
Hi please help me im make smartphone andromax e2 plus b16c2g,im make rom miui 7 and my trouble in magisk safetynet I have followed the tutorial but still not work, I try to pass terminal emulator and when select fingerprint turns out there disable, is there any other way to ctc profile to true
[Magisk] Didgeridoohan:
Come on... I've asked for logs several times, and you've yet to provide a single one. If you use the Collect Logs option in this module you'll collect a whole bunch of the useful logs. Provide the packaged file here and we can see about figuring things out.

The fingerprint option is disabled because you've got some other module installed that edits the build fingerprint. Since you where posting in the USNF thread, I'm going to guess that's the one. You'll find out of you select the fingerprint option in this module.

You mentioned that you have both ctsProfile and basicIntegrity false, so there's not much that this module can do about that. But, if you provide those logs, I might be able to help with what's wrong.

You can also take a look here to try you figure things out yourself:

https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] Athing13:
Magisk* : * Creating /sbin overlay

01-02 04:42:47.799***224***224*I Magisk* : * Mounting mirrors

01-02 04:42:47.799***224***224*I Magisk* : mount: /sbin/.core/mirror/system

01-02 04:42:47.799***224***224*I Magisk* : link: /sbin/.core/mirror/vendor

01-02 04:42:47.809***224***224*I Magisk* : bind_mount: /sbin/.core/mirror/bin

01-02 04:42:47.809***224***224*I Magisk* : * Setting up internal busybox

01-02 04:42:47.839***224***224*I Magisk* : Magisk v16.0(1600) daemon started

01-02 04:42:47.839***224***230*I Magisk* : ** post-fs mode running

01-02 03:42:47.939***224***232*I Magisk* : ** post-fs-data mode running

01-02 03:42:47.939***224***232*I Magisk* : * Mounting /data/adb/magisk.img

01-02 03:42:48.059***224***232*I Magisk* : * Running post-fs-data.d scripts

01-02 03:42:48.059***224***232*I Magisk* : post-fs-data.d: exec [propsconf_post]

01-02 03:42:48.659***224***232*I Magisk* : * Running module post-fs-data scripts

01-02 03:42:48.659***224***232*I Magisk* : MagiskHidePropsConf: exec [post-fs-data.sh]

01-02 03:42:48.699***224***232*I Magisk* : xiaomi-safetynet-fix: exec [post-fs-data.sh]

01-02 03:42:48.749***435***435*I Magisk* : *** [Universal Hide] Version: v2 Beta 5*

01-02 03:42:48.789***439***439*I Magisk* : *** [Universal Hide] Changing build fingerprint value*

01-02 03:42:48.829***442***442*I Magisk* : *** [Universal Hide] Hiding dangerous props*

01-02 03:42:48.969***224***232*I Magisk* : * Loading modules
[Magisk] Didgeridoohan:
[MENTION=9298283]Athing13[/MENTION]

Don't paste logs directly into your post. It makes the thread hard to read. You've got 10 posts now, so you should be able to use the attachment function. If not, use a cloud service, or similar, and provide the link.

That's not the entire Magisk log. The second half (which contains the important stuff) is missing...

Read through the link I gave you in my last post, and make sure you've at least got the basics covered for MagiskHide to work.
[Magisk] yassouna51:
please help i have an issue in terminal after typing su and props commands i get "The original prop values are not loaded, possibly due to a full reqet of the module, or something has gone wrong. Please reboot your device to reqet. If the issue persits after a reboot, please report the issue, with logs!" So yeah the issue persisted after several reboots and here i am reporting this issue but without the propslog.tar.gz because its always empty and i can't upload it please help me