Commodore4eva's Xtreme firmware 4.2A/B Rev.1 for TS-H943 Xbox 360 Options

[Xbox-Scene]

Commodore4eva's Xtreme firmware 4.2A/B Rev.1 for TS-H943 Xbox 360 Posted by XanTium | November 6 23:19 EST

Commodore4eva just released a new firmware for Toshiba-Samsung TS-H943 Xbox 360 drives: [QUOTE] What's new/fixed: (v4.2 rev1) Updated firmware and Make files for Error 66 swapped drives/motherboards from Hitachi XBox 360 and for MS25 consoles manufactured around/after end of May/start of June 2006. There is no change for drives already running Xtreme 4.2x Technical details: Fall update 2006 included DVD Drive version lockdown on consoles manufactured around end of May/start of June 2006. These consoles are now locked to the version of DVD drive that came with the console. If the DVD drive is different than original drive, Error 66 will be displayed. The response of the Atapi Inquiry command is compared to the stored original drive response to achieve this. (Thanx to DeViLs360 for initial find. Smiley Consoles manufactured before end of May 2006 do not perform this comparison. Only MS25 drives affected by Error 66 with Xtreme 4.x should use the Make file for MS25. Changes have also been made to the resulting Hitachi/MS25 reporting firmware to make them more similar to their original firmwares. To use the updated Make files (only if getting Error 66), just copy your existing Samsung firmware to the extracted directory and rename it to orig.bin. Then run the corresponding Make file for your Original drive. This will create the modified X42a.bin/x42b.bin. [/QUOTE] Official Site: xboxhacker.net Download: n/a (May be Illegal under DMCA/EUCD)

[MetalRampage]

Hey, good stuff, doesn't apply to us Hitachi-LG owners, but this issue didn't apply to us in the first place.

Anyway, great job on the fix!

MR

[brywalker]

Wow. The Hitachi is good for something now? I remember when the FW mods first came out and we were left in the cold for so long....

Now all we need is stealth media and the foot will be on the other hand!

[modman360]

so, should this be applied to all drives i do from now on, just incase? Even if they havent had the fall update yet, incase?

[bongmaster420]

good work c4e lets put another notch up there for us sammy owners lol kool stuff hope homebrew happens soons lol hint hint lol

[joshwaan2k]

Hi guys

I'm currently using a MS25 samsung drive and have firmware 3.3, if I update to this lastest firmware
will the lastest MS update work?

I just don't want to stuff me xbox up

This post has been edited by joshwaan2k: Nov 7 2006, 08:10 AM

[rodpad]

Wait, so C4E's saying that any console that was manufactured before May 2006 will be 100% ok to update with ANY configuration without fear of Error 66?

[sh4dowd4ncer]

Wait, so C4E's saying that any console that was manufactured before May 2006 will be 100% ok to update with ANY configuration without fear of Error 66?

Yeah, i'd be glad if this is true....

meaning even if the console's drive has been flashed with any version of firmware, or has been swapped from a hitachi to a samsung or vice versa, as long as the console is manufactured before a certain point of time, applying the fall update would never give any error 66 whatsoever...

Please anyone, do confirm these facts...

[SCSI]

Wait, so C4E's saying that any console that was manufactured before May 2006 will be 100% ok to update with ANY configuration without fear of Error 66?

It seems so. I have a newly bought xbox360 made on 05-19-2006 with a MS25 made on March 2006 and did the fall update. I then flashed the FW with Xtreme firmware 4.2A/B (NOT rev.1) and didn't get the Error 66. Next I will try and swap my Hitachi 47DJ to see if I get Error 66.

This post has been edited by SCSI: Nov 7 2006, 12:24 PM

[ArkitekT]

Sounds as if MS really is not able to do much about gathering info on consoles with modified dvd firmware, due to the fact that they are using a marriage theory between the motherboard and drive to report an E66? However it maybe possible for them to gather info about what errors have occurred on what consoles if they have a log that reports history of errors? This is pure speculation on my part.

[bonsc2]

Wait, so C4E's saying that any console that was manufactured before May 2006 will be 100% ok to update with ANY configuration without fear of Error 66?

How do you tell when your 360 as made

[stevenh78]

How do you tell when your 360 as made

manufacture date on the back of console above serial number

[Obveron]

It would be nice if the E66 database showed manufacturing date, to confirm this find.
I hope if there is anyone with E66, and an older system, they will speak up.

I wonder whats preventing the older systems from being locked to the original drives?

C4E sounds very convinced that this is fact, but proof that the older systems are invulnerable to being locked to a drive would be nice.

This post has been edited by Obveron: Nov 7 2006, 02:40 PM

[JUANVAN]

What he is saying is for People who swapped drives from the HI to the TS after the certain manufac. Date will now NOT have the E66 Error.

This is b/c, I guess, once M$ knew they were getting hammered, they started accually gathering that data before they shipped to customers. Unlike the old ones where they thought they were to Good for 4EVA.

Good work!!!

[OriginalCompGeek]

Mine was an MS25 made in march that has no problems with the 4.1a firmware and the dash update.