Print

[badmonkey]

QUOTE(haris2887 @ Oct 31 2006, 08:18 AM)

i just want to know if anyone who has an ms25 with 4.1 or 4.2 got this error ?

   It's not an ms28, so no.

[schouwenberg]

Any news with the hitachi/lg drive ?

yes, that they are all working fine

[haris2887]

yeah....
ms 25 users are safe wiith 4.1 or 4.2........
so just have the latest Fw before you usgrade.....
and if you do get error 66 then just flash back to orignal and they reflash the hacked fw it works 100%...

[yedimaster]

QUOTE(Zydroid @ Oct 31 2006, 05:18 PM)

I have a feeling that some users get error 66 while others don't is because some have a premium with HDD and some dont, please post if you have HDD or not and if you had error 66 or not.

Mmmmh, this is my scenario:

MFG Dec-2005
DVD drive model: Samsung
Original Firware version: MS25
Hacked firmware version: xtreme 4.2b
How you modded: manually hex edited 4000-4400
Region: NTSC
Succesful Update: No. Got E66. Premium with hard drive attached.

Switched to 4.1b. Still E66
Switched to 3.2 - It's working

Used a second MS25 drive with Xtreme 3.2 worked
Flashed this MS25 with 4.2b - Didn't work
Flash back to Xtreme 3.2 and worked

After getting the E66 error, I turned off the console and opened it.  Switched the MS25(X4.2b) for the MS25(X3.2), turned the console and when it booted, it asked for the Hard drive to be attached to continue.  Then, turned off and attached the Hard drive and it booted normally.  Swiched the to the original ms25(X4.2b) and E66.

----------- My second console ---

Unopened console MFG Feb-2006
DVD drive model: Samsung
Original Firware version: Probably MS25
Hacked firmware version: Original untouched
How you modded: Untouched
Region: NTSC
Succesful Update: Yes, using memory card

[Mastadon69]

MFG: Didn't look
DVD drive model: Samsung
Original Firware version: MS25
Hacked firmware version: xtreme 4.1a
How you modded: manually hex edited 4000-4400
Region: NTSC
Succesful Update: Yep, using live

[Fraudster]

Hi All...

my best guess with this is that ms have introduced some kind of cross-reference check with regards to the firmware...

here's my findings



From what i can see this is due to a firmware mis-match...

I've been playing around with 2 xbox's tonight...

Both of them had samsung drives... 1 was ms28 and 1 was ms25 both had the corresponding stickers on them to PROOVE IT.

The one that was ms25 i first flashed with xtreme 3.0... worked fine and i then flashed with xtreme 3.3 worked fine... this is because both of these hacked firmwares are based on ms25 which was the drives original firmware... ithen tried xtreme 4.1 didnt work... and xtreme 4.2 didnt work... thats because this firmware is based on ms28 code

i think microsoft have basically introduced some kind of software or tool that cross checks the firmware with what the drive was originally and if its a differant version then it wont allow the console to boot.

[OriginalCompGeek]

QUOTE(Fraudster @ Oct 31 2006, 05:37 PM)

Hi All...

my best guess with this is that ms have introduced some kind of cross-reference check with regards to the firmware...

here's my findings
From what i can see this is due to a firmware mis-match...

I've been playing around with 2 xbox's tonight...

Both of them had samsung drives... 1 was ms28 and 1 was ms25 both had the corresponding stickers on them to PROOVE IT.

The one that was ms25 i first flashed with xtreme 3.0... worked fine and i then flashed with xtreme 3.3 worked fine... this is because both of these hacked firmwares are based on ms25 which was the drives original firmware... ithen tried xtreme 4.1 didnt work... and xtreme 4.2 didnt work... thats because this firmware is based on ms28 code

i think microsoft have basically introduced some kind of software or tool that cross checks the firmware with what the drive was originally and if its a differant version then it wont allow the console to boot.

I don't think this can be correct, though.  Many people, including me, have MS25's flashed with 4.x and had/have no issues.

[Mastadon69]

QUOTE

I don't think this can be correct, though. Many people, including me, have MS25's flashed with 4.x and had/have no issues.

I just posted what my drive is and how I updated. My MS25 drive with 4.1a FW works just fine...manually hexed.



Can someone answer this...Why would there be a difference between manually hexediting and using X360SAM, don't both still put the exact same bytes on the FW?

