Database Develop

modules fail to install

so I'm running a Huawei nova plus and magisk works fine but modules don't install no matter in twrp or magisk app I get halted at /data/magisk_merge.img failed to mount installation stopped is there any fix or am I screwed for viper4android (cant install normally as the driver just never installs)

Same error in my Xiaomi mi a1

Delta wolf said:
so I'm running a Huawei nova plus and magisk works fine but modules don't install no matter in twrp or magisk app I get halted at /data/magisk_merge.img failed to mount installation stopped is there any fix or am I screwed for viper4android (cant install normally as the driver just never installs)
Click to expand...
Click to collapse
Same problem on some moto devices. It's due to f2fs format. You would need custom kernel that supports a different file format for data (like ext4). So if kernel sources for your device are available, you need to compile it with different data format options.

Problem installing modules (magisk.img failed to mount)

I've tried installing multiple modules by both directly using the magisk manager and flashing them in recovery and both don't work, I'm using magisk 15.1, on Android 6, mtk6735 device. The problem I face is that in magisk manager when I try to install a module it says "magisk is not activated" and during the installation during recovery mode it says "magisk.img failed to mount", any help would be gladly appreciated

simply the most awesome said:
I've tried installing multiple modules by both directly using the magisk manager and flashing them in recovery and both don't work, I'm using magisk 15.1, on Android 6, mtk6735 device. The problem I face is that in magisk manager when I try to install a module it says "magisk is not activated" and during the installation during recovery mode it says "magisk.img failed to mount", any help would be gladly appreciated
Click to expand...
Click to collapse
Probably f2fs loopback issue. You need a custom kernel, or at least a patched boot.img. there is a module that claims to fix this issue. Search magisk section for f2fs loopback work around.
Here's a link f2fs loopback issue workaround
This may not be your issue because usually ppl with this issue still have magisk working for root. Just get the "failed to mount" issue installing modules.

madbat99 said:
Probably f2fs loopback issue. You need a custom kernel, or at least a patched boot.img. there is a module that claims to fix this issue. Search magisk section for f2fs loopback work around.
Here's a link f2fs loopback issue workaround
This may not be your issue because usually ppl with this issue still have magisk working for root. Just get the "failed to mount" issue installing modules.
Click to expand...
Click to collapse
Tried that module, installing it gives the exact same issue, error:1, magisk.img failed to mount, any help would be appreciated

exact same here, Workaround spit out same issue, any help?

Works well on my Moto
But even when every thing is flashed property there is no module shown in module list of magisk tried Mount magisk :crying:and f2fs both but only worked after formatting my data f2fs again:angel:
Like repair via TWRP and starting with fresh ROM PARTITION

same problem here , im on stock rom with stock recovery i installed latest magisk and then i flashed xposed frmaework through it ,it installed and working now even , but i dont know why every time i want to install a module from repo or file manager it says magisk not activated or magisk not mounting , for example i wanted to instal camera 2 api enabler but no success , any solution? what is the problem?

It's really annoying this issue is never fixed no matter how much we request help from the devs. I'm thinking of switching to another Su app at this point, happens across all my devices.

same issue here.I do not have a recovery, used it once for boot, maybe that is the problem? but it used to work fine,

F2FS patch for Mediatek?

Every time I try to install a Magisk module, I get the error "magisk.img mount failed"
I've looked online and found a F2FS patch zip that didn't work, but someone has made a kernel for Qualcomm versions of this device
Is there any patches for the Mediatek version?

Huades said:
Every time I try to install a Magisk module, I get the error "magisk.img mount failed"
I've looked online and found a F2FS patch zip that didn't work, but someone has made a kernel for Qualcomm versions of this device
Is there any patches for the Mediatek version?
Click to expand...
Click to collapse
Go to twrp and format data and type yes
That will fix magisk

If you are facing "! /data/adb/magisk_merge.img mount failed" move to thread https://forum.xda-developers.com/app...uding-t3577875. Flash last zip. Move to magisk manager, install updated (2018.3.6) version. All modules should now install fine.

Strange Magisk installation behaviour

Hi guys.
I'm facing an issue with Magisk (stable and beta) that I never had before. I'm on OP5, PixelExperience, Android Pie (but I've tried also on a Oreo ROM yesterday, not sure if it was stable or beta version of Magisk). Here's the flash routine I do for every single ROM:
- Wipe everything, internal storage included
- Flash ROM
- Flash Magisk
- Boot
In the past few days, Magisk isn't installing MM, don't know why. It always installed MM on every single flash I did in my life, now suddenly it isn't installing it anymore. I haven't changed my flashing "habits", I do the exact steps I wrote above on every single flash (not on updates, of course).
This issue also leads to not being able to install modules from MM, but I can install them via TWRP (I've got the latest blu_spark, I'm decrypted, flashed no_verity_v2 for OP5). When I install modules via MM it says:
! /data/adb/magisk_merge.img mount failed.
I tried re-installing Magisk, using the uninstaller and then first time the stable, then the beta, but they won't installing MM after flashing.
What do you guys think?
Thanks.
EDIT: I've recreated the issue, I've attached the log. I tried 2 different modules, Sysconfig Patcher and Busybox. The first one is installing only via TWRP (via MM it produces the log in the attachments), the second one is istalling via MM correctly.

"update-binary: line 203: make_ext4fs: not found"
Unable to format the .IMG to ext4 it seems so there's no magisk merge image to be mounted
Not entirely sure where to go with that but it could be a start.
Bad version of twrp?

If I understand you correctly, the Busybox module install just fine, no matter if installed through the Manager or TWRP.
Have you tried other modules?
The Sysconfig Patcher module isn't using the official module template, so it's very likely that @VR25 need to fix something in his install script.

Didgeridoohan said:
If I understand you correctly, the Busybox module install just fine, no matter if installed through the Manager or TWRP.
Have you tried other modules?
The Sysconfig Patcher module isn't using the official module template, so it's very likely that @VR25 need to fix something in his install script.
Click to expand...
Click to collapse
Indeed, there's stuff to "fix". I've been working on that for a few days now. I noticed [some] recent ROMs lack a bunch of useful binaries, such as make_ext4fs and resize2fs. So, I'm migrating to Magisk Module Template and relying on Magisk's util_functions.sh for better "future-proof" compatibility.

Didgeridoohan said:
If I understand you correctly, the Busybox module install just fine, no matter if installed through the Manager or TWRP.
Have you tried other modules?
The Sysconfig Patcher module isn't using the official module template, so it's very likely that @VR25 need to fix something in his install script.
Click to expand...
Click to collapse
I tried YTVanced module, downloaded via MM and it installed just fine. So I think that, as VR25 said, the ROMs I've tried these days might have lacked of those utilities. So we might have "solved" this issue.
And what about the fact that flashing Magisk from TWRP doesn't install MM? Is it also related to the fact that those ROMs are recent?

Pipodi93 said:
And what about the fact that flashing Magisk from TWRP doesn't install MM? Is it also related to the fact that those ROMs are recent?
Click to expand...
Click to collapse
That happens once in a while, and may very well be ROM related. Fortunately, it's easy to install manually...

Didgeridoohan said:
That happens once in a while, and may very well be ROM related. Fortunately, it's easy to install manually...
Click to expand...
Click to collapse
Yeah, I thought so too. Because when I was on AICP, MM was installed after flashing. My concern was that "mount failed" was related to the fact that MM wasn't installed during the flashing operation, but I'm glad to see that's not the case and my phone isn't cursed. Thank you!

Cannot mount magisk on Moto G5s Plus(Sanders)

Hi!
I tried installing Magisk v20.4 beta on my Moto G5s Plus (Sanders) running PixelExperience ROM (2020/04/12) with TWRP with treble support but I get the following message
- Mounting /system, /vendor
! Cannot mount /vendor
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v20.4.zip'
Can anybody please help.

As you've surmised, that usually indicates that you're not using a TWRP that is Treble compatible.
And even if you do have a Treble compatible TWRP, it is much more likely that the issue lies with the recovery rather than Magisk. You can hopefully get help with that in the corresponding TWRP thread, if there is one.
A way around it would be to patch the boot image with the Manager and then install that patched image though TWRP, instead of using the zip. Installation instructions here:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching