[Magisk] flipmode_11:
I would suggest your ask in your LG G4 Device forum or Custom ROM forum on XDA, as is the best place. The logic is: Magisk-related issues & Bugs in Magisk Forums, and Device/ROM issues in their forums. :)

Note: [MENTION=4291621]hteles[/MENTION] You can always prefix "@" and the user's name, to mention them, so they get an alert and can read your post.

I would recommend asking your device-specific questions in the Moto Z2 Play forums as it is device specific.

Restore Images means it restores the "Stock_Boot.img" that Magisk backed up when you first installed/flashed Magisk. I don't beleive a backup is made in one circumstance if you use download mode or fastboot (I forget which).

In future, try using BK Disabler (or others like Package Disabler) to disable apps and listeners, free up memory and resources. This allows you to disable apps instead of uninstall. Then you can export a backup of the selected disabled apps, bulk re-enable all apps, flash ROM or OTA update, and then restore the exported backup to re-disable everything.

You can use the Magisk Module - Systemizer (or something) to disable apps systemlessly. :D

If you have made *any* changes to the /system or other partitions (excluding /data) then you should do backups of all your apps

and their data

, then I suggest full device backup (just in case), then restore the Current OS system image and boot image (that wipes boot.prop, all other disabled apps and system changes). Then try updating again to the New OS. If that fails, then it could be one of the other partitions as you mention (e.g. /vendor/). I wouldn't know. But find out your device details (DevCheck, Aida64, etc) and download your current ROM (.md5, .md5.tar or .zip). Always keep it handy, just in case!

Normally - flash stock boot.img (or Magisk's 'stock_boot.img'), recovery.img and current OS's system image, perform the update, then flash your Magisk ZIP or Magisk modified Boot.img to regain root.

The developer has previously suggested members can flash over the top to downgrade, or if you have issues that way, you can uninstall, choose "restore images", then now you're back to stock, flash the older version's Magisk ZIP and patch the boot.img. I beleive v14.0, v15.3 (or v15.4) and v16.0 are the stable and recommended releases.

Fully remove Xposed to prevent any issues. TopJohnWu doesn't recommend using it because it is out of his control. You are *always* going to be better off using Systemless editions of Xposed and any other system (e.g. Busybox NDK) to prevent detection by Google and app developers.

You can either Flash Magisk ZIP via recovery, or install the Magisk APK and then flash the Magisk modified boot.img (option #2) and reboot into TWRP recovery to flash the .img. However if option #3 is available "Direct" then you can use this, which flashes the boot image 'hot', without rebooting. A backup of your boot image is saved on your device as "./data/stock_boot.img".

Actually, you could also use the option in SuperSU to switch to another Super User. That will allow Magisk to just over-write the SuperSU 'su' with it's own. :)

[MENTION=5802494]AndrOmega[/MENTION] I think you misunderstand mate! Here is a basic summary:

Magisk SU/Root is currently at version 16.0 stable, or 16.4 beta. This Super User that can run via shell or other apps.

Magisk Manager is currently at version 5.7.0. This is what gives you the SU GUI and features to interact and control root. It allows you to interface and offers the ability to manage your device, while interacting with your Super User SU elevated environment. e.g. Set PIN to authorise SU commands through apps.

If you can continue to update Magisk Manager, then you should not be concerned as you will continue to enjoy the functionality of Magisk, plus working root! However, to gain access to Magisk SU updates, you need Manager updates.

The other issue is that your settings may be set to

STABLE updates only

, so you will not see Beta SuperUser updates, only Stable. But if your Manager is too old you won't see recent updates (Download ZIP, Patch Boot, Direct Install <--- This One!), so it is important to stick with a combination you are happy with, that is stable and works best.

Stick with the Stable releases unless you have 12+hr/day to be troubleshooting your device.

I hope that wasn't too confusing! :D

No worries mate. Glad you got somewhere. But I would definitely update that TWRP. That has been the major issue that comes to mind with others (e.g.3.1 upgrade to 3.2 to fix immediately). Always check XDA for device issues before buying a new device. :silly:

Good luck [MENTION=6269851]Hadookie[/MENTION]!