[lonsdale]

i dotn wanna double post but here seems a bette rplace for my problem...thnx in advance..

ok..here im at.......

i had firmware 3.3 on a samsung ms28...i updated from microsoft...got the E66 error....
i have put back the orig firmware with the 10 seconds trick and the command: mtkflash /w m orig.bin

that worked.....

but now after resetting my pc and xbox360....the red light (xboxpower botton)is still flashing...what went wrong? +...what are my next steps to get it to firmware 4.2?...

thnx in advance.....

[OriginalCompGeek]

QUOTE(Mastadon69 @ Oct 31 2006, 05:50 PM)

I just posted what my drive is and how I updated. My MS25 drive with 4.1a FW works just fine...manually hexed.
Can someone answer this...Why would there be a difference between manually hexediting and using X360SAM, don't both still put the exact same bytes on the FW?

They should, there doesn't seem to be any logic to it, though there must be somewhere.  Hopefully we will figure out what the connection is between the failures and successes before too long.

The only consistent pattern I've seen is that manually edited firmware seems to work, though there currently is no pattern that indicates why.

[Techmaster]

This is an important post, because I have yet to see anyone report on this combination!

MFG: July-ish 2006
DVD drive model: Samsung
Original Firware version: MS28
Hacked firmware version: xtreme 4.0a
How you modded: Used X360SAM and verified with hex editor, was okay!
Region: NTSC
Succesful Update: Yes!



Therefore, everybody has been saying 4.1+ works on MS28, you can CHANGE that to 4.0+!  

[Matt_Tracy]

QUOTE(Techmaster @ Oct 31 2006, 05:16 PM)

This is an important post, because I have yet to see anyone report on this combination!

MFG: July-ish 2006
DVD drive model: Samsung
Original Firware version: MS28
Hacked firmware version: xtreme 4.0a
How you modded: Used X360SAM and verified with hex editor, was okay!
Region: NTSC
Succesful Update: Yes!
Therefore, everybody has been saying 4.1+ works on MS28, you can CHANGE that to 4.0+!  

I love you.

I've an identical setup (4.0b, but MS28 + X360SAM + NTSC). I've been playing offline all day, not wanting to risk it/update to 4.2b w/o having to.

[thisisglen]

My information:

MFG: 2006/02/03
DVD drive model: Samsung
Original Firware version: MS25
Hacked firmware version: xtreme 4.2A
How you modded: used maximus toolbox version 1 "360FwTb.exe" to change the key
Region: PAL AUS
Succesful Update: Yes!

Firmware history - Orig -> V1 -> V3 -> V3.3 -> V4.2A

[Techmaster]

QUOTE(Matt_Tracy @ Nov 1 2006, 12:30 AM)

I love you.

I've an identical setup (4.0b, but MS28 + X360SAM + NTSC). I've been playing offline all day, not wanting to risk it/update to 4.2b w/o having to.

I agree, these MS28's are a nightmare to flash...I got mine to work once, and I was not looking forward to having to do it again.  But I just did it about 30mins ago, and it worked fine.  So I say go for it, and report back if it worked.  It should, seeing as it worked for me...

[Penfoldian]

QUOTE(mr-smith @ Oct 31 2006, 10:45 PM)

"...he only other option is software in the update for the samsung drive is conflicting with incorrect based firmware. This could be due to the HD dvd add-on compatibility.

It seems strange that those with ms25 and ms28 who flashed to the same ms based extreme firmware seem to be not having any E66 errors..."

i prefer your comment here, this makes more sense than anything i have read on this forum, the e66 error is to random, and we are over thinking m$' strategy on the matter, what ever happpened to "it is what it is"
this update had nothing to do with hacked firmwares at all, it just happened to be that a part of the update conflicted with some drives due to the fact that the update needed to update a few things on the drive anyway.

such as

• Optionally disable notifications from Xbox Live while watching DVD movies.
• Improved support for audio streams on incorrectly authored DVDs.
• Better handling of unreadable discs.
• Updated count-down timer.
• HD DVD player support.
• Added zoom support for non-anamorphic content.
• Added support to Family Settings to block Unrated Content
• Improved support for DVD insertion while playing a video file.

And to bring some more attention to the obvious..."Better handling of unreadable discs"

Why must we assume this is an attempt to block firmware?


Again this is why I will always say all firmware talk should be banned or limited.