Magisk General Support / Discussion

[matth76]

Finally it works,
I installed again 21.2 from a .zip i had and the menu and all settings are back (i had nothing after the doanlod path option in the settings)
updated to 21.4 and it's ok

Thanks for help

 

[MoL_82]

Than you, i don't have this menu (?)View attachment 5194479

It says Magisk is not installed. You do not have all the options when it is not installed.
I am not a dev, but my guess is you should flash Magisk again in TWRP.

EDIT: Ah, you already solved it.

 

[regularmen]

hello, I have an odd issue in my Nokia 5 running Magisk 21.4 .

Everything is fine and working, I have added some module to suit my needs, no problem.
Then, some times later, every apps would cease to open at all. it would stuck at the apps splash screen and never goes beyond it. at this point I can't do anything, I can't open magisk manager or even the android settings. what's weird is that its still responding well, not like it hangs or lags or something. I can swipe down status bar and turn some stuff, I can still reboot the phone normally and this is the only thing I can do at that point. to fix this all I need is just to reboot, but it would happen again later. I wondered what's going on? also this has happened way back since magisk 18.0. and thanks for the help!

 

[nowster]

hello, I have an odd issue in my Nokia 5 running Magisk 21.4 .

Everything is fine and working, I have added some module to suit my needs, no problem.
Then, some times later, every apps would cease to open at all. ...

I think this is related to the f2fs problem. I've had this a few times with my Pixel 3a.

 

[CSX321]

I think this is related to the f2fs problem. I've had this a few times with my Pixel 3a.

Me, too, with my Pixel 3. I wonder is this something we can expect to be fixed in a future Android update, or are we going to have to fix it ourselves with a patched or custom kernel? I hate that my phone feels unstable now, after years of being rock solid with A10 and Magisk.
Edit...I just installed the ElementalX kernel. Seems stable so far with systemless hosts enabled. I used to use it with my old Nexus 5, but this is the first time I've used it with the Pixel 3.

 

[uvzen]

My device:
Name: Huawei P10
Model: VTR-L29
Build: 8.0.0.386(C432)

I have unlocked bootloader and root magisk in version 20.4. When I want to update magisk to higher version 21.x, then I lose root. I tried update in magisk manager app or flash update magisk in TWRP and neither of these methods work. What is wrong?

 

[nowster]

Edit...I just installed the ElementalX kernel. Seems stable so far with systemless hosts enabled. I used to use it with my old Nexus 5, but this is the first time I've used it with the Pixel 3.

I'm trying out the MVK kernel at the moment for the same reason.

 

[oollee]

Hey folks,
I am not able to root the Sony Xperia Z3 Compact (z3c) running LineageOS17.1.

## How I recognized the problem:
- The Card "Magisk" in MagiskManager is showing the following:
- A/B: No
- Installed: n/a <---------
- SAR: Yes
- Ramdisk: Yes
- Crypto: n/a
- MagiskManager has no bottom menu

## How I flashed Magisk (also tried flashing multiple times)
- Lineage Recovery 17.1-20210117 > Apply Update
- sideloading fails: "serving: 'Magisk-v21.1.zip' (~47%) adb: failed to read command: Success"
- TWRP 3.0.2 > ADB Sideload
- sideloading succeeds
- fastboot flash boot patched_boot.img
- fastboot fails: "fastboot: error: Couldn’t parse partition size ‘0x’"
- fastboot flash:raw boot patched_boot.img
- fastboot succeeds

Is there a way to flash Magisk with debugging output or even install Magisk by hand?

 

[iamrance.asa]

Hey folks,
I am not able to root the Sony Xperia Z3 Compact (z3c) running LineageOS17.1.

## How I recognized the problem:
- The Card "Magisk" in MagiskManager is showing the following:
- A/B: No
- Installed: n/a <---------
- SAR: Yes
- Ramdisk: Yes
- Crypto: n/a
- MagiskManager has no bottom menu

## How I flashed Magisk (also tried flashing multiple times)
- Lineage Recovery 17.1-20210117 > Apply Update
- sideloading fails: "serving: 'Magisk-v21.1.zip' (~47%) adb: failed to read command: Success"
- TWRP 3.0.2 > ADB Sideload
- sideloading succeeds
- fastboot flash boot patched_boot.img
- fastboot fails: "fastboot: error: Couldn’t parse partition size ‘0x’"
- fastboot flash:raw boot patched_boot.img
- fastboot succeeds

Is there a way to flash Magisk with debugging output or even install Magisk by hand?

Have you tried flashing the zip via twrp or other recovery? It seems like when you try to flash it, it's trying to flash a broken img.

 

[FourSilver]

I'm guessing you have / can use Fastboot then?

Correct... Only after I have done a factory reset to get rid of the bootloop.

As seen in installation instructions, this is the method for Samsung devices. I'm unaware of other OEMs packaging boot / recovery images this way. PW

That makes sense. Thanks for the clarification.

 

[FourSilver]

re: EDL tool: I think he was saying that ADB or fastboot has some option to "boot" into Emergency Download Mode. As someone else mentioned, this might be one of those cases where you have to hold a dead chicken in one hand while connecting a powered down phone to the USB cable already connected to a PC running ADB (or fastboot). If you can find the right ritual, it's probably less frustrating than the "hold three buttons until precisely half-a-second *before* a certain message shows on the screen, at which point switch to four other buttons".

It seems an even less frustrating approach would be to use the SP Flash Tool's Download feature to restore the device to the factory configuration.

 

[nowster]

I'm trying out the MVK kernel at the moment for the same reason.

Nope! The current MVK kernel doesn't stop the f2fs lockups. In fact, it might be worse than stock!

 

[FourSilver]

No. Any older version of the Manager will still use the same update channel as a new version, so it makes no difference. To downgrade Magisk using the Manager you'll have to use a custom update channel (or flash the zip manually as you would a module zip, I'd forgotten about this possibility), and then it doesn't really matter what version of the Manager you use (unless we're talking very old releases of Magisk or Manager).

This is a really interesting approach. Last weekend, @a-dead-trousers posted information on the forum about a TWRP release for the Atom XL. I wonder if I could use that to flash a zipped version of Magisk that apparently worked (i.e. prior to v8.0.0) for the device.

Is this still considered a "downgrade", since installing TWRP requires installation of a non-stock ROM? (According to the install docs for the TWRP release, "booting into stock ROM will replace TWRP with the stock recovery.")

 

[x.trinity]

Ive tried A11 but Magisk is not working as it supposed to ..Back to A10 and it works properly.
Ive checked Installation guide from Magisk GitHub, but its confused..its not possible to install Magisk through Magisk Manager anymore, nor flashing magisk.zip from recovery?

 

[regularmen]

I think this is related to the f2fs problem. I've had this a few times with my Pixel 3a.

Me, too, with my Pixel 3. I wonder is this something we can expect to be fixed in a future Android update, or are we going to have to fix it ourselves with a patched or custom kernel? I hate that my phone feels unstable now, after years of being rock solid with A10 and Magisk.
Edit...I just installed the ElementalX kernel. Seems stable so far with systemless hosts enabled. I used to use it with my old Nexus 5, but this is the first time I've used it with the Pixel 3.

Hi, thanks for the response, at least I'm getting somewhere.

So what can we do about this issue. Several google searches shows dead end and it seems a recurring issue to some hardware.

 

[pndwal]

This is a really interesting approach. Last weekend, @a-dead-trousers posted information on the forum about a TWRP release for the Atom XL. I wonder if I could use that to flash the a zipped version of Magisk that apparently worked (i.e. prior to v8.0.0) for the device.

Is this still considered a "downgrade", since installing TWRP requires installation of a non-stock ROM? (According to the install docs for the TWRP release, "booting into stock ROM will replace TWRP with the stock recovery.")

Yes, flashing w/ custom recovery achieves the same thing if it works / can be done, so it will be a downgrade if using earlier version.

There are also usually ways to make a custom recovery stick w/ stock rom. Often simply booting immediately to recovery after install does this, or simlply having Magisk root installed, but but it may be more difficult for some devices.

Of course, you can keep stock recovery and still boot / use custom recovery from PC using Fastboot (fastboot boot recovery.img). PW

 

[pndwal]

It seems an even less frustrating approach would be to use the SP Flash Tool's Download feature to restore the device to the factory configuration.

QCom Emergency Download mode and MTKs similar 'Emergency' mode is generally for when bootloader is corrupt / Fastboot function is broken. I think he suggested this as an alternative option because you indicated you couldn't use Fastboot initially. PW

 

[Didgeridoohan]

This is a really interesting approach. Last weekend, @a-dead-trousers posted information on the forum about a TWRP release for the Atom XL. I wonder if I could use that to flash the a zipped version of Magisk that apparently worked (i.e. prior to v8.0.0) for the device.

Is this still considered a "downgrade", since installing TWRP requires installation of a non-stock ROM? (According to the install docs for the TWRP release, "booting into stock ROM will replace TWRP with the stock recovery.")

Yes, flashing w/ custom recovery achieves the same thing if it works / can be done, so it will be a downgrade if using earlier version.

There are also usually ways to make a custom recovery stick w/ stock rom. Often simply booting immediately to recovery after install does this, or simlply having Magisk root installed, but but it may be more difficult for some devices.

Of course, you can keep stock recovery and still boot / use custom recovery from PC using Fastboot (fastboot boot recovery.img). PW

Just to be clear (since I was a little unclear when I said "flash the zip manually as you would a module zip"), what I meant was that you can take a Magisk zip and install it from the modules section of the Manager (as long as you're already rooted). I haven't tried that in a while though (actually forgot about it), but it has worked perfectly in the past.

 

[nowster]

For anyone with AdAway problems with Amazon "sad dog pages", make sure you've enabled IPv6 support in AdAway, then pause and turn on AdAway again.

 

[BHUSHAN7988]

Myjio app still does not work for me. Safety net passes every time for me.
Op6t
Stock oos
Have edxposed white list mode

Any solution?