Topic: Xbox Live Update (Read 1466 times)

steddyman · « **Reply #75 on:** October 31, 2006, 05:12:00 AM »

I'm finding this very suspicous. Why would reverting to the stock firmware fix it?

It sounds like MS has patched the frimware itself and it is this that is failling. Perhaps they didn't understand every firmware combination and on some drives this causes a dead firmware. Maybe thats why reflashing works. What happens if you reflash to the same firmware as what is currently failing or dump the firmware after the update and compare?

Maybe they are getting the drive to report its patched status, but then just recording that on your account but not actioning anything currently. I guess they would need to reflash the drives to do this. Also I wonder if it makes any difference if you have a backup in at the time you perform the Dashboard Update?

If I was MS I would record the modded status, but not do anything for at least 30 days. Everyone is bound to have their modded 360s disconnected from Xbox Live until they are sure there are no problems. If they changed it right away, everyone would just wait for a patch before reconnecting.

Steddyman

dekker7 · « **Reply #76 on:** October 31, 2006, 05:20:00 AM »

If i reflash my drive with 4.2 i have nou 3.3 with e66 can i play then safety on live with original games? And with Copied games(STEALT)

mcding82 · « **Reply #77 on:** October 31, 2006, 05:23:00 AM »

QUOTE(dekker7 @ Oct 31 2006, 12:27 PM)

If i reflash my drive with 4.2 i have nou 3.3 with e66 can i play then safety on live with original games? And with Copied games(STEALT)

We dont no yet give it a try and tell us your results

the soul poet · « **Reply #78 on:** October 31, 2006, 05:40:00 AM »

I can confirm, a Samsung MS28 with 4.2a firmware works perfectly with the update

(for how long)

Speed1000 · « **Reply #79 on:** October 31, 2006, 05:40:00 AM »

I could not resist and updated my dash with the ms25 and 3.2 firmware. Everthing went 100% with the update. There must be a conflict with Ms28 and early versions of the firmware. But it is good news that people are unbricking there systems by updating firmware on the ms28.

Pups · « **Reply #80 on:** October 31, 2006, 05:49:00 AM »

Hey Guys

I got a very big problem.
Im so pissed of with that.
I updated my new Box,this one has NO FW HACK or chip.
After the update the Box rebootet.
Now i got E71 and the led right down is red.
Whats going on with this?
Sorry for my english hope u understand my problem :/

EDIT:I got a Samsung Drive with MS25 ORIG FW.

ob110k · « **Reply #81 on:** October 31, 2006, 05:53:00 AM »

Sammy MS25 3.2 works fine post-update.

There has to be a common thread with the E66ers here. Perhaps they manually updated or grabbed a slightly different range from their hex editors... i dunno... something's going on.

And is it me, or were all those number there before at the bottom of the system info page on the dash?

Maybe they were... or maybe part of this update is to simply make detecting firmware easier for future banning. I think the E66 error is a side effect and not some scheme to brick. If they wanted to shut you down entirely they could, but that doesn't seem to be the case.

gabrielconnor · « **Reply #82 on:** October 31, 2006, 06:06:00 AM »

I have a ms25 Samsung flashed with xtreme 3.3 . From what I've read so far it seems that I should be ok running the dashboard update. Could someone with a similar format please confirm this? I'm at work right now and I would really like to play live when I get home

badmonkey · « **Reply #83 on:** October 31, 2006, 06:07:00 AM »

QUOTE(ob110k @ Oct 31 2006, 08:00 AM)

Sammy MS25 3.2 works fine post-update.

There has to be a common thread with the E66ers here. Perhaps they manually updated or grabbed a slightly different range from their hex editors... i dunno... something's going on.

Common thread:

MS28 (with anything other than orig or 4.1+) = e66

Already established in this very topic.

.

IcemaN22 · « **Reply #84 on:** October 31, 2006, 06:09:00 AM »

Have nobody tried Hitachi-LG with firmware: Birdy 2,2 with the mediapatch?
I have that and im not sure if that is safe

Please answear!

haris2887 · « **Reply #85 on:** October 31, 2006, 06:11:00 AM »

has anyone got this error with an ms25 and 4.2 FW....
from what i understand ithe problem is that....
ppl who have ms28 must have either 4.1 or 4.2 installed because these are the only FW based on the ms28 code.....
so there is the incompatibility issue for ya if you have a ms28 with a ms25 based FW you will get tis error.....
so ms28 users do use anything but 4.1 or 4.2.....

i just want to know if anyone who has an ms25 with 4.1 or 4.2 got this error

?

purepwnage12560 · « **Reply #86 on:** October 31, 2006, 06:12:00 AM »

yea i can confirm my friend just mailed me bitching at me over AIM that he just updated and got the E66 we live in USA i cant confirm on mine because my xbox 360 is dead i have to go get a new one today but he has confirmed he updated and then got the E66

deltop · « **Reply #87 on:** October 31, 2006, 06:17:00 AM »

QUOTE(haris2887 @ Oct 31 2006, 03:18 PM)

i just want to know if anyone who has an ms25 with 4.1 or 4.2 got this error

?

PAL box, ms25 with 4.1a working fine here.

schouwenberg · « **Reply #88 on:** October 31, 2006, 06:18:00 AM »

I also got the E71 error with the red right-down led blinking for 3 seconds.
I rebooted, and no more problems at all.
Everything works fine.

I have samsing drive, from januari, so I think 25,
and I have the very first xtreme-proper firmware, I don't know the version number.
it;s not into the nfo file of it.

Canard-WC · « **Reply #89 on:** October 31, 2006, 06:20:00 AM »

Any news with the hitachi/lg drive ?

edit : upgrade in progress on my pal hitachi 47d, i'll tell you in a few mins...

Author Topic: Xbox Live Update (Read 1466 times)