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.
@Potsdamer, @Macschrauber , @Ausdauersportler

- Are the tools currently discussed here, well, safe? Are they open-source, and if so, has anyone knowledgeable examined them for malicious code?

The question is ernst gemeint serious ;-)
Hmm, what do you expect the answers? ;)

The 1st wiki post of this thread already lists the Gibhub project for OCLP download:

OCLP derives heavily from Opencore which has its own Gibhub project page :

From the developers, would they say yes or no to your question? :oops:

From the users here already enjoying the OCLP for their iMac, would they say yes or no to your question ? 🤔

It is good that you have a doubtful mind and cautious on anything downloaded from Internet.👏
No tools in the public is completely "safe" in a sense.😲
Even apps in Google Play store and iOX app store, carefully screened by expert teams, have apps with malicious code detected every now and then and got banned.😔

Would you believe a single poster here saying that he/she has examined all the million lines of code and say this is "safe"?🧐

The community is built on trust. You can never be sure whether some malicious intent is present.
You have to assess yourself sometimes by your own instinct and the thousands of posts here for their feedback.🤗

So, have you searched thru this thread to look for such report ?😊
 
Hmm, what do you expect the answers? ;)

The 1st wiki post of this thread already lists the Gibhub project for OCLP download:

OCLP derives heavily from Opencore which has its own Gibhub project page :

From the developers, would they say yes or no to your question? :oops:

From the users here already enjoying the OCLP for their iMac, would they say yes or no to your question ? 🤔

It is good that you have a doubtful mind and cautious on anything downloaded from Internet.👏
No tools in the public is completely "safe" in a sense.😲
Even apps in Google Play store and iOX app store, carefully screened by expert teams, have apps with malicious code detected every now and then and got banned.😔

Would you believe a single poster here saying that he/she has examined all the million lines of code and say this is "safe"?🧐

The community is built on trust. You can never be sure whether some malicious intent is present.
You have to assess yourself sometimes by your own instinct and the thousands of posts here for their feedback.🤗

So, have you searched thru this thread to look for such report ?😊
Well, mate, what about AOSP, which has been examined - and more often than not at that - by users and experts alike? ;-)
 
@Potsdamer, @Macschrauber , @Ausdauersportler

- Are the tools currently discussed here, well, safe? Are they open-source, and if so, has anyone knowledgeable examined them for malicious code?

The question is ernst gemeint serious ;-)
About the open-source: You could have checked the download links to find out the obvious yourself. This first question makes it really hard to take the next one serious.

According to which test and results you will accept safety of code? This question is so general no answer can be given.

Yes, I am serious :)

Apple makes a lot of efforts to save guard the basic system against any form of tampering (crypto seals) and our general approach is to achieve exactly this tampering to make older systems work (especially the ones not having a metal capable GPU) again.

For all system using a metal GPU *no* changes on disk are needed. Check the docs of OCLP and OC what and how this can be achieved (in memory injection of changes, not system disk patching). As one can use SecureBootModel and FileVault with those Macs I would claim it is pretty sure compared to all other patcher approaches we had so far.

In fact OCLP is not a patcher!

P.S.: 6 minutes remaining installing Monterey Beta 1 on my iMac11,3 with AMD RX480 mobile
 
About the open-source: You could have checked the download links to find out the obvious yourself. This first question makes it really hard to take the next one serious.

According to which test and results you will accept safety of code? This question is so general no answer can be given.

Yes, I am serious :)

Apple makes a lot of efforts to save guard the basic system against any form of tampering (crypto seals) and our general approach is to achieve exactly this tampering to make older systems work (especially the ones not having a metal capable GPU) again.

For all system using a metal GPU *no* changes on disk are needed. Check the docs of OCLP and OC what and how this can be achieved (in memory injection of changes, not system disk patching). As one can use SecureBootModel and FileVault with those Macs I would claim it is pretty sure compared to all other patcher approaches we had so far.

In fact OCLP is not a patcher!

P.S.: 6 minutes remaining installing Monterey Beta 1 on my iMac11,3 with AMD RX480 mobile
Very informative, thanks a lot for taking your time to write this out! Is it actually possible to instal Big Sur / Monterey on removable media using this method? A dual-/triple-boot of sorts?
 
just a quick note for OCLP 0.1.6 and OC 0.70

OCLP built a package with OC 0.7.0 what was not able to install or run Big Sur 11.2.3 on a Mac Pro 5.1

On my test rig the OCLP Package 0.1.5 I built last week (with OC 0.6.9) installed without any problems.


its 3 A.M. here so I need some sleep now, no time for more details, just want to give a little hint before someone else steps into the same trap :)
I'm running Big Sur 11.2.3 successfully with OCLP 0.1.6 and OC 0.7.0 on a MacPro5,1. My machine details are in the signature if you want to compare to your setup.

I did have 11.2.3 already installed so I haven't tried any OS installs lately.
 
  • Like
Reactions: K two
P.S.: 6 minutes remaining installing Monterey Beta 1 on my iMac11,3 with AMD RX480 mobile

So... it never was installed? ;)
I tried on a 2012 Mac Mini, installed yesterday late at night, didn't want to wait for it to finished, It hanged I thought.
Looked at it again for a minute before I went off this morning, shut it off.
Now, I figured out it goes all the way up to the login screen but just before it loops.
Something ado with AppleKeystore numbers, operation failed more numbers.blah blah.
Screenshot.jpg
 
Last edited:
  • Like
Reactions: Tockman
Very informative, thanks a lot for taking your time to write this out! Is it actually possible to instal Big Sur / Monterey on removable media using this method? A dual-/triple-boot of sorts?

Sure you can install on removable media!

I've just put Monterey on an external SSD rather than the main drive on my MBP10,2 - and glad I did, since it's not ready for prime time yet. (Which ofc is only fair - not to say true by definition! - given that it is the very first beta.)
 
  • Like
Reactions: AlexMorello
Sure you can install on removable media!

I've just put Monterey on an external SSD rather than the main drive on my MBP10,2 - and glad I did, since it's not ready for prime time yet. (Which ofc is only fair - not to say true by definition! - given that it is the very first beta.)
 
Thanks mate!... i have another question, what big sur version can i install on the whitebook?, can i install the latest version (11.4)? or what version do you suggest mate, what version is the most stable with the OpenCore patches on the 7.1 whitebook (mid 2010 MacBook), thanks for the help!
 
  • Like
Reactions: K two
How did you run the installation? I tried with BKE's patcher but it did not work, even after renaming USB drive and target system.

I'm not quite sure which bits of your iMac13,1 will and won't work without patches and kexts - the Wi-Fi/Bluetooth card and the graphics card are the things you'll have to look up. But if you've got a machine which can more or less run Monterey (or Bug Sur) without any additional drivers, then you can actually follow the instructions from here https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/ - more or less!

You should not need to modify their basic sample config.plist file at all, except change the value of SMBIOS/PlatformFeature to -1 instead of 4294967295 (-1 picks up the OEM value from your machine, and will work better for you than their custom value designed for an older Mac), and (the key thing to make the unsupported OS start) change SMBIOS/BoardProduct to the Mac-xxxxxx string of a similar supported Mac - e.g. Mac-A369DDC4E67F1C45 (for iMac16,1) for you.

All you're trying to do is set up a working OpenCore installation, using that config.plist. If you can set that up, then just always boot through that when accessing an unsupported OS. Btw Monterey is not (IMHO) ready for use on a main machine at this early beta stage. You can install on an external SSD to test.
 
I'm not quite sure which bits of your iMac13,1 will and won't work without patches and kexts - the Wi-Fi/Bluetooth card and the graphics card are the things you'll have to look up. But if you've got a machine which can more or less run Monterey (or Bug Sur) without any additional drivers, then you can actually follow the instructions from here https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/ - more or less!

You should not need to modify their basic sample config.plist file at all, except change the value of SMBIOS/PlatformFeature to -1 instead of 4294967295 (-1 picks up the OEM value from your machine, and will work better for you than their custom value designed for an older Mac), and (the key thing to make the unsupported OS start) change SMBIOS/BoardProduct to the Mac-xxxxxx string of a similar supported Mac - e.g. Mac-A369DDC4E67F1C45 (for iMac16,1) for you.

All you're trying to do is set up a working OpenCore installation, using that config.plist. If you can set that up, then just always boot through that when accessing an unsupported OS. Btw Monterey is not (IMHO) ready for use on a main machine at this early beta stage. You can install on an external SSD to test.

While I think the above will work - and you did ask how I'm installing it - arguably simpler (and at least more supported) might be: https://forums.macrumors.com/thread...unsupported-macs-thread.2299557/post-29992221
 
Thanks mate!... i have another question, what big sur version can i install on the whitebook?, can i install the latest version (11.4)? or what version do you suggest mate, what version is the most stable with the OpenCore patches on the 7.1 whitebook (mid 2010 MacBook), thanks for the help!
Seems to be 11.2.3 is a good version to start and OTA update from there. You can D/L any release version of macOS from Apple with this tool. https://github.com/corpnewt/gibMacOS 👀
 
  • Like
Reactions: CharlieRuiz97
If I get flamed, I understand.

Posts that discuss macOS Monterey in this thread should be moved to the following thread:


Let's not confuse the natives. Thank you.
 
just a quick note for OCLP 0.1.6 and OC 0.70

OCLP built a package with OC 0.7.0 what was not able to install or run Big Sur 11.2.3 on a Mac Pro 5.1

On my test rig the OCLP Package 0.1.5 I built last week (with OC 0.6.9) installed without any problems.


its 3 A.M. here so I need some sleep now, no time for more details, just want to give a little hint before someone else steps into the same trap :)
thanks @Macschrauber
I've spent the whole day today trying to install Big Sur with oclp 0.1.6, continually hanging.
I'm downloading 11.2.3 and will try with OCLP 0.1.5.
hope it gets my Mac Pro (4.1->5.1) going again.
 
Just upgraded my mid 2012 MBP from catalina with oclp 0.1.6. More reboots than I expected(slight concern at one point) but finally the big sur welcome etc appeared etc...

Many thanks to everyone who put the work into this.
 
Can you upload the 0.1.5 EFI and the 0.1.6 EFI somewhere and post a link?
@Macschrauber @bbb555
I have somewhat similar issue with the imac 12,2 using 0clp 0.1.6 and big sur installer doesnot proceed and gets stuck just before apple logo progress bar. I tried both using oclp installed in internal drive as well as used with usb but no luck. Even posted verbrose screenshot.

6AA11B14-419E-4B8A-9C2F-F3C7951C82AA.jpeg
 
I have somewhat similar issue with the imac 12,2 using 0clp 0.1.6 and big sur installer doesnot proceed and gets stuck just before apple logo progress bar. I tried both using oclp installed in internal drive as well as used with usb but no luck. Even posted verbrose screenshot.

View attachment 1790066
Currently this happens with 0.1.6 even on an iMac11,3 startup up the Monterey installer.

At which stage did you take this picture? After first or second reboot or when basically starting up the installer? If this happened after copying and after the first reboot just power off the system and reboot. It should recover from that and picking up the installation process where it hung before.
 
i have read the documentation.
i'm not very good at these things so i was wondering if anyone had experienced this before.

thanks anyway.
 
If I get flamed, I understand.

Posts that discuss macOS Monterey in this thread should be moved to the following thread:


Let's not confuse the natives. Thank you.
I am guilty...I admit:oops:

You are right, should've looked for the new Monterey on unsupported macs thread.👍
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.