I noticed there’s a new night shift patch in the patch updater. I assume you’re testing this and will include it in the post install tool if it ends up working?
Last edited:
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
Yes, they are changing the Safari Extensions into Safari "Apps", and so now if you want to keep and use your favorites "extensions" properly you need to download (the updated one) only from the "New App Store".
For example I do intense use of Adblock, I've found a way to force using the old extension.safariextz installing from the gallery, however will not work properly, instead the one downloaded from the "New App Store" will work and will be installed into the "Applications" folder.
I found a way to use it, I switched to the Safari Technology Preview
Ok, however I guess it won't work in the long run, so passing through "New App Store" will be almost mandatory.
I’m also interested in doing this on my iMac. Do you have APFS support?
No APFS. But I got it working!
Used the kexts out of the High Sierra post-update utility together with the instructions where to put them and how to fix file permissions:
https://forums.macrumors.com/goto/post?id=23696261#post-23696261
Now I have found a new issue, my AirPort Extreme (0x14E4, 0x111) has no Bluetooth anymore.
Anyway, dosdude1 you are awesome and I’ll definitely donate enough to buy you dinner.
This AirPort Extreme (0x14E4, 0x111) should be a combo/BT 4.0 card, is supported natively on HighSierra, so it should work without "Wifi patch", with the stock Mojave IO80211Family.kext (or at least with the HS kext), and this eventually will auto fix the Bluetooth too.
Last edited:
Did not use the Wifi patch. Also did not need any tinkering before, apart from the ordeal of acquiring and installing that modern Airport Extreme
Like you said, everything worked natively, until now. But: I restored both IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext from HS (though i suppose the latter is not needed) and now i have working BT4.0 including continuity again. So for me everything works as good as it did in HS now, thanks guys!
APFS encryption for Mojave ~ not enough space to install.
I wanted to try to install Mojave on an external drive partition that is formatted APFS Encrypted. When using @dosdude1's Mojave patch to install, I got a message that I do not have enough disk space. It was allocated 64GB so I do not understand. Anyone else experience this? If so, solutions? Mahalo.
I wanted to try to install Mojave on an external drive partition that is formatted APFS Encrypted. When using @dosdude1's Mojave patch to install, I got a message that I do not have enough disk space. It was allocated 64GB so I do not understand. Anyone else experience this? If so, solutions? Mahalo.
It should work as long as you're using the latest version of Mojave Patcher (downloaded within the last day). Also, make sure you use Disk Utility to mount the volume first.
Thanks @dosdude1.
When you mentioned the last day, I am using your version 1.2.2 which has the same hash value indicated on your website. I downloaded 1.2.2 this past weekend. Should I re-download and setup my USB install boot drive?
Also I am not sure what you meant by mounting Disk Utility first?
Yeah, you need to re-download the patcher and re-create your USB drive. What I mean by mounting in Disk Utility is opening Disk Utility after booting off the patched USB drive, selecting the volume you intend to install onto, and selecting "Mount".
Hello JackLuke,
Thanks for your suggestions, unfortunately I was unable to boot into "single user" mode; the computer would become trapped in the same boot-loop, which prevented "standard" booting.
However, I was able to repair my boot drive, and make it fully functional, without any data loss, via "aggressive" use of terminal commands. I did not apply hardware ROM patch.
I did execute the commands you suggested while booted into the USB "Patcher Drive," via disk-utility to execute "fsck -fy" like command (using First Aid), and via terminal to execute rest of your suggested commands (the latter after I negotiated a pathway to my "lost drive'). The above procedure unfortunately did not repair the drive; after reboot the infernal boot-loop persisted.
Below, in as short terms as possible, is a description of what I implemented to restore my drive to full functionality, running final Mojave 14.0, and without any data loss. The process depends on user having another Mac to rebuild the USB patcher drive, unless the user is sure, that the patcher on USB drive is the latest version from Dosdude1.
- erase your USB patcher drive by using disk utility (format HFS+ journaled), unless it already has latest versions of patch and Mojave installation image; if so, skip next 4 lines.
- download the latest of Dosdued1's patchers
- lunch patcher app. and use it to download latest Mojave installer. The download tool can be accessed via menu command
dropdown item.
- use Mojave patcher app to create boot drive on a USB stick (drive)
- Boot into the USB Mojave Patcher drive (make sure it is the latest of Dosdude1's patchers) -> press "option key" on restart, and choose your USB patcher drive from drive selections which appear on the screen.
- once booted into USB Patcher drive, lunch terminal and enter the command -> diskutil APFS list (this command will list all viable APFS formatted drives and/or volumes)
- using terminal app., (it's on same USB drive, in utilities), mount the drive volume to be "worked on" via command --> diskutil diskmount "name of your target drive in parentheses."
NOTE: no actual drive will appear on the desktop, but it will be accessible via terminal and disk utilities (e.g. first aid)
- access the, now, mounted drive via terminal--> cd /volumes/ "name of your target drive in parentheses"
- this should result in access to the affected drive --> type ls (lower case L and lover case s) and press enter--> the contents of the directory of that drive should be listed in the terminal window.
- delete System folder via command --> rm -rf System (and press return)
- delete Library folder via command --> rm -rf Library (and press return)
**in my case I also had to use disk-utility to remove a partition called "Macintosh HD-Boot"; if user needs to delete a partition as well, the instructions on how to remove partitions are on the web (post will be too long)
- lunch disk utility, select the drive worked on, and run first-aid
- if everything is in order, lunch the Mojave installer - the window with installer should already be open, it lunches automatically, as soon as USB patcher drive boots, and stays open throughout the process.
- let the installation proceed
- once completed, an auto-reboot will be initiated - make sure to press "option key," while rebooting, to boot into drive-selection screen, and choose the USB patcher drive again.
- once booted into the USB patcher drive --> lunch disk utility, choose drive worked on, and select "first aid"; let the process complete -> there should not be errors listed in the disk utility output screen.
- go back to utilities window, lunch PostInstall app. and choose a *patch list* appropriate for the computer being worked on (in my case MacBook Pro 5,2), then choose the drive to patch, and lunch the patching process.
- when finished patching, and question is asked "whether to force rebuild caches," click in the disk-first aid window once more, and run "first-aid" again.
- once first-aid completes the process, press reboot button in the patcher window (I did not select "Rebuild caches" option")
- patcher will finished its file amendments, and computer will reboot (if all is well) into the white screen with Apple logo, and progress bar. Installation will proceed to middle of progress bar, and the computer will reboot once more; that's normal. Do *Not* press any keys on that reboot, the machine should go back to white screen with Apple logo and progress bar. Installation should complete, and your standard login window should appear on the screen.
- login, and enjoy.
Note, that this process worked for me as described, but there is no guarantee that it will bring other machines back from the boot-loop "hell". Exercise care when entering unix command in terminal, verify spelling is correct, and spaces are in fact where they must be.
The post is long, but t is descriptive, in hope of allowing someone else to recover their machine, not necessarily just for boot-loop issue. It is a set of steps that may be taken before being forced to format the drive.
Thanks for everyone's contribution to this thread.
Last edited:
Well, here are my experience with Mojave Patcher. Installation was ok, until I reached the desktop showing the Patcher Update window. Than the screen freezed, I can move the mouse cursor but nothing in screen responds.
Macbook Air mid-2011 with the default patches applied “MacBookAir 4,2”.
Macbook Air mid-2011 with the default patches applied “MacBookAir 4,2”.
@RogueB your steps are acceptable however I don't understand why you remove the System and Library content, I guess to make your drive lighter in using DiskUtility's First Aid so you can recover with less effort the Users folder ?
I believe that if a main drive SSD or spinning asks often to check/repair file-system or some little system/library files become corrupted, it's a signal of main drive becoming faulty, sometimes a full erase can make it workable again for a period, but I'd not rely much on it for storing important datas.
I believe that if a main drive SSD or spinning asks often to check/repair file-system or some little system/library files become corrupted, it's a signal of main drive becoming faulty, sometimes a full erase can make it workable again for a period, but I'd not rely much on it for storing important datas.
please forgive my ignorance. But what does "metal" support mean?
[doublepost=1538541083][/doublepost]
Gosh 7 years is not that old. I wish Apple would continue support out to at least 10 years. When I bought my 2011 laptop it was top of the line and paid about $3500 CND. Spread that over 7 years, that is about $500 a year. Which is like buying a new cheap crappy $500 laptop every year for 7 years.
EDIT:
Well I think I found my answer: https://appleinsider.com/articles/18/06/28/why-macos-mojave-requires-metal----and-deprecates-opengl
I still don't like the answer
Seven years mostly doesn't seem that old due to the end of Moore's law and the pitiful speed improvements being achieved.
Precisely that is what apple wants you to do. Meanwhile Windows 10 1809 just arrived. I have installed it on all MACs and PCs. The oldest 3 MACs are 2 macmini1.1 (Windows 10 32bit) and 1 macbook3.1 (Windows 10 64bit). This October update brings enhanced dark mode, which looks beautifully on all machines I have (in total 3 PCs and 6 MACs). Both the macmini1.1 and the macbook3.1 were abandoned by apple long time ago at 10.6 and 10.7, yet both are running today latest Windows 10 and better than they did run Mac OS. I am done with apple. Will never, ever buy another apple product. Nice looking, but overpriced and outdated hardware, with hardware defects never to be fixed (like mid 2010 macbook pro) and which software-wise will definitely be abandoned soon enough too. Besides I am not going to be alone. Very soon all professionals will forget apple in favor of either Windows, or Linux. I bet within the next 2 versions, macOS will be just an iOS, which will turn the machines into a toy, with a sole option to BUY apps from the store. I was a strong apple fan, but it is just insane how this company wants to milk us over and over again like cows on a farm. Great idea Jobs!
I think you could thank Tim Cook for the dismal macOS push Steve Job's was a big macOS supporter and user. Apple has not been the same since he passed away
Yes the new apps in the app store are all paid and have 10 times less power, which will make it impossible for some extensions to convert into apps. One such example are the ads blocking extensions (uBlock origins, Adblock and the likes). The only working solution in that respect is the application AdGuard (which of course is a paid app) and while this application works perfectly with current Mojave version, it will likely be broken in a future versions (as per the creators). For now however it is the best solution and works in ALL browsers since it acts on a network level ( I disabled uBlock origin + Tamper Monkey for the AntiAdblock killer script in Chrome, Firefox, Vivaldi and all ticks like a swiss clock)
@pkouame I found also a single byte patch in HIToolbox to reduce the transparency only for the menu bar.
Maybe it‘s the same byte you already found?!
Did you make any progress with reducing transparency on the sidebars (i.e. in Finder) without affecting other components.
Maybe it‘s the same byte you already found?!
Did you make any progress with reducing transparency on the sidebars (i.e. in Finder) without affecting other components.
hello. i managed to install mojave on an imac 8,1 with an upgraded wifi card (0x14E4, 0x112). my bluetooth is not working. does anyone know how to get it to work? thanks
Last edited:
Hi, apologies in advance as I’m inputting this on my phone. Hoping there’s a simple fix I missed before cracking the box open...
iMac9,1 upgraded to Mojave final no problem, but it auto-updated to PB1 (my mistake).
My formerly fine APFS formatted SSD checks ok from single user mode (it ran great with High Sierra and Mojave final), but no matter what I boot with (dosdude's latest USB installer or an installed Mojave on HFS external drive), everything freezes at:
AppleLPC::notifyPlatformASPM - registering with plugin with ASPM Support false.
My guess is I have to pull the SSD out to reformat or something, but thought I’d run it by the pros here to see if I maybe just inadvertently reset something...I might try whipping up an ElCapitain install disk (latest "supported version") to see if I can at least get the thing to boot.
Regards,
iMac9,1 upgraded to Mojave final no problem, but it auto-updated to PB1 (my mistake).
My formerly fine APFS formatted SSD checks ok from single user mode (it ran great with High Sierra and Mojave final), but no matter what I boot with (dosdude's latest USB installer or an installed Mojave on HFS external drive), everything freezes at:
AppleLPC::notifyPlatformASPM - registering with plugin with ASPM Support false.
My guess is I have to pull the SSD out to reformat or something, but thought I’d run it by the pros here to see if I maybe just inadvertently reset something...I might try whipping up an ElCapitain install disk (latest "supported version") to see if I can at least get the thing to boot.
Regards,
Last edited:
Yes and Yes! I have a private github repo you can sign up for to follow the progress. Some have already joined. PM me for details. If you were capable enough to find the same HIToolbox byte, we can talk...@pkouame I found also a single byte patch in HIToolbox to reduce the transparency only for the menu bar.
Maybe it‘s the same byte you already found?!
Did you make any progress with reducing transparency on the sidebars (i.e. in Finder) without affecting other components.