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.
Thanks @dosdude1 (and @BookEmDanno on a later similar post). I did find the cable disconnected. So i re-attached the cable, and upon powering off, both bluetooth and camera are now recognized and working. However, my WiFi is showing on the menubar with an "x" and drop down says "WiFi: No hardware installed".
System report does show software wifi 13.0.

Thanks for additional suggestions.

My WiFi is now LIVE! again on my mojave un-supported MBP5,5. Perhaps just got into a good karma. Didn't use this mac for a couple of days or so. Then all of a sudden .... :p
 
  • Like
Reactions: TimothyR734
APFS ROM Patcher error

I intended to patch my un-supported MBP5,5 to convert my High Sierra and Mojave partitions from HFS+ to APFS boot. Ran @dosdude1's APFS ROM patcher and tried the following steps:
  1. Initial run of the patcher correctly identified the model of my MacBookPro5,5.
  2. Got into "Firmware Programming Mode" by taking the necessary steps (a) shut down system (b) waited 15 seconds (c) press and hold power button until LED begins flashing rapidly.
  3. Re-ran patch updater and click continue.
  4. Entered password.
  5. Got the following messages:
Kext Error
DirectHW.kext could not be loaded. The operation cannot proceed.

Suggestions on fixing this or are there any additional steps or requirements missing?

Thank You.
 
  • Like
Reactions: TimothyR734
APFS ROM Patcher error

I intended to patch my un-supported MBP5,5 to convert my High Sierra and Mojave partitions from HFS+ to APFS boot. Ran @dosdude1's APFS ROM patcher and tried the following steps:
  1. Initial run of the patcher correctly identified the model of my MacBookPro5,5.
  2. Got into "Firmware Programming Mode" by taking the necessary steps (a) shut down system (b) waited 15 seconds (c) press and hold power button until LED begins flashing rapidly.
  3. Re-ran patch updater and click continue.
  4. Entered password.
  5. Got the following messages:
Kext Error
DirectHW.kext could not be loaded. The operation cannot proceed.

Suggestions on fixing this or are there any additional steps or requirements missing?

Thank You.
Have you checked that SIP is still turned off?
 
You cannot disable the discrete GPU on a Mac Mini. That's only possible on the MacBook Pro, because it has dual-GPU switching (gMux). The Mac Mini does not, it uses only the dedicated GPU.
Thanks a lot for the information. So it means that i will remain stuck with High Sierra from now on I guess. Or is it possible to install Mojave in my Mac Mini mid 2011 even if I have an AMD card on it?
 
Last edited:
  • Like
Reactions: TimothyR734
Any ideas of how to get all QE (quartz composer) screensavers to work again? I have installed some 3rd party "iOS Lockscreen" saver and cannot get it to run under Mojave. Error message displayed instead of content...
 

Attachments

  • Screenshot 2018-08-19 at 12.41.24.png
    Screenshot 2018-08-19 at 12.41.24.png
    195.6 KB · Views: 145
  • Like
Reactions: TimothyR734
Any ideas of how to get all QE (quartz composer) screensavers to work again? I have installed some 3rd party "iOS Lockscreen" saver and cannot get it to run under Mojave. Error message displayed instead of content...

Same here. Found a nice flying toaster clone and it worked just fine with HS but now I get the same error message.
 
  • Like
Reactions: TimothyR734
APFS ROM Patcher error

I intended to patch my un-supported MBP5,5 to convert my High Sierra and Mojave partitions from HFS+ to APFS boot. Ran @dosdude1's APFS ROM patcher and tried the following steps:
  1. Initial run of the patcher correctly identified the model of my MacBookPro5,5.
  2. Got into "Firmware Programming Mode" by taking the necessary steps (a) shut down system (b) waited 15 seconds (c) press and hold power button until LED begins flashing rapidly.
  3. Re-ran patch updater and click continue.
  4. Entered password.
  5. Got the following messages:
Kext Error
DirectHW.kext could not be loaded. The operation cannot proceed.

Suggestions on fixing this or are there any additional steps or requirements missing?

Thank You.

I had the same issue . what solved it for me was to take a spare ssd and do a clean install of high sierra and patch it with dosdudes HS installer as normal SIP disabled etc. Then i followed the steps you have outlined above and all worked. I would stress that you check which type of chip is on your board so you don't brick it . I have patched a 5,3 and 5,5 and both were MX25L3205D . Its important you select the right one . Good luck
 
Could we agree on not YELLING IN RED BOLD LETTERS on the wiki page (#1) of this thread?
I´ve tried to pipe it down a grade or two, but got overwritten soon after.
imho it´s not very helpful anyway to put such focus on one of the many side issues (here: the ROM patcher) of getting Mojave installed on our unsupported machines.
Quite right, it looks awful, people with Macs are supposed to have taste, well they certainly used to, now Apple just sell to anyone, it's disgraceful.
 
Could we agree on not YELLING IN RED BOLD LETTERS on the wiki page (#1) of this thread?
I´ve tried to pipe it down a grade or two, but got overwritten soon after.
imho it´s not very helpful anyway to put such focus on one of the many side issues (here: the ROM patcher) of getting Mojave installed on our unsupported machines.

Fixed it and changed the language a bit.
 
@dosdude1, is it possible to get the backup of my ROM if it got deleted? My HDD corrupted yesterday and I had to start from scratch. Is it possible to repatch my ROM and get a new backup or something of that sort or am I out of luck?
 
  • Like
Reactions: TimothyR734
Any ideas of how to get all QE (quartz composer) screensavers to work again? I have installed some 3rd party "iOS Lockscreen" saver and cannot get it to run under Mojave. Error message displayed instead of content...

I have no idea but I like tinkering with stuff, upload a copy of the QTZ file and I'd take a quick look (QuickLook?) at it :)
 
@dosdude1, is it possible to get the backup of my ROM if it got deleted? My HDD corrupted yesterday and I had to start from scratch. Is it possible to repatch my ROM and get a new backup or something of that sort or am I out of luck?
Once the ROM is patched, it's patched... If you were to run the patch again, the backup would become your patched ROM. If the system is working fine, though, I wouldn't worry about it. You most likely will never need to flash the backup ROM.
 
Once the ROM is patched, it's patched... If you were to run the patch again, the backup would become your patched ROM. If the system is working fine, though, I wouldn't worry about it. You most likely will never need to flash the backup ROM.

Maybe you shouldn’t allow the patch to be run twice. If the backup is corrupted that’s not good even if it shouldn’t need to be used.
 
  • Like
Reactions: TimothyR734
Has anyone ran the APFS Patcher on a MacBook Pro 5,4? I'm weary of trying it.
The key is to identify your eeprom model and number precisely.
The rom patcher may not be able to recognize your rom, in which case you'll possibly get a list of options to choose from. A mistake there will be costly and will probably brick your device.

If you want I can look for your board schematic and post it? I've already done so for two other models here.
Just send me a screenshot of your model and make ("About this mac" screen) Unless someone knows what your eeprom should be already.

As always, read as many of the rom patcher posts here and heed all the warnings. Good luck.
 
  • Like
Reactions: jackluke
Maybe you shouldn’t allow the patch to be run twice. If the backup is corrupted that’s not good even if it shouldn’t need to be used.
It warns you if a backup is already saved.
[doublepost=1534706165][/doublepost]
The key is to identify your eeprom model and number precisely.
The rom patcher may not be able to recognize your rom, in which case you'll possibly get a list of options to choose from. A mistake there will be costly and will probably brick your device.

If you want I can look for your board schematic and post it? I've already done so for two other models here.
Just send me a screenshot of your model and make ("About this mac" screen) Unless someone knows what your eeprom should be already.

As always, read as many of the rom patcher posts here and heed all the warnings. Good luck.
The schematic won't tell you the model EEPROM the board has. I've seen the same model board use different EEPROMs in many machines. The ONLY way to tell for sure is to look at it yourself... It's pretty easy to spot, as it will always be the largest TSOP8 chip on the board.
 
It warns you if a backup is already saved.
[doublepost=1534706165][/doublepost]
The schematic won't tell you the model EEPROM the board has. I've seen the same model board use different EEPROMs in many machines. The ONLY way to tell for sure is to look at it yourself... It's pretty easy to spot, as it will always be the largest TSOP8 chip on the board.
You're right. I was just checking on his board and it is the same as mine A1286 (i posted previously) so the only way is for @videotape74 to open his box. Can you give him some tips on where it would be located - I think it's located on the reverse side but not sure.

Edit: I think flipping the board may only be valid for macbook's. macbook pro eeproms should be located on the top right? the diagram worked for me so I never opened my laptop.
 
Last edited:
did you try dosdude1's APFS Rom patcher on the OP

It should not be required, the 8,2 supports APFS natively, and the drive is completely accessible when the machine is booted into HS.

Edit: A clean install to an APFS formatted drive works flawlessly, but an in-place conversion from HPFS+ fails to yield a bootable system.
 
Last edited:
  • Like
Reactions: TimothyR734
The key is to identify your eeprom model and number precisely.
The rom patcher may not be able to recognize your rom, in which case you'll possibly get a list of options to choose from. A mistake there will be costly and will probably brick your device.

If you want I can look for your board schematic and post it? I've already done so for two other models here.
Just send me a screenshot of your model and make ("About this mac" screen) Unless someone knows what your eeprom should be already.

As always, read as many of the rom patcher posts here and heed all the warnings. Good luck.

thanks to @pkouame & @dosdude1 if it requires removing the motherboard, I will hold off...not quite that comfortable, but thanks for the info!
 
  • Like
Reactions: TimothyR734
Just wanted to let you guys know that I am not seeing the graphics anomalies as described in the in the ops initial post on my Early 2011 Macbook Pro 15 (8,2) using the latest patcher tool and latest developer preview.

I did however have the graphics issues using the earlier tools. @dosdude1 Thanks for your genius mind!!!
 
  • Like
Reactions: TimothyR734
Light Mode bug

Anyone getting this error message in their console log when switching (in General Preferences) from Dark to Light mode on unsupported non-metal machine (with Light mode glitches)?

Code:
default    13:44:48.637108 -0400    WindowServer    SetFrontProcessInternal(0x0,0x16d16d pid4127) Posting kCGSEventResume to application, allWindows=0 noWindows=0 userGenerated=0.
default    13:44:48.668767 -0400    contextstored    27366555: RECEIVED OUT-OF-SEQUENCE NOTIFICATION: 0 vs 132, 513, <private>
error    13:44:48.665288 -0400    System Preferences    Unable to load Info.plist exceptions (eGPUOverrides)

This does not happen when switching from Light to Dark.

Thanks.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.