Keeping getting errors reading

[segseven]

Sorry guys i know u will anser it bad soldering,
i did a jasper withou prob, now the slim, got tricky always the same bad block, checked wiring, removed qsb, reeinstalled, did direct cables, and the result is always the same.

I also have this 2 points briged is that normal?

The guy who soldered said it looked like an alternate

my logs are

K:\resources\xbox\rgh\Nandpro30>NandPro.exe usb: -r16 nand1.bin
NandPro v3.0a by Tiros

Looking for usb interface device
Flash Config: 0x00023010
Block Size: 16KB Block Limits: 0x000000..0x0003FF
File: nand1.bin
Reading
Error: 25C reading block DE
Error: 254 reading block 384
03FF

K:\resources\xbox\rgh\Nandpro30>NandPro.exe usb: -r16 nand2.bin
NandPro v3.0a by Tiros

Looking for usb interface device
Flash Config: 0x00023010
Block Size: 16KB Block Limits: 0x000000..0x0003FF
File: nand2.bin
Reading
Error: 25C reading block DE
Error: 25C reading block 384
03FF

K:\resources\xbox\rgh\Nandpro30>fc /b nand1.bin nand2.bin
Comparing files nand1.bin and NAND2.BIN
00393E83: DF FF
00393F28: FF F7
00393F73: FF F7
003950E2: FF DF
0039510F: FF DF
00395112: FF DF
00395113: FF DF
00395712: FF DF
0039573C: FF DF
00395743: FF DF
00395754: FF DF
00395922: FF DF
0039594F: FF DF
00395952: FF DF
00395953: FF DF
00395F52: DF FF
00395F7C: DF FF
00395F94: DF FF
00396792: FF DF
003967BC: FF DF
003967C3: FF DF
003967D4: FF DF
00397A22: FF DF
00397A4F: FF DF
00397A52: FF DF
00397A53: FF DF
00397C32: DF FF
00397C5C: DF FF
00397C63: DF FF
00397C74: DF FF
00E80ED3: FE FF
00E812F3: FE FF
00E82732: FF FD
00E8278F: FF FE
00E82806: FF FD
00E82B52: FF FD
00E82BAF: FF FE
00E82C26: FF FD
00E837B2: FF FD
00E8380F: FF FE
00E83886: FF FD

 

[esbmaepo]

Sorry guys i know u will anser it bad soldering,
i did a jasper withou prob, now the slim, got tricky always the same bad block, checked wiring, removed qsb, reeinstalled, did direct cables, and the result is always the same.

I also have this 2 points briged is that normal?

The guy who soldered said it looked like an alternate
Link To Image
my logs are

K:\resources\xbox\rgh\Nandpro30>NandPro.exe usb: -r16 nand1.bin
NandPro v3.0a by Tiros

Looking for usb interface device
Flash Config: 0x00023010
Block Size: 16KB Block Limits: 0x000000..0x0003FF
File: nand1.bin
Reading
Error: 25C reading block DE
Error: 254 reading block 384
03FF

K:\resources\xbox\rgh\Nandpro30>NandPro.exe usb: -r16 nand2.bin
NandPro v3.0a by Tiros

Looking for usb interface device
Flash Config: 0x00023010
Block Size: 16KB Block Limits: 0x000000..0x0003FF
File: nand2.bin
Reading
Error: 25C reading block DE
Error: 25C reading block 384
03FF

K:\resources\xbox\rgh\Nandpro30>fc /b nand1.bin nand2.bin
Comparing files nand1.bin and NAND2.BIN
00393E83: DF FF
00393F28: FF F7
00393F73: FF F7
003950E2: FF DF
0039510F: FF DF
00395112: FF DF
00395113: FF DF
00395712: FF DF
0039573C: FF DF
00395743: FF DF
00395754: FF DF
00395922: FF DF
0039594F: FF DF
00395952: FF DF
00395953: FF DF
00395F52: DF FF
00395F7C: DF FF
00395F94: DF FF
00396792: FF DF
003967BC: FF DF
003967C3: FF DF
003967D4: FF DF
00397A22: FF DF
00397A4F: FF DF
00397A52: FF DF
00397A53: FF DF
00397C32: DF FF
00397C5C: DF FF
00397C63: DF FF
00397C74: DF FF
00E80ED3: FE FF
00E812F3: FE FF
00E82732: FF FD
00E8278F: FF FE
00E82806: FF FD
00E82B52: FF FD
00E82BAF: FF FE
00E82C26: FF FD
00E837B2: FF FD
00E8380F: FF FE
00E83886: FF FD

Well your Flashconfig is right, so theres no trouble reading. Bad blocks are common. Create ecc - file and flash it. Grap your cpu key. Run your orig nand through Multibuilder, thats gonna remap bad blocks for you. You can check in Multibuilder log-file. Flash nanddump.bin and it should work.

Why did he bridged the two points?

 

[segseven]

i know bad blocks happens, bad the nand compares fails every time, the point are bridged somehow, i asked if this is normal? if not perhaps is the reason why my nand dumps/comparing keeps failing all the times.

 

[esbmaepo]

i know bad blocks happens, bad the nand compares fails every time, the point are bridged somehow, i asked if this is normal? if not perhaps is the reason why my nand dumps/comparing keeps failing all the times.

It is not normal and it shouldn't be bridged.

And I asked you why "this guy" bridged them:rolleyes2:

 

[segseven]

well they weren't bridged on purpose of course but under magnifient glass theres is nothing visible, over and under the board

i it wasn't me who soldier it i don't know jack about that, i stick to program stuff, so any ideas b4 we scrap the whole thing off the board again, once more?

 

[segseven]

Read Dark Fiber's guide again, so if i understand correctly if bad block are found i will not get matching nands right, on 360 flash dump tool 0.97 all bad blocks found are found at another location as my 0x00DE and 0x0384 are below 0x0050, so i'm safe to write xell even though i don't have matching nands right? Thnx for the help by the way esbmaepo!!!

 

[esbmaepo]

Read Dark Fiber's guide again, so if i understand correctly if bad block are found i will not get matching nands right, on 360 flash dump tool 0.97 all bad blocks found are found at another location as my 0x00DE and 0x0384 are below 0x0050, so i'm safe to write xell even though i don't have matching nands right? Thnx for the help by the way esbmaepo!!!

Yes thats correct. But you should not flash anything to NAND before you have solved this reading issue! You risk a bad nand flash and a shortend NAND chip.

You must have matching NANDs before you continue flashing!

You have to start over again I'm afraid. Look for any shorts. It could also be your nand reader, what are you using? Make sure it works.

 

[segseven]

im using nand-x with v3 code, flashed nand for a jasper and coolrunners (jasper & trinity) without probs, so you're saying we must discover where the yellow is bridged shorted to read again even though the bad blocks are always the same?
any ideas to look besides the j2c1 area?

 

[esbmaepo]

im using nand-x with v3 code, flashed nand for a jasper and coolrunners (jasper & trinity) without probs, so you're saying we must discover where the yellow is bridged shorted to read again even though the bad blocks are always the same?
any ideas to look besides the j2c1 area?

You do NOT have matching nands right?

I mean, even if you have bad blocks your NANDS may still match.

Try this:

1) Read nand again 2 times

2) Compare your NANDS in JTAG Tool

3) Tell me what JTAG Tool says

 

[segseven]

it say 2 non-matching block(s) found
DE
384

if i eliminate this blocks from the 4 nands i dumped they all match following this guide http://team-xecuter.com/forums/showthread.php?t=75434

should i still worry about the yellow point passing continuity to the other still... i think nothing is going to go there... could be wrong though...

 

[esbmaepo]

it say 2 non-matching block(s) found
DE
384

if i eliminate this blocks from the 4 nands i dumped they all match following this guide http://team-xecuter.com/forums/showthread.php?t=75434

should i still worry about the yellow point passing continuity to the other still... i think nothing is going to go there... could be wrong though...

I think youre okay!

1) Go ahead and create your image_00000000.ecc file in Multibuilder and flash it.

nandpro usb: +w16 image_00000000.ecc

2) Boot xell and grab your cpu key.

3) Create your flashdump file in Multibuilder but DO NOT FLASH it just yet!

4) Post flashdump log file to me. Multibuilder should remap bad blocks for you.

 

[segseven]

Can someone with a trinity board please tell me just if the points i posted check for continuity? If i don't mess any writing somehow because of that.

Thanks again for all the help esbmaepo, the step after boot writing i did it b4, i didn't had any problems 'cause the jasper was error block free on the 16mb.

 

[esbmaepo]

Can someone with a trinity board please tell me just if the points i posted check for continuity? If i don't mess any writing somehow because of that.

Thanks again for all the help esbmaepo, the step after boot writing i did it b4, i didn't had any problems 'cause the jasper was error block free on the 16mb.

Sure I'm gonna check them for you as soon as possible

 

[Martin C]

If you want to eliminate bad blocks from your nands for comparison, delete them:

nandpro nand1.bin: -e16 DE 1
nandpro nand1.bin: -e16 384 1

nandpro nand2.bin: -e16 DE 1
nandpro nand2.bin: -e16 384 1

If they compare after this, you know you're ok.

Best way is to open in 360 Flash Dump Tool and make sure these blocks are being remapped to the reserved memory area (3FF and 3FE).

 

[segseven]

already did that Martin following some previous post of yours, they check just fine after (removing the blocks in question form the nands), i'm just afraid of the points i posted if they could induce error on writing... i think it should be ok, cause reading with and without qsb i had the same bad blocks, but as i said not a electrical guy ...

 

[Martin C]

It won't cause a problem from what I understand. You have a good NAND dump so you should be able to recover if needed.

 

[esbmaepo]

Can someone with a trinity board please tell me just if the points i posted check for continuity? If i don't mess any writing somehow because of that.

Thanks again for all the help esbmaepo, the step after boot writing i did it b4, i didn't had any problems 'cause the jasper was error block free on the 16mb.

Okay I have checked the points for continuity and there is. So you are allright and can continue with your SLIM

 

[segseven]

many thnx guys, wish I saw your other thread Martin b4 we soldered / desoldered the qsb twice see u when I have a red dot xD