<< Solved >> Clover: In config.plist, I set scan to <false/>, with no boot entries defined

[b.kind]

Shot myself in the foot. Made a mistake and messed up my hackintosh.

In the config.plist, I set scan to <false/>, without first creating custom boot entries.
Now, clover shows zero entries. No way to boot macOS or the Recovery drive.

Does anyone know how I can access my drive, so I can edit the config.plist?
Do I need to run UniBeast again?

Does this have a simple, smart fix?

Clover is a black box to me. Any help would be greatly appreciated.

 

[b.kind]

No ideas, huh?

I am going to try reinstalling Clover using UniBeast.
I do NOT want it to reinstall the OS, just Clover, so I will have to duck out of the process somewhere.

Does anyone know if I will also need to re-run MultiBeast?

Oy. This small experiment quickly turned into a mess.

 

[b.kind]

Fixed.
Booted from unibeast disk, copied to old config.plist back into place.