Hi. So a few weeks ago I rooted my Nexus 5. I had Google Wallet up and working fine before. However, I forgot to go in and disable everything before rooting. The problem is that when I tap and pay it always says "payment declined" and just doesn't work. I was reading that this might have broken the secure element or something. I've called and been in touch with Google to see if they could help me out buy that's not really going anywhere. Does anyone have any method of completely clearing out the Google Wallet cache or something? I can't even uninstall the app as it's built into the phone or ROM. Any help is much appreciated.
Go into settings, apps and clear it's cache, may have to clear data too
Sent from my Nexus 5
If I remember correctly you need to make sure that you authorize the phone to make payments even though you have broken Google's security. This is if I remember correctly it might be under Google settings. This thread may help http://forum.xda-developers.com/showthread.php?t=1696909.
Sup fellas just posting this from my phone
Basically I rooted it with CFAUTO root I found on a site that seemed trustworthy due to its credibility found on various sites.
Root works perfectly along with Xposed for awhile but eventually a week later every single app will start force closing, or immediately fail to launch on touch. From instagram to KiK to play store itself.
Rebooting is not a good solution as it resolves into a boot loop.
This has been happening consistently for a few weeks. The only solution to get my phone back up and running is to do a factory reset (which in turn means setting everything up again to my preferences. )
This pretty much led me to leave the phone as it comes plus a few common apps and just rely on my iPad more.
Does anyone have a solution? I followed the tutorial down to the T. Video and guide. I'm considering switching to stock but want to see if anyone else had this issue or was able to fix it
I would say to use this guide.
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
Havent tried CFAUTO root, and I dont think its recommended.
I had a similar issue with apps force closing, though I didn't use cfauto root.
The issues I had, after finding out from much trial and error, was that after I rooted my apps would update before Google play services. This would cause problems because the updated apps needed the updated play services to run.
Revert back to stock, then make sure that Google play services is up to date before updating any other app. After play services are up to date, make sure your play store is up to date. Then go ahead and update all of your apps. Next reroot your phone.
Like I said before I didn't use cfauto root, but I hope this helps.
I got a new debit card over a week ago and ever since I cannot get this new card verified with SPay for my Gear S watch! I've gotten it verified for my phone, however, no problem! I only wish it didn't have to be done once for the watch and once for the phone! Anybody else with this problem? The verifying center is no help at all, all they say is "Your token is activated"!
Sent from my SM-N930T using Tapatalk
This has suddenly become a problem for me as well. It seems every time they update the Samsung Pay Gear Plug-in app, it was disabling my card, and I was having to add it all over again. This last time, it won't let me add it.
Couple things:
- It works fine on Samsung Pay on the phone
- I've tried clearing cache and data
- I've tried uninstalling and reinstalling every Samsung Pay app - Phone, Gear Plug-in, and Framework
- Strange, when it fails (continuous spinning while trying to validate the card), it says Gear Not Responding, and my only option is to try again, or back up, where it tells me the card will be discarded. BUT, I get an email saying I've registered a new card?!?! (No card is available on the watch or showing in the plug-in app).
Samsung Pay help line says to factory reset the watch. Great, now every time they update the app I'm supposed to reset the watch and set everything back up the way I like it?! No thanks!
Any ideas?
arl16 said:
This has suddenly become a problem for me as well. It seems every time they update the Samsung Pay Gear Plug-in app, it was disabling my card, and I was having to add it all over again. This last time, it won't let me add it.
Couple things:
- It works fine on Samsung Pay on the phone
- I've tried clearing cache and data
- I've tried uninstalling and reinstalling every Samsung Pay app - Phone, Gear Plug-in, and Framework
- Strange, when it fails (continuous spinning while trying to validate the card), it says Gear Not Responding, and my only option is to try again, or back up, where it tells me the card will be discarded. BUT, I get an email saying I've registered a new card?!?! (No card is available on the watch or showing in the plug-in app).
Samsung Pay help line says to factory reset the watch. Great, now every time they update the app I'm supposed to reset the watch and set everything back up the way I like it?! No thanks!
Any ideas?
Click to expand...
Click to collapse
It was my bank that finally figured out it was something on their end. I never got an explanation of the problem.
Hello everyone,
Got the problem with GPay yesterday, and cannot resolve it yet.
Performed the clean install of 9.0.2, wiped everything, all is working fine except adding my debit card in GPay.
What happens:
I open GPay app, it shows the card linked to my Google account, and says that i must 'Set up in-store payment'. When i tap the card and enter the CVC code, it starts to load something for an instant, but then just returns to the starting screen of the GPay app. Seems like it can't connect to the bank services.
What i tried:
- Linking this card to my wife's GPay - works fine.
- Linking my wife cards to my GPay - fails as mine.
- Flashing different official ROMs - 8.1.0, 9.0.1, 9.0.2.
- Wiping everything, locking bootloader etc.
- Setting the phone anew with a fresh new Google account - GPay returns an error with 'OR-TAPSH-15' code. Google does not show any info about it.
- Talking to tech support of my bank and Google - they only say that my firmware is or was modified and cannot help me because of that.
It seems that I wiped something that I shouldn't. I thought about EFS at first, but the wi-fi and cellular data works fine, and IMEI is shown right.
Maybe there's something that i miss, or there are some thoughts about this situation?
skyrood said:
Hello everyone,
Got the problem with GPay yesterday, and cannot resolve it yet.
Performed the clean install of 9.0.2, wiped everything, all is working fine except adding my debit card in GPay.
What happens:
I open GPay app, it shows the card linked to my Google account, and says that i must 'Set up in-store payment'. When i tap the card and enter the CVC code, it starts to load something for an instant, but then just returns to the starting screen of the GPay app. Seems like it can't connect to the bank services.
What i tried:
- Linking this card to my wife's GPay - works fine.
- Linking my wife cards to my GPay - fails as mine.
- Flashing different official ROMs - 8.1.0, 9.0.1, 9.0.2.
- Wiping everything, locking bootloader etc.
- Setting the phone anew with a fresh new Google account - GPay returns an error with 'OR-TAPSH-15' code. Google does not show any info about it.
- Talking to tech support of my bank and Google - they only say that my firmware is or was modified and cannot help me because of that.
It seems that I wiped something that I shouldn't. I thought about EFS at first, but the wi-fi and cellular data works fine, and IMEI is shown right.
Maybe there's something that i miss, or there are some thoughts about this situation?
Click to expand...
Click to collapse
Check playstore/ settings scroll down to the bottom to see if playstore is certified. If not and you still have a locked bootloader Wipe playstore data to become certified.
If you have an unlocked bootloader you need to flash magisk then Erase playstore data to become certified.
yldlj said:
Check playstore/ settings scroll down to the bottom to see if playstore is certified. If not and you still have a locked bootloader Wipe playstore data to become certified.
If you have an unlocked bootloader you need to flash magisk then Erase playstore data to become certified.
Click to expand...
Click to collapse
I cannot get GP certified, it is not or it shows nothing about it.
At local russian forum another person encountered the same situation after full wipe, but he's got a xiaomi
skyrood said:
I cannot get GP certified, it is not or it shows nothing about it.
At local russian forum another person encountered the same situation after full wipe, but he's got a xiaomi
Click to expand...
Click to collapse
Thanks for your attention, the resolution was really blunt
Just had to switch phone to russian, and it worked allright.
Never expected that =)
skyrood said:
I cannot get GP certified, it is not or it shows nothing about it.
At local russian forum another person encountered the same situation after full wipe, but he's got a xiaomi
Click to expand...
Click to collapse
Dude you just made my day. I had been battling with the same problems with GPay for past 2 days on my new Pixel 3... Tried just about everything. Switching to Russian, doing all GPay setup and then switching back to English finally resolved everything. If I could buy you a beer - I would
Bogega said:
Dude you just made my day. I had been battling with the same problems with GPay for past 2 days on my new Pixel 3... Tried just about everything. Switching to Russian, doing all GPay setup and then switching back to English finally resolved everything. If I could buy you a beer - I would
Click to expand...
Click to collapse
It's not me who you should say thanks =)
I know it's an old topic, but after upgrading at Android 10 yesterday I lost my Revolut card from Google pay and there is no way to set-up again the in store payments.
Anyone found any new solutions?
Just thought id put this up in case anyone else is going round in circles after an update to A13/OneUI 5.0 on Samsung devices
Updated my S20+ 5G overnight and only one issue so far...unable to connect my Watch 4 to it
Sometimes get as far as pairing code shown before inevitable fc
Issues with Watch 4 connection noted on S22's, so may be related
You would think they would test this stuff, wouldnt you.....
Bloody Samsung, premium price for garbage software updates
Im going back to A12 or start looking round for a new phone....why cant Google make a decent Pixel without buggy hardware...life was so easy when they did
Update:
Reading the S22 threads theres a whole host of issues with A13 and OneUI 5.0
Really, how does Samsung do this on a flagship??? Its like a clown show
73sydney said:
Just thought id put this up in case anyone else is going round in circles after an update to A13/OneUI 5.0 on Samsung devices
Updated my S20+ 5G overnight and only one issue so far...unable to connect my Watch 4 to it
Sometimes get as far as pairing code shown before inevitable fc
Issues with Watch 4 connection noted on S22's, so may be related
You would think they would test this stuff, wouldnt you.....
Bloody Samsung, premium price for garbage software updates
Im going back to A12 or start looking round for a new phone....why cant Google make a decent Pixel without buggy hardware...life was so easy when they did
Update:
Reading the S22 threads theres a whole host of issues with A13 and OneUI 5.0
Really, how does Samsung do this on a flagship??? Its like a clown show
Click to expand...
Click to collapse
check lot of iPhone problems..
btw, Oneplus had problem with connection GW4 after upgrade from 12 to 12.1. only one solution was reset GW. now on 1+ A13 doesnt work Google Wallet/Payments with cloned apps enabled.. Samsung is better competetion..
I haven't had the 1st issue (knock on wood) and it paired up with my GW4 right away. I flashed my One UI 5 manually
HyperChick said:
I haven't had the 1st issue (knock on wood) and it paired up with my GW4 right away. I flashed my One UI 5 manually
Click to expand...
Click to collapse
Yup, since im rooted it was a manual clean flash for me via ODIN
It seems very random according to what ive seen....but ever since Watch 4 came out its been one connection problem after another, and Watch 5 users have been plagues by them too
Try updating google play services to the latest beta (apkmirror). Solved my issue
shaharofir said:
Try updating google play services to the latest beta (apkmirror). Solved my issue
Click to expand...
Click to collapse
tried latest beta (22.45.15 (190400-488417729) beta (190400))
absolutely no difference
73sydney said:
Yup, since im rooted it was a manual clean flash for me via ODIN
It seems very random according to what ive seen....but ever since Watch 4 came out its been one connection problem after another, and Watch 5 users have been plagues by them too
Click to expand...
Click to collapse
There's your problem, root! But there are workarounds available. Just search in this forum and you'll find some
DaReDeViL said:
There's your problem, root! But there are workarounds available. Just search in this forum and you'll find some
Click to expand...
Click to collapse
Cheers, but just for reference, im quite involved in Magisk circles and hiding root (have modules to assist in this)...im usually helping others hide stuff or deal with root issues.....so i know what im doing
Also the same setup i use had no such issues in Android 12, its very much a Samsung making life harder for everyone, on purpose, because theyre basically acting like the new Apple and want to lock everything down. Ive decided to go back to Pixel, off to buy one soon, Samsung has gotten their last $ from me, they can go hang...
73sydney said:
Yup, since im rooted it was a manual clean flash for me via ODIN
It seems very random according to what ive seen....but ever since Watch 4 came out its been one connection problem after another, and Watch 5 users have been plagues by them too
Click to expand...
Click to collapse
Rooted Samsung Phones doesn't connect to Samsung Watches anymore.
You need to modify 2 files in vendor partition,
Vendor - build prop and remove SAKV2 from security keys
Vendor/etc/Wintf - Empty the Manifest.xml file
reboot and the watch will connect fine.
JazonX said:
Rooted Samsung Phones doesn't connect to Samsung Watches anymore.
You need to modify 2 files in vendor partition,
Vendor - build prop and remove SAKV2 from security keys
Vendor/etc/Wintf - Empty the Manifest.xml file
reboot and the watch will connect fine.
Click to expand...
Click to collapse
You prolly missed this module of mine in my signature (signatures dont show on mobile) , but i was already using that method and had been for a while :
GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices
Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices - GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" f...
github.com
I did later figure it out, will post my outcome separately
73sydney said:
You prolly missed this module of mine in my signature (signatures dont show on mobile) , but i was already using that method and had been for a while :
GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices
Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices - GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" f...
github.com
I did later figure it out, will post my outcome separately
Click to expand...
Click to collapse
Thank you for this.
I will use this If I ever lose the R/W ability in my device.
For now I have R/W - so I wrote to the file directly.
Heres what i found out......
TLDNR version:
Dont backup and restore Samsung Wearables Apps - even if you previously were able to do this for eons, like i had. I have used Migrate to backup and restore apps and app data for eons (important to note i always left the app data (middle column in Migrate GUI) disabled for Samsung Wearables apps. Always let the Watch be detected as part of device setup on stock ROM OR install the Galaxy Wearable live from the Play Store (after clearing Google Play Services/Store sata and achieving Integrity check if you are rooting your device)
Longer version:
The other night i finally got time to flash back to A12, ran my normal procedure, rooted, USNF...clear data on GP/GS and then connected Watch...only it still wouldnt connect, even though the app restore was taken from a clearly working A12 (just before i flashed A13)
So i had to alter my procedure in leaving out the backed up Samsung wearables apps during restore, and then let the installed ROM detect the presence of the Watch 4 AFTER i have rooted, USNF...clear data on GP/GS and then connect Watch...
Looks a little like this:
* Flash ROM via ODIN (including my special AIO.zip to install TWRP, format data, decrypt data etc)
* Watch 4 WAS powered on and waiting to be detected when setup wizard looks for it towards end of setup - ignored/cancelled setup this time - going to do the root, USNF module and integrity check thing firsties
* Finish setup
* Reboot to TWRP recovery
* Root with Magisk (renamed to .zip) via TWRP
* Reboot
* Install Magisk App to complete install (you can just use the stub installer which will download the full app, but im used to doing it this way)
* Reboot
* Install USNF (Mod) and put device in airplane mode clear data on Google Play Store/Services to pass Integrity Check
* Reboot
* Take device off airplane mode....
* Open Google Play and confirm its certified (just needs to show version (Device Is Certified of course comes later - as along as it doesnt say Device Is Not Certified, all is well)
* Watch 4 automatically detected (Wearable Manager Installer - this is i think obviously a stub installer to detect and call the latest Galaxy Wearable from the Play Store) and Watch setup commences
* Watch setup completes
* Restore remaining apps via Migrate (leaving wearables unselected - will leave them unchecked on next backup)
NOTE: you must do (and ALWAYS have had to do) the Watch connection AFTER clearing data on GP/GS to get Integrity to pass. If you do that data clear after you connect the Watch it will sever the connection, as it tied to GS
Noter 2: Ultimately i decided id had enough of Samsung tomfudgery, and i bought a Pixel 6 Pro and departed for sanity back to Pixel Lyfe.....
My watch 5 out of nowhere stopped connecting to the wearable app, but was still connected to Bluetooth. Tried clearing cache on my s22 and the watch, reset data to the wearable app, uninstalled it and the watch 5 app, reset the watch, nothing works.. Now that I reset the watch I can't get it set up.. It downloads the watch 5 app, I click OK on accept updates, then it says error then the wearable app crashes.. I tried installing an older version of the app, but it wants to update before it'll do anything. Anyone able to get past this? I can't use my watch at all. Sooo aggravating.
gettinwicked said:
My watch 5 out of nowhere stopped connecting to the wearable app, but was still connected to Bluetooth. Tried clearing cache on my s22 and the watch, reset data to the wearable app, uninstalled it and the watch 5 app, reset the watch, nothing works.. Now that I reset the watch I can't get it set up.. It downloads the watch 5 app, I click OK on accept updates, then it says error then the wearable app crashes.. I tried installing an older version of the app, but it wants to update before it'll do anything. Anyone able to get past this? I can't use my watch at all. Sooo aggravating.
Click to expand...
Click to collapse
That behaviour has been noted on S22, and well even the Watch 4, once disconnected could be a pain to get connected again, involving a Watch reset (which of course you have tried
Samsung got wise to the whole "install and older version fo the app" thing a little while ago, because it was a legit way to get Samsung Health working on rooted Samsungs, and so now its a forced upgrade on some of the wearables related apps....
As i said above, the backup (that started all this) i had was from a working install where everything worked and had for many months, but when restoring it, which id done a couple of dozen times, this last time it caused chaos. the ONLY way i could get it working was the way i outlined above, which wasnt an issue for me as i was already clean flashing, but from an installed system, well i dont know what to tell you , i tried various clearing/uninstalls of apps and could never get it to connect until i did what i did in the last post
But i dont even know if youre using a rooted S22...im guessing not
You could try clearing data on the Google Play Store and Google Play Services as they also play a part in the Watch connection (i.e. if you clear data on these ever with the Watch connected, you WILL sever the connection) and then try running Watch connection setup again
73sydney said:
That behaviour has been noted on S22, and well even the Watch 4, once disconnected could be a pain to get connected again, involving a Watch reset (which of course you have tried
Samsung got wise to the whole "install and older version fo the app" thing a little while ago, because it was a legit way to get Samsung Health working on rooted Samsungs, and so now its a forced upgrade on some of the wearables related apps....
As i said above, the backup (that started all this) i had was from a working install where everything worked and had for many months, but when restoring it, which id done a couple of dozen times, this last time it caused chaos. the ONLY way i could get it working was the way i outlined above, which wasnt an issue for me as i was already clean flashing, but from an installed system, well i dont know what to tell you , i tried various clearing/uninstalls of apps and could never get it to connect until i did what i did in the last post
But i dont even know if youre using a rooted S22...im guessing not
You could try clearing data on the Google Play Store and Google Play Services as they also play a part in the Watch connection (i.e. if you clear data on these ever with the Watch connected, you WILL sever the connection) and then try running Watch connection setup again
Click to expand...
Click to collapse
Yeah, not rooted. I'll give the clearing play store and services data a whirl. I also have a conversation going with Samsung support on Twitter. Thanks for replying!
DaReDeViL said:
There's your problem, root! But there are workarounds available. Just search in this forum and you'll find some
Click to expand...
Click to collapse
Root has nothing to do with, the Galaxy Wearable app doesnt stop working if your knox has been tripped.
Ive had the last 3 Galaxy watches and all my phones have been rooted with custom roms, any issues ive had connecting/pairing were user error.