Related
Hello, When I try to turn off the mini s3 I have this message "security policy restricts power off" ; I search in google but I found nothing Can somebody help me please ? N.B: I cant do the factory reset from the setting and I cant enter to the recovery mode
octopus82 said:
Hello, When I try to turn off the mini s3 I have this message "security policy restricts power off" ; I search in google but I found nothing Can somebody help me please ? N.B: I cant do the factory reset from the setting and I cant enter to the recovery mode
Click to expand...
Click to collapse
Google Apps Device Policy for Android application enforces policies on your Android device that protect it should it get lost or stolen. Once you install this application on your Android, your administrator can set up security measures such as password protection so only you can sign in. And the device can be wiped remotely if you lose it.
Uninstall Google Apps Device Policy
There are two ways to uninstall Google Apps Device Policy. The easisest is to unregister all accounts associated with the Device Policy app and then uninstall the app. To do this, follow these steps:
On your Android device, open the Device Policy app and press Unregister on the Status screen for each account you have registered with the device.
Exit the Device Policy app and on your Android, go to Settings > Applications > Manage Applications and select the Device Policy app.
Press Uninstall and OK to remove the application.
Alternatively, you can uninstall Google Apps Device Policy by following these steps:
On your Android device, go to Settings > Security.
Press Select device administrators.
Uncheck Google Apps Device Policy.
Press Deactivate and OK.
Go to Settings > Applications > Manage Applications and select the Device Policy app.
Press Uninstall and OK to remove the application.
If your Google Apps administrator is enforcing device policies on your device, when you uninstall Device Policy, your device will stop syncing with your Google Apps account.
gummygum said:
Google Apps Device Policy for Android application enforces policies on your Android device that protect it should it get lost or stolen. Once you install this application on your Android, your administrator can set up security measures such as password protection so only you can sign in. And the device can be wiped remotely if you lose it.
Uninstall Google Apps Device Policy
There are two ways to uninstall Google Apps Device Policy. The easisest is to unregister all accounts associated with the Device Policy app and then uninstall the app. To do this, follow these steps:
On your Android device, open the Device Policy app and press Unregister on the Status screen for each account you have registered with the device.
Exit the Device Policy app and on your Android, go to Settings > Applications > Manage Applications and select the Device Policy app.
Press Uninstall and OK to remove the application.
Alternatively, you can uninstall Google Apps Device Policy by following these steps:
On your Android device, go to Settings > Security.
Press Select device administrators.
Uncheck Google Apps Device Policy.
Press Deactivate and OK.
Go to Settings > Applications > Manage Applications and select the Device Policy app.
Press Uninstall and OK to remove the application.
If your Google Apps administrator is enforcing device policies on your device, when you uninstall Device Policy, your device will stop syncing with your Google Apps account.
Click to expand...
Click to collapse
Thank's
I dont found Google Apps Device Policy in the device, and there's no registered account; when I Select device administrators there's nothing to cheking only desactivate the service but it not work !
I cant do any factory or hard reset, no recovery mode, and I try to code to do a factory reset but it not work !
I will try to flash an rooted rom but I dont know if it do a wipe data
Can you suggest some solution for hard reset please ?
Thank's
Update (28. Sep. 2014):
Did some more research on that matter for I found this really annoying. Deactivated Apps shall remain deactivated, even more so for as long as we don't have root yet.
Figured finally out (reproducible) that it's Disabling Device Administrators to trigger (some) Apps to get activated again.
Steps to reproduce:
Goto Settings -> Apps -> All
Deactivate e.g. Chrome, Google+, Hangouts, File Commander, Gmail, Maps, Play Store, Sony Select or Video Unlimited (so it's not only the GAPPS coming back).
Check the App Drawer, all the above should no longer be visible.
Goto Settings -> Security -> Device Administrators: Disable a Device Admin (BTW: Enabling does not re-activate Apps, only deactivation!)
Check the App Drawer again and find all of the above deactivated Apps have re-appeared.
This works in 23.0.A.2.98 (customized DE) as well as 23.0.A.2.105 (customized UK).
Sony: please fix this asap.
Devs: please, please give us root. The phone is worth it
Original assumption (OUTDATED):
Noticed a strange behaviour in builds 23.0.A.2.98 (customized DE) and builds 23.0.A.2.105 (customized UK) w.r.t. deactivated Apps getting automatically re-activated after changing language settings.
Started off with 23.0.A.2.98 (customized DE) on my phone and deactivated e.g. Chrome, Google Play Store, Google Play Services and some other Apps. Now, as I wanted to make some screenshots in English, I changed language settings from German to English. That moment Chrome, Google Play Services and otheres (but not all of them) got automatically re-activated and also (re-)appeared in the App drawer. Changing the phone back to German did not help as still some Apps keep getting re-activated after say a re-start of the phone.
Then, installed 23.0.A.2.105 (customized UK), immediately set it to German during first boot, deactivated same apps as before and guess what... same here.
It looks as if whenever you set your phone to use a language different to the one for which the build was localized for this problems shows.
Can anyone please try and confirm?
This explains this reactivating of Apps. I was trying to deactivate Admin for the Sony Enterprise something. It re-activates automatically and reactivates some of the disabled apps. Not all though...
Very anoying. Especially that Sony gives themselves admin rights again after I deactivated it.... hmmm.
msm1111 said:
Very anoying. Especially that Sony gives themselves admin rights again after I deactivated it.... hmmm.
Click to expand...
Click to collapse
Happy to see (well, kind of, for it shouldn't be present in the first place) that finally someone has been able to reproduce the bug.
In order to get rid of admins "Sony Enterprise API" and "Sony My Xperia" do the following:
Download ADB and store it somewhere on you PC.
Enable USB debugging on the phone and connect it to your PC.
Open a command window and navigate to where you stored ADB.
Type "adb shell" at the prompt, hit ENTER and and the prompt changes to "[email protected]:/ $"
To block "Sony Enterprise API", issue command: "pm block com.sonymobile.enterprise.service"
To block "Sony My Xperia", issue command: "pm block com.sonymobile.mx.android"
While we are at that (though not an Admin, yet annoying), to block "What's New", issue command: "block com.sonymobile.advancedwidget.entrance".
The result of the block commands should look like "Package %PACKAGE_NAME% new blocked state: true. If still "false", you have to deactivate the corresponding admin in the settings first and re-issue the command again.
Only thing I have not been able to figure out yet is how to remove/block admin "Configuration Agent" but that one does not turn on itself (like the "Sony Enterprise API" does).
sxtester said:
Only thing I have not been able to figure out yet is how to remove/block admin "Configuration Agent" but that one does not turn on itself (like the "Sony Enterprise API" does).
Click to expand...
Click to collapse
Ah, thank you!
Configuration agent is: pm block com.sonymobile.deviceconfigtool
Wonderful, that removed my last (unwanted) one.
Thanks. I'll try it on Sunday! Is this enterprise stuff actually good for something? Or just tracking.
msm1111 said:
Thanks. I'll try it on Sunday! Is this enterprise stuff actually good for something? Or just tracking.
Click to expand...
Click to collapse
This is mainly for policy enforcement on mobiles given to employees by their company.
Check this for more info: http://developer.sonymobile.com/201...-work-with-our-sdk-and-become-a-sony-partner/
Just a quick note to say thanks to the guys who wrote this one up. I managed to follow the instructions and get rid of the whats new icon ive lost a bit of my touch though as this is not for those who don't know what sdk is.
pm block com.sonymobile.enterprise.service with this one I was getting: "False" without knowing how to change it to "true"
sxtester,
Thanks! It worked! I got rid of this stuff. I needed some attemps and reboots in between.
For "com.sonymobile.enterprise.service" you need to first disable admin and block "com.sonymobile.mx.android", reboot, then disable admin for the enterpriseAPI, block, reboot. Now its gone
I also successfully blocked "com.sonymobile.advancedwidget.entrance", "com.sony.smallapp.launcher" and "com.sony.smallapp.app.widget"
As I am not so familiar in adb, may I ask what is the difference between blocking and disabling (I guess its the same disable I can do in Settings/Apps)? I realized the blocked packages do not show up in the "pm list packages" anymore. Disabled ones do. Is there a list to see what was blocked? Thanks.
Btw I can also confirm that the OP is correct. When I first disabled Sony enterprise most or all of my disabled apps were re enabled.
Every thing worked great, thanks for help!
Thank you!!! Worked great Z3
PM BLOCK commands don't work...
I tried what was suggested above, but after I entered my ADB SHELL, the PM BLOCK command didn't work. I used the latest ADB that was installed on my system, but the only command that seems relevant to this was: PM DISABLE. I used that with the packages mentioned but they didn't get disabled. I had to disable them manually again after rebooting.
m0b1f0n3 said:
I tried what was suggested above, but after I entered my ADB SHELL, the PM BLOCK command didn't work. I used the latest ADB that was installed on my system, but the only command that seems relevant to this was: PM DISABLE. I used that with the packages mentioned but they didn't get disabled. I had to disable them manually again after rebooting.
Click to expand...
Click to collapse
As you didn't specify the version of ADB, try the following:
Download EasyRoot Tool from http://forum.xda-developers.com/showthread.php?t=2784900
Don't run the tool itself, it won't work on the Z3/Z3C! However, it contains a very slim ADB version 1.0.31 which worked for me.
Unpack the ZIP to a directory of your choice.
Open a CMD Window and navigate to %YOUR_FOLDER%\EasyRootTool v12.3\files
Connect you phone and issue the PM block commans as described above.
PM BLOCK commands still don't work...
sxtester,
Thanks for your response. I tried all sorts of ADB versions (1.0.25) including the one you suggested. I had no luck. Once I issued any of the commands above, I got the message: "Error: unknown command 'block'". I am not sure what more I can do at this point.
Any ideas?
m0b1f0n3 said:
sxtester,
Thanks for your response. I tried all sorts of ADB versions (1.0.25) including the one you suggested. I had no luck. Once I issued any of the commands above, I got the message: "Error: unknown command 'block'". I am not sure what more I can do at this point.
Any ideas?
Click to expand...
Click to collapse
I used "hide" command and it worked like a charm, i.e.: pm hide com.sony...
Hope it will help.
I rooted my moto g titan with twrp and installed cm13 to avoid device slowness. Now I want to know about the securities of the devices. Because when i googled for bank app security, personal data security and some forum said that jailbreak/rooted devices are very dangerous for this app and personal data like password and all.Is it true or they right about this?Because i love my device after rooting but in the other hand afraid of this stealing data thread.I have installed my banking app,whatsapp,gmail etc.Please help me is there any process to keep rooted device from stealing data.If it is true.
Root your device will let your app have more permission to read your data so your personal data may in danger with some unknown apps.
As the above post said.
When rooted it gives certain apps more permissions to your phone.
But only when rooted as I've read in many discussions such as that of Kaspersky Internet Security etc where they have mantioned malware apps which can take info from your phone without root.
Basic precautions :
Just browse safely : install adaway or use an adblock browser
Install an anitvirus and use Kaspersky internet Security (if you're paranoid about your bank details being stolen).
Use Google for more info.
So it's all about precautions...
Thanks a lot though
Ok. I am running magisk....made shell cmd task of data on and off...they work....but why when I click "use root", it says device doesn't appear rooted. Could magisk be the culprit? Thanks.
Tmobilefan906 said:
Ok. I am running magisk....made shell cmd task of data on and off...they work....but why when I click "use root", it says device doesn't appear rooted. Could magisk be the culprit? Thanks.
Click to expand...
Click to collapse
Tasker cannot detect root with MagiskSU. If you attempt to select the Use Root option, you get a toast: "Error, you device doesn't appear to be rooted." However, as mentioned here, if you preface a Run Shell command with /sbin/su -c, Magisk Manager will prompt to allow Tasker root access and your command will work.
Code:
/sbin/su -c "svc data enable"
axxbat said:
Tasker cannot detect root with MagiskSU. If you attempt to select the Use Root option, you get a toast: "Error, you device doesn't appear to be rooted." However, as mentioned here, if you preface a Run Shell command with /sbin/su -c, Magisk Manager will prompt to allow Tasker root access and your command will work.
Click to expand...
Click to collapse
Yes. I know the commands for it. Lol. The task still works when I click the play arrow button in task window, it just says no root when I click use root.
Tmobilefan906 said:
Yes. I know the commands for it. Lol. The task still works when I click the play arrow button in task window, it just says no root when I click use root.
Click to expand...
Click to collapse
Didn't mean to offend will give a try a Magisk-enabled ROM today and hope will be back with ideas
Tmobilefan906 said:
Yes. I know the commands for it. Lol. The task still works when I click the play arrow button in task window, it just says no root when I click use root.
Click to expand...
Click to collapse
Well. Original position:
- Used RR April 16, 2017 nightly build as fresh install
- recovered Tasker from TiB backup
- created new task
- to avoid cheating assumptions created Tasker's task shortcut to run the task.
Video link is below. Pay attention to LTE symbol in the beginning of the vid. Task's goal was to disable it. The task was run via desktop shortcut
https://drive.google.com/file/d/0B8jDZdXO_06aMW5GYVJIRjBfemM/view?usp=drivesdk
Arrgh.just saw - LTE link run down before the task run - Tasker spotted my homecells and tried to setup WiFi connection (but no WLAN settings were restored). Nevertheless, it changes nothing - Task call via shortcut didn't call any root complaints, did it?
P.S. no offences again. In the cast i've intentionally shown Magisk's superuser tab to demonstrate nothing but two apps had root access. But after restore Tasker asked for 'su' perms (baloon), and was granted. Maybe, skipped 'su' perms for Tasker is Your headache?
axxbat said:
Didn't mean to offend will give a try a Magisk-enabled ROM today and hope will be back with ideas
Click to expand...
Click to collapse
u didn't offend me at all
axxbat said:
Well. Original position:
- Used RR April 16, 2017 nightly build as fresh install
- recovered Tasker from TiB backup
- created new task
- to avoid cheating assumptions created Tasker's task shortcut to run the task.
Video link is below. Pay attention to LTE symbol in the beginning of the vid. Task's goal was to disable it. The task was run via desktop shortcut
https://drive.google.com/file/d/0B8jDZdXO_06aMW5GYVJIRjBfemM/view?usp=drivesdk
Arrgh.just saw - LTE link run down before the task run - Tasker spotted my homecells and tried to setup WiFi connection (but no WLAN settings were restored). Nevertheless, it changes nothing - Task call via shortcut didn't call any root complaints, did it?
P.S. no offences again. In the cast i've intentionally shown Magisk's superuser tab to demonstrate nothing but two apps had root access. But after restore Tasker asked for 'su' perms (baloon), and was granted. Maybe, skipped 'su' perms for Tasker is Your headache?
Click to expand...
Click to collapse
What u mean skipped su perms?
Tmobilefan906 said:
What u mean skipped su perms?
Click to expand...
Click to collapse
1:48 request dialog
Sorry for late reply. Could it be so that Tasker was asking for root permission, but was not granted? Also, guess, You've checked that Tasker is in Device Administrators?
Upd. Stupid assumption. You've said , the task works when running on its own, from Tasker, but pops up the warning, when 'Use root' is checked... Not a big specialist in Magisk, but, haven't You use something like 'Hide root from apps' or alike in Magisk?
axxbat said:
1:48 request dialog
Sorry for late reply. Could it be so that Tasker was asking for root permission, but was not granted? Also, guess, You've checked that Tasker is in Device Administrators?
Upd. Stupid assumption. You've said , the task works when running on its own, from Tasker, but pops up the warning, when 'Use root' is checked... Not a big specialist in Magisk, but, haven't You use something like 'Hide root from apps' or alike in Magisk?
Click to expand...
Click to collapse
I guess I'm not too worried about it. As long as the task works, I'm fine with it. Haha
Trying to use Secure Tools to disable volume warning Samsung S5 running Marshmallow. I installed everything and ran adb command. No error, but when I search for Secure Tools it says Not Installed. Then I read this doesn't work on Marshmallow?
My phone is NOT rooted. Any help would be much appreciated.
Thanks - Frankie
Frankie-o said:
Trying to use Secure Tools to disable volume warning Samsung S5 running Marshmallow. I installed everything and ran adb command. No error, but when I search for Secure Tools it says Not Installed. Then I read this doesn't work on Marshmallow?
My phone is NOT rooted. Any help would be much appreciated.
Thanks - Frankie
Click to expand...
Click to collapse
I'm confused. What app are you referring to? "AutoTool's secure settings" or the app "Secure settings" or something else that I'm missing?
TASKER and AUTO TOOLS
I guess I forgot to mention that I'm user Tasker to do this... Thank you.
Be very specific what you are using and what you are trying.
Trying to disable high volume warning on Samsung S5
Using Tasker Auto Tools to run a command on my phone that will allow me to override the Volume High Warning on the Samsung S5 phone. It's supposed to enable WRITE SECURE SETTINGS with this command - and the command runs fine but it's not working for me. But when I go back to the app and look for Secure Settings, it's not there.
adb shell pm grant com.joaomgcd.autotools android.permission.WRITE_SECURE_SETTINGS
Auto tools is a plugin to tasker.
The "adb shell pm grant com.joaomgcd.autotools android.permission.WRITE_SECURE_SETTINGS" is one of two steps required to give the type of system level OS access this tool needs. The first thing that should be done is to enable "allow modify system settings" for AutoTools.
From the AutoTools Secure Settings page:
To use this, AutoTools needs to be granted permission to change secure settings on your device
If you're on Android 6 or above click here to grant AutoTools the first Settings permission
Then follow these steps to grant AutoTools the Secure Settings permission:
Enable Developer Mode: Go to Android Settings -> About Phone and look for the Build Number option. Touch it multiple times until developer mode is enabled.
Enable USB Debugging: Go to Android Settings -> and look for the Developer Options option. In there, enable the USB debugging option.
Install ADB on your PC: Check here for a quick way to do it.
Connect device to PC: Connect your device to a PC and look on your phone. A prompt should show up asking you to allow your phone to be debugged by your PC. Accept this.
Grant permission: Open a command line on your PC and write
adb shell pm grant com.joaomgcd.autotools android.permission.WRITE_SECURE_SETTINGS
Congratulations, AutoTools should now be able to use the "Secure Settings" action!
Click to expand...
Click to collapse
Once those things are done ( I typically reboot for no good reason ☺ ), then go to tasker, add an action in a task, then: plugin -> Auto tools -> secure settings (scroll down the list) you'll end up in a screen where you can configure the AutoTools secure settings action.
WOW! I think I did it.. I just hope I can do it again - this was my "test" phone. I think I was messed up by doing the "search" for secure settings because it said it wasn't installed.. Yet I had looked for the secure settings option and didn't find before - although I had already done all the steps. Somehow I got on to a screen that said the app (I forget the exact words) didn't have permission to change the settings, and to press NO if I wanted to allow the permissions - and I pressed no! I had already created the task to disable the warning - but it's been so long, I'm not sure how I did that - but the bottom line is I think it's working.. I had found several sites that said this wouldn't work with Marshmallow unless the phone was rooted, and my phones are not rooted.. so that makes me skeptical, but I did a reboot, and the warning didn't come back. Thanks a ton for your help.. Let's hope I can re-create on the phone that really needs it.
In case this is found by someone else, many of those "how to use secure settings" posts from lollipop and marshmallow predate the (awareness of the) approach used by AutoTools. People spent a lot of effort trying to force an unsupported, outdated app (the original secure settings) to work in a systemless root environment.
I'm sad to say this did NOT work on my test phone.. It looked like it did, but it didn't.