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.
Right. Adding to yor last sentence, kexts in /Library/Extensions are not removed while installing a new macOS version. They seem to be essential in KDK-less patching (as for my MBP11,1).
They get removed by reverting root patches (or by removing them manually), and are put there while root patching.
Even if they are the correct versions, they may not harmonize with the not-yet-patched system (as in my case).
The solution is simple: if there is a boot loop or login loop after installing new macOS, boot in safe mode then apply the root patches, and all fine. See my previous post #4,147 .
Sorry for the longish explanation of my special case - and correct me if this is the wrong interpretation.
Not 100% sure, but there has been code added to get rid of the additional extensions. Since I do not own a single KDK less patched system I am kind of blind on this eye. At least command line arguments are there.

Take a look at the current changelog.md on the Github page (referring to 1.2.0)

  • Add new arguments:
    • --cache_os: Cache necessary patcher files for OS to be installed (ex. KDKs)
    • --prepare_for_update: Clean up patcher files for OS to be installed (ex. /Library/Extensions)
 
Hello Good People,

I was able to install Sonoma v14.2 without any issues. Also rocking the latest OpenCore 1.3.0
The desktop images are now appearing like in v14.1
v14.2 and v14.1.2 seem a bit slower on my MacBookPro 8,3 than v14.0.
I turned off animated wallpaper and reduced transparency and still see the non animated spinning beachball more than I would like.

Thank you All :)
 
Not 100% sure, but there has been code added to get rid of the additional extensions. Since I do not own a single KDK less patched system I am kind of blind on this eye. At least command line arguments are there.

Take a look at the current changelog.md on the Github page (referring to 1.2.0)

  • Add new arguments:
    • --cache_os: Cache necessary patcher files for OS to be installed (ex. KDKs)
    • --prepare_for_update: Clean up patcher files for OS to be installed (ex. /Library/Extensions)
Thanks. Yes, there is code added in resources/sys_patch/sys_patch.py (_clean_auxiliary_kc). It is executed (only) when reverting the root patches and does its job well.
Still need to look at these arguments... --prepare_for_update sounds promising.

The code for it is in resources/arguments.py (_clean_le_handler invoked by prepare_for_update_handler)
Will try to see what happens. Code executes only if an update is staged in /System/Volumes/Update so not at the moment.
 

Attachments

  • Bildschirmfoto 2023-12-13 um 22.46.38.png
    Bildschirmfoto 2023-12-13 um 22.46.38.png
    80.7 KB · Views: 52
Last edited:
  • Like
Reactions: perez987 and K two
… BTW, talking about paravirtualization, I made yet another new macOS VM in the newly updated Parallels 19.2.0 and Sonoma 14.2, but sadly it still doesn’t work: and, as has happened since upgrading to Sonoma, the VM boots into a black screen (and using it without paravirtualization, with the old non-accelerated Parallels driver, renders it of little practical use: too slow and without transparency effects). So, definitely still an issue…
 
  • Like
Reactions: josehill
Just a small hint, when updating a MacBookPro 6,2 OCLP 1.3.0 sadly did not show the top menu finder etc. and is not able to start apps etc. in my case - patching with OCLP 1.2.1 relase version works like a charm, only MacBookPro 6,2 15" is affected in may case - booting in safe mode and repatching with 1.2.1 solved all problems - may this helps when migrating to macOS 14.2 🤞
 
  • Like
Reactions: K two
right now I'm running 14.1 on my MBP 11,3 with OCLP 1.3.0.
when i click the update button in SoftwareUpdate, no OCLP Notification appears to download the latest KDKs for 14.2.
Is this ok? Can I update? I ask because I read earlier in this forum, that the needed KDKs for 14.2 are downloaded bei OCLP?
Do I need to download them manually? Where can I find those?
Kind regards!
Not all Macs need KDK i.e. my 15" rMBP 11,2 2014 neither. But I download BEFORE Update the KDK manually – as a "safe net" 😉


Try switching between discrete graphics or integrated one. Memories will work but only on discrete graphics for me if that’s a option.
😢 Many users waiting for a solution with iGPU (see i.e. OCLP discord), my 15" rMBP 11,2 2014 has also only iGPU
Fingers crossed that the developers find a solution.🤗


Someone on YT asked me if stickers in iMessage on Mac work. I never used them and checked for him. Indeed stickers don't work. Menu closes immediately before I can select a sticker. Posting this for the devs...
Yeah, don't work at my 15" rMBP 11,2 2014 neither.

❗️DON'T try to set a Memoji cause this freezes or crashes with no chance of revert the system.
This happened to me by accident last night, as iOS 17.1+ offers "Contact Photo" and "Poster" as new features in the Contacts app. Memoji in "Contact photo" is synchronized with iCloud User pic + Mac Login pic❗️😢

After that, despite several hours of trying, nothing could be recovered and I had to reset my 15" rMBP 11,2 mid 2014.😢
 
Last edited:
right now I'm running 14.1 on my MBP 11,3 with OCLP 1.3.0.
when i click the update button in SoftwareUpdate, no OCLP Notification appears to download the latest KDKs for 14.2.
Is this ok? Can I update? I ask because I read earlier in this forum, that the needed KDKs for 14.2 are downloaded bei OCLP?
Do I need to download them manually? Where can I find those?
Kind regards!
Here in Mr. Macintosh's latest video (position already marked) you see which machines need KDKs and how to install them if needed. If you start the OTA update and OCLP does not force KDK downlaod automatically, your machine most probably does not need KDKs. After this clarification I deleted the KDK folder on my Mac. No issues afterwards. My Macbook Pro was updated without any KDKs. No problems there either.
 
Mac Pro 5,1 OCLP 1.2.1 upgraded to OCLP 1.3.0. Everything workrs like a charm. Now upgrading to Sonoma 14.2
This feature of OCLP is simply amazing.
Same here. After upgrading my Early 2015 11" Macbook Air (already posted), I've decided to resurrect my venerable Mid 2009 17" Macbook Pro (MBP 5,2) which had a blown component at the supply stage that would reboot and loop right after boot. First upgraded from Mojave to Monterey with 1.2.1 and then the big step to the OTA Sonoma 14.1.2 (with a usb 2.0+ hub as you still need to login to patch) with 1.3.0. I was very impressed seeing the automatic download and install of KDK. Amazing stuff, thank you guys again and again. And then again to OTA 14.2, this time OCLP detected the OTA and downloaded the KDK *before* the Sonoma install and reboot, so that the patching was a breeze. 👏🙏🥳😎
 

Attachments

  • Sonoma_14.2_on_MBP17.png
    Sonoma_14.2_on_MBP17.png
    40.2 KB · Views: 71
3D acceleration works fine on my machine (MBP11,3, with Intel iGPU and Nvidia dGPU) for Windows and Linux VMs, both in Fusion and Parallels; while it hasn’t worked anymore since upgrading to Sonoma for macOS VMs (paravirtualization). But this might also depend on the specific machine: for example, I don’t know how it is for AMD GPUs…
The issue is with AMD GCN GPUs ...
 
  • Like
Reactions: Sven G
3D acceleration works fine on my machine (MBP11,3, with Intel iGPU and Nvidia dGPU) for Windows and Linux VMs, both in Fusion and Parallels; while it hasn’t worked anymore since upgrading to Sonoma for macOS VMs (paravirtualization). But this might also depend on the specific machine: for example, I don’t know how it is for AMD GPUs…
It's the AMD GPUs i need to know about The 11,1 has an intel Iris and it works on that, but that machine isn't worth depending on anymore. I am following AMD support because that's what the iMac has and is the computer I currently need stable and dependable.
 
  • Like
Reactions: Sven G
iMac 14,2. Updated to OCLP 1.3.0 then OTA update to 14.2. So far no issues after checking Apple TV, Photos, Maps etc. Continuity Camera works with iPhone 14pro, unlock with Apple Watch works. Airplay receiver does not work, iMac shows as a speaker on iPhone/iPad, but when selected, no sound or just reverts back to device speaker. My workaround for this has been Rogue Amoeba Airfoil, which works very well and has more features.
Hello dear friend @Marfan-58. I just updated to Sonoma 14.2 from the installer App which the installer package puts in the Applications folder by default.
So, in my iMac, perfectly identical to yours, Airplay works fine and of course AirDrop works too.
Likewise, when iMac appears as a speaker on iPhone and is selected, iMac plays audio.
As for the rest, everything works, including "Continuity Camera" with my iPhone 12.
So far I've found that only iMessage stickers don't work.
Maybe try resetting the NVRAM when the Mac starts but please, he keeps holding down the Option-P-R keys until he hears the Gong sound four times! At least I did it that way.
 
Today I updated to macOS Sonoma 14.2 using OCLP's latest release 1.3.0 official build.
In my iMac 27-inch 14,2 late 2013 (i7 CPU and nVidia GTX780M) everything works, Continuity Camera included and the System is so snappy and fast that I have to chase the mouse cursor, the text I write, ecc... So, the Mac gives me the impression that runs under my feet...

My installation's notes.
1) To install macOS 14.2 I downloaded the Apple Installer from the MrMacintosh site.
2) I downloaded and installed OCLP 1.3.0 latest release 1.3.0 official build.
3) Then, I restarted the Mac and at the chime I pressed the Option+P+R keys and held them until chime repeated FOUR TIMES. Why four times?... Because I read on Internet that a Mac user wrote that only after finding and executing this trick was he able to actually clean the Mac's NVRAM and completely fix some small problems he had with the Mac that wouldn't go away in any other way..
4)
Upon rebooting, I pressed and held the Option key, then enabled OCLP's EFIBoot
5) The Mac then booted up and after logging in I launched the Sonoma Installer and started the installation.
6) In the end, obviously, by installing directly from macOS and not from a USB stick, the Mac restarts in Safe Mode and runs very slowly. We then MUST install the Post Install Patch from the OCLP app, wait for the process to complete and when we are asked to reboot, reboot.
Easier to do than to describe all this.
Enjoy

EDIT
Unfortunately, this bug still persists: when your Mac wakes up from sleep, some icons in the right menu bar disappear.
The icons reappear by clicking in the empty spaces, with the exception of the Bluetooth icon (mystery...).
But in these cases I prefer to solve the problem by opening the Terminal, typing
Code:
killall Dock
and pressing Enter.
I hope the OCLP developers can find the right way to fix this annoying issue

iMac-14.2-Sonoma-14.2.jpg
 
Today I updated to macOS Sonoma 14.2 using OCLP's latest release 1.3.0 official build.
In my iMac 27-inch 14,2 late 2013 (i7 CPU and nVidia GTX780M) everything works, Continuity Camera included and the System is so snappy and fast that I have to chase the mouse cursor, the text I write, ecc... So, the Mac gives me the impression that runs under my feet...

My installation's notes.
1) To install macOS 14.2 I downloaded the Apple Installer from the MrMacintosh site.
2) I downloaded and installed OCLP 1.3.0 latest release 1.3.0 official build.
3) Then, I restarted the Mac and at the chime I pressed the Option+P+R keys and held them until chime repeated FOUR TIMES. Why four times?... Because I read on Internet that a Mac user wrote that only after finding and executing this trick was he able to actually clean the Mac's NVRAM and completely fix some small problems he had with the Mac that wouldn't go away in any other way..
4)
Upon rebooting, I pressed and held the Option key, then enabled OCLP's EFIBoot
5) The Mac then booted up and after logging in I launched the Sonoma Installer and started the installation.
6) In the end, obviously, by installing directly from macOS and not from a USB stick, the Mac restarts in Safe Mode and runs very slowly. We then MUST install the Post Install Patch from the OCLP app, wait for the process to complete and when we are asked to reboot, reboot.
Easier to do than to describe all this.
Enjoy

EDIT
Unfortunately, this bug still persists: when your Mac wakes up from sleep, some icons in the right menu bar disappear.
The icons reappear by clicking in the empty spaces, with the exception of the Bluetooth icon (mystery...).
But in these cases I prefer to solve the problem by opening the Terminal, typing
Code:
killall Dock
and pressing Enter.
I hope the OCLP developers can find the right way to fix this annoying issue

Just create a script in Automator until that’s fixed
 
  • Love
Reactions: OKonnel
Just create a script in Automator until that’s fixed
Your suggestion is excellent, @amaze1499! Thank you. Unfortunately I don't really know where to start...
In practice, the Script should start automatically whenever the Mac comes out of sleep. The Script would then start the Terminal, run the killall Dock command, and then close the Terminal and exit the Script.
Since I am not a developer and in 30 years of computer science I have created few Scripts, in situations like this I really don't know where to start.
If there was any friend capable of creating a Script that does what is listed above and posting it... we would all be very grateful.
 
I have problems with Transmission App with Beta di 14.3 (23D5033f) OCLP 1.3.0 on my MBP Retina, 13-inch, Mid 2014, it keeps crashing
I grabbed the latest build and while it doesn't crash upon launch, there are other issues (downloads not starting, app not quitting gracefully) https://build.transmissionbt.com/job/trunk-mac/lastBuild/

I'm going to retry applying the latest nightly OCLP.

Update: the stable Transmission 4.0.5 still crashes upon launch
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [1309]

VM Region Info: 0 is not in any region. Bytes before following region: 4475248640
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 10abee000-10adee000 [ 2048K] r-x/r-x SM=COW .../Transmission

Kernel Triage:
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 AppKit 0x7ff807d8af74 -[NSWrapperCellView drawRect:] + 126
1 AppKit 0x7ff80717ab24 _NSViewDrawRect + 121
2 AppKit 0x7ff807c2b8fd -[NSView _recursive:displayRectIgnoringOpacity:inContext:stopAtLayerBackedViews:] + 1848
3 AppKit 0x7ff807c2bc4b -[NSView _recursive:displayRectIgnoringOpacity:inContext:stopAtLayerBackedViews:] + 2694
4 AppKit 0x7ff80717a3da -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 747
5 AppKit 0x7ff80774c53a -[NSViewBackingLayer drawInContext:] + 64
6 AppKit 0x7ff807465f01 0x7ff806ff1000 + 4673281
7 AppKit 0x7ff80748643c 0x7ff806ff1000 + 4805692
8 AppKit 0x7ff80743abde 0x7ff806ff1000 + 4496350
9 AppKit 0x7ff807485f2c 0x7ff806ff1000 + 4804396
10 AppKit 0x7ff807483850 0x7ff806ff1000 + 4794448
11 AppKit 0x7ff807465e4f 0x7ff806ff1000 + 4673103
12 AppKit 0x7ff807465f4b 0x7ff806ff1000 + 4673355
13 AppKit 0x7ff80774c17a -[NSViewBackingLayer display] + 1763
14 QuartzCore 0x7ff80c491e8d CA::Layer::display_if_needed(CA::Transaction*) + 867
15 QuartzCore 0x7ff80c62aa24 CA::Context::commit_transaction(CA::Transaction*, double, double*) + 758
16 QuartzCore 0x7ff80c47302d CA::Transaction::commit() + 725
17 AppKit 0x7ff80718b40d __62+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayLink]_block_invoke + 285
18 AppKit 0x7ff807c72559 ___NSRunLoopObserverCreateWithHandler_block_invoke + 41
19 CoreFoundation 0x7ff803ac1ccc __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
20 CoreFoundation 0x7ff803ac1bf1 __CFRunLoopDoObservers + 493
21 CoreFoundation 0x7ff803ac1173 __CFRunLoopRun + 850
22 CoreFoundation 0x7ff803ac0859 CFRunLoopRunSpecific + 557
23 HIToolbox 0x7ff80e9939d9 RunCurrentEventLoopInMode + 292
24 HIToolbox 0x7ff80e993616 ReceiveNextEventCommon + 201
25 HIToolbox 0x7ff80e993531 _BlockUntilNextEventMatchingListInModeWithFilter + 66
26 AppKit 0x7ff80702fdb9 _DPSNextEvent + 880
27 AppKit 0x7ff807939a44 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1304
28 AppKit 0x7ff807021332 -[NSApplication run] + 603
29 AppKit 0x7ff806ff5341 NSApplicationMain + 816
30 Transmission 0x10abf24ca 0x10abee000 + 17610
31 dyld 0x7ff80365b386 start + 1942

However, the last build is now working after applying OCLP nightly, clearing caches via Onyx and reboot.
 
Last edited:
  • Like
Reactions: K two
Why?🤔 If you update (not upgrade) then this should work automatically
Hi @Ready-for-Apple! After having downloaded and installed a new version of OCLP, of any type, official or nightly, I always restart the Mac and at the sound of the gong, holding down the Option key, I waited for the EFIBoot icon to appear and by clicking on it I load the EFIBoot into NVRAM. Otherwise, as far as I know, the Mac will continue to use the OCLP version it's already using.
Having said that, even if you want to tell me that when OCLP updates it automatically overwrites the NVRAM (which I wasn't aware of until now and I don't know where it is written), however - if you review my post in point 3) I explained that I had deleted the NVRAM. For this reason, therefore, it is necessary and essential to carry out the procedure described in point 4) otherwise the Mac will not start.
I would like to point out that I added this point to help all those who have various problems and since they are beginners discover that deleting the NVRAM can only be useful after having written many posts looking for help. Cleaning the NVRAM, after all, never hurts and only wastes a few seconds on boot...
Am I wrong?... Thanks for any corrections
 
Your suggestion is excellent, @amaze1499! Thank you. Unfortunately I don't really know where to start...
In practice, the Script should start automatically whenever the Mac comes out of sleep. The Script would then start the Terminal, run the killall Dock command, and then close the Terminal and exit the Script.
Since I am not a developer and in 30 years of computer science I have created few Scripts, in situations like this I really don't know where to start.
If there was any friend capable of creating a Script that does what is listed above and posting it... we would all be very grateful.
I haven’t used recently, but isn’t there an action record button that turns everything into a script eventually?
 
  • Like
Reactions: OKonnel and K two
I grabbed the latest build and while it doesn't crash upon launch, there are other issues (downloads not starting, app not quitting gracefully) https://build.transmissionbt.com/job/trunk-mac/lastBuild/

I'm going to retry applying the latest nightly OCLP.



However, the last build is now working after applying OCLP nightly, clearing caches via Onyx and reboot.
FYI - The current OCLP nightly is the release version, essentially. Onyx/Maintenance solves lots of problems. :cool:
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.