How To Download And Use Cheats On An R4i Ace Card

Using cheat codes on an R4i Ace (a Nintendo DS flashcart) is all about working with a special file called a cheat database, then making sure your R4i knows where that file is and how to use it. Once you understand those basics, downloading and enabling cheats is mostly a matter of organization and compatibility.

Below is a clear walkthrough of how it works, what can change from one setup to another, and why there isn’t one single “right” method for every R4i Ace owner.


What “Cheats” Mean On An R4i Ace

On an R4i-type card, cheats are not built into the game. Instead, the R4i firmware (the menu software that appears when you boot the card) reads from a cheat database file and applies those cheats to the game as it runs.

A typical cheat setup involves:

  • Cheat database file
    Usually named something like:

    • usrcheat.dat
    • cheat.dat
    • usrcheat.dat inside a “cheats” or “system” folder
  • Flashcart firmware / kernel
    The menu/interface that shows your game list. This software:

    • Looks for the cheat file in a specific folder
    • Matches cheats to games using each game’s Game ID
    • Lets you enable/disable individual cheats before launching a game
  • ROM file of the game
    The .nds file. Cheats are tied to a specific version of the game (region + revision), so:

    • A cheat made for the EU version may not work for the US version
    • Patches or “trimmed” ROMs can sometimes change the ID and break cheats

In short: cheats live in a database; the R4i firmware reads that database and injects those effects into the game at runtime.


Step-By-Step: General Process To Get Cheats Working

Exact menus differ slightly between R4i Ace variants and firmware versions, but the overall flow is quite similar.

1. Check What Cheat Format Your R4i Ace Uses

Different R4/DS firmwares expect cheats in different places and formats. Common patterns:

Card / Firmware StyleCommon Cheat File NameTypical Folder Location
R4i-style “original” UIusrcheat.dat/_system_/ or /cheats/
Some clone/skin-based firmwarecheat.datRoot of microSD or /cheats/
Wood R4-basedusrcheat.dat/__rpg/cheats/ or similar

How to find out on your card:

  • Look in your microSD card for folders like _system_, __rpg, R4iMenu, or cheats
  • Open your R4i’s settings or help/about screen; some show the cheat file name or path
  • If there’s an existing usrcheat.dat or cheat.dat, note its location

You don’t need to know why the name matters; you just need to match the expected name and folder.

2. Get A Compatible Cheat Database

Most people don’t write their own cheats; they download a pre-made cheat database created for DS flashcarts. These databases typically include cheats for hundreds of games.

What matters for compatibility:

  • File type
    Your R4i Ace will most likely accept:

    • usrcheat.dat (very common)
    • cheat.dat (used by some older menus)
  • Database “type”

    • Some databases are tuned for R4/TTDS-style carts
    • Others are for different loaders (like CycloDS, etc.) For an R4i Ace, you’re usually looking for an R4/TTDS-compatible cheat database.
  • Recency
    Newer databases:

    • Cover more games
    • Contain more stable or fixed codes But even old databases often work fine if you’re playing older titles.

You generally download the file to your computer, then move it to the microSD card (explained next).

3. Copy The Cheat File To Your microSD Card

Once you have the correct cheat file:

  1. Turn off your DS/DSi/3DS.
  2. Remove the microSD from the R4i Ace, and put it in your computer.
  3. Back up your existing cheat file (if any):
    • If you see a usrcheat.dat or cheat.dat, copy it to your computer as a backup.
  4. Copy the new cheat database into the same folder the old one was in, or into the folder your firmware expects (as checked in step 1).
  5. Make sure the file name matches exactly what your firmware needs:
    • Rename if needed: for example, usrcheat.datcheat.dat, or vice versa.

Then safely eject the microSD, put it back into your R4i Ace, and boot the DS.

4. Enable Cheats For A Specific Game

The next step is done on the DS itself, inside the R4i interface.

Typical process (may vary slightly):

  1. From the R4i menu, highlight the game you want.
  2. Press the button your firmware uses for game settings (often Y, X, or a touch icon like a gear).
  3. Look for a Cheats or Cheat Options menu.
  4. You should now see a list of cheats related to that game (if the Game ID matches one in the database):
    • Enable a cheat by tapping it or pressing A
    • Some firmwares let you “Select All” or “Clear All”
  5. Save your cheat selection (often a “Save”, “OK”, or pressing A to confirm).

When you then start the game, the firmware injects the chosen cheats as the game loads.

If no cheats appear:

  • The game’s Game ID might not match what’s in the database
  • The ROM might be a different region or version
  • The cheat file might be in the wrong place or wrong format

Key Variables That Influence Whether Cheats Work

Even if you follow the general steps, several technical details can affect success.

1. Firmware / Kernel Version

Your R4i Ace firmware version directly affects:

  • Which cheat file name it recognizes
  • Which folder path it searches
  • Whether it supports larger cheat databases or only smaller ones
  • Menu options for enabling/disabling cheats

Older or unofficial/clone firmwares:

  • May have buggy or partial cheat support
  • Might require a specific custom build of a cheat file

Changing the firmware can fix cheat issues, but it can also introduce new ones, so people often stick to the version that’s stable for them.

2. Game Region, Version, And Game ID

Cheats are tied to a Game ID derived from the ROM’s internal data.

Variables that matter:

  • Region: US, EU, JP, etc.
    A database might have cheats only for certain regions.
  • Game revision: v1.0 vs v1.1, etc.
    Minor updates can change the memory layout, breaking cheats.
  • Patched ROMs: fan translations or hacks
    These nearly always change the Game ID.

If your ROM’s ID doesn’t match any in the cheat database, you’ll see:

  • No cheats listed for that game, or
  • Cheats that simply do nothing or crash

Advanced users sometimes use tools to edit the cheat database and adjust the Game ID entries to match their own ROM versions.

3. microSD Card Organization And Health

Your microSD card can quietly cause cheat problems:

  • Wrong folder structure
    If the file isn’t where the firmware expects it, cheats will never show.
  • File system issues
    Corrupted sectors or half-written files can make the cheat database unreadable.
  • Card speed and quality
    Rarely, a very slow or failing card can lead to strange behaviors, including cheat loading issues.

Keeping a simple, clearly organized folder layout helps minimize confusion:

  • Example: /R4iMenu/, /games/, /cheats/, etc., instead of deeply nested or mixed folders.

4. User Settings In The R4i Menu

Many firmwares let you toggle cheat support globally:

  • A main settings option like “Cheat Enable: On/Off”
  • A per-game toggle that disables cheats entirely

If this is turned off:

  • The cheat database may exist and be correct, but no cheats will apply in-game.

Checking both:

  • Global cheat setting
  • Per-game cheat selection

is important when troubleshooting.


Different User Profiles, Different Cheat Experiences

Not every R4i Ace user will approach cheats in the same way. A few typical patterns:

Casual Player: “I Just Want Infinite Lives”

  • Likely to use:
    • A single, pre-made cheat database
    • Only a few simple, stable codes (infinite health, max money)
  • Less likely to:
    • Edit cheat files
    • Change firmware
  • Experience:
    • If the database matches their game versions, setup is quick.
    • If not, they may assume cheats “don’t work” and stop trying.

Tinkerer: “I Want Full Control Over Every Code”

  • More willing to:
    • Use cheat editors on PC to modify usrcheat.dat
    • Adjust Game IDs manually
    • Maintain multiple cheat databases for different firmware versions
  • Experience:
    • Can get cheats working for obscure titles or patched ROMs
    • Invests more time, but gains flexibility and control

Multi-System User: “I Use Several Flashcarts”

  • May juggle:
    • Different file names and locations (cheat.dat on one card, usrcheat.dat on another)
    • Varying firmware capabilities
  • Experience:
    • Needs a clear mental map (or notes) of which card expects what
    • Often standardizes on one or two commonly compatible database formats

Preservation-Minded User: “I Don’t Want To Break Anything”

  • Priorities:
    • Backing up original cheat files before replacing them
    • Minimizing writes to the microSD
  • Experience:
    • Might keep several dated backups of cheat databases
    • More cautious about firmware updates, preferring stability over new features

Each of these profiles will follow the same basic logic—get the right database, put it in the right place, enable cheats—but they differ in how much they’re willing to customize and troubleshoot.


Why Your Own Setup Ultimately Decides The Exact Steps

The core idea of downloading and using cheats on an R4i Ace is fairly consistent:

  1. Identify the cheat file type and location your R4i Ace firmware expects.
  2. Download a compatible cheat database (usrcheat.dat or cheat.dat).
  3. Copy it to your microSD in the correct folder with the correct name.
  4. Enable cheats for each game through the R4i menu, making sure the ROM’s Game ID matches a database entry.

Where things diverge is in the details of your situation:

  • Which exact R4i Ace revision and firmware version you have
  • Whether your games are original region, patched, or trimmed
  • How your microSD is structured and whether there are legacy files from older setups
  • How comfortable you are with editing files or experimenting with different databases

Once you understand these moving pieces, the remaining question is how they line up with your particular card, games, and comfort level—and that’s the part only you can see directly on your own system.