ANSWERED Bad block. Safe to continue?

[RedFarmer]

Hi!

I know that there are some threads about this but i'm still a bit uncertain.

I'm dumping a Xenon and after 4 dumps it always end up with error 250, bad block at 15F. I'm using JTAG Tool.

I can't run Degraded to remap because it keeps crashing on me when i try to load any of the dumps. I've tried it on both my Win7 and WinXP machine with the same problem.

Would i be safe just continuing and write Xell, get the CPU key, create the Freeboot image and write? I guess it would be worse if the bad block was in the first 50 sectors?

Thanks!

 

[M AzeeM K]

How about you try to open the NAND image in 360 Flash Dump Tool ?

 

[Martin C]

Error 250 is an empty block. It's altogether possible that a block could have 16k of zeroes (or had been zero'd out at some point.

Do what M AzeeM K suggests though and open it in 360 Flash Dump Tool but don't be too surprised if it's not remapped.

 

[RedFarmer]

Thanks guys!

Flash Tool worked great!

It seems to be remapped to 3FF. Am i correct?

To remap in JTAG Tool, can i just do like this?

 

[Martin C]

Yep - you may need to zero out 0x15f after remapping too. Depends on how your console handles it. i.e you may get E71 on bootup even after remapping.

 

[RedFarmer]

Yep - you may need to zero out 0x15f after remapping too. Depends on how your console handles it. i.e you may get E71 on bootup even after remapping.

I see! As the console expects zeroes and not possible junk? If so, how would I go about zeroing the blocks? Hex editor?

Sorry for silly questions.

 

[Martin C]

No worries - better to ask

Since your dump has zeroes at 015f, use NANDPro to get it:

nandpro nand.bin: -r16 badblock.bin 015f 1

open badblock.bin in a hex editor and confirm it's all zeroes. If not, make it all zeroes.

Then, either write to your remapped freeboot NAND or directly to the console:

nandpro usb/lpt/<file>: -w16 badblock.bin 015f

You can wait until after it's been reprogrammed before doing this, so you don't need to go through the lot again.

 

[RedFarmer]

What can i say? Greatest and fastest support you could ever have! I'll check it out. Thanks alot!

 

[Martin C]

No worries - let me know how you get on.

 

[RedFarmer]

I created a remapped "original" image.
I wrote Xell and got key
I created FB from the remapped image
I wrote FB
I tried writing the zeroed 15f bin-block but get the following...

However, the console seems to work. Any comments?

 

[RedFarmer]

Hmmm... I think i got ahead of myself. I seems to get stuck on the bootlogo after the startup animation

 

[Martin C]

Hmmm... I think i got ahead of myself. I seems to get stuck on the bootlogo after the startup animation

Do you have a HDD attached to the console? Try removing it and rebooting.

Failing that, have you tried erasing the NAND and writing back to it?

Sent from my iPhone using Tapatalk.

 

[RedFarmer]

No HDD attached. It's still out of its case.

Actually, it doesn't freeze completely. If i sync a controller and press the XBox-button i get the mini-blades. If i choose XBox Dashboard i get a black screen. However, I can still press the XBox-button again to get the blades back.

I tried erasing the NAND but get an error at 15f, and also an error when writing FB back. =/

It seems i can't touch 15f whatever i do.

 

[Martin C]

ok - so instead of trying to erase the block, just copy 015f of the freeboot image to 03ff. Don't worry about trying to erase the bad block as it can't be read anyway:

nandpro freeboot.bin: -r16 remap.bin 015f 1

nandpro usb: -w16 remap.bin 03ff

then try again.

 

[RedFarmer]

Oh man! Ofcourse! Now i get the picture!

You're a genius! Now it works!

Thanks a million!

 

[Martin C]

No worries, glad you got it sorted

Happy gaming!


Sent from my iPhone using Tapatalk.

 

[M AzeeM K]

Glad you got it sorted, all credit to Martin C

Since everything is sorted......

[Thread Closed]