Database Info

Upgrading Magisk... Want to confirm how

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!

Anyone able to root the Dec update?

For the life of me I cannot root this latest patch. I have tried 6 times either with having the Magisk app repack the boot image or by booting TWRP to install the Magisk zip. Using either method forces my phone into the same state/condition. When the phone reboots, it goes into recovery which says the data on my phone may be corrupt and prompts me to either try again or factory restore (erase data).

i was able to. i booted into twrp, sideloaded the twrp installer, then the magisk zip and sultan kernel and everything is running smoothly for me

Ok, so I was able to recover and root from an answer given in a pixel 3 thread using:
Pixel 3/Pixel 3 XL
- fastboot flash boot --slot all boot.img (from December factory image)
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- magisk-18.0.zip
- reboot system
What happens though is when I use adaway to update the hosts file, it breaks everything and I can't boot into system until I do the above steps again. Strange...
Do you have adaway install by chance?

Hi! I have no problem with last update, magisk nor adaway. I just flashed last update with flash-all.bat script, than fastboot twrp, install magisk ver. 18... and everything is working on 100%.

To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.

Diesel_Jeremiah said:
To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.
Click to expand...
Click to collapse
I'm on the December patch and am rooted with Magisk 17.1.
I actually just noticed the new update and am fixing to update Magisk. But you don't have to use v18. 0 to root December update. I've been on December update since it came out and rooted like always right away and haven't had any bootloops.

I rooted okay today with Magisk 18.0. It sounds like some people have had problems if they did not first uninstall Magisk with the latest uninstaller. That's what I did as a precaution (rather than just restoring the stock boot.img with the Magisk app, before upgrading the factory image).

FilthyFord said:
I'm on the December patch and am rooted with Magisk 17.1.
I actually just noticed the new update and am fixing to update Magisk. But you don't have to use v18. 0 to root December update. I've been on December update since it came out and rooted like always right away and haven't had any bootloops.
Click to expand...
Click to collapse
I had issues on both of my Pixel 2 phones trying to use any Magisk less than v18.0
I also had issues with v18.0 until I used the uninstaller first.
I read that other people were having the same issue.
I guess you got lucky?

Diesel_Jeremiah said:
I had issues on both of my Pixel 2 phones trying to use any Magisk less than v18.0
I also had issues with v18.0 until I used the uninstaller first.
I read that other people were having the same issue.
I guess you got lucky?
Click to expand...
Click to collapse
I guess so. I always open the .bat file and remove the -w so that it don't we my phone tough. Not sure if that makes a difference.

somin.n said:
Hi! I have no problem with last update, magisk nor adaway. I just flashed last update with flash-all.bat script, than fastboot twrp, install magisk ver. 18... and everything is working on 100%.
Click to expand...
Click to collapse
I enabled automatically granted root access and after a few mins after boot it granted access to adaway and after a reboot it seems to have worked again.

https://androidfilehost.com/?w=files&flid=249276&sort_by=date&sort_dir=DESC

March Boot file - stock & patched

In case it helps anyone out, here is a link to the stock boot.img from March QQ2A.200305.003, and one I patched with Magisk 20.3 (20300).
Stock file: https://drive.google.com/open?id=1I9cnV8rH4GVCgEDJa1j4ps5VwVj3zfD-
Patched file: https://drive.google.com/open?id=1DA7vt1AtFmtc4XYX5_UCTjbkEa0fweuc
These files are to install Magisk. Please only flash it if you are already on March update. This is not March OTA!
Link courtesy of @i5lee8bit; March OTA patched with Magisk 20.4 https://www.androidfilehost.com/?w=files&flid=306923

Dear Mushtafa, great thanks to you! I've been looking for this all day. Thank you!

mushtafa said:
In case it helps anyone out, here is a link to the stock boot.img from March QQ2A.200305.003, and one I patched with Magisk 20.3 (20300).
Stock file: https://drive.google.com/open?id=1I9cnV8rH4GVCgEDJa1j4ps5VwVj3zfD-
Patched file: https://drive.google.com/open?id=1DA7vt1AtFmtc4XYX5_UCTjbkEa0fweuc
Click to expand...
Click to collapse
Doesn't work for me when I flash the magisk and reboot, I can no longer swipe or tap anything on my screen. Only physical side buttons are functioning.

onlyguynamedniles said:
Doesn't work for me when I flash the magisk and reboot, I can no longer swipe or tap anything on my screen. Only physical side buttons are functioning.
Click to expand...
Click to collapse
You've already updated to March and booting OK?
Have Magisk Manager installed?
You could flash the stock file and modify itself with your install of Magisk and see if that makes any difference.
I'm not sure how many people have flashed this? Not sure if anyone else has had issues with it?

mushtafa said:
You've already updated to March and booting OK?
Have Magisk Manager installed?
You could flash the stock file and modify itself with your install of Magisk and see if that makes any difference.
I'm not sure how many people have flashed this? Not sure if anyone else has had issues with it?
Click to expand...
Click to collapse
No I'm still on January, I never got the Feb OTA and didn't bother to try manually since it didn't seem significant enough but I wanted this March update because of the new Pixel drop feature set.

You can't flash the March boot image if you're still on January! That's why you're having issues.
You need to flash the boot mode mage from January, or update to Match firmware

mushtafa said:
You can't flash the March boot image if you're still on January! That's why you're having issues.
You need to flash the boot mode mage from January, or update to Match firmware
Click to expand...
Click to collapse
I tried to do this with the March update downloading it from Google and the result was the same as onlyguynamedniles, my touchscreen not working, I am in February update.
Last month there were several downloads for February, this time for March only one file available.

otrobruno said:
I tried to do this with the March update downloading it from Google and the result was the same as onlyguynamedniles, my touchscreen not working, I am in February update.
Last month there were several downloads for February, this time for March only one file available.
Click to expand...
Click to collapse
You flashed the March boot.img on your February firmware? Why?

mushtafa said:
You flashed the March boot.img on your February firmware? Why?
Click to expand...
Click to collapse
sorry but this was my first time trying this, before all I had to do was:
when OTA was available, went to Magisk Manager/Uninstall/Restore Images (Not Reboot)
applied OTA as everyone ormally would Settings/System/System Update (Not Reboot)
then, go to Magisk Manager/Install/Install to Inactive Slot
finally, after installation done, reboot
but this march update is not appearing so steps I've tried this time:
1. Got the latest boot image
2. Patched boot image in magisk manager
3. Flashed magisk-patched boot image
please your help what's missing?

otrobruno said:
sorry but this was my first time trying this, before all I had to do was:
when OTA was available, went to Magisk Manager/Uninstall/Restore Images (Not Reboot)
applied OTA as everyone ormally would Settings/System/System Update (Not Reboot)
then, go to Magisk Manager/Install/Install to Inactive Slot
finally, after installation done, reboot
but this march update is not appearing so steps I've tried this time:
1. Got the latest boot image
2. Patched boot image in magisk manager
3. Flashed magisk-patched boot image
please your help what's missing?
Click to expand...
Click to collapse
If you're not getting the March OTA, you need to download it from Google and sideload it. https://developers.google.com/android/ota
There is a thread here somewhere which shows how to do this.
The boot.img I shared above is for people who need it for Magisk and saves them downloading the ~2GB factory file.

Hi.
Is "10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)" ok for the pixel 4 xl unlocked ?

wonderlander17 said:
Hi.
Is "10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)" ok for the pixel 4 xl unlocked ?
Click to expand...
Click to collapse
Affirmative :good:

dang is it that hard to understand . if youre build number does not look exactly like this QQ2A.200305.003 then do not use these boot.img's
its that simple this is not to upgrade you to the march sec patch with root this is for people already on the march sec patch to use to gain root

FIXED IT!! After taking the March update I flashed this patched img the phone boots up to a black screen. If you use the power button it brings up a White menu with "power off" "restart". So then I turn the phone off and load fastboot and flash the stock boot img and everything works again. Any ideas? Figured it out.... Magisk modules that were running.

Can you flash any of them without the use of a computer?

mydjtl said:
Can you flash any of them without the use of a computer?
Click to expand...
Click to collapse
Nope. TWRP or any other recovery is not yet compatible.

mydjtl said:
Can you flash any of them without the use of a computer?
Click to expand...
Click to collapse
Yes with ex kernel manager it's possible

Here's an updated patched March 2020 QQ2A.200305.003 boot image with Magisk 20.4.
I've been using it for the last 2 days and haven't noticed any problems as of yet. Couldn't direct install in Magisk Manager, so feel free to use this if it makes things any easier. OP, please feel free to add this link to your post if you want.
https://www.androidfilehost.com/?w=files&flid=306923

i5lee8bit said:
Here's an updated patched March 2020 QQ2A.200305.003 boot image with Magisk 20.4.
I've been using it for the last 2 days and haven't noticed any problems as of yet. Couldn't direct install in Magisk Manager, so feel free to use this if it makes things any easier. OP, please feel free to add this link to your post if you want.
https://www.androidfilehost.com/?w=files&flid=306923
Click to expand...
Click to collapse
Added to OP, cheers

Magisk crashing when trying to patch boot.img (March Patch)

As the title says, Magisk crashes when I try to patch the boot.img after installing the latest March security patch on my Pixel 3a.

You are right, wait for a fix at
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
In the meantime, I did go back to the February security patch...

biontx said:
You are right, wait for a fix at
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
In the meantime, I did go back to the February security patch...
Click to expand...
Click to collapse
Thanks for letting me know, should've checked the Magisk Canary thread first ^^
However, I get into a bootloop when I try to downgrade back to the February patch. Guess I'll just wait it out...

I'm on the March patch as well and I was able to successfully patch the boot.img using the lastest magisk manager.

NinjaCoool said:
I'm on the March patch as well and I was able to successfully patch the boot.img using the lastest magisk manager.
Click to expand...
Click to collapse
That's weird. How did you update? Magisk OTA, sideload OTA or flashing March factory image?
In any case, would you mind sharing your patched boot.img? I'm not sure I want to live without root until they fix it ^^
EDIT: Scratch that, it seems that flashing a prepatched boot.img causes a bootloop. They probably changed something in the files, that causes the issues when flashing the factory image.

I had the same issue with crashing while patching. I had to install MagiskManager 7.5.1 from the xda forum. After that patching succeeded.

AndDiSa said:
I had the same issue with crashing while patching. I had to install MagiskManager 7.5.1 from the xda forum. After that patching succeeded.
Click to expand...
Click to collapse
But 7.5.1 is the stable/beta relase channel which doesn't even support Android 10 yet?! I can patch the boot.img with that, but it doesn't boot.

I had no problems applying the February update but I did it before it was available through system update. So I had to do it the long way - uninstalling magisk, downloading the update and installing it, downloading the boot image, patching it, and then installing the magisk patched boot image. It all worked fine though with no issues after the update.
My Magisk version is 20.3 and Magisk Manager is 7.5.1.

Velcorn said:
But 7.5.1 is the stable/beta relase channel which doesn't even support Android 10 yet?! I can patch the boot.img with that, but it doesn't boot.
Click to expand...
Click to collapse
If I remember correctly versions before 19.1 /7.3.x didn't support Android 10. For me 7.5.1 worked flawlessly.

yaconsult said:
I had no problems applying the February update but I did it before it was available through system update. So I had to do it the long way - uninstalling magisk, downloading the update and installing it, downloading the boot image, patching it, and then installing the magisk patched boot image. It all worked fine though with no issues after the update.
My Magisk version is 20.3 and Magisk Manager is 7.5.1.
Click to expand...
Click to collapse
Weird, thanks for letting me know. I manually updated through flashing the March factory image and when I patch the boot.img through MM 7.5.1 I just get into a bootloop.

I did the sideload. 7.5.1 beta. Patched ok. Flashed ok all set for another month.

dkryder said:
I did the sideload. 7.5.1 beta. Patched ok. Flashed ok all set for another month.
Click to expand...
Click to collapse
Could you upload your patched boot.img please?

It said file too large when I tried. It's about 30MB. Not sure what's up with that.

Latest magisk from topjohnwu's github set to beta update channel, March update straight from Google, bootloader unlocked. Patched with magisk 1st time, and flashed via fastboot. Booted first time.
Not sure what to advise, just wanted to let you know that it does work with the latest versions of both magisk and firmware. Did you enable adb and enable OEM unlock in Developer Options?
---------- Post added at 01:19 AM ---------- Previous post was at 01:01 AM ----------
biontx said:
Could you upload your patched boot.img please?
Click to expand...
Click to collapse
here you go mate, Pixel3a (Sargo) March firmware straight from google, patched and confirmed working.
http://bit.ly/sargobootpatchedmarch
MD5: d69ee45e403b5bcf24c43cacf31cb7c2

captain sideways said:
Latest magisk from topjohnwu's github set to beta update channel, March update straight from Google, bootloader unlocked. Patched with magisk 1st time, and flashed via fastboot. Booted first time.
Not sure what to advise, just wanted to let you know that it does work with the latest versions of both magisk and firmware. Did you enable adb and enable OEM unlock in Developer Options?
---------- Post added at 01:19 AM ---------- Previous post was at 01:01 AM ----------
here you go mate, Pixel3a (Sargo) March firmware straight from google, patched and confirmed working.
http://bit.ly/sargobooypatchedmarch
MD5: d69ee45e403b5bcf24c43cacf31cb7c2
Click to expand...
Click to collapse
Super, tx

Is anyone else having issues with Safetynet CTS after the latest security patch? For some reason it doesn't work for me anymore. I haven't made any other changes.

captain sideways said:
Latest magisk from topjohnwu's github set to beta update channel, March update straight from Google, bootloader unlocked. Patched with magisk 1st time, and flashed via fastboot. Booted first time.
Not sure what to advise, just wanted to let you know that it does work with the latest versions of both magisk and firmware. Did you enable adb and enable OEM unlock in Developer Options?
---------- Post added at 01:19 AM ---------- Previous post was at 01:01 AM ----------
here you go mate, Pixel3a (Sargo) March firmware straight from google, patched and confirmed working.
http://bit.ly/sargobooypatchedmarch
MD5: d69ee45e403b5bcf24c43cacf31cb7c2
Click to expand...
Click to collapse
Thanks for the effort. Still ends in a bootloop for me. Guess it's time for a fullwipe...

Velcorn said:
Thanks for the effort. Still ends in a bootloop for me. Guess it's time for a fullwipe...
Click to expand...
Click to collapse
Sorry it didn't help, thanks for letting me know though, but I'm out of ideas now

MeowDotEXE said:
Is anyone else having issues with Safetynet CTS after the latest security patch? For some reason it doesn't work for me anymore. I haven't made any other changes.
Click to expand...
Click to collapse
Me too. It's the first time now with the March update.
"cts profile: false"

Made an account to say I had the same problem with Pixel 3XL and I did what captain sideways posted. I went to the github for magisk, took the apk from the latest zip file release and installed that. I was able to patch my boot image afterwards. Root works fine. I flashed the patched boot image to both slots. However, the ctsProfile does fail like mentioned above.

Magisk 23.0 compatible with newest stock image RQ3A?

Hi,
I tried to patch the newest stock image 11.0.0 (RQ3A.210705.001, Jul 2021) with Magisk 23.0. Patching of boot.img looks ok, at least it does not complain. Then I flashed the patched image (or booted from it directly, to test).
The boot works, but Magisk does not detect any installation. It wants to install the full app, and then displays "Install n/a".
Did Google change anything which breaks Magisk? If so, is there a safe way to downgrade the phone without loosing data?
Best Regards

So I'm running a Pixel 5 currently, but it sounds like after booting to your patched image, you just need to go grab the Canary version of Magisk from the official GitHub: Magisk 23 Official GitHub.
I've had this happen too after flashing the patched boot image and rebooting back to homescreen.
If you don't install the apk separately it'll try to install Magisk on it's own, but doesn't usually have success in doing so, at least in my experience. So just download the APK from the official GitHub or try the Canary version of Magisk 23. After installing the APK you should be good to go!
If I'm not mistaken, you can grab the APK there or try the "stub-release.apk" for a direct "Canary" version.
The reason I mention the Canary version is because it's like an updated beta, but I've had a lot of success running it myself (Pixel 2XL and Pixel 5).

irxvus said:
Hi,
I tried to patch the newest stock image 11.0.0 (RQ3A.210705.001, Jul 2021) with Magisk 23.0. Patching of boot.img looks ok, at least it does not complain. Then I flashed the patched image (or booted from it directly, to test).
The boot works, but Magisk does not detect any installation. It wants to install the full app, and then displays "Install n/a".
Did Google change anything which breaks Magisk? If so, is there a safe way to downgrade the phone without loosing data?
Best Regards
Click to expand...
Click to collapse
The July release works fine with Magisk. Did you have Magisk installed before updating to the July release? If so, did you hide the Magisk app? In that case, you'll have to unhide the app, remove both instances, and reinstall.
If that is not the case, just complete the install as @ProjectAlly said. There is no need to use Canary, though. Currently Canary and Stable are the same.