Group: Moderator
Posts: 2737
Joined: 5-April 07
Member No.: 337188
Xbox Version: v1.0
360 version: none
There is no need to do that. I use the Phoenix Bios Loader to start the xbox debug bios. I think the bios is the tatx bfm (boot from memory) debug bios. The Phoenix Bios Loader came from the kingroach ndure package. You can find it in the E:\ndts folder. It is the default.xbe that is used to launch the maintenance unleashx dashboard. The debug dashboard files can live together on your C partition with the retail dashboard files. Both debug dash and retail M$dash work fine.
The original M$ debug biosses that come with the xdk recovery cd work as well. You just can't run a retail signed xbe with one of those.
Group: Moderator
Posts: 2737
Joined: 5-April 07
Member No.: 337188
Xbox Version: v1.0
360 version: none
QUOTE
but i really need to flash it
It might help if you could explain us why?
Flashing a debug bios is the same as flashing a retail bios. However, most debug biosses are 1 meg in size. On some xbox versions with only a 256KB flash chip, you can't flash those. It also means you don't have a way to recover from a bad flash in case things go wrong. (Besides installing a modchip.)
Group: Moderator
Posts: 2737
Joined: 5-April 07
Member No.: 337188
Xbox Version: v1.0
360 version: none
Evoxdash is just a xbe like the others. What debug bios did you use on your xbox? As I told already, some debug biosses will not run retail signed applications.
To run xbmc, you don't need a debug bios. As I already explained, you can launch a debug bios with the Phoenix Bios Loader from within your xbmc dash.
You still didn't tell what you are trying to do. Running the evoxdash on a debug bios doesn't make much sense to me, unless you are trying to take screenshots.
Group: Head Moderator
Posts: 1947
Joined: 7-May 08
From: north carolina
Member No.: 380500
Xbox Version: v1.2
360 version: v4.0 (jasper)
you should really look at the value of the debug xbox before you go about flashing a retail bios or any other bios for that matter. The debug unit is a rare item. Your best bet though is to just install a chip and flash that with a bios.
Group: Moderator
Posts: 2737
Joined: 5-April 07
Member No.: 337188
Xbox Version: v1.0
360 version: none
Sorry, I totally misunderstood. I thought you tried to flash a debug bios in a retail xbox instead of the other way around. Forget all previous I wrote.
A debug unit differs from a retail one:
I think it has 128MB of memory instead of the usual 64MB The MCPX chip is different. It contains different code to decode the 1BL (first part of the bios) The tsop flash write enable points are connected. The tsop is flashable.
I remember having read that a lot of biosses have problems with 128MB of memory. You will need to find a bios that works fine with it.
I also have read somewhere that the eeprom of a debug unit is empty.
I agree that a debug unit is more valueable if you leave it intact. I can understand that the situation is diferent in your country.
There are programs that can modify the header of a xbe from retail to debug. Maybe you can get the evoxdash running that way?
The easiest way to get programs on the debug unit is probably installing the xdk on a pc. It will create a xbox neiborhood with access to the xbox harddisk.
An alternative to the evoxdash might be raincoat. However, if I remember well, debug biosses don't like programs that are created without the official xdk. The small reboot program for instance refused to run from the debug dash. The eeprom can be programmed with an eeprom reader in case it should be empty. You can create a valid eeprom image with the liveinfo beta 3 program.