Dear Team,
When I try to patch the AP file there is an error and it says: "Process error installation failed" , both canary and magisk 24.1 are used in the process
phone info:
android 12, one ui 4.0 (firmware downloaded and flashed 12 hrs ago on my s21 phone)
s21 5g (sm-g991b/ds)
AP filename that iam trying to patch: AP_G991BXXU4BULF_G991BXXU4BULF_SCL23365054_VCL23364085_MCL23373251_SQB47608375_VQB47608374_MQB47608349_REV01_user_low_ship_MULTI_CERT_meta_OS12.tar.md5
see screenshot, please help. thank you.
In my case, when I click the update button while on Canary 23016, Magisk Manager simply evaporates with no error, no log. I'm going to try patching a boot image. I have the January update, Pixel 6 stock.
Kenaz Rune said:
In my case, when I click the update button while on Canary 23016, Magisk Manager simply evaporates with no error, no log. I'm going to try patching a boot image. I have the January update, Pixel 6 stock.
Click to expand...
Click to collapse
So, it turned out to be a bit of a confusing UI "language". I had the 24.1 app installed, but it had an update button next to it. The Magisk library had the typical "install" button rather than "update". I clicked install and was able to proceed normally.
Edit: Spoke too soon. It updated, and I rebooted, but it still showed the Canary. I finally had to delete the app (which was still actually the canary version, but crashed on update) and install the new APK. After reboot.... The proper version is now applied - 24.1.
Whew!
Related
Rooted Pixel 2XL 9.0
No TWRP
Upgraded Magisk to 7.2 - get error, "Unsupported Magisk Version"
trying to upgrade to 19.x manually, but all guides say, "Then go open Magisk on your phone", which I can't do.
If I downgrade to 6.x, I cannot upgrade to 19.x. So what to do?
Apologies if this has been addressed, but I cannot find a solution
With your old version of Magisk and Manager installed, download the the update and flash it manually from the modules section (the "+" button).
Didgeridoohan said:
With your old version of Magisk and Manager installed, download the the update and flash it manually from the modules section (the "+" button).
Click to expand...
Click to collapse
did that, and ended up in a boot loop.
It would seem that with version 6.x, (or anything lower than 7.x), you can't upgrade to 18.x or higher. I tried this 2-3x and same result. Had to flash old patched_boot.img and was back where I started.
The Manager version shouldn't really matter when installing like that (it is a known working solution for your exact problem). You might have a module acting up and causing issues. Might be a good idea to uninstall Magisk and start out clean.
Booting TWRP and flashing the Magisk zip there could also be a thing to try.
Walsh_M said:
did that, and ended up in a boot loop.
It would seem that with version 6.x, (or anything lower than 7.x), you can't upgrade to 18.x or higher. I tried this 2-3x and same result. Had to flash old patched_boot.img and was back where I started.
Click to expand...
Click to collapse
I tried again, and it worked
1. I downgraded to 6.1 and when prompted to reboot, I just closed, and restarted.
2. I then upgraded to 18.1. Again, when prompted to reboot, I closed and then restarted manually.
There seems to be a bug with regard to rebooting straight from upgrading.
It's only a bug if you can consistently reproduce it, and preferably provide logs showing it happening. Until then it was just gremlins...
After November's system update, I followed the guide rooted my Pixel 5 and pass SafetyNet. But I can not receive OTA update, here is my original post.
Yesterday, I found a Magisk module - Universal SafetyNet Fix, here is the post. First, I modified the build.prop from Pixel 3 back to default Pixel 5 by MagiskHide Props Config. Then I install Universal SafetyNet Fix 1.1 module. After the restart, "Check SafetyNet" Success.
I checked system update, it's back! I uninstall Magisk (restore image), then start the system update. Before restart, back to Magisk install. But there is no option for "install to inactive slot". I googled what's happened here. So I have to "Direct Install". After restart, as I guess, Magisk and root both fine, but the system update still let me restart to apply. So this time I restart directly without uninstalling Magisk. This time, the system update to December, Magisk still installed but root is not available. I check system update again and update to the latest January patch.
Then followed the regular steps, I patch the latest Stock Boot image, then flashflash the patched image to my phone. Module and root back again.
So i was minding my own business then i notice "Magisk Manager" have red dot notification on it's icon upon opening there's update for "Magisk Manager" app and "Magisk" itself... so i decided to first Install the "Magisk Manager" update and it went real smooth
but when i try to update Magisk itsaid "Magisk Manager is Dead. Love live the Magisk app" then it ask me for Method
"Select and Patch file" or "Direct Install" now at this point idk what to do. I have at least done 3x Magisk update installation already it never ask me this option also when i try download root checker on playstore itsaid im rooted i just want to update Magisk should i patch my stock boot.img again or what??
For me this has been the case all this time for Magisk updates - I get that choice, and I choose 'direct install'. This time also I chose the same - 'direct install'. It got installed and prompted me to reboot.
scarmage said:
For me this has been the case all this time for Magisk updates - I get that choice, and I choose 'direct install'. This time also I chose the same - 'direct install'. It got installed and prompted me to reboot.
Click to expand...
Click to collapse
clicking Direct Install doesn't do anything
This is what my Magisk Manager look like before i update it to v22.0
https://ibb.co/gvPzDs7
Now after i update it to Magisk Manager V22.0 i can't update Magisk
https://ibb.co/HXLCvLS
You can try going to the Magisk GitHub and download the app and install it through file manager and try updating again. I did that accidentally and had no issues installing.
dl200010 said:
You can try going to the Magisk GitHub and download the app and install it through file manager and try updating again. I did that accidentally and had no issues installing.
Click to expand...
Click to collapse
I have the app already but after they decided to merge Magisk Manager and Magisk in just one apps i can't update Magisk anymore also i have stock boot.img of my device that i have previously patched via Magisk so it's just unusual for Magisk Manager to ask me again ...
ineedroot69 said:
I have the app already but after they decided to merge Magisk Manager and Magisk in just one apps i can't update Magisk anymore also i have stock boot.img of my device that i have previously patched via Magisk so it's just unusual for Magisk Manager to ask me again ...
Click to expand...
Click to collapse
I downloaded the apk from GitHub and installed it over the updated one. I was able to do a direct update. I was just suggesting it. Couldn't hurt to try it.
dl200010 said:
I downloaded the apk from GitHub and installed it over the updated one. I was able to do a direct update. I was just suggesting it. Couldn't hurt to try it.
Click to expand...
Click to collapse
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
PrussianWolf said:
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
Click to expand...
Click to collapse
Can you tell more? How did you extract the boot.img? Did you get it from the newest Android full OTA? DId it just straight up work after flashing the new boot.img? I'm asumming it was an unpatched one, right?
PrussianWolf said:
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
Click to expand...
Click to collapse
How do I flash a ROM from bootloader? I am on Xiaomi Redmi Note 4 (mido) and have the same issue. Device won't boot into anything except fastboot. I tried flashing recovery using fastboot flash recovery <reccovery>.img but it got stuck in bootloop again.
ineedroot69 said:
This is what my Magisk Manager look like before i update it to v22.0
https://ibb.co/gvPzDs7
Now after i update it to Magisk Manager V22.0 i can't update Magisk
https://ibb.co/HXLCvLS
Click to expand...
Click to collapse
Exactly the same experience as OP here.
I am at exactly this stage as well..oneplus 6T; rooted; stock image.
Not sure what to do next?
Thanks in anticipation.
~S.O
where is the "Download zip only" option ?
VangelisGi said:
where is the "Download zip only" option ?
Click to expand...
Click to collapse
There isn't one, because there is no separate zip anymore:
https://topjohnwu.github.io/Magisk/releases/22000.html
Why?
I'm so confused.
I'm on Lineageos 17 on Oneplus 6
I used to install magisk with the zip and it went smoothly now I don't have the option anymore..
How can you do when you use OTA update?
Cygnust said:
Why?
I'm so confused.
I'm on Lineageos 17 on Oneplus 6
I used to install magisk with the zip and it went smoothly now I don't have the option anymore..
How can you do when you use OTA update?
Click to expand...
Click to collapse
It's all explained in the link posted right above your post...
Spoiler: rename the .apk to .zip.
Didgeridoohan said:
It's all explained in the link posted right above your post...
Spoiler: rename the .apk to .zip.
Click to expand...
Click to collapse
Sorry, I skipped that part and when directly to the one saying you had to patch BOOT.IMG..
Many thanks
Didgeridoohan;
I understand that the 'Manager' now has become the 'App'. I also understand to just rename the '.apk' file to '.zip' to flash from an OTA update event. I also understand that the '.apk' now with this latest release has everything you need to install Magisk.
I have had Magisk already installed like this: https://ibb.co/gvPzDs7
So, after I updated, can I ask what do I do about the problem of 'update' indicating via the Magisk Home page on the App?
I mean now I have this: https://ibb.co/HXLCvLS
Just don't worry about it?
Thank-you for your help.
sprocketoctopus said:
Didgeridoohan;
I understand that the 'Manager' now has become the 'App'. I also understand to just rename the '.apk' file to '.zip' to flash from an OTA update event. I also understand that the '.apk' now with this latest release has everything you need to install Magisk.
I have had Magisk already installed like this: https://ibb.co/gvPzDs7
So, after I updated, can I ask what do I do about the problem of 'update' indicating via the Magisk Home page on the App?
I mean now I have this: https://ibb.co/HXLCvLS
Just don't worry about it?
Thank-you for your help.
Click to expand...
Click to collapse
Magisk still consists of two parts, Magisk app and Magisk internals, they're now just distributed together.
What your screenshot shows is that you've now updated the app, but not yet the internals...
Do not update simply as the update is Device bricking.
Magisk 22.0 update killed phone will only boot into fastboot
Have never had an issue went to update to latest Magisk app, followed directions and restored it first, everything seemed fine, then went to flash Magisk itself from the app (Direct install) like always, didn't seem to do anything, checked the...
forum.xda-developers.com
I updated my magisk to version 22, and it looks ok, except for the bottom menu that disappeared, does anyone know where it went or is it a bug?
Trying to update magisk via direct install using latest magisk manager v23 on rooted S10 on pie.
View attachment 5351001
Install goes well according to this ^
But when I hit reboot, and then hold down power+bixby+vol-up to get back into root mode, it always gives this error when starting magisk app
View attachment 5351005
So the update fails every time.
Since Magisk Manager v23 wont even show the current magisk version- upon downgrading to MM 8.0.7, we see that it never upgraded magisk past 19.4 (19302)
Also the "additional setup" never completes when we try that from 8.0.7, fyi, and the Update button is greyed out too.
View attachment 5351007
What is the next step to getting magisk 20.4+ working with a recent version of the app?
Thanks!
Since upgrading LineageOS on my Moto G7 to Android 13 and Magisk to 25.2 I had to reinstall patched boot.img after every update. It was a bit of a PITA, but not painful enough to google if there's a solution for Magisk to survive the LineageOS update, like it did before. It worked just well enough for me.
After today's LineageOS update I was going to do all the usual stuff: download boot.img, patch, fastboot, flash and done. But there was an info about the new Magisk version. Updated to 26.1, patched my boot.img, rebooted to fastboot, flashed the patched image. But after the restart Magisk says it's not installed. I tried 2 more times, then downgraded Magisk back to 25.2, but it doesn't work any more - nothing happens after patching and flashing the patched image.
I checked the Magisk installation instruction, but there's nothing about changes in 26.1 What can I do to get Magisk work again?
Debug app did what regular Magisk could not:
Uninstalled Magisk app. Flashed the stock boot image. Installed Magisk debug app and patched boot.img. Flashed the patched file. Opened the debug app and finished the installation. Updated Magisk app and Magisk. It works now.
I have no idea why did the debug version succeed, where the regular one failed, but I'm happy it did
For me on Samsung S7 9.0 Pie NFE 2.2, after flashing the Rom clean, after configuring the phone, I go to TWRP and upload Magisk_26.1.zip and every time in the Magisk app it says "root is not installed" . I tried several times and each time the same, I found a solution, after flashing the NFE Rom clean, phone configuration, then installs the Magisk_26.1.apk application on the phone (I do not open Magisk), then I change Magisk_26.1.apk to Magisk_26.1.zip, go to TWRP and install the Magisk zip file, reboot and ? "root Magisk installed"
I can't find the debug version of the app. Where is it?
Havock2 said:
I can't find the debug version of the app. Where is it?
Click to expand...
Click to collapse
It's on GitHub.
da.killa said:
It's on GitHub.
Click to expand...
Click to collapse
@da.killa I looked everywhere in the current Magisk GitHub Repo, but could not finde the debug version as an .apk file.
Could you share the direct Link to the Debug App?
xte41778 said:
@da.killa I looked everywhere in the current Magisk GitHub Repo, but could not finde the debug version as an .apk file.
Could you share the direct Link to the Debug App?
Click to expand...
Click to collapse
This is the URL behind that link on github.com:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
WoKoschekk said:
View attachment 5910161
This is the URL behind that link on github.com:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Click to expand...
Click to collapse
@WoKoschekk
Thank you so much! Sorry I didn't see it before.
And I can also confirm that using the Magisk debug app solves the problem. It worked for me on OnePlus 6 running LineageOS.