Topic: Info & How To: Avoid/fix E66 Issues With Fall Dash Update (Read 762 times)

OriginalCompGeek · « **on:** October 31, 2006, 05:19:00 AM »

Here (link) is a database thread with the results people have had with the dash update. Post yours!

Current Stats as of Nov. 1 @ 11PM EST:

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.

HOW TO AVOID PROBLEMS:
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:

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.)

IF YOU HAVE RUN INTO E66:

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.

*There is absolutely NO reason to panic if you get an E66 error, it is almost definitely fixable*

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

charis_k · « **Reply #1 on:** October 31, 2006, 05:24:00 AM »

one comment is that 4.2 is the FIXED 4.1.
So 4.2 is the way to go..

We must not forget once again to THANK c4e (and the rest) for being AGAIN one step forward before MS!!!

OriginalCompGeek · « **Reply #2 on:** October 31, 2006, 05:26:00 AM »

I noted no real advantages for 4.2 unless you were getting open tray errors. 4.1 is working fine for me.

This post has been edited by OriginalCompGeek: Oct 31 2006, 01:36 PM

charis_k · « **Reply #3 on:** October 31, 2006, 05:41:00 AM »

U R right,sorry..
4.2 can help on open tray errors?

Though c4e told its the 1.29 fw of pioneer 111 doing this...

joe90 · « **Reply #4 on:** October 31, 2006, 05:50:00 AM »

I was just about to post the same.. someone please highlight sitcky this.. hopefully we can get past the 'OH NOES BANNEDD !!!!111\1!!!' posts.

NO-ONE is banned.. obviouly just a compatabilty issue, which IS fixable.

why do people love mass hysteria and panic.. (more to come before the midterms)

noikz · « **Reply #5 on:** October 31, 2006, 05:57:00 AM »

I was running 4.2a. Grabbed the fall update and ran into the E66 error. Flashed back to original, worked fine, flashed back to 4.2a and hit E66 again. Eventually I flashed to 3.3 and it's working fine.

Chaval BR · « **Reply #6 on:** October 31, 2006, 06:35:00 AM »

QUOTE(OriginalCompGeek @ Oct 31 2006, 10:26 AM)

IF YOU HAVE RUN INTO E66:
Simple, reflash your drive. Seems to have worked every time.

You mean...
Reflash with orig.bin, yes, it works...
What about reflash a drive with E66 with a newer (4.2) xtreme FW, works too?

liteon6x · « **Reply #7 on:** October 31, 2006, 06:03:00 AM »

i just flashed my ms28 with the latest 4.2a and did the dash update and now everthing is perfect
thanks c4eva

haccord · « **Reply #8 on:** October 31, 2006, 06:12:00 AM »

Hi guys !

Someone have been tried with a MS25 (firmware 1.0) ?

Regards

Mana · « **Reply #9 on:** October 31, 2006, 06:17:00 AM »

remember even non modded people are now getting the e66, so this could just be the update being buggy...

Canard-WC · « **Reply #10 on:** October 31, 2006, 06:17:00 AM »

Hi guys
Any news with the Hitachi/LG drive ? Seems thoses e66 bugs are juste compatibility issues, but I'd rather be sure before I apply this update ^^

purepwnage12560 · « **Reply #11 on:** October 31, 2006, 06:20:00 AM »

my friend just ran into the e66 and he has MS25 samsung drive

Vintersorg69 · « **Reply #12 on:** October 31, 2006, 06:58:00 AM »

QUOTE(purepwnage12560 @ Oct 31 2006, 02:27 PM)

my friend just ran into the e66 and he has MS25 samsung drive

modded? unmodded? what firmware?

Canard-WC · « **Reply #13 on:** October 31, 2006, 06:28:00 AM »

Well i can confirme there is NO BUG with the update with the Hitachi/LG dvd with GaryOPA 2.3 (at least with the 47d drive)

You can play on live and enjoy backups too

purepwnage12560 · « **Reply #14 on:** October 31, 2006, 06:35:00 AM »

he was using the latest FW the 4.2 from c4e i can confirm im looking at it right now it says E66 so i dont know what happened

Author Topic: Info & How To: Avoid/fix E66 Issues With Fall Dash Update (Read 762 times)