Hello, i installed Magisk via TWRP, is there a way to update system (maybe removing Magisk, reinstalling it after the update) without bootlooping?
Related
I rooted my phone and use magisk modules too. New update appeared, am I safe to install it OTA? Will I lose root or magisk if I update?
Tomogitarist said:
I rooted my phone and use magisk modules too. New update appeared, am I safe to install it OTA? Will I lose root or magisk if I update?
Click to expand...
Click to collapse
The update won't go through and you will encounter an installation problem error. Revert back to the stock boot.img of your security patch month (e.g. January, Feb patch) and then try the OTA and you should be able to update.
Google "how to apply OTA with Magisk" if you haven't touched the system partition. But no it is not safe, I bootlooped.
It is safe. OTA updates system partition. Magisk uses boot partition.
In other hand if you ever mounted system as read AND WRITE even if you didn't make any change to it the OTA will fail.
OTA also will fail if detects boot partition modification, what means you'll have to temporally restore boot (uninstall Magisk) to update and then reinstall it. You'll find how to in this forum.
When I install an update from the Lineageos system this reminds Magisk and the TWRP, and if I install from TWRP you always have error "signature mismatch" even if I downloaded the same update or other updates.
Install update via lineage updater, then boot TWRP Flash magisk and twrp
an expert computer friend of mine said that there should be a configurable device setting, perhaps in the developer settings, to remove the twrp installation which should consequently also not remove magisk. does anyone know the method? even if it is difficult I can do it, or even a method to install via twrp the system that should not give problems whatsoever.
Hello friends,
I would like to know how to apply OTA update via TWRP with the magisk running. I have not found any good tutorials that explain the correct procedure. Always when I need to update the security path, I remove all the root magisk through the zip unistall magisk via TWRP, update the system and then return with custom recovery + root.
So pie is already rolling out on some countries. Before it rolls out to my country, I want to know if the usual method of installing Magisk over ota will work to preserve root. I use magisk solely to enable camera2api for gcam and occasionally for some apps requiring root access. Usually when I receive a security patch for 8.1, I restore stock boot img then apply the update without restarting. After the update, I go to magisk and select install > install to inactive slot and reboot. Anyone tried this while installing pie?
So I'm running the 03/25/2019 Lineage OS microG build for my OP5, it is Android Pie and I have the latest codeworkxx TWRP 03/11/2019 and PIE firmware.
When flashing the rom (clean install) I decided to go unencrypted this time so I used the following force encryption disable zip found bellow after I clean flashed/installed the rom...
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
...followed by flashing magisk right after. Everything worked, LOS PIE is installed and unencrypted/rooted perfectly.
Problem I am having is that now when I try and install the weekly builds through the Android OS updater, it does it's thing, reboots to recovery, installs the update, magisks then re-installs through the survival addon.d script but then the phone just gets stuck into a bootloop. While reading the install messages in TWRP it does mention that magisk is removing dm-verity for what it's worth.
Does this have something to do with magisk or the LOS ROM having an "encrypted kernel" by default and how I am installing an encrypted kernel/update over an unencrypted phone? Or is this some issue with magisk?
Does this mean if I want to flash weekly updates while keeping unencrypted status I will have to dirty flash them by downloading the zip, manually placing it in my storage, booting to recovery, flashing, then flashing the encryption disable zip again and finally Magisk instead of of just pressing a button in the Android OS updater?
Luckily I restored successfully from a backup but I'm wondering is I screwed myself over here setting up my rom without encryption. Never had this issue updating with the weekly builds when my phone was encrypted.
What do you guys think?
Alright well I managed to update my ROM without bootlooping, just like I thought instead of being able to use the built in OS update manager that does everything for you I have to manually download/transfer file to my phone, flash rom update, flash force encryption disable zip and then magisk again.
While this is an alright workaround for now, is there anyway to regain the stock updating functionality built into the rom while remaining unencrypted and having it NOT bootloop my phone each time? What if I want to use addonSU instead of Magisk, I don't think the disable encryption zip works unless you flash Magisk right after unless I have to update the rom, flash the disable zip, flash magisk, remove magisk and then use addonSU.