Magisk 19.3 - Core Only Mode Enabled ALWAYS

[carlos6034]

Hi there, so to be as brief as possible.

I just installed a ROM on my J7 Pro to upgrade from android 8.1 to 9.0 (if it helps at all the variant is J730G/DS).

When installing magisk I noticed my modules were not enabled, and then I saw that Core Only Mode was enabled. Tried disabling it and rebooting no luck, still comes on after booting up.

Tried different methods like using older version of the magisk apk and not using version 19.x.
Even tried completely uninstalling and installing again but no luck at all.

There are no anomalies on logs so I won't post them for now, but if requested I will try to do it.

PD: Yes, I've read previous threads on this issue but I think the problem is not API or Android version, so please just don't close it.

[AaronKeener]

I suggest you to flash the "Magisk manager in recovery mode" module into twrp, and then disable core only mode Into TWRP"

[carlos6034]

I do always flash magisk through TWRP, currently running 19.4 Canary. What I do not know is how to disable core only mode in TWRP.

Mind a quick explanation?

[AaronKeener]

I'm not talking about magisk, I'm talking about a module named :"Magisk Manager in recovery mode" that you can flash through TWRP and use to disable core only mode through TWRP's terminal

[carlos6034]

Now I get it, I'll try that right now

[carlos6034]

UPDATE: Disabling through TWRP didn't work

[AaronKeener]

Well...I don't have any other idea to fix your problem :/

But, I advise you to keep this module in your storage, disabling module through TWRP can be really useful if some of your modules lead to bootloops

[carlos6034]

Thanks for the help though Aaron, I will keep that in mind.

I would suggest the mods to keep this thread opened until this is solved. We don't know who else might be experiencing this issue.

[topjohnwu]

You want to keep this open, but yet does not provide any info regarding the issue....

[carlos6034]

Well after being closed, I can just say it was a ROM problem

[Untzo]

I have the same problem on my lg g5

[rCan9]

same problem here. dont know how to fix