yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Extreme_Ninja2099:
Awesome! I'm glad I asked before switching to a Android 13 ROM. What's wrong with the regular V2.3.1 from kdrag0n?
[Android Software Development] Extreme_Ninja2099:
Do

Nvm I found the link. V2.3.1-MOD_2.0 download link: https://github.com/Displax/safetynet-fix/tree/integrity
[Android Software Development] Gordietm:
It hasn't been updated yet.
[Android Software Development] zgfg:
Everything was written, described and discussed many times in this thread
[Android Software Development] Erdy232:
For some reason, it doesn't work on my Pixel 7.

After installing the module, I pass the CTS profile match. But shortly after some time, it fails and I cannot use Google Wallet or install Netflix.

Edit: I don't fail the CTS profile match anymore after updating to the new OTA, which removed the root from my phone and then re-flashing Magisk.
[Android Software Development] usernamejames:
For Netflix you need magisk hide modules besides safetynetfix
[Android Software Development] TioCareca:
In my poco f1 A13 i got Netflix with just safety net fix
[Android Software Development] Slim2none4u:
You just need to get play store certified. Safetynet fix is all you need. Turn on airplane mode and clear cache on play store and play services and gpay. Restart phone. Turn air plane mode off.
[Android Software Development] manan001:
Banking app like HDFC has updated their app. Now when we start the app it checks for root check and immediately redirects to web browser with root alert. I think module or magisk needs to be updated to make work with such apps. Note: I have magisk in hidden mode as well as app is hidden and

Universal SafetyNet Fix 2.3.1 module activated but app does not work.​
[Android Software Development] Slim2none4u:
Add said app to magisk deny list and then clear cache/data. Restart your phone.
[Android Software Development] manan001:
I did but latest hdfc app does not work.
[Android Software Development] Homeboy76:
After, you did it "Add said app to magisk deny list and then clear cache/data. Restart your phone." Is your device certified? It may take up to 24h for your device to get certified. Also, you should enable the Denylist.
[Android Software Development] manan001:
Yes i can see device certified but app redirects to attach page. App added to denylist. But same issue.
[Android Software Development] zgfg:
This is out of topic for the USNF module. USNF module is to pass SafetyNet, and the moded version, to pass Play Integrity API (Google's successor for SN)

Various 'banking' apps use various additional techniques to detect 'root' - from relatively stupid things like looking for Magisk app, TWRP folder, USB debugging mode to more complicated like looking for LSPosed and its modules or even for Zygisk, etc

If you know (of course, they don't tell you, you have to experiment), you can try to hide Magisk app (disable it or even uninstall it), to rename or delete TWRP folder, to use Hide My Apps module (to hide Magisk app and LSPosed modules apps) for LSPosed, etc.

Certain custom ROMs (or just custom Kernels) are built in debug mode - and that can be just another way for a 'banking' app to find that you are not using the certified, stock ROM

Sorry, I will not go into the details or guide how to use Hide My Apps, etc - there are really tens and tens of posts in the general XDA Magisk thread about all that

There are posts with particular 'solutions' (users found by experimenting for this or that app which technique to use to hide 'root' from that app).

One has to read there, search, study, experiment himself, etc

However, and that has also been discussed in the Magisk General thread (with names/examples of those apps - you should look there, maybe your app is among them) there are now apps that look for Zygisk and unfortunately that cannot be hidden (by the out-dated Shamiko module)

Apparently, one must not use this new 'official' Magisk with Zygisk and DenyList but the custom fork (it has its own thread on XDA) Magisk Delta, that uses the 'good' old MagiskHide (instead of Zygisk+DenyList) to 'hide root' from those apps

---

All together, USNF module is not a module to hide 'root' from the x-y-z app, but to pass SN (and now its successor PI)

SN/PI APi is just one point on the checklist what 'banking" apps may use when they look for 'root' - for various techniques they use, one must apply various particular solutions to hide

All that is out-of-topic for this thread, and too big and complex to be guided in one post.

One has to look into the threads and posts (by searching, etc) where these things have been already and extensively discussed

It's the game - today you hide, tomorrow they will discover new way to detect

TJW works for Google and he had distanced himself from hiding the 'root,'

To make things worse, it seems that there are now new sorts/versions of 'banking' apps that detect Zygisk, with no known solution to hide - except for going back from this new Zygisk+DenyList to the old MagiskHide (but again, you could not blain TJW, hiding from root is not his business anymore)
[Android Software Development] ipdev:
I fully agree with what you said. (y)

Except going back to MagiskHide. 🙁

MagiskHide had it's own issues and John lost interest in it well before he started working for Google.

Even before his stint at Apple.

Cheers. :cowboy:
[Android Software Development] ipdev:
I do not have a HDFC account so I can not login but, I was able to get to the initial account login without warning. 🙃

Not sure if I got beyond the "Security Threat ALERT!" screenshot or not. :unsure:​

View attachment 5750927 View attachment 5750929 View attachment 5750931 View attachment 5750933

Cheers. :cowboy:
[Android Software Development] manan001:
O got the solution removed magisk and installed magisk delta.
[Android Software Development] wugga3:
I try to read everything here almost every day... I'm no a developer.... But I still need to ask:

The reason why Magisk Delta would work for this app when Magisk stable wouldn't??? Please direct me to the appropriate reference that I can read which might/might not make sense to me. Thanks
[Android Software Development] 73sydney:
The very very, and i repeat, very simplistic 30 second answer is that Magisk Stable had all its hiding code removed (on purpose even), as TJW put it, to make Magisk get out of the way of itself, and to make it actually more powerful (for applications beyond hiding necessarily), whereas "legacy" Magisk forks, like Delta still include the code to hide processes.

Magisk stable can actually have modules for hiding (such as Shamiko) run under zygisk, but it can be, as noted hit or miss, as theres no 100% way to hide zygisk, given how it operates in the way and at the level it does

Some people get very territorial (and waaaay too emotional at times) over this or that fork, and TJW took 100% more flack than he should have making the change, but those folks need to know that neither fork is immune to or exempt from being made redundant

Im sure @pndwal will no doubt come down from his bell tower to provide more relevant material and links (he has ALL the links)

Also probably worth mentioning, because it really isnt mentioned or highlighted enough, that theres more to Magisk than just hiding stuff, case in point i have about 14 self made modules, just 2 of them in any way rely on the hiding abilities provided by zygsik and shamiko
[Android Software Development] pndwal:
Seems many are assuming Play Protect certification will fix detection for Netflix etc... And indeed Netflix suggests checking this themselves...

However all such apps are migrating from depreciated SafetyNet to new Play Integrity API... Not sure, but I'm guessing Netflix will require this by now...

Last time I checked, Play Protect was still using old S/N API, so it's possible to have 'Device is certified' while newly required PI deviceIntegrity is failing... A clue is when updates for affected apps no longer show up on Play Store which filters according to the attestation label used by hosted apps...

So assuming official USNF is enough since 'Device is certified' is not longer good policy...

Some users won't need to update to the @Displax modded USNF fork which solves this since further HKA enforcement bypasses aren't needed to pass deviceIntegrity on some devices, especially A10 stock and earlier. However I strongly suggest using Play Integrity AOI Checker app to ensure this verdict label passes. If not, install the Displax forked USNF w/ extra deviceIntegrity fix (essentially Universal deviceIntegrity PI fix now) as apps will often say 'root is detected' when deviceIntegrity is simply failing...

Of course apps may also add their own new custom detections in addition, but don't make assumptions before at least passing deviceIntegrity, taking Hide the Magisk app Magisk option and adding app in denylist... I'd be substituting denylist for Shamiko (deny-->hide) also...

🤠 PW
[Android Software Development] manan001:
Finally i managed to get this by using magisk delta latest version. All set well.
[Android Software Development] pp085ster:
Been having this issue since day 1 on my Pixel 7 trying to have root and contactless working side by side. Whenever I flash the USNF MOD 2.0 via Magisk, I gain the ability to pass 2/3 integrity checks, however I lose the ability to enter my Google settings page (clicking on settings -> Google does nothing), and GPay stops working altogether - cannot access the "wallet" section. I have tried flashing USNF MOD 2.0 then going into airplane mode, clearing cache for Google Play Services, Google Play Store and GPay, rebooting and deactivating airplane mode.

This also hasn't worked. Does anyone have any idea as to what is going on here? It looks like some conflict with a Google service, but have no idea how to troubleshoot it.

Thanks in advance!
[Android Software Development] rocapillon:
I tried what you say here, USNF as USNF mod 2.0, I tried to remove from the deny list, add, and nothing, I tried the solutions that I saw here, in play store it comes out certified, but in wallet it says that I cannot pay

Sorry for my bad English

Edit: A week ago without further ado I was left without a fingerprint, I already tried another module but it must be something systemic, I couldn't get it to work again, I put it in case it helps

View attachment 5756013View attachment 5756015
[Android Software Development] 73sydney:
I think you missed the part where you ask an actual question, and provide details

We dont troubleshoot from screenshots alone here....

Also you seem to have missed reading from any of the last dozen or so pages which would tell you that its no longer just about passing safetynet, and what the fix is...

You should get into the habit of reading the last pages of any thread before posting a query, as generally if youre experiencing an issue (one thats usually a dramatic change) then others are too, therefore an answer probably has already been provided.

Posting just a screenshot, no info and expecting people to jump to attention for you will not go well for you here...youre expected to do some work yourself..

This will get you up to speed, but please, next time, dont be lazy...

https://xdaforums.com/t/discussion-...cussion-thread.3906703/page-149#post-87481637
[Android Software Development] rocapillon:
I'm sorry, I uploaded the photos from my mobile, I was going to edit the publication from my PC, but I had a mishap and I couldn't, I read from page 110 and I don't see a solution.
[Android Software Development] 73sydney:
"I'm sorry, I uploaded the photos from my mobile, I was going to edit the publication from my PC, but I had a mishap and I couldn't, I read from page 110 and I don't see a solution."

Okay, fair enough, but sometimes its best to just use a PC, i wouldnt dream of doing all i do on XDA from a mobile :)

The issue is the most discussed in the thread in particularly the last 12 pages, the link i provided was maybe 2 pages back
[Android Software Development] rocapillon:
Automatic AI Translation brought to you by...

"I'm very sorry, I uploaded the screenshots from my cell phone so as not to transfer them to the PC, I was thinking of editing to add information, but I had a physical problem and I couldn't use the PC, now I saw the notification and I know I did wrong, until next time that has the text I will not upload the photos

Thanks for the warning"

Lo siento mucho, subí las capturas de mi celular para no pasarlas a la PC, estaba pensando en editar para agregar información, pero tuve un problema físico y no podía usar la PC, ahora vi la notificacion y se que hice mal, hasta la proxima que tenga el texto no subire las fotos

gracias por la advertencia
[Android Software Development] zgfg:
Please, this is English forum, use Translate if necessary to post in English
[Android Software Development] nikitasius:
perfect !
[Android Software Development] rocapillon:
I'm using a translator, I don't know how it was put in Spanish, now I change it, I'm sorry
[Android Software Development] kbarb:
Pixel 4a

Android : A12

ROM : sunfish-sq3a.220605.009.a1-factory

I'm not sure if I have a problem - yet - but wanted to check for futureproofing as it's the first time I've been on this particular rooting adventure.

The objective is to root the phone for its benefits, and finally install LSPosed framework so as to install XPrivacyLua module.

I don't do Google Pay, banking or Netflix on my phone - yet.

But I'd like to avoid screwing up the phone for regular use though.

Questions :

From the screenshots below, is this as good as it gets ? Or am I going to run into obvious problems.

So far, Play Store works and says "Device is Certified".

What is the consensus for exactly what

of Google

to put in Magisk DenyList (gms, etc) ? (Besides some banking app, whatever).

I see advice all over the place, and finally gleaned it's probably now handled by Universal-SafetyNet-Fix-MOD (USNF) ??

Anything else I should do, like spoof the device w/ MagiskHide Props Config ?

The steps/process I performed :

Unlock Bootloader with ADB commands

Install Magisk v25.2 and patch boot.img and flash it

Enable Zygisk

Install Magisk modules :

-- Universal SafetyNet Fix (USNF) : safetynet-fix-v2.3.1-MOD_2.0 (Displax version)

-- Shamiko-v0.5.2-120-release

Hide Magisk

(Turn on Airplane Mode); Clear data for G-Services & G-Play Store, and ReBoot, (turn off Airplane mode.)

Magisk config :

Nothing in DenyList (waiting for advice)

Denylist set as not Enforced (because Shamiko installed)

View attachment 5758797

View attachment 5758799
[Android Software Development] pndwal:
View attachment 5758901

View attachment 5758903

Have you put these in denylist?

Yup, put nothing Google other than Google Pay/Wallet.

No need...

You may need to hide many apps associated with root etc from bank apps using Hide My Applist LSPosed module... HMA itself and other xposed modules can also be hidden using HMA.

Nb . While XPrivacyLua module will also be hidden to such app detection, Applist Detector still finds it in Environment checks (using classpath?) AFAIK there is no way bypass this detection.*

View attachment 5758907

View attachment 5758905

👀 PW

Edit: - Looks like simply renaming this folder:

/data/system/xlua

and building module to use the new one could work...
[Android Software Development] m0han:
Would such a thing work for the ones in the attached screenshot too?
[Android Software Development] zgfg:
You need to use HMA (Hide My Applist) to hide LSPosed and HMA (and all other LSPosed modules) from Ruru

Always the same:

You install new checker like Ruru, TB-Checker or whatever, go back to DenyList and HMA and enable hiding from them - your previously enabled hiding from Momo or else cannot help for Ruru, TB-Checker or some banking app, etc.

For each and everyone, you need to enable hiding from that app

---

Maybe you also need App data isolation module - I don't remember for what kind of hiding I needed that module, but it won't hurt
[Android Software Development] pndwal:
If these relate to an actual folder, I guess it would work... In this case removing the folder does revert the detection... PW
[Android Software Development] rocapillon:
Without making any changes, just like that I enter the wallet and it tells me that I can now pay without contact, I go to the touch-to-pay configuration and if the ad no longer appears, I did nothing, I don't know how it solved itself, the fingerprint It still doesn't work, from the test menu, it says that the fingerprint hardware is not available, so I can't use biometrics, but I can pay, which is more important
[Android Software Development] m0han:
Screenshot showing folders attached. But, I don't get this part:

simply renaming the folder and

building module

to use the new one... How is this done?
[Android Software Development] 73sydney:
App Data Isolation (a module i wrote/packaged for and credit (shifted any blame for) to @Stillhard after @Stillhard found the method and then hospital passed to me by telling people i would make it, did i ever really say thanks for that @Stillhard? :)) was a kind of additional tool to try and assist block some Libc and Syscall stuff by blocking access to apps private data directories

I found a downside pretty quickly, i forgot to toggle it off once before running my Migrate backups, and wondering why the backups failed....theres now a warning about this on my github repo for it

I dont currently use it personally
[Android Software Development] pndwal:
This was a general comment... I wanted to revert detection after uninstalling xprivacylua since I'm finished with it but uninstall doesn't properly remove the folder...

After discovering this I surmised that since Applist Detector is apparently looking for this folder, using a different folder might work with the app active.

Understanding how the app/module interfaces with this folder would be necessary in that case; one would need to fork the module, locate the commit(s) specifying the original folder name and adjust these before initiating a build...

I have very little experience with this, but I did build a Magisk fork using GitHub Actions to make a workflow a while back and it was pretty easy...

@ipdev, others may have more tips to offer you... 🙃 PW
[Android Software Development] kbarb:
Sorry for going awol - had to fix a roof problem.

I really appreciate the help & advice though !

That was another question of mine . . . I should I put all the root-checker type apps in the DenyList ?

That's because they could actually tip off some app that's doing root-checking (banking, etc.) - that I have a rooted/tampered-with system ?

From reading the Hide-My-Applist "About", it seems like that's it, not that I'm just going to get a good root-checking "grade".

Thanks again for the advice !
[Android Software Development] kbarb:
So to summarize then, for my questions (post #2,450) . . .

From the screenshots below, is this as good as it gets ? Or am I going to run into obvious problems.

<snip>

What I meant there is, I'm not to expect a perfect score w/ Play Integrity API Checker, Oprek, etc - right ?

Not going to get "Meets Strong Integrity", etc.

What is the consensus for exactly what

of Google

to put in Magisk DenyList (gms, etc) ?<snip>

So, basically, nothing of Google

Anything else I should do, like spoof the device w/ MagiskHide Props Config ?

No, except install Hide-My-Applist, and hide "many apps associated with root", including LSPosed module, HMA itself.

Thanks again !
[Android Software Development] pndwal:
Yes, but only to see if you can bypass their detections!; Object is to test the same hiding you apply to banks on such apps...

No... Banks etc may use tricks to detect presence of these apps but don't care / can't know about their results... Denylist (especially when hijacked as hidelist by Shamiko) only hides root traces etc from apps in list...

You can use HMA to prevent applist detection and put all such root/mod associated apps in a template to be applied to individual bank apps etc as I've said...

Yup... That's the province of HMA, not denylist... Don't confuse the two...

😉 PW
[Android Software Development] pndwal:
You can get perfect scores with many, unusual with Momo however, by applying same hiding to these you use for banks... add in denylist, hide apps from some detection apps w/ HMA etc... See post above...

No... It's roughly equivalent to S/N API's CTS Profile Match pass w/ HARDWARE _BACKED Evaluation type enforced...

... Unless using Google Pay/Wallet... Add just like a bank...

I can't know what custom detection methods banks, games you use will employ... worry about detections as they arrive... There'll always be something new arising...

You've got the basics... Hide all LSP modules w/ HMA... For LSP module, don't use full manager app; ensure you use 'parasitic' manager... No need to put in HMA if you do this...

🤠 PW
[Android Software Development] creeve4:
I haven't kept up on this thread over the last few months and recently upgraded my phone to A13. I see that there is now a MOD version of this module, but I am not sure what the best method currently is for passing SafetyNet/Play Integrity.

Will someone please enlighten me on the current best practice for passing?
[Android Software Development] zgfg:
Currently, it's not really about passing SafetyNet but passing the Google's successor Play Integrity API (integrated to the Google Play Services since this summer - already used by Google Wallet, and by more apps that are switching from SN to the PI API checking)

That's why safetynet-fix-v2.3.1-MOD_2.0.zip is needed, to pass both the old SN and the new PI API (btw, during the next year, Google will stop supporting the old SN)

You can find more in this thread (posts over the last couple of months) and the Google Wallet thread also here on XDA
[Android Software Development] _litz:
Any idea on what we'll be able to do in the post SN world?
[Android Software Development] pndwal:
Post S/N world is from June 2024...

Banks etc must have current apps migrated to PI by June 2023, so for most users 'post S/N' will occur before then; probably most have already migrated... S/N gets switched off for banks / users of obsolete apps in June 2024...

You won't need to do anything assuming you already pass PI deviceIntegrity... If banks start using strongIntegrity verdict the game will be very different, no doubt over for custom modders... PW
[Android Software Development] V0latyle:
Not sure whether this is the appropriate place for this...

My wife's Pixel 5a won't install Hulu from the Play Store. Says her device is incompatible. Stock firmware rooted with Magisk 25.2, no system mods - only systemless hosts module and USNF 2.3.1 Mod 2 by @Displax

Did some troubleshooting and discovered that even though Play Integrity BASIC and DEVICE integrity were both passing, YASNAC showed CTSProfileMatch as FAIL and evaluationType as HARDWARE_BACKED. Disabled USNF, rebooted, reinstalled USNF module, YASNAC now showing BASIC evaluationType, both CTSProfileMatch and Basic integrity pass. Didn't fix it...

Play Protect says device is certified.

The only difference between this and my Pixel 5 is I used to use MHPC, which is now disabled in the Magisk modules tab; I'm using the same modules (systemless hosts and USNF 2.3.1 Mod 2) but Hulu is available for download in the Play Store.

Ended up working around it by sideloading Hulu, which worked fine. Still wondering why Play Store is giving me trouble. Ideas?
[Android Software Development] rodken:
Some folks that I know that have the Pixel stated that when the bootloader is locked, they are able to install Hulu from the Google Play Store.
[Android Software Development] V0latyle:
Did you maybe mean this the other way around - as in, when the bootloader is unlocked,, they're unable to install Hulu from Play Store? I would imagine anyone with a locked bootloader (and presumably stock firmware) would have no issue installing anything from the Play Store

I'm hoping we can dig a little deeper into this and figure out what the issue is.

I would try fixing the device fingerprint with MHPC but I don't know if that would interfere with the Play Integrity fix?