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.
@nekton1 I don't know the OCLP behavior with your MM7,1; however, if you didn't perform a clean install, that may be suspect.

If you inspect your Open Core config.plist again and look at the top section labeled "#Revision," what do you see? Can you post it? It should look something like this:
View attachment 2474242

Note that your "format" is not different from mine, just the "view" is different. The config.plist format (raw file) is unchanging. The view depends on which plist editor (or raw editor) you're using to view the file. I use Xcode.

EDIT: @nekton1 On your iMac16,1, if you want to enable spoofing, you should be able to do the following: 1) Run OCLP 2.2.0 on your iMac16,1 2) change SMBIOS spoofing level to "Moderate" under the SMBIOS tab 3) Return to the main menu and "Build and Install Open Core" and click "Install to Disk" when prompted.

I prefer to install the OC EFI to a GUID formatted USB thumb drive for testing before I make it "permanent" on my SSD. That way, if I screw it up, I can always remove the USB thumb drive and boot to recover.
Here it is:

</data>
<key>Hardware-Wifi</key>
<string>14E4:43A0</string>
<key>Hardware-iMac-dGPU-1</key>
<string>8086:A2E</string>
<key>OpenCore-Version</key>
<string>1.0.1 - RELEASE</string>
<key>Original-Model</key>
<string>Macmini7,1</string>
<key>Spoofed-Model</key>
<string>Macmini8,1 - Moderate</string>

Thanks for the 16,1 spoofing advice.
 
  • Like
Reactions: K two and deeveedee
@nekton1 I don't know the OCLP behavior with your MM7,1; however, if you didn't perform a clean install, that may be suspect.

If you inspect your Open Core config.plist again and look at the top section labeled "#Revision," what do you see? Can you post it? It should look something like this:
View attachment 2474242

Note that your "format" is not different from mine, just the "view" is different. The config.plist format (raw file) is unchanging. The view depends on which plist editor (or raw editor) you're using to view the file. I use Xcode.

EDIT: @nekton1 On your iMac16,1, if you want to enable spoofing, you should be able to do the following: 1) Run OCLP 2.2.0 on your iMac16,1 2) change SMBIOS spoofing level to "Moderate" under the SMBIOS tab 3) Return to the main menu and "Build and Install Open Core" and click "Install to Disk" when prompted.

I prefer to install the OC EFI to a GUID formatted USB thumb drive for testing before I make it "permanent" on my SSD. That way, if I screw it up, I can always remove the USB thumb drive and boot to recover.
Spoofing the iMac 16.1 to 18,2 worked as you described but still no Universal Control at either spoofed MM 8,1 or iMac 18,2.
 
I just stumbled upon this thread while searching for something else and found it quite curious. For those of you trying to run on really old hardware, what is the reason behind it? Are you rebels? Do you like a challenge? Are you into masochism? Are you poor?
 
  • Haha
Reactions: JedNZ
Apple Watch does not unlock mac. It did on 15.0.1.
This was not an OCLP problem.

Yesterday I turned off my Apple Watch and iPhone and rebooted my mac. I did not do it to solve the unlock problem, but it did.

I have done nothing to OCLP or MacOS since I reported it. I have upgraded my iPhone a week ago.
 
Spoofing the iMac 16.1 to 18,2 worked as you described but still no Universal Control at either spoofed MM 8,1 or iMac 18,2.
I can only help you with the spoofing part since I don't have your Macs to test and don't use UC myself.

Why are you spoofing iMac18,2 on your iMac16,1? According to the OCLP docs here, selecting Moderate spoofing is supposed to spoof iMac19,2.
Screenshot 2025-01-21 at 7.44.33 AM.png


If OCLP is spoofing iMac18,2 when Moderate spoofing is selected, you may have found a bug or a problem with documentation. Good luck!

EDIT: @nekton1 I thought you were testing Sequoia (since we're in the Sequoia thread). According to OCLP docs here, spoofing for iMac16,1 depends on which macOS you're running. For example, on my MBP6,2 running Ventura, I "built open core" with OCLP 2.2.0 (Release) for IMac16,1 with Moderate spoofing. OCLP generated an Open Core EFI spoofing iMac18,3 which is different from what you found and different from Dortania docs (which say to spoof iMac18,2). For Sequoia, the OCLP docs say you should be spoofing iMac19,2 for UC.

EDIT2: @nekton1 It appears to me that there is a difference between OCLP docs and OCLP behavior. Docs say that, for iMac16,1, spoof iMac18,2 for Ventura and iMac19,2 for Sequoia. I just performed another test on my MBP6,2 running Sequoia 15,2. When I "build open core" for iMac16,1 with Moderate spoofing, the resulting Open Core EFI still spoofs iMac18,3 (as it did when I ran OCLP in Ventura). Not sure what's going on, so you may need to experiment with different SMBIOS spoofing to find the solution. Sorry I couldn't be more helpful.

EDIT3: It's also possible that since I'm testing on my MBP6,2 (requiring me to manually set the Host Model to iMac16,1) that I'm overriding OCLP auto-detection and "breaking" its spoofing detection. Will be interested to learn your results when running OCLP on your iMac16,1 / Sequoia.
 
Last edited:
  • Like
Reactions: houser
If you inspect your Open Core config.plist again and look at the top section labeled "#Revision," what do you see? Can you post it? It should look something like this:
Screenshot 2025-01-20 at 8.31.56 PM.png


Note that your "format" is not different from mine, just the "view" is different. The config.plist format (raw file) is unchanging. The view depends on which plist editor (or raw editor) you're using to view the file. I use Xcode.

I really like the GUI to inspect the plist file.👍🏻 But installing XCODE for that alone is over 12GB 😱
Does anyone know of another free Mac application that offers this view and is only a few MB in size?


This was not an OCLP problem.

Yesterday I turned off my Apple Watch and iPhone and rebooted my mac. I did not do it to solve the unlock problem, but it did.

I have done nothing to OCLP or MacOS since I reported it. I have upgraded my iPhone a week ago.
I had the same problem and have since realized that it's always the Apple Watch that causes problems for me. After I rebooted the Apple Watch - Mac does not need to be rebooted - the unlock of the MacBook with the Apple Watch works again. 👍🏻
 
I really like the GUI to inspect the plist file.👍🏻 But installing XCODE for that alone is over 12GB 😱
Does anyone know of another free Mac application that offers this view and is only a few MB in size?
ProperTree by CorpNewt has been specifically written for editing OpenCore plists, as a prerequisite you need rather up to date Python for it to work well.
 
macOS 15.3 Kernel 24D60 Release Candidate is available.
MBP11,1: updated OTA from 15.3b3 to RC (24D60) on external SSD. Using OCLP 2.2.0.
Smooth update and running, no surprises. Thanks to developers!

The metallib from b3 is used in root patching (wired ethernet works but metallib for RC not there yet).
 

Attachments

  • thissys.png
    thissys.png
    140 KB · Views: 36
  • Bildschirmfoto 2025-01-21 um 23.17.21.png
    Bildschirmfoto 2025-01-21 um 23.17.21.png
    380.8 KB · Views: 37
Last edited:
OTA update to 24D60 done using 2.2.0.

Intervention through hard reset was necessary as expected at this point:

AppleUserUSBHostHIDDevice:0x10000047d close by AppleUserHIDEventDriver:0x1000004bf (0x0)

DK: AppleUserHIDEventDriver-0x1000004bf :force close (AppleUserUSBHostHI

Windowserver crashed
Kernelpanic

Continued installation using safe mode.

Patching was rather uneventful and went as expected.

Edit: This update sent the bluetooth module to neverland.

Bluetooth Controller:
Address: NULL
State: Off
Chipset: BCM_4350C2
Discoverable: Off
Firmware Version: v0 c0
Supported services: 0x392039 < HFP AVRCP A2DP HID Braille LEA AACP GATT SerialPort >
Transport: USB
Vendor ID: 0x004C (Apple)

Fix: Removed power/battery. Performed SMC reset (Not NVRAM reset).

State: On
Chipset: BCM_20702A3
Discoverable: Off
Firmware Version: v156 c5914
Supported services: 0x392039 < HFP AVRCP A2DP HID Braille LEA AACP GATT SerialPort >
Transport: USB
Vendor ID: 0x004C (Apple)
 
Last edited:
MacBookPro14,1: macOS 15.3 (24D60)
still smooth...
Thanks Devs
 

Attachments

  • Screenshot 2025-01-22 at 01.18.37.png
    Screenshot 2025-01-22 at 01.18.37.png
    268 KB · Views: 38
  • Screenshot 2025-01-22 at 01.23.17.png
    Screenshot 2025-01-22 at 01.23.17.png
    495 KB · Views: 38
I just stumbled upon this thread while searching for something else and found it quite curious. For those of you trying to run on really old hardware, what is the reason behind it? Are you rebels? Do you like a challenge? Are you into masochism? Are you poor?
Dear friend @hoodafoo, I will pretend that I did not understand and I will gloss over your somewhat sarcastic and perhaps somewhat insulting attitude toward some users who really have financial difficulties and I will try, therefore, to respond regarding my choice to use OCLP.

I have a wonderful and perfect late 2013 iMac purchased from Apple, in BTO and therefore with the most powerful hardware configuration. You can see the features in my signature below. (Note: if you use your smartphone, put it horizontally to see the signatures)

Let me preface this by saying that I am well aware (!!) that my Mac has - obviously - objective hardware limitations that cannot be overcome; for example, when it comes to encoding and exporting video, my Mac cannot compete with the new Apple Silicon; but this, nevertheless, I do not do or do rarely and with little complexity and in any case the behavior of my Mac satisfies me, even if I have to wait a few minutes longer for Da Vinci Resolve or Final Cut Pro (however fast while using they...) to save the video.

But apart from this aspect, thanks to OCLP and macOS Sonoma or with Sequoia [see *Note at the end] the behavior of my iMac, both using Finder and in my usual uses, while working on it is perfectly superimposable to that of a last generation Mac.
Everything works 100% better than Catalina which is the latest officially supported OS, even Photoshop 2025 (26.2) and all other Apple or third-party applications.

Do you therefore think I should scrap the Mac? ....
So, instead of being argumentative towards us passionate and capable to use OCLP very well and/or maybe even economically indigents, why aren't you argumentative towards Apple?
To Apple would have been enough mainly not to remove many drivers present in macOS and some other small tricks and gimmicks. If you know or examine WHAT OCLP does, in fact, you will find that it is basically super simple and, most importantly, does not alter the System.

At the limit, Apple could have made people accept the total absence of warranty and service for Macs with a certain number of years (but in fact Apple already acts that way!!!).
Backwards compatibility, so, was easily possible at least up to the 2013 Macs since these Macs, up to the earliest versions of macOS Monterey, still maintained all the necessary drivers.

I hope I have answered your questions, at least to a large extent.

[*Note:
From my point of view, macOS Sequoia still has some minor problems, both with OCLP and with supported Macs, since Sequoia is in fact a quasi-experimental system because of the constant additions regarding AI and other innovations, experimental or otherwise, that are useless to many users and/or that many users will never use.
Maybe when it is all ripe and really necessary to have a new Mac we will all buy it and even the poor will find many cheap ones in the used market.
But until then: OCLP forever and endless thanks to its Developers, all living Saints :) ]
 
I just stumbled upon this thread while searching for something else and found it quite curious. For those of you trying to run on really old hardware, what is the reason behind it? Are you rebels? Do you like a challenge? Are you into masochism? Are you poor?
poor sustainability rebel here...greetings from the Caribbean...🏝️🇨🇼
 
I'm really looking forward to the dual socket support for my MacPro3,1 with OCLP and Sequoia. I've already tried it with 4 cores, but the performance drops significantly.

Hopefully the developers involved will find a way for this Mac to run with 8 cores. That would be great.

Is there any news on this that I may have missed?
 
Hello to all,

iMac 13,2 (2012 - Metal capable)

Updated OTA to 15.3 RC from 15.3 beta 3 after reverting OCLP 2.2 patches ( patches prevent any updates from downloading via OTA on said machine).

See post# 2119 page# 85 for steps usually taken to update OTA on both iMac 13,2 and MacBook Pro 5,2. (Latter is a 2009 and Not Metal capable).

While OTA update appeared to complete, upon last reboot during installation process, iMac went into boot loop. I was forced to shut down via power button, then reboot into recovery partition. I was able to use recovery’s OS system reinstall function to install 15.3 beta 3 version of Sequoia OTA, then, without patching, initiated OTA update to 15.3 RC. This time installation completed, and patching with OCLP 2.2 went without untoward “sequelae”. Metal Lib library downloaded mid-patching process, as designed; the Metal lib descriptive matched 24D60 designation. Note, computers are connected to Ethernet while updating OS to allow Metal Lib and KDK downloads initiated by OCLP.

WiFi, Bluetooth, Networking, Hand off, Air Drop and continuity features work without noticeable problems.

MacBook Pro 5,2 2009 - listed as the process may apply to other not-metal capable computers.

Updated OTA to 15.3. RC from 15.3 beat3 without issues; patching process was uneventful, however, OCLP mediated automatic KDK download would not complete; the download window showed no progress. Had to download KDK from Apple developer’s website and install it manually, then initiate successful patching.

Observations:

Grey Screen- appears for brief moment on iMac, when installing or upgrading OS, before showing wall paper or desktop background. It does not occur when rebooting or waking up from sleep. MacBook Pro 5,2 shows grey screen for about 15 to 20 seconds, post OS installation, before standard desktop of wall paper appears. It does not appear when waking up from sleep or rebooting.

Sluggishness after using OCLP to install OS: as reported by others, there is a lot of background activity that needs to be completed when unsupported machines boot into latest OS.
A good way to monitor what is happening in the background is to have Activity Monitor (located in utilities folder) run in the background (probably familiar to most already, but just in case). Start Activity Monitor app. before updating OS; it will relaunch automatically once desktop is reached after OS installation. Make sure that the “monitoring scope” is set for “All Processes” and not just “My Processes” ( go to “View” in application’s menu bar, and select “All Processes” from dropdown menu.
Then, look at “% CPU” column in application window, and note which processes are taxing CPU; medianalysisd, photanalysisd, crashreporter and tailspin are some of the applications that often take high percentage of the CPU. Those processes can be selected (individually) and stopped, by clicking on the name of process, to highlight it, then clicking button marked by a circle with an X symbol in it; the button is located just above the “%CPU” column heading.
The processes listed above can be “deleted” with impunity. If the process restarts, repeat above steps to inactivate it again. There are other rogue activities that can be discontinued in similar manner. Doing this “cleanup” can substantially reduce CPU lug and decrease time for the computer to return to “idle”.
Note also the box, just below “%CPU” column; it shows percentage of CPU that is being utilized. If “idle” percentage is 0, computer will be sluggish until background activity completes, or given process is forced to discontinue (see above).
When no maintenance activity or active applications are consuming CPU, iMac 13,2 idles at between 98 to > 99%. This denotes that 98 to > 99% of CPU “power” is available for use. MacBook Pro 5,2 idles (minimum CPU activity) at 96 to > 97%.

I am sure most are already aware of Activity Monitor’s function.

Some Application compatibility data:
iMac 13,2 under Sequoia 15.3 RC can utilize at speed:
LibreOffice (need to download JDK for data base functions), GIMP (version 3.0), Blender (up to Version 3.6.9), iWork, Keynote, Numbers (latest versions), and applications usually bundled with system when OS is installed.
There are other compatible applications, but those specifically listed I actually tested, and are open source/free (for most personal use scenarios(?)). [Disclaimer: I have no direct connection, in any way, with developers of any of the listed applications, I am an end user]. Downloading alternate browser, to supplement Safari, is another good preemptive measure to guard against possible incompatibility.

Multiple Mac OS systems on same drive (internal or external) on one computer; see Post #2195 on Page# 88 for details.

I have not encountered any discernible problems running multiple Mac OS variants on same machine, and iCloud data syncs without problems, albeit all instances connect to same Apple account, whether utilizing Catalina, Sonoma or Sequoia variants.

Another great feat by the developers to “purvey” newest Mac OS for the unsupported machines.

Hope some of the above data may be of help.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.