|
. . I have a regular cygnos v2 jtaged xbox. I updated the dash to a later one right after xgd3 was official. By that I mean I'm not sure what version, but it looks like the latest (latest as of 05.30.2012...419'ish). It was working fine, but then I played a retail game.
I threw in a retail xgd3 game (COD MW3) and I never updated the dvdrom for xgd3, so it immediately blinked out. However, I thought it was just the bank that had something else on it that wouldn't boot normally anyways, so I switched over to bank 2 (Cygnos bank) and tried again, same thing. That is when it came to me that it was a xgd3 game and I never updated the dvdrom firmware to handle that.
After I took the game out, I went on to another xbox and started playing. However, when I got back to that one, it gave me 3 red rings on both banks over and over. I don't have the cpu key in a place I can find, I just used the latest program to read it from Xell directly into the program and went on. I have it, but I just won't find it (it's been over 3 years since I wrote it down on something I would call "paper").
So, are these 3 red rings just uncanny timing for the system to finally bomb out or did the xgd3 game cause this? I flashed back the original nand image that came with the xbox with the same result. But it's so old I'm not sure if party chat on xbox live was even around (the orginal nand image I know is the blade style, as most were for jtag'ing).
My last ditch effort would/could be to remove the cygnos and try vanilla jtag.
BTW I removed the resistor to the fuse when I installed the cygnos.
BTW again, why do I need the cpu key for these lateast programs? I don't remember ever needing it for XBR (which was what was on there prior to this update). . .
This post has been edited by Julets: May 31 2012, 02:31 AM
|