Alright, let's try the following first before going further:
1.
config.plist on your USB flash disk (the one created by UniBeast) -- first make a backup copy of the file.
- Insert the USB flash disk on your working Mac, mount the EFI partition using EFI Mounter v3 and use latest version of Clover Configurator to edit the EFI/CLOVER/config.plist file.
- Enable verbose flag in the Boot section.
- In the SMBIOS section, click the pop-up icon near the bottom right side of the pane. It will pop up a long list of Mac models. Choose iMac18,1 from the pop-up menu. All of your SMBIOS fields should now be populated. Make sure the Trust flag is still checked on.
- I've posted my config.plist here. You're welcome to try it, but be sure to follow the above step to choose iMac18,1 because I've put dummy serial numbers in the file. My config.plist includes ACPI patches for renaming XHCI and XHC1 to XHC. This might (or might not) help your USB keyboard/mouse problems during installation.
- Save the modified config.plist.
2. If the cause of the hang is still
cannot convert this volume to AFPS then note some observations:
- The screenshot in Post #1 shows that the error occurred on disk23s1. This looks strange. It should be disk0s1 or disk1s1.
- Do you have a lot of disks plugged into the Hackintosh? Or do you have some disks with a lot of partitions?
- Is your Samsung EVO NVMe drive new?
- Do you have anything plugged into any other NVMe slots or any SATA ports?
- Do you have a spare SSD that you can temporarily use to install Mojave? The spare SSD can be a cheap $35 240GB 2.5" form factor. I have 3 of these SSDs installed in external USB 3.0 enclosures that I use for backup and test purposes.
- If you have a spare SSD, it might be a good idea to try and install Mojave onto that. If the "cannot convert to APFS" error goes away, then we can suspect something is wrong with the Samsung EVO (or with M.2 compatibility). But if the error persists, then at least we've ruled out any hardware or other fault with the Samsung EVO.
3. You have 2 copies of
FSInject-64.efi. I would suggest removing the one in the
drivers64 folder. It might be okay to remove that folder entirely.