Database Develop

Switching from SuperSU to MagiskSU

Dear all,
I currently use the Minotaurus S8 Port V11.0 (pre-rooted ROM) on a Samsung S7 Edge.
During the installation I chose SuperSU.
Now I'd like to switch to MagiskSU - if possible without flashing the complete ROM one again.
Nevertheless my efforts currently are not successful.
I read that I have to unroot first what I did with using osm0sis unSU. This worked and root was gone.
Trying then to install Magisk (v12) ended up with an error:
****************************************
Magisk v12.0 Boot Image Patcher
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking patch status
- SuperSU patched boot detected!
- Adding ramdisk patch script for SuperSU
- We are using SuperSU's own tools, mounting su.img
! SuperSU image mount failed...
! Magisk scripts are placed correctly
! Flash SuperSU immediately to finish installation
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v12.0.zip'
Updating partition details...
...done
Then I installed SuperSU v2.82 again which brought back root (with SuperSU).
I tried to flash Magisk v13.0 (96f8efc) but again end up in an error:
****************************************
Magisk v13.0 (96f8efc) Installer
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs!
! please restore stock boot image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v13.0(96f8efc).zip'
Updating partition details...
...done
Is anybody able to help me and give me some guidance to get MagiskSU (with v13.0)
Thank you in advance,
Best regards,
MarkusTh

Besides flashing the unSU script you'll need to also flash a boot image without the SuperSU patches. That's gonna be an issue on a pre-rooted ROM. You say you chose SuperSU during installation? Did you have any other options (Magisk or no root)? If so, reinstall the ROM and make a different choice.

Didgeridoohan said:
Besides flashing the unSU script you'll need to also flash a boot image without the SuperSU patches. That's gonna be an issue on a pre-rooted ROM. You say you chose SuperSU during installation? Did you have any other options (Magisk or no root)? If so, reinstall the ROM and make a different choice.
Click to expand...
Click to collapse
Thanks for the quick answer.
Yes, the other options mentioned by you are available.
Is it possible to do a "dirty" flash over the current ROM without having to reinstall everything again afterwards ?
If yes, I assume the steps would be:
1) "dirty" flash of original ROM with choosing "MagiskSU" or "no root"
2) reboot necessary ?
3) flashing Magisk v13
4) reboot and ready ?
That easy ?
Thx,
MarkusTh

Or extract the kernel from your ROM.zip and flash it in TWRP.
Nothing in your current ROM will change.
So...
1.) unsu.zip
2.) Flash unpatched kernel (just go to "Install" in TWRP and choose in the bottom right "Select Image" > Select you boot.img and choose "boot" as partition in the next screen)
3.) Flash Magisk Beta v13
4.) Reboot
That's how I did it on my HTC 10.

Maik268 said:
Or extract the kernel from your ROM.zip and flash it in TWRP.
Nothing in your current ROM will change.
So...
1.) unsu.zip
2.) Flash unpatched kernel (just go to "Install" in TWRP and choose in the bottom right "Select Image" > Select you boot.img and choose "boot" as partition in the next screen)
3.) Flash Magisk Beta v13
4.) Reboot
That's how I did it on my HTC 10.
Click to expand...
Click to collapse
Thanks so much for this!! I would have been in a mess without this method which worked perfectly on my Samsung GS6. Thanks.

MarkusTh said:
Dear all,
I currently use the Minotaurus S8 Port V11.0 (pre-rooted ROM) on a Samsung S7 Edge.
During the installation I chose SuperSU.
Now I'd like to switch to MagiskSU - if possible without flashing the complete ROM one again.
Nevertheless my efforts currently are not successful.
I read that I have to unroot first what I did with using osm0sis unSU. This worked and root was gone.
Trying then to install Magisk (v12) ended up with an error:
****************************************
Magisk v12.0 Boot Image Patcher
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking patch status
- SuperSU patched boot detected!
- Adding ramdisk patch script for SuperSU
- We are using SuperSU's own tools, mounting su.img
! SuperSU image mount failed...
! Magisk scripts are placed correctly
! Flash SuperSU immediately to finish installation
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v12.0.zip'
Updating partition details...
...done
Then I installed SuperSU v2.82 again which brought back root (with SuperSU).
I tried to flash Magisk v13.0 (96f8efc) but again end up in an error:
****************************************
Magisk v13.0 (96f8efc) Installer
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs!
! please restore stock boot image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v13.0(96f8efc).zip'
Updating partition details...
...done
Is anybody able to help me and give me some guidance to get MagiskSU (with v13.0)
Thank you in advance,
Best regards,
MarkusTh
Click to expand...
Click to collapse
Mate, just unroot from supersu as you did earlier, then copy original boot image to internal memory, boot into TWRP, flash original boot image and then flash Magisk. It should work now.

atf2m4 said:
Mate, just unroot from supersu as you did earlier, then copy original boot image to internal memory, boot into TWRP, flash original boot image and then flash Magisk. It should work now.
Click to expand...
Click to collapse
I got the same issue and I tried to fix that but I don't know where the original boot image is located respectively where can I get the orginal boot image back? Could you help me out with my Samsung S8?
Thanks a bunch!

cocolish said:
I got the same issue and I tried to fix that but I don't know where the original boot image is located respectively where can I get the orginal boot image back? Could you help me out with my Samsung S8?
Thanks a bunch!
Click to expand...
Click to collapse
SOLVED! I managed to extract the boot.img from the original Samsung firmware and flashed the original boot.img via TWRP!

Maik268 said:
Or extract the kernel from your ROM.zip and flash it in TWRP.
Nothing in your current ROM will change.
So...
1.) unsu.zip
2.) Flash unpatched kernel (just go to "Install" in TWRP and choose in the bottom right "Select Image" > Select you boot.img and choose "boot" as partition in the next screen)
3.) Flash Magisk Beta v13
4.) Reboot
That's how I did it on my HTC 10.
Click to expand...
Click to collapse
Im having a similar problem. i have an lgms550. my problem is when i flash the stock boot img, magisk still states unable to mount. im not sure whats wrong here

So, I got a Huawei P9 (L09) and want to UnSU as well to install Magisk.
I once took apart an update file and therefore also have a boot.img from this package.
Is this file the one I would need to restore my boot partition on this phone?
If so, then I got super lucky here.

I am on J7 Prime (SM-G610F) the issue is I'm on the stock Nougat ROM which comes in a .tar.md5 format which I don't know how to disassemble.

The .md5 files are in fact .TAR files with the MD5 sum appended at the end.
If you rename each .md5 to a .tar file, they can be unpacked with 7zip or Winrar.

Can someone please please help me. I have j7 prime with supersu & trying to move on magisk but it says boot image is patched by another program. I'm soo tired with this issue please help me.

MarkusTh said:
Dear all,
I currently use the Minotaurus S8 Port V11.0 (pre-rooted ROM) on a Samsung S7 Edge.
During the installation I chose SuperSU.
Now I'd like to switch to MagiskSU - if possible without flashing the complete ROM one again.
Nevertheless my efforts currently are not successful.
I read that I have to unroot first what I did with using osm0sis unSU. This worked and root was gone.
Trying then to install Magisk (v12) ended up with an error:
****************************************
Magisk v12.0 Boot Image Patcher
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking patch status
- SuperSU patched boot detected!
- Adding ramdisk patch script for SuperSU
- We are using SuperSU's own tools, mounting su.img
! SuperSU image mount failed...
! Magisk scripts are placed correctly
! Flash SuperSU immediately to finish installation
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v12.0.zip'
Updating partition details...
...done
Then I installed SuperSU v2.82 again which brought back root (with SuperSU).
I tried to flash Magisk v13.0 (96f8efc) but again end up in an error:
****************************************
Magisk v13.0 (96f8efc) Installer
****************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
- Found Boot Image: /dev/block/sda5
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs!
! please restore stock boot image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/S7E Minotaurus/Magisk/Magisk-v13.0(96f8efc).zip'
Updating partition details...
...done
Is anybody able to help me and give me some guidance to get MagiskSU (with v13.0)
Thank you in advance,
Best regards,
MarkusTh
Click to expand...
Click to collapse
I can't find mt boot.img file
And unsu.zip is not unrooting my phone
And unroot failed saying in supersu
Please help????
And magisk 14.0 is not flashing saying error 1
Same as described
---------- Post added at 07:37 PM ---------- Previous post was at 06:39 PM ----------
Maik268 said:
Or extract the kernel from your ROM.zip and flash it in TWRP.
Nothing in your current ROM will change.
So...
1.) unsu.zip
2.) Flash unpatched kernel (just go to "Install" in TWRP and choose in the bottom right "Select Image" > Select you boot.img and choose "boot" as partition in the next screen)
3.) Flash Magisk Beta v13
4.) Reboot
That's how I did it on my HTC 10.
Click to expand...
Click to collapse
I did bit nothing happens
Showing my device is rooted even after uninstalling supersu
I can't flash magisk
First of all I've no boot.img file in my phone

brdude said:
I can't find mt boot.img file
And unsu.zip is not unrooting my phone
And unroot failed saying in supersu
Please help????
And magisk 14.0 is not flashing saying error 1
Same as described
---------- Post added at 07:37 PM ---------- Previous post was at 06:39 PM ----------
I did bit nothing happens
Showing my device is rooted even after uninstalling supersu
I can't flash magisk
First of all I've no boot.img file in my phone
Click to expand...
Click to collapse
The boot image you can extract from your device's factory image/firmware/ROM.
One of the best ways to unroot is to flash the unSU zip and then restore the stock boot image. That should be it.
If it doesn't work, provide logs (recovery log from flashing) and more details about your setup.

What is recovery log????
I have only copy log in my twrp recovery
And i tried copy log still saying boot image patched by other program
---------- Post added at 09:23 PM ---------- Previous post was at 09:12 PM ----------
I tried recently that unsu.zip
But still showing root is properly installed

brdude said:
What is recovery log????
I have only copy log in my twrp recovery
And i tried copy log still saying boot image patched by other program
---------- Post added at 09:23 PM ---------- Previous post was at 09:12 PM ----------
I tried recently that unsu.zip
But still showing root is properly installed
Click to expand...
Click to collapse
That is the recovery log.
Save the log after flashing the unSU zip and upload it. Or, just wipe and clean flash your device. Sounds like it might be easier... There are so many questions raised from your posts, but so few answers...
I'd suggest to go over to your device's forum and read up on the basics.

I have uninstalled SuperSU by flashing unsu.zip .
But when i tried to install magisk,it is failed showing this message "Boot image patched by other program,please restore stock boot image "
What to do??

madhuresh11 said:
I have uninstalled SuperSU by flashing unsu.zip .
But when i tried to install magisk,it is failed showing this message "Boot image patched by other program,please restore stock boot image "
What to do??
Click to expand...
Click to collapse
You do what the message says (the unSU zip doesn't restore the stock boot image for you)...
You'll find some pointers here:
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417

Didgeridoohan said:
You do what the message says (the unSU zip doesn't restore the stock boot image for you)...
You'll find some pointers here:
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
Click to expand...
Click to collapse
Thanks. It worked!!

Can't get past repacking boot image

My first time rooting my phone, and I'm trying to get magisk to work. But whenever I try to update from the Magisk Manager, I get the following:
- Detecting target image
- Target image: /dev/blocl/mmcblk0p15
- Device platform: armeabi-v7a
- Extracting files
- Unpacking boot image
- Checking ramdisk status
- Patching ramdisk
- Repacking boot image
! Unable to repack boot image !
Failed!
! Installation failed
I have no idea where I've gone wrong. If its any use, I use a Samsung Galaxy S5, with Magisk Version 16.
Thanks in advance.

jacobjbarker said:
My first time rooting my phone, and I'm trying to get magisk to work. But whenever I try to update from the Magisk Manager, I get the following:
- Detecting target image
- Target image: /dev/blocl/mmcblk0p15
- Device platform: armeabi-v7a
- Extracting files
- Unpacking boot image
- Checking ramdisk status
- Patching ramdisk
- Repacking boot image
! Unable to repack boot image !
Failed!
! Installation failed
I have no idea where I've gone wrong. If its any use, I use a Samsung Galaxy S5, with Magisk Version 16.
Thanks in advance.
Click to expand...
Click to collapse
Try with 16.7 or past version

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

Magisk destroyed my recovery partition.

Hello,
I have a px5 head unit.
I was trying to get root access on this unit, the kignoroot or whatever its name was didn't work. Using recovery.img which I exteracted from a working update.img, I preformed offline patch using Magisk. Magisk recognized the recovery.img and patched it. When I flashed the image my recovery is gone. There is black screen instead. I know it is working and the options are there.. but I can't see them to be able to use them.
With recovery gone, thanks to Magisk, I think the only hope now is to be able to use adb to restore recovery partition, try booting from sd card, or be able to access the bootloader to flash recovery partition.
so far I tried the commands:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
but when I try to connect I get "device unauthorized"!
I am unable to update the unit anymore..!
thanks for your help.

why the heck you patch the recovery.img in the first place?
the manual patch is only got boot.img aka kernel, not recovery.
this is clearly your fault!
no need to thanks Magisk for destroying your recovery, you destroyed it yourself.
Sent from my MI 5s Plus using Tapatalk

zohair_ said:
Hello,
I was trying to get root access on this unit, the kignoroot or whatever its name was didn't work. Using recovery.img which I exteracted from a working update.img, I preformed offline patch using Magisk. Magisk recognized the recovery.img and patched it. When I flashed the image my recovery is gone. There is black screen instead. I know it is working and the options are there.. but I can't see them to be able to use them.
With recovery gone, thanks to Magisk.
Click to expand...
Click to collapse
Well, about all I can say as a noob is READ, READ, READ. Everything you need is pretty well right here if you take the time to investigate your options. Nobody is going to hold your hand if you choose to follow through. Trashing the developer for your error isn't going to win you any friends either.
I came here some time ago looking for a way in to an SM-J320W a friend had picked up at an auction and I've probably spent close to 70+ hours reading about the various exploits, anomolies, file structures, device security, risks, and potential operational impacts, and indeed the distinct possibility I could even brick the device.
Like you I tried KingoRoot, Kingroot, and SU as relatively easy and benign attacks to no avail.
That led to longer investigation of more intensive attempts like CF-Auto-Root, Magisk, Rooted Boot Images, Custom Recovery ....
Right now I am looking at my Magisk App screen with 4 green checkmarks and a pass by Root Checker. ROOTED!
So, for all the other noobs out there:
Do your RESEARCH
Evaluate your OPTIONS
Understand the potential RISKS
Proceed only if you are PREPARED FOR THE CONSEQUENCES
It ain't rocket science, but it is science and you need to understand what you're doing.

Thanks for your responses. I would like to agree with your that it was my fault but can you explain how did Magisk was able to:
1. Unpack the recovery. Img
2. Recognize that the file was in the correct arm64 processor format and the correct one to patch.
3. Patch the file it recognized and unpacked.
4. Made a backup copy of the file before patching it.
5. Repacked the file.
6. Produce a log file affirming that the patching process was Successful!
All of this while it was the wrong file in the first place? It is hard to believe that it was my fault because recovery. Img was the only file accepted by Magisk. I tried all the other firmware files like boot. Img and kernel. Img and others, the only file that was accepted and recognized by Magisk was recovery. Img. Between us Magisk was not able to determine that the file it already patched was actually patched, no matter how many times you repatch that file.
Sorry to prove you wrong sir...!

I'm going to assume that your device is simply too far removed from a vanilla Android experience for it to be compatible with Magisk. The fact that it recognised and patched the recovery.img when Magisk is designed to alter the boot.img is a big hint... It would have been interesting to see the log from when you patched the file.

zohair_ said:
Thanks for your responses. I would like to agree with your that it was my fault but can you explain how did Magisk was able to:
1. Unpack the recovery. Img
2. Recognize that the file was in the correct arm64 processor format and the correct one to patch.
3. Patch the file it recognized and unpacked.
4. Made a backup copy of the file before patching it.
5. Repacked the file.
6. Produce a log file affirming that the patching process was Successful!
All of this while it was the wrong file in the first place? It is hard to believe that it was my fault because recovery. Img was the only file accepted by Magisk. I tried all the other firmware files like boot. Img and kernel. Img and others, the only file that was accepted and recognized by Magisk was recovery. Img. Between us Magisk was not able to determine that the file it already patched was actually patched, no matter how many times you repatch that file.
Sorry to prove you wrong sir...!
Click to expand...
Click to collapse
Even if the software trashes your whole system, it comes "as is", meaning that you get all the features and all possible bugs too without any kind of warranty. Nobody forced you to install it, so is the user's responsability to take all necessary steps to be able to recover the system to their prior state or assuming the risks involved in not doing so.
What you should and can do is provide as much information about your hardware and software so you may help others in the same situation and maybe make the developer take a look at it.
Understand that with that kind of attitude will not get you far here. As mentioned by others, educate yourself properly before taking any action that might brick your device, if something goes wrong is your sole responsability, but there are a lot of people here willing to help if you treat them with respect.

contents of the log file (magisk_install_log_20181204_054200.log) :
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
- Unpacking boot image
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user/0/com.topjohnwu.magisk/install/boot.img]
KERNEL [15104080]
RAMDISK [20858336]
SECOND [0]
EXTRA [0]
PAGESIZE [16384]
NAME []
CMDLINE []
CHECKSUM [7415a67292764b19e4067d67731d81ecc63a557b]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
- Checking ramdisk status
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Backing up stock boot image
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_334712fd9ff58aa61ae0734b157fc1261e8a616f.img.gz]
- Patching ramdisk
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]
Remove pattern [,verify]
Remove pattern [,verify]
Save SHA1: [334712fd9ff58aa61ae0734b157fc1261e8a616f] -> [.backup/.sha1]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [fstab.rk30board.bootmode.emmc] -> [.backup/fstab.rk30board.bootmode.emmc]
Backup mismatch entry: [fstab.rk30board.bootmode.unknown] -> [.backup/fstab.rk30board.bootmode.unknown]
Backup mismatch entry: [init] -> [.backup/init]
Dump cpio: [ramdisk.cpio]
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Patch @ 00CA4257 [736B69705F696E697472616D6673]->[77616E745F696E697472616D6673]
- Repacking boot image
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user/0/com.topjohnwu.magisk/install/boot.img]
KERNEL [15104080]
RAMDISK [20858336]
SECOND [0]
EXTRA [0]
PAGESIZE [16384]
NAME []
CMDLINE []
CHECKSUM [7415a67292764b19e4067d67731d81ecc63a557b]
KERNEL_FMT [raw]
RAMDISK_FMT [gzip]
Repack to boot image: [new-boot.img]
KERNEL [15104080]
RAMDISK [21090778]
SECOND [0]
EXTRA [0]
PAGESIZE [16384]
NAME []
CMDLINE []
CHECKSUM [f8b4e9f25b0c488e9a96a66263730d46737766b8]
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Cleaning up...
****************************
Patched image is placed in
/storage/emulated/0/Download/patched_boot.img
****************************
- All done!
EOF
=========================================
The Name of the firmware file is update. Img extracted from kgl_px5_6.0(20171102).rar (the link to download this file is posted somewhere here on the forum)
Version of Magisk: 5. 9.1
I think a reproduction of the same log is possible using the recovery. Img extracted from that firmware.

Why do I have this feeling that I am the one who is being treated with disrespect here..?

Device details? Android version? Are you using Magisk 17.1 for some particular reason? (At the time of this post, Magisk 18.0 was the latest stable release). You should also attach or link boot.img that you're trying to patch (saying is "somewhere in the forum" is not really helpful).

zohair_ said:
Why do I have this feeling that I am the one who is being treated with disrespect here..?
Click to expand...
Click to collapse
First: You blamed Magisk for what's clearly your fault.
Second: Of course Magisk will be able to patch stock recovery.img since it's essentially a SECONDARY OS in your phone albeit minimal, to recover your phone to working state.
It got it's own kernel and such, like an almost complete OS. Of course Magisk will be able to patch it & recognized it as a correct file to patch (it got untouched kernel which is compatible in it).
But if you patch it, you'll get what you get now: broken recovery, since it's not designed to patch recovery and no one crazy enough to attempt to patch a recovery with Magisk.
So, about disrespect: research before blaming. As anyone says: no one forced you to use Magisk. It's free & power come with great responsibility.
Magisk will give you degree of freedom to tinker with your phone, like root & xposed. But if you use them wrong, well, don't blame it if your phone's broken.
Just flash your phone with complete stock firmware and start over.
No hard feeling.

J_M_V_S said:
Device details? Android version? Are you using Magisk 17.1 for some particular reason? (At the time of this post, Magisk 18.0 was the latest stable release). You should also attach or link boot.img that you're trying to patch (saying is "somewhere in the forum" is not really helpful).
Click to expand...
Click to collapse
The device is a rockchip sdk3026. This head unit is popular on your forum as px5.
Android version is 6 Marshmallow.
I wasn't using Magisk 17.1 directly, I was using Magisk GUI and the "Boot Image Modification Tool" version 17.1 was used by the main program.
I downloaded the firmware from here. I cannot access that link anymore.
I will provide you with an ftp link soon where you can down load all the needed files.
Thanks for tying to help.

1.
Crescendo Xenomorph said:
why the heck you patch the recovery.img in the first place?
the manual patch is only got boot.img aka kernel, not recovery.
this is clearly your fault!
Click to expand...
Click to collapse
2.
Crescendo Xenomorph said:
Second: Of course Magisk will be able to patch stock recovery.img since it's essentially a SECONDARY OS in your phone albeit minimal, to recover your phone to working state.
Click to expand...
Click to collapse
3. no comment...!

zohair_ said:
The device is a rockchip sdk3026. This head unit is popular on your forum as px5.
Android version is 6 Marshmallow.
I wasn't using Magisk 17.1 directly, I was using Magisk GUI and the "Boot Image Modification Tool" version 17.1 was used by the main program.
I downloaded the firmware from here. I cannot access that link anymore.
I will provide you with an ftp link soon where you can down load all the needed files.
Thanks for tying to help.
Click to expand...
Click to collapse
head here: https://forum.xda-developers.com/an...eneral/mtcd-px5-headunits-repository-t3619906
there's a link for the firmware you need.
as for the instruction of how to flash it, better search in those subforum as I don't have the head unit myself.
as for root info: https://forum.xda-developers.com/android-auto/mtcd-software-development/root-oreo-t3779605
you're welcome

Well, about all I can say as a noob is READ, READ, READ. Everything you need is pretty well right here if you take the time to investigate your options. Nobody is going to hold your hand if you choose to follow through. Trashing the developer for your error isn't going to win you any friends either.
I came here some time ago looking for a way in to an SM-J320W a friend had picked up at an auction and I've probably spent close to 70+ hours reading about the various exploits, anomolies, file structures, device security, risks, and potential operational impacts, and indeed the distinct possibility I could even brick the device.
Like you I tried KingoRoot, Kingroot, and SU as relatively easy and benign attacks to no avail.
That led to longer investigation of more intensive attempts like CF-Auto-Root, Magisk, Rooted Boot Images, Custom Recovery ....
Right now I am looking at my Magisk App screen with 4 green checkmarks and a pass by Root Checker. ROOTED!
So, for all the other noobs out there:
Do your RESEARCH
Evaluate your OPTIONS
Understand the potential RISKS
Proceed only if you are PREPARED FOR THE CONSEQUENCES
It ain't rocket science, but it is science and you need to understand what you're doing.
Click to expand...
Click to collapse
Hi, for the J320W, did you root it at 7.1 ? If so, do you mind sharing the steps ? I only found one rooting approach but only for 6.0.1 . Many thanks in advance !

MAGISK unable to repack

Hi, i tried many times to use MAGISK app on a tablet ASUS FONEPAD 7 (model K00E) with Lollipop in order to patch the BOOT.IMG.
Always failed during the patching, with the messages:
DEVICE PLATFORM: x86
COPYING IMAGE TO CACHE
UNPACKING BOOT IMAGE
CHECKING RAMDISK STATUS
STOCK BOOT IMAGE DETECTED
PATCHING RAMDISK
REPACKING BOOT IMAGEUNABLE TO REPACK BOOT IMAGE!
INSTALLATION FAILED
I have searched for all the possible articles etc, without success.
I have tried many different versione of MAGISK, the last 20.4 and MANAGER 8.0.2 (i have used MAGISK install >> go >> method select and file update >> boot.img)
Obviously i have the original BOOT.IMG file, loaded on internal memory.
Please, may you help me?
Thanks in advance
Marco G

That's a pretty old device, and since Asus has been known to not quite follow Android standards I wouldn't be surprised if it's simply not compatible...
Since you say that you used Magisk v20.4 it might be worth it to try the Canary build (just in case there's been some kind of improvement upstream). You can find the Canary Manager on GitHub:
https://github.com/topjohnwu/Magisk
And providing the actual installation log is always a good idea (there's a disc icon in the flashing window).