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

macpro_mid2014 said:
When you compile OC, it generates the folder structure with Kexts on Kext folder and everything else.

The goal here is to run OC without any Kexts because these types of computers (2013/2014 MBP/A) don't need any special kext to run Monterey natively.

I think that with the death of Kepler GPUs in Monterey, one can still benefit from this thread by injecting ONLY the appropriate kext in the kext folder (root patch) + modify the config.plist file appropriately and get rid of all the other Kexts generated by OC
Click to expand...
Thanks again for sharing! Yes this will be my approach as well. Just the necessities, nothing else.

Does yours have the dedicated gpu as well?
 
  • Like
Reactions: macpro_mid2014
chris1111 said:
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? Please confirm this solution if its work for you
Confirm works on MacBook Pro (Mid 2014)

Download files ➤ EFI Monterey 12
Credit: Acidanthera
Click to expand...
Hi Chris, I'm comparing your EFI with the one from macpro_mid2014.

I see you have more files in Drivers folder: HfsPlus.efi < is there a reason why you'd included this?

And in Tools folder: OpenShell.efi < what do you use this one for?

Thanks!
 
Tronstar said:
Hi Chris, I'm comparing your EFI with the one from macpro_mid2014.

I see you have more files in Drivers folder: HfsPlus.efi < is there a reason why you'd included this?

And in Tools folder: OpenShell.efi < what do you use this one for?

Thanks!
Click to expand...

My reasoning while choosing the EFI files in my installation (from https://dortania.github.io/OpenCore-Install-Guide/):

HfsPlus.efi - that might be needed for Hackintoshs only? I guess the MBP11,2 Firmware will recognize the HFS+ partitions automatically (native support).

OpenCanopy.efi - So I can run chris1111 beautiful screens.

OpenRuntime.efiRequired Required for proper operation

ClearNVRAM.efi - following this discussion, I think it is not required either. (https://www.tonymacx86.com/threads/cleannvram-vs-resetnvram-in-opencore-0-7-0-a-question.313679/)
 
Just wondering, how does it register with your apple-id, any problems there? And when you spoof the 11,4 how does it appear in your Apple ID device list as 11,2?

As I have one with the dGPU 11,3, I came across this post.
it appears that it’ll boot even without OpenCore.


Post in thread 'macOS 12 Monterey on Unsupported Macs Thread'
https://forums.macrumors.com/thread...unsupported-macs-thread.2299557/post-30087893

ill try as soon as release is final!
 
Last edited:
  • Like
Reactions: rezzo and macpro_mid2014
Just installed the Monterey 12.0.1 without issues...
Tronstar said:
Just wondering, how does it register with your apple-id, any problems there? And when you spoof the 11,4 how does it appear in your Apple ID device list as 11,2?

As I have one with the dGPU 11,3, I came across this post.
it appears that it’ll boot even without OpenCore.


Post in thread 'macOS 12 Monterey on Unsupported Macs Thread'
https://forums.macrumors.com/thread...unsupported-macs-thread.2299557/post-30087893

ill try as soon as release is final!
Click to expand...
That is great!! I will do that too! Thank you for sharing... I regularly read that thread, but I must have missed the post...
 
Tronstar said:
Hi Chris, I'm comparing your EFI with the one from macpro_mid2014.

I see you have more files in Drivers folder: HfsPlus.efi < is there a reason why you'd included this?

And in Tools folder: OpenShell.efi < what do you use this one for?

Thanks!
Click to expand...
Only CleanNvram.efi is activated
HfsPlus.efi is for HFS+J volume if you have it and without this driver OC not see USB Create install Media
 
  • Like
Reactions: Tronstar
Update 12.0.1 without any issue
Screen Shot 2021-10-18 at 7.35.04 PM.png
 
  • Like
Reactions: Tronstar, macpro_mid2014 and rezzo
Last edited:
DmitryZ said:
Hi. Does sleep/hibernation work normally for you? Cause I have macBook 11.2 with Monterey 12.0.1 and if I put laptop to sleep and open after a few hours - laptop restarted as power on and show me message "your macbook restarted because of a problem". I have Sabrent Rocket with Sintech adapter + efi patch as described in this theme https://forums.macrumors.com/threads/upgrading-2013-2014-macbook-pro-ssd-to-m-2-nvme.2034976/
Click to expand...
If you have Big Sur, you don't need to patch the EFI anymore for hibernation to work. Apple fixed that some time ago.
 
Last edited:
Install went okay but when install is finished and booting from disk there is an issue with display I think?
Only apple logo visible with hanging (empty) progress bar.
Mac eventually starts speaking to offer voice control.
Any ideas? I’m using OC. 0.7.4 and B10
MBPr 11,3 dGPU
  • NVIDIA GeForce GT 750M with 2GB of GDDR5 memory and automatic graphics switching
github.com

Nvidia Kepler Acceleration Support in macOS Monterey · Issue #498 · dortania/OpenCore-Legacy-Patcher

With macOS Monterey Beta 7 (21A5522h), Apple dropped support for Nvidia Kepler GPUs. To reimplement support, we will need to use Big Sur .bundle binaries due to issues with dyld extraction. Current...
github.com github.com
Appears to be lack of Kepler support after B7. Looking for a way to patch manually (without OCLP), or disable dGPU.

@chris1111 I've seen you made a patch for the Kepler . Would you like to share how I can patch this manually?
 
Last edited:
Tronstar said:
Install went okay but when install is finished and booting from disk there is an issue with display I think?
Only apple logo visible with hanging (empty) progress bar.
Mac eventually starts speaking to offer voice control.
Any ideas? I’m using OC. 0.7.4 and B10
MBPr 11,3 dGPU
  • NVIDIA GeForce GT 750M with 2GB of GDDR5 memory and automatic graphics switching
github.com

Nvidia Kepler Acceleration Support in macOS Monterey · Issue #498 · dortania/OpenCore-Legacy-Patcher

With macOS Monterey Beta 7 (21A5522h), Apple dropped support for Nvidia Kepler GPUs. To reimplement support, we will need to use Big Sur .bundle binaries due to issues with dyld extraction. Current...
github.com github.com
Appears to be lack of Kepler support after B7. Looking for a way to patch manually (without OCLP), or disable dGPU.

@chris1111 I've seen you made a patch for the Kepler . Would you like to share how I can patch this manually?
Click to expand...
 
@Tronstar I had the same issue, managed to boot in Safe Mode holding the shift key and patching with OCLP. I have reverted back to Big Sur as this is a fix that will have to be repeated after MacOS updates and using an external drive to boot was too much for me.
 
lord.macintosh said:
@Tronstar I had the same issue, managed to boot in Safe Mode holding the shift key and patching with OCLP. I have reverted back to Big Sur as this is a fix that will have to be repeated after MacOS updates and using an external drive to boot was too much for me.
Click to expand...
Yes, I understand your choice to go back. Well if you don't need the dGPU maybe you could disable it in nvram? setting. For what I now understand is that this mbpr 11,3 (once upgraded to Monterey) doesn't even need OC to boot. All that's needed is a simple NVRAM command -no_compat_check and it'll boot fine. I'm trying to find a way to disable this 750M and also how to patch this Kepler GPU manually.
 
Unfortunately it's not working on MacBook Pro 11,3 late 2013.
Only boots in safe mode because of the Kepler dGPU (NVIDIA GeForce GT 750M)

Is there a way to make it work by disabling the dGPU?

I know there is the OCLP post install System patch but that requires disabling SIP and I prefer not to.
 
Tronstar said:
I'm trying to find a way to disable this 750M and also how to patch this Kepler GPU manually.
Click to expand...
Thats not really make sense
what is the graphics of your CPU

Can be used WEG Injected from OC and see if you could disable the Intel card with a specific boot args
Or the other way around?
 
Last edited:
  • Like
Reactions: Tronstar
chris1111 said:
Thats not really make sense
what is the graphics of your CPU

Can be used WEG Injected from OC and see if you could disable the Intel card with a specific boot args
Or the other way around?
Click to expand...

Thanks for pointing that out! I really dig your approach, just OC and leaving SIP in tact.

CPU = 2.3GHz quad-core Intel Core i7 processor (Turbo Boost up to 3.5GHz) with 6MB shared L3 cache
iGPU:
Chipset Model: Intel Iris Pro
Type: GPU
Bus: Built-In
VRAM (Dynamic, Max): 1536 MB
Vendor: Intel
Device ID: 0x0d26
Revision ID: 0x0008
Automatic Graphics Switching: Supported
gMux Version: 4.0.8 [3.2.8]
Metal Family: Supported, Metal GPUFamily macOS 1
 
Last edited:
I tested the csrutil disable / reboot / nvram boot-args="-no_compat_check" / csrutil enable

It works!! Monterey RC1 booted without any complaints... It does not detect the RC2 update, though.

Maybe, we could think about having a hybrid solution with OC on a memory stick to boot when we have macOS updates and the -no_compat_check for our day-to-day reboots!!
 
macpro_mid2014 said:
I tested the csrutil disable / reboot / nvram boot-args="-no_compat_check" / csrutil enable

It works!! Monterey RC1 booted without any complaints... It does not detect the RC2 update, though.

Maybe, we could think about having a hybrid solution with OC on a memory stick to boot when we have macOS updates and the -no_compat_check for our day-to-day reboots!!
Click to expand...
Great, but you actually don't need to disable SIP to do that.
 
  • Like
Reactions: macpro_mid2014
This is quite interesting.

Post in thread 'macOS 12 Monterey on Unsupported Macs Thread'
https://forums.macrumors.com/thread...unsupported-macs-thread.2299557/post-30397064
Do you think it’s possible to disable the GT 750M and force the Iris pro iGPU? Then SIP can remain untouched and is my install a succes. I don’t think Apple will re-add Kepler support in final version, do you?
I’m lost here

Ran into a minor strange thing. I reinstalled Monterey with your OC config on external usb SSD for the second time. The first time it could be booted without OC by setting nvram boot-args=“-v -no_compat_check” after install in recovery mode.
Now the second install it won’t work anymore. Nothing important but just trying to understand why.
 
  • Like
Reactions: macpro_mid2014
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