xboxscene.org forums

Author Topic: When Good Bioses Go Bad  (Read 71 times)

chinmi

  • Archived User
  • Full Member
  • *
  • Posts: 205
When Good Bioses Go Bad
« on: September 11, 2003, 02:43:00 AM »

x4977 didn't bypass the clock set.... maybe that's why it cause an error.....
have u tried disabling the mod-chip and set the clock with the original dashboard ??
Logged

TEAM XODUS

  • Archived User
  • Jr. Member
  • *
  • Posts: 86
When Good Bioses Go Bad
« Reply #1 on: September 19, 2003, 06:36:00 AM »

Skanky have u tried using the new d6 ? ( distributed together with the latest evo-x dash )
Logged

KevC

  • Archived User
  • Newbie
  • *
  • Posts: 14
When Good Bioses Go Bad
« Reply #2 on: September 19, 2003, 02:30:00 PM »

Sometimes i ruminate if there is a potential exploit in the lpc and d0 if theyre really read only because it might be an act of a chain reaction that somehow conducted to the destruction of a whole bios not related to you but in relation to your question well i still think its somehow integrating the collective thing we are all being thru these days which oddly lead to total apocalypse to our xboxes

and no there isnt life beyond xbox once you get in there is no way out


Logged

KevC

  • Archived User
  • Newbie
  • *
  • Posts: 14
When Good Bioses Go Bad
« Reply #3 on: September 19, 2003, 02:31:00 PM »

Sometimes i ruminate if there is a potential exploit in the lpc and d0 if theyre really read only because it might be an act of a chain reaction that somehow conducted to the destruction of a whole bios not related to you but in relation to your question well i still think its somehow integrating the collective thing we are all being thru these days which oddly leads to total apocalypse to our xboxes

and no there isnt life beyond xbox once you get in there is no way out


Logged

Skanky

  • Archived User
  • Newbie
  • *
  • Posts: 5
When Good Bioses Go Bad
« Reply #4 on: September 21, 2003, 06:15:00 PM »

I couldn't get Evox D6 to work for some reason.  Flashed bank 0 with 256K bios, then when rebooting, it came up with the MS logo (under the Xbox logo).  Afterwards, EvolutionX loaded (what seemed to be) fine.

Funny thing is that i could not launch any games and would ususally freeze up the xbox if i tried to do so.

Going to try the new M7 tonight (or D7 or whatever it is).

Any info on why D6 wouldn't work?  Should I be using the eject fix version or not?

Thanks


Skank
Logged

Beretta1979

  • Archived User
  • Newbie
  • *
  • Posts: 4
When Good Bioses Go Bad
« Reply #5 on: October 06, 2003, 07:52:00 AM »

Is your Xbox mod chip soldered or just bolt to your xbox ??? In de the latter case it just can be a bad contact ... First my matrix was bolted too but after a while it stopped working properly due to bad contact on the D0 point ... Sometimes the xbox booted , sometimes I got the error ... Then i would re align the chip but after a while it would get fucked up again ... It went to somebody who is an expert in soldering , he just soldered a little adapter on my motherboard and one wire (to the D0) .. Much better now it doesn't get loose any more .. Maybe this would solve your porblem too ??? That no solder method is really not reliable certainly on the long term ...
Logged

Skanky

  • Archived User
  • Newbie
  • *
  • Posts: 5
When Good Bioses Go Bad
« Reply #6 on: October 07, 2003, 09:37:00 AM »

QUOTE (Beretta1979 @ Oct 6 2003, 04:52 PM)
Is your Xbox mod chip soldered or just bolt to your xbox ??? In de the latter case it just can be a bad contact ... First my matrix was bolted too but after a while it stopped working properly due to bad contact on the D0 point ... Sometimes the xbox booted , sometimes I got the error ... Then i would re align the chip but after a while it would get fucked up again ... It went to somebody who is an expert in soldering , he just soldered a little adapter on my motherboard and one wire (to the D0) .. Much better now it doesn't get loose any more .. Maybe this would solve your porblem too ??? That no solder method is really not reliable certainly on the long term ...


My chip is bolted on (using pogo pin adapter with rivets).

I suppose it could be losing contact sometimes, but the xbox behaves differently than I would expect if it were just a d0 or pogo point not making contact.  Again, this ALWAYS ends up with the error 13 message.  Additionally, I have never had to re-align the chip - I've always been successful in re-flashing it, but then it just returns to the error 13 message after a few restarts (yes, sometimes it restarts without the error).

Granted, it does sound mechanical, and of course, soldering the contacts wouldn't hurt anything (granted I don't fuck it up).  Maybe that's the next step.

Is there a place I can go to find out what the different error codes actually mean?  Maybe this would lend some insight.

Thanks again.

Skank
Logged