GlitchMod tutorials

Getting Started and Firmware Decisions

Identify your installed system software, decide between official online use and preserving a research console, prepare backups, and evaluate homebrew instructions before changing anything.

3 min read Updated

Source check: October 10, 2026. Menu wording and project capabilities can change. Verify the linked primary documentation before following a procedure.

Start with a console inventory

The useful first step in PS5 modding is documenting the console you actually have. A model name such as “Slim” describes hardware; a firmware version describes installed system software. Neither substitutes for the other. Write down the full model identifier, installed version, whether a disc drive is present, available storage, and the activities you want to support. Keep this inventory privately: serial numbers, account details, and network addresses are unnecessary in a public help request.

Open Settings → System → System Software → Console Information to read the installed system software. This screen also provides network identifiers. Record the displayed version rather than assuming that the version on a seller’s listing remains installed. Reading this information is separate from selecting an update. Sony documents the path in its version-check guide.

Choose an operating goal

An everyday gaming console and a homebrew research console have different priorities. For everyday use, supported features, game requirements, account services, and security updates matter. Sony recommends current system software and notes that some content requires an update. For research, a specific public project may depend on an older version, a particular entry point, and additional payloads. A project’s exact requirements should drive that decision; “PS5 jailbreak” is too broad to establish compatibility.

Use a written decision: “I need current official online features,” or “I will keep this console on its recorded version while checking public homebrew support.” If you use one machine for both, accept that the goals may conflict. An advertised loader, SDK, or package does not prove that your firmware has a complete working exploit chain. Read the glossary before comparing projects.

Review automatic behavior

Sony places system update controls under System Software Update and Settings, including separate automatic download and installation switches. Game and app updates have their own controls under Saved Data and Game/App Settings → Automatic Updates. Rest-mode internet settings also affect background downloads. These are distinct settings, so reviewing only one switch is incomplete. See Sony’s automatic-update instructions.

If preserving firmware is your chosen goal, review those controls while the console is disconnected from the internet, then plan the network policy described in Networking and DNS. Do not interpret a DNS address as a guarantee that updates cannot happen. A game, service, manual USB operation, or later settings change can create a different update path.

Prepare before installing anything

  1. Create a list of irreplaceable saves and captures. Follow Backups and Save Data, and document when each copy was made.
  2. Bookmark the original repository for the project you intend to use. Read prerequisites, release notes, known issues, and the expected loader.
  3. Separate claims about entry-point support, kernel access, payload support, and application compatibility. Each is a different question.
  4. Keep a simple session log: project release, firmware, loaded components, and the result. Change one component at a time when troubleshooting.
  5. Read Recovery and Reinstallation before entering any destructive recovery screen.

For a normal supported update, Sony’s system-software page is the authoritative download source. Its update and reinstallation downloads serve different purposes. Do not select a reinstallation file merely because it is larger or sounds more complete. A reset, a backup restore, and a firmware change are separate operations; none should be assumed to return a research console to an earlier exploitable version.

Use Model Identification for hardware details and Firmware Compatibility to check each public exploit chain separately from its payloads.

Primary sources