Related
I have just made successful transaction via Android Pay on my rooted & Xposed Samsung Galaxy S7.
I'm curious to know what is the actual reason for working as I was under impression that Android Pay is guarded by SafetyNet.
My Samsung Galaxy S7 runs Android 7.0 (G930FXXU1DQIC - patch level 8/2017), good old CF-Auto-Root and latest Xposed framework (no systemless root or Magisk). I started using S7 year and half ago and I am rooted from the very beginning. CF-Auto-Root disabled device internal memory encryption (after the last reinstallation). I only use two my own Xposed modules and YouTube AdAway. I block ads via AdAway. (I also disable any system/provisioning updates, security checks, unused system apps - but without using of any 3rd party software or hacks)
As I was thinking Android Pay won't work on my S7, I setup payment card on Samsung Galaxy S5 which I have reinstalled (from LineageOS) to the latest stock ROM (without rooting). Then I gave try my S7 and confirmed the same card for use on that device as well.
First I tried reading card info using "Credit Card Reader NFS (EMV)" which worked fine on both phones in either way so I tried using S7 today in a shop (two days after setup)... and it just worked.
Android Pay version: 1.36.177845727
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Interesting [emoji848][emoji848]
Could you please share your android pay apk? I would like to try
But I have magisk and a lot of modules with xposed, anyway I'll try
Enviado desde mi SM-G930F mediante Tapatalk
The version (name/code) I use is the same as here: https://www.apkmirror.com/apk/googl...id-pay-1-36-177845727-4-android-apk-download/
Before running any SafetyNet checks on my working S7, I will try replicating the setup on rooted S5 first.
EDIT (day later):
After rooting S5, Android Pay reports the "Android Pay can't be used on this device" message. However I used older image for rooting (as I had some issues with latest but will try again). It further confirms that there's some quirk in my setup/configuration that makes it work on S7.
S5 gave me that error shortly after trying reading card via "Credit Card Reader" app - so it seems like a perfect verification without the need to use a real terminal in a shop.
I don't have much time lately but I will be digging deeper...
EDIT (18th January):
Made second payment via Android Pay, this time above the limit requiring unlocking. It still works.
Still no luck with S5 - all SafetyNet checks fail. I'm too scared to actually run any SafetyNet checks on S7 but I guess I could snoop the network and compare the local SafetyNet logs/dbs inside GMS...
moneytoo said:
The version (name/code) I use is the same as here: https://www.apkmirror.com/apk/googl...id-pay-1-36-177845727-4-android-apk-download/
Before running any SafetyNet checks on my working S7, I will try replicating the setup on rooted S5 first.
EDIT (day later):
After rooting S5, Android Pay reports the "Android Pay can't be used on this device" message. However I used older image for rooting (as I had some issues with latest but will try again). It further confirms that there's some quirk in my setup/configuration that makes it work on S7.
S5 gave me that error shortly after trying reading card via "Credit Card Reader" app - so it seems like a perfect verification without the need to use a real terminal in a shop.
I don't have much time lately but I will be digging deeper...
EDIT (18th January):
Made second payment via Android Pay, this time above the limit requiring unlocking. It still works.
Still no luck with S5 - all SafetyNet checks fail. I'm too scared to actually run any SafetyNet checks on S7 but I guess I could snoop the network and compare the local SafetyNet logs/dbs inside GMS...
Click to expand...
Click to collapse
Just curious, is there any progress on this? I'm using latest Magisk with Xposed. One of my local payment app refused to work after a recent Google update. I think Google has strengthened the SafetyNet checking again. I wonder if your S7 is still working after the recent update.
@itandy
I've made over 10 payments, used S7 for setup Android Pay on Android Wear and it still works. I tried running SafetyNet checks and they said that attestation fails (both baseic integrity and cts profile match).
So far my thinking is that it's allowed by design. S7 features fingerprint reader which means (by CTS requirements) it also has embedded secure storage for signing keys (SE/TEE?). The S5 doesn't have that (their fingerprint reader was one of the firsts and didn't use system APIs) so it fall backs to unsecured software keystore implementation. I see that only S7 contains some actual data in table "StorageKey" (in Android Pay db inside GMS).
I tried spoofing "KeyInfo.isInsideSecureHardware()" but maybe I was too late as the device profile was already setup.
I've just realized I should be able to get another device (with fingerprint reader) for testing this theory so I will do that.
moneytoo said:
@itandy
I've made over 10 payments, used S7 for setup Android Pay on Android Wear and it still works. I tried running SafetyNet checks and they said that attestation fails (both baseic integrity and cts profile match).
So far my thinking is that it's allowed by design. S7 features fingerprint reader which means (by CTS requirements) it also has embedded secure storage for signing keys (SE/TEE?). The S5 doesn't have that (their fingerprint reader was one of the firsts and didn't use system APIs) so it fall backs to unsecured software keystore implementation. I see that only S7 contains some actual data in table "StorageKey" (in Android Pay db inside GMS).
I tried spoofing "KeyInfo.isInsideSecureHardware()" but maybe I was too late as the device profile was already setup.
I've just realized I should be able to get another device (with fingerprint reader) for testing this theory so I will do that.
Click to expand...
Click to collapse
Thanks for you response. But still it doesn't make sense to me. S7 is not the only device to have the requirements you mentioned. And specifically Xposed is one major target of SafetyNet. My device with Magisk passed everything without Xposed. But once Xposed is enabled, both ctsProfile and Basic Integrity fails, as expected.
I had the same situation S7 working android pay with root and xposed for the last year , until all of a sudden last week it stopped and now will only work if i disable xposed
is anyone's s7 still working with android pay ,root and xposed ?
or is it just mine that stopped last week ?
Stef
sjpage10 said:
I had the same situation S7 working android pay with root and xposed for the last year , until all of a sudden last week it stopped and now will only work if i disable xposed
is anyone's s7 still working with android pay ,root and xposed ?
or is it just mine that stopped last week ?
Stef
Click to expand...
Click to collapse
I'm not using S7. But my local payment app used to work with Magisk and Xposed until recently. I think a recent Google Play update strengthened the SafetyNet.
@sjpage10
The most recent payment I made with S7 was 9 days ago but that's cause I'm using watch now. I'm still able to read Android Pay card data from S7.
Android Pay version may not actually matter that much as the core for payments is in Google Play Services. I'm currently on version 11.9.75.
moneytoo said:
I have just made successful transaction via Android Pay on my rooted & Xposed Samsung Galaxy S7.
I'm curious to know what is the actual reason for working as I was under impression that Android Pay is guarded by SafetyNet.
Click to expand...
Click to collapse
sjpage10 said:
I had the same situation S7 working android pay with root and xposed for the last year , until all of a sudden last week it stopped and now will only work if i disable xposed
is anyone's s7 still working with android pay ,root and xposed ?
or is it just mine that stopped last week ?
Stef
Click to expand...
Click to collapse
I did a clean install of Superman ROM 2.8.0 by @Tkkg1994 (Android 7.1) + Magisk w/MagiskSU on my Galaxy S7 (SM-G930FD) back in December. With this combination, I was able to pass SafetyNet, and install Android Pay 1.36.177845727 using the Play Store app. I configured it and began using it without issue. I then installed Systemless Xposed, and even though SafetyNet would fail whenever Xposed is activated in Magisk Manager, Android Pay continued to work normally. Even with Xposed activated, the Play Store settings dialog would report "Certified" in the Device certification field. Nevertheless, apps that prohibit distribution to compromised devices (e.g., Netflix, which I don't have installed) would not show up in Play Store searches. Android Pay would still show up, presumably only because it was already installed on my device.
I have been using Android Pay nearly daily every evening at the supermarket across the street without issue until yesterday. During the day, I upgraded to Magisk 15.4 (from 15.3), Magisk Manager 5.6.0 (from 5.5.0), and Systemless Xposed 89.2 (from 89.1). Nothing appeared different; Android Pay continued to open normally. Note that I have NOT been offered (nor installed from any other source) any updates to Google Play Services in recent weeks; I am on 11.9.75. However, when presenting the device at the supermarket's payment terminal last night, I was greeted by a window featuring a red exclamation point in a circle, an image of my credit card, and the verbiage "You can no longer use Android Pay on this phone". There was a link to activate a feedback form, though I didn't submit feedback. When I backed out of the window, things otherwise seemed normal with respect to Android Pay: I was able to browse my various payment methods, explore the settings dialog, etc. I then disabled Xposed momentarily in Magisk Manager, and was once again able to pass SafetyNet. I haven't had the opportunity of try Android Pay again since this incident.
So, like most in this thread, I am trying to understand the relationship between Android Pay and SafetyNet, as well as any other device integrity checks it makes. Based on the experiences reported in this thread by @moneytoo, @sjpage10 and myself, it looks like Android Pay doesn't regularly check SafetyNet, though the Play Store does not offer it to you if your device is failing SafetyNet when you look for it. Obviously, that doesn't preclude sideloading it using an APK from APKMirror or another source.
So, I have a few questions:
It isn't clear to me why Android Pay suddenly stopped working last night. Is this a consequence of my updates, or did something change on the server side? It seems like it might be a bit more than a coincidence that both @sjpage10 and I experienced the same phenomenon within a short period of time.
Is there a convenient way to do complete end to end testing of Android Pay without actually making a charge? It sounds like @moneytoo has some method, but I am not clear what this is.
What does Android Pay actually check to determine if a device is allowed to use it, and when is this checked?
How can I find out the underlying cause of an Android Pay failure? I'll try logcat the next time I attempt to use Android Pay to make a purchase, but any hints on what to look for would be helpful.
Thanks.
@sjevtic
It stopped working for me as well.
So far on every device I tried, Android Pay works perfectly fine offline (for at least few days) but after a device reboot it requires internet connectivity for initialization.
The "Device certification" status in Play Store is cached and doesn't 100% correspond with the actual SafetyNet responses. Apps like Netflis doesn't show up when SafetyNet fails but there's no such protection turned on for Android Pay.
1) Seems like they disabled the responses on servers needed for initialization of Android Pay
2) As I already mentioned, install "Credit Card Reader NFC (EMV)" on second phone and try reading card with that. When this works, Android Pay also works.
3-4) That's the question. I still think it's possible to hack it so Android Pay will continue working on our phones. The key here is that it works offline. It may be a bit cumbersome though (automate rebooting to environment without Xposed to refill new payment tokens).
BTW: At least Android Pay still works on my Android Wear watch (connected to S7).
moneytoo said:
@sjevtic
It stopped working for me as well.
So far on every device I tried, Android Pay works perfectly fine offline (for at least few days) but after a device reboot it requires internet connectivity for initialization.
Click to expand...
Click to collapse
So Android Pay previously didn't need to be online to process payments? Are you suggesting that there was some form of pre-authorization, either for some period of time, dollar amount, or number of transactions for which it will work with no further attempts to connect to a server? And was SafetyNet only checked at the time of this pre-authorization? For what it is worth, I have been online every single time I attempted a transaction to date, so as of the moment I have no additional data to offer here.
The "Device certification" status in Play Store is cached and doesn't 100% correspond with the actual SafetyNet responses. Apps like Netflis doesn't show up when SafetyNet fails but there's no such protection turned on for Android Pay.
Click to expand...
Click to collapse
It doesn't make a lot of sense why the SafetyNet status displayed would be cached, yet a live value would be used to filter apps displayed by the Play store. Nonetheless, observations seem to support this.
1) Seems like they disabled the responses on servers needed for initialization of Android Pay
Click to expand...
Click to collapse
So are you suggesting that now Android Pay goes online for every transaction made, checking SafetyNet at each transaction as well?
2) As I already mentioned, install "Credit Card Reader NFC (EMV)" on second phone and try reading card with that. When this works, Android Pay also works.
Click to expand...
Click to collapse
Ah, ok, I found the app now. That said, it didn't seem to actually be able to read NFC cards, let alone my S7's Android Pay "card" on the HTC One M8 that happened to be sitting in my desk. Just to make sure the app was sane, I tried installing it on my S7 and was able to read my NFC-enabled transit card, but that doesn't help much for these experiments. I can find a different phone on Monday if needed.
Before you responded though, I found a vending machine in the office that accepts NFC payments, and for which I can just cancel the transaction after scanning. I did a couple simple tests with it:
Android Pay transaction with Xposed on (SafetyNet failing): "You can no longer use Android Pay on this phone"
Android Pay transaction with Xposed off (SafetyNet pass): Success/green check mark
Android Pay transaction with Xposed on (SafetyNet failing): "You can no longer use Android Pay on this phone"
In each of these scenarios, I was online. It seems like now SafetyNet has to be passing whenever Android Pay is used to make a transaction. It isn't yet clear whether the phone also has to be online.
I am out of the office today, but can try some other scenarios on Monday if needed (e.g., Android Pay while offline).
3-4) That's the question. I still think it's possible to hack it so Android Pay will continue working on our phones. The key here is that it works offline. It may be a bit cumbersome though (automate rebooting to environment without Xposed to refill new payment tokens).
BTW: At least Android Pay still works on my Android Wear watch (connected to S7).
Click to expand...
Click to collapse
An occasional boot with Xposed off for a "refill" would be manageable; requiring that Xposed be off at every boot during which an Android Pay transaction is made not so much.
Any suggestions? I am happy to help out in any way I can, though sadly I have no significant Android development experience at this point.
Quick update
Over the course of the weekend, I upgraded my phone to Superman ROM v2.9.0, and along the way, I spent some time (that is, more than a few minutes) with my phone booted up without Xposed running. I am not sure if this had any effect, but when I next tried Android Pay on Saturday and then again on Sunday, it worked. In both cases, Xposed was running and the phone was online.
Today, however, Android Pay failed again with the same message I reported earlier. So, that makes me wonder:
Is offline authentication caching working again?
Does the phone need to be booted up for an extended period in a SafetyNet-passing state (Xposed off) to refill the offline token cache?
Is there a way to examine the contents of the offline token cache, and determine the state of remaining tokens, if any?
Thanks.
moneytoo said:
@itandy
So far my thinking is that it's allowed by design. S7 features fingerprint reader which means (by CTS requirements) it also has embedded secure storage for signing keys (SE/TEE?). The S5 doesn't have that (their fingerprint reader was one of the firsts and didn't use system APIs) so it fall backs to unsecured software keystore implementation. I see that only S7 contains some actual data in table "StorageKey" (in Android Pay db inside GMS).
I tried spoofing "KeyInfo.isInsideSecureHardware()" but maybe I was too late as the device profile was already setup.
Click to expand...
Click to collapse
Indeed SE (oldschool sim toolkit), or TrustZone (TEE) is to blame. SafetyNet is consulted only if the pay is, well ... exposed.
I'd advise against releasing yet another safetynet bypass though, as those are promptly coopted by banking trojans and google is forced to update safetynet soon after (magisk didn't work for very long now, did it). Xposed is difficult beast to hide sort of by design.
isInsideSecureHardware
Click to expand...
Click to collapse
I suspect that when you do that, you tell the NFC payment stack that you now sign tokens inside TEE trustlet, but without having TEE...
Got my new P20Pro today - coming from a Mate 10 Pro. Love the phone and everything works great except the Samsung gear app and my Samsung Frontier S3 watch (AT&T LTE version). The app downloads and i can pair the watch and restore my watch settings but when i try to open Samsung pay the Samsung pay gear plug-in doesn't install and if i try to look at watch faces or apps, I get an error "this device does not support gear" - any idea how to fix/troublshoot this?
Hi, we are all in the same situation.
We have to wait for Samsung to update gear app
Look in this thread.
https://forum.xda-developers.com/gear-s3/themes/galaxy-apps-huawei-p20-t3774050
Thanks for pointing out that post - I hadn't thought to look in the p20 forums. I guess we'll have to wait for Samsung to update the Gear app. In the meantime, I was able to use appsharer to move the Samsung pay framework and Samsung pay gear plugin from my mate10 pro to the p20pro and install them without any problems (just after install, you need to clear cache/storage on both apps to reset them) so I have Samsung pay working fine on my gear d3 connected to the p20 pro -just missing ability to download new apps/watchfaces
TGUY25 said:
Thanks for pointing out that post - I hadn't thought to look in the p20 forums. I guess we'll have to wait for Samsung to update the Gear app. In the meantime, I was able to use appsharer to move the Samsung pay framework and Samsung pay gear plugin from my mate10 pro to the p20pro and install them without any problems (just after install, you need to clear cache/storage on both apps to reset them) so I have Samsung pay working fine on my gear d3 connected to the p20 pro -just missing ability to download new apps/watchfaces
Click to expand...
Click to collapse
Cool, happy for you if everything work well except watchface, so if you still have your mate 10 pro can you share the mms.apk for messaging please
I tried to find it and couldn't. No messaging app appears in the list - i didn't root my phone so don't know where/how to find individual apk's. I wanted to move that one too as the p20 doesn't come with a stock messaging app (so i'm using textra)
Download Pay Plug in from the net and install and it will work.
Skickat från min EML-L29 via Tapatalk
Hi,
On your Samsung Gear S3 Frontier (WiFi only version), if Samsung Pay is not working after pairing with Huawei P20 Pro due to no Samsung Pay Plugin available in the app, here is how I managed to make it work.
If you already reset and paired your watch, you can skip to Step 4.
1. Hard reset your Gear S3 (Turn off, press and hold Power button until you see the logo don't release the Power button, seconds later you will see the logo and a blue colored 'rebooting', once you see it repeatedly press on Power button until you see the bios-like like menu, by pressing the Power button you can browse the menu, stop at 'recovery' and keep pressing the Power button then quickly press the Home button, your watch will restart to its factory settings).
2. Download and install Samsung Gear app on your phone, get it from Play Store. Once you open the app, it may ask to install two more required apps, Gear S Plugin and Samsung Accessory Service.
3. Pair your watch and phone. So far nothing fancy.
4. Download and install Samsung Pay using your phone from apkmirror (a security question will pop up asking to allow to install an app from a third party, just accept).
5. On your watch, press and hold the Home button to start Samsung Pay, this will ask you to continue setup on your phone.
6. On your phone, Samsung Pay will start and may state an updated version of Samsung Pay is available for you watch version, accept and it finish updating on your watch.
7. Start Samsung Pay as in Step 5. At this point, the app on your phone asks to set a passcode or pin on your watch for security.
8. You are all set now and can add your credit/debit cards as usual.
This is my first post and thank you for your support and for an amazing XDA app.
- Oguz
P20 pro & S3
Hello,
This thread is a few months old now, does anyone know if there has been an update Samsung’s end? Just taken delivery of P20 pro and want the S3 watch mainly for its offline Spotify feature. Don’t want to pay £250 if it won’t work. Not interested in android pay (as my bank isn’t supported) but do want texts and WhatsApp to work. Any advice would be appreciated.
I have had the p20 pro since shortly after release and have had no issues with it's relationship with my S3 (non lte), it works seemlessly.
I wasn't aware of any issues, I have only just stumbled across this thread.
Sent from my [device_name] using XDA-Developers Legacy app
S3 & P20 Pro
Brilliant, thank you. I'll go and buy one then
So I finally received my Chinese version Mate 20 Pro Emerald variant and I spent the last 24 hours setting it up, now it's finally getting into a more or less stock android feeling. I decided to write a post because man, I've never spent so much effort just trying to setup a new phone.
Ordering
I ordered the phone from Huawei T Mall store on Nov. 11th. I paid about 1250 CAD through Alipay for the phone and ~ 600 RMB having my friend sending it to me via DHL. I also had to pay some import tax getting it into Canada but it's just bad luck, plus the tax really depends on how much you declare the value to be.
First Impression
I had a Oneplus 5, I like the cleanness of its ROM, it's close to stock android and I was using the Rootless Pixel 2 Launcher which makes it essentially a stock Android device. The Mate 20 Pro is a bit heavier than the Oneplus 5 and it's just slightly bigger.
I started with applying the tempered glass screen protectors I bought also from Taobao when I ordered the phone. Sadly I can't seem to get it in the right place, and it's greatly affecting the screen responsiveness and accuracy. I ended up throwing them away.
Turning it on, and I'm already having issue with the initial setup process. First of all, I was asked to create a Huawei ID. But guess what -- I live in Canada but Canada isn't an available option in the region list, somehow US is. I mean, this phone is not even available in US, why would you provide that as an option but not Canada?
I went ahead choosing US as the region. It asked for phone verification, that worked for me because US and Canada share the same country code.
After that, I uninstall a bunch of pre-installed apps -- they are mostly popular apps in China, plus a few useless utilities made by Huawei. I uninstall about 25 apps during this process.
Then I tried to restore all my apps from the old phone, first step would be getting Google Play Service working. Surprisingly Google Play Service is pre-installed. but I wasn't able to update it through the Huawei App Store, because US Huawei ID apparently is not supported. In fact I can't use any of the pre-installed Huawei apps, they are all blocked. So I deleted my account and created a Chinese one instead.
I was able to access the app store and update Google Play Service, along with Play Store. Google backup apparently didn't work. I ended up using the Huawei "Phone Clone" app to transfer all my stuff to this phone. It does the job pretty well.
Getting third party launcher working on Chinese ROM (If you have a global version then this may not apply to you)
Spent sometime getting all the apps logged in and tweaking settings, I started to look into replacing the stock launcher. But then you can't change launcher on the Chinese rom, so I did some research and here is what I did:
1. Install a third party launcher. I chose Nova Launcher here. Never used it before but Rootless Launcher kept crashing and for Rootless Pixel 2 Launcher, there is an annoying security alert saying "Google is using microphone" that kept popping up.
1. Enable developer mode
2. Enable USB Debug
3. Connect the phone to PC
4. Access ADB shell
5. uninstall stock launch: pm uninstall -k --user 0 com.huawei.android.launcher
6. Reboot
A few notes on using this 3rd party launcher hack:
* I also installed the Nova companion app to have Google Feed panel access.
* You need to allow Nova companion to auto-launch in Settings -> Apps -> App Launch, otherwise rebooting the phone will make Google Feed panel disappear.
* If you select gesture navigation in system setting, swiping up from bottom may not work.
Getting Google Assistant to work
The phone has the Huawei voice assistant by default, and changing the default Assistant app to Google doesn't work. The shortcut still only bring up the Huawei voice assistant. The fix is to uninstall the app using the same process above. The package name is com.huawei.vassistant. After reboot, I was able to access Google Assistant using the home button (I still prefer three key navigation). "OK Google" doesn't work on Home screen though.
Make sure push notifications are working
I also noticed I don't receive push notifications most of the time. For example, I have Duo Mobile which is used as an authenticator at work. Having the screen on, I didn't receive the push notification. I had to launch the app manually to see the authentication request. Here is a workaround:
1. Settings -> Apps -> App Launch
2. Find the app you wish to receive push notification
3. Disable auto manage, it will ask you how you want to manage manually, choose Auto-launch and Run in Background at least
Known Issues/Todo list
Here are some of the things that I'm having issue with but haven't figured out a solution yet. Please let me know if you know a solution to any of them:
1. Google Pay Contactless does not work. This is almost a deal breaker. From what I've read, it seems to be just Chinese version doesn't work.
1. LastPass accessibility setting gets reverted to off randomly. This seems to related to when I close all apps using the trashcan button on recent apps screen.
2. Default Assistant app setting mysteriously gets reset to None. Still don't understand why.
3. Text in the notification just look so bad. Also not sure how to tweak that.
4. The security alert for app using microphone keeps popping up in Google Assist and Google Feed. I'm not sure how I should feel about that...
Things I like about this device
1. Chinese version supported dual SIM. I believe the global version does not.
2. photos in low lights are awesome.
3. charging is super fast! I also got the wireless charging thing.
4. I'm happy with its battery performance so far.
5. It's a faster device overall. The games I play run smoother on this phone comparing to Oneplus 5. I understand OP5 is an older phone but that's the only reference point I got.
That's what I had so far. I'm also keeping an eye on the progress of FunkyHuawei Mate 20 Pro support -- I'm looking forward to flash the global version ROM hoping it has better google integration and less chinese-oriented useless "features".
Hope it helps!
Thanks for sharing
Does the device show as being certified in the Google Play Store? If not, this would probably explain why contactless via GP doesn't work
Minotaur said:
Does the device show as being certified in the Google Play Store? If not, this would probably explain why contactless via GP doesn't work
Click to expand...
Click to collapse
Yes it shows as certified in playstore.
henexekrar said:
Yes it shows as certified in playstore.
Click to expand...
Click to collapse
Hmmm interesting... is there an error message or such that might indicate why GPay doesn't work?
Minotaur said:
Hmmm interesting... is there an error message or such that might indicate why GPay doesn't work?
Click to expand...
Click to collapse
when attempting to enable contactless, the following messages appear in order:
contacting your bank...
your bank is verifying your card...
added feature cannot be setup. contact your bank to resolve this issue.
I called the bank and they said they didn't get the request so they don't know what error it is.
I contacted Google and haven't got a response.
Did you already have the card in your GPay wallet, and were re-verifying, or did you add it from scratch? Guessing it may not make a difference though.
Minotaur said:
Did you already have the card in your GPay wallet, and were re-verifying, or did you add it from scratch? Guessing it may not make a difference though.
Click to expand...
Click to collapse
I had the card in the wallet for a long time. Used it with my old phone without issue.
Does it support Band 66? Thanks
Sent from my iPhone using Tapatalk
I was in China last week and almost bought the Mate 20 Pro. After reading many reviews I decided to not buy the Chinese Version and pay a little more to get the Google version from Hong Kong
Any updates?
Were you able to find any way to get LastPass working properly?
Accessibility features keep resetting for me right away.
Hi, have your version finger-id? I bought a mate 20 pro red in aliexpress but i can't find the finger-id......
John_nl_74 said:
Hi, have your version finger-id? I bought a mate 20 pro red in aliexpress but i can't find the finger-id......
Click to expand...
Click to collapse
The LYA-AL00 with 6 GM RAM and 128 GB storage has no fingerprint sensor. It only uses face, pattern, and password unlock.
I got fed up by the blatant digital racism i face of not being able to "purchase" something because it is not available on my country (or the one i reside), so i installed this module to give it a try. I do remember using a very similar module for Xposed, but i couldnt risk the compatibility with a two year old module.
According to the guide at the dev's github of the module, Google Play Services should work out of the box as it is included in the initial list of the module.
Since i needed the same solution for a few things, mainly Galaxy Store, Galaxy Themes and Good Lock, i made sure i added them. I also discovered that Play Services is obviously already in, but Play Store wasnt, so i added that one too.
My results are mixed. Galaxy Store and Good Lock work with the spoofed region/carrier, and i get the content of the region i wanted, or should i say, i got rid of the region i didnt want to.
Play Services/Store, and Galaxy Themes on the other hand dont change at all (I even made sure to include the system app Samsung Themes just for the sake of testing).
I can obviously confirm that i have a running Magisk environment, with Riru Core installed as well. I can also confirm that the Module is activated and working.
I followed the dev's guide to:
Code:
Add/enable package
touch /data/misc/riru/modules/location_report_enabler/packages/com.google.android.gms
touch /data/misc/riru/modules/location_report_enabler/packages/com.android.vending
touch /data/misc/riru/modules/location_report_enabler/packages/com.samsung.android.goodlock
touch /data/misc/riru/modules/location_report_enabler/packages/com.samsung.android.themestore
touch /data/misc/riru/modules/location_report_enabler/packages/com.samsung.android.themecenter
Return value
echo -n 310030 > /data/misc/riru/modules/location_report_enabler/gsm.sim.operator.numeric
echo -n us > /data/misc/riru/modules/location_report_enabler/gsm.sim.operator.iso-country
PS, device is a Note 8 Exynos, and all the above apps are of the latest version.
Can anyone help me out on this?
I got a rooted (including eDxposed) Galaxy Note 10 Plus (N975F) and planning to buy the GW3 from the USA.
So far I am able to make the phone pass safetynet, work with Gpay. Samsung Health works thanks to the modified apk from xda.
Samsung pay doesn't work on the phone.
As my phones is rooted - Will I be able to use Samsung Pay on the watch? What about ECG, BP and other fitness measurements?
P.S. To the mods - I am not sure if this is the right forum for this question. I wasn't able to find any other GW3 Q&A forum. Please kindly move it to the right forum if this is not it. Thanks.
I have also a rooted phone and wonder if Samsung Pay, ECG, BP and other fitness measurements can be used or not with a rooted phone
I have the same problem, any solution? I was able to have the health monitor app in the watch, but I can't use it as the phone app says my galaxy is rooted.
This may be slightly irrelevant to you, but I'll share my experience. I have the Galaxy Watch 3 paired to a OnePlus 7 Pro, rooted with Magisk, passing safetyNet.
ECG is not working for me (not available in my region).
Samsung Pay is not working for me. I tested with friends' Samsung phones and they don't have Samsung Pay either (therefore not available in my region so I can't test).
I've read on the forums that ECG is not working with rooted Samsung phones. Rooting a Samsung (or unlocking the bootloader, generally) trips KNOX. If you have KNOX tripped, people reported ECG not working and Samsung Pay getting disabled as well. This happened in THE UNITED STATES where ECG and Samsung Pay are usually working.
Don't take my word for it though, read it for yourself
TermoZour said:
This may be slightly irrelevant to you, but I'll share my experience. I have the Galaxy Watch 3 paired to a OnePlus 7 Pro, rooted with Magisk, passing safetyNet.
ECG is not working for me (not available in my region).
Samsung Pay is not working for me. I tested with friends' Samsung phones and they don't have Samsung Pay either (therefore not available in my region so I can't test).
I've read on the forums that ECG is not working with rooted Samsung phones. Rooting a Samsung (or unlocking the bootloader, generally) trips KNOX. If you have KNOX tripped, people reported ECG not working and Samsung Pay getting disabled as well. This happened in THE UNITED STATES where ECG and Samsung Pay are usually working.
Don't take my word for it though, read it for yourself
Click to expand...
Click to collapse
I have one plus 7 pro with magisk and galaxy watch 3 too... I can use galaxy watch 3 as well, no problem. but when I try to use samsung health monıtor app (installed as apk seperately) it says ''samsung healt monıtor does not work with rooted phone''. safety net passed, magisk hide is on and magisk manager packed with different name. no luck
If you have knox tripped phone:
1) rooted :
- samsung pay (watch) not working
- shealth working (including sync!!!) when ro.config.tima fixed using magisk and magisk configbuild module
- samsung health monitor not working
- btw gpay working using sqlfix magisk module
2) unrooted/official/relocked bootloader:
- samsung pay (watch) working
- shealth working partialy (no sync), to use latest version find xpirt patched version, install it, open, agree to terms...then download latest apk on apkpure, install SAI from google store, settings -> sign apks.. install/update using latest apk using SAI.. now you have latest shealth with no online sync working (so forget 3rd party integrations.. google fit, xiomi scale...)
-health monitor working, but doesnt sync with shealth
Search xda for details if confused..
doclucas said:
I got a rooted (including eDxposed) Galaxy Note 10 Plus (N975F) and planning to buy the GW3 from the USA.
So far I am able to make the phone pass safetynet, work with Gpay. Samsung Health works thanks to the modified apk from xda.
Samsung pay doesn't work on the phone.
As my phones is rooted - Will I be able to use Samsung Pay on the watch? What about ECG, BP and other fitness measurements?
P.S. To the mods - I am not sure if this is the right forum for this question. I wasn't able to find any other GW3 Q&A forum. Please kindly move it to the right forum if this is not it. Thanks.
Click to expand...
Click to collapse
Samsung pay watch depends on samsung pay on phone, so if the phone isn't working, you can't use it...
S Health works fine since it's tima in build.prop set from 1 to 0...
However, the BP and ECG in Samsung health monitor, you can grab my modified apk and it will work, the app is guarded against root, not just tima in build.prop, but root apps, busybox, xposed and su commands...
Hope that helps...
Samsung Galaxy Note 20 Ultra Rooted with Galaxy Watch 3...
@Dante63
Thank you.
I already have the watch.
Samsung pay actually works just fine through the watch, although the Spay on the phone doesn't work due to tripped knox.
I tried your modified SHM on the Samsung phone, but it seems to not only check for root, but on Samsung phone it also checks for Knox and then exits with the error that the phone has been modified.
Is there anything you can do to fix it so that it will also skip knox check?
Thanks again
doclucas said:
@Dante63
Thank you.
I already have the watch.
Samsung pay actually works just fine through the watch, although the Spay on the phone doesn't work due to tripped knox.
I tried your modified SHM on the Samsung phone, but it seems to not only check for root, but on Samsung phone it also checks for Knox and then exits with the error that the phone has been modified.
Is there anything you can do to fix it so that it will also skip knox check?
Thanks again
Click to expand...
Click to collapse
SPay works?
EDIT: Yes it does, good catch... thanks for the info...
As for SHM, then i might have not seen tima and it actually checks build.prop... did you change your build.prop, set tima from 1 to 0 and reboot...? Does your Samsung Health work..?
Yes, I changed build.prop and SH works, but SHM doesn't. Can you fix this?
doclucas said:
Yes, I changed build.prop and SH works, but SHM doesn't. Can you fix this?
Click to expand...
Click to collapse
Just to be sure, you grabbed the files from my google drive...?
If you grabbed the Carabana Mod from androidfilehost, that has root detection...
OK, what's the link and which file should I grab?
@Dante63
Just wanted to thank you for modifying the file and removing the root detection.
I downloaded it from your drive and it works perfectly!
[RESTRICTIONS-REMOVED] Samsung Health Monitor - TIZEN - 1.1.3.002 - Root, Age, Country & Device Restriction Removed - 23rd May 2023
Hello Everyone, I hope you all are fine... ~~~ TIZEN WATCHES ONLY ~~~ ~~~ FEATURES, BUGS & FUTURE WORKS~~~ FEATURES: Works on Active2 and Watch3 (as mentioned, Samsung Tizen Watches), Multilanguage, no root detection, no country restriction...
forum.xda-developers.com
doclucas said:
@Dante63
Just wanted to thank you for modifying the file and removing the root detection.
I downloaded it from your drive and it works perfectly!
[RESTRICTIONS-REMOVED] Samsung Health Monitor - TIZEN - 1.1.3.002 - Root, Age, Country & Device Restriction Removed - 23rd May 2023
Hello Everyone, I hope you all are fine... ~~~ TIZEN WATCHES ONLY ~~~ ~~~ FEATURES, BUGS & FUTURE WORKS~~~ FEATURES: Works on Active2 and Watch3 (as mentioned, Samsung Tizen Watches), Multilanguage, no root detection, no country restriction...
forum.xda-developers.com
Click to expand...
Click to collapse
You're most welcome ...
@Dante63
I know it's off-topic, but is it possible to remove root/knox detection from Samsung pay app as well? (the one for the phone, not for the watch)
doclucas said:
@Dante63
I know it's off-topic, but is it possible to remove root/knox detection from Samsung pay app as well? (the one for the phone, not for the watch)
Click to expand...
Click to collapse
Samsung pay and any banking apps are heavily guarded against tempering and modifications, so it's not possible...
Dante63 said:
Samsung pay and any banking apps are heavily guarded against tempering and modifications, so it's not possible...
Click to expand...
Click to collapse
Yes, and still we can get safety-net to pass with the new safetynet-fix magisk module, hide magisk from other apps (including all my banking apps) and able to use them and google pay without a problem now, except for Samsung Pay app. What makes this app so special compared to the other apps I mentioned?
doclucas said:
Yes, and still we can get safety-net to pass with the new safetynet-fix magisk module, hide magisk from other apps (including all my banking apps) and able to use them and google pay without a problem now, except for Samsung Pay app. What makes this app so special compared to the other apps I mentioned?
Click to expand...
Click to collapse
Samsung Pay rely on several Samsung services and framework apks which are also guarded against tampering and have root detection which is not the safety net...
Root detection comes in forms of apps installed, as you can see from Samsung Health monitor, it also would attempt to look for busybox and attempt to call "su" which is Linux command to get root access and try mounting partitions which all on success would trigger flag rooted...
So Samsung pay has additional protections aside the Samsung Health Monitor ways, it is also guarded like all banking apps with encoded strings, in other words, things you don't know what they stand for and the apps names get encoded to be compared with the provided...
Also, as long in download mode it shows custom and not official, Samsung pay won't work, it is not linked to the knox trip since official Samsung ROM works fine with everything despite the device was rooted before, knox now is mainly for voiding warranty...
I'm not much of an expert in this so some of what I said about know and Samsung pay may not be accurate...
The only things I'm sure about is how strongly they are secure against tampering and detection of root in different forms which even by having a folder named "magisk" on the internal memory believe it or not...
Thanks for the thorough and modest answer.
I personally want to believe that nothing is impossible, I guess it's only a matter of time until this will also get hacked.
The only question is - who will really want to use a hacked samsung pay app when it may contain some malwares or god knows what...
doclucas said:
Thanks for the thorough and modest answer.
I personally want to believe that nothing is impossible, I guess it's only a matter of time until this will also get hacked.
The only question is - who will really want to use a hacked samsung pay app when it may contain some malwares or god knows what...
Click to expand...
Click to collapse
I'd rather not use modified apps related to banks and cards or anything sensitive... there is a reason why they tightened the security on them but SMH or apps that have no important info, well I don't mind if my BP or ECG is leaked lol...