[Q] AT&T S4 - Xposed and XPrivacy - Root Required? - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

SGH-l337
I'm very interested in running Xposed and XPrivacy on my Stock S4 and I have some questions and concerns.
My main concern is keeping the phone rooted. I've read that you can remove root after installing/upgrading the Xposed framework, which is awesome. However, i'm wondering if anyone has any experience running XPrivacy without root?
Main issue is that my company requires airwatch. They purchased the phone and pay my bill, so i'm not looking to get into a discussion about airwatch and company policy. I'm just interested in managing application privacy settings.
Thanks

Related

[Q] KNOX and Rooted Device

I hope I am nut cluttering things up with a stupid question but I would like to find out if rooting and KNOX are mutually exclusive. My situation is that I will be moving from a personal to corporate liable account at work soon (taking my S4 with me) and their only requirement is securing the device on MobileIron with KNOX. I don't really mind the stock rom but there are two or three things I would like to be able to do on my device that require root access (mostly config toggles with a profile manager and using TiBu).
Thanks for any wisdom you can pass on.
drichter12 said:
I hope I am nut cluttering things up with a stupid question but I would like to find out if rooting and KNOX are mutually exclusive. My situation is that I will be moving from a personal to corporate liable account at work soon (taking my S4 with me) and their only requirement is securing the device on MobileIron with KNOX. I don't really mind the stock rom but there are two or three things I would like to be able to do on my device that require root access (mostly config toggles with a profile manager and using TiBu).
Thanks for any wisdom you can pass on.
Click to expand...
Click to collapse
This belongs in the Q&A forum. You know...since this is a Q.

[Q] Looking for ROM suggestions

I hope this is the right forum to ask this question. If not, please accept my apologies and guide me where I can pose the question.
I bought the AT&T version of GS4 and currently on Straight talk. I am looking for a good ROM to flash with, and open to suggestions. My most important things are:
Battery Life
Clean Experience (No AT&T Crapware) - I loved CleanROM concept but looks like the developer stopped work on that.
OTA Updates
TouchWiz (not stock Google experience) & Samsung version of Email Client (My exchange policies requires it)
It would be great if some Stock Google apps, such as Photosphere work, but it is not a hard requirement.
Any suggestions?

[Q] Privacy on the Note 3

So I recently got my N3 and I've been looking around the forums for privacy features similar to those shipped with cyanogen-mod and AOKP with regard to apps. I really want to block apps like twitter and such from getting into my address book and this I could do with "Privacy Guard" on my old handset.
So I've been on the lookout for something similar for the N3 via a mod or root+tweak but haven't seen anything yet. Maybe there's some manual way to it? Any thoughts or ideas?
xposed framework + xprivacy module - all you need
Don't worry, the NSA has got everything anyways
How about some firewall + Titanium Backup..
You can freeze / delete all unwanted apps with Titanium Backup and put some apps behind firewall if you need them, but they just don't need to get internet access
I'm not that concerned with whatever the agencies do in this case... I however don't want to be part of this aggressive advertisement that companies run. Do you know this or that person e-mails...
Thanks for the tips. Will look into them

Privacy concerns returning to android from iOS

Hi
I have decided to move back to android from iOS as i would like to have more freedom and less dependency on itunes
I am having some issues with android
The biggest one is app permissions on ios i was able to choose which permissons i can give an app however on android its take it or leave it. Please please help me on this.
I know i can root my S5 and i might be able to control app permissions however i am worried i wont be able to use my banking apps after rooting my device.
I will appreciate a simple solution to this as i am not very technical and dont understand much about rooting (you cant blame me i am an ios user)
Thanks
I had that same issue you are worried about......I rooted my device and some apps detected this and refused to function. I got around it by installing xposed framework and adding the Rootcloak module to it......The apps in question can't tell I have root now......
Edit......Rootcloak contains a list of *known* root checking apps, but also offers the capability of adding new apps to the list if your app is not listed.....
Edit 2.......Welcome back from the dark side...... lol
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Hi Keith thanks for the info
Could you please direct me to a newbie friendly root method.
humadoon said:
Hi Keith thanks for the info
Could you please direct me to a newbie friendly root method.
Click to expand...
Click to collapse
That depends on whether you are running 4.4.2 KK or 5.0.0 LP.......
But whichever Android version you have, you'll need to use a PC/Laptop and some software called Odin.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Could you guide me towards any step by step guide so much confusing info for newbie i dont want to brick my phone
As I said in my previous post, we need to know which version of Android your phone is running in order to direct you to the correct method......
You'll find that info in......
Settings >> general >> about device
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
humadoon said:
Hi
I have decided to move back to android from iOS as i would like to have more freedom and less dependency on itunes
I am having some issues with android
The biggest one is app permissions on ios i was able to choose which permissons i can give an app however on android its take it or leave it. Please please help me on this.
I know i can root my S5 and i might be able to control app permissions however i am worried i wont be able to use my banking apps after rooting my device.
I will appreciate a simple solution to this as i am not very technical and dont understand much about rooting (you cant blame me i am an ios user)
Thanks
Click to expand...
Click to collapse
Hello
Welcome in the Android familly!
Getting root access on the phone removes the basis of the security feature of the Android framework. For sure you will have more control on the application installed but some malware could
take benefit from the fact your phone is rooted. It is not surprising that critical stuff like banking does not want to run if the phone is rooted. This beeing said I rooted my previous phone (GS3) and
might well root this one (GS5) after a while.
For me main reason for rooting the phone was enabling automatic control of data on/off/ wifi on/off, flight mode which have been removed from latest Android revisions.
However when you give root access to an application that ask for it, you just give it more responsibility/power over your phone content/stability/integrity.
Apps without root support cannot "damage" the phone/content by construct because they only have access to their own stuff.
jm_38 said:
Hello
Welcome in the Android familly!
Getting root access on the phone removes the basis of the security feature of the Android framework. For sure you will have more control on the application installed but some malware could
take benefit from the fact your phone is rooted. It is not surprising that critical stuff like banking does not want to run if the phone is rooted. This beeing said I rooted my previous phone (GS3) and
might well root this one (GS5) after a while.
For me main reason for rooting the phone was enabling automatic control of data on/off/ wifi on/off, flight mode which have been removed from latest Android revisions.
However when you give root access to an application that ask for it, you just give it more responsibility/power over your phone content/stability/integrity.
Apps without root support cannot "damage" the phone/content by construct because they only have access to their own stuff.
Click to expand...
Click to collapse
Hi thanks i agree.
I wish android could give more control to users so they dont have to take the rooting route as i said my only reason is i want to control app permissions. I should have the right to choose which areas i allow fb to i dont want fb to save my contacts on their servers or my location.
humadoon said:
Hi thanks i agree.
I wish android could give more control to users so they dont have to take the rooting route as i said my only reason is i want to control app permissions. I should have the right to choose which areas i allow fb to i dont want fb to save my contacts on their servers or my location.
Click to expand...
Click to collapse
Lol.....do what I do.......bookmark their mobile site, and save a shortcut to your home screen........no more resource hogging apps (FB and messenger) and no more dodgy permission requests.......
You won't get notifications anymore.......but is that REALLY that important that you do?
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
My only concern from making the switch from iphone 6 to note 4 is the loss of imessage encryption witch is pretty solid to now using the basic sms messanger. There is 3rd party apps but they require both people to be on them. As far as documents and photos go google drive is encrypted just like i cloud i believe. Life would be perfect if they had imessage for android. I am rooted and set permissions based on what the app is and delete unnecessary Google apps like google + ect.
Edit but I also dont use Facebook ect only instagram
Sent from my SM-N910P using XDA Free mobile app
Got myself a oneplus one which is perfect I can now restrict apps and also use banking apps

Safetynet check, apps won't run on rooted devices. What IS CTS?

If you are running Lineage OS for the BLU R1HD, or almost any custom ROM on any device, you have probably gotten this message from android pay, PS Vue, or a number of other apps: "can not run on a rooted device". This is easy to fix on a rooted device, but a custom ROM is a whole other story. I kept getting CTS profile mismatch, regardless of what I tried. I'm not a developer, but I am no dummy, work as an OpenStack engineer, and have been in network engineering for 15 years, yet I could not find crap about CTS, other than it is the " Comparability Test Suite ". After hunting the web, I finally stumbled upon a good article that explains it pretty nicely, so here it is:
------------
Rooting your Android device gives you access to a wider variety of apps and a deeper access to the Android system. But some apps–like Google’s Android Pay–won’t work at all on a rooted device.
Google uses something called SafetyNet to detect whether your device is rooted or not, and blocks access to those features. Google isn’t the only one, either–plenty of third-party apps also won’t work on rooted Android devices, although they may check for the presence of root in other ways.
SafetyNet: How Google Knows You’ve Rooted Your Android Phone
Android devices offer a “SafetyNet API,” which is part of the Google Play Services layer installed on Google-approved Android devices. This API “provides access to Google services that help you assess the health and safety of an Android device,” according to Google. If you’re an Android developer, you can call this API in your app to check whether the device you’re running on has been tampered with.
This SafetyNet API is designed to check whether a device has been tampered with–whether it’s been rooted by a user, is running a custom ROM, or has been infected with low-level malware, for example.
Devices that ship with Google’s Play Store and other apps installed must pass Google’s Android “Compatibility Test Suite”. Rooting a device or installing a custom ROM prevents a device from being “CTS Compatible”. This is how the SafetyNet API can tell if you’re rooted–it merely checks for CTS compatibility. Similarly, if you get an Android device that never came with Google’s apps–like one of those $20 tablets shipped direct from a factory in China–it won’t be considered “CTS compatible” at all, even if you haven’t rooted it.
To get this information, Google Play Services downloads a program named “snet” and runs it in the background on your device. The program collects data from your device and sends it to Google regularly. Google uses this information for a variety of purposes, from getting a picture of the wider Android ecosystem to determining whether or not your device’s software has been tampered with. Google doesn’t explain exactly what snet is looking for, but it’s likely snet checks if your system partition has been modified from the factory state.
You can check the SafetyNet status of your device by downloading an app like SafetyNet Helper Sample or SafetyNet Playground. The app will ask Google’s SafetyNet service about your device’s status and tell you the response it gets from Google’s server.
It’s Up to the App
SafetyNet is optional for app developers, and app developers can choose to use it or not. SafetyNet only prevents an app from working if an app’s developer doesn’t want it to work on rooted devices.
Most apps won’t check the SafetyNet API at all. Even an app that does check the SafetyNet API–like the test apps above–won’t stop working if they receive a bad response. The app’s developer has to check the SafetyNet API and make the app refuse to function if it learns your device’s software has been modified. Google’s own Android Pay app is a good example of this in action.
Android Pay Won’t Work on Rooted Devices
Google’s Android Pay mobile payment solution doesn’t work at all on rooted Android devices. Try to launch it, and you’ll just see a message saying “Android Pay cannot be used. Google is unable to verify that your device or the software running on it is Android compatible.”
It’s not just about rooting, of course–running a custom ROM would also put you afoul of this requirement. The SafetyNet API will claim it’s not “Android compatible” if you’re using a custom ROM the device didn’t come with.
Remember, this doesn’t just detect rooting. If your device were infected by some system-level malware with the ability to spy on Android Pay and other apps, the SafetyNet API would also prevent Android Pay from functioning, which is a good thing.
Rooting your device breaks Android’s normal security model. Android Pay normally protects your payment data using Android’s sandboxing features, but apps can break out of the sandbox on a rooted device. Google has no way to know how secure Android Pay would be on a particular device if it’s rooted or running an unknown custom ROM, so they block it. An Android Pay engineer explained the problem on the XDA Developers forum if you’re curious to read more.
Other Ways Apps Can Detect Root
SafetyNet is just one way an app could check if it’s running on a rooted device. For example, Samsung devices include a security system named KNOX. If you root your device, KNOX security is tripped. Samsung Pay, Samsung’s own mobile-payments app, will refuse to function on rooted devices. Samsung is using KNOX for this, but it could just as well use SafetyNet.
Similarly, plenty of third-party apps will block you from using them, and not all of them use SafetyNet. They may just check for the presence of known root apps and processes on a device.
It’s tough to find an up-to-date list of apps that don’t work when a device is rooted. However, RootCloak provides several lists. These lists may be out-of-date, but they’re the best ones we can find. Many are banking and other mobile wallet apps, which block access on rooted phones in an attempt to protect your banking information from being captured by other apps. Apps for video streaming services may also refuse to function on a rooted device as a sort of DRM measure, attempting to prevent you from recording a protected video stream.
Some Apps Can Be Tricked
Google’s playing a cat-and-mouse game with SafetyNet, constantly updating it in an attempt to stay ahead of people getting around it. For example, Android developer Chainfire has created a new method of rooting Android devices without modifying the system partition, known as “systemless root”. SafetyNet initially didn’t detect such devices as being tampered with, and Android Pay worked–but SafetyNet was eventually updated to detect this new rooting method. This means Android Pay no longer works along with systemless root.
Depending on how an app checks for root access, you may be able to trick it. For example, there are reportedly methods to root some Samsung devices without tripping the KNOX security, which would allow you to continue using Samsung Pay.
In the case of apps that just check for root apps on your system, there’s an Xposed Framework module named RootCloak that reportedly allows you to trick them into working anyway. This works with apps like DirecTV GenieGo, Best Buy CinemaNow, and Movies by Flixster, which don’t normally work on rooted devices. However, if these apps were updated to use Google’s SafetyNet, they wouldn’t be so easy to trick in this way.
Most apps will continue working normally once you’ve rooted your device. Mobile payment apps are the big exception, as are some other banking and financial apps. Paid video-streaming services sometimes attempt to block you from watching their videos as well.
If an app you need doesn’t function on your rooted device, you can always unroot your device to use it. The app should work after you’ve returned your device to its secure, factory state.
I am checking every way hoping to find a solution ...
Yes...It's working.
I am using GPay on my rooted device !

Categories

Resources