Error 210

[The_Pretender]

Hello,

First of all, i must say i'm a newbie....
I tried to Jtag my box and started to solder the Nand-X items.
I have read the nand many times, and always get the same error messages:

Error 250 reading block 3ED8
Error 210 reading block 3ED9
Error 210 reading block 3EDA
Error 210 reading block 3EDB
Error 210 reading block 3EDC
Error 210 reading block 3EDD
Error 210 reading block 3EDE
Error 210 reading block 3EDF

It's a Jasper with 256MB Nand
D:6717 K:6717

What is that error 210?
And what can i do to fix the problem?

 

[rocket8080]

If your getting a the same error in every read at the same block then its probably just bad blocks in the nand, open you nand image in degraded to confirm this. If so then just remap the bad blocks at your good to go.

 

[The_Pretender]

Okay,
Thanks for the answer, but for me to understand....
What do you mean with:
Open you nand image in degraded to confirm this.
If so then just remap the bad blocks at your good to go.

Sorry my englisch is not so good, can you explain step by step what i have to do?

I have already compare the nand images in the Jtag tool and there are 0 non-matching block(s) found......

 

[rocket8080]

Follow the steps below

• Grab Degraded 1.1b from Xbins or somewhere like megaupload .
• Run Degraded and click settings, enter key you found using google "Degraded 1BL key" should pop right up.
• After you set the key click Valid next to it and set the File System Start to 39. Click ok.
• Open orig.bin
• If you get, cannot read file , you must edit the orig.bin file. Make a copy of it, origcopy.bin and open it up in your hex editor. At offset 0x0012 , you will see 2004 - 2007 Microsoft Corporation...
• Change it to : 2004 - 2005 Microsoft Corporation and it will open with Degraded :

 

[The_Pretender]

Thanks for the quick reply!

I followed your steps....but get stuck at the point when i open the orig bin....
The degraded say's: Bad File Length
Very strange!

(whith the orig.bin you mean the one i've read with the jtag tool isn't it?)
In my case it's than the nand.bin

 

[rocket8080]

yes its your nand.bin, and try placing it on your desktop and loading it from there.

 

[The_Pretender]

Okay....

I understand....stil got the Bad File Length problem...

 

[manwithoutname]

You can't open any HDMI console NAND file in degrader without editing it in a hex editor first as degrader was written to work with xenon boards only.

Load a copy of the original NAND dump into a hex editor and change the bit that says (2004-2007) to (2004-2005) then it should load into degrader. You always use 360 flash tools instead.

 

[The_Pretender]

Strange...
I change the bit like you say2004-2008 to 2004-2005......still keep the bad file length problem!
What if i go further without repair?? Because the errors are at the end of the nand reading and XBR uses the first 1000 blocks isn't it?
Did i get in trouble then??

 

[manwithoutname]

XBR? Why do you want to use XBR when freeboot is there? With XBR you'll end up with dash 8955 which isn't compatible with all latest games, and also it has less features than freboot as well as less stable.

First thing, make sure you got 3 dumps of your NAND and compare them in Nand Compare tool to ensure they are identical and there are no mismatching blocks.

Next try opening one those 3 dumps in 360 flash tool, you should be able to see all the info about dash & kernel on the left side.

I still can't understand why you're unable to view it in degraded but if you can upload a copy of your NAND dump to some place like mediafire I could have a look at it for you!

 

[The_Pretender]

I got 3 identical dumps from the nand. (even more)
And when i opening in the 360 flash tool i can see al the info about te dash and the kernel on the left and on the right i can read only bad key/kv......
Can i then proceed with the next step? (write Xell?)
Here you can get my dump: http://www.mediafire.com/file/g8c1q31vy8blopx/Nand.rar

 

[manwithoutname]

If all 3 dumps are identical then you're good to go. There doesn't seem to be any bad blocks as none were showing in 360 flash tool.

If you have done the JTAG connection then proceed and write xell to obtain your CPU key. Are you using the standard jtag connections or the alternate points?

 

[The_Pretender]

Thanks man.....

Yep....ussing the standard jtag connections

 

[The_Pretender]

Okay, next problem.....
Write the Xell, and when i then start the box i've got only a black screen and only the green light from the powerbuton goes on....
After remove the Xcell (write back the orig nand) i got at the end from the write proces a error:202 programming block 3ED8
But that was at the nand read a error 250.
But the xbox startet ater that normal....
And yes i didn't use the HDMI cable....only the normal TV cable....

 

[manwithoutname]

Which version of Jtag tool are you using? The older versions has a bug and does not support consoles with large NAND's ... Also now I relaise that Degrader doesn't support larger block NAND's so it doesn't matter if you made the changes we showed you, it still won't load into degrader.

My suspicion now is that the bad blocks are still there, except we just can't see them. Can you do a dump of your original NAND again and take a picture with the command prompt with all the errors that show during the dump?

Technically speaking, you only need the 1st 66mb of your NAND to create a working freeboot. But lets work out on xell first.

 

[The_Pretender]

Okay manwithoutname.

Thank you that you helping me for finding a solution!
I solved the problem!
There was a switsch on the smal jtag pcb that was off.
After i switched it ones i've got the screen with the cpu key!
After that i instal freeboot!
Problem solved!

Thanks you

 

[manwithoutname]

Good for you .. Now enjoy ..