xboxscene.org forums

Author Topic: Duox2 Gs Cromwell Flashing  (Read 73 times)

Chancer

  • Archived User
  • Hero Member
  • *
  • Posts: 5751
Duox2 Gs Cromwell Flashing
« on: November 23, 2006, 02:16:00 AM »

If it says 2.32 you are on the Cromwell Linux bank (Bank 0) You have to use a linux flash app (Eurasia) to flash from that bank. If not switch to bank 1 and use flashbios
Logged

driftin240

  • Archived User
  • Newbie
  • *
  • Posts: 3
Duox2 Gs Cromwell Flashing
« Reply #1 on: November 23, 2006, 08:05:00 PM »

ok, after about 30 restarts, it finally loaded 3.03. i uploaded m8 1.6 via network, it flashed, shut off, and now i'm getting the good ol 3 reboots and frag. bank 0 works and disabled still works. btw, the system is a 1.6
Logged

Chancer

  • Archived User
  • Hero Member
  • *
  • Posts: 5751
Duox2 Gs Cromwell Flashing
« Reply #2 on: November 24, 2006, 04:09:00 AM »

It sounds like you flashed a 256k bios instead of resizing M8.16 to 512k.
You will have to flash the box using bank 0 now.
Obtain Eurasia and burn the ISO to disc.
make up a bios disc with a 512k (M8+.16 etc) bios named bios.bin  and a dummy file named aabbcc.dat (around 100mb) burn the bios disc as a data disc.
You also need a regular MS controller (The big ugly type) and standard av lead to the TV
Boot the box on Bank 0 and insert the Eurasia flash disc. when it prompts for the bios disc, flick the bank switch to bank 1 before inserting the bios disc (use a non metalic object such as a toothpick)
The flash goes over bank 1.
network flash does not work on bank 0
Logged

Chancer

  • Archived User
  • Hero Member
  • *
  • Posts: 5751
Duox2 Gs Cromwell Flashing
« Reply #3 on: December 22, 2006, 05:51:00 AM »

If you mis-flashed both banks then you will have to hot swap with a working chip to flash it now.
Logged

fiveten

  • Archived User
  • Newbie
  • *
  • Posts: 44
Duox2 Gs Cromwell Flashing
« Reply #4 on: January 11, 2007, 11:29:00 PM »

I have had good luck with the oz flash disk. You can get this from the usual places and Yes, as chancer said make sure you have the correct bios size.
Logged