If you are on a non metal device you have to unpatch your system with OCLP. Than you will find the 1,9gb b4 with developer account. You can force this: sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil enroll DeveloperSeed
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
Thanks for taking the time and effort to reply, but did you read the whole post? This Mac is a 2014 iMac with a metal-capable GPU, and I did enroll in the DeveloperSeed program. When I tried to use the System Software Update preference pane, it throws a preferences error and does not show or get the b 4 update. That error has been persistent on this machine for years, and if you have any idea about how to correct it, fire away. I assume it is some file, perhaps a bom file somewhere in the receipts folder? that is the cause of that.
I assume that the Mr. Macintosh HP will show the b4 full installer in due time (it is not listed to date, May 4 2022).
I am wondering if the terminal fetch full installer command will work. I might try that later today, but I am not sure about the correct syntax to use:
softwareupdate --fetch-full-installer --full-installer-version 12.4 21F5071b
Does not work, "Update not found."
Attachments
Last edited:
You can also use GibmacOSmaster script (search Github for it) to DL all (developer) betas. 12.4b4 is listed already, but somehow I get an "invalid install package" error currently. Will be fixed on Apple´s side shortly, I guess.
Hi, I have a problem, maybe someone can help me: I installed OCLP 0.4.4 and then Monterey 13.2.1 on a MacBookAir3,2. During installation the it hung up whenever an internal reboot was performed, it just showed a white screen and nothing happened (just the fan was running high). I had to unplug the battery and restart, then it would continue with the installation. it was a bit cumbersome but in the end it worked, i had a working Monterey. But when i turn the macbook off and on again, it hangs the same way, just a white screen. I have to force shut down and do a PRAM reset, then it boots normally.
Any suggestions?
Any suggestions?
Thanks for the reply. I tried a search on Github, but, as usual, while that search does show the script, it is not obvious how to download it. Maybe it is just me, but I hate looking through a ton of text for a download link. Gave up on that.
Updated today, the Mr. Macintosh page has the Monterey 12.4 b4 download listed, as well as a Big Sur 11.6.6 RC b4 available.
Last edited:
Just to remind, it appears that Beta 4 has a build number of 21F5071b, as that's the latest version I was able to update to yesterday (I know it was posted last page.)
Seems to be doing just fine on a MP 5,1 running OCLP 0.4.4 final, but I haven't tested Wi-Fi or Wi-Fi Sharing yet.
Seems to be doing just fine on a MP 5,1 running OCLP 0.4.4 final, but I haven't tested Wi-Fi or Wi-Fi Sharing yet.
I'm hoping someone can help..
I installed 12.4 Beta3 from scratch using OCLP 4.4 and everything is working except WIFI... I have 4 cMP machines running perfect w/Wifi but my one cMP with a clean install has no WIFI???
Thanks in advance.
P.S. Yes, I ran the OCLP patch.
I want to add that I can see my wifi network but it wont connect like it does on my other cMP's... I re-patched to no avail..
I installed 12.4 Beta3 from scratch using OCLP 4.4 and everything is working except WIFI... I have 4 cMP machines running perfect w/Wifi but my one cMP with a clean install has no WIFI???
Thanks in advance.
P.S. Yes, I ran the OCLP patch.
I want to add that I can see my wifi network but it wont connect like it does on my other cMP's... I re-patched to no avail..
Last edited:
Try connecting your problematic cMP to a different wireless network, like a personal hotspot on your smartphone or another computer. In case it connects to those networks, maybe your router needs a reboot.
You should also check in the macOS system information whether the wireless hardware is in fact identical or maybe slightly different in the affected machine.
Thanks! I got it.. I just needed to join the network the long way around... lol
Never needed to do it that way before.
Cheers!
Last edited:
Saying goodbye to OCLP, cranky developers and hobbled old Macs, my son gifted me a Mini7,1 2xi7 16GB, PCI-e 1TB boots Monterey in 7 seconds. Best wishes to users,testers and hobbyists. It was fun for awhile. Peace out.
i hear you!
this whole upgrade is not worth the trouble.
you had incredible incite and was very patient helping others solver problems.
enjoy you new mac!
The mini 7,1 could very likely be dropped for macOS 13, so my money’s on that you’ll be back within a year and begging the “cranky developers” to take you back. lol lol 😂
Enjoy your 2014 mini….while it is still supported with the latest macOS. 😅
I found it a lot more enjoyable, easier, and more rewarding to put OCLP Monterey on my old abandoned 2011 MacBook Air, than the two days of HELL I just went through to get bootcamp to work on my supposedly fully supported 2015 iMac.
Congratulations! See you next year.
It’s more simple… After verifying the name of the EFI partition I'm interested in mounting in Finder, using the Terminal I just digit firstI've been using this method for years. No need to install anything extra, just need to be able to decipher the output of diskutil list.
*edit*
Mounting the EFI Boot Partition on Mac OS X
Here’s the answer to another reader request… According to WIkipedia, “On Apple–Intel architecture Macintosh computers, the EFI partition is initially blank and not used for bootin…themacadmin.com
Also I forgot that you might have an additional EFI partition because of OCLP, so be sure to mount the correct the EFI partition.
Code:
diskutil list
Code:
sudo diskutil mount /dev/NAME_disk0sx_to_mountNote: It is very important to use “sudo”!!! or the command “diskutil mount” doesn’t works.
The more experienced users can do better with OpenCore Configurator which brings up a button on the Menu bar from which to mount the EFI’s of the desired internal or external drives.
Well, it´s easy while not obvious: Just DL all components, put in a folder, use Terminal to run gibmacosmaster.command and enjoy the text based menus...
abandon MacBook air? wow!
I'm still using my 2010 now and still amazed how fast this is!
anyways
was there an extra step to installing Monterey?
Im using the same MBA and the original ssd drive, toshiba i think
after 3 reboots, the 4th one stops and sez: can't be done, son!
im hoping i can get Monterey or Big Sur on the mini12 soon
once a new ssd drive and usb 3,0 thumb drive arrives.
Bootcamp was always a pain in the but, but that should hav installed as anything else.
I've recently renamed all my EFI partitions.
For example, my iMac14,2 has an NVMe and a SATA drive. So it has two EFI partitions named EFINVME and EFISATA.
My MacPro3,1 has 4 drive bays and two ODD ports, so the EFI partitions are named EFIB1, EFIB2, EFIB3, EFIB4, EFIO1, EFIO2.
Then I can mount any of them just using their name so I don't have to look up what disk they belong to after each boot.
sudo diskutil mount EFIO2
NO more unsupported Macs, will get a newer Mac if need be.
What will happen to all your trusty Minis? Thanks for all your cranky posts!
Ah! Ah! Ah!... Great K two said and makra !K two said: NO more unsupported Macs, will get a newer Mac if need be.
makra: What will happen to all your trusty Minis? Thanks for all your cranky posts!
Some time ago (at Monterey 12.1 beta build) I had reacted like this too, but then I retraced my steps and now, thanks to the continuous improvements made by latest Monterey releases and by OpenCore Legacy Patcher my Mac with Monterey 12.3.1 and OCLP 0.4.4 is as perfect as a supported original Mac and works even better than some less powerful supported Macs than mine. (see my Signature).Ditto with my mid 2010 MacBook Pro on which, however, I preferred to install Catalina using dosdude1 patch 1.4.4.
In fact, I was back in High Sierra, disappointed because I could no longer activate Safari extensions and because many applications crashed many times even if usually only on first start. Then, fortunately, I discovered both the Script to activate "non-Metal" Safari's Extensions, both the Terminal command to deactivate AMFI in NVRAM and both the patch to activate the Catalina's OTA updates. And now my MBP is also much better than with High Sierra. It has only one limitation: iMovie and Final Cut Pro X for Catalina were crashing, but then I found that iMovie and Final Cut Pro X for High Sierra work fine. The rest all ok.
Trying to plan ahead, so I have a question about using an external boot drive and using on multiple iMacs:
If I create a boot drive using Monterey on a 2017 iMac, I presume this would work on all Monterey supported iMacs? What about on a 2013 iMac - what would happen if I tried to boot? How about if I created the external boot drive on the 2013 iMac using OpenCore - would that boot drive then work on later iMacs?
Thanks in advance
If I create a boot drive using Monterey on a 2017 iMac, I presume this would work on all Monterey supported iMacs? What about on a 2013 iMac - what would happen if I tried to boot? How about if I created the external boot drive on the 2013 iMac using OpenCore - would that boot drive then work on later iMacs?
Thanks in advance