macOS 15 Sequoia on Unsupported Macs Thread

[Kevo]

I have run into a problem with youtube on Safari. I'm using 15.5 with OCLP 2.4.0 on my Mid 2012 MBP. After clearing my web data I can no longer get youtube to load. At first I thought it was just the TechPreview version of Safari I am using, but I cleared the data on the current version and I'm seeing the same thing there. In Brave I have no issue.

The problem is that Safari hangs with a beachball after loading youtube.com and redirecting to https://www.youtube.com/?themeRefresh=1

I end up having to force quit after that. I've tried to duplicate the problem on my iPad but I have no issue there after clearing web data and reloading the youtube page.

Has anyone else noticed this? If you have the urge to try it on an OCLP Mac or a currently supported Mac, please be sure to back up your safari files before hand. I'm not sure yet if there is a way to get the site to load again after clearing web data.

*** Follow up for anyone who runs into this or something similar. ***
I ended up restoring my ~/Library/Containers/com.apple.SafariTechnologyPreview/ folder from TimeMachine and that allowed me to load the youtube site again. After I was able to get the site to load it was still acting very funny and taking a long time to play video if they played at all. I then tried loading rumble and had a similar issue with video there. Most everything I tried would not play and I would get a spinning beach ball.

After making sure local video was still playing fine I decided to zap the PRAM. After 4 chimes I logged in and loaded both youtube and rumble with no issues and both played video. So I am speculating that something to do with my video card settings got borked somehow and that's what was causing the initial problem. There must be something in the themeRefresh script that triggers some video handling code. My initial reason to dumb web data was in fact issues with some videos not loading with an error message. I thought it was ad blocking at first, but disabling all of that made no difference.

 

[kkinto]

Question regarding spoofing and OCLP/cMP 5,1: is it necessary at all?

I would like to use hardware accelerated H264/H265 (video toolbox). What model I need to spoof? Are there any other advantages or disadvantages?

At present I seem unable to ever get rid of the message "Some iCloud Data isn't Syncing" as nothing ever happens, just keep entering passwords so no calendar, passwords. mail, photos are syncing at all. Could this be related to the machine spoofing? My settings are set to "SMBIOS Spoof: Minimal" and "SMBIOS Spoof Model: Default" and "Allow spoofing native Macs: unchecked." In "Statistics" it says:
real_board_id='Mac-F221BEC8',
reported_model='iMacPro1,1',
reported_board_id='Mac-7BA5B2D9E42DDD94',
build_model='MacPro5,1',

Is there a list anywhere of recommended OCLP settings for a 5,1?

 

[olad]

Question regarding spoofing and OCLP/cMP 5,1: is it necessary at all?

I would like to use hardware accelerated H264/H265 (video toolbox). What model I need to spoof? Are there any other advantages or disadvantages?

At present I seem unable to ever get rid of the message "Some iCloud Data isn't Syncing" as nothing ever happens, just keep entering passwords so no calendar, passwords. mail, photos are syncing at all. Could this be related to the machine spoofing? My settings are set to "SMBIOS Spoof: Minimal" and "SMBIOS Spoof Model: Default" and "Allow spoofing native Macs: unchecked." In "Statistics" it says:
real_board_id='Mac-F221BEC8',
reported_model='iMacPro1,1',
reported_board_id='Mac-7BA5B2D9E42DDD94',
build_model='MacPro5,1',

Is there a list anywhere of recommended OCLP settings for a 5,1?

I think spoofing is to enable 'Universal Control' for Intel laptops that are not natively supported by the installed macOS, so that, for example, one mouse could control two or more computers. I used to believe otherwise, until I was - very politely - set straight on this thread.

 

[ronton3]

Today I set up a new external SSD volume with a 2.4/15.5/OCLP/USB, as a test for the first 16/26 Dev release next week, thinking that it will probably need to be deleted, and hopefully will not brick the entire SSD. After restarting in the used SSD volume I found three of these credence volumes, recently I used recovery to reinstall Seq 15.5 on the external SSD and the internal HHD, because of some beachballing/mouse slowness. Yesterday there were 2 Creedences, now there are three, yesterday I force ejected two of them, but they are back. What is the best thing to do with these please?

 

[basslik]

Hi, where do you name the port? Please

Sorry for the delay.

Anyhow, I just clicked details o the Ethernet, either 1 or 2. the next page you can name it.

Not sure it it's going to work, but for some reason it worked for me.

Any case, I hope you already resolved the issue.

 

[Mystere65]

Question regarding spoofing and OCLP/cMP 5,1: is it necessary at all?

I would like to use hardware accelerated H264/H265 (video toolbox). What model I need to spoof? Are there any other advantages or disadvantages?

At present I seem unable to ever get rid of the message "Some iCloud Data isn't Syncing" as nothing ever happens, just keep entering passwords so no calendar, passwords. mail, photos are syncing at all. Could this be related to the machine spoofing? My settings are set to "SMBIOS Spoof: Minimal" and "SMBIOS Spoof Model: Default" and "Allow spoofing native Macs: unchecked." In "Statistics" it says:
real_board_id='Mac-F221BEC8',
reported_model='iMacPro1,1',
reported_board_id='Mac-7BA5B2D9E42DDD94',
build_model='MacPro5,1',

Is there a list anywhere of recommended OCLP settings for a 5,1?

On 5.1 it should be like this

 

[Jauso]

I have a problem, I originally had 2.3.2 and then i updated to 2.4.0 and restarted and then it says i have 2.1.2 (!) and if i wanted to update? so i clicked yes and i repeat and then this keeps going on in a loop

everything works fine (i am on MacOS 15.3 if it matters), so should i try to update to 2.4.0 again? and will it show up as 2.1.2 again after i restart?

does anyone else have this problem?

 

[Kevo]

Are you updating the drive you are booting from?

 

[olad]

I should have reported back that I am online. A friend generously lent me his old MBP11,3 from 2014 on which, in 2023, I had installed OCLP 0.6.9 and Ventura, with exhortations that he update often (he ignored that, but enabled auto update). He lent me the MBP because I said I would use an external SSD for my stuff, and not touch the internal SSD. As soon as I received it, I downloaded OCLP 2.4.0 meaning to remove 0.6.9 later. But autoupdates don't wait for anyone, and the MBP updated to Sequoia on the main SSD. It is to the credit of OCLP 0.6.9 that not only the installation go well, it restarted albeit without WiFi and stuff. As I had OCLP 2.4.0, I updated to that, and did a root patch. Dead easy. No hiccups whatsoever. Now the laptop was running Sequoia, it was relatively easy to create a USB installer for the external SSD and just do a 'routine' install. OCLP spoils one - no extraordinary mods, nothing, just works. And since the M1-MBA was gone, I didn't need to spoof anything. Laptop is working like a champ. Thanks to you all.

 

[Jauso]

Are you updating the drive you are booting from?

What do you mean, there is only one way to update oclp: when the popup comes up after I click on the icon when starting the app and I click yes and then after I restart my computer and that is that right? It is there a different day to update oclp to make it permanent?

 

[macpro_mid2014]

What do you mean, there is only one way to update oclp: when the popup comes up after I click on the icon when starting the app and I click yes and then after I restart my computer and that is that right? It is there a different day to update oclp to make it permanent?

What is probably happening is that you are installing OCLP 2.4.0 to another disk or partition, not the disk/partition you are booting from.
After the update, you are prompted to install OCLP to a partition. Ensure it is the one you are booting from.

 

[Kevo]

What do you mean, there is only one way to update oclp: when the popup comes up after I click on the icon when starting the app and I click yes and then after I restart my computer and that is that right? It is there a different day to update oclp to make it permanent?

Updating the OCLP app itself should have no effect on your computer. Only updating open core or the root patches to your boot drive should affect anything.

 

[Jauso]

Are you updating the drive you are booting from?

What is probably happening is that you are installing OCLP 2.4.0 to another disk or partition, not the disk/partition you are booting from.
After the update, you are prompted to install OCLP to a partition. Ensure it is the one you are booting from.

Updating the OCLP app itself should have no effect on your computer. Only updating open core or the root patches to your boot drive should affect anything.

There is only 1 drive that i have installed OCLP onto, anyways I went through the whole process again, it installed and showed up as 2.4.0, and restarted my computer at the end, and then started up OCLP again, still again 2.1.2 and asked me to update to 2.4.0

then i wanted to try something new, I shutdown and started in safe mode, did the exact same thing in the above paragraph, same result

so started back into normal mode, went to the OCLP folder, deleted it manually by moving it to the trash (btw, the OCLP uninstaller app named OpenCore-Patcher-Uninstaller.pkg as shown the releases => assets section, it does not do anything(!), because I installed it and the program was nowhere to be found in the apps folder, nor was my OCLP folder uninstalled. not sure what is going on, it just might be a useless app, the devs should fix it or remove it). then i went to the OCLP releases page and manually downloaded 2.4.0 and installed it, and afterwards to double check i restarted my computer and opened OCLP again and this time it is 2.4.0 permanently!

so i dont know why the update from the app way didn't work, i had to delete and install from new, but it works now, and I don't know if any devs read this forum, or if they don't then i hope someone can send my post to them (note I am running 15.3, which is not the latest (15.5) macOS version at the time of writing), because there is an update bug and i had to do this work around to fix it.

thanks for reading, i had to take like 10 min out of my life to type this out, i hope this is useful to future readers! 😎

 

[rehkram]

Installing the new version of OCLP is only the first step. You then have to use it to "build", or "rebuild" in your case, the new version's EFI, and then move it from its temporary folder to the production boot drive. This all done using the first option (top left, labeled "Build and Install OpenCore") on the main OCLP GUI

Then you have to reapply the root patches (top right, labeled "Post-Install Root Patch") and reboot.

All this is explained in the documentation on Dortania's site, might pay to read it 😉

 

[Jauso]

Installing the new version of OCLP is only the first step. You then have to use it to "build", or "rebuild" in your case, the new version's EFI, and then move it from its temporary folder to the production boot drive. This the first option (top left) on the main OCLP GUI

Then you have to reapply the root patches (top right) and reboot.

All this is explained in the documentation on Dortania's site, might pay to read it 😉

yup, i think i did all of that, the build and install, restart, and the post patches, but for good measure i did it all again, this is what it shows me:

 

[Neon Ball]

There is only 1 drive that i have installed OCLP onto, anyways I went through the whole process again, it installed and showed up as 2.4.0, and restarted my computer at the end, and then started up OCLP again, still again 2.1.2 and asked me to update to 2.4.0

then i wanted to try something new, I shutdown and started in safe mode, did the exact same thing in the above paragraph, same result

so started back into normal mode, went to the OCLP folder, deleted it manually by moving it to the trash (btw, the OCLP uninstaller app named OpenCore-Patcher-Uninstaller.pkg as shown the releases => assets section, it does not do anything(!), because I installed it and the program was nowhere to be found in the apps folder, nor was my OCLP folder uninstalled. not sure what is going on, it just might be a useless app, the devs should fix it or remove it). then i went to the OCLP releases page and manually downloaded 2.4.0 and installed it, and afterwards to double check i restarted my computer and opened OCLP again and this time it is 2.4.0 permanently!

so i dont know why the update from the app way didn't work, i had to delete and install from new, but it works now, and I don't know if any devs read this forum, or if they don't then i hope someone can send my post to them (note I am running 15.3, which is not the latest (15.5) macOS version at the time of writing), because there is an update bug and i had to do this work around to fix it.

thanks for reading, i had to take like 10 min out of my life to type this out, i hope this is useful to future readers! 😎

I am a documentation contributor of the project but not really a dev, anyway to give some insight:

What may be the issue why you were always launching old OCLP versions is trying to launch OCLP via Spotlight. Due to a change, OCLP puts an alias into "Applications" and as such Spotlight won't show it since it won't pickup aliases for some reason and will keep finding the older version(s) of the .app if they exist. Hence always launch via the alias in "Applications".

Basically, OCLP v2.3.0 deprecated the ".app.zip" package in favor of a new .pkg based installer method that existed for a while already but was an option. This new method always installs the app to "/Library/Application Support/Dortania" and puts an alias to "Applications", which ensures it will always be in a fixed location and all the mechanisms work. If you used the ".app.zip" method with 2.1.2 and extracted it to a random location (as in not into "Applications"), the updater/installer/uninstaller can't be aware of those locations and therefore cannot know to remove or replace them. You'll have to find and remove these yourself, as the updater will just make a new install to that previously mentioned location.

The uninstaller only works if the app exists in the aforementioned location, it again has no idea if an older app extracted from the .zip resides elsewhere on the system. The uninstaller was created to target the new method from the beginning, since the new method does more than just extracting the app, such as installing a PrivilegedHelperTool to avoid admin password spam in every section. As such the uninstaller has to make sure to remove those as well, in addition to the app.

These have been tested working by many, including myself. It's not a bug, the transition just can leave residuals.

Finally, even if it were to be possible to make an uninstaller that removes it from everywhere, having an app that goes full rogue by scanning and deleting files on folders that don't belong to it (even if it's just the OCLP app itself) isn't a good way to go about it. Some may, for example, intentionally backup older OCLP versions.

 

[Jauso]

I am a documentation contributor of the project but not really a dev, anyway to give some insight:

What may be the issue why you were always launching old OCLP versions is trying to launch OCLP via Spotlight. Due to a change, OCLP puts an alias into "Applications" and as such Spotlight won't show it since it won't pickup aliases for some reason and will keep finding the older version(s) of the .app if they exist. Hence always launch via the alias in "Applications".

Basically, OCLP v2.3.0 deprecated the ".app.zip" package in favor of a new .pkg based installer method that existed for a while already but was an option. This new method always installs the app to "/Library/Application Support/Dortania" and puts an alias to "Applications", which ensures it will always be in a fixed location and all the mechanisms work. If you used the ".app.zip" method with 2.1.2 and extracted it to a random location (as in not into "Applications"), the updater/installer/uninstaller can't be aware of those locations and therefore cannot know to remove or replace them. You'll have to find and remove these yourself, as the updater will just make a new install to that previously mentioned location.

The uninstaller only works if the app exists in the aforementioned location, it again has no idea if an older app extracted from the .zip resides elsewhere on the system. The uninstaller was created to target the new method from the beginning, since the new method does more than just extracting the app, such as installing a PrivilegedHelperTool to avoid admin password spam in every section. As such the uninstaller has to make sure to remove those as well, in addition to the app.

These have been tested working by many, including myself. It's not a bug, the transition just can leave residuals.

Finally, even if it were to be possible to make an uninstaller that removes it from everywhere, having an app that goes full rogue by scanning and deleting files on folders that don't belong to it (even if it's just the OCLP app itself) isn't a good way to go about it. Some may, for example, intentionally backup older OCLP versions.

Interesting, i have some info to add.

I never did launch OCLP from spotlight (it is not really my thing to launch apps this way, i still have the windows habit of clicking the apps folder and selecting the app i want by mouse pointer), i always used the apps folder, and either launched it by the shortcut (as shown)

OR

i launched it from the app icon inside the OCLP folder inside the apps folder (and it seems that the 2.4.0 version does NOT have the folder here anymore (as you can see (or can't see)), so that has changed in 2.4.0)

both ways of launching still launched into 2.1.2 (although i cannot be 100% sure as this new info that you gave me above, i did not take it into consideration before as I did not know it, so I did not remember my past steps exactly), although if i had to guess i would say i launched OCLP many times by both ways while trying to "fix" this bug and i am 90% sure both ways still ended up opening 2.1.2 and not 2.4.0 (even though I installed it multiple times in the past).

with this new info, does your spotlight launch shortcut theory still apply?

as for the uninstaller app, i dont understand your explanation, but if it works i will take your word for it 👍. i just used the uninstaller app bc i thought it does something extra or different compared to dragging and dropping the OCLP folder into the trash, but it turns out since dragging+ dropping worked too so i won't ever need to use the uninstaller app in the future anyways.

 

[amaze1499]

Finally, even if it were to be possible to make an uninstaller that removes it from everywhere, having an app that goes full rogue by scanning and deleting files on folders that don't belong to it (even if it's just the OCLP app itself) isn't a good way to go about it. Some may, for example, intentionally backup older OCLP versions.

AppCleaner for Mac could achieve that.