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.
72F88291-9744-4F2F-8CC1-61EEEEB3D5D8.jpeg
I watched this more carefully. After finishing the install run, it reboots with the startup volume set to a volume I've not seen before called "PreBoot". That boots, shows the Apple logo and a progress bar, which gets about 1/3 of the way across before rebooting again, with the startup volume set to my normal boot volume.

View attachment 1904403

I had several attempts at booting repeatedly from the PreBoot volume, but it always acted the same way, and so I'm still stuck on 11.6. FWIW, I'm booting from a PCIe NVME card with OC installed on a separate SATA SSD. My upgrades from 11.2.3 to 11.3, and on to 11.6 all worked fine previously.

Any bright ideas?
Further experiments. I made a bootable flash drive with the Monterey installer on and booted from that. The installer ran for about 15 mins, then rebooted into a macOS installer assistant mode which displayed this error saying it could not install a firmware update:



After that the progress bar stopped moving. I went through this twice with the same results. So I’m still stuck in 11.6!
 
🪓AHOY!🪓12.1b1+ will now (run)better on unsupp Ivy Bridge (i-series) CPU Macs now that RDRAND and SurPlus are fully enabled. Recent OCLP_032 rdrand (aka "Montrand")/SurPlus Branch nightly, here: https://nightly.link/dortania/OpenC...build-app/rdrand/OpenCore-Patcher-TUI.app.zip This branch has not yet been merged into the Main Branch. However, the Main Branch was recently merged into the rdrand/SurPlus Branch.:cool:
 
Last edited:
I’m having the problem also. Did you ever find a solution? Any version higher than Catalina causes this issue. Any any version of Safari higher than 13 does as well (even on Catalina).

No I haven't found a solution unfortunately, I've tried many different things with no solution. And yes it's the same for me it's happening on anything beyond Catalina, I have to use Catalina until this is solved unless I want to slowly go blind. What I'm wondering is how come more people aren't reporting this issue...
 
  • Like
Reactions: K two
?AHOY!?12.1b1+ will now (run)better on unsupp Ivy Bridge (i-series) CPU Macs now that RDRAND and Surplus are fully enabled. Recent OCLP_032 rdrand (aka "Montrand")/SurPlus Branch nightly , here: https://nightly.link/dortania/OpenC...build-app/rdrand/OpenCore-Patcher-TUI.app.zip This branch has not yet been merged into the Main Branch. However, the Main Branch was recently merged into the rdrand/Surpus Branch.:cool:
Using the 0.3.2 RDRAND branch nightly, downloaded two hours ago. Looks good!

Also tried the new (already present since yesterday) download feature, TUI item 6 Installer Creation. Can use this now instead of gibmacos. Used it to download the installer pkg and let it put the installer app into /Applications.
(Didn't use it to create a bootable USB installer - I've several of them in different partitions of one disk, but the new feature of OCLP TUI seems to need an entire medium.)

This adds another piece of convenience to OCLP, like dosdude1 did when adding download to his Catalina patcher.
Thanks!
 
Further experiments. I made a bootable flash drive with the Monterey installer on and booted from that. The installer ran for about 15 mins, then rebooted into a macOS installer assistant mode which displayed this error saying it could not install a firmware update:



After that the progress bar stopped moving. I went through this twice with the same results. So I’m still stuck in 11.6!
if you use an after market internal SSD to install the OS it will not work with Monterey because apple have a new firmware update and to upgrade to Monterey you need an apple original SSD so you can update the firmware on the chip and then Monterey will install no problem and when get that done you can put your after market SSD and install Monterey with no problem. i had to do that on my MBP mid 2015
 
if you use an after market internal SSD to install the OS it will not work with Monterey because apple have a new firmware update and to upgrade to Monterey you need an apple original SSD so you can update the firmware on the chip and then Monterey will install no problem and when get that done you can put your after market SSD and install Monterey with no problem. i had to do that on my MBP mid 2015
The joys of T2. Earlier Macs use any SSD. :cool:
 
  • Like
Reactions: Hackintosh HD
The joys of T2. Earlier Macs use any SSD. :cool:
I was so mad when found out that i need that apple ssd to do the OS upgrade. so i had buy one from kijiji because it was a used MBP that i got 2 years ago and it had an after market SSD.
but after you get that firmware update done we should be ok for a few years using after market SSD i think until Apple decided to do a firmware update again. so it will be a good idea to keep that Apple SSD.
 
Last edited:
  • Like
Reactions: K two
if you use an after market internal SSD to install the OS it will not work with Monterey because apple have a new firmware update and to upgrade to Monterey you need an apple original SSD so you can update the firmware on the chip and then Monterey will install no problem and when get that done you can put your after market SSD and install Monterey with no problem. i had to do that on my MBP mid 2015
Not true in my case. Still seeing the same firmware error message after swapping out aftermarket 1TB for the stock samsung 256gb one. What am I doing wrong? Do I need to reset PRAM or do something else? 10,1 MacBook Pro Mid 2012 15" Retina. Thanks!
 
Not true in my case. Still seeing the same firmware error message after swapping out aftermarket 1TB for the stock samsung 256gb one. What am I doing wrong? Do I need to reset PRAM or do something else? 10,1 MacBook Pro Mid 2012 15" Retina. Thanks!
when you say samsung is that an apple original ssd or its an after market samsung? if you can do a screen shot for your ssd i can tell you if its an original or after market.
witch OS you are trying to install?
in your case your MacBook the last OS you can get (no patching) is macOS Mojave
 
I have installed the latest OCLP on my mid-2014 15 inch MBP with gt750 and everything seemed to bo working fine. Then I started to realize that my mac never sleeps if it is plugged and I close the lid. Audio will keep playing and popping once in a while like it's trying to make it go to sleep but it can't. So I started testing it, usual suspects, pmset, wake for network/bluetooth/powernap etc. Nothing. It's only happening when plugged in and I close the lid. On battery it goes to sleep and wakes up properly. Also sleep works as I can press the sleep button and it goes to sleep. If I then close the lid, it will wake up and go to sleep again. Strange behavior. Didn't have it on Catalina and Mojave. I thought to myslef, too bad, let's go back to Big Sur which I skipped entirely. Guess what? Same problem. Won't go to sleep by closing the lid when plugged to power. Did a bunch of clean installs to test it without even opening any apps, same thing. Mojave and Catalina behave as expected, tested that 20+ times just to have some clarity that it's not my machine. It seems to me that apple screwed something up for some older machines with Big Sur and then instead of fixing it, they decided to cut it off from to support making Catalina the last fully functioning OS for my mid-2014 MBP with gt750m. Found a bunch of people online saying the same thing. I'm quite pissed as my hackintosh has never given me a problem which I couldn't solve and runs Monterey better than my MBP runs Big Sur.
I have the same MBP (late 2013) 11,3 with GT750.
Unplugged: everything is fine.
PluggedIn:
My one goes to sleep (PowerNap is disabled)
Sometimes it don’t sleep when PowerNap is enabled. I think it has to do with process photolibraryd
 
Currently we had no success with the 24" 2009 and 21.5" 2009 because the internal display is connected via LVDS and not eDP - so one would need a different vBIOS on the card.

But using the cards listed on the thread in my signature will give you full metal support on an external display. One weird solution to use the internal 24" LCD is making it an external display using a converter kit from eBay. Your iMac has a standard MXM port.


Would this card be a working solution or just a senseless overkill? I am still torn between ditching my old trusty iMac and getting a m1 24 inch.
 

Would this card be a working solution or just a senseless overkill? I am still torn between ditching my old trusty iMac and getting a m1 24 inch.
The best card you can get. DRM with Big Sur and Monterey, 40W and high performance at the same time. Check the thread link on my signature.
 
  • Like
Reactions: macinfo
Has anyone seen issues getting desktop and documents to sync on an unsupported Monterey install after signing into iCloud?

I also found most of my other (non boot) apfs volumes are marked as read only from within Montery. (I physically removed the drives during the upgrade to prevent them from getting modified). If I boot back into Mojave, they are fine...
 
I noticed on my 2011 MBP that when I wake from sleep, the system wakes, but the display stays off until I hit a key a second time.

Also, I prefer the older power preferences, when you could easily set when the Mac sleeps with the slider. Now I have to go into terminal.
 
I’ve installed Monterey successfully on my iMac14,2, but the graphics looked a little funny so I did the patch system volume to fix my Nvidia Graphics card and it looked like everything patched correctly, but when I reboot it froze on the apple logo with the loading bar for over an hour.

I tired a force reboot and it froze again on the apple logo with loading bar. So I had to reinstall Monterey. I have tried this 3 times now and the same thing happens every time. It looks like I can't patch the system for the graphic drivers. Any ideas how to fix the graphics without it freezing and make my system not bootable? Thanks for any help.
 
I’ve installed Monterey successfully on my iMac14,2, but the graphics looked a little funny so I did the patch system volume to fix my Nvidia Graphics card and it looked like everything patched correctly, but when I reboot it froze on the apple logo with the loading bar for over an hour.

I tired a force reboot and it froze again on the apple logo with loading bar. So I had to reinstall Monterey. I have tried this 3 times now and the same thing happens every time. It looks like I can't patch the system for the graphic drivers. Any ideas how to fix the graphics without it freezing and make my system not bootable? Thanks for any help.
read previous posts, mine in particular as i had the same issue
 
My old mid-2011 MBA 4,2 is currently only running Windows 10 since Apple stopped supporting it.

From what I've read so far, I could use OCLP to install Monterey, but:

1. No hardware video acceleration

2. Wifi and Bluetooth both mostly work

3. Safari doesn't work well, but other browsers do

Is this correct?

Has anyone with a MacBook Air 4,2 actually tried this yet?
 
My old mid-2011 MBA 4,2 is currently only running Windows 10 since Apple stopped supporting it.

From what I've read so far, I could use OCLP to install Monterey, but:

1. No hardware video acceleration

2. Wifi and Bluetooth both mostly work

3. Safari doesn't work well, but other browsers do

Is this correct?

Has anyone with a MacBook Air 4,2 actually tried this yet?
Go here: https://dortania.github.io/OpenCore-Legacy-Patcher/MODELS.html :rolleyes:
 
  • Like
Reactions: Larsvonhier
I have a nanoTECH expresscard with two USB3 ports which I use to connect external disks in a faster way than with the onboard USB2 connectors.

Worked upto Big Sur 11.6.1 (and maybe still Monterey 12.0.1, I forgot).
Doesn't work anymore in 12.1b1: card is detected, but when connecting a USB disk to it, the OS fails in that the pointer of the internal trackpad (connected to internal USB) stops moving.
Will certainly affect very few users, and I could also live without it.

Maybe an effect of the beta software, going to analyse further.
Thank you for the warning, I've both the nanoTECH ExpressCard/34 and the Sonnet Tempo Duo ExpressCard/34 and do not want to loose their functionality.
 
  • Like
Reactions: macinfo
Does anybody know the background of the OpenCore Legacy Patcher 0.2.5 changelog entry on FileVault 2?



I've tested activating FileVault 2 on my root volume OCLP-patched MacBookPro5,2 on both macOS 11.6 Big Sur and macOS 12.0.1 Monterey without success. An active FileVault 2 would render the system unbootable immediately.

I also was under the impression that FileVault 2 use would be forever impossible on root volume patched systems. Do I misunderstand something here? - Thanks!
Answer to myself (for the purpose of delivering documentation to hopefully everybody's benefit here):

As stated in the OpenCore Legacy Patcher 0.2.5 changelog, FileVault 2 is indeed possible with OpenCore Legacy Patcher ≥ 0.2.5 on root volume patched systems. The reason why it wouldn't work on my 17" MacBook Pro Mid 2009 (MacBookPro5,2) was the machine's APFS-patched ROM, which I had flashed using Dosdude1's APFS ROM Patcher 2.0 (password for the ZIP archive). While this patch makes APFS volumes visible and bootable in the machines' startup volume selection screen, it apparently is not compatible with OCLP's methods to implement FileVault 2 support for root volume patched systems. Big thanks to @khronokernel for pointing me in the right direction in the GitHub issue I had opened.

I've therefore reflashed my MBP5,2's ROM with the unaltered ROM backup dump of Dosdude1's patcher which I had kept using his ROMTool 2.0 (password for the ZIP archive). I've now FileVault 2 Disk encryption working on my MBP5,2 and macOS 11.6.1 Big Sur.
 
  • Like
Reactions: macinfo and K two
Answer to myself (for the purpose of delivering documentation to hopefully everybody's benefit here):

As stated in the OpenCore Legacy Patcher 0.2.5 changelog, FileVault 2 is indeed possible with OpenCore Legacy Patcher ≥ 0.2.5 on root volume patched systems. The reason why it wouldn't work on my 17" MacBook Pro Mid 2009 (MacBookPro5,2) was the machine's APFS-patched ROM, which I had flashed using Dosdude1's APFS ROM Patcher 2.0 (password for the ZIP archive). While this patch makes APFS volumes visible and bootable in the machines' startup volume selection screen, it apparently is not compatible with OCLP's methods to implement FileVault 2 support for root volume patched systems. Big thanks to @khronokernel for pointing me in the right direction in the GitHub issue I had opened.

I've therefore reflashed my MBP5,2's ROM with the unaltered ROM backup dump of Dosdude1's patcher which I had kept using his ROMTool 2.0 (password for the ZIP archive). I've now FileVault 2 Disk encryption working on my MBP5,2 and macOS 11.6.1 Big Sur.
You might want to post your comment on the Big Sur thread? :rolleyes:
 
  • Like
Reactions: Hackintosh HD
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.