Related
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.
Just wanted to create a thread similar to the Pokémon Go one because i've seen the only one having problems with this app and magisk despite the John announncement made in September...
Anyway, back to the main topic, in this thread i would like to gather all users with some requirements:
- Fate GO istantly closes, opens the default mail app and prompts the "Error 61" in the mail, other errors have nothing to do with magisk.
- Latest version of Magisk Dev
- Magisk Hide enabled and Fate GO ticked in the list
- Magisk Manager hidden
- Check if other apps (Like GPay for example) find Magisk/Root or not
- Safetynet "full" passes
- No Xposed
- Running the uninstaller of magisk makes Fate GO working normally
- Always write: ROM, Kernel, Magisk Version, Fate GO version and region (NA, CN, JP ecc...)
Thanks in advance to everyone that will help with this problem or share their experiences or thoughts, and if someone else would like to test itself you can find the apk on APKPure if it's no present on play store.
Make sure USB debugging is disabled, then if that doesn't work, clear the data for the app
Sent from my Pixel using Tapatalk
Hello, I'm sorry for you, but I'm the same, and the worst is that I recently installed magisk, just yesterday, because I thought it would work with Fate G / O but apparently I happen the same as you, it was supposed to be fixed, right?
By the way, just to complete other apps I can't find magisk.
-StockRom Android 6.
-Kernel 3.18.19+
-Last Magisk Dev
-Last ver JP and NA
Chocobubba said:
Make sure USB debugging is disabled, then if that doesn't work, clear the data for the app
Click to expand...
Click to collapse
Debug usb has nothing to do with error 61, which is magisk, that's why I specified it in the list xD
Niiya said:
Hello, I'm sorry for you, but I'm the same, and the worst is that I recently installed magisk, just yesterday, because I thought it would work with Fate G / O but apparently I happen the same as you, it was supposed to be fixed, right?
By the way, just to complete other apps I can't find magisk.
-StockRom Android 6.
-Kernel 3.18.19+
-Last Magisk Dev
-Last ver JP and NA
Click to expand...
Click to collapse
Yep, it was supposed to bi fixed since September, but the majority of the players here and on reddit reported the opposite, I've tried anything suggested and to ask it many times in many threads and for now I'm stuck with a not-rooted OP6...
Btw I got it "barely working" with the app "Island" but I say "barely" because sometimes it didn't work.
Killua96 said:
Debug usb has nothing to do with error 61, which is magisk, that's why I specified it in the list xD
Yep, it was supposed to bi fixed since September, but the majority of the players here and on reddit reported the opposite, I've tried anything suggested and to ask it many times in many threads and for now I'm stuck with a not-rooted OP6...
Btw I got it "barely working" with the app "Island" but I say "barely" because sometimes it didn't work.
Click to expand...
Click to collapse
I tried flashing the reddit hide zip and several more until I surrendered, after all I gave him delete without remembering to save the save code.
It's weird, because I installed magisk believing that go would work, if a bank app works because it wouldn't work fate GO?
It seems that I was wrong.
Niiya said:
I tried flashing the reddit hide zip and several more until I surrendered, after all I gave him delete without remembering to save the save code.
It's weird, because I installed magisk believing that go would work, if a bank app works because it wouldn't work fate GO?
It seems that I was wrong.
Click to expand...
Click to collapse
Btw my bank app doesn't work with and without magisk, anyway the problem is that FGO was advised as playable since September and it's not...
Hello, i get some problems like this. My device - Asus me302kl with Nitrogen os 8. I install magisk (canary), hide fate app, and rebuilt magisk with new package name. After killing process in app settings i can play, but after some time (i think when magisk has autolaunch) fate found magisk and i recieve error 61. After this I need restore and rebuild package again, for normal fgo launch.
Now i try something for stable result.
This could be interesting: https://twitter.com/topjohnwu/status/1064941972375392257?s=19
Let's see if he can do something about it...
Killua96 said:
This could be interesting: https://twitter.com/topjohnwu/status/1064941972375392257?s=19
Let's see if he can do something about it...
Click to expand...
Click to collapse
And in fact now magisk is not detected at all by FGO, finally...!
For a moment I got error 43 so I deactivated the USB debug, but then I went back to error 61, is it still possible that it is an error of my device?
The developer options are activated permanently because oem unlock is activated.
Niiya said:
For a moment I got error 43 so I deactivated the USB debug, but then I went back to error 61, is it still possible that it is an error of my device?
The developer options are activated permanently because oem unlock is activated.
Click to expand...
Click to collapse
If you have added fgo to the magisk hidelist, and have hidden MagiskManager trough the option in the settings then you could try to use the ProcGate apk and see if the proc bug is the issue.
FGO works well now, no errors or anything. This is great because I use root regularly, but wasn't willing to let go of it.
:victory:
I have android 6, well I can always use an emulator.
Just tried this game and can't open just white screen and there some gmail option
-AEX N 7.1
-latest mgisk cannary
-3.10.108
-latest NA
I can play dragalia lost just fine with magisk hide,this game sure annoyingxD
Edit: Oookay its weird,I just reboot my device and it work like a charmxD
Niiya said:
I have android 6, well I can always use an emulator.
Click to expand...
Click to collapse
Check with procgate app if you have leaks, if there are unfortunately there aren't solutions atm on Android versions bellow nougat...
Well looks like this topic is a bit dead. Is Fate GO still working with Magisk?
I can't seem to get it working. Keep getting error 61 & 60
Running on 7.1 LineageOS with latest canary build
Both Fate GO & MM are hidden
All safetynet checks passed
Freshly flashed ROM, no Xposed or anything
No leaks detected in Procgate
Running magisk uninstaller makes Fate GO working normally
AsakuraVN said:
I can't seem to get it working. Keep getting error 61 & 60
Running on 7.1 LineageOS with latest canary build
Both Fate GO & MM are hidden
All safetynet checks passed
Freshly flashed ROM, no Xposed or anything
No leaks detected in Procgate
Running magisk uninstaller makes Fate GO working normally
Click to expand...
Click to collapse
What error code you have last? 61?
Try hide MM from framework+google apps
Lordische said:
What error code you have last? 61?
Try hide MM from framework+google apps
Click to expand...
Click to collapse
Already tried. Right now it's 60.
Guilhermex12 said:
Well looks like this topic is a bit dead. Is Fate GO still working with Magisk?
Click to expand...
Click to collapse
Yes. Poke GO and FGO work with Magisk - at least with 17.4 and 18.1. i played Fate a few days ago, no problem on Pie.
I just bought a Pixel 3a from swappa.com. One of the things that I've noticed is that when I run any Niantic games, it tells me my device or OS is incompatible with this version. I suspect this may be because the bootloader is unlocked? However, the phone is NOT rooted.
Any ideas on what my options would be? Had a chat with Google and they're supposed to be emailing me once their experts find a solution, but not crossing my fingers on that. I already tried locking the bootloader with fastboot and had a freakout (was able to unlock it again and factory reset, LOL . . . )
summerblink said:
I just bought a Pixel 3a from swappa.com. One of the things that I've noticed is that when I run any Niantic games, it tells me my device or OS is incompatible with this version. I suspect this may be because the bootloader is unlocked? However, the phone is NOT rooted.
Any ideas on what my options would be? Had a chat with Google and they're supposed to be emailing me once their experts find a solution, but not crossing my fingers on that. I already tried locking the bootloader with fastboot and had a freakout (was able to unlock it again and factory reset, LOL . . . )
Click to expand...
Click to collapse
I'm unlocked, rooted (stock ROM and kernel), and spoofing gps and I'm still able to play Pokemon Go.
I'd recommend flashing the latest stock factory image to clear out anything the old user may have left behind.
If that doesn't work I'd root using Magisk, then hide Magisk and applicable apps.
gargleblarg said:
I'm unlocked, rooted (stock ROM and kernel), and spoofing gps and I'm still able to play Pokemon Go.
I'd recommend flashing the latest stock factory image to clear out anything the old user may have left behind.
If that doesn't work I'd root using Magisk, then hide Magisk and applicable apps.
Click to expand...
Click to collapse
Ok, cool, I'll try that! Thanks for the reply!
Wiped and rooted phone, installed stock rom from Google, and it worked! Pokémon Go AND Wizards United working. Thanks so much!
Im on Stock Rooted and Ex Kernel all you have to do is go to magisk use Mgaisk Hide the games and go into settings then HIDE Magisk or i think its repackage hide something aroudn that and yeah it works oh also you have to turn off debugging in dev options.
summerblink said:
Wiped and rooted phone, installed stock rom from Google, and it worked! Pokémon Go AND Wizards United working. Thanks so much!
Click to expand...
Click to collapse
If you decide to use the GPS spoof, I highly recommend fakegps route, it gives you a thumb stick so you can walk around while being a couch potato. It's 4 bucks.
Just use the Magisk module "systemize" to make it a priv-app, restart your phone, uninstall the app from the app store, enable expert mode in the GPS app, then disable fused locations the GPS app.
gargleblarg said:
If you decide to use the GPS spoof, I highly recommend fakegps route, it gives you a thumb stick so you can walk around while being a couch potato. It's 4 bucks.
Just use the Magisk module "systemize" to make it a priv-app, restart your phone, uninstall the app from the app store, enable expert mode in the GPS app, then disable fused locations the GPS app.
Click to expand...
Click to collapse
i have not been able to use any systemized priv-apps to work, they all crash the instant they open on 10, are you still on 9?
Xepherxv said:
i have not been able to use any systemized priv-apps to work, they all crash the instant they open on 10, are you still on 9?
Click to expand...
Click to collapse
I'm still on 9
I'm trying to use this app: play.google.com/store/apps/details?id=br.com.banrisul
I've added to the hiding list and enable core only mode, it still closes at startup after saying my phone is either root or running a modified system. I've tested with rootbeercheck and it doesn't detect root in any of its tests.
i.imgur.com/60Zs5IH.png
No issues opening the app here... That means Magisk is perfectly capable of hiding from it, but you might have something else in your setup that triggers it.
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Didgeridoohan said:
No issues opening the app here... That means Magisk is perfectly capable of hiding from it, but you might have something else in your setup that triggers it.
Click to expand...
Click to collapse
but what exactly would trigger it? The link talks mostly about methods to hide magisk, I didn't find anything about what to do if magisk is working but the check fails. I've uninstalled titaniumbackup and rootbrowser. I've disable adb and developer options, I've deleted any folder or downloaded file related to magisk or those apps.
I'm running lineageos, would that be it? How would I go about it?
Could be any number of things... Your ROM might be one of them (more details about that?). It's pretty much impossible for me to do anything else but make educated guesses. The only thing I can say with relative certainty is that it shouldn't have anything to do with Magisk (since I can hide from the app just fine when testing).
You do pass SafetyNet, right? Could be that this is one of those apps that actually use SN.
Didgeridoohan said:
Could be any number of things... Your ROM might be one of them (more details about that?). It's pretty much impossible for me to do anything else but make educated guesses. The only thing I can say with relative certainty is that it shouldn't have anything to do with Magisk (since I can hide from the app just fine when testing).
You do pass SafetyNet, right? Could be that this is one of those apps that actually use SN.
Click to expand...
Click to collapse
It passes both checks.
I am running lineage OS 14.1 (Android 7.1.2) on a moto g4.
My main guess is that it's detecting something about your ROM. LOS is well known enough for apps to look for certain properties of it.
Didgeridoohan said:
My main guess is that it's detecting something about your ROM. LOS is well known enough for apps to look for certain properties of it.
Click to expand...
Click to collapse
Yes, after searching around a bit more I found about why. I completely forgot that I had flashed supersu on my phone before flashing magisk. So I guess that's what the app was freaking out about. So I flashed a supersu removal and reflashed my ROM, now the app is working normally
Thanks for the help!
Same problem
Hello everyone
After the last update of my banking app and wallet too
Both apps stopped starting due tl root device detection
While it was working well yesterday
I just updat apps to the last version
I think these app's developers find a way to detect magisk
Of course im hiding and randomly renaming it
hammohammo said:
Hello everyone
After the last update of my banking app and wallet too
Both apps stopped starting due tl root device detection
While it was working well yesterday
I just updat apps to the last version
I think these app's developers find a way to detect magisk
Of course im hiding and randomly renaming it
Click to expand...
Click to collapse
What version of the application do you want?
I have the latest version installed and it does not detect root
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