Print

[appleguru]

These aren't the BFM versions are they? They should only be 256K each, in which case you should be able to flash up to four at a time... No need to rename to bios.bin, name doesn't matter...

[Gumba]

Make sure you're following XOS2.0 instructions... not XOS1.x

You don't need to rename the .bin files to BIOS.BIN, and you don't even need to burn CDs, you can just ftp the bios, or place it on a USB thumbdrive.

Use X2 4981 or 4983

[Gumba]

QUOTE (Cousteau @ Sep 22 2004, 12:20 PM)

So somebody was kind enough to give me a copy of the bios that should be good (x2 4981) but I get the same result when I install it. What does the flashing red and green led mean? What are possible causes of this? I reseated the adaptor and used the paper trick so I don't  think that could be it. I've been following a guide called "xenium ice total n00b guide by cap269" and it seems fairly self explanitory. What does BFM version mean? It wouldn't make any difference if I'm using a mac would it? At this point I think I'm doing everything right. The xenium menus seem clear. I'm rewriting the same disk and the xbox is reading it fine. The chip is acting like it's accepting the bios. Am I missing something here or is it starting to look like I have hardware issues?

No, it won't make a difference if you use a mac

I use a mac, appleguru uses a mac

BFM means Boot From Media, basically its a bios which is formatted to be loaded from another bios, rather than booted to from flash.

You need to use non BFM bioses with the xenium (at least with current XOS releases)

There are virtually an infinite number of reasons why you could be getting a FRAG (flashing red and green). FRAG happens when the MCPX chip can't load a BIOS successfully.... but that could be for many reasons, including loose connections.

If you can see the XOS menus it means the connections are good

[appleguru]

Check the jumper settings on the HDD, make sure it's set to Cable Select. Make sure all your cables are plugged in....

[appleguru]

Nah, not d0, the Xenium OS wouldn't load.. It's quite possible one or two of your LPC points arent making good contact, other than that I'm at a loss to think of anything.

[Gumba]

QUOTE (appleguru @ Sep 23 2004, 01:18 AM)

Nah, not d0, the Xenium OS wouldn't load.. It's quite possible one or two of your LPC points arent making good contact, other than that I'm at a loss to think of anything.

Well, the Xenium OS is uploaded to the Xbox via the LAD points on the LPC so basically if you see XOS everything to do with BIOS loading is working correctly. The only thing which could be wrong is d0 is grounded instead of installed properly... that causes the reboot to XOS instead of to TSOP when TSOP is selected issue.

So, I'm assuming your modchip install is correct, and then your problem is either

1) loading a corrupt/wrong bios
2) hardware damage
3) software damage

So, you are *sure* you have a 1.0 box?
Ensure that the HD cable is properly connected to motherboard, hd and dvd. If you can boot to retail kernel that more or less proves that

...

You might want to try upgrade the Xenium to XOS2b2, basically you're using an old version which most people here are no longer familiar with. Of course, if you have a clone chip then it will die. But if you have a clone chip (there are tutes to detect the difference) then you should get a refund!

[Gumba]

I'm sorry, i've got no idea what could possibly be wrong

It really does sound like everything should be fine.

All I can suggest is trying to do the upgrade to XOS2b2.