Download 9.0.7 Patched Boot Image For Magisk

[Ray Kowalewski]

Theresult of Ramdisk determines whether your device has ramdisk in the boot partition. If your device does not have boot ramdisk, read the Magisk in Recovery section before continuing.

If your device has boot ramdisk, get a copy of the boot.img (or init_boot.img if exists).

If your device does NOT have boot ramdisk, get a copy of the recovery.img.

You should be able to extract the file you need from official firmware packages or your custom ROM zip.

Warning: NEVER flash patched image shared by others or patch image on another device even if they have the same device model! You may need to do a full data wipe to recover your device. ALWAYS patch boot image on the same device where you want to install Magisk.

The easiest way to uninstall Magisk is directly through the Magisk app. If you insist on using custom recoveries, rename the Magisk APK to uninstall.zip and flash it like any other ordinary flashable zip.

In the case when your device does not have ramdisk in boot images, Magisk has no choice but to hijack the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk enabled.

When Magisk hijacks the recovery, there is a special mechanism to allow you to actually boot into recovery mode. Each device model has its own key combo to boot into recovery, as an example for Galaxy S10 it is (Power + Bixby + Volume Up). A quick search online should easily get you this info. As soon as you press the key combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. If you decide to boot into the actual recovery mode, long press volume up until you see the recovery screen.

Installing using custom recoveries is only possible if your device has boot ramdisk. Installing Magisk through custom recoveries on modern devices is no longer recommended. If you face any issues, please use the Patch Image method.

In this tutorial, we are going to show how one can root an android device by patching the stock boot.img using Magisk Manager. This comes in particularly handy for those on Lollipop and above where one-click-root apks like Kingroot don't work and would therefore require a custom recovery to root. With this method, you won't be needing a one-click-root apk or custom recovery (e.g Philz, CWM, TWRP etc) to root your device.

Stock boot.img for your phone model (its best its for your Build Number / Variant ) . You can extract from the stock rom / firmware of your device (you may check our collection at -89.html ) OR backup from your device using a hardware box e.g Miracle Box, CM2, Nck Box Pro etc

Install MagiskManager apk on your android device Copy the stock boot.img of your device to your phone's internal storage or SD card Launch Magisk Manager app If you're not using the latest version, you'll have to update the app first before proceeding If you intend to patch recovery.img then manually tick "Recovery Mode" in Advanced Settings Select Install > Install > Select and Patch a File > Navigate to the location of the stock boot.img you copied earlier on, then Select it. Note that if you are using a samsung device then you should select the firmware of your device in .tar format instead of boot.img Magisk Manager should begin downloading the magisk zip file used for patching Once download is complete, MagiskManager will automatically patch the file and store it under SDcard/Download/magisk_patched.img[.tar]

You have a variety of options to flash the patched boot.img depending on your chipset (e.g Mediatek MTK, Spreadtrum SPD, Qualcomm QLM etc ), the resources you have and your skills. Note that some flashing methods might require you to rename the file to boot.img For those using MTK devices and have the specific scatter file for their device, you can flash the patched boot.img using SP flash tool or Miracle Box For those using SPD devices and have the PAC file for their device, you can flash the patched boot.img using Research download tool by replacing the stock boot.img with your patched boot.img For those using Qualcomm devices, you can flash patched boot.img using Miracle box custom flasher; see -26213.html For those using Samsung devices and wish to flash patched boot.img.tar using Odin see Generally speaking, you could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below

I was running Magisk on Android 11 on my Google Pixel 5.I installed it using a patched boot image from 11.0.0 (RD1A.200810.021.A1, Oct 2020, EU carriers).Today Android 11 prompted me with an update, I installed it without thinking about the consequences. After rebooting Magisk stopped functioning. So I rebooted to fastboot mode and flashed the same patched boot image as i did the first time. I flashed both boot_a and boot_b, I remembered i did that the last time.

I also tried flashing the unpatched boot image from the original image, but same effect.Maybe i had to patch the latest magisk version on a fresh boot image, but can't do that anymore without access to magisk on my phone. Was running the latest canary YAHFA version.

In the end i fixed it with extracting the boot image from the correct factory image. At first I didn't see that the latest image was at the end of the list here the boot image gave me a 'no command' screen. But I was able to boot into safe mode. After that i could patch the boot image file with magisk, and patch it in fastboot. And then everything was working again!

While booted from that image we have root privileges available to us and we use those to install Magisk through the app. Magisk patches the real boot partition directly and after a reboot we have a working Magisk installation.

The /e/ .zip contains disk images you have to manually flash to your device, rather than a OTA style install where you flash a ota.zip containing payload.bin through recovery (iode are using that method for example)

Just wanted to leave a big thank you in here for all of you.

I flashed /e/ os yesterday on my new FP4, stupidly thinking it would be rooted automatically.

After reading all the posts in here I could easily patch the /e/ os boot image on my phone, boot this image and then install magisk.

I will now try out the phone, but so far everything seems to just work!

This might still eat your data, so make sure you have a reliable system in place to automatically safe your data off device (something like syncthing). With that in place, go ahead and have fun

Just a short info:

Installed /e/OS on my FP5 yesterday and rooted it. The FP4 rooting method (as described in the first post; which I also used that time on my FP4 with CalyxOS)

is useable and went fine for the FP5 as well.

as the title states, I am trying to root my FairPhone 5 with Magisk and would appreciate any help I can get.

I already tried rooting it by patching the boot image with Magisk and then booting the image in Fastboot mode.

This did in fact install a stub Magisk app on the phone, but when I used it to bootstrap to a complete Magisk app and rebooted the phone it still showed:

How should I proceed?

I could try the same process again, hoping for a different outcome (maybe I made a mistake the first time).

I could also try the custom recovery approach with installing the Magisk .apk as a .zip file.

Any advice is greatly appreciated

patching the boot image with Magisk and then booting the image in Fastboot mode.

This did in fact install a stub Magisk app on the phone, but when I used it to bootstrap to a complete Magisk app and rebooted

Imaging you directly flash it and whatever is wrong goes wrong or you end up in a bootloop. Imho direct flash is more risky. Still you can flash an old boot.img and hope that it works again - still I think the risk higher.

This instructions from the XDA is that also applicable for CalyxOs? I look a bit critical to this because it is mixed up the file boot.img from the ROM of the manufacturer with the CalyxOs. I am not sure if this is a good idea.

I downloaded it (took the lower IMG since it was more similar to my phones build number). Extracted the .zip. Copied the boot.img to my phone. Patched with Magisk, but the patched_boot.img is again 0 bytes. This can not be correct?!

The FP4 Instructions should be a summary of the official instructions so I will add them here till someone confirms something else. I didnt test so when you try its at your own risk.

I will make this a wiki, so please update, correct as needed.

For OTA update with root on a FP5 the following would be expected to work, however for unknown reason might not which then requires re-rooting (see below for further information. In my eyes the patched boot.img should never be flashed!)

Did you also try from a different network? Like mobile instead of WiFi, or work/friend/etc. instead of (presumably) home?

Can you tell if it actually downloads and then has a problem during installation or if the download does not even start?

To update your Fairphone, always use the regular procedure.This article will help you install Fairphone OS via computer if you encounter issues with the regular procedure or if you are reverting to...

Now comes the actual fix that restored my ability to upgrade via OTA:

Extract the vbmeta.img from the aforementioned zip of your currently installed version and place it in your working directory.

I now got the OTA to work with basically stock everything, except for the unlocked bootloader, which means loosing magisk for every OTA as of now and reflashing the patched image via fastboot every time.

3a8082e126