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.

MacinMan

macrumors 65816
Jan 27, 2011
1,379
787
Denham Springs, LA
I don’t have Monterey in front of me but I would bet not much has changed:
Overall, Monterey to Sonoma isn't a huge jump. I could have stayed with Monterey and been fine. However, I wanted to update my apple apps to the latest so that needed Ventura, or Sonoma, and decided to do Sonoma so I wouldn't get asked to upgrade to it later from Ventura. FYI, Monterey is a native install for this iMac 17,1, it's the last officially supported version.
 

comptalk

macrumors member
Dec 22, 2010
48
4
I don’t have Monterey in front of me but I would bet not much has changed:

I was able to install Sonoma through the software update route from Monterey. I would like to import the mailboxes and accounts from the Time machine backup. What's the best way to do this?
 

imrazor

macrumors 6502
Sep 8, 2010
401
120
Dol Amroth
I have successfully installed Sonoma on a 2017 5k iMac. However, I do have a couple of odd problems that *may* be related to OCLP or its boot picker/loader. When I have an ExFAT formatted USB SSD (Crucial X9 Pro) attached to the iMac at boot, the system will not boot or let me choose an OS. I just see the Apple logo, and the drive LED blinking like it's being scanned or read from. The system never boots until I detach the SSD, power off, and reboot without the external drive plugged in.

The other issue I'm running into is frequent game crashes. That said, I'm trying to use a 128GB APFS SSD as a boot drive (severed from a Fusion Drive) with the game files on the ExFAT SSD.

I'm not sure if my issues are related to OCLP or an incompatible SSD. There was a firmware update, but applying it to the SSD didn't resolve the problem. I'm not sure if I should throw in the towel and just format the SSD as HFS or APFS (or maybe split it 50/50 between APFS and NTFS), or install Ventura to see if it has issues.
 

Furka

macrumors regular
Dec 12, 2019
106
50
My MBP-13 on 14.3 OCLP from 2012 is waking up from sleep on the night (I do not know how many times) :-/ It looses 7% of battery in 8-9 hours :-/
 

cmedina90

macrumors newbie
Apr 13, 2023
7
7
I have exactly the same model. I install the post patches in safe mode and have not noticed any problems so far.

The only thing that doesn't work is the privacy and security settings, I don't get a request from the respective app.

Sorry but How can I install post patches in safe mode? Can you give me any instructions or link?

Thanks.
 

rehkram

macrumors 6502a
May 7, 2018
855
1,192
upstate NY
Sorry but How can I install post patches in safe mode? Can you give me any instructions or link?

Thanks.
Power off. Power back on with the shift key pressed. Keep holding the shift key down until the login screen appears. Log in and run the OCLP GUI, click the button labeled 'Post-Install Root Patch'. And please read the OCLP documentation.
 

MacinMan

macrumors 65816
Jan 27, 2011
1,379
787
Denham Springs, LA

deeveedee

macrumors 65816
May 2, 2019
1,449
2,111
Peoria, IL United States
I would upgrade to the new M3 Pro MPB and run the ARM version of W11+VS on a VM, unless you don't want to upgrade your hardware!
I may need to look into your suggestion. The migration of my development projects from VS 2022 Mac to VS 2022 Windows was very easy.

EDIT: @macpro_mid2014 I looked into the W11 VM on Arm and see that, while W11 may run, the apps would also need to be written for Arm. If there is a solid Intel emulation in the VM, it is likely that the apps would be relatively slow.
 
Last edited:
  • Like
Reactions: macpro_mid2014

K two

macrumors 68020
Dec 6, 2018
2,313
3,184
North America
Installed macOS 14.4b1 OTA onto a supported Mini8,1, runs as expected. :cool:
b1.jpg
 
Last edited:

RogueB

macrumors 6502
Sep 9, 2016
272
471
Hello to all,

I had no lasting major issues installing or running 14.3.x betas, and 14.3 final, on MacBook Pro 5,2 (2009) and iMac 13,2 (2012). On few occasions a full installer was needed to install some of the betas, but mostly upgrades were accomplished via OTA (and nightly OCLPs). There were issues with blue tooth connectivity and, predictably, MacBook Pro 5,2 (non-metal) could not run certain "Metal-dependent" applications.

However, beta1 14.4 is another matter. Much as already reported by other posters, Sonoma 14.4 beta1 does not fully install over 14.3 final, and results in "prohibitory" sign when attempt is made to upgrade via either OTA or full installer mode. That is true for both iMac 13,2 and MacBook Pro 5,2.

Interestingly enough MacBook Pro 5,2 appeared to complete the installation OTA, using OCLP from 1.30.24, and actually booted into the log-in window. In previous reiterations of Sonoma, when stuck at login, attaching wired keyboard and mouse to a modern USB hub, then plugging the hub itself to USB port of the MacBook Pro (credit hvds) did allow connection, and hence, ability to type-in password, and proceed to fully functional desktop. Experimentally, I pressed space-bar while booted from USB thumb drive, and Sonoma 14.4 beta1 recovery volume became available; selecting it allowed boot to proceeded without prohibitory sign, but did stall with flashing icons for mouse and keyboard on the screen. Plugging external mouse and keyboard via USB hub, as described above, did not change the outcome. Neither wired keyboard nor mouse were recognized. This is in contrast to Sonoma 14.3 series, where external mouse and keyboard solved the problem. A USB bluetooth dongle plugged into MacBook Pro's USB ports showed that none were energized (its blue led was not activated).

There is enough of a trend to suspect possible problem with USB ports; this was already mentioned by K two, and referenced to possible related issues in threads discussing supported Macs.

iMac 13,2 fared no better; choosing 14.4 beta1 recovery volume allowed installation to proceed, but process stalled on second reboot, with progress bar barely initiated; there was a kernel panic message on subsequent reboot.

Great work by developers, who have an "eternally" moving target with updates.
Hope this post may be of help.
 

Sven G

macrumors 6502
Jun 3, 2012
428
879
Milan, EU
I wanted to do that on my Mac Pro 5,1. Unfortunately, safe mode doesn't work for me under OCLP. If I press Shift + Enter when I select my Sonoma SSD in the OpenCore boot picker, the boot process gets stuck. I've even tried it after an NVRAM reset; it will still freeze up. Do you have any suggestions as to how to proceed? I haven't tried an SMC reset. Would that do the trick?
You can always try: maybe a SMC reset, followed by a NVRAM reset…? (On my MBP11,3, safe mode with OCLP began to work again on Sonoma some time ago: maybe it doesn’t yet work on all Macs.)
 
Last edited:

Sven G

macrumors 6502
Jun 3, 2012
428
879
Milan, EU
Last edited:

Bmld

macrumors member
Dec 25, 2022
65
37
I was able to install Sonoma through the software update route from Monterey. I would like to import the mailboxes and accounts from the Time machine backup. What's the best way to do this?
Hello, use Iclood account to importe mailboxes and other param.
 

Calibre5

macrumors member
Sep 1, 2020
57
124
However, beta1 14.4 is another matter. Much as already reported by other posters, Sonoma 14.4 beta1 does not fully install over 14.3 final, and results in "prohibitory" sign when attempt is made to upgrade via either OTA or full installer mode. That is true for both iMac 13,2 and MacBook Pro 5,2.

iMac 13,2 fared no better; choosing 14.4 beta1 recovery volume allowed installation to proceed, but process stalled on second reboot, with progress bar barely initiated; there was a kernel panic message on subsequent reboot.

I had a different experience with my iMac 13,2. It updated itself overnight from 14.3 final to 14.4 beta 1 seemingly successfully. As the OCLP patches were installed on 14.3 it must have been the full 13.xx GB OTA update.
The next morning I realised I'd lost wifi and graphics acceleration and when I checked saw it was running on 14.4 beta. Strange, as I was sure I'd switched off auto updates!

Tried installing the OCLP 1.4.0 Nightly patches and that's when it subsequently failed to reboot.

Gone back to 14.3 from a backup for now.
 
Last edited:
  • Like
Reactions: K two

mikelets456

macrumors 6502a
Feb 15, 2022
733
640
Bucks County, PA
Running 6 weeks or so on 14.2.1 OCLP 1.3.0 with minimal problems. Today, my computer froze up twice and I had to hold the power button to reboot. Not sure what's going on....the only App added was "Tax cut" 3 days ago.

Should I reapply root patches? Go to 14.3?
 

K two

macrumors 68020
Dec 6, 2018
2,313
3,184
North America
After sometime running macOS 14.4b1 on a supported Mini, I noticed a big increase in demand of CPU time and memory compared to macOS 14.3 suggesting Macs with 4GB of RAM, even 8GB will notice a substantial decrease in performance once the OCLP devs sort-out the post-install patch issues brought about by macOS 14.4. FWIW 🤔
 
  • Like
Reactions: rehkram

MacinMan

macrumors 65816
Jan 27, 2011
1,379
787
Denham Springs, LA
After sometime running macOS 14.4b1 on a supported Mini, I noticed a big increase in demand of CPU time and memory compared to macOS 14.3 suggesting Macs with 4GB of RAM, even 8GB will notice a substantial decrease in performance once the OCLP devs sort-out the post-install patch issues brought about by macOS 14.4. FWIW 🤔
What's the minimum amount of ram supported Macs come with these days? is it 8 GB now?
 
  • Like
Reactions: K two
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.