Topic: Info & How To: Avoid/fix E66 Issues With Fall Dash Update (Read 762 times)

bourke · « **Reply #60 on:** November 01, 2006, 04:43:00 AM »

QUOTE(I'dkickurass@cod2 @ Nov 1 2006, 07:29 AM)

Yep got the E66 error when I downloaded the update this morning. I have a MS25 drive with 4.2A firmware. I flashed it back to original, worked fine, then I flashed it back to 4.2A, same error. Did that a couple of times then went back to 3.3. It works but I don't feel like I'm protected.

Sounds like the update checks whether or not it can 'see' your drive during the firmware installation - if it can't see your drive and KNOWS that it should (i.e. it knows that you have a MS25 not a MS28) then that could be it!

Can anyone confirm that early (2005 model) MS25 drives work with 4.x firmwares after the update?

TDB · « **Reply #61 on:** November 03, 2006, 07:30:00 AM »

Noob post here...

I have got the E66 after the update & have a Samsung TS-H943A F/W MS28 the problem being i got a company to flash the drive for me & they have said they do not have a backup of the orig.bin & said they will look at trying to fix it for me but will have to charge a standard fee + additional costs (im a mug for taking the easy option in the first place).

Am i screwed? or is there a way around this? i have all the gubbins here to re flash but without the original .bin from the drive i cannot see a way around this (i mean the drive key)

Any help would be great.

TIA

Obveron · « **Reply #62 on:** November 03, 2006, 07:33:00 AM »

Your unique hexkey should be retrievable from you existing 'hacked' firmware. I don't think you are screwed.

mattyv · « **Reply #63 on:** November 03, 2006, 07:35:00 AM »

QUOTE(TDB @ Nov 3 2006, 09:37 AM)

Noob post here...

I have got the E66 after the update & have a MS28 the problem being i got a company to flash the drive for me & they have said they do not have a backup of the orig.bin & said they will look at trying to fix it for me but will have to charge a standard fee + additional costs (im a mug for taking the easy option in the first place).

Am i screwed? or is there a way around this? i have all the gubbins here to re flash but without the original .bin from the drive i cannot see a way around this (i mean the drive key)

Any help would be great.

TIA

As long as the current flash has the correct key embedded, all you need to do is dump the FW, hex edit and copy the key into a stock MS28 FW bin.

Jozek · « **Reply #64 on:** November 03, 2006, 11:40:00 AM »

QUOTE(cerealkillajme @ Nov 1 2006, 02:35 PM)

Yeah you should be fine to update using either FW when updating, and both FWs should work fine after the update too.

But when I ' ve got 3.0, Can I update too?

bluefalcon · « **Reply #65 on:** November 03, 2006, 03:59:00 PM »

Anyone heard of E76? I bought a Premium Xbox near launch. Kept it and maybe did an update on the day i bought it, dont remember. Just got around to firmware hack a few days ago. It is a sammy ms25 and i put in 4.2b via extreme bootmaker and it worked fine. Played a few game backups and then decided to go online and do the fall update. It had an error after it finished and the tray was out. I powered down and rebooted, played a backup, and it worked. I went back online and it asked for another update. It took that update played a backup and went to sleep with internet unplugged from xbox. Now it is giving me E76, i might be mistaken but i thought i read E75 on the boot before that. If i have a backup in the drive it loads the world screen then goes to E76, lower right light blinking. If i do not have a disk in, it goes right to E76. I was able to bring the firmware back down to 3.3 and it still does the same thing. I have not tried leaving it at original firmware yet, that is next. Am i missing something really obvious here? Has anyone heard of E76? The forums say they do not know what it means. I am guessing that this is an offshoot of the E71 problem. Completely stumped.

Ready to go out and buy a new xbox360 core but i am afraid of bricking another one. I read in one forum that someone accidently updated there xbox 360 by plugging in the hard drive of an updated one. They said it just updated without asking.

It should be noted that i did my fall update during the time frame that microsoft was going to come out with a fix for the fall update but had not done so yet.

OriginalCompGeek · « **Reply #66 on:** November 03, 2006, 04:11:00 PM »

QUOTE(bluefalcon @ Nov 3 2006, 06:06 PM)

Anyone heard of E76? I bought a Premium Xbox near launch. Kept it and maybe did an update on the day i bought it, dont remember. Just got around to firmware hack a few days ago. It is a sammy ms25 and i put in 4.2b via extreme bootmaker and it worked fine. Played a few game backups and then decided to go online and do the fall update. It had an error after it finished and the tray was out. I powered down and rebooted, played a backup, and it worked. I went back online and it asked for another update. It took that update played a backup and went to sleep with internet unplugged from xbox. Now it is giving me E76, i might be mistaken but i thought i read E75 on the boot before that. If i have a backup in the drive it loads the world screen then goes to E76, lower right light blinking. If i do not have a disk in, it goes right to E76. I was able to bring the firmware back down to 3.3 and it still does the same thing. I have not tried leaving it at original firmware yet, that is next. Am i missing something really obvious here? Has anyone heard of E76? The forums say they do not know what it means. I am guessing that this is an offshoot of the E71 problem. Completely stumped.

Ready to go out and buy a new xbox360 core but i am afraid of bricking another one. I read in one forum that someone accidently updated there xbox 360 by plugging in the hard drive of an updated one. They said it just updated without asking.

It should be noted that i did my fall update during the time frame that microsoft was going to come out with a fix for the fall update but had not done so yet.

Well, first things first, try the original firmware and see what happens. We'll work from there.

Assi9 · « **Reply #67 on:** November 03, 2006, 08:03:00 PM »

Remember the days when you installed software and it asked "are you sure?" and when you got ready to flash something, YOU executed and rebooted? Do you remember why it was such a big deal? Because you had so much money into the machine, and wanted to actually use it.

Don't buy into the whole MS doesn't make money off the consoles crap. You bought a console, a hard drive, a network adapter, wireless controller, XBOX LIVE (and some upgrades and games), a cooling fan, a battery charger, a few games. So you bought some discs and backed up some games so you didn't have to rent them 2 or 3 times until you decided to buy them. If anyone is losing money, it's Blockbuster. But do they disable your ability to go back and rent more games or even buy something there? No that wouldnt make sense.

Microsoft has done the equivalent of the mafia going out and slashing tires on cars of everyone in a family because someone in it didn't pay back the loan. Disabling legitimate hardware, what a great way to boost sales of PS3s.

bluefalcon · « **Reply #68 on:** November 03, 2006, 10:53:00 PM »

Got a solution to my E76 Error - I had lower right red light flashing and E76 error no matter which firmware i had after the fall update (but not right after, the next day). I read in another forum That E76 code is for network error. I plugged in a network cable and booted my PGR3 Orig and it started working after over 2 days of hell.

Jozek · « **Reply #69 on:** November 04, 2006, 12:26:00 AM »

QUOTE(Jozek @ Nov 3 2006, 07:47 PM)

But when I ' ve got 3.0, Can I update too?

Who can ask to my question?

averian · « **Reply #70 on:** November 05, 2006, 07:38:00 PM »

Sometimes reflashing back to the original firmware isn't enough...when you have swapped drives!

I have your fix for those that swapped original Hitachi's for replacement Samsungs.

Story: Refurb Xbox with Samsung ms25 swapped in place of its original Hitachi 47DJ 3 months ago. Not even the stock original firmware would work on the Samsung ms25 after the update (e66).

THE FIX: Manual hexedit of Samsung ms25 firmware to replace mentions of TS-H943 with equivalent code from original Hitachi 47DJ firmware. (starts around $2020, be diligent here as there are some slight differences, use the Samsung's syntax). Now original edited Samsung firmware works, as should any edited xtreme firmware without any e66 error!

ewok666 · « **Reply #71 on:** November 05, 2006, 08:39:00 PM »

QUOTE(Assi9 @ Nov 4 2006, 03:58 AM)

I'm unplugged my network adapter until FW comes out that resolves all issues with all drives.

Looks like you've got a network cable for sale ;-)

Liquidslim · « **Reply #72 on:** November 07, 2006, 07:52:00 AM »

I have Xtreme v3.3 Samsung (M25).

Should I unplug DVD Drive then update or should I just update?

Thanks.

StayingOccupied · « **Reply #73 on:** November 07, 2006, 11:01:00 AM »

QUOTE(thetarget @ Nov 7 2006, 04:39 PM)

hi all is the update you are talking about the one that pops up soon as you connect your xbox to live
saying that you can not use live unless you download this update ?

Yes

I have a Samsung MS28/xtreme33 and i unhooked the dvd drive sata/power and updated. It worked fine, until i rehooked up the dvd drive then i got error 66. I'm attempting to reflash right now with xtrem42b. Will let you know how it turns out.

thetarget · « **Reply #74 on:** November 07, 2006, 12:04:00 PM »

thanks for the info

i have the ms25 xtreme 3.2 and updated with no problem and never removed the drive

Author Topic: Info & How To: Avoid/fix E66 Issues With Fall Dash Update (Read 762 times)