Unfortunately that 512gb blade is in iMac and i can't open again for that, is to much work for that. But if i remove nvme ssd and i run os from external usb sata ssd, you think i have a chance ?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 MacPro5,1: BootROM thread | 144.0.0.0.0
- Thread starter tsialex
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Zero, needs to be installed in the 12+16 connector. MP6,1 people tried every trick imaginable and nothing work.
Any Apple OEM 12+16 blade of the same generation will work, even the SSD part of Fusion drives (32/64/128GB).
Phew... I'm glad I hang on to all of my old parts. It doesn't effect my Army Tank cMP51, but it seems a good practice to retain original parts none the less.
Last edited:
Alex this is 64gb for macbook air *2012* 11" 13" A1465 A1466 . You think i can use to update my firmware? I find cheap in eBay
Attachments
These are SATA, with a totally different conector.
You need:
- late-2013 MP6,1,
- late-2014 mini,
- late-2013 to late-2015 MBPs,
- mid-2013 to 2017 Airs,
- mid 2014 to late-2015 iMacs.
Apple released 10.15.1 for everyone this afternoon, seems we have new firmwares, I’ll check everything later today.
[automerge]1572375078[/automerge]
Build 19B88.
[automerge]1572375078[/automerge]
Build 19B88.
Last edited:
Applied the Security Update 2019-001 for macOS 10.14.6 on my Mac Pro 5,1 and it's still the same at 144.0.0.0.0
Tried upgrading an Early 2015 rMBP to 10.15.1, don't see any changes, still 187.0.0.0.0 as it was before in 10.15.0.
Tried upgrading an Early 2015 rMBP to 10.15.1, don't see any changes, still 187.0.0.0.0 as it was before in 10.15.0.
For MP5,1 as far as i know FW updates are only applied by the full installer. Correct me if i am wrong.
From 10.15.0 to 10.15.1, the only firmware upgrade for non BridgeOS Macs was for iMac19,1, from 1037.0.73.0.0 to 1037.40.118.0.0.
Firmwares creation date for 10.15.1 was October 11.
Firmwares creation date for 10.15.1 was October 11.
| Mac: | EFI version: |
|---|---|
| IM13,1 | 288.0.0.0.0 |
| IM14,1 | 140.0.0.0.0 |
| IM14,2 | 140.0.0.0.0 |
| IM14,3 | 140.0.0.0.0 |
| IM14,4 | 200.0.0.0.0 |
| IM15,1 | 231.0.0.0.0 |
| IM16,1 | 231.0.0.0.0 |
| IM16,2 | 231.0.0.0.0 |
| IM17,1 | 173.0.0.0.0 |
| IM18,1 | 178.0.0.0.0 |
| IM18,3 | 178.0.0.0.0 |
| IM19,1 | 1037.40.118.0.0 |
| MB10,1 | 182.0.0.0.0 |
| MB8,1 | 185.0.0.0.0 |
| MB9,1 | 187.0.0.0.0 |
| MBA5,1 | 260.0.0.0.0 |
| MBA6,1 | 118.0.0.0.0 |
| MBA7,1 | 190.0.0.0.0 |
| MBP10,1 | 258.0.0.0.0 |
| MBP10,2 | 281.0.0.0.0 |
| MBP11,1 | 157.0.0.0.0 |
| MBP11,2 | 157.0.0.0.0 |
| MBP11,4 | 195.0.0.0.0 |
| MBP12,1 | 187.0.0.0.0 |
| MBP13,1 | 240.0.0.0.0 |
| MBP13,2 | 262.0.0.0.0 |
| MBP13,3 | 262.0.0.0.0 |
| MBP14,1 | 202.0.0.0.0 |
| MBP14,2 | 202.0.0.0.0 |
| MBP14,3 | 202.0.0.0.0 |
| MBP9,1 | 229.0.0.0.0 |
| MM6,1 | 281.0.0.0.0 |
| MM7,1 | 245.0.0.0.0 |
| MP6,1 | 133.0.0.0.0 |
I was reading through this thread and realised that I might also have a bootrom issue. I previously used a uefi install of Win10. Upon dumping my bootrom I noticed the 509 certs. This is on a 2010 cmp 5,1.
![Screen Shot 2019-11-05 at 23.00.47.png]( "Screen Shot 2019-11-05 at 23.00.47.png")
Is this still the most appropriate thread to bring this up in? I read about 80 or so pages in and then came back to the more recent posts, so if it has moved elsewhere apologies in advance.
Edit: was pretty tired last night and could have added more details. I am running 10.13.6 with the
MP51.0089.B00 bootrom. I use a stock 5770 but will be upgrading to an RX580. I am rather wary of installing Mojave when it arrives as I don't really wanna mess around with my firmware given that there have been these problems.
I only came across this thread after trying to figure out why my machine was acting so strangely, and realised that it all ties to the nvram/bootrom. Here are a couple of things that I am currently having problems with, to give an idea:
- I cannot reset nvram/pram using cmd+optn+p+r. I have to go into terminal and use
Resetting the pram using the terminal command does not re-enable SIP as it should (at least, I have been told that it should).
- in addition to the nvram problem, virtually no startup shortcut keys work (bar holding alt/option to select boot drive).
- I cannot switch between windows (legacy install) and MacOS using Startup Disk. It tells me that the bless tool was unable to set the startup disk. Bootchamp, Boot Manager and Quickboot all either print a similar error message ('legacy mode not supported') or simply restart into MacOS instead of Win10. I can select & boot with no problem from my Win10 partition when I press alt/option at startup.
In relation to the third problem, I thought that I had messed up the partition table somehow, as I have tinkered with the disks an awful lot and am aware of how easy it is to confuse the OS, so today I tried a test. I erased an SSD and ran 10.13.6 recovery on it, in order to install a fresh copy. I then switched the disk into my MBP 2012 in order to perform a bootcamp partitioned install of Windows (playing by the rules for control purposes). Once this was complete, I switched between Windows and MacOS on the macbook a few times and it worked flawlessly using startup disk.
Upon switching the disk back to the cMP, however, back to the same problem - Startup Disk refused to cooperate. Switch it back to the Macbook Pro again and all works fine. Tried this with all other drives removed, drive inserted into every possible SATA bay etc. Attempting to set the windows drive as startup disk & failing adds an unintelligible line to the nvram output from
Please note that I am not asking for assistance with these three outlined problems, but rather trying to illustrate my belief that these may be symptoms of corruption to my BootROM. All are related in some way to the nvram.
Is this still the most appropriate thread to bring this up in? I read about 80 or so pages in and then came back to the more recent posts, so if it has moved elsewhere apologies in advance.
Edit: was pretty tired last night and could have added more details. I am running 10.13.6 with the
MP51.0089.B00 bootrom. I use a stock 5770 but will be upgrading to an RX580. I am rather wary of installing Mojave when it arrives as I don't really wanna mess around with my firmware given that there have been these problems.
I only came across this thread after trying to figure out why my machine was acting so strangely, and realised that it all ties to the nvram/bootrom. Here are a couple of things that I am currently having problems with, to give an idea:
- I cannot reset nvram/pram using cmd+optn+p+r. I have to go into terminal and use
Code:
nvram -c.- in addition to the nvram problem, virtually no startup shortcut keys work (bar holding alt/option to select boot drive).
- I cannot switch between windows (legacy install) and MacOS using Startup Disk. It tells me that the bless tool was unable to set the startup disk. Bootchamp, Boot Manager and Quickboot all either print a similar error message ('legacy mode not supported') or simply restart into MacOS instead of Win10. I can select & boot with no problem from my Win10 partition when I press alt/option at startup.
In relation to the third problem, I thought that I had messed up the partition table somehow, as I have tinkered with the disks an awful lot and am aware of how easy it is to confuse the OS, so today I tried a test. I erased an SSD and ran 10.13.6 recovery on it, in order to install a fresh copy. I then switched the disk into my MBP 2012 in order to perform a bootcamp partitioned install of Windows (playing by the rules for control purposes). Once this was complete, I switched between Windows and MacOS on the macbook a few times and it worked flawlessly using startup disk.
Upon switching the disk back to the cMP, however, back to the same problem - Startup Disk refused to cooperate. Switch it back to the Macbook Pro again and all works fine. Tried this with all other drives removed, drive inserted into every possible SATA bay etc. Attempting to set the windows drive as startup disk & failing adds an unintelligible line to the nvram output from
Code:
nvram -xpPlease note that I am not asking for assistance with these three outlined problems, but rather trying to illustrate my belief that these may be symptoms of corruption to my BootROM. All are related in some way to the nvram.
Last edited:
Looks like this update was released, re-released, newly released, mis-labeled, or something...
I'm currently on 10.14.6 (18G103) and was just alerted about this update's availability. Will update with build number after install in a little bit.
-----
Currently available versions from script:
Code:
# ProductID Version Build Post Date Title
1 041-91758 10.13.6 17G66 2019-10-19 macOS High Sierra
2 041-83630 10.15.1 19B88 2019-10-29 macOS Catalina
3 061-26589 10.14.6 18G103 2019-10-14 macOS Mojave
4 041-88800 10.14.4 18E2034 2019-10-23 macOS Mojave
5 041-90855 10.13.5 17F66a 2019-10-23 Install macOS High Sierra Beta
6 061-26578 10.14.5 18F2059 2019-10-14 macOS Mojave
This update was released last week and then republished overnight. The build number remains at 18G1012 both before and after today's republishing of the update. Apple generally does not release new full installers that incorporate security updates so the installer showing in the catalog is unlikely to ever by anything beyond 18G103.
The 10.14.6 security update situation is a mess.
Initial release in July 2019.
A security update in August 2019 for some.
Followed by another security update in August 2019 for all.
A security update in September 2019.
A security update in October 2019.
Followed by a re-release/re-package in November 2019.
At least label the 2019-### correctly at this point, or release 10.14.7 as an all encompassing cleanup. What was just re-released/re-packaged was not "2019-001" by any means.
Initial release in July 2019.
A security update in August 2019 for some.
Followed by another security update in August 2019 for all.
A security update in September 2019.
A security update in October 2019.
Followed by a re-release/re-package in November 2019.
At least label the 2019-### correctly at this point, or release 10.14.7 as an all encompassing cleanup. What was just re-released/re-packaged was not "2019-001" by any means.
Yes, Apple reissued the last security updates and 10.15.1 yesterday. Even the full installer for Catalina 10.15.1 was re-issued yesterday afternoon.
I have no time available this week, but maybe I have some in the weekend, tomorrow I’ll send a PM with instructions, gather everything and send me back before Saturday and I’ll take a look.
For what it's worth i just downloaded ( Nov. 7th. 2019 ) Mojave FULL 10.14.6 using this link https://apps.apple.com/us/app/macos-mojave/id1398502828?mt=12 from the App Store:
The build No. is still 18G103
![Nov 7th 2019 Mojave full 10.14.6 build 18G103.jpg]( "Nov 7th 2019 Mojave full 10.14.6 build 18G103.jpg")
Software Update assures me that my 4,1>5.1 is up to date - I don't recall doing any Security updates for Mojave since doing "three " CLEAN " full installs of builds 18G87 - 18G95 & finally 18G103 "
I'm presuming that any Security Updates were included in one of the builds.
The build No. is still 18G103
Software Update assures me that my 4,1>5.1 is up to date - I don't recall doing any Security updates for Mojave since doing "three " CLEAN " full installs of builds 18G87 - 18G95 & finally 18G103 "
I'm presuming that any Security Updates were included in one of the builds.
The "supplemental" updates to 10.14.6 were included in the full installer, but security update 2019-001 for Mojave is not included. Software update should be telling you that update, as well as Safari 13.0.3, is still required.