Error: 250

[Suicyde]

Afternoon all -

I'm pretty amateur @ JTAG - but I've managed to get hold of a 512MB Jasper - so I'm just starting the process.

Using the NAND-X obviously - dumping the NAND, and on all 3 I get:

Error 250: reading block 5138
Error 250: reading block 6488
Error 250: reading block 7F60

Now, I was going to go ahead and write Xell - but last thing I want to do is goose this rarity.

Do we think these errors are normal, and that I'm safe to continue with writing Xell or Xellous?

Either way, I'm a novice at any problems with regard to JTAG - fine to do it if I don't get any errors!

Thanks in advance -

 

[rdubbs007]

Xell or Xellous only writes the first few blocks of the nand it looks like those errors are later on in the nand. A few errors are fine anyways, usually with the BB xboxes there are more chances to get bad blocks. Writing Xell or Xellous will be fine

 

[Suicyde]

Thanks Dubbs - I had read that it was only the early blocks where Xell(ous) went - so that's cool.

Only thing I'm a bit worried about is, I had a Jasper, 256MB I think, that when I tried to write back too had Error Programming blocks...this was on the original NAND I was trying to write back because Xell didn't boot.

Any insight on this? I should've added that in the first post!

 

[Martin C]

You only need to dump the first 70MB of a 256/512MB NAND (from memory). The areas you're getting error 250 (empty block) is because there is no data in there.

try nandpro usb: -r70 orig.bin instead and make sure this is clean.

 

[Suicyde]

Dubbs & Martin - thanks for the help - both Jaspers I did that day worked fine. Appreciated.

 

[Martin C]

Appreciate you coming back to tell us

I'll close the thread as fixed.

 

[Martin C]

Just for clarity:

Certain tools don't accept a 70MB image of a big block nand, only 64 (1000 blocks).

Therefore:

nandpro usb: -r256 orig.bin 0 1000

or

nandpro usb: -r512 orig.bin 0 1000