MP 1,1-5,1 MacPro5,1: What you have to do to upgrade to Mojave (10.13/10.14 BootROM upgrades instructions thread)

[tsialex]

Also, I don't know if this has been covered before, but I noticed I now get the full PCIe 2.0 link speed. In the olden days, we got saddled with PCIe 1.0 speeds on non-Apple cards. Amazing how after 10 years we can still squeeze out more power from these old beasts.

That happened last year with the first 1xx.0.0.0.0 series BootROM, 138.0.0.0.0.

 

[DPUser]

You risked a lot doing this with a MP4,1>5,1. Netkas forum method overwrite the BootBlock and makes impossible to use Firmware Restoration CD.

No one should upgrade from a pre MP51.0089.B00 to 1xx.0.0.0.0 BootROMs.

Alex, you may want to emphasize this in the first post.

And thank you for taking the time to lay this all out for us. Much appreciated!

 

[donluca]

Only the full Mac App Store installers work for upgrading the firmware, macOS installers downloaded/patched with dosdude tool can't upgrade the firmware.

Just noticed this: this is absolutely not true. All of my bootrom updates have been made with the installer downloaded via dosdude’s patchers.
What I did was downloading the tool (High Sierra/Mojave), launch the program, go into “Tools”, “Download macOS XXX” and then, when the download is completed, close the Patcher, go where I downloaded the installer (I use Applications because that’s where App Store puts it by default) and launch it and proceed with the bootrom updates.

You might want to update that part.

 

[Macschrauber]

Can 2nd that, those installers what dosdudes tool loads are the same as those from installmacos.py script.

Also use them and I upgraded about a dozen Mac Pros in the last year.

 

[tsialex]

Just noticed this: this is absolutely not true. All of my bootrom updates have been made with the installer downloaded via dosdude’s patchers.
What I did was downloading the tool (High Sierra/Mojave), launch the program, go into “Tools”, “Download macOS XXX” and then, when the download is completed, close the Patcher, go where I downloaded the installer (I use Applications because that’s where App Store puts it by default) and launch it and proceed with the bootrom updates.

You might want to update that part.

I removed the downloaded part, thx for the correction. The rest stands since the installer detection of the firmware is removed from a patched install.

 

[Monarchvideo]

Hi,
I’m new to this group but am having similar problems. I have a 2010 5,1 Mac Pro tower 2x3.46 6 core
ATI Radeon HD 5870 GPU
Running Sierra and High Sierra
Stuck on Boot rom 144.0.0.0
SMC version 1.39f11

I replaced my backplane and can not upgrade to the newest firmware.
I tried a clean install to Sierra and High Sierra. The firmware upgrade page never appeared.
I tried using the Mac Pro firmware update but Infet an alert that this software is not supported on my system.
I tried using Nekas tool as well. After booting in recovery mode and using the terminal command it only gives me the option to downgrade to 2009 firmware.

I’m looking for any ideas.
Thanks

 

[tsialex]

Hi,
I’m new to this group but am having similar problems. I have a 2010 5,1 Mac Pro tower 2x3.46 6 core
ATI Radeon HD 5870 GPU
Running Sierra and High Sierra
Stuck on Boot rom 144.0.0.0
SMC version 1.39f11

I replaced my backplane and can not upgrade to the newest firmware.
I tried a clean install to Sierra and High Sierra. The firmware upgrade page never appeared.
I tried using the Mac Pro firmware update but Infet an alert that this software is not supported on my system.
I tried using Nekas tool as well. After booting in recovery mode and using the terminal command it only gives me the option to downgrade to 2009 firmware.

I’m looking for any ideas.
Thanks

144.0.0.0.0 is the current BootROM.

 

[Monarchvideo]

[doublepost=1562955765][/doublepost]

I’m confused. I thought MP51.007F.B03 was the latest firmware?

 

[tsialex]

View attachment 847874

144.0.0.0.0 is the current MP5,1 BootROM:

BootROM Version	Released with:	Type:	Note:
MP51.0083.B00	10.13 DP5	Beta	Beta APFS support
MP51.0084.B00	10.13 DP6 and 10.13.0	General release	Initial APFS support
MP51.0085.B00	10.13.4 and Mojave DP1 to DP3	General release	APFS support
MP51.0087.B00	10.13.5	General release	Missing microcodes
MP51.0089.B00	10.13.6	General release	Spectre/Meltdown mitigated microcodes on the April 2 Microcode Update Guidance.
138.0.0.0.0	10.14 DP7 and 10.14.0	General release	5GT/s support for every PCIe 2.0 card
139.0.0.0.0	10.14.1 DP1	Beta	minor updates and corrections
140.0.0.0.0	10.14.1 DP3 and 10.14.1 to 10.14.4	General release	NVMe boot, minor updates and corrections
141.0.0.0.0	10.14.4 DP2	Beta	minor updates and corrections
142.0.0.0.0	10.14.4 DP4 and 10.14.5 DP1	Beta	Updated APFSJumpStart EFI module - W3xxx Xeon bricker
144.0.0.0.0	10.14.5 DP4 and 10.14.5	General release	lot's of corrections, booting improvements

The Apple EFI and SMC firmware page is deprecated since 2017.

 

[Monarchvideo]

144.0.0.0.0 is the current MP5,1 BootROM:

BootROM Version	Released with:	Type:	Note:
MP51.0083.B00	10.13 DP5	Beta	Beta APFS support
MP51.0084.B00	10.13 DP6 and 10.13.0	General release	Initial APFS support
MP51.0085.B00	10.13.4 and Mojave DP1 to DP3	General release	APFS support
MP51.0087.B00	10.13.5	General release	Missing microcodes
MP51.0089.B00	10.13.6	General release	Spectre/Meltdown mitigated microcodes on the April 2 Microcode Update Guidance.
138.0.0.0.0	10.14 DP7 and 10.14.0	General release	5GT/s support for every PCIe 2.0 card
139.0.0.0.0	10.14.1 DP1	Beta	minor updates and corrections
140.0.0.0.0	10.14.1 DP3 and 10.14.1 to 10.14.4	General release	NVMe boot, minor updates and corrections
141.0.0.0.0	10.14.4 DP2	Beta	minor updates and corrections
142.0.0.0.0	10.14.4 DP4 and 10.14.5 DP1	Beta	Updated APFSJumpStart EFI module - W3xxx Xeon bricker
144.0.0.0.0	10.14.5 DP4 and 10.14.5	General release	lot's of corrections, booting improvements

The Apple EFI and SMC firmware page is deprecated since 2017.

View attachment 847875

[doublepost=1562957177][/doublepost]Thank you for posting that page. I never saw that before.
I totally misunderstood.
I am going to install Mojave following the instructions on your thread.
I have a flashed AMD Radeon R9 280X
to install first.

 

[JoesMorgue]

I just bought a 2009 Pro with a pair of quad-core processors.

The upgrade to 5.1 has been done. I'm wondering if I can upgrade to the 6-core CPU, as I intend on running Win10 that will run in Fusion in Unity mode from boot.

Right now, I'm in need of a video card that does metal. My friend has a 2010 Pro, and did the video card upgrade. He'd upgrade one for me, as he still has the files.

Outside of video, and memory, what can I do to improve the machine?

 

[kohlson]

You've come to the right place - the MR Mac Pro forum. I suggest taking a look at the sticky threads at the top. In particular: The "I just ordered/bought/got my new/refurb Mac Pro" thread [merged]

 

[flowrider]

I just bought a 2009 Pro with a pair of quad-core processors.

The upgrade to 5.1 has been done. I'm wondering if I can upgrade to the 6-core CPU,

Many Many, I would even say hundreds, of threads on this topic over the years. Your main obstacle is the 2009 4,1 dual processor cMP uses delidded CPUs. All stock Xeon CPUs have lids. They will either have to be mounted with spacers or the lids will need to be removed. Do a Search and you will learn much.

Lou

 

[DPUser]

You've come to the right place - the MR Mac Pro forum. I suggest taking a look at the sticky threads at the top. In particular: The "I just ordered/bought/got my new/refurb Mac Pro" thread [merged]

Yes on the Wikis, but the more specifically titled ones are easier to gather good info from. And the "Upgrade Guide" sticky has loads of linked resources.

Your 4,1 will make a great 12 core machine, but pay careful attention to installing those CPUs... 4,1 dual CPU Mac Pros utilized de-lidded CPUs, so the upgrade is a bit more complicated than it is with all 5,1s or 4,1 single CPU models.

 

[ftbtx]

Entered in Error

 

[Mac Hammer Fan]

Since I updated to bootrom 141 and 144 I had 3 kernel panics in three months. I never had kernel panics before.
Panic (system crashes) log:

Source: /Library/Logs/DiagnosticReports/Kernel_2019-07-24-215405_MacPro-1.panic
Size: 3 KB (3.475 bytes)
Last Modified: 24/07/2019, 22:33
Recent Contents: Anonymous UUID: 65667677-F579-95EE-2E6C-96B823FE550F

Wed Jul 24 21:54:05 2019

*** Panic Report ***
panic(cpu 2 caller 0xffffff801b2bb0ef): initproc exited -- exit reason namespace 2 subcode 0xa description: none

uuid info:
0x10ab6e000 uuid = <d3e77331-ace5-349d-a7cc-433d626d4a5b>
0x100f01000 uuid = <bbd445b6-fba9-3a9c-828f-a112f63e2080>

Thread 1 crashed

RAX: 0x0000000000000000, RBX: 0x0000000100f4f068, RCX: 0x0000000100f4c000, RDX: 0x0000000100f4f088
RSP: 0x000070000eefe300, RBP: 0x000070000eefe3a0, RSI: 0x0000000100f4f078, RDI: 0x0000000100f01000
R8: 0x0000000100f01ae8, R9: 0x0000000000000d0e, R10: 0x0000000000000010, R11: 0x0000000000000206
R12: 0x0000000100010ce3, R13: 0x0000000000001eb0, R14: 0x0000000100f51748, R15: 0x0000000100f01000
RFL: 0x0000000000010246, RIP: 0x00007fff63230b7f, CS: 0x000000000000002b, SS: 0x0000000000000023

Thread 0: 0xffffff8054c62520
0x00007fff6336b126
0x00007fff631f4ede
0x0000000000000000

Thread 1: 0xffffff808d0b3a40
0x00007fff63230b7f
0x00007fff63230a07
0x00007fff632308d1
0x00007fff6328db2a
0x0000000100f11ce3
0x0000000100f11324
0x00007fff631e563d
0x00007fff631e7de6
0x00007fff631f6f42
0x00007fff631eb792
0x00007fff631ec396
0x00007fff631f46ed
0x00007fff63425611
0x00007fff634253fd
0x0000000000070507

Thread 2: 0xffffff80674cc000
0x00007fff634253f0

Thread 3: 0xffffff805ed98a40
0x00007fff634253f0


Mac OS version:
18G84

Kernel version:
Darwin Kernel Version 18.7.0: Thu Jun 20 18:42:21 PDT 2019; root:xnu-4903.270.47~4/RELEASE_X86_64
Kernel UUID: 982F17B3-0252-37FB-9869-88B3B1C77335
System model name: MacPro5,1 (Mac-F221BEC8)
Root disk errors: "Failed to issue COM RESET after 3 attempts. Terminating."

EOF

System Profile:
Bluetooth: Version 6.0.14d3, 3 services, 27 devices, 1 incoming serial ports
Model: MacPro5,1, BootROM 144.0.0.0.0, 6 processors, 6-Core Intel Xeon, 3.33 GHz, 32 GB, SMC 1.39f5
Thunderbolt Bus:
Boot Volume File System Type: apfs
Graphics: Radeon RX 580, Radeon RX 580, spdisplays_pcie_device, 8 GB
USB Device: USB 2.0 Bus
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Keyboard Hub
USB Device: Apple Optical USB Mouse
USB Device: Apple Keyboard
USB Device: Apple Cinema HD Display
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB Bus
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB 3.0 Bus
Memory Module: DIMM 1, 8 GB, DDR3 ECC, 1333 MHz, 0x80AD, 0x484D54333147523742465234412D48392020
Memory Module: DIMM 2, 8 GB, DDR3 ECC, 1333 MHz, 0x80AD, 0x484D54333147523742465234412D48392020
Memory Module: DIMM 3, 8 GB, DDR3 ECC, 1333 MHz, 0x80AD, 0x484D54333147523742465234412D48392020
Memory Module: DIMM 4, 8 GB, DDR3 ECC, 1333 MHz, 0x80AD, 0x484D54333147523742465234412D48392020
FireWire Device: built-in_hub, Up to 800 Mb/sec
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.102.31)
Network Service: AirPort, AirPort, en2
PCI Card: pci1002,aaf0, Audio Device, Slot-1
PCI Card: Radeon RX 580, Display Controller, Slot-1
PCI Card: pci1b21,625, AHCI Controller, Slot-4
PCI Card: PXS3, USB eXtensible Host Controller, Slot-3
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: Neptune 6G SSD, 480.1 GB
Serial ATA Device: WDC WD6400AAKS-65A7B2, 640.14 GB
Serial ATA Device: ST2000DM006-2DM164, 2 TB
Serial ATA Device: ST2000DM006-2DM164, 2 TB
Serial ATA Device: Samsung SSD 850 EVO 500GB, 500.11 GB



I zapped the PRAM. Is there a solution?

 

[tsialex]

Since I updated to bootrom 141 and 144 I had 3 kernel panics in three months. I never had kernel panics before.
Panic (system crashes) log:

Source: /Library/Logs/DiagnosticReports/Kernel_2019-07-24-215405_MacPro-1.panic
Size: 3 KB (3.475 bytes)
Last Modified: 24/07/2019, 22:33
Recent Contents: Anonymous UUID: 65667677-F579-95EE-2E6C-96B823FE550F

Wed Jul 24 21:54:05 2019

*** Panic Report ***
panic(cpu 2 caller 0xffffff801b2bb0ef): initproc exited -- exit reason namespace 2 subcode 0xa description: none

uuid info:
0x10ab6e000 uuid = <d3e77331-ace5-349d-a7cc-433d626d4a5b>
0x100f01000 uuid = <bbd445b6-fba9-3a9c-828f-a112f63e2080>

Thread 1 crashed

RAX: 0x0000000000000000, RBX: 0x0000000100f4f068, RCX: 0x0000000100f4c000, RDX: 0x0000000100f4f088
RSP: 0x000070000eefe300, RBP: 0x000070000eefe3a0, RSI: 0x0000000100f4f078, RDI: 0x0000000100f01000
R8: 0x0000000100f01ae8, R9: 0x0000000000000d0e, R10: 0x0000000000000010, R11: 0x0000000000000206
R12: 0x0000000100010ce3, R13: 0x0000000000001eb0, R14: 0x0000000100f51748, R15: 0x0000000100f01000
RFL: 0x0000000000010246, RIP: 0x00007fff63230b7f, CS: 0x000000000000002b, SS: 0x0000000000000023

Thread 0: 0xffffff8054c62520
0x00007fff6336b126
0x00007fff631f4ede
0x0000000000000000

Thread 1: 0xffffff808d0b3a40
0x00007fff63230b7f
0x00007fff63230a07
0x00007fff632308d1
0x00007fff6328db2a
0x0000000100f11ce3
0x0000000100f11324
0x00007fff631e563d
0x00007fff631e7de6
0x00007fff631f6f42
0x00007fff631eb792
0x00007fff631ec396
0x00007fff631f46ed
0x00007fff63425611
0x00007fff634253fd
0x0000000000070507

Thread 2: 0xffffff80674cc000
0x00007fff634253f0

Thread 3: 0xffffff805ed98a40
0x00007fff634253f0


Mac OS version:
18G84

Kernel version:
Darwin Kernel Version 18.7.0: Thu Jun 20 18:42:21 PDT 2019; root:xnu-4903.270.47~4/RELEASE_X86_64
Kernel UUID: 982F17B3-0252-37FB-9869-88B3B1C77335
System model name: MacPro5,1 (Mac-F221BEC8)
Root disk errors: "Failed to issue COM RESET after 3 attempts. Terminating."

EOF

System Profile:
Bluetooth: Version 6.0.14d3, 3 services, 27 devices, 1 incoming serial ports
Model: MacPro5,1, BootROM 144.0.0.0.0, 6 processors, 6-Core Intel Xeon, 3.33 GHz, 32 GB, SMC 1.39f5
Thunderbolt Bus:
Boot Volume File System Type: apfs
Graphics: Radeon RX 580, Radeon RX 580, spdisplays_pcie_device, 8 GB
USB Device: USB 2.0 Bus
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Keyboard Hub
USB Device: Apple Optical USB Mouse
USB Device: Apple Keyboard
USB Device: Apple Cinema HD Display
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB Bus
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB 3.0 Bus
Memory Module: DIMM 1, 8 GB, DDR3 ECC, 1333 MHz, 0x80AD, 0x484D54333147523742465234412D48392020
Memory Module: DIMM 2, 8 GB, DDR3 ECC, 1333 MHz, 0x80AD, 0x484D54333147523742465234412D48392020
Memory Module: DIMM 3, 8 GB, DDR3 ECC, 1333 MHz, 0x80AD, 0x484D54333147523742465234412D48392020
Memory Module: DIMM 4, 8 GB, DDR3 ECC, 1333 MHz, 0x80AD, 0x484D54333147523742465234412D48392020
FireWire Device: built-in_hub, Up to 800 Mb/sec
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.102.31)
Network Service: AirPort, AirPort, en2
PCI Card: pci1002,aaf0, Audio Device, Slot-1
PCI Card: Radeon RX 580, Display Controller, Slot-1
PCI Card: pci1b21,625, AHCI Controller, Slot-4
PCI Card: PXS3, USB eXtensible Host Controller, Slot-3
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: Neptune 6G SSD, 480.1 GB
Serial ATA Device: WDC WD6400AAKS-65A7B2, 640.14 GB
Serial ATA Device: ST2000DM006-2DM164, 2 TB
Serial ATA Device: ST2000DM006-2DM164, 2 TB
Serial ATA Device: Samsung SSD 850 EVO 500GB, 500.11 GB



I zapped the PRAM. Is there a solution?

Sorry, but you need to find a more appropriate thread, no?

@Mac Hammer Fan This is your best tip:

Root disk errors: "Failed to issue COM RESET after 3 attempts. Terminating."

One of your drives is probably almost dying, install DriveDX and see what is causing this problem.

 

[MapleGreen]

Sorry, but you need to find a more appropriate thread, no?

@Mac Hammer Fan This is your best tip:

One of your drives is probably almost dying, install DriveDX and see what is causing this problem.

Thanks I had this problem, but it fixed by reinstalling macOS
by the way I just installed DriveDX you said, but it says my drives are not supported. is there appropriate thread in here?
maybe ''Mac Hammer Fan'' could start the new thread

 

[Mac Hammer Fan]

Drive DX reports no problems with my drives. I will continue this problem in this thread:
https://forums.macrumors.com/thread...-6-on-your-cmp-4-2-5-1.2190914/#post-27570153

 

[Condor2409]

I'm new here .. your article show's my problem ... Syst: Mac Pro 4.1 --> flashed 5.1 octcore // 64 GB Ram // NVIDIA GTX 680 2 GB // All SSD's // Running 10.9.6 Maverick --> will go to High Sierra and then to Mojave

I have a NVIDIA GTX 680 / 2 GB flashed version...no way to get the boot manager w. "alt" ..no way to get recovery manager.. w. Apple+ R -- all happens after flashing the mac from 4.1 to 5.1 ..for a couple of weeks. Therefore can't update from my install ready bootable High Sierra stick - I had selected the stick inside the syst. pref. as start "USB boot drive" ... but nothing than black screen.... - My boot version: MP51.007F.B03
which one is newer ? -> MP51.007F.B03 or MP51.0089.B00

It seems that your'e right with your consid. above. reg . 4k & DP 2 - I running a 40" 4 K Phillips monitor over DP port 2 w. 60 Hz

What to do ?
Agradeço sua ajuda

 

[tsialex]

I'm new here .. your article show's my problem ... Syst: Mac Pro 4.1 --> flashed 5.1 octcore // 64 GB Ram // NVIDIA GTX 680 2 GB // All SSD's // Running 10.9.6 Maverick --> will go to High Sierra and then to Mojave

I have a NVIDIA GTX 680 / 2 GB flashed version...no way to get the boot manager w. "alt" ..no way to get recovery manager.. w. Apple+ R -- all happens after flashing the mac from 4.1 to 5.1 ..for a couple of weeks. Therefore can't update from my install ready bootable High Sierra stick - I had selected the stick inside the syst. pref. as start "USB boot drive" ... but nothing than black screen.... - My boot version: MP51.007F.B03
which one is newer ? -> MP51.007F.B03 or MP51.0089.B00

It seems that your'e right with your consid. above. reg . 4k & DP 2 - I running a 40" 4 K Phillips monitor over DP port 2 w. 60 Hz

What to do ?
Agradeço sua ajuda

Look at the table on the first post, you will see the history of all MP5,1 BootROMs.

BootROM versions increase, first using hexadecimal EFI versioning up to the last High Sierra BootROM, then with Mojave Apple changed the EFI versions to decimal but continuing from the same previous point. The current version is 144.0.0.0.0.

If you can't access the BootPicker/BootSelector, or you have an incorrectly flashed GPU or you are using a 4K DP1.2 display. If it's the later you can set your display to DP1.1 (check your settings) or use another monitor up to fullHD, this is explained on the first post. If it's the former, you can flash your GTX 680 for pre-boot configuration support, see these posts:

Confirmed and Possible Flashable GTX680 Models
Step-by-Step Instructions for Flashing GTX680
GTX680 4GB - ROM Image - Full Boot Screens, Full Clock Rates & PCI-E 2.0 - 5GT/s

 

[Condor2409]

Look at the table on the first post, you will see the history of all MP5,1 BootROMs.

BootROM versions increase, first using hexadecimal EFI versioning up to the last High Sierra BootROM, then with Mojave Apple changed the EFI versions to decimal but continuing from the same previous point. The current version is 144.0.0.0.0.

If you can't access the BootPicker/BootSelector, or you have an incorrectly flashed GPU or you are using a 4K DP1.2 display. If it's the later you can set your display to DP1.1 (check your settings) or use another monitor up to fullHD, this is explained on the first post. If it's the former, you can flash your GTX 680 for pre-boot configuration support, see these posts:

Confirmed and Possible Flashable GTX680 Models
Step-by-Step Instructions for Flashing GTX680
GTX680 4GB - ROM Image - Full Boot Screens, Full Clock Rates & PCI-E 2.0 - 5GT/s

Now I have a complete desaster .. after installing the new boot rom version MP51.0089.B00 and put any 4 k cables out and run the installation with VGA cable in small resolution I could start the HS installer .. he was running throuh the install routine-- finally asking where to install I had choose the new SSD preformtted with External Journaled.. so far so good... then I got this screen

 

[tsialex]

Like I said on the BootROM thread, please open a thread describing your problem or find a more appropriate thread, you are posting in threads unrelated to your problem.

You are trying to install High Sierra, so the High Sierra forum would be more appropriated, since you already have the correct BootROM for 10.13.6, MP51.0089.B00, and won't need a BootROM upgrade at all. Maybe you have a createinstallmedia USB installer problem, or you have a hardware problem.

High Sierra forum: macOS High Sierra (10.13)

 

[fendersrule]

Hi @tsialex,

Love this thread and your contributions.

I have a real 5,1 w/ RX 580. Currently running High Sierra. I JUST upgraded my bootrom to the newest, but did not install Mojave.

I noticed when I updated my bootrom previously (whichever High Sierra required), that it killed support for booting to my Windows 10 EFI drive via Bootchamp. I cannot recall what the screen said when I tried booting into Windows 10, but it was a black DOS-looking screen that said something...I think it was related to a boot image of some sort. Maybe this is a problem with bootchamp not redirecting the Mac appropriately? I remembered that could go through the reinstall process successfully for Windows 10 in EFI mode, but as soon as it does a full boot it always throws me to that screen. I attribute the problem to something that changed in the bootrom update from High Sierra that broke this functionality for Windows EFI.

My thoughts is now that I have the newest firmware, I should reinsert my Windows 10 EFI drive back into the Mac Pro and give it another whirl. Maybe even go through the installation process again. If that doesn't work, then I'm sure installing Windows 10 in Bios mode should still work?

My ultimate question, is that now that I'm High Sierra with the latest F/W, is there still a way to boot back and forth into Windows given I have an RX 580 if I were to move to Mojave?

 

[tsialex]

Hi @tsialex,

Love this thread and your contributions.

I have a real 5,1 w/ RX 580. Currently running High Sierra. I JUST upgraded my bootrom to the newest, but did not install Mojave.

I noticed when I updated my bootrom previously (whichever High Sierra required), that it killed support for booting to my Windows 10 EFI drive via Bootchamp. I cannot recall what the screen said when I tried booting into Windows 10, but it was a black DOS-looking screen that said something...I think it was related to a boot image of some sort. Maybe this is a problem with bootchamp not redirecting the Mac appropriately? I remembered that could go through the reinstall process successfully for Windows 10 in EFI mode, but as soon as it does a full boot it always throws me to that screen. I attribute the problem to something that changed in the bootrom update from High Sierra that broke this functionality for Windows EFI.

BootChamp don't work anymore.

My thoughts is now that I have the newest firmware, I should reinsert my Windows 10 EFI drive back into the Mac Pro and give it another whirl. Maybe even go through the installation process again. If that doesn't work, then I'm sure installing Windows 10 in Bios mode should still work?

The correct way is to use a SATA disk installed on one of the six Mac Pro native SATA ports dedicated to Windows 10 and will have to be installed with CSM mode (BIOS) via a DVD. Then you can use iMac Pro BootCamp drivers and have a fully working and functional Windows BootCamp Boot Selector panel. After that you can go to and from Windows just using System Preferences/StartUpDisk and Windows BootCamp Boot Selector panel.

Read this post to know what to do:

-- How to install Windows and switch between different OS without boot screen --
https://forums.macrumors.com/thread...ut-a-boot-screen.2114788/page-9#post-26689280

My ultimate question, is that now that I'm High Sierra with the latest F/W, is there still a way to boot back and forth into Windows given I have an RX 580 if I were to move to Mojave?

Already answered above.