Booting Into Msdash
Posted 07 April 2009 - 12:52 PM
First of all I'm a big newbie in the consoles world so please bear the stupidness of this topic Recently I have bought an used xbox console. Here are the specs:
- chip - DuoX 2 Lite
- dash - EvoX
- it's a 1.3 console
- custom 250 GB hdd
The console itself it's working perfectly so far, but I can't force it to load into original dash. When I'm pressing the eject button it starts, but it's loading Evox, the same as if I pressed the power button. I've opened the console and the chip is placed correctly (I have checked with the schematics on the creators page). The BT cable is placed correctly. I can run the original dash from evox menu so I don't know what's the reason for this. Maybe the solution is really simple Or someone could tell me if there's another way to disable the chip?
Posted 08 April 2009 - 10:03 AM
i wish i could help more, but it sounds like a BT prob
Posted 09 April 2009 - 04:14 PM
if BT isn't hooked up to your eject PCB, then it won't make a difference what button you start with.
if you need to boot to m$dash, just put it into your bootpath, or patch a different bootpath to your bios of choice.
otherwise, add M$dash as an application...that's what i do.
Posted 09 April 2009 - 05:11 PM
What BC54 is getting at is that if the HD isn't locked, starting up the Xbox with the modchip disabled will throw an error. Since you purchased this already modded, its possible that it is still unlocked. Its a pretty simple process to lock the HD, but lets cross that bridge as it comes.
Show a pic of the mobo focusing on the BT point and the chip itself.
Posted 09 April 2009 - 07:32 PM
Maybe it's this hdd locking and stuff. Don't exactly know what it is about duh. If I lock the drive it would work as it should?
Posted 09 April 2009 - 10:52 PM
Maybe they did a TSOP flash and a DuoX mod.
Posted 09 April 2009 - 11:05 PM
TSOP and a chip? Well this is an idea, I didn't thought about that... It would explain why after pressing the eject button it boots to the evox. How I can check what BIOS is loaded in the eeprom? (in the evox, in the place where the info about bios should be, there's an empty space...) And is the flashing of it safe?
Posted 10 April 2009 - 01:23 AM
also, just in case it is not a tsop, and it boots to ms dash, put in the original hard drive. if you don't have it anymore, then it should boot to an error 5.
Edited by bc54, 10 April 2009 - 01:27 AM.
Posted 10 April 2009 - 03:26 PM
if it does, then you have a BT issue. the chip should only light up when it's active.
TSOP and a DuoX2 chip....seen it many times.
it's a good way to have 3 custom bios images available.
if your HD isn't locked, your not going to get a retail boot.
the retail bios will give error 5/6 if the HD is not properly locked.
locking the HD is a one-step process in evox. very easy to do.
locking your HD can cause major problems down the road, so only do it if you're going to be using xbox live, otherwise it's just not worth it.
if you want it to boot up like a regular xbox, and you don't care about XBlive, just follow my original advice.
put M$dash (xboxdash.xbe) in your bootpath and rename to evoxdash.xbe. don't forget all the other files that go with it.
it's that simple.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users