yashsingh1/xdaforums huggingface dataset:
[Magisk] rdis:
Poco M3 Pro 5G

M2103K19PG

MIUI Global

Regional Indonesia

Security Update June 1, 2021

POCO/camellian_p_id/camellian:11/RP1A.200720.011/V12.0.3.0.RKSIDXM:user/release-keys
[Magisk] Didgeridoohan:
Oh man...

The backlog for submitted fingerprints is just growing and growing. Thank you so much guys for still providing all these prints!

I've had ridiculous amounts of work in the past few weeks and my testing device has decided to give out on me. I don't test prints on my daily driver, so currently I'm a bit stumped. Hopefully I'll have time to give my old devices some TLC over the next few days and I can get back to business as usual.
[Magisk] 73sydney:
I have a theory that when you close your eyes at night you still see 2 words:

release keys :)
[Magisk] Ariold:
I know I should've searched before posting but there are so many pages I couldn't do it. Sorry.

Just to make sure, to use a custom fingerprint I have to create a file named printslist (without extensions) on the root of internal storage. Then on that file I simply write the device name + fingerprint?

MotorolaOneAction=motorola/troika_m1/troika:10/QSBS30.121-12-12-7/702ad:user/release-keys

Would this be correct for example?
[Magisk] yazakachka:
Oneplus 6, Android 11 (taken from beta):

OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2106301530:user/release-keys
[Magisk] iamatx:
does it work on avd?
[Magisk] ipdev:
Looks to be an Android 10 build so you will need to add the matching security date to the end.

__YYYY-MM-DD

MotorolaOneAction=motorola/troika_m1/troika:10/QSBS30.121-12-12-7/702ad:user/release-keys__YYYY-MM-DD

The part before the = is what is displayed on the screen when you run the props command and select custom prints list.

You can space it out if you want.

Example using the Nexus 6 and 6P.

The last build for 6 was not new enough to require the matching security date.

The last build for 6P was so it requires the matching security date.

Google Nexus 6 (7.1.1):Motorola:Nexus 6=google/shamu/shamu:7.1.1/N8I11B/4171878:user/release-keys
Google Nexus 6P (8.1.0):Huawei:Nexus 6P=google/angler/angler:8.1.0/OPM7.181205.001/5080180:user/release-keys__2018-12-05

The above example is a little different than the basic MHPC printslist, it includes manufacture and model.

Motorola made the Nexus 6 and Huawei made the Nexus 6P

Small tweek to your printslist..

Motorola one action (10):Motorola:motorola one action=motorola/troika_m1/troika:10/QSBS30.121-12-12-7/702ad:user/release-keys__YYYY-MM-DD

The part before the first : is what is displayed on the screen when you run the props command and select custom prints list.

Note: The Android version is added to the end of the MHPC display name in parentheses (10).

If you put all the above into a printslist file and run props the custom list would show..

MotorolaOneAction
Google Nexus 6 (7.1.1)
Google Nexus 6P (8.1.0)
Motorola one action (10)

Note:

The MHPC display name is cosmetic.

The part before the equal = using the older (basic) printslist layout.

The part before the first colon : using the current printslist layout.

The manufacture, model, build fingerprint and (if required) the matching security date, all need to be correct matching values.

You can find all this and more in the documentation.

MHPC Documentation - GitHub - Link

- Custom fingerprints list - GitHub - Link​

To quote Didgeridoohan.

Cheers. :cowboy:

PS.

I did not see troika_m1 on Google's certified list.

Only troika and troika_sprout.

Retail Branding	Marketing Name	Device	Model
Motorola	motorola one action	troika	motorola one action
Motorola	motorola one action	troika_sprout	motorola one action

Both models are also motorola one action.
[Magisk] ipdev:
OnePlus's Open Beta is normally certified but, also need the matching security patch date. ;)

MHPC Documentation - Matching the Android security patch date - GitHub - Link

