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
1. There is no need to run Migration Assistant (MA) if you update from B9 to B10.
2. If you install B10 on to an empty partition and use MA app for data restoration, don't select system data.
3. Try PRAM reset 1st by pressing the space bar at the start of the boot and select PRAM reset icon, if you use OCLP.
Last edited:
Yah. How can I put this... I know very well there is no need to run migration assistant 
I ran it for a specific reason, to get my data files refreshed from production. Jeesh.
Just wondering, what is MS? Microsoft? Multiple Sclerosis?
Also, how does one install anything from an empty disk?
I might try your PRAM reset though, thank you.
I ran it for a specific reason, to get my data files refreshed from production. Jeesh.
Just wondering, what is MS? Microsoft? Multiple Sclerosis?
Also, how does one install anything from an empty disk?
I might try your PRAM reset though, thank you.
Last edited:
'09 Mini3,1 OCLP_030 Offline Variant installed Beta 10 OTA atop suspect b9, went unattended to boot into Build #21A5552a - applied OCLP Step #3, restart. Promising but Magic Trackpad seen as mouse, Bluetooth C/P reports Bluetooth permanently OFF Trackpad MIA. Not good PITA, Magic Trackpad is a lousy mouse. Worked well in b9 and previous. (Noticed Beta 10 B/T driver is for mid-2014 Macs and newer but after a reboot the entry vanished. USB Device Tree reports BRCM2046 using no power.) Wi-Fi works, post-patch. C/Ps are a minefield of "Preferences Error." Fortunately, the over-install grabbed most of the previous version C/P settings. Graphics smooth and crisp exactly like unsupported Big Sur and Catalina.
A little snapshot upkeep tmutil thinlocalsnapshots / 999999999999999 4 seems to have fixed the crashing apps cascade lockout seen post-b6.
Magic Trackpad is a lousy mouse. Worked well in b9 and previous. (Noticed Beta 10 B/T driver is for mid-2014 Macs and newer but after a reboot the entry vanished. USB Device Tree reports BRCM2046 using no power.) Wi-Fi works, post-patch. C/Ps are a minefield of "Preferences Error." Fortunately, the over-install grabbed most of the previous version C/P settings. Graphics smooth and crisp exactly like unsupported Big Sur and Catalina. A little snapshot upkeep tmutil thinlocalsnapshots / 999999999999999 4 seems to have fixed the crashing apps cascade lockout seen post-b6.
Last edited:
See next post'09 Mini3,1 OCLP_030 Offline Variant installed Beta 10 OTA atop suspect b9, went unattended to boot into Build #21A5552a - applied OCLP Step #3, restart. Promising but Magic Trackpad seen as mouse, Bluetooth C/P reports Bluetooth permanently OFF Trackpad MIA. Not good PITA,
A little snapshot upkeep tmutil thinlocalsnapshots / 999999999999999 4 seems to have fixed the crashing apps cascade lockout seen post-b6.
View attachment 1865299
View attachment 1865295
Last edited:
I am having a problem with a full 12.0 beta 10 USB installer built using the most recent 0.3.0 nightly OCP on an erased SSD on a MacPro 3,1.
With about 14 minutes to complete it displays the following screen notifying that a required firmware update could not be installed! It looks to me like there is an issue with the 0.3.0 OCP nightly and this recent beta.
With about 14 minutes to complete it displays the following screen notifying that a required firmware update could not be installed! It looks to me like there is an issue with the 0.3.0 OCP nightly and this recent beta.
Had the same problem with migration assistant (post 1966).
Using CCC data-only copying instead, and then installing the OS over the result, worked. CCC data-only is probably good to resync user data later, I think I saw this suggested by someone but didn‘t find it back.
Migration assistant without system data, as suggested by TigerA, I‘ll try for my next clean install.
Thanks hvds. I decided to delete the whole Monterey beta volume while logged in to Big Sur using disk utility. I then recreated it as a new, empty, volume.
While still in Big Sur I downloaded the beta 10 full installer inked to on Mr Macintosh's site. Unzipped the .dmg file, ran the installer .app and selected the newly created Monterey beta volume for the install location.
It's still running as we speak. When it's done next step will be to run the OCLP rebuild on Big Sur, and the OCLP drive install directed to the new Monterey beta volume. Then to test booting it.
I'll check out your post #1966. Looks like a bug in migration assistant to me, at this stage. That might be showstopper for release until fixed, a lot of people are going to running migration.
While still in Big Sur I downloaded the beta 10 full installer inked to on Mr Macintosh's site. Unzipped the .dmg file, ran the installer .app and selected the newly created Monterey beta volume for the install location.
It's still running as we speak. When it's done next step will be to run the OCLP rebuild on Big Sur, and the OCLP drive install directed to the new Monterey beta volume. Then to test booting it.
I'll check out your post #1966. Looks like a bug in migration assistant to me, at this stage. That might be showstopper for release until fixed, a lot of people are going to running migration.
Last edited:
Not sure if this is a good idea to have Big Sur and Monterey in the same partition with different volume. It may cause a lot of issues. I am not familiar with Apple's file system, but I remember I read somewhere before that it's far better to have a separate partition for each macOS.
not really: this forums' title says it all: "Unsupported ...." ?
I think I may have seen that or something similar.
Not 100% but my experience with Migration Assistant is that it might also restore incompatible system setup files that corrupt a newer install.
My fix is to skip the restore of system settings when restoring from Time Machine.
Has helped me so far, as I have not seen it when doing this. FWIW. YMMV.
Hi sorry I have so many it’s probably not worth it…
but…
i have a 2015 MacBook 12 doesn’t work,
A 2011 iMac 27 doesn’t work
And even a 2020 M1 Mac mini it stopped working there too so I guess they’ve broken it?
Hi, did you try to install it on another ssd drive?
NVRAM? Boot-args keepsyms = 1 debug = 0x100 shikigva = 128 unfairgva = 1 agdpmod = pikera -wegtree -v
csr-active-config 00000000
This is quite simple if you take a look at the download page:
The 0.2.5 is as of now the current release.
The nightly builds reflect the daily updates and fixes and enhancements made by the crew of developers. I can only assume that the big jump in version numbering is a planned move to make the upcoming 0.3.0 release in a few days the supported OCLP version with the expected final release of macOS 12.0 Monterey.
The TUI is always on top of the the functionality, the GUI simplifies for a good reason the number of available options to a reasonable smaller number.
So I can only recommend to use the TUI with the latest nightly builds if you need special settings and plan to do adjustments yourself.
Note:
Currently there is a real good reason to use the 0.3.0 nightly builds with all systems pre 2011 because of the SurPlus patch solving the race condition problem.
Edit:
As of today the current release is 0.3.0 (10/16/2021)
Last edited:
Great news with latest BlueToolFixup.kext only need this kexts for USB Bluetooth dongle ?
Testing with 4 dongle brand and its work perfect Injected from OC 0.7.5
Testing with 4 dongle brand and its work perfect Injected from OC 0.7.5
Last edited:
Yes, I was getting uneasy about the dual boot setup using dynamic space volumes but I guess I had been lucky up until now.
I've gone to an external SSD via USB for Monterey beta. I removed the volume on the internal drive I'd been installing it on. Monterey beta is now back in business on the external drive, and the internal SSD is only running one version of macOS. I feel much better!
Last edited:
Hi guys, some time ago, I took an SSD off an MBP9,1 that died. On it was Big Sur installed with OCLP (which version I don't remember). Now I am using a MBP12,1 running Big Sur, from which I slave the SSD from the old machine as an external drive, and upgraded it to Monterey. It has worked well, so far. However, an EFI Boot partition shows up when I boot into the external drive using the Alt key. I don't know how to remove it. I know the EFI partition is on the slaved SSD, but how do I access it to delete it? Any advice will be greatly welcome. I know the MBP12,1 is supported natively for Monterey, but I'd rather ask you guys. Thank you.
Last edited:
Oh sorry to read it did not work with an empty disk. That is the solution I would have suggested, as it worked for me.
That being said, it worked with beta 6. I didn’t not try with beta 10.
MacBook Pro 5,2 (mid 2009) 8 GB of RAM, internal EVO SSD, Multi-boot: Catalina, BigSur, Monterey Beta10,
Nvidia GE Force 9600GT 512 MB
I've had same error message ( ... required firmware could not be updated) when installing B10 from USB thumb drive with OCLP 0.3.0, and when attempting (thereafter) installation using OCLP 0.2.5. In former case (0.3.0), more then one installation was attempted; each time the Post Install Volume patch was run, it would cause boot process to stall soon after (necessary) reboot.
Had to download Beta 10 full installer onto internal drive with BigSur partition, erase Monterey partition, and then install Beta 10 onto its own partition form BigSur.
Installtion from BigSur partition was successful, however, the OCLP 0.3.0 post install patches would always cause Kernel panic. The OCLP 0.2.5 allowed installation of Beta10, and post install volume patches (after fresh Monterey B10 install)
Still, the display panel in system preferences only shows one [default] resolution and there is no screen brightness adjustment)
While OCLP 0.2.5 seems to have provided graphic acceleration, it causes Window Server to crush every time an item on the right side of the menu bar is "clicked"; there was no such problem before volume patches were applied (of course there was also no graphic acceleration). The menu bar and dock are not translucent, but window movement across the screen and window minimizing is very smooth).
Just to provide complete background; my first installation, using OTA over beta 9, went well but OCLP 0.2.5 could not invoke graphic acceleration; subsequent application of the OCLP 0.3.0 volume patches, in an attempt to achieve graphic acceleration, resulted in the described issues.
This is a report associated with use of two OCLP variants on my machine, which hopefully may lead to resolution (everyone understands the risks).
Addendum: Monterey Beta10 Window Server currently crashes (randomly) without any "provocation".
***Update 10.16.21:utilizing OCLP 0.3.1 resulted in same problems with window server, see attached:
Nvidia GE Force 9600GT 512 MB
I've had same error message ( ... required firmware could not be updated) when installing B10 from USB thumb drive with OCLP 0.3.0, and when attempting (thereafter) installation using OCLP 0.2.5. In former case (0.3.0), more then one installation was attempted; each time the Post Install Volume patch was run, it would cause boot process to stall soon after (necessary) reboot.
Had to download Beta 10 full installer onto internal drive with BigSur partition, erase Monterey partition, and then install Beta 10 onto its own partition form BigSur.
Installtion from BigSur partition was successful, however, the OCLP 0.3.0 post install patches would always cause Kernel panic. The OCLP 0.2.5 allowed installation of Beta10, and post install volume patches (after fresh Monterey B10 install)
Still, the display panel in system preferences only shows one [default] resolution and there is no screen brightness adjustment)
While OCLP 0.2.5 seems to have provided graphic acceleration, it causes Window Server to crush every time an item on the right side of the menu bar is "clicked"; there was no such problem before volume patches were applied (of course there was also no graphic acceleration). The menu bar and dock are not translucent, but window movement across the screen and window minimizing is very smooth).
Just to provide complete background; my first installation, using OTA over beta 9, went well but OCLP 0.2.5 could not invoke graphic acceleration; subsequent application of the OCLP 0.3.0 volume patches, in an attempt to achieve graphic acceleration, resulted in the described issues.
This is a report associated with use of two OCLP variants on my machine, which hopefully may lead to resolution (everyone understands the risks).
Addendum: Monterey Beta10 Window Server currently crashes (randomly) without any "provocation".
***Update 10.16.21:utilizing OCLP 0.3.1 resulted in same problems with window server, see attached:
Last edited:
lolol, man your funny but glad they fixed it for all our sake!Apple killed the BRCM2046 in Beta 10.
And the OCLP_N just now posted fixes it.
Beta 10 OTA atop b9 runs better than previous Betas on this minimal Mini w/ OCLP 030_N TUI, makes it useful, once more.
Last edited: