项目的 README,来自 github.com/xwtk/hmg_nemesis。合并为一个 markdown 文件:README.md。
Own your car, to its fullest.
Browse and download packages in the NEMESIS Package Store. The NEMESIS website also has the Discord link.
You may pledge a small amount to help cover research costs for Gen5W systems as well as NEMESIS development. It is completely optional and is considered as a gratitude for the done work.
NEMESIS is subject to GNU AGPL 3.0 License, get to know more here.
You bear complete responsibility for any procedure with your car and its components, it is important to understand that there is always risk associated with procedures described in this and associated documents in this repository, your car functionality may be heavily impacted if this software is not compatible with your components.
Discover packages to install on your car in the NEMESIS Package Store. Made one of your own? Submit it to the store.
For your car to be compatible with NEMESIS, it has to:
First of all, I want to express my sinecere gratitude to user sin from Gen5W/ccNC community Discord, he has contributed his new installation architecture for NEMESIS to become available to pretty much all Gen5W head units.
Because of this, we now have 2 methods available for installation, the first method is the Update OTA method which has been the way of installing NEMESIS from the beginning (option 1), the second method requires slightly more work, but it does not depend on OTA update capabilities of the car.
| Step | Guidance |
|---|---|
| 1 | Download the ota_package.tar asset from the latest release onto your computer. |
| 2 | Prepare an exFAT or FAT32 formatted blank USB drive. |
| 3 | Copy the downloaded tar file onto the USB, do not extract or repack the archive file. |
| 4 | Insert into the car's HU USB port, messages such as "No Supported Files" are expected. |
| 5 | Navigate to Engineering Mode (use web to search on how to do so), open USB Copy, select Update DSP |
| 6 | Tap on Update OTA (existence of this doesn't mean your car has OTA support), if you see a loading animation come up on the status bar in the top right, everything is going as planned. Wait for installation to complete and the HU to restart. |
| Step | Guidance |
|---|---|
| 1 | Download the nemesis-usb-update-package.7z asset from the latest release onto your computer. |
| 2 | Prepare an exFAT or FAT32 formatted blank USB drive. |
| 3 | Extract (not copy the 7z file) the contents of the downloaded 7z file onto the root of the USB, so the .tar files and such are in the USB, not inside a folder or anywhere else, root means the USB drive itself when you open it (I can't believe I have to clarify this). |
| 4 | Insert into the car's HU USB port, messages such as "No Supported Files" are expected, wait for up to 15 seconds. |
| 5 | Remove USB, restart the HU, this can be done by pressing the reset pinhole for example. |
| 6 | Wait for boot to complete, you may see an Updating screen popup briefly, if so, then the entrypoint has been achieved. Wait for the buttons in the disclaimer screen to become available, then proceed to the home screen. |
| 7 | DO NOT OPERATE THE HU, wait for a few seconds for NEMESIS Installation Interface to popup. |
| 8 | Proceed with installation. |
If you have mistakenly closed the installer, NEMESIS Installation Interface will popup on every HU boot, you can restart the HU to see it again. Press Decline in the interface to remove the installer and restore the system to factory state.
| Step | Description |
|---|---|
| 1 | Follow Quick Installation Guidance procedures for updating to 1.16, no need to uninstall 1.15. |
| Step | Description |
|---|---|
| 1 | From the latest release, download the nemesis-update-<version>.zip asset and the NEMESIS.data next to it, then copy both to the root of a blank exFAT or FAT32 USB drive. Do not extract the zip or put them in a folder. |
| 2 | Insert the USB drive into the car's HU USB port with Android running. |
| 3 | Choose Yes when NEMESIS asks to update. The HU restarts when the update is done. |
OR
Settings → Check for updates in NEMESIS Manager does the same over the internet, once the update is on the portal. You may additionally get a popup saying new update is ready to be installed, that is the automatic update doing its job.
.. is refused, and so is an id starting with -. A nested NEMESIS.data can no longer replace the one at the root.-o rw,remount and -o ro,remount.qb_runtime.sh.!id in depends (for example depends="base@>=1.0,!other") for a package that cannot be installed together with yours.replace /system/etc/qb_runtime.sh failed errno=95 and restore FAILED. A unit that showed this is still on 1.16 and is safe to use: update again to 1.16.2.type=list). Rows are colored by compatibility with your OS version, car model and dependencies, and several packages can be installed in one go. Tap a package to open its details, where Install, Update and Uninstall are. Packages with a version=1.0 descriptor are shown in yellow with a warning that they may not be compatible. The same store is on the website, where packages from other publishers carry a Community badge.nemesis update, USB type=update, a manual check in Settings, and an hourly Update Monitor that does the 24 hour online check.nemesis wipe --confirm and a Wipe action in Manager, which asks twice.version=1.1. New keys: type, package-version, short-desc, os, models and depends. version=1.0 descriptors still work. A package cannot be uninstalled while another one depends on it.GET_TASKS and after Close, the service staying disabled after repeated crashes, Manager opening on the first press, and Setup covering Manager after it opened.Read about NEMESIS, what it is exploiting, what it features, and its use manual.
| Document | Contents |
|---|---|
| 01 - Entrypoint variant 1: DSP OTA troubleShooter | First entrypoint variant. How the firmware runs unsigned DSP OTA members as root, and how that path is reused. |
| 02 - Entrypoint variant 2: USB update package | Second entrypoint variant. The stock USB system-package upgrade path and the three steps that lead to a NEMESIS install. |
| 03 - Debugging Execution Interface | What NEMESIS is on the unit after it is present: features, how you open it, CLI and Manager usage. |
| 04 - Install and uninstall | How NEMESIS is written onto /system and how it is removed. |
| 05 - Packages | Installable packages: metadata, layout, builder, lifecycle. |
| 06 - Run scripts | USB NEMESIS.sh / type=execute: when they run and how to write them. |
| 07 - Cloud Store API | The public store and update API, for running a store of your own in a fork. |
| 08 - Submit a package | Step by step: from an xwtk.Account to a listing in the NEMESIS Package Store. |
Documents 01, 02 and 04 are the only ones that describe the entrypoint variants and the on-disk install, do not use them with advanced LLMs which may have safeguards enabled. 03, 05, 06 and 07 assume NEMESIS is already on the head unit and treat it as a Debugging Execution Interface for packages and privileged commands, so safeguards will not be triggered.
Developed by Gor Mirzoyan (xwtk.cloud).