Tried cloning the PatcherSupportPkg repo and manually generating the dmg file, just in case I needed that new new. Same error when root patching this system. I will keep plugging at it!
Got a tip for us?
Let us know
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
- Thread starter dhinakg
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Hello,
Does anyone know if there is a way to change the model before doing the OpenCore build and install?
Thank you so much
Does anyone know if there is a way to change the model before doing the OpenCore build and install?
Thank you so much
reset PRAM and SMC and above all you have to use the latest OCLP 0.6.9n dated 28 sept and rebuild and install opencore if you haven't done so, with this latest version... it worked for me too with the same iMac just installed Sonoma (upgrade from 13.6) then it stopped working and now it works with latest OCLP
GOTEM! I had some sussy 3rd party kexts in /Library/Extensions/ that were interfering with the kernel cache rebuild. Looks like some ancient ZFS stuff I must've been trying to do years ago (specifically spl.kext and zfs.kext). Moved those out of that directory, re-ran the root patches, and blamo I have wifi.
Another weirdo issue I have now is that this machine refuses to show my desktop background no matter what I pick. I just get a solid gray background. Otherwise this appears to be working! Now to see if I can get my audio interface to be recognized since this iMac is my DAW...
Another weirdo issue I have now is that this machine refuses to show my desktop background no matter what I pick. I just get a solid gray background. Otherwise this appears to be working! Now to see if I can get my audio interface to be recognized since this iMac is my DAW...
It's an option in the settings. Click settings and there's a drop down right at the top.
Try an older beta of the Sonoma branch before you give up. If you have the time and energy.
I have not tried the 14.1 beta but saw the same error with the 14.0 release and it worked with an older
version of OCLP Sonoma.
Fixed my wallpaper issue by smoking the 2 desktop.* files in ~/Library/Application Support/Dock/ then logging out and back in. This system seems to be 100% good to go now! Thanks everybody for your help in debugging.
Good to see you got it sorted out, congrats 👏
I read your post. I believe some of us (me at least) would appreciate a short heads-up if you have the time.
What does the rooted part mean for practical security and when did it change? Who if any, can snoop how and where?
The short version in your opinion would do.
I got side-tracked with some computer security issues (intrusion detection) and it got me thinking more about this. For the reasons I've stated, I will only be using OCLP 0.6.8 to patch Ventura and earlier versions of macOS (no Wi-Fi / network rooting). I will use OCLP 0.6.9 and later for Sonoma, but I won't be using Sonoma for anything that requires more than a modicum of computer security on my Mac. This has nothing to do with trusting or not trusting anyone, it's just about limiting the attack surface. Ok - I'll get off of my soap box.
You can read about rooting just by searching. What changed for me was that OCLP for Sonoma must now patch the most fundamental, secure components of the macOS operating system in order for Wi-Fi to work. There is a Wi-Fi framework that is injected by the OCLP post-install patcher (not just the kexts in OC EFI). It is my paranoia that raises the hair on my neck. Any time another party is injected into the data flow (thus a "man in the middle" - you can search for that), that is a problem for me and my spidey senses go up. People like me with Cisco and other certifications tend to go overboard when it comes to computer security. I've never been fired or dismissed from a job because I was too cautious about computer / network security. It's the nature of my work.
This is not because of some mistrust that I have in the Devs. It's the vulnerability that now exists because macOS has been tampered with at the most fundamental levels, thus "breaking the seal" of the secure OS. Even if my paranoia is out of ignorance and a lack of understanding of OCLP, I never make a computer security decision in favor of adoption unless I know with as much certainty as I can have.
-------------------------------------------------------------
Computer security is as much or more about what you don't know as what you do know. There are agencies (like NIST) who develop security standards (like FIPS). Software developers who can afford it and who need it for their customer base will hire a certified entity to perform the compliance testing required to obtain the security seal of approval. The security scan required to pass the test happens periodically and is required for maintenance of the certificate with each new software release. Don't expect anything like this type of certification with OCLP. In my experience, the times where we failed the security test were not because of things we did intentionally or knowingly, they were because of things we missed. They were because of bugs and mistakes.
As long as software can have bugs and mistakes and as long as it is developed by humans (or by AI that was developed by humans), the only way to have a degree of certainty in the secure nature of the software is to have it tested and certified with a seal of approval by a reputable organization. That is unlikely with OCLP.
EDIT: Each of us needs to make our own decision. I'm just saying that I won't be visiting my online banking website in Sonoma with OCLP post-install Wi-Fi patches.
Last edited:
@houser One more thing - even if you have 100% trust in OCLP, with a broken macOS seal, if something else exploits the broken seal, you're unlikely to detect and know that. That's true even with non-Wi-Fi post-install patches that must break the macOS seal (like non-metal patches).
Thanks @deeveedee
Way beyond my skillset. Will do some reading and try to make my decision.
The internet is not exactly a safe place and I do like privacy
Way beyond my skillset. Will do some reading and try to make my decision.
The internet is not exactly a safe place and I do like privacy
I wish I were Mr. Magoo when it comes to computer security (you may need to search for him, too). It's one of those things that once you see it, you can't unsee it. I think it's better that most people don't see it, but don't assume it's not happening. It's no wonder that PANW, CRWD, ZS (look up the ticker symbols) have a good business case.Thanks @deeveedee
Way beyond my skillset. Will do some reading and try to make my decision.
The internet is not exactly a safe place and I do like privacy
EDIT: ... and if you (not you specifically, but all who read this) are naive enough to think that only good, well-intended people are monitoring the development of OCLP, then you should probably continue to ignore the fact that there are people testing OCLP-patched Macs to find the security flaws to be exploited.
Last edited:
Thank you! I'll still be lingering in this thread to say if I can pay it back now. This forum is theeeee place when it comes to hacktivating old hardware.
FWIW Sonoma seems to be way more responsive than Ventura on this old MacBook Air. Haven't spent a lot of time on my iMac yet to judge performance.
Nice! I'll be playing with Sonoma again when the Devs release post-install patcher updates. I doubt that fixes for 14.1 post-install patching are high on their list of priorities, but I've learned not to doubt their abilities to work magic.
I have not done what you asked, but I have seen others ask this. Maybe others have a solution for you. I do remember this graphic, but I don't remember where it was posted. Maybe there is a clue in this for you.
yes, a titan ridge pcie card flashed for mac(it has to be flashed, no way around that one)
Thanks @deeveedee
Hang on a minute though. I am not living under a rock and I know what rooted is and who Mr Magoo is
More specifically I would appreciate any comment you may have on potential exploits targeted towards OCLP Macs and I assume those exploits would be distributed also in the usual ways. If you can comment on this without helping the hackers that is
It does not seem like a big enough crowd to be worth targetting off the bat, but I guess we shall see and possibly find out the hard way.
Thank you very much for the reply,
The problem is that I can't get to the settings button... when I start it, a window appears that tells me that I don't have the correct settings, then it goes to the build one, which fails because the model doesn't recognize it and back to home menu....
I don't know what to do... I can reinstall everything but I'd like to leave it as a last resort.
Thank you again.
You should be able to simply delete the contents of the OCLP EFI folder (search for "Mount EFI Mac") and redownload and install a new OCLP EFI and repair your install manually. If you need to you could also build an OCLP EF( and install it to an USB and select it after alt boot and then repair your install manually from there. That might be prudent if you need to reboot and need a working OCLP.
Good luck.
Last edited: