Help Getting Config Magic To Switch Version, Input eeprom.bin != Flashed eeprom.bin Options

[triggernum5]

I was wondering if anyone can tell me what I'm doing wrong.. I have a v1.0 xbox with a v1.4 eeprom on it. I have it up and running via a chameleon LE with an embedded eeprom in a 4981.67 bios. When I try to flash my eeprom via CM or EEPROMER 0.45 it does not make an exact copy. When I look at my EEPROMBackup.txt (The one that holds the rest of the info from my v1.0 eeprom, and also worked for embedding in the bios) it says that that eeprom version is 1.1 (I know that means 1.1-1.5). Does anyone know what is going on its pissing me off. Sorry if I overlooked the answer to my question, I did look . Found lots of ppl saying you could edit the eeprom, but none said how...

[triggernum5]

I'm still reading up on this, and from what I read I think maybe CM read the eeprom in the beginning,realized its a 1.1 and keeps autoconverting to avoid problems. But if this is the case, why did it let me screw myself in the beginning?

[triggernum5]

Just to let ppl know, the way I solved the problem of an incorrect/unbootable version of the eeprom and preventing was:
Flashed a modchip with a copy of x2 4981.67 with a valid eeprom embedded (use XBTool)
Booted Xbox and used EEPROMER to flash with a TOTALLY corrupted eeprom.bin (Config Magic will not allow this. If You flash a valid EEPROM on while you have an uncorrupted invalid EEPROM on your xbox both CM and EEPROMER will read the current xbox version and alter the EEPROM to prevent incompatibilities. This is a good idea in general, but not if your EEPROM is programmed with an incorrect version already.)
Reflashed the correct eeprom.bin with EEPROMER since Config Magic wouldn't start while the EEPROM was garbled. Now, since it can't read a version off the chip it copies the eeprom.bin exactly.
Ran Config Magic, loaded the current EEPROM and doubled checked to see that it had infact changed the version. (It prints the Xbox version at the top left of the screen)
Thats it. Gotta love the ability to embed EEPROMs/HDD Keys in bioses:)

****Note EEPROMer has alot of dumb errors. It states the the working directory is Z:\ but it is actually Y:\. Also, the filename IS eeprom.bin. DO NOT lock HDDs with EEPROMer (1.1-1.5 anyways) I didn't read the top line (which is misleading as my box was a 1.0 with a 1.4 EEPROM) and lost a 10Gig Seagate.
Lastly, EEPROMer did allow me to alter my version from 1.0-1.1 directly, but prevented me from changing it back without the steps above

[justtaint]

finally someone nice enough to post how they solved their problem, more people should follow your lead. (and more people should search before they post).

[triggernum5]

[Evil Ryu]

triggernum5... just wondering if you could explain that one more time. I got a little lost in your explanation towards the end.

I've got an xbox (unmodded) with a corrupt EEPROM that I'm trying to replace. I've embedded a valid EEPROM into a X2-4981 bios and put that on a modchip so that I could boot up the machine. But when I run ConfigMagic, I get the 'Invalid xbox version specified' error and it doesn't allow me to do anything.

I was going to try using EEPromer tonight and see if I can reflash the EEPROM with a valid one, but from what I understand of your post, EEPromer will change the EEPROM to prevent incompatiblities (I'm assuming video mode and region).

You say to flash the EEPROM with a 'TOTALLY corrupt' one. I've managed to do a backup with Evox and I have the corrupt EEPROM that is currently on the xbox. I can't see a reason to flash the EEPROM with it again, as it would be the exact same image (am I way off here?).

Last thing,... I assume the reason you ran ConfigMagic in the last step was simply to double-check the EEPROM to make sure that it had changed and that the settings were correct?

Thanks

[triggernum5]

[QUOTE]I was going to try using EEPromer tonight and see if I can reflash the EEPROM with a valid one, but from what I understand of your post, EEPromer will change the EEPROM to prevent incompatiblities (I'm assuming video mode and region).[QUOTE]Cool, so I figure you'll have it fixed tonight. Config Magic won't start when the eeprom is invalid, but EEPROMer will reflash with a proper image. My bad, I talked way too much about Config Magic considering it is absolutely not needed to solve the problem. But as far as safety measures go, if CM says you're cool. Then you're cool. Trust me, I lost a stock HDD (Or gained a hobby getting it unlocked) to EEPROMer. Forgot that for all intents and purposes, a v1.4 is a v1.1
Doh!

[Evil Ryu]

Thanks triggernum5... I haven't messed with it yet. I'm waiting to see if how much $$$ he wants to spend on this xbox fixing. I went out and found an unlocked harddrive for him and I'm just waiting for the 'go ahead' from him before I flash his EEPROM. I'd hate to flash his machine with a valid EEPROM and then have him decided he doesn't want to fix it because I'm not sure if I would be able to flash the corrupt EEPROM back.

Anyhow, thanks again and I'll probably reply to let you guys know how I made out.

Cheers

[triggernum5]

No, you can reflash with a bad eeprom (You did with EEPROMer). Only when eeprommer 'can' read the version as being opposite rather than mangled. Remember thats one of the steps. Any idea how he screwed his eeprom on an unmodded box..?

[Evil Ryu]

No idea. I actually had someone else bring this machine to me to fix for him. I would guess that it was probably a power surge or something along those lines.

Maybe I'll try flashing that EEPROM anyway tonight - even if I don't hear from him. But I'll keep you updated...

Thanks again,
ER

[triggernum5]

Power down/outage at the wrong time could do it I guess. Eeprom is written to more than you would think. Anyways, fix it yet?

[Evil Ryu]

*UPDATE*

Consider this xbox fixed. I had to get a new unlocked harddrive for him and I had to use eepromagic to overwrite the corrupt EEPROM. ConfigMagic wouldn't startup because of the corrupt EEPROM, and EEPROMer didn't work either (it said that it had re-flashed the EEPROM, but it didn't). That program is messed up - just like you mentioned triggernum5. I put the eeprom.bin file in the Z: partition the first time and it seemed to have flashed fine, but when I check it, it still had the same corrupt EEPROM. Then when I went to try it again, it kept giving me the error that it couldn't find the Z:\eprom.bin (nice spelling mistake BTW). Then I copied the eeprom.bin to the Y: partition alà your instructions and I still got the same error. Then I put it into the X: partition and it recognized it, and said that it had flashed the EEPROM (and verified it), but once again when I checked it, the xbox still had the old, corrupt EEPROM. So then I tried eepromagic and it worked like a charm! I simply put the valid eeprom.bin in the C: partition and ran the program. No problems at all.

I locked the harddrive to the new EEPROM and everything is working great!

Thanks again for the help triggernum5!
ER

[triggernum5]

Maybe I just got lucky in the way I corrupted my eeprom, or got a fluky fix like I got a fluky bad flash.. I was going to use eeprom magic b4 eepromer, but couldn't find it on my PC. Put you in X:\ huh... If I didn't know better I'd guess there were random seed generators in every function of eepromer.. Glad its fixed though. And now we know Eeprom Magic works so simply anyone can do it..

[Evil Ryu]

word.

[lenballs]

Big thanks to triggernum5 and Evil Ryu, I have now fixed my v1.1 with corrupt eeprom. (flashing red led)

I used eepromagic v0.01, and it restored the eeprom no problems.

I just had to ensure the embedded eeprom on my modchip I was booting off had the same serial number as the serial number eepromagic found on the corrupted eeprom chip. Easily done with xbtool.

Which leads me to ask, eepromagic can obviously see the proper serial number on the eeprom chip, and ignores the serial number embedded on the modchip, can I find the original HDD key using a similar method? I guess not now that I've restored the eeprom, so I have a locked 120Gb segate which might as well be thrown in the bin.

At least I have a working mobo again.

Thanks guys, it's good to be able to register a positive result