samsung pay with root - Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot

I have a A8 2018 version and knox has been tripped since shortly after i got it, and samsung pay has worked perfectly fine on my watch the whole time. I finally decided to install TWRP and Magisk, and ever since them samsung pay hasnt worked. Ive been reading everywhere that samsung pay doesnt work with the knox e-fuse tripped, which plainly isnt true. Its been working for me just fine for months all the while samsung health hasnt worked because of it being a "rooted phone". So, samsung pay was working, samsung health wasnt, knox was tripped, no TWRP or Magisk installed, then installed the last two items there and boom, samsung pay broke. I havent tried reflashing the stock img.tar file and reloading all my apps etc etc, but im also wanting to avoid having to do that. Is there some magic way to hide root from everything that needs to be oblivious to it? Ive checked [email protected] near every box in the hide magisk tool within magisk manager to no avail. Besides, does hide magisk actually hide root, or just the presence of the magisk app?
anyways, if anyone has had success regaining functionality of sammy pay while maintaining root, your feedback is most welcome. My next step is going to be to reflash the stock tarball with Odin, thats just a huge waste of time if it doesnt work

Related

New to Samsung devices, but just need to make sure

Hello all,
This is my first Samsung device, the Galaxy S7 Edge Dual sim (SM-G935FD) bought from UAE.
I used to install TWRP and root every android phone I had before, so I am still not sure whether to root this one. I already have the files required for rooting, but I noticed that there are 2 ways of rooting:
1. Using Odin to install TWRP and then from there install SuperSU.
2. CF-Auto-Root.
What is/are the difference(s) in both methods?
My other question is: I read that rooting will trip Knox, and there is NO WAY to get it back to normal even flashing the original ROM. Is that the case?
One last thing, I am now stuck in the download mode (turned off the phone, pressed "Volume down", "Home" and "Power"), I did that just to check the info on the top left (model and warranty void...) but I cannot seem to restart the phone even by pressing the power button for more than 20 seconds, how can I turn the phone off then back on?
Thank you
*****EDIT*****
Regarding my last question (stuck in Download mode), pressing the same combination got me back to start the phone normally
Cf-AutoRoot will root your phone but then you will have to put your recovery on also usually flashed with Odin anyway or an app if it's working for the Galaxy S7... Twrp plus superuser will root and you'll have the recovery installed.... They both will trip your official (0x0) knox and make it (0x1) custom.... You can always go back to stock rom and get OTA updates but your knox will remain at 0x1......this is supposed to void the warranty but depending on where you live it won't make a difference.... Also if you want to flash roms and mods and kernels just use the twrp method and if you just want root and to be able to use root permission apps use the Cf-AutoRoot.... As of right now I haven't rooted because there aren't to many Roms available... I'm sure I will cause I miss titanium backup and the ability to get rid of all the bloat ware (especially Facebook & Microsoft ****).... The phone runs great without root and battery is excellent.... The last reason I was waiting was Samsung pay won't work with tripped Knox counter.... I live in the US but have the international 935F... So it doesn't look like this variant will support Pay anytime soon.... Probably gonna root when development picks up a little....
*edit*... Always have a stock rom just in case saved to your computer just in case... That would of saved me lots of freak outs and headaches years ago... Now it's the first thing I do before Rooting or flashing anything to my phone
Galaxy S7 edge
Kjc99 said:
Cf-AutoRoot will root your phone but then you will have to put your recovery on also usually flashed with Odin anyway or an app if it's working for the Galaxy S7... Twrp plus superuser will root and you'll have the recovery installed.... They both will trip your official (0x0) knox and make it (0x1) custom.... You can always go back to stock rom and get OTA updates but your knox will remain at 0x1......this is supposed to void the warranty but depending on where you live it won't make a difference.... Also if you want to flash roms and mods and kernels just use the twrp method and if you just want root and to be able to use root permission apps use the Cf-AutoRoot
Galaxy S7 edge
Click to expand...
Click to collapse
Thank you for the detailed reply.
I made a research yesterday on Knox (as I said, this is my first Samsung device), and I just wanted to make sure that I understood things properly.
So now after reading, tripping Knox will disable Samsung Pay (I do not have it in my country) so that is not going to make any difference. But, what about paying using the fingerprint sensor in Google Play, will it stop working if Knox is tripped? I also use the fingerprint sensor to login to my mobile banking app (instead of typing the password every time I want to login), will that stop too? I guess not but again just to be sure.
Thanks a lot once again.
I know when I rooted my S6 all the fingerprint stuff still worked so I dont think it will make a difference... Im not sure with the S7 edge but I would think it would still work cause all of those require a typed password before you use your fingerprint(1st setup only) Then use your fingerprint there after... .. Doesn't have anything to do with Knox
Galaxy S7 edge
yep, it all still works. just Samsung pay & private mode.

Samsung Pay still not working after restoring to stock through ODIN

Got my S7 yesterday, played around with root, and decided to go with a stock experience for the time being so I can use Samsung Pay and MST (blasphemous, I know). I used ODIN to restore back to stock, verified KNOX counter wasn't tripped, and went on setting everything up.
I installed Samsung Pay and launched, only to run into the access denied message you would see if you were attempting to open it with a rooted device. Any thoughts as to what could be happening?
Song0330 said:
Got my S7 yesterday, played around with root, and decided to go with a stock experience for the time being so I can use Samsung Pay and MST (blasphemous, I know). I used ODIN to restore back to stock, verified KNOX counter wasn't tripped, and went on setting everything up.
I installed Samsung Pay and launched, only to run into the access denied message you would see if you were attempting to open it with a rooted device. Any thoughts as to what could be happening?
Click to expand...
Click to collapse
I would make sure you followed the return to stock instructions in psouza4 thread (http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039). I flashed through odin yestererday and took the pf2 update that was available when I was done. I am able to install and access Samsung pay. What all did you flash in ODIN?
thefirst__noel said:
I would make sure you followed the return to stock instructions in psouza4 thread (http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039). I flashed through odin yestererday and took the pf2 update that was available when I was done. I am able to install and access Samsung pay. What all did you flash in ODIN?
Click to expand...
Click to collapse
Resolved! Actually, it was my strict adherence to the instructions that led to the issue - the instructions only tell you to flash AP, CP, and CSC back down to PE1. Which was fine and dandy, but my BL remained at PF2, which is the reason why I had issues loading Samsung Pay. I was afraid that I had either tripped the mythical physical e-fuse somehow, or my phone was blacklisted from Samsung Pay servers - fortunately this was not the case! Once I updated everything back to PF2, Samsung Pay was able to load.
Help Galaxy s7
Hello friends, I made the root process in my S7 GALAXY, but the direct method cf self root, now my knox is 0x1. Is this with your method, I can return to the original state knox 0x0 and able to use the Samsung pay ???
[email protected] said:
Hello friends, I made the root process in my S7 GALAXY, but the direct method cf self root, now my knox is 0x1. Is this with your method, I can return to the original state knox 0x0 and able to use the Samsung pay ???
Click to expand...
Click to collapse
Sorry but there's no method at this time to reset Knox back to 0x0. The method of root that was posted here wouldn't trip Knox which is why when flashing back to stock they are able to use Samsung Pay again.
how to trip that knox again? and how to check knox state? I had installed stock samsung s7 edge India ROM latest but now smart tutor apps is gone (that i intalled from playstore) and samsung pay is not working

Android Pay not working.

I Haven't rooted my phone yet but it keeps telling me this when I open android pay, when I first got my phone I set my up my card but now it saying that phone is either rooted or bootloader unlocked which isn't the case.
On Vodafone UK, before this I used my OP3 with Magisk with Android Pay but I haven't used that since I've got my s8 so I'm not sure what the issue could be.
Any insight to this?
Besides the usual factory reset.
same here EE UK S8 not rooted (yet) but comes up with same error message. It worked fine on my rooted and hidden with magisk S6
edit - oh and factory reset doesn't work as I already tried that. I thought it might have had something to do with bringing over magisk app from my google backup but I specifically didnt install that the 2nd time around. Knox hasn't been tripped so its not that
I'm having the same issue on a Galaxy S8 via Tmobile. I've never rooted it, have no clue if the bootloader is unlocked and I'm stock since I reset the phone the first time I got the error. Still getting the error and Android pay help chat was not useful.
Same issue here, on Voda UK. I used Package Disabler pro and thinking I might have disabled something I need.
So since I had OEM unlock enabled after disabling it, it passes and safetynet now.
I had no problems adding cards, but a few days later when I wanted to add more cards, I get the error. I can't remember what I did in between that would've caused this, but definitely not rooting! I turned developer option to off and still get the error.
My S7 is rooted and TWRPed and have no problems adding cards!!!!???
Very weird. Working just fine on my rooted s8+ with magisk.
I'm on T-Mobile with a S8 and Android Pay connected to my PayPal is getting card read error everywhere I try to use it.
Safety net says everything is ok too. Not sure what's going on. I have the newest update and not rooted.
Sent from my SM-G950U using Tapatalk
I installed different Samsung Pay Framework apk and now I want to revert back and downgrade to another version to make Spay work.. when I click uninstall updates it wont let me. (Gives message that App is needed by system administrator.. when I open sys admin nothing there. hidden app)
Any ideas or suggestions on how to downgrade Samsung Pay Framework?
Thank you in advance,
Joe
xeathpk said:
Very weird. Working just fine on my rooted s8+ with magisk.
Click to expand...
Click to collapse
Hi Can you let me know how you managed to root with Magisk and get Android pay etc to work?
My phone:
Model: SM-G955F
SW: G955FXXU1AQF7
I tried rooted and couldn't get it working, and now recovered to official ROM and still can't get it to work?!?
Dont you people know anythin?
All EU(exynos) S8 and other galaxies come with unlocked bootloaders. Thats causing the problem
Lock it
Hi all,
I already posted a question in the Official stock upgrade but it got lost in the other comments, so I'm trying my luck again.
I had an italian branded SM-G950F (OMN), I wanted to remove all the Vodafone stuff, so I installed a MULTI-CSC as per the official stock firmware upgrade thread, when I did it I had my Australian sim card in and I got a weird UK CSC (the multi CSC didn't have australia in it), after installing everything I noticed that Android Pay didn't work, so I did a factory reset with my italian sim card in and still Android Pay was complaining that my firmware was modified or rooted.
I decided to use an australian specific firmware so I downloaded an XSA firmware and did the procedure again.
At this stage Secure Folder and Samsung Pay work (the phone is NOT rooted, this update has been the only "mod" I have done) but Android Pay is still saying that my rom may be modified or rooted so it doesn't open.
It is pretty important for me because my back supports android pay but not samsung pay
The phone is not rooted, if I reboot the phone in download mode the warranty void bit is 0 (which is good).
If I use Root Checker Pro, under safety net tab, I get CTS profile match as FAIL, I was thinking this could cause Android Pay to fail.
any idea?
start to uninstall suspicious apps, then restart . worked with my un-rooted S8. OEM unlock: OFF
degsyh said:
same here EE UK S8 not rooted (yet) but comes up with same error message. It worked fine on my rooted and hidden with magisk S6
edit - oh and factory reset doesn't work as I already tried that. I thought it might have had something to do with bringing over magisk app from my google backup but I specifically didnt install that the 2nd time around. Knox hasn't been tripped so its not that
Click to expand...
Click to collapse
Does rooting in UK\Europe void our warranty?
mariuscrist said:
start to uninstall suspicious apps, then restart . worked with my un-rooted S8. OEM unlock: OFF
Click to expand...
Click to collapse
Hi mariuscrist,
I'm not sure what app can be suspicious, I have reinstalled the apps I had before the firmware update and I could use android pay then. I'll see what it can be, probably it could be worth to do a factory reset and test android pay before anything else?

Help: Tripped Knox - Some apps are not working

I have a Samsung S8 G950F - Nougat 7
It was originally on a Vodafone firmware and I installed the stock BTU firmware to get rid off some of the bloat apps.
It was then flashed with TWRP.
A NANDROID backup was done on the system, data, bootloader, baseband.
Afterwards, magisk was installed.
The reason why I installed Magisk was because I believe it would not trip KNOX but in download mode it shows void warranty = 1
Magisk is now successfully installed and I can see all three sections being green.
However when it comes to using some apps that check if the phone has been rooted, the check fail and I can't use those, some of the apps are:
- Software update {error, it recognises the software being changed
- Secure folder {error, can't because of knox mode
- Lloyds banking {error, it recognises the software being changed
In Magisk manager settings, I activated Magisk hide and then from magisk hide I checked the boxes of the aforementioned apps but this hasn't fixed the issue.
1) How can I make those apps/actions work?
2) I understand knox trip is irreversible, I can't go back now?
3) what are my options?
Thanks
Vodafone give 30 days satisfaction guarantee, ask for a replacement at the door or a return and order again.
It was bought through someone and it's been more than 30 days.
You blew the fuse when you installed TWRP, not Magisk. And no, there is nothing you can do now to go back. I don't use the 3 apps you specified, but I'd ask the Magisk Hide dev's about them. They may or may not be able to work around them....
I've asked them and they told me to go to the specific section of the device as there might be other people using these apps in this device and they might have found the workaround

Future SafetyNet and Knox.

So how likely is it that SafetyNet will be updated in the future to properly detect Systemless root existence, or Magisk itself?
I'm no android system expert, but assume its possible and if/when the day comes devices that have tripped knox will no longer be able to run apps like Samsung pay.
It's possible the cat and mouse game could continue and another bypass could come out, but sadly as time goes on there is much less support for our devices that are now multiple years old.
--
Edit: It's too bad Magisk (as far as I know) cannot be flashed with Flashfire. Using FlashFire I currently have a rooted device, latest stock firmware, xposed framework and knox 0x0... so I'm" knox check" future proof for now and continually hesitant towards installing a custom recovery. The note 3 will continue to be a great phone for at least a few more years

Categories

Resources