Jump to content


Photo

#xbins And Executer 2 4977


  • Please log in to reply
6 replies to this topic

#1 dizturbd

dizturbd

    X-S Expert

  • Members
  • PipPipPip
  • 556 posts
  • Xbox Version:v1.0
  • 360 version:unknown

Posted 01 July 2003 - 06:34 PM

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?

#2 dizturbd

dizturbd

    X-S Expert

  • Members
  • PipPipPip
  • 556 posts
  • Xbox Version:v1.0
  • 360 version:unknown

Posted 02 July 2003 - 03:01 AM

Jebus. 41 views and no replys. Someone has got to know the answer.

#3 bb07

bb07

    X-S X-perience

  • Members
  • PipPip
  • 426 posts

Posted 02 July 2003 - 03:03 AM

well ,whats the question dry.gif

#4 dizturbd

dizturbd

    X-S Expert

  • Members
  • PipPipPip
  • 556 posts
  • Xbox Version:v1.0
  • 360 version:unknown

Posted 02 July 2003 - 03:14 AM

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?

#5 nix2k

nix2k

    X-S Member

  • Members
  • Pip
  • 82 posts
  • Location:Calgary somewhere

Posted 02 July 2003 - 08:04 AM

When you boot your xbox, does it say XECUTOR2 on the logo screen? Or are you just going by what the dashboard says.

#6 akula169

akula169

    X-S X-perience

  • Members
  • PipPip
  • 439 posts
  • Xbox Version:v1.1
  • 360 version:v3.0 (falcon)

Posted 02 July 2003 - 08:27 PM

posting the checksum might help

#7 sharkzor

sharkzor

    X-S Member

  • Members
  • Pip
  • 74 posts
  • Location:the nehterlands
  • Xbox Version:v1.1
  • 360 version:v4.0 (jasper)

Posted 03 July 2003 - 07:12 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).




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users