Database Users

Firts Confg, stopped because Unfortunately, the process com.google.process.gapps

My phone has shutted down and won't turn on anymore since it's stuck on the M logo. I made a hard reset and it worked! I went through the initial settings until this appears:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, Google Play Services has stopped.
These messages are appearing every single time, which then make the phone reboot. Now it's got into an endless cycle and I cannot use it. Any help?
Mi teléfono se apago y no arrancaba mas se quedaba en el logo de Motorola realice un hard reset desde recovery mode, ahora enciende y empezamos con la configuración inicial. PERO OH SORPRESA
Mensaje:
Lo sentimos el proceso com.google.process.gapps se detuvo.
La Aplicacion Google Play Service se detuvo.
Estos mensajes inundan mi pantalla imposibilitan dome continuar y posteriormente se reinicia el teléfono.
Se a creado un ciclo asi esta hasta que se acaba la bateria.
[FONT="<font><font>Arial Negro</font></font>"]Necesito Ayuda que Puedo hacer para solucionar este problema?[/FONT]

Esto es solamente en inglés amigo, no uses español. PD: trata de reinstalar todo desde fastboot. (This is english only, bud. Do not use spanish. PD: try reinstalling the system with fastboot)
Translation:
My phone has shutted down and won't turn on anymore since it's stuck on the M logo. I made a hard reset and it worked! I went through the initial settings until this appears:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, Google Play Services has stopped.
These messages are appearing every single time, which then make the phone reboot. Now it's got into an endless cycle and I cannot use it. Any help?

lucianogm said:
Esto es solamente en inglés amigo, no uses español. PD: trata de reinstalar todo desde fastboot. (This is english only, bud. Do not use spanish. PD: try reinstalling the system with fastboot)
Translation:
My phone has shutted down and won't turn on anymore since it's stuck on the M logo. I made a hard reset and it worked! I went through the initial settings until this appears:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, Google Play Services has stopped.
These messages are appearing every single time, which then make the phone reboot. Now it's got into an endless cycle and I cannot use it. Any help?
Click to expand...
Click to collapse
ok thankyou friend, i cant use fastboot because i dont have permition for usb debug i cant enter to configuration on my celphone, if I try to install from fastboot says "there is sufficient permissions"

cgrwar93 said:
ok thankyou friend, i cant use fastboot because i dont have permition for usb debug i cant enter to configuration on my celphone, if I try to install from fastboot says "there is sufficient permissions"
Click to expand...
Click to collapse
really weird. Do you have a custom recovery installed? You could try to format all partitions (system, data, caché and dalvik) and reinstall the system with a zip.

lucianogm said:
really weird. Do you have a custom recovery installed? You could try to format all partitions (system, data, caché and dalvik) and reinstall the system with a zip.
Click to expand...
Click to collapse
i dont have a custum recovery, i cant install because i dont have permissions, whei i try installe say failure on verifying packets.

Unbrick RN3 from HS USB 900E with EDL cable %100 working methode

If your RN3 Pro brick ,no download, no recovery mode ...
only 900E mode ...
http://i.hizliresim.com/NkW24O.jpg
Press power button 10 sec. while EDL button pressing.
Then release power button.
After then 8 sec. release EDL button.
Your RN3 turn from 900E to 9008
http://unbrick-snapdragon.blogspot.com.tr/2016/07/mi-snapdragon-telefonlar-icin-9008.html
Now you can flash with miflash fastboot rom.
http://unbrick-snapdragon.blogspot.com.tr/2016/05/snapdragon-islemcili-xiaomi.html
Making home made EDL cable ;
http://i.hizliresim.com/Y4JEl6.jpg
http://i.hizliresim.com/aX0NDz.jpg
https://www.youtube.com/watch?v=DJZ6Ka7mrIA
thanx to @manaswb

interesting to know, thanks
it might save people from having to use the test points which requires disassembly of the phone

Saludos amigo, me puedes ayudar, tengo el problema en este momento, el detalle es que al parecer no tengo carga en la batería, ¿Como cargo la batería de mi teléfono? o ¿como se que se esta cargando? si no enciende para nada.
En su momento (hace 1 mes) me reconocio siempre en 900E Diagnostic, pero ahora no ya que no me reconoce para nada (seguro porque no tiene batería)
"Ya tengo el cable hecho"
Me pueden ayudar @manaswb
Gracias amigos

same as MI5 edl flash cable

you saved my ass! after an unofficial bootloader unlock on kate, my phone went black. Couldn't do anything. Only 900E mode in windows device manager... it worked!

GNVM said:
same as MI5 edl flash cable
Click to expand...
Click to collapse
Hi GNVM,
Where did you got that information?
I need it since my friend is want to flash from china stable to global stable but still locked bootloader and now it can't be getting into EDL mode.
Could you please advise about it?
Please advise.
Thank you.
Regards,
Karkand

karkand said:
Hi GNVM,
Where did you got that information?
I need it since my friend is want to flash from china stable to global stable but still locked bootloader and now it can't be getting into EDL mode.
Could you please advise about it?
Please advise.
Thank you.
Regards,
Karkand
Click to expand...
Click to collapse
Follow the below Links.It will help you to make the flash cable.Good Luck.
http://en.miui.com/forum.php?mod=viewthread&tid=310325&highlight=mi5+flash+cable
http://en.miui.com/forum.php?mod=viewthread&tid=324300&highlight=mi5+flash+cable

https://www.youtube.com/watch?v=DJZ6Ka7mrIA

This worked to get an Orbic Wonder back into EDL model from 900E however I cannot get QPST nor UNI Antroid Tools or other flashers to work with it.

micro77 said:
If your RN3 Pro brick ,no download, no recovery mode ...
only 900E mode ...
http://i.hizliresim.com/NkW24O.jpg
Press power button 10 sec. while EDL button pressing.
Then release power button.
After then 8 sec. release EDL button.
Your RN3 turn from 900E to 9008
http://unbrick-snapdragon.blogspot.com.tr/2016/07/mi-snapdragon-telefonlar-icin-9008.html
Now you can flash with miflash fastboot rom.
http://unbrick-snapdragon.blogspot.com.tr/2016/05/snapdragon-islemcili-xiaomi.html
Making home made EDL cable ;
http://i.hizliresim.com/Y4JEl6.jpg
Click to expand...
Click to collapse
cableon picture is micro USB male and USB A female ??
thanx K.

krabat said:
cableon picture is micro USB male and USB A female ??
thanx K.
Click to expand...
Click to collapse
Because its posible connect microUSB cable, microC too etc.

BRICK QUSB_BULK device manager

Hello everyone was rotting when installing all successful and starting the device does not advance from the screen of the zte logo can be even hours with the logo until the battery is dead i have testered all the combinations of possible buttons ... The axon tools does not detect adb or fastboot mode and i can also reach it edl mode.
The only one that i get is then once when i have to uninstallthe driver to get the state in the device manager of windows qusb_bulk like universal usb. I do not know what to do if you can recover the phone please some link or guide to this problem
thanks

VIFTOKSKY said:
Hello everyone was rotting when installing all successful and starting the device does not advance from the screen of the zte logo can be even hours with the logo until the battery is dead i have testered all the combinations of possible buttons ... The axon tools does not detect adb or fastboot mode and i can also reach it edl mode.
The only one that i get is then once when i have to uninstallthe driver to get the state in the device manager of windows qusb_bulk like universal usb. I do not know what to do if you can recover the phone please some link or guide to this problem
thanks
Click to expand...
Click to collapse
You're not letting lots of things clear.
When you got into EDL, was the driver
-Qualcomm HS-USB QDLoader 9008
or
-ZTE something something DFU interface?
If you uninstall the Qualcomm HS-USB driver you won't be able to use MiFlash, which is the only thing that will help you at this point.
If you have the DFU thing, you can try letting the battery discharge completely and trying volume down + power many times, maybe while charging... Try some things, and if you get into FTM mode, you might be saved. If not you'll have to take apart your phone and follow the 4th category brick repair manual.
What's the model of your phone? (look in the back)

Choose an username... said:
You're not letting lots of things clear.
When you got into EDL, was the driver
-Qualcomm HS-USB QDLoader 9008
or
-ZTE something something DFU interface?
If you uninstall the Qualcomm HS-USB driver you won't be able to use MiFlash, which is the only thing that will help you at this point.
If you have the DFU thing, you can try letting the battery discharge completely and trying volume down + power many times, maybe while charging... Try some things, and if you get into FTM mode, you might be saved. If not you'll have to take apart your phone and follow the 4th category brick repair manual.
What's the model of your phone? (look in the back)
Click to expand...
Click to collapse
I'm going to start with the start
with the command axon7root.exe -p com3 -b -r (before the error was port 3 now appears as 10) but restarting the mobile stayed in the permanent zte logo I can only leave the Logo pressing the combo of the three keys volumen+/- + power at a time and just after that combo, it is left the black cell and appears in the device manager of windows the images that I attached, now has passed from qusb_bulk to qualcom 900 because i uninstall the drivers and then manually install the Drivers and chose that particular from the list of drivers
now
I'm going to start with the start with the command axon7root.exe -p com3 -b -r (before the error was port 3 now appears as 10) but restarting the mobile stayed in the permanent zte logo I can only leave the Logo pressing the combo of the three keys at a time and just after that combo, it is left the black cell appears in the device manager the images that I attached has passed from qusb_bulk to qualcom 900 because 1disntale the drivers and then manually install the Drivers and chose that particular from the list of drivers
I'm going to start with the start with the command axon7root.exe -p com3 -b -r (before the error was port 3 now appears as 10) but restarting the mobile stayed in the permanent zte logo I can only leave the Logo pressing the combo of the three keys at a time and just after that combo, it is left the black cell appears in the device manager the images that I attached has passed from qusb_bulk to qualcom 900 because 1disntale the drivers and then manually install the Drivers and chose that particular from the list of drivers
I'm going to start with the start with the command axon7root.exe -p com3 -b -r (before the error was port 3 now appears as 10) but restarting the mobile stayed in the permanent zte logo I can only leave the Logo pressing the combo of the three keys at a time and just after that combo, it is left the black cell appears in the device manager the images that I attached has passed from qusb_bulk to qualcom 900 because 1disntale the drivers and then manually install the Drivers and chose that particular from the list of drivers
I can not enter the edl mode as the attached image because when I press the volume- + power combination the device manager of windows does not detect the mobile phone.
Only detects the phone the device manager windows when I press the combination of all the buttons and then it is the current situation that I have although I put port 10 the adb does not detect the phone
Axon tool kits in this state also does not detect it ,and my flash is left empty list does not appear the phone
mi model of phone is ztea2017 (version china)
That is my current situation. so you recommend to me using the 4 category to repair a brick?
Or recommend me other steps

VIFTOKSKY said:
I'm going to start with the start
with the command axon7root.exe -p com3 -b -r (before the error was port 3 now appears as 10) but restarting the mobile stayed in the permanent zte logo I can only leave the Logo pressing the combo of the three keys volumen+/- + power at a time and just after that combo, it is left the black cell and appears in the device manager of windows the images that I attached, now has passed from qusb_bulk to qualcom 900 because i uninstall the drivers and then manually install the Drivers and chose that particular from the list of drivers
now
I'm going to start with the start with the command axon7root.exe -p com3 -b -r (before the error was port 3 now appears as 10) but restarting the mobile stayed in the permanent zte logo I can only leave the Logo pressing the combo of the three keys at a time and just after that combo, it is left the black cell appears in the device manager the images that I attached has passed from qusb_bulk to qualcom 900 because 1disntale the drivers and then manually install the Drivers and chose that particular from the list of drivers
I'm going to start with the start with the command axon7root.exe -p com3 -b -r (before the error was port 3 now appears as 10) but restarting the mobile stayed in the permanent zte logo I can only leave the Logo pressing the combo of the three keys at a time and just after that combo, it is left the black cell appears in the device manager the images that I attached has passed from qusb_bulk to qualcom 900 because 1disntale the drivers and then manually install the Drivers and chose that particular from the list of drivers
I'm going to start with the start with the command axon7root.exe -p com3 -b -r (before the error was port 3 now appears as 10) but restarting the mobile stayed in the permanent zte logo I can only leave the Logo pressing the combo of the three keys at a time and just after that combo, it is left the black cell appears in the device manager the images that I attached has passed from qusb_bulk to qualcom 900 because 1disntale the drivers and then manually install the Drivers and chose that particular from the list of drivers
I can not enter the edl mode as the attached image because when I press the volume- + power combination the device manager of windows does not detect the mobile phone.
Only detects the phone the device manager windows when I press the combination of all the buttons and then it is the current situation that I have although I put port 10 the adb does not detect the phone
Axon tool kits in this state also does not detect it ,and my flash is left empty list does not appear the phone
mi model of phone is ztea2017 (version china)
That is my current situation. so you recommend to me using the 4 category to repair a brick?
Or recommend me other steps
Click to expand...
Click to collapse
Para hacertela mas facil: Necesitas usar la guia '4th category brick repair manual' (googleala, esta en XDA) pero empezando desde la parte que entran en modo EDL. Necesitas tener los drivers de Qualcomm para eso, asi que no los desinstales.

Choose an username... said:
Para hacertela mas facil: Necesitas usar la guia '4th category brick repair manual' (googleala, esta en XDA) pero empezando desde la parte que entran en modo EDL. Necesitas tener los drivers de Qualcomm para eso, asi que no los desinstales.
Click to expand...
Click to collapse
muchas gracias, si ya tenia esa pagina en favoritos, pero la tenia en plan ultimo recurso, no quería abrir si no era estrictamente necesario. tampoco quería hablar en español por si no se podia o alguien mas esta en este punto de error y respecto a mi ingles le tengo un poco oxidado y todo lo que escribo lo compruebo con el google translator por eso se copio dos veces.
una duda que me dejas con tu ultimo comentario lo voy a poner en ingles también para ayudar a gente que le pase igual.por eso lo leeras dos veces. cuando te refieres que empiece desde la parte de entrar en modo edl no te entiendo, porque segun el tutorial hay que abrir conectar el cable.... IN ENGLISH DOWN
1. Connect original USB Type-C cable to the phone.
2. Circtuit Test-point on the housing (there is sim-cards slot body nearby).
3. Connect USB cable to PC USB-port (preferably USB 2.0 version).
4. You will hear the USB device connection sound from PC (but you will not notice any vibration of the phone or red diode indicator blinking).
estos puntos ninguno pone mode edl no ? os me estoy saltando algun paso que no veo.
ENGLISH
A doubt that you leave me with your last comment I 'm going to put in English also to help people that happens to him equal. When you mean start from the part of entering edl mode I don't understand you, because according to the tutorial you have to open connect the cable not entering edl mode i'm forgetting some step ??

On your second pic, that is already in edl mode.
Try to enter that mode again by pressing all the buttons and make to the computer detect it as 9008. Once it is already in 9008, here's what you do:
1. Open the folder where you have the axon7root.exe.
2. Delete/rename or move the files "boot.img and recovery.img".
3. Rename the files "stock_boot_backup.img" to "boot.img". Do the same for recovery.img
4. Issue this command: "axon7root.exe -p COM10 -b -r"
Be sure it's COM10 in device manager. Else, try puting it in another usb slot and enter what port it is there.
That will restore your original boot and recovery.
If you still can't recover from that, install Teamviewer on your PC and let me access it remotely. That is if we can find a time convenient for us since we're not in the same timezone.
---------- Post added at 01:12 AM ---------- Previous post was at 12:30 AM ----------
Try also this method to restore.
https://forum.xda-developers.com/showpost.php?p=73449127&postcount=1

