FORUMS
Remove All Ads from XDA

TUTORIAL: Convert Xiaomi Huami Amazfit Smartwatch from Chinese to English firmware

611 posts
Thanks Meter: 630
 
By Neuer_User, Senior Member on 5th January 2017, 04:40 PM
View First Unread Post Reply Email Thread
NOTE:
I have published an alternative way of having an English translated watch, WITHOUT FLASHING (so, no risk of bricking!). See my other thread "PACEfied AmazFit"!
I recommend this to most people, as this firmware is much more advanced than the official English PACE firmware.


Hi guys

We have successfully converted several dozens Chinese Amazfit watches to the English Amazfit Pace firmware (see this link).

This has been tested with AmazFit Chinese FW 1.2.3 and 1.2.4b successfully.

ATTENTION: There are some people that have problems with the touchscreen after the flash. They have flashed with the watch being on a very early firmware (no updates done after purchase). Please update the watch first to a recent Chinese firmware (ideally 1.2.3 or 1.2.4b) before flashing the English version!
UPDATE: The issue has been fixed by reflashing the watches back to the old Chinese version, then updating to a current version, and finally converting the watches to English version. See here: https://forum.xda-developers.com/sma...5#post70521085


Requirements:
You need to have ADB and FASTBOOT installed and working on your PC. For ADB you will need the universal drivers from Khoush (if you use Windows). YOU MUST HAVE EXPERIENCE WITH ADB AND FASTBOOT!!!

DISCLAIMER:
I AM NOT RESPONSIBLE FOR ANY BRICKED WATCHES, LOST DATA, HEART ATTACKS OR WHATEVER. YOU DO THIS ON YOUR OWN RISK. WE CURRENTLY HAVE NO WAY TO UNBRICK A WATCH, IF SOMETHING GOES WRONG!!! YOU WILL PROBABLY ALSO VOID YOUR WARRANTY (although warranty is difficult with Chinese watches anyway). YOU HAVE BEEN WARNED!!!


OK, you want to continue? Here are the steps:

# Download the archive here: https://mega.nz/#!gQ9XiJbT!qPQD6Uw-1...k_jiOL8ezLrqvs
# unzip the archive on your PC and read the instructions

# connect your watch to your PC
adb devices
# this should list your watch, otherwise something is wrong

# push the files from the archive to the watch
adb push boot.img.gz /sdcard/
adb push system.img.gz /sdcard/
adb push flash_eng_version.sh /sdcard/
adb push md5s.txt /sdcard/

# now reboot into bootloader
adb shell reboot bootloader

# when you see the fastboot logo, check that you can access fastboot
fastboot devices

# you should see your device listed, otherwise your fastboot installation is not correct on your PC
# then boot into the temporary recovery
fastboot boot Amazfit-mod-recovery.img

# this command will end with a "FAILED" message. Don't be afraid. This is normal. It is important that you see
# a triangle and/or the text "No command" on the watch. Then you are in recovery and can enter adb.
#Check first, if adb can see the device
adb devices

# if you do NOT see your watch listed, then you need to update your (Windows) adb drivers (see post #2).
# if you see your device listed, then enter adb with
adb shell
# you should see only a "#", meaning you have full root access

# move to the sdcard
cd /data/media/0/
ls
# you should see your files on the "sdcard", including the ones that were pushed before
# start flashing the files (THIS IS THE CRITICAL PART!!! Now, the watch gets modified! Last chance to stop. In case you changed your mind, simply type "reboot".)

sh flash_eng_version.sh

# if everything worked correctly, you should see something like:
Code:
# sh flash_eng_version.sh
Validating images
boot.img.gz: OK
system.img.gz: OK
Generating backup files
Creating boot.img.bak
18432+0 records in
18432+0 records out
9437184 bytes (9.0MB) copied, 3.958210 seconds, 2.3MB/s
Creating system.img.bak
1687552+0 records in
1687552+0 records out
864026624 bytes (824.0MB) copied, 1821.060340 seconds, 463.3KB/s
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE! THIS WOULD BRICK YOUR WATCH!! Press Enter to continue or CTRL-C to stop!

Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 2.075793 seconds, 4.3MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 107.981352 seconds, 7.6MB/s
Finished
# If you see any error message during or after flashing, then DO NOT REBOOT the watch, but get some help or analyse yourself, what went wrong. You can still reflash.
# If everything is ok, then you can reboot the watch
reboot

# The watch should reboot as an English version, if everything is ok. That means, first logo, then boot animation (here you are already safe!), then optimizing apps, then watch face. If your stuck at the logo, the watch might well be bricked!!!!

So far, it looks as our method completely converts the watch, as we exchange the boot and system image. You will keep your data and your serial number, though.

There are so far no long term experiences. We expect that OTAs will continue to work, but as there are so far no OTAs for the English version, we could not verify it by experiment.

Another disclaimer:
I did that in my free time. I am not a professional developer, and I do not have much time (if ANY) for supporting this. I hope that others will jump in and help people that are in need.


Changelog:
2017-01-09: Flash script now backups original boot.img and system.img first.
The Following 33 Users Say Thank You to Neuer_User For This Useful Post: [ View ] Gift Neuer_User Ad-Free
 
 
5th January 2017, 04:43 PM |#2  
Junior Member
Thanks Meter: 10
 
More
With the help of Neuer I was to flash my smartwatch with US Image!

I had some problems regarding android drivers while running fastboot and adb steps, this is how I solved them:

if fastboot is not detecting your device just download/install Google USB Driver at:
https://developer.android.com/studio/run/win-usb.html

Follow this guide on how to install the driver:
http://www.teamandroid.com/2012/07/3...android-sdk/3/

Quote:
Originally Posted by Neuer_User

Hi guys
...
fastboot boot Amazfit-mod-recovery.img
...


After booting into the modded recovery, adb was not detecting my smartwatch. All that i had to do was to go to "Step 35" of the previous guide and install the "Android Composite ADB Interface" driver and everything started to work again with ADB.

Big thanks to Neuer for his amazing hard work and patience! He did it! Also big thanks to everyone that provided useful information for this to work.
The Following 5 Users Say Thank You to darkmaniac For This Useful Post: [ View ] Gift darkmaniac Ad-Free
5th January 2017, 05:14 PM |#3  
Member
Flag Aachen
Thanks Meter: 12
 
More
The instructions are good.
Model is now A1612.
ROM Version is now 1.3.0n

I cannot switch from Mi to KM.
The Following User Says Thank You to koegs For This Useful Post: [ View ] Gift koegs Ad-Free
5th January 2017, 05:18 PM |#4  
Member
Thanks Meter: 16
 
More
Hi all,

Big thanks to Neuer_User for his hard work!
Just a quick question for those who have converted into english: does sync work and in which app (strava or mifit)?

Thanks.
5th January 2017, 05:26 PM |#5  
Junior Member
Thanks Meter: 2
 
More
It works perfectly. Thank you very much Neuer.
5th January 2017, 05:34 PM |#6  
Member
Thanks Meter: 8
 
More
Great work Neuer_User you are now officialy a Amazfit Legend!!

May i suggest the next person to attempt this does a video tutorial and uploads it to youtube. Kudos to all those who have contributed in one way or another.

Another XDA Headline
5th January 2017, 05:42 PM |#7  
Junior Member
Thanks Meter: 0
 
More
I've an error during update, do you have any hint:
Code:
C:\Downloads\convert_to_eng>adb push boot.img.gz /sdcard/
7573 KB/s (5575879 bytes in 0.719s)

C:\Downloads\convert_to_eng>adb push system.img.gz /sdcard/
7713 KB/s (189626362 bytes in 24.009s)

C:\Downloads\convert_to_eng>adb push flash_eng_version.sh /sdcard
/
267 KB/s (547 bytes in 0.002s)

C:\Downloads\convert_to_eng>adb push md5s.txt /sdcard/
45 KB/s (94 bytes in 0.002s)

C:\Downloads\convert_to_eng>adb shell reboot bootloader

C:\Downloads\convert_to_eng>fastboot devices
0123456789      fastboot

C:\Downloads\convert_to_eng>fastboot boot Amazfit-mod-recovery.im
g
downloading 'boot.img'...
OKAY [  0.436s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.403s
5th January 2017, 05:45 PM |#8  
tzwenno's Avatar
Member
Flag Rönkhausen
Thanks Meter: 1
 
More
Thank you so much. it worked perfectly.
5th January 2017, 05:54 PM |#9  
Junior Member
Thanks Meter: 0
 
More
Can you make a tutorial movie ?? Im not very good whit fastboot. Tks
5th January 2017, 05:54 PM |#10  
OP Senior Member
Thanks Meter: 630
 
More
Quote:
Originally Posted by perritos

I've an error during update, do you have any hint:

C:\Downloads\convert_to_eng>adb push boot.img.gz /sdcard/
7573 KB/s (5575879 bytes in 0.719s)

C:\Downloads\convert_to_eng>adb push system.img.gz /sdcard/
7713 KB/s (189626362 bytes in 24.009s)

C:\Downloads\convert_to_eng>adb push flash_eng_version.sh /sdcard
/
267 KB/s (547 bytes in 0.002s)

C:\Downloads\convert_to_eng>adb push md5s.txt /sdcard/
45 KB/s (94 bytes in 0.002s)

C:\Downloads\convert_to_eng>adb shell reboot bootloader

C:\Downloads\convert_to_eng>fastboot devices
0123456789 fastboot

C:\Downloads\convert_to_eng>fastboot boot Amazfit-mod-recovery.im
g
downloading 'boot.img'...
OKAY [ 0.436s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.403s

That is no error. You just need to continue with the next step. You should be recovery now and need to start adb.
The Following 2 Users Say Thank You to Neuer_User For This Useful Post: [ View ] Gift Neuer_User Ad-Free
5th January 2017, 06:13 PM |#11  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by Neuer_User

That is no error. You just need to continue with the next step. You should be recovery now and need to start adb.

That's ok
Now my amazfit is in English version.
Thanks very much
Great job!!
Post Reply Subscribe to Thread

Tags
amazfit smartwatch firmware

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread