yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
I Have osmosis's latest busybox 1.29.2 Magisk Module installed.

I updated my post above.

---------- Post added at 02:16 AM ---------- Previous post was at 02:15 AM ----------

I updated my post above.

---------- Post added at 02:18 AM ---------- Previous post was at 02:16 AM ----------

The info about my device is in my signature. The only thing different about the device in question that I am aware of, is the rom build number and the IFWI version.
[Magisk] osm0sis:
Extremely hard to read the blue text over the forum's dark theme, but I think I see you're running an Android 6.0.1 x86(_64?) device? Might be a bug with busybox's x86/_64 build. Does it work with busybox 1.28.4? You can grab the zip from my Odds thread.
[Magisk] Didgeridoohan:
Yes, if there already is a current Busybox binary present a new one won't be downloaded.

Could you upload new logs now that you've got the Busybox binary moved over to the module?

It seems to be a very rare occurance. I could only find one reference to the same issue (linked above), and that was with your Busybox v1.28.4.
[Magisk] Didgeridoohan:
They are x86 (64 or not) I believe, but why would it work on one device and not the other?
[Magisk] osm0sis:
I looked into Cherry Trail SoC and it's actually x86_64 from what I've read, but Magisk's busybox would be x86 and mine would be x86_64 so both architectures must be affected.

So which busybox did work? I'd like to check their configs.
[Magisk] martyfender:
I have never seen that dark theme to be aware of it as my Linux Mint desktop is all white as are all of my tablets. My 60 year old eyes can't handle dark themes and strain my eyes, but if I was much younger I would have the same opinion.

I have used all of your busybox versions since the first of the year and, but of course, with this module version it has been v1.29.2 only.

I do have it installed as a magisk Module and that old version is not on your odds and ends thread, as a Magisk Module, as far as I know unless you mean for me to copy it into the sbin magisk hide props config module folder only, or the binary to /sbin/.core/mirror/bin/ , or other location?
[Magisk] Didgeridoohan:
Well... That's the funny thing. I'm assuming that [MENTION=8126387]martyfender[/MENTION] was using the same Magisk version and the same Busybox module version on both devices. One device seems to have the error, one doesn't.

Actually, [MENTION=8126387]martyfender[/MENTION], could you post the logs from the device that didn't have an issue? And, could you specify details about the differences between the two devices (I seem to recall there are slight differences between your tablets)?
[Magisk] martyfender:
The tablet differences are build id numbers, dates and (IFWI Intel) Firmware interface versions.

All 4 tablets:

Processor: Intel x86 Cherry Trail Atom x5-Z8350 @1.92 GHz, 1gb RAM, 16gb internal storage

Model number: NX16A8116K

Android version: 6.0.1 Marshmallow

Kernel version: 3.14.64-x86_64

Recovery: TWRP 3.1.0-0 built by vampirefo

Root: Magisk (2018080822) Unofficial Version Kantjer With [MENTION=4470081]topjohnwu[/MENTION] 's lastest commits on github.

One of the four tablets has [MENTION=7187684]ianmacd[/MENTION] 's build, but not the 2 tablets in question.

What colors will show up in both light and dark themes? Should I change to the default black? That looks like that would not show up on a dark theme, but white would not show up on my white backgrounds.
[Magisk] martyfender:
I tried the above command in the root teminal with osmosis busybox 1.29.2 and get:

u0_a90@NX16A8116K:/ $ su
aw.githubusercontent.com/StevenBlack/hosts/master/hosts <
Connecting to raw.githubusercontent.com (151.101.184.133:443)
wget: note: TLS certificate validation not implemented
HTTP/1.1 200 OK
Content-Security-Policy: default-src 'none'; style-src 'unsafe-inline'; sandbox
Strict-Transport-Security: max-age=31536000
X-Content-Type-Options: nosniff
X-Frame-Options: deny
X-XSS-Protection: 1; mode=block
ETag: "2c85c91a49080c60c09dc5812f0d6c44d12cea49"
Content-Type: text/plain; charset=utf-8
Cache-Control: max-age=300
X-Geo-Block-List:
X-GitHub-Request-Id: 08F0:7C2A:233C65:24EB2A:5B6BED60
Content-Length: 1810764
Accept-Ranges: bytes
Date: Thu, 09 Aug 2018 07:34:24 GMT
Via: 1.1 varnish
Connection: close
X-Served-By: cache-mdw17372-MDW
X-Cache: HIT
X-Cache-Hits: 1
X-Timer: S1533800064.033789,VS0,VE2
Vary: Authorization,Accept-Encoding
Access-Control-Allow-Origin: *
X-Fastly-Request-ID: a691c63cda5e9b42a0fca4c8c5d2e4ff1de8ddde
Expires: Thu, 09 Aug 2018 07:39:24 GMT
Source-Age: 287

wget: clock_gettime(MONOTONIC) failed
1|u0_a90@NX16A8116K:/ #

I tried copying and pasting the above command twice, not sure why the r was cut off in the beginning for raw?
[Magisk] martyfender:
New log after busybox copy:
[Magisk] ghiblies:
My device is Samsung Galaxy S20 5G.

The evaltype for this device is 'HARDWARE'.

ctsProfile has failed.

We want to set 'Force BASIC key attestation' to pass through ctsProfile.

When using 'Force BASIC key attestation', is the default device ID(SM-A300FU) to be set OK?

Is it better to set the device ID of another 'Galaxy device' that has a similar function?
[Magisk] Didgeridoohan:
That's the preferred way. It'll be less of a risk that device specific functions (and HD YouTube, etc) stop working that way.
[Magisk] Didgeridoohan:
Like I posted in my previous reply regarding this, you should be able to benefit from that...

As long as you pick a model that is the slightest bit different you'll get basic attestation. You were even involved in the discussion on this when @ipdev first brought it to my attention:

https://xdaforums.com/t/module-magi...nd-more-v5-3-6.3789228/page-211#post-83647965

https://xdaforums.com/t/module-magi...nd-more-v5-3-6.3789228/page-212#post-83654739
[Magisk] zgfg:
Currently I have beta A11 firmware, for that CTS passes with no need to change props

Before that, with stock, month ago, I was also passing CTS with Basic, with no need to change any props

As said, when I previously needed (Google changing their policies from time to time), I used the name davinci ('code name' for Mi 9T) and it worked fine with the stock

Hence it was long ago (when displax discovered the trick and provided his module) when I experimented by using real but different product name (Mi 9T Pro instead of Mi 9T) but at that time it didn't force CTS to Basic for me - now, cannot conduct retesting
[Magisk] ghiblies:
Please let me know if you know of any other "Galaxy devices" that have similar features to the 'Galaxy S20 5G' and the evaltype is BASIC.

Is there a list of Galaxy devices whose evaltype is BASIC?
[Magisk] ipdev:
Hi all. :)

I have not tested the force basic option recently.

The last I tested and confirmed by a few others, you can pick a device that is hardware test.

It has to be a different device, not the same as you are using.

@dimm0k posted this while I was actively testing Force Basic and shortly after reading something in a gapps thread (may have been a TG channel).

Post 4,232 - Link

Google changed something (I would have to look back, think it was one of the lib files) in Pixel 4 when they reintroduced face unlock.

This affected bio-metrics sensors. That is why I made the suggestion to try Pixel 4 since, 4XL was the device in question.

No. This will not enable face unlock on a different device.

As noted, it fixed the bio-metrics issue on Pixel 4XL using the Pixel 4 as the Force Basic device.

Post 4,244 - Link

---

Sorry, I am not a Sammy guy so, I am not sure what model is closest to your device. 🙃

Call out to the Sammy users that watch this thread.

Any ideas on this? :unsure:

---

Cheers all. :cowboy:
[Magisk] ghiblies:
Everyone in this thread.

Please lend me your wisdom.

I want to solve the problem of #4789.

Please let me know if you know of any other "Galaxy devices" that have similar features to the 'Galaxy S20 5G' and the evaltype is BASIC.

Is there a list of Galaxy devices whose evaltype is BASIC?
[Magisk] M1ster1:
Oh that's right, indeed!

Well, I hope flashing OTA through OF won't end up in Factory Reset, I will do a backup anyway before just in case, but I would be happy if this works and can save me some time and maneuvers.

Thanks again for the time you took to help me! 😁
[Magisk] bartleby999:
It doesn't matter if the other device is using Hardware or Basic Eval. Just that it's different from your device. You should pick the closest device to yours to avoid losing any app functions.

Try the S20 or the S20 Ultra.

All you need to do is set a custom prop (ro.product.model) to something different this should force the check to basic regardless. For example, if someone with an S10 set it to a S205G they should still pass CTS because the device is different.

Another example as I stated earlier...

My device Tab S6 (WIFI) fails because of Hardware so I switched to a Tab S6 (LTE) which would be hardware too as it's exactly the same device except it has LTE functions but SafetyNet still reverts to Basic Eval checks.

So all you should need to do is switch to another of the S20 lines.
[Magisk] ghiblies:
Thank you so much!

By setting the 'S20 Ultra', the ctsProfile was passed without any problems.

-Background of the question-

Microsoft's Intune app has detected a Custom OS.

I thought it was because of the error in ctsProfile.

However, the error was not resolved when the ctsProfile passed.

The detection mechanism of the Intune app may be powerful.

It's unfortunate, but it can't be helped.

Thanks all.
[Magisk] zgfg:
You can try by cleaning the app' s cache, data or even by uninstalling the app

But if the app declares custom ROM, it probably reads from device fingerprint (you can try changing the print)
[Magisk] bartleby999:
I'm not familiar with that app but try looking through its thread if you need help.

Intune thread
[Magisk] Vanmanman:
Hi, I have a Mi9t MIUI Global 12.0.5 that was a Chinese K20 phone and I live in New Zealand if that helps anything.

To test I uninstalled Magisk and used osmosis su thing to uninstall any root and I couldnt pass saftey net as stock.

I reinstalled magisk (hid it) and MHPC and tried changing "ro.product.model" to "Mi Note 3". The downloaded saftey net checker I got says "your Mi Note 3 Failed saftey net compatibility test".

Anyone have any ideas how I can pass saftey net check?

I tried MI 8 device simulation with all props enabled and still doesn't pass too. Not entirely sure what I've done to my phone but Google really dosnt like it :)
[Magisk] dr4go:
Samsung Galaxy S10e SM-G970F (11):Samsung:SM-G970F=samsung/beyond0ltexx/beyond0:11/RP1A.200720.012/G970FXXU9ETLJ:user/release-keys__2021-01-01
Samsung Galaxy S10 SM-G973F (11):Samsung:SM-G973F=samsung/beyond1ltexx/beyond1:11/RP1A.200720.012/G973FXXU9ETLJ:user/release-keys__2021-01-01
Samsung Galaxy S10 Plus SM-G975F (11):Samsung:SM-G975F=samsung/beyond2ltexx/beyond2:11/RP1A.200720.012/G975FXXU9ETLJ:user/release-keys__2021-01-01
[Magisk] zgfg:
First, disable MHPC, reboot, make sure Magisk hide is enabled, use the Magisk Manager built-in SafetyNet check and read what does THAT say

If Basic integrity is passing (should be if Magisk hide is enabled and if you didn't use problematic Magisk modules like Xposed or so), then pay attention does it show Basic or Hardware eval for CTS

If CTS fails with Hardware eval type, then change ro.product.model

I don't like to 'rename' my own Mi 9T to some Note, to 'downgrade' it to Mi 8 or whatever, I rather redefine:

ro.product.model=davinci

(you have Mi 9T hence you now why davinci and not e.g. raphael)

Reboot and that's it
[Magisk] Vanmanman:
please delete, not sure how
[Magisk] Vanmanman:
1) Disabled MHPC (have no other modules) and rebooted, magiskhide enabled. Magisk Manager safteynet says

