Print

[kingroach]

I didnt try any other firmware after error 66. Just flashed 4.2a with changed version number and worked.

[evil666]

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.

[angryxboxguy]

Ok.  Everyone is saying the if you have the ms25 drive you shouldn't use any v4+ firmware.  I already put 4.1b on and now I can't flash it back down.  The enable800 mode disk isn't working like the readme says it should.  I tried the whole powering down the unit and turning it back on thing with no luck.  Is there any other way to back down the firmware on this drive or is it fubar?

[Zappza]

This worked good for me

With 3.3 I couldn't open my drive, and with the original 4.2 I got E66.

Thanks a lot!

[pog0]

Do you have to dump your firmware again before editing? Or do you edit your existing hacked firmware then reflash?

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?