- Joined
- Apr 21, 2008
- Messages
- 5,716
- Trophies
- 1
- Age
- 35
- Location
- London, UK
- Website
- metalix.deviantart.com
- XP
- 1,904
- Country
It's 1am and google searches just aren't helping me. Too many similar problems but with different symptoms/causes/fixes.
I got a RRoD 360 from a friend of a friend a few hours ago. Did the X-Clamp fix, and it worked fine. Didn't even need reheating, but I did it anyway. Fans pointed at CPU, 10 minutes later GPU overheats, turned off, removed the DVD drive, let the whole thing cool down, then put it back together. Still worked fine.
To test its stability, I decided to play the game provided, Ninja Gaiden 2. After a while, fans went crazy then it overheated. E-code tells me CPU at fault, although when I checked, I realised I hadn't put the fans back in properly (silly mistake, but easily fixed). When it overheated though, it immediately ejected the disk. I pulled the plug, let it cool down, pushed the tray back in, then turned it back on. Fans normal, working normal. Then I noticed the middle green light flashing at me and realized the disk tray was "opening". Tried using the controller to make it close, it switched to "closing". No difference. Tried manually pulling it all the way out and trying again, no movement. Pushing it in didn't help either. I did notice that I could make it switch between "opening" and "closing" just by pushing it past a certain point, but it doesn't help.
Next step, I tried plugging it into the connectivity kit for my comp to make it open/close. No help. Tinkering around shows that when it's half open, pressing eject will create a slight buzzing sound but no movement. Entirely open and nothing will happen. Entirely closed, buzzing sound again. I tried opening it up to see if anything looks obviously wrong. Belt intact, looks strong still. Bit of dust but nothing extreme. Tried pushing the white lever thing to "close" it completely, with the thing moving in to hold the disk (as if for reading) and got slightly different results. Pressing eject makes the laser move slightly. Pressing it again makes it blink red twice, but there's no disk movement.
Final step, I tried looking at it through JungleFlasher with it half open. It already had iX1.61 on it (it's a Samsung) so I just clicked intro and it showed me the usual, including "Parallel flash with Status 0x70". Clicked Read and it showed me iX1.61 as expected with the key. EDIT: As an extra step, I tried accessing it through windows. It detects it and shows no problems, but it won't respond after being told to eject. Didn't think it would help, but there was always a chance.
I don't know what I can do from here. General impression I get from google is that its a drive failure and I should "send it to M$ and have them replace it", although that doesn't sound feasible with a 2 year old 360 that's been X-Clamp fixed and flashed. I don't want to accept that it could fail simply by ejecting a disk upon overheating and having the tray pushed back in whilst it was off. To this end, any advice anyone could give?
EDIT: One extra detail that doesn't affect anything: It's got a dashboard version of 74xx, so it's JTAGgable. It's a shame that the drive is failing on it - I'd love to take a shot at running homebrew on it
I got a RRoD 360 from a friend of a friend a few hours ago. Did the X-Clamp fix, and it worked fine. Didn't even need reheating, but I did it anyway. Fans pointed at CPU, 10 minutes later GPU overheats, turned off, removed the DVD drive, let the whole thing cool down, then put it back together. Still worked fine.
To test its stability, I decided to play the game provided, Ninja Gaiden 2. After a while, fans went crazy then it overheated. E-code tells me CPU at fault, although when I checked, I realised I hadn't put the fans back in properly (silly mistake, but easily fixed). When it overheated though, it immediately ejected the disk. I pulled the plug, let it cool down, pushed the tray back in, then turned it back on. Fans normal, working normal. Then I noticed the middle green light flashing at me and realized the disk tray was "opening". Tried using the controller to make it close, it switched to "closing". No difference. Tried manually pulling it all the way out and trying again, no movement. Pushing it in didn't help either. I did notice that I could make it switch between "opening" and "closing" just by pushing it past a certain point, but it doesn't help.
Next step, I tried plugging it into the connectivity kit for my comp to make it open/close. No help. Tinkering around shows that when it's half open, pressing eject will create a slight buzzing sound but no movement. Entirely open and nothing will happen. Entirely closed, buzzing sound again. I tried opening it up to see if anything looks obviously wrong. Belt intact, looks strong still. Bit of dust but nothing extreme. Tried pushing the white lever thing to "close" it completely, with the thing moving in to hold the disk (as if for reading) and got slightly different results. Pressing eject makes the laser move slightly. Pressing it again makes it blink red twice, but there's no disk movement.
Final step, I tried looking at it through JungleFlasher with it half open. It already had iX1.61 on it (it's a Samsung) so I just clicked intro and it showed me the usual, including "Parallel flash with Status 0x70". Clicked Read and it showed me iX1.61 as expected with the key. EDIT: As an extra step, I tried accessing it through windows. It detects it and shows no problems, but it won't respond after being told to eject. Didn't think it would help, but there was always a chance.
I don't know what I can do from here. General impression I get from google is that its a drive failure and I should "send it to M$ and have them replace it", although that doesn't sound feasible with a 2 year old 360 that's been X-Clamp fixed and flashed. I don't want to accept that it could fail simply by ejecting a disk upon overheating and having the tray pushed back in whilst it was off. To this end, any advice anyone could give?
EDIT: One extra detail that doesn't affect anything: It's got a dashboard version of 74xx, so it's JTAGgable. It's a shame that the drive is failing on it - I'd love to take a shot at running homebrew on it