Error 250: 23E Bad Block, Trinity Board

[MightyShots]

Hi,

I am posting this just to make sure my nand is ok.

Basically i purchased the nand-x and followed the install instructions from here. I have installed this successfully, i believe as i have made 5 nand dumps and still plays games fine!

However i have made the Nand dumps using JTAG tool selecting Jasper 16mb as my board. 5 dumps in total all with error 250 @ 23E block. The dumps are identical as reported back with JTAG tool. I was just wondering if this is ok and do i need to fix it if so how? Could my TX replacement PCB in my drive(0225) affect the nand dump?

Here are some images to help with your response,

Thanks guys in advance!

 

[mgrover]

check your wires and make sure your soldering is all right

 

[manwithoutname]

If the bad block appears in the same place in all dumps then it is normal. Also check your dumos via nandcompare tool to make sure there are no mismatching.

 

[MightyShots]

If the bad block appears in the same place in all dumps then it is normal. Also check your dumos via nandcompare tool to make sure there are no mismatching.

Thanks for the response guys, ive done 17 dumps in total now and all the same. Always 23E, i have used nad campare in jtag tools and the program on its own which i downloaded from google all say 0 non-mismatches found, all identical. If it was the soldering then surely it would be in random places? Then in jtag tool in the pic it says kv is bad but not sure why. Please help lmao my soldering is good i have done soldering for years just not for nands so a new area for me. Could this be just a bad nand block but how do i repair it? This may be a bad idea but maybe i could forward it to someone to take a look?

Thanks guys

I have just used nand compare v1.4

1024 block(s) in nand image
0 non-matching block(s) found

 

[MightyShots]

Thanks mitch_thepcman i was worried about it im glad you have answered my query. So just wait for the coolrunner now and hopefully some qsb's for the slim nand-x and coolrunner to tidy up the wires etc.

Thanks guys

 

[Martin C]

Could you not have just searched for bad blocks? A new thread for something known for the last 2 years??

Google is your friend, matey

 

[MightyShots]

Could you not have just searched for bad blocks? A new thread for something known for the last 2 years??

Google is your friend, matey

I did and it was saying repair it with bad block remapper and it wouldnt work, also it was saying do something else with freeboot which wont work yet.

Sorry mate but i did look through the forums on here and nothing was directly the same as my situation with a trinity board. Im new to team xecuter forums and on the box it says visit here for support so i did.

 

[Martin C]

I did and it was saying repair it with bad block remapper and it wouldnt work, also it was saying do something else with freeboot which wont work yet.

Sorry mate but i did look through the forums on here and nothing was directly the same as my situation with a trinity board. Im new to team xecuter forums and on the box it says visit here for support so i did.

I wasn't having a stab per-se. I'm just giving you a gentle push in the right direction. You could google 'bad blocks jtag' and you'd see all kinds of entries to read up on. The issue isn't related to the NAND-x, either!

this might help you also:

http://www.free60.org/NAND:Bad_Blocks

I searched google for 'wiki bad blocks xbox' in case you're wondering.

 

[MightyShots]

No sorry i didnt mean it like that, i searched google for 23E bad block but nothing showed up that helped, i didnt search for jtag because i was doing a nand dump.

Again sorry i didnt mean it the way you took it i was explaining. But thank you i know what to search for now

 

[Martin C]

Searching for specific blocks won't really help you. Sounds a little like you're not overly sure on what you're doing anyway.

Have a good read on the Free60 page as although you're not doing a standard JTAG, the read/write will be the same.

 

[WNYConsoles]

Decided to mess around with my NANDX and a Slim since CR's are going to be in my hands very soon. I get 250 reading block 156 however all dumps match.

I used JTAG Tool 16MB Jasper.

Having JTAGGED dozens of consoles before I have found bad and remapped blocks on many consoles and had no problems with them. Just another defect in Microsofts design.

 

[jtag360.nl]

If you need to remap it just you can use programs like jtagtool or nandhealer.

But you can also do it manualy.

Like this if you use nandpro.

nandpro nanddump.bin: -r16 23e.bin 23e 1

nandpro nanddump.bin: -w16 23e.bin 3ff 1

Succes.

 

[Martin C]

Decided to mess around with my NANDX and a Slim since CR's are going to be in my hands very soon. I get 250 reading block 156 however all dumps match.

I used JTAG Tool 16MB Jasper.

Having JTAGGED dozens of consoles before I have found bad and remapped blocks on many consoles and had no problems with them. Just another defect in Microsofts design.

In MS's defence, it's genius.

If during the write process, the programmer detects a verify issue with a sector it marks it as bad and writes it at the end of the NAND (small block). It may have written correctly the second time but why risk it?

Compare it to Sony and it's possible to RSoD a PS3 even when you have a full, correct NOR dump before you start (as I discovered). *That's* why Microsoft do what they do.