I have the Pixel 3XL with Android 9.
Magisk indicates Installed 19.3, latest 22.1
Magisk Manager indicates installed 7.3.2, latest 22.1
I'd like to bring Magisk up to date.
Are there any issues or special procedures for performing this update spanning several versions?
Is there a preferred order to update? Magisk first, then Magisk Manager? Or Manager first?
Is a reboot after each update?
It's always the Magisk app that gets updated first. And the reason why you see such a big jump in the app version is that from Magisk v22 the app and the base are no longer separate. It's all contained within the app. See the release notes for details:
https://topjohnwu.github.io/Magisk/releases/22000.html
The reason why you don't see the latest version as v23 (the actual latest release) is that the update channel changed at that point and you won't see the v23 update before you update to v22.1. Rebooting in-between Magisk updates is a good idea. Updating the app all the way to v23 shouldn't be any issue though. You might encounter issues where the app won't recognise such an old Magisk version. I can't remember where the current breaking point is set...
Big update jumps always have the possibility of causing issues and sometimes a clean install might be necessary. But, in theory it should be fine. Just make sure to have a backup of anything important...
Related
I have a Xiaomi Redmi x4 that has been flashed and running mokee.
I can flash Magisk 12 and the Magisk Manager 4.3.3 just fine and then flash the fix (https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431) to make it unseen and the CTS profile to go green, working root etc. If I flash Magisk v13 or 13.1 I believe that it flashes okay, but when I install Magisk Manager 5.x whenver I try to open the manager it will instantly close itself. I've tried using the magisk uninstaller and trying again with fresh ROM but it seems to do the same thing.
I'm unsure if this is at all in any way a common problem, I did a little looking around and couldn't find my problem exactly. My apologies if has been answered many times before.
Thanks.
I got this problem since beta too
i have the same problem
it's know issue, just revert back to 5.0.6.
i suggest to refer to magisk manager's github topic: https://github.com/topjohnwu/MagiskManager/issues/225
[Problem]
I noticed google pay not working after enjoying magisk happily for two days.
[Research]
I searched the forum and found many others have issue with google pay, too.
[Trial]
I started to do something with the hope to solve this problem.
1. I changed the update channel to beta test and installed magisk v19. Google pay was not working.
2. I then changed back to stable update channel to install magisk v18. Strange thing happened.
3. Phone booted fine but magisk manager detected no trace of magisk. I re-flashed patched_boot.img. Same thing, magisk was gone.
4. I am on stock ROM (S6 edge) and installed magisk by patching boot.img. I had no TWRP recovery. I could not do much under this circumstance.
5. So, I was in a situation of missing magisk and disabled google pay.
[Final]
I flashed the stock ROM via odin.
1. The google pay was working again in stock ROM (without root).
2. I lost magisk (and root).
I will install magisk again if google pay can work with it. The problem is the security check by google. I still hope there will be some work-around method.
You can never be certain that a dirty downgrade will work. You can of course try, but be prepared for trouble.
If I remember correctly, in this case, simply uninstalling the Manager and reinstalling the apk that comes bundled with v18.1 might have fixed things.
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?
Curious if anyone else is running into this issue or if I'm just completely missing something but for the last month or two, I completely lost the ability to get on any canary or canary_debug build channel of magisk. I have tried everything, flashing multiple different builds of canary_debug.zip along with the canary_debug.apk's and no matter what I do the option to select canary or canary_debug under the update channel options is gone. As a result of this, as soon as I use the "hide magisk manager" feature, my magisk app reverts to the beta.apk which is the old UI and I have some random issues with that apk not displaying all my installed modules. I have completely uninstalled magisk and reinstalled, I have factory reset, I've tried stock ROMs, custom ROMs and nothing works. Someone please direct me on what I'm doing wrong, I have never ever run into this issue before in all my time using magisk.
1dopewrx05 said:
Curious if anyone else is running into this issue or if I'm just completely missing something but for the last month or two, I completely lost the ability to get on any canary or canary_debug build channel of magisk. I have tried everything, flashing multiple different builds of canary_debug.zip along with the canary_debug.apk's and no matter what I do the option to select canary or canary_debug under the update channel options is gone. As a result of this, as soon as I use the "hide magisk manager" feature, my magisk app reverts to the beta.apk which is the old UI and I have some random issues with that apk not displaying all my installed modules. I have completely uninstalled magisk and reinstalled, I have factory reset, I've tried stock ROMs, custom ROMs and nothing works. Someone please direct me on what I'm doing wrong, I have never ever run into this issue before in all my time using magisk.
Click to expand...
Click to collapse
As posted in Magisk canary forum:
Didgeridoohan
26-02-2020, 12:35 AM
Not having the Canary channel in the Manager settings is a bug, of course (it's a Canary release after all). Fixed upstream, so add a custom channel and wait for a new release (no ETA, of course).
https://forum.xda-developers.com/ap...canary-channel-bleeding-edge-t3839337/page301
Tulsadiver said:
As posted in Magisk canary forum:
Didgeridoohan
26-02-2020, 12:35 AM
Not having the Canary channel in the Manager settings is a bug, of course (it's a Canary release after all). Fixed upstream, so add a custom channel and wait for a new release (no ETA, of course).
https://forum.xda-developers.com/ap...canary-channel-bleeding-edge-t3839337/page301
Click to expand...
Click to collapse
Thanks buddy, I appreciate the answer. Glad I'm not crazy. Funny thing is a few hours ago, I flashed a new rom to try out (PixelDust) and after flashing the patched boot.img I had the canary debug option back. I will add in my specific case, I didn't have Canary as the bug-report you linked states because my magisk manager was the old UI, which correct me if I'm wrong, isn't Canary. I could not get the new UI to stick, hence it switching to the beta build that was permanently selected in options.
Hi everyone!
It's been about a year and a half since I first installed Magisk on my phone with TWRP and considering that I now noticed I'm getting SafenityNet API error, I wanted to update my Magisk to the latest version and install the Universal SafetyNet module as well to fix this issue.
I just have some questions regarding this:
I'm running Magisk Manager 7.5.1 & Magisk 20.4 repacked and with Magisk Hide, how can I update from Magisk 20.4 to Magisk 23? My phone shows 22.1 as the latest.
Before updating do I need to restore Magisk Manager to the original package and app names?
Will updating Magisk affect my already installed Modules or will they stay in effect?
I'm using a Xiaomi with Android 9 Pie and MIUI Global 11.0.5.0
Thanks in advance.
reldinado said:
Hi everyone!
It's been about a year and a half since I first installed Magisk on my phone with TWRP and considering that I now noticed I'm getting SafenityNet API error, I wanted to update my Magisk to the latest version and install the Universal SafetyNet module as well to fix this issue.
I just have some questions regarding this:
I'm running Magisk Manager 7.5.1 & Magisk 20.4 repacked and with Magisk Hide, how can I update from Magisk 20.4 to Magisk 23? My phone shows 22.1 as the latest.
Before updating do I need to restore Magisk Manager to the original package and app names?
Will updating Magisk affect my already installed Modules or will they stay in effect?
I'm using a Xiaomi with Android 9 Pie and MIUI Global 11.0.5.0
Thanks in advance.
Click to expand...
Click to collapse
Maybe let Magisk Manager take you to v22.1, then you'll be one step away from v23.0 and hopefully at some point it becomes available. If upgrading to v22.1 succeeds you'll end up with one app that is Magisk SU and the manager all in one. I mention this in case you're wondering why Magisk Manager disappeared.
I don't understand what you mean about restoring Magisk Manager "to the original package and app names" but your modules should still work after upgrading. Worst case would be a module that didn't keep up with Magisk and isn't supported anymore.
reldinado said:
Before updating do I need to restore Magisk Manager to the original package and app names?
Click to expand...
Click to collapse
Yes, you do. See the v22.0 release notes:
https://topjohnwu.github.io/Magisk/releases/22000.html
Didgeridoohan said:
Yes, you do. See the v22.0 release notes:
https://topjohnwu.github.io/Magisk/releases/22000.html
Click to expand...
Click to collapse
Ahh, the question makes sense now. I've never needed to conceal Magisk.
Didgeridoohan said:
Yes, you do. See the v22.0 release notes:
https://topjohnwu.github.io/Magisk/releases/22000.html
Click to expand...
Click to collapse
Thanks to both of you for the clarifications.
I will unhide/restore the manager and will install 22 before going onward to 23.