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

[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

[SOLVED*] POCO M3 stuck in EDL (No Fastboot, No Recovery)

――――――――――――――――――――――――――――​My Case | The Beginning (November 18, 2021):​――――――――――――――――――――――――――――​
A while ago I unlocked Bootloader from my POCO M3 European [EU] [citrus] and downgraded MIUI (12.5.2.0 to 12.0.3.0) because the update had made the experience worse in several things. I managed to do this and used my POCO for several weeks normally. This week I simply had to Restart the device, and then it didn't turn on anymore. There have been no updates applied, I have not confirmed this. He died and when connecting to the Computer I noticed that he was in EDL Mode (Qualcomm HS-USB QDLoader 9008). From there, after tirelessly searching forums and countless websites, I did this:​
I found the POCO M3 Engineering ROM and through the Firehose File that came in it I managed to bypass Xiaomi's EDL Authentication. I used this Firehose in the Original ROM and managed to install it normally.
I installed the engineering version, I also tried the Original version 12.0.3.0 (oldest 12.0) and also the Original version 12.0.11.0 (latest 12.0), but after successful installation the device wouldn't reboot (stuck in the EDL). [Note: with this method I installed using MiFlash and sometimes I also used QFIL, but the result was exactly the same]. If I used the Power and Volume buttons (different combinations) the device would restart but immediately return to the EDL.
I let the battery completely discharge and the next day I plugged the USB cable into the Computer (and the POCO) and this time it showed the charging icon (battery empty), and a few minutes later the screen turned on by itself (showing the POCO symbol ) and the battery icon appeared "1%" (charging). And so Windows recognized the device as "Linux File-Stor Gadget USB Device" (in MiFlash it was recognized as "c12feb2e0720 device").
With high hopes, I opened the Command Prompt and tried to communicate with POCO through Fastboot and ADB, but both didn't see any devices (fastboot devices | adb devices) and that made any command impossible.
I tried to flash the Original ROMs again (using MiFlash), taking advantage of this "Strange Mode", but it didn't work, because in the first command the software didn't get a response from the device.
I noticed (by the MiFlash verbose) that the flash command was started with "fastboot -s c12feb2e0720...", so to access the device it would be necessary to specify where it was. Unfortunately, using the Command Prompt (as well as MiFlash), I was not successful, as in both cases the device did not "answer/return" anything.
Click to expand...
Click to collapse
―――――――――――――――――​Workarounds (Jun 02, 2022):​―――――――――――――――――​If your device is under warranty, use it for Xiaomi to repair it. If this is not your case, I have two alternatives that worked for me (the second is the one I use repeatedly with success).
Fully discharge the battery
My device was 11% charged and I simply disconnected the battery cable from the device (manually) and waited for a many hours (If your device is heavily charged, you may need to wait for days for the battery to fully discharge). After reconnecting the battery and pressing the Power button (no USB Cable Connected) the POCO started normally.
Click to expand...
Click to collapse
Heating the Motherboard
Some time later I had to restart my POCO, but I knew that this would cause the "EDL Stuck Mode". Then I found that overheating a specific part of the Motherboard forced POCO out of EDL Mode and allowed the system to boot. From there, I disassembled my device (the SIMCard/SD Slot, the plastic cover and the protection above the cameras, that order), disconnected the wires that were attached to the motherboard (including fingerprint connector), and removed it. So, I turned it upside down and used a soldering iron to overheat a specific part for 5 minutes (the specific part is in this image). After those minutes, I reconnected everything and simply pressed the Power button, and POCO turned on normally.​
Click to expand...
Click to collapse
*Note1: Make sure all connectors are properly plugged into the motherboard. Otherwise, Poco will not recognize the fingerprint or some other component.
*Note2: In my case, the 'procedure 2' needs to be used EVERY TIME I need to RESTART my device. And it also serves to apply OTA updates. {For example: when the update appears, confirm it. After it downloads, confirm to apply as normal. The phone will restart and get stuck in the EDL. Then use the above overheat procedure to turn on the device, and during the boot process the update will be applied.}​―――――――――――――――――――――――――――――――――​Flashing the MIUI ROM on EDL (with EDL Auth Bypass)​―――――――――――――――――――――――――――――――――​
The safest way is using "MiFlash". Before starting, download the following files:
- Qualcomm HS-USB Driver (64bit) or Qualcomm HS-USB Driver (32bit)​- MIUI ROM (Fastboot version) (select your device variant: EEA/RU/Global/IN, etc...)
- MiFlash (Xiaomi Flash Tool)
- Firehose File (Bypass EDL Auth)
​
Install the Qualcomm Driver (if I haven't done so), restart the computer; connect your POCO and open Windows Device Manager (shortcut: Windows + X). In the "Serial Port" category, make sure your POCO (EDL Mode) appears as "Qualcomm HS-USB...". If yes, all right. Else, check that the drivers were installed correctly (no exclamation marks) or if your device is being recognized in another mode (ADB or Fastboot). If so, it will show up as "Android ADB Interface" or something similar, and that means your device is not in EDL (This is great news, so continue the tutorial as MiFlash will be able to flash the ROM in the alternate mode of your device. If you can't, let me know.).​
Unzip the MIUI ROM until it becomes a folder. Inside the created folder, open the "images" folder and replace the downloaded "Firehose (Bypass EDL)" file with the one in the folder.​
Run MiFlash, click "Refresh" and make sure your device appears in the device list. If yes, click "Select" and check the MIUI ROM folder (not the "images" folder).​
Click on Flash and wait for the process to complete (the word "success" in green will appear).​
Important: If your device is in EDL Mode, flash will delete all files on your device. But if the device is in ADB or Fastboot Mode, you can flash without erasing your files. Just look at the bottom of MiFlash and click "Save User Data". This script is expected to work.
Click to expand...
Click to collapse
​Hope this helps someone

man i have the same problem i can not let thah my phone discharged
its a shame of xiaomi

etvtaglios said:
man i have the same problem i can not let thah my phone discharged
its a shame of xiaomi
Click to expand...
Click to collapse
Sorry, I didn't understand you well :s
Did you mean that if your phone discharges (turns off) it goes into EDL mode?

yes dont turn on again I have to disconnect the battery again for me it's a really it's a deception this poco was a really decent option

etvtaglios said:
yes dont turn on again I have to disconnect the battery again for me it's a really it's a deception this poco was a really decent option
Click to expand...
Click to collapse
Absolutely! Poco is a very good alternative. Too bad the support sucks :/
I don't know how I'm going to solve this problem. I already installed MIUI version 12.0.3.0 as it is the oldest available, but the problem persists. I don't want to lock the Bootloader (it's open) as I worry if the device dies and I can't flash the system again.

can you make a video please! you can save us i guess

Jamder said:
can you make a video please! you can save us i guess
Click to expand...
Click to collapse
I'm getting ready to do this. But meanwhile, tell me what your question is, I can help you.

My question is any permanent fix for this particular problem?
I'm considering buying this phone

Ozemir Elion said:
I'm getting ready to do this. But meanwhile, tell me what your question is, I can help you.
Click to expand...
Click to collapse

I have a question , if you were to try and update your M3 that has the deadboot issue , would it fail all the time? Because we can't reboot the phone or power it off without it going into deadboot. Can we still access recovery?

ultimatelegend1 said:
I have a question , if you were to try and update your M3 that has the deadboot issue , would it fail all the time? Because we can't reboot the phone or power it off without it going into deadboot. Can we still access recovery?
Click to expand...
Click to collapse
Good question! I'm looking forward to updating the MIUI version, but I'm sure the M3 will go into deadboot. About Recovery/Fastboot I can't access it, but right now I'm doing some tests to make sure I can access it.

ultimatelegend1 said:
I have a question , if you were to try and update your M3 that has the deadboot issue , would it fail all the time? Because we can't reboot the phone or power it off without it going into deadboot. Can we still access recovery?
Click to expand...
Click to collapse
I tried to restart the M3 using ADB on Windows (adb reboot recovery) with USB Debugging but the device went into deadboot, unfortunately. So far I haven't found any solution to update the device other than Flashing via EDL (Xiaomi Mi Tool), replacing the "firehose" file in the ROM folder.

Ozemir Elion said:
Hace un tiempo desbloqueé Bootloader de mi POCO M3 European [EU] [citrus] y bajé MIUI ( 12.5.2.0 a 12.0.3.0 ) porque la actualización había empeorado la experiencia en varias cosas. Logré hacer esto y usé mi POCO durante varias semanas normalmente.
Esta semana simplemente tuve que reiniciar el dispositivo y luego ya no se encendió. No se han aplicado actualizaciones, no lo he confirmado. Murió y al conectarme a la computadora noté que estaba en modo EDL ( Qualcomm HS-USB QDLoader 9008 ). A partir de ahí, después de buscar incansablemente en foros e innumerables sitios web, hice esto:
Encontré la ROM de ingeniería POCO M3 y, a través del archivo Firehose que venía, logré omitir la autenticación EDL de Xiaomi. Usé este Firehose en la ROM original y logré instalarlo normalmente.
Instalé la versión de ingeniería , también probé la versión original 12.0.3.0 (la más antigua 12.0) y también la versión original 12.0.11.0 (la última 12.0), pero después de una instalación exitosa, el dispositivo no se reiniciaba (atascado en la EDL). [Nota: con este método lo instalé usando MiFlash ya veces también usé QFIL , pero el resultado fue exactamente el mismo]. Si usaba los botones de Encendido y Volumen (diferentes combinaciones), el dispositivo se reiniciaba pero regresaba inmediatamente a la EDL.
Dejé que la batería se descargara por completo y al día siguiente enchufé el cable USB a la Computadora (y al POCO) y esta vez mostró el ícono de carga (batería descargada), y unos minutos después la pantalla se encendió sola (mostrando la Símbolo POCO) y el icono de la batería apareció "1%" (cargando). Y así, Windows reconoció el dispositivo como " Dispositivo USB File-Stor Gadget de Linux " (en MiFlash se reconoció como " dispositivo c12feb2e0720 ").
Con muchas esperanzas, abrí el símbolo del sistema e intenté comunicarme con POCO a través de Fastboot y ADB, pero ninguno de los dos vio ningún dispositivo ( dispositivos fastboot | dispositivos adb ) y eso hizo que cualquier comando fuera imposible.
Intenté flashear las ROM originales nuevamente (usando MiFlash), aprovechando este "Modo extraño", pero no funcionó, porque en el primer comando el software no obtuvo respuesta del dispositivo.
Noté (por el detallado MiFlash ) que el comando flash se inició con " fastboot -s c12feb2e0720 ... ", por lo que para acceder al dispositivo sería necesario especificar dónde estaba. Desafortunadamente, al usar el símbolo del sistema (así como MiFlash), no tuve éxito, ya que en ambos casos el dispositivo no "respondió / devolvió" nada.
Hasta ahora, estos son los avances que he logrado para eliminar los ladrillos de mi POCO M3, pero no sé qué hacer. Seguro que si consigo resucitar mi dispositivo haré un tutorial para ayudar a otras personas, porque esta situación es terrible.
_______________________________________________________
¡YO LO RESUELTO! Después de todo lo que hice anteriormente (el dispositivo estaba cargado al 11%), simplemente desconecté la batería del dispositivo y lo dejé durante unos minutos (sin batería conectada). Después de volver a conectar la batería y presionar el botón de encendido (sin cable USB conectado), el POCO se inició normalmente .
Espero que esto ayude a alguien
* Nota: Estoy usando MIUI 12.0.3.0 (UE, es posible una versión anterior de fastboot) y no quiero actualizar. Para propósitos de prueba, reinicié el dispositivo y confirmé: Se atasca nuevamente en la EDL . Pero simplemente desconecto la batería durante al menos 5 minutos, la vuelvo a conectar y enciendo el dispositivo normalmente, y puedo usar mi Poco . La única pregunta principal ahora es: ¿cómo puedo reiniciar / apagar el dispositivo normalmente sin quedar atascado en la EDL? ¿Cualquier sugerencia?​Si te ayudaron con esta publicación, comenta.
Click to expand...
Click to collapse
Hi, I have the same problem, I followed your steps, I flashed several ROM'S but nothing so I tried version 12.0.3.0 and I think it worked, I left it connected to the PC, after having flashed the ROM, but I fell asleep when I woke up, I tried to turn it on and the battery appeared, it gave me a life expectancy! immediately connect it to the power and yes! "1%" appeared from there the LOGO OF POCO, but from there he did nothing more ... he stayed in EDL again: c I don't know what to do ...

