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

No problem. I looked up the picture in English. I did NVRAM reset. Start with CMD+ATL+P+R and SHIFT+CTRL+Power. Problem occurs with every restart or after shutdown.
You are probably having a kernel panic just before it shuts down.

If you are comfortable with it, one test that you can try would be running the OCLP on your machine (installing it to a USB drive for instance) to see if the panics continue.
 
Last edited:
hello chris1111 and macpro_mid2014,
Could you explain please why you use different key of SMBIOS (BIOSversion) in yours configs? Is it important to use 9999.999.999.999.999?
I googled it and didn't find an answer.
 
Last edited:
  • Like
Reactions: macpro_mid2014
hello chris1111 and macpro_mid2014,
Could you explain please why you use different key of SMBIOS (BIOSversion) in yours configs? Is it important to use 9999.999.999.999.999?
I googled it and didn't find an answer.
My config.plist has been originally generated by OCLP and then I edited it and removed everything not required by my MBP. Also, I downloaded OpenCore and compile it in my MBP and then, I switched all files from OCLP to the OpenCore files I compiled in my computer, customizing only the config.plist file.
Since OCLP 0.4.2, it is possible to use a virtual machine (spoofless) approach while communicating with Apple's update servers, so I kept that in my config.plist.

chris1111's config.plist has been created by him, not OCLP. It still uses the previous approach which is to spoof a compatible MackBook while communicating with Apple's servers. The 9999.X thing is to disable any attempt to update the Firmware while updating macOS.

"Is it important to use 9999.999.999.999.999?"
Well, it depends on how you will update your MB when a new version of Monterey is released.
What I do: First, I update the version of Big Sur I have installed on an external SSD. If there is any Firmware update, it will happen there, only then I update Monterey.
Concluding: if you use the spoof approach you need to use the 9999.X otherwise you risk installing the wrong firmware during a Monterey update. If you use the spoofless approach, you don't need the 9999.X
 
Last edited:
  • Like
Reactions: peirato
My config.plist has been originally generated by OCLP and then I edited it and removed everything not required by my MBP. Also, I downloaded OpenCore and compile it in my MBP and then, I switched all files from OCLP to the OpenCore files I compiled in my computer, customizing only the config.plist file.
Since OCLP 0.4.2, it is possible to use a virtual machine (spoofless) approach while communicating with Apple's update servers, so I kept that in my config.plist.

chris1111's config.plist has been created by him, not OCLP. It still uses the previous approach which is to spoof a compatible MackBook while communicating with Apple's servers. The 9999.X thing is to disable any attempt to update the Firmware while updating macOS.

"Is it important to use 9999.999.999.999.999?"
Well, it depends on how you will update your MB when a new version of Monterey is released.
What I do: First, I update the version of Big Sur I have installed on an external SSD. If there is any Firmware update, it will happen there, only then I update Monterey.
Concluding: if you use the spoof approach you need to use the 9999.X otherwise you risk installing the wrong firmware during a Monterey update. If you use the spoofless approach, you don't need the 9999.X
Thank you for so full explanation.
Some months ago I've already installed Monterey on my MacBookPro11,1 and then turned back to BigSur because I had Volume Hash Mismatch errors. After that firmware is 432.60.3.0.0. SilentKnight shows that it's expected version. Considering this I changed config of Chris a little bit by turning off updating of SMBios.

Previously I used OCLP, now I trying your approach (OpenCore).
Let's see how it will work now.
 
  • Like
Reactions: macpro_mid2014
Can anybody confirm on-screen OC debug logs (with errors, warnings and info all logged to console, on DEBUG version of OC) working fine on a MacBookPro10,2 updated to BIOS version (reported in system information, when OC is not masking it) of 426.0.0.0.0? (NB This machine will only ever get this BIOS update if a recent update of Catalina is installed onto the SSD which the machine shipped with.) I'm seeing hangs; despite lots of effort to rule out other things, it really does seem to be a factor of the firmware update. (Which I did on purpose at the time; arguably regretting it now!) I would really love to hear a report of this happening elsewhere, or even definitely not happening...
 
Last edited:
So quick question:

I want to update my 15" MacBook Pro 2013 to Monterey.
All I need to do is using OCLP, and installing it directly on my existing BigSur installation. (instead of creating an USB)

Then I restart my Mac with OpenCore as the new Bootloader.
All I need to do is open System Preferences and hit the update button, right?
 
@LucMac Better to post on thread https://forums.macrumors.com/threads/macos-12-monterey-on-unsupported-macs-thread.2299557/ (because this thread is for @chris1111's installer specifically not OCLP, and is not supported on this thread any more anyway, only on github, see p.1 of this thread)

Thanks, @chris1111 for starting (and ending) this thread. I hope Apple won't kill the Intel Iris Pro Graphics in macOS 13 and people will continue to rely on your method!

Thank you again.

PS: I am stopping to monitor this thread. It was good while it lasted.

RIP
 
Hi All

@Chris F1111 method suggests formatting the HDD.

Once I finish the installation of the monetary. Do I need to use my timemachine backup to restore all my apps and documents etc. _
 
Greetings to you!

Since I updated to 12.5, my screen stays black when I try to wake up the Macbook.
 
Greetings to you!

Since I updated to 12.5, my screen stays black when I try to wake up the Macbook.
Unfortunately, the graphics and display of these models are very problematic.
Just take a look at the comments on this link to understand that you are not alone and countless other people have had this problem too.
https://osxdaily.com/2014/11/22/fix-macbook-pro-booting-black-screen/
Not long ago, my brother's laptop, which is exactly the same model as mine, froze when logging into the OS.
By asking what happened to it, I found out that the laptop was turned on in very cold conditions in winter and this problem occurred.
Of course, safe mode was entered without any problem, but in normal mode, it got stuck when logging into the OS.
Because I had a copy of this model, I was able to replace the displays and yes, after checking, I realized that the problem is with the display.
It was interesting that even though the display was showing an image, it was not working properly and I finally found out the reason.
As you can see in the pictures, in addition to the display, WiFi/Bluetooth antenna and webcam are also located inside the panel.
The problem must have been one of these two.
We couldn't get another display for the laptop because it was too expensive here.
But fortunately, the HDMI output of the laptop was working and it could be used in detached display connector mode.
I hope this is not your problem, try software solutions, if the problem persists, suspect a hardware problem.
 

Attachments

  • IMG-20220227-WA0009.jpg
    IMG-20220227-WA0009.jpg
    83.8 KB · Views: 126
  • IMG-20220227-WA0010.jpg
    IMG-20220227-WA0010.jpg
    78.7 KB · Views: 102
  • IMG-20220227-WA0012 2.jpg
    IMG-20220227-WA0012 2.jpg
    110.6 KB · Views: 110
  • IMG-20220227-WA0013.jpg
    IMG-20220227-WA0013.jpg
    55.4 KB · Views: 121
  • IMG-20220227-WA0016.jpeg
    IMG-20220227-WA0016.jpeg
    105.7 KB · Views: 135
  • Like
Reactions: rezzo
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.
Can you please post some more details on how to do this - I am a newbie with MBP late 2013. Thanks
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.