Jump to content

Sierra AppleGraphicsDevicePolicy Clover Patch


Brumbaer
 Share

38 posts in this topic

Recommended Posts

The patch doesn't seem to work reliably, so it will be better to stick to the old method of using a command file to patch the kext.

 

Disappointing, but I do not see a way to quickly find a solution, that will work as well as patching by command file.

 

I leave the patches here so the posts will still be in context.

 

 

 

The following 5 patches will spare you to manual patch the AppleGraphicsDevicePolicy kext - if you have to patch it.
You need all 5 patches.
 
The easiest way is to copy them into the kextstopatch array in your config.plist
 
Here they come


			<dict>
				<key>Comment</key>
				<string>Brumbaer's GDP Patch 1</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				RURJRAA=
				</data>
				<key>Name</key>
				<string>AppleGraphicsDevicePolicy</string>
				<key>Replace</key>
				<data>
				RURJSQA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Brumbaer's GDP Patch 2</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				dW5sb2FkAA==
				</data>
				<key>Name</key>
				<string>AppleGraphicsDevicePolicy</string>
				<key>Replace</key>
				<data>
				dW5sb2FlAA==
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Brumbaer's GDP Patch 3</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				RGVmYXVsdAA=
				</data>
				<key>Name</key>
				<string>AppleGraphicsDevicePolicy</string>
				<key>Replace</key>
				<data>
				bm9uZQAAAAA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Brumbaer's GDP Patch 4</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				Q29uZmlnTWFwAA==
				</data>
				<key>Name</key>
				<string>AppleGraphicsDevicePolicy</string>
				<key>Replace</key>
				<data>
				Q29uZmlnTWFxAA==
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Brumbaer's GDP Patch 5</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				RmVhdHVyZUNvbnRyb2wA
				</data>
				<key>Name</key>
				<string>AppleGraphicsDevicePolicy</string>
				<key>Replace</key>
				<data>
				RmVhdHVyZUNvbnRyb20A
				</data>
			</dict>
			

Tested under Sierra only.
 
There's no reason why they shouldn't run under El Capitan or Yosemite

  • Like 11
Link to comment
Share on other sites

Not again  :(

 

Have you ever used that patch ? Did it work for you ? I assume that you will answer one of those questions with "No"

 

I don't know whether his worked at some time or under certain combinations of hardware, but it never worked for me and many (all ?) others.

That's why you see so many "guides" how to patch the kext manually.

 

You will note that I use two patches to ensure that it works. It does work on my 3 systems while PikerAlphas patch works on none of them.

 

I hope it will help all people who are in the same spot.

  • Like 1
Link to comment
Share on other sites

Yes Its worked 10.12

Thank you.

post-413859-0-61372000-1475853268_thumb.png

post-413859-0-26685900-1475853278_thumb.png

  • Like 2
Link to comment
Share on other sites

@ Brumbaer

 

Many thanks! I have been looking for a long time for a working clover patch. :D

 

The patch is working with the SMB of MBP 8,3 on GT 550m with Yosemite 10.10.5.

 

There should be the big chance, that  it is also working on El Capitan.

 

Have fun.

  • Like 1
Link to comment
Share on other sites

I'm sorry to say so, there seems to be a major problem.

Interestingly enough it seems to work, if you had patched the Kext manually once even if you revert to the original kext, but it does not work if you start with a freshly installed system.

 

Sorry for the bother - back to the drawing board.

Link to comment
Share on other sites

I'm sorry to say so, there seems to be a major problem.

Interestingly enough it seems to work, if you had patched the Kext manually once even if you revert to the original kext, but it does not work if you start with a freshly installed system.

 

Sorry for the bother - back to the drawing board.

Did you test with a fresh install?

 

Sent from my SM-G900I using Tapatalk

Link to comment
Share on other sites

I'm sorry to say so, there seems to be a major problem.

Interestingly enough it seems to work, if you had patched the Kext manually once even if you revert to the original kext, but it does not work if you start with a freshly installed system.

 

Sorry for the bother - back to the drawing board.

Did you try to boot without cache on first boot ?

Link to comment
Share on other sites

Did you try to boot without cache on first boot ?

 

 

 
No difference.
I also rebuild the cache manually, no difference.
 
My test procedure involuntarily was (because I had the kext already patched). 
 
Patching the Kext and rebuild caches - had been done before
Restore original kext, rebuild caches, reboot -> fail
Insert patches in Clover, reboot -> success
 
Disable patches in Clover, reboot -> fail
 
That's why I thought the patches were working.
 
 
Than I installed a System anew to test El Capitan:
Insert patches in Clover, reboot -> fail
Rebuild caches, reboot -> fail
Did some other stuff->fail
Patching the Kext, rebuild caches, reboot -> success
Restore original kext, rebuild caches, reboot -> fail
Insert patches in Clover, reboot -> success
Disable patches in Clover, reboot -> fail
 
Did the same sequence with Sierra same behaviour.
 
Installed the Upfate to 10.12.1 ß3 and it failed again, After patching once it does work.
But if I have to patch it once, I don't need the Clover patch.
 
Whether I run a command to make Clover recognise the kext or a command top patch the kext doesn't matter.
 
I'll crosscheck on a different System when the next Beta comes out.
 
I anybody does an "System Update" and the patch still works, let me know. Just in case it's something on my System/Clover whatever combo.
  • Like 1
Link to comment
Share on other sites

Ok,

managed to get it done.

 

Now there are 5 patches, see first post.

 

Probably there is some other way, but it is tedious to test as 3 of those patches are only needed on an freshly updated or installed system. 

Once the system startet successfully, you would have to reinstall the complete system to be able to test the function.

 

Let me know whether it works for you especially after an update or fresh install of a system.

Link to comment
Share on other sites

 Share

×
×
  • Create New...