macOS 12 Monterey on Unsupported Macs Thread

[Heat_Fan89]

Errr….. you may use the opencore patcher app after you have updated the normal way.

But to actually update your OS (like Monterey security updates) , the procedure is the same as always….OTA update. That means “over the air update”. Just like you always do, you go to system preferences, and you press update. The rest should take care of itself.

Then, after you have updated, you may need go to the open core patcher app to re-patch your system.

That was the reason for my question because after about 30 minutes at the desktop, I got the system update notification and it was to download Ventura, which I wasn't about to do. I did run the only patch that was available from Opencore.

Edit: I ran OpenCore again just to double check and it gives me two options to reinstall root patch or revert so I will leave it alone for now. I did install the last version of Monterey 12.6.3 and Safari is at 16.3

I went back into System Update and all it shows is a Ventura upgrade. I deseleceted and reselected all the update options and all it shows is Ventura. Is the latest Monterey version of Safari 16.3?

 

[Flocondavoine]

I have a A1278 / MacBookPro7,1 / Macbook Pro Mid 2010.
I installed 12.5.1 and i can’t fully disable sip. I’m using the Open Core Legacy Patcher, i opened it as admin and disabled sip from the app, when i restart i try to open an app (cDock) and it tells me to turn sip off. I ran cDock multiple times and i think it was after i used internet recovery mode (took like 5min) ran csrutil disable on it, and opened the app in admin mode but when i restarted it was the same issue.
is this happening for anyone else on monterey?
i just can’t seem to disable it.

I have the exact same issue for a different app. I tried everything thinkable, nothing works. I know that Appled hardened the SIP and I am wondering if there is a runaround with OCLP that prevents such feature.

 

[Flocondavoine]

The problem isn't SIP, it is cDock. Look at the cDock home page, Monterey is not supported (support for up to and including Big Sur).

macEnhance

The tools you need to enhance your macOS experience.

www.macenhance.com

It is highly recommended to let OCLP determine the SIP settings, which will vary widely depending on the hardware.
Run OCLP, Build and Install, then write to disk. Then after a reboot, run OCLP again and try the Root patch, after installation, which is not required on newer hardware. I am fairly sure the volume root patches are required on that MBP 2010.

I have a Mid 2010/2012 Mac Pro (first owner) with Monterey and I want to use TotalFinder. I tried everything to disable SIP and it never works. Is there a turnaround to bypass that security feature that Apple hardened? I really cannot live without TotalFinder.

 

[h9826790]

I have a Mid 2010/2012 Mac Pro (first owner) with Monterey and I want to use TotalFinder. I tried everything to disable SIP and it never works. Is there a turnaround to bypass that security feature that Apple hardened? I really cannot live without TotalFinder.

Most likely your OpenCore config took over the SIP control. In that case, you can simply turn off SIP by changing the OC config.

You can check this video about how to mod the config

My package has SIP disabled by default. Therefore, this video is for "how to re-enable SIP". What you need to do is reverse the process, and change the AAAAAA to fwgAAA.

 

[KateMatsuda]

That was the reason for my question because after about 30 minutes at the desktop, I got the system update notification and it was to download Ventura, which I wasn't about to do. I did run the only patch that was available from Opencore.

Edit: I ran OpenCore again just to double check and it gives me two options to reinstall root patch or revert so I will leave it alone for now. I did install the last version of Monterey 12.6.3 and Safari is at 16.3

I went back into System Update and all it shows is a Ventura upgrade. I deseleceted and reselected all the update options and all it shows is Ventura. Is the latest Monterey version of Safari 16.3?

It should show you more things below the Ventura upgrade marked by a small text saying "more available updates" or similar, just forgot the exact wording and below that a text URL "more Info". There you should see after clicking on that updates to Monterey 12.6.5 . Safari 16.3 is currently the most recent update to this.

 

[Heat_Fan89]

It should show you more things below the Ventura upgrade marked by a small text saying "more available updates" or similar, just forgot the exact wording and below that a text URL "more Info". There you should see after clicking on that updates to Monterey 12.6.5 . Safari 16.3 is currently the most recent update to this.

It did have the more followed by dots and a + sign and no I did not click on that but since you mentioned it, I will.

 

[davidlv]

It should show you more things below the Ventura upgrade marked by a small text saying "more available updates" or similar, just forgot the exact wording and below that a text URL "more Info". There you should see after clicking on that updates to Monterey 12.6.5 . Safari 16.3 is currently the most recent update to this.

The latest Release version of Monterey is 12.6.3 build # 21G419, not 12.6.5.
You can get that installer app as shown below:

macOS 12 Monterey Full Installer Database. Download Directly from Apple!

Download macOS Monterey full installer with one click straight from Apple! Every version of Monterey Beta & Final available all in one place!!

mrmacintosh.com

 

[nospamboz]

Good luck and do keep us posted. 😉

OK, I think I uderstand my situation a little better now. The instructions mention the possibility of creating the installer USB manually, so I used "createinstallmedia" to make a Monterey installer USB (GPT with ESP), and went straight to the "Build and Install Opencore" step. It built fine, but when I went to install, this is what I saw:

The only disk it sees is disk0, my internal drive. I have several external drives, USB and Firewire, including the USB Monterey installer, but they don't show up.

My guess is that the patcher GUI app is incompatible with my system for some reason, and it cannot locate any external drives. Something about the way the app locates external drives doesn't work on my system. Of course, that means that the patcher GUI is useless for me to create an Opencore installer USB.

Is there any way to use a Terminal window command line to put Opencore on the Monterey installer USB? I need a way to bypass the GUI.

 

[davidlv]

OK, I think I uderstand my situation a little better now. The instructions mention the possibility of creating the installer USB manually, so I used "createinstallmedia" to make a Monterey installer USB (GPT with ESP), and went straight to the "Build and Install Opencore" step. It built fine, but when I went to install, this is what I saw:

View attachment 2152830

The only disk it sees is disk0, my internal drive. I have several external drives, USB and Firewire, including the USB Monterey installer, but they don't show up.

My guess is that the patcher GUI app is incompatible with my system for some reason, and it cannot locate any external drives. Something about the way the app locates external drives doesn't work on my system. Of course, that means that the patcher GUI is useless for me to create an Opencore installer USB.

Is there any way to use a Terminal window command line to put Opencore on the Monterey installer USB? I need a way to bypass the GUI.

The USB should be made with HFS+ format, not ESP (whatever that is) with the GUID Partition Map setting. Do you have another Mac or have access to one, a friend's Mac or such?
When you start up the OCLP app from another Mac, you will see a menu that has a Settings item. Use that to specify the intended target Mac, and then install OCLP to the USB.
What Mac and system are you on now? That info is required to give you good advice.

 

[Heat_Fan89]

It should show you more things below the Ventura upgrade marked by a small text saying "more available updates" or similar, just forgot the exact wording and below that a text URL "more Info". There you should see after clicking on that updates to Monterey 12.6.5 . Safari 16.3 is currently the most recent update to this.

Okay so I checked and all I see is More Info.... below the option to upgrade to Ventura. If I click on more info, it opens Safari and directs me to Apple.com

I also checked and my version of Monterey is 12.6.3

 

[KateMatsuda]

Okay so I checked and all I see is More Info.... below the option to upgrade to Ventura. If I click on more info, it opens Safari and directs me to Apple.com

I also checked and my version of Monterey is 12.6.3

It should look like this..not the "more Info" directly below the Ventura upgrade but the second one further down.

 

[nospamboz]

The USB should be made with HFS+ format, not ESP (whatever that is) with the GUID Partition Map setting. Do you have another Mac or have access to one, a friend's Mac or such?
When you start up the OCLP app from another Mac, you will see a menu that has a Settings item. Use that to specify the intended target Mac, and then install OCLP to the USB.
What Mac and system are you on now? That info is required to give you good advice.

Thank you. I believe Apple's createinstallmedia script formats the USB as HFS+, and I can confirm that my Monterey installer USB is HFS+. ESP stands for "EFI System Partition", the standard EFI partition. By the way, GPT is GUID Partition Table, the post-MBR standard, which usually includes an ESP.

I am on a Macbook5,2 (mid-2009) on Mojave using the dosdude1 patcher. I have no access to any other Macs.

Do you know how to install Opencore to an installer USB via the command line? I think that's my best option at this stage.

 

[KateMatsuda]

Thank you. I believe Apple's createinstallmedia script formats the USB as HFS+, and I can confirm that my Monterey installer USB is HFS+. ESP stands for "EFI System Partition", the standard EFI partition. By the way, GPT is GUID Partition Table, the post-MBR standard, which usually includes an ESP.

I am on a Macbook5,2 (mid-2009) on Mojave using the dosdude1 patcher. I have no access to any other Macs.

Do you know how to install Opencore to an installer USB via the command line? I think that's my best option at this stage.

What exactly keeps you from formatting your USB medium with the right partiton map and format? When it is formatted it will be shown as an install medium by OCLP, if it is not correctly formatted neither Finder nor OCLP will recognize it as it seems to be the case here?

 

[nospamboz]

What exactly keeps you from formatting your USB medium with the right partiton map and format? When it is formatted it will be shown as an install medium by OCLP, if it is not correctly formatted neither Finder nor OCLP will recognize it as it seems to be the case here?

I don't understand what you mean. It's formatted GPT with an EFI partition and the install partition as HFS+. How is that not the "right partition map"? I did it with Disk Utility. And it's Apple's createinstallmedia script that ensures it's the right format.

Also, my other external disks are GPT/EFI/HFS+. They're not showing up either. The problem must be the method the app uses to locate external disks, which doesn't work on my system, as I explained.

 

[Heat_Fan89]

View attachment 2152905
It should look like this..not the "more Info" directly below the Ventura upgrade but the second one further down.

No, it doesn't look like that. The only option that is available is the upgrade to Ventura. The option for updates below Ventura is missing. However it was a few days ago that I installed the latest version of Monterey via OCLP so perhaps there aren't any updates as of yet.

 

[Ambrozio]

Hi,
Can anyone help me? I have read all the posts and all the solutions and answers, and I can't find the solution to my problem.
I have a Quadro K3000M graphics card installed, which I have flashed and it works fine on High Sierra.

I've done the whole process again, with a clean install to an external SSD, and the result is the same.
The last part of log of the installation (every 3 minutes generates a new one) is this:

Spoiler: Log

patchd: DeviceInfo:
BoardID: 240
ChipID: 32786

