FORUMS
Remove All Ads from XDA

TUTORIAL: Unbrick your Huami AmazFit Smartwatch / Xiaomi AmazFit PACE

1,088 posts
Thanks Meter: 2,516
 
By Neuer_User, Senior Member on 29th January 2017, 07:35 PM
Post Reply Email Thread
6th February 2017, 10:32 AM |#11  
Senior Member
Flag Petah Tiqwa
Thanks Meter: 442
 
Donate to Me
More
well, nothing helped, there's no configs for the JZ4785, and there's no relevant information of partitions offset for flashing. we tried to flash both 1.2.5 and some generic ingenic image, with a lack of success as well
contacted ingenic for some clarification and some help, lets see where this lead to ...
2nd March 2017, 11:34 AM |#12  
Junior Member
Thanks Meter: 0
 
More
Hello and thanks for tour support.
Also "launcher has stopped" i have to consider as a brick situation?
Palese led me know because i tried to update from chinese firmware but Now it doesn't work, i am able to start in fastboot mode
Thank you vero much fo and your advice
2nd March 2017, 12:00 PM |#13  
Senior Member
Flag Petah Tiqwa
Thanks Meter: 442
 
Donate to Me
More
regarding the launcher errors, please try to unpair your watch and re-pair it again, it's a non-brick situation.
29th March 2017, 04:50 PM |#14  
Junior Member
Thanks Meter: 0
 
More
after i worte: fastboot boot Amazfit-mod-recovery.img . it says:

downloading 'boot.img'...
FAILED (command write failed (Unknown error))
finished. total time: 5.014s
30th March 2017, 07:28 AM |#15  
OP Senior Member
Thanks Meter: 2,516
 
More
Quote:
Originally Posted by alon1211

after i worte: fastboot boot Amazfit-mod-recovery.img . it says:

downloading 'boot.img'...
FAILED (command write failed (Unknown error))
finished. total time: 5.014s

Try a different USB cable. Bad cables are known to produce that error.
31st March 2017, 08:23 AM |#16  
Member
Flag San Jose
Thanks Meter: 12
 
Donate to Me
More
This is pretty awesome! I used this to convert my Chinese Amazfit watch to English ROM, and it seems to work OK.

However, there's a piece missing from the bundle -- the recovery image. There's an OTA available, and I pulled the update.zip file using the Fastboot trick so the OS didn't load and delete it - then booted the "mod recovery". Here's that update.zip (to 1.3.2b): https://mega.nz/#!nIBDhLrR!7nQlWsn-T...2R3dSavrDp1wsA

The OTA didn't succeed -- when it went to reboot to recovery and apply the update, it booted with Chinese text in recovery boot and failed with just one word - "Error". I'd imagine that's because recovery.img wasn't part of the bundle, so my watch still has the Chinese ROM recovery on it. Looking at the update.zip, it's fairly clear it's built in English - with English error messages in "updater-script".

I'm hunting around for the English ROM's recovery image, and will probably find it in the next few minutes, but figure I should mention this hole - and that this routine is also useful for converting to English. It'd been demonstrated before that you can run the English ROM just by flashing it (and boot.img), but no unified thread seems to exist for it yet (that I can find via Googling at least).

edit: Literally 5 minutes later, bam. https://forum.xda-developers.com/sho...&postcount=599 - I downloaded that Fix_recovery bundle, pushed it to /data/media/0/ from the mod recovery, ran it, and it gave some errors but fell back to the "dd" method. So, all that's needed to get a complete English ROM flash is to add recovery.img and the line:
Code:
busybox dd if=recovery.img of=/dev/block/platform/jzmmc_v1.2.0/by-name/recovery bs=4096
31st March 2017, 02:02 PM |#17  
Member
Thanks Meter: 7
 
More
Hi All,

I have just received my watch from a BT/WiFi issue repair.
I am not sure if they have fixed it as starting the watch and
I am getting "Unfortunately the launcher has stopped" message.
I do see the charging indicator but this is pretty much the only thing I see.
If I reboot pushing the button I get to the same point.

I see that this is an old problem. How do you guys fix this?
I do have adb shell access. Can I somehow reset to factory default using adb?

Thanks
Dimitar
31st March 2017, 02:29 PM |#18  
OP Senior Member
Thanks Meter: 2,516
 
More
Quote:
Originally Posted by dpenevdpenev

Hi All,

I have just received my watch from a BT/WiFi issue repair.
I am not sure if they have fixed it as starting the watch and
I am getting "Unfortunately the launcher has stopped" message.
I do see the charging indicator but this is pretty much the only thing I see.
If I reboot pushing the button I get to the same point.

I see that this is an old problem. How do you guys fix this?
I do have adb shell access. Can I somehow reset to factory default using adb?

Thanks
Dimitar

You can boot into the bootloader (fastboot) with "adb shell reboot bootloader". Then in fastboot you can tyoe "fastboot -w continue". That will boot the watch normally, but clear cache and all userdata.
31st March 2017, 03:22 PM |#19  
Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by Neuer_User

You can boot into the bootloader (fastboot) with "adb shell reboot bootloader". Then in fastboot you can tyoe "fastboot -w continue". That will boot the watch normally, but clear cache and all userdata.

Thanks Neuer_User,

what I did:

1. I have entered Fastboot as you explained. Fastboot logo on the watch
2. :~$fastboot devices
0123456789 fastboot
:~$fastboot -w continue (this in the Linux bash shell)
resuming boot...
FAILED (status read failed (No such device))
finished. total time: 6.395s
:~$
The watch reboots due to above

Or should I enter fastboot watch shell first?
The above procedure doesn't help.
Still I get "Unfortunately the launcher has stopped"

This should be on the original Chinese ROM 1.2.9 as far as I remember. It was long time ago I ship the watch to China for repair.
Should go to Pace ROM. what would you advice.

Thank you once again.
31st March 2017, 05:51 PM |#20  
OP Senior Member
Thanks Meter: 2,516
 
More
Quote:
Originally Posted by dpenevdpenev

Thanks Neuer_User,

what I did:

1. I have entered Fastboot as you explained. Fastboot logo on the watch
2. :~$fastboot devices
0123456789 fastboot
:~$fastboot -w continue (this in the Linux bash shell)
resuming boot...
FAILED (status read failed (No such device))
finished. total time: 6.395s
:~$
The watch reboots due to above

Or should I enter fastboot watch shell first?
The above procedure doesn't help.
Still I get "Unfortunately the launcher has stopped"

This should be on the original Chinese ROM 1.2.9 as far as I remember. It was long time ago I ship the watch to China for repair.
Should go to Pace ROM. what would you advice.

Thank you once again.

Hmm, if that doesn't work, try "fastboot erase cache" and "fastboot erase data". That will really completely delete all user and cache data. The next restart should take a long time.
31st March 2017, 09:13 PM |#21  
Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by Neuer_User

Hmm, if that doesn't work, try "fastboot erase cache" and "fastboot erase data". That will really completely delete all user and cache data. The next restart should take a long time.

Hi Neuer_User

"fastboot erase data" did the job!
It looks as equivalent to factory reset and I got the QR code after reboot.
Thank you very much for the help!
Dimitar
Post Reply Subscribe to Thread

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

Advanced Search
Display Modes