Bad Block when taking a dump

Hi All,
I have been jtagging a xenon and I keep getting a read error (error 280) on block 3BB, its the same block every time. I have done this 6 times with the same error on the same block. When I compare the nand dumps, each of them has either 16 or 17 difference, do you think this is due to this bad block?

I have had this issue with another xbox once before when I was repairing a E79 issue (ended up fixed it by jtagging ). I ended up just retriving kv & config direct via LTP and not the full nand, writing xbr and then injecting kv. Thing with this xbox was I had nothing to lose, it was already broke when I got it.

 

LMFAO at thread title, thought it was gonna be about constipation

 

Check your dump with degraded to get it to work you have to click settings and enter the 1BL key (same for every xbox google it) and click the valid box. If your blocks have been remapped then you have to move them to the bad blocks with nandpro.

 

Nice one, understood apart from this bit

Can you clarify how I would do this

 

If you use degraded to check your dump it will tell you where the bad blocks are remapped too.

 

http://nzbmatrix.com/forums.php?action=viewtopic&topicid=22401&page=1

Scroll down a little bit and you'll see a quick how-to for remapping bad blocks.

 

Can you do a quote? The site is denied for non-members.

 

I keep forgetting about the forums being members-only. Sorry about that.



Bad Blocks in the nand

If Degraded shows you some bad blocks, you will have to move the blocks from your xbr.bin to where they are remapped.


You may have good luck with Bad Block Remapper. If not, then you can move the blocks manually.

If you want to do it manually, you have to do this:

* Take the picture above as example.
* It says: Note : Block 0x2CE found at 0x3F8
* This is where the bad block 0x2CE was remapped.
* nandpro xbr.bin: -r16 block2ce.bin 2ce 1 (Reads block 0x02CE and saves as block2ce.bin)
* nandpro xbr.bin: -w16 block2ce.bin 3f8 1 (Write block2ce.bin to 0x3f8 where block is remapped)
* You will have to do this for each block.
* Here is the "formula":
* nandpro xbr.bin -r16 blockXXX.bin XXX 1 (Where XXX is the bad block number)
* nandpro xbr.bin -w16 blockXXX.bin YYY 1 (Where YYY is the address where block is found in degraded)

 

No problem at all. Thanks a lot for the info.

 

this works great i just finished fixing my 360

 

+1 this fixed my problem. Thanks for all your help guys!

 

That thread title is legendary!

 

lmfao

 

I didn't even notice this piccy, I thought it was an advertisement. I do love the term, "taking a dump", I'm so childish sometimes.