Uefitool For Mac
Posted : admin On 10.09.2019Hi everyone, long story this evening. I did some test with patching the BootRom on my trusty late 2013 rMBP. It's too soon to tell that the patch I did was successful, but at present it seems to work.
Here is what I wanted to do: I had previously watched into and compared BootRom files between rMBP late 2013 and early - mid 2015. I had extracted EFI payloads files from the High Sierra installer, and compared them with UEFI tool. I had seen some differences between the NVMe DXE drivers include in the BootRoms: all DXE drivers are located at an address starting with 51116915, but those from 2013-2014 macs bootroms all have a size of 10382 bytes, while all DXE drivers from 2015 and later macs are 25820 bytes wide.
Nikolaj Schlej (@NikolajSchlej) August 5, 2016 UEFITool repo will be handed over to []. UEFITool is a Qt-based GUI tool that works on Mac/Windows/Linux.
Also, 2015 macs have an NVMe entry in the compiled DSDT table included in the EFI. I must also say I had previously success with patching an UEFI of an old Fujitsu TX140 server (I did successfully added to its UEFI/bios a generic NVMe DXE driver in order to make it recognize NVMe drives at boot: ). So I wanted to do the same with my late 2013 rMBP, and edit its BootRom so that it would include the proper NVME driver and DSDT table reference. Here is what I did: - I bought an EFI cable at MacUnlocks: - I already had an SPI programmer, a little EZP-2013 which does works great (even under windows 8.1 64 bits) Ok, so the first tries were epic fails. The dump of BootRom I did were never the same, and the rom file was not editable in UEFI tool. I was too scared of briking my rMBP.
What was in cause? I thought I had a bad cable, or any other problem, and managed to unsoldered the SPI rom and connect it directly on the EZP programmer. With no luck: I had the same unreliable results. Worse, in desoldering the SPI rom I did loose some resistor, and had to read the schematics and find some new 33k resistors and solder them in the proper place. Once the SPI rom again in place, I did some googling and find that other had same problems: I have read somewhere (here: ) that the power supplied by the SPI programmer wasn't strong enough. So I did a little mod to my programmer and added an iPhone battery to provide it a 3.7-3.9V supply (not so clean but sorry. I was lazy this time).
And that time the dump of the SPI eeprom worked, I could even do it with the logic board in place, without having to desolder anything! What next: with the full dump of my SPI bootrom, I could to some patch to it without any fear to brick my mac. So I did extract the full BootRom, and did the following: - open the BootRom of a rMBP 2015 with UEFI Tool for Mac, find the NVMe DXE driver and extract it - open the BootRom of my rMBP 2013 with UEFI Tool for Mac, and replace the NVMe DXE driver with the new one from the 2015.
Next the DSDT Table: - find and extract the compiled (assembly langage) DSDT table of a 2015 Mac, and decompile it with MacIASL - find and extract the compiled (assembly langage) DSDT table from my 2013 Mac, and decompile it with MacIASL - compare the difference to add the NVMe reference (I know nothing in ACPI tables, I just add at line 288 the line 'NVME, 8' just before 'Offset 0x12C) - recompile the DSDT table as an aml file, and insert it back in the BootRom of my 2013 mac. EDIT 2018-05-30: seems the whole DSDT table edition is not necessary.
Then I just flashed inplace my BootRom with the obtained file. And the result: the NVMe SSD is still orange at startup menu, but who cares.
Startup is now without any delay. Hibernation now works fully. (I tested 4 times, with setting standby to 1 and standbydelay to 10s) I think some tests need to be done, but a step has been made! GillesPolysoft, thats one brave move there mate - I've already bricked a tablet trying to pull stunts like that. It will be good if you eventually make a tool that will allow members of the forum to flash their roms so as to eliminate the hibernate issues on the 2013-2014 model computers.
This thread has been an absolute gold mine of information. Thankyou to all the contributers. My ebay adapter has turned up as has the SSD, now just waiting for the macbook itself to arrive (another brave stunt - buying a macbook on ebay LOL). I won a 2013 I7 16Gb macbook with a 256Gb flash drive. Long story short, I used to have a 2012 macbook pro, but someone stole it, and being on a not so great income at that stage meant I have had to wait till now to be able to afford a new unit!
Uefitool For Mac Os
Ecu dowdy student stores. At my disposal is a hackintosh with two nvme slots, so I should be able to update firmwares where needed, and if the Toshiba XG5 512Gb disk doesn't want to co-operate (the one I ordered for the mac), I can swap it out by carbon copy cloning my Samsung 960 Evo in the hack to the backup spinning drive, swap the two, and CCC it back to the toshiba, allowing it to be the boot drive for my hack, and the main disk in the macbook will then be the Samsung. Triboot usb stick on hand too, for macOS, Ubuntu and windows. Since the 'book comes with sierra installed, I will install high sierra so as to update the boot rom. Also have two sintech adapters coming (as seperate orders no less), a 'b' type (which sometimes gets black, sometimes gets big green; the one that comes with the screw drivers), and a long black 'C' type. Also have a PCI-E to apple SSD adapter for the original apple SSD, but may just end up getting an OWC caddy and using it as a big USB stick. Edit: typo's, and I swore - sorry. Ok Team: I'm happy to report that I have finally been able to upgrade my MBPr mid 2014 A1398 EMC 2876 with the Samsung 960 Evo NVME PCIE M.2 SSD + High Sierra + third party adapter board.
I live in Silicon Valley and I am an automation engineer (not a software developer). I cannot stand the site of the Apple young engineers, whose mission in live is to put up road blocks to keep Apple products artificially high cost - instead of competing on the high quality and innovative products. The bottomline is the Samsung Evo NVME drive is upgradeable on the MBPr mid 2014 + Bootcamp.after about two weeks of messing around with the apple's road blocks, it finally works! Some keys take away: - Be patient - The overheat problem will go away if you keep the power supply plugged in all the time ( I have a theory why - but I could be wrong.) - Backup your Mac and Windows 10 partitions on an external SSD drive using Carbon Copy Clone to backup/restore the Mac partition - and backup/ restore your Windows partition using AOEMI partition assistant and AOEMI back upper.
Do not use Apple's BootCamp assistant because it will lock your drive up with some messy EFI (GUID) schemes that will forever curse your life (anytime you want to change/ resize the partition or upgrade your MBPr). Winclones is essentially useless - accept for one last step: 'make the disk (partition) EFI Bootable' - Once again you'd need to create a bootable external SSD drive ( for both Mac and Windows) and clone/ restore the Mac and Windows partitions. Good luck and PM me if you have any question - I just don't want to reveal the work around because the little Apple Wizels will try to put up more roadblocks. Wow, that's a great improvement for our dusty machines sir.
I'm waiting native nvme as a 4.1-5.1 user quite long time. If you provide rom dump, I will check the other uefi part of the rom. Maybe we will find some overclock settings, pci express speed settings, basic video rom for non flashed cards etc. Edit I've just checked firmware restoration cd and unzipped. There is 4 file in the folder. 0/1/2 and 3.hfs or the biggest is efi/bios file. I opened 3.hfs with UEFITool and I can see the modules.
I can insert any module even NVMe but there is a problem. Our machines (Mac Pro 4.1 - 5.1) have updated/better bootrom if HS installed than Apple's firmware restoration cd release.
Hi everyone, long story this evening. I did some test with patching the BootRom on my trusty late 2013 rMBP. It's too soon to tell that the patch I did was successful, but at present it seems to work.
Here is what I wanted to do: I had previously watched into and compared BootRom files between rMBP late 2013 and early - mid 2015. I had extracted EFI payloads files from the High Sierra installer, and compared them with UEFI tool. I had seen some differences between the NVMe DXE drivers include in the BootRoms: all DXE drivers are located at an address starting with 51116915, but those from 2013-2014 macs bootroms all have a size of 10382 bytes, while all DXE drivers from 2015 and later macs are 25820 bytes wide. Also, 2015 macs have an NVMe entry in the compiled DSDT table included in the EFI. I must also say I had previously success with patching an UEFI of an old Fujitsu TX140 serveur (I did successfully added to its UEFI/bios a generic NVMe DXE driver in order to make it recognise NVMe drives at boot: ). So I wanted to do the same with my late 2013 rMBP, and edit its BootRom so that it would include the proper NVME driver and DSDT table reference.
Here is what I did: - I bought an EFI cable at MacUnlocks: - I already had an SPI programmer, a little EZP-2013 which does works great (even under windows 8.1 64 bits) Ok, so the first tries were epic fails. The dump of BootRom I did were never the same, and the rom file was not editable in UEFI tool. I was too scared of briking my rMBP. What was in cause? I thought I had a bad cable, or any other problem, and managed to unsoldered the SPI rom and connect it directly on the EZP programmer. With no luck: I had the same unreliable results.
Worse, in desoldering the SPI rom I did loose some resistor, and had to read the schematics and find some new 33k resistors and solder them in the proper place. Once the SPI rom again in place, I did some googling and find that other had same problems: I have read somewhere (here: ) that the power supplied by the SPI programmer wasn't strong enough. So I did a little mod to my programmer and added an iPhone battery to provide it a 3.7-3.9V supply (not so clean but sorry.
I was lazy this time). And that time the dump of the SPI eeprom worked, I could even do it with the logic board in place, without having to desolder anything!
What next: with the full dump of my SPI bootrom, I could to some patch to it without any fear to brick my mac. So I did extract the full BootRom, and did the following: - open the BootRom of a rMBP 2015 with UEFI Tool for Mac, find the NVMe DXE driver and extract it - open the BootRom of my rMBP 2013 with UEFI Tool for Mac, and replace the NVMe DXE driver with the new one from the 2015. Next the DSDT Table: - find and extract the compiled (assembly langage) DSDT table of a 2015 Mac, and decompile it with MacIASL - find and extract the compiled (assembly langage) DSDT table from my 2013 Mac, and decompile it with MacIASL - compare the difference to add the NVMe reference (I know nothing in ACPI tables, I just add at line 288 the line 'NVME, 8' just before 'Offset 0x12C) - recompile the DSDT table as an aml file, and insert it back in the BootRom of my 2013 mac. Then I just flashed inplace my BootRom with the obtained file. And the result: the NVMe SSD is still orange at startup menu, but who cares. Startup is now without any delay.
Hibernation now works fully. (I tested 4 times, with setting standby to 1 and standbydelay to 10s) I think some tests need to be done, but a step has been made! After reading thousands of replies in this thread, I chose the Toshiba XG3 1TB for my MacBook Air 2015 11', thought it would be a hassle-free solution for the upgrade. The installation of macOS 10.13.4 went well and the speed is acceptable due to the pcie2.0x4 limitation. However, it can't wake up after deep sleep and shows a folder icon with a question mark. The laptop then reboots and shows a kernel panic report. This problem has been temporarily solved with the hibernatemode 25.
Uefitool For Mac
Bootcamp (win10 1803) works fine for me. The benchmark seems to be ok. But everytime when i try to reboot from the OS, it fails to recognize my ssd as if it doesn't exist.
I guess it has something to do with the sleep issue under mac os. Looking forward to advice and help. Thanks in advance.
MacSurfer's Headline News™ Monday, December 3, 2018 Checked 8:10 AM; Last Updated 8:00 AM CST; 14:00 GMT.