Watches ⟩ MTK6580 Watches

Hardware Support

Please make sure to test all hardware functions of your watch in your current operating system to rule out hardware defects before installing AsteroidOS. You can report any hardware support issue here. Use the label harmony/inharmony for issues specific to your watch.

The following list shows the state of the features of the harmony version of this watch.

badHeart Rate

The following list shows the state of the features of the inharmony version of this watch.

badHeart Rate
Model NumberModel NameCodename
KW68Kingwear KW68 3G Phoneharmony
KW88Kingwear KW88harmony
KW88 ProKingwear KW88 Proharmony
KW98Kingwear KW98harmony
KW99Kingwear KW99harmony
KW99 ProKingwear KW99 Proharmony
Blocks WatchBlocks Watchharmony
LES1Lemfo LES1harmony
LooK WatchLooK Watchharmony
D101Diggro DI01 3Gharmony
D107Diggro DI07harmony
W1AllCall W1harmony
W2AllCall W2harmony
ThorZeblaze Thor (original)harmony
Thor SZeblaze Thor Sharmony
IQ I2IQ I2harmony
D106Diggro DI06inharmony
D107older Diggro DI07inharmony
LES1Lemfo LES1inharmony

Model number and variants

This port of AsteroidOS should cover multiple watches as listed above.

MTK6580 based watches are marketed as different versions from different manufacturers. There are two known versions that are compatible with a range of MTK6580 based watches. These two versions are referred to as harmony and inharmony.

However, please note that only the Kingwear KW88 has been rigorously tested. Other watches have been reported to have various bugs, for instance the Zeblaze Thor has non working touchscreen. The Lemfo LES1 and Zeblaze Thor 3G have a screen rotated by 45° or the KW88 Pro requires a different scatter file.

Choose your variant

Download AsteroidOS for harmony

Store the files in your "Downloads" folder so the later commands work

asteroid-image-harmony.ext4 zImage-dtb-harmony.fastboot

MT6580_AsteroidOS_scatter-harmony.txt logo.bin

Download AsteroidOS for inharmony

Store the files in your "Downloads" folder so the later commands work

asteroid-image-inharmony.ext4 zImage-dtb-inharmony.fastboot

MT6580_AsteroidOS_scatter-inharmony.txt logo.bin

Prepare installation

Inform yourself

See the watch wiki page for up-to-date information about this watch.

Install SPFlashTool

SPFlashTool is a tool designed to flash Mediatek devices, you can download its latest version from

On Linux systems

Extract the content to a folder of your liking and run flash_tool as root.

On Windows systems

Extract the content to a folder of your liking and run flash_tool.exe.

Install instructions

1. Connect your watch

Plug the USB cable of your watch to your computer, with the current operating system running.

2. Setup SPFlashTool

In SPFlashTool, select the Download tab, under Scatter-loading File choose the MT6580_AsteroidOS_scatter-.txt file you just downloaded.
Make sure you have a screen looking like the image below and then press Download.

3. Turn your watch off

Long press the power button until the watch turns off. As soon as the watch is off, it should be detected by SPFlashTool which will then initiate the flashing sequence. This step might take a while.

4. Turn your watch on

Once the flashing is over, long press the power button until the watch boots to AsteroidOS.

5. Enjoy your new OS!

See the wiki for synchronization clients, SSH access, watchface and package installation, backup guide and much more!

Boot problems

Bootloop of any kind or stuck boot process

Don't panic. None of the commands we advised you to use can damage or brick your watch permanently.
You can always go back to the fastboot bootloader menu, by using the manual finger combos for your watch.

Boot gets stuck even after repeated reflash

Congratulations, you might have found a new issue for us to solve. While this should not happen with stable builds, the nightlies are advancing quickly, and are not tested on all watches. You are likely using a nightly build, as the installation pages currently link to those. You can try again and install a stable build when available.
To help us solve the problem, you could try to collect logs. It is possible that the watch does not show a UI but is already accessible using ssh ceres@ or adb shell in the state the boot process stops. In case SSH connection works, try the following commands to write logs to local .txt files. or, if your watch presents an ADB interface, use the following commands: In case no connection is available, it is still interesting to see if the watch leaves any traces in your local dmesg. Try to spot USB related messages in sudo dmesg -w while the watch is connected and booting. Record the log using the sudo dmesg > dmesg-local.txt command.
You can share those logs in a new Github issue tagged with the watch codename. For support chat, you are invited to join our Matrix channel.

Watch only boots when powered via USB, but shuts off when booted while worn

This is a clear sign of a worn battery that will soon fail. Maybe you should replace it.
The boot process of AsteroidOS uses all cores of a watch to ensure a fast startup. This leads to power spikes during the boot process, which can completely shut down watches with worn out batteries. It has been observed that WearOS can still boot on watches with worn out batteries, but AsteroidOS cannot, depending on the progress of battery wear. However, AsteroidOS can usually still provide a useful 10-20 hours of uptime when the watch is worn once booted while powered up.
Batteries are relatively easy to replace on watches with screwed down backs. Glued back plates usually require creative solutions involving hair driers.

Watch successfully boots into the AsteroidOS user interface, but immediately reboots

This is a known behavior when the battery charge is very low. The watch usually recovers from this condition by simply boot cycling for some time. All watches also charge in fastboot or recovery mode. Letting the watch dwell on the fastboot or recovery menu screen for some time should fix the problem even faster.

Flashing problems

Watch is not detected and all fastboot commands fail

ADB connection works, but fastboot does not?

The fastboot oem unlock command not working even though the watch could be booted into fastboot mode using adb reboot bootloader is a known issue on windows systems. It is caused by using a watch manufacturer USB driver with missing fastboot support. Try removing that one and install the offical Google USB driver we linked above in the install section.

Fastboot command crashes or hangs at "invalid sparse file format at header magi" (explicitly missing the "c" in magic)

This error occurs when using deprecated fastboot and ADB versions on Windows systems. If you already had adb.exe and fastboot.exe installed and skipped downloading our supplied ZIP file, please install and try those commands instead. Another reliable source for updated windows ADB and fastboot versions is the official Google platform tools ZIP file.

Fastboot command stops with error during the ~5 minute flashing process

Smartwatches are prone to lose a proper connection to their cradle over time due to sweat corroding the watch pins.
Clean the pins and pads with isopropyl alcohol and repeat the flashing process.
Try to ensure a stable USB connection by putting the watch and your computer on the same flat surface. Try to not move the cable connecting your computer and the watch during the whole flashing process. In case of worn or corroded contacts and pogo-pins that lost their springiness, it might be useful to attach the watch to its cradle or charging cable using duct tape or rubber bands.

Fastboot command displays "invalid sparse file format at header magic" when starting to flash the device

This is not a fatal error and can safely be ignored. Fastboot expects images to be in sparse format. When a raw image is supplied like in case of most of the AsteroidOS watches, fastboot converts it to sparse and shows above message.