Try to boot in safe mode and do the root patches from there
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 14 Sonoma on Unsupported Macs Thread
- Thread starter dhinakg
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
What version of OCLP were you using? I had a similar issue getting the Post install root patches installed, and using OCLP 1.2.0 nightly link solved that problem. Do a search for the bold phase on this thread for a link to that version.
Safe mode took a couple shots for it to register for me, but eventually did work after resetting PRAM/NVRAM and SMC.
When resetting PRAM/NVRAM, you do have to hold the Option key while booting like when you update OCLP, then the shift+enter on the Sonoma disk.
Any specific errors? or does it just get stuck on the progress bar?
Updated OCLP to version 1.2.0 using link found. But still same error: Reason for Patch Failure (31).
nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:OCLP-Version
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:OCLP-Version 1.2.0%00
I will try resetting.
Sonoma starts normally. Problem that none of the root patches could be applied.
Reason for Patch Failure (31):
No variant specified, falling back to release
No variant specified, falling back to release
Error Domain=KMErrorDomain Code=31 «Error occurred while building a collection:
1: One or more binaries has an error which prevented linking. See other errors.
2: Could not use ‘com.nvidia.web.GeForceWeb’ because:
Cannot find symbol for metaclass pointed by ‘__ZN16nvDisplayManager10superClassE’. Expected symbol ‘__ZN22lOAccelDisplayMachine210gMetaClassE’ to be defined in another kextCannot find symbol for metaclass point to by ‘__ZN13nvDisplayPipe10superClassE’.
Expected symbol ‘__ZN19lOAccelDisplayPipe210gMetaClassE’ to be defined in another kextCannot find symbol for metaclass pointed to by ‘__ZN9nvSurface10superClassE’. Expected symbol ‘__ZN15lOAccelSurface210gMetaClassE’ to be defined in another kext com.nvidia.web.GeForceWeb specific:
1: Cannot find symbol for metaclass pointed to by ‘__ZN16nvDisplayManager10superClassE’. Expected symbold ‘__ZN22lOAccelDisplayMachine210gMetaClassE’ to be defined in another kextCannot find symbol for metaclass pointed to by ‘__ZN13nvDisplayPipe10superClassE’.
Expected symbol ‘__ZN19IOAccelDisplayPipe210gMetaClassE’ to be defined in another kext
Cannot find symbol for metaclass pointed to by ‘__ZN9nvSurface10superClassE’. Expected symbol ‘__ZN15IOAccelSurface210gMetaClassE’ to be defined in another kext
« UserInfo={NSLocalizedDescription=Error occured while building a collection:
1: One or more binaries has an error which prevented linking. See other errors.
2: Could not use ‘com.nvidia.web.GeForceWeb’ because: Cannot find symbol for metaclass pointed to by: ‘_ZN16nvDisplayManager10superClassE’.
Expected symbol ‘__ZN22IOAccelDisplayMachine210gMetaClassE’ to be defined in another kext
Cannot find symbol for metaclass pointed to by ‘__ZN13nvDisplayPipe10superClassE’.
Expected symbol ‘__ZN19IOAccelDisplayPipe210gMetaClassE’ to be defined in another kext
Cannot find symbol for metaclass pointed to by ‘__ZN9nvSurface10superClassE’. Expected symbol ‘__ZN15IOAccelSurface210gMetaClassE’ to be defined in another kext com.nvidia.web.GeForceWeb specific:
1: Cannot find symbol for metaclass pointed to by ‘__ZN16nvDisplayManager10superClassE’. Expected symbol ‘__ZN22IOAccelDisplayMachine210gMetaClassE’ to be defined in another kext
Cannot find symbol for metaclass pointed to by ‘__ZN13nvDisplayPipe10superClassE’.
Expected symbol ‘__ZN19IOAccelDisplayPipe210gMetaClassE’ to be defined in another kext
Cannot find symbol to metaclass pointed to by ‘__ZN9nvSurface10superClassE’. Expected symbol ‘__ZN15IOAccelSurface210gMetaClassE’ to be defined in another kext
}
Please reboot the machine to avoid potential issues rerunning the patcher.
Stocks app still broken in MacOS 14.2 Beta w/ OCLP v.1.2.0n, both Widget and app. All OK in macOS 14.1 w/OCLP v.1.1.0
Works without issues on my MacBook Pro 2014 Widget and app 14.2 with OCLP 1.2n .
Unfortunately resetting - does not solve my issue.
Maybe with Sonoma some tools (apps for kext compilig, applying etc) are being changed and do not work like they did before Sonoma? And because of that some of the code could not be applied?
I've jumped to the Sonoma after using Monterey, skipping Ventura. Maybe this is the root of my problem?
I thought Safe Mode was Shift (only). Restart a machine holding down Shift until the Apple logo appears.
It is the same way, tried both. Just adding Enter speeds up choosing an option. And on a screen I do see that it started in Safe mode with red font at the corner.
If someone has any idea or knowledge how to fix my issue - I will be much thankful for helping me. Currently due to lags, impossible to use brightness control, no GPU acceleration, CPU high usage - it is nearly impossible to use system.
No. If OCLP is installed, to enter Safe Mode you need to press the Shift key in this sequence:
- First shut down and then start your Mac
- When the beep sounds, press and hold the Option key
When OCLP EFIBoot appears, press the left Shift key, then press Enter.
You can also use another method and that is, after starting the Mac, wait for the disk icon with Sonoma to appear and then immediately press the space bar. All the OCLP options appear and at this point you can press the left Shift key and then Enter
Good afternoon I have exactly the same computer as yours. When updating Sonoma 14.1, the installation file downloaded was over 12 gigabytes in size. OCLP 1.1 installed. I don't have any of the problems you described. The entire update went smoothly and well. All functions work as they should (video acceleration, backlight and sound control) I think you have some kind of hardware problem.
That's part of what confused me about the pop-up. It is already disabled in the way you described, but did not stop the pop-up. Blocking by explicitly adding the fully-qualified mediasharingd path to "System Settings > Network > Firewall > Options > Block Incoming" works. Little Snitch recommended by @amaze1499 would work, too.
Skipping Monterey shouldn't be a problem, but I've resolved many issues with clean installs of macOS.
If you have enough storage, install macOS to a new APFS volume and use Migration Assistant as the last step of the macOS install (when prompted).
I edited my reply - thought he had upgraded from Mojave at first. You're too quick for me.
Sorry for the delay in response...
I don't actually know where to find any of that... The Wi-Fi card is the one that comes in it as standard; a Broadcom one.
Hi, @lab1r1nt! I also have a 27" iMac from late 2013 (i7 and GTX780M) and it accepts macOS 11, 12 and 13 without problems with which everything works perfectly.
It also works well with macOS 14.0 and OCLP 1.1.0 or 1.2.0 Nightly, except Continuity Camera and some other small problems that we hope can be solved.
From what you write unfortunately I think that you are approaching the problem in the wrong way, unless you are very expert; but in this case you would have solved the problem without asking for help...
The only way I recommend, therefore, is to create a macOS 14.0 installer on a USB stick, using the appropriate button in OCLP. You will then have to use this stick to install Sonoma.
In this way, in fact, OCLP It also automatically installs the most suitable hardware patch for your Mac.
In your place I would do as I said and if I still had problems I would do it again, but this time after formatting the disk from Recovery mode, before continuing with the installation.
After this operation, if the problems persist, it could almost certainly be a hardware problem.
I would add that in my case, in moment I decided to install Big Sur, I eliminated the Fusion Drive and replaced the mechanical HD with a 2 TB SSD. However, I kept the 128GB Apple SSD on which I still installed Catalina
Bye ✌️
In a quest to get 14.1 installed cleanly I decided to install 1.2.0 nightly. Python 3.10.11 from python.org is installed on the rMBP10,1
Downloaded the OCLP nightly package from GitHub following all instructions and ran the GUI from terminal. Installed 1.2.0 nightly to disk successfully.
It rebooted fine so I reran the GUI from terminal and attempted to apply root patches, got the error message below.
So I deleted the first OCLP nightly download and redownloaded it. Same result.
Has anyone else experienced this? I'm wondering if the message is spurious and that I should have removed the 1.1.0 root patches before attempting to repatch(?)
Edit, later: Tried safe mode boot, removing the 1.1.0 root patches, rebooting again into safe mode, and installing the 1.2.0 patches from terminal. Same result. Put the 1.1.0 patches back, all OK
Downloaded the OCLP nightly package from GitHub following all instructions and ran the GUI from terminal. Installed 1.2.0 nightly to disk successfully.
It rebooted fine so I reran the GUI from terminal and attempted to apply root patches, got the error message below.
So I deleted the first OCLP nightly download and redownloaded it. Same result.
Has anyone else experienced this? I'm wondering if the message is spurious and that I should have removed the 1.1.0 root patches before attempting to repatch(?)
Edit, later: Tried safe mode boot, removing the 1.1.0 root patches, rebooting again into safe mode, and installing the 1.2.0 patches from terminal. Same result. Put the 1.1.0 patches back, all OK
Last edited:
Hello @OKonnel ,
I was tried installing (upgrading) Sonoma once more again using pre-downloaded image from OCLP. And it did not work. Same issue was present.
And creating new APFS volume and making fresh install of Sonoma and then by last step just migrate everything I had on the previous volume - and at least currently brightness/volume control keys are functioning, as well as graphics is way faster and seems that has proper acceleration (keeping in mind that hardware wise this is already old one), and CPU does not go to 100% all the time. Seems that it was some bug, maybe related to some software I had, don't know.
Now there are some minor problems that all software requires updates. And for some reason Lightroom asks for converting to newer library and just shuts application after 10 seconds or so (if someone faced with same issue and knows how to solve that, I will be very thankful). But never the less, system is now stable and I could keep working using this Mac again.
Thanks @deeveedee for your tip about trying to make fresh install.
Thank you everyone for your help, suggestions!
Trying to update the firmware on my MacBook Pro 12,1, to the very latest version: 486.0.0.0.0
using what I believe should get me there.
That is, Installing Monterey v12.7.1 (unless the firmware is in a prior version of Monterey, please advise)
From the very first post in this thread, dhinakg writes;
- Note that when booting a supported OS to get firmware updates it must not be booted via OpenCore.
Press alt/option on boot and do a PRAM reset before booting back into Ventura. -
What is the Exact keystroke sequence to accomplish this very thing, please?
So
Power On and hold option key,
then
what keystrokes exactly & when, to do the PRAM reset, please?
using what I believe should get me there.
That is, Installing Monterey v12.7.1 (unless the firmware is in a prior version of Monterey, please advise)
From the very first post in this thread, dhinakg writes;
- Note that when booting a supported OS to get firmware updates it must not be booted via OpenCore.
Press alt/option on boot and do a PRAM reset before booting back into Ventura. -
What is the Exact keystroke sequence to accomplish this very thing, please?
So
Power On and hold option key,
then
what keystrokes exactly & when, to do the PRAM reset, please?
Mini7,1 OCLP v.1.2.0n (11/1 8:28 AM build) macOS 14.2 build 23C5030f aka Beta 1, SMC/NVRAM 3 Bong reset, Safe Boot, remove Post-install patches, Safe-reboot, re-install Post-install patches, reboot - Stocks app and Widget both inop, Stocks app requires Force quit after it appears in the Dock. In macOS 14.1 everything OK. 🤔
Select the native macOS in Systems Settings>General>Startup Disk, reboot, hold option/command/p/r for three(3) restarts. 😶🌫️
Last edited:
As Ktwo said, and as in dhinakg's instructions, Power on and immediately hold down the Option + Command + p + r keys, i.e., before booting into OCLP via the EFI, not after as you were doing.
then Hold down the Option key to get the OCLP boot picker, select the EFI icon with the TAB key and hit Enter,
Then select the target start up volume, using either the tab key or a mouse/trackpad.
If you need to boot into Safe mode, hold down the option key to get into the boot picker, select the EFT icon, hit Enter, and then the left Shift key as you select the target start up disk and press enter.
What version of OCLP are you using?
Last edited:
Quick question. In my "Applications", I noticed there's two OCLP programs...one is OCLP 0.6.8 and the other is a shortcut, but when you click on it it opens OCLP 1.1.0....Everything is running fine. Why are there two patchers installed? Should I delete 0.6.8?