Post by: OriginalCompGeek on October 31, 2006, 05:19:00 AM
Current Stats as of Nov. 1 @ 11PM EST:
- 81.25% of drive updates completely successful with 4.0+ firmware
- 78 Drives had no problems
- 18 Drives required a firmware downgrade, a firmware reset to original, or would not work at all.
The problem seems to be completely random, and avoiding it seems to be a matter of luck more than anything. However, the best precautions would be:
- Make sure your drive is flashed to Xtreme 4.1/4.2
- Manually hex-edit your key into the firmware. Try to avoid using auto-flashers, etc.
- Completely disconnect your DVD-ROM from your 360 before booting up and updating (This includes the power cable, simply unplugging the SATA cable will cause your 360 to refuse to boot.)
- Option 1 - Flash back to original firmware, this works every time.
- Option 2 - Manually hex-edit your drive key into your modified firmware and flash that firmware. This seems to have a pretty good success rate.
- Option 3 - If you have an MS25 drive, try flashing to Xtreme 3.2-3.3. If you have an MS28 drive try 4.0-4.2. You can also simply try manually hexediting your drive key into 4.1/4.2, and then flashing your MS25. This is sometimes effective.
- If you can't get 4.1/4.2 firmware to work, try hex editing the firmware to make it read as MS25. The method can be found here.
Commodore4Eva has given us information what exactly E66 is HERE. It appears he may be right in his interperetation, but Microsoft's detection of different firmware is shaky at best as 80% of users have no issues whatsoever.
ABOUT E71:
E71 was apparently related, in most cases, to brand new consoles. Microsoft has patched the dash update and people should not be getting this error anymore.
SOME INFO: HERE
This E66 seems to be a very ineffective attempt by MS to stop modders.
I, myself, ran the dashboard update with my MS25 w/4.1a firmware connected and had no issues. There seems to be no logical pattern that causes one person to get the error, and another not to. If more news becomes available, the thread will be updated.
*Good Luck!*
This post has been edited by OriginalCompGeek: Nov 3 2006, 01:03 AM
Post by: charis_k on October 31, 2006, 05:24:00 AM
So 4.2 is the way to go..
We must not forget once again to THANK c4e (and the rest) for being AGAIN one step forward before MS!!!
Post by: OriginalCompGeek on October 31, 2006, 05:26:00 AM
This post has been edited by OriginalCompGeek: Oct 31 2006, 01:36 PM
Post by: charis_k on October 31, 2006, 05:41:00 AM
4.2 can help on open tray errors?
Though c4e told its the 1.29 fw of pioneer 111 doing this...
Post by: joe90 on October 31, 2006, 05:50:00 AM
NO-ONE is banned.. obviouly just a compatabilty issue, which IS fixable.
why do people love mass hysteria and panic.. (more to come before the midterms)
Post by: noikz on October 31, 2006, 05:57:00 AM
Post by: Chaval BR on October 31, 2006, 06:35:00 AM
QUOTE(OriginalCompGeek @ Oct 31 2006, 10:26 AM) 
IF YOU HAVE RUN INTO E66:
Simple, reflash your drive. Seems to have worked every time.
You mean...
Reflash with orig.bin, yes, it works...
What about reflash a drive with E66 with a newer (4.2) xtreme FW, works too?
Post by: liteon6x on October 31, 2006, 06:03:00 AM
thanks c4eva
Post by: haccord on October 31, 2006, 06:12:00 AM
Someone have been tried with a MS25 (firmware 1.0) ?
Regards
Post by: Mana on October 31, 2006, 06:17:00 AM
Post by: Canard-WC on October 31, 2006, 06:17:00 AM
Any news with the Hitachi/LG drive ? Seems thoses e66 bugs are juste compatibility issues, but I'd rather be sure before I apply this update ^^
Post by: purepwnage12560 on October 31, 2006, 06:20:00 AM
Post by: Vintersorg69 on October 31, 2006, 06:58:00 AM
QUOTE(purepwnage12560 @ Oct 31 2006, 02:27 PM)
my friend just ran into the e66 and he has MS25 samsung drive
modded? unmodded? what firmware?
Post by: Canard-WC on October 31, 2006, 06:28:00 AM
You can play on live and enjoy backups too
Post by: purepwnage12560 on October 31, 2006, 06:35:00 AM
Post by: loonyx on October 31, 2006, 06:56:00 AM
Post by: Kibe on October 31, 2006, 07:08:00 AM
QUOTE(loonyx @ Oct 31 2006, 02:03 PM) 
easy way to avoid any problems, unplug the dvd drive and update, works everytime on any 360 with no errors
Hey, didn't even knew it would boot without a DVD drive attached!
Will try that as soon as I get home!
Thanks for the hint!
Post by: kolpro on October 31, 2006, 07:18:00 AM
Thanks in advance
Post by: Bananas on October 31, 2006, 07:19:00 AM
QUOTE(loonyx @ Oct 31 2006, 02:03 PM)
easy way to avoid any problems, unplug the dvd drive and update, works everytime on any 360 with no errors
Nice! Might not have to flash it again then, just hope i don't burn too many 0800 coasters if i do have to re-flash it.
Post by: loonyx on October 31, 2006, 07:26:00 AM
Post by: antz1970 on October 31, 2006, 07:39:00 AM
QUOTE(loonyx @ Oct 31 2006, 04:33 PM)
unplug the drive completely from the 360, and power on and update. works fine
if this is the case then that means that ms is flashing something into the firmware!! , maybe someone needs to get a dump of an error66 firmware and compare to a non error 66 firmware(of the same type) and see if there are any differences between the 2
Post by: fakka on October 31, 2006, 08:03:00 AM
What would you recomend me to do...
* Update the box first before I flash
* Flash, then update
* Or wait with buying one until this thing blows over
?
Post by: Vintersorg69 on October 31, 2006, 08:09:00 AM
QUOTE(fakka @ Oct 31 2006, 04:10 PM)
LOL! I was about to buy one today and flash it.
What would you recomend me to do...
* Update the box first before I flash
* Flash, then update
* Or wait with buying one until this thing blows over
?
Buy know, buy the games you like, and have some fun.
And hack/flash the thing when there are more infos about security...
...if u have to!
If u don't care bout XBL, then buy it now and flash it w/ whatever works...
Post by: Trex666 on October 31, 2006, 08:09:00 AM
QUOTE(OriginalCompGeek @ Oct 31 2006, 12:26 PM)
HOW TO AVOIDProblems:
Samsung MS25 - Rarely seems to have issues, your safest bet is to have 4.1 or 4.2 firmware before you update.
Samsung MS28 - Seems to have issues a lot, though not always. Best bet is to update to Xtreme 4.1/4.2 firmware before updating.
Hitachi - Does not seem to be having issues.
IF YOU HAVE RUN INTO E66:
Simple, reflash your drive. Seems to have worked every time.
*There is absolutely NO reason to panic, if it happens to you it is easily fixable*
I'll need mods to edit this with new info if/when it becomes available.
QUOTE(noikz @ Oct 31 2006, 02:00 PM)
I already tried that before this thread was started.
I updated with 4.2a which gave me the E66 error. Flashed back to original, worked fine, re-flashed a freshly updated 4.2a, E66 again. Flashed to 3.3 and all working.
So the E66 error occurs when the update attempts to write to a 4.x xtreme firmware and fails?
Post by: Hinotori on October 31, 2006, 08:24:00 AM
Post by: OriginalCompGeek on October 31, 2006, 08:33:00 AM
I'd do some slight updates, but of course, I can't edit my post... I don't know if there's anything that can be done about this.
Post by: Bananas on October 31, 2006, 08:46:00 AM
Post by: NookularDeath on October 31, 2006, 08:54:00 AM
I seriously doubt the firmware is attempting to write to the DVD firmware.. that is highly risky on M$s part.. suppose you had a region wide power outage in mid upgrade and it bricked your system... M$ would get a class action lawsuit for bricking thousands consoles..
how many people have PAL and NTSC systems??
I upgraded both of my NTSC consoles which have a Hitachi and Samsung drives with the latest firmware respectively.. neither one got an error...
Post by: lordinfamouz on October 31, 2006, 10:07:00 AM
can anyone confirm..most likely someone with the ms28 drive who have done the above method
Post by: CreisoN on October 31, 2006, 10:18:00 AM
Read team-xecuter.com
Post by: smash_linux on October 31, 2006, 11:26:00 AM
- MS25 : ORIGINAL OK
- MS25 : 3.0 OK
- MS25 : 3.1 OK
- MS25 : 3.2 OK
- MS25 : 3.3 OK
- MS25 : 4.0a/b OK
- MS25 : 4.1a/b ERR66
- MS25 : 4.2a/b OK
- MS28 : ORIGINAL OK
- MS28 : 3.0 ERR66
- MS28 : 3.0 ERR66
- MS28 : 3.1 ERR66
- MS28 : 3.2 ERR66
- MS28 : 3.3 ERR66
- MS28 : 4.0a/b ERR66
- MS28 : 4.1a/b OK
- MS28 : 4.2a/b OK
Post by: blackwing on October 31, 2006, 11:39:00 AM
QUOTE(smash_linux @ Oct 31 2006, 07:33 PM)
I think this is right for now, anyone can prove that this is wrong?
- MS25 : ORIGINAL OK
- MS25 : 3.0 OK
- MS25 : 3.1 OK
- MS25 : 3.2 OK
- MS25 : 3.3 OK
- MS25 : 4.0a/b OK
- MS25 : 4.1a/b ERR66
- MS25 : 4.2a/b OK
- MS28 : ORIGINAL OK
- MS28 : 3.0 ERR66
- MS28 : 3.0 ERR66
- MS28 : 3.1 ERR66
- MS28 : 3.2 ERR66
- MS28 : 3.3 ERR66
- MS28 : 4.0a/b ERR66
- MS28 : 4.1a/b OK
- MS28 : 4.2a/b OK
Post by: smash_linux on October 31, 2006, 12:00:00 PM
Post by: alphanumeric303 on October 31, 2006, 12:28:00 PM
For those that updated and unplugged their drives, can you please post your firmware version and drive version.
On a side note: It still bugs me that people that havent even modded their boxes are getting the same error. I dont know if this is a good thing or bad. I still havent turned on my 360, and I will probably wait until there is more testing done.
Post by: OriginalCompGeek on October 31, 2006, 01:04:00 PM
Drive: MS25
Firmware: 4.1a, key inserted with the Xtreme included .bat
Drive Left Connected during update
Everything went perfectly smooth.
Post by: infidelity on October 31, 2006, 01:08:00 PM
This update DID NOT effect my flashed Hitachi.
Just wanted to share my findings.
Post by: OriginalCompGeek on October 31, 2006, 01:14:00 PM
QUOTE(vicfalc09 @ Oct 31 2006, 03:15 PM)
If a drive is not flashed yet do you reccomend flashing before or after the update.
I don't think it matters a whole lot.
Im not even sure what I'd do in the same situation. Might as well update first, I guess.
Post by: I'dkickurass@cod2 on October 31, 2006, 01:22:00 PM
Post by: OriginalCompGeek on October 31, 2006, 01:29:00 PM
QUOTE(I'dkickurass@cod2 @ Oct 31 2006, 03:29 PM)
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.
Manually hexedit your key from orig.bin into the 4.2a firmware.
Post by: OriginalCompGeek on October 31, 2006, 03:24:00 PM
Post by: HSDEMONZ on October 31, 2006, 03:36:00 PM
Post by: HaZe303 on October 31, 2006, 03:56:00 PM
Ps. Thx everyone for doing such fast and good jobs on this issue!!
Post by: OriginalCompGeek on October 31, 2006, 03:58:00 PM
Post by: OriginalCompGeek on October 31, 2006, 04:10:00 PM
QUOTE(TigerHawk @ Oct 31 2006, 06:12 PM)
Originally MS25 Samsung Drive, flashed with 4.1A by way of Make41A.bat
System works after updating. NTSC
If it means anything, I unplugged my network cable immediately after it restarted and the startup animation stuttered. I wasn't able to recreate this stutter by restarting. Maybe random but it might be significant.
I left mine plugged in and it stuttered. I think it's just the update being applied.
Post by: OriginalCompGeek on October 31, 2006, 04:18:00 PM
QUOTE(Techmaster @ Oct 31 2006, 06:18 PM)
MS28 works with 4.0 as well. I just tested it. Not sure about MS25, but I don't see why it wouldn't work as well.
I have refrained from tying a specific drive to a specific firmware giving a specific error, because there are no solid lines in that area.
4.1+ contains some extra read-blocking features that 4.0- does not (See Xtreme 4.1 readme). I can't recommend flashing to 4.0 or below. There are success stories with just about every version of the firmware.
Post by: biga55 on October 31, 2006, 04:41:00 PM
I bet I'll get the error if I update, as I've already read some others had errors with the old firmware.
Post by: purepwnage12560 on October 31, 2006, 04:46:00 PM
Post by: antz1970 on October 31, 2006, 04:53:00 PM
Post by: OriginalCompGeek on October 31, 2006, 04:59:00 PM
QUOTE(Dravor @ Oct 31 2006, 07:05 PM)
I'm willing to be a reflash of the dvd drive firmware causes something to clear in cmos on the board? It would almost make sense, sometime goes wrong with the update, something isn't cleared, and the firmware flash on the dvd drive simply causes the board to reset.
Now what really sucks is those with stock boxes who get these errors have to send them back in. Ouch.
Not quite, a good number of people still get the error when they flash back to original, and then back to modded firmware.
Post by: jxoxn21 on October 31, 2006, 05:31:00 PM
QUOTE(TigerHawk @ Oct 31 2006, 06:12 PM)
Originally MS25 Samsung Drive, flashed with 4.1A by way of Make41A.bat
System works after updating. NTSC
If it means anything, I unplugged my network cable immediately after it restarted and the startup animation stuttered. I wasn't able to recreate this stutter by restarting. Maybe random but it might be significant.
I just got home and updated:
Hitachi 47dj
xtreme 2.2
Updated, automatically restarted. I put in my backup of import tuner challenge. it started reading the cd, about 2 seconds later it studdered and the beginning animation studdered. I was unable to duplicate the error a second time. Not sure if this is relevent but i see other people are having the same issue. MY 2 CENTS
Post by: OriginalCompGeek on October 31, 2006, 05:43:00 PM
Post by: OriginalCompGeek on October 31, 2006, 06:13:00 PM
Maybe the new update checks to see if the firmware is readable to begin with, and if that changes gives you the error? Kinda' goin' out on a limb, but it's possible.
Post by: port443 on October 31, 2006, 08:11:00 PM
Have an Original or backup game disc in the drive then do the update. 100% no error 66
Done on multiple Xbox 360 configs. All 100%.......
Post by: boofie75 on October 31, 2006, 09:46:00 PM
Post by: TheDarkLord on October 31, 2006, 09:49:00 PM
QUOTE(smash_linux @ Oct 31 2006, 01:33 PM)
I think this is right for now, anyone can prove that this is wrong?
- MS25 : ORIGINAL OK
- MS25 : 3.0 OK
- MS25 : 3.1 OK
- MS25 : 3.2 OK
- MS25 : 3.3 OK
- MS25 : 4.0a/b OK
- MS25 : 4.1a/b ERR66
- MS25 : 4.2a/b OK
- MS28 : ORIGINAL OK
- MS28 : 3.0 ERR66
- MS28 : 3.0 ERR66
- MS28 : 3.1 ERR66
- MS28 : 3.2 ERR66
- MS28 : 3.3 ERR66
- MS28 : 4.0a/b ERR66
- MS28 : 4.1a/b OK
- MS28 : 4.2a/b OK
Well I have a TS MS28 with the 3.2 hacked firmware and it works fine, no error, no problems, everithing is fine.
Post by: jayb082 on October 31, 2006, 10:52:00 PM
Drive: Toshiba-Samsung
Firmware: Xtreme 3.0
SUCCESS! Updated perfectly fine, everything works like before!
Post by: Monty1157 on November 01, 2006, 01:24:00 AM
Original: Worked every time.
4.2a: E66
4.1a: E66
4.0a: E66
3.3: Working.
Don't ask me why it didn't like the stealthed firmware. But for whatever reason it just got plain upset. Booting with the drive plugged into the PC sata port did not cause an error, so it's deffo something to do with the drive in one way or another. I did try flashing the original firmware onto the drive, letting the 360 boot a couple of times, just in case M$ decided to play around with the original flash, re-read it from the drive, and re-patched this new original onto the above firmware. All met with the same results. Oh yeah, and I tried both KDX and X360SAM for patching in the keys. I did not try to manually patch the key. May attempt that with the latest firmware when I have a better day than yesterday. Getting it working was the up point for me last night.
If it could have went wrong, it did...... *sigh*
Post by: 360newbie360 on November 01, 2006, 02:41:00 AM
Have not updated yet..
Can someone confirm that updating without the DVD drive connected works?
If not I think it's better to wait for a while...
Post by: CreisoN on November 01, 2006, 03:59:00 AM
XBOX360 USA NTSC
Hitachi-LG 46D
FW-Maximus-Garyopa_XTRM-HITACHI_v2_3_Stealth_Rev2
PS:EVERYTHING VERY NORMAL UPDATE NICE AND CLEAR 100%
NEW DASH ALL WORKING GOOD
ON LIVE
GAMES EVERYTING TESTED
====================================================================
Post by: Obveron on November 01, 2006, 04:42:00 AM
Why does the ms25 work with 3.x firmware but ms28 doesnt?
Is it because the key is different?
Has anyone succesfully got a ms28 to work with a 3.x firmware (maybe with a different hex editing procedure)?
I know the solution is to update to 4.2, I'm just looking for speculation as to why the error.
Post by: bourke 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?
Post by: TDB on November 03, 2006, 07:30:00 AM
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
Post by: Obveron on November 03, 2006, 07:33:00 AM
Post by: mattyv 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.
Post by: Jozek 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?
Post by: bluefalcon on November 03, 2006, 03:59:00 PM
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.
Post by: OriginalCompGeek 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.
Post by: Assi9 on November 03, 2006, 08:03:00 PM
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.
Post by: bluefalcon on November 03, 2006, 10:53:00 PM
Post by: Jozek 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?
Post by: averian on November 05, 2006, 07:38:00 PM
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!
Post by: ewok666 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 ;-)
Post by: Liquidslim on November 07, 2006, 07:52:00 AM
Should I unplug DVD Drive then update or should I just update?
Thanks.
Post by: StayingOccupied 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.
Post by: thetarget on November 07, 2006, 12:04:00 PM
i have the ms25 xtreme 3.2 and updated with no problem and never removed the drive
Post by: Liquidslim on November 07, 2006, 12:54:00 PM
Will it be safe for me to do the fall update? (Should I unplug dvd drive or not?)
Thanks A Lot.
*Just want to be sure.
Post by: Daveychan on November 08, 2006, 06:26:00 PM
I have an MS25 Toshiba-Samsung flashed with Xtreme 3.2 (created by the X360SAM.EXE) and updated to the new desktop version with no problems. I did not remove my DVD connections.
(Tested and played my backups without any issues or hangs, including the latest game release, F.E.A.R.)
Post by: mcding82 on November 09, 2006, 01:34:00 PM
Post by: SNAAAKE on November 09, 2006, 02:59:00 PM
thanks in advance..DOODS !
btw, I did flash a ms25 drive yesterday with the updated x42b and everything working perfect, no E66 error.
Post by: diddyk on November 11, 2006, 03:35:00 PM
Thanks
Post by: dbl on November 19, 2006, 05:59:00 PM
Just modded a MS-25 with 4.2 xtreme FW.
Did the update before i flashed the DVD.
Now im getting E66 as i turned it on after the flash, wtf :/
And now it seems i have problems to get the old stored fw back into the drive, it just hangs at "port : 9e0, Master/Slave a0"
Bitchass shit :x ..can anyone give me some advise?
To get the old FW back its "mtkflash w /sata orig.bin ... right?
peace, and thanks in advance yo
Post by: sonny11 on November 20, 2006, 12:51:00 PM
I have a new xbox360 with HL drive 47DH Firmware.
I plan on flashing it with Max v2.3 r2
I don't have any plans on going on xboxlive..
My question is do I need to install this Fall update for the 360 to work correctly or can I just leave off firmware on it?
Post by: EMoNey1 on November 21, 2006, 02:32:00 PM
Thanks
Post by: EMoNey1 on November 21, 2006, 04:03:00 PM
Post by: OriginalCompGeek on November 21, 2006, 04:17:00 PM
QUOTE(dbl @ Nov 19 2006, 08:06 PM)
Hey..
Just modded a MS-25 with 4.2 xtreme FW.
Did the update before i flashed the DVD.
Now im getting E66 as i turned it on after the flash, wtf :/
And now it seems i have problems to get the old stored fw back into the drive, it just hangs at "port : 9e0, Master/Slave a0"
Bitchass shit :x ..can anyone give me some advise?
To get the old FW back its "mtkflash w /sata orig.bin ... right?
peace, and thanks in advance yo
chances are that a game will eventually include the update.
Post by: donrapello on December 15, 2006, 09:28:00 AM
QUOTE(eugenile @ Dec 4 2006, 10:21 AM)
I am having the exact same problem! It was fine flashing, then I get e66, and I try toi flash and it just hangs there.
well, i flashed one 360 with xtreme 4.2 and it went to e66 after that. ts-drive with ms25.
re-flashed with updated version of xtreme 4.2 and it's working just fine. just remember to use enable
0800-mode-disc if you have already flashed your drive.. you should understand that you aren't
able to read/write the firmware if 4.x xtreme is installed because the firmguard.. that's if you have read the readme.txt.
Post by: oldhouse on December 20, 2006, 10:38:00 AM