Magisk General Support / Discussion

[zgfg]

For those who still want MagiskHide with the new Magisk (seems that Alpha will soon remove MagiskHide to provide only DenyList as in Canary) - App Manager Debug root app, v2.7.0 b1667)

App Manager | DEBUG

https://github.com/MuntashirAkon/AppManager RELEASE channel: @AppManagerChannel

t.me

Note: I didn't test since I'm using DenyList (with Shamiko)

 

[traversone]

Good to know. In fact, I still keep that Alpha apk and my corresponding patched boot.img (just in case)

I have updated through all the later Alpha versions, updated LSPosed, HMA, installed and updated Shamiko

Sometime among those updates I started to observe instabilities. I never observed loosing the root but occasionally it loop-boots two or three times (soft- rebooting) before booting successfully. One day it rebooted five times to TWRP (I didn't do anything there except wiping Cache and Dalwik trying to 'help') until it finally rebooted successfully to the system

Since it does not happen on every reboot and since (as mentioned above) I updated various components, I was unable to point to anything specific (Alpha, Shamiko...) but my hunch was that it's maybe related to Magisk (thinking that I saw it first time upon updating Alpha from that version, before all the later updates)

But without a hard proof I didn't want to charge anything or anybody

unfortunately, after re-enabling mobile data/wifi this morning, again root is lost.

going to try latest alpha with zygisk and "app manager" acting as magisk hide

 

[traversone]

For those who still want MagiskHide with the new Magisk (seems that Alpha will soon remove MagiskHide to provide only DenyList as in Canary) - App Manager Debug root app, v2.7.0 b1667)

App Manager | DEBUG

https://github.com/MuntashirAkon/AppManager RELEASE channel: @AppManagerChannel

t.me

Note: I didn't test since I'm using DenyList (with Shamiko)

"could not enable Magisk Hide" comes up when trying to use this feature

of course, I am on Zygisk coherently with the general assumption said before

 

[zgfg]

"could not enable Magisk Hide" comes up when trying to use this feature

of course, I am on Zygisk coherently with the general assumption said before

I don't know, not using. You can ask in TG channel

However, I would at least try with Zygisk disabled (if that's like the old school MagiskHide)

 

[butilka]

If your phone is an old model, launched before A11, then there should be the proper TWRP for the phone and it should work

It worked, before I've had LineageOS installed; Now fasload doesn't do anything to that device.

But what do you mean that it fails from Fastboot.
Does it fail to flash and with what error, or it flashes but then fails to boot?

It displayed < waiting for any device > as if no device is connected.
ADB is able to catch this device, and any other.

Anyhow, I've managed to root the device with the LineageOS recovery screen and a renamed Magisk package:

1) Download Magisk-v23.0.apk to your desktop computer (where ADB is installed)
2) Rename Magisk-v23.0.apk to Magisk-v23.0.zip
3) Enter to recovery mode, on your phone
4) Apply update > Apply from ADB
5) Execute adb sideload Magisk-v23.0.zip
6) Restart

 

[zgfg]

It displayed < waiting for any device > as if no device is connected.

You can always use
fastboot devices
to check if USB cable, Fastboot drivers, etc are ok - seems that's the problem

 

[zgfg]

Module Update Notifications

...So we're getting getting active module.zipUrl with new updateJson!
https://github.com/topjohnwu/Magisk/issues/4908#issuecomment-1015911378

Thanks vvb2060. PW

If I recall correctly, time ago (when Repo was still alive, snd earlier) there was support field in the module.prop, providing a way for developer to put a link to his Github page, XDA thread or anything where users could further find info about downloading the new version, etc

Unfortunately, it was removed (I never understood why was removing good for or neccessary)

Currently, developer can put URL to the description field but it's not clickable (it cannot be even copied from the Modules page in the Magisk app)

IMO, two clickbable fields like support and download would sufficce

 

[pndwal]

For those who still want MagiskHide with the new Magisk (seems that Alpha will soon remove MagiskHide to provide only DenyList as in Canary) - App Manager Debug root app, v2.7.0 b1667)

App Manager | DEBUG

https://github.com/MuntashirAkon/AppManager RELEASE channel: @AppManagerChannel

t.me

Note: I didn't test since I'm using DenyList (with Shamiko)

I've had AM for some time, but public (6.2.1 now), not debug version...

Some nice root features incl. 'Block activities, broadcast receivers, services, or providers', but didn't hide root...
https://github.com/MuntashirAkon/AppManager/tree/master

Just updated to debug 2.7.0 to test AM debug's Magisk hidelist feature, and it seems this app simply intercepts hidelist / DOESN'T do hiding itself... but may be useful to identify isolated processes for apps in Magisk hidelist.

Anyway, this was a mistake, at least w/ my Alpha setup w/ Zygisk; After installing AM debug I checked Magisk app and couldn't access Configure denylist (greyed out)... Discovered I can access it by enforcing denylist then closing app and opening again. List opens / isn't greyed after this. I can then close and open again, but if I disable Enforce denylist it is still accessable one time only. After exiting Configure dentist it is greyed out again and nothing enables it again except.closing / re-opening app w/ denylist enforced...

Since this I have uninstalled AM debug, deleted / reinstalled Magisk app several times, deleted all in /data/adb except modules and rebooted to reconfigure Magisk, uninstalled (removed) and reinstated Shamiko etc to no avail... The behaviour remains the same, although hiding / Magisk etc seems otherwise to work normally... Guessing I will need factory reset to fix strange new denylist behaviour...

Anyway, AFAICS, this is NOT a MagiskHide alternative. What's more, it's uninstall scripts may be buggy / fail to revert all changes... Fair warning... PW

 

[traversone]

I've had AM for some time, but public (6.2.1 now), not debug version...

Some nice root features incl. 'Block activities, broadcast receivers, services, or providers', but didn't hide root...
https://github.com/MuntashirAkon/AppManager/tree/master

Just updated to debug 2.7.0 to test AM debug's Magisk hidelist feature, and it seems this app simply intercepts hidelist / DOESN'T do hiding itself... but may be useful to identify isolated processes for apps in Magisk hidelist.

Anyway, this was a mistake, at least w/ my Alpha setup w/ Zygisk; After installing AM debug I checked Magisk app and couldn't access Configure denylist (greyed out)... Discovered I can access it by enforcing denylist then closing app and opening again. List opens / isn't greyed after this. I can then close and open again, but if I disable Enforce denylist it is still accessable one time only. After exiting Configure dentist it is greyed out again and nothing enables it again except.closing / re-opening app w/ denylist enforced...

Since this I have uninstalled AM debug, deleted / reinstalled Magisk app several times, deleted all in /data/adb except modules and rebooted to reconfigure Magisk, uninstalled (removed) and reinstated Shamiko etc to no avail... The behaviour remains the same, although hiding / Magisk etc seems otherwise to work normally... Guessing I will need factory reset to fix strange new denylist behaviour...

Anyway, AFAICS, this is NOT a MagiskHide alternative. What's more, it's uninstall scripts may be buggy / fail to revert all changes... Fair warning... PW

totally aligned to you!

Actually we would need a fully working Zygisk/Shamiko (still unusable in Android 9 and with some issues in Android 10 on some ROMs)

 

[pndwal]

If I recall correctly, time ago (when Repo was still alive, snd earlier) there was support field in the module.prop, providing a way for developer to put a link to his Github page, XDA thread or anything where users could further find info about downloading the new version, etc

Unfortunately, it was removed (I never understood why was removing good for or neccessary)

Currently, developer can put URL to the description field but it's not clickable (it cannot be even copied from the Modules page in the Magisk app)

IMO, two clickbable fields like support and download would sufficce

Yup, I recall at least the readme.md info was accessible in Magisk app. Since it looks like "description" string will be in use again I already asked if this will make readme.md or other info available in app again - this comment in the original issue (marked enhancement / now closed):
https://github.com/topjohnwu/Magisk/issues/4908#issuecomment-1015911378

... looks like we may have to wait / test to see if we actually get docs back with update notification... PW

 

[zgfg]

Yup, I recall at least the readme.md info was accessible in Magisk app. Since it looks like "description" string will be in use again I asked if this will make readme.md or other info available in app again - this comment in the original issue (marked enhancement / now closed):

Possible module enhancement in lieu of repo... · Issue #4908 · topjohnwu/Magisk

Device: any Android version: any supported Magisk version name: 258e89c Magisk version code: 23013 I wonder if the following possible module enhancement (in lieu of repo) could be considered: It se...

github.com

looks like we may have to wait / test to see if we actually get docs back with update notification... PW

Thanks to @73sydney (PM) for pointing that Fox Mmm (still) supports support= field in the module prop

Taking a closer look, it supports also donate= field and it recognizes where the links point to (XDA, Github, Telegram, PayPal...), by providing then different icons

 

[rodken]

Thanks to @73sydney (PM) for pointing that Fox Mmm (still) supports support= field in the module prop

Taking a closer look, it supports also donate= field and it recognizes where the links point to (XDA, Github, Telegram, PayPal...), by providing then different icons

+1

 

[cognitivedissonance]

Does anyone know how to get the latest BusyBox NDK module now that the Magisk Repo is down? I apparently don't have a saved version of the zip anywhere, and the github does not appear to have Releases.

EDIT: Apparently AdAway was blocking access to the Magisk repo. I am using the En Blu Go hosts list, so I would imagine that any of the En hosts lists would end up blocking it too.

I'm attempting to find what to whitelist in order to allow it to be accessed properly, but the AdAway DNS logger doesn't seem to be of much help. If anyone knows what I should whitelist, please let me know. Oh, and everyone make sure you have a backup of the BusyBox module, because if the Magisk Repo does get shut down and you don't have it, you're SOL from what I can tell.

EDIT 2: For anyone who finds this, I did figure out what I needed to whitelist to allow downloads from the Magisk Repo to complete successfully. It was "cdn.jsdelivr.com" (less the quotes.) It wasn't showing up in the DNS logger of AdAway the first bunch of times I tried it out, and so I was just whitelisting "*.github.com" but that didn't do it (and also isn't necessary since github.com urls are not actually blocked. I'm a bit hesitant to allow jsdelivr to stay on the whitelist b/c I'm not really sure what it is, so I'll look into it. Really though, I may just disable AdAway anytime I use Magisk if I'm trying to grab something from the [now abandoned] Repo.

 

[zgfg]

Does anyone know how to get the latest BusyBox NDK module now that the Repo is down? I apparently don't have a saved version of the zip anywhere, and the github does not appear to have Releases.

1) Google for Github BusyBox NDK, download and install. Magisk app (still) supports installation of locally downloaded zip module files

2) As already asked & answered several times here, you can install (google for) Fox Magisk Module Manager app. More info, incl. about the new Alt(ernative) repository can be found starting from their Github page.
Use of Fox Mmm will replace for you the old (frozen) Repo and the removed support for Repo in the new Magisk 2301x app (Canary or Alpha)

 

[zgfg]

I've had AM for some time, but public (6.2.1 now), not debug version...

Some nice root features incl. 'Block activities, broadcast receivers, services, or providers', but didn't hide root...
https://github.com/MuntashirAkon/AppManager/tree/master

Just updated to debug 2.7.0 to test AM debug's Magisk hidelist feature, and it seems this app simply intercepts hidelist / DOESN'T do hiding itself... but may be useful to identify isolated processes for apps in Magisk hidelist.

Anyway, this was a mistake, at least w/ my Alpha setup w/ Zygisk; After installing AM debug I checked Magisk app and couldn't access Configure denylist (greyed out)... Discovered I can access it by enforcing denylist then closing app and opening again. List opens / isn't greyed after this. I can then close and open again, but if I disable Enforce denylist it is still accessable one time only. After exiting Configure dentist it is greyed out again and nothing enables it again except.closing / re-opening app w/ denylist enforced...

Since this I have uninstalled AM debug, deleted / reinstalled Magisk app several times, deleted all in /data/adb except modules and rebooted to reconfigure Magisk, uninstalled (removed) and reinstated Shamiko etc to no avail... The behaviour remains the same, although hiding / Magisk etc seems otherwise to work normally... Guessing I will need factory reset to fix strange new denylist behaviour...

Anyway, AFAICS, this is NOT a MagiskHide alternative. What's more, it's uninstall scripts may be buggy / fail to revert all changes... Fair warning... PW

Sorry, I didn't fully understand that story, but:

- Shamiko reads from Configure DenyList

-To use Shamiko, Enforce DenyList must be disabled

- While Enforce DenyList is disabled, Confugure DenyList is grayed out

That's the known ('normal') behavior. And that's why users ask that Configure DenyList should not be grayed out while Enforce DenyList is disabled

Because it's troublesome if you need to make a change in DenyList, when you use Shamiko:

You must first temporarily enable Enforce DenyList, for Configure DenyList to become functional.
Finally, upon reconfiguring DL, you must disable again Enforce DL, for Shamiko

---

Anyway, I also tried to use AM Debug v2.7.0 1667 but no success regarding to MgiskHide.
I tried with various combinations in Magisk Alpha app, always rebooting upon, before retrying with AM

When I tried e.g. to enable MagiskHide for gms and gms.unstable from AM (check boxes), AM always reported an error

Besides, it asked me do I want to use my Google account or some XSpace account (?), but failed for both

Maybe we still don't know how to properly use it for MagiskHide

Otherwise, AM seems to be a powerful app manager. However, I'm accustomed to use other app mngrs, most recently Packet Manager (less powerful but enough for what I needed), hence I stopped playing with AM ;-(

Btw, when I uninstalled the AM, I have no artefacts and no issues with Magisk, Magisk app, Zygisk, Shaniko, DenyList - everything works for me as before I tried AM

 

[Lord Sithek]

Guys (especially @zgfg and @pndwal), big thumb up for your patience in explaining everything gazillion times over and over

 

[pndwal]

Sorry, I didn't fully understand that story, but:

- Shamiko reads from Configure DenyList

-To use Shamiko, Enforce DenyList must be disabled

- While Enforce DenyList is disabled, Confugure DenyList is grayed out

Not any more... Reverse is true; see screenshots.

That's the known ('normal') behavior. And that's why users ask that Configure DenyList should not be grayed out while Enforce DenyList is disabled

But I get access (not grey) w/ Enforce disabled, as shown...

Because it's troublesome if you need to make a change in DenyList, when you use Shamiko:

You must first temporarily enable Enforce DenyList, for Configure DenyList to become functional.
Finally, upon reconfiguring DL, you must disable again Enforce DL, for Shamiko

Of course, and that's exactly how it always used to behave, but not since using AM debug!... I cannot get standard behaviour back!...

Once greyed out if I Enforce denylist it stays grey... I have to close magisk app and reopen to get Configure denylist access as I said!! ... And after that I can access it with Shamiko working and denylist NOT enforced too, but only once... Is this normal???

Here you go:

... Expected behaviour reversed!

---

Anyway, I also tried to use AM Debug v2.7.0 1667 but no success regarding to MgiskHide.
I tried with various combinations in Magisk Alpha app, always rebooting upon, before retrying with AM

When I tried e.g. to enable MagiskHide for gms and gms.unstable from AM (check boxes), AM always reported an error

Besides, it asked me do I want to use my Google account or some XSpace account (?), but failed for both

Maybe we still don't know how to properly use it for MagiskHide

Otherwise, AM seems to be a powerful app manager. However, I'm accustomed to use other app mngrs, most recently Packet Manager (less powerful but enough for what I needed), hence I stopped playing with AM ;-(

It just doesn't hide; simply accesses hidelist to show which hidden apps have isolated processes for information purposes... I believe that's what's described in documentation too... PW

 

[pndwal]

Add new build command avd_patch
https://github.com/topjohnwu/Magisk/commit/20ef724fad5e0cbf2ee679406f2333eb17f9121b

I wondered about this / why so much effort! -

John Wu, 3h

Last night I spent an immense amount of time adding support for MagiskInit end-to-end integration testing using the Android Emulator.

As older hardware is more and more difficult to find nowadays, this is important to ensure no regressions will happen...

MagiskInit is *the* most complex, error prone, and difficult to debug part of Magisk. Any minor failures there will make a device simply "stop booting".

With these changes, we can finally test most boot configurations on a PC running emulators w/o the need of physical devices.

This is part of the effort to make Magisk development more scalable, and in preparation for the imminent public release Winking face

There are some significant MagiskInit refactoring planned down the pipeline. Without this infra in place, I don't think I will feel comfortable doing it.

... And now I understand, what you tried to say to me ...
And how you suffered for your sanity
And how you tried to set them free
They would not listen, they did not know how
Perhaps they'll listen now...
They would not listen, they're not listening still
Perhaps they never will... PW

 

[zgfg]

Not any more... Reverse is true; see screenshots.

But I get access (not grey) w/ Enforce disabled, as shown...

Of course, and that's exactly how it always used to behave, but not since using AM debug!... I cannot get standard behaviour back!...

Once greyed out if I Enforce denylist it stays grey... I have to close magisk app and reopen to get Configure denylist access as I said!! ... And after that I can access it with Shamiko working and denylist NOT enforced too, but only once... Is this normal???

Here you go:
View attachment 5512933 View attachment 5512937
... Expected behaviour reversed!


It just doesn't hide; simply accesses hidelist to show which hidden apps have isolated processes for information purposes... I believe that's what's described in documentation too... PW

New AM Debug, v2.7.0 (1669) relesed but no change (despite some fixes claimed on TG)

1) I don't believe that AM is only for monitoring MagiskHide hide status.
Why does it have check-boxes?
Why it reports a fiailure to enable/disable Magisk Hide upon I check-in or check out MagiskHide.
If only to display the status, it should not have (active) check-boxes

2) I see now the problem you reported. But only upon I had Zygisk enabled when playing with MagiskHide in AM.
Indeed, upon I enable Enforce DL, then Confugure DL remains grayed-out.
It's not necessary to re-open Magisk app, it's enough to reopen Magisk Settings page - then Configure DL becomes un-grayed (as expected)

Similarly in the opposite direction, upon disabling Enforce DL, then Configure DL remains functional until you re-open Magisk app, or just re-open Magisk app settings, or open Configure DL for once - only then Configure DL will become grayed-out as expected

To make things worse, uninstalling the AM, and even uninstalling and reinstalling Magisk app does not restore the original/normal behavior of Magisk Alpha app - too much work to uninstall Magisk or to delete /data/adb folder to see would it fix

Definitely a BAD idea to play with AM and its MagiskHide 'functionality', it doesn't work and it breaks something with Enforce DL/Configure DL functionality in Magisk app

 

[cognitivedissonance]

1) Google for Github BusyBox NDK, download and install. Magisk app (still) supports installation of locally downloaded zip module files

2) As already asked & answered several times here, you can install (google for) Fox Magisk Module Manager app. More info, incl. about the new Alt(ernative) repository can be found starting from their Github page.
Use of Fox Mmm will replace for you the old (frozen) Repo and the removed support for Repo in the new Magisk 2301x app (Canary or Alpha)

Haha, I actually did exactly what you listed in (1) and crawled all over both the Magisk Repo and the Osmosis BusyBox Source Repo for the better part of an hour trying to figure out where they may have hidden the zips and then trying to figure out if someone maybe dropped guide on how to build my own. Guess I should've remembered Occam's Razor and just kept on with the Google search, because it turns out the third link down was the right one. Whoops.

While I was able to access the Repo through Magisk still after disabling AdAway, I do appreciate the mention of Fox; I'll have to read up on it. I am guessing it's may not be the new replacement that allows for a URL pointing to a JSON in module.prop that John mentioned in his tweet, but either way it's great to have an alternative to the unmaintained repo in the meantime.

Thanks again for your help!

Guys (especially @zgfg and @pndwal), big thumb up for your patience in explaining everything gazillion times over and over

I'd encourage anyone who makes comments like this to take a second and consider the impact. Thanking someone who tirelessly helps others is a bigtime thumbs-up, but by pairing it up with a snarky tones aimed at those receiving the help, it introduces a negative dynamic that ends up chasing away people away; people who otherwise might have paid it forward, or left a comment that helped someone else (both things that make this place so great.) I speak from experience, because I saw this exact thing happen when I was much more active here, and it did chase people away, which was a shame, because some of them were battling issues that probably were fixable.

Trust me, I completely understand how tiring it can be seeing people ask the same questions over and over, but throwing shade isn't going to do anyone any good; all it accomplishes is inadvertently diminishing the hard work of those helping others, and in this particular case it ended up tarnishing an otherwise very nice complement. I say all this not to condemn you or anyone else, because I've said things very similar myself in the past; I mention it because I hope that by sharing a perspective that I've gained over my years here, it helps promotes positivity, results in good feelings all around, and possibly keeps a few more people here paying it forward.

Anyway, thank you again Zgfg and everyone else who helps out in this forum. You're all awesome and I hope you all have great days!