PDA

View Full Version : Do not download Dashboard update if you have a Toshiba-Samsung drives DVD



optimalkiller
01-11-2006, 01:21 AM
Fall Update - E66 Error with some modified Toshiba-Samsung drives *Updated*
>> It looks like some people get an E66 (hardware failure) when trying to reboot their console after the Xbox 360 Fall Dashboard Update. So far it does not look like it's something MS did on purpose to stop modified DVD firmwares as it only happens with some specific configurations, they do NOT ban the console/gamertag from LIVE and it's easy to solve. It's probably a compatibility issue between the new Xbox360 OS/kernel build and some combinations of DVD drives and modified firmwares.

From our data (see this thread (http://forums.xbox-scene.com/index.php?showtopic=559081) and this thread (http://forums.xbox-scene.com/index.php?showtopic=559060)) it looks like it only happens on some Xbox360 consoles with a combination of a Toshiba-Samsung TS-H943 DVD drive (mostly MS28, but we get reports of problems with some MS25 aswell) and some hacked firmwares (below v4.1 on MS28?, MS25 seems to work with older 3.x FWs and manually patched (key) v4.x).
As far as we know consoles with Hitachi-LG drives seem totally unaffected (any version, any FW) and all works fine after the update.

So this is easy to solve, just reflash your Toshiba-Samsung drive with the original FW (100% working solution - we suggest you this until we get all details) or upgrade to C4E's latest TS FW (v4.2 (manual key patch might be required for MS25 ... some MS25 users reported that downgrading to v3.3 or lower helped for them)).

Microsoft is NOT banning your gamertag/console on LIVE for this (afaik), but of course ... going on LIVE with a modified FW is always at your own risk (it's against the LIVE terms&conds). Someday MS could start banning consoles/gamertags with modified FWs and if they're smart they first collect info for 1month or 2 and then ban everyone at once ;)

Also note that this story is NOT related with that news about Xbox LIVE banning that was published by xboxic.com (To view links or images in this forum your post count must be 1 or greater. You currently have 0 posts. re-posted on many other blogs incl. slashdot (http://hardware.slashdot.org/article.pl?sid=06/10/30/202227)) 2-3 days ago. We didn't post about that news here on x-scene, simply because it's not true. heh. MS is banning if you don't behave on LIVE, they might ban on some modified content (like super cars in PGR3) ... but they are not mass banning for modified firmwares (yet). Of course, like I said above, they could start doing this at anytime (and they might be logging stuff already, who knows) ... even if stealth firmwares and (partially) stealth media could make it harder for them.

Here's what Team Xecuter (To view links or images in this forum your post count must be 1 or greater. You currently have 0 posts. wrote about the E66-issue:


There have been many reports of peoples Xbox 360's dying after the fall update when they have a flashed drive.

One of our friends had this problem so he brought his Xbox to us for analysis. Here are some facts.
1. Samsung MS28 Drive
2. Flashed with Xtreme v3.3
3. E66 error after Fall Update
4. Red lights / No boot to dash

We dumped his firmware and compared to his original X33.bin flash - MD5 was the same and of course that meant his drivekey was correct too.

We then simply converted his X33.bin to the new X42a.bin (Xtreme v4.2 Fast Boot Mode as Default) and reflashed (and for those that may ask using a VIA 6421L card and Xecuter Connectivity Kit v2 with a seperate Molex PSU (wouldnt work with PC power - had to power up the drive first before PC - of course you could use power from the 360 itself too if you wish)

The Xbox 360 now boots just fine - both offline and on live with originals and backups.

Conclusion?
That there was no evidence of the drive being reflashed by the fall update & the live account / MAC address was NOT banned. Also that there was some kind of incompatibility with the new update and the older hacked firmware. Maybe this was accidental or part of the master plan. Who knows?

If others could give input on their own experiences then that would help a lot of people. We are not yet sure if this causes any problems with MS25 or Hitachi drives - time will tell.

For now enough of the scaremongering. You can rescue your drive, although I feel sorry for those people who don't learn from sites like ours on how to do it yourself, as no doubt you'll have to go pay $80 or whatever to the local Joe Schmo who originally flashed your drive.

And of course, as always, use Xbox Live at your own risk if you are using a hacked console. If you ever kill your box or you get banned your cries will unfortunatley fall on deaf ears.

g3o
05-11-2006, 01:34 PM
That'a a bit dramatic, there's plenty of tosh/sam owners with the update and no problems at all.
I am one of them..

tinkertiler
05-11-2006, 02:40 PM
Microsoft has sorted the update out now as it was killing xbox 360s that had not even been flashed! If you had a flashed drive and you are now getting error code 66 reflash your drive back to original and then reflash to 4.2 firmware and everything will be ok again.

violentj
06-11-2006, 10:59 AM
the firmware was a problem due to a drive and revision check being implemented into the update-it seems folk who had put 4.2 onto there machines had no probs-but folk with ms28 who put lower than 4.0 on had basicaly downgraded there drive-which showed the error-the fix ms released was for error 71

the drive error throws up a error 66

morgyn
06-11-2006, 05:52 PM
The problem is only with m28 drives, if they are running the 3.3 firmware. the 3.3 firmware is based off the m25, and at some point the xbox makes a note of the revision of the firmware, and as this seems to go backwards the error is thrown.

You can easily restore your old firmware and your xbox will work again, but obviously uncracked. Upgrading to the 4.2 is the way forward after that.

The Hitachi drives aren't affected as its not a complete flash, just areas that are written over.

Lets hope this isn't going to be a common occurance.

marvinx
14-11-2006, 02:00 PM
Upadate to the new 4.2 before upgrading should sort all problems as this is based on m28.Due to the 360 looking to make sure not downgraded drive, this should be OK

Fraudster
18-11-2006, 11:04 PM
Yeah you will need to update to 4.2a report as ms25 and all of your issues should be resolved

thanks c4e - u da man

KoFi G
26-02-2007, 11:51 PM
update ok here done later date dec when fix was done I persume