"Attestation failed!

BasicIntegrity -

ctsProfile -

evalType BASIC"
[Magisk] zgfg:
Still you didn't answer does Basic Integrity pass or not?

Right from the "Basic integrity" there is an icon - is that icon check-mark indicating pass or minus sign indicating a failure

Also, Magisk hide must be enabled before reboot.

And for Google Play Services, com.googlr.android.gms and com.gms.sndroid.unstsble must be checked-marked in the Msgisk Hide tab
[Magisk] Vanmanman:
Sorry "-" was meant to indicate fail. Was trying to copy the magisk fail indication but don't know how to type a minus with circle around it.

Magisk hide enabled with those ticked and then reboot but no luck
[Magisk] ghiblies:
zgfg & bartleby999 Thanks.

Clearing the app cache & data had no effect.

'Edit device fingerprint' was also tried, but to no avail.

Maybe it is because the 'Phone Status' is set to Custom even after setting the MHPC.

I don't know what 'Phone Status' is set to custom based on.

I think it's probably due to the settings here, but I have no idea.
[Magisk] bartleby999:
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] bartleby999:
Have you hidden Company Portal in Magisk Hide? Also hidden Outlook?
[Magisk] ghiblies:
Of course, I've also set up 'Magisk hide'.

The Intune app creates a 'work profile', so I set that up as well.

However, it still detects 'Custom OS'.
[Magisk] INTseed:
Revolut work?
[Magisk] Didgeridoohan:
Updated fingerprints list to v112

It's been a full month since the last fingerprints list update. So naturally this update got big... 50+ prints updated/added. 🤘

Thanks go out to these amazing individuals that keep those prints coming (in no particular order):

@emanresu2, @BlueMan_86, @Sh3rRy, @FivEawE, @oursgentil, @GtrCraft, @Displax, @Max128, @Some_Random_Username, liwenjie119 on GitHub and @dr4go

The list will update when you run the props command, or if you have turned off automatic updates you can update by using the -f option (use -h for help or see the docs) or from the "Edit device fingerprint" menu.

New

Meizu 17

OnePlus N10 Global

OnePlus N100 Global

Redmi Note 8 Pro Europe

Samsung Galaxy A6 SM-A600F

Samsung Galaxy S10e SM-G970F

Samsung Galaxy Tab S6 Lite SM-P610

Updated

Google Pixel 3 to 5, all variants

OnePlus 6 to N100, all models - many variants (too many to list)

POCO X3 Europe and Global

Samsung Galaxy S10 SM-G973F

Samsung Galaxy S10 Plus SM-G975F

Xiaomi Mi 10T Europe

Xiaomi Mi 10T Pro Europe

Xiaomi Mi A2 Global

Xiaomi Mi A2 Lite Global

Xiaomi Mi A3 Global

Xiaomi Redmi K20 Pro China

Xiaomi Redmi Note 8 Global
[Magisk] Didgeridoohan:
Apart from the Intune Hider thread that @bartleby999 linked you, there's a discussion thread for Intune here: https://xdaforums.com/t/microsoft-intune-company-portal.3611588

I know next to nothing about Intune and Microsoft's app and infrastructure, and it's a bit off-topic in this thread, but there's a very good chance that it's detecting your tripped Knox. If that's the case you're SOL...
[Magisk] Didgeridoohan:
I have no idea what that means...
[Magisk] Didgeridoohan:
I haven't been very active on XDA for a few days, but this thread sure has! It's great to see that there are so many helpful forum members hanging out in here. :love:
[Magisk] Vanmanman:
Tried this with multiple devices simulated and just fingerprint enabled but cant pass anything in safteynet
[Magisk] Didgeridoohan:
I think you got the wrong section of the docs... The link goes to the troubleshooting section and the part about "I can't pass the basicIntegrity check", and that can't be fixed with"device simulation".

You might want to take a look in my MagiskHide troubleshooting guide:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] Vanmanman:
Thanks man, I've been through all this but after the last 2 magisk updates it just hasnt worked on my device anymore. Was working amazingly before.
[Magisk] Didgeridoohan:
That means something changed on your device, simple as that. Magisk has no issues passing SafetyNet as long as your device uses basic key attestation, and that you can force using this module (only applicable for the CTS check). Pretty much everything you need to troubleshoot SafetyNet not passing can be found in the above link. What I can add though, that I'm not sure if I've written anything about in the guide, is that I've seen several reports of people having issues passing SafetyNet on some MIUI builds. You might want to look around your devices forum for more help.
[Magisk] donnelldouglas:
Hi, I have been using this module for almost two years on my PocoF1 on Nitrogen OS android 9 without any issues, so THANK YOU!

I have updated everything and am using the latest Magisk 21.2 and Manager 8.0.5 with props config v5.3.6-v111. my device integrity check is successful.

I have two banking apps, one that works with no issues but with the other one I'm facing a problem. app is called myRaiffeisen and as soon as I open it it opens a web browser that shows a message on the bank website that it has detected a modified system or a custom rom...

I have tried updating everything and I have gone through all the steps I could find on different threads without success... is there any way I can resolve this? thanks in advance
[Magisk] Didgeridoohan:
It is unlikely that this module can help you any further (unless the app is looking for specific prop values that you could change with the custom props option).

Everything I've got on hiding root can be found here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] ghiblies:
I knew it....

There's nothing I can do about it.

Thanks...
[Magisk] Max128:
@Didgeridoohan Thanks for the update! I have set the new fingerprint for the tablet.. ( i choose 1 edit device fingerprint ) but after reboot i am still not can pass the ctsprofile. I have reset the google play store , i have also hiding service google play with magiskhide ( i have use your apps on my phone too before and is working fine ) Any ideas why is not working ? I am using the last version of magisk and manager
[Magisk] Didgeridoohan:
Could be a lot of things... Take a look in the docs:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] Rindmann:
So you have exposed installed? I have the Vr secure go app (Volksbank) and got the same issue like you. Blacklisting everything in exposed and hiding everything in magisk resolved the issue for me..
[Magisk] donnelldouglas:
I don't have xposed, I read that some of these banking apps look for xposed , so I always assume it shouldn't be installed as it causes issues?
[Magisk] svendsvin:
Can this mod do the same as this?: https://xdaforums.com/posts/83028387/

Or can I use both?
[Magisk] ipdev:
Yes.

MHPC ReadMe (How-To) GitHub - Force BASIC key attestation - Link

You will want to use one or the other, not both.

Cheers. :cowboy:
[Magisk] Umination:
Hello if we have an s10 lite (SM-G770F) can we use another fingerprint ? if yes, which one ?
[Magisk] Didgeridoohan:
You can generally use whatever fingerprint you want:

https://github.com/Magisk-Modules-R...ob/master/README.md#can-i-use-any-fingerprint

If your specific device isn't included you can pick a different one, but it's often a good idea to pick one as close as possible to your own. So in your case one of the other S10 variants might do.

Or, you could find a S10 Lite fingerprint and manually enter that or better yet submit it so I can include it in the list:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] Umination:
Okay, thanks for this answer and sorry for publishing the same question twice.
[Magisk] amk316:
did google do something ???View attachment 5185233
[Magisk] Didgeridoohan:
No idea, maybe.

But, before anything else, have you made sure that MagiskHide is enabled and if it is that you have toggled it off and on again? Maybe you even need a reboot...
[Magisk] amk316:
not just me also my friend, we have s20 and we used basic setting for months this just happened !!!
[Magisk] saabsaviorlee:
I woke up and now fail safetynet. Didn't change anything on my part. Anyone else experiencing same??
[Magisk] Didgeridoohan:
It is of course very possible that Google has updated something. There's been several reports along those lines just now.

But it might also be something with MagiskHide, considering that there was just a new release.

If you guys make sure that MagiskHide is enabled, toggle it off and on if it already is and then reboot and check that MagiskHide is enabled once more, and CTS still fails it looks more and more like something's been updated...
[Magisk] amk316:
did that

no luck
[Magisk] Didgeridoohan:
If they've done something, my first guess would be that they've added something to detect the model change to force basic attestation. Not something I can test though, since all my devices are ancient and have basic attestation out of the box...
[Magisk] GoldElocks:
It appears the update was pushed from Google's side and has to do with Google's new Pay app.

I was on my phone and got a pop-up along the lines that Pay for Google is the new app and Google Pay will be discontinued. It then said that my phone was rooted and I could not use contactless payment. I wasn't in the app it just popped up.

I've tried toggling magisk hide, rebooting, switching from canary to beta channels and re-rooting, updating to newest manager and CTS still fails.

I guess we knew this was coming but I'm hopeful that the guys here can work there magic and get us back in business once again.
[Magisk] /spectre/:
I am also unable to pass SafteyNet as of today, no changes made since Magisk update.

basicIntegrity ✓

ctsProfile –

evalType BASIC
[Magisk] Snow_ball:
same here. Pixel 3a, January patch, latest Magisk

out of the blue it fails ctsProfile
[Magisk] MoL_82:
Same issue here.
[Magisk] bender85:
Same problem.

Pixel 3a

Magisk 21.2

Latest firmware
[Magisk] zgfg:
Not only Pixels. See the same reports in Magisk general thread. Since this afternoon failing also on my Xiaomi Mi 9T

Shortly tried Fingerprint and Device simulation, no avail (no point in trying Force Basic since it is on Basic)
[Magisk] /spectre/:
I'm on a Samsung S9+ Exynos chipset.

Also got the Google Pay pop-up regarding root detection.
[Magisk] Didgeridoohan:
Guys... There's no need for more "same" posts. It's quite apparent that it's widespread.

Please only add posts about possible solutions/workarounds from now on. That would be appreciated.
[Magisk] ThrashWolf:
To save others some time, I just want to mention that changing my fingerprint with this module hasn't done anything to fix the issue. Looks like we're going to have to wait for Magisk itself to be updated.
[Magisk] tsteeples:
Hi

Thank you for all your work on this project, it's very much appreciated and it's a great benefit to the community.

Please could I ask you to add support for the Fairphone 3/3+? The build.prop I've extracted from the stock image has the following values:

ro.product.system.device=FP3

ro.product.system.manufacturer=Fairphone

ro.system.build.fingerprint=Fairphone/FP3/FP3:10/8901.3.A.0054.20200929/09290922:user/release-keys

ro.build.version.security_patch=2020-10-05

However, I've put the following line:

Fairphone FP3/3+:Fairphone:FP3=Fairphone/FP3/FP3:10/8901.3.A.0054.20200929/09290922:user/release-keys__2020-10-05

into a printslist, and whilst I can load the fingerprint successfully, my ctsProfile check still isn't passing. Do you have any suggestions for anything else I can try? No worries if not. My next step was going to try flashing the stock ROM and using getprop to get the values instead. Cheers again.
[Magisk] Didgeridoohan:
@tsteeples You might also have to force basic attestation (currently option 2 in the main menu) if your device uses hardware backed key attestation. Could also be that you're one of those that have started failing CTS today. Google might be tinkering with things.

I tested the print and it works perfectly. If you want to give it a go (to see if there was something wrong with your file), my test fingerprint file currently has only this print in it, and you can access it by running the props command with the -d option. To get back to the original list just use the -f option.