Related
If you own the international s7/s7 edge, and was able to install samsung pay on the united arab emirate variant, than be sure not to update the app to 2.1.04 or .03. It will not work on the UAE firmware. Stick to the older version until someone figure out what had happen.
I'm on the .04 haven't tried to use it yet
woodydog said:
I'm on the .04 haven't tried to use it yet
Click to expand...
Click to collapse
do you have the UAE firmware? When you try to use it, you will not be able to activate the app with the pin or fingerprint sensor. I updated the app through the app itself, and there was no problem. But when I tried to pay for something using my pin, the keypad will not open. I then tried installing the latest available APK, but I only get a server error message when setting up my account. I eventually had to reset my phone and reinstall the older SP APK and SPF APK to get it back. I am currently using 2.0.36 and 2.3.03 respectively. They work just fine.
jetscreamer001 said:
do you have the UAE firmware? When you try to use it, you will not be able to activate the app with the pin or fingerprint sensor. I updated the app through the app itself, and there was no problem. But when I tried to pay for something using my pin, the keypad will not open. I then tried installing the latest available APK, but I only get a server error message when setting up my account. I eventually had to reset my phone and reinstall the older SP APK and SPF APK to get it back. I am currently using 2.0.36 and 2.3.03 respectively. They work just fine.
Click to expand...
Click to collapse
On the UAE firmware did the same as you and updated in the app. Was all good till I tried to use it
Could you please provide the steps to install samsung pay on international s7 edge UAE version?
Shanky091 said:
Could you please provide the steps to install samsung pay on international s7 edge UAE version?
Click to expand...
Click to collapse
Just go-to APKmirror and download the Samsung pay app and Samsung pay framework in the versions noted above.
ChristopherXDA said:
Just go-to APKmirror and download the Samsung pay app and Samsung pay framework in the versions noted above.
Click to expand...
Click to collapse
Thanks for this. After installing Samsung pay app and Samsung pay framework I was able to get in the Samsung Pay App. When I am trying to add any of my credit cards I am getting a server error. Anyone else getting the error after adding the new card?
Shanky091 said:
Thanks for this. After installing Samsung pay app and Samsung pay framework I was able to get in the Samsung Pay App. When I am trying to add any of my credit cards I am getting a server error. Anyone else getting the error after adding the new card?
Click to expand...
Click to collapse
Did you use the newest version?
woodydog said:
Did you use the newest version?
Click to expand...
Click to collapse
I used 2.0.36 of SPay and 2.3.03 of SPay Framework as mentioned above. Trying to add Amex and Visa but got following error.
"Failed to connect to server. Try again later"
its asking me to update Samsung pay how can i stop that
Shanky091 said:
I used 2.0.36 of SPay and 2.3.03 of SPay Framework as mentioned above. Trying to add Amex and Visa but got following error.
"Failed to connect to server. Try again later"
Click to expand...
Click to collapse
You can delete the app and then reinstall to see if that will work. If not, you may have to do what I did. I had to eventually factory reset and do a clean install. After that, I had no issue with the setup process, except for one server error message. But I just kept went back and hit the start button again.
be_wise73 said:
its asking me to update Samsung pay how can i stop that
Click to expand...
Click to collapse
Are you on 2.0.36? That is the version I am using, and I only get a notification in settings of a newer version available. But it does not force my to update.
jetscreamer001 said:
Are you on 2.0.36? That is the version I am using, and I only get a notification in settings of a newer version available. But it does not force my to update.
Click to expand...
Click to collapse
Yes
I'm not rooted but I can't launch s health on the final version of Nougat that my phone updated to today. (Xxu1dplt)
It says about a Knox warning and device compromised?
It's running stock though! Anyone else with the same issue?
Have you ever rooted before and then unrooted? Sorry if stupid question
Sent from my SM-G935F using XDA-Developers Legacy app
Once knox is tripped, game over even if you unroot.
jadaress1 said:
Have you ever rooted before and then unrooted? Sorry if stupid question
Sent from my SM-G935F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Nope. I assumed s health didn't work in earlier beta due to being beta.
I've never rooted this phone. Only thing I did was install beta by applying in the beta app.
Try uninstall and re-install again s-health
Go to download mode by switching off the device then hold Power + Volume Down + Home
Does it say Warranty void: 1?
CuBz90 said:
Go to download mode by switching off the device then hold Power + Volume Down + Home
Does it say Warranty void: 1?
Click to expand...
Click to collapse
It wasn't but it is now. Seems somehow during the beta it has tripped it. I contacted samsung and they're not interested.
It doesn't matter now as i've bit the bullet and installed twrp+renovate edge rom. Ironically renovate edge is running better than the official rom did with better doze despite having all the same apps installed. And s-health works fine on it.
Not sure what samsung are trying to prove by crippling people running the official ROM.
f1ux said:
It wasn't but it is now. Seems somehow during the beta it has tripped it. I contacted samsung and they're not interested.
It doesn't matter now as i've bit the bullet and installed twrp+renovate edge rom. Ironically renovate edge is running better than the official rom did with better doze despite having all the same apps installed. And s-health works fine on it.
Not sure what samsung are trying to prove by crippling people running the official ROM.
Click to expand...
Click to collapse
Ye if Knox has tripped, Samsung will have nothing to do with it, even if it's their fault, they just don't want to hear about it.
f1ux said:
It wasn't but it is now. Seems somehow during the beta it has tripped it. I contacted samsung and they're not interested.
It doesn't matter now as i've bit the bullet and installed twrp+renovate edge rom. Ironically renovate edge is running better than the official rom did with better doze despite having all the same apps installed. And s-health works fine on it.
Not sure what samsung are trying to prove by crippling people running the official ROM.
Click to expand...
Click to collapse
If what you want is to use SHealth on stock nougat with a knox tripped phone, I can give you a working solution with one caveat.
If you were already a beta tester you need to Odin back to BTU mm (or whatever CSC version you used to join the beta) and setup your phone normally. Make sure you also open SHealth. After, if you have not received a notification to update, go to settings and manually search for updates. Depending on which version of marshmallow you went back to, you might receive one update to the latest 6.0.1 available and after that, you will again be prompted to update, this time to 7.0. If you follow these steps, SHealth will work, even with knox tripped, but, if you manually reset the phone. SHealth will be blocked once again.
I know it seems a little complicated, but it's really not that hard.
Hope this helps.
f1ux said:
Nope. I assumed s health didn't work in earlier beta due to being beta.
I've never rooted this phone. Only thing I did was install beta by applying in the beta app.
Click to expand...
Click to collapse
This is weird . There's no way Knox is tripped without you doing anything like flashing TWRP.
joejoe23 said:
This is weird . There's no way Knox is tripped without you doing anything like flashing TWRP.
Click to expand...
Click to collapse
people lie. the dindu nuffins
joejoe23 said:
This is weird . There's no way Knox is tripped without you doing anything like flashing TWRP.
Click to expand...
Click to collapse
yes, i've been flashing my phone for around 10times with official binaries and never tripped knox. I flashed BTU(from INS) and updated to N, s health working fine here
Ive had the same problem, after flashing the official UK Rom. Knox is not triggered but shealth refused to work.
I reflashed the rom using every file incl. CSC and now everything works like it should.
1stlynx said:
Ive had the same problem, after flashing the official UK Rom. Knox is not triggered but shealth refused to work.
I reflashed the rom using every file incl. CSC and now everything works like it should.
Click to expand...
Click to collapse
I am quite new at this, so you basically did this in Odin?
.... can't post link to picture
You add in Odin: BL, AP, CP and CSC ?
I have the same problem in Shealth, and i would really like to stick with warrenty (Currently in the dawnload mode is still 0). And with Shealth compromised, My Knox app doesn't works as well.
Punisher159 said:
I am quite new at this, so you basically did this in Odin?
.... can't post link to picture
You add in Odin: BL, AP, CP and CSC ?
I have the same problem in Shealth, and i would really like to stick with warrenty (Currently in the dawnload mode is still 0). And with Shealth compromised, My Knox app doesn't works as well.
Click to expand...
Click to collapse
Hi,
i used this guide :
https://www.sammobile.com/forum/showthread.php?t=30800
dont know if i am allowed to post the link.
i did step 3.
Way to make shealth working on tripped but stock devices:
Install marshmallow with odin
Run shealth for it to start collecting user data
Update to nougat without wiping device
profit
kartonick said:
Way to make shealth working on tripped but stock devices:
Install marshmallow with odin
Run shealth for it to start collecting user data
Update to nougat without wiping device
profit
Click to expand...
Click to collapse
i have tried that but i wont count steps. so its of no use. when updated it... stopped working completely
poncespr said:
If what you want is to use SHealth on stock nougat with a knox tripped phone, I can give you a working solution with one caveat.
If you were already a beta tester you need to Odin back to BTU mm (or whatever CSC version you used to join the beta) and setup your phone normally. Make sure you also open SHealth. After, if you have not received a notification to update, go to settings and manually search for updates. Depending on which version of marshmallow you went back to, you might receive one update to the latest 6.0.1 available and after that, you will again be prompted to update, this time to 7.0. If you follow these steps, SHealth will work, even with knox tripped, but, if you manually reset the phone. SHealth will be blocked once again.
I know it seems a little complicated, but it's really not that hard.
Hope this helps.
Click to expand...
Click to collapse
Hello,
I am interested with the first solution. Can you please give me more detail how to proced ? Thank you in advance
does samsung pay works with u? i bought a second hand uk handset without having any knowledge of knox which was tripped. though i got it to work following a post here, samsung pay doesnot work evenon stock firmware.
elkhalifi said:
Hello,
I am interested with the first solution. Can you please give me more detail how to proced ? Thank you in advance
Click to expand...
Click to collapse
Thank you poncespr, your solution woked for me.
I am able to launch SHealth again
App Alet popup
---------------------------------------------------
"Your device has been compromised
Because of a new security policy
intruduced in version 5.0 knox is not
available on compromised devices."
---------------------------------------------------
I have same problem, cannot use my Gear S3 now, funny is that S health works at non Samsung rooted devices :/
Some say to uninstall s health and install a previous version.. to open it and set it up and then to update the app
Check your knox. Its probably 0x1.
Knox is tripped ofc after root, i tried to unistall app but i cannot get it unistall, tried app from play store and link2sd to unistall it but it still there so if i try to flash older version i get error saying that file is corrupted.
Flashing official ROM using Odin does not trigger Knox (at least it shouldn't). I have the same problem after flashing official 7.0 ROM and my Knox Counter is NOT triggered (it is 0x0000).
I cannot uninstall or downgrade S Health since it's a "default app".
Any workarounds?
Nalix said:
Flashing official ROM using Odin does not trigger Knox (at least it shouldn't). I have the same problem after flashing official 7.0 ROM and my Knox Counter is NOT triggered (it is 0x0000).
I cannot uninstall or downgrade S Health since it's a "default app".
Any workarounds?
Click to expand...
Click to collapse
If knox is triggered then:
- make a root
- remove S health with Titanium Backup
- install older version S health before version 5
- launch app, sync account and then update to new version of S health
Working, tested one hour ago, i had this problem after flashing and rooting 7.0 stock rom.
Mystero said:
If knox is triggered then:
- make a root
- remove S health with Titanium Backup
- install older version S health before version 5
- launch app, sync account and then update to new version of S health
Working, tested one hour ago, i had this problem after flashing and rooting 7.0 stock rom.
Click to expand...
Click to collapse
Thanks for the tip but I'm not ready to trigger Knox just yet Again - My knox is NOT triggered.
Mystero said:
If knox is triggered then:
- make a root
- remove S health with Titanium Backup
- install older version S health before version 5
- launch app, sync account and then update to new version of S health
Working, tested one hour ago, i had this problem after flashing and rooting 7.0 stock rom.
Click to expand...
Click to collapse
Hi
I've just come across this problem upgrading to Nougat today. I'd like to try your suggestion but how do I find an older version of S Health like you suggest?
TIA
Just found 4.8.1. I'll give it a go.
norm2002 said:
Hi
I've just come across this problem upgrading to Nougat today. I'd like to try your suggestion but how do I find an older version of S Health like you suggest?
TIA
Just found 4.8.1. I'll give it a go.
Click to expand...
Click to collapse
Same problem and my Knox is 0×0. Anyone found what is wrong yet?
norm2002 said:
Hi
I've just come across this problem upgrading to Nougat today. I'd like to try your suggestion but how do I find an older version of S Health like you suggest?
TIA
Just found 4.8.1. I'll give it a go.
Click to expand...
Click to collapse
I had to try three versions. Two kept saying they were corrupt when trying to install. I managed to install the third but, when I try to sync, I keep being told the server is temporarily offline. I suppose that may be true but I doubt it.
And now whenever I try to open the app, it freezes and the only way to open it is to clear the data in the app settings.
So I think it's back to Marshmallow for me for now. I need S Health for my Gear S3.
norm2002 said:
I had to try three versions. Two kept saying they were corrupt when trying to install. I managed to install the third but, when I try to sync, I keep being told the server is temporarily offline. I suppose that may be true but I doubt it.
And now whenever I try to open the app, it freezes and the only way to open it is to clear the data in the app settings.
So I think it's back to Marshmallow for me for now. I need S Health for my Gear S3.
Click to expand...
Click to collapse
I tried going back to Marshmallow but after I boot the Galaxy S7 it asks for a code. I have no idea what to do next because no code seems to work.
norm2002 said:
I had to try three versions. Two kept saying they were corrupt when trying to install. I managed to install the third but, when I try to sync, I keep being told the server is temporarily offline. I suppose that may be true but I doubt it.
And now whenever I try to open the app, it freezes and the only way to open it is to clear the data in the app settings.
So I think it's back to Marshmallow for me for now. I need S Health for my Gear S3.
Click to expand...
Click to collapse
Where did you find those versions?
Cya
alehawk said:
Where did you find those versions?
Cya
Click to expand...
Click to collapse
Here under Show more.
norm2002 said:
Here under Show more.
Click to expand...
Click to collapse
thank you very much!
This guide will work for everyone. Including those getting force closes and corrupt file messages.
CuBz90 said:
This guide will work for everyone. Including those getting force closes and corrupt file messages.
Click to expand...
Click to collapse
This is for those who have triggered Knox. Our's not triggered...
theoaman said:
This is for those who have triggered Knox. Our's not triggered...
Click to expand...
Click to collapse
Have you checked if it's tripped or are you just guessing? Are you on your phones official firmware or did you flash different firmware in Odin?
I think it's not compatible with N.
I flashed MM after trying RR, and then it worked just fine. Strange though, Samsung should be able to get their apps working.
Bjaped said:
I think it's not compatible with N.
I flashed MM after trying RR, and then it worked just fine. Strange though, Samsung should be able to get their apps working.
Click to expand...
Click to collapse
Can you explain what you mean? You had the same problem and now it is solved?
I have upgraded my A310F to Nougat but decided I don't like some things (mostly related to Dream UX or whatever the thing is called) and some minor flaws like inability to use keyboard other than Samsung one (other ones crash the Samsung Keyboard process when trying to use emoticons), also the battery management is quite poor (there is no longer a list of apps I want to be killed once I just stop using them).
Anyway - I got back to Marshmallow by simply flashing firmware via Odin (all works fine again).
But the question is... how can I stay on Marshmallow forever?
Currently I've disabled the autoupdate over wi-fi but AFAIK the update popups will keep appearing once only Nougat will be officially available in XEO region.
How can I make this permanent? Any ideas?
If you have any - be it without or with rooting - please let me know. I don't want to loose the ability to use Samsung Store.
wolfensg said:
I have upgraded my A310F to Nougat but decided I don't like some things (mostly related to Dream UX or whatever the thing is called) and some minor flaws like inability to use keyboard other than Samsung one (other ones crash the Samsung Keyboard process when trying to use emoticons), also the battery management is quite poor (there is no longer a list of apps I want to be killed once I just stop using them).
Anyway - I got back to Marshmallow by simply flashing firmware via Odin (all works fine again).
But the question is... how can I stay on Marshmallow forever?
Currently I've disabled the autoupdate over wi-fi but AFAIK the update popups will keep appearing once only Nougat will be officially available in XEO region.
How can I make this permanent? Any ideas?
If you have any - be it without or with rooting - please let me know. I don't want to loose the ability to use Samsung Store.
Click to expand...
Click to collapse
If you are root it will never update
sakat49 said:
If you are root it will never update
Click to expand...
Click to collapse
Thanks!
sakat49 said:
If you are root it will never update
Click to expand...
Click to collapse
BTW: Do you know by any chance if the content bought previously in the Themes Store will be available after rooting?
wolfensg said:
BTW: Do you know by any chance if the content bought previously in the Themes Store will be available after rooting?
Click to expand...
Click to collapse
why not?
MoshPuiu said:
why not?
Click to expand...
Click to collapse
Yup. It is there I thought that this may be related with not working Samsung Pay with rooted phone but fortunately it's not.
I bought a S8 that has XSG csc from UAE. With my S7 I was able to reflash the csc/rom to make Samsung Pay work in United States.
Is this possible with S8?
When I open Samsung Pay it gives advertisement "Samsung Pay is only available in the UAE"
My service is AT&T
Download the Samsung Pay 2.7.03 apk.
Skander1998 said:
Download the Samsung Pay 2.7.03 apk.
Click to expand...
Click to collapse
I will try it tonight but when I tried the latest APK from apkmirror it told me I had to update the software and then it always says Download failed.
oplix said:
I will try it tonight but when I tried the latest APK from apkmirror it told me I had to update the software and then it always says Download failed.
Click to expand...
Click to collapse
Don't download the latest, download 2.7.03.
Skander1998 said:
Don't download the latest, download 2.7.03.
Click to expand...
Click to collapse
Thanks bro will try and post back
Sent from my SM-G930F using Tapatalk
Skander1998 said:
Don't download the latest, download 2.7.03.
Click to expand...
Click to collapse
It works. I added my chase card no problem. You are a god. I was about to resell the phone.
oplix said:
It works. I added my chase card no problem. You are a god. I was about to resell the phone.
Click to expand...
Click to collapse
Doesn't work on my S8.
I have the Panama version, TPA and using it in US with AT&T sim card.
The app will launch now, YAY!!!
I scan in a credit card with the camera, enter in the CVC code, expiration and zip code and then it tries to verify card and I get the "connection to server failed" message.
I thought this post was too good to be true.
Oh well back to the drawing board.
Mhjeff301 said:
Doesn't work on my S8.
I have the Panama version, TPA and using it in US with AT&T sim card.
The app will launch now, YAY!!!
I scan in a credit card with the camera, enter in the CVC code, expiration and zip code and then it tries to verify card and I get the "connection to server failed" message.
I thought this post was too good to be true.
Oh well back to the drawing board.
Click to expand...
Click to collapse
Having played with CSCs and Samsung Pay for my S8 and S7 Edge there are options but with compromises.
BTU firmware fast updates no white pages.
XSG firmware no white pages at least on my edge phones moderately quick updates but Ramadan shows up in the calendar.
XSA firmware slow updates white pages works Samsung pay updates through the play store and MST function works.
I have the same issue, and tried to download the 2.7.0.3 framework APK, but get a "The package appears to be corrupt" error when trying to install it.
I'm guessing this is because I already have a newer version installed. When looking into the version installed, there's no "Uninstall" button to either remove the app, or even just remove some updates.
Any suggestion please ?
Thanks in advance !
tarkil said:
I have the same issue, and tried to download the 2.7.0.3 framework APK, but get a "The package appears to be corrupt" error when trying to install it.
I'm guessing this is because I already have a newer version installed. When looking into the version installed, there's no "Uninstall" button to either remove the app, or even just remove some updates.
Any suggestion please ?
Thanks in advance !
Click to expand...
Click to collapse
its not framework. only the Samsung Pay app should be 2.7.03. Framework must be left stock. if you modified the framework you must wipe phone and start over
oplix said:
its not framework. only the Samsung Pay app should be 2.7.03. Framework must be left stock. if you modified the framework you must wipe phone and start over
Click to expand...
Click to collapse
Thanks, I was too dumb to read properly !
And I did the correct install, and my Samsung Pay now works!!!!! After few months trying to find how to make it work !!!!
Awesome, thanks all for your help!
tarkil said:
Thanks, I was too dumb to read properly !
And I did the correct install, and my Samsung Pay now works!!!!! After few months trying to find how to make it work !!!!
Awesome, thanks all for your help!
Click to expand...
Click to collapse
glad it worked out for you!
I've downloaded that Samsung pay APK but right after I open it , gives me connection error saying failed to connect to the server. Happened to me with all Samsung pay apks.. anyone knows why ? And how to fix it ?