RGH - bad blocks and E71

[kl1k]

Just installed a Matrix Glitcher v2 - I used nandpro to dump my nand 5 times. Each time it found a bad block at B2 (204) and another one at 2A2 (250)

From reading a few posts it said I shouldnt worry as the bad block is below 50. So I create the ecc file - write it to the nand, gt the cpu key and create the nandflash.bin (Using 360 multi  builder 0.82)

Put rawflash v4 and the bin file on USB - boot up the xbox and it flashed the bin file. It gives my 2 warnings.

block 0xb2 seems bad (204)
block 0x2a2 seems bad (250)

This seems right as it matches the above. However now on reboot the xbox dash boots and right after I see the logo I get a E71. I can still boot into xell.

Any ideas? Could it be the bad blocks - I read the multi build remaps the bad blocks?

[galo911]

Yes it should, read the log it will say that blocks were remapped. Open your original nand on flash tool. There as well you should be able to see the remaps

[kl1k]

The original image and the new images both show this:

Note: Bad block ID 0x02A2 [ Offset: 0x00ADC400 ] -> Block ID 0x2A2 found @ 0x3FF [ Offset: 0x0107bE00]

[janvkem]

Seems the B2 block is not recognized as bad block. Null it out in the new image and remap to 3FE and you should be fine.

edit: Remap before nulling out of course 

[kl1k]

Cool - i'll give it a shot and let you know what happens.

[kl1k]

I'v already disconnected my nandflasher from my xbox. If there someway I can change the nandflash.bin file to include the bad block rewrites, that way I can put it on a usb stick and flash with rawflash on xell?

[janvkem]

You can use nandpro for remapping. See cory1492's post for more detailed info: http://www.xboxhacker.org/index.php?topic=17411.msg131235#msg131235

[cory1492]

I'v already disconnected my nandflasher from my xbox. If there someway I can change the nandflash.bin file to include the bad block rewrites, that way I can put it on a usb stick and flash with rawflash on xell?

rawflash isn't going to touch either of these blocks, no matter what you do to the image you feed it. Technically it's the safest way to treat such blocks at a raw level, even though it occasionally produces results like yours. Hence why it's called rawflash, and not doeverythingforyouflash  

block 0xb2 seems bad (204)
block 0x2a2 seems bad (250)

the problem is, 0xb2 is likely not bad (yet) and just has a single bit error which is correctable by the controller. In your dump you are getting the corrected data, and because of that the block doesn't seem to have any issues when you examine it with tools like flash tool because the bit error doesn't exist in the dumped data.

Block 0xb2 likely is already labeled by LBA as 0xb2 and unless you can overwrite it with 0x0 data after you remap it, the system will keep trying to use it as 0xb2 even though it has old data in it resulting in essentially a corrupt file in the flash - in this case, dash.xex which produces E71.

Here are two variations of rawflash, not meant for normal use but only to overcome problems like this... remap your block with the ecc error to the end of NAND as mentioned above, zerofill the origin block, and try the no_ecc_care one first. Once it works, do not use these "no care" versions again, they won't be needed unless a new issue comes up later.

Another option to manually remapping, is to simply get out a hex editor and write 00 in the byte at (0xb2*0x4200)+0x205 (=0x2DE605, it should be 0xFF with 00 on each side of it) in nanddump.bin that you are feeding to your image builder. This effectively marks the block as bad, and the builder should remap it for you.

This version simply ignores ecc errors, and should be able to correct your issue with 0xb2 if you remap it as described:
rawflash_v4_no_ecc_care.zip @ http://www.mediafire.com/?1b81mqwraoscgrl

This version just puts onscreen message when ecc error or bad block error are detected, but otherwise attempts to read/write the block anyway:
rawflash_v4_no_badb_care.zip @ http://www.mediafire.com/?twsmlgdpmre8su4

Now the lecture on why you shouldn't use these normally: when you tamper with blocks that are marked as bad, you may have no way of marking them as bad again. Good luck!

[kl1k]

Ok - this is weird...its working. Mostly my fault

I flashed the original bin back and rebooted the xbox - it gave me the screen where the dash update failed. I should have checked this before I started - the guy that gave it to me obviously tried to update to 13599 off a backup and after reboot it gets stuck. So I fix the failed dash, upgrade to the next version, redo the nand and flash and its all working again.

Weird that the failed dash would give me so much crap! Good to know for next time - power on the xbox first before you open it!

Interesting enough when I dumped the nand again after the dash upgrade 0xB2 no longer reports as being bad - only 0x2A2 reporting a 250.