Update Magisk 17.1 to 18.1? - General Questions and Answers

I currently have Magisk 17.1 installed and when I open Magisk manager I am notified about the new update to Magisk manager v7.0.0. When I update to the new manager and try to open it I am told that it came open because Magisk is below v18.0.
My question is what is the best/safest way of updating to 18.0/18.1 from 17.1? I don't have TWRP installed currently. Do I need to uninstall Magisk, patch a system.img with the latest version (18.1), then reinstall that way? Supposedly you can easily go from 18.0 to 18.1 but I haven't found any straight forward answers to go from 17.x to 18.x.
Thanks for any help

Related

Magisk 14.5 is officially in Beta

Just tested it this morning as all is working well. Now we are officially in the supported device (along side with Pixel 2 and 2XL). Thus means that we can now patch boot.img on the fly using Magisk Manager when there's an OTA update.
Steps would be the same as Pixel 2 series as our phones apparently using the same partition and logic method as the Pixel 2. Mentioned here : https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
I would suggest anyone who uses magisk snapshot build to upgrade to this latest version for proper magisk patching without TWRP. For minimal issue :
1. install magisk manager 5.4.1 (your current app will prompt for update usually, if not sideload from the official magisk beta xda forum.)
2. Uninstall magisk using the manager app, this will restore your boot.img backup. DO NOT REBOOT, just tap close.
3. Tap update/install magisk. It will then ask which method of installation. Choose install right now (recommend).
4. Reboot and wait, latest magisk should be installed after reboot.
Note : if the backup boot img is not stock, not available or is already patched. You'll need to boot to fastboot, flash your current build boot img. And then boot twrp to flash the magisk 14.5 flashable zip.
Full details here : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

Magisk — Invalid Uri / Installation failed

Hi,
I am running Magisk 16.0 on my OnePlus 3. I would like to install my modules via the manager, but I always get that error. What's there to be done? Thanx.
AlexBurnout77 said:
Hi,
I am running Magisk 16.0 on my OnePlus 3. I would like to install my modules via the manager, but I always get that error. What's there to be done? Thanx.
Click to expand...
Click to collapse
Latest magisk is 17.2 version so it seems you need to update it

Android 10 Root Guide?

So how do we root with offical Android 10 update? My last way i rooted doesnt seem to be working anymore? Any guides?
Magisk working on final android 10
oscar1823 said:
So how do we root with offical Android 10 update? My last way i rooted doesnt seem to be working anymore? Any guides?
Click to expand...
Click to collapse
Magisk is working on my pixel 3a with the current android 10.
First, I (fully) uninstalled magisk via magisk manager, then did an OTA to Android 10.
After that, I followed "The Boot Image Patching Installation method" on this guide:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783
Take care: use the latest canary-build of magisk, with the release one it didn't work.
Magisk refuses to install after upgrade to 10. Whether by patched image or by twrp, no magisk, no root.
alliance1975 said:
Magisk refuses to install after upgrade to 10. Whether by patched image or by twrp, no magisk, no root.
Click to expand...
Click to collapse
Odds are you are using the standard Magisk version and not the latest Canary version. TWRP doesn't work on Android 10, so you can't use it to install Magisk.
sic0048 said:
Odds are you are using the standard Magisk version and not the latest Canary version. TWRP doesn't work on Android 10, so you can't use it to install Magisk.
Click to expand...
Click to collapse
I almost brick my phone, I guest all we need to do now is wait till a compatible version of TWRP gets released.. the lastest does not read the Pixel 3a memory/data, thus Magisk Canary cannot be installed
omiCar said:
I almost brick my phone, I guest all we need to do now is wait till a compatible version of TWRP gets released.. the lastest does not read the Pixel 3a memory/data, thus Magisk Canary cannot be installed
Click to expand...
Click to collapse
I installed it while still Pie.
sic0048 said:
I installed it while still Pie.
Click to expand...
Click to collapse
That was my mistake, I didnt installed the canary versino while on Pie. I guest we all have to wait... thanks tho
I made the mistake of having Magisk set to beta instead of canary when I did the Magisk OTA update, but no issues with the regular boot image patching method.
Simply follow the guide linked above and you should be fine.
omiCar said:
That was my mistake, I didnt installed the canary versino while on Pie. I guest we all have to wait... thanks tho
Click to expand...
Click to collapse
Did you install the Canary Magisk Manager App? I would think you could install the Canary version that way even if you are on Android 10. The biggest unknown for me is if the fact that you have the Magisk stable version already installed would cause some issues. Normally I would recommend that you completely uninstall Magisk via the Magisk Uninstall zip and TWRP prior to moving to Canary, but obviously that isn't an option without TWRP.
Got it to work.
1. Sideloaded the Android 10 OTA through adb.
2. Download the factory image and extract the boot.img
3. Move boot.img to your phone.
4. Download the Canary Magisk Manager (NOT DEBUG).
5. Use Canary Magisk Manager to download Magisk Canary (19.4) (NOT DEBUG).
6. Use Canary Magisk Manager to install Magisk Canary, select file and patch option. Select the boot.img file.
7. Transfer the magisk_boot.img to your computer.
8. Reboot to fastboot.
9. "fastboot flash boot magisk_boot.img"
10. If it works, then it works.
11. If it doesn't work, it will probably hang at fastboot.
12. If that is the case "fastboot set_active other" "fastboot reboot"
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
sic0048 said:
Did you install the Canary Magisk Manager App? I would think you could install the Canary version that way even if you are on Android 10. The biggest unknown for me is if the fact that you have the Magisk stable version already installed would cause some issues. Normally I would recommend that you completely uninstall Magisk via the Magisk Uninstall zip and TWRP prior to moving to Canary, but obviously that isn't an option without TWRP.
All you really need to do is flash Pie back on the phone and start the process over. I realize that seems like a long process, but it really isn't that hard. Just be sure to backup any important data off phone before you start because installing Pie should wipe the phone.
Click to expand...
Click to collapse
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
darkmeridian said:
1. Sideloaded the Android 10 OTA through adb.
2. Download the factory image and extract the boot.img
3. Move boot.img to your phone.
4. Download the Canary Magisk Manager (NOT DEBUG).
5. Use Canary Magisk Manager to download Magisk Canary (19.4) (NOT DEBUG).
6. Use Canary Magisk Manager to install Magisk Canary, select file and patch option. Select the boot.img file.
7. Transfer the magisk_boot.img to your computer.
8. Reboot to fastboot.
9. "fastboot flash boot magisk_boot.img"
10. If it works, then it works.
11. If it doesn't work, it will probably hang at fastboot.
12. If that is the case "fastboot set_active other" "fastboot reboot"
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
Click to expand...
Click to collapse
Thanks for the response, I will download the Andriod 10 and flash it into my phone, hopefully it will work
darkmeridian said:
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
Click to expand...
Click to collapse
I agree that normally that would work.
However, simply replacing the boot.img file doesn't completely uninstall Magisk. That is why there is a Magisk Uninstaller zip that can be used with TWRP. It normally isn't needed, but it is a great way to completely wipe Magisk if you are having issues. Obviously that isn't an option on Android 10 currently because TWRP doesn't work yet.
Hopefully he doesn't have any issues moving from stable to Canary Magisk versions. But if he does, he will likely have to flash a full factory image to completely wipe the phone and reinstall everything without traces of Magisk
flow5673 said:
Magisk is working on my pixel 3a with the current android 10.
First, I (fully) uninstalled magisk via magisk manager, then did an OTA to Android 10.
After that, I followed "The Boot Image Patching Installation method" on this guide:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783
Take care: use the latest canary-build of magisk, with the release one it didn't work.
Click to expand...
Click to collapse
This worked for me. Thanks
darkmeridian said:
1. Sideloaded the Android 10 OTA through adb.
2. Download the factory image and extract the boot.img
3. Move boot.img to your phone.
4. Download the Canary Magisk Manager (NOT DEBUG).
5. Use Canary Magisk Manager to download Magisk Canary (19.4) (NOT DEBUG).
6. Use Canary Magisk Manager to install Magisk Canary, select file and patch option. Select the boot.img file.
7. Transfer the magisk_boot.img to your computer.
8. Reboot to fastboot.
9. "fastboot flash boot magisk_boot.img"
10. If it works, then it works.
11. If it doesn't work, it will probably hang at fastboot.
12. If that is the case "fastboot set_active other" "fastboot reboot"
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
Click to expand...
Click to collapse
Can you elaborate on this? like is there a video, or more detailed tutorial on how to accomplish this?
If you experience manager telling you that Magisk isn't installed after installing it through fastboot, uninstall manager and reinstall it. Deleting app data won't do the trick. Strange bug but I encountered that in the Q beta
Anyone else having issues with the canary build? I hard reboot and it shows magisk not installed, then I reboot again and its installed again?
Also Android Q is hella laggy for me?
Currently doing a full fresh image install
Magisk installed ok but it won't allow root operations. In particular neither app uninstaller (root) nor titanium backup is capable or removing system apps. Magisk includes them superuser list but the apps don't perform. Safety net both true and advanced settings has preserve avb 2.0 unchecked. App remover always fails and titanium won't show app list. Canary Magisk installed but it's as though there is no root.
MM is version 7.3.3
M is version 19.4
alliance1975 said:
Magisk installed ok but it won't allow root operations. In particular neither app uninstaller (root) nor titanium backup is capable or removing system apps. Magisk includes them superuser list but the apps don't perform. Safety net both true and advanced settings has preserve avb 2.0 unchecked. App remover always fails and titanium won't show app list. Canary Magisk installed but it's as though there is no root.
MM is version 7.3.3
M is version 19.4
Click to expand...
Click to collapse
Can't recommend uninstalling system apps anyway. Hasn't worked for me under Pie either. Rebooting always brought the app back and in the case of Digital Wellbeing, I uninstalled it through Root Uninstaller and encountered a bootloop.
Velcorn said:
Can't recommend uninstalling system apps anyway. Hasn't worked for me under Pie either. Rebooting always brought the app back and in the case of Digital Wellbeing, I uninstalled it through Root Uninstaller and encountered a bootloop.
Click to expand...
Click to collapse
For now I disabled the unused apps. Similar behavior also in pie. One update app remover wouldn't work but titanium would, the next update the reverse would happen. I think the apps need updating so as to work with Android 10.
omiCar said:
Can you elaborate on this? like is there a video, or more detailed tutorial on how to accomplish this?
Click to expand...
Click to collapse
I don't have a video but you can look up the individual steps. You want to do the OTA through ADB sideloading. Then patch the stock boot.img with Magisk Canary, which was linked to above, and then flash with fastboot.
alliance1975 said:
Magisk installed ok but it won't allow root operations. In particular neither app uninstaller (root) nor titanium backup is capable or removing system apps. Magisk includes them superuser list but the apps don't perform. Safety net both true and advanced settings has preserve avb 2.0 unchecked. App remover always fails and titanium won't show app list. Canary Magisk installed but it's as though there is no root.
MM is version 7.3.3
M is version 19.4
Click to expand...
Click to collapse
Uninstall and reinstall Canary Magisk Manager (NOT DEBUG). I had both force encryption and preserve avb CHECKED. Then patch boot.img and flash using fastboot.

System update 01/21

I've seen several posts that upgrading to Android 11 is causing serious issues with twrp and root. I have an update dated 01/21 that is ready to install and I'd like to know if I can install it and still keep twrp and root. I'm on stock model gm1925 build 10.0.9.gm27ba and as stated, keeping root is important for me.
Bump
scuzzo500 said:
I've seen several posts that upgrading to Android 11 is causing serious issues with twrp and root. I have an update dated 01/21 that is ready to install and I'd like to know if I can install it and still keep twrp and root. I'm on stock model gm1925 build 10.0.9.gm27ba and as stated, keeping root is important for me.
Click to expand...
Click to collapse
You are on stable channel surely the notified upgrade is to version 10.0.11, so you can update and keep root and twrp working.
To do this follow the steps described by @strongst in the op7 forum and you will have no problems.
Here the steps to follow:
Optional but highly recommended, backup everything in case of issues.
Download the full rom zip file and the twrp zip installer file and place it into the phone storage memory.
Go to Magisk Manager and uninstall all modules.
Reboot phone.
Go to Android settings -> system -> system update and hit gear icon top right -> local upgrade, select the .zip file of the new firmware and wait for the installation to finish. Attention don't reboot yet!
Install TWRP within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+" select .zip file of the twrp recovery installer. Attention don't reboot yet!
Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version -> hit again install -> hit "install to inactive slot".
Finally reboot.
Reinstall your Magisk Modules.
Done! Your device is now updated and you keep TWRP and root.
Very important: At the moment this procedure is to be considered reliable only if used with firmware based on Android 10.
scuzzo500 said:
I've seen several posts that upgrading to Android 11 is causing serious issues with twrp and root. I have an update dated 01/21 that is ready to install and I'd like to know if I can install it and still keep twrp and root. I'm on stock model gm1925 build 10.0.9.gm27ba and as stated, keeping root is important for me.
Click to expand...
Click to collapse
As of right now there is no TWRP working some have had luck but unfortunately most havent. i have uploaded a patched boot.img that will let you root
how to install android 11 on gm 1925, if my phone does not see files via local update?????

Question LineageOS 19.1 + root with magisk: how to do that?

What's the best way, to install root with magisik on an a52q device?
The manual at https://topjohnwu.github.io/Magisk/install.html seems to describe how to install root with the official Samsung OS, but not with LineageOS?
And how can I update LineageOS regularly with staying root persistent?
Thanks!
redcarholder said:
What's the best way, to install root with magisik on an a52q device?
The manual at https://topjohnwu.github.io/Magisk/install.html seems to describe how to install root with the official Samsung OS, but not with LineageOS?
And how can I update LineageOS regularly with staying root persistent?
Thanks!
Click to expand...
Click to collapse
LineageOS, at least the PHH builds, already have root built in. Just install the Magisk app.
V0latyle said:
LineageOS, at least the PHH builds, already have root built in. Just install the Magisk app.
Click to expand...
Click to collapse
When I install the Magisk app, it says:
Installed: N/A
Zygisk: No
Ramdisk: Yes
When pressing the Install button, I'm asked for selecting and patching a file.
What I'm doing wrong? I use this manual: https://wiki.lineageos.org/devices/a52q/install
Flash Magisk in TWRP. No need to rename the extension, TWRP will flash apks.

Categories

Resources