JTAG 1033 error after reflow

specopbookie

Noob Account
Oct 9, 2010
3
0
Alright, first off let me assure everyone that I have read all around the interweb on the 1033 error code related to jtags. Any information provided to me will be greatly appreciated.
A couple days ago my XENON jtag started red ringing with a gpu error so I took apart the box, reflowed the CPU and gpu with a heat gun, and reapplied paste and the xclamp fix. Upon reassembling the Xbox, I was presented with the dreaded E79 with 1033 secondary error. This happens with or without the HDD attached so I'm assuming that we can rule out it being a faulty HDD???
The southbridge seems to be fine, and upon pressing firmly on the chip and booting, I still get the error. NOW, here's where I need the expertise of everyone. I plugged my hdd into a USB adapter on my PC, loaded and ejected it, and then plugged it back into my Xbox. Tried booting again for giggles and it worked!!! All was fine, so I shut it off and completely reassembled the box. Plugged it back in, and now its displaying the 1033 error again.
What does this mean??? That its the southbridge??? I'm assuming that the diodes and resisters are fine on the jtag because it booted once today... if they were fried wouldn't they not allow for a boot at all??? What is everyone's take on this?? I checked the board, nothing looks damaged from the heat gun (I gunned it from the bottom) .

Sent from my DROIDX using Tapatalk
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Ok - read it in full this time.

#1 do NOT take a DIY heat gun to anything you want to keep. They're weapons of mass destruction and not to be used on consoles - ever. Especially a JTAG!

#2 The fact it booted once has nothing to do with the HDD, unless you can replicate the action each time.

#3 E79 is normally SMC wiring, Southbridge or GPU related. Double check all wiring to make sure nothing's come loose. Check J2D2 in particular. Write back the original NAND and remove the wiring and see if it boots fine.
 
Last edited:

frayed

DINDU NUFFIN
VIP Member
Dec 22, 2010
3,245
118
A galaxy far far away....
I reflowed the CPU and gpu with a heat gun, I checked the board, nothing looks damaged from the heat gun (I gunned it from the bottom)
sorry to hear you added some youtube magic to your console

not sure but while searching the interwebs you may have missed the part where using a heat gun is bad and causes more damage, and no you wouldn't be able to see the damage with your eyeballs
 

specopbookie

Noob Account
Oct 9, 2010
3
0
I'm going to take a multimeter to the jtag wiring here soon, to test everything. I did read that heatgunning CAN be dangerous but I used variable temps and thought I was capable. I really don't think its the gpu, but ill check it. I didn't think 1033 was gpu related... ill do some more tinkering and post my results. Thanks for the information so far guys.

Sent from my DROIDX using Tapatalk
 

specopbookie

Noob Account
Oct 9, 2010
3
0
Yes Martin. E79 could be gpu related. But the secondary code is 1033. That is typically NOT GPU related. I assume you do know how to get the secondary code on a red ringed box... and from what I've seen a 1033 is southbridge, jtag wiring, or hdd related. However ... update... plugged it in on just the metal frame and its working again... dumb thing.

Sent from my DROIDX using Tapatalk
 

mcornbill

VIP Member
Jan 2, 2003
176
0
Birmingham, UK
Yes Martin. E79 could be gpu related. But the secondary code is 1033. That is typically NOT GPU related. I assume you do know how to get the secondary code on a red ringed box... and from what I've seen a 1033 is southbridge, jtag wiring, or hdd related. However ... update... plugged it in on just the metal frame and its working again... dumb thing.

Sent from my DROIDX using Tapatalk
specopbookie, what dashboard version was the console on before you jtagged it and what proces did you use to create the hacked nands?
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Yes Martin. E79 could be gpu related. But the secondary code is 1033. That is typically NOT GPU related. I assume you do know how to get the secondary code on a red ringed box... and from what I've seen a 1033 is southbridge, jtag wiring, or hdd related. However ... update... plugged it in on just the metal frame and its working again... dumb thing.

Sent from my DROIDX using Tapatalk
1033 *is* E79. It's the numerical value of it. Yes, it may be related to JTAG wiring, specifically J2D2.1 and J2D2.2 which, surprise surprise, talk to TMS and TDI on the GPU. Last E79 JTAG I fixed needed a new GPU fitted.

If it's working intermittently (when put back in the chassis for example), it may just be a wiring issue. Take a pic and post it up.
 
Last edited:

mcornbill

VIP Member
Jan 2, 2003
176
0
Birmingham, UK
1033 *is* E79. It's the numerical value of it. Yes, it may be related to JTAG wiring, specifically J2D2.1 and J2D2.2 which, surprise surprise, talk to TMS and TDI on the GPU. Last E79 JTAG I fixed needed a new GPU fitted.

If it's working intermittently (when put back in the chassis for example), it may just be a wiring issue. Take a pic and post it up.
Martin knows his stuff here and has helped me in the past (hello again Martin :p), however I have my tuppence worth to add.

I had a problem with a Xenon E79 after it was jtagged, and working fine for a small period of time (like only a few hours). After checking jtag points with multimeter, testing diodes were ok etc, reflashing back to stock nand was the only way I could get it to stop throwing E79.

Now you may have read that the Freeboot images are based on the 7371 dashboard. This console happened to be on an earlier version than this when I created my FB image. I thought nothing of it as I have done several jtags on consoles with pre 7371 dash and had never needed to update to 7371 before. So I thought I would have one last crack and flash stock nand back, update to 7371 with official MS update, then re-dump nand and rebuild FB image. Voila E79 gone and console working fine again.

Might be a complete fluke at my end but hey it worked and always worth a try, particularly if like I've said your console wasn't on 7371 in the first place.

Cheers
Mark