Yes. Cleared cache & data and set everything up afresh. All fine now..... device app bug or something in your device.... confirm your side.
Yes. Cleared cache & data and set everything up afresh. All fine now..... device app bug or something in your device.... confirm your side.
It's supported upto android 13 and currently I'm using LSposed with android 12.@DineshValor does Privacy Space support android 10 with Lsposed? Also can share the link to download the module? I'm finding a old one which mentioned support for Android 9
following this guide, landed me into bootloop. Is there a brief guide - blog or video?Requirements:-
- Magisk v25.2
- LSPosed v1.8.6
- PrivacySpace v1.3.7 (LSPosed module app)
- Enable Zygisk (Enforce DenyList - Disabled) under Magisk (+ download some Magisk module as shown in screenshot¹)
View attachment 5865833
Follow below steps to fix "This functionality is not available due to security concerns with your device" in Paytm (Tap to Tay):-
1. Download frest original Paytm app or clear data & force stop.
2. Open PrivacySpace app/module under LSPosed.
3. Hidden Apps > select Paytm (+ all other modules such as Lucky Patcher, etc as show in screenshot²).
View attachment 5865841
4. Blacklist > select Paytm.
Note: If u want to recieve Paytm app update in Play Store then select Play Store in "Connected with Others" to unhide Paytm app for Play Store.
View attachment 5865845
5. All Set, Try your Luck Now, and do not forget to let me know if it's work for you too.
Sorry about that issue, but right now I'm busy in some other stuff, i will make sure to create a brief video as a demo, plz grant me some time.following this guide, landed me into bootloop. Is there a brief guide - blog or video?
Sorry about that issue, but right now I'm busy in some other stuff, i will make sure to create a brief video as a demo, plz grant me some time.
Can't say I've had exactly that behaviour... My bank app doesn't get opened to verify...Hi everyone
I've had to factory reset my phone (Xiaomi Mi 9T) recently, and since then I am unable to verify my payment cards for contactless payment on Google Wallet, on any rom that I tried (even the ones that pass SafetyNet by default).
The weird thing is that I don't get any error messages or security warning, but the verification process simply goes in an infinite loop:
1) I add a card
2) The Wallet app says it needs to verify the card with the bank, it asks me how I want to verify
3) I chose "use the bank's app"
4) The bank's app opens, I verify the card, it says everything is good and the card can now be used for contactless payments
5) I go back to Wallet and... it asks me how do I want to verify the card again! (in other words: I'm back at step 2)
Has anyone here experienced something like this? I've been tinkering for hours now, switching roms, installing magisk and various combinations of modules, but to no avail. Any suggestions?
Thanks for the info, is there an app I can use to check the status of Play Integrity?Can't say I've had exactly that behaviour... My bank app doesn't get opened to verify...
However SafetyNet API is of course now deprecated, so are your ROMs up to date and passing new Play Integrity API's deviceIntegrity verdict?
Nb. If using Magisk, late official Universal SafetyNet Fix module is broken... You need @Displax's fork... PW
Of course. It has been described in this threadThanks for the info, is there an app I can use to check the status of Play Integrity?
Thanks a lot for your help.Of course. It has been described in this thread
Search for Play Integrity on the Play Store and you will find the PI API Checker
Or, Google Play Store app itself (Developer options) can be used
Strong Integrity is not relevant and you will never be able to pass with the Bootloader unlockedThanks a lot for your help.
Indeed, the strong Integrity check is failing, only the basic and device ones are passing. I'll try to install magisk and the modded module and see if it helps. Should I use original magisk? I've seen the Delta version recommend elsewhere![]()
Sorry, I've been reading about this stuff all day but a lot of the information out there is at times contradictory and I have yet to find a single case similar to mine (i.e: where no error occurs but the Wallet app simply refuses to advance to the next step of the verification wizard).Strong Integrity is not relevant and you will never be able to pass with the Bootloader unlocked
Again, before posting/,asking, please read and be familiar with the common facts
Ask here?:Can P7P users with GPay working please chime in with the following:
OTA version:
Magisk version:
Universal SafetyNet Fix version:
+any other relevant info
Thank you in advance!
Can P7P users with GPay working please chime in with the following:
OTA version:
Magisk version:
Universal SafetyNet Fix version:
+any other relevant info
Thank you in advance!
With the deny list enforcement disabled in Magisk manager, e.g. Revolut does not work. Therefore, when you are adding payment cards to Google Wallet, the "Enforce Denylist" option in Magisk manager must be disabled, and after adding your cards to the wallet, you can re-enable it for the Revolut application to work. A very simple trick ;-)Just a quick update for you guys. The "Enforce Denylist" option must be turned OFF, otherwise gpay won't work. I tried and tested this. Don't worry if you don't pass device integrity, as long as you have a checkmark for "your phone meets security requirements" you are good to go (see image). View attachment 5852701
Denylist is not proper root hiding; it's a little of MagiskHide code repurposed for the purpose of reverting/preventing Magisk modifications in listed processes... This is no longer a function for the general modder, but for the Android developer, security researcher etc...With the deny list enforcement disabled in Magisk manager, e.g. Revolut does not work. Therefore, when you are adding payment cards to Google Wallet, the "Enforce Denylist" option in Magisk manager must be disabled, and after adding your cards to the wallet, you can re-enable it for the Revolut application to work. A very simple trick ;-)
Unfortunately Revolut Bank app says that it won't work on rooted phones when Enforce Denylist option is disabled. I must confess that I'm still using Magisk 25.2 with application name changed. Because some dumb apps find rooted phone based on an installed app called "Magisk". Also, is Magisk 26.1 fundamentally better than version 25.2?So for those wanting proper root hiding, Denylist must necessarily be disabled and a suitable hiding module utilised... This mode works well for GPay/Wallet and much better to bypass detections in other bank apps etc.
I believe GPay/Wallet would usually fail after some time unless you still pass Play Integrity deviceIntegrity verdict because ROM integrates SNF or it's own spoofs for this...Thanks to pndwal's suggestions, I confirm what rogerinnyc wrote above. On my S10e I'm using Ambassadii ROM 5.6 and Magisk 26.1 the Zygisk option is enabled. I set denials for GPay/Wallet, Google Play Services, banking applications and the Allegro application (a popular shopping platform in Poland, something like eBay). Also, I have the safetynet-fix-v2.4.0-MOD_1.2 module installed in Magisk. Without the Shamiko module installed in Magisk and without Enforce Deny List enabled, a strange thing happens. Namely, the GPay/Wallet application worked, but the banking applications detected the root.
Having Play Services, specifically the droid guard/attestation process com.google.android.gms.unstable in active denylist breaks Zygisk based USNF builds (note, it will remove these from denylist on next boot for this reason) because DenyList reverts/prevents Magisk modifications in listed processes unlike old MagishHide. (It's really now a development tool, not a hiding tool.) In this case USNF injects code in gms to register a fake keystore to cause the fallback to basic attestation that's it's key function, so we can't hide root front gms using Denylist... Shamiko on the other hand is a proper hiding module and simply uses denylist (for convenience) as a hidelist, so it doesn't break USNF in this case...When Enforce Deny List was enabled, banking applications did not detect the root, but GPay/Wallet stopped working and showed that the device does not comply with security rules. Only the installation of the Shamiko module with the DISABLED Enforce Deny List in Magisk solved the problem. Both GPay/Wallet works and other banking apps don't see root. I did not tested removal of safetynet-fix-v2.4.0-MOD_1.2 module and leaving Shamiko module alone anymore. But my current combination of modules works for me. Thank you, Dear Friends, once more for your hints.
It happens exactly as you said. So denylist enforcement in Magisk should be disabled. Shamiko module properly hides the root for all the rest bankig/shopping appsGPay/Wallet needs passing PI deviceIntegrity and you need to check this is passing with a Play Integrity checker app... You'll see this fail as soon as denylist is enforced...
You have 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)
The app is running on a device that has signs of attack (such as API hooking) or system compromise (such as being rooted), or the app is not running on a physical device (such as an emulator that does not pass Google Play integrity checks).
...
If you are having problems with your testing device meeting device integrity, make sure the factory ROM is installed (for example, by resetting the device) and that the bootloader is locked.