Latest Public STABLE Official Magisk:
Magisk Changelog
v24.1
- [App] Stability improvements





Last edited:
Please distinguish Magisk app from Magisk itself (patched into the img, data saved under /data/adb)What happens if you freeze magisk using Link2SD or another app? Will you have to reinstall it from TWRP?
Oh! Thank you so much for educating me and clearing it up. Cheers.Please distinguish Magisk app from Magisk itself (patched into the img, data saved under /data/adb)
You can even uninstall Magisk app, Magisk will continue to work but you will not be able to grant new root requests and manage other things like modules, etc - but what was configured will continue to work.
And you can later reinstall/unfreeze the app and continue to use it for managing
her is a logcat during the rebootconnect your phone to a pc restart your phone then do adb logcat > logcat.txt in powershell let it log till your phone restart then share your log here you'll have a better chance of resolving your issue
01-28 16:36:31.970 6804 9224 E AndroidRuntime: [email protected]*** FATAL EXCEPTION IN SYSTEM PROCESS: Thread-42
You are still on v23 and Hide Magisk app fails - what is exactly the error?I am using Magisk V23, since the V24 launches. I can't create "Hide the Magisk App" of V23 anymore, do anyone get a bug like me
I tried V23 to create "Hide the Magisk App" on many Android devices and have such an error
When creating "Hide The Magisk App" it creates a icon according to the registration name. But that icon is unusable and the old Magisk App remains. Cannot use hidden root at V23 anymore. I have many jobs to do on the old device so I don't want to go to V24 nowYou are still on v23 and Hide Magisk app fails - what is exactly the error?
I suppose that v23 stub somehow connects to the new v24 Magisk app, causing to fail
Frankly, it should not be the case, but bugs are always possible, and specially this story with hiding/unhiding/hidden while updating are known to be 'touchy'
Sorry, bad luck (don't understand why do you need to hide the old v23 Magisk app today now right after the v24 was released, if you hid v23 over the last 9 or so months, there wouldn't be a problem)When creating "Hide The Magisk App" it creates a icon according to the registration name. But that icon is unusable and the old Magisk App remains. Cannot use hidden root at V23 anymore. I have many jobs to do on the old device so I don't want to go to V24 now
well like the guy above said it's caused by:
Tell us: Have you ever hidden the Magisk app?When creating "Hide The Magisk App" it creates a icon according to the registration name. But that icon is unusable and the old Magisk App remains. Cannot use hidden root at V23 anymore. I have many jobs to do on the old device so I don't want to go to V24 now
I have hidden Magisk V23 for 4 months and it still hides good root. Until the V24 appears and does not use hidden Root V23 anymoreTell us: Have you ever hidden the Magisk app?
It sounds like you installed a new Magisk app without unhiding the old app first.
Look carefully at all apps. Start with those shortcuts on your home screen. Press and hold an icon. Select "App info". Look for where it identifies the app -- I think usually at the bottom of the info screen it shows a version number, and maybe from where app was downloaded. If it might be a version of the Magisk app, uninstall it. Do that for every possible Magisk app. (I would reboot at this point -- not Restart; Shutdown and then reboot.) Then install the one version of the Magisk app you want
Re: smaller /dataGood evening, how and why rooting jumps when there is an update. I had the magisk 32fc34f9 24101 update is boom magisk not installed, since yesterday rooting ok I had to redo the rooting.
Also why the internal memory ends up at 15 GB or 32 GB that I have 128 GB on my S10.
well like the guy above said it's caused by:
--------- beginning of crash
01-28 16:36:31.970 6804 9224 E AndroidRuntime: [email protected]*** FATAL EXCEPTION IN SYSTEM PROCESS: Thread-42
01-28 16:36:31.970 6804 9224 E AndroidRuntime: java.lang.IllegalArgumentException: Unknown authority com.samsung.klmsagent.provider
not sure what it means maybe a smarter guy in this forum can tell you but what I did find is someone with the same issue as you and he says that if he restart with the wifi off he doesn't get a reboot
Bootschleife des Galaxy S20 5G, wenn WLAN aktiviert ist
Hi, seit dem Sicherheitspatch Januar 2022, hängt mein S20 in einer Bootschleife fest. Es erscheint nach dem Startvorgang die PIN-Eingabe und wenige Augenblicke danach startet das Telefon neu. Starte ich im abgesicherten Modus, läuft das Telefon normal. Starte ich es danach wieder normal, dann...www.android-hilfe.de
Since Debug and Canary builds are basically functionally identical, they are produced in tandem and appear in https://github.com/topjohnwu/magisk-files/tree/canary (repo/branch).He didn't mention the debug release on the commit, like stable version or canary.
John Wu, May 15
An update to future Magisk releases: the "Canary" channel will start shipping release builds, and a new "Debug" channel will be shipping debug builds. Both channels will be updated at the same time from the same source code, the only difference is the build flag.
Debug builds should only be used if you are actively developing Magisk, or if you want to submit bug reports. An upcoming change will start enforcing APK signature verifications on release builds to combat fraudulent/modded/hacked Magisk app APKs.
We also plan to start adding symbols (and maybe some sanitizers) and enabling core dumps on debug executables for better debugging and auditing. All these changes can be an issue on older device, and could significant effect performance, which is why it should not be used daily.
John Wu, May 24 (8h)
I just pushed out a new Canary build that enforces Magisk app signature verification directly in the root daemon. I have also updated the README on GitHub with guidance for developers working on Magisk itself and distributing your own builds signed with your own keys.
I meant did you ever use patch in app & then flash separately (eg after an OTA) as this is where many (unwary) get kernel mismatches due to using image from earlier ROM etc... This is different from Direct Install...I've had 21.4 for a long while, then last day I updated it via its app which put the phone into a permanent loop of "Phone is starting" across the desktop. I then installed the same 24.3 via TWRP which removed the loop but also took away mobile data.
You may report to Magisk GitHub but you would need to use 24313 Debug and the logs
why should we?
"... Momo enjoys helping Shamiko become stronger in all aspects despite Shamiko's goal of defeating her..."
libsu 5.0.0 is out!Looks like major libsu release is now imminent; most fixes are now merged.
Should see major stability improvements in Magisk and root app implementation... Should see new commits for Magisk proper again soon too!
John has made some major libsu changes (see libsu GitHub).
Here are extra comments on vvb2060 fixes from her TG (Chinese translated....
PW
John Wu, 2h
Major libsu update 5.0.0!
Introduces a new module "nio" to perform I/O operations through root services, moving away from the error prone, inefficient shell command backed I/O the library used to provide.
It's already using splice under-the-hood. There is already some Linux magic!