Hi,
For a few weeks now, my stratos 3 doesn't work despite all my efforts. The problems started to occur on 4.2.5.0.
When I boot the watch in smart mode, I only see a black screen. But the watch can be linked to the phone in bluetooth and adb commands are working fine.
I can restart the watch in ultra mode using adb reboot mcu and it works fine in that mode.
I tried to wipe data with adb reboot wipe, same
I tried to install the stock firmware (https://forum.xda-developers.com/smartwatch/amazfit/fw-tool-stock-global-international-t4031153), no change (even with older FW)
I tried the PACEficator Custom ROM (https://forum.xda-developers.com/smartwatch/amazfit/paceficator-project-stratos-3-multi-t4033223), it worked for 2 minutes, then the problem reappeared.
I tried to flash the watch with the ingenic tool (https://forum.xda-developers.com/smartwatch/amazfit/tutorial-ingenic-cloner-tool-aamzfit-t3908237), same...
At this point I don't know what to do, except only using the watch in ultra mode.
Is my SD card damage? Or is it another component ?
If you have any lead, idea or insight, I would take it willingly :fingers-crossed:
elimeXCI said:
Hi,
For a few weeks now, my stratos 3 doesn't work despite all my efforts. The problems started to occur on 4.2.5.0.
When I boot the watch in smart mode, I only see a black screen. But the watch can be linked to the phone in bluetooth and adb commands are working fine.
I can restart the watch in ultra mode using adb reboot mcu and it works fine in that mode.
...
Click to expand...
Click to collapse
Hi! I have the same problem that I encountered in the same period ( the 4th May FW 4.2.5.0) but in my case the watch optimizes app for 20 minutes (15% of battery), then gives QR but can not pair the mobile. I skipped QR from adb and the watch boots in Smart mode but it works wery slowly and shows big charge leak. In my case i can pair with earphones but not with the mobile.
I did all to pair but adb shell dumpsys bluetooth_manager says:
enabled: false
state: 10
address: D8:80:3C:3B:71:F3
name: Watch
Bluetooth Service not connected
I upgraded with original OTA update to 4.2.6.0 - useles
I unlocked bootloader and flashed with Saratoga moded FW 4.2.6.0 - useless
Now thinking to downgrade or eraze and unbrick.
Taking into consideration mentioned above I don't think our problem is a hardware one.
Hello,
Little update...
I decided to downgrade to 4.2.2.1 to see what would happen.
But first I started to go into fastboot mode and then I rebooted the watch. A message that I had never seen before appeared :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't even know what is the launcher , so I closed it.
And then, :angel: :angel: :angel: the watch started to work normally.
I don't know what happened, and if the problems that I had will be coming back. But I'm praying that it won't.
So I'm now in 4.2.6.0 and everything seems to be working fine.
You're right Godfly, That's not a hardware issue.
elimeXCI said:
Hello,
Little update...
I decided to downgrade to 4.2.2.1 to see what would happen.
But first I started to go into fastboot mode and then I rebooted the watch. ....
I don't even know what is the launcher , so I closed it.
And then, :angel: :angel: :angel: the watch started to work normally.
I don't know what happened, and if the problems that I had will be coming back. But I'm praying that it won't.
So I'm now in 4.2.6.0 and everything seems to be working fine.
You're right Godfly, That's not a hardware issue.
Click to expand...
Click to collapse
Congrats! I downgraded to 4.2.2.1 - useless. Now upgrading to 4.2.4.0. I am afraid will have to to flash the watch with the Ingenic Cloner tool and dawngrade like you.
Don't go to 4.2.6.0 it's so bugged 4.2.5.0 is ok
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I bought second hand z4 from some guy who work for Sony. How to flash normal (not prototype) rom in this device? Everything works fine, Camera., Apps, Android os is 5.0.2 kernel 3.10.49, everything is smooth, but there is anoying message "You have crash artifacts to upload" all the time!? If I cant flash normal rom, is there any method to kill that message? Thanks..
Bite_my_shiny_metal_ass! said:
I bought second hand z4 from some guy who work for Sony. How to flash normal (not prototype) rom in this device? Everything works fine, Camera., Apps, Android os is 5.0.2 kernel 3.10.49, everything is smooth, but there is anoying message "You have crash artifacts to upload" all the time!? If I cant flash normal rom, is there any method to kill that message? Thanks..
Click to expand...
Click to collapse
I believe that sticker talks for itself and my advice would be not to be so open about this transaction.
In any case unless you have an EMMA account with relevant privileges you can't do much.
If you are lucky enough and Sony enables OTA updates for customer acceptance firmware applicable to the variant you have then at least you might get a firmware update in the future. But if you have as you say the crash handling app installed then probably you have an quite old FW which might not get any OTA.
Is there any way to instal new firmware without OTA? I think for z4 actual android official version is 5.11? If i kill process com.sonymobile.crashmonitor.system and com.sonymobile.crashmonitor.ui anoying message "You have crash artifacts to upload" is gone. Z4 is alredy long time on the market, so stickers now dont have much point anymore?
Bite_my_shiny_metal_ass! said:
Is there any way to instal new firmware without OTA? I think for z4 actual android official version is 5.11? If i kill process com.sonymobile.crashmonitor.system and com.sonymobile.crashmonitor.ui anoying message "You have crash artifacts to upload" is gone. Z4 is alredy long time on the market, so stickers now dont have much point anymore?
Click to expand...
Click to collapse
The last part is something you need to discuss with Sony but I don't believe a prototype unit on the loose is something they don't take seriously.
If I were you I'd ask the seller to take it back and refund you because as I wrote the only option for updates you have is either EMMA access with the proper permissions to download customer acceptance firmwares, someone with such access to give you the firmware or sony to enable OTA for customer acceptance firmware. The latter happens some times.
With the current firmware you have you can of course kill as you said some processes to get rid of the crash monitor app and notifications but there are still other debug bits enabled. If the firmware has root access enabled - there are such debug firmwares and you can check that from adb shell with su - you can clean it up a bit more.
That is all I can provide as info.
Solution is very simple. I download latest firmware 28.0.A.8.260 with XperiFirm and flash with flashtool and everything works perfect! No anoying messages anymore, nothing..
Bite_my_shiny_metal_ass! said:
Solution is very simple. I download latest firmware 28.0.A.8.260 with XperiFirm and flash with flashtool and everything works perfect! No anoying messages anymore, nothing..
Click to expand...
Click to collapse
Prototypes have a different bootloader so you can't flash retail firmware on it and vice versa.
Up to Z3 tablet this was valid also for tablets, if they changed that in Z4 then you are lucky.
Hi all,
think i bricked/ defected my Pace today. The idea was a mod with german language so i began to read here at xda for info. I'm on iOS now but modding on Android is nothing new for me, i modded some mobiles before, everthing workedtill today. I unlocked the bootloader and installed the mod, something went wrong i think, maybe i tried an incorrect image or something else, i don't know. After installing the watch wanted to update via OTA an after that it was shown as a Stratos in the Huami Amazfit Tool, sn was NULL an so on. The watch booted to os but the app was not able to read the QS Code for connection, touch doesn't work...
I can't say which ways i tried the last 6 to 8 hours to repair it and now i'm sure there is no bootloader/ software anymore on the watch. It starts with Amazfit Logo and stops with "No Command" & and the triangle. The only way to connect is in Fastboot, which shows chinese signs at the bottom of the display. There is no connection possible on ADB or otherwise.
Is there any way to get back the software on my watch? Maybe download mode which starts from my pc or something else? I'm on win 10 here, there is no linux machine or something else.
Thanks for reading
If you can get to fastboot and recovery, you have not deleted the bootloader.
Follow this guide: https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
Quinny899 said:
If you can get to fastboot and recovery, you have not deleted the bootloader.
Follow this guide: https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
Click to expand...
Click to collapse
Hi,
i tried this yesterday for about 10 to 15 attempts, but after step 4 there is no adb connection for step 5 and adb commands doesn't work. Getting the watch in fastboot is no problem anymore for me after last night
You have flashed Stratos firmware on your Pace, that's why touch didn't work. If the unbrick tutorial didn't work for you, then you should check your drivers: both drivers for adb and fastboot (they are different) should be installed and working properly. Sometimes you must re-connect the watch for the computer to detect it when the mode change, I usually keep Device Manager when I am using Windows to check this.
Or try AmazeROM installer, it has an option to start flashing from fastboot and it will guide you through the process.
Hi all,
sorry for my later post but under week i have no time for doing things like this here.
I checked adb and fastboot on the pc, installed system wide and works, fastboot drivers seems to be ok, but i have no idea how to check adb drivers. It's all the same, if i try this guide https://forum.xda-developers.com/sma...azfit-t3547300 or if i install amazeos with installer. The watch is recognized in fastboot but afterwards switching to adb there is no new connection, it's still in fastboot and does not switch to anything, i can restart it when amazeos installer script runs but nothing happens and if i let it run for about three hours the watch is still in fastboot and nothing happens there. In the device manager i see only an ADB Testing Device when in fastboot connected, on adb nothing happens there.
I tried everything on a clean win 7 machine, in this case the watch won't even recognize, so i could't run an installer or try to use the unbrick guide.
Just for information, it was Stratosfied which killed my watch in my mistake, but after that i think i deleted all with Amazfit Tools for doing the worst case for me here an unplugged it before reinstalling something else.
I attached some pics of the watch, first is after starting and directly after Amazfit logo, second is in fastboot with this method https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829, Point two there is not reachable, only point one fastboot, but in it i can't do anything though.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And for information, every fastboot command will be determind with "The command is not allowed"
My $20 hoot huawei p20 pro CLONE (here a link /w info about the phone with false specs full of bugs)https://www.freebrowsinglink.com/hoot-p20-pro/ got bricked a week ago after I left it connected to a Windows computer with internet access.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The story starts with when I tried to root the phone with KingoRoot, eventually ads started popping up, facebook, dating or porn sites and malware like that. I uninstalled KingoRoot and installed some anti spam software like avg and avast, but that did not help, ads kept coming. The phone has Android 5.1 Lollipop on it and after I left it connected to a Windows Laptop, like I said before, error messages with 'UI has stopped working' and 'other stuff stopped working' started popping up in a whole sequence of error messages so it rendered the phone unusable.
Next I started messing with it via platform-tools and wanted to flash TWRP on it and eventually a different OS like Lineage, but now the phone is totally shot and I can not use recovery any longer. The only thing that seems to work is fastboot mode, but it doesn't let me install a custom recovery like TWRP. Unlocking the bootloader seems to work, like shown in the attached pix, but other commands like 'fastboot devices' give a funny looking device name: '0123456789abcdef'. Other commands like fastboot erase -w and oem info show failure only; reboot-bootloader works and so on.
Any advice on this one? I'm just trying to learn about phones and android and this seems like a perfect opportunity, unless this cloned smartphone is piece of a worthless brick, which most assuredly is.
Try to flash corect stock firmwares for your device , check which one is yours .
https://hellostockrom.com/huawei-clone-p20-pro/
Yo TeddyLo, I tried already a similar website and after 2 hours of downloading through a slow internet connection the files were encrypted WinRaRs and probably useless anyway...thanks bro.
Hard Bricked Hoot P20 pro Clone
Yo, Teddy Lo, I had been busy last few days and tried to follow your suggestion, but to no avail. The device is now a hard brick, it does not come on at all, no more fastboot mode, or battery status logo when off and loading for that matter. It all happened when I tried to flash this file 'DOOGEE-Shoot_2-Android7.0--20170517' with SP Flash Tool. The device downloaded the files, but is completely dead now.
I am trying to do format and download with different ROMs for whatever is available on the internet for a P20 Pro clone phone, and phone manages to establish connection through USB with SP Flash Tool, but every time I get the following error message:
How can I fix this problem? Thanks.
Clone_Cat said:
Yo, Teddy Lo, I had been busy last few days and tried to follow your suggestion, but to no avail. The device is now a hard brick, it does not come on at all, no more fastboot mode, or battery status logo when off and loading for that matter. It all happened when I tried to flash this file 'DOOGEE-Shoot_2-Android7.0--20170517' with SP Flash Tool. The device downloaded the files, but is completely dead now.
I am trying to do format and download with different ROMs for whatever is available on the internet for a P20 Pro clone phone, and phone manages to establish connection through USB with SP Flash Tool, but every time I get the following error message:
How can I fix this problem? Thanks.
Click to expand...
Click to collapse
hi, i had the same problem, and i found this forum , it solved the issue ....
forum.gsmhosting.com/vbb/f296/clone-welcome-huawei-p20-pro-firmware-2574709/
Regards
I was trying to flash an MIUI ROM to my phone, so
here is what I have done:
- unlocker the bootloader.
- install the recovery.
- flashed the ROM.
- reboot the device.
after I finished all the above steps my phone have stuck in the boot loop, so the obvious solution for me was to reinstall the stock ROM so I have done that by:
- download MIFlash.
- download stock ROM.
- unzip the ROM.
- then I flashed the ROM.
the flashing process took longer than usual, so i have unplugged my phone and tried to reboot it, then the phone doesn't work, even the screen not working, the only sign that the phone is working is when I plug it in my computer I see MIFlash recognize it as COM20 port.
anyone helps me please.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kannanhassouna said:
I was trying to flash an MIUI ROM to my phone, so
here is what I have done:
- unlocker the bootloader.
- install the recovery.
- flashed the ROM.
- reboot the device.
after I finished all the above steps my phone have stuck in the boot loop, so the obvious solution for me was to reinstall the stock ROM so I have done that by:
- download MIFlash.
- download stock ROM.
- unzip the ROM.
- then I flashed the ROM.
the flashing process took longer than usual, so i have unplugged my phone and tried to reboot it, then the phone doesn't work, even the screen not working, the only sign that the phone is working is when I plug it in my computer I see MIFlash recognize it as COM20 port.
anyone helps me please.
View attachment 5265971
Click to expand...
Click to collapse
Please tell us which versions you have tried to install. It may be that you will try to install Android 10 and you were already with Android 11.
In that case it may be that the phone has been bricked. You can check how to reset it in this other post https://forum.xda-developers.com/t/this-way-i-unbrick-mi-a3-no-qfil.4231465/
In that case it may be that the phone has been bricked. You can check how to reset it in this other post https://forum.xda-developers.com/t/this-way-i-unbrick-mi-a3-no-qfil.4231465/
more detail....
what version of android has your phone? the root process was succesfully? what version of miui try to install? stock miui? port miui? miui for android 10? android 11? modding mi a3 require a lot of attention.... and install miui is not a good idea.... if fastboot mode work, try to install stock firmware via fastboot ... mi a3 have android one, is different from miui. probably you used a guide for install custom rom on miui device
Greeting,
I ask good people for help, more than a month trying to revive my a3.
It’s a child’s cell phone so I don’t know if update 11 worked so it blocked or the display went off disinfectants.
I made a repair according to "We A3 UNBRİCK Solution After Update Android 11! For FREE exclusive 2021!
, everything went without a hitch.
The current situation is that the phone works if the call if I put the sim card, it normally charges, the display is black and there is no response on the display, if there is one I can't see.
If someone has a suggestion of what to do, how can I know which Android is on it now, how can I know if maybe the display itself is broken.
Thank You in advance.
I don't saw the video but the solution is: download and install miflash tool. Connect your phone to pc in edl mode with a normal usb cable Flash a11 fastboot stock firmware. That's all
My tablet Lenovo tab 2 a10-70L crashed during an automatic update and since then it keeps returning to recovery. Any attempt to upload recovery e.g. via sp flash tool results in returning to the above mentioned screen. Although the whole process is theoretically successful. I tried uploading different versions of software and theoretically it ends successfully. However, the tablet returns to the recovery mode all the time. The bootloader mode works but I don't know if there is any easy way to use it by uploading some modified software. Please give me your suggestions.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Last year I tried to fix a neighbours lenovo, forget the model, but I'm sure I wrote of it here.
She took an update at the beginning of december last year that crashed like this.
Downside in my case was I could do what you could.
I tried everything to get back in, and it was this bad. Lenovo had locked the device completely, no adb, no fastboot, could not obtain edl flashtools for that device, because it had failed in the update, held on their server!!
I did the reset, loaded up some lenovo firmware updater in pc, it flashed online, but would not complete the flash because it required the neighbours login. So she says she's forgot it, (old woman that used to change my nappies lol ) and told me to keep it, she bought another.
So I come home and try again. In the end, they had lowered the battery power output to just the right amount to prevent any update running until the login was provided.
Spares or repares lol...
Goto Lenovo site, look for the live updater software for your pc, and plug in the tablet, see if that gets you back in. you will need to use previous login.
Lenovo's Google Home Devices Have Been Bricking For Months Now
Lenovo’s Google Home devices have been affected by a serious software issue that has been bricking them left and right. This issue started occurring
www.androidheadlines.com
Edit: Last year they were banned in at least three country's from operating due to this update hitting so many people.
The update was forced two weeks before christmas hint hint...
This is not a freezing screen problem. This tablet sat in the box for quite a long time. After taking it out of the box connecting it to a wi-fi network and booting it up an update to android Lollipop appeared. I allowed this update and everything went fine. After restarting it turned out that the system detected another update, this time to Marshmallow. So I also allowed this update. The tablet rebooted and began this update. During this update, an android icon with an open belly and an exclamation mark symbol appeared. At this screen the installation crashed and I simply restarted the tablet after three hours. Since then it has been stubbornly returning to recovery. The tablet has not been updated or rooted before. The whole problem occurred during an automatic update.
szybki10 said:
This is not a freezing screen problem. This tablet sat in the box for quite a long time. After taking it out of the box connecting it to a wi-fi network and booting it up an update to android Lollipop appeared. I allowed this update and everything went fine. After restarting it turned out that the system detected another update, this time to Marshmallow. So I also allowed this update. The tablet rebooted and began this update. During this update, an android icon with an open belly and an exclamation mark symbol appeared. At this screen the installation crashed and I simply restarted the tablet after three hours. Since then it has been stubbornly returning to recovery. The tablet has not been updated or rooted before. The whole problem occurred during an automatic
Click to expand...
Click to collapse
szybki10 said:
This is not a freezing screen problem. This tablet sat in the box for quite a long time. After taking it out of the box connecting it to a wi-fi network and booting it up an update to android Lollipop appeared. I allowed this update and everything went fine. After restarting it turned out that the system detected another update, this time to Marshmallow. So I also allowed this update. The tablet rebooted and began this update. During this update, an android icon with an open belly and an exclamation mark symbol appeared. At this screen the installation crashed and I simply restarted the tablet after three hours. Since then it has been stubbornly returning to recovery. The tablet has not been updated or rooted before. The whole problem occurred during an automatic update.
Click to expand...
Click to collapse
I also got same issue did u get any solution?