macOS 14 Sonoma on Unsupported Macs Thread

[0134168]

I share this great article with you.

Controlling System Integrity Protection using csrutil: a reference

Why disable the whole of SIP when all you need is to disable some of its features? Here are all the options explained, and how to combine them.

eclecticlight.co

 

[dataharvested]

good tip. If you want to see where OpenCore gets the boot menu names, look in

• /System/Volumes/Preboot/<uuid>/System/Library/CoreServices/.contentDetails
• /System/Volumes/Preboot/<uuid>/System/Library/CoreServices/.disk_label.contentDetails

One or both of these files will exist. Manually editing the name in these files will also change the Open Core boot menu item name.

EDIT: <uuid> will be different for each macOS volume (e.g., if you have Sonoma and Ventura volumes, each will have a unique UUID).

EDIT2: For the interested reader: On a fully-supported Mac that is not patched by OCLP (with Open Core EFI that partially disables SIP), the .contentDetails and .disk_lable.contentDetails files are not normally this easy to edit. Editing them normally requires some extra steps to defeat protections.

How can I edit the .disk_label.contentDetails file? After I installed OpenCore Legacy Patcher 1.5.0 along with macOS Ventura and my SSD drive's name changed from "macOS" to "macOS - Data - Data". I want to get it back to the original name of just "macOS". Thanks!

 

[rehkram]

How can I edit the .disk_label.contentDetails file? After I installed OpenCore Legacy Patcher 1.5.0 along with macOS Ventura my SSD drive's name changed from "macOS" to "macOS - Data - Data". I want to get it back to the original name of just "macOS". Thanks!

Probably not connected with OCLP, there are several posts on this topic on Macrumors going back years. As a first step, use disk utility to rename the APFS volume. For reasons I can't remember you may not see your change in other apps until installing a macOS update later.

 

[dataharvested]

Probably not connected with OCLP, there are several posts on this topic on Macrumors going back years. As a first step, use disk utility to rename the APFS volume. For reasons I can't remember you may not see your change in other apps until installing a macOS update later.

I'm not blaming OCLP, just mentioning the events that took place to get it where it is now. I've already renamed the volume in Disk Utility and that does not change what is displayed upon boot.

 

[rehkram]

I'm not blaming OCLP, just mentioning the events that took place to get it where it is now. I've already renamed the volume in Disk Utility and that does not change what is displayed upon boot.

So you're basically off-topic. Do a search on MacRumors, something to the effect of "renaming disk volume". You will see that after renaming it in Disk Utility it won't change on the boot screen until you install a macOS update. Which is exactly what I just said in my previous post.

 

[dataharvested]

So you're basically off-topic. Do a search on MacRumors, something to the effect of "renaming disk volume". You will see that after renaming it in Disk Utility it won't change on the boot screen until you install a macOS update. Which is exactly what I just said in my previous post.

I was seeking guidance from the person I quoted. Next time I'll try to PM the person directly as it seems this a nuisance question that I'm asking in public. Sorry for intruding on this thread.

 

[surszki]

That file is in a formatted extFAT drive?

no, it shows this everywhere on the system disk.

 

[deeveedee]

How can I edit the .disk_label.contentDetails file? After I installed OpenCore Legacy Patcher 1.5.0 along with macOS Ventura and my SSD drive's name changed from "macOS" to "macOS - Data - Data". I want to get it back to the original name of just "macOS". Thanks!

I have found that on some systems, it may just be easiest to completely disable SIP, then return SIP to OCLP default after editing the file. With SIP fully disabled, run your editor with SU priviledges (e.g., sudo vi .disk_label.contentDetails).

 

[dataharvested]

I have found that on some systems, it may just be easiest to completely disable SIP, then return SIP to OCLP default after editing the file. With SIP fully disabled, run your editor with SU priviledges (e.g., sudo vi .disk_label.contentDetails).

Thank you!

 

[deeveedee]

Sweet, Also I have to ask.

Can I have Monterey & Sonoma on the same NVMe drive by utilizing a separate container?

Yes

 

[Bmld]

Sweet, Also I have to ask.

Can I have Monterey & Sonoma on the same NVMe drive by utilizing a separate container?

Yes it is possible, read this old post and the other. (select my old post )

Hello, I had promise to explain how I installe a new MacOs : I create a new volume (in the same container) with disk utility. It is possible to have more than one system on you Mac. Not problem with OCPL. When I install MacOs I select all drive to select the second drive. So I have always 2 MacOs on my Mac. On booting, a screen display 2 icons to choose your MacOs. (if not, use the option key). If everything is correct, select the new drive with the control panel stratup disk. You don't have to reinstall software. All my software are on another disk (or partition). I use lot of technical software, 3D et development, so if a software don't works with this new config, I switch on the old one. For the document, I use googleDrive/dropbox so everything is reinstalled.The install is always a clean install. Just one problème, to do this you need a 256gb ssd minimum. Don't forget the OCPL post install on each MacOs.

Attachments​

• 

 

[Bmld]

Hello,

If you want a simple solution to schedule your Mac, I write software with a GUI like the old MACOS.
My site to download: http://bmaillard.free.fr//programmer/ (the source is online)
I test it on Ventura and Sonoma.

Enjoy

 

[mib01]

Does installing Sonoma on the MacBook Pro 2017 need to be over Ventura to keep the correct T1 chip working? And from what I've been noticing the only pending driver in Sonoma is Wireless, because the GPU continues to work natively.

Does the Radeon Pro 555 also work natively without the need for OCLP (post install)? I'm still using Ventura because it's receiving security updates.

 

[natus.w]

Does installing Sonoma on the MacBook Pro 2017 need to be over Ventura to keep the correct T1 chip working? And from what I've been noticing the only pending driver in Sonoma is Wireless, because the GPU continues to work natively.

