Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Install macOS Monterey 12 MacBook Pro retina late 2013

chris1111

chris1111

macrumors 6502
Original poster
Jul 8, 2015
433
1,041
Montréal Canada
Update 23 April 2022
Support in Github only!
--------------------------------------------------------------------------------------------

How to install macOS Monterey on a MacBook Pro retina late 2013
Without patcher, without any kexts files. Genuine macOS booting with OpenCore SIP activate
Probably work on other Mac?

Guide ➤ Install macOS Monterey 12 MacBook Pro retina late 2013
For support open Issue: [New Issue]


If you are using OCLP, please post your comments on the subject to dedicate this effect, do not post here.
If you have a mac with are you using dual Graphics or any GPU other than the Intel Iris Pro Graphics I recommand to using OCLP and post your comments on the subject to dedicate this effect.
 
Last edited:
  • Like
Reactions: pippox0, dbgt, Tronstar and 2 others
Update Beta 5 perfectly :D
untitl35.png

Untitled.png
 
  • Like
Reactions: Tronstar and rezzo
this is great but can you do it without encore nd keep it all native? my 2015 MacBook 12 has all the drivers still available in Monterey its just an arbitrary cut off?

Thanks
 
  • Like
Reactions: chris1111
To achieve this would have to change a few things in the system.
Currently with only OC as bootloader without any kexts inject it is original untouch
 
chris1111 said:
Update Beta 5 perfectly :D
View attachment 1817518
View attachment 1817516
Click to expand...


Hi @chris1111,

Your solution worked for me. What I did:

1- Generated an EFI folder using OCLP 0.2.4;
2- Removed all Kext files from Kexts;
3- Added HfsPlus.efi on Drivers (OpenCanopy.efi, OpenRuntime.efi, and HfsPlus.efi);
4- Added CleanNvram.efi in Tools (BootKicker.efi, OpenShell.efi, and CleanNvram.efi);
5- Removed ALL PCI in <key> including the key for brcmfx-country from DeviceProperties in config.plist;
6- Fine tuned config.plist to reflect all my previous changes (spoofing a MacBookPro11,4).

I started by booting a CCC clone of my main internal SSD (Thunderbolt 2 Lacie SSD) and enrolling it in the Public Beta software program. I went from Public Beta 4 to Public Beta 5 using OTA and 2.54 GB download in Software Update.

I hope this helps someone else.

Thank you,
 
  • Like
Reactions: pippox0, Tronstar and chris1111
macpro_mid2014 said:
Hi @chris1111,

Your solution worked for me. What I did:

1- Generated an EFI folder using OCLP 0.2.4;
2- Removed all Kext files from Kexts;
3- Added HfsPlus.efi on Drivers (OpenCanopy.efi, OpenRuntime.efi, and HfsPlus.efi);
4- Added CleanNvram.efi in Tools (BootKicker.efi, OpenShell.efi, and CleanNvram.efi);
5- Removed ALL PCI in <key> including the key for brcmfx-country from DeviceProperties in config.plist;
6- Fine tuned config.plist to reflect all my previous changes (spoofing a MacBookPro11,4).

I started by booting a CCC clone of my main internal SSD (Thunderbolt 2 Lacie SSD) and enrolling it in the Public Beta software program. I went from Public Beta 4 to Public Beta 5 using OTA and 2.54 GB download in Software Update.

I hope this helps someone else.

Thank you,
Click to expand...
Yes OC is sufisant :cool:
 
  • Like
Reactions: macpro_mid2014
Thanks again for sharing Chris! This saves so much time, frustration and trial and error as I have the exact same MacBook Pro as well as others.

I just wonder why dortania opencore team on GitHub used a different account for the core package, inacidanthera.
As its probably the same opencore package used in the dortania account.
As far as I can see they share some developers so probably partly the same team.
Maybe they used different accounts to keep it more accessible by creating a distinction between corepackage and patcher?
 
Tronstar said:
Thanks again for sharing Chris! This saves so much time, frustration and trial and error as I have the exact same MacBook Pro as well as others.

I just wonder why dortania opencore team on GitHub used a different account for the core package, inacidanthera.
As its probably the same opencore package used in the dortania account.
As far as I can see they share some developers so probably partly the same team.
Maybe they used different accounts to keep it more accessible by creating a distinction between corepackage and patcher?
Click to expand...

In my opinion OCLP is a project totaly apart from OpenCore development and the OC developers are not really involved in this project, on my side it was very easy to arrive at this solution because I use OC on a lot of my Hackintosh
 
  • Like
Reactions: Tronstar and macpro_mid2014
In my opinion With the Flavours theme this is more beautyful then the original Mac boot
2018316149.png



22113038.png


Attaching theme Flavours

Update theme Flavours new Windows Disk Icon
22113038.png

attaching Windows.icns.zip.zip
 

Attachments

  • Flavours.zip
    521.7 KB · Views: 177
  • Windows.icns.zip
    11.7 KB · Views: 146
Last edited:
  • Like
Reactions: macpro_mid2014
Just wondering… Without OpenCore and native Big Sur install obviously it’s impossible to download the Monterey public beta via Apple’s system update because this MacBook isn’t supported anymore for macOS 12.
Do you think that it’s possible to use your approach using the BigSur installer instead of Monterey and afterwards upgrade the official way to the public beta?
As mentioned above all that’s needed for the system update to download macos12 public beta probably is making it appear as a 11,4 MacBook Pro?

And if this is possible, do you think installing OpenCore bootloader only in the existing native Big Sur will do the trick?

So technically i mean only replacing the regular EFI by OpenCore in a regular working Big Sur install.
 
  • Like
Reactions: macpro_mid2014
Tronstar said:
Just wondering… Without OpenCore and native Big Sur install obviously it’s impossible to download the Monterey public beta via Apple’s system update because this MacBook isn’t supported anymore for macOS 12.
Do you think that it’s possible to use your approach using the BigSur installer instead of Monterey and afterwards upgrade the official way to the public beta?
As mentioned above all that’s needed for the system update to download macos12 public beta probably is making it appear as a 11,4 MacBook Pro?

And if this is possible, do you think installing OpenCore bootloader only in the existing native Big Sur will do the trick?

So technically i mean only replacing the regular EFI by OpenCore in a regular working Big Sur install.
Click to expand...
I did not test from Big sur, as I mentioned I booted from an installation USB key
If you need the Install macOS Monterey Beta open this link


In my opinion it is much better to test a bootable USB key before, even if you boot into the macOS install without problem you could surely boot on your Big Sur and see if the update is available
 
  • Like
Reactions: macpro_mid2014
chris1111 said:
I did not test from Big sur, as I mentioned I booted from an installation USB key
If you need the Install macOS Monterey Beta open this link

In my opinion it is much better to test a bootable USB key before, even if you boot into the macOS install without problem you could surely boot on your Big Sur and see if the update is available
Click to expand...
Yes you are right, that makes sense. And thanks for the link.

So if you boot from the custom made USB key with the Opencore EFI on it and only use it to boot the regular BigSur install the opecore boot loader isn't installed and will probable only function as a bootpicker. Once BigSur is selected isn't the Apple Big Sur EFI loaded. I mean that's what I expect it to do.
Anyway.. I'll try it out and if it doesn't there is always your first approach with a clean install.
 
Last edited:
Tronstar said:
Yes you are right, that makes sense. And thanks for the link.

So if you boot from the custom made USB key with the Opencore EFI on it and only use it to boot the regular BigSur install the opecore boot loader isn't installed and will probable only function as a bootpicker. Once BigSur is selected isn't the Apple Big Sur EFI loaded. I mean that's what I expect it to do.
Anyway.. I'll try it out and if it doesn't there is always your first approach with a clean install.
Click to expand...

I started with a bootable Thunderbolt clone (CCC) of my internal SSD. Used a USB stick with the Monterey installer which I created using createinstallmedia.
Booted with the USB and installed Monterey over the original Big Sur system disk, without formating anything. After the installation, I can choose to boot into my internal Big Sur SSD or my Thunderbolt SSD.
All the original apps installed in my internal SSD are now also available in the Data partition of the Monterey system so I can have a look at what apps are working and what apps are still not working in Monterey.

Thanks
 
I almost forgot:

If you have a single SSD to test, I encourage you to get a spare to play with Monterey. There are some apps that are still not working properly in Monterey.

Also, I believe that you CAN update through Monterey using Software Update if you have Big Sur installed.

You can use this to enroll your Mac:

sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil enroll DeveloperSeed OR PublicSeed

sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil gives you a list of options.
 
  • Like
Reactions: chris1111
Simple way to install Monterey on Retina MBP Late 2013 and get native updates is to :

- Create a USB Installer ( Any Beta Version ).
- Patch the USB with OC.
- Boot from USB Installer and install Monterey.
- Patch internal drive.
- Done.

Retina MBP Late 2013 does not need any additional drivers patching.
 
  • Like
Reactions: Sanjay.radia, Tronstar and macpro_mid2014
Tronstar said:
Yes you are right, that makes sense. And thanks for the link.

So if you boot from the custom made USB key with the Opencore EFI on it and only use it to boot the regular BigSur install the opecore boot loader isn't installed and will probable only function as a bootpicker. Once BigSur is selected isn't the Apple Big Sur EFI loaded. I mean that's what I expect it to do.
Anyway.. I'll try it out and if it doesn't there is always your first approach with a clean install.
Click to expand...

OpenCore is as much 'installed' if you boot it from a USB drive as from an internal drive.

OC loads up and injects certain hooks and patches (whatever you've configured it to, which will vary a lot depending on what is required, from machine to machine). It injects all this as it is loading, and it never replaces the firmware on a Mac. E.g. On Macs which have their own bootpicker (all newer ones) that is always still there, and can be accessed before OC ever starts by holding down the ALT/OPT key. But using OC you can end up installing a newer macOS which the builtin EFI/bootpicker alone will refuse to start. HTH. :)
 
Last edited:
  • Like
Reactions: Tronstar and chris1111
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back