RG34XX / muOS RECONSTRUCTION
Reconstruction guide — RG34XX port
A complete, validated public build recipe is not yet available. The files provide a starting point for studying and reconstructing the private V1.
This page explains what exists and what a new build still needs.
01 / WHAT IS PROVEN
What is proven?
Traceable work
You can inspect named patches, selected logs and source revisions.
A working rebuild
A new executable needs its own device tests. A validated public rebuild recipe is still needed.
Identical rebuilt bytes
Reproducing the private file exactly requires a complete build environment. Its hash alone is not that recipe.
02 / INPUTS
What inputs are available?
The repository contains 15 historical patches, a launcher, source identifiers and selected test records.
The foundation is EstebanPdN's Project Picori-derived source. The exact revision is recorded in the source baseline.
Four retained source snapshots do not form a complete final build environment. The full upstream tree is not included here.
03 / REFERENCE BUILD
Which build is the reference?
The acceptance record identifies an 8,858,736-byte private executable. It records one manual session with visual/audio OK, plus two preceding automated soaks.
Recorded settings include CPU/GPU ceilings of 936/420 MHz, an audio request of 1600 frames and three rendering threads.
These identify a tested private configuration. They do not establish a full playthrough or a successful public rebuild.
04 / SAFE STARTING POINT
Where should reconstruction start?
Use a separate worktree. Leave private V1, saves and earlier evidence untouched.
Inspect the pinned upstream and each patch's purpose. Some patches overlap; some only add diagnostics.
Do not apply every patch in filename order. Select compatible changes, then build and test each stage.
05 / MISSING STEPS
What is still needed?
- A complete source, dependency and toolchain list.
- A compatible patch order and exact build settings.
- Generated inputs, final processing steps and build logs.
- The new executable's fingerprint and fresh device tests.
Recalculating statistics is a different task. The analysis script is public, but the full raw traces remain in the private archive.
06 / DISTRIBUTION
Can a rebuilt package be shared?
Distribution needs a separate review. The recorded VirtuaAPU restriction remains unresolved for the private executable.
No ROM, extracted Nintendo assets, saves or private executable are included in this repository.
07 / FURTHER READING