Amazfit 2S - Chinese to English - Amazfit

I have bought a Chinese version of Amazfit 2S. Unfortunately there is no possibility to change the language from the menu.
I have tried the procedure as mentioned here:
https://nicolasagliano.com/lo-sblocco-del-bootloader-e-arrivato/
But it is not possible to complete the procedure with ADB commands mentioned in the procedure.
Can someone help with instructions for a layman to convert from Chinese to English?
I have tried this several times and it always get stuck with the last command.
************************
C:\Users\kcv269\Desktop>adb devices
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
9a402c2f device
C:\Users\kcv269\Desktop>ADB shell reboot bootloader
C:\Users\kcv269\Desktop>fastboot devices
C:\Users\kcv269\Desktop>fastboot reboot
< waiting for device >
When I restart CMD
********************************
C:\Users\kcv269\Desktop>adb shell reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
C:\Users\kcv269\Desktop>fastboot getvar all
< waiting for device >
I cannot get forward from here.

Are there no solution to this problem?
C:\Users\kcv269\Desktop>fastboot getvar all
< waiting for device >
Here my watch get stuck and there is no response from it

Related

[Q] [q] this adb not working is driving me insane!!! H=e=l=p!!!

this has been a problem after problem situation the whole way through trying to knock my HTC one out of this softbrick state it is currently trapped in.
long story short. currently at point where trying to sideload rom to phone... past flashing twrp.img... and if its not one error its the next.
1) adb will refuse to start.. it will just stick on:
C:\adb>adb start-server
* daemon not running. starting it now on port 5037
2) C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
3) last error type, everything will be running smoothly then as after the 'adb sideload ROM.zip' or should it be this,'adb sideload Desktop/ROM.zip' dont know but it shoots back "error: closed"
FIX THIS PLEASEEEEEEEEEEEE!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[q] adb issue, need help

Hi friends ,
I just cannot get rid of the issue with the 8 things I tried (see below). I need your help pls, it has taken me alot of time and still unsolve.
I am running on window7, 64bits. I am building the "hello world" program and follow the instruction from Andriod developer website. At first, everything went well including the installation. I even manage to run the program on my Samsung S5. However, in a while, I notice something is wrong after I edited the code, so I delete and re-install the SDK and ADT package, objective is to bring the code back to the same factory state. I had tried installing both version of 32bits and 64bits Eclipse package but encounter the following problem when i click RUN as Android application:
******************** Return the following txt: ************************
The connection to adb is down, and a severe error has occured.
You must restart adb and Eclipse.
Please ensure that adb is correctly located at 'D:\ADT\sdk\platform-tools\adb.exe' and can be executed.
**********************************************************************
I did the following troubleshooting:
1) Restart the computer and my phone (samsung S5)
2) Check that there is a connection icon on my PC (USB connected between phone and PC)
3) Update adb in the SDK using the SDK manager
4) Make sure i go to the "help-->Install new software" in the Eclipse and key in the dl-ssl weblink every time i re-install the Elipsce package.
5) Make sure I click "help-->check for update" in the Eclipse every time i re-install the Elipsce package.
6) Checked that I am the adminstrator of my PC
7) Run command at command prompt. I did the follwoing steps:
a. Close the Eclipse if running
b. Go to the Android SDK platform-tools directory in Command Prompt
c. type adb kill-server
************************* Return the following txt ************************
* server not running *
--> adb server is out of date. killing...
ADB server didn't ACK
* fail to start daemon *
**********************************************************************
d.then type adb start-server
Return the same txt as above.
8) I suspect some other process is occupying the port 5037 which the adb access. So I attempt to find the PID (process id) of the process which occupied the port 5037 by giving the command "D:\Android\sdk\platform-tools>netstat -aon|findstr 5037"
************************ Return the following txt *****************************
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 3640
TCP 127.0.0.1:5037 127.0.0.1:50506 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50507 TIME_WAIT 0
**********************************************************************
Then I go to PC Task Manager, but there is no PID with 3640.
I also type at command prompt the below:
tasklist /fi "pid eq m3640
************************* Return the following txt ************************
No task are running which match the specified criteria
**********************************************************************
Seems that the adb is not responding to any re-installation, or restarting of PC and device. The task manager shows PID 3640 but couldn't see any process related to it.
I am a electronics engineer and much a novice in this field of computer.
pls help

Linux Mint ADB sees my phone as 'offline' & how to 'untrust' computer

After connecting the phone via usb cable, "adb devices" command lists :
$ adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
FA3BSWG00401 offline
1) First time it asked whether to trust this computer and I checked 'always trust this computer'. Is there a way to untrust a specific computer / make it ask again ?
2) plugging the cable to my older SGS3 works fine :
$ adb devices
List of devices attached
4df1d4650790afdf device
Has anybody encountered this before ?
Additional info :
$ adb version
Android Debug Bridge version 1.0.32
Revision 57224c5cff69-android
I'm using Linux Mint 17.2, NuSense 6 (Lolipop)

How to exit FastBoot mode ( not successful process)

I'm try to Unlock my Amazfit stratos
my step
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
3a15090d device
C:\adb>adb shell reboot bootloader
C:\adb>fastboot getvar serialno
< waiting for device >
Click to expand...
Click to collapse
But after that It's not return any parameter. I'm wait along time 20-30 mins.
my stratos still show in Fastboot mode.
I'm try to open new command promt to reboot it. but it's not found devices
c:\adb>adb devices
List of devices attached
:crying:
How to exit. comeback to normal mode. please help me
just press the upper button until the watch will restart itself
1immortal said:
just press the upper button until the watch will restart itself
Click to expand...
Click to collapse
thank you. It's come back :victory:
Next how to Unlock process.
because I'm already use this adb driver from https://forum.xda-developers.com/showthread.php?t=2588979
I'm try both version 1.4.2 and 1.3
But same result at step;
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
3a15090d device
C:\adb>adb shell reboot bootloader
C:\adb>fastboot getvar all
Click to expand...
Click to collapse
But still show" < waiting for device >"

Using `adb pair` on Adroid 10- devices

From starting Android 11 we can use ADB wirelessly by pairing the device wirelessly using,
Code:
adb pair ipaddr:port
When I try the same in an Android 10- device,
Code:
./adb pair 192.168.8.120:5555
Code:
Enter pairing code: 123456
adb server version (39) doesn't match this client (41); killing...
* daemon started successfully
Failed: Unable to start pairing client.
The problem seems that a pairing code cannot be provided by the device. I think if we could have a method (hack) to provide a pairing code from the device, we could succeed.
Have anyone tried to do it on Android 10- ?
Isn't that possible at all?
Code:
adb pair
only available on Android 11 and up.
Look inside here.

Categories

Resources