nand problem

M

mhd444

Junior Member
Dec 28, 2012
20
0
hi , i have jasper 512 and i try to read nand using j-runne with nand-x but every time i try this i got this erorr .....
Flash Config: 0x00AA3020
CB Version: 6751
Reading Nand to C:\Users\mhd\Documents\J-Runner v02 Beta (286) Core Pack\output\nanddump1.bin
Reading Nand
Done!
in 0:17 min:sec

Reading Nand to C:\Users\mhd\Documents\J-Runner v02 Beta (286) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Too Many Bad Blocks
Header is wrong..
Reading Nand
Nand Initialization Finished
Done!
in 0:18 min:sec

Comparing...
Bad Block ID @ 0x0000 [Offset: 0x0]
Bad Block ID @ 0x0001 [Offset: 0x4200]
Bad Block ID @ 0x0002 [Offset: 0x8400]
Bad Block ID @ 0x0003 [Offset: 0xC600]
Bad Block ID @ 0x0004 [Offset: 0x10800]
Bad Block ID @ 0x0005 [Offset: 0x14A00]
Bad Block ID @ 0x0006 [Offset: 0x18C00]
Bad Block ID @ 0x0007 [Offset: 0x1CE00]
Bad Block ID @ 0x0008 [Offset: 0x21000]
Bad Block ID @ 0x0009 [Offset: 0x25200]
Bad Block ID @ 0x000A [Offset: 0x29400]
Bad Block ID @ 0x000B [Offset: 0x2D600]
Bad Block ID @ 0x000C [Offset: 0x31800]
Bad Block ID @ 0x000D [Offset: 0x35A00]
Bad Block ID @ 0x000E [Offset: 0x39C00]
Bad Block ID @ 0x000F [Offset: 0x3DE00]
Bad Block ID @ 0x0010 [Offset: 0x42000]
Bad Block ID @ 0x0011 [Offset: 0x46200]
Bad Block ID @ 0x0012 [Offset: 0x4A400]
Bad Block ID @ 0x0013 [Offset: 0x4E600]
Bad Block ID @ 0x0014 [Offset: 0x52800]
Bad Block ID @ 0x0015 [Offset: 0x56A00]
Bad Block ID @ 0x0016 [Offset: 0x5AC00]
Bad Block ID @ 0x0017 [Offset: 0x5EE00]
Bad Block ID @ 0x0018 [Offset: 0x63000]
Bad Block ID @ 0x0019 [Offset: 0x67200]
Bad Block ID @ 0x001A [Offset: 0x6B400]
Bad Block ID @ 0x001B [Offset: 0x6F600]
Bad Block ID @ 0x001C [Offset: 0x73800]
Bad Block ID @ 0x001D [Offset: 0x77A00]
Bad Block ID @ 0x001E [Offset: 0x7BC00]
Bad Block ID @ 0x001F [Offset: 0x7FE00]
Too Many Bad Blocks
Bad Block ID @ 0x0000 [Offset: 0x0]
Bad Block ID @ 0x0001 [Offset: 0x4200]
Bad Block ID @ 0x0002 [Offset: 0x8400]
Bad Block ID @ 0x0003 [Offset: 0xC600]
Bad Block ID @ 0x0004 [Offset: 0x10800]
Bad Block ID @ 0x0005 [Offset: 0x14A00]
Bad Block ID @ 0x0006 [Offset: 0x18C00]
Bad Block ID @ 0x0007 [Offset: 0x1CE00]
Bad Block ID @ 0x0008 [Offset: 0x21000]
Bad Block ID @ 0x0009 [Offset: 0x25200]
Bad Block ID @ 0x000A [Offset: 0x29400]
Bad Block ID @ 0x000B [Offset: 0x2D600]
Bad Block ID @ 0x000C [Offset: 0x31800]
Bad Block ID @ 0x000D [Offset: 0x35A00]
Bad Block ID @ 0x000E [Offset: 0x39C00]
Bad Block ID @ 0x000F [Offset: 0x3DE00]
Bad Block ID @ 0x0010 [Offset: 0x42000]
Bad Block ID @ 0x0011 [Offset: 0x46200]
Bad Block ID @ 0x0012 [Offset: 0x4A400]
Bad Block ID @ 0x0013 [Offset: 0x4E600]
Bad Block ID @ 0x0014 [Offset: 0x52800]
Bad Block ID @ 0x0015 [Offset: 0x56A00]
Bad Block ID @ 0x0016 [Offset: 0x5AC00]
Bad Block ID @ 0x0017 [Offset: 0x5EE00]
Bad Block ID @ 0x0018 [Offset: 0x63000]
Bad Block ID @ 0x0019 [Offset: 0x67200]
Bad Block ID @ 0x001A [Offset: 0x6B400]
Bad Block ID @ 0x001B [Offset: 0x6F600]
Bad Block ID @ 0x001C [Offset: 0x73800]
Bad Block ID @ 0x001D [Offset: 0x77A00]
Bad Block ID @ 0x001E [Offset: 0x7BC00]
Bad Block ID @ 0x001F [Offset: 0x7FE00]
Too Many Bad Blocks
Nands are the same



i did rgh falcon before and it was good with no problem at all but with my jasper 512 gave me a very hard time , so if any one can help me i would be very thankful .
 
Last edited:
stefanounick

stefanounick

VIP Member
Jun 9, 2010
1,178
118
Orbiting Sun
once your nanddump is loaded in JR, click tools-> hex viewer and post a screen shot from that
 
  • Like
Reactions: mhd444
frayed

frayed

DINDU NUFFIN
VIP Member
Dec 22, 2010
3,245
118
A galaxy far far away....
mhd444 said:
hi , i have jasper 512 and i try to read nand using j-runne with nand-x but every time i try this i got this erorr .....
Flash Config: 0x00AA3020
Click to expand...
if you want help you need to follow the TEMPLATE: RGH/JTAG help

15432 said:
I think you have 16mb jasper. Could you provide the reading log?
Click to expand...
Flash Config: 00023010 = 16MB
Flash Config: 008A3020 = 256MB
Flash Config: 00AA3020 = 512MB
 
Last edited:
  • Like
Reactions: mhd444
stefanounick

stefanounick

VIP Member
Jun 9, 2010
1,178
118
Orbiting Sun
mhd444 said:
Flash Config: 0x00AA3020
CB Version: 6751
Reading Nand to C:\Users\mhd\Documents\J-Runner v02 Beta (286) Core Pack\output\nanddump1.bin
Reading Nand
Done!
in 0:17 min:sec

Reading Nand to C:\Users\mhd\Documents\J-Runner v02 Beta (286) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Too Many Bad Blocks
Header is wrong..
Reading Nand
Nand Initialization Finished
Done!
in 0:18 min:sec
Click to expand...
and this is ... ?
 
  • Like
Reactions: mhd444 and frayed
M

mhd444

Junior Member
Dec 28, 2012
20
0
MY Flash Config: 00AA3020 THAT'S MEAN 512 RAM ... RIGHT ?
AND WHEN I READ NAND IN 64 MODE I GOT THIS



Flash Config: 0x00AA3020
CB Version: 6751
Reading Nand to C:\Users\MHD\J-Runner v02 Beta (286) Core Pack\output\nanddump1.bin
Reading Nand
Done!
in 8:42 min:sec

Reading Nand to C:\Users\MHD\J-Runner v02 Beta (286) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Header is wrong..
Reading Nand
Nand Initialization Finished
Done!
in 8:41 min:sec

Comparing...Takes a while on big nands
Nands are the same
Invalid Image
Failed to create ecc image
 
M

mhd444

Junior Member
Dec 28, 2012
20
0
.

---------- Post added at 08:05 ---------- Previous post was at 08:03 ----------

I CANT PAST THE HEX HERE , HOW CAN I ?
 
Last edited:
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
These are the dangers when you don't understand what you're doing.

You should have NEVER written to the console before you got at least 1 confirmed good NAND dump.

Another console bites the dust. J-Runner would have had Jasper 256 or 512 as a selection, but you decided to override this by choosing 16.
 
  • Like
Reactions: mhd444
M

mhd444

Junior Member
Dec 28, 2012
20
0
yea you are right its my fault , i should be more careful .

---------- Post added at 23:51 ---------- Previous post was at 23:46 ----------

but i still wonder what was the wrong at the first time , i mean why i couldn't read my nand good in the beginning i tried 2m ,64m and full dump but all go bad ?
 
M

madhaxer

VIP Member
Sep 27, 2012
879
0
Arkansas USA
Could have been several things, pm'ed you about the console.
 
  • Like
Reactions: mhd444
1

15432

VIP Member
Nov 14, 2010
703
68
Russia
You wrote to 512mb nand the image with wrong spare data so JRunner recognizes it as bad block.
frayed, sorry, I missed this out... But this error usually appears in wrong nand type recognition

EDIT: it seems this message is wrong
 
Last edited:
  • Like
Reactions: mhd444
You must log in or register to reply here.