How to build your own iMac Pro [Successful Build/Extended Guide]

[kgp]

Thanks for the thorough guide!

Unfortunately I'm stuck trying to boot the install USB,

I get an error message saying com.Apple.WindowServer exited with abnormal code 1.

From previous posts I've gathered that it has something to do with the NvidiaGraphicsFixUp kext, but I can't figure out what I've done wrong. I've downloaded v1.2.2 of it, as well as Lilu 1.2.1 and AppleALC 1.2.2. There is something in the guide about compiling the kexts, but I have no idea what that means...

Any help would be appreciated

I would not see any relation of this error with NvidiaGraphicsFixUp kext. Please carefully read and strictly follow and apply my guide.

Thanks,

KGP

 

[kgp]

ah, that makes sense!

yeah i know, but how cool would it be to just pop in a vanilla usb key installer?

We pop in a vanilla USB installer! Anything else would be totally at odd with the forum rules. If you have now all additional required information within an EFI-Folder or directly implemented in the mobo BIOS makes absolutely no difference to me.

I still think that it is not worth to commit any efforts for an Ozmosis implementation..

However, this is certainly my personal opinion.. I don't want to minimise or hamper your personal enthusiasm...

 

[kgp]

The resulting file of Install macOS High Sierra occupies 5.21
It is right?

The createInstaller.sh.zip is no longer necessary to use it after doing all the previous steps, right?

Either you use createInstaller.sh, which does all steps automatically, or you follow my detailed guidelines and perform each step manually.

I guess, the idea is straight and clear, isn't it?

 

[kgp]

Thank you very much mgregrs, I have achieved it with the ""

Do you know if it is mandatory to disconnect the windows disk for installation?

No it is not mandatory to disconnect the windows disk before the OSX installation. In contrary it is indeed mandatory to disconnect all OSX drives before performing a Windows installation.

Cheers,

KGP

 

[kgp]

I have created the pkg installer that occupies 5.2 GB however the downloaded files occupy 5.69, I imagine it is because of the compression but when trying to create the "Install MacOS High Sierra.app" I get the following message in the terminal
View attachment 307520

I have replaced YOUR_SYSTEM_DISK logically by the name of the disk where the operating system is installed, which in my case is "High Sierra"

Can anybody help me?

Note that the correct unix convention to access a disk or folder called "High Sierra" is:

/Volumes/High\ Sierra/

If a directory's or disk's naming implements spaces, it is mandatory and totally unavoidable to use in Unix the "\" before the space in the naming!!!!! This is a very, very basic unix convention, which usually even somebody with just a more than rudimentary unix knowledge is aware of!!!!

With the command:

/Volumes/High Sierra/

OSX will never be able to find your /disk or folder "High Sierra" in "Volumes" !!!!!!

 

[shael]

Try to edit posts sometimes at the place of new ones

and you simply have to write with "High Sierra" because without "" you will have only Sierra
something like /Volumes/"Install High Sierra or something"/
voila

@PedroJSkywalker you can also put a \ before sierria. so it would look like /Volumes/Install \High \Sierra

edit: Just saw @kgp beat me to it!

 

[shael]

We pop in a vanilla USB installer! Anything else would be totally at odd with the forum rules. If you have now all additional required information within an EFI-Folder or directly implemented in the mobo BIOS makes absolutely no difference to me.

I still think that it is not worth to commit any efforts for an Ozmosis implementation..

However, this is certainly my personal opinion.. I don't want to minimise or hamper your personal enthusiasm...

yea i dont really care to do this, just would be cool to make it that much more native.

 

[kgp]

Hello KGP, the resulting file of Install macOS High Sierra occupies 5.21
It is right?

The createInstaller.sh.zip is no longer necessary to use it after doing all the previous steps, right?

Pedro, please try not to spam this thread with hundreds of mails implementing singular questions. Try to write a comprehensive but report that implements all your questions.

The above request you already posted before and it has ben answered by myself 4 min ago...

Cheers,

KGP

 

[kgp]

yea i dont really care to do this, just would be cool to make it that much more native.

What means much more native. Where is the difference in having the required information within either an EFI-Folder or an mainbaord BIOS?

Anyway. Let's stop with this discussion.. I guess it has no relevance, as an Ozmosis implementation in any case is not feasible at present.

 

[shael]

What means much more native. Where is the difference in having the required information within either an EFI-Folder or an mainbaord BIOS?

Anyway. Let's stop with this discussion.. I guess it has no relevance, as an Ozmosis implementation in any case is not feasible at present.

agreed, sorry for mentioning it and being off topic.