Related
I've recently rooted my OP6 and added bank application like indusnd and icici as well Google pay to Magisk hide,but it's not working.
Bank applications are giving error that you are on a rooted device.
Any help?
nvrmndryo said:
I've recently rooted my OP6 and added bank application like indusnd and icici as well Google pay to Magisk hide,but it's not working.
Bank applications are giving error that you are on a rooted device.
Any help?
Click to expand...
Click to collapse
probably you should ask the Magisk guys here: Magisk General Support / Discussion
computersalat said:
probably you should ask the Magisk guys here: Magisk General Support / Discussion
Click to expand...
Click to collapse
Thanks
nvrmndryo said:
I've recently rooted my OP6 and added bank application like indusnd and icici as well Google pay to Magisk hide,but it's not working.
Bank applications are giving error that you are on a rooted device.
Any help?
Click to expand...
Click to collapse
working perfectly with me ...!! on google pay paytm & phone pe ...!!!
google pay and paytm works even without magisk hide but phonepe doesn't complete any transactions until i use magisk hide ...!!
ur magisk must pass safetynet or ..non of the apps works !!!
don't use xposed as ....safetynet does not pass becoz of it !!!
In Magisk settings, they should only give you the option to Repack magisk, you assign a new name and voila, after a few seconds the application closes and when you open it will ask you to install the full version you give it in ok and then in magisk hide Select your banking applications, restart and go.
Sorry for m6 bad english im.using a traductor
Magisk Hide works just fine. Some banking apps look for the app named 'Manager' to detect the hidden Magisk and GooglePay is stepping up their game in detections too. If you Google Gpay SQL Lite fix, you may be more successful as that does a little extra. I would also like to add that if you have Riru/EdXposed/Xposed installed, banking apps and Gpay detects that also. Heading into the EdXposed manager settings, turning on App List and then adding Play Store, Play Services, Google Framework GPay and your banking app to the blacklist and reboot, you will then hide EdXposed from them and pass SafetyNet
Hey, my Banking apps arent working. Im rooted on One Plus 7 Android 10.0.10 with Magisk 21.1.
I hide Magisk in its Settings and Restarted but didnt worked for me. Please help!
Banking App: VR-SecureGo
Silazius said:
Hey, my Banking apps arent working. Im rooted on One Plus 7 Android 10.0.10 with Magisk 21.1.
I hide Magisk in its Settings and Restarted but didnt worked for me. Please help!
Banking App: VR-SecureGo
Click to expand...
Click to collapse
Settings/Hide magisk manager and reboot, then tap shield icon the bottom, and tap Magisk hide and check then bank app.
Shyciii said:
Settings/Hide magisk manager and reboot, then tap shield icon the bottom, and tap Magisk hide and check then bank app.
Click to expand...
Click to collapse
Did not Worked...
Is there any other option?
Silazius said:
Did not Worked...
Is there any other option?
Click to expand...
Click to collapse
In order for certain apps to work your device will need to pass safetynet check some apps include banking, entertainment and even a few games. You can check this from within Magisk Manger itself. Some custom roms do not support safetynet and therefore it will not pass while on those roms. However, most do such as LineageOS among others. If you need to pass safetynet then making sure software and vendor is updated is your first step, I don't know all the steps as I am unfamiliar with the process but this applies for any device with Magisk not just the OnePlus 7
Silazius said:
Did not Worked...
Is there any other option?
Click to expand...
Click to collapse
Mr.Conkel said:
In order for certain apps to work your device will need to pass safetynet check some apps include banking, entertainment and even a few games. You can check this from within Magisk Manger itself. Some custom roms do not support safetynet and therefore it will not pass while on those roms. However, most do such as LineageOS among others. If you need to pass safetynet then making sure software and vendor is updated is your first step, I don't know all the steps as I am unfamiliar with the process but this applies for any device with Magisk not just the OnePlus 7
Click to expand...
Click to collapse
Saftynet is okei... So what should i do now?
Considering your passing it, you may want to contact the devs of your rom on this one. Not sure why it wouldn't work even with a successful check but that is your best bet assuming your not on stock that is.
I have Oneplus 8 pro . and i have same problem,
the bank app updated their safety and the old way don't work.
also i pass saftynet.
Silazius said:
Did not Worked...
Is there any other option?
Click to expand...
Click to collapse
XPrivacyLua together Magisk Hide is enough.
Try using my app VD INFOS, you can see every detectable thing. (Root/Magisk/Xposed/Riru/and others.)
And then you can fix what needs to be fixed.
[APP][v1.10] VD Infos (Package: com.vitaodoidao.vdinfos)
(Para quem fala PORTUGUÊS, o próximo post está totalmente traduzido !) VD Infos v1.10 As we all know, Android is a super powerful and super versatile operating system. What nobody tells you is that all your personal details and confidential...
forum.xda-developers.com
I'm facing exactly the same issue, my bank's app checks if OEM unlock is active and if so, it fails to start. This thing cannot be hid by Magisk.
Deus. said:
I'm facing exactly the same issue, my bank's app checks if OEM unlock is active and if so, it fails to start. This thing cannot be hid by Magisk.
Click to expand...
Click to collapse
You can hide it easily.
Just unlock bootloader first and then, erase nvdata.
Nvdata contains developer settings, like "oem unlock".
But, if you aready have an unlocked bootloader, the settings "oem unlock" doesn't change nothing.
Hello Everyone,
I recently installed LineageOS 18.1 (build: lineage_kebab-userdebug 11). I have retrieved my Android ID using the ADB commands found here: Device Registration and registered my Android ID a few days ago but Google Play Store still shows: "Device is not certified" under Settings --> About --> Play Protect certification. Is there something I'm doing wrong or something else I need to do in order to get my device certified with Google Play Store?
use magisk hide props config I use the pixel 5 fingerprint and add new props
ro.product.model Pixel 5
ro.product.manufacturer Google
option 5 add those 2 after you change fingerprint you will pass and get stadia discounts just can't run edxposed I do but a few changes in that you fail hope that helps
ecompton59 said:
use magisk hide props config I use the pixel 5 fingerprint and add new props
ro.product.model Pixel 5
ro.product.manufacturer Google
option 5 add those 2 after you change fingerprint you will pass and get stadia discounts just can't run edxposed I do but a few changes in that you fail hope that helps
Click to expand...
Click to collapse
Thank you for the info. So you are saying in order to get my device "certified" with Google Play Store I need to root my device, add new props and change my fingerprint (I assume you mean Android ID)? I'm not sure what you mean by: "stadia discounts" or "edxposed". Also, I do not see where I need to root my device in the LineageOS documentation or the Google documentation so I'm still unclear why this must be done. Does Google block LineageOS devices from getting "certified" or something?
long as you used dual sim oos file to unlock your phone it won't unless you do something like that and Google thinks I have pixel 5 see pics I pass
alteredstate82 said:
Thank you for the info. So you are saying in order to get my device "certified" with Google Play Store I need to root my device, add new props and change my fingerprint (I assume you mean Android ID)? I'm not sure what you mean by: "stadia discounts" or "edxposed". Also, I do not see where I need to root my device in the LineageOS documentation or the Google documentation so I'm still unclear why this must be done. Does Google block LineageOS devices from getting "certified" or something?
Click to expand...
Click to collapse
Unlocking a bootloader breaks SafetyNet passes. This results in the play store as not being certified which usually hides specific apps such as Netflix and some other banking apps and will break them. Magisk is needed to help with spoofing your device to let the play store know your device is certified. Some ROMs have built in patches in which SafetyNet passes fine without root. I believe lineage does not do this with their ROM, so you will need magisk.
This is actually a decent article which describes this if you desire to read it - https://www.hexnode.com/blogs/safetynet-android-security/
azoller1 said:
Unlocking a bootloader breaks SafetyNet passes. This results in the play store as not being certified which usually hides specific apps such as Netflix and some other banking apps and will break them. Magisk is needed to help with spoofing your device to let the play store know your device is certified. Some ROMs have built in patches in which SafetyNet passes fine without root. I believe lineage does not do this with their ROM, so you will need magisk.
This is actually a decent article which describes this if you desire to read it - https://www.hexnode.com/blogs/safetynet-android-security/
Click to expand...
Click to collapse
Okay that makes sense. According to the: Patching Images section of the How to Install Magisk App guide I can install Magisk to the boot ramdisk (see screenshot). However, the LineageOS build I installed does not contain a "boot.img" in the zip file. There is however a "payload.bin" file which according to the: XDA Magisk Installation Guide I need to use "payload-dumper-go" to extract the boot.img from the payload.bin? Does that about sum it up or is there something else I'm missing?
alteredstate82 said:
Okay that makes sense. According to the: Patching Images section of the How to Install Magisk App guide I can install Magisk to the boot ramdisk (see screenshot). However, the LineageOS build I installed does not contain a "boot.img" in the zip file. There is however a "payload.bin" file which according to the: XDA Magisk Installation Guide I need to use "payload-dumper-go" to extract the boot.img from the payload.bin? Does that about sum it up or is there something else I'm missing?
Click to expand...
Click to collapse
Yep. You will need to extract the payload.bin file in which you will use the boot.img, then patch it with magisk, then flash the patched boot.img using fastboot. Then, you will need to use magiskhide to hide magisk itself and use the props spoof module to help with passing safetynet.
I want to say thank you for the help! I successfully installed Magisk and passed the SafetyNet checks! Everything seems to be working good. However, it seems my efforts might be wasted as Magisk is dropping support for hiding root access. This is unfortunate as I have a few job critical apps that will not work unless I hide them from root access in Magisk. Hopefully someone else will pick up the torch and continue development. It's a crime these big tech companies work so hard to prevent us from modifying hardware we own!
Hi, I flashed LineageOS 18.1 to my OnlePlus 8T (KB2003). The device is not rooted.
Since that, he device is no longer Play Protect certified and I am not able to install Netflix or use PayPal anymore.
Therefore I installed Magisk and MagiskHidePropsConf-v6.1.2 and followed the instructions above to change the fingerprint and hopefully hide, that the bootloader is unocked. But the device is still not certified (PayStore App > Settings > Info)
What have I done:
- extracted boot.img from LineageOS payload.bin
- boot.img was patched and fastboot flashed to my device (Patching_Images)
- 2 props added: ro.product.model: "Pixel 5", ro.product.manufacturer: "Google"
Did I forgot something?
But in general, why is it needed to change the fingerprint to Pixel 5? Should not work the default fingerprint of my OnePlus 8T as well?
BR Greg
gregattack said:
Hi, I flashed LineageOS 18.1 to my OnlePlus 8T (KB2003). The device is not rooted.
Since that, he device is no longer Play Protect certified and I am not able to install Netflix or use PayPal anymore.
Therefore I installed Magisk and MagiskHidePropsConf-v6.1.2 and followed the instructions above to change the fingerprint and hopefully hide, that the bootloader is unocked. But the device is still not certified (PayStore App > Settings > Info)
What have I done:
- extracted boot.img from LineageOS payload.bin
- boot.img was patched and fastboot flashed to my device (Patching_Images)
- 2 props added: ro.product.model: "Pixel 5", ro.product.manufacturer: "Google"
Did I forgot something?
But in general, why is it needed to change the fingerprint to Pixel 5? Should not work the default fingerprint of my OnePlus 8T as well?
BR Greg
Click to expand...
Click to collapse
All I needed to do to get Play Protect certified was to change my fingerprint to the OP8T KB2003 fingerprint included in MagiskHide Props Config. No other model spoofing needed.
I am still stuck on Widevine L3, however. Still haven't figured that one out, and may be unrelated.
Did you install and use the Universal SafetyNet Fix module?
If I set the kb2003 OP 8T (EU) fingerprint, it seemed not to work. But I will try again.
Do I need to clear some caches eg: play store, after changing the fingerprint or something else?
cpkelley94 said:
All I needed to do to get Play Protect certified was to change my fingerprint to the OP8T KB2003 fingerprint included in MagiskHide Props Config. No other model spoofing needed.
I am still stuck on Widevine L3, however. Still haven't figured that one out, and may be unrelated.
Click to expand...
Click to collapse
finally I installed Universal SafetyNet Fix and switched to the kb2003 fingerprint and reset all other modification like custom props for the pixel phone. Now it's working. No idea why it fails in previous approach
Strange, on my device. Not on lineage though - I pass safetynet without help from any modules. No props or even USF module. Rooted and bootloader unlocked.
Op8t 5g tmobile.
ykjae said:
Strange, on my device. Not on lineage though - I pass safetynet without help from any modules. No props or even USF module. Rooted and bootloader unlocked.
Op8t 5g tmobile.
Click to expand...
Click to collapse
which image are you using?
I read, that some images like https://evolution-x.org/ pass safetynet out of the box but I did'nt test this.
Finally the unlocked bootloader is the problem.
I'm trying to bypass the SafetyNet chore by using MagiskHide and tools like this one.
I have yet to have success.
I have read lots of information about the topic, but most seems irrelevant and obsolete.
I use a custom ROM with Root enabled.
Can anyone please point me in the right direction of solving this issue?
Thank you.
It would help if you stated which ROM or Android version you are on...
pnin said:
It would help if you stated which ROM or Android version you are on...
Click to expand...
Click to collapse
Android 11, Octavi OS.
I see... can't really help, no experience.
Magisk, Universal SafetyNetFix and MagiskHideProps
robogo1982 said:
Magisk, Universal SafetyNetFix and MagiskHideProps
Click to expand...
Click to collapse
Of course, I have that installed and working according to tutorials, already...
Still, not working.
"Fixed" it by appending `LEGACY_MIFARE_READER=1` to `/system/vendor/etc/libnfc-nci.conf`.
However, this breaks my SIM service. Not sure, how those features are related, but here we are.
Another reboot seems to have fixed the SIM service issue.
Is this really it? Is the NFC problem really fixed after such a long time?
I cannot believe it.
I will test this for some time, just to be sure....
Did you force basic attestation in props?
I'm using ArrowOS 12 (ArrowOS 11 before that) and never had problems with SafetyNet.
Using latest Magisk, Zygisk and DenyList enabled. As for modules, I use GPay SQLite Fix and Universal SafetyNet fix. No other fixes or modules were necessary
if it's for banking apps, just check "Google services" on DenyList (first of all click the dots on right upper corner and check system apps). I was fighting that some time ago.
there's no need to install modules or do anything else, just check all apps U need on DenyList but the main app to deny is still "Google Services"
xSokol said:
if it's for banking apps, just check "Google services" on DenyList (first of all click the dots on right upper corner and check system apps). I was fighting that some time ago.
Click to expand...
Click to collapse
Enabled DenyList, checked Google Play Services and it stays checked. Checking Google Services Framework gets reverted each time I visit DenyList. There is no "Google services".
I found `*.gservices` as a sub-category of Google Services Framework. Disabled. Rebooted several times, after trying out multiple possibilities, but none did work. One time, even basic attestation was broken, which needed another reboot to fix.
no, sorry for my rush, it was about Google Play Services. I have never "denied" Google Services Framework.
what I would do is uninstall modules like "safetynet fix" and reboot to twrp, there's a fix for zygisk, install that one.
then reboot to system, clear all the data of an disobedient app, then go to Magisk DenyList and look for the app, check all services and search for Google Play Services again (I have to check it aftet every reboot somehow).
I just have had similar issue an hour ago with Revolut app because I crashed my system and had to dirty flash what swiped Magisk.
just be patient, it's not hard or complicated work
xSokol said:
there's a fix for zygisk, install that one.
Click to expand...
Click to collapse
Which one? Where? How?
xSokol said:
clear all the data of an disobedient app, then go to Magisk DenyList and look for the app, check all services
Click to expand...
Click to collapse
Check the app or what services? What exactly?
ok, then..
if You go in TWRP to "advanced" and then to "magisk" (sorry if the name isn't correct, I don't focus on names of options) and there are options like "install magisk 24..." or "uninstall magisk 24...", under that there are fixes, so You should find it, it's under "SafetyNet Fix". You need Zygisk, so get fix for Zygisk.
I was about the app that's not working, if You click on the bar with the name it will show its services. in standard Magisk denies only the main service of an app, but some apps require checking all of them.
hello @Aki-to , did U manage?
xSokol said:
hello @Aki-to , did U manage?
Click to expand...
Click to collapse
I did not dare to go into TWRP, because I am not absolutely sure if data or storage encryption works perfectly fine with TWRP on Android 11. I don't want to boot into TWRP and have everything encrypted and therefore unusable.
I did so many flashes and some of them had this problem, but I cannot remember if it was because of a failed flash or because it actually did not work.
I also do not want to remove encryption in Android Security Settings every single time I visit TWRP.
Posts like the following also sound very concerning.
[FIXED] How to remove data encryption in TWRP
Users of TWRP 3.1 on Doogee Mix (including myself) faced the mammoth problem of an encrypted storage after unlocking the bootloader and flashing the custom recovery. This problem is not peculiar to the Doogee Mix, any other device with TWRP 3.1+...
forum.xda-developers.com
there's no need to remove encryption, nothing abiut that.
I just have changed MIUI to 13 today, didn't change anything on TWRP, just installed Magisk from TWRP and checked all the bank apps, GPay and Google Play Services
Aki-to said:
"Fixed" it by appending `LEGACY_MIFARE_READER=1` to `/system/vendor/etc/libnfc-nci.conf`.
However, this breaks my SIM service. Not sure, how those features are related, but here we are.
Click to expand...
Click to collapse
Hi, could you share your Magisk module?
Haobin said:
Hi, could you share your Magisk module?
Click to expand...
Click to collapse
Sure, wanted to do that, anyway, but forgot about it.
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do:
- Update Magisk to 25.2, Update magisk app to 25.2 as well
- Rename Magisk app if you havent already
- [ OPTIONAL ] Add all google apps on deny list (good practice in case google wants to detect root throught their other apps)
- install these modules: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf and https://github.com/kdrag0n/safetynet-fix
- then:
step 1.) Download any terminal (I use termux)
step 2.) type SU
step 3.) type props
step 4.) edit device fingerprint
step 5.) follow the onscreen promt
step 6.) once successfully changed, reboot device
optional (i didnt have to but you can try) reset google play, play services and google wallet appdata.
step 7.) enjoy working google wallet.
- Reboot
NOTE: Remeber to clear google wallet just in case.
ANOTHER NOTE: If your device is not on this list: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/common/prints.sh
then you'll have to manually obtain an old fingerprint for your device, its all on here how to do:
MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
Enjoy.
EDIT: Alternatively try this:
https://github.com/Displax/safetynet-fix/releases/
it wont work for all from what I know but it was successful for some.
I only had to update magisk then add Wallet to the deny list.... Haven't tested an actual payment yet, but it stopped complaining about root when I open it.
I probably already had some of those modules installed from before. Some of the names look familiar.
Tried it at McDonald's... Didn't work. I guess the app stops complaining after a few goes of starting it up... Need to check in the "contactless setup" part of the Wallet app to be sure. Has a warning there if your device is "unsafe".
I'll try the full list of steps above tonight and confirm tomorrow if I can pay with it.
ahhh, it was not only with me... going to install to see if it passes...
None of the above works. If you try to pay contactless it will fail. If you try to add card it will fail also. I think that the new google wallet can detect if bootloader is unlocked. I don't see any workaround on this.
covar said:
None of the above works. If you try to pay contactless it will fail. If you try to add card it will fail also. I think that the new google wallet can detect if bootloader is unlocked. I don't see any workaround on this.
Click to expand...
Click to collapse
Yeah I removed Magisk and I still failed. It seems bootloader related I think.
covar said:
None of the above works. If you try to pay contactless it will fail. If you try to add card it will fail also. I think that the new google wallet can detect if bootloader is unlocked. I don't see any workaround on this.
Click to expand...
Click to collapse
works fine for me, I added something you should try as well in case it didnt work for you.
Danishblunt said:
works fine for me, I added something you should try as well in case it didnt work for you.
Click to expand...
Click to collapse
Still nothing. Have you try to make payment????
covar said:
Still nothing. Have you try to make payment????
Click to expand...
Click to collapse
I made 4 payments after the fix, latest being 12 minutes prior to this reply. it works fine.
I suggest starting from my post 1point by point. If it still doesnt work then you may have an app that somehow triggers the root detection that I don't have on my phone.
You should probably mention that picking correct CTS fingerprint is crucial. Sometimes its one version down for your device, but other times you have to use entirely different (but probably related somehow?) device FP, either because prior version doesn't exist, or Google simply doesn't accept it. The Google Pay thread has a scattered reports of working combos somebody should probably make a nicer list of.
I think some steps are not necessary. Like hiding all Google apps and SQ Lite
Also, momo-hider is depreciated. Use shamiko.
Lastly, I just installed magisk hide props (and configured it) and now it works.
Thanks its work✓ !! Is it permanent? Or someday its gonna pop out because some updates?
Magisk user
Paulo_1307_ said:
I think some steps are not necessary. Like hiding all Google apps and SQ Lite
Also, momo-hider is depreciated. Use shamiko.
Lastly, I just installed magisk hide props (and configured it) and now it works.
Click to expand...
Click to collapse
You are correct. The only thing to do is to configure props. I personally change the fingerprint and now works fine.
Paulo_1307_ said:
I think some steps are not necessary. Like hiding all Google apps and SQ Lite
Also, momo-hider is depreciated. Use shamiko.
Lastly, I just installed magisk hide props (and configured it) and now it works.
Click to expand...
Click to collapse
You're right, just listed old modules i gathered over time just in case without testing if they are needed anymore. Tested if they were needed and indeed, they arent.
Hiding the google apps is a good idea regardless if its needed or not.
Fixed the original post to reflect the changes.
Danishblunt said:
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do:
- Update Magisk to 25.2, Update magisk app to 25.2 as well
- Rename Magisk app if you havent already
- [ OPTIONAL ] Add all google apps on deny list (good practice in case google wants to detect root throught their other apps)
- install these modules: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf and https://github.com/kdrag0n/safetynet-fix
- then:
step 1.) Download any terminal (I use termux)
step 2.) type SU
step 3.) type props
step 4.) edit device fingerprint
step 5.) follow the onscreen promt
step 6.) once successfully changed, reboot device
optional (i didnt have to but you can try) reset google play, play services and google wallet appdata.
step 7.) enjoy working google wallet.
- Reboot
NOTE: Remeber to clear google wallet just in case.
ANOTHER NOTE: If your device is not on this list: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/common/prints.sh
then you'll have to manually obtain an old fingerprint for your device, its all on here how to do:
MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
Enjoy.
Click to expand...
Click to collapse
hi may I ask what does step 5 mean? Thanks!
darkhunter9 said:
hi may I ask what does step 5 mean? Thanks!
Click to expand...
Click to collapse
baisically just means follow instructions on your screen.
Paulo_1307_ said:
I think some steps are not necessary. Like hiding all Google apps and SQ Lite
Also, momo-hider is depreciated. Use shamiko.
Lastly, I just installed magisk hide props (and configured it) and now it works.
Click to expand...
Click to collapse
Can confirm this works
I had both GPay and Wallet installed on my Pixel 5; yesterday I got the "security requirements" notification.
I've now removed both apps. When I tap on the GPay tile in Quick Settings, it says "Hold to reader", but when I tap Show All, it says "Not set up". I'll test it later today.
Does anyone know how to clear cache for embedded GPay?
V0latyle said:
I had both GPay and Wallet installed on my Pixel 5; yesterday I got the "security requirements" notification.
I've now removed both apps. When I tap on the GPay tile in Quick Settings, it says "Hold to reader", but when I tap Show All, it says "Not set up". I'll test it later today.
Does anyone know how to clear cache for embedded GPay?
Click to expand...
Click to collapse
It will show an error when you try to do a transaction if you havent done the above. Minr also showed that it was reafy but when trying to pay it would throw error.
Danishblunt said:
It will show an error when you try to do a transaction if you havent done the above. Minr also showed that it was reafy but when trying to pay it would throw error.
Click to expand...
Click to collapse
I just went to Dollar General and successfully used tap to pay. I do not have either of the discrete apps installed, just embedded GPay.
Danishblunt said:
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do:
- Update Magisk to 25.2, Update magisk app to 25.2 as well
- Rename Magisk app if you havent already
- [ OPTIONAL ] Add all google apps on deny list (good practice in case google wants to detect root throught their other apps)
- install these modules: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf and https://github.com/kdrag0n/safetynet-fix
- then:
step 1.) Download any terminal (I use termux)
step 2.) type SU
step 3.) type props
step 4.) edit device fingerprint
step 5.) follow the onscreen promt
step 6.) once successfully changed, reboot device
optional (i didnt have to but you can try) reset google play, play services and google wallet appdata.
step 7.) enjoy working google wallet.
- Reboot
NOTE: Remeber to clear google wallet just in case.
ANOTHER NOTE: If your device is not on this list: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/common/prints.sh
then you'll have to manually obtain an old fingerprint for your device, its all on here how to do:
MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
Enjoy.
Click to expand...
Click to collapse
Even tho Xiaomi Mi 11 Lite 5g (European version) is not on either list, I got Google Wallet to play nicely (ie work! ) using this guide. In effect the Xiaomi Mi 11 Lite Indonesia Xiaomi:M2101K9AG must have similar coding to Xiaomi M2102K9G. I am now on 13.0.6 SKIEUXM MIUI version. I was worried in the termux app re warnings about ensuring device fingerprint is compatible etc, but when I got the sae warning in adb shell command within minimal adb & fastboot command, I decided to see what happens and it all worked for me. Have carried 2 transactions within Google wallet over yesterday & today with complete success. My device was already certified within Play protect part of Google Play Store.
So I have rooted phone with Magisk 25.2 version, zygisk and deny list set up ; magisk hidden (Hide) then froze Magisk Hide within SD Maid so my fully rooted phone runs Ad Away, no ads & all my banking apps eg Santander & Halifax work fine, so root is hidden from them. Given up trying to get Chase banking app tho