MBP 1,1-10,2 Force 2011 MacBook Pro 8,2 with failed AMD GPU to ALWAYS use Intel integrated GPU (EFI variable fix)

[saldin]

I have the same symptom on the MBP 15 "i7 Late 2011 820-915-B, everything is displayed more blue. For now I set the standard LCD profile, but this is not the color I had before disconnecting the AMD GPU. I found a tip in some thread to convert two resistors to 0R, but that was for MBP 17 ". Maybe one of the colleagues will suggest a solution.

I hope someone else can contribute with this stumper. My MacBook Pro is the Early-2011 with no hardware fix, only software fix. Right now I left the calibrated profile there and switch to it when I have to work with Quick Look or a PDF and then switch back to the old one after I'm done, but I wish I wouldn't have to resort to a workaround... This whole thing is a huge workaround as is. 😓

 

[anyany]

I hope someone else can contribute with this stumper. My MacBook Pro is the Early-2011 with no hardware fix, only software fix. Right now I left the calibrated profile there and switch to it when I have to work with Quick Look or a PDF and then switch back to the old one after I'm done, but I wish I wouldn't have to resort to a workaround... This whole thing is a huge workaround as is. 😓

I used the hardware method and removed the resistor r8911 that turns on the DC/DC converter ISL6263C that powers the AMD GPU. In a word, I have no problem with the returning AMD GPU because it is turned off. However, this excess of blue screen color is tiring.

 

[DeppJones]

I removed as well the resistor on my MBP 2011 15“ and the machine is running quite good with only the HD3000.

What I have noticed, are graphical errors in the photos app but only in some RAW-Files. Other file formats like jpeg or png are without any issues. Since the 13“ MBP has only the HD3000 and has no such issues, I guess it has something to do with the deactivated AMD GPU.

Is there any way to tell the 15“ MBP, that it is a 13“ model? The 13“ model shouldn‘t have the option for „graphic card switching“ in the energy options. Would it be an option to use OpenCore and spoof the device identifier? Will the OpenCore EFI entries interfere with the deactivated AMD GPU?

 

[anyany]

I removed as well the resistor on my MBP 2011 15“ and the machine is running quite good with only the HD3000.

What I have noticed, are graphical errors in the photos app but only in some RAW-Files. Other file formats like jpeg or png are without any issues. Since the 13“ MBP has only the HD3000 and has no such issues, I guess it has something to do with the deactivated AMD GPU.

Is there any way to tell the 15“ MBP, that it is a 13“ model? The 13“ model shouldn‘t have the option for „graphic card switching“ in the energy options. Would it be an option to use OpenCore and spoof the device identifier? Will the OpenCore EFI entries interfere with the deactivated AMD GPU?

This forum is down, no answer. I also have a problem after turning off the AMD GPU power converter (MBP 15 Late 2011 i7). I have a lot of blue color cast and errors in some places in my photos. It looks as if the computer has a graphics mode that is too low and the color configuration was for an AMD GPU instead of Intel HD Graphics 3000. I feel close, but no one wants to help.

 

[apples_arrogance]

Excuse me for not reading all 113 pages of this thread. For me with a 15" Early 2011 and broken graphics chip booting into single user mode via ⌘S and applying
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00 nvram boot-args="-v" reboot
worked nicely and the machine is again able to boot normally, while it got stuck on boot when using the discrete GPU.

Ideally I would want to reinstall a fresh High Sierra from a bootable USB. Created the USB but when booting from it, the computer gets stuck on a white screen. Assume that is, because it is trying to use the discrete GPU. As I am unable to get into recovery mode I cannot apply the terminal commands. Certainly I can just remove all user files and go with that solution, but a clean start would be nicer.

Any ideas how to tackle this?

 

[JMVB]

Most of us actually read the 113 pages...
Good luck with that

 

[Boomish69]

I can't seem to find a solution on installing a new SSD on a 17" MacBook Pro with a GPU problem, I can boot into internet recovery but it gets blue screen halfway through installing. Do we install on another Mac and move the drive?

 

[anyany]

I can't seem to find a solution on installing a new SSD on a 17" MacBook Pro with a GPU problem, I can boot into internet recovery but it gets blue screen halfway through installing. Do we install on another Mac and move the drive?

No, you install immediately to the target disk. If you cannot install the system via the Internet, try to make an installation pendrive with this system.

 

[aisymbian]

I deleted the OS. So there isn't any OS there and if I try Internet Recovery, it's always Vertical BlueScreen. Can I use this method?

 

[aisymbian]

I can't seem to find a solution on installing a new SSD on a 17" MacBook Pro with a GPU problem, I can boot into internet recovery but it gets blue screen halfway through installing. Do we install on another Mac and move the drive?

have you found the solutions?

 

[anyany]

I deleted the OS. So there isn't any OS there and if I try Internet Recovery, it's always Vertical BlueScreen. Can I use this method?

Search the internet for a method of creating a bootable flash drive with the selected OS-X system.

 

[studio_music_guy]

Hello. Hopefully someone can help me out, or possibly point me in the right direction.
I tried a similar method on my 2011. It involves moving the kext files to a temp location and I’m pretty sure the same code in single user mode. However, in both my partitions (High Sierra and Mountain Lion, yes I did the process for both OS versions) the graphics were very laggy as described. But I can log on and it won’t shut itself off.

Anyone have either any ideas to fix me seemingly non-accelerated graphics issue or alternatively help me go back to “how it was”? I moved the kext files back to the extensions folder and reset smc and pram and it’s still doing the laggy thing!

Here is the exact method I used.

Disable Discrete Graphics on MBP

Any help is GREATLY appreciated.

 

[Sakul]

Search the internet for a method of creating a bootable flash drive with the selected OS-X system.

I have the same problem.Disabled the second GPU and now i'm trying to install OS to a new SSD .i created the USB boot stick, starting with option key selecting USB boot, but i get black screen ( identifying devices i thing) and freeze.Any ideas are appreciated

 

[Boomish69]

No mate, no solution yet, I can do the disable script and it starts installing but it gets so far and I get a blue screen.

Thing is my problem started after a security update, I had zero grqphics problems before this, and booting up the screen is fine, it crashes to a blue screen at about 75% every time, it’s almost as if it’s loading the wrong kext.
so frustrating I wish I’d never done that update. I’d left it for so long..

 

[mbp17forever]

Ideally I would want to reinstall a fresh High Sierra from a bootable USB. Created the USB but when booting from it, the computer gets stuck on a white screen. Assume that is, because it is trying to use the discrete GPU. As I am unable to get into recovery mode I cannot apply the terminal commands. Certainly I can just remove all user files and go with that solution, but a clean start would be nicer.

Any ideas how to tackle this?

Not sure if it's related, but here is what worked for my early 2011 17" after disabling dGPU with "nvram fa4ce28d..." method, when I tried to install a fresh copy of any MacOS to a new/empty SSD.

First of all, what i realised when AMD graphics failed, is that after disabling dGPU, the only MacOS version that can be installed without issues on an empty SSD is Catalina (with dosdude patcher). All other versions (El capitan, Sierra etc) i tried to install always freeze/stuck at some point, staying at the loading bar forever. My guess is that, since dosdude version of Catalina doesn't include all AMD drivers, it always bypasses dGPU on the installation/boot process.

After having Catalina successfully installed on my empty disk, i created a second partition on my SSD to install Yosemite (chose Yosemite to keep brightness control and legacy software). On the second partition, before installation of Yosemite completes, at some point around 70% it stuck on the loading bar. After some minutes on this screen i manually turned off MBP and booted again normally into Catalina partition. Into Catalina partition i opened folder of the second partition, the one with the Yosemite "unfinished" installation, which btw seemed to be installed successfully (even if the bar stayed on 70% and never completed), then found AMDRadeonX3000.kext file on the relevant folder and manually deleted it (send it to trash-empty trash). Had no hope it will work but voila: on the next boot it entered normally to Yosemite. Then i ran Dosdude program dGPU disabler. Right now i stay with this Catalina/Yosemite dual boot setup with no issues. Don't know if it will work for someone else but for me it did...

 

[Projectns]

Short question.
Is it posible to use the method from dos with
Gmux and Flash the Bios from the MacBook 2011 13 Inch? It has also the Intel hd 3000. i have also flasher to Test it

 

[Projectns]

Does someone use Windows on the Mac?

 

[jdran]

There is not *one* guide to write up. Many roads lead to Rome. The best option would be if AppleMacFinder would update the first post of this thread pointing to the best alternatives.

Anyway. Even if this post now will quickly drown in the sheer length of this thread, I think this is currently one of the better guides:

#####__ The Guide __#####

This guide assumes that you run a stock system. Problem just occured. That means:
This guide assumes that all kexts are still in their default location /System/Library/Extensions.
Having all AMD-kexts there except one is beneficial for 'proper' operation.

What does "stock system" means? If I have moved the kexts, does this becomes fixed again if I move them back?

 

[mrzo]

Hello AppleMacFinder ! Hey Everybody !!

I had to re-apply the ( great ) fix ( because : reseted Pram and Smc ).
No problem to apply the fix ( for 3rd time for me ) but ...

When I checked Activity Monitor ( see attachments ) :

The first time i had to apply the fix ( 2017 ), everything Ok.

The second time ( 2019 ): My system started with with 6go ram already used on 16go installed. ( I mean on Activity Monitor ). I fixed the problem with Onyx ( Automation : cache rebuilded ).

The Third time ( today ) : I applied the fix, and when I checked Activity Monitor bim ! again : more than 6go already used, without any application launched.

I tried : AppleJack, Onyx, Yasu, nothing worked ... ( note : they don't kill the fix )

Before patching, I made a Ghost with Carbon Copy Cloner.

So I am able to boot on my old system with external drive to compare both system. ( the ghost was alrealy patched with AppleMacFinder's fix )

See attachments : less than 3GO before - Now, 7go

So i decided to replace the actual system by the Ghost.
and when i restarted ... My system used 7go de ram again, with exacty the same system i checked on the ghost 30 mn before ( the ghost use only 3go ).

Still some cache somewhere ... prelinkedkernel ?

If someone can help me, thanks.

 

[MacBook17]

I don't get much time to research the internet, so I'll try to make this quick as I can...

After nearly a decade of service, the early-2011 MBP17 we purchased new is just now giving us video problems (pink and white vertical bars). Based on the reading I've done, thus far, this is normally caused by an AMD GPU chip that Apple used back in the day and, furthermore, is no longer available for replacement purposes.

Now, I've done enough research on this to know that there is more than one way to address this problem. Some of them involve physical repairs and/or mods and some of them involve instruction/script changes. Although I will never have the time to read through this entire thread, it would seem that it's based on a script fix.

I do not own any specialized surface mount type soldering equipment, but I was a tech who, once upon a time, calibrated and repaired all manner of USAF aircraft test equipment -- so I've done a lot of soldering.

My questions are:

(1) Does one have to own specialized soldering equipment to perform the hardware mod fix?

(2) Is there a viable [please read: permanent] fix that can be performed via script/instructions?

(3) Has there been a shift to a "new" GPU fix that makes a lot of these discussions a thing of the past?

Once again, I don't get a lot of time for this kind of research, so a pointer to "the latest" on this issue would be most greatly appreciated. We simply can't afford another MBP, so thank you very much for your time and your kind attention.

 

[panwato]

I don't get much time to research the internet, so I'll try to make this quick as I can...

After nearly a decade of service, the early-2011 MBP17 we purchased new is just now giving us video problems (pink and white vertical bars). Based on the reading I've done, thus far, this is normally caused by an AMD GPU chip that Apple used back in the day and, furthermore, is no longer available for replacement purposes.

Now, I've done enough research on this to know that there is more than one way to address this problem. Some of them involve physical repairs and/or mods and some of them involve instruction/script changes. Although I will never have the time to read through this entire thread, it would seem that it's based on a script fix.

I do not own any specialized surface mount type soldering equipment, but I was a tech who, once upon a time, calibrated and repaired all manner of USAF aircraft test equipment -- so I've done a lot of soldering.

My questions are:

(1) Does one have to own specialized soldering equipment to perform the hardware mod fix?

(2) Is there a viable [please read: permanent] fix that can be performed via script/instructions?

(3) Has there been a shift to a "new" GPU fix that makes a lot of these discussions a thing of the past?

Once again, I don't get a lot of time for this kind of research, so a pointer to "the latest" on this issue would be most greatly appreciated. We simply can't afford another MBP, so thank you very much for your time and your kind attention.

1.- No, the only tools needed are a soldering iron and a bit of patience.
2.- No, there is no “permanent” fix with any script or variable. The nvram fix last until you do a PRAM reset.
3.- today there is only, three?, methods available.
EFI variable (permanent until PRAM reset)
Gmux flash (paid but permanent)
Tiresias mod (cmizapper), a little board (paid) soldered onto the ROM chip, but with this you have backlight control with the keyboard on HighSierra+

I think I don’t missed anything, if you have any questions, feel free to ask

 

[MacBook17]

1.- No, the only tools needed are a soldering iron and a bit of patience.
2.- No, there is no “permanent” fix with any script or variable. The nvram fix last until you do a PRAM reset.
3.- today there is only, three?, methods available.
EFI variable (permanent until PRAM reset)
Gmux flash (paid but permanent)
Tiresias mod (cmizapper), a little board (paid) soldered onto the ROM chip, but with this you have backlight control with the keyboard on HighSierra+

I think I don’t missed anything, if you have any questions, feel free to ask

Thanks very much for the informative reply, panwato.

I've [now] been in touch with the guy who apparently started the gMux flash fix, but, as you've alluded to, I suspect that it comes with the loss of external monitor capability and/or screen brightness control...but I'm still awaiting a response to certain questions to learn what the exact downsides are.

I wasn't aware of the Tiresias modification. We are at presently at OS X El Capitan (10.11.6), so, once again, I'm at loss when it comes to OS X versions like High Sierra (10.13.X). If you would kindly let me know what's involved with performing this mod and, just as importantly, adding the newer OS X, I'd be most grateful for the information.

Thanks again for the reply ~ MacBook17

 

[PedroHenriques]

Hello all.
I have been a long time performer of the famous nvram fix in the last 2/3 years. But this week the problem came back much stronger. So now I can rarely manage to even see anything on the screen: most times I just hear the optical drive sound and see the sleep light in a kind of 50% always on state. Sometimes in addition to this I hear one chime sound.
In some rare attempts I am able to see the gray screen and make some boot inputs like single user, but whenever I reboot again I loose complete acess to anything and can only see a black "turned off" screen and the sleep light. The fans are turned on. I manage to erase the main disk and get into a usb installer of yosemite, but when it finishes the progress bar and goes for the first reboot, screen goes black and I cant do anything until I wait some good 10/15minutes or more and then with some luck I am able to put some commands on boot again.
Any ideas? Can I discard CPU/RAM problems? (even yesterday I was able to install Sierra and it was working fine until I put it to sleep - then these problems never stopped)

 

[mbp17forever]

Hello all.
I have been a long time performer of the famous nvram fix in the last 2/3 years. But this week the problem came back much stronger. So now I can rarely manage to even see anything on the screen: most times I just hear the optical drive sound and see the sleep light in a kind of 50% always on state. Sometimes in addition to this I hear one chime sound.
In some rare attempts I am able to see the gray screen and make some boot inputs like single user, but whenever I reboot again I loose complete acess to anything and can only see a black "turned off" screen and the sleep light. The fans are turned on. I manage to erase the main disk and get into a usb installer of yosemite, but when it finishes the progress bar and goes for the first reboot, screen goes black and I cant do anything until I wait some good 10/15minutes or more and then with some luck I am able to put some commands on boot again.
Any ideas? Can I discard CPU/RAM problems? (even yesterday I was able to install Sierra and it was working fine until I put it to sleep - then these problems never stopped)

try to install Catalina (dosdude1 patcher version) from a USB drive instead of Yosemite.
If the problem is related to the failed dGPU, probably it will complete the installation process without problems

 

[PedroHenriques]

try to install Catalina (dosdude1 patcher version) from a USB drive instead of Yosemite.
If the problem is related to the failed dGPU, probably it will complete the installation process without problems

Thanks for the reply.
I started last night installing that patched version of catalina. But then in the first reboot it goes to a black screen again.
So this morning I went and turned it on:

It turns on and kept trying to conclude the installation. But after that when it goes for another reboot:

It goes into the problematic behaviour of black screen, sleep light on, fans on, but no chime and no progress.
Funny thing is if I wait another 20 minutes or so, I can have another chance of it turning on and behaving "normally".

I´m not even sure if this is the gpu problem. Tried changing the ram from 16gb to the original 4gb but the same behaviour is present. Did an apple hardware test and showed no problems..