when you are done give us update please and quick remark of how all is workin'No this is my first time doing this.
Just wanted to update to the latest version of High Sierra before starting
when you are done give us update please and quick remark of how all is workin'No this is my first time doing this.
Just wanted to update to the latest version of High Sierra before starting
Just updated a 13-inch MacBook Pro Late 2015 from 10.13.4 to 10.13.5, using the combo update..
looks like the BootROM was updated from MBP121.0175.B00 to MBP121.0176.B00.
If someone were to tell me what to look for, I could report on whether or not the NVMe driver was patched/updated or not..
The firmware only gets updated with the original drive in the MacBook. This is what I found with two different early 2015 13" Air and my late 2013 13" Pro.
Maybe it depends on the nvme drive in the machine? Firmware wouldn't update for me with an Intel 600p in place.Not true, at least with my late 2013 15” rMBP, Bootrom did update to 146.
Disks also still show up as external in the boot chooser after I type my EFI password. Control choosing the correct boot volume eliminates the delay.
Maybe it depends on the nvme drive in the machine? Firmware wouldn't update for me with an Intel 600p in place.
Not true, at least with my late 2013 15” rMBP, Bootrom did update to 146.
Maybe it depends on the nvme drive in the machine? Firmware wouldn't update for me with an Intel 600p in place.
when you are done give us update please and quick remark of how all is workin'
Yes, the output is the same as “bless” with the modified UEFI capsule (SCAP). EFIUPDATER (per the paper referenced above) seems to be picking the SCAP/FD files from a directory based on MacBook model and detected EFI ROM versions. Force-update in EFIUPDATER correctly picks up the modified SCAP (in my case, 0146 to Modified 0146 on a MBP11,1): I can see the SCAP file being copied to the EFI paritition and the NVRAM variables for boot changing, but it is not actually flashing the ROM upon boot - neither with the NVMe drive nor the stock SSD. There is probably some checksum/signature check that will need to be defeated, and that check is not in “bless” or “efiupdater”.
I had high hopes that 0146 on MBP11,1 introduces proper NVMe support (the DXE section did change between 0145 and 0146).
I'll try to answer some of your questions.So it seems I ordered the wrong adapter from sintech, but I can't seem to find a valid reason. The adapter I ordered is apparently the original? (http://eshop.sintech.cn/ngff-m2-pcie-ssd-card-as-2013-2014-2015-macbook-ssd-p-1139.html)
Can someone please help me in telling me why this might be the wrong adapter can it be fixed(saw a post about a guy soldering his) and then which adapter should I buy and why. I have a macbook pro mid 2014 256gb at the moment and would like to upgrade my internal storage.
I'm just worried now after reading the thread and all the issues people seem to be having that:
1. Battery life is going to go bad
2. The extra heat might damage components around the ssd bay
3. Might not be able to update macos cause of a nvme modified rom that might need to be installed to get hibernation back.(Can someone with more knowledge help with this please)
4. If it is only the nvme rom which is modified to the 2015s rom will I be able to do normal software updates on MacOS and just have to put back the orginal ssd when I need to upgrade the bootrom?
Thanks guys