Related
Hi All..I have a galaxy S4 paired to by Asus zenwatch 2. I keep flashing custom ROMS and am tired of always having to factory reset and pair ZW2 to the phone..
Finally found a way of surviving custom ROM flashing..Steps in below post
No. Stop flashing roms.
Sent from my Nexus 6P using Tapatalk
kenkiller said:
No. Stop flashing roms.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
On XDA once you are used to custom roms..That's not possible bro
Anyways thanks for the response..I hope some way comes out sooner or later for flashaholics..
1. Lets suppose your android watch is paired with Phone A OR Phone with ROM A
2. You have flashed Rom B on your phone or using a new Phone B
3. Now, enable developer options on your watch and turn on ADB Debugging
4. Connect Watch to PC and open command prompt. Ensure that the command 'adb devices' lists your watch. If not use ADB Fastboot tools from the link http://forum.xda-developers.com/showthread.php?t=2588979
5. Run the command adb shell "pm clear com.google.android.gms && reboot" for your watch. This should reboot your watch
6. Run Android Wear app on your phone and it discovers your watch and syncs
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
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
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?
Hey. I might have killed my phone but I am still sort of hopeful I can save it.
I don't care about the data on the phone I am just trying to install an OS.
1. When I boot into TWRP I am asked for a password. This is niether my pin, "password" nor "default_password". Some suggest going into android to fix this but I no longer have an os.
2. Hitting cancel to advance and entering wipe menu it appears some partitions are missing. These are the phone partitions I see: Dalvik/ART, Data, interal storage even when everything is checked in the mount settings.
3. When I use the fastboot terminal program to install roms it complains that some of the partitions are 'raw' and can't be written to.
4. When I use sideload the device stops being recognized by fastboot.
5. I can install ROMs from TWRP and it looks like it works but I still don't get a working system.
6. I tried to flash no-verity-opt-encrypt 6.1 but that doesn't seem to effect anything in my situation.
7. RSD Lite and universal adb driver can't see my phone even though i have the driver installed and can interact with fastboot.
Is there anything else I should try?
eunem said:
Hey. I might have killed my phone but I am still sort of hopeful I can save it.
I don't care about the data on the phone I am just trying to install an OS.
1. When I boot into TWRP I am asked for a password. This is niether my pin, "password" nor "default_password". Some suggest going into android to fix this but I no longer have an os.
2. Hitting cancel to advance and entering wipe menu it appears some partitions are missing. These are the phone partitions I see: Dalvik/ART, Data, interal storage even when everything is checked in the mount settings.
3. When I use the fastboot terminal program to install roms it complains that some of the partitions are 'raw' and can't be written to.
4. When I use sideload the device stops being recognized by fastboot.
5. I can install ROMs from TWRP and it looks like it works but I still don't get a working system.
6. I tried to flash no-verity-opt-encrypt 6.1 but that doesn't seem to effect anything in my situation.
7. RSD Lite and universal adb driver can't see my phone even though i have the driver installed and can interact with fastboot.
Is there anything else I should try?
Click to expand...
Click to collapse
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com