| QUOTE (bishop05 @ Sep 3 2004, 06:11 PM) |
I was having the same issues woth my chip, I sent it back because i tought it was a bad chip. Where you able to get it to boot to the OS and flash the chip?
P.S. Do you have the Focus encoder? |
Yes, I don't have a problem, if you get this issue... press eject when the eject led is flashing green.
No more issue.
(yes, it boots up to the OS fine then)
if you press power then eject again, you get the issue again
Not sure which Encoder I have any more, my Xbox is a 1.4
I bet this is the reason so many people have 'broken' ICE chips, or ICE chips which need to be recovered again and again.
That good news, but why didnt Team Xodus release this info?
| QUOTE (bishop05 @ Sep 3 2004, 07:36 PM) |
| That good news, but why didnt Team Xodus release this info? |
I dunno... maybe they don't know ;)
I just worked this out earlier tonight and felt compelled to let others know :)
I've seen quite a few people posting with the same issue, and some saying how it randomly fixed itself after a few boots (ie when they accidentally pushed eject)
I basically worked out exactly how to reproduce and fix the problem, and am documenting it for others to... find :)
| QUOTE (Gumba @ Sep 3 2004, 08:56 PM) |
I dunno... maybe they don't know  |
Actually.... we knew about, and were investigating, a related issue.... you just found a much easier way to reproduce the problem!
| QUOTE |
I just worked this out earlier tonight and felt compelled to let others know 
I've seen quite a few people posting with the same issue, and some saying how it randomly fixed itself after a few boots (ie when they accidentally pushed eject) |
Yes, it seems, also, that leaving some boxes unplugged for a certain amount of time may cause the same issue. Not sure, currently, if it is clock related.
| QUOTE |
I basically worked out exactly how to reproduce and fix the problem, and am documenting it for others to... find  |
Also, if you allow the xbox to sit at the flashing green eject led for some time (2-5 minutes) it may "snap out of it" and continue to boot xos normally.
Thank you, btw. You may not realize it, but you just helped push us a long way towards solving one of the bugs that I've been pulling my hair out and losing sleep over for several days now.
--Arti
You DA Man!!!
| QUOTE (Artifex @ Sep 3 2004, 09:06 PM) |
| Thank you, btw. You may not realize it, but you just helped push us a long way towards solving one of the bugs that I've been pulling my hair out and losing sleep over for several days now. |
Glad I've managed to save you some hair ;)
| QUOTE (Gumba @ Sep 3 2004, 03:23 PM) |
Glad I've managed to save you some hair |
omfg thank you!!!!!!!!!!!!!!!
I'll never press eject after booting anymore.
/me hugs you
Problem where my Xenium ICE won't boot into xos 2.0 when I hit eject button to power on. X-box has corrupted eeprom but xos 1.1 was still able to boot when this happened once before. Since updating to 2.0 beta2 I can no longer downgrade to v1.1 so my x-box is dead in the water. Have tried reinstall xos 2.0beta|beta2 recovery.bin from both CD-RW and HDD but still no joy.
Anyone know what would cause xos 2.0 not to load when eject button pressed (red flashing eject led) and eeprom is corrupt?
NB: Latest evolution-x was set as default BIOS so bios should still be able to boot regardless of eeprom afaik.
I have some additional information to add to this thread. Hopefully with enough input, Team Xodus will supply a OS 2.0 Final.
Xbox v1.6 modded with Xenium (blue) using OS 2.0 beta2.
When power button is pressed to boot up, no video is displayed on TV and the LED on the chip is a yellowish color (not red).
Pressing the eject button causes the Xbox to reboot. DVD tray does NOT eject and still no video with chip LED still yellowish.
I tried leaving the Xbox on for about 10 minutes to see if it would "snap" out of it. It did not.
I opened the box, removed the chip and unsoldered the LFrame ground and booted up with the power button. Original bios loaded and I set the system clock, then shut down.
Resoldered the LFrame ground and put the chip back in. Powered on and what do you know, good as new - booting the hacked bios.
Observation 1: Xenium OS Restore unnecessary
Observation 2: Setting the system clock fixed the problem. Obviously the system clock plays a role in this bug, but I wondering whether the M8_16 doesn't contribute too.
Observation 3: The OS was set to Instant Boot. I wonder if the Instant Boot feature plays a role in this.
I'd be curious to know how many people who have had this problem, also had Instant Boot enabled. Or, whether anyone has had this issue with Instant Boot disabled.
Hope to see a permanent fix soon.
The problem is not related to the system time, but *IS* related to the CMOS. (the bit of memory in the box where the system time is stored)
Quickboot and InstantBoot are not factors.
The problem can be caused by other things then the power/eject "hammering."
--Arti
| QUOTE (Artifex @ Sep 13 2004, 04:46 AM) |
The problem is not related to the system time, but *IS* related to the CMOS. (the bit of memory in the box where the system time is stored)
Quickboot and InstantBoot are not factors.
The problem can be caused by other things then the power/eject "hammering."
--Arti |
Yes
I had my xbox unplugged for a while the other day (12 hrs?) and when I turned it on with the power button (InstantBoot is enabled) it went the flashing green black screen. So I pushed eject, then powered down, then powered up and it went to Avalaunch which promptly reset the corrupted clock (it brings up a little dialog while it does it)
Its weird I guess
PS: I'm using the X2 4981 bios, not M8
This issue is dealt with, and does not really need "bumped"....
Closing thread.
--Arti