macOS 12 Monterey on Unsupported Macs Thread

[Diggi]

I already told you where to gather the in depth information you need to do manual changes. Guess you will be able to find the thread knowing its name? Just read my few posts, again.

You should double check who has/had access to you MacPro and who installed the High Sierra macOS before you got the system. There was an OpenCore installation (most likely hidden on the EFI partition of your disk) on this system according to the OCLP error message and the MacPro booted it.

I bought this computer brand-new over a decade ago. No one but me has ever had access to this computer, ever… unequivocally.
I installed hi Sierra. I had to because the open core products would not work, and gave me crazy errors (as you have witnessed)

Look at the screenshot I posted where my system says that I am on a mod-2010 Mac Pro, 5,1 … But the Open Core software says that I am on a MacBook Pro 6,2.

The only thing I have ever done is change the boot ROM to 144. 00 and upgrade the software operating system to hi Sierra. Other than that, that’s it.

And I’ll say it again and for the last time: no one has ever touched this machine. No one except me. OCLP has a problem where it thinks that my machine (and possibly others , I don’t know) is something other than it is.

Thanks for responding to all of my posts. Your help has been, appreciated…

 

[serafin79]

I bought this computer brand-new over a decade ago. No one but me has ever had access to this computer, ever… unequivocally.
I installed hi Sierra. I had to because the open core products would not work, and gave me crazy errors (as you have witnessed)

Look at the screenshot I posted where my system says that I am on a mod-2010 Mac Pro, 5,1 … But the Open Core software says that I am on a MacBook Pro 6,2.

The only thing I have ever done is change the boot ROM to 144. 00 and upgrade the software operating system to hi Sierra. Other than that, that’s it.

And I’ll say it again and for the last time: no one has ever touched this machine. No one except me. OCLP has a problem where it thinks that my machine (and possibly others , I don’t know) is something other than it is.

Thanks for responding to all of my posts. Your help has been, appreciated…

If I look into my crystal ball, this is what I get from your posts.

You have tried to install a newer version of MacOS using OCLP that your Mac Pro does not support and it failed.
Then you installed Hi Sierra on your Mac Pro.
If my crystal ball is correct that means OCLP was installed on the EFI partition when the failed attempt happened and it is now giving you grief and you need to follow Ausdauersportler advise

 

[Ausdauersportler]

And I’ll say it again and for the last time: no one has ever touched this machine. No one except me. OCLP has a problem where it thinks that my machine (and possibly others , I don’t know) is something other than it is.

The single screen shot (you posted before) shows a few things:

1. You have indeed a MacPro5,1

2. The OCLP man GUI windows recognizes your system correctly as a MacPro5,1 (printed nearly on top of the bottom GUI window)

2. For a yet unknown reason the same OCLP program believes to have found a booted OpenCore version (either on your main disk or on an external device like an USB thumb drive) which has been wrongly configured to be used with a MacBookPro6,2 (printed on the top alert window).

So your statement is simply not true. You do not understand the messages printed and you do not understand what I was trying to explain.

 

[JedNZ]

The only thing I have ever done is change the boot ROM to 144. 00 and upgrade the software operating system to hi Sierra. Other than that, that’s it.

Very strange indeed, but regardless of why this is the case, the advice from @Ausdauersportler for sorting this is solid.

So consider downloading direct from the source, delete everything in your EFI folder (and empty the trash can) and start again.

Also, check the EFI partition on other drives to make sure you there isn’t another OpenCore build sitting on another drive. Drive numbering (disk#s#) can alter between reboots, and blessing the wrong EFI drive isn’t difficult to do, even for those of us who have been playing with OpenCore for a while.

Let us know how you go. There’s amazing talent here who will help you get this sorted.

 

[Diggi]

The single screen shot (you posted before) shows a few things:

1. You have indeed a MacPro5,1

2. The OCLP man GUI windows recognizes your system correctly as a MacPro5,1 (printed nearly on top of the bottom GUI window)

2. For a yet unknown reason the same OCLP program believes to have found a booted OpenCore version (either on your main disk or on an external device like an USB thumb drive) which has been wrongly configured to be used with a MacBookPro6,2 (printed on the top alert window).

So your statement is simply not true. You do not understand the messages printed and you do not understand what I was trying to explain.

Thanks for your kindness, understanding very thoughtful replies.

 

[Diggi]

Very strange indeed, but regardless of why this is the case, the advice from @Ausdauersportler for sorting this is solid.

So consider downloading direct from the source, delete everything in your EFI folder (and empty the trash can) and start again.

Also, check the EFI partition on other drives to make sure you there isn’t another OpenCore build sitting on another drive. Drive numbering (disk#s#) can alter between reboots, and blessing the wrong EFI drive isn’t difficult to do, even for those of us who have been playing with OpenCore for a while.

Let us know how you go. There’s amazing talent here who will help you get this sorted.

Yes, he's been extremely kind and willing to help.

 

[Diggi]

"You" asked me not to say anything, but I have to:

Thank you for diagnosing the problem with OCLP and my machine, and for believing that I have NEVER had an MBP and that I haven't altered my machine in some way> YOU fixed this will a cursory look at OCLP and sent me a simple yet elegant solution. Please reach out to the OCLP people and explain that which I could not.

Thank you again, madame.

 

[Diggi]

Very strange indeed, but regardless of why this is the case, the advice from @Ausdauersportler for sorting this is solid.

So consider downloading direct from the source, delete everything in your EFI folder (and empty the trash can) and start again.

Also, check the EFI partition on other drives to make sure you there isn’t another OpenCore build sitting on another drive. Drive numbering (disk#s#) can alter between reboots, and blessing the wrong EFI drive isn’t difficult to do, even for those of us who have been playing with OpenCore for a while.

Let us know how you go. There’s amazing talent here who will help you get this sorted.

Thank you JedNZ. I have no idea what it means to "bless" a drive and there is only one SSD in this machine at the time of writing this. Someone reached out to me and sent me a "fix". I now have Monterey installed on my machine and apparently needs no other patches, etc.

Thank you again JedNZ.

 

[hvds]

Apologies if too late to the party, but are you saying that I could "restore" a CCC backup of an APFS Big Sur volume group (Macintosh HD and Macintosh HD - Data) to an erased drive, run through the OCLP procedure to install Monterey to it (without erasing the drive in the OCLP process), and that Monterey would then have the same settings, same apps installed, and same data (barring a conflict) as the Big Sur installation?

Yes. I erased an SSD, then ran CCC to make a data-only clone of my Big Sur system on this SSD, then installed Monterey on it from a USB installer using OCLP. Did the same when (experimentally) going from Monterey to Ventura.
To reduce risk, I'm always using an external target SSD for such operation. The internal production SSD remains untouched.
Common resources like NVRAM settings or importantly, firmware chips could be affected, but that wasn't observed since very long now.

 

[OKonnel]

Yes. I erased an SSD, then ran CCC to make a data-only clone of my Big Sur system on this SSD, then installed Monterey on it from a USB installer using OCLP. Did the same when (experimentally) going from Monterey to Ventura.
To reduce risk, I'm always using an external target SSD for such operation. The internal production SSD remains untouched.
Common resources like NVRAM settings or importantly, firmware chips could be affected, but that wasn't observed since very long now.

An important question: after installing Big Sur or Monterey and before creating the User Home, "Migration Assistant" does it fully recognize an external disk backup made with Carbon Copy Cloner? And does macOS accept it to complete data and settings restore (including various email accounts, etc.)? Are you sure? Thank you

 

[hwojtek]

And I’ll say it again and for the last time: no one has ever touched this machine. No one except me. OCLP has a problem where it thinks that my machine (and possibly others , I don’t know) is something other than it is.

No, OCLP recognizes your computer correctly. It is cleanly visible in your screenshot.
Also what is visible is that you probably DO have OpenCore installed, in fact with a configuration for a Macbook Pro.

If you wouldn't mind, please open the Terminal and copy/paste exactly the line below, followed by pressing enter:
nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version
Post a screenshot of the window after the result shows up. This will help troubleshoot your issue.

 

[davidlv]

An important question: after installing Big Sur or Monterey and before creating the User Home, "Migration Assistant" does it fully recognize an external disk backup made with Carbon Copy Cloner? And does macOS accept it to complete data and settings restore (including various email accounts, etc.)? Are you sure? Thank you

Yes MA does recognize a CCC backup disk. It even worked with Big Sur when the backup disk was made with Monterey (which surprised me greatly), but of course, one app that was specific to Monterey had to be changed for the Big Sur version (Onyx). I used a Volume (1 of 3) created on a Buffalo 512GB USB 3 SSD.
No issues noted.

 

[hvds]

An important question: after installing Big Sur or Monterey and before creating the User Home, "Migration Assistant" does it fully recognize an external disk backup made with Carbon Copy Cloner? And does macOS accept it to complete data and settings restore (including various email accounts, etc.)? Are you sure? Thank you

I don't know, didn't use Migration Assistant for quite a while. I always went as described, by making a data-only clone of the source system with CCC, then installed macOS on it.
To really know, would have to make a clean Monterey installation and then try Migration Assistant (a) from a "pure" CCC clone without macOS installed on it in addition, (b) with macOS installed on it. Could do that in the next days and let you know.

 

[Diggi]

No, OCLP recognizes your computer correctly. It is cleanly visible in your screenshot.
Also what is visible is that you probably DO have OpenCore installed, in fact with a configuration for a Macbook Pro.

If you wouldn't mind, please open the Terminal and copy/paste exactly the line below, followed by pressing enter:
nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version
Post a screenshot of the window after the result shows up. This will help troubleshoot your issue.

 

[hwojtek]

Thanks, I was just a bit too late (as you have already solved this issue when I posted this) and what you are seeing now is the Open Core you intentionally installed on the computer. However, if you wanted to check for Open Core back then, when OCLP complained about OC being installed and configured for a Macbook Pro and you didn't recall installing it - that is the command you would use to check whether Open Core is booted on the computer.

 

[davidlv]

"You" asked me not to say anything, but I have to:

Thank you for diagnosing the problem with OCLP and my machine, and for believing that I have NEVER had an MBP and that I haven't altered my machine in some way> YOU fixed this will a cursory look at OCLP and sent me a simple yet elegant solution. Please reach out to the OCLP people and explain that which I could not.

Thank you again, madame.

When you can, could you post the "simple yet elegant solution" you used to solve your issue?
I am interested and I am sure others would like to know how you solved the issue. Thanks!

 

[Diggi]

Thanks, I was just a bit too late (as you have already solved this issue when I posted this) and what you are seeing now is the Open Core you intentionally installed on the computer. However, if you wanted to check for Open Core back then, when OCLP complained about OC being installed and configured for a Macbook Pro and you didn't recall installing it - that is the command you would use to check whether Open Core is booted on the computer.

Very good. Thank you. As I mentioned, there isn’t a MacBook at this location, so installing it to such would have been impossible. OCLP threw the error - in error.

 

[Diggi]

When you can, could you post the "simple yet elegant solution" you used to solve your issue?
I am interested and I am sure others would like to know how you solved the issue. Thanks!

Apparently this problem will be fixed in an updated version of OCLP. That’s all I can tell you, right now.

 

[Ausdauersportler]

Apparently this problem will be fixed in an updated version of OCLP. That’s all I can tell you, right now.

Can you disclose who from the OCLP development team has confirmed the bug and promised there will be fix in an upcoming version of OCLP?

 

[dKupe]

TL;dr- Any reason not to practice with OCLP and Monterey on my internal 128gb blade SSD?

Hey gang-

Just finished upgrading my late-2013 iMac 27" (iMac 14,2) with a 4TB Western Digital SSD. The stock internal 3TB Seagate HDD was throwing SMART errors, so I had to make a decision and this will put me in good shape for Monterey and OCLP. Thank you OWC and iFixit! And especially Mr. Macintosh on Youtube and Khronokernel here!

So here's my question. With my new 4TB SSD purring along, I now also have the internal 128gb blade SSD mounted on my Desktop (left over from the 3TB Fusion Drive). I've erased and formatted it APFS. It occurs to me that would be a great drive to practice with OCLP and Monterrey. I know it's small, but sounds like it's adequate for an install of Monterrey. (I also have the 32GB USB flash drive to be used during the OCLP install).

So, any reason to not install Monterrey with OCLP on my internal 128gb blade SSD? EDIT: My intent would be to continue running Catalina on my 4TB SSD for awhile until I feel proficient with OCLP.

Thanks!

 

[Ausdauersportler]

So, any reason to not install Monterrey with OCLP on my internal 128gb blade SSD?

Go ahead, should work fine for test installations. Keep in mind that updates need a lot of space, so do not add too much personal data to this small disk.

 

[Diggi]

i’m just trying to do my best. I’m an old man, but I’m not feeble …yet… Someone offered me a solution, asked me not to explain it and said that this bug would be fixed in the next instance/iteration/update of OCLP. It worked. if I was reading this from somebody else I would think “great “!. This solved the person‘s problem. I wouldn’t question it, I’d just be delighted that that person found some sort of fix.

Onward – OK? Thank you everybody for helping me.

 

[Ausdauersportler]

i’m just trying to do my best. I’m an old man, but I’m not feeble …yet… Someone offered me a solution, asked me not to explain it and said that this bug would be fixed in the next instance/iteration/update of OCLP. It worked. if I was reading this from somebody else I would think “great “!. This solved the person‘s problem. I wouldn’t question it, I’d just be delighted that that person found some sort of fix.

Onward – OK? Thank you everybody for helping me.

Unfortunately there is no such bug and no change request and surely no upcoming change, but there is a simple way to create the error message you have seen by changing the target model from MacPro5,1 to MacBookPro6,2. Unfortunately this needs some user intervention. Unfortunately the single user having access to this machine is not able to remember the key strokes he made when starting the app the first time.

 

[dKupe]

Go ahead, should work fine for test installations. Keep in mind that updates need a lot of space, so do not add too much personal data to this small disk.

Thank you! Do I need to be concerned that OCLP might write to the Catalina installation on my main SSD? I tend to be slow and meticulous so trying to be very careful to keep all this only on the internal blade SSD and the USB flash drive until I have learned OCLP.

 

[Diggi]

Please check the forum rules again and post using the English language.

Unfortunately there is no such bug and no change request and surely no upcoming change, but there is a simple way to create the error message you have seen by changing the target model from MacPro5,1 to MacBookPro6,2. Unfortunately this needs some user intervention. Unfortunately the single user having access to this machine is not able to remember the key strokes he made when starting the app the first time.

We should stop playing children's games here...you never talked to any OLCP developer.
First posts were just helpless, now you are starting to publish simply false facts. What comes next?

I don’t have a MacBook. I’ve said it several times… If this is directed at me - know that I don’t have a MacBook. I have an old 2010 Mac Pro. Aside from my iPhone that’s all I have.

I didn’t say that I talked to an OCLP developer. I said someone “someone“ sent me a fix and it worked. Well it didn’t work entirely… But it worked well enough that I was able to install OCLP in Monterey. I’m going back to Catalina because Monterey doesn’t work well on this particular machine, and I don’t know why… I’m not an engineer, I’m not a programmer… I’m an old man just asking for a little help, and someone did.

Am I guilty of someone helping me? I guess so. Is it wrong for someone to offer me a solution privately? I didn’t read anything in your rules that stated so.