The native OS maintains the T1 firmware in EFI so you should ideally keep that (or install over it) if you want to keep functionality (if Ventura is going to be moved to LTS support I'd keep it as that's the only way you'll get any firmware updates..

see: https://dortania.github.io/OpenCore-Legacy-Patcher/SONOMA-DROP.html#issues

Does the Radeon Pro 555 also work natively without the need for OCLP (post install)? I'm still using Ventura because it's receiving security updates.

It should work fine, I do not see anything about support being dropped or missing instructions..

 

[OKonnel]

Well I left a comment about it on the electric light website hoping someone would reach out to me from there. I left my email and name I told them I couldn't find a contact link to contact them directly.

Hi @MacinMan . Since the excellent site you cite is a blog and not a forum, it is difficult for another reader to answer a question. Howard, however, always responds unless he misses your comment.
There is, however, the possibility of contacting Howard directly and if you do a search at the bottom of each page of the blog you will find his e-mail address and an invitation to write to him.
To be fair, I will not post it here, but you can go to the link -> About this blog and at the bottom you will find the address you are looking for, but written in such a way that it can only be found by human beings and not by automatic search mechanisms.
Keep in mind that Howard is on his own and does a lot for all of us, free of charge to boot; so let's turn to him only in extreme and important cases where we can't find a solution, which is almost always present in his blog if we read his articles carefully and/or scroll through the comments and/or insert our comment in the right place and at the right time. You will often notice my Avatar and as you see Howard always responds to me.
I hope I have been of some help

 

[OKonnel]

Sweet, Also I have to ask.

Can I have Monterey & Sonoma on the same NVMe drive by utilizing a separate container?

Ho @basslik. You can install and use multiple versions of macOS on your internal disk or external devices.
However, as Apple continually updates APFS, read this article —> https://eclecticlight.co/2024/08/22/dual-booting-your-mac-with-multiple-versions-of-apfs/ and the comments carefully to understand what not to do.
For example, perhaps get distracted by using Catalina's Disk Utility functions (or Terminal commands) with volumes where later operating systems are installed and this can cause unexpected problems and data loss.
I don't know if you only damage one volume or if there is a risk of damaging the entire disk and then being forced to format it.

 

[MacinMan]

Hi @MacinMan . Since the excellent site you cite is a blog and not a forum, it is difficult for another reader to answer a question. Howard, however, always responds unless he misses your comment.
There is, however, the possibility of contacting Howard directly and if you do a search at the bottom of each page of the blog you will find his e-mail address and an invitation to write to him.
To be fair, I will not post it here, but you can go to the link -> About this blog and at the bottom you will find the address you are looking for, but written in such a way that it can only be found by human beings and not by automatic search mechanisms.
Keep in mind that Howard is on his own and does a lot for all of us, free of charge to boot; so let's turn to him only in extreme and important cases where we can't find a solution, which is almost always present in his blog if we read his articles carefully and/or scroll through the comments and/or insert our comment in the right place and at the right time. You will often notice my Avatar and as you see Howard always responds to me.
I hope I have been of some help

Thanks for your response. Yes, I found the info I needed, and communicated with Howard after he responded to my comment. He was aware of the issue I was having, and Apple fixed it. So everything is good now

 

[jacou]

Please Help!

I‘m having a problem since updated my late 2013 iMac (14.1) to 14.6.1 with OCLP 1.5.

My iMac worked fine for about 1,5 days then the screen froze and since then I’m stuck on the boot screen with the bar loaded 1/3 and the fans running fast.

I then uninstalled the post install patch in safe mode and my iMac started again. But whenever I install the post patch again it gets stuck on the boot screen. Also tried OCLP 1.6n without luck.

Any help is highly appreciated!

 

[houser]

Please Help!

I‘m having a problem since updated my late 2013 iMac (14.1) to 14.6.1 with OCLP 1.5.

My iMac worked fine for about 1,5 days then the screen froze and since then I’m stuck on the boot screen with the bar loaded 1/3 and the fans running fast.

I then uninstalled the post install patch in safe mode and my iMac started again. But whenever I install the post patch again it gets stuck on the boot screen. Also tried OCLP 1.6n without luck.

Any help is highly appreciated!

Have you tried installing the patch from safe boot?
If that does not work, reset the NVRAM if you have not tried that.
Preferably from the icon in the OCLP boot screen if you can get to it.
Press spacebar after selecting your EFI and then scroll to the far left for the icon.

 

[jacou]

Have you tried installing the patch from safe boot?
If that does not work, reset the NVRAM if you have not tried that.
Preferably from the icon in the OCLP boot screen if you can get to it.
Press spacebar after selecting your EFI and then scroll to the far left for the icon.

Thanks for your help! Yes I tried installing the post install root patch from the safe mode.
I also tried resetting the NVRAM now but it doesn’t work either.
Still stuck at 1/3 boot with loud fans.

 

[rehkram]

Thanks for your help! Yes I tried installing the post install root patch from the safe mode.
I also tried resetting the NVRAM now but it doesn’t work either.
Still stuck at 1/3 boot with loud fans.

Hmmm, strange. If I were you I'd power-off and let the m/c cool all the way down to room temperature. Then boot. I suggest this based on my experience with a different m/c, when the fans were ramping-up so early in the boot sequence. It might give you the additional thermal headroom you need.

 

[houser]

Still stuck at 1/3 boot with loud fans.

I guess you might have some files in the install directories that may need deleting.
Something that will also not hurt is to try a reinstall of 14.6.1 from a USB stick and see if OCLP asks to download some kexts that may be missing. Create the USB installer from OCLP.

 

[0134168]

Thanks for your help! Yes I tried installing the post install root patch from the safe mode.
I also tried resetting the NVRAM now but it doesn’t work either.
Still stuck at 1/3 boot with loud fans.

How did you reset the NVRAM?

 

[jacou]

Hmmm, strange. If I were you I'd power-off and let the m/c cool all the way down to room temperature. Then boot. I suggest this based on my experience with a different m/c, when the fans were ramping-up so early in the boot sequence. It might give you the additional thermal headroom you need.

I waited a few hours but still doesn’t start. It doesn’t only seem to be a thermal issue unfortunately.

 

[jacou]

I guess you might have some files in the install directories that may need deleting.
Something that will also not hurt is to try a reinstall of 14.6.1 from a USB stick and see if OCLP asks to download some kexts that may be missing. Create the USB installer from OCLP.

Thanks for the tip. I’ll try that now.