| QUOTE (mjimi420 @ Nov 19 2004, 02:57 AM) |
| I replaced my hdd key with the stock hdd key that came with my xbox and updated the eeprom. I still can't sign into xbox live because now when xblive tries to connect i now get a communication error. Anyone else experience this problem? |
Regarding communication errors you might want to try the following.
I just modded a brand new xbox with Xenium ice and 120GB HDD.
Uploaded evox, XBMC and a few more apps and homebrew games.
Booted in evox and tested some of the apps/games.
Booted to M$ dash every thing was OK.
Tried to setup a new xbl account using a 2months free trial.
Connected to XBL just fine, started to download upgrade files, system rebooted after download. When back to M$ dash and tried to finish seting up account.
everytime i tried to connect to XBL my box locked up !!!.
Restored M$dash from previous back-up, started set-up process again, connect download upfdate files, reboot and ... locked-up again !!! Tried one more time just to be sure, same result !
I had all my apps on F: so C was"virgin", but e: was not !
Some of the homebrew apps/ games had created folders and files on E: . In particular I had a game folder on E (created by xbmc, in think)
Compared current content of E to backed-up content (prior to installing/running any new apps) removed what did not belong. Booted in M$ dash launched XBL and "VOILA" connected right away, completed my account set-up and went into live and I am still in it after 2 weeks (I do not have Halo2). Note that this box had never been connected to live before I did the mod and HDD upgrade.
To recap, i could connect just fine to XBL to download the XBL/M$ dash update files.
After Update files were downloaded, and the box rebooted as needed, I could not connect.After Cleaning my C: and E: from any "foreign" content I was able to connect just fine.
So i think that the new updated XBL/Xbdash files try to verify and convert the content of your C and E to the new version of XBL, if a file is found not "signed" by M$ or not supposed to be there the system hangs; and this happens even before you are connect to XBL, it is an internal check of C and E files.
Just my experience! Maybe worth trying to clean your C and E if you cant connect.