Print

[adamscybot]

Wow! This might be a fix already. Can soemone try this?

[PoksterG]

So for MS25 owners who have 4.x, this fix is an alternative to downgrading to 3.3?  This would be great if it works, because I still believe in Firmgard!!  

[jameswalter]

QUOTE(PoksterG @ Nov 2 2006, 08:56 AM)

So for MS25 owners who have 4.x, this fix is an alternative to downgrading to 3.3?  This would be great if it works, because I still believe in Firmgard!!  

Problem is that MS25 isn't supposed to have firmguard.  So if MS can now detect what drive you should have, they can tell if they should be able to read the firmware.

[Exobex]

I feel an X360SAM 0.5 coming on...

[Looouky]

http://forums.xbox-s...howtopic=559651 Try this please!

[evil666]

I am getting more confirmations of this working from other bords i have posted this on.

QUOTE

I've got a Samsung 25 ms, after I flashed it with Xtreme 4.2a I got Error 66, with your fix everything works! You are my hero

QUOTE

Wow man it works good! Simple Trick.. cool

Thank you man!

[pacmeoff]

I have just installed the fall update via xbox live with my hitachi drive installed flashed with opa2.3 stealth fw. All worked fine after reboot.  I then inserted my dvd key into a samsung m28 drive flashed with 4.2a and the x360 still works fine on & off line.

So the update must place an item on the hdd or cache if it detects a drive/fw problem during the update otherwise if it checks eveytime surely I would have received the error e66 after replacing drive.

Anyone managed to update with a different make of dvd drive from the original installed drive without getting the e66 problem.

Thanks

[Looouky]

Good stuff, anyone try with the factory reset or just the hex edit. If the factory reset works then it could be a solution for ppl who did the drive swap.

[OriginalCompGeek]

Does this in any way affect the functionality of the firmware?  I want to make sure there isn't a drawback before  I recommend it.

[Antman1]

A friend of mine did this and it was a great fix.  great Job!   I personally did not have this issue with mine but he did and this took care of it.  Thanks

[Exobex]

Can someone confirm that older firmwares such as ms21 also stores the ID in the same locations ($202e and $20d4) please?

[Shaner99]

QUOTE(thisisglen @ Nov 2 2006, 11:34 PM)

Good work. I have an ms25 with 4.2A which i never got E66 on, but it's good to know that this problem is sorted for the moment anyway.

I do find it very interesting though that MS can detect some ms25's with 4.x given that with the firmgaurd (apparently) they can't read any of the firmware... but obviously if this fixes it, then they can read at least some parts.

Thing is, the update affected unmodded 360s also, so who really knows.

[tigerk]

This trick works, It took all of about 2 seconds to do. No more E66 for me is a good thing.

[stowelly]

right so now in theory if iw as gonna put a replacement hitachi in my samsung machine i would just have to edit  the hitachi to ms25 ?

[ZakMcRofl]

While this has been mentioned before in this thread I want to emphazise it again:

WARNING
This fix can help Microsoft determine that you have hacked your firmware!
WARNING

Why? Because, as was pointed out before, you now have a "ms25" drive that is unflashable. If M$ does a check on "drive is updateable & drive is ms25" you get caught.
On the other hand, if you use extreme 3.3 you only lack firmguard. That means that only if a flash is forced by M$ at some point you'll have a problem, however that is considered pretty unlikely. The "broken samsung technique" would probably still work then so you're not losing anything by going with 3.3.