Dec 19 2004, 06:51 PM
So i've been playing on live for a long time now, and just the other day my xbox wasn't connecting to my modem (no PC/Activity light), did the connection troubleshooting and I got the No IP found message. Since I was trying to access live through my dashboard to get to account management, i rebooted box to try again, only to find that damn screen with error 21. I haven't been able to fix this problem please help!
My Xbox: version 1.3, stock hdd, bios, everything else. aladdin 64 advance mod with on or off option. only one dashboard: original m$. Everything was working fine, this just happened out of no where. If you need any other information to help please ask and i'll tell you.
Dec 19 2004, 07:18 PM
error 21, thats an odd error, according to the xbox error codes explainded : "21 - anywhere - This error says that the machine was booted to display a error, basically someone told the machine to reboot (or launch a xbe) with this flag, and the error code just means its been rebooted by the flag" I have experienced this error before when i was tinkering with the tHc dashboard, i changed something and got this error since that was the dashboard i had the bios launch. So i would guess that somehow you currupted your m$ dash. I hope you have a back up of your C:\ drive, because i would suggest reformatting your C:\ drive and then ftping a back up of the C:\ drive when it worked back to your xbox and see if that work. If you dont have a working back up of your C:\ drive, i believe that slayers 2.6 has a back up of a C:\ drive on there, i'm not sure though, its worth a shot.
Dec 19 2004, 08:59 PM
already ahead of you on that, with slayers 2.6, i formatted C: and then did the M$ Dash inst/repair option, everything should work. i also installed slayers evox (just on c, not full rebuild) and evox loads with mod on, and i can launch m$ dash from there, but with mod off it should load M$ dash as well should it not? hdd is locked and everything.
Dec 19 2004, 10:03 PM
Yes, it should load the m$ dash with the chip off if you did the C:\ restoration thing with slayers. And if it loads through evox with the chip on, then there should also be no problem. Give it a try.
Dec 19 2004, 10:59 PM
oops sorry, didnt mention that thats what I did and it still doesnt work
Dec 20 2004, 12:30 AM
Really? So the M$ dashboard loads with the chip enabled through evox right? But not when you turn the chip off? Well, the onlyother thing i can think of is that: 1) slayers didnt work because i have heard of cases where the dashboard supplied with slayers isnt compatable with some xboxs. or 2) you m$ bios is messed up and you need to reflash your tsop with another m$ bios.
Dec 23 2004, 03:40 AM
hmm still havent fixed the problem i would really appreciate some help
Dec 23 2004, 07:15 AM
Dec 23 2004, 07:18 AM
21 is due to a signing error or missing/bad files in the dashbaord
sicne you have Live you must have a Live game or two, get a newer one and go to the Live option on it, it should update the dashbaord automativcally
Dec 23 2004, 07:31 AM
cant do that man, modem cant connect to xbox therefor no xbox live connection for the dashboard. i've tried the m$ dash repair option in slayers 2.6, still no luck, im gonna use a router to ftp in and replace my c: files with someone elses whos m$ dashboard works
Dec 23 2004, 07:32 AM
you dont need th enet connection, the games can update the dashbaord off the disc
Dec 23 2004, 07:33 AM
i'll try that with rainbow six 3 rite now, i have halo2 and have been trying to connect with it recently, no luck
Dec 23 2004, 07:39 AM
ok tried with many live enabled games, went to the xbox live option and it asked me for my account, then tried to connect, no dashboard updating whatsoever. i dont think its anything with the dashboard because i can load the m$ dashbaord thru evox, but it wont boot up with modchip enabled, hdd is locked, all xbe's are named properly
Dec 23 2004, 07:36 PM
Dec 23 2004, 07:59 PM
Error 21 [QUOTE]Typically means you're missin[QUOTE]g .xip files on your c: drive, or you have .xip's from a different (wrong) dashboard version. To fix simply restore a complete backup of the c: drive.[/QUOTE]
[/QUOTE] i dont think its anything with the dashboard[/QUOTE]
I still do. the explanation of the error code earlier on this thread is not quite right.
When you did the rebuild with Slayers did you format and rebuild the drive.
I don't understand the bit where you said
[QUOTE]it wont boot up with modchip enabled[/QUOTE]
How did you get evox to load then?.
Dec 23 2004, 08:56 PM
sorry i meant disabled, heres what happenes...
boot with mod on: slayers 2.6 evox loads up
boot with mod off: error 21
i can load the m$ dashboard through evox, so how can there be problems with it if it loads like that?
hdd is locked, never messed with bios, modded with aladin 64 advance
Dec 23 2004, 08:58 PM
well when xips and stuff get edited the dashboard can be resigned to work with those xips, however since this isnt an official MS signiture it wont run on an unmodded xbox (or with modchip disabled)
Dec 23 2004, 10:32 PM
hmmm so how do i solve my problem? im gonna try to ftp into my xbox today and put someone else's c: drive into mine, couldnt do it before because no router
Dec 23 2004, 11:07 PM
QUOTE(peckerdude @ Dec 23 2004, 04:35 PM)
im gonna try to ftp into my xbox today and put someone else's c: drive into mine
yeah, thast pretty much all you can do at this point
Dec 24 2004, 04:31 AM
update: ok i've narrowed it down to a problem with the ethernet port, since I cant ftp into my xbox. not a software problem, i figure the when i boot without mod, xbox bios detects problem and shows me that screen.
Dec 24 2004, 04:51 AM
another thing, ive looked on google and someone said they're ethernet port stopped working after a storm, so maybe a power surge fried it. when i was hooking up my modem before it stopped working, i got a pretty hurtiing shock, so i must've caused a small surge and fried my ethernet port, will i have to get a completely new one?
Jan 5 2005, 05:19 AM
Error 21....what a coincidence... my Xbox (completely unmodded) was making a funny noise the other day (like a fan hitting something it shouldn't be...) and then it stopped at now it won't boot to the dashboard. It will play xbox games, it will play DvDs, it will play Xbox live, but it WON'T boot to the xbox dashboard. Everytime I boot it up without a disc, it gives me the green screen of death with Error 21 in the corner. I took apart my xbox (v 1.0) and noticed that the fan that cools that chip (I think the CPU is the big one without the fan, so what is that chip anyway) had stopped working (fan blades separated from fan casing). I was able to reassemble it, and the fan works, but I still can't boot to the dashboard. Any suggestions?? I think I may need to chip my xbox to fix this problem, perhaps I can reload the dashboard from someone elses backup. And I will spend the $150 that i would have otherwise spent on a new Xbox, on 3 new games, which in the end will give M$ a higher profit margin...so this modding could actually be beneficial to M$.
Jan 5 2005, 05:30 PM
It sounds like your hard drive died. That would explain the whole situation. Also, if you want to update to the newest xbox live... simply unplug your ethernet cable incase it starts working
. Boot modded and then in file manager in avalaunch or whatever boot up dashupdate.xbe off of one of your live discs. This will upgrade you to the newest live dash and will work with your kernel.
I know you'll argue about the hard drive dying since you swapped and the problem continued... but if your fan is not hitting anything but you heard a grinding and your dash won't load... it's your hard drive doing the grinding.
Jan 7 2005, 12:34 AM
Ok I think you might be onto something with the hard drive not sure what exactly though. I just got through reloading dash via slayer evox disk on a drive that was giving me a error 16. After i booted up it gives me a code 21. Just happened I'll update if i find something new.
Jan 7 2005, 01:58 AM
Update: After installing a new drive into the formentioned machine, she now works like a charm. I did notice one strange thing however, I was using a xenium ICE chip + Slayers for process of locking etc. The chip gave me a strange error when going into disk options, I've never worked on a 1.1 before but i know the chips software is fine. I don't know if this was part of the original problem or not.
As far as the error 21 goes i do believe it may be some sort of bad sector on the HDD. Because the new HDD was prepared in the same way. I think i might try to examine the failing drive via PC. Perhaps some partition magic will be able to clean it up or at least find the cause of all our woes. Hope this was helpful.
Jan 7 2005, 06:17 AM
Why are you posting under multiple accounts?
Jan 8 2005, 03:46 AM
i'm not must be some problem with the forums
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here