yashsingh1/xdaforums huggingface dataset:
[Magisk] ipdev:
There have been a lot of fingerprints given in the last few (11/12) months.

Start at Post # 5,920

Since this module only includes the latest level print, you do not need all the Pixel 12 prints, only the last 12 and last 12L prints along with the current 13 print.

Fingerprints get submitted on GitHub also.

PullRequests

Note:

Didgeridoohan tested each fingerprint on two different devices to make sure they were correct.

If the fingerprint passed on both devices, he added it to the list.

The reason for the delay between submitting a fingerprint and it being added to the list.

Cheers. :cowboy:
[Magisk] ipdev:
MHPC Documentation - GitHub

- Finding a certified fingerprint - Link

Seems that needs to edited a bit, it will also pull the necessary information from a current running device.

mHide Get Props - [GitHub] - Link

Wiki - mHideGP - Example Android - Link

Basically copy mHideGP.sh and certified.list to the device.

Normally into the Download directory.

Then run the mHideGP script from command line using sh or from a file manager that can run script files.

From shell or terminal app.

sh /sdcard/mHideGP.sh​

Cheers. :cowboy:
[Magisk] vithuselservices:
Ah yes. Its already on my list to process. Ill be working through the PR's first then looking at the posts on here :)t

In the immediate moment. I can only test on one device. Ill see if i've got any old phones lying around if not ill pick up a pixel 5 as a secondary testing device.
[Magisk] mvincent2k:
OK I am not understanding this, so let me present the exact scenario. I feel like there is no SINGLE clear instructions for what I am asking and being pointed to multiple places. I will compile a final instructions once I understand as it seems this will benefit the community and be used for exporting and sending to the new Fork dev for updates.

1.) When I ran the getprop.... commmand, it stored the fingerprint correct? And I received this: OnePlus/NE2215/OP516FL1:12/SKQ1.211019.002/S.202209131402:user/release-keys which shows as current and passes all safetynet checks.

2.) I now want to take that fingerprint and restore it on a completely different device. Is that string (above) just the fingerprint text all I need? ......or is there some information stored in a prop file or backup somewhere that I need to copy over for the restore to work?

3.) If I need to then export or modify a file so I can restore, where is it and what is needed to be done?

i.e.- do I need to edit the OnePlus.sh under /MagiskHidePropsConf/printfiles and add the fingerprint text above there? If so what is the syntax as there are additional arguments from what I can see.

Sorry for all the questions but just want to get this right.

thnx
[Magisk] vithuselservices:
Hi!

The fingerprint value alone wont be enough. Safetynet will want the security patch date as well as model and a few other entries to validate. There's a few things that need to match up for safetynet to pass. Newer builds also need basic key attestation enabled as the device encryption might not match that of the original rom (if your on a custom rom).

to answer question 3. The best method would be to submit the fingerprint officially via this link. It requests all the relevant data and once its verified i can add it into future releases.

Sorry i can't go into more detail at the moment. I'm at work and typed this out in-between meetings.
[Magisk] ipdev:
There are a few ways to to the same thing. 🙂

---

The getprop command will display the current property of the device.

It will not store anything unless you point the output into a file as zgfg noted.

getprop ro.build.fingerprint > NameOfFile

> will create a new file, >> will append a file.​

Example:

getprop ro.build.fingerprint > /sdcard/Download/NE2215_props.txt
getprop ro.vendor.build.security_patch >> /sdcard/Download/NE2215_props.txt

This will write the output to a file named NE2215_props.txt in your Download directory that now contains the fingerprint and security patch date.

---

mHide Get Props started out as a small script that I used to pull and share device properties.

Didgeridoohan nudged me into sharing it.

Kept me motivated (for a few months) and helped me a bit when I got stuck, while I updated the script(s) for sharing..

I automated some more of what I was still manually doing. So the small script got a lot bigger, turned into a project and spawned a few helper scripts. 🙃

When run on a device, the mHideGP script (if no prop file is found) will dump the properties of the device into a prop file.

Then it will use that prop file to generate a file that is formatted to work as a custom printslist file.

When done it will display what files have been created.

Example using Asus ZenFone Max M1 (ZB556KL):

If an additional prop file is found or used, it will be renamed.
getprop.props file has been renamed as asus_asus_x00pd_1585733555-getprop.props
Keep it or delete it as you wish..

Done.

New mHideGP prop file saved as /storage/emulated/0/Download/mhp_asus_asus_x00pd_1585733555.sh

