yashsingh1/xdaforums huggingface dataset:
[Magisk] scootley:
I can report that OTA updates work on a Pixel 5 configured to act like a Pixel 3a.

Specifically updating from the Nov 2020 to Dec 2020 security update.

Of course I restored the factory boot image before applying the OTA (edit: see below it was before rebooting but actually after install).

I guess it should be noted that my device downloaded a "full" OTA and not an incremental one, though.

Yes the OTA notification screen said: "Improve the security of your device (Pixel 3a)", but I double-checked before applying the update that it matched the sha256 hash for the Pixel 5, so that text is obviously not connected to the downloaded OTA file.

Edit: I also found it weird that the OTA update seems to have actually fully applied itself and was just waiting for a reboot. I didn't think that was supposed to happen with the Developer setting for "Automatic system updates" turned off. I thought it would only notify but never actually apply the update before the user asks it to. And shouldn't that process have failed since I was rooted at the time it seems to have applied itself? Maybe full OTAs behave differently than incremental ones in this regard because they don't need to check for integrity of existing partition images since they are going to be fully overwritten and not have deltas applied to them as they are updated onto the inactive A/B slot. But still, what's up with installing without asking?
[Magisk] pndwal:
... Seems this may now only be part of the more elegant fix for many. And the other vital part?...

MHPC? Who would have thought?!...

But that's what happens when experts collaborate! 👍

https://github.com/kdrag0n/safetynet-fix/issues/1

What an inconvenience to require 2 modules for SafetyNet... .. . Most will probably just give up now. 😁

... But seriously, many with issues will want to try the elegant new USN/MHPCF (wow!)...

Reports in USNF thread already indicate teething/device compatibility issues are diminishing rapidly. PW
[Magisk] der_Kief:
@Didgeridoohan

here is the fingerprint for Xiaomi Mi 10T Lite

Its from V12.0.8.0.QJSEUXM EEA version

Hopefully this is added asap :)
[Magisk] Didgeridoohan:
@scootley Thanks for the report. Unfortunately I cannot give any insight into why an update seemed to have installed itself even with "Automatic system updates" turned off.
[Magisk] Didgeridoohan:
Thanks. What's the corresponding security patch date?
[Magisk] der_Kief:
It's 12/2020
[Magisk] TBolley:
any way to get fingerprint with bank apps working ? s9 Android 10 (Alexis Rom 2.3)

Magisk 21.3

MagiskHide Props Config 5.4.0

Universal Safety Net Fix 1.1.1
[Magisk] Didgeridoohan:
Depends... What is it that causes it? Magisk? MagiskHide Props Config? Universal SafetyNet Fix? A combination? Something else?
[Magisk] badral07:
Please add support on Rog Phone 3. Thank you.
[Magisk] paolocorpo:
DEar Developer,

I am back again ;)

I started a new job and I have received a new smartphone ( Samsung A71)

As you can imagine I cannot root it

I have an app (Minimed Mobile) tha I am using to verify continuosly my diabet

Unfortunately the list of smartphone usable is very short (:() and the Samsung A71 is not included

I fixed some weeks ago the problem with my Xiaomi Mi A1 using your module and forcing it as Pixel 3 (accepted by app)

THE QUESTION:

Is there any possibility to apply your module on a smartohone not rooted ?? o_O

Paolo
[Magisk] badral07:
asus/WW_I003D/ASUS_I003_1:10/QKQ1.200419.002/17.0823.2012.122-0:user/release-keys

Dec 1
[Magisk] TBolley:
Safetynet was pass but for bank apps no fingerprint works anymore, Magisk / Props and Fix installed
[Magisk] zgfg:
Not, MHPC is Magisk module and it requires Magisk framework to run

Even if you would have an old phone with the old SuperSU root, it would not work with

Also, without root, no chance to edit/change ro.* (read only) props
[Magisk] Didgeridoohan:
Yes, I got that. My question is what it is that causes it. Does it manifest by just installing Magisk, or any of the modules? You've got to give some more info...
[Magisk] OhioYJ:
@Didgeridoohan, I just swapped to a OnePlus 8T, Magisk 21.2, Lineage 18.1, Build 5.4.0 presents the error below (not sure if anything else would be helpful, let me know). The previous version (5.3.6) works fine.

https://www.cdmfabrication.com/bbpics2/os/propsconfig1.jpg
[Magisk] Didgeridoohan:
I guess you installed the zip from the OP rather than downloading and installing directly from the Manager. There was a small error in the zip. Fixed now and new one uploaded.

Oopsie...
[Magisk] zgfg:
Maybe you should consider to rewrite 👍
[Magisk] BlueMan_86:
I have Mi 10T pro EEA EUROPE, it worked fine, when I select MI 10T EEA EUROPE, but now it is showing evalType is hardware, and ctsProfile fails... Please help... I set 1 option and it fails, than i set 2nd option, device simulation and I enable S (device simulation) it stills fail.. What can I do?
[Magisk] Didgeridoohan:
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
[Magisk] 2spuki:
can someone tell me how to get this into the fingerprint list? this is for the Galaxy A71
[Magisk] Didgeridoohan:
The best option is to post it on this thread and then I'll test it and include it in the next update. So you're good they're...

If you want to start using it immediately you can just place the file in the root of your internal storage and rename it to "printslist" (just like that, no extension). That way the print will show up in the prints list in the module, under "Custom".

https://github.com/Magisk-Modules-R...lob/master/README.md#custom-fingerprints-list
[Magisk] zfk110:
Master, can you look into this log to see why its failing CTS Thanks
[Magisk] zgfg:
For the new CTS issue (as of few days ago, thanks to Google), are you using the new Magisk module Universal SafetyNet Fix?

If not, scroll back, there was a lot of ink last days about here, you will find the posts about and in one of them the link to the new XDA thread opened by the developer of that module, there you will find the link to install the module, etc
[Magisk] j1gga84:
Anybody has an idea why my device status in google Play Store still is uncertified allthough i pass SafetyNet Check completely?

Is there anything I can do to get my device certified again?

I installed Universal SafetyNet Fix, Avoiding hardware evalType and latest MagiskHide Props Config modules.

When using MagiskHide Props Config and changing the G960F fingerprint from Android 10 to android 8.0.0, like in the fingerprint list, the line for the certification status in playstore disappeared, any ideas?

regards
[Magisk] ipdev:
Once SafetyNet is passing, clear the cache and storage for the PlayStore app.

Note:

You may only have to clear cache.

When you clear storage you will also clear updates to PlayStore.

May take a reboot or a little time for Play Certification to show at all.

The certification will not show up until Google determines if your device is certified or not.

Cheers. :cowboy:
[Magisk] zfk110:
Couldn't install it
[Magisk] Wolfcity:
If you look at the error message you'll see the problem: Your device is 32bit and the module is for 64bit devices.

Check out on GitHub if there's a fix for 32bit (armeabi v7a) and naturally for the android version you're running.

GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk

Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix

github.com
[Magisk] ipdev:
I am not a Sammy guy but, I had to take a look after seeing your error.

SafetyNet is showing as Hardware Attestation ?

Do you have a Samsung Galaxy Tab A (gta3xlwifi) SM-T510 ?

A 2019 Samsung device (released with Android 9), that is only arm?

Do you have a Samsung Galaxy Note 8 (greatlte) SM-N950F ?

A 2017 Samsung device (released with Android 7.x), that is only arm?

From the log you posted.

[ro.product.cpu.abi]: [armeabi-v7a]

[ro.product.cpu.abi2]: [armeabi]

[ro.product.cpu.abilist]: [armeabi-v7a,armeabi]

[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]

[ro.product.cpu.abilist64]: []

I assumed everything released in the last three/four years would be 64 bit.

The bits and pieces I could find searching, it looks likes both the Tab A and Note 8 use 64 bit chips, not sure why it is only supporting 32 bit.

¯\_(ツ)_/¯

--

I assume you are spoofing a device, or at least using a different fingerprint.

Is this causing SafetyNet to switch from basic to hardware attestation when you check ?

If you are forced to hardware attestation on a stock arm device, then you would need to ask for help in the Universal SafetyNet Fix thread or create an issue on the Universal SafetyNet Fix GitHub.

Universal SafetyNet Fix xda thread - Link

Universal SafetyNet Fix GitHub - Link

Cheers. :cowboy:
[Magisk] dr4go:
Check out the following fork: https://github.com/wulan17/safetynet-fix
[Magisk] RenVilo:
So.. I installed a fresh Rom (Alex), updated Magisk and it failed both with eval Hardware. I enabled Hide and it passed but basic but failed cts. All apps working with fingerprint bit gpay and google not certify is showing.

Installed the safetynet fix 1.1.0 and passed cts bit several apps doesnt work with fingerprint. Removed safetynet fix and now fingerprint works again but both basic and cts fails. Installed fix 1.1.1 and sadetynet keeps failing on both. Tried the props fingerprint setup but no change. I would like to set it up to pass again but dont want to reinstall the rom again. Any ideas?

It is a note 9.
[Magisk] Iustin_Theft-07:
Android 5.1 AOSP-like rom. I get this screen while running 'props' in Terminal Emulator. I have the latest module in the magisk repo as of 18/12/2021. Phone passes basicintegrity but not ctsprofile.

I have tried changing the boot scrip time thing and background scripts to enabled. No result with any combination.

Here are the logs automatically saved to my internal storage. Taken after fresh module install.. https://drive.google.com/file/d/1wGtDyfC54XcPS04lvihZEyFt1Z5sBs0I/view?usp=drivesdk

Can I fix this or is this phone doomed ?
[Magisk] j1gga84:
When I apply the fingerprint for my device (Samsung Galaxy S9 - G960F) on a Samsung based android 10 stock ROM the phone info says N950F after applying the fingerprint for G960F (Android 8.0.0).

Any idea?

Regards
[Magisk] Didgeridoohan:
Fingerprint authentication failing to work seems to be a recurring issue when using the SafetyNet Fix module. No idea if there's any way around it, but if there is that info would be found in the modules own thread: https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/

Try toggling MagiskHide off and on again to get basic integrity to pass, but you will currently not be able to pass CTS without the SafetyNet Fix module.
[Magisk] Didgeridoohan:
Like it says in the error message: try disabling other modules.

In the log it looks like the late_start service mode stops running after Aunir Narsil runs it's service.sh script (and MagiskHide Props Config is after that module in the execution queue), so that is a very likely suspect.
[Magisk] Didgeridoohan:
No idea... Would need to see your logs to be able to say anything.

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs
[Magisk] Didgeridoohan:
If you've got problems with the SafetyNet Fix module it's better if you report these in the modules own thread:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
[Magisk] RenVilo:
Yea I like to have Gpay as a backup and then I have 1 card that's just a virtual card so my idea was to mainly use the phone without the Fix and IF I need to use gpay I simply install the SafetyNet fix and restart, scan and then I can just remove it after. But somewhere something got screwed up. So I tried going into a terminal again with "su" and it now says it can't find it. I then open Android ID Editor and it also says device isn't rooted... So I just used Odin again to flash. Seems I can grant Superuser access again but still doesn't even pass Basic. Seems like I have to redo my phone again :( Wish I can unroot my phone lol. Only rooted it to try and get my stupid whatsapp messages back which seems is pointless considering everyone is starting to jump elsewhere lol
[Magisk] Hemudon:
But Bro it doesnt let me make a google backup it says couldnt make backup try again later

my device poco f1 ( beryllium)

using awaken os

didnt changed anything everything stock

it problem with me on every rom our

they dont let me backup

i try to change rom

tried another account

no luck

actually its random , on paranoid android it worked out of the box on pe i fixed by magisk hide props( i just flashed your module nothing touched) it fixed

but it never fixed like that on any other rom idk why
[Magisk] Didgeridoohan:
First: not your bro... (probably showing my age here :ROFLMAO: )

Second, I'm honestly not following what it is you're trying to say. Are you asking for help with something?
[Magisk] Hemudon:
yeah I am asking help, Sir
[Magisk] Didgeridoohan:
But with what? Details please...

Edit: I get you're trying to activate backups, but exactly what is it that you need help with?
[Magisk] Hemudon:
Device is Poco f1 ( beryllium)

Im on android 11 custom aosp rom (Awaken OS)

my google backup is broken ( because of props ig)

on my phone every rom spoof another pixel to get pass safety net

it never broken on android 10 roms

It says Couldnt backup try again later
[Magisk] Hemudon:
One time on one rom (Pixel experience ) i flashed your module magisk hide props

and bam backup starts working

but it never worked again like that for me

can give you logs but rom dev said its server problem

(ig they are right as props spoofing wont let connect to backup servers)

theres a force bacup method

but it says transport error
[Magisk] Didgeridoohan:
If you need to edit more props to spoof a different device (to enable backups) you can pick a device fingerprint and then enable "device simulation" (and activate the props you need), or you can use the "Add/edit custom props" option to add the props you need.
[Magisk] Didgeridoohan:
If spoofing props doesn't work there's nothing I can do.

Just flashing this module without setting it up in any way does absolutely nothing. That must have been a coincident.
[Magisk] Hemudon:
Yeah nothing worked , ig its google side of issue as only some random people face it.

Still thanks for your time sir
[Magisk] zgfg:
If I recall correctly, there was a thread here on XDA (also under some general topics like Magisk - i.e. not for some specific device) about the intermittent issues with G backup, and with some 'method' how to fix it.

I've seen that, but TG I never needed to experiment with.

You could try googling for, on XDA Web there is also a search for posts and threads
[Magisk] Didgeridoohan:
Fingerprints list updated to v114

Stressed out of my head and got a 1000 things to do, so what better time to spend testing some new prints and updating the included list of fingerprints?

Thank you to @Sid220, @der_Kief, @badral07 and @2spuki for providing the fingerprints.

The list will update when you run the props command, or if you've disabled automatic updates by using the -f flag or from the "Edit device fingerprint" menu.

New

Asus ROG Phone 3

Samsung Galaxy A71

Xiaomi Mi 10T Lite Europe

Updated

Xiaomi Pocophone F1
[Magisk] Hemudon:
They doesnt work

Bmgr backupnow --all gives transport error

Bmgr backupnow appdata gives package not found error
[Magisk] Iustin_Theft-07:
Thank you for replying. I did disable every module but magiskhideprops before but it didn't have any effect. I apologise for not saying this. Also, just realized every boot, the boot stage defaults back to system.prop instead to what I set it to (late, post..) also, I get those weird lines in terminal emulator when navigating the options...
[Magisk] Didgeridoohan:
Then I need to see new logs where you've disabled the other modules and also where you've tried changing the boot stage.
[Magisk] zgfg:
Try asking there, if OP or users could give you help
[Magisk] Iustin_Theft-07:
Logs https://drive.google.com/file/d/1VwYIlvRR8YV_UD3f35U8ODruLt9wjeBV/view?usp=drivesdk Checked now, boot stages work only with busybox module installed. If I remove it, changes don't stick. Installing another busybox, or not having any busybox results in changes not sticking. Maybe it's impossible for this phone idk thanks anyway
[Magisk] ShaDisNX255:
I went back to version 5.3.6 because as I see from your changelog, you removed forcing basic key attestation because it no longer works.

I gave 5.4 a shot, along with the "Universal SafetyNet fix" but unfortunately, that fix breaks a few things in Samsung's OneUI including Secure Folder after it's been fixed

With 5.3.6, I downloaded A51 fingerprint (I'm using an A71) and forcing basic key attestation, it seems that it still works, so I'll keep using this until it no longer works I guess

Btw, I'm using Magisk Manager's SafetyNet check, and I downloaded another SafetyNet checker on Playstore to make sure it works. Are these outdated and there's a new type of SafetyNet checker? I'm asking because according to both of them, I'm passing.
[Magisk] Didgeridoohan:
@ShaDisNX255

So if you check SafetyNet in the Manager, with "Force BASIC key attestation"

disabled

and no SafetyNet Fix module, you get evalType=HARDWARE and fail CTS? And if you enable the feature you get BASIC and pass CTS?
[Magisk] Didgeridoohan:
I've taken a look at these additional logs, and can't say at a first glance what's wrong. This time the service.sh script executes, but doesn't finish. And the fact that you also need to install busybox to make the module work means that there are more issues. The module uses Magisk's internal busybox (and this is also apparent in the log), but maybe the alias command fails.

And that should definitely not matter in the boot scripts since it's Magisk itself that executes them and all command should be available. We could of course that this by you editing the util_functions.sh file on the module directory.

Edit /data/adb/modules/MagiskHidePropsConf/common/util_functions.sh and change line 16 from

if [ -z "$INSTFN" ] && [ "$BOOTSTAGE" != "post" -a "$BOOTSTAGE" != "late" ]; then

to

if [ -z "$INSTFN" ] && [ "$BOOTSTAGE" != "post" ]; then

I doubt it'll make a difference, but stranger things have happened...
[Magisk] ShaDisNX255:
I went ahead and disabled everything and returned to original fingerprint because I don't want to give you false information. Here are my results:

Original fingerprint, force basic key attestation off:

Attestation failed

basicIntegrity ✓

ctsProfile X

evalType: HARDWARE

Original fingerprint, force basic key attestation on (which changes model to SM-A300FU)

Attestation success

basicIntegrity ✓

ctsProfile ✓

evalType BASIC

Force basic key attestation, A51 fingerprint and device simulation (all turned on)

Attestation success

basicIntegrity ✓

ctsProfile ✓

evalType BASIC

Also, my model is now SM-A515F

Force basic key attestation, A71 fingerprint downloaded from module and device simulation (all turned on)

Attestation failed

basicIntegrity ✓

ctsProfile X

evalType: HARDWARE

Model is now SM-A715F
[Magisk] Iustin_Theft-07:
Did what you suggested, still no change. I can't get them to work. Thank you anyway mate )
[Magisk] Mnjrvndr:
Hi. Being using Samsung Galaxy S9 with Resurrection Remix 8.6.5, I've successfully set my fingerprint to Motorolla device and enabled all 10 prop strings. The problem is when I'm scanning network with Fing, I can still see the name of my device. What can I do about that?

Also, with this Motorolla fp my earphones microphone doesn't work.

Also, when I changed fp from Motorolla to Nvidia device, I couldn't boot into ui, and even button combination to boot into recovery didn't work. What I did was pressing and holding all buttons at once and catching moment when Rom booting logo disappeared and quickly pressing combination for recovery so I could delete module.
[Magisk] zfk110:
hardwareoff_1.1 (2).zip

SafetyNet is showing as Hardware Attestation ?

It was but I flashed hardwareoff_1.1.zip which it changed the Hardware Attestation to Basic

at that point I flashed fingerprint and that might change it to SM-N950F, Yea its 64 bit.
[Magisk] Didgeridoohan:
@ShaDisNX255 Ok, so the model props trick still seems to work for you. Which is bound to happen and expected... There's always going to be exceptions, major and minor, in the Android ecosystem.

I somewhat foresaw this and didn't actually remove the "Force BASIC key attestation" feature from the module, it's just gone from the menu settings file but everything's still there in the code. Just in case Google flip things again...

But, for now at least, I'm not bringing the feature back. From that we've seen the majority of reports are that users need the new fix and that the model prop change no longer works. Users that still can change the model prop to force basic attestation have the option of using the keystore fix, hardwareoff, the previous release of MHPC or simply use "Device simulation" or "Add/edit custom props" in MHPC to change the model props. At the moment that should be more than enough options to cover most use cases/users.
[Magisk] Didgeridoohan:
There are usually tons of different props that contain the same information on your device. So there's a good chance there's still one in there with the device name. You can check by using the getprop command in a terminal. Example:

getprop | grep "S9"

This will check all props and filter out those that contain "S9". You can change the filter to your liking...

Once (if) you've found the remaining props you would like to change you can then use the "Add/edit custom props" option to change those.
[Magisk] Didgeridoohan:
Too bad we couldn't get any further. Unfortunately those old mediatek devices often are more than a little finicky when it comes to Magisk and modding.
[Magisk] zgfg:
Maybe you could enable the feature again but by renaming it to avoid misunderstanding and false hopes.

That you call it like Change device model or something in line with the option for changing device fingerprint
[Magisk] Didgeridoohan:
If there are enough reports for it being wanted/needed I might (I might do it anyway). But for now I'm just waiting and seeing how things with Google's CTS shenanigans progress...
[Magisk] Didgeridoohan:
Looking at that screenshot again there's an "Edit" button next to the device name. That makes me think this is a cached value that is saved the first time the app sees the device. You could test this by clearing data for the app, and then open it up again with all the Motorola props still set. If the app still detects the device as a Samsung Galaxy S9, go with my previous suggestion with the getprop command. If it now sees your device fully as a Moto, you're good.

I didn't address this the last time, but it is very possible to experience major issues when using the "Device simulation" option. Fortunately there are multiple ways of getting out of these issues, like a non-booting device: https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module
[Magisk] elgsantos:
Hi, I'd like to contribute too, I could not find for Galaxy M31 so there you go mine (non-rooted, safetynet passing):

$ getprop ro.build.fingerprint
samsung/m31nnxx/m31:10/QP1A.190711.020/M315FXXU1ATG4:user/release-keys
$ getprop ro.build.version.security_patch
2020-07-01
$ getprop ro.product.manufacturer
samsung
$ getprop ro.product.model
SM-M315F
$ getprop ro.product.name
m31nnxx

This model uses hardware attestation, and fails if firmware is modified. Idk if it passes in other rooted devices. Btw thanks for your module!