Per my original post below, I've updated the NAND (using 360 Multi Builder v0.7), now I'm getting an E79 error. I've tried to rebuild and flash via Xell Reloaded and while flashing it yet again found 2 bad blocks:
! SFCX: Bad block found at 0000029F
block 0x29f seems bad, status 0x00000250
! SFCX: Bad block found at 000002A0
block 0x2a0 seems bad, status 0x0000250
processing block 0x0400 of 0x0400
image written, shut down now!
I then pull the plug for a minute or two and attempt to re-boot, when I reboot I get red light and E79 error.
At this point, I'm not even sure how to re-flash my original NAND as I simply have nand.bin / updflash.bin files and it looks like Xell Reloaded wants a xenon.elf to start the process of flashing.
Jasper 16MB
--------------------------
Original post:
http://team-xecuter.com/forums/showthread.php?t=75280
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.
--------------------
! SFCX: Bad block found at 0000029F
block 0x29f seems bad, status 0x00000250
! SFCX: Bad block found at 000002A0
block 0x2a0 seems bad, status 0x0000250
processing block 0x0400 of 0x0400
image written, shut down now!
I then pull the plug for a minute or two and attempt to re-boot, when I reboot I get red light and E79 error.
At this point, I'm not even sure how to re-flash my original NAND as I simply have nand.bin / updflash.bin files and it looks like Xell Reloaded wants a xenon.elf to start the process of flashing.
Jasper 16MB
--------------------------
Original post:
http://team-xecuter.com/forums/showthread.php?t=75280
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.
--------------------