Hey,
I've got a question to the Ultimate Guide to Blocking Packages That Causes 60% Battery Firmware (All Models).
Previously, I have disabled all packages over the application "package disabler pro". After an update, the packages are no longer displayed. So I have uninstalled the app.
In German forums they said after updating or uninstalling the app, packages are re-enabled.
I installed some more "Package Disabler" but i couldn't find any relevant packages to block.
Now to my problem blocking the update via ADB.
The ADB-Drivers are already installed.
After that I tried to block the update with "Disable_ADB.cmd". If the script says: Package "packagename" new hidden state: true
At my windows stands: Error: java.lang.SecurityException: Neither user 2000 nor current process has an droid.permission.MANAGE_USERS.
Do you have an idea? Do I need a rooted phone?
Sorry for my terrible english.
best regards
Sebastian
[SOLVED] Question to block the following Updates on my Note 7
Moderators: Junior Moderator, Jr. Admin
- Sebastian94
- Alliance Member
- Posts: 2
- Joined: Mon Dec 12, 2016 4:48 am
Last edited by NCqTee on Thu Dec 22, 2016 5:35 pm, edited 1 time in total.
- beowulf381
- Administrator
- Posts: 579
- Joined: Mon Dec 12, 2016 10:57 am
The error seems to have to do with android security updates. Originally this has nothing to do with Note 7, the development for this restriction was made earlier this year:
The following is from googlesource:
commit 01875b0274e74f97edf6b0d5c92de822e0555d03 [log] [tgz]
author Sudheer Shanka <[email protected]> Wed Jun 08 17:13:24 2016 -0700
committer The Android Automerger <[email protected]> Fri Jun 24 16:52:58 2016 -0700
and:
Reduce shell power over user management.
Remove MANAGE_USERS permission from shell and whitelist it for
some specific functionality.
So the developers decided to cripple the ADB functionality for non-root users.
This change will obviously implemented in different versions of firmware patches depending on your region / provider. Some reports said is was implemented in September or October, some found it already in August patch version.
Could test on an Note 7 with September security patch, here the debloater and ADB pm works without problems. The script here does the same as debloater, it will hide/deactivate the apk's via ADB method.
For you and those who get the error, maybe you can find another stock kernel / rom suitable for your device model that has this update not implemented yet.
And for a rooted device, it will work of course.
Just try one of the following disablers, described here:
http://note7alliance.com/viewtopic.php?p=693#p693
The following is from googlesource:
commit 01875b0274e74f97edf6b0d5c92de822e0555d03 [log] [tgz]
author Sudheer Shanka <[email protected]> Wed Jun 08 17:13:24 2016 -0700
committer The Android Automerger <[email protected]> Fri Jun 24 16:52:58 2016 -0700
and:
Reduce shell power over user management.
Remove MANAGE_USERS permission from shell and whitelist it for
some specific functionality.
So the developers decided to cripple the ADB functionality for non-root users.
This change will obviously implemented in different versions of firmware patches depending on your region / provider. Some reports said is was implemented in September or October, some found it already in August patch version.
Could test on an Note 7 with September security patch, here the debloater and ADB pm works without problems. The script here does the same as debloater, it will hide/deactivate the apk's via ADB method.
For you and those who get the error, maybe you can find another stock kernel / rom suitable for your device model that has this update not implemented yet.
And for a rooted device, it will work of course.
Just try one of the following disablers, described here:
http://note7alliance.com/viewtopic.php?p=693#p693
Last edited by beowulf381 on Wed Dec 14, 2016 4:22 pm, edited 1 time in total.
- Sebastian94
- Alliance Member
- Posts: 2
- Joined: Mon Dec 12, 2016 4:48 am
@Catwoman my carrier is 1&1 (Vodafone) in Germany.
The device ordered directly by Samsung.
If I find time next week, I will looking for a ROM with an older security patch.
For the first time, I fixed the problem with the second variant in the guide, so I'm safe befor the 30% update but this is not the optimal solution.
Really thanks for your great help to find the error
best regards
The device ordered directly by Samsung.
If I find time next week, I will looking for a ROM with an older security patch.
For the first time, I fixed the problem with the second variant in the guide, so I'm safe befor the 30% update but this is not the optimal solution.
Really thanks for your great help to find the error
best regards
