Did you get this error : "Error: installation could not be completed. Bad disk" ?
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
Apple is gearing up to release macOS Mojave! Check out this: https://support.apple.com/macos/mojave
Still their bad release specs of "plus mid 2012 and mid 2010"
You can install macOS Mojave on any of these Mac models:
MacBook models introduced in early 2015 or later
MacBook Air models introduced in mid 2012 or later
MacBook Pro models introduced in mid 2012 or later
Mac mini models introduced in late 2012 or later
iMac models introduced in late 2012 or later
iMac Pro (all models)
Mac Pro models introduced in late 2013, plus mid 2010 or mid 2012 models with recommended Metal-capable graphics processor, including MSI Gaming Radeon RX 560 and Sapphire Radeon PULSE RX 580
Still their bad release specs of "plus mid 2012 and mid 2010"
You can install macOS Mojave on any of these Mac models:
MacBook models introduced in early 2015 or later
MacBook Air models introduced in mid 2012 or later
MacBook Pro models introduced in mid 2012 or later
Mac mini models introduced in late 2012 or later
iMac models introduced in late 2012 or later
iMac Pro (all models)
Mac Pro models introduced in late 2013, plus mid 2010 or mid 2012 models with recommended Metal-capable graphics processor, including MSI Gaming Radeon RX 560 and Sapphire Radeon PULSE RX 580
Weird without VRAMSize it has worked on IntelHD4000 (Metal supported), while it seems mandatory to allocate physical RAM that VRAMSize value inside the AppleIntelHD3000Graphics.kext/Contents/Info.plist
Anyway if you want increase more on IntelHD3000, try these steps to increase VRAM from 1536 MB up to 2048 MB:
cd /S*/L*/Ext*/AppleIntelSNBGraphicsFB.kext/C*/M*
sudo cp AppleIntelSNBGraphicsFB AppleIntelSNBGraphicsFB.backup
sudo perl -pi -e 's|\xC7\x45\xD0\x00\x00\x00\x60|\xC7\x45\xD0\x00\x00\x00\x80|g' AppleIntelSNBGraphicsFB
sudo plutil -replace VRAMSize -integer 2048 --> use instead manual edit inside: /System/Library/Extensions/AppleIntelHD3000Graphics.kext/Contents/Info.plist
<key>VRAMMethod</key>
<integer>0</integer>
<key>VRAMOverride</key>
<integer>0</integer>
<key>VRAMSize</key>
<integer>2048</integer>
Then
sudo chown -R 0:0 /System/Library/Extensions && sudo chmod -R 755 /System/Library/Extensions
sudo kextcache -i /
sudo reboot
edit:
if something should go wrong, don't worry you can revert the correct VRAM also from the Recovery Terminal or from dosdude1 Mojave USB Installer simply using Post-Install selecting only "Video Patch" and "Force cache rebuild".
Last edited:
no, no such text. All I got was a circle with a bar through it.
I ask because you reported "Bad disc!" If so, your HDD may need to be repaired. You can try running diskutil repair on that drive from Sierra (since you are booted back into Sierra with SSD). A bad hard drive will (of course) prevent an install.
Bad hardware notwithstanding, there is no reason you shouldn't be able to install HS on your system straight from Apple.
Why did you create a bootable HS stick? After the HS download, you should have just invoked the install HS app on your hard disk. Or maybe you did...I can't tell.
Did you scan the links I sent about your OWC SSD and 5,1 bootroms? Here's another OWC page about firmware updates for their Mercury SSDs : https://eshop.macsales.com/tech_center/OWC/SSD. You should really check that your third-party SSD is compatible with your system before proceeding. Else you're back to KPs again, especially if you APFS the thing.
Last thing, if you haven't already, try running a full diagnostic on your machine
Not much more to recommend remotely. Again, you'll have to get HS up and running before considering Mojave.
Wait, it depends on how much VRAM quantity you have from your stock IntelHD3000
if you have 384 MB you have to use instead of 60 the hex byte 18
if you have 512 MB you have to use instead of 60 the hex byte 20
if you have 1024 MB you have to use instead of 60 the hex byte 40
If you patch VRAM for first time you can't use this:
sudo plutil -replace VRAMSize -integer 2048 /System/Library/Extensions/AppleIntelHD3000Graphics.kext/Contents/Info.plist
but instead you have to edit manually this file:
/System/Library/Extensions/AppleIntelHD3000Graphics.kext/Contents/Info.plist
Adding after these strings, the orange part:
<key>VRAMMethod</key>
<integer>0</integer>
<key>VRAMOverride</key>
<integer>0</integer>
<key>VRAMSize</key>
<integer>2048</integer>
Last edited:
I am trying to update from beta 5 to beta 6 but the update isn’t showing up.
Have you installed the software update patch and the developer or public beta profile?
That's a known issue. I have that problem too and many others also.
Since updating from beta 3 to 4 i have double boot.
Updating to beta 5 made no changes.
Is there a solution?
Updating to beta 5 made no changes.
Is there a solution?
Will the final version of Mojave fix the Isight and Brightness control on the keyboard, not working ?. I have been following this threat since its inception, and reading about patching the system with kexts from HS , but been not savy enough to do so ,and Mojave betas have been running and updating without a hitch on my older MacPro and 21 'LED Cinema Display with an upgraded ATI RADEON SAPPHIRE 7950 .
Use the macOS Mojave Patcher to patch your system automatically with the required patches that are currently available.
I used the High Sierra patcher and worked like a charm in a MacBook 2008 Aluminium Univody.
How and in what stage(s) of the upgrade process I disable the discrete GPU in a Mac Mini mid 2011 to install Mojave using the patcher? By disabling the discrete GPU, how this will affect monitors’ connectivity and HDMI sound? It would be great if an option to do that is available in the list of post-installation patches available to this Mac model in the patcher app.
How and in what stage(s) of the upgrade process I disable the discrete GPU in a Mac Mini mid 2011 to install Mojave using the patcher? By disabling the discrete GPU, how this will affect monitors’ connectivity and HDMI sound? It would be great if an option to do that is available in the list of post-installation patches available to this Mac model in the patcher app.
Last edited:
Yes, still an issue with many of us. Some are successful though. You'll have to get the full image and create a patcher disc (use the latest from the OP always). Same old dance...but it works.
Some of us are looking into this, so before you upgrade, can you save and share your current install.log. It's in Console /var/log under install.log. Will help the research. Thanks.
[doublepost=1534085582][/doublepost]
Yes - per Julian - it's best to use the installed patcher update to install your kexts.
Question: have you been system updating your betas (the preference's one)? Seems like it works well on your macpro (which flavor?) If you have - without creating a new patcher stick every time - sharing your /var/log installer log would help. Thanks.
[doublepost=1534086300][/doublepost]
Yes - it's getting close to showtime!
You cannot disable the discrete GPU on a Mac Mini. That's only possible on the MacBook Pro, because it has dual-GPU switching (gMux). The Mac Mini does not, it uses only the dedicated GPU.
Looking back at all apple OS release dates, they normally come out the 2nd or 3rd week of September. They release the new OS when their new devices come out, like the new iPhone. If Mojave keeps up with the trends, we will probably have 3 or so more betas until the GM comes out.
We had 9 (i think) with HS. The beta/preview program launched early this time (especially public). But we're close.
Would be nice if they fixed they're UI mode glitches cause it's a no-go for some. I reached out with a ticket but got no substantial response (as expected especially for unsupported devices)
Although this Beta is pretty "stable" at the moment... with minor bugs... (well known)
I tried everything now I don’t bother using public beta or
Developer beta
me too. Nothing works. I just use the latest version of the patch tool to download latest developer beta. Patch it to USB stick. Do an install over the top and run the patch tool again from the applications/utilities folder. Apply all patches again.
To those who have used dosdude1's Mojave Patcher on their Mac with any IntelHD3000 stock VRAM 384/512 MB
and want to try the VRAM increase without using my previous Terminal commands:
I attached all the possible already binary patched combinations of VRAM choices 1024/1536/2048 MB into a zipped folder, it also include an entire backup of the IntelHD3000, so just simply replace only the 2 kexts from their related VRAM folder copying into your Mojave /S/L/E/, use your preferred method to install the 2 kexts, after done fix /S/L/E/ permissions, rebuild kextcache, reboot. That's all.
Anyway after copying/replacing the chosen VRAM's two kexts, to fix permissions and rebuild kextcache I suggest this known method typing from Mojave Terminal:
sudo chown -R 0:0 /System/Library/Extensions && sudo chmod -R 755 /System/Library/Extensions
sudo kextcache -i /
sudo reboot
and want to try the VRAM increase without using my previous Terminal commands:
I attached all the possible already binary patched combinations of VRAM choices 1024/1536/2048 MB into a zipped folder, it also include an entire backup of the IntelHD3000, so just simply replace only the 2 kexts from their related VRAM folder copying into your Mojave /S/L/E/, use your preferred method to install the 2 kexts, after done fix /S/L/E/ permissions, rebuild kextcache, reboot. That's all.
Anyway after copying/replacing the chosen VRAM's two kexts, to fix permissions and rebuild kextcache I suggest this known method typing from Mojave Terminal:
sudo chown -R 0:0 /System/Library/Extensions && sudo chmod -R 755 /System/Library/Extensions
sudo kextcache -i /
sudo reboot
Last edited: