MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[h9826790]

Included in the sticky 4,1/5,1 upgrade thread

How to: Boot Camp without a Boot Screen

I don't remember uninstalling any bootcamp drivers before 6. But I had to uninstall before 6.1

forums.macrumors.com

 

[jackluke]

Included in the sticky 4,1/5,1 upgrade thread

How to: Boot Camp without a Boot Screen

I don't remember uninstalling any bootcamp drivers before 6. But I had to uninstall before 6.1

forums.macrumors.com

You're right when you chose a Windows DVD rather than Windows USB installer, since it still contains the legacy bootloader, and when you remove the "bootcamp apps" , because, apart they don't detect more the APFS, starting from the Windows 10 (I guess from 1803 build) and on latest releases keeping "bootcamp apps" will produce "windows blue screen kernel panic", because apparently apple have dropped their Bootcamp software from Mojave.

 

[tsialex]

You're right when you chose a Windows DVD rather than Windows USB installer, since it still contains the legacy bootloader, and when you remove the "bootcamp apps" , because, apart they don't detect more the APFS, starting from the Windows 10 (I guess from 1803 build) and on latest releases keeping "bootcamp apps" will produce "windows blue screen kernel panic", because apparently apple have dropped their Bootcamp software from Mojave.

MP5,1 with W10 installed with CSM mode can use iMacPro1,1 BootCamp drivers and have APFS support and can go to macOS and back without problem, using BootCamp Control panel app or the taskbar icon in Windows and StartUp Disk while in macOS.

 

[jackluke]

MP5,1 with W10 installed with CSM mode can use iMacPro1,1 BootCamp drivers and have APFS support and can go to macOS and back without problem, using BootCamp Control panel app or the taskbar icon in Windows and StartUp Disk while in macOS.

Using the iMacPro1,1 bootcamp drivers the APFS Volume is detected only during the Bootcamp control panel or also in Windows explorer ?

I mean apple included some apfs drivers for windows 10?
I ask because they did for hfs+.

 

[h9826790]

also in Windows explorer ?

I mean apple included some apfs drivers for windows 10?

NO

 

[Danne32]

Hi.
I use the iMacPro1,1 in config, and my system clock is very slow but i can't the set CPU frequency values FSB nad ART frequency. How can i solve the slow clock?

 

[jackluke]

If I want to do this what parts of the code do I supplement with my system information, do I put my system serial number and MLB serial number?

Through OpenCore I have spoofed MacBook7,1 mid 2010 (Penryn C2D) as many supported Catalina machines using my stock serial number (and I guess also with my Main Logic Board SN), only things that changed were the Mac-ID and the system profiler model ids, just swapping the "SystemProductName" xml key, this is essentially the config I used:


<key>Emulate</key>
<dict>
<key>Cpuid1Data</key>
<data></data>
<key>Cpuid1Mask</key>
<data></data>
</dict>



<key>Automatic</key>
<true/>
<key>Generic</key>
<dict>
<key>SystemProductName</key>
<string>MacBookPro11,1</string>
<key>SystemSerialNumber</key>
<string></string>
</dict>
<key>UpdateDataHub</key>
<false/>
<key>UpdateNVRAM</key>
<false/>
<key>UpdateSMBIOS</key>
<true/>
<key>UpdateSMBIOSMode</key>
<string>Create</string>

 

[tsialex]

Through OpenCore I have spoofed MacBook7,1 mid 2010 (Penryn C2D) as many supported Catalina machines using my stock serial number (and I guess also with my Main Logic Board SN), only things that changed were the Mac-ID and the system profiler model ids, just swapping the "SystemProductName" xml key, this is essentially the config I used:


<key>Emulate</key>
<dict>
<key>Cpuid1Data</key>
<data></data>
<key>Cpuid1Mask</key>
<data></data>
</dict>



<key>Automatic</key>
<true/>
<key>Generic</key>
<dict>
<key>SystemProductName</key>
<string>MacBookPro11,1</string>
<key>SystemSerialNumber</key>
<string></string>
</dict>
<key>UpdateDataHub</key>
<false/>
<key>UpdateNVRAM</key>
<false/>
<key>UpdateSMBIOS</key>
<true/>
<key>UpdateSMBIOSMode</key>
<string>Create</string>

Catalina installer validates just two things, the board-id and if the VMM flag is enabled, so you need to spoof the board-id if you can't spoof the VMM flag.

 

[jackluke]

Catalina installer validates just two things, the board-id and if the VMM flag is enabled, so you need to spoof the board-id if you can't spoof the VMM flag.

Yes, I spoofed only the board-id, since my machine doesn't support the VMM flag, but I meant that I kept my original serial number and it worked too.

Just with this value empty OpenCore takes automatically my Macbook7,1 serial number:

<key>SystemSerialNumber</key>
<string></string>

 

[startergo]

Yes, I spoofed only the board-id, since my machine doesn't support the VMM flag, but I meant that I kept my original serial number and it worked too.

Just with this value empty it takes my serial number:

<key>SystemSerialNumber</key>
<string></string>

The problem with mix/match serial numbers with the boards may reflect imessage and face time. You can even get your account blocked by Apple

 

[tsialex]

Yes, I spoofed only the board-id, since my machine doesn't support the VMM flag, but I meant that I kept my original serial number and it worked too.

Just with this value empty it takes my serial number:

<key>SystemSerialNumber</key>
<string></string>

AFAIK, for running Catalina, the installer and the kernel don't check anything besides board-id/VMM combo.

Serial number is checked remotely by SystemReport to show the year-model and Messages/FaceTime checks SSN and several other hardware IDs - but nothing else is required to run Catalina itself.

 

[jackluke]

AFAIK, for running Catalina, the installer and the kernel don't check anything besides board-id/VMM combo.

Serial number is checked remotely by SystemReport to show the year-model and Messages/FaceTime checks SSN and several other hardware IDs - but nothing else is required to run Catalina itself.

Right, that's why after spoofing a supported Catalina machine, while opening "About this Mac" I still read my original Macbook, because of its serial number.

 

[Fairdinkem]

—- Warning!!! This config may brick your Mac. Do NOT use it unless you know what you are doing. —-

As a record. The following setting to simulate iMac Pro will cause black screen.


<key>PlatformInfo</key>
<dict>
<key>Automatic</key>
<true/>
<key>Generic</key>
<dict>
<key>MLB</key>
<string>C02706700J9JG36JA</string>
<key>ROM</key>
<data>ESIzAAAA</data>
<key>SpoofVendor</key>
<true/>
<key>SystemProductName</key>
<string>iMacPro1,1</string>
<key>SystemSerialNumber</key>
<string>C02T75Y5HX87</string>
<key>SystemUUID</key>
<string>EF81678C-50D7-4A13-9D1A-B423E7F7BE5B</string>
</dict>
<key>UpdateDataHub</key>
<true/>
<key>UpdateNVRAM</key>
<true/>
<key>UpdateSMBIOS</key>
<true/>
<key>UpdateSMBIOSMode</key>
<string>Create</string>
</dict>


Basically, UpdateSMBIOS = true will cause black screen.

I haven't have time to insert a Mac EFI UGA GPU or Remote Desktop to check what's happening yet. However, I highly suspect that the cMP actually booted to desktop with the above settings, because the Eject key works, Caps Lock key works, and Command + Control + power button also work.

If the cMP was jammed at loading screen, eject key shouldn't work.

And AFAIK, Command + Control + Power button only react properly inside macOS.

So, very high chance the cMP actually booted to desktop. However, using the iMac Pro SMBIOS cause the GPU fail to display properly.

Anyway, one more good news. PCIe info won't be mess up like using Clover. It's a good start.

I have followed your guide and created serial numbers etc in OC Configurator and edited the Config.Plist as per your demonstrated code - however after restarting the computer and verifying the computer has started using OC VMM flag using the terminal command the system still is not spoofing as an iMac Pro as far as I can tell, I check the system about info and it shows all my REAL system info. Is there any steps required beyond what is outlined in your guide that I may be missing?

My computer by the way is a Mac Pro 4,1 flashed to 5,1 with radeon 280x GPU

 

[startergo]

I have followed your guide and created serial numbers etc in OC Configurator and edited the Config.Plist as per your demonstrated code - however after restarting the computer and verifying the computer has started using OC VMM flag using the terminal command the system still is not spoofing as an iMac Pro as far as I can tell, I check the system about info and it shows all my REAL system info. Is there any steps required beyond what is outlined in your guide that I may be missing?

My computer by the way is a Mac Pro 4,1 flashed to 5,1 with radeon 280x GPU

Can You check the output:

nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

Also in the Update section did you check update SMBIOS (and remove Auto as it only applies the generic section)?

 

[jackluke]

I have followed your guide and created serial numbers etc in OC Configurator and edited the Config.Plist as per your demonstrated code - however after restarting the computer and verifying the computer has started using OC VMM flag using the terminal command the system still is not spoofing as an iMac Pro as far as I can tell, I check the system about info and it shows all my REAL system info. Is there any steps required beyond what is outlined in your guide that I may be missing?

My computer by the way is a Mac Pro 4,1 flashed to 5,1 with radeon 280x GPU

I'd suggest to don't mix the OC Configurator with a manual editing of config.plist , from my test new OpenCore version can parse old xml syntax, while the OC GUI editor maybe uses some new syntax, moreover when you manual edit the plist you must chose plain-text (not rich-text), and before spoofing the machine I guess you should unflag first the VMM cpumask editing the config.plist as in this part :

<key>Kernel</key>
    <dict>
        <key>Add</key>
        <array/>
        <key>Block</key>
        <array/>
        <key>Emulate</key>
        <dict>
            <key>Cpuid1Data</key>
            <data>AAAAAAAAAAAAAAAAAAAAAA==</data>
            <key>Cpuid1Mask</key>
            <data>AAAAAAAAAAAAAACAAAAAAA==</data>
        </dict>


</dict>

<key>PlatformInfo</key>
    <dict>
        <key>Automatic</key>
        <true/>
        <key>Generic</key>
        <dict>
            <key>SystemProductName</key>
            <string>iMacPro1,1</string>
            <key>SystemSerialNumber</key>
            <string></string>
        </dict>
        <key>UpdateDataHub</key>
        <false/>
        <key>UpdateNVRAM</key>
        <false/>
        <key>UpdateSMBIOS</key>
        <true/>
        <key>UpdateSMBIOSMode</key>
        <string>Create</string>
    </dict>

I suppose also @Danne32 that's why you get a slow clock, probably you have the VMM flag.

 

[startergo]

and before spoofing the machine I guess you should unflag first the VMM cpumask editing the config.plist in this part :

not necessarily. All you will get is iMacPro in a "virtual machine"

 

[h9826790]

I have followed your guide and created serial numbers etc in OC Configurator and edited the Config.Plist as per your demonstrated code - however after restarting the computer and verifying the computer has started using OC VMM flag using the terminal command the system still is not spoofing as an iMac Pro as far as I can tell, I check the system about info and it shows all my REAL system info. Is there any steps required beyond what is outlined in your guide that I may be missing?

My computer by the way is a Mac Pro 4,1 flashed to 5,1 with radeon 280x GPU

Can You check the output:

nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

I also agree with startergo, the first step is to check if you really boot from OpenCore

 

[tsialex]

I have followed your guide and created serial numbers etc in OC Configurator and edited the Config.Plist as per your demonstrated code - however after restarting the computer and verifying the computer has started using OC VMM flag using the terminal command the system still is not spoofing as an iMac Pro as far as I can tell, I check the system about info and it shows all my REAL system info. Is there any steps required beyond what is outlined in your guide that I may be missing?

My computer by the way is a Mac Pro 4,1 flashed to 5,1 with radeon 280x GPU

Do you have a Xeon processor that supports AppleHypervisor? Only Westmere, W36xxx and X56xx, Xeons supports it, no earlier Xeon have the requirements needed by AppleHypervisor.

Btw, why you want to spoof iMacPro1,1 with an AMD 280x? This GPU don't have hardware encoding at all.

 

[Danne32]

I'd suggest to don't mix the OC Configurator with a manual editing of config.plist , from my test new OpenCore version can parse old xml syntax, while the OC GUI editor maybe uses some new syntax, moreover when you manual edit the plist you must chose plain-text (not rich-text), and before spoofing the machine I guess you should unflag first the VMM cpumask editing the config.plist as in this part :

<key>Kernel</key>
    <dict>
        <key>Add</key>
        <array/>
        <key>Block</key>
        <array/>
        <key>Emulate</key>
        <dict>
            <key>Cpuid1Data</key>
            <data>AAAAAAAAAAAAAAAAAAAAAA==</data>
            <key>Cpuid1Mask</key>
            <data>AAAAAAAAAAAAAACAAAAAAA==</data>
        </dict>


</dict>

<key>PlatformInfo</key>
    <dict>
        <key>Automatic</key>
        <true/>
        <key>Generic</key>
        <dict>
            <key>SystemProductName</key>
            <string>iMacPro1,1</string>
            <key>SystemSerialNumber</key>
            <string></string>
        </dict>
        <key>UpdateDataHub</key>
        <false/>
        <key>UpdateNVRAM</key>
        <false/>
        <key>UpdateSMBIOS</key>
        <true/>
        <key>UpdateSMBIOSMode</key>
        <string>Create</string>
    </dict>

I suppose also @Danne32 that's why you get a slow clock, probably you have the VMM flag.

I do not use the VMM flag. I left the Cpuid1Data and Cpuid1Mask fields blank.

 

[jackluke]

I do not use the VMM flag. I left the Cpuid1Data and Cpuid1Mask fields blank.

For safety check the "VMM" from an OpenCore session opening a Catalina Terminal: sysctl machdep.cpu.features
Because if you used the config.plist attached in OP one time the VMM flag is stored even after a PRAM reset.
[automerge]1573742107[/automerge]
@tsialex I confirm what you wrote about latest firmware spoofing, using OpenCore 0.5.2 I have made another attempt of spoofing MacBook7,1 as iMac19,1 (the retina 5k ddr4 ram 2019 version) and I got this spoofed BootROM:

https://forums.macrumors.com/attachments/opencore-spoofing-macbook7-1-as-imac19-1-coffeelake-jpeg.877055/

IM19,1

1037.40.118.0.0 (1037.0.73.0.0) 10.15.2 beta 2 : 1037.60.5.0.0

 

[MoerBoer]

This might be off-topic, but this "issue" forced me to load Linux on Mac Pro 5.1.

Can I install Mojave this way ( even though it's officially supported ), and then be able to enable FileVault? I don't mind entering the information into a blank screen when booting ( I'm doing it right now with my Linux Mint 19.2 in any case )

 

[h9826790]

I do not use the VMM flag. I left the Cpuid1Data and Cpuid1Mask fields blank.

My recommendation is NOT to spoof SMBIOS WITHOUT VMM flash. Tests shows the CPU performance will drop a lot (about 40%)

Reason - unknown

But all my tests shows the same behaviour. The only way to resume CPU performance when spoofing at iMac Pro or 7,1 is by turning on the VMM flag.

 

[Danne32]

With VMM even worse, even slower the clock.

 

[jackluke]

This is a funny experiment, through OpenCore 0.5.2 spoofed MacBook7,1 as Vmware7,1 that should be a generic vmware fusion virtual machine, showing in systemprofiler as an Apple Device and a BootROM 182.0.0.0.0 it worked, with Catalina software update, and the internal laptop LCD display detected as an external apple thunderbolt display.

Hence I guess spoofing a machine as Vmware7,1 should be similar to enabling a VMM flag.

edit:
I noticed that I typed Vmware7,1 , anyway even typing in config.plist the SystemProductName as VMware7,1 it worked at the same way (Apple Device, BootROM 182.0.0.0.0).

 

[Ludacrisvp]

This might be off-topic, but this "issue" forced me to load Linux on Mac Pro 5.1.

Can I install Mojave this way ( even though it's officially supported ), and then be able to enable FileVault? I don't mind entering the information into a blank screen when booting ( I'm doing it right now with my Linux Mint 19.2 in any case )

I posted a thread on how to bypass the check for FileVault to be used in mojave with the 5,1.
The issue i understand is that the pre-boot environment that loads up to have you enter the password just causes the boot to hang, therefore its my understanding that you can't just enter it blindly ... you need to have a GPU that supports a UGA preboot environment (aka a 'mac' efi flashed GPU) or figure out how to get GOP cards working in the 5,1 like they do in the 3,1 via refind (but not via OC yet).