Android Pay Problem - error? - Xiaomi Mi 6 Questions & Answers

Hi guys
Few days ago came my Mi6, I flashed xiaomi.eu rom (it came factory unlocked) and got a problem:
my Android Pay doesn't work, my bank is mBank (Poland), supported by Android Pay.
The problem is that when I try pay by phone, terminal beeps 2 or 3 times like the card is unreadable or anything else (no idea).
Miui 9, TWRP, Magisk, Unlocked Bootloader
In attachments screenshots from Android Pay app and Settings app.
Any ideas what's wrong?
EDIT:// Magisk SafetyNet: Passed

Dose safetynet pass?

Switch NFC off and on. It worked for me in an identical situation.

Hi, did you ever find a solution for this? Having the exact same problem in the UK on MIUI Global 8.5

Also having same issue but with the Barclays app. 3 beeps and card error message

Related

Google Pay - Android Pie - Credit Cards keep requiring verification

Hey All - so this is a weird problem. I'm running Android Pie on a Google Pixel XL. Stock. Unlocked. Rooted. (Magisk 16.7 (1671) w/ Magisk Mgr 5.8.3). I've been running and using Google Pay for a long time successfully. I have two credit cards stored in my account and the only times I need to re-enter / re-verify them is when I disable security (usually to use TWRP to install Magisk when TWRP is unable to decrypt - which is currently the case). But once I have verified the cards (via text message from each bank), I usually never have to worry about them again. However, since upgrading to Pie and after initially verifying the cards, I have had to unexpectedly reverify the cards even though nothing has changed about my configuration or the cards themselves. It happened once a few weeks ago - shortly after the Pie upgrade which I assumed was just something I hadn't completed after the upgrade (even though I believe I did). And then it happened again yesterday. I went to use my phone to pay via Google Pay at the store and it prompted me to verify both credit cards (Setup Card for use in store)...
Anyone else experiencing this? Or am I just lucky? The reverify is painless - but can be annoying - especially when you don't have your wallet and there is a line behind you at the checkout counter...
Thanks,
S
Google Pay can be used under rooted device?
I'm used to use Google Pay very often, but didn't encounter that need to re-verify cards again.
I had tried device unlocked, rooted, but I can't use Google Pay since my bank add the root detection for the security.
It's very surprising that you're running Google Pay with rooted device.
I have seem others encountered double fingerprint verification.
Not sure if you're the same case with them.
BR.
JD_dadada
sb1893 said:
Hey All - so this is a weird problem. I'm running Android Pie on a Google Pixel XL. Stock. Unlocked. Rooted. (Magisk 16.7 (1671) w/ Magisk Mgr 5.8.3). I've been running and using Google Pay for a long time successfully. I have two credit cards stored in my account and the only times I need to re-enter / re-verify them is when I disable security (usually to use TWRP to install Magisk when TWRP is unable to decrypt - which is currently the case). But once I have verified the cards (via text message from each bank), I usually never have to worry about them again. However, since upgrading to Pie and after initially verifying the cards, I have had to unexpectedly reverify the cards even though nothing has changed about my configuration or the cards themselves. It happened once a few weeks ago - shortly after the Pie upgrade which I assumed was just something I hadn't completed after the upgrade (even though I believe I did). And then it happened again yesterday. I went to use my phone to pay via Google Pay at the store and it prompted me to verify both credit cards (Setup Card for use in store)...
Anyone else experiencing this? Or am I just lucky? The reverify is painless - but can be annoying - especially when you don't have your wallet and there is a line behind you at the checkout counter...
Thanks,
S
Click to expand...
Click to collapse
JD_dadada said:
I'm used to use Google Pay very often, but didn't encounter that need to re-verify cards again.
I had tried device unlocked, rooted, but I can't use Google Pay since my bank add the root detection for the security.
It's very surprising that you're running Google Pay with rooted device.
I have seem others encountered double fingerprint verification.
Not sure if you're the same case with them.
BR.
JD_dadada
Click to expand...
Click to collapse
I've always been able to leverage the root hiding capabilities offered by the root providers I have used. Originally suhide for SuperSu...then when I moved to Magisk MagiskHide. Both have worked well for my root (and unlocked bootloader) hiding purposes. I've always been able to use Android/Google Pay, banking apps, alarm system apps, Netflix, etc...Occasionally, the cat and mouse game catches up with the root hiding solution, but the developers have been pretty quick to overcome any of the challenges encountered thus far.
Got the same problem with verifying card.
It's just poping up the verify load page and then goes back instantly.
I hadn't got any problems with it before so it's strange for me.
I tried hiding root, reinstalling, readding card and even installing older versions of google pay.
However I am on Galaxy S7 Edge Oreo
Zaczero said:
Got the same problem with verifying card.
It's just poping up the verify load page and then goes back instantly.
I hadn't got any problems with it before so it's strange for me.
I tried hiding root, reinstalling, readding card and even installing older versions of google pay.
However I am on Galaxy S7 Edge Oreo
Click to expand...
Click to collapse
I have exactly the same behavior on my LG G5 with root and Magisk. My bank is mBank (part of Commerzbank) if that matters.
javlada said:
I have exactly the same behavior on my LG G5 with root and Magisk. My bank is mBank (part of Commerzbank) if that matters.
Click to expand...
Click to collapse
Looks like I found the problem (at least in my case).
Some ROMs got issues with fingerprint scanner. I noticed that in my bank app after adding the fingerprint unlock it started to crash. Also in google play I couldn't add fingerprint as payment confirmation.
In Google Pay one of the steps of verifying cc is fingerprint check. I think that this fingerprint bug may cause the google pay to fail.
After installing a ROM with fingerprint scanner working properly (now I'm on LineageOS) the issue went away. Got my cc verified successfully with root and rom

Android 10 WW BETA 10 OUT

Android 10 BETA WW
Special thanks as always to Vietnam ROG II Grp. They do amazing work.
Links removed due to request
Rename the downloaded file to UL-ASUS_I001_1-ASUS-16.0631.1912.22-1.1.227-user.zip then put on root of internal storage and restart.
Root & Bootstock for 1912.22 ANDROID 10 BETA
https://mega.nz/#!hxJGCQpT!6xU71ihzA1cA5JLDB_hMMJNg5iHt80FmOf6z8Hrb7gA
Use at your own risk, do not raise issues on Zentalk forums.
So far user feedback has been positive.
Please let us know your experiences.
Current known issues (some bad English here!):
When in the game scenario and answer the phone call, user will not hear the sound and cut off the call after 30 seconds later.
Can not open the icon manager and showing "System UI has stopped"
When you install Avast.apk don't have any scan notice.
Working with twinview dock and open one of a app on the phone side then press twinview side panel recent key. The phone side will back home screen.
When using DT Dock or twinview or Pro dock to play Netflix will keep portrait mode and only show subtitle.
Any bugs?
Link root from telegram
Anyone tried it? If yes can post pictures thanks
Successfully update to Android 10 beta with magisk installed but now I am without TWRP. Tried flash TWRP with adb but it reboot to bootloader every time. Maybe TWRP must be updated for Android.
This is failing for me. Gets to 2% then fails. I'm on Rooted 128 GB Tecent with WW ROM, fingerprint is changed to WW.
xbamaris1` said:
This is failing for me. Gets to 2% then fails. I'm on Rooted 128 GB Tecent with WW ROM, fingerprint is changed to WW.
Click to expand...
Click to collapse
If you're rooted then you probably need to flash it manually.
tsoureki said:
Successfully update to Android 10 beta with magisk installed but now I am without TWRP. Tried flash TWRP with adb but it reboot to bootloader every time. Maybe TWRP must be updated for Android.
Click to expand...
Click to collapse
Step for update without lost root sir?
If you are rooted on latest Android 9 you need to go in magisk, press uninstall and restore images. Then you can apply the beta 10 ota. For root flash on adb the modified boot image from op
Does anyone have the Android 10 beta full RAW firmware ???
Hello, if anyone has access to the full Android 10 beta RAW firmware, please share it with us. Thanks !!!
Wow it's amazing. The red tint gone and it's way too smooth
It seems this has also broken the ability to enable VoLTE (*#*#4636*#*#) greys out the options but they do show up in the Settings menus. So not sure what that means?
EDIT: Ignore, its because the profile set in PDC was reset as someone else has pointed out. I JUST got VOLTE to work again after working with AT&T to get a provisioning error resolved (this was on their end, but probably because I was swapping SIMs between phones for testing)
Im going to let this settle a little bit before I try upgrading again to this (I downgraded back to 9 in fear that VOLTE wasnt going to work again)
Gpay is not working
Is this WW or CN beta????
cheetah2k said:
Is this WW or CN beta????
Click to expand...
Click to collapse
When you download zip its named WW.
CTS doesn't pass on this version. Hence done apps like gpay may not work
I'm not sure what I'm doing wrong but as soon as I tap update it instantly just says failed. I am on ww rom ww fingerprint and have twrp.
Hello
What is the difference between a version and the orange star?
candiesdoodle said:
CTS doesn't pass on this version. Hence done apps like gpay may not work
Click to expand...
Click to collapse
Do you know if this version will keep getting OTA?
lol cloud1 you just posted without giving credit to the owner from telegram vietnam group. it is like u stealing their work. now they just informed they will not post any update anymore in that group.

Some app issues with LineageOS 17.1 (Android 10) Galaxy S8+ dream2lte

I have some issues with certain apps on an unrooted Galaxy S8+ Exynos running LineageOS 17.1 (Android 10.0) with TWRP recovery installed.
I own a Galaxy Watch Active, and I attempted to install the Galaxy Wear app from the Play Store and opened it, and got a 'Operating System on your phone has been modified in an unauthorised way' error. I also own Galaxy Buds+ which I need to pair as well (using standard bluetooth with them for now). How do I fix this issue? (bear in mind I'm not rooted)
The HSBC UK app is also messing around a bit, every time I open it and click the checkbox next to 'I accept the terms and conditions', it reboots my phone and crashes the app. Is this a general Android 10 issue with support for the HSBC app, or an anti-custom ROM move from HSBC? And if this is the case, how would I fix this too?
A more general issue is that Google Pay isn't working. It says my phone isn't supported to make payments in-store via NFC because it has been rooted (it hasn't been rooted, just installed a custom ROM). I didn't pass the SafetyNet test. It was installed with gapps by the way.
The least important issue is the Transport for London app, which says that my phone has been tampered with and is no longer supported by TfL and the app closes. Any way to trick the app into thinking I am not running a custom ROM?
Thank you so much for reading and I'd really appreciate your help! Thanks!
Did you manage to find a fix for the HSBC UK app reboot/crashing problem? I am having the same issue, but on Havoc OS running Android 11 rooted with Magisk.

Black shark 3 assistance needed

So I have had my bs3 just over a mth now and I really love it.
Unfortunately mine came with the Chinese Rom and this is causing some problems for me.
1) cant sign in to the black shark account because the region code is locked
2) whatsapp, snapchat and a few other apps are really inconsistent with notifications (the min the phone goes to sleep it stops receiving msgs until I reopen the app)
3) tinder gives me a location access not granted even though it has been given access.
4) phone doesnt stay connected to pc when plugged in and I have to constantly tweak the usb settings to get it to. (semi fixed by usb drivers which were a pain to install)
In reading up seems like this could be fixed by the global rom but nowhere seems to have it. I even tried contacting blackshark directly to which they said they dont give out the firmware over the internet as there is a chance it would brick it ( I call bs because xiaomi does it FOR EVERY OTHER PHONE and has a tool for it on their site). Does anyone have any idea how to fix any of these issues?
Contact me telegram @hoangtieubao
I will help u
chaict
lostpunkrock said:
So I have had my bs3 just over a mth now and I really love it.
Unfortunately mine came with the Chinese Rom and this is causing some problems for me.
1) cant sign in to the black shark account because the region code is locked
2) whatsapp, snapchat and a few other apps are really inconsistent with notifications (the min the phone goes to sleep it stops receiving msgs until I reopen the app)
3) tinder gives me a location access not granted even though it has been given access.
4) phone doesnt stay connected to pc when plugged in and I have to constantly tweak the usb settings to get it to. (semi fixed by usb drivers which were a pain to install)
In reading up seems like this could be fixed by the global rom but nowhere seems to have it. I even tried contacting blackshark directly to which they said they dont give out the firmware over the internet as there is a chance it would brick it ( I call bs because xiaomi does it FOR EVERY OTHER PHONE and has a tool for it on their site). Does anyone have any idea how to fix any of these issues?
Click to expand...
Click to collapse
Head over to black shark 3 pro threads. There is a guide to unlock bootloader for bs3 and bs3pro and then you can install global rom..
Sent from my [device_name] using XDA-Developers Legacy app
chaict said:
chaictHead over to black shark 3 pro threads. There is a guide to unlock bootloader for bs3 and bs3pro and then you can install global rom..
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
The loader is great but cant find the global rom anywhere. Cant afford to pay for it to be redone right now so stuck with hoping it gets released.
lostpunkrock said:
The loader is great but cant find the global rom anywhere. Cant afford to pay for it to be redone right now so stuck with hoping it gets released.
Click to expand...
Click to collapse
If your bootloader unlocked , flash the twrp and magisk to root it. Then systemize google apps ,your notifications will be no issue. Most of the google apps will work like global rom. For my case i still use China and i found out china mp5 is more smooth. Just my 2 cent..
chaict said:
If your bootloader unlocked , flash the twrp and magisk to root it. Then systemize google apps ,your notifications will be no issue. Most of the google apps will work like global rom. For my case i still use China and i found out china mp5 is more smooth. Just my 2 cent..
Click to expand...
Click to collapse
Lol so you basically speaking gibberish to me is there any instruction or tutorial on how to do those things?
As I said I generally love the layout its just the annoying part of not getting a few apps to work properly (whatsapp, tinder and snapchat in particular)

GPay card cannot be set for contactless payments

Hi, I need help adding a card to gpay.
The card cannot be added for contactless payments. I don't know what it is or what could have happened while playing rom. In the original, everything worked well. After that I switched to alexis rom and everything worked. After some time I tried xFire rom and also nothing. I wanted to try the resurrection remix because it's my favorite rom from previous phones and I don't know there because I left it due to problems with the Gear S3 Frontier parking. Using Odin, I recorded the original rom and the problems started. The card could not be added at all, but it was resolved with the bank. The problem was logging the card on multiple devices and the bank fixed it. The card can be added manually, but the settings for contactless payments cannot be completed. The process ends when the card is verified at the bank. I thought it was a rom problem, but I tried several roms and the problem is the same.
I tried to set the card on my older asus zenfone max for m1s HavocOS and the card was added to gpay without any problems. So the problem must be in the phone.
Could someone please help how to fix this? I'm really desperate. Sorry English, I use google transalator
Are you rooted?
Yes. Currently alexndr rom. Magisk hide. Neither the banking app nor the gpay app report root. Safenet check pass
The strange thing is that a week ago on alexis rom it still worked. Now it is not possible to add for contactless payments on any rom. Manually yes, but only for online payments. The contactless payment setup ends during the verification process at the bank.
jampce said:
Yes. Currently alexndr rom. Magisk hide. Neither the banking app nor the gpay app report root. Safenet check pass
The strange thing is that a week ago on alexis rom it still worked. Now it is not possible to add for contactless payments on any rom. Manually yes, but only for online payments. The contactless payment setup ends during the verification process at the bank.
Click to expand...
Click to collapse
I have no idea what to suggest then, it can't be root related because safety net passes, have you tried adding another card to google pay?
Sent from my SM-G960F using Tapatalk
I tried to add a girlfriend card and it ends the same way. My card on my old phone can be added normally .. That's why I don't understand .. I already received an answer from Google support that everything is fine on their part ..
So there must be something wrong with the phone. But what .. Bootloader I have for sure flash as well. The only thing that comes to mind can be influenced by CSC? I don't know what it was originally like, but I chose XEZ (Czech) when installing alexis, which it probably should be. But there was a card to add and after replacing other roms it doesn't even go there.
I'm still thinking. Before flash original rom using odin, I twrp wipe all the partitions (including vendor and preloaded). It still seemed to me that everything was not right, so I did it. Couldn't it be wrong? If so, can it be fixed? Although I assume odin will record everything again

Categories

Resources