Xenon JTAG Random Errors

[bob1258]

This is the second 360 I've had the pleasure of jtaging; or maybe I should say displeasure.  I am having problems beyond belief.  I haven't gotten anywhere, despite sifting through Google for 6 hours.

I am working with a USB SPI interface, just for the record.

For starters, yes, it is exploitable, with a 6xxx dash, CB 1921.  I have done everything from flashing just xell to the xbox, to making my own xbr image, and everything I can imagine in between.

The main errors I get (and I don't quite remember when exactly they occur) are a solid green light on the power button (most common), E79, E74, and E71.  I was able to boot into xell once, but I was greeted by errors, and it wouldn't boot back into it again.

I have also tried flashing my original nand back every so often, and the xbox boots fine.

There is also a bad block at 3A7.  At first I tried writing it to the same spot on the xbr image (silly me) until I found that it is supposed to me remapped to the very end; this did not help either.

I am just dumbfounded on what to do...my diodes are definitely working, as I've swapped them with new ones; but still, nothing.  I'm beginning to believe it has something to do with the bridge on j2d2? 

If desired, I can provide pictures of my wiring, and further information...

[l_oliveira]

I'm sorry to inform you but if you've seen E74, it's already afflicted with a faulty GPU.  The more you flex the board, the less chances you have of making it work properly.

For now, I suggest that you protect the efuses from being blown, flash back the original NAND and assembly it back on the metal cage. (after securing it properly with some X-CLAMP mod)

Do not undo the JTAG diodes. Once you have it working property inside the metal cage, with all screws fastened you proceed to do the software part.

I suggested you to protect the fuses from blowing as you will need to have it assembled. The more you flex the board the worse/harder will be to make it work.

[bob1258]

That's odd...Before I began the process, I turned it off and on about 10 times in a 30 minute period to be sure it was in working condition.  I should also add that this xbox was sent in for repairs years ago, but the friend who gave it to me never used it once he got it back.  I respect your judgement, but each of these errors occurred when I did a certain thing to the nand, i.e. flashing config, not flashing config, not remapping, etc.  E74 never once happened on the original nand.

Also, when I jtag, I don't take the motherboard out of the metal case because I try to avoid as much flexing as possible (unplugging and plugging in the power cord on this is rather difficult, and I didn't want to risk anything).  In fact, I didn't remove it from the case until tonight.

However, I have no doubt that the GPU could be faulty considering it's a release console, and has needed a repair before.  However, I fail to understand why I am getting so many other errors...

[l_oliveira]

That's odd...Before I began the process, I turned it off and on about 10 times in a 30 minute period to be sure it was in working condition.  I should also add that this xbox was sent in for repairs years ago, but the friend who gave it to me never used it once he got it back.  I respect your judgement, but each of these errors occurred when I did a certain thing to the nand, i.e. flashing config, not flashing config, not remapping, etc.  E74 never once happened on the original nand.

Also, when I jtag, I don't take the motherboard out of the metal case because I try to avoid as much flexing as possible (unplugging and plugging in the power cord on this is rather difficult, and I didn't want to risk anything).  In fact, I didn't remove it from the case until tonight.

However, I have no doubt that the GPU could be faulty considering it's a release console, and has needed a repair before.  However, I fail to understand why I am getting so many other errors...

Get yourself an X-NAND or simular USB SPI flasher and you take a unreliable LPT port from the equation. Even if your PC has a reliable LPT port, processes polling it might cause data corruption during writes, causing the odd behaviors.  The only scary one was the E74 error which is specific to a certain GPU fault (EDRAM).

[neonpolaris]

Get yourself an X-NAND or simular USB SPI flasher ...

I am working with a USB SPI interface, just for the record.

If you flash back to original and get no problems at all, it seems like your board is ok.  A bad GPU would affect stock/jtag equally bad.  This seems to point to either your XeLL/XBR image being bad/wrong, your jtag wiring unreliable, and/or not unplugging the device between flashes (to refresh SMC).

[bob1258]

I know for sure the many times I flashed xell it was the right version for my motherboard, so I can rule that out.  Last night I flashed xbr with my config, kv, and remapped block 3A7 to 3FF; I get E79, secondary 1033...it definitely must have something to do with the diodes/jumper, because I do let it sit for a few minutes w/o any cables plugged in.  However, all of my connections are solid and clean...Maybe I should try doing it on the bottom of the board?

[l_oliveira]

I know for sure the many times I flashed xell it was the right version for my motherboard, so I can rule that out.  Last night I flashed xbr with my config, kv, and remapped block 3A7 to 3FF; I get E79, secondary 1033...it definitely must have something to do with the diodes/jumper, because I do let it sit for a few minutes w/o any cables plugged in.  However, all of my connections are solid and clean...Maybe I should try doing it on the bottom of the board?

Doesn't matter much if you have corruption while the data is being sent to the board.  A decent test would be dump the current contents of the flash and compare with the file you uploaded to it.

If both files match, then the LPT port must be working properly.

[neonpolaris]

Again, he said he was using a USB SPI interface.

Of course, dumping the nand back and comparing would rule out a bad write, and worth a look, but if he never gets symptoms when flashing back to stock, it *suggests* that writing is ok.

Bad jtag wiring/components will give you E79.  Bad remapping will give you a myriad of symptoms.  Other threads have had good results with replacing diodes that they did not know were faulty.

[bob1258]

Just to make sure I'm remapping correctly:  I have a bad block at 3A7.  It being error 250, I just do nandpro usb: -r16 3A7.bin 3A7 1, and then nandpro xbr: -w16 3A7.bin 3FF 1

I will buy some new diodes later tonight...hopefully all goes well and it's not more money wasted...

If new diodes still do not work, are there any other options, any hope for this xbox?

[l_oliveira]

Just to make sure I'm remapping correctly:  I have a bad block at 3A7.  It being error 250, I just do nandpro usb: -r16 3A7.bin 3A7 1, and then nandpro xbr: -w16 3A7.bin 3FF 1

I will buy some new diodes later tonight...hopefully all goes well and it's not more money wasted...

If new diodes still do not work, are there any other options, any hope for this xbox?

You need to read the block 3A7 from the IMAGE FILE that is on your PC harddisk and flash at 3FF on the XBOX NAND.
Basically you're flashing an readback from the 3A7 corrupted block to the remap area. Bogus data.

That's what you're doing wrong.

Now, after flashing the whole image on the nand (ignore the error at 3A7) do this:

nandpro xbr: -R16 3A7.bin 3A7 1    (we're reading the block data without ECC so -R)
nandpro usb: -W16 3A7.bin 3FF 1  (we're having nandpro re-create the ECC data so -W)

[bob1258]

You need to read the block 3A7 from the IMAGE FILE that is on your PC harddisk and flash at 3FF on the XBOX NAND.
Basically you're flashing an readback from the 3A7 corrupted block to the remap area. Bogus data.

That's what you're doing wrong.

Now, after flashing the whole image on the nand (ignore the error at 3A7) do this:

nandpro xbr: -R16 3A7.bin 3A7 1    (we're reading the block data without ECC so -R)
nandpro usb: -W16 3A7.bin 3FF 1  (we're having nandpro re-create the ECC data so -W)

So, after flashing xbr (config and kv included) over the original nand, I proceed with that?  I read the block from my xbr image, remapped it to 3FF, and didn't work.

Could this be the answer to my problems?  Or did I misinterpret your instructions (which I think I did...) : http://www.team-xecuter.com/forums/showthread.php?t=55007

Also, I am unsure if this is an issue, but with the jumper wire in place, I'm still able to read/write the nand...It was my belief that this wire prevented reading/writing to the nand.

[neonpolaris]

I can't tell from the photo what's different in that kit.  Different diodes?  Resistors instead of diodes, maybe?

If you knew what was on that board, you could try it without having to buy the kit.  Removing "quicksolder" parts is a real pain in the ass without damaging the board.

I suppose it's possible that you just have a problem board like they mention.  I read through that thread and it seemed like most of the people asking for the kit just had really terrible soldering jobs, though.

I would say rebuild your XBR starting from your original known good image again, and make sure you understand how remapping works.  There's no point in taking your iron to your board over and over if all you did was make a typo somewhere and kept using the same files.

[bob1258]

So, after reading many tutorials on remapping, I have come to this process...

nandpro usb: -w16 xbr.bin (kv and config included)

nandpro xbr.bin: -R16 3A7.bin 3A7 1

nandpro usb: -W16 3A7.bin 3FF 1

I'm sure I'm forgetting something, but from trying what you, l_oliveira said, along with many other tutorials, it's not working.  I'm not getting any write errors either.

I could upload my nand if one of you would like to see it for yourself, rather than relying on what I'm saying.

Also, I'm sorry if I'm not understanding this completely, or if I've been ignorant...I've put in 3+ hours every night searching google, looking up tutorials, etc...I am very frustrated. 

[neonpolaris]

Try writing just the standalone XeLL image.  It's not long enough to worry about remapping that block at 3A7.  If it doesn't boot, it almost certainly points to your wiring.

[Xumpy]

Why make it so hard with all this remapping of bad blocks?

Just boot xell, afterwards run the gentoo live cd from http://free60.org. Plug the xbox into your network and sent the file to your system. Flash it with the command xbrflash and the remapping is done by gentoo.

BTW if xell gives you errors, I believe your using bad diodes. What kind of diodes are you using (what is the type/nr)

[bob1258]

Why make it so hard with all this remapping of bad blocks?

Just boot xell, afterwards run the gentoo live cd from http://free60.org. Plug the xbox into your network and sent the file to your system. Flash it with the command xbrflash and the remapping is done by gentoo.

BTW if xell gives you errors, I believe your using bad diodes. What kind of diodes are you using (what is the type/nr)

I have both 1N4148 and 1N914, neither of which work.  Xell will not boot with either in place.  I also tried putting the jumper wire on the back. 

I'm beginning to think that this console requires that special wiring...

[NetMan66]

 Are you sure your diodes are facing the proper direction.  look for the "Black line" and make sure they are oriented properly in the wiring.

[bob1258]

 Are you sure your diodes are facing the proper direction.  look for the "Black line" and make sure they are oriented properly in the wiring.

Yes, they are facing the proper direction.

[modme09]

As stupid as this sounds I had one that would e79 due to my RF board was slightly tilted down and to the right after unpluggin it and remounting it the E79 would go away and for the hell of it I unmounted it then itd E79 moved it back in place bam no E79( this was a Falcon but I solder to the bottom of the board and itd still do this)

[l_oliveira]

Have you tried to remap the bad blocks with an automated tool and then flash the whole image (with blocks already remapped) ?