RGH Corona 4GB with 4GB R/W kit - BAD BLOCK

Craps

Full Member
Dec 1, 2011
31
0
Earth
Hi

I get bad block when i read out NAND.

Code:
Checking Files
Finished Checking Files
D:\
Reading from D:\ to C:\X360\jtag\J-Runner\output\nanddump1.bin
Done!
in 0:04 min:sec
D:\
Reading from D:\ to C:\X360\jtag\J-Runner\output\nanddump2.bin
Done!
in 0:04 min:sec
Comparing...
Initializing Nand..
Too Many Bad Blocks
Header is wrong..
It's already unecc'd
Nand Initialization Finished
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 have try different USB reader and its the same.

I have try to make my own R/W reader, it reads fine but JR cant check it for badblock, and it wont write ECC to nand, so deside to buy the xecuter R/W thing but it gives me to many bad blocks.

I have read other treats about same problem but i dit not find a solution to this problem, hope some one have the magic fix for this problem.

I have only solder the R/W kit to the MB, i have check the solder point, i have bin soldering for over 15 years and i dont think its the soldering.
 
Last edited:

stefanounick

VIP Member
Jun 9, 2010
1,178
118
Orbiting Sun
id rather pay attention to header is wrong message rather than the "bad blocks"
did you try to open the nand in a hex editor? (theres one in tools menu)
 
  • Like
Reactions: Craps

Craps

Full Member
Dec 1, 2011
31
0
Earth
No have only try to get a good dump.

It all so fail to create ECC file.

But the dump i made with my own R/W i can make ECC file.

If i open the dump in hex from xecuter R/W it says in top

Code:
RGH2 2stage CB img, CB=13121
The dump i made with my own R/W it says Microsoft.
 

Craps

Full Member
Dec 1, 2011
31
0
Earth
To me it looks like it have write some of the ECC file to the NAND even that it faild with my own R/W, and now when i try to read it with xecuter R/W it gives me Too Many Bad Blocks and Header is wrong..


What dos this mean ?

It's already unecc'd


If i turn the reader to XBOX and start it up its running ok.
 
Last edited:

Craps

Full Member
Dec 1, 2011
31
0
Earth
ok i took the chance and flash back the first full dump i made with my own R/W

Now i can read the nand with no errors and bad blocks, i just dump 48mb files and create ECC and flash back to NAND

Code:
Checking Files
Finished Checking Files
Initializing Nand..
Nand Initialization Finished
Writing to E:\ from C:\X360\jtag\J-Runner\output\første\dump1.bin
Done!
in 10:59:205 min:sec:ms
E:\
Reading from E:\ to C:\X360\jtag\J-Runner\output\nanddump1.bin
Done!
in 0:04 min:sec
E:\
Reading from E:\ to C:\X360\jtag\J-Runner\output\nanddump2.bin
Done!
in 0:04 min:sec
Initializing Nand..
Comparing...
Nand Initialization Finished
Can't check for bad blocks. No Spare data. Possibly Corona 4GB
Can't check for bad blocks. No Spare data. Possibly Corona 4GB
Nands are the same
* unpacking flash image, ....
Spare data NOT found
* found decrypted CD
* found XeLL binary, must be linked to 0x1c000000
 * we found the following parts: 
SMC: 2.5
CB_A: 13121
CB_B: 13121
CD (image): 12905
CD (decrypted): 9452
 * checking required versions...
ok
 * patching SMC...
Patching Corona version 2.5 SMC at offset 0x13B4
 * Replacing CD...
 * patching CB_B...
patchset for 13121 found, 5 patch(es)
 * constructing new image...
 * base size: 70000
 * No separate recovery Xell available!
 * Flash Layout:
0x0..0x1FF (0x200 bytes) Header
0x200..0x7FF (0x600 bytes) Padding
0x800..0x3FFF (0x3800 bytes) SMC
0x4000..0x7FFF (0x4000 bytes) Keyvault
0x8000..0x9AEF (0x1AF0 bytes) CB_A 13121
0x9AF0..0x1162F (0x7B40 bytes) CB_B 13121
0x11630..0x1762F (0x6000 bytes) CD 9452
0x17630..0xBFFFF (0xA89D0 bytes) Padding
0xC0000..0xFFFFF (0x40000 bytes) Xell (backup)
0x100000..0x13FFFF (0x40000 bytes) Xell (main)
NOT adding Spare Data
Done!
------------- Written into output\image_00000000.ecc

Writing to E:\ from C:\X360\jtag\J-Runner\output\image_00000000.ecc
Done!
in 0:00:247 min:sec:ms
So now ill try to get it to glich on this.
 
  • Like
Reactions: stefanounick

Craps

Full Member
Dec 1, 2011
31
0
Earth
Yes it is working :-D

Now i only need to tweek glitch time. (its about 10 Glitch atm.)

Thx for pointing me in the right direction :-D
 

frostbyt

BANNED
Sep 18, 2011
129
0
Your header was wrong most likely because you flashed the .ecc file with the homemade programmer...So now that you were trying to read it with the original tx programmer/reader you were getting header error..This shows up when the nand only has ecc written to it, never seen this error otherwise.

Glad you got it sorted, the reader works great and is another superb product by tx :)