Print

[Fuzzy]

what? i understood you modded 5 boxes and you dont want them getting banned but i dont understand the rest.

[realdream]

Sorry for English

My box is v1.0 4034. HDD 100 Go, Evox 2.6  Eject trick.

XBL FRANCE
IP Manu
DNS auto

X : 0001 - 8005
Y: 00A8 - 6000
Z : 8015 - 190D

XBL FRANCE
ALL Auto

X: 0000 - F0001
Y: 00A8 - 6860
Z : 8015 - 190D

[Knightshado]

Hi Guys Here are my settings with matrix in mode3.  Brooklyn, NY

XBL with no connection problems, and not Banned.

X: 001C-F003
Y: 00A8-4800
Z: 0000-0000

[Fuzzy]

people i need more info than just ur chip and ur code. I need what country ur in do u thin ur banned, conneciton problems, any eeprom or other changes, ESPECIALLY IF YOUR BOX IS CONNECTIONG OR NOT. i thank you for what you have contributed but i really need more detailed posts.

[Icculus]

Hey fuzzy...front page news! Congrats man

[BlueMnky]

x:0000 - F001
y:00A8 - 4860
z:8015 - 1917

HomeBrew EvoX2.5 - Ybox/orange - External On/Off switch
USA
Not Banned - XBL Working
v1.0
Full Auto Setup
Original HDD
Cable Inet

[Fuzzy]

QUOTE (Icculus @ Dec 7 2002, 06:42 PM)

Hey fuzzy...front page news! Congrats man

                                    i couldnt believe it myself until i asked xantium about it (thanks again man)

[admiralj]

x:0000 - F001
y:00A8 - 4860
z:8015 - 1917

pcbioxx w/evox 2.5 on usa v1.0 xbox. (of course i disable the chip for live)
locked 120gb hdd.
DHCP enabled on live setup.
Live working 100%.
cable connection.

[Dools]

settings for both where IP: auto   DNS: auto   PPPOE:  default

i got my xbox last year when they came out and i live in the US. i couldn't play live so i took out my mod chip and left my 80gb hdd in there and i still couldn't connect to live. my code was:

X: 0000-F001
Y: 00C2-03C0
Z: 0000-0000

then i took out my hdd and replaced it with the regular one and my mod chip was still out and got the same error that it can't connect to xbox live and my code then was:

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

whats up with that? i can't play xbox live anymore, that sucks

[penguinofdoom564]

X: 0000-F001
Y: 00A8-4840
Z: 0000-0000

Xecuter (v1) with a switch (disabled...duh). Everything else on the box is virgin, no changes whatsoever. I've been connecting fine since day one. BTW, i'm in the US. Guess they didn't detect it at all. Keep up the great work fuzzy!

[ZPaul2Fresh8]

USA, Version1.0 (Nov01), 120G HDD, Matrix Mode4, EvoX 2.6 eject trick....

As of now I'm not sure if this info will be any help...
I had no problems with XBL during beta, but since the launch of live I've heard about people being banned so I never updated to the retail disc yet. I'm waiting to see what the fix will be. But anyhow here's my info without being connected and having beta(Don't think it matters with no connection!)

X 8000-0011
Y 0000-0000
Z 0000-0000

IP Manual and Auto are the same results
DNS Auto

Nice work so far, people like you make this community go 'round  

Maybe with some influencing I'll update the Retail and see what happens...

Oh yeah, I was running MotoGP Beta off HDD.

[emailer33]

well i hope mine help.  i'm running a matrix/xodus chip in always on mode, it's running the evox 2.6 ejectfix w/ red logo bios.  I have a router hooked up and the ports are open.  here's my codes:

1.00.4920.01   << dashboard version
X: 0000 - F001
Y: 008A - 0DE4
Z: 8015 - 1917


and it says no packets whatsoever were sent.

and i noticed realdream mention taht in the Y code A8 was common among banned membres, but mine as you see says 8A.  dunno if it means anything   .  hope this helped.

[Ius]

Ok, here's the numbers I got screwing around with it for ya fuzzy:
(sorry for the length, but hopefully they'll help)
I'm using a v1.0 with xecutor1, always been disabled for live. US, DSL, Not banned, everything works fine. Everything on my xbox should be factory with the chip off except some files on the HD.
In case it's relevant, I have my xbox hooked up to my LAN, my windows XP PC running as a router.
[EDIT - I pasted it wrong. I labled it auto IP, but pasted the manual. Here's the right numbers for auto]
IP Auto - DNS Auto - Working
And
IP Auto - DNS Manual - Working (gives same numbers):
X: 0000 - F001
Y: 00A8 - 4860
Z: 8015 - 1918

Manual IP - Auto DNS - working:
And
Manual IP - Manual DNS - working:
X: 0001 - 8005
Y: 00A8 - 4800
Z: 0000 - 0000
[/EDIT]
Here I screwed up the IP settings:
All Y and Z numbers were 0 here. I'm asuming it didn't get to the rest of the tests since it failed at the IP config.

Manual IP (set to conflict with my PC's) - Auto DNS - Not working:
X: 8000 - 0805

Manual IP (set to conflict with my PC's) - Manual DNS - Not working:
X: 8000 - 080D

Manual IP (gateway set wrong) - Auto DNS - Not working:
X: 8001 - 9005

Manual IP (gateway set wrong) - Manual DNS - Not working:

X:8000 - 100D
(Notice the 90 changed to 10. That would happen if X3.1 is 0 here and 1 in above. I had thought that bit had something to do with weather or not it could get a valid IP. *shrug* X2 changed too. Strange.)

Manual IP (Subnet mask set wrong) - Auto DNS - Not working:
X: 8001 - 8205

Manual IP (Subnet mask set wrong) - Manual DNS - Not working:
X: 8000 - 020D

Here I screwed up the DNS settings:

Manual IP - Manual DNS (set wrong) - Not working:
X: 0000 - 000D
Y: 008C - 0000
Z: 0000 - 274C

Auto IP - Manual DNS (set wrong) - Not working:
X: 0000 - F009
Y: 008C - 0060
Z: 0000 - 274C

Auto IP - Manual DNS (primary bad, secondary good) - Working:
And
Auto IP - Manual DNS (primary good, secondary bad) - Working:
X: 0000 - F009
Y: 00A8 - 4860
Z: 8015 - 1918

Here I just started throwing stuff at it to break it for more numbers
(Y's and Z's all 0's again)

Cable Not Connected:
X: 8000 - 0011

Crossover to hub (so it detected a cable, but it wasn't working) - Not working:
X: C000 - 4003

I just threw in a random IP that didn't match my network's - Not working:
X: 8001 - 8405

Note how all the 05's changed to 0D's when I changed to manual DNS settings up in the 'messing with IP settings' section. That would suggest that X4.5 indicates manual DNS settings. Also note though, that if everything's working, it doesn't seem to apply. If ONE DNS server is bad, but the other is good, it does still set that bit. So if that's correct, it only reports manual/auto DNS if there's some kind of failure.

There's my numbers and my thoughts. Good luck fuzzy.

-Ius

[Fuzzy]

wow that post was the shit, that will help a lot, i wish more people were as dedicated to helping as you.

[ZPaul2Fresh8]

I know you're trying to understand all the bits in each of the hex#, but how will you utlimately fix the banned Xboxes? How would you edit the 48 bytes? When you figure it out; will we need a hex generator program? You know, if your good to go just enter your exsisting hex#s and generate you a fix!? I don't know I just wanna write something since I'm bored of my Evox.ini editor already.

But WHEN exactly does Xbox Live ban users? I'm guessing with the Retail Update correct? I haven't update to retail yet so I'm unsure...

Hey fuzzy do you have MSN messenger?