The script is designed to be non-intrusive, copying files to the EFI partition without renaming or moving critical system files.
However, the implementation of Clover on the Steam Deck is not without risks. It requires a fundamental alteration of the device’s boot structure. A misstep in installing Clover can result in the device failing to boot entirely, necessitating a recovery image and a potentially nerve-wracking reinstall of SteamOS. Furthermore, the Steam Deck’s unique A/B partition scheme for seamless OS updates can conflict with third-party bootloaders if not managed carefully. The process requires a user to be comfortable with the Linux command line, understanding concepts like mounting partitions and editing configuration files. steam deck clover dual boot