Database Develop

Magisk v15.2 not installing

Hello
Okay i flashed my mobile with new OTA
after i try to install magisk but getting error that "Magisk manager stopped" after zip downloaded
i dont know why that happening
after zip downloaded getting black window then pop up shown about error
i think it cant patch boot img properly
in my old rom it works properly, but after flashing it did not work
thank you....

Try installing it in recovery

I sometimes get that majisk stopped toast on just about any ROM and just about any majisk release. I just ignore it. I have no idea of the what or why. Haven't noticed it affecting anything.

Yes. It's happening to me too. Does it work if I flash this update with twrp?

rabin69x said:
Yes. It's happening to me too. Does it work if I flash this update with twrp?
Click to expand...
Click to collapse
Did you read the responses above? It was already suggested to try that.

After installing magisk 15.2, magisk manager 5.5.3 stuck at the splash screen for me. What's wrong ?

rabin69x said:
Yes. It's happening to me too. Does it work if I flash this update with twrp?
Click to expand...
Click to collapse
I always flash builds from TWRP.

Eng.Raman said:
After installing magisk 15.2, magisk manager 5.5.3 stuck at the splash screen for me. What's wrong ?
Click to expand...
Click to collapse
Having the exact same issue on a pixel xl. Tried on 7.1 and 8.1, both with the same result.

I never use manager. Always TWRP, and can people start searching and using the support thread for questions, logs, and bugs instead of keep making a hundred useless threads of the same thing, can't install, can't install modules, etc. That's what support thread for. Thanks.

I am using MIUI 7.12.28 (latest) on Redmid 3S and I can flash magisk 15.2 using TWRP normally but when the phone restart, i go to magisk manager and it shows that magisk is not installed
I tried flash many time but the same problem happen
When i tried to flash magisk 14.0, it works. what is the problem here o_o

hungragezone said:
I am using MIUI 7.12.28 (latest) on Redmid 3S and I can flash magisk 15.2 using TWRP normally but when the phone restart, i go to magisk manager and it shows that magisk is not installed
I tried flash many time but the same problem happen
When i tried to flash magisk 14.0, it works. what is the problem here o_o
Click to expand...
Click to collapse
If updating, why not use direct method?

madbat99 said:
If updating, why not use directethod?
Click to expand...
Click to collapse
No, i am flashing from start
I just flash new miui (full wipe, factory reset)
and i also try to update from Magisk manager but when the flash screen appear, magisk manager force close (I already tried to clear data of Magisk manager and tried to update again but no success)
Now i can have root with Magisk 14.0 but when i tried to update to 15.2 using TWRP, it just disappear lol
(Flashing normally, no error, restart phone, go to magisk manager -> magisk is not installed )

Can't update magisk to v17

I try and install directly from magisk but when I go and flash the zip through app it says installation failed. Am I doing something wrong?

Me too
I try unistall magisk in recovery but non success
I'm blocked
Edit: i'm return at v16.6 and work
I don't update for Now Walt for more info

Ty for now I'll wait

same here
Edit:- can't go back to v16.0 either,i'm getting "updater process ended with ERROR: 1
Any suggestions?

1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.

Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
If I don't have TWRP I just install it? Sorry for noob question but i'm new here

Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
Thanks mate,worked for me.

Hi,
I'm running a HTC 10 with Lineage OS 15.1 (8.1.0). I came from Magisk 16 and an update message appeard. I downloaded Magisk 17 and tried to install it via TWRP as usual. The installation stopped with an Error 2. After that I had a boot loop and had to reinstall the Lineage OS. After that it booted again. But I still get this error message when trying to install Magisk 17.
Very odd. Besides of that, GREAT WORK!
Cheers

lmrcarneiro said:
If I don't have TWRP I just install it? Sorry for noob question but i'm new here
Click to expand...
Click to collapse
Magisk uninstaller will not works without custom recovery so i think my instruction is not applicable in this situation.
chaos_since_78 said:
Hi,
I'm running a HTC 10 with Lineage OS 15.1 (8.1.0). I came from Magisk 16 and an update message appeard. I downloaded Magisk 17 and tried to install it via TWRP as usual. The installation stopped with an Error 2. After that I had a boot loop and had to reinstall the Lineage OS. After that it booted again. But I still get this error message when trying to install Magisk 17.
Very odd. Besides of that, GREAT WORK!
Cheers
Click to expand...
Click to collapse
Double check if the package is not corrupted, MD5 should be: 6237bfaf7dcf516b60922b5b26f2dca8.

Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
Thanks for this
but now i can't install universal fix for safetynet check

I'm not sure if Magisk v.17.0 is fully backward compatible. Maybe this is preventing the module from installing?

Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
thank you very much i installed twrp and followed your steps worked great

Karls0 said:
I'm not sure if Magisk v.17.0 is fully backward compatible. Maybe this is preventing the module from installing?
Click to expand...
Click to collapse
ok so wait for new fix thanks

On my pixel 1 it claims to install, but causes a bootloop. AND updating to the most recent manager breaks using v16. So I'm stuck with an old manager and v16

Yes, the new manager seems to not fit to Magisk v16. In my case it also broke something so I updated to v17.

Karls0 said:
Magisk uninstaller will not works without custom recovery so i think my instruction is not applicable in this situation.
Double check if the package is not corrupted, MD5 should be: 6237bfaf7dcf516b60922b5b26f2dca8.
Click to expand...
Click to collapse
I got it solved by uninstallion the former Magisk package with the uninstaller. After reboot I could reinstall version 17 and until now it works fine. Thanks.

uninstaller for me does not flash for me. error 255 v16 same error and 17.1 wont flash either error 2

Thanks.
I'm able to do the steps without error. But then it is in bootloop. Using redmi note 4g (dior) Dot os

adz63 said:
uninstaller for me does not flash for me. error 255 v16 same error and 17.1 wont flash either error 2
Click to expand...
Click to collapse
Have you tried rebooting TWRP when the errors appear, and where are the logs?
barathrr96 said:
Thanks.
I'm able to do the steps without error. But then it is in bootloop. Using redmi note 4g (dior) Dot os
Click to expand...
Click to collapse
Is this on a clean install of Magisk v17.1? Also, logs...

Didgeridoohan said:
Have you tried rebooting TWRP when the errors appear, and where are the logs?
Is this on a clean install of Magisk v17.1? Also, logs...
Click to expand...
Click to collapse
Thanks.. the device does not belong to me..
for the time being I have installed magisk v16.7 and did installed viper and removed it ..
so when I get the device next time in my hand I will try to flash and take logs..

Error while installing Magisk through Magisk manager

I'm trying to instal Magisk 19.3 through Magisk Manager Version: v7.3.4
and getting this error:
Device platform: arm64-v8a
Coping image to cache
unpacking boot image
!unsupported/unknown image format
!installation failed
Any ideas how to solve it?
I have used Stable Magisk Version: v19.3 (also tried Beta Magisk Version: v19.4)

Maybe something's wrong with the boot image? Try to re-download magisk stable zip and reintall it via TWRP.

@LogicalMaverick, tried to download it again from this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 but still the same error message
I did try to install in TWRP mode and also from the Magisk Manager and still not working.
When I install in TWRP mode the result is the phone is getting into loop mode and the only way out if it is to uninstall it

try to wipe data after flashing magisk before booting to system

Kzak25 said:
try to wipe data after flashing magisk before booting to system
Click to expand...
Click to collapse
Yeah, for me there are 2 ways:
1. Wipe data after flashing magisk before booting system
2. Complete phone setup first after installing new ROM, and then boot into recovery, then you're good to install magisk

Kzak25 said:
try to wipe data after flashing magisk before booting to system
Click to expand...
Click to collapse
Didn't work. Still getting to the same issue where the phone is stuck in bootloop and the only way out of it is to uninstall Magisk

What phone are you using?

cohenelad said:
Didn't work. Still getting to the same issue where the phone is stuck in bootloop and the only way out of it is to uninstall Magisk
Click to expand...
Click to collapse
are you on stock or custom ROM (if stock what MIUI Ver)

Kzak25 said:
are you on stock or custom ROM (if stock what MIUI Ver)
Click to expand...
Click to collapse
I'm on stock ROM.
Was on MIUI 10.3.2 Now I'm on 10.4.8.
Tried to install Magisk on bot ROM through TWRP and didn't work.
Tried also through Magisk manager and didn't work
When I installed TWRP on my phone it asked if I want to give it permission to modify the system or to leave it read only mode.
I choose read only mode as I thought it will be easier to get OTA updates.
Maybe that's the reason Magisk cannot be installed correctly ?
TIA for your help

cohenelad said:
I'm on stock ROM.
Was on MIUI 10.3.2 Now I'm on 10.4.8.
Tried to install Magisk on bot ROM through TWRP and didn't work.
Tried also through Magisk manager and didn't work
When I installed TWRP on my phone it asked if I want to give it permission to modify the system or to leave it read only mode.
I choose read only mode as I thought it will be easier to get OTA updates.
Maybe that's the reason Magisk cannot be installed correctly ?
TIA for your help
Click to expand...
Click to collapse
Yeah i think you should give TWRP all permission when you boot into it the first time
you can re-flash TWRP and try again

reboots to fastboot
Kzak25 said:
Yeah i think you should give TWRP all permission when you boot into it the first time
you can re-flash TWRP and try again
Click to expand...
Click to collapse
I can flash over twrp. then it says no rom installed so flash over magisk-error unknown image. this is a fresh download tried 3 new downloads same error. use adb sideload to flash rom. successful do the reboot and it reboots to fastboot. what do i do

Magisk v22.0 update confusion

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?

Magisk not showing root after patching boot

I just patched boot.img using latest ver of magisk and flashed to device Samsung m01 core (android 10(Q) go edition)
Magisk simply showing all done!
But after flashing magisk_patched_boot
Application is not detecting root i ve repeated steps but no use still it showing device not rooted
Can anyone help me.
I ve tried same procedure on other devices it worked perfectly but i don't know what happened this time...

Problem solved. The hidden magisk just renamed it to magisk...

What?
Renaming magisk solves problem?
Did u mean rename apk file
My problem is magisk not detecting rooted boot.img or recovery.img that i ve flashed to my device

Wait, what.. I thought I replied to another post. Sorry

MasterGmind said:
I just patched boot.img using latest ver of magisk and flashed to device Samsung m01 core (android 10(Q) go edition)
Magisk simply showing all done!
But after flashing magisk_patched_boot
Application is not detecting root i ve repeated steps but no use still it showing device not rooted
Can anyone help me.
I ve tried same procedure on other devices it worked perfectly but i don't know what happened this time...
Click to expand...
Click to collapse
Which magisk version?

Selvam_2568 said:
Which magisk version?
Click to expand...
Click to collapse
Here is the solution...(It will work for all magisk versions)
1.Uninstall magisk manager.
2.Reboot to twrp recovery. Then Advanced > File manager > /data/adb/
3.Delete the "adb" folder which present inside the /data.
4.Restore stock boot.img
5.Now flash magisk via recovery...it will work now.