Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

BabyWolf

macrumors newbie
Feb 10, 2022
1
0
Hola!

My MacBook:
Late 2006; MacBook 2,1; 1.83 Core 2 Duo, 4Gb, GMA 950
Boot ROM MB21.00A5.B07
SMC 1.13f3

HDD 320Gb:
ElCapitan (was Lion 10.7.5) ~260Gb
Install (installer Mountain Lion 10.8.4) ~8Gb
ML (Mountain Lion 10.8.4) ~21Gb

El Capitan 10.11.6.app in Applications.

I try osx-patcher 1.1.5, installer from flash drive 16Gb.
After start installer i get the message:
OS X coud not be installed on you computer.
No packages were eligible for install.

I try pikify3.1.v14, instal to volume ElCapitan.
After reboot and start from volume ElCapitan, get installer window and message:
OS X El Capitan is already installed.

What are your tips?
 

TimothyR734

macrumors 68030
Apr 10, 2018
2,723
2,753
Logsden Oregon
Hola!

My MacBook:
Late 2006; MacBook 2,1; 1.83 Core 2 Duo, 4Gb, GMA 950
Boot ROM MB21.00A5.B07
SMC 1.13f3

HDD 320Gb:
ElCapitan (was Lion 10.7.5) ~260Gb
Install (installer Mountain Lion 10.8.4) ~8Gb
ML (Mountain Lion 10.8.4) ~21Gb

El Capitan 10.11.6.app in Applications.

I try osx-patcher 1.1.5, installer from flash drive 16Gb.
After start installer i get the message:
OS X coud not be installed on you computer.
No packages were eligible for install.

I try pikify3.1.v14, instal to volume ElCapitan.
After reboot and start from volume ElCapitan, get installer window and message:
OS X El Capitan is already installed.

What are your tips?
maybe one of these might help https://osxhackers.net/patchers/
 

Flipao83

macrumors newbie
Mar 23, 2022
1
0
Hello i used Greg Hrutkay El Capitan image, restored it to my upgrade iMac 4.1 and i can boot, but don't have usb inputs, do i need to modify some files on the dmg?
 

ggkameleon

macrumors newbie
Nov 20, 2014
16
3
Salut ! J'ai un MacBook blanc fin 2009 core 2 Duo 2,4 Gha X1300 sur Mac Os Lion.
Je veux le mettre à jour mais sur El Capitan mais je ne sais pas quel patch utiliser ?
Extracteur ? Pasteur ? Ou FairFax ? Wich is the best ?
 

fbagnato

macrumors newbie
Jul 5, 2023
9
1
Hi All,

First post here so be gentle with me :p

I am a Windows user with some minor exposure to Macs (my daughter has a 2023 Macbook Air which I help her with sometimes).

About a week ago I bought a bulk lot of old Apple hardware.

I am intending to sell the items for reasonable prices (they are old after all).

I started up the first of the 3 iMacs that were in the lot. It ran fine.

It is a White iMac Model No. A1207 (EMC 2118) Model ID: iMac5,1 with a Radeon X1600.

I then proceeded to update the Mac OS X to the last supported version of 10.7.5 (Combo Update).

I then came across these great threads of updating to El Capitan and Yosemite OS's on Unsupported Macs.

I searched through both threads for posts relating to X1600 and read ALL of them.

After reading all of them I am in two minds whether to update the iMac to either version.

I would like to update it to El Capitan but couldn't seem to find anyone that had successfully updated a X1600 based iMac without issues afterwards.

Logic tells me that people with problems are more likely to post on the threads more so than people who had success with the update so searching the thread did not give me definitive answers to my queries.

My questions are:

1) Is it possible to update my iMac X1600 based to El Capitan without leaving things not working (I understand that Graphics Acceleration is definitely not going to happen with the X1600 on El Capitan)

2) If not El Capitan, what (realistically) is the latest unsupported Mac OS X version that I could install on this X1600 based iMac, again without leaving things not working (I understand that Graphics Acceleration may not be supported with some versions)

The reason I would prefer a fully functioning iMac is that I would be selling the iMac so I want to leave the buyer a fully functioning iMac and if I can provide a newer OS than 10.7.5 then that would be great.

Thanks in advance and thanks to contributors of these threads / projects!

fbagnato
 
Last edited:

fbagnato

macrumors newbie
Jul 5, 2023
9
1
Hi,
Don't know if this is the right thread... Anyway I was succesfull since last year in installing yosemite and el capitan on iMac 5.1 w/o any issue and working normally (with julian fairfax os x patcher).

The troubles started today when trying to have a behringer UMC204HD (USB audio interface with MIDI) which uses apple coreaudio (It works fine on 2015 iMac with Mojave and on the same iMac 5.1 with Snow Leopard).
Pratically the interface is recognised but just the MIDI support is present (from "MIDI Studio") while the audio part is not listed in audio preferences. I've tried also with yosemite and the results is exactly the same...

I know that "osx patcher" apply patch to "AppleHDA.kext" and "IOAudioFamily.kext" but it is not clear to me if this is the cause for coreaudio to not recognise the device or there is any other possible reason linked to the fact the SO is patched.

I remember that to have internal audio working the patch is necessary but in case I can also survive w/o it if the Behringer would work...

Any idea?

Thanks in advance!
Hello GP70,

You say you successfully installed El Capitan on an iMac 5.1.

Can you confirm that your iMac 5.1 has a Radeon X1600?

I have an iMac 5.1 with a Radeon X1600 and all the posts I have read on this thread relating to Radeon X1600 video adapters seem to describe problems successfully installing El Capitan. I am therefore a bit unsure whether to try the El Capitan update from my current OS X 10.7.5.

Thanks,

fbagnato
 

Adamscomputerrepair

macrumors 6502a
Aug 9, 2015
549
287
Hi All,

First post here so be gentle with me :p

I am a Windows user with some minor exposure to Macs (my daughter has a 2023 Macbook Air which I help her with sometimes).

About a week ago I bought a bulk lot of old Apple hardware.

I am intending to sell the items for reasonable prices (they are old after all).

I started up the first of the 3 iMacs that were in the lot. It ran fine.

It is a White iMac Model No. A1207 (EMC 2118) Model ID: iMac5,1 with a Radeon X1600.

I then proceeded to update the Mac OS X to the last supported version of 10.7.5 (Combo Update).

I then came across these great threads of updating to El Capitan and Yosemite OS's on Unsupported Macs.

I searched through both threads for posts relating to X1600 and read ALL of them.

After reading all of them I am in two minds whether to update the iMac to either version.

I would like to update it to El Capitan but couldn't seem to find anyone that had successfully updated a X1600 based iMac without issues afterwards.

Logic tells me that people with problems are more likely to post on the threads more so than people who had success with the update so searching the thread did not give me definitive answers to my queries.

My questions are:

1) Is it possible to update my iMac X1600 based to El Capitan without leaving things not working (I understand that Graphics Acceleration is definitely not going to happen with the X1600 on El Capitan)

2) If not El Capitan, what (realistically) is the latest unsupported Mac OS X version that I could install on this X1600 based iMac, again without leaving things not working (I understand that Graphics Acceleration may not be supported with some versions)

The reason I would prefer a fully functioning iMac is that I would be selling the iMac so I want to leave the buyer a fully functioning iMac and if I can provide a newer OS than 10.7.5 then that would be great.

Thanks in advance and thanks to contributors of these threads / projects!

fbagnato
Macpostfactor will allow you to do 10.8-10.10. 10.8 will still have working graphics. Personally, I’d dual boot 10.8 and Linux
 

fbagnato

macrumors newbie
Jul 5, 2023
9
1
Macpostfactor will allow you to do 10.8-10.10. 10.8 will still have working graphics. Personally, I’d dual boot 10.8 and Linux
Hello Adamscomputerrepair,

Thanks for your reply.

I didn't think about a Dual Boot on the Mac but it makes sense as then Linux will be a current OS that a user can make use of even if the Mac OS is not compatible with a lot of current software.

I'll do some reading into 10.8 install. I only read through the 10.11 and 10.10 threads.

Thanks again for your input Adamscomputerrepair! :)
 

EugW

macrumors G5
Jun 18, 2017
14,878
12,855
Personally I dislike running Linux on Macs. Too many little issues and un-Mac-like behaviour (for obvious reasons). And to be honest, my personal macOS cutoff these days for daily use machines is 10.13 High Sierra. (I keep older machines around just for fun though.)
 

fbagnato

macrumors newbie
Jul 5, 2023
9
1
Hello EugW,

Thanks for your input.

I am planning to try a Linux system when I finish with the Mac OS X installation on the first of the iMacs.

I will have a play around with it and decide then whether to put Linux on the iMacs.

