SO Android Pay is out, and since we lost ISIS/SoftCard we have been without Tap and Pay. It says that Android pay should work on any NFC Android phone KitKat or above. I installed the app and made sure I have the latest Google Services, which I do, but I keep getting an Android Pay Unavailable error when I try to run it. Has Anyone had any luck. I have a Note 3 with stock Deoxed Rom Rooted and Xposed.
Link to Pay
Link to Services 8.1.13 - 238
Same issue for me. Actually found services 8.1.14(238) and get same issue and am stock. I have unlocked the BL in the past though if that becomes info we need to see to understand this. Would be curious what luck a 100% stock and never messed sorta T-Mo person would have.
nygmam said:
SO Android Pay is out, and since we lost ISIS/SoftCard we have been without Tap and Pay. It says that Android pay should work on any NFC Android phone KitKat or above. I installed the app and made sure I have the latest Google Services, which I do, but I keep getting an Android Pay Unavailable error when I try to run it. Has Anyone had any luck. I have a Note 3 with stock Deoxed Rom Rooted and Xposed.
Link to Pay
Link to Services 8.1.13 - 238
Click to expand...
Click to collapse
It won't work on a rooted system. It also won't work if xposed is installed...even with root cloak. I think you have to be 100% stock unrooted and odexed. I really hope I'm wrong here, but that seems to be the case.
Sent from my SM-N900T using Tapatalk
I am 100% stock and get Samsung updates and the like. I had rommed prior and so had unlocked the BL, but am now 100% stock again other than the BL security flag that knows I once had BL unlocked. Getting this same exact message.
I have to assume this fist release of Pay has yet to address the missing tap to pay sorta NFC stuff on our T-Mo Note 3's and is basically won't load on our devices as it knows it won't work. Probably why none of us have seen Wallet upgrade to Pay in the Play Store just yet or got the services 8 upgrade without doing it manually. They probably need updated still to make our devices work.
The SM-N900T never had a locked bootloader. You may be referring to the knox flag, which shouldn't matter.
Sent from my SM-N900T using Tapatalk
Yeah...meant the Knox flag...other than tripping that awhileven back I am 100% stock again...recovery and all. Never realized the BL was always unlocked on this. I have just tried Google Services 8.1.15 and still the same error.....seems the base Pay app is still not compatible with all NFC capable hardware yet probably. I'm sure this is why I can load the new wallet app from Play, but still don't see the Pay upgrade to the old one.
New Pay app and still no luck...same Pay Unavailable error. This build of Pay may have added support for some devices other than ours though...
https://www.apkmirror.com/apk/google-inc/android-pay/android-pay-1-0-103131485-android-apk-download/
3rd play build still no good....the Play Store page for Pay now shows up and old Wallet is gone. The Pay page says my device is not compatible....so the NFC nonsense must will be an issue...so annoying they can't get this working.
Then they shouldn't say that it will work on any device with 4.4.4 and above with nfc because that is clearly a lie
Yeah....seemingly they should have said "Our goal is to" rather than it "It will" as if it would be good to go for everyone out of the gate.
Note 3 will not support android pay, ever...or samsung pay?
This is something I have researched for a while. It appears that the note 3 was built with an NFC not capable of host card emulation, which google wallet and now android pay depends upon. The work around I am hoping for is to pair a gear s2 with my note 3 and get samsung pay loaded somehow, so I can tap and pay with the watch. I was linked to a page by AT&T support that listed the note 3 as a non supported device on Google's android pay site.
Related
I hear that Google Wallet does not work if the phone is rooted. I got unsupported device message. Here's my question :
- Can you use wallet app with rooted phone ? (actual work , I haven't tried yet ; I denied root access but the message still there)
- Do other NFC apps request root to run ?
Nhan Lam said:
I hear that Google Wallet does not work if the phone is rooted. I got unsupported device message. Here's my question :
- Can you use wallet app with rooted phone ? (actual work , I haven't tried yet ; I denied root access but the message still there)
- Do other NFC apps request root to run ?
Click to expand...
Click to collapse
It works fine with a rooted device, it just warns that it's not supported (and links to the article describing the security risks briefly).
In general root access isn't needed for anything NFC related - this was a recent addition to Google Wallet.
So you still can pay with GWallet on root phone :great: I also interested with NFC modding. I see there are many NFC card with vary capability (from 50b to 1Kb) , which one should I buy ? (I'll use for turn Wifi/Bluetooth on/off or Change brightness e.t.c)
Nhan Lam said:
So you still can pay with GWallet on root phone :great: I also interested with NFC modding. I see there are many NFC card with vary capability (from 50b to 1Kb) , which one should I buy ? (I'll use for turn Wifi/Bluetooth on/off or Change brightness e.t.c)
Click to expand...
Click to collapse
There's a thread for that...
http://forum.xda-developers.com/showthread.php?t=1697563
Confused
krohnjw said:
It works fine with a rooted device, it just warns that it's not supported (and links to the article describing the security risks briefly).
In general root access isn't needed for anything NFC related - this was a recent addition to Google Wallet.
Click to expand...
Click to collapse
I have an EVO 4G LTE and prior to rooting I definitely cleared my Google Wallet. But just now since rooting and installing Charmeleon, when I load Google Wallet I get this message:
Not Supported
--------------
Unfortunately, Google Wallet has not yet been certified in your country or on your device / carrier.
Obviously, this is not true, because it worked just fine prior to rooting.
Clicking OK merely closes it out, so how can it still work if I can't go any further?
It can still run up until that verification takes place, I've seen it many times on my sgs2 when we first got nfc enabled awhile back. Anyway to address your problem it could be a couple of things, first thing that comes to mind is your apn settings. My reasoning is you said it worked completely before and you flashed chameleon so the error your getting could definitely be that. Check your apn settings, make sure your connecting to the same servers as before. If that isn't the issue let me know as I don't have your lg so I couldn't tell you if it has something to do with the secure element at this time.
Actually I just did some quick research for you. It seems even people on stock rom are having issues with nfc and not just Google wallet but a lot of reports of not being able to detect nfc cards or other credit cards,pay pass etc. Does your nfc work in any of those capacities? If not I would start there because if that doesn't work Gwallet surely won't. Lastly I just read a few issues in the sprint version of the phones forum on xda people believe there's an issue with the placement. Check it out
Sent from my SGH-I777 using xda premium
Nizda1 said:
Actually I just did some quick research for you. It seems even people on stock rom are having issues with nfc and not just Google wallet but a lot of reports of not being able to detect nfc cards or other credit cards,pay pass etc. Does your nfc work in any of those capacities? If not I would start there because if that doesn't work Gwallet surely won't. Lastly I just read a few issues in the sprint version of the phones forum on xda people believe there's an issue with the placement. Check it out
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Thank you for looking into this, and for discovering others are having issues. I'm not sure how to go about checking my APN settings, but I am looking it up.. so as soon as I figure that out I will post back and let you know what I find lol
---------- Post added at 09:02 PM ---------- Previous post was at 08:57 PM ----------
I believe my APN was and is LTE/CDMA unless I'm miss understanding, this doesn't appear to have changed. As far as the other trial&error's you've suggested, I am going to have to try those later because I am at work for the night, and don't have access to anything here. Thank you for looking into this!
I can't Help You *_*
USAMac said:
I have an EVO 4G LTE and prior to rooting I definitely cleared my Google Wallet. But just now since rooting and installing Charmeleon, when I load Google Wallet I get this message:
Not Supported
--------------
Unfortunately, Google Wallet has not yet been certified in your country or on your device / carrier.
Obviously, this is not true, because it worked just fine prior to rooting.
Clicking OK merely closes it out, so how can it still work if I can't go any further?
Click to expand...
Click to collapse
You can check out my guide here for your answer http://forum.xda-developers.com/showthread.php?t=1810282
i am new to android and roms altogether so any help is much appreciated.
I just recently got ahold of a tmobile Galaxy S3. it came with 4.3 on it i rooted it and installed the cm11 rom evrything worked out perfectly but the tap to pay functions were not working. i have searched online and see this is a common problem and was wondering if there is any working roms or fixes that will allow for the nfc to work on the phone?
Short answer nope.
Back when Google Wallet was Google's the nfc payment app(AKA when it was good) it used Secure Element that worked as long as you had a T-Mobile sim and a modded copy of Google Wallet. Later on Wallet switched to H.C.E (Host Card Emulation) as so died NFC payment on the S3.
Cyangenmod doesn't support H.C.E and Samsung stop at Android 4.2-43 which also doesn't have H.C.E support. Even if the S3 had an official 4.4 rom Samsung used some weird NPX chip that doesn't work with H.C.E anyway.
Let's say you find a way around all that Android Pay doesn't work on a custom rom or rooted devices even with the system less root method.
I went to use Samsung Pay and noticed it did not show up at the bottom of the home screen, so went into programs to open it. I got a message saying I needed to update it to continue, but when I tried, got a message saying it was not available. Obviously, blocked on the N7. I'm actually sorry I tried to update, as anything Samsung is risky under the circumstances. I really liked SP, but guess I'll switch over to Android Pay. Any ideas?
Google the apk
Just Google samsung pay apk along with what ever new version of samsung pay you need to update to. Use your phone for the search because you can just down load the updated version directly onto your phone. Once downloaded just find it on your phone and click on it to open it up and follow the directions. It's pretty easy and should get you up and running in about 10 mins or less. I've done it a couple times on my Note 7
wakecrash said:
Just Google samsung pay apk along with what ever new version of samsung pay you need to update to. Use your phone for the search because you can just down load the updated version directly onto your phone. Once downloaded just find it on your phone and click on it to open it up and follow the directions. It's pretty easy and should get you up and running in about 10 mins or less. I've done it a couple times on my Note 7
Click to expand...
Click to collapse
Thanks! I'll check that out. I'm always a little reluctant to sideload apps that involve financial stuff. But I'm also reluctant to load anything Samsung now in case they include some kind of kill switch.
Still trying to find a way to get Google Pay working when the device is rooted with magisk.
https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
Works for me.
Is there something wrong with the XDA search function? Geezal peezal.
Sent from my Pixel 3a XL using Tapatalk
Google Pay works just fine on this device out of the box.
If you have unlocked and rooted your phone, then you may need to do additional tweaks or mods to get Google Pay to work again. It has nothing to do with this device, and everything to do with making your phone less secure which prevents Google Pay from working. This is not the correct forum for this question and although users have been helpful in pointing you to the correct solutions, any future questions should be directly to the forums for your root method or even more specifically on threads dedicated to making Google Pay work with root.
Hello everyone.
I'm totally new here. This is my first post on XDA.
Recently I bought a 2nd hand phone, Samsung Note 10 Plus with a very good condition. Everything seems to me perfect when I purchased it. All features are working great.
Recently I tried to add an educational google account that was provided from one of educational institution.
When I tried to add this account on this particular phone, it's showing an error that -
"Can't create work profile!!
The security policy prevents the creation of a work profile because a custom OS has been installed on this device."
(I'm posting the screenshot also)
I don't know why it's showing this error message, because I'm not using any custom OS, according to my knowledge. I got official OTA update after purchasing it.
So as far as I know, it's running on stock OS.
The model number of my Note 10 Plus is "SCV45". It's a Japanese variant named "au".
What is reason of this error behind it? I didn't install any custom OS nor root my phone. I don't know the previous history as it's a 2nd hand phone. What should I do now to fix this issue. Please help me as I'm new to this thread.
Settings>About Phone>Status>Phone Status
Phone status should be "Official" otherwise it's been rooted and the Knox efuse tripped.
Can you set up/use Secure Folder?
Thanks for your earliest reply.
Here, phone status is showing "Official".
But after using some days, I get t know about "Knox Security" & I found heart breaking fact that my phone's "Knox Security" is void & I have to live with it as there is no workaround for that issue. (Found on XDA)
But the fact is, currently I didn't found any root access & from the about section, it's showing Official OS.
Then why it's giving error msg that I am using custom OS?
I got to know from xda that if knox security is tripped then I can't use some of Samsung app like Samsung Pass, Secure Folder, Samsung Heath....
But why I can't use a work profile when I am running on stock OS & which is not ever rooted (according to my knowledge).
So what I can do now to fix this issue?
Please help.
So much for that efuse trip method indicator... there are other ways to tell. Lol, always thought that one worked. You're questions have me curious as well.
My guess it was Knox efuse, but as for work profile not sure if it was or is tied together with Knox.
I avoid the Knox features as they're rules are convoluted... and I have no need for them.
You might want to reflash the firmware to be on the safe side. There are many here that can give you a better appraisal about this than me though.
I run stock N10+'s.
Lastly you could consider returning the device if it has been rooted in the past and the seller didn't state so.
blackhawk said:
So much for that efuse trip method indicator... there are other ways to tell. Lol, always thought that one worked. You're questions have me curious as well.
My guess it was Knox efuse, but as for work profile not sure if it was or is tied together with Knox.
I avoid the Knox features as they're rules are convoluted... and I have no need for them.
You might want to reflash the firmware to be on the safe side. There are many here that can give you a better appraisal about this than me though.
I run stock N10+'s.
Lastly you could consider returning the device if it has been rooted in the past and the seller didn't state so.
Click to expand...
Click to collapse
I didn't think so it is tied with knox security. Because I have used that work profile on another mobile other than a Samsung phone. So there is no link up between my work profile and the knox security.
Now I want to reflash the stock firmware by Odin3. But the problem I faced is, when I visited SamMobile for downloading the exact firmware, I didn't see any model number with "SCV45".
All the model numbers are like - SM-N975F, SM-N975U, SM-N975U1, SM-N975N... & so on.
So, should I flash any of them? I can't choose the proper version.
My mobile is snapdragon variant.
If I flash any of the version, what will happen?? I need to know about that.
And lastly, about returning the device.
I have purchased it as 2nd hand, and the first unit that I got, has the hardware problem. So I already returned that one. So they already gave me a replacement.
So I know, there must be some issues & I have to accept that as I am getting at very cheap price. But the last one I received, is totally in fresh condition. Even the screen paper that comes with intact phone, is still there. I have checked all the the hardware and sensors. All are working perfectly. And battery backup is also good. I am getting almost 7.5hr SOT. I have checked the battery cycle. Battery discharge cycle count is 164 (I don't know whether it is modified or not). I checked the other phones that have battery discharge cycle count is almost 500 to 700.
That's why I pick this last one. All seems perfect. Only have the issues with knox security, but I get to know about that later. And knox security is also not important for me. But at least I need to use my work profile.
That is the Japanese variant.
If you're stateside a Samsung Experience center at a Best Buy can run advanced diagnostics on it and reflash it if needed.
I would stay on Android 10. Either 9 or 10 run well. 11 not so much so and 12 is a mess, both have fully active cpu cycle sucking scoped storage.
blackhawk said:
That is the Japanese variant.
If you're stateside a Samsung Experience center at a Best Buy can run advanced diagnostics on it and reflash it if needed.
I would stay on Android 10. Either 9 or 10 run well. 11 not so much so and 12 is a mess, both have fully active cpu cycle sucking scoped storage.
Click to expand...
Click to collapse
When I purchased the Mobile, It has Android 10. I've upgarde to andoird 11 just. Everything is working fine except that issue.
Can I flash SM-N975U or SM-N975U1 firmware? there will be any problem??