yashsingh1/xdaforums huggingface dataset:
[Magisk] yanilata:
For all I'm referring to the microG patched LineageOS builds:

lineage-20.0-20230124-microG-enchilada.zip <- this update includes a boot.img (extracted from payload.bin with payload-dumper-go)

lineage-20.0-20230122-microG-enchilada-boot.img <- this is the other boot.img

True I did not try to backup boot and patching this. I thought there is no point because the boot.img contained in the update should be identical to the boot partition after sideloading lineage-20.0-20230124-microG-enchilada.zip. Unless the partition is changed during the first bootup while these changes are mandatory for magisk patching to work?
[Magisk] pndwal:
Yup, last boot image flashed should be the same unless the microg installation does alter the boot.img somehow as you suggest...

You initial posts were a little less than clear respecting various boot images however, and many users have patched mismatched boot images before reporting issues in these forums and in GitHub issues too. Can't hurt to consider the possibility... 🙃 PW
[Magisk] blksith0:
Am I supposed to use shamiko with kdragon fix together, or just choose one?
[Magisk] pndwal:
Don't use official USNF 2.4.0 ATM as it is broken and fails intermittently... Use any of @Displax's published modded USNF builds...

USNF and Shamiko do quite different things...

Most banks require Play integrity deviceIntegrity passing verdict (ie. use @Displax's modded USNF). Some use their own approaches to detect root/modified runtime environment (ie. use Shamiko etc)... Both can be used in tandem with no conflicts... PW
[Magisk] blksith0:
Okay. I'm using both in tandem. (The only way to get Google-Pay working, it seems.)

I will search for Displax's mod.

Unfortunately Shamiko gives my a phone a lot of instability: crashing, freezing, hanging, forced to hold-power-button-reset...
[Magisk] pndwal:
You didn't add any gms processes in denylist did you?... Don't do that with any Zygisk USNF solutions...

Interesting Shamiko issue... Shouldn't cause that... Please give device / OS / setup details...

I would generally suggest keeping Shamiko, but you don't actually need it for G Pay/Wallet... PW
[Magisk] blksith0:
Thanks for replying.

Nothing like that in the denylist. I've disabled shamiko and now trying out only the Displax 2.3.1 mod. Seems to be okay...

Sometimes I think it might be easier to just go the Magisk Delta mod and bring Magisk Hide back!

device: Google Pixel 3a (sargo)

ROM: crDroid, Android 12.1
[Magisk] pndwal:
Ah, custom crDroid... I think that normally integrates @kdrag0n SNF per Proton ROM options (2 methods offered), and may also pull extra @Displax fixes... could be wrong...

You could try this:

Remove USNF completely, add Google Play Services attestation/droidguard (com.google.android.gms.unstable) and main (com.google.android.gms) processes in denylist (enforced) and reboot...

Check YASNAC results... You should be passing S/N (ctsProfileMatch) w/ BASIC evaluationType...

Check Play Integrity API Checker results... If you have recent crDroid and maintaining Dev has added recent fixes for SNF you should be passing deviceIntegrity too... If not, you may be best to run a @Displax modded USNF build... You could alternatively globally spoof (eg with MHPC module) a mismatched but passing fingerprint prop that bypasses fingerprint property based PI-hardware-based-verdict-enforcement, but targeting spoofing is preferable...

If you can pass PI deviceIntegrity with no USNF module this way, you could also disable denylist enforcement and check if Shamiko becomes stable with this setup... PW
[Magisk] meric57:
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.

As in the screenshot, then no more root, so I must again reflash the AP patch_magisk and the 3 CP -BL and home CSC files with odin.

There is no direct way to recover with magisk.

thank
[Magisk] badabing2003:
Would you happen to have two instances?

Notice the package name of one which is hidden and the other not hidden
[Magisk] pndwal:
In your first screenshot you have full Magisk App (not hidden)... I'm guessing you also had the stub (hidden) App still installed and that's causing the conflict...

In the second screenshot you have stub (ver 33) (hidden) App restored...

In the first case, simply uninstalling the hidden App should allow the full App to work again, and you can also then hide it again... 🙂 PW
[Magisk] meric57:
Hello Badading2003, magisk is hidden in the magisk parameter, the root is present until I install a third-party or magisk-specific apk. As on the screenshot, neither magisk nor zigysk is available, so the root jumps at startup, there is no way to recover the magisk application directly the magisk application in boot.img or recovery.img flash.

why is talking about two instence , LSPosed .apk install in module

normal the capture already registered following the previous problem with LSPosed APK, the I have just restored magisk hidden these good.

I would like to know the reason as explained during updates or apk installation.

I find magisk not available and application ok
[Magisk] pndwal:
The fact is, in your first screenshot (w/ root not recognised by app) your App shown as installed is NOT the hidden App (App is NOT hidden); it's actually a completely different app to the hidden one; hiding uninstalls full 17MB app and installs the v33 tiny stub App and later fills it's data with approx. 17MB of data (Magisk binaries)...

If you think you had the hidden App you're probably right!... you actually had Both! Ie. Two instances!... Believe me, that's very common... root and modules are still there, but App can't see them when two Apps are competing... 🙃 PW
[Magisk] meric57:
Hello pndwal, yes I have hidden magisk in magisk parameter. My concern that I would like to know why as explained during an example installation yesterday I installed superNDS a DS nitendo emulator. apk then in magisk not available and application always install, how to fix worry because each time you have to flash with odin to recover the root.

I use google translate I'm French so hard for my spelling
[Magisk] pndwal:
Then why is full App still installed in screenshot??? It should be gone!... If Magisk installed it during an update and failed to uninstall hidden stub, you simply need to uninstall one or other, or sometimes both apps and reinstall for one app to work again...

No, no such need; if you had hidden app as you state, you do need to remove the full app which is clearly installed also... You can't have two Magisk apps... 😶 PW
[Magisk] meric57:
Complicated this situation which is to install that its is magisk and sigisk and application magisk ok, why magisk this uninstalls during an installation of an apk.

I don't have a bank problem, just that I would like to know how to solve this problem during an installation after a restart

At the moment I wanted to hide magisk again I got an error then I restarted my S 10 magisk not available, so to find my root I must redo with odin BL -APp atched _magisk -home CSC

Screenshot after flashing to find the root in magisk
[Magisk] badabing2003:
You can't have multiple instances of Magisk manager.

What is sigisk?

I would uninstall all Magisk Managers (don't worry you won't lose root by doing so)

Start with uninstalling the unhidden one if you have one currently.

adb shell pm uninstall com.topjohnwu.magisk

Next unhide Magisk if you have one

if you can't find one look for Application Accueil

then uninstall it

repeat the process if you have more hidden Magisk Apps or Accueil that is Magisk

You can also issue these commands based on your screenshots

adb shell pm uninstall tu.ec
adb shell pm uninstall r.iazafs.l.kn.jntj

When you have all Magisks uninstalled

Reboot

See if you find Magisk Manager after reboot.

If you don't, just go ahead and install it

Hide if you want.

If you get an error during hiding, that is a clue that you will encounter a problem.

Perhaps it is failing to uninstall the unhidden one, which is causing multiple versions to exists and pose problems.
[Magisk] meric57:
Good evening Badading2003, I am with samsung first generation so exynos not 5 G in 4 G.

As marked in signature A12, applist detector I have this so no worries I think on the hidden side of magisk.

Me my concern what I would like to know why magisk is unavailable when installing an APK ???

Then how to re-install magisk as shown on a screenshot.

look at the applist detector screenshot,you see in application not available and tu.ec package therefore hidden.
[Magisk] badabing2003:
You have to realize that there is two parts to Magisk.

The manager which is the ui component, and the core, which is what you flash.

When you have multiple managers, then they would get confused about the state.

I bet you're still rooted even though the manager says you're not.

Run a root app and you'd see.

The solution is to keep only one copy/version of manager.
[Magisk] meric57:
yes, these are where I don't understand the magisk party and magisk app.

When I see the part magisk not available and zigisk not available when I do with root checker its me not root as I know that if I unroot with the official rom the knox0x1 so concern for system health samsung applications.

the information you said is explained or on the forum.
[Magisk] badabing2003:
Have you tried my suggestion?
[Magisk] J.Michael:
When you run the Magisk app, the first screen has two parts. The top part is describing the magic Magisk installed in boot or recovery. The next part down is describing the Magisk manager app. Where it says "Paquet" (packet? package?) it is identifying the app. When it says "com.topjohnwu.magisk", that means an unhidden Magisk manager app. When it says jumbled name, like "r.iazafs.l.kn.jntj", that means a hidden Magiso manager app. It is not good to have more than one Magisk manager app.

Are you generating new screen shots every timevyou post? I am trying to understand whether you can see both of these Magisk screens without changing your system.

Stop hiding the Magisk manager app.
[Magisk] pndwal:
@meric57, all, FWIW:

Yup, and further,

indicates installed App is full ver 25200 whereas

indicates installed App is stub ver 33 w/ binaries from 25200 loaded in its data...

As I've already said,

Also https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-88094379

Full App is

Hidden App is simply an empty shell/container, ie the

and Magisk simply

extracted from the current full App (.apk package) before that is removed...

But often the Hide the Magisk app option fails to remove the full app!!!

In this situation we end up with dual apps, which is very easily done since we haven't simply installed an update, but rather a different app with different package name and signing keys!!!... The former (competing) full app/package needs special treatment to be removed after its binaries are transferred to the stub app...

Also, this situation is

😬 PW
[Magisk] meric57:
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.

I would like to know if possible to do with ABD or other direct from the smartphone to find magisk on yes and zigisk on yes, I'm talking about magisk the one who is first step APP which is always installed.

I saw on the son of descution which must be done with boot.img or recovery.img of the file patched_magisk.img.tar, will have to make an explanation on the first page of this forum to recover magisk not available.

THANKS

I do it like this I reflash with the 3 files from the official home rom CSC -BL-CP- patched-magisk.img.tar, root recovery which is not practical slower which works all the same.

Also I read that USNF of KdragOn was broken which has a modification must go through the modified version, I put you 2 screenshots one to show that I removed the cache of magisk and the other the module in question is he the one who needs to be changed.
[Magisk] J.Michael:
Do you have a problem now?

Do you have Magisk available at this moment?

Stop re-installing Magisk. Do not use Odin when you think you have lost Magisk. We do not think you have really lost Magisk.

You have a lot going on. You are doing a lot of things. The next time you think you have lost Magisk, do not reinstall Magisk. Look around for Magisk manager apps in your app drawer. If you find two -- that is probably the problem. Uninstall all of them. Do not uninstall Magisk. Uninstall apps -- Magisk manager apps. Then install the Magisk manager app apk. See if that can see Magisk is already installed.

Can you stop trying to hide the Magisk manager app?

Did you try @badabing2003's suggestions? (Using the command line to remove packages.)
[Magisk] 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.
[Magisk] pndwal:
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...

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
[Magisk] 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. 🙃

- 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? :unsure:

Cheers :cowboy:

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.
[Magisk] J.Michael:
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.
[Magisk] badabing2003:
@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.
[Magisk] ipdev:
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. :unsure:

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. :cowboy:

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.🤪
[Magisk] J.Michael:
@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.
[Magisk] pndwal:
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
[Magisk] pndwal:
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
[Magisk] pndwal:
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://xdaforums.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:

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...

So why did he show the full app not working? 🤔

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

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

🙂 PW
[Magisk] 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.
[Magisk] pndwal:
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