Question What is this magisk module and why can't delete it ?
- Thread starter Plathoon
- Start date
That's weird....
If you are bothered and you don't mind re-installing/re-flashing all your modules again, you could try the adb command
and that should remove all your modules including that unknown weird one.
Also, if for whatever reason that doesn't work, I read somewhere that Magisk has its data folder outside of the internal storage folder and is more in the root data folder -- so if one wiped their phone, all the Magisk data (deny list i imagine, on top of modules) would still survive -- and you might consider finding and deleting that folder and reinstall/re-flash Magisk. CAUTION: I imagine this has a chance of bringing up some glitches or bugs (incompatibilities) when the app connects-to/works-in-conjuction-with the patched init_boot.
If you are still sure you wish to do that, I believe I found the folder which I put in spoilers below...
These are just a couple of ideas...hope it helps...
If you are bothered and you don't mind re-installing/re-flashing all your modules again, you could try the adb command
Code:
adb wait-for-device shell magisk --remove-modulesAlso, if for whatever reason that doesn't work, I read somewhere that Magisk has its data folder outside of the internal storage folder and is more in the root data folder -- so if one wiped their phone, all the Magisk data (deny list i imagine, on top of modules) would still survive -- and you might consider finding and deleting that folder and reinstall/re-flash Magisk. CAUTION: I imagine this has a chance of bringing up some glitches or bugs (incompatibilities) when the app connects-to/works-in-conjuction-with the patched init_boot.
If you are still sure you wish to do that, I believe I found the folder which I put in spoilers below...
root: /data/adb
These are just a couple of ideas...hope it helps...
I also have the same problem.... ".core" and i cannot delete it...its like a bug or something like that?
Hello, I have the same problem where I have to apply those lines, in the bootloader, recovery? I tried both and neither worked. Thank you in advance
sorry for the very late reply...been a busy couple of weeks and am only catching up on things now...I'm fairly positive you figured it out already, but in case you haven't and/or any other person reading this looking for the answer...
I've never used the line before, but as I understand it, after turning off your phone and before connecting your phone to the computer, open up the cmd and run the command when you've changed the directory to the platform-tools folder. I believe the "wait-for-device" part has it running but on standby to activate once you plug your phone to the computer and it powers on (and tries to load up)...
I imagine once it does, it'll run the command and is executed before it goes any further loading up the module that is causing the issue/bootloop...
Hopefully I am correct and this helps...
in fact I had already applied that line and it didn't work either in fastboot or in ell recovery. It worked for me, to my surprise, with the phone on. all modules were deleted
Top Liked Posts
-
There are no posts matching your filters.
-
1
in fact I had already applied that line and it didn't work either in fastboot or in ell recovery. It worked for me, to my surprise, with the phone on. all modules were deleted
New posts
-
-
[All XDA Members] Requests to Moderators and Admins- Latest: Neelthegamer007
-
[ROM] [UNOFFICIAL] [12.1] LineageOS 19.1
- Latest: methythebozo
