简体中文 · English
IrisBox (虹膜空间) runs multiple Android userspaces inside a rooted Raspberry Pi 4 Android host. Install the APK, grant host Magisk root, import a compatible ROM, create an instance and start it.
This preview supports one matched Raspberry Vanilla AOSP 13 / ARM64 / Raspberry Pi 4 host profile. Instances share the host Linux kernel, with separate namespaces, Binder devices, overlays and app data. Root access alone does not make other devices or arbitrary Android ROMs compatible.
- Read the host and installation guide. The host needs the matched build, kernel capabilities, Wi-Fi and an already configured Permissive environment.
- Install host Magisk yourself, following its upstream installation instructions and the board's boot layout. IrisBox never installs or patches host Magisk.
- Install
IrisBox-0.1.4.apk. Open it and choose Authorize and check, then Install engine. - Choose Import ROM, select
IrisBox-rpi4-a13-aosp.irisrom, then Manage instances → New instance → Start → Enter. - Use EN / 中文 to choose System default, English or 简体中文. This changes the host App UI only; each guest keeps its own Android language and data.
Downloads and SHA-256 · GitHub Releases
The image illustrates the workflow; it contains no account or device data.
- ROM import with path, size, manifest and per-file SHA-256 checks; no installer scripts from ROM packages.
- Independent instance data, memory ceilings, resolution presets, lifecycle controls and optional guest Root.
- Live list previews, shared-buffer fullscreen display, mouse/keyboard/touch input and file exchange.
- Per-instance playback audio and software video support on the tested profile.
- Matched host image preparation, source provenance, build instructions and comparison with the previous Project Iris engine.
The public ROM contains AOSP and compatibility files, without Google apps or accounts. Optional Google support remains available for separately supplied, appropriately licensed matching components. Existing private Google-enabled instances retain their ROM and data. Guest Root uses the existing bundled component and per-instance switch; this is separate from installing host Magisk.
The published 0.1.3 test was blocked by a Play Protect certification warning. On October 24, the 0.1.4 test restored the catalog and actually installed Open Sudoku and Google Calculator from Play; device certification still has not passed. See the current results. Each guest needs its own custom-ROM registration where applicable; registration does not establish device certification.
Version 0.1.4/e21 adds Orientation → Follow app / Landscape / Portrait to the fullscreen toolbar, with live changes and saved per-instance selections. English/Chinese menus, rotated input and persistence across Guest restart passed device tests. Existing 0.1.3 users need the stopped-state engine maintenance upgrade described in building and recovery.
| Play installation in progress | Installed from Play | Tiantian Xiangqi running |
|---|---|---|
 |
 |
 |
Real device captures, cropped and privacy-redacted with owner permission; no AI redraw. The game image shows a puzzle board. The owner separately confirmed WeChat and QQ QR login/gameplay. In this list capture, instance 1 is stopped and instance 2 has a live preview. Screenshots do not establish Google device certification. Image details.
Version 0.1.3 requires a distinct User namespace per instance. Guest root maps to a dedicated unprivileged Host UID range, with no Host-UID0 fallback. Existing e13 installations need a stopped-state backup and migration; installing the APK alone is insufficient. See the migration and isolation guide.
The clean flash image has new, empty userdata and unmodified factory boot/system/vendor partitions. Static checks are recorded; a fresh USB-disk flash and first boot have not been tested. Existing-host validation does not establish a complete installation on a host that never ran the previous project. Other kernels/devices, Enforcing SELinux, camera/microphone, protected video, Play Integrity and arbitrary third-party Root modules are not covered.
This is an independent project. VMOS is mentioned only as a user-experience comparison; there is no affiliation. Internal names such as com.rootvmos.viewer, /data/rootvmos and .irisrom are retained to preserve upgrades and protocol compatibility.
See third-party notices and source provenance. Publishing this repository does not relicense third-party components; project-specific code currently has no blanket license grant. Signing keys, user data, accounts, raw device logs and screenshots are excluded.
The clean host preview is USB/sda only, with 12 GiB empty userdata for a 16 GB or larger USB disk. It is not an SD/mmc image.