nand read differences

[.:.VEGETA.:.]

Sorry if this has been answered b4, i did a search i could not find anything.
I have installed the pin header install for nand reding (not put the jtag in yet) after reading the nad 3 times i checked for differences using TOTALCMD. it came up with 2 differenes. I then read the nand 8 more times and kept getting 1-5 differences, although 2 of them now match should I go ahead with the nand that matches?? Also I have 2x 250 errors reading block 29c and 3C0 I hear this is not an issue.

EDIT: I now have 3 that match, but i had to do 14 dumps to get them.

 

[manwithoutname]

Compare your dumps with nandcompare and report back, bad blocks are normal so long they stay the same in all the dumps you made.

Personally I wouldn't write anything to my NAND unless 3 continues dumps match in nandcompare.

 

[.:.VEGETA.:.]

Compare your dumps with nandcompare and report back, bad blocks are normal so long they stay the same in all the dumps you made.

Personally I wouldn't write anything to my NAND unless 3 continues dumps match in nandcompare.

Okay I used nandcompare. The problem seems to be block 29C (which is one of the 2 bad blocks from my orginal dumps) it always comes up with (except the 3 that matched in TOTALCMD which come up as perfect) with "1 non-matching block(s) found 29C." But the block itself is bad (it said so in NANDPRO) so is there anything i can/should do???

 

[manwithoutname]

We are not concerned with the bad blocks, they are there for a reason and we will deal with them once freeboot is created.

I suggest you dump 3 fresh dumps, make sure there is nothing interfering with your console. Good grounding and nothing else running next to it and the pin headers are well in place. Once you dumped those 3 fresh dumps, compare them again with nandcompare.

 

[.:.VEGETA.:.]

We are not concerned with the bad blocks, they are there for a reason and we will deal with them once freeboot is created.

I suggest you dump 3 fresh dumps, make sure there is nothing interfering with your console. Good grounding and nothing else running next to it and the pin headers are well in place. Once you dumped those 3 fresh dumps, compare them again with nandcompare.

Okay I re-dumped 3 more times, 2 of them matched the other didnt. The one that didnt had 29C as non matching again. also the 2 that matched together this time did not match the other 3 that matched. After puttin it throught TOTALCMD it found 1 difference. Once again it's coming from the bad block.

 

[manwithoutname]

There's defenitly something with your connection/soldering. At this stage I wouldn't recommend proceeding as once you written to your NAND there is no going back and if you got no good working dump then it's just asking for trouble.

If you have spare NAND-X connector you might want to cut the end wires and solder the wires directly to the board from beneath as I don't imagine you wanting to remove the pin headers.

 

[.:.VEGETA.:.]

There's defenitly something with your connection/soldering. At this stage I wouldn't recommend proceeding as once you written to your NAND there is no going back and if you got no good working dump then it's just asking for trouble.

If you have spare NAND-X connector you might want to cut the end wires and solder the wires directly to the board from beneath as I don't imagine you wanting to remove the pin headers.

I re-soldered twice before i even posted. Its the same block over and over again, surely if it were a bad connection then surely it would not be so consistent? Can you think of anything else it could be?

 

[manwithoutname]

Bad blocks are not affected in your case, they are physcially bad memory blocks located within your NAND and will continue to show no matter what. That's why we will remap them later.

What I'm saying is that if nandcompare keeps showing non matching blocks that means whenever your reading your NAND it's not 100% clean dump and has errors. This simply will lead to non working freeboot or if you need to write back your original NAND to your console for whatever reason then you can't get it working again.

 

[.:.VEGETA.:.]

Bad blocks are not affected in your case, they are physcially bad memory blocks located within your NAND and will continue to show no matter what. That's why we will remap them later.

What I'm saying is that if nandcompare keeps showing non matching blocks that means whenever your reading your NAND it's not 100% clean dump and has errors. This simply will lead to non working freeboot or if you need to write back your original NAND to your console for whatever reason then you can't get it working again.

Yeah I understand, i was pointing out that the only non-matching block is always the bad block. Is there anything else other than soldering that can cause a bad nand read?? If it's defo soldering then I will resolder for the fourth time.

 

[.:.VEGETA.:.]

Hmm just found this on xboxscene

http://forums.xbox-scene.com/index.php?showtopic=699426&st=15#

According to this guy bad blocks CAN cause a differential between dumps if some data is being read (as opposed to totally dead) but it does not matter since it gets remapped. Can anyone confirm this.

 

[manwithoutname]

Before you re-solder, try posting high resolution pictures of your board and soldering points. As I suggested if you have a spare NAND-X connector/wires then instead of messing around with the pin headers just solder to the back of the board.