Edit 1: Will do. I'm currently waiting on the adapter to get delivered and then I will see how things go.
Edit 2: I just ran everything that I went through and I think it did work! I'm waiting for the adapter to come but I ran all the commands on an apple SSD. I don't see any reason of this not working on an non-apple ssd since we are manually updating the EFI.
@tshelby73 It passed the integrity check with no problems!
@erudyne, The firmware file name and version would remain the same since we actually modifying just a piece of the original firmware. Here's how i confirmed:
From the original Mojave update file, you had extracted your MBP firmware right? In my case, the firmeware was MBP112.SCAP file.
Using this article as a guide: https://www.modmy.com/how-mount-your-efi-partition-macos
I copied the firmware onto my desktop and compared the two.
Edit 3: See the attached screenshoot. The left shows the original firmware for my MBP 15, 2013 A1398. The guide provided by CMD+Q (Click on most liked posts) told me what firmware to use.
The right shows the firmware currently sitting on my EFI volume with the updated driver from the 2015 version.
For anyone wanting to try this, please note that I mentioned earlier that I had the original ssd in the macbook when i updated my firmware manually.
Could someone please try this out with a non apple ssd? My adapter is still being shipped so I can't try out yet. If it does work, I will try to replicate the steps and if needed, post a guide.
Edit 4: Re-uploaded screenshot and added modified plus 2015 version of the same nvme driver. I'm really confused why as to why an external device was needed now. Did I modify the right thing?
Thanks for your investigation!
But just to make sure:
The EFI partition is not your BootRom; It's a partition on your HDD/SSD that is loaded prior to loading the actual macOs.
It looks to me like you have written the update file to your EFI partition but not to your BootRom. The BootRom resides on your Logicboard on a separate chip and is responsible for "early stage" booting - even if no HDD/SSD is present.
Are you sure, the BootRom has actually been updated with your "fixed" driver?