Database Develop

Problem with magiskmanager

I had rooted with superSU than switched to magisk root which is now updated to Magisk v15.2(Magisk Manager 5.5.3) and I have some problems
Every Modules I intall gives Installation error(magisk_merge.img merge failed)
tried flashing modules via recovery but not showing into magisk manager
safetynet check failed what to do?
can i install viper4android or ARISE sound system(cant install from magisk modules)
If anybody can help would be great

Odds are good you didn't remove su properly

flash the unSU zip file to uninstall superSU

doesnt work

Magisk 15.3 make me confused

I remember when I'm using Magisk 14.0 on Nougat 7.1.2 and Oreo 8.0 when i install module and then when i check module on Magisk Manager the module was installed
But when i install Magisk 15.3 on Oreo 8.1 when i install the module and then check on Magisk Manager the module doesn't installed properly even in twrp say instalation complete i try to install module via Magisk Manager first it was installed but when i reboot to recovery to install Magisk module which can be installed via recovery and then opening again module menu the module doesn't installed properly again instead it makes me more confused how to install module on Magisk 15.3

I forgot this

ZidanBlaster said:
I forgot this
Click to expand...
Click to collapse
Instead of all those screenshots it would have been more useful if you had provided the installation log, recovery log and Magisk log...
One thing to try is a complete uninstall and reinstall of Magisk.

Didgeridoohan said:
Instead of all those screenshots it would have been more useful if you had provided the installation log, recovery log and Magisk log...
One thing to try is a complete uninstall and reinstall of Magisk.
Click to expand...
Click to collapse
Ok when i trying to unistall and reinstall Magisk some of module can be installed but some of module doesn't installed properly when i check it the problem was being caused by this
I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop1' - change
Here's the recovery log

ZidanBlaster said:
Ok when i trying to unistall and reinstall Magisk some of module can be installed but some of module doesn't installed properly when i check it the problem was being caused by this
I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop1' - change
Here's the recovery log
Click to expand...
Click to collapse
And what about the Magisk log? Even better would be if you could install the v15.3 beta (only difference is more verbose logging) and provide the magisk_debug.log from /data/adb.

Didgeridoohan said:
And what about the Magisk log? Even better would be if you could install the v15.3 beta (only difference is more verbose logging) and provide the magisk_debug.log from /data/adb.
Click to expand...
Click to collapse
Ok i try later

Is it posible to uninstall Magisk temporarily?

Hi,
Sometimes I have some problems with my devices and want to disable Magisk just to be sure it's not the cause of the problems. My question is - if I uninstall it from Magisk Manager, and then after some time reinstall again will all modules with their configurations remain untouched? If not then is there any way to backup them somehow? Thanks in advance.

As long as you restore the stock boot image and keep the Magisk image intact, you'll have temporarily disabled Magisk and all your modules will still be installed and intact. Just flash the Magisk zip again to enable.
Easiest way to do this should be to use the "Restore Images" option when pressing "Uninstall" in the Manager.

Thank you. will do this that way. When installing again can't I just use "Install" from Magisk Manager?

You can patch your boot image and then flash the patched image manually. You can not install Magisk directly, since that requires superuser access...

Thanks, works like a charm.

Re: Temporarily Disable Magisk & Complete Removal?
Didgeridoohan said:
As long as you restore the stock boot image and keep the Magisk image intact, you'll have temporarily disabled Magisk and all your modules will still be installed and intact. Just flash the Magisk zip again to enable.
Easiest way to do this should be to use the "Restore Images" option when pressing "Uninstall" in the Manager.
Click to expand...
Click to collapse
Thanks! :good:
"...Easiest way to do this should be to use the "Restore Images" option when pressing "Uninstall" in the Manager." - That's what I did on Galaxy S5 SM-G900M (klteub) running Official 16.0 build 2019-03-04 klte + Open GApps ARM 9.0 Pico + Magisk v18.1 to temporarily disable Magisk so I could test an unofficial addonsu alternative.
Note that a manual reboot is required to disable Magisk after using "Restore Images" as the reboot is not automatic like when using Completely uninstall.
I have 2 questions:
I see that the 99-magisk.sh survival script is still in /system/addon.d/ so if I update the firmware would it restore Magisk & re-enable it?
I'm happy with the addonsu so would running the Latest Uninstaller from the Magisk thread completely delete 100% of the files installed by Magisk & the mods it made to the original setup & in /Data?
***

