It appears that System Firmware/Boot ROM 427.0.0.0.0 on my Late 2013 13" MacBook Pro (MacBookPro11,1) with macOS Catalina 10.15.7 does not require messing with the hibernation settings or patching to address hibernation issues. However, the hibernation and autopoweroff behavior appears to be have changed entirely. Does anybody else have experienced this with the new firmware on these older MacBook Pro models?
It handles it fine. Just don’t use NVMeFix/Lilu at the moment, it crashes the OS (at least last time I tried it did)
Wonderful. I just ordered a 1TB WD Blue and a Sintech adapter to upgrade my paltry 128gb 2014 MacBook Pro 13".
Thank you for the instructions
EFI found at IODeviceTree:/efi
Failed to stat firmware file, MBP112.scap: 2
Error while writing firmware updater for EFILast week I updated just the OS. The SSD replacement I did a couple of months ago. But anyway, I am using the SanDisk Ultra 500gb and updated the macOS directly on it.
It's a mbp 13 but it's viewed as a mbp 11,1 in the system information. I have already seen the case before to some other people.
This looks pretty good: the firmware has been staged. All you'd need to do is to gracefully shutdown the MacBook Pro and then power it back up. The system firmware update should commence immediately. Essentially, you are performing the firmware upgrade that would happen during a macOS upgrade. Good luck!
Yes, you will need to download the entire macOS Big Sur installation. I built a disk image from the installer app and provided the path to the system firmware files relative to the installer app in my post. However, you should find the files required in
/Library/Updates if you downloaded Big Sur using Software Update in System Preferences. Does that help?You are likely referencing a file that does not exist. Did you obtain the system firmware file from the macOS Big Sur installer app? I recommend placing the system firmware file into a folder on your desktop or similarly accessible in your home folder. Hope this helps.
you are correct this helped and produced the attached logs, but when i shut down and power up again nothing is changed
EFI found at IODeviceTree:/efi
Will need to copy 8523776 bytes to EFI system partition
No auxiliary booter partition required
System partition found
Preferred system partition found: disk0s1
Returning booter information dictionary:
{
"Auxiliary Partitions" = (
);
"Data Partitions" = (
disk1s5s1
);
"Preboot Volumes" = (
disk1s2
);
"System Partitions" = (
disk0s1
);
}
Mounting at /Volumes/bless.jtY2
Executing "/sbin/mount"
Executing: /usr/bin/kmutil load -p /System/Library/Extensions/msdosfs.kext
Returned 0
Creating /Volumes/bless.jtY2/EFI/APPLE/FIRMWARE if needed
Deleting previous contents of /Volumes/bless.jtY2/EFI/APPLE/FIRMWARE
Deleting /Volumes/bless.jtY2/EFI/APPLE/FIRMWARE/MBP112.scap (8520304 bytes)
Opened dest at /Volumes/bless.jtY2/EFI/APPLE/FIRMWARE/MBP112.scap for writing
preallocation not supported on this filesystem for /Volumes/bless.jtY2/EFI/APPLE/FIRMWARE/MBP112.scap
/Volumes/bless.jtY2/EFI/APPLE/FIRMWARE/MBP112.scap created successfully
No auxiliary booter partition required
System partition found
Preferred system partition found: disk0s1
Returning booter information dictionary:
{
"Auxiliary Partitions" = (
);
"Data Partitions" = (
disk1s1
);
"Preboot Volumes" = (
disk1s2
);
"System Partitions" = (
disk0s1
);
}
Bad path for boot item: /Users/amr/Desktop/bigSur/MBP112.scap
Relative path of /Volumes/bless.jtY2/EFI/APPLE/FIRMWARE/MBP112.scap is \EFI\APPLE\FIRMWARE\MBP112.scap
IOMedia disk0s1 has UUID 4833C283-439B-49F2-816E-C6866E45502F
Executing "/sbin/umount"
Returned 0
Write to RTC: 0
Setting EFI NVRAM:
{
"efi-apple-recovery" = "<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>4833C283-439B-49F2-816E-C6866E45502F</string></dict></dict><key>BLLastBSDName</key><string>disk0s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\\EFI\\APPLE\\FIRMWARE\\MBP112.scap</string></dict></array>";
}The messages look exactly like mine; the system firmware appears to be staged correctly. The only thing I do afterwards is select "Shut Down..." from the menu, wait 5 seconds after the screen is dark, and then power the system back up. I do not use bootcamp, and I have my startup disk set to macOS.
Yes, it should. Ever since Catalina, the firmware updates have worked seamlessly on my MacBookPro11,1 with the non-Apple SSD installed. I wonder if you need to be on a certain firmware version to make future firmware updates. Sorry that this does not work for you and @amr-213.
It is what it is. Thanks for your follow up anyway. I'll wait untill the next update to see if anything will change. Otherwise I'll try with another ssd. Cheers.
My two suggestions: