Sidebar Sidebar
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

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.
5T33Z0 said:
iMac11,3. 27"
OCLP: 1.2.1
OC Debug Commit: 9215e5c

View attachment 2311574
Click to expand...
We are getting ahead of ourselves. There is no macOS beta, no OCLP nighty, no manually updated/maintained OCLP generated OC support. But thanks for pointing this out. You might go the usual route and report this in the OC repo.

Edit:
The driver seems to break other configs OLCP 1.2.1 based configs with the published OC 0.9.6....only a water mark message.
 
Last edited:
  • Like
Reactions: macpro_mid2014, ChrisOSX, K two and 1 other person
roronl said:
Highly recommended, with thanks to Mr. Macintosh.

Click to expand...
Thanks for the video. Maybe you could answer this….for example. I am on 14.1 and on OCLP 1.2.0.

Before I update to 14.2 (or whatever) and 1.2.1 (or whatever is out at the time) what would be the best way set everything to the way it was before updating?

Would I create a 14.1 USB installer and 14.1 Time Machine then wipe and reinstall everything? Would the Time Machine install over top of OCLP and everything reset as before? It’s not clear if Time Machine installs correctly on an unsupported Mac with different versions of OCLP and operating systems.

The reason I ask, is the last few updates got more confusing and complicated and I want to be prepared if I jump up to another update and it fails miserably. I use this for work and am at the point I might simply wait a while until this stabilizes and there’s a solid fix.
 
  • Like
Reactions: INK1
mikelets456 said:
Thanks for the video. Maybe you could answer this….for example. I am on 14.1 and on OCLP 1.2.0.

Before I update to 14.2 (or whatever) and 1.2.1 (or whatever is out at the time) what would be the best way set everything to the way it was before updating?

Would I create a 14.1 USB installer and 14.1 Time Machine then wipe and reinstall everything? Would the Time Machine install over top of OCLP and everything reset as before? It’s not clear if Time Machine installs correctly on an unsupported Mac with different versions of OCLP and operating systems.

The reason I ask, is the last few updates got more confusing and complicated and I want to be prepared if I jump up to another update and it fails miserably. I use this for work and am at the point I might simply wait a while until this stabilizes and there’s a solid fix.
Click to expand...
A backup is always a must. Then it is presently still recommended to connect your machine for the update process with an ethernet cable to the internet. Make sure you have the latest OCLP 1.2.1 installed. Usually the program will notify you that a new version is available. Then download Sonoma 14.1.1. here https://mrmacintosh.com/macos-sonoma-full-installer-database-download-directly-from-apple/ (I prefer this update method as it causes less issues than the internal update feature). Depending on what machine you have, the update will proceed flawlessly. If you want to be on the safe side you can do the updates with an USB installer that you can create with OCLP first....alternatively you can also create a test OS on a new separate partition and always test all updates on your machine there first...
 
  • Like
Reactions: mikelets456 and roronl
I added an APFS volume for Sonoma (Release), so that my MBP6,2 has one volume for the Sonoma Beta track and one for the Sonoma Release track. Sonoma 14.0 (Release) install and the upgrade to 14.1.1 (Release) was flawless with OCLP 1.2.1. Both 14.1.1 (Release) and 14.2 (Beta) run well and my MBP6,2 is able to boot Recovery Mode for both versions of macOS. I continue to perform my macOS installations and upgrades while maintaining a wired Ethernet connection, but I suspect that Devs have eliminated the need for the wired Ethernet connection by downloading resources before Wi-Fi is lost.
 
  • Like
Reactions: mikelets456 and luckyduke23
mikelets456 said:
Thanks for the video. Maybe you could answer this….for example. I am on 14.1 and on OCLP 1.2.0.

Before I update to 14.2 (or whatever) and 1.2.1 (or whatever is out at the time) what would be the best way set everything to the way it was before updating?

Would I create a 14.1 USB installer and 14.1 Time Machine then wipe and reinstall everything? Would the Time Machine install over top of OCLP and everything reset as before? It’s not clear if Time Machine installs correctly on an unsupported Mac with different versions of OCLP and operating systems.

The reason I ask, is the last few updates got more confusing and complicated and I want to be prepared if I jump up to another update and it fails miserably. I use this for work and am at the point I might simply wait a while until this stabilizes and there’s a solid fix.
Click to expand...
Never used Time Machine, but a Carbon Copy Cloner backup (standard backup, non-bootable) will work fine with an unsupported Mac running OCLP. Install the new version (copy the app directly to the /Library/Application Support/Dortania folder), do the backup, and Reboot to the new USB installer, wipe the SSD and install the OS. During the install process you should be prompted to transfer your data via the Migration Assistant. After everything settles down, run the OCLP app using the Build and Install Open Core option to install the OCLP EFI to your internal SSD. All of you settings, folder, etc., ie., everything, should be the same as it was before the upgrade.
 
Last edited:
  • Like
Reactions: olad and mikelets456
deeveedee said:
.... I continue to perform my macOS installations and upgrades while maintaining a wired Ethernet connection, but I suspect that Devs have eliminated the need for the wired Ethernet connection by downloading resources before Wi-Fi is lost.
Click to expand...
That's correct. I also read it but I had no issues at all so far anyway. But if users still run into problems anyway, it's always the first solution to connect via ethernet. It often happens that OCLP was corruped for an unknown reason...
 
  • Like
Reactions: mikelets456, roronl and deeveedee
wwise said:
So I was checking my mac mini 8,1 and brought up OCLP but it won't allow - the Build and Install OpenCore is greyed out - is that expected?
Click to expand...
MM8,1 is still supported by Apple, so I wouldn't think that OCLP would recognize it as an unsupported Mac. If you are using your MM8,1 to "Build and Install Open Core" for another unsupported Mac, you need to manually change the Target Model in OCLP > Settings.
Screenshot 2023-11-13 at 10.55.04 AM.png


EDIT: Whoops - sorry for the duplicate of davidlv's post here.

EDIT2: It's worth noting that OCLP generates an Open Core EFI that is unique for each macOS model (SMBIOS model). This, combined with the fact that OCLP customizes post-install patches for each Mac is why one user's experience with OCLP cannot be assumed for another user. Each user needs to test OCLP with their own Mac and their own use cases to determine whether OCLP is suitable for one's needs and applications.
 
Last edited:
  • Like
Reactions: olad, davidlv and K two
mikelets456 said:
Thanks for the video. Maybe you could answer this….for example. I am on 14.1 and on OCLP 1.2.0.

Before I update to 14.2 (or whatever) and 1.2.1 (or whatever is out at the time) what would be the best way set everything to the way it was before updating?

Would I create a 14.1 USB installer and 14.1 Time Machine then wipe and reinstall everything? Would the Time Machine install over top of OCLP and everything reset as before? It’s not clear if Time Machine installs correctly on an unsupported Mac with different versions of OCLP and operating systems.

The reason I ask, is the last few updates got more confusing and complicated and I want to be prepared if I jump up to another update and it fails miserably. I use this for work and am at the point I might simply wait a while until this stabilizes and there’s a solid fix.
Click to expand...
@mikelets456 "wipe and reinstall everything" Is not a requirement for upgrading via OCLP.

If you 1) install the latest version of the OCLP app
2) install this tool on your disk via the app.
3) Upgrade Macos via OTA or Ethernet
4) apply the patches via the OLPC tool for these new Macos
5) reboot. If all goes well, everything should be fine as it was before you upgraded.

This means you have installed the new MacOS version over your old version and you do not need a recovery via Time Machine or another backup.
 
  • Like
Reactions: K two
Noticed macOS 14.2b(23C5041e) boot-loops (WindowServer and MTLCompilerService crashes) on Metal Macs and not so on non-Metal Macs with OCLP v.1.2.1. Suspect LaunchServices may be the source of this issue? Hopefully this observation doesn't get me booted from Discord, yet again. ;)
 
  • Like
Reactions: cab_007 and Calibre5
K two said:
Noticed macOS 14.2b(23C5041e) boot-loops (WindowServer and MTLCompilerService crashes) on Metal Macs and not so on non-Metal Macs with OCLP v.1.2.1. Suspect LaunchServices may be the source of this issue? Hopefully this observation doesn't get me booted from Discord, yet again. ;)
Click to expand...
Another data point; no such boot-loop issues on either my native supported MBA or the very old (2014) iMac 15,1. Both metal capable.
 
  • Like
Reactions: K two
davidlv said:
Another data point; no such boot-loop issues on either my native supported MBA or the very old (2014) iMac 15,1. Both metal capable.
Click to expand...
Concur on the supported Mac, Mini8,1 is OK here but on Haswell Mac Mini7,1 it crashes every time. Observed on this thread non-Metals seem immune. 🤷‍♂️
 
  • Like
Reactions: cab_007
I took nightly OCLP this am and while unpatched 14.1b2 booted up ok, upon patching with OCLP (post root install), I got the boot loop with what is reported above. Now trying to revert back.
 
  • Like
Reactions: olad, K two and houser
I've upgraded my macmini3,1 (early 2009) but the drivers for bluetooth and wifi aren't working. I'm also seeing crashreporter running over and over again. I looked through the options in OCLP but there doesn't seem to be any option to change anything regarding BT/Wifi. Can anyone point me to some other information on how to resolve this?

Thanks!

*** Edit ***

Correction, it's just bluetooth. Wifi is just super slow to turn on - symptomatic of the computer constantly writing its crashreports...
 
Last edited:
K two said:
Concur on the supported Mac, Mini8,1 is OK here but on Haswell Mac Mini7,1 it crashes every time. Observed on this thread non-Metals seem immune. 🤷‍♂️
Click to expand...
Can you clarify regarding your comment on the "non-Metals seem immune"? Also regarding the "Haswell" involvement?
If I am not mistaken, my iMac 15,1 has a Haswell chip, and it didn't have the boot-loop issue.
 
  • Like
  • Wow
Reactions: K two and sinbad21
davidlv said:
Can you clarify regarding your comment on the "non-Metals seem immune"? Also regarding the "Haswell" involvement?
If I am not mistaken, my iMac 15,1 has a Haswell chip, and it didn't have the boot-loop issue.
Click to expand...
Noticed that more non-Metal Macs were not having issues with the lastest updates both MacOS and OCLP, yet more than a few with Metal Macs trying the second Beta of 14.2 (23C5041e) were seeing the same issues whether OTA or USB installed. Actually, to me it appears there is a problem with Metal patches (I can only test Haswell) and Launch Services since the MTLCompilerService (too many corpses) and the WindowServer are directly involved. Also, a clean install with an OCLP-made USB, ethernet-connected over a FiberOptic network yielded the same issue. Is AMD Radeon R9 a Haswell?? 🤔 Hmm?
 
K two said:
Noticed that more non-Metal Macs were not having issues with the lastest updates both MacOS and OCLP, yet more than a few with Metal Macs trying the second Beta of 14.2 (23C5041e) were seeing the same issues whether OTA or USB installed. Actually, to me it appears there is a problem with Metal patches (I can only test Haswell) and Launch Services since the MTLCompilerService (too many corpses) and the WindowServer are directly involved. Also, a clean install with an OCLP-made USB, ethernet-connected over a FiberOptic network yielded the same issue. Is AMD Radeon R9 a Haswell?? 🤔 Hmm?
Click to expand...
Apparently yes. See the screenshot attached, from MacTracker, my iMac is the i5 model.
 

Attachments

  • Screenshot.jpg
    Screenshot.jpg
    145.6 KB · Views: 113
  • Like
  • Wow
Reactions: K two and houser
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back