2 bad blocks in this nand xbox 360 nand pro nand jtag Coolrunner

[mowax]

Good morning guys,

I've been directed to your site to see if you can help at all with a little problem that i have with a Jasper (512 meg) and a Coolrunner board that i've fitted.

Now i'm great (modest) with the soldering iron and have soldered 2 x QSB's to read the "nand" I have downloaded and installed "jtag Tool" and have done 2 reads of the nand.

Saved one in "nand read folder 1" and the 2nd in "nand read folder2"

Now when i go to compare them i get 2 bad blocks.

32768 block(s) in nand image
2 non-matching block(s) found
44
34EB

So I've downloaded and run "nand repair" and loaded nand 1 into source and then nand 1 as destination, it then gives me the warning of "it'll overwrite" etc. etc. So i allow it too and then if I try and load them nands back into jtag tool then it comes back with the failed blocks and of course can not continue.

So not sure what to do now as "nand repair" is telling me that it's saved them and amended them but jtag tool is still telling me that the blocks are bad.







Here an Example of the what jtag tool tells me




So I thought that I’d follow the a tut on mapping the bad blocks. I have mapped the address and the bad block, in the ”You Tube” video this guy shows you and he presses the "un-map" option,

When i do that and then select create freeboot and choose the "nand" the one it created i get the following error.







i see this when i select "un-map" in jtag tool..



I've been reading and has some sound advice from a few on here and there saying that the xell is in the 1st 50 blocks and of course that's where i'm getting the nand bad blocks.

I was then going to follow the "degraded" post but that's also throwing the toys out the pram.

I get the following error when i try and open the 1st nand that i read. (Having a ball at this i am!)

1.   If you are unfortunate enough to have a bad block in the first 50 blocks (where the ecc file goes), you'll find it hard to get the CPU key. Ironically, once you have the CPU key, Multi_builder will happily remap the block for you. Before you get there, you'll need to do it manually:



So then that got me onto editing the date to 2005 in a hex editor, so I’ve followed the procedure and then realised that at the end it told me “For Big Block consoles. Degraded will not open your image.”

So that’s not going to work either.

it's a huge jasper 500 meg sized 45 minute per nand read that I have been convicted off! (i know that there's a few saying that i don't have to read it all as xell confides in the 1st fifty blocks..or some thing like that) I was even thinking of ripping it all out and starting on another 360 but i ain't given up with it, + i'd also like to get it put up here for people to read. Nothing better than starting with the hardest most difficult thing going, (for me any way) done loads of broadcom reading/writing, blackkatz etc. so nearly getting my head around this new task!

Sounds like the nand was bad @ base, (so when M$ wrote it....according to why they are bad in the 1st place). (defo can't be the soldering as that's all sorted, tried 2 QSB's a direct wire etc.. Multi meter etc.. etc.)

Would anyone be able to give me any heads up please as I’m at a loss now.

Thanks all.