Bad Blocks, Minidash Not Working

[null0pointer]

I have a Jasper 16mb jtag system that I've flashed to various versions of the dashboard without issues. During my last update to 13604 I saw that I had a few bad blocks during the flash. After the flash I noticed several odd things, so I decided that I would dump the nand again and try and remap and reflash. Note: all reading/writing of the nand was using flash360.

The dump of nand in Jtag flash dump tool yields the following:
Note: Bad Block ID 0x029F [Offset: 0x00ACFE00]
Note: Bad Block ID 0x02A0 [Offset: 0x00AD4000]

-> Block ID 0x02A0 found @ 0x3E0 [Offset: 0x00FFC000]
----------------
After unmapping the bad block, creating the freeboot image, and finally mapping the nand, it "appeared" to be correct. It did list the "Note: Bad Block IDs", but did not list out individual Block ID. I went ahead and added to usb drive and used Xellous to flash (putting usb drive in slot and "boot" using eject button).

This doesn't appear to have done anything as I still see "Bad Block ID xxxx" when I took a new backup of my nand using flash360.

I should also note that my Xbox guide button (mini dash) no longer works...obviously the button itself is fine (as I can power ON), but I'm assuming because of the bad flash, it's disabled it somehow. I verified in dashlaunch the minixbe is enabled. I also cannot hold it down to power the system off.

Also, Degraded 1.1 just crashes when it's opening the dump.

Any ideas would be greatly appreciated.

 

[null0pointer]

Nothing? I've even tried to go back to an older NAND in hopes of resolving this. The old NAND loads fine, but mini-guide/blade still doesn't work and it's still showing 2 bad blocks in NAND Flasher. I'm at a loss and not sure what the next move should be.

 

[Martin C]

"After unmapping the bad block, creating the freeboot image, and finally mapping the nand, it "appeared" to be correct."

BIG mistake. Don't mess about with your original NAND. You don't need to be manually mapping and remapping anythnig. I wish people would stop doing this as it's carried out automatically by tools like Multi_builder. More often than not, people are doing so without any idea what they're doing.

Write the original NAND and confirm it works ok . We'll then go from there.

 

[null0pointer]

Finally able to come back to this...

I found and wrote the original NAND. It does appear that the mini-guide is back and functional.

As a quick test, I ran Flash360 to take another backup of the NAND, and again, it listed two bad blocks. I then tried NAND Flasher 360 (XBox version) to grab another backup and in the bottom corner it says "Bad Blocks: 2".

How should I proceed? You advised against re-mapping bad blocks.

 

[Martin C]

Yes, you don't need to manually re-map.

Just run it through multi_builder 0.7 and it will do all the remapping for you.

 

[null0pointer]

So, I downloaded Multi_Builder 0.7. Put my original NAND (renamed to nanddump.bin) and cpukey.txt in my360 folder. I ran run.exe, selecting Jasper 16MB, JTAG hack image type, tried both Dashlaunch with default and no Dashlaunch.

I then put the nandflash.bin and xenon.elf on root of USB stick... powered on Xbox using eject button and waited a while (can't see output, using HDMI). Then powered off and pulled the plug for a minute...powered on and am still on old dash. I then tried renaming nandflash.bin to updflash.bin and did the same thing as above (power on via eject, pull plug, etc). This yielded the same results, old dashboard.

As an FYI, I'm using my ORIGINAL "good" NAND dump, that was made pre-kinect. I believe the dash is 6199

What else am I missing?

 

[Martin C]

"I then put the nandflash.bin and xenon.elf on root of USB stick... powered on Xbox using eject button and waited a while (can't see output, using HDMI)"

You can't do anything blind. You have to look at the screen to make sure it's even picked up the nandflash.bin file.

No point in carrying on without it TBH.