Print

[Renthal]

I've got an Xbox that I'm attempting to fix. There's a problem with the HDD, and the xbox frags, but being a v1.0 there's no error code generated. So...to figure out what the exact error is, I put my xenium in and attempt to bootup, but I get half a screen of corrupt video at the xenium OS initial bootup and I can get no further. After powering off and back on, the screen shows an error, "Corrupt JPEG data: bad Huffman code".

Does anyone have any knowledge as to why this is occurring? The xenium has worked fine in every other Xbox I've put it in.

[Renthal]

OK, I found a solution. Unplugging the controller and forcing the xenium to bootup into it's default bios worked. For some reason, the xenium OS will not run on this Xbox though. I was still able to fix the Xbox though.

[Xeero]

v1.0 Xboxes still generate error codes, FYI.

Does the Xenium not work in other Xboxes now?  If not, I'd use its recovery mode to update the XOS to 1.1.

[Renthal]

Xeero, about the first point, some, the keyword being some, v.1.0 Xbox's are capable of generating a proper error code number. The majority that I have fixed (v1.0's), will not, and do not generate any error code number.

The Xenium does still work fine in other Xbox's. I think there's some type of video problem w/this particular Xbox. It locks up whenever I attempt to change a skin in Unleashx.

The xenium is running OS 1.1, but I cannot use the recovery switch on the side as smoke rises off the xenium. I need to contact ozXodus about a replacement as I'm sure it's not supposed to do that    

[Xeero]

All v1.0 Xboxes generate error codes the same as a v1.1-v1.5 will.  I'm not sure what crazy Xboxes you've worked on that won't generate error codes.  Maybe pre-releases Xboxes?

[Renthal]

OK, perhaps we're talking about different things, let me clarify. I'm referring to the number in the upper left hand corner when you see the "Your Xbox needs Service" screen.

Case in Point: I have 6 Xbox's (all v1.0), in my rat's nest of a work area, that have been fixed in the past 3 days. Only one of those six was able to generate an error code as to its problem (error 16 to be exact). Now, after installing the xenium and booting from an x2 4981 bank, an error code was generated for each and every one (most of them being error code 6). So, booting from the original BIOS on these Xbox's does not generate a number, simply "your Xbox needs service".

These are early production boxes from late Oct. 2001 and early November 2001. I believe the one that generated the proper error code number was dated July 30, 2002 (I just checked and verified the date).

I've talked before (on these forums) about some v1.0 boxes not being able to generate an error code number (with the retail BIOS of course) and have received feedback from other individuals stating the same. It seems this is an issue related to early production Xbox's only.

[Artifex]

The first ms bios shipped out on retail boxes displayed a slightly different boot-error screen then contemporary boxes, and no error code.

--Arti

EDIT: In fact, my first box was this way....

I'm one of those silly kids who camps out in front of bestbuy the night before a new console is released.  

Hrmm.... that gives me an idea....

The entire xbox scene should organize a big meetup at some consumer electronics or games shop in Redmond the night before the xbox2 release.... just to show MS we all care.... hehehehe

[JoePo]

i have a V1.0 xbox w/ xenium.  Like you guys have said, it does give out error codes, but not often.  I think if it boots to MS dash, then it will only say "your xbox needs service" if something is wrong.  But if it fails to even boot the msdash, then thats when I think it gives the actual error code numbers.