Database Users

Android Pay - Root, Unroot?

I am interested in using Android Pay but understand the phone cannot be rooted.
I am curious I am would be able to Root for whatever purposes, and the unroot for day to day use to retain the ability to use Android Pay. I am willing to stay on the stock rom and install if needed.
Thanks

MoreGone said:
I am interested in using Android Pay but understand the phone cannot be rooted.
I am curious I am would be able to Root for whatever purposes, and the unroot for day to day use to retain the ability to use Android Pay. I am willing to stay on the stock rom and install if needed.
Thanks
Click to expand...
Click to collapse
I've seen threads that say to disable supersu, add cards, and reenable supersu and it should work. However, I tried this on the 6 and it never worked. As of now there doesn't seem to be surefire way to get Pay to work while rooted. If xposed is made for 6.0 a root cloak should work, but I can't be sure. Others may be able to provide addition info on this.

theycallmerayj said:
I've seen threads that say to disable supersu, add cards, and reenable supersu and it should work. However, I tried this on the 6 and it never worked. As of now there doesn't seem to be surefire way to get Pay to work while rooted. If xposed is made for 6.0 a root cloak should work, but I can't be sure. Others may be able to provide addition info on this.
Click to expand...
Click to collapse
What if you root your phone, apply an adblock, change your dpi, etc....and then unroot, leaving your changes intact. Then will android pay work?

ArkAngel06 said:
What if you root your phone, apply an adblock, change your dpi, etc....and then unroot, leaving your changes intact. Then will android pay work?
Click to expand...
Click to collapse
Some reports say the a DPI change causes AP to fail.
As far as the other, that should work fine.

Can anyone confirm this..? No Adblock is killing me.

I'm curious about this too. I've read that with nexus devices your have to lock the boatloader again as well as unroot. But then I've also seen people say these root then unroot tricks only work for adding cards, not for actually paying with them. I really like the idea of Android pay and hope nfc payments spread more, but everyday I ask myself "how many stores have nfc payment today vs how many things could I do with root today..." Not sure how long I can hold out.

It would be nice if we had a definitive answer or steps on how to add Android Pay but keep root. I'm using a systemless root now but have modified mixer_paths to increase headphone volume. I'm thinking about flashing stock boot then trying to add a card then going back to the modified boot.

Guys - you cannot root with the /system way (the traditional way).
Modifying anything in /system will cause Android Pay to fail. That explains editing hosts, DPI, build.prop, etc. /system has to be clean otherwise when you go to actually pay it will fail but allow you to add your payment methods.

new root method
http://www.androidpolice.com/2015/1...d-root-without-touching-the-system-partition/
http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2
New root method that does not modify the /system

exSD said:
Guys - you cannot root with the /system way (the traditional way).
Modifying anything in /system will cause Android Pay to fail. That explains editing hosts, DPI, build.prop, etc. /system has to be clean otherwise when you go to actually pay it will fail but allow you to add your payment methods.
Click to expand...
Click to collapse
Are you saying even if you edit DPI, Android Pay will not work ? Can anyone confirm this ?

Good article on just what SafetyNet (Googles tamper checking for Android pay) does behind the scenes:
https://koz.io/inside-safetynet/
About 1/3 the way down the page it details the checks that are run to determine if the device has been tampered
Pretty interesting stuff, with a fairly important point: it does not reside on the actual device, its actually pulled down and run real-time when you fire up Android Pay. The interesting part about it is that could allow Google to disable some of the checks, to allow for things like Root, DPI changes, etc to actually NOT list the device as tampered. Will they? Who knows.

I have root and Android pay working fine. I've mad purchases multiple times this way
Sent from my Nexus 6P using Tapatalk

trebills said:
I have root and Android pay working fine. I've mad purchases multiple times this way
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You have systemless root.
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
kolyan said:
Are you saying even if you edit DPI, Android Pay will not work ? Can anyone confirm this ?
Click to expand...
Click to collapse
That is what I'm saying.
You edit DPI by modifying your build.prop file. That file resides in /system.
If you make any change to /system, Android Pay will NOT work. Period. You can root cloak/add card/unroot after editing DPI/etc but when it comes time to actually pay, the SafetyNet will fail because you've modified your /system.

kolyan said:
Are you saying even if you edit DPI, Android Pay will not work ? Can anyone confirm this ?
Click to expand...
Click to collapse
Confirmed.
Here's the testing ive done:
Unlocked bootloader...AP works entirely.
rooted...AP will not allow you add a card, or process a transaction. If you have a card added prior to root, AP will not allow a transaction.
Disable root in SuperSu...AP will work entirely after you disable root and reboot your phone with root disabled. If you enable root again, AP will continue to work until you reboot.
With a modded DPI/no root...AP will not process a transaction.
Modified hosts file via Adfree/Adaway-root disabled...adblocking with a modified hosts file has no effect on AP
Click to expand...
Click to collapse
Those tests are all completed transactions at a terminal.

exSD said:
Guys - you cannot root with the /system way (the traditional way).
Modifying anything in /system will cause Android Pay to fail. That explains editing hosts, DPI, build.prop, etc. /system has to be clean otherwise when you go to actually pay it will fail but allow you to add your payment methods.
Click to expand...
Click to collapse
This is not universally true. I tested/verified a working method for using AndroidPay on a Sprint LG G3 that had a modified /system partition. Obviously that's a completely different phone, but it's one of the first things I'll be testing once my Angler comes in on Monday. Same method works for enabling adding cards the same as making a purchase. Here's what worked for me.
I got it figured out as well and so here's my method. I honestly think, though, that its every man for himself out there on this and that what works for one is unlikely to work for another.
Mine does not use XPosed, I don't have it installed. Requires use of SuperSU as your superuser manager and be currently rooted. I am running BarePapA-TE_V3 and NavelA-V1.6.
Download RootCloak Plus (Cydia) and Cydia Substrate from the Play Store.
Open Substrate. It tells me "Note: something about your device made it impossible for Substrate to perform its internal safety check; can you please contact saurik via e-mail?". Doesn't seem to effect anything.
Open RootCloak Plus (Cydia). Here you are going to be adding apps to a list of ones you don't want knowing you have root. There are a bunch of defaults already which you can leave. Add AndroidPay (com.google.android.apps.walletnfcrel). Now beyond that, I went ahead and added a number of other Google Apps and be certain any of them are required, but its what I did. I added the new Wallet app, Google Play Services, Play Store, Google Partner Setup, Google Account Manager, and Google Services Framework. Basically, my reasoning was that given the commitment to blocking rooted devices from using AndroidPay, it'd be useful to cloak any of the other financial apps and core GAPPS as well . . . because who knows how they are checking for root?
Reboot device.
Open SuperSU and uninstall superuser.
Reboot device. AndroidPay now works, buy yourself an Oreo McFlurry with your phone you clever hacker.
Obviously, your rooted apps won't work. So, if you want them back you will have to open SuperSU and reinstall superuser. That is going to break AndroidPay. Each time you want to use it again, you have to repeat the last two steps. So, there's the compromise . . . you can either leave your phone unrooted or have to reboot every time you want to use it.
Click to expand...
Click to collapse

cabbieBot said:
This is not universally true. I tested/verified a working method for using AndroidPay on a Sprint LG G3 that had a modified /system partition. Obviously that's a completely different phone, but it's one of the first things I'll be testing once my Angler comes in on Monday. Same method works for enabling adding cards the same as making a purchase. Here's what worked for me.
Click to expand...
Click to collapse
My phone is rooted in the normal way by flashing SuperSu.
If you change DPI on the phone it no longer passes a check of hardware configuration, so the device fails.
Other files have no effect. Hosts file does not describe HW so it doesn't matter.
Build.conf can be modified but not in areas that don't match the hardware.
I've had xposed installed after adding cards and added root cloak and had no isses.

I am rooted with system less root and android pay works fine. N6p angler.
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
kolyan said:
Are you saying even if you edit DPI, Android Pay will not work ? Can anyone confirm this ?
Click to expand...
Click to collapse
That's correct do not edit stock dpi or pay will not work /at least as far as adding cards anyway (tested).

Thanks. I guess no AP for me. I root only to edit built.prop

puritan007 said:
I am rooted with system less root and android pay works fine. N6p angler.
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
That's correct do not edit stock dpi or pay will not work /at least as far as adding cards anyway (tested).
Click to expand...
Click to collapse
Rooted with system less root and Android Pay works....are you referring to it works without disabling root and rebooting? Or it just works regardless?
Seems there are some posts saying it works as long as you reboot with root disabled, and others saying "it works" but need clarification of any process that needed to be done before using it.

chrisexv6 said:
Rooted with system less root and Android Pay works....are you referring to it works without disabling root and rebooting? Or it just works regardless?
Seems there are some posts saying it works as long as you reboot with root disabled, and others saying "it works" but need clarification of any process that needed to be done before using it.
Click to expand...
Click to collapse
With any root before 5.46 you had to Un root to add cards. With 5.46 system less I did nothing it just works how it should with no messing about

Need some help of a rare sort... deleted folders arent deleting!

Ive purchased the full version of No Bloat, trying to get things more manageable on my device.
There are things that are not removing, despite me telling them to.
in system/app/flipboarddebriefing/arm/<somefilename>.odex
this is a reminant of an app i have already removed...so i wanted to fully delete it... but it wont delete!! Root browser says it deleted, for a quick second... but the damn thing stays there.
i *am* rooted, i *have* removed system apps with other apps (at first uninstall master, but since ive discovered that wont recover properly on my device, im using nobloat now).
Why if i have root, and am using a root based browser, are things NOT removing as though i am not rooted??!? I downloaded root checker today, and yes i am in fact rooted successfully.... so what gives? i DONT understand this, not one bit.
Im on rooted but stock samsung galaxy s5 neo, with twrp recovery installed, and a full nandroid backup made. successfully.
I dont understand why some root features are going smooth while others are almost like in high school when deep freeze was installed on the library computers, where no matter what you did, next reset (or in my case, not even a reboot required!) things were exactly as they were *before* you messed wth them, things unchanged.
why is this happening to me?? i never did enable knox so it cant possibly be that... can it??
ETA i have tried going in through the file explorer in twrp... but even in there i cant access the system folder at all, let alone delete things. A few days ago, some things in another folder werent deleting, so i went into twrp and ultimately deleted them, and those did stay deleted.
I just plain dont understand. s2 = root = do whatever the heck you want. s5=root=well remove some apps for you but its remains will stay on your system, for-evvvv-errr.
is there some sort of build in deep freeze type app that i can go in and get rid of (some how, if it will let me, frig).

Can anyone help me with this? Still not working properly...
Sent from my SM-G903W using XDA-Developers mobile app

Pawprints1986 said:
Ive purchased the full version of No Bloat, trying to get things more manageable on my device.
There are things that are not removing, despite me telling them to.
in system/app/flipboarddebriefing/arm/<somefilename>.odex
this is a reminant of an app i have already removed...so i wanted to fully delete it... but it wont delete!! Root browser says it deleted, for a quick second... but the damn thing stays there.
i *am* rooted, i *have* removed system apps with other apps (at first uninstall master, but since ive discovered that wont recover properly on my device, im using nobloat now).
Why if i have root, and am using a root based browser, are things NOT removing as though i am not rooted??!? I downloaded root checker today, and yes i am in fact rooted successfully.... so what gives? i DONT understand this, not one bit.
Im on rooted but stock samsung galaxy s5 neo, with twrp recovery installed, and a full nandroid backup made. successfully.
I dont understand why some root features are going smooth while others are almost like in high school when deep freeze was installed on the library computers, where no matter what you did, next reset (or in my case, not even a reboot required!) things were exactly as they were *before* you messed wth them, things unchanged.
why is this happening to me?? i never did enable knox so it cant possibly be that... can it??
ETA i have tried going in through the file explorer in twrp... but even in there i cant access the system folder at all, let alone delete things. A few days ago, some things in another folder werent deleting, so i went into twrp and ultimately deleted them, and those did stay deleted.
I just plain dont understand. s2 = root = do whatever the heck you want. s5=root=well remove some apps for you but its remains will stay on your system, for-evvvv-errr.
is there some sort of build in deep freeze type app that i can go in and get rid of (some how, if it will let me, frig).
Click to expand...
Click to collapse
The reason why it keeps coming back is becoz some of the apps are PRELOADED by default and to get rid of them for good you need to go to the root of those apps.
Use any root explorer app
1. Check /preload/ folder..make sure you delete the apps there as well
2. Check /System/CSC/ and look for any /System/app/ and /System/priv-app/ and do the same as above.

Hmm... I'll give it a look, but I even had problems with deleting data from a user app in the same manner...
Eta, I have nothing in my preload folder at all.. At least not that root browser is seeing.
Tried Flipboard deleting the odex file again, still not working.
Any other suggestions?
Sent from my SM-G903W using XDA-Developers mobile app

Pawprints1986 said:
Hmm... I'll give it a look, but I even had problems with deleting data from a user app in the same manner...
Eta, I have nothing in my preload folder at all.. At least not that root browser is seeing.
Tried Flipboard deleting the odex file again, still not working.
Any other suggestions?
Click to expand...
Click to collapse
Which root/file explorer are you using?
EDIT: Ok I see you said Root browser.
Try another file explorer like ES file explorer

Reset Knox Counter or edit kernel or mod apk? Trying to get secure folder to work

I believe most people wanted to reset Knox counter because some Samsung app stop working.
Mod kernel to fake knox counter ain't easy isn't it? I didn't see any guide on XDA
I've been thinking for long time, lot of people know how to decompile and mod apk, why not just change the function so Secure Folder can work regardless of knox counter?
I want the secure folder to work so badly but I don't want to use third party apps. We need a hero to post a guide.

root Samsung Galaxy Note 3 SM-N9005 Android 5.0 - Secure method

Root Samsung Galaxy Note 3 SM-N9005 Android 5.0 - Secure method
I am looking for a safe, secure, foolproof method, from reliable source, from trusted person, with safe elements .
Without data leakage, IMEI theft, backdoors, viruses, ads, system modifications etc. Clean root.
Can you recommend something?
Best KNOX flag 0x0 and With the possibility of unroot.
Something simple and fast will also be an advantage - I am an amateur.
The only reason why I want to do a root of the phone is the security of my data and my privacy. A phone without a privacy manager like App Ops seems like a very dangerous solution. Firewall will also be useful.
Sorry for my English

sn3 said:
Root Samsung Galaxy Note 3 SM-N9005 Android 5.0 - Secure method
I am looking for a safe, secure, foolproof method, from reliable source, from trusted person, with safe elements .
Without data leakage, IMEI theft, backdoors, viruses, ads, system modifications etc. Clean root.
Can you recommend something?
Best KNOX flag 0x0 and With the possibility of unroot.
Something simple and fast will also be an advantage - I am an amateur.
The only reason why I want to do a root of the phone is the security of my data and my privacy. A phone without a privacy manager like App Ops seems like a very dangerous solution. Firewall will also be useful.
Sorry for my English
Click to expand...
Click to collapse
Search and read about "cf-auto-root"

Rooting may prevent certain banking type apps working as they see it as insecure .

Thank you very much for the help and information.
Unfortunately, "cf-auto-root" switches the KNOX flag. But it is more important that it is a secure source. Thank you very much.
I did not know about problems with banking applications. Thank you for the information.
If you have any other suggestions, let me know.

I THINK there was a way to root without tripping knox but it required having JB. Now that you are on LL I doubt you will find a way to root without tripping it. Banking apps can be fooled using xposed modules or Magisk systemless root, but again, you'd be tripping knox. If knox is so important to you, I'd stick with stock.

The most important for me is the privacy and security of my data on the phone. Without root, applications use everything they want. I would like to have the Permission Manager to control access to my data on the phone. I would also like to use a normal firewall without VPN.

Is it possible to use secure folder after root ?

Hi,
I just root my s8, but find out I'm not able to use secure folder anymore.
Is there any way that I can use it.
Or do I have to remove the root to use secure folder again.
Many thanks

Little-white said:
Hi,
I just root my s8, but find out I'm not able to use secure folder anymore.
Is there any way that I can use it.
Or do I have to remove the root to use secure folder again.
Many thanks
Click to expand...
Click to collapse
Generally NO once your phone has been modified you will trip your Knox. Once Knox is tripped you can not use things like secure folder,Shealth, Samsung pay. There is no fix for a tripped knox

spawnlives said:
Generally NO once your phone has been modified you will trip your Knox. Once Knox is tripped you can not use things like secure folder,Shealth, Samsung pay. There is no fix for a tripped knox
Click to expand...
Click to collapse
Bastards man, why can't they be like they used to with the S5 and below...
Now they just want people to use dumb phones and scare them away from exploring their own devices potential.

Hi,
If you had something, like the pin or password list, in the secure folder, you did the backup before rooting and now restore it, what happens with that list? Is it restored or not? If yes, where?
Thanks!
Sent from my SM-G955F using Tapatalk

CoreyOS said:
Bastards man, why can't they be like they used to with the S5 and below...
Now they just want people to use dumb phones and scare them away from exploring their own devices potential.
Click to expand...
Click to collapse
First, thinking about it, Knox is a bonus. Without Knox you still have access to every function that other Android also have. You can use Google Fit to replace Shealth, Google Pay to Samsung Pay, and Island (by Oasis Feng) or Parallel Space to Secure Folder. Obviously all of these alternatives don't perfectly replace Knox, but there is a reason to root devices lose access to Knox, it's for security. Knox is a subsystem isolated from the rest of the system to store highly confidential information. it's not about you bank data or your nudes, it's to prevent that industrial secrets you could have in your Secure Folder will not be stolen by a malware disguised as a game. There is also a hardware implementation called ARM TrustZone that stores encrypt keys and biometrical data and do security related computing. Remember now that a Root device can be deeply compromised. Normally all we do are tweaks to turn UI better, but you can also change firmware, modify system as you like, etc. To guarantee that your device are safe to store whatever your cautious boss want, Knox could verify every single file of your OS, firmware and beyond, or only verify if a bit have changed from 0x0 to 0x1. That's why they can't be like S5 and below
I'm not here exactly to defend Samsung, only trying to explain why it's works that way (and I'm not an Samsung Employee nor what to spend 3 hours explaining how it's hardware implemented, so what I'm saying is based on my own research)