You may remove the shield that is shorting a cap. Take a look here:
I did that. Removed the shield and then heated the IC.You may remove the shield that is shorting a cap. Take a look here:
I recently updated my Poco M3, it updated correctly but after that, it doesn't turn on anymore, I searched about it and I found that it was a problem with the update. I managed to turn on my phone again by pressing 13 seconds the power button...forum.xda-developers.com
My M3 was working perfectly. I put it to restart and then it didn't turn on anymore. It is now only recognized as "Qualcomm HS-USB QDLoader 9008" on Windows. I opened the phone and with some magical combination (remove/connect flat cables from the battery and display, connect the USB cable, press volume keys and short the test points) it started in fastboot. So I was able to flash the "fastboot ROM". Unfortunately, on the next boot it still does not turn on normally. Has anyone succeeded in repairing the Poco M3? In Mi Flash is requested an authenticated account to flash through it, is it worth paying someone to provide the account? Does anyone have the contact of someone who makes cheap? Any help is welcome, thank you!
I don't know what IC you mean. For me it was enough just to remove the shield.
That isn't a fix, only a workarround in order to power on the phone.The solution:
1- Simply disconnect the battery and the flex from the screen then reconnect them.
2- Now leave it like this for 8 days until the battery is completely drained (you should not do anything else, it will discharge itself)
3- After 8 days connect it to the original charger and let it charge for 5 minutes, without disconnecting the charger, click the power button and it should turn on normally as if nothing had happened; I know it seems like something funny or stupid, but that method worked for me, maybe it was luck, I don't know, I had been battling a solution for 3 months, I just wanted to eagerly share this solution before they damage their cell phones by doing experiments with their motherboards. I wish you luck.
Note 2: the phone was only uncovered to release the battery and screen flex, nothing more for that ok
tu metdo funciona pero hay problemas con esa actualizacionChicos, este es mi procedimiento para encender el teléfono:
Puedo hacer que encienda Android después de jugar con la batería y los cables de la placa secundaria, pero esto es solo un truco, tratar de encenderlo normalmente a través del botón de encendido siempre hace que se encienda en modo edl
Pero abrir el dispositivo anula la garantía, por lo que es mejor que cualquier persona que tenga acceso a un centro de reparación solicite la garantía.
1. Desconecte el cable de la batería y el cable de la placa secundaria.
2. Conecte el cargador.
3. Mantenga presionado el botón de encendido.
4. Conecte el cable de la placa secundaria y conecte rápidamente el cable de la batería.
5. Suelte el botón de encendido cuando el dispositivo vibre.
No siempre funciona la primera vez, es posible que necesite varios intentos para conseguirlo.
[URL unfurl = "true"] https://drive.google.com/file/d/12OfCPzS2tSLr6uQ7BIp8x3_4gz2fYBnF/view?usp=drivesdk [/ URL]
heyyy can u help me with my device?Guys this is my procedure to turn on the phone:
I can make it turn on Android after messing with the battery and sub-board cables but this is just a workahound, trying to turn it on normally through the power button always makes it turn on in edl mode
But opening the device voids the warranty, so anyone who has access to a repair center is better off asking for the warranty
What to do:
1. Disconnect the battery cable and the secondary board cable.
2. Connect charger.
3. Hold the power button.
4. Connect the secondary board cable and quickly connect the battery cable.
5. Release the power button when the device vibrates.
It doesn't always work the first time, you may need several tries to get it
no pmic also motherboard is healthy do not attack your MB. )
This problem started to happen to me while I was running Crdroid. A couple of weeks earlier when it was still in the stock ROM I had installed update 12.0.8. Install custom ROM does not solve the problem. Although it appears to be an issue created by an update, it's not simply a software issue, it's a problem that was bound to happen. If that weren't so, Poco's repair centers would only be repairing the system of the devices that arrive there and not entirely replacing the main board. I also have a suspicion that this issue is happening with a specific manufacturing batch. Mine and those of people I know with the same problem were manufactured in 2020.11. I would like everyone here with this problem to say the date of manufacture of your M3, you can read this information on the box.