Code: ... <string>com.apple.driver.AppleGraphicsDevicePolicy</string> <key>Config1</key> <dict> <key>GFX1</key> <dict> <key>unload</key> <true/> </dict> </dict> <key>Config2</key> <dict> <key>GFX0</key> <dict> <key>EDID</key> <dict> <key>0610ae02</key> <data> AP///////wAGEAOuAAAAAAwYAQS1 PCJ4IsgFp1VLoCYMUFQAAAABAQEB AQEBAQEBAQEBAQEBAAAAEAAAAAAA AAAAAAAAAAAAAAAAEAAAAAAAAAAA AAAAAAAAAAAA/ABpTWFjCiAgICAg ICAgAAAAAAAAAAAAAAAAAAAAAAAA Ai0CAx6BcPoQAAASejH8eL3MApCI UdNo+hAA9fn6//8AAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAknATeQMAAwAUgG4BhP8TnwAv gB8APwtRAAIABAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAMeQ </data> <key>0610ae06</key> <data> AP///////wAGEAeuAAAAABsZAQS1 PCJ4IAAAAAAAAAAAAAAAAAABAQEB AQEBAQEBAQEBAQEBAAAAEAAAAAAA AAAAAAAAAAAAAAAAEAAAAAAAAAAA AAAAAAAAAAAA/ABpTWFjCiAgICAg ICAgAAAAAAAAAAAAAAAAAAAAAAAA AaZwE3kDAAMAFIBuAYT/E58AL4Af AD8LUQACAAQAf4EY+hAAAQEAEnYx /HixmQIQiGLT+vj4/v//AAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAB3kA== </data> <key>0610ae0a</key> <data> AP///////wAGEAuuAAAAABoZAQS1 PCJ4IAAAAAAAAAAAAAAAAAABAQEB AQEBAQEBAQEBAQEBAAAAEAAAAAAA AAAAAAAAAAAAAAAAEAAAAAAAAAAA AAAAAAAAAAAA/ABpTWFjCiAgICAg ICAgAAAAAAAAAAAAAAAAAAAAAAAA AaNwE3kDAAMAFIBuAYT/E58AL4Af AD8LUQACAAQAf4EY+hAAAQEAEnYx /Hix/wIQiGLT+vj4/v//AAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAARkA== </data> <key>index</key> <integer>0</integer> </dict> <key>unload</key> <false/> ... <key>ConfigMap</key> <dict> ... <key>Mac-42FD25EABCABB274</key> <string>Config2</string> ... <key>Mac-65CE76090165799A</key> <string>Config2</string> ... <key>Mac-B809C3757DA9BB8D</key> <string>Config2</string> ... <key>Mac-F60DEB81FF30ACF6</key> <string>Config1</string> <key>Mac-FA842E06C61E91C5</key> <string>Config2</string> ...

How to verify that your system is functional except for video:

Fixes:

Code: <dict> <key>Comment</key> <string>AppleGraphicsDevicePolicy (board-id) Patch (c) Pike R. Alpha</string> <key>Find</key> <data> Ym9hcmQtaWQ= </data> <key>Name</key> <string>AppleGraphicsDevicePolicy</string> <key>Replace</key> <data> Ym9hcmQtaXg= </data> </dict>

My preferred method

1. Share the screen from another Mac on your network to control the system and verify that it is functional and responsive (you must have Screen Sharing enabled). NOTE: You should be able to boot using nv_disable=1 to enable screen sharing if you have a Nvidia GPU.2. Use a keyboard shortcut to verify that the system is responsive:• On a Apple keyboard, the eject key will open and close my optical drive.• On a Apple keyboard, the play button will launch iTunes and hitting it a 2nd time will start playback depending on what state the app was in when I quit it last.• On a Apple keyboard, control + eject will bring up the the "Shut Down" dialog window with the default button being "Shut Down". When you hit enter/return it causes the default button to activate and the system will shut down properly.• Holding down control + option + command and then pressing the power button on your case or mobo quickly (less than 1 second) will cause open apps to quit and the system will shut down properly. NOTE: Holding down the power button for 5 seconds will cause the system to hard power off and this is not proof of response from OS X (this is how you force a frozen system to power off).Many people have been looking for a Clover "on the fly" info.plist patch to be done at every boot but it fails because Clover's info.plist patches are only visible in the kext caches and it doesn't change the actual info.plist file. It seems that more than one kexts are reading the ConfigMap from the info.plist in it's actual file path, so putting "none" in the kext cache changes nothing. This also makes it impossible to use the dummy kext method. Even if you get a dummy kext with a patched info.plist to load instead of the original kext, the info.plist will still be read from the original kext's file path.Pike came to the rescue (sort of) again on November 23rd, 2015 with a Clover "on the fly" binary patch for the AppleGraphicsDevicePolicy.kextThis patch changes board-id to board-ix in the binary file but only seems to give the desired result if you have 1 discreet GPU. I have have 2. With 2 GPUs, one always unloads and it's unpredictable which one will work. Some people with only 1 GPU also have issues with this patch.NOTE: You will need to use the boot argument kext-dev-mode=1 for 10.10 Yosemite, disable SIP or use kext-dev-mode in 10.11 El Capitan and 10.12 Sierra.In this pic from IORegistryExplorer you can see the AppleGraphicsDevicePolicyControlClient loaded on my second GPU (GTX 980) installed in PCI slot 4 (NPE7):In this state, it will not send a video signal from any of it's ports.In the next pic you can see that I have injected my GTX 980 as GFX1 in NPE7 and AGDPCC is no longer loaded to it:Now all ports are functional. It's also worth noting that I have my 1st GPU (GTX Titan X) injected as GFX1 as well.