xboxscene.org forums

Author Topic: #xbins And Executer 2 4977  (Read 96 times)

dizturbd

  • Archived User
  • Sr. Member
  • *
  • Posts: 357
#xbins And Executer 2 4977
« on: July 01, 2003, 11:34:00 AM »
I just dled the 4977 bios from #bins and did a tsop flash with it.  It shows up as a Evox D.6 and Brute Force won't work.  So beware and can someone look into this?
Logged

dizturbd

  • Archived User
  • Sr. Member
  • *
  • Posts: 357
#xbins And Executer 2 4977
« Reply #1 on: July 01, 2003, 08:01:00 PM »
Jebus.  41 views and no replys.  Someone has got to know the answer.
Logged

bb07

  • Archived User
  • Full Member
  • *
  • Posts: 153
#xbins And Executer 2 4977
« Reply #2 on: July 01, 2003, 08:03:00 PM »
dry.gif
Logged

dizturbd

  • Archived User
  • Sr. Member
  • *
  • Posts: 357
#xbins And Executer 2 4977
« Reply #3 on: July 01, 2003, 08:14:00 PM »
I dled the Executer 2 4977 bios from #xbins and flashed a TSOP with it.  The xbox says it's a EvoX D.6.  Brute Force won't work with a D.6, so what's the dealy yo?
Logged

nix2k

  • Archived User
  • Newbie
  • *
  • Posts: 24
#xbins And Executer 2 4977
« Reply #4 on: July 02, 2003, 01:04:00 AM »
When you boot your xbox, does it say XECUTOR2 on the logo screen? Or are you just going by what the dashboard says.
Logged

sharkzor

  • Archived User
  • Newbie
  • *
  • Posts: 30
#xbins And Executer 2 4977
« Reply #5 on: July 03, 2003, 12:12:00 AM »
nothing wrong with it. just ran bios checker

256k BIOSES:
 1.Bios > X-Ecuter2 4977 (1539300447)

i think you didn't correctly replaced the default bios (evox d6 is in most raincoat saves).
Logged