MP 6,1 MP61.0120.B00 for MP6,1

[macguru9999]

Someone brought me a 2013 mac pro with an nvme blank drive installed. But they have not done a firmware update yet and it obviously does not like the nvme drive.

I have put an older ssd in and i just want to know the best sequence to update the firmware, sierra on internal, then run a 10.13 installer ? any 10.13 like the latest one ? can you do the firmware update with a mojave installer ?

 

[macguru9999]

Its OK, when I did a 10.13.6 update on an apple ssd it fixed the firmware. The problem was that the owner was moving from an original aura ssd to an nvme. The original one is seen as an external by macos so the necessary firmware update is not carried out, so then when you plug in the nvme drive its not supported. So you have to have an apple ahci drive or similar to do the upgrade. !!

 

[tommy chen]

firmware updates can only be performed with the original module.
therefore you should keep it and not sell it!

 

[macguru9999]

firmware updates can only be performed with the original module.
therefore you should keep it and not sell it!

Its not my computer, but the ssd from a macbook air 2015 worked just fine.

 

[chrfr]

Its OK, when I did a 10.13.6 update on an apple ssd it fixed the firmware. The problem was that the owner was moving from an original aura ssd to an nvme. The original one is seen as an external by macos so the necessary firmware update is not carried out, so then when you plug in the nvme drive its not supported. So you have to have an apple ahci drive or similar to do the upgrade. !!

Firmware updates are an integral part of security updates too, so when installing those security updates, the original drive should go back in at that point in order to get the firmware updated then as well.

 

[macguru9999]

Firmware updates are an integral part of security updates too, so when installing those security updates, the original drive should go back in at that point in order to get the firmware updated then as well.

why ? If the newer replacement drive is seen as internal, and it is, surely he can use that for the firmware update

 

[chrfr]

why ? If the newer replacement drive is seen as internal, and it is, surely he can use that for the firmware update

The firmware updates usually won't install if there's an aftermarket drive in the computer.

 

[tsialex]

why ? If the newer replacement drive is seen as internal, and it is, surely he can use that for the firmware update

It's not about internal or external, like MP5,1 checks for an EFI GPU (MP51.00xx.Bxx BootROM upgrades) or a METAL GPU (1xx.0.0.0.0 BootROM upgrades), MP6,1 checks for an Apple OEM SSD installed. You can't circumvent that.

 

[macguru9999]

The firmware updates usually won't install if there's an aftermarket drive in the computer.

Well firmware updates did install with an Apple 128ssd from a macbook installed but thats an apple ahci ssd of course. I suppose if there are any more firmware updates and the nvme does not work, he can bring the computer back to me, but as far as i know he did not keep his internal original drive ... I know with my 5,1 i had to update the firmware from an internal sata drive, not a pcie blade, but it did not matter what brand os sata drive i used, as long as it was in one of the internal bays ...
[automerge]1580152232[/automerge]

It's not about internal or external, like MP5,1 checks for an EFI GPU (MP51.00xx.Bxx BootROM upgrades) or a METAL GPU (1xx.0.0.0.0 BootROM upgrades), MP6,1 checks for an Apple OEM SSD installed. You can't circumvent that.

Well its just as well I had one then ... even if it was from a different mac. Is this firmware mp61.00124.B00 new enough for the time being ? or is there a better one ?
[automerge]1580152792[/automerge]
another reason not to own a trash can

 

[tsialex]

Well firmware updates did install with an Apple 128ssd from a macbook installed but thats an apple ahci ssd of course. I suppose if there are any more firmware updates and the nvme does not work, he can bring the computer back to me, but as far as i know he did not keep his internal original drive ... I know with my 5,1 i had to update the firmware from an internal sata drive, not a pcie blade, but it did not matter what brand os sata drive i used, as long as it was in one of the internal bays ...
[automerge]1580152232[/automerge]

Well its just as well I had one then ... even if it was from a different mac. Is this firmware mp61.00124.B00 new enough for the time being ? or is there a better one ?
[automerge]1580152792[/automerge]
another reason not to own a trash can

Any Apple OEM 12+16 blade will work for updates, AHCI or NVMe after MP61.0120.B00, even the 24/32GB 12+16 blades made for iMac Fusion drives.

 

[macguru9999]

currently i have mp61.00124.B00 on the 6,1.

Is there a newer one i should install yet, or a list of which ones work with each os version ?

 

[tsialex]

currently i have mp61.00124.B00 on the 6,1.

Is there a newer one i should install yet, or a list of which ones work with each os version ?

MP6,1 with 10.15.2 have 133.0.0.0.0, 10.15.3DP3 have 134.0.0.0.0. Each macOS version has a maximum BootROM that can be installed, but the current BootROM work with any supported macOS release.

 

[macguru9999]

Thanks, so I should put my apple ssd back in and run a current catalina installer and then put back his nvme drive to run whatever system before or up to that ,,, thanks that explains alot
[automerge]1580155007[/automerge]
For instance, when i tried to run a high sierra security update, with his nvme installed, you could see the installer tried to do a restart an extra couple of times before giving up and running the rest of the update... it must have been failing to install the firmware update because the nvme drive was not an apple ....

 

[macguru9999]

OK I put 133.0.0.0.0 on it then reinstalled the nvme drive. seems to be working fine now , thanks

 

[mattwestside]

I think that's where I am stuck too. I have 10.14.6 installed on a Fledging M13 2TB and the latest security updates to Mojave installed, but I am still at a 127.x Boot ROM.

In order to update to Catalina, could someone confirm if this order of operations is correct?

1 - remove M13
2 - install Apple OEM SSD
3 - run installer for Mojave and all security updates
4 - update to Catalina on Apple SSD, verify update to 10.15.3 DP2, verify bootrom is at 134.x
5 - remove Apple SSD, install M13
6 - update to Catalina on M13

Thanks!

 

[tsialex]

I think that's where I am stuck too. I have 10.14.6 installed on a Fledging M13 2TB and the latest security updates to Mojave installed, but I am still at a 127.x Boot ROM.

In order to update to Catalina, could someone confirm if this order of operations is correct?

1 - remove M13
2 - install Apple OEM SSD
3 - run installer for Mojave and all security updates
4 - update to Catalina on Apple SSD, verify update to 10.15.3 DP2, verify bootrom is at 134.x
5 - remove Apple SSD, install M13
6 - update to Catalina on M13

Thanks!

Yes. No need to install Catalina on your 2TB SSD, if you do not want to.

 

[mattwestside]

Yes. No need to install Catalina on your 2TB SSD, if you do not want to.

Thanks. Is the general consensus to stay away from Catalina? I am in a pretty good state with Mojave with no real need to update, especially if stability is a trade-off.

 

[tsialex]

Thanks. Is the general consensus to stay away from Catalina? I am in a pretty good state with Mojave with no real need to update, especially if stability is a trade-off.

Nothing that is really compelling with Catalina works with MP6,1, like Sidecar, so you can update when is more stable.

 

[tsialex]

Apple sent 134.0.0.0.0 with High Sierra and Mojave Security Updates and 10.15.3 final.

 

[macguru9999]

Apple sent 134.0.0.0.0 with High Sierra and Mojave Security Updates and 10.15.3 final.

Thanks, I was just about to ask. Ill update his rom before i hand the trash can back later today .....

 

[rawweb]

@tsialex looks like I'm on 129.0.0.0.0 with my 6,1 on 10.15.2. This was a refurb unit sold NIB from OWC, though they configured it with a 1.0TB OWC Aura Pro X2 SSD. They didn't give me the factory apple drive so assuming I'm SOL on getting newer boot rom? Unfortunately, I wasn't aware of this at purchase.

 

[tsialex]

@tsialex looks like I'm on 129.0.0.0.0 with my 6,1 on 10.15.2. This was a refurb unit sold NIB from OWC, though they configured it with a 1.0TB OWC Aura Pro X2 SSD. They didn't give me the factory apple drive so assuming I'm SOL on getting newer boot rom? Unfortunately, I wasn't aware of this at purchase.

Yes, you will need to get an Apple OEM 12+16 blade, anything will work even 32GB blades from Fusion drives.

No way around it.

 

[macguru9999]

@tsialex looks like I'm on 129.0.0.0.0 with my 6,1 on 10.15.2. This was a refurb unit sold NIB from OWC, though they configured it with a 1.0TB OWC Aura Pro X2 SSD. They didn't give me the factory apple drive so assuming I'm SOL on getting newer boot rom? Unfortunately, I wasn't aware of this at purchase.

You will have to get a cheap little one on ebay ... 128g is fine from an old macbook air or pro

 

[th0masp]

So, if there's a significant mismatch of firmware and OS version but the thing boots and appears to work just fine - no urgent need to update, right?

 

[Soba]

So, if there's a significant mismatch of firmware and OS version but the thing boots and appears to work just fine - no urgent need to update, right?

Your system will not catch fire and explode if you cannot install firmware updates, but new firmware often contains security updates and other important fixes. If you can update the firmware somehow, you should do so.