Database Users

Completely dead P9 lite

So it looks like this phone is not completely unbrickable. I've seem to brick mine pretty bad.
The phone doesn't turn on at all. No vibration or other kind of feedback.
Doesn't appear on the computer either.
So my question is: is there any emergency download mode like in qualcomm based phones?

randhackr said:
So it looks like this phone is not completely unbrickable. I've seem to brick mine pretty bad.
The phone doesn't turn on at all. No vibration or other kind of feedback.
Doesn't appear on the computer either.
So my question is: is there any emergency download mode like in qualcomm based phones?
Click to expand...
Click to collapse
I don't know about it.

michal383 said:
I don't know about it.
Click to expand...
Click to collapse
It seems completely dead. Probably only with test point. Warranty most likely will refuse it since it is boot loader unlocked.

randhackr said:
It seems completely dead. Probably only with test point. Warranty most likely will refuse it since it is boot loader unlocked.
Click to expand...
Click to collapse
Yes Warranty falls if the bootloader unlocked. Test Point could help.

Well warranty will most likely only complain if it was bricked by the user and software modification.
If your phone broke because of an hardware issue, you have a chance that warranty still repairs it for free.

Schlengge said:
Well warranty will most likely only complain if it was bricked by the user and software modification.
If your phone broke because of an hardware issue, you have a chance that warranty still repairs it for free.
Click to expand...
Click to collapse
Well since it broke after I flashed b160 firmware I am most likely SOL. Since I had twrp flashed they will find out that it was modified..
My advice is not to mess with fastboot mode. Flash twrp and be careful with what you flash.

Did you tried to flash original firmware with the three buttons?
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app

Potato997 said:
Did you tried to flash original firmware with the three buttons?
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yup. It's completely dead. No fastboot mode, no recovery or erecovery. It simply does not turn on (or enumerate in a computer either).

If you could boot into recovery,the rest would be simple....download the stock firmware, unzip it and push the file to your phone,then install

LiaquateRahiman said:
If you could boot into recovery,the rest would be simple....download the stock firmware, unzip it and push the file to your phone,then install
Click to expand...
Click to collapse
He can't enter in recovery or fastboot.

Potato997 said:
He can't enter in recovery or fastboot.
Click to expand...
Click to collapse
Have you tried to enter fastboot or recovery solely using the button combos? or did you try using adb as well? It's possible your battery deep-discharged, or your power adapter/connectors are faulty.

Potato997 said:
He can't enter in recovery or fastboot.
Click to expand...
Click to collapse
Yes I cant enter anything in fact. There was a suggestion to connect the phone without battery to the computer but it implies opening up the phone and even if it did something I don't have the tools to flash it. (dc-phoenix only seems to work with phones with fastboot working)
As far as I know the symptoms that my phone is experiencing are due to the fastboot partition being messed up.
As far I was able to research there is another boot loader before the fastboot one. But the phone doesn't respond at all, it is dead. I will ask around in phone repair shops if they can reflash the phone.

randhackr said:
Yes I cant enter anything in fact. There was a suggestion to connect the phone without battery to the computer but it implies opening up the phone and even if it did something I don't have the tools to flash it. (dc-phoenix only seems to work with phones with fastboot working)
As far as I know the symptoms that my phone is experiencing are due to the fastboot partition being messed up.
As far I was able to research there is another boot loader before the fastboot one. But the phone doesn't respond at all, it is dead. I will ask around in phone repair shops if they can reflash the phone.
Click to expand...
Click to collapse
Before you do anything rash, have you considered getting a usb jig? Simply put the stock firmware on the jig then plug it into the usb port on your phone. It will automatically put your phone into download mode and install the firmware. Here's the link to make your own usb jig http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707. Hopefully this helps!!!

LiaquateRahiman said:
Before you do anything rash, have you considered getting a usb jig? Simply put the stock firmware on the jig then plug it into the usb port on your phone. It will automatically put your phone into download mode and install the firmware. Here's the link to make your own usb jig http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707. Hopefully this helps!!!
Click to expand...
Click to collapse
That is for samsung phones. I gave on trying to fix the phone. Next week I'm going to send it to a phone repair shop and see what they can do.
Edit: The phone repair guy says that the only way it can be repaired is by replacing the emmc or replacing the motherboard. So for now the phone will sit in the drawer until I manage to get a new board.

Hello
I had the same problem with my honor 7, the only solution is to replace the motherboard :/

If the phone is completely dead, warranty will accept it just because they will change your motherboard if they can't turn it on. I had the same problem last week, probably an hardware fail, I gave it to them saying that the phone simply turned off and they changed the whole motherboard (bootloader unlocked, twrp and root).

Well I tried sending it to the repair center. Two days later they replaced the whole phone, they said that there was an issue with the power ic.

B160 works for me.. hmm.... using it for like a [email protected]@
might be your hardware that cause the problem and not the firmware?

ivanwong1989 said:
B160 works for me.. hmm.... using it for like a [email protected]@
might be your hardware that cause the problem and not the firmware?
Click to expand...
Click to collapse
I'm starting to think so, I've flashed the replacement and it didn't brick. May or may not be related to the headers, but I don't want to be creative right now since I need the phone lol.

What is b160 can you explain

Help sort of "bricked" phone to unbrick!

My Asus Zenfone Max Pro M1 is stuck on the screen," Powered by Android". I have neither rooted nor unlocked the bootloader. I had received the error of "Your device is corrupted" and had followed the guide to remove that. For a month, my phone lagged and had a drop in battery. Restarting it has caused it to not work.Now, it's showing no signs of starting. Any help will be sincerely appreciated!

manav113 said:
My Asus Zenfone Max Pro M1 is stuck on the screen," Powered by Android". I have neither rooted nor unlocked the bootloader. I had received the error of "Your device is corrupted" and had followed the guide to remove that. For a month, my phone lagged and had a drop in battery. Restarting it has caused it to not work.Now, it's showing no signs of starting. Any help will be sincerely appreciated!
Click to expand...
Click to collapse
download 059 fastboot rom[search in forum you will find 059 fastboot rom. it is in-(how to use flashtool thread)]
unzip it.
connect your phone with pc as in fastboot mode.
double click on flashallAFT.bat or .cmd file from fastboot rom folder.
059 fresh installtion will be donw by this although you will lose all your data so please backup if possible.
after that if u still have that 'your device is corrupt' error follow my thread . corrupt state fix command dosnt mess with your system whatsoever. so either u deleted some files accidently or it got deleted during update. dont blame any buddy regarding that.

P53mutant said:
download 059 fastboot rom[search in forum you will find 059 fastboot rom. it is in-(how to use flashtool thread)]
unzip it.
connect your phone with pc as in fastboot mode.
double click on flashallAFT.bat or .cmd file from fastboot rom folder.
059 fresh installtion will be donw by this although you will lose all your data so please backup if possible.
after that if u still have that 'your device is corrupt' error follow my thread . corrupt state fix command dosnt mess with your system whatsoever. so either u deleted some files accidently or it got deleted during update. dont blame any buddy regarding that.
Click to expand...
Click to collapse
Thanks for Replying bro. TMy phone is not going to any mode ie neither fastboot nor recovery. Its only showing Powered by Android whatever combinations I go with.I am thinking to try the QFIL s/w.

manav113 said:
Thanks for Replying bro. TMy phone is not going to any mode ie neither fastboot nor recovery. Its only showing Powered by Android whatever combinations I go with.I am thinking to try the QFIL s/w.
Click to expand...
Click to collapse
go for qfil then but use 059 qfil otherwise 130 qfill u will lose your persist,factory,fsg partition. doownload 059 fastboot rom . it is combined fastboot qfill rom. use it same as other qfill rom but choose here ww_no-nfc_no-fsg raw program.
btw your device showing powered by android that means u can go into fastboot mode and recovery mode both. just press and hold power button untill u see restart of ur screen. as soon as u see that press violume up along with power key. u will def get acess to fastboot mode.

P53mutant said:
go for qfil then but use 059 qfil otherwise 130 qfill u will lose your persist,factory,fsg partition. doownload 059 fastboot rom . it is combined fastboot qfill rom. use it same as other qfill rom but choose here ww_no-nfc_no-fsg raw program.
btw your device showing powered by android that means u can go into fastboot mode and recovery mode both. just press and hold power button untill u see restart of ur screen. as soon as u see that press violume up along with power key. u will def get acess to fastboot mode.
Click to expand...
Click to collapse
Didn't worked.. QFIL s/w was not able to detect the port even after connecting the mobile.. Tried to completely discharge and recharge hoping it would work.. Now, its not even recharging.. Nothing works now..Feels like a motherboard problem now..Should I rebuy the 4GB version or look for another mobile?

Try asus service center

manav113 said:
Didn't worked.. QFIL s/w was not able to detect the port even after connecting the mobile.. Tried to completely discharge and recharge hoping it would work.. Now, its not even recharging.. Nothing works now..Feels like a motherboard problem now..Should I rebuy the 4GB version or look for another mobile?
Click to expand...
Click to collapse
motherboard issue not lead to sudden death of phone. did u encounter random reboot before every 10-20 mins if not no worry.
for qfill u have to turn off your phone and press vol + and vol - together and have to connect your hpone with pc. check device manager of pc it will show port and comt device 2-3 mins after successfull qualcomm diag port driver installation.

98har**** said:
Try asus service center
Click to expand...
Click to collapse
No response. They said they aren't able to fix it. Can give 1k for the lcd screen.. :crying:

P53mutant said:
motherboard issue not lead to sudden death of phone. did u encounter random reboot before every 10-20 mins if not no worry.
for qfill u have to turn off your phone and press vol + and vol - together and have to connect your hpone with pc. check device manager of pc it will show port and comt device 2-3 mins after successfull qualcomm diag port driver installation.
Click to expand...
Click to collapse
Didn't had any random reboot stuff. I thought voltage fluctuations might have affected it. I had charged it at the Airport the same day the phone gave up. The QFIL software was not able to detect port even while pressing vol+ and vol- .Service Centre tells me its a PCB problem and are asking 3k for repair. Looks like a new phone is somewhere in the line for future.

manav113 said:
Didn't had any random reboot stuff. I thought voltage fluctuations might have affected it. I had charged it at the Airport the same day the phone gave up. The QFIL software was not able to detect port even while pressing vol+ and vol- .Service Centre tells me its a PCB problem and are asking 3k for repair. Looks like a new phone is somewhere in the line for future.
Click to expand...
Click to collapse
well good riddance

Help!!!!!! Boot image destroyed pls read this::::

Hii!! I have a realme 2 pro rmx1801. I was on real.e ui v1.0. I somehow managed to unlock the bootloader by fastboot. Then i tried to flash twrp recovery. My phone was stucking on the white realme logo and was again automatically booting normally into system. I tried to flash recovery 10-11 times but the same thing happening. Then i searched for it and found a guy who was saying that after flashing recovery, I will have to flash a file named " boot+patched+magisk". Then i did the same but found that my phone now niether was able to boot into recovery nor into system. It was just showing white realme logo, then turned off again, again tried to start and again turned off... the process repeated again and again until i booted it into fastboot. I got afraid and thought that after relocking bootloader it would return to normal but when i locked it again it just showed---- " the current boot image (boot/recovery) has been destroyed and can not boot." I took it to a local repair shop as there is no official realme service centere in my city. He said it would take 3 days to repair it, he told that he will have to download files. I left it there and then the third day called him. He said that he tried to flash but he was not able to repair it. He also told that the phone booted up one time upto the home screen but again reached to the same boot image destroyed message automaticall. I told him that i want my phone repaired and he asked for 2 more days. I allowed. It is about 21 days and he is saying the same thing again and again. Is my phone dead? He is saying that the chances of my phone get reapaired are very low. He said i have also tried ufi but no success. Is he lying? I have not seen my phone from about 21 days, as it is covid-19 spread. We are only talking on phone. Pls tell that can my phone be reapired?
Edit: I bring my phone back from him today. He said that he was not able to repair it. When i gave the device to him it was turning on upto realme and then showing boot image destroyed. But now it is not even turning on. What should i do now. Is this a mistake of mine or he is responsible?

Have you locked Bootloader?
If yes then probably you must flash using flash tool.
(Which may work or not)
If you haven't locked Bootloader then easily flash stock recovery,then flash stock rom
For guide go to YouTube then search your title
The current boot recovery destroyed and cannot boot.

androport said:
Have you locked Bootloader?
If yes then probably you must flash using flash tool.
(Which may work or not)
If you haven't locked Bootloader then easily flash stock recovery,then flash stock rom
For guide go to YouTube then search your title
The current boot recovery destroyed and cannot boot.
Click to expand...
Click to collapse
My bootloader is locked. But i thing ufi should work as it directly flashes emmc of device.

Kartikkala said:
My bootloader is locked. But i thing ufi should work as it directly flashes emmc of device.
Click to expand...
Click to collapse
Will msm work? the guy which is repairing my phone is telling that the device turned on for some time but it went to the same condition automatically again. I am thinking is this even possible? Well i tried connecting it to msm and it showed up there on msm as com4 and in devices as qualcomm hs qdloader.

How did you unlock bootloader ?? Can you help me with that please ?? a
Kartikkala said:
Hii!! I have a realme 2 pro rmx1801. I was on real.e ui v1.0. I somehow managed to unlock the bootloader by fastboot. Then i tried to flash twrp recovery. My phone was stucking on the white realme logo and was again automatically booting normally into system. I tried to flash recovery 10-11 times but the same thing happening. Then i searched for it and found a guy who was saying that after flashing recovery, I will have to flash a file named " boot+patched+magisk". Then i did the same but found that my phone now niether was able to boot into recovery nor into system. It was just showing white realme logo, then turned off again, again tried to start and again turned off... the process repeated again and again until i booted it into fastboot. I got afraid and thought that after relocking bootloader it would return to normal but when i locked it again it just showed---- " the current boot image (boot/recovery) has been destroyed and can not boot." I took it to a local repair shop as there is no official realme service centere in my city. He said it would take 3 days to repair it, he told that he will have to download files. I left it there and then the third day called him. He said that he tried to flash but he was not able to repair it. He also told that the phone booted up one time upto the home screen but again reached to the same boot image destroyed message automaticall. I told him that i want my phone repaired and he asked for 2 more days. I allowed. It is about 21 days and he is saying the same thing again and again. Is my phone dead? He is saying that the chances of my phone get reapaired are very low. He said i have also tried ufi but no success. Is he lying? I have not seen my phone from about 21 days, as it is covid-19 spread. We are only talking on phone. Pls tell that can my phone be reapired?
Edit: I bring my phone back from him today. He said that he was not able to repair it. When i gave the device to him it was turning on upto realme and then showing boot image destroyed. But now it is not even turning on. What should i do now. Is this a mistake of mine or he is responsible?
Click to expand...
Click to collapse
I am running realme ui v1 f.11.. In depth test app is not working.help me please..

Samanto70 said:
I am running realme ui v1 f.11.. In depth test app is not working.help me please..
Click to expand...
Click to collapse
Go in below thread and check #2 post
https://forum.xda-developers.com/realme-2-pro/help/bootloader-unlock-problem-t4167125
I already posted how to unlock bootloader on realme ui

Samanto70 said:
I am running realme ui v1 f.11.. In depth test app is not working.help me please..
Click to expand...
Click to collapse
Doesn't work on realme ui

Samanto70 said:
I am running realme ui v1 f.11.. In depth test app is not working.help me please..
Click to expand...
Click to collapse
You are lucky. Dont try to unlock ur boot loader forcefully. Or you will perish too. You can unlock it but any custom recovery is not yet launched for realme ui. If u want to still unlock it, download bugjaegar app form playstore on another device, turn on usb debug on ur realme 2 pro and the another device too , connect ur device and open bugjaegar app on ur other device, it will ask for allowing bugjaegar to debug via usb. Allow it, a prompt will pop up on ur realme 2 pro. Allow it. If u are not asked, click on reboot bootloader on bugjaegar app, definitely the prompt will pop up on your realme 2 pro. Click allow and u are good to go. Make sure that u turn on oem unlock too.

Has anyone succeeded in repairing a bricked Poco M3?

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!

me too

waiting, someone pls

LeandroFarias said:
waiting, someone pls
Click to expand...
Click to collapse
I kind of managed to get my Poco M3 to start on Android (but it's not fully fixed).

That is the points

vinod3362 said:
That is the points
Click to expand...
Click to collapse
What?

me too. after i reboot my poco m3. it came to black and wont boot up. i google everything, the only need to flash is to modified the firehose. badly needed.

KaMyKaSii said:
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!
Click to expand...
Click to collapse
how do you get into fastboot?? i tried mine but it wont boot in fastboot. i'm stuck in QDLoader.

did someone successfully recover their bricked poco m3 ?

gasleak08 said:
did someone successfully recover their bricked poco m3 ?
Click to expand...
Click to collapse
nothing yet. we need firehose to bypass miflash authentication. or drain the battery then press vol down + power for 10secs.

KaMyKaSii said:
I kind of managed to get my Poco M3 to start on Android (but it's not fully fixed). Are you Brazilian too? Call me on telegram
Matheus
You can contact @MatheusCoelho1998 right away.
t.me
Click to expand...
Click to collapse
can u tell me how?mine too?

my phone has bricked with UBL condition and i flash whole partition with twrp and magisk to solve the heating problem now its alive again

I just wait till the battery totally discharge and then plug in the charger,sofar been through this problem for 2x,the first one for 2 days and 5 days for later because the battery was full.
This happens when Im restarting the device and now even there is a new update,Im still scare to update my device to the latest firmware incase it wont boot again.
Should I try to update or nah,guys?

Minoda86 said:
I just wait till the battery totally discharge and then plug in the charger,sofar been through this problem for 2x,the first one for 2 days and 5 days for later because the battery was full.
This happens when Im restarting the device and now even there is a new update,Im still scare to update my device to the latest firmware incase it wont boot again.
Should I try to update or nah,guys?
Click to expand...
Click to collapse
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself

yankee77 said:
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself
Click to expand...
Click to collapse
I did update it and now my phone wont boot at all,after the battery hits 1%,it just wont do anything and its been 2 weeks,pc does detect it as qualcom loader but flashing without auth wont work,Im just waiting for firehose file for this stupid phone.People with auth asking for $30 for fixing it but without guarantee that it will work,what a joke.
So did you fix your phone?

yankee77 said:
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself
Click to expand...
Click to collapse
Yeahhh,my phone finally boot up!
But sadly the latest update failed to install.Guess I should just wait until someone patch the firehose file and try not to update until then.Fingercross!

i fixed the deadboot issue. but it wont fix the restart deadboot. try to flash every region and version firmware both recovery and fastboot. the problem still there.

vinzikidz said:
i fixed the deadboot issue. but it wont fix the restart deadboot. try to flash every region and version firmware both recovery and fastboot. the problem still there.
Click to expand...
Click to collapse
how did u fix deadboot can you elaborate? how did you flash from edl ?

gasleak08 said:
how did u fix deadboot can you elaborate? how did you flash from edl ?
Click to expand...
Click to collapse
sorry, there's is no tutorial for this and it has a quite process. you just need to throttle the proc temperature of your phone board using hot blower or any device you have. while your phone is in high temp. both pin board and battery is in unplug hold vol down then put back the board pin and battery pin at the same time. it will vibrate and fastboot will be fine.

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
VID_20210514_152510.mp4
drive.google.com

[HELP THREAD] Poco M3 Bricked (No Recovery, No Fastboot, ONLY EDL)

Hey guys! I made a newbie mistake by not using mi flash tool and use manual flashing using sdk fastboot and i dont know what mistake i did but im pretty sure i did something wrong. Bootloader is already unlocked and i have root access already. Right after i flashed a magisk patched boot file to give root access and booted it up. The wifi wasnt working and tried to flash a stock rom again hoping it will fix the wifi not turning on problem, but unfortunately i think i flashed wrong rom or something and it basically bricked. Cant boot to recovery nor fastboot. but mi flashtool and QFIL can detect it. Tried flashing stock rom that i downloaded from official website and Mi flash tool will always fail at authentication and it says "only nop and sig tag can be received before authentication" and other different errors like resdump(etc. cause i dont understand. I tried QFIL using test points i found on google. and it will say Sahara fail or sometimes "firehose fail fhloader fail the system cannot find the file specified". Im not really good at this and really regretting rooting it. I cant give it to Xiaomi Phone centers because i bought it from overseas and there are no xiaomi phone centers in my country.
Can someone with a kind heart help me with this problem? Thank you very much.

Hello! Sorry to say this, but it is pretty much dead. You are in EDL mode, which Xiaomi locked out and you need to have an authorized service account to unbrick it through Mi Flash. A free way to do this would have been to find a patched programmer file, but it doesn't exist yet. I recommend you to ask every phone service in your city if they have an authorized service account or if they have USB Dongles (like Miracle Box or Hydra) for unbricking.

Theres no other choice.. only service center could handle it..

TheAlmigthyOne said:
Hello! Sorry to say this, but it is pretty much dead. You are in EDL mode, which Xiaomi locked out and you need to have an authorized service account to unbrick it through Mi Flash. A free way to do this would have been to find a patched programmer file, but it doesn't exist yet. I recommend you to ask every phone service in your city if they have an authorized service account or if they have USB Dongles (like Miracle Box or Hydra) for unbricking.
Click to expand...
Click to collapse
You
TheAlmigthyOne said:
Hello! Sorry to say this, but it is pretty much dead. You are in EDL mode, which Xiaomi locked out and you need to have an authorized service account to unbrick it through Mi Flash. A free way to do this would have been to find a patched programmer file, but it doesn't exist yet. I recommend you to ask every phone service in your city if they have an authorized service account or if they have USB Dongles (like Miracle Box or Hydra) for unbricking.
Click to expand...
Click to collapse
It can be fixed using heat its not totally dead I've done this temporary solution many times on my POCO

I fixed mine using THIS but just temporary solution there is no permanent solution at the moment,

Darkvintage09 said:
I fixed mine using THIS but just temporary solution there is no permanent solution at the moment,
Click to expand...
Click to collapse
i used thqt qnd still not fix it

Yeh at least we can still use it just to get the device booting up

What do you mean temporary solution?

Hi Everyone, Just wanted to share the solution that we found out. My Friend had his Poco M3 Bricked, dead boot. No recovery, No display(totally black screen) and when I plug it in via USB it shows "
Qualcomm HS-USB QDLoader 9008 "​Been here about a month ago hoping that there is a solution. We tried the rubber band Method(See the attached image how to do it) you just need a cotton buds and a rubber band. Just place the tip of the cotton bud into the power button and secure it with rubber band 2 knots. So it's pressing the power button that way it's draining the battery it took him 2 days to drain it, But once the battery is drained the Charging Icon will display in the screen. And you can charge it and wait for it to boot up. This worked for my Xiaomi Redmi 9T and my Friend Poco M3 bot uses MIUI 12. After it boot again try to Avoid restarting it and Shutting it down so this may never happen Again.

bjsalcedo10 said:
Hi Everyone, Just wanted to share the solution that we found out. My Friend had his Poco M3 Bricked, dead boot. No recovery, No display(totally black screen) and when I plug it in via USB it shows "
Qualcomm HS-USB QDLoader 9008 "​Been here about a month ago hoping that there is a solution. We tried the rubber band Method(See the attached image how to do it) you just need a cotton buds and a rubber band. Just place the tip of the cotton bud into the power button and secure it with rubber band 2 knots. So it's pressing the power button that way it's draining the battery it took him 2 days to drain it, But once the battery is drained the Charging Icon will display in the screen. And you can charge it and wait for it to boot up. This worked for my Xiaomi Redmi 9T and my Friend Poco M3 bot uses MIUI 12. After it boot again try to Avoid restarting it and Shutting it down so this may never happen Again.
Click to expand...
Click to collapse
Wonderful!!!! it really works on my Redmi 9T...cheers

Hello thank you it's work
I managed to turn my poco m3 back on which was in edl. can i restart without worrying that i'm still in edl? Do you know? thank you

totodu13190 said:
Hello thank you it's work
I managed to turn my poco m3 back on which was in edl. can i restart without worrying that i'm still in edl? Do you know? thank you
Click to expand...
Click to collapse
No, same will happen again. It was issue with my Poco M3 too.
Don't restart, recover your data to PC or other mobile. It's a firmware to motherboard issue. Same happened with me, the set was in warranty, I took it to warranty service centre and they replaced motherboard Free of cost, now it's working fine

For all those friends having Poco M3 and having brick issue. Battery drains in 5-7 days. Attempt restart, if successful, recover your data to PC or other mobile. It's a firmware to motherboard issue. Same happened with me, the set was in warranty, I took it to warranty service centre and they replaced motherboard Free of cost, now it's working fine

Asif9 said:
For all those friends having Poco M3 and having brick issue. Battery drains in 5-7 days. Attempt restart, if successful, recover your data to PC or other mobile. It's a firmware to motherboard issue. Same happened with me, the set was in warranty, I took it to warranty service centre and they replaced motherboard Free of cost, now it's working fine
Click to expand...
Click to collapse
For how much time does it work ? Is it a permanent fix ? The service center did the same for my Poco M3 (replacing motherboard) but I'm afraid it will go deadboot again one day.

Darkvintage09 said:
I fixed mine using THIS but just temporary solution there is no permanent solution at the moment,
Click to expand...
Click to collapse
Can you explain how to managed to fix it?

https://forum.xda-developers.com/t/poco-m3-does-not-turn-on-anymore.4286783/post-85692315
https://forum.xda-developers.com/t/...no-fastboot-no-recovery.4363681/post-86748309

Lingatsu said:
For how much time does it work ? Is it a permanent fix ? The service center did the same for my Poco M3 (replacing motherboard) but I'm afraid it will go deadboot again one day.
Click to expand...
Click to collapse
After service centre motherboard replacement the set is working fine, it has updated Miui to 12.5 too. No more issues.

Asif9 said:
After service centre motherboard replacement the set is working fine, it has updated Miui to 12.5 too. No more issues.
Click to expand...
Click to collapse
It's been more than six months after replacement motherboard.

bjsalcedo10 said:
Hi Everyone, Just wanted to share the solution that we found out. My Friend had his Poco M3 Bricked, dead boot. No recovery, No display(totally black screen) and when I plug it in via USB it shows "
Qualcomm HS-USB QDLoader 9008 "​Been here about a month ago hoping that there is a solution. We tried the rubber band Method(See the attached image how to do it) you just need a cotton buds and a rubber band. Just place the tip of the cotton bud into the power button and secure it with rubber band 2 knots. So it's pressing the power button that way it's draining the battery it took him 2 days to drain it, But once the battery is drained the Charging Icon will display in the screen. And you can charge it and wait for it to boot up. This worked for my Xiaomi Redmi 9T and my Friend Poco M3 bot uses MIUI 12. After it boot again try to Avoid restarting it and Shutting it down so this may never happen Again.
Click to expand...
Click to collapse
How do I understand that it is ready to be connected to the battery charger? low battery icon will appear on the smartphone screen? thank you

It's already solved in this thread, you have to go back and find it.
[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...
forum.xda-developers.com