Search results

You should not have upgraded. v13.9 works fine with its built-in props However, v13.9 is purged from GitHub now Find it in your Download and reinstall

Yes, eg my bank allows/authorizes contactless payments (or withdrawals on ATM) for my Visa credit and debit cards only through G Pay/Wallet I could add my cards to Xiaomi Pay or any other similar third party app but with no use - they will never pay by NFC Only the Wallet or plastic

Xiaomi.eu is not official, certified ROM by Xiaomi but a custom ROM. Also, custom ROMs require unlock Bootloaders. Every user of the custom ROMs (this or any other) has to be aware of that and must understand the (potential) consequences Hence no matter is it called Stable, Beta, Dev or...

V13.9 is brand new from today, hence expected that it 'still' works

And Taimen (from v13.9) too - they are catching faster and faster For how long there will be prints to spoof?!

So what would be better for you with the old build? In the OLD days Goggle Pay worked with the OLD Stable release but NOW Google Pay does no more work with that same OLD Stable release

You cannot. PIF module is not a static change to be patched to the ROM. PIF module runs as a Zygisk service - hence you need Zygisk started by Magisk at the time of booting (when Magisk initializes)

Why not. I always use. However, when using Shamiko: - DenyList must be properly filled - But DenyList must not be Enforced It has nothing to do with PIF nodule, it's due to Shamiko that has to hide Zygisk from the apps listed in DenyList instead of the Magisk built-in And of course, PIF will...

Link with instructions were posted here (it can be also found by searching). So once again: https://xiaomi.eu/community/threads/how-to-flash-magisk-and-play-integrity-fix-on-xiaomi-eu.70553/

Banking apps use various detection methods Eg, try putting them to DenyList and reboot Btw, you say you removed Magisk - you really did or you just removed Magisk app (Magisk app is not Magisk itself) You could search for Magisk thread(s) on XDA and find more info there

Does it really matter if everything works? And doesn't the table in post #1 say that gauguin and gauguinpro share the same Xiaomi.eu ROM And they share same chipset, screen, etc: https://www.gsmarena.com/compare.php3?idPhone1=10480&idPhone2=10582&idPhone3=10473

Downloaded yesterday from Source Forge Net for Lisa and installed, everything fine To speed up downloading I use ADM (find on Playstore)

In Download folder, nowhere else in hidden folders or so However, if using TWRP, you have to enable IMG files for installing/flashing - otherwise TWRP shows zips only Check Download folder in Android before rebooting to TWRP

You mean Magisk had to be hidden from - by use of DenyList Btw, last Thu and Fri, after Device Integrity failed, I was still paying my bills by scanning the QR code (Photo payments), paying by NFC and withdrawing money from their ATM However, I updated the ROM today, applied the module and...

Open post-fs-data.sh that belongs to PIF module and you will see that it intentionally removes com.google.andtoid.gms.unstable from DenyList And that's not a cause for anything (what you claimed). To the contrary, it has to do so since PIF needs to hook to GMS to be able to spoof, instead of...

You may need to Wipe Data for that app (long press to the app icon and take App Details) since some apps cache the previous root detection For some apps additional methods to hide are necessary, like installing Zygisk-LSPosed and then HMA = Hide My Apps module to hide Magisk app, HMA and other...

Not because it is a Zygisk module. It runs as a Zygisk process, hence Zygisk must be enabled in Magisk. As a Zygisk process it captures calls to GMS for Play Integrity checking and then performs spoofs only for that process (if those spoofs would be performed globally, for all apps, they will...

Thanks, waiting for the re-release

It's not only about the unlocked Bootloader but also about the custom ROM People wrongly think that unlocked BL is a culprit. It's just that if BL is locked, you cannot flash custom ROMs, hence you have a phone with the official, unmodified firmware and therefore you don't have a problem But...

Google blocked Device Integrity early afternoon yesterday (CET), see the posts from here and elsewhere For Wallet it take some hours to becomes 'aware' (it caches previous results) - unless you don't manually open the app and force it to retest Play Integrity