Related
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.
[ENGLISH - ESPAÑOL MAS ABAJO!!]
ADVISE: First of all, remember that you are the only responsible for what you do with your phone. I'll always try to help you and share my knowledge and experience, just as others do. But please read as much as you can BEFORE trying it! Ok, let's go:
► KDZ DOWNLOAD LINK FROM LG SITE: http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FWC9W5Q132VMABR926A6DWJ/H340AR10a_04.kdz
I've searched a lot for this KDZ, and could finally find it at http://devtester.ro/projects/lg-firmwares/country.php?country=Argentina .
At that page it's stated as a CLARO variant, but I can confirm that it is a NO-CARRIER clean ROM for Argentina. I don't know if it works in other countries. Keep in mind that, even if everything is working perfectly (at least in my Leon), every time you boot your phone, you will receive a little advice saying "Warning! Current version is not available for user. Can't find matchest cust for NT-code..." that means that this is not a ROM meant to be used by users, but devs. That's true, but you can just dismiss that advice, by BACK button and everything work fine without carrier bloatware. Personally, I felt my device more responsive. And I'm (let's see the bright side) *happy* that I needed to try this firmware after a brick, and not having the original KDZ for my carrier. [/B]
-----------------
How to FLASH it?
You will need to install LG USB drivers, LG Mobile Support tool, download LG FLASH UTILITY 2014, and the KDZ.
I'll show a method taken from this site, the same I've followed: Note that you don't loose any data with this method, unless you factory reset.
INSTALL IN THIS ORDER:
1) LG Mobile Support Tool [atached to this same post]
2) LG United Mobile Driver 3.14.1 https://mega.nz/#!oQV3yS6Y!D2JPtEMfHiAXB5E5jC2lfFH8ZIOVLNhEHju28JtYwfI
3)LG Flash tool 2014 https://mega.nz/#!BB8UgKCT!YAdGWfYGXGLiV5arZzeSGGivtLlW-BuiKlv_ci2Xp0Y [also atached to this same post]
After everything has been installed:
1. Remove the battery and put it back in.
2. Hold the Volume Up button (ONLY) while connecting the USB Cable to the PC
3. The Volume up button needs to be held until it reaches download mode (FIRMWARE UPDATE screen)
4. Open device manager in Windows and changed the LGE Mobile USB Serial port to COM 20
5. Open the LG Flash Tool 2014
6. Select Type: 3GQCT
7. PhoneMode: EMERGENCY
8. KDZ : Select the location where the KDZ has been downloaded
9. Click on Normal Flash
10. Click on START. And wait, it will open a new window.
11. On that window, click on "Clear update registry"
12. Country: different country
13. Language: English
14. Click okay and wait for the LG Mobile Support tool to recognize the device. It takes a minute or two but the tool will recognize it. The software starts the extraction and re-boots at %100. WAIT UNTIL IT REBOOTS! It seems to be frozen at 100% or 99$%, but it is NOT!
Once your device is in Android, you can remove USB cable, your device will boot normally, and the device is no longer stuck in a boot loop.
Click to expand...
Click to collapse
----------------
How to avoid bricking it?
Root - In my case I could root it with KingRoot apk, the LATEST FROM THEIR SITE (not xda, not other.. but kingroot site. Others didn't work)
TWRP - Meh, I wouldn't mess with it, if you want to avoid flashing kdz. Everything started there, in my case. TWRP couldn't flash correctly.
SuperSUMe - DO NOT use this! After using it to remove kingroot app and install superSU , reboot & bricked. Another person here told me it worked for him. But in my case that was the 'root' cause for the brick. Maybe the method by W0lf works! At least you can read the script and see what does it do. And it does not cost money... meh
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[ESPAÑOL!]
AVISO: Recordá que sos el/la unico/a responsable por lo que hacés con tu celular. Siempre voy a intentar ayudarte y compartir mis conocimientos, como lo hacen el resto de los usuarios de la comunidad. Pero intentá leer lo más que puedas ANTES de intentarlo. Ok? Vamos!
► LINK DE DESCARGA DEL KDZ DESDE SITIO LG: http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FWC9W5Q132VMABR926A6DWJ/H340AR10a_04.kdz
Estuve buscando mucho este KDZ hasta que lo contré en http://devtester.ro/projects/lg-firmwares/country.php?country=Argentina . Ahí está listado como ser de Claro Argentina, pero puedo confirmar que es una version LIMPIA developer, la que usan luego las compañías para llenarlas de bloatware. Ehm, digo, de hermosas utilidades de la empresa. QUizá funcione para otros paises, no lo se. Tené en cuenta que, incluso si todo funciona perfecto (al menos en mi Leon) cada vez que reinicias el celular, vas a tener un pequeño mensaje que dice "Warning! Current version is not available for user. Can't find matchest cust for NT-code..." que significa que la ROm no es para usuarios finales sino developers, y es cierto, pero simplemente podes descartar ese mensaje con el boton atrás. Personalmente, siento mi dispositivo más rapido. Por un lado estoy (busquémosle el lado positivo a todo) "feliz" de haber tenido un softbrick y no tener la KDZ de personal, porque pude probar ésta.
-----------------
¿Cómo flashearla? (y me refiero al KDZ!)
Necesitás instalar LG USB drivers, LG Mobile Support tool, y descargar LG FLASH UTILITY 2014, y el KDZ.
Este método a continuación es el que yo encontré en este sitio y fue el que utilicé. No perdés ninguna data usando este método, salvo que hagas reseteo de fábrica.
INSTALAR EN ESTE ORDEN:
1) LG Mobile Support Tool [adjuntado en este post]
2) LG United Mobile Driver 3.14.1 https://mega.nz/#!oQV3yS6Y!D2JPtEMfHiAXB5E5jC2lfFH8ZIOVLNhEHju28JtYwfI
3) LG Flash tool 2014 https://mega.nz/#!BB8UgKCT!YAdGWfYGXGLiV5arZzeSGGivtLlW-BuiKlv_ci2Xp0Y [también adjuntado en este post]
Luego de instalar todo:
1. Remover la batería y volver a colocarla
2. Conectar un extermo del cable USB a la PC y mantener presionado VOL+ mientras se conecta el otro extremo del cable al celular
3. VOL+ Tiene que mantenerse presionado hasta que aparezca la ventana de Firmware Update en el celular
4. Abrir administrador de dispositivos en Windows y cambiar el puerto COM de LGE Mobile USB Serial al COM 20
5. Abrir LG Flash Tool 2014
6. En Type seleccionar: 3GQCT
7. En PhoneMode: EMERGENCY
8. En KDZ : Seleccionar la ruta donde está la KDZ descargada (quiza sea óptimo tener todo en una carpeta en C:\, por si hay rutas largas)
9. Clickear Normal Flash
10. En la nueva ventana, clickear START. Y esperar... se abrirá una nueva ventana.
11. En esa ventana nueva, clickear "Clear update registry"
12. Country: different country
13. Language: English (yo lo hice así. Si está Spanish, quizá podes seleccionarla! O cambiar despues el idioma)
14. Clickear OK y esperar a que se abra LG MOBILE SUPPORT y reconozca el dispositivo. Esto puede tomar unos minutos, pero lo reconoce. Empieza a trabajar y al 99 o 100% parece que se frizea, pero tenes que ESPERAR a que se reinicie el dispositivo. Luego de reiniciar, ya podes sacar el USB cable. No antes de que salga de Firmware Update. Ya deberia estar funcionando sin problemas! Puede tardar un poco el primer boot.
Click to expand...
Click to collapse
----------------
¿Cómo evitar BRICKEARLO?
*Root - En mi caso lo rutié sin dramas usando el último KingRoot de SU SITIO WEB, no de xda, sino del sitio de ellos. Es una apk.
*TWRP - En mi caso no pude flashearla, y ahi empezó todo el problema. Pero no causó el root. Seguí el método "dd" y el de TWRP manager sin éxito.
*SuperSU Me - Éste guacho me lo brickeó. Un generoso compañero de XDA intentó ayudarme pasándome el dato, pero al correrlo, se brickeó. Quizá el método de W0lf funcione. Hay que probar. Al menos se puede leer el script para ver exactamente qué hace, y no cuesta dinero...
********************************** MUCHOS MÁS TUTORIALES EN MI CANAL EN YOUTUBE ******************************************
**************************** NUEVO APRENDIZAJE ► http://www.youtube.com/NuevoAprendizaje ************************************
I find this very interesting. I wonder if it would work on my T-Mobile LG Leon LTE (H345n)...What carrier variant do you have of the phone... Also.. just out of curiousity... I'm wondering if this rom takes up less internal storage on the phone. Because that would be real cool considering most of the firmwares take up more than half of the 8 gb internal storage. Would you mind checking that out and getting back to me about it?
Yazuken1 said:
I find this very interesting. I wonder if it would work on my T-Mobile LG Leon LTE (H345n)...What carrier variant do you have of the phone... Also.. just out of curiousity... I'm wondering if this rom takes up less internal storage on the phone. Because that would be real cool considering most of the firmwares take up more than half of the 8 gb internal storage. Would you mind checking that out and getting back to me about it?
Click to expand...
Click to collapse
I guess the only difference in storage would be anything carrier-related. None of those apps are installed. That includes games, carrier apps, promotions... This is v10a-722-34 LRX21Y, Android 5.0.1
Hola leandeganis, muchas gracias man me vino de 10 el post.
Pudiste encontrar alguna rom modificada que funcione bien con el Leon?
nmastellone said:
Pudiste encontrar alguna rom modificada que funcione bien con el Leon?
Click to expand...
Click to collapse
Nope, but I'm posting all improvements I do to stock ROM in this thread: http://forum.xda-developers.com/android/development/fix-low-mic-volume-bad-quality-headset-t3270558
What model Leon do you have? I have an lgl21 which is a straight talk variant. Called LG Destiny. Do you know if in that rom there is the oem unlock option in dev settings? The reason why I'm asking is because I'm trying to figure out how to unlock my bootloader to attempt to flash the c50 recovery to my phone. Just in case I get a brick I'll try this KDZ. But once I figure out how to pull my device tree and then try to port the 5.1 KDZ for my variant. I've never dev before so this is going to be a learning experience for me.
Failbringer60 said:
What model Leon do you have? I have an lgl21 which is a straight talk variant. Called LG Destiny. Do you know if in that rom there is the oem unlock option in dev settings? The reason why I'm asking is because I'm trying to figure out how to unlock my bootloader to attempt to flash the c50 recovery to my phone. Just in case I get a brick I'll try this KDZ. But once I figure out how to pull my device tree and then try to port the 5.1 KDZ for my variant. I've never dev before so this is going to be a learning experience for me.
Click to expand...
Click to collapse
No oem unlock. Only in 5.1.1 versions
http://forum.xda-developers.com/showpost.php?p=62275619&postcount=461
Following these steps you'll be able to remove the warning. It worked in my sister's LG Spirit. Cheers
Siguiendo estos pasos van a poder sacar el cartel, funcionó en el LG Spirit de mi hermana. Saludos
Question
Hi, i have a LG Risio from Cricket, is the model -lg-H343 but i dont see this model in the list room, do you know if i can brick my phone if i install a open room of Argentina, like the H340?..What do you think?
roberto217 said:
Hi, i have a LG Risio from Cricket, is the model -lg-H343 but i dont see this model in the list room, do you know if i can brick my phone if i install a open room of Argentina, like the H340?..What do you think?
Click to expand...
Click to collapse
You can try I think it should either fail in the flash process or succeed. But I think you should better try an specific kdz for your model. lg-phone-firmware.com and devtester.ro have lot of firmwares listed. Try with your imei.
igna.98 said:
http://forum.xda-developers.com/showpost.php?p=62275619&postcount=461
Following these steps you'll be able to remove the warning. It worked in my sister's LG Spirit. Cheers
Siguiendo estos pasos van a poder sacar el cartel, funcionó en el LG Spirit de mi hermana. Saludos
Click to expand...
Click to collapse
Gracias! Probaste instalar este kdz en el spirit? O como llegaste aca?
do you have a good link for this kdz? the old one is down
Buenas gente! Podrían pasarme las especificaciones técnicas del h340 LTE ya que estoy viendo si es posible flashar al h320 una banda base para que levante LTE! Por lo visto en la pagina de LG este modelo (h320) tiene LTE pero para una compañía de México.
Hi people, can u share tecnical hardware from H340 LTE , im tinking to port an base band to H320 it seems capable but unly whit a mexican carrier..
Sorry for my bad english.
Enviado desde mi XT1045 mediante Tapatalk
Compré mi celular en musimundo. Pero aún liberado, la rom que tiene está llena de basuras y hace lento todo el sistema. Incluso tenía mal configurado el cpu con planificacion noop y governor en performance, trabajando de 1.21ghz a 1.21ghz. La batería se moría en menos de 5 horas. Horrible. Usé el Kingroot y habia aplicaciones como una tal "Aplicativos nacionails" o algo por el estilo, con una bandera brasileña en el ícono. Me pregunto para qué carajo estaba ahi consumiendo ram. Por supuesto la eliminé junto con play fotos/videos/musica, el antivirus inservible y otras pavadas que consumian recursos.
Voy a flashear esta y usar el tutorial que está por ahi que mejora el uso de memoria por parte del sistema operativo.
Se agradece el aporte.
help,ayuda para ser root LG Leon
hola como puedo rootear lg leon h340ar con android 6.0 (segui tu tutorial pero el kdz lo saque de aqui
http://forum.xda-developers.com/leon/how-to/how-to-update-lg-leon-h340n-to-android-t3393648
). cuando tengo apretado el boton de encendido + volumen bajo solo aparece la opcion de restaurar de fabrica.
¡¡¡¡¡¿¿¿¿¿Para ser root tengo que cargar el zip de superSU,pero para hacerlo necesito tener un recovery personalizado Y Para instalar un recovery personalizado tengo que ser root.!!!???
Gracias de antemano.
Ayuda!
Buenas! Necesito ayuda...estaba haciendo bien todos los pasos hasta que llegue al 10
"10. En la nueva ventana, clickear START. Y esperar... se abrirá una nueva ventana."
Cuando hago click en START se cierra la ventana, pero no aparece ninguna nueva...y se queda asi, no pasa nada...que puedo hacer?
El celu sigue en 0% y solo dice que no tengo que desconectar el USB hasta que termine el proceso.
Se agradece cualquier ayuda
Luego de hacer esto todos los datos van a ser borrados? Yo lo hice, el boot no me arrancaba, hice el flash y lo pude hacer prender pero las apps, fotos y demas datos seguían ahí
che, tengo dos problemas: No puedo bajar el kdz, me dice "no file found" y 2do: tengo el kdz de claro (justo el stock de mi cel) y cada vez que flasheo el kdz el cel se queda en la bootscreen y se reinica
Sabes como puedo fixearlo?
I CANT DOWNLOAD ROM!
never download the rom from site!
blank page from the link...
totto210 said:
I CANT DOWNLOAD ROM!
never download the rom from site!
blank page from the link...
Click to expand...
Click to collapse
Como puedo descargar el KDZ?
I bought a new z5 compact E5803 from my carrier here in Mexico, the first thing that I did was to install an unbranded firmware, the Customized US one (32.0.A.6.209/R7B) but found that the fingerprint is disabled.
I want to install a UK version, but I only found it over the E5823 device firmwares, so, can I install it on my E5803 or will I brick my phone?
earoth88 said:
I bought a new z5 compact E5803 from my carrier here in Mexico, the first thing that I did was to install an unbranded firmware, the Customized US one (32.0.A.6.209/R7B) but found that the fingerprint is disabled.
I want to install a UK version, but I only found it over the E5823 device firmwares, so, can I install it on my E5803 or will I brick my phone?
Click to expand...
Click to collapse
This thread should help
http://forum.xda-developers.com/xperia-z5/general/e6653-flash-e6603-firmware-enable-t3307158
Pakman123 said:
This thread should help
http://forum.xda-developers.com/xperia-z5/general/e6653-flash-e6603-firmware-enable-t3307158
Click to expand...
Click to collapse
Thanks, that will help I'm checking it right now.
As another question, do you know if it's safe to just update my phone with a E5823 firmware? Or better play safe and just update the required files?
Thanks!!
earoth88 said:
I bought a new z5 compact E5803 from my carrier here in Mexico, the first thing that I did was to install an unbranded firmware, the Customized US one (32.0.A.6.209/R7B) but found that the fingerprint is disabled.
I want to install a UK version, but I only found it over the E5823 device firmwares, so, can I install it on my E5803 or will I brick my phone?
Click to expand...
Click to collapse
Pues segun el tutorial de link si se puede solo reemplazando los archivos mencionados.
Yo tengo el unbranded de turquia si mal no recuerdo y jala bien lo unico es q aparece "LTE" en vez de "4G" ah y no aparece el icono de "nfc" aunque este activado.
Me salta la duda si realizando el tutorial se podria actualizar via ota jejeje
Saludos!
MOD EDIT English translation added
Well according to the tutorial link if you can just replace the aforementioned files.
I have the unbranded of turkey if I remember well and pulls the only thing is q appears "LTE " instead of "4G" ah , not the icon " nfc " although this appears activated .
I doubt if it jumps doing the tutorial can be updated via OTA lol
Greetings!
acabreram said:
Pues segun el tutorial de link si se puede solo reemplazando los archivos mencionados.
Yo tengo el unbranded de turquia si mal no recuerdo y jala bien lo unico es q aparece "LTE" en vez de "4G" ah y no aparece el icono de "nfc" aunque este activado.
Me salta la duda si realizando el tutorial se podria actualizar via ota jejeje
Saludos!
Click to expand...
Click to collapse
Hace unas horas hice la actualización de acuerdo al tutorial y funcionó bien, lo único raro es que ya no me sale "TELCEL" arriba; pero todo lo demás funciona sin problema (Aparece 4G también, yo creo que por ser el de UK y sí sale el de NFC).
Y lo de la actualización OTA creo que sí se podría hacer, porque estamos usando el firmware "normal", pero si lo hacemos directo perderíamos el lector de huellas.
Yo también andaba viendo si instalaba la de Turquía, pero prefería la de Estados Unidos (y creo que sí trae unos bug fixes porque siento un poco más fluido el celular).
-----------------------
I followed the procedure a couple of hours ago and it worked fine, the only thing that seems missing is the carrier name on the notification bar, but everything else works as expected (network is shown as 4G, I suppose it's because the ROM is from UK, and NFC is shown as expected).
About the OTA update, I think that we could do it, because we're still on an "original" ROM, but if we do it I guess we'll lose the fingerprint reader.
I thought about installing Turkey ROM, but I preferred USA (I think it has a couple of bug fixes, phone runs a little faster than before, at least to me).
earoth88 said:
Hace unas horas hice la actualización de acuerdo al tutorial y funcionó bien, lo único raro es que ya no me sale "TELCEL" arriba; pero todo lo demás funciona sin problema (Aparece 4G también, yo creo que por ser el de UK y sí sale el de NFC).
Y lo de la actualización OTA creo que sí se podría hacer, porque estamos usando el firmware "normal", pero si lo hacemos directo perderíamos el lector de huellas.
Yo también andaba viendo si instalaba la de Turquía, pero prefería la de Estados Unidos (y creo que sí trae unos bug fixes porque siento un poco más fluido el celular).
-----------------------
I followed the procedure a couple of hours ago and it worked fine, the only thing that seems missing is the carrier name on the notification bar, but everything else works as expected (network is shown as 4G, I suppose it's because the ROM is from UK, and NFC is shown as expected).
About the OTA update, I think that we could do it, because we're still on an "original" ROM, but if we do it I guess we'll lose the fingerprint reader.
I thought about installing Turkey ROM, but I preferred USA (I think it has a couple of bug fixes, phone runs a little faster than before, at least to me).
Click to expand...
Click to collapse
ok pues que bueno que si funciona lo intentare ya que tenga un poco mas de tiempo, en el numero de modelo te aparece 5803 o 5823?
Veo muy pobre el desarrollo para este cel, ya se q no es algo tan facil pero pues a comparacion de otro modelos hay mas desarrollo solo espero que para la siguiente version podamos probar un concept como el z3!!
Lo siento necesitaba desahogarme!!
jajajajaja
MOD EDIT English translation added
ok for that good if it works I'll try and have a little more time in the model number 5803 or 5823 appears to you ?
I see poor development for this cel, already q is not so easy but as a comparison of other models there is more development just hope that for the next version can test a concept as z3 !!
Sorry I needed to vent !!
hahaha
acabreram said:
ok pues que bueno que si funciona lo intentare ya que tenga un poco mas de tiempo, en el numero de modelo te aparece 5803 o 5823?
Veo muy pobre el desarrollo para este cel, ya se q no es algo tan facil pero pues a comparacion de otro modelos hay mas desarrollo solo espero que para la siguiente version podamos probar un concept como el z3!!
Lo siento necesitaba desahogarme!!
jajajajaja
Click to expand...
Click to collapse
Yo tengo el E5803, y sí noté que casi no hay desarrollo para este cel, vengo del z1 Compact que si bien no era taaaan desarrollado, sí tenía más vida el foro.
Lo que si es que ya estoy esperando a que salga el ROM de MarshMallow, ojalá no se tarden tanto.
--------------
Mine's E5803, and yes, I noticed too that there's almost no development for this phone, my previous one was Z1 Compact and, although there wasn't that much development surely there was more than here.
What I'm waiting for is for the MarshMallow ROM, hoping that its release date is not that far away.
earoth88 said:
Yo tengo el E5803, y sí noté que casi no hay desarrollo para este cel, vengo del z1 Compact que si bien no era taaaan desarrollado, sí tenía más vida el foro.
Lo que si es que ya estoy esperando a que salga el ROM de MarshMallow, ojalá no se tarden tanto.
--------------
Mine's E5803, and yes, I noticed too that there's almost no development for this phone, my previous one was Z1 Compact and, although there wasn't that much development surely there was more than here.
What I'm waiting for is for the MarshMallow ROM, hoping that its release date is not that far away.
Click to expand...
Click to collapse
segun los rumores el 17 marzo pero pues a ver, yo estoy igual esperando mm ya sea aosp o stock rom.
MOD EDIT English translation added
Rumor March 17, but it 's see, I 'm just waiting mm either or stock AOSP rom .
did you guys end up doing the file replacement or flash another firmware over it !?
Hola, pues llevo ya casi un mes intentando que me funcione el reloj reseteando,probando la china y la inglesa. y siempre se queda la pantalla en negra y lo tengo que apagar y encender.
he probado con huangeheUS-1.3.3a-installer
Verge_Stock_US_3.2.7.5_Firmware_Installer
Instalador_v2.0.1_Verge_ROM_3.0.52.0_Multi
Bootloader_Flash
y nada,
no se que metedo mas probar.
gracias
Mi modelo según en caja es el A1811. Pero luego en el reloj me pone el A1801, y cuando instalo la rom paceficator tambien me pone modelo A1801 aunque instale la A1811 me pone que teno el modelo chino y eso porque?
Hello, I have been trying to reset the clock for almost a month, trying the Chinese and the English. and the screen always stays black and I have to turn it off and on.
I have tried with huangeheUS-1.3.3a-installer
Verge_Stock_US_3.2.7.5_Firmware_Installer
Installer_v2.0.1_Verge_ROM_3.0.52.0_Multi
Bootloader_Flash
and nothing,
I don't know what else to try.
Thank you
My boxed model is the A1811. But then in the clock it puts the A1801, and when I install the paceficator rom it also gives me the A1801 model, although I install the A1811 it tells me that I have the Chinese model and why?
I'm looking for official firmwares for Moto One Fusion (not plus). XT2073-2.
Android 10 latest build is: Motorola_One_Fusion_XT2073-2_ASTRO_RETAIL_QPLS30.62-22-3_10
I haven't found a place to download from. The only one is a google drive invalid/expired link. I would thank any help!
VassagoU7XDA said:
I'm looking for official firmwares for Moto One Fusion (not plus). XT2073-2.
Android 10 latest build is: Motorola_One_Fusion_XT2073-2_ASTRO_RETAIL_QPLS30.62-22-3_10
I haven't found a place to download from. The only one is a google drive invalid/expired link. I would thank any help!
Click to expand...
Click to collapse
There you go https://mirrors.lolinet.com/firmware/moto/astro/official/
jmcc30 said:
There you go https://mirrors.lolinet.com/firmware/moto/astro/official/
Click to expand...
Click to collapse
Thank you very much , but sadly can't reach the link. Do you know if still alive?
VassagoU7XDA said:
Thank you very much , but sadly can't reach the link. Do you know if still alive?
Click to expand...
Click to collapse
Oh yeah, they seem to have storage issues, tell me your country and I might find you the link
jmcc30 said:
Oh yeah, they seem to have storage issues, tell me your country and I might find you the link
Click to expand...
Click to collapse
Link was working today , I found and already downloaded the firmware. You helped me so much . Thank you!
VassagoU7XDA said:
Link was working today , I found and already downloaded the firmware. You helped me so much . Thank you!
Click to expand...
Click to collapse
Nice, have great flashing!
.
duvancho said:
good that someone help me what happens els that fhasee a boot.img patched by magisk manager and I damaged the touch tatil of my android
bueno que alguien me ayude lo q pasa els que fhasee un boot.img parcheado por magisk manager y me daño el touch tatil de mi androide
Click to expand...
Click to collapse
That happens when you flash the incorrect boot.img. incorrect I mean another firmware version of the boot.img or a boot.img from another device .
You have to get the correct boot.img and flash it the same way you did it.
* Be sure you have the Moto One Fusion. If you have the Moto One Fusion Plus you have to get the firmware for that specific device. The link in the steps below is for Moto One Fusion.
Don't worry, if you read carefully and follow the next steps you can fix your device.
1. I suggest you to download the most recent firmware from here https://mirrors.lolinet.com/firmware/moto/astro/official/
2. Unzip the downloaded file and get the boot.img
3. Flash it the same way you did it with the incorrect boot.img
4. If that fix the touch issue and everything works fine you can use the same boot.img to be patched by magisk and try the step 3 with the patched boot.img.
5. If step 3 doesn't work return to step 1 and try with another firmware version.
6. If the steps above didn't work, You can flash the full firmware. You have to follow another steps for that. Let me know first if that happens .
,
?
duvancho said:
[QUOTE = "VassagoU7XDA, publicación: 84191209, miembro: 11327551"]
Eso sucede cuando actualiza el archivo boot.img incorrecto. incorrecto me refiero a otra versión de firmware de boot.img o un boot.img de otro dispositivo.
Debe obtener el boot.img correcto y actualizarlo de la misma manera que lo hizo.
* Asegúrese de tener el Moto One Fusion. Si tiene el Moto One Fusion Plus, debe obtener el firmware para ese dispositivo específico. El enlace de los pasos a continuación es para Moto One Fusion.
No se preocupe, si lee atentamente y sigue los siguientes pasos, puede reparar su dispositivo.
1. Le sugiero que descargue el firmware más reciente desde aquí https://mirrors.lolinet.com/firmware/moto/astro/official/
2. Descomprima el archivo descargado y obtenga el archivo boot.img
3. Actualice de la misma manera que lo hizo con el archivo boot.img incorrecto.
4. Si eso soluciona el problema táctil y todo funciona bien, puede usar el mismo boot.img para ser parcheado por magisk e intentar el paso 3 con el boot.img parcheado.
5. Si el paso 3 no funciona, vuelva al paso 1 e intente con otra versión de firmware.
6. Si los pasos anteriores no funcionaron, puede actualizar el firmware completo. Tienes que seguir otros pasos para eso. Avísame primero si eso sucede.
[/ CITAR]
No friend is still the same with the same problem and I'm sad that I bought it for six days and I already damaged it and the guarantee does not cover those failures, I have to repair it on my own merits as well as damage it. I have already installed several firmware from this rom:
astro_retail-user 10 QPLS30.62-22-3 f2517 (moto one fusion) in several pages and it still does not work.
the other would be to install the complete rom but I would not know if the commands are fhasable I got them from a third party page.
Anyway, any help would be very useful to me, thanks.
Click to expand...
Click to collapse
I'm totally sure you can fix your phone. I'm not at home right now , maybe tomorrow at night I will review the firmware file and give you the steps to fash the full firmware.
duvancho said:
[QUOTE = "VassagoU7XDA, publicación: 84191209, miembro: 11327551"]
Eso sucede cuando actualiza el archivo boot.img incorrecto. incorrecto me refiero a otra versión de firmware de boot.img o un boot.img de otro dispositivo.
Debe obtener el boot.img correcto y actualizarlo de la misma manera que lo hizo.
* Asegúrese de tener el Moto One Fusion. Si tiene el Moto One Fusion Plus, debe obtener el firmware para ese dispositivo específico. El enlace de los pasos a continuación es para Moto One Fusion.
No se preocupe, si lee atentamente y sigue los siguientes pasos, puede reparar su dispositivo.
1. Le sugiero que descargue el firmware más reciente desde aquí https://mirrors.lolinet.com/firmware/moto/astro/official/
2. Descomprima el archivo descargado y obtenga el archivo boot.img
3. Actualice de la misma manera que lo hizo con el archivo boot.img incorrecto.
4. Si eso soluciona el problema táctil y todo funciona bien, puede usar el mismo boot.img para ser parcheado por magisk e intentar el paso 3 con el boot.img parcheado.
5. Si el paso 3 no funciona, vuelva al paso 1 e intente con otra versión de firmware.
6. Si los pasos anteriores no funcionaron, puede actualizar el firmware completo. Tienes que seguir otros pasos para eso. Avísame primero si eso sucede.
[/ CITAR]
No friend is still the same with the same problem and I'm sad that I bought it for six days and I already damaged it and the guarantee does not cover those failures, I have to repair it on my own merits as well as damage it. I have already installed several firmware from this rom:
astro_retail-user 10 QPLS30.62-22-3 f2517 (moto one fusion) in several pages and it still does not work.
the other would be to install the complete rom but I would not know if the commands are fhasable I got them from a third party page.
Anyway, any help would be very useful to me, thanks.
Click to expand...
Click to collapse
Try the guide I wrote here: https://forum.xda-developers.com/t/guide-one-fusion-xt2073-fastboot-flashing.4205723/
Tell me if it works
.
duvancho said:
[QUOTE = "jmcc30, publicación: 84194363, miembro: 3905426"]
Prueba la guía que escribí aquí: https://forum.xda-developers.com/t/guide-one-fusion-xt2073-fastboot-flashing.4205723/
Dime si funciona
[/CITAR]
gracias amigo, lo que
[QUOTE = "jmcc30, publicación: 84194363, miembro: 3905426"]
Prueba la guía que escribí aquí: https://forum.xda-developers.com/t/guide-one-fusion-xt2073-fastboot-flashing.4205723/
Dime si funciona
[/CITAR]
gracias amigo, lo que sospechaba tenía los códigos parpadeando mal si funcionó para mí muchas gracias jmcc30 y VassagoU7XDA.
Click to expand...
Click to collapse
Good to know your phone is working again. That guide has exactly the steps I was talking about. Just in case you still interested in magisk, you can use the boot.img file you flashed to fix your phone to be patched by magisk app. The result will be a flashed_boot.img that you can flash using the command:
fastboot flash boot flashed_boot.img
and there you go. If something goes wrong you can flash the original one as follow
fastboot flash boot boot.img
The only rule here is to flash the correct boot.img file. The same your phone is already using. If you use a boot.img from another firmware version you're going to experience the same screen touch problem.
In Spanish (trying to explain in the best way)
En Español (tratando de explicar de la mejor manera)
Es bueno saber que su teléfono está funcionando nuevamente. Esa guía tiene exactamente los pasos de los que estaba hablando. En caso de que todavía estés interesado en magisk, puedes utilizar el archivo boot.img que flasheaste para arreglar su teléfono para que sea parcheado por la aplicación magisk. El resultado será un archivo flashed_boot.img que puedes flashear usando el comando:
fastboot flash boot flashed_boot.img
y ahí lo tienes. Si algo sale mal, puede flashear el boot.img original de la siguiente manera
fastboot flash boot boot.img
La única regla aquí es flashear el archivo boot.img correcto. El mismo que tu teléfono ya está usando. Si usas un boot.img de otra versión de firmware, experimentarás el mismo problema de que no responde la pantalla.
good friends again what happens is that it begins to present errors in the android. the screen goes black every time I use it. and then I have already restarted it from the factory, I have also fasted all the versions of the firmware and it continues with the same failure if someone knows why this happens to me I would thank you
,
Can you make a video (from another phone)
Ok, I asked for a video because I don't understand the problem at all.
By the way, are you sure you flashed the last firmware version?
Can you put here the full firmware file name ?
Have you tried with another firmware versión?
,