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

[DekuBleep]

@agregson
Mine is an i5 iMac.

I first contacted Apple in March 2020. No feedback. Upgrading to macOS Big Sur last month I noticed recovery not working any more. I was at the genius bar then. The guys there failed to upgrade EFI firmware and also failed to repair recovery. The Apple way to fix it, that's what they told me, is to replace the logic board. But I would have to pay for it, about 640 euros. They also talked to Apple Cupertino, nothing more they can do. So in my case it's pay or live with it. I am really very frustrated.

well the only issue it causes is that you don’t have a recovery partition. Everything else about your iMac still works the same. That’s why I’m just going to live with it. I have a USB thumb drive that I use for recovery

 

[rgmenke]

@rgmenke
Thanks for your reply. May I ask one more question: Is the SSD still connected to your SATA port? Or did you remove the drive after you suceeded in upgrading the EFI firmware?
Thanks.

I kept the SATA SSD connected. I'm not using it.

 

[MilaM]

Push Apple. Push to escalate the issue.

Thanks for this detailed report and glad that your perseverance pushed Apple to do something.

Could you maybe clarify the following questions:

• Was Mac was still covered by some kind of guaranetee like Apple Care or something similar?
• What country are you from?
• Through which channel did you contact Apple Support?

I'm still mad that Apple is still trying to deny there is a problem with a big batch of 17,1 iMacs. Not being able to lauch Internet Recovery is not a nuisance anymore. It's a serious defect in my opinion. We also don't know what the future wil bring. So far all systems seem to boot fine into Big Sur. But I would not be so sure if that will be true in the future.

Would appreciate it if you could help me with my questions.

Thanks again for posting here.

 

[MilaM]

Installing and booting from an external USB HDD/SSD does not lead to a succesfull FW upgrade. Clean installing all macOS releases from High Sierra to Big Sur (11.4) to the internal SSD also did not work. I tested this myself recently.

So far the only known solution seems to be to attach a hard drive or ssd using the internal SATA connector. That of course is a lot of work and you need special tools, so it' not very practical.

I was now wondering if using a Thunderbolt 2 to SATA adapter might do the trick. Has anyone tried that?

 

[zorinlynx]

I'm still mad that Apple is still trying to deny there is a problem with a big batch of 17,1 iMacs.

Yeah, I want Apple to at least admit the problem. My machine runs great with the old firmware, and I'm sure Apple had a good reason to hold back the updates (if even 1% of machines get bricked by the update, that's a LOT of support calls!) but at least ADMIT IT and tell us why the updates are held back.

 

[rgmenke]

Yeah, I want Apple to at least admit the problem. My machine runs great with the old firmware, and I'm sure Apple had a good reason to hold back the updates (if even 1% of machines get bricked by the update, that's a LOT of support calls!) but at least ADMIT IT and tell us why the updates are held back.

Whatever the reason, they seemed to have gotten past it with the newer firmware. My machine is running great.

Apple's response has been very disappointing, which is why some of us made the effort to resolve it ourselves. I can honestly say that I have spent more time and effort on resolving this issue than I care to count.

 

[bear_in_mind]

My 2015 i7 5k first developed this issue in November 19. I became aware when the OS reported integrity check fails. Many calls to Apple and many, many hours spent on this and numerous escalations, traces, dumps and so on later and eventually someone was very candid with me. The OS update and associated EFI firmware update had failed. The flash chip was damaged and a new logic board was needed. They did agree to do this and it was collected, repaired and returned.

All flawless and worked just fine. Until the next update to 11.0. Firmware issue again - OS upgraded, EFI did not. Many more calls to Apple and same outcome. Update had damaged the flash chip. Admitted it was not my issue and agreed to logic board repair again. Machine collected. After around 10 days I was called to advise me a replacement machine would be advised. I queried why and what was happening a no they were evasive. Eventually I was advised the replacement would be current model with same or closest processor speed to what I had and same spec - 500GB and 32GB. A new machine arrived and I could even add AppleCare to it.

This issue has only happened to the 2015 model. I also have a late 2017 model and it seems fine. Any reports I found at the time online and since have suggested this is an issue with the 2015 5k and seems to affect the i7 more than others.

I was happy enough to get a replacement board then machine. I am less enthused that it happened as a result of an OS update and that it could so seriously damage the flash chip. It also made me think just how unrepairable the iMac is and how totally I have surrendered any sense of ownership or capability to repair my own computer despite paying a large fee for the privilege.

It does not seem to affect everyone. YMMV. Push Apple. Push to escalate the issue. Stay calm but remain relentless. This is a model defect in the 2015 and, IMO, a design defect in the whole iMac concept. I suspect the issue of throwaway kit will become even more pronounced with the move to M series SoC and a continued focus on minimisiation over any form of user upgrade or repair.

Thank you for so well documenting your experience! I have a late-2015 5K (Model A1419) that's also stuck on the firmware.

I went to Terminal shell to run an integrity check on my EFI and received this message: "Matching allowlist not found in EFIAllowListShipping. Searching in EFIAllowListAll. Primary allowlist version match not found for version IM171.88Z.F000.B00.1906171551 (Boot ROM Version: 170.0.0.0.0)."

Grrrr...

I see that OS Big Sur v.11.5 is available this morning, so I'm going to download and install it to see if it might address the issue. UPDATE: It did *not* fix the issue.

I want to applaud your grit and perseverance. Calm, but relentless is a good mindset in dealing with a bureaucracy like Apple.

I also had a somewhat similar experience w/iPhone 6 Plus screen issues and had to push Apple repeatedly and firmly to address *their hardware* issue. They wouldn't even acknowledge there was an issue until I did my due diligence online and discovered it was a widespread issue, but they apparently either kept the info from support staff, or told them to deny the issue existed. I ultimately received a new replacement (iPhone 7 Plus) after weeks of advocacy and haggling.

 

[rgmenke]

Thank you for so well documenting your experience! I have a late-2015 5K (Model A1419) that's also stuck on the firmware.

I went to Terminal shell to run an integrity check on my EFI and received this message: "Matching allowlist not found in EFIAllowListShipping. Searching in EFIAllowListAll. Primary allowlist version match not found for version IM171.88Z.F000.B00.1906171551 (Boot ROM Version: 170.0.0.0.0)."

Grrrr...

I see that OS Big Sur v.11.5 is available this morning, so I'm going to download and install it to see if it might address the issue. UPDATE: It did *not* fix the issue.

I want to applaud your grit and perseverance. Calm, but relentless is a good mindset in dealing with a bureaucracy like Apple.

I also had a somewhat similar experience w/iPhone 6 Plus screen issues and had to push Apple repeatedly and firmly to address *their hardware* issue. They wouldn't even acknowledge there was an issue until I did my due diligence online and discovered it was a widespread issue, but they apparently either kept the info from support staff, or told them to deny the issue existed. I ultimately received a new replacement (iPhone 7 Plus) after weeks of advocacy and haggling.

Apple has not acknowledged this or they would have offered a fix or replacement program. They have pulled the EFI upgrade for this model and config. Installing the SATA drive allows the upgrade to happen. I am running the Monterey beta and my machine firmware continues to update and now sits at 429.140.8.0.0. Good luck.

 

[wrw2570]

I did the same as Bear_in_mind. I pushed took to twitter, did multiple runs using apple engineer diagnostics program uploaded to apple. ~Basically after 2 months Apple arranged to have the machine in store they couldn't resolve the issue and then replacement machine 2 months ago.
you have to stick to your guns so to speak. the EFI is part of the security system (apple advertises as "safest") I used their own marketing quotes to the European head office and direct to the engineering team in Cupertino. they don't need to acknowledge there is an issue and wont, as it will lead to class actions. but read between the lines why replace users machines when the user persists and if its not a design/parts issue?

 

[rgmenke]

I ended up with engineering on two separate pushes to get a fix and asked them to fix the issue. Both times ended with them stonewalling with no admission and no solution. After the Internet recovery was broken I was sure they would fix it. Nope.

I’m glad that you got through to them and would agree, it takes serious effort.

 

[agregson]

Thank you for so well documenting your experience! I have a late-2015 5K (Model A1419) that's also stuck on the firmware.

I went to Terminal shell to run an integrity check on my EFI and received this message: "Matching allowlist not found in EFIAllowListShipping. Searching in EFIAllowListAll. Primary allowlist version match not found for version IM171.88Z.F000.B00.1906171551 (Boot ROM Version: 170.0.0.0.0)."

Grrrr...

I see that OS Big Sur v.11.5 is available this morning, so I'm going to download and install it to see if it might address the issue. UPDATE: It did *not* fix the issue.

I want to applaud your grit and perseverance. Calm, but relentless is a good mindset in dealing with a bureaucracy like Apple.

I also had a somewhat similar experience w/iPhone 6 Plus screen issues and had to push Apple repeatedly and firmly to address *their hardware* issue. They wouldn't even acknowledge there was an issue until I did my due diligence online and discovered it was a widespread issue, but they apparently either kept the info from support staff, or told them to deny the issue existed. I ultimately received a new replacement (iPhone 7 Plus) after weeks of advocacy and haggling.

The 170.0 boot rom on 2015 iMac 5k seemed to be a common issue. There also appears to be no fix other than a new logic board.
For me it did not present any issues other than a weekly integrity check failure. That can lead to the system integrity protection being disabled. Besides, it annoyed me that it was not right.

I had a long battle with Apple and all I can say is persist. The bottom line is they have issued an OS update that included an EFI update and it has failed and damaged the flash chip. Sadly we cannot service iMac - at least on a PC board I could possibly boot, it tended to have multi BIOS/EFI and I could even change the EFI/BIOS chip with some soldering. Alas not so on modern Macs. The price we pay for ceding control of our hardware and software to vendors in return for convenience.

It took me many hours and persistence. You know they will run out of options on diagnostics as there is a hardware issue. Just keep carrying out all the tests and checks. Ask to be elevated to a senior tech. persist. Ask for diagnostic logs and ask for call backs. Book call backs for a specific day and time and ask for reference numbers, names and email addresses. Stay calm and just keep pushing the issue.

When they exhaust all options ask what do they suggest? I asked it simply - was this something I did or something Apple did on an update? No grey options and the call is recorded. They hesitated and I pushed it - did I do something or did Apple do something or is this a fundamental flaw in the hardware or OS?

Eventually we had to work through elimination.

"did I do something wrong?". No.
"Did Apple install an update that has led to this issue?". Not conclusive.
"It was not an issue before update and was an issue after update". It appears so.
"Numerous reports on forums and Apple support of same issue on same hardware". Not seen those posts.
"Does apple not read or respond to support logs and reports even on their own". We do.
"Has this issue been reported or are there any reports in your database of similar". Yes I see several.
"How were they resolved". Return for repair eventually.
"When is mine going for repair?". I will see what I can arrange. It is out of warranty and AppleCare.
"Did I cause this issue"? No.
"So when is it going for repair"? Let me check with "senior"
"We can arrange a repair. Can you bring to store"?
"No. It is miles, huge heavy box and a major issue. Plus I did not cause this issue"
"I will arrange collect and repair at approved"

It took ages but the machine went fo repair. It has been fine since with numerous updates. I sold it to a friend a few weeks after repair and he is delighted and it continues to work fine.

I was concerned about this. It appeared to affect the 2015 5k i7 most. I suspect a design flaw and maybe a revision in logic board.

I would persist and not accept this. It is not a cheap computer from local retailer but a premium device from a premium supplied and at a premium price.

 

[agregson]

I did the same as Bear_in_mind. I pushed took to twitter, did multiple runs using apple engineer diagnostics program uploaded to apple. ~Basically after 2 months Apple arranged to have the machine in store they couldn't resolve the issue and then replacement machine 2 months ago.
you have to stick to your guns so to speak. the EFI is part of the security system (apple advertises as "safest") I used their own marketing quotes to the European head office and direct to the engineering team in Cupertino. they don't need to acknowledge there is an issue and wont, as it will lead to class actions. but read between the lines why replace users machines when the user persists and if its not a design/parts issue?

I think it is madness how this issue has been dealt with. Why persist and give users such a negative feeling? Clearly the issue is known. Simply hold up hands, say there is an issue, repair it and move on. It is not as if they are a small tech company pushed for money. What would a few hundred or even a few thousand logic board repairs cost them?

Persist. I would persist on principle alone. We choose Apple for premium hardware and support and accept we pay for this price and also cede access to hardware and software in pursuit of the ideal and model Apple sell. I think it is reasonable to except them to live up to it.

I should say I am far from an Apple basher. I have numerous Apple devices and have just ordered a new iPad Pro and iMac 24, changed to latest Apple TV 4K, change to new iPhone Pro max every year and so on. The kit is superb and the whole experience is superb. There are minor issues but way less than on rival platforms. All I expect is Apple to maintain the bargain and show me the same loyalty I show them.

My absolute pet hate with Apple is they do not admit to problems and try to convince users it is their problem before some magical fix appears. I just wish they would be honest and open. Problems happen. Consider them as opportunities to demonstrate the level of user service and commitment. Be honest, open. If they say to me there is an issue and there is no known fix at the moment then that is fine. I move on and wait until a fix comes along. Numerous times they waste my time with maddening diagnostics.

I just went through this with an M1 mini and the sleep/wake issue on displays. I prepared all my notes in advance. First step was going to be "reinstall the OS" (it was 1 day old and no apps installed!), then we were talking a new Apple ID (seriously). Then he said I could just return it for a refund if I preferred. Clearly they know of the issue and yet again did not come clean.

 

[Philuk20]

I used a SSD connected to the SATA port. I did remove the M2 SSD but others have reported you don't have to.
Once the machine EFI was updated it continues to update with OS updates. The last one was with 11.4, which upgraded the EFI to 429.120.4.0.0.

Like rgmenke, I too removed the M2 SSD. Was able to push the firmware forward using MacOS running on a SSD connected to the SATA port. Formatted the M2 (in a 2014 Mac mini) and then reinstalled it in the iMac. Once back in the iMac I was able to install MacOS onto the M2 and the firmware has updated fine since.

 

[Mikey86uk]

Anyone in the UK have this issue and get anywhere?

my i7 2015 27" iMac is also stuck on 170.0

 

[rgmenke]

By now I think there is too much evidence for Apple to ignore. Having said that, the machine is getting old so either get Apple to fix it or do it yourself (documented in this thread). If you decide to take it on, I would replace the SSD with something faster like a wd black. for me th added speed of the drive and the current firmware (internet recovery works) was worth it. I can wait until apple unleashes the M2 imac.

 

[zorinlynx]

By now I think there is too much evidence for Apple to ignore. Having said that, the machine is getting old so either get Apple to fix it or do it yourself (documented in this thread). If you decide to take it on, I would replace the SSD with something faster like a wd black. for me th added speed of the drive and the current firmware (internet recovery works) was worth it. I can wait until apple unleashes the M2 imac.

Apple might just be stuck between a rock and a hard place here. The issue may be that the current firmware has a bug that doesn't allow it to update from the PCIe SSD. That would explain why when you do an update by replacing the PCIe SSD with a SATA drive, then put the PCIe SSD back, updates work again, because the bug that prevents updates is in the currently installed version.

Since the lack of an EFI firmware update doesn't break the system, Apple's best course of action is to just let it stay on this old version.

 

[bear_in_mind]

Like rgmenke, I too removed the M2 SSD. Was able to push the firmware forward using MacOS running on a SSD connected to the SATA port. Formatted the M2 (in a 2014 Mac mini) and then reinstalled it in the iMac. Once back in the iMac I was able to install MacOS onto the M2 and the firmware has updated fine since.

Thanks! I've been torn over how to proceed. I would really like to swap the 500GB Blade SSD with a 2TB model, and was willing to endure the teardown expense and headaches, but I don't have a 2nd Mac system that I could use to format the new 2TB Blade SSD to address the firmware issues.

While I could likely prevail via the Apple Engineering support route, I know it's:
1) Going to be a long haul
2) I'll be without a system for an undetermined period for 'repairs' (or AAPL swaps it w/ another system)
3) I'll still be stuck with 500GB of internal storage.

What a pain in the rear!

 

[bear_in_mind]

The 170.0 boot rom on 2015 iMac 5k seemed to be a common issue. There also appears to be no fix other than a new logic board.
For me it did not present any issues other than a weekly integrity check failure. That can lead to the system integrity protection being disabled. Besides, it annoyed me that it was not right.

I had a long battle with Apple and all I can say is persist. The bottom line is they have issued an OS update that included an EFI update and it has failed and damaged the flash chip. Sadly we cannot service iMac - at least on a PC board I could possibly boot, it tended to have multi BIOS/EFI and I could even change the EFI/BIOS chip with some soldering. Alas not so on modern Macs. The price we pay for ceding control of our hardware and software to vendors in return for convenience.

It took me many hours and persistence. You know they will run out of options on diagnostics as there is a hardware issue. Just keep carrying out all the tests and checks. Ask to be elevated to a senior tech. persist. Ask for diagnostic logs and ask for call backs. Book call backs for a specific day and time and ask for reference numbers, names and email addresses. Stay calm and just keep pushing the issue.

When they exhaust all options ask what do they suggest? I asked it simply - was this something I did or something Apple did on an update? No grey options and the call is recorded. They hesitated and I pushed it - did I do something or did Apple do something or is this a fundamental flaw in the hardware or OS?

Eventually we had to work through elimination.

"did I do something wrong?". No.
"Did Apple install an update that has led to this issue?". Not conclusive.
"It was not an issue before update and was an issue after update". It appears so.
"Numerous reports on forums and Apple support of same issue on same hardware". Not seen those posts.
"Does apple not read or respond to support logs and reports even on their own". We do.
"Has this issue been reported or are there any reports in your database of similar". Yes I see several.
"How were they resolved". Return for repair eventually.
"When is mine going for repair?". I will see what I can arrange. It is out of warranty and AppleCare.
"Did I cause this issue"? No.
"So when is it going for repair"? Let me check with "senior"
"We can arrange a repair. Can you bring to store"?
"No. It is miles, huge heavy box and a major issue. Plus I did not cause this issue"
"I will arrange collect and repair at approved"

It took ages but the machine went fo repair. It has been fine since with numerous updates. I sold it to a friend a few weeks after repair and he is delighted and it continues to work fine.

I was concerned about this. It appeared to affect the 2015 5k i7 most. I suspect a design flaw and maybe a revision in logic board.

I would persist and not accept this. It is not a cheap computer from local retailer but a premium device from a premium supplied and at a premium price.

This exactly! I'm willing to pay the "Apple Tax" in exchange for higher-quality gear and services. When the gear fails to work as advertised, they should own it and make the proper amends to the customer(s). It's not like they don't have the resources to make things right.

 

[bear_in_mind]

Hmm, this is very interesting. Just read through this tread quick. I've seen this problem being reported in other threads and was afraid I'd get the same problem with my 17.1 iMac. But, since mine was shipped with only spinning rust it never got stuck on 170.xxx.... at all. Seems to confirm that the issue is blade related.

Side note, have anyone actually installed an OWC Aura Pro x2 in an 17.1 and got it working properly?
OWC says it's not compatible with 17.1 iMac and I guess this BOOT-ROM issue is part of that. I got a super good deal on one and bought it without thinking much. But since I'm well past 170.xxx and now on 428.xxx it shouldn't be a problem right? Got the WD Black SN750 and a Sintech adapter that I planned on using also, so might just give the OWC a try and see if it works.

Did you proceed with the OWC Aura Pro x2? And if so, did it work out for you?

 

[zorinlynx]

This exactly! I'm willing to pay the "Apple Tax" in exchange for higher-quality gear and services. When the gear fails to work as advertised, they should own it and make the proper amends to the customer(s). It's not like they don't have the resources to make things right.

I'm curious, what problems are you having because of the old firmware?

I'm running Monterey on my iMac 17,1 with the old firmware (170) and have absolutely no issues at all. I'm wondering why some other people are so desperate for this upgrade.

 

[bear_in_mind]

I'm curious, what problems are you having because of the old firmware?

I'm running Monterey on my iMac 17,1 with the old firmware (170) and have absolutely no issues at all. I'm wondering why some other people are so desperate for this upgrade.

Given the premium I paid for Apple products, and the purported premium Apple places on security and privacy, leaving this system vulnerability unaddressed for owners of the 17.1 iMac is no bueno.

It's like saying, "Well, a zero-day EFI exploit hasn't hit *my* system yet, so I'll worry about with it when it does." Which is one-day too late.

 

[zorinlynx]

Given the premium I paid for Apple products, and the purported premium Apple places on security and privacy, leaving this system vulnerability unaddressed for owners of the 17.1 iMac is no bueno.

It's like saying, "Well, a zero-day EFI exploit hasn't hit *my* system yet, so I'll worry about with it when it does." Which is one-day too late.

EFI bugs can be mitigated by the operating system, as it has full control of the hardware. There's only a very narrow attack surface for them in the boot process which would require physical access anyway.

It's really not a big deal, and you don't have anything to worry about. And I say this as someone affected by this as well.

 

[holty]

I have one of these affected late 2015 27 inch iMacs. I have sat on 10.14.6 for ages awaiting for an App named Pure mMusic to be updated but have now decided to move forward without it. Has this affected iMac been successfully updated to OS 12. without issue. Thanks in anticipation

 

[MilaM]

I have one iMac that has the stuck firmware problem. It's currently running the latest Big Sur release and I will upgrade it to Monterrey later today.

Will report back how it went.

 

[rgmenke]

It updates fine. I have been on the betas and then the final release including the latest 12.2. The one caveat is that I fixed the firmware issue so I’ve been operating on current firmware for a while. A big issue with the old firmware was that Internet Recovery quit working correctly.