Back to my question: If I could run an OS in a VM should it then theoretically be possible to run the OS also natively on this machine? Because a VM couldn't add or implement hardware that isn't on that machine (maybe it could emulate, but then it should be possible to emulate it natively too?)?
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
Try to boot again from the USB installer or any MacOS recovery and launch the Terminal and give in sequence these commands:
csrutil disable
nvram boot-args="kext-dev-mode=1 -no_compat_check"
csrutil enable
reboot
sorry dosdude1 if I answer in your place but I think you will be submerged by trivial questions of which I am a champion.
After 30min install .. the install will.an reboot to continue install.... Must i go to the post script to install? Or what...
Imac 12,2 i5 prozessor
// After reboot i have the no logo...
/// Install post script for imac 12,2 ....
/// After install i have see the progess bar but befor the end i have an black screennn...now Force Cache Rebuild ...
Your computer has an problem pls reboot the mac .. what this?
Imac 12,2 i5 prozessor
// After reboot i have the no logo...
/// Install post script for imac 12,2 ....
/// After install i have see the progess bar but befor the end i have an black screennn...now Force Cache Rebuild ...
Your computer has an problem pls reboot the mac .. what this?
Last edited:
Well, I tried your suggestion. Downloaded the beta from a supported system. Then I patched the app with the destination a usb external drive (32g).
I then rebooted using the external usb drive on my unsupported system. Got these messages after restart:
"macOS could not be installed on your computer. Volume contains macOS or OS X Installation Media. Quit the installer and restart your computer and try again".
Appreciate the response.
You need to use the patcher to create an installer USB drive, boot from that, and install onto your SSD. It works exactly like High Sierra Patcher did.
Apple iMac "Core i5" 2.7 27-Inch (Mid-2011) iMac 12,2
Installed Mojave b2 using USB Dosdude1's patcher
Rebooted to USB Patcher, Ran patches iMac 12,2
Rebooted:
Boots to Gray Apple Logo, light gray screen, progress bar gets about 2/3's of the way through and the machine reboots. It then reboots a second time with a double chime. It's like a full chime with a half chime right afterwards.
Will try again later with verbose output.
This is from memory (last night).
I am guessing its an issue with the AMD Video Card. I have not tried anything outside the patcher. Tried to run it like it is for a good test.
I would like to thank dosdude1 again for his hard work and dedication (and anyone else associated with this project). I will be sending a donation to dosdude1 after my next eBay sale. I used to write donation ware about ten years ago and will be paying it forward. Your HS patches are solid.
Last edited:
this happened on my MBP6,2 earlier as well, although installation and post patches went fine.
edited the boot.plist and voila.
Or it's 32 gb usb corrupted/worn out USB flash drive, since those main system files are really really small and so with a broken usb drive they jump out of read/write cycles.
Theoretically, yes; even Mac Pro 1,1 / 2,1 from 2006 / 2007 with an upgraded GPU can theoretically run Mojave. But practically, it is more of a challenge, especially when having to reverse-engineer a closed-source OS with closed-source proprietary hardware kexts.
@dosdude1 and @parrotgeek1 seem to be good at doing this. I definitely wish them luck with Core 2 Duo compatibility, these Macs may not be as powerful as Core i-series but they are still quite viable in 2018. I will be happy to test any patches on my MacBook (Mid 2010).
"kext-dev-mode=1" is completely unnecessary... It actually hasn't done anything since Yosemite.
[doublepost=1530027871][/doublepost]
It doesn't work yet with AMD video cards.
[/doublepost]
It doesn't work yet with AMD video cards.[/QUOTE]
Thank you for your work ... Iam back to high sierra
It doesn't work yet with AMD video cards.[/QUOTE]
Thank you for your work ... Iam back to high sierra
Maybe but trying on my macbook 2010 patching kexts tests I get many of them "with invalid signature" instead with that flag "with invalid signature: allowed", just an impression.
When I attempted to get Mojave working on my 2011 iMac 12,2, it did boot, just without acceleration on the AMD GPU (despite the required kext showing as loaded). It was however installed / set up using a supported Mac, not using the patched installer.
Alright, thanks for clarifying.
[doublepost=1530028698][/doublepost]It may help to know that after I installed Mojave using the supported Mac but before I ran through the initial setup, I wasn't able to get past the "This version of Mac OS X is not supported on this platform!" message, despite adding the 2011 MBP's board / model ID to PlatformSupport.plist and setting the -no_compact_check boot arg. After running through the initial setup on the supported Mac, it then booted up on the unsupported 2011 MBP.
Ok I'll try to answer even if today my English is very broken.
After other tests on some Penryn Core 2 duo aka legacy Macs, I have highlighted that through any Virtualization software even Virtualbox can boot Mojave beta 2 from a C2D cpu.
Since Virtualbox actually lacks of apfs support so only in HFSplus or with Clover bootloader, Parallels lacks of feature of USB RAW disk I need will explain later so only creating a virtual machine file, I used Vmware fusion 8.5.8 that supports native apfs and has a EFI boot loader very close to the real Mac EFI.
I can boot to the Mojave GUI system and with usb devices perfectly detected and working.
But in System Profiler noticed that:
1) first of all a vmware machine, apart different GPU vmware kext, is considered totally another kind of Mac, with different boot rom, different SMC, different efi firmware, different serial number, I would say it is a kind of Mojave supported Mac of the SMBIOS allowed series.
2) USB Bus are seen as XHCI and/or EHCI compatible with totally new hardware PCI ids, while on the real C2D Mac they are OHCI compliant and their physical ids are real and totally different. (of course they are new it is an emulation/sharing of the real ports)
I have to contradict many who believe that if can boot an unsupported system installed on an unsupported Mac from a virtual machine then also porting them on an external drive, natively will work. I am afraid no.
It will be very hard this time to support Mojave booting natively from a C2D and with USB OHCI working.
Last edited:
dosdude's patch works great on my MBA 2011 13" with HD3000. Couple of questions though - I saw someone got news, stocks apps working, how?? Stocks app launches but doesn't show any stocks, voice memos works great though. Another problem - news app is completely missing for some reason, probably just some beta 2 bug?
Yes, my mistake, stocks working fine, I just forgot I haven't enabled iCloud and there just weren't any stocks added by default that's why it didn't show. News app should probably work fine too, if it just were there. So I guess overall Mojave works fine on HD3000, except for the tinted menu bar on light mode and there are some graphics glitches which may or may not be related to the OS being a beta (context menu a bit glitched out on dock items).
I actually already got OHCI working by using IOUSB* kexts from 10.13, however it still kernel panics on boot. This panic is NOT related to USB.
I think there's too much speculation and old information in the first post. We need to fix that.
Damn. The Patcher doesnt work on my 2008 iMac 24“ with Upgraded CPU (T9300) 
I Hope you will add C2D and ATI/AMD support
I Hope you will add C2D and ATI/AMD support
Last edited:
I doubt, glitches and artifacts depend from HD3000, and generally I haven't encountered such big differences between a late beta and golden master, indeed there are more old resources traces in betas, in a final release often I found less, for these threads scopes I meant.
Also noticed, since the kexts for HD3000 are from Sierra it has the same issue I had in Sierra and previous versions (High Sierra has fixed this) - washed up display (black is not as black) when automatic brightness adjustment is turned on in display settings, minor issue but I guess it will be as good as it gets for now, unless magically High Sierra kexts start working towards the gm release.
You might try running the Display Calibrator in System Preferences (hold down option when clicking on "Calibrate"). Could help.
Apple Releases First Public Beta of macOS Mojave to Public Beta Testers
Links to the same place as developer beta 2. For Mojave the developer / public betas appear to be exactly the same.
Links to the same place as developer beta 2. For Mojave the developer / public betas appear to be exactly the same.