Magisk General Support / Discussion

[pndwal]

I'm on Android 7.1.2, RR-N 5.8.5 ONYX

Previous versions of magisk gave me the ability to use magisk-hide, even though I had to use "Magiskhide --disable Magiskhide --enable" on every reboot, I really didn't mind. Ive been using this workaround for a LOOOOONG time.

There's a fix for that: create a late_start service boot script. See here:
https://www.didgeridoohan.com/magisk/MagiskHideIssues#

Yesterday I updated to the new version and now everything is broken, I can no longer use my banking app. Magiskhide is no longer working. What is the solution here? I'd LOVE to downgrade but I can't find the means to do so, not even on github. Please help.

New public 22.0?

Sure MagiskHide is toggled on in Settings? Try toggling off, then on again.

Also, if you had Magisk Manager hidden/renamed, did you unhide BEFORE updating app as per instructions/reasons in changelog? If not, you'll have manager/app issues, and need to locate/uninstall BOTH before re-installing Magisk app.

You could try latest debug (Canary) build. It has many fixes. See differences in Release Notes I posted above.

Download apk file from main page Downloads / Magisk Canary link. (Clange extension to.zip to install from Custom Recovery)

Downgrading is easy w/ TWRP / zip package; just download and flash. Restore clean boot.img from ROM package in case of problems.

To download older public builds,, click Releases near end of main Magisk GitHub page, scroll to desired version, click Assets, then (zip) file.

To downgrade to pre public 22.0 releases from Manager/app, you'll need to set hosted address of raw json file for custom channel in app Settings. PW

 

[pndwal]

News:

John Wu, 11h

I have decided that Magisk v22 will be the last major version to support anything lower than Android 5.0. The next major release with the version bump will drop Kitkat and Jellybean support.

Reason:

John Wu, 4h

First video game I played. My 6-year-old dum dum brain cannot solve many of the puzzles LOL

What modesty! Age ÷ 4; We like your Dum Dum efforts John.

Thanks for spilling the J Beans... Have a break! Break a Kit Kat...

No one can handle too much desert, but you GOTTA leave some room for a Snow Cone! PW

 

[proza]

On the Installation page, at the bottom, there is a "Samsung (System-as-root)" section. Does this also applies to the custom ROM?

 

[pndwal]

On the Installation page, at the bottom, there is a "Samsung (System-as-root)" section. Does this also applies to the custom ROM?

Oooh YES!

If device launched w/ Android 9 or later.

You'll need to patch / use boot image for CUSTOM ROM, however that is packaged though...

Some info (patching tar files etc) will be useful for legacy Sammy devices also.

PW

 

[nowster]

I installed https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/ and now CTS is good as well, Safety net is OK, but Google Pay is not working still and now phone is hanging, after OS boot, phone freez.
Help guys..

//edit: phones booted up finally, but Google Pay is still not working, CTS is good.
Any idea?

The freeze is a problem with f2fs filesystem in the kernel.

The fix is to use a different kernel, which for the Pixel 3a and 3aXL MVK is the best maintained.

[KERNEL] [Android 11] [v11.6] MVK - Maximum Velocity Kernel

For those familiar with Velocity Rom this is the kernel I build for it. Velocity hasnt been on XDA as a rule so Im sure not many are familiar. Velocity is my personal Rom Ive been building for years and have shared with all that are interested...

forum.xda-developers.com

 

[newsera]

Hi, I got this app called Singpass, its basically a 2FA app by the singapore government. It seems to detect magisk installation, and detects root even after magisk hide had been enabled and the magisk manager itself being reconfigured to a random package name.

At times magisk hide works on the app, but will stop working soon after. clearing the app cache and ticking unticking the app in magisk hide works sometimes.

I'm running lineage 17.1 with magiskhideprops config enabled - my device is sony kirin, and I'm able to pass safetynet check, any idea how I can debug this?

Did you find a workaround for this? I am running Evo X rom on my Poco and have the same issue. I don't even have Magisk installed and I assume by default the rom doesn't provide root privileges.

 

[Xanth0k1d]

Did you find a workaround for this? I am running Evo X rom on my Poco and have the same issue. I don't even have Magisk installed and I assume by default the rom doesn't provide root privileges.

I wrote a post on this, you can find it under posts by me.
The vkey thing detects your devuce fingerprint as well, so if u r running a custom rom, singpass will not work.

 

[newsera]

Thank you very much! Let me give it a try!

 

[Mr.Brownstone]

Hi guys, first thanks for the hard work ! I have an issue that I think comes from Magisk: VoIP calls make my phone crash (Whatsapp, signal, etc). Looking at the log it seems to be audioserver that crashes, is there any fix for that ? Thanks in advance ! (FP3+, /e/ OS with microG, no Magisk modules installed) Log is here, see line 2546

 

[zgfg]

Hi guys, first thanks for the hard work ! I have an issue that I think comes from Magisk: VoIP calls make my phone crash (Whatsapp, signal, etc). Looking at the log it seems to be audioserver that crashes, is there any fix for that ? Thanks in advance ! (FP3+, /e/ OS with microG, no Magisk modules installed) Log is here, see line 2546

