Print

[justinjas]

Figured I'd post mine as well.  I'm running an enigmah modded xbox original hd.

X: 0000-000D
Y: 00A8-6800
Z: 8015-190D

I've acutally been in this situation before.  When I originally got my xbox live beta disc, I couldn't log into the servers.  I would get the xbox live not found error.  After trying it plugged directly into my cable modem and still not working I called tech support.  I was slightly worried that they had already banned my serial number because of a wal-mart switch I had done.  Never this less I gave them my info and error message.  The tech support guy seemed very strange after I gave him the error code, hard to explain but when I asked him what it ment he wouldn't tell me at first and then after more questioning he gave me a bs answer that my xbox couldn't talk to my ISP!  Anyways after about a week I could connect fine without changing any of my configuration and I signed up for an account.  If anyone is interested this was the code I got then:

X: 0000-F021
Y: 00C2-01E4
Z: 8015-1917

I also did some packet sniffing to see what was going on with my xbox now that I can't logon like everyone else.  My xbox seems to login as it gets back a response from the ms server that contains my xbox serial number.  I wish I would have done some sniffing when my xbox could login fine so I would have something to compare it to.  Oh well hope this info helps someone out.

[DEEZNUTZ]

1.00.4920.01
X: 0000-F001
Y: 00A8-6820
Z: 8015-190D

I have an X-ecuter (v1) chip installed with no BIOS or HDD mods.
I installed a switch.....disabled mod and tried to connect through the dash.....NOTHING!!!!

[WintrXtrem]

i have a matrix mod chip with evox 2.5.  here are my numbers:

1.00.4920.01
X: 0000-000D
Y: 00A8-6800
Z: 8015-190D

about 3 days ago i could only connect when the chip was disabled.  as of either yesterday or the day before i cannot connect at all- dash or in game.

[[AD]]

I have Enigmah Final..... XBL Beta on Pal Machine.

X: 0000-F001
Y: 00A8-6860
Z: 8015-1918

UL:0kb                    DL:0kb
L:0ms (0ms)             P:0/0


Could these codes not say what address the mod is?? so you get a different code for what mod is in the xbox. Or if you have changed the HD/DVD

( Dont Flame me. Im no programmer, Just a Thought =D )

[FSHoCKZ]

QUOTE (XBOB LIVE @ Nov 14 2002, 07:00 PM)

okay virgin xbox 1.00.4920.1 x:0000-f001 y:00a8-6860 z:8015-1917 niether can connect from dashboard, bothe retail version

                                    mines the same as your virgin xbox. with Xodus (EvoX2.5 err blue evox) and a 60gig HD.

[XBOB LIVE]

[lucasz]

You guys are all idiots.  If you change around your networking configuration, these numbers change dramatically.  This crap has nothing to do with detecting your Xbox BIOS, etc.

It's probably used so the guys at support can check your network configuration without you thinking they're going to hack you or invade your privacy.

[lucasz]

I think that some of us have our serial number banned.  Others are just being prevented from connecting from a modded system.

Maybe this depends on your system version or whether your HD has been tampered with?

Please post everything about your system history and the system version (Look at the Xbox settings--System Info and report the K and D numbers).

If you can't connect, even with the original HD and the mod chip removed/disabled, please indicate this.

If you can connect with the mod chip disabled, please say so.

[XBOB LIVE]

is anyones different from this 1.00.4920.01
??

[DKo5]

)
Reflashed TSOP w/ EvoX 2.5 noani.colormod.ybox.err (used an Enigmah to do it)
30GB Maxtor HDD
EvoX boots from C: (ybox)

Xbox Live beta worked fine last time I tried on Friday night. Then I heard on Monday morning about the "scare" so I didn't try again until today when I had a chance to test w/ MechAssault. No connection, instantly tells me that I can't connect. I am going to be reflashing to the retail BIOS and then putting in an X-ecutor w/ a switch.

Here's hoping to a workaround!  

[guboogi]

hrm, now mine has seemed to change from:

1.00.4920.01
X: 0400 - F001
Y: 00A8 - 6820
Z: 8015 - 190D


to:

1.00.4920.01
X: 0400-F001
Y: 00A8-6860
Z: 8015-1917

no clue why, though.  and i'm still the only one with a "0400" in their X value.  has anyone a clue what these things are yet?

[Friggin Joe]

Modded with Enigmah 29 wire.

1.00.4920.01

X: 0000-000D
Y: 00A8-4800
Z: 0000-0000

I can't ping TGS.XBOXLIVE.COM or AS.XBOXLIVE.COM

Yet I connect in the Dashboard (not the games though).

[Duece]

If I ping or trace the connection to the addresses listed here on this forum (TGS.XBOXLIVE.COM) I get destination net unreachable.  either with a tracert or ping....from to different ISPs. Maybe it is just server problems??

[XBOB LIVE]

QUOTE (lucasz @ Nov 15 2002, 01:22 AM)

You guys are all idiots.  If you change around your networking configuration, these numbers change dramatically.  This crap has nothing to do with detecting your Xbox BIOS, etc. It's probably used so the guys at support can check your network configuration without you thinking they're going to hack you or invade your privacy.

                                    its intersting that you say that seeing as how the y: are pretty much the same for all of us no matter what region or setup we have.  im not saying it has anything to do with modchip detection, but calling us ALL idots is going to get you no where.

[Zander]

Pinging is irrelevant.

They can block ICMP echoes but let data packets through.

A few of us (including me) have done packet sniffs and can see that AS.XBOXLIVE.COM IS UP! So is TGS btw.

Z