The mHideGP prop file is formatted to be used as a custom printslist and also contains all the signification prop values you might need. ;)

The getprop.props file is a full dump of the device properties using the getprop command.

Formatted to be the same as a traditional build.prop file.

---

MHPC Documentation - GitHub

- Please add support for device X - Link

- Finding a certified fingerprint - Link

- Matching the Android security patch date - Link

- How do I submit a fingerprint? - Link

- Custom fingerprints list - Link

---

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
[Magisk] zmovie:
Fingerprint submission:

ro.product.manufacturer

OnePlus

ro.product.model

IV2201

ro.build.version.security_patch

2022-09-05

ro.build.fingerprint

OnePlus/IV2201EEA/OP555BL1:12/SP1A.210812.016/R.GDPR.202209011617:user/release-keys
[Magisk] 73sydney:
Explain how he has "ghosted us"

He's active on this very page, 3 posts above yours....

You can fork all you like, after all its your forking right, but please dont go spreading forking rumours
[Magisk] vithuselservices:
Thank you for your faith haha.

Ill admit my first release is taking a little longer then expected. I have proper eta's now.

Today i will get the migration tests complete to make sure no ones phones drops any settings when they move to my release. Once im confident with that ill be making a beta release to allow users to move from the original mhpc to mine.

Ill be dropping the first beta by Sunday.

Ive not pushed any changes to my git or my download repo as a worrying number of people were downloading my broken experiment releases even with the warning 😅.

Ill also need a few volunteers to be testers for fingerprints. As i cannot do as extensive testing of fingerprints ill be keeping new ones in beta and waiting to hear back from end users before i move those to stable so users can have more options.

There's also a separate hidden branch that's working on android 13 compatibility but ill pause that till after Sunday's release
[Magisk] Mlinko6:
Dear all,

I need your help with my fingerprint. I have an Fire HD 10 (Suez) with an Lineage 12.1 Rom and would like to be "supported" by Google so I can watch Netflix, Disney + etc. in FHD. Can someone help me out?

Thank you!

KR

Rok
[Magisk] pndwal:
So Android 5.1...

What does MHPC say is original value for fingerprint?; If it displays a valid one (I think LOS builds w/ valid prints) a device of this vintage should pass SafetyNet and new Play Integrity (Android builds from March 16 2018 often require ro.build.version.security_patch to be set to a date matching the fingerprint) with the following considerations AFAIK:

You will need:

1) Zygisk = Yes on Magisk home screen.

2) Either denylist enforced or Shamiko module installed w/ denylist NOT enforced; this still uses the dentist, but repurposes it as a hidelist.

3) gms (Google Play Services) attestation (droidguard) process (com.google.android.gms.unstable) in denylist.

4) MagiskHide Props Config module active but not configured (Edit MagiskHide props should be active by default) for automatic setting of sensitive props to 'safe' values. (Nb. This is likely, but not necessarily, needed, however if no triggering values are found nothing is altered anyway.)

With S/N passing in YASNAC and PI deviceIntegrity passing in Play Integrity API Checker, clearing Google Play Services and Google Play Store data and rebooting should restore Play Protect device certification and Netflix etc to Play Store... PW
[Magisk] Mlinko6:
Hi,

thx for your help! I've put the GPS on Denylist and activated it (I only have GPS installed), after the reboot I can't open GPS - which I actually don't as I can install the Netflix with an apk.

Netflix app recognises my Tablet as Nexus 5 but only plays the videos in SD:

View attachment 5762943
[Magisk] zgfg:
By GPS, do you mean Global Positioning System or Google Play Services

The second one we usually call GMS, since it's its package name: com.google.android.gMs

(GMS = Google Mobile Services, that would actually by a better name, but Play was probably chosen as more catchy - in line with Google Play Store, although they don't sell just games)

Also, you don't open (it's service, cannot be opened) Google Play Services but Google Play Store app (different thing, package name com.android.vending)

---

Anyway, it's strange that you cannot open Playstore - maybe you need to wipe its Cache

And yes, with the spoofed fingerprints, Netflix can now play for you but since you don't have L1 license with your (custom) ROM, you can only play by L3
[Magisk] Mlinko6:
Hi,

yes I meant Google Play Store, I still can't open it, even with cleared cache. But I'm not bothered by it, I'd like to know if I can get an L1 License so I'm able to play FHD Movies on my tablet :-). Is that even possible?

