curtisy

GueGuerreiro Sorry for the late reply. Unfortunately I'm out of ideas on this one as well. I suspected it's a package that got deprecated which would make the rollback fail in some weird cases (looking at you megatools) but md5 missing looks even more weird.
What you could try, from a quick search in the Solus repository is follow this thread even if it's a bit old: https://dev.getsol.us/T5310

henriiquecampos From your live session, chroot into your installation and install the package as you usually would.
As a guideline on how to chroot, you can follow the Solus Troubleshooting article here https://getsol.us/articles/troubleshooting/boot-rescue/en/

Follow all of it (just to make sure it's not another package causing this) and afterwards, install the NVIDIA drivers as you usually would (probably something like sudo eopkg it nvidia-glx-driver-current)

GueGuerreiro You might want to try chrooting into your system and repairing whatever package is broken there. Only downside is that you need a live ISO of Solus.
See here for a quick HowTo: https://getsol.us/articles/troubleshooting/boot-rescue/en/

That being said, if you manage to get around it, could you post the output of the libcrypt error when attempting to rollback with sudo eopkg history -t {whatever version you want to rollback to} -d? there might be some workaround to get it to work