iMac 17,1 (Retina 5K, 27-inch, Late 2015) EFI firmware update failures

[George Dawes]

Same problem here , wish I'd stayed at Sierra

Really getting bored with the mac , thank god for iOS imo , thats the future

 

[JDW]

My late 2015 5K iMac still has version 170.0.0.0.0 firmware; however, I am still running MacOS High Sierra and have zero desire to update to Catalina, so it makes sense I still have the old firmware. I occasionally boot Catalina from an external 2TB SSD only so I can run the latest FCPX. I like High Sierra because it's rock solid stable and allows me to run my previous 32-bit apps.

With that said, I am wanting to know 2 things:

1. Where are the release notes for all the late 2015 5K iMac firmware updates so I know what is contained in those updates? Only then can I better determine if it's truly safe to install or not, seeing I am still on MacOS High Sierra. Or do any of you know if it's safe to run the latest firmware yet run an older MacOS version like High Sierra?

2. Where is the standalone firmware downloader for the late 2015 5K iMac? I found many firmware updates on this TarDisk web page, but bizarrely, none in that long list include the late 2015 5K iMac!

Thank you.

 

[DimaVR]

I’m on 428 firm ware in late 2015 5K 27 inch with i5

 

[Philuk20]

Yesterday I once again have updated my 170.0.0.0.0 iMac from High Sierra to Catalina 10.15.7 (no change in FW version) and today got a message "Your computer has detected a potential problem - click send to Apple..... (screenshot detail attached) I never got this message when I last tried back in March. Hope it means someone is taking note.

 

[DimaVR]

Yesterday I once again have updated my 170.0.0.0.0 iMac from High Sierra to Catalina 10.15.7 (no change in FW version) and today got a message "Your computer has detected a potential problem - click send to Apple..... (screenshot detail attached) I never got this message when I last tried back in March. Hope it means someone is taking note.

that means you have a problem with your motherboard and it needs to be replaced

 

[zeratul75]

did you guys try to update using silentknight?
I am sure it can detect if firmware is not what it should be and maybe (but I don't know) it can force the update......deserve a try

 

[rgmenke]

I've used it (Silentknight) but it can't do the firmware update. You may be thinking about another of Howard's tools (LockRattler) that has an update button. It seems to be able to trigger other smaller security updates. The firmware updater code is only in the OS installer.

If you read through the installer.log (I'm going on mine) - it recognizes the need to update the firmware, in my case 170 to 428. Then somewhere down the line refuses to do the update. We as a community have been unable to define why and Apple has ignored it.

 

[rickydoo]

I don't recall the details, but I ended up calling the Apple hot line and told them that my firmware wasn't upgrading. They gave me some pointers on how to download an operating system from scratch and get my firmware upto snuff. I actually learned that this was a problem for this model mac from my subscription to MacLife. My mac wouldn't shutdown, it would hang up. Now, everything is fine. I also wnet to the apple bar in Boulder CO, and they didn't know anything. SAD.

 

[rickydoo]

They may have sent me this link: https://support.apple.com/en-bn/HT208691

 

[Philuk20]

Thanks to Legaleye3000 giving me the idea of swapping hard drives I have now updated firmware from 170.0.0.00 to 428.0.0.0.0.
Removed original blade 512GB SSD, installed a Crucial SATA SSD and performed internet recovery 10.11 (fw170) then AppStore upgrade to 10.15 (fw428). For good measure formatted iMac blade SSD in a 2014 MacMini before reinserting into iMac. With the blade back in the iMac did the same internet recovery on it and fw version is 428.0.0.0.0. (Not sure I needed to do the SATA OS install/upgrade but this worked for me.)

 

[rgmenke]

That maybe the final solution but it’s seems a bit extreme. One of the theories is that something remains on the HD preventing the upgrade. I have tried to reformat the drive every way possible to erase it but have had no success. The install routine will not upgrade my firmware. My Apple so drive works fine so I’d like to find a solution that doesn’t require replacing it. Congratulations, but my search for a solution continues.

 

[Philuk20]

That maybe the final solution but it’s seems a bit extreme. On of the theories is that something remains in the HD preventing the upgrade. I have tried to reformat the drive every way possible to erase it but have had no success. The install routine will not upgrade my firmware. My Apple so drive works fine so I’d like to find a solution that doesn’t require replacing it. Congratulations, but my search for a solution continues.

I quite agree! Apple really need to sort this out without users having to open their iMacs. I hope Big Sur finally updates the firmware on these Macs.

 

[BeatCrazy]

delete

 

[cromagnontech]

My iMac 17,1 27" is also stuck at 170.0.0.0.0. In Big Sur, I can no longer access the Recovery Partition via Cmd-R (it only launches Internet Recovery, and the El Capitan era version of Recovery / Disk Utility etc.). I'm wondering is the firmware issue and this are connected?

I'm actively working with Apple techs on the Recovery issue, but wondered if anyone else is having the issue, and, if so, if they are also stuck on the old firmware? ... and if anyone who isn't stuck on the old firmware CAN access the Big Sur version of Recovery OK? Thanks all.

 

[DimaVR]

I do IT work!! Replace SSD with feather nvme turbo SSD drive google it, yes entire iMac comes apart but any apple repair dealer will do it! And it will update firmware stupid SSD that came OeM have issues in these macs

 

[cromagnontech]

I do IT work!! Replace SSD with feather nvme turbo SSD drive google it, yes entire iMac comes apart but any apple repair dealer will do it! And it will update firmware stupid SSD that came OeM have issues in these macs

That's really not something I would want to do. This is for Apple to resolve. Maybe if the Recovery Partition issue is connected to the firmware problem, it will lead them to finally sorting out the firmware problem ...

 

[DimaVR]

That's really not something I would want to do. This is for Apple to resolve. Maybe if the Recovery Partition issue is connected to the firmware problem, it will lead them to finally sorting out the firmware problem ...

You going to be waiting a long time. I issue mine $300 for SSD and $200 labor they installed SSD inside and I moved on with life and Big Sur loved new drive speeds

 

[DimaVR]

That's really not something I would want to do. This is for Apple to resolve. Maybe if the Recovery Partition issue is connected to the firmware problem, it will lead them to finally sorting out the firmware problem ...

Apple isn’t and won’t care they moved onto new iMac and chips good luck 👍 they don’t care

 

[vangeliis]

I have just updated my iMac17,1 from Catalina to Big Sur and unfortunately, the system firmware was not updated.
Disappointing...

 

[cromagnontech]

I have just updated my iMac17,1 from Catalina to Big Sur and unfortunately, the system firmware was not updated.
Disappointing...

Can you confirm whether you can access Recovery mode please, by holding down Cmd-R during reboot? Or whether your machine instead goes into Internet Recovery? Thanks.

 

[cromagnontech]

Apple isn’t and won’t care they moved onto new iMac and chips good luck 👍 they don’t care

Well, let's see. I'm hoping that the Recovery partition issue is connected to the firmware not updating, as this gives them a tangible problem caused by the lack of firmware updates, and therefore, maybe, some impetus to sort it out. Until now, my iMac has functioned fine despite being stuck on the old firmware. Even now, when logged into Big Sur, it's very smooth, with no crashes or kernel panics. The only issue is the inability to access Recovery.

You're more cynical about Apple's motivations than I am - they do, generally, try to do the right thing, I believe.

 

[vangeliis]

Can you confirm whether you can access Recovery mode please, by holding down Cmd-R during reboot? Or whether your machine instead goes into Internet Recovery? Thanks.

Hi,

I can confirm that rebooting my iMac17,1 while holding down cmd-R takes me to Internet Recovery. Rebooting while holding down the option key, I can only see the Macintosh HD.

I see more and more reports that the recovery partition is gone for older macs. Any ideas?

 

[micbarry]

Hi,

I can confirm that rebooting my iMac17,1 while holding down cmd-R takes me to Internet Recovery. Rebooting while holding down the option key, I can only see the Macintosh HD.

I see more and more reports that the recovery partition is gone for older macs. Any ideas?

May I ask - when CMD-R takes you to internet recovery, which version of the MacOS recovery partition does it use? Is it El Capitan?

Also, what happens when you boot using Option-Command-R?

Thank you!

 

[vangeliis]

May I ask - when CMD-R takes you to internet recovery, which version of the MacOS recovery partition does it use? Is it El Capitan?

Also, what happens when you boot using Option-Command-R?

Thank you!

Hi

I have only tried option-cmd-R and it seems that now it downloads the macOS base image from Apple’s servers and yes it gave me the option to reinstall big sur.

 

[rgmenke]

My iMac 17,1 27" is also stuck at 170.0.0.0.0. In Big Sur, I can no longer access the Recovery Partition via Cmd-R (it only launches Internet Recovery, and the El Capitan era version of Recovery / Disk Utility etc.). I'm wondering is the firmware issue and this are connected?

I'm actively working with Apple techs on the Recovery issue, but wondered if anyone else is having the issue, and, if so, if they are also stuck on the old firmware? ... and if anyone who isn't stuck on the old firmware CAN access the Big Sur version of Recovery OK? Thanks all.

Yes, I just noticed the same problem and have the same firmware version. I haven't called yet so can you report what they told you?

I'm actually on the phone with them now but this is way past their paygrade. Last time I was told by a level 2 person that if it was meant to upgrade - it would. Awesome!