Hello, I installed magic 12.0 with no problems, But I have had issues specifically trying to add modules I keep getting installation error notice. I have read here that magisk 12.0 has many problems. I read here that many highly recommended to update to version 14 And manager version 5.4.3. My question is do I need to uninstall magisk 12.0 and manager 1st or can I just simply Flash the new 2 zip versions up to 14.0 tespectively? Any help on this matter is greatly appreciated.
taudio123 said:
Hello, I installed magic 12.0 with no problems, But I have had issues specifically trying to add modules I keep getting installation error notice. I have read here that magisk 12.0 has many problems. I read here that many highly recommended to update to version 14 And manager version 5.4.3. My question is do I need to uninstall magisk 12.0 and manager 1st or can I just simply Flash the new 2 zip versions up to 14.0 tespectively? Any help on this matter is greatly appreciated.
Click to expand...
Click to collapse
I'd flash magisk uninstall zip first and uninstall the manager. Then flash new
I recently had the same issue with, 12.0 just stopped passing safety net for some reason. I flashed the 14.0 zip from twrp straight away and had no problems.
Related
I updated Magisk Manager to 5.5.5 and it is asking if I want to update Magisk from 15.2 to 15.3. If I want to, can I just patch the boot img that is on the phone (Pixel 2) from installing 15.2 on 8.1.0 January patch, then flash that? Do I need to download the boot img again? Do I have to (should I) remove the old patched boot img prior to doing so?
Do I have this somewhat straight, or am I going off the rails? I looked for specific "upgrading" info, but just keep seeing the installing for the first time info.
Thanks in advance!
amajamar said:
I updated Magisk Manager to 5.5.5 and it is asking if I want to update Magisk from 15.2 to 15.3. If I want to, can I just patch the boot img that is on the phone (Pixel 2) from installing 15.2 on 8.1.0 January patch, then flash that? Do I need to download the boot img again? Do I have to (should I) remove the old patched boot img prior to doing so?
Do I have this somewhat straight, or am I going off the rails? I looked for specific "upgrading" info, but just keep seeing the installing for the first time info.
Thanks in advance!
Click to expand...
Click to collapse
I don't remember the actual choices, since mine is already updated, but I do it straight from Magisk Manager app. I think I choose update then the direct install (recommended) option. I believe it then shows the log as it updates and once done gives option to reboot. Once it reboots, you should be on latest (15.3) version of Magisk, and you still have root and pass Safety checks. It has never caused any boot loops for me, just smooth and simple.
HTH!
amajamar said:
I updated Magisk Manager to 5.5.5 and it is asking if I want to update Magisk from 15.2 to 15.3. If I want to, can I just patch the boot img that is on the phone (Pixel 2) from installing 15.2 on 8.1.0 January patch, then flash that? Do I need to download the boot img again? Do I have to (should I) remove the old patched boot img prior to doing so?
Do I have this somewhat straight, or am I going off the rails? I looked for specific "upgrading" info, but just keep seeing the installing for the first time info.
Thanks in advance!
Click to expand...
Click to collapse
like the other response, i am able to upgrade magisk directly from magisk manager (direct install method)
one caveat, i don't know if it's still true, i had an issue upgrading a month or two back and someone on here recommended i set my magisk to the "beta" channel (settings -> update channel). i suspect this is no longer needed, but i left it on the beta channel and have had no issues upgrading magisk every time it notifies me of a new update
Ok, so I can upgrade directly from the app. Great! I guess I was overthinking...
Thanks!
I've installed a deodexed rom with Magisk but now I can't update past 15.x version of Magisk.
I tried to do it in the Magisk app, and trough TWRP both to version 16.0 and to version beta 16.1, but it always just hangs in the part "Flashing new boot image".
I've waited several hours in that part, but nothing.
I've also tried it with and without TWRP installed.
I think I'm missing some step here.
I always uninstall Magisk via TWRP and the latest official uninstaller prior to flashing an upgraded version. A bit cumbersome to once again configure all the settings in the modules, but it works for me.
Hi guys! I am having some issues when trying to install magisk. I am currently running the latest twrp-3.2.2-0-enchilada. When trying to install magisk I'm currently having a constant error. Attached are the recovery log and a screenshot.
Magisk Error 1 fix
Hi, it looks as though you are trying to install an unsupported version of magisk you need to use the 16.4 installer not the 16.0 installer this will most likely fix your issue, I hope this helped. PS it is a beta version of magisk not the latest stable build.
16 is the stable build and SHOULD work!
Did for me.
It looks like the problem was a bad install of magisk. I went to the forums of magisk and found an uninstaller. I flashes it and then flashes the stable version. It looks like it worked. I have root back.
I'm pretty sure i couldn't be the only one who recently updated from 16.0 to 17.0 (Stable Channel). I first updated the magisk manager and it prompted me to flash 16.0(1600) instead of a 17.0 version. Well since i flashed the 16.0(1600) version it prompted me to download, i got into a nasty bootloop and thankfully recovered with me having the stock ROM in my storage. I'm wondering if anyone else went through the bootloop i did this morning and if people should just flash the newer zips outside of the manager
HighOnLinux said:
I'm pretty sure i couldn't be the only one who recently updated from 16.0 to 17.0 (Stable Channel). I first updated the magisk manager and it prompted me to flash 16.0(1600) instead of a 17.0 version. Well since i flashed the 16.0(1600) version it prompted me to download, i got into a nasty bootloop and thankfully recovered with me having the stock ROM in my storage. I'm wondering if anyone else went through the bootloop i did this morning and if people should just flash the newer zips outside of the manager
Click to expand...
Click to collapse
I also got a bootloop but I flashed 17.0 through twrp. I had to go through the qualcomm drivers process to unbrick it because it was hard bricked lol
Flashed uninstall magisk and than magisk 17 and all worked well.
dracoboss said:
I also got a bootloop but I flashed 17.0 through twrp. I had to go through the qualcomm drivers process to unbrick it because it was hard bricked lol
Click to expand...
Click to collapse
That's horrible to have a hard bricked device. There's a hotfix that just got released right at this moment (17.1) so i'd recommend you to download that and continue the process to try getting root access back
Got the same problems as described here. Then I downloaded the latest Magisk uninstaller and Magisk 17 from the Magisk thread. The next step was to flash the uninstaller and afterwards Magisk 17 and the device booted well.
Running 17.1 and still getting the same thing with safety net check as before
The response is invalid
HighOnLinux said:
That's horrible to have a hard bricked device. There's a hotfix that just got released right at this moment (17.1) so i'd recommend you to download that and continue the process to try getting root access back
Click to expand...
Click to collapse
Yeah that's what I did and everything is fine... For now lol. Thanks
From Magisk 17.0 to Magisk 17.1, install it automatically. SafetyNet test successful
it's better and more secure deinstall first magisk manager clearing cache and data, install magisk 17.1 from twrp and if magisk manager doesnt be installed, install the apk
As the title says, I want to know if I can root Android 13 using Magisk 22.1
Any answers appreciated
bulieme0 said:
As the title says, I want to know if I can root Android 13 using Magisk 22.1
Any answers appreciated
Click to expand...
Click to collapse
No.
Android 12 (and Android 13) started using Boot Image Header v4, and Magisk prior to 23016 does not properly handle the boot image header, resulting in a boot failure. Several more fixes were needed until 24.0 which was fairly stable, and we are still dealing with issues with attempting to patch OTA updates on A/B devices.
I highly recommend you use the latest Magisk 25.2.