MP 1,1-5,1 MacPro5,1: BootROM thread | 144.0.0.0.0

[tsialex]

Thanks, I will check before flashing, and thanks for putting me "back on track"

Nice! You can send your BootROM by PM. Remember to compress it first.

Thx!

 

[Catzjes]

Nice! You can send your BootROM by PM or to my email, my nick here plus gmail.com. Remember to compress it first.

Thx!

Already done ;-)

 

[Earl Urley]

No AV software on cMP, only HS firewall enabled. AV was enabled on my MBP which I used to download the files but I downloaded the ROMTool direct on the cMP. Should I try to download all needed files directly on the cMP?

I had to clear out ROMTool data before reading/flashing mine as well.. from memory you have to remove the ROMTool folder in /Library/Application Support, then the ROMTool preferences file in your user Library/Preferences folder (think it's called com.dosdude1.ROMTool.plist.

From what I can tell, ROMTool puts a copy of DirectHW.kext in that Application Support folder and loads it just as it needs to dump / flash a ROM.

 

[Catzjes]

I had to clear out ROMTool data before reading/flashing mine as well.. from memory you have to remove the ROMTool folder in /Library/Application Support, then the ROMTool preferences file in your user Library/Preferences folder (think it's called com.dosdude1.ROMTool.plist.

From what I can tell, ROMTool puts a copy of DirectHW.kext in that Application Support folder and loads it just as it needs to dump / flash a ROM.

After totally removing/de-installing all traces of old/corrupted RoomTool app with AppCleaner and re-downloading and installing ROMTool from "scratch" it eventually worked

 

[tsialex]

Just to everyone know:

Apple updated the MP61 NVMe DXE with 10.13.5 trashcan BootROM upgrade (MP61.0124.B00).

So, now everyone with NVMe on MP51 is outdated

Checked the NVMe DXE from the two different MP61 MP61.0124.B00 dumps that I have (thx @krakman and @saulinpa) and compared with the usual NVMe DXE.

Changes are little, as you can see.


[doublepost=1535984871][/doublepost]Who wants to test the new one? I only have SM951-AHCI and SSBUX at the moment.

 

[rosskinard]

Just to everyone know:

Apple updated the MP61 NVMe DXE with 10.13.5 trashcan BootROM upgrade (MP61.0124.B00).

So, now everyone with NVMe on MP51 is outdated

Checked the NVMe DXE from the two different MP61 MP61.0124.B00 dumps that I have (thx @krakman and @saulinpa) and compared with the usual NVMe DXE.

Changes are little, as you can see.

View attachment 779412 View attachment 779413
[doublepost=1535984871][/doublepost]Who wants to test the new one? I only have SM951-AHCI and SSBUX at the moment.

I'll test...I need to redo my ROM anyway after a reinstall of Mojave updated my 4,1->5,1 box and broke the booting from the Lycom+Samsung 970 EVO.

I can send you the clean original ROM dump from my system (pre-modifications of any sort) if you'd like to build a new 138 ROM with NMVe to try out.

Ross

 

[macgirl-mx]

Mojave installer only install itself with APFS, if you manually install it to a HFS disk via a 3rd party util, you do not get updates. Game over for HFS+ with Mojave.

Thanks, but the new bootrom is not problem in a 4,1>5,1?

 

[tsialex]

Thanks, but the new bootrom is not problem in a 4,1>5,1?

Why would be a problem?

Everyone here is using 138.0.0.0.0. I did BootROM upgrades to people with pre-production early-2009s, the Base_17 one, to mid-2012s with logic boards made on the last production day. All working fine.
[doublepost=1535995660][/doublepost]

I'll test...I need to redo my ROM anyway after a reinstall of Mojave updated my 4,1->5,1 box and broke the booting from the Lycom+Samsung 970 EVO.

I can send you the clean original ROM dump from my system (pre-modifications of any sort) if you'd like to build a new 138 ROM with NMVe to try out.

Ross

I'll PM you.

 

[MIKX]

tsialex

You absolutely must be a bachelor ( bacharel ) ! The sheer amount of time you devote to our cMP's would result in a divorce in my country of origin, Australia ( I'm currently in Japan ).

I salute you Sir. Apple should headhunt you .. but that would be a loss for us.

 

[tsialex]

tsialex

You absolutely must be a bachelor ( bacharel ) ! The sheer amount of time you devote to our cMP's would result in a divorce in my country of origin, Australia ( I'm currently in Japan ).

I salute you Sir. Apple should headhunt you .. but that would be a loss for us.

Thx. Btw, read my reply to you on the other thread.

 

[handheldgames]

Just to everyone know:

Apple updated the MP61 NVMe DXE with 10.13.5 trashcan BootROM upgrade (MP61.0124.B00).

So, now everyone with NVMe on MP51 is outdated

Checked the NVMe DXE from the two different MP61 MP61.0124.B00 dumps that I have (thx @krakman and @saulinpa) and compared with the usual NVMe DXE.

Changes are little, as you can see.

View attachment 779412 View attachment 779413
[doublepost=1535984871][/doublepost]Who wants to test the new one? I only have SM951-AHCI and SSBUX at the moment.

After installing the new NVMe.dxe I can report that the double boot issue between high Sierra and Mojave appears to be fixed with the new driver.

Although, it may have been fixed by clearing out my Nvram with the updated ROM you upgraded and I installed. Thanks for making the update process sooo much easier.

 

[Catzjes]

@tsialex Thanks for all your efforts and cheers

 

[crjackson2134]

After installing the new NVMe.dxe I can report that the double boot issue between high Sierra and Mojave appears to be fixed with the new driver.

Although, it may have been fixed by clearing out my Nvram with the updated ROM you upgraded and I installed. Thanks for making the update process sooo much easier.

Clearing out the Nvram wasn't the fix. I know that for a fact after dozen or more reflashes.
It’s because the new ROM set SIP as enabled (default setting).

I updated as well too, so I'll test out if it fixed my Mojito 2 step boot.

 

[tsialex]

Clearing out the Nvram wasn't the fix. I know that for a fact after dozen or more refreshes.

I updated as well too, so I'll test out if it fixed my Mojito 2 step boot.

I didn't had time to test this yet, all my free time today went studying the MP61.0124.B00 NVMe DXE and doing BootROMs to people with NVMe drives.

 

[LightBulbFun]

on the NVMe thing

I recall people going with the MBP11,4 NVMe driver as IIRC that driver is much "newer" and handles drives better (I Know it solved several issues on older MBPs that "supported" NVMe natively anyway)

so out of curiosity why are you going for the MP6,1s buggier NVMe driver?

 

[crjackson2134]

I didn't had time to test this yet, all my free time today went studying the MP61.0124.B00 NVMe DXE and doing BootROMs to people with NVMe drives.

No, it didn't fix it here, and it has increased my boot times dramatically. It now takes a VERY long time (over a minute) to boot into either OS. Both SATA and NVMe. Seriously degraded boot performance for me so far. Still going to try a hunch I have about something though.

My “Hunch” was correct...

Setting SIP to disabled adds an additional 10 Sec. to boot times (both Cold/Warm booting). This is also the cause of the double-chime when switching from Mojave to High Sierra or vice-versa. Setting SIP to enabled corrects both issues, but switching OS versions by booting into a different drive is still an unnecessarily long event.

[doublepost=1536005595][/doublepost]

on the NVMe thing

I recall people going with the MBP11,4 NVMe driver as IIRC that driver is much "newer" and handles drives better (I Know it solved several issues on older MBPs that "supported" NVMe natively anyway)

so out of curiosity why are you going for the MP6,1s buggier NVMe driver?

By all means, PM me the .ffs for testing. I'd like to check it out.

 

[handheldgames]

No, it didn't fix it here, and it has increased my boot times dramatically. It now takes a VERY long time (over a minute) to boot into either OS. Both SATA and NVMe. Seriously degraded boot performance for me so far. Still going to try a hunch I have about something though.
[doublepost=1536005595][/doublepost]

By all means, PM me the .ffs for testing. I'd like to check it out.

Interesting. I’m seeing 48 second boot times to Mojave. Which seems about right, if not faster with the hardware configuration im running.

Initial boot after a ROM install was sloooow. Like it usually is.

 

[macgirl-mx]

Why would be a problem?

Everyone here is using 138.0.0.0.0. I did BootROM upgrades to people with pre-production early-2009s, the Base_17 one, to mid-2012s with logic boards made on the last production day. All working fine.

Oh I see, thanks again.

 

[tsialex]

on the NVMe thing

I recall people going with the MBP11,4 NVMe driver as IIRC that driver is much "newer" and handles drives better (I Know it solved several issues on older MBPs that "supported" NVMe natively anyway)

so out of curiosity why are you going for the MP6,1s buggier NVMe driver?

Was not my choice, I only have SM951-AHCI and SSBUX, someone picked the trashcan one to test on another thread and everyone did the same. Since I'm studying the MP61 firmware for other reasons, I've noticed today the new DXE with the most recent trashcan BootROM.

To me, the best choice would be IM15,1, but I really hate scap files…

 

[LightBulbFun]

No, it didn't fix it here, and it has increased my boot times dramatically. It now takes a VERY long time (over a minute) to boot into either OS. Both SATA and NVMe. Seriously degraded boot performance for me so far. Still going to try a hunch I have about something though.
[doublepost=1536005595][/doublepost]

By all means, PM me the .ffs for testing. I'd like to check it out.

heres the NVMe driver from the MBP11,4 BootROM

 

[crjackson2134]

heres the NVMe driver from the MBP11,4 BootROM

Got it... I may test today, or in a day or so... Depending on Honey Do's...

EDIT:
On second thought, I’ll wait until someone else proves it’s good to go. I’ve learned my lesson by seeing what happend to @tsialex (big silver brick), I don’t have the equipment or skills needed to recover the SPI chip.

 

[tsialex]

heres the NVMe driver from the MBP11,4 BootROM

I'd wait on that one. People are reporting a lot of trouble with Samsung drives on the NVME MacBook Pro thread.

 

[LightBulbFun]

heres the NVMe driver from IM18,3 which ships from the factory with a NVMe drive (same form factor as what the MP6,1 and MBP11/12,x use etc)

(EDIT: WARNING: it looks like the iMac18,3 NVMe driver will brick an older macintosh if you insert it into its BootROM, DO NOT use this DXE for adding NVMe bootablity to any older macintosh)

 

[tsialex]

heres the NVMe driver from IM18,3 which ships from the factory with a NVMe drive (same form factor as what the MP6,1 and MBP11/12,x use etc)

I have that one, it's a .fd one. I'll test it when my elcheapo NVMe drive arrive. I don't want to inject untested DXEs with other people BootROMs. With the trashcan one we have support of the @CodeJingle thread.

 

[crjackson2134]

Interesting. I’m seeing 48 second boot times to Mojave. Which seems about right, if not faster with the hardware configuration im running.

Initial boot after a ROM install was sloooow. Like it usually is.

ON MY SYSTEM (net necessary anyone else)....

Double boot 2-step is caused or affected by SIP enable/disable.

If I fully enable SIP, I get an 80 sec. boot time into HS after fully shutting down Mojave. But it doesn't double boot any more. I get EXACTLY the same times when switching OS's in the other directions as will. Also no double booting.

Disabling SIP triggers double-chime boot again, and increases boot time by 10 sec. (cold/warm boot).

[doublepost=1536007104][/doublepost]

I have that one, it's a .fd one. I'll test it when my NVMe drive arrive. I don't want to inject untested DXEs with other people BootROMs. With the trashcan one we have support of the @CodeJingle thread.

You can still test it for bricking without the NVMe drive. If it doesn't brick, I'm not averse to testing NVMe performance. Just make sure it doest brick the MP51.