yashsingh1/xdaforums huggingface dataset:
[Magisk] Mirardt:
Yep I did this and a bit more. This was the solution that finally allowed GPay to say yes to NFC. It still didnt work in the supermarket (that was a bit emberassing since I didn take my actual Wallet with me) because of some weird Mi Wallet settings, also Google Pay hadn't permission to use NFC :silly:. I fixed that setting and gave permission and gonna try again later today, but I'm confident that it should work now.

Thank you so much for your invaluable help <3

Yes, it remains and is the only thing that still sucks. Do you have any hint where I can start on working on this? I made this thread but it seems that there are not a lot of ideas.

I'm probably gonna do this after i setup my phone properly. I wiped it so much and tried stuff out that I really wanna have a "running system". Only decision to make is whether to install a chinese custom ROM or not since I can't that do later, right?

It really is!!! Completely notch- and bezelless 120hz OLED screen that gets super bright, quick charging, super fast chip, nice in-display fingerprint sensor and beautiful glass case for 307€. :D
[Magisk] zgfg:
That's why a backup, in one form or another, even as a plastic is important?

But wait a minute, I use to debloat Mi Wallet - don't say that you needed for GPay, or how did you have to change the Mi Wallet settings?

Thx, been there, seen that - not sure if the hint about monitoring UE Capabilities in negotiating could help you

Ok, so how/where did you purchase/order the phone?
[Magisk] Mirardt:
Nope I just changed my default wallet from Mi Pay to HCE Wallet and it worked. Just went to the supermarket again and Google Pay works. (: Only weird thing that i had to open the Google Pay/ it didnt work from lockscreen. Not sure why but I'm gonna figure it out and its not a big deal anyway.

Nice thanks for the comment I'm gonna try to understand what it is all about!

Ordered it at TradingShenzen but it was like 10 bucks cheaper. Also i used a discount code from their newsletter and 30 bucks back because I got the wrong color. The support was very friendly and offered me the choice of either getting a new one or keeping the phone and cashing in 30€. Since I was very on the edge between black and white anyway I just kept it.
[Magisk] zgfg:
Excellent purchase

Btw, I debloat Mi Pay, Mi Wallet, Mi Credit and things like that?
[Magisk] Mirardt:
Thank you feels good to read that!! :cool:

Oh yeah I'm totally gonna debloat all of those Apps. I just didn't do it so far because it would be back at the next wipe.

Btw is there any chance that apps like "Carrier Services" from google could help me out with the LTE issue? Because I'm gonna need to debloat a LOT of apps to be able to install GApps mini which includes "Carrier Services" but I have the feeling that the phone could run considerably better with a big fat stock google package flashed in twrp after a wipe. Also I'd be able to remove apps like Phone and replace it with the google versions.
[Magisk] zgfg:
I don't recall do you have TWRP - with TWRP would be easier/safer, you renane an unwanted stock app on System to bak, reboot and in case of bootloop you just rename back to apk.

Once you are sure about, you really remove it

You can debloat various Mi* apps (see my recent posts in the Magisk thread - point was on something else but there is the list of 50 apps I debloat).

You can also remove stuff like Calculator, Notepad and similar, not integrated with the phone (you can larer install the same or alternative apps from Playstore or elswhere)

You can also remove GMaps, GMail (any mail), GBoard (maybe not present in your Chinese firmware), YouTube, WhatsApp - apps that you can later install (to Data) from Playstore or even from apkmirror
[Magisk] Spartacus500:
I have another question, is it possible to cheat with this module that the device is encrypted on the Samsung S7 9.0 Pie NFE 2.2? The entry that is responsible for whether it is enabled or not is this one:

getprop ro.crypto.state

ro.crypto.state = unencrypted
[Magisk] Didgeridoohan:
If it's a prop you can use the module (or just simply the Magisk resetprop tool if you want full control).

If you're asking what would happen if you change that prop, the answer would be: please let me know when you've tried (make sure to have a backup of your data).
[Magisk] Spartacus500:
I don't want to risk losing my data, I'm looking for a way to fool the device that it's encrypted but it really isn't. But how to do it :confused:
[Magisk] Displax:
New Pixel`s:

Google Pixel 4a (5G) (11):Google:Pixel 4a (5G)=google/bramble/bramble:11/RD1A.200810.020/6792687:user/release-keys__2020-10-05
Google Pixel 5 (11):Google:Pixel 5=google/redfin/redfin:11/RD1A.200810.020/6792687:user/release-keys__2020-10-05
[Magisk] zgfg:
If I understand correctly, resetprop would really change the ro property, not systemlessly like MHPC does

But what about vendor/etc/fstab* with the filedystems flags, like for encrypted /data:

fileencryption=ice

or

fileencryption=aes-256

I would be also highly interested in the outcome, but I would not test on my phone ⁉️ - [MENTION=6138728]Spartacus500[/MENTION], don't worry, it can not trigger a termonuclear war

If it's only for spoofing (but not already at a boot time), wouldn't be better to stick with MHPC, custom props option (5 if I recall correctly), making it systemlessly
[Magisk] Didgeridoohan:
You mean the resetprop tool? That's what MHPC uses and is quite systemless... If you know how the tool works this module is really just a bunch of unnecessary bytes on your device.
[Magisk] zgfg:
Wouldn't resetprop -n bypass reset_prop and thus really change the read-only ro property?

Or is -n just to bypass reset_prop that does not allow changing the ro property, but the change is still systemless

To simplify, when your MHCP (systemlessly) chanes ro properties, does it also use resetprop -n?
[Magisk] Didgeridoohan:
The module mostly uses the system.prop file (the default setting), which means that it's actually Magisk that executes the resetprop command on that file during boot. And if I remember correctly it uses the -n flag. Which the module also uses in most places (IIRC, there's no need to use anything else during boot).

Being systemless just means that it doesn't touch the system partition, as in: editing build.prop (or whichever prop file the prop is stored in) directly. Resetprop just loads the value to memory (prop_area), over whatever was loaded from the prop files. The only option/flag of resetprop that doesn't just load a value to memory is the -p flag (and that only touches /data/property, not any system files).

Caveat:

Even though the prop changes with resetprop are systemless (doesn't edit system files), changing a prop can have very real consequences for your system as a whole... Always be careful, even when it's systemless.
[Magisk] Some_Random_Username:
Hello, here are more OnePlus 8T fingerprints:

OnePlus/OnePlus8T_IND/OnePlus8T:11/RP1A.201005.001/2009181137:user/release-keys__2020-09-01

OnePlus/OnePlus8T/OnePlus8T:11/RP1A.201005.001/2009181139:user/release-keys__2020-09-01

OnePlus/OnePlus8TTMO/OnePlus8TTMO:11/RP1A.201005.001/2009240808:user/release-keys__2020-09-01

T-Mobile fingerprint is for KB2007 while international fingerprint is for KB2005.

I don't know yet about model number for indian build, I will tell later when I will find it.
[Magisk] Didgeridoohan:
Following the pattern from previous devices I would guess KB2001.
[Magisk] zgfg:
Thank you for clarifying

One more reason (GCam ports read ro.product.device to identify the phone) to be careful with not spoofing ro.product props that are not necessary to pass SafetyNet.

We should know if there are really devices that need more/different than ro.product.model for CTS Basic
[Magisk] zgfg:
Xiaomi Mi 9T, MIUI 12 Global, Android 10:

Thanks

PS: Tested, passing
[Magisk] Displax:
Xiaomi Mi A2 Lite

xiaomi/daisy/daisy_sprout:10/QKQ1.191002.002/V11.0.12.0.QDLMIXM:user/release-keys__2020-10-01
[Magisk] Damianek420:
brand=Xiaomi

device=dipper

manufacturer=Xiaomi

model=MI 8

name=dipper

LineageOS 17.1

Xiaomi/dipper/dipper:8.1.0/OPM1.171019.011/V9.5.5.0.OEAMIFA:user/release-keys__2020-10-05
[Magisk] Displax:
Some updates to NVIDIA products:

1. Rename "Nvidia Shield TV Pro" to "Nvidia Shield TV 2015 Pro".

2. Add "Nvidia Shield TV 2015" (foster_e)

3. Add "Nvidia Shield TV 2019" (sif)

4. Add "Nvidia Shield TV 2019 Pro" (mdarcy)

5. Update all prints.

Ready code:

Nvidia Shield TV 2015 (8.0.0 & 9):NVIDIA:SHIELD Android TV=NVIDIA/foster_e/foster:8.0.0/OPR6.170623.010/3507953_1441.7411:user/release-keys__2018-12-05;NVIDIA/foster_e/foster:9/PPR1.180610.011/4079208_2235.1395:user/release-keys__2020-07-05
Nvidia Shield TV 2015 Pro (8.0.0 & 9):NVIDIA:SHIELD Android TV=NVIDIA/foster_e_hdd/foster:8.0.0/OPR6.170623.010/3507953_1441.7411:user/release-keys__2018-12-05;NVIDIA/foster_e_hdd/foster:9/PPR1.180610.011/4079208_2235.1395:user/release-keys__2020-07-05
Nvidia Shield TV 2017 (8.0.0 & 9):NVIDIA:SHIELD Android TV=NVIDIA/darcy/darcy:8.0.0/OPR6.170623.010/3507953_1441.7411:user/release-keys__2018-12-05;NVIDIA/darcy/darcy:9/PPR1.180610.011/4079208_2235.1395:user/release-keys__2020-07-05
Nvidia Shield TV 2019 (9):NVIDIA:SHIELD Android TV=NVIDIA/sif/sif:9/PPR1.180610.011/4079180_2235.1395:user/release-keys__2020-07-05
Nvidia Shield TV 2019 Pro (9):NVIDIA:SHIELD Android TV=NVIDIA/mdarcy/mdarcy:9/PPR1.180610.011/4079208_2235.1395:user/release-keys__2020-07-05
[Magisk] Didgeridoohan:
Thanks, but that exact print is already included in the module fingerprints list. And newer ones at that...

If you did pick that print from a LOS 17.1 build, that just means that they're including an old device fingerprint in the ROM (must be an unofficial build, since IIRC official LOS builds never include a certified device fingerprint).
[Magisk] Spartacus500:
How to change the file java "os.version" name Kernel ?
[Magisk] Didgeridoohan:
Sounds like you would need to recompile the kernel. That's outside the scope or topic for this thread (and my skills, at least)...
[Magisk] Spartacus500:
I have no idea and tools how to do it, I wanted to cheat the system like editing getprop, but can such a command work :confused:

resetprop proc/sys/kernel/version "date release Kernel"

resetprop proc/sys/kernel/osrelease "name Kernel"

:confused: :confused: :confused:
[Magisk] Damianek420:
[MENTION=4667597]Didgeridoohan[/MENTION]

Ohh sorry for that, I have not checked the fingerprint database before. My Build was from the official website(17.1 and next few from ota) I don't know why fingerprint is for version 8.1 cuz im on 10 and I didn't use your script before this. But after activating fingerptint from your script in Build.props I still have this one from 8.1

However, It's still going through safetynet so I Probably don't have anything to worry about.
[Magisk] Didgeridoohan:
No, that won't work.

You can only change/add prop values. Simply put: if you can see it with the getprop command you can change it with resetprop. And when you run the resetprop on a prop that doesn't currently exist on your system it will add it. But the command you have there will just result in an error of the "illegal property" kind.

You'll have to practise your Google-Fu if you want to find how to get this done (recompiling the kernel)...
[Magisk] Didgeridoohan:
Like I said, it's likely that whomever is building that release of LOS is using a certified fingerprint to make the ROM pass SafetyNet from the get-go. They just haven't bothered using anything newer (since it works).

But if you install this module and pick a different fingerprint from the module list it should change the used print. It won't show up in the build.prop though, you'll have to use getprop (or check the "Edit device fingerprint" menu).

But as you say, things are working and you have nothing to worry about.
[Magisk] Damians82:
I flashed AOSP 10 on this device (pra-LX1) but default fingerprint don't pass safetynet.

Which is the better fingerprint?
[Magisk] Didgeridoohan:
What do you mean by "default fingerprint"? The ROM fingerprint (which for custom ROMs won't be certified) or the fingerprint included in the module list?

If you mean the ROM print, change to the module print for the PRA-LX1.

If you mean the module print and you're still not passing SafetyNet, take a look here: https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] Legion495:
I tried that... well i mean I do not even pass basicintegrity running a LOS GSI.

Either way. I tried using props and I got a never ending bootscreen. Or does it take insanely long to boot?
[Magisk] Didgeridoohan:
If you don't pass basic integrity it's very likely that there's nothing this module can do for you. Until you figure out what is triggering SafetyNet or what causes MagiskHide to fail (assuming that you've enabled it at all).

Boot should not take "insanely long"... Did you only set a fingerprint, or did you do not more than that? To even have a chance of helping with that (if that's what you're asking for) I would have to see some kind of log, at least.
[Magisk] zgfg:
MHCP modules is only for prop(ertie)s, not for files.

Is this really a file and what is its full path?
[Magisk] Damians82:
I mean fingerprint included in module list (from terminal > props > 1 - Edit device fingerprint), but I Don't pass safetynet.

I need to make myself a custom fingerprint?
[Magisk] Didgeridoohan:
No. You need to figure out why it's failing... The link I posted for you is a good place to start.
[Magisk] fvx12:
is there anyone that can help on providing a valid fingerprint for Samsung J7 Prime SM-G610Y?
[Magisk] Didgeridoohan:
Have you tried the various methods that are described in the docs?

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint
[Magisk] fvx12:
thanks for pointing that out. since im new to this, can you review this one. here's what im going to put on the printslist file

Samsung Galaxy J7 Prime SM-G610Y (6.0.1):Samsung:Galaxy J7 Prime=samsung/on7xeltezt/on7xelte:7.0/NRD90M/G610YZTU1BRF1:user/release-keys

is it in the right format?

sorry for such a noob question.
[Magisk] Didgeridoohan:
Looks good. Expect that's an Android 7.0 print, so you can change the info in the parenthesis (it's purely cosmetical though).
[Magisk] djjohnnyblaze:
Hi everyone,

Got a google play services update today that now forces my Pixel 3a to use HARDWARE for evalType.

I am trying to use the module to change it to use BASIC. However, when I try to use option 2 in the module, it asks me if I want to disable forced BASIC key attestation. So I assume it is already enabled. I tried choosing a different google pixel model from the list and rebooted but it always says currently loaded value is Pixel 3a.

Can anyone point me in the right direction?

sargo:/ # getprop ro.product.model
Pixel 3a
sargo:/ #

Thanks in advance!
[Magisk] ahecht:
Even though my 3a was switched to hardware key attestation, choosing the 3a option fixed it for me. Did you try disabling, rebooting, and re-enabling?
[Magisk] djjohnnyblaze:
I tried disabling it but even after a reboot it still asks if I want to disable it.
[Magisk] Didgeridoohan:
[MENTION=4950275]djjohnnyblaze[/MENTION] Try resetting the module (option "r" in the main menu) and starting over. You do not need to reboot directly after the reset, but can set everything up again first.
[Magisk] djjohnnyblaze:
[MENTION=4667597]Didgeridoohan[/MENTION], thanks that worked! However, I chose Pixel 3a from the list and rebooted but its still set to HARDWARE. Is there any recommended device to try from the list for Pixel 3a?

Thanks in advance
[Magisk] Didgeridoohan:
Anything except your own device should do it.

Edit: picking one as close to your own device as possible is generally a good idea, so as not to lose any device specific features (possibly).
[Magisk] djjohnnyblaze:
That did the trick, thanks! Selected pixel 4a
[Magisk] Klownicle:
So I've installed this and I'm trying to switch my device to something other than the 3a to fix the hardware detection and go back to basic. When I go to choose, it only lists Nvidia and Xiaomi on my Pixel 3a. What am I doing/missing to select the Pixel 4a device?
[Magisk] Didgeridoohan:
Sounds like you've accidentally downloaded the developer's fingerprints test file... :laugh: For real, no joke.

Run "props -f" and you'll get the proper device list.
[Magisk] Klownicle:
That worked, no idea. I just installed it from Magisk directly. :good:
[Magisk] paolocorpo:
Dear developer,

I used your module a couple of years ago with my XIAOMI Mi A1

At that time ... it was probably Android 7 or 8 ... I don't remember

I was able 2 years ago to fix my Safety Check in Google Play setting

My Mi A1 now has normal Android 9.0 patch August 2020 but it is unlocked and rooted with Magisk 21.0

Now I have not the same result :(

Under Play Store setting the device is NOT CERTIFIED

Under Magisk teh Safety Net check is OK for basicintegrity but not for ctsProfile

I am not able to install NETFLIX app by Play Store ...

Thank you for support

Paolo

EDIT

I used the fingerprint for Android 8 and now the device looks as certified ... good ;)

But ctsProfile is not OK :(

Netflix app is not available ... :(

EDIT 2

Setting Magisk Hide > ctsProfile check is OK now

But nevertheless Netflix app is not available on Play Store :(
[Magisk] Didgeridoohan:
[MENTION=5056724]paolocorpo[/MENTION] First thing to check is if your device uses hardware attestation. Make a SafetyNet check in the Magisk Manager and it'll tell you if evalType is basic or hardware. If it's hardware you'll need to force it to basic to pass CTS.

Either way, you've got more info in the docs:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] paolocorpo:
Dear many thanks

The check is software based

cts profile check now is OK > it was only necessary to hide Magisk ;)

But ... nevertheless ... NETFLIX app is not available to me on Play Store :(
[Magisk] Didgeridoohan:
It helps having MagiskHide active, yes. :laugh:

You'll likely have to clear data for the Play Store to get it certified:

https://www.didgeridoohan.com/magis...and_other_apps_wont_install_or_doesnt_show_up
[Magisk] paolocorpo:
As usual .. you have really helped me !!

All is oK now (after a clear data of PlayStore) as you suggested

Netflix has been installed on my Mi A1 !!

Thanks a lot :laugh::good:
[Magisk] jonsnow69:
A quick thanks to the dev. My Galaxy S9 now passes safetynet, I had to use options 1 and 2.

It's my understanding switching to evalType BASIC is a temporary fix only. I'm still learning but would appreciate advice if there's anything else I can do to prepare for google forcing hardware evalType.
[Magisk] Didgeridoohan:
Knowing Google, "temporary" might mean years. Or days...

Once they do enforce it (if they ever do), the outlook of being able to pass CTS with an unlocked bootloader looks bleak. But we'll cross that bridge when we get there.
[Magisk] dron39:
Didgeridoohan,

Good evening,

What should I send you to add N9860 (Galaxy Note 20 Ultra 5G China) to the list ?
[Magisk] xunholyx:
Read the OP is what you should do.

It has a link to know how to do it that sends you to this: https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint
[Magisk] maialo:
not work for readmi 9 pro, MIUI Global 11.0.7

:(
[Magisk] Didgeridoohan:
A bit more information would be necessary if you require any kind of assistance...

What doesn't work? Have you changed the device fingerprint, but CTS still fails? Tried forcing basic attestation, but it still uses hardware? Is there an error?

Details, and possibly logs are needed.
[Magisk] dron39:
Didgeridoohan,

Could you please add Samsung Galaxy Note 20 Ultra 5G (SM-N9860) HongKong TGY.

There is result of "getprop ro.build.fingerprint" on latest stock non-rooted firmware for SM-N9860:

samsung/c2qzhx/c2q:10/QP1A.190711.020/N9860ZSU1ATJ6:user/release-keys
[Magisk] Didgeridoohan:
Thank you.

What's the security patch date?
[Magisk] Displax:
Xiaomi Mi A2

xiaomi/jasmine/jasmine_sprout:10/QKQ1.190910.002/V11.0.15.0.QDIMIXM:user/release-keys__2020-10-01
[Magisk] dron39:
1 September 2020
[Magisk] maialo:
Have you changed the device fingerprint, but CTS still fails
[Magisk] Didgeridoohan:
Then I suggest you start reading here:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] maialo:
"Force BASIC key attestation option" it worked for me!

Thanks for your work
[Magisk] C0rn3j:
Entry 25 - Redmi should be merged under entry 30 - Xiaomi
[Magisk] piojan:
Hi,

I have a problem with using the module on Huawai Mate 10 Pro. When I was on L29B432C137 or C145 the ctsProfile was true. I have installed C148SP1 (few weeks ago something different) and I am not able to pass the ctsProfile check with this module. When I do "getprop ro.build.fingerprint" it shows 137 or 145 (or from P20 - I once tried that). However the magisk still shows ctsProfile false. And the about / phone shows C148SP1 version. I already tried changing the boot order. Is the any thing else to check?
[Magisk] Didgeridoohan:
Hm... I'll take a look at your logs a bit later.
[Magisk] Ravi_sh594:
I am using it on redmi 5 plus but not able to pass safety net..
[Magisk] MajinkenSword:
Hi, I don't really mind it but just wanted to check if it could be resolved.

On my Huawei P20 Pro using custom rom, RomAur v1.3. Cts and basicintegrity always show false.

Before this, I was using stock and always passed cts and basicintegrity after activating your module.

Here are my logs for your perusal...

Edit: Encountering issues uploading logs... will try again later
[Magisk] Didgeridoohan:
MIUI often have issues passing ctsProfile by just changing the device fingerprint. Especially on China builds. If you need further help, please provide logs.

XDA have had a lot of issues with attachments lately...

If you can't pass basicIntegrity, this module can't do anything for you.

https://github.com/Magisk-Modules-R...EADME.md#i-cant-pass-the-basicintegrity-check
[Magisk] Didgeridoohan:
Fingerprints list update - v24

Added a few fingerprints, courtesy of P1N20 over at GitHub. Thank you very much.

Added:

Asus Zenfone 4 Max

Xiaomi Redmi 3S/X Prime, Redmi 5A and Redmi Note 2

ZTE Blade
[Magisk] Tecalote:
Things you should know:

1) If you flash Firmware downloaded from Firmware Finder for Huawei, which is currently not approved, your ctsProfile has the result = false.

It's not the case, if you use Firmware (installing with HWOTA or HuRUpdater or FF) which is shown as approved. Then you also don't need to modify the Fingerprint.

2) I wouldn't recommend to flash (unofficial) Firmware, which is not approved.

3) If you have time, check this out:

https://xdaforums.com/mate-10/how-to/beware-bla-l29c432b147-t3817241

Huawei uses on Mate 10 (+Pro) two different xloader.img in the Firmwares (01 and 02). We don't know the reason. The Firmware you have currently (b148SP1) has xloader 01. And I guess you had previous already Firmware with xloader 02 installed.

If you update or downgrade next from xloader 01 to a Firmware which has xloader 02 your device can be hard bricked (without any function, no Fastboot mode, no Recovery, just Black Screen)

4) If you change the Fingerprint with this awesome module by Didgeridoohan - on Huawei Phones Settings "About Phone" /Build Number will show you always the installed Firmware, because it's only the "display-ID" and not the Fingerprint

- but if you check it with any system info app, it will show you the changed Fingerprint.
[Magisk] flow.gunso:
Nvidia Shield Tablet (7.0)=nvidia/wx_na_wf/shieldtablet:7.0/NRD90M/1928188_904.2811:user/release-keys

Just tested that one. It works.
[Magisk] Didgeridoohan:
Another fingerprints list update - v25

Ok... I did another quick update of the list, with the fingerprint for the Nvidia Shield Tablet provided by [MENTION=8142266]flow.gunso[/MENTION]. Thank you.
[Magisk] _Ayhan_:
Mi5s plus miui 10 Android Xiaomi/natrium/natrium:7.0/NRD90M/8.7.26:user/release-keys
[Magisk] gingin88:
mate9

Device Build Fingerprints: HUAWEI/MHA-L29/HWMHA:8.0.0/HUAWEIMHA-L29/373(C636):user/release-keys

Postscript This fingerpirint comes from LineageOS Beta 4 open kinrin.