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.

saudor

macrumors 68000
Jul 18, 2011
1,512
2,115
Distinguish between "natively supported in Sonoma" and "Sonoma's Broadcom Wi-Fi framework still natively supports the card." If Sonoma's Wi-Fi framework still supports the device without root-patching, then the only requirement would be the injection of missing kexts via OC (which could be accomplished without OCLP and with OC alone).
I was under the impression that it was a no starter for all dropped macs without root patching. they've also mentioned that they observed this behavior until the release. Anyways this is interesting so I'm going to try what they did and see what happens (obviously with some changes as this is a hack and not a real mac).

My Wifi card reports 3602 with 4.2 BT, which seems to be the same as in the 4k 2017.
 

Attachments

  • Screen Shot 2023-09-30 at 8.57.04 AM.jpg
    Screen Shot 2023-09-30 at 8.57.04 AM.jpg
    455.6 KB · Views: 210

deeveedee

macrumors 65816
May 2, 2019
1,453
2,116
Peoria, IL United States
I was under the impression that it was a no starter for all dropped macs without root patching. they've also mentioned that they observed this behavior until the release. Anyways this is interesting so I'm going to try what they did and see what happens (obviously with some changes as this is a hack and not a real mac).

My Wifi card reports 3602 with 4.2 BT, which seems to be the same as in the 4k 2017.
Thanks! I will test my hack's BCM94352HMB again (without root patches) and report back.

EDIT: That was a quick test without surprises. I have a test volume on my MBP6,2 with 14.1 installed (no root patches). In the test volume, I initially installed 14.0 Release (directly from Apple), applied 0.6.9 root patches, and then upgraded to 14.1 Beta (which required the full installer via OTA for my non-metal Mac). After booting the upgraded 14.1, I did NOT re-apply post-install patches.

No surprises, no Wi-Fi. Wi-Fi appears to turn on, but it will never find available networks. That's the behavior when the Brcm Wi-Fi framework is missing from Sonoma.

Screenshot 2023-09-30 at 9.02.47 AM.png


Screenshot 2023-09-30 at 9.26.38 AM.png
 
Last edited:

DeBilbao

macrumors member
Jan 13, 2008
53
6
Distinguish between "natively supported in Sonoma" and "Sonoma's Broadcom Wi-Fi framework still natively supports the card." If Sonoma's Wi-Fi framework still supports the device without root-patching, then the only requirement would be the injection of missing kexts via OC (which could be accomplished without OCLP and with OC alone).


That makes a lot of sense, and likely will be the only explanation required.

And it’s good news for my 2017 4K Mac!

Being that way, I don’t like what Apple is doing, retiring from support when the only requirement is a small file.


 
  • Like
Reactions: perez987

MacinMan

macrumors 65816
Jan 27, 2011
1,379
787
Denham Springs, LA
Can I use Open Core as a Linux boot loader instead of grub? I ask because I have issues with getting grub to install to an external drive instead of trying to overwrite the bootloader on my internal drive. Open core is good on external media so i wanted to find out because it's an EFI bootloader if I can use it to boot linux instead of grub. Thanks
 

DeBilbao

macrumors member
Jan 13, 2008
53
6
That was a quick test without surprises. I have a test volume on my MBP6,2 with 14.1 installed (no root patches). In the test volume, I initially installed 14.0 Release (directly from Apple), applied 0.6.9 root patches, and then upgraded to 14.1 Beta (which required the full installer via OTA for my non-metal Mac). After booting the upgraded 14.1, I did NOT re-apply post-install patches.

No surprises, no Wi-Fi. Wi-Fi appears to turn on, but it will never find available networks. That's the behavior when the Brcm Wi-Fi framework is missing from Sonoma.

This is not exactly the same test I would do to check if my procedure applies to your card.

I suggest using a USB pendrive with at least 16GB capacity, download latest macOS Sonoma official install app, use latest OCLP Nightly to create the installer in the USB drive, let OCLP read your configuration and create the EFI folder and write it to the pendrive.

Once it is done, boot from the thumb drive, select EFI boot from the Apple boot loader and once OpenCore boot loader appears, start your macOS system.

This won’t be exactly the same scenario, as I also did a new clean install in an external drive.
 

davidlv

macrumors 68020
Apr 5, 2009
2,291
874
Kyoto, Japan
Can I use Open Core as a Linux boot loader instead of grub? I ask because I have issues with getting grub to install to an external drive instead of trying to overwrite the bootloader on my internal drive. Open core is good on external media so i wanted to find out because it's an EFI bootloader if I can use it to boot linux instead of grub. Thanks
With all respect, that post shold be in the "Linux on Mac" thread. I am surprised you didn't think of that.
 

deeveedee

macrumors 65816
May 2, 2019
1,453
2,116
Peoria, IL United States
This is not exactly the same test I would do to check if my procedure applies to your card.

I suggest using a USB pendrive with at least 16GB capacity, download latest macOS Sonoma official install app, use latest OCLP Nightly to create the installer in the USB drive, let OCLP read your configuration and create the EFI folder and write it to the pendrive.
How do you think I installed Sonoma 14.0 Release? I created the USB installer using the official Apple Release and booted with the OC EFI.

I've done what I think is required to test on my system. Hopefully others can test and reply with their 'Cold Fusion' test results 😀
 

MacinMan

macrumors 65816
Jan 27, 2011
1,379
787
Denham Springs, LA
With all respect, that post shold be in the "Linux on Mac" thread. I am surprised you didn't think of that.
Sorry, I didn't think of that probably because i didn't think it was still a big enough topic to have it's own active community. it made since to ask here because this is also about using open core over Apple's boot loader.
 

TOM1211

macrumors 6502
Apr 15, 2012
390
571
I was using "online banking" to convey the type of security that I am describing and requiring (for my use). Hopefully readers are extrapolating to things like investment/stock transactions and other operations where their digital identity and data privacy needs to be protected. Even something like FaceBook (which allows single-sign-on to other secure applications) needs data integrity.

I’ve wondered if the risk is about the same as a jailbroken iPhone , which with that considering you stick to legit sources and such i have never had a issue there surely it’s more important to just not install random software more than anything could say the same about installing random stuff on a Mac without oclp and installing homebrew.
 

deeveedee

macrumors 65816
May 2, 2019
1,453
2,116
Peoria, IL United States
I’ve wondered if the risk is about the same as a jailbroken iPhone , which with that considering you stick to legit sources and such i have never had a issue there surely it’s more important to just not install random software more than anything could say the same about installing random stuff on a Mac without oclp and installing homebrew.
Take your jailbroken iPhone and replace the network layer with uncertified 3rd-party code. That's a better analogy. Even if the 3rd-party code is from a trusted/secure source, you need to decide for yourself if the risk is worth it.

Jailbreaking (rooting) has one set of exposed vulnerabilities. Replacing the network layer after you've rooted the device? At least worth some consideration.

EDIT: Then, after you've rooted the device and replaced the network layer, make sure that all installed apps and their future upgrades don't exploit the vulnerabilites or allow other apps to exploit the vulnerabilities. If you know enough, the security concerns grow exponentially and will hurt your head to think about.

EDIT: I'm thoroughly enjoying the dialog with what are clearly competent team mates. I mean that sincerely, both 'competent' and 'team.' So far, the questions and 'challenges' have only solidified my belief in my position about security vulnerabilities in OCLP-patched Sonoma.

I am totally open to a Dev visiting and opining on why I am full of $#!+ and we have nothing to worry about. Finding out I am wrong would be the best news possible.

EDIT: My wife says no matter what the Devs say, I'm still full of $#!+... and today's a good day ;)

===============================

EDIT: For the interested reader ... this will bore most. In a previous life, I developed NDIS drivers for Windows (up to Windows 7). My NDIS drivers were designed to operate at a "low" network layer that gave them complete access to the IP stack. Each NDIS driver had a debug switch that I could turn on and off to enable "transparent" mode where I could see all the packets traversing the stack. Since my drivers operated in "promiscuous" mode, I could see the headers of all the packets that the PC observed on the network (like a network "sniffer"). Initially, when my NDIS drivers were installed, Windows would flash a prompt asking for permission to install the driver. My team became so good with the driver development, that we found ways to install the drivers such that the Windows "malicious software" detection wasn't alerted and no messages were displayed. Our software could be installed without the user's knowledge. Fortunately, we were the good guys and we never used the capability with malicious intent. I'd like to think that everyone is one of the good guys.
 
Last edited:

saudor

macrumors 68000
Jul 18, 2011
1,512
2,115
Thanks! I will test my hack's BCM94352HMB again (without root patches) and report back.


View attachment 2285129
Following up on this. Getting the same result. Just for lolz, i root patched it and it started working as expected. Even with the root patches, the S/L/E folder does not contain any of those legacy kexts

@DeBilbao can you check to see if your SSV is still sealed by running diskutil apfs list
 

deeveedee

macrumors 65816
May 2, 2019
1,453
2,116
Peoria, IL United States
EDIT: Read this before attempting to upgrade to 14.1 Beta

I looked back to try to give credit where credit is due, but couldn't find the earliest reference. Someone here had mentioned that the 14.1Beta post-install patches fail because Apple has not yet released the 14.1 KDK. This is confirmed on Discord. I think this means that 14.1 post-install patches could start working without any changes to OCLP (just a re-application of the post-install patches) after Apple posts the new KDK (and OCLP is able to download it).

EDIT: More from Discord and something I didn't know. Some Mac models do not require the KDK for root patching. If you have a Mac that does not require the KDK (don't know which ones), then 14.1 with OCLP post-install patches should work for you.
 
Last edited:

amaze1499

macrumors 65816
Oct 16, 2014
1,192
1,221
I need some help please:

I accidentally installed the 14.1 beta on my 9,2 and somehow bricked my device. Since then I can’t install neither Sonoma 14 (downgrade is not possible) or Ventura on any internal or external drive whatsoever.

The error seems to be always the same:

Mac update assistant couldn’t install a firmwire required. It doesn’t matter whether I try the internal SSD and external SSD, or I am connected to Wi-Fi or ethernet.

Did anyone else had the same issue or similar one and how did you solve it? Any advice is appreciated.
 
  • Like
Reactions: alexjohnson

Omar9x

macrumors newbie
Sep 30, 2023
1
0
I installed Sonoma 14.0 to my MacBook 11,5 (2015), after installation completed, WIFI, Bluetooth & Screen Resolution Didn't work, but After root Patching with OCLP 0.6.9 Everything seems to be ok except Bluetooth and AirDrop, its looks active but doesn't work, i cant Connect any Bluetooth Device, Any Ideas Please?
 

houser

macrumors 6502
Oct 29, 2006
405
544
I need some help please:

I accidentally installed the 14.1 beta on my 9,2 and somehow bricked my device. Since then I can’t install neither Sonoma 14 (downgrade is not possible) or Ventura on any internal or external drive whatsoever.

The error seems to be always the same:

Mac update assistant couldn’t install a firmwire required. It doesn’t matter whether I try the internal SSD and external SSD, or I am connected to Wi-Fi or ethernet.

Did anyone else had the same issue or similar one and how did you solve it? Any advice is appreciated.
Yes, I have seen this.
I fixed it last time by wiping the APFS container and using an older OCLP Sonoma branch to install Sonoma 14.0 again
In my case 18 Sept. nightly. Maybe either or both works for you too. Good luck.
 
Last edited:
  • Like
Reactions: olad and amaze1499

schmalen

macrumors newbie
Nov 2, 2020
15
13
No surprises, no Wi-Fi. Wi-Fi appears to turn on, but it will never find available networks. That's the behavior when the Brcm Wi-Fi framework is missing from Sonoma.

try -brcmfxbeta

I also have the BCM94352HMB but not in a realmac ...;-) have first still patched with OPLC then I used in boot arg still additionally the -brcmfxbeta. As Kext I have the 2.1.8 AirportBrcmFixup.kext and AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext additionally activated. My wifi works. I also had WiFi before without this boot arg but it did not detect any networks. Bluetooth I got by additional Kexte to run.
 
  • Like
Reactions: deeveedee

deeveedee

macrumors 65816
May 2, 2019
1,453
2,116
Peoria, IL United States
try -brcmfxbeta

I also have the BCM94352HMB however not in a realmac ...;-) I have in boot arg additionally used the -brcmfxbeta. As Kext I have the 2.1.8 AirportBrcmFixup.kext and AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext additionally activated. My wifi is running. I also had WiFi before without this boot arg but it did not detect any networks. Bluetooth I got by additional Kexte to run.
Yup - it's in there. We were just confirming that BCM94352HMB needs OCLP 0.6.9 post-install patches to operate in Sonoma. Works great!

See here. I'm not maintaining that thread any more, but you can see my progress through recent OCLP 0.6.9 commits with Sonoma 14.0 Beta.

EDIT: I was just looking through my not-so-old thread and noticed that I concluded with an experiment. In case anyone still cares about that thread, -no_compat_check is still required on the hack. That was a failed experiment (not unlike Cold Fusion). The "boot-loop" problem that I was trying to solve turned out to be a flaw in RestrictEvents.kext (which has been fixed by Devs).

... Wait a second. I thought it wasn't possible to have a bug in software ... especially a Kext.
 
Last edited:

DeBilbao

macrumors member
Jan 13, 2008
53
6
Following up on this. Getting the same result. Just for lolz, i root patched it and it started working as expected. Even with the root patches, the S/L/E folder does not contain any of those legacy kexts

@DeBilbao can you check to see if your SSV is still sealed by running diskutil apfs list

System volume seal is broken when running macOS Sonoma with OCLP

My MacBook Pro is running Sonoma and the system disk reports Sealed: Yes

My regular system drive for the iMac 4K is an 480MB Aura X2 from OWC

Code:
|   +-> Volume disk2s5 9382499C-
|       ---------------------------------------------------
|       APFS Volume Disk (Role):   disk2s5 (System)
|       Name:                      Aura Pro X2 (Case-insensitive)
|       Mount Point:               Not Mounted
|       Capacity Consumed:         9169129472 B (9.2 GB)
|       Sealed:                    Yes   <-------------------------- SSV Sealed
|       FileVault:                 No
|       |
|       Snapshot:                  2F0F2D58-
|       Snapshot Disk:             disk2s5s1
|       Snapshot Mount Point:      /
|       Snapshot Sealed:           Yes   <--------------------------  Snapshot Sealed

I installed macOS Sonoma in 100GB partition of a 1TB Samsung T5 SSD drive, and both the system and the snapshot seals are broken

Code:
|   +-> Volume disk7s5 48F5D910-
|   |   ---------------------------------------------------
|   |   APFS Volume Disk (Role):   disk7s5 (System)
|   |   Name:                      macOS iMac 4k (Case-insensitive)
|   |   Mount Point:               Not Mounted
|   |   Capacity Consumed:         9842647040 B (9.8 GB)
|   |   Sealed:                    Broken   <----------------------- SSV Broken
|   |   FileVault:                 No
|   |   |
|   |   Snapshot:                  89F7A280-
|   |   Snapshot Disk:             disk7s5s1
|   |   Snapshot Mount Point:      /
|   |   Snapshot Sealed:           Broken   <----------------------- Snapshot Broken

:)
 

saudor

macrumors 68000
Jul 18, 2011
1,512
2,115
I installed macOS Sonoma in 100GB partition of a 1TB Samsung T5 SSD drive, and both the system and the snapshot seals are broken
That really seems like root was patched, which can cause the seal to break. Your MBP is of course natively-supported so those results are in line with expectations.
 

DeBilbao

macrumors member
Jan 13, 2008
53
6
That really seems like root was patched, which can cause the seal to break. Your MBP is of course natively-supported so those results are in line with expectations.

I said MacBook Pro when I wanted to say iMac 2017 4K.

I wanted to share that with the same device, different operating systems installed in different drives behaves different regarding SSV seal.
  • macOS Ventura was installed by Apple and seal isn't broken
  • macOS Sonoma was installed with the help of OpenCore Legacy Patcher and seal is broken
My MacBook Pro 2020 is running macOS Sonoma and as it's officially supported by Apple, the seal of it's system drive isn't broken.

:)
 
  • Like
Reactions: deeveedee

MacinMan

macrumors 65816
Jan 27, 2011
1,379
787
Denham Springs, LA
Hey all, just reporting that I changed a few settings in Sonoma and things seem to be working much better.
1 being, my WiFi apparently got switched to 2.4ghz instead of 5, and I disabled the new setting regarding clicking on the desktop that's on by default and it also helped improve things.
 

K two

macrumors 68020
Dec 6, 2018
2,314
3,187
North America
Mini7,1 14.0 23A344 Bug type 313, Siri Search related and the old MTLCompilerService crash in Weather app. btw, Siri search turned off in C/P. Siri crashes while sleeping. Not seen in Beta7 but concerning.:rolleyes: OCLP069n 9/28 11:11AM build.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.