Hey guys! I'm new to this community so first of all I want to say hello to you all! Sadly my arrival is mostly based on a possible-problem for me.
So here's the situation:
1- Bad Guy runs an app on Good Guy's phone that asks for root access, this app is malicious and can be used to steal almost everything (like theftspy that was developed by a dev from xda)
2-Bad Guy grants it the access and sets SuperSU to "grant on demand" for this specific app. Then deletes all the logs of all this and removes this app from APPS tab of SuperSU.
3- Good Guy is completely unaware of all these.
4-A few weeks later Good Guy learns that this Bad Guy could have been installed an app on his phone that can steal sensitive information. He performs an Avast Mobile Security scan that returns clean and later performs a complete wipe of his phone and loads a new ROM.
So I'm the Good Guy here I confronted Mr. Bad Guy about it who ultimately denied that, but I got some strong suspicions that he might be lying. Data in the phone was private (mostly business) so even the probability of this being stolen is scary.
Without any further ado my question is: Can this malicious app keep onto its root access after a reboot (can any app do that)? Because if it can not, then even if it starts itself after boot, it'll have to grant root access again which would leave logs and would be seen on SuperSU this time, which neither was there so would mean I am safe. Also is Avast's scan result reliable on this basis?
Thanks to everyone who took their time to read, any help is so much appreciated.
Bump
Well, there are many root apps that run after system startup. It depends on the app that was installed on your phone.
If Mr.Bad removed app from SuperSU and deleted logs, that means the app isn't in use and will no longer do its work. That means, the app is just installed with no harm.
Also there was no need to change your ROM and factory reset. Just by uninstalling the app you'll be done.
Even, you scanned through AntiVirus and didn't found anything.
Stilling data from one phone and sending to other phone must need a medium to transmit data, in your case it must be internet. You could have check in Data Usage in Setting weather there is any anonymous app that is using your data.
Still there is probability, that your personal data must be stolen.
It depends on the duration between 'granted root permission to app and removing app from SuperSU list'
Also you said about 'grant on demand' its similar to 'prompt' was applied to the app in SuperSU.
Have you granted permission anytime? I yes them probably your data is stolen by Me.Bad.
Hope you understand everything
Regards,
hitman-xda
hitman-xda said:
Well, there are many root apps that run after system startup. It depends on the app that was installed on your phone.
If Mr.Bad removed app from SuperSU and deleted logs, that means the app isn't in use and will no longer do its work. That means, the app is just installed with no harm.
Also there was no need to change your ROM and factory reset. Just by uninstalling the app you'll be done.
Even, you scanned through AntiVirus and didn't found anything.
Stilling data from one phone and sending to other phone must need a medium to transmit data, in your case it must be internet. You could have check in Data Usage in Setting weather there is any anonymous app that is using your data.
Still there is probability, that your personal data must be stolen.
It depends on the duration between 'granted root permission to app and removing app from SuperSU list'
Also you said about 'grant on demand' its similar to 'prompt' was applied to the app in SuperSU.
Have you granted permission anytime? I yes them probably your data is stolen by Me.Bad.
Hope you understand everything
Regards,
hitman-xda
Click to expand...
Click to collapse
Thanks for answer hitman!
I haven't granted any app root access. But Mr. Bad could have done it before I got my phone back. After starting to use my phone I rebooted it. I wonder if this app can start running with root access on its own after a reboot. Or should it get granted root access again by the user.
If so, then that'd be like NSA level coding / spying to avoid detection and still run after resetting.
es0tericcha0s said:
If so, then that'd be like NSA level coding / spying to avoid detection and still run after resetting.
Click to expand...
Click to collapse
Resetting as in like restarting your phone right? And not returning to factory state.
remorseful said:
Thanks for answer hitman!
I haven't granted any app root access. But Mr. Bad could have done it before I got my phone back. After starting to use my phone I rebooted it. I wonder if this app can start running with root access on its own after a reboot. Or should it get granted root access again by the user.
Click to expand...
Click to collapse
If the app is setup such that it runs on startup and SuperSU is set as 'prompt' for that app, it must have asked user for granting permission after every reboot.
remorseful said:
Resetting as in like restarting your phone right? And not returning to factory state.
Click to expand...
Click to collapse
Nope dude! Resetting means going back to factory state.
Say, Mr.Bad could have installed an app in your phone that you are unaware of.
Whats more important is the permissions of that app. If it can claim sensitive permissions like access to contacts / messages / sdcard , then he can get that data even when the app doesn't have root access. And if the app has root access, then the damage could have been done already before he deleted the supersu logs. And no, it cannot be granted root access after the logs are deleted automatically on startup.
And Mr.Bad could have installed his malicious app on to system partition in which case u may not be aware of what the app is. And what damage it does. In such case even a factory reset doesn't help.
It is advised to reinstall the rom and protect superuser with some pin / password.
bharat g said:
Say, Mr.Bad could have installed an app in your phone that you are unaware of.
Whats more important is the permissions of that app. If it can claim sensitive permissions like access to contacts / messages / sdcard , then he can get that data even when the app doesn't have root access. And if the app has root access, then the damage could have been done already before he deleted the supersu logs. And no, it cannot be granted root access after the logs are deleted automatically on startup.
And Mr.Bad could have installed his malicious app on to system partition in which case u may not be aware of what the app is. And what damage it does. In such case even a factory reset doesn't help.
It is advised to reinstall the rom and protect superuser with some pin / password.
Click to expand...
Click to collapse
Well I'm mostly scared of screenshots being taken remotely which requires root access.
HA! That's what I wanted to hear! The startup part!
Yeah since resetting won't clear off a possible /system infection I performed a full wipe and installed Cloudy ROM.
Yet I have done it after a few weeks.Still, a possible spy app would need to grant root access again on device start up by me which didn't happen so I assume I'm safe Is there a known way for an app to grant root access without user permission once the device is turned off and turned back on ?
remorseful said:
Well I'm mostly scared of screenshots being taken remotely which requires root access.
HA! That's what I wanted to hear! The startup part!
Yeah since resetting won't clear off a possible /system infection I performed a full wipe and installed Cloudy ROM.
Yet I have done it after a few weeks.Still, a possible spy app would need to grant root access again on device start up by me which didn't happen so I assume I'm safe Is there a known way for an app to grant root access without user permission once the device is turned off and turned back on ?
Click to expand...
Click to collapse
Once an app gets root granted and is in whitelist of superuser management app, then if such app can autostart on boot it can get root granted without user permission.
Eg: Firewall app.
bharat g said:
Once an app gets root granted and is in whitelist of superuser management app, then if such app can autostart on boot it can get root granted without user permission.
Eg: Firewall app.
Click to expand...
Click to collapse
True but if it is whitelisted on the Superuser management app then it is pretty easy to detect since it'll be listed there.
P.S:I assume you mean to be "set to "'grant on demand'" on SuperSU by "being whitelisted".
Related
Is there a way to install an apk as a system app? I want to 'unroot' a device but still run an app that requires root access. I'm unsure of how this can be done, any advise would be very much appreciated!
Thanks
I know that the Z4 root app has an option for temp root functions which goes back to an unrooted state once you reboot.
My guess is that you can run that, place your apk in the appropriate system folder, install the apk from there & then reboot.
But again I'm not to sure if temp root functions work on our G-Tabs & if it does if it's as simple as I explained. Worth a try I guess.
Again I'm assuming that your not already in a permanent root state. If so then you'll have to unroot completely first & then try what I mentioned above.
Unless someone has an easier method?
convert user apps to system apps
nikt said:
Is there a way to install an apk as a system app? I want to 'unroot' a device but still run an app that requires root access. I'm unsure of how this can be done, any advise would be very much appreciated!
Thanks
Click to expand...
Click to collapse
Titanium Backup Pro (paid version 3.8.1 and higher) has a function that allows one to convert user apps-->system apps (as well as system app-->user app ... though this sometimes causes initial FCs, which generally disappear with reboot).
Not sure if the effect will remain after unrooting.
Just to clear up a bit, not because an app its on /system it will have root access. If you want to run an app that needs root, you need root, thats it. You cant unroot and use the app after that.
So, no you cant do that. Its 2 different things installing an app on /system than having root for an app.
pmcnano said:
Just to clear up a bit, not because an app its on /system it will have root access. If you want to run an app that needs root, you need root, thats it. You cant unroot and use the app after that.
So, no you cant do that. Its 2 different things installing an app on /system than having root for an app.
Click to expand...
Click to collapse
So then how do proprietary apps like Sprint Nascar (as an example) run on an unrooted phone?
Why would Sprint Nascar need root permision?
pmcnano said:
Why would Sprint Nascar need root permision?
Click to expand...
Click to collapse
It probably doesn't or it might I have no idea. The op never pointed out which apps he wants to use.
However & this is a big however, as I have no idea which apps require root access, one has to assume that any of the preinstalled apps that come on our G-Tabs do in fact need root access, yet they can run on an unrooted device. Again I could be wrong.
That being said, how does one go about determining which apps require root access?
Thanks for the replies guys. The issue is supporting proxy servers on unrooted devices. There are several proxy apps that require root access as well as a kernel that supports proxy. If the proxy app were installed as a system app, would this have enough rights to access the kernel as required? I don't know enough about this but was led to believe this might work if it was running as system. Same for apps that use CIFS, like mount manager. I guess I'll give it a try and see what happens...!
Like I said, being installed on System doesnt have anything to do with having root or not.
Im 95% sure about what I am saying.
edit: I confirmed it..so 100% sure, if the app needs root, you will need root no matter where the app is installed.
In the past I read a thread from someone claiming that he had
Appbrain App Market installed on his phone which is a Non-Root app the last time I checked, Well anyways he said that he was Receiving Popups from the app to Grant it Superuser Permissions.
I really Didn't think much about it until now when I Received a Popup of my own, After I Installed whatever Stupid Basketball 3D game from the Market myself...
I checked and it Wasn't a Root app, and it Didn't even show up in the Superuser app Log, even though I Didn't Grant it Permission. I just UnInstalled it as soon as I saw the Popup!
So my Question is...
What the Hells up with that? Is that some type of Virus app or some ****?
Thanx in Advance!
PMGRANDS said:
In the past I read a thread from someone claiming that he had
Appbrain App Market installed on his phone which is a Non-Root app the last time I checked, Well anyways he said that he was Receiving Popups from the app to Grant it Superuser Permissions.
I really Didn't think much about it until now when I Received a Popup of my own, After I Installed whatever Stupid Basketball 3D game from the Market myself...
I checked and it Wasn't a Root app, and it Didn't even show up in the Superuser app Log, even though I Didn't Grant it Permission. I just UnInstalled it as soon as I saw the Popup!
So my Question is...
What the Hells up with that? Is that some type of Virus app or some ****?
Thanx in Advance!
Click to expand...
Click to collapse
i'm not familiar with random apps from the market asking for superuser permission but i am familiar with the superuser app and how the permission structure/process works.
essentially, the superuser.apk file replaces your /system/bin/su binary with its own binary. the superuser custom binary, whenever any user or application executes a command using the su binary (executing a command as root) the superuser su binary redirects to the superuser application then prompting the user to accept or deny the request.
i know i have seen it is possible to spoof these requests, but it was done by a very knowledgable friend and i don't think the spoofing of superuser requests is common place or well known (might have been patched recently too).
without knowing the application's source code that requested superuser access, i personally would not trust the application unless the application stated it would need root access and performed functions which required root access. example, if the application were a game, i don't see any reason it would need superuser access.
once an application has been granted superuser access on an s-off evo 3d, it essentially has write/read access to the majority of the android partitions including the kernel, system, data, cache, etc.
from what you've described, i think you're correct in not granting an unknown application superuser access. as a developer with applications in the market, i would appreciate an email from a user who experienced such a situation and a screenshot attached would be even more helpful. might be worthwhile reaching out to the developer to confirm or ask them to explain.
thanks for posting this information. always good to know. hope some of the information i provided helps!
joeykrim said:
i'm not familiar with random apps from the market asking for superuser permission but i am familiar with the superuser app and how the permission structure/process works.
essentially, the superuser.apk file replaces your /system/bin/su binary with its own binary. the superuser custom binary, whenever any user or application executes a command using the su binary (executing a command as root) the superuser su binary redirects to the superuser application then prompting the user to accept or deny the request.
i know i have seen it is possible to spoof these requests, but it was done by a very knowledgable friend and i don't think the spoofing of superuser requests is common place or well known (might have been patched recently too).
without knowing the application's source code that requested superuser access, i personally would not trust the application unless the application stated it would need root access and performed functions which required root access. example, if the application were a game, i don't see any reason it would need superuser access.
once an application has been granted superuser access on an s-off evo 3d, it essentially has write/read access to the majority of the android partitions including the kernel, system, data, cache, etc.
from what you've described, i think you're correct in not granting an unknown application superuser access. as a developer with applications in the market, i would appreciate an email from a user who experienced such a situation and a screenshot attached would be even more helpful. might be worthwhile reaching out to the developer to confirm or ask them to explain.
thanks for posting this information. always good to know. hope some of the information i provided helps!
Click to expand...
Click to collapse
Yeah man I Never really Experienced a App Requesting Superuser Permission, that Wasn't even a Root App... Just Didn't seem right to me either... A Game Shouldn't need Root Access!!
Thanx for your Reply!
I recently had the same op-ups from Tasker. But since I had been using Tasker even before rooting, I denied the request.
Are there any more precautions we need to take with regards to this.
odyssseus said:
I recently had the same op-ups from Tasker. But since I had been using Tasker even before rooting, I denied the request.
Are there any more precautions we need to take with regards to this.
Click to expand...
Click to collapse
Great question. If anybody else has experience/knowledge feel free to chime in.
Regarding precautions, there are a few basic steps which I think we're all fairly familiar with as being general computer precautions. These are a few which come to mind:
1) Don't load software you don't trust.
2) Always thorougly check the permissions being granted to an application. Example, once you grant an application permission to load at startup, it now has the potential to always be running in the background. Potential bad situation: the application *could* be gathering user/system data and if it has network access, sending this data back.
3) Superuser provides a great basic level of security to protect root access. Without superuser, any application can execute the su binary now running with root priviledges and there will be no required notification to the end user. This could all happen in the background w/o a log, audit trail or notification to the user. Root priviledges, as I mentioned above on an S-OFF EVO 3D will give write access to /system, /data, boot (kernel), recovery, etc. This is potentially very dangerous and important to protect the su binary.
Important to realize, once an application has been granted superuser access, it has the potential to destroy the device or grab extensive system/personal information and send it out. This makes it essential to trust the application.
As with any type of security, there are always ways to bypass. Essentially, these three steps should help avoid the majority of issues.
On a brighter note, there really aren't many Android viruses or malicious applications in circulation. For the most part, people who post on XDA and android application developers/posters in the market have are trustworthy. The comments on Market applications are usually fairly helpful. Might be worth skimming thru a page or 2, maybe 3 or 4 of market comments on a suspicious application or emailing the developer.
I know as a developer I'm more than happy to explain any function or question regarding my applications, especially if it raises a security/privacy concern to a user.
Hope that helps round out some simple precautions!
Why Reset Notify always ask for permissions, and what should I pick grant or deny ? And why system app wants root ?
mrpeev said:
Why Reset Notify always ask for permissions, and what should I pick grant or deny ? And why system app wants root ?
Click to expand...
Click to collapse
I denied it long back.. I dont think it has any drawback or something like that
can I remove it from my phone and will there be any negative effect ?
I have this issue,too.And even if i deny it,it keeps coming back
Sent from my HTC Desire X
same here...thats why I want to remove it but I dont know how this will affect
this happens to me too. i wonder what reset notify is
Sent from my HTC Desire X using xda app-developers app
isn't there an Option to automatically allow/deny requests from Certain Apps in superSU ?
BatEarsJoe said:
isn't there an Option to automatically allow/deny requests from Certain Apps in superSU ?
Click to expand...
Click to collapse
Yes there is, I used it for the reset notify and the init request
mrpeev said:
Why Reset Notify always ask for permissions, and what should I pick grant or deny ? And why system app wants root ?
Click to expand...
Click to collapse
Doesn't matter whether you pick grant or deny as that is not so important process.
You can even remove the apk without any impact on the ROM performance.
SuperSU made it a feature to scan all system user processes so if any "naughty" process that is not a system process but running as system user can be intercepted.
For me, I just tick the "Trust system user" in SuperSU settings.
yea I did the same this morning...thanks anyway
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
njaustin123 said:
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
Click to expand...
Click to collapse
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
dimm0k said:
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
Click to expand...
Click to collapse
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
Whenever you do a clean fresh flash Rom at the setup most rooms let you restore all your previous apps from google, no need to go to the play store it does it automatic. If you made a backup just restore the data.
Sent from my LG-H901 using XDA-Developers mobile app
dimm0k said:
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
Click to expand...
Click to collapse
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
I have witnessed this, mainly with Google apps. after restoring the app with data the app would randomly crash... removing the app and installing it from Google fixes it, but I have not experienced this with non-Google apps. I'll keep this in mind the next go around when restoring my stuff.
njaustin123 said:
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
Click to expand...
Click to collapse
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
after doing some research and from my understanding, the bad news is that it looks like it's up to devs to add the feature of writing to the external SD via the Storage Access Framework (SAF). unfortunately it doesn't look like an easy task, as the developer of Tasker mentioned that he won't be implementing this since the number of external SD users are far and few =( and would revisit it if that number changes.
the good news for those of us smart and brave enough to root our devices, this is solvable via editing packages.xml and adding in one line for each app you want to "fix". this is documented here
justice26 said:
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
works fine for me here... are you using stock ROM?
dimm0k said:
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
Click to expand...
Click to collapse
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
njaustin123 said:
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
Click to expand...
Click to collapse
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
dimm0k said:
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
Click to expand...
Click to collapse
OK, so here is it: I was able to mount /system as rw with the terminal emulator in ROM toolbox and then create a dummy file named su. Rebooted the phone, both the apps still fail. I will write to the developers. For the time being, I am OK turning data on/off manually along with using MyProfiles for other things. And for the One Power Guard, I believe freezing many of the T-Mobile and LG junk using Titanium and having SetCPU with a little bit under-clocking have already made the battery better. So I can wait. Am also evaluating Craig's Root Battery App instead of OPG. Thank you anyways.
After I root a phone, I would like to be able to uninstall/remove some stock apps (for example, stock Messaging app) and add some new apps (for example, 3d-party Messaging app).
Do I need Titanium app to achieve that? Or is there something more lightweight?
After I complete the setup, I want to disable/ restrict any further software changes. Pretty much the same as Window OS "Admin" VS "Standard User"
So I guess I would need some app manager capable of permission managing.
Any advice on my project? Will my phone be as stable as the original stock after such modding?
The phones: Moto E2 and Moto G2 and G3, Android 5.01 or 6.01
Well, Backing Up the Stock Content before doing any Modding to your Phone is a Good Practice and Extremely Recommended in Case of any worst case scenarios and you can achieve the same by Titanium Back or any Other app Readily available on Play Store.
After Back up, Yes, you can Uninstall PreInstalled apps or any other bloatware that you may don't want in your phone. And Install 3rd Party apps in place of stock Ones.
Talking about Permissions, until/unless you give Root Access to that App, it won't be able to Make any changes in the System. So, you also have to keep a check on giving Root permissions to apps.
Your Phone Will remain stable When you know what actually you are doing with it and what measures could be taken to revert it.
abhinavp649 said:
Talking about Permissions, until/unless you give Root Access to that App, it won't be able to Make a.
Click to expand...
Click to collapse
Once the phone is rooted, will I be able to block/restrict both: uninstalling apps (which are already installed) and installing new apps? The phone will be used by my kids, so I want to prevent them from making any phone changes.
rybshik said:
Once the phone is rooted, will I be able to block/restrict both: uninstalling apps (which are already installed) and installing new apps? The phone will be used by my kids, so I want to prevent them from making any phone changes.
Click to expand...
Click to collapse
You can't restrict to install and uninstall apps. As abhinavp649 said the application makes modifications to the system if you give root permission to them. If you are using SuperSU superuser app then you can set pin to grant root permission to the app from the settings of supersu
rybshik said:
Once the phone is rooted, will I be able to block/restrict both: uninstalling apps (which are already installed) and installing new apps? The phone will be used by my kids, so I want to prevent them from making any phone changes.
Click to expand...
Click to collapse
To Prevent app from uninstalling the best way is to hide it From Home screen Or Make that as System.
And Revoke SU permissions from those apps which can uninstall system apps or any similar one.
Hit thanks if Helped :laugh:
abhinavp649 said:
to hide it From Home screen Or Make that as System.:
Click to expand...
Click to collapse
How can I do that?
Additionally, can I, for example, turn on Location (GPS) and prevent the phone user from turning it OFF? thanks!
rybshik said:
How can I do that?
Additionally, can I, for example, turn on Location (GPS) and prevent the phone user from turning it OFF? thanks!
Click to expand...
Click to collapse
Installing an App as system is a easy and you can find tools easily on play store. Just search 'make app system' or something else similar.
Using GPS to prevent Turn off? I think you are expecting too too much out of a device.
However, you can disable Power Off from options you get by holding lock button.
To do this You Have to Install Xposed Framework in your Device.
Xposed Framework allows you to do Amazing modding to your Android device. You can just do everything with the device(Exceptions are always present)
rybshik said:
How can I do that?
Additionally, can I, for example, turn on Location (GPS) and prevent the phone user from turning it OFF? thanks!
Click to expand...
Click to collapse
If you are thinking of turning on GPS for the sake of tracking your kids, then make sure you tell them you are doing so. Have known a few people that got into legal trouble for not doing so.
In the end if the kids are smart enough there will be nothing you can really do as they can just reset the device and everything you did is gone.
zelendel said:
nothing you can really do as they can just reset the device
Click to expand...
Click to collapse
So, can I prevent that by disabling/removing or password-protecting the option of "Factory Reset" on a rooted Android 6.0?
rybshik said:
So, can I prevent that by disabling/removing or password-protecting the option of "Factory Reset" on a rooted Android 6.0?
Click to expand...
Click to collapse
No. You can not restrict or disable factory data reset option by any ways even you are rooted. Some brands like Samsung gives FRP (factory reset protection) to their device. Devices without FRP easily factory data reset by entering in recovery mode or in settings.