Really odd symptoms on my X2.6CE

[someweirdguy]

I've been fussing with this thing for days now, and found something quite interesting today. I guess this is a bit of a cry for help for anything about this problem, just cause I'm about out of ideas. I've got a V1.1 XBox, new 160GB HDD (Loaded with XBMC as the dash). When I turn it on with the mod chip disabled, it goes to a blank screen. The eject light stays green and it acts normal, but I never get any video. When I turn it on with the modchip enabled (X5035 flashed), it gives me the "loading x2config.ini file" message. Then, this is the kicker...it actually loads the settings contained in the .ini file I stored on the HDD. The only way I can tell is because the eject light goes to red, which is what I told it to do. That's as far as it gets. As soon as it loads the settings, the screen goes blank. No flubber, no sounds, no nothing. The Xbox remains on with the red light, but that's all I get.
I guess I've stopped looking for a quick fix, and am now trying to figure out the root of the problem. What is the common thread between the flubber animations on the chip and the default on the XBox? Neither will display, and that's the stopping point for both boots. Correct me if I'm wrong, but aren't they stored in different locations? The default is on the TSOP and the modded is on the modchip itself? Or does the modchip pull the flubber animation from somewhere on the motherboard and change colors, etc.? Anyone with any knowledge of the boot sequence would be of great help, cause I'm only looking for leads at this point. Any bit of information would be much appreciated and a great help, as this has really been taking days of my time. Thanks for your time!

 

[Martin C]

I would remove the chip for the time being and test without, until you have your Xbox working as stock. Whatever this isssue is, it's causing both the retail and modded BIOSes to behave in the same way.

Martin

 

[someweirdguy]

That was actually my thought as well. Just to get rid of as many potential problems as possible. I guess I just get frustrated that way, because it does the same thing minus modchip, DVD drive, and HDD. I can't seem to make any progress with even figuring out a solution. I've checked for solder splashes a hundred times, but I just can't think of any possible things to try. I don't see any physical damage, and I don't know what could go wrong that would mess up both Bioses (even when I reflash the chip with any new BIOS). Thanks for the tip, though. Do you have any more that I might benefit from?

 

[Martin C]

I'm guessing you get FlashBIOS up ok - yes?

Any error messages on the FlashBIOS screen?

Did it ever work with the X2 5035, or was it blank screen from the word go?

Martin

 

[someweirdguy]

FlashBIOS does boot up fine. No error messages at all. Originally I had a FRAG that was caused by a bit of desoldering braid that tore at the LPC points. I fixed that and then booted back up and the problem was there from the start. So I suppose 5035 has never worked. However, when the box was originally fragging due to the braid, it would still boot with the chip disabled. So whatever happened must have happened when I was removing the braid, though I only went near the LPC points, and I can't imagine that those would cause such a problem. Again, thanks for the tips.

 

[Pantless]

Hmm....check again. Maybe something is shorting out on the bottom of the chip, the TSOP (should be noticable) or some random trace. I'd just turn the mobo upside down and look for any debris on it or under it.

 

[someweirdguy]

I'll go ahead and check again. I've checked quite a few times before for anything under there, but this time I'll look up where the TSOP is and make sure to look very carefully around there. Thanks

 

[someweirdguy]

There's not a bit of stray solder or anything under or near the TSOP. I even de-soldered the d0 wire, just to be sure that it wasn't interfering with anything. Is it possible that the TSOP was damaged when soldering on the d0 wire? I noticed the bottom d0 point was right under the chip. I'm not ready to admit that as the problem yet, but I'm hoping there's something I can do. It looks like TSOP replacement is not an option, and I'm just wondering what could have gone wrong here. I've got the modchip out and detached, but still can't seem to make any progress.

 

[someweirdguy]

Here's my thought. What if I load a BIOS that doesn't use the flubber or XBox loading screen (If one exists)? Then, would it bypass the TSOP completely, and boot without a problem. FlashBIOS doesn't show any of those things, and it boots fine. Are there any suggestions for a BIOS that doesn't show the flubber or Xbox logo screen at all?

 

[Martin C]

Here's my thought. What if I load a BIOS that doesn't use the flubber or XBox loading screen (If one exists)? Then, would it bypass the TSOP completely, and boot without a problem. FlashBIOS doesn't show any of those things, and it boots fine. Are there any suggestions for a BIOS that doesn't show the flubber or Xbox logo screen at all?

Booting from the LPC bypasses the TSOP completely.

The X2/X3 BIOSes have the flubber and logo etc inside them too. Otherwise you couldn't change the colours!!!

Martin

 

[someweirdguy]

Alright, I suppose that changes things a little bit. My next step is to try the "three wire method" (which I know nothing about) to try and reflash the TSOP

 

[Martin C]

You're really embarking on areas you don't understand. This is NOT a TSOP issue.

Get some desoldering braid and remove what you've already done. I believe you'll find a short or bridge somewhere.

You'll eventually get to the stage where your Xbox boots normally.

Martin