yashsingh1/xdaforums huggingface dataset:
[Android Software Development] BrimoFan123:
Thanks for this guide.

Unfortunately it doesn't work.

Once I have renamed locksettings.db to something else phone doesn't ask for PIN but it is stuck with "Phone is starting"

Reading this thread it is confirmed result for Android 9.

Looks I have to flash stock ROM and then again to flash LinaeageOS.

****!
[Android Software Development] Lord Sithek:
I did it on A10 as well, but I deleted those files, not renamed them. But I can't guarantee nothing...
[Android Software Development] BrimoFan123:
I have no TWRP so I have access to system files using adb root -> adb shell

And probably it doesn't work in my case because the data partition is encrypted so it won't boot me because data need to be decrypted with fingerprint or PIN so if those files are deleted or renamed then decryption can't be successfully performed.

I will leave it as it is - maybe in few hours some other good people suggest me what to do?

I did nothing except disabled SafetyNet Fix Module in Magisk so why the sake phone do not accept my fingerprint nor PIN?
[Android Software Development] BrimoFan123:
Is there uninstall script for Universal SafetyNet Fix ?

In short: once I have disabled Universal SafetyNet Fix in Magisk and rebooted my phone - PiN nor fingerprint don't allow me to unlock it.

Even when I have deleted "disable" file in /data/adb/modules/safetynet-fix still phone is not unlocking with PIN nor fingerprint.

What about if I put "remove" file in /data/adb/modules/safetynet-fix ?

(According to: https://www.didgeridoohan.com/magisk/MagiskModuleIssues

If you create the "remove" or "disable" files, Magisk will take care of removing or disabling the module on the next reboot. Uninstalling the module this way is the preferred way, since it will also run any

uninstall script that the module is using

. )

Will Universal SafetyNet Fix be properly uninstalled and will it be possible to unlock my phone?

I'm desperate now...
[Android Software Development] chiteroman:
Try to spoof another device fingerprint with same CPU.
[Android Software Development] zgfg:
Are you sure that he (1) understood what you asked and (2) he wanted to answer

Generally, he doesn't like to answer on questions distracting from what they consider being in the scope of their ROM and usage (Magisk and its modules definitely are not for them), and also (he/they know very well that they spoof but) he correctly thinks that it's not in their and their users interest to describe all the spoofing details

Sorry to say so, but you're pushing on this kind of like you are from Google😁
[Android Software Development] chiteroman:
ArrowOS force BASIC evaluation so I can't know if it works

View attachment 5896289
[Android Software Development] chiteroman:
When I installed ArrowOS the rom asked me about the google account and password so TEE saved my info.
[Android Software Development] chiteroman:
Understandable.
[Android Software Development] chiteroman:
I tried Arrow and Lineage and can't pass Strong due forcing BASIC evaluation. In stock rom doesn't work too (I fail CTS). But in xiaomi.eu I pass all including Strong.
[Android Software Development] pndwal:
Haha... I just disabled Zygisk and now see it... (I just installed it again a couple of days ago as you know, to test native bridge hiding)... Thought MagiskHide was long gone in Alpha per Aug 9 TG Alpha TG post...

You said " I managed to completly broke TEE that's why in official ROM I can't pass CTS/Strong"... I said "You mean it doesn't pass with bootloader locked?..."; I was speaking of your device; I know this stuff about ROG Phone 3...

🤔...

You said "sensible props"... I said "Sensitive props?"...

That's what I said... NOT "completely broken"... But it's not between bootloader and tee as I keep saying; TEE keypairs are being extrapolated correctly in Key Attestation app!... Only droidguard / GSM / Google servers seem to be getting it wrong in device integrity APIs...

That was to confirm for you that TEE isn't broken...

But you're already passing deviceIntegrity with XiaomiEU ROM!?... Am I missing something?... If not, did you try what I said after installing Magisk?... I said you only need to fix sensitive props w/ stock in addition to hiding root from gms as for XiaomiEU...

... Did you never pass deviceIntegrity w/ stock, Magisk and modded USNF?

So did you pass on Xiaomi EU & Magisk w/ the gms processes in denylist?... Should be easy to pass deviceIntegrity on stock too if you did the same + had a sensitive props solution. (Of course I mean with NO USNF)... PW
[Android Software Development] chiteroman:
Stock rom fails Device even with MHPC and Shamiko, with USNF I can pass it except Strong.

But with xiaomi.eu rom fresh install (without Magisk):

View attachment 5896321View attachment 5896323
[Android Software Development] zgfg:
Btw, I see that you have a screenshot showing that you pass all three Device, Basic and Strong Integrity (good for you and better do not question too much) but what do you mean by "having two eval types"?
[Android Software Development] immortalwon:
Based on the evidence, the verdict is the rom is using some mysterious strong integrity bypass that the devs don't want to share, do you blame them? Very interesting
[Android Software Development] chiteroman:
I think xiaomi.eu ROM + my bugged TEE let me pass Strong. I dont have another explanation for this xD.
[Android Software Development] chiteroman:
There isn't a strong bypass, also I never pass strong in my phone with this rom until a few days ago.
[Android Software Development] pndwal:
🤔... I think you're still confused about TEE... PW
[Android Software Development] zgfg:
Generally, when you unlock BL, you need USNF to pass Device and Basic Integrity

You will not pass by Shamiko only and better don't use MHCP for stock ROMs - these are common facts, please find the thread Play Integrity API and STUDY the OP post for the basics/commons

Also, Xiaomi.eu ROMs do integrate USNF, eg I have two devices with their ROMs (and I don't need USNF) but your case is unique that you pass also Strong Integrity with their spoof
[Android Software Development] chiteroman:
Yeah, and if you see the JSON request of YASNAC in evaluationType you will see only BASIC, but I have BASIC and HARDWARE_BACKED so my TEE is working with unlocked bootloader i guess.
[Android Software Development] zgfg:
TEE = Trusted Execution Environment (it can be used for various purposes, not only for SN or PI API)

PI API provides more or less similar as SN, but the interface is different

If you wanted to say that you pass HW evaluation type - fine, we know, you repeated really many times.

Otherwise, if you wanted to say something more by "you see the JSON request of YASNAC in evaluationType you will see only BASIC, but..." please put the screenshot and circle what do you exactly mean by that
[Android Software Development] pndwal:
There's nothing wrong with BASIC, HARDWARE_BACKED... droidguard collects both types for gms... It's normal w/o fallback... PW
[Android Software Development] chiteroman:
Yeah, maybe I should stop talking, just enjoy this "bug" and wait Google's veredict.

I just wanted to find an explanation and see if it had happened to anyone else.
[Android Software Development] pndwal:
So first, please answer "did you pass on Xiaomi EU & Magisk w/ the gms processes in denylist?" (With nothing more)...

If it works, you could try adding the two processes in denylist with stock ROM again, but try this solution: https://github.com/Magisk-Modules-Alt-Repo/sensitive_props from Huskydg instead of MHPC or Shamiko... (Of course be sure both MHPC and USNF are disabled... PW
[Android Software Development] chiteroman:
Yes, if I disable Zygisk and MagiskHide, only core, I fail Device and Strong.
[Android Software Development] pndwal:
... And you manually included the two processes in denylist and enforced it?? PW
[Android Software Development] chiteroman:
Fresh rom install -> Pass Device, Basic and Strong

A fresh Magisk install -> Fail Device, Pass Basic and fail Strong.

MagiskHide / Magisk Zygisk force deny list / Shamiko -> Pass Device, Basic and Strong.

Only xiaomi.eu rom (Android 13, MIUI 14)
[Android Software Development] chiteroman:
I will try!
[Android Software Development] JovenCalixto:
Hello, I'm new to Magisk, I've recently installed it and every app I have works fine except for my bank's app (even with this module installed). My question is, is there something I can do to solve this problem?

P.D: I've also added the app to the denylist.
[Android Software Development] Nergal di Cuthah:
Which app (it'll help to see whether others have found a solution to that particular app). Have you tried universal safetynet fix (USNF) module? What version of magisk?
[Android Software Development] JovenCalixto:
The app is called "Bankinter" (is a Spanish bank) and my Magisk version is 26.1. Yes, I have installed the module from this post.
[Android Software Development] zgfg:
Yes, there are more things to do. Unfortunately it's not short and easy to describe, hence please do not ask me to write you the guide 😁

But if you go and read like 5-10 last pages in the Magisk General thread, you will see that the same questions are repeating and people who invest the time to search and read they find solutions (except for some rare and/or stubborn 'banking' apps)

Hints:

Shamiko, USNF, App Data Isolation, HMA and if needed DevOptsHide

or even different Magisk fork Delta with Sensitive Props, App Data Isolation, HMA and if needed DevOptsHide

or even Delta with Riru instead of Zygisk (or even Magisk Alpha instead of Magisk Delta)

Best bet: Search or ask for the specific 'banking' app since generic questions are pointless - various 'banking' apps may use different methods (hence different tricks to hide are needed) when trying to detect 'root'
[Android Software Development] JovenCalixto:
Ok, I'll look there, thank you : )
[Android Software Development] zgfg:
If that's the right app (it's usually better to give installation URL to avoid any misleading):

Bankinter Mobile - Apps on Google Play

The bank that sees money the way you see it.

play.google.com

I went up to the login page (screenshot) with absolutely no problem - I just installed the app and opened

However, I have Magisk Delta in the SUList mode... and even HMA was not needed

Hence one of the easier cases
[Android Software Development] chiteroman:
Don't work, I fail CTS and Strong. So the "bypass" only works in xiaomi.eu rom
[Android Software Development] zgfg:
Pretty much expected

Btw I lost track, what is your phone model, chipseta is Snapdragon or MTK, MIUI 13 or 14?

You could inspect service sh script in the USNF module, all props it attempts to change and read their original values in Xiaomi.eu by getprop in Terminal emulator

Maybe (but no guarantee) you find the prop that makes a difference
[Android Software Development] JovenCalixto:
Yes, that's the app, is Magisk Delta necessary to make it work?
[Android Software Development] chiteroman:
Nah, I will stay in xiaomi.eu rom, in my opinion it's the best rom for my phone. It's Snapdragon and run MIUI 14 (Android 13).
[Android Software Development] chiteroman:
Install Shamiko module and add the app into deny list.
[Android Software Development] JovenCalixto:
I tried to do that but it still doesn't allow me in.
[Android Software Development] zgfg:
Not enough on Magisk 26101 - it says that device is compromised when clicked on Login

However, with Magisk Delta it works fine (posted earlier)
[Android Software Development] JovenCalixto:
Yes, that's exactly what happens to me. How can I update from Magisk to Magisk Delta? And are any drawbacks to it?

Thank you for all your help.

P.D: I installed Magisk Delta and it finally works, thank you so much for all your help 😁
[Android Software Development] chiteroman:
Zygisk of official Magisk is detected in some apps, for example, the anticheat Xigncode for Android can detect it and you must use Delta or Alpha to bypass it.
[Android Software Development] zgfg:
So why are you talking that to me?!

Who did post #3610 reporting that his banking app works fine with Magisk Delta (hours before your posts)

Actually, you were the one who gave him the wrong directions, telling to use (official Magisk and) Shamiko (obviously, without even testing yourself first) - I was just answering to yozr post thar you were wrong

Anyway, don't know how about you but I use Delta for for half a year and more
[Android Software Development] pndwal:
This module is broken... @kdragon seems too busy to fix it, so @Displax has built module with fixes... Use link from here:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88149057

... Most members here are using that and just using this thread for discussion. 😜... Maybe everyone forgot... PW
[Android Software Development] chiteroman:
Noooo 😂
[Android Software Development] zgfg:
Maybe you could consider asking on their Forum other users to confirm if they also pass Strong Integrity

Give them link to the PI API Checker and ask those without Magisk

It will be interesting to see if it works for others, particularly on different models with the same ROM - btw, are you on the Stable or last Weekly 14?
[Android Software Development] chiteroman:
My friend also has this rom (but different device) and don't pass Strong. Also I have this rom in the past and I never passed Strong, it starts passing few days ago.

I'm running latest stable MIUI 14.
[Android Software Development] pndwal:
So why are you talking that to me?!

Who did post #3603 etc reporting this??? 🤣 😜 PW
[Android Software Development] pndwal:
@swer45

It's still not clear if you did the test with stock ROM, Magisk and a sensitive props solution

with two Google Play Services processes, com.google.android.gms.unstable and com.google.android.gms, manually added to denylist

(unless I missed your stating that)... Please say, otherwise your results would be expected... PW
[Android Software Development] pndwal:
FWIW, it'll probably work with official Magisk w/ Zygisk, @Displax USNF mod and Shamiko from 27.0... PW
[Android Software Development] pndwal:
If they can crack hardware keys for strongIntegrity revoked by Google (read pass possible without valid keys sent in cryptographic attestations) I guess they will have solved the riddle (busted current strong attestation to device integrity implementation) for all of us! 😋

Got an ingenious dev in mind? 😜 PW
[Android Software Development] chiteroman:
I tried that and it doesn't work. I fail CTS in SafetyNet and Device (and Strong) in Play Integrity.

Only xiaomi.eu rom let me pass Strong.
[Android Software Development] pndwal:
Ta... One more... My memory may be bad, but did you ever pass PI deviceIntegrity with stock ROM w/ Magisk and any USNF? (Something is strange if you don't)... PW
[Android Software Development] chiteroman:
Stock rom don't pass Device but if I install Shamiko + Displax USNF I can pass it, but I can't pass Strong. The same for AOSP roms.
[Android Software Development] chiteroman:
See: https://github.com/kdrag0n/safetynet-fix/issues/269#issuecomment-1455422631

This module block keystore so it's impossible I can pass Strong with it.
[Android Software Development] pndwal:
Of course... That's why I said be sure USNF is disabled (but I see I made a typo... Not ISNF 🥴)... Why do you think I said you need to add gms processes manually and use an independent sensitive prop solution???... Because USNF would do these also if enabled... 🙄 PW
[Android Software Development] pndwal:
That's what I thought should happen... Ta... PW
[Android Software Development] chiteroman:
I will try the same but I will use Magisk Delta + the same module but removing "sepolicy.rule" so GMS can access the keystore.
[Android Software Development] chiteroman:
It doesn't work. I always fail Device so I fail Strong. I give up, I will stay in xiaomi.eu XD.
[Android Software Development] pndwal:
Sorry, in which module did you remove sepolicy rule? PW
[Android Software Development] pndwal:
If you mean USNF, you'd need to disable it's fake keystore registration... I don't understand why sepolicy rules would prevent keystore access... You may be able to disable parts of its functionality including this simply by disabling Zygisk in Magisk... PW
[Android Software Development] chiteroman:
sensitive_props/sepolicy.rule at master · Magisk-Modules-Alt-Repo/sensitive_props

Reset sensitive properties to safe state, take from MagiskHide code - Magisk-Modules-Alt-Repo/sensitive_props

github.com
[Android Software Development] pndwal:
Ah, ok...

I took a look at customize.sh in USNF... Seems if you change it from:

if [[ "$(getprop ro.build.version.sdk)" -lt 26 ]]; then
ui_print ""
ui_print "Functionality is limited on Android 7 and older."
ui_print "Hardware-backed attestation will not be disabled."
ui_print ""

# Remove Zygisk module, but keep props and scripts

to:

if [[ "$(getprop ro.build.version.sdk)" -lt 35 ]]; then
ui_print ""
ui_print "Functionality is limited..."
ui_print "Hardware-backed attestation will not be disabled."
ui_print ""

# Remove Zygisk module, but keep props and scripts

you should be able to use this...

I believe inbuilt root hiding for gms is in Zygisk module part so you'd still probably need to add the gms processes discussed to denylist manually...

🤠 PW
[Android Software Development] chiteroman:
View attachment 5900015View attachment 5900017

I managed to disable TEE key attestation using LSposed (Momo detect It) but It doesn't show Bootloader open or TEE Broken.

Also, this is strange af:

View attachment 5900021

I can still pass Strong even with this xD.
[Android Software Development] DineshValor:
Using LSposed which module?
[Android Software Development] chiteroman:
My custom module, I deleted it but if you want I can redo and share. I don't recommend it because LSPosed it's detected in many apps, maybe I will do a Zygisk version.
[Android Software Development] DineshValor:
Please share, I want to test atleast once your module.
[Android Software Development] chiteroman:
GitHub - chiteroman/AttestationSpoofer: Xposed module that spoofs a fake root of trust in local attestations

Xposed module that spoofs a fake root of trust in local attestations - GitHub - chiteroman/AttestationSpoofer: Xposed module that spoofs a fake root of trust in local attestations

github.com
[Android Software Development] m0han:
TEE Fcuker v1.0 1 does hide TEE, but 'unhides' others.

1. Starting stage

2. TEE Fcuker installed, enabled and rebooted

3. TEE Fcuker still installed, but disabled and rebooted

4. TEE Fcuker uninstalled and rebooted
[Android Software Development] pndwal:
Please give link... 👍 PW
[Android Software Development] chiteroman:
That's why I want to do it as Zygisk module. LSPosed it's detected in many apps.
[Android Software Development] chiteroman:
I updated the Xposed module with better hooking method to don't affect another apps. This afternoon I will work in Zygisk module, I will try to do it.
[Android Software Development] m0han:
Provided by the dev: https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88499109
[Android Software Development] m0han:
But, why same version and build numbers?
[Android Software Development] pndwal:
Name threw me... Thought you'd mentioned a different mod... You name for it?... Couldn't see any reference... PW
[Android Software Development] pndwal:
LSPosed isn't detectable AFAIK if you use 'parasitic' manager and hide modules using Hide My Applist module (hide HMA also). At least nothing detects mine... (Some modules aren't hidden properly as create detectable folders, like XPrivacyLUA.)...

About to try hiding... Please say which detector you use/finds module... 👍 PW
[Android Software Development] pndwal:
... So module breaks key attestation altogether and maybe breaks keystore (from Android 4)?... I don't think hiding is an issue, but unevaluated attestations from Play Integrity API is... PW
[Android Software Development] chiteroman:
This module is for testing purposes and a very basic method of hiding bootloader status. DroidGuard detects hooking frameworks like Frida or Xposed (LSPosed included), that's why you will fail all integrity checks.

So... The solution is using Zygisk of Magisk Alpha + Shamiko. Also Shamiko updated their module for KernelSU, that's another interesting option...
[Android Software Development] chiteroman:
I forget to change that, also the older version I shared here maybe will give problems with Keystore.
[Android Software Development] zgfg:
Ok so, I don't have any other difference than that Momo does no more complain about Bootloader unlocked (+) and that Key Attestation does no more work (-) - you can probably fix that by using Zygisk approach

Magisk Delta, Zygisk, SuList, HMA
[Android Software Development] shoey63:
It does hide unlocked bootloader 👍

However it breaks hiding Zygisk with Shamiko installed (Which normally hides Zygisk)

Also having gms in Play services enabled in the Lsposed module completely breaks API checker

(Tested on Pixel 6)

Probably competing with USNF which requires it to be disabled.

This is the best result I can get

View attachment 5904455View attachment 5904457

View attachment 5904459

Great start though. Keep up the good work 🙂
[Android Software Development] pndwal:
Yeah, I understand this.

But, at least with fallback to basic attestation LSPosed is not detected by droidguard VM or in other signals collected by gms... My point is that the module seems to break basic attestation too.

Yup... But current issue is clearly more than a detection problem... It's broken evaluation itself...

Is it breaking Zygisk modules?...

Everything is failing in Play Integrity API Checker on my normal device with unevaluated results:

View attachment 5904469

🙃 PW
[Android Software Development] chiteroman:
If GMS are active in LSPosed app it will always fail all checks, Droidguard detects hooking frameworks.
[Android Software Development] zgfg:
No issues on my phone with PI API and SN, only Key Attestation is broken (and Momo does no more find unlocked BL)
[Android Software Development] chiteroman:
Which rom are you using?
[Android Software Development] zgfg:
Xiaomi Mi 11 Lite 5G NE, Xiaomi.eu 13 (A12), with Magisk Delta, Zygisk and SuList, HMA (whitelist mode)

That is, I still pass everything (TB Checker, Ruru, etc)

Btw, for my ROM (Xiaomi.eu) I don't need USNF since they integrate in (although it must be based on an old version since my ROM is now 5+ months old - I didn't upgrade to MIUI 14/A13)
[Android Software Development] m0han:
Red is how @swer45 named it. Yellow is how I renamed it, when I found that out.
[Android Software Development] zgfg:
I installed about 4 hrs ago, and it's named Tee hide, as on the screenshot

Are we talking about the same?
[Android Software Development] m0han:
That's probably the update. How I had it when I had it installed (more than 6 hrs. earlier) can be seen in the screenshot.
[Android Software Development] zgfg:
Installation
[Android Software Development] m0han:
TEE ****er v1.0 1_swer45 - md5: 6bf4454389fda72e5210a992d0ff515b

TEE Hide v1.0 1_swer45 - md5: 654ac2b3a40c31f75575daac37b6f4a1

Try both the apk files, if interested.
[Android Software Development] zgfg:
I have the newer one, downloaded from GitHub and being happy with

But if you like the older - or maybe its name 😁
[Android Software Development] zgfg:
Now, from my older phone (Xiaomi.eu 12.5, A11) with Canary 26201, Zygisk, Shamiko, HMA

Differences in Momo with TEE Hide and without (hides BL but opens two other detections)

Everything else is also ok (PI API, SN, all other checkers), just Key Attestation is also broken
[Android Software Development] m0han:
I have neither. I can't help it if you can't read that I 'uninstalled and rebooted'. Also, maybe you weren't here when there was an apk attached to the dev's post, which has since been edited to remove that apk and include source and download links.

This opening other detections was also reported earlier through a combo screenshot.
[Android Software Development] zgfg:
I don't need and didn't ask for help. This version is good for me and I'm not interested to try the older

Don't know for you/your phone