*** Always Backup your Mac ***
So I was using the uninstaller for leopard rebirth, when I accidentally deleted the file it was restoring from mid-process. the computer acted all weird and it would launch applications.
Yes. That would certainly cause a problem! I feel partly responsible for your broken OS.
The uninstaller has a very basic safety net, but I didn't factor in that... (With great power comes great responsibility!)
I plan to port the codebase back to Tiger for a "TigerSierra Remover" shortly and I'll put in a lock to prevent unmounting/deleting while the uninstallation is in progress. (Thanks for uncovering this shortcoming!)
How things are operating behind the scenes;
1. First,
LeopardRebirth Remover will copy the file from the restore point across to the system, putting the file in the correct destination folder and appending the file name with .restoreFromLR. This "atomic" copy ensures we don't overwrite the destination file without first confirming the byte size of the copy matches the restore source file.
2. Once confirmed that the copy was successful, the system file is deleted
3. Once deletion is confirmed, the .restoreFromLR extension is removed from the file name to lock it in.
I am just taking a guess, but perhaps one of these steps became unstuck.
Try this:
Boot into single-user mode as
@bunnspecial recommended and check that the following 4 files exist:
/System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/Resources/ArtFile.bin
/System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/Resources/SArtFile.bin
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/Resources/Extras.rsrc
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/Resources/Extras2.rsrc
(Confirm the files exist with
ls /path/to/file - hit the Tab key to auto-complete as you are beginning to type out each of the path sub-directory names).
These resource files are critical for the OS to boot. If any of these files exist with a .restoreFromLR extension, then rename the file, removing the extension:
e.g.
Code:
mv /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/Resources/ArtFile.bin.restoreFromLR /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/Resources/ArtFile.bin
Then
exit or
reboot to leave single user mode.
Once you boot back to your desktop, mount the
LRRRestoreResource.dmg bundled with
LeopardRebirth Remover and run through the uninstallation again. Let it run through without touching anything and then reboot.
All should then be A OK.
-- If the resource files are missing, then the options are:
1. Reinstall from an installation disc.
2. Put the Power Mac into Target Disk Mode and mount the boot volume on another Mac's desktop, then manually restore those four files from the other Mac (only if they are running the same System version e.g. 10.5.8)
3. If you have a Time Machine backup of before you ran the uninstallation, you can use that to restore the specific resource files, or simply do a complete Time Machine restore.
*** Always Backup your Mac ***
[doublepost=1506321129][/doublepost]
Option 4 would be to manually restore the files from the LRRRestoreResource.dmg image when your G5's boot volume is mounted via TDM on another Mac. This can include a non-PowerPC Mac which has a FireWire port (such as a MBP '15 or similar with a Lightning->FW adapter or an earlier MB/MBP/Mini/MP with a FW800 or 400 port).
If any other ideas pop into my head, I'll post it up. Someone else might have something to contribute? (e.g. can single-user mode see files on a USB stick? I've never tried)