xenon e79 trouble.

[1980blakey]

Hi all, Just to start this is my 5th jtag, i only do them for friends and family because i enjoy it not for profit.
This is the 2nd xenon ive had trouble with, the first had a broken trace i managed to fix and all was o.k but this one just will not work.
specifics
Xenon with 6717 dash.
Cb 1903.
I didnt update to 7371.
Efuses protected.
Flashing via lpt cable and nandpro which has never gave me any trouble.
3 x nand reads no bad blocks
Ive tryed the 3 330ohm resistors and the diodes 1n4148 with no luck.
Also used the TX e79 jtag with no luck.
Ive checked points j2d2.1 & j2d2.2 and getting 1.5k to ground also checked j2d2.4 1.5k and j2d2.7 60 ohms.
Neither xell or xbr will work just constant e79 unless i flash back to orig nand flash.
Ive tryed using all the xenon images and all the xenon xell files i can find but with no luck.
My soldering is quite good with many years of practice BUT i will double check anything anyone wants me to as im totaly stumped.
I havnt got a good enough camera to post picks. Thanks in advance.

 

[TheRealKTFO]

Have you tried using JTAG TOOL by Coolshrimp? That's what I used on my first and only jtag and it worked like a charm.

Good Luck.

 

[BL4K3Y]

JTag Tool is just a front end for already-existant applications and it won't make a difference really. Try building your NAND image with fbbuild if you aren't using it already.

 

[1980blakey]

How cool another blakey lol, i will give it a go in the morning thanks.

 

[1980blakey]

o.k ive looked at the fbbuild, Do i need my cpu key first tho? if so i cant get it as i cant run xell or xellous? am i wrong about this? any more help would be great.

I just put original image back then used jtag tool to put xell on, gave it a couple of minutes unplugged and then turned on by ejecting, rrod 0022! switched it off and tryed turning on with controller in rear usb nothing for about 20 seconds and then rrod 0022! WTF?
I really dont know what to do, i only bought this as my daughters other jtag rrod 0022 the other day.

 

[1980blakey]

back on original image and all o.k again. Staring to give up on it, might just update it and give it to a friend.

 

[TilVl]

Might need a reflow. Even though it working might be a problem with the GPU and a reflow will most likely fix it.

 

[1980blakey]

Hi Tilvi, i have got a irda rework station but honestly dont think it needs it. It was on original x-clamps and thermal paste with seal intact so wasnt a rrod refurb.

 

[WestCoastConsoles]

Jtag tool is just a front for other operations but give it a whirl can't hurt right and if your flashing original NAND back and it's all good obviously it isn't grounds for a reflow/reball. Pics of the install would help but I understand not having a camera to do so. You must get your CPU key through xell/xellous to get the freeboot image built correctly and update to 7371 it will make things go smoother. Update there's a link available here redump the NAND and start fresh

I know the camera is good enough but try this is the only true way we can diagnose the issue

Jtag tool is awesome and I would highly reccomend using it.

 

[1980blakey]

Thanks for your reply, updating to 7371 is the only thing i havnt tryed. I will go and do this and then dump the nand again. I have just got my nokia n8 back from repair so will take pics with this and post in a bit. Thanks again.

 

[1980blakey]

O.k just updated to 7371 7mb file and now ive got rrod e80? tryed clearing updates with sync button but no go.
O.k im dumb, i didnt unsolder the points before updating, going to sort this now then update.

 

[WestCoastConsoles]

Are Your e fuses still protected remove and boot

Let me rephrase how did you protect your efuses did you remove the resistor or bridge the two points

This should work I the other doesn't flash old NAND back earlier dump you had remove efuse protection update and after all jtagging and everything is done protect your efuses

 

[1980blakey]

O no, unsoldered point and rebooted, all went well had new dash with 7371 but it froze, rebooted again and now 3rrod 0022 again. I think its going in the garage to be melted with the plasma cutter.

o.k im flashing it back to to orig again.

 

[WestCoastConsoles]

If it gets to that point I'll take it off your hands. Try flashing back original NAND and repudating minus efuse protection. But first boot with old NAND to check if it boots fine or not xenons are old consoles and can go at any time

 

[1980blakey]

Back to original nand and still 0022. I take it its fked as i havnt got my cpu key?

 

[1980blakey]

Right i have wrote xbr to it and then k.v and now getting 0020, Am i just flogging a dead horse or do i have a chance of sorting it without the cpu key? Anyone?

 

[WestCoastConsoles]

Hey just got home if you have a full original dump your fine but obviously now it has become a hardware issue. Is the jtag portion still installed after flash back original NAND.

I noticed over the years that consoles on the edge of failure can rrod when trying to tag them I would do a reflow it can't hurt

Please list any and all error codes along with secondary error codes so I can rack the brain for ya


Removed last little bit cause I wasn't thinking

 

[manwithoutname]

There is no point in trying to create Freeboot if you can't get xell to work. If one didn't work then the other won't.

Just to confirm, after you removed the efuse soldered points and resumed the 7371 after which the console froze, you flashed back the original 6717 dash but still getting RROD?

 

[mcornbill]

Right i have wrote xbr to it and then k.v and now getting 0020, Am i just flogging a dead horse or do i have a chance of sorting it without the cpu key? Anyone?

Hi Blakey

I have had two Xenons go from perfectly working on Freeboot 13599 images, to E79 errors. One within a few days, one within 2 minutes of it being tagged.

I too have tried a variety of reflashes, and one of them boots fine when original nand is put back on, I haven't tried on the other one yet as I noticed it had a very hot CPU temp rising rapidly when in XexMenu.

E79 error is usually associated with a corrupted nand, but I know my nands are straight and no doubt yours are too. A friend of mine reworks/reballs 360's and he reckons that all of the E79's he's been getting in are blown efuses in the CPU. If you protected yours then maybe this is not always the case. I hope so as I didn't remove my resistor or bridge the points as I wanted to run the 13599 update to get avatar and kinect functionality back. I assumed that had I protected the efuses then the 13599 update wouldn't apply.

The last thing I've read about it possible southbridge reflow needed. But then if it's a hardware issue why does the console work on stock nand still, bizarre! My money has to be on that now as everything else seems to be discounted.

Just my tuppence worth.

Cheers
Mark

 

[1980blakey]

There is no point in trying to create Freeboot if you can't get xell to work. If one didn't work then the other won't.

Just to confirm, after you removed the efuse soldered points and resumed the 7371 after which the console froze, you flashed back the original 6717 dash but still getting RROD?

Hi manwithoutaname, i was only instaling xbr to see if i could still maybe get my cpu key as the original read dosnt do anything as its a 6717 and i updated to 7371 then froze then rrod 0022, Am i right in thinking i cant use my original nand read as i cant go back after updating? i did remove the efuse protection to update. when i flash xbr and my k.v the error changes to 0020 which im taking its not a hardware failure?Thanks for your help

---------- Post added at 09:02 ---------- Previous post was at 08:57 ----------

Hey just got home if you have a full original dump your fine but obviously now it has become a hardware issue. Is the jtag portion still installed after flash back original NAND.

I noticed over the years that consoles on the edge of failure can rrod when trying to tag them I would do a reflow it can't hurt

Please list any and all error codes along with secondary error codes so I can rack the brain for ya


Removed last little bit cause I wasn't thinking

Hi LittleT, ive got 3 full original dumps backed up 3 times lol. I dont think it is a hardware issue as when i change from stock nand (0022) to xbr (0020) the error code changes. Thanks for your help.