--- JTAG just stopped working - any advice appreciated! ---

[makks]

Hi ppl,

Jtag (AUD_clamp) was working fine - console powers on, gives a little beep and boots right into custom 9199.

Now upon power on, it sometimes beeps, but always shows a black screen.

-no difference regardless of jtag QSB setting
-no difference in using power or eject button (so xell doesn't boot either)
-DVD tray still opens after pressing eject 2 times.

Since console is a Jasper-256, internal MU was erased (nandpro usb: -e256 1000) about 20 boots ago, no problems during those until now.

Flashed previously working XBR3 back, same black screen.
Then flashed first 1000 blocks (66mb) of original 7371 NAND back, boots fine on *all 3* jtag QSB settings.

Isn't 7371 kernel supposed to e72 on 2 of the JTAG QSB settings? Does this mean bad soldering on jtag wires then?
Or could efuses somehow got blown?


any help much appreciated

 

[sick360mods]

have u tried writing back ur orig nanad. if that still give u black sreen then uyr gpu needs a reflow

 

[makks]

original boots fine on all jtag QSB settings :/

Then flashed first 1000 blocks of original 7371 NAND back, boots fine on *all 3* jtag QSB settings.

Isn't 7371 kernel supposed to e72 on 2 of the JTAG QSB settings? Does this mean bad soldering on jtag wires then?

 

[rocket8080]

The original nand image should only boot when the switch is set to off on the qsb. I would say maybe a bad solder connection on the jtag if its booting when switched on.

 

[manwithoutname]

Then flashed first 1000 blocks of original 7371 NAND back, boots fine on *all 3* jtag QSB settings

He's already flashed his old 7371 nand and it booted fine. As far I know it doesn't matter what position the QSB switch is on when the the original NAND is booted, console should work as normal and not give any E** codes (specially when the modded jtag SMC point uses the AUDIO_CLAMP which is not active with the original NAND).

Possibly corrupt MU????

 

[makks]

The original nand image should only boot when the switch is set to off on the qsb. I would say maybe a bad solder connection on the jtag if its booting when switched on.

So its the soldering...

the soldering wasn't touched between last time it worked and now, could the heat somehow disconnected the soldering?

 

[rocket8080]

No, solder melts way hotter than what the xbox temp reaches.

 

[makks]

Possibly corrupt MU????

Internal MU wasn't used between last time it worked and now. Indeed the MU portion of the NAND was erased for that very reason (corruption).

Any point in writing back the original MU portion of NAND and see if it works?

 

[rocket8080]

I would try and do a erase of the full nand and try the original freeboot image you created, also have a look over your solder connections make sure nothing looks suspect.

 

[Xmods]

The original nand image should only boot when the switch is set to off on the qsb. I would say maybe a bad solder connection on the jtag if its booting when switched on.

original nand will boot with the switch in any position


i would try rewriting your custom nand to the ox see what happens

 

[M AzeeM K]

Did you make a backup of the NAND while it was working fine?

 

[makks]

Did you make a backup of the NAND while it was working fine?

unfortunately not,

the thinking was: its working then- if it stops working, then just re-flash the already working image... seems so stupid now :/

 

[makks]

another thought: could the NAND-X jtag diodes or QSB have been overheated by soldering iron?

 

[Xmods]

another thought: could the NAND-X jtag diodes or QSB have been overheated by soldering iron?

this would cause e79 what odd part is the working then 1 day black screen

 

[M AzeeM K]

this would cause e79 what odd part is the working then 1 day black screen

Ditto...

By the way, which tutorial did you follow while Jtagging your Xbox360?

 

[makks]

which tutorial did you follow while Jtagging your Xbox360?

http://team-xecuter.com/forums/showthread.php?t=55189
M AzeeM K's tut was followed until the CPU key was shown, then Jtag tool was used to create 0.032 image (couldn't get XBR3 to Freeboot to work).

Here the process exactly (srry for the long read):


1. Updated Jasper256 to official 7371

2. Dumped NAND(256mb) 3 times, verified in NandCompare, dumps identical with 1 bad block in kernel zone (block 678)

3. Extracted kv (1 1) and config (ef7 2)

4. Injected kv & config into XBR_JasperBB_8955_3.bin

5. Updated XBR3 using update-my-SMC!.exe as per MAK's tut

6a. Soldered NAND-X jtag wiring as per MAK's tut

6b. Flashed this XBR3_smc.bin to NAND, 360 boots, shows CPU key

7. Used Freeboot toolbox (BestPig) v.24 rev3 to create image, used CPU key & modfied smc from XBR3_smc.bin (using DumpSMC-fromANY_image.exe)

8. Flashed Freeboot to NAND, everything works apart from xb1 compat

9. Used Jtag Tool 1.74, selected mem editing (due to reverse selection bug) to make another image using same CPU key & modified smc

10. Flashed to NAND, now xb1 also works

11. Erased internal mu (nandpro usb: -e256 1000)

12. everything works, nothing is flashed or soldered from here on, no updates applied and no Live

13. Few days later, now - black screen


really hope to get to the bottom of this with the wonderful help of the experts here.

 

[M AzeeM K]

http://team-xecuter.com/forums/showthread.php?t=55189
M AzeeM K's tut was followed until the CPU key was shown, then Jtag tool was used to create 0.032 image (couldn't get XBR3 to Freeboot to work).

Here the process exactly (srry for the long read):


1. Updated Jasper256 to official 7371

2. Dumped NAND(256mb) 3 times, verified in NandCompare, dumps identical with 1 bad block in kernel zone (block 678)

3. Extracted kv (1 1) and config (ef7 2)

4. Injected kv & config into XBR_JasperBB_8955_3.bin

5. Updated XBR3 using update-my-SMC!.exe as per MAK's tut

6a. Soldered NAND-X jtag wiring as per MAK's tut

6b. Flashed this XBR3_smc.bin to NAND, 360 boots, shows CPU key

7. Used Freeboot toolbox (BestPig) v.24 rev3 to create image, used CPU key & modfied smc from XBR3_smc.bin (using DumpSMC-fromANY_image.exe)

8. Flashed Freeboot to NAND, everything works apart from xb1 compat

9. Used Jtag Tool 1.74, selected mem editing (due to reverse selection bug) to make another image using same CPU key & modified smc

10. Flashed to NAND, now xb1 also works

11. Erased internal mu (nandpro usb: -e256 1000)

12. everything works, nothing is flashed or soldered from here on, no updates applied and no Live

13. Few days later, now - black screen


really hope to get to the bottom of this with the wonderful help of the experts here.

Did you try to write the freeBOOT image generated by Jtag Tool and/or Freeboot Toolbox to the NAND again and see if it worked?

 

[makks]

Did you try to write the freeBOOT image generated by Jtag Tool and/or Freeboot Toolbox to the NAND again and see if it worked?

Tried already and unfortunately, still black screen.

Tried breaking jtag wiring - disconnected TRAY_OPEN wire from mobo (jtag red diode wire). Powered on - same black screen : /

 

[makks]

Its still booting to black screen, it *has* to be one of the following: (process of elimination by logic)

1. Motherboard is faulty
​

Cannot be, as re-flashed original 7371 boots just fine.
​

2. Incorrect video cable / mode

In addition to above, the same Component AV cable has not changed (set to "HDTV", although "TV" still result in black screen)
​

3. Incorrectly made Freeboot image or bad original dump

Cannot be, NAND was not touched before it started black screening. If the same image worked before, then it must have been correctly made.
​

4. Correct Freeboot image but bad blocks

There is a bad block at 0678, with block ID 00CF (Jasper big block = 8 small blocks, CF x 8 = 678). This block has *not* been relocated in original NANDs and seems unrecoverable.

The block 00CF on pre-made Jasper-16mb and Falcon NANDs has much data, as opposed to just FFFFs.

If there exists a pre-made 66mb Big block NAND, then it would easy to relocate 0678 to the end bad block area.

This still doesn't explain why it booted fine before, next day boots to black screen.
​

5a. AUD_clamp wiring is bad
5b. AUD_clamp wiring is fine but overheated traces.

Most likely. (they both mean a broken AUD_clamp connection?)

Is there an error code which appears when AUD_clamp connection is bad but software (XBR, Xell, ect.) is flashed correctly?

Because if I can get this error code to appear, then its bad AUD_clamp connection for sure.
​

This jasper motherboard has always been in a cardboard box, and worked fine for weeks. Could something have shorted?

and causing it to boot black screen only under AUD_clamp?

 

[rocket8080]

Is there an error code which appears when AUD_clamp connection is bad but software (XBR, Xell, ect.) is flashed correctly?

Is E79 error for bad jtag wiring. The only time I ever got a boot to black screen is when Ive had the smc wrong. If your using the qsb's maybe its worth a go at doing the direct wire method. Also maybe flash the 7371 original nand image that works back on to the xbox and start from scratch again.

EDIT

AUD_clamp wiring is fine but overheated traces.

Whats your soldering like?