Jump to content


Can Somebody Define Soft Mods For Me?

  • Please log in to reply
2 replies to this topic

#1 iBOtpeaches


    X-S Young Member

  • Members
  • Pip
  • 36 posts
  • Location:Kansas
  • Xbox Version:v1.6b
  • 360 version:v1 (xenon)

Posted 29 December 2006 - 01:47 AM

Im writing some huge thing on xbox, and i need a definition for softmods.

if you do respond to this, dont tell me what i can do with soft mods but what are soft mods.
thats a lot

#2 JayDee


    X-S Legend

  • Head Moderators
  • PipPipPipPipPipPipPipPipPip
  • 5,750 posts
  • Gender:Male
  • Location:Sweden
  • Xbox Version:v1.1
  • 360 version:v2 (zephyr)

Posted 29 December 2006 - 02:21 PM


This is the first softmod, and much have happened since.

Most packages today uses an exploit in a xbe file on c: to load nkpatcher


For some in depth info check this video:


~1hour but it covers alot from the start of xbox hacking and also about softmods.

Some more links worth reading:



That should actually cover everything for you

#3 FrostyTheSnowman


    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,674 posts
  • Location:Utah
  • Xbox Version:v1.0
  • 360 version:v1 (xenon)

Posted 29 December 2006 - 09:12 PM

Basically, most softmods work like this...

When booting, the XBOX executes 'c:\xboxdash.xbe' - This file NEEDS to be an officially signed XBE by MS. So, we need an exploitable, signed XBE file to boot, and load our new dashboard, because if we simply place our dashboard files on C and rename the main file to 'xboxdash.xbe' the XBOX will crash at startup because the file will not be officially signed. So, to accomplish this, we need an exploitable, signed XBE file to do this. The most commonly used file is the official XBOX Live! dashboard file. This file is exploitable because when executed, it looks in the c:\fonts directory, and loads the fonts in that directory for it's menus. So, to exploit it we simply put in some bogus font files, which cause a buffer overflow, and crashes the XBOX, leaving it wide open for an UNSIGNED XBE file to run. But how do we get our dashboard to run now, you ask? Easy. Those font files not only crash the XBOX, but are also packed with a small amount of code that executes a new, unsigned XBE from whatever location it's programmed to load from. The unsigned XBE file is commonly a BIOS patcher, like NKPatcher or Phoenix BIOS Loader. (Search on these to learn more about them.) Basically, a BIOS patcher is like a software 'modchip' that modifies the BIOS on-the-fly, so that it will have new features like LBA48(Large HDD Support), Shadow C, Shadow EEPROM, XBOX Live! Blocking, etc. After the BIOS patcher is executed, it patches the BIOS and then loads up your dashboard of choice. (EvolutionX, UnleashX, XBMC, Avalaunch, etc.)

That pretty much sums it up, but here's a quick overview:

1. XBOX is turned on, and 'c:\xboxdash.xbe' is executed.

2. 'c:\xboxdash.xbe' looks in the font directory for the necessary fonts.

3. The fonts are bogus, and they cause a buffer overflow and crash the XBOX.

4. Once crashed, the fonts execute a BIOS patcher, usually NKPatcher, from wherever they are told to execute it from.

5. NKPatcher patches the BIOS with all the extra features, and then loads up your Dashboard of choice. (EvolutionX, UnleashX, XBMC, Avalaunch, etc.)

This, in a nutshell, is how softmods work.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users