Magisk General Support / Discussion

[meric57]

Hello J.Michael, Everything is ok for the moment the concern this one how to find magisk if it goes unavailable.
Without reflashing with odin, use the recovery boot, as on a pc, a restore to solve the problem.

 

[pndwal]

Hello thank you for your answers pndwal and J.Michael, ok I don't see why and how to reinstall following a third-party installation or other magisk which shows me not available and zygisk not available without going through odin...

Magisk (Magic Mask/root) is always installed in a real device's ramdisk... Thus root (superuser permission) exists regardless of any App...

The Magisk App is NOT Magisk (Mask); it's only a UI or 'dashboard' interface for Magisk...

Your issue is apparently not loss of Magisk/root... Only that the App (dashboard) becomes disconnected... Root still exists...

This issue commonly occurs when you have both the stub (hidden) App and the full (original apk package) App installed at the same time... There should only ever be one or the other...

The 'dashboard' displays/controls fail if you have two instances... (Like a car, installing dual controls requires specialised modifications.)

You have said you have the hidden App while your screenshot proved that the full App was also installed... That's why the App can't see or control Magisk/root status or functions...

If you simply uninstall one or other or both Apps and ensure only one is installed, you will see root/Magisk version in App again... Uninstalling Apps will not affect Magisk (the Magic Mask/root) itself, and you don't need to reflash using Odin etc as only the App (UI/'dashboard') is the issue...

Just uninstall stub or full Apps like any regular App and ensure you only have one App (instance) remaining, then check for Magisk/root...

Don't worry about losing configuration, modules etc as these are not stored in App data unlike regular app configurations... They are stored independently of Magisk App at /data/adb...

... the concern this one how to find magisk if it goes unavailable...

If you think you have lost root, run a terminal emulator app and type magisk -c to see current binary version. If Magisk is not installed, no version info will be returned... To check Magisk is running in the background, type magisk -V to see running daemon version code. If Magisk daemon is not running properly no version info will be returned...

You can check this whether any Magisk App is installed or not.

I hope this helps clarify the difference between Magisk (Magic Mask/root) installation and Magisk App (UI/'dashboard') installation for you...

Bien à vous, PW

 

[ipdev]

@badabing2003 @pndwal @J.Michael

Now that everyone has explained Magisk root vs. the Manager app.

Sorry.
I will always refer to the Magisk app as the Manager because that is what it is.
I have used Xposed and other(s) for too long to not refer to the application that allows you to setup, install modules, configure and control as the Manager.​

---

I would like to bump the other half of his question.

Hello, I would like to know the reason when installing an application or updating the fox manager apk or others. Magisk application is found unavailable.

My concern that I would like to know why as explained during an example installation yesterday I installed superNDS a DS nitendo emulator.

- Why would installing/updating a Module cause Magisk to fail for him.
- Why would installing an APK file even affect Magisk let alone cause it to fail.

I can not duplicate this part of the issue.
Any ideas on why this part of the issue would happen?

Cheers

PS.
I update and install modules, apks and even system updates with Magisk hidden (renamed).
Very rarely do I have an issue due to the Magisk app being renamed.

 

[J.Michael]

@badabing2003 @pndwal @J.Michael

Now that everyone has explained Magisk root vs. the Manager app.

Sorry.​

I will always refer to the Magisk app as the Manager because that is what it is.​

I have used Xposed and other(s) for too long to not refer to the application that allows you to setup, install modules, configure and control as the Manager.​

---

I would like to bump the other half of his question.





- Why would installing/updating a Module cause Magisk to fail for him.
- Why would installing an APK file even affect Magisk let alone cause it to fail.

I can not duplicate this part of the issue.
Any ideas on why this part of the issue would happen?

Cheers

PS.
I update and install modules, apks and even system updates with Magisk hidden (renamed).
Very rarely do I have an issue due to the Magisk app being renamed.

There is no denying that the Android app formerly known as "Magisk Manager" is a manager. The quibbling comes from John Wu declaring that he no longer wanted the app to be called "Magisk Manager", but rather just "Magisk".

As for @meric57's disappearing Magisk: He mentioned installing apps, not so much modules. And we are all currently so hung up on him displaying screenshots showing no-Magisk/unhidden-manager vs. Magisk/hidden-manager, I think we are ignoring his claim that the problem is triggered by installing/updating an app.

 

[badabing2003]

There is no denying that the Android app formerly known as "Magisk Manager" is a manager. The quibbling comes from John Wu declaring that he no longer wanted the app to be called "Magisk Manager", but rather just "Magisk".

As for @meric57's disappearing Magisk: He mentioned installing apps, not so much modules. And we are all currently so hung up on him displaying screenshots showing no-Magisk/unhidden-manager vs. Magisk/hidden-manager, I think we are ignoring his claim that the problem is triggered by installing/updating an app.

@J.Michael and @ipdev
To me the problem of why installing an app is triggering the issue is a secondary problem, that I wouldn't look into until I address the primary issue.
Which is:
1- Multiple versions of the manager on the system.
2- Redoing the root patch (this should not be necessary)

Hence I asked to first uninstall all managers, reboot and the install one copy, preferably not hidden (just for testing) and then install an app and see if it triggers the issue. I suspect that it won't, but if it does, at least at that point we know it is not the manger misleading him.

It is also possible that the Magisk root is of a different version than the manager being installed.
Once change at a time to narrow it down, that would be my approach.

 

[ipdev]

@J.Michael and @ipdev
To me the problem of why installing an app is triggering the issue is a secondary problem, that I wouldn't look into until I address the primary issue.
Which is:
1- Multiple versions of the manager on the system.
2- Redoing the root patch (this should not be necessary)

Hence I asked to first uninstall all managers, reboot and the install one copy, preferably not hidden (just for testing) and then install an app and see if it triggers the issue. I suspect that it won't, but if it does, at least at that point we know it is not the manger misleading him.

It is also possible that the Magisk root is of a different version than the manager being installed.
Once change at a time to narrow it down, that would be my approach.

Competing installed Magisk manager apps would give the error even before installing a random apk file.
Both the full Magisk app and the hidden (renamed) one would show Magisk as N/A.

I do not think the initial issue is with multiple Magisk apps installed.
Since Magisk (hidden) seems to be working before installing an apk file.

I can see reflashing magisk via Odin might install the full Magisk app.
But, it does not explain why it (full version) shows Magisk actively installed if there is a hidden magisk Manager app still active.
The full version and the hidden (renamed) version should both show Magisk as N/A until you remove one of them.

---

I fully agree with your suggestion about testing without the Magisk app hidden (renamed).

Cheers.


PS.
Just tried to duplicate competing full and hidden Magisk app on my Pixel 7.
Current commits in Magisk seem to now keep this from happening.
I installed the full Magisk app version.
Opened it and it closed and was removed, leaving only my hidden (renamed) version active.

 

[J.Michael]

Competing installed Magisk manager apps would give the error even before installing a random apk file.
Both the full Magisk app and the hidden (renamed) one would show Magisk as N/A.

I do not think the initial issue is with multiple Magisk apps installed.
Since Magisk (hidden) seems to be working before installing an apk file.

I can see reflashing magisk via Odin might install the full Magisk app.
But, it does not explain why it (full version) shows Magisk actively installed if there is a hidden magisk Manager app still active.
The full version and the hidden (renamed) version should both show Magisk as N/A until you remove one of them.

---

I fully agree with your suggestion about testing without the Magisk app hidden (renamed).

Cheers.


PS.
Just tried to duplicate competing full and hidden Magisk app on my Pixel 7.
Current commits in Magisk seem to now keep this from happening.
I installed the full Magisk app version.
Opened it and it closed and was removed, leaving only my hidden (renamed) version active.

@meric57's screenshots show no Magisk with unhidden manager; Magisk with hidden manager

I don't remember anyone ever talking about locating the hidden app in the app drawer and using it. I have been assuming that it would show Magisk installed -- the problem was always that the victim didn't realize he had two manager apps, I don't remember anyone saying that with two managers, both managers are disabled, only that the new, unhidden, manager did not communicate with the installed Magisk because the installed Magisk had somehow been co-opted by the manager that is now hidden.

Maybe meaningless details. I do not feel that we have been told what @meric57 did, in exactly what order.

 

[pndwal]

@badabing2003 @pndwal @J.Michael

Now that everyone has explained Magisk root vs. the Manager app.

Sorry.​

I will always refer to the Magisk app as the Manager because that is what it is.​

I have used Xposed and other(s) for too long to not refer to the application that allows you to setup, install modules, configure and control as the Manager.​

