xboxscene.org forums

OG Xbox Forums => Xbox Online Gaming (Xbox Live, Xlink, and others) => Other Online Gaming Options (Gamespy, etc.) => Topic started by: opjose on November 16, 2002, 06:41:00 AM

Title: A Fix For Connectivity Issues.
Post by: opjose on November 16, 2002, 06:41:00 AM
Someone posted ths on xboxhacker.net

QUOTE

One of my modded xboxs was getting the infamous Xbox live not found error. After numerous calls to the very unhelpful desk with no fix. I decided to try a few things to get my box on live again. What eventually fixed it was snagging the serial number/online key/mac address from one of my virgin systems and placing it on the "banned" xbox. After which it hopped right on.

After my success I was wondering what would happen if I dumped the old eeprom back on there and I bet you can guess what happened. Xbox live not found. Perhaps someone smarter then me will come up with a better solution then snagging another eeprom from a non-banned box but for now that is what is working for me.



This is exactly as I surmised.

Note the machines are NOT being banned per-se, rather the servers are NOT replying to certain seemingly random serial numbers.

Title: A Fix For Connectivity Issues.
Post by: Satan00 on November 16, 2002, 06:46:00 AM
wow so they are blocking xboxes, those assholes! i'm surprised your xbox isnt anned yet opjose, maybe they know you're "special" smile.gif
Title: A Fix For Connectivity Issues.
Post by: pike-old on November 16, 2002, 06:51:00 AM
Swings and roundabouts...Live not found error on a MODDED box. Not found because he was 'banned', or just random?. If random, why????? and surely if he uses another serial/mac etc, on another box, he then has your 'random' 20% chance that that one is stuffed too!
Title: A Fix For Connectivity Issues.
Post by: pike-old on November 16, 2002, 06:55:00 AM

OP - OK, Ill play

I have 2 machines here


1. xecutor with switch  - Live not found
2. Xtender 1.1 no switch  - live found, but no connection to games (no switch, you see)

If you can tell me the procedure, I'll happily test this theory for the benefit of all....
Title: A Fix For Connectivity Issues.
Post by: opjose on November 16, 2002, 06:56:00 AM
QUOTE (Satan00 @ Nov 16 2002, 01:46 PM)
wow so they are blocking xboxes, those assholes! i'm surprised your xbox isnt anned yet opjose, maybe they know you're "special" smile.gif

                                    No this guy is using the term BANNING wrong.

It's an authentication issue as I've stated.

For some reason or another the servers are not replying to certain serial numbers and/or not recognizing their initial handshake packets as being "valid".

Since this applies to old and new systems, modded and unmodded, it indicates a bug, error, or overzealous setting problem on the authentication servers.

Hopefully it will be fixed. If not I'll bet we will see a utility to circumvent the problem soon based upon the "identity switch" working properly!

I'm convinced that MS DID NOT intend for the connectivity problem to happen as it did.


I'm also fully convinced that the mod chip detection "fix" was their real line of defense. It's also a pretty good solution all around for them. It doesn't block "valid" machines playing retail games. It also permits modded machines to work with a slight wink on their part, to the whole mod chip issue.


The Kerberos issue is a nightmare for them on the other hand. It's blocking both valid and non-valid, modded and non-modded systems. Someone ROYALLY screwed up.



Title: A Fix For Connectivity Issues.
Post by: Satan00 on November 16, 2002, 06:58:00 AM
i doubt if even thoes assholes are doing anything about this problem, it sure is taking a WHILE
Title: A Fix For Connectivity Issues.
Post by: opjose on November 16, 2002, 07:07:00 AM
QUOTE (pike @ Nov 16 2002, 01:55 PM)
OP - OK, Ill play

I have 2 machines here


1. xecutor with switch  - Live not found
2. Xtender 1.1 no switch  - live found, but no connection to games (no switch, you see)

If you can tell me the procedure, I'll happily test this theory for the benefit of all....

                                    Ok if the machines are IDENTICAL...

E.G. both are NTSC
Both have the SAME kernel REV.

BACKUP the eeprom by hitting the BACKUP command in EVOLUTION-X.

FTP the C:\BACKUP files down and COPY THEM into proper directories so you know which is which. DO NOT CONFUSE THEM!

Copy the EEPROM.BIN from the working machine to the non-working one's C:\ drive as C:\eeprom.bin

For safety have an Evolution-X boot disk handy to undo changes if you need to...

Now grab EEPROMagic V0.01.rar from the net.

Load the XBE to the C:\ drive and run it using boXplorer or Evolution-X itself.

It will again back up the current EEPROM as C:\BACKUPEEPROM.BIN and then burn the C:\eeprom.bin file. It will shut the machine down when done.

DO NOT turn it back on yet!

Remove the power and open the unit.

Take the drive from the OTHER machine and install it on the non-working one.

Remember since the non-working one assumes the "identity" of the working one, your LOCKED hard drive from the working one will now work on your non-working machine with the mod chip disabled!

Your old hard drive is locked for the old EEPROM contents so it will no longer work until you either unlock & relock it (after figuring out it's NEW password as per the tutorial) or you revert back to the original EEPROM.

However as a test, and to avoid a lot of hassles, moving the drive from the other machine will suffice.

Keep the old working machine OFF the network or cable modem.

Power up the "new" now working machine.

Voila it's FIXED!

Now you can either leave it this way or unlock the old drive and put it back into your other previously working unit.

Note: you will now be unable to have BOTH of these Xboxes connected to ANY network, LAN, or CABLE MODEM -AT THE SAME TIME!-

Of course you could reburn the non-working eeprom code into your switchless machine... heh.

This works.

Title: A Fix For Connectivity Issues.
Post by: opjose on November 16, 2002, 07:09:00 AM
QUOTE (silkweed @ Nov 16 2002, 01:56 PM)
My god!!! Please learn to read for understanding!!!!!!

                                    Who are you talking to?
Title: A Fix For Connectivity Issues.
Post by: opjose on November 16, 2002, 07:20:00 AM
QUOTE (pike @ Nov 16 2002, 02:14 PM)
Op - therein lies the problem. I have the mods fitted, but no evos etc. Fitted by a tech guy and left to their own devices. Suppose I could go through the procedure though, but it looks like a lot of work..

I'm sure, in the fullness of time a solution will be found.

Mind you, there is a REAL IRONY here. Through trying to stop modders, MS have shot themselves in the foot. Folk locked out on a unmodded box are gonna have to open it up in order to get it to work. They'll be 'borrowing' identities from other machines and causing chaos, when those other machines try to go online...

Mess, Disaster, CHAOS

                                    Re: IRONY

Yet another reason why this is a nightmare for them!
I really do not believe that this was intended.

They WANT to cut down on the number of returned machines if anything...

The mod chip detection code which is downloaded is another matter which was definitely intended.

Re: problem

What's the problem?

Create a bootable DVD with Evolution-X on it.

Use this to create the "backups" and FTP to, to make the changes.

Put boXplorer and EEPROMagic on the same disk with entries in the evox.ini file, and you are all set both to perform the "test" and undo the damage later.
Title: A Fix For Connectivity Issues.
Post by: ICEFuZiOn on November 16, 2002, 09:04:00 AM
Great Info...

You said this doesnt fix the connectivity problem in the Xbl settings though.
There is currently no fix for that as its on MS's Side. I still think my xbox is blocked, The last day I played was tuesday (note that was on the Beta).

Could someone answer me on this one?
People with the Beta....Did you recive a update when logging on to the retail games?I never logged into a retail game, does this matter?

So it all comes down to this, I need to wait till that Kurbose error is fixed and the xbl see's my machine bfor I should do any of this EPROM switching?
Like you said Opjose, a Blocked or non-Blocked from XBL machine should still see all Green in the Connection test?
Title: A Fix For Connectivity Issues.
Post by: teetu on November 16, 2002, 10:26:00 AM
tongue.gif
Title: A Fix For Connectivity Issues.
Post by: clifface on November 16, 2002, 10:36:00 AM
The way I see it is if you want to play on live anytime soon, get another xbox.  Everybody on here has been great and every few hours there is a new breakthrough but in the end we are still leaving up to MS to fix this on their servers.  Might be hours/days/weeks, who knows.  I myself am really starting to think getting another xbox would be quickest and easiest way to play online.
Title: A Fix For Connectivity Issues.
Post by: Cybersage on November 16, 2002, 10:57:00 AM
QUOTE ([AD] @ Nov 16 2002, 04:53 PM)
Is there no way of editing the Eprom? Like checking whats different in both Eproms and trying to match it on the none connecting one? or is it a serial number problem??

                                    Someone was/is working on the issue in IRC. I think soon well see some fixes. The problem is that people are going to go to wal-mart and get the serial # off that machine and take it back, just adding to MS's problem. Opjose said it best...MS shot themselves in the foot.


Cheers
Cybersage
Title: A Fix For Connectivity Issues.
Post by: pike-old on November 16, 2002, 12:46:00 PM

Well, I bit the bullet and bought another box. Live was on my memeory card. I plugged inthe machine, inserted the retail disk and bosh, connected, without having to setup or recover an account or ANYTHING. Weird.

BUT, I can tell you this. Looking at MOTOGP theres a lot changed on the front end from when i was in beta (adverts and stuff). Makes me think that blocked users are flagging up to the wrong/dead server as a result of changing from beta to retail (perhaps BEFORE the required 15th?)

Anyway, i now have 1 x box in an arcade cabinet playing dedicated MAME. One for homebrew applications, and one dedicated to online play....
Title: A Fix For Connectivity Issues.
Post by: Zander on November 16, 2002, 12:53:00 PM
QUOTE
BUT, I can tell you this. Looking at MOTOGP theres a lot changed on the front end from when i was in beta (adverts and stuff). Makes me think that blocked users are flagging up to the wrong/dead server as a result of changing from beta to retail (perhaps BEFORE the required 15th?)


This is the running theory, with one difference. I know I have the connection problem, "Xbox Live not found". I also know I tried to use the retail disc on the 14th, but I'm not 100% sure that has something to do with it. There are new xbox live users that are getting the same problem that never put in the retail disc before the beta.

I'm starting to lean more toward a server issue, like database corruption, or just plain data loss. Perhaps some serials were wiped from the database holding serials that are authorized to be used?

How about doing this...

Do a sniff with a known, non-working serial.

Do a sniff with a made-up, fake serial.

Do a sniff with a known working serial.

Find the differences. If a non-working and a completely made up serial (like say 000000000000) generate roughly the same packet sniff (broken down kerberos handshark) are the same, we MIGHT have something. Maybe nothing, but I'm running out of things to try.

It may be there is nothing we can do short of getting a new xbox or serial at this point without some sort of inkling from MS.

Thoughts opjose?

Z
Title: A Fix For Connectivity Issues.
Post by: Oger on November 16, 2002, 01:04:00 PM
Im not sure if this will help or not but ill share the info

Got live last night...took off EvoX to put on original Xboxdash

-signed up for new account and everything

-got the update from each game Whacked(demo) Fever(rented it) and MotoGP(demo)

- couldnt connect through the game to xbox live...but could "Connect to LIVE through the dashboard"

-phoned tech support waste of time said live doesnt launch for 6 more hours LOL

-But now this afternoon I went to try it cant connect to xbox live from the dashboard

so I dunno



Title: A Fix For Connectivity Issues.
Post by: slappynutz on November 16, 2002, 01:34:00 PM
Try this for now. It's the only thing I can think of working long-term (at least until MS really decides to get serious about banning modders).


http://xbox-scene.fx...b9dca276ba50dca
Title: A Fix For Connectivity Issues.
Post by: Zander on November 16, 2002, 01:39:00 PM
Interesting. I hope it's true, becuase for the not so sharp of you out there, that is GOOD news.

If it's true.

Z
Title: A Fix For Connectivity Issues.
Post by: andreo on November 16, 2002, 02:16:00 PM
QUOTE (pike @ Nov 16 2002, 02:46 PM)


Anyway, i now have 1 x box in an arcade cabinet playing dedicated MAME. One for homebrew applications, and one dedicated to online play....

                                    This is what I was planning on doing with Mame and a Xbox! Did you buy the cabinet from somewhere or did you make it yourself?
I want to make one but I don't want it to come out looking like sh*t. The ones you can buy are through the roof $1k plus in price.
Title: A Fix For Connectivity Issues.
Post by: heliXbox on November 16, 2002, 03:10:00 PM
rolleyes.gif

I have NOTHING on the drive, if I want to play MAME or a backup I boot from a DVD+RW.

Anyway, I was able to connect just fine last night.  Got in, played some Mechassault (bought) and called it a night.

Now today I get the XBL not found error.  Grrr.

Guess I'll have 2 boxes now.  It seems that a great deal of people out there are doing this.  I don't see MS intentinaly planning this since they take a financial hit on each box sold.  I'm just hoping that the servers are busy or something.  dry.gif
Title: A Fix For Connectivity Issues.
Post by: upstatenyguy22 on November 16, 2002, 03:18:00 PM
QUOTE (heliXbox @ Nov 16 2002, 10:10 PM)
Working last night, not working today.

I've got a Matrix in Mode 3 and a retail XBL kit...guess I wasn't cool enough for MS's beta testing  rolleyes.gif

I have NOTHING on the drive, if I want to play MAME or a backup I boot from a DVD+RW.

Anyway, I was able to connect just fine last night.  Got in, played some Mechassault (bought) and called it a night.

Now today I get the XBL not found error.  Grrr.

Guess I'll have 2 boxes now.  It seems that a great deal of people out there are doing this.  I don't see MS intentinaly planning this since they take a financial hit on each box sold.  I'm just hoping that the servers are busy or something.  dry.gif

                                    I'm in the same boat.  Matrix mode 3 with retail kit, on last night, could connect through the dask with chip on or off, all like opjose said.  Today, I've moved to the group1 problem - xbox live not found even though the dash.  I'm not heading out for a new box, though.
Title: A Fix For Connectivity Issues.
Post by: Oger on November 16, 2002, 03:52:00 PM
aaa sweet sweet

guess thats a bit better

but the help line in so horrible LOL
Title: A Fix For Connectivity Issues.
Post by: NIGHTBREED on November 16, 2002, 08:31:00 PM
BETA TESTERS...

If in the past you have logged on to XBL with the BETA=non retail version (before nov 15th) with the mod chip ON then M$ already have your serial/mac address #s, so on the 15th when they started the servers with the blocking/not responding authentication they ALREADY HAD YOUR INFORMATION. It was just a question of adding it to their databases.

This is just like DIRECT TV serial#s and all...

By the way don't you guys find it funny that M$ is in a way HACKING US...
We've been doing it for a long time and i think it's their turn...
Lets show them that the best minds are not on their payroll...

Cheers to all of the over 500 post (i don't know how you do it)
Title: A Fix For Connectivity Issues.
Post by: andreo on November 16, 2002, 08:45:00 PM
I bet that connectivity test had something to do with it. Us mod users should have been a little more careful during the beta tests. I think we were all lead to the slaughter house with the biggest grins on our faces.
Title: A Fix For Connectivity Issues.
Post by: clifface on November 16, 2002, 09:45:00 PM
I didn't do the connectivity test though.  I only played 1 game of nfl2k3 and about 5 games of whacked with my mod enabled.
Title: A Fix For Connectivity Issues.
Post by: Fuzzy on November 16, 2002, 09:59:00 PM
uhh.gif
Title: A Fix For Connectivity Issues.
Post by: opjose on November 16, 2002, 10:33:00 PM
QUOTE ([AD] @ Nov 16 2002, 04:53 PM)
( Im not a Coder, so this might be a tall order )

Is there no way of editing the Eprom? Like checking whats different in both Eproms and trying to match it on the none connecting one? or is it a serial number problem??

BTW this sounds cool so far... There is light at the end of the tunnel.

                                    Yes these sucesses do indicate a "light at the end of the tunnel" if MS fails to do anything about all of this.

It's easy to envision a utility to adjust your EEPROM and MAC address to fix all of this.
Title: A Fix For Connectivity Issues.
Post by: opjose on November 16, 2002, 10:34:00 PM
QUOTE (teetu @ Nov 16 2002, 05:26 PM)
Its cool that you can switch things around and it works, but this still isn't a "solution" since you have to use 2 xboxes- one of which was working previously.  If you have an umodded xbox lying around that works with xbox live- thats your solution right there! tongue.gif

                                    Yes and no. It's a POINTER to a possible solution.

At present it's only a workaround, but it does indeed work!

It also proves that this is NOT a mod chip issue at all!
Title: A Fix For Connectivity Issues.
Post by: opjose on November 16, 2002, 10:35:00 PM
QUOTE (eXpired @ Nov 16 2002, 07:25 PM)
I'm VERY glad we have found this fix, but let's be realistic here... it's pointless. Unless you have a certain attachment to your xbox's motherboard, why not just USE the other xbox? Swapping the HD and flashing the EEPPROM is pointless. =P It's a step in the right direction, though, and I would like to find out a way to modify JUST the serial number to work.

                                    The serial number and MAC need to be modified in UNISON.

Then the header (which is encrypted) must be adjusted.

Once done, you have a "new" xbox. Heh.
Title: A Fix For Connectivity Issues.
Post by: opjose on November 16, 2002, 10:38:00 PM
QUOTE (Zander @ Nov 16 2002, 07:53 PM)
QUOTE
BUT, I can tell you this. Looking at MOTOGP theres a lot changed on the front end from when i was in beta (adverts and stuff). Makes me think that blocked users are flagging up to the wrong/dead server as a result of changing from beta to retail (perhaps BEFORE the required 15th?)


This is the running theory, with one difference. I know I have the connection problem, "Xbox Live not found". I also know I tried to use the retail disc on the 14th, but I'm not 100% sure that has something to do with it. There are new xbox live users that are getting the same problem that never put in the retail disc before the beta.

I'm starting to lean more toward a server issue, like database corruption, or just plain data loss. Perhaps some serials were wiped from the database holding serials that are authorized to be used?

How about doing this...

Do a sniff with a known, non-working serial.

Do a sniff with a made-up, fake serial.

Do a sniff with a known working serial.

Find the differences. If a non-working and a completely made up serial (like say 000000000000) generate roughly the same packet sniff (broken down kerberos handshark) are the same, we MIGHT have something. Maybe nothing, but I'm running out of things to try.

It may be there is nothing we can do short of getting a new xbox or serial at this point without some sort of inkling from MS.

Thoughts opjose?

Z

                                    The second packet send back by the kerberos servers are where everything falls apart.

At this point if your Xbox gets a reply it is redirected to a second server which actually does the authentication.

Finally a third server is brought into play which acts as a DNS for subsequent communication.

A failing Xbox never hits the second server.

Oh, the second server has ALMOST the same IP as the first.
Title: A Fix For Connectivity Issues.
Post by: opjose on November 16, 2002, 10:41:00 PM
QUOTE (Fuzzy @ Nov 17 2002, 04:59 AM)
this is a reply from way back in the beginning, directed towards opjose, what if i dont wanna change my eeprom, is there any way around it? and just what the hell is a Kerberos  uhh.gif

                                    Someone will have to write a utility (not me) to modify the Xbox's serial number and mac address in "unison" and adjust the encrypted header correctly.

It would be vastly helpful to have a few consecutively numbered EEPROM dumps to verify that things were being coded and decodded properly.

Re: Kerberos

Consider a google search.
Title: A Fix For Connectivity Issues.
Post by: opjose on November 16, 2002, 10:43:00 PM
QUOTE (NIGHTBREED @ Nov 17 2002, 03:31 AM)
BETA TESTERS...

If in the past you have logged on to XBL with the BETA=non retail version (before nov 15th) with the mod chip ON then M$ already have your serial/mac address #s, so on the 15th when they started the servers with the blocking/not responding authentication they ALREADY HAD YOUR INFORMATION. It was just a question of adding it to their databases.

This is just like DIRECT TV serial#s and all...

By the way don't you guys find it funny that M$ is in a way HACKING US...
We've been doing it for a long time and i think it's their turn...
Lets show them that the best minds are not on their payroll...

Cheers to all of the over 500 post (i don't know how you do it)

                                    No this is all incorrect conjecture.

I've already proven this wrong.
Title: A Fix For Connectivity Issues.
Post by: NaughtyNu on November 16, 2002, 10:52:00 PM
QUOTE (NIGHTBREED @ Nov 17 2002, 03:31 AM)
This is just like DIRECT TV serial#s and all...

                                    Actually they just removed the old H card out of the stream smile.gif
Title: A Fix For Connectivity Issues.
Post by: opjose on November 16, 2002, 11:58:00 PM
QUOTE (clifface @ Nov 17 2002, 05:44 AM)
So, opjose what do you think the best solution is at this time?  Wait for MS to fix this or get another xbox?  I want to play on live but don't mind waiting a little while till this is straightened out, I just don't want to be waiting weeks.  Thank you for all your help and research.  MS should hire you biggrin.gif

                                    Heh,

The M-icrosoft techs have been blaming the ISP's all day on the forums.

It's funny to see the ISP's firing back that it's M-icrosoft's problems.

There are some REALLY long threads from people with non-modded xboxes dropping like flies from the service.

The ISP's are also talking about how they are not blocking ports and that they have even put the xboxes directly on the backbones just to test... heh.

Yeap it's a M-icrosoft problem.

I'd give it a few days to be sorted out though.
Title: A Fix For Connectivity Issues.
Post by: Questioner on November 17, 2002, 11:34:00 AM
deleted
Title: A Fix For Connectivity Issues.
Post by: gilbrt on November 17, 2002, 11:43:00 AM
Hello out there, I too have gotten the xbox not found error. I was a beta tester and have a matrix modded xbox, with ybox hack. I was able to connect to xbox live with no problem until. 11/16/02. I got the update(retail) disc from m$ and loaded it up on the 15th. Played mech assault and unreal tournament online. Something strange did happen when I went to eject the disc. The xbox turned off, then back on then off again, at the same time I could hear the dvd spinning up then stopping and spinning up again. It did this for a minute or so. I finally unplugged it, had to reset clock. After that incident, I was no longer able to connect to live.
I do agree that the problem is due to the serial # not being recognized or authenticated what ever terminolgy you want to use, but I don't believe it is by accident. M$ has more than likely detected mod chip and put serial # in database that will not allow access. The possibility that their snooping software erroneously reported non modded boxes as modded ones could explain why non modded boxes or experiencing the same error. I myself will not go and buy another xbox, I can play on gamespy or some other alternative until we come up with a solution for this obstacle.
Title: A Fix For Connectivity Issues.
Post by: pvwr on November 17, 2002, 03:09:00 PM
QUOTE
The reason you don't get a denied response back from the Kerberos authentication, is that it helps in hacking. No response is better as far as MS is concerned.


Good point. It helps on the confusion on trying to figure out what's going on. After all, this could be told as a "server issue".
Title: A Fix For Connectivity Issues.
Post by: angone54321 on November 17, 2002, 03:22:00 PM
sad.gif  sad.gif  sad.gif  sad.gif  sad.gif  sad.gif  sad.gif  sad.gif
Title: A Fix For Connectivity Issues.
Post by: dvdvideo on November 17, 2002, 04:49:00 PM
"MAC addresses are GLOBALLY UNIQUE ID's for a reason , and if you start changing your xbox ones willy nilly , then it will cause problems for people with proper unmoddded xboxes , who are just trying to use a service"

Except that if that did happen in mass, MS would actually be forced to turn off the ban.

What I don't get is why they banned the xbox machines, it seems a poor choice, since:

A: You can't play online with a mod chip no matter what anyhow.
B: You can't play a backup game online no matter what.

They could have just banned the Live accounts.    But they were trying to be smart, figured they didn't want to lose the potenetial monthly revenue from the live customers.  Force them to buy a new xbox seemed to be the right choice.    What they did not count on or think enough of:

A: People taking make thier moddded bannded systems to the stores.  (i.e cost MS money)
B: People selling thier banned xboxes, thus creating a group of unhappy new customer who can't log on.
C: People changing thier serial # thusly causing problems for legit customers.  
D: The cost involved in the machines that the mod chip owners buy.

I think just banning the live accounts that had a mod chip would havebeen a better choice for them.  That or just go with the modchip = no play, that would have worked.
Title: A Fix For Connectivity Issues.
Post by: PillMonster on November 17, 2002, 05:01:00 PM
READ THIS AND WEEP

http://www.gotmod.com/#0000000096

Title: A Fix For Connectivity Issues.
Post by: PillMonster on November 17, 2002, 05:40:00 PM
I am not trying to spoil the efforts of hackers at all, and in fact admire the hacking work that has been done on the xbox. You however, from your limited knowledge are not what I would consider to be a hacker.
Title: A Fix For Connectivity Issues.
Post by: Beantown on November 17, 2002, 10:45:00 PM
flamethrower.gif          pop.gif
Title: A Fix For Connectivity Issues.
Post by: opjose on November 17, 2002, 10:50:00 PM
QUOTE (dvdvideo @ Nov 17 2002, 11:49 PM)
"MAC addresses are GLOBALLY UNIQUE ID's for a reason , and if you start changing your xbox ones willy nilly , then it will cause problems for people with proper unmoddded xboxes , who are just trying to use a service"

Except that if that did happen in mass, MS would actually be forced to turn off the ban.

What I don't get is why they banned the xbox machines, it seems a poor choice, since:

A: You can't play online with a mod chip no matter what anyhow.
B: You can't play a backup game online no matter what.

They could have just banned the Live accounts.    But they were trying to be smart, figured they didn't want to lose the potenetial monthly revenue from the live customers.  Force them to buy a new xbox seemed to be the right choice.    What they did not count on or think enough of:

A: People taking make thier moddded bannded systems to the stores.  (i.e cost MS money)
B: People selling thier banned xboxes, thus creating a group of unhappy new customer who can't log on.
C: People changing thier serial # thusly causing problems for legit customers.  
D: The cost involved in the machines that the mod chip owners buy.

I think just banning the live accounts that had a mod chip would havebeen a better choice for them.  That or just go with the modchip = no play, that would have worked.

                                    Yeap, especially the last choice. This makes the most fiscal sense from their perspective.
Title: A Fix For Connectivity Issues.
Post by: opjose on November 17, 2002, 11:38:00 PM
While I remain unconvinced that the connectivity issues are related to mod chip detection at present... and there are a few juvenile flamers here  (you know how you are!)...

Let it not be said that I've endangered anyones prized posession through ANY assertion.



To that end please
HEAD THIS CAVEAT....


Until more is known, assume XBLive will CATCH your modded Xbox and ban you!

I'm not saying that this is indeed the case, but I am advising EVERYONE to err on this side of caution for your own sake, by assuming that this is true.
Title: A Fix For Connectivity Issues.
Post by: angone54321 on November 18, 2002, 12:34:00 AM
brywalker all the stuff u post is on assumption, cuz ur a quitter.

jpose said himself he has 2 virgin boxes that are banned, so how do u explain that brywalker? maybe they arnt banned and everything he is saying is true, did that ever cross ur mind?
Title: A Fix For Connectivity Issues.
Post by: PillMonster on November 18, 2002, 02:24:00 AM
What Opjose is saying now is "Don't use Live with a mod turned on" - I would say heed that advise. In fact, I would go further, and say don't go on live with a modified HD. Although I doubt it, it would be relatively easy for MS to change the update code to scan the HD...with privacy issues, I doubt they would do this. Personally, this is what I have done, I have one "special" box, one virgin box which I use for Live, and another which I'll probably give to my brother for xmas.
Title: A Fix For Connectivity Issues.
Post by: PillMonster on November 18, 2002, 02:52:00 AM
This is so not the case...here in the UK it could be deemed in breach of new laws...it is at present "shaky ground". MS could argue that scanning modchips helps its legitimate users, it couldn't really do this with the HD!
Title: A Fix For Connectivity Issues.
Post by: Zander on November 18, 2002, 10:33:00 AM
luma is right.

Changing your MAC, from a network standpoint will only break things on your local segment.

It's fine.

Z
Title: A Fix For Connectivity Issues.
Post by: dvdvideo on November 18, 2002, 11:47:00 AM
"This is so not the case...here in the UK it could be deemed in breach of new laws...it is at present "shaky ground". MS could argue that scanning modchips helps its legitimate users, it couldn't really do this with the HD! "

I don't know about UK laws, however, MS can argue the exact same thing,  that detecting the modded hard drive helps it's users.  
Also, they could run a script that doesn't invade anyone's privacy at all, just checks to see if the hard drive is the right size or # of files, or type of files, not the contents of the files at all.
Title: A Fix For Connectivity Issues.
Post by: prestige on November 18, 2002, 12:45:00 PM
So we have determined once and for all that flashing the eeprom with a working serial will fix things on a black listed box.  Here's my naive question: Can you not simply change the serial number that is clearly visible when you open the backed up bin with a hex editor?

Is there some kind of checksum issue or something preventing a hacked eeprom.bin from working?  I realize a solution this obvious must have been tried but what would happen?  Why would it not work?
Title: A Fix For Connectivity Issues.
Post by: Zander on November 18, 2002, 01:13:00 PM
no.

At this time, ppl have transplanted the ENTIRE contents of a eeprom to another xbox and it then works fine.

It's not JUST the serial they swapped, the swapped the contents of an entirely different working xbox's eeprom.

There is still a bit more work to be done to just implant a new serial that will work and pass checksums.

Z
Title: A Fix For Connectivity Issues.
Post by: Skunky on November 18, 2002, 02:05:00 PM
QUOTE (Zander @ Nov 18 2002, 12:13 PM)
no.

At this time, ppl have transplanted the ENTIRE contents of a eeprom to another xbox and it then works fine.

It's not JUST the serial they swapped, the swapped the contents of an entirely different working xbox's eeprom.

There is still a bit more work to be done to just implant a new serial that will work and pass checksums.

Z

                                     ph34r.gif Do we know if a ver 3944 bios (my old box ..non live fuctioning) will work with a 4034 bios?  IE swap eeprom data? ph34r.gif
Title: A Fix For Connectivity Issues.
Post by: mod7 on November 18, 2002, 02:21:00 PM
Opjose....am I right in saying that when a locked hd is booted with a signed bios that f:\ is not even accessable?  Would that make it impossible for xbl gremlins to mess with it?  I mean if they coded something sure they could check but at it's present state it should be impossible to see correct?


Thanx
Title: A Fix For Connectivity Issues.
Post by: halfwayhouse on November 18, 2002, 03:40:00 PM
After reading this whole thread it doesnt make much sense to me.  It seems to be a mod chip detecition issuse to me as people buy new xboxes they are online right away.  Has anyone gathered up serial numbers of virgin xboxes that cannot connect and look for similarities?  Dont know if this is any help.  One other thing I can think of for the virgin xboxes is some cable modems keep track of arp entries and some isp's have ip limiting enabled on there system so say you have 2 ip's for your internet.  One for your pc and one for your xbox (that is modded and doesnt work) if you get a virgin xbox and it doesnt connect it could be a third arp entry as they will all have different mac addresses.  Call your isp and see if they can clear it up for you???  Sorry if it dont make sense typing it up while i clear arp entries for a customers modem thast why that idea came into mind.
Title: A Fix For Connectivity Issues.
Post by: opjose on November 19, 2002, 12:03:00 AM
QUOTE (Zander @ Nov 18 2002, 05:33 PM)
luma is right.

Changing your MAC, from a network standpoint will only break things on your local segment.

It's fine.

Z

                                    Yeap he's right.
Title: A Fix For Connectivity Issues.
Post by: opjose on November 19, 2002, 12:04:00 AM
QUOTE (halfwayhouse @ Nov 18 2002, 10:40 PM)
After reading this whole thread it doesnt make much sense to me.  It seems to be a mod chip detecition issuse to me as people buy new xboxes they are online right away.  Has anyone gathered up serial numbers of virgin xboxes that cannot connect and look for similarities?  Dont know if this is any help.  One other thing I can think of for the virgin xboxes is some cable modems keep track of arp entries and some isp's have ip limiting enabled on there system so say you have 2 ip's for your internet.  One for your pc and one for your xbox (that is modded and doesnt work) if you get a virgin xbox and it doesnt connect it could be a third arp entry as they will all have different mac addresses.  Call your isp and see if they can clear it up for you???  Sorry if it dont make sense typing it up while i clear arp entries for a customers modem thast why that idea came into mind.

                                    In my case this is not an issue at all.

No it's not as you say.
Title: A Fix For Connectivity Issues.
Post by: opjose on November 19, 2002, 12:06:00 AM
QUOTE (mod7 @ Nov 18 2002, 09:21 PM)
Opjose....am I right in saying that when a locked hd is booted with a signed bios that f:\ is not even accessable?  Would that make it impossible for xbl gremlins to mess with it?  I mean if they coded something sure they could check but at it's present state it should be impossible to see correct?


Thanx

                                    As I posted in Zander's thread, the current technique is NOT looking for extra files on the drive, nor even a locked replacement drive.

However M-icrosoft did something very sneaky which I posted in his thread.

In effect by fooling you a bit, they can detect the mod chip even when it is switched OFF.

It's a real misdirection, but like all good magic, it works!
Title: A Fix For Connectivity Issues.
Post by: Duece on November 19, 2002, 07:42:00 AM
QUOTE (opjose @ Nov 19 2002, 02:06 AM)
QUOTE (mod7 @ Nov 18 2002, 09:21 PM)
Opjose....am I right in saying that when a locked hd is booted with a signed bios that f:\ is not even accessable?  Would that make it impossible for xbl gremlins to mess with it?  I mean if they coded something sure they could check but at it's present state it should be impossible to see correct?


Thanx

As I posted in Zander's thread, the current technique is NOT looking for extra files on the drive, nor even a locked replacement drive.

However M-icrosoft did something very sneaky which I posted in his thread.

In effect by fooling you a bit, they can detect the mod chip even when it is switched OFF.

It's a real misdirection, but like all good magic, it works!

                                    MS can detect a modchip when it is switched OFF or disabled???  If that is the case how come I can still get on live?  I thought if it was detected then it was blocked??
Title: A Fix For Connectivity Issues.
Post by: VaporStone on November 19, 2002, 12:24:00 PM
OPJOSE
were can i find the program hdlock. because i unlocked it with hddunlock and then hddisable and then i tried to lock it later with a program called unlockX and it said "this drive cannot be locked" so could u tell me if the hdlock will work and if so could u send it my way

Thanx!!!
Title: A Fix For Connectivity Issues.
Post by: Giorgos on November 19, 2002, 05:17:00 PM
smile.gif

just one question for you ..

i installed XBOX live via the NBA2k3 feature, about 1 month ago (you have the XBOX live option on the dashboard but you can only check your connection). I am in the UK so i do not have live yet. But i have tested my connection about 2 weeks ago using the connectivity tool.
BUT i always play games with the mopd chip on, and i do regurarly drop to the XBOX dashboard ..

do you think that MY XBOX would have been flagged as well ??

Is that a new addition to the XBOX dashboard, after the 15th of november or am i in trouble ??

Thnx

Giorgos
Title: A Fix For Connectivity Issues.
Post by: b0b on November 19, 2002, 05:40:00 PM
I believe clifface is correct. I modded my xbox and in copying the orginals C: and E: directorys I missed a folder essential to the dash becuase my ftp program had a glitch in it's directory listings. therefor I could not access the ms dash. I then discovered my mistake last night with an updated version of the ftp program. I then copied this folder to my modded hd and launched xboxdash.xbe to make sure it functioned and so it did at this point I believe the updated xboxdash.xbe detected my mod as it was in mode 2. I then proceeded to the xboxlive dash through the ms dash and got the now famous XBL live could not be found. this explains it as the updated xboxdash.xbe must record the fact it detected a mod chip and then when you next launch xboxlive dash and the connectivity test is make it to the XBL live step it sends the mod information to XBL. So even if you have made it right with a new serial/mac be careful and don't access the ms dash from anyother program,  disable the mod with a switch or use mode 3 on your matrix.
Title: A Fix For Connectivity Issues.
Post by: opjose on November 20, 2002, 12:55:00 AM
QUOTE (clifface @ Nov 19 2002, 11:01 PM)
You can disable the chip and play online but what opjose said I believe is that if you at any point go to the ms dashboard by launching xboxdash.xbe from the evolution x menu, you will only be able to get on live one more time.  During that time something is sent to MS saying you have a mod and after that you will get the xbox live not found msg.  As long as the only time you go to the xboxdash.xbe is when your chip is disabled then you should be fine.  Until perhaps they do start searching for diff hd's.  I'm not sure how big of a threat that is as of yet.  Please correct me if I'm wrong anybody.

                                    Exactly!
Title: A Fix For Connectivity Issues.
Post by: opjose on November 20, 2002, 12:58:00 AM
QUOTE (b0b @ Nov 20 2002, 12:40 AM)
I believe clifface is correct. I modded my xbox and in copying the orginals C: and E: directorys I missed a folder essential to the dash becuase my ftp program had a glitch in it's directory listings. therefor I could not access the ms dash. I then discovered my mistake last night with an updated version of the ftp program. I then copied this folder to my modded hd and launched xboxdash.xbe to make sure it functioned and so it did at this point I believe the updated xboxdash.xbe detected my mod as it was in mode 2. I then proceeded to the xboxlive dash through the ms dash and got the now famous XBL live could not be found. this explains it as the updated xboxdash.xbe must record the fact it detected a mod chip and then when you next launch xboxlive dash and the connectivity test is make it to the XBL live step it sends the mod information to XBL. So even if you have made it right with a new serial/mac be careful and don't access the ms dash from anyother program,  disable the mod with a switch or use mode 3 on your matrix.

                                    Yeap.

So far this has been very consistent.

I've also been able to keep a modded Xbox from being banned because I know this.

Effectively the modded Xbox is NEVER permitted to drop to the M-icrosoft dashboard, connect to Xboxlive, or even bring up an Xblive program with the mod chip ON.

With the mod chip OFF I only drop to the OLDER MS Dashboard that has no mod chip detection or XBLive issues.

This has worked flawlessly, but it can be easily be screwed up by a friend, sibling or significant other.

Title: A Fix For Connectivity Issues.
Post by: emoney on November 20, 2002, 03:02:00 AM
wait wait wait.. opjose... what do you mean the "older" ms dashboard?
Title: A Fix For Connectivity Issues.
Post by: opjose on November 20, 2002, 03:54:00 AM
QUOTE (emoney @ Nov 20 2002, 10:02 AM)
wait wait wait.. opjose... what do you mean the "older" ms dashboard?

                                    The "pre-live" update.
Title: A Fix For Connectivity Issues.
Post by: opjose on November 20, 2002, 03:55:00 AM
QUOTE (scoobster @ Nov 20 2002, 09:59 AM)
QUOTE (opjose @ Nov 20 2002, 07:58 AM)
This has worked flawlessly, but it can be easily be screwed up by a friend, sibling or significant other.

F-boot2 may help, as it will only run c:xboxdash with mod disabled, unless you go out of your way to run it

bad m$neaky bad
ph34r.gif

                                    Yes, this reduces the problem to someone trying to connect to live with XboxLive enabled games.

So you would have to keep these off the hard drive and locked away when the mod chip is turned on.

Remember it MAY also "report in" at game startup.
Title: A Fix For Connectivity Issues.
Post by: opjose on November 20, 2002, 06:44:00 AM
QUOTE (emoney @ Nov 20 2002, 11:17 AM)
ok here's a question...... when would you ever NEED to use the ms dashboard??   can you not play retail games with the other bioses?

                                    Some settings require the M-icrosoft Dashboard to set them.

E.G. audio, video, etc. at present.

Title: A Fix For Connectivity Issues.
Post by: opjose on November 20, 2002, 08:37:00 AM
QUOTE (Duece @ Nov 20 2002, 02:40 PM)
Why would you need to use a bios that has F_Boot ot E_Boot?  As long as you change the evox ini file to use a pre-live version of the MS Dashboard then you should be ok right?

                                    Try doing this and you'll see it's not as easy as you think.