[Magisk] pndwal:
I assume you mean you installed Magisk normally in boot partition (flashed w/o Recovery mode selected), not in recovery, or flashed as .zip from custom recovery...

As mentioned, this suggests you have a Xiaomi A-only SAR device which is an exception to the rule that SAR A-only devices can only accommodate Magisk in boot partition.

Magisk's Ramdisk = No means no OEM ramdisk in boot is detected, so no 'fix' is needed for this; the ramdisk (initramfs) Magisk occupies in boot partition is 'manually' added / created by Magisk...

Even though you now actually have ramdisk in boot partition, Magisk continues to show Ramdisk = No for good reason: Only OEM ramdisk is an indication that Magisk in boot will work; generally Magisk-created ramdisk won't work on A-only SAR devices necessitating Magisk in recovery... It just happens to work on Xiaomi!

Nb. It's actually a good thing that you don't need to install Magisk in recovery ramdisk despite OEM not providing boot ramdisk as this is fraught and requires always booting system via recovery w/ John's special variation on recovery key-combo... On some such devices users must also boot w/ USB PC or headphones connected get system with Magisk...

Magisk Booting Process for Legacy SAR devices:

For those interested, here are technical details. Nb. This does not cover further changes for 2SI devices.

Since Xiaomi bootloaders are generally (if inexplicably) compatible w/ ramdisk in boot partition and Magisk (now) always creates the basic ramdisk required to accommodate Magisk if OEM ramdisk is missing (This commit: https://github.com/topjohnwu/Magisk/commit/e72c6685edf81706617a3444575c4500b9b8fe6c ) ramdisk in boot can actually be used by Magisk in A-only SAR devices, just as with their A/B counterparts. (Magisk uses the existing recovery ramdisk that was relocated to boot partition in A/B SAR devices whereas A-only SAR devices leave recovery ramdisk in recovery partition and no OEM ramdisk in boot is provided.)

With normal system boot on legacy system-as-root devices (in general A9+ where launched w/ A9) the kernel directly mounts the system partition as rootdir and executes /init to boot.

To boot system w/ Magisk on these devices, Magisk alters the booting process using the following components:

• Pre-Init:

ramdisk initramfs (rootfs) is used as initial rootdir and replaces init with magiskinit as the first program to run. This then

1) switches root to system as an 'Early mount partition'.

2) loads and/or compiles sepolicy.

3) patches sepolicy rules and dumps these to /sepolicy or /sbin/.se or /dev/.se.

4) patches init or libselinux.so to force the system to load the patched policies.

5) injects magisk services into init.rc.

6) executes the original init to continue the boot process.

• post-fs-data:

Next,

1) post-fs-data is triggered and /data is decrypted and mounted.

2) the magiskd daemon is launched

3) post-fs-data scripts are executed

4) module files are magic mounted.

• late_start:

Lastly, the class late_start is triggered, Magisk “service” mode is started and service scripts are then executed.

Refs:

• https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

• https://topjohnwu.github.io/Magisk/boot.html

• https://topjohnwu.github.io/Magisk/details.html#magisk-booting-process

👀 PW