macOS 12 Monterey on Unsupported Macs Thread

[dKupe]

I make a bootable backup on all versions of Monterey using CCC legacy mode. Read the manual.

Dude- I’m the original RTFM guy. Heck I was linking to the CCC manual about this issue in my earlier post. I accomplished all the Bombich troubleshooting per the manual. Legacy mode failed every time. There are lots of reports in numerous forums of failed cloning on devices patched with OCLP.

I’m going to go with the Bombich suggestion of making a standard backup and installing Monterey on top of it to make it bootable. No big deal. But it would be nice to know why some OCLP installations can’t be cloned as bootable.

 

[Sven G]

Hmm… maybe we could begin with seeing what is different, on an OCLP’ed install…? First of all, the modified EFI volume, and then - in root patched installs - at least the disabled SSV and possibly also some disabled SIP components: maybe the quite picky ASR doesn’t like some of these modifications…? Real experts needed, here, anyway: probably not a trivial issue…

 

[Sven G]

… Anyway, returning to the MBP11,1, the occasional “volume hash mismatch” alert doesn’t seem to be due to any adverse effects (everything still works perfectly): probably more a cosmetic issue, than a real problem.

 

[chrickers]

… Anyway, returning to the MBP11,1, the occasional “volume hash mismatch” alert doesn’t seem to be due to any adverse effects (everything still works perfectly): probably more a cosmetic issue, than a real problem.

On my MBP 11,1 also get these messages quite randomly and without any obvious consequences. I can live with it.

 

[peirato]

… Anyway, returning to the MBP11,1, the occasional “volume hash mismatch” alert doesn’t seem to be due to any adverse effects (everything still works perfectly): probably more a cosmetic issue, than a real problem.

On my MBP 11,1 also get these messages quite randomly and without any obvious consequences. I can live with it.

Did you try what shafez wrote on previous page? He said that after disabling some features "volume hash mismatch" doesn't appear anymore on his MBP11,1.

 

[Dewdman42]

Dude- I’m the original RTFM guy. Heck I was linking to the CCC manual about this issue in my earlier post. I accomplished all the Bombich troubleshooting per the manual. Legacy mode failed every time. There are lots of reports in numerous forums of failed cloning on devices patched with OCLP.

I’m going to go with the Bombich suggestion of making a standard backup and installing Monterey on top of it to make it bootable. No big deal. But it would be nice to know why some OCLP installations can’t be cloned as bootable.

Interesting. I wonder why OCLP is failing? I use a more vanilla OC setup, not OCLP because it installs too many hacks, most of which are not needed for many of us. That's just me, and CCC is working fine for me. Sorry to hear you're having these problems. Might be nice to figure out what exactly in OCLP is causing the problem.

 

[Dewdman42]

Hmm… maybe we could begin with seeing what is different, on an OCLP’ed install…? First of all, the modified EFI volume, and then - in root patched installs - at least the disabled SSV and possibly also some disabled SIP components: maybe the quite picky ASR doesn’t like some of these modifications…? Real experts needed, here, anyway: probably not a trivial issue…

Since CCC legacy is working for me with a more vanilla OC (I don't use OCLP), you can eliminate some of the things mentioned. For example, it most likely doesn't have anything to do with SIP being disabled. Every OCLP setup is a little bit different because of the way the user will configure it....and it will auto configure itself, but OCLP does implement quite a few kext hacks...many of which are not actually needed in many cases, but anyway, trying to figure out which one of those might be causing CCC to fail would require an exhaustive process of elimination. Does CCC provide any detailed logging or is there any more info in the console logs at the time of failure?

 

[Dewdman42]

Have this problem, too, with CCC; a recommended workaround is to make first an ordinary data clone, and then install macOS on top of that, in order to have a bootable clone: which works perfectly, even if of course it might take more time.

Where did you find this recommended work around? What I see from Bombich is that the best approach to create a bootable clone without ASR is to do these steps:

1. install MacOS on the destination
2. Using Migration assistant, migrate everything from source drive to destination

 

[Sven G]

Where did you find this recommended work around? What I see from Bombich is that the best approach to create a bootable clone without ASR is to do these steps:

1. install MacOS on the destination
2. Using Migration assistant, migrate everything from source drive to destination

It’s just another way to make a bootable backup, if ASR fails (while the use of Migration Assistant still remains the preferred method):

Creating legacy bootable copies of macOS (Big Sur and later) | Bombich Software

bombich.com

 

[Sven G]

Did you try what shafez wrote on previous page? He said that after disabling some features "volume hash mismatch" doesn't appear anymore on his MBP11,1.

I’ve just begun to apply this workaround: let’s see if it works (it will take some time, to see)…

 

[dKupe]

I’ve just begun to apply this workaround: let’s see if it works (it will take some time, to see)…

Thanks Sven let us know. I'll be there prolly tomorrow. How do guys sleep without a bootable backup LOL? 😉

I presume you'll be running the Mac OS installer from your OCLP USB stick?

 

[dKupe]

Interesting. I wonder why OCLP is failing? I use a more vanilla OC setup, not OCLP because it installs too many hacks, most of which are not needed for many of us. That's just me, and CCC is working fine for me. Sorry to hear you're having these problems. Might be nice to figure out what exactly in OCLP is causing the problem.

Not familiar with which Open Core OC you might be running, but the attraction of OCLP to me was its support for the Kepler Video card in my Late 2013 iMac 14,2- an NVIDIA GeForce GTX 780M 4 GB. I presume you didn't need Kepler support?

 

[d0od]

Just started my first ever OTA update on a MacBook Pro 9,1 having installed Monterey a few weeks back thanks to OpenCore. Wish I'd read this thread before I hit upgrade... 😅

 

[headlessmike]

… Anyway, returning to the MBP11,1, the occasional “volume hash mismatch” alert doesn’t seem to be due to any adverse effects (everything still works perfectly): probably more a cosmetic issue, than a real problem.

On my MBP 11,1 also get these messages quite randomly and without any obvious consequences. I can live with it.

I got rid of them simply by disabling their notifications in the Settings panel for Notification Center.

 

[MacPeasant123]

1) I updated a 2013 retina MBP to Monterey 12.6 OTA with no problem.

2) However the one I'm trying to update now has an interesting situation: it's a 2011 MBP already on Monterey 12.5.1 and I had expected the download size for the updated to be around ~2GB or so. But the Software Update that macOS is showing says the download is 11.48GB, which is even larger than what Mr. Macintosh's website lists as the full update size of 11.3GB.

I've added a screenshot to show this and I hope it uploads correctly.

Whatever the case may be, I'm going ahead with it just to see what happens, as this is not my main Mac so I can afford to have it go sideways. I'll report back later with what happens

 

[MacHosehead]

I had expected the download size for the updated to be around ~2GB or so.

If the 2011 MBP had any post-installation root patches then full installation will be downloaded. Some people remove the patches to do the update. You have to reapply the patches after the update is done anyway. I did the update on three machines and I think it was 1.59GB on all of them.

 

[MacPeasant123]

If the 2011 MBP had any post-installation root patches then full installation will be downloaded. Some people remove the patches to do the update. You have to reapply the patches after the update is done anyway. I did the update on three machines and I think it was 1.59GB on all of them.

Yes, I did apply post-installation root patches before so that explains it, thanks for that info! I'll try to remember to remove the root patches in the future.

I did the update, it went through fine, and like you said, I had to reapply the root patches after the macOS update. That went smoothly as well so OCLP has worked wonders yet again on my old Macs, so big thanks again to the developers!

 

[macpro_mid2014]

W A R N I N G
​

Guys, I've been running Monterey 12.6 and Safari 16 since the release date without serious issues until this morning. I've just recovered my Safari 16 from a nasty bug and I decided to post it here because some of you might be in the same situation.

Starting this morning, Safari started to act strange and quit with an error. No matter what I tried, every time I opened Safari and browse through the tabs, it kicked me out and quit. After reinstalling Monterey 12.6 and Safari 16, the error persisted.

After a while and a moment of despair, I remembered that three days ago, I also installed the Public beta of iOS 16.1 and PINNED all of my Safari's Tab Group's tabs in iOS.
That is the cause of the unexpected exits in Safari, once I unpinned the tabs in iOS, the bug disappeared.
The bug also happens in Safari Technology Preview and Safari 16.1 Beta for macOS.

Thank you.

 

[TimmuJapan]

Since Catalina is going out of service, I finally got around to updating my mbp 9,1 and 9,2 with Monterey 12.6 and OCLP 0.4.10. Both are running great. Catalina is also on a separate volume and boot camp on separate partition, and the OCLP installation did nothing to affect how the other partitions / volumes boot. Everything great! Thank you, OCLP developers.

One anecdote— my 9,1 is a little janky and probably has some kind of slight hardware problem. (which by the way, I can’t diagnose because Apple took away the hardware test on these models🙄)… but anyway, it’s become increasingly difficult to install even a supported OS on this machine via recovery or usb. Always get “ The installer is damaged“ error or “ macOS cannot be installed” error—not just for OCLP, but for any supported Mac OS. I can only do a fresh install on this device if it is with a time machine back up. Weird right?

So, to get Monterey via OCLP on this device, I took out the internal SSD and connected it externally to my 9,2. Installed OCLP Monterey via an external sata to usb cable(until the hello screen), then popped the ssd back inside the 9,1, and finally built and installed an opencore for 9,1, and voila…… perfection!

So even with janky, old hardware, where there is a will, there is a way! 😉

❤️✌🏻OCLP forever!❤️✌🏻

 

[amaze1499]

Anyone else seeing Safari acting up weirdly after the update? Especially while using YouTube. Lagging, freezing, rescaling the clip.... typing within forums is just possible in slow motion

 

[OKonnel]

W A R N I N G
​

Guys, I've been running Monterey 12.6 and Safari 16 since the release date without serious issues until this morning. I've just recovered my Safari 16 from a nasty bug and I decided to post it here because some of you might be in the same situation.

Starting this morning, Safari started to act strange and quit with an error. No matter what I tried, every time I opened Safari and browse through the tabs, it kicked me out and quit. After reinstalling Monterey 12.6 and Safari 16, the error persisted.

After a while and a moment of despair, I remembered that three days ago, I also installed the Public beta of iOS 16.1 and PINNED all of my Safari's Tab Group's tabs in iOS.
That is the cause of the unexpected exits in Safari, once I unpinned the tabs in iOS, the bug disappeared.
The bug also happens in Safari Technology Preview and Safari 16.1 Beta for macOS.

Thank you.

Good boy! I hope you immediately reported the bug to Apple via Feedback Assistant.
If you do this clearly and completely, Apple always steps in, in its own interest.

Some example
With iOS 16 Beta I had reported AirPlay not working between my iPhone XS and my iMac (unsupported… ) with Monterey and Apple responded, asked me for more info and logs and proceeded to solve the issue.
I pointed out that with iOS 16.1 Beta the scrolling of the Apps, in the home’s folders, doesn’t works and that you can scroll them only by moving j dots down in the folders; but it still works poorly and jerky.

I suggest, however, to use Feedback Assistant from the iPhone since for several years now, unfortunately, Apple has been more attentive and involved in development of iOS and less involved in the issues and to development of macOS. Probably even the staff of internal developers is now biased in favor of the Engineers for iOS and iPadOS.

Good luck

 

[amaze1499]

Out of curiosity: I am on a MBA 13" mid 2012 here. Eversince I couldnt get AppeTV to work. To be more specific: whenever i try to start any show or stream the window opens up, sometimes plays the trailer but then stops or closes again. Regardless the settings. Anyone else?

 

[OKonnel]

Since Catalina is going out of service, I finally got around to updating my mbp 9,1 and 9,2 with Monterey 12.6 and OCLP 0.4.10. Both are running great. Catalina is also on a separate volume and boot camp on separate partition, and the OCLP installation did nothing to affect how the other partitions / volumes boot. Everything great! Thank you, OCLP developers.

One anecdote— my 9,1 is a little janky and probably has some kind of slight hardware problem. (which by the way, I can’t diagnose because Apple took away the hardware test on these models🙄)… but anyway, it’s become increasingly difficult to install even a supported OS on this machine via recovery or usb. Always get “ The installer is damaged“ error or “ macOS cannot be installed” error—not just for OCLP, but for any supported Mac OS. I can only do a fresh install on this device if it is with a time machine back up. Weird right?

So, to get Monterey via OCLP on this device, I took out the internal SSD and connected it externally to my 9,2. Installed OCLP Monterey via an external sata to usb cable(until the hello screen), then popped the ssd back inside the 9,1, and finally built and installed an opencore for 9,1, and voila…… perfection!

So even with janky, old hardware, where there is a will, there is a way! 😉

❤️✌🏻OCLP forever!❤️✌🏻

Years ago I had similar problems with two identical 2010 MBP 13” where I installed Catalina with the dosdude1 patch. In a MBP the installation was always good, in the other it was not. I attributed the cause to the different brand of SSD. But it was all solved when I found a "low level" RAM test to use by USB boot. One of the extensive tests, in fact, allowed me to find out that the RAM was faulty. So, after purchasing a new Crucial RAM (with 2-2-2-2 timing) this MBP also became perfect and no longer showed difficulties or strange messages during Catalina installation.

 

[chrickers]

Did you try what shafez wrote on previous page? He said that after disabling some features "volume hash mismatch" doesn't appear anymore on his MBP11,1.

Yes, i read that. And I may have jinxed it, because today I got the notification again. I set the feature unlock status to partially enabled. Let's see if that'll help 👍

 

[herrdude]

Has anyone upgraded to 12.6 on 2011 iMac that was upgraded with a Kepler graphics card?