ANSWERED multiple dumps, no match, same block

knuckfoes

Full Member
Feb 23, 2012
32
0
hi all,

just got a 256mb jasper. using j runner i have made 6 dumps of my nand. i get error 250 on blocks 500, 508, 510, 518 on every read.

when i compare the nands, none of them match. the difference is ALWAYS block 510. and only block 510.

does this mean that my reads are ok and that it is a bad block and i just continue on.

asking as i dont want to flap up and brick it

thanks
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
What version of J-Runner do you have?

It should be erasing the bad block prior to comparison, so a little confused as to why you're seeing this.

Open your NAND in 360 Flash Dump Tool and check to see if these blocks are being remapped already. If so, you should be ok to carry on.
 

knuckfoes

Full Member
Feb 23, 2012
32
0
thanks martin.

im using j runner 262.

flash dump tool tells me 4 bad blocks at A0,A1,A2,A3 have been remapped to 1FC,1FD,1FE,1FF

nothing about 510 though
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
do this:

nandpro usb: -r64 510.bin 510 1

nandpro usb: -r64 510.bin.2 510 1

fc /b 510.bin 510.bin.2

How many differences do you get?

I think what's throwing J-Runner off is that error 250 simply means 'empty block', which you can get from time to time especially on BB Jaspers. Open the 510.bin file in a hex editor and let me know what you see.
 

knuckfoes

Full Member
Feb 23, 2012
32
0
apologies. my internet went down. cant get nandpro running. it opens and quickly closes a command prompt. on windows 7 x64. will troubleshoot now.

unless you got suggestions?

---------- Post added at 21:13 ---------- Previous post was at 21:09 ----------

edit. sorted nandpro. really do belong in noob section
 

knuckfoes

Full Member
Feb 23, 2012
32
0
its reading error 258 now. there are no matching pairs on comparison. about to DL a hex editor
 

knuckfoes

Full Member
Feb 23, 2012
32
0
getting read errors of 250 and 258 now. with the hex editor i really have no idea what im looking at. left habd column starts at 0 down to 41F1. centre part is all zeros from 0 to 1067. then its a mixture of 00 and FF until 1CD2 wher it becomes 03 and 07 and 00 and 01. then it becomes 00 and FF again at 18C5. this changes a few more times until it ends in all FF from 2101.

hope that means something to you
 

Thanet_360s

VIP Member
Dec 6, 2011
180
0
Thanet, ENGLAND
getting read errors of 250 and 258 now. with the hex editor i really have no idea what im looking at. left habd column starts at 0 down to 41F1. centre part is all zeros from 0 to 1067. then its a mixture of 00 and FF until 1CD2 wher it becomes 03 and 07 and 00 and 01. then it becomes 00 and FF again at 18C5. this changes a few more times until it ends in all FF from 2101.

hope that means something to you

double double and TRIPLE check ALL your soldering. this can be down to dodgy points mate.

had a few like that myself. and make sure you use FLUX :D
 

tingedace

VIP Member
Feb 23, 2011
387
0
Scotland
This is a big block NAND so block 510 is block A2 as reported by 360 flash tool.

If moving manually with nandpro you need to move 8 blocks at a time.
Easy to be caught out with this!
 
  • Like
Reactions: knuckfoes

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
No worries - to clarify, what tingedace says is correct:

BB NANDs are either addressed as 16kb blocks (NANDPro for example) or 132kb blocks (360 Flash Dump Tool). This is why with NANDPro you need to specify blocks of 8 (16 x 8 = 132) and why when you manually remap you go to FF8 (FF8 / 8 = 1FF) and why A2 * 8 = 510.
 

knuckfoes

Full Member
Feb 23, 2012
32
0
well we are all done. thanks to all. only issue left is massive boot times. will pick up a 68nF cap tomorrow.
cheers all
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com