For someone who has installed the latest beta: What is the Darwin kernel version? In Wikipedia it says it is still 18.2 .
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
osKernelVersion= 18.2.0
MacOS 10.14.3 Beta 4 (18D38a)
Yes, it is still 18.2.0
~~~
[doublepost=1547426657][/doublepost]
Build is actually 18D39a
~ Aloha ~
I stand corrected. Beta 3 is
System Version: macOS 10.14.3 (18D38a)
while Beta 4 is 18D39a
Thanks. This is really odd. Both 10.14.1 and 10.14.2 had the version of the Darwin kernel 18.2.0 . This is both good news and bad news.
I'm quite sure @dosdude1 is willing to help you if you send him a short, simple private message. He knows what to do.
Can you please elaborate on the advantages and disadvantages of the kernel version retaining the same version in this case? Thanks.
Download Mojave, make a normal USB boot key. Boot on it and reinstall Mojave on top or your previous install.
You'll have to delete system files and then reinstall macOS to reinstall all the original files. Delete /Library/Extensions, /System/Library/Extensions, /Applications/Utilities/Patch Updater.app, /Library/LaunchAgents/com.dosdude1.PatchUpdater.plist, and /usr/local/lib. Some of these are directories and will be rebuilt when you reinstall macOS. There are better ways of doing this but this is by far the easiest. Please let me know if you have the APFS patch so I can give you more instructions for that.
[doublepost=1547486694][/doublepost]
But USB drivers at boot are EFI level. Nothing should ever be able to modify the EFI firmware. Have you used the APFS firmware patch?
When I used the APFS Rom patcher I just hit continue as there was no indicator light
I'm on 10.14.2 but have no keyboard backlight at all now. I just replaced the sensor earlier today hoping to recover it but nothing.
Noticed there is no patch box on the list for 10.14.2 on the DosDude patcher either.
I do see the indicators when I hit F5 and F6 and they move but there's no backlight on the keyboard at all.
Bummer.
Just re-install the Ambient Light Sensor Patch using the Patch Updater tool.
Great thread though I'm a little out of my depth here with most of the 460 pages. However, I'm brave enough ask:
I have a late 2011 MB Pro (8.1) running Sierra. It needs more RAM and an SSD. I want to bring the RAM to 8GB and replace the HDD with an SSD. I'm more than happy to fit these. Can I also upgrade this to Mojave? If so, what is the best method? I am able to connect the SSD externally to my iMac (currently with an SSD and running Mojave) if that makes it more straightforward, and then transfer the SSD directly into the MB Pro.
Any guidance?
I have a late 2011 MB Pro (8.1) running Sierra. It needs more RAM and an SSD. I want to bring the RAM to 8GB and replace the HDD with an SSD. I'm more than happy to fit these. Can I also upgrade this to Mojave? If so, what is the best method? I am able to connect the SSD externally to my iMac (currently with an SSD and running Mojave) if that makes it more straightforward, and then transfer the SSD directly into the MB Pro.
Any guidance?
So one of the 4 MacBook Pros I installed the Mojave Patcher 10.14.1 on was Updated because of a system notification accidentally being accepted and installing the OS 10.14.2 unpatched version. This is a family member that probably did not know what they were doing. It resulted in a boot loop upon startup, which was upsetting for them. USB Patcher was able to be Option key booted, re-installing the patches didn't work, Forcing Cache Rebuild did work and restored booting into 10.14.2.
1) However, the boot up time is now 10x longer than it should be. Any fix for this? Resetting PRAM, SMC, Holding Option on bootup and then holding Ctrl to set the boot volume all did not fix the problem. The computer is fully operational otherwise.
On other threads they have mentioned that the following method can regenerate boot cache to increase startup time (after the first boot, which is slow for the cache rebuild). Since booting on the Recovery Partition isn't possible, the instruction would be to boot off the Patched USB and open Terminal and enter the two commands below. Since I'm fairly a noob to Terminal commands, especially with a Patched OS, are these commands safe to try on the Patched OS to possibly restore boot times? Has anyone tried these? " In Terminal:
cd /Volumes/Macintosh\ HD/var/db/caches/opendirectory
mv ./mbr_cache ./mbr_cache-old
Modify the command to reflect the name of the startup volume if it's not Macintosh HD. Remember to use an escape character before each white space in the command path. Mind the spaces in general. Press Return after each command. After both have been entered quit Terminal
"
-- again I haven't tried these and don't want to risk it without further confirmation from the team here.
2) Is there a way to restore the recovery partition and include this in future Mojave Patched versions? Or is this more hassle than it's worth?
3) Can part of the Mojave Patcher have a function to toggle disabling of automatic updates and/or notifications and to only check and install security updates? I only mention this because family members are more likely to update accidentally without this feature. Or maybe an auto-downloader/updater for a patched USB to update might ease regular OS updates? Pie in the sky dreams, I know.
Any help especially with 1) would be greatly appreciated!
1) However, the boot up time is now 10x longer than it should be. Any fix for this? Resetting PRAM, SMC, Holding Option on bootup and then holding Ctrl to set the boot volume all did not fix the problem. The computer is fully operational otherwise.
On other threads they have mentioned that the following method can regenerate boot cache to increase startup time (after the first boot, which is slow for the cache rebuild). Since booting on the Recovery Partition isn't possible, the instruction would be to boot off the Patched USB and open Terminal and enter the two commands below. Since I'm fairly a noob to Terminal commands, especially with a Patched OS, are these commands safe to try on the Patched OS to possibly restore boot times? Has anyone tried these? " In Terminal:
cd /Volumes/Macintosh\ HD/var/db/caches/opendirectory
mv ./mbr_cache ./mbr_cache-old
Modify the command to reflect the name of the startup volume if it's not Macintosh HD. Remember to use an escape character before each white space in the command path. Mind the spaces in general. Press Return after each command. After both have been entered quit Terminal
"
-- again I haven't tried these and don't want to risk it without further confirmation from the team here.
2) Is there a way to restore the recovery partition and include this in future Mojave Patched versions? Or is this more hassle than it's worth?
3) Can part of the Mojave Patcher have a function to toggle disabling of automatic updates and/or notifications and to only check and install security updates? I only mention this because family members are more likely to update accidentally without this feature. Or maybe an auto-downloader/updater for a patched USB to update might ease regular OS updates? Pie in the sky dreams, I know.
Any help especially with 1) would be greatly appreciated!
There will probably no need to update the patcher. Is this a good thing? It depends. On a short term, it seems so. On the long term, probably not. My guess is the Apple shall bring the kernel in line with the rest of the os somewhere in March and due to that more work will be needed for all of us. The kernel changed more then expected with the first update of Mojave and it caused a lot of issues, more then some of us hoped.
Thank you Mighty dosdude; I had run a reinstall from the patch in the utility folder to no luck.
Was going to update and say after going inside for like the sixth time; cleaned the little connector once again but this time a bunch of other ribbon connectors and parts with alcohol and the keyboard backlight is back!
Thanks for your kind response but it wasn't the Mighty Mojave Patcher upgrade but a dirty connector among a bunch impacting the keyboard backlight. Update: Spoke too soon. Backlight went out again. Went inside cleaned everything all over again and rebooted and it came back; albeit briefly. It flashed a few times settling in and then goes out again. There's some up and down with the screen brightness again too. But unlike the updated High Sierra; it will settle down and stay down when you lower it. I'm thinking it's software related.
But boy does Mojave run great on the early 2008 Macbook Pro. WoW!
Last edited:
According to the list on the Opening Page of the thread, all MBP8,x are supported, and that includes yours. Most folks on this thread have used Dosdude1's Patcher (the link is provided on the OP), and done the post-install patch, all without any problem. It is simple, direct, provides you with a link to download Mojave 10.14.2, and how to install Mojave. You should try that first, after adding more RAM and the SSD of course.
Hi!...How i can download macOS Mojave 10.14.3 Public Beta?, i have iMac early 2008..is possible?
Thanks!
Thanks!
Hello, I am unable to install macOS mojave on my macbook pro 2011 late.
I have formatted the USB as told in tutorial but when i start operation i see the following error
Restore Error
Unable to restore base system when i open Verbose Output it shows
The volume on device """ is not of type Apple_HFS or Apple_UFS
I have formatted the USB as told in tutorial but when i start operation i see the following error
Restore Error
Unable to restore base system when i open Verbose Output it shows
The volume on device """ is not of type Apple_HFS or Apple_UFS
Hello,
That's the same machine I've, If you can afford it jump to 16gb ram, 2x8gb, I did that and it works like a charm.
Attachments
Is anyone else getting this weird glitchy black border around windows: https://imgur.com/a/g3WHhb2
I don't get this on a native Mojave machine.
I don't get this on a native Mojave machine.
Yes, it's mention in this thread a couple of times and you can find it on the first page:
Someone mentioned a work around somewhere in this thread, I think. Though I can't tell you more since it never bothered me, I wasn't paying attention tbh.
I'll trade you, your black border in dark mode looks more at home then my white border in dark mode.
Ah, right. My mistake the solution was to change from the mis-rendered white borders to black ones..