otaconremo said:
On your second pic, that is already in edl mode.
Try to enter that mode again by pressing all the buttons and make to the computer detect it as 9008. Once it is already in 9008, here's what you do:
1. Open the folder where you have the axon7root.exe.
2. Delete/rename or move the files "boot.img and recovery.img".
3. Rename the files "stock_boot_backup.img" to "boot.img". Do the same for recovery.img
4. Issue this command: "axon7root.exe -p COM10 -b -r"
Be sure it's COM10 in device manager. Else, try puting it in another usb slot and enter what port it is there.
That will restore your original boot and recovery.
If you still can't recover from that, install Teamviewer on your PC and let me access it remotely. That is if we can find a time convenient for us since we're not in the same timezone.
---------- Post added at 01:12 AM ---------- Previous post was at 12:30 AM ----------
Try also this method to restore.
https://forum.xda-developers.com/showpost.php?p=73449127&postcount=1
Click to expand...
Click to collapse
yes in the second pictures looks like alreday
If but the same explain me wrong in the second image seems to be in edl mode but does not detect it (install the drivers manually from the disk choosing that option ... ponia qusb_bulk and I manually update the driver series to that particular Prque knew it was the right one so now I dial that when I connect it stays on black screen after pressing the 3 buttons at a time and quickly connect the usb cable (if I do not this does not appear so when I enter the command screen Of amb and put the third image does not detect devices and does not recognize it even putting port 10 attached screenshot of the test ...
I suppose that only left to make option category brick 4

VIFTOKSKY said:
yes in the second pictures looks like alreday
If but the same explain me wrong in the second image seems to be in edl mode but does not detect it (install the drivers manually from the disk choosing that option ... ponia qusb_bulk and I manually update the driver series to that particular Prque knew it was the right one so now I dial that when I connect it stays on black screen after pressing the 3 buttons at a time and quickly connect the usb cable (if I do not this does not appear so when I enter the command screen Of amb and put the third image does not detect devices and does not recognize it even putting port 10 attached screenshot of the test ...
I suppose that only left to make option category brick 4
Click to expand...
Click to collapse
En la guia el celular esta brickeado de una manera que no se puede entrar al modo EDL. Se supone que podes entrar al modo si mantenes apretadas las dos teclas de volumen, y metes el cable USB-C al celular (tiene que estar conectado a la computadora). Desde ahi tenes EDL si no tiene un DFU brick (tendrias que desarmarlo). En la guia haces corto en un pad de cobre para entrar en EDL, pero podes meterte al EDL de manera que te salga el driver de Qualcomm en la PC y seguir con la guia despues de lo que copiaste. Lo de despues debe ser seleccionar la carpeta y flashear con MiFlash me imagino

Huawei P9 Lite (2017) Stuck at Your device is booting now

HI i have a Huawei P9 Lite (2017)
Model: PRA-LX1
Its stuck at the your device has been unlocked and cant be... To learn visit.. Your device is booting now...
Can any one help me?
Or give me the stock firmware(update.app) for PRA-LX1.
Please help.

What tutorial did you use to unlock your bootloader?
What did you do exactly?

just re flash your stock rom by dload using three buttons method

Arsaam said:
just re flash your stock rom by dload using three buttons method
Click to expand...
Click to collapse
I am having the same issue, and absolutely NO combination of power/vol buttons changes the outcome....still just boots to that message. (Nova (P8) lite PRA-LX2 Telkom)
After clicking on an infected MMS (yes, hindsight is wonderful), the phone display started scrambling and turned off (3 days ago). After that, it wouldn't boot up. I have spent the past 3 days working to get it going. Managed to connect to ADB, then scoured the web looking for the correct firmware package. I managed to get a boot.img recovery.img and system.img that would flash but ZERO cust.img files flash. All of these failed with various flashing error messages. Last night, just before this happened, after flashing the above PLUS a TWRP.img file I found, the phone rebooted to the usual splash animation but then went to bootloop to the splash.
I thought "YES....progress!"
Then thru ADB again, I tried to flash a different CUST.img I found and after reboot got stuck at "your device is booting now".......
No recognition in adb....no change is bootup (even with any update.app and au_temp.cfg loaded on sd card)
So.....no, no buttons working, no D/L mode, no fastboot..........nada
Any other assistance would REALLY REALLY be appreciated
Thanks
---------- Post added at 10:23 AM ---------- Previous post was at 09:45 AM ----------
**UPDATE**
After leaving the device on until the battery ran out I pressed the vol up/down and power I rebooted till the very last drop of juice. Then when it had nothing left in the tank I plugged in the charger (not connected to the laptop) and simultaneously pressed all buttons....and it booted up into eRecovery (which incidentally is USELESS), but at least now I can keep trying to flash roms until one day (hopefully before the end of days) I find one that works......

your device is booting now
hola tengo el mismo problema, el telefono queda en "Your device is booting now" y no funcina ninguna combinacion de botones, mejor dicho, haga lo que haga, siempre termina en esa pantalla y el problema mayor es que la PC no lo reconoce, lo conecto a la pc y no aparece conectado.
por favor si alguien sabe de que manera reparar el sistema.
gracias
hello sorry my english is not good I have the same problem, the phone is in "Your device is booting now" and it does not work any combination of buttons, that is to say, whatever it does, it always ends in that screen and the biggest problem is that the PC does not recognize it, I connect to the pc and it does not appear connected.
please if anyone knows how to repair the system.
Thank you

juanchocapital said:
hola tengo el mismo problema, el telefono queda en "Your device is booting now" y no funcina ninguna combinacion de botones, mejor dicho, haga lo que haga, siempre termina en esa pantalla y el problema mayor es que la PC no lo reconoce, lo conecto a la pc y no aparece conectado.
por favor si alguien sabe de que manera reparar el sistema.
gracias
hello sorry my english is not good I have the same problem, the phone is in "Your device is booting now" and it does not work any combination of buttons, that is to say, whatever it does, it always ends in that screen and the biggest problem is that the PC does not recognize it, I connect to the pc and it does not appear connected.
please if anyone knows how to repair the system.
Thank you
Click to expand...
Click to collapse
Hello,
One solution that should work: Leave the phone until it discharge completely, then keep pressing the volume down button then plug the phone in pc (while you are pushing the volume down button). This will boot the phone in fastboot mode. Right then you can flash the recovery with stock recovery or with TWRP (TWRP 3.1.1 should work)
BR,
Alaa.

[SOLVED] Need help with fixing unknown model in LGUP

I flashed the Fulmics ROM on my G6 and could not go back to stock using LGUP. Under Model and Port it shows "Unknown" and "Com 5, Fulmics" preventing me from proceeding.
I, however, managed to flash the stock rom from a zip provided in one of the threads. Still when I connect the phone to computer, LGUP says "Unknown" and "Com 5, Fulmics".
How can I fix this so that I can use LGUP again? (I also tried the Flashtool with no success)
Thanks

Go to
Code:
C:\Program Files (x86)\LG Electronics\LGUP\model\common
paste this file there https://drive.google.com/open?id=0B8K3M8fXJmgzX1hMNTBkZ3p2M1E

Did that before. Didn't make a difference.

backslashV said:
Did that before. Didn't make a difference.
Click to expand...
Click to collapse
Did you install the drivers properly and have you tried using a different USB?

Mavelos said:
Did you install the drivers properly and have you tried using a different USB?
Click to expand...
Click to collapse
Yes. I even tried another computer. It appears that something about this Fulmics rom is hard coded into the phone. The developer of the rom isn't responding so I don't know what else to do.

backslashV said:
Yes. I even tried another computer. It appears that something about this Fulmics rom is hard coded into the phone. The developer of the rom isn't responding so I don't know what else to do.
Click to expand...
Click to collapse
Well, I use Fulmics also and i can say nothing is hardcoded. When you connect your G6, check the device manager on your PC to be sure your phone is detected.

Mavelos said:
Well, I use Fulmics also and i can say nothing is hardcoded. When you connect your G6, check the device manager on your PC to be sure your phone is detected.
Click to expand...
Click to collapse
It is detected. I even tried changing the com port but nothing happened. So when you connect your phone to pc in download mode LGUP recognizes it?

backslashV said:
It is detected. I even tried changing the com port but nothing happened. So when you connect your phone to pc in download mode LGUP recognizes it?
Click to expand...
Click to collapse
yes it does. Have you used LGUP before?

Yes I have. I used it to go back to stock from lineage os.

Good news. I found this guide and it did the trick:
https://forum.xda-developers.com/showthread.php?t=3565508

backslashV said:
Good news. I found this guide and it did the trick:
https://forum.xda-developers.com/showthread.php?t=3565508
Click to expand...
Click to collapse
Hi, how do you solve this issue?
i face same problem.
i even cannot tun off the G6 and cannot enter download mode
when i connect my G6 to PC via uppercut, it says unkonown model and i cannot go on the process.
in the link you put above. we have to enter download mode. how do you do that?
thanks

Just hold volume down and power button at same time to power off.
Sent from my LG-H870 using Tapatalk

i have a same problem with my LG Aristo 2
necesito el dll para flashear Lg Aristo 2 (LM-X210MA)

@ade_k012 I have exactly the same problem you just described. Were you able to resolve?

Yes i have solved it and i can update my g6 to the firmware i want. But sorry, i forgot the steps. It was quite long time ago..

Hola yo lo resolvi usando este tutorial
en el ultimo paso donde tienen que crear el common ddl, no lo hagan, solo descarguen el archivo ddl que proporcionan al principio de este post y lo pegan en la ruta especificada. Lo probe en mi lg h873 y funciono perfecto pude flashear y desbriquear mi telefono que se quedaba en el logo de lg