yashsingh1/xdaforums huggingface dataset:
[Magisk] Tiemichael:
Thanks for the quick reply!

I am wondering why Play store certification will soon be a problem with a (currently certified) Stock ROM?
[Magisk] Didgeridoohan:
Because Play Store certification is directly tied to the CTS profile. If CTS fails, so will the certification status (once it catches up).
[Magisk] Tiemichael:
Thanks!
[Magisk] swour:
The error shows while launching the module and before applying custom props and changing other settings like key attestation. The logs don't contain this error so I've made a short clip.

So basic key attestation that does not change the model will be nothing more than a placebo? Then the only difference that allows my phone to pass the CTS profile check is setting the "ro.product.model" to any other (randomly picked) value than the original, causing a mismatch with the other device names.
[Magisk] Didgeridoohan:
Hm... Obviously I can't reproduce, since I'm pretty sure I would have caught that while testing everything. Are you sure there's nothing in the logs? Neither Magisk nor module logs?

That's spot on. You can actually set the model prop to anything, as long as it doesn't match your current device. Using a device that's as close as possible is good practice though, so as not lose device specific features (so for a Pixel 2 XL a regular Pixel 2 might be a good idea).
[Magisk] olivercervera:
I'm trying to install the module but I get this error.

Latest Magisk.

Redmi Note 8T running Pixel Experience (Android 11).

EDIT: Mhh, looks like is not specific to this module and I get this error for all modules.

EDIT2: Okay, I've reinstalled Magisk and finally I was able to install modules back again.
[Magisk] ipdev:
I had to give up on testing earlier today.

Thought I would have the majority of the day for testing.

I was sidetracked by life. 🙃​

Will test more (and grab logs) tomorrow (this) evening after work.

---

Since vvb2060's alpha build(s) still includes all the MagiskHide goodies.

I made a personal build of Magisk from John's repo for testing. :sneaky:

Magisk - GitHub - Building and Development - Link

If any one wants to give my personal build a try feel free.

EDIT: Switch to GitHub.

GitHub - Link

Note(s):

Uninstall your current Magisk app.

The builds are signed with a build key.

Unless you were using my build (highly unlikely since I just made one), the Magisk app is signed with a different key.​

I am not sure what will happen if you install it on top of an older Magisk setup.

Best to fully uninstall Magisk before testing this build.

Clean flash or a Factory Reset after removing Magisk would probably be best.​

The Module online repo is currently removed.

You will have to push/download the modules to internal storage.

Then use the Install from storage option to install.​

The Magisk hide list is empty.

The last two defaults to the hide list..

com.google.android.gms

com.google.android.gms.unstable

Built straight from the official Magisk repo, no modifications on my part.

Save for creating a signing key.​

See the Building and Development link above.​

​

----

I have tested on a couple of devices.

Clean flash, OEM ROM.

Poco F2 Pro

OEM MIUI (Global) 12.5.2

SDK30 - 2021-06-01 security.

OnePlus 5T

OEM OOS 10.0.1

SDK29 - 2021-08-01 security.

Pixel 4a

OEM Google RQ3A.210805.001.A1

SDK30 - 2021-0x-0x security.

Not yet tested on Pixel 4a.​

When testing, I was hitting the wall head first when trying to get SafetyNet to pass.

Hope I am overlooking something. :unsure:

I tested on OEM builds since they should pass SafetyNet with little alteration.

Should only require hiding the bootloader and boot status/state. :cautious:

I am not sure if this can be done with just resetting the prop values.

At least not traditionally.

I hope some instruction on how to utilize Magisk's zygote (Zygisk) shows up.​

--

I can change the prop values if I use a script and place it in post-fs-data.d or service.d.

When placed in post_fs, there is a very noticeably lag on boot. When placed in service.d the boot lag is not there.

The prop values are changed when checked using getprop but, SafetyNet still fails.

MHPC module does not seem to change the values for some reason. :unsure:​

As we know, depending on the API used to get the values, the values may differ.

System-> About. Shows the rom build security date (unless we change it in post_fs and not always then).

The getprop command will show security date we set (to match the fingerprint with the matching security date).

Cheers all. :cowboy:
[Magisk] Ryano89:
Sorry to turn this into safetnet thread, bit I'm still confused. I'm on a a custom ROM. If I buy kdragon 2.1 safetnet fix and magisk hide props module, what exactly do I need to configure in hide props module? Fingerprint? Key attestation? I've tried to read along bit I'm still confused
[Magisk] Didgeridoohan:
With custom ROMs you often have to change the device fingerprint, that's what you'd need MagiskHide Props Config for. The rest should be taken care of by USNF v2.1.0.
[Magisk] Ryano89:
Thank you. Should I choose my device fingerprint 8t KB 2007? Or like an pixel 2 or something? When I was on OOS I always just picked my device. And thank you so much for tirelessly answering all of these questions
[Magisk] Didgeridoohan:
Pick your device. That way you won't get any discrepancies of what device you're using in the Play Store and such.
[Magisk] Skye Menjou:
I'm having some issues with the startup sh script, I've tried the different script options.

It's a Xiaomi mi 9, I've attached the logs.
[Magisk] Didgeridoohan:
The service.sh script stops just after initialising busybox, and this message is all over your Magisk log:

E : execve /dev/kcX8Cj/.magisk/busybox/busybox failed with 8: Exec format error

So... Your Magisk installation is borked for some reason, and needs to be fixed. Maybe an uninstall of Magisk and a reinstall could fix thing.

Edit: I knew I had seen that somewhere already... If a reinstall doesn't work:

https://xdaforums.com/t/module-magi...p-edits-and-more-v6-0-1.3789228/post-85057131
[Magisk] Didgeridoohan:
Module updated to v6.0.2

Yet another small update to maybe fix things. Details can be found in the updated release notes for v6.0.0-v6.0.2
[Magisk] zgfg:
Small observation - I observed when I was on v5.4.1 and you released v6.0.1 and now when I was on v6.0.1 and you released v6.0.2

I run props (without updating the module first).

It loads and it says Checking if update available - then No update available (?!)

However, if I take Check if update abailable (u) or Exit (e) and I run props again, then it says that Update is available
[Magisk] Displax:
Cool phone to collection

Asus Smartphone for Snapdragon Insiders ASUS_I007D (11):asus:ASUS_I007D:asus/WW_I007D/ASUS_I007_1:11/RKQ1.201112.002/18.1030.2107.138-0:user/release-keys__2021-07-01
[Magisk] Didgeridoohan:
What kind of device is that? Asus is weird...

https://www.asus.com/us/Mobile/Phones/Snapdragon-Insiders/Smartphone-for-Snapdragon-Insiders/
[Magisk] Didgeridoohan:
Yup... As it turns out, it's a good idea to check the file after it is downloaded, not before. Who knew, huh?

Thanks.
[Magisk] rodken:
Force BASIC key attestation works like a charm.
[Magisk] Hateware:
Hi everyone, I need help if possible!

Preamble:

OnePlus 8T, OnePlus decides to abandon the OxygenOS in favor of OPPO's ColorOS.

I don't like it, so I decide to install the Pixel Experience ROM (Plus version), ROM at the moment excellent, zero problems.

About three weeks ago I rooted the device, yesterday Google Pay "notices" that the system is rooted.

Ok, I don't want to format and flash everything from scratch, I'm too lazy to do that, I admit.

I start looking for a solution, I find this thread and this module.

Checking SafetyNet from Magisk I always get the same negative result:

* basicintegrity ✓

* ctsProfile X

* evalType BASIC

Note that according to the Play Store my device is certified, but apparently this is common.

Reflash stock boot.img (not rooted) didn't help, restore everything uninstalling Magisk didn't help, my phone won't pass the ctsProfile.

For more precise help here are some data:

# Magisk 23.0

# MagiskHide *ON*

# Module - MagiskHide Props Config *latest installed*

# Module - Universal SafetyNet Fix *latest installed*

OnePlus 8T Pixel Experience Plus ROM *latest*

No fingerprint works for my device (or my ROM?), I've tried several, there's no way.

Do you have any ideas?
[Magisk] Didgeridoohan:
Have you also tried "Force BASIC key attestation" (in this module)? Don't pick your own device, but maybe an OP8 or OP9.

Edit: and OnePlus has completely messed up the hardware key attestation on many of their devices, so you probably don't even need the Universal SafetyNet Fix.
[Magisk] Hateware:
Hey, in the meantime, thank you so much for the very quick reply!

I uninstalled the Universal SafetyNet Fix module, tried "Force Basic Key Attestation" using first the OnePlus 8 (Europe) and then the OnePlus 9 (Europe).

Nothing to do, there is no way.

I guess I have to format.

Can I possibly help you in some way? Perhaps by providing logs?

Maybe I'll be talking nonsense, I'm not an expert, let me know if I can help.

Thanks!
[Magisk] Didgeridoohan:
@Hateware It could be your ROM. I've seen more than one report of users on PE having problems...

If you haven't seen it already, you've also got some tips on how to pass SafetyNet here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet

Maybe something applies, if you're lucky...
[Magisk] linuxares:
Seem to be unique to Pixel Experience for some bizar reason. I just tried to enable freaking everything. Makes no difference so it's something inside PE that triggers it.

EDIT: Added my logs with everything activated if anyone wanna check
[Magisk] OhioYJ:
I don't think so... I'm on Lineage and my 8T does the same thing. So I checked my 5T and Tab S5E all have the same issue right now. I have more devices I can check in the morning, but they are all Lineage as well. I've tried a few different things no changes. Maybe if I get a chance tomorrow I'll mess around with versions of things to see if that helps.
[Magisk] rodken:
Would i I be able to change the Model in the 'about' section because it's displays [Model A0001] on a OP8 or is that really not much of a big deal?
[Magisk] Didgeridoohan:
You went with the default it sounds like... A0001 is the model for the OnePlus One, that will be set if you pick the default value. The recommendation is to pick a device from the list, one that most closely matches your device (but not your actual device). It'll still show the wrong model, but you're less likely to experience weird issues...

Or, you could use the latest Universal SafetyNet Fix (v2.1.0). It's more a Riru model and will only spoof the module props to Play Services and nothing else. Resetprop is global, Riru can target specific services...

If you don't want to or can't use Riru, for whatever reason, you could use this module while waiting for @topjohnwu to get the next release of Magisk out. Once that's out @kdrag0n has mentioned that he might move the Universal SafetyNet Fix over to use Zygisk (I might actually look into that myself, would be cool to have an option to only target prop changes to specific apps/services).
[Magisk] pndwal:
Actually it seems to be a number of custom ROMs with prebuilt utils which already manipulate the props values. Seems Devs must fix these internally.

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

Sadly, posts in USNF thread indicate that even USNF 2.1.0 doesn't work with such ROMs, so don't expect any of the model prop changing solutions to work.

TeamFiles XPrivacyLua solution reportedly does work however:

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

I'm guessing that LOS is an unofficial build with similar utils / props changes. If I'm not wrong, Official LineageOS doesn't allow such changes due to policy... PW
[Magisk] 73sydney:
Chickens coming home to roost for ROM devs who thought it was clever to fake props on ROMs, been a pet hate of mine with Pixel 2/XL devs changing the props to present as a Pixel 5 for the bloody free premium Photos tier....
[Magisk] OhioYJ:
So far only 2.0.0 safetynet fix is available unless you are pateron of kdrag0n. I know the 2.0.0 build does not work on anything I have. I haven't checked on devices I haven't updated yet.

I was under the impression we weren't getting anymore releases anytime soon from topjohnwu now that he was working for Google. I thought most people had gone to vvb2060's builds of Magisk?
[Magisk] Didgeridoohan:
Johns working like crazy for the next Magisk release, check the commits on GitHub. The only thing he won't be working on is MagiskHide.
[Magisk] tonyniu2008:
HI there,

I would need some help with the configuration file, the procedure works like a charm

but the Device simulation seems got buggy, i have set the CONFDEVSIM=true in the configuration, but any time, the configure loaded from /sdcard/, the Device simulation feature turned out, i checked this both with getprop and go into the menu, the "3 - Device simulation" turned disabled, even though go the the detail page, the variables marked as active but i am afraid the whole feature turned out.

my configuration is here:

Spoiler content hidden.
[Magisk] Didgeridoohan:
@tonyniu2008 I'll take a closer look at that but meanwhile, could you post your module logs (in case I can't reproduce the issue)?
[Magisk] Chicada:
from fingerprint is 2021-02-01

Sorry long response!
[Magisk] UDPSendToFailed:
Hi guys!

I just updated the module from 5.4.0 to the latest 6.0.2 version, and now my device fails on ctsProfile check.

It was working fine before the update. Magisk says attestation failed, while Google Play says the device is certified. Tried forcing BASIC key attestation, nothing changed.

basicIntegrity ✓

ctsProfile -

evalType BASIC

The device is a Samsung SM-T590 running Resurrection Remix 8.6.8 with Magisk 23.0
[Magisk] Didgeridoohan:
Have you made sure that the device fingerprint you used previously still is set? And did you make sure to pick a different device than your own under Force BASIC key attestaion?

Since you were passing before, I'm going to assume you're already using the Universal SafetyNet Fix.

You could try reverting to v5.4.0 and see if that changes anything. If that makes it start working and you then can confirm that an update to v6.0.2 breaks things again I would love to see the module logs, to see if anything in there can give a hint as to what's going on.
[Magisk] UDPSendToFailed:
You are right, using a different device than the actual one under force basic key attestation did the trick. Switched to SM-T595 and the cts profile passes fine without problems.

I haven't used anything else than this module before, just set the fingerprint for SM-T590 from the list and it was working fine. I will give it a try to downgrade to 5.4.0, and send you the logs.
[Magisk] Didgeridoohan:
If forcing BASIC key attestation worked you won't be helped by downgrading... Google updated the SafetyNet backend recently so now you have to change the model prop to trick CTS into passing. And you do that by changing it to anything else except your own device...

Everything's working as expected.
[Magisk] UDPSendToFailed:
Oh, I didn't know about that change on Google's side. Thanks for the help!
[Magisk] tonyniu2008:
Hi there, thanks for the reply, i just reproduce the issue and log attached.

So simply use the configuration i used to /sdcard, and after the rooting, try props, and choose "3 - Device simulation (active)", you will see "s - Device simulation (disabled)", this is the issue i met.

What actually wanna do is to automate the process with one line command or by replacing configuration file, and the aim is simply to change the fingerprint which will trigger the simulation. if you have any workaround, please let me know, thanks.
[Magisk] Chicada:
I got the updated version

samsung/j6ltedx/j6lte:10/QP1A.190711.020/J600GDXUACUD1:user/release-keys

Security patch : 2021-03-01
[Magisk] pepote666:
mi 10 lite 5g

Xiaomi/monet_global/monet:11/RKQ1.200826.002/V12.5.3.0.RJITWXM:user/release-keys
[Magisk] Didgeridoohan:
Excellent. What's the security patch date?
[Magisk] pepote666:
2021-07-01 thanks
[Magisk] gfrank227:
Hi, I'd like to submit a fingerprint:

This is for the moto g8 plus

ro.product.manufacturer: motorola

ro.product.model: moto g(8) plus

fingerprint: motorola/doha/doha:10/QPIS30.28-Q3-26-4-1-6/9976a:user/release-keys

Security patch date: August 1, 2021

Thanks.
[Magisk] gravityz3r0:
Sorry if i'm asking the obvious...is there a way to modify the props but without the use of Magisk/root? Really would like to avoid rooting my device if possible while i want to fix the Google Play Certification issue.
[Magisk] gfrank227:
I don't believe so. But if you're not rooted, why would you have a certification issue to begin with?
[Magisk] gravityz3r0:
The certification problem arises from an unlocked BL i believed. To be more precise, i'm using a Xiaomi 10 Ultra with xiaomi.eu ROM. I could get it certified by using Magisk with this prop config module installed, but it will break some of my app detecting root (cannot be hidden with Magisk no matter what). So , i'm down to choosing either root or device certification. I can't have both at the same time. I read somewhere that builds.prop should be able to be modified directly from TWRP? Not sure if it works though..
[Magisk] gfrank227:
If you don't want to root, you might consider attempting to relock the bootloader, if your device supports that.
[Magisk] gravityz3r0:
Have you heard of any success of certification passing with unlocked BL and without root at the same time so far? Re-locking BL is a no go for me because that means i'm forced to return to China ROM which is even more restrictive in term of Google Services offered.
[Magisk] Didgeridoohan:
In theory it's possible to edit the props in the files manually (for example with the help of a custom recovery). But, on many modern devices it's impossible to mount system partitions rw which means it's only possible the systemless way (Magisk). If that's the case on your device I can't say... Doing it systemless is also much safer.

And unless Xiaomi have messed up their implementation of hardware backed key attestation it'll also be impossible to hide the unlocked bootloader, unless that's implemented natively into the ROM you're using.
[Magisk] pndwal:
Bit further to info above -

Unlocked bootloader is just the root of a broken 'chain of trust', and new shared-blocks file system (can't write to system) on later Android stock versions will mean you can only do such mods systemlessly in any case (without re-aligning the whole file system; there is a method on XDA to do this, but it's not for the faint-hearted!).

So Magisk systemless solution is still probably your best option.

If you get a combination of MHPC (you'll need certified fingerprint set to pass ctsProfile on China uncertified stock ROM, bit XiaomiEU custom ROM may well have spoofing integrated. Many other custom ROMs like official LOS won't do that. Also, likely Force Basic set) and USNF (2.1.0 early release includes best fix for September Google server end changes) to achieve full SafetyNet pass (It's hiding unlocked bootloader among other things), you'll generally get Play Protect certification after clearing Play Store and Play Services data.

Regarding additional methods of detection, if you've tried everything here (Check before @Didgeridoohan edits / removes all references to MagiskHide! 😁 and don't forget Isolation apps):

https://www.didgeridoohan.com/magisk/MagiskHide# incl. @vvb2060's Enhanced mode for MagiskHide, since many banks are now reportedly using Momo techniques to detect isolated process leaks, you can give MomoHider

https://github.com/canyie/Riru-MomoHider a try. Many found it works better for them. Usage here:

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

Further:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85300227 👍 PW
[Magisk] Dante63:
Hello all,

I might be repeating the question that many may have asked,

I was wondering if the latest update broke the safetynet...

I have Samsung galaxy note 20 ultra 5G, the modules that I have are

View attachment 5408649

View attachment 5408651

And as a temp solution to fix the broken safetynet i installed this

View attachment 5408647

The only problem with this solution is it changes the device brand to BASIC and device info becomes unknown

This breaks galaxy store functionality (not that I care about) but if I ever disable the module, all mobile banking apps reset and I have to fill all details again, same thing if I enable, I think it's because of device type and brand keep changing...

Is there a way to fix safetynet either using this module alone or using this module with kDrag0n or something else...? I do not want xposed solution, not fond of it nor of installing too many modules...

Thank you very much in advance
[Magisk] Didgeridoohan:
@Dante63

Using this module and the "Force BASIC key attestation" feature, while picking a device that is as similar as your own at possible (but not your own device) will work. You could also get v2.1.0 of the Universal SafetyNet Fix (or wait until it's released to the general public) which will do a dynamic spoof of the model props only towards Play Services (using Riru and at a later date it'll switch to using Zygisk).
[Magisk] Dante63:
If you will update this module, what modules would be required to work alongside yours?
[Magisk] Didgeridoohan:
Not sure what you mean... What update?

Currently, depending on your setup you will need to use this module and Universal SafetyNet Fix to fully pass SafetyNet.

This module will take care of the device fingerprint and can also help passing the bootloader check by spoofing model props (Force BASIC key attestation). But, to fully fool the bootloader check you'll also need USNF, which from v2.1.0 also will take care of the model prop spoofing.
[Magisk] Dante63:
You said you'll later switch to Zygisk

So I was wondering when that is done, do I need Universal SafetyNet Fix 2.1.0?

I'm trying to get rid of unnecessary modules
[Magisk] Didgeridoohan:
No, I said that USNF will later switch from Riru to Zygisk. Once Zygisk goes live that's maybe something I'll look into, but that would be completely new to me and not on the near horison (if ever).
[Magisk] Coldtrain6989XD:
I am on a rooted pixel 4a with a patched stock image running magisk with magisk hide props config v6.0.2 and universal safety net fix v1.1.1 and can't bypass safety net
[Magisk] Didgeridoohan:
In that case you most likely need to enable Force BASIC key attestation and pick a device other than your own from the list (but as close as possible) or use Universal SafetyNet Fix v2.1.0.
[Magisk] Coldtrain6989XD:
I picked 3a instead of a 4a and I might to use USN v2.1.0 but don't see v2.1.0 on Github.
[Magisk] Didgeridoohan:
USNF v2.1.0 is so far only available to patrons. It'll likely be released for everyone sometime this week.
[Magisk] Coldtrain6989XD:
Thanks for the info man!
[Magisk] pndwal:
safetynet-fix-v2.1.0 is public now... PW
[Magisk] Coldtrain6989XD:
It works like a charm! Thanks Didgeridoohan really appreciate it man!