Cheers. :cowboy:
[Magisk] ipdev:
I never tried running modules or Magisk on a virtual device.

When I get time, I will give it a try and see what happens. 🙃

Cheers. :cowboy:

PS.

Welcom to xda. :D
[Magisk] yazakachka:
Is it the same as post-security-patch-level?

post-build=OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2106301530:user/release-keys
post-build-incremental=2106301530
post-sdk-level=30
post-security-patch-level=2021-07-01
post-timestamp=1625038551
pre-device=OnePlus6
reserve-image-size=943841280
version_name=OnePlus6Oxygen_22_2106301542
wipe=0
[Magisk] iamatx:
@ipdev

i did it but didn't work :(

thankyou
[Magisk] Didgeridoohan:
What didn't work? Passing SafetyNet?

On an emulator it's not enough to change the device fingerprint, you would also have to hide the fact that it is an emulator since that's also a trigger factor for SN (I've no idea of that's even possible).
[Magisk] iamatx:
am trying to change fingerprint and model name etc
[Magisk] Didgeridoohan:
If there's something that doesn't work as expected it's good to provide as much detail as possible. The module logs can help with that:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#logs
[Magisk] Some_Random_Username:
Android 11 fingerprint for OP6T: OnePlus/OnePlus6T/OnePlus6T:11/RKQ1.201217.002/2106301531:user/release-keys__2021-07-01

Android 11 fingerprint for OPPO Find X2 Neo Europe CPH2009: OPPO/CPH2009EEA/OP4C2DL1:11/RKQ1.200903.002/1622715759798:user/release-keys__2021-06-05
[Magisk] ipdev:
Yes.

The post- values are what will be installed.

Cheers. :cowboy:

PS.

I just checked, and it passed on my Poco F1 running Lineage 18.

OnePlus 6 Beta (11):OnePlus:ONEPLUS A6003=OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2106301530:user/release-keys__2021-07-01
[Magisk] Ariold:
Oh, ok. I read about possibly having to find a matching security date, and I've tried like, twice before giving up.

But in that case I'll try a bit more to find it.

Actually, I had asked for a stock fingerprint on the Moto forum. It didn't work however, so I'm still a bit stuck hahaha.

I'll try to figure this out, but thanks a lot for your help!
[Magisk] AddYX11:
Can someone please guide me how to use this module to Spoof my device as a Pixel 1 (Sailfish). I tried using other pixel props modules they break my Poco F1's IR Face Unlock. Please any kind of guidance or links to such a guide would be appreciated.

ROM - EvolutionX 5.8 (Unofficial)
[Magisk] 73sydney:
First post? Its always good manners to read the first post before posting asking for help.

It has a link to the documentation: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md

Perhaps specifically:

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

short video:
[Magisk] AddYX11:
I found this module instead!

I found this module instead!

Thanks for your help tho, really appreciate it.
[Magisk] Techguy777:
Yeah great example you take an old device that is probably the device you selected and you show us nothing really. If this works why is it my device if I use pixel device on my Samsung doesn't allow me to install pixel or Google things like google recorder? I don't understand what this app really does or covers up. To me it seems like they always know I'm a Samsung S10 lite or whatever device I'm using my Google login does send me an email saying pixel device logged in. Could someone on a new device at least android 10 or 11 say what this module does and I'm not taking about a lollipop device on android 11 custom rom I'm talking a new device that you bought with android 10 or 11 because things change and I truly don't think you can hide what your device is. If you can't touch system files than you can't change build prop it's like spoofing it but they can still check real build prop
[Magisk] Didgeridoohan:
Only root apps have access to the real build.prop files, that's not how regular apps "detect" your changes...

The issue is most likely that prop changing is a very rudimentary way of simulating another device and in many cases nowhere near enough. That's probably why @AddYX11 had success with another module that changes xml files rather than props (the post right before yours).
[Magisk] 73sydney:
I answered exactly the posters question....

They asked how to use it, check my response, includes links and even a video showing you how to use it...question answered

Not sure why youre commenting other than to troll me.

Please dont
[Magisk] Techguy777:
Yes your right are you the developer? What is the point of the module is the real question? Even if your not the developer what does this module do for you? Change props I know what does that allow you to do that you wouldn't be able to? Anyone feel free to chime in. Is it just like look my about information says pixel but it doesn't allow the play store to download pixel only specific apps so what is the point
[Magisk] Didgeridoohan:
The point of the module is to make it relatively easy to change prop values using Magisk (systemlessly). That's it, nothing else...

There are many uses for this, one of which might be making your device appear as another one. But, as already stated this is great from certain to work and not at all the main function.
[Magisk] Techguy777:
That's serves no purpose if it doesn't unlock the features of that device like apps. Otherwise it doesn't matter. I said that in my comment other than just changing the name or whatever what does it do? You said it changes the name which does nothing because the phone has a 100 ways of knowing exactly what your phone really is. Like the build prop in system that you used to be able to really change and I'm sure for older phones this module can do that for real but anything above android 8 or 9 it's got not real use.
[Magisk] Techguy777:
I hate to ruin everyone's fun but the problem is new users don't understand what this does and they run around saying they can hide their device has another device when really they can't. They believe the developer over everyone and none of the veteran users have the balls to say no it doesn't. It's not anyone's fault unfortunately you basically can't write to the system anymore which makes root access handicapped and that's why they did it. Companies don't want to allow people to install oneui apps on devices that aren't one ui. Same with pixel devices google doesn't want their voice recorder on devices that aren't google. If you could change anything in the system than you could with enough knowledge make a device appear to be one ui. Only it would be so old now it still couldn't install the app lol.
[Magisk] Techguy777:
Here's an idea for magisk module, let's see if someone could make a module that keeps changing the data file that marks down your build number or Id number to allow 2 weeks trials and then every 2 weeks you flash it and it's changes the id the apps stored to give you another 2 week trial. This is not pirating because you do nothing to the APK itself You're only changing the data file totally not pirating.
[Magisk] Didgeridoohan:
I'm the developer of this module, and I'm saying that changing prop values sometimes works to make your device appear as another and sometimes it doesn't. It all depends on what you're actually trying to do and how the app you're trying to fool actually checks your device. Knowing Samsung they probably make it plenty difficult.

For your sake I'll take a look at the docs later and add some disclaimers...
[Magisk] ipdev:
This one I will answer separately.

It is piracy.

When you agree to the User Agreement (UA) to the Terms of Service (ToS), you commit to use it for fourteen (14) days at no charge.

As soon as you use it on the fifteenth (15th) day (without paying), you are stealing it.

The dividing line between working around legalities and breaking them is not always clear.

In this case, using it up to twenty eight (28) or more days for free is definitely breaking the UA/ToS.

Cheers.
[Magisk] ipdev:
I checked the Lineage repo for troika.

LineageOS - [GitHub] - android_device_motorola_troika - Link

Looks like they are using sprout. lineage_troika.mk - Line # 37

BUILD_FINGERPRINT := motorola/troika_retail/troika_sprout:10/QSBS30.62-29-7/0ea60:user/release-keys

Cleanup back in May, they did not replace/update the print used.

LineageOS does not over-ride the security date(s).

Would be nice if they did but, it is against their charter​

The one I found and tested the other day did not pass SafetyNet.

Motorola motorola one action (10):motorola:motorola one action=motorola/troika_retail/troika_sprout:10/QSB30.62-17/10ff7:user/release-keys__2019-12-01

If we can find the matching security date for the print Lineage uses.

or a different custom rom that includes the matching security date to the stock print they use.

Outside of that, if you can revert to (or have access to another device running) the stock (Motorala system) then use the getprop command to dump the props from a running system.

