Hello, I need help with an amazfit beep, when updating in IOS to the latest version the clock was on screen a message that said "connect app to update resources".
Then I linked the clock to an android and using gadgetbridge install the res 9.40 and then the fw 9.26 then in this last step the clock did not end and it was turned off. Now I can not turn it on or in the charging base.
Help
Nadie te va a responder en este foro ya que solo se habla inglés, edita tu respuesta o escribela en otros foros como HTCMania
Anyone won't respond you because this is an English forum, edit your response or write it on another forum like HTCMania
Related
Tuve un problema hace poco con mi vibrant que me me tuvieron que dar otro remfacturado...ahora estoy intentando con el Kies mini de darle un upgrade a froyo 2.2 y esto es lo q me sale ( FAILED TO CONNECT TO THE MODEL INFORMATION SERVER) y no puedo darle upgrade....mas a parte de eso como no puedo darle upgrade pues intente darle un root el celular y tampoco me deja llegar al area de root que dejando los tres botones pegados, mas intente tambien por via odin y no puedo abrir el area de Downloading ayuda por favor....yo se que esta en espanol pero no se ingles y mas si uso google para esto no me va a traducir bien gracias y disculpen...
MOD EDIT: Please translate your post to English.
4. Use the English language.
We understand that with all the different nationalities not everyone speaks English well, but please try. If you're really unable to post in English use an online translator, You're free to include your original message in your own language below the English translation.
Click to expand...
Click to collapse
GOOGLE TRANSLATOR TO THE RESCUE!
WHAT HE'S SAYING:
"I had a problem recently with my vibrant that I had to give me another remfacturado ... now I'm trying to give Kies mini Froyo upgrade to 2.2 and this is what I get q (FAILED TO CONNECT TO THE SERVER INFORMATION MODEL) I can not give more to upgrade .... as part of that upgrade I can not give it a try to give the cell root, nor let me get to the root area, leaving the three buttons that stuck, but also try and not by way odin I can open the Downloading area help please .... I know it is in Spanish but not English and over if I use google for this is not going to translate well thanks and sorry ..."
Answer:
If i understand correctly, your power button and volume buttons DO NOT WORK?
If they don't work and your trying to enter download mode, you'll need to buy your self a JIG or make one your self. theres info in this video sorry idk about a spanish video:
http://www.youtube.com/watch?v=2hBUOPh_9mI&feature=channel_video_title
Thats the only solution that i know.
Translated my answer to spanish:
Si he entendido bien, los botones botón de encendido y volumen NO FUNCIONA?
Si no funcionan y su tratando de entrar en modo de descarga, tendrás que comprar su auto una plantilla o hacer su uno mismo. theres de la ciudad en este video IDK lo de un video en español:
http://www.youtube.com/watch?v=2hBUOPh_9mI&feature=channel_video_title
Esa es la única solución que conozco.
Just a polite reminder to all. Please remember to translate your post to English as per the forum rules.
Thanks.
ok gracias ya entendi.....siguiendo con el tema, por que me sale ese mensaje en Kies mini que debo hacer....
ok ..... thanks and understanding along with the topic, that I get this message that I do Kies mini ....
I'm sorry i don't know about the KIES problem, maybe someone else can help.
Lo siento, no sé sobre el problema Kies, tal vez alguien más puede ayudar.
English (Google Translator): Hi, Sorry but first of all. Do not speak English. : ( But I need the help of this great community of developers.
My problem is this, I have an Optimus One P500, brought android originally wanted to upgrade to 2.2.1 and 2.3.3. Check all the options of the forum and I decided to root using the method GingerBreak the rooteo runs without any apparent error, but to my surprise when you restart your phone is Emergency Mode (yellow screen), I thought instantly that I had bricked, remove the battery and left it like 10min, then place it back and turned on the computer, strangely lit correctly, did not show emergency mode. Again I thought it had already been solved, but when
you turn off the computer again returned to the screen yellow emergency mode, the strange thing is that by removing the battery 10min and starts back up if the right way.
But because it's annoying that every time you turn it off need to do
this (remove the battery and such) because I decided to follow the methods desbrickeo who are here in the forum, flashing a ROM format 2.3.3. Kdz smoothly , then do factory reset (wipe) the data necessary to eliminate the previous ROM and the phone lit correctly, but off and on again to find the screen yellow emergency mode again, no change, wait 10 minutes and starts normally.
The situation is tired and annoyed me, so I turn to you, help you regain normal operation.
Any suggestions or help will be welcome, please do not delete the post because it is in Spanish which really NOT write or speak English.
Best regards.
Buenas, primero que nada DISCULPAS pero. DON'T speak english.
Sin embargo estoy necesitando la ayuda de esta gran comunidad de desarrolladores.
Mi problema es el siguiente, tengo un Optimus One P500, originalmente traia android 2.2.1 y queria actualizarlo a 2.3.3. Revise todas las opciones del foro y me decidi a rootear usando el metodo GingerBreak, el rooteo se ejecuto sin ningun error aparente, pero para mi sorpresa cuando reinicie el telefono quedo en MODO EMERGENCIA (pantalla amarilla), pense instantaneamente que lo habia brickeado, quite la bateria y lo deje asi como 10min, luego la coloque de nuevo y encendi el equipo, cosa rara encendio de manera correcta, NO mostro el modo emergencia.
De nuevo pense que ya se habia solucionado, pero al apagar de nuevo el equipo volvio a mostrar la pantalla amarilla en modo emergencia, lo raro es que quitando la bateria 10min y volviendolo a encender SI arranca de manera correcta.
Pero debido a que es MOLESTO que cada vez que lo apague deba hacer esto (quitar la bateria y tal) pues me decidi a seguir los metodos de desbrickeo que estan aqui en el foro, flashee una ROM 2.3.3 en formato .kdz sin inconvenientes, luego realice el reseteo de fabrica (wipe) necesario para eliminar los datos de la ROM anterior y el telefono encendio de manera correcta, pero nuevamente al apagarlo y encenderlo encontre la pantalla amarilla del modo emergencia de nuevo, sin cambios, espere 10min e inicia normalmente.
La situacion me tiene cansado y molesto, por eso acudo a ustedes, ayudenme a recuperar el funcionamiento NORMAL del equipo.
Cualquier sugerencia o ayuda sera MUY bien recibida, por favor no borren el post por estar en español que de verdad NO se escribir ni hablar ingles.
Saludos cordiales.
Forum rules
Speak English, or use Google Translate.
Google Translate :
Hi, Sorry but first of all. Do not speak English.
But I need the help of this great community of developers.
My problem is this, I have an Optimus One P500, brought android originally wanted to upgrade to 2.2.1 and 2.3.3. Check all the options of the forum and I decided to root using the method GingerBreak the rooteo runs without any apparent error, but to my surprise when you restart your phone is Emergency Mode (yellow screen), I thought instantly that I had bricked, remove the battery and left it like 10min, then place it back and turned on the computer, strangely lit correctly, did not show emergency mode.
Again I thought it had already been solved, but when you turn off the computer again returned to the screen yellow emergency mode, the strange thing is that by removing the battery 10min and starts back up if the right way.
But because it's annoying that every time you turn it off need to do this (remove the battery and such) because I decided to follow the methods desbrickeo who are here in the forum, flashing a ROM format 2.3.3. Kdz smoothly , then do factory reset (wipe) the data necessary to eliminate the previous ROM and the phone lit correctly, but off and on again to find the screen yellow emergency mode again, no change, wait 10 minutes and starts normally.
The situation is tired and annoyed me, so I turn to you, help you regain normal operation.
Any suggestions or help will be welcome, please do not delete the post because it is in Spanish which really NOT write or speak English.
Best regards.
Edit. Google Translator Post. Sorry. :S
try installing custom recovery?
Thundeg or ClockworkMod (from Rom Manager)? I already had installed from ROM ClockworkMod rootee manager when using GingerBreak, but the problem persisted, trying to thunderg? now I have the ROM 2.3.3 (Romanian) flashed as I said from kdz.
i think u have some problem in hardware....
make sure your phone dont have custom recovery and not rooted
go to lg service center.
juanitomigraña said:
English (Google Translator): Hi, Sorry but first of all. Do not speak English. : ( But I need the help of this great community of developers.
My problem is this, I have an Optimus One P500, brought android originally wanted to upgrade to 2.2.1 and 2.3.3. Check all the options of the forum and I decided to root using the method GingerBreak the rooteo runs without any apparent error, but to my surprise when you restart your phone is Emergency Mode (yellow screen), I thought instantly that I had bricked, remove the battery and left it like 10min, then place it back and turned on the computer, strangely lit correctly, did not show emergency mode. Again I thought it had already been solved, but when
you turn off the computer again returned to the screen yellow emergency mode, the strange thing is that by removing the battery 10min and starts back up if the right way.
But because it's annoying that every time you turn it off need to do
this (remove the battery and such) because I decided to follow the methods desbrickeo who are here in the forum, flashing a ROM format 2.3.3. Kdz smoothly , then do factory reset (wipe) the data necessary to eliminate the previous ROM and the phone lit correctly, but off and on again to find the screen yellow emergency mode again, no change, wait 10 minutes and starts normally.
The situation is tired and annoyed me, so I turn to you, help you regain normal operation.
Any suggestions or help will be welcome, please do not delete the post because it is in Spanish which really NOT write or speak English.
Best regards.
Buenas, primero que nada DISCULPAS pero. DON'T speak english.
Sin embargo estoy necesitando la ayuda de esta gran comunidad de desarrolladores.
Mi problema es el siguiente, tengo un Optimus One P500, originalmente traia android 2.2.1 y queria actualizarlo a 2.3.3. Revise todas las opciones del foro y me decidi a rootear usando el metodo GingerBreak, el rooteo se ejecuto sin ningun error aparente, pero para mi sorpresa cuando reinicie el telefono quedo en MODO EMERGENCIA (pantalla amarilla), pense instantaneamente que lo habia brickeado, quite la bateria y lo deje asi como 10min, luego la coloque de nuevo y encendi el equipo, cosa rara encendio de manera correcta, NO mostro el modo emergencia.
De nuevo pense que ya se habia solucionado, pero al apagar de nuevo el equipo volvio a mostrar la pantalla amarilla en modo emergencia, lo raro es que quitando la bateria 10min y volviendolo a encender SI arranca de manera correcta.
Pero debido a que es MOLESTO que cada vez que lo apague deba hacer esto (quitar la bateria y tal) pues me decidi a seguir los metodos de desbrickeo que estan aqui en el foro, flashee una ROM 2.3.3 en formato .kdz sin inconvenientes, luego realice el reseteo de fabrica (wipe) necesario para eliminar los datos de la ROM anterior y el telefono encendio de manera correcta, pero nuevamente al apagarlo y encenderlo encontre la pantalla amarilla del modo emergencia de nuevo, sin cambios, espere 10min e inicia normalmente.
La situacion me tiene cansado y molesto, por eso acudo a ustedes, ayudenme a recuperar el funcionamiento NORMAL del equipo.
Cualquier sugerencia o ayuda sera MUY bien recibida, por favor no borren el post por estar en español que de verdad NO se escribir ni hablar ingles.
Saludos cordiales.
Click to expand...
Click to collapse
Hi ,writing in simple English as possible for you to understand ..
I had/have this same problem ..meaning the phone when restarted would go into emergency mode ..like always after it being earlier connected to pc.
well after doing all sorts of bells and whistles ,I found out that the culprit is sd-card due to improper partitioning etc.. and just replacing the sd-card solves this highly irritating problem .. Hope this helps ya !
Thanks for your answers. The solution to bring it to technical service is the one used, I have flashed from "kdz" the official ROM from my operator, without root and no custom recovery. Tomorrow I'm taking, how sad is having these problems with a team of good behavior like this. A greeting.
Hi all,excuse my English but I'm from Argentina and not write well in this language,so use the google translator. Q Since last year I am a member of this site,I am looking for a q update.zip opcione me of taking pictures with the volume button using the stock cam. If anyone knows or has one appreciate it. Thx
Greetings
Te hablo en criollo así no careteo que se inglés (porque no se xD)
Fíjate si eso te sirve http://forum.xda-developers.com/showthread.php?t=853989
Ahí linkean a otro thread de una app para remapear los botones del celu. No es un zip pero capas te sirve
Tetas naturales > Tetas hechas
Sorry my bad english
Puse la STOCKfied_1.3.5_Multilenguaje, y luego reloj reset y cuando voy hacer una actividad me dice que gps bien, me sale el contador 3,2,1 y luego error.
Unfortunately, gpx-recorder has stopped.
¿De que puede ser?
Gracias
Unfortunately, I can not help. I'm just saying the language of the forum is English.
Solved
I have installed SCRIPT FLASH AMAZFIT A1602 & A1612 AND FIX UPDATE 1.3. 1n, I paired the clock then install via OTA Original 1.3.5 update, then I desemparejo the clock with the phone and install Instalador_v1.2_STOCKfied_1.3.5_Multilenguaje and without matching MODs_ & _ TWEAKs_v1.1.
And after installing paired clock and everything perfect.
Luck.
CIBERCHININ said:
I have installed SCRIPT FLASH AMAZFIT A1602 & A1612 AND FIX UPDATE 1.3. 1n, I paired the clock then install via OTA Original 1.3.5 update, then I desemparejo the clock with the phone and install Instalador_v1.2_STOCKfied_1.3.5_Multilenguaje and without matching MODs_ & _ TWEAKs_v1.1.
And after installing paired clock and everything perfect.
Luck.
Click to expand...
Click to collapse
Cuando tengas problemas con alguna Rom, mejor que escribas en el hilo de la propia Rom, y si no dominas el inglés mejor pásate por aquí: http://www.htcmania.com/forumdisplay.php?f=2281
If you have an issue with any Rom, just post on its thread, or even better if you don't speak English to check this: http://www.htcmania.com/forumdisplay.php?f=2281
Hey all
Today in the morning watch showed 9% on battery and I placed it to charge and after an 1 hour I came back to check and it was showing Amazfit logo, the one when you boot the device but logo stays forever. If I hold red button to reset it reloads and starts by itself. Also there is no way to turn it off.
Everything was working fine in the morning before the charge and all other days.
Maybe someone has experienced same stuff. Watch is only 1 month old...
Mioleris said:
Hey all
Today in the morning watch showed 9% on battery and I placed it to charge and after an 1 hour I came back to check and it was showing Amazfit logo, the one when you boot the device but logo stays forever. If I hold red button to reset it reloads and starts by itself. Also there is no way to turn it off.
Everything was working fine in the morning before the charge and all other days.
Maybe someone has experienced same stuff. Watch is only 1 month old...
Click to expand...
Click to collapse
The same situation here. I have tried everything without success. I am thinking that next version of zeep maybe automatically fix the issue.
Mam to samo. W nocy obudził bootloop. Nic nie pomaga.
Same problem here pethatic amazfit support money wasted
Any help for gtr2 bootloop restarting problem any hope help please
How to go in Fastboot mode gtr2 any guy answer please
Hey, I have a GTR 2, and at first I thought that the bootloop issue is software based. That can be easily fixed if you put the watch on the charger as it can finish loading even with a corrupted watchface installed.
In my case however, the watch only worked for a short time after I've put it in the freezer. That is a hardware issue. All that can be done is to get it replaced by the store that sold it to you, or in case that option is not available to you, you need to actually heat the board over 300C so that, hopefully, the bad connection is fixed (mobile repair shops can actually help with that).
As a test: put device in freezer, connect, reset, whatever, then shutdown the watch.
Wait for the watch to reach room temperature (non working state). If it's a hardware bootloop, the watch will not react to any buttons, will not show he charging animation, nothing. Basically black screen.
I also tried removing the battery for 10 seconds, holding any combination of buttons, charging states, screen presses, so simply don't waste time with that.
Every electronic equipment has a failure rate of 0-5%, we just happened to buy those 0 to 5% watches.
From what I understand, it is a design error and some contacts on the circuit board may not make contact...
The Amazfit GTR2 just doesn't work on the touch screen. I only used it for a week .... I restarted in vain, nothing.
Can anyone help me?
Good morning everyone
I wanted to share an experience with you. And the solution in the Amazfit GTR2 that was stuck in the logo
after I read the method of placing it in the freezer for a few minutes and that it really works for a few minutes
thing that and verified!
I came to deduce that it would be ??!!
It could be a violation of 183
well I proceeded to do a reflux since it still turns on I proceeded to use
125 degree heat
60 air
in a uniform way after saying the heat
turned on without problems
I hope it helps you
Buenas.. A todos
les quería compartir una experiencia. Y la solucion en la Amazfit GTR2 que quedaba pegada en el logo
despues que lei el metodo de colocarlo en el freezer por algunos minutos y que en verdad funciona por algunos minutos
cosa que e comprobado!!!
llegue a deducir que seria ??!!
Podría tratarse de una infracción de 183
bueno procegui en hacerle un reflujo ya que el mismo ahun prende procedi a usar
125 grados de calor
60 de aire
de una forma uniforme luego de decir el calor
encendió sin problemas
Espero les ayude
Ronaldvd said:
Good morning everyone
I wanted to share an experience with you. And the solution in the Amazfit GTR2 that was stuck in the logo
after I read the method of placing it in the freezer for a few minutes and that it really works for a few minutes
thing that and verified!
I came to deduce that it would be ??!!
It could be a violation of 183
well I proceeded to do a reflux since it still turns on I proceeded to use
125 degree heat
60 air
in a uniform way after saying the heat
turned on without problems
I hope it helps you
Buenas.. A todos
les quería compartir una experiencia. Y la solucion en la Amazfit GTR2 que quedaba pegada en el logo
despues que lei el metodo de colocarlo en el freezer por algunos minutos y que en verdad funciona por algunos minutos
cosa que e comprobado!!!
llegue a deducir que seria ??!!
Podría tratarse de una infracción de 183
bueno procegui en hacerle un reflujo ya que el mismo ahun prende procedi a usar
125 grados de calor
60 de aire
de una forma uniforme luego de decir el calor
encendió sin problemas
Espero les ayude
Click to expand...
Click to collapse
Hola! tengo el mismo problema, por cuanto tiempo le aplicaste el calor? le colocaste Flux si es así en que parte? no soy muy experto en esto pero quiero intentarlo.
Quedo atento. Saludos!.