I chuckle when I read posts, and solutions, like those posted above by the OP and respondents.
There are ways that are so much easier, that folks will never understand unless they try.
The "quick and easy" solution to "getting back to where you once belonged" after an upgrade-gone-wrong is to have a bootable cloned backup of your prior installation on an external drive.
You can make one with either CarbonCopyCloner or SuperDuper.
If things go wrong with the upgrade, it's simple and trivial to do this:
1. Boot from the backup
2. Re-initialize the internal drive.
3. RE-CLONE the "cloned backup" BACK TO the internal drive.
Three simple steps, and takes only as long as the time spent "in the copying" of step 3.
Frankly, I think those who jump at installing beta software onto their "main, working machines" are nuts.
I "test fly" all the latest software on external drives that exist "for test purposes only".
This way I can fool with the latest betas, while leaving "my important stuff" Untouched!
There are ways that are so much easier, that folks will never understand unless they try.
The "quick and easy" solution to "getting back to where you once belonged" after an upgrade-gone-wrong is to have a bootable cloned backup of your prior installation on an external drive.
You can make one with either CarbonCopyCloner or SuperDuper.
If things go wrong with the upgrade, it's simple and trivial to do this:
1. Boot from the backup
2. Re-initialize the internal drive.
3. RE-CLONE the "cloned backup" BACK TO the internal drive.
Three simple steps, and takes only as long as the time spent "in the copying" of step 3.
Frankly, I think those who jump at installing beta software onto their "main, working machines" are nuts.
I "test fly" all the latest software on external drives that exist "for test purposes only".
This way I can fool with the latest betas, while leaving "my important stuff" Untouched!