search

topjohnwu / Magisk

The Magic Mask for Android
GNU General Public License v3.0
47.66k stars 12.1k forks source link

Unable to install any module on Latest Canary and Debug Builds #6741

Closed Dusk-Golem closed 1 year ago

Dusk-Golem commented 1 year ago

Device: Samsung Galaxy A8 2018 Android version: 9.0 (Nov 2021 Patch) Magisk version name: 25210 Debug & Canary Builds Magisk version code: 981ccabb (25210)

Hello, so after the hair-pulling and annoying issue of #6309 I am back with another one. I just clean installed the latest OS today and tried installing the latest canary build of magisk. First, I must report that the hiding and restoring issue is indeed gone for my device, although I haven't tried spamming hide/restore like @pndwal for testing, I did it once and it was successful.

About the actual issue now, I installed the latest canary, patched boot.img and flashed it and rebooted, enabled zygisk and rebooted. Now when I tried enabling the systemless hosts module, it says successful but the module window is empty. I still continued and rebooted but the result was the same, magisk says "no modules installed".

I am not going to invest any more time in testing. This device is my daily driver and the only one I have and having to go back and forth is, like I mentioned in the issue above, is a problem for me. Sorry if this sounds like complaining but I mean no offence. Maybe I should just throw my phone and buy a classic nokia.

HERE ARE MAGISK LOGS: Before installing modules.log After Installing Modules.log

I haven't tried installing any third party modules because I don't have the time. I am going to stick to debug build 25205 like my man @osm0sis suggested (even though he said the canary one but canary doesn't work for me, so...). I hope someone clears out all the kinks before the next major update.

Peace.

MagiskBot commented 1 year ago

Invalid bug report, automatically closed. Please report issues using the latest debug Magisk build (version code: 25210).

Dusk-Golem commented 1 year ago

Common man, seriously....

Whatever then

Kyliekyler commented 1 year ago

This issue has been already fixed by this commit #6690 but still not pushed to public yet, you may want to consider downgrading to 25209 or the stable version.