MTP ECU PHONE PROTOTYPE001 is Montpellier ECU's experimental reuse terminal, based on a Microsoft Lumia 950 retaining Windows 10 Mobile 15254.603 ARM32. Documented installations and trials are distinguished below from functions awaiting validation.
Independent project, not affiliated with Microsoft. This is neither an official Microsoft Lumia edition nor a commercially available product. The MTP Shop adds no platform fees; Base network fees may apply depending on the operation.
PC preview of the interface prototype: internal MTP engine in a sandbox, with SAFE / ALPHA status. This visual is not a Lumia screenshot and does not constitute hardware evidence. Native installations and tests rely on separate diagnostics, summarised in the timeline.
The hardware already exists. We are building a second life through software, without replacing Windows 10 Mobile or erasing the phone's history.
An internal local MTP engine, not CMD, DOS or Unix. The SAFE terminal passed targeted tests; CODEX LIVE displays read-only events sent from a PC. Base viewing belongs to MTP LIVE, which is partially validated.
Experimental prototypePublic balances, public QR codes and history are explored uses, with no overall Lumia validation claimed. The link opens the read-only web wallet, separate from the phone's apps. No seed phrase or private key.
Open the read-only Wallet ↗The shop and creations give a physical presence to the connection between objects, software and the local economy.
No added platform fees. Only potential Base network fees may apply.
Open the MTP Shop ↗Prototype 001 does not replace Android, does not present itself as a certified Microsoft device and does not promise current Windows 10 Mobile support.
It preserves the Windows Phone spirit and explores a new local purpose: a real, identifiable and demonstrable object.
The evidence does not fully validate the phone or pack. CODEX LIVE receives technical facts from the PC: it is not embedded AI. The described network and blockchain operations are read-only, without signing or transactions; the local terminal can write in its own private space.
No actual signing integratedEach step must answer one simple question: does this function truly make the Lumia more useful as an MTP ECU Phone?
The terminal and CODEX LIVE were installed and tested on the device on 7 October 2026. PC previews do not replace those native diagnostics.
Twelve parsing and containment self-tests passed on Lumia on 7 October 2026. Interactive commands, touch input and long-term stability still need testing.
MTP LIVE: initial HTTPS reads and chart documented. QR, shop integrations, the complete pack and 3D experiments still need completion or validation through explicit action.
Documentation status as of . All times below are Paris time (UTC+02:00). These are historical observations, not live checks of the phone.
7 October 2026, 16:47–16:48 — Terminal SAFE 1.0.3.0: installed, targeted tests passed. Launch accepted at 16:47:45; native diagnostics read back at 16:48:35, with twelve successful parsing and containment self-tests. Windows.Mobile and build 10.0.15254.603 are reported. HTML/JavaScript apps use neutral UWP packages running on the ARM32 OS, not ARM64 executables. Not all interactive commands are validated.
7 October 2026, 18:19 — Device Portal: documented access. Official system and inventory APIs respond successfully. The observed OS version corroborates Windows 10 Mobile 15254.603 ARM32. Later interruptions are recorded: no permanent portal availability is promised.
7 October 2026, 18:29 — CODEX LIVE 1.0.7.0: native feed tested. The terminal update receives events from an actual PC test over an encrypted connection. The Lumia runtime reports sixteen rendered and acknowledged events, including the successful test result. These are application diagnostics and acknowledgements, not a screen photograph. No remote PC control or phone-local AI model is demonstrated. SAFE is an earlier milestone of the same terminal.
7 October 2026, 19:09 — MTP Reader 1.0.0.0: installed, reading not validated. The native runtime loads a three-page document, but diagnostics record zero rendered pages. Prepared fixes and PC tests do not prove functional reading on the device.
7 October 2026, 20:57 — MTP IA VOICE 0.1.0.0: installation documented, voice validation pending. Installation status indicates success, then the app appears in the inventory; this time comes from report files. At 21:00, a portal interruption occurs before the launch request. No native launch, microphone, French recognition or audible welcome is validated in the examined records. The earlier summary stating that the app was not installed is superseded by this milestone.
7 October 2026, 22:09 — MTP LIVE 0.1.0.0: installed, partial native validation. Launch and native diagnostics document HTTPS responses, completed initialisation and a six-point chart reported as drawn. Physical touch and background execution are not established; the tile is not pinned. Market data includes warnings and a degraded state: the MTP/EURC spot remains indicative, approximated in euros, not an execution price. Version 0.1.0.1 is prepared and signed, without examined installation evidence.
7 October 2026, 16:45–22:08 — Microsoft applications: package presence corroborated. Inventory comparison increases from 121 to 125 entries. All 54 initially inventoried Microsoft-published packages are found with the same full identity. These are inventory-file times. This is not an exhaustive audit of accounts, settings, private data or every application's operation, nor a complete system backup.
The software pack, additional utilities, multimedia, games and 3D experiments are not globally validated. The recorded PC regression has 26 passes and one failure related to a missing personalisation file. PC tests and package preparation do not replace device testing.
The examined records document no OS replacement or removal of inventoried Microsoft packages. No general compatibility, security or long-term stability guarantee is inferred. The project remains independent of Microsoft, experimental and not commercially released.
This timeline publishes only a summary of evidence and its limitations. No raw report, device identifier, local network address, secret or private data is published.