Database Develop

edxposed bootloop. TWRP=ERROR 1 // is there a module.list file like in orig xposed?

im using a samsung galaxy s9 with pie installed and could install edxposed.zp only via magisk manager. in twrp i get the error 1 wich states that magisk is not installed, which isnt true. anyways i installed an incompatible app which coused a bootloop and now i cant install the uninstaller
my question is, is there a module.list like discribed in the following link so i can just prevent the module is beeing loaded manualy?
https://forum.xda-developers.com/xposed/howto-disable-xposed-modules-via-t3227175
edit:
i worked around thios problem via uninstalling magisk via zip file:
https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242

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

How do I upgrade from Magisk 20.4 to 22.0?

Device: Samsung Galaxy On7
Android: 6.0.1
I have Magisk Manager 8.0.7 and Magisk 20.4 installed on my device. I went to the GitHub repo and found that the app and the zip have been combined in Magisk 22.0. Fine. But how do I upgrade to v22.0? When I open the app, it asks me to upgrade the app first. Okay, I do that. When I open the upgraded app, it can no longer find Magisk. I click on "Install" beside Magisk, choose Direct Install, and then it gives me an error: Device signature invalid.
Any help is appreciated.

Wrichik Basu said:
Device: Samsung Galaxy On7
Android: 6.0.1
I have Magisk Manager 8.0.7 and Magisk 20.4 installed on my device. I went to the GitHub repo and found that the app and the zip have been combined in Magisk 22.0. Fine. But how do I upgrade to v22.0? When I open the app, it asks me to upgrade the app first. Okay, I do that. When I open the upgraded app, it can no longer find Magisk. I click on "Install" beside Magisk, choose Direct Install, and then it gives me an error: Device signature invalid.
Any help is appreciated.
Click to expand...
Click to collapse
if you have a custom recovery, change the magisk.apk file to.zip so it would be magisk.xx.zip then just flash it via twrp or whatever you have

xHvlios said:
if you have a custom recovery, change the magisk.apk file to.zip so it would be magisk.xx.zip then just flash it via twrp or whatever you have
Click to expand...
Click to collapse
Okay. Do I leave the old Manager as it is, or should I uninstall it before I flash the zip from TWRP?

Wrichik Basu said:
Okay. Do I leave the old Manager as it is, or should I uninstall it before I flash the zip from TWRP?
Click to expand...
Click to collapse
I think it will update it, so just flash the new one

Unable to open Magisk App

I've flashed recently CSC file and lost the root. I updated MAgisk app up to 25.1 version (not a zip file just apk) but still no root. I have flashed Magisk 25.1.zip file in TWRP recovery. Now the phone is rooted, but I unable to start Magisk app. It just stuck on the start (The Mask). I tried to uninstall Magisk app via Application manager, and reinstall it following by reboot. Still Magisk unable to start. I don't remember whether MAgisk was unhidden before the update and zip installation. What should I do next?
Should I rename the Magisk.apk to uninstall.zip and run this file in TWRP. Then install Magisk apk and install zip file from within Magisk App? If so, what the best way to install MAgisk App; via TWRP or File Manager?
Samsung Galaxy S5
Marshmallow 6.0.1

Magisk root not detected by Magisk Manager 25.2 (25200)(33) after uninstallation of hidden (renamed) Magisk Manager (by mistake)

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.