Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 12 Monterey on Unsupported Macs Thread
- Thread starter khronokernel
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Great questions, Joe!
— RAM upgraded to 8 GB
— Internal SSD: Crucial MX300, 525 GB
This got me curious as to whether withdrawing and re-inserting the card in the built-in slot would un-stall the stalled startup process that I described earlier. I tried it twice; the first time, boot stalled at "Failed to get system info, retrying..." displayed repeatedly ad infinitum; messing with the card was no help. However, when the process stalled at the more common point, seven lines after mention of "HID: Legacy shim 2"—and indeed, even after the "Prohibited" sign had been displayed on-screen—re-inserting the card DID un-stall the process, and the Installer was able to boot successfully. (I didn't go thru another round of actually installing, but I presume it would've worked fine.) Same story if Recovery/Installer startup falls into a repeating cycle of "Mount (#) failed" with "#" incrementing by one each time.
Macmini5,1 • Mac mini "Core i5" 2.3 GHz • MC815LL/A • Model A1347 • EveryMac.com page
— RAM upgraded to 8 GB
— Internal SSD: Crucial MX300, 525 GB
An SD card already inserted at the time of system startup does appear in the boot picker, but does not appear in Disk Utility (or
diskutil list) once the Recovery/Installer has finished booting from the USB-attached card. However, withdrawing and then re-inserting the card in the built-in reader slot causes it to reappear and become readable as normal.This got me curious as to whether withdrawing and re-inserting the card in the built-in slot would un-stall the stalled startup process that I described earlier. I tried it twice; the first time, boot stalled at "Failed to get system info, retrying..." displayed repeatedly ad infinitum; messing with the card was no help. However, when the process stalled at the more common point, seven lines after mention of "HID: Legacy shim 2"—and indeed, even after the "Prohibited" sign had been displayed on-screen—re-inserting the card DID un-stall the process, and the Installer was able to boot successfully. (I didn't go thru another round of actually installing, but I presume it would've worked fine.) Same story if Recovery/Installer startup falls into a repeating cycle of "Mount (#) failed" with "#" incrementing by one each time.
Yes, it does.
Point me to instructions and I'll see what I can do.
Last edited:
Thanks - and I can't reproduce the problem I had with Safari 15.2. All working correctly and smooth.
I found that this happens when there is no battery installed and the system gets buggy, but a newbie like me couldn't imagine it
another quick fix modifying com.apple.AppleMultitouchTrackpad.plist
Another Mini3,1 to macOS 12.1RC2 OTA atop b4 via OCLP_031R>032N, install smooth, unattended, no ghosts, browsers all accounted for.
works ok but firewire needs restart to enable.
just to verify, when next "ota" becomes available, is preparing for it a two step process (a) unpatch (b) enable sip?
just to verify, when next "ota" becomes available, is preparing for it a two step process (a) unpatch (b) enable sip?
I think you solved the problem.
The prohibited icon does not mean the boot process has stopped. The icon just means the boot process has waited a certain amount of time for the disk containing the macOS to get enumerated by the macOS kernel and is still waiting (before this, the disk was being read by UEFI code in boot.efi - not the macOS kernel). In the case of an SD card, you have to eject it and insert it for it to get enumerated by the macOS kernel. Then the waiting stops and boot continues. I think SD card readers are a little strange - they exist as a block device even if no media is inserted. I'm not sure how macOS knows when new media is inserted.
I am planning in updating to macos monterey my late 2013 macbook pro, model 11,3 with the dGPU GT 750M, running catalina 10.15.7 with latest (i think) boot room: 432.40.8.0.1. This is the only mac I have ever had, I skipped Big sur altogether, and have never installed unsupported OS before, I have read the documentation of OCLP, but just wanted to ask to be sure:
Are there at the moment any problems in using macos monterey with my macbook pro model? Anything I should know or do before updating? has there been reports of bricks with OCLP?
Are there at the moment any problems in using macos monterey with my macbook pro model? Anything I should know or do before updating? has there been reports of bricks with OCLP?
It would be more easy to search this thread for MacBookPro11,3
- your Mac will need post install patching to support the Kepler GPU and the HD4000 iGPU on Monterey
- Big Sur supports your hardware fully
- you should be aware of the fact that a supported machine may get firmware updates in near future - which will not be installed running Big Sur or Monterey (all such updatesd are blocked by OpenCore to avoid bricks). so keep a small Catalina installation on disk just to update your machine (can be deleted with Catalina EOS).
I did that of course, not a lot of results or useful comments regarding my model. The search proposal you suggested does not give any results at all for example.
Yes, I know my model supports big sur, never updated to it because of all the problems reported, so I decided to skip it.
ohh ok ok, so even if our hardware are not supported anymore we will still get firmware updates? and because of this I should keep a Catalina installation on my disk, because OCLP blocks all updates? ok, got it. But I didnt understand the "can be deleted with Catalina EOS", delete what? and i also dont know what EOS means... sorry..
EOS End of Service
If your system is still supported with Big Sur you should keep a Big Sur installation. Yes, you get updates as long as your system runs natively a supported macOS version. Big Sur will get two more years of support. You may get firmware updates for your machine, too.
I would not move to Monterey 12,01 if I had a Big Sur supported system. The most new Apple bugs will be solved with 12,3 or 12.4 next spring....especially in your case needing patches for graphics.
Hallo
My iMac has no iNet Connection after reboot
MacOS 12.1 beta 4
OCLP 32n
All my other devices haven’t problems
My iMac has no iNet Connection after reboot
MacOS 12.1 beta 4
OCLP 32n
All my other devices haven’t problems
Last edited:
MBP4,1 Early 2008 17-inch Big Sur 11.6.2 with excellent performance, better than Catalina.
Can't complete the installation of Monterey 12.0.1 via OCLP 0.3.1. over external USB drive
Our machines share the same SMIOS identifier "MBP4,1".
Would you tell me, how you successfully installed 12.1b1?
Where can I get OCLP 0.3.2n with RDRAND patch (what is that btw, and do I need it also?) as per your post above?
(EDIT: I found OCLP 0.3.2 nightly build TUI via search in this thread, but no offline version, or GUI)
I was using OCLP 0.3.1 TUI (with Ethernet connection during installation) and TUI Offline with WLAN connection. I also tried OCLP 0.3.1 GUI... all providing the same result: after about 30mins. into Monterey installation, the MBP4,1 reboots, then is stuck. Once I reboot with alt-key, choose my Macintosh HD, I am on Big Sur 11.6.2 again, with 13.4GB of macOS Install Data leftovers in the System folder. I was able to delete the macOS Install data.
In all futile attemps, I chose to upgrade my existing Big Sur installation, I did not try a clean install yet.
Advice, how you bumped your MBP4,1 to Monterey 12.1b1 is highly appreciated.
Maybe @K two also has some tricks up his sleeve?
P.S.: I did n o t try to upgrade from the OTA update via System Preferences, as the update is "macOS Monterey beta 12.1". Is this the way, and if so, with which version of OCLP?
Last edited:
mmm i see, the thing is that i have read many comments saying how monterey is much better than big sur. well i think i will try to research a little bit more and think about it. But I would really like to try monterey
Now on Monterey 12.1RC in the meantime. The trick is to prepare a boot volume with OCLP including the RDRAND patch enabled. You will find this option in the 0.3.2n build (and probably also in 0.3.1, not sure, would have to DL and check again). Also make sure that either you have your EFI flash patched for APFS or also enable APFS boot through OCLP. (Can be ignored if you're still on HFS+ if this still supported at all for installation on Monterey).
The other hint: During the 2nd boot phase (and following ones !) it's advisable to boot in verbose mode to see if you're really stuck or it just takes long to run the installer stages. Actually, it can really take so long that ppl reported to let it run overnight!
I remember years ago that in a situation like this, one would expect to see an icon—I think it looked like a 3.5" floppy disk—with a blinking question mark inside it. If the "prohibited" icon is modern replacement for that older version, I'd have to say that the old way was a lot more informative as to what was actually happening. Semantically, the "prohibited" icon connotes final and unrecoverable failure, rather than a continuing wait for a needed resource to become available.
Is this specific to the OCLP EFI code, or are you saying this is true in general? Because normally, the 2011 Mini is perfectly happy to cold-boot from an SD card, no removal and re-insertion necessary. In the case of the OCLP EFI, could the practical effect of the remove-and-reinsert be accomplished (or simulated) in some way by adding appropriate directives to the OCLP EFI script?
I just updated my mid 2014 macbook 11,3 with nvidia 750m from 12.0.1 to 12.1 without problems with OCLP 0.3.1 , applied the post patch from safe mode and rebooted to normal 100% working.
after that I saw that 0.3.2 was pushed on github so I also downloaded it and built it to my EFI
now I have some questions regarding 0.3.2 :
will that change the size of OTA I receive ? can I receive delta now or it will continue to be Full size Installer ?
I still need to do post system patch for Nvidia gpu or this new VM feature introduced in 0.3.2 change the behaviour of this ?
Thanks
after that I saw that 0.3.2 was pushed on github so I also downloaded it and built it to my EFI
now I have some questions regarding 0.3.2 :
will that change the size of OTA I receive ? can I receive delta now or it will continue to be Full size Installer ?
I still need to do post system patch for Nvidia gpu or this new VM feature introduced in 0.3.2 change the behaviour of this ?
Thanks
For installation, the OCLP TUI will do.
MBP4,1 cannot boot APFS file systems so it has to be either patched by dosdude1´s APFS ROM patch* or OCLP has to be set to allow booting APFS volumes.
*unzip pwd is "apfs"
Downloading 12.1 full installer (InstallAssistant.pkg) with gibmacos. Will install it with the just released OCLP 0.3.2.
Updating BS to 11.6.2 (20G313) already worked fine with 0.3.2 release (using an external testing SSD).
Updating BS to 11.6.2 (20G313) already worked fine with 0.3.2 release (using an external testing SSD).
Last edited: