Topic: To Chicken To Proceed (Read 79 times)

xman954 · « **on:** March 25, 2005, 10:50:00 AM »

you rite flashing red is epprom
can you reflash the bios (with embedded eeprom) on a PC with that modchip ?
or put chip in a working xbox and try that

xboxmodder4life · « **Reply #1 on:** March 25, 2005, 11:12:00 AM »

i thought the matrix came with a programmer. I used to have a matrix and was pretty sure it came wtih a programmer

xman954 · « **Reply #2 on:** March 25, 2005, 11:20:00 AM »

QUOTE(TheRealJobe @ Mar 25 2005, 12:07 PM)

Why would ol' eepy just up and do that to me?

shit happens

but it is more likely that the interface to the EEPROM failed (mcpx)
and that if you got it working it would only work with chip on ..
but nothing to lose at this point by trying...

xman954 · « **Reply #3 on:** March 25, 2005, 11:46:00 AM »

QUOTE(TheRealJobe @ Mar 25 2005, 12:28 PM)

I was going to try to use this guide:
http://arisme.free.fr/Xbox/Reflash/

thats a good start if you can get it into your modchip
and it will tell you if it is fixable

TheRealJobe · « **Reply #4 on:** March 25, 2005, 07:10:00 PM »

Okay, I placed the eeprom on my matrix, and put it in place while in test mode. When I did this I went back to running the three restarts back to back on its own.

Then staying on during the last restart and flashing red and green but w/o any A/V. Now once again my chip is still in test mode, becasue I cant get the expletive deleted alignment....

But I just wanted thoughts on this status check. Is the triple boot better than the rapid red, and why would putting a matrix xhip on the board in test mode (yes I'm sure) change the box from rapid red to the triple restart?

Any help is appreciated, in the mean time I'll be trying to align my expletive deleted matrix chip.....

Thanks

novakpower · « **Reply #5 on:** March 25, 2005, 09:59:00 PM »

I just had a triple boot with a Frag tonight, with my X3 1.1 board, I selected the wrong bank on my chip. If you could reflash your chip it should work, I have switches on the X3 so I just switched them to the correct banks and it fired up. Good luck.

xman954 · « **Reply #6 on:** March 25, 2005, 10:37:00 PM »

QUOTE(TheRealJobe @ Mar 25 2005, 11:08 PM)

so a triple reset is a bad flash on the mod?

dont' know that chip

QUOTE

How did my eeprom suddenly fix itself?

with chip off is it the same
if so then it did NOT...

xbox boot seq
mcxp gets the bootloader from the first part of
of the bios if this fails the it frags..( bad flash)
if not it loads the bios(stock,moded) then turns control over to it
it in turn reads the EEPROM, HDD and other stuf ( thats why Cromwell works)
any failure of those have there respective indicators ( blink , error #)

Perplexer · « **Reply #7 on:** March 26, 2005, 10:47:00 AM »

What happened is this:

* You left your Xbox unplugged, and it lost the time setting.
* Your original MS dashboard is missing or corrupt.
* The Xbox tried to boot to the MS dash (even with chip on) so you could set the time. Since it couldn't load the dashboard, you got an error 16.
* When you turned off/on the Xbox, you happened to do so exactly as the EEPROM was being read or written to, and it corrupted the EEPROM.
* Now you get flashing red with or without modchip.

You need to first:

1. Fix the eeprom issue. I would recommend you proceed with caution, or you will turn your hard drive into a paperweight (especially if you don't have a backup of your EEPROM contents).

2. Update your BIOS on the modchip. If you embed your current EEPROM into a current (clock-fix) BIOS like X2 4981.06 and flash it to the modchip, you can ignore step 1 for now.

3. Fix your MS dashboard files.

Hope this gets you pointed in the right direction.

TheRealJobe · « **Reply #8 on:** March 26, 2005, 01:17:00 PM »

in deed it has, and I have fixed my capacitor ala Radio Shack, now I've gotten A/V, the flubber, and a 16 this is w/o the chip on.... currently the chip has the eepropm patched cromwell on it.....

So do I just need to put my evox bios back on the mod and all is saved? or is the eep still going poo?

I'm so happy right now that I just got the flubber and 16 back

Perplexer · « **Reply #9 on:** March 26, 2005, 01:37:00 PM »

Now you'll just need a recent BIOS with the "clock fix" - M8 or X2 4981.xx will work fine.

Then replace the MS dashboard files with the proper ones (you can run dashupdate.xbe from Halo2 or some other recent game, or use some other method.)

TheRealJobe · « **Reply #10 on:** March 26, 2005, 02:18:00 PM »

Well my solderless chip isnt solderless anymore but I have fixed my problem.... and she's a working.... now what files would i need to copy back over if the m8 fixed the issue? I mean to fix the clock and all?

xman954 · « **Reply #11 on:** March 26, 2005, 02:38:00 PM »

Good job !
all you need is the stock MS dash files (all C:\ files)
with your new bios in will boot C:\evoxdash.xbe (or whater the bios is set to)
with chip off it will boot C:\xboxdash.xbe (stock dash fix clock )

pmrush · « **Reply #12 on:** March 26, 2005, 03:57:00 PM »

http://www.xboxmodz....dfrag.html#fix1

You could try these guides see if they help.

P.

Perplexer · « **Reply #13 on:** March 26, 2005, 04:57:00 PM »

QUOTE(TheRealJobe @ Mar 26 2005, 02:18 PM)

But I thought running dashupdate.xbe from recent games like Halo 2 geeked with the dashboard?

TheRealJobe · « **Reply #14 on:** March 26, 2005, 08:50:00 PM »

Perplexer, I guess I'm unclear, I have Halo 2 backed up, when I browse it's contents all I see is update.xbe, and if I try to run that it tries to contact Live, which I thought was a huge problem... where am I going wrong on this?

Author Topic: To Chicken To Proceed (Read 79 times)