2.6 Lite fried trace.... Solution?

[phish3r]

I got an Xecuter 2.6 lite the other day and went to program it with the X-Programmer 2.6. When i plugged it in on of the traces (Shown below) fried, and it did not program. My first thougth was my chip is dead. I decided to plug it in anyway and give it a shot.

When i plugged it in, to my surprise, the chip booted to FlashBIOS 3.0.3. I was thinking sweet i didn't kill it, now i can just do a network flash!

Tried the network flash, no go. It just sits at the "flashing" screen. The xbox doesn't turn off, nor does the power turn amber. Disc flash (CD-RW and DVD) produce the same results.

Its almost as if i've turned on some perminant flash protection. Is there any chance of saving this chip? Should i just scrap it and get a new one?

 

[Martin C]

I got an Xecuter 2.6 lite the other day and went to program it with the X-Programmer 2.6. When i plugged it in on of the traces (Shown below) fried, and it did not program. My first thougth was my chip is dead. I decided to plug it in anyway and give it a shot.

When i plugged it in, to my surprise, the chip booted to FlashBIOS 3.0.3. I was thinking sweet i didn't kill it, now i can just do a network flash!

Tried the network flash, no go. It just sits at the "flashing" screen. The xbox doesn't turn off, nor does the power turn amber. Disc flash (CD-RW and DVD) produce the same results.

Its almost as if i've turned on some perminant flash protection. Is there any chance of saving this chip? Should i just scrap it and get a new one?

ok

1. How did you connect it to the programmer?
2. Why did you connect it??

It's probably fixable, but I'd need to see an actual picture of it.

Martin

 

[phish3r]

I'll take a picture of it when i get home today. I'm at work now so I dont have access to it.

I connected it to the pins on the programmer, (they're just like the header pins you install on the xbox motherboard.) Then i plugged in the programmers USB power, then i plugged the programmer directly into the parallel port of my PC.

I was doing it this way cause i had a programmer lying around from when a friend of mine tried to flash his chip and his power blinked in the middle of flashing so it didn't complete. Couldn't boot his chip to flash it again so we bought a programmer. I figured i had it and it has worked before, so I might as well use it.

 

[phish3r]

As promised, here's an image of the chip.... Dispite the way it looks its really only that one trace that is visably damaged. There is also no visable damage on the top of the chip.

Do you think i could just solder in place of where the trace was?

Any chance on getting a schematic of the PCB so I can see where exactly that trace goes?

 

[phish3r]

No thoughts or comments?

How about which two components/pins does this trace connect so i can try soldering a wire to them on the top side of the chip.

 

[Martin C]

Not having one in front of me, I cannot see exactly where it goes. Why it blew to begin with is also puzzling me.

Martin

 

[phish3r]

If you follow the burnt trace up it you can see that it goes to a via that connects to the jack that the front panel plugs into.

This makes me think that i've burnt the trace for the flash protection. that would explain why my chip still works but I am unable to flash anything.

If i knew what pin on the top connector the via went to, and where the other end of the trace went i should just be able to solder a wire across the two.

any way i can find this out?

 

[anburton]

What did you do to program the chip. I have a Xecuter 2.6CE and the X-Programmer. With X2BM v2.1 I get a "Xecuter 2 not detected; Code 0x1010" If I change any settings it gives me, Code 0xFFFF. Not sure what I'm doing wrong.

Also, the X-Programmer came with 2 red cable with a 2pin connector on one side and white connectors on the other that appear to go into the Xecuter somewhere. However, it doesn't fit any of the female connectors on the X 2.6CE.

I'm guessing they are for power but I don't know where they go. Funny thing is they both fit on my Xecuter 2.2 but there's only one two pin header on the X-Programmer.

Team-Xecuter seems to make great hardware. But the documentation is hard to find to say the least.