Revision history for MagiskInstallationIssues


Revision [1023]

Last edited on 2021-03-30 04:30:55 by didgeridoohan
Additions:
It is also possible to dump the boot partition directly from the recovery terminal, by entering the following:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
That will save the device boot image to the internal storage, ready for you to patch.

Revision [1015]

Edited on 2021-03-20 02:30:54 by didgeridoohan
Additions:
If disabling verity through Magisk doesn't help, you can try the following command (provided that your device has a //vbmeta.img//):
%%
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
%%
Deletions:
This section of the guide is mainly kept for legacy devices. Do not tamper with dm-verity and encryption on modern devices if you do not know what you are doing.

Revision [1013]

Edited on 2021-03-19 12:47:43 by didgeridoohan
Additions:
If there's a "process error" when installing Magisk it is usually caused by the app not having storage permission. It might also be fixed by clearing data for the app.
Deletions:
If there's a "process error" when installing Magisk it is usually caused by the app not having storage permission (see above). It might also be fixed by clearing data for the app.

Revision [1012]

Edited on 2021-03-19 08:40:46 by didgeridoohan
Additions:
If there's a "process error" when installing Magisk it is usually caused by the app not having storage permission (see above). It might also be fixed by clearing data for the app.
Deletions:
If there's a "process error" when installing a module it is usually caused by the app not having storage permission (see above). It might also be fixed by clearing data for the app.

Revision [1011]

Edited on 2021-03-19 08:40:24 by didgeridoohan
Additions:
===**Process error**===
If there's a "process error" when installing a module it is usually caused by the app not having storage permission (see above). It might also be fixed by clearing data for the app.

Revision [1007]

Edited on 2021-03-17 08:15:12 by didgeridoohan
Additions:
Most of the time you can find the stock boot or recovery image in your factory image/firmware package/ROM. Unzip it and look for the boot.img file. If you're unsure on how to go about acquiring the stock boot/recovery image for your device, ask for help in your device's forum.
If you for some reason want to install Magisk by patching the boot or recovery image but you already have Magisk installed you might be able to find a copy of the image in /data/magisk_backup_<sha1 checksum>. Before patching, Magisk saves a copy of the untouched image there. Note that it's compressed, so you need to unpack it before flashing to your device.
Deletions:
Most of the time you can find the stock boot or recovery image in your factory image/firmware package/ROM. Unzip it and look for the boot.img file. If you're unsure on how to go about acquiring the stock boot image for your device, ask for help in your device's forum.
If you for reason want to install Magisk by patching the boot or recovery image but you already have Magisk installed you might be able to find a copy of the image in /data/magisk_backup_<sha1 checksum>. Before patching, Magisk saves a copy of the untouched image there. Note that it's compressed, so you need to unpack it before flashing to your device.

Revision [1006]

Edited on 2021-03-16 06:43:57 by didgeridoohan
Additions:
If you need tools for other operating systems (or have other reasons why the above examples don't work) they're just a web search away...

Revision [1004]

Edited on 2021-02-28 04:12:06 by didgeridoohan
Additions:
If you want to try doing it on your device you can test something like this: https://forum.xda-developers.com/t/tutorial-android-ota-payload-dumper-on-android.4061799/

Revision [1003]

Edited on 2021-02-28 02:59:23 by didgeridoohan
Additions:
Another way, if you have access to TWRP for your device, is that you can make a backup of your boot image in TWRP and then simply rename that backup file to .img.

Revision [1002]

Edited on 2021-02-28 01:11:03 by didgeridoohan
Additions:
On some devices you won't find an image file in the firmware, but a payload.bin file that you need to unpack to get to the boot image. A web search is your friend and this is a great time to practice your Google-Fu, but XDA member ipdev has a good description and example here: https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84572491
Deletions:
On some devices you won't find an image file in the firmware, but a payload.bin file that you need to unpack to get to the boot image. A web search is your friend here, but XDA member ipdev has a good description and example here: https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84572491

Revision [1001]

Edited on 2021-02-28 01:10:14 by didgeridoohan
Additions:
On some devices you won't find an image file in the firmware, but a payload.bin file that you need to unpack to get to the boot image. A web search is your friend here, but XDA member ipdev has a good description and example here: https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84572491

Revision [1000]

Edited on 2021-02-25 00:27:55 by didgeridoohan
Additions:
If you for reason want to install Magisk by patching the boot or recovery image but you already have Magisk installed you might be able to find a copy of the image in /data/magisk_backup_<sha1 checksum>. Before patching, Magisk saves a copy of the untouched image there. Note that it's compressed, so you need to unpack it before flashing to your device.
Deletions:
If you for reason want to install Magisk by patching the boot or recovery image but you already have Magisk installed you might be able to find a copy of the image in /data/magisk_backup_<sha1 checksum>. Before patching, Magisk saves a copy of the untouched image there.

Revision [999]

Edited on 2021-02-24 11:53:29 by didgeridoohan
Additions:
===**Where's my boot/recovery image for the Magisk app to patch**===
When trying to patch the boot or recovery image of your device with the Magisk app, you will first have to get a copy of the stock image, place this on your internal storage where it will be accessible for the app and then select it according to the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | instructions]]. After that you can flash the patched image to your device, either in recovery or through fastboot/download mode, Odin or similar
Most of the time you can find the stock boot or recovery image in your factory image/firmware package/ROM. Unzip it and look for the boot.img file. If you're unsure on how to go about acquiring the stock boot image for your device, ask for help in your device's forum.
If you for reason want to install Magisk by patching the boot or recovery image but you already have Magisk installed you might be able to find a copy of the image in /data/magisk_backup_<sha1 checksum>. Before patching, Magisk saves a copy of the untouched image there.
Deletions:
===**Where's my boot image for the Magisk app to patch**===
When trying to patch the boot image of your device with the Magisk app, you will first have to get a copy of your stock boot image, place this on your internal storage where it will be accessible for the app and then select it according to the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | instructions]]. After that you can flash the patched boot image (that you'll find in the Downloads directory on your internal storage) to your device, either in recovery or through fastboot/download mode, Odin or similar
Most of the time you can find the stock boot image in your factory image/firmware package/ROM. Unzip it and look for the boot.img file. If you're unsure on how to go about acquiring the stock boot image for your device, ask for help in your device's forum.

Revision [998]

Edited on 2021-02-24 10:54:39 by didgeridoohan
Additions:
If you're trying to find a stock boot image because you're moving from ""SuperSU"" to Magisk, there might be a backup of the stock boot image in /data that you can use.
Deletions:
If you're trying to find a stock boot image because you're moving from ""SuperSU"" to Magisk, there might be a backup of the stock boot image in /data/magisk_backup_<sha1 checksum> (compressed) that you can use.

Revision [975]

Edited on 2021-02-23 08:17:20 by didgeridoohan
Additions:
==**Can't install from the Magisk app**==
When trying to install/update either the app or Magisk in the Magisk app v8+, some users experience that nothing happens. Usually this is caused by having a custom hosts file, or similar, that is blocking the CDN used by the Magisk app (JSDelivr). The solution is to whitelist that URL.
If your custom recovery is a bit outdated, this might be the reason why the installation fails. Try letting the Magisk app patch your devices boot image and then flash this to your device, either in recovery or through fastboot/download mode, Odin or similar. See the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | release thread]] for instructions.
===**Where's my boot image for the Magisk app to patch**===
When trying to patch the boot image of your device with the Magisk app, you will first have to get a copy of your stock boot image, place this on your internal storage where it will be accessible for the app and then select it according to the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | instructions]]. After that you can flash the patched boot image (that you'll find in the Downloads directory on your internal storage) to your device, either in recovery or through fastboot/download mode, Odin or similar
Since Magisk app v8.0.0 the advanced settings/install options for dm-verity and forced encryption won't be available on most modern devices (see [[MagiskInstallation | Advanced Settings/Install Options]] for details). The tools are still there and may be accessed through various means.
If your device supports it, the app will auto-detect if your device is encrypted and if it’s recommended to keep dm-verity enabled and the “Preserve forced encryption” and “Preserve dm-verity” will then be enabled by default. If these options aren’t enabled, you can keep dm-verity and forced encryption by checking the options for this before installing a new version of Magisk through the app.
The boot image can usually be found in your device's factory image/firmware file. If you're using a custom ROM it's found in the ROM zip. //Also see "Where's my boot image for the Magisk app to patch" above//.
If you get a message when opening the Magisk app after installing or updating Magisk, that additional setup is required and that it fails, try uninstalling the Magisk app and install it again manually.
Deletions:
==**Can't install from the Manager**==
When trying to install either the Manager or Magisk in Magisk Manager v8+, some users experience that nothing happens. Usually this is caused by having a custom hosts file, or similar, that is blocking the CDN used by the Manager (JSDelivr). The solution is to whitelist that URL.
If your custom recovery is a bit outdated, this might be the reason why the installation fails. Try letting the Magisk Manager patch your devices boot image and then flash this to your device, either in recovery or through fastboot/download mode, Odin or similar. See the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | release thread]] for instructions.
===**Where's my boot image for the Manager to patch**===
When trying to patch the boot image of your device with the Magisk Manager, you will first have to get a copy of your stock boot image, place this on your internal storage where it will be accessible for the Manager and then select it according to the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | instructions]]. After that you can flash the patched boot image (that you'll find in the Downloads directory on your internal storage) to your device, either in recovery or through fastboot/download mode, Odin or similar
Since Magisk Manager v8.0.0 the advanced settings/install options for dm-verity and forced encryption won't be available on most modern devices (see [[MagiskInstallation | Advanced Settings/Install Options]] for details). The tools are still there and may be accessed through various means.
If your device supports it, the Manager will auto-detect if your device is encrypted and if it’s recommended to keep dm-verity enabled and the “Preserve forced encryption” and “Preserve dm-verity” will then be enabled by default. If these options aren’t enabled, you can keep dm-verity and forced encryption by checking the options for this before installing a new version of Magisk through the Manager.
The boot image can usually be found in your device's factory image/firmware file. If you're using a custom ROM it's found in the ROM zip. //Also see "Where's my boot image for the Manager to patch" above//.
If you get a message when opening the Magisk Managerm after installing or updating Magisk, that additional setup is required and that it fails, try uninstalling the Magisk Manager and install it again manually.

Revision [952]

Edited on 2020-11-12 23:56:04 by didgeridoohan
Additions:
==**Can't install from the Manager**==
When trying to install either the Manager or Magisk in Magisk Manager v8+, some users experience that nothing happens. Usually this is caused by having a custom hosts file, or similar, that is blocking the CDN used by the Manager (JSDelivr). The solution is to whitelist that URL.

Revision [938]

Edited on 2020-11-05 16:03:07 by didgeridoohan
Additions:
Since Magisk Manager v8.0.0 the advanced settings/install options for dm-verity and forced encryption won't be available on most modern devices (see [[MagiskInstallation | Advanced Settings/Install Options]] for details). The tools are still there and may be accessed through various means.
Deletions:
Since Magisk Manager v8.0.0 the install options for dm-verity and forced encryption won't be available on most modern devices (see [[MagiskInstallation | Install Options]] for details). The tools are still there and may be accessed through various means.

Revision [914]

Edited on 2020-11-03 02:35:43 by didgeridoohan
Additions:
If you're trying to find a stock boot image because you're moving from ""SuperSU"" to Magisk, there might be a backup of the stock boot image in /data/magisk_backup_<sha1 checksum> (compressed) that you can use.
If you see a message in the install log, stating "Invalid image: not signed", that simply means that your boot image isn’t signed. It’s perfectly normal and nothing to worry about.
===**Working with dm-verity and forced encryption**===
Since Magisk Manager v8.0.0 the install options for dm-verity and forced encryption won't be available on most modern devices (see [[MagiskInstallation | Install Options]] for details). The tools are still there and may be accessed through various means.
This section of the guide is mainly kept for legacy devices. Do not tamper with dm-verity and encryption on modern devices if you do not know what you are doing.
==**Keeping dm-verity and forced encryption**==
If your device supports it, the Manager will auto-detect if your device is encrypted and if it’s recommended to keep dm-verity enabled and the “Preserve forced encryption” and “Preserve dm-verity” will then be enabled by default. If these options aren’t enabled, you can keep dm-verity and forced encryption by checking the options for this before installing a new version of Magisk through the Manager.
If you install through recovery (either for the first time or as an update) run one or both of the following commands in a terminal emulator or in your recovery's terminal before installing:
==**Disabling dm-verity and forced encryption**==
Deletions:
If you're trying to find a stock boot image because you're moving from ""SuperSU"" to Magisk, there might be a backup of the stock boot image in /data (compressed) that you can use.
If you see a messag in the install log, stating "Invalid image: not signed", that simply means that your boot image isn’t signed. It’s perfectly normal and nothing to worry about.
===**Keeping dm-verity and forced encryption**===
The Manager will auto-detect if your device is encrypted and if it’s recommended to keep dm-verity enabled and the “Preserve forced encryption” and “Preserve dm-verity” will then be enabled by default. If these options aren’t enabled, you can keep dm-verity and forced encryption by checking the options for this before installing a new version of Magisk through the Manager. If you install through recovery (either for the first time or as an update) run one or both of the following commands in a terminal emulator or in your recovery's terminal before installing:
===**Disabling dm-verity and forced encryption**===

Revision [727]

Edited on 2019-10-15 15:38:55 by didgeridoohan
Deletions:
@@{{image url="https://img.shields.io/badge/-PayPal-blue.svg" title="" alt="PayPal"}}
Please don't hesitate to [[https://www.paypal.me/didgeridoohan | support the work involved]] in keeping this guide alive.@@
----

Revision [654]

Edited on 2019-07-22 14:25:27 by didgeridoohan
Additions:
@@{{image url="https://img.shields.io/badge/-PayPal-blue.svg" title="" alt="PayPal"}}
Please don't hesitate to [[https://www.paypal.me/didgeridoohan | support the work involved]] in keeping this guide alive.@@
----

Revision [571]

Edited on 2019-02-04 11:04:21 by didgeridoohan
Additions:
===**Additional setup failed**===
If you get a message when opening the Magisk Managerm after installing or updating Magisk, that additional setup is required and that it fails, try uninstalling the Magisk Manager and install it again manually.

Revision [570]

Edited on 2019-01-26 00:11:33 by didgeridoohan
Additions:
If you get this message, //"Cannot mount /vendor"//, when trying to install Magisk through TWRP it usually means you have a Treble device but the TWRP version you have installed is not Treble compatible. Simply find an updated Treble compatible TWRP for your device.
Deletions:
If you get this message, //"Cannot mount /vendor"//, when trying to install Magisk through TWRP it usually means you have a Treble device but the TWRP version you have installed is not Treble compatible. Simply find a updated TWRP for your device.

Revision [568]

Edited on 2019-01-18 14:59:02 by didgeridoohan
Additions:
%%echo KEEPVERITY=true>>/cache/.magisk
echo KEEPFORCEENCRYPT=true>>/cache/.magisk%%
If you can't access /data (TWRP can't decrypt, etc) you can instead use either /data/.magisk or/system/.magisk, but please note that using /system/.magisk isn't systemless.
Deletions:
%%echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk%%

Revision [500]

Edited on 2018-11-26 09:50:56 by didgeridoohan
Additions:
Most of the time you can find the stock boot image in your factory image/firmware package/ROM. Unzip it and look for the boot.img file. If you're unsure on how to go about acquiring the stock boot image for your device, ask for help in your device's forum.
Deletions:
Most or the time you can find the stock boot image in your factory image/firmware package/ROM. Unzip it and look for the boot.img file. If you're unsure on how to go about acquiring the stock boot image for your device, ask for help in your device's forum.

Revision [499]

Edited on 2018-11-26 09:50:13 by didgeridoohan
Additions:
When trying to patch the boot image of your device with the Magisk Manager, you will first have to get a copy of your stock boot image, place this on your internal storage where it will be accessible for the Manager and then select it according to the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | instructions]]. After that you can flash the patched boot image (that you'll find in the Downloads directory on your internal storage) to your device, either in recovery or through fastboot/download mode, Odin or similar
Deletions:
When trying to patch the boot image of your device with the Magisk Manager, you will first have to get a copy of your stock boot image, place this on your internal storage where it will be accessible for the Manager and then select it according to the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | instructions]]. After that you can flash the patched boot image (that you'll find in the MagiskManager directory on your internal storage) to your device, either in recovery or through fastboot/download mode, Odin or similar

Revision [496]

Edited on 2018-11-20 14:02:51 by didgeridoohan
Additions:
If you can't access /data (TWRP can't decrypt, etc) you can instead use either /cache/.magisk or/system/.magisk, but please note that using /system/.magisk isn't systemless.
If you can't access /data (TWRP can't decrypt, etc) you can instead use either /cache/.magisk or/system/.magisk, but please note that using /system/.magisk isn't systemless.
Deletions:
If you can't access /data (TWRP can't decrypt, etc) you can instead use one of these locations - /cache/.magisk, /.backup/.magisk or/system/.magisk. Note that using /system/.magisk isn't systemless.
If you can't access /data (TWRP can't decrypt, etc) you can instead use one of these locations - /cache/.magisk, /.backup/.magisk or/system/.magisk. Note that using /system/.magisk isn't systemless.

Revision [471]

Edited on 2018-10-18 05:31:08 by didgeridoohan
Additions:
===**Cannot mount /vendor**===
If you get this message, //"Cannot mount /vendor"//, when trying to install Magisk through TWRP it usually means you have a Treble device but the TWRP version you have installed is not Treble compatible. Simply find a updated TWRP for your device.

Revision [446]

Edited on 2018-09-09 03:32:29 by didgeridoohan
Additions:
If you can't access /data (TWRP can't decrypt, etc) you can instead use one of these locations - /cache/.magisk, /.backup/.magisk or/system/.magisk. Note that using /system/.magisk isn't systemless.
If you can't access /data (TWRP can't decrypt, etc) you can instead use one of these locations - /cache/.magisk, /.backup/.magisk or/system/.magisk. Note that using /system/.magisk isn't systemless.
Deletions:
If you can't access /data (TWRP can't decrypt, etc) you can instead use one of these locations - /cache/.magisk, /.backup/.magisk or/system/.magisk would also be possible locations for the file. Note that using /system/.magisk isn't systemless.
If you can't access /data (TWRP can't decrypt, etc) you can instead use one of these locations - /cache/.magisk, /.backup/.magisk or/system/.magisk would also be possible locations for the file. Note that using /system/.magisk isn't systemless.

Revision [445]

Edited on 2018-09-09 03:31:46 by didgeridoohan
Additions:
If you can't access /data (TWRP can't decrypt, etc) you can instead use one of these locations - /cache/.magisk, /.backup/.magisk or/system/.magisk would also be possible locations for the file. Note that using /system/.magisk isn't systemless.
If you can't access /data (TWRP can't decrypt, etc) you can instead use one of these locations - /cache/.magisk, /.backup/.magisk or/system/.magisk would also be possible locations for the file. Note that using /system/.magisk isn't systemless.
Deletions:
(If you can't access /data, /cache/.magisk, /.backup/.magisk or/system/.magisk would also be possible locations for the file. Note that using /system/.magisk isn't systemless.)
(If you can't access /data, /cache/.magisk, /.backup/.magisk or/system/.magisk would also be possible locations for the file. Note that using /system/.magisk isn't systemless.)

Revision [444]

Edited on 2018-09-09 03:21:41 by didgeridoohan
Additions:
Some devices need to keep dm-verity enabled to work properly. One example is some Huawei devices that might otherwise experience weird behaviour or bootloops.
Deletions:
Some devices need to keep dm-verity enabled to work properly. One example is some Huawei devices that might otherwise experience weird behaviour.

Revision [443]

Edited on 2018-09-09 02:59:00 by didgeridoohan
Additions:
(If you can't access /data, /cache/.magisk, /.backup/.magisk or/system/.magisk would also be possible locations for the file. Note that using /system/.magisk isn't systemless.)
(If you can't access /data, /cache/.magisk, /.backup/.magisk or/system/.magisk would also be possible locations for the file. Note that using /system/.magisk isn't systemless.)
Deletions:
(If you can't access data, /cache/.magisk, /.backup/.magisk or/system/.magisk would also be possible locations for the file. Note that using /system/.magisk isn't systemless.)
(If you can't access data, /cache/.magisk, /.backup/.magisk or/system/.magisk would also be possible locations for the file. Note that using /system/.magisk isn't systemless.)

Revision [442]

Edited on 2018-09-09 02:58:09 by didgeridoohan
Additions:
(If you can't access data, /cache/.magisk, /.backup/.magisk or/system/.magisk would also be possible locations for the file. Note that using /system/.magisk isn't systemless.)
(If you can't access data, /cache/.magisk, /.backup/.magisk or/system/.magisk would also be possible locations for the file. Note that using /system/.magisk isn't systemless.)

Revision [408]

Edited on 2018-09-04 01:33:49 by didgeridoohan
Additions:
The Manager will auto-detect if your device is encrypted and if it’s recommended to keep dm-verity enabled and the “Preserve forced encryption” and “Preserve dm-verity” will then be enabled by default. If these options aren’t enabled, you can keep dm-verity and forced encryption by checking the options for this before installing a new version of Magisk through the Manager. If you install through recovery (either for the first time or as an update) run one or both of the following commands in a terminal emulator or in your recovery's terminal before installing:
%%echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk%%
===**Disabling dm-verity and forced encryption**===
If you on the other hand want to disable either dm-verity or forced encryption, you can go about it the same way as described above. If you're using the .magisk file method, just change KEEPVERITY and/or KEEPFORCEENCRYPT in the commands to false:
%%echo KEEPVERITY=false>>/data/.magisk
echo KEEPFORCEENCRYPT=false>>/data/.magisk%%
If you have a completely stock boot image installed and still get this message, there's likely some kind of incompatibility between your device/ROM and Magisk (see [[MagiskHelp | Asking for help]] for info on what to provide when asking for support).
Deletions:
The Manager will auto-detect if your device is encrypted and if it’s recommended to keep dm-verity enabled and the “Preserve forced encryption” and “Preserve dm-verity” will then be enabled by default. If these options aren’t enabled, you can keep dm-verity and forced encryption by checking the options for this before installing a new version of Magisk through the Manager. The first time you install (or if you just want to update Magisk through the recovery) run one or both of the following commands in a terminal emulator or in your recovery's terminal before installing:
%%echo KEEPVERITY=true>>/cache/.magisk
echo KEEPFORCEENCRYPT=true>>/cache/.magisk%%
If you have a completely stock boot image installed and still get this message, there's likely some kind of incompatibility between your device/ROM and Magisk.

Revision [388]

Edited on 2018-08-14 05:05:23 by didgeridoohan
Additions:
If you're trying to find a stock boot image because you're moving from ""SuperSU"" to Magisk, there might be a backup of the stock boot image in /data (compressed) that you can use.
With ""SuperSU"", most of the times you can simply use the full unroot option in the ""SuperSU"" app and let it restore your stock boot image, alternatively use the full unroot option and then flash the stock boot image before installing Magisk. When moving from ""SuperSU"" to Magisk, you might have a backup of the stock boot image in /data (compressed).
When moving from ""SuperSU"" to Magisk there might be a backup of the stock boot image in /data (compressed) that you can use.
Deletions:
If you're trying to find a stock boot image because you're moving from SuperSU to Magisk, there might be a backup of the stock boot image in /data (compressed) that you can use.
With ""SuperSU"", most of the times you can simply use the full unroot option in the ""SuperSU"" app and let it restore your stock boot image, alternatively use the full unroot option and then flash the stock boot image before installing Magisk. When moving from SuperSU to Magisk, you might have a backup of the stock boot image in /data (compressed).
When moving from SuperSU to Magisk there might be a backup of the stock boot image in /data (compressed) that you can use.

Revision [387]

Edited on 2018-08-14 05:05:00 by didgeridoohan
Additions:
Most or the time you can find the stock boot image in your factory image/firmware package/ROM. Unzip it and look for the boot.img file. If you're unsure on how to go about acquiring the stock boot image for your device, ask for help in your device's forum.
If you're trying to find a stock boot image because you're moving from SuperSU to Magisk, there might be a backup of the stock boot image in /data (compressed) that you can use.
With ""SuperSU"", most of the times you can simply use the full unroot option in the ""SuperSU"" app and let it restore your stock boot image, alternatively use the full unroot option and then flash the stock boot image before installing Magisk. When moving from SuperSU to Magisk, you might have a backup of the stock boot image in /data (compressed).
When moving from SuperSU to Magisk there might be a backup of the stock boot image in /data (compressed) that you can use.
Deletions:
Most or the time you can find the stock boot image in your factory image/firmware package/ROM. Unzip it and look for the boot.img file. If you're unsure on how to go about acquiring the stock boot image for your device, ask for help in your device's forum.
With ""SuperSU"", most of the times you can simply use the full unroot option in the ""SuperSU"" app and let it restore your stock boot image, alternatively use the full unroot option and then flash the stock boot image before installing Magisk.

Revision [386]

Edited on 2018-08-14 05:00:54 by didgeridoohan
Additions:
The boot image can usually be found in your device's factory image/firmware file. If you're using a custom ROM it's found in the ROM zip. //Also see "Where's my boot image for the Manager to patch" above//.
Deletions:
The boot image can usually be found in your device's factory image/firmware file. If you're using a custom ROM it's found in the ROM zip.

Revision [364]

Edited on 2018-07-19 15:42:28 by didgeridoohan
Additions:
==**""SuperSU""**==
==**unSU script**==
==**Prerooted ROM**==
==**Dirty flash**==
Deletions:
**""SuperSU""**
**unSU script**
**Prerooted ROM**
**Dirty flash**

Revision [354]

Edited on 2018-07-19 15:27:56 by didgeridoohan
Additions:
**""SuperSU""**
Deletions:
**SuperSU**

Revision [353]

Edited on 2018-07-19 15:27:43 by didgeridoohan
Additions:
**SuperSU**
**unSU script**
**Prerooted ROM**
**Dirty flash**

Revision [315]

Edited on 2018-07-19 09:11:14 by didgeridoohan
Additions:
If you see a messag in the install log, stating "Invalid image: not signed", that simply means that your boot image isn’t signed. It’s perfectly normal and nothing to worry about.
Deletions:
If you see something like this in the install log when flashing a Magisk zip, it simply means that your boot image isn’t signed. It’s perfectly normal and nothing to worry about.
%%java.lang.ClassCastException: org.bouncycastle.asn1.DERApplicationSpecific cannot be cast to org.bouncycastle.asn1.ASN1Sequence
at com.topjohnwu.crypto.SignBoot$BootSignature.<init>(Unknown Source)
at com.topjohnwu.crypto.SignBoot.verifySignature(Unknown Source)
at com.topjohnwu.magisk.utils.BootSigner.main(Unknown Source)
Invalid image: not signed%%

Revision [306]

Edited on 2018-07-14 17:20:50 by didgeridoohan
Additions:
When trying to patch the boot image of your device with the Magisk Manager, you will first have to get a copy of your stock boot image, place this on your internal storage where it will be accessible for the Manager and then select it according to the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | instructions]]. After that you can flash the patched boot image (that you'll find in the MagiskManager directory on your internal storage) to your device, either in recovery or through fastboot/download mode, Odin or similar
Deletions:
When trying to patch the boot image of your device with the Magisk Manager, you will first have to get a copy of your stock boot image, place this on your internal storage where it will be accessible for the Manager and then select it according to the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | instructions]]. After that you can flash the patched boot image to your device, either in recovery or through fastboot/download mode, Odin or similar

Revision [305]

Edited on 2018-07-14 17:19:31 by didgeridoohan
Additions:
Most or the time you can find the stock boot image in your factory image/firmware package/ROM. Unzip it and look for the boot.img file. If you're unsure on how to go about acquiring the stock boot image for your device, ask for help in your device's forum.
Deletions:
If you're unsure on how to go about acquiring the stock boot image for your device, ask for help in your device's forum.

Revision [304]

Edited on 2018-07-14 02:53:27 by didgeridoohan
Additions:
%%echo KEEPVERITY=true>>/cache/.magisk
echo KEEPFORCEENCRYPT=true>>/cache/.magisk%%
Deletions:
%%echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk%%

Revision [282]

Edited on 2018-04-29 04:53:35 by didgeridoohan
Additions:
If you have a completely stock boot image installed and still get this message, there's likely some kind of incompatibility between your device/ROM and Magisk.
Deletions:
If you have a completely stock boot image installed, there's likely some kind of incompatibility between your device/ROM and Magisk.

Revision [281]

Edited on 2018-04-29 04:53:22 by didgeridoohan
Additions:
If you have a completely stock boot image installed, there's likely some kind of incompatibility between your device/ROM and Magisk.

Revision [205]

Edited on 2018-02-11 02:43:46 by didgeridoohan
Additions:
Otherwise, and this applies to any other root solution as well, you an use [[https://forum.xda-developers.com/member.php?u=4544860 | osm0sis]] [[http://forum.xda-developers.com/showpost.php?p=63615067 | unSU script]] (in recovery) and then flash your device's/ROM's stock boot image before installing Magisk, or you can dirty flash your ROM.
Deletions:
Otherwise, and this applies to any other root solution as well, you an use [[https://forum.xda-developers.com/member.php?u=4544860 | osm0sis]] [[http://forum.xda-developers.com/showpost.php?p=63615067 | unSU script]] (in recovery) and then flash your device's/ROM's stock boot image before installing Magisk.

Revision [202]

Edited on 2018-02-08 02:10:49 by didgeridoohan
Additions:
===**Installation through recovery fails**===
===**Invalid image: not signed**===
Deletions:
===**Installation in recovery fails**===
===**Invalid image not signed**===

Revision [181]

The oldest known version of this page was created on 2018-02-05 15:37:43 by didgeridoohan
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki