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!.
Related
Traducido con google traductor: Tengo un gran problema, tengo un brick en mi celular, y estoy tratando de flashear, pero falla, y me di cuenta de porque, es que mi celular se descarga antes de que termine de flashear, por mas que llene la bateria al maximo y empiece el flasheo, se termina la bateria y se cancela el flasheo, de hecho no se si ya se daño mas de que esta, pero ahora no se que hacer, creo que aproximadamente tardara 12 horas, y el telefono solo resiste 5 horas, y no se si haiga una firmware muy liviano como para que se pueda instalar rapidamente, solo quiero que inicie el celular para poder usar el recovery e instalar minicm u otro... helpppppppppp
ENGLISH please !
Sent from my stunning x10mini !
[MINICM 1.0.2 with CWM]
(Any problem ? Feel free to contact me - [email protected] , +919033451101)
He bricked his phone, when he tries to flash the phone is out of battery before it's done so he can't finish the process.
He has charged the battery to the max but still can't do it. Says his battery lasts like 5 hours in the process and he thinks it's supposed to last like 12 hours so it's a lot of time.
tell him to unplug the power cable (i mean remove the battery) then charge again, the phone will be back soon
Ok sorry, im a fail:
Translated with google translator: I have a big problem, I have a brick in my cell and I'm trying to flash, but fails, and because I realized is that my cell is discharged before the end of Flash, and more than full the maximum battery and start flashing, the battery ends and cancels the flash, in fact if you are not hurt over this, but I do not know what to do, I think that about takes 12 hours, and phone only stand 5 hours, and do not know if a firmware haiga very light so that it can be installed quickly, I just want to start the cell to use the recovery and install minicm or other ... helpppppppppp
untime said:
tell him to unplug the power cable (i mean remove the battery) then charge again, the phone will be back soon
Click to expand...
Click to collapse
Desconecta el cable de poder (es el que va a la bateria en los minis, le quitas la tapa y hay una cosita que se remueve porque el mini la trae interna la bateria y con eso es como si la quitaras) y vuelvelo a cargar, el telefono va a estar de vuelta pronto.
De otro post que te pusieron agarre esto
jodhaniohm97 said:
Does the led of your phone flash the red colour three times? The red led flash three times because your phones battery is dead. So you plug in your phone with usb cable to the computer and let it remain for two or more hour (this means that you're charging your phone )During this time the phone would not turn on and you can do nothing with your phone during this time. You will only see the red led . After two hours of charging disconnect and run seus and Follow the onscreen instruction. I followed the above mentioned procedure and I got my mini back .
Click to expand...
Click to collapse
El led te tu telefono flashea 3 veces en color rojo? El flasheo triple del led rojo es porque la bateria del telefono esta muerta. Entonces conecta tu telefono con el cable usb a la computadora y dejalo ahi por 2 o mas horas (esto significa que estas cargando el telefono). Durante este tiempo el telefono no se va a prender ni vas a poder hacer nada con el. Solo vas a ver el led rojo.
Despues de dos horas de carga desconectalo y corre SEUR y sigue las instrucciones en la pantalla. Yo segui (el que te da el consejo) el procedimiento mencionado y recupere mi mini.
Creo que ya habias visto ese post, igual te lo puse por si acaso y por si la traduccion de google variaba un poco. Ojala se te arregle el mini, suerte.
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.
Help me please, I installed a stock rom in my Ace 4 Lite SM-G313ML and the battery of my cell phone got out of control, every time I reach 20.21 or 15 percent, the button is started to close the background apps And so it happens until the cell phone turns off completely, then if I take the battery and put it back and turn it on and I get out that it has 0% charge.
Already try all possible ways to solve it and nothing that succeeds, and changed rom, erased the batterystats.bin, and done many cycles full load and always comes out the same and before my battery was ok.
Ayudenme por favor, instalé una rom stock en mi Ace 4 Lite SM-G313ML y la bateria de mi celular se descontrolo, cada vez que mi llega al 20,21 o 15 porciento se comienza a tocar el boton para cerrar las apps de segundo plano y asi pasa hasta que el celular se apaga por completo, luego si le saco la bateria y pongo de nuevo y enciendo ya me sale que tiene 0% de carga.
Ya e probar todas las maneras posibles para solucionarlo y nada que lo logra, e cambiado de rom, borrado el batterystats.bin, e hecho muchos ciclos de carga completa y siempre sale lo mismo y antes mi bateria estaba bien.
Have you tried replacing battery?
¿Intentaste cambiando de batería>
Try charging the phone with USB cable it worked for me
ExillustX said:
Try charging the phone with USB cable it worked for me
Click to expand...
Click to collapse
Me pasa lo mismo ¿en verdad funciona?, ¿qué pasos debo seguir?
I'm in the same way, really work it?, how can I do?
I've had my Pixel 6 for a little over 3 weeks now and everything was working perfectly with it however, a few days ago (Friday) I opened up an app and the screen suddenly froze. Couldn't interact with anything and holding the power button didn't do anything. I rebooted into recovery by holding power + volume up however, my phone ended up repeatedly boot-looping and saying my "Android system was corrupt". I had to factory reset everything and go through the entire set up process again. I am very confused as I haven't rooted my phone or changed any aspect of it in that way, and my phone has always been on me so no one else had physical access to it.
Has this happened to anyone else?
Your forced shutdown may have resulted in a corrupt filesystem. Its rare, but happens. Or, the problem you were experiencing prior to forcing it down could have been hardware failure.
96carboard said:
Your forced shutdown may have resulted in a corrupt filesystem. Its rare, but happens. Or, the problem you were experiencing prior to forcing it down could have been hardware failure.
Click to expand...
Click to collapse
I'll keep that in mind and hopefully it doesn't occur again. Everything is running normally after the factory reset. Thankfully almost all of my data is backed up regularly.
AshenFire579 said:
He tenido mi Pixel 6 durante un poco más de 3 semanas y todo funcionaba perfectamente, sin embargo, hace unos días (viernes) abrí una aplicación y la pantalla se congeló repentinamente. No se pudo interactuar con nada y mantener presionado el botón de encendido no hizo nada. Reinicié en recuperación manteniendo arriba el encendido + volumen, sin embargo, mi teléfono terminó repetidamente en bucle de arranque y dijo que mi sistema Android estaba dañado. Tuve que restablecer todo de fábrica y volver a realizar todo el proceso de configuración. Estoy muy confundido porque no he rooteado mi teléfono ni he cambiado ningún aspecto de él de esa manera, y mi teléfono siempre ha estado conmigo, por lo que nadie más tuvo acceso físico a él.
¿Le ha pasado esto a alguien más?
Click to expand...
Click to collapse
Tengo el pixel 6 y ayer lo tenía en el bolsillo y cuando lo saqué estaba en modo recovery y me dijo que lo mismo sutema es corrupto Android no pudo arrancar y tuve que resetear el dispositivo
Mafuponce said:
Tengo el pixel 6 y ayer lo tenía en el bolsillo y cuando lo saqué estaba en modo recovery y me dijo que lo mismo sutema es corrupto Android no pudo arrancar y tuve que resetear el dispositivo
Click to expand...
Click to collapse
According to XDA rules you are required to at least add an english translation if you post in a different language. Please do that, you can't expect everybody else to translate your post for you.
I have the pixel 6 and yesterday I had it in my pocket and when I took it out it was in recovery mode and told me that the same sutema is corrupt Android could not boot and I had to reset the device
Mafuponce said:
I have the pixel 6 and yesterday I had it in my pocket and when I took it out it was in recovery mode and told me that the same sutema is corrupt Android could not boot and I had to reset the device
Click to expand...
Click to collapse
I had to force my one into recovery mode, but it's strange now that it's not just me who experienced this
Yessss
AYUDAR TEngo un lenovo y90 esta bien y se actualizo empeso pagarse de repente y luego empeso ponerse verde y ya no se ve bada como puedo cambiarle rom o que puedo aser ya no se ve nada en pantalla solo neas verdes
Mod translation: HELP I have a lenovo y90 it's fine and it updated it started to pay suddenly and then it started to turn green and it no longer looks bad how can I change the rom or what can I do, nothing can be seen on the screen anymore only green lines
Does rebooting works