Stratos Bricked... - Amazfit

Hi Everybody !!
I was under StartosFied,
I wanted to go back to the official Rom.
Well, now the watch is bricked ... ?
It stays on the boot but nothing more. It is well recognized in adb but I can not do anything more ...
Exec / system / bin / sh FAILED ...
Basically more way to run internal commands to the watch and suddenly not possible to fastboot ...
Recognized by the device manager but does not mount in storage ...
Help....

https://mega.nz/#!7Zt3yYCC!j5h00vjZWIcgRz8w4uxkzeJpuR5gsR6STzkcqVOtKos
put your watch into fastboot and run with the bat installer.

kiija- please help
not working for me.. what should I do?
**************************************************
sdcard based system flash restore - Stratos ONLY
**************************************************
downloading 'boot.img'...
OKAY [ 0.452s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.330s
Waiting for 0 seconds, press CTRL+C to quit ...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully
adb: error: failed to get feature set: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
---------- Post added at 10:28 AM ---------- Previous post was at 10:16 AM ----------
1immortal - can you please help me out ?

I am facing the same situation.
Today my Stratos suddenly turned off didn't turn on again getting stuck on boot logo.
After a lot of trials i got reflash firmware but still stucked on logo.
---------- Post added at 11:50 PM ---------- Previous post was at 11:40 PM ----------
1immortal said:
https://mega.nz/#!7Zt3yYCC!j5h00vjZWIcgRz8w4uxkzeJpuR5gsR6STzkcqVOtKos
put your watch into fastboot and run with the bat installer.
Click to expand...
Click to collapse
I tried this (up)
And got the same (down)
Any help?
avinashkalro said:
kiija- please help
not working for me.. what should I do?
**************************************************
sdcard based system flash restore - Stratos ONLY
**************************************************
downloading 'boot.img'...
OKAY [ 0.452s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.330s
Waiting for 0 seconds, press CTRL+C to quit ...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully
adb: error: failed to get feature set: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
---------- Post added at 10:28 AM ---------- Previous post was at 10:16 AM ----------
1immortal - can you please help me out ?
Click to expand...
Click to collapse

Related

HELP - Cannot Flash Custom Recovery - ERROR: usb_read failed with status e00002e8

My phone is rooted and unlocked. I have installed adb and fastboot. I had twrp installed and I used it to install a custom rom. Then, I accidentally flashed something (maybe update.zip?) that not only changed the regular system partition, but also the recovery partition. I've been trying to get twrp back and I'm having major issues.
When I try the command "fastboot erase recovery" I receive the following error message:
erasing 'recovery'...
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (Invalid argument))
finished. total time: 0.005s
I've searched google with several different parameters and nothing is helping me, so I figure best to post my own question. I get the same error and status e00002e8 when trying to flash recovery.img or boot.img

[Solved]Fastboot flash recovery stuck on sending

Hello everybody,
I own a Lenovo k5 pro phone (L38041).
I've unlocked bootloader yesterday with this method, then I flashed via twrp zui 11 with android pie, prerequisite to install havoc 2.9. That overwrited twrp with stock recovery, so I tried to flash twrp again via fastboot but it got stuck sending.
See here, when prompted «FAILED (Status read failed (No such device))» is because I reboot phone bootloader after a long wait sending.
Code:
$ adb version
Android Debug Bridge version 1.0.41
Version 29.0.4-1
Installed as /usr/bin/adb
$ fastboot --version
fastboot version 29.0.4-1
Installed as /usr/bin/fastboot
$ fastboot devices
4488d6fc fastboot
$ fastboot flash recovery recovery-TWRP-3.2.3-0225-LENOVO_K5PRO-CN-wzsx150.img
Sending 'recovery' (55144 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot -w
Finished. Total time: 0.002s
$ fastboot flash recovery recovery-TWRP-3.2.3-0225-LENOVO_K5PRO-CN-wzsx150.img
Sending 'recovery' (55144 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed
$ fastboot -w
Erasing 'userdata' FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot flash recovery recovery-TWRP-3.2.3-0225-LENOVO_K5PRO-CN-wzsx150.img
Sending 'recovery' (55144 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed
$ fastboot -w
Erasing 'userdata' FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot -w
Finished. Total time: 0.002s
$ fastboot -w
Erasing 'cache' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
$ fastboot getvar all
getvar:all FAILED (remote: 'unknown command')
Finished. Total time: 0.001s
$ fastboot getvar all
getvar:all FAILED (remote: 'GetVar Variable Not found')
Finished. Total time: 0.001s
$ fastboot getvar all
getvar:all FAILED (remote: 'GetVar Variable Not found')
Finished. Total time: 0.001s
$ fastboot -w
Finished. Total time: 0.001s
$ fastboot flash unlock sn.img
Sending 'unlock' (8 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed
$ fastboot -w
Erasing 'userdata' FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot -w
Finished. Total time: 0.001s
Bootloader info:
Fastboot mode (secure)
Product: kunlun
Variant: SDM EMMC
SN: 4488d6fc
Device state: unlocked
In develorper options it shows as unlocked too.
Last thing, I've pushed some files via adb while system is on, (debugging mode on).
Thank you.
Today I've updated adb and fastboot to 29.0.4-2 with same result.
Some other commands I've tried (notice it fails when I restart fastboot at device some time after wait):
Code:
$ fastboot devices
4488d6fc fastboot
$ fastboot boot recovery-TWRP-3.2.3-0225-LENOVO_K5PRO-CN-wzsx150.img
Sending 'boot.img' (55141 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed
$ fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot oem lock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Any help?
I'ts solved.
I've used different computer and different cable, it was as easy.

The system has been destroyed - Pocophone F1

Hi Guys!
So I got a phone from a friend to assist him with a problem.
When I opening the phone, the phone showing an error message "The system has been destroyed".
I tried to use Fastboot but when I running any command an error message received, for example:
Example1:
fastboot flash recovery "twrp-3.3.0-0-beryllium (1).img"
Sending 'recovery' (31068 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Example2:
fastboot devices -l
???????????? fastboot
Example 3:
fastboot flashing unlock
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
fastboot oem device-info -v
< waiting for any device >
FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
Any ideas??
Please help!
Thanks!

Nokia 2.1 bootloader unlock issues

Hi I'm trying to unlock the bootloader on my Nokia 2.1 but I'm having issues. When I issue the command "fastboot oem dm-verity 8131ad00718c028b21431808b0b6f2c3"
I get this error
"FAILED (remote: 'unknown command') fastboot: error: Command failed"
Please post in the proper section i have moved your post
IAmTheYikes said:
Hi I'm trying to unlock the bootloader on my Nokia 2.1 but I'm having issues. When I issue the command "fastboot oem dm-verity 8131ad00718c028b21431808b0b6f2c3"
I get this error
"FAILED (remote: 'unknown command') fastboot: error: Command failed"
Click to expand...
Click to collapse
Obviously fastboot driver not installed on PC
DL: https://nokia-connectivity-usb-driver.en.lo4d.com/windows

adb fastboot command failed

Erasing 'system' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'system_ext' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'odm' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'product' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Can someone help? i downloaded the new adb drivers, adb is updated. bootloader is unlocked.
1.
ADB and Fastboot are different drivers that serve different purpose
2.
How Fastboot commands are implemented depends on manufacturer. In any case download and install the "Android USB Driver" suitable to your Android device.
jwoegerbauer said:
1.
ADB and Fastboot are different drivers that serve different purpose
2.
How Fastboot commands are implemented depends on manufacturer. In any case download and install the "Android USB Driver" suitable to your Android device.
Click to expand...
Click to collapse
The thing is fastboot works for other things but when I try to flash this from which formats it, it fails on erasing system and the other images. I've always used the adb 15 second installer on xda.
I'm pretty sure the Fastboot you've installed is for Google devices. If your device isn't a Google one then install, as by me suggested earlier, the driver provided by your device's manufacturer.

Categories

Resources