macOS 10.14 Mojave on Unsupported Macs Thread

[bmillz]

Hmmm that ebay seller robbed me..lol that the same laptop I ask you about concerning the trackpad on high sierra... early 2008 my ass..anyway I have a broadcom broadcom bcm94313hmg2l from a lenovo..maybe that would work or an atheros AR5B225 from a samsung...

I swapped the WiFi card out of my MacBook Pro 4,1 all the way back when Sierra came out because it did not support the WiFi card installed. I switched it out with the WiFi card I had from a Late 2006 MBP that I had laying around (Atheros like yours). It did work fine, no patches needed, until Mojave. However, I did get it to work again by installing the WiFi patch in the post install tool. I then installed it manually again with the patch updater in Mojave and it works flawlessly again. Make sure you rebuild the cache after install in the post install tool. Try it and see if it works.

 

[TimothyR734]

@dosdude1 My MacBookPro 7,1 loses access to my bottom RAM slot after rebooting, is the slot broken? Seems to come back randomly. Now I only have 2GB, also have when my Mac is in sleep it can't wake, I have to force shut it down?

What you could do is if you have access to your ram pull the chips out and use a eraser tip of a pencil gently rub the gold parts at the boot of the ram chip then gently wipe off with a soft cloth

 

[PianoPro]

Does anyone know if the video card drivers from Mojave can be used in High Sierra? I bought a MSI RX-560 card (one of the 2 cards officially supported for Mojave in a 2010 Mac Pro) and it works very well in the PB Mojave, but it has significant problems in HS, both when performance stressed and when the Civ4/5 game's 1080p full-screen mode is used (under no stress).

I notice the AMD drivers are a different version in Mojave than HS (version 2.0.36 Aug 23, 2018 versus version 1.68.20 Jun 29 2018 for HS). I'm thinking the Mojave versions may have been optimized/fixed for using the RX-560 in the 2010 Mac Pro because that card is officially supported, but not in the HS versions because it's not officially supported. I don't know which of the Mojave AMD drivers (listed below) would apply to the RX-560 card. Can anyone advise if its possible to copy and paste them into HS, and which drivers would apply to this card?

 

[DaniloGeekDude]

Is your hdd or ssd formatted APFS if its HFS you wilt get the update through the software update

My Mojave boot partition is APFS. I thought it was the other way around - software update if APFS, install and patch if HFS+. Anyways, I went ahead and did the install/patch process to implement the update.



Thank You @TimothyR734!

 

[visberry]

What you could do is if you have access to your ram pull the chips out and use a eraser tip of a pencil gently rub the gold parts at the boot of the ram chip then gently wipe off with a soft cloth

It detects them sometimes - has sleep issues can’t wake it sometimes.

 

[AnonMac50]

Nope, two reasons.

First, every Mac that has Internet Recovery, has a SPI flash memory of at least 8MB, old Macs have 2 or 4MB FWB/SPI flash memory. Second, Internet Recovery uses the Mac hardware ID to download the images from Apple, if your hardware ID is not there…

Ah I see, thanks for clearing that up!

 

[SDAVE]

Oh that's why, you have a MBP 15" dual GPUs IntelHD3000 and AMD/ATI 6xxx series, you need to use the original AMD/ATI kexts in order to have the brightness/sleep functions.

While I can assure if you install correctly mine patched IntelHD3000 VRAM (through KextUtility in your case), they will work and will not affect in any way the brightness/sleep, you just need the stock backup AMD6xxx kext for enabling that, I meant you need the patched AMD6xxx kext based on AMDRadeonX3000 Framebuffer.

However I guess your issues depend mainly from not correctly installing the patched kext and generating the kextcache, instead of KextUtility, better using these commands from Mojave Terminal:

sudo -s

chown -R 0:0 /S*/L*/E* && chmod -R 755 /S*/L*/E*

kextcache -i /

reboot

edit:
Probably to use QE/CI and VRAM patch with your IntelHD3000 you need to disable totally the AMD/ATI GPU.

Are you sure you used the dosdude1's vram command booting from your Mojave Volume in single user mode (holding CMD+S) after power-on ?
Typing correctly any single character (since obviously you can't copy/paste in single user mode) ?
After done have you used the dGPU Disabler app suggested by dosdude1?

Thanks for that.

What's weird is if I put back the amd kexts in S/L/E and do what you said above (manually or with Kext Wizard) upon reboot brightness works, but then the kexts are automatically deleted from S/L/E?

Then another restart the brightness doesn't work..

 

[jackluke]

Upgraded from DP9 to DP10 my iMac 10,1 using Software Update from System Preferences. The installation was rather fast. Had again the endless boot loop. Solved using the usual, booting from the USB stick with the Mojave Patcher. Open Terminal

rm -r /Volumes/Mojave/SystemLibrary/Extensions/*IOUSB*
cp -a /Volumes/macOS/SystemLibrary/Extensions/*IOUSB* /Volumes/Mojave/System/Library/Extensions/

Then close Terminal. Run Mojave Post Install tool and reinstall only USB related patches. Reboot with force cache rebuild.

Good suprise with DP10: my iSight is again working

For night Shift i applied



After unziping the downloaded file :

xattr -d com.apple.quarantine CoreBrightness

Then I installed it :

sudo cp CoreBrightness /System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/

Night Shift started to work immediately. The only glitch is that i can only use with Custom Schedule. Trying to set it to "Sunset to Sunrise", opens a window asking location for time zone to be enabled. Opening Privacy Preferences does not solve as Time Zone & System Customisation is already checked

To me (Mojave beta 9) it's working, try this open System Preferences / Security and Privacy / Privacy
now click on the lower-left lock and type your user admin password.
Select Enable Location Services, then click Details... near System Services, when inside select all the checkboxes (they are 8). Now Night Shift "Sunset to Sunrise" should work.

 

[olad]

Has anyone downloaded the Installer from dosdude1's Mojave Patcher? Is it the DP10? The reason I ask is that if I download that, I can use it on all 3 laptops I have - 2 unsupported, 1 supported. No point in downloading thru the updates when I can use one installer on all of them. Thanks.

 

[jackluke]

Turns out Siri cannot change Night Shift on my patched MacBookPro 7,1 on macOS High Sierra. By the way, thanks @jackluke for the patcher.

Most probably Siri services are based on the Mac Serial number or machine platform (Night Shift) supported ids, so that's why she can't find the Night Shift switch button.
[doublepost=1536134844][/doublepost]

My Mojave boot partition is APFS. I thought it was the other way around - software update if APFS, install and patch if HFS+. Anyways, I went ahead and did the install/patch process to implement the update.

View attachment 779729

Thank You @TimothyR734!

I guess some issues are due to the APFS "software" EFI script patch, you'd need the risky APFS "hardware" EEPROM EFI Patch to use correctly the Mojave system update.

[doublepost=1536137371][/doublepost]

@dosdude1 My MacBookPro 7,1 loses access to my bottom RAM slot after rebooting, is the slot broken? Seems to come back randomly. Now I only have 2GB, also have when my Mac is in sleep it can't wake, I have to force shut it down?

If you upgraded RAM recently be sure that at least one of two sticks is:
DDR3 PC3-8500 • CL=7 • Unbuffered • NON-ECC • DDR3-1066 Mhz

 

[scrub10rd]

has anyone gotten the APFS patcher (hardware one) to work on the Macbook5,2?

 

[Rand0mUserNam3]

I can confirm that my mac board ID is contained in the SupportedBoardId list and my model number is also contained within the SupportedModelProperties list. Still won’t successfully boot with these values present.

Success!

I managed to successfully patch and boot from my internal drive by using a bootable external volume to allow me to access the internal drive and clean out the the system extensions folder, leaving only the default extensions. I had acquired many extensions over the years from app installs, all of which were unnecessary and one or more of them were the cause of my kernel panic at boot.

So if you are having issues at boot, it is worth clearing out unneeded files from your system folder, using a fresh install as a reference.

Thanks for the help everyone.

 

[thegurgz]

Has anyone downloaded the Installer from dosdude1's Mojave Patcher? Is it the DP10? The reason I ask is that if I download that, I can use it on all 3 laptops I have - 2 unsupported, 1 supported. No point in downloading thru the updates when I can use one installer on all of them. Thanks.

Yes, it's DP10. Downloaded and installed last night on my MBP 5,5, build 18A384a installed.

 

[dosdude1]

@dosdude1 My MacBookPro 7,1 loses access to my bottom RAM slot after rebooting, is the slot broken? Seems to come back randomly. Now I only have 2GB, also have when my Mac is in sleep it can't wake, I have to force shut it down?

Yes, the slot is bad, most likely. Open the system and try reseating the memory modules first, though, and see if that helps at all.
[doublepost=1536155041][/doublepost]

Thanks for that.

What's weird is if I put back the amd kexts in S/L/E and do what you said above (manually or with Kext Wizard) upon reboot brightness works, but then the kexts are automatically deleted from S/L/E?

Then another restart the brightness doesn't work..

The reason for that is my tool that you've most likely installed. Just delete /Library/LaunchDaemons/com.dosdude1.dGPUDisableHelper.plist.

 

[StratUk]

I've been "playing" with Mojave and HDDs (since I can't afford a SSD) on my Mac Pro 3.1 with some interesting (for me) results.

1. A HDD can be formatted as APFS, clean installed and booted (using the patched ROM without the post-install software patch).
2. Initial boot to recognizing the HDD is very, very slow (over 60 seconds), whereas it was under 10 seconds for HFS.
3.Performance is significantly lower than it was with HFS on the same drive offering copy times of 30GB files of over 30 minutes as opposed to 6 to 7 minutes for HFS
4. Decided to try to use Migration Assistant to Migrate my current High Sierra setup - so excruciatingly slow (150 GB of 1.5TB after 10 hours - the usual time it take on HFS) I gave up and rebuilt as APFS.
5. I initially installed Beta 9 and checked several times over a day for the Software Update - it still says up to date.

In conclusion I think I'll stick with HFS and manually apply updates from the full install.

 

[jackluke]

I've been "playing" with Mojave and HDDs (since I can't afford a SSD) on my Mac Pro 3.1 with some interesting (for me) results.

1. A HDD can be formatted as APFS, clean installed and booted (using the patched ROM without the post-install software patch).
2. Initial boot to recognizing the HDD is very, very slow (over 60 seconds), whereas it was under 10 seconds for HFS.
3.Performance is significantly lower than it was with HFS on the same drive offering copy times of 30GB files of over 30 minutes as opposed to 6 to 7 minutes for HFS
4. Decided to try to use Migration Assistant to Migrate my current High Sierra setup - so excruciatingly slow (150 GB of 1.5TB after 10 hours - the usual time it take on HFS) I gave up and rebuilt as APFS.
5. I initially installed Beta 9 and checked several times over a day for the Software Update - it still says up to date.

In conclusion I think I'll stick with HFS and manually apply updates from the full install.

Agree, SSDs with more than 1TB capability are still a bit expensive, APFS is not best suited for "spinning hdds" that's why have slower performance, so HFS+ is preferable and luckily still possible with Mojave.

However I had similar slowing recognizing on a supported Mac of some SSD vendor (ex. Samsung EVO) before booting the OS system, it tooks about 10 seconds after the power-on chime, so that's depend probably from not-best compatibility between the SSD Controller and main logic board controller, while the same SSD is quickly identified on some older machines but not on other similar ones.
So it's very important before buy a Tera sized SSD to be sure of it's 99% compatibility.

For best compatibility on very old unsupported machines (here supported to Mojave), Marvell SSD Controller results the main one that allow the full "Negotiated Link Speed", that is one of the most important feature to check when swapping a spinning disk with a SSD into an old Mac (apart the hdd temperature sensor for the iMacs). To check also from Terminal:
system_profiler SPSerialATADataType

Here are the most popular and widespread SSD controllers: https://en.wikipedia.org/wiki/List_of_flash_memory_controller_manufacturers

 

[mnsiw]

Hi I'm running 18A326h on MacBook5,1, any suggestion about updating to 18A384a, System Update not showing any update

 

[0403979]

After Xcode Command Line Tools are installed:

sudo codesign -f -s - <path_to_mac_binary_exec>

@dosdude1 I still have a question;
Is it possible to block specific system files (kext, framework, etc) to not be changed upon macOS update?
For example, preventing pre-installed /S*/L*/E*/AppleHDA.kext to be replaced by Update Process. Thanks.

Will this fix codesigning issues on all applications?

 

[Badruzeus]

Will this fix codesigning issues on all applications?

Not trying yet with all apps here #LoL

 

[jackluke]

hey @pkouame , since with your hybrid light/dark mode you're already inside the Appkit.framework Xcode's code, take a glance here:

https://developer.apple.com/documentation/appkit/nsvisualeffectview

https://stackoverflow.com/questions...style-view-with-translucent-blurry-background

It may help for yours experiments.

I've noticed that the "transparency effect" into Finder menu bar, Finder side bar, Safari Favorites background, are essentially "blur opacity", that in Mojave "light mode" OpenGL case glitch to a solid dark grey color.

I suppose that this function that handles with "blurs" could be the key:
https://developer.apple.com/documentation/appkit/nsvisualeffectview/1535468-blendingmode

edit:

Moreover, left "Vibrancy" on the side, patching the Appkit.framework, are you able to "paint" with NSColor function the finder menu bar into another color for ex. white or blue?

Or another workaround, could you try "reducing transparency" setting 0% opacity only into the finder menu bar main color? (In order to keep all the other transparencies Dock, Notification Center, Application "comic window" etc.)

I've done some attempts to isolate the transparency/opacity but I guess that these are not related to the CoreServices's "Finder.app".

 

[olrik77]

Bonsoir,

Success with the last PB on my MacPro 3,1 :

All is running fine !

Merci Dosdude1, Pkouame, Jhowarth, Jackluke and all of you !

PJN

 

[visberry]

Most probably Siri services are based on the Mac Serial number or machine platform (Night Shift) supported ids, so that's why she can't find the Night Shift switch button.
[doublepost=1536134844][/doublepost]

I guess some issues are due to the APFS "software" EFI script patch, you'd need the risky APFS "hardware" EEPROM EFI Patch to use correctly the Mojave system update.

[doublepost=1536137371][/doublepost]

If you upgraded RAM recently be sure that at least one of two sticks is:
DDR3 PC3-8500 • CL=7 • Unbuffered • NON-ECC • DDR3-1066 Mhz

I didn’t upgrade RAM

 

[jackluke]

I didn’t upgrade RAM

Try one at once in the same slot, and then again one at once in the other slot.
In this way you could check if one ram stick is becoming defective, even if it occurs rarely.

It depends on how much saturation you have on all the physical RAM available, once happened to me that a faulted 4 GB DDR3 SODIMM stick was working until 2/3 GB RAM and then after passing that threshold the system freezed itself or KP. Changing the stick fixed my issues.

Otherwise as per dosdude1's opinion, if you used too much force putting stick some slot's pins are gone.

 

[visberry]

Try one at once in the same slot, and then again one at once in the other slot.
In this way you could check if one ram stick is becoming defective, even if it occurs rarely.

It depends on how much saturation you have on all the physical RAM available, once happened to me that a faulted 4 GB DDR3 SODIMM stick was working until 2/3 GB RAM and then after passing that threshold the system freezed itself or KP. Changing the stick fixed my issues.

Otherwise as per dosdude1's opinion, if you used too much force putting stick some slot's pins are gone.

This seemed to just happen, it detects 2GB of RAM, when in fact I have 4GB of RAM. I have never touched the RAM until the issue occurred and never opened it with the exception of installing an SSD way back. It has been slow for a while but it never came across as it is the RAM, and I guess I now just realized because I do not check my "About This Mac" screen daily.

Not it is detecting 2GB as I said, and it says the second slot is Empty. Sometimes, it detects it, but after swapping them around and leaving either in the bottom it beeps on startup. Placing one in the top always works. Would I get away with leaving the bottom open and having 4GB/8GB in the top slot without any issues?

 

[jackluke]

This seemed to just happen, it detects 2GB of RAM, when in fact I have 4GB of RAM. I have never touched the RAM until the issue occurred and never opened it with the exception of installing an SSD way back. It has been slow for a while but it never came across as it is the RAM, and I guess I now just realized because I do not check my "About This Mac" screen daily.

Not it is detecting 2GB as I said, and it says the second slot is Empty. Sometimes, it detects it, but after swapping them around and leaving either in the bottom it beeps on startup. Placing one in the top always works. Would I get away with leaving the bottom open and having 4GB/8GB in the top slot without any issues?

If you never touched or forced the putting, it's weird, the startup beeps could indicate also faulty RAM, anyway, using only one 4/8 GB stick acknowledged it's rigorously a 204pin SO-DIMM DDR3 PC3-8500 CL7 Non-ECC Unbuffered 1.5V (or 1.35V), yes you can.