Database Develop

Apps refuse to start because phone being rooted but it isn't!

At least 2 of my Apps refuse to start. One is my banking app and they do not offer any other way of interaction.
The problem is that the phone in fact is not rooted! It's just "OEM unlocked" to be prepared for root (which I need for E.g. titanium backup, but only maybe once a month).
Please give me a way out of this vicious circle!
I cannot remove the OEM unlock because it requires full wipe every time. Or is there a way?
Or what can I possibly tell the App Provider to improved their Code so that Oneplus phone state is being recognized (more) correctly?
Any help would be greatly appreciated.

Use Magisk I guess? Use it to hide root from that app.

Reeb_Lam said:
Use Magisk I guess? Use it to hide root from that app.
Click to expand...
Click to collapse
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?

ako673de said:
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
Click to expand...
Click to collapse
You need to do some reading about Safetynet. If you're OEM unlocked you fail Verified Boot checks. Most custom Kernels include a bypass for this. Magisk alone should also work. I think you missed one important step:
Open Play Store Settings. Scroll down. It says 'Uncertified' at the bottom, right? Now install and set up Magisk. Go to system App Settings and clear Data and Cache for Play Store. Return to the Play Store Settings and scroll down. Now it should say 'Certified'. It might not be immediate, but it will happen. Now your Banking Apps work.
If you don't want, or have no luck with Magisk, simply flash a Custom Kernel that bypasses Verified Boot, and works with OOS.
Simple.

Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?

ako673de said:
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
Click to expand...
Click to collapse
Link to other Thread?
I don't know Magisk but are you hiding Root from your Banking App? Have you cleared Data and Cache for the Banking App since getting Certified?

First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?

ako673de said:
Any other idea?
Click to expand...
Click to collapse
Nope. If Play Store says Certified you should be good to go. I can only imagine it's a Magisk issue. Post screenshots of your config and let the Magisk experts pick through them. Maybe there's something not set up correctly.

ako673de said:
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
Click to expand...
Click to collapse
Hide Magisk Manager. I had to do that to get my banking app to work.
Edit: you may need to reboot after hiding Magisk Manager and clear you banking app's data before it works.
Sent from my OnePlus3T using XDA Labs

Thank you, indeed that WORKED! Well, at least for 2 out of 3 Apps. I think I can tell which one: "HVB banking". Maybe could somebody cross-check this one on his/her phone?

After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?

ako673de said:
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
Click to expand...
Click to collapse
Did you reflash custom kernel after update?

I'm not using any. What I did right after the update is to disable dm-verity (with a patched boot.img), like I did last time. But magisk is not yet re-installed because I wanted to see at least once the HypoVereinsbank App working, which it in fact does (different to last time when the phone was not rooted as well, and the store not certified!).

ako673de said:
But magisk is not yet re-installed
Click to expand...
Click to collapse
That's why... You can't pass the ctsProfile check if your bootloader is unlocked, and if you can't pass the ctsProfile check the Play Store won't be certified. You need Magisk for that...

Now I'm getting confused. The initial mail of this thread explains the situation as it was when I opened this thread:
--> Original ROM, no root, and banking apps didn't work <--
The advice to clear data of the PlayStore immediately brought the PlayStore back to "certified".
This is clearly in contrast to what you're saying now.
I can imagine only one reason: Maybe the older PlayStore had a bug and therefore was able to "certify" even with unlocked bootloader?
Sidenote: My main intention to do the firmware upgrade was that the "safety net checks" in Magisk suddenly stopped working one day (with the error message "invalid response", most probably you know what I'm talking about, I've read some comments from you on this issue). Therefore it's maybe really not too unlikely that Google has changed something very basic. Could you please confirm?
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).

ako673de said:
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid

Sorry, now comes a probably often asked question: do I need the safetynet check option in magisk for something real? Or do the alternative apps fulfill all possible needs? What are these needs? Isn't that exactly what the PlayStore does to determine "certified"?

After quite some months of absolutely no "root" problems with any of my apps, since today o2banking again doesn't work.
I tried to update Magisk, but after update of the Magisk manager app to v7.1.1(203) it reports that Magisk is not installed at all, and any update of Magisk itself resulted in just the same. So I reverted back to v6.1.0(165) and everything seems to be okay, except that o2banking doesn't work. SafetyNet is clean, Magisk is hidden for o2banking and Magisk manager is repacked.
Does anybody know what the problem might be? Especially with that new version of the manager app, but also with Magisk v19.0 which cannot be installed from v6.1.0 (max. is v18.1). Any ideas welcome! I'm now on OOS 5.0.8 by the way.
SOLVED it myself: As mentioned somewhere in the update FAQ of Magisk there was a bug in manager v6.1.0 that causes the updated v7.1.1 to co-exist with the old version if the old version has been re-packed. If anybody encounters the same problem, the solution is at the bottom of this page: https://www.didgeridoohan.com/magisk/ManagerIssues.
o2banking will then still not work. Update to v19.0 is mandatory. But that is no problem then any more...

probably your banking app identified oxygen os as custom rom and have root. 1 out of 3 banking app in my phone doesn't work with lineageos even though i already hide magisk, but when running oxygen os with magisk hide, and also hide magisk manager (turn it on in magisk manager setting) all 3 banking app work just fine. maybe try sending a message to bank app developer to add oxygen os as exception.

Did you notice my edit? It was a problem with magisk manager update and magisk main version. Now everything is back up and running.

Kernal or ROM that hides KNOX Trip?

Hello,
I rooted and installed a custom ROM on my Note 9 a couple of months ago and yesterday I was getting annoyed not being able to use apps like Android Pay, Samsung Pay and Banking apps, So I decided to use Odin to flash the stock ROM back and set OEM Unlock to OFF. To my Horror, I found out the hard way about what a KNOX Trip was. I have no idea how I missed all the warnings on every ROM post about tripping it and not being able to change it back. I can now use my Banking apps, Android Pay and play Fortnite however, Because of the Knox being tripped I can no longer use Samsung Health and Samsung Pay
My Question is is there a way to just install a custom kernel or ROM that tricks apps like Samsung Pay and Samsung Health into working again without installing root and having modifications hidden so I can use my Banking apps and play games??
Any Help is very much appreciated!

After a bit more searching the forums and Google I now understand that no matter what I do I can't get Samsung pay to work which is fine. However any help on the rest is still appreciated! ?

You should go read some more as you also missed the part where tou can use magisk hide. but it wont get back spay.
Just use the forum sarch feature as if you were google searching ie:
magisk shealth
magisk hide
magisk google pay
magisk android pay
magisk insert what ever query

bober10113 said:
You should go read some more as you also missed the part where tou can use magisk hide. but it wont get back spay.
Just use the forum sarch feature as if you were google searching ie:
magisk shealth
magisk hide
magisk google pay
magisk android pay
magisk insert what ever query
Click to expand...
Click to collapse
I did use Magisk Hide to hide root from apps but some apps could still detect the custom rom was installed.

VortexHD said:
I did use Magisk Hide to hide root from apps but some apps could still detect the custom rom was installed.
Click to expand...
Click to collapse
so for example you went to magisk hide menu and selected your banking app and it didnt work?

bober10113 said:
so for example you went to magisk hide menu and selected your banking app and it didnt work?
Click to expand...
Click to collapse
Yes i selected my banking app along with google pay and all its services and Samsung pay with its services and none of them worked.
This also doesn't work for pokemon go and fortnite.

VortexHD said:
Yes i selected my banking app along with google pay and all its services and Samsung pay with its services and none of them worked.
This also doesn't work for pokemon go and fortnite.
Click to expand...
Click to collapse
how about safety net status, is it passing?

bober10113 said:
how about safety net status, is it passing?
Click to expand...
Click to collapse
Yes Everytime. I'm about to flash TWRP and only install a custom kernal with no root.

VortexHD said:
Yes Everytime. I'm about to flash TWRP and only install a custom kernal with no root.
Click to expand...
Click to collapse
try endurance. but besure ure rom base matches kernel ramdisk or u won't be able to get past lock screen. so do a full twrp backup in case
or just try dr ketan. usualy best all round working rom.

bober10113 said:
try endurance. but besure ure rom base matches kernel ramdisk or u won't be able to get past lock screen. so do a full twrp backup in case
or just try dr ketan. usualy best all round working rom.
Click to expand...
Click to collapse
I have installed a custom rom without root access and my banking app and games work perfectly however Google pay is detecting the unlocked bootloader. Anyway to hide this with out rooting the phone?

VortexHD said:
I have installed a custom rom without root access and my banking app and games work perfectly however Google pay is detecting the unlocked bootloader. Anyway to hide this with out rooting the phone?
Click to expand...
Click to collapse
for google pay, some actualy revert to an older version. just search the forums. for me magisk hide works great with my banking app. and for games, im not much of a gamer so i realy dknt know. but again you should try with dr. ketan rom just in case it works. just choose to flash kernel and magisk during setup.( do a clean install so factory wipe in twrp before flashing his rom)

Well i decided to just use Stock Rom and lock the bootloader so at least most of my apps then work. I installed a modified apk of Samsung Health but it doesn't contain the heart rate monitor but I suppose that's fine and I just have to accept that Samsung Pay will never work again

Where can i get the old version of Google pay which works with unlocked bootloader?
Sent from my SM-N960F using Tapatalk

S heath can work on a rooted device with a simple change to the build prop , but secure folder and spay remain a dud

Sky go help needed to hide root with magisk

On my phone xiaomi A1 rooted it works on the wife's phone xiaomi note 5 pro rooted it used to work fine but for some reason it has suddenly detected root and won't work now. I have checked all the settings to do with hiding are still selected as before, strange thing is it has worked briefly for a few seconds but then stopped again.
Please can people tell me if they have had this happen and how they fixed it please.
What checks is it doing to detect root does anyone know?
Thanks

hycraig said:
On my phone xiaomi A1 rooted it works on the wife's phone xiaomi note 5 pro rooted it used to work fine but for some reason it has suddenly detected root and won't work now. I have checked all the settings to do with hiding are still selected as before, strange thing is it has worked briefly for a few seconds but then stopped again.
Please can people tell me if they have had this happen and how they fixed it please.
What checks is it doing to detect root does anyone know?
Thanks
Click to expand...
Click to collapse
Try updating magisk.
Try to disable xposed modules.
Try to disable all modules.
See if it works now.
Then one by one reenable them.
Sent from my SM-G985F using Tapatalk

vash_h said:
Try updating magisk.
Try to disable xposed modules.
Try to disable all modules.
See if it works now.
Then one by one reenable them.
Sent from my SM-G985F using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.

hycraig said:
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.
Click to expand...
Click to collapse
Credits Google
Now safetynet fails after March update
You need to change device props to pixel or lock bootloader

hycraig said:
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.
Click to expand...
Click to collapse
Biggest_Noob said:
Credits Google
Now safetynet fails after March update
You need to change device props to pixel or lock bootloader
Click to expand...
Click to collapse
My safteynet passes fine on both my devices
Thanks

somehow they manage to detect root even if magisk manager is running under custom package name and magisk hide is enabled.
Last version that is still running is 13.1.1 (apk available on apkmirror).

h4lli said:
somehow they manage to detect root even if magisk manager is running under custom package name and magisk hide is enabled.
Last version that is still running is 13.1.1 (apk available on apkmirror).
Click to expand...
Click to collapse
thanks @h4lli i couldn't see sky go version 13.1.1 for uk
so i got Sky Go UK 12.4.14 from apkmirror and can confirm is working fine

yeah still doesnt work, latest sky go app 20, latest magisk, still detects, anyone able to reverse the sky app to see what methods its using?

Fyi - any version other than the latest (20.6.1) at the moment forces an upgrade to 20.6.1, which then detects root.
Safety net is passing both basic and cts with Eval type basic. I'm on latest canary (20425).
I've tried :-
Uninstalling all apps that skygo could look for (titanium, openvpn etc.)
Using a work profile (shelter and island)
Disabling oem unlocking
Disabling usb/adb debugging
Disabling developer options
Deleting all files and folders that have magisk, twrp or titanium in them.
Basically everything here https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
So, I think it's basically no go for sky go at the moment. Happy to be corrected if someone has it working.
Beardy

beardymarrow said:
Fyi - any version other than the latest (20.6.1) at the moment forces an upgrade to 20.6.1, which then detects root.
Safety net is passing both basic and cts with Eval type basic. I'm on latest canary (20425).
I've tried :-
Uninstalling all apps that skygo could look for (titanium, openvpn etc.)
Using a work profile (shelter and island)
Disabling oem unlocking
Disabling usb/adb debugging
Disabling developer options
Deleting all files and folders that have magisk, twrp or titanium in them.
Basically everything here https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
So, I think it's basically no go for sky go at the moment. Happy to be corrected if someone has it working.
Beardy
Click to expand...
Click to collapse
Yeah still can't get it working. Damn it.

Hast everyone a sollution for running the sky Go App on rooted phones?

Skygo doesnt Work... hast anyone a sollution?

eula1977 said:
Skygo doesnt Work... hast anyone a sollution?
Click to expand...
Click to collapse
Have you tried this? It worked for me
SkyGo app detected root!
Hi everyone i have a problema using SkyGo app on my device because It detects the root. I renamed magisk , used magisk Hide , tried magiskhide props config , tried to delete cache and re-install SkyGo app but nothing worked...any solution...
forum.xda-developers.com

Question Finally got my m11u, 2 more hurdles!

Hi guys, coming from a OnePlus 5t, got my m11u and finally waited the 168hrs! Following the instructions on the first post and finally got the bootloader unlocked, I found that was the hardest part, as I had to figure out on my own how to set up adb and the unlock tool etc. But thanks to YouTube I got through and now on EU 13.0.9.0 stable.
During the first week waiting for the unlock, I was hopeful of seeing if I can just enjoy the CN MIUI 13 ROM...deleted as many CN apps, installed Google Play etc and it seemed to be going well....until I noticed the huge problem w getting call and msg notifications. That was already a dealbreaker and seems like no real solution but to continue with a new ROM.
Now using the EU 13.0.9, everything seems great and working well. Except, I am trying to install Vanced youtube but cannot! On the CN ROM it was simply to turn off MIUI optimization in dev options, but xiaomi.eu has removed that option (cannot get the toggle even by pressing reset multiple times). What are my options at this point? Am I left with only option to root the device?
if so, I will try to learn to do it, but I'm hoping someone can point me towards the correct path. There is a how to thread here but it seems outdated as it refers to MIUI 12 and not 13(a12). So far from what I understand:
- a12 root is done with latest magisk v24+
- however v24 no longer use hide magisk and need to use zygisk and a deny list
- bear in mind I don't understand what the above means yet
- from my current status (newly installed EU ROM), what steps do I take?
- download magisk manager APK and install on phone
- make a patched boot.img - DO I USE THE BOOT.IMG FROM THE EXACT EU ROM I FLASHED?
- use fastboot to boot the patched boot.img?
- after this most tutorials tell me to download hide magisk and such, but v24 will be different
- where to go from here to install Vanced root version, and am I missing any steps? After root, will it affect my banking etc?
any help appreciated! Cheers

