>HaX<

Hacking an Xbox

>HaX<

Hmm, I suppose the acronym for this site's title would be HaX. Neat. Accidental. Quite appropriate.

Please consider investing time in assisting with the OpenXDK so we can have more fully legitimate tools. (See ideas on needed useful software).

Current Version Of Site

Where to find what you want

What most users will want to do is to scroll down past the Introductions and in the "The Steps To Hack An Xbox" section scroll past the "Preparation" step. I do not necessarily recommend missing all the useful warnings such as getting banned from the "Xbox Live!" service.

Current Status

This version of this site is meant to be an informational resource, and a lengthy guide on how to hack an Xbox. This site is not designed to be a quick how-to. I leaned more towards including more information, which may or may not be needed, rather than less. Furthermore, I leaned more in getting more information on this site rather than cosmetics. My logic was that I want to hinder the accidental destruction of Xboxes as soon as possible (and slowing visitors down so they read information doesn't hurt that goal), and I can worry about spiffiness later.

Future Plans

I do have interest in this site being streamlined (nicer navigation, more visible access to the most desired information) and spiced up (more graphics), and to have a good section for troubleshooting (to quickly come up with a resolution when there is a problem). I haven't yet decided if these things will be done primarily by myself, or primarily by someone else, or a primarily a combination. Time will tell.

I have interest in moving this site to another location once some more software has been made with the OpenXDK.

Contacting This Site's Webmaster

If you have any interest in contacting me about helping with this site, or any thoughts you have about the content on this site, please E-Mail HaXOrigLocation@toogam.bespin.org and include the word "Xbox" in the subject. If you are wanting help with hacking an Xbox, and you know what files are located on your Xbox hard drive and why you are getting the results you are, I may be willing to assist if you try contacting me. If you're not sure why you are getting the results you are, I recommend reading more material or utilizing the forums on X-S (see this site's Other Resources page). I would be slowed down from working further on this or other projects if I assisted everyone these days who is having troubles hacking an Xbox, so please do not be offended if I do not offer my personal assistance at studying your situation for you and determining what is wrong.

Site Mission

It is my genuine hope that this site assists more people in the joys obtainable by successfully hacking an Xbox system. With more users will come more talent. I hope to help more people be more successful (getting past hurdles to accomplish more) and less unsuccessful (hopefully someone will find enough documentation on this site to prevent a "negative frag" (broken Xbox)).

Most Frequently Asked Questions

Can my Xbox be hacked?

Yes. The following hacks are known to work on every Xbox to date:

What is the most recommended hack to use?
  1. Whatever works
  2. Whatever is safest
What is the safest hack to use?

Check your Xbox kernel version. If it is *EARLIER* than 5713, then the Easter Egg Exploit can be installed and so that is the safest hack available.

How do I fix a problem I created by installing a less safe hack?

Navigation

Early reviews of this site quickly pointed out that a table of contents is highly desired. Understand that this is incomplete, because the site isn't finished, but this does cover the first part of the site and what I view to be the most useful part of the site.

This site contains hundreds of Kilobytes of HTML. This table of contents contains only this page. As of this writing, the site is at least six times larger. Don't be afraid to explore, because if you do, you just might learn something!

  • More sections may be added.

    • Introductions

    Introductions to Xbox hacking and to this website.

    How does this site define a hacked Xbox?

    A hacked Xbox which was restrictive by disallowing certain activities, but which has since been given methods to perform the following specific prohibited actions:

    (See What one can do with a hacked Xbox)

    Users of a hacked Xbox have the above abilities, limited only by the data capacity ("disk space" limitations) of a physical or logical drive (partition) on the media that the Xbox uses.

    How does this site define "unsigned code"?

    The term "unsigned code" refers to code which does not have a signature that the Xbox's official BIOS would consider valid in its signature checking. (Such code actually possesses data in what is known as the XBE signature, but the signature may be rather random, and hence considered unsigned. Another possibility is that the code may be signed with a known signature like Habibi's key, but such signatures are fairly easy to create and manipulate, and therefore are really not any more special than a randomly signed "unsigned signature"). Another term often used for "unsigned code" on an Xbox is "home-brew software".

    "Xbox Hacking Community" Resources

    Disclaimer

    This information may not be accurate. I have done some things on this site. As of this writing, I have not done other things on this site. Some writing may have been written when the writer was lacking sleep. Some software may not have been fully tested. Some may have been fully tested and found to cause problems such as data corruption. Some may have been tested and had no problems found, but that's just because I haven't found them, and the problems may exist. Some software here can do things not normally done on an Xbox that has only ever run officially licensed software, such as making the LED on the front flash red or orange as well as green or off, or changing the fan speed which can affect the internal temperature of the machine. The owner of this website, the hosts of this website, and all entities associated with this website bear no responsibility for how any one visitor may decide to use or misuse any of the information on the page.

    This site is meant to communicate the knowledge I have about Xbox Hacking. In some cases, I may use phrases like "I think". When you don't see such phrases, it is because I do believe I know what I'm talking about. When you do see such phrases, it is for things that I haven't fully researched, likely because they are less important, but I still thought it would be better to share such knowledge so as to point people in what I am guessing is the right direction, rather than not sharing the knowledge at all.

    Warning about Linux's Data Corruption

    A bad Linux driver can cause corruption on a FATX file system partition. I have had to format the partition on my Xbox's hard drive that stores saved games, custom sound tracks, and similar user data (like extra costumes for DOA3 characters).

    I first posted about this problem on an X-S forum: See TOOGAM's post on this Xbox-Scene.Com Forum Topic (Text of that post on this site) for details I wrote then. Yet, despite this problem, Linux development continues and people seem to use Linux. What I suspect is one of:

    The last option could very well be what happened, and in that case, my warning may just be from old times and might be safely ignorable. I most certainly do not trust the file system driver of LiveLinux version 0.2, which I first came accross (not knowing its name) since it was bundled in a 007: Agent Under Fire saved game exploit package.

    Since I have not read how this problem has been solved, I've been acting like it hasn't. Therefore, I have this notice on this page, and I warn anybody who has an Xbox that I put LiveLinux 0.2 on to not use the software I just gave them.

    Warning about Copyright issues

    The most common way that Xbox software is created is using Microsoft's Development Kit, a set of software tools called the XDK which place copyrighted-by-Microsoft code in every executable that these tools make. Much of the software mentioned on this Xbox Soft Modding site was made with these tools, and therefore the general consensus is that these software products are not allowed to be distributed or in the posession of anybody except as allowed by a license agreement created by Microsoft. Any derivation from this is generally considered Copyright Infringement. This website is meant to be educational in order to minimize catastrophic errors (such as making an Xbox unable to boot) which some people might create without such documentation. This website does not pretend to know whether a visitor has acquired a license from Microsoft, nor does this website pretend to decide what legal risks the visitor may choose to take, nor does this website pretend to judge whether using XDK materials even is a breech of a real copyright or if that's just a well-propagated but false rumor. Since this is claimed to be an area of concern, though, one may wish to be aware of such issues.

    To obtain most of the XDK software, a visitor can go to what is often referred to as "the usual places".

    Who is this site for?

    This site is primarily targetted to those using software only to hack a system, although there is a bit of mod-chip-only information. Users of hardware-based mod chips may not need to know some of this information, but then again some information on this site may be good for such users as well (since both camps of users have common things such as alternate dashboards). Most if not all of the information on this site will work for those with and without a mod-chip (it's just that some of the information and procedures may be unnecessary for those with a working mod-chip).

    This site is meant to provide the information needed. There are many more sparse tutorials: Those who can get by with less information may or may not be better off reading a more sparse tutorial. Those who don't want important details skipped over, though, may love this site.

    Introduction

    This Xbox is a video game console with a hard drive. As it has a hard drive, it can be used as not only a video game console, but a capable Linux machine. However, there can be great difficulty reading, writing, and executing data on the hard drive when the data and location on the hard drive isn't something pre-approved by Microsoft. Originally accomplishing these things required adding a chip to the Xbox which modified the Xbox's behavior (and hence a chip that did this had the generic name "mod chip"). Now these things have become possible using a bare minimum of special hardware, and the techniques to accomplish these tasks are heavily based on using specially-designed software in order to accomplish what hardware mod chips used to be needed for. Because the results of these software-based modifications to an Xbox are similar in result to having hardware mod chips installed, installing such liberating software is called performing a soft mod.

    Why this site?

    I made this site for the same reason I partitipate in many of my projects, and for the same reason I have decided to make many web sites: I felt this site would fulfill a need for the community. Specifically, to have a list of hacking steps in order so people can know where to start.

    The reason for this site: I believe this site fulfills a task that provides benefit for people. Many people feel that they could accomplish the task if they can first just figure out what the task is. Some of these people may know how to use FTP, can unzip files, and can read documentation, but still have quite a bit they do not yet know about the steps necessary to take control of an Xbox. I have found that lots of other sites contain a lot of information, but there is too much information which is not organized in a fashion that is good for newcomers. A lot of writing documenting Xbox Hacking expects other knowledge of the hacking process, either from experience or from other readings. Newcomers would have great difficulty understanding even some simple things, and knowing what things mattered or not, and what information being read was old and obsolete, and what wasn't.

    The original idea of this site was to document all of the challenges, from writing to a hard drive to dealing with an Xbox's signature checking, and then to document the solutions. Separating these things became too cumbersome for viewing the information once this site reached a certain size. I have since streamlined this site by just providing a walkthrough, and allowing people to learn about the challenges as they are being overcome in the process of overcoming them.

    This site is meant mainly to convey my knowledge, and was started because I:

    The Steps To Hack An Xbox

    These are the steps of Xbox hacking. I would call this "How To Hack An Xbox In However-Many Easy Steps", but some of these aren't necessarily easy steps. These are just the steps to be taken, and with little flexibility, in this order.

    The Steps (attempt #(huge number) to make this section)

    Problems

    Do you see Error 21 or some other such Error screen? Check out Error Screens.

    Frequently Asked Questions And Unasked Questions And Answers

    Older Stuff

    All information below this section on the page is older material, which may be a duplicate of other material written elsewhere on the site.

    More Information

    Install what is needed to run unsigned code

    This may mean installing a mod-chip, or it may mean installing (writing) the unsigned code to the Xbox hard drive so that it can be executed.

    See How To Write To An Xbox Hard Drive

    What to write to an Xbox Hard Drive (a.k.a. How to write a saved game)

    Gain the Second Ability: Ability to store any data on any location of the file system of any writable storage device.

    Running unsigned code

    By the time user-decided-upon data is written to the hard drive, or very shortly after, the user is likely to spend some time figuring out what is the best data to put on the hard drive and where on the hard drive's file system the data should go. The preferable answer is: Place executable code on the hard drive, and put that code in a location where it can be run.

    The second ability comes rapidly after the first becomes quite successful. Once unsigned code can be run from the hard drive, files can be moved around on the hard drive using a file manager on the Xbox or by using an FTP client on a computer connected to the Xbox. (The latter case may require some networking knowledge.)

    Do not worry so much if running unsigned code is a tedius process, or has undesired requirements (like a commercial game that can be exploited by a hacked saved game). Simplifying this process is focused on in Step Seven: Make using unsigned code easier.

    Back up newly accessible information

    Gain the Third Ability: Ability to execute whatever code is desired from any storage medium accessible on the system, without having errors from signature checking.

    Defeat Signature Checking

    Users may want to skip this step long enough to perform the next step in order to remove any requirements needed to run unsigned code (like posessing a commercial game that can be exploited by a hacked saved game). Especially if the next step can be done quickly. However, the next step (installing more hacks) may take some time to learn how to accomplish the installation, especially if there are drawbacks that need to be dealt with. Meanwhile, this step may take a bit of time to get to work, but is pretty safe and straightforward.

    Mod-chip users may be able to skip this step. Soft Modders will likely want to quickly create easier ways to run unsigned code, and create ways to worry less about signature checking.

    nkpatcher, PBL.

    Clean-Up

    Make using unsigned code easier: Create another points of entry (that you plan to use)

    Once a mod-chip is installed, install a saved game exploit. Once a saved game exploit is installed, get a dashboard/XBE hack installed. Hackers have been known to try tinkering in different ways, and end up losing the ability to directly boot unsigned code using the primary entry method. Perhaps a new version of a mod-chip BIOS doesn't work as expected, or a dashboard update seals up a hole that has been used before, or an exploitable saved game's disc gets scratched and can't be read.

    Mod-chip users may be able to skip this step. Once a saved game exploit is installed

    XBE Hacks (previously most commonly referred to as "Dashboard hacks")

    Various Hacks

    Step Eight: Make Even More Points Of Entry
    Not only soft-modders, but also mod-chip users have been known to benefit from using a saved game exploit, after tinkering with files on the C: and making any dashboard there unbootable.
    Next Step: Be sure to do anything important
    A responsible person hacking an Xbox would probably have already already backed up an EEPROM, and maybe even the entire hard drive on the Xbox. However, there could of course be times when the directions are best not-followed, such as if the person is reasonably confident of not destroying the hard drive and if time pressures are involved, such as renting a game that has a saved game exploit or meeting someone breifly before some time limit will separate the two of you. Why back up someone else's Xbox hard drive when you don't expect to see that person again? If there is anything important, though, that hasn't been put off because people just wanted to see the hacks fully working, then it is recommended to surely do such important things at this stage before doing any of the more frivelous steps below.
    Next Step: Install more software
    Check out all the things you can do!
    Next Step: Final Call: Do Anything Important that is remaining
    For the really irresponsible who have waited this long definitely back up anything that should be backed up which hasn't been backed up by now. (I in fact, didn't. I performed the next step first.)
    (Optional (Sigh)) Step: Contribute
    Perform one or, as I did, more than one of the following:

    The most difficult steps for many is: Obtaining equipment/software needed, and writing to the hard drive, especially since an earlier step, Obtain information on the process, has proven to be quite challenging for some (in some cases because they may have tried to accomplish Step Two before some of the resources existed).

    Information on the Xbox Hacking Scene

    Installing Hacks

    Some things in this guide are really perfectly safe to do on any Xbox. Some are risky things that I have been reluctant to do on my Xbox, but ended up working without trouble. Some could damage an Xbox and I will not do this to my Xbox. Do not be afraid of the dangers, just do the things which are perfectly safe. This will in fact make your Xbox experience MORE safe than if you avoided the hacking scene altogether (because you can back up saved games to your computer, as well as your hard drive key which can help if your Xbox's hard drive ever fails for any reason). Only do the riskier things after carefully considering the possible benefit compared to the possible cost. This site breaks down the dangers for you.

    Using a Pre-Made Package

    Doing Things Yourself

    Ah, now here is the recommended way of doing things.

    Downloading Software
    Setting up very-safe saved game exploits (minimal)
    Setting up saved game exploits (advanced)
    putting additional software on memory card (so less work is needed later)) Getting memory unit to exploit any one of 3 games. Ideal for package distributors, those who intend to do this often, or those whose memory unit is far from a computer.
    Linux
    See safety warning
    Back up anything super-important (saved games)
    Tutorial of Evolution-X RemoteX FTP:
    literal remote mkd somedir (not mkdir somedir which becomes xmkd somedir) literal remote execute file rename (some concern about this?)
    If using Dashboard 4920 or earlier, and if no custom sound tracks (or if no fear of temporarily losing them), install best Audio Hack
    First backup old Sound File index. Then backup custom sound tracks? Then try one audio hack. If doesn't work, try another. This can run X-Select 0.9. Then have it run Evo-X (or can we run signed UnleashX, now that XBEDump's reports are known to be more rigid than required and different than what newer XDK uses?) Demonstrated ability to run unsigned code without commercial game.
    Defeat Signature Checking
    NKPatcher PBL versions
    Install other dashboard hacks
    Note that these may be more gutsy to install. UDE2 UDE Once installed, hex edit dash to look in C:\f0nts (with a zero) instead of C:\fonts by modifying the strings (stored in Unicode, with every other character being ASCII value zero)
    Installing more software
    What can do AvaLaunch - Telnet, IRC, ACAM skinning, etc. Emulators Homebrew games (MineXweeper, Connect 4, DeadBabies) Hacked Games (DOA3 skins, Halo hacks, Soul Calibur 2 changes) Linux installation
    End of installing really neat stuff. Now go do the responsible things, like backing up EEPROM, if that wasn't already done
    Sound Exploit MechAssault: "(Not Platinum or Game of the Year version)"
    Do whatever is less problematic: Installing a dashboard hack or installing PBL. Installing a safe dashboard hack: Run X-Select 0.9 / Evo-X Defeat Signature Checking: Installing PBL and alternate BIOS files or some similar such file (NKPATCHER/nkpatcher) Installing a different dashboard hack: UDE (more gutsy?) Installing some more software Linux installation UnleashX - unzips, uses keyboard, has FTP server, relatively easy to install Save HDDKey if not yet done Running other software Save HDDKey/EEPROM if not yet done Setting up saved game exploits (advanced: putting additional software on memory card)

    FAQ

    Can you run unsigned code, such as Linux, on any Xbox without using a modchip?
    Yes.
    Can you run unsigned code, such as Linux, without needing to using a hacked saved game or a modchip?
    It depends on the Xbox. And even those Xboxes where you can do this, the easiest/only way to do this initially may be to load a saved game.
    How do you run unsigned code?
    One of several ways:
    1. Run a commercial game which has exploitable saved game handling.
      Games Include
      • James Bond 007: Agent Under Fire (AUF). (Any release, either Original or Platinum.)
      • The original release of MechAssault (with a ???-colored sticker, not the Platinum release)
      • Splinter Cell
    2. Exploit a bug in an XBE file signed by Microsoft (namely, a bug in one of the releases of Microsoft's dashboards and/or the dashboard-updating program
      Games Include
      NFL Fever 2003 !Live
    3. Use a modchip
    What do I need for a software-based modification?
    What Xbox is best to have?
    Other than having an early kernel that doesn't interfere with running certain software, it isn't a very big deal. Here are good things, though: Of all these, having a pre-5530 kernel is good, and the rest doesn't matter much. With the advent of nkpatcher, it seems even the kernel version won't be as much of a big deal anymore. Some versions of some software that uses text mode, most notably some versions of Linux releases and Phoenix BIOS Loader, do not work so well with some video encoder chips, but this doesn't matter too much because newer versions of the software tend to add support for newer versions of the Xbox hardware.
    Concern that newer games would update dashboard on you. stable hdd hack only had audio cd option 5101 4920 Honorable mentions: I'm sure there are others, like the authors of certain dashboards, who are quite knowledgable. These are some of the names I've picked up over time. (check spellings) devz3ro - Hacker Catfish - Grospolina noted a post about the stable hard drive exploit. "Method discovered by Catfish (we all know who he formerly is) & mainly Mordenkainen, so no credit goes to me."" (No, I don't know who Catfish is. Oh well. (maybe devz3ro?)) Mordenkainen - has made package, Grospolina credits Mordenkainen for stable audio exploit. I think he also made a lot of posts to help people out. Grospolina - Knowledgable on various topics, posts useful information, does a good job of being accurate Angerwound - Unpleasant icon/sig perhaps, but knowledgable rmenhal (spelling checked) - hacker involved with UDE BenJeremy - posted "The Truth" on X-S's n00b guide. Seems to be in charge of X-Select. PedrosPad - involved with rh in creating the first version of UDE. ldots - on top of things, credited for creation of PBL-Lite, which he considers obsolete to Metoo edition. http://forums.xbox-scene.com/index.php?showtopic=245403&st=30 As for Error 13... that's a dashboard launch failure. Check that c:\xboxdash.xbe is the correct update.xbe, and that you've placed the fonts correctly. I thought it had to do with Hard drive locking... include:

    UDE2 http://forums.xbox-scene.com/index.php?showtopic=245403 upload files? http://24.170.16.12/upload/ http://forums.xbox-scene.com/index.php?showtopic=245403&st=60