Cheers

Rok
[Magisk] zgfg:
AFAIK not, you would need the L1 certificate/licence, that must be supplied for the particular ROM (custom ROMs are not certified, it costs)

PS: Per the document linked to the later post #6381, it seems that Widevine certification does not cost
[Magisk] rocketda7331:
my los reports back that I have L1. I thought this was also based on passing safetynet or just having certified fingerprint
[Magisk] zgfg:
L1 has nothing with Google's SN / Play Integrity.

Different kind of certification - Widevine Digital Rights Management:

What is Widevine digital rights management (DRM) and why does it matter?

Google's Widevine DRM is used to check if your phone can stream HD content from services like Netflix. Here's what you need to know.

www.androidauthority.com

Btw, suggesting you to ask somewhere in the LOS channels about L1 in LOS
[Magisk] rocketda7331:
I am saying that I have L1 widevine on LOS which is custom ROM without doing anything special to actually get it and there is nothing to suggest they have paid for it so achieving L1 is not limited to stock ROMs as far as I can deduce. I only posted this as response to you suggesting it is not possible on custom roms. To me this suggests that L1 can be achieved on custom ROM without the developer paying for it; how - I don't know. But it seems helpful information to add nonetheless, as the person can try to find solutions to this issue and not throw away their attempts because they were told L1 is limited to stock only(or to be precise, limited to roms that devs have paid to get certified).

I understand these certifications are different but I thought were tied in a way, but apparently not. thank you for explaining this
[Magisk] zgfg:
Actually, per document enclosed to my previous post, DRM certification is not to be paid for

Btw, on my two Xiaomi phones (A11 and A12) I use Xiaomi.eu custom ROMs. Although the custom ROMs, they have L1 certs and Netflix happily plays with FHD, Dolby Vision HDR

And SafetyNet fix (I use to pass SN / Play Integrity) does not affect L1 DRM - screenshot
[Magisk] rocketda7331:
Yes, I was replying to a previous post of yours.

You made a statement that based on my experience does not reflect reality and I wanted to add clarifying information. I also already said I now understand that L1 and SN are not related, no need to repeat that.

Am I misunderstanding something? That the previous L1 in your post refers to something else than the later posts of yours?

Anyways the article seems to suggest the person can go to https://help.netflix.com/en/node/23939 and see if their device supports L1 in the first place. The page seems to make a point that you have to be on latest firmware which might be the first thing I would try to look into after confirming that hardware side the phone is certified.
[Magisk] pndwal:
Google Play Store? Why put that in denylist?; Only need to hide root from gms (Play Services) droidguard process (com.google.android.gms.unstable) as stated... Need to select Show System apps in menu to see/select this ..

Seems you're playing with MHPC settings you don't understand... Do you have Force BASIC key Attestation option active?; The default setting spoofs Nexus 5 in Model prop(s) on Google devices an very likely in devices unknown to MHPC... You certainly don't need to do this spoofing on your old device that uses Basic attestation out of the box... Hardware backed key attestation began w/ devices launched w/Android 8...

You should revert any MHPC changes you made; many are critical... Only use Edit MagiskHide props to automatically set sensitive props to 'safe' values as I said...

No, not possible on your device... This certification is hardware dependant and your device has no High Dynamic Range (HDR) / HDCP capabilities... Many lower spec modern devices never had L1 certification to begin with for this reason; your old hardware certainly can't render HD video and doesn't even have hardware TEE OS required for this task by the DRM / Widevine spec.

Nb. My original response was simply to help you pass SafetyNet and get Netflix in Play Store as requested...

🤠 PW
[Magisk] zgfg:
There is only one Widevine L1, needed for FHD playback of DRM protected media

While answering the post #3678, I thought that vendors have to pay for certification - when answering #3681, I googled, found and linked that document that states that L1 certification is for free, but nevertheless vendors have to go through the cert process

Anyway, I can not help you for your L1, specially related to LOS.

My advice was to ask in the LOS channels (threads, etc), since IMO, LOS users (for your device) could help you better
[Magisk] a.jacq90:
Any props for fold 4 ?
[Magisk] pndwal:
... Gets my props!... Reckon fold phones must rock!... Never held one but... PW
[Magisk] pndwal:
Widevine (L1) is a device certification but like CTS (Compatibility Test Suite) it depends on ROM configuration to pass… In practice it seems Android either pass L1 or have the default L3 security needed for standard definition rendering... L2 is not offered for Android AFAIK...

Implementation of this spec is also very much OEM dependant. Some devices do fail L1 without CTS Profile match (ie. S/N, PI deviceIntegrity) pass, others lose it on unlocking bootloader, but many seem to generally retain it easily... The degree of difficulty restoring L1 when keys are lost, revoked etc also varies between OEMs; some get it back on relocking bootloader, some need service department intervention to fix (OnePlus etc), others can fix by restoring persist partition, Oppo users can us an APK from service dept. to fix (a common APK works for some, other users need APK taylored to their IMEI)...

Xiaomi has messed up updates several times resulting in the need for renewed L1 certification, eg MUI 12.5 broke Widevine for many devices; Xiaomi have now implemented a fix for a number of devices like Redmi Note 10 Pro in the form of a feature that can be accessed via Settings > Passwords & security > Fingerprint unlock > Fingerprint payments > Widevine (L1)... Similar instructions for Note 9S:

https://adimorahblog.com/how-to-fix-widevine-l1-certificate-issue-on-redmi-note-9s/

We did cover this in April! 😉:

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

🤠 PW
[Magisk] 2nqey:
My play store now shows certified!!
[Magisk] Samrat Sengupta:
Thanks I will check with the ZOOL..if unsuccessful try with the configuration...:cool:
[Magisk] Didgeridoohan:
[MENTION=7447951]2nqey[/MENTION] The Play Store will only be certified until it does one of it's periodical checks. Then it'll be uncertified again... And the reason is: Xposed. You will not be able to pass SafetyNet with Xposed installed and active (yes, Xposed is your issue). Basic integrity will always fail, but you can get the cts profile to pass with the "No Device Check" Xposed module. That will likely also keep your Play Store certified.

About "invalid response": https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid
[Magisk] 2nqey:
Oh! Thank you so much for this, i appreciate.
[Magisk] prabhatpatel93:
Module for moto g4 plus 7.0 stock???

Will this work in moto g4 plus if basic integrety: fails and cts profile: fail also
[Magisk] Didgeridoohan:
https://github.com/Magisk-Modules-R...EADME.md#i-cant-pass-the-basicintegrity-check
[Magisk] BajinganTengik:
[MENTION=4667597]Didgeridoohan[/MENTION] please kindly check this fingerprint for Capricorn as on your list is still on 9.2.1.0

Thank you.
[Magisk] jdogg4000:
Thanks for posting this I just tried the note 3 fingerprint on my essential phone with custom rom and it's working as well for Google pay.

UPDATE: When I check Google account and devices it thinks the fingerprint is a Note 8.
[Magisk] Didgeridoohan:
Indeed... It looks like the Note 3 fingerprint in the module list has been confused with one from the Note 8. Nice catch and thank you. Another thing to put on the list of things to fix... :p

And about your Google account: that's the drawback to using a fingerprint for a different device. It'll be perceived as that device in certain situations.
[Magisk] NOS_bzone:
Hi dev,

Please adding new fingerprint for Mi Mix 2s running android pie 9.0, because on the list is only android 8.0. Thank you.
[Magisk] aydinbahadir88:
Magisk Hide works again

Im on Havoc OS 8.1, Redmi Note 5 Pro

All Pay and Banking Apps works perrect

Thank you Dev
[Magisk] paolocorpo:
Dear developer,

Initially thanks a lot for your effort into developing this module !!

I installed and used on my Xiaomi Mi A1 with 8.1.0 stock aug 5 security patch

As you know the my version is not listed

There is the Mi A1 but with 8.0.0 Oreo version (mine is 8.1.0)

I tried and I had success but only disabling Xposed module (as described in OP)

Play store/setting the device is described as not certified

May I have a problem using the script made for a different version ?

May I fix the info into Play Store information ?

View attachment 4586140

Inviato dal mio Mi A1 utilizzando Tapatalk
[Magisk] allrockedout:
I just got safety net to pass on Pie Treble. My device is mi mix 2 but I used fingerprint for mi mix 2s.

---------- Post added at 06:56 AM ---------- Previous post was at 06:41 AM ----------

I just used your fp for mi mix 2 lol and I'm on Pie as well. So I'll need yours for a while till op uploads one for my device.
[Magisk] Didgeridoohan:
About using different fingerprints:

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

And for the Play store you just need to make sure you're passing SafetyNet, clear Play Store data and possibly reboot.
[Magisk] paolocorpo:
Ok

