yashsingh1/xdaforums huggingface dataset:
[Magisk] ipdev:
I struck out on Oppo. :o

[MENTION=1758866]cd993[/MENTION]

Was looking for Asus 7 Pro so, I grabbed a few Asus prints to add to the list.

Asus ZenFone 4, 5, 3 Ultra and 7 Pro.

Had to adjust the prints for 4 and 5 to pass.

As for Poco F2 Pro, not sure if it is necessary to replace the current one in the list.

Switch from EU Global to Global.

Cheers all. :cowboy:
[Magisk] Didgeridoohan:
Fingerprints list update to v104

Had a few fingerprints to add to the list, and since I've got important schoolwork to do this is the perfect time.

Thank you [MENTION=4450994]kk9999gada[/MENTION], [MENTION=8234677]Some_Random_Username[/MENTION], [MENTION=6345368]Displax[/MENTION] and [MENTION=7280276]ipdev[/MENTION] for allowing me to procrastinate.

New

Asus ZenFone 3 Ultra

Asus ZenFone 4

Asus ZenFone 5

Asus ZenFone 7/7 Pro

OnePlus 8 IN2015 Visible

POCO F2 Pro Global

Samsung Galaxy Tab S4 LTE

Updated

Asus ZenFone Max Pro M1

Xiaomi Mi A2 Lite
[Magisk] Didgeridoohan:
Module updated to v5.3.5

Small bug fix. The changelog speaks for itself...

Changelog

v5.3.5

Fixed issue with partition model props not being set correctly.

Make sure that simulating ro.product.model is completely disabled when enabling "Force BASIC key attestation".

Removed Android versions from the device list when picking a model for "Force BASIC key attestation".
[Magisk] Zachary_Foxx:
Hi [MENTION=4667597]Didgeridoohan[/MENTION]

I would like to try to configure the module on a clean Magisk / ROM flash.

If I keep propsconf_conf with the default options and just set "CONFIG FINGERPRINT", is it the same as doing a normal installation just using the props command on a terminal?

And the "CONFIGFINGERPRINT" should be defined as follows:

CONFFINGERPRINT="Xiaomi Mi Pad (4.4.4):Xiaomi:MI PAD=Xiaomi/mocha/mocha:4.4.4/KTU84P/V7.5.2.0.KXFMIDE:user/release-keys"
[Magisk] Didgeridoohan:
Hello.

Yes.

Yes.

Edit: actually no. You only need the part after the equal sign.
[Magisk] cmstlist:
Woke up this morning and Pixel-4a is no longer passing using the Pixel-4a fingerprint. It's doing HARDWARE attestation and failing.
[Magisk] Didgeridoohan:
Seems like Google turned the switch again yesterday (for the umpteenth time).

It's got nothing to do with the device fingerprint. Try changing to basic attestation (currently option 2 in the main menu of the module, "Force BASIC key attestation").
[Magisk] cmstlist:
Yes that's exactly what I was already doing and did again. I selected force BASIC, chose 4a as fingerprint, and it didn't work anymore as of this morning. SafetyNet check was still running in HARDWARE mode.

Tried 3a instead and now it passes but Google Pay is still angry.
[Magisk] Didgeridoohan:
The Pixel 4a uses hardware attestation out of the box, so you can't use that for the "Force BASIC key attestation" feature.
[Magisk] cmstlist:
Hmm. Well forcing 4a to BASIC using its own fingerprint worked for about 2 weeks compared to not using the module at all. I guess Google did flip a switch.
[Magisk] Didgeridoohan:
For the past few weeks CTS has been passing even with hardware backed key attestation. Google has been testing things, probably. You sure it was using basic attestation though, or did you just assume so since CTS was passing? As far as I know the 4a has been in Google's list the whole time.

And, again, tricking the attestation check has nothing to do with the fingerprint... We're using the device model to change from hardware to basic.
[Magisk] cmstlist:
Wrong word then, device model.

Yes I am sure that when I first got the phone and setup Magisk, it was failing in HARDWARE mode. I am also sure that after I invoked your module and selected 4a, it started passing in BASIC mode. Today I got a notification from Google Pay that my device no longer met security requirements, so I checked and it was again failing in HARDWARE mode.

I upgraded Magisk, upgraded your module, still failing in HARDWARE mode. Switched to 3a and now passing again in BASIC mode.
[Magisk] dron39:
And? Is Gpay working now?
[Magisk] cmstlist:
Pay was still unhappy but I think it might be because it remembered. I uninstalled, reinstalled, re-enabled Hide, and it was happy.

EDIT: nope never mind, it's again telling me my phone doesn't meet security requirements
[Magisk] dron39:
So... To make Gpay happy :) I need to make above-described by you steps, reinstall Gpay, and it will work again?
[Magisk] cmstlist:
Read my edit. No it's still not happy. Open to suggestions.
[Magisk] Didgeridoohan:
[MENTION=2280859]cmstlist[/MENTION] and [MENTION=2038193]dron39[/MENTION]

https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
[Magisk] pndwal:
Just to be clear:

You have full SafetyNet pass? Playstore shows 'certified'? Have SQLite fix and SQLite binaries installed? Hidden root in Magisk Manager for G Playstore, G Play services, GServices framework and GPay app? Cleared Data for GPay app? Tried clearing data for G Playstore, G Play services, GServices framework too? GPay shows in Playstore?... As long SafetyNet passes, and Playstore certified, better answer in thread linked above! :D PW
[Magisk] cmstlist:
Magisk says I pass SafetyNet, basicIntegrity, ctsProfile, evalType BASIC. I am currently presenting as Pixel 3a.

Play Store still shows Certified.

Don't know what you mean by "SQLite fix".

Yes I have Magisk Hide enabled for Play Store, GP Services, Pay. Did not have it enabled for Framework though.

Cleared data for GPay app. GPay shows in Play Store.

Haven't tried clearing more of above, can test after work.
[Magisk] pndwal:
Well that's the problem. Without SQLite fix, GPay stays angry with root. (MagiskHide alone doesn't hide root on its own for all banking apps, etc.)

Check here:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post82509725

Read full post for SQLite Fix module (2nd link)... It's a doozy, worth every penny. PW
[Magisk] cmstlist:
Strange. I went 2 full weeks of Pay being happy without any SQLite Fix.
[Magisk] Didgeridoohan:
Come on guys... Please keep the thread on topic. A link to the discussion thread for GPay has already been posted above. Keep further discussion regarding Pay there, please.
[Magisk] TheUndertaker21:
Hi [MENTION=4667597]Didgeridoohan[/MENTION]

How are you? I see there's no note 20ultra

This is my fingerprint from my note 20ultra U model

Rooted but the rom I am on is having cst issue.

Gonna flash a s20 ultra fingerprint and see.

There's my below

It's for the SM-N986U1

samsung/c2qsqw/c2q:10/QP1A.190711.020/N986USQU1ATH3

edt: fixed with option 2.

no need to change the fingerprint
[Magisk] Didgeridoohan:
I might as well add it the list, but I'll need the security patch date as well.
[Magisk] TheUndertaker21:
Haha you got it

View attachment 5103567
[Magisk] Didgeridoohan:
I just noticed I was selectively blind the first time reading your post. You only want the part after the equal sign, that's the fingerprint. The rest, before that, is just information specific for this module.
[Magisk] azzyhighlights:
S20

Hey [MENTION=4667597]Didgeridoohan[/MENTION] I'm new to rooting. Rooted my s20 G980F. I know Samsung isn't the best phone to root ?. How can I pass the ctsprofile? If there's fingerprint out there for it that passes the securitynet I'd appreciate it :)
[Magisk] Didgeridoohan:
If it's just rooted and on stock ROM still, you do not need to mess with the fingerprint. The stock ROM will already be certified.

First, make sure that MagiskHide is actually enabled in the Manager settings.

What you might have to do is to force the bootloader state check to use basic key attestation rather than hardware backed. You do that with the "Force BASIC key attestation" feature of the module (entry 2 in the main menu).

Further reading found here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] PoochyX:
You really left me on unread tho when I came to you for help [emoji849]

([emoji88]Omni Rom[emoji88])
[Magisk] Didgeridoohan:
Not sure what that's about, but do you mean this off-topic post that I replied to here?
[Magisk] PoochyX:
My bad I didn't see that [emoji53]

([emoji88]Omni Rom[emoji88])
[Magisk] azzyhighlights:
Hey [MENTION=4667597]Didgeridoohan[/MENTION]. Option 2 works perfectly and thanks for the detailed reply. However my model number in settings shows us up as A300F instead of G980F. Will this affect my performance and how can I get it to state G980F and still pass the CTSprofile? Cheers man
[Magisk] Didgeridoohan:
Changing the model is how we fool SafetyNet into using basic attestation rather than hardware.

https://github.com/Magisk-Modules-R...master/README.md#my-devices-model-has-changed

If you don't want the model to show as A300F you can manually pick from the device list instead, but be warned that not all the devices on the list will use basic attestation... If you still want to go with Samsung, but want something newer, I have had reports that the S9 uses basic attestation.
[Magisk] azzyhighlights:
Thank you
[Magisk] Feeleepino:
Poco x3 cts profile

Hi,

Just got to run magisk on my Poco x3 passing safety net but have to tweak the props to make cts profile pass.

This is the actual prop from a stock + lightly debloated + unlocked and magisked device.. FYI:

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

I am trying to find the keys from in the image files of the 12.0.2 global update to compare but could it be that they are still not validated by big G?
[Magisk] Milouz57:
Hello, im using a Redmi Note 9 Pro, module is up to date with v104 list, but with termux i cant find my device but in this thread i saw it was supported... [IMG="screenshot termux"]https://i.imgur.com/VSde0Kk.jpg[/IMG]
[Magisk] ipdev:
That looks to be the global print. Passes SafetyNet for me with 2020-09-01 as the security date.

Xiaomi is a little goofy with branding.

Redmi Note 9 Pro is in the Redmi list instead of Xiaomi.

Cheers all. :cowboy:
[Magisk] Jon8RFC:
I have a problem...

I've been updating option 2 to force basic attestation with each new version/list, just incase something with the fingerprint changes since I don't know what all it entails.

It seems like 5.3.5-v104 maybe I accidentally changed from Pixel 3a (phone is a Pixel 4 using Android 11 Sept 2020 update) to Nexus 5 and didn't type the zero to set Pixel 3a, but I've not been able to change it back to Pixel 3a from Nexus 5. Is turning off option 2 and then turning it back on absolutely necessary to get Pixel 3a to be set again?
[Magisk] Didgeridoohan:
There's absolutely no need to reapply the "Force BASIC key attestation" feature unless you want to change to another device. The model value does not change when a fingerprint is updated.

Exception: in v5.3.5 I fixed an bug where partition specific model props didn't get set properly in some cases. After updating to v5.3.5 it might have been necessary to reapply the feature...

Changing the device you use for the basic attestation feature is just a matter of going back into the list of devices and picking the one you want to use instead (and then rebooting). I just tested and can't see any issue with that...
[Magisk] whitewallman:
Hello and thanks for this module!

I'm running into a bit of a problem though.

I use a Pixel 4 XL (Android 11).

To pass safety net, I have to set "force basic".

I also chose Pixel 4 XL (Android 11) as fingerprint.

Passes safety net, but identifies as "Nexus 5" no matter what I do. Can anyone put me in the right direction to fix this?
[Magisk] pndwal:
https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228/post83576605
[Magisk] amk316:
ok ... in my galaxy s10

i chose #1 fingerprint and chose a galaxy s10 ... safetynet did not pass

i chose #2 force basic and chose a galaxy s10 ... safetynet did not pass

i chose #2 force basic and chose a galaxy s9 ... safetynet pass

is something not working if i chose a s10 in fingerprint or force basic???
[Magisk] Didgeridoohan:
The S10 is on Google's list of devices that use hardware backed key attestation, so nothing changes with your device if you pick that for the "Force BASIC key attestation" feature.

Meanwhile, the S9 is not on their list, so it'll use basic attestation and if you use that for the "Force BASIC key attestation" feature you'll fool SafetyNet into thinking that you're using an S9 and CTS will pass even with an unlocked bootloader.

Edit: you can still use the S10 fingerprint, but you'll have to use some other device (that's not on Google's list) for "Force BASIC key attestation".
[Magisk] amk316:
yes i under stand ... but why is the s10 fingerprint is listed if its not working or is there more to do than just select and reboot my device??
[Magisk] Didgeridoohan:
The S10 (and other devices that use hardware attestation) is listed under "Force BASIC key attestation" because I'm using the module fingerprint list as a base for that device list (but just to make sure that all info is correct here, it's not using the fingerprint but the device model). It's practically impossible for me to know beforehand which devices are listed as using hardware, so you'll get them all as a choice.

This is a temporary (although we do not know how long "temporary" is for Google) measure, so I'm not going to be spending more on this feature than is necessary... It works; go with the default value or pick a device that you know uses basic attestation. That's all there's to it.
[Magisk] Jon8RFC:
Good to know about not needing to reapply it, thanks!

I had tried switching to a couple different models and it doesn't apply when I reboot. I'm just hoping to avoid disabling and reenabling the forced bacis attestation to get it switched. I'll PM a logcat to you of an attempt to change it, before rebooting.
[Magisk] Burt Squirtz:
this is probably a hilariously stupid question, but can this Magisk module spoof your device id? I'm trying to find something that can change your device ID on Android 11, and nothing's working.
[Magisk] Jon8RFC:
Interesting. The issue didn't occur in 5.3.4 or prior versions for me, since I was redoing force basic each time it was updated. It was in 5.3.5 when it set wrongly and now can't seem to be corrected as expected.
[Magisk] ipdev:
Yes. ;)

This module will allow you to add or change setting and properties.

Some are offered as an option and will adjust what needs to be adjustd.

Others you will need to manually adjust, change or add as you wish.

From the top.

MagiskHide Props Config GitHub - Link

If you are looking to pass SafetyNet on Android 11 due to Hardware attestation.

Force BASIC key attestation GitHub - Link

If you are looking to spoof a device fully.

Device simulation GitHub - Link

I just checked on a Pixel 4a, no problem with the update.

Using Pixel 3a XL to force basic.

Using a Poco X3 fingerprint to pass SafetyNet.

Only idea I have to offer is start again clean.

Run props and select r - Reset all options/settings and reboot.

Run props, select 2 - Force Basic key ...

Select the device you want to use to force basic. Do not reboot, just exit and reboot manually.

If you want to change the fingerprint first, run props again and use option 1, select the device (fingerprint) and then reboot.

Cheers all. :cowboy:
[Magisk] Didgeridoohan:
Something has happened with your settings file, which is probably why you're seeing issues. I can't be sure why things went wrong, since I'd likely have to see the logs from the time where you accidentally picked the Nexus 5 to be able to see that, but I'll do some testing later.

Meanwhile you can follow the advice by [MENTION=7280276]ipdev[/MENTION] and reset the module settings (r in the main menu), but you shouldn't actually have to reboot before activating "Force BASIC key attestation" again. That should get you back to running normally again.
[Magisk] Jon8RFC:
Yep, that fixed it. Thank you both!

I didn't reboot after resetting, and only rebooted after enabling force basic attestation again, which avoided me having to redo Google pay and various other inconveniences. Whew. Thank you!
[Magisk] Jon8RFC:
Nope, maybe it's the multipartion change that happened. I just unlocked the bootloader on a Pixel 3, wiped it, ran the factory image installer, switched partitions and ran it again, got magisk and root squared away, and installed busybox and magiskhide props config. Rebooted. Ran terminal emulator as su, chose option 2 and because it is a pixel 3, it automatically selected setting it as pixel 3 and said that's what it was. I didn't even go through the 'f' option to manually pick a fingerprint. Rebooted and it's set to nexus 5.
[Magisk] Didgeridoohan:
The value you see in that menu ("The currently loaded value") is what the prop is currently set to. Since you hadn't changed the value yet it is showing you the actual device model. If you then pick "Yes" to enable the feature the default value will be picked. And, the default value is just going to be the first old enough (but not too old) device from the list of devices in the fingerprint list (filtered on your OEM). In Google's case the Nexus 5.

What you're describing is exactly how the feature is meant to work.

I realise that I have some work to do when it comes to making the documentation/UI easier to understand though... :laugh:
[Magisk] ipdev:
Sorry, I misunderstood your prior post. :o

I thought you were trying to mimic (spoof) a different device.

The only way I know to change (regenerate) the ID (GSF ID and Android Device ID) is to factory reset the device.

Wish I had a better answer for you.

As for the Simulation mode.

There were issues awhile back that caused bootloops depending on the device and prop set.

The safe props were enabled by default when selecting Simulation mode.

The other props you have to manually select (or enable all).

A little safer since you could select the values depending on your device.

Cheers. :cowboy:
[Magisk] pndwal:
So for device ID change, could he simply backup (Android, or Titanium etc for complete user data), factory reset, then restore? PW
[Magisk] jcmm11:
There used to be just one Device ID for the entire phone but in recent (since O) Android versions the system stores a Device ID on a per app basis (per developer key to be exact). If you delete and reinstall an app it will get the same id back again. See https://android-developers.googleblog.com/2017/04/changes-to-device-identifiers-in.html

for more background.

There are apps out there that allow you to change Device ID. One that I tried, and appears to work, is https://play.google.com/store/apps/details?id=com.aksym.androiddeviceidchanger

There are others. One problem I have with this one is there's no search function and the app identities aren't in alphabetical order, but it does appear to work. (Root required).

Good luck.

