Get a shell without a live USB: rescue kernel parameters at the boot menu (Limine, GRUB, systemd-boot)
Almost all of it verified: Limine has an in-menu editor (CONFIG.md: editor_enabled, default yes) and cmdline: is the right key, systemd.unit=, systemd.mask=, nomodeset, fsck.mode=skip, init=/bin/bash and the SysV alias 3 are all real, and the /etc/limine-entry-tool.d/99-local.conf drop-in with KERNEL_CMDLINE[default]+=" ..." matches the exact syntax Omarchy uses in etc/limine-entry-tool.d/omarchy-defaults.conf. But the record contradicts itself and gives a dead-end escape: it correctly says rescue.target requires the root password, then recommends systemd.unit=rescue.target as the workaround for a machine where root has no password. rescue.service and emergency.service both run systemd-sulogin-shell, so rescue mode is exactly as unreachable as emergency mode on Omarchy's locked root. Also rd.break is offered without noting that Omarchy/Arch use mkinitcpio, not dracut, so it does nothing there.
init=/bin/bash leaves the root filesystem mounted read-only and journald not running. Remount rw before editing and remount ro (or sync) before power-cycling, or you will lose the edit or corrupt the filesystem. Anyone with physical access can use these parameters to get root without a password. That is exactly why full-disk encryption matters. On Omarchy the menu entries are unified kernel images, so a cmdline edited at the Limine prompt is only honoured when Secure Boot is off. If it appears to be ignored, boot a snapshot instead.
Symptom
"My machine boots to a black screen / hangs / drops straight into a failing graphical session and I don't have a USB stick handy. How do I get a root shell to fix it?" Common variants: a bad /etc/fstab line hangs the boot, a display manager crash-loops, a GPU driver update leaves nothing on screen after the boot menu, or systemd prints You are in emergency mode and refuses the root password.
Cause
Almost every one of these is recoverable by adding a kernel parameter for one boot. Boot loaders let you edit the command line of a menu entry before launching it, and both systemd and the kernel honour parameters that stop the boot early (before the display manager, before fstab mounts, or before KMS).
Fix
Keep the whole record except the no-root-password paragraph and add the mkinitcpio equivalents.
systemd.unit=rescue.target is NOT an escape from a locked root account: rescue.service and emergency.service both hand off to systemd-sulogin-shell, so rescue mode prompts for the same root password. On Omarchy (root locked, you use sudo) use one of these instead, at the boot menu:
systemd.mask=sddm.service 3 # normal boot without a display manager - log in as your own user, then sudo
systemd.debug_shell # root shell on tty9 with no password (Ctrl+Alt+F9)
init=/bin/bash # no systemd at all; root is read-only, remount rw as shown below
Once you can boot again, you can make emergency/rescue usable in future without setting a root password (understand that this removes the password gate for anyone with physical access):
sudo systemctl edit emergency.service # add: [Service]\n Environment=SYSTEMD_SULOGIN_FORCE=1
And rd.break is dracut-only. Omarchy and Arch use mkinitcpio. The equivalents there are:
break=premount stop in the initramfs before root is mounted
break=postmount stop after root is mounted, before the switch
disablehooks=plymouth skip one initramfs hook for this boot
Everything else is accurate as written: the Limine e editor and cmdline: line, GRUB e/Ctrl+X, systemd-boot e (editor yes in /boot/loader/loader.conf), the parameter table, the read-only remount dance under init=/bin/bash, and making a parameter stick via /etc/limine-entry-tool.d/99-local.conf plus sudo limine-mkinitcpio.
Verify
cat /proc/cmdline after booting shows the parameter you added. systemctl get-default and systemctl list-units --failed work from the rescue shell.