I had a look to your Readme file: now it is clear It is not important thing to got the exact mix of device and version Android

And perfect: I cleaned data of Play store and now the device is classified as Certified

Many many thanks

Paolo

View attachment 4586318

Inviato dal mio Mi A1 utilizzando Tapatalk
[Magisk] dhom666:
Ty
[Magisk] susevista:
Please add support for device LG G4 H815 with Android 7.0 V30 Rom port v2.2
[Magisk] LORD.ABUMOHAND:
I'm on Android pie

The safetynet works fine and my device is certified on Google play but, still the banks apps aren't working. What's the problem here? I don't get it.
[Magisk] paolocorpo:
Have you Hide Magisk against these bank apps ?

Inviato dal mio Mi A1 utilizzando Tapatalk
[Magisk] LORD.ABUMOHAND:
Yep, still doesn't work

But I have a strange thing, when I run safetynet test on magisk it's passed, but with 3d party app doesn't pass.

View attachment 4586413
[Magisk] Mlinko6:
Dear PW,

your right about playing with MHPC, I'm no expert but if I do a mistake I can still flash the tablet and install the OS again. I'm only using it for streaming so I'm not afraid of beeing "hacked". I didn't know that the devices under Android 8 don't have the key attestation.

I'll survive with the videos not being played in FHD :-), it is mostly for my son that will watch the cartoons.

I'm gratefull for all your help!

KR

Rok
[Magisk] Light_8-0:
Just for saying THANK YOU !!!

All green on Pixel 2 with latest LineageOS.

:)
[Magisk] pndwal:
... Device launched with Android 8...

Are you using USNF module?... Guessing you mean you pass PI deviceIntegrity now with USNF and a mismatched fingerprint prop configured in MHPC module?; please say if other...

Nb. Most users are now using only @Displax fork of USNF w/ fix for PI deviceIntegrity... This is probably a better solution if assumptions above are correct... PW
[Magisk] Light_8-0:
I'll try my best to clearly answer; I'm no expert with all these.

I already had the latest LOS 19.1 installed.

Was unable to launch PayPal, so I started to search about the culprit.

After checking with YASNAC I installed latest Magisk with those two modules, USNF and MHPC.

During all the search, I haven't seen anything about Displax, so I'll have a look into it.

Thanks for sharing the tip about the new method. :)
[Magisk] pndwal:
So I guess you configured a passing fingerprint in MHPC (since official LOS won't spoof matching security patch date for a passing fingerprint prop)... Nb. SafetyNet is now deprecated and most security-centric apps are moving to Play Integrity API... Depending on the fingerprint you chose you may or may not pass PI deviceIntegrity although I'm guessing this is likely now needed for PayPal... If you're using an Android 11 (or under) level fingerprint prop it is likely you are passing as this creates an API level mismatch w/ your Android 12 that triggers hardware verdict enforcement bypass in PI API... Could be enforcement is already bypassed for devices as old as P2 anyway...

In any case, check deviceIntegrity with this:

https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck

Nb. You can't pass strongIntegrity w/ unlocked bootloader...

Even if already passing, @Displax modded USNF is better as critical prop changes target GMS attestation (droidguard) process only unlike globally applied MHPC changes so issues with device/OEM specific functionality are practically eliminated...

Nb. MHPC can be disabled as the modded USNF module is now setting a (very old) fingerprint prop to ensure that the needed mismatch for hardware key attestation enforcement bypass occurs for all A8+ devices and this also fixes CTS Profile match issues for custom, China region, developer ROM users etc). Download and usage here:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517

🤠 PW
[Magisk] Light_8-0:
I only meet Basic Integrity.

Will be doing some reading and be ready for LOS 20, which should be officially released soon.

Again, I appreciate all the info you're sharing. :)
[Magisk] pndwal:
So seems PayPal hasn't updated to Play Integrity API yet. 🙃... But they surely will sooner rather than later. (I guess PayPal appears in your Play Store, but Netflix and others likely don't show up)...

As discussed, simply swapping out MHPC for @Displax modded USNF should future-proof your P2... for a while. 😉 PW
[Magisk] Light_8-0:
Will do, likely tomorrow, and report. :)
[Magisk] Light_8-0:
Had some minutes to kill and tried as you suggested.

I now have 2 out of 3. Device and Basic are green. :)
[Magisk] westruk:
Hey guys, does anyone know why the "gsm.operator.iso-country" prop didn't change with this module?

all other props change without problems