Skip to content

← Firmware Downloads

Post-install setup · Reborn (Y2Linux) · Y2

Current non-root system baseline

Debian-based Linux with a fast clickwheel interface for the Innioasis Y2.

Instructions published by the project, shown here word for word.

Current non-root system baseline

> **Historical record.** The dates, candidate identity, "current" claims, > next steps and permissions below belong to this recorded boundary. See > [current state](../CURRENT_PLATFORM_STATE.md) for the latest physically observed result.

Date: 2026-09-08. Task: Y2E-105. Capture: 20260908-stock. One authorized USB target was selected explicitly for all remote commands; its serial and full properties remain private. No device state was intentionally changed.

Method and status

Host ADB: 1.0.41, platform-tools 37.0.1-15733141, /opt/android-sdk/platform-tools/adb. Initial sandbox USB/ADB access was denied; the host-side permission retry succeeded. This is distinct from device-side access denial. Commands were captured separately with a 15-second host timeout. The first status-marker attempt failed because the device lacks printf; its diagnostic output was retained. The compatible form was <read command>; y2_rc=$?; echo __Y2_REMOTE_EXIT__=$y2_rc. Both host status and remote marker are retained. Device clock is recorded separately; host UTC anchors the session.

EvidenceResultScope
idCONFIRMED uid 2000 shell, SELinux context u:r:init_shell:s0Non-root only; no privilege changes attempted.
/proc/versionCONFIRMED Linux 3.4.67, GCC 4.7, SMP PREEMPT, build timestamp June 1 2026Version string alone does not exclude a patched kernel.
/proc/cpuinfoCONFIRMED MT6582, Cortex-A7 part 0xc07, ARMv7, NEON/VFPv4Revision string 0000 is not a physical PCB-revision identification.
Selected propertiesAndroid 4.4.2/API 19, model/board/device Y2, ro.hardware=mt6582Current runtime evidence supersedes assumptions about hardware property resolution.
Build identityY2/Y2/Y2:4.4.2/KOT49H/1786599642:user/test-keys, display Y2-v1.0.0Device is not certified stock. Exact installed boot/system image hashes and installation lineage remain UNKNOWN.
Security/USB propertiessecure=1, debuggable=0, adb.secure=1; mass_storage,adbConsistent with secure non-root ADB; does not uniquely identify an image.
/proc/meminfo, interrupts, iomem, CPU topologyCOLLECTEDEvidence available for later memory/IRQ analysis; do not treat an incomplete reservation map as boot-ready.
/proc/modulesEMPTY successful observationNo loadable modules listed at capture; built-ins remain possible.
/proc/cmdline, dmesgDENIED, remote 1 while ADB host 0No root/su workaround.
uname -aUNAVAILABLE, remote 127 while ADB host 0Use the separately captured proc version.
config.gz and exported DT pathsUNAVAILABLE, remote 1No exported tree/config; embedded config/DT remains an offline question.
Module/firmware directory metadataPARTIAL; aggregate remote 1/system paths list entries while /vendor/lib/modules and /vendor/firmware are absent. Do not discard the successful portion.
dumpsys batteryCOLLECTED but internally conflictingRepeated status/present/level fields disagree (100/50 and true/false). Do not infer battery health or adequate recovery power from this service alone.

Firmware names include WIFI_RAM_CODE_MT6582, other Wi-Fi variants, WMT_SOC.cfg, MT6572/82 patch blobs and an mt6627 directory. /system/lib/modules/wlan.ko points to wlan_consys_mt6582.ko; the listing alone does not establish that the target exists or is loaded. No firmware was executed and no radio state was toggled.

Mount evidence shows read-only /system, writable /data, /cache, /protect_f and /protect_s, plus mounted internal and removable-card media. USB composition does not prove storage is safely quiesced for a raw snapshot. Protect/calibration candidates are mutable mounted filesystems at this point.

Review decision

The access baseline is complete, including denials and missing exports. The target is a non-root stock-family Android system; exact installed provenance remains unknown. This is sufficient for Y2E-110 to read partition metadata only. It is insufficient for raw partition acquisition, any recovery write or Linux boot. Battery service inconsistency is recorded as a separate observation for later passive power investigation.

Published by the schulzcode/y2linux project [1] [3]