I think John did this:
https://topjohnwu.github.io/Magisk/...agisk-manager-is-deadlong-live-the-magisk-app
to clearly distinguish the old Manager which was just that, the Manager component, a "companion app" finishing with version 8.0.7, from the new Magisk app which is actually a complete Magisk package w/ the App (UI) part now necessarily in sync with the Magisk binaries and including "everything it needs within the APK itself, making installation a 100% offline process" incl. zip installers and now stub APK etc and starting wrapped with Magisk itself as version 22.0 (22000)...

Magisk Manager is dead.
Long live the Magisk app!

PW

 

[pndwal]

PS.
I update and install modules, apks and even system updates with Magisk hidden (renamed).
Very rarely do I have an issue due to the Magisk app being renamed.

This may be device or version dependant... I always try this just to guage if the issue has been resolved... On my device the issue is less frequent than a year ago, but both taking Hide the Magisk app and updating with App hidden have still failed several times recently to remove the full App and required manual removal...

Here's an open issue on this; My comments there too:
Hiding and Restoring Magisk App not working properly on Galaxy A8 2018 (Android 9.0)
#6309 opened on Oct 6, 2022 by DarkKnight1995

PW

 

[pndwal]

I would like to bump the other half of his question.

- Why would installing/updating a Module cause Magisk to fail for him.
- Why would installing an APK file even affect Magisk let alone cause it to fail.

I can not duplicate this part of the issue.
Any ideas on why this part of the issue would happen?

I did wonder about this too, but am not familiar with how Fox updates / other apps etc might interfere or even restore full app...

However the fact is the member said he had hidden app but first screenshot showed full app was used when Magisk Installed = Non disponible (N/A)...
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-88094125

After his flashing efforts the hidden app is shown working, so the difference is evidently the simple removal (however it occurred) of the full app and thus the conflict...

As @badabing2003 said:

To me the problem of why installing an app is triggering the issue is a secondary problem, that I wouldn't look into until I address the primary issue.
Which is:
1- Multiple versions of the manager on the system.
...
Once change at a time to narrow it down, that would be my approach.

Competing installed Magisk manager apps would give the error even before installing a random apk file.
Both the full Magisk app and the hidden (renamed) one would show Magisk as N/A.

Yes, but that is evidently the state of things now for whatever reason... And FWIW, once the hidden stub is properly working the full App has necessarily been removed... In my experience it can't just re-appear (it's a different app from stub after all) unless some app or routine is called by the user... [Edit: Actually, I recall now that Magisk could restore full app in stub (?) some time ago ... see post below] The issue may be "how did it get there", but it seems something (lost in translation) was executed purposefully if not inadvisably, and the fix is simple...

I do not think the initial issue is with multiple Magisk apps installed.
Since Magisk (hidden) seems to be working before installing an apk file.

So why did he show the full app not working?

I can see reflashing magisk via Odin might install the full Magisk app.
But, it does not explain why it (full version) shows Magisk actively installed if there is a hidden magisk Manager app still active.

Ah... But it didn't... Full App showed Non disponible ... Excusez mon français...

PS.
Just tried to duplicate competing full and hidden Magisk app on my Pixel 7.
Current commits in Magisk seem to now keep this from happening.
I installed the full Magisk app version.
Opened it and it closed and was removed, leaving only my hidden (renamed) version active.

Please say which commit... (This: Fix automatic stub installation seems unrelated)...

PW

 

[meric57]

Hello, my installation I do as explained by JohnWu modify AP with magisk then adb pull then odin.
Then once active start zygisk and installation of the main modules, applications like root checker and others give me active root.
Why for example when I update LSPosed in magisk or an application like Saturday that I installed nitendo DS emulator, when I restart my s10 exynos I find in the first magisk and zigisk not available.
So either it comes from a conflict with magisk installer or magisk is jealous that I install another application with its permission.
if it starts again how to proceed for the reinstallation without going through odin normally I just update firmware when a new security arrives, I read on the thread of the discussions you have to flash the boot.img or recovery.img of the AP patched_magisk with adb or magisk in recovery.

Canyie talks about uninstalling app manager no, for automatic installation
https://github.com/topjohnwu/Magisk/pull/6547

Badading2003 talks about 2 install managers, he talks about magisk and app magisk manager .
unless it speaks that on the internal memory of the Samsung S 10 I have 2 installations of the magisk manager app.

 

[pndwal]

Hello, my installation I do as explained by JohnWu modify AP with magisk then adb pull then odin.
Then once active start zygisk and installation of the main modules, applications like root checker and others give me active root.
Why for example when I update LSPosed in magisk or an application like Saturday that I installed nitendo DS emulator, when I restart my s10 exynos I find in the first magisk and zigisk not available.
So either it comes from a conflict with magisk installer or magisk is jealous that I install another application with its permission.
if it starts again how to proceed for the reinstallation without going through odin normally I just update firmware when a new security arrives, I read on the thread of the discussions you have to flash the boot.img or recovery.img of the AP patched_magisk with adb or magisk in recovery.

Canyie talks about uninstalling app manager no, for automatic installation
https://github.com/topjohnwu/Magisk/pull/6547

Badading2003 talks about 2 install managers, he talks about magisk and app magisk manager .
unless it speaks that on the internal memory of the Samsung S 10 I have 2 installations of the magisk manager app.

Ah... So appearance of full app happens with a reboot...

Could be to do with the broken function (Fix automatic stub installation) the Pull Request you linked is supposed to fix... Not sure...

I just deleted my Magisk App to see if it's restored on reboot (issue comments says it works without Zygisk so I disabled Zygisk to test) and sure enough I get stub installed named "Magisk" on reboot!... However it won't open nor does it ask for additional setup, so can't test further...

It could be that Magisk checks aren't recognising the hidden stub App on your device and Magisk is also installing another stub with full Magisk (I seem to recall this working this way a long while ago) on reboot which then conflicts with existing hidden stub App...

If this continues to occur, I'd try what's been suggested; uninstall every Magisk app (hidden, not hidden), then install full app from GitHub matching Magisk build you have installed again (without rebooting), then take Hide the Magisk app and reboot to see if all is the same and working (ie working hidden stub App still)... If full Magisk appears again after this, please let us know! PW

 

[pndwal]

PS.
Just tried to duplicate competing full and hidden Magisk app on my Pixel 7.
Current commits in Magisk seem to now keep this from happening.
I installed the full Magisk app version.
Opened it and it closed and was removed, leaving only my hidden (renamed) version active.

Just did the same to ensure forced app removal occurs even with same build App installation... It did...

So seems we do have forced app removal for App when hidden stub App is present in addition to when signing keys differ or App has a lower version than Magisk daemon...

Man, Magisk Devs are trying hard to protect us from ourselves! (Not sure I need my hand held this much)... Except that when this fails to work as expected we may need protecting from them! PW

 

[pndwal]

Just did the same to ensure forced app removal occurs even with same build App installation... It did...

So seems we do have forced app removal for App when hidden stub App is present in addition to when signing keys differ or App has a lower version than Magisk daemon...

Man, Magisk Devs are trying hard to protect us from ourselves! (Not sure I need my hand held this much)... Except that when this fails to work as expected we may need protecting from them! PW

... But regarding this:

PS.
I update and install modules, apks and even system updates with Magisk hidden (renamed).
Very rarely do I have an issue due to the Magisk app being renamed.

This may be device or version dependant... I always try this just to guage if the issue has been resolved... On my device the issue is less frequent than a year ago, but both taking Hide the Magisk app and updating with App hidden have still failed several times recently to remove the full App and required manual removal...

Here's an open issue on this; My comments there too:
Hiding and Restoring Magisk App not working properly on Galaxy A8 2018 (Android 9.0)
#6309 opened on Oct 6, 2022 by DarkKnight1995

PW

Just uninstalled hidden App (on latest Canary) again, reinstalled Canary Magisk App, then took Hide the Magisk app, and once again process failed to uninstall full app, asks for superuser permission for Magisk App etc ... As usual, simply ignoring requests and uninstalling the full App restores hidden app functions...

PW

 

[J.Michael]

Hello, my installation I do as explained by JohnWu modify AP with magisk then adb pull then odin.
Then once active start zygisk and installation of the main modules, applications like root checker and others give me active root.
Why for example when I update LSPosed in magisk or an application like Saturday that I installed nitendo DS emulator, when I restart my s10 exynos I find in the first magisk and zigisk not available.
So either it comes from a conflict with magisk installer or magisk is jealous that I install another application with its permission.
if it starts again how to proceed for the reinstallation without going through odin normally I just update firmware when a new security arrives, I read on the thread of the discussions you have to flash the boot.img or recovery.img of the AP patched_magisk with adb or magisk in recovery.

Canyie talks about uninstalling app manager no, for automatic installation
https://github.com/topjohnwu/Magisk/pull/6547

Badading2003 talks about 2 install managers, he talks about magisk and app magisk manager .
unless it speaks that on the internal memory of the Samsung S 10 I have 2 installations of the magisk manager app.

What did you do?

1. install Magisk APK
2. find boot image
3. patch boot image
4. use Odin to install patched boot image
5. allow Android to update
6. find new boot image

When did you make the screenshot showing Magisk: No, Package: com.topjohnwu.magisk?

When did you make the screenshot showing Magisk: Yes, Package: gibberish?

When you update Android, do you look for a new boot image? Do you
patch the new boot image? Do you install the new patched new boot image?

 

[pndwal]

Samsung compatibility

Fix for Magisk on new A13 LV Samsung (S23 Ultra etc) devices coming soon!

Add init_boot.img patching for Samsung tar firmware packages #6586 opened 6 hours ago by BlackMesa123• Approved

- Ckecks now passed, tested, ready to merge. ... Thanks @BlackMesa123 and @dr.ketan!

PW

 

[ipdev]

@meric57's screenshots show no Magisk with unhidden manager; Magisk with hidden manager

I don't remember anyone ever talking about locating the hidden app in the app drawer and using it. I have been assuming that it would show Magisk installed -- the problem was always that the victim didn't realize he had two manager apps, I don't remember anyone saying that with two managers, both managers are disabled, only that the new, unhidden, manager did not communicate with the installed Magisk because the installed Magisk had somehow been co-opted by the manager that is now hidden.

Maybe meaningless details. I do not feel that we have been told what @meric57 did, in exactly what order.

As for competing managers.
I was going off of memory from when it used to happen to me every now and then.

Both the regular (not hidden) and hidden (renamed) would show Magisk N/A.

All I had to do was uninstall one of them.
Normally I uninstalled the hidden (renamed) one and rebooted.
Then the regular (not hidden) one would show Magisk installed again. Then I could hide (rename) the manager again.
It was hit or miss if I uninstalled the regular one and rebooted.
Sometimes the hidden one would still show N/A. If so, then I had to uninstall it and reinstall the regular version again.
Then hide (rename) the manager again.

---

I wasted a bit of time tonight trying to get two Magisk manager apps to run currently.
The best I got was an error with Magisk Stable v25.1 on my Pixel 4a.

The initial hiding gave me issues with setting permissions and such.
Once the hidden app was installed, the regular version was removed.
The hidden version showed Magisk installed and active but, would keep throwing errors telling me to restore the Magisk app and hide again.
So I did and no issues the second time around.​

Cheers.

Edit:
@pndwal I did not read your last couple of posts before testing.
When I have time (tomarrow) I will see if I can duplicate it.

 

[ipdev]

I think John did this:
https://topjohnwu.github.io/Magisk/...agisk-manager-is-deadlong-live-the-magisk-app
to clearly distinguish the old Manager which was just that, the Manager component, a "companion app" finishing with version 8.0.7, from the new Magisk app which is actually a complete Magisk package w/ the App (UI) part now necessarily in sync with the Magisk binaries and including "everything it needs within the APK itself, making installation a 100% offline process" incl. zip installers and now stub APK etc and starting wrapped with Magisk itself as version 22.0 (22000)...

Magisk Manager is dead.
Long live the Magisk app!

PW

Like I said I have been using Manger apps way too long to not refer to them as the Manager.

Instructions

You can install/update phh's SuperUser in Magisk Manager's Download section
If you have no root in the first place, please flash the zip in the attachment through custom recovery
A root solution is part of a proper Magisk installation.
After phh's SuperUser is installed, please install the SuperUser manager Application through the Play Store
phh's SuperUser Manager​

Guess I am turning into the "Old Man".
Next I will be yelling at kids to keep of my lawn.

Cheers.

 

[IronTechmonkey]

Like I said I have been using Manger apps way too long to not refer to them as the Manager.

The combination of app and on-device services (root) could be called Magisk The Gathering.

 

[Telperion]

It's been a long, long time since I've paid attention to how rooting works on a technical level with modern devices.

I have an Android 10 head unit that I'm trying to get a working userspace root solution onto. The bootloader is locked, but I have root via both a wireless ADB shell as well as serial console. I have read/write access to /system. I don't have the ability to unlock the bootloader and flash a patched boot image. Is it possible to get Magisk working?