Unfortunately the iMac I am working on can't run 10.13 so I am stuck with older OS options.

Regards,

fbagnato
 

Adamscomputerrepair

macrumors 6502a
Aug 9, 2015
549
287
Hello EugW,

Thanks for your input.

I am planning to try a Linux system when I finish with the Mac OS X installation on the first of the iMacs.

I will have a play around with it and decide then whether to put Linux on the iMacs.

Unfortunately the iMac I am working on can't run 10.13 so I am stuck with older OS options.

Regards,

fbagnato
Back in the day, I triple booted my Macs. 10.8 for Mac apps, Ubuntu for Linux apps and VM stuff, and Windows 10 for anything those two couldn’t handle. It can be done and there are plenty of guides out there to do it.
 

fbagnato

macrumors newbie
Jul 5, 2023
9
1
Sounds good but I don't have any spare licenses for Windows so I will be looking at Mac OS X / Linux Dual Boot setup for the iMacs.
 

fbagnato

macrumors newbie
Jul 5, 2023
9
1
Well I didn't get very far.

I installed macOS Extractor v1.45 and it installed fine (I selected Customize and selected El Capitan instead of the default Sierra).

I then tried to run the AutoPatch package.

I ran it a million times, ok, less than that but it keeps ending in an error after it says "Cleaning Up"

I don't know what the problem is and would appreciate if someone can tell me what is wrong.

I have attached the Log File.

Regards,

fbagnato
 

Attachments

  • Installer Log 14-Jul-2023.txt
    15.2 KB · Views: 88

SergueiTemp

macrumors member
May 20, 2005
59
56
Seoul
After years of working with El Capitan my 2007 Mac Mini (4 gb, I installed additional stick) now refuses to boot (infinite Apple logo). When I'm trying to load anything - safe mode, recovery, diagnostics - it gives kernel panic error and Mac OS version - not set. Also I sometimes see OS X hackers logo so I assume I used patcher to install El Capitan to this Mac mini. But now it seems corrupted and I have no way to restore it to factory state. Can EFI partition somehow be restored to factory?
 

ikir

macrumors 68020
Sep 26, 2007
2,175
2,366
MacPostfactor can no longer talk to Adfly and the installer always fail, any idea how to bypass ADfly check?
trying to install Mavericks on a upgraded Mac mini 2,1
 

IDoRandomThings

macrumors newbie
Aug 3, 2024
1
0
Hi everyone,

I recently managed to install OS X El Capitan onto my MacBook Pro 2,2. However, i can never use it for more than 2 minutes before it kernel panics. Below are the specs of my system and attached is a panic report i managed to get before it kernel panicked again.

Specs:
CPU: Intel Core 2 Duo 2.33 GHz
GPU: ATI Radeon X1600
RAM: 4GB

Panic report:
Anonymous UUID: 32C504F5-4DCE-386E-6EF9-B4D8A9E95387

Sat Aug 3 21:26:28 2024

*** Panic Report ***
panic(cpu 0 caller 0xffffff80141ce6fa): Kernel trap at 0xffffff7f94c8c42a, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x00007f9cbb014000, CR3: 0x000000007da5c000, CR4: 0x0000000000002660
RAX: 0x20258f3100000005, RBX: 0xffffff801d8944e0, RCX: 0xffffff8014883da0, RDX: 0x0000000000000001
RSP: 0xffffff90ab3cbf90, RBP: 0xffffff90ab3cbfb0, RSI: 0x0000000000000001, RDI: 0xffffff801d674a50
R8: 0x000000000024e85b, R9: 0xffffff801d894490, R10: 0x0000000000000000, R11: 0x0000002be12e542f
R12: 0xffffff7f94c917e8, R13: 0xffffff80148efbc8, R14: 0xffffff801d894490, R15: 0x20258f3100000005
RFL: 0x0000000000010206, RIP: 0xffffff7f94c8c42a, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00007f9cbb014000, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0

Backtrace (CPU 0), Frame : Return Address
0xffffff80842c4c50 : 0xffffff80140dab52
0xffffff80842c4cd0 : 0xffffff80141ce6fa
0xffffff80842c4eb0 : 0xffffff80141ec563
0xffffff80842c4ed0 : 0xffffff7f94c8c42a
0xffffff90ab3cbfb0 : 0xffffff80141c9117
Kernel Extensions in backtrace:
com.apple.kec.pthread(1.0)[39D0B4EB-B7F4-3891-96C2-F8B886656C8A]@0xffffff7f94c87000->0xffffff7f94c93fff

BSD process name corresponding to current thread: tccd
Boot args: -no_compat_check kext-dev-mode=1 mbasd=1

Mac OS version:
15G31

Kernel version:
Darwin Kernel Version 15.6.0: Thu Jun 23 18:25:34 PDT 2016; root:xnu-3248.60.10~1/RELEASE_X86_64
Kernel UUID: B5AA8E3E-65B6-3D0E-867B-8DCCF81E536C
Kernel slide: 0x0000000013e00000
Kernel text base: 0xffffff8014000000
__HIB text base: 0xffffff8013f00000
System model name: MacBookPro2,2 (Mac-F4238BC8)

System uptime in nanoseconds: 188461618374
last loaded kext at 23228738773: com.apple.driver.pmtelemetry 1 (addr 0xffffff7f95f92000, size 61440)
loaded kexts:
com.apple.driver.pmtelemetry 1
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.iokit.IOBluetoothSerialManager 4.3.6f3
com.apple.driver.AppleUpstreamUserClient 3.6.1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleTyMCEDriver 1.0.2d2
com.apple.driver.AppleMuxControl 3.12.8
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleHV 1
com.apple.driver.AppleBacklight 170.8.9
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.AppleSMCLMU 208
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleLPC 3.1
com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0
com.apple.driver.AppleFIVRDriver 4.1.0
com.apple.driver.AppleMCCSControl 1.2.13
com.apple.driver.SMCMotionSensor 3.0.4d1
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleUSBTrackpad 240.2
com.apple.driver.AppleUSBTCKeyEventDriver 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.CSRHIDTransitionDriver 4.3.6f3
com.apple.driver.AppleIRController 327.5
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0
com.apple.BootCache 38
com.apple.iokit.SCSITaskUserClient 3.7.7
com.apple.iokit.IOAHCIBlockStorage 2.8.5
com.apple.driver.AppleUSBHub 705.4.2
com.apple.iokit.AppleYukon2 3.2.3b1
com.apple.driver.AppleUSBEHCI 705.4.14
com.apple.driver.AppleFWOHCI 5.5.4
com.apple.driver.AppleAHCIPort 3.1.8
com.apple.driver.AppleIntelPIIXATA 2.5.1
com.apple.driver.AirPort.Atheros40 700.74.5
com.apple.driver.AppleUSBUHCI 656.4.1
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleACPIButtons 4.0
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 4.0
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 218.0.0
com.apple.nke.applicationfirewall 163
com.apple.security.quarantine 3
com.apple.security.TMSafetyNet 8
com.apple.driver.AppleIntelCPUPowerManagement 218.0.0
com.apple.iokit.IOSurface 108.2.3
com.apple.iokit.IOSerialFamily 11
com.apple.iokit.IOBluetoothFamily 4.3.6f3
com.apple.driver.CoreCaptureResponder 1
com.apple.driver.AppleGraphicsControl 3.12.8
com.apple.driver.AppleBacklightExpert 1.1.0
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.driver.AppleSMBusPCI 1.0.14d1
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.IOPlatformPluginFamily 6.0.0d7
com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0
com.apple.driver.AppleSMBusController 1.0.14d1
com.apple.kext.AMDSupport 1.4.2
com.apple.AppleGraphicsDeviceControl 3.12.8
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.driver.AppleSMC 3.1.9
com.apple.kext.triggers 1.0
com.apple.iokit.IOUSBUserClient 705.4.0
com.apple.iokit.IOUSBHIDDriver 705.4.0
com.apple.driver.AppleUSBMergeNub 705.4.0
com.apple.driver.AppleUSBComposite 705.4.9
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.7.7
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.8
com.apple.iokit.IOCDStorageFamily 1.8
com.apple.driver.AppleXsanScheme 3
com.apple.iokit.IOATAPIProtocolTransport 3.5.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.7
com.apple.iokit.IOFireWireFamily 4.6.1
com.apple.iokit.IOAHCIFamily 2.8.1
com.apple.iokit.IOATAFamily 2.5.3
com.apple.iokit.IO80211Family 1110.26
com.apple.iokit.IONetworkingFamily 3.2
com.apple.driver.corecapture 1.0.4
com.apple.iokit.IOUSBFamily 720.4.4
com.apple.driver.AppleEFINVRAM 2.0
com.apple.iokit.IOUSBHostFamily 1.0.1
com.apple.driver.AppleUSBHostMergeProperties 1.0.1
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.DiskImages 417.4
com.apple.iokit.IOStorageFamily 2.1
com.apple.iokit.IOReportFamily 31
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 4.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.pthread 1
com.apple.kec.corecrypto 1.0
Model: MacBookPro2,2, BootROM MBP22.00A5.B07, 2 processors, Intel Core 2 Duo, 2.16 GHz, 4 GB, SMC 1.12f5
Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 5 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F7FFE0000000000, 0x4542453231554538414355412D36452D4520
Memory Module: BANK 1/DIMM1, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F7FFE0000000000, 0x4542453231554538414355412D36452D4520
AirPort: AirPort Extreme, Atheros 5416: 4.0.74.0-P2P
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Crucial_CT240M500SSD1, 240.06 GB
Parallel ATA Device: MATSHITADVD-R UJ-857D
Thunderbolt Bus:

Can anyone find out what the issue is and how to solve it? Thanks!
 

AD1234567890

macrumors newbie
Oct 25, 2024
23
18
To everyone experiencing the same issue as me, meaning a MacBook2,1 (Late 2006 or Mid 2007) that restarts by itself after 2 minutes on OS X El Capitan using Julian Fairfax’s osx-patcher: I have the solution! THANK YOU FOR READING:

I spent days trying to figure out how to get OS X El Capitan to work as it should on my Mid-2006 MacBook... and I finally found how to fix it. Since no one has published the solution so far, here it is.

This solution works at least for a MacBook2,1 (Late 2006 or Mid 2007). Since I don’t have other models, I’m not sure if it works for them, but feel free to try.

Why does the Mac restart by itself? Simply because the EFI (boot.efi) injected by osx-patcher is broken.

Here’s what I did (from start to finish):

To install OS X El Capitan, I used... a compatible MacBook. It may sound silly, but it was the only way for me to do it. When I tried installing it directly on my Late 2006 MacBook, it would restart after a few minutes (likely due to the EFI issue), or even with other versions of osx-patcher, the USB installer wouldn’t even boot. :/

So, I burned the OS X El Capitan installer with the latest version of osx-patcher (https://gitlab.com/0403979/osx-patcher/-/archive/main/osx-patcher-main.zip), took the hard drive out of my Late 2006 MacBook, put it in my Mid-2009 MacBook Pro, plugged in the OS X El Capitan USB installer (with SIP disabled beforehand), and installed it normally on my hard drive (note that the trackpad and keyboard of the MacBook Pro don’t work here, so I used an external keyboard). Just before it restarted, I clicked the menu to open Terminal, typed "patch", selected "use an existing model", chose MacBook2,1, selected the partition, and it "patched" the OS X El Capitan installation. Then I shut down the MacBook Pro.

I removed the hard drive, put it back in the MacBook, and since I have multiple macOS systems in dual boot on this drive, I handled it this way, but it might be different for you. In any case, I had another partition with OS X Mountain Lion, so I booted into this partition and started editing the boot.efi files.

As I mentioned earlier, the boot.efi file provided with osx-patcher doesn’t work with El Capitan. So you need to download the other boot.efi file (https://www.dropbox.com/s/akp2vdwaes0hf85/EC-EFI32-SIP-disabled-boot.efi-v3.zip?dl=1 - File designed for Macs with EFI32). Then, you need to replace the broken boot.efi file from osx-patcher with the working one we just downloaded.

You need to replace it in 2 locations (within your El Capitan partition): /Volumes/(your partition)/System/Library/CoreServices/ /Volumes/(your partition)/usr/standalone/i386/

Step 1: You need to change the flags for these 2 boot.efi files, so enter the following commands in Terminal:

cd /Volumes/(your partition)/System/Library/CoreServices/
sudo chflags nouchg boot.efi
cd /Volumes/(your partition)/usr/standalone/i386/
sudo chflags nouchg boot.efi

Step 2: Using Finder, go to the folder /Volumes/(your partition)/System/Library/CoreServices/; you’ll see a boot.efi file, take your new boot.efi and replace it in there.

Step 3: Do the same for /Volumes/(your partition)/usr/standalone/i386/

Step 4: Assign the correct owner to these two files. Use the terminal:

cd /Volumes/(your partition)/System/Library/CoreServices/
sudo chown root:wheel boot.efi
cd /Volumes/(your partition)/usr/standalone/i386/
sudo chown root:wheel boot.efi

Step 5: Change the flags back on the two boot.efi files:

cd /Volumes/Capitann/System/Library/CoreServices/
sudo chflags uchg boot.efi
cd /Volumes/Capitann/usr/standalone/i386/
sudo chflags uchg boot.efi

Then, boot into the El Capitan partition, and magically, there is no more kernel panic after a few minutes!

BONUS: How to update OS X El Capitan

Step 1: Do the update via the Mac App Store.
Step 2: Boot from the El Capitan USB installer (this is crucial, don’t do it on another partition, use the USB installer), and patch your El Capitan partition like you did initially.
Step 3: Repeat the steps to replace the two EFI files like we did earlier.

And there you have it, you now have a Late 2006 or Mid 2007 MacBook running El Capitan!
 
Last edited by a moderator:
  • Like
Reactions: Hasefroch

Hasefroch

macrumors member
Oct 5, 2024
34
10
Argentina
To everyone experiencing the same issue as me, meaning a MacBook2,1 (Late 2006 or Mid 2007) that restarts by itself after 2 minutes on OS X El Capitan using Julian Fairfax’s osx-patcher: I have the solution! THANK YOU FOR READING:

I spent days trying to figure out how to get OS X El Capitan to work as it should on my Mid-2006 MacBook... and I finally found how to fix it. Since no one has published the solution so far, here it is.

This solution works at least for a MacBook2,1 (Late 2006 or Mid 2007). Since I don’t have other models, I’m not sure if it works for them, but feel free to try.

Why does the Mac restart by itself? Simply because the EFI (boot.efi) injected by osx-patcher is broken.

Here’s what I did (from start to finish):

To install OS X El Capitan, I used... a compatible MacBook. It may sound silly, but it was the only way for me to do it. When I tried installing it directly on my Late 2006 MacBook, it would restart after a few minutes (likely due to the EFI issue), or even with other versions of osx-patcher, the USB installer wouldn’t even boot. :/

So, I burned the OS X El Capitan installer with the latest version of osx-patcher (https://gitlab.com/0403979/osx-patcher/-/archive/main/osx-patcher-main.zip), took the hard drive out of my Late 2006 MacBook, put it in my Mid-2009 MacBook Pro, plugged in the OS X El Capitan USB installer (with SIP disabled beforehand), and installed it normally on my hard drive (note that the trackpad and keyboard of the MacBook Pro don’t work here, so I used an external keyboard). Just before it restarted, I clicked the menu to open Terminal, typed "patch", selected "use an existing model", chose MacBook2,1, selected the partition, and it "patched" the OS X El Capitan installation. Then I shut down the MacBook Pro.

I removed the hard drive, put it back in the MacBook, and since I have multiple macOS systems in dual boot on this drive, I handled it this way, but it might be different for you. In any case, I had another partition with OS X Mountain Lion, so I booted into this partition and started editing the boot.efi files.

As I mentioned earlier, the boot.efi file provided with osx-patcher doesn’t work with El Capitan. So you need to download the other boot.efi file (https://www.dropbox.com/s/akp2vdwaes0hf85/EC-EFI32-SIP-disabled-boot.efi-v3.zip?dl=1 - File designed for Macs with EFI32). Then, you need to replace the broken boot.efi file from osx-patcher with the working one we just downloaded.

You need to replace it in 2 locations (within your El Capitan partition): /Volumes/(your partition)/System/Library/CoreServices/ /Volumes/(your partition)/usr/standalone/i386/

Step 1: You need to change the flags for these 2 boot.efi files, so enter the following commands in Terminal:

cd /Volumes/(your partition)/System/Library/CoreServices/
sudo chflags nouchg boot.efi
cd /Volumes/(your partition)/usr/standalone/i386/
sudo chflags nouchg boot.efi

Step 2: Using Finder, go to the folder /Volumes/(your partition)/System/Library/CoreServices/; you’ll see a boot.efi file, take your new boot.efi and replace it in there.

Step 3: Do the same for /Volumes/(your partition)/usr/standalone/i386/

Step 4: Assign the correct owner to these two files. Use the terminal:

cd /Volumes/(your partition)/System/Library/CoreServices/
sudo chown root:wheel boot.efi
cd /Volumes/(your partition)/usr/standalone/i386/
sudo chown root:wheel boot.efi

Step 5: Change the flags back on the two boot.efi files:

cd /Volumes/Capitann/System/Library/CoreServices/
sudo chflags uchg boot.efi
cd /Volumes/Capitann/usr/standalone/i386/
sudo chflags uchg boot.efi

Then, boot into the El Capitan partition, and magically, there is no more kernel panic after a few minutes!

BONUS: How to update OS X El Capitan

Step 1: Do the update via the Mac App Store.
Step 2: Boot from the El Capitan USB installer (this is crucial, don’t do it on another partition, use the USB installer), and patch your El Capitan partition like you did initially.
Step 3: Repeat the steps to replace the two EFI files like we did earlier.

And there you have it, you now have a Late 2006 or Mid 2007 MacBook running El Capitan!
Hello, I have the MacBook2,1 but I don't have another Mac at all, what could I do? I'm on perfectly working Lion 10.7.5. I'm trying to use that patcher and it always give errors, and at one time I created an USB Installer, but can't boot it. I will try with 10.10 or 10.9 at this time
I also have Windows computers with modern hardware and software, I can download and make things here
 
Last edited:
  • Like
Reactions: AD1234567890

AD1234567890

macrumors newbie
Oct 25, 2024
23
18
Hello,

For the answer : I don't know what to do unfortunately in your case, sorry ... I really tried to do this since 2015, all the steps on an unsupported Mac (the same MacBook2,1), and it nevers works :/ To be precise :
-First, i used this installer : https://archive.org/details/el-capitan-installer-app ... I don't know why but it seems that this install is less buggy than others
-On the actual version of osx-patcher (1.3.1), so when I boot the USB flash drive made with it, on my MacBook2,1, it goes to a black screen with white Apple logo, then 1 second later, the colors are "inverted", and this is booting to another partition on the hard drive
-On the old version, I don't remember ... 1.2.1 ? When I boot the USB Flash drive made with it, it goes to a black screen with white Apple logo (take note of this detail this is important for what I will say), then it goes to the actual installer. But when you install around 2 minutes later, the Mac actually shut off itself and reboot with saying that there was a Kernel Panic.

This is interesting, because at first I made a El Capitan installer with osx-patcher 1.3.1, it took the hard drive of my MacBook2,1, put this on my MacBook Pro, then I installed it on this MacBook Pro, after the installation I patched the hard drive, then I power off the MacBook Pro and I put back my hard drive on my MacBook2,1, without doing all the others next steps (like the previous post). And then when I booted the El Capitan partition on my MacBook2,1, it goes on the same black screen with white Apple logo, and white progress bar, then we are in El Capitan, but it also shut off 2 minutes after this, like a lot of people.

Then I searched on this forum, and I saw also someone few years ago that said that the cause of random kernel panic is because of the boot.efi file ... So I downloaded the boot.efi, specifically made of EFI32 Macs ... I did the steps in my previous post, and take note of this thing : after replacing the boot.efi file ... the boot screen has changed ! Now it is white background with grey Apple logo and progress bar.

What I want to say here ... Like I said unfortunately, I didn't have the solution to make this work only with a MacBook2,1 ... but maybe I have a part of the solution : maybe on the USB Flash drive of the El Capitan installer, try to find alls the boot.efi file that is loaded when you boot the El Capitan installer ... then replace it with the boot.efi file for EFI32 Macs ... and maybe now it should work ... I hope ... I tried to find the file ... but I never found it (I was missing time, I already spend 3-4 days again to try to install El Capitan on this ... but at the end after 9 years ... I finally have El Capitan on this MacBook2,1)

Maybe if one day I have the time to do this ... maybe I will make an image of an El Capitan partition compatible with MacBook2,1, so that after this ... maybe all people will be able to do this, without having a compatible machine, I will see
 
  • Like
Reactions: Hasefroch

AD1234567890

macrumors newbie
Oct 25, 2024
23
18
And I also forget ... for the fact that with osx-patcher 1.3.1 ... it reboots to another partition like immediatly when you boot on an unsupported Mac ... I just remember i saw this on the first post :

If the Installation Drive boots you back to the main partition, try blessing the drive from your terminal app:
Code:
sudo bless --folder /Volumes/[Installation Drive Name] --file /Volumes/[Installation Drive Name]/boot --setBoot

So maybe there is also something to do with this line of code ... I don't exactly remember, but I think I tried this, and it dosen't work ... So I don't know
 
  • Like
Reactions: Hasefroch

Hasefroch

macrumors member
Oct 5, 2024
34
10
Argentina
Hello,

For the answer : I don't know what to do unfortunately in your case, sorry ... I really tried to do this since 2015, all the steps on an unsupported Mac (the same MacBook2,1), and it nevers works :/ To be precise :
-First, i used this installer : https://archive.org/details/el-capitan-installer-app ... I don't know why but it seems that this install is less buggy than others
-On the actual version of osx-patcher (1.3.1), so when I boot the USB flash drive made with it, on my MacBook2,1, it goes to a black screen with white Apple logo, then 1 second later, the colors are "inverted", and this is booting to another partition on the hard drive
-On the old version, I don't remember ... 1.2.1 ? When I boot the USB Flash drive made with it, it goes to a black screen with white Apple logo (take note of this detail this is important for what I will say), then it goes to the actual installer. But when you install around 2 minutes later, the Mac actually shut off itself and reboot with saying that there was a Kernel Panic.

This is interesting, because at first I made a El Capitan installer with osx-patcher 1.3.1, it took the hard drive of my MacBook2,1, put this on my MacBook Pro, then I installed it on this MacBook Pro, after the installation I patched the hard drive, then I power off the MacBook Pro and I put back my hard drive on my MacBook2,1, without doing all the others next steps (like the previous post). And then when I booted the El Capitan partition on my MacBook2,1, it goes on the same black screen with white Apple logo, and white progress bar, then we are in El Capitan, but it also shut off 2 minutes after this, like a lot of people.

Then I searched on this forum, and I saw also someone few years ago that said that the cause of random kernel panic is because of the boot.efi file ... So I downloaded the boot.efi, specifically made of EFI32 Macs ... I did the steps in my previous post, and take note of this thing : after replacing the boot.efi file ... the boot screen has changed ! Now it is white background with grey Apple logo and progress bar.

What I want to say here ... Like I said unfortunately, I didn't have the solution to make this work only with a MacBook2,1 ... but maybe I have a part of the solution : maybe on the USB Flash drive of the El Capitan installer, try to find alls the boot.efi file that is loaded when you boot the El Capitan installer ... then replace it with the boot.efi file for EFI32 Macs ... and maybe now it should work ... I hope ... I tried to find the file ... but I never found it (I was missing time, I already spend 3-4 days again to try to install El Capitan on this ... but at the end after 9 years ... I finally have El Capitan on this MacBook2,1)

Maybe if one day I have the time to do this ... maybe I will make an image of an El Capitan partition compatible with MacBook2,1, so that after this ... maybe all people will be able to do this, without having a compatible machine, I will see
Yes, I also got the black screen with white Apple and then booted back into Lion.
I'm trying with Yosemite 10.10 now (I'm downloading on the MacBook with the script mac OS Downloader that gives me the "Install OS X Yosemite" app
I always have a Snow Leopard bootable USB in case of things go wrong
 

Hasefroch

macrumors member
Oct 5, 2024
34
10
Argentina
And I also forget ... for the fact that with osx-patcher 1.3.1 ... it reboots to another partition like immediatly when you boot on an unsupported Mac ... I just remember i saw this on the first post :

If the Installation Drive boots you back to the main partition, try blessing the drive from your terminal app:
Code:
sudo bless --folder /Volumes/[Installation Drive Name] --file /Volumes/[Installation Drive Name]/boot --setBoot

So maybe there is also something to do with this line of code ... I don't exactly remember, but I think I tried this, and it dosen't work ... So I don't know
I also tried that, but doesn't work
I'm trying now with 10.10
 
  • Like
Reactions: AD1234567890

AD1234567890

macrumors newbie
Oct 25, 2024
23
18
For 10.10 ... I remember I tried also with osx-patcher, with another older version, and it worked, and I didn't have to use another Mac for this ...

But the problem is ... if you see the Julian's page ... I remember almost all the versions was deleted between last year and now :/ And I didn't save the precise version that works with Yosemite on MacBook2,1 ... I tried all the versions that are present now ... and first I also have the need to do the installation on another supported Mac and also ... we have the same problem : it reboots itself after some minutes (For El Capitan it's around 2 minutes, for Yosemite, for some reason it's around 10 minutes ...). And maybe this is also because of the buggy boot.efi that the osx-patcher provides.
 
  • Like
Reactions: Hasefroch
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.