Hey acayon, and everyone else having this issue. I also have a mid 2007 MacMini 2,1 1.73 GHz with (upgraded) 4 GB 667 MHz DDR2 SDRAM and Intel GMA 950 64 MB graphics. It is on the latest lion version with all combo updates and security patches or whatever (there is nothing in the updates left to update) and cannot get it to install, it came with . However I did follow 13,14,15 based on the steps here
https://blog.christophersmart.com/2009/12/22/does-your-mac-have-64bit-efi/ it shows UFI32. I am under the impression that the core2 duo is a 64bit cpu as well, but just stating that even following those steps did not produce anything - you may be right to skip those steps - i honestly don't know.
Before i go on, i'll mention i'm using a separate partition on the same disk and no USB.
My outcome is a bit different though than others stating a loading bar and some store of crossed out symbol, for me it just hangs on the grey background apple icon, if there is a loading bar its gone faster than i can see it, and i have no crossed out line thing.
Further, I tried both boot.efi variants (black/grey). First I went with black because the site stated the legacy grey was for macpro but again, both result in a gray background with dark grey apple logo (thats it, nothing more) and it just stays there forever. What may be of interest however is that when i used the black boot.efi it did start as a white on black apple logo for less than a second, then reverts to the dark grey on light grey logo.
I tried the bless command too, and got the same message. When i enter the installer partition in safe mode, all i get is a couple of lines displaying my device UID. and it just sits there.
There are a couple of things that were a bit confusing, If anyone would like to answer these I'd appreciate it!
- Is the black / grey boot.efi required to match that of the original boot color? or is it just preference.
- The instructions in most place state that operations are to be done to the installation device, and I was curious (even though the example command states install device in brackets) that i am not supposed to apply these things to the current hard drive -- also I did not follow the step for RestoreHD, If its neccisary to get it to install then that may be my issue.
- The instructions state to apply the same text edit to both plists, and states before hand that these are the only things that should be edited, so I'd like some clarification that we are not supposed to edit the second array in the PlatformSupport.plist that looks to have model (not board-id) values in it? Also if it could be clarified that we are supposed to CHANGE the last entry in the list and not add it to the list as suggested in a prior step right?
example: PlatformSupport.plist
<plist ..>
<dict>
<key>SupportedBoardIds</key>
<array><string>Mac-....</string>..</array>
<key>SupportedModelProperties</key>
<array><string>MacPro#,#</string>..</array>
</dict>
</plist>
I am using a july 2016 el capitan app file which appears to be the latest version, but just for the purpose of seeing if we are all running into the same issue because of the source -- i didn't acquire this app file from the mac app store directly. I am guessing/taking a shot in the dark that the issue everyone else is running into at the same time derives from either the latest version or possibly that we are all getting it from a popular source.
Also, just to follow up on MacPostFactor, I do get error code 1 as well. And as mentioned its stuck at that same 97.something percent.
I'm going to try and locate an older version of el capitan app, (perhaps one that has a "boot" file on it that is apparently missing with the bless call?) I am curious though if i should be using the EFI32 boot or not now though.. Is there any kind of a model number / board id to EFI32/64 lookup?
Thanks guys
Also, for further verification here is the MD5/SHA1 hashes..
Code:
openssl md5 "/Applications/Install OS X El Capitan.app/Contents/SharedSupport/InstallESD.dmg"
06f6e4a7b1996c542cbda28eb5f7a8f2
openssl sha1 "/Applications/Install OS X El Capitan.app/Contents/SharedSupport/InstallESD.dmg"
7739e3f62080000da5d28efa689c53976112a262
update
I'll be trying 10.11.5 next, just to see if its 10.11.6 that is causing the issue. I'll try MacPostFactor and let you all know how it goes, then the longer version afterwards. Thanks
update
10.11.5 with macpostfactor fails as well.
I'll try the other method next. Decided to instead try macpostfactor with 10.11.4 first, i'll update then.
update
10.11.4 does not work either. I'm going to change tactics and get something to make the first method automated.
update
Just a quick note, about something that I could be completely wrong about.. but it seems like the 97.75 % error could be related to you having the log zip on your desktop. When i delete the zip, it gets much further before failing. I noticed this after trying v2.0.0 and noticing that the logs were printing v2.0.1, so i figure that when the log file exists ( or i dunno, maybe for some reason a app had the file handle open or something and it was unwritable..? ) no attempt is made without first removing it (like it checks for it at that percent..), So basically all my results from testing / extracting/ wasting time with 10.11.5 and 10.11.4 seem to have been for no reason, since the log literally wasn't updating.
So, now that I've ran into that. I'll be retrying 10.11.5. 10.11.6 still fails (for some reason, it does not generate any log zip file however) but at least it ran for a couple of minutes before failing. It could be that i need more disk space or something, either way it doesnt look good for 10.11.6 (if it is even a version related issue). yea going to try 10.11.5 on macpostfix and if it fails again, I will actually do the manual method again and verify.
I hope these long forum posts are not against the rules or anything, but yea I've read elsewhere there could be an issue with the fact that I installed the security update(s) on lion. So if 10.11.5 does not work through both methods, I'll do a clean restore, get back to lion, attempt it at 10.7.2 then if that does not work, update to full blown 10.7.5 avoiding the the security patches, then if that does not work, well I'll probably give up on el capitan and target yosemite. Trying to remain positive though!
update
Ok, so with the 10.11.5 install app and MacPostFactor 2.0.1 I was able to make an external installer (the second option on the right bottom). Going to try installing from that now.
