Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

dosdude1

macrumors 68030
Feb 16, 2012
2,776
7,409
more problems after editing with mac A1286 mid 2010 of me.
1. Well it only worked until my computer went to sleep. Now back at gray screen
2. sometime broken image
3. When booting the machine has 15-30s load code system same as editing in command + S
What need I to do ? Please !
Mid 2010? Repair it properly. No need to disable the dedicated GPU. Disabling is only necessary on 2011 machines, that actually have a defective GPU.
 

giapson

macrumors newbie
Apr 7, 2017
6
1
Thanks bro. I did it.
Good things will come to you . :D
Hic hic. Something wrong
Chip Nividia GT 330M has died . And I want disrupt it . Now in System report-Graphics/Display it still exist .
I want a complete system stability .
Thanks bro. :D
 

dosdude1

macrumors 68030
Feb 16, 2012
2,776
7,409
@dosdude1 Would removing the R8911 resistor on the 2011 Macbook Pro fix the GPU problems including sleep/wake issues?
No. The ONLY way to disable the dedicated GPU and retain full sleep/wake functionality and brightness control in High Sierra and later is to use my hardware mod, plus my DyingLight module. I strongly recommend that you DO NOT remove R8911 if using the NVRAM variable fix, as when NVRAM gets reset or a system update is installed (both of which are inevitable), your display will stop working entirely.
[doublepost=1542177123][/doublepost]
Hic hic. Something wrong
Chip Nividia GT 330M has died . And I want disrupt it . Now in System report-Graphics/Display it still exist .
I want a complete system stability .
Thanks bro. :D
GT330M never dies, it's a quality nVidia chipset. The issue is a bad capacitor, just watch my video, and repair yours the same way. It will work 100% perfectly afterwards.
 
  • Like
Reactions: Matejh

caincha

macrumors member
Jul 15, 2012
63
7
Does a dead GPU do something with the battery or whatever?
My GPU seems to be on it's last legs - sometimes it works, something glitches and freezes - and now my laptop behaves as if it has no battery: cord always shows amber and if I pull it out the laptop dies…

Also, that code
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00

Looks like it's working - screen comes back to like, no glitches or anything - but it won't finish booting the system and not even boot from the installation disk either.
What gives…?
 

Dave111

macrumors newbie
Nov 1, 2018
24
4
No. The ONLY way to disable the dedicated GPU and retain full sleep/wake functionality and brightness control in High Sierra and later is to use my hardware mod, plus my DyingLight module. I strongly recommend that you DO NOT remove R8911 if using the NVRAM variable fix, as when NVRAM gets reset or a system update is installed (both of which are inevitable), your display will stop working entirely.
[doublepost=1542177123][/doublepost]
GT330M never dies, it's a quality nVidia chipset. The issue is a bad capacitor, just watch my video, and repair yours the same way. It will work 100% perfectly afterwards.

@dosdude1 Your hardware mod seems too complicated for my little brain. I probably shouldn't even try. Do you offer this service in your business? And thanks for the suggestion about not removing R8911!! I almost did :)
 

NewToMacPro2011

macrumors newbie
Jun 8, 2011
3
0
Thank you to MikeyN and everyone for their contributions. For some reason, and it wasn't a SMC/PRAM/NVRAM is reset, the changes made had to be redone using force-iGPU-boot.sh. No big issue. However, is there an easy way, beyond plugging in an external monitor to determine if the AMD GPU is off? Thanks again
 

caincha

macrumors member
Jul 15, 2012
63
7
Another weird thing happening to my system other than not recognising the battery: it won't boot into single user or verbose anymore and I get blue screen when trying to boot from USB Mavericks. Also it seems to be always OK when booting into online recovery - but I say 'it seems' because although the screen won't show any lines or glitches it gets stuck on white screen, doesn't actually go into recovery…
 

pmanalo21

macrumors newbie
Nov 17, 2018
2
0
@dosdude1

I have performed the hardware modification and the efi modifaction via the linux boot drive. I have succesfully used my macbook for quite a while. Until my airport card broke down and i called apple support for help. I unconciously performed a nvram reset as per their advise. Now my macbook boots with no video at all. Is there a way to fix this?
 

dosdude1

macrumors 68030
Feb 16, 2012
2,776
7,409
@dosdude1

I have performed the hardware modification and the efi modifaction via the linux boot drive. I have succesfully used my macbook for quite a while. Until my airport card broke down and i called apple support for help. I unconciously performed a nvram reset as per their advise. Now my macbook boots with no video at all. Is there a way to fix this?
I really hope you didn't remove R8911... Doing that is NOT the correct hardware modification. You need to fully bypass the gMux IC via hardware, so it doesn't rely on an NVRAM variable. Relying on an NVRAM variable to keep a hardware modification like this working is just stupid, I have no idea why people are recommending it. The only thing you can do now is re-install R8911, and set that NVRAM variable again. The best thing you can do, though, is perform a full gMux IC bypass, as I've detailed here. Performing this mod is permanent, and does not rely on any NVRAM variables that, as you've found out, can easily get reset.
 

Fried Chicken

Suspended
Jun 11, 2011
582
610
I have a 2011 Macbook Pro that's bricked. I applied this solution, but now the computer won't start. Pushing the power button gives me the Optical Drive noise, but no startup chime. The stays LED turns on and stays lit.

Does someone know what I can do? I might need to start an independent thread on this.
 

pmanalo21

macrumors newbie
Nov 17, 2018
2
0
I really hope you didn't remove R8911... Doing that is NOT the correct hardware modification. You need to fully bypass the gMux IC via hardware, so it doesn't rely on an NVRAM variable. Relying on an NVRAM variable to keep a hardware modification like this working is just stupid, I have no idea why people are recommending it. The only thing you can do now is re-install R8911, and set that NVRAM variable again. The best thing you can do, though, is perform a full gMux IC bypass, as I've detailed here. Performing this mod is permanent, and does not rely on any NVRAM variables that, as you've found out, can easily get reset.

Yep. R8911 removed. How do i exactly restore it as i dont have the resistor anymore. Or should i just try to the gmu ic?
 

erebos007

macrumors newbie
Oct 26, 2018
12
2
I put a link to the wire I used in the post, but it is 0.1MM enamel coated wire.

Just a quick update, I managed to perform the gmux bypass hardware mod and now the mbp is working as intended, so thank you very much dosdude1 ! All I need is to make a DyingLight now :D
 
Last edited:

prisstratton

macrumors 6502a
Dec 20, 2011
543
127
Winnipeg, Manitoba, Canada
Hi Everyone,

Well, my MBP finally bit the bullet last week, but, I would like to thank all of you that worked on or added to this fix as it has allowed me to keep using my Mac……….THANK YOU.

I wanted to post my experience’s with these fixes in case someone is in the same situation as I was.

I had a firmware password set, so this did not allow me to boot into single user mode. I was also unable to boot into a regular session or recovery mode. I therefore had to go with the Linux option. I followed the instructions and after a few missteps I was able to complete. The system would actually boot after this, but the fans would run very hard and the system would just reboot endlessly. But, it did allow me to boot into recovery, once in recovery I removed the firmware password and then booted into single user mode. I then followed the guide as provided by @MikeyN (post # 875) and I now have a working system.

Again, many thanks to everyone that contributed to this thread, all of your experiences do help. Two thumbs up !!
 

Dave111

macrumors newbie
Nov 1, 2018
24
4
Hi Everyone,

Well, my MBP finally bit the bullet last week, but, I would like to thank all of you that worked on or added to this fix as it has allowed me to keep using my Mac……….THANK YOU.

I wanted to post my experience’s with these fixes in case someone is in the same situation as I was.

I had a firmware password set, so this did not allow me to boot into single user mode. I was also unable to boot into a regular session or recovery mode. I therefore had to go with the Linux option. I followed the instructions and after a few missteps I was able to complete. The system would actually boot after this, but the fans would run very hard and the system would just reboot endlessly. But, it did allow me to boot into recovery, once in recovery I removed the firmware password and then booted into single user mode. I then followed the guide as provided by @MikeyN (post # 875) and I now have a working system.

Again, many thanks to everyone that contributed to this thread, all of your experiences do help. Two thumbs up !!

Seems like the best way to go. Congrats!!
 
Last edited:

tony359

macrumors member
Oct 23, 2018
89
22
Dave,

dosdude's solution is permanent and will likely survive any upgrade or reset. It's clearly not for the faint hearted! I went for the software mod because 1. it was not my macbook 2. I felt that before attempting hardware mods, the SW one was worth a try. I ended up - so far - with a 100% working system but I appreciate that Apple may screw that up with future updates. Thankfully ;) there are no more OS updates for this model!!
 

Dave111

macrumors newbie
Nov 1, 2018
24
4
Dave,

dosdude's solution is permanent and will likely survive any upgrade or reset. It's clearly not for the faint hearted! I went for the software mod because 1. it was not my macbook 2. I felt that before attempting hardware mods, the SW one was worth a try. I ended up - so far - with a 100% working system but I appreciate that Apple may screw that up with future updates. Thankfully ;) there are no more OS updates for this model!!

@tony359 How did you manage to do all that?? It seems too complicated for me and that's why I even asked him if he does that repair but he won't respond. I really don't wanna even try doing it myself because at least with the linux fix my mac is working and I don't wanna end up bricking it.

And you're right, there's no more upgrades to the OS but what about security updates? Don't know if they get accepted without issues..
 

giapson

macrumors newbie
Apr 7, 2017
6
1
No. The ONLY way to disable the dedicated GPU and retain full sleep/wake functionality and brightness control in High Sierra and later is to use my hardware mod, plus my DyingLight module. I strongly recommend that you DO NOT remove R8911 if using the NVRAM variable fix, as when NVRAM gets reset or a system update is installed (both of which are inevitable), your display will stop working entirely.
[doublepost=1542177123][/doublepost]
GT330M never dies, it's a quality nVidia chipset. The issue is a bad capacitor, just watch my video, and repair yours the same way. It will work 100% perfectly afterwards.
Thanksk bro . I understand. But i need a solution for my case. I can remove chip GT330m or do something to disconnected driver Nvidia GT330 out of the system graphichs .
Thanks bro .....
 

dosdude1

macrumors 68030
Feb 16, 2012
2,776
7,409
Thanksk bro . I understand. But i need a solution for my case. I can remove chip GT330m or do something to disconnected driver Nvidia GT330 out of the system graphichs .
Thanks bro .....
No, you do not. Replace that capacitor, and it will work perfectly fine.
 

cyki

macrumors newbie
Mar 6, 2018
4
0
Last night I've updated to 10.13.6 (17G3025) and seems that CMD + S + R shortcut brings you to GUI, where you can still disable SIP via Terminal.app. After this update my SSD that is placed in primary SATA and HDD in CD-Rom slot was somehow not recognised but OPT + CMD + P + R fixed that. During boot right after the update I got the circle with crossed line like when your system is gone.
What was different this time that AMDRadeonX3000.kext which came with the update was different and could not be loaded after boot to prevent overheating:
Code:
macbook:~ root# /sbin/kextload /backup2/AMDRadeonX3000.kext/
/backup2/AMDRadeonX3000.kext failed to load - (libkern/kext) not found; check the system/kernel logs for errors or try kextutil(8).

So I tried to load the old kext which worked, files are different in new kext so apparently Apple did some mambo jambo with drivers. hopefully it will continue working even with old kext loaded...

Although my MBP gets frozen from time to time especially during sleep, I am incredibly happy for IT geeks who saved us a big bunch of money, thank you for this solution! I got replaced motherboard three times and the last fourth failure was supposed to be last nail in a coffin for Apple laptops, seems I will delay my hammer a bit..
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.