Quantcast
SideQuesting… We Love Video Games!
We Love to Write About Games, Geeks, and Beer!


Featured

May 29, 2011

E66: Targeted Xbox Patch Packs Pitfalls [Update]

More articles by »
Written by: Alex Rubens
Tags: , ,

[UPDATE] I was contacted by Stephen Toulouse (@stepto), Xbox Live Director of Policy and Enforcement, who said “@alexrubens you were given incorrect information. I’m looking into it now. We do not disable consoles. Just ban them from Live.”. Interesting. I will update as more information comes in.

[UPDATE 2] Stephen has commented below clarifying that ” We do not disable consoles. We only ban them from LIVE. I suspect the support people were reading from some outdated or incorrect documentation.” “But to be clear, we DO NOT disable consoles. Whatever information the support people had was totally incorrect and I will take care of that separately.”. He has offered to look into my case, hopefully this can be resolved.

[Update 3] Below is a video of Alex trying to update his console and subsequently being hit with the E66 error (ed. note: Third and fourth updates written by Eric Smith):

[Update 4] Several people that have unmodded consoles have contacted SideQuesting reporting the same problem as Alex. Also, an Xbox 360 owner that has admitted to modding his console claims that he has not been banned. More details forthcoming.

[UPDATE 5] According to users in this thread on GameTrailers.com, the picture is photoshopped and the “Xbox 360, Comp, 480i” box in the corner of the screen means that my console is modified. This is due to the TV trying to find the input when the console went into error mode. There are even more posts on this topic on Xbox.com with other users having the same issue. When they attempt to contact Xbox Support, they are treated with the same attitude. Users with consoles that have been modified are reportedly not having issues according to @LOKIOLR on twitter, ” You want to hear the ironic part. I have a modded console that updated just fine with the last live update. Not banned either.” followed by “oh, and their added security has already been defeated. All in all, quite a successful update Microsoft.”.

[UPDATE 6] I went to Microsoft today and handed my Xbox over to Stephen Toulouse so that he can investigate the problem.

[UPDATE 7] According to the comments and message boards that I have been looking around on, the speculation is that the firmware is not compatible with Samsung DVD drives. No official word on this though.

[UPDATE 8] I just got off the phone with someone at MS who is investigating my console. The console was tampered with and they are looking into how. Before you say, “A HA! I knew he tampered with it!”. The things that he described, I have nowhere near the capabilities to do. He said that while there are people who do that intentionally, some people get caught up in it unintentionally. Besides the case intrusions, there was signs of the ODD (Optical Disk Drive) being moved and installed with a custom firmware. I’m not saying that this is the case. This is a scenario that happens though, as in, someone mods their Xbox, returns it, and it gets put back out on the shelf. This is always a possibility.

NOTE: Before I continue to just update this post with new facts, please think about this, before you say “Oh, he is modded and is just mad that he got caught.” Think about it, modded consoles are not affected and they have already found a work around for the update system.

On Friday I received my copy of Dirt 3 for Xbox 360 in the mail. When I turned on my Xbox to put the aforementioned game in, a prompt came up, “An update is available from Xbox Live. Please install to connect to Xbox Live.” Thinking that this was normal, I did as it instructed and right near the end of the update, the screen cut out. When it came back I received a system crash error message stating “Error Code: E66 Contact Xbox Support for more information.” I found this vague error message to be very odd. I retried the update process a few more times with the same outcome. I eventually decided that I should do as the message asks and call the Xbox Support line. This is where the madness began.

I called and was greeted by a very helpful person who asked me what my issue was. They were great and very eager to help, going through the steps of where I bought the console and those necessary steps, right up until the point where I mentioned the E66 error code. I was greeted with a sigh, “Sir, this error code is associated with modified consoles. This is happening because you modified your console and are trying to connect to Xbox Live, which violates the terms of service.” This was an outright surprise to me as I have never modified my console. I asked him to elaborate on what he meant by modifying my console. “According to our policies, we cannot disclose how exactly it has been modified. Just know that we have a system in place that does multiple checks and that is how we KNOW that your console has a software modification.” Despite my numerous attempts at trying to get them to clarify what that meant and how it was possible that my console was associated with that, The only response that I could get was, “There isn’t a debate here. This doesn’t happen by accident. It happens when the system determines that you have been using these modifications.” He went on to share that they sent out this update to those that they suspected and the update was a security check. Without this check, your console is permanently banned.

I asked them if there was any other way for them to check. I was asked for the “x-code” in my system information and was told that they would use that to look it up. After waiting on hold for 20 minutes, the representative returned and said, “Yeah, your console is banned for software modification, and there is nothing that we can do after you modify it.” I told him that I was 110 percent positive that my console had not been modified in any way. His snarky response was, “Well, if you are so confident, pay $100, send your modified console in to our repair center; we will prove that it has been modified and send it back to you in without repair”. There was no doubt in their mind that I had modified my console and nothing I could say would change that.

While I attempted numerous times to speak to a supervisor, I was assured that they would tell me the exact same thing and that it wouldn’t make a difference. I demanded to speak to one as this was an outrageous claim. I was put on hold and after 30 minutes of waiting, I was told that there were no supervisors for me and that they don’t have a schedule for that kind of thing, but I would be getting a call back anytime within the next 24 to 48 hours. WHAT?!

At this point, I just wanted to understand why the software would flag my unmodified console. I asked the representative to clarify what “system” they were using to determine this. Just like everything else, I was told that they “cannot disclose that information”. I suggested that the Policy and Enforcement department might be behind this and he immediately confirmed that fact. I asked for all of his information (name, reference number, etc) so that I could have that information for the callback. I then asked to be transferred to that department’s service line as he assured me that they had one. He asked for my gamertag and then told me that he was transferring me and did so before telling me his name.

I then heard the all too familiar “Please wait” and then a voice said “Hello, this is Xbox Support, how can I help you?” I said, “This isn’t the Policy and Enforcement department is it?” She confirmed this fact and said that they don’t even have a number for that department and that there would have been no way for the previous guy to transfer me there. I asked her to pull up his data that he assured me was in the file; only to find out that his notes were, but not his data. So here I am, back at the start; almost two hours later and even more confused than I was at the start. She told me that I would be best to wait for that callback to happen and we ended the call there.

I knew that a console bricker couldn’t be something that had gone unnoticed; this is the Internet after all. I searched for “E66 error update” and found a few shady sites talking about the error, but the last that I had seen was from early 2007. Throughout my entire conversation with Xbox Support on the phone, I had been tweeting the outrageous claims that they had been making. Suddenly, tweets started to come in from people having the same problem. @xKoRnDoggx says, “[I’m] seeing a new trend here. Xbox ugottaproblem. Not just the new slims either.” Followed up by @Lak3, “Why should you have to play 100 bucks for something that is happening to a lot of people @xboxsupport I’m not modded either.” This just goes to show that it isn’t just me and that contrary to what the personnel at Xbox Support say, I am not the only one that this is happening to.

We’ve reached out to Microsoft for comment, but have yet to hear back from them. We will update as the story develops.

What would you do in a situation like this? The fact that this was a targeted effort towards console modifiers that ended up hurting regular consumers without any credit from Microsoft is the worst part of this. Imagine that you are suddenly accused of criminal acts and told that you cannot use your console anymore without any explanation. This is crazy, especially when you have done nothing wrong? Have you heard of anything like this before?



About the Author

Alex Rubens





74 Comments


 
 

  1. Catchinuslippin

    Still playin black ops. created a new gamertag and have all updates i need now. Its 100% legit. real! When you take your console apart first run the update without your cd drive connected. You’ll get an error code saying it couldn’t finish the update to hardware malfunction. wonder what that could be?! so plug back in your old cd drive and update your system. after the update finishes it will shut off a cpl times and update again. then it will install all new updates and your back on live killing people all night long. This update is the worst update ever. I think its because microsoft thought thier new xbox kenect system would be a top seller. That it sure is. But doesnt pull in enough money for the systems. Because most of us have older consoles and dont see the point in spending 300 when you have a console that works fine. So ms starts thinking, HMMM wonder what would happen if we throw an update out on all old consoles and if they ever cracked it open and had parts replaced lets ban them so they have to buy a new xbox. My name is Josh Pfister and if xbox or ms wants to contact me please do! jpfister25atgmaildotcom. OH and Stephen Toulouse i hope you email me and let me hear what you have to say. Infact please email me because I would love to have a nice conversation with you.


  2. Catchinuslippin

    Here are all your error codes and what most of them mean.

    1 red light flashing:

    Primary———-Secondary—————Reason

    E64——————1000—————-Bad DVD flash/ dead flash chip(Timeout)
    E65——————1001—————-Bad DVD flash/ dead flash chip(DMA)
    E66——————1002—————-Wrong DVD-drive version
    E67——————1003—————-Broken Harddrive(Timeout)
    E68——————1010—————-Broken Harddrive(DMA)
    E69——————1011—————-Broken Harddrive(HDDSS)
    E70——————1012—————-HDD Error Filesystem/Not Found
    E71——————1013—————-Dashboard update error (NAND related)
    E72——————1020—————-NAND issue (loose pin/ bad flash)
    E73——————1021—————-Cold solderjoint – Ethernet/Southbridge
    E74——————1022—————-Cold solder joint under GPU- (H)ANA
    E75——————1023—————-Network chip cold joint/ wrong vendor
    E76——————1030—————-Dead network chip
    E77——————1031—————-Dead network chip
    E78——————1032—————-AsicId check failed
    E79——————1033—————-Broken Harddrive(Xam.xex)
    E80——————1100—————-NAND – Wrong LDV Version

    2 Red Lights

    E05——————0011—————-The CPU is overheating
    E06——————0012—————-The GPU is overheating
    E07——————0013—————-Cold joint under RAM/ RAM overheating

    3 Red Lights

    E00——————0000—————-The Xbox doesnt know whats wrong it freezes after showing the first digit(0) of the error code.Might be a cold solder joint somewhere under the GPU as someone fixed it with the X-Clamp replacement, might also be scaler or Southbridge related since this is where the error code is calculated..
    E01——————0001—————-Short circuit in the console/faulty PSU
    E02——————0002—————-Cold solderjoint under CPU
    E03——————0003—————-Power problem/ Cold solder joint under CPU
    E04——————0010—————-Cold solder joint under Southbridge
    E08——————0020—————-Bridged solderjoint/Short – CPU/GPU/RAM
    E09——————0021—————-Bridged solderjoint/Short – GPU/Southbridge
    E10——————0022—————-Bridged solder joint/Short GPU-> (H)ANA
    E11——————0023—————-(unknown) probably a short under Southbridge>ANA
    E12——————0030—————-Temp sensor problem/ Cold solder joint under CPU
    E13——————0031—————-Faulty RAM brick/ Shorted out resistor
    E14——————0032—————-(unknown) probably temp sensor related
    E15——————0033—————-(unknown) probably temp sensor related
    E16——————0100—————-Cold solder joint – GPU
    E17——————0101—————-USB port (bridged pins)
    E18——————0102—————-Cold solderjoint – CPU/GPU/RAM
    E19——————0103—————-Cold solderjoint- GPU/ bad cap
    E20——————0110—————-Cold solder joint -> RAM
    E21——————0111—————-(unknown) probably NAND/RAM?
    E22——————0112—————-(unknown) probably RAM
    E23——————0113—————-(unknown) probably RAM
    E24——————0120—————-(unknown) short under RAM
    E25——————0121—————-Cold solder joint under CPU
    E27——————0123—————-(unknown)
    E28——————0130—————-(unknown)
    E29——————0131—————-(unknown)
    E30——————0132—————-(unknown)
    E31——————0133—————-(unknown)
    E32——————0200—————-Cold solder joint GPU/RAM
    E33——————0201—————-Cold solderjoint-> GPU/RAM
    E34——————0202—————-(unknown)
    E35——————0203—————-GPU related – resistors
    E36——————0210—————-(unknown)\
    E37——————0211—————-(unknown)
    E38——————0212—————-(unknown)
    E39——————0213—————-(unknown)
    E40——————0220—————-(unknown) missing resistors GPU
    E41——————0221—————-(unknown)
    E42——————0222—————-(unknown)GPU/CPU related?
    E43——————0223—————-(unknown)
    E44——————0230—————-(unknown)
    E45——————0231—————-(unknown)
    E46——————0232—————-DVD Drive Failure
    E47——————0233—————-(unknown)
    E56——————0320—————-(unknown)
    E57——————0321—————-(unknown)
    E58——————0322—————-(unknown)
    E59——————0323—————-(unknown)
    E60——————0330—————-(unknown)
    E61——————0331—————-(unknown)
    E62——————0332—————-(unknown)
    E63——————0333—————-(unknown)

    4 Red Lights

    ——————-4444—————-No/Faulty A/V cable or (H)ANA related


  3. Catchinuslippin

    Whenever the Xbox 360 Console has a problem it will display error lights/codes.. These lights/codes are used to determine the problem with the console. There are many different patterns which will also show a numbered error code. These numbered error codes are shown below with their corresponding LED Code and may helped you with your trouble shooting..

    Instructions:
    If you have encountered one of these service errors:
    - look up the code in the list below
    - read the info
    - read the solution (very important )

    Leds 1, 2, 3, and 4 are flashing red:

    Info:
    The AV cable cannot be detected by the console

    Solution(s):
    - Make sure that the AV cable is correctly connected to the Xbox 360 console.
    - Disconnect the AV cable from the Xbox 360 console, and then reconnect the AV cable to the Xbox 360 console.
    - If the four flashing red lights continue to flash, try wiping the metal area of the AV pack with a dry cloth. The metal area is the end that plugs into the console. Wipe the metal area thoroughly, and then try the AV Pack again.
    - If the AV cable is correctly connected but the four red lights are still flashing, substitute a different AV cable if you have one available.

    Leds 1, 3, and 4 are flashing red:

    Info:
    General Hardware Failure
    The specific type of hardware failure can be determined by a “hidden” error code:
    - Turn the xbox 360 on, and wait till the 3 red lights are flashing.
    - Press and hold the sync up button (the small white one), while holding that button press the eject button.
    - The LEDs will now blink the first number in the code (as described below).
    - Release the eject button and press it again.
    - The LEDs will now blink the second number of the code.
    - Release the eject button and press it again.
    - The LEDs will now blink the third number of the code.
    - Release the eject button and press it again.
    - The LEDs will now blink the forth number of the code.
    - Release the eject button and press it again.
    - The LEDs will go back to the 3 red flashing lights.

    You should be able to determine the difference between the 3 flashing lights and the error code lights by the rate in which they flash.

    Here is how you interpret the LEDs to get the code number:
    * All four lights flashing – 0
    * One light flashing – 1
    * Two Lights flashing – 2
    * Three lights flashing – 3

    0001 – power supply problem
    0002 – power supply problem
    0003 – power problem could be the PSU could be the GPU/CPU, somehow the console isn’t getting clean power from the power supply.
    0010 – over heating
    0011 – over heating
    0012 – over heating
    0013 – over heating
    0020 – not yet known, possibly overheating
    0021 – DVD Drive Time out – Can be caused by problems with a firmware flash. This is also speculated to sometime be caused by a problem with the southbridge chipset on the motherboard.
    0022 – GPU Error / GPU Overheating
    0102 – unknown error – littereally means the console does not know what is wrong. possibly a short or cold solder joint somewhere (2 reports of people repairing this, one was removing moisture build up inside the console, the other used a hot-air rework to reflow the BGA Ram chips)
    0110 – not yet known
    1022 – not yet known

    Solution(s):
    - Try restarting the console.
    - If restarting the console does not resolve the behavior, follow these steps:
    * Turn the console off.
    * Unplug all the power and AV cables from the console.
    * Unplug the power cord from the wall socket.
    * Firmly reconnect all the cables.
    * Turn on the console.
    - If these steps do not resolve the behavior, turn the console off, remove the hard drive, and then turn on the console. If the 3x Red LED error light is no longer displayed, turn the console off, re-attach the hard drive, and then turn on the console.

    Sections 1, and 3 are flashing red.:
    Info:
    Overheating

    Solution(s):
    - Let the Xbox 360 console cool. You may have to wait several hours for the console to cool enough. Do not turn on the console when the console is hot.
    - Verify that the console has sufficient ventilation and that the fan is operating. For more information about ventilation, see the “More Information” section.

    Info:
    Hardware Failure

    The Specific Type of hardware failure can be determined by the error code displayed on the screen.

    The Specific Type of hardware failure can be determined by the error code displayed on the screen. If the screen is blank or you would like additional information follow the instructions for determining the secondary error code in the section below.

    E01:
    possibly a power supply problem

    E02:
    possibly a Network Interface problem (might be fixed by loosening the x-clamps)

    E03:
    possibly Power problem could be the PSU could be the GPU/CPU, somehow the console isn’t getting clean power from the power supply.

    E04: Unconfirmed:
    There is a problem with the Southbridge Chip usually dealing with how it connects to the mainboard (cold solder joint/bridged solder joints)

    E05: CPU over heating
    If you are receiving this error after disassembling your console make sure to all 8 of the heatsinc screws are tightened securely to the board/heatsink holes.

    E06:
    GPU over heating -ensure your x-clamps are installed properly.

    E07:
    RAM over heating

    E08: Unconfirmed:
    General I/O Malfunction, could be caused by an error with any of the I/O devies such as A/V port, USB, Hard drive, DVD drive, etc. over torquing of the AV or heatsync bolts can cause this error.

    E09: Unconfirmed:
    This can be caused by two completely different things either:

    A. DVD Drive Time out – Can be caused by problems with a firmware flash. This is also speculated to sometime be caused by a problem with the southbridge chipset on the motherboard based on how it connects to the DVD drive.

    B. GPU error – generally caused by a poor connection to the mainboard (cold solder joints/bridged solder joints) See error E18 for more information

    E10: Unconfirmed:
    CPU error, generally caused by a poor connection to the mainboard (cold solder joints/bridged solder joints). This can also be triggered by an error with the TSOP.

    E11:
    (not yet known)

    E12:
    Possibly a problem with temperature control

    E13: Unknown:
    could be caused by a short between the heatsink and surrounding capacitors

    E14:
    (not yet known)

    E15:
    (not yet known)

    E16: Unknown:
    Likely a cold solder join in GPU or Ram chips (see error E18)

    E17:
    (not yet known)

    E18:
    Error in the “Digital Backbone” (CPU/GPU/RAM), this is usually caused by a cold solder joint between the GPU and the mainboard.

    There are two theories to fixing this one deals with the “X” clamps that hold down the chips. The other involves re-Heating the chips. DO NOT attempt either of these if your console is still under warranty. If your console is still under warranty return it to the store where it was purchased or call MS to have it replaced.

    E19: Unknown:
    GPU Error this is usually caused by bridged solder points where the GPU connects to the mainboard. see error E18 for more detailed information

    E20:
    likely a Ram error, this can be caused by a cold or bridged solder joint on one of the Ram chips.

    E32:
    (not yet known)

    E33:
    (not yet known)

    E34:
    (not yet known)

    E35:
    over heating GPU possibly due to lack of thermal compound.

    E45:
    Unknown (possibly dashboard update related)

    E64: DVD Drive Error
    Dvd drive timed out during reset :Wrong firmware, dvd is without f/w chip, etc. This can also be caused by the tray not being fully closed on boot. also it could mean that the Kernel can’t be launched/signature in NAND Flash chip is broken It could be possible after bad update. This might also be caused by a bad SATA cable.

    E65: DVD Drive Error
    Dvd drive is not DMA configured :Wrong firmware, dvd is without f/w chip, etc. This can also be caused by the tray not being fully closed on boot.

    E66: DVD Drive Error
    Dvd drive pairing failure: DVD model, or version does not match that of the version expected by the dashboard. OR the firmware version on the drive is older then the firmware version expected by the dashboard. Make sure the DVD drive is of the same version originally included with the console and that it is using either the original firmware included with the console or newer. if drive can eject, read, and write under windows but errors on console, replacing original firmware should fix issue.

    E67: Hard Drive Error
    Hard drive timed out during reset: It could be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it.

    E68: Hard Drive Error
    Hard drive not DMA configured: It could be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it. Also this can be caused by a problem with the fans that make them draw too much power, it can also be caused if you have unnecessary accessories attached to the console like an external fan unit. Attempt to remove unnecessary accessories first, and then necessary components such as the hard drive and USB devices. If you have any case mods you may want to investigate those as well.

    E69: Hard Drive Error
    Reading the HD Security sector failed: It could be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it

    E70: Hard Drive Error
    Hard drive not found

    E71: Dashboard Error
    Error within Xam.xex: possibly a dashboard update error, Check below in the “Console Reset Codes” for instructions. If that does not work there is no other solution and the console must be sent back to MS for repair.

    E72: Dashboard Error
    Error within Xam.xex: Like a problem with the NAND flash

    E73: I/O Hardware Error
    Couldn’t calibrate HSIO Bus from edram: this error is likely caused by a problem with the Ethernet port or supporting control devices

    E74: I/O Hardware Error
    HSIO related, could be crc error, or many things: There is high chance it’s a scaler chip problem (the “ANA” or “HANA” chip near the AV cable connection) it can also be caused by a faulty AV cable so check that first. Microsoft covers this error under their 3-year warranty, this is availble to anyone who hasn’t modified their console. contact MS to get a free replacement console before attempting to fix this yourself. Failing that this error In some cases it is a problem with the GPU and may be repairable by doing the x-clamp replacement (see error 0102)

    Try using a different AV cable. If the AV cable is known to be working then there is a 90% chance it’s a scaler chip problem (the “ANA” or “HANA” chip connected directly to the AV cable) in rare cases it is the GPU.

    E75: Ethernet Error
    Couldn’t read ethernet phy vendor: Strange but sometimes caused by the DVD drive not being connected properly.

    E76: Ethernet Error
    Couldn’t complete ethernet reset: This error is usually cased by the Ethernet port’s controller chip, a dead chip may not cause the error but removing the Ethernet controller chip does, it may also be caused by other Ethernet related problems.

    E77: Ethernet Error
    phy request is already processing/reading reg failed/Failed to write reg: This error is sometimes caused by power problems with the RAM chips. It might be cause by a short between the heat sink and resistors or by more serious problems with the RAM.

    E78: Dashboard Error
    AsicId check failed

    E79: Dashboard Error
    Couldn’t start xam.xex: probably a file system corruption, it could also be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it.

    E80: Dashboard Error
    Wrong LDV version in NAND Flash: This is in new dashboard. You have the update but haven’t R3T6 resistor. You can:
    -Downgrade to old dashboard, solder back the resistor and then update your xbox
    -If you have CPU Key, get current NAND Flash image and fix LDV (just add 1 up to latest kernel). (See error 1100)

    E81: Dashboard Related?
    Corrupted NXE Dashboard install or other dashbaord related files.

    Related 360-HQ Forums – Xbox 360 E81 Error after NXE Feb 2009 Update??

    If you are having issues with your xbox 360 console please post in our official error codes topic in our forums so that our other members and staff can reply.. You can find the official 360-hq Xbox 360 Error Codes topic.

    Console Reset Codes
    1. Clear All Installed Game Updates and Console CacheGo to the “system” blade
    2. Select “memory”
    3. Press Y on the HD symbol
    4. Press X,X, Left Bumper, Right Bumper, X,X
    5. A message will appear saying: “Do you want to perform maintenance on your Xbox 360 storage devices?” Select Yes
    6. Clear Any Failed system updates that cause the console to error.With the console off, press and hold the sync up button (the small white one) While holding the sync button press the power button to turn on the console
    7. Continue to hold the sync button until the Console has booted up completely.

    During the boot process the console should now remove/clear any failed Xbox 360 updates, allowing you to use it normally.


  4. Darquan

    Solved my problem…had the PIRATES do their thing and update it. Made sure to tell them I do not want to play pirate games. Now the updates work and my LEGAL Madden can be enjoyed!


  5. MacGyver

    The method of putting another Xbox 360 DVD drive in letting it update worked. Then put the original back. Thanks for the post.


  6. Hitachi_beatse66

    i am discusted in the way microsoft is treating you guys with e66 error. because its only the toshiba drives and am going to help you all. get a hitaci 79 fitted with your key from your sammy. and it will update no problem weather it is flashed or stock { standard}
    obviously there is an eror with the sammys, and the arent fixing it, just like they got away with rrod. arseholes. FIT A HITACHI IN YA XBOX E66 FIX the hitachi i used 4 a customer was hitachi 79. also microsoft remember that song i dont need you now. you taken everything from me. :) no more


  7. Finewithoutu

    Am fine without you now. ive given you everything. microsoft. scum


  8. Discustingcompany

    after fitting the hitachi 79. updated without problems or without error. no sammy drive no E66.
    ive only tried this with an hitachi, because you can update from disk, even without the propper key. obviously you need the right key for playing games.
    it wont cost you 100pounds either. you can pick up an hitachi from ebay for about 19.99. bit less. and someone should flahs your drive over for at least 30ish. maybe less. so your talking 50 pounds. and you have halfed what microsoft will charge you just to tell you they wont fix it.
    arseholes. money goes to money. and this company wants all the money. greedy arseholes. if its not a error or fault. why is it only happening with toshiba-samsung drives. why not a benq or a lite-on. or why not a hitachi. because it is a fault. just like the red ring of death is a fault. but they are still wriggleing there way out of that mess. discusting company.


  9. XB pLAYA

    This solved my E66 problem.
    I have a xenon xbox with sammy drive. I just updated to LT + 2.0 to try to play some of the newer games and got the E66 when it tried upgrade the dashboard to version 2.0.13604.0 . Apparently E66 error happens when the upgrade code detect that the DVD firmware is the “Wrong DVD-drive version” . So I just downgrade my dvd firmware to stock version and then do the dashboard upgrade via USB then re-update the dvd firmware to LT + 2.0 .

    Go here to update Dashboard to version 2.0.13604.0
    http://digiex.net/downloads/download-center-2-0/xbox-360-content/dashboard-updates/9501-xbox-360-dashboard-update-2-0-13604-0-download-avatars.html


  10. Possiblefutureps3owner

    I got this error when attempting to play TES V Skyrim which i picked up today. I was prompted to update which i did as usual, only to be greeted by a myriad of different languages basically telling me to go f myself. I have never had my box repaired as i have never had a problem with it before. I merely want to play my game, i really do not have any need for online play in a single player rpg, but unfortunately i cannot escape this error. If i put the skyrim disc in, i get the e66 error page, if i put any other game in, i get a screen prompting me to reinsert the skyrim disc to finish the update, which of course, WONT WORK. So if anyone out there can give me a simple fix to just play in offline, it would be greatly appreciated, otherwise, i just wasted 60 dollars.


  11. swaRts

    im having the same problem.. just bought TES skyrim and i get an e66 error.. still able to play other games, just not skyrim..


  12. Sstieber16

    boah -.- i cant play skyrim because of this fucking error. i’ve waited a very long time for this game and as i put it in my console this fucking error came up. dammit! and when i call microsoft they do not have something better to do than telling my that my xbox is modded. IT IS NOT MODDED!! i guess i will buy a new xbox. a slim with 4 gigs. in germany it’ll costs me “just” 180 bucks. This is not fair..


  13. Graderman81

    I got this error the first time I ever tried to use live. I bought my xbox brand new 6 months ago. Have played a few games in campaign mode. Just hooked it up to the internet for the first time today and tried to create a gamertag and it says my console is banned. How can this be if I have done nothing to it, and never even been online. I know nothing about any kind of modding. I hardly even play my xbox as is. this is ridiculous!!!!


  14. Hb2kbuzzsaw

    Just bought WWE 12, tried to play, update needed, E66. Never modded, never even opened. Infuriating to say the least, any more word on a resolution to this problem??


  15. Dj_keef_c

    Hi guys I’m having the same problem!! Cannot play any new games because it won’t update, sent 12 emails spoke to numerous people and it all comes back and they say that the error code is because I have tampered/moded my Xbox!! WTF! I have never moded my box! So I’m stuck again with an Xbox that won’t work! Now I did leave this allow as I could be bothered to waste my time trying to tell them that I HAVEN’T MODED my Xbox so I bought a nice new black Xbox but this has just bloody broken so tried to get my other one to update but guess what…………….NOPE still won’t update! I’m hoping the next update that has been realised today will sort this!


  16. Shabasheh

    Sounds like MS is making mugs of us and from some of the comments it sounds like it works for them by getting you to buy a new console. I got told the same. I’m not buying another xbox. I’ll go for a wii instead. Bye bye MS.


  17. Bjorn

    Buy an PLAYSTATION 3. And skimm XBOX 360, that is there service too us, this is what we will do! I had from the first day on an xbox360 still have, and even my friends. we all got problems with the xbox ring of dead etc. they all purchased an new one. i still haven’t. My brother has an playstation 3 from the beginning, never had any problems with it. and plays his online games for free. I know what i am gonna do.

    Microsoft: manufactures Windows. Every new windows thats got manufactured. still haves problems. These guys can’t make things right the first time. They make products fast, Launch it, and after it is on the markets, thenthey work the bugs out and refine it! They only got eye for one thing: PROFIT!!

    Well im done with microsoft products, i’ll buy myself an Apple computer and An Sony Playstation 3 gamingconsole.

    From Holland:

    Bjorn


  18. Anonymous

    I too am getting this error. If modded xboxes are not getting this error, how do I mod my xbox in order to get rid of it?


  19. Sx_turbo1

    mine has just done this, i was boughjt the console by my brother 2 years ago, he got it 2nd hand from game, i’m not a huge game player but do like to play here and there, now my xbox has been fine with all updates, even when they done the update to get rid of all the modded xboxes, my xbox still worked, (mine is defo not modded). at xmas, i tried to do the update like it asked for, and froze halfway through, i reset the xbox and downloaded the update again, after completing it came back and flashed up e66 error code, and now i cannot access any xbox live at all. its not very fair. microsoft keep just telling me there nothing they can do, and suggest i buy a new xbox for the problem to be resolved. after a bit more arguing they said they could repair it for a fee of £75, and that if they find the console to be modded in any way they will box it back up straight away without putting it back together. I dont trust microsoft to do this as they will just turn round and say it been modified regardless. i tackled the guy and said how can he be certain that its me who has caused this, and reminded him of microsofts sketchy past with unreliable xbox’s and he flatly denied all knowledge of xboxes ever being troublesome, i even reminded him of the rrod, and he denied that was ever a big issue and said it was dramatised by forums lol, thats why microsoft had to put away 100 million dollars into a seperate account just for warranty claims lol


  20. Sx_turbo1

    oh forgot to mention mine is the pre hdmi version built 26/8/2006, which adds to the conspiracy of the internet that microsoft are deliberately killing off the early machines, spose it keeps the sales of xboxes up and gets rid of old consoles out of the food chain


  21. wonder if this was just an update to target all outdated consoles w/o an HDMI input to force a trip to Frys/BB to buy a new console….I can hear the meeting now… OK everyone, the update is going out today and you will be faced with a lot of upset customers. Just let them know it doesn’t matter if they got the RROD and had it repaired or not, the console has been modified and can no longer be used on xbox live. You will have to get a new console. Billy! we need some humanitarian characteristics here….


  22. Thomas C

    I have just gotten this error too, E66. I have had a hard time trying to research exactly what causes this and I have not heard of anyone I know of having it. The most I have found are mostly people claiming that it is an update error. My xbox 360(a very old one) has been repaired from 3 rings (big surprise there) multiple times and have never had that problem before. Repaired by myself (past warranty anyways and not going to pay hundreds of dollars to start the cycle over again). And just like Sstieber16 said for himself, I was trying to play Skyrim. Once my system “updated” it will show E66 whenever I put in a game from the new update generation, while I am still able to play whatever game I want before this update. My only long term idea for a solution is get a PS3 when possible, leave the Microsoft scams and scandals behind and never look back.


  23.  trying to do what you did, i mistakenly bought a modded xbox off craigslist. i know how to upgrade dashboard via usb but can you explain how to downgrade the dvd firmware to stock version


  24. Wasn’t the first time this happened. Won’t be the last. Microsoft is well aware none of their users have the kind of funds, and class of lawyers, that Microsoft does. So they know there is absolutely nothing you can do about it.


 
 



Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>