macOS 14 Sonoma on Unsupported Macs Thread

[mpbb]

I think the issue may be with the root patch installing the legacy kexts for the WiFi card that should have been in my iMac, I have a BCM94322MC card in the iMac, could that be the issue? could it just be a case of reinstalling the correct kexts?

I've had also this bluetooth issue in the past and posted my unorthodox solution on post #4,762. I was able to reproduce it when installing Ventura and Sonoma from scratch. I would guess using the Ben Backer's Hackintool.app should also work though I couldn't replicate the case as I had none of the culprit entries mentionned after BT started working (what seems consistent). If you read my post, my advice is to just be patient and after a few time/reboots bluetooth starts working out of the blue. Really seems like a huge timeout issue before the system clears the entries or something like. BTW the issue doesn't seem to reappear when I do OTA updates...

 

[Marfan-58]

Just updated my Mac Mini 7,1 to Sonoma 14.4. Most things seem to be working fine, but Ive noticed no option for Continuity Camera in the FaceTime app. I’ve never tried this feature before on this machine. Is this a known issue?

 

[amaze1499]

Just now updated to OCLP v.1.5.0n, over mac OS 14.4, runs as expected.

Hail the brave beta tester! A true pioneer. I'll walk a few releases behind you.

 

[TommesPommes]

Several ways. Do you have another Mac? If so, "Build and Install Open Core" to a USB thumb drive and boot from USB. Be sure to properly set the target host in OCLP when building Open Core for an external Mac.

EDIT: Once you recover, it's always a good idea to test any Open Core EFI changes with USB before installing them to your primary boot disk. It's also a good idea to keep a USB thumb drive with a known-working EFI for recovery.

Thanks, I used the EFI of a thumb drive with the modified Host to boot into os. From there I repatched the efi on the ssd, thank you

 

[MacinMan]

So, i was actually a bit confused about the whole SIP and OCLP situation. Even reading the guide on the site. So when dealingwith OCLP and SIP is it actually backwards as in checking items disables and unchecking enables? vs checking enable unchecking disable ?

 

[trifero]

Hardware incompatible
W11 not playable ethernet or wifi (need drivers bootcamp)
Install Legacy Mode (MBR/GPT)

I understand. I updated from Windows 10, but it was a legacy installation.

 

[trifero]

@TommesPommes Just boot from an USB with OpenCore EFI installed, if you have still the istallation USB. Reinstall OCLP to the HD.

 

[trifero]

So, i was actually a bit confused about the whole SIP and OCLP situation. Even reading the guide on the site. So when dealingwith OCLP and SIP is it actually backwards as in checking items disables and unchecking enables? vs checking enable unchecking disable ?

Checked is disabled. Its clear, all the options begins with "ALLOW...".

 

[MacinMan]

Checked is disabled. Its clear, all the options begins with "ALLOW...".

Well, remember I'm not used to dealing with the OCLP way of doing things. If I wanted to disable SIP i always booted into recovery and ran the csrutil. When I read the guide on dortania's site it assumed checking the boxes was to allow. I didn't realize until after reading the above post that checking the boxes in OCLP actually disabled things. I had planned on asking about SIP anyway at some point because I was curious if it was possible to completely kill SIP and just use macOS with regular UNIX permissions along apart from anything Apple specific or at least more like it was from Tiger through Yosemite, when talking (intel support.)
Also keep in mind with my question / post here, I never fully understood SIP with a supported version of macOS either. So I mainly just left it on by default, so I only asked because of the above post of trying to disable it ended up enabling it and a non bootable system.

 

[K two]

Hail the brave beta tester! A true pioneer. I'll walk a few releases behind you.

OCLP v.1.5.0n is the v.1.4.2 release with only a OpenCore to v.0.9.9 update. 🧐

 

[deeveedee]

If I wanted to disable SIP i always booted into recovery and ran the csrutil.

Since you're used to csrutil, open OCLP > Settings > Security and uncheck all the SIP "ALLOW" boxes. Currently configured SIP goes to 0:

EDIT: You already know this, but I'll state for completeness... Any SIP changes in OCLP don't become effective until you "Build and Install Open Core" and reboot with the modified Open Core EFI. And experiment with EFI changes on a USB Thumbdrive - not your primary boot drive.

 

[MacinMan]

Since you're used to csrutil, open OCLP > Settings > Security and uncheck all the SIP "ALLOW" boxes. Currently configured SIP goes to 0:
View attachment 2358428

Thanks, will do that once I install macOS with OCLP again. Currently using Monterey (natively supported) Have really just been quietly watching this thread with the updates taking place to see how things are working. I only spoke up because a topic I was interested in came up. Thanks again @deeveedee

 

[trifero]

Thanks, will do that once I install macOS with OCLP again. Currently using Monterey (natively supported) Have really just been quietly watching this thread with the updates taking place to see how things are working. I only spoke up because a topic I was interested in came up. Thanks again @deeveedee

And have in mind csrutil is of no use in OCLP. When you boot, the settings in OCLP at boot prevalence. For your information, all my OCLP macs boot at 0xfef. But be cautious, this reduce security considerably.

 

[MacinMan]

And have in mind csrutil is of no use in OCLP. When you boot, the settings in OCLP at boot prevalence.

That's what I was thinking, that csrutil no longer applied to OCLP as no one running it ever mentions using it to disable SIP anymore. Plus I figured if it still worked there would have been no reason to add the settings to OCLP as people could have just turned it off with csrutil. Thanks again guys for the info, and clarification.

 

[deeveedee]

all my OCLP macs boot at 0xfef.

Good thing you're not enabling ALLOW_APPLE_INTERNAL

 

[chevyboy60013]

So i am assuming it is still not possible to upgrade to 14.4 from 14.3.1 on my mid 2010 MacBook pro 7,1 model? not that there is any reason to need to do so.

 

[jon8214]

I've had also this bluetooth issue in the past and posted my unorthodox solution on post #4,762. I was able to reproduce it when installing Ventura and Sonoma from scratch. I would guess using the Ben Backer's Hackintool.app should also work though I couldn't replicate the case as I had none of the culprit entries mentionned after BT started working (what seems consistent). If you read my post, my advice is to just be patient and after a few time/reboots bluetooth starts working out of the blue. Really seems like a huge timeout issue before the system clears the entries or something like. BTW the issue doesn't seem to reappear when I do OTA updates...

thanks mate ill let you know how i get on

 

[webg3]

So i am assuming it is still not possible to upgrade to 14.4 from 14.3.1 on my mid 2010 MacBook pro 7,1 model? not that there is any reason to need to do so.

That's right, it's not possible, it's in the Github OCLP documentation, MacBook Pro 2008 to 2011 (this includes 2009 and 2010).

 

[pepepro]

How do you install Windows 11?

hi trifero!

my first attempt was as described here:

https://dortania.github.io/OpenCore-Legacy-Patcher/WINDOWS.html#installation-process

... and there i first tried the standard "microsoft method" with windows 11 - the only thing i changed was the creation of the usb stick - i did it on another windows machine with the help of rufus, to overcome windows 11's hardware restrictions right from the beginning. then i got that annoying bluescreen - i assume it was quite short of the end of the whole installation process and after some necessary restarts before

next i tried the same method with windows 10
again the bluescreen - at around the same moment of the installation processs

i also tried the creation of the usb-stick with the sonoma buit-in bootcamp-assistant. in this case i just created the usb stick, but then used the installation method as in my first attempt -> bluescreen

finally i went some steps back and successfully installed windows 8.1 following the attempt 1 method... and afterwards tried to upgrade that with the by rufus created windows 11 usb stick -> bluescreen

all these tries i did using opencore's bootpicker (efi installed on a separate fat32 partition as described in the link above)

i am just confused because i already had running windows 11 on that macbook pro 11,1 some time ago. first next to high sierra and then next to big sur before i installed opencore and did a completely clean and successful installation of sonoma on a new ssd.

and thats where i'm now - i have nicely running sonoma and a also good and working windows 8.1
but i want windows 11

puhh - i just don't havy any clue where my mistake(s) is (are) ...

 

[webg3]

hi trifero!

my first attempt was as described here:

https://dortania.github.io/OpenCore-Legacy-Patcher/WINDOWS.html#installation-process

... and there i first tried the standard "microsoft method" with windows 11 - the only thing i changed was the creation of the usb stick - i did it on another windows machine with the help of rufus, to overcome windows 11's hardware restrictions right from the beginning. then i got that annoying bluescreen - i assume it was quite short of the end of the whole installation process and after some necessary restarts before

next i tried the same method with windows 10
again the bluescreen - at around the same moment of the installation processs

i also tried the creation of the usb-stick with the sonoma buit-in bootcamp-assistant. in this case i just created the usb stick, but then used the installation method as in my first attempt -> bluescreen

finally i went some steps back and successfully installed windows 8.1 following the attempt 1 method... and afterwards tried to upgrade that with the by rufus created windows 11 usb stick -> bluescreen

all these tries i did using opencore's bootpicker (efi installed on a separate fat32 partition as described in the link above)

i am just confused because i already had running windows 11 on that macbook pro 11,1 some time ago. first next to high sierra and then next to big sur before i installed opencore and did a completely clean and successful installation of sonoma on a new ssd.

and thats where i'm now - i have nicely running sonoma and a also good and working windows 8.1
but i want windows 11

puhh - i just don't havy any clue where my mistake(s) is (are) ...

Try not to boot from EFI Boot (OCLP) when booting the bootable USB stick for Windows 11 (try to create a USB stick in MBR format and not GPT), you will be able to update your existing Windows 8.1 installation if you do it this way.

 

[trifero]

hi trifero!

my first attempt was as described here:

https://dortania.github.io/OpenCore-Legacy-Patcher/WINDOWS.html#installation-process

... and there i first tried the standard "microsoft method" with windows 11 - the only thing i changed was the creation of the usb stick - i did it on another windows machine with the help of rufus, to overcome windows 11's hardware restrictions right from the beginning. then i got that annoying bluescreen - i assume it was quite short of the end of the whole installation process and after some necessary restarts before

next i tried the same method with windows 10
again the bluescreen - at around the same moment of the installation processs

i also tried the creation of the usb-stick with the sonoma buit-in bootcamp-assistant. in this case i just created the usb stick, but then used the installation method as in my first attempt -> bluescreen

finally i went some steps back and successfully installed windows 8.1 following the attempt 1 method... and afterwards tried to upgrade that with the by rufus created windows 11 usb stick -> bluescreen

all these tries i did using opencore's bootpicker (efi installed on a separate fat32 partition as described in the link above)

i am just confused because i already had running windows 11 on that macbook pro 11,1 some time ago. first next to high sierra and then next to big sur before i installed opencore and did a completely clean and successful installation of sonoma on a new ssd.

and thats where i'm now - i have nicely running sonoma and a also good and working windows 8.1
but i want windows 11

puhh - i just don't havy any clue where my mistake(s) is (are) ...

You CAN´T boot or install a legacy windows installation from OCLP boot picker, always will give you errors. OCLP boot picker can only manage operating systems based on EFI boots. You have to press Alt when booting and NOT LOAD the OCLP boot picker, just choose the Windows Partition or USB installation directly.

 

[trifero]

Hardware incompatible
W11 not playable ethernet or wifi (need drivers bootcamp)
Install Legacy Mode (MBR/GPT)

Just fot curiosity, I have updated my efi Windows 10 installation in a macbook pro 15" 2013 to Windows 11 directly from Windows 10. All drivers are loaded. Wifi, bluetooth, sound, etc. Even shortcuts for controlling keyboard brightness, display brightness and sound work.

 

[webg3]

Just fot curiosity, I have updated my efi Windows 10 installation in a macbook pro 15" 2013 to Windows 11 directly from Windows 10. All drivers are loaded. Wifi, bluetooth, sound, etc. Even shortcuts for controlling keyboard brightness, display brightness and sound work.

I also achieved this in the past, but last week I tried with Windows 11 23H2 and I was only able to update but without keeping the previous version of Windows 10.

 

[trifero]

I also achieved this in the past, but last week I tried with Windows 11 23H2 and I was only able to update but without keeping the previous version of Windows 10.

How did you bypass the Windows 11 checking?

 

[hvds]

Just now updated to OCLP v.1.5.0n, over mac OS 14.4, runs as expected.

MBP11,1: 1.5.0n wıth 14.4 also fıne here. Trying it on external SSD‘s EFI.