by MrQuickFX » 25. Oct 2018, 21:04
I didn't check in depth what steps does your program do, but from my point of view you could incorporate steps (at some point after initial MacOS install step - when everything is created on virtual drive) to mount EFI partition, copy needed drivers and script, restart and let the script take over. You can even place calls to specific boot.efi images (Install phase, normal phase). If there's install phase, it will boot file and continue with update/upgrade. If it's not install phase, it will show error but continue to next boot image you specify (that exists).
In short, boot process would go like this:
Call install efi file from MacOS Install map on destination drive. If it's there, it will start upgrade process (most of the time it's 2nd phase) and ignore rest of the script.
If it's not, it will say no map/file to execute and continue to next step where you call regular boot.efi as usual.
It's "dirty" solution but I think it might work. Even if there's some update when you have OS up and running on next boot it will update OS without digging through UEFI GUI to select proper file.
Last edited by
socratis on 25. Oct 2018, 21:33, edited 1 time in total.
Reason: Removed unnecessary verbatim quote of the whole previous message.