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.
OS X El Capitan on Unsupported Macs
- Thread starter TMRJIJ
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I did method 3 by SkyFly555 on my MacBook 2,1. It is honestly much more difficult than it appears, due to the fact that every time there are system updates, something major (Usually USB, Keyboard and mouse) quit working.
by comparison, Yosemite is very easy to install. if your time is even slightly important to you, recommend you go that route. that said,with all the correct Kexts this MacBook runs very well on ElCapitan.
After MacPostFactor and MacOS Extractor don't worked with me I downloaded Carbon Copy Cloner and cloned the HDD with that from my MacMini where I installed El Capitan (Legal). Then I've edited PlatformSupport and anything works fine except no driver is installed. So no USB no Trackpad no Keyboard. I've got an MacBook 4,1 (2007) and now I dual Installed Lion. Does anyone have an idea how to manual install the drivers, then I would install Lion drivers?
The original Lion-Kexts do not work, you need a patched version: USB-Kexts (by TMRJIJ - OS X Hackers). That's a quite old version of them - maybe TMRJIJ has newer ones, they should be also in the macOS Extractor.
Or try the USB-Inject-All (by RehabMan).
To your question:
http://OSXDaily.com/2012/01/12/How-to-Manually-Install-Kernel-Extensions-in-Mac-OS-X/
Good work. Odd that you are also missing the background wallpaper image. Was it always like that or did you remove it?
I did not have a supported Mac to clone from, so mine came from a temporarily Hacintoshed ASUS UX305FA. Dock and background image were both present and continue to be there...
Probably. The Graphics-RAM size should normally be 64MB if the Intel GMA 950 Kexts are fully working.
In OSX 10.10 Yosemite it was a clear sign for working Graphics Kexts if the ATI X1600 shows 128MB/256MB or the Intel GMA X3100 144MB. But as far I've seen it in the OSX 10.10 Yosemite-Thread the Intel GMA 950 seems to be a different thing and it shows only 10 MB Graphics-RAM size there.
Last edited:
My MacBook 2,1 with GMA950 running ElCapitan also says only 6MB Graphics-RAM, but in fact it runs very well. It plays 720p YouTube full screen without stuttering. I estimate it achieves 70-80% of the video performance capable when running supported on SnowLeopard 32-bit.
You can install the GMA 950 Kexts using macOS Extractor to get its full 144MB Graphics RAM in use.
Isn't MacBook GMA950 only 64MB ? I tried lots of different video Kexts, the ones that feel most smooth in fact only indicate 6MB on the System Report. Any chance that system report is not accurate?
It is 64MB. I was thinking of the MacBook 4,1. My bad. It would be unlikely that the system report is not accurate but if you are happy with the performance, then hooray!
I downloaded the zip on a machine running 10.12. When I unzip using macOS, I also get an error saying the package is damaged and can't be opened (and should be trashed).
If instead I unzip from the command line, I get the mpkg as expected, but I also get a folder called __MACOSX, which itself contains the mpkg and Readme again. Both of those mpkgs give me the same "damaged" error.
I'll upload it tonight when I finish Beta 5. I probably just need to set all FTP transfer types for Zips in 'Binary' mode since this seems to be a reoccurring issue.
[doublepost=1490669250][/doublepost]
macOS Extractor v1.4.2 Beta 5
Here is macOS Extractor v1.4.2 Beta 5. This Beta is for Developers and Beta Testers who can diagnose their Macs if something goes wrong.
A macOSE update is recommended to assist you in installing macOS Sierra, El Capitan, Yosemite, and Mavericks on your old Mac. Also, by updating this patching software on your Mac, you can enjoy various additional features and enhanced security. Always use to the latest version.
Never download this from any other provider. All links must be from these forums or directly from our server. This is to ensure that nothing was tampered with and that you have the most reliable and tested stuff.
This update includes the following:
- Maintenance script now compresses Dock app resources
- [dev] AutoPatch main script now includes variables for each OS and steps required
- [dev] Graphical Kexts Web Installers now addresses changes in version control
- Address differences between Mountain Lion and other OSs’ BaseSystem
- Hides Framework error from installer logs (Not Important)
Other features in Previous Betas:
- Address Issue that would cause Mountain Lion Patching to fail due to file name errors.Adds a PostInst script within the AutoPatch that can be addressed through the Installer’s terminalGraphical Kexts are automatically downloaded to the Installer for use during patching.AutoPatch now verifies that the Installer is ‘bless’ to boot.
- Maintenance Script is now fully executable and includes more optimizations.Address issue where Graphics Kext Installer fails even when the kexts are installed.
- Fixed issue where the Graphical Installer fails after clearing kernel cache
- Addresses issue where the AutoPatch refuses to complete all of its tasks within the Target Partition/Image
- Fixes issue where some scripts are in rich text formatting (ugh...who did that?)
- Replaces brightness app with a new app recommended by a member is the Yosemite thread.
- Smart OS detection
- Installer Logs now echo its current process to help diagnose where more issues may occur.
Developer Focus Area:
- Booting into OS X Mountain Lion, El Capitan, and macOS Sierra Installer
- Usage of PostInst script
- Performance
- General Reliability
- Rootless Disabling
Download Size:
70 - 170 MB
Prerequisites
Tested Macs listed below. Here are the minimum requirements:
- Running 10.7 Lion
- At least 2GB of RAM.
- A copy of Yosemite or Mavericks in Applications Folder (.app file preferred)
- 15 GB of free space from USB or HDD Partition.
-MacBook2,x
-MacBook3,x
-MacBook4,x
-MacBookPro2,x
-MacBookAir1,1
-MacMini1,x (C2D upgraded)
-MacMini2,x
-iMac4,x (C2D can be upgraded)
-iMac5,x
We DON'T assist with Hackintosh. All private messages/emails involving installing OS X on non-Apple hardware will be redirected to another support team.
How to Use It:
1. Download macOS Extractor
2. Install it. Choose a version of macOS/OS X to get the correct patches.
3. Open the AutoPatch in your Applications and view to corresponding guide the OS you choose. (Use Post 1 right now)
I still do not get a functional package when I unzip. What are you using to unzip? Are you able to download the file from that link on a Mac OS system and properly unzip?
Just using the built-in Archive Utility in macOS. Safari/Firefox downloads and unzips it fine on both my Mac and MacBook 4,1 as well the Macs/Windows 10 PCs at my University labs.
I'm on Mac OS Sierra (tested on 2 different laptops). I tried downloading with Safari, Firefox and Chrome. I tried to unzip with the built-in Archive Utility, the Unarchiver and the unzip command-line tool. All result in the same "damaged" error when opening the mpkg.
---
Interesting, I just tried downloading using curl and I got a functional mpkg. Not sure why this works and the others fail.
--- Edit: Additional info added ---
The AutoPatch installer fails when installing Mavericks, but succeeds for El Capitan (I prefer the former since it seems to work best for my Mac Mini). However, the El Capitan install partition cannot be booted since it doesn't seem to be complete: it only contains a Library folder, no System or anything else. Maybe the mpkg was still corrupted, even though it allowed me to successfully install?
---
Interesting, I just tried downloading using curl and I got a functional mpkg. Not sure why this works and the others fail.
--- Edit: Additional info added ---
The AutoPatch installer fails when installing Mavericks, but succeeds for El Capitan (I prefer the former since it seems to work best for my Mac Mini). However, the El Capitan install partition cannot be booted since it doesn't seem to be complete: it only contains a Library folder, no System or anything else. Maybe the mpkg was still corrupted, even though it allowed me to successfully install?
Last edited:
Is there a dedicated installer log, or do you just want the output shown in Console.app?
I did noticed many errors like this one:
default 17:50:04.875258 -0500 cp Cannot make directory /Volumes/OS X Base System/System/Installation/SMCPayloads/Mac-2BD1B31983FE1663: No such file or directory
Does the partition I am using as AutoPatch installation destination have to be named "OS X Base System"? I haven't been doing that, but tried after seeing this error. It seemed to get further (a few more things installed into partition, including "kernel") but still no System directory.
When you open the AutoPatch. Go to the Menu Bar > Window > Installer Log
A new Window should show up. Now you can Change the Detail Level to 'Show All Logs' and save it.
There's actually a known bug where if the partition has a space in the name, it will sometimes fail during restore.
Last edited:
Looking at log, I noticed that OS X Install ESD wasn't loaded. I reran the macOS_Extractor, which reloaded it. Now I see my partition seems complete (still haven't tested).
One suggestion: the installer should fail immediately if it cannot find OS X Install ESD.
Last edited:
The El Cap install just hanged on the Apple screen. Left it over 10 minutes, saw no activity.
Tried with Mavericks as well and starting from install partition kicked me out to normal internal disk. I assume I need to bless the system, but the command for that fails (on Sierra host). Is SIP getting in the way? Is there a way to bless the system without having to disable SIP on my Sierra machine?
For El Capitan:
The boot.efi should have been replaced with one that sets SIP to disabled by default (0x67). If this still doesn't seem to be the case then perhaps I need get the autopatch to make another partition that disables it and redirects to the installer.
If you are using the AutoPatch within your Sierra machine, I can see SIP blocking some of the commands because there is a bless command in the main script. Also check if the Mavericks installer has a mach_kernel in the root.
Would SIP block anything else? Should I rerun the whole installer?
I don't see mach_kernel nor kernel in the Mavericks installer. The El Cap installer does have kernel.
Here's my install log for the AutoPatch of El Capitan after:
1. disabling SIP in my host machine
2. renaming the destination partition to name without a space
Couple of errors I noticed:
a) cp: ./El Capitan/prelinkedkernel: No such file or directory
b) cp: /Volumes/Mac OS X Base System/mach_kernel: No such file or directory
Not sure what Mac OS X Base System volume is -- my installation partition was renamed to OS X Base System, though.
About that: why is the installation partition renamed to OS X Base System? Can it be renamed to its original name at end of installation?
1. disabling SIP in my host machine
2. renaming the destination partition to name without a space
Couple of errors I noticed:
a) cp: ./El Capitan/prelinkedkernel: No such file or directory
b) cp: /Volumes/Mac OS X Base System/mach_kernel: No such file or directory
Not sure what Mac OS X Base System volume is -- my installation partition was renamed to OS X Base System, though.
About that: why is the installation partition renamed to OS X Base System? Can it be renamed to its original name at end of installation?