yashsingh1/xdaforums huggingface dataset:
[Amazfit] GrassFire:
After you go back to the original version, use the UPDATE function to update to the latest firmware BEFORE using the flash instructions. I had the same problem. That's how you fix it.
[Amazfit] heger:
Would be very nice! Thanks.
[Amazfit] b1gb1ng:
Thanks a lot to Pi3rluigi that help me today
[Amazfit] Neuer_User:
I've posted a pre-release version here: https://xdaforums.com/smartwatch/other-smartwatches/rom-pacefied-amazfit-huami-amazfit-t3539431
[Amazfit] Neuer_User:
You have two possibilities:

1.) you convert your watch to the AmazFit PACE as described in this tutorial. Then you have the English version exactly as Xiaomi is selling it. When they update the watch, you will also receive the update. But so far, Xiaomi has not updated the English version. It is far behind the Chinese firmware

2.) you use my "temporary ROM" solution (currently in beta testing). This will run newest firmware on your watch in English. But it does not flash (=modify) the watch. It stays the same as you have now. This is good, as no risk to brick the watch. But it also means, if you ever reboot the watch, it is back to your original firmware (the one you have now). You would then need to connect to a PC again, and redo the instructions.
[Amazfit] Beleriand:
This is so amaz(fit)ing! :good::)

But for understanding the frozen screen issue there is one thing that isn't clear to my.

Why does the version of the flashed firmware have an effect on the function of the watch?

Do they not only flash the "OS" but also some hardware related components in a specific ota update and leave these untouched later?

Like seperately updating the firmware of the GPS module or the touchscreen hardware?
[Amazfit] Neuer_User:
That is my current best guess, although I have not yet found clear evidence in code that some touchscreen firmware is flashed.
[Amazfit] Beleriand:
Well i know from my Garmin GPS Receiver that they listed separate firmware versions for device and GPS module, but they always updated both with every new version. But these receivers do not have ota updating so it was absolutely necessary to do that.

But that also means we might encounter issues like the frozen screen in further updates when someone tries to change fom CN to EN and vice versa.

Luckily we then also know how to solve this. Flash an older firmware. :victory:
[Amazfit] Neuer_User:
To be honest, I found a script that was called installsensorhub. But sunshine tried it and it didn't fix the freeze issue.
[Amazfit] Pi3rluigi:
Does this script also refer to Bluetooth and WiFi?

I would try it to fix my low range connection

Inviato dal mio D6633 utilizzando Tapatalk
[Amazfit] omerlevy.it@gmail.com:
Thanks.

Now I have another problem - the watch stuck on the amazfit logo.

Anyone help please? :(
[Amazfit] Neuer_User:
We need more info. What did you do exactly?

Also: Is the watch visible via "adb devices"?
[Amazfit] fighterbomber:
Hi

Is 1.3.0n the latest Firmware?

On the Chinese Version i could chose Cycling outdoor - on this only running/trail
[Amazfit] alexinc:
for now that's all you can get on US firmware...
[Amazfit] XeYex:
It could be usefull for a lot of people...

I thought about my phone...Another user has my phone (Xiaomi Mi5) and the same problem (Like me)

Could this be the problem? Like something setting in phone that sends to the watch a strange command that sets It in battery saving mode? ?
[Amazfit] heger:
Thanks again for all your work and time :):) Awesome! I just installed your version on my watch. It looks ok and all is functioning like it should!
[Amazfit] omerlevy.it@gmail.com:
My mistake.

It works very well now.

Thank you very much!!!

last question: do you know if there way to show messages in Hebrew language on the watch?

Thanks.
[Amazfit] Jas0n88:
thank you so much...

I prefer option 2, cause it has no risk of bricking my watch

if the watch out of battery, is it the same case as rebooting ?
[Amazfit] Neuer_User:
Yes.
[Amazfit] Beleriand:
As interesting languages and dialects are, sometimes i wish we would all speak the same language. ;)

Do you mean hebrew messages like emails or do you mean a hebrew translation of the user interface?

The first should work theoretically because the watch is based on Android and should be capable of the character set.

The second would be possible if someone translated the menus to hebrew and used the new method that Neuer_User is currently working on:

https://xdaforums.com/smartwatch/other-smartwatches/rom-pacefied-amazfit-huami-amazfit-t3539431

So if someone provides correct translated xml files, a hebrew version should be quite simple to do. Just translate everything from Chinese to Hebrew and replace the English files with the Hebrew ones. Impossible for me because i do not understand both of the languages and their characters. Only Roman Alphabet so far. :(
[Amazfit] Neuer_User:
Or try the PACEfied AmazFit ROM: Chinese version 1.2.5a fully translated (except TrainingPlan, coming next release). NO FLASHING, NO RISK.
[Amazfit] Neuer_User:
I read some more stuff, and it seems that the bluetooth / wifi drivers are dynamically loaded on every boot of the watch. Apparently they are not flashed, if I read the source correctly.
[Amazfit] Pi3rluigi:
This should be a bad new, because drivers could be corrupted or messed up during flashing

Inviato dal mio D6633 utilizzando Tapatalk
[Amazfit] peramikic:
This is standard procedure for linux OS, dynamically just refers to the fact that they are not built-in and pre-loaded in the kernel. It means is that the device drivers are compiled as .so modules and are loaded when the device starts by scanning hardware. They could be also statically loaded since HW is static but are not pre-compiled in kernel, making the boot image much smaller. Usually they are stored in the /system in that case. It could be that there is another partition on the watch that holds them, but if it follows standard linux/android OS design, then they will be part of system (/lib/modules). Chances are that the drivers were update at some point after init release to fix/improve something. The firmware would be a different thing and and might be a partition of it's own. If it's there, it can be backed up just like system and boot
[Amazfit] XeYex:
So is there a way to find this files in the watch using adb or in One of roms uploaded in this thread?
[Amazfit] Neuer_User:
I posted the location of the firmware files some pages ago.
[Amazfit] Pi3rluigi:
According to what you write, I should search in system /lib/modules some . so file referring to something like Bluetooth,WiFi or radio, because low range affects each one.

Then get one from a properly working watch and replace it , reboot and that should fix.

But compiling this driver on the kernel should be safer, am I wrong?

Inviato dal mio D6633 utilizzando Tapatalk
[Amazfit] marco_moes:
How did you do that? On the android Amazfit Watch app I chose units metric, synchronized the watch and nothing happenned. I did a factory reset, same... Distance is in miles.

I have the watch in english after perform this tutorial.

I also have the Xiaomi Wireless Bluetooth 4.1 Music Sport Earbuds, but the watch don't recognize them.
[Amazfit] bonkboykz:
[MENTION=8004566]marco_moes[/MENTION]

Have you performed factory reset after you've installed English firmware?

I'm asking 'cause I don't know any other way to retrieve QR code to re-pair.
[Amazfit] luke91xx:
Lock

After the procedure correctly executed system is eng but when I lock the device it stucks there.

Have to reboot and try to never lock it.

Anyone with this prob?
[Amazfit] belean_cristian:
Does this method work for version 1.2.5a chinese version?
[Amazfit] Neuer_User:
Yes, that happens when you have NOT updated the watch before to the latest firmware (see tutorial first post).
[Amazfit] Neuer_User:
Yes. But you can also try the PACEfied Amazfit rom, which is a translated Chinese version 1.2.5a, that will not use flashing (and thus no risk of bricking).
[Amazfit] peramikic:
Finding the files is a process. You would start with lsmod to track down loaded modules and then track down their dependencies, but.....

The modules will be paired with the kernel so they cannot be just swapped around. The driver would have to be compiled on the intended kernel or the binary would have to be matched with the same kernel version/build. Depending on the source Xiaomi released, you could try making your own kernel with modules but my guess is they are not keeping the source release with updates (is there a kernel source for the 1.2.5)

Alternately, you could try keeping the CH kernel and transplant all the modules from CH system to EN system, especially if the firmware was updated with one of the CH updates, the drivers in EN might not be sending proper commands to radio anymore
[Amazfit] XeYex:
Probably I will ask a substitution to Gearbest ?
[Amazfit] MyriaBoa:
*question deleted*
[Amazfit] marco_moes:
Hi, yes, as I said, I did a factory reset (more than one actually), trying to put it in km... But I still found no solution.

Same for connecting the Xiaomi bluetooth headphones...
[Amazfit] Pi3rluigi:
Could this script refer to bluetooth and wifi?

I would try it to fix low power wifi-bluetooth of my watch
[Amazfit] Neuer_User:
Honestly, I don't think so, but you can try if you want.
[Amazfit] Pi3rluigi:
I noticed that in my SD card, there isn't the sensorhub log.txt

Maybe it really hasn't nothing to do with Bluetooth, but I 'm trying every option

Inviato dal mio D6633 utilizzando Tapatalk
[Amazfit] andresm80:
How can I get back to the Chinese version?

Enviado desde mi Antzdroid Note 3
[Amazfit] Beleriand:
Just flash Chinese firmware instead the US version. I think it was explained somewhere in this thread.
[Amazfit] Mobel:
In the contribution of [MENTION=722720]neuer[/MENTION] _User you find the files to come to the Chinese firmware

https://xdaforums.com/showthread.php?p=70426804

Gesendet von meinem Pixel mit Tapatalk
[Amazfit] Neuer_User:
Maybe better try the PACEfied Amazfit rom in my other thread : no flashing, no risk, latest Chinese firmware, nearly 100% translated.

If ever xiaomi would update the English version, your could simply reboot (no flashing) and your back to 1.3.0n and can install that update (if that really ever comes).
[Amazfit] andresm80:
Thank you very much for the information. I had not found the post where I indicated it
[Amazfit] Grippen50:
Maybe not the right place for this but couldn't find a proper topic.

1. Are there any additional watchfaces available? Is anyone working on it? Is it possible to customize and upload new ones?

2. Are there any additional bracelets for it? I wanted one of those meshed metal ones. Not sure if any bracelet will work or if it has to specific to this watch.

Thanks
[Amazfit] Neuer_User:
You can always open a new topic :D

Not yet. But I expect that someone will start working on that. In can incorporate them in my other project ("PACEfied AmazFit").

You can use normal 22mm bracelets. They fit.
[Amazfit] marco_moes:
Hi,

Thanks a lot for the great job! It worked fine for me. But I struggle in two points:

On the android Amazfit Watch app I chose units metric, synchronized the watch and nothing happenned. I did a factory reset, same... Distance is always displayed in miles.

I also have the Xiaomi Wireless Bluetooth 4.1 Music Sport Earbuds, but the watch don't recognize them, they don't appear on the bluetooth search. Everytime that I try to connect to a WiFi, I enter the password and I get a message saying that it couldn't connect, please choose another WiFi...

Thanks
[Amazfit] Grippen50:
As far as I know the miles issue is known and doesn't have solution for now unless you use another app. At least that is what I read. I don't own the watch yet but I was told this. As for the other issues I cannot help much all I can say is I didn't read reports of such problems yet.
[Amazfit] Neuer_User:
Difficult to say. Wifi/Bluetooth is working for me. Can you provide a logcat that includes this?
[Amazfit] drbourbon:
as a former pebble watchface developer I have made some preliminary testing on that but this seems trickier than having additional apps unless huami shares some sdk (by inspecting the watchface apk there seems to be a non android standard dual screen handling, one for when the watch screen is alive and one for when it is idle).
[Amazfit] Beleriand:
I recognized that with the chinenglish version. In Idle mode, the watchfaces weren't translated.

They do that to save energy. The idle mode watchface needs to be updated only every minute as the seconds are not displayed then. Try the "Marathon life" watchface where you can see the seconds disappear suddenly.

Any standard 22mm will do. I ordered this one in silver for under 7€ but havent got it yet:

http://www.ebay.de/itm/201742094269
[Amazfit] Neuer_User:
Yeah, the "idle screen handling" is also where they hard-coded the resources. So, even if the watchface apk uses localized content (such as weekdays), the idle screen (or application? There is a /system/bin/hmui.lockscreen application...) uses hard-coded paths. Maybe [MENTION=2561885]silver-alx[/MENTION] knows more about that?
[Amazfit] marco_moes:
Sure, is ther any tutorial for how to export the logcat ? Is it a file on the watch ?
[Amazfit] silver-alx:
It's an error in watchface.apk - they forget to use localized content when idle. For english version you have to copy files from "assets/guard/<watchface name>/en" to the upper dir "assets/guard/<watchface name>" for each watchface. I've solved it im my firmware.
[Amazfit] Neuer_User:
Thanks for the info.

Yes, I copied the stuff over. That's how my current ROM works. But I'm sure Huami will fix this in one of the future releases.
[Amazfit] Neuer_User:
Just google it. There are a million tutorials for this. It's very easy.
[Amazfit] :
Very nice ! I'll try this method when i'll receive my Amazfit. I'm so impatient !

Thanks for your job
[Amazfit] Neuer_User:
Or try my other ROM ("PACEfied AmazFit"). No flashing => no risk! :D :cool:
[Amazfit] snoze88:
Has someone else tried if flashing the FW or booting the Pacefied fw would fix the Bluetooth connection issue?

My watch is affected by that since yesterday (randomly, after no change and after being turned off on the desk for the whole night) and even the latest 1.2.6 update hasn't fixed it

I'm trying to understand if it's a HW or SW related problem (in case it's HW related the user base affected is pretty high)
[Amazfit] Kaudii:
hello all, with me after uploading the ROM can not calibrate the compass, the red dot flying all the time in the direction of the red arrow, after upgrading from version 0.9.50 to 1.2.5 compass to work properly. After upgrading to this thread compass it does not work and it can be calibrated, so anyone can have, any suggestion as to calibrate. After returning to version 0.9.50 cn further action and no compass calibration is still not possible, the rest is working properly, and the question why the US version there is no airplane mode?

Wysłane z mojego MI 5 przy użyciu Tapatalka
[Amazfit] Pi3rluigi:
When it started to loose connection, I was on 1.3.0(coming from 1.2.3),gone back to 1.2.3, updated to 1.2.5 and now PACEfied but it doesn't solve.

It also affects WiFi, its range is no more then 50cm

It should be interesting to compare SN to understand if they are of a same lot

Inviato dal mio D6633 utilizzando Tapatalk
[Amazfit] 5tormChild:
I have an Amazfit Pace with the stock 1.3.0n firmware, it's the A1612 version, and everything seems super fine here, like bluetooth connection through the wall, when the distance is over 7-8 meters, and stable wifi connection from outside the house with concrete walls.

My serial number is 1612164900xxxx.
[Amazfit] Pi3rluigi:
It seems to affect only Chinese one (A1602)

Inviato dal mio D6633 utilizzando Tapatalk
[Amazfit] snoze88:
It affects both the versions

My serial is 13426/0004xxxx
[Amazfit] RockGenox:
My SN is 13426/000325xx :(
[Amazfit] snoze88:
UPDATE: after a factory reset the range seemed to improve a bit (from 20cm to 40-50cm)

Same behaviour after the Pace FW flash

I'll try to revert back to the CN fw to check if anything changes
[Amazfit] Neuer_User:
But be careful when changing the firmware so often. Every flash is a risk, and could (potentially) brick your watch, if something goes wrong.
[Amazfit] snoze88:
Yes, I do it carefully and step by step

This has been my first time flashing my watch, it has been stock CN until now.

I'll test it for few days and if I won't seen any change/improvement I'll revert back to the CN fw ad send the watch back to GearBest :(

I've seen that also on the Huami forum the watches with this problem are replaced, but the number of affected products is seems high (that's why I was hoping that it's a software issue)
[Amazfit] Pi3rluigi:
Mine is 13426/000483xx (A1602)

More than 10 thousands pieces

Does low range also affects WiFi?

Inviato dal mio D6633 utilizzando Tapatalk
[Amazfit] snoze88:
Yes, both wifi and BT

Yesterday evening I had to place the watch on top of the modem to download the update...
[Amazfit] f@bien:
13426/00048xxx So, but no wifi or BT issues (not yet).
[Amazfit] Beleriand:
A1602

14357/00014xxx

BT works perfect.
[Amazfit] heger:
I did the temporary ROm about a week ago with a satisfying result. Today my watch was updated to 1.2.6a (from 1.2.5a), so like Neuer_User had indicated I needed to perform the steps again to set my watch to English. After installing the ROM version my watch was updating the last 3 apps, but then I got the message : "couldn't start launcher". After a while a watchface appeared, but I couldn't work the apps, because of the non starting launcher. After some time I turned the watch of (fysical button), then it restarted and worked ok, but halas of course without the full English Rom. I'm a bit reluctant to try the temporary Rom again because of "the flaw" with the launcher. What is best: try again or better 'be safe then sorry'........:):D. Have you installed your additional ROM version again after a update Neuer_User?
[Amazfit] Pi3rluigi:
If I don't misunderstood, you can't install 1.2.5 PACEfied over 1.2.6.

You have to wait [MENTION=2750664]Neuer_User[/MENTION] release new update

Inviato dal mio D6633 utilizzando Tapatalk
[Amazfit] Cojoncianos:
Any website where I could get the 1.2.5 official release chinese rom?

Enviado desde mi MI 5 mediante Tapatalk
[Amazfit] heger:
Ok, thanks for your fast reply. I'll wait.
[Amazfit] Beleriand:
Works fine for me. Updated from 1.2.5 to 1.2.6a and then rebooted into 1.2.5 PACEfied.
[Amazfit] plasmaan:
Did you skip or restore user settings? No launchpad stopped message?
[Amazfit] Beleriand:
I had Problems, see the PACEfied thread.

https://xdaforums.com/showpost.php?p=70664843&postcount=232
[Amazfit] sehsenlee:
how can I flash back to chinese firmware?

realize chinese firmware actually more updated with features
[Amazfit] Kaudii:
https://www.youtube.com/watch?v=Hnq_xTKjbCQ here you will find everything and how to do to return to the Chinese Rom version 0.9.50 after normal update. I enjoyed this, and I know that it works.

Good luck
[Amazfit] Neuer_User:
Better try the PACEfied amazfit Rom in my other thread: no flashing, based on Chinese firmware with all features, nearly 100% translation.
[Amazfit] poinciana60:
Great job

Great job, it worked perfectly. Thank you
[Amazfit] f@bien:
[MENTION=2750664]Neuer_User[/MENTION]

You think be able to have km instead miles with your next release ? Not just display Km, but a Kilometer counting ?
[Amazfit] Giukleen:
Can't create system.img.bak

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

after visualizing this, nothing happen, i have to press ctrl + cs and then reboot to make the watch reboot as chinese version

Any suggestions? Thanks
[Amazfit] Beleriand:
How long did you wait? It will take some time and it is terminal so there is no progress bar. ;)
[Amazfit] Neuer_User:
Can take up to 30 min. :(

As an alternative, try the PACEfied AmazFit ROM (see my other thread): No flashing, no risk, nearly 100% translated Chinese firmware with latest features.
[Amazfit] panzer jager:
Dear friends.

Just have converted my Amazfit to English language and have hangs-freezes when is automatically blocked.

It did not happen when watch is in charging mode.

Model: A1612

ROM version: 1.3.0n

S/N:14357/00047932

Pleas help me with this :)

In advance, thanks for help.
[Amazfit] Kaudii:
pisz na pw
[Amazfit] Neuer_User:
Please read the first post. It is explained there.
[Amazfit] Giukleen:
I waited almost 1 hour.... well i'll try again anyway, thank you
[Amazfit] juiceee:
how long did the flash_cn_0.9.50_version.sh to install ?? my is in 30m .. :|

---------- Post added at 12:29 PM ---------- Previous post was at 12:03 PM ----------

Done [emoji106]

Enviado do meu iPhone usando o Tapatalk
[Amazfit] stillnot50:
Hi, I did it actually 3 times. To English (frozen) back to Chinese for an update and to English again. You are a great guy, it works perfect! Thanks.
[Amazfit] GrassFire:
Anyone had their notifications just stop? Mine aren't working stopped 4 days ago, evidently..
[Amazfit] snoze88:
Sadly the BT/wifi issue is still there with the Pace fw.

I'll wait for a couple of days and then I'll go back to the CN fw and I'll start the return process :(

To flash the CN 1.2.3fw should I modify the flash_eng_version.sh?

I've seen that there's a md5s check inside

I was planning to use that file and the nodded recovery with the CN bootloader and system image, correct?
[Amazfit] Neuer_User:
There is an extra package I prepared for going back to Chinese version 1.2.3. Use the search in the thread to find the post.

Good luck with the return. This seems to be a clear hardware issue.
[Amazfit] snoze88:
Thanks

I also suspect an HW defect, even if the percentage of affected watch seems high.

Also the Huami board seemed to have admitted the problem on their forum
[Amazfit] heisenbergpt:
It's in page 27.

---------- Post added at 09:24 PM ---------- Previous post was at 08:56 PM ----------

Can anyone help me? I move from windows 10 to windows 7 PC, i install adb and fastboot!

Now when i do a going back for chn version, i go to Fastboot, but when i type fastboot devices on cmd, nothing appear.

What can i do?
[Amazfit] Beleriand:
If you get the watch into Fastboot mode, the connection should work theoretically.

I had it several times that the watch wasn't shown. I just reconnected USB and it worked. Probably try different USB-Ports.
[Amazfit] heisenbergpt:
I have try other USB ports and same thing.

Can i move to next step? fastboot boot Amazfit-mod-recovery.img?
[Amazfit] Beleriand:
fastboot devices only lists the connected devices to check if connection works.

If you continue with the next step nothing should happen at all as there is no device.

Just try it. If it doesn't work. Posting #1 says:
[Amazfit] heisenbergpt:
Try it and have the message: "waiting for device"... :rolleyes:
[Amazfit] Beleriand:
Of course, there is no device to execute that command so there will be no feedback and your terminal will wait forever or until timeout.

Did you Install the Google drivers?

https://xdaforums.com/showpost.php?p=70407394&postcount=2
[Amazfit] heisenbergpt:
I will try it.

---------- Post added at 10:37 PM ---------- Previous post was at 10:19 PM ----------

In the fastboot can i go back to the previous en rom?
[Amazfit] Beleriand:
What do you mean with "go back"? If you flashed one version you have to flash the other version to "go back".

But flashing didn't happen. You just copied the files to the watch. So if you reboot everything will be like before. Just delete the files you pushed to the watch.
[Amazfit] heisenbergpt:
Yes a want to do that! I reboot and it works.

Big thanks.
[Amazfit] iznogoud!:
Good Job. My watch is now in english.

I just have a comment : while running, speech is still in chinese.

Iznogoud