software:stock_firmware
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| software:stock_firmware [2026/10/11 15:31] – external edit 127.0.0.1 | software:stock_firmware [2026/10/24 16:49] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Stock firmware 0051 ====== | + | ====== Stock Firmware |
| (MX64_V2.01.0051.05-9-R-210326) | (MX64_V2.01.0051.05-9-R-210326) | ||
| Line 9: | Line 9: | ||
| ===== Which file fits my car? ===== | ===== Which file fits my car? ===== | ||
| - | All three downloads contain the same operating system 0051; they differ only in the apps, the **app build**. Take the one that fits your car: under '' | + | All five downloads contain the same operating system 0051; they differ only in the apps, the **app build**. Take the one that fits your car: under '' |
| ^ AP version ends in ^ Download ^ Status ^ | ^ AP version ends in ^ Download ^ Status ^ | ||
| - | | **-052** | '' | + | | **_052** | stock-0051-ap052-raw.zip | flashed several times on our test head unit | |
| - | | **-060** | '' | + | | **_060** | stock-0051-ap060-raw.zip | flashed on our test head unit (11 October 2026), app build 060 afterwards | |
| - | | **-104** | '' | + | | **_102** | stock-0051-ap102-raw.zip | flashed on our test head unit (15 October 2026), app build 102 afterwards | |
| + | | **_104** | stock-0051-ap104-raw.zip | flashed on our test head unit (11 October 2026), app build 104 afterwards | | ||
| + | | **_108** | stock-0051-ap108-raw.zip | flashed on our test head unit (24 October 2026), app build 108 afterwards | | ||
| - | * With firmware 0051 the **System version** ends in **-060**. If it ends in **-052**, your car still has an older firmware, e.g. 0046 — then each of these sticks is an update of the operating system (see above). | + | * With firmware 0051 the **System version** ends in **_060**. If it ends in **_052**, your car still has an older firmware, e.g. 0046 — then each of these sticks is an update of the operating system (see above). |
| * Other app builds (e.g. 076 or 086) we don't have yet. | * Other app builds (e.g. 076 or 086) we don't have yet. | ||
| + | * Which AP, System and MCU versions belong together: [[: | ||
| * The apps of 060 and 104 come from backups of cars that were still in their original state — not from a manufacturer package. Both backups were checked: no trace of ADC in them. | * The apps of 060 and 104 come from backups of cars that were still in their original state — not from a manufacturer package. Both backups were checked: no trace of ADC in them. | ||
| + | * The apps of 102 and 108 were checked too: no trace of ADC in them. | ||
| + | * **102, 104 and 108** speak a different " | ||
| ===== What's inside ===== | ===== What's inside ===== | ||
| - | ^ File ^ Contents ^ | + | Each download is the image of a USB stick: one FAT32 partition holding exactly these three files. |
| - | | '' | + | |
| - | | '' | + | * **imx6.bin** — The original operating system 0051: kernel, recovery, Android system and configuration |
| - | | '' | + | * **imx6ap.bin** — the apps (vendor partition, app build 052, 060, 102, 104 or 108 depending on the download), the data image and the boot logo — data image and logo are identical to version 0046 in all five downloads, and so are the apps in the 052 download |
| + | * **imx6.ini** — the flash instructions: | ||
| ===== Download ===== | ===== Download ===== | ||
| - | ^ File ^ Size ^ SHA-256 | + | ^ App build ^ Download |
| - | | {{: | + | | **052** |
| - | | {{: | + | | **060** |
| - | | {{: | + | | **102** | {{: |
| + | | **104** | ||
| + | | **108** | {{: | ||
| + | |||
| + | SHA-256 of the downloads: | ||
| + | * 052: '' | ||
| + | * 060: '' | ||
| + | * 102: '' | ||
| + | * 104: '' | ||
| + | * 108: '' | ||
| + | |||
| + | We tested the image format on 18 October 2026 on our test head unit and in a car. | ||
| + | |||
| + | ===== Writing the stick ===== | ||
| + | |||
| + | The ZIP contains an '' | ||
| - | Unzip the three files '' | + | - Unzip the ZIP (right-click › **Extract All**) — that gives the '' |
| + | - **Windows: Rufus** ([[https:// | ||
| + | - **macOS: dd** in the Terminal: '' | ||
| + | - **Linux: dd** — '' | ||
| + | - ⚠️ With '' | ||
| + | - Afterwards the stick shows a 750–860 MB drive with exactly | ||
| + | - balenaEtcher works on many computers too; if it stops with "The writer process ended unexpectedly", | ||
| Line 41: | Line 68: | ||
| ==== On a car that already has an Aiways Drivers Community firmware ==== | ==== On a car that already has an Aiways Drivers Community firmware ==== | ||
| - | - Switch the car on and plug the stick into the **USB port in the centre console**. A window should open automatically with the message | + | - Switch the car on and plug the stick into the **USB port in the centre console**. A window should open automatically with a row like **Stock Firmware · AP _102** (from ADC 0.14.15 on it names the stick' |
| - After a check of the correct version, this firmware is installed automatically. Some interesting effects happen along the way — don't let them confuse you. First a white screen builds up from top to bottom, then the head unit reboots a few times with different messages. In between it's completely dark for a moment, nothing dramatic. Since the bootloader can't be overwritten, | - After a check of the correct version, this firmware is installed automatically. Some interesting effects happen along the way — don't let them confuse you. First a white screen builds up from top to bottom, then the head unit reboots a few times with different messages. In between it's completely dark for a moment, nothing dramatic. Since the bootloader can't be overwritten, | ||
software/stock_firmware.1791725490.txt.gz · Last modified: by 127.0.0.1