Related
I've always loved the idea of being able to pay (at a lot of places, now) using NFC technology. Unfortunately, root access, xposed, and now a custom rom (Props to the EpicROM team!) have always out prioritized the NFC payment feature.
I've read a great deal about Magisk, and so I know how it works, but afaik EpicROM is packaged with SuperSU and so there isn't a straightforward way to use one of the compatible superuser apps. So, my question is (and the custom rom issue might be a bit much to tackle, but it's worth asking), has ANYONE managed to get Android Pay working on their Mix?
Also, I searched around for a good bit, only to find the answer elude me: Are there acceptable substitutes for Android Pay that do the same thing (NFC payment, "tap and go"?) and are accepted by most point of sale setups?
bigcc32 said:
I've always loved the idea of being able to pay (at a lot of places, now) using NFC technology. Unfortunately, root access, xposed, and now a custom rom (Props to the EpicROM team!) have always out prioritized the NFC payment feature.
I've read a great deal about Magisk, and so I know how it works, but afaik EpicROM is packaged with SuperSU and so there isn't a straightforward way to use one of the compatible superuser apps. So, my question is (and the custom rom issue might be a bit much to tackle, but it's worth asking), has ANYONE managed to get Android Pay working on their Mix?
Also, I searched around for a good bit, only to find the answer elude me: Are there acceptable substitutes for Android Pay that do the same thing (NFC payment, "tap and go"?) and are accepted by most point of sale setups?
Click to expand...
Click to collapse
To pass safety net you need to
1. Be unrooted
2. Have an official rom, which is stable (not developer)
3. Have a locked bootloader
So most probably, Magisk will not help you on this
Sent from my MI MIX using Tapatalk
Nikos2k said:
To pass safety net you need to
1. Be unrooted
2. Have an official rom, which is stable (not developer)
3. Have a locked bootloader
So most probably, Magisk will not help you on this
Sent from my MI MIX using Tapatalk
Click to expand...
Click to collapse
Yeah the three things you listed there are things I think I'd rather have than the slight inconvenience of having to actually pull out my wallet to pay for things.
In an ideal world we'd all be able to pay with PayPal using NFC technology, but oh well.
There is a kernel patch which fakes a verifiedboot state; you can try that.
https://github.com/sultanxda/androi...bc05b16bbd33521c2fffaf491c5657a94bfcfc5.patch
Which you can apply to: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/scorpio-m-oss
adwinp said:
There is a kernel patch which fakes a verifiedboot state; you can try that.
https://github.com/sultanxda/androi...bc05b16bbd33521c2fffaf491c5657a94bfcfc5.patch
Which you can apply to: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/scorpio-m-oss
Click to expand...
Click to collapse
I'm usually pretty technologically literate, but I'm not sure what I'm looking at. Part of the first URL you linked includes the words "oneplus," suggesting to me that it might not be as simple as just running that command line script. I don't expect to be spoon-fed information, but links to any related threads would be much appreciated.
I relocked my bootloader after I installed the official Global rom. I can add my credit cards but I can't get it to pay for anything at a terminal. It just doesn't launch at all.
Instead of flashing patched kernel, I would recommend flashing resurrection rom instead.
Please post a PIE ROM with Google pay working(India)
CUSTOM ROM or root detected is the error when using PIE ROM like havoc,pixel,aosp.........
Please provide ROM with Google pay working....
All Pie ROMs do have Google Pay working. You've not installed Magisk, which is a must to pass Safetynet on Custom ROMs. No Magisk != No Safetynet pass. You can't not install Magisk and stay rootless, it still will detect your bootloader is unlocked and will still fail Safetynet.
Hey, Skydragon 12/10 build and H4K3ROM seems to work with google pay india as i tried.
I think Google pay india has some issue or what am not sure. It isn't working with any other ROM as of now. Even when we've Hidden all google apps and related app, also have tried hiding magisk it self.
Safetynet and GPay working flawlessly here, without Magisk or any hacks and tweaks. Cheers.
shawnsaimohan said:
Please post a PIE ROM with Google pay working(India)
CUSTOM ROM or root detected is the error when using PIE ROM like havoc,pixel,aosp.........
Please provide ROM with Google pay working....
Click to expand...
Click to collapse
Dirty Unicorns latest RC build passes Safetynet out of the box. Google Pay working. No Encryption yet.
Dirk said:
Dirty Unicorns latest RC build passes Safetynet out of the box. Google Pay working. No Encryption yet.
Click to expand...
Click to collapse
Apparently Google Pay in India (rebranded from Google Tez) has issues on the latest RC. No reports of any issues from other regions.
legendavey said:
Apparently Google Pay in India (rebranded from Google Tez) has issues on the latest RC. No reports of any issues from other regions.
Click to expand...
Click to collapse
The issue was the user, not the ROM.
---------- Post added at 14:58 ---------- Previous post was at 14:56 ----------
>Akshay< said:
Hey, Skydragon 12/10 build and H4K3ROM seems to work with google pay india as i tried.
I think Google pay india has some issue or what am not sure. It isn't working with any other ROM as of now. Even when we've Hidden all google apps and related app, also have tried hiding magisk it self.
Click to expand...
Click to collapse
Try it without Magisk, on a ROM that passes Safetynet out of the box.
Dirk said:
The issue was the user, not the ROM.
---------- Post added at 14:58 ---------- Previous post was at 14:56 ----------
Try it without Magisk, on a ROM that passes Safetynet out of the box.
Click to expand...
Click to collapse
i can't say about without magisk but with magisk those above roms and also bootleggers rom seems to work for me. I've not tried rom without magisk, will probably try it when i have some time to clean flash again and test.
i thought he was doing the same probably and facing the issue so shared what i found for a solution. Didn't mean to say bad about any rom or dev.
>Akshay< said:
Hey, Skydragon 12/10 build and H4K3ROM seems to work with google pay india as i tried.
I think Google pay india has some issue or what am not sure. It isn't working with any other ROM as of now. Even when we've Hidden all google apps and related app, also have tried hiding magisk it self.
Click to expand...
Click to collapse
Yes. Google Pay for India uses a different package name as the rest of the world that has contactless (NFC) payments. We have UPI gateway based payments and way more stringent rules by NPCI. Since they're two separate packages, it definitely makes sense that Google Pay works for some but the rebranded Google Tez in India has issues with some ROMs without Magisk.
I'm using the Indian Google Pay (aka Tez) on LineageOS beta without Magisk and I have had zero issues so far. It didn't work very well on the DU RC for me, kept logging me out after a while. But I haven't had a single issue for three weeks now on the LOS beta.
legendavey said:
..Google Tez in India has issues with some ROMs without Magisk.
I'm using the Indian Google Pay (aka Tez) on LineageOS beta without Magisk and I have had zero issues so far. It didn't work very well on the DU RC for me, kept logging me out after a while. But I haven't had a single issue for three weeks now on the LOS beta.
Click to expand...
Click to collapse
I think you meant with Magisk? Otherwise you just contradicted yourself with your next sentence.
If a ROM passes Safetynet, i.e Selinux Enforcing/Verified Boot Patches in Kernel/Certified in Play Store then any app no matter what it's name or where it's used, will work if it checks for Safetynet status.
The problems i've seen reported were all with Magisk. Then there are factors like people not knowing to clear Cache/Data on Play Store if coming from a failing setup to a passing one, before trying Google Pay.
Sadly, at the moment Magisk is going to be needed most of the time because the number of ROMs that pass Safetynet out of the box right now is about Three, including DU. With all the Selinux Permissive ROMs Magisk is the only solution.
I wouldn't count on LOS passing out of the box once it's in Stable. That would break their 'Charter'. The maintainer has already said he hasn't done anything deliberately to pass Safetynet. Maybe accidentally...? Who knows. It will eventually need a custom Kernel with the verified boot patches to pass. (Not Caesium though as it still breaks the camera when paired with LOS. The old 'Black image with flash' issue. Still a problem on LOS Pie and presumably any ROMs that will be based on it like RR, if and when it arrives. RR of course comes with Caesium so will need a Kernel flashed on top that doesn't break the camera).
So many problems still with Pie. I'm back on RR Oreo with Franco Kernel for now. (And no Black image problem!)
Dirk said:
I think you meant with Magisk? Otherwise you just contradicted yourself with your next sentence.
If a ROM passes Safetynet, i.e Selinux Enforcing/Verified Boot Patches in Kernel/Certified in Play Store then any app no matter what it's name or where it's used, will work if it checks for Safetynet status.
The problems i've seen reported were all with Magisk. Then there are factors like people not knowing to clear Cache/Data on Play Store if coming from a failing setup to a passing one, before trying Google Pay.
Sadly, at the moment Magisk is going to be needed most of the time because the number of ROMs that pass Safetynet out of the box right now is about Three, including DU. With all the Selinux Permissive ROMs Magisk is the only solution.
I wouldn't count on LOS passing out of the box once it's in Stable. That would break their 'Charter'. The maintainer has already said he hasn't done anything deliberately to pass Safetynet. Maybe accidentally...? Who knows. It will eventually need a custom Kernel with the verified boot patches to pass. (Not Caesium though as it still breaks the camera when paired with LOS. The old 'Black image with flash' issue. Still a problem on LOS Pie and presumably any ROMs that will be based on it like RR, if and when it arrives. RR of course comes with Caesium so will need a Kernel flashed on top that doesn't break the camera).
So many problems still with Pie. I'm back on RR Oreo with Franco Kernel for now. (And no Black image problem!)
Click to expand...
Click to collapse
I think my post was pretty clear, but I can type it out again using different words if you want.
LOS 16 beta allows GPay India (Tez) without Magisk, without any tweaks. *Doesn't* work on DU or *any* other ROM without Magisk in my experience. Magisk doesn't break Safetynet, it *fixes* it on most ROMs that don't pass by default.
Yes, DU passes Safetynet out of the box without Magisk too, but it occasionally logs me out of GPay India (Tez) and Netflix occasionally disappears from the Play Store. Which means something isn't working properly. Probably because its a userdebug build. I honestly couldn't care about DU rn because encryption is broken and they seem to be ignoring my report about it on JIRA.
I know about the LOS charter. I'll probably flash a custom kernel like Franco when LOS goes official.
I dunno what these problems with Pie that you speak of are. I haven't had a single issue and is now my daily driver. Oreo battery is also horrible compared to Pie in my experience, and the interface feels outdated. But you do you, bud.
shawnsaimohan said:
Please post a PIE ROM with Google pay working(India)
CUSTOM ROM or root detected is the error when using PIE ROM like havoc,pixel,aosp.........
Please provide ROM with Google pay working....
Click to expand...
Click to collapse
RR 7.0.0
Hello,
For latest news from topjohnwho, Google fixed Safetynet check for hardware based key attestation. So no Google Pay in future with UB.
Is latest Android 10 for XZ2/C affected with this or is magisk working with GPay flawlessly?
Thank you for answer if anyone tried that.
it works on stock android 10
edit: u can install magiskhide props config and enable magiskhide in the settings to get it pass completely although things can change with the next security update
Thank you.
He wrote that Safetynet check is made on google servers, so magiskhide will lost purpose in future, right.
Have you tried GPay? That is only reason why I stay on 9, because here it works.
Vi.sr said:
Thank you.
He wrote that Safetynet check is made on google servers, so magiskhide will lost purpose in future, right.
Have you tried GPay? That is only reason why I stay on 9, because here it works.
Click to expand...
Click to collapse
GPay works on my rooted XZ2 on android 10
There's no dedicated thread for it here on xda forums. Apparently it's on omnirom's website and regularly maintained as well.
Those who have tried it please post how it compares to other roms. Thanks.
farhanshaikh671 said:
There's no dedicated thread for it here on xda forums. Apparently it's on omnirom's website and regularly maintained as well.
Those who have tried it please post how it compares to other roms. Thanks.
Click to expand...
Click to collapse
I just install omnirom right now... twice, with format data, factory reset... the same bootloop, stuck into mi logo...
I didn't find anywhere some installation instructions, I installed it after miui rom.
Omni is booting for me. works fine.
morpheus620 said:
Omni is booting for me. works fine.
Click to expand...
Click to collapse
mind giving me a brief review?
is very very fast for a A12 ROM. faster than other A12 ROMs.
a few things are missing. There is no face unlock and the sound adjustment under Sounds.
I used it for face unlock: https://forum.xda-developers.com/t/11-universalauth-face-unlock-for-all-roms.4419343/
morpheus620 said:
is very very fast for a A12 ROM. faster than other A12 ROMs.
a few things are missing. There is no face unlock and the sound adjustment under Sounds.
I used it for face unlock: https://forum.xda-developers.com/t/11-universalauth-face-unlock-for-all-roms.4419343/
Click to expand...
Click to collapse
Did you flash before omnirom any miui firmware?
yes. FW 12.5.
there is an update from OMNi today. unfortunately it does not boot. I have already written to OMNi in the telegram.
morpheus620 said:
yes. FW 12.5.
there is an update from OMNi today. unfortunately it does not boot. I have already written to OMNi in the telegram.
Click to expand...
Click to collapse
What's about battery backup and stability?
Full gestures without lagging?
Extended gestures like long swipe to kill app in foreground...present?
Thanks in advance
What's about battery backup and stability?
I can't say anything yet. I only flashed OMNI yesterday evening and today the faulty update came.
Full gestures without lagging?
yes
Extended gestures like long swipe to kill app in foreground...present?
no
I wrote to the maintainer. Firmware 12.5 is fine. face unlock will not come as it was removed from AOSP.
I'll get a test build later. I don't know if it's already 12.1/L.
@morpheus620 hey can you please check which device's fingerprint this rom uses if you get a chance? thanks.
like which fingerprint?
the one in the power button. Which one else?
farhanshaikh671 said:
@morpheus620 hey can you please check which device's fingerprint this rom uses if you get a chance? thanks.
Click to expand...
Click to collapse
For what you need to know?
You mean fingerprint in build.prop?
Laptapper said:
For what you need to know?
You mean fingerprint in build.prop?
Click to expand...
Click to collapse
yes. Most roms use fingerprint from pixel devices to pass safetynet so I was wondering if it's the same in this case as well
I'm running omnirom right now, the latest Android 13 MicroG version:
omni-13-202305201702-sweet-MICROG
The instructions don't specify which MIUI kernel to use. I'm currently using 14.0.2.0 (android 13). I also tried 13.0.16.0 (android 12), and briefly 12.5.9.0 (android 11) -- all with separate clean installs. They all seemed to work.
It is bare-bones, without many included apps, which is fine. It has a phone dialer, messaging, and contacts app. They look like they have been somewhat updated vs. the really old AOSP versions. It boots up right away after installing, without any setup.
The MicroG safetynet test always fails with "integrity check failed" -- whether magisk is installed or not. It doesn't have an issue with the CTS profile, though.
I've tried the safetynet-fix modules, v2.4.0 and v2.3.1, both the original and MOD versions, but they didn't help. I've also tried HidePropsConf, but it also didn't help (I think that's mainly for CTS profile issues, anyway, which this doesn't have).
My banking app is still working despite that, but it's too bad it won't pass. On /e/ OS I can get it to pass, using safetynet-fix v2.4.0 (original) and HidePropsConf.
Wireguard VPN works, but "Always-on VPN" and "Block connections without VPN" don't work properly. This is also the case for some versions of LineageOS and for /e/ OS. So you have to leave those settings off.
All of the cameras/lenses are available to Camera2 API and working in Open Camera. They are also available in /e/ OS. Many of the new LineageOS builds only have Camera2 API access to the main front and back cameras, so they're not suitable for me.
It does allow for partial and extended screenshots, but there's no swipe gesture to do screenshots.
It is fast charging with my phone's bq2597x charger.
It is using the JARVIS kernel, dated May 20. The rom has weekly updates, but I'm not sure if it's a new kernel version, or if it just gets rebuilt as part of the update.
I ran /e/ OS for awhile before this. It is also good, but it's Android 12, and not as up to date.
So phone is rooted with safety net bypassed and all app Inc Gpay worked fine till this morning! Did Google change something, has anyone noticed anything?? Any other ways around? Thanks
I think a lot of people face the same issue. You can check this :
https://forum.xda-developers.com/t/discussion-google-pay-magisk-discussion-thread.3906703/page-128
I think Google did a upgrade.
Try to spoof your phone to an Android 10 fingerprint . I have choosen the "MI 10T Pro Europe" Fingerprint . Cleared the cash of Playstore and Gpay. and Rebooted the phone.
Now it's seems to be OK.
ps: You have to install MagiskHide Props
Guys reading the thread above, I changed the font recently. Just as Google updated GPay it stopped working. Someone mentioned that font ot theme change can upset root status.I reverted to original font and reboot. Viola Gpay is working again.. amazing stuff. thanks
samy233 said:
Try to spoof your phone to an Android 10 fingerprint . I have choosen the "MI 10T Pro Europe" Fingerprint . Cleared the cash of Playstore and Gpay. and Rebooted the phone.
Now it's seems to be OK.
ps: You have to install MagiskHide Props
Click to expand...
Click to collapse
I wanted to give fingerprint spoofing a try too, but I don't want to change my device's fingerprint to another device.
Perhaps a vili Android 11 (MIUI 12) fingerprint would work, too.
But I don't know the right fingerprint. My current Android 12 fingerprint is:
Xiaomi/vili_eea/vili:12/SKQ1.211006.001/V13.0.10.0.SKDEUXM:user/release-keys
Perhaps someone could post his EEA Android 11 fingerprint?
Another update: font restore worked only for a few minutes. As soonest as I went to use a nfc pay the "warning" came back and Gpay stopped working.
Next solution for me was to change the fingerprint to a Mi 10T pro (A10). Rebooted device and still the same warning. As clear cache option is greyed out, I deleted Google wallet and reinstalled. So far no warning.I just have to try it out in the shop now and see if it works
_WiNNa_ said:
I wanted to give fingerprint spoofing a try too, but I don't want to change my device's fingerprint to another device.
Perhaps a vili Android 11 (MIUI 12) fingerprint would work, too.
But I don't know the right fingerprint. My current Android 12 fingerprint is:
Xiaomi/vili_eea/vili:12/SKQ1.211006.001/V13.0.10.0.SKDEUXM:user/release-keys
Perhaps someone could post his EEA Android 11 fingerprint?
Click to expand...
Click to collapse
This is my config now , you can see the original one and the spoofed one.
You can also see in the menu that you can reset the fingerprint , so you can back to normal.
samy233 said:
View attachment 5666255
This is my config now , you can see the original one and the spoofed one.
You can also see in the menu that you can reset the fingerprint , so you can back to normal.
Click to expand...
Click to collapse
Yes, can confirm this is working.
But I would definitely feel better, when this will work with a fingerprint from another version of Android from this very same device.
_WiNNa_ said:
Yes, can confirm this is working.
But I would definitely feel better, when this will work with a fingerprint from another version of Android from this very same device.
Click to expand...
Click to collapse
Right , we have to wait for a fix.
samy233 said:
View attachment 5666255
This is my config now , you can see the original one and the spoofed one.
You can also see in the menu that you can reset the fingerprint , so you can back to normal.
Click to expand...
Click to collapse
How do I get/start the GUI?
soadfan said:
How do I get/start the GUI?
Click to expand...
Click to collapse
You did the right think , I don't know why is not getting started, maybe the path.
Here's mine, I use Termux
soadfan said:
How do I get/start the GUI?
Click to expand...
Click to collapse
Did you reboot after installing the module?
Update:
Fingerprint set to Mi 11 Pro EU A10 works as usual.
Tried and tested and all my Gpay and banking apps working as before.
samy233 said:
You did the right think , I don't know why is not getting started, maybe the path.
Here's mine, I use Termux
Click to expand...
Click to collapse
_WiNNa_ said:
Did you reboot after installing the module?
Click to expand...
Click to collapse
Yes, and yes, I've installed Termux too and it's working. I guess the terminal emulator is not that good anymore
soadfan said:
Yes, and yes, I've installed Termux too and it's working. I guess the terminal emulator is not that good anymore
Click to expand...
Click to collapse
cool, so now all is ok
So, I've tested with
Xiaomi/vili_eea/vili:11/RKQ1.200903.002/V12.5.20.0.RKDEUXM:user/release-keys
That's not working
_WiNNa_ said:
So, I've tested with
Xiaomi/vili_eea/vili:11/RKQ1.200903.002/V12.5.20.0.RKDEUXM:user/release-keys
That's not working
Click to expand...
Click to collapse
Yes , all the A12/A11 modele seems not working
What's the downside of using another device's fingerprint, like 10T Pro for example?
get newest Magisk enable Zygisk:
install Zygisk LSPosed
Release 1.8.3 · LSPosed/LSPosed
Changelog Fix module not working normally on Android 10 Refine notification on module installation (thanks @fankes) Fix hook may not work on debuggable apps/modules Fix XSharedPreference after a s...
github.com
and Shamiko
Releases · LSPosed/LSPosed.github.io
Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.
github.com
in Magisk, hide root by going into the Denylist and hide it from the google apps like google wallet, play store, services framework, carrier services, clear cache and restart, if it doesnt work, use the Universal Safetynet Fix with it.
Marvin732 said:
get newest Magisk enable Zygisk:
install Zygisk LSPosed
Release 1.8.3 · LSPosed/LSPosed
Changelog Fix module not working normally on Android 10 Refine notification on module installation (thanks @fankes) Fix hook may not work on debuggable apps/modules Fix XSharedPreference after a s...
github.com
and Shamiko
Releases · LSPosed/LSPosed.github.io
Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.
github.com
in Magisk, hide root by going into the Denylist and hide it from the google apps like google wallet, play store, services framework, carrier services, clear cache and restart, if it doesnt work, use the Universal Safetynet Fix with it.
Click to expand...
Click to collapse
No need to spoof to another model ? works with A12 ? what's your phone ?