xboxscene.org forums

Author Topic: Can't Boot Into Disable Mode - And Flashing Problem  (Read 71 times)

blazedgoldfish69

  • Archived User
  • Newbie
  • *
  • Posts: 19
Can't Boot Into Disable Mode - And Flashing Problem
« on: August 11, 2006, 03:04:00 AM »

It also seems that the LED is flashing red. Is this bad..?
Logged

Chancer

  • Archived User
  • Hero Member
  • *
  • Posts: 5751
Can't Boot Into Disable Mode - And Flashing Problem
« Reply #1 on: August 11, 2006, 04:32:00 AM »

How have you wired BT and D0?
How did you make the bios disc?
The LED should be flashing red when the chip is on.
Logged

Chancer

  • Archived User
  • Hero Member
  • *
  • Posts: 5751
Can't Boot Into Disable Mode - And Flashing Problem
« Reply #2 on: August 11, 2006, 11:11:00 AM »

The bios file first.
To make abios disc you don't use qwix or make it an ISO at all.
You should burn a plain old fashioned data disc with 2 files in the root of the disc
BIOS.BIN (Your 512k hacked bios)
aabbcc.dat (Dummy File)
An XISO will not work as a bios disc.

The always on.
You have a short to ground on the D0 somewhere or your BT connection is incorrect (short to 3v3 rail)
Check through these 2 connections. Most likely is a trapped D0 wire that has nicked the insulation and is shorting to ground.
Logged

dbldown768

  • Archived User
  • Sr. Member
  • *
  • Posts: 317
Can't Boot Into Disable Mode - And Flashing Problem
« Reply #3 on: August 12, 2006, 10:36:00 AM »

ok, i just did the same thing. i just put in a DuoX 2  GS Cromwell/FlashBios Edition and everything booted up fine.  i have to rebuild installs before but its been awhile and i was a puss when it came to try and solder the d0 point this time, dunno why.  anyway i cant seem to disable the mode.  i know the eject button wire is good and the pin headers are fine.  I flashed using bank 1 and a 512k 4983 x2 bios.  put that on a dvd with a dummy 100mb file and everything flashed fine.

So what im getting from your previous post is that i need to make the d0 point connnection better to turn this off correct???  Lets say i dont want to bother doing that, does it cause any harm?  I can care less if i cant turn off the bios anyway.

Btw, if i power on with the eject button, it seems to ask for the time to be entered in every time... i dont know why that is probably related i would guess.  this xbox is rather old so it could be that capacitor as well.  the reason for the chip in the first place is that the box would randomly frag, so i was thinking the tsop might have gone bad - that or the mcpx chip or whatever.
Logged

Chancer

  • Archived User
  • Hero Member
  • *
  • Posts: 5751
Can't Boot Into Disable Mode - And Flashing Problem
« Reply #4 on: August 12, 2006, 02:58:00 PM »

The clock resetting could be the back up capacitor but can equally be a soldering problem with the installation.
Always on is sometimes a cut in the wire from the Xbox D0 to the chip. this shorts out on a ground point and makes the Xbox boot always on. Also check the length of stripped ends of the wire they must be short so as not to contact any other points on the mobo.
With a GS an open circuit BT line will also cause the chip to be always on so it needs double checking.
Wiring always on will do no harm if you don't need the retail bios, but the clock not being set can cause some games eg Rockstar games not to boot
Logged

dbldown768

  • Archived User
  • Sr. Member
  • *
  • Posts: 317
Can't Boot Into Disable Mode - And Flashing Problem
« Reply #5 on: August 14, 2006, 07:07:00 AM »

since my post i have tried to use the bottom d0 point for the installation.  Didnt seem to correct any problems.  I know most say its not their soldering, but after using 2 different points on the board something seems wrong.  The BT point has to be fine, because that was the easies one of them all the solder.  Granted i did to a full rebuild of a 1.6 back in the day (maybe got lucky with that one) so i cant see why this one was such a problem.  As far as the clock resetting, i have to say almost 100% its the capacitor.  Is there any way of fixing that?  I know avalaunch when it boots up says that it fixed the clock reset issue, but not exactly sure what that means.
Logged