Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
What this will accomplish? Pre-boot configuration support is a BootROM resource and MP5,1 EFI requires UGA. RX 580 is GOP
I know but OC has some quirks to provide GOP in firmware where it is missing (I don't know if it will work though):
"
  • ProvideConsoleGop: YES
    • Enables GOP(Graphics output Protcol) which the macOS bootloader requires for console handle
How can I migrate from AptioMemoryFix?
Behaviour similar to that of AptioMemoryFix can be obtained by installing FwRuntimeServices driver and enabling the quirks listed below. Please note, that most of these are not necessary to be enabled. Refer to their individual descriptions in this document for more details.
• ProvideConsoleGop (UEFI quirk)
.....
"
 
I know but OC has some quirks to provide GOP in firmware where it is missing (I don't know if it will work though):
"
  • ProvideConsoleGop: YES
    • Enables GOP(Graphics output Protcol) which the macOS bootloader requires for console handle
How can I migrate from AptioMemoryFix?
Behaviour similar to that of AptioMemoryFix can be obtained by installing FwRuntimeServices driver and enabling the quirks listed below. Please note, that most of these are not necessary to be enabled. Refer to their individual descriptions in this document for more details.
• ProvideConsoleGop (UEFI quirk)
.....
"
Ok, but why the eGPU spoof?
 
  • Like
Reactions: h9826790
Ok, but why the eGPU spoof?
No that was just an idea because we can't get the console output just by spoofing imacpro1.1 or cMP7.1 yet, but the macmini somehow provides boot screen. I wish we knew how it is hooked in the registry so it can see it.
 
No that was just an idea because we can't get the console output just by spoofing imacpro1.1 or cMP7.1 yet, but the macmini somehow provides boot screen. I wish we knew how it is hooked in the registry so it can see it.
2018 Mac mini has eGPU pre-boot configuration support because the last BootROM upgrade implemented it. Now the BootROM provides pre-boot configuration support for eGPU connected screens and not just the integrated GPU.

We can't spoof that.
 
Premise: I have read that doing this from a "Sandy Bridge" spoofing as "Ivy Bridge" (that is the minimum natively Catalina supported architecture with i5 cpu), the OpenCore SMBIOS spoofing worked.

I ask this because I guess spoofing among too different board architecture might lead to a brick, I am on MacBook7,1 mid 2010, but I can assure that with a MacBookPro/Air 2011 (Sandy Bridge) OpenCore SMBIOS spoofing as an iMac 2012 worked. My doubt is about from "Core2Duo Penryn" to "Ivy Bridge".

Hence to those who already tested the OpenCore SMBIOS spoofing (example a MacPro5,1 as a Mojave supported iMac 2012), could it work too if I try to spoof a "C2D Penryn architecture" to an "Ivy Bridge" ?

I found the answer to the question I posted on my own, taking a bit risk of bricking the EFI firmware, but since can't use the "VMM flag" on my machine then through OpenCore bootloader and a config I tried to spoof my MacBook 2010 as a supported Catalina iMac, moreover I jumped even forward than an "Ivy bridge", from "Core2Duo Penryn" to "Haswell".

Not bad.
 

Attachments

  • Screenshot 2019-11-08 at 11.43.00.png
    Screenshot 2019-11-08 at 11.43.00.png
    865 KB · Views: 277
  • Image 2019-11-08 at 12.38.06.jpeg
    Image 2019-11-08 at 12.38.06.jpeg
    86.2 KB · Views: 268
  • Image 2019-11-08 at 12.38.06-2.jpeg
    Image 2019-11-08 at 12.38.06-2.jpeg
    103.2 KB · Views: 277
  • Screenshot 2019-11-08 at 12.43.35.png
    Screenshot 2019-11-08 at 12.43.35.png
    790 KB · Views: 282
  • Screenshot 2019-11-08 at 15.53.33.png
    Screenshot 2019-11-08 at 15.53.33.png
    72.2 KB · Views: 223

Not bad at all. (I would encourage you here to recall post #95.)

Upgraded enough, the Mac Pro 5,1 can run a functional macOS Catalina system unmodified, unlike your MacBook. I wonder now if you could collect all the necessary modifications for your MacBook and apply them to a vanilla installation entirely with OC... The outcome could illustrate what is possible for the 5,1 down the line.
 
  • Like
Reactions: jackluke
Not bad at all. (I would encourage you here to recall post #95.)

Upgraded enough, the Mac Pro 5,1 can run a functional macOS Catalina system unmodified, unlike your MacBook. I wonder now if you could collect all the necessary modifications for your MacBook and apply them to a vanilla installation entirely with OC... The outcome could illustrate what is possible for the 5,1 down the line.
That may be possible if you look into the dosdude's installer USB. The kexts are there.
 
Not bad at all. (I would encourage you here to recall post #95.)

Upgraded enough, the Mac Pro 5,1 can run a functional macOS Catalina system unmodified, unlike your MacBook. I wonder now if you could collect all the necessary modifications for your MacBook and apply them to a vanilla installation entirely with OC... The outcome could illustrate what is possible for the 5,1 down the line.

Yes, I already noticed a similar thing, Catalina OTA update is downloaded in this path /Volumes/Catalina Data/Library/Updates/
inside there are placed the packages and also the FirmwareUpdate.pkg , after clicking install the OTA stage1 installer prepares the drive, then auto-reboot, after triggers some kind of firmware update showing the apple big loading bar, I have immediately power-off , probably wasn't necessary, then holding alt-option I continued the installation from OTA stage2 installer "macOS Install data".

You wrote about spoofing the latest iMac firmware through OpenCore, this is useful in order to avoid an attempt of OTA firmware EFI update, either if should fail automatically without bricking the machine.
 
Yes, I already noticed a similar thing, Catalina OTA update is downloaded in this path /Volumes/Catalina Data/Library/Updates/
inside there are placed the packages and also the FirmwareUpdate.pkg , after clicking install the OTA stage1 installer prepares the drive, then auto-reboot, after triggers some kind of firmware update showing the apple big loading bar, I have immediately power-off , probably wasn't necessary, then holding alt-option I continued the installation from OTA stage2 installer "macOS Install data".

You wrote about spoofing the latest iMac firmware through OpenCore, this is useful in order to avoid an attempt of OTA firmware EFI update, either if should fail automatically without bricking the machine.
How is your cooling and sensors? Don't they need virtual SMC?
 
You wrote about spoofing the latest iMac firmware through OpenCore, this is useful in order to avoid an attempt of OTA firmware EFI update, either if should fail automatically without bricking the machine.
I don't think that spoofing a Mac that is having firmware upgrades frequently is safe. Since you have a MB2010, Your best bet is to use a Mac that Apple is not constantly sending updates, like MacBook 13" mid-2012 (MacBookPro9,2). Even with this, you will have BootROM upgrades sometime down the road.
 
How is your cooling and sensors? Don't they need virtual SMC?

At the beginning the overall temperatures increased a bit, then they settled down, however I just spoof for the time of an upgrade, after I don't boot more from OpenCore but from apple startup manager and MacBook returned to its default board values even without PRAM reset.

Sensors are still detected (also the battery temperature), I don't used special detailed apps, just Macs Fan Control.
 
Last edited:
  • Like
Reactions: octoviaa
This is a preliminary account of how to use the excellent OpenCore (OC) bootloader on a Mac Pro 5,1 to install, run, and update macOS Catalina, resulting in a clean, unpatched operating system no different than what you would find on a supported Mac.

This documentation is an ongoing process. The steps here are subject to change as more testing gets done.

1. Test Setup

Variations of this setup are likely possible:

Disk A. Newly APFS-formatted drive (GUID scheme)

This is where OC and a clean install of Catalina will go.

Disk B. macOS Mojave

Installation and configuration will be done from here.

C. Non-bootscreen graphics card

Of course, a flashed card can't hurt.

2. Materials

A. The application "Install macOS Catalina" (the full installer)

B. OpenCore

See the releases page of the project site. Download OpenCore-0.5.2-RELEASE.zip. The uncompressed folder will be referred to here as "OpenCore."

C. Support files

See the releases page of the project site. Download AppleSupport-2.1.2-RELEASE.zip. The uncompressed folder will be referred to here as "AppleSupport."

D. Configuration file

Provided in this post. Download config.zip. The uncompressed file is "config.plist".

Most important is the manual located at OpenCore/Docs/Configuration.pdf. By reading the manual you will be able to better understand the settings in the configuration file. For a sustainable use of OC, it is important that you read the manual.

The configuration described in this guide should be safe, but please be aware of the following:

WARNING!
Using OpenCore without extensive knowledge of the configuration options
may lead to a bricked Mac.

Because OC is in active development, the configuration file for the current version (0.5.2) will likely be incompatible with future versions.

3. Installing OC

a) Mount the EFI partition of Disk A: To find the identifier of the partition, enter the following in terminal:
Code:
diskutil list

The identifier will be something like "disk0s1;" the next step will assume that this is the case.
Code:
sudo diskutil mount /dev/disk0s1

You may need to authorize this. The partition should mount as /Volumes/EFI and appear as "EFI" in Finder.

b) Copy the OpenCore/EFI folder to the EFI partition. The resulting folder, /Volumes/EFI/EFI, should contain the folders OC and BOOT.

c) Copy AppleSupport/Drivers/FwRuntimeServices.efi to /Volumes/EFI/EFI/OC/Drivers.

d) Copy config.plist to /Volumes/EFI/EFI/OC.

4. Configuration

The file config.plist can be edited with any plist editor and even with TextEdit; the following steps will assume TextEdit.

a) Open config.plist with TextEdit.

b) Enable the VMM flag: Find the Cpuid1Mask entry, and carefully change AAAAAAAAAAAAAAAAAAAAAA== to AAAAAAAAAAAAAACAAAAAAA==. The value should now be the same as for Cpuid1Data.

c) Enable boot entry preservation: Find the RequestBootVarRouting entry, and change false to true.

d) Close the file. It should be saved automatically (select OK if informed about there being no permanent version storage).

The purpose of doing these steps explicitly is to be able to reverse them if desired.

5. Booting

a) Reboot into recovery mode by entering
Code:
sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery

You may need to authorize this. Be patient. Mac Pro boot times can be long, especially when booting into recovery mode.

b) Carry out step 3a (sudo is not needed in recovery).

c) Set the partition for booting:
Code:
bless --mount /Volumes/EFI --setBoot

d) Shut down the Mac and do an SMC reset (unplug the power cord, wait 15 seconds, plug the power cord back in, wait 5 seconds, and then press the power button).

Remark: Being installed on Disk A, OC can have trouble seeing Disk B. Doing an SMC reset helps ensure that Disk B is seen when OC starts.

e) Power up the machine. OC should boot Disk B (currently the only macOS system).

Be patient. Mac Pro boot times can be long. If it seems that the machine is not booting up. Hold the power button to shut down the machine. Do an NVRAM reset on the next power up (immediately press and hold Option, Command, P, and R, and release after 20 seconds or after you hear the second startup chime). The Mac should boot without OC. Recheck all the steps above.

f) Booted into the system on Disk B, verify that it is indeed OC that has booted the system by entering this in terminal:
Code:
nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

You should see REL-052-2019-10-30.

You can also verify that the VMM flag is present by entering
Code:
sysctl machdep.cpu.features

Congratulations for making it this far! The hard part is done.

6. Installing Catalina

a) Booted into the system on Disk B, run Install macOS Catalina. Install to Disk A.

The machine will reboot and eventually you should see the installation progress bar.

b) Complete the installation.

From now on, OC should boot Catalina on Disk A by default. In any case, OC will respect the selection in Startup Disk; however, be mindful of the remark in step 5d. Also, by carrying out step 5a, OC should boot the recovery mode corresponding to the system currently booted into.

7. Updates

As long as the VMM flag is present, Software Update should just work.

8. Post Install

To make the system as native as possible while still using OC, the VMM flag can be disabled by reversing step 4b. This might be a good idea until the long term effects of having the VMM flag enabled on a non-virtualized system are clarified.

9. Platform Information

It is possible to use OC to customize platform information. You may want to preserve some of the original identifiers.

The MLB can be obtained by entering the following in terminal:
Code:
nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB | awk '{ print $NF }'

There is also the serial number of the processor tray:
Code:
ioreg -l -p IODeviceTree | awk '/"processor-memory-board-serial-number"/ {gsub(/\"/,""); print $NF}'

The ROM (in Base64, suitable for entry using TextEdit) can be obtained with
Code:
nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM | awk '{split($NF,chars,""); for(n=0;n<256;n++){ord[sprintf("%c",n)]=n}; i=1; j=0; while(i<=length($NF)){if(substr($NF,i,1)=="%"){printf "%s",toupper(substr($NF,i+1,2)); i=i+2} else {printf "%x",toupper(ord[chars[i]])} j=j+2; i++} print("")}' | xxd -r -p | base64

The SSN can be obtained with
Code:
ioreg -l -p IODeviceTree | awk '/"IOPlatformSerialNumber"/ {gsub(/\"/,""); print $NF}'

and the system UUID with
Code:
ioreg -l -p IODeviceTree | awk '/"system-id"/ {print toupper(substr($NF,2,8)"-"substr($NF,10,4)"-"substr($NF,14,4)"-"substr($NF,18,4)"-"substr($NF,22,12))}'


10. Disabling OC

a) Carry out step 3a.

b) Open config.plist with TextEdit.

c) Reverse step 4c.

d) Reboot.

e) Select the desired entry in Startup Disk.

f) Reboot.

It is also possible to boot Catalina natively, after using recovery to add the "-no_compat_check" boot argument. In this case replace step c above by 5a. In recovery, enter
Code:
nvram boot-args="-no_compat_check"

and then carry out steps d and e in recovery. Catalina should boot without OC.

Failure to add the "-no_compat_check" boot argument may result in the machine suddenly shutting down when booting into Catalina. Although OC adds this argument, booting without OC does not guarantee that the argument will be there, unless it is added as described above.

11. Uninstalling OC

a) Disable OC (see 10).

b) Carry out step 3a.

c) Delete the /Volumes/EFI/EFI folder.

Acknowledgements

A big thank you to the talented developers of OpenCore for making all of this possible.
I have a problem, I followed all the steps to start from Oc and everything went well.
Now I would like to return to the configuration without oc, but following steps 10 and 11, there is no longer Catalina.

I suspect one of the operations went to change approaches to the start.
Can you help me restore the initial configuration?
vmm flag is aaaaaaaaaaaaaaaaaaa?
 
I have a problem, I followed all the steps to start from Oc and everything went well.
Now I would like to return to the configuration without oc, but following steps 10 and 11, there is no longer Catalina.

I suspect one of the operations went to change approaches to the start.
Can you help me restore the initial configuration?
vmm flag is aaaaaaaaaaaaaaaaaaa?

I guess you should re-edit your config.plist where is the VMM flag, this way and re-run OpenCore:

Code:
<key>Emulate</key>
        <dict>
            <key>Cpuid1Data</key>
            <data>AAAAAAAAAAAAAAAAAAAAAA==</data>
            <key>Cpuid1Mask</key>
            <data>AAAAAAAAAAAAAACAAAAAAA==</data>
        </dict>
 
Now I would like to return to the configuration without oc, but following steps 10 and 11, there is no longer Catalina.

If your setup is like the one described in the guide, boot into Mojave and confirm (a) that you are not booted through OC and (b) that the "-no_compat_check" boot argument is present. Then you should be able to boot into Catalina natively by selecting the corresponding disk in Startup Disk.
[automerge]1573231171[/automerge]
Code:
<key>Emulate</key>
        <dict>
            <key>Cpuid1Data</key>
            <data>AAAAAAAAAAAAAAAAAAAAAA==</data>
            <key>Cpuid1Mask</key>
            <data>AAAAAAAAAAAAAACAAAAAAA==</data>
        </dict>

Strictly speaking, to restore the original configuration, the data entries should actually be reversed here.
 
Last edited:
  • Like
Reactions: jackluke
This is a preliminary account of how to use the excellent OpenCore (OC) bootloader on a Mac Pro 5,1 to install, run, and update macOS Catalina, resulting in a clean, unpatched operating system no different than what you would find on a supported Mac.

This documentation is an ongoing process. The steps here are subject to change as more testing gets done.

1. Test Setup

Variations of this setup are likely possible:

Disk A. Newly APFS-formatted drive (GUID scheme)

This is where OC and a clean install of Catalina will go.

Disk B. macOS Mojave

Installation and configuration will be done from here.

C. Non-bootscreen graphics card

Of course, a flashed card can't hurt.

2. Materials

A. The application "Install macOS Catalina" (the full installer)

B. OpenCore

See the releases page of the project site. Download OpenCore-0.5.2-RELEASE.zip. The uncompressed folder will be referred to here as "OpenCore."

C. Support files

See the releases page of the project site. Download AppleSupport-2.1.2-RELEASE.zip. The uncompressed folder will be referred to here as "AppleSupport."

D. Configuration file

Provided in this post. Download config.zip. The uncompressed file is "config.plist".

Most important is the manual located at OpenCore/Docs/Configuration.pdf. By reading the manual you will be able to better understand the settings in the configuration file. For a sustainable use of OC, it is important that you read the manual.

The configuration described in this guide should be safe, but please be aware of the following:

WARNING!
Using OpenCore without extensive knowledge of the configuration options
may lead to a bricked Mac.

Because OC is in active development, the configuration file for the current version (0.5.2) will likely be incompatible with future versions.

3. Installing OC

a) Mount the EFI partition of Disk A: To find the identifier of the partition, enter the following in terminal:
Code:
diskutil list

The identifier will be something like "disk0s1;" the next step will assume that this is the case.
Code:
sudo diskutil mount /dev/disk0s1

You may need to authorize this. The partition should mount as /Volumes/EFI and appear as "EFI" in Finder.

b) Copy the OpenCore/EFI folder to the EFI partition. The resulting folder, /Volumes/EFI/EFI, should contain the folders OC and BOOT.

c) Copy AppleSupport/Drivers/FwRuntimeServices.efi to /Volumes/EFI/EFI/OC/Drivers.

d) Copy config.plist to /Volumes/EFI/EFI/OC.

4. Configuration

The file config.plist can be edited with any plist editor and even with TextEdit; the following steps will assume TextEdit.

a) Open config.plist with TextEdit.

b) Enable the VMM flag: Find the Cpuid1Mask entry, and carefully change AAAAAAAAAAAAAAAAAAAAAA== to AAAAAAAAAAAAAACAAAAAAA==. The value should now be the same as for Cpuid1Data.

c) Enable boot entry preservation: Find the RequestBootVarRouting entry, and change false to true.

d) Close the file. It should be saved automatically (select OK if informed about there being no permanent version storage).

The purpose of doing these steps explicitly is to be able to reverse them if desired.

5. Booting

a) Reboot into recovery mode by entering
Code:
sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery

You may need to authorize this. Be patient. Mac Pro boot times can be long, especially when booting into recovery mode.

b) Carry out step 3a (sudo is not needed in recovery).

c) Set the partition for booting:
Code:
bless --mount /Volumes/EFI --setBoot

d) Shut down the Mac and do an SMC reset (unplug the power cord, wait 15 seconds, plug the power cord back in, wait 5 seconds, and then press the power button).

Remark: Being installed on Disk A, OC can have trouble seeing Disk B. Doing an SMC reset helps ensure that Disk B is seen when OC starts.

e) Power up the machine. OC should boot Disk B (currently the only macOS system).

Be patient. Mac Pro boot times can be long. If it seems that the machine is not booting up. Hold the power button to shut down the machine. Do an NVRAM reset on the next power up (immediately press and hold Option, Command, P, and R, and release after 20 seconds or after you hear the second startup chime). The Mac should boot without OC. Recheck all the steps above.

f) Booted into the system on Disk B, verify that it is indeed OC that has booted the system by entering this in terminal:
Code:
nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

You should see REL-052-2019-10-30.

You can also verify that the VMM flag is present by entering
Code:
sysctl machdep.cpu.features

Congratulations for making it this far! The hard part is done.

6. Installing Catalina

a) Booted into the system on Disk B, run Install macOS Catalina. Install to Disk A.

The machine will reboot and eventually you should see the installation progress bar.

b) Complete the installation.

From now on, OC should boot Catalina on Disk A by default. In any case, OC will respect the selection in Startup Disk; however, be mindful of the remark in step 5d. Also, by carrying out step 5a, OC should boot the recovery mode corresponding to the system currently booted into.

7. Updates

As long as the VMM flag is present, Software Update should just work.

8. Post Install

To make the system as native as possible while still using OC, the VMM flag can be disabled by reversing step 4b. This might be a good idea until the long term effects of having the VMM flag enabled on a non-virtualized system are clarified.

9. Platform Information

It is possible to use OC to customize platform information. You may want to preserve some of the original identifiers.

The MLB can be obtained by entering the following in terminal:
Code:
nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB | awk '{ print $NF }'

There is also the serial number of the processor tray:
Code:
ioreg -l -p IODeviceTree | awk '/"processor-memory-board-serial-number"/ {gsub(/\"/,""); print $NF}'

The ROM (in Base64, suitable for entry using TextEdit) can be obtained with
Code:
nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM | awk '{split($NF,chars,""); for(n=0;n<256;n++){ord[sprintf("%c",n)]=n}; i=1; j=0; while(i<=length($NF)){if(substr($NF,i,1)=="%"){printf "%s",toupper(substr($NF,i+1,2)); i=i+2} else {printf "%x",toupper(ord[chars[i]])} j=j+2; i++} print("")}' | xxd -r -p | base64

The SSN can be obtained with
Code:
ioreg -l -p IODeviceTree | awk '/"IOPlatformSerialNumber"/ {gsub(/\"/,""); print $NF}'

and the system UUID with
Code:
ioreg -l -p IODeviceTree | awk '/"system-id"/ {print toupper(substr($NF,2,8)"-"substr($NF,10,4)"-"substr($NF,14,4)"-"substr($NF,18,4)"-"substr($NF,22,12))}'


10. Disabling OC

a) Carry out step 3a.

b) Open config.plist with TextEdit.

c) Reverse step 4c.

d) Reboot.

e) Select the desired entry in Startup Disk.

f) Reboot.

It is also possible to boot Catalina natively, after using recovery to add the "-no_compat_check" boot argument. In this case replace step c above by 5a. In recovery, enter
Code:
nvram boot-args="-no_compat_check"

and then carry out steps d and e in recovery. Catalina should boot without OC.

Failure to add the "-no_compat_check" boot argument may result in the machine suddenly shutting down when booting into Catalina. Although OC adds this argument, booting without OC does not guarantee that the argument will be there, unless it is added as described above.

11. Uninstalling OC

a) Disable OC (see 10).

b) Carry out step 3a.

c) Delete the /Volumes/EFI/EFI folder.

Acknowledgements

A big thank you to the talented developers of OpenCore for making all of this possible.
The problem still Also with nvram boot-args="-no_compat_check"
This is a preliminary account of how to use the excellent OpenCore (OC) bootloader on a Mac Pro 5,1 to install, run, and update macOS Catalina, resulting in a clean, unpatched operating system no different than what you would find on a supported Mac.

This documentation is an ongoing process. The steps here are subject to change as more testing gets done.

1. Test Setup

Variations of this setup are likely possible:

Disk A. Newly APFS-formatted drive (GUID scheme)

This is where OC and a clean install of Catalina will go.

Disk B. macOS Mojave

Installation and configuration will be done from here.

C. Non-bootscreen graphics card

Of course, a flashed card can't hurt.

2. Materials

A. The application "Install macOS Catalina" (the full installer)

B. OpenCore

See the releases page of the project site. Download OpenCore-0.5.2-RELEASE.zip. The uncompressed folder will be referred to here as "OpenCore."

C. Support files

See the releases page of the project site. Download AppleSupport-2.1.2-RELEASE.zip. The uncompressed folder will be referred to here as "AppleSupport."

D. Configuration file

Provided in this post. Download config.zip. The uncompressed file is "config.plist".

Most important is the manual located at OpenCore/Docs/Configuration.pdf. By reading the manual you will be able to better understand the settings in the configuration file. For a sustainable use of OC, it is important that you read the manual.

The configuration described in this guide should be safe, but please be aware of the following:

WARNING!
Using OpenCore without extensive knowledge of the configuration options
may lead to a bricked Mac.

Because OC is in active development, the configuration file for the current version (0.5.2) will likely be incompatible with future versions.

3. Installing OC

a) Mount the EFI partition of Disk A: To find the identifier of the partition, enter the following in terminal:
Code:
diskutil list

The identifier will be something like "disk0s1;" the next step will assume that this is the case.
Code:
sudo diskutil mount /dev/disk0s1

You may need to authorize this. The partition should mount as /Volumes/EFI and appear as "EFI" in Finder.

b) Copy the OpenCore/EFI folder to the EFI partition. The resulting folder, /Volumes/EFI/EFI, should contain the folders OC and BOOT.

c) Copy AppleSupport/Drivers/FwRuntimeServices.efi to /Volumes/EFI/EFI/OC/Drivers.

d) Copy config.plist to /Volumes/EFI/EFI/OC.

4. Configuration

The file config.plist can be edited with any plist editor and even with TextEdit; the following steps will assume TextEdit.

a) Open config.plist with TextEdit.

b) Enable the VMM flag: Find the Cpuid1Mask entry, and carefully change AAAAAAAAAAAAAAAAAAAAAA== to AAAAAAAAAAAAAACAAAAAAA==. The value should now be the same as for Cpuid1Data.

c) Enable boot entry preservation: Find the RequestBootVarRouting entry, and change false to true.

d) Close the file. It should be saved automatically (select OK if informed about there being no permanent version storage).

The purpose of doing these steps explicitly is to be able to reverse them if desired.

5. Booting

a) Reboot into recovery mode by entering
Code:
sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery

You may need to authorize this. Be patient. Mac Pro boot times can be long, especially when booting into recovery mode.

b) Carry out step 3a (sudo is not needed in recovery).

c) Set the partition for booting:
Code:
bless --mount /Volumes/EFI --setBoot

d) Shut down the Mac and do an SMC reset (unplug the power cord, wait 15 seconds, plug the power cord back in, wait 5 seconds, and then press the power button).

Remark: Being installed on Disk A, OC can have trouble seeing Disk B. Doing an SMC reset helps ensure that Disk B is seen when OC starts.

e) Power up the machine. OC should boot Disk B (currently the only macOS system).

Be patient. Mac Pro boot times can be long. If it seems that the machine is not booting up. Hold the power button to shut down the machine. Do an NVRAM reset on the next power up (immediately press and hold Option, Command, P, and R, and release after 20 seconds or after you hear the second startup chime). The Mac should boot without OC. Recheck all the steps above.

f) Booted into the system on Disk B, verify that it is indeed OC that has booted the system by entering this in terminal:
Code:
nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

You should see REL-052-2019-10-30.

You can also verify that the VMM flag is present by entering
Code:
sysctl machdep.cpu.features

Congratulations for making it this far! The hard part is done.

6. Installing Catalina

a) Booted into the system on Disk B, run Install macOS Catalina. Install to Disk A.

The machine will reboot and eventually you should see the installation progress bar.

b) Complete the installation.

From now on, OC should boot Catalina on Disk A by default. In any case, OC will respect the selection in Startup Disk; however, be mindful of the remark in step 5d. Also, by carrying out step 5a, OC should boot the recovery mode corresponding to the system currently booted into.

7. Updates

As long as the VMM flag is present, Software Update should just work.

8. Post Install

To make the system as native as possible while still using OC, the VMM flag can be disabled by reversing step 4b. This might be a good idea until the long term effects of having the VMM flag enabled on a non-virtualized system are clarified.

9. Platform Information

It is possible to use OC to customize platform information. You may want to preserve some of the original identifiers.

The MLB can be obtained by entering the following in terminal:
Code:
nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB | awk '{ print $NF }'

There is also the serial number of the processor tray:
Code:
ioreg -l -p IODeviceTree | awk '/"processor-memory-board-serial-number"/ {gsub(/\"/,""); print $NF}'

The ROM (in Base64, suitable for entry using TextEdit) can be obtained with
Code:
nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM | awk '{split($NF,chars,""); for(n=0;n<256;n++){ord[sprintf("%c",n)]=n}; i=1; j=0; while(i<=length($NF)){if(substr($NF,i,1)=="%"){printf "%s",toupper(substr($NF,i+1,2)); i=i+2} else {printf "%x",toupper(ord[chars[i]])} j=j+2; i++} print("")}' | xxd -r -p | base64

The SSN can be obtained with
Code:
ioreg -l -p IODeviceTree | awk '/"IOPlatformSerialNumber"/ {gsub(/\"/,""); print $NF}'

and the system UUID with
Code:
ioreg -l -p IODeviceTree | awk '/"system-id"/ {print toupper(substr($NF,2,8)"-"substr($NF,10,4)"-"substr($NF,14,4)"-"substr($NF,18,4)"-"substr($NF,22,12))}'


10. Disabling OC

a) Carry out step 3a.

b) Open config.plist with TextEdit.

c) Reverse step 4c.

d) Reboot.

e) Select the desired entry in Startup Disk.

f) Reboot.

It is also possible to boot Catalina natively, after using recovery to add the "-no_compat_check" boot argument. In this case replace step c above by 5a. In recovery, enter
Code:
nvram boot-args="-no_compat_check"

and then carry out steps d and e in recovery. Catalina should boot without OC.

Failure to add the "-no_compat_check" boot argument may result in the machine suddenly shutting down when booting into Catalina. Although OC adds this argument, booting without OC does not guarantee that the argument will be there, unless it is added as described above.

11. Uninstalling OC

a) Disable OC (see 10).

b) Carry out step 3a.

c) Delete the /Volumes/EFI/EFI folder.

Acknowledgements

A big thank you to the talented developers of OpenCore for making all of this possible.
still also with nvram boot-args="-no_compat_check"

47922AE4-9B84-4449-9BF7-414148B9855F.jpeg
 
The problem still Also with nvram boot-args="-no_compat_check"

still also with nvram boot-args="-no_compat_check"

Probably you done a PRAM reset that's why you need the "-no_compat_check" in nvram, so you should boot from any OSX USB Installer (El Capitan or higher), open a Recovery/Installer Terminal and type:

nvram boot-args="-no_compat_check"
 
Last edited:
Boot Mojave/High Sierra or Recovery and post a screenshot of your terminal running nvram -p:

Code:
sudo nvram -p

Recovery do not need sudo.
LocationServicesEnabled %01

efi-backup-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>CF295F86-69FA-422E-BFBB-B805F8E2200B</string></dict></dict><key>BLLastBSDName</key><string>disk1s2</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\AC9D438F-419E-4BDB-AF5F-A93F9BE02130\System\Library\CoreServices\boot.efi</string></dict></array>%00

