Post by: petegas on February 26, 2004, 08:55:00 AM
I installed a Xenium in my buddies box, and he's fairly new the the Xbox scene. I told him about how great the xenium was because you dont' have to worry about bad bios flashes, blah blah blah, and to just play around as he pleased. I also set up EVO-X for him and a couple apps.
One thing I didn't think of was that he'd choose the 'restore EEPROM' menu option in XOS before ever choosing to 'backup EEPROM'. Now I would have figured that the Xenium would at least set a flag or something when the EEPROM is backed up to prevent what happened, but apparantly not. So yup, he wiped his eeprom with whatever garbage happened to ship in the Xenium's EEPROM backup address range.
Since his HD was locked, of course he got the ol' Error 6 whenever he tried to boot anything as the HD lock key was no more. just by luck, when I installed evo-x for him I backed up his eeprom onto the c:\ drive, and backed it up onto PC.
The newest beta of XBTool has the ability to embed EEPROM into the BIOS, which got the box back up so we could flash his eeprom back with good data.
Not sure if this has changed in XoS 1.1, but it would be handy to be able to flash eeprom from CD in XOS.
Post by: Artifex on February 26, 2004, 09:16:00 AM
After a couple of reports of this, however, it's not something we're just going to ignore. We will add in some additional precautions, but as there doesnt seem to be a bug there to fix, we suspect that something else may be the culprit in these cases.
--Artifex
Post by: warbeast on February 26, 2004, 11:34:00 AM
Post by: petegas on February 26, 2004, 11:49:00 AM
| QUOTE (Artifex @ Feb 26 2004, 07:16 PM) |
| XOS checks to see if there is a valid eeprom backup on each boot. If not, it takes a backup of the eeprom. It should not be possible to "restore" an eeprom that hasnt been backed up yet. After a couple of reports of this, however, it's not something we're just going to ignore. We will add in some additional precautions, but as there doesnt seem to be a bug there to fix, we suspect that something else may be the culprit in these cases. --Artifex |
'as there doesnt seem to be a bug there to fix, we suspect that something else may be the culprit in these cases.'
- if the Xenium is supposed to take a valid backup of the eeprom on XOS boot if one does not exist, then there is a bug, as this did not happen! I don't know what else could be considered a culprit in this case, as the XOS is the first thing to come up when powering on your box.
I'm glad to hear this isn't supposed to happen, anyway. Being an engineer myself I know how hard something like this can be to track down and fix if you cannot reproduce it in your dev lab.
If this helps in any way, the very first time I powered up the box after the install the Xenium did not power up properly because of a bad solder join on one of the pinheader pins. Is it possible that this caused corrupt data to 'backed up' instead of the valid eeprom, and then after that the xenium did not attempt to back up the eeprom because it thought it had valid data?
Post by: oblox on February 27, 2004, 02:11:00 AM
) but I don't see why it's not possiable to do:XOS Boot
Check for valid eeprom
Non found
Check CD/HD for copy of backup valid eeprom
Found
Backup to Xenium
Then you already have reflash options on there
EDIT the one maybe difficult thing would be an option save eeprom to HD
Post by: petegas on February 27, 2004, 09:22:00 AM
| QUOTE (oblox @ Feb 27 2004, 12:11 PM) |
| EDIT the one maybe difficult thing would be an option save eeprom to HD |
Evo-x has long had the ability to backup eeprom to HD - this isn't a hard process. I strongly agree with the necessity to be able to recover eeprom from a CD/DVD.
Since not being able to access your HD is one of the symptoms of fuxoring your eeprom (if it is locked), the HD should be left out of the backup process in this case.
Post by: rahula on February 27, 2004, 09:37:00 AM
Post by: oblox on February 27, 2004, 11:40:00 AM
The best yet is if someone implements USB this way you could stick a memory card in to the xbox and backup to that
Creating the Xenium gamesave
Which could also be used to flash the chip add bioses etc
Reading discs and FTPing can cause problems especially for people who arn't all that good with computers but a save copied to a memory card that makes easy sence
Post by: warbeast on February 27, 2004, 06:01:00 PM
i'm just on about recovery because thats the only reason i want a new modchip to be more safe. i flashed my xbit with x2_4981 and my eeprom inside so it can boot with a blank onboard eeprom and allow me to use configmagic to recover if i ever need to.
you could boot the XOS even with a blank eeprom fine because its based on cromwell, then flash a bios with your eeprom inside if for some reason you cant recover the eeprom from the modchip then your beable to unlock the hdd and load configmagic from the hdd to recover
sorry about the txt need sleep 4am
