Android Pay for rooted/unlocked devices - Android Q&A, Help & Troubleshooting

I wanted to start this thread because it appears the new Android Pay app will not work on rooted devices. It's not a device specific issue.
I was able to gain a small victory on my VZW MotoX 2014 unlock/rooted device. I disabled superuser within the SuperSU app and was able to add one of my CCs.
Thats where the good news stops. My phone does not work at retailers and I am no longer able to add any more CCs even with root disabled. There must be a fuse that triggers when the app discovers you are rooted.
I've tried xposed mods - Root Cloak and No Device Check with no luck.
I have not tried it at the store with the xposed mods, but I am not able to add any more CCs.
Thoughts?

Related

Prevent app from reading root status?

Is it possible to prevent an app from reading the phone's root status? Can lucky patcher or something similar help?
Sent from tapatalk
Lucky Patcher is forbidden to be discussed here given what most people use it for.
I'm not aware of anything that will hide root on a per app basis, you can only 'hide' it on a system-wide basis in SuperSu (uncheck Enable Superuser in settings), run the app you want to run, then unhide root (recheck Enable Superuser in settings; you may need to reboot to re-enable root).
This will work for some apps, but it depends on what the app actually checks for when it checks for root. If it only queries if SuperSu/similar is enabled, then that will solve your problem.
There's actually two ways to do this that I know of, there's an Xposed module, Root Cloak which will hide root on a per-app basis. There's also Root Cloak Plus on Play Store which requires Cydia Substrate to run (both apps/methods are called the same thing but are different apps/methods of hiding root). I've never used either of them, but I know a lot of people have success with the Xposed version, Root cloak.
Short story, install Xposed framework if you haven't already, and then install the Root Cloak module from XDA and see if it works for you.
Good info Hopper
Tried the first method by disabling root in super su, that did work. And a reboot later, root was back. But once you disable root, it's so for all apps. I'm going to try the xposed module now. Thanks a lot for the info.
Sent using Tapatalk

[Q] Cydia Substrate can't perform its "internal safety check"

Hello there xda developers-Community ,
this is my very first post and I hope this is the correct board I'm posting in .
I have an issue with Cydia Substrate on Android, but before explaining to you what the issue is, I'd like to explain to you what I wanted to do and why I need Cydia Substrate (if you don't really care you can skip this, of course ):
I'm using a banking-app which, when detecting root on a device, stops working completely (it doesn't just show a warning, it refuses the user from continuing to the next screen). Of course, I don't want to unroot my device. So I did some research and came across apps like Hide my Root and RootCloak which is a Xposed Module. All of these apps didn't work for me, even when installed and set up correctly. After doing some research again I found out that it doesn't work for other users either... Doing even further research I finally came across RootCloak Plus which works with Cydia Substrate and not Xposed anymore. I can't confirm it yet, but according to the thread this method should work with my app. So, I downloaded Cydia Substrate (I tried the Google Play-Version and the APK from the website) and RootCloak Plus from Google Play. But now we get to the main issue:
Everytime I open Cydia Substrate it shows me a message saying:
Note: something about your device made it impossible for Substrate to perform its internal safety check; can you please contact saurik via e-mail?
Click to expand...
Click to collapse
Of course, actually contacting saurik via e-mail wasn't my first option .
I tried to fix this issue on my own with doing the following:
I updated CyanogenMod to the latest nightly
I switched my superuser app from SuperSU to superuser and back to SuperSU
I tried changing the SELinux mode from "enforcing" to "permissive" with SELinuxModeChanger
Reinstalled the apps and rebooted my device serveral times
Unfortunately, even though this problem seems to be quite common, there are only a few to nearly no threads covering this topic anywhere (at least I only came across over a few of them).
Here are some of my specs and details, maybe any of this will help:
Device: Samsung Glaxaxy S4 (jfltexx)
CyanogenMod version: CyanogenMod 12 12.1-20150708-NIGHTLY-jfltexx (Android 5.1.1)
Superuser App: SuperSU Free (CM) v2.46 (binary up to date and SuperSU working with other apps just fine)
BusyBox version: BusyBox v1.23.2-Stericson
Root properly installed and working, confirmed by serveral apps.
Do you have any idea how to fix this issue? I hope you can help !
Thank you very much,
DigitalClark .
I have the exact same issue. On my streaming app, xposed module allows me to bypass warning, but I still can't watch any shows...
Lg G3 D855
Rooted, Resurrection remix 5.5.4
Lollipop 5.1.1
I've emailed Saurikit on the email address provided on google play, but no reply...
Sent from my LG-D855 using XDA Free mobile app
I have the same problem on a Sony Z2 (sirius) CM12.1
So if anyone has an idea for a solving I'd highly appreciate!
Bump, in-case if someone has ran across a similar issue and found a solution.
Cydia Substrate is supported on Android 2.3 to 4.3 according to their website. Also the app itself hasn't been updated since 2013. Thus the chances that it will work on 5.1.1 are pretty dim.
I get the same message. I am just wondering if SuperUser is the reason. I don't think SU can find it, will this cause the internal safety check message to occur?
If you jail break your device it will work
I have the same problem ASUS ZenFone 2

Lloyds mobile banking app uk

I have kenzo cyanogen ROM installed (13.0-20160617 unofficial kenzo) I have used Lloyds banking app for a long time but tonight it tells me I can't log in as using a rooted or jail broken device. I haven't updated the app for a while or ran any other updates.
Is this room rooted by default? As I didn't think it was and I didn't think I had root.
Is there a way to fix it so I can use my banking app again?
It has a root option which you can enable. I can suggest trying root cloak but that also means you'll have to install xposed. Make sure root is turned off in dev settings and clear the cache/data of the banking app before trying root cloak. Otherwise you may have to settle for their website.
Root is off in the developer options. I wonder if the banking app can see the ROM or something else is not stock? Its frustrating as it was the reason I didn't root my phonephone/want it rooted.
I noticed that even installing an older version of the app I get same error so maybe something else has changed . if a system app has somehow updated and caused this? I am still on the original ROM from june. I haven't installed nightlies.
Either that or my account has somehow been flagged so even old app versions dont work(deleted data and folders etc from the app first.)
regarding ths problem - Im guessing its not looking at root as this is disabled, but it can see either an unsupported rom, or something else. Can i flash a different rom (prefereably not Miui) and regain the banking app? a rom that would be classes as supported?

S-pushTAN still detects root, even with magisk hide

Hello!
I recently activated Online Banking for my Bankaccount. They use pushTAN with their own build app. I used xposed and SuperSU, but decided to flash a new ROM with only magisk. My current device is the Huawei P8lite with OmniROM and magisk 13.3. My device passes SafetyNET and it says certified at the Play Store. I checked magisk hide for the pushTAN app and the normal Sparkasse app. The Sparkasse app works, but it still says that my device is rooted. The pushTAN app however wont start. It says, that the app was closed and opens a website in chrome saying that my device is unsecure because I have root. I just flashed this ROM and I have no other root requiring apps installed. I've uploaded both apps to my G-Drive, so maybe someone can look and see why it still sees root. the pushTAN app is more important.
pushTAN.apk
Sparkasse.apk
Soo, I used the phone of my brother now. After getting my TAN I was able to set up the normal Sparkassen App. It works fine. But the pushTAN app still doesn't work on my device. I tried another different ROM now, but still no difference.
Any news on that?
I have the exact same problem. Axon 7 here, rooted via Magisk. Magisk is set to "hide" from pushTAN app and also "hide from various detections" in settings.
pushTAN crashes and redirects to a webpage hinting that i have rooted my device.
Same issue for me :/ once i run Magisk-uninstaller pushtan app works immediately
I can approve: it works if you temporarly uninstall magisk, without? uninstalling the root patch.
Other way would be to install s-pushtan into an emulator on your PC, like this:
Download S-pushTAN on PC with MEmu
Download S-pushTAN on PC with MEmu Android Emulator. Enjoy playing on big screen. pushTAN is the correct procedure for anyone who wants to make mobile banking.
www.memuplay.com
But, I would NOT trust a download that packs app and emulator into a single package. This massively increases the likelyhood of a special hack applied that spies on s-pushtan. I recommend finding any plain Android emulator then install S-pushtan from Play store. This might be more difficult, though.
Would be a joke if it really worked, since S-pushtan is all about using different devices for login and transaction authorization. This would be broken if you use an emulator on your PC. So it would make the transaction even more insecure than a rooted phone.
I'll have a look if there is an official, viable alternative to s-pushtan.

Odd question- Magisk 'full' root?

Main question at the end of post.
I came across an app that said my device isn't rooted properly, when it is, or I thought it was?
Spyera is the app. For those not familiar, spyera is an app that is used to monitor devices, family members, employees, doesn't matter. Let's assume everyone owns the devices and those using the devices are aware. Not the point of the post.
spyera has a rooted and a non rooted version. The rooted version will not install on my devices. I talked to tech support and they are saying my device isn't a full root. Their software root algorithm says my phone isn't rooted. Basic root checkers and all of my apps requiring root seem to think my root is fine.
I have a few pixel 4xl device's and some samsung s21 ultras that are all rooted with magisk. All other root apps work fine.
This brings up my main question....is magisk a "full" root? Or is it something else?
Spyera tends to be a pretty reliable platform and if their software is saying I'm not rooted, I am curious what could be the reason.
Magisk is "full" root. If an app can't detect Magisk as a root solution it's poorly written.
And yes, that's a shady app... I'd be very careful with giving an app like that complete and full access to a device by giving it superuser permissions (or even install it in the first place). Also, doesn't sound like the company even knowns what they're talking about.
Thanks. And yes, very shady
@Didgeridoohan
Magisk ISN'T ROOT, it's a framework that allows to inject some functionalities into Android ecosystem.
jwoegerbauer said:
@Didgeridoohan
Magisk ISN'T ROOT, it's a framework that allows to inject some functionalities into Android OS.
Click to expand...
Click to collapse
And one of the parts of the Magisk suite of software is MagiskSU that provides root for Android applications... Sure, Magisk is more than "just" root, but when you talk about Magisk and root in the same context, generally it's understood that what you're actually talking about is MagiskSU.
But thanks for clarifying.

Categories

Resources