Magisk General Support / Discussion

[pndwal]

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

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

 

[blksith0]

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

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

 

[pndwal]

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

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

 

[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

 

[badabing2003]

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

Would you happen to have two instances?
Notice the package name of one which is hidden and the other not hidden

 

[pndwal]

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

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

 

[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

 

[pndwal]

Hello Badading2003, magisk is hidden in the magisk parameter,

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

 

[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

 

[pndwal]

Hello pndwal, yes I have hidden magisk in magisk parameter..

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

... each time you have to flash with odin to recover the root...

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

 

[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

 

[badabing2003]

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

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.

 

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

 

[badabing2003]

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

 

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

 

[badabing2003]

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.

Have you tried my suggestion?

 

[J.Michael]

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.

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.

 

[pndwal]

@meric57, all, FWIW:

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.

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,

...App shown as installed is NOT the hidden App...

Also https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-88094379

Full App is

actually a completely different app to the hidden one...

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

tiny stub App

and Magisk simply

fills it's data with approx. 17MB of data (Magisk binaries)...

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

very common... root and modules are still there, but App can't see them when two Apps are competing... PW

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

... You can't have two Magisk apps... PW

PW

 

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

 

[J.Michael]

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.

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