MP 1,1-5,1 My trusty 5,1 won’t let me create a boot drive using OpenCore/Monterey.

[Diggi]

I go through all of the steps, and it gives me the error message shown below. I just installed Catalina on this old 2010 Mac, without any problems whatsoever… But it won’t let me get past creating the installer for Monterey.

I would be grateful for some advice.

 

[paronga]

Could be an issue with the DMG being corrupt? Perhaps the download had an issue?

 

[Diggi]

Could be an issue with the DMG being corrupt? Perhaps the download had an issue?

I have downloaded it three times and placed it in the applications folder, or the desktop just to see if that made a difference. It didn’t of course. The install package that PKG is over 12 gigs, but the installer itself is about five gigs… In any case I’ve done it that many times and every time I get to that screen, it fails there. I even tried changing the thumb drive from GUID to master boot record, just to see what would happen. Clearly that’s not going to make a difference, but I really tried everything that I can think of. Somebody somewhere I’m sure knows or is familiar with the screen and perhaps can point me in the right direction. Thank you for your reply.

 

[paalb]

I have had problems with installers giving errors like that. Selecting an other way of downloading solved it. This page lists 8 different ways https://mrmacintosh.com/how-to-download-macos-catalina-mojave-or-high-sierra-full-installers/

 

[Diggi]

I have had problems with installers giving errors like that. Selecting an other way of downloading solved it. This page lists 8 different ways https://mrmacintosh.com/how-to-download-macos-catalina-mojave-or-high-sierra-full-installers/

Thank you friend. I have to download the installer to an old mbp running high sierra (unfortunately). And because the only other way i can find to get Catalina or Monterey is through the app store links, I have no other option but to get it through the OpenCore download.

My Terminal won't give me a download, even when I copy and paste the command line perfectly. In every case, that just brings me to "help" screen in terminal.

Its frustrating. OPenCore doesn't work for me because I am too dense to understand every detail.... and so far I've only been able to upgrade my 2010 mac pro to any different, is via the dosdude catalina patcher.

Is there ANY direct link to Monterey (or even Big Sur) that won't otherwise refuse my attempt to download because I'm using an old MBP for such?

 

[Macschrauber]

OpenCore on the Mac Pro

This guide explains how to use the excellent OpenCore boot loader to install, run, and update the latest version of macOS on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.

forums.macrumors.com

search for Full Installer

 

[Diggi]

OpenCore on the Mac Pro

This guide explains how to use the excellent OpenCore boot loader to install, run, and update the latest version of macOS on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.

forums.macrumors.com

search for Full Installer

Thank you.

That's what I thought I'd been doing, but obviously not effectively. ... and, I downloaded it 3 times using the OpenCore utility. Each one was the exact same size, and I couldn't get the thing to finish making a usb drive to install monterey.

So, I'm trying to find another link to the full installer.

 

[Macschrauber]

You will better read, it describes a method with installinstallmacos.py

 

[krakman]

Use open core legacy patcher. It makes the process easier.

Search OCLP on git hub

 

[paalb]

Use open core legacy patcher. It makes the process easier.

Search OCLP on git hub

Have a look at the screenshot in first post. The error is from OCLP.

 

[Diggi]

Other than open core, I can’t seem to find a direct link to download that OS. I’m on a 2010 Mac Pro 5,1 with 144.00 bootrom. It seems there lots of links to ways you can finagle a possible download going through terminal, etc. but none of that has worked for me.

 

[Diggi]

Right now I want to try to use RomTool to successfully clear the boot ROM before I break the machine. And so far, I haven’t been able to do it with that tool (with SIP disabled, mind you)

 

[Stex]

Right now I want to try to use RomTool to successfully clear the boot ROM before I break the machine. And so far, I haven’t been able to do it with that tool (with SIP disabled, mind you)

When you mention you are trying to clear the BootROM, could you provide more details as to what BootROM are you trying to flash? Is it a reconstructed BootROM or an old backup of yours?

 

[Macschrauber]

Right now I want to try to use RomTool to successfully clear the boot ROM before I break the machine. And so far, I haven’t been able to do it with that tool (with SIP disabled, mind you)

You can't clear the boot rom with RomTool. You can just dump it. Clearing the boot rom is a manual procedure. @tsialex is the mastermind what offers that service.

I made a combined tool to dump and analyse the bootrom.

with demonstration in YouTube:

https://forums.macrumors.com/threads/healthy-nvram-normal-behaviour-on-4-1-5-1-machines.2333460/post-30948082

latest version:

https://forums.macrumors.com/threads/healthy-nvram-normal-behaviour-on-4-1-5-1-machines.2333460/post-31048702

 

[paalb]

You can use appstore. I have done that many times. You just quit the installer and then you can pick it out from the Application folder.

 

[Diggi]

You can't clear the boot rom with RomTool. You can just dump it. Clearing the boot rom is a manual procedure. @tsialex is the mastermind what offers that service.

I made a combined tool to dump and analyse the bootrom.

with demonstration in YouTube:

https://forums.macrumors.com/threads/healthy-nvram-normal-behaviour-on-4-1-5-1-machines.2333460/post-30948082

latest version:

https://forums.macrumors.com/threads/healthy-nvram-normal-behaviour-on-4-1-5-1-machines.2333460/post-31048702

Sorry, I meant "dump"....

I managed to get your .dmg and would like to post the log file(s)... but it is greyed-out when I try to pick it using the attachment option on this forum. I grabbed all that I could see and zipped it instead...

 

[tsialex]

Sorry, I meant "dump"....

I managed to get your .dmg and would like to post the log file(s)... but it is greyed-out when I try to pick it using the attachment option on this forum. I grabbed all that I could see and zipped it instead...

Remove the attachment above, it probably contains a lot of personal data, like your AppleID/iCloud email, your name, your Wireless credentials, besides all the serial numbers to clone your Mac Pro…

Btw, you are using a MacBookPro6,2 as your OCLP model, this will never work…

 

[Diggi]

Remove the attachment above, it probably contains a lot of personal data, like your AppleID/iCloud email, your name, your Wireless credentials, besides all the serial numbers to clone your Mac Pro…

Btw, you are using a MacBookPro6,2 as your OCLP model, this will never work…

That’s another thing, I keep getting a message every time I open OC on this 2010 Mac Pro - it says I’m on an MBP! I’m not! I don’t have one!

 

[tsialex]

That’s another thing, I keep getting a message every time I open OC on this 2010 Mac Pro - it says I’m on an MBP! I’m not! I don’t have one!

This is very weird by itself, I don't even know how this could be detected incorrectly since it's based on the modelID of your Mac.

Seems the most sane course of action right now is to step back and do a clean install of HighSierra/Mojave with a small SSD/HDD and then start from scratch - you gonna need a HighSierra/Mojave install as a rescue/flashing disk anyway.

 

[Macschrauber]

That’s another thing, I keep getting a message every time I open OC on this 2010 Mac Pro - it says I’m on an MBP! I’m not! I don’t have o

Sorry, I meant "dump"....

I managed to get your .dmg and would like to post the log file(s)... but it is greyed-out when I try to pick it using the attachment option on this forum. I grabbed all that I could see and zipped it instead...

the tool says dont post or publish your serial numbers fot a reason. Alex explained.

 

[Diggi]

This is very weird by itself, I don't even know how this could be detected incorrectly since it's based on the modelID of your Mac.

Seems the most sane course of action right now is to step back and do a clean install of HighSierra/Mojave with a small SSD/HDD and then start from scratch - you gonna need a HighSierra/Mojave install as a rescue/flashing disk anyway.

I’ve been on high Sierra while attempting all of this.

 

[tsialex]

I’ve been on high Sierra while attempting all of this.

If I've had this Mac Pro to diagnose, I'd nuke this install. I don't know what exactly you did, but I'm sure that you don't have a working install since you already wrote a list of things that are not working correctly and I wouldn't lose any time trying to debug it.

 

[Diggi]

It’s crazy, indeed.

I’ve had this machine for over a decade. It’s almost never been connected to the internet and I’ve been running my recording studio with it for eons.

I go to upgrade some components, update the bootrom (successfully) and use a new piece of software to get it to a newer OS, and now OpenCore thinks it’s an MBP.

I can’t make a reason….

 

[tsialex]

I'm sure this probably can be explained in some weird user error way, but right now its saved inside your BootROM NVRAM, with the variable 4d1fda02-38c7-4a6a-9cc6-4bcca8b30102:OCLP-Model:

--------
Variable: 4d1fda02-38c7-4a6a-9cc6-4bcca8b30102:OCLP-Model (OpenCore Variable)
StartID:  55aa (Valid)
State:    7f (Normal)
Unknown8: 00
Attr:     00000007 (NON_VOLATILE, BOOT_SERVICE_ACCESS, RUNTIME_ACCESS)
NameSize: 22
DataSize: 14
DataType: looks like NULL-terminated ASCII
Data:
00000000: 4d 61 63 42 6f 6f 6b 50 72 6f 36 2c 32 00        MacBookPro6,2.  
--------

You should nuke your install, install HighSierra/Mojave to a small SSD/HDD (making a rescue/flashing disk) and then flash a cleaned/upgraded/reconstructed BootROM image to your Mac Pro.

 

[Diggi]

I'm sure this probably can be explained in some weird user error way, but right now its saved inside your BootROM NVRAM, with the variable 4d1fda02-38c7-4a6a-9cc6-4bcca8b30102:OCLP-Model:

--------
Variable: 4d1fda02-38c7-4a6a-9cc6-4bcca8b30102:OCLP-Model (OpenCore Variable)
StartID:  55aa (Valid)
State:    7f (Normal)
Unknown8: 00
Attr:     00000007 (NON_VOLATILE, BOOT_SERVICE_ACCESS, RUNTIME_ACCESS)
NameSize: 22
DataSize: 14
DataType: looks like NULL-terminated ASCII
Data:
00000000: 4d 61 63 42 6f 6f 6b 50 72 6f 36 2c 32 00        MacBookPro6,2. 
--------

You should nuke your install, install HighSierra/Mojave to a small SSD/HDD (making a rescue/flashing disk) and then flash a cleaned/upgraded/reconstructed BootROM image to your Mac Pro.

I will do this and then inquire how to / what to flash bootrom with.