yashsingh1/xdaforums huggingface dataset:
[Magisk] rogerinnyc:
Thanks for the info. I need to update my post -- this a.m., Wallet showed that the device was not secure even tho I had not changed anything in my settings. Grr. Tried a whole bunch of variations (with data wipes of gms, play and wallet each time) and ended up with USNF 2.4 enabled, Shamiko 0.7 enabled and MagiskHide Props Config enabled. No GMS in the deny list. Working for now (although yesterday I had secure messages working in Chase and although I can log in with fingerprint and pretty much do everything else, that is not working today).

Device integrity and Basic Integrity passes with Integrity API Checker; YASNAC, evaluating on a BASIC level passes also. I don't have/use Momo, but I found an apk and it seemed to say my environment was broken??

Will report further after I've lived with this configuration for a while (or if it breaks also)

EDIT: The secure message issue in the Chase App was an AdGuard setting; nothing to do with root hiding
[Magisk] nicky-xda:
I was able to solve the issue by re-installing magisk in magisk app by "direct install" again.

I installed magisk by patching "boot.img" extracted from my ROM and flashig it in orange fox recovery.

Even if it showed magisk installed correctly something must have failed when flashing in recovery before.

thanks once more for your hints!
[Magisk] jimbobmcginty:
I see similar to you. Earlier today I used wallet with NFC to pay, and now wallet tells me "doesn't meet security requirements" - I've changed nothing in between.

Magisk Canary 26101

MagiskHideProps v6.1.2-v137

Shamiko 0.7.1(166)

USNF v2.4.0

Zygisk enabled

Enforce DenyList off

Denylist :

Various bank apps

- Google Play Services / gms

- Google Wallet / walletnfccrel

- Google Services Framework / gsf

I see a weird thing with GSF though, it keeps getting unticked . Any time I open the denylist, it's unticked, even though last time I definitely made sure both gapps and gservices sub-items were ticked
[Magisk] zgfg:
Not weird. Mentioned here and elsewhere that USNF removes GFS from DenyList (it takes care by itself, and it has been that since the beginnings of USNF). You can find how it removes from the USNF scripts

Btw, make sure to use the newer and modded safetynet-fix-v2.4.0-MOD_1.2.zip
[Magisk] jimbobmcginty:
Installing the modified USNF appears to have fixed it, Wallet is back in action, thanks!
[Magisk] cridus:
This sucks, tomorrow (in a few hours actually) I'll go on a trip and since two days ago google pay (or google wallet) started telling me that my phone doesn't meet security requirements... I'd really like being able to pay with the phone again...

google wallet, google play services, google play and (for what it's worth) google services framework are all in the denylist. my bank's app too.

I've updated magisk to the latest (stable) version, updated the universal safety-net fix to the latest ver and installed both shamiko and MagiskHide Props Config. I did disable "enforce denylist" after installing shamiko.

I've cleared all data from google play, google play services and google wallet and then rebooted.

nothing worked.

what else can I try?
[Magisk] zgfg:
Have you updated USNF from this thread or the newer/better/modded version from another thread (please don't ask which thread - every second post is about, just scroll back, where, why, etc)
[Magisk] cridus:
I didn't know there were two different variants. I got it from kdrag0n's github. is there a new better one?

(I'll take a look in the meantime)

edit: it worked, omg thank you so much.

here's the thread with the other, working version of USNF, for convenience for anyone bumping into this post:

https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699
[Magisk] Sorensonn:
My GooglePay stopped working today for no apparent reason. Bank app and other root-sensitive apps were working fine. I was using older Magisk version GPay SQLite Fix, MagiskHide Props Config and regular version of Universal Safety Net Fix.

Now I updated Magisk, turned off GPay SQLite Fix and MagiskHide Props Config, updated Universal SafetyNet Fix to version 2.4.0 mod 1.2, installed Shamiko 0.71 (blacklist enforcing turned off) and....

GPay still doesn't work (root or blahblah). SafetyNet check is OK, Google Play integrity is OK (device and basic integrity, strong integrity fails), I've purged google services cache - same. Bank app and other root sensitive apps work just fine. I removed and added again my debit card, but GPay still refuses to work.

Any ideas? Oneplus 7T Pro.
[Magisk] cridus:
my phone is a OnePlus 7 so if you do all that I did and it still doesn't work, it's pretty odd (I'd expect them to be pretty similar in that).

did you also add google play and google play services to the denylist? I'm not sure it's actually needed but I did that too.
[Magisk] wfred:
I also have a 7T. Try clearing the gpay and play cache & data. You have to reenter the cards, but it worked for me
[Magisk] malkovich78:
The same happened to me on a Xiaomi device.

The solution which worked in my case was unistalling the official Magisk app and installing Magik Delta instead with SafetyNet Fix module version 2.4.0; no need to reinstall Wallet nor re-adding cards.

Regards.
[Magisk] Sorensonn:
Thanks everybody, I will try that. Something must have happened to GPay (update or something?) because GPay stopped working on my wife's OnePlus 8 same day as mine.
[Magisk] TurboLed:
Same for me, I was about to pay at a gas station on Friday and it failed when the day before everything was fine. When I clear the storage, Google Pay says the phone is compliant until I try to add a credit card. Will try updating to latest USNF. Pixel 3 XL with Shamiko...
[Magisk] pndwal:
@Sorensonn, @malkovich78, @TurboLed, others...

SQLite fix hasn't been needed for a couple of years now...

Also, Official USNF is broken (timing issues/failures)... Use @Displax's mod fork with fixes... PW
[Magisk] TurboLed:
Yep, the patched Universal SafetyNet fix solved the issue.
[Magisk] Tester786:
will google pay per hour or week?
[Magisk] AdamLarry:
Can you send me the module?
[Magisk] zgfg:
This was the old GitHub project. There is nothing anymore there - only the Readme that project was moved (but no link). New/valid link below

Edit:

I had to remove the link since I has been requested by developer
[Magisk] tehdomic:
Is the failing MEETS_STRONG_INTEGRITY thing the reason why some Google Wallet payments don't work anymore?
[Magisk] zgfg:
I wonder, how many times in this thread was answered about Strong Integrity

a) 2-5

c) 5-10

d) 10-20

e) 20 or more
[Magisk] tehdomic:
My apologies.
[Magisk] Zeti2000:
When I installed Magisk (no matter wich version), the ”module” and ”superuser” are grayed out and I can click them. Also on settings I’m missing options (screenshot). Am I doing something wrong here? Or whats going on?
[Magisk] beeshyams:
Delete cache of Magisk module and reboot.. May need to repeat twice. For me, this happened with hide Magisk module, in which case also uninstall the hidden (Magisk with new name default being settings)
[Magisk] zgfg:
Check on the main screen Magisk app, on top, does it say which version of Magisk is installed?

Not Magisk app version but Magisk version!

If it says Magisk No, then Magisk is not installed. Maybe you installed only Magisk app - but that is not enough for Magisk

How did you install MAGISK - via TWRP, by patching and flashing boot.img or how (describe)?

Did you have another version of Magisk (properly working) ever installed, and Magisk app hidden?

Eg, you had Magisk Delta (Alpha) previously installed?

Or this is your first time playing with Magisk?
[Magisk] crok.bic:
Likely this happens because the Magisk app can't communicate with the Magisk daemon.. like it is not running or not even installed. Did you patch and flash the image created with Magisk app or flashed Magisk as a zip in recovery? I hope you didn't just installed the Magisk app and start it - and expect that it rooted your device..

Oh, others already answered almost the very same thing.. sry.
[Magisk] Zeti2000:
I tried the Magisk for the first time few days ago and installed (and uninstalled) different versions. None of those worked. Now I have Magisk Delta. It does not say the version I have… I think… but I’ll post the screenshot of the main screen.

I installed Magisk from my phone. Didn’t use TWRP nor flashing boot, etc. I downloaded from Guthub. So maybe I just installed only the app? I’m not good with these things.
[Magisk] shoey63:
What guide did you follow that said installing the Magisk apk will root your device?

You need to do some more research.

In particular, regarding patching the stock boot image with Magisk and fastbooting it.
[Magisk] Zeti2000:
I am following the instructions from the official site but it’s very confusing for me. Also my English is not the most perfect. I also don’t know much of this stuff, nor undersand. So probably I’m missing something and I have no clue what to do.
[Magisk] zgfg:
You have only installed Magisk app - formerly Magisk Manager. That is not the Magisk itself

You don't have Magisk installed yet, no root yet and hence SuperUser, Modules, etc are disabled in the Magisk app (app cannot manage them since Magisk is not installed yet)

Please go to Magisk GitHub, read How to install Magisk - Magisk must be installed by patching and flashing boot.img or by flashing in TWRP (if TWRP is available for your particular phone and ROM)

Please search also in the Magisk General thread (it's out-of-topic for this Google Pay/Wallet thread)
[Magisk] Zeti2000:
Ah ok. Thanks for the reply. One last question, if I flash boot.img, does it wipe all my data from my phone?
[Magisk] zgfg:
Flashing Boot partition does not affect Data partition

But your Bootloader must be unlocked - without, nothing can be flashed (neither custom Recovery/TWRP nor Boot)

Procedure depends on the phone vendor (and model) and it (usually) includes Factory reset
[Magisk] crok.bic:
Unlocking and locking are both including a factory reset to prevent the ability to mess with data that is not otherwise (normally) accessible. Source: source.android.com
[Magisk] cmstlist:
Pixel 6a, haven't upgraded yet to Android 14. Can anyone report that all the same workarounds are just fine on A14 with Magisk?
[Magisk] panni:
I've had Hanseatic Bank Secure working as well, until version 1.12.1. It's the only app not working - even DKB PushTAN and Barclays work. Currently using:

- Magisk Delta

- USNF v2.4.0-MOD_2.0 (Displax)

Got any advice or are you in the same boat?
[Magisk] Homeboy76:
Try using Displax's USNF v2.4.0-MOD_1-3.
[Magisk] panni:
Thank you, tried, but no dice. Safetynet isn't the issue anyways.
[Magisk] panni:
Pretty certain they're using the rootBeerNative implementation. I can't for the life of me figure out what they detect. Has to be some RW mount or native lib.
[Magisk] zgfg:
You must put the RB app to DenyLisst

Btw, it still detects me SE Linux flag
[Magisk] panni:
I have. Why does the RootBeer app detect the SE Linux flag? Shouldn't that be back to enfording after Magisk has done its thing? Ref: https://github.com/KimChangYoun/roo...imchangyoun/rootbeerFresh/util/Utils.java#L17
[Magisk] zgfg:
My ROM is running in the Enforcing mode!

And I have no modules or anything using the Permissive mode

And no other detector complains me about - so that's bothers me.

And when I did my own tests, everything was clean - SE Linux runs in Enforcing mode

IMIO, this lib (improperly?) looks for something that is not really a proof for Permissive mode
[Magisk] zgfg:
Per code, SE Linux Flag Enabled should be caused by

getprop ro.build.selinux == 1

For me, ro.build.selinux is not defined, but RootBeer Fresh reports that 'flag is enabled'

I tried also by putting:

resetprop -n ro.build.selinux 0

and it still reported that 'flag is enabled'

So I finally put (just the opposite of how it should be):

resetprop -n ro.build.selinux 1

And then I got everything green (?!) as on the screenshot - something is fishy in the RootBeer Fresh app

Btw, I have with my ROM:

get enforce

enforcing

hence really SELinux Enforcing mode, therefore all that above how RootBeer Fresh 'detects' or not has nothing to do with reality

Edit:

Btw, I found also a similar issue reported on Magisk GitHub (closed by TJW):

https://github.com/topjohnwu/Magisk/issues/1477

Particularly, see this comment about RootBeer Fresh in that issue:

https://github.com/topjohnwu/Magisk/issues/1477#issuecomment-493933645
[Magisk] panni:
Yeah I'm investigating right now. Decompiled 1.12.1 of Hanseatic and 1.11.1 - there's subtle changes, but nothing major. And they're using parts of the original RootBeer Lib, which implemented the selinux check but never activated it by default. Also they're _not_ including the Apache LICENSE under which RootBeer is licensed.

Currently trying to debug what it actually detects - once I disable the RootBeer Lib check inside the APK completely, it doesn't detect root anymore, so it's definitely something in there. I'm guessing I have an RW mount point somewhere. Nah, I just disabled the detected-screen, not the actual detection itself.

Edit: What's weird is that I can completely hide root from the original RootBeer Sample app, but not from the banking app. But I can disable the root check inside the banking app by editing the APK.

Edit 2: Nope, guessing they're honeypotting with including parts of RootBeer. Their checks seem to be different.

Edit 3: Not really honeypotting, the rootbeer based checks are active as well, but the main culprit seems to be `com.en*kt.sdk.internal`, which does its own thing.

Edit 4: OK, my initial guess was correct. The app has honeypot-like references to RootBeer, but doesn't really use it anymore, or it simply doesn't trigger because of MagiskHide/HMA.

The real culprit is what I mentioned in Edit 3. The en*kt SDK does its own thing to detect root. This is above my paygrade. If anyone's interested, you can take a look at `redacted.java` for example after `redacted` of the APK.
[Magisk] panni:
^ tl;dr: Hanseatic Bank Secure 1.12.1 isn't usable right now, at least not with Magisk Delta, unmount and HMA.

Edit: Yep, it detects Zygisk.
[Magisk] pndwal:
I'd give Alpha + latest Shamiko a go then...

Delta's old POC native bridge loaded Zygisk from Maru fork is better for hiding than standard Zygisk, but LSP Dev's WIP NB-Z from LSPosed/Metagisk (built in Alpha) works to hide Zygisk memory in many more Apps...

Some, like Starling Bank, still apparently detect this Zygisk however, but it seems use of ZygiskNext (just changed from NB to new fuse+ptrace loading mechanism) is confirmed to bypass that detection at least with KernelSU root...

FWIW, Starling apparently detects resetprop utility use and if any module like PIF with it's services.sh scripts or Shamiko is loaded it trips so that's a catch 22...

👀 PW
[Magisk] Lubo99:
i was on magisk alfa for a half a year now and google wallet worked for me untill today when I wanted to pay in the store by phone and known stupid message your phone does not meet requirements. i used usual approach deleted goople play and google play services cache and data and it does not work anymore. Motorola edge 30 android 12 and latest magisk alpha installed plus universal safety fix 2.4.0 displax modded.and zygisk lsposed 1.9.2 . any idea what google changed ?? i have update locker module applied against google play services .gms and google wallet but when i delete all cache and data after a while these suckers load somehow data back. does anyone know why?
[Magisk] BillGoss:
Google made some changes yesterday which resulted in unlocked phones no longer passing device integrity.

You now need to use Play Integrity Fix module (https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/) instead of USNF.
[Magisk] Lord Sithek:
You should follow discussions here and here
[Magisk] Lubo99:
yep chiteroman's fix worked.

yep lol. I posted yesterday posts and 20 minutes later fixed by finding chiteroman's fix LOL
[Magisk] Caipi123:
Latest Magisk 26.4 with Shamiko 0.7.4 bypasses detection of Hanseatic Bank Secure 1.12.1 but fails with comdirect photoTAN 8.13.0

Then tried Magisk Delta 0fe46c5a-delta(26301) with Shamiko 0.7.3, as 0.74 requires Magisk 26.302+ and now both apps are working fine. Don't know if it's a bad idea to use both at the same time, but so far I couldn't find any issues.
[Magisk] Lubo99:
well for me it works with all my bank apps an resolved yestarday's issue with google wallet.
[Magisk] panni:
Wtf, you're right! Shamiko 0.7.3 works with magisk delta and hanseatic. Thank you so much!

Edit: perfect. Hanseatic, Barclays, DKB all work flawlessly with delta, HMA, Pif 9.9 and Shamiko 0.7.3

Edit 2: ****, Google pay just tripped with that combination.

Edit 3: OK, that was a coincidence, Google updated their detection. Updated Pif, deleted data from wallet, gsf, play store, play services and now it works again.
[Magisk] janehull:
"This module works around hardware attestation and updates to SafetyNet and Play Integrity CTS profile checks. You must already be able to pass basic CTS profile attestation, which requires a valid combination of device and model names, build fingerprints, and security patch levels."

Just found this yesterday; haven't played wit it yet.

GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk

Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix

github.com
[Magisk] zgfg:
OMG, that module is a way old and not up-to-date with Google's constant changes to pass Device Integrity

Search for the Play Integrity Fix (PIF) module on GitHub or for it's XDA thread and use that module (instead of MHPC and/or USNF)
[Magisk] raphytaffy:
Fresh Pixel 8 owner dropping by this thread and man, the acronyms!

What is everything that I need to get up and running?

- Magisk or Magisk Delta?

- Hide My Applist

- Play Integrity Fix

- Shamiko

- Universal SafetyNet Fix

Do I need all of the above? If so, which versions?
[Magisk] panni:
That depends. If using the latest Magisk Delta and want Google Wallet, you only need:

- Magisk Delta (now "Kitsune Mask")

- Play Integrity Fix (latest)

If you have specific banking apps that still detect root, add:

- Hide My Applist

Shamiko doesn't seem to be necessary with latest Delta/Kitsune.
[Magisk] raphytaffy:
Thank you.

What are the steps to install Magisk again? I thought I remembered the steps.

Here's what I did:

Downloaded factory image and extracted the boot.img file from image.zip

In Magisk Delta, clicked Install > Select and Patch a File > boot.img

Copied the patched.img file to my PC

adb reboot bootloader

fastboot flash boot patched.img

fastboot flash boot magisk_patched-26401_ephVP.img
Sending 'boot_b' (65536 KB) OKAY [ 1.506s]
Writing 'boot_b' OKAY [ 0.668s]
Finished. Total time: 2.178s

Everything completed successfully, but Magisk is not showing as installed.
[Magisk] zgfg:
Probably a classical issue. If you previously had Magisk and you did Hide Magisk app - then you still have the old Magisk app, under different name and with random package name, and that one 'sees' your new Magisk, not the new Magisk app

Find and uninstall the old Magisk app and reboot

In that case you would still have the root and you can check that through Terminal emulator/ADB
[Magisk] raphytaffy:
I have not installed Magisk previously on this phone.

Edit: patching init_boot.img instead of boot.img worked and Magisk Delta is now installed properly. Instructions were not very clear on whether we should use init_boot.img or boot.img if both exist in the factory zip.
[Magisk] raphytaffy:
Thanks for the help.

I have installed:

- Magisk Delta (latest)

- Play Integrity Fix (latest)

- Hide My Applist (latest)

I have not modified any settings other than turning Zygisk on in order to install the Play Integrity Fix module.

Checks are passing with YASNAC and the Play Integrity API Checker.

Are there any other settings I need to do before trying to set up Google Pay?
[Magisk] panni:
I would create a template in HMA for all your banking apps, that hides the hidden Magisk Manager and HMA. And obviously add GPay (and related) to Magiskhide.
[Magisk] zgfg:
That depends on the phone. New Pixels but it seems also some new Xiaomi models need patching init_boot.img

Things always change
[Magisk] raphytaffy:
Making sure I understand the correct steps:

Magisk app > Hide the Magisk app

Hide My Applist > Template manage > Create a blacklist template > Add hidden Magisk app + HMA

Should I activate the HMA module? It is showing as Module Not Activated > System service not running

Double checking the correct steps:

Magisk app > Enable MagiskHide

Magisk app > Configure MagiskHide > Show system apps > Select Gpay and related apps

Anything else I'm missing?
[Magisk] zgfg:
That's a paranoia😁

If you hide Magisk app by HMA, then no need for Hide Magisk app in Magisk app.

Specially if Delta or Alpha that already have diff package names than official Magisk app
[Magisk] panni:
Probably, yeah. Does it hurt, though? I still use the old HMA template which also hides the hidden Magisk app, as DKB PushTan detected it in the past.
[Magisk] raphytaffy:
I'm confused on how to use HMA. Do I need to do something to activate the module?

Is this all I need in my blacklist? I am trying to get Cashapp working.
[Magisk] beeshyams:
See this guide
[Magisk] raphytaffy:
Thank you! Cashapp is working now. I'll ask further questions in the Hide My Applist thread. Appreciate the help!
[Magisk] raphytaffy:
If I'm using Gpay, do I need to configure it in Hide My Applist?

This is what my current configuration looks like.
[Magisk] OGBenn:
I've been using google pay with no problems for the past week until it suddenly stopped working today or yesterday..what gives?

I'm running pixel experience on poco f3 5g, with magisk installed. Here's my config:

Am I missing something from my setup?
[Magisk] zgfg:
Watch in the PlayIntegrity Fix thread to be up to date with the banned spoofs

And/or check in Modules tab to update the PIF module
[Magisk] sawdoctor:
Little tip , the bundled fingerprint gets banned at least once a week so if you follow one of the guides and find your own fingerprint it's likely to last a lot longer and save you a lot of hassle in the long run
[Magisk] dmlykag6:
Hi guys my Google pay stopped working again. There no update button on the module. It's up to date play integrity 14.4
[Magisk] zgfg:
Mine for your 'own' custom pif json, and when Google bans the one in the module, your spoofs will still pass

Instructions and tools are in the PIF thread
[Magisk] dmlykag6:
Hey bro I have no idea what any of the things you just said. I am new to all this and got sent here for help and don't really understand how all this works
[Magisk] sawdoctor:
Have a read of this thread, the bundled fingerprint gets banned every other day so safest to use your own.

Also it's a really good idea to read the release notes and wiki in the play integrity fix download section. It's extremely dangerous flashing things on a rooted device without reading the release notes you could brick your device

How to search & find your own fingerprints [noob friendly]: A Comprehensive Guide w/ tips & Discussion for Complete Noobs (from one)

It seems Google has banned more than 95% of custom fingerprints, so this thread/guide has kind been laid to the wayside. But it's still a great resource to understanding the foundations of fingerprints and all that... This is for any/all utterly...

xdaforums.com
[Magisk] ihavenolifee:
After a working fingerprint and play integrity passing, I'm getting an error when i try to add a new card to Google wallet.

It says that i have a connection error and it occurs even if adding the card directly from the banking app. Google wallet itself doesn't show any issues either. Any ideas?

Edit

Going to try to be a bit more thorough to hopefully get some help....

Pixel 7

Stock Rom

Magisk Canary from huskydg - Kistune (26404)

Trying to directly add any cards and have that issue that says "Check your network connection, Make sure you're connected, then try again"

Have tried adding different bank cards, and have tried adding it directly tfrom the banking app, where I don't have to enter the info of the card.

Cards are active and work fine too.