One thing that could affect this is if the system attempts to stage an update, as the system updates (since 15.4 I believe?) as I understand it will be able to modify the system volume, which in turn may break some aspects of the patching and so needs redoing.Has anyone found they have to reinstall the post-install root patches after every reboot in order to avoid massive system sluggishness and graphical stuff not working best?
Thank you, good to know what I’m trying to do, once I can do it. Bonus frustration: when I went to try that I found no Ethernet port on this MBP, but I’ll try an adapter with USB or HDMI and see if that works. Man, they really headed this one off at the pass.Connect to your router using an ethernet cable perhaps? Once connected, download OCLP, build it and install to SSD. Then apply the post install root patches and reboot.
One way around which has been discussed here is to make sure all auto updates are off, so no unintended staging of updates takes place which requires you to apply patches again. That is also what has been recommended by the OCLP peeps that visit this forum at times. So when you update a Mac with OCLP, it should be an active choice.>> but the question arises: is there a way around all this? Can that switch flipping be avoided? Is there a work-around?
To maintain an OCLP setup on one of those rMBP:s , you probably need the Apple Thunderbolt to ethernet adapter for smooth upgrading. Has worked here at least. Or maybe something else solidly compatible with current drivers. A bonus point is that you are also more secure with that than when using Wifi for things like online banking. Ah well. Good luck.Bonus frustration: when I went to try that I found no Ethernet port on this MBP, but I’ll try an adapter with USB or HDMI and see if that works. Man, they really headed this one off at the pass.
are you sure the OpenCore Legacy Patcher app isn't on the Mac? If not you can simply download it onto a USB drive, copy and install it. Once installed, run the Post-Install Root Patch.I know. I mean NOW I know. It shouldn’t have. And yet, it prompted me to and did upgrade. mid 2015 MBP, I bought it used just a few months ago, previous owner had OCLP on it, hence the upgrade loophole. Made the regrettable decision to apply the upgrade, not assuming it would offer/attempt something it’s own hardware couldn’t logistically do. But long story short, it upgraded and now it’s not bricked exactly, and my config, desktop and files are there BUT the system text is comically small (like 4pt, see photo) and something is actively blocking it from finding wifi networks.
Mac forums kept deleting my threads about it (3rd party patch maybe), so I’m not sure if I should be trying to fix those few things or if more under the hood isn’t really as functional as it seems to be all there, and I need to revert to my previous functional OS. Problem is, I can’t do it through the internet. Internet Recovery mode instantly sees and connects to my wifi but when booting back into the OS, somewhere it’s being blocked. No networks found and unable to join when adding it manually through system settings.
I’ve already tried:
- Sudo commands to stop/start wifi
- rebooting in all the modes
- rebooting routers
- forgetting network in Settings
- trashing plist files
- resetting NVRAM
- yelling at it
- building a Time Machine to go back to yesterday and tell my younger dumber self to continue ignoring “System Upgrade Available” for life.
What have I done, o wise ones? I don’t know when Macs got so into planned obsolescence, but does anyone know how I can strongarm the wifi into working so OCLP can build a new boot, or what I should be doing from here?
I stopped updating new macOs release thru OTA since OCLP 2.3.2, using USB installer to update automatically apply Post install root patch in one process, no need to do extra stuff.are you sure the OpenCore Legacy Patcher app isn't on the Mac? If not you can simply download it onto a USB drive, copy and install it. Once installed, run the Post-Install Root Patch.
I've never used disk installation or creating a macOS Installer; I've always done it via OTA without any issues, even the initial upgrade from Big Sur.
Updating with OTA and then doing the rootpatch after a restart isn't a lengthy process...besides, OCLP now updates itself, so it takes me much longer to create a USB installer.I stopped updating new macOs release thru OTA since OCLP 2.3.2, using USB installer to update automatically apply Post install root patch in one process, no need to do extra stuff.
You got lucky, the swap worked cause they're really close in parts for example the same CPU/GPU generation. When the systems start deviating in parts and year, then there can be major issues especially with non-AVX2 vs AVX2 and so on.Random post ,
I picked up a 2014 Mac mini running Catalina , formatted it updated it to latest macOS Monterey , opened it up (clearly never been
Opened ) sorted the inside out it had collected rather a lot of dust took the drive out of my mid 2014 MacBook Pro put it in the Mac mini 2014 and booted straight into Sequoia 15.5 beta 3
as patched on the MacBook Pro . OCLP rightly complained that I was booting with the wrong settings and patched accordingly. Still a straight swap was not what i was expecting.
.![]()
Thank you, good to know what I’m trying to do, once I can do it. Bonus frustration: when I went to try that I found no Ethernet port on this MBP, but I’ll try an adapter with USB or HDMI and see if that works. Man, they really headed this one off at the pass.
Interesting. Does that thing require its own software install or will it work without it and only Sequoia and OCLP?UGREEN 2.5Gb USB to Ethernet Adapter
In my case no proprietary software was required to install on a Mac, it was plug and play on an rMBP10,1 with Sequoia & OCLPInteresting. Does that thing require its own software install or will it work without it and only Sequoia and OCLP?
Wow.. That's interesting.. I've only seen something like that when I tried to restore an app from my TM backup that I took on unsupported OS ver back to supported version on same machine..looks like something is confused.. wish I could help.Hey all, does anyone know how to fix an issue like this? I've tried deleting and reinstalling the app, and a reboot.
This is under the native macOS install. Haven't tried under Sequoia.
I am pretty sure I've seen something like that before. I believe it's a bug in the code of the app that checks the version number. Something to do with a change in how the version string is delivered by the OS and the app not using the officially sanctioned method of checking the version.Hey all, does anyone know how to fix an issue like this? I've tried deleting and reinstalling the app, and a reboot.
This is under the native macOS install. Haven't tried under Sequoia.
I've already received this warning with my MacBook Pro running macOS Big Sur (without OCLP). I waited for the next application update (Amazon Prime Video) and the problem was gone...Hey all, does anyone know how to fix an issue like this? I've tried deleting and reinstalling the app, and a reboot.
This is under the native macOS install. Haven't tried under Sequoia.
Yeah, what’s up with that? I had the same problem when I upgraded Safari to 18.4 on my Mac Pro 3,1.All good so far except the Safari issue not loading pages. I use Firefox anyway
View attachment 2507082