On the thread, users have traded horror stories of their MacBook Pros' graphics breakdowns, swapped tales of trying to get Apple to repair the notebooks - sometimes with success, many times without - and raked the Cupertino, Calif. By any measurement, but especially for an Apple support thread, that's massive with a capital "M." That thread has grown to include more than 7,800 messages, and has been viewed an amazing 1.1 million times. Since then, the screen has gone awry on numerous occasions - each time necessitating a hard reset." "The computer was working fine, when all of a sudden the screen completely blue. 1, 2013, in the thread's opening message. Note: You will probably have to do this all again when doing any system updates and from my experience even security updates."As of two days ago, the problem has become substantially more severe," wrote abelliveau on Feb. Hope this helps anybody else with the same problem. Important! This is up to you but I would suggest doing a Time Machine backup just to be safe.
Now your mac should be booting normally without any issues, if not then there really is more than a graphics card issue. On the screen that loads choose the following in the menu Utilities -> Terminal. Now reboot into Recovery mode using CMD + R. Now we are more or less repeating the same as Step 1.
Now update the timestamps of the driver cache without the AMD drivers.
Now once done lets delete the kext drivers cache. sudo mv /System/Library/Extensions/AMD*.* /amd-backup-kexts/ Then move all of the drivers with a wildcard naming. So first make a backup directory to copy them into. Now we are going to move all the AMD graphics card drivers, so best to make a copy of them rather than deleting them all. Try using /sbin/mount if you get mount command not found
Once done mount the MacBook Pro hard drive by adding.
Now in the terminal add the following, which will fix any disk permissions before we do anything. On reboot go back into single user mode by holding down the CMD + S keys. When csrutil is disabled we can now move kexts and delete system folders.
On the screen that loads choose a language then on the screen which appears next choose the following options in the menu Utilities -> Terminal - see below. The terminal will now be on the screen.įirst input. So first reboot your Macbook Pro into single user mode by holding down the CMD + S keys. But I had two problems - I had no permissions when trying to disable the csrutil and when trying the same with Recovery Mode - CMD + R I had the blue lines on black screen appearing, but the below sorted it for me. Now there are other solutions that say at first boot into Recovery Single User Mode - CMD + R + S.
The solution is to change your energy settings and make sure the screen saver animation options are always active. NOTE: One known issue to this solution (and maybe others) is that when the screen goes to sleep/black it no longer wakes up, therefore needing a forced reboot. Now there are several solutions on the web but this is the only one that worked for me running macOS High Sierra (10.13.6+) and what was worst for me is that the MacBook Pro was stuck in looping reboot. If you are suffering from the infamous blue lines on the black screen on startup or random reboots then you maybe suffering from an AMD graphics card hardware issue with your later 2011 Macbook Pro laptop.