In this guide, we will make you aware of the reason and more importantly, the steps to fix the issue of the Magisk Restore Images option missing/not working along the expected lines. When it comes to gaining administrative privileges by rooting your device, then Magisk is still the go-to choice for the masses, in spite of the likes of APatch and the popular KernelSU. While it tends to get the job done quite effectively, you might come across an issue or two during its usage.
For instance, one of its most useful features is the ability to retain root while installing OTA updates. For that, you’ll have to restore the stock boot/init_boot image, install the OTA, and then use Magisk’s Install to Inactive Slot. However, all this is proving to be easier said than done for a subset of users as the said option is either not working or surprisingly is missing from the app itself. So why is this the case and how could you fix it? Let’s find out.
Why is Magisk Restore Images option missing/not working
Before Magisk performs the Direct Install it makes a backup of some files, including the boot/init_boot file. Then when you are planning to do the update, you may use the Magisk Restore Images option followed by Install to Inactive Slot. Then restart your device and you will have the new OS installed and at the same time, the root will be retained as well.
However, if you carry out this task by flashing the patched boot/init_boot via Fastboot Commands, then in some instances, Magisk does not get enough time to take a backup. This, in turn, has a direct consequence on the Restore Images option which tends to perform unexpectedly or go missing altogether. With that said, there does exist a nifty method through which you could bring back this option and make it work again. So without further ado, let’s show you how this could be carried out.
Fix Magisk Restore Images option missing/not working
You should use the boot or init_boot, depending on which file you initially used for rooting. Moreover, before starting, please take a backup of all the data on your device, just to be on the safer side. Thedroidwin will not be held responsible if something happens to your device or data after carrying out the below steps.
- To begin with, download the stock firmware for your device.
- It should be of same version that is installed on your device.
- Then extract it and get hold of the boot/init_boot.img file.
- Transfer this file to your device, but not inside any folder.
- Enable USB Debugging and connect your device to a PC.
- Then download and extract Android SDK Platform Tools.
- Now open Command Prompt inside the platform tools.
- Then type in the below two commands, one after another:
adb shell su
- You might get a SuperUser request, tap on Grant/Allow.
- Now type in the below command to bring the partition table
ls -la /dev/block/bootdevice/by-name
- Note down the block address of boot_a/boot_b or init_boot_a/init_boot_b.
- In our case, they are:
init_boot_a -> /dev/block/sde32 init_boot_b -> /dev/block/sde63 - Then type in the below command and replace “address” with the block address of your boot_a/boot_b or init_boot_a/init_boot_b
dd if=/sdcard/boot.img of=/dev/block/address -->for boot_a dd if=/sdcard/boot.img of=/dev/block/address -->for boot_b dd if=/sdcard/init_boot.img of=/dev/block/address -->for init_boot_a dd if=/sdcard/init_boot.img of=/dev/block/address -->for init_boot_b
- In our case [init_boot_a and b], the above commands will transform to:
dd if=/sdcard/init_boot.img of=/dev/block/sde32 dd if=/sdcard/init_boot.img of=/dev/block/sde63
- The above command will flash the boot/init_boot to their respective slots.
- Now launch Magisk, tap on Install, and select Direct Install. Once done, hit Reboot.
- Upon reboot, you should still be rooted and have the stock init_boot installed.
- Moreover, now that you have the Restore Images option up and working, you can use it to install OTA updates on your rooted device.
That’s it. These were the steps to fix the issue of the Magisk Restore Images option missing/not working along the expected lines. If you have any queries concerning the aforementioned steps, do let us know in the comments. We will get back to you with a solution at the earliest.
Does your advice to download the stock firmware 7 boozimage apply even if my device is running LineageOS? Or should I rather use the bootimage from the LOS download site?
If you’re currently on LineageOS, then you’ll have to use the boot.img of LineageOS itself.