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.
- Status
Ok!
I´m on a cMP 5.1 (84´) and I just booted off my Samsung NVMe 960 Pro M.2. So thanks to;
gilles_polysoft: the man who showed the way.
erer: for pointing at the right "installer direction"
handheldgames: for the fine tutorial
dosdude1: thanks for providing the tools
Wow! Nice. I will keep my SSD for future updates. Boom!!! Wow.
Sorry if I'm happy! @Miks do the jump! Do it, just do it!
/Per
I´m on a cMP 5.1 (84´) and I just booted off my Samsung NVMe 960 Pro M.2. So thanks to;
gilles_polysoft: the man who showed the way.
erer: for pointing at the right "installer direction"
handheldgames: for the fine tutorial
dosdude1: thanks for providing the tools
Wow! Nice. I will keep my SSD for future updates. Boom!!! Wow.
Sorry if I'm happy! @Miks do the jump! Do it, just do it!
/Per
Nice! Great to see multiple confirmations of success. Amazing how after stagnating for so long it finally feels like a bit of a renaissance for the old cMP (thanks to gilles, dosdude1 and the others).
I read over the instructions for getting this to work. Does SIP need to remain disabled when your done in order for the nvme drive to boot?
No, but that has nothing to do with the NVMe. That is an SH and its APFS-system. But if you disable the SIP, go for BootChamp and have W10 on another SSD it will work.
/Per
/Per
EDIT : Moderators : I realise that strictly speaking I should have posted this in High Sierra : "What works" thread
but I feel that it is important to be certain that everything one depends on for pro use WORKS
in case an upgrade/hack fails or prevents vital apps from loading/performing.
================================================================
This is very off topic for this thread but very relevant for me if I am to go ahead with the NVMe boot bootROM update.
I have an English school here in Japan and 100% depend on my Canon LBP-1610 A3 format B/W laser printer ( A3 laser printers are still very expensive ! ).
I bought this laser printer in 2002 ( Yes ! it's now 16 years old ! ).
I've kept all the OS X Canon drivers since OS 9 and just one of them allows installation right up to High Sierra 10.13.5 ..
this also involved hacking the "Sandbox" though Terminal.
I've had it working flawlessly right up to 10.13.4 on a 2.5" SSD but. . after going up to 10.13.5 it would not print.
This virtually ruled out doing the NVMe EFI boot upgrade for me but today I had an inspiration .. .
I noticed that in comparing Library/Printer/InstalledPrinters.plist .. that the Canon LBP-1610 IS LISTED in my Siierra 10.12.6 installation on another SSD BUT NOT in the 10.13.5 "Library/Printer/InstalledPrinters.plist".
So. . I copied the plist entry in Sierra to the plist in 10.13.5 .. .
It worked ! .. and should be good for 10.13.6
I'm over the moon about this, it gives me confidence to go ahead with the NVMe BOOTING HACK.
If, after testing that all of my essential daily use apps work in 10.13.5 I'll go ahead with the NVME EFI boot upgrade.
You can see that the entry " <string>MANUFACTURER:Canon;MODEL:LASER SHOT LBP-1610 L</string>" is the one I copied from Sierra 10.12.6
but I feel that it is important to be certain that everything one depends on for pro use WORKS
in case an upgrade/hack fails or prevents vital apps from loading/performing.
================================================================
This is very off topic for this thread but very relevant for me if I am to go ahead with the NVMe boot bootROM update.
I have an English school here in Japan and 100% depend on my Canon LBP-1610 A3 format B/W laser printer ( A3 laser printers are still very expensive ! ).
I bought this laser printer in 2002 ( Yes ! it's now 16 years old ! ).
I've kept all the OS X Canon drivers since OS 9 and just one of them allows installation right up to High Sierra 10.13.5 ..
this also involved hacking the "Sandbox" though Terminal.
I've had it working flawlessly right up to 10.13.4 on a 2.5" SSD but. . after going up to 10.13.5 it would not print.
This virtually ruled out doing the NVMe EFI boot upgrade for me but today I had an inspiration .. .
I noticed that in comparing Library/Printer/InstalledPrinters.plist .. that the Canon LBP-1610 IS LISTED in my Siierra 10.12.6 installation on another SSD BUT NOT in the 10.13.5 "Library/Printer/InstalledPrinters.plist".
So. . I copied the plist entry in Sierra to the plist in 10.13.5 .. .
It worked ! .. and should be good for 10.13.6
I'm over the moon about this, it gives me confidence to go ahead with the NVMe BOOTING HACK.
If, after testing that all of my essential daily use apps work in 10.13.5 I'll go ahead with the NVME EFI boot upgrade.
You can see that the entry " <string>MANUFACTURER:Canon;MODEL:LASER SHOT LBP-1610 L</string>" is the one I copied from Sierra 10.12.6
Last edited:
Original eeprom is 4096kb, right? Adding every .ffs module enlargening the file size. All of these will fit in the free space of eeprom or should we look 8192kb eeprom for future updates?
dosdude1
If I go ahead with the NVMe DXE inject bootROM upgrade, first I just run RomTool ..
( shut down after that )
At cold startup do I have to HOLD DOWN the power button until I hear the firmware upgrade chime as happens with Apple firmware upgrades or just start up normally ?
Any need to do a PRAM reset ?
Thanks in advance.
If I go ahead with the NVMe DXE inject bootROM upgrade, first I just run RomTool ..
( shut down after that )
At cold startup do I have to HOLD DOWN the power button until I hear the firmware upgrade chime as happens with Apple firmware upgrades or just start up normally ?
Any need to do a PRAM reset ?
Thanks in advance.
I will suggest to remove all not standard like pcie m2 card this way no PRAM reset maybe not necessary
You can install them after flash
1. Dump your Boot-rom
2. Save a copy
3. Inject the NVMe.ffs
4. Made a install USB with High Sierra 10.13.5 with the Firmware folder deleted.
5. Shut down with 15 sec wait (did a minute just to be sure).
6. Cold start-up with holding the power button. (did not remove anything, all disk mounted)
7. Flash with new Boot-rom+NVMe
8. Fresh install of High Sierra from USB onto the NVMe in PCIe slot 3
9. Just did a reboot, just to check that it was true
/Per
2. Save a copy
3. Inject the NVMe.ffs
4. Made a install USB with High Sierra 10.13.5 with the Firmware folder deleted.
5. Shut down with 15 sec wait (did a minute just to be sure).
6. Cold start-up with holding the power button. (did not remove anything, all disk mounted)
7. Flash with new Boot-rom+NVMe
8. Fresh install of High Sierra from USB onto the NVMe in PCIe slot 3
9. Just did a reboot, just to check that it was true
/Per
The DXE modules can be compressed (quite significantly, actually... Usually down to about half their original size). If somebody can upload all the DXE modules needed, I'll compress them, and test fit them into my MP5,1's 4MB ROM dump.
Just a question, could this be done using UEFITool instead of DXEInject tool? Also what DXE modules do you want? I can extract them from any firmware.
Yeah, you could use UEFITool... That's what DXEInject is based off of. The only DXE module I don't have is the USB3.0 one.
Not sure what controller then iMac Pro uses but I'm guessing Intel. I expect most cMP users need the FL100 based driver from the nMP, but I'm not sure.
I already tried the MP6,1s ones on my MP5,1
the FL1100 driver never loaded and I noticed it seemed to of have some sort of dependancy of some kind...
the XHCI driver did load and it did seem to recognise my USB 3 card and USB devices connected to it kinda... in that it hard locked up the Mac Pro if I invoked the boot picker LOL (and my USB 3 sticks blinking Read Write LED was on solid)
dosdude1, LightBulbFun
I'm just about ready to do the NVMe bootROM flash to my MP51.0085.B00 4,1>5,1 cMP.
After the firmware is flashed is it OK to restore a working Carbon Copy Clone of my HFS+ High Sierra 10.13.5 internal SSD install to my Samsung 960 EVO ?
I'm not ashamed to say that I'm still a bit nervous about this . . . .
I've backed up my MP51.0085.B00 bootROM and have had the NVMe DXE driver.ffs injected by a kind member here prior to dosdude1 releasing his Inject DXE tool.
I'm just about ready to do the NVMe bootROM flash to my MP51.0085.B00 4,1>5,1 cMP.
After the firmware is flashed is it OK to restore a working Carbon Copy Clone of my HFS+ High Sierra 10.13.5 internal SSD install to my Samsung 960 EVO ?
I'm not ashamed to say that I'm still a bit nervous about this . . . .
I've backed up my MP51.0085.B00 bootROM and have had the NVMe DXE driver.ffs injected by a kind member here prior to dosdude1 releasing his Inject DXE tool.
It’s probably a better idea to do it yourself. With the new tools.
Maybe there is a dependency that is missing, I will look through the iMac Pro firmware I extracted it from and see what I can find. Maybe its this UsbMassStorage module that is needed.
Last edited:
- Status