Become a MacRumors Supporter for $25/year with no ads, private forums, and more!

photochthon

macrumors newbie
Original poster
Feb 13, 2020
9
1
Greetings - first post, relatively new to forums in general, thanks for being patient with me!

I am attempting to upgrade a 13" mid 2010 MBP running El Capitan. I have a series of questions pertaining to the general sequence of actions I need to take as well as what those specific actions are and how they are best performed.

I need to cross a few different chasms here: from El Capitan to High Sierra; from HDD to SSD; from HFS+ to APFS. I have two identical HDD bootable clones made with CCC. I have been slogging through what feels like 20% of the internet today trying to wrap my head around all the steps in this process.

I have a Crucial MX500 SSD and a new HD cable to install in the MBP. I have been warned (by a couple of very helpful, pro greybeards on iFixit) against cloning from a CCC bootable clone to move my data and instead to install the SSD, clean install High Sierra (for the sake of the APFS) and then run Migration Assistant from the current (by then removed) HDD via USB. I am prepared to remake the backups in a better way if using CCC is to be avoided. This is my working plan, with questions inserted:

Make bootable installers for El Capitan and High Sierra
(Do I have to do this? Will I be able to clean install OS from Recovery in a backup?)

Make current (preferably bootable) backups for the HDD currently in the machine.
(Can I do this without CCC? Using Disk Utility?)

Upgrade HDD to High Sierra.

Upgrade the backups to reflect the OS upgrade.
(What about the HDD externals' file system? APFS? HFS+? Can I create an exact copy using "Restore a Disk" in Disk Utility? Again, will it be bootable?)

Install SSD and replace HD cable.

Clean Install High Sierra on SSD
(Use Recovery Mode on one of the backups? Boot from USB installer?)

Use Migration Assistant to move data from HDD to SSD.
(Or "Restore a Disk" in Disk Utility from a backup?)

Upgrade RAM from 4GB to 16GB.

Sit back, amazed that this seemingly interminable task has been completed!

Also, the HDD in my computer is old and probably failing (original to my refurbished purchase in 2011), does it really make sense to move data from this disk versus one of my brand new WD 2TB HDD drives I'm using for backup?

Okay, I think that's it. I'm in a muddle - I keep making progress and hitting snags. The actual physical install seems like a piece of cake next to preparing for it. Thank you in advance for your assistance.

EDIT: I am performing this upgrade at home where my only internet connection is through tethering to my phone, so Internet Recovery is out of the picture unless I camp out somewhere with wifi.
 

Fishrrman

macrumors Core
Feb 20, 2009
21,529
7,782
Get an EXTERNAL 2.5" USB3 enclosure if you don't have one.
They're cheap, under $10.

Get the SSD (the one that will end up in the MBP) into the enclosure.

Now, erase (format) it to Mac OS extended with journaling enabled, GUID partition format.

Now, install High Sierra onto it (drive will be automatically converted to APFS).

When done, run the setup assistant.
IMPORTANT
You can use setup assistant to migrate your data from the internal drive to the new SSD.
I recommend that you do this.

When setup assistant is done, DO ONE OR MORE TEST BOOTS while the SSD is still in the enclosure.
Reboot, and IMMEDIATELY hold down the option key and KEEP HOLDING IT DOWN until the startup manager appears. Select the external SSD and hit return.
Do you get a good boot?

OK, now it's time to "do the disk swap".

Take out the old HDD and hard drive cable if you're going to replace that.
Put the new SSD and cable it, close it up.

Now, THE MOMENT OF TRUTH:
Again, use the "option key trick" to start.
DO YOU GET A GOOD BOOT?
If so, fine, now and important step:
Log in, go to the startup disk pref pane, and select the new SSD to be the NEW boot drive.

Now, reboot once more.
You should go right to the login screen.
If so, that's it.

A final thought:
THE REASON for doing the install with the external enclosure is that you can "prep and test" the new SSD WITHOUT disturbing your current OS setup. If things don't go as planned, you'll still have a working computer.
Got that...?
 
Last edited:
  • Like
Reactions: photochthon
Comment

iluvmacs99

macrumors 6502a
Apr 9, 2019
746
533
Greetings - first post, relatively new to forums in general, thanks for being patient with me!

I am attempting to upgrade a 13" mid 2010 MBP running El Capitan. I have a series of questions pertaining to the general sequence of actions I need to take as well as what those specific actions are and how they are best performed.

I need to cross a few different chasms here: from El Capitan to High Sierra; from HDD to SSD; from HFS+ to APFS. I have two identical HDD bootable clones made with CCC. I have been slogging through what feels like 20% of the internet today trying to wrap my head around all the steps in this process.

I have a Crucial MX500 SSD and a new HD cable to install in the MBP. I have been warned (by a couple of very helpful, pro greybeards on iFixit) against cloning from a CCC bootable clone to move my data and instead to install the SSD, clean install High Sierra (for the sake of the APFS) and then run Migration Assistant from the current (by then removed) HDD via USB. I am prepared to remake the backups in a better way if using CCC is to be avoided. This is my working plan, with questions inserted:

Make bootable installers for El Capitan and High Sierra
(Do I have to do this? Will I be able to clean install OS from Recovery in a backup?)

Make current (preferably bootable) backups for the HDD currently in the machine.
(Can I do this without CCC? Using Disk Utility?)

Upgrade HDD to High Sierra.

Upgrade the backups to reflect the OS upgrade.
(What about the HDD externals' file system? APFS? HFS+? Can I create an exact copy using "Restore a Disk" in Disk Utility? Again, will it be bootable?)

Install SSD and replace HD cable.

Clean Install High Sierra on SSD
(Use Recovery Mode on one of the backups? Boot from USB installer?)

Use Migration Assistant to move data from HDD to SSD.
(Or "Restore a Disk" in Disk Utility from a backup?)

Upgrade RAM from 4GB to 16GB.

Sit back, amazed that this seemingly interminable task has been completed!

Also, the HDD in my computer is old and probably failing (original to my refurbished purchase in 2011), does it really make sense to move data from this disk versus one of my brand new WD 2TB HDD drives I'm using for backup?

Okay, I think that's it. I'm in a muddle - I keep making progress and hitting snags. The actual physical install seems like a piece of cake next to preparing for it. Thank you in advance for your assistance.

EDIT: I am performing this upgrade at home where my only internet connection is through tethering to my phone, so Internet Recovery is out of the picture unless I camp out somewhere with wifi.

Someone here had already posted a good guide to upgrade your Macbook Pro 2010 to High Sierra, so I won't repeat.

I will explain the main reason why some guys on iFixit said it's a bad idea to clone the boot drive with HS back into the SSD for your Macbook Pro 2010. And the reason is that, cloning the drive back to SSD WILL NOT UPDATE your Macbook Pro 2010 firmware. The firmware that is needed to support APFS. If you just simply clone an installed High Sierra drive from an external SSD or install it on an external SSD, the installer WILL NOT INSTALL the SMC firmware and the BOOT firmware needed to support APFS. So while it may seem that you may have success installing High Sierra on an external SSD or SSD on the external drive enclosure, eventually you will be greeted by a grey screen with a slash sign; meaning that your computer can not support this OS. A sign that the computer wasn't firmware updated.

Apple changed this update method in 2018 or mid-2019 (can't remember offhand) from a sequence of number and alphabets with their SMC and Boot firmware to just a series of numbers with their boot firmware. The implication to this change is that, in order to successfully and properly update your macbook pro 2010 firmware to the latest to support APFS, you need to install High Sierra over an existing OS like El-Capitan ON AN ORIGINAL Apple stock drive. It won't install the new firmware on a NON-Apple SSD drive.

Once you have the new firmware, you can clone the content of the High Sierra install from your original stock Apple drive or drive inside your Macbook Pro to the new SSD. Then move the SSD into the Macbook Pro and it will boot properly.

I work in a computer recycling and refurbishing store and I had seen many instances of people facing the grey screen with a slash sign and usually it's because they installed HS on an external SSD or HD or clone the drive where cloning and installing on an external SSD will not update your Apple firmware. That's how Apple set it up. You also need to make double sure your SMC and Boot firmware are properly updated by checking the firmware version against what Apple published. Only then you would proceed to do the rest.

I hope this helps.
 
Last edited:
Comment

photochthon

macrumors newbie
Original poster
Feb 13, 2020
9
1
Fishrrman - Thank you - this is great and straightforward! I already have the SSD installed in an SATA to USB enclosure, so it's ready to go.
[automerge]1581826310[/automerge]
iluvmacs99 - Thank you for your explanation - this is precisely the information I wanted to know. I will update the original Apple stock HDD and double check the firmware information before I go any further.

I had mentioned to the guys on iFixit that I was planning to clone from a CCC bootable clone to the SSD when they warned me against cloning. If I first upgrade the original HDD to HS and make sure the firmware is correct, cloning from the original HDD to the SSD will present no problem? They got me all worried about using CCC to make bootable clones, but maybe it was just the firmware issue they were referring to (they didn't explain, just said they'd seen issues). I currently have two identical CCC bootable clones of the HDD that came with (and is still in) the computer; if anything goes awry with the upgrade to HS will I still be alright? Thanks again!
 
Last edited:
Comment

iluvmacs99

macrumors 6502a
Apr 9, 2019
746
533
Fishrrman - Thank you - this is great and straightforward! I already have the SSD installed in an SATA to USB enclosure, so it's ready to go.
[automerge]1581826310[/automerge]
iluvmacs99 - Thank you for your explanation - this is precisely the information I wanted to know. I will update the original Apple stock HDD and double check the firmware information before I go any further.

I had mentioned to the guys on iFixit that I was planning to clone from a CCC bootable clone to the SSD when they warned me against cloning. If I first upgrade the original HDD to HS and make sure the firmware is correct, cloning from the original HDD to the SSD will present no problem? They got me all worried about using CCC to make bootable clones, but maybe it was just the firmware issue they were referring to (they didn't explain, just said they'd seen issues). I currently have two identical CCC bootable clones of the HDD that came with (and is still in) the computer; if anything goes awry with the upgrade to HS will I still be alright? Thanks again!

When your firmware is updated, then yes it will be no problem. I had this problem with my Macbook Air and nobody at Apple could figure it out until I realized the firmware on my Air was too old. When it updated, then everything is fine. I did a few for our clients and they all went smoothly!
 
Comment

photochthon

macrumors newbie
Original poster
Feb 13, 2020
9
1
When your firmware is updated, then yes it will be no problem. I had this problem with my Macbook Air and nobody at Apple could figure it out until I realized the firmware on my Air was too old. When it updated, then everything is fine. I did a few for our clients and they all went smoothly!
Great, thank you!
And if I understand correctly what Bombich is saying, it looks like once I have switched over to the SSD as my new startup disk running High Sierra in APFS I will also still be able to clone it to my HFS+ formatted HDDs with CCC 5: "CCC 5 can make a bootable backup from an APFS-formatted volume to an HFS+ formatted volume or to an APFS-formatted volume."
 
Comment

iluvmacs99

macrumors 6502a
Apr 9, 2019
746
533
Great, thank you!
And if I understand correctly what Bombich is saying, it looks like once I have switched over to the SSD as my new startup disk running High Sierra in APFS I will also still be able to clone it to my HFS+ formatted HDDs with CCC 5: "CCC 5 can make a bootable backup from an APFS-formatted volume to an HFS+ formatted volume or to an APFS-formatted volume."

Yes. CCC5 claims are correct but with certain caveats. Some USB enclosures that used to be bootable with older firmware will be rendered un-bootable with the new firmware. There are certain OWC models that were bootable before High Sierra and APFS and then no longer boots after the firmware update. Another Apple way of shutting out USB bootable and forcing people to buy Thunderbolt drives.
 
Comment

photochthon

macrumors newbie
Original poster
Feb 13, 2020
9
1
Ugh. The planned obsolence of non-Thunderbolt drives also pushes people with computers as old as mine to buy new ones. As much as I have loved Apple products (my first Apple arrived I think in 1987) I've already begin learning about Linux and repairability ranking of non-Apple laptops. I just bought two Western Digital USB enclosures (WD Elements 2TB) for use as bootable clones - what is the best way to determine (preferably in advance) whether or not they will work with High Sierra and APFS?
 
Comment

iluvmacs99

macrumors 6502a
Apr 9, 2019
746
533
Ugh. The planned obsolence of non-Thunderbolt drives also pushes people with computers as old as mine to buy new ones. As much as I have loved Apple products (my first Apple arrived I think in 1987) I've already begin learning about Linux and repairability ranking of non-Apple laptops. I just bought two Western Digital USB enclosures (WD Elements 2TB) for use as bootable clones - what is the best way to determine (preferably in advance) whether or not they will work with High Sierra and APFS?

You need to find a machine that has the updated SMC and boot firmware with High Sierra or Mojave (a Mac that supports High Sierra and lower) and then press the "Option" key when booting up. If the boot manager sees your WD Elements 2TB as a boot partition, then it will show on the boot manager as being bootable. If not, then it's not. I have the NexStar TX USB 3 enclosure which Bombich certified as being High Sierra and APFS compatible, which it is. But I think there are a few others that work just as well.
 
Comment

photochthon

macrumors newbie
Original poster
Feb 13, 2020
9
1
You need to find a machine that has the updated SMC and boot firmware with High Sierra or Mojave (a Mac that supports High Sierra and lower) and then press the "Option" key when booting up. If the boot manager sees your WD Elements 2TB as a boot partition, then it will show on the boot manager as being bootable. If not, then it's not. I have the NexStar TX USB 3 enclosure which Bombich certified as being High Sierra and APFS compatible, which it is. But I think there are a few others that work just as well.
Thank you very much, I will give this a try!
 
Comment

photochthon

macrumors newbie
Original poster
Feb 13, 2020
9
1
I hope it's not poor form to revive an old post, but I've finally been able to upgrade to High Sierra and have a question about the BOOT firmware update and APFS compatibility before I proceed with the hardware upgrade. Thank you for any further insight you can provide!

You also need to make double sure your SMC and Boot firmware are properly updated by checking the firmware version against what Apple published. Only then you would proceed to do the rest.

System Information shows that my SMC version matches what Apple has published here (my computer is a MacBook Pro 13-inch, Mid 2010; MacBookPro7,1), but the BOOT version is different. According to the link above, Apple's most current version is MBP71.0039.B0E (EFI 2.5), while my computer is reporting MBP71.003F.B00.

I have tried to update to the most current version manually (both before and after updating to High Sierra) and got a window indicating this version was not compatible with my system.

Does this mean I won't be compatible with APFS? Should I not upgrade to the SSD? My HDD is at least nine years old and running more slowly with each OS update I have performed - I feel like I'm lucky it's still alive!

If it's worth proceeding, my plan is to install the SSD, perform a clean install of High Sierra, and then use the Migration Assistant to transfer data to the new drive.

My concern is about APFS compatibility with the BOOT firmware I seem to be stuck with.

Thanks again!
 
Comment

iluvmacs99

macrumors 6502a
Apr 9, 2019
746
533
I hope it's not poor form to revive an old post, but I've finally been able to upgrade to High Sierra and have a question about the BOOT firmware update and APFS compatibility before I proceed with the hardware upgrade. Thank you for any further insight you can provide!



System Information shows that my SMC version matches what Apple has published here (my computer is a MacBook Pro 13-inch, Mid 2010; MacBookPro7,1), but the BOOT version is different. According to the link above, Apple's most current version is MBP71.0039.B0E (EFI 2.5), while my computer is reporting MBP71.003F.B00.

I have tried to update to the most current version manually (both before and after updating to High Sierra) and got a window indicating this version was not compatible with my system.

Does this mean I won't be compatible with APFS? Should I not upgrade to the SSD? My HDD is at least nine years old and running more slowly with each OS update I have performed - I feel like I'm lucky it's still alive!

If it's worth proceeding, my plan is to install the SSD, perform a clean install of High Sierra, and then use the Migration Assistant to transfer data to the new drive.

My concern is about APFS compatibility with the BOOT firmware I seem to be stuck with.

Thanks again!

Your boot EFI firmware should be - 68.0.0.0.0 for Macbook Pro 7.1. Anything that start with MBP.x is too old for APFS.
To upgrade properly, you need to download the latest High Sierra COMBO update and use an original Apple supplied hard drive or a compatible hard drive to do the clean install and after all updates are performed, your EFI bootrom should be 68.0.0.0.0. Hope this helps.
 
Comment

photochthon

macrumors newbie
Original poster
Feb 13, 2020
9
1
Thank you! I did not know to use the COMBO update. Is it necessary to do this as a clean install? I tried updating today with the COMBO update installer but got this notice: "This volume does not meet the requirements for this update." I have been unable to ascertain what the requirements are. If I install the COMBO as a clean install can I expect a different result?
 
Comment

chrfr

macrumors G4
Jul 11, 2009
10,912
4,501
Your boot EFI firmware should be - 68.0.0.0.0 for Macbook Pro 7.1. Anything that start with MBP.x is too old for APFS.
To upgrade properly, you need to download the latest High Sierra COMBO update and use an original Apple supplied hard drive or a compatible hard drive to do the clean install and after all updates are performed, your EFI bootrom should be 68.0.0.0.0. Hope this helps.
The 2010 doesn't require having an original Apple disk to update firmware.
[automerge]1588079353[/automerge]
Thank you! I did not know to use the COMBO update. Is it necessary to do this as a clean install? I tried updating today with the COMBO update installer but got this notice: "This volume does not meet the requirements for this update." I have been unable to ascertain what the requirements are. If I install the COMBO as a clean install can I expect a different result?
Have you installed the latest security update for High Sierra? If you have, that's a newer version of High Sierra than the 10.13.6 combo update so the combo update won't install at that point. Your computer is on the correct firmware version for a base 10.13.6 install. One of the later security updates would have moved it to the aforementioned 68.0.0.0. So, if you have not installed the latest security update, just install that and it'll update the firmware to the most recent version available.
 
Last edited:
Comment

iluvmacs99

macrumors 6502a
Apr 9, 2019
746
533
Thank you! I did not know to use the COMBO update. Is it necessary to do this as a clean install? I tried updating today with the COMBO update installer but got this notice: "This volume does not meet the requirements for this update." I have been unable to ascertain what the requirements are. If I install the COMBO as a clean install can I expect a different result?

Do you have the original hard drive that came with your Macbook Pro? If yes, then do it with a clean install using the COMBO update on the hard drive by formatting it with the installer. Make sure you are booting off from this COMBO installer via a USB thumbdrive and formatting your install volume with a GUID partition. When you do that, the EFI partition will be automatically created. And this is what you are missing, which the original hard drive would have had if you have not had done firmware updates on a consistent basis. The COMBO update addresses what you missed.

[automerge]1588097128[/automerge]
The 2010 doesn't require having an original Apple disk to update firmware.
[automerge]1588079353[/automerge]

The poster got "This volume does not meet the requirements for this update." That is the reason, because the original hard drive would had been formatted with a GUID partition and would already have an EFI partition created before hand.
 
Last edited:
Comment

chrfr

macrumors G4
Jul 11, 2009
10,912
4,501
The poster got "This volume does not meet the requirements for this update." That is the reason, because the original hard drive would had been formatted with a GUID partition and would already have an EFI partition created before hand.
That's not necessarily the case. The combo updater will report this message if there's been a security update installed.
Also, the computer is already at the firmware version installed by 10.13.6. To get to EFI version 68.0.0.0.0, the most recent security update would need to be installed.
 
Comment

iluvmacs99

macrumors 6502a
Apr 9, 2019
746
533
That's not necessarily the case. The combo updater will report this message if there's been a security update installed.
Also, the computer is already at the firmware version installed by 10.13.6. To get to EFI version 68.0.0.0.0, the most recent security update would need to be installed.

That had been my experience while we were refurbishing Macbook Pros when I was working in the non-profit recycling facility where they had issues updating the EFI bootrom even if there's been a security update installed. Not all the time, but occasionally. The only exception was that we used an original Apple hard drive and the EFI bootrom got installed properly all the time and every time no exceptions. It is strange, but what was the solution we came up with with some of these problems. And the fact that I had proved it myself. I updated first my Macbook Air 13" with a non-Apple SSD and the EFI bootrom did not get updated. And yet, when I updated the same Macbook Air 13" onto the tiny 128Gb SSD with the same combo update, it worked! Please explain to me why is that? Same machine, same ram, same Combo update but different drives.
 
Comment

chrfr

macrumors G4
Jul 11, 2009
10,912
4,501
That had been my experience while we were refurbishing Macbook Pros when I was working in the non-profit recycling facility where they had issues updating the EFI bootrom even if there's been a security update installed. Not all the time, but occasionally. The only exception was that we used an original Apple hard drive and the EFI bootrom got installed properly all the time and every time no exceptions. It is strange, but what was the solution we came up with with some of these problems. And the fact that I had proved it myself. I updated first my Macbook Air 13" with a non-Apple SSD and the EFI bootrom did not get updated. And yet, when I updated the same Macbook Air 13" onto the tiny 128Gb SSD with the same combo update, it worked! Please explain to me why is that? Same machine, same ram, same Combo update but different drives.
Yes, newer computers like the MacBook Air, depending on model year, usually need the stock SSD to update firmware. The 2010 is not one of those models- any drive will work. The requirement for the stock SSD is only an issue on models which use the blade style SSDs, not the standard SATA drives that older Macs use.
 
Comment

iluvmacs99

macrumors 6502a
Apr 9, 2019
746
533
Yes, newer computers like the MacBook Air, depending on model year, usually need the stock SSD to update firmware. The 2010 is not one of those models- any drive will work. The requirement for the stock SSD is only an issue on models which use the blade style SSDs, not the standard SATA drives that older Macs use.

Do you have an idea if the Macbook Pro 2015 is not one those models that any drive will work?
 
Comment

chrfr

macrumors G4
Jul 11, 2009
10,912
4,501
Do you have an idea if the Macbook Pro 2015 is not one those models that any drive will work?
I think pretty much anything newer than about 2013 may have the behavior. In particular with the 2013 Mac Pro, it looks like the update included in 10.15.4 and the 2020-002 security updates may actually install regardless of the drive that's installed.
 
  • Like
Reactions: iluvmacs99
Comment

iluvmacs99

macrumors 6502a
Apr 9, 2019
746
533
I think pretty much anything newer than about 2013 may have the behavior. In particular with the 2013 Mac Pro, it looks like the update included in 10.15.4 and the 2020-002 security updates may actually install regardless of the drive that's installed.
Thank you!
 
Comment

photochthon

macrumors newbie
Original poster
Feb 13, 2020
9
1
ave you installed the latest security update for High Sierra? If you have, that's a newer version of High Sierra than the 10.13.6 combo update so the combo update won't install at that point. Your computer is on the correct firmware version for a base 10.13.6 install. One of the later security updates would have moved it to the aforementioned 68.0.0.0. So, if you have not installed the latest security update, just install that and it'll update the firmware to the most recent version available.
Do you have the original hard drive that came with your Macbook Pro?

Thanks to you both, @iluvmacs99 and @chrfr ! I have installed the 2020-002 Security Update (March 24, 2020) and the system now reports Boot ROM Version: 68.0.0.0.0. I had previously updated to High Sierra using the non-COMBO installer 13.6.02, which apparently had updated the SMC Version to 1.62f7 but not the Boot ROM.

I am happy to report I did not need to perform a clean install for this outcome. I am still using the original HDD (which came with the machine when I bought it refurbished from Apple in 2011).

I can hardly tell you how happy I am to have jumped that hurdle! Now I can proceed with SSD and RAM upgrade I began trying to perform sometime in the middle of last year. Thanks again, wish me luck!
 
  • Like
Reactions: iluvmacs99
Comment

iluvmacs99

macrumors 6502a
Apr 9, 2019
746
533
Thanks to you both, @iluvmacs99 and @chrfr ! I have installed the 2020-002 Security Update (March 24, 2020) and the system now reports Boot ROM Version: 68.0.0.0.0. I had previously updated to High Sierra using the non-COMBO installer 13.6.02, which apparently had updated the SMC Version to 1.62f7 but not the Boot ROM.

I am happy to report I did not need to perform a clean install for this outcome. I am still using the original HDD (which came with the machine when I bought it refurbished from Apple in 2011).

I can hardly tell you how happy I am to have jumped that hurdle! Now I can proceed with SSD and RAM upgrade I began trying to perform sometime in the middle of last year. Thanks again, wish me luck!
Thanks to you @photochthon & @chrfr, I also learned something new, which will re-define how I approach this issue moving forward! Good luck on your upgrade!
 
  • Like
Reactions: photochthon
Comment

AdLibbing

macrumors newbie
May 23, 2020
7
0
Thank you @photochthon for your initial post and thank you @iluvmacs99 and @chrfr for all your answers. I thought I'd struck gold when I found this thread !!
My situation is exactly the same.... MBP7,1 running El Capitan, wanting to upgrade with the Corsair 16gb ram and Crucial MX5000 1TB ssd I've purchased (making sure all the specs are correct!)
My question is... do I have to stay with High Sierra (with the firmware update) for the new hardware to function? Can I go back to a previous osX and retain the updated firmware version?

Thank you all for kindly revisiting this thread and shedding some light for me.

P.S. @photochthon How did your final upgrade go? Is your MBP breaking all the speed limits now? lol. I trust everything went well.
 
Last edited:
Comment

photochthon

macrumors newbie
Original poster
Feb 13, 2020
9
1
Hello, @AdLibbing !

This thread has surely been a pot of gold for me in my own process, glad it has also benefited you!

I have no idea whether or not you will retain the firmware update if you go back to a previous os. I assume you have a specific reason for rolling back to an older os, as it seems like it would otherwise make the most sense to stick with the most recent one available.

As for my own upgrade, I have been stalled out again, this time purely in terms of hardware. I opened my laptop and replaced the HD cable, but found the kit I bought for the SSD upgrade was lacking the screwdriver necessary for removing the old HD. I have now acquired that screwdriver, but have been holding out for the right moment to engage this final disruption. Sadly, with all the software updates and the old drive, my machine has slowed down with each update. I am fairly confident that once I install the SSD that will turn around, and I am really looking forward to that outcome!

Best of luck! I'm sure one of the others will have an answer for your question.
 
Last edited:
Comment
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.