JTAG tool Errors

[xTXRxFrosty]

I keep getting these errors whenever using jtag tool to create a freeboot and create an .ecc image.

This one for when I'm trying to create an .ecc image:

And when I try to create a freeboot image:

I can post pics of my wiring as well but I'm pretty sure its golden. I DID do a bypass alt point on the CPU_RST. Using thebombers tut that I found here.

I'm not exactly sure what I could be doing wrong but any and all feedback would be greatly appreciated.

 

[Martin C]

What console is it? Can you open your NAND in 360 Flash Dump Tool?

 

[xTXRxFrosty]

What console is it? Can you open your NAND in 360 Flash Dump Tool?

Its a slim console.

I'll search google for that program now... what exactly will that do?

 

[Martin C]

It's a tool you really should be using before writing anything to the console.

It tells you a lot of good information about your NAND dump.

Google '360 Flash Dump Tool 0.97'

 

[xTXRxFrosty]

It's a tool you really should be using before writing anything to the console.

It tells you a lot of good information about your NAND dump.

Google '360 Flash Dump Tool 0.97'

It is not letting me open my nand in that tool. It gives me an error saying, couldnt read file or this image isnt supported.

Now what should I do?

 

[Hackerjac]

did you get any error reading the nand ?

 

[Martin C]

Have you written anything to the console yet?

if not, use xNANDHealer - new version is out:

http://www.team-xecuter.com/forums/showthread.php?t=79855

 

[xTXRxFrosty]

I get no errors when I'm trying to read the nand using jtag tool.

Nothing what so ever... but for some reason no programs are liking my nand.

I'm checking out that xnandhealer right now... gonna have a go at it to see if that might help.

 

[Hackerjac]

try getting nandpro 3.0
try reading your nand with it using nandpro :usb -r16 nanddump.bin

 

[xTXRxFrosty]

try getting nandpro 3.0
try reading your nand with it using nandpro :usb -r16 nanddump.bin

When I use that method, this is the screen I get.

 

[xTXRxFrosty]

BUMP...

I'm really confused... could anyone shed some light on this situation for me??

 

[BL4K3Y]

That Flash Config is wrong in the screen shot you provided, Slim consoles have a Flash Config of 00023010 (same as Jasper 16MB)..... re-solder your SPI wiring and try reading again - Flash Dump Tool won't open the image you dumped because it isn't valid.

 

[xTXRxFrosty]

That Flash Config is wrong in the screen shot you provided, Slim consoles have a Flash Config of 00023010 (same as Jasper 16MB)..... re-solder your SPI wiring and try reading again - Flash Dump Tool won't open the image you dumped because it isn't valid.

I know I'm going to sound like a complete asstard right now...

I'm not following you on the SPI wiring... I'm using a QSB for the nand, and direct wiring for the two points on the back of the motherboard, so I'm not sure where to even go with that.

I'm not getting any errors what so ever in the reading process... so could it still be my soldering?

I've been working on this for over 2 days now, so I'm kinda getting frustrated at this point.

 

[BL4K3Y]

By SPI, I meant to read/write the NAND.

Check your soldering of the QSB, images would help.

 

[xTXRxFrosty]

Okay, so heres a couple shots... not so high quality but its the best I can do...

Keep in mind I am using alternative points for the blue wire on the bottom of the motherboard.

 

[xTXRxFrosty]

Okay, so I have an update on my situation... I'm absolutely confused, more so than ever.

I checked all my points visually, touched up a couple of them... made sure I wasn't bridging anywhere. I flipped around a little bit here and came across this tut from fib3r:

http://www.team-xecuter.com/forums/showthread.php?t=76193

I followed it to a T, everything was going great... I even checked if I could load my nanddump into 360 Flash Tool and it worked, where the nanddumps I was getting from Jtag Tool were coming up with errors upon loading... so anyway... everything was going great until I went to boot my console into Xell to get the cpukey.

The ROL blinked continuously... the CR green LED would blink, but no Xell.

Any suggestions?

 

[Martin C]

When I use that method, this is the screen I get.

Link To Image

Why are you WRITING to your NAND???????

You don't have a good image and now you're reliant on a donor NAND to get sorted.

 

[jtag360.nl]

Why are you WRITING to your NAND???????

You don't have a good image and now you're reliant on a donor NAND to get sorted.

That's what I just planning to say.

You are ussing -w16 instad of -r16.

Do you know what you are doing?

If you don't watch out you are killing your Slim.

And why is the heatsink off?

 

[KhaineGB]

Not only did he try to write to the NAND...

That Nandpro screenshot clearly states "Incompatiable ARM firmware for this version of Nandpro".

Go update your NAND-X. :facepalm:

 

[Martin C]

OP - you have a massive problem now.

From recent work I did on a slim here, I'm not 100% sure whether it's possible to glitch a slim without an ECC created from the original NAND as I believe it needs your keyvault. I was rebuilding a NAND last night and wanted to get it glitching for the LDV. It would only glitch once I built a replacement donor nand with the known CPU key (as that's all I had) and then an ECC image out of that.

I really hope I'm wrong on this, but if not (and at no point have you managed to dump your keyvault in any of the dumps you've done), you've just FUBAR'd the console.