![]() It’s clear from the number of reports that this is affecting a number of machines. They directly programmed EFI with special tool, and it works now. I went to official local service and they said that “it’s just too old…” So I get to unofficial service but with normal guys, and they tested all the hardware and it works great, but didn’t wake up with this motherboard. The Extensible Firmware Interface (EFI) was designed by Intel to replace the Open Firmware used on PowerPC Macs. Some of those reporting the issue are on a beta, while others are on the official release.Ī number of posts point to corruption of the EFI firmware as the likely cause. Everything points to be a BIOS-EFI firmware corruption by the Catalina installer. No keys are recognized by the device and 5 minutes after turning it on the flashing question mark folder. It happened to my 2014 MacBook Air and I have two other friends with MacBook Pro 2015 that have the same issue. ![]() I can’t imagine that, after all, the iMac has been running smoothly since 2014. After the Genius, like me, had done all the shortcuts, he said it might be the logic board. This is a serious problem that Apple need to address. ![]() No combination of boot up keystrokes work. I am now left with a laptop that flashes the “?folder” icon after a couple of minutes. I followed the update instructions from “Settings - software update” as one would normally do. My computer was perfectly fine until I attempted to install Catalina. He said it was a hardware problem not caused by the update. I had a call with Apple support last night. It seems the update must have corrupted the firmware on the logic board since it no longer recognizes key combos. ![]() All I get is the “folder?” logo or nothing at all if I try “option” or “command R” on boot up. There are multiple threads on Apple’s support forums (below), with most reports appearing similar in nature. There are forum reports of the update to macOS Catalina resulting in some Macs becoming non-responsive, with some indication that an update to the EFI firmware may be responsible… ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |