Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Hello,
to short question.
I wanna try the wire method (w/o the flasher). Should i remove the gpu chip and than wire the pins or should i wire only the pins of the schematic?
Is it possible to flash the efi rom to install windows 7/10?
thanks and regards
 
@jdran @b251 take a look to the efi variable fix


I did this procedure at least 10 computers, mine, my brother, friends etc, and no one had issues:

I use my mac to video playback, with a Blackmagic thunderbolt mini monitor, or with a Displaylink adaptor, flawlessly

I used the ubuntu method and removed the r8911

Then upgraded to HS, and no wake up or brightness problems at all

Check my post


Is just matter to do a good search!
The problem with that method is that you reset the PRAM, you lose it. Also, doesn´t go out from sleep. I mean the "Or try the simplest way - No needed ArchLinux - Only MacOS:"
 
The problem with that method is that you reset the PRAM, you lose it. Also, doesn´t go out from sleep. I mean the "Or try the simplest way - No needed ArchLinux - Only MacOS:"
I have no need to reset the pram in almost 3 years...
And, if you bother in take a look my answer carefully, mine indeed sleep...
 
  • Like
Reactions: jdran
I have no need to reset the pram in almost 3 years...
And, if you bother in take a look my answer carefully, mine indeed sleep...
As I said, ai was talking about the “Only MacOs” method. I supose you follow the Arch Linux method. No need to be so agressive.
 
@JMVB Yes but the EFI variable method does not survive a NVRAM reset. If you accidentally reset the NVRAM while R8911 is removed the system gets unbootable.
 
Before I read your answers, I tried the simple method removing kexts. I was able to login first time after three years.
Then the strange things started (I think it was either sleep or a reboot. I don't remember exactly how did this happen).
My mbp lost the dim light, everything was dark. I pressed the dim lights, nothing changed.
Then, I pressed Command+Option+P+R and then reboot. Again strange lines appeared. Went to Safe mode (Command+S), I located Library/Extensions path to see if kexts files were back, but they were still missing. I expected them to be back.
I reboot again, saw strange lines, I pressed this time Command+S+R, and safe mode this time took a bit more to be ready. Checked again for kexts, still missing.
I was able to go to login page where dim lights worked again and it was bright as before. I didn't dare to login fearing it will freeze again, I shut it down for 20min (in order to do some research), but I decided to turn it on again. It worked normally until I ran up Whatsapp and got frozen 'till it rebooted by itself 1 min later.
Now I ran Command+S+R and I see kexts files being back.
Really weird. If someone knows why with Com+S the kexts files can't be seen but they can with Com+S+R, please shed a light.

@JMVB, first of all, honestly, thank you very much for you willing to help. That's very important.
(I hide the message below as it is not unrelated to the thread, and there is no point adding "reading noise")
However, only as I guess and please don't get offended, it seems you don't understand how reading thousands of comments can be a tedious and confusing process. I say this because you said "it is just a matter of a good search", and I think you have repeated to several other users that they should read all the comments.
To explain, over the years, I may have collected over than 100 useful comments and a good bunch of page bookmarks. I even tried a solution in the past (I don't remember which one) with no success.
Now, imagine a non very tech-savvy user, and get into his boots. Ok, I may know some unix, I am comfortable with some programming aspects, but in by no means I am an experienced user who may play on his fingers some parts of this world. And then, imagine me being desperate, I see a good bunch of articles saying "I did this and worked! Try this and everything is perfect!"
Which one should I follow? Which one should I try? Once, a user (Mike something) said "Many roads lead to Rome". Exactly.
Well, finding a working solution sometimes can feel like an utopia and reading so many different opinions can give you a misleading feeling (meaning that a solution may not be the right one for you). I have a 8.2 machine. You have a 8.3. I have a 17'', you have a 15'' display. Many different aspects and problems may show up, and it is enough to make you feel unsure. That's what was I meant that my message is pathetic.


next steps:
I noted down the EFI solution to be the next one to try, before I switch entirely the machine to permanently use LinuxOs instead of MacOs. The OSX I have (ElCapitan) is already dying and I am not even able to update some programs I use. For example, I am not allowed to install OneDrive (ok, in reality I found a workaround but you get what I mean), etc etc.
What scares me is the accidental nvram reset. If my mbp gets unbootable, I don't know what I should do if this happens. Ofcourse, I won't deliberately try it.
 
Hi all. I tried this method repeatedly, saw the green light but kept getting the same error message while trying to flash. I re-soldered a handful of times and finally I think I messed up one of the pads (third from the bottom). The laptop also has a black screen - no longer draws anything at all.

I've attached a screenshot. Is there anything I can do at this point? Or is it over :-(
 

Attachments

  • Photo 2021-02-07, 10 47 20.jpg
    Photo 2021-02-07, 10 47 20.jpg
    489.9 KB · Views: 304
@JMVB Yes but the EFI variable method does not survive a NVRAM reset. If you accidentally reset the NVRAM while R8911 is removed the system gets unbootable.
It is there a procedure to bring it back...
 
It is there a procedure to bring it back...
@JMVB, if you know a link, please post it! I am going to do this EFI attempt first thing when I find time to deal the problem with this solution.
Thank you very much
 
@JMVB, if you know a link, please post it! I am going to do this EFI attempt first thing when I find time to deal the problem with this solution.
Thank you very much
did you remove the r8911 and now have a blackscreen?
 
did you remove the r8911 and now have a blackscreen?
no, no.. Sorry. Perhaps I wasn't clear.
I am only planning ahead. Meaning that I haven't implemented any solution yet. (except the one I posted above -> angelofarina.it 's solutuon).
I just want to be prepared.
 
This "custom" pogo pin connector(?) for doing the flash, is this something we could make for ourselves, and perhaps easier than the soldering? Just curious.

I just learned about dosdude1 about a week ago, while preparing to update to highsierra using his patcher to find the full install.
Then saw his video with louis rossman, and I thought 'hey, sounds like their describing my previous issue with that model mbp" (it was fixed under the "recal" or whatever, replaced logic board).

Within a week of learning about this guy and his work with this issue, and now my computer's gpu appears to be dying again...great.

I've never soldered such small stuff before though, that would be a first so I'd do some practice tries first and probably even get a better soldering iron.
*sigh*...

I haven't read the whole thread, I got here from a link on Doslabs.

Many thanks to dosdude1, what a smart, helpful guy.
Thanks.
Some else has made a design that you can build yourself, which you can find here: https://oshpark.com/shared_projects/x8CMvEG2

It's a bit easier to assemble than my design, as the pogo pins on mine are extremely difficult to solder on straight (which is the main reason I've stopped selling them for the time being). You should be able to order the boards and listed parts to assemble your own.
 
  • Like
Reactions: Aguymac
Although we purchased our MBP17 new in early 2011, I'm brand new to the forum.

I don't get a lot of time for the internet, but the title of this @dosdude1 thread tells me that a lot of people are having [apparent] GPU problems just like we are.

The problem is that this thread is fairly old now, so how does one determine if the fix featured here is up to date?

I happened upon an interview last night in which the OP of this thread was indicating that this fix has evolved and/or improved. If anyone would kindly update me on the latest options for permanently repairing our MBP17, I would be most gratetful for the help. We simply cannot afford another MBP.

Thank you for your time...
 
Just a question to dosdude1:
I run your patch "MacBookPro dGPU Disabler" on my 2010 MBP 17" just to safe battery time. Now the MBP permanently accesses the internal screen via the nVidia-GPU as an external one with just a very poor graphic performance.
Can you tell me a way back? I've copied back the KEXT-files, deleted your launch demon, and performed an PRAM- and SMC-reset several times – without any changes.
Thanks a lot in advance for your efforts!
 
Just a question to dosdude1:
I run your patch "MacBookPro dGPU Disabler" on my 2010 MBP 17" just to safe battery time. Now the MBP permanently accesses the internal screen via the nVidia-GPU as an external one with just a very poor graphic performance.
Can you tell me a way back? I've copied back the KEXT-files, deleted your launch demon, and performed an PRAM- and SMC-reset several times – without any changes.
Thanks a lot in advance for your efforts!
You just need to re-apply the NVRAM variable shown on the webpage.
 
  • Like
Reactions: 0134168
Not sure if it was mentioned here but in case the flash fails - instead of removing L2406 You can ground PLT_RESET_L line (the easiest place is U2890), just don't forget to remove jumper after successful flash. It's easier
 
Last edited:
  • Like
Reactions: petttu and 0134168
I'm not able to flash the firmware sadly. I checked my wiring multiple times and also added the capacitor between TCK and GND line but it still fails every time... What can I do?

Connected to Lattice Cable Server. USB V2.0 detected. Check configuration setup: Start. File C:\Users\user\AppData\Local\Temp\28716\program\data\vmdata\database\xpga\xpld\XPLD.jed has been modified since last check.Default using the modified file. Device#1 LFXP2-5E: Failed to verify the ID (Expected: 0x01299043 Read: 0x00000000). Check configuration setup: Unsuccessful.
 
Not sure if it was mentioned here but in case the flash fails - instead of removing L2406 You can ground PLT_RESET_L line (the easiest place is U2890), just don't forget to remove jumper after successful flash. It's easier
Where can I find the U2890? Can you send me a picture of the exact location or how you bridged it?
 
I grounded PLT_RESET_L but used R2881 instead of U2890.

Luckily, the flash worked first try after i did that (I was short before pulling the TCK pad but fortunately it survived ;))
 
Some else has made a design that you can build yourself, which you can find here: https://oshpark.com/shared_projects/x8CMvEG2

It's a bit easier to assemble than my design, as the pogo pins on mine are extremely difficult to solder on straight (which is the main reason I've stopped selling them for the time being). You should be able to order the boards and listed parts to assemble your own.
Thanks DD. I'll check that out.

I'm writing this from a phone now, guess why..

For anyone reading this, not just DD, I have an important question.
In the YT interview DD did with Louis Rossman, they mention a 2012 MBP model that does NOT suffer from this GPU issue, despite having the same internals, and slightly higher power draw.

AT TIMESTAMP: 21:35, Louis says an identifier, from what I heard it was "A203330" (A two zero, thirty-three thirty).
Can anyone help me out with this MBP model, as maybe I can find a used one worth buying - ASAP.

I plan to attempt fixing this late 2011 8,2. I need to get the data/files off it - I hope they're still fine.. But I have a feeling it'll be over a month waiting for parts.

Does anyone know this 2012 model please?
While I'm at it, can anyone recommend any other well tested and proven specific year and model MBPs that I could perhaps find at a reasonable price, please?

Thanks for any assistance.

Edit: added timestamp for model mentioned.
 
Last edited:
Thanks DD. I'll check that out.

I'm writing this from a phone now, guess why..

For anyone reading this, not just DD, I have an important question.
In the YT interview DD did with Louis Rossman, they mention a 2012 MBP model that does NOT suffer from this GPU issue, despite having the same internals, and slightly higher power draw.

AT TIMESTAMP: 21:35, Louis says an identifier, from what I heard it was "A203330" (A two zero, thirty-three thirty).
Can anyone help me out with this MBP model, as maybe I can find a used one worth buying - ASAP.

I plan to attempt fixing this late 2011 8,2. I need to get the data/files off it - I hope they're still fine.. But I have a feeling it'll be over a month waiting for parts.

Does anyone know this 2012 model please?
While I'm at it, can anyone recommend any other well tested and proven specific year and model MBPs that I could perhaps find at a reasonable price, please?

Thanks for any assistance.

Edit: added timestamp for model mentioned.
It's an 820-3330 board. Fully compatible with all the 2011 MBP's components except for the LCD connector, which is slightly different. It is possible to bend it a bit to force the 2011 LCD connector into it, but a bit risky.
 
  • Like
Reactions: Aguymac
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.