Revision history for ManagerIssues


Revision [1041]

Last edited on 2021-09-24 08:53:40 by didgeridoohan
Additions:
===**There are two Magisk apps**===
Deletions:
===**There are two Magisk app**===

Revision [1027]

Edited on 2021-05-15 06:33:48 by didgeridoohan
Additions:
If you're having issues with the Magisk app force closing/crashing/freezing at any point, clear data for the app or uninstall it and install it again. Note that you might have two apps installed, the regular Magisk app and a hidden one with a random package name. You'll need to uninstall both...
Deletions:
If you're having issues with the Magisk app force closing/crashing/freezing at any point, clear data for the app or uninstall it and install it again.

Revision [1005]

Edited on 2021-03-01 07:05:46 by didgeridoohan
Additions:
If there suddenly are two Magisk app in your app drawer, this might be caused by somehow installing a new app while having the old one repackaged (hidden) with a random package name. It can happen when updating Magisk, and usually if you install the app apk manually, or if you use the Magisk zip in recovery while having a repackaged app installed. Also, the uninstaller zip (the Magisk app apk renamed to uninstall.zip) cannot uninstall the repackaged app (since it doesn't know the random package name), and you'll have to uninstall the old app manually. Or something else... If the duplicate app doesn't disappear (it'll be uninstalled by the "real" app) after you open the one named just "Manager" (or whatever name you've picked), the best thing is probably just to uninstall both and install the app again (apk can be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub]]). It might also be necessary to delete /data/adb/magisk.db. Also see //"Can't hide the Magisk app"// below.
Deletions:
If there suddenly are two Magisk app in your app drawer, this might be caused by somehow installing a new app while having the old one repackaged (hidden) with a random package name. It can happen when updating Magisk, and usually if you install the app apk manually, or if you use the Magisk zip in recovery while having a repackaged app installed. Also, the uninstaller zip (the Magisk app apk renamed to uninstall.zip) cannot uninstall the repackaged app (since it doesn't know the random package name), and you'll have to uninstall the old app manually. Or something else... If the duplicate app doesn't disappear (it'll be uninstalled by the "real" app) after you open the one named just "Manager" (or whatever name you've picked), the best thing is probably just to uninstall both and install the app again (apk can be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub]] or in the Magisk zip's common folder). Aldo see //"Can't hide the Magisk app"// below.

Revision [983]

Edited on 2021-02-23 08:39:17 by didgeridoohan
Additions:
=====**{{color text="Magisk app Issues" c="blue"}}**=====
===**Can't install the Magisk app**===
If the Magisk app doesn't get installed when you flash the Magisk zip, or that you're trying to install the apk manually and it doesn't work, you might first have to remove remnants of an old installation. This can be done through ADB. Start by uninstalling any currently installed app (especially if it's repackaged with a random package name) and then just run the following command from ADB Shell and you should be good to go:
//"There was a problem while parsing the package"//. If you see this message while trying to update the app and the app is hidden, go to the app settings and choose to //"Restore Magisk app "//. The new app release will be downloaded and installed with the regular package name and you'll just have to rehide the app again afterwards.
If you don't have the app hidden, but still see this message, try clearing the app cache, or if that doesn't work uninstalling the app and reinstalling it again (you'll find the apk on [[https://github.com/topjohnwu/Magisk/releases | GitHub]]).
If there are issues with the Magisk app, it's often a good idea to clear data for the app. All your granted superuser requests and apps added to the MagiskHide list will still be intact (since they're saved elsewhere).
If the information for the latest available Magisk or app just show N/A you either do not have internet access (or you have something blocking internet access for the app), or you might have an invalid link set for the custom update channel in the app settings. This could be, for example, caused by the links to the Canary channel json file has changed.
Tip: Instead of putting the link to the Canary channel in a custom update channel, simply download the Canary app from [[https://github.com/topjohnwu/Magisk | GitHub]] and pick the make sure the Canary update channel is selecte in the app settings. That way you won't have to keep track on if and when topjohnwu changes the link.
===**Magisk app crashes/freezes**===
If you're having issues with the Magisk app force closing/crashing/freezing at any point, clear data for the app or uninstall it and install it again.
The app crashing might also be caused by using a theme engine to theme the app (Substratum, etc). Disable it and reapply after an update to the app .
==**Magisk app installed to external/adoptable storage**==
Installing the Magisk app to an external or adoptable storage is known to cause issues. Reinstall it to the internal storage.
==**Magisk app as a system app**==
Another reported reason for the app crashing is if you've for some reason added the Magisk app as a system app. If this is the case try de-systemising to see if that fixes the issue.
If the app crashes when pressing the "Install from storage" button in the Modules window, it's likely caused by your ROM not having a file explorer installed. Install one from [[https://f-droid.org/ | F-Droid]] or the [[https://play.google.com/store/apps | Play Store]].
===**There are two Magisk app**===
If there suddenly are two Magisk app in your app drawer, this might be caused by somehow installing a new app while having the old one repackaged (hidden) with a random package name. It can happen when updating Magisk, and usually if you install the app apk manually, or if you use the Magisk zip in recovery while having a repackaged app installed. Also, the uninstaller zip (the Magisk app apk renamed to uninstall.zip) cannot uninstall the repackaged app (since it doesn't know the random package name), and you'll have to uninstall the old app manually. Or something else... If the duplicate app doesn't disappear (it'll be uninstalled by the "real" app) after you open the one named just "Manager" (or whatever name you've picked), the best thing is probably just to uninstall both and install the app again (apk can be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub]] or in the Magisk zip's common folder). Aldo see //"Can't hide the Magisk app"// below.
It's also possible that you'll get two apps installed when trying to hide (repackage) the app. If you have made the app a system app, or the ROM you're using has the app pre-installed as a system app, the repackaging feature can't uninstall the old app (because it's a system app) after having installed the new one with a random package name (the app might get stuck on "Hiding it now"). Remove the app from /system/app or /system/priv-app (depending on where you or the ROM creator have placed it). If the app comes pre-installed as a system app, please let your ROM creator know that it's a bad idea to include the app like this.
If your ROM doesn't come with the Magisk app installed as a system app, or you haven't made the app into a system app, if disabling Play Protect doesn't help, or if the app can't be hidden/repackaged at all, please provide details and logs //(see [[MagiskHelp | "Asking for help/reporting bugs"]])//.
===**Can't hide the Magisk app**===
First thing to try is to temporarily disable Play Protect in the Play Store. From v7.4.0 the app uses a stub apk to hide fully on Android 9+ systems. This sometimes triggers Play Protect which will silently block the install, and you'll just get a "Hide Magisk app failed" message. On some devices this might be caused by SELinux issues, so if the above doesn't work, try changing SELinux to permissive when you hide the app.
If you have a Xiaomi device and MIUI, you might have to turn on "Install via USB" in Developer options before trying to hide the app.
===**Can't restore the Magisk app**===
If you can't restore the Magisk app, either that it gives an error or nothing happens at all, the easiest way is to simply uninstall the hidden/repackaged app and install the apk manually. The latest stable app apk can always be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub ]].
It might be necessary to remove any remnants of old installs through ADB before the app can install again //(see "Can't install the Magisk app" above)//.
It's very likely that nothing is actually wrong. Take a look at [[MagiskModuleIssues | "A module has been updated but doesn't show up in the Magisk app"]] for details.
Deletions:
=====**{{color text="Magisk Manager Issues" c="blue"}}**=====
===**Can't install the Magisk Manager**===
If the Magisk Manager doesn't get installed when you flash the Magisk zip, or that you're trying to install the apk manually and it doesn't work, you might first have to remove remnants of an old installation. This can be done through ADB. Start by uninstalling any currently installed Manager (especially if it's repackaged with a random package name) and then just run the following command from ADB Shell and you should be good to go:
//"There was a problem while parsing the package"//. If you see this message while trying to update the Manager and the Manager is hidden, go to the app settings and choose to //"Restore Magisk Manager"//. The new Manager release will be downloaded and installed with the regular package name and you'll just have to rehide the Manager again afterwards.
If you don't have the Manager hidden, but still see this message, try clearing the app cache, or if that doesn't work uninstalling the Manager and reinstalling it again (you'll find the apk on [[https://github.com/topjohnwu/Magisk/releases | GitHub]] or in the /common directory of the Magisk installation zip).
If there are issues with the Magisk Manager, it's often a good idea to clear data for the app. All your granted superuser requests and apps added to the MagiskHide list will still be intact (since they're saved elsewhere).
If the information for the latest available Magisk or Manager just show N/A you either do not have internet access (or you have something blocking internet access for the Manager), or you might have an invalid link set for the custom update channel in the Manager settings. This could be, for example, caused by the links to the Canary channel json file has changed.
Tip: Instead of putting the link to the Canary channels in a custom update channel, simply download the Canary Manager from the [[https://github.com/topjohnwu/Magisk | GitHub]] and pick the Canary update channel of your choice in the settings. That way you won't have to keep track on if and when topjohnwu changes the link.
===**Magisk Manager crashes/freezes**===
If you're having issues with the Magisk Manager force closing/crashing/freezing at any point, clear data for the Manager or uninstall it and install it again.
The Manager crashing might also be caused by using a theme engine to theme the Manager (Substratum, etc). Disable it and reapply after an update to the Manager.
==**Magisk Manager installed to external/adoptable storage**==
Installing the Magisk Manager to an external or adoptable storage is known to cause issues. Reinstall it to the internal storage.
==**Magisk Manager as a system app**==
Another reported reason for the Manager crashing is if you've for some reason added the Magisk Manager as a system app. If this is the case try de-systemising to see if that fixes the issue.
If the Manager crashes when pressing the "Install from storage" button in the Modules window, it's likely caused by your ROM not having a file explorer installed. Install one from [[https://f-droid.org/ | F-Droid]] or the [[https://play.google.com/store/apps | Play Store]].
===**There are two Magisk Managers**===
If there suddenly are two Magisk Managers in your app drawer, this might be caused by somehow installing a new Manager while having the old one repackaged (hidden) with a random package name. It can happen when updating Magisk, and usually if you install the Manager apk manually, or if you use the Magisk zip in recovery while having a repackaged Manager installed. Also, the uninstaller zip cannot uninstall the repackaged Manager (since it doesn't know the random package name), and you'll have to uninstall the old Manager manually. Or something else... If the duplicate Manager doesn't disappear (it'll be uninstalled by the "real"Manager) after you open the one named just "Manager" (or whatever name you've picked), the best thing is probably just to uninstall both and install the Manager again (apk can be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub]] or in the Magisk zip's common folder). Aldo see //"Can't hide the Magisk Manager"// below.
It's also possible that you'll get two Managers installed when trying to hide (repackage) the Manager. If you have made the Manager a system app, or the ROM you're using has the Manager pre-installed as a system app, the repackaging feature can't uninstall the old Manager (because it's a system app) after having installed the new one with a random package name (the Manager might get stuck on "Hiding it now"). Remove the Manager from /system/app or /system/priv-app (depending on where you or the ROM creator have placed it). If the app comes pre-installed as a system app, please let your ROM creator know that it's a bad idea to include the Manager like this.
If your ROM doesn't come with the Magisk Manager installed as a system app, or you haven't made the Manager into a system app, if disabling Play Protect doesn't help, or if the Manager can't be hidden/repackaged at all, please provide details and logs //(see [[MagiskHelp | "Asking for help/reporting bugs"]])//.
===**Can't hide the Magisk Manager**===
First thing to try is to temporarily disable Play Protect in the Play Store. From v7.4.0 the Manager uses a stub apk to hide fully on Android 9+ systems. This sometimes triggers Play Protect which will silently block the install, and you'll just get a "Hide Magisk Manager failed" message. On some devices this might be caused by SELinux issues, so if the above doesn't work, try changing SELinux to permissive when you hide the Manager.
If you have a Xiaomi device and MIUI, you might have to turn on "Install via USB" in Developer options before trying to hide the Manager.
===**Can't restore the Magisk Manager**===
If you can't restore the Magisk Manager, either that it gives an error or nothing happens at all, the easiest way is to simply uninstall the hidden/repackaged Manager and install the apk manually. The latest stable Manager apk can always be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub ]].
It might be necessary to remove any remnants of old installs through ADB before the Manager can install again //(see "Can't instll the Magisk Manager" above)//.
It's very likely that nothing is actually wrong. Take a look at [[MagiskModuleIssues | "A module has been updated but doesn't show up in the Manager"]] for details.

Revision [950]

Edited on 2020-11-11 07:24:06 by didgeridoohan
Additions:
It's very likely that nothing is actually wrong. Take a look at [[MagiskModuleIssues | "A module has been updated but doesn't show up in the Manager"]] for details.
Deletions:
It's very likely that nothing is actually wrong. Take a look at [[MagiskModuleIssues | "A module has been updated but doesn't show up in the Manage"]] for details.

Revision [949]

Edited on 2020-11-11 07:23:56 by didgeridoohan
Additions:
It's very likely that nothing is actually wrong. Take a look at [[MagiskModuleIssues | "A module has been updated but doesn't show up in the Manage"]] for details.
Deletions:
It's very likely that nothing is actually wrong. Take a look at [[MagiskModulesIssues | "A module has been updated but doesn't show up in the Manage"]] for details.

Revision [948]

Edited on 2020-11-11 07:23:34 by didgeridoohan
Additions:
It's very likely that nothing is actually wrong. Take a look at [[MagiskModulesIssues | "A module has been updated but doesn't show up in the Manage"]] for details.
Deletions:
It's very likely that nothing is actually wrong. Take a look at [[MagiskModulesIssues |"" A module has been updated but doesn't show up in the Manage"]] for details.

Revision [947]

Edited on 2020-11-11 07:23:16 by didgeridoohan
Additions:
===**Updates doesn't show up for modules**===
It's very likely that nothing is actually wrong. Take a look at [[MagiskModulesIssues |"" A module has been updated but doesn't show up in the Manage"]] for details.

Revision [942]

Edited on 2020-11-10 11:52:03 by didgeridoohan
Additions:
If there suddenly are two Magisk Managers in your app drawer, this might be caused by somehow installing a new Manager while having the old one repackaged (hidden) with a random package name. It can happen when updating Magisk, and usually if you install the Manager apk manually, or if you use the Magisk zip in recovery while having a repackaged Manager installed. Also, the uninstaller zip cannot uninstall the repackaged Manager (since it doesn't know the random package name), and you'll have to uninstall the old Manager manually. Or something else... If the duplicate Manager doesn't disappear (it'll be uninstalled by the "real"Manager) after you open the one named just "Manager" (or whatever name you've picked), the best thing is probably just to uninstall both and install the Manager again (apk can be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub]] or in the Magisk zip's common folder). Aldo see //"Can't hide the Magisk Manager"// below.
Deletions:
If there suddenly are two Magisk Managers in your app drawer, this might be caused by somehow installing a new Manager while having the old one repackaged (hidden) with a random package name. It can happen when updating Magisk, and usually if you install the Manager apk manually, or if you use the Magisk zip in recovery while having a repackaged Manager installed. Also, the uninstaller zip cannot uninstall the repackaged Manager (since it doesn't know the random package name), and you'll have to uninstall the old Manager manually. Or something else... If the duplicate Manager doesn't disappear after you open the one named just "Manager" (or whatever name you've picked), the best thing is probably just to uninstall both and install the Manager again (apk can be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub]] or in the Magisk zip's common folder). Aldo see //"Can't hide the Magisk Manager"// below.

Revision [940]

Edited on 2020-11-10 11:45:46 by didgeridoohan
Additions:
If there suddenly are two Magisk Managers in your app drawer, this might be caused by somehow installing a new Manager while having the old one repackaged (hidden) with a random package name. It can happen when updating Magisk, and usually if you install the Manager apk manually, or if you use the Magisk zip in recovery while having a repackaged Manager installed. Also, the uninstaller zip cannot uninstall the repackaged Manager (since it doesn't know the random package name), and you'll have to uninstall the old Manager manually. Or something else... If the duplicate Manager doesn't disappear after you open the one named just "Manager" (or whatever name you've picked), the best thing is probably just to uninstall both and install the Manager again (apk can be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub]] or in the Magisk zip's common folder). Aldo see //"Can't hide the Magisk Manager"// below.
Deletions:
If there suddenly are two Magisk Managers in your app drawer, this might be caused by somehow installing a new Manager while having the old one repackaged (hidden) with a random package name. It can happen when updating Magisk, it happens if you install the Manager apk manually, or if you use the uninstaller zip in recovery while having a repackaged Manager installed, and then flashing a new Magisk zip. The uninstaller zip cannot uninstall the repackaged Manager (since it doesn't know the random package name), and you'll have to uninstall the old Manager manually. Or something else... If the duplicate Manager doesn't disappear after you open the one named just "Manager", best thing is probably just to uninstall both and install the Manager again (apk can be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub]] or in the Magisk zip's common folder). Aldo see //"Can't hide the Magisk Manager"// below.

Revision [921]

Edited on 2020-11-03 02:59:36 by didgeridoohan
Additions:
===**Latest show "N/A"**===
If the information for the latest available Magisk or Manager just show N/A you either do not have internet access (or you have something blocking internet access for the Manager), or you might have an invalid link set for the custom update channel in the Manager settings. This could be, for example, caused by the links to the Canary channel json file has changed.
Tip: Instead of putting the link to the Canary channels in a custom update channel, simply download the Canary Manager from the [[https://github.com/topjohnwu/Magisk | GitHub]] and pick the Canary update channel of your choice in the settings. That way you won't have to keep track on if and when topjohnwu changes the link.
If the Manager crashes when pressing the "Install from storage" button in the Modules window, it's likely caused by your ROM not having a file explorer installed. Install one from [[https://f-droid.org/ | F-Droid]] or the [[https://play.google.com/store/apps | Play Store]].
Deletions:
===**Menus and buttons are missing**===
If there are a bunch of menus and buttons missing in the Manager (Install, ""SafteyNet"" check, Download, etc), and the main Manager window is only showing the currently installed version and the Uninstall button, you'll have to enable data or Wi-Fi and make sure that nothing is blocking data for the Manager. It needs internet access for these features to function.
===**Stuck on "Checking for updates"**===
If the Manager is constantly stuck on "Checking for updates" you likely have an invalid link set for the custom update channel in the Manager settings. This could be, for example, caused by the links to the Canary channel json file has changed.
Tip: Instead of putting the link to the Canary channels in a custom update channel, simply download the Canary Manager from the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary thread]] and pick the Canary update channel of your choice in the settings. That way you won't have to keep track on if and when topjohnwu changes the link.
If the Manager crashes when pressing the "+" button in the Modules tab, it's likely caused by your ROM not having a file explorer installed. Install one from [[https://f-droid.org/ | F-Droid]] or the [[https://play.google.com/store/apps | Play Store]].

Revision [908]

Edited on 2020-10-09 04:59:35 by didgeridoohan
Additions:
If you have a Xiaomi device and MIUI, you might have to turn on "Install via USB" in Developer options before trying to hide the Manager.
Deletions:
If you have a Xiaomi device and MIUI, you might have to turn on "Install from USB" in Developer options before trying to hide the Manager.

Revision [907]

Edited on 2020-10-06 17:08:46 by didgeridoohan
Additions:
If you have a Xiaomi device and MIUI, you might have to turn on "Install from USB" in Developer options before trying to hide the Manager.

Revision [887]

Edited on 2020-08-30 03:17:17 by didgeridoohan
Additions:
//"There was a problem while parsing the package"//. If you see this message while trying to update the Manager and the Manager is hidden, go to the app settings and choose to //"Restore Magisk Manager"//. The new Manager release will be downloaded and installed with the regular package name and you'll just have to rehide the Manager again afterwards.
If you don't have the Manager hidden, but still see this message, try clearing the app cache, or if that doesn't work uninstalling the Manager and reinstalling it again (you'll find the apk on [[https://github.com/topjohnwu/Magisk/releases | GitHub]] or in the /common directory of the Magisk installation zip).
Deletions:
//"There was a problem while parsing the package"//. If you see this message while trying to update the Manager, go to the app settings and choose to //"Restore Magisk Manager"//. The new Manager release will be downloaded and installed with the regular package name and you'll just have to rehide the Manager again afterwards.
If you don't have the Manager hidden, but still see this message, try uninstalling the Manager and reinstalling it again, manually (you'll find the apk on [[https://github.com/topjohnwu/Magisk/releases | GitHub]] or in the /common directory of the Magisk installation zip).

Revision [861]

Edited on 2020-06-19 05:41:02 by didgeridoohan

No Differences

Revision [860]

Edited on 2020-06-19 05:40:08 by didgeridoohan

No Differences

Revision [787]

Edited on 2020-01-15 08:52:28 by didgeridoohan
Additions:
First thing to try is to temporarily disable Play Protect in the Play Store. From v7.4.0 the Manager uses a stub apk to hide fully on Android 9+ systems. This sometimes triggers Play Protect which will silently block the install, and you'll just get a "Hide Magisk Manager failed" message. On some devices this might be caused by SELinux issues, so if the above doesn't work, try changing SELinux to permissive when you hide the Manager.
Deletions:
First thing to try is to temporarily disable Play Protect in the Play Store. From v7.4.0 the Manager uses a stub apk to hide fully on Android 9+ systems. This sometimes triggers Play Protect which will silently block the install, and you'll just get a "Hide Magisk Manager failed" message.

Revision [770]

Edited on 2019-11-19 01:48:06 by didgeridoohan
Additions:
First thing to try is to temporarily disable Play Protect in the Play Store. From v7.4.0 the Manager uses a stub apk to hide fully on Android 9+ systems. This sometimes triggers Play Protect which will silently block the install, and you'll just get a "Hide Magisk Manager failed" message.
If your ROM doesn't come with the Magisk Manager installed as a system app, or you haven't made the Manager into a system app, if disabling Play Protect doesn't help, or if the Manager can't be hidden/repackaged at all, please provide details and logs //(see [[MagiskHelp | "Asking for help/reporting bugs"]])//.
Deletions:
If your ROM doesn't come with the Magisk Manager installed as a system app, or you haven't made the Manager into a system app, or if the Manager can't be hidden/repackaged at all, please provide details and logs //(see [[MagiskHelp | "Asking for help/reporting bugs"]])//.

Revision [767]

Edited on 2019-11-03 04:37:35 by didgeridoohan
Additions:
If you don't have the Manager hidden, but still see this message, try uninstalling the Manager and reinstalling it again, manually (you'll find the apk on [[https://github.com/topjohnwu/Magisk/releases | GitHub]] or in the /common directory of the Magisk installation zip).

Revision [745]

Edited on 2019-10-16 06:35:56 by didgeridoohan
Additions:
===**Stuck on "Checking for updates"**===
If the Manager is constantly stuck on "Checking for updates" you likely have an invalid link set for the custom update channel in the Manager settings. This could be, for example, caused by the links to the Canary channel json file has changed.
Tip: Instead of putting the link to the Canary channels in a custom update channel, simply download the Canary Manager from the [[https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 | Canary thread]] and pick the Canary update channel of your choice in the settings. That way you won't have to keep track on if and when topjohnwu changes the link.

Revision [731]

Edited on 2019-10-15 15:39:36 by didgeridoohan
Deletions:
@@{{image url="https://img.shields.io/badge/-PayPal-blue.svg" title="" alt="PayPal"}}
Please don't hesitate to [[https://www.paypal.me/didgeridoohan | support the work involved]] in keeping this guide alive.@@
----

Revision [718]

Edited on 2019-09-13 01:10:26 by didgeridoohan
Additions:
===**Problem parsing the package**===
Deletions:
===**Problem while parsing the package**===

Revision [715]

Edited on 2019-09-09 02:03:14 by didgeridoohan
Additions:
===**Problem while parsing the package**===
//"There was a problem while parsing the package"//. If you see this message while trying to update the Manager, go to the app settings and choose to //"Restore Magisk Manager"//. The new Manager release will be downloaded and installed with the regular package name and you'll just have to rehide the Manager again afterwards.

Revision [659]

Edited on 2019-07-22 14:27:12 by didgeridoohan
Additions:
@@{{image url="https://img.shields.io/badge/-PayPal-blue.svg" title="" alt="PayPal"}}
Please don't hesitate to [[https://www.paypal.me/didgeridoohan | support the work involved]] in keeping this guide alive.@@
----

Revision [608]

Edited on 2019-05-02 02:49:32 by didgeridoohan
Deletions:
===**Updating from Manager v6.1.0 to v7.0.0+ (Magisk v18.0 to v18.1+)**===
There's a bug in Manager v6.1.0 that will cause the update to a newer version to fail if you have Manager v6.1.0 [[https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_the_Magisk_Manager | hidden/repackaged]]. Before updating the Manager (or Magisk if updating by flashing the zip in recovery), [[https://www.didgeridoohan.com/magisk/MagiskHide#hn_Unhiding_the_Magisk_Manager | restore the Manager to its original package name]] and things should work fine. See [[MagiskUpdating | "Updating from v18.0 to v18.1+"]] for more details.

Revision [604]

Edited on 2019-04-16 02:39:36 by didgeridoohan
Additions:
If there suddenly are two Magisk Managers in your app drawer, this might be caused by somehow installing a new Manager while having the old one repackaged (hidden) with a random package name. It can happen when updating Magisk, it happens if you install the Manager apk manually, or if you use the uninstaller zip in recovery while having a repackaged Manager installed, and then flashing a new Magisk zip. The uninstaller zip cannot uninstall the repackaged Manager (since it doesn't know the random package name), and you'll have to uninstall the old Manager manually. Or something else... If the duplicate Manager doesn't disappear after you open the one named just "Manager", best thing is probably just to uninstall both and install the Manager again (apk can be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub]] or in the Magisk zip's common folder). Aldo see //"Can't hide the Magisk Manager"// below.
Deletions:
If there suddenly are two Magisk Managers in your app drawer, this might be caused by somehow installing a new Manager while having the old one repackaged (hidden) with a random package name. It can happen when updating Magisk, it happens if you install the Manager apk manually, or if you use the uninstaller zip in recovery while having a repackaged Manager installed, and then flashing a new Magisk zip. The uninstaller zip cannot uninstall the repackaged Manager (since it doesn't know the random package name), and you'll have to uninstall the old Manager manually. Or something else... If the duplicate Manager doesn't disappear after you open the one named just "Manager", best thing is probably just to uninstall both and install the Manager again (apk can be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub]] or in the Magisk zip's common folder).

Revision [602]

Edited on 2019-03-03 16:19:59 by didgeridoohan
Additions:
If there are a bunch of menus and buttons missing in the Manager (Install, ""SafteyNet"" check, Download, etc), and the main Manager window is only showing the currently installed version and the Uninstall button, you'll have to enable data or Wi-Fi and make sure that nothing is blocking data for the Manager. It needs internet access for these features to function.
Deletions:
If there are a bunch of menus and buttons missing in the Manager (Install, SafteyNet check, Download, etc), and the main Manager window is only showing the currently installed version and the Uninstall button, you'll have to enable data or Wi-Fi and make sure that nothing is blocking data for the Manager. It needs internet access for these features to function.

Revision [584]

Edited on 2019-02-11 10:39:43 by didgeridoohan
Additions:
There's a bug in Manager v6.1.0 that will cause the update to a newer version to fail if you have Manager v6.1.0 [[https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_the_Magisk_Manager | hidden/repackaged]]. Before updating the Manager (or Magisk if updating by flashing the zip in recovery), [[https://www.didgeridoohan.com/magisk/MagiskHide#hn_Unhiding_the_Magisk_Manager | restore the Manager to its original package name]] and things should work fine. See [[MagiskUpdating | "Updating from v18.0 to v18.1+"]] for more details.
Deletions:
There's a but in Manager v6.1.0 that will cause the update to a newer version to fail if you have Manager v6.1.0 [[https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_the_Magisk_Manager | hidden/repackaged]]. Before updating the Manager (or Magisk if updating by flashing the zip in recovery), [[https://www.didgeridoohan.com/magisk/MagiskHide#hn_Unhiding_the_Magisk_Manager | restore the Manager to its original package name]] and things should work fine. See [[MagiskUpdating | "Updating from v18.0 to v18.1+"]] for more details.

Revision [583]

Edited on 2019-02-11 10:39:24 by didgeridoohan
Additions:
===**Updating from Manager v6.1.0 to v7.0.0+ (Magisk v18.0 to v18.1+)**===
There's a but in Manager v6.1.0 that will cause the update to a newer version to fail if you have Manager v6.1.0 [[https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_the_Magisk_Manager | hidden/repackaged]]. Before updating the Manager (or Magisk if updating by flashing the zip in recovery), [[https://www.didgeridoohan.com/magisk/MagiskHide#hn_Unhiding_the_Magisk_Manager | restore the Manager to its original package name]] and things should work fine. See [[MagiskUpdating | "Updating from v18.0 to v18.1+"]] for more details.

Revision [573]

Edited on 2019-02-08 00:18:16 by didgeridoohan
Additions:
If the Magisk Manager doesn't get installed when you flash the Magisk zip, or that you're trying to install the apk manually and it doesn't work, you might first have to remove remnants of an old installation. This can be done through ADB. Start by uninstalling any currently installed Manager (especially if it's repackaged with a random package name) and then just run the following command from ADB Shell and you should be good to go:
Deletions:
If the Magisk Manager doesn't get installed when you flash the Magisk zip, or that you're trying to install the apk manually and it doesn't work, you might first have to remove remnants of an old installation. This can be done through ADB. Just run the following command from ADB Shell and you should be good to go:

Revision [572]

Edited on 2019-02-04 11:07:03 by didgeridoohan
Additions:
If there suddenly are two Magisk Managers in your app drawer, this might be caused by somehow installing a new Manager while having the old one repackaged (hidden) with a random package name. It can happen when updating Magisk, it happens if you install the Manager apk manually, or if you use the uninstaller zip in recovery while having a repackaged Manager installed, and then flashing a new Magisk zip. The uninstaller zip cannot uninstall the repackaged Manager (since it doesn't know the random package name), and you'll have to uninstall the old Manager manually. Or something else... If the duplicate Manager doesn't disappear after you open the one named just "Manager", best thing is probably just to uninstall both and install the Manager again (apk can be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub]] or in the Magisk zip's common folder).
Deletions:
If there suddenly are two Magisk Managers in your app drawer, this might be caused by somehow installing a new Manager while having the old one repackaged (hidden) with a random package name. It happens if you install the Manager apk manually, or if you use the uninstaller zip in recovery while having a repackaged Manager installed, and then flashing a new Magisk zip. The uninstaller zip cannot uninstall the repackaged Manager (since it doesn't know the random package name), and you'll have to uninstall the old Manager manually. Or something else... Best practice if it happens is usually to uninstall both and install the Manager again (apk can be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub]]).

Revision [567]

Edited on 2019-01-18 14:53:07 by didgeridoohan
Additions:
If there suddenly are two Magisk Managers in your app drawer, this might be caused by somehow installing a new Manager while having the old one repackaged (hidden) with a random package name. It happens if you install the Manager apk manually, or if you use the uninstaller zip in recovery while having a repackaged Manager installed, and then flashing a new Magisk zip. The uninstaller zip cannot uninstall the repackaged Manager (since it doesn't know the random package name), and you'll have to uninstall the old Manager manually. Or something else... Best practice if it happens is usually to uninstall both and install the Manager again (apk can be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub]]).
Deletions:
If there suddenly are two Magisk Managers in your app drawer, this might be caused by somehow installing a new Manager while having the old one repackaged (hidden) with a random package name. It happens if you install the Manager apk manually, or if you use the uninstaller zip in recovery while having a repackaged Manager installed, and then flashing a new Magisk zip. The uninstaller zip cannot uninstall the repackaged Manager (since it doesn't know the random package name), and you'll have to uninstall the old Manager manually. Or something else... Best practice if it happens is to uninstall both and install the Manager again (apk can be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub]]).

Revision [566]

Edited on 2019-01-18 14:52:54 by didgeridoohan
Additions:
If there suddenly are two Magisk Managers in your app drawer, this might be caused by somehow installing a new Manager while having the old one repackaged (hidden) with a random package name. It happens if you install the Manager apk manually, or if you use the uninstaller zip in recovery while having a repackaged Manager installed, and then flashing a new Magisk zip. The uninstaller zip cannot uninstall the repackaged Manager (since it doesn't know the random package name), and you'll have to uninstall the old Manager manually. Or something else... Best practice if it happens is to uninstall both and install the Manager again (apk can be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub]]).
Deletions:
If there suddenly are two Magisk Managers in your app drawer, this might be caused by somehow installing a new Manager while having the old one repackaged (hidden) with a random package name. It happens if you install the Manager apk manually, or if you use the uninstaller zip in recovery while having a repackaged Manager installed, and then flashing a new Magisk zip. The uninstaller zip cannot uninstall the repackaged Manager (since it doesn't know the random package name), and you'll have to uninstall the old Manager manually.

Revision [565]

Edited on 2019-01-17 00:54:15 by didgeridoohan
Additions:
===**Can't install the Magisk Manager**===
If the Magisk Manager doesn't get installed when you flash the Magisk zip, or that you're trying to install the apk manually and it doesn't work, you might first have to remove remnants of an old installation. This can be done through ADB. Just run the following command from ADB Shell and you should be good to go:
%%adb uninstall com.topjohnwu.magisk%%
===**Can't restore the Magisk Manager**===
If you can't restore the Magisk Manager, either that it gives an error or nothing happens at all, the easiest way is to simply uninstall the hidden/repackaged Manager and install the apk manually. The latest stable Manager apk can always be found on [[https://github.com/topjohnwu/Magisk/releases | GitHub ]].
It might be necessary to remove any remnants of old installs through ADB before the Manager can install again //(see "Can't instll the Magisk Manager" above)//.

Revision [489]

Edited on 2018-11-14 06:13:52 by didgeridoohan
Additions:
If there still are issues, capture a [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | logcat]] from the crash/freeze and post it in the [[https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382 | support thread]] or as an [[https://github.com/topjohnwu/Magisk/issues | issue on GitHub]] (just make sure to do it [[https://github.com/topjohnwu/Magisk#bug-reports | properly]]), with a detailed description of the problem //(also see [[MagiskHelp | "Asking for help/reporting bugs"]])//.
Deletions:
If there still are issues, capture a [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | logcat]] from the crash/freeze and post it in the [[https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382 | support thread]] or as an [[https://github.com/topjohnwu/Magisk/issues | issue on GitHub]] (just make sure to do it properly), with a detailed description of the problem //(also see [[MagiskHelp | "Asking for help/reporting bugs"]])//.

Revision [488]

Edited on 2018-11-14 06:12:42 by didgeridoohan
Additions:
If there still are issues, capture a [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | logcat]] from the crash/freeze and post it in the [[https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382 | support thread]] or as an [[https://github.com/topjohnwu/Magisk/issues | issue on GitHub]] (just make sure to do it properly), with a detailed description of the problem //(also see [[MagiskHelp | "Asking for help/reporting bugs"]])//.
Deletions:
If there still are issues, capture a [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | logcat]] from the crash/freeze and post it in the [[https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382 | support thread]], with a detailed description of the problem //(also see [[MagiskHelp | "Asking for help/reporting bugs"]])//.

Revision [487]

Edited on 2018-11-14 06:08:07 by didgeridoohan
Additions:
==**Magisk Manager installed to external/adoptable storage**==
Installing the Magisk Manager to an external or adoptable storage is known to cause issues. Reinstall it to the internal storage.
Another reported reason for the Manager crashing is if you've for some reason added the Magisk Manager as a system app. If this is the case try de-systemising to see if that fixes the issue.
Deletions:
Another reported reason for the Manager crashing is if you've for some reason added the Magisk Manager as a system app or installed it to your external storage. Try de-systemising or reinstalling it to the internal storageand see if that fixes the issue.

Revision [472]

Edited on 2018-10-18 06:43:11 by didgeridoohan
Additions:
===**Clearing cache and data**===
If there are issues with the Magisk Manager, it's often a good idea to clear data for the app. All your granted superuser requests and apps added to the MagiskHide list will still be intact (since they're saved elsewhere).

Revision [417]

Edited on 2018-09-04 01:50:18 by didgeridoohan
Additions:
If you're having issues with the Magisk Manager force closing/crashing/freezing at any point, clear data for the Manager or uninstall it and install it again.
Deletions:
If you're having issues with the Magisk Manager force closing/crashing/freezing at any point, clear data for the Manager or uninstall it and install it again. //Uninstall the Manager by clicking on the “Uninstall” button in the Manager and choosing “Uninstall App”.// This way all Manager related files will be removed.

Revision [396]

Edited on 2018-08-20 10:58:15 by didgeridoohan
Additions:
If your ROM doesn't come with the Magisk Manager installed as a system app, or you haven't made the Manager into a system app, or if the Manager can't be hidden/repackaged at all, please provide details and logs //(see [[MagiskHelp | "Asking for help/reporting bugs"]])//.
Deletions:
If the Manager can't be hidden/repackaged at all, please provide details and logs //(see [[MagiskHelp | "Asking for help/reporting bugs"]])//.

Revision [395]

Edited on 2018-08-19 02:40:20 by didgeridoohan
Additions:
It's also possible that you'll get two Managers installed when trying to hide (repackage) the Manager. If you have made the Manager a system app, or the ROM you're using has the Manager pre-installed as a system app, the repackaging feature can't uninstall the old Manager (because it's a system app) after having installed the new one with a random package name (the Manager might get stuck on "Hiding it now"). Remove the Manager from /system/app or /system/priv-app (depending on where you or the ROM creator have placed it). If the app comes pre-installed as a system app, please let your ROM creator know that it's a bad idea to include the Manager like this.
Deletions:
It's also possible that you'll get two Managers installed when trying to hide (repackage) the Manager. If you have made the Manager a system app, or the ROM you're using has the Manager pre-installed as a system app, the repackaging feature can't uninstall the old Manager (because it's a system app) after having installed the new one with a random package name. Remove the Manager from /system/app or /system/priv-app (depending on where you or the ROM creator have placed it). If the app comes pre-installed as a system app, please let your ROM creator know that it's a bad idea to include the Manager like this.

Revision [368]

Edited on 2018-07-20 23:49:54 by didgeridoohan
Additions:
If the Manager can't be hidden/repackaged at all, please provide details and logs //(see [[MagiskHelp | "Asking for help/reporting bugs"]])//.
Deletions:
If the Manager can't be hidden/repackaged at all, please provide logs //(see [[MagiskHelp | "Asking for help"]])//.

Revision [367]

Edited on 2018-07-20 23:48:34 by didgeridoohan
Additions:
If the Manager can't be hidden/repackaged at all, please provide logs //(see [[MagiskHelp | "Asking for help"]])//.

Revision [361]

Edited on 2018-07-19 15:40:30 by didgeridoohan
Additions:
==**Theming**==
==**Magisk Manager as a system app**==
==**Trying to install modules in the Modules tab**==
==**Cant' fix**==
Deletions:
**Theming**
**Magisk Manager as a system app**
**Trying to install modules in the Modules tab**
**Cant' fix**

Revision [352]

Edited on 2018-07-19 15:26:07 by didgeridoohan
Additions:
**Theming**
**Magisk Manager as a system app**
**Trying to install modules in the Modules tab**
**Cant' fix**
Deletions:
==**Theming**==
==**Magisk Manager as a system app**==
==**Trying to install modules in the Modules tab**==
==**Cant' fix**==

Revision [351]

Edited on 2018-07-19 15:24:21 by didgeridoohan
Additions:
==**Theming**==
==**Magisk Manager as a system app**==
==**Trying to install modules in the Modules tab**==
==**Cant' fix**==

Revision [350]

Edited on 2018-07-19 15:22:23 by didgeridoohan
Additions:
If the Manager crashes when pressing the "+" button in the Modules tab, it's likely caused by your ROM not having a file explorer installed. Install one from [[https://f-droid.org/ | F-Droid]] or the [[https://play.google.com/store/apps | Play Store]].

Revision [342]

Edited on 2018-07-19 10:01:12 by didgeridoohan
Additions:
===**Menus and buttons are missing**===
If there are a bunch of menus and buttons missing in the Manager (Install, SafteyNet check, Download, etc), and the main Manager window is only showing the currently installed version and the Uninstall button, you'll have to enable data or Wi-Fi and make sure that nothing is blocking data for the Manager. It needs internet access for these features to function.

Revision [336]

Edited on 2018-07-19 09:51:31 by didgeridoohan
Additions:
Another reported reason for the Manager crashing is if you've for some reason added the Magisk Manager as a system app or installed it to your external storage. Try de-systemising or reinstalling it to the internal storageand see if that fixes the issue.
Deletions:
Another reported reason for the Manager crashing is if you've for some reason added the Magisk Manager as a system app. Try de-systemising it and see if that fixes the issue.

Revision [333]

Edited on 2018-07-19 09:45:31 by didgeridoohan
Additions:
===**Can't hide the Magisk Manager**===
It's also possible that you'll get two Managers installed when trying to hide (repackage) the Manager. If you have made the Manager a system app, or the ROM you're using has the Manager pre-installed as a system app, the repackaging feature can't uninstall the old Manager (because it's a system app) after having installed the new one with a random package name. Remove the Manager from /system/app or /system/priv-app (depending on where you or the ROM creator have placed it). If the app comes pre-installed as a system app, please let your ROM creator know that it's a bad idea to include the Manager like this.
Deletions:
==**Can't hide the Magisk Manager**==
It's also possible that this happens when trying to hide (repackage) the Manager. If you have made the Manager a system app, or the ROM you're using has the Manager pre-installed as a system app, the repackaging feature can't uninstall the old Manager (because it's a system app) after having installed the new one with a random package name. Remove the Manager from /system/app or /system/priv-app (depending on where you or the ROM creator have placed it). If the app comes pre-installed as a system app, please let your ROM creator know that it's a bad idea to include the Manager like this.

Revision [332]

Edited on 2018-07-19 09:45:02 by didgeridoohan
Additions:
==**Can't hide the Magisk Manager**==

Revision [331]

Edited on 2018-07-19 09:42:13 by didgeridoohan
Additions:
It's also possible that this happens when trying to hide (repackage) the Manager. If you have made the Manager a system app, or the ROM you're using has the Manager pre-installed as a system app, the repackaging feature can't uninstall the old Manager (because it's a system app) after having installed the new one with a random package name. Remove the Manager from /system/app or /system/priv-app (depending on where you or the ROM creator have placed it). If the app comes pre-installed as a system app, please let your ROM creator know that it's a bad idea to include the Manager like this.
Deletions:
It's also possible that this happens when trying to hide (repackage) the Manager. If the ROM you're using has the Manager pre-installed as a system app, the repackaging feature can't uninstall the old Manager (because it's a system app) after having installed the new one with a random package name. Remove the Manager from /system/app or /system/priv-app (depending on where the ROM creator have placed it), and then let the ROM creator know that it's a bad idea to include the Manager as a system app.

Revision [330]

Edited on 2018-07-19 09:40:36 by didgeridoohan
Additions:
If there suddenly are two Magisk Managers in your app drawer, this might be caused by somehow installing a new Manager while having the old one repackaged (hidden) with a random package name. It happens if you install the Manager apk manually, or if you use the uninstaller zip in recovery while having a repackaged Manager installed, and then flashing a new Magisk zip. The uninstaller zip cannot uninstall the repackaged Manager (since it doesn't know the random package name), and you'll have to uninstall the old Manager manually.
It's also possible that this happens when trying to hide (repackage) the Manager. If the ROM you're using has the Manager pre-installed as a system app, the repackaging feature can't uninstall the old Manager (because it's a system app) after having installed the new one with a random package name. Remove the Manager from /system/app or /system/priv-app (depending on where the ROM creator have placed it), and then let the ROM creator know that it's a bad idea to include the Manager as a system app.
Deletions:
If there suddenly are two Magisk Managers in your app drawer, this is caused by somehow installing a new Manager while having the old one repackaged (hidden) with a random package name. It happens if you install the Manager apk manually, or if you use the uninstaller zip in recovery while having a repackaged Manager installed, and then flashing a new Magisk zip. The uninstaller zip cannot uninstall the repackaged Manager (since it doesn't know the random package name), and you'll have to uninstall the old Manager manually.

Revision [320]

The oldest known version of this page was created on 2018-07-19 09:26:32 by didgeridoohan
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki