I've been reading here on the sidelines for a while, but I'm seeing a flash dump that has me perplexed and I'd like to submit to this forum's expertise.

I have raw data ripped from an 8GB tsop flash chip, I'm seeing each page being repeated 4 times as displayed in the attached screen shot. A program was written to help provide a visual: each row represents sequencial pages (starting from page 0). The column represents the first 100+ bytes of that page. The red bytes indicate bit differences from the previous row (intermittent bit errors).

I've cleaned the pins and repeated the extract with same outcome, this data repetition goes on throughout the dump.

I tried some experiments to check if the address bits were merely shifted by two into higher bits by reading a full 32GB and then comparing page data at 0,8GB,16GB,24GB, but these were all the same pages with the high order bits just being ignored.

I was inclined to conclude that there was some kind of bad connection to the IO pins, however conducted two tests which I believe ruled this out:
1. I forced the reader's page size to 32*[real page size], which (I'm assuming) causes the NAND chip to increase it's pointer internally instead of over the bus. I confirmed that one large read from the reader STILL produced the same repeating page sequence for bits 0-1.

2. I looked at the NAND's TSOP pinout and found that the IO pints are shared with multiple address bits, if there were IO errors at pins 0 & 1, then it would affect additional address lines.

8 BIT
IO0 IO1 IO2 IO3 IO4 IO5 IO6 IO7
A00 A01 A02 A03 A04 A05 A06 A07
A08 A09 A10 A11 LOW LOW LOW LOW
A12 A13 A14 A15 A16 A17 A18 A19
A20 A21 A22 A23 A24 A25 A26 A27

16BIT
IO0 IO1 IO2 IO3 IO4 IO5 IO6 IO7 (I08-I15 LOW)
A00 A01 A02 A03 A04 A05 A06 A07
A08 A09 A10 LOW LOW LOW LOW LOW
A11 A12 A13 A14 A15 A16 A17 A18
A19 A20 A21 A22 A23 A24 A25 A26


However the data did now show any addressing problems at bit A08 or A09.

I'm out of ideas, so my questions are:
Has anyone else ever seen this?
Is there anything else I can try?
Is the NAND chip is bad?

Please disregard the quoted line since I was being tricked by a bug. The chip is actually returning 0xff bytes after the page data is read.