VinillaIce82 said:
Hi guys, coming from a OnePlus 5t, got my m11u and finally waited the 168hrs! Following the instructions on the first post and finally got the bootloader unlocked, I found that was the hardest part, as I had to figure out on my own how to set up adb and the unlock tool etc. But thanks to YouTube I got through and now on EU 13.0.9.0 stable.
During the first week waiting for the unlock, I was hopeful of seeing if I can just enjoy the CN MIUI 13 ROM...deleted as many CN apps, installed Google Play etc and it seemed to be going well....until I noticed the huge problem w getting call and msg notifications. That was already a dealbreaker and seems like no real solution but to continue with a new ROM.
Now using the EU 13.0.9, everything seems great and working well. Except, I am trying to install Vanced youtube but cannot! On the CN ROM it was simply to turn off MIUI optimization in dev options, but xiaomi.eu has removed that option (cannot get the toggle even by pressing reset multiple times). What are my options at this point? Am I left with only option to root the device?
if so, I will try to learn to do it, but I'm hoping someone can point me towards the correct path. There is a how to thread here but it seems outdated as it refers to MIUI 12 and not 13(a12). So far from what I understand:
- a12 root is done with latest magisk v24+
- however v24 no longer use hide magisk and need to use zygisk and a deny list
- bear in mind I don't understand what the above means yet
- from my current status (newly installed EU ROM), what steps do I take?
- download magisk manager APK and install on phone
- make a patched boot.img - DO I USE THE BOOT.IMG FROM THE EXACT EU ROM I FLASHED?
- use fastboot to boot the patched boot.img?
- after this most tutorials tell me to download hide magisk and such, but v24 will be different
- where to go from here to install Vanced root version, and am I missing any steps? After root, will it affect my banking etc?
any help appreciated! Cheers
Click to expand...
Click to collapse
- In xiaomi.eu rom, u didnt need to turn off miui opti, they already tweak the rom, so u can install vanced normally (no-root version)
how to root
Installation
The Magic Mask for Android
topjohnwu.github.io
how to hide root : 2:52
- if any app detect root, u can add it in deny list

hungragezone said:
- In xiaomi.eu rom, u didnt need to turn off miui opti, they already tweak the rom, so u can install vanced normally (no-root version)
how to root
Installation
The Magic Mask for Android
topjohnwu.github.io
how to hide root : 2:52
- if any app detect root, u can add it in deny list
Click to expand...
Click to collapse
now that you mentioned it, i went and tried to install it again. I played with some permission settings and now it does work! thank goodness now i don't have to deal with rooting.
thanks!

Question NFC

good evening. I have a problem and I want to know if it happens to someone too. I can't find any custom rom that has NFC support. All the ones I've tried don't even have an option to activate it. Does this have a solution? my device is redmi note 10 pro sweet. Thanks.

I've tried PixelOS and Xiaomi.eu and both have NFC options and can link with Google Pay (I've tried xiaomi.eu NFC pay and it worked, I didn't try PixelOS, but it has the options)

I remember someone asking this before a while back, and my response is frankly the same (and just as puzzled) - I don't think I've ever seen a sweet ROM that *didn't* have NFC support.

In M2101K6R Japanese versions, nfc does not work on aosp based roms. I am having the same problem

Hmm I am on cr droid and NFC seems to work. With apps like NFC Tools or MIFARE Classic Tool I can read NFC Tags.
Unfortunately Google Pay does not work for me. The pay terminal always say "try again". Dont know what the problem is there

wuslschweiz said:
Hmm I am on cr droid and NFC seems to work. With apps like NFC Tools or MIFARE Classic Tool I can read NFC Tags.
Unfortunately Google Pay does not work for me. The pay terminal always say "try again". Dont know what the problem is there
Click to expand...
Click to collapse
install safetynet fix 2.1 with magisk, then try again.
install safetynet test via playstore and run it. this should be passed now.
If gpay isnt working, go to magisk/settings and activate zygisk. after this, add all google services (use search with "google" and "gms") to the denial-list, reboot phone and try again
if this doesnt the trick, change ROM ;-)
Lineage OS 19.1 is just great. GPay and MIUI Cam working like charme.
links in my signature

I think phone should be encrypted for working NFC (payments).

ottili81 said:
install safetynet fix 2.1 with magisk, then try again.
install safetynet test via playstore and run it. this should be passed now.
If gpay isnt working, go to magisk/settings and activate zygisk. after this, add all google services (use search with "google" and "gms") to the denial-list, reboot phone and try again
if this doesnt the trick, change ROM ;-)
Lineage OS 19.1 is just great. GPay and MIUI Cam working like charme.
links in my signatur
Click to expand...
Click to collapse
I checked with this SafetyNet Test app. All tests passed without magisk. Anyway I would expect a fault message in google pay if something safety related is not ok, same as in banking apps, which are working fine.
Was also thinking to change to lineage but right now I am not motivated to reinstall the phone completely because its my daily driver^^
@otttili81 how can I see your signature?

wuslschweiz said:
I checked with this SafetyNet Test app. All tests passed without magisk. Anyway I would expect a fault message in google pay if something safety related is not ok, same as in banking apps, which are working fine.
Was also thinking to change to lineage but right now I am not motivated to reinstall the phone completely because its my daily driver^^
@otttili81 how can I see your signature?
Click to expand...
Click to collapse
Use Desktop PC to open XDA

Google Pay (well, Wallet now) can be incredibly finicky. Also sometimes it might seem like it has a security issue, but actually it's something else, like the card not being set up properly (but appearing like everything's fine).

Case_ said:
Google Pay (well, Wallet now) can be incredibly finicky. Also sometimes it might seem like it has a security issue, but actually it's something else, like the card not being set up properly (but appearing like everything's fine).
Click to expand...
Click to collapse
Yes everything looks fine in the wallet itself. Only when it comes to payment, the terminal refuses it. I tried several cards. Also reinstallation of the app.
Is there a possibility to check or test it except on the payment terminal?

@wuslschweiz What kernel are you running? Some kernels can cause issues like this.
I just came off a clean install of the current crDroid with Flame GApps last week and Google Pay was working perfectly fine, I didn't have to do a thing except the usual Zygisk deny list setup.

Case_ said:
@wuslschweiz What kernel are you running? Some kernels can cause issues like this.
I just came off a clean install of the current crDroid with Flame GApps last week and Google Pay was working perfectly fine, I didn't have to do a thing except the usual Zygisk deny list setup.
Click to expand...
Click to collapse
@Case_
Standard crDroid kernel 4.14.290-sigmaKernel-v1.0
I havent rooted my phone so no Magisk or Zygisk.
But good to know that Google Pay is working on your phone so the problem is my phone.
Now when you mention kernel I remember I seem to have a firmware problem (notification volume level is related to sound volume)
Maybe also something NFC/GPay is related to this.
Is it better to flash MIUI 13.8 firmware with miui flash tool or twrp?

Flash it with twrp

wuslschweiz said:
Hmm I am on cr droid and NFC seems to work. With apps like NFC Tools or MIFARE Classic Tool I can read NFC Tags.
Unfortunately Google Pay does not work for me. The pay terminal always say "try again". Dont know what the problem is there
Click to expand...
Click to collapse
GPay is a bit of hit and miss. Make sure it says 'Device is certified' in Playstore settings. It usually won't work without it. It's also very dependent on Kernel. There is also an option to reset NFC in settings, which helped me a few times.

Seems like I am just to dumb for Google Pay.
I reflashed Miui 13.08 firware via TWRP and then LOS 19.1L. Installed Magisk to restore Apps and Appdata wirh Alpha Backup Pro. Uninstalled Magisk (I dont need Root) Installed Google Pay, Still not working, same as bevore.
If I am motivated, maybe I try Google Pay on Stock MIUI...
Thx to all for the help

wuslschweiz said:
Seems like I am just to dumb for Google Pay.
I reflashed Miui 13.08 firware via TWRP and then LOS 19.1L. Installed Magisk to restore Apps and Appdata wirh Alpha Backup Pro. Uninstalled Magisk (I dont need Root) Installed Google Pay, Still not working, same as bevore.
If I am motivated, maybe I try Google Pay on Stock MIUI...
Thx to all for the help
Click to expand...
Click to collapse
Storage is encrypted? It won't work with out it.

pablo.see said:
Storage is encrypted? It won't work with out it.
Click to expand...
Click to collapse
I havent done anything special to encrypt it but when I boot into TWRP it requests a PW to decrypt so I assum it is encrypted