is a database thread with the results people have had with the dash update. Post yours!Current Stats as of Nov. 1 @ 11PM EST:
HOW TO AVOID PROBLEMS
- 81.25% of drive updates completely successful with 4.0+ firmware
- 78 Drives had no problems
- 18 Drives required a firmware downgrade, a firmware reset to original, or would not work at all.
The problem seems to be completely random, and avoiding it seems to be a matter of luck more than anything. However, the best precautions would be:
IF YOU HAVE RUN INTO E66
- Make sure your drive is flashed to Xtreme 4.1/4.2
- Manually hex-edit your key into the firmware. Try to avoid using auto-flashers, etc.
- Completely disconnect your DVD-ROM from your 360 before booting up and updating (This includes the power cable, simply unplugging the SATA cable will cause your 360 to refuse to boot.)
*There is absolutely NO reason to panic if you get an E66 error, it is almost definitely fixable*
- Option 1 - Flash back to original firmware, this works every time.
- Option 2 - Manually hex-edit your drive key into your modified firmware and flash that firmware. This seems to have a pretty good success rate.
- Option 3 - If you have an MS25 drive, try flashing to Xtreme 3.2-3.3. If you have an MS28 drive try 4.0-4.2. You can also simply try manually hexediting your drive key into 4.1/4.2, and then flashing your MS25. This is sometimes effective.
- If you can't get 4.1/4.2 firmware to work, try hex editing the firmware to make it read as MS25. The method can be found here.
Commodore4Eva has given us information what exactly E66 is HERE
. It appears he may be right in his interperetation, but Microsoft's detection of different firmware is shaky at best as 80% of users have no issues whatsoever. ABOUT E71
E71 was apparently related, in most cases, to brand new consoles. Microsoft has patched the dash update and people should not be getting this error anymore.
SOME INFO: HERE
This E66 seems to be a very ineffective attempt by MS to stop modders.
I, myself, ran the dashboard update with my MS25 w/4.1a firmware connected and had no issues. There seems to be no logical pattern that causes one person to get the error, and another not to. If more news becomes available, the thread will be updated.
*Good Luck!*This post has been edited by OriginalCompGeek: Nov 3 2006, 01:03 AM