You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Try to remember the blocking method you’ve used. Default is IFW + Disable. This is also the worst case scenario here. So, if you can’t remember it, assume it’s the default.
Take note of the packages and components that App Manager blocked. You can find them at /data/user/0/io.github.muntashirakon.AppManager/files/conf/ (assuming the user ID was 0). Rules for each app is saved in a file with format <package-name>.tsv (eg. io.github.muntashirakon.AppManager.tsv). If you only need the components blocked in a particular interval, you can do this by inspecting the modification date of the files.
Navigate to /data/secure/system/ifw (Android M or earlier) or /data/system/ifw (Android N onwards) and delete the noted packages or components. App Manager stores rules for each package in a file with format <package-name>.xml (eg. io.github.muntashirakon.AppManager.xml)
Navigate to /data/system/users/0/package-restrictions.xml, find the package names you noted earlier and delete all the XML tags called disabled-components.
Example: Say you’ve accidentally block the .MainActivity of App Manager. You should find an entry like this:
In order to ensure that you didn’t corrupt the file, you should copy this file to your PC, delete the entries, validate the file using any XML validator and copy it back to where it belongs. Also, none of these files are accessible from ADB without root, but you can do this in the recovery if it supports this. If the recovery doesn't offer a terminal or a file manager, use something like the Aroma FM.
The text was updated successfully, but these errors were encountered:
/data/user/0/io.github.muntashirakon.AppManager/files/conf/
(assuming the user ID was0
). Rules for each app is saved in a file with format<package-name>.tsv
(eg.io.github.muntashirakon.AppManager.tsv
). If you only need the components blocked in a particular interval, you can do this by inspecting the modification date of the files./data/secure/system/ifw
(Android M or earlier) or/data/system/ifw
(Android N onwards) and delete the noted packages or components. App Manager stores rules for each package in a file with format<package-name>.xml
(eg.io.github.muntashirakon.AppManager.xml
)/data/system/users/0/package-restrictions.xml
, find the package names you noted earlier and delete all the XML tags calleddisabled-components
.Example: Say you’ve accidentally block the
.MainActivity
of App Manager. You should find an entry like this:<disabled-components>
and ending with</disabled-components>
like this:In order to ensure that you didn’t corrupt the file, you should copy this file to your PC, delete the entries, validate the file using any XML validator and copy it back to where it belongs. Also, none of these files are accessible from ADB without root, but you can do this in the recovery if it supports this. If the recovery doesn't offer a terminal or a file manager, use something like the Aroma FM.
The text was updated successfully, but these errors were encountered: