Differences

This shows you the differences between two versions of the page.

--- software:stock_firmware [2026/10/08 17:32] – created - 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)
-The head unit's original software — **MX64_V2.01.0051.05-9-R-210326** — to bring a modified head unit back to its factory state, or to repair one.
+**Not suitable for cars with a different original firmware**
-**Only for head units of the same line.** It is made for ''MX64_V2.01.0051.05-9-R-210326'' (shown under Settings › About). Our bench head unit runs it. Other versions of the same ''…05-9…'' line, such as 0046, should take it like an update — not yet tested by us. The flash replaces the operating system, the apps and all data as one set: a head unit of a different line must not get it.
+This version is only suitable for cars on which this same version is or was installed. See ''Settings › About''.
+For older versions of the same car type with a software version of the ''…05-9…'' line, e.g. 0046, this version would be an update, but that has never been tested in a real car. Flashing this version from a USB stick completely replaces the operating system, apps and all data. A head unit that had a newer version installed, or a car of a different line, should not get this version — it may then no longer be compatible with the instrument panel.
-===== What is in it =====
+===== Which file fits my car? =====
-^ File ^ Content ^
+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 ''Settings › About'' tap the version entry about **5 times**; then the **System**, **MCU** and **AP version** are shown. The **AP version** ends in your app build. **Write it down before flashing** — afterwards the car shows the stick's version.
-| ''imx6.bin'' | the operating system 0051: kernel, recovery, Android system and configuration (the bootloader copy inside is never written) — taken from an unmodified 0051 head unit and checked to contain none of our changes |
-| ''imx6ap.bin'' | the apps (vendor partition, app build 052), the data image and the boot logo — byte for byte the original Aiways package 0046 |
+^ AP version ends in ^ Download ^ Status ^
-| ''imx6.ini'' | the flash instructions (ours): writes boot, recovery, system, vendor, data and logo — **never** the bootloader and **never** the MCU firmware |
+| **_052** | stock-0051-ap052-raw.zip | flashed several times on our test head unit |
+| **_060** | stock-0051-ap060-raw.zip | flashed on our test head unit (11 October 2026), app build 060 afterwards |
+| **_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).
+  * Other app builds (e.g. 076 or 086) we don't have yet.
+  * Which AP, System and MCU versions belong together: [[:software:versions|Head unit versions]].
+  * 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 "language" with the MCU than 052 and 060: never flash them onto a car with MCU version _030, _052 or _060 ([[:software:versions|Head unit versions]]).
+===== What's inside =====
+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: writes boot, recovery, system, vendor, data and logo, but **never** the bootloader and **never** the MCU firmware
-⚠️ The apps are those of **app build 052**. A car that ran a different app build (060, 104, …) has build 052's apps after the flash.
 ===== Download =====
-^ File ^ Size ^ SHA-256 ^
+^ App build ^ Download ^ Size ^
-| {{:downloads:stock-0051-usb-stick.zip|stock-0051-usb-stick.zip}} | 740 MB | ''c53cc9516f39ca624351d20f281a951637bf49550995ab2ccadce3c8d649090c'' |
+| **052** | {{:downloads:stock-0051-ap052-raw.zip|stock-0051-ap052-raw.zip}} | 318 MB |
+| **060** | {{:downloads:stock-0051-ap060-raw.zip|stock-0051-ap060-raw.zip}} | 330 MB |
+| **102** | {{:downloads:stock-0051-ap102-raw.zip|stock-0051-ap102-raw.zip}} | 360 MB |
+| **104** | {{:downloads:stock-0051-ap104-raw.zip|stock-0051-ap104-raw.zip}} | 360 MB |
+| **108** | {{:downloads:stock-0051-ap108-raw.zip|stock-0051-ap108-raw.zip}} | 360 MB |
-Unzip it and copy the **three files** — ''imx6.ini'', ''imx6.bin'' and ''imx6ap.bin'' — to the **top level** of a **FAT32** stick. Nothing else on that stick: no ''update.zip'', ''update_os.zip'' or ''ota_update.ini'' (two jobs on one stick compete at the restart, and either may win) and never an MCU firmware file.
+SHA-256 of the downloads:
+  * 052: ''6ebaee81a2ab64c03ad25599356c33d9079a62f4b097d72e5a471e70dffe86b3''
+  * 060: ''3f9f5e7e92d06b33e1453be0803c8b640dfe38c8e0a4916344a2f93bcd7c8475''
+  * 102: ''e6c44ddeaab4c62009978bc0d22f35469f7dc382aa9df6cf52b61c9b8c482047''
+  * 104: ''fcb3f6dcde5000aa1bcb67d7045650395e350413856c826bc65cbd10ee89c278''
+  * 108: ''099c0e09dd48521589b234d489371dee62f6d4c4685dae42e28fad9eb383d8ad''
-===== Flash =====
+We tested the image format on 18 October 2026 on our test head unit and in a car.
-**Everything on the head unit is erased:** ADC, paired phones, Wi-Fi networks, settings. The 3D parts catalogue on the internal storage stays.
+===== Writing the stick =====
-==== On a car with ADC ====
+The ZIP contains an ''.img'' file: the image of a complete USB stick. It is **not copied** but **written** onto the stick with an imaging tool. Afterwards the stick is byte for byte the one we tested, however it was formatted before. This **erases everything on the stick**. Any stick of 1 GB or more will do.
-  - Plug the stick into the **front USB port**. The Connect app opens a box with a row **Stock firmware 0051** — press **Revert** and confirm.
+  - Unzip the ZIP (right-click › **Extract All**) — that gives the ''.img'' file.
-  - Connect checks the stick first (the flash instructions, no MCU firmware, the stick is the first USB drive) and then restarts into the flash.
+  - **Windows: Rufus** ([[https://rufus.ie|rufus.ie]], the portable version needs no installation): pick the stick under **Device**, open the ''.img'' file with **SELECT**, press **START**, confirm the erase and wait until the status says **READY**.
+  - **macOS: dd** in the Terminal: ''diskutil list'' shows the stick (e.g. ''/dev/disk4''), then ''diskutil unmountDisk /dev/disk4'' and ''sudo dd if=stock-0051-ap060-raw.img of=/dev/rdisk4 bs=1m'' (adjust the file name and the number).
+  - **Linux: dd** — ''lsblk'' shows the stick (e.g. ''/dev/sdb''), then ''sudo dd if=stock-0051-ap060-raw.img of=/dev/sdb bs=4M conv=fsync status=progress''.
+  - ⚠️ With ''dd'', make sure it really is the stick — a wrong device overwrites another disk.
+  - Afterwards the stick shows a 750–860 MB drive with exactly ''imx6.ini'', ''imx6.bin'' and ''imx6ap.bin''. Don't copy anything onto it. If Windows asks to format the drive: **Cancel**.
+  - balenaEtcher works on many computers too; if it stops with "The writer process ended unexpectedly", use Rufus.
-==== On any car ====
-  - Switch the car on and plug the stick into the **front USB port** — the one official Aiways update sticks use.
+===== Flashing =====
+==== 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 a row like **Stock Firmware · AP _102** (from ADC 0.14.15 on it names the stick's app build; older versions show **Stock firmware 0051** for every stick) — press **Revert** and confirm. From ADC 0.14.7 on, the Connect app checks when you press **Revert** whether the stick's apps fit your car's MCU, and refuses otherwise ([[:software:versions|Head unit versions]]). ⚠️ That only covers this button: if the head unit restarts while the stick is plugged in, it flashes it without any check — for example after a factory reset, and on cars without the USB hub already when you switch on (see ⚠️ below). So still check yourself beforehand (see above) and pull out a refused stick straight away.
+  - 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, there should always be a way to install a new firmware.
+==== On a car without ADC firmware ====
+  - Switch the car on and plug the stick into the **USB port in the centre console**.
   - Open **Settings › About › Factory Reset** and confirm.
-  - The car restarts and flashes, with progress bars, for several minutes.
+  - The car restarts and flashes for a few minutes with a progress bar. Wild things happen here again, as described above.
 ==== Afterwards ====
-  - **Pull the stick** as soon as the flash has finished — left in, a later restart flashes again. If the screen asks you to remove the stick and then waits, pull it and switch the car off and on.
+  - **Pull out the stick** as soon as flashing has finished. Pull out the stick and reset the head unit by pressing both thumbwheels on the steering wheel for 10 s, or switch the car off and lock it, wait a moment and switch it on again, so that the head unit reboots.
-  - The first start takes longer; the car then runs the stock software.
+  - The first start takes longer than normal, don't panic; after that the car runs on the original software again.
-⚠️ Simply switching the car off and on does **not** start the flash — only a restart from the running system does (factory reset, or the Connect app).
-To install ADC afterwards, use a **separate** stick: [[software:adc|ADC 0.13.4]].
+⚠️ Simply switching off and on again does **not** start the flashing — only a restart from the running system (factory reset or the Connect app) does, unless you have a car with this head unit firmware version but without the USB hub on the head unit that the DAB radio is also connected to.