Database Develop

Magisk v17 Failed to Install

I attempted to go from Magisk v16 to Magisk v17 from the app, Install > Patch Boot Image File > Magisk-v17(1700).zip and I get the below .
I opened up Root Checker and it let me know that the device no longer has Root.
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
! Installation Failed
Magisk Log File
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
boot_patch.sh[73]: can't create /proc/self/fd/: Is a directory
MagiskBoot v17.0(17000) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
! Installation failed
Device Stats
Nexus 6P
Lineage 15.1
TWRP - latest
Any help would be greatly appreciated.

monteie2016 said:
I attempted to go from Magisk v16 to Magisk v17 from the app, Install > Patch Boot Image File > Magisk-v17(1700).zip and I get the below .
I opened up Root Checker and it let me know that the device no longer has Root.
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
! Installation Failed
Magisk Log File
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
boot_patch.sh[73]: can't create /proc/self/fd/: Is a directory
MagiskBoot v17.0(17000) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
! Installation failed
Device Stats
Nexus 6P
Lineage 15.1
TWRP - latest
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Happened with me also...i gues the only solution is you have to uninstall mafisk via magisk uninstaller and flash it once again via whatever recovery you are using...i am also using lineage os 15.1 but with RN4....

Happened to me as well. HTC u11, ViperU 1.8.0, Android 7.1.1, TWRP 3.2.2. Tried flashing it though TWRP got a bootloop. Had to revert back to my previous nan which luckily I made yesterday.

I attempted the same, now my galaxy s6 is in a boot loop

Look other posts in this section - you should flash latest uninstaller before Magisk v17 package. It seems that some residues from v16 prevent v17 from installing correctly.

^^^^^^^^^^

how to uninstall magisk completely without custom recoery

Hello Guys
I can not install Magisk v17.1
I delete it complete with the uninstaller
And then flashed again in TWRP, but dont work
Magisk icon is not visible and I can not manually install the Magisk Manager
Pls Help

edkmho said:
how to uninstall magisk completely without custom recoery
Click to expand...
Click to collapse
I had to reflash stock (OTA sideload version, in stock recovery) via adb sideload. Essential phone. Wifi is working now, didn't lose any data.

I'm also having the issue on my OnePlus 5T. I was running v16.0, and when I tried to flash the v17.1 zip in TWRP like usual, but it said zip signature verification failed. I flashed the Magisk uninstaller zip and tried again, but still had the same problem. I've lost root, but all my data is still intact and it never had boot issues.

After using uninstaller in recovery, restart into recovery to flash v17

aydinbahadir88 said:
And then flashed again in TWRP, but dont work
Magisk icon is not visible and I can not manually install the Magisk Manager
Click to expand...
Click to collapse
Do you update from 16.0? If Yes test following:
Download the seperate MagiskManager-v5.9.1.apk
Make sure that you adb is working, connect your phone to computer
Code:
adb devices
must show your phone, if not adb is not proper set
Code:
adb install MagiskManager-v5.9.1.apk
if you get a error message like
the sign with the installed apk has not matsched..aborted
Click to expand...
Click to collapse
the uninstaller not proper delete the old magisk manager
try
Code:
adb uninstall com.topjohnwu.magisk
the result must be an sucess
then again
Code:
adb install MagiskManager-v5.9.1.apk
result must also sucess
Reboot, voiala its done....
You see the Magisk Manager

Does anyone have a working solution?

1.download magisk 17.zip from inside magisk 16
2. uninstall magisk 16 (i do from inside, not twrp)
3. instal magisk 17.zip from twrp
4. open magisk 17 and get notification for downloaded magisk 17.apk
5. download and instal it,
tested by my phone
mi5 Lineage Os 15.1

