Unable to patch 15-inch 2010 MacBook Pro on High Sierra

[jeromydp]

I'm getting the following message:
| Checking compatibility
MBPModelVersion : MacBookPro6,2 ➔ Compatibility : OK ✓
| Checking SIP Status
SIP Disabled
| Searching for AppleGraphicsPowerManagement.kext
AppleGraphicsPowerManagement.kext found
********** Starting MBP GPU Fix **********
Copying Info.plist file
Previous Info.plist file removed
Could not open Info.plist file
********************* MBP GPU Fix FAILED *********************

[julian-poidevin]

Hi,

Did you try the app on a previous version of macOS before updating to High Sierra ?

After patch failure, can you please go to /tmp/ directory and see if there is a file named PatchedInfo.plist in it. If so, let me know if you are able to open the file by double-clicking on it.

Also, before running the patch, you can also try to remove all the files in /tmp/ folder.

Thanks.

[mhamzas]

It worked fine for me on High Sierra

[kickass-id]

For me, I got MBP GPU Fixed Successfully but it doesn't seem to work (also MBP 15" mid-2010, High Sierra). After applying the patch (log below), I excitedly open IMDB using Safari, and my laptop crashed :(

| Checking compatibility
MBPModelVersion : MacBookPro6,2 ➔ Compatibility : OK ✓
| Checking SIP Status
SIP Disabled
| Searching for AppleGraphicsPowerManagement.kext
AppleGraphicsPowerManagement.kext found
********** Starting MBP GPU Fix **********
Copying Info.plist file
Patching Info.plist
- FindChild - key|MacBookPro6,2
- NextSibling - dict
- FindChild - key|LogControl
- ModifyIntValue - integer|1
- FindSibling - key|Vendor10deDevice0a29
- FindSibling - key|BoostPState
- FindSibling - key|BoostTime
- FindSibling - key|Heuristic
- FindSibling - key|IdleInterval
- ModifyIntValue - integer|10
- RemoveSiblingLabel - P3HistoryLength Not found
- FindSibling - key|SensorSampleRate
- ModifyIntValue - integer|10
- FindSibling - key|Threshold_High
- FindSibling - key|Threshold_High_v
- FindSibling - key|Threshold_Low
- FindSibling - key|Threshold_Low_v
Info.plist successfully patched
| Loading Kernel Extension
Removing existing kext in tmp : ✓
Copying actuel kext into tmp : ✓
Copying patched Info.plist into kext : ✓
Changing permission of kext : ✓ /tmp/AppleGraphicsPowerManagement.kext/Contents/_CodeSignature/CodeResources
/tmp/AppleGraphicsPowerManagement.kext/Contents/_CodeSignature
/tmp/AppleGraphicsPowerManagement.kext/Contents/MacOS/AppleGraphicsPowerManagement
/tmp/AppleGraphicsPowerManagement.kext/Contents/MacOS
/tmp/AppleGraphicsPowerManagement.kext/Contents/Info.plist
/tmp/AppleGraphicsPowerManagement.kext/Contents/version.plist
/tmp/AppleGraphicsPowerManagement.kext/Contents
/tmp/AppleGraphicsPowerManagement.kext

Removing existing kext : ✓
Copying patched kext into Extension : ✓
Loading modified kext : ✓
********************* MBP GPU Fixed Successfully *********************

[mhamzas]

Try applying patch twice. It worked for me.

[kickass-id]

After applying the patch twice, my laptop hasn't crashed ever since. I have Android Studio opened (usually it's instant-crash). What kind of sorcery is this!!! :D

EDIT: Just curious, what's the downside other than making it unsuitable for gaming (which I don't care, I have a PC)?

[julian-poidevin]

The Mac is just a bit less performant and it does not work if you are using an external screen. These are the only two downsides.

[mhamzas]

@kickass-id , The same happened to me and I thought that may be it didn't get applied. After crashing I tried and it worked.
That's strange but some how I make it work :p

[mhamzas]

@julian-poidevin But you really did an amazing job. You've save a lot of $ !

[julian-poidevin]

@mhamzas : Glad it finally worked. If I saved you the price of a mac please consider paying me a beer via the donation button in the app !😄 🍺

[mhamzas]

@julian-poidevin I am not gonna pay you for beer. I'll pay you for a Dinner. 🥇

[julian-poidevin]

@jeromydp Could you get the patch running by following my tips ?

[julian-poidevin]

@jeromydp Please let me know if it's ok for you, I'll close the issue if I get no news in few days.

[jeromydp]

Sorry about my delay & thanks for checking in. I haven’t made time to try it, but my kids remind me regularly about how their MacBook crashes. I’ll make a point to follow your tips tomorrow.

…

On Nov 16, 2017, at 1:19 PM, Julian Poidevin ***@***.*** ***@***.***>> wrote: @jeromydp <https://github.com/jeromydp> Please let me know if it's ok for you, I'll close the issue if I get no news in few days. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#35 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AfIuM63sEHez0PWqHgwjTMdgL4BmjQB0ks5s3KbUgaJpZM4Pyz4E>.

[jeromydp]

I followed you instructions, reran the patch and it appears to be successful! Do I need to reapply the patch after minor operating system upgrades?

[julian-poidevin]

Yes, the patch has to be run after EVERY OS update.

[amordicus]

Bonjour Julian,
I'm not sure you will get this message, since the issue is closed. But I'll comment anyway!
This problem happens when MBPMid2010_GPUFix is ran from a none admin user. And login into an admin account to run it again doesn't stop the error (Could not open Info.plist file) from happening again, but deleting files from /tmp/ works just fine.

I guess the application should ask for an admin user name!

[Bl2c5FlA9]

Amordicus- Thank you for your thoughtful insight.  I followed your procedure and ultimately had success.  I appreciate you taking the time to assist me with this problem!

…

On Oct 31, 2018, 11:48 AM -0700, amordicus ***@***.***>, wrote: Bonjour Julian, I'm not sure you will get this message, since the issue is closed. But I'll comment anyway! This problem happens when MBPMid2010_GPUFix is ran from a none admin user. And login into an admin account to run it again doesn't stop the error (Could not open Info.plist file) from happening again, but deleting files from /tmp/ works just fine. I guess the application should ask for an admin user name! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.