Cl3arCh0ice
Active member
Update: decided to try it again and updated and registered pin this time
Posted via the Android Central App
Posted via the Android Central App
Same here. I can't get it to register the pin.Mine screwed up too. It tries to get me to register my pin but asks for my fingerprint to verify. I try but it just keeps going back to the page saying register. I hit register, it asks for fingerprint and the circle continues. Can't use at all now
Posted via the Android Central App
Did you talk to Samsung or Samsung Pay?
Also I would call back, get a supervisor and of they can't help, ask them to transfer you to the next level of tech support.
I talked to both Samsung and Samsung Pay for over 2 hours and at least 3 levels of support. All I got was "they have no idea" and a hang up on their part. Nothing they suggested did anything other than cause me to have to completely reset my phone twice after factory resets.
You need to ask them to escalate to a ticket.
I have found a better, less time consuming solution. I will simply not use Samsung Pay.
Well there is an issue and you aren't the only one with it. Escalating it and people calling Samsung is the only thing that will get it the attention needed for them to be required to investigate it. After a certain number of reports of an issue, an automatic investigation is triggered.
I agree there is an issue but I am not convinced it is a Samsung issue. In working with Samsung Support for over 2 hrs. and doing my own digging around in my phone I am thinking the issue is really a Verizon issue. An artifact from their actively blocking and then trying to undo the blocking and doing it poorly. The hint for me is the fact that doing a factory reset which reports and error that the Preload directory that is in fact on the phone can't be found during reset. But then what would a "simple" consumer know anything.
It is possible it is Verizon, but the above in my post still applies, need the reports, but Samsung probably needs to be involved too.
I wondered about the issue with people that side loaded and then Verizon blocked it. Some Verizon people on here aren't having an issue. That is why I asked if the ones having the issue, sideloaded the app before Verizon approved to use allow Samsung Pay.
Can't remember from all the posts.. Had people having the issue tried a wipe cache?
Also are any that are having the issue, people that side loaded the app when it went live?
I restarted. I wiped cache (twice). I don't know anything else to do. It's dead.
In answer to your question. I did side load the Framework apk. And once loaded you can't ever remove it. And I am not sure the official framework did, in fact, replace the side loaded version. I would love to burn the original OS onto the phone replacing the current version and truly start from scratch.
And I had not loaded any side APK before. I did it straight up. Mine started yesterday before I updated. I figured it wouldn't work till upated so I tried it.