efi-backup-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%02%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00`%04%ec%1b%00%00%00%00A%19%12%9fZD%05H%93%02%9b%c6%17>%14%9a%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hBO%8dcp%df%9b%15K%bb%cb%ca%be%af%0b%f5%ef%04%04%9a%00\%008%00E%001%008%000%00A%006%004%00-%004%00B%003%00F%00-%004%004%00C%007%00-%00B%001%003%008%00-%00A%004%00A%008%004%002%003%00C%004%000%003%008%00\%00S%00y%00s%00t%00e%00m%00\%00L%00i%00b%00r%00a%00r%00y%00\%00C%00o%00r%00e%00S%00e%00r%00v%00i%00c%00e%00s%00\%00b%00o%00o%00t%00.%00e%00f%00i%00%00%00%7f%ff%04%00

SystemAudioVolume +

boot-args -no_compact_check

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>684EB3C2-02D8-4535-0C5D-49AAEE7C8BAD</string></dict></dict><key>BLLastBSDName</key><string>disk2s7</string></dict></array>%00

bluetoothActiveControllerInfo %89%82%ac%05%01%00%00%00%13Z%bcT6%cf]%1d

BootCampHD %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%03%00%00%00%00%00%7f%ff%04%00

bluetoothInternalControllerInfo %89%82%ac%05%00%00%13Z%bcT6%cf]%1d

AAPL,PanicInfo000L %db%ed%b0%9b<'%96%ed%e9q9A%83%e1\%b2%1a%cc5S%f0%93%cf%e9p%9a%0c%ca%c7%e84%bd<%a6%d7%e5%e5%e6%9b\f%87%8c%09%1a%0c%e7%92%d5`%ae%99%82%9f|%86%a6!cB%e6%8a)%80%eb2%9e%ee%1a%be%e5e%aa%bc>%a7'b%0a_(8%94%97%c9e7=%1df7%c3%ee%f0%b9,O%c4\0%85oY%96%bb%cbli%99%1d%ce#%dfsz"%a6%e0'%9f%d5%a9%10%f9%9e%d3C%c6D%cc%25S%f8%eas%b1+T%1d%be%db%ed%b7;%11s%c1%14%bePPX%9fC%df%f7%b2<4L%c4\0%85/%14%9c%16%a1%cd%b0;|.%cb%131%17%cc%15S%f8%92%cf);l/C%e5%efqy>%7f%cb%131%05?%f9%a4%a6%db%e5i%de=%0e%19%137%1a%cc%25S%f0%93Og%99~%7f%cb%d7i%f79dL%cc\4%05?%f9%94%96%e1o9=dL%d0n%0a_(%18%1cB%93Pv%98n~%cb%db%09%9b+%a6%f0%85%82%d3%e601s%c5\9%05?%f9%84%0e%93!cB%e6%ca)%f8%c9gp%08M%86%8c%89%98%8b%a6%00%ae%cbc%17%9c%8e%96%97%c3%e4DL%01\%97%c7%ae%f1[^%1e%cb%f3p%fa;%11s%c1%14%c0uy%ecb%a6%c5%edDL%01%00%00%00

prev-lang:kbd it:223

SystemAudioVolumeDB %eb

efi-apple-payload0-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%02%00%00%00%00%00%04%01*%00%01%00%00%00(%00%00%00%00%00%00%00%00@%06%00%00%00%00%00%d3%bbB%e8%0d(%05L%9e%e8%8d%d0%89w(%88%02%02%04%04<%00\%00E%00F%00I%00\%00A%00P%00P%00L%00E%00\%00F%00I%00R%00M%00W%00A%00R%00E%00\%00M%00P%005%001%00.%00f%00d%00%00%00%7f%ff%04%00

fmm-computer-name Mac Pro di Mark0

efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%03%00%00%00%00%00%04%01*%00%07%00%00%00%00%a0]1%00%00%00%00%e0@%1a%1c%00%00%00%00%c2%b3Nh%d8%025E%0c]I%aa%ee|%8b%ad%02%02%7f%ff%04%00

efi-apple-payload0 <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>E842BBD3-280D-4C05-9EE8-8DD089772888</string></dict></dict><key>BLLastBSDName</key><string>disk0s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\APPLE\FIRMWARE\MP51.fd</string></dict></array>%00

AAPL,PanicInfo000K z%99X%b6%a7%c7%e5D%cc%25S%f8%eas%b1+TE%d6%c5%89%98K%a6%e0'%9f%c6%b4%bc|M%cb%cb%d3%b2<%1df%0b%ebs%a8%fcM%7f%8f%dfl%aa<%ec%9e%c3%dfrzB%e6%aa%b9b%0a~%f2iL%cb%cb%d7%b4%bc<%15Be%09%9ak%e6%9a)%f8%c9%e7%b4,O%87%d9!c"%16S%00%cdivy%9e%9f%d3%cb%ed%b9%0bm%9e%bb%ca%ee%f1%9b%9cv%9f%e7%aeu%19OO%c4%14%fc%e4s:%9c&%9bu6=%dd.%93%d3%e1%e1%bb%dd%0e%bb%c9sb%d9%9e%1e%97%134%18%ce%25%ab%c1\3%05?%f9%14%12C%d3%901%11s%e1%14%fc%e4%93h%25%86%a6!c"%e6%c2)%f8%c9%e7%90%18%9a%86%8c%89%98%0b%a7%f0%85%82%d8y%d8=%1d%a3%cb%edrb%a6%e0'%9fA%e40)d%bf%c7%eb%d041%83%c5\2%1b%cc%15S%f0%93%cf r%98%9c%96%e5%e90;H%0dB%93%09%99%ed%e6%aa%c1\1%05?%f94%a6%e5%e5kZ^%0e%19%134%d7%cd5S%f8B%d5fY~.;%eb%e2D%0e%06s%d1\2%05?%f9%c4%c1d%b1X%c8%98%88%c9`0WL%e6%92)|m%a2s%fa4%9b%d9%ef0%b9:/%cb%87%ect%d9MO%c4\0WL%8cS%f8%c6oyy%1c%86%d3%eb%f2r"%e6%82%b9h%0a_}.v%85%aaE%e40%09%1d&%131%97L%c1O>%83%c8a2dL%c8p8%85%af>%17%bbBU,r%98%84%0e%93%89%98K%a6%f0%d5%e7bW%a8%8aE%0e%93%89%98K%a6%f0%d5%e7bW%a8ZE%0e%93%d0a2%11s%c9%14%be%fa\%ec%0aU%ab%c8a2%11s%c9%14%be%fa\%ec%0aU%8b%c8a2%11s%c9%14%be%fa\%ec%0aU%91%ef9%1d%1a%1e%af%cbtc%9aM/%cb%131%17L%c1O>%abSa%c8%98%c8%c1`.%9aK%a6%f0%85%aa%c8%f7%9c%de,%cb%cfe%a8%fc%0d/%cb%e9%e9%f2<%11s%c9%14%beP%b0hL:%ad%d2`3!s%c5%14%beP%b0hLJ%ebnz%ba]N%c8\1%05?%f9%9c6%85%f5y%c8%98%88%b9b%0a~%f2%89L%12C%c6%84%cc%05s%c1%14%a4x=,%0f%bb%e9iw91S%90%e6a7Y%fc%c6'f0%98%0b%a6%00%ae%cbx%ba+%14l%86%e9ct"%e6%82%b9`%e4%98%c2GL%cf%d7%c9v%f8\%9e'h%b9%99%0b%e6%82)|%a1%a0%91X\%96%f3S%fa[^N%c8p%ae%19L%e1%0b%05%8bfsx\%0e%8b%d9%e5%d04%11s%c1%14%bePpY%ceO%e9oy9!S%f8BU*%b1%99%a0%d5l.%99%0d%e6%9a)|%a1`%f3-N%b3%cb%c64%bb%9ct%d3%cbgy%9a%9eO%c4\0WM%c1O>%abSa3<%9f%87%a6Dy%da^%96'b%b4%9aK%06%83%b9d%0a~%f29%1dN%93B%f6{%bc%1e%be

EFIBluetoothDelay %b8%0b

efi-backup-boot-device-data-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%02%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00`%04%ec%1b%00%00%00%00%c8&%ff%d0%0a!%edI%a9Hz#J%9an`%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%86_)%cf%fai.B%bf%bb%b8%05%f8%e2 %0b%04%04%9a%00\%00A%00C%009%00D%004%003%008%00F%00-%004%001%009%00E%00-%004%00B%00D%00B%00-%00A%00F%005%00F%00-%00A%009%003%00F%009%00B%00E%000%002%001%003%000%00\%00S%00y%00s%00t%00e%00m%00\%00L%00i%00b%00r%00a%00r%00y%00\%00C%00o%00r%00e%00S%00e%00r%00v%00i%00c%00e%00s%00\%00b%00o%00o%00t%00.%00e%00f%00i%00%00%00%7f%ff%04%00
 
Try reboot to the apple startup manager (holding alt-option), highlight your Catalina Volume, hold CMD+V , keep holding press Enter key, this should tell what's behind the prohibitory symbol.
 
LocationServicesEnabled %01

efi-backup-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>CF295F86-69FA-422E-BFBB-B805F8E2200B</string></dict></dict><key>BLLastBSDName</key><string>disk1s2</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\AC9D438F-419E-4BDB-AF5F-A93F9BE02130\System\Library\CoreServices\boot.efi</string></dict></array>%00

efi-backup-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%02%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00`%04%ec%1b%00%00%00%00A%19%12%9fZD%05H%93%02%9b%c6%17>%14%9a%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hBO%8dcp%df%9b%15K%bb%cb%ca%be%af%0b%f5%ef%04%04%9a%00\%008%00E%001%008%000%00A%006%004%00-%004%00B%003%00F%00-%004%004%00C%007%00-%00B%001%003%008%00-%00A%004%00A%008%004%002%003%00C%004%000%003%008%00\%00S%00y%00s%00t%00e%00m%00\%00L%00i%00b%00r%00a%00r%00y%00\%00C%00o%00r%00e%00S%00e%00r%00v%00i%00c%00e%00s%00\%00b%00o%00o%00t%00.%00e%00f%00i%00%00%00%7f%ff%04%00

SystemAudioVolume +

boot-args -no_compact_check

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>684EB3C2-02D8-4535-0C5D-49AAEE7C8BAD</string></dict></dict><key>BLLastBSDName</key><string>disk2s7</string></dict></array>%00

bluetoothActiveControllerInfo %89%82%ac%05%01%00%00%00%13Z%bcT6%cf]%1d

BootCampHD %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%03%00%00%00%00%00%7f%ff%04%00

bluetoothInternalControllerInfo %89%82%ac%05%00%00%13Z%bcT6%cf]%1d

AAPL,PanicInfo000L %db%ed%b0%9b<'%96%ed%e9q9A%83%e1\%b2%1a%cc5S%f0%93%cf%e9p%9a%0c%ca%c7%e84%bd<%a6%d7%e5%e5%e6%9b\f%87%8c%09%1a%0c%e7%92%d5`%ae%99%82%9f|%86%a6!cB%e6%8a)%80%eb2%9e%ee%1a%be%e5e%aa%bc>%a7'b%0a_(8%94%97%c9e7=%1df7%c3%ee%f0%b9,O%c4\0%85oY%96%bb%cbli%99%1d%ce#%dfsz"%a6%e0'%9f%d5%a9%10%f9%9e%d3C%c6D%cc%25S%f8%eas%b1+T%1d%be%db%ed%b7;%11s%c1%14%bePPX%9fC%df%f7%b2<4L%c4\0%85/%14%9c%16%a1%cd%b0;|.%cb%131%17%cc%15S%f8%92%cf);l/C%e5%efqy>%7f%cb%131%05?%f9%a4%a6%db%e5i%de=%0e%19%137%1a%cc%25S%f0%93Og%99~%7f%cb%d7i%f79dL%cc\4%05?%f9%94%96%e1o9=dL%d0n%0a_(%18%1cB%93Pv%98n~%cb%db%09%9b+%a6%f0%85%82%d3%e601s%c5\9%05?%f9%84%0e%93!cB%e6%ca)%f8%c9gp%08M%86%8c%89%98%8b%a6%00%ae%cbc%17%9c%8e%96%97%c3%e4DL%01\%97%c7%ae%f1[^%1e%cb%f3p%fa;%11s%c1%14%c0uy%ecb%a6%c5%edDL%01%00%00%00

prev-lang:kbd it:223

SystemAudioVolumeDB %eb

efi-apple-payload0-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%02%00%00%00%00%00%04%01*%00%01%00%00%00(%00%00%00%00%00%00%00%00@%06%00%00%00%00%00%d3%bbB%e8%0d(%05L%9e%e8%8d%d0%89w(%88%02%02%04%04<%00\%00E%00F%00I%00\%00A%00P%00P%00L%00E%00\%00F%00I%00R%00M%00W%00A%00R%00E%00\%00M%00P%005%001%00.%00f%00d%00%00%00%7f%ff%04%00

fmm-computer-name Mac Pro di Mark0

efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%03%00%00%00%00%00%04%01*%00%07%00%00%00%00%a0]1%00%00%00%00%e0@%1a%1c%00%00%00%00%c2%b3Nh%d8%025E%0c]I%aa%ee|%8b%ad%02%02%7f%ff%04%00

efi-apple-payload0 <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>E842BBD3-280D-4C05-9EE8-8DD089772888</string></dict></dict><key>BLLastBSDName</key><string>disk0s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\APPLE\FIRMWARE\MP51.fd</string></dict></array>%00

AAPL,PanicInfo000K z%99X%b6%a7%c7%e5D%cc%25S%f8%eas%b1+TE%d6%c5%89%98K%a6%e0'%9f%c6%b4%bc|M%cb%cb%d3%b2<%1df%0b%ebs%a8%fcM%7f%8f%dfl%aa<%ec%9e%c3%dfrzB%e6%aa%b9b%0a~%f2iL%cb%cb%d7%b4%bc<%15Be%09%9ak%e6%9a)%f8%c9%e7%b4,O%87%d9!c"%16S%00%cdivy%9e%9f%d3%cb%ed%b9%0bm%9e%bb%ca%ee%f1%9b%9cv%9f%e7%aeu%19OO%c4%14%fc%e4s:%9c&%9bu6=%dd.%93%d3%e1%e1%bb%dd%0e%bb%c9sb%d9%9e%1e%97%134%18%ce%25%ab%c1\3%05?%f9%14%12C%d3%901%11s%e1%14%fc%e4%93h%25%86%a6!c"%e6%c2)%f8%c9%e7%90%18%9a%86%8c%89%98%0b%a7%f0%85%82%d8y%d8=%1d%a3%cb%edrb%a6%e0'%9fA%e40)d%bf%c7%eb%d041%83%c5\2%1b%cc%15S%f0%93%cf r%98%9c%96%e5%e90;H%0dB%93%09%99%ed%e6%aa%c1\1%05?%f94%a6%e5%e5kZ^%0e%19%134%d7%cd5S%f8B%d5fY~.;%eb%e2D%0e%06s%d1\2%05?%f9%c4%c1d%b1X%c8%98%88%c9`0WL%e6%92)|m%a2s%fa4%9b%d9%ef0%b9:/%cb%87%ect%d9MO%c4\0WL%8cS%f8%c6oyy%1c%86%d3%eb%f2r"%e6%82%b9h%0a_}.v%85%aaE%e40%09%1d&%131%97L%c1O>%83%c8a2dL%c8p8%85%af>%17%bbBU,r%98%84%0e%93%89%98K%a6%f0%d5%e7bW%a8%8aE%0e%93%89%98K%a6%f0%d5%e7bW%a8ZE%0e%93%d0a2%11s%c9%14%be%fa\%ec%0aU%ab%c8a2%11s%c9%14%be%fa\%ec%0aU%8b%c8a2%11s%c9%14%be%fa\%ec%0aU%91%ef9%1d%1a%1e%af%cbtc%9aM/%cb%131%17L%c1O>%abSa%c8%98%c8%c1`.%9aK%a6%f0%85%aa%c8%f7%9c%de,%cb%cfe%a8%fc%0d/%cb%e9%e9%f2<%11s%c9%14%beP%b0hL:%ad%d2`3!s%c5%14%beP%b0hLJ%ebnz%ba]N%c8\1%05?%f9%9c6%85%f5y%c8%98%88%b9b%0a~%f2%89L%12C%c6%84%cc%05s%c1%14%a4x=,%0f%bb%e9iw91S%90%e6a7Y%fc%c6'f0%98%0b%a6%00%ae%cbx%ba+%14l%86%e9ct"%e6%82%b9`%e4%98%c2GL%cf%d7%c9v%f8\%9e'h%b9%99%0b%e6%82)|%a1%a0%91X\%96%f3S%fa[^N%c8p%ae%19L%e1%0b%05%8bfsx\%0e%8b%d9%e5%d04%11s%c1%14%bePpY%ceO%e9oy9!S%f8BU*%b1%99%a0%d5l.%99%0d%e6%9a)|%a1`%f3-N%b3%cb%c64%bb%9ct%d3%cbgy%9a%9eO%c4\0WM%c1O>%abSa3<%9f%87%a6Dy%da^%96'b%b4%9aK%06%83%b9d%0a~%f29%1dN%93B%f6{%bc%1e%be

EFIBluetoothDelay %b8%0b

efi-backup-boot-device-data-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%02%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00`%04%ec%1b%00%00%00%00%c8&%ff%d0%0a!%edI%a9Hz#J%9an`%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%86_)%cf%fai.B%bf%bb%b8%05%f8%e2 %0b%04%04%9a%00\%00A%00C%009%00D%004%003%008%00F%00-%004%001%009%00E%00-%004%00B%00D%00B%00-%00A%00F%005%00F%00-%00A%009%003%00F%009%00B%00E%000%002%001%003%000%00\%00S%00y%00s%00t%00e%00m%00\%00L%00i%00b%00r%00a%00r%00y%00\%00C%00o%00r%00e%00S%00e%00r%00v%00i%00c%00e%00s%00\%00b%00o%00o%00t%00.%00e%00f%00i%00%00%00%7f%ff%04%00
You made a typo:

Code:
boot-args -no_compact_check

Remove it with:
Code:
sudo nvram -d boot-args
sudo nvram boot-args="-no_compat_check"

Btw, your PanicInfo logs are already at K, you have some serious hardware problem. Run AHT/ASD and find what it is.
 
You made a typo:

Code:
boot-args -no_compact_check

Remove it with:
Code:
sudo nvram -d boot-args
sudo nvram boot-args="-no_compat_check"
You made a typo:

Code:
boot-args -no_compact_check

Remove it with:
Code:
sudo nvram -d boot-args
sudo nvram boot-args="-no_compat_check"

Btw, your PanicInfo logs are already at K, you have some serious hardware problem. Run AHT/ASD and find what it is.
so I don’t replace vmm with original?

only type in recovery on terminal
boot-args -no_compact_check?
Thank you
 
so I don’t replace vmm with original?

only type in recovery on terminal
boot-args -no_compact_check?
Thank you
From Recovery you don't use sudo, type everything exactly as I did.

Check what is causing your PanicLogs, you have a hardware problem.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.