Database Develop

SuperSU and SafetyNet / Android Pay

This is the place to discuss anything and everything related to SuperSU and SafetyNet / Android Pay.
To clarify, I am not currently actively doing any development on having SuperSU pass SafetyNet detection, or having Android Pay work; the same way I put no effort into beating other root detection methods such as various enterprise security tools.
In case any SuperSU-rooted device passes SafetyNet, that is a bug in SafetyNet, not a feature of SuperSU.
While I may not agree with Google's stance, I'm not about to go messing with payment systems. Is it possible though? Probably yes.
This thread has been created because you guys simply cannot stop talking about this, so these posts can now go here, where I don't ever have to see them.

Will v2.50 cause Android Pay not to work in 6.0? If so, I am guessing there is no way around it?

0.0 said:
Will v2.50 cause Android Pay not to work in 6.0? If so, I am guessing there is no way around it?
Click to expand...
Click to collapse
Root is a no no with android pay and I think custom ROMs are also out at the moment
Sent from my A0001 using Tapatalk

Pure Drive GT said:
Hey, thanks for your continued support for root on Android, was just wondering, is google making it harder to achieve decent root privileges, as in they don't want rooted devices or are they just unrelatedly changing up things which forces you guys to adapt?
On another note, is there any progress on root without the modded boot? This is by no means an ETA, just wanted to know if you think it's possible or the situation looks rather dire.
Thanks again for your many efforts!
Click to expand...
Click to collapse
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.

mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
Many banking and financial apps restrict access on rooted devices; it's not just Google.
It makes sense in some ways: root access allows running things in the background to either circumvent, monitor, or interrupt program transactions. They're being paranoid, and I don't blame them.
I don't like the Google Pay concept (or Apple's either); like every other encryption or security system, it's destined to eventually be hacked.

mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
Yep, I was able to add my debit card but not credit.
VZW LG G4

mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
http://www.androidpolice.com/2015/0...hy-android-pay-doesnt-support-rooted-devices/

shaggyskunk said:
Yet the Note 5 has been rooted for at least a couple of weeks
Click to expand...
Click to collapse
On Lollipop... And you also have to unlock your bootloader to do that, right? If yes, then you will trip the KNOX, and that mean you will loose some of your device functionality (Samsung Pay for example), without option to take it back. On the Nexus on the other hand, when you want to use Android Pay on Nexus, you can restore your phone to completely stock condition, without any trace of previously used root.
Also, all of this is completely irrelevant to carried device users, since they have a locked bootloaders.

Srandista said:
On Lollipop... And you also have to unlock your bootloader to do that, right? If yes, then you will trip the KNOX, and that mean you will loose some of your device functionality (Samsung Pay for example), without option to take it back. On the Nexus on the other hand, when you want to use Android Pay on Nexus, you can restore your phone to completely stock condition, without any trace of previously used root.
Also, all of this is completely irrelevant to carried device users, since they have a locked bootloaders.
Click to expand...
Click to collapse
I believe that it's only at&t and Verizon that locks the bootloader - And none in Canada and many other Countries.
Sent From my SM-N910W8 Running SlimRemix V5.1

Had an interesting event, on 2.52.
I unchecked "Enable Superuser" in Settings, to attempt to use Android Pay (Android Pay still wouldn't work). Then, when I rechecked "Enable Superuser", the re-installation of the binary failed, and I was prompted to reboot to try again. However, then I got a boot loop (never even got the opportunity to enter my encryption code). The only way I was able to boot was to re-flash the modified boot.img and re-install SuperSU from the zip (no idea whether both steps were necessary).
I have a Marshmallow Nexus 6, encrypted. For what it's worth, I was previously rooted on 5.1.1, and, after updating to 6.0 and until I re-rooted, I always got a "Your device is corrupt" message on startup, despite being all stock.

NYZack said:
Had an interesting event, on 2.52.
I unchecked "Enable Superuser" in Settings, to attempt to use Android Pay (Android Pay still wouldn't work). Then, when I rechecked "Enable Superuser", the re-installation of the binary failed, and I was prompted to reboot to try again. However, then I got a boot loop (never even got the opportunity to enter my encryption code). The only way I was able to boot was to re-flash the modified boot.img and re-install SuperSU from the zip (no idea whether both steps were necessary).
I have a Marshmallow Nexus 6, encrypted. For what it's worth, I was previously rooted on 5.1.1, and, after updating to 6.0 and until I re-rooted, I always got a "Your device is corrupt" message on startup, despite being all stock.
Click to expand...
Click to collapse
Root doesn't have to be enabled for pay to fail. Any time the system partition is modified pay will not work. There was an xda news article on it. A quick Google search involving Android pay and root should find it.

Lrs121 said:
Root doesn't have to be enabled for pay to fail. Any time the system partition is modified pay will not work. There was an xda news article on it. A quick Google search involving Android pay and root should find it.
Click to expand...
Click to collapse
I also found that having an unlocked bootloader will stop Pay working. When MM released I decided to go fully back to stock but kept the bootloader unlocked so I could flash MM. Pay still failed, so I've given up and gone rooted again.
Sent from my Nexus 6 using Tapatalk

Ch3vr0n said:
@Chainfire if you actually are able to pull off fully working stable root WITHOUT modifying the /system does that mean you MIGHT have opened the door into having root AND still being able to get OTA's?
Click to expand...
Click to collapse
osm0sis said:
Yup, all you'd need to do is reflash stock kernel to pass the boot partition EMMC check, or, we could automate restoring the previous stock kernel, flashing the OTA and then injecting the new stock kernel with root after flashing (à la AnyKernel2 or MultiROM). So many exciting possibilities there where custom recoveries are concerned.
Click to expand...
Click to collapse
Chainfire said:
Honestly it's not so different from using FlashFire to flash re-flash system, then OTA, then re-root. But it is easier, yes.
Click to expand...
Click to collapse
This is indeed exciting. However, I noticed that @Chainfire posted this downside on Google+ :
Andrew Morykin 12:24
This should retain Android Pay, right?
Click to expand...
Click to collapse
Chainfire 12:58
+Andrew Morykin if it does, then it's by accident and not by design, and Android Pay will be updated to block it.
Click to expand...
Click to collapse
https://plus.google.com/+Chainfire/posts/aJbqUZ8PEP4
also, I was confused by this:
Chainfire said:
- I have not tested with encrypted devices
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63197935
Aren't
Nexus 6P / angler
angler-mdb08k-boot-systemless.zip
Click to expand...
Click to collapse
and
Nexus 5X / bullhead
bullhead-mdb08i-boot-systemless.zip
Click to expand...
Click to collapse
encrypted out of the box?

dabotsonline said:
This is indeed exciting. However, I noticed that @Chainfire posted this downside on Google+ :
Click to expand...
Click to collapse
How is that a downside?
It's exactly the same with every other form of root you will ever see. They don't want to support Android Pay (and some other stuff) on rooted devices. If we find a root that allows it, they will update their system to detect and block it. That cat and mouse game will not end as long as Google doesn't want Android Pay on rooted devices.
Maybe someone will make apps/modules that help circumvent this, but it certainly will not be me.
also, I was confused by this:
Aren't
Nexus 6P / angler
and
Nexus 5X / bullhead
encrypted out of the box?
Click to expand...
Click to collapse
Still can't test what I don't have.

russlowe73 said:
Factory images
Click to expand...
Click to collapse
So basically I have to go back to 100% stock using ADB, and then flash the new SuperSU stuff with any custom ROM? If so, what are the benefits of this other than getting Android Pay while rooted?

I'm not sure if anyone has specifically mentioned this, but Android Pay still works with this form of root on the Nexus 6!!

efrant said:
Starting with Android 5.0, OTA updates are now block-based rather than file-based, so any modification to the system partition will cause the OTA to fail, even mounting the system partition as r/w.
Click to expand...
Click to collapse
Just to add to this, it's a whole-partition /system patch OTA if the device launched with Lollipop or later, anything that launched with KitKat is still receiving the old file-based patch OTAs. Modifying Settings.apk would likely trip either method for a lot of OTAs though, since it's a pretty central component.
galaxyuserx said:
I use Galaxy s6 G9200 HK with Kernel compiled by me, but i have problem with root 5.1.1 and i think in future too 6.0
These root method is integrated in kernel source or i can integrate with those "boot.img systemless" my selfcompiled kernel?(repack boot.img with kernel compiled by me)
Is possible to work this new root method to android 5.1.1?
I have problem with gain root when i use kernel compiled by me ( STOCK kernel have too this problem BOOTLOOPs and FREEZEs on boot system) and i don't know how slove it :/
I found on chineese forums root integrated in boot.img it working good and isn't comunicat "KERNEL is not SEandroid enforced" but when i try integrate my kernel with this boot.img error with boot system :/
Click to expand...
Click to collapse
Yup, it's all ramdisk changes so should be workable on any version of Android. Chainfire left instructions outlining the ramdisk changes in the WIP thread if you want to give it a try.
phishfi said:
I'm not sure if anyone has specifically mentioned this, but Android Pay still works with this form of on the Nexus 6!!
Click to expand...
Click to collapse
Yup, seems to be the case with most banking and root-detecting apps... for now.

Can someone with the non-system SU use this app: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground and post the results?
This app is supposed to do the SafetyNet checks cleanly, the same way Android Pay does them.
Would be interesting to see if it succeeds on devices with this new supersu version.

secguy said:
Can someone with the non-system SU use this app: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground and post the results?
This app is supposed to do the SafetyNet checks cleanly, the same way Android Pay does them.
Would be interesting to see if it succeeds on devices with this new supersu version.
Click to expand...
Click to collapse
Just ran it and it passed.

Went ahead and installed su on a stock nexus 5, so far working well, android pay does not work but that was me being stupid and changing the host file and dpi before setting it up
I do notice a little input lag after this, not enough to even make me consider removing root, but it is noticeable, anybody else with this?

January Security Patch

I am currently using CM13 with December patch, but the January patch fixed a high priority exploit. I do not want to upgrade to Nougat just yet because I want to keep the Xposed framework. Is there any community build for CM13 with January Patch? Or is there an alternative ROM to switch to that will continue to update Marshmallow? And if so, will I be able to flash it without a data wipe?

ExpertMC said:
I am currently using CM13 with December patch, but the January patch fixed a high priority exploit. I do not want to upgrade to Nougat just yet because I want to keep the Xposed framework. Is there any community build for CM13 with January Patch? Or is there an alternative ROM to switch to that will continue to update Marshmallow? And if so, will I be able to flash it without a data wipe?
Click to expand...
Click to collapse
You should ask Neo from Resurrection Rom if he's still building for M
Edit: Apophis9283 made a build, check his afh mirror at his
Singularity kernel thread, may he merged the January patch

coremania said:
You should ask Neo from Resurrection Rom if he's still building for M
Edit: Apophis9283 made a build, check his afh mirror at his
Singularity kernel thread, may he merged the January patch
Click to expand...
Click to collapse
I thought Singularity kernel is no longer under active development.

ExpertMC said:
I am currently using CM13 with December patch, but the January patch fixed a high priority exploit. I do not want to upgrade to Nougat just yet because I want to keep the Xposed framework. Is there any community build for CM13 with January Patch? Or is there an alternative ROM to switch to that will continue to update Marshmallow? And if so, will I be able to flash it without a data wipe?
Click to expand...
Click to collapse
From what I read about that patch, Nexus 6 got it back in November and the 6p just got. I believe we been had this patch. Let me find where I read that.[
Here goes the article.
http://www.androidauthority.com/google-patches-exploit-nexus-6-6p-742048/
If you are running a November or December security update, your already patched it seems.

christianpeso said:
From what I read about that patch, Nexus 6 got it back in November and the 6p just got. I believe we been had this patch. Let me find where I read that.[
Here goes the article.
http://www.androidauthority.com/google-patches-exploit-nexus-6-6p-742048/
If you are running a November or December security update, your already patched it seems.
Click to expand...
Click to collapse
Thanks for the info, but I would still like to know my options for the future.

coremania said:
You should ask Neo from Resurrection Rom if he's still building for M
Edit: Apophis9283 made a build, check his afh mirror at his
Singularity kernel thread, may he merged the January patch
Click to expand...
Click to collapse
No he didn't include the January patch. It's stock RR with November security patch. He also added a commit to fix verizon visual voicemail (which now works) and to stop battery issues below 40%
If you really want January security patch on MM my only guess would be Mokee. Google search Mokee Shamu.
It's funny being concerned so much about security patches, when you're running a rooted phone with an unlocked bootloader lol I wouldn't stress too much over it.

ExpertMC said:
... And if so, will I be able to flash it without a data wipe?
Click to expand...
Click to collapse
Flashing another type ROM generally needs wiping data.
You can try to keep the data but there could be bootloop or forced closing apps.

Dopamin3 said:
....
It's funny being concerned so much about security patches, when you're running a rooted phone with an unlocked bootloader....
Click to expand...
Click to collapse
I agree with you for the 'stressing' part, but one of the advantages of rooting for me is that root access allows installing a firewall and blocking ads with a hosts file.
Rooting can give us more security.[emoji1]

Rooting for that simply limits how much you're tracked. There are non-root methods of reducing your tracking. Rooting, as much as we may want it, is a security hole. This is why every device manufacturer - including Google - either does not recommend it or locks the bootloader to prevent it.

Hmm; I said 'one of the advantages' another important thing is the use of layers.
As long as Google only offers white UI rooting is a must.

Except your very last sentence says "rooting can give us more security." That is absolutely wrong, thus my comments.
I do agree that theming is a reason to root, along with ad blocking. Root however is still a security hole.

Strephon Alkhalikoi said:
Except your very last sentence says "rooting can give us more security." That is absolutely wrong, thus my comments.
Click to expand...
Click to collapse
Is it though? What about instances of things like AdAway which edit your hosts file to block advertisements and potentially malicious websites? What about AppOpsXposed which can revoke permissions for apps even if on stock it forces you to accept and use those permissions for the app to work? How about uninstalling pre-installed carrier garbage like CarrierIQ or system apps which could invade privacy and report things either to your carrier or the app manufacturer?
Rooting doesn't give you more security. But rooting can give you more security.

Dopamin3 said:
Rooting doesn't give you more security. But rooting can give you more security.
Click to expand...
Click to collapse
A rooted device is a compromised device, period. In order to prevent a device from being compromised, on Linux you never run as root and execute commands via sudo. It's dangerous to run as root, yet on Android we have no choice as Android does not have the sudo command. Thus, a rooted device renders any security measures useless as root has total control over everything. The loss of security is why manufacturers do not support root, with some manufacturers taking steps to prevent it.
Using your example, malware on an untouched device is limited to infecting your data on the internal storage. On a rooted device that same malware can infiltrate the system and do damage that can only be fixed by a factory reset or worse, flashing the entire system again. By rooting, you open the door to more severe attacks than by not rooting.
Some of us on this site understand the risks involved with rooting, but every day we have noobs coming to this site trying to root for s***s and giggles, and neither thinking about or caring about the consequences. To them, it's all fun and games until some rogue app steals their information because their device is rooted, and then they come here and ask us to fix their screwups.
Rooting is not a game, but serious business. One that could cost you a lot more than you think.

Strephon Alkhalikoi said:
Using your example, malware on an untouched device is limited to infecting your data on the internal storage. On a rooted device that same malware can infiltrate the system and do damage that can only be fixed by a factory reset or worse, flashing the entire system again.
Click to expand...
Click to collapse
Okay, so what about the dirty cow exploit (and potentially others)? This would allow full root access to a device EVEN if it was unrooted. Just because you're running stock, unrooted, BL locked doesn't make it so you can never get affected by an exploit that achieves root access and totally wrecks your device.
I guess it just comes down to the user. I don't use an antivirus on any of my Windows PCs (gasp!) but have I ever been infected or compromised in any manner? No. I'm an IT technician and use common sense. Any files I'm suspicious of I will scan on virustotal.com before executing them. On Android I don't load "sketchy" apps from the Play Store and don't sideload APKs (except Kernel Adiutor-Mod). I've never been compromised on Android and while I can't guarantee it, it's unlikely that it will happen even with my rooted device. I guess I'll just agree to disagree because I do see your points.

You claim to see my points, but as an IT professional, you should not be discounting them simply because you haven't encountered them. I don't know if you have used Linux in your IT work, but Linux has always required the root account have a password. Dirty Cow wouldn't have been able to do much if root on Android required a password.
It is a proven fact that root compromises the device's security. Windows users likely wouldn't be familiar with the Linux security model as their user accounts always ran with admin privileges by default. That is one reason - the other being popularity - why antivirus and anti malware programs are so common on Windows, yet virtually nonexistent on Linux.

Strephon Alkhalikoi said:
.....
It is a proven fact that root compromises the device's security..,,.
Click to expand...
Click to collapse
Dopamin3 said:
.... Just becaus I guess I'll just agree to disagree because I do see your points.
Click to expand...
Click to collapse
It wasn't my intention to start a discussion about security.
It can't be denyed that root access is a security issue. But I wouldn't have a Nexus phone when I could not:
- install a firewall,
- change the hosts file for ad-blocking,
- change the theme to dark (eyes),
- flash a kernel (better battery life),
- remove bloat ware,
- block/remove services I do no want/use,
- disable NFC, no pay apps,
- unencrypt for a bit more performance.
I prefer to configure devices myself instead of Google etc. I am aware that comfort and performance have a price.

@NLBeev: I believe @Dopamin3 and I are actually on the same page here. It's only a difference in perception he and I have as to the seriousness of it all. Neither of us were questioning your choices, because all of us have rooted our devices. We are I believe all aware of the risks involved. But the noobs who come in and root for the wrong reasons might benefit from the discussion.

Strephon Alkhalikoi said:
@NLBeev: I believe @Dopamin3 ...the noobs who come in and root for the wrong reasons might benefit from the discussion.
Click to expand...
Click to collapse
Fully agree. [emoji106]

Is it worth it to root the device??

As the title suggests the question is it wise to root the tab now like what is scenario of custom roms and kernels??
Please reply soon.....

depend on your device since the development of custom rom are less for tab s2. i dont event root any of my device nowadays.

edan1979 said:
depend on your device since the development of custom rom are less for tab s2. i dont event root any of my device nowadays.
Click to expand...
Click to collapse
So what do you say ultimately should I root with Magisk or wait..

Androbots said:
So what do you say ultimately should I root with Magisk or wait..
Click to expand...
Click to collapse
Not a big fan of Magisk but I believe it is worth it to root any device. Granted, you are voiding your warranty and risking losing out if your device gets bricked or fails for some reason. But I like having the control and added access that rooting gives me. Plus the custom ROMs usually provide less bloat and added features that make them preferable over stock.
In the end it is a matter of personal preference.

pastorbob62 said:
Not a big fan of Magisk but I believe it is worth it to root any device. Granted, you are voiding your warranty and risking losing out if your device gets bricked or fails for some reason. But I like having the control and added access that rooting gives me. Plus the custom ROMs usually provide less bloat and added features that make them preferable over stock.
In the end it is a matter of personal preference.
Click to expand...
Click to collapse
Actually i am a bit confused.... My warranty has gone since March 17 and I am just thinking if the device will get any more updates like the update to 7.1 official ohh... Btw i am using a tab s2 T710 (2015).. Thanks for the tips... ?
Will knox create any probs when I root?

Androbots said:
Actually i am a bit confused.... My warranty has gone since March 17 and I am just thinking if the device will get any more updates like the update to 7.1 official ohh... Btw i am using a tab s2 T710 (2015).. Thanks for the tips...
Will knox create any probs when I root?
Click to expand...
Click to collapse
It will detect the root but it doesn't cause any issues. However if Samsung does release another update (don't hold your breath waiting for it), you might not be able to apply it through OTA. Also, be sure to search for and use the correct method of rooting for your device. Trying to root incorrectly will give you nothing but problems and may brick your device. I have the T813 9.7" so I can't direct you to the procedure for your device.
Bottom line - read, read and read some more and be certain you understand the procedure and risks before you take the next step.

pastorbob62 said:
It will detect the root but it doesn't cause any issues. However if Samsung does release another update (don't hold your breath waiting for it), you might not be able to apply it through OTA. Also, be sure to search for and use the correct method of rooting for your device. Trying to root incorrectly will give you nothing but problems and may brick your device. I have the T813 9.7" so I can't direct you to the procedure for your device.
Bottom line - read, read and read some more and be certain you understand the procedure and risks before you take the next step.
Click to expand...
Click to collapse
I just rooted my tab today.. With Magisk.. Works well

Androbots said:
I just rooted my tab today.. With Magisk.. Works well
Click to expand...
Click to collapse
Awesome! Glad to hear it. :good::good::good::good::good:

Why do people say it's "dangerous" to root a Huawei phone?

I've seen this in a few places now - is rooting - or having a rooted - Huawei phone more dangerous than any other kind? Are they easier to brick? If so, why?

Nope. Just as dangerous as any other device. The problem cones from using 3rdvparty software to do such things rather than just doing it yourself. The only difference is that you need to generate a device specific code from Huawei. Nothing big. Risks are imposed when doing anything outside of stock stuff but those issues are usually consequence of user error

I think it's said primarily for two reasons. First there's no TWRP, so recovering back to stock is more complicated and involves, at minimum, being able to get back to Fastboot. Second, people tend to freeze or uninstall system apps that they don't understand. Huawei, reputationally, can brick if you freeze the wrong system app. Personally, I haven't experienced that, and have frozen (as opposed to uninstalled) a bunch, but I admit that I'm proceeding more cautiously.
Also, some of the earlier warnings were before @mankindtw's rooting method -- before then the only available root cost you your AI and your themes (although the latter could be reloaded with some complexity). That's no longer the case -- the Magisk root doesn't delete/affect either. Nor, if you install the zip in his OP, does it blow up SafetyNet (although xPosed always will).

Hi, do you mind posting which zip file you flashed? Do you have the mate 10 pro version? Will bank apps after rooting still work?

mefistofelis said:
Hi, do you mind posting which zip file you flashed? Do you have the mate 10 pro version? Will bank apps after rooting still work?
Click to expand...
Click to collapse
If they need to pass safety net you need to use Magisk, use the one in here:
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814

Question rooting

is it possible to root my galaxy s21u? if possible how should it be done and is it safe to do so?

seancannery88 said:
is it possible to root my galaxy s21u? if possible how should it be done and is it safe to do so?
Click to expand...
Click to collapse
I'm not sure if Exynos can be root as of now...If you are on the SD version, there are some posts here that show how to unlock the BL, install magisk and SU...but honestly, it's best to wait until some foolproof method is out...whatever be the case, you will lose Knox and other Knox related stuff

Exynos can be rooted I believe, but ask yourself why you want or need to root your phone.
I've had various Android phones since around 2009, and this is the first Android device I've owned that I haven't immediately rooted, and don't immediately see the need to. Previously, I mainly rooted because I wanted XprivacyLUA, Viper4Android and AFWall (amongst other things like Titanium Backup and Root Explorer but they're the main three). However, in the 3 weeks I've had this phone I've not really missed them. I use Netguard for a firewall, and the DAC appears to be good enough to not really need Viper. XPrivacy is a miss, but not one I can l can't deal with.
I'm not ruling out rooting it at some point in the future. I've just decided it's not required right now. Especially as I've started using Samsung Pay and that would immediately and permanently be lost once Knox is tripped.