I found this according to my problem in this thread:
Boot hangs on grey screen (even when booting from USB drive with fresh OS X install)

My MacBook Pro 15" Early 2011 with AMD Radeon HD 6750M exhibited display corruption and associated system crashes/resets over a period of two weeks before it entirely failed to boot. The boot would progress through the grey screen with the Apple logo and spinner, but just when it seems it should have switched to the login screen the Apple logo and spinner would disappear and hang on a blank grey screen.

Initially I suspected hard-drive corruption and went about trying to remedy that. Unsuccessfully, I tried the following, with each continuing to hang as described above:

Safe boot
Boot into recovery (including Internet Recovery)
Boot from install media on USB drive
Boot from OS X installation on USB drive
Reset SMC

I also ran the Apple Hardware Test many times without it finding any issues.

Verbose safe boot (Cmd+Shift+V) output everything that I'd expect to see but would then hang as described above.

After coming across more posts online at Apple's discussion forums of GPU related problems I revisited this as the cause:

2011 MacBook Pro and Discrete Graphics Card or 2011 MacBook Pro and Discrete Graphics Card

Attempting to boot Ubuntu from a USB flash drive, I could only get as far as GRUB. When trying to boot Ubuntu Desktop or run the graphicstest in GRUB the system would hang.

At this point, running Apple Hardware Test hung right before the end of the standard test, possibly [guessing] when doing a video test.

Based on the advice in the Apple Discussions posts above I did the following:

Boot into Single-User mode
Execute the following commands:

/sbin/fsck -fy /
/sbin/mount -uw /
mkdir /Disabled_System_Library_Extensions
cd /Disabled_System_Library_Extensions
mv /System/Library/Extensions/ATI* .
mv /System/Library/Extensions/AMD* .
touch /System/Library/Extensions

This time the machine booted all the way through. However, graphics are extremely slow, even just transitions when minimizing windows. I will be taking my MBP to Apple to demand a replacement as the large number of reports of others facing similar issues makes it look like a recurrence of a similar GPU-related failure that resulted in them doing a recall.

But when I use the "mv" command the files won't get moved (neither deleted) and it shows me:
Sandbox deny(01) file-write-unlinked…

Any Solution ?


4 Answers 4


Background and explanations

Please read all of this post at least once from start to finish before taking any action.

All MacBook Pros from 2011 have a serious design defect. The thermal management and the generated heat together with the robustness of the discrete AMD graphics chips do not match up very well. Apple knew this and acted like a typical Soapy Smith, only reacting to this after an outrage. This scandal is known as RadeonGate. Only threatened with class-action law suit Apple finally offered a so called "Repair Extension Program".

The Repair Extension program is not available anymore. The only real way to fix this problem is to replace the AMD chip alone. Not the logic board. Not "re-balling", not "reflowing", not "baking". Apple replaced a failed chip with a failing chip. Time and time again. Only replacing the graphics chip is still a costly hardware procedure for such a vintage laptop.

The only known way – that is: with software alone – to get a 2011 MacBook Pro (8,2) with 'only' a failed AMD graphics chip to almost reliably turn on again and boot into macOS and be quite useable with an accelerated GUI is this guide or a variation of it. Most previous tips just removed all AMD-kexts and this results in a horrible user experience with no GUI acceleration at all.

It is necessary to know your exact OS version. The following guide will be simpler for Yosemite but assumes El Capitan or newer. El Capitan, Sierra and High Sierra need SIP (System Integrity Protection) disabled. On previous systems (10.6–10.10) these steps are unnecessary.

Important: This guide assumes further that all kexts are still in their default location /System/Library/Extensions. Having all AMD-kexts there except one is beneficial for 'proper' operation. Previous hacks in this direction might have instructed you to move, or worse: remove all AMD*/ATI* kernel extensions. If that is the case: either move the kexts back into their default location or reinstall a system of your choice. Having most of the AMD kexts in place and then having the X3000-kext loaded with a delay will enable power management of the GPU which will otherwise burn electricity for nothing (and might hasten the final heat death of the chip on top of that). To reiterate: Only the file AMDRadeonX3000.kext really has be absent on boot to enable a successful startup, but all other (needed) AMD drivers should be in their default location and the X3000-kext loaded afterwards/delayed to get back into a realm of almost sensible power and temperature management.

Bypassing the discrete graphics chip

To get some display acceleration back it will be necessary to force the machine to not boot in discrete graphics (dGPU) but directly into integrated graphics (iGPU) and stay in this mode.

Booting into dGPU mode is the default on Macs with two switchable graphics cards. The procedure below will set an NVRAM variable that disables the dGPU and forces the system to only use the integrated Intel graphics even when booting.

The NVRAM variable is undocumented but appears to be universally applicable to all Macs with two switchable graphics cards. That means it should work on iMacs and MacBook Pros. Whether they have AMD or NVIDIA chips. The specifics about the drivers that might be necessary to move only cover AMD in this guide. But the NVRAM variable will bypass the discrete graphics chip in any case.

This will give you back your machine – but you will lose some features: e.g. the ability to drive an external display from the DisplayPort, a bit of 3D performance. Thunderbolt data connections should work.

In case this guide fails or is not wanted anymore: this procedure is pure software configuration and therefore fully reversible at any time with simple NVRAM reset.

The initial procedure:

Part 1: Disable SIP, disable dGPU, move one kernel extension

  1. To start from a clean slate: reset SMC and NVRAM:
    shutdown, unplug everything except power, now hold

    and release all at the same time;

  2. Now power on again and hold

    Cmd+Opt+p+r at the same time until you hear the startup chime two times.

  3. Boot into Single User Recovery by holding


  4. Disable SIP: enter:

    csrutil disable

  5. disable dGPU on boot with setting the following variable:

    nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00

  6. enable verbose boot mode:

    nvram boot-args="-v"

  7. reboot into Single User-mode by holding

    Cmd+s on boot

  8. mount root partition writeable

    /sbin/mount -uw /

  9. make a kext-backup directory

    mkdir -p /System/Library/Extensions-off

  10. only move ONE offending kext out of the way:

    mv /System/Library/Extensions/AMDRadeonX3000.kext /System/Library/Extensions-off/

  11. inform the system to update its kextcache:

    touch /System/Library/Extensions/

  12. reboot normally:

You should now have an iGPU-accelerated display, but the system doesn't know how to power-management the failed AMD-chip. (In this state the GPU is always idling with relatively high power, consuming quite a bit of battery when unplugged and leading to GPU temperatures from 60°C upwards [on average 60-85°C], despite not being otherwise unused.)

Part 2: improve thermal and power management

For improved power management of the disabled GPU you have to either manually load the one crucial kext after boot by:

sudo kextload /System/Library/Extensions-off/AMDRadeonX3000.kext

If you have a temperature sensor application you might want to have it open before issuing the above command and watch the temps drop…

Automate this with the following LoginHook that will get executed after the next reboot:

sudo mkdir -p /Library/LoginHook
sudo nano /Library/LoginHook/LoadX3000.sh

with the following content:

kextload  /System/Library/Extensions-off/AMDRadeonX3000.kext
pmset -a force gpuswitch 0    # undocumented/experimental
exit 0

then make it*1 executable and active:

sudo chmod a+x /Library/LoginHook/LoadX3000.sh  
sudo defaults write com.apple.loginwindow LoginHook /Library/LoginHook/LoadX3000.sh 

*1: The undocumented use of this pmset command seems to improve sleep/wake/shutdown behaviour. If it doesn't, experiment with leaving it out.
See Disclaimer below. The following is just speculation: sleep/wake/shutdown may remain troublesome. The theory here is that "something slowly corrupts" what is saved in the SMC. Therefore, resetting the SMC and re-applying the variable hack seems to alleviate the situation for a time. (Permanent solutions for this welcome!) As short time workarounds you might want to try to avoid "lid-closing sleep", that seems to give more trouble than other methods (Apple-Menu, Keyboard-Shorcut). Apparent hangs on shutdown are usually just very long delays that will shutdown, eventually, cleanly and successfully.
Unscientific sampling suggests that Yosemite is worst for this and El Capitan and Sierra much better behaved in this regard.

Manually or otherwise delayed loading of this crucial kernel extension allows the system to handle power management a bit better. The battery will be less used and the temperatures emanating from the unused GPU will drop to a range significantly below 50°C (on average between 15-50°C).

For proper power management the minimal set of loaded kexts are on boot (versions for 10.12.6, check with kextstat | grep AMD):

com.apple.kext.AMDLegacySupport (1.5.1) 
com.apple.kext.AMD6000Controller (1.5.1)  
com.apple.kext.AMDSupport (1.5.1)
com.apple.kext.AMDLegacyFramebuffer (1.5.1) 

And if the above method of loading succeeded this should appear added to the list:

com.apple.AMDRadeonX3000 (1.5.1) 

A final step is to reboot once again into SingleUserRecovery
Do this with Cmd+r+s
after the commandline becomes active, enter:

 nvram boot-args="-v agc=0"   

and reboot normally.

This will cool down the dGPU a bit further.

It is imperative to issue this command from SingleUserRecovery since the system with SIP enabled will block your attempts to set this variable when booted from the normal boot volume, whether in normal full boot mode or regular SingleUser. It is important to note that therefor this step cannot be easily integrated into the force-iGPU.sh script (that you will be creating in a minute) and has to be repeated on its own after a NVRAM reset.

This last step assumes that SystemIntegretyProtection has been reenabled. But if SIP is intentionally and permanently kept off, then this step can be integrated in the force-iGPU.sh script above.
But since somehow I intended to keep SIP off permanently and it was turned back on without me noticing it, reliance on SIP staying "off" might be not the best approach. Clearing NVRAM, where SIP settings are stored, might be one such unforeseen disturbance.

Preventive measures for future use

There are two further caveats to know: This is reversible when the SMC/NVRAM is reset. If that happens the GPU-power-pref NVRAM-variable can or even has to be set again to force the use of the iGPU from boot-time.

Since this can happen quite easily (and is often erroneously recommended way too many times than it is actually useful), you should probably prepare for such a scenario and create a simple script to greatly speed up the process and also make entering the necessary variable much less error prone:

 sudo nano /force-iGPU-boot.sh

– Enter the following content to this file:

sudo nvram boot-args="-v"
sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
exit 0

– Now make that executable:

sudo chmod a+x /force-iGPU-boot.sh

In the future, when the SMC/PRAM/NVRAM gets reset to default values it is now possible to boot into SingleUser with:


– And after mounting your boot-volume read-write to execute just this single line:

sh /force-iGPU-boot.sh

Remember that the agc variable is now also cleared. (See above)
Also, make sure you set the default boot-volume again in System Preferences > Startup Disk.

Part 3: Handling Updates from Apple

This setup has now one kext in a place Apple's installers do not expect. That is why in this guide SIP has not been reenabled. If an update that contains changes to the AMD drivers is about to take place it is advisable to move back the AMDRadeonX3000.kext to its default location before the update process. Otherwise the updater writes at least another kext of a different version to its default location or at worst you end up with an undefined state of partially non-matching drivers.

After any system update the folder /System/Library/Extensions has to be checked for the offending kext. Its presence there will lead to e.g. a boot hang on Yosemite and Sierra, an overheating boot-loop in High Sierra.

Upgrading to High Sierra 10.13: with this hack in place is almost straightforward: Despite applying a firmware update the installation process should not touch the NVRAM variable. The installation process also does not use a fully accelerated AMD chip but basic acceleration that is not problematic regarding this hack. However, as noted in the paragraph above the first boot into a system that is finished installing but just about to start the setup process will produce a heat/crash induced boot loop. The offending kernel extension has to be moved again like described above. (Starting at Step 3) After moving the kext, all shall be well.

Important notice for recent updates from Apple:

The last updates for (High) Sierra break the machine again. It updates the firmware, RecoveryPartition, seems to disable the possibility to boot into SingleUserRecoveryMode
and to top it off it installs – even with the DeltaUpdate – a working AMDRadeonX3000.kext!
Without preparation and with just the machine at hand you will be stuck a bit.

In case SingleUserRecoveryMode is gone for good, use regular RecoveryMode. Results are the same, it is just a little slower to boot into: the above procedure is still valid, and faster for all previous versions of Mac OS X/macOS.

If you update to 10.13.6, or later:
Replace the instructions for SingleUserRecoveryMode (Command+r+s) with regular RecoveryMode (Command+r) and disable SIP via Terminal (Example for this precise use case).

In case you find that even regular RecoveryMode doesn't work as expected:
Workarounds for the inability to disable SIP with SingleUserRecovery:

  1. First, boot into single user recovery mode. csrutil edits are not allowed in this mode, but can set the gpu-power-prefs nvram property. This will help to reboot the machine in recovery mode. Then you have to replace the instructions for SingleUserRecoveryMode (Command+r+s) with regular RecoveryMode (Command+r) and disable SIP via Terminal (Example for thi use case).

  2. Before an update, prepare a bootable volume. That can be an external disk or a stick. Any version that boots the machine will be fine. Such a drive can be created on another Mac.
    Keep in mind that on the external drive the AMDRadeonX3000.kext has to be (re)moved as well. Try booting from that drive. Only if that works as expected and you can mount your internal drive with it: reboot from your internal drive and proceed with the update of your internal drive/system to 10.13.6.
    After the update is nearly finished, one reboot will hang. Force a shutdown and reboot from your external drive. Mount the internal drive and move the Radeon.kext. SIP only protects the booted system.

  3. Suggested somewhere online, but really a desperate guess and untested: Instead of SingleUserRecoveryMode with Cmdrs you might try InternetRecoverySingleUserMode CmdOptrs. Alternatively, it might be worth a try to see whether SafeRecoveryMode works CmdShiftr.

Graphical recovery mode might not work too, as it did for me. However, in the last version of High Sierra, it is still possible to boot to single user recovery mode. It just needs good timing. The trick is to first enable recovery mode by pressing cmd+R and immediately after it is recognized the cmd+S command for the single user mode. The exact moment has to be figured out by the user. If cmd+R+S are pressed at the same time, only single user mode will be activated. If first cmd+R is pressed and cmd+S is pressed too late, graphical recovery mode is loaded. – TAKeanice ↵

Screen brightness keys not working in High Sierra or Mojave?

Apple changed how keyboard events for changing screen brightness are handled in High Sierra. With this hack in place the keys might be functionless. If that's the case: One more reason to stay with Sierra.

But you might also resort to another software solution. Ready made applications or apps or extensions:

Recommended OS version

This hack was developed with machines running Yosemite (10.10) to Sierra (10.12). Working nicely on those.

High Sierra

High Sierra (10.13) works nice as well. And it is the last version 'officially fully supported by Apple'. Well, formerly supported. It works fine with this hack, and you might re-enable SIP. To get more security updates you have to go one step further:


With Mojave (10.14) the install process is totally unspported by Apple and gets much more complicated:

  1. You need to install High Sierra once, to get the firmware updates for APFS boot support from Apple. (Alternative: part of the dosdude1 patch guide.)
  2. You need to follow the procedures required by the dosdude1 patcher.
  3. This means trusting 'that guy'.
  4. Lots of reboots required.
  5. NVRAM setting gets seemingly always lost in the process — re-apply like described above once the patch/install procedure is finished. (If you get weird colours eg in Safari's tabs after upgrade to 10.14: AMD is active…, check via System Report)
  6. Caveat: do not follow dosdude1's GPU-disabling recommendation! — ; Use the one above, as usual (The dosdude1 version runs hotter…). Because, once you accept this Franken-status of 'support' from Apple, this patched OS, SIP now kept off by necessity (!), plus the usual downsides from this hack (and eg newer Safari versions killing your favourite extensions…)
  7. You will need to keep around an external volume/USB-Stick with the patched installer, otherwise your machine may become unbootable by updates from Apple…
  8. Mojave is currently the best working OS (IMO) for this machine. Try it out.

To avoid crashes/hangs/boot-loops – which are never a good idea for your filesystem – on a fresh install or an upgrade: make sure to babysit the installation process and always boot into SafeMode (keep Shift pressed during boot-ups until the kext is moved into a safe place –– the installation should proceed just fine in SafeMode.

Closing Remarks and Recommendations

Further: this laptop is overheating, no matter what you do. The cooling system is inadequate and the huge number of failing AMD chips are just proof of that.

To prolong the life of this now hacked machine it is advisable to abstain from really heavy lifting over prolonged stretches of time. Strictly follow the usual recommendations for laptops: use on hard surfaces, keep the fans and fins inside it clean. Using any fancontrol software with relatively aggressive settings should also help: like smcFanControl, MacsFanControl, or TGPro (both commercial).

Disclaimer: This whole procedure is no magic bullet. The state of failure for these chips not 100% predictable. Very few users have issues even with this hack in place: there might be issues with rebooting, going to sleep or waking up properly, most of them coming from users with Yosemite, the least trouble seems to be on Sierra. In these cases it seems sometimes necessary to not use the AMDRadeonX3000.kext, and therefore also not the LoginHook from Part 3. (But see the additional note under *1 above.) High Sierra users report issues with their displays backlight adjustment.

In some cases, even with all these measures in place it seems that the still functioning Thunderbolt port will cause some issues if any peripherals are attached and active when the machine goes to sleep. After this happens any subsequent sleep cycle might be affected and an NVRAM reset with subsequent variable setting dance outlined above will be necessary, again. It seems advisable in such cases to either prevent machine sleep or unplug any hardware on the Thunderbolt port before letting the machine sleep.

Within the restrictions outlined at the start of this answer: Most users report complete success.

Hardware mods/hacks

Several ways available now, some bad, some good.

Bad solution: A very cheap hardware modification is available at/from RealMacMods: While they use a relatively complicated way of setting the necessary EFI variable with linux the following has the advantage of cutting the core voltage to the dGPU completely by removing just one tiny resistor! (Pictures at the link)

On this reboot it is essential that you boot once into safe mode (hold Shift throughout boot), and then choose shutdown (not restart) from the menu.
Do this safe boot with the R8911 resistor in place. Without this SAFE BOOT, the next steps may not work.
Do no more boots until you complete the next steps.
The safe boot clears OS level GPU preferences, that may interfere with the following process.
This will now cause your MacBook Pro to stop switching to the Radeon automatically, but it will still draw power, create heat, and be visible to the OS.
We discovered that simply removing 1 resistor will resolve this.
The resistor can also be replaced with a switch, in case you need to turn your radeon back on for any reason.
The placement of this resistor varies between logic board models.
The resistor in question is R8911 on the 17″ MBP and R8911 on the 15″ MBP a 1 Ohm resistor that provides a current path to the ISL6263C DC to DC Converter.
This resistor controls power to the Voltage Regulator that provides the Core Voltage to the Radeon GPU. Simply put, no core voltage, no GPU. You will find the resistor just to the right of a cooling fan (in the above orientation). It will be near the ISL Voltage converter chip. This is the chip we will be disabling.
Just remove it. The preferred method is a professional reflow station, but an iron and a steady hand will get you where you need to be. If you used flux to remove it (not needed), make sure you clean up with a little Alcohol or other suitable solvent.
That is basically it. Next time you boot up you will notice your GPU defect issue is gone, and you will no longer see the AMD GPU as installed hardware.

I have not tested this but it should eliminate any need to care for the kexts and also solve any issues regarding sleep, wakeup, hibernation, reboot etc.
Caveat for considering this method: since it also seems to rely on having this NVRAM variable set it is likely absolutely essential to have a fully automated method in place to set this variable without any user intervention. (Like a linux stick that makes the necessary changes) Otherwise an NVRAM reset might practically brick the machine. The vendor suggests to protect from accidental NVRAM resets via password and if a reset was made to call them for a 'procedure'.

If bitten by this method, ending up with just a black screen: it seems possible to remotely access the machine with VNC or ssh, so if these are setup beforehand, it may indeed a not so bad option after all, as the nvram variable can bet set in this way. Remember: Untested internet story.

Permanent, reliable and cheap hardware solution!

Dosdude1 has found a solution that looks like the holy grail for this problem: Permanently Disable 2011 15"/17" MacBook Pro Dedicated GPU - gMux IC Bypass

  • Option A, which will be detailed below, is to hard-wire the LVDS output lines from the integrated graphics LVDS output lines straight to the lines connecting to the display.
  • Option B would be to re-program the gMux IC (which is simply a Lattice LFXP2 micro-controller), with a custom firmware to disable the GPU switching functionality. I may experiment with this in the future, but doing so requires special hardware that I don't have. This would, of course, be the optimal solution, though.

This is almost easy. All that's needed are various lengths of wire. To get a glimpse: image on youtube.

The 'bad solution' from above is now made into an almost professional and pre-made hardware solution, eliminating the previous 'badness' of that approach:

Tiresias (the GPUkiller): The Tiresias is a small board that can be soldered onto the motherboard of the MacBook Pro 15-inch or 17-inch 2011 (Early or Late) models.
These are all the models that have the 820-2914-A, 820-2914-B, 820-2915-A or 820-2915-B motherboard.
The 820-2914 and 820-2915 board has two GPUs. The internal (Intel) GPU that is part of the PCH, and an external (discrete) AMD GPU. It is the external GPU that fails in 'a small percentage of MacBook Pro systems' (Apple-speak for: 'very many'). The Tiresias writes the 'gpu-power-prefs' nvram-variable to the ROM so that the Mac does not use the (dead) external (discrete) AMD GPU anymore. If the user clears the NVRAM (PRAM) there is no problem as the Tiresias will write the record again, and the Mac will work again.

This makes this the ideal solution to bring a 820-2914 or 820-2915 with dead GPU back to life. Installation is easy (no wires to solder). You will need to mount a very small board onto the motherboard. An experienced technician can do this in minutes. Other than that R8911 should be removed to turn off power to the dead GPU. This saves energy, generating less heat and conserving battery life. Removing R8911 also prevents the Mac from getting confused by the dead GPU because even with the GPU turned off it will still try to talk to the dead GPU. Depending on what internal contacts in the GPU are ruptured this might confuse or even crash the Mac.
Mac OS X 10.13 High Sierra is also supported. To solve the issue of the backlight not coming back on after sleep also remove R9704 and connect R9704 pin 2 to C9711 pin 1.

OS X 10.6 - 10.12 (Sierra)
The backlight slider (in System Preferences) and the backlight keys (F1 and F2) work. System sleep works. Video out on the Thunderbolt port does not work, but all other functions of the Thunderbolt port do work.

OS X 10.13 (High Sierra)
As far as we know 10.13 (High Sierra) offers no advantages over 10.12 (Sierra). Apple totally redid the video drivers in High Sierra, and seem to have made a mess of it. The backlight controls will not work. And worse, after the machine wakes up from sleep the backlight is not turned back on at all.
To solve the issue of the backlight not coming back on after sleep remove R9704 and connect R9704 pin 2 to C9711 pin 1. This sets the backlight to full brightness. The down-side is that with this modification the brightness will also be on full brightness with the oldes OS's.
Tiresias for 820-2915 (15-Inch) Quantity one (1) Including shipping (world wide) 60 EURO.

image image image

Update for a one-stop software solution

This hack seems to have been cast partially into an application related to the hardware hack! On the one hand this application is more universal than the solution above, as it seems to handle also NVidia cards, that is: it is for disabling all discrete CPUs in all Macs.

Alas, this app by dosdude1 is not well documented. The readme says that it would set the NVRAM variable, move all graphic acceleration drivers, and then install a launchdaemon to handle updates and ensure that the variable stays set.

Not tested and not endorsed — if you already have followed the procedure outlined above!
But if the hack above didn't work at some point for you or seems just to daunting to begin with, then you might try this:

dosdude1: Other, undocumented software that I've written is stored here: MacBook Pro dGPU Disabler.zip

You might have to look into the procedure above again, as the application seems to miss out on improving the thermal management part (if you modify the hardware by removing the transistor this becomes mood: mix and match).
If someone tests this out, please give feedback here via comments or an edit.

Update 2019: 20$ solution that uses a 64bit Windows computer and a Lattice HW-USBN-2A ICSP FPGA programmer to apply a custom firmware to the gMux IC. Dosdude1 claims this to be 'perfect' solution, meaning that even under HighSierra and Mojave battery life, temperature, brightness control and wake/sleep work as expected. Using that solution is permanent and makes everything above obsolete.
But this new solution is not free and requires hardware in the form of a Windows PC and the programmer); as well as currently soldering a few wires temporarily to the logic board.)

[Update June 2020]: This gMUX Bypass with native brightness control is a cheaper (opensource) version of the Dosdude1 hardware hack. GitHub: gMUXBypass

  • 2
    Worked on a MacBook Pro early 2011 that's on its fourth GPU/motherboard replacement - thanks! Commented Feb 8, 2018 at 15:01
  • 2
    @Tarek Strange. You seem to be on High Sierra. I do not know if they have tightened that further up lately. Do you have an older system bootable? From Yosemite it works always; in Sierra as described above (and from both the setting will stick). Otherwise I'd suggest to disable SIP and try that again (then perhaps also from a normal boot?). (Leaving agc out is not catastrophic, I ran the Mac for month without it before finding this trick. Improvement varies only from 'a bit' to 'OK, almost great') Radical chic would be to use a linux stick and set the variable from there… Commented Mar 5, 2018 at 16:47
  • 9
    After a couple of months trying to get my Late 2011 17" mbp back into the land of the living, I finally discovered that the discrete GPU issue was the culprit. Honestly @LangLangC in all my years in IT, I've never seen such a logically-written and comprehensive explanation of a well-crafted solution, with undeniably-expert level detail. And all from an altruistic desire to help others. I'm typing this on my revived MBP, and while I know that you didn’t do this to make money, you saved me potentially thousands so I’ll PM you in the hope I can buy you a beer via Patreon etc. Thanks so much.
    – bobsmells
    Commented Apr 7, 2018 at 5:56
  • 2
    For the record, as of 10.13.4 the kexts related to AMD GPUs are: com.apple.kext.AMDLegacySupport (1.6.6), com.apple.kext.AMD6000Controller (1.6.6), com.apple.kext.AMDLegacyFramebuffer (1.6.6) and com.apple.kext.AMDRadeonX3000 (1.6.6). Commented Apr 7, 2018 at 7:41
  • 6
    Worked for me on a 17" early 2011 running Sierra! External display doesn't work but better than a giant paperweight! Do note (for the noobs like me), you need to type reboot after the initial SIP disable csrutil disable and after the gpu nvram changes in recovery. I wasn't sure how to reboot from the recovery terminal, and tried hard powering down, but the SIP change did not persist that way.
    – Will Buck
    Commented Jun 28, 2018 at 13:57

If the problem is that you're unable to move those files it's probably the System Integrity Protection that's stopping you. I'm assuming you're on El Capitan or Sierra.

  • Shutdown your laptop.
  • Press Command + R and then the power button to boot into recovery mode.
  • Click the Utilities menu and select Terminal.
  • Type csrutil disable and press return.
  • Close the Terminal app and restart out of recovery mode.
  • Now try booting back into Single-User mode and try to mv command.

If that worked re-enable SIP:

  • Shutdown your laptop.
  • Press Command + R and then the power button to boot into recovery mode.
  • Click the Utilities menu and select Terminal.
  • Type csrutil enable and press return.
  • Close the Terminal app and restart out of recovery mode.
  • @klanomath thank you for your quick response. But the only mode I can get throught is the single user mode. It freez in recovery mode even in the Internet recovery mode. Commented Jan 6, 2017 at 6:26
  • @GhaziMarzouk Snacking_IT answered your question! I just edited it a little bit...
    – klanomath
    Commented Jan 6, 2017 at 11:32
  • @Snacking_IT thank you for your quick response. But the only mode I can get throught is the single user mode. It freez in recovery mode even in the Internet recovery mode Commented Jan 6, 2017 at 11:54
  • 2
    Just as an update, in @LangLangC's answer, I was unable to disable SIP on El Capitan during Step 1.3 and 1.4, as Single User Recovery only mounts the drive as read-only. The above approach (booting into recovery mode instead) does work, so this information is useful to include. Commented Nov 15, 2017 at 20:09

Thanks to this answer https://apple.stackexchange.com/a/295805/300460 from https://apple.stackexchange.com/users/251859/langlangc. I followed it when I had this issue in last Sep2018. However I struggled a bit to figure out the exact delta steps to be performed for the second time, when I came across the same issue yesterday again when I did the OSX Security update 2019-003. So, thought of putting down exactly those steps thinking of those users who might come across this issue for a second time. Once again, huge thanks to langlangc for the original one.

I was on OSX 10.13.6 at the time when I did the update.

  1. Restart in single-user mode by press&hold Cmd+S (Cmd+R won't load giving the white screen. Actually, langlangc had asked me to confirm this in Sep2018; but I couldn't reply then as I don't have permission to comment)
    • Run sh /force-iGPU-boot.sh
  2. Restart in recovery mode by press&hold Cmd+r
    • Run these commands. In fact, I put these into a small script file /force-iGPU-boot_without_sudo.sh.
      csrutil disable nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00 nvram boot-args="-v"
  3. Restart in single-user mode by press&hold Cmd+s
    • Ensure an existing /System/Library/Extensions-off folder is removed after taking a backup
    • Run these commands. Again, I put these into a small script file /move_out_amd_kext.sh /sbin/mount -uw / mkdir -p /System/Library/Extensions-off mv /System/Library/Extensions/AMDRadeonX3000.kext /System/Library/Extensions-off/ touch /System/Library/Extensions/
    • Enter nvram boot-args="agc=0"
    • Enter reboot to boot it normally.

Everything else should be working as expected as you would have done all the other necessary steps when you got it working for the first time. All the best.

Update 12 August 2019

I used to depend upon the software based solution suggested by @LangLangC. However, the recent update in August found the normal booting hung on the progress bar. I can get through safe boot mode, though but will find screen flickering a lot.

Update 14 August 2019

Booted successfully when I disabled the SIP in recovery-mode. I can't remember if I have done in the past - but now I guess I may have.

I wasted a lot of time suspecting many different reasons - including the GPU problem getting worse, or potential bugs with 10.13.6 security update 2019-004.

However, now I noticed that it booted this time even with the problematic /System/Library/Extensions/AMDRadeonX3000.kext in place !!!

Update 11 November 2019

The AMD6000Controller.kext is necessary to get the brightness control back to work as usual. That kext has to be present at /System/Library/Extensions/.

  • Could you explain what exactly you mean with "2nd time"? The above looks as if you had NVRAM/PRAM reset in the process. Or is this indeed what you did while being with a working hack on 10.13 and just applied the recent SecUpdate? (The SecUpdate itself should do nothing to invalidate the hack itself, but install a working AMD.kext in the – for the hack – wrong location, and hence needs to be moved). Or from the other side: was your NVRAM reset during the update? Commented May 19, 2019 at 21:46
  • I was already on a working hack on 10.13.6 which was done in last Sep2018 following your answer. Then applied the security update yesterday after which I am stuck again with white screen. I never play around with KEXT files unless I do have to follow your instructions to fix the white screen issue after the security update. With just step-1(1st single-user mode) did not fix issue, so I had to go into step-2(recovery mode) subsequently to step-3(single-user mode again).
    – Raj
    Commented May 20, 2019 at 1:46
  • I just updated my High Sierra volume with the latest 2019-005 security update. The process bar got stuck on the reboot, so I waited for the fans to stop and rebooted my MBP manually in single-user mode and followed your guide. Worked fine! A few questions though: why do you have to repeat the NVRAM hack in step 2? it's already in the /force-iGPU-boot.sh script no? and my Extensions-off directory was already in place, I just moved the new AMDRadeonX3000.kext and called it AMDRadeonX3000v2.kext. Seems better to keep and load the original as stated in @LangLangC guide I guess.
    – aroom
    Commented Oct 22, 2019 at 10:34
  • 1
    @aroom The above repeats a few redundant steps, doing no harm, just a belt & suspenders approach. The key to updates is with NVRAM in place a working X3000 hangs booting. Quite often Apple shipped a defective kext that depended on one original install, all deltas missing a crucial file. (For optimal results, we had to mv old kext into place, then update, then mv to Ext-off again) Now that Apple finally fixed that, it is best to use the newest kext from update, matching the version numbers in the update. With SIP off, just boot SafeMode and mv to Ext-off, deleting the previous version. Commented Oct 22, 2019 at 11:55
  • Has anyone ever reenabled the dGPU setting? What would be the opposite of nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00? Commented Aug 5, 2021 at 16:41

I cannot thank @LangLangC enough for this response. This has just resuscitated 2 machines. A few curve balls are worthy only as a complement to the above:

  • one machine was on Mavericks (10.9.5), so yes SIP related commands could be discarded. However, since the AMDRadeon issue starting arising (and your truly resetting galore the SMC and PRAM), I had ended up generating a split screen somehow with a thin high vertical line as a cursor. It required two cycles of phase 1 to overcome.

  • a second machine was on High Sierre 10.13.6. csrutil disable (point 3 above) would not run; this was tried twice with distinct disks, with identical results. Only Recovery mode allowed the command to proceed successfully

    Cmd + r [Be Pa.tien.t. The recovery partition has to start up with the GUI (I kept the keys pressed until the language choice dialog box that appears when installing system for a first time appears) ] Select the terminal under the Utility menu. This allowed the call. Proceed with the instructions

    nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
    nvram boot-args="-v"
    then reboot

    shutdown -r now and proceed to step 8 above. ( I may have done an extra round of the above two commands; I lost track - but no harm done) ... After step 11

    touch /System/Library/Extensions/ will actually cycle through a couple of reboots and verbose messages before presenting a crisp, grey apple. [Continue with the patience exercise.]

I second the suggestion of downloading and activating smcFanControl or similar before dealing with heat management; seeing the temperature drop is more enlightening than waiting for the fan to spin down.

  • once going, change energy saving settings for the automated computer sleep settings: it played 2020_shuffle with my screen upon waking. So under power adapter, never put computer sleep (the screen can go black though). I have not tried lid down, but I believe this can be an issue. If the screen does get garbled, I found that log-out hotkeys Shift+ Cmd + Q will invariably reset the video to its expected state.

Some flickering will occur; I guess this is practical proof of the necessity for two graphics chips. no big deal though.

  • finally, it dawned on me that since this is a software solution, popping the boot disk with directories and files already prepared and installing in another machine (if that's an option) might make the process faster to edit the arching and shell scripts. Will attempt later. attempted but failed as step 8 did not seem to register.


  • external video is not accessible as designed, but doing so via USB port is.
  • Bootcamp also is a casualty.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .