Firstly my system could not boot up, so I tried -s and got
Still waiting for boot device.
I then set SATA MODE to ACHI in the BIOS
Tried to boot the system and it worked.
NO SOUND
NO WiFi
All these worked after installing Kext from the
Extensions backupHere is the Guide I used from
Insanelymac1. Download the 10.5.3 Combo Update from the Apple website
2. run Terminal and type:
CODE
sudo su
then type your password
then paste
CODE
while sleep 1; do rm -rf /System/Library/Extensions/AppleIntelCPUPowerManagement.kext; done
and hit enter
(nothing seems to happen but it is now monitoring your Extensions folder for the AppleInterCPUPowerManagement.kext file (folder))
You can, for safety, open a Finder window in the folder /System/Library/Extensions and look for that file (sort by filename of course), and you willl see it'll be removed automatically within a few seconds after it's created in step 3.
3. Run the MacOSXUpd10.5.3.pkg file in the MacOSXUpd10.5.3.dmg you just downloaded, and follow the instructions, but do not reboot at the end.
4. When the installation finishes, do not press reboot. Go back to your terminal window and hit ctrl+c. This will stop the script from running. In my case, there was some kind of error, but that's okay.
5. type
CODE
nano /System/InstallAtStartup/scripts/1
A very simple text editor within Terminal will appear. Note you can't use your mouse to click to a certain line/point. 'Walk down' using your arrow keys to the line that contains
CODE
"/System/Library/Extensions/Dont Steal Mac OS X.kext"
In this line, replace
CODE
Dont Steal Mac OS X.kext
with
CODE
dsmos.kext
Now hit ctrl+o, enter, ctrl+x (this first saves the file, confirms it, then closes the editor).
Type
CODE
exit
and close Terminal.
6. Return to the installer window and click reboot. If you need to restore some kexts, you can do that before or after rebooting, doesn't really matter. I recommend doing it after rebooting, to see which things still work (so you have the latest drivers for those).
It will reboot, right up until the point that the screen would usually turn blue, then reboot again, and all should be well. I guess it has to reboot twice to execute the commands within the /System/InstallAtStartup/scripts/1 file we just edited, and has to reboot again after that.
