Print

[smash_linux]

I think this is right for now, anyone can prove that this is wrong?

- MS25 : ORIGINAL OK
- MS25 : 3.0 OK
- MS25 : 3.1 OK
- MS25 : 3.2 OK
- MS25 : 3.3 OK
- MS25 : 4.0a/b OK
- MS25 : 4.1a/b ERR66
- MS25 : 4.2a/b OK

- MS28 : ORIGINAL OK
- MS28 : 3.0 ERR66
- MS28 : 3.0 ERR66
- MS28 : 3.1 ERR66
- MS28 : 3.2 ERR66
- MS28 : 3.3 ERR66
- MS28 : 4.0a/b ERR66
- MS28 : 4.1a/b OK
- MS28 : 4.2a/b OK

[blackwing]

QUOTE(smash_linux @ Oct 31 2006, 07:33 PM)

I think this is right for now, anyone can prove that this is wrong?

- MS25 : ORIGINAL OK
- MS25 : 3.0 OK
- MS25 : 3.1 OK
- MS25 : 3.2 OK
- MS25 : 3.3 OK
- MS25 : 4.0a/b OK
- MS25 : 4.1a/b ERR66
- MS25 : 4.2a/b OK

- MS28 : ORIGINAL OK
- MS28 : 3.0 ERR66
- MS28 : 3.0 ERR66
- MS28 : 3.1 ERR66
- MS28 : 3.2 ERR66
- MS28 : 3.3 ERR66
- MS28 : 4.0a/b ERR66
- MS28 : 4.1a/b OK
- MS28 : 4.2a/b OK

[smash_linux]

Cool, thanks!

[alphanumeric303]

Unplugging might work, but we dont know if it is related or not.  What if the same people that unplugged their drive before installing the update were the same people that wouldnt have been affected by the update anyway.  

For those that updated and unplugged their drives, can you please post your firmware version and drive version.  



On a side note:  It still bugs me that people that havent even modded their boxes are getting the same error.  I dont know if this is a good thing or bad.  I still havent turned on my 360, and I will probably wait until there is more testing done.

[OriginalCompGeek]

My update:

Drive: MS25
Firmware: 4.1a, key inserted with the Xtreme included .bat
Drive Left Connected during update

Everything went perfectly smooth.

[infidelity]

I havent received any error codes, but after the update, my gamertag did disappear, and I was able to recover it from XBOX Live.

This update DID NOT effect my flashed Hitachi.

Just wanted to share my findings.

[OriginalCompGeek]

QUOTE(vicfalc09 @ Oct 31 2006, 03:15 PM)

If a drive is not flashed yet do you reccomend flashing before or after the update.

I don't think it matters a whole lot.

Im not even sure what I'd do in the same situation.  Might as well update first, I guess.

[I'dkickurass@cod2]

Yep got the E66 error when I downloaded the update this morning. I have a MS25 drive with 4.2A firmware. I flashed it back to original, worked fine, then I flashed it back to 4.2A, same error. Did that a couple of times then went back to 3.3. It works but I don't feel like I'm protected.

[OriginalCompGeek]

QUOTE(I'dkickurass@cod2 @ Oct 31 2006, 03:29 PM)

Yep got the E66 error when I downloaded the update this morning. I have a MS25 drive with 4.2A firmware. I flashed it back to original, worked fine, then I flashed it back to 4.2A, same error. Did that a couple of times then went back to 3.3. It works but I don't feel like I'm protected.

Manually hexedit your key from orig.bin into the 4.2a firmware.

[OriginalCompGeek]

Original posted updated with more solid facts.

[HSDEMONZ]

^ added as moderator.

[HaZe303]

Anyone with LG drive having this issue yet??

Ps. Thx everyone for doing such fast and good jobs on this issue!!

[OriginalCompGeek]

There seem to be a few sporadic Hitachi issues, much less often than the Samsung.  If you have a Hitachi, chances are you'll be alright.

[OriginalCompGeek]

QUOTE(TigerHawk @ Oct 31 2006, 06:12 PM)

Originally MS25 Samsung Drive, flashed with 4.1A by way of Make41A.bat
System works after updating. NTSC

If it means anything, I unplugged my network cable immediately after it restarted and the startup animation stuttered. I wasn't able to recreate this stutter by restarting. Maybe random but it might be significant.

I left mine plugged in and it stuttered.  I think it's just the update being applied.

[OriginalCompGeek]

QUOTE(Techmaster @ Oct 31 2006, 06:18 PM)

MS28 works with 4.0 as well.  I just tested it.  Not sure about MS25, but I don't see why it wouldn't work as well.

I have refrained from tying a specific drive to a specific firmware giving a specific error, because there are no solid lines in that area.

4.1+ contains some extra read-blocking features that 4.0- does not (See Xtreme 4.1 readme).  I can't recommend flashing to 4.0 or below.  There are success stories with just about every version of the firmware.