Post by: adamscybot on November 02, 2006, 08:51:00 AM
Post by: PoksterG on November 02, 2006, 09:49:00 AM
Post by: jameswalter on November 02, 2006, 10:07:00 AM
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.
Post by: Exobex on November 02, 2006, 10:15:00 AM
Post by: Looouky on November 02, 2006, 10:44:00 AM
Post by: evil666 on November 02, 2006, 11:38:00 AM
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 ;D
QUOTE
Wow man it works good! Simple Trick.. cool
Thank you man! ;D
Post by: pacmeoff on November 02, 2006, 12:23:00 PM
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
Post by: Looouky on November 02, 2006, 12:24:00 PM
Post by: OriginalCompGeek on November 02, 2006, 12:52:00 PM
Post by: Antman1 on November 02, 2006, 01:14:00 PM
Post by: Exobex on November 02, 2006, 03:10:00 PM
Post by: Shaner99 on November 02, 2006, 03:30:00 PM
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.
Post by: tigerk on November 02, 2006, 03:30:00 PM
Post by: stowelly on November 02, 2006, 03:52:00 PM
Post by: ZakMcRofl on November 02, 2006, 04:18:00 PM
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.
Post by: kingroach on November 02, 2006, 05:36:00 PM
Post by: evil666 on November 03, 2006, 07:10:00 AM
QUOTE(ZakMcRofl @ Nov 2 2006, 05:25 PM)
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.
True but MS isn't doing dumps yet. If they were we would have more then this issue on our hands.
Post by: angryxboxguy on November 13, 2006, 06:35:00 PM
Post by: Zappza on November 28, 2006, 01:33:00 PM
With 3.3 I couldn't open my drive, and with the original 4.2 I got E66.
Thanks a lot!
Post by: pog0 on December 12, 2006, 09:31:00 PM
I tried to reflash my drive with my orig.bin and my x42a.bin and MTKFlash just froze when I chose the drive number. Would this be due to the update?