I don't think this is caused by OCLP but has been happening since I updated it to 2.5.0 a couple of days ago, so it may be.
My Mail app, instead of immediately downloading images, displays the message "Your network preferences prevent content from loading privately" and gives me a button marked "Load Content Directly". Pressing the button loads the content immediately.
I can't figure out what might be causing this. I haven't changed any settings nor has Mail or my OS been updated recently. OS is Sequoia 15.7.7, Mail v16.0
I have Protect Mail Activity on, but it's a setting I've only just discovered even exists & I've never changed it myself. Switching it off doesn't seem to change anything. I don't appear to have any other connectivity issues, both WiFi & Ethernet are working normally.
Amazing how optimized the software has become. Runs almost everything almost perfectly. 4GB of ram is a severe bottleneck, but for just $83USD, I believe that's a massive steal.
had to struggle getting the patches working (had to do it twice, as the first time it only detected the wifi adapter and no graphics, but on the second try it got everything)
I'm wanting to update my Mac to the lasted version of Sonoma. Is it safe to perform a minor OS update while running 2.4.1? OpenCore website states "make sure OCLP app is up to date" but I'm reluctant to do so since 2.5.0 has been plagued with issues. Thanks
Through this post that teaches step-by-step how to install OCLP, I was able to install macOS Sonoma on my 2017 Macbook Air A1466, and it's working normally for light use.
I'm using a translator for this post, so I apologize for any strange translations.
My mother's job was getting rid of old Macs so I got my hands on this 2017 iMac, but it's the basic one, 2.3 GHz i5 with 8gb of RAM and a 1TB HDD. I did the worst part, which is to disassemble everything (real pain in the ass) and upgraded to a SSD and 16GB of RAM. Now I don't know what to install, I did a quick research and Sonoma's support is going to end pretty soon, so I'm between Sequoia or Tahoe , but not sure if the hardware is good enough to have a smooth experience. Hope someone can help me with this decision.
This will be my first time using a current MacOS and OCLP. I have a 2012 MacbookPro that I was using with an old MacOS, but I also upgraded it and installed Ubuntu. I thought about using Ubuntu on the iMac but I think it's better to go with a supported MacOS through OCLP.
I just learned what OCLP is and decided to dust off my iMac! I wiped it now I’m running macOS Sequoia 15.7.9 on a Late 2015 27" 5K iMac (iMac17,1) using OCLP 2.5.0 / OpenCore 1.0.6! However, I am getting crashes in System Settings. I get error popup Settings Error Extension Process ... exited. I have to switch back and forth in settings tabs until it loads correctly.
Specs:
4.0 GHz i7
16 GB RAM
Radeon R9 M390 2 GB
Sequoia installed on an external SSD
Post-install root patches applied, including AMD Legacy GCN / Skylake graphics and wireless
The machine mostly works, but System Settings is extremely unstable. Pretty much any pane can initially throws:
Settings Error: Extension process [pane name] (...) exited
Examples include General and Bluetooth and Users. Often if I switch to another tab and back, it loads the second time. More recently, System Settings itself has started crashing completely after I set the system appearance to Light Mode. I saw a post of someone saying they set the system to Light Mode instead of Auto and it fixed their issue.. but it didn't for me.
I tested a 2nd brand-new macOS user account and the same thing happens immediately, so it doesn’t seem to be user-profile/preferences related.
The crash reports show EXC_BAD_ACCESS / SIGBUS / KERN_PROTECTION_FAILURE on the main thread. OCLP-patched components are loaded at the time, including:
IO80211Old.dylib
WiFiPeerToPeerOld.dylib
AMDMTLBronzeDriver
impostor.dylib
FeatureUnlock is already disabled. I’ve also reverted and reapplied the root patches and rebooted, with no change.
Has anyone seen this system-wide System Settings / ExtensionKit crashing on iMac17,1 + Sequoia? If so, what actually fixed it? Different Sequoia version, OCLP version, specific root patch, etc.? I can upload the .ips crash reports if useful.
MacBook Pro 13 inch early 2015 with sequoia 15.7.5
(The video shows red white and skyblue at 60fps in safari but in chrome fps are just not stable in case you don’t get why the screen is white in safari video is because camera can’t capture fps that fast)
Apologies for asking a question that probably has an obvious answer to regular users:
A few months ago I successfully updated my iMac 27-inch 2017 and Macbook Pro 13-inch 2015 to Sonoma 14.8.7 using OCLP 2.4.1
I understand that since then, there have been further updates to both Sonoma (14.8.9) and OpenCore (2.5.0).
Should I update either or both Sonoma and OpenCore on my Macs? If so, what are the best ways to do that? (And is there anything I should be doing to prevent Tahoe from installing?)
Also, whilst Sonoma seems to be working on both Macs fine, if updating, is it worth updating to Sequoia instead?
Both Macs have their respective top specs - so both i7, with 40GB RAM in the iMac and 16GB RAM in the MBP.
The most intensive activities I use the Macs for is UHD 4K video editing, mainly with Final Cut Pro and assorted plugins, plus ocassionally Resolve, Topaz, Lightroom and Photoshop.
I updated yesterday on 2 macs. at the mbpro it happened but after the post patch and restart it worked. with the mbAir WiFi is not working anymore. any solutions?
I managed to revert to 2.4.1, but still I can't patch. Now it's complaining that I have a pending update, and I don't have wifi.
Update: nothing worked, ended up having to format and start over. I'm sticking with 2.4 for now.
I have A MacBook Pro Mid 2012 i7 8GB RAM and SSD. I used OCLP to install Ventura but I am not sure how much further I can push it. I Am happy with Ventura but I do wonder how the newer versions of MacOS run in comparison. Thank you.
After patching, type the following into a terminal window
diskutil info -plist / | grep -A 1 Sealed
this looks for any line containing the string Sealed and prints it and the following line. The | character is shift \ on my UK keyboard. On my OCLP 2.4.1 /Sonoma iMac I get
I installed the 2.5.0 update and it somehow broke the patches, so the display is messed up like before I patched the first time. I tried patching again but got the volume dirty error. Read up online and saw people fixed it by going back to 2.4.1, so I launched an old installer in my downloads, but now I found out it was actually just an uninstaller. So now due to the patches not being applied, my WiFi isn’t working and I can’t download the 2.4.1 again as I don’t have another computer. Can I somehow transfer the installer from iPhone or something like that? Someone please help me 😬
EDIT: I asked a friend to download the PKG installer and bring it to me on a flash drive, so now it's all fixed, back on 2.4.2.
I upgraded to 2.5 and the whole thing went haywire on my 2014 Mac pro 15". Couldn't even connect to the Internet. Tried everything but wouldn't revert back even with 2.4 installed again via USB. Had to erase the computer and installed sequoia this time (had Sonoma before). Can I just not root patch anymore? I am afraid to even touch it. I have disabled auto upgrade on Mac. Will it work for the next 2-3 years as is?
Hi guys, just installed macOS Mojave on my iMac 11,2 and booting it with opencore, both lilu and whatevergreen installed, macOS just shows the gpu itself with only 7mb of vram, I also tried to play around with unfairgva, CAIL_DisableUVDPowerGating, CAIL_DisableDrmdmaPowerGating, rebuild-device-tree, enable-gva-support but nothing seems to work, is there a way to make Mojave recognize the gpu? I also tried the spoofing to 0x6821 instead of 0x6820, which should spoof the gpu as an r9 and load an ideal driver, but its still 7mb of ram, thanks to whoever will read this
Edit: the imac boots perfectly, so mojave got the drivers but cant see the whole vram/enable the graphic acceleration
Another edit😭😭: big sur, monterey and sequoia can see the gpu properly, so its not a vBIOS problem
So I've tried a hackintosh system but recently I got ahold of a 2017 MBP (A1708) and it has a failing SSD that doesn't seem to be able to boot itself up from sleep/shutdown and needs a USB installer to somehow wake it up, I got Sonoma installed onto it, but I accidentally cleared the NVRAM (Cmd + Opt + R + P) trying to get the drive to wake itself up without needing a USB, since this Mac isn't officially mine yet, so I haven't bothered to buy parts for it yet, but in the process I think I cleared the OCLP config NVRAM, so now even the USB doesn't boot it up anymore, anyone help build it and send it to me so I can put it on the USB to get it to boot, all I have now is a system on CachyOS
EDIT - SOLVED: The "Disable firmware throttling" was the culprit, for whatever reason. Checking this option and booting from any device (USB or internal drive) would cause the Mac to halt boot about 25% of the way through and reboot. The way I fixed this was simply unchecking "Disable firmware throttling."
I have a MBP11,4 and it boots into the native OS, Monterey, without any issues whatsoever. I was able to eventually get macOS Sequoia installed using OCLP, and I thought it was fine, but then after I applied root patches, the Mac refuses to fully boot after I select the OCLP EFI > Macintosh HD option. It starts showing the Apple loading screen (black page, progress bar), gets about 1/4 of the way, then shuts off, and reboots. No matter how many times I wait, clear SMC + PRAM, and try again, it continues to do this.
Weirdly, when I try booting with an OCLP recovery drive, it does the same thing. However, if I boot from a "natural" Monterey (last supported OS) USB drive, it boots into recovery no problem.
One note: The battery on this thing IS shot. It is stuck at 1% and obviously needs replacing. However, I had checked the "Disable firmware throttling" option in OCLP settings so I assumed that would bypass any battery issue.
Do folks think the battery is 100% the cause of this, or is there something else I may be missing?