 |
 |
I screwed up my BootX file
|
|
|
|
|
Mac Elite
Join Date: Feb 2002
Location: Hilton Head, SC
Status:
Offline
|
|
I was trying to change my bootx file on my system to another boot image and it now keeps my system from booting... what can i do to restore the file?
|
|
|
| |
|
|
|
|
|
|
|
Grizzled Veteran
Join Date: Dec 2000
Location: Málaga, Spain, Europe, Earth, Solar System
Status:
Offline
|
|
Well, if you don't have a backup you will have to reinstall the OS.
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Feb 2002
Location: Hilton Head, SC
Status:
Offline
|
|
All for screwing up one file? Without any evidence... which you did not supply (hey, maybe you're in a hurry) I'm forced to stress for a second opinion.
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: May 2002
Location: New York City
Status:
Offline
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
Dedicated MacNNer
Join Date: Apr 2003
Location: Rochester, NY
Status:
Offline
|
|
Do you realize the importance of that one file?
|
|
|wishing is for suckers|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Feb 2002
Location: Hilton Head, SC
Status:
Offline
|
|
You people are killing me. No... would I be here askig for a way to get the file had I made a backup? Yes... that's what they all warn me on,,,, the BOOTX file!!! AHHHHHHHHHH!! 
|
|
|
| |
|
|
|
|
|
|
|
Clinically Insane
Join Date: Oct 2001
Location: San Diego, CA, USA
Status:
Offline
|
|
If you don't have a backup of BootX, I can't see any way you're going to get it back short of reinstalling. It's one of the core system files. You can't boot from the drive without it, so you'll need to either a) use a second hard drive and restore from a backup (any working installation of the same OS version will do, to my knowledge), or b) reinstall OS X on that drive from the CD.
|
|
Chuck
___
"Instead of either 'multi-talented' or 'multitalented' use 'bisexual'."
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Feb 2002
Location: Hilton Head, SC
Status:
Offline
|
|
All for too much file trading... where's my mother... I'm going to kill her.
|
|
|
| |
|
|
|
|
|
|
|
Posting Junkie
Join Date: Dec 2000
Status:
Offline
|
|
All these people are wrong. You can get the BootX file back, and it's easy to do.
1. Boot from something that you can mount the problematic hard drive with. If you have another bootable partition on the drive, boot from that. Otherwise, you can connect another Mac to your Mac by running a FireWire cable from your FireWire port to the other Mac's FireWire port and boot your Mac into FireWire Target Mode by holding down T at startup, which will cause your hard drive to show up on the other Mac's desktop. Another thing you could do would be to download my BootCD and make a boot CD on another Mac that you can use to boot your Mac. Unfortunately, though, BootCD isn't compatible with 10.3.x yet, so you'll have to find a Mac that is still running 10.2.x in order to do this.
Once you find something you can boot your machine with, just do the following:
2. Move the current BootX file out of the CoreServices folder (don't just delete it, just in case something goes wrong and we need it back). You can do this with the following Terminal commands if the Finder won't let you:
cd /Volumes/"<hard disk name here, with quotes around it>"/System/Library/CoreServices
sudo mv BootX ../../..
3. Bless the CoreServices folder on the drive, using this command:
sudo bless -folder /Volumes/"<hard disk name here, with quotes around it>"/System/Library/CoreServices -bootinfo /Volumes/"<hard disk name here, with quotes around it>"/usr/standalone/ppc/bootx.bootinfo
That ought to create a new BootX file in your CoreServices folder. If it boots, you can safely delete the old BootX file, which should be sitting at the root of the drive.
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Feb 2003
Status:
Offline
|
|
have you tried moving a bootx file from another computer and place it in your coreservices folder?
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Feb 2002
Location: Hilton Head, SC
Status:
Offline
|
|
Originally posted by CharlesS:
All these people are wrong. You can get the BootX file back, and it's easy to do.
1. Boot from something that you can mount the problematic hard drive with. If you have another bootable partition on the drive, boot from that. Otherwise, you can connect another Mac to your Mac by running a FireWire cable from your FireWire port to the other Mac's FireWire port and boot your Mac into FireWire Target Mode by holding down T at startup, which will cause your hard drive to show up on the other Mac's desktop. Another thing you could do would be to download my BootCD and make a boot CD on another Mac that you can use to boot your Mac. Unfortunately, though, BootCD isn't compatible with 10.3.x yet, so you'll have to find a Mac that is still running 10.2.x in order to do this.
Once you find something you can boot your machine with, just do the following:
2. Move the current BootX file out of the CoreServices folder (don't just delete it, just in case something goes wrong and we need it back). You can do this with the following Terminal commands if the Finder won't let you:
cd /Volumes/"<hard disk name here, with quotes around it>"/System/Library/CoreServices
sudo mv BootX ../../..
3. Bless the CoreServices folder on the drive, using this command:
sudo bless -folder /Volumes/"<hard disk name here, with quotes around it>"/System/Library/CoreServices -bootinfo /Volumes/"<hard disk name here, with quotes around it>"/usr/standalone/ppc/bootx.bootinfo
That ought to create a new BootX file in your CoreServices folder. If it boots, you can safely delete the old BootX file, which should be sitting at the root of the drive.
thanks worked perfectly... (puts shootgun away)
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
|
Top