How I recovered from this on a Pixel 2 XL
I'll chime in with my experience here, as it might save someone else a lot of time if they are at my skill level with this stuff (which is only moderate, I suppose, although I do always get things to work eventually!).
As of yesterday, I had a Pixel 2 XL, rooted with Magisk, and working great. This morning, during the middle of the night, Magisk innocently asks if I want to upgrade to a new version. I was very tired (in fact, I think I was sleeping when my phone buzzed to alert me of the upgrade message) and don't even know how I responded except that it was "yes" to the upgrade part. By the time I'd fully awakened, I had a phone that waw in a boot loop. I went back to sleep, figuring I'd have better luck looking at it after a little rest.
Getting out of the boot loop was easy: I just reinstalled the August 2018 factory image for the phone. However, getting Magisk reinstalled was an adventure. I saw posts that said I should run the Magisk uninstaller, but when I did it just said that Magisk was already uninstalled. And yet, whenever I tried to apply either v16.0 or v17.1, I got errors (error codes 1, 2, and 255 at different times).
Up until this event, I'd always upgraded Magisk by installing it via TWRP. However, that was not working, so I thought I needed to try patching the boot image, something I'd never done before. Because I'd never done it before, it took me a while to understand the steps, which are actually quite simple. This is where I'm hoping I might save someone some time. Basically, my fear was not knowing which file the "boot image" was. Seasoned Android veterans might get a chuckle out of this, and that's fine, but I was looking at the file in the factory image download and basically saw only two image files: bootloader-taimen-tmz20j.img and radio-taimen-g8998-00253-1805232234.img. I was trying to figure out if either of those could be the boot image, and they both seemed pretty big to be a boot image! Finally it dawned on me that the much larger file in the directory was a zip archive (named image-taimen-ppr1.180610.009.zip). I looked inside there, and sure enough, there was a rather small file named boot.img. I was pretty sure that was the "boot image" file!
Here's what I did after that, again just hoping to help anyone who finds themselves in the same predicament I was in: Magisk is broken, root isn't working, and I can't install any of the Magisk *.zip images via TWRP.
- First, I downloaded a copy of Magisk Manager: this version is named MagiskManager-v5.9.1.apk.
- Next, I ran a couple adb commands to send the Magisk Manager apk and the stock boot.img to my phone:
Code:
adb push MagiskManager-v5.9.1.apk /sdcard/Download
adb push boot.img /sdcard/Download
- Next, I installed /sdcard/Download/Magisk-Manager-v5.9.1.apk by nagivating to it (I use ES File Manager) and launching it from there.
- Next I opened Magisk Manager
- Magisk Manager detects that there is a newer version available and asks if I want to upgrade
- I said yes
- I told it that I wanted to patch a boot image
- I chose /sdcard/Download/boot.img as the "unpatched" (stock) boot image
- Magisk Manager churned away for maybe half a minute and then produced a new file called patched_boot.img, saved in the same directory as boot.img.
After that, all I had to do was run these commands:
Code:
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot reboot
As soon as the phone restarted, I opened Magisk Manager again and it verified that its upgrade was successful, and root began working for me again also.
Like I said, I hope this helps someone else. If not, it's probably good for me to just write it all out anyway.
Cheers,
Sky Captain

_sky.captain_ said:
I'll chime in with my experience here, as it might save someone else a lot of time if they are at my skill level with this stuff (which is only moderate, I suppose, although I do always get things to work eventually!).
As of yesterday, I had a Pixel 2 XL, rooted with Magisk, and working great. This morning, during the middle of the night, Magisk innocently asks if I want to upgrade to a new version. I was very tired (in fact, I think I was sleeping when my phone buzzed to alert me of the upgrade message) and don't even know how I responded except that it was "yes" to the upgrade part. By the time I'd fully awakened, I had a phone that waw in a boot loop. I went back to sleep, figuring I'd have better luck looking at it after a little rest.
Getting out of the boot loop was easy: I just reinstalled the August 2018 factory image for the phone. However, getting Magisk reinstalled was an adventure. I saw posts that said I should run the Magisk uninstaller, but when I did it just said that Magisk was already uninstalled. And yet, whenever I tried to apply either v16.0 or v17.1, I got errors (error codes 1, 2, and 255 at different times).
Up until this event, I'd always upgraded Magisk by installing it via TWRP. However, that was not working, so I thought I needed to try patching the boot image, something I'd never done before. Because I'd never done it before, it took me a while to understand the steps, which are actually quite simple. This is where I'm hoping I might save someone some time. Basically, my fear was not knowing which file the "boot image" was. Seasoned Android veterans might get a chuckle out of this, and that's fine, but I was looking at the file in the factory image download and basically saw only two image files: bootloader-taimen-tmz20j.img and radio-taimen-g8998-00253-1805232234.img. I was trying to figure out if either of those could be the boot imag, and they both seemed pretty big to be a boot image! Finally it dawned on me that the much larger file in the directory was a zip archive (named image-taimen-ppr1.180610.009.zip). I looked inside there, and sure enough, there was a rather small file named boot.img. I was pretty sure that was the "boot image" file!
Here's what I did after that, again just hoping to help anyone who finds themselves in the same predicament I was in: Magisk is broken, root isn't working, and I can't install any of the Magisk *.zip images via TWRP.
- First, I downloaded a copy of Magisk Manager: this version is named MagiskManager-v5.9.1.apk.
- Next, I ran a couple adb commands to send the Magisk Manager apk and the stock boot.img to my phone:
Code:
adb push MagiskManager-v5.9.1.apk /sdcard/Download
adb push boot.img /sdcard/Download
- Next, I installed /sdcard/Download/Magisk-Manager-v5.9.1.apk by nagivating to it (I use ES File Manager) and launching it from there.
- Next I opened Magisk Manager
- Magisk Manager detects that there is a newer version available and asks if I want to upgrade
- I said yes
- I told it that I wanted to patch a boot image
- I chose /sdcard/Download/ as the "unpatched" (stock) boot image
- Magisk Manager churned away for maybe half a minute and then produced a new file called patched_boot.img, saved in the same directory as boot.img.
After that, all I had to do was run these commands:
Code:
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot reboot
As soon as the phone restarted, I opened Magisk Manager again and it verified that its upgrade was successful, and root began working for me again also.
Like I said, I hope this helps someone else. If not, it's probably good for me to just write it all out anyway.
Cheers,
Sky Captain
Click to expand...
Click to collapse
I too have a Pixel 2XL but had a much easier upgrade experience. I downloaded the latest version of Magisk files (3 files: MagiskManager-v5.9.1.apk, Magisk-uninstaller-20180901, and Magisk-v17.1 from here https://www.xda-developers.com/magisk-v17-1-android-pie-a-b-support/) and put them on my phone.
Rebooted into recovery TWRP run the Magisk-uninstaller-2018090 file, then ran Magisk-v17.1 rebooted and all worked (thanks to ALL the developers out there!!!)
I'm running rooted Pie (standard google Pie) with Rootchecker, 4.4.153-FlashKernal-Wahoo-v3.06, Greenify, AdAway, and of course Magisk 17.1.
Hope this helps.

akohle said:
After using uninstaller in recovery, restart into recovery to flash v17
Click to expand...
Click to collapse
flashed uninstaller in recovery
flashed v17
rebooted
it worked

If patch boot image is getting failed in magisk latest version v17.1 then enable storage permission for magisk app manually in Device/OS setting. Now patch boot image again, It will get patched successfully.

I
pierro78 said:
flashed uninstaller in recovery
flashed v17
rebooted
it worked
Click to expand...
Click to collapse
OK...im a relative newbie here...first post actually....but Im a bit stuck in a fastboot boot loop
LG G5 tmobile running fulmics
I decided to try this exact process to get my root back by updating Magisk
booted into TWRP through ADB
flashed uninstaller using TWRP
(cleared cache/dalvik)
flashed v 17.1 (not 17) using TWRP
(cleared cache/dalvik)
rebooted
now i'm stuck in fastboot bootloop….can reboot from fastboot but nothing else
any advice would be appreciated!
update: I am able to get to TWRP using reboot command and holding power and volume down. flashed uninstaller wiped cache/dalvik...rebooted into TWRP long way and then installed 17....still fastboot at startup again

Art1mis said:
If patch boot image is getting failed in magisk latest version v17.1 then enable storage permission for magisk app manually in Device/OS setting. Now patch boot image again, It will get patched successfully.
Click to expand...
Click to collapse
many thanks for the tip!!
spent like an hour trying to figure out why my pixel 2 was failing to patch the boot image.
Allowed storage permissions, flashed the patched boot and now im rooted

Android 4.2 and 4.4 Mediatek bootloop after installing Magisk 18.1

Hello everybody.
I've read that 18.1 supports 4.2+ so I've tried to install in two MTK6589T devices I've. One running 4.2, the other running 4.4
CMW/TWRP gave an error mounting system, so I mounted system manually and it started flashing. Firstly it detected old root installed and disabled the old root. But when it tried to find the boot, installation was aborted because installator claims cannot find the boot on both phones.
Then I though, okay, lets reboot back to android, I will try to install a few days later, maybe its buggy now, but both phones cannot boot.
I can easily fix them by flashing rom again I guess, but I would like to know where's the issue and also post it for more people could face the same problem.
Any idea where's the problem/how to fix without rom reflashing? I've tried magisk uninstaller but after mounting system in recovery it is also giving error.
Thanks
UPDATE: For now, if no other solution is found, bootloop can be bypassed by dirty installing the rom again. But it has to be an easier workaround...
We know now that the problem is caused because of two factors merging:
1- Using Magisk.zip installer through custom recovery
2-In the case that the custom recovery CMW/TWRP installed in the phone is very old (for instance, CMW automade for MTK6589X or TWRP 2.5.0).
While installing, Magisk tries to send commands to the custom recovery that cant be understood by it, leaving the installation incomplete after some modifications in /system (read below recovery log).
Acording to the recovery, it seems that Magisk did some modifications without running correctly survival script - Adding addon.d survival script ("Unrecognized option '-Xnodex2oat'") and .zip installer is not designed to revert actions in this case.
Also, Magisk couldn't reach the boot modification step, so boot is not damaged, therefore workarounds for restoring boot won't work.
Using Magisk Unistaller.zip is also not possible as the uninstaller is mainly designed for boot backup restoration, and again, this is not the case.
Currently needed: Find what's wrong in system due to the incomplete Magisk installation to revert it back to the original state (before faulty magisk.zip installation).
Recovery log:
************************
* Magisk v18.1 Installer
************************
- Mounting /system, /vendor
- Target image: /dev/bootimg
- Device platform: arm
- Removing system installed root
- Constructing environment
- Adding addon.d survival script
Unrecognized option '-Xnodex2oat'

up!

I' also having the same problem. My Samsung J2 Prime stuck at logo after updating to 18.1. Any tips on how to fix it without resetting my phone? Thanks.
Update: Bootloop fixed. I used TWRP to restore boot image. I then update Magisk by flashing zip file from TWRP. Everything went back to normal. Hope this help.

trol_sg said:
Hello everybody.
I've read that 18.1 supports 4.2+ so I've tried to install in two MTK6589T devices I've. One running 4.2, the other running 4.4
CMW/TWRP gave an error mounting system, so I mounted system manually and it started flashing. Firstly it detected old root installed and disabled the old root. But when it tried to find the boot, installation was aborted because installator claims cannot find the boot on both phones.
Then I though, okay, lets reboot back to android, I will try to install a few days later, maybe its buggy now, but both phones cannot boot.
I can easily fix them by flashing rom again I guess, but I would like to know where's the issue and also post it for more people could face the same problem.
Any idea where's the problem/how to fix without rom reflashing? I've tried magisk uninstaller but after mounting system in recovery it is also giving error.
Thanks
Click to expand...
Click to collapse
If you have a backup of your boot image, you can just restore it using TWRP. But in case that you have no backup of boot image, you can try to get boot image from the internet and restoring using it. In my case, this is what I did.
1. Go to TWRP and then make backup of boot image of the faulty phone*. (Folder 1)
2. I used another J2 prime to create a boot image backup. (Folder 2)
3. Once that is done, copy and replace the files inside the Folder 2 into Folder 1.
4. Reboot to TWRP again then use that to restore the boot image on my stuck J2.
Tips: make backup in SD card so you can easily swap it in between the bad and good phone.
*This is to create a folder of the backup file. I did tried to directly copy and paste the backup boot image file from another good phone but TWRP didn't detect it. So this is the workaround that I come with. And it worked for me.

Thanks for your answer but I doubt your case is mine. Your device is much newer than mine and according to your comment, you've sucesfully installed previous version of Magisk without issues. This is not a problem while updating, as Magisk v. earlier than 18.1 was not compatible with android 4.2+. I think Magisk is not compatible with MT6589T even if they run 4.2 or 4.4.
I think that it cannot be a boot problem as TWRP/CWM displayed msg 'Boot cannot be found' while installing Magisk, so that I don't think boot was replaced or modified in any ways. Moreover, the bootloop is not in the boot loading, as phone can pass boot image without any problem, but it is stuck in android loading image. I'm thinking in some script or root modification that Magisk did before trying to unpack the boot, however I'm not that deep into the Magisk install to find the proper workaround.
I can restore boot backup and also I can take boot file from the original rom and flash, because in Mediatek-based devices, boot.img is inside de zip, but I dont think it will solve the problem. Anyhow I'll get back ASAP with the answer.
Any more ideas??

Nothing, boot/uboot restoration or flashing again just the boot won't fix the problem, so it's something that Magisk installator touch in /system or /data I guess, but what?

trol_sg said:
Nothing, boot/uboot restoration or flashing again just the boot won't fix the problem, so it's something that Magisk installator touch in /system or /data I guess, but what?
Click to expand...
Click to collapse
Have you read/tried this?
didgeridoohan(dot)com/magisk/MagiskIssues

Ato09 said:
Have you read/tried this?
didgeridoohan(dot)com/magisk/MagiskIssues
Click to expand...
Click to collapse
Yes, I've read them before I made the post. I've also looked for a solution in some of the threads and using search, but couldn't find a way.

Here I attach recovery.log if someone is interested to see the detailed problem.
Also, here below I attach the lines concerning the installation. All other is uninstallation tries and so on:
************************
* Magisk v18.1 Installer
************************
- Mounting /system, /vendor
- Target image: /dev/bootimg
- Device platform: arm
- Removing system installed root
- Constructing environment
- Adding addon.d survival script
Unrecognized option '-Xnodex2oat'
dalvikvm: [options] class [argument ...]
dalvikvm: [options] -jar file.jar [argument ...]
The following standard options are recognized:
-classpath classpath
-Dproperty=value
-verbose:tag ('gc', 'jni', or 'class')
-ea[:<package name>... |:<class name>]
-da[:<package name>... |:<class name>]
(-enableassertions, -disableassertions)
-esa
-dsa
(-enablesystemassertions, -disablesystemassertions)
-showversion
-help
The following extended options are recognized:
-Xrunjdwp:<options>
-Xbootclasspath:bootclasspath
-Xcheck:tag (e.g. 'jni')
-XmsN (min heap, must be multiple of 1K, >= 1MB)
-XmxN (max heap, must be multiple of 1K, >= 2MB)
-XssN (stack size, >= 1KB, <= 256KB)
-Xverify:{none,remote,all}
-Xrs
-Xint (extended to accept 'ortable', ':fast' and ':jit')
These are unique to Dalvik:
-Xzygote
-Xdexopt:{none,verified,all,full}
-Xnoquithandler
-Xjniopts:{warnonly,forcecopy}
-Xjnitrace:substring (eg NativeClass or nativeMethod)
-Xstacktracefile:<filename>
-Xgc:[no]precise
-Xgc:[no]preverify
-Xgc:[no]postverify
-Xgc:[no]concurrent
-Xgc:[no]verifycardtable
-XX:+DisableExplicitGC
-X[no]genregmap
-Xverifyopt:[no]checkmon
-Xcheckdexsum
-Xincludeselectedop
-Xjitop:hexopvalue[-endvalue][,hexopvalue[-endvalue]]*
-Xincludeselectedmethod
-Xjitthreshold:decimalvalue
-Xjitcodecachesize:decimalvalueofkbytes
-Xjitblocking
-Xjitmethod:signature[,signature]* (eg Ljava/lang/String\;replace)
-Xjitclass:classname[,classname]*
-Xjitoffsetffset[,offset]
-Xjitconfig:filename
-Xjitcheckcg
-Xjitverbose
-Xjitprofile
-Xjitdisableopt
-Xjitsuspendpoll
Configured with: debugger profiler hprof jit(armv7-a-neon) smp show_exception=1
Failed to initialize runtime (check log for details)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/dev/bootimg]
No boot image magic found!
! Unable to unpack boot image
- Unmounting partitions
E:Error executing updater binary in zip '/sdcard/Magisk-v18.1.zip'
Error flashing zip '/sdcard/Magisk-v18.1.zip'

@trol_sg I'm gonna guess it's got to do with the absolutely ancient TWRP you're using. It just can't handle everything that the Magisk installation script is trying to do...
Your best bet (if Magisk will work at all on your device) is to patch the boot image with the Magisk Manager and then flash the patched image manually. There are new and shiny installation instructions available here: https://topjohnwu.github.io/Magisk/

Didgeridoohan said:
@trol_sg I'm gonna guess it's got to do with the absolutely ancient TWRP you're using. It just can't handle everything that the Magisk installation script is trying to do...
Your best bet (if Magisk will work at all on your device) is to patch the boot image with the Magisk Manager and then flash the patched image manually. There are new and shiny installation instructions available here: https://topjohnwu.github.io/Magisk/
Click to expand...
Click to collapse
Thank you so much for your answer. So it's the recovery, but can't find newer ones, sadly. Too old phones I know, but just curious if I could make Magisk working on them, lol.
I was going into the boot modification manually right now, but in order to patch the boot I need manager installed first, and phone couldn't boot so I did dirty flash of the rom to be able to boot into it again.
Lets see what happens then. I'll be right back.
Anyhow, this is not a solution to fix the problem of bootloop that I am requesting help in case someone could face the same and did not make a backup of the phone and didn't want to make dirty re-flash. Any idea?
Update: After I did dirty flash of the rom, and now Jiayu g3s android 4.4 booted.

UPDATE: So, after patching manually boot and installing (using restore in TWRP 2.5 as image flash is not yet implemented AFAIK), phone booted and yes Magisk is working.
Magisk installation .zip through a very old recovery is making the bootloop. So that, a thing learnt now.
But, for other people facing this bootloop, can we do a research to find what magisk.zip did to the phones to leave them in bootloop? Maybe we can revert without rom flashing easily if we knew what's the issue...
Thanks in advance!

Doing a bit more tests I found that magisk.zip did something in /system so that it is left in bootloop, but still no idea why/whats causing that...

There are delay complete boot like 4 5 second in j7 prime. I didn't love this version

any more help?? up!!

trol_sg said:
Yes, I've read them before I made the post. I've also looked for a solution in some of the threads and using search, but couldn't find a way.
Click to expand...
Click to collapse
Try this.
Quote:
Originally Posted by void74
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
Quote:
Originally Posted by Mangraviti
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
-------------
Original post. https://forum.xda-developers.com/apps/magisk/bootloop-magisk-update-t3836904
Hope it help.

Ato09 said:
Try this.
Quote:
Originally Posted by void74
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
Quote:
Originally Posted by Mangraviti
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
-------------
Original post. https://forum.xda-developers.com/apps/magisk/bootloop-magisk-update-t3836904
Hope it help.
Click to expand...
Click to collapse
Hello, thanks
This method won't work in my case as in the step:
- installed magisk uninstall = gives error
Note 5 is much newer phone with a recent recovery TWRP that allows all Magisk.zips commands, but unluckyly not this case.
Also, this method is for wrong boot installation/damaged boot. In my case what Magisk damage is /system, not boot.
I wish it could be boot, because that is very easy to fix (flashing through fastboot/SP Flash tools in the case of MTK, recovering boot twrp "backup" even if you didn't make backup...) as you mentioned.
Hope someone have a great idea to revert system to origin, then we could post the solution for those who would like to install Magisk in 4.2+ old phones, and instead of doing boot flash manually, they try to flash magisk.zip and they got bootloop.

Main post updated with all thread information. Up!

Nothing?? Up!!

trol_sg said:
Hope someone have a great idea to revert system to origin, then we could post the solution for those who would like to install Magisk in 4.2+ old phones, and instead of doing boot flash manually, they try to flash magisk.zip and they got bootloop.
Click to expand...
Click to collapse
The only part of the Magisk installation that actually touches /system is if it installs the addon.d survival script. The log you posted earlier shows that it's trying to do this, for some reason, and failiing. I'd start looking there...

Magisk 20.1 Canary, Android 10, Pixel 3: Unsupported/Unknown image format on boot img

Google helpfully updated my Pixel 3 (with Magisk) OTA to Android 10.
I've followed the instructions to move to the Canary/Canary Debug channel, updated Magisk Manager, uploaded to the phone both the OTA and recovery images, but Magisk is unable to patch:
Code:
- Device platform: arm64-v8a
- Copying image to cache
1618+0 records in
1618+0 records out
1656832 bytes (1.5 M) copied, 0.005972 s, 265 M/s
1085+1 records in
1085+1 records out
1111628 bytes (1.0 M) copied, 0.005266 s, 201 M/s
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
I've tried with these factory images:
blueline-ota-qp1a.191005.007-e5bf373b.zip
blueline-qp1a.191005.007-factory-c36610c6.zip
Extracting boot.img from either of those images, uploading to the phone "Download" directory and attempting to patch isn't possible. Magisk Manager does not show boot.img at all in the file selection list, even though it is there, verified by both Astro file manager as well as adb shell and PC file sharing.
Suggestion what to try next?

I gave it a shot and downloaded the factory image to test. Had no issues patching the boot image file with Magisk Canary 20001 on my OP3T using Manager 245. Something's obviously wrong (and you're not the only one reporting this), but I've no idea what...

Didgeridoohan said:
I gave it a shot and downloaded the factory image to test. Had no issues patching the boot image file with Magisk Canary 20001 on my OP3T using Manager 245. Something's obviously wrong (and you're not the only one reporting this), but I've no idea what...
Click to expand...
Click to collapse
Hi, I flashed coltos5.1 on my op3t yesterday to give a try with Android 10 but I'm unable to install magisk 20 (downloaded from Magisk Manager 7.3.5). I tried from TWRP and also by patching the boot file (extracted from the ROM). How have you been able to flash it ? Which ROM are you using ?

coolrick said:
Hi, I flashed coltos5.1 on my op3t yesterday to give a try with Android 10 but I'm unable to install magisk 20 (downloaded from Magisk Manager 7.3.5). I tried from TWRP and also by patching the boot file (extracted from the ROM). How have you been able to flash it ? Which ROM are you using ?
Click to expand...
Click to collapse
I have not yet tried 10 on my 3T. I merely tested patching the Pixel 3 Android 10 boot image, and that worked without problem. On my device, I have to add...
Right now I downloaded ColtOS and tried patching the boot image. That worked without issue (can't test flashing it though, of course), so what problems do you have?

Didgeridoohan said:
I have not yet tried 10 on my 3T. I merely tested patching the Pixel 3 Android 10 boot image, and that worked without problem. On my device, I have to add...
Right now I downloaded ColtOS and tried patching the boot image. That worked without issue (can't test flashing it though, of course), so what problems do you have?
Click to expand...
Click to collapse
Thanks for the quick reply - Patching was not a problem but then it doesn't boot. I got the oneplus logo but it doesn't go further (no bootloop, I stays on the logo and doesn't do anything).

coolrick said:
Thanks for the quick reply - Patching was not a problem but then it doesn't boot. I got the oneplus logo but it doesn't go further (no bootloop, I stays on the logo and doesn't do anything).
Click to expand...
Click to collapse
Getting off-topic... Replied here: https://forum.xda-developers.com/ap...systemless-t3432382/post80522263#post80522263

coolrick said:
Thanks for the quick reply - Patching was not a problem but then it doesn't boot. I got the oneplus logo but it doesn't go further (no bootloop, I stays on the logo and doesn't do anything).
Click to expand...
Click to collapse
I just refollow everything from the magisk guide (https://topjohnwu.github.io/Magisk/install.html#boot-image-patching) and retry the Boot Image Patching. This time it was OK - My OP3T endly boot up fine. Anyway, thanks for your help.

Magisk, TWRP and Android 10
coolrick said:
Hi, I flashed coltos5.1 on my op3t yesterday to give a try with Android 10 but I'm unable to install magisk 20 (downloaded from Magisk Manager 7.3.5). I tried from TWRP and also by patching the boot file (extracted from the ROM). How have you been able to flash it ? Which ROM are you using ?
Click to expand...
Click to collapse
I think Magisk and TWRP don't support Android 10 quit well. I got the same error message.

Pixel 5 w/ Jan Update - Flash of patched boot.img = loop

Hi all,
I seem to be struggling with my usual process of getting root on my Pixel 5.
I installed the latest Canary build of the Magisk Manager and patched my base boot.img and then flashed it and the phones goes into an infinite loop. Only way to get out of it is to flash-all.bat (w/out the -w). Any ideas on why this process, which I've used even on my previous P2XL, is no longer working?
When I open the manager, it says my installed version is 8.0.4 (4770) and the latest version is 6d88d8ad (4770) (15) but I can't update.

I have the January release and the same magisk version, and my device boots fine. What steps did you do to patch the boot.img file and how did you flash the patched magisk_patched.img file?

Amd4life said:
I have the January release and the same magisk version, and my device boots fine. What steps did you do to patch the boot.img file and how did you flash the patched magisk_patched.img file?
Click to expand...
Click to collapse
This is the process I follow each month/followed for this update:
Download and extract FW
Edit flash-all.bat to remove the -w
Run flash-all.bat while at bootloader screen
Copy \redfin-rq1a.210105.003\boot.img to device
Open Magisk Manager Canary (latest) and click on "Install"
Select "Select and Patch a File"
Copy \download\magisk_patched_0eKAS.img to platform-tools folder on PC
At bootloader screen, run: fastboot flash boot magisk_patched_0eKAS.img
Reboot
I've been using that process for months, going back to my Pixel 2 XL and used that process (with different .img names obviously) last month even for the December update on this here Pixel 5.
Only way to get out of the loop is to re-run step 3.

IlyaKol said:
Hi all,
I seem to be struggling with my usual process of getting root on my Pixel 5.
I installed the latest Canary build of the Magisk Manager and patched my base boot.img and then flashed it and the phones goes into an infinite loop. Only way to get out of it is to flash-all.bat (w/out the -w). Any ideas on why this process, which I've used even on my previous P2XL, is no longer working?
When I open the manager, it says my installed version is 8.0.4 (4770) and the latest version is 6d88d8ad (4770) (15) but I can't update.
Click to expand...
Click to collapse
Have you tried using Magisk latest beta? I ended up using beta for January for whatever reason and had no issue. I'd upload my boot.img but I'm a Verizon user and not sure if it'll work for you. "magisk_patched_dnuD3.img"
Magisk v21.2 (21200)
Magisk Manager v8.0.4 (4768) (15)

andybones said:
Have you tried using Magisk latest beta? I ended up using beta for January for whatever reason and had no issue. I'd upload my boot.img but I'm a Verizon user and not sure if it'll work for you. "magisk_patched_dnuD3.img"
Magisk v21.2 (21200)
Magisk Manager v8.0.4 (4768) (15)
Click to expand...
Click to collapse
Let me give that a whirl in a bit.

IlyaKol said:
Let me give that a whirl in a bit.
Click to expand...
Click to collapse
andybones said:
Have you tried using Magisk latest beta? I ended up using beta for January for whatever reason and had no issue. I'd upload my boot.img but I'm a Verizon user and not sure if it'll work for you. "magisk_patched_dnuD3.img"
Magisk v21.2 (21200)
Magisk Manager v8.0.4 (4768) (15)
Click to expand...
Click to collapse
I installed 8.0.4 but when I try to patch the image with it, it fails. When I try to sideload 21.2 or 20.4, it says:
E:footer is wrong
E:Signature verification failed
E:error: 21
Install from ADB completed with status 2.
Installation aborted.

I was able to patch the image after changing to the beta channel. However, it started to loop again and eventually went back to bootloader with the reason being "no valid slot to boot". I've flash-all.bat'ed again and am back to working. I don't understand why I can't get this to work.

I also had an inability to boot after I tried to do the December update using Minimal ADB. No valid slot.
I switched to a new platform tools install, and the same procedure has now worked twice. How old is your platform tools install?

If anyone is having problems patching the stock boot.img, you can upload it and I can patch it and re-upload it for you.

earlgrey_44 said:
I also had an inability to boot after I tried to do the December update using Minimal ADB. No valid slot.
I switched to a new platform tools install, and the same procedure has now worked twice. How old is your platform tools install?
Click to expand...
Click to collapse
It was pretty new/latest version but I went ahead and just re-downloaded the factory image and platform tools and am trying again...
If it matters, I'm back to Canary manager and here is what my patch screen says:
Code:
- Device platform: arm64-v8a
- Magisk Manager: 8.0.4 (4770)
- Install target: 6d88d8ad (21201)
- Copying image to cache
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
- Repacking boot image
- Output file *path*
- All done!
My actual flash output is:
Code:
> fastboot flash boot magisk_patched_Mx5Yh.img
Sending 'boot_a' (98304 KB) OKAY [ 2.277s]
Writing 'boot_a' OKAY [ 0.312s]
Finished. Total time: 2.918s
UPDATE:
I got it working this time around using a fresh new factory image and platform tools download.
I'm actually wondering if, in my haste, I actually used the bootloader image, not the boot img...but wouldn't Magisk have complained? lol.
Who knows, but looks like my issue is resolved! Thanks all for having me try things like a new platform tools download.

Question Root doesn't work after update

I did as I usually do I updated my system and then reflashed vbmeta and root but for the latest update it didn't work.

If you're using magisk to root (and twrp), then after flashing the latest version (24.1 right now), boot into you system, open the apps drawer then close it and wait a little while. sometimes it takes a minute to load in that shortcut for installing the magisk app. if you managed to install the app, but you dont have root, open the app and make sure that you have both options on the home page installed (i believe its magisk, and magisk app). You need the top one for root, the bottom one is the one you just installed. Also make sure they are up to date, as sometimes outdated versions dont work. Or maybe the opposite is happening, and the newer version of magisk doesnt work for you, if thats the case then download the version you used before and flash that.

blocky3321 said:
I did as I usually do I updated my system and then reflashed vbmeta and root but for the latest update it didn't work.
Click to expand...
Click to collapse
Because the ota cancel magisk robot. U have to repatch new boot.img and reflash magisk

PhotonIce said:
If you're using magisk to root (and twrp), then after flashing the latest version (24.1 right now), boot into you system, open the apps drawer then close it and wait a little while. sometimes it takes a minute to load in that shortcut for installing the magisk app. if you managed to install the app, but you dont have root, open the app and make sure that you have both options on the home page installed (i believe its magisk, and magisk app). You need the top one for root, the bottom one is the one you just installed. Also make sure they are up to date, as sometimes outdated versions dont work. Or maybe the opposite is happening, and the newer version of magisk doesnt work for you, if thats the case then download the version you used before and flash that.
Click to expand...
Click to collapse
with the older versions i get suck in a boot loop and with the new version there is no root

blocky3321 said:
with the older versions i get suck in a boot loop and with the new version there is no root
Click to expand...
Click to collapse
Look into how to root discussion. I have uploaded boot.img patched from new 12.5.4
Open your eyes

wetito said:
Look into how to root discussion. I have uploaded boot.img patched from new 12.5.4
Open your eyes
Click to expand...
Click to collapse
i tried the boot and vbmeta it didnt work got stuck in a boot loop

It you have 12.5.4 firmware working 100% I have flashed on my device

wetito said:
It you have 12.5.4 firmware working 100% I have flashed on my device
Click to expand...
Click to collapse
tried again and got suck on the miui screen on fastboot reboot

blocky3321 said:
with the older versions i get suck in a boot loop and with the new version there is no root
Click to expand...
Click to collapse
i just tried rooting my phone with magisk 24.2 (latest at the moment). just follow the steps i listed in my first post and you'll have root.

PhotonIce said:
i just tried rooting my phone with magisk 24.2 (latest at the moment). just follow the steps i listed in my first post and you'll have root.
Click to expand...
Click to collapse
use magisk 24.1, because 24.2 it's a beta. it's buggy. my files are patched with 24.1

blocky3321 said:
tried again and got suck on the miui screen on fastboot reboot
Click to expand...
Click to collapse
1. Download the fastboot version of your rom here:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
I prefer 12.5.4 as it's not buggy, laggy as MIUI 13 and it has navigation button shortcuts, a new cool feature. Remind again, you must download Type fastboot, not Type recovery
2. Unzip downloaded rom, look for [rom name] folder -> images -> boot.img file
3. Copy that boot.img to your phone storage, any phone is fine
4. Run Magisk 24.1 on the any phone that got the boot.img file
5. Press Install
6. Choose Select and Patch a file
7. Navigate and choose the copied boot.img
8. You'll get something like this in your phone storage: magisk_patched-24100_VDv7z.img
9. Copy magisk_patched-24100_VDv7z.img to your PC
10. Install ABD 15 seconds installer, if not already done so
11. Get phone to fastboot mode
12. Use this command to enter fastbootd
Code:
fastboot reboot fastboot
13. Flash empty vbmeta.img:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vbmeta_b vbmeta.img
Where is this vbmeta.img from? Check downloaded rom folder, look for [rom name] folder -> images -> vbmeta.img file
14. Use this command to flash your Magisk patched img:
Code:
fastboot flash boot magisk_patched-24100_VDv7z.img
Reminder: Each time Magisk patches an img file, it changes name randomly, so don't blindly input this command, you must change name too: fastboot flash boot [magisk patched boot name].img
15. Reboot to your phone's rom:
Code:
fastboot reboot