That should work, but it's also more work.
[Magisk] TheUndertaker21:
Option 2 is powerful

Worked on note 20 ultra.

Too bad we can no longer use it with edxposed.

Hidden core is fake
[Magisk] qzan7:
Can the fingerprint for note 20 ultra be added?

Edit:

Sorry, i jumped the gun with this comment. Didn't read about how finger prints are added.

And how option 2 works.

Thanks.
[Magisk] Techguy777:
Im not the best with this build prop stuff. Is it possible to change my kernel and build date or build finger to match the security patch so I can use a kernel lower than my firmware on samsung?
[Magisk] zgfg:
Changes performed by MHPC are systemless, they take place only once the system is booted

- not at the time of flashing or loading a kernel
[Magisk] Techguy777:
Right I understand that. What Im trying to do Is I updated my S6 tablet to One UI 2.5 DBT which has September security patch I have an old custom permissive kernel with	2020-05-01 security patch its stock just permissive. I tried flashing it and it works fine boots into system but no wifi because the security dates. Is this module able to allow me to trick the system into wifi working?
[Magisk] zgfg:
All properly written modules are systemless.

You could try with the root app like:

https://play.google.com/store/apps/details?id=by4a.setedit22

Or by using setprop commands from Terminal or adb shell setprop from PC - and don't forget to reboot

However, all that won't work if your system is read-only (only the systemless approach will work there)
[Magisk] Techguy777:
Im not 100 percent sure but I nothing ever sticks when I use build prop editor or others. I can flash things in twrp. The new systemless root seems to have a lot of disadvantages. I liked when we could edit build prop or you could move apps to system app or private system and actually have them work. It seems like root is almost not full root access anymore. Now for 99 percent of stuff its not a problem but I miss the old system root. Ive never needed magisk hide and from the sounds of it thats pretty much done now to.
[Magisk] zgfg:
That does not depend on root method but on your Androud version and its filesystem.

If you root an old Android like MM or N with Magisk you would still have 'full root' access - that is, practically being able to change any file you want

On the read-only SAR P, Q, R, even root privilege is not enough to be able to change system files, because the system is read-only on the file system level - find more info in the Magisk GitHub Guide.

In that case Systemless root means that changes are saved somewhere to /data and mounted over the particular folders and files at the boot time (no 'full root' but the only way to make changes to the system, and Magisk provides the framework for)

System may even not be read-only but the system partition may have only a tens of KB of empty space left - as a result, AdAway will not have space to save the changed hosts file, and you would again have to use Systemless hosts.

No 'full root' (whatever that would mean) can help you there, only reformating and resizing partitions but that has obviously nothing with root=taking the root privileges in the running Android system

E.g., use a root explorer like MiXPlorer, go to /vendor/etc and find a file fstab.*

Open as text (you probably wouldn't have 'full root' access but don't attempt to edit/save changes) and take a look how the filesystems for partitions are defined.

Partitions with ro flag are read-only (probably your /vendor, /system, blocking your 'full root' access), rw read/write like /data, /cache, fileencryption= means that partition is encrypted (/data on newer Android versions, potentially causing a problem for TWRP to access)

Also, execute df in Terminal. On SAR (System As Root) you would not find /system under "mounted on" column but only Filesystem=/dev/root mounted on=/ and its Available or Use% column gives you info about the available and used space left (if 99% or 100% Use%, even if not read-only, AdAway would not be able to save changes to /system/etc/hosts)

Hope it gives some light to our frustrations why there is no more 'full root' but only systemless root on the newer devices
[Magisk] pippo45454:
Could I ask you to add fingerprints for Xiaomi note 9 pro European? 11.0.4.0 QJZEUXM.

I cannot use fingerprint with banks app.

Could you help me?

Any suggestion?
[Magisk] zgfg:
Sorry but can you please elaborate:

>> I cannot use fingerprint with banks app

Is this about the device fingerprint (kind of a device signature) or about authenticating to the app by a finger

Fingerprint for a device can be only submitted by somebody with that particular device and firmware:

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

Without such help from users/community, developer cannot add the fingerprints for devices he does not have
[Magisk] Didgeridoohan:
You mean the Redmi Note 9 Pro? It'll be under the Redmi menu, and I already have the global version of that device fingerprint on the list. If you really want the European version:

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

But, changing the device fingerprint is only for passing CTS on custom ROMs (or otherwise not certified devices). Does CTS fail on your device and does your bank app really use that for the fingerprint scanner (which I'm assuming you're talking about, otherwise you need to be more detailed)?