How to restrict/block access to settings with adb and is it possible to do it with no root.If impossible (and only if impossible) with no root other no root alternatives would be appreciated.
I'm doing this bc everytime I restart my phone the third party apps that should block access to settings aren't started as yet so it leaves an opening for settings to be accessed.
I am a noob with adb so a little explanation would be very welcome.
Today is Monday said:
How to restrict/block access to settings with adb and is it possible to do it with no root.If impossible (and only if impossible) with no root other no root alternatives would be appreciated.
I'm doing this bc everytime I restart my phone the third party apps that should block access to settings aren't started as yet so it leaves an opening for settings to be accessed.
I am a noob with adb so a little explanation would be very welcome.
Click to expand...
Click to collapse
Probably not. If you want to control things on your device other than the things you have installed yourself, it almost always requires root. There are apps and tools that claim to be able to do things without root but they are not effective.
Droidriven said:
Probably not. If you want to control things on your device other than the things you have installed yourself, it almost always requires root. There are apps and tools that claim to be able to do things without root but they are not effective.
Click to expand...
Click to collapse
So disabling specific UI Buttons would also need root?
Today is Monday said:
So disabling specific UI Buttons would also need root?
Click to expand...
Click to collapse
It may or may not depend on which buttons you mean and on what you mean by disable, I suppose. But, generally, modifying the kinds of things you want to modify requires root because the things that need to be accessed and modified are in the system partition, the user has no control of system without root. Without root the user can generally only access, use, read/write/delete and modify things in the data or data/media partitions(userspace).
Droidriven said:
It may or may not depend on which buttons you mean and on what you mean by disable, I suppose. But, generally, modifying the kinds of things you want to modify requires root because the things that need to be accessed and modified are in the system partition, the user has no control of system without root. Without root the user can generally only access, use, read/write/delete and modify things in the data or data/media partitions(userspace).
Click to expand...
Click to collapse
Nvm the sheer no. of buttons that give access to settings make it that it would probably be better to disable the pull down feature altogether not even gonna mention the no. of the buttons outside the pull down feature.
Is there anyway without root to just make my phone inaccessible for 2-3 mins after it starts up so it can load the third party apps that block settings? I'm feeling pretty hopeless rn tbh.
Today is Monday said:
Nvm the sheer no. of buttons that give access to settings make it that it would probably be better to disable the pull down feature altogether not even gonna mention the no. of the buttons outside the pull down feature.
Is there anyway without root to just make my phone inaccessible for 2-3 mins after it starts up so it can load the third party apps that block settings? I'm feeling pretty hopeless rn tbh.
Click to expand...
Click to collapse
You've already been given the answer to that question. As stated, the things that need to be changed in order to get the result that you want, requires root.
Requires root
Requires root
Requires root
Again...
It requires root.
Why does it require root? Because you cannot access the system partition without root. The system apps are loaded first, then user apps are loaded during startup, therefore, the system apps will always beat the third party apps to the punch, unless you root the device and do something like modify parts of the system partition or add your third party apps to the system partition so that they load when the system loads during startup.
Droidriven said:
You've already been given the answer to that question. As stated, the things that need to be changed in order to get the result that you want, requires root.
Requires root
Requires root
Requires root
Again...
It requires root.
Why does it require root? Because you cannot access the system partition without root. The system apps are loaded first, then user apps are loaded during startup, therefore, the system apps will always beat the third party apps to the punch, unless you root the device and do something like modify parts of the system partition or add your third party apps to the system partition so that they load when the system loads during startup.
Click to expand...
Click to collapse
Thx for answering. Sorry if I annoyed you didn't mean to
Related
I am brand new to the Android stuff and the learning curve is rather large. I am pretty well versed in modding iPhones and RIM devices. From what I have read thus far and am trying to confrim.
2.3.3 Just recently has been temp rooted on this device?
Temp or Full rooting is required to remove the bloatware crap?
SDK is installed and ADB is working. I followed the temp rooting method and was able to get SU #.
With that being done is that enough to start removing the junk?
What app should I used to delete the apk's? or should it be done in ADB Shell?
Is there anything that I should backup while I'm at this?
ounvme said:
I am brand new to the Android stuff and the learning curve is rather large. I am pretty well versed in modding iPhones and RIM devices. From what I have read thus far and am trying to confrim.
2.3.3 Just recently has been temp rooted on this device?
Temp or Full rooting is required to remove the bloatware crap?
SDK is installed and ADB is working. I followed the temp rooting method and was able to get SU #.
With that being done is that enough to start removing the junk?
What app should I used to delete the apk's? or should it be done in ADB Shell?
Is there anything that I should backup while I'm at this?
Click to expand...
Click to collapse
You can delete the apk's in system/app
I normally use the Root Explorer app, but you can use adb shell as well
just cd into /system/app and do rm Twitter.apk for example
Root will disappear on reboot, and the bloatware will return unfortunately =/
Stuke00 said:
You can delete the apk's in system/app
I normally use the Root Explorer app, but you can use adb shell as well
just cd into /system/app and do rm Twitter.apk for example
Root will disappear on reboot, and the bloatware will return unfortunately =/
Click to expand...
Click to collapse
Thank you for the reply. I will wait for a more permanent solution. Are the apps reinstalled on reboot or are they never truely removed? It's annoying to have programs forced on a device that I paid for. If I didn't install it then I dont want or use it. I'm a big fan of simple and clean. I am sure something will be out soon to allow this. Thanks again!!!
This reminds me of buying a laptop that has all kinds of junk on it and looking for drivers to make it work with a clean install.....Such a pain in the ass.
ounvme said:
Thank you for the reply. I will wait for a more permanent solution. Are the apps reinstalled on reboot or are they never truely removed? It's annoying to have programs forced on a device that I paid for. If I didn't install it then I dont want or use it. I'm a big fan of simple and clean. I am sure something will be out soon to allow this. Thanks again!!!
This reminds me of buying a laptop that has all kinds of junk on it and looking for drivers to make it work with a clean install.....Such a pain in the ass.
Click to expand...
Click to collapse
I tried it with the temp root, I didn't even have to reboot before the apps reappeared. :S We gotta wait for either permanent root or S-OFF (not really too different in this case I think) to remove the apps, and by that time we can just go and install a custom ROM with the apps removed already.
I'm looking forward to permanent root at the moment, this being my first Android phone. And with recent developments, like the temp root and Revolutionary being tested on the Shift, I'd say the future looks good. So keep an eye out.
Racer_X_NFS said:
I tried it with the temp root, I didn't even have to reboot before the apps reappeared. :S We gotta wait for either permanent root or S-OFF (not really too different in this case I think) to remove the apps, and by that time we can just go and install a custom ROM with the apps removed already.
I'm looking forward to permanent root at the moment, this being my first Android phone. And with recent developments, like the temp root and Revolutionary being tested on the Shift, I'd say the future looks good. So keep an eye out.
Click to expand...
Click to collapse
lol that sucks. Yeah... need to get S-OFF!
I am gaining much interest in the custom rom idea. I however have the time and the drive to want to read up and learn to do it myself. If full device customization is available I would like to be able to do so.
I have done some reading here and some google searching but is there any 1 place where I can find full info on cooking my own rom?
The main things that I want to change is disable the side button to not control ringer volume. Add native volume control for all audible things. Remove bloatware and add certin apps.
I know there are apps to control all of this, but if its possible to have it funcion at the system level...why not learn how to do it. Things like this are fun to me and I like mind challenging tasks.
Like I stated I have the time I just need to be schooled where the proper most current place to start is.
Obviously this will just be practice and learning until a full root/backup is available.
Thanks
I am a NOOB, but I like myself just fine. The video for NOOBs is funny, but IMHO, should be a bit more serious.
I'm one of those people experiencing issues with GPS and TTFF being excessively long on the MT. Cry.
If I run MyPhoneExplorer, I can see the system file structure, and I believe I can move files to the phone. I believe I can do the same with SwiFTP.
Can one drop replacement GPS libraries for example into the SYSTEM and SYSTEM/HW sub-directories using a program like MPE, or an FTP program like SwiFTP without rooting, and would they be honored on the next reboot?
Would I be mangling some check-sum or other that determines the integrity of the system loaded?
I'm one of those users that doesn't really want to root if not necessary, but I wonder if doing some mod like the above - would doing so lay subsequent update pushes from VMUSA to waste?
Also, I'd really like if possible to flag some programs not to load, unless I explicitly ask them to load via the U.I. with intent. I suppose I'd have to root to do something like that. Perhaps with Ginger-Break? Would doing this make subsequent updates problematic?
Any information regarding my constraints and options to effect both of the above would be very appreciated. Thanks.
There are ways to mount the various partitions from a host machine (e.g. Linux) while it is in the "emergency" flash mode, which would permit what you want to do. Doing this is quite dangerous - at least as much as rooting the device and perhaps more-so.
I appreciate the response.
OK, if I were to root via Gingerbreak and install the files that way, then un-root, would my system then appear to be (to an update provided by Motorola or VMUSA) as something which couldn't be updated?
In other-words would rooting put me on a path to having to use specially modified updates?
Thanks.
Depends on what you change.
In GENERAL no, the update will come through. The major risk is that it crashes on install as some part of what you changed is a dependency but is not reloaded. This is rare, but can happen.
So.... root, install Clockwork, and make an immediate Nandroid backup BEFORE you screw with anything. That SHOULD allow you to un-hose yourself if you get in trouble.
This is something I have been wondering for a while and after searching the forums and Google I have not been able to find a clear answer. As a long time Linux user the idea of running your system as root all the time is appalling. It is a huge security risk. But for some reason that is really the only way to gain root access on an Android device (as far as i am aware). Apps like SuperSU allow you to pick the apps that are allowed to run as root, but there is no password or verification that the entity approving the access actually has the authority to do so. I hear all the time that rooting your phone is a trade-off between customizability and security, but every Linux system has a root user and it is incredibly secure when properly administered. What is the reason for the difference?
From what I have read, it sounds like part of the issue has to do with Android handling users differently. I would love to be able to maintain a more limited root function on my devices. Thanks.
funkbuqet said:
This is something I have been wondering for a while and after searching the forums and Google I have not been able to find a clear answer. As a long time Linux user the idea of running your system as root all the time is appalling. It is a huge security risk. But for some reason that is really the only way to gain root access on an Android device (as far as i am aware). Apps like SuperSU allow you to pick the apps that are allowed to run as root, but there is no password or verification that the entity approving the access actually has the authority to do so. I hear all the time that rooting your phone is a trade-off between customizability and security, but every Linux system has a root user and it is incredibly secure when properly administered. What is the reason for the difference?
From what I have read, it sounds like part of the issue has to do with Android handling users differently. I would love to be able to maintain a more limited root function on my devices. Thanks.
Click to expand...
Click to collapse
You can set a passcode with SuperSU....
Thanks for the reply. That is good to know. Does that really fill the security gap though? I guess if I set My non-background root permissions to expire every 15 minutes that does help for apps that do not need to run as root in the background.
I am more referring to the distinction between regular user land and the root user. Titanium Backup for example; If I want it to be able to run a full backup (including system apps and settings) of my phone every night I have to give it permanent root permissions. That root permission applies to both the automatic process and anything that I as a user (or any entity that can get control of TB) to act as root as well. Ideally there would be 2 separate instances of the program; the back-up process (a daemon perhaps) initiated by the root user and a second available in regular user space. This sort of thing is common on Linux systems.
My knowledge of Android is not particularly deep. I cannot tell if there is actually a separate root user or how user/group permissions work. It seems that the Android framework is designed around the user not having root access. Which is a bit confusing for an OS that prides itself on customization and "Be together not the same". I can't imagine buying a desktop PC that didn't allow me to have system level (root) access. Why should it be any different on a mobile device?
I'm no pro, so forgive anything stupid I may say in advance. I recently learned that any android application has permission to see any application installed on your device. I'm a bit of a privacy nut, and I have concerns with this for a plethora of reasons. I was hoping to learn of a method that would allow me to somehow prevent apps from being able to see what's installed, or at minimum, mask the actual application names so the data an app gets is useless for any purposes they may have for it.
Is there any way to achieve such a thing?
I'm no pro either, but what I do is I use two apps to accomplish this. The first is MyAppSharer (no root required). The second is Advanced Permission Manager (again, no root required). Both can be found on the play store.
First I use MyAppSharer to create an .apk of the app I want to isolate. Place it In the download folder (or any folder of your choosing). Next I install the .apk with Advanced Permission Manager. While installing simply uncheck the 'view other apps permission' or whatever it's called and that might work.
The only concern I have is that apps usually check to see if they have access to all their permissions before startup, and if one is missing it might either not allow you to launch the app or or will crash. Or it'll work perfectly fine and all's well
Good luck
I think you need to hide apps and permission manager. For me, I used to use Greenify, the ForceStop as permission manager, which are available on xposed module repository, but they both require root.
For hiding apps, maybe the "PrivateMe" can help you, it also can hide photos, install apps in hidden mode.
Dresden_ said:
I'm no pro, so forgive anything stupid I may say in advance. I recently learned that any android application has permission to see any application installed on your device. I'm a bit of a privacy nut, and I have concerns with this for a plethora of reasons. I was hoping to learn of a method that would allow me to somehow prevent apps from being able to see what's installed, or at minimum, mask the actual application names so the data an app gets is useless for any purposes they may have for it.
Is there any way to achieve such a thing?
Click to expand...
Click to collapse
The sudo hide xposed module is exactly what you want to figure out
You will get first list of apps where you have to select ''which app to hide"
Then you will get second list of apps where you can select "from which apps to hide that app"
If you want any help regarding xposed,reply me back
Please push the thanks button if it helped
Enjoy:victory::victory:
Regards milkyway3
For whatever reason Onyx Boox devices only seem to have PIN as an option for security. I would prefer the standard pattern lock if possible. Is there a reliable way to activate or reinstall that option? I don't mind rooting or going through extra steps with adb to do so.
jptiger said:
For whatever reason Onyx Boox devices only seem to have PIN as an option for security. I would prefer the standard pattern lock if possible. Is there a reliable way to activate or reinstall that option? I don't mind rooting or going through extra steps with adb to do so.
Click to expand...
Click to collapse
You can try searching to see if there any 3rd party apps that have pattern lock as an option.
Or
You can root your device and then pull a copy of the system app/apps that controls screen lock then decompile the app in APKeditor then modify the contents of the .apk to add a pattern lock feature then recompile the new apk and install it on your device then boot into recovery and wipe only the cache partition and/or dalvik cache but do not factory reset or wipe data then reboot the device to let the new system changes load.
(I don't see a way to delete this message so I'm editing it instead. It was a duplicate)
Droidriven said:
You can try searching to see if there any 3rd party apps that have pattern lock as an option.
Or
You can root your device and then pull a copy of the system app/apps that controls screen lock then decompile the app in APKeditor then modify the contents of the .apk to add a pattern lock feature then recompile the new apk and install it on your device then boot into recovery and wipe only the cache partition and/or dalvik cache but do not factory reset or wipe data then reboot the device to let the new system changes load.
Click to expand...
Click to collapse
I guess what I'm hoping for is either a specific recommendation for the former (apps like this have decidedly mixed reviews with many including obtrusive ads or malfunctioning and locking you out of your device more permanently) or specific instructions/ packages to help do the latter. I doubt I'm the first person with this kind of device to have this sort of request and would like to know how those who came before me handled it.
jptiger said:
I guess what I'm hoping for is either a specific recommendation for the former (apps like this have decidedly mixed reviews with many including obtrusive ads or malfunctioning and locking you out of your device more permanently) or specific instructions/ packages to help do the latter. I doubt I'm the first person with this kind of device to have this sort of request and would like to know how those who came before me handled it.
Click to expand...
Click to collapse
I did some searching for how to set that up on your device, the only thing I found mentioned using one of those 3rd party apps with ads. But, with root, you can use ad blockers or create a custom host file to potentially prevent the ads.