Hi, when i select the restore image option it says "stock backup does not exist" but i have it in root/data...

The root permission request is no longer displayed

I have the root with Magisk in Android 8.0. At first, the warning always came out asking if you wanted to grant root rights to the application that you just opened. However, this warning is no longer displayed, even though the configuration of Magisk Manager is configured in this way.
In the Magus Superuser section, I do not see any trace of the applications that I can not 'root'.
I have updated Magisk Manager, but the error continues. I also removed BusyBox, but the error continues.
I can not give root permission to any other application. But the mobile is rooted, since the first applications that I installed that require root continue to function normally. I can even deactivate the root and then activate it again.
Reinstalling the applications is not solved. With Dalvik and Caché wipe either.
That could be happening? How is it solved?
____
Magisk Manager has all the permissions of everything (memory, background, manual battery mode). I have tried to reinstall Magisk Manager and nothing.
Deactivating BusyBox (Magisk module) and Xposed and restarting still does not work.
Returning to install the Magisk image by TWRP or Fastboot is not fixed either.
I have removed all the fret that I had done to the phone (BusyBox, Xposed, root Magisk and boot modified for the root) and the problem has not been solved. I do not know what may be happening. I do not have other rare applications.
I have installed Device Control and the TWRP application. I have not gotten the root request to skip (although it has activated that option in Magisk Manager).
Definitely, it is not the fault of the new applications, which was the first question I wanted to solve.
Magisk version:
19.3 (19300)
And from Manager 7.2.0 (213), although I have also tried 7.3.2 (224).
The root is done with patching (via Magisk) of RAMDISK.IMG.
I understand that some applications are not compatible with systemless. But I'm not going any of the new ones that I'm trying. Interestingly, other applications compatible with Magisk (except those that installed the first days of the mobile) do not work either.
I have installed Magisk Manager 7.0.0 (and also 6.1.0), but the bug is still there. It seems that it does not depend on the APK.
As my Magisk file to root consists of a patch of RAMDISK.IMG created directly from Magisk Manager I do not know how to create one based on a lower version (for example, version 18.1). It only gives me the option to patch with the latest Magisk Manager version (if I have a lower one, it asks me to update the APK).
Whenever I generate the IMG of my patched RAMDISK.img it is based on 19.3.
How could I generate a patched IMG based on a lower version?
I have microG, not the GApps. Could that influence? Does Magisk need them?

@rovo89

@topjohnwu

https://www.didgeridoohan.com/magisk/MagiskHelp

I have added much more information.

Reinstall firmware???

LoneWolfz said:
Reinstall firmware???
Click to expand...
Click to collapse
I'm going to do it today. Will I lose data if I install SYSTEM.img via Fastboot?

535iu said:
I'm going to do it today. Will I lose data if I install SYSTEM.img via Fastboot?
Click to expand...
Click to collapse
No maybe but i suggest you to backup all your data etc. just to be safe

25.2 upgrade error (mine)

In 25.1, I'd enabled zygisk and used magiskhide then frozen the renamed magisk app using SDmaid in order to use banking app.
I upgraded to 25.2 via twrp but couldn't see the magisk app as it was frozen. At this point SD maid had lost root so I couldn't unfreeze the old app.
I installed the latest APK but it doesn't think magisk is installed and the only option given is to patch boot IMG which seems pointless as magisk 25.2 already flashed using recovery successfully (result 1.000).
Any ideas most welcome. Would prefer not to wipe data as a few of my apps need special manual verification by their support team each time they're installed which is cumbersome.