A
I mentioned this already in the other thread about FileVault, but wanted to report here also now that I have tried again. This method does not work for me, with a USB installer created via createinstallmedia and with a Sapphire RX 580 8GB card installed. I tried this method yesterday afternoon by chance before even seeing your post. The only step I did not do that time was the "gpt destroy" terminal command (but the drive was clean prior to formatting as APFS (encrypted). When running the installer after formatting the disk as APFS (encrypted), at the screen where I am supposed to choose the destination drive, the encrypted disk is greyed out. When I click on it, I get the message "You may not install to this volume because it is encrypted by FileVault"
I didn't think anything of it at the time, because Apple has disabled all other avenues of enabling FV on the cMP in Mojave. So I just reformatted the drive as plain APFS and proceeded with the install.
Then, in reading the new FileVault thread this afternoon you made a reference to this post. I was really surprised it worked for you, so I decided to try again just now. This time, I followed your directions exactly, including gpt destroy. Unfortunately, I ended up with the exact same result.
So at this point, it would be good to try to figure out why it worked for you and not for me. I think you said in the other thread that you used dosdude1's patcher to make your USB installer. So maybe that removes the "If Mac Pro 5,1, disallow installation onto encrypted volume" check--since I'd imagine it disables a lot of the other checks the installer does prohibiting install onto unsupported machines.
The only other possibility I can think of (less likely) is that the installer checks for the presence of an EFI GPU before allowing install onto an encrypted volume. But if that's the case then why didn't they include the same intelligence in the FV control panel so that users with Metal+EFI cards could enable FV after the fact?
Maybe some others can test this to make certain, but my hunch is that the key to making your method work is to use dosdude1's patcher to install Mojave. I bet it disables the 5,1-specific check for an encrypted install drive.
View attachment 791867
EDIT: Just want to confirm that it's dosdude1's patcher that allows this method to work. I created an installer with his tool and was allowed to install Mojave to my encrypted drive.
So the method W1SS posted does work, but the "magic" of it is dosdude1's patcher modifications to the Mojave installer (which makes sense since his patcher removes the other checks so Mojave can be installed on Mac models Apple no longer supports). The normal createinstallmedia installer will not allow Mojave to be installed on an encrypted volume on a cMP.