Hello, I decided to just make a new topic on this error as the other topics titles were misleading. This thread is ONLY to discuss this particular error. There are variations on the error code by a digit depending on if you are connected by ethernet or wireless adapter.
My original story:
QUOTE((>Stormy<))
Here is my story.
Got Xbox in Jan, died in Sept. Sent it for repairs. Bought another one for while it was away.
Got repaired Xbox back yesterday. Set it up and everything worked fine. Tried to connect to Live and got error.
W:0000-000B
X:0000-F001
Y:00C2-03E0
Z:0000-0000
Error comes at the XboxLive section after passing all previous connection parts.
So I plugged same connection into my newer Xbox and could connect fine, not a network issue at all.
Called up MS last night, they have definitely just switched their call center to India. It is a nightmare dealing with them now. Just a warning. I spent two hours on the phone going through all normal troubleshooting tests.
In the end I would recommend against going along with these tests if you have a similar error as it is a huge waste of time (and they are just reading off a screen).
They have no idea what this code means so eventually they will ask if they can put you on hold to contact a supervisor. Do not let them do this as no one will ever answer requiring you to call back again and start over.
Similarly the reference numbers they give you about your call don't work for anything, anyone you are transferred to will have no idea who you are or what the problem is and you will have to re-explain and they will try to do the same troubleshooting.
I recommend simply stating that the xbox does not work and that you would like to send it to them for them to troubleshoot and repair if necessary. This seems to work. They will then transfer you to hardware repairs.
Alternatively I would suggest not going through the Live section of the 18004MYXBOX, just go straight to repairs.
I had to hang up last night as it was 1am and was getting nowhere with the support line. I called back this morning, went straight to repairs, explained that I had received a repaired Xbox that would not connect to Live, had attempted lengthy troubleshooting with no solution, had another Xbox that used the same connection and worked fine, and did not want to troubleshoot the issue further. I indicated I wished to send the unit back to them and they could troubleshoot it themselves and send me a working console. They said ok and set me up for expedited shipping. Of course for some reason now I have to send them my power supply too, standard 2nd repair protocol I suppose.
A quick search with google reveals others are having this issue and that it is new, only being posted about in the last month or so.
I mentioned to the Live service people that the code was an existing EEPROM corruption code from the original Xbox but they really are not trained to know anything but read off a teleprompter. If I had to hazard a guess I would imagine that this is some screwball result of a region problem, perhaps modders sending in broken RRoD boxes gotten off eBay from other regions and sending them in to US repair centers (or vice versa) and then updates being applied to the console with the wrong region, but this is just a total blind guess. At this stage I don't think even MS has an idea of what this error means. Hope that this post is helpful. Be firm but polite and I believe in all cases they will agree to attempt a repair. The important thing is to get past the network problem possibility as they will waste an enormous amount of your time troubleshooting this when I can confirm this is not the issue as my other Xbox360 connects fine using the same connection. Good luck!
Then I found out what is, probably, causing the error:
QUOTE((>Stormy<))
Okay so having done a bit more research I believe I have found the cause of this error. I noticed that this error is the same error reported by Zouzz when he unbanned his console with the timing attack/keyvault replacement mod. After he downgraded his kernel he began getting this error.
I believe what we are dealing with here is one of the following:
1. Microsoft for some reason downgrades the kernel in some repair cases, perhaps 3RRoD caused by a bad update. Then they restore current kernel without checking for Live connection issue. This seems unlikely.
2. Foreign mobo's are sent into repair in different shells as a scam, repair center has no way of knowing origin of board and fixes problem and wipes kernel replaces with different region kernel update after repair. All appears to work and they don't test Live connection as they are unaware of this issue.
3. Modders send broken 360 in to repair after a timing attack.
These all seem to me to be completely ridiculous, and yet here we are. If anyone can think of other possibilities please share. This error is as far as I can find only known to exist after kernel downgrade or possibly kernel region change. The fact Zouzz got this error after only downgrading from PAL 5787 to NTSC 4532 makes me think a downgrade is all that is necessary to create this connection issue.
Links for reference:
http://translate.google.com/translate?hl=e...174687&st=0http://www.xboxhacker.net/index.php?topic=8972.0]
I also want to add this link:
http://www.xboxhacker.net/index.php?topic=8669.0This is a rare error that seems to be becoming more common. It is international in those affected. Reported cases are in the U.S., the Netherlands, France and Germany. The error code as mentioned above was experienced by Fouzz during his timing attack/unban trials. It appears similar in nature to the original error from the Xbox1, but for the most part has only been reported after a repair has taken place or after the timing attack, and also with keyvault changes. The error probably has to do with region kernel problems, or a corrupted dvd-mobo key pairing. You can not at this time fix this error and it will need to be serviced by MS. MS appears to have been fixing this error but after lots of troubleshooting and they do not seem to be acknowledging it as an actual issue. I recommend that if you are experiencing this problem you contact MS immediately for repair service and do not indulge them in their network troubleshooting as it is a waste of your time.
Feel free to discuss this error, possible theories of its cause, and your experience with MS at getting repair service.
This post has been edited by (>Stormy<): Dec 7 2007, 04:59 AM
Author
Topic: Official Y:00c2-03e0 Error Thread. (Read 139 times)