Hey.
I wanted to use Android Pay on my LG G3 (LGD855) 6.0 LP, but i had root , TWRP and Xposed installed.
So i read some article and installed Magisk (root uninstalled before ofc) - SafetyNet OK, Magisk Hide turned on - but i still can't get Pay working.. same notfication "You can't use Android Pay on this device"
Any suggestions?
@edit
Tried do Full Data Wipe (factory reset) through TWRP, but now i have SafetyNET Mismatch error....... hilarious
look for universal safetynet fix, I'm using latest beta, myself if your on version 12 don't touch check systemless busybox use osmosis busybox. Don't check systemless host files either and confirm that your hiding android pay and the settings are sticking after closing magisk. Hiding Google Play store as well is what I do. I've never had CTS pass until I tried universal safetynet fix, worked well for me even on a Samsung!
Hi, thanks for reading.
I've used Magisk 17.3 with all my bank apps perfectly, with Magisk hide and Magisk manager hidden.
After update to 18.0 and update manager to 6.1, the bank apps start detecting root status, and stop working.
So, I've flashed back to 17.3 and old manager 6.0.1, and everything's back to working normally.
My system:
Poco F1
LineageOS 16.0 built 27/11/2018
The apps are from Thai's banks:
SCB EASY: detected root, still working
TMB Touch: detected root, stop working
KTB Next: detected root, working partially
If you'd want any log or anything, please also tell me how to get them.
Adios2nd said:
Hi, thanks for reading.
I've used Magisk 17.3 with all my bank apps perfectly, with Magisk hide and Magisk manager hidden.
After update to 18.0 and update manager to 6.1, the bank apps start detecting root status, and stop working.
So, I've flashed back to 17.3 and old manager 6.0.1, and everything's back to working normally.
My system:
Poco F1
LineageOS 16.0 built 27/11/2018
The apps are from Thai's banks:
SCB EASY: detected root, still working
TMB Touch: detected root, stop working
KTB Next: detected root, working partially
If you'd want any log or anything, please also tell me how to get them.
Click to expand...
Click to collapse
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Sent from my Nexus 6P using Tapatalk
Can confirm that this works, thanks.
For me, it started getting detected on 17.x even before updating to 18, right after the banking app (Sparkasse) was updated.
LG G6.
hsiehboss said:
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This didn't work for me. I had to downgrade back to 17.1 to get my banking app working again. Appears that the root detection prevention is a regression in this latest version.
-- SSS
hsiehboss said:
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Click to expand...
Click to collapse
This doesn't work for me.
Did all of these...still got detected.
I have the same problem. Magisk says: ctsProfile: False and Google Pay don't work. Also my Banking App detects root.
I flashed today the latest Los 15 build and the crt false error is till there after flashing magisk 18. The same error is also with 17.4...
Tell me if I'm wrong but I believe we have two different reports: the original report where root is detected, and the ctsProfile/basicIntegrity failing. The second one is a regression fixed by rebooting device (however, it is annoying to reboot 10 times a day because suddenly SafetyNet fails for no reason).
I am using Magisk Hide Props module, and after 18.0 update Santander App detects root, even with Magisk Manager says I pass safetynet
It's happened with my bank app as it detected root & saftynet false and have to downgrade to ver.17.2
Sent from my SM-C900F using Tapatalk
See in install app delete old magisk manager, after install magisk 18.0 new magisk manager rename to manager.
I have same problem. After install v18 magisk, same bank app can detect the system is rooted. Downgrade to v17.2, all bank app become normal.
Same here since Magisk 18 my BankApp (Intesa Sanpaolo) start and says that there is a safety problem and it close, if I choose Magiskhide it doesn't start at all.
SafetyNet check spin without an end.
With Magisk 17.1 and 17.3 no problem at all.
Same problem here, after upgrading to Magisk 18 claiming to better hide root in the history, apps now suddenly detect root.
This affects also the Safety Net check and Google Pay... so far, Root Hiding in 18.0 seems COMPLETELY broken.
A solution would be great.
Later... after downgrading to Magisk 17.2, MagiskHide is working for me again and Safetynet checks succeed. The dev is aware of the problem, an issue is open on the Magisk Github (#907)
After uninstalling and reinstalling my bankapp now works without any problem and doesn't detect root even if is not under Magisk hide
I can confirm the v18 update breaks something and BOTH safety net checks fail. So all apps detect you are rooted, especially bank apps and Get Pay. Downgrading back to v17 restored everything to normal.
The only thing I could think of is the installation method. I did the direct install rather than installing the zip via recovery. Not sure if it makes a difference but I will wait for next release.
I am on a Pixel 2 with Android Pie updated to the Aug 2018 release.
---------- Post added at 12:47 PM ---------- Previous post was at 12:43 PM ----------
Harlock1978 said:
After uninstalling and reinstalling my bankapp now works without any problem and doesn't detect root even if is not under Magisk hide
Click to expand...
Click to collapse
I did not uninstall but tried clearing bank app data and cache and the problem persisted. Magisk still showing all red for safetyNet. Just sharing testing feedback.
@Djtrip83 Did you try just toggling MagiskHide off and on once after updating to v18? Sometimes MagiskHide simply needs a restart after an update...
I did that too. Toggled Hide on and off for all apps. Repackaged Magisk. Turned off USB debugging. Removed modules installed. Tried everything I thought would work. Even restored hosts in case Ad Away affected something on /system.
The only thing I did not do was remove root apps and re-install them to re-grant permissions after the Magisk update. And I wonder now if uninstalling Magisk completely and make a brand new clean install with v18 would work rather than upgrading.
I was at a loss so I downgraded. Sorry I don't have a log to share. However, v17 works fine.
Djtrip83 said:
I did that too. Toggled Hide on and off for all apps. Repackaged Magisk. Turned off USB debugging. Removed modules installed. Tried everything I thought would work. Even restored hosts in case Ad Away affected something on /system.
The only thing I did not do was remove root apps and re-install them to re-grant permissions after the Magisk update. And I wonder now if uninstalling Magisk completely and make a brand new clean install with v18 would work rather than upgrading.
I was at a loss so I downgraded. Sorry I don't have a log to share. However, v17 works fine.
Click to expand...
Click to collapse
We might be misunderstanding each other, but what I'm talking about is simply to go to the Manager settings and change the toggle for MagiskHide to off and then on. No need to do anything to the Hide list or anything else... Did you do that? As I said, that's sometimes something you the to do after an update, but it's rare.
After installing xiaomi.eu and Magisk on my device, I cannot manage to make a mobile payment app to work (I don't have access to Gpay, I use a newly released app called RaiPay from Raiffeisen Bank).
Magisk passes safetynet. I followed a guide to make Gpay work ( installed Busybox, gpay sqlite fix and sqlite for amr aarch64 through Magisk, then hid the app for RaiPay through Magisk Hide).
Still, after following all these steps, I get: device does not match the application requirements.
Any ideas as to how I could possibly fix this issue?
//Fixed it by going to magisk settings and hiding magisk manager.
2 question:
does actually by rooting Pixel 5 will make loose Google Pay functionality ?
does Bank apps will be affected from root here ?
Whitch methods to 100% make working things above ?
Hi!
For 1) use safetynet fix - https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
For 2) use magisk hide feature
This is how it works for me without any issues
somin.n said:
Hi!
For 1) use safetynet fix - https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
For 2) use magisk hide feature
This is how it works for me without any issues
Click to expand...
Click to collapse
can you tell me:
how to force an app in Full Screen ? I can't see any option to make this job.
the best app here to make camera ring notifications ?
Just an fyi, some apps can still detect root. I have root via magisk, safety net fix, magisk hide for apps needing it with safety net passing but Chase app, while it runs, certain features such as points, redemption etc fail with the message about root or malware devices.
wolfgart said:
can you tell me:
how to force an app in Full Screen ? I can't see any option to make this job.
the best app here to make camera ring notifications ?
Click to expand...
Click to collapse
Are you talking about the black bar that covers the camera hole in landscape mode? There's a new magisk module that fixes that.
Download the module.zip from here: https://github.com/logmd/N3O-No-Nonsense-Notch-Overlay/releases
Flash that with Magisk Manager and reboot.
Go to settings > system > developer options > scroll down to display cutout > select the Pixel 5 option
That's it, no more black bar
wolfgart said:
2 question:
does actually by rooting Pixel 5 will make loose Google Pay functionality ?
does Bank apps will be affected from root here ?
Whitch methods to 100% make working things above ?
Click to expand...
Click to collapse
I was shocked this worked so easily, but if yiu go into the terminal just issue this command:
Code:
chmod 440 /data/data/com.google.android.gms/databases/dg.db
```
For me Google pay immediately started working, don't really remember where I found this tip somewhere googling...lol so credit to unknown.
I've been successfully able to use GPay and other security/DRM sensitive apps with the folllowing:
Magisk 23001 with MagiskHide and Universal SafetyNet Fix 2.1.1
Magisk 23014 with DenyList and Universal SafetyNet Fix 2.2.0
Use MagiskHide/DenyList on all components of Google Play Services (com.google.android.gms) and Google Play Store (com.android.vending), as well as GPay, banking apps, and DRM sensitive apps such as Netflix, Hulu, Prime Video, etc.
Hi, I've been trying to get the fingerprint to work in GSI with no luck.
Currently, you can start the enrollment process and the fingerprint icon appears in the correct place, but as soon as you touch the icon, the enrollment fails.
Has anyone else tried to get it to work?
Looking at logs, the oplus.fingerprint service crashes with a "null pointer dereference" and there are a lot of denied permissions.
Has anyone gotten closer, or has any idea what to do?
Btw, I'm on
PixelExperience_Plus_treble_arm64_bvN-12.1-20230217-1612-meowice-gsi
Welp, then try to find a ROM which had working fingerprint
If it even doesnt work, downgrade to stock.
As you install any GSI, you are responsible for not working functions.
Update, I got closer, yet still far.
By extracting biometric related frameworks from stock ROM (installed via a magisk module) I was able to get the "Face & Fingerprint" option back in the settings menu.
Registration still doesn't work due to vendor.oplus.hardwsre.osense.client being missing. I can't figure out how to bootstrap this framework as 'getTrasport' tells me that it's missing from VINTF manifest. Help very much wanted (See attached file)
You can still get face unlock working via https://github.com/null-dev/UniversalAuth xposed module, like I've done! For now that is.
melontini said:
Update, I got closer, yet still far.
By extracting biometric related frameworks from stock ROM (installed via a magisk module) I was able to get the "Face & Fingerprint" option back in the settings menu.
Registration still doesn't work due to vendor.oplus.hardwsre.osense.client being missing. I can't figure out how to bootstrap this framework as 'getTrasport' tells me that it's missing from VINTF manifest. Help very much wanted (See attached file)
You can still get face unlock working via https://github.com/null-dev/UniversalAuth xposed module, like I've done! For now that is.
Click to expand...
Click to collapse
Its not working because it doesnt have "end-points, client is missing tho.
Try extracting that client from stock ROM,
Give the application all permisions, allow that app to work in background.