[Magisk] FeraVolt:
FDE.AI autostart troubleshooting post​

FDE has several options to autostart on different systems and automatically chooses best option. But due to a lot of various custom ROMs & security things FDE may face unexpected troubles with autostart. I hope this post will help you in this case.

If you have MAGISK root method:

Update both Magisk base & Magisk manager to latest official or beta (not canary) working version on your device.

For yet unknown reasons FDE may not autostart if you have this modules installed:

Riru - EdXposed (SandHooK) (YAHFA version works, but not sure about it)

MagiskHide Props Config

Install latest FDE version via Magisk manager, not via recovery.

If still not autostarting - try to install universal FDE installer zip from this thread, not via repository.

If still not starting, check Magisk manager settings & make sure Magisk Core mode is turned

OFF

and reboot. If Magisk Core mode is automatically enabled again after reboot - then it's Magisk problem, try another Magisk version or switch to another root method, because none of modules will work in Magisk Core mode for you.

If you have SUPERSU root method:

Completely uninstall FDE.AI via recovery using THIS zip.

Update your root method to MAGISK - SuperSU is getting outdated, but if there is no choice, let's go on..

Update SuperSU to very latest working official (not anyhow modded) version. Or even completely uninstall SuperSU using THIS zip via recovery & fresh install SuperSU back (systemless mode is preferred).

Open SuperSU app settings and turn ON "Enable SU during boot" option.

Forget about init.d - latest SuperSU versions allow running scripts via own method via su.d and this method is much stable than init.d.

If you have systemless SuperSU this folder will be located at /su/su.d - no need to do anything.

If you have system SuperSU (no /su/su.d folder) this folder will be located at /system/su.d and there is no such folder - create in manually.

Install latest FDE universal installer zip via recovery, reboot & wait few minutes - should be working.

If not working, make sure you have

99fde.sh

file in /su/su.d/ or /system/su.d/ folder. If there is no such file, installation went wrong, try to manually mount /data and /system partitions in recovery before installing .zip.

If still no luck - proceed to next part of this post - 'bad cases'.

If you have another root method, or your case is bad:

It's highly recommended to use Magisk or SuperSU as root method, but if there is no choice or those methods are not working for you, let's move on.. We need to autostart FDE via init.d and set

SElinux

mode to permissive. Using custom ROMs (like Linage OS for ex.) in this case may help a lot because most SElinux & init.d troubles are most likely resolved there.

Completely uninstall FDE.AI via recovery using THIS zip.

Check if /system/etc/init.d folder exists - if not, manually create it.

Turn

SElinux

mode to permissive. In some custom ROMs this can be done in system settings. You also can do this by using THIS app. Make sure SElinux mode stays at 'permissive' after reboot.

Install latest FDE universal installer zip via recovery, reboot & wait few minutes - should be working.

If not working, make sure you have

99fde

file in /system/etc/init.d folder. If there is no such file, installation went wrong, try to manually mount /data and /system partitions in recovery before installing .zip.

If still not working, then your ROM doesn't support init.d init - you need to activate it manually. This can be done using THIS app. Or using Kernel Auditor app - emulate init.d option. After all reboot device & see if it works now.

If still no luck, try to run FDE manually via any terminal emulator app:

su
setenforce 0
/system/etc/fde.ai/r.sh

If this method worked out, you need to add this code somewhere to autostart. Tasker or Script manager app can be used for this for ex.

FDE.AI does have own optimized busybox binary which is automatically used, but if there is something wrong with your system partition, there can be a problem with busybox. If so, install THIS busybox via recovery.

Good luck.