EEPROM (Xbox)
From Wiki-Scene
Contents |
It determines the console's:
- Serial number
- MAC address
- TV output settings (PAL or NTSC, resolution & aspect ratio)
- Xbox Live key
- DVD region
- HDD key used for drive locking
- Auto-off timer setting
Certain pieces of saved content are "locked" to your EEPROM and will not work with a system using a different one. This includes, for example, anything downloaded off Xbox Live, and some saved games (such as those generated by Team Ninja titles).
It is possible to alter the contents, using either LiveInfo (on your PC) or ConfigMagic (on the Xbox itself). Changing some system settings (such as the display resolution) will also trigger writes to the chip.
The EEPROM of one Xbox can even be copied to another, assuming the two are compatible. This would make them appear to be identical when using Live, for example (though since the service would spot a inconsistency in the hard drive serial numbers, it'd promptly ban that EEPROM). Cloning also duplicates the MAC address, which can cause problems if both consoles are connected to the same LAN, though that can be altered using the MS Dash.
It is strongly recommended to backup your EEPROM at the first available opportunity. Note that a backup is next to useless unless you copy it to your PC - If you simply extract it to your Xbox's hard drive, you may find it inaccessible when you need it due to drive locking. As the EEPROM is the "key" to this lock, failing to copy it elsewhere is the equivalent to locking your keys in the car.
Compatibility
While EEPROM chips are all the same, the data within is formatted differently between different console versions. Attempting to write a given EEPROM to an incompatible system can result in trouble.
Version 1.0 EEPROMs are only compatible with other 1.0 EEPROMs.
1.1 through to 1.5 EEPROMs are all compatible with each other.
1.6 and 1.6b EEPROMs are only compatible with each other.
LiveInfo and ConfigMagic can convert 1.0 EEPROMs to work with 1.1-1.5 systems, and vice versa. There is currently no tool available to convert 1.6/1.6b EEPROMs.
Virtual EEPROMs
Some softmods use a "fake" EEPROM in order to protect the "real" version. This can prevent you from getting a valid backup, or prevent you from changing system settings. If this feature is causing problems for you, there are a variety of methods to disable it:
- If you modded using ANY save game exploit, cold boot the disc you originally used (insert it, power the console off, then power it back on again). Load the save game and you'll be taken to the softmod installer screen with no virtual EEPROM active. Removing the game disc and rebooting will restore it.
- If you're using NDure, create an empty file called "EEPROM_off.bin" and place it either on the root of your E partition (if using Kingroach's 3.0 or Krazie's version) or in the E:\NKP11\ folder (if using Kingroach's 3.1 version) (there's no harm in putting the files in both locations if you're not sure). Reboot for the change to take effect.
- If all else fails, cold booting Frosty's Rescue Disc should temporarily disable a virtual EEPROM.
Obtaining Your EEPROM
Using The Console
It is by far easiest to gain a copy of your EEPROM when your console is functional and either soft or hard modded.
Some softmod installers (such as NDure) force you to extract your EEPROM to the console's HDD as part of the setup process. This can then be transfered to your PC (via FTP, for example).
ConfigMagic can also be used to rip a copy. When prompted to do so, press Start to open the menu, then select "Create Backup Files". Your EEPROM backup will be created on the root of the E partition, under the name "EEPROMBackup.bin".
The EvoX dashboard also has this function (it stores it where ever the dashboard itself is located).
When manually extracting the EEPROM with these programs, make sure you don't have a virtual copy active.
Checking The HDD With A PC
If your modified console becomes non-operational, there is a chance that the EEPROM can be recovered by manually looking around the HDD with Xplorer360. Note that this "chance" is entirely based on whether or not it's been extracted there from the real copy on the motherboard. If your console is unmodded (and has never BEEN modded), then this chance is nil. Likewise, if you haven't gone through a softmod installation or can't remember specifically extracting the file (either using ConfigMagic or the EvoX dashboard), then odds are it won't be there to find.
If your drive is locked then you will need to hotswap. Once this is done Xplorer360 should be able to browse it. EEPROM backups are usually entitled "EEPROM.bin" or similar. Drives which are not currently locked can simply be connected directly. LiveInfo can inform you of the locking status of a given drive, and also to confirm that the backup is good.
Using A Reader
If your console is non-operational or unmodded, so long as the EEPROM chip itself is still intact it's possible to obtain the information in it by connecting a reader to your computer. While you'll likely need to construct it yourself, the electrical knowledge/experience required is about equal to that of what the average high school student is taught. The parts usually cost less then $10US and are purchased from typical electronics shops.
Confirming A Backup
Once you've obtained a copy of your EEPROM, it's a good idea to check that the backup is valid. To do this, open the file with LiveInfo, then compare the serial number it shows you to the one written on the underside of your console.
If there is any discrepancy then you've made a mistake. However, some refurbished consoles have had their motherboards replaced (hence changing the serial in the EEPROM) - if this applies to you, then you should be able to find a sticker on the underside stating that it is refurbished.
Note that (once installed) some softmods use a "fake" EEPROM in order to protect the "real" version. This can prevent you from getting a valid backup.
Trouble Shooting
Unable To Change Settings
Some softmods use a "fake" EEPROM in order to protect the "real" version. Any EEPROM based settings you alter while such an EEPROM is active (for example, changing your display mode to high definition) may be lost on the next reboot. Simply disabling the virtual copy should solve the problem.
Red Blinking LED
If your LED is showing a red blinking error light, then you have a corrupt EEPROM. If this is the case then the console will not output any video or audio to your television set.
This can be caused by a software glitch, user error, or perhaps the chip itself has become degraded.
There are a variety of possible fixes:
- Flashing With A Reader
An EEPROM reader can be hooked up between your computer and Xbox to write a backup to the chip. Obviously this method will not help you if you haven't obtained a backup prior to the chip malfunctioning, and there's always the chance that the chip is truly dead and a fresh write won't help.
While you'll likely need to construct it yourself, the electrical knowledge/experience required is about equal to that of what the average high school student is taught. The parts usually cost less then $10US and are purchased from typical electronics shops.
- Using A Modchip
The installation of a modchip allows you to use BIOS types specially tailored for dealing with corrupt EEPROMs.
The X2 5035 BIOS will allow the console to boot and function normally regardless of whether the EEPROM is readable or not. This is assuming the hard drive connected is not locked, as the original EEPROM must be accessible in order to read the drive under those circumstances.
Alternatively, there is a special version of the Cromwell BIOS available that can be used to re-flash your chip with an existing EEPROM backup.
- Transplanting
If an EEPROM chip is truly dead, it is still possible to unsolder a (working) EEPROM chip from one console and place it in another. While the chips themselves are all the same, the contents may vary; so long as the chip was sourced from a compatible system it should work.
If the EEPROM is not compatible it can still be flashed with a reader once installed.
