xenon e79 trouble.

1

1980blakey

Full Member
Apr 10, 2011
26
1
Essex Baby
mcornbill said:
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
Click to expand...
Hi Mark, i to had 3 jtags go down one a day for 3 days lol, Turned out that when i updated with bestpig there was something wrong. my daughter finished playing with the first one at night swithched it off and in the morning it rrod? i knew it wasnt hardware as it was my first succseful rebal and only 24hrs old. I reflashed back to stock and all was well, this happened exactly the same the next 2 days with another 2 consoles.
I really cant yours being a hardware as well if it works with stock nand either! Does it rrod at all on stock? if not just proves its software.
 
Last edited:
manwithoutname

manwithoutname

1
Jun 4, 2010
3,080
0
No necessary, hence why I asked. I had slightly different situation with a Jasper that gave the E80 error during an update from 7363 to 7371 due to a protected efuse set. However since the owner didn't have his original nand dump I used a jasper's donor nand which got the console working fine.

So it's worth trying the original 6717 dump and see if the console works again.

1980blakey said:
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 :)
Click to expand...
 
1

1980blakey

Full Member
Apr 10, 2011
26
1
Essex Baby
It dosnt work with original nand dump only rrod 0022, I have just taken the xclamps off to do a reflow and noticed it has got the epoxy around gpu-cpu. Am i right in saying xenons never had this only opus as it hasnt got hdmi but does have the xenon power socket!
 
manwithoutname

manwithoutname

1
Jun 4, 2010
3,080
0
Your next step then to try is to find a donor 7371 nand with CB1903. If you find one flash that and see what happens.
 
1

1980blakey

Full Member
Apr 10, 2011
26
1
Essex Baby
i got a donor nand but i cant connect to it anymore, i plugged it into another jtag and can read from it o.k so my lpt cable and software is o.k, but the xbox does power up with center green light on but then does nothing!.
 
W

WestCoastConsoles

VIP Member
Dec 29, 2010
1,339
0
Portland, OR
Oh I see. So the box isn't even recognizing that it's available to write to. Hmm don't k kw what to do maybe try a reattach and post some pics of install. I would really like to get this going for you. But it's hard without images. What all is installed on the board I know LPT cable was removed but is jtag wiring still on
 
1

1980blakey

Full Member
Apr 10, 2011
26
1
Essex Baby


---------- Post added at 00:59 ---------- Previous post was at 00:56 ----------


---------- Post added at 01:00 ---------- Previous post was at 00:59 ----------
 
Last edited:
TilVl

TilVl

VIP Member
May 11, 2011
1,383
0
I know your console is working. Could be a problem with one of the points under the GPU where the hack takes place.

If you do a search you'll see a post from Martin the points and values it should be.
 
S

srt4fun

Senior Member
Sep 8, 2011
133
0
California
Have you tried the 2 Diode method for the JTAG hack? And For the NAND not showing up, it could have been just a bad flash, try this tut here.

I looked up the error codes you're getting:
0020 is Bridged solderjoint/Short - CPU/GPU/RAM, but also could be the JTAG wiring. Try alternate methods.
0022 is Bridged solder joint/Short GPU-> (H)ANA, also appears when xell is flashed to a JTAG-Fixed 360. (Possibly also when wrong dash version is flashed? Just a thought though.)

Also don't trash it...I had a Falcon board that gave me trouble for at least a month...restrained myself countless times from breaking it in half. Now it's my main JTAG. hahahaha!
 
Last edited:
1

1980blakey

Full Member
Apr 10, 2011
26
1
Essex Baby
Hi everyone, Ive fixed the problem of not being able to write to the nand by changing nands, I then put my old nand onto a spare board and could read from it again? dogdy connection? Anyway ive got a donor nand image from jtagtool so hoping i cant start to get somewhere now.
 
mcornbill

mcornbill

VIP Member
Jan 2, 2003
176
0
Birmingham, UK
1980blakey said:
Hi everyone, Ive fixed the problem of not being able to write to the nand by changing nands, I then put my old nand onto a spare board and could read from it again? dogdy connection? Anyway ive got a donor nand image from jtagtool so hoping i cant start to get somewhere now.
Click to expand...
Hopefully you'll get somewhere Blakey.

I've never actually updated old dash 360's to 7371 if they were on earlier dash's than 7371 before building my FB image. Never had any issues in the past but for my two E79ers I am now going to flash back to stock nand and run the 7371 update then re-dump some fresh nand images to build FB again. It's a long shot and I'm expecting to still get E79, that will then be my last attempt and I will have to assume they both need a reflow if it doesn't work.

It just seems ominous now that the only two jtags I decided to update with 13599 to get avatars back both develop E79. Never had E79 before when tagging with FB 13599 and not updating afterwards to get avatars back. Is the 13599 update from Coolshrimps Jtag Tool different from the official 13599 update from MS can anyone confirm? I did use the update from Coolshrimp anyway but was just wondering.

Cheers
Mark
 
Last edited:
1

1980blakey

Full Member
Apr 10, 2011
26
1
Essex Baby
Well im on the right tracks as its back to e79, so just need to sort the original problem of why the jtag isnt working. I have been looking for the points and values post but cant find it, does anyone have a link? plz.
 
You must log in or register to reply here.