Hi Devs, Community and all of Android's guy.
I have a OP5T and I have received the OTA update some weeks ago. I have already installed Magisk Manager by a Year, and in this I saw many updates. I generally delete all modules and the complete Magisk. After that, I update the System with the OTA and then install Magisk again (I also prefer it for a matter of order and cleanliness). Today, I have decided to unistall Magisk but both through the manager and through the file unistaller.zip it fails with a bootloop after the flash.
Has anyone a solution for this problem?
Or Is there a way for this version to install the ota without uninstalling magisk?
Thanks a lot!
same problem here
Related
How do I update Magisk? In the main topic it is advised to update Magisk using the Manager but that's not possible. I'm currently having Magisk Manager 6.0.1 with Magisk 17.3 installed. The Manager only asks to update itself to version 6.1. But that version directly crashes on start because there is no backwards compatibility with with Magisk < 18. Therefor I want to update using TWRP. My question is now if I can simply install the new version without uninstalling Magisk? Or do I have to uninstall Magisk first? If the latter, is it enough to restore the original bootloader or do I have to uninstall Magisk completely (and loosing all data in the progress)?
Thanks for your help.
Same question here, somebody please look into this.
I have Magisk 20.1 (Magisk Manager 7.5.1) currently installed on my Samsung Galaxy Tab A (2016). While initially installing it was not as straight forward as it might have been (install doc could use some work; I think it's written for folks with more familiarity with android devices on a day to day basis than those who root a phone maybe once every few years); I installed Magisk and it's been working fine.
However, this morning I had a notification that I needed to run Magisk setup. I told it to do so; it downloaded something; rebooted the tablet ( which wasn't warned of in the notification); and on coming back up ran Busybox so I'm assuming that was the setup. Going into Magisk Manager, however, I got the same notification over again. So I let it update again with the same result.
This time I told it to cancel the update/setup. I then tried to manually do the update from 20.1 (20100) to 20.3 (20300, latest available version). Update proceeded normally until repacking; which failed. Since Magisk is already installed and working (with several root level apps) on this phone; I can't see where this could be the "wrong image problem" which seems to be the most prevalent root cause of this kind of error. Unfortunately the update as distributed doesn't say anything about *why* it can't repack the image; so the message doesn't help us ordinary folks in debugging.
Any ideas as to what the actual issue is?
Android info:
Version 8.1.0
Kernel 3.18.14-1570595
Build M1AJQ.T580UEU4CSC1
Note: Busybox had an update I believe came out sometime yesterday (saw notification it updated successfully). Could it be that something in the Busybox update broke the Magisk update process?
Hi, my device currently on China ROM v2.20 and rooted with Magisk. Is it safe to OTA update to China ROM v2.21?
When I read about Magisk I found it:
"Magisk works systemless-ly, and it doesn’t modify or alter your system partition. If you want to install a banking application or if you want to install official OTA updates, and much more. You can install the OTA updates without losing the root privileges, and that is everyone need. They don’t need to root again and again."
Anyone dare to try?
Suddenly after a long time even after not updating because the new update bricked my phone Magisk Manager 5.5.5 (really old version) suddenly decided to give up on me..
Magisk Manager keeps prompting for a update now but I cannot open or install it. Theres even no more crash message.. I have no xposed modules or anything installed, just Magisk Manager and root in order for my own small apps that I wrote(years ago) and to read wpa_supplicant.conf...
I have no known damage to my phone. I am still using my Lenovo Vibe P2 same firmware Android 7 kernel 3.18.31-perf-g247719e.
Any advice?
Hint: Can't update rom firmware, because 1. I have been banned from OTA because I unlocked bootloader. 2. Because I am too lazy.
I can give adb log, but I have not touched Magisk Manager for years and suddenly it ****ed up.. Now I want to run a specific app and it checks for root, I need a magisk module to hide it.
Other applications still work fine even those what can check for root. Except for a few new ones.
Hello everyone, I have a weird issue that I never encountered before. I updated my custom ROM from fastboot, and as always I had to re-root my device after updating. Im under Android 12, so I didnt use TWRP but I used the patched boot image method to reinstall magisk and have my phone rooted. Surprisingly, it seems my phone is rooted correctly, but the Magisk app shows Installed:N/A. A quick google search showed that it could be due to not unhiding Magisk before updating (even If I never did in the past and never had this issue). I tried the solution I found (unistalling magisk from adb) but it didnt fix the problem. Any idea on how to solve this?
[Discussion] Magisk - The Age of Zygisk.Magisk 24.1 released and perfect for android 12.