Jonathan RdGz said:
Hi, I have the same problem, I followed your steps, I flashed several ROM'S but nothing so I tried version 12.0.3.0 and I think it worked, I left it connected to the PC, after having flashed the ROM, but I fell asleep when I woke up, I tried to turn it on and the battery appeared, it gave me a life expectancy! immediately connect it to the power and yes! "1%" appeared from there the LOGO OF POCO, but from there he did nothing more ... he stayed in EDL again: c I don't know what to do ...
Click to expand...
Click to collapse
You must flash the MIUI of the same version as your phone (eg: Europe, Global, Russian,...). The Flash process must be done in EDL mode, using Xiaomi Flash Tool (Mi Flash). In my case it was the "QJFEUXM" ROM.
After the flash, just follow the same battery disconnect procedure you did.

Ozemir Elion said:
A while ago I unlocked Bootloader from my POCO M3 European [EU] [citrus] and downgraded MIUI (12.5.2.0 to 12.0.3.0) because the update had made the experience worse in several things. I managed to do this and used my POCO for several weeks normally.
This week I simply had to Restart the device, and then it didn't turn on anymore. There have been no updates applied, I have not confirmed this. He died and when connecting to the Computer I noticed that he was in EDL Mode (Qualcomm HS-USB QDLoader 9008). From there, after tirelessly searching forums and countless websites, I did this:
I found the POCO M3 Engineering ROM and through the Firehose File that came in it I managed to bypass Xiaomi's EDL Authentication. I used this Firehose in the Original ROM and managed to install it normally.
I installed the engineering version, I also tried the Original version 12.0.3.0 (oldest 12.0) and also the Original version 12.0.11.0 (latest 12.0), but after successful installation the device wouldn't reboot (stuck in the EDL). [Note: with this method I installed using MiFlash and sometimes I also used QFIL, but the result was exactly the same]. If I used the Power and Volume buttons (different combinations) the device would restart but immediately return to the EDL.
I let the battery completely discharge and the next day I plugged the USB cable into the Computer (and the POCO) and this time it showed the charging icon (battery empty), and a few minutes later the screen turned on by itself (showing the POCO symbol ) and the battery icon appeared "1%" (charging). And so Windows recognized the device as "Linux File-Stor Gadget USB Device" (in MiFlash it was recognized as "c12feb2e0720 device").
With high hopes, I opened the Command Prompt and tried to communicate with POCO through Fastboot and ADB, but both didn't see any devices (fastboot devices | adb devices) and that made any command impossible.
I tried to flash the Original ROMs again (using MiFlash), taking advantage of this "Strange Mode", but it didn't work, because in the first command the software didn't get a response from the device.
I noticed (by the MiFlash verbose) that the flash command was started with "fastboot -s c12feb2e0720...", so to access the device it would be necessary to specify where it was. Unfortunately, using the Command Prompt (as well as MiFlash), I was not successful, as in both cases the device did not "answer/return" anything.
So far these are the progress I've made to Debricking my POCO M3, but I don't know what to do. Surely if I manage to resurrect my device I will make a tutorial to help other people, because this situation is terrible.
_______________________________________________________
I SOLVE IT! After everything I did above (the device was 11% charged) I simply disconnected the battery from the device and left it for a few minutes (no battery connected). After reconnecting the battery and pressing the Power button (no USB Cable Connected) the POCO started normally.
Hope this helps someone
*Note: I'm using MIUI 12.0.3.0 (EU, older fastboot version possible) and I don't want to update. For Testing purposes, I restarted the device and confirmed: It gets stuck in the EDL again. But I just disconnect the battery for at least 5 minutes, reconnect it and turn on the device normally, and i can use my Poco. The only main question now is: how can I restart/shutdown the device normally without getting stuck in the EDL? Any suggestion?​If you were helped with this post, comment.
Click to expand...
Click to collapse
Many thanks for the link to POCO M3 Engineering ROM, it solved everything with my phone, I was in EDL mode and after installing, reinstalling and modifying the phone is like new, I also repaired another phone.

rotoko said:
Many thanks for the link to POCO M3 Engineering ROM, it solved everything with my phone, I was in EDL mode and after installing, reinstalling and modifying the phone is like new, I also repaired another phone.
Click to expand...
Click to collapse
Glad it worked out for you!
But I have a doubt: you said that the cell phone "was like new" after (...) modifications.
1. Does it mean you can restart your phone normally without getting stuck in EDL?
2. What changes did you make?
These answers can help everyone who is experiencing the problem.

Ozemir Elion said:
Glad it worked out for you!
But I have a doubt: you said that the cell phone "was like new" after (...) modifications.
1. Does it mean you can restart your phone normally without getting stuck in EDL?
2. What changes did you make?
These answers can help everyone who is experiencing the problem.
Click to expand...
Click to collapse
I have restarted the mobile phone many times after the repair, when installing the rom and the applications works perfectly.
After flashing via Flashtool, I immediately installed TWRP via Fastboot and installed Miu 12.5.3.

rotoko said:
I have restarted the mobile phone many times after the repair, when installing the rom and the applications works perfectly.
After flashing via Flashtool, I immediately installed TWRP via Fastboot and installed Miu 12.5.3.
Click to expand...
Click to collapse
It really is a very interesting situation. In my case, ever since I got stuck in EDL for the first time I was never able to restart the phone again. Despite installing the Engineering ROM, the device can no longer access Fastboot Mode or Recovery Mode. The only thing I can boot is the System, and if I restart the phone I will need to open it and heat up a point on the Motherboard so that it exits EDL and boots normally.
My device is an EU version, and this week I installed the MIUI version 12.5.5 (Global) via EDL (with a Fastboot ROM) as it is the only method I can flash...

Ozemir Elion said:
It really is a very interesting situation. In my case, ever since I got stuck in EDL for the first time I was never able to restart the phone again. Despite installing the Engineering ROM, the device can no longer access Fastboot Mode or Recovery Mode. The only thing I can boot is the System, and if I restart the phone I will need to open it and heat up a point on the Motherboard so that it exits EDL and boots normally.
My device is an EU version, and this week I installed the MIUI version 12.5.5 (Global) via EDL (with a Fastboot ROM) as it is the only method I can flash...
Click to expand...
Click to collapse
Interestingly, my cell phone got into the bootlop by installing the wrong Rom, when it couldn't, just boot through EDL by connecting two points, it didn't seem logical for me to fix it by discharging the battery or destroying components by heating.
I used a modified MIFLASH DRIVER, Qualcomm HS-USB QDLoader 9008 and POCO M3 Engineering ROM. Also when repairing another mobile phone.
The phones are working perfectly so far.

rotoko said:
Interestingly, my cell phone got into the bootlop by installing the wrong Rom, when it couldn't, just boot through EDL by connecting two points, it didn't seem logical for me to fix it by discharging the battery or destroying components by heating.
I used a modified MIFLASH DRIVER, Qualcomm HS-USB QDLoader 9008 and POCO M3 Engineering ROM. Also when repairing another mobile phone.
The phones are working perfectly so far.
Click to expand...
Click to collapse
Got it! Do you know what modification was made to the Driver?
And from what I understand, you weren't exactly stuck in EDL, you were actually in Bootloop. That's right?