Hi Guys
So I've done a few jtags so assume that I at least half know what I'm doing!
Had a jtagged Xenon all working fine a few days ago, now it has thrown an E79 error. So stage one, checked the hard drive and it is ok, removed the hard drive and tried booting, still E79. Changed the video cable to make sure it wasn't that , still E79.
Ok, stage two. Opened the console up and checked continuity on all jtag points, everything as it should be, soldering all good.
Stage three. Dumped nand and compared it to the freeboot_13599 nand that was flashed to it when it was all working in the first place. Several mismatches. I assume this would be normal as after flashing the nand I went on to update the console with MS 13599 update to get avatar and kinect functionality working? Re-flashed the known good freeboot_13599 nand back onto the console and powered up. Just black screen, no ring of light spin on boot up, no error messages.
Stage four. Flashed stock nand back to console and powered up. Everything good and console boots back to orignal dash. So re-wrote just Xell and powered up, E79. Re-wrote Xell and FB, black screen again.
When I first dumped this console's nand three times I had one bad block everytime, block 250 @ 2C9. As it was the same block everytime across the three dumps, and that it was way past the boot sector blocks, I continued without re-mapping this one block so when writing the nand I get the "Error 202 programming block 2C9" message. However I knew it was going to say that and like I said earlier the console was running fine for a couple of days after the FB flash.
So I thought I would re-map this problem block as I can't see what else it could be now, it is a first for me and I'm not sure what I'm doing tbh. I used Coolshrimp's 'Remap Bad Blocks' facility, selected a good copy of my nand, entered "250" into 'Bad Block' field and "2c9" into 'Location' field. Clicked 'Add' and then clicked the 'ReMap' button. When writing new re-mapped nand to console I'm still getting the error programming at block 2C9. Opened up my nand in XNandHealer and checked it, it also says still a bad block at 2C9:
I messed about with XNandHealer's repair facility and flashed a supposedly fixed image to the console. Booted up to E71 - there's a first! Yet another dashboard related error I believe.
I've now got a copy of NandCompare-v1.2 and I'm reconstructing using the three good nand dumps but it says that they are not matching (due to this 2C9 block). I always do three dumps and I always nand compare them, if the differences are the known bad block then that shows that my three nand dumps do all match doesn't it?
Anyway I'm off to try about the 10th flash now, any help would be greatly appreciated.
Cheers
Mark
So I've done a few jtags so assume that I at least half know what I'm doing!
Had a jtagged Xenon all working fine a few days ago, now it has thrown an E79 error. So stage one, checked the hard drive and it is ok, removed the hard drive and tried booting, still E79. Changed the video cable to make sure it wasn't that , still E79.
Ok, stage two. Opened the console up and checked continuity on all jtag points, everything as it should be, soldering all good.
Stage three. Dumped nand and compared it to the freeboot_13599 nand that was flashed to it when it was all working in the first place. Several mismatches. I assume this would be normal as after flashing the nand I went on to update the console with MS 13599 update to get avatar and kinect functionality working? Re-flashed the known good freeboot_13599 nand back onto the console and powered up. Just black screen, no ring of light spin on boot up, no error messages.
Stage four. Flashed stock nand back to console and powered up. Everything good and console boots back to orignal dash. So re-wrote just Xell and powered up, E79. Re-wrote Xell and FB, black screen again.
When I first dumped this console's nand three times I had one bad block everytime, block 250 @ 2C9. As it was the same block everytime across the three dumps, and that it was way past the boot sector blocks, I continued without re-mapping this one block so when writing the nand I get the "Error 202 programming block 2C9" message. However I knew it was going to say that and like I said earlier the console was running fine for a couple of days after the FB flash.
So I thought I would re-map this problem block as I can't see what else it could be now, it is a first for me and I'm not sure what I'm doing tbh. I used Coolshrimp's 'Remap Bad Blocks' facility, selected a good copy of my nand, entered "250" into 'Bad Block' field and "2c9" into 'Location' field. Clicked 'Add' and then clicked the 'ReMap' button. When writing new re-mapped nand to console I'm still getting the error programming at block 2C9. Opened up my nand in XNandHealer and checked it, it also says still a bad block at 2C9:
I messed about with XNandHealer's repair facility and flashed a supposedly fixed image to the console. Booted up to E71 - there's a first! Yet another dashboard related error I believe.
I've now got a copy of NandCompare-v1.2 and I'm reconstructing using the three good nand dumps but it says that they are not matching (due to this 2C9 block). I always do three dumps and I always nand compare them, if the differences are the known bad block then that shows that my three nand dumps do all match doesn't it?
Anyway I'm off to try about the 10th flash now, any help would be greatly appreciated.
Cheers
Mark
Last edited:
