Print

[Lugnut]

I cant answer you that one.  i had a 1.3 xbox that just went "tits up" as you say with the eeprom corruption, the person went to change games and something happened and they rebooted it.  the light started to blink red.

still dont know what did it, so i took it fixed it with the backup eeprom. and i just lifted pin 7 on the eeprom and shorted it to pin 8 to make it write protected, and its been fine ever since.

[kevlar69]

Lugnut, can you confirm if my post above about how to sort out the eeprom is correct please?

cheers

Kevlar

[lenballs]

QUOTE (Lugnut @ May 10 2004, 02:59 AM)

the first thing you always always always do when modding an xbox is get an eeprom backup.

Yip, having a backup of your eeprom on your PC is an excellent idea, but when you do mods for other people, it gets a bit hard to store every individual eeprom.

QUOTE

So the 2 month old Samsung drive is shagged, what do you think the chances of passing this off as a faulty drive and getting it replaced?

This is not a bad idea, I never actually thought of doing this, any technician checking the drive would plug it into a PC and it would be a nogo....can I handle the guilt complex.....

QUOTE

Another question, why did his eeprom go tits up in the first place?

I also find this strange, if you have an eeprom corrupt itself, and it needs to be reflashed, isn't it likely to happen again fairly soon? I'm going to hang onto the xbox I fixed and see if it hangs on in there.

[lenballs]

QUOTE (kevlar69 @ May 10 2004, 04:03 AM)

7, boot up and use config magic to flash the eeprom with the image contained in the bios

I couldn't get Config Magic to load when I booted with an embedded eeprom, it kept saying invalid xbox version.

I had to use eepromagic v0.01 to flash the eeprom with an eeprom.bin on C:

eepromagic also warned me to make sure the serial number in the eeprom on c: matched the serial number of the shagged xbox, ie., it knew what the original serial number was even though the eeprom was corrupt.

[kevlar69]

QUOTE

eepromagic also warned me to make sure the serial number in the eeprom on c: matched the serial number of the shagged xbox, ie., it knew what the original serial number was even though the eeprom was corrupt.

Did it work anyway? or were you using a backup of the original eeprom? If you can only flash an eeprom with a backup of it's original image then most of what wev'e been talking about was a waste of time as I don't have a backup of the original.

cheers

Kevlar

[kevlar69]

Another question, is there a tutorial on XBtool? I haven't used it before. Do I load a 256k 4981 file or a 1024k bios I created before?

cheers

Kevlar

[kevlar69]

Kevlar

[lenballs]

I don't have the original eeprom either, I took a backup of the eeprom on a fully working v1.3, used liveinfo to load and edit the eeprom to change the serial number to be the same as the shagged xbox, (eepromagic tells you what serial number it wants, you can also check the serial number on the sticker on the bottom of the xbox) then flashed the shagged xbox eeprom.

Some steps which might help you do this:

Make sure you have the latest xbtool, v1.0.22, or it won't work.

Go here for the xbtool documentation:

http://home.alltel.n.../XBtoolDoc.html

XBtool, load your bios, eg. 4981, and choose the '1024k' option at the bottom of the screen.

Copy your eeprom.bin file into the xbtool\patchdata folder, then choose the 'embed eeprom' checkbox.

When you click 'save as', it will save the bios as a 1024k bios with an embedded eeprom. Flash your modchip with this bios.

Install flashed modchip into the shagged xbox, and boot.

Copy the eeprom.bin file we spoke about before onto the c:\ of your xbox.

Copy the eepromagic app onto your xbox.

Load eepromagic and flash the eeprom.

I hope I've got the correct sequence of events here, I don't want to mislead people, however if your xbox eeprom is already corrupt, you can't make it any worse. I've just recently carried out this procedure and I now have a working xbox again.

Triggernum5 and Evil Ryu state you don't need to have matching serial numbers, I prefer to, I also don't want two xboxes having the same serial number.

Hope this helps.

[lenballs]

Just thought of something else, I think I recall you saying your using an X2.2 or 2.3 modchip, in this case you need a 1024k bios, obviously if your using a 256k modchip like aladdin etc. then save the bios as 256k.

[Renthal]

Contrary to popular opinion, I can confirm a 1.1 eeprom will flash and work on a 1.0 Xbox.

[xboxhaxorz]

QUOTE (kevlar69 @ May 8 2004, 01:12 PM)

ok, after some investigation I have come to the conclusion that the eeprom on the motherboard has become damaged ( how could this happen anyway? ) and following this link http://arisme.free.fr/Xbox/Reflash/ seems to explain how to reflash the eeprom using a mod chip and cromwell bios. I need an eeprom image first though, and have my own xbox here, as well as 2 good mod chips, but how do I get the eeprom image from my motherboard to my pc/modchip? any help appreciated. Kevlar

pardon my intrusion kevlar

but will this work for my problem, again i am sorry alot kevlar
but i have had this prob for 8 wks or something

http://forums.xbox-s...howtopic=212549

[Evil Ryu]

 Then you don't have to worry about storing a ton of eeproms and such on your PC.

[lenballs]

[kevlar69]

Guys, I'm failing at the first hurdle, I haven't managed to flashe my modchip yet with my eeprom embedded bios. Obviously having chipped 8 xbox's I've successfully flashed all chips from Cromwell to 4981, but as yet I haven't had to flash a chip which already has a full bios on it. I expected to just insert my bios disc while booted to evox for it to happen automatically, ala Cromwell. Obviously it doesn't work like this. I've tried installing Flashx but for some reason I can't get it to run, it just sits there on loading screen.

What is the easiest way to flash a 2.4b lite that already runs 4981?

Thanks in adance

Kevlar

[kevlar69]

sorry, double post.