Print

[MagusIII]

I think you have to unplug the HD, and then try to boot XOS.

This sounds very similar to my problem, really...

[getset]

tried it with no hard drive, same thing happens.

also tried with a working, unlocked retail hard drive. still no use.

still looking for more help, thanks

[eco]

QUOTE (MagusIII @ Nov 14 2004, 01:57 PM)

I think you have to unplug the HD, and then try to boot XOS. MagusIII Archived User Newbie Posts: 32 Help! Bad Epprom, New Xenxium, Still Won't Work I haven't managed to find a solution to the problem yet. I've been trying to get in touch with Team Xodus at #TeamXodus on EFNet. Haven't had much luck yet. I was gonna give up, but now that there are two of us with the exact same problem (and one with a similar problem), they're gonna have to listen! eco Archived User Newbie Posts: 4 Help! Bad Epprom, New Xenxium, Still Won't Work I still have to look for the right bios (able to boot with a corrupted eeprom and compatible with the old Matrix), but I will of course let you know the end of the story. MagusIII Archived User Newbie Posts: 32 Help! Bad Epprom, New Xenxium, Still Won't Work You should be able to boot an EEPROM set to PAL60 with the X2 4983 BIOS. That's the one I was using before the accidental flash that caused this very annoying problem. I wouldn't say the EEPROM is corrupt, though... it's just set to a video mode that is not supported by all applications, and unfortunately Xenium OS is one of them. getset Archived User Newbie Posts: 3 Help! Bad Epprom, New Xenxium, Still Won't Work We need the blue screen, come on Xenium. that's the whole reason i bought this chip. to fix me epprom. at least i'm not alone. eco Archived User Newbie Posts: 4 Help! Bad Epprom, New Xenxium, Still Won't Work QUOTE (MagusIII @ Nov 15 2004, 07:18 PM) You should be able to boot an EEPROM set to PAL60 with the X2 4983 BIOS. That's the one I was using before the accidental flash that caused this very annoying problem. I wouldn't say the EEPROM is corrupt, though... it's just set to a video mode that is not supported by all applications, and unfortunately Xenium OS is one of them. QUOTE Thanx for the information about X2 4983. Another bios that should (according to the .nfo) work with a corrupted eeprom is IND-BIOS 5003. But I am quite sure my system eeprom is corrupted (and so would be yours... ) : I had already set MS dashboard to PAL60 and XOS was having no pb with it. It's true however that XOS itself was still in PAL (50), but it's just to point that this only setting from MS dashboard is not an issue for the Xenium. Anyway, if I remember well, XOS itself had an option to display — and boot — in PAL60; I remember I was about to set it but I got a warning saying that not all TV would be able to display PAL60, so I didn't switched to PAL60 under XOS (even if I knew that my TV supports PAL60... just to see a warning msg made me extremly cautious... Ah if only Avalaunch had displayed such a warning! Anyway... ) Only to say that if XOS has PAL60 as an option, I think that at least, it supports it! But our problem started after we had changed to PAL60 in some eeprom setting under Avalaunch. And on my system, although I already had the video standard set to PAL60 under MS dashboard, this option under Avalaunch was still in PAL50 (before I changed it to PAL60... damn! ) So I figured (but too late  ) that the setting we have changed under Avalaunch, is not the same as in MS dashboard. My thought is that we made a sort of conflict between two "video standard or region" references, configured differently in the eeprom, resulting in a corrupted one. And there is another thought, which will testify of my noobness and extreme carelessness on this issue : when I changed this damn video setting under Avalaunch, I got a message like: "DVD successfully unlocked" or something. Or was it after I changed an option unambiguously related to DVD? LOL I cannot even remember exactly, but I do remember that I was a bit surprised to see this msg about DVD... That makes me say that it was when I changed an option explicitely related to video standard... THis was just a thought... I promise I am not trying to confuse you!   As for you, getset, I think you would have had less problem flashing your eeprom with a 3rd gen chip which could only boot from a bios (that you would have chosen). Maybe I am wrong (and I would be happy if I am...) but as far I know, booting directly from a bios that can deal with corrupted eeprom is the best way to fix it. But your Xenium could still prove some usefullness, according it is installed with a solderless solution and that you have access to another opened Xbox. This is what I will do when I have the time (simpler than my previous "solution"): put my chip on the unmodded Xbox of a friend. If my chip is ok — and it should be — I will install X2, IND-BIOS or another "corrupted eeprom"-compatible bios on it, make it "default" under XOS and "instant boot" (like MagusIII had). Then back on my console, I will reflash the eeprom using my backup. This should work, right? MagusIII Archived User Newbie Posts: 32 Help! Bad Epprom, New Xenxium, Still Won't Work EDIT: Also, the reason that I don't think the EEPROM is corrupted, is that I've been using Avalaunch and PAL60 for a long time with many different BIOS'es and applications, and there's never been a problem with any of them. Expect for XOS and MS dash, of course. MagusIII Archived User Newbie Posts: 32 Help! Bad Epprom, New Xenxium, Still Won't Work I'm bumping this. MagusIII Archived User Newbie Posts: 32 Help! Bad Epprom, New Xenxium, Still Won't Work eco Archived User Newbie Posts: 4 Help! Bad Epprom, New Xenxium, Still Won't Work Print Pages: [1] « previous next » xboxscene.org forums > OG Xbox Forums > Modchip Forums > Team Xodus Chips (Xenium) > Help! Bad Epprom, New Xenxium, Still Won't Work   SMF 2.0.19 | SMF © 2021, Simple Machines

[MagusIII]

I haven't managed to find a solution to the problem yet. I've been trying to get in touch with Team Xodus at #TeamXodus on EFNet. Haven't had much luck yet. I was gonna give up, but now that there are two of us with the exact same problem (and one with a similar problem), they're gonna have to listen!

[eco]

I still have to look for the right bios (able to boot with a corrupted eeprom and compatible with the old Matrix), but I will of course let you know the end of the story.

[MagusIII]

You should be able to boot an EEPROM set to PAL60 with the X2 4983 BIOS. That's the one I was using before the accidental flash that caused this very annoying problem. I wouldn't say the EEPROM is corrupt, though... it's just set to a video mode that is not supported by all applications, and unfortunately Xenium OS is one of them.

[getset]

We need the blue screen, come on Xenium. that's the whole reason i bought this chip. to fix me epprom. at least i'm not alone.

[eco]

QUOTE (MagusIII @ Nov 15 2004, 07:18 PM)

You should be able to boot an EEPROM set to PAL60 with the X2 4983 BIOS. That's the one I was using before the accidental flash that caused this very annoying problem. I wouldn't say the EEPROM is corrupt, though... it's just set to a video mode that is not supported by all applications, and unfortunately Xenium OS is one of them.

QUOTE

Thanx for the information about X2 4983. Another bios that should (according to the .nfo) work with a corrupted eeprom is IND-BIOS 5003.

But I am quite sure my system eeprom is corrupted (and so would be yours...
) : I had already set MS dashboard to PAL60 and XOS was having no pb with it. It's true however that XOS itself was still in PAL (50), but it's just to point that this only setting from MS dashboard is not an issue for the Xenium.
Anyway, if I remember well, XOS itself had an option to display — and boot — in PAL60; I remember I was about to set it but I got a warning saying that not all TV would be able to display PAL60, so I didn't switched to PAL60 under XOS (even if I knew that my TV supports PAL60... just to see a warning msg made me extremly cautious... Ah if only Avalaunch had displayed such a warning! Anyway... )

Only to say that if XOS has PAL60 as an option, I think that at least, it supports it!

But our problem started after we had changed to PAL60 in some eeprom setting under Avalaunch. And on my system, although I already had the video standard set to PAL60 under MS dashboard, this option under Avalaunch was still in PAL50 (before I changed it to PAL60... damn! )
So I figured (but too late  ) that the setting we have changed under Avalaunch, is not the same as in MS dashboard.

My thought is that we made a sort of conflict between two "video standard or region" references, configured differently in the eeprom, resulting in a corrupted one.

And there is another thought, which will testify of my noobness and extreme carelessness on this issue : when I changed this damn video setting under Avalaunch, I got a message like: "DVD successfully unlocked" or something. Or was it after I changed an option unambiguously related to DVD? LOL I cannot even remember exactly, but I do remember that I was a bit surprised to see this msg about DVD... That makes me say that it was when I changed an option explicitely related to video standard...
THis was just a thought... I promise I am not trying to confuse you!  

As for you, getset, I think you would have had less problem flashing your eeprom with a 3rd gen chip which could only boot from a bios (that you would have chosen). Maybe I am wrong (and I would be happy if I am...) but as far I know, booting directly from a bios that can deal with corrupted eeprom is the best way to fix it.
But your Xenium could still prove some usefullness, according it is installed with a solderless solution and that you have access to another opened Xbox. This is what I will do when I have the time (simpler than my previous "solution"): put my chip on the unmodded Xbox of a friend. If my chip is ok — and it should be — I will install X2, IND-BIOS or another "corrupted eeprom"-compatible bios on it, make it "default" under XOS and "instant boot" (like MagusIII had). Then back on my console, I will reflash the eeprom using my backup. This should work, right?

[MagusIII]

EDIT: Also, the reason that I don't think the EEPROM is corrupted, is that I've been using Avalaunch and PAL60 for a long time with many different BIOS'es and applications, and there's never been a problem with any of them. Expect for XOS and MS dash, of course.

[MagusIII]

I'm bumping this.

[MagusIII]

[eco]