yashsingh1/xdaforums huggingface dataset:
[Magisk] ipdev:
Hi. :)

Magisk v23 should be fine.

I normally use the patch boot method on newer devices.

Magisk [Install] - GitHub.io - Patching Images - Link

Custom ROM(s) use a certified OEM build fingerprint when building.

If the fingerprint does not match the security date used, you will need to adjust the security date to match.

MagiskHide Props Config - SafetyNet, prop edits, and more - v6.0.1 xdaThread - Link​

A bit confused on mine since SafetyNet shows basic with or without the USNF module.

Regardless, it was needed to pass CTS on OEM (MIUI) rom.

Universal SafetyNet Fix 1.1.0 xdaThread - Link​

Some custom ROMs include USNF and is the preferred way.

kdrag0n [safetynet-fix] - GitHub - ROM integration - Link​

If needed, you might want to suggest to the OneOS maintainer/dev to include USNF in the build.

---

There are a few ways change ro.product.model.

This exploit was only temporary the last time.

Who knows how long it will last this time. ;)​

Manually using the Magisk resetprop command or..

You can use MHPC (MagiskHide Props Config) module to set it.

See link above.

osm0sis recently made a module to change it.

Post 47,566 - Link

Displax found this exploit originally, and has a module to set it.

Post 40,651 - Link

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
[Magisk] TheKerevas:
Thanks for the very long explanation. I put the Alpha of vvb2060 and am trying to replicate your method but I can't... I am stuck about the version of Universal SafetyNet Fix to put and a working method to change "ro.product.model". Until now I have used Universal SafetyNet Fix 1.2.0 Mod and changed the value from the module itself by putting my model but on reboot I have bootloop, changed the value even after installing it from the module itself and I have bootloop again. From how you described what I have to do to change it, I definitely have the wrong method, which one of these do you recommend to change the "ro.product.model" safely?

It doesn't just pass "cts Profile", evalType tells me it's BASIC

P.S OneOS is based xiaomi.eu, I don't know if they have already integrated USNF and they don't change anything of the xiaomi.eu base

UPDATE: In the end, I succeeded. I installed SafetyNet 1.2.0 Fix Mod, then MagiskHide Props Config putting fingerprint F2 Pro A11 and "ro.product.model" F2 Pro. For now your method works well, who knows how long it lasts x'D
[Magisk] pndwal:
As I said, seems it hasn't been uploaded yet. That's not unusual; there has sometimes been a delay of several days in the past... Perhaps for private testing? PW
[Magisk] HippoMan:
Actually, someone else has already picked this up. Check back over the last several pages of messages here.
[Magisk] pndwal:
Early release (paid) @kdrag0n USNF 2.0.0 is Android 12 compatible, and fixes latest ctsProfile failures due to recent Google server end changes for many (on earlier Android too). 😉 PW
[Magisk] pndwal:
If you had a previous satisfactory SafetyNet Fix working (there are several modified versions for various Sammy models), go back to that and try latest MagiskHide Props Config module; Force Basic attestation, Set a custom value option, and choose a closely related, preferably newer Sammy model to spoof...

This used to restore most OEM specific features and compatibility. 👍

See my post above also. 🙂 PW
[Magisk] pndwal:
Yup, devices that never needed fixes to force fallback to basic attestation before January and always did report Basic evalType, eg my Mi Pad 4, suddenly needed USNF after the January Google change in addition to those previously reporting Hardware evalType.

Here is the reason:

https://github.com/kdrag0n/safetynet-fix#universal-safetynet-fix

So it may be that Google is being sneeky, but evidently John's evalType has simply no longer detected all instances of Hardware based attestation correctly since January (after all it was developed before the January changes and did reliably detect Hardware attestation in use till then), and devices returning 'Basic' evalType are actually using Hardware "under-the-hood" attestation.

Evidently, latest server end changes detecting ctsProfile issues are also occuring "under-the-hood", at least as far as inbuilt Magisk Check SafetyNet evalType component in is concerned. 😜 PW
[Magisk] sergej_7:
yeah i saw it here https://t.me/proton_projects but I thougt maybe there is a solution that has not to be paid for
[Magisk] pndwal:
Actually, USNF module 1.2.0 is compatible with Android versions 8–12 Beta 2; Just don't know about mileage w/ official Android 12, which is what you asked. 😜

https://github.com/kdrag0n/safetynet-fix#universal-safetynet-fix

Guess USNF 2.0.0 may be free later too, if you can wait! At present you're paying for 'early release'. 😛 PW
[Magisk] MoL_82:
This works! Thank you!

(Including a working backup :) )
[Magisk] c3k:
wich samsung model have you set? (and wich device you have?)

before USNF (almost a year ago), I've used MagiskHide Props Config with Samsung A3 model to pass SafetyNet on a S10, I'm wondering if I can use samething more recent (now I'm on S21).

thanks
[Magisk] c3k:
safetynet-fix-v2.1.0.zip is out (paid, need riru core) and i'm passing SafetyNet again on S21
[Magisk] pndwal:
Interestingly this may be a more universal fix for latest Google changes / ctsProfile failures as well as a proper (complete?) MagiskHide replacement:

Universal SafetyNet Fix · 2.1.0​

Changes since 2.0.0​

Fixed new SafetyNet CTS profile failures as of September 2, 2021

Added MagiskHide features that will be removed in future versions of Magisk

Download​

This version is currently only available to early access supporters...

It'll also be interesting if this can fix [Seems this still won't fix] ctsProfile failures for ROMs w/ prebuilt utils that manipulate props like Pixel Experience. [See following post]

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

😛 PW
[Magisk] howpathetic:
Nope, I have Xiaomi mix 2s with Pixel Experience v11(Plus) and with v2.1.0 still ctsProfile is failing
[Magisk] pndwal:
Notice:

Universal SafetyNet Fix · 2.0.0​

This release is now public on GitHub!

Changes since 1.2.0​

Added support for heavy OEM skins (One UI, MIUI, etc.)

Added support for Android 12 Beta 4 and future versions

Fixed broken Play Services features other than SafetyNet

Fixed rare system freezes caused by Play Services breakage

Android 12: Fixed face unlock on Pixel 4 series

Added support for Android 7.0 and 7.1

Rewritten as a Riru module

Download​

This release is now public on GitHub.
[Magisk] jons99:
use the safetynet fix 2.0 from above works for me on beta 4.1
[Magisk] pleasetouchmenot:
On MIUI, using @Didgeridoohan 's MagiskHideProps Config alongside with Universal SafetynetFix by @kdrag0n , just use only Force Basic Key Attestation feature on HideProps Config module, and cts will passed.. It don't need a custom fingerprint.
[Magisk] charlessxavier:
Which one should I choose under force basic key attestation feature?
[Magisk] pndwal:
Nb. The mechanism here is a model prop change which causes a mismatch triggering fallback to basic attestation.

Since you must effectively spoof a different model to cause the mismatch / fallback, use Set a custom value option and choose a closely related model, preferably newer from same OEM to spoof...

This used to (should still) retain most OEM / device specific features and compatibility.

🤠 PW
[Magisk] Chandru123:
Should I move to the alpha version of the Magisk now. I have succeeded my attestation by installing mod from @Displax. So far it works with basic. Is this a right time to move, or still we can use v23 until magisk hide is removed. Any thoughts.
[Magisk] conmaxanhle:
USNF 2.1.0 not working on Poco F2 Pro ( lmi) Sparks OS. Follow the #safetynetfail guide in the group, re-do 3 times. CTS profile not match. Change from Cherish OS to Sparks OS to test again. Not working. Im gonna stick to TeamFile method for custom rom. Damn wasting money and time. Maybe if i go back to MIUI then USNF may useful.

P/s: Have receive refund
[Magisk] Detonatte:
For Samsung Galaxy Note 9 with Android 10?
[Magisk] dcarvil:
There is no "correct" answer to that question. It is just a matter of opinion, and everyone has their own opinion. My opinion is I am going to stay on v23 until it no longer works. I see no reason to try to fix something that is not broken.
[Magisk] Cypherous2:
So, seeing as the Xperia 1 III seems to be doing HW attestation in the background regardless of safetynet defaulting to basic, is there a way to bypass this so that stuff actually works and to prevent apps from actually seeing the phone is rooted as magisk isn't doing it
[Magisk] martyfender:
According to your log, dm_verity is not disabled.
[Magisk] pndwal:
Since the Alpha fork includes all John's upstream changes as well as @vvb2060's experimental ones (For example, latest uploaded Alpha build includes scores of new commits incl. John's to Aug 30. Current TJW builds have no fixes since mid May) it will improve compatibility for some devices but is otherwise really only for those wanting to try these changes early / be on the 'bleeding edge' / understand and appraise changes and Magisk's direction (how things will work) going forward.

Others will want to take the 'If it ain't broke don't fix it' approach. PW
[Magisk] dnsmo:
is Magisk gona work on Pixel 6?
[Magisk] pndwal:
This 'seeming' anomaly has actually been occurring with most devices new enough to support Hardware TEE attestation since January this year, and I'm only just starting to understand it fully! See my

New Conclusions

Nb. As always, I may be way off in some aspects! 😜

Hardware attestation is actually occurring and I now believe evalType would reflect this if a 'Basic' result hadn't already been triggered to reflect a fallback for an altogether different component (or components) of Hardware attestation.

Before January methods were devised to cause Hardware based attestation to fall back to Basic (non-hardware based) attestation (ie. cause-model_prop-mismatch to trigger this) and evalType evidently reported such attestation accurately both before and after fallback.

With Google's server end changes in January however, newer Hardware based checks that are not made to fall back to Basic via the same methods were introduced, and these surprised many since the evalType response of Magisk's Check SafetyNet was already Basic due to the early fix.

A new fix (Universal SafetyNet Fix module) soon became available, and, since old cause-model_prop-mismatch methods seemed no longer to have any effect (perhaps older Hardware attestation used was turned off by Google, or perhaps the new fix handled these also), these were disabled by most.

Notably, evalType continued to show Basic, and this supports my conclusion that evalType = Basic can be triggered by unrelated mechanisms causing fallback to Basic attestation.

At the time, the USNF dev @kdrag0n described the new components as occuring "under the hood" evidently because Magisk evalType was already reporting Basic when these failures began.

Now, with new September server end changes, it seems that either the older Hardware attestation components have been reintroduced or new ones also circumvented by the old cause-model_prop-mismatch method, and these have again caught us by surprise for the same reason; evalType is already reporting Basic for most.

The Rub (My Conclusion)

It now appears that the anomaly w/ evalType occurs because because it reports Basic when only one of a number of components of Hardware based attestation is made to fall back to Basic, ie we get 'Basic' if any component falls back to Basic attestation even when others are using Hardware.

This led Danny to describe the new Hardware attestation components as occuring "under the hood" as stated, but now seems to really be a consequence of the fact that a trigger for fallback to Basic affecting altogether different Hardware attestation component(s) was already set (or pulled). 🤪

Any of the fixes that result in ctsProfile ✓ are real bypasses for SafetyNet API, and current Magisk w/ MagiskHide enabled is still doing much of the heavy lifting.

This will change with next release, but may already be largely addressed by latest USNF module (2.1.0) as well as additional MHPC module where uncertified ROMs / devices are used.

Nb. Many Bank apps are using additional (Momo and other) custom detection methods aside from calling SafetyNet API.

🤠 PW
[Magisk] pndwal:
Y

Yu

Yup

Yup!

Yup!!!!!!

PW
[Magisk] dnsmo:
well then, first thing when I get the pixel 6 pro will be -oem unlock
[Magisk] pndwal:
Note that days for SafetyNet attestation bypassing (Google Pay w/ root, etc) are likely limited however, but ball is in Google's court.

Devs have been hitting it back till now, but expect Game Over at any tick of the clock. 😜 PW
[Magisk] AJHutchinson:
Hey where do I get this module from @Displax ? I don't mind paying just can't find it anywhere 🤷‍♂️😂
[Magisk] jons99:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/page-2375#post-85573473
[Magisk] AJHutchinson:
It's technically for magisk isn't it ? Cheers for being a douche though 😂
[Magisk] Didgeridoohan:
Douche? He linked you the module you asked for... :(
[Magisk] AJHutchinson:
Oh I thought he was giving me the rules of the thread my apologies @jons99 I guess I'm the douche sorry buddy 😞
[Magisk] Cypherous2:
So is there anything we can do regarding those specific checks?

Not being able to use GPay or my banks app are not really "deal breakers" but i need to know if its even worth trying to keep on top of them or if these checks are likely to be something we are just going to have to live with
[Magisk] pndwal:
Banks have been doing this for some time now, and different security measures seem to be increasing particularly as Google's SafetyNet API can be easily thwarted, especially with root, making this attestation to Trusted Execution Environment (for running their code) seriously flawed.

Recent efforts to detect isolated processes that reveal device tampering can be found by searching recent posts here, and there are several Magisk modules (also discussed recently) to help hiding these.

Other (older) methods used by banks etc are discussed here:

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot#

Sooner or later I believe these 'custom' efforts to detect 'root' will cease, being replaced by a reliable SafetyNet API from Google when they finally flip the switch and turn on Hardware TEE attestation across the board. This is already years in the making, but there has been a need to wait for saturation (Hardware components to come to a sufficient number of devices) and for vendors to fix bad implementations of it (like OnePlus). It is assumed by most that Hardware TEE will eventually be impervious to efforts to bypass it such as the fallback to basic attestation that can be achieved at present.

Nb. Google seems to be playing catch-up with Apple who's mobile platform is perceived as far more secure / impenetrable, causing many corporate, government, security industry and other players to issue iPhones and / or forbid employees to use Android devices for work. Their need is to protect their bottom line.

I hope this small insight helps some understand the game banks etc are playing while they wait for Hardware TEE implementation.

Of course, as custom modders we can play the game too, while it lasts, but no-one says we must! PW
[Magisk] Zanglus:
Fixed CTSProfile and Gpay with the LSposed method, but GPS not working and some problem with Google Backup.

Any advise ?
[Magisk] lottarake:
Uncheck "get location" from the xprivacylua restrictions, then clear cache and data and GPS will work again.
[Magisk] Zanglus:
I tried, but fix wrong coordinates
[Magisk] lottarake:
Needs to be unchecked from Google play services as well. Clear data and cache from both apps and try again.
[Magisk] Zanglus:
Thank you so much, now GPS is working
[Magisk] nowster:
Welcome to Null Island.
[Magisk] wtosta:
HI Guys,

By pure coincidence, I managed to make Google Pay contactless payments work on a rooted Samsung S9 and S10e phones. AlexisROM 3.0 for S9 and Ambasadii ROM 4.6 for S10e are installed on the phones. Also installed custom White Wolf and Thunderstorm kernels, though it probably doesn't matter for this case. From the very beginning Magisk SafetyNet check with BASIC eval-type was going to pass, but contactless payments in Google Pay did not work, although the payments cards were correctly allowed to register by the bank in Google Pay app. But after turning on the NFC module to make a payment on the payment terminal, the Google Pay application said that the NFC module was not configured.

I did as follows...

Magisk 23.0 is installed. Magisk hide was turned on and I loaded in order:

1. Riru. Phone restart

2. SafetyNet Fix shim-mod. Phone restart.

3. SafetyNet Fix 2.1.0 installed immediately (this one is paid for now), but maybe on 2.0.0 from GitHub it will work as well - I did not try. After restarting the phone SafetyNet check passes in Magisk and the contactless payment also works. The rest of the applications like fingerprint, GPS, Galaxy Store are working correctly. I did not notice any anomalies.

Maybe someone will find it useful.

Best regards,
[Magisk] kost7:
How about Google backup?
[Magisk] osm0sis:
Backup is working on my 8T with my simple model change module, just it is now backing up with whatever model name got set, e.g. KB2005_SN for me.

If there's an issue with @kdrag0n's 2.1.0 along those lines then someone should report it to him, he can probably target the prop spoofing more specifically within Play Services so backups are unaffected.
[Magisk] wtosta:
Do you mean, Google phone backup? I don't use Google phone restore feature, thus my question. The Google phone backup has just completed successfully.
[Magisk] kost7:
Yes, thank you, I was asking about the Google backup, because no matter which method I try, whilst everything else works fine, I cannot initialize the phone backup not even via adb commands.
[Magisk] wtosta:
It's interesting, I've never had a problem with that. Perhaps because the phone is backed up in the background, and I have never used the backup restore feature either. But moment ago I checked the copy is properly deposited in my Google Drive account.
[Magisk] jons99:
an easy fix is to disable the lockscreen
[Magisk] jons99:
new alpha is out looks like the repo is removed and if you try to check safetynet in app it'll crash the manager safetynet is still passing tho
[Magisk] kost7:
I am using your mode (thanks, by the way!) along with USNF 2.0 as it was the only way to pass CTSprofile check. As I said, the only side effect is that google backup does not work.

Sorry, but I hardly find it an easy fix so long as it requires to re-add fingerprints and reconfigure password managers, bank apps etc.
[Magisk] jons99:
not so easy then?
[Magisk] zgfg:
From Telegram:

Magisk 714feeb9-alpha released
[Magisk] pndwal:
Latest @vvb2060 Alpha Magisk Changes (Chinese translated):​

alpha update log​

Magisk (714feeb9-alpha)​

Based on 714feeb9, please refer to the upstream update log for related modifications

Properly process any data from magiskd

Support SharedUserId

Delete the backup file after restoring the boot image

Built-in current version update log

Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline

Fix the default shell path of busybox

Extended update to MagiskHide

Remove hard-coded gms version number

https://github.com/vvb2060/Magisk/b...3f867e1efcf/app/src/main/res/raw/changelog.md

app-release.apk from here (click View code):

https://github.com/vvb2060/magisk_files/tree/3261123a379effeb1e6b5e39bef9dc6dd929d6f2

Will add notes later... PW
[Magisk] pndwal:
Installed Latest @vvb2060 Alpha Magisk.

Observations:

Magisk App Check SafetyNet crashes App initially. Solution is to clear App's data.

MagiskHide is still working fine with my previous settings on RN8T:

Only settings needed for S/N full pass are manually added SafetyNet service in Google Play services (com.google.android.gms.unstable) to MagiskHide list (Check 'Show system apps'.), and Universal SafetyNet Fix module + Riru (needed for v2.0.0)

Nb. Some devices apparently additionally need the main service in Google Play services (com.google.android.gms) manually added to MagiskHide list.

Nb. Those with new September ctsProfile attestation fail caused by Google changes will need additional fix for this, or USNF 2.1.0 w/ integrated fix.

Module repo is removed. Previous module's unaffected. Install from storage remains.

Floating bottom menu is replaced by fixed menu with labels:

Alpha seems to include all TJW commits to date + 12.

https://github.com/vvb2060/Magisk/commits/alpha

Interesting commit labeled Alpha only:

https://github.com/vvb2060/Magisk/commit/0d8f54ce10c3afb00f54698a851018d4cd1efb1e

This changes MagiskHide properties incl. for sensitive props in 10 files. I'm guessing this may be restoring MagiskHide settings removed by TJW and allowing MagiskHide to work for SafetyNet pass...

PW
[Magisk] zgfg:
Modules Repo still present?
[Magisk] pndwal:
No. Previous module's unaffected. Install from storage remains. Other observations above. PW
[Magisk] klemi71:
Is there a link for switching from Magisk to Magisk alpha without twrp? Sorry for this dumb question, I just don't have time for running into trouble and solving this.
[Magisk] pndwal:
Just install the Alpha app (probably need to remove TJW build first due to different file signature), then update Magisk.

app-release.apk from here (click View code):

https://github.com/vvb2060/magisk_files/tree/3261123a379effeb1e6b5e39bef9dc6dd929d6f2

PW
[Magisk] Mowca:
after installing safetynet-fix-v1.2.0-MOD.zip the name of the phone model has changed in information about phone-> Model from SM-G970F to Pixel. How to change it?
[Magisk] zgfg:
That is because the modul works by faking ro.product.model (the same that is used in About)

If you don't like, take the other approach with XPrivacyLua
[Magisk] pndwal:
Restore standard USNF module, and use MagiskHide Props Config module, Force Basic attestation, custom option to set a different but close model from same OEM to keep device specific features working. (Nb. You still need mismatched model to cause the fallback to basic attestation.) PW
[Magisk] pndwal:
... Appended URL to previous answer... PW
[Magisk] simika:
well this worked for me lol.. on my old honor 8 Pro never had Google pay working.. I wanted to try this and guess what? Google pay works, card added, tomorrow morning I'm gonna pay my breakfast with it 😂💯👍🏻

[UPDATE]

it worked.. perfect breakfast 💯💯💯
[Magisk] BillGoss:
On my OnePlus 8T running A11 I can backup and restore (followed by a restart) these files to keep my fingerprints after removing the lock screen password: /data/system/users/0/settings_fingerprint.xml /data/vendor_de/0/fpdata.

I've also attached a shell script I use in Termux to manage this.
[Magisk] wtosta:
As I observed faking ro.product.model to "Pixel" probably breaks The Galaxy Store on S9 and S10e. The Galaxy Store refuses to launch after such modification. I haven't tested it for too long and I'm not completely sure about it.
[Magisk] zgfg:
Likeky. I'm not on Sammy but I had similar problem with Xiaomi.eu builds, faking the model causes trubles for their Updater app. AFAIK, wrong product model also causes issues for GCam (devs usually distinguish models per ro.product.model for loading default settings)
[Magisk] Shxckz:
When i install it, i have 2 magisk apps, 1 renamed (my used one) and the alpha version, do i still have to remove the tjw build ?

because in the alpha version it doesnt even show that i have installed magisk and i cant update

The alpha app also vanishes when i close it.
[Magisk] zgfg:
You have to uninstall the old Magisk apk, but not Magisk

Then Alpha app should be able to see your (old) Magisk

Then patch from Alpha apk and flash
[Magisk] Shxckz:
Perfect, just what i thought. Flashed the alpha version now, lets see how this version is doing. :D
[Magisk] zgfg:
Which Alpha did you install, f98c68a2 from Github (with Magisk modules repo) or 714feeb9 as latest from Telegram (without the Repo)