Developers are not really here but on Github - link to Gothub is on the Magisk app.
You will need to report the issue there, following the strict requirements (otherwise, ticket might be closed) about (Magisk) logs, phone, Android, firmware, Magisk version, etc (you will see when you go to open the ticket)

Also, make sure you test without Magisk - if you have no module or root app installed, Magisk, IMO, should not affect the audio driver

 

[DualJoe]

How can i edit files in /system? When i do 'sudo vim /system/etc/hosts' it says 'file is read-only'. I also cannot do a 'mount -o remount,rw /system'. It says '/system is not in /proc/mounts'.

LOS18.1

 

[pndwal]

How can i edit files in /system? When i do 'sudo vim /system/etc/hosts' it says 'file is read-only'. I also cannot do a 'mount -o remount,rw /system'. It says '/system is not in /proc/mounts'.

LOS18.1

Post Android 10, probably with some effort!

Here's one way, incl. info on new 'Shared Blocks' filesystem:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84739785

Magic Mount is the way to do it systemlessly using Magisk. It's essentially what Magisk modules do to load:
https://topjohnwu.github.io/Magisk/details.html#magic-mount PW

 

[DualJoe]

Thanks, found the bug. Instead of 'mount -o remount,rw /system' it's 'mount -o remount,rw /'. Not sure if it works on newer devices as well.

 

[Mr.Brownstone]

Developers are not really here but on Github - link to Gothub is on the Magisk app.
You will need to report the issue there, following the strict requirements (otherwise, ticket might be closed) about (Magisk) logs, phone, Android, firmware, Magisk version, etc (you will see when you go to open the ticket)

Also, make sure you test without Magisk - if you have no module or root app installed, Magisk, IMO, should not affect the audio driver

OK thanks !

 

[proza]

What is "preserve avb 2.0/dm-verity"? Should I check it or not?

 

[JimSmith94]

I'm not 100% sure what bricked my Pixel 5 but after installing the April Security update and patching boot.img, it was stuck on the fastboot screen with no boot image on slot b. I believe it happened because I patched boot. img without checking and installing the new Magisk Manager first. UbreakIFix was unable to force flash so now I'm waiting for them to get in a new motherboard. As I said, I'm not positive this caused it, but perhaps this warning will keep someone else from doing something stupid like I did.

 

[ineedroot69]

What is "preserve avb 2.0/dm-verity"? Should I check it or not?

if you have no plan installing custom rom or you have no intention of modifying the partition that are protected by dm-verity such as system.img and vendor.img (see list of partition here https://source.android.com/security/verifiedboot/verified-boot) .... leave it check

 

[pndwal]

Latest Public (Stable / Beta)​

Release Notes and Changelog:​

2021.4.9 Magisk v22.1​

This release is focused on fixing regressions and bugs. Check the v22.0 release notes if coming from older releases.

Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 will only support Android 5.0 and higher.

Bug Fixes​

• [App] Prevent multiple installation sessions running in parallel
• [App] Prevent OutOfMemory crashes when checking boot signature on PXA boot images
• [General] Proper cgroup migration implementation
• [General] Rewrite log writer from scratch, should resolve any crashes and deadlocks
• [General] Many scripts updates fixing regressions
• [MagiskHide] Prevent possible deadlock when signal arrives
• [MagiskHide] Partial match process names if necessary
• [MagiskBoot] Preserve and patch AVB 2.0 structures/headers in boot images
• [MagiskBoot] Properly strip out data encryption flags
• [MagiskBoot] Prevent possible integer overflow
• [MagiskInit] Fix sepolicy.rule mounting strategy
• [resetprop] Always delete existing ro. props before updating. This will fix bootloops that could be caused by modifying device fingerprint properties.

PW

 

[pndwal]

Latest Debug (Canary)​

Changelog and Release Notes:​

Magisk (f623b988) (22101)​

• Sync with public release

Diffs to v22.1​

• None

PW

 

[stormy1777]

Being Xiaomi, patching boot.img will most likely work despite Ramdisk=no. If your previous successful Installation was installed using zip archive flashed from TWRP, this would confirm Magisk in n boot partition succeeds on your device as zip necessarily installs to boot ramdisk, even if Magisk has to add it. (Works for me -RN8T- and for other models/users also). See below.*

Method:
Select Install Magisk, deselect Recovery mode, Patch boot.img, flash to boot partition using fastboot.

It's not clear what you first did. If you tried direct Install to update, you MUST unhide /restore Magisk Manager/app thru settings menu if hidden/renamed as clearly stated in the changelog (due to new incompatible hiding method) BEFORE updating Manager/app.

If you failed to do so, you likely had working root, but app shows 'n/a' due to the two apps conflicting. You need to uninstall BOTH newly installed app AND renamed (hidden) Manager, before installing app again.

Seems you may have Magisk in recovery partition now also (not sure whether you still have patched boot.img). - To get rooted OS depends on boot method in this case. Did you thereafter (starting from power off):
Use Recovery Key Combo, → (Splash screen) → Release all buttons (to get System with Magisk)?

Nb. Power up normally (= System with NO Magisk),
Recovery Key Combo → (Splash screen) → Keep pressing volume up (= Recovery Mode)

Also, your error message suggests archive download is corrupted, and this may be causing other issues too. Or, if you were still using Magisk patched recovery, this is a likely cause as you CANNOT use zip installer to update Magisk in recovery partition. You may also have TWRP incompatibilities, which is common, and why recovery flashing has been consigned to 'Legacy device support'.

I'd recommend cleaning up conflicting Magisk app/manager(s) as described above, flash clean / unpatched boot and recovery images, check system and recovery now boot normally, Install latest Magisk app, then try recommended patching method I described at the outset, but w/ boot.img, not recovery.img.

*Regarding Ramdisk=no

The current Installation Instructions say:

"if the result is **No** this means your device's boot partition does **NOT** include ramdisk. This means you will have to go through some extra steps to make Magisk work properly."

However, there are exceptions to this where patching and flashing boot image (as if your device's boot partition does include ramdisk) works because the assumption that bootloader is incompatible where OEM doesn't supply ramdisk in boot partition may not be true.

Magisk will add needed ramdisk functionality to boot image where lacking, but Magisk app will continue to indicate factory ramdisk state, ie. 'no', to indicate that bootloader support cannot be relied on. The only way to know for sure whether bootloader does or does not support the Magisk-added ramdisk in boot is to try patching / flashing boot image. Notably, this will work on most recent Xiaomi devices.

While Magisk should install in recovery partition by patching / flashing recovery also in these cases, installing in boot will be a better alternative.

If your bootloader does not support boot ramdisk, Magisk must be installed to recovery. Read the Magisk in Recovery section for VERY important information!

Hope this helps. PW

Thanks for the tips, and time writing.

Being Xiaomi, patching boot.img will most likely work despite Ramdisk=no. If your previous successful Installation was installed using zip archive flashed from TWRP, this would confirm Magisk in n boot partition succeeds on your device as zip necessarily installs to boot ramdisk, even if Magisk has to add it. (Works for me -RN8T- and for other models/users also). See below.*

Method:
Select Install Magisk, deselect Recovery mode, Patch boot.img, flash to boot partition using fastboot.

It's not clear what you first did. If you tried direct Install to update, you MUST unhide /restore Magisk Manager/app thru settings menu if hidden/renamed as clearly stated in the changelog (due to new incompatible hiding method) BEFORE updating Manager/app.

If you failed to do so, you likely had working root, but app shows 'n/a' due to the two apps conflicting. You need to uninstall BOTH newly installed app AND renamed (hidden) Manager, before installing app again.

Seems you may have Magisk in recovery partition now also (not sure whether you still have patched boot.img). - To get rooted OS depends on boot method in this case. Did you thereafter (starting from power off):
Use Recovery Key Combo, → (Splash screen) → Release all buttons (to get System with Magisk)?

Nb. Power up normally (= System with NO Magisk),
Recovery Key Combo → (Splash screen) → Keep pressing volume up (= Recovery Mode)

Also, your error message suggests archive download is corrupted, and this may be causing other issues too. Or, if you were still using Magisk patched recovery, this is a likely cause as you CANNOT use zip installer to update Magisk in recovery partition. You may also have TWRP incompatibilities, which is common, and why recovery flashing has been consigned to 'Legacy device support'.

I'd recommend cleaning up conflicting Magisk app/manager(s) as described above, flash clean / unpatched boot and recovery images, check system and recovery now boot normally, Install latest Magisk app, then try recommended patching method I described at the outset, but w/ boot.img, not recovery.img.

*Regarding Ramdisk=no

The current Installation Instructions say:

"if the result is **No** this means your device's boot partition does **NOT** include ramdisk. This means you will have to go through some extra steps to make Magisk work properly."

However, there are exceptions to this where patching and flashing boot image (as if your device's boot partition does include ramdisk) works because the assumption that bootloader is incompatible where OEM doesn't supply ramdisk in boot partition may not be true.

Magisk will add needed ramdisk functionality to boot image where lacking, but Magisk app will continue to indicate factory ramdisk state, ie. 'no', to indicate that bootloader support cannot be relied on. The only way to know for sure whether bootloader does or does not support the Magisk-added ramdisk in boot is to try patching / flashing boot image. Notably, this will work on most recent Xiaomi devices.

While Magisk should install in recovery partition by patching / flashing recovery also in these cases, installing in boot will be a better alternative.

If your bootloader does not support boot ramdisk, Magisk must be installed to recovery. Read the Magisk in Recovery section for VERY important information!

Hope this helps. PW

@pndwal thanks for the time, tips. helped.
Finally managed to update to magisk v22, with help of an EXTERNAL patcher:

YaAlex3/patcher-oss

ARM32 zImage Patcher. Contribute to YaAlex3/patcher-oss development by creating an account on GitHub.

github.com

It appears there's something "funky" with Redmi 7A in that ramdisk=no, but if patched outside by such tools, it can be added back, then Magisk's patching works.. original thread above has exact steps I've carried out.
Thanks.
Stormy.