patchd: patchd_macos_block_invoke_7(1512): Chip environmentis medium/relaxed/x86
patchd: patchd_macos_block_invoke_7(1526): Found system manifest im4m at /mnt9/128E00FA-6BC2-4F5A-89A4-5BE38CAB0248.staging/usr/standalone/OS.dmg.mtree.x86legacyap.im4m and root hash im4m at /mnt9/128E00FA-6BC2-4F5A-89A4-5BE38CAB0248.staging/usr/standalone/OS.dmg.root_hash.x86legacyap.im4m
patchd: patchd_macos_block_invoke_7(1545): Done copying MSUBootObjects folder
[16:57:58.0128-GMT]{3>6} CHECKPOINT END: PATCHD:[0x0573] patchd_macos_fixup_preboot
ota-step-ids = {}
executing /usr/sbin/nvram ramrod-nvram-sequence=60
nvram successfully persisted to the filesystem
ota-step-names = {}
executing /usr/sbin/nvram ramrod-nvram-sequence=61
nvram successfully persisted to the filesystem
ota-step-uptime = 22
executing /usr/sbin/nvram ramrod-nvram-sequence=62
nvram successfully persisted to the filesystem
ota-step-user-progress = 10
executing /usr/sbin/nvram ramrod-nvram-sequence=63
nvram successfully persisted to the filesystem
[16:57:58.0261-GMT]{3>6} CHECKPOINT BEGIN: PATCHD:[0x0572] patchd_fixup_system
ota-step-ids = {0x11030572:28}
executing /usr/sbin/nvram ramrod-nvram-sequence=64
nvram successfully persisted to the filesystem
ota-step-names = {0x11030572😛atchd_fixup_system}
executing /usr/sbin/nvram ramrod-nvram-sequence=65
nvram successfully persisted to the filesystem
ota-step-uptime = 22
executing /usr/sbin/nvram ramrod-nvram-sequence=66
nvram successfully persisted to the filesystem
ota-step-user-progress = 10
executing /usr/sbin/nvram ramrod-nvram-sequence=67
nvram successfully persisted to the filesystem
Initialized MSUMigrationHelper (system = /mnt1, data = /mnt4, update = /mnt5/softwareupdate/)
patchd: Migrating using Template Migration
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /AppleInternal -> AppleInternal
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Skipping attempt to create missing firmlink: /mnt1/AppleInternal (error: 2)
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /Applications -> Applications
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/Applications -> Applications
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /Library -> Library
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/Library -> Library
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /System/Library/Caches -> System/Library/Caches
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/System/Library/Caches -> System/Library/Caches
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /System/Library/Assets -> System/Library/Assets
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/System/Library/Assets -> System/Library/Assets
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /System/Library/PreinstalledAssets -> System/Library/PreinstalledAssets
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/System/Library/PreinstalledAssets -> System/Library/PreinstalledAssets
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /System/Library/AssetsV2 -> System/Library/AssetsV2
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/System/Library/AssetsV2 -> System/Library/AssetsV2
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /System/Library/PreinstalledAssetsV2 -> System/Library/PreinstalledAssetsV2
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/System/Library/PreinstalledAssetsV2 -> System/Library/PreinstalledAssetsV2
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /System/Library/CoreServices/CoreTypes.bundle/Contents/Library -> System/Library/CoreServices/CoreTypes.bundle/Contents/Library
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/System/Library/CoreServices/CoreTypes.bundle/Contents/Library -> System/Library/CoreServices/CoreTypes.bundle/Contents/Library
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /System/Library/Speech -> System/Library/Speech
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/System/Library/Speech -> System/Library/Speech
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /Users -> Users
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/Users -> Users
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /Volumes -> Volumes
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/Volumes -> Volumes
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /cores -> cores
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/cores -> cores
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /opt -> opt
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/opt -> opt
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /private -> private
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/private -> private
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /usr/local -> usr/local
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/usr/local -> usr/local
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /usr/libexec/cups -> usr/libexec/cups
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/usr/libexec/cups -> usr/libexec/cups
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlinking /usr/share/snmp -> usr/share/snmp
-[MSUMigrationHelper _createFirmlinkFromSource:toDestination:]: Firmlink is already correct: /mnt1/usr/share/snmp -> usr/share/snmp
patchd: Writing file to path: /mnt9/128E00FA-6BC2-4F5A-89A4-5BE38CAB0248.staging
patchd: patchd_macos_block_invoke(1594): Returning from fixup_system..Result is 0
[16:57:58.0424-GMT]{3>6} CHECKPOINT END: PATCHD:[0x0572] patchd_fixup_system
ota-step-ids = {}
executing /usr/sbin/nvram ramrod-nvram-sequence=68
nvram successfully persisted to the filesystem
ota-step-names = {}
executing /usr/sbin/nvram ramrod-nvram-sequence=69
nvram successfully persisted to the filesystem
ota-step-uptime = 22
executing /usr/sbin/nvram ramrod-nvram-sequence=70
nvram successfully persisted to the filesystem
ota-step-user-progress = 10
executing /usr/sbin/nvram ramrod-nvram-sequence=71
nvram successfully persisted to the filesystem
[16:57:58.0557-GMT]{3>6} CHECKPOINT BEGIN: PATCHD:[0x058F] macos_install_recovery
ota-step-ids = {0x1103058F:29}
executing /usr/sbin/nvram ramrod-nvram-sequence=72
nvram successfully persisted to the filesystem
ota-step-names = {0x1103058F:macos_install_recovery}
executing /usr/sbin/nvram ramrod-nvram-sequence=73
nvram successfully persisted to the filesystem
ota-step-uptime = 22
executing /usr/sbin/nvram ramrod-nvram-sequence=74
nvram successfully persisted to the filesystem
ota-step-user-progress = 10
executing /usr/sbin/nvram ramrod-nvram-sequence=75
nvram successfully persisted to the filesystem
patchd: patch_common_stage_recovery(297): Located RecoveryBoot folder stashed by the booted os at /mnt5/softwareupdate/MSUPreservedBootObjects/RecoveryBootFlat/..Copying to /mnt5/recovery/128E00FA-6BC2-4F5A-89A4-5BE38CAB0248.staged/
patchd: patch_common_stage_recovery(308): Done copying RecoveryBoot folder
patchd: patch_common_stage_recovery(323): Copying: /mnt5/softwareupdate/recovery/ -> /mnt5/recovery/128E00FA-6BC2-4F5A-89A4-5BE38CAB0248.staged/
patchd: patchd_macos_block_invoke_2(1610): Returning from fixup_system..Result is 0
[16:59:01.0412-GMT]{3>6} CHECKPOINT END: PATCHD:[0x058F] macos_install_recovery
ota-step-ids = {}
executing /usr/sbin/nvram ramrod-nvram-sequence=76
nvram successfully persisted to the filesystem
ota-step-names = {}
executing /usr/sbin/nvram ramrod-nvram-sequence=77
nvram successfully persisted to the filesystem
ota-step-uptime = 85
executing /usr/sbin/nvram ramrod-nvram-sequence=78
nvram successfully persisted to the filesystem
ota-step-user-progress = 10
executing /usr/sbin/nvram ramrod-nvram-sequence=79
nvram successfully persisted to the filesystem
[16:59:01.0545-GMT]{3>6} CHECKPOINT BEGIN: PATCHD:[0x0593] macos_set_bootable
ota-step-ids = {0x11030593:30}
executing /usr/sbin/nvram ramrod-nvram-sequence=80
nvram successfully persisted to the filesystem
ota-step-names = {0x11030593:macos_set_bootable}
executing /usr/sbin/nvram ramrod-nvram-sequence=81
nvram successfully persisted to the filesystem
ota-step-uptime = 85
executing /usr/sbin/nvram ramrod-nvram-sequence=82
nvram successfully persisted to the filesystem
ota-step-user-progress = 10
executing /usr/sbin/nvram ramrod-nvram-sequence=83
nvram successfully persisted to the filesystem
[16:59:01.0680-GMT]{3>6} CHECKPOINT END: PATCHD:[0x0593] macos_set_bootable
ota-step-ids = {}
executing /usr/sbin/nvram ramrod-nvram-sequence=84
nvram successfully persisted to the filesystem
ota-step-names = {}
executing /usr/sbin/nvram ramrod-nvram-sequence=85
nvram successfully persisted to the filesystem
ota-step-uptime = 85
executing /usr/sbin/nvram ramrod-nvram-sequence=86
nvram successfully persisted to the filesystem
ota-step-user-progress = 10
executing /usr/sbin/nvram ramrod-nvram-sequence=87
nvram successfully persisted to the filesystem
[16:59:01.0822-GMT]{3>6} CHECKPOINT BEGIN: PATCHD:[0x0577] macos_seal_system_volume
ota-step-ids = {0x11030577:31}
executing /usr/sbin/nvram ramrod-nvram-sequence=88
nvram successfully persisted to the filesystem
ota-step-names = {0x11030577:macos_seal_system_volume}
executing /usr/sbin/nvram ramrod-nvram-sequence=89
nvram successfully persisted to the filesystem
ota-step-uptime = 85
executing /usr/sbin/nvram ramrod-nvram-sequence=90
nvram successfully persisted to the filesystem
ota-step-user-progress = 10
executing /usr/sbin/nvram ramrod-nvram-sequence=91
nvram successfully persisted to the filesystem
patchd: patchd_macos_block_invoke_4(1651): Successfully obtained name of new snapshot(com.apple.os.update-F5C5616AE870B47846005A91E114C0212A596352A26CD27BF28F6CA5A3C1009A)
patchd: patchd_macos_set_progress(137): Setting progress to 20.000000
ramrod_display_set_granular_progress_forced: 20.000000 (27.246094)
patchd: patchd_macos_set_progress_with_auto_increment(174): patchd_macos_set_progress_with_auto_increment: Configuring progress increment: Interval: 1.000000 Increment: 0.388889
patchd: patchd_macos_set_progress(133): Progress(20.000000) is beyond requested value(20.000000)patchd: patchd_macos_block_invoke_4(1684): Attempting to seal system volume(if needed)
patchd: patchd_macos_seal_system_volume(281): patchd_macos_seal_system_volume: Setting up environment for sealing system volume
Running mtree and saving output to /mnt5/mtree_remap.xml
Using xmtr tag for validating system manifest im4m
Clearing IMG4_FIRMWARE_SUBSEQUENT_STAGE flag for x86
ramrod_get_trusted_img4_payload: Attaching in passed in im4m to fw object
img4_firmware_execute failed: 2
patchd: MobileSoftwareUpdateErrorDomain error 1130 - Failed to verify against canonical metadata
ota-result = MSU 1130
executing /usr/sbin/nvram ota-result=MSU 1130
executing /usr/sbin/nvram ramrod-nvram-sequence=92
nvram successfully persisted to the filesystem
ota-initial-result = MSU 1130
executing /usr/sbin/nvram ramrod-nvram-sequence=93
nvram successfully persisted to the filesystem
patchd: patchd_store_failure_info(824): setting ota-failure-reason=MSU 1130 (Failed to verify against canonical metadata);NSPOSIXErrorDomain 2 (img4_firmware_execute failed);
ota-failure-reason = MSU 1130 (Failed to verify against canonical metadata);NSPOSIXErrorDomain 2 (img4_firmware_execute failed);
executing /usr/sbin/nvram ota-failure-reason=MSU 1130 (Failed to verify against canonical metadata);NSPOSIXErrorDomain 2 (img4_firmware_execute failed);
executing /usr/sbin/nvram ramrod-nvram-sequence=94
nvram successfully persisted to the filesystem
ota-initial-failure-reason = MSU 1130 (Failed to verify against canonical metadata);NSPOSIXErrorDomain 2 (img4_firmware_execute failed);
executing /usr/sbin/nvram ramrod-nvram-sequence=95
nvram successfully persisted to the filesystem
patchd: patchd_macos_block_invoke_4(1688): Failed to seal system volume
patchd: patchd_macos_block_invoke_4(1701): Returning from step patchd_seal_system_volume. Result is 1130
[16:59:04.0679-GMT]{3>6} CHECKPOINT FAILURE🙁FAILURE:1130) PATCHD:[0x0577] macos_seal_system_volume [0]LD(Failed to verify against canonical metadata)[1]D(img4_firmware_execute failed)
ota-step-results = {0x11070577:{0:1130}}
executing /usr/sbin/nvram ramrod-nvram-sequence=96
nvram successfully persisted to the filesystem
ota-step-codes = {0x11070577:{0:1130}}
executing /usr/sbin/nvram ramrod-nvram-sequence=97
nvram successfully persisted to the filesystem
ota-step-domains = {0x11070577:{0:"MobileSoftwareUpdateErrorDomain"}}
executing /usr/sbin/nvram ramrod-nvram-sequence=98
nvram successfully persisted to the filesystem
ota-step-error = {0x11070577:"[0]LD(Failed to verify against canonical metadata)[1]D(img4_firmware_execute failed)"}
executing /usr/sbin/nvram ramrod-nvram-sequence=99
nvram successfully persisted to the filesystem
ota-step-uptime = 88
executing /usr/sbin/nvram ramrod-nvram-sequence=100
nvram successfully persisted to the filesystem
ota-step-user-progress = 20
executing /usr/sbin/nvram ramrod-nvram-sequence=101
nvram successfully persisted to the filesystem
[16:59:04.0887-GMT]{3>6} CHECKPOINT NOTICE: (NVRAM set) ota-step-user-progress=20 [sync=true] (first failure)
[16:59:04.0887-GMT]{3>6} CHECKPOINT NOTICE: MAIN:[0x0104] handle_new_connections
[16:59:04.0888-GMT]{3>6} CHECKPOINT FINISHED-ENGINES🙁FAILURE:1) {0x11070577:{0:1130}}
[16:59:04.0889-GMT]{3>6} CHECKPOINT PROGRESS: FAILED (initial_engine) -> (initial_engine_failure)
ota-outcome = initial_engine_failure
executing /usr/sbin/nvram -s ota-outcome=initial_engine_failure
executing /usr/sbin/nvram ramrod-nvram-sequence=102
ramrod_display_set_granular_progress_forced: 21.000000 (28.125000)
nvram successfully persisted to the filesystem
[16:59:05.0051-GMT]{3>6} CHECKPOINT NOTICE: (NVRAM set) ota-outcome=initial_engine_failure [sync=true] (engine process terminating)

Is there any help to solve it?
My iMac is this:



Thank you[/SPOILER]

 

[davidlv]

I have a Mid 2010/2012 Mac Pro (first owner) with Monterey and I want to use TotalFinder. I tried everything to disable SIP and it never works. Is there a turnaround to bypass that security feature that Apple hardened? I really cannot live without TotalFinder.

If you only want to run Monterey, you do not need any OCLP version higher than 0.4.11, which enables SIP by default, but will let you disable SIP completely. Give it a try.

 

[sashkin_bro]

Hello everyone) I noticed that on my imac 21.5 2011, macos monterey 12.6.3 works worse than 12.6 animations, and I began to think hard, is this the case for everyone? it seems that it is only a security update, but it works worse than the older version, it is back to 12.6 😉 oc legacy patcher used the same 0.4.7

 

[nospamboz]

Is there any way to use a Terminal window command line to put Opencore on the Monterey installer USB? I need a way to bypass the GUI.

Well, nobody suggested anything, so I tried to figure it out on my own. The "Build" process creates a temporary directory containing "EFI" and "System" file trees, so I copied those to the USB installer from "createinstallmedia". (I noted that would overwrite a System "boot.efi" with a new one.)

I was able to boot the USB into Opencore.efi, but couldn't start the installer, so I booted back into Mojave....

...and discovered that simply booting into Opencore.efi on a USB overwrote my hard disk's Refind EFI setup, as well as overwriting some nvram variables.

Seriously, that was rude. That's the sort of behavior I expect from malware, not community software like Opencore.

My guess is that someone did some quick-and-dirty programming, without any "fail gracefully" finesse.

So, no, I'm not going this route any time soon. I was able to clean up that mess, and am not inclined to try and find more.

 

[haralds]

Resurrected my cMPro 5,1 after retiring and cleaning it off (NO!) I bought a Mac Studio Ultra to replace it.
But now, there is my "office" man cave project, and the 5,1 is just the thing.
Revived it with backups of Mojave and WinCloned Windows 10 and brought those up to date. Then followed up with a DosDude patched Catalina on another disk. My flashed RX 580 and upgraded WiFi BLE only require a hardware plist patch. SIP is fully enabled for these.
Catalina is great except for outdated Logic Pro and a number of synths like AniMoog not working.
So next was Monterey with the OpenCore Legacy patcher. I still have my old EFI OC config but decided to test the easy way to update. After a few failed attempts due to aging SSDs, Open Core Legacy Patcher GUI worked like a charm.
But I have some questions. Dortania points to Discord for answers, but the response seems very selective. Perhaps somebody here knows the answers.

The situation:

• Mac Pro 5,1 with flashed AMD-RX 580 and Broadcom BCM94352.
• Monterey installed using the OpenCore GUI. Catalina is running with full SIP using a simple DosDude patch for Hardware plist and a signed/notarized LegacyUSBInjector kext (codeless.)

What exactly does the OC Legacy PostPatch root patch do and is it needed for this config? I would like to run full SIP, if possible.

 

[PropClear]

Resurrected my cMPro 5,1 after retiring and cleaning it off (NO!) I bought a Mac Studio Ultra to replace it.
But now, there is my "office" man cave project, and the 5,1 is just the thing.
Revived it with backups of Mojave and WinCloned Windows 10 and brought those up to date. Then followed up with a DosDude patched Catalina on another disk. My flashed RX 580 and upgraded WiFi BLE only require a hardware plist patch. SIP is fully enabled for these.
Catalina is great except for outdated Logic Pro and a number of synths like AniMoog not working.
So next was Monterey with the OpenCore Legacy patcher. I still have my old EFI OC config but decided to test the easy way to update. After a few failed attempts due to aging SSDs, Open Core Legacy Patcher GUI worked like a charm.
But I have some questions. Dortania points to Discord for answers, but the response seems very selective. Perhaps somebody here knows the answers.

The situation:

• Mac Pro 5,1 with flashed AMD-RX 580 and Broadcom BCM94352.
• Monterey installed using the OpenCore GUI. Catalina is running with full SIP using a simple DosDude patch for Hardware plist and a signed/notarized LegacyUSBInjector kext (codeless.)

What exactly does the OC Legacy PostPatch root patch do and is it needed for this config? I would like to run full SIP, if possible.

Even with your flashed GPU you'll need the root patch because native your MacPro is not able to manage AVX2.0 - so full SIP will not be possible, but OCLP uses optimal settings after patching, so in my case cMP5.1 dual Xeon CPU X5690 96GB ram and 990 Pro on Lycom DT-130 NVMe card - it was worth to switch to Ventura because much faster boot times and aprox. 10% better performance compared to Monterey - so Yes you'll need root patching and must lower SIP here's a link to my BT Solution with the internal OSXWIFI Card - good luck, btw a amazing job done by the whole OCLP team😍!
Sorry my fault, Monterey will run with SIP fully enabled - no patches needed, also Wifi / BT should be fully supported under Monterey. Ventura needs the described root patching.

 

[internetzel]

Resurrected my cMPro 5,1 after retiring and cleaning it off (NO!) I bought a Mac Studio Ultra to replace it.
But now, there is my "office" man cave project, and the 5,1 is just the thing.
Revived it with backups of Mojave and WinCloned Windows 10 and brought those up to date. Then followed up with a DosDude patched Catalina on another disk. My flashed RX 580 and upgraded WiFi BLE only require a hardware plist patch. SIP is fully enabled for these.
Catalina is great except for outdated Logic Pro and a number of synths like AniMoog not working.
So next was Monterey with the OpenCore Legacy patcher. I still have my old EFI OC config but decided to test the easy way to update. After a few failed attempts due to aging SSDs, Open Core Legacy Patcher GUI worked like a charm.
But I have some questions. Dortania points to Discord for answers, but the response seems very selective. Perhaps somebody here knows the answers.

The situation:

• Mac Pro 5,1 with flashed AMD-RX 580 and Broadcom BCM94352.
• Monterey installed using the OpenCore GUI. Catalina is running with full SIP using a simple DosDude patch for Hardware plist and a signed/notarized LegacyUSBInjector kext (codeless.)

What exactly does the OC Legacy PostPatch root patch do and is it needed for this config? I would like to run full SIP, if possible.

OCLP will tell you whether patches are needed or not for your machine when clicking the button for installing the patches.
Furthermore the online documentation has some information about the different patches.
I don't know about the BCM94352 but otherwise your machine doesn't seem to need any post install patches for running Monterey; fully enabling SIP might be possible then, but you would have to manually configure OCLP to do so.
I have Big Sur running on a somewhat similar iMac late 2009, upgraded with an RX480 and Broadcom BCM4360, so no patches needed and SIP and AMFI can be fully enabled.

 

[trio93]

Failed to install Parallels
Hello everyone, need your advice, I tried installing Monterey on my macbook6,1 using OCLP 0.6.1 and it worked fine (at least office apps, adobe, R, spotify, etc. are working fine). However, I failed to install Parallels 17. Here's the fail record:
Please advise and your solution?

--------------
Translated Report (Full Report Below)
-------------------------------------

Process: prl_client_app [17833]
Path: /Volumes/VOLUME/Parallels Desktop.app/Contents/MacOS/prl_client_app
Identifier: com.parallels.desktop.console
Version: 17.1.0 (51516)
Build Info: Parallels-51516.0~17.1.51516.0
Code Type: X86-64 (Native)
Parent Process: Exited process [17828]
User ID: 501

Date/Time: 2023-02-06 21:30:36.8114 +0700
OS Version: macOS 12.4 (21F79)
Report Version: 12
Anonymous UUID: F4491A80-DEED-4C01-96A4-3E1261F18E35


Time Awake Since Boot: 2800 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00007ff8427a7460
Exception Codes: 0x0000000000000002, 0x00007ff8427a7460
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace SIGNAL, Code 10 Bus error: 10
Terminating Process: exc handler [17833]

 

[tec0815]

Problem cloning Monterey boot disk

Has someone ever managed to successfully clone an OCLP bootdisk on Monterey? I am using CCC 6.1.4 with the clone option on a MacPro5,1, but the cloning starts and stops after 12 seconds with an error "This volume is missing". Does anyone know a fix?

Next question: If cloning does not work anymore, how do I recover my Monterey installation if "something goes wrong"? I don't want to go back to El Capitan (the latest native MacOS) to reinstall everything.

I would appreciate any hint.

 

[Dilli]

Problem cloning Monterey boot disk

Has someone ever managed to successfully clone an OCLP bootdisk on Monterey? I am using CCC 6.1.4 with the clone option on a MacPro5,1, but the cloning starts and stops after 12 seconds with an error "This volume is missing". Does anyone know a fix?

Next question: If cloning does not work anymore, how do I recover my Monterey installation if "something goes wrong"? I don't want to go back to El Capitan (the latest native MacOS) to reinstall everything.

I would appreciate any hint.

Maybe this will help