Hello.
I have Amazfit Pace A1612 on stock old firmware 1.3.4f with a broken button. I'd like to update firmware, but I can't do it due to really weird software issues. The list of the problems includes:
Can't boot into Fastboot mode - the watch just reboots normally after 'adb shell reboot bootloader' command;
Can't make Factory Reset - the watch just reboots normally;
Can't update - the watch checks for a new firmware version, says that 1.3.8a is available, then I can confirm updating, but after downloading and rebooting nothing changes - just an old firmware. I can tap Update button again and repeat the whole process, but everything remains the same.
At the same time everything else works just fine: all functions work, GPS works, PC recognizes it as Amazfit Pace external storage device, adb works in 'device' mode (install and uninstall commands work), I can connect and sync it with Amazfit app.
So, is it possible to do something without a working button? I would really like to get rid of all those issues.
Systematis said:
Hello.
I have Amazfit Pace A1612 on stock old firmware 1.3.4f with a broken button. I'd like to update firmware, but I can't do it due to really weird software issues. The list of the problems includes:
Can't boot into Fastboot mode - the watch just reboots normally after 'adb shell reboot bootloader' command;
Can't make Factory Reset - the watch just reboots normally;
Can't update - the watch checks for a new firmware version, says that 1.3.8a is available, then I can confirm updating, but after downloading and rebooting nothing changes - just an old firmware. I can tap Update button again and repeat the whole process, but everything remains the same.
At the same time everything else works just fine: all functions work, GPS works, PC recognizes it as Amazfit Pace external storage device, adb works in 'device' mode (install and uninstall commands work), I can connect and sync it with Amazfit app.
So, is it possible to do something without a working button? I would really like to get rid of all those issues.
Click to expand...
Click to collapse
Try this: https://mega.nz/#!sp4lxQIA!2Z4iSxLPEb1AXcOVXh12VrfXRFbbqc1GaPniqaWsXoU
It's an official update from Huami.
Saratoga79 said:
It's an official update from Huami.
Click to expand...
Click to collapse
I've just tried it, but without success. I assume it's a wrapper for adb commands, so the watch simply reboots after executing option 1 or 2. Option 4 successfully collects and pulls log files.
Code:
Please select[1/2/3/4], press enter to continue:
1
start to upgrade
***************************************************************
* 1.Please make sure that update.zip is in the current folder *
* 1.Please make sure the watch is connected to adb *
***************************************************************
Send update.zip to watch, please wait...
1999 KB/s (213515625 bytes in 104.275s)
Start to upgrade..
Systematis said:
Hello.
I have Amazfit Pace A1612 on stock old firmware 1.3.4f with a broken button. I'd like to update firmware, but I can't do it due to really weird software issues. The list of the problems includes:
Can't boot into Fastboot mode - the watch just reboots normally after 'adb shell reboot bootloader' command;
Can't make Factory Reset - the watch just reboots normally;
Can't update - the watch checks for a new firmware version, says that 1.3.8a is available, then I can confirm updating, but after downloading and rebooting nothing changes - just an old firmware. I can tap Update button again and repeat the whole process, but everything remains the same.
.
Click to expand...
Click to collapse
Your problem is Power buttons do not work.
It is a hardware problem.
Caused by the button has moisture.
I have encountered this problem before.
Can we factory reset amazfit Pace from Fast Bootloader via ADB Command Prompt?
guhan1995viswa said:
Can we factory reset amazfit Pace from Fast Bootloader via ADB Command Prompt?
Click to expand...
Click to collapse
Unlock Bootloader then using command via Fastboot Mode.
fastboot erase cache
fastboot erase data
any solutions?
Systematis said:
Hello.
I have Amazfit Pace A1612 on stock old firmware 1.3.4f with a broken button. I'd like to update firmware, but I can't do it due to really weird software issues. The list of the problems includes:
Can't boot into Fastboot mode - the watch just reboots normally after 'adb shell reboot bootloader' command;
Can't make Factory Reset - the watch just reboots normally;
Can't update - the watch checks for a new firmware version, says that 1.3.8a is available, then I can confirm updating, but after downloading and rebooting nothing changes - just an old firmware. I can tap Update button again and repeat the whole process, but everything remains the same.
At the same time everything else works just fine: all functions work, GPS works, PC recognizes it as Amazfit Pace external storage device, adb works in 'device' mode (install and uninstall commands work), I can connect and sync it with Amazfit app.
So, is it possible to do something without a working button? I would really like to get rid of all those issues.
Click to expand...
Click to collapse
i have the same problem with you.
have you got any solutions for this problem?
Related
Hi all,
I need your help. Given what I already (unsuccessfully) tried, I'm not sure if there will be a solution, at all...worst case, my Huawei Smartwatch isn't usable anymore,,,
Given that there is a preview version of WEAR Version 2.0 available, I thought it might be good idea to install and test. In fact, given that I manually/successfully installed the WEAR Version 1.4, some months ago, I was sure that I can manage to do it, with the preview version, as well.
I followed the steps, which you can find here developer.android.com/wear/preview/downloads
The point is, after the update has been done (given the message in ADB) the Smartwatch didn't automatically start to reboot. I was waiting about 30- 40 minutes, but nothing happened. So, I rebooted the watch by my own, via the fastboot menu.
But, the watch was only booting up to the Huawei Logo and nothing more did happen. I was also waiting for 30 - 40 minuntes.
After that, I googled and found a way how to access the fastboot mode (long and shore pressing of the power button of the watch) Here I tried the possible options. But, I would say, the only option which worked was "shutdown". All the other option, except fastboot recovery, brought me to the same result, as described above. Finally, I tried fastboot recovery, which might have made the situation even worse...means, after the Huawei Logo I can see a fallen over "android" with a open flap / a sign with a bang plus some text lines. But, it's so fast disappearing, nobody can read...even this is coming up again and again.
Next what I wanted to try is, to flash the WEAR version 1.4 again. But, it seems to be that ADB doesn't find the Huawei device anymore. (command ADB Devices doesn't show me any device)
Meanwhile, even it is somehow not logical (as it was working before with my "Standard Win 10 PC and the drivers installed) I tried 3 different PC with different combinations of Windows Version (7,8, 10), USB Ports (2.0 and 3.0) and probably almost all Android USB Drivers you can find.on the WEB. I even followed a procedure how to modify the INF file with some HUAWEI specific entries. I also let the watch run, overnight, in the loop mode, so the battery got empty..which really didn't help, as once loaded again, the watch started with the "loop procedure" again. However, I tried all the steps I did before, once again.
Regarding ADB/Fastboot, I'm not using the full Android SDK package, but the minimal version, at first version 1.1.3 and the later 1.4.3. I also followed the hints to open a command line with shift and right click "in" the respective ADB folder.
So, as you can read, I already tried a lot of thinks with no luck. in fact, I wasn't able to find anything more when I googled.
Hope you / some Android "guru's" can help me, now.
Here some of my current thoughts to which you have answers/comments.
1. Could it be, that the watch is totally broken and can't be "repaired" anymore?
2. Could it be, even the watch is in the fastboot mode, that the watch really isn't in a "full" one (...because the upgrade procedure of WAER 2.0 somehow failed) and this might be the reason, why ADB can't find the device anymore?
3. If 2. is really the case, is there any way to force a "full" fastboot mode?
4. Do you have any other idea, what can be done to make ADB aware of the device?
5. Is there meanwhile a specific ADB driver for the HUAWEI watch available? / Can somebody send me a link to a driver which is definitely working with that watch.
6.Whatever you can think of.
I really would appreciate any help to get my problem fixed.
Thanks in advance
Claus
TL;DR
When you used flash-all.bat it wipes your userdata partition. That means all settings are back to default. So no developer options, no adb debugging.
You can only use fastboot.
Code:
fastboot devices -l
needs to show your device.
- Then untargz the factory image.
- unzip the *.zip
- print out the flash-all.bat (or open in an editor)
use these commands:
Code:
fastboot flash bootloader bootloader-sturgeon-nvd36i.img
fastboot reboot-bootloader
sleep 5
and now flash each image in sequence (boot, cache, recovery, system, userdata.img
fastboot's 2nd param is like the basename of the corresponding .img file
Hi ranf,
first of all, THANKS A LOT, my watch is alive, again.
FYI, what I did...both ways are working, but as I saw, that you updated the procedure, I did the flash the watch two times. To add, I flashed the WEAR 2.0 Preview version.
1. The normal flash process by using one IMG and the one ZIP file, following the steps in the flash-all.bat.
2. Your updated "version", means the IMG file, plus all IMGs (extract from the ZIP file) plus the steps you have written, above.
I just finnished number 2 and the watch is synchronizing..looks good so far.
Thanks
Claus
Nice.
I have the suspicion that this "sleep 5" (seconds) sometimes is not enough.
I did All the steps, but my watch is stucked in moving circles screen
In case you bricked your watch, here is a tutorial how to unbrick the watch:
1. What is a "bricked" watch?
A bricked watch does no longer boot. It typically stops at the boot logo and waits forever. This can happen for example, if a flash of the system image failed and the boot image can no longer boot the system.
In such cases, you cannot reach adb from the command line, so there seems to be no way to recover the watch. Fortunately, it has been discovered how fastboot can be entered without a running system.
2. Procedure
Step 1: Get into fastboot
This is the most difficult part. @kiralex1995 has developed a procedure that will lead reproducible to boot the watch into fastboot mode, but it may take many tries (one user reported that it took him 30 min of tries).
Follow this guide: https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829
When you are in fastboot and see the fastboot logo, you have mastered the most difficult part.
Step 2: Choose a ROM to flash on the watch
There are currently three possible ROMs to choose from:
a.) The English AmazFit firmware 1.3.0n
Download the following file on your PC: https://mega.nz/#!xIkC1IQZ!bLLSN9BMvbp7zhZHg2oQq6p4ud-EFyUYkatCGKgHeS8
b) The Chinese AmazFit firmware 1.2.5a
Download the following file on your PC: https://mega.nz/#!tNdggR4b!VXmExGqdNixrj8pVLqTkAi_munmjF5RidRJP9L-LAXE
c) An old Chinese AmazFit firmware 0.9.50:
Download the following file on your PC: https://mega.nz/#!wY9mEQoI!0ARB0MaK0byjttgrPmJJQX4ZFdIXgHOUquxqFhghg7U
Step 3: Download flash script from xda
Download the attached flash script from this post to your PC.
Step 4: Unpack the archive on your PC
Depending on you PC choose the right method to extract the files in the ROM archive and the flash script.
Step 4: Boot the watch into special recovery
Check that your fastboot drivers see that watch (which should still show the fastboot logo):
'fastboot devices'
You should see your device listed. Otherwise check your fastboot driver installation on your PC. (Note: On Linux you sometimes need to use "sudo fastboot ...".)
Then boot the modded recovery that is included in the archive you unpacked in step 2.
'fastboot boot Amazfit-mod-recovery.img'
You will see a "FAILED" message on your commandline. This is normal.
On the watch you should see the recovery triangle and the text "No command".
Step 5: Transfer the ROM files and the flash script onto the watch
First check that you are now able to connect to your watch via adb:
'adb devices'
You should see your watch listed. Otherwise check you "adb driver" installation. For Windows take care that you use Khoushs universal adb drivers.
Then push the files to the watch:
'adb push boot.img /data/media/0/
adb push system.img.gz /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/'
Step 6: Enter the shell on the watch and check your files
After you have successfully transferred the files to the watch, you then enter the shell on the watch:
'adb shell'
You should see only a "#", meaning you have full root access.
Now switch drirectory to the sdcard
'cd /data/media/0/
ls'
You should see your files on the "sdcard", including the ones that were pushed before
7. Start flashing the files
Run the flash sccript with the following command on the watch:
'sh flash_rom.sh'
If everything worked correctly, you should see something like:
Code:
Validating images
boot.img.gz: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE! 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.
8. OPTIONAL: Delete the dalvik-cache
You can erase the dalvik-cache on the watch with the following command:
'rm -rf /data/dalvik-cache'
This will make the system "re-optimize" all apps when it boots (successfully) the next time. This is optional, as you could always do that later again.
9. Reboot the watch
If everything is ok, then you can reboot the watch
'reboot'
Your watch should boot normally into the flashed system, you downloaded. CONGRATULATIONS, you unbricked your watch!
Thank you for this post.
Neuer_User said:
In case you bricked your watch, here is a tutorial how to unbrick the watch:
1. What is a "bricked" watch?
A bricked watch does no longer boot. It typically stops at the boot logo and waits forever. This can happen for example, if a flash of the system image failed and the boot image can no longer boot the system.....[/B]
Click to expand...
Click to collapse
I'm so happy that my post help people. Thanks to your job and thanks to your rom @Neuer_User .
I wonder if it would be possible to create a rom with all google services included ?
First watch has just successfully been unbricked (1immortals watch) [emoji106] [emoji2]
kiralex1995 said:
I'm so happy that my post help people. Thanks to your job and thanks to your rom @Neuer_User .
I wonder if it would be possible to create a rom with all google services included ?
Click to expand...
Click to collapse
Yes, it would be possible. But you also need to look at connectivity. The watch checks does turn off wlan automatically.
@Neuer_User, you're a GOD !!!
All bow @Neuer_User , he is the true ruler of Amazfit, conquer of the M200 SoC, bringer of root to the MIPS platform ! all hail the king !!!
Neuer_User said:
Yes, it would be possible. But you also need to look at connectivity. The watch checks does turn off wlan automatically.
Click to expand...
Click to collapse
Well i guess constant WiFi would dramatically reduce the running time? On the other hand it might just be turned on for short periods, don't know how Google does that.
1immortal said:
@Neuer_User, you're a GOD !!!
All bow @Neuer_User , he is the true ruler of Amazfit, conquer of the M200 SoC, bringer of root to the MIPS platform ! all hail the king !!!
Click to expand...
Click to collapse
Congratulations and thanks to Neuer_User.
hi, after this step the watch reboot and restart the loop on logo. why?
'fastboot boot Amazfit-mod-recovery.img'
You will see a "FAILED" message on your commandline. This is normal.
On the watch you should see the recovery triangle and the text "No command".
edit: after more test, i'm not able to go to recovery mode. For an errore, when i try another time to go to Fastboot mode, i push 2 times the button and i ERASE ALL the watch, now i have a device called JZ4785 USB Boot Device.
There's some way to save this watch?
Thanks.
I think that you have entered some "Deep" flash mode - the JZ4785 is the SoC model, and you need to provide a driver for the flashing process.
please download this tool:
ftp://ftp.ingenic.com/DevSupport/Tools/USBBurner/cloner-1.2.0/cloner-1.2.0-windows_release.zip
you will need a 32 bit machine for running that.
it contains the drivers and the software for flashing. I hope that there's a way of creating a dump file of a working watch, and flashing it directly on yours.
1immortal said:
I think that you have entered some "Deep" flash mode - the JZ4785 is the SoC model, and you need to provide a driver for the flashing process.
please download this tool:
ftp://ftp.ingenic.com/DevSupport/Tools/USBBurner/cloner-1.2.0/cloner-1.2.0-windows_release.zip
you will need a 32 bit machine for running that.
it contains the drivers and the software for flashing. I hope that there's a way of creating a dump file of a working watch, and flashing it directly on yours.
Click to expand...
Click to collapse
This could indeed be the case. Noone of us ever entered that mode so far. It would be very good to understand, how you really got into that. It must have happened in the first step, where you were supposed to enter fastboot. Did you see the screen on the watch with the two options? There is a video in the link of @kiralex1995 post. Maybe you can comment, what exactly looked identical for you and where it exactly started to differ.
In case, you are really in that SOC flash mode, the Ingenic USBburner tool would indeed, probably, be the right tool to reflash the watch. As I mentioned, nobody here used that before. I have some experience with similar tools for the MTK platform. I believe that it should be possible to generate the necessary dump from a working watch, but this is all theory so far.
Where are you located?
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 ...
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
regarding the launcher errors, please try to unpair your watch and re-pair it again, it's a non-brick situation.
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
alon1211 said:
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
Click to expand...
Click to collapse
Try a different USB cable. Bad cables are known to produce that error.
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-TF4bsMNBSaTOfimY-vo-Z2R3dSavrDp1wsA
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). :good:
edit: Literally 5 minutes later, bam. https://forum.xda-developers.com/showpost.php?p=71264431&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
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
dpenevdpenev said:
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
Click to expand...
Click to collapse
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.
Neuer_User said:
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.
Click to expand...
Click to collapse
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.
dpenevdpenev said:
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.
Click to expand...
Click to collapse
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.
Download Link: https://android.googleapis.com/pack.../f0095b7e9162d37af8f00140aea38d7922887a0a.zip
Enable Developer settings by going into Settings > Info > Tap "Build Number" a few times until a toast message says that you're now a developer
Activate "ADB Debugging"
Install THIS ADB Quick Installer with drivers if you don't have ADB installed yet
Open a CMD and type "adb start-server", connect your watch via USB and accept the connection on the watch
Then type "adb reboot recovery"
Your watch should display that it's in recovery mode now, swipe down to get more menu options
Select "Apply update from ADB" and swipe right
In the CMD cd to your Download folder
Type "adb sideload f0095b7e9162d37af8f00140aea38d7922887a0a.zip" and wait, it may appear stuck at some point but just wait!
After that's done select "Reboot" and swipe right
...
PROFIT!
It may or may not boot into Android Wear 2 at the first reboot. Leave it sitting for up to 15 Minutes and if it's still stuck on the boot animation force-turn-off the watch by holding the button. To prevent this you could also try to clear cache in the recovery before updating but I'm not 100% if that'd fix this, just a theory because a normal System Update would indeed wipe cache first.
Thanks, your guide worked perfectly, there are no replies so it seems doubtful but it's very clear and perfect.
Updated my watch to Android wear 2.0, as it got flashed from stock recovery means it should be stock OS from Asus
You are the man!!! For some reason it kept getting stuck after adding my Google account, so I did a full data and cache wipe afterwards, and now it's working smooth. I haven't had a chance to really play with it yet to get a good feel for it, though.
EpicLPer said:
Download Link: https://android.googleapis.com/pack.../f0095b7e9162d37af8f00140aea38d7922887a0a.zip
Enable Developer settings by going into Settings > Info > Tap "Build Number" a few times until a toast message says that you're now a developer
Install THIS ADB Quick Installer with drivers if you don't have ADB installed yet
Open a CMD and type "adb start-server", connect your watch via USB and accept the connection on the watch
Then type "adb reboot recovery"
Your watch should display that it's in recovery mode now, swipe down to get more menu options
Select "Apply update from ADB" and swipe right
In the CMD cd to your Download folder
Type "adb sideload f0095b7e9162d37af8f00140aea38d7922887a0a.zip" and wait, it may appear stuck at some point but just wait!
After that's done select "Reboot" and swipe right
...
PROFIT!
It may or may not boot into Android Wear 2 at the first reboot. Leave it sitting for up to 15 Minutes and if it's still stuck on the boot animation force-turn-off the watch by holding the button. To prevent this you could also try to clear cache in the recovery before updating but I'm not 100% if that'd fix this, just a theory because a normal System Update would indeed wipe cache first.
Click to expand...
Click to collapse
Can you please share a full rom zip, not only update zip?
---------- Post added at 20:16 ---------- Previous post was at 19:25 ----------
Anyone knows how to root the rom?
matze19999 said:
Can you please share a full rom zip, not only update zip?
---------- Post added at 20:16 ---------- Previous post was at 19:25 ----------
Anyone knows how to root the rom?
Click to expand...
Click to collapse
A full ROM will require someone to dump it from their watch.
Lrs121 said:
A full ROM will require someone to dump it from their watch.
Click to expand...
Click to collapse
Yeah, I know ^^
awesome finally. just flashed the 6.0.1 again its syncing now. had the watch lying around 3 weeks since i got tired of charging 2 times a day with webwear.
can go straight to recovery and sideload the update or should i wait out the 6.0.1 syncing with my phone ?
I just wanted to add that for #8 I have a Windows 10 PC and Minimal ADB installed and you can just drag the file to the CMD window instead of typing all of that.
My watch has definitely recognized that I'm a developer, but I don't the message to "accept the connection on the watch" anywhere.
I am typing the adb reboot recovery command in the outer shell of CMD, but get the message "error : device '(null)' not found.
Windows 10 machine. A little help, please?
EDIT: Got it!
I forced the Zenwatch into Recovery Mode manually and accepted to install update manually.
Hi
I'm trying to updae but cmd says:
error: protocol fault (no status)
and in watch:
You need adb 1.0.32 or newer to sideload to this device.
installation aborted
???
After enabling the developer-settings, you need to enter those settings and activate ADB-Debugging. After that your watch will be recognized and you get the "Accept connection" message on the watch.
Hello,
I flashed my Zen2 this morning and do not notice any lag like others are stating...actually runs pretty good. One thing I do notice however is that my phone shows an active connected bluetooth device (like when connected to a car stereo or speaker). This is different than my Moto2 watch when connected to the same phone. Also on the older Wear 1.5 software did not show as actively connected as a bluetooth device. Does this mean the Zen2 will be using more juice or that we can use it as a portable speaker to play music? Just seems odd as I have always had multiple watches connected to the same phone. I just grab whichever suits my needs for that day. Why would this change by updating from Wear 1.5 to Wear 2.0? I suspect we will notice more drain on both the phone and the watch...time will tell. As far as those concerned with updating just do it as Wear 2.0 works fine once you get used to the change.
Cheers
Thanks this procedure worked for me. I di have to power off and power back on when first boot hung on animation
Update is perfect
wait was good
Procedure worked great, easy and fast. I am receiving email notifications on the watch but no text messages. Any ideas?
i waited out the 6.0.1 syncing to my phone before sideloading aw2.0
what i did:
reboot to recovery
sideload update
factory reset watch
clear watch cache (i know its alrdy done by factory reset but still)
reboot
still got stuck at booting the 1st time. boot animation forever.
hard rebooted the watch and aw2.0 came up fine.
Full rom zip. Wipe system, data, cache, dalvik and flash the files in the zip with these commands:
fastboot format system
fastboot format userdata
fastboot flash system system.img
fastboot flash boot boot.img
optional:
fastboot flash cache cache.img
No update zip!
https://www.androidfilehost.com/?fid=961840155545583518
matze19999 said:
Full rom zip. Wipe system, data, cache, dalvik and flash the files in the zip with these commands:
fastboot flash system system.img
fastboot flash boot boot.img
optional:
fastboot flash cache cache.img
No update zip!
https://www.androidfilehost.com/?fid=961840155545583518
Click to expand...
Click to collapse
THX!
TheDantee said:
THX!
Click to expand...
Click to collapse
You're welcome bro
So I followed the steps, zero issues. Everything went like you said it would. When it rebooted I was still on 1.5....i rebooted again and same thing. Did a full factory reset and still won't take the update even though it seems to have been loaded. Tried clearing cache as well. Any ideas?
Sent from my S8
I have a problem connecting to Blutooth. I bought a car 2DIN radio for android. My phone turns on blutooth and connects to a call without a phone call. My radio with other smartphones connects seamlessly, has a problem with my phone only. My phone connects properly with the handsfree, with the speaker and other devices, just does not want to connect with my radio. I had an original Image, now I changed to MUI, but it is the same.
Is it really so difficult to repair if no one else has encountered such a problem?
Help
I'm fighting for 3 days and I do not know where I'm making a mistake. I was looking for a solution for bluetooth connection with 2DIN radio. I found the image in EUI 5.8 15S still works well. I had TWRP installed so there was no problem, I found the image I installed. Unfortunately bluetooth does not work. I wanted to install MIUI so I downloaded the image and here my problem starts. I am in TWRP unfortunately I can not access the phone memory. I will start everything from scratch. I will do everything as described:
I have ADB installed on my PC
on the phone I enter the system developer set
in the directory where I have downloaded twrp with shift PPM and the command window opens
adb devices command - correct answer
adb reboot command bootloader - telefin into bootloader mode
fastboot oem unlock command - correct answer
fastboot flash twrp twrp.img - install twrp
button + volume and power - twrp mode
in the twrp install button - and again the same I can not access the memory.
If I choose the memory, I have 0 mg memory and OTG memory
What I do is not where the error is.
wojt_wc said:
Help
I'm fighting for 3 days and I do not know where I'm making a mistake. I was looking for a solution for bluetooth connection with 2DIN radio. I found the image in EUI 5.8 15S still works well. I had TWRP installed so there was no problem, I found the image I installed. Unfortunately bluetooth does not work. I wanted to install MIUI so I downloaded the image and here my problem starts. I am in TWRP unfortunately I can not access the phone memory. I will start everything from scratch. I will do everything as described:
I have ADB installed on my PC
on the phone I enter the system developer set
in the directory where I have downloaded twrp with shift PPM and the command window opens
adb devices command - correct answer
adb reboot command bootloader - telefin into bootloader mode
fastboot oem unlock command - correct answer
fastboot flash twrp twrp.img - install twrp
button + volume and power - twrp mode
in the twrp install button - and again the same I can not access the memory.
If I choose the memory, I have 0 mg memory and OTG memory
What I do is not where the error is.
Click to expand...
Click to collapse
When you start it, is TWRP asking for a password? If it does, that means your phone is encrypted, which, for example, is the default for Indian firmwares. It's a bug, but not the end of the world. You have to hit cancel at the password prompt and restart recovery. It will eventually start without asking for a password and then you'll have access to the internal memory. Once, I had to restart TWRP about 10 times until this worked, so you have to be patient.
Thanks a lot. Actually I had to start again and it was OK. But now I have a bigger problem. I downloaded the picture MIUI 9. The installation ran smoothly. MIUI 9 has been installed but I can not take over the configuration. Even though the SIM card is inserted it does not see it. Can not find no IMEI. Can not set up MI Acccount. The phone is hot all the time and it's still on Mi Account. Can you stop it? Can I upload another image?
Yesterday at a late hour I managed to run everything on a regular basis on SmailSUI. I reinstalled the memory cleaner and it works fine. All the time I'm waiting for MIUI 9. As you work on this image you can check if BT is working properly. At me mixed with different images from this began. So far I have not found a system that works properly BT. When connected to another Android BT connects without a phone. You can not receive or call BT.
Thanks again for your help.
Hello,
I bought an Amazfit Stratos (A1619) and when I turned on, it asked to update to the latest version. I agreed and the watched seemed to be working fine, but after a couple of after, the watch started to not respond well to the commands, so I tried to restart it and then the watch was bricked, stucked in the amazfit logo.
I follow the first tutorial I found, for the Pace watch and it seemed to work, the watch went to the QR code phase, but I realized I installed the Pace firmware, so I redid the process again using the stratos file, but when I put the stratos file, the watch got stuck again in the amazfit logo.
I tried a couple of available firmwares (US stock firmware, firmware 2.3.7, Stratosfied), all without success. For the Stratosfied firmware, the watch starts the update, but it stops at around 75% and it does not go further.
Have anyone run in the same trouble? Any advice on how to unbrick this watch?
Probably it has a damaged internal storage (eMMC), hardly you can fix it by installing any firmware, but maybe one of them, specially an old one, can be installed completely so the watch boots at least.
If you know how to flash from fastboot mode, you can do a full wipe (erase everything on watch, including system partition), using the commands bellow while in fastboot mode.
PS: only do this if you know what you are doing and if you know how to flash a firmware from fastboot manually or using some installer, otherwise the watch won't turn on anymore!
Code:
fastboot erase data
fastboot erase cache
fastboot erase userdata
fastboot erase system
Then try to flash an old firmware and do NOT upgrade if it works.
you can't install system on locked bootloader and if you erase it somehow the watch will not boot .
Only first three comands are available on locked BL
Check this:
https://forum.xda-developers.com/smartwatch/amazfit/guide-restore-null-sn-locked-t3775998