D0 FRAG problem

10secX

Noob Account
Nov 28, 2005
7
0
am very frustrated here. I started off trying to do a solderless install with a xadpt3r. The blue lights from the adapter regarding the LPC would light fine, but the D0 red light on the adapter would turn on briefly, but would not stay on. When powered up I would get FRAG. So I decided to go ahead and solder in the LPC header. I checked the voltage on each PIN and they seem consistent with what others have posted. I can power on the Xbox with just the header in place (no mod chip) with the original HD and I get the MS Dash. I then solder the small wire harness to the HDD and LAN LEDs and got the "contact Service Message" and FRAG after ~5-10 seconds, not immediately as I had seen before. If I remove the D0 solder point on the bottom side of the MB, I can boot to the MS Dash. I can not understand why this would be a problem just by soldering a wire to the D0 point. Anyone run across this or have any ideas?

More info. This is a refurbished v1.1 xbox. I plan on using an Xecuter 2.6 mod chip once I am confident on the solder results.
 

MKChampion

VIP Member
Oct 12, 2004
875
0
Toronto, Canada
D0 should not cause a frag
check to make sure you haven't bridged any connections around the point and lpc
and that the swtich cable is properly fitted at both ends

which error code do you get when you boot?
 

10secX

Noob Account
Nov 28, 2005
7
0
Thanks for the reply. I did not notice which code came up. I'll have to reconnect the D0 lead again. I am trying to move forward systematically, so I do not have the chip installed at the moment, just the pin header and the LAN/HDD leads. At the moment the only thing different is the connection of the D0 lead. I should be able to boot into the MS DASH with all the connections made without the mod chip installed, right?
 

MKChampion

VIP Member
Oct 12, 2004
875
0
Toronto, Canada
10secX said:
I should be able to boot into the MS DASH with all the connections made without the mod chip installed, right?
yes, with the chip removed from the pinheader, the box should boot normally
 

10secX

Noob Account
Nov 28, 2005
7
0
I reconnected the D0 lead and I no longer get the FRAG with the chip removed or disabled. With the Xecuter 2.6 chip enabled, I now get the power up/down/up/down/up FRAG situation.... Could this be a defective mod chip? I may take apart my other working xbox with the soldderless adapter and try that mod chip that is flashed and is working. Any other ideas?
 

MKChampion

VIP Member
Oct 12, 2004
875
0
Toronto, Canada
try the non-working chip in your working box and see if it makes a difference with the solderless adapter, if it doesn't, try switching the external swtiches with the chips and see if that works

if it does work with the solderless adapter without having to change around the swtiches, then the problem lies somewhere within your install
 

10secX

Noob Account
Nov 28, 2005
7
0
Didn't get a chance to try tonight, will give it a shot tomorrow and let you know what happens. Its a good idea which I did not consider that angle. Thanks!
 

10secX

Noob Account
Nov 28, 2005
7
0
Looks like my install is good. I get the same FRAG on both of the new chips that I bought. I can use my existing chip in the new install and boot fine. I am kind of upset that I have two bad mod chips. I got them both at modchip.com. I will have to contact them to try and get new ones, unless anyone else has any other ideas. I tried using the lite programmer. It intermittently recognizes the chips, but if I try and flash them I get errors.
 

10secX

Noob Account
Nov 28, 2005
7
0
Ok problem solved. I setup x2bm on a laptop and had better results flashing the mod chips. I had to erase them a couple of times and had to play around with the chip in the programmer to be able to flash them without getting the dreaded "bad parallel cable" issue, even though I was plugged directly in the parallel slot. For me I had to skew the chip on the programmer by slightly having the right side of the chip higher than the left side instead of flush. So if you run into a programming issue definately experiment with the way that the chip sits on the programmer. Seems unnecessary, but worked in my case...

Thanks MKChampion for helping open up my troubleshooting methods.