Database Info

Android Pay & custom rom

So I have tripped KNOX already. I'm using TWRP, Xstrolite 2.3.
I've tried unchecking superSU root and retrying. I've tried using root cloaker.
Is there an easy way to not have the bootloader unlocked? Or is it once I flashed TWRP, its unlocked forever.
Has anyone else been able to successfully use Android Pay? Post your experience

I'm in the same boat as you, I've tried disabling SuperSU and using root cloak as well to no avail. I've also got the Xtrestolite ROM running Unikernel V8 and I keep getting compatibility errors no matter what I seem to do. Could it be possible that Android Pay is detecting that KNOX is compromised and therefore disabling Android Pay? The only other thing I can think of is that running a custom ROM somehow prevents Android Pay from being compatible. I'm almost tempted to make a nandroid backup and temporarily install the stock ROM to see if that solves the problem.

derwreck said:
I'm in the same boat as you, I've tried disabling SuperSU and using root cloak as well to no avail. I've also got the Xtrestolite ROM running Unikernel V8 and I keep getting compatibility errors no matter what I seem to do. Could it be possible that Android Pay is detecting that KNOX is compromised and therefore disabling Android Pay? The only other thing I can think of is that running a custom ROM somehow prevents Android Pay from being compatible. I'm almost tempted to make a nandroid backup and temporarily install the stock ROM to see if that solves the problem.
Click to expand...
Click to collapse
Exactly.. Or that we're running a custom recovery too.
My thought is that the xstolite rom makes your phone be seen as a s6 edge.. Wonder if that affects things too. Though I've changed in the build prop back to 920T.
Would be a big bummer for us who've tripped Knox getting screwed out of android and Samsung pay. Others with rooted phones, have said it works.

tlxxxsracer said:
Exactly.. Or that we're running a custom recovery too.
My thought is that the xstolite rom makes your phone be seen as a s6 edge.. Wonder if that affects things too. Though I've changed in the build prop back to 920T.
Would be a big bummer for us who've tripped Knox getting screwed out of android and Samsung pay. Others with rooted phones, have said it works.
Click to expand...
Click to collapse
I also changed the build prop to reflect my SM-G920F model. I really wish I could get Android Pay to function on this device, I tripped KNOX with the full understanding that I was going to lose the ability to use Samsung Pay but never did I imagine that using a custom ROM would cause me to compromise Android Pay as well. I purchased an international unlocked model of the S6 so naturally, the bootloader was unlocked from the factory, I don't know if having an unlocked bootloader necessarily causes you to lose Android Pay. It either has to be due to the fact that we're running a custom ROM, custom recovery, or because KNOX is tripped and it's preventing AP to run like it should.

Try installing the stock rom for your phone. Then under supersu simply uncheck root and see if adding the cards work

I have it running and got my bank card added haven't had a chance to use it though. I'm using TWRP on WanamLite, Adam kernel, with Xposed and a whole lot of stock apps deleted including KNOX and private mode. All I did was unroot, install, AP, root, profit. I'm guessing its something missing from XtreStoLite.
Sent from my SM-G920F

Infekxion said:
I have it running and got my bank card added haven't had a chance to use it though. I'm using TWRP on WanamLite, Adam kernel, with Xposed and a whole lot of stock apps deleted including KNOX and private mode. All I did was unroot, install, AP, root, profit. I'm guessing its something missing from XtreStoLite.
Sent from my SM-G920F
Click to expand...
Click to collapse
When you said you unrooted.. did you uncheck the root box in SU app or uninstalled all together and then reinstalled?

Full unroot under the Cleanup section
Sent from my SM-G920F

think its reading something in the buildprop similar to how google wallet did.
i also tried modifying a few things in build prop to show official firmware nomenclature to no avail.

Infekxion said:
Full unroot under the Cleanup section
Sent from my SM-G920F
Click to expand...
Click to collapse
After you did full unroot. did you reboot? and to reinstall root, you flashed zip again? or what

After unrooting within SU app I just activated my card then reflashed the zip in recovery.
Sent from my SM-G920F

wouldn't let me set it up on my g920a rooted with custom rom at first.
all i did was go to my super su app from chainfire disabled root and without reboot went back into android pay after i closed it and it let me set up my cards from my Google wallet and a new one. then i went back to the su app and enabled su again.

rob219 said:
wouldn't let me set it up on my g920a rooted with custom rom at first.
all i did was go to my super su app from chainfire disabled root and without reboot went back into android pay after i closed it and it let me set up my cards from my Google wallet and a new one. then i went back to the su app and enabled su again.
Click to expand...
Click to collapse
What rom are you on?
Sent from my SM-G920F

Infekxion said:
What rom are you on?
Sent from my SM-G920F
Click to expand...
Click to collapse
XtreStoLite 1.5 on att

So has anyone got this working on XtreStoLite 2.3 ? Maybe just something that needs to be added to the rom?

Mrzoops said:
So has anyone got this working on XtreStoLite 2.3 ? Maybe just something that needs to be added to the rom?
Click to expand...
Click to collapse
So i did a fresh install but with Tyrannus rom 5.1, it runs the same base as Xstolite (I believe)
I got android pay working on tyrannus rom 5.1
maybe try backing up your current setup, wipe and flash the rom and first thign you do is try android pay and see if it works. Thats what I did on the rom im running now

I got it working on Tyrannus as well...briefly...although I am not sure how I did it.
Currently on XtreStoLite 2.3, using Xposed + No Device Check and an app called SafetyNet Helper...it says my device is good to go, but Android Pay won't work still.
I hope someone is able to pinpoint what prevents it from working and how to spoof it. I tend to have my phone in my hands a lot more than my wallet.

K, got it working. Fresh install of Tyrannus 5.1, did NOT install Xposed. Immediately turned SU off after 1st boot, before updating Google Play Services. Was then able to activate Android Pay and add cards.
Update 20150924: tried to use it at McDonalds for tap and pay. Android Pay started when tapped but never completed the transaction and I had to use my card.

How can I root and keep S Health?

I have the Exynos S7 Flat (G930FD) and I'm wanting to root it.
I've done this before about a year ago, but then I ended up getting a new device.
Since then, apparently SHealth now requires KNOX, which rooting will trip.
Is there any way I can bypass this? Perhaps a custom ROM or something? I know there used to be an Xposed module that restored private mode and something else, but I don't think it works anymore.
Basically I want to have root access as well as to be able to use S Health.

FallenArchangel7 said:
I have the Exynos S7 Flat (G930FD) and I'm wanting to root it.
I've done this before about a year ago, but then I ended up getting a new device.
Since then, apparently SHealth now requires KNOX, which rooting will trip.
Is there any way I can bypass this? Perhaps a custom ROM or something? I know there used to be an Xposed module that restored private mode and something else, but I don't think it works anymore.
Basically I want to have root access as well as to be able to use S Health.
Click to expand...
Click to collapse
Remove s health and install like a normal app a older version.
Enviado do meu SM-G930F através de Tapatalk

Basically, what vladmir said. S-Health disables services if you're rooted starting from version 5, so any previous versions will not have this problem. Just Google S-health APK 4.9 or something like that, and install.

https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306 Works well thanks to CuBz90

FallenArchangel7 said:
I have the Exynos S7 Flat (G930FD) and I'm wanting to root it.
I've done this before about a year ago, but then I ended up getting a new device.
Since then, apparently SHealth now requires KNOX, which rooting will trip.
Is there any way I can bypass this? Perhaps a custom ROM or something? I know there used to be an Xposed module that restored private mode and something else, but I don't think it works anymore.
Basically I want to have root access as well as to be able to use S Health.
Click to expand...
Click to collapse
I'm running Sheath on multiple devices all with Rooted Custom Roms that are AOSP / LineageOS based....
The interesting thing is that Sheath won't run on a Stock Rooted TW Rom
Sent from my SM-G930W8 using Tapatalk

shaggyskunk said:
I'm running Sheath on multiple devices all with Rooted Custom Roms that are AOSP / LineageOS based....
The interesting thing is that Sheath won't run on a Stock Rooted TW Rom
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
It works just fine on Marshmallow, but if you upgrade to Nougat then you need a custom ROM to make it work.
Removing it and installing it as a non-system app doesn't seem to change anything, and installing an older version didn't help me either.
I've downgraded to 6.0.1 so it doesn't really affect me any more though.

It is very simple to make SHealth working.
First root your device with Magisk using this thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Magisk is able to hide itself from a lot of apps, which won't run if your phone is rooted (i.e. Pokemon go, Mario run...)
If Magisk won't help you then:
install file explorer, it can be ES file explorer,
enable root explorer option (in ES file explorer)
go to /system directory
edit file build.prop
Look for ro.config.tima=1 and change the value to 0
reboot phone and now SHealth will work perfectly

e-fuse blown S8+

Hi all,
I am writing to ask for advice on what the next step should be with my S8+. I flashed TWRP and then SuperSu, made a huge fail because I voided the warranty by tripping Knox (0x1), there is no going back. The thing is that I do not care about Samsung Pass or Samsung Pay, I want the other apps not to detected that my phone is rooted, e.g. bank apps and Google Playstore to let me through the safenet, and etc.
I decided to wipe SuperSu and unroot completely the phone, but with no avail. TWRP throws an error when flashing Magisk, that the ROM is modified, fair enough. My next step was to flash a stock ROM, but Odin throws an error after "cm.bin" saying that it failed. Could it be possible that is it due a possible older ROM? And it interprets it as a downgrade?
My phone in question is SM-G955F, with the latest software update, unlocked.
Any ideas? Thanks in advance :good:
EDIT: Okay, found the solution, uploaded custom ROM with same version of build number to internal storage, flashed with TWRP and everything is working flawlessly. The ROM was "Alexega".
Banking apps working as well, used hide function from Magisk.
Hope this helps everyone who has this problem.

samsung sm-a520w stuck with knox and samsung pass saying phone rooted while it is not rooted.

my phone got flashed with custom rom and since then my samsung pass tries to work but as soon as it tries to fill passwords it says my phone is rooted and refuses to proceed.
when i go to knox in security it refuses to switch on.
so i cannot use any of the stuff linked to samsung for this and i have tried all kinds of solutions to try to fix, flashed different roms, magisk, even wiped with odin and all has pretty wel been tried and finally went back to factory android 8, so this includes samsung tied apps to it and i cannot use samsung services since the samsung pass says my phone is rooted, so i wish to fix it but finaly i wonder if it would just be better to change my rom and go with lineage 16.1 for my sm-a520w, but cannot find copy of it for an official version.
i would prefer to fix my phone and return back to how it was before i flashed custom rom on it but i cannot seem to be able to fix knox and the false fact of samsung pass describing my phone rooted while it is not.
so can anyone help me with all this please be kind and help me fix or get rid of these problems, joel.

Back to Android after almost a decade. Need some clarification.

Hi,
I've been away from messing about with android phones from almost a decade. A lot has changed so far. There is now so many different things associated with rooting your phone, and I was hoping someone could clear some stuff up for me.
1. Will unlocking the bootloader itself cause some issues with using banking apps or raise some red flags with other apps ?
2. Some ROMs use their custom recovery for flashing ROM to keep the encryption intact. They say flashing with magisk or twrp will break encryption. What encryption are they talking about ? And if encryption is indeed broken, what problems will that cause ?
3.If the phone is rooted, and custom rom installed, are there magisk modules, or any other way to hide it and use the phone normally ? You used to able to hide root on your phones back then.
Thanks
BB

BisonBro said:
Hi,
I've been away from messing about with android phones from almost a decade. A lot has changed so far. There is now so many different things associated with rooting your phone, and I was hoping someone could clear some stuff up for me.
1. Will unlocking the bootloader itself cause some issues with using banking apps or raise some red flags with other apps ?
2. Some ROMs use their custom recovery for flashing ROM to keep the encryption intact. They say flashing with magisk or twrp will break encryption. What encryption are they talking about ? And if encryption is indeed broken, what problems will that cause ?
3.If the phone is rooted, and custom rom installed, are there magisk modules, or any other way to hide it and use the phone normally ? You used to able to hide root on your phones back then.
Thanks
BB
Click to expand...
Click to collapse
1) yes
2) not sure, I've never seen anything about this question.
3) In the past, hiding root wasn't that difficult, now it is significantly harder, if it can even be done at all on modern devices. I guess it depends the specific device and android version question. I see many users looking for a way to hide root, I don't recall any of them finding a solution.