yashsingh1/xdaforums huggingface dataset:
[Magisk] phrichuk99:
After many months of running Magisk App etc. with no update option popping up, and everything Magisk just continuing to work for me, a couple of days ago I saw and pressed the update button, and upgraded to 24.1, without realising just how much had changed. Luckily I found this thread quickly, otherwise I really would have struggled!

So, thanks to this thread (which I have read all the way through), I undertand the reasons for the changes, and have got most of my stuff working again in the new model (e.g. Sky TV app, my banking apps as well as play protect cert, Google Pay), but I have two questions:

1) Does anyone have a recipe for 'Microsoft Company Portal'? It now seems to detect the 'suspect' nature of my phone, whereas it did not before I upgraded.

2) I used to use App Systemizer for Magisk by Stangri (https://xdaforums.com/t/module-app-systemizer-for-magisk-v9-v14-deprecated.3477512/), but it no longer seems to install/work and it seems to be deprecated; what is the idiot-proof way to systemize apps in the new world please?

Thanks again for a helpful and focused thread.
[Magisk] Lord Sithek:
I don't have a quick answers to your questions, but I want to congratulate you for being the proof that it is possible to read with understanding and find the necessary information! 🤝🏻
[Magisk] Fif_:
You'll need https://xdaforums.com/t/module-terminal-app-systemizer-v17-3-1.3585851/post-84330057
[Magisk] Hallux_:
Yes, you can make it work just using Universal Safeynet Fix & Deny List. Add all MS apps in deny list, make sure to delete app data for intune/teams/outlook.
[Magisk] szazs89:
So, I've recently updated to Magisk v24.1 on an older device, SM-G920F, w/ custom ROM LOS-16.0.

Originally, I had a hidden Magisk v22.1... So,

I have firstly updated the app to v24.1 from the "app card" (discarding the warnings from GPlayServicesProtect about unknown app),

then the zip from the "Magisk card" clicking on Direct install (no manual boot.img searching and flashing, etc.)

Reboot, as suggested

Since I didn't unhide Magisk before the upgrade, the renamed app have to be accessed from the App Drawer.

Configuration:

Settings: enable Zygisk and select apps in the DenyList (GPlayServices can be left out)

Modules:[Install from Storage] manually the following zips downloaded from GitHub links given in the posts

MHPC (for custom ROM) and USNF as described in #3

Shamiko (to hide Magisk itself) #9 and ensure the Enforce DenyList is OFF in the app Settings

Reboot, again

Checks:

MHPC: from su terminal using command props, see #7

shows "everything" active as required

EDIT: because of using custom ROM fake STOCK fingerprint (Samsung Galaxy S6)

USNF: using installed YASNAC from PlayStore:

Basic Integrity: PASS

CTS match: FAIL PASS (after faking fingerprint in props)

Evaluation type: BASIC

Apps: most of them seems to work, except a new Banking App (complaining about SafetyNet). Maybe it is related to the failing CTS profile match mentioned above.

Any hints to resolve this? Should I switched on DenyList Enforcing (despite of installed Shamiko)?

PS: it would be nice, if the installation guide of SHamiko can be found either in its GitHub repo, or in post #9...

EDIT2: [SOLVED] the new app was forgotten to be added to the DenyList
[Magisk] pndwal:
Good, needed SafetyNet pass.

(Don't enable denylist; Shamiko is 'borrowing' it but doing extra hiding itself; extract readme.md from zip archive to see release notes / usage)

- Play Protect 'Device is certified'?

- Added bank app to denylist, then cleared its data?

Which bank app? 👍 PW
[Magisk] szazs89:
- where can I see this? In PlayStore I can force PlayProtect check, which finds no harming apps...

- anyway, the second guess was the winner: the former app was upgraded through installing a new banking app (OTP SmratBnak), which I forgot to add to the DenyList.

Finally, everything is OK. :cool:

Thanks!
[Magisk] pndwal:
Good stuff!

Guess if you look in Play Store settings, about, last item, you'll see Device is certified then... 👍 PW
[Magisk] szazs89:
I see...

Galaxy S6, SM-G920F, Pie (LOS-16.0) ROM: no such info - only about the opensource licenses and PlayStore version (???)

Magisk v24.1, apps - no problem

Galaxy S7 edge, SM-935F, Oreo stock ROM: device is certified - OK

Magisk v23.0, apps - no problem (not yet upgraded to 24.1)
[Magisk] szazs89:
I see... Hm,

Galaxy S6, SM-920F, Pie (LOS-16.0) ROM: no such info - only about open source licenses and PlayStore version (???)

Magisk v24.1, apps working as expected

Galaxy S7edge, SM-935F, Oreo stock ROM: device is certified (OK)

Magisk v23.0, apps working as expected
[Magisk] quasimoju:
Could anyone help with s-pushtan on pixel 6 android 12 rooted? Tried it with lposed and hma but it's not working for me.
[Magisk] pndwal:
My Play Store is 29.0.15-21...

IIRC older versions still displayed certification status at end of settings... PW
[Magisk] pndwal:
I posted a solution that was working for most here:

https://github.com/topjohnwu/Magisk/issues/1084#issuecomment-964222271

With latest P-Tan update it no longer works for me (on MIUI device) and a number of others, but some users/devices are still still hide 'root' fine.

Some Simply had to add extra apps to LSPosed-HideMyApplist, eg:

https://github.com/topjohnwu/Magisk/issues/1084#issuecomment-1016084224

😬 PW
[Magisk] xabu:
The hero2lte or Galaxy S7 Edge is my treasure too ... It might be a good idea to add your post and nice guide to the latest @Ivan_Meler Rom with Anroid 12 for the Galaxy S7 and Galaxy S7 Edge. Maybe a new challenge for you ?? Thanks again for the detailed and good info.
[Magisk] quasimoju:
Oh I got it to work, I m just stupid that's what it was. I had to add hma also on the list not just magisk to hide now it works fine. 😂🤦🏻‍♂️
[Magisk] beeshyams:
Firstly, thank you for the pointers, secondly apologize for possibly bugging you and thirdly again apologize for hijacking this thread

I got the hang of it and all but XPrivacyLua is found only in "suspicious environment" - rest all pass. Is this normal?

Magisk 24.1, Lsposed Zygisk latest, Magisk Zygisk module for HMA installed

Any clues please. Feel free to ignore.
[Magisk] zgfg:
LSPosed Manager apk can be safely uninstalled, it will create the shortcut and there are also other ways to invoke the uninstlled LSPosed mngr apk - the so called Parasitic behaviour, it's well explained on the LSPosed Github Readme

I don't use XPrivacyLua for two+ months, but I think I also had problems with Applist Detector detecting it even upon I uninstalled - I had to manually delete some folder, maybe /data/system/xlua, not sure anymore
[Magisk] beeshyams:
Thanks for your time and explanation
[Magisk] meric57:
Good evening, I have a notification with message expand notification, it must be YouTube Vanced or microG Vanced. I don't know if it should be deactivated or not as it is activated
[Magisk] pndwal:
Used to work w/ just hidden Magical app added. Needed HMA and others added since last P-Tan update. PW
[Magisk] pndwal:
New Canary 24102:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86381851 👍 PW
[Magisk] szazs89:
Actually, it was about an S6. The S7 Edge is still in the queue... :)
[Magisk] zgfg:
And the new Shamiko v0.4.3 (100) released:

-Fix tmp mount being detected

Update through the Magisk app, Modules window (Shamiko, Update icon)
[Magisk] Palazzo_K:
Where can I find Shamiko GitHub page? Whenever I try to install it say:

! Only support SDK 27+ devices

! Installation Failed
[Magisk] Palazzo_K:
I don't know why, but with my S7 Flat, no version besides Canary 24102 recognize magisk core. Even installing this version, no matter what I do, Zygisk keeps saying 'No' after activating and reactivating. Shamiko also cannot be installed as I get the message 'Only support SDK 27+ devices'. I'm seriously thinking about switching phone.
[Magisk] zgfg:
Releases · LSPosed/LSPosed.github.io

Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.

github.com
[Magisk] m0han:
md5: d3554771b39f991129184a0066fe192d

md5: f0f88bfffb40e3ef23bae5029ca5fa48

which one to go with?
[Magisk] zgfg:
Interesting, strange.

You could unzip and compare or ask in the (LSPosed ?) TG channel

Since of the Update mechanism for modules, I always update that way, not by downloading manually from the Github
[Magisk] m0han:
the md5 has changed again for the 'in-app update', although the time is still 8:20.
[Magisk] meric57:
Hello, yesterday I activated impose exclusion list and I had to get a magisk settings shortcut, I have the settings shortcut and no more magisk icon why activating impose exclusion list hides the magisk icon.

When I press on settings I have the magisk interface with good version and all the rest install.
[Magisk] xabu:
This is normal behaviour as soon as the Magisk module is hidden. You were given "this" choise while hiding your Magisk.
[Magisk] hungtinglung:
if you want to use shamiko module,then you must turn off enforce denylist in magisk settings.

tick only what app you want to hide root at denylist.
[Magisk] pndwal:
New Shamiko 0.4.3

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

👍 PW
[Magisk] DaOldMan:
Anyone knows how to hide root from this app? It's called S. Check.
[Magisk] Spartacus500:
What is this app ?
[Magisk] DaOldMan:
This one. Always detects I am rooted :-( no matter what:

Security Check - Device compliance for payments
[Magisk] Stillhard:
That's the most easiest checker I see, use your luck with Momo instead, don't bother to use it
[Magisk] Spartacus500:
For me, the same as for you 😔
[Magisk] zgfg:
Probably you also have Magisk or Bootloder unlocked in Momo?

I have them detected, and cannot pass this one either (hence, 'easy' or not depends on the phone, ROM, etc)

MIUI 12.5, A11
[Magisk] wiston86:
Hi, i have the same situation.

At the moment i have unroot all.

I have tried the sequence for Samsung devices on the guideline, but the smartphone stuck in the download mode, without start.

So i have re-flashed the stock version.

If i try to install as zip, i have only the APP but not magisk...so NO ROOT.

I have a question for @Prof_Shekhar : how you have re-installed magisk version 23? with TWRP and zip files?

thanks
[Magisk] wiston86:
Hi @Prof_Shekhar , can you please write the exact sequence that you have used? because i'm not able to re install magisk..thanks
[Magisk] Prof_Shekhar:
@wiston86

After I uninstalled the Magisk 24.1 using the Magisk 23.0 App, rerooted with the Magisk 23.0 and reinstalled the Magisk 23.0 app using patched Magisk 23.0 AP file vía ODIN3.

All worked well except I wasn't able to hide the Magisk app itself and this resulted in most of the banking apps not working.

Let me know if I can be of any further assistance.
[Magisk] wiston86:
Thank you for the reply.

When you say "After I uninstalled the Magisk 24.1 using the Magisk 23.0 App": so with an unrooted device, you have installed the Magisk 23.0 app, and unistalled from this version? how?

thanks
[Magisk] zgfg:
I hope you were able to hide Magisk v23 apps.

It's been written a lot about, the hint is to set the Custom channel, pointing to json for v23.

Either in this or in the old Magisk thread there was a post this weekend with URLs for Custom channels for the couple of previous versions, incl. v23
[Magisk] Prof_Shekhar:
@wiston86

Sorry, if I wasn't clear enough.

To begin with, my device was rooted with the Magisk 23.0 and had Magisk app 23.0. I was able to hide the Magisk app itself with flying colours. They both worked very well until one day I took the bait and decided to upgrade to 24.1.

All I did was to hit the update button on Magisk app and it updated the app to 24.1 but with no no functionality left in it. Root didn't upgrade to 24.1 but was still version 23.0

To get out of this picquet situation, deleted the Magisk app 23.0 which was also now partially crippled but atleast gave me an option to uninstall the Magisk root 23.0, hence I removed the Magisk root 23.0

Now there was no root and no Magisk app left in the device.

Now reinstalled the Magisk app 24.1, patched the AP (Boot image) file from the stock firmware using the option in the Magisk app for patching.

Then, pulled this patched boot image AP file and reflashed the device with the help of ODIN3 and other 3 stock firmware files.

This rerooted my device to Magisk 24.1 which was confirmed by root cheker. However the Magisk 24.1 app showed my device not rooted.

Deleted the Magisk 24.1 app, reinstalled Magisk 23.0 and now it showed my device rooted with 24.1.

This is my current situation.

Now as suggested by one of the senior members to search for the hidden Magisk app (1st instance) and delete it.

Now, I have spent my past 2 days searching in system directory for all elusive hidden Magisk app. Unfortunately, success still has still eluded me

Hoe you are in much better situation.
[Magisk] DaOldMan:
I don't know what Momo is, I have OnePlus 6T. Can't ever pass this "easy" app even that I don't have key attestation disabled on the device. No idea what to do.
[Magisk] Prof_Shekhar:
@zgfg

Thanks for your reply.

After going through so much pain and struggle in the last one week to get my Magisk app 24.1 communicate with its root and be able to try Zygisk, I may not give up my quest any time soon.

Hope to continue to receive your guidance and support.
[Magisk] simplydat:
You should just factory reset your phone and start over at this point.
[Magisk] pndwal:
Nb. This issue

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

(Last working version 23.0)

https://github.com/topjohnwu/Magisk/issues/5339

Is now fixed / merged / available w/ canary 24102.

The only tester had very old kernel (Kernel Version: 3.18.91-13895453-QB29822865) however, and Zygisk wouldn't start. This issue is already addressed by #5372 but only for kernel version >= 3.19...

Seems #5339 is a proper fix as long as you have 3.19+ kernel. If not, see #5395

---------​

If you really want to downgrade, you can simply use the app if you wish. Follow instructions for Custom Channel here:

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

- Ensure app is restored (not hidden).

- Take Install App (Latest should now show 23.0) first. Downgrades will likely fail, but you will find apk in Download folder set in Magisk app. Just uninstall current app then install APK manually.

- Take Install Magisk. You will have Patch file option, and Direct install if you have existing root available.

Putting proper JSON URL in Custom Channel allows 'Hide the Magisk app' to work as it calls compatible (matched) older stub file instead of latest version.

🤠 PW
[Magisk] Prof_Shekhar:
Hi @simplydat

I have already factory reset the device not once but twice. However, the situation didn't change.
[Magisk] mingkee:
Root is in /system

You must clean install the whole ROM
[Magisk] pndwal:
NO! 😱

Magisk root is systemless!

Root is in ramdisk in a boot partition w/ config files / overlays in /data/adb!

😳 PW
[Magisk] Prof_Shekhar:
I have clean installed the stock firmware (all 4 files) using ODIN and later using the Magisk 24.1 patched AP file.

But I am still not able to find the hidden Magisk 23.0 app

Even adb shell pm unhide com.topjohnwu.magisk failed to yield any result.

Deleted, every possible instances of Magisk from the / (system) directory, including deletion of the all those files which are not present on similar device. But it was of no avail.
[Magisk] Prof_Shekhar:
@pndwal

Thanks for showing me the right direction.

I may sound silly, but highly appreciate if you could help me with how to wipe this ramdisk in boot partition. I thought that once I deleted everything present on the device using TWRP advance wipe function, I got rid of the past baggage. But it now seems, it may not have been the case.
[Magisk] PanTh€R:
@Prof_Shekhar

Instead I think that some leftovers of v24.1 are creating the mess. As per his opinion on factory reset, I would suggest to go for a clean flash via odin and re-root with v23. That will surely do the work unless you wanna try to get v24.1 work on your device. (But you will lose your data and apps)

But yes, giving up isn't an option, searching or trying for a solution will help the community and new beginners.

Edit: Also clean your A/B partition.

As per ramdisk, it is in the boot image and also in the recovery image which is kind of boot image.

So you may need to check the recovery image.
[Magisk] pndwal:
Removing root is as simple as reversing rooting process.

You don't need to wipe ramdisk within partition; you flashed a magisk-patched version of either boot or recovery* image (Nb. both boot and recovery are boot partitions). Just flashing back unpatched 'stock' boot image (boot or recovery depending on device) reverses root for most devices. Newer Samsung are a special case; it seems a proper return to stock must be accompanied by a full data wipe by flashing AP + BL + CP + CSC. See Special considerations below.

Nb. While /system is always untouched, /vbmeta, /vendor or other partitions may be altered when flashing patched boot image to allow root on some devices.

Special considerations -

John's Important Notes for Samsung Devices launching with Android 9+:​

Never, ever try to restore either boot, recovery, or vbmeta partitions back to stock! You can brick your device by doing so, and the only way to recover from this is to do a full Odin restore with data wipe.

To upgrade your device with a new firmware, NEVER directly use the stock AP tar file with reasons mentioned above. Always patch AP in the Magisk app and use that instead.

Never just flash only AP, or else Odin may shrink your /data filesystem size. Flash AP + BL + CP + HOME_CSC when upgrading.

* when ramdisk in boot partition = no. Nb. Magisk is actually showing if OEM Ramdisk in recovery = yes or no. Since recent Magisk installs a basic ramdisk if missing, ramdisk in boot will actually now = yes if boot.img is patched, but OEM ramdisk in boot (displayed) = no. This is correct behaviour because the new ramdisk for these devices generally fails to function due to bootloader incompatibly. In the case of Xiaomi and a few other devices, the bootloader is inexplicably compatible allowing for Magisk in boot despite Ramdisk = no displayed.

The baggage is another story. It resides in /data/adb. When stock images are restored it is harmless, but if a prior Magisk installation is incompatible (eg often when downgrading but seldom upgrading) or had become borked, bootloops and other issues can / do occur on restoring a Magisk root solution. Further, uninstall.zip or uninstall scripts in app may fail to execute properly.

In this case, the db (database) or the whole /data/adb can simply be (safely) removed# (using twrp or other means) and the Magisk Daemon will restore a clean / working configuration on booting. Borked configurations can actually be rectified at any time by deleting /data/adb and rebooting; reflashing patched boot image is not necessary.

# Before deleting /data/adb it is best practice to uninstall all modules using remove button, if that's still possible, to run their uninstall scripts. Simply deleting /adb directory will properly remove module /system overlays, but modules may make other changes in data that will otherwise remain. In practice this seldom causes issues however.

🤠 PW
[Magisk] Prof_Shekhar:
@pndwal

Thanks for showing me the right direction.

I may sound silly, but highly appreciate if you could help me with how to wipe this ramdisk in boot partition. I thought that once I deleted everything present on the device using TWRP advance wipe function, I got rid of the past baggage. But it now seems, it may not have been the case.

Awaiting your reply.

Hi @PanTh€R

Thanks for your reply.

What really surprises me is the fact that I have twice reinstalled the stock firmware using ODIN 3, once without patched boot image followed by the installation of Magisk 23.0 using TWRP and second time reinstalled the stock firmware with patched Magisk 24.1 using ODIN 3. Unfortunately, the issue has still persisted.

For the past 2 day, I am trying to various files of installed boot image under root/dev/block/platform/*

and try to open each of those files including persistent to see if I can find hidden Magisk app. Strangely all these files are showing content as 0 B. May be I am not using the right tool to open these files or they actually don't contain anything.

Do you know if it is the case or I need some special software to investigate the above mentioned files.
[Magisk] J.Michael:
Please stop looking for the hidden Magisk 23.0 app. When you clean installed stock firmware and wiped data, you eliminated any "hidden" app. You probably never had a hidden app.

@pndwal has cited a known problem that is probably your problem. He has cited a new canary build that might address the problem. If you don't want to stay with 23.0, your next attempt to upgrade should involve this latest canary build.

You might post your kernel version -- the note about a possible fix mentioned limits on which kernels could be helped.
[Magisk] pndwal:
@Prof_Shekhar

Nb. I've added John's special considerations for newer Samsung devices to post above.

Also my dear Watson, seems you didn't test earlier fix, but I suggest now you do try w/ latest Canary build; see @J.Michael's advice above. Much effort has been spent on these recent fixes for Sammy.

👍 Sherlock.
[Magisk] Prof_Shekhar:
Hi @pndwal

Thanks for very detailed information and precise steps to follow.

I have done the stock firmware flashing so many times using all possible methods under the sun (ODIN, adb fastboot etc) that I can do flashing of Samsung galaxy phones while in sleep. Disected almost all files on which I could lay my hands with an intent to find the smoking gun, but all my efforts have come a cropper. Wondering if all these didn't get rid of the remanants of the missing Magisk app 23.0, what would do.

Worst, due to excessive use of the power and Bixby buttons of my device, I have lost both of them. Now I use 2 toothpick to get around the problem 😁. But still pressing on.

I didn't have any chance to install any module on this phone while it was functioning well with root (had planned to do so only when I found my way around).

As I have nothing to lose (there are no data whatsoever on this phone), I will continue to fix this Magisk issue until this phone gives up ghost.
[Magisk] Prof_Shekhar:
Thanks @pndwal.

Would follow your suggestion today.

Will post the outcome 🙏🏻

Thanks @J.Michael, for your suggestion to stop looking for missing Magisk app 23.0 which even I was getting convinced that it may not have vsurvived so many onslaught.

Will check the kernel version and get back 🙂
[Magisk] Prof_Shekhar:
Hi @J.Michael

Kernel version: 4.4.111-21737876

Android Pie (9)

Device: Samsung Galaxy Note 8
[Magisk] pndwal:
Told you many posts back it's not dual app issue; symptom (root present but App says Installed - N/A) is identical, but seems the issue was Busybox.

Fortunately for you the fix was actually derived from testing / analysis of logs in this 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​

https://github.com/topjohnwu/Magisk/issues/4174

since early April.

Fix:

Make sure busybox can be executed recursively …

Busybox will execute itself. On some older Samsung devices, when it is located in /data, it will not have rights to execute other programs including itself. We should also relocate busybox in this case to workaround Samsung bull****.

See topjohnwu/ndk-busybox@bdc8655

Fix the "app doesn't detect installed Magisk" issue in #4174

canyie authored and topjohnwu committed 9 days ago

Strangely, the initial issue for armeabi-v7a devices is still open despite the fix (for further testing?) while the issue for your arm64-v8a device was closed after just one user got Magisk recognised in App. He had the old kernel issue however, and couldn't activate Zygisk.

Hope it works for you Capt-watson, Prof_Shekhar, Dr Spock or whoever you are. 😜

😀 PW
[Magisk] pndwal:
... Apparently working with kernel version >= 3.19... 😉 PW