I could now try to reinstall the OS, or do a clean install onto my SSD. 've now got back to the stage where I can boot the system from a freshly made Sierra Unibeast USB stick. But it seems to create chaos and confusion within the whole boot regime. Sorry if this isn't the correct forum, but I couldn't find where else to raise this question.īackground: I think the reason for the problems with Clover has been my attempts to duplicate a working config file and then rename it. Is there a correct way of removing Clover from an SSD / hard drive and doing a clean install of Clover?Īnd does that require a clean install of the OS as well? Or might I get away with a reinstall of the OS? The thing is, I already tried that once and not only did it send me back into a spiral of an unbootable system, it also messed up my working Unibeast stick (hence the need for a fresh one). That sounds like it should be easy: mount the EFI partition, delete the relevant folder, and then maybe replace it with one that you know works. However, I'm certain that I need to delete the existing Clover installation, remove it completely and do a fresh install.
So once the OS starts to install, follow the on-screen instructions and enjoy your clean install. Again, installing a new OS, especially a clean install, is a matter of patience. I've now got back to the stage where I can boot the system from a freshly made Sierra Unibeast USB stick. Step 9: Now to install MacOS Sierra onto your primary drive, select it, and the process of installing the latest Mac OS from Apple will begin. After much research and countless reboots, I've decided the problem was, and is, a corruption (or something) of Clover.
I've been having serious problems with my system, which was running fine, but then became completely unbootable. Building a CustoMac Hackintosh: Buyer's Guide
0 kommentar(er)
