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.
Motorola G5 Plus
Lineage 15.1
TWRP 3.2.1
I want to go back to my stock boot image but I appear to be stuck with the Magisk 16.4 boot image.
I first ran this (I didn't know there was an updated uninstaller): Magisk-uninstaller-20170813.zip
Unfortunately I don't have the exact output because when I run this again (after running the updated one below) I have a different output now, but here's the basics of what I do remember:
- Mounting /system, /vendor
- Device platform: arm64
.
.
.
I remember it saying that the stock boot image was found, but then immediately after it said Magisk wasn't installed and then aborted.
(Magisk is definitely installed as when I rebooted the phone after that, the Magisk app said 16.4 was installed, plus I still had root).
Then I ran this: Magisk-uninstaller-20180429.zip and got:
- Mounting /system, /vendor
- Device platform: arm64
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Download/Magisk-uninstaller-20180429.zip'
Updating partition details...
...done
So I'm currently stuck at this point and I don't know what to do. If wiping everything and reinstalling Lineage 15.1 will fix this, then that's what I'll do but I'm looking for any suggestions to get my stock boot image back in place.
Try the next to last uninstaller:
https://github.com/topjohnwu/Magisk/releases/download/v16.3/Magisk-uninstaller-20180328.zip
The latest one has issues on 64-bit systems...
Didgeridoohan said:
Try the next to last uninstaller:
https://github.com/topjohnwu/Magisk/releases/download/v16.3/Magisk-uninstaller-20180328.zip
The latest one has issues on 64-bit systems...
Click to expand...
Click to collapse
That did it. Thanks!
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!
Hi
Since PIE roms for santoni are available, some people, including me, can't root their santoni.
I don't know why.
Flash looks ok in recovery, but after reboot, Magisk Manager says that Magisk isn't installed.
I tried every solution found in forums here, but everytime, same result : "magisk isn't installed"...
So sad !
Could you guys (and girls) centralize here your solutions, step by step, from flash the rom to root it...
It would be so nice for helping desperate people...
I also tried SuperSU and am having the same problem. I've tried Magisk 17.1, 17.2 and the Canary build along with the newest SuperSU and the result is always the same. Flashes fine but Magisk Manager and SuperSU apps can't find root.
The weird thing is that Enpass always tells me that my device is rooted and that it's a security risk even though Magisk Manager can't find root.
Also, I'm positive Magisk is patching the ramdisk. The Uninstaller always finds a Magisk-patched image. I'm assuming something has to be happening during boot that's cancelling root.
Two things I don't understand :
- why some people, with same configuration, don't have root problem ?
- why, with same recovery, same flash method, root works with nougat/oreo rom, and doesn't work with pie...?
Just like that : do you think problem could come from the sd card ?
I'm using à 128 gb samsung sd-card. Maybe I should format it before trying again root ?
I'm not sure it's the problem, since I can flash all roms, but I could try...
Or flash Magisk from internal storage ?
Really desperate...
Hi,
I´m in the same situation like you.
Yesterday I made a new experience of that without solution:
- Backuped all
- Uninstalled magisk at twrp
- Installed santoni_twrp_silent 27_treble (recommended from dev to install havoc)
- Rebooted
- Formated data with factory reset
- Wiped vendor, cache, data... (everything)
- Installed havoc (version 2018-09-08)
- Rebooted
- Installed magisk at twrp
- Rebooted
Same issue like before...
If I try to install magisk on magisk manager I get the following log:
Copying image to cache
Device platform: arm64-v8a
Existing zip found
Extracting files
boot_patch.sh[73]: can't create /proc/self/fd/: Is a directory
MagiskBoot v17.1(17100) (by topjohnwu)
Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory!
Installation failed
It seems magisk can´t install correct in cause of failing permissions to create new directories. But why?
Edit:
I think there´s an old magisk information written in device system who has to removed manually, cause magisk uninstaller is not able to do
Edit:
I think there´s an old magisk information written in device system who has to removed manually, cause magisk uninstaller is not able to do
Click to expand...
Click to collapse
Ok, but I wiped AND format data of internal storage, same results.
Do you think I should format/wipe micro-sd too ?
newbie_or_not_newbie said:
Ok, but I wiped AND format data of internal storage, same results.
Do you think I should format/wipe micro-sd too ?
Click to expand...
Click to collapse
I don´t think so. Well, if you like you can try, but I think it´s an internal problem, not an external
So,
I tried another wipe of internal storage, made a format data with recovery. Then I flashed another pie rom, then magisk. And after reboot : tada !! still not working...
try with version 16.6 of magisk
Great news, actually my magisk works on Pixys 2.1!
I installed this twrp:
https://drive.google.com/file/d/1RR-8WMNSQgx6QzQv5U4i-sST1Af42nrI/view
What I did:
Uninstalled old magisk, rebooted to twrp, installed magisk 17.2, rebooted, installed magisk manager 6.0 and it works.
The only thing is I didn´t rebooted until now, maybe it still works after next reboot or not...
Lemmy554 said:
Great news, actually my magisk works on Pixys 2.1!
I installed this twrp:
https://drive.google.com/file/d/1RR-8WMNSQgx6QzQv5U4i-sST1Af42nrI/view
What I did:
Uninstalled old magisk, rebooted to twrp, installed magisk 17.2, rebooted, installed magisk manager 6.0 and it works.
The only thing is I didn´t rebooted until now, maybe it still works after next reboot or not...
Click to expand...
Click to collapse
I just tried this and it didn't work for me either. I tried multiple clean flashes, flashed MIUI then back to Pie and flashing things in different orders last night and nothing worked. I'm tired of messing with it. I don't know how to get logs without root. I've come to the conclusion that for now I either have Pie or root. Not both. lol
Me too. I stop trying every day a solution.
For the moment, no root for pie roms, so I keep staying with oreo roms (nice dot OS...) I can root.
Hope next builds of pie roms will accept to be rooted on our santoni...
You can try this:
1 Flash Magisk v 17.2, Reinica in fast boot mode, turn it off and turn the phone on again
2 Install Magiskmanager V6 APK, do not open and restart in recovery
3 Flash Magisk v 16.6 and ready...
It worked for me... important, do not update magisk... The root is lost again
Best regards
Thanks for your reply.
Did you have root trouble before trying your solution ?
yes, when installing Pie only. In oreo no, I tried it in havoc and pixys
Try OrangeFox recovery for flashing magisk.
hyperkin said:
Try OrangeFox recovery for flashing magisk.
Click to expand...
Click to collapse
That's what I've been using. Also tried TWRP. Neither worked for me. The flash always looks good with no errors but when I boot the ROM Magisk says it's not installed.
I just realize to make magisk work on pie roms i realize that i need dev miui firmware not stable miui firmware the file you need is named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1.zip i not sure why stable firmware wont work on magisk.
i used OrangeFox Recovery Project R8.1 for recovery
1. install rom PixysOS 2.1 as normal (clean flash). Note: LineageOS 16.0 also works I have tested it
2. boot up os to make sure it that everything is working
3. then reboot back to recovery
4. flash firmware zip file named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1
5. reboot to system making sure that it still boots in os
6. reboot back to recovery
7. flash magisk 17.2 beta i think magisk 17.1 also works
8. reboot up back to system
9. installl magisk manager apk
10. done
i just uplolad screenshot just to prove it
neijzen said:
I just realize to make magisk work on pie roms i realize that i need dev miui firmware not stable miui firmware the file you need is named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1.zip i not sure why stable firmware wont work on magisk.
i used OrangeFox Recovery Project R8.1 for recovery
1. install rom PixysOS 2.1 as normal (clean flash). Note: LineageOS 16.0 also works I have tested it
2. boot up os to make sure it that everything is working
3. then reboot back to recovery
4. flash firmware zip file named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1
5. reboot to system making sure that it still boots in os
6. reboot back to recovery
7. flash magisk 17.2 beta i think magisk 17.1 also works
8. reboot up back to system
9. installl magisk manager apk
10. done
i just uplolad screenshot just to prove it
Click to expand...
Click to collapse
Sounds like a plan! I'll try it out when I get home from work and let you know how it goes!
Trying asap.
Thanks
neijzen said:
I just realize to make magisk work on pie roms i realize that i need dev miui firmware not stable miui firmware the file you need is named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1.zip i not sure why stable firmware wont work on magisk.
i used OrangeFox Recovery Project R8.1 for recovery
1. install rom PixysOS 2.1 as normal (clean flash). Note: LineageOS 16.0 also works I have tested it
2. boot up os to make sure it that everything is working
3. then reboot back to recovery
4. flash firmware zip file named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1
5. reboot to system making sure that it still boots in os
6. reboot back to recovery
7. flash magisk 17.2 beta i think magisk 17.1 also works
8. reboot up back to system
9. installl magisk manager apk
10. done
i just uplolad screenshot just to prove it
Click to expand...
Click to collapse
This post right here works, thank you so much
Hello,
I stuck in quite specific situation. I am using OnePlus 7T Pro (HD1913) with installed the most recent stock Oxygen OS 12.1 MP2 - 11.F.17. EU (Android 12) and Magisk 25.2 (25200)(33) stable release.
What I did I used Magisk hide option and renamed package to random one. After this operation succeeded by mistake I uninstalled Magisk Manager from my device, and that was big mistake. Since I installed Magisk Manager from apk file once again it doesn't detect Magisk root installation anymore. In result installed apps for which there were granted root privileges when Magisk Manager properly detected Magisk Root installation (before hiding operation) still have root privilleges (e.g. Tasker, Total Commander in my configuration). Of course for new apps Magisk Manager behaves like there would be no root so it doesn't ask for granting root privilleges.
What can I do now to make Magisk Manager aware that Magisk root is installed in my system? Is there any way to achieve that (below there is some explanation why it is a bit tricky to root Oxygen OS 12.1 MP2)?
Below there are steps which I already done and some explanation why I cannot simply re-root my device with Magisk package with e.g. TWRP etc.
1. Currently there is no working TWRP compatible with Oxygen OS 12.1 MP2. Whenever I try to perform 'fastboot boot twrp.img' (and many other users confirm that in this forum) bootloader stuck and TWRP is not being loaded. I didn't found any resolution for that. This is the reason why I cannot simply reroot my device with Magisk package again.
2. I tried to extract 'boot.img' from Oxygen OS 12.1 MP2 firmware and used Magisk Manager to patch it. Unfortunately it didn't resolve the issue becasue after command 'fastboot boot patched_magisk_boot.img' Magisk Manager still doesn't detect Magisk root.
3. Before the whole described here issue occurred in order to root my device I had to use Magisk Manager with the last version of Oxygen OS working on Android 11 (rooted with Magisk) and performed patching to inactive slot directly from Magisk Manager just after installation (before reboot) of Oxygen OS 12.1 MP2. This is the only way which worked for me. This is the reason why I cannot simply perform this process again now because I would have to erase all my data / configuration and revert to the previous Oxygen OS.
Thanks
A new APP desktop shortcut will be generated after random naming. Please look for it on your mobile phone
Hi phidix, have you solved the problem? I got into exactly the same trap and still looking for a way out...
It looks like I found the solution.
First, I ensured that I had the latest stock ROM installed without any modifications. For that, I downloaded the official ROM and flashed it manually using the old system updater with the local upgrade option. Just to be on the safe side, I had repeated that twice, so both A and B slots eventually contained the same stock ROM.
Then I installed Cygisk, the same steps as for Magisk (I extracted boot.img from the firmware, patched it with Cygisk and flashed with fastboot).
Voilà, my phone reverted to being rooted.