I guess your printer is indeed very old + your MBP 2011 is maybe too recent for your printer.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.14 Mojave on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I guess your printer is indeed very old + your MBP 2011 is maybe too recent for your printer.
Hello. Is it posible to install (patch) MacBook 4,1 (early 2008) to OS Mojave according to MacOS Extractor 1.45 (Beta 1) release notes. They said: ◦ macOS 10.12-10.14 Support for MacBook 4,1 (In Next Betas)...
Has anyone tried, and how to access to the discord app to try it?
I need to upgrade it because im stuck with OS Lion
Tnx
Has anyone tried, and how to access to the discord app to try it?
I need to upgrade it because im stuck with OS Lion
Tnx
Hello there (
)
what's with the supplemental update, is it ok to update? (MacBook Pro 13' late 2011)
)what's with the supplemental update, is it ok to update? (MacBook Pro 13' late 2011)
Hi
iMac late 2009 (10,1) OK with 10.14.6 supplemental update direct from software update, without patching again.
Cheers !
iMac late 2009 (10,1) OK with 10.14.6 supplemental update direct from software update, without patching again.
Cheers !
Yes, it's oké to update. But keep for safety always a usb patcher stick available.Hello there (
what's with the supplemental update, is it ok to update? (MacBook Pro 13' late 2011)
Thanks for the link. I read through and double checked my settings, but everything looks to be set correctly. I have hibernate mode set to 25, but when I put my computer to sleep, it does not write out the RAM contents to disk and power off. Instead it goes into normal sleep mode.
Macbook pro 13 mid 2010 running wonderfully well.
Congratulations to dosdude1 and those involved in the fantastic work, it's magical to be exact!
I found, after a lot of research, that the numbering format of Boot ROM has changed. So from what I saw, the information Boot ROM: 66.0.0.0.0 is the most current.
https://forums.developer.apple.com/thread/110339
https://eclecticlight.co/2018/10/31/which-efi-firmware-should-your-mac-be-using-version-3/
https://eclecticlight.co/2018/10/31...2018-002-and-sierra-security-update-2018-005/
I hope this information can help someone who also has the same question about updating the ROM.
I tried to apply the supplemental patch through normal settings/update and it froze at 16%. I just restored to the latest without the patch. Am I the only one who has trouble? I guess I can try again if it’s just me or I can just download the full install and go over it.
Was this the final realase?
Was this the final realase?
I reinstalled 10.14.6 and applied your patches (again). Wi-Fi worked this time, so I didn't need to re-apply the patches. I must have done something wrong during the first 10.14.5 -> 10.14.6 upgrade / patch, but I'm not sure what. Anyway, this old HackBookPro4,1 with Atheros Wi-Fi runs 10.14.6 perfectly! Thank you.
You can install it with macOS Patcher 2.4 (link in my bio). It's been tested and confirmed to work by a few people, including me (the developer).
@dosdude1 I have checked the patch for updates, it is listed that no updates were available. That is strange, since I have not installed all the components of the patcher, not being necessary, and always those components were offered for installed. Also checked the installed components of the patcher, none were listed. It is a bug somewhere.
I'm having issues on MacBook Pro 6,2 (2.8ghz i7 640m). Patch successful but the computer randomly crashes and restarts. Passes AHT and seems to work fine under supported OS. I don't think this is a hardware issue. Mojave 10.14.5.
Are you sure you patched the right hardware...?
I don't recall MBP6,2 has 640m... only 330m...
Yes, typo, I meant 330m. Turns out that it isn't an issue with the patch. It's an issue with the GPU. I suspect it's the capacitor issue notorious with the 2010 15". The issue was intermittent and its first occurrence was in the patched OS but it later happened in high Sierra so it isn't related to the patch.
same trouble , random reboot
but i will try this
https://github.com/julian-poidevin/MBPMid2010_GPUFix/releases/
What I should expect now? a new update?
As I was receiving the reinstall message continuosly, I choose "do not remember" ... did I stop the posibility for future updates/fixes?
[doublepost=1565252234][/doublepost]And,... also got this update. It's safe to make it?
Attachments
Greetings all,
I'm wondering if someone could point me in the right direction. I have a mac mini 5,1 that I patched a few months ago and I recently went to update the OS to 10.14.6, but I ran into a small issue. When I plugged what I thought was my patched installer into my mini to rerun the post install process I came to the realization that my fiancé had wiped the drive to use for a project. Now said mini won't boot and the only other machine that I have that runs macOS is my T2 equipped MacBook Air.
Is there a way I can create a utility disk that's just the post process function of the patcher? Or do I need to reinstall High Sierra and try patching to Mojave again?
I'm wondering if someone could point me in the right direction. I have a mac mini 5,1 that I patched a few months ago and I recently went to update the OS to 10.14.6, but I ran into a small issue. When I plugged what I thought was my patched installer into my mini to rerun the post install process I came to the realization that my fiancé had wiped the drive to use for a project. Now said mini won't boot and the only other machine that I have that runs macOS is my T2 equipped MacBook Air.
Is there a way I can create a utility disk that's just the post process function of the patcher? Or do I need to reinstall High Sierra and try patching to Mojave again?
You make again the full installer with the patcher, and just select the "Post install..." in the menu. No need to install again.
I understand that's what I should do in theory but judging from a previous post on this thread from @dosdude1 the T2 enabled Macs don't play nice with his software. I've tried several times to recreate the installer on my 2018 MacBook Air with no luck.
Has anyone found a work around for using the patching software on a T2 enabled Mac?
BlueSky
I just released a new tool for macOS 10.14 Mojave and macOS 10.15 Catalina.
Here are the release notes from GitHub: "BlueSky is a command-line patch tool for the SkyLight and HIToolbox frameworks. This tool is intended for non-Metal graphics cards running unsupported versions of macOS 10.14 Mojave and 10.15 Catalina. This tool fixes transparency issues by swapping UI materials in the SkyLight framework and setting the menubar and context menus to opaque in the HIToolbox framework. The HIToolbox framework patch is only supported on macOS 10.14 Mojave. The download size for the zip is around 100MB. If you download only the script then BlueSky will automatically download the full zip file that includes all the patched binaries. The original binaries are also included in the zip file and are used for the patch removing options. Backups are also made before and after patching in /Users/Shared. These backups can be restored manually but should only be used as a last resort. Please contact RMC if you need help in recovering a damaged system."
Download link: https://github.com/rmc-team/bluesky/releases/tag/1.0
I just released a new tool for macOS 10.14 Mojave and macOS 10.15 Catalina.
Here are the release notes from GitHub: "BlueSky is a command-line patch tool for the SkyLight and HIToolbox frameworks. This tool is intended for non-Metal graphics cards running unsupported versions of macOS 10.14 Mojave and 10.15 Catalina. This tool fixes transparency issues by swapping UI materials in the SkyLight framework and setting the menubar and context menus to opaque in the HIToolbox framework. The HIToolbox framework patch is only supported on macOS 10.14 Mojave. The download size for the zip is around 100MB. If you download only the script then BlueSky will automatically download the full zip file that includes all the patched binaries. The original binaries are also included in the zip file and are used for the patch removing options. Backups are also made before and after patching in /Users/Shared. These backups can be restored manually but should only be used as a last resort. Please contact RMC if you need help in recovering a damaged system."
Download link: https://github.com/rmc-team/bluesky/releases/tag/1.0
Last edited:
A permanent fix is fairly simple. It's an issue with the C9560 capacitor. I'm using a gpu switcher until the new part.arrives. A permanent fix costs ~$12 for the part and a tiny bit of soldering.same trouble , random reboot
but i will try this
https://github.com/julian-poidevin/MBPMid2010_GPUFix/releases/
I fixed my problem with hibernation. I wound up scrapping my APFS formatted volume and the APFS boot patch and reinstalling mojave in an HFS volume. After that, updated to 10.14.6 with a patched installer and everything is working again.
I have a late 2008 aluminum unibody that I was successfully running Mojave on. I'd made it through the update where the new patcher (1.3.0 or later) was required and everything was running smoothly. I left it to put itself to sleep as usual yesterday, but today when I went to wake it up it was powered down even though it was fully charged. When I tried to boot it, it got stuck and eventually told me that my computer failed to boot due to a problem. It still shows my user accounts and asks for the password during boot, but fails after that. When I tried to use the patcher USB to start it up, it asked me for the language I'd like to proceed in like it was a fresh install.
I have no idea what happened or what to do from here. The only thing I'm aware of that changed yesterday was I installed a patch for Night Shift - it was prompted from the patcher tool. My system was not 100% up-to-date, if that matters, as I'm working on a dissertation and was putting off messing with it until I finished at the end of the month. Maybe the Night mode patch was for a newer version than I have? I really don't know.
I have no idea what happened or what to do from here. The only thing I'm aware of that changed yesterday was I installed a patch for Night Shift - it was prompted from the patcher tool. My system was not 100% up-to-date, if that matters, as I'm working on a dissertation and was putting off messing with it until I finished at the end of the month. Maybe the Night mode patch was for a newer version than I have? I really don't know.
Last edited: