Softmod vs Hardmod vs TSOP flash: which should you choose?

Three roads to the same place

Every route to a modded Original Xbox ends up in roughly the same destination: a custom dashboard, homebrew and emulators, media playback, network file transfer, and the ability to run a bigger hard drive. What differs is how you get there — and how much you’re risking on the way.

The three routes:

1. Softmod — software only. Exploits the console’s own save-game handling to install a custom

dashboard on the hard drive. No soldering, no hardware, fully reversible.

1. TSOP flash — reflash the BIOS chip that is already soldered to the motherboard. Requires

bridging points on the board and a working softmod to perform the flash. No added hardware.

1. Hardmod (modchip) — fit a physical chip to the console’s LPC header that supplies a

replacement BIOS at boot. The most capable, the most soldering.

This guide helps you pick. The short version: most people should softmod, and the main reason to do anything else is a dead or replaced hard drive.

The decision table

Route 1 — Softmod

What it is. The Xbox loads game saves from the hard drive. A specially crafted save exploits that process to run code, which installs a custom dashboard onto the console’s E: partition. Nothing on the board changes.

What you need

• A console that boots normally on its original, working hard drive. This is the hard

requirement. The Xbox HDD is locked to the motherboard’s EEPROM — a drive from another console won’t work, and a dead drive means no softmod.

• A way to get the save file onto the drive: a USB stick plus an Xbox-to-USB adapter.
• Rocky5’s Xbox Softmodding Tool, the current standard for this. Open source, GPL v3.

Our Xbox Softmodding Kit is exactly that hardware side in one box: a USB stick pre-loaded with the softmod files plus a USB-to-Xbox adapter.

Which revisions? All of them, 1.0 through 1.6b. This is the big one. Because it’s software on the hard drive, it does not care that a 1.6 can’t be TSOP flashed and needs an LPC rebuild for a chip.

Where it can go wrong. ⚠️ Softmodding is low-risk but not zero-risk. The two reliable ways people break a console: deleting the wrong files from the E: partition, and misusing FTP or the disk tools afterwards. Read the entire procedure before starting, don’t improvise, and don’t stop halfway. Also note that a softmod is only as durable as the hard drive it lives on — when that drive dies, the mod dies with it.

Choose this if: your console boots on its original drive and you want the result without the risk. Which is most people.

Route 2 — TSOP flash

What it is. The BIOS lives on a flash chip soldered to the motherboard — a TSOP package, hence the name. Bridge the right points on the board to make that chip writable, then flash a custom BIOS onto it. You end up with a hardmod-like result with no extra hardware in the console.

What you need

• A revision 1.0 to 1.5. Full stop. 1.6 and 1.6b cannot be TSOP flashed.
• A soldering iron, for bridging the write-enable points on the board
  • A way to run the flashing software, which in practice means a softmod first.

  The trade-off. TSOP is elegant: no chip, no ribbon cable, nothing to come loose, and the mod survives a hard drive swap. It’s also the only route here where a mistake can leave you with a console that won’t boot at all.

  ⚠️ Bricking is a real outcome. A failed or interrupted flash overwrites the BIOS the console needs to start. Recovery generally means an external programmer or a modchip to boot from instead — which is to say, recovery requires either equipment or skills you may not have. Don’t flash a console you can’t afford to lose, don’t flash on a flaky mains supply, and don’t flash without reading the specific procedure for your revision.

  Choose this if: you have a 1.0–1.5, you can solder, you want the mod to survive hard drive changes, and you’d rather not buy or fit a chip.

  Route 3 — Hardmod (modchip)

  What it is. A small board that attaches to the LPC header on the motherboard and provides a replacement BIOS at boot, independent of the hard drive and independent of the onboard flash.

  What you need

  • A modchip and the soldering skill to fit it. ⚠️ **Note: OGXMods does not currently stock

  modchips** — this section is here because it’s part of an honest comparison, not because we’re selling you one.

  • On a 1.6 or 1.6b, an LPC rebuild first: the LPC header on those boards isn’t fully

  populated, and the missing components have to be added before a chip will talk to the console.

  Why people do it anyway. A modchip is the only route that works on a console with a dead or already-replaced hard drive, because the BIOS comes from the chip rather than from the drive. It also opens the door to modern BIOS options such as Cerbios, and it’s the most robust setup for a console that gets used hard. Remove the chip and the console is stock again.

  Choose this if: your hard drive is dead or swapped, or you have a 1.6 and want BIOS-level capability, or you simply want the most capable and durable setup and can solder.

  So which one?

  Your console boots on its original hard drive → softmod. Start with the Xbox Softmodding Kit.

  You have a 1.6 or 1.6b → softmod, unless the hard drive is gone. TSOP is off the table entirely.

  Your hard drive is dead or came from another console → modchip. A softmod has nothing to install onto, and TSOP flashing generally needs a working softmod to get started.

  You have a 1.0–1.5, you solder, and you want it chip-free and drive-independent → softmod first, then TSOP flash from there.

  You’re not sure which revision you have → stop and find out: Which Original Xbox revision do I have?

  One thing to do before any of this

  If your console is a revision 1.0 to 1.5, check the clock capacitor before you mod anything. There is no point installing a beautiful dashboard on a motherboard that is quietly dissolving itself. It’s a sub-hour job and it’s the difference between a console that lasts another twenty years and one that doesn’t: How to replace the Original Xbox clock capacitor

  FAQ

  Is modding my own Xbox legal? Modifying hardware you own is generally fine. What you do with it is the part that matters: running homebrew, emulators you have the rights to use, media playback and backups of your own discs is the intended use. Downloading commercial games you don’t own is not, and we don’t help with it.

  Will a softmod stop me playing original discs? No. A modded console still plays your retail games.

  Can I undo a softmod? Yes. Rocky5’s tool includes an uninstall path that returns the console to stock.

  Does modding let me play online? Xbox Live for the Original Xbox is long dead, but the community-run Insignia service has replaced it. The Skeleton Key payload we stock includes an Insignia setup assistant.

  Can I use a bigger hard drive? Yes — that’s one of the main reasons people mod. The specifics (drive size limits, IDE vs SATA adapters, cable requirements) deserve their own guide; the 40-Pin 80-Wire IDE Cable is the part you’ll need either way.

  Which is fastest? Softmod, comfortably. Kit in hand, it’s an evening.

  What you need from us

  • Xbox Softmodding Kit — USB stick with Rocky5’s Xbox Softmodding Tool pre-loaded, plus a

  USB-to-Xbox adapter. The complete hardware side of a softmod.

  • USB with Skeleton Key Payload — a broader toolkit: PrometheOS boot menu, Rocky5’s softmod

  v1.2.2, XCAT, Insignia setup assistant, gamepad tester, MemCheck and XDON. Supplied with an Xbox-to-USB PCB.

  • USB to Xbox Port Adapter Cable / Original Xbox to USB Adapter — if you already have a USB

  stick and just need the adapter.

  • USB Xbox Memory unit — memory-unit form factor USB device for save transfers.
  • 40-Pin 80-Wire IDE Cable — for when the mod is done and the hard drive upgrade starts.
  • Set of motherboard capacitors (excluding clock capacitor) — the repair you should do before the

  mod, not after.

  Stuck on which route fits your console? Tell us the revision and whether the original hard drive still works, and we’ll tell you straight.

  A note on the “1.5”

  You will see version 1.5 mentioned in older guides and forum posts. It is worth knowing that no such board has ever actually been confirmed. The reports date back to around 2004 and are now generally thought to have been in error, so it is likely no console was ever built to that specification. Where we mention 1.5 below, read it as a revision that was long assumed to exist rather than one you are likely to be holding.

  Which pads you bridge, per board

  The BIOS chip is write protected from the factory, so before anything can be written to it you have to bridge a couple of points on the board. Which points depends on the revision — and not in the way people often assume. 1.0 and 1.1 are the same as each other; the split is between those two and the 1.2–1.4 range.

  • 1.0 and 1.1 — bridge R7D3 on the top of the board and R7R4 on the underside.
  • 1.2 to 1.4 — bridge R7D1 to R7D2, and the R7D10 pads together, both on the top side.
  • 1.6 and 1.6b — no TSOP at all, so this route does not exist. Those boards keep their firmware in the Xyclops chip, which is flashed a different way.

  One catch on the early boards: if the chip is marked SHARP, a plain bridge is not enough. You have to run the R7D3 connection out to a switch, boot with it open, and close it once you are in a dashboard. Only two flashing tools handle a SHARP chip at all, so check the marking before you start.

  Chip sizes differ too, which matters when you pick a BIOS: 1 MB on 1.0 and 1.1, 256 KB on 1.2 through 1.4.

  Does a TSOP flash need a softmod first?

  Not a permanent one, but you do need a way in. The flashing tool has to run on the console, and a stock console will not run unsigned code, so you use an exploit to get there — either a dashboard exploit or a game save exploit. Both work from a stock machine. What you cannot do is flash the TSOP with a modchip running, because the chip is not reachable while the modchip is in charge.

  Two warnings worth repeating, because both are permanent: do not inject configuration files into a BIOS image, and do not flash a BFM BIOS to the chip. Those are meant to be loaded a different way and will leave you with a console that needs a hardware programmer to recover.

  How big a hard drive can it take?

  Most dashboards top out at 2 TB. Larger drives can work, but only under a dashboard that understands the extra partitions needed to reach the space, such as XBMC. Below that ceiling, the practical limit is what your adapter and cable will do, not the console.

  What you need to softmod

  If you decided the software route is right for you, this is the hardware side of it.

  • Xbox Softmodding Kit — Everything for the software route in one package.
  • USB with Skeleton Key payload — A USB stick with the Skeleton Key payload already on it.
  • Original Xbox to USB Adapter — Connects a standard USB stick to a controller port.
  • USB Xbox Memory unit — A memory unit the console reads as its own, for save-game based exploits.