Magisk General Support / Discussion

[m0han]

... tested also MagiskCustom... with Zygisk No and MagiskHide Yes. Modules:
- Riru
- Riru-LSPosed (GravityBox-R)
- Riru-Momohider

i refer to screenshot 5.jpg in your post above. i have almost the same setup as you. yet, magisk detector reports that 'su file exists in path'. how can i resolve this? i have just installed Momo hider module. any further configuration required? i'm running the latest magisk alpha.

 

[pndwal]

I just want to instal stable 23 version. And i download zip file, install this zip file by TWRP but MM still show me old version 22.1. And i can't install any modules because the module, log, etc, buttons from bottom of the screen disappeared.

I have no buttons on bottom, just look at the SS. Root Checker shows my phone is no rooted...

Screenshot showing Magisk not installed, so no bottom menu...

Edit: [Seems you may have a previous manager /app installed causing conflict (can't see Magisk/root). Have you searched settings / apps for that as previously described?]

Actually, seems TWRP might be the issue, and ruined previous root... (This is a common problem and reason John depreciated Custom Recovery installation method...)

If you can restore previous old root (backups?) you should be able to update from app using Direct Install...

With existing old root ensure Magisk App is restored first (not hidden), then uninstall the Magisk App, download the late version (APK) you want, install app, update within app (direct install)...

If you can't restore you should do as @zgfg advised above. PW

 

[zgfg]

i refer to screenshot 5.jpg in your post above. i have almost the same setup as you. yet, magisk detector reports that 'su file exists in path'. how can i resolve this? i have just installed Momo hider module. any further configuration required? i'm running the latest magisk alpha.

To hide su from the path, you need isolated option. On the Momohider Github page you have instructions

 

[lokopol]

¿Significa actualización de Magisk o Rom?

Estos síntomas suelen ser un indicio de que la imagen de inicio no coincide ...

¿Tomó una actualización de OTA y restauró la imagen de arranque previamente parcheada, o quizás actualizó Magisk pero parcheó una imagen de arranque extraída de una ROM antes de una actualización de OTA u otra ROM por completo? ... PW

Meaning Magisk Update, or Rom?

These symptoms are often an indication of mismatched boot image...

Did you take an OTA update and restore previously patched boot image, or perhaps updated Magisk but patched a boot image extracted from a ROM prior to an OTA update or other ROM entirely?... PW

thanks for answering. no, my stock ROM worked fine, it was with the magisk update when the wifi connection stopped working.

 

[pndwal]

thanks for answering. no, my stock ROM worked fine, it was with the magisk update when the wifi connection stopped working.

And you never took OTA since initially Magisk installation? PW

 

[lokopol]

And you never took OTA since initially Magisk installation? PW

No

 

[pndwal]

No

Have you tried new Canary released only an hour ago?

Says fixes crashes caused by patching process; may have been other issues fixed - worth a shot. I'd start fresh ( un-patched boot image) with it... PW

 

[pndwal]

No

Also, did you ever use Custom Recovery installation, or Patch, Fastboot flash and update w/ Direct Install? PW

 

[Dwightsch]

Okay @topjohnwu you're probably sick of the "sell out" stuff and just flaming over the changes in magisk in this new direction you're taking this great project since your employment at Google. I totally agree with you. I think devs and apps and... Should have the option to "opt out" of any modification. but riddle me this, when I have some banking app, some other system app or whatever and that has nothing to do with the modifications I have using root, should they force me to unroot my phone? It's their choice that I shouldn't mess with their app but is it theirs to demand I either choose banking or modifications to other parts of my phone? My point being, if it's at all possible, consider adding Deny list functionality for system apps because currently it doesn't work on any and Hide options for apps that force you to either choose magisk or their app, regardless of what you're modifying. You can factor out any app or service that Google runs but a "choice" for users to bypass detection and modification for apps and services that insist you don't root android and enforce that whether by themselves or using Google services, would be great and probably in sprit of your current decisions.
Other than that, cheers and thanks.
I hope you stay strong and healthy.

 

[abagm]

Which of the things doesn't match the others?
To my great delight, I discovered a ROM for Samsung S5e (kminilte) with Android 9. Runs great - just can't get Magisk to work. Have tried alpha, Hitman's and JohnWu's new releases. Neither with TWRP nor with the direct patch of the boot.img (and flash via download mode) I get further - the flashing stops with every method when repacking the bootimage, without anything being flashed/patched. Do I have to mount anything manually or so? Honestly, I do not get through meanwhile - is there somewhere a working guide, which system requirements, which flash method and which other requirements should be given? Here in the thread I have bravely read along - as far as I know, I have also tried all the instructions, but no Magisk was installed. I do not need SNP, only ROOT and Hiding Root and the ExSD card module. I'm not sure, but I had the impression that Zygisk (first two alpha versions up to ...31 I could still completely flash via TWRP) brings my device into bootloop /freezing. Should we users (who do not have their own dev skills) rather wait until there is any beta or use an old Magisk classic or have I overlooked / not understood something essential?

 

[pndwal]

Which of the things doesn't match the others?
To my great delight, I discovered a ROM for Samsung S5e (kminilte) with Android 9. Runs great - just can't get Magisk to work. Have tried alpha, Hitman's and JohnWu's new releases. Neither with TWRP nor with the direct patch of the boot.img (and flash via download mode) I get further - the flashing stops with every method when repacking the bootimage, without anything being flashed/patched. Do I have to mount anything manually or so? Honestly, I do not get through meanwhile - is there somewhere a working guide, which system requirements, which flash method and which other requirements should be given? Here in the thread I have bravely read along - as far as I know, I have also tried all the instructions, but no Magisk was installed. I do not need SNP, only ROOT and Hiding Root and the ExSD card module. I'm not sure, but I had the impression that Zygisk (first two alpha versions up to ...31 I could still completely flash via TWRP) brings my device into bootloop /freezing. Should we users (who do not have their own dev skills) rather wait until there is any beta or use an old Magisk classic or have I overlooked / not understood something essential?

Yup - you need to read / follow official Installation Instruction linked from Magisk home page; pay special attention to Samsung section... PW

 

[m0han]

To hide su from the path, you need isolated option...

got it. many thanks. had to run setenforce 1 to get the 3rd screenshot.

 

[pndwal]

Latest Canary Magisk

Magisk (ea75a09f) (23011)

• Make Zygisk survive zygote restarts
• Fix crashes when Magisk environment was not properly setup. This will fix the crashes experienced after installing Magisk with patching boot images.

Diffs to v23.0

• [General] MagiskHide is removed from Magisk
• [General] Support 64-bit only systems
• [General] Support Android 12
• [Zygisk] Introduce new feature: Zygisk
• [Zygisk] Introduce DenyList feature to revert Magisk features in user selected processes
• [MagiskBoot] Support patching 32-bit kernel zImages
• [MagiskBoot] Support boot image header v4
• [MagiskInit] Support /proc/bootconfig for loading boot configurations
• [MagiskInit] Better support for some Meizu devices
• [MagiskInit] Better support for some Oppo/Realme devices
• [MagiskSU] Use isolated devpts if the kernel supports it
• [resetprop] Deleted properties are now wiped from memory instead of just unlinking
• [App] Build a single APK for all ABIs

[App] Switch to use standard bottom navigation bar

[App] Downloading modules within the Magisk app is removed

PW

 

[pndwal]

got it. many thanks. had to run setenforce 1 to get the 3rd screenshot.

Nb. There may be issues with isolated as per GitHub page for module. - it is deprecated and replaced by setns (need isolated + setns). Without Zygisk you should be able enable all options. In Alpha with Zygisk + Riru co-existing, only isolated & initrc work. PW

 

[pndwal]

LSPosed Telegram group reporting LSPosed & Magisk on WSA + GApps, and just confirmed that GApps works on both arm64 and x64. PW

 

[rodken]

new alpha is out and working fineView attachment 5442539
Changelog:

- Fixed magiskd may crash
- Support Zygote restart
- Fixed CWD process across namespace in isolated namespace mode
- Improve deny list loading
- Use Traditional Search list in deny list

According to your screenshot, you might want to toggle your 'Update Channel' so that the current version matches the latest.

There is a newer alpha version released as of this writing?

 

[zgfg]

Nb. There may be issues with isolated as per GitHub page for module. - it is deprecated and replaced by setns (need isolated + setns). Without Zygisk you should be able enable all options. In Alpha with Zygisk + Riru co-existing, only isolated & initrc work. PW

With or without setns I have no difference. For me only isolated works (hiding su from the path)

With setns but without isolated - su is visible again in the path

Sticking with isolated - it worked to me with all flavours and Magisk versions (of course, without Zygisk and with Riru)

 

[Eng.Raman]

got it. many thanks. had to run setenforce 1 to get the 3rd screenshot.

Why you need to run setenforce 1 to get a screenshot ?

 

[Makishima]

I'm on the latest Magisk Canary released a few hours ago, I see people putting Google Play gms and so on on the denylist yet I can't see it listed. Do you do it via terminal? And if so, how? Or are you using a different version of Magisk?

 

[Eng.Raman]

I'm on the latest Magisk Canary released a few hours ago, I see people putting Google Play gms and so on on the denylist yet I can't see it listed. Do you do it via terminal? And if so, how? Or are you using a different version of Magisk?

Magisk → Settings → Configure DenyList → Search icon → Show system apps → Search for gms in Filter by name.