The MacOS fails to start after a fresh installation.
The MacOS fails to start after a fresh installation.
Hello to fellow MacOS specialists, I’m currently working on fixing a friend’s 13-inch Mid 2012 MacBook Pro (Model 1278) after the Apple Store quoted over AUD$400 for swapping the internal HDD with a 250GB SSD. Following that, I replaced the extremely slow 5400 RPM HDD and swapped it out for a 250GB Samsung 860 EVO drive. After setting up Internet Recovery, I formatted the SSD as HFS+ for OS X Mavericks and began the installation process. It took roughly six hours before the OS finished installing. Once done, I restarted the system and encountered a problem: a flashing grey cross appeared on the screen. Initially assuming it was just an installation failure, I reformatted the drive and tried again, but it still didn’t work. After another restart, another flashing grey cross showed up. This time I turned on verbose startup and saved the error images (files attached). I’ve also attempted to install MacOS Sierra, High Sierra, and Mojave, but each attempt ended in similar issues. Anyone have any advice or tips to resolve this? I’m also looking for help with the pictures you mentioned. Thanks, Kale04
Create a bootable USB for the newest macOS release that matches your MacBook’s specs, using the official guide here: https://support.apple.com/en-us/HT201372. After preparing it, format the entire drive—including the recovery partition—and install macOS directly from there.
Updated: I tried a fresh approach by making another bootable USB for MacOS Mojave and reformatted the drive to HFS+ again. The installer blocked direct APFS installation due to required firmware updates, and when I attempted to reinstall, a new error appeared. Someone, could you help with this issue? Thanks ahead, Kale04
Just trying to figure things out. I installed Windows 10 1809 onto a Bootcamp drive built from the same MacBook Pro. It seemed to work at first, but whenever the Mac restarts into Windows, I get a new error message. I've attached a screenshot of the issue. It might be a hardware or firmware problem, not just a MacOS one. Anyone have any advice? Thanks, Kale04
I didn't fully understand the subject, maybe the period at the end was confusing you.