See? My xbox doesn't get to the dash...It simply splashes a "needs service" screen right after the Flub animation and the eject will flash red...Sorry if I seem to be overlooking something, I just need some help.
don't worry about it... jsut update your Xenium to the latest verison first....
additionaly... that bios ISN'T a hacked bios... it is the origanal one.... just a reminder...
This post has been edited by EmperorPsiblade on Oct 9 2004, 10:30 PM
Thank you so much EmperorPsiblade, you are truly awsome, I'm glad you helped me 
I will upgrade to Xenius OS 2.0.1 later and tell you how it goes, I just was worried about what might happen if I don't set the clock from within MS DASH..I know it's not hacked
hehehe
Alrighty, updated to 2.0.1 fine but still the same error. All I want to know is this: Will it harm my xbox in any way if I just installed my X2 bios and load up evox? I just heard of horrible stories from people that failed to set their clock from the MS Dash..Please and thank you.
it shouldn't harm anything...
from
hereyou somehow corrupted you're retail bios image..
Hrmm...It worked perfectly fine before installing the chip (tested) and now it is corrupted (how can one corrupt a retail bios
)...hrmm well I guess I will follow ur advice and flash the chip with X2 4983.06 and try to install Evox! I hope this doesn't fux0r my xbox up
dropping a screw on the contacts and booting, grounding the D0 to a ground instead of the Xenium's d0 point.. etc...
Some early 1.0 xboxes don't display error numbers
Sounds to me like your HD is simply unlocked... or something similar.
As i said previously, early 1.0 xboxes don't display error numbers, they just have a general "Needs service" screen.
The clock issue is not important once you have XOS2.0.1 installed 
As far as I know, its virtually impossible to corrupt your TSOP without making a hardware modification to your xbox. Your eeprom is a different matter. But your eeprom is fine.
Seriously, you're probably just getting an error 5 or 6 or 13 or something, you should ignore the fact that you don't have an error number and start trying to fix your error. I'm betting its an unlocked HD.
Thank you guys so much. I will try locking the HDD via the xenium menu
thx.
Ok, I tried locking my hard drive but it won't. Within the Xenium menu it says as soon as I press the button that locking had failed. Now I tried to boot into the msdash one more time after that and then the flubber animation wnt and then the Xbox splash screen afterwards just sat there for a good 20 seconds before displaying a service messege/red flashing of eject.
I didn't drop a screw on a contact...I chose the correct d0 point (it wouldnt be working if I hadn't right?) and so far all I get is this...
Is your hard drive set as a slave?
If not it should be.
I'm not a complete newb either hehehe...but
It was never changed from factory settings. Worked fine before chip install, now it is unlocked. I know that it is unlocked but the xenium won't let me lock it from the disk tools.
As far as the cables being tight: I successfully backed up the eeprom and the toggle to "lock the xbox HDD" in the disk tools wouldn't be visible unless it saw an unlocked drive connected.
It is as if there is a big ass bug in 2.00-2.01 because on their official site there are dozens of this same report daily and the admins are giving generic answers that do not fix anything.
Seriously stick a jumper on it an set it to slave, your problem sounds alot like the one I had, it was solved when i switched it to slave from the default of cable select
have you also tried formatting it?
You might wanna stick it in your pc and use some fatx drivers to get the stuff of it
The easiest way to lock your hard disk is either using EvoX dashboard or using Slayers auto install disk. Both of these have options within the settings menu to lock and unlock a hard disk. Often you'll find you need to edit evox.ini in order to enable those commands in the menu by just removing the # characters at the beginning of each respective line. These lines should be easily found by looking for the words Lock and Unlock within the INI file.
I'm getting the exact same error message and my modded xbox worked fine for a few months beforehand. It's either a 1.0 or 1.1. I'm using evox.
I got the error message thursday night and I had been using the xbox that morning. There were no bumps or anything like that to the xbox in between my last play and the time of the error.
If anyone can help, that'd be awesome.
Thanks
I used the same chip and this might sound stupid but is it the same hard drive that the motherboard came with? I had a similar problem and that was the problem. I got that fixed and now I cant get live games to load! and I havent found the way to fix that problem. the only real reason you need to get to the ms dash that way is to play live games. you can just load the origional dash off of the evox dash to set the clock.