yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
App issue should be simple; don't try to update from 23.0; find it in download folder and install from there; uninstall other app first if still fails, also check allowed installation from unknown sources, play protect isn't set to prevent unknown apps etc...

Edit: I see from this:

https://xdaforums.com/t/magisk-24-1-no-gydisk-option-available.4396933/post-86358829

we're not talking about app signing, rather attempting to flash a patched boot image through Magisk app. Seems from this:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86359701

that you got direct install back, which means you must have restored root visible to app, Here I'm confused; did you have 24 app w/ 23 root and were attempting to update to 24 root?... Or other?

Main issue:

Magisk 24.1 Showing Installed N/A - Root Functions Intact​

- for you and

please see here:

https://github.com/topjohnwu/Magisk/issues/5339#issuecomment-1029931680

👍 PW
[Magisk] Spartacus500:
I don't know if this message will be helpful, Samsung Galaxy S7 edge Custom Pie 9.0 Rom NFE 2.2 has been updated with the latest Magisk 24.1 without any problems.
[Magisk] pndwal:
Guess it's a clue; may only be a stock or Android 8 Oreo issue... or other factor... 😜 PW
[Magisk] Prof_Shekhar:
Thanks Xabu for your encouraging words.

I wish I was half as lucky as I would like to believe. I am still not out of woods.

Although, I have managed to root my device with Magisk 24 .1 but yet not able to connect it with the Magisk app for 24.1. What you may have seen is Magisk app 23.0 paired with root created by Magisk 24.1. Hence I'm still not at home due to this mismatch marriage.

Now, I have tried so far all the methods suggested by the seniors here except one with ADB. I think, this unable to check signature error comes from the mismatch between the signature of the Magisk root and it's corresponding app as I keep experimenting with various versions of Magisk viz 23 & 24.1 just to see which one works.

Tomorrow, I would get boot.img file patched with existing Magisk version 24.1, flash the system using ADB commands and then use the same Magisk which was used for patching, to work with the root.

Hope this concoction works 🤞🏻

Hang on buddy, we'll succeed. Your case appears to very similar to mine.

I think, we both had perfectly working Magisk root 23.0 until we took the bait to update it to 24.1.

Now I suspect that although the auto update, updated the Magisk app 23.0 to Magisk 24.1 but as I had earlier deleted the original Magisk which came with the installed root.

I am not an expert but I guess, that when the Magisk app tried to update the root to 24.1 but as the app probably couldn't find the signature of the app which was being upgraded match with the signature of root and hence gives a message that unable to check signature.

I may be 99% wrong but definitely worth trying to root the device with the patch generated by its Magisk app.

No pain, no gain
[Magisk] J.Michael:
I cannot make sense of your description.

When do you get message "unable to check signature"?

You posted a screenshot showing Magisk 24.1 and Magisk Manager app 23 installed.

At this point, I do not believe you should be continuing to try to install Magisk -- you have installed Magisk.

If the current problem is the version of the Magisk Manager app, you should not be using TWRP, or patching boot images. Leave Magisk alone, focus on Magisk Manager app. Uninstall Magisk Manager app and reboot. If after reboot there is no Magisk Manager app, install Magisk Manager app 24 apk.

If you ever in the past hid/renamed the app, you must check all apps and uninstall every copy of Magisk Manager app you can find.
[Magisk] Prof_Shekhar:
This is what has frustrated me so far.

As far as removing all previous instances of hidden Magisk manager app, I have tried my best using ADB commands to search for them and uninstall them.

I did manage to find one and uninstalled it. But that's all I could find.

Would you be able to suggest me some more ways of searching for the previously hidden app which may be still lurking in the background.

However as far as I remember, I had only one instance of Magisk app hidden when the Magisk app decided to auto update. This removed all the option for me to restore the hidden app. Anyway, that incident took place few days ago and since then lot of water has flown under the bridge.

Thank you

Hi pndwal,

Currently, I have rooted my device with a Magisk 24.1 patched image but it is being detected as instled version 24.1 only when I install a Magisk app version 23 and not 24.1.

With Magisk app 24.1, it shows as no root.

Therefore what my little understanding tells me that Magisk app 24.1 is not able to communicate with the installed Magisk 24.1 root and hence not displaying any information about the root.

Not sure if I'm right but can't think of any other possible reasons.

Even the close scrutiny of the log of the time gives me a vague clues in this direction.

May be you could shed light on any other possible reasons.
[Magisk] zgfg:
How do you 'uninstall" by ADB - what command do you exactly use?

adb shell pm uninstall -k --user 0 <pkg name>

is by no means real uninstallition - if you later run

adb shell cmd package install-existing <pkg name>

it will 'install' the same app without the need to provide apk file (as for the real installation after the real uninstallition)

You have to uninstall the hidden/renaned/repackaged Magisk app = Magisk mngr (same thing, old and newer term) through Settings, Apps (or by using root and deleting its subfolder from /data/app)
[Magisk] J.Michael:
I think you need to search your app drawer (the set of all apps on your device; on my tablet, from home screen, stroke up, then maybe stroke sideways to scroll through all of them -- it varies by Android version). You can probably ignore anything with an elaborate (colorful) icon. If it calls itself Magisk, uninstall it: press on icom to get tooltip, select "App info", select "Uninstall".

The hard part is finding one that does not call itself Magisk. I think the default is for it to call itself "Settings" -- you will have to figure out whether it is the one real Android Settings app, or an impostor. I think you will be able to tell from the App info. Look for whether it even has an Uninstall option; see if the version number looks like one of the Magisk app versions you have tried to use; see what it says about where it came from.

Only you can imagine what name you might have chosen when you renamed the Magisk Manager app. If you see an app with a name you might have chosen, suspect it.

At worst, you can try running each app to see which ones are really Magisk.

A last resort would be to wipe data. It's hard to imagine any app surviving that.
[Magisk] gorman42:
Ok, I managed to update from 23 to 24.1. DenyList managed to overcome root detection on some apps but my banking app still refuses to work. Is there a list of best practices to try in order to use it while keeping root?

Edit: YASNAC reports Basic integrity and CTS profile patch as Pass, in case it matters.
[Magisk] zgfg:
I don't really understand all those users who did "Hide Magisk App" and forgot the names they gave it

What if they wanted to manage modules - how would they do it (I doubt they would do it by CLI commands), to revoke a root grant or something

If they ever used it later, they should remember what name they gave it.

It sounds to me like: Plesse help, I forgot my Android unlock pin (pattern) and cannot unlock the system upon rebooting, or so
[Magisk] J.Michael:
The first few posts of this thread *are* a list of best practices.
[Magisk] pndwal:
@Prof_Shekhar

Please re-read what I said here. Especially 'Main issue'...

Many here, like my initial conclusion, are still thinking you are speaking of an app signing issue, but I'm satisfied that this is not an issue with multiple app instances of app.

I'm unclear on how you tried to apply manually patched image through Magisk App's Direct install option... General manual patch is for initial setup only and on Samsung you need to flash the 4 ROM components w/ Odin. Direct install is for updating Magisk after obtaining initial root. I suspect the 'signature' issue is due to either your underlying issue, or need to flash using Odin (you may like to answer my question above about existing root at the point you tried this 😉).

Anyway, all this seems pretty much beside the point as it appears you have the Magisk 24.1 Showing Installed N/A - Root Functions Intact issue I linked.

This was closed till only an hour ago as someone thought it was s duplicate issue. It's actually the same as yours.

Last night I asked @osm0sis to reconsider closing it (my post above was to make you aware of this 😉) and he has. - The issue has just been opened again with "Needs Investigation" label. 👍

I linked the additional example/descriptions from @Palazzo_K and yourself (last) in my linked post...

Please watch that space as the issue will (hopefully) now get attention from experienced Devs... Patience. 🙂 PW
[Magisk] Spartacus500:
Can you provide a link to this app ?
[Magisk] pndwal:
Links in OP's post #4. PW

Edit: For YASNAC... Seems you may mean bank app!?
[Magisk] xabu:
I think @Spartacus500 means the banking app.
[Magisk] xabu:
{Mod edit: Quoted post has been deleted on request of author - Oswald Boelcke}

I still think that @Spartacus500 meant the banking app.
[Magisk] pndwal:
Guys, please check his screenshots; 'signature' issue is not app related; it's flash failure. He does not seem to have this issue as I said. 😜 PW
[Magisk] szazs89:
What about Shamiko?
[Magisk] pndwal:
Ta... Usually last noun mentioned!

Edited post. 👍 PW
[Magisk] gorman42:
Did not see instructions for this in the first page. Did I miss them?

App is this: https://play.google.com/store/apps/details?id=it.copergmps.rt.pf.android.sp.bmps
[Magisk] pndwal:
OP's post no. 9. 👍

Release notes cover basic usage; Please open the module zip archive and check readme.md file.

Tip: You can find Usage instructions and other details in readme.md file in module zip archive of many modules.

🤠 PW
[Magisk] gorman42:
Shamiko did the trick. Thank you.

I suggest to point out what it's for in OP #9. The way it's written, it's just for people already in the know.

Thanks again, much appreciated.
[Magisk] Prof_Shekhar:
To begin with, I have already wiped all the data including the OS & TWRP.

Started from device showing only Samsung Logo.

Reinstalled everything using the stock firmware. Don't know if the hidden Magisk app still survived.

Listed all the installed package, couldn't find the name of the hidden Magisk app which incidentally I had kept as Hulu.

Searched for anything related with com.topjohnwu.magisk. Didn't find anything.
[Magisk] pndwal:
Great!

So Banca MPS fixed by Shamiko on what device / ROM?

OP just added that info on Wednesday... Hasn't updated everything incl post #1 yet... 😜 I'm sure he's doing his best, but still a WIP.

Nb. You need to ping @ipdev, OP, to make suggestions. 👍 PW
[Magisk] Prof_Shekhar:
I have so far tried to list all the pkgs installed on my device, searched for the com.topjohnwu.magisk, Hulu (renamed magisk app) and other possible permutations and combinations. But so far not lucky enough to get anything useful so far.

In utter frustration, completely wiped the entire device leaving nothing except permanently displayed logo.

Reinstalled everything from stock firmware using ODIN.

Still searched all the installed apps present on this device for any signs of hidden Magisk app either by its real name or assumed/presumed names, but far success has still eluded me.

It is hard to not believe that the hidden Magisk app is still not hiding somewhere on the device and not letting the new Magisk manager to do its job.

Appreciate if you can suggest me some more ways to intensify my search for the missing app.

Hi Xabu,

Thanks for taking out your time to help me.

As you mentioned, I have thrice rooted my device using AP patched by Magisk 24.1 alongwith (stock) BL, CP, CSC (ODIN3) and by following the steps as described by topjohnwu in this forum. Every time, I have checked about the success of root using root checker and it passed with flying colors.

Now today, as I have uninstalled the Magisk root 24.1, I am thinking of using fastboot to flash the Magisk 24.1 patched boot image to see how does it goes. Also intend to do everything possible to search the all elusive hidden Magisk 23.0 app from the first install.

Let me know if you could think of any other possible steps.
[Magisk] pndwal:
Did you mean to ping me or @xabu?

I'm not sure why you don't seem to have read / understood what I have told you twice... It's not dual app issue... You have a known issue... I've linked some details re. your example in that Magisk issue ticket, and it has just been re-opened after being closed in error 4 days ago... Please check that issue, comment there re. observations, logs etc and wait for an experienced dev to pick it up / diagnose / create pull request for merging a fix! PW
[Magisk] Prof_Shekhar:
Hi pndwal,

Sorry for any confusion caused.

My intention was to keep you updated about the steps taken by me so far.

Shall wait as suggested.
[Magisk] pndwal:
Please post in that issue with device details, Android version, your steps / symptoms, any logs taken to assist Devs with a fix... (They won't want to look through XDA posts.) 👍 PW
[Magisk] Prof_Shekhar:
Device name: Samsung Galaxy Note 8 (SM-N950F).

Android Version: 9 (Pie)

Rooted with TWRP and Magisk 23.0

Worked flawlessly. Hide features worked as expected.

Few days ago, fell for auto update to 24.1. Update failed due to unable to check signature error though the Magisk app got upgraded from 23 to 24.1.

Now the upgraded Magisk had no option to do anything except upgrade root to Magisk 24.1 via direct install method.

Tried once again, install failed again due to unable to check signature error.

Left with Magisk 24.1 app which gave me no option to unhide the previous Magisk i.e.23.0, uninstalled the Magisk 24.1 app inorder to install Magisk 23.0 to get the original functionality back.

Most of the functionality of root restored except the ability to hide the Magisk app itself. This led to all banking and some financial apps stopping to work.

Decided to uninstall root altogether via TWRP and with Magisk 23 app renamed as uninstall.zip. TWRP flashed the uninstall zip file with no issues.

Reinstalled the Magisk 23.0 (TWRP & ODIN method. Device reported success with root cheker app.

Reinstalled the Magisk 23.0 app but situation remained as it was before ,(i.e. not able to hide Magisk app).

Thinking that this problem could be due to previously hidden Magisk app 23.0, decided to wipe everything on the device including OS and TWRp using TWRP.

Finally left with no OS and any type of data on this device, reinstalled the stock firmware using ODIN.

This time rooted the device to 24.1 following the steps mentioned by Topjohnwu (Magisk patched AP file & ODIN). Regained root as confirmed by the root checker but still no Zygisk or any other option available in Magisk app. Also couldn't hide the Magisk app itself.

Uninstalled the Magisk app 24.1 and reinstalled the Magisk app 23. This app showed that device has Magisk root 24.1 but couldn't passed the safety check and not able to hide anything.

But it gave me the option to uninstall root which version 24.1 didn't give.

Uninstalled the root yesterday, reinstalled the Magisk app 24.1, patched boot.img file with Magisk 24.1.

Was planning today to flash the device with ADB fastboot but have decided to hold on after I heard from you. Will wait for the next step only after I hear from the seniors in this forum.
[Magisk] pndwal:
@Prof_Shekhar

Just noticed your post above. Please could you post the issue details in that issue thread, not here on XDA... ie. On GitHub, link I gave you... (Did you check it yet?)

Once you make a post there you'll get email notifications of progress, log requests, test fixes etc...

Please do so as I can't keep relaying to you what's going on...

Already, Canyie has responded and is asking you guys to test her previous fix which may solve this issue also with next TJW release, ie. Make sure busybox can be executed recursively #5334, merged upstream and fixes similar issue:

Magisk 22101 (22.+) not detected by Manager ("N/A"), but SU still working on Android 6.0 (+) Marshmallow with Samsung Note 4 SM-N910F TouchWiz, armeabi-v7a and other devices #4174

by trying a downstream test build with her fix:

https://github.com/topjohnwu/Magisk/issues/5339#issuecomment-103052649

@Palazzo_K, please post there too if you wish to contribute if requested / be informed of progress / fixes.

👍 PW
[Magisk] zgfg:
When you do "Hide Magisk App", you don't only rename the app from Magisk to Settings or Hulu (your choice) but it also (not your choice or influence) REPACKAGES from com.topjohnwu.magisk to some TOTALLY RANDOM package name (look at the screenshot)

Otherwise, it would be totally useless 'hiding' - all banking apps would still be trivially able to find it under the well known package name com.topjohnwu.magisk

Hence, i instead of looking for com.topjohnwu.magisk package name, you could be better looking for the random package name since usually package names of the regular apps are not random

But if you renamed the app name to Hulu, then it should be found under that name in your Settings, Apps or your App drawer

Btw, you reinstalled the ROM. If you lost other your user apps then Factory reset was performed alongside and Hulu should have also been removed.

If you did not loose your user apps and data, then Factory reset was not performed and therefore reinstalling the ROM did not affect presence of your Hulu app

Hence take a look for the variations of Settings or Hulu app name (you could have made a mistake while renaming) and for the random package names - if you cannot find, then hidden/renamed/repackaged Magisk app is no more present on your phone and better look to what @pndwal is pointing you🥸
[Magisk] xabu:
I am still following your adventure. I knew you would find here the right specialism to help you further. I also understand how difficult it is for them as it is for you. Hope they don't give up because it takes a lot of energy to help you ...not because it's you but because the problem is difficult to understand and very complicated

as shown by @zgfg (y) and @pndwal (y) .... wishing everyone a good weekend.
[Magisk] holymoz:
updated now to 24.1, for banking apps I only checked the app in applist in magisk options, never installed anything more and apps doesnt warn me anymore about root, why so simply?
[Magisk] zgfg:
An interesting regression bug in the latest Magisk Alpha 24101

I did Hide M app and renamed to Hulu:), later Restore M app

As you can see, i ended up with Hulu, its shortcut and restored Magisk app

Restored app was properly recognizing Magisk.

Hulu did no more - problem is, it had to be automatically uminstalled but it was not (I did it then manually)

PS: Retested the same two more times, issue did not repeat - upon restoring, there was only the restored Magisk app and the renamed/repackaged one was correctly uninstalled
[Magisk] Prof_Shekhar:
@pndwal

Posted all the details to the above link as suggested.

BTW, I attach herewith all the screenshots.
[Magisk] Prof_Shekhar:
@zgfg

Thank you so much for this info.

I shall definitely

run adb shell pm list packages

and

adb shell pm list packages -s

to search for random name packages.

Also I have done factory reset twice so far just to ensure there is no baggage from the past is lurking in the background.

Only app currently in my phone are the one provided by Samsung in stock firmware.

Will also relook at the suggestions made by @pndwal.
[Magisk] gorman42:
OnePlus 6T, Lineage 18.1, January 27th build.

Sure, didn't mean it in a bad way. Just a suggestion, as I stated. As always, I remain grateful there's so many people willing to share knowledge and to help others.
[Magisk] Prof_Shekhar:
@xabu

Thanks a ton for all your help throughout this week..

Wish a relaxing weekend (y)
[Magisk] meric57:
Hello, how to adjust the red circles of a white cross in oprek detector3I have 7 in negative status, I have messages failled no ads found.
[Magisk] zgfg:
First of all, checkmark Oprek in DenyList (and reboot).

If using Shamiko, you must enable Enforce DL, then add it, disable Enforce DL and reboot

You will also have to use Zygisk-LSposed and HMA = Hide My Apps.

But I'm really tired of explaining how to use HMA - try to find posts about or let somebody who recently learned about, explain you 😁
[Magisk] meric57:
312 / 5 000

​

Hello zgfg, where I understand you I am French I leave messages with google translation. Having explanations on other modules is not obvious there is not a French community on XDA which leaves French messages. Thank you for your patience and your help like all the other members thank you

yes I use shamiko and I have LSposed from zygisk instaler, when you say enforce DL I don't understand to update it I have version 0.4.2 (97)
[Magisk] Stillhard:
Get rest thee old man
[Magisk] zgfg:
I'm lazy typing, Enforce DL = Enforce DenyList
[Magisk] zgfg:
Usage HMA = Hide My Apps to hide some apps (one or more) from another app(s) (again, one or more of them)

One guide how to use Hide My Apps for hiding (=detaching) YouTube from Google Play

(If you use Vanced YT you must make sure that Google Play does not detect that YouTube is i installed, to prevent that it updates YT and thuse overwrite YT Vanced):

https://xdaforums.com/t/app-mod-root-nonroot-youtube-vanced-edition.3758757/post-85828495

And another guide how to hide AndroidAuto from Google Play (also to prevent updting AA because certain hacks work only with particular older AA version):

https://xdaforums.com/t/root-only-a...te-android-auto-utility.4194239/post-86119983

Apply little your imagination (to understand and learn) how to 'translate' the guides to hide Magisk app, HMA app, XPrivacyLua app and other LSPosed modules you may have installed (apps A1, A2, A3...), from Oprek Detector, maybe from Applist Detector, some banking apps (apps B1, B2...)

In the given guides 'translate':

- Blacklist template with YouTube or AndroidAuto to blacklist template with apps A1, A2, A3 (apps you are hiding)

- Effective app Google Play (from whom you are hiding) to Oprek Detector, Applist Detector, banking apps (B1, B2...)

More posts (not so detailed) but closer - how to hide Magisk app and LSPosed modules/apps from particular app detectors or certain banking apps:

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

and:

https://xdaforums.com/t/module-magi...p-edits-and-more-v6-1-2.3789228/post-86221337

At the end I have two blacklist templates:

One with YT and AA applied to Google Play - hiding/detaching YT and AA from Google Play

The other template with Magisk app, LSPosed modules apps, applied to Oprek and Applist Detectors and one my banking/payment app

Good luck.

PLEASE don't jump tomorrow or on Monday into this thread and ask: How should I use HMA - before asking, read what was already posted