I will keep an eye out for troika, if I can find something that works, I will let you know. ;)

Cheers. :cowboy:
[Magisk] Xanth0k1d:
Hey guys, just a heads up, I was updating my Xperia 10 to Lineage 18.1 and I tried to device stimulation and got in a bootloop

It's probably because I tried to stimulate some props in option 4 - 8 i.e. the build.version.sdk I guess it has to do with the original fringerprint being for android 10. (spoofing some of those 4 options might cause bootloop)

Not sure if uninstalling Magisk would recover from the bootloop (My /data was encrypted so I can't run the uninstall zip, had to restore a back up of my boot image without Magisk - this did help with solving the bootloop, but when I reinstalled magisk the bootloop came back)

@Didgeridoohan is there a way to reset all the stimulations and prop changes in a recovery environment(like twrp)?

another question for anyone out there who might know: if a device stops receiving update (stuck at android 10), a custom rom is installed( say android 11), how much impact would be there if the option 4-8 are not being stimulated? (chances of an apk comparing the android version and the build sdk version etc?) I mean, I passed the safetynet test without those 4 props changes
[Magisk] Didgeridoohan:
@Xanth0k1d

Resetting a module from TWRP is quite easy, and there are also module specific options available. It's all covered in the docs:

https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module
[Magisk] flyl0:
It was working fine for me a little while ago just by editing the fingerprint of my Xperia 5II with the one of the Xiaomi 8t, But it doesn't work at all anymore, and I have no idea why..
[Magisk] Didgeridoohan:
Hard to know what you mean when you say it "doesn't work", without actually saying what it is that doesn't work...

But usually it's SafetyNet, so start by taking a look in the docs:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] rodken:
Provide me wiith an example on how to utilize 'reset_mhpc or disable_mhpc' function?
[Magisk] flyl0:
It means that i can't pass the safetynet test anymore, sorry I thought it was obvious
[Magisk] tepsys:
OnePlus 9 Pro fingerprint

getprop ro.build.fingerprint

OnePlus/OnePlus9Pro/OnePlus9Pro:11/RKQ1.201105.002/2105290043:user/release-keys

getprop ro.product.manufacturer

OnePlus

getprop ro.product.model

LE2125

Build Number:

Oxygen OS 11.2.7.7.LE15AA

Android Security update:

2021-05-01

If anything other device info is useful, let me know
[Magisk] DjLeleX:
Update S10 series (International, Korea and Europe) to July security patch (sorry for my inactivity in the past months):

Samsung Galaxy S10e - SM-G970F

samsung/beyond0ltexx/beyond0:11/RP1A.200720.012/G970FXXSBFUF3:user/release-keys_2021_07_01

Samsung Galaxy S10e - SM-G970N

samsung/beyond0lteks/beyond0:11/RP1A.200720.012/G970NKSU6FUF5:user/release-keys_2021_07_01

Samsung Galaxy S10e - SM-G970F (Europe)

samsung/beyond0lteeea/beyond0:11/RP1A.200720.012/G970FXXSBFUF3:user/release-keys_2021_07_01

Samsung Galaxy S10 - SM-G973F

samsung/beyond1ltexx/beyond1:11/RP1A.200720.012/G973FXXSBFUF3:user/release-keys_2021_07_01

Samsung Galaxy S10 - SM-G973N

samsung/beyond1lteks/beyond1:11/RP1A.200720.012/G973NKSU6FUF5:user/release-keys_2021_07_01

Samsung Galaxy S10 - SM-G973F (Europe)

samsung/beyond1lteeea/beyond1:11/RP1A.200720.012/G973FXXSBFUF3:user/release-keys_2021_07_01

Samsung Galaxy S10 Plus - SM-G975F

samsung/beyond2ltexx/beyond2:11/RP1A.200720.012/G975FXXSBFUF3:user/release-keys_2021_07_01

Samsung Galaxy S10 Plus - SM-G975N

samsung/beyond2lteks/beyond2:11/RP1A.200720.012/G975NKSU6FUF5:user/release-keys_2021_07_01

Samsung Galaxy S10 Plus - SM-G975F (Europe)

samsung/beyond2lteeea/beyond2:11/RP1A.200720.012/G975FXXSBFUF3:user/release-keys_2021_07_01

Samsung Galaxy S10 5G - SM-G977B

samsung/beyondxxx/beyondx:11/RP1A.200720.012/G977BXXS8FUF3:user/release-keys_2021_07_01

Samsung Galaxy S10 5G - SM-G977N

samsung/beyondxks/beyondx:11/RP1A.200720.012/G977NKSU5FUF5:user/release-keys_2021_07_01
[Magisk] Andrew456:
Hello, should I disable or uninstall MagiskHide Props module before OTA update and installing Magisk to inactive slot?
[Magisk] Ryano89:
No need
[Magisk] ipdev:
The file is a trigger to reset or disable the module.

Just create an empty file and name it one or the other.

From command line (linux/mac).

You can create an almost empty file using the echo command.

echo>reset_mhpc will create a file that only has a newline(carriage return).

Use a an editor like nano to create an empty file.

nano disable_mhpc save and exit nano.

Example

echo>reset_mhpc
adb push reset_mhpc /sdcard/
adb reboot

This will reset the MHPC module on boot.

echo>disable_mhpc
adb push disable_mhpc /sdcard/
adb reboot

This will disable the MHPC module on boot.

Example 2.

nano zero_byte_file
adb push zero_byte_file /sdcard/reset_mhpc
adb reboot

This will reset the MHPC module on boot.

nano zero_byte_file
adb push zero_byte_file /sdcard/disable_mhpc
adb reboot

This will disable the MHPC module on boot.

Note:

I used the root of internal storage /sdcard/ in the example.

You can place the file in a few locations as described in the link in the post you quoted.

MHPC Documentation - GitHub - Link

Device issues because of the module - Link​

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
[Magisk] tepsys:
Oneplus 9 Pro fingerprint for 11.2.8.8.LE15AA

getprop ro.build.fingerprint

OnePlus/OnePlus9Pro/OnePlus9Pro:11/RKQ1.201105.002/2107082110:user/release-keys

getprop ro.product.manufacturer

OnePlus

getprop ro.product.model

LE2125

Build Number:

Oxygen OS 11.2.8.8.LE15AA

Android Security update:

2021-07-01
[Magisk] ipdev:
OnePlus 6T. (Pending)

OOS 10.3.12

OnePlus6T [A6013] (10):OnePlus:ONEPLUS A6013=OnePlus/OnePlus6T/OnePlus6T:10/QKQ1.190716.003/2107132231:user/release-keys__2021-07-01

Cheers all. :cowboy:
[Magisk] Zylynzer:
Time for some Redmi's to be updated:

Redmi Note 9S

Global

:

Redmi/curtana_global/curtana:11/RKQ1.200826.002/V12.0.2.0.RJWMIXM:user/release-keys

2021-04-01
[Magisk] Ariold:
Oh crap! So sorry for not replying earlier!

I'm using a random fingerprint from a Pixel and thankfully it's been working fine, and so I've ended up forgetting about it.

I'll be honest, I don't really know how any of this works, but maybe I can help others who might be having the same problem.

I just need to change the date at the end of the fingerprint right?

So if I check each individual date I'm bound to find one that works correct?

I actually asked for a stock fingerprint on the forum but for some reason it also did not pass SafetyNet. I'd imagine it has to do with security date too?

This was the one I got:

motorola/troika_m1/troika:10/QSBS30.121-12-12-7/702ad:user/release-keys
[Magisk] DjoniBro:
the emulator does not have my phone samsung galaxy a10 SM-A105F what should i do? Bro help plz!!!View attachment 5372673
[Magisk] ReservedName:
Pixel 4a on android 11 here

rq1a.201205.008 I'm not sure how I got this to work originally but I had to remove all the magisk modules after flashing a wrong one. Now that I'm spoofing the fingerprint the option for my device is rq3a instead. I'm guessing that's why the basic attestation is failing. How do I fix this? Should I try device simulation or get the older fingerprint? How can I find the older fingerprint btw..

edit: nevermind I don't know how but I disabled device simulation, installed systemless hosts (probably unrelated), enabled "hide magisk from various forms of detection" and then checked again and passed safetynet

I couldn't get g pay to open at first but it seems that is ok now too.

good to go i guess
[Magisk] Didgeridoohan:
If you need a fingerprint for a specific module you usually need to find that yourself and submit it here so that I can test it and add it to the module.

If you look back in the thread there are a whole bunch of wonderful people whom have doing just that. Unfortunately the backlog for me to test prints is pretty big at the moment, since I have no device you test prints on and I'm also running on summer time (meaning everything takes twice the time it usually takes and at least 20 hours a day are spent sleeping or doing nothing at all; and the remaining 4 hours are spent playing with my kid or eating good food).

If you can get me that print it'll be added once I get my test setup back up and running (probably within a week or so, but no ETA currently). For some tips on how to find a print (and don't forget the security patch date) take a look in the docs:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] ipdev:
I was looking for a used tablet for my Brother.

Between 100 and 300 USD

Decided on a Samsung Tab S5e since it had official TWRP and LineageOS builds.

Long story short, my find/purchase was not as good as I thought.

I did not realize that the Tab S4 and Tab S5e share the same gts4lv name.

- Sometimes I think Samsung is more complicated then Xiaomi. ;)

At least I got another device to add to the fingerprint list. :D

---

Samsung Galaxy Tab S4 [SM-T837A] Android 10

LTE (AT&T) version.​

Samsung Galaxy Tab S4 [SM-T837A] (10):samsung:SM-T837A=samsung/gts4llteuc/gts4llteatt:10/QP1A.190711.020/T837AUCU5CUF1:user/release-keys__2021-03-01

Cheers all. :cowboy:
[Magisk] xuxu1:
I just saw that you don't have a single fingerprint for the Redmi Note 8 Pro, here is one.

Redmi Note 8 Pro (begonia) EEA (Europe Version) Android 11 security date: 2021-07-01

Redmi/begonia_eea/begonia:11/RP1A.200720.011/V12.5.2.0.RGGEUXM:user/release-keys

Keep up your good work
[Magisk] CHT45:
Back with Global POCO X3 NFC.

Fingerprint: POCO/surya_global/surya:11/RKQ1.200826.002/V12.5.1.0RJGMIXM:user/release-keys

Security patch: 2021-07-01

Before I forget, thanks for all the work you'll do and have done. :)
[Magisk] akshay.ku:
Hi,

For Samsung S10 lite Indian version I tried with S10E and S10 plus still the CTS is getting failed

Model:G770F

Any way to fix the fingerprint issues, I tried to get the fingerprint manually, i am not able to get that way as i don't understand to work with scripts (Sorry on that)

please help in the fingerprint issues with this Variant.
[Magisk] akshay.ku:
Hey,

I got the fingerprint keys (latest firmware as of today)

Samsung S10 lite android 11, G770F :samsung/r5qnsxx/r5q:11/RP1A.200720.012/G770FXXS4EUF6:user/release-keys
[Magisk] Didgeridoohan:
Thank you. I've just finished testing a little over 100 prints that was submitted over the summer, and I'll give this one a shot as well before I start getting the new list out there.

I do need the security patch date as well though, and since it's recent firmware I'll assume it's August or July 1st. Is that correct (it's a bit of a hassle to guess)?

Regarding your issues with CTS, you also have to consider hardware backed key attestation. For that you'll need the new Universal SafetyNet Fix. See here:

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