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.
Stock Apple SSDs or have they been upgraded?

Hi, it's the stock Apple SSD from new. I think it's actually considered a 500GB and not a 512, but yes it's the stock SSD.

Takes well over a minute to boot up (I'll time it next time) and when the battery runs out and it goes to sleep, waking it is a nightmare...
 
Last edited:
I have a Monterey (12.3.1) up and running on my MacPro3,1 (patched to a MacPro 5,1). I did that on a usual HD-Drive for testing. On this installation, I tried to run everything I need. And it looks like, I can use it well. So i configured everything.

But, because of the slow HD, I would like to copy this installation to a M2-SSD because of speed. I tried to do it the simple way with CCC, but i can not boot into this M2-SSD.

What i tried: I use OCLP to rebuild the patch via "Build and Install OpenCore" and use the EFI of the M2-SSD. But it didn't work. I also reset the NVRAM, still the same.

Do I need to make a dummy installation of Monterey plain to the M2-SSD via a USB-Drive? And after finishing the base, can I copy my slow but fine already configured Monterey-Installation over?

Thanks for helping in advanced!
 
Hhmmm, i can not boot up my old, but necessary Mojave on my M2-SSD. Any hints?
Depending on the OCLP spoofing you might add the -no_compability_check to the OCLP boot-args or try to boot Mojave without OLCP (which I would prefer when you need the feeling of a totally untouched (but not any longer supported) macOS Mojave.

Edit: Thought he meant a MacPro5,1 - and there is no MacPro3,1 patched to 5,1 :)
 
Last edited:
I'm pretty sure you can just install Mojave on an external drive, even a thumb drive, and boot from there by holding down CMD or selecting startup disk in Preferences.
I have a necessary installation of Mojave already, but i can't boot it. Before i test the OCLP installation on an old HD i removed my M2-SSD with the Mojave setup for safety. But after i put the drive back, it appears as a startup drive but did not boot up. Either after selecting it with the boot manager or in the control panel.
 
Well, this is my first message here, and ironically, I arrived here not searching on macrumors but from DuckDuckGo (my search engine) and Reddit. But I guess we all end up here xD

I was considering using the patcher when I upgrade to Monterey to enable Universal Control, or just use Monterey without the feature enabled. I’m not sure what to do, and that’s why I came here to ask:

1. About the safety of this patch. It is a very low level patch, and if it carries anything malicious, it will be stuck at EFI/BIOS level. I guess this is Open Source? Still, is this well reviewed by peers to be sure it doesn’t leak or harvest data, installs key loggers, or anything else?

2. I have a third party SSD installed, with the command “TRIMFORCE ENABLE” to enable TRIM on my SSD. Can this patcher make any mess on my system? Can I experience glitches that make me lose important data?

If the answer to any of the questions above is “no, it isn’t 100% safe” then I won’t use it. I repeat, that I can install Monterey perfectly on my 2014 Mac mini, so no problem, but it would be nice to have Universal Control as I have a 2018 iPad Pro, and I personally suggested/explained/asked for this feature to Craig 15 months before the announcement, and I totally felt that this was a direct response to my situation, explained on my letter to Craig.

Anyways, if this is just 80% safe, I think I will wait for my next M2 or M3 Mac mini to enjoy this feature. But I wanted to ask here first.

Thank you, if this was already answered on any of the 240 pages, I apologize for not reading all of them.

***********
Its been a while since ive posted. I think the last time I posted any issues was with the 12.3 betas when Universal control was first released and it didn't work on my MacBook Pro 2015 even though it was a supported platform.

Thanks to the amazing work by the dev's of OCLP we discovered these were disabled on purpose, so to get round this I simply patched my MBP with OCLP as a 2016 MacBook Pro. job done.

Since 2.14 has been doing the rounds, this is no longer needed on my Map and I'm a happy bunny.

Im excited for WWDC 2022 when we may see the next MacOS version and look forward to the new thread "MacOS 12 'insert name here' on unsupported Macs"

This is just a HUGE thank you to everyone involved in this thread, the OCLP team and for all the people here way more clever than me who have helped us all out over this last year to keep our older (but still massively useable) iMac. MacBooks etc running the latest and greatest OS in the world.
Maybe you meant “MacOS 13 on unsupported macs” :p
 
Well, this is my first message here, and ironically, I arrived here not searching on macrumors but from DuckDuckGo (my search engine) and Reddit. But I guess we all end up here xD

I was considering using the patcher when I upgrade to Monterey to enable Universal Control, or just use Monterey without the feature enabled. I’m not sure what to do, and that’s why I came here to ask:

1. About the safety of this patch. It is a very low level patch, and if it carries anything malicious, it will be stuck at EFI/BIOS level. I guess this is Open Source? Still, is this well reviewed by peers to be sure it doesn’t leak or harvest data, installs key loggers, or anything else?

2. I have a third party SSD installed, with the command “TRIMFORCE ENABLE” to enable TRIM on my SSD. Can this patcher make any mess on my system? Can I experience glitches that make me lose important data?

If the answer to any of the questions above is “no, it isn’t 100% safe” then I won’t use it. I repeat, that I can install Monterey perfectly on my 2014 Mac mini, so no problem, but it would be nice to have Universal Control as I have a 2018 iPad Pro, and I personally suggested/explained/asked for this feature to Craig 15 months before the announcement, and I totally felt that this was a direct response to my situation, explained on my letter to Craig.

Anyways, if this is just 80% safe, I think I will wait for my next M2 or M3 Mac mini to enjoy this feature. But I wanted to ask here first.

Thank you, if this was already answered on any of the 240 pages, I apologize for not reading all of them.

***********

Maybe you meant “MacOS 13 on unsupported macs” :p
No, it is not 100% save.

Watch the great movie Don‘t look up! to understand what I mean when writing about 100%.

Have you ever heard of the NSA? They have already installed a backdoor to your system, regardless which macOS version and which Mac you have. And joining social networks makes it superfluous to harvest data from your system, you are already posting all interesting facts out by your choice of topics and networks.

Visit the OLCP GitHub page to get a better understanding of the software yourself. You may even find the source code there.
 
And joining social networks makes it superfluous to harvest data from your system, you are already posting all interesting facts out by your choice of topics and networks.

Phew! Luckily I‘m not on any social network, and I am very cautious about what I install on my mac. I don’t use anything from Google, Facebook or Microsoft. And I do use Apple products and services because I trust them and their services. We all have to draw a line, and make concessions, and some people make more concessions than others. You see, things aren’t black or white, going totally offline or throwing my ID and pictures to the internet for everyone to know where I live etc. Those are 2 extreme cases, and most of us are in between those extreme points. In my case, I’m closer to the privacy extreme than to the “public profile” or influencer one. That’s why I’m asking.


Visit the OLCP GitHub page to get a better understanding of the software yourself. You may even find the source code there.

Did you think I was going to come here to ask without reading the README on GitHub? I’ve done it, and I haven’t seen how the patcher works, and to what extent it modifies my macs EFI in case I’m runnign Monterey natively and just want to enable Universal Control. At this point, I’m not sure how it works on native Monterey installs, if it just modifies the kexts, or if it flashes the EFI.

And no, I cannot read the source code because I’m not IT and I don’t know coding, that’s why I came here in the first place.

Watch the great movie Don‘t look up!

Great movie indeed.

EDIT: Searching a bit more, I stumbled upon this website: https://dortania.github.io/OpenCore-Legacy-Patcher/HOW.html

There is a diagram of every step that the patched mac makes in order to boot on an unsupported macOS. However, what I’d like to know, is if all that process is the same on a native Monterey install that has been patched just to enable Mission Control.
 
Last edited:
Phew! Luckily I‘m not on any social network, and I am very cautious about what I install on my mac. I don’t use anything from Google, Facebook or Microsoft. And I do use Apple products and services because I trust them and their services. We all have to draw a line, and make concessions, and some people make more concessions than others. You see, things aren’t black or white, going totally offline or throwing my ID and pictures to the internet for everyone to know where I live etc. Those are 2 extreme cases, and most of us are in between those extreme points. In my case, I’m closer to the privacy extreme than to the “public profile” or influencer one. That’s why I’m asking.




Did you think I was going to come here to ask without reading the README on GitHub? I’ve done it, and I haven’t seen how the patcher works, and to what extent it modifies my macs EFI in case I’m runnign Monterey natively and just want to enable Universal Control. At this point, I’m not sure how it works on native Monterey installs, if it just modifies the kexts, or if it flashes the EFI.

And no, I cannot read the source code because I’m not IT and I don’t know coding, that’s why I came here in the first place.



Great movie indeed.

EDIT: Searching a bit more, I stumbled upon this website: https://dortania.github.io/OpenCore-Legacy-Patcher/HOW.html

There is a diagram of every step that the patched mac makes in order to boot on an unsupported macOS. However, what I’d like to know, is if all that process is the same on a native Monterey install that has been patched just to enable Mission Control.
You cannot read the source, nor you have the skills to understand the technological impacts by using the software and yet you are asking for 100% safety. You are investing your hope into unknown people giving you a better feeling when posting here? This becomes more and more ridiculous.

You still not got the message. There is no 100% safety, you have already joined this social network and presumably reddit, too. If you are asking for 100%, YOU are asking for black and white. I tried to explain you would have to accept the grey - even when using the (native) Apple products you trust so much.

Apple is an U.S. based company. Unlike many people living in the land of the free believe trade is not free in the U.S. The U.S. government has to grant the right to export goods and technology , which gives them a great angle on every company. Now you can believe naively in the white Apple refusing all wishes came in through NSA or home land security or other agencies while all other companies are black deliberately harvesting your important data.

On the first post of the thread the main author of OCLP already put a disclaimer:

Apple and all patch developers are not responsible for any potential damage or data loss caused by using pre-release software or unofficial support patches. Please use at your own risk.
 
You cannot read the source, nor you have the skills to understand the technological impacts by using the software and yet you are asking for 100% safety. You are investing your hope into unknown people giving you a better feeling when posting here? This becomes more and more ridiculous.

You still not got the message. There is no 100% safety, you have already joined this social network and presumably reddit, too. If you are asking for 100%, YOU are asking for black and white. I tried to explain you would have to accept the grey - even when using the (native) Apple products you trust so much.

Apple is an U.S. based company. Unlike many people living in the land of the free believe trade is not free in the U.S. The U.S. government has to grant the right to export goods and technology , which gives them a great angle on every company. Now you can believe naively in the white Apple refusing all wishes came in through NSA or home land security or other agencies while all other companies are black deliberately harvesting your important data.

On the first post of the thread the main author of OCLP already put a disclaimer:

Apple and all patch developers are not responsible for any potential damage or data loss caused by using pre-release software or unofficial support patches. Please use at your own risk.

You say my messages on this thread are becoming more and more ridiculous, and I say your messages towards me are becoming more and more unrespectful. And I don’t care if you’re part of the development team of this patch, a contributor, or just a tester; the way you’re talking to me, a kind neighbor of this forum who is just politely asking to people more versed on this subject, is pretty unpleasant. I don’t care if you’re a programmer, a former CPU designer, or the most brilliant person on the planet: Respecting others and being kind to others is the baseline for me.

This will probably be my last message on this thread, but let me tell you that this is not the way to address someone who just, without the proper knowledge, asks about the safety, security, and the possible corruption and glitches it can cause on a TRIMmed SSD etc. Since when someone asking is subject of this kind of attacks? I can’t believe it. Let me remind you that, at this side of the screen there is another person too. Who might be right or wrong, but that is secondary when you employ that aggressive tone.

And no, I’m not asking more questions, because at this point I’ve discarded installing the patch and will go with the native install of Monterey, Universal Control can wait, but in hopes that other ignorant people -just like myself- asking here get treated with proper respect, I’m writing this message.

Now, to the proper reply.

You cannot read the source, nor you have the skills to understand the technological impacts by using the software and yet you are asking for 100% safety. You are investing your hope into unknown people giving you a better feeling when posting here? This becomes more and more ridiculous.

Yes; It is called asking help to the community. Maybe some forum user doesn’t know if X app (lets say, Fortnite) works well under iOS 15.4.1, and I happen to have it installed and after the update, I can tell him: “go ahead, you can update, Fortnite works well“. That’s the spirit of this great community, helping each other with topics and subjects others don’t know.

And of course, if the official thread on Macrumors, where Dosdude and other users and contributors to the project participate, and can review the code, tell me that “it works this way, or that way, it is safe because this or that”, or “it needs to flash the EFI, so don’t do it if you’re not sure”, or “don‘t worry, to enable Mission Control you just need to patch some kexts, so there are no security implications”, I will believe them, because I trust this community I’ve been on for 10 years.

You still not got the message. There is no 100% safety, you have already joined this social network and presumably reddit, too. If you are asking for 100%, YOU are asking for black and white. I tried to explain you would have to accept the grey - even when using the (native) Apple products you trust so much.

I will give you this one, because yes, when asking for 100% safety, I was going to that extreme, and as me and you said, we need to accept we’re moving on the grey area. So in that case, asking literally for a 100% was my mistake. It’s just that I wanted to emphasize how much I valued the safety on a project like this one. Actually, there were other technical questions but apparently those didn’t get your attention. But doesn’t matter, I’ve already decided to not use it.

Apple is an U.S. based company. Unlike many people living in the land of the free believe trade is not free in the U.S. The U.S. government has to grant the right to export goods and technology , which gives them a great angle on every company. Now you can believe naively in the white Apple refusing all wishes came in through NSA or home land security or other agencies while all other companies are black deliberately harvesting your important data.

And yeah, I’m probably being pretty naive here, but among all the companies, and until Apple proves to be another one to be untrusted, I will keep using their services. It’s not that I disagree with you, mind you, but if I have to choose a company to rely on, I choose the one who has sold me privacy, until I read news that break my trust in Apple.

And going back to the topic, I usually trust open source software. I actually love open source software! But it is not the same a mere app that installs on your system, often times without even asking for system privileges, than a software that (from what I understood) flashes or patches the booting partition of the mac. That’s lower level, if I’m not mistaken (and if I’m mistaken, you’re free to say so, but I’d ask you to be less aggressive).

On the first post of the thread the main author of OCLP already put a disclaimer:

Apple and all patch developers are not responsible for any potential damage or data loss caused by using pre-release software or unofficial support patches. Please use at your own risk.

Totally understandable. That’s why in the first place I came here to merely ask about my doubts (something completely legitimate), and in the second place decided to not install it.

EDIT: unpleasant instead of disgusting because I’m not a native speaker and the original word didn’t fit what I intended to say, nor the tone of it.
 
Last edited:
1. About the safety of this patch. It is a very low level patch, and if it carries anything malicious, it will be stuck at EFI/BIOS level.
OpenCore does not make permanent changes to EFI/BIOS. That would be a firmware update which people have done to add features like booting from NVMe. But OpenCore can load drivers from disk so that is unnecessary.

OpenCore is usually installed to a EFI partition of a disk. You can easily remove OpenCore by deleting the files it puts there, restarting, and selecting a new default boot option.

OpenCore patches the kernel and kexts in memory only. They are unchanged on disk. The Lilu kext and its plugins can also do similar patches to the kernel and kexts and also apps - all in memory with no permanent changes.

I guess this is Open Source? Still, is this well reviewed by peers to be sure it doesn’t leak or harvest data, installs key loggers, or anything else?
Yes. It's all open source. Thousands of people have used it. Hundreds of people have looked at the source. Dozens have contributed to the source. It would be difficult to hide anything malicious.

2. I have a third party SSD installed, with the command “TRIMFORCE ENABLE” to enable TRIM on my SSD. Can this patcher make any mess on my system? Can I experience glitches that make me lose important data?
I haven't used trimforce enable. OpenCore has some trim related options. I don't know how they relate.

If the answer to any of the questions above is “no, it isn’t 100% safe” then I won’t use it. I repeat, that I can install Monterey perfectly on my 2014 Mac mini, so no problem, but it would be nice to have Universal Control as I have a 2018 iPad Pro, and I personally suggested/explained/asked for this feature to Craig 15 months before the announcement, and I totally felt that this was a direct response to my situation, explained on my letter to Craig.
I use OpenCore on my Mac mini 2018 for some features (loading Lilu and WhateverGreen for some GPU experiments). Basically, you can turn off a lot of stuff in OpenCore except the stuff that provides the patch that you want to use.
 
OpenCore does not make permanent changes to EFI/BIOS. That would be a firmware update which people have done to add features like booting from NVMe. But OpenCore can load drivers from disk so that is unnecessary.

OpenCore is usually installed to a EFI partition of a disk. You can easily remove OpenCore by deleting the files it puts there, restarting, and selecting a new default boot option.

OpenCore patches the kernel and kexts in memory only. They are unchanged on disk. The Lilu kext and its plugins can also do similar patches to the kernel and kexts and also apps - all in memory with no permanent changes.


Yes. It's all open source. Thousands of people have used it. Hundreds of people have looked at the source. Dozens have contributed to the source. It would be difficult to hide anything malicious.


I haven't used trimforce enable. OpenCore has some trim related options. I don't know how they relate.


I use OpenCore on my Mac mini 2018 for some features (loading Lilu and WhateverGreen for some GPU experiments). Basically, you can turn off a lot of stuff in OpenCore except the stuff that provides the patch that you want to use.

Thank you for such a kind, comprehensive and accurate answer.

My main doubt was (and is) if the patcher works the same way regardless of having an unsupported mac or a Monterey supported mac. Because most of the users and experiences I’m reading, use it in order to run the latest macOS on unsupported mac hardware (and that’s great, many thanks to the team that makes it possible), but I was wondering if using it on an officially supported hardware made the process different. In order to, for example, make the system believe this is a 2018 Mac mini instead of a 2014, to enable the UC. But, now that I think about it, it’s the same thing as making the system believe it is a Monterey supported model.

So, yeah, I guess the process is the same regardless of it being a Monterey supported hardware or not, if the feature you want to enable is restricted by Apple, you have to make the system believe it is a more modern hardware. Shame on Apple for doing this, by the way.

Again, thank you so much, I will think about it, but I’ve read about some glitches and reboots, and right now I rather have a rock-stable system than enjoying Mission Control, specially having a third party SSD with the TRIMFORCE command enabled.
 
I have a necessary installation of Mojave already, but i can't boot it. Before i test the OCLP installation on an old HD i removed my M2-SSD with the Mojave setup for safety. But after i put the drive back, it appears as a startup drive but did not boot up. Either after selecting it with the boot manager or in the control panel.
Try this?

 
Totally understandable. That’s why in the first place I came here to merely ask about my doubts (something completely legitimate), and in the second place decided to not install it.

EDIT: unpleasant instead of disgusting because I’m not a native speaker and the original word didn’t fit what I intended to say, nor the tone of it.
Well, well! I have learned that people tend to shoot the messanger when the message does not suit their feelings. Feelings are a big big hurdle to jump over when making scientific or facts based decisions. The whole world struggles with this. So you are not alone.

To add some data points to your 100% safety quest:

1. While OCLP is in fact based on OpenCore it makes persistent changes to the root volume of an Mac when necessary. This is valid for the vast majority of systems here (literally all pre 2014 models).

2. GitHub is owned by Microsoft, a company on your personal blacklist?

3. Even when a system will not be patched on disk the whole idea of OpenCore is basically replacing software made by Apple originally and intending to work on Monterey/Big Sur with modified or different software (in memory) to achieve a different functionality. You can do anything with this approach.

4. Any, and I say any website on the planet can be completely captured and you will (with limited technical skills) not be able to detect this and download software from it. So there is again no 100% safety. Countries already have or start to build military forces to fight this internet or data war.

5. About near future: Apple dropped hardware support in the past, which is not a shame but a business decision in a world ruled by money transactions, only. You will experience with the advent of macOS 13 another round of this. So be prepared to see your still supported (and not root volume patched) system moving into the category described above.

About the 100%:
- Look up the scene where the scientist try to convince the female president of the U.S. to stop the astroid.
- To my limited knowledge I currently believe there is only a single thing for sure at the very end: We are going to die in some points in time.
- If you want your personal data kept safe (close, but only close to 100%) do not store it on an device connected to the internet ever.
 
Last edited:
OSs older than BigSur will not run on the Silicon Macs - they won't run as Virtual Machines either under Parallels or VM Fusion; not even with UTM.
Because that would be a emulation. Parallels, Fusion, etc, are for virtualize
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.