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
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
My watch is stuck in Bootloop, sometimes I can get into fastboot mode but mostly only the LG logo. Want to make a factory reset but can't get into recovery mode. When I choose recovery from fastboot menu the clock only restarts back to bootloop.
Is there another way to reset the watch besides the recovery mode?
Maybe the battery was dead?
My last watch "LG Watch Urbane" had the same situation as you,and I had tried to flash it,but nothing works.
TomLiu.CMJH said:
Maybe the battery was dead?
My last watch "LG Watch Urbane" had the same situation as you,and I had tried to flash it,but nothing works.
Click to expand...
Click to collapse
Ok. Maybe I try change the battery.
LG Watch Sport stuck in bootloop
You would first need to find the firmware online for your specific watch. The firmware should consist of three image files, boot.img, recovery.img, and system.img. You'll flash all three separately using fastboot commands. Once your watch is recognized via "fastboot devices" you can type the commands one after another (waiting for each to finish before proceeding). The commands would be...
fastboot flash boot (drag and drop boot.img to command window to copy its path)
fastboot flash system (drag and drop boot.img to command window to copy its path)
fastboot flash recovery (drag and drop boot.img to command window to copy its path)
There's more info on YouTube or XDA if needed. Let me know if you have questions, too
My watch switches off randomly and the only way to restart it is to put it on the charging device and restart it. This is not a battery related issue as the watch switches off at around 90%+ battery level. There is no consistent way of reproducing this problem. I've had this random switching off occur mostly when I have Google Fit and Google Play Music running together on the watch. I have tried doing a factory reset and the problem persists.
It most likely seems like a hardware issue, although, I started facing this issue after the WearOS update. I wanted to check if anyone else has encountered this problem and has been able to solve it.
Thanks!
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?
Hi, I have a semibrick on my X3 Superzoom (Global), and I can't seem to restore the original firmware. When it was working properly, I think the phone was updated to the latest version available in Europe (RMX2081EU_11.A.50), hence Realme UI 1.0.
I do not remember very well what I did, it's been a few weeks since my "screw up", I must have flashed an untrusted firmware, the thing is that when rebooting the screen looks black and goes into a continuous bootloop, but allows to enter fastboot mode with power + Vol down (I know because I can launch fastboot commands). Curiously, when it goes into bootloop you don't see the Realme logo, I discovered that the logo is there but with the screen illumination at minimum, and you can only glimpse a little if you put it under a lamp. Very strange.
Since it can go into fastboot mode I have tried flashing several firmwares for my phone, RMX2086 and none of them repair brik. I have tried always by command line because with MsmDownloadTool I don't have login access and with Realme Flash Tool always shows error "cannot find central directory", I have tried also with QFil and I can't get it to stay stable on the port.
I flash with command line with "fastboot flash" all .img files of super, recovery, boot, boot, dtbo, vbmeta (in that order) but it does nothing. Furthermore, I have tried with several ofp files like for example the following file from realmefirmware.com, which seems to be the last released full version of Realme UI 2.0 (I have tried also with Realme UI 1.0 versions):
RMX2086GDPR_11_C.11_2022011318270168.zip (I decrypt the ofp file inside to extract the .img files.).
Interestingly, I can flash TWRP Recovery (it works, and you see the screen with normal TWRP recovery) and from the recovery I can flash a Custom Recovery like PixelPlusUI. The phone boots (no logo visible) in CustomROM normally, but after a while of use the screen turns off but working ROM.
What should I do? Although I have some flashing experience, I'm pretty much stuck. Can anyone give me any suggestions?
Sorry with making it so long, but I wanted to explain this as best as possible so it is well understood.
When you already upgrades to Android 11, you can not flash custom rom, otherwise it bricks, because all the custom roms required android 10 ROM system, you may downgrade using flash tool (I tried but failed to flash any stock rom using any tool, only able to flash using fastboot commands)
bernarbernuli said:
Hi, I have a semibrick on my X3 Superzoom (Global), and I can't seem to restore the original firmware. When it was working properly, I think the phone was updated to the latest version available in Europe (RMX2081EU_11.A.50), hence Realme UI 1.0.
I do not remember very well what I did, it's been a few weeks since my "screw up", I must have flashed an untrusted firmware, the thing is that when rebooting the screen looks black and goes into a continuous bootloop, but allows to enter fastboot mode with power + Vol down (I know because I can launch fastboot commands). Curiously, when it goes into bootloop you don't see the Realme logo, I discovered that the logo is there but with the screen illumination at minimum, and you can only glimpse a little if you put it under a lamp. Very strange.
Since it can go into fastboot mode I have tried flashing several firmwares for my phone, RMX2086 and none of them repair brik. I have tried always by command line because with MsmDownloadTool I don't have login access and with Realme Flash Tool always shows error "cannot find central directory", I have tried also with QFil and I can't get it to stay stable on the port.
I flash with command line with "fastboot flash" all .img files of super, recovery, boot, boot, dtbo, vbmeta (in that order) but it does nothing. Furthermore, I have tried with several ofp files like for example the following file from realmefirmware.com, which seems to be the last released full version of Realme UI 2.0 (I have tried also with Realme UI 1.0 versions):
RMX2086GDPR_11_C.11_2022011318270168.zip (I decrypt the ofp file inside to extract the .img files.).
Interestingly, I can flash TWRP Recovery (it works, and you see the screen with normal TWRP recovery) and from the recovery I can flash a Custom Recovery like PixelPlusUI. The phone boots (no logo visible) in CustomROM normally, but after a while of use the screen turns off but working ROM.
What should I do? Although I have some flashing experience, I'm pretty much stuck. Can anyone give me any suggestions?
Sorry with making it so long, but I wanted to explain this as best as possible so it is well understood.
Click to expand...
Click to collapse
Have you found solution? I have exactly the same problem!
maskalicz said:
Have you found solution? I have exactly the same problem!
Click to expand...
Click to collapse
It's been over a year since it happened, I didn't find a solution on my own, and since it was still under warranty, I sent it to the official technical service and a couple of weeks later I received it back with the firmware working.
Hello, i want to share my experience because it may me useful for others. I have also a question for you at the end of the story.
I rooted my MI A3 with magisk but without twrp back in 2019 following the guide posted on this forum. The phone had android 9 and I never did software updates. Once in a while a messagge appeared on the screen saying that my software was obsolete and that I needed to update but I always managed to dodge it.
Some days ago my phone started behaving strangly (eg: I turned the volume down to zero but it turned up by itself) so I decided to reboot it. Something went wrong and the phone rebooted in fastboot mode. I tried many things but the phone was only able to boot in fastboot mode.
I thought that maybe the problem was related to the software update that sometimes was popping on the screen. So, i connected the phone to my pc and executed some fastboot commands:
fastboot getvar current-slot (to know which partition was in use. It was B)
fastboot set_active A (to switch to the other partition)
fastboot reboot
The phone rebooted correctly but it was on android 10 (before the problem it was on android 9) and without root. Everything seemed working fine and all the data was safe (only one thing changed, the boot process require much more time now). So, I realized that the phone applied the system update by itself (without my consent).
Now my question. The phone works well for the moment but how can i check the status of the partition B? I suspect that it may be damaged.
Furthermore I would like to flash the stock firmware, clear all the data and unroot the phone. Can I proceed? Should I flash both partitions?
Thanks
Any suggestions?