Hi everyone, just got a Moto G5 flashed AEX and Magisk. Now, when trying to install Viper4Android through the repo I get "/data/magisk merge.img mount failed". If I try to flash the ZIP for V4A manually through TWRP it comes back with "Error 1". What gives?
Oops maybe should have posted in general discussion thread
So it's not just me then? The merge error went away with one of the newer updates on my G5 Plus, but even though the script says SUCCESS the modules never install.....running Stoneware .67 and ElementalX 2.01 with Magisk 14.
I got the same problem trying to install module for greenify, audio mod, gms mode
But some work too
Nexus 6p, nougat
Same problem with my Doogee S60
Aneuryst said:
Hi everyone, just got a Moto G5 flashed AEX and Magisk. Now, when trying to install Viper4Android through the repo I get "/data/magisk merge.img mount failed". If I try to flash the ZIP for V4A manually through TWRP it comes back with "Error 1". What gives?
Click to expand...
Click to collapse
It's on most moto phones. F2fs loopback issue. You either need a kernel (or at least a boot.img) patched to fix loopback issue on f2fs, or there is a flashable zip that may fix it. The zip moves the magisk.img to /cache and links it to the original location. It does more but it's alot to write. I'll grab you a link.
Found it f2fs loopback bug work around
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.
after reformatting my device and flashing stock rom through twrp, i went and download the zip file with magisk manager latest version and then i fully unroot my device with full unroot of supersu. after i rebooted to twrp, i installed magisk v14 zip and this is what it tells me after i flashed it.
Installing '/sdcard/Magisk-v14.0.zip...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
! Unable to detect boot image
- Unmounting partitions
E: Error executing updater binary in zip ' /sdcard/Magisk-v14.0.zip'
Error flashing zip ' /sdcard/Magisk-v14.0.zip'
Updating partition details...
...done
i have few questions.
1. unable to detect boot image. what do you mean by that? where can i get this boot image?
2. what's that updater binary in the zip file?
what can i do to be able to use magisk? thank you in advance
my device is oppo neo 7 android 5.1
The boot image is a part of your device's software. It's what Magisk modifies to do it's thing. If the installer can't recognise it, there's not much you can do... Except providing logs, that is.
The update binary is a part of the installer. It's the script that modifies the boot image to install Magisk on your device.
When you have these kind of errors, save the recovery log after flashing the zip (Advanced -> Copy Log) and post that (attach it or use Pastebin or similar, don't copy it directly to the post). It's so much easier to troubleshoot with proper logs.
First thing you can try is to use the latest beta and see if that works.
Didgeridoohan said:
The boot image is a part of your device's software. It's what Magisk modifies to do it's thing. If the installer can't recognise it, there's not much you can do... Except providing logs, that is.
The update binary is a part of the installer. It's the script that modifies the boot image to install Magisk on your device.
When you have these kind of errors, save the recovery log after flashing the zip (Advanced -> Copy Log) and post that (attach it or use Pastebin or similar, don't copy it directly to the post). It's so much easier to troubleshoot with proper logs.
First thing you can try is to use the latest beta and see if that works.
Click to expand...
Click to collapse
i got the log, how do i upload it here? im only using android browser.
so itried to install magisk v14 and it didnt detect bootimg but v14.5 did detect but still failed to install.
rajoholic said:
i got the log, how do i upload it here? im only using android browser.
so itried to install magisk v14 and it didnt detect bootimg but v14.5 did detect but still failed to install.
Click to expand...
Click to collapse
I guess you can't attach a file, being so new... You can upload it somewhere and provide the link or use Pastebin and provide the link/id for it.
Didgeridoohan said:
I guess you can't attach a file, being so new... You can upload it somewhere and provide the link or use Pastebin and provide the link/id for it.
Click to expand...
Click to collapse
https://dropmb.com/download/aca1616df3f0d913cb70d1f88176d9d4.html
here it is. thanks for the help
I m also facing same problem
rajoholic said:
after reformatting my device and flashing stock rom through twrp, i went and download the zip file with magisk manager latest version and then i fully unroot my device with full unroot of supersu. after i rebooted to twrp, i installed magisk v14 zip and this is what it tells me after i flashed it.
Installing '/sdcard/Magisk-v14.0.zip...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
! Unable to detect boot image
- Unmounting partitions
E: Error executing updater binary in zip ' /sdcard/Magisk-v14.0.zip'
Error flashing zip ' /sdcard/Magisk-v14.0.zip'
Updating partition details...
...done
i have few questions.
1. unable to detect boot image. what do you mean by that? where can i get this boot image?
2. what's that updater binary in the zip file?
what can i do to be able to use magisk? thank you in advance
my device is Micromax canvas nitro a310 current android version is cyanogen mode 13
Click to expand...
Click to collapse
rajoholic said:
https://dropmb.com/download/aca1616df3f0d913cb70d1f88176d9d4.html
here it is. thanks for the help
Click to expand...
Click to collapse
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Didgeridoohan said:
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Click to expand...
Click to collapse
sorry bout that. i just search the google free and temporary storage online. haha! thank you for the help. I'll try what u just said
Didgeridoohan said:
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Click to expand...
Click to collapse
how do i flash the patched boot.img with twrp? i cant find it in my sd card. it's not showing up. i already got the patched boot img
rajoholic said:
how do i flash the patched boot.img with twrp? i cant find it in my sd card. it's not showing up. i already got the patched boot img
Click to expand...
Click to collapse
Hm.... It might be that your TWRP is to old, but it should be the same procedure as when flashing a zip file except you switch to image flashing by pressing the "Image" button after going to the "Install" screen.
If that doesn't work, use fastboot (or whatever is available for your device).
Code:
fastboot flash boot patched_boot.img
Didgeridoohan said:
Hm.... It might be that your TWRP is to old, but it should be the same procedure as when flashing a zip file except you switch to image flashing by pressing the "Image" button after going to the "Install" screen.
If that doesn't work, use fastboot (or whatever is available for your device).
Code:
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
So I did what u told me and flashed the boot.img succesfully. Now after flashing that, I flashed v14 and still error in executing update binary. Same with 14.5. But this time after I saw that, I rebooted my device and found magisk manager on my phone. It says v14 installed. Is it installed already?
rajoholic said:
So I did what u told me and flashed the boot.img succesfully. Now after flashing that, I flashed v14 and still error in executing update binary. Same with 14.5. But this time after I saw that, I rebooted my device and found magisk manager on my phone. It says v14 installed. Is it installed already?
Click to expand...
Click to collapse
Yes, if you flash the patched boot image you don't have to do anything else. The Magisk Manager has already taken care of everything.
If you want v14.5 beta, you should now be able to change the update channel (in Manager settings) to beta and update. Just as a FYI, you could have done this already when patching the boot image.
Sounds like it's working now, or? Can you install modules?
Didgeridoohan said:
Yes, if you flash the patched boot image you don't have to do anything else. The Magisk Manager has already taken care of everything.
If you want v14.5 beta, you should now be able to change the update channel (in Manager settings) to beta and update. Just as a FYI, you could have done this already when patching the boot image.
Sounds like it's working now, or? Can you install modules?
Click to expand...
Click to collapse
I installed an app and gave it root permission. It looks like it's working. However the module part, I'm still unsure. When I try to add modules, the screen took me in storage. Looks like it requires me to import something? Where can I download modules?
rajoholic said:
I installed an app and gave it root permission. It looks like it's working. However the module part, I'm still unsure. When I try to add modules, the screen took me in storage. Looks like it requires me to import something? Where can I download modules?
Click to expand...
Click to collapse
First of all, don't even mention that piece of piracy software on xda. It's used to steal from developers and is not allowed here.
In the "Modules" part you can manually install modules that you've previously downloaded. If you want to install directly from the Magisk repo, you (unsurprisingly ) go to the "Downloads" section of the Manager. If you can't see "Downloads", make sure the Manager has internet access.
Didgeridoohan said:
First of all, don't even mention that piece of piracy software on xda. It's used to steal from developers and is not allowed here.
In the "Modules" part you can manually install modules that you've previously downloaded. If you want to install directly from the Magisk repo, you (unsurprisingly ) go to the "Downloads" section of the Manager. If you can't see "Downloads", make sure the Manager has internet access.
Click to expand...
Click to collapse
Sorry I didn't know. What I had in mind is that I'll give u all the details without leaving none so u know what I do and be able to help fast. Anyway, again I'm sorry. I didn't mean it.
I tried to dl greenify4magisk and I successfully download and install it. Rebooting the device now
rajoholic said:
Sorry I didn't know. What I had in mind is that I'll give u all the details without leaving none so u know what I do and be able to help fast. Anyway, again I'm sorry. I didn't mean it.
I tried to dl greenify4magisk and I successfully download and install it. Rebooting the device now
Click to expand...
Click to collapse
Sir, did you manage to install? when i tried to install log is failed.
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,
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