Error 250 reading block 161

[crispybits]

Hi,
i dumped the nand of my xbox 360 with the following error message:
Error: 250 reading block 161
03FF

Can I ignore this?

My specs:
- Xbox 360 slim, mfr date: 2011-03-04, Trinity, dashboard 2.0.13604.0, cb 9188
- TX nand-x programmer, updated successfully to v.3 firmware with usb to nand-x cable,
Nandrpo 2.0d drivers.
- Windows 7 64bit, nandpro 3.0a, 360 multibuilder 0.7, xnandhealer 0.71
- Used xbox 360 slim quick solder board

Dumped the image with nandpro and the following command: nandpro usb: -r16 nanddump.bin.
When I compare the nand dumps with the fc /b command, there are differences.
Xnand healer tells me under tab nand info: bad blocks 0x161 – 0x3ff.
multibuilder completes building the .ecc image with no errors.

Think the soldering is all right.
Just want to be sure if this error is normal because the cpu key isn’t known, the blocks are really empty or any else reason.
I didn’t write anything to the nand yet and my question is, will this image work?

Thxia
cb

 

[Martin C]

Everyone should be running their image through 360 Flash Dump Tool. It's far better than comparing NANDs etc.

As long as any bad blocks encountered are remapped, you're good to go. This should be in whatever guide you're following.

 

[tingedace]

I'd agree that 360 flash dump tool is a great tool that we couldn't live without. However as far as I can see it will not notify you if the nand is corrupt.

For example, take any perfect NAND image and with a hex editor change any single bit in that image and save the file. Now run it through Xnandhealer and you will be notified of an ecc failure for the block you changed.

If you don't compare NANDs and/or check integrity you could have a corrupt NAND and never know. Granted nothing bad may come of that, but I'd rather know.

Crispybits, you've probably already discovered this by now but xebuild handles the remapping for you (unless you tell it not to) so just build and flash.

Nice name abbreviation too...CB :wink: