xboxscene.org forums

Author Topic: Slayer's Boot Disk And Ndure  (Read 40 times)

ldotsfan

  • Archived User
  • Hero Member
  • *
  • Posts: 2072
Slayer's Boot Disk And Ndure
« on: May 19, 2008, 08:35:00 AM »
QUOTE(K@mui @ May 19 2008, 10:59 PM) View Post

The problem is that after i replaces all the files in C and E folder the xbox doesn't start at all (I disabled the chip also)

What do you mean by the xbox doesn't start at all? Any error messages? Led colors? Blank screen?
Logged

ldotsfan

  • Archived User
  • Hero Member
  • *
  • Posts: 2072
Slayer's Boot Disk And Ndure
« Reply #1 on: May 19, 2008, 08:59:00 AM »
Is this xbox a 1.0? Because its error message has no error no. Can you enable the chip again, rebuild C drive with Slayer's and check the kernel version? Once you have the kernel version, run ndure 3.1 again with kernel specific selection and regenerates files for that specific kernel and attempt to softmod again.
Logged

ldotsfan

  • Archived User
  • Hero Member
  • *
  • Posts: 2072
Slayer's Boot Disk And Ndure
« Reply #2 on: May 19, 2008, 09:17:00 AM »
Kernel generic usually works. Is the hdd locked? I'm still wondering why a xbox 1.4/1.5 error screen has no error code.
Logged

HD10291

  • Archived User
  • Full Member
  • *
  • Posts: 127
Slayer's Boot Disk And Ndure
« Reply #3 on: May 19, 2008, 12:54:00 PM »
You must have your HDD locked with the CORRECT eeprom , unless you got a chip, then leave it unlocked.
Logged

kingroach

  • Archived User
  • Hero Member
  • *
  • Posts: 1522
Slayer's Boot Disk And Ndure
« Reply #4 on: May 19, 2008, 01:00:00 PM »
you should be able to lock the the system with configmagic .. I think slayers disk already has that inside.. Otherwise, with the modchip on, copy evox in the harddrive.. backup eeprom and lock the hard drive..
Logged