Database Users

LG Flash Tool crashed while flashing, phone bricked

Hi,
I was about flashing stock rom (following this thread and using CSE Flashing mode), when suddenly LG Flash Tool crashed on windows (I hate windows). Flashing progress stuck at 16%, so I press and hold power button to power phone off. but when I tried to enter to Download Mode, phone start too boot, and after LG logo, screen keeps going on and off (showing black screen)
I tried to enter to recover or factory hard reset, but it going to Factory data reset, even if I confirm reseting data it would try to boot same as when I tried to get Download Mode.
adb does not work
I followed this thread, but /dev/sdb1..36 just available for a few second and then disappear, after a while they are available and then disappear, and this will going on, (I think this is related to that screen on and off thing)
Would someone help me?
Sorry for my bad english, I'm a little nervous right now

Ok, finally I could see sdb1...36 and do what have been said here, and now I stuck at LG logo at boot.
still cannot get the download mode
factory hard reset is back but it'll stuck at "Factory reset processing..."

I have really lost my respect to flashtool after this kind of errors. If someone solve that issue it would be great for our community

please help

IM SORRY
we have the same scenario before, identically as yours.. and im sorry to tell you that you bricked your G2 so bad. i need to take mine to service center and they said that it needs the board to be replace, luckily im still on warranty. hope you still have yours as well

berceniqgil said:
we have the same scenario before, identically as yours.. and im sorry to tell you that you bricked your G2 so bad. i need to take mine to service center and they said that it needs the board to be replace, luckily im still on warranty. hope you still have yours as well
Click to expand...
Click to collapse
Yes I'm still have warranty.
But I hope I can fix it myself

Mine just got this issue too. Repair center denied the phone for repairs, claiming it is user damage.
So yup, I have a neat paperweight now.

berceniqgil said:
we have the same scenario before, identically as yours.. and im sorry to tell you that you bricked your G2 so bad. i need to take mine to service center and they said that it needs the board to be replace, luckily im still on warranty. hope you still have yours as well
Click to expand...
Click to collapse
Zulake said:
Mine just got this issue too. Repair center denied the phone for repairs, claiming it is user damage.
So yup, I have a neat paperweight now.
Click to expand...
Click to collapse
Somewhere in the forum i saw that you can detect your phone as a adb device on ubuntu or etc. Have you tried that? Im really feeling sorry about hearing that issue. As advice use old flashtool method that is harder but safer

abdulkadiro said:
Somewhere in the forum i saw that you can detect your phone as a adb device on ubuntu or etc. Have you tried that? Im really feeling sorry about hearing that issue. As advice use old flashtool method that is harder but safer
Click to expand...
Click to collapse
Ubuntu is running in a VM, so I would need Windows to find the phone first.
Unfortunately, Windows never sees the phone.
It's weird though. TWRP got successfully flashed during the QHSUSB_BULK guide method, but I cannot boot into it.

Zulake said:
Ubuntu is running in a VM, so I would need Windows to find the phone first.
Unfortunately, Windows never sees the phone.
It's weird though. TWRP got successfully flashed during the QHSUSB_BULK guide method, but I cannot boot into it.
Click to expand...
Click to collapse
Maybe you had a bad download try an another base

abdulkadiro said:
Maybe you had a bad download try an another base
Click to expand...
Click to collapse
I lost QHSUSB_BULK mode now, the PC won't see the phone anymore and all modes are gone.
No download mode, no recovery, no ADB, no fastboot, factory reset freezes, nothing works.

Zulake said:
I lost QHSUSB_BULK mode now, the PC won't see the phone anymore and all modes are gone.
No download mode, no recovery, no ADB, no fastboot, factory reset freezes, nothing works.
Click to expand...
Click to collapse
If you see the lg logo maybe you will have a change. A guy who had the same results like you brings his phone plugged for 10-15 minutes than he have find his phone in download mode. Of course he plug the cable while holding the down button. I hope you will get your phone back with its functions

abdulkadiro said:
If you see the lg logo maybe you will have a change. A guy who had the same results like you brings his phone plugged for 10-15 minutes than he have find his phone in download mode. Of course he plug the cable while holding the down button. I hope you will get your phone back with its functions
Click to expand...
Click to collapse
Well, that's worth the try.
I just connected it while holding volume up.
Hopefully it will still charge when connected.
//Well, it's been about 15 minutes now and it still displays the LG logo.
Guess I'm outta luck on this one.

Zulake said:
Somewhere in the forum i saw that you can detect your phone as a adb device on ubuntu or etc. Have you tried that? Im really feeling sorry about hearing that issue. As advice use old flashtool method that is harder but safer
Click to expand...
Click to collapse
I tried that on my ubuntu laptop, ubuntu did not detect the phone
Zulake said:
Well, that's worth the try.
I just connected it while holding volume up.
Hopefully it will still charge when connected.
//Well, it's been about 15 minutes now and it still displays the LG logo.
Guess I'm outta luck on this one.
Click to expand...
Click to collapse
I read this post one more time, this guy who had download mode after 10-15 minute, have discharged the phone then do what he said. have you try that?
I have discharged my phone, but I'm going to work right now, later today I will try and let you know if it was fixed or not

Behzadsh said:
I tried that on my ubuntu laptop, ubuntu did not detect the phone
I read this post one more time, this guy who had download mode after 10-15 minute, have discharged the phone then do what he said. have you try that?
I have discharged my phone, but I'm going to work right now, later today I will try and let you know if it was fixed or not
Click to expand...
Click to collapse
I won't dare doing that, as it doesn't seem to charge anymore.
I'm gonna retry sending it in today, otherwise it's going into the bin.

I tried one more time last night when phone was fully discharged. nothing has been changed.
Zulake said:
I won't dare doing that, as it doesn't seem to charge anymore.
I'm gonna retry sending it in today, otherwise it's going into the bin.
Click to expand...
Click to collapse
Hopefully it start charging.

Qualcomm hs-usb qdloader 9008 nexus 6P (HELP!)

Hi there, I've been browsing through the threads related to unbricking of the Nexus 6P stuck in qualcomm hs-usb qdloader 9008 mode, really desperate to get my device working again if even possible however I've tried for about four days now different ways and files and I've had no luck.
My bootloader is locked and no ADB etc managed to get my device showing as the 9008 port so I think it's stuck in EDL.
Following guides, this is the furthest I've yet to get (In screenshot)
Could anyone shed some light and some assistance please? what am I doing wrong!?

attempted to apply for heat some to the device then re flash ?

blackcell1 said:
attempted to apply for heat to the device then re flash ?
Click to expand...
Click to collapse
Sorry, I don't quite understand what you mean?

Clarkeofcurtis said:
Sorry, I don't quite understand what you mean?
Click to expand...
Click to collapse
Use a hairdryer to warm up the back of the phone.

Are you pulling my leg? Warm it up then reflash?

nah im not trying to make you destroy your phone, being rather serious with this method. i use it on a daily basis to solve phones that fail during restoring factory images. i wouldn't know how long to give it with a hair dryer as i have access to a heat gun/heat mats .
just think of it as a cheap mans re balling method

blackcell1 said:
nah im not trying to make you destroy your phone, being rather serious with this method. i use it on a daily basis to solve phones that fail during restoring factory images. i wouldn't know how long to give it with a hair dryer as i have access to a heat gun/heat mats .
just think of it as a cheap mans re balling method
Click to expand...
Click to collapse
Sorry haha, I'm a noob with most of this android stuff bar rooting and flashing a few devices prior! I shall give it a go now and get back to you - thank you for the advice

Clarkeofcurtis said:
Sorry haha, I'm a noob with most of this android stuff bar rooting and flashing a few devices prior! I shall give it a go now and get back to you - thank you for the advice
Click to expand...
Click to collapse
good luck, id give it a good couple of minutes on the highest setting, just so its a little hot to the touch. and attempt the flashing of the files when its still hot/warm.

blackcell1 said:
good luck, id give it a good couple of minutes on the highest setting, just so its a little hot to the touch. and attempt the flashing of the files when its still hot/warm.
Click to expand...
Click to collapse
thank you so much that worked, it has said flash successful, first time I got a google logo but now nothing, what would be my next step please?

if the bootloader is unlocked then you can directly flash the firmware. but if its not google "nexus ota" and then on your phone jump into the recovery and check the firmware model number and download the same ota and adb sideload it.
im not 100% sure on the next step as I've never had a nexus 6p with a dead bootloader. but thats what id do.
---------- Post added at 04:50 PM ---------- Previous post was at 04:49 PM ----------
but from my personal experience with having to heat a phone up to restore factory images, it kinda means the phone is nearing the end of its life and id start thinking about buying your next phone before it sh*ts the bed.

blackcell1 said:
if the bootloader is unlocked then you can directly flash the firmware. but if its not google "nexus ota" and then on your phone jump into the recovery and check the firmware model number and download the same ota and adb sideload it.
im not 100% sure on the next step as I've never had a nexus 6p with a dead bootloader. but thats what id do.
Click to expand...
Click to collapse
Thank you for the reply and continuing to help, after seeing the google logo just once I'm getting nothing again - I'm even more determined now though as It's been dead for 2 months so this is the furthest I've gotten - the application of heat is what did it for me and fixed the error I was getting, can't get into recovery now though holding power + down etc

Clarkeofcurtis said:
Thank you for the reply and continuing to help, after seeing the google logo just once I'm getting nothing again - I'm even more determined now though as It's been dead for 2 months so this is the furthest I've gotten - the application of heat is what did it for me and fixed the error I was getting, can't get into recovery now though holding power + down etc
Click to expand...
Click to collapse
yeah can you access the bootloader at all ? does it say that the bootloader is locked ? from trying to restore LG's it sometimes has to be re heated a few times, but yeah if you need to re heat it to get further into the phone then its pretty much a lost cause. the only reason i do it is to remove the data so we can resell the device.

blackcell1 said:
yeah can you access the bootloader at all ? does it say that the bootloader is locked ? from trying to restore LG's it sometimes has to be re heated a few times, but yeah if you need to re heat it to get further into the phone then its pretty much a lost cause. the only reason i do it is to remove the data so we can resell the device.
Click to expand...
Click to collapse
I can get into the andriod screen where you can select recovery and such, with the BL, Baseband product variation and such, where should I go from here?
Oh right, so even once restored to firmware, will it be useless do you think if I can even manage to?

Clarkeofcurtis said:
I can get into the andriod screen where you can select recovery and such, with the BL, Baseband product variation and such, where should I go from here?
Oh right, so even once restored to firmware, will it be useless do you think if I can even manage to?
Click to expand...
Click to collapse
Sorry if you can't access the recovery from the bootloader and its in locked state then your a member of the lovely group of BLOD (bootloader of death) if you hit recovery does it show a little android logo and sit there?
Sorry for the late reply

blackcell1 said:
Sorry if you can't access the recovery from the bootloader and its in locked state then your a member of the lovely group of BLOD (bootloader of death) if you hit recovery does it show a little android logo and sit there?
Sorry for the late reply
Click to expand...
Click to collapse
I believe so, I can just about get into the bootloader at the best of times and when I do I can select options but once proceeding to start said mode phone freezes so can't get into recovery mode :/
Thank you for your continuous help, only way i can get it into bootloader is by heating it up so does that mean for the device to ever work It'll need heat every time? looking like a spares and repairs listing on ebay

Clarkeofcurtis said:
I believe so, I can just about get into the bootloader at the best of times and when I do I can select options but once proceeding to start said mode phone freezes so can't get into recovery mode :/
Thank you for your continuous help, only way i can get it into bootloader is by heating it up so does that mean for the device to ever work It'll need heat every time? looking like a spares and repairs listing on ebay
Click to expand...
Click to collapse
Hello....
How did you manage to get in to EDL mode..? I'm really curious. With stock bootloader? Since you can't access recovery
Also what is exactly displayed in Windows device manager?
You are using an outdated QFil version... It is from 2014 àr 2015.
Do a google search with: QPST_2.7.453.0 . This version seem to be from 2016.
Use the first link from the result. I analysed the files with virustotal, those seem clean or malware...
Also when plugging your usb cord to your PC, does your phone vibrate? Or does the LED blink in red?
You may have to press power button when plugging the usb cord or press power button for a certain amount of time before you plug the usb cord. I'm not completly sure, but your phone may not be in the "proper" EDL state to accept the QFil flash.
Good luck... :good:

Is it possible to send me the guide you used? Thanks.
Clarkeofcurtis said:
Hi there, I've been browsing through the threads related to unbricking of the Nexus 6P stuck in qualcomm hs-usb qdloader 9008 mode, really desperate to get my device working again if even possible however I've tried for about four days now different ways and files and I've had no luck.
My bootloader is locked and no ADB etc managed to get my device showing as the 9008 port so I think it's stuck in EDL.
Following guides, this is the furthest I've yet to get (In screenshot)
Could anyone shed some light and some assistance please? what am I doing wrong!?
Click to expand...
Click to collapse

Hey there sorry for slow replies, will be back on my desktop in an hour I'll send you links for what I followed and such, I think the only reason my device was in EDL mode was due to a hardware fault? As my device is faulty indefinitely as I had to use a hairdryer to warm it up while flashing this then allowed it to enter firehose state which a lot of people seem to error with - after all my attempts and research I'm to velieve there's a fault with the phone itself the only way I could get it to even power up was applying heat to it after removing the back panel
As blackcell said deballing or something? Worked a treat!
Furthest I've managed to get now is into my boot loader however everything is locked - when I press enter recovery my handset just freezes ?

5.1 said:
Hello....
How did you manage to get in to EDL mode..? I'm really curious. With stock bootloader? Since you can't access recovery
Also what is exactly displayed in Windows device manager?
You are using an outdated QFil version... It is from 2014 àr 2015.
Do a google search with: QPST_2.7.453.0 . This version seem to be from 2016.
Use the first link from the result. I analysed the files with virustotal, those seem clean or malware...
Also when plugging your usb cord to your PC, does your phone vibrate? Or does the LED blink in red?
You may have to press power button when plugging the usb cord or press power button for a certain amount of time before you plug the usb cord. I'm not completly sure, but your phone may not be in the "proper" EDL state to accept the QFil flash.
Good luck... :good:
Click to expand...
Click to collapse
Thanks pal if you check last post I wrote about my EDL mode forgot to tag you my apologies, as for my LED I've never seen that light up since I bricked it, even when google logo came up etc and while in the boot loader

Clarkeofcurtis said:
Thanks pal if you check last post I wrote about my EDL mode forgot to tag you my apologies, as for my LED I've never seen that light up since I bricked it, even when google logo came up etc and while in the boot loader
Click to expand...
Click to collapse
Light usually a red LED blink while in proper EDL state as far as I know. Could be something else on the N6P. Well, it looks like you are SOL. Sorry, I don't know what else to say, since you exhausted all possibilities...
Good luck...

Hardbricked Phone, please help!!!

Hi,
I was flashing the stock firmware from Essential Developers website and the flash-all.bat gave me a bunch of errors and the phone shut down. I won't power on anymore. No button combination help. When I connect it to my computer the computer dings and device manager shows 'Qualcomm HS-USB QDLoader 9008'. Now that I know for sure that the phone is hard bricked, is there a way to bring this back to life?
I followed this tutorial, but it didn't help.
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/

rukesh18 said:
Hi,
I was flashing the stock firmware from Essential Developers website and the flash-all.bat gave me a bunch of errors and the phone shut down. I won't power on anymore. No button combination help. When I connect it to my computer the computer dings and device manager shows 'Qualcomm HS-USB QDLoader 9008'. Now that I know for sure that the phone is hard bricked, is there a way to bring this back to life?
I followed this tutorial, but it didn't help.
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Click to expand...
Click to collapse
Does your phone have the bootloader unlocked?
Sent from my PH-1 using Tapatalk

TJSteveMX said:
Does your phone have the bootloader unlocked?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I did unlock the bootloader before flashing the stock image. Unlocking the bootloader is a step quoted in Essential's Website.

rukesh18 said:
I did unlock the bootloader before flashing the stock image. Unlocking the bootloader is a step quoted in Essential's Website.
Click to expand...
Click to collapse
Can you do to terminal on your PC and type adb devices?
It Should show your device and a serie of numbers
Sent from my PH-1 using Tapatalk

TJSteveMX said:
Can you do to terminal on your PC and type adb devices?
It Should show your device and a serie of numbers
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
No, I don't think my phone has bootloader anymore. So, I does not show up in either fastboot or adb

rukesh18 said:
No, I don't think my phone has bootloader anymore. So, I does not show up in either fastboot or adb
Click to expand...
Click to collapse
I don't think your phone is bricked, if it's showing on your PC.
Also you don't loose your bootloader just by flashing stock images. Must be something else...
If you can, contact me via telegram
https://t.me/El_Esteban
I can probably help you there better and/or send you tons place were they can help you
Sent from my PH-1 using Tapatalk

TJSteveMX said:
I don't think your phone is bricked, if it's showing on your PC.
Also you don't loose your bootloader just by flashing stock images. Must be something else...
If you can, contact me via telegram
https://t.me/El_Esteban
I can probably help you there better and/or send you tons place were they can help you
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Thanks, I am sending you a PM in Telegram.

rukesh18 said:
Thanks, I am sending you a PM in Telegram.
Click to expand...
Click to collapse
Any resolution? Have the same issue.

rukesh18 said:
Hi,
I was flashing the stock firmware from Essential Developers website and the flash-all.bat gave me a bunch of errors and the phone shut down. I won't power on anymore. No button combination help. When I connect it to my computer the computer dings and device manager shows 'Qualcomm HS-USB QDLoader 9008'. Now that I know for sure that the phone is hard bricked, is there a way to bring this back to life?
I followed this tutorial, but it didn't help.
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Click to expand...
Click to collapse
If you're using the USB c cable that came with the phone, it is known to brick devices as it's not a full fledged USB C cable. I would RMA the device with essential and let them know that their cable bricked it. They should hook you up for free as they have admitted the flaw on their end. Good luck

chray1 said:
Any resolution? Have the same issue.
Click to expand...
Click to collapse
Nope, nothing as of yet. Will update if I find something out

stryver said:
If you're using the USB c cable that came with the phone, it is known to brick devices as it's not a full fledged USB C cable. I would RMA the device with essential and let them know that their cable bricked it. They should hook you up for free as they have admitted the flaw on their end. Good luck
Click to expand...
Click to collapse
Oh, Essential basically asked to pay $200 for a refurbished phone. They tole it was my problem for trying to flash back to stock from their website and it voided the warranty

isnt there a tool out for the Qualcomm HS-USB QDLoader 9008 to flash a new bootloader?
edit: my consideration comes from here: https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868

I had the same issue and Essential replaced my device at no cost. Just my 2 cents.

I have the same question. How did you solve it?
Is it related to the cable of type-C?
---------- Post added at 10:23 ---------- Previous post was at 10:21 ----------
I have the same question. How did you solve it?
Is it related to the cable of type-C?

I did the exact thing about a month ago, I wasn't able to bring it back to life.
Essential offered me an out of warranty replacement for $200, which was cool of them considering.

jAm-0 said:
I did the exact thing about a month ago, I wasn't able to bring it back to life.
Essential offered me an out of warranty replacement for $200, which was cool of them considering.
Click to expand...
Click to collapse
It's too expensive. It's clear that it's not a customer's problem. This is caused by the hardware defect of the mobile phone.

mapleshadow said:
It's too expensive. It's clear that it's not a customer's problem. This is caused by the hardware defect of the mobile phone.
Click to expand...
Click to collapse
In my case, it was definitely my fault. I managed to mess up the boot image, and I was using a legit usb cable.
So the fact they offered a replacement in the first place, as I clearly voided ANY warranty I had (I didn't have one), I thought was cool of them to do.

jAm-0 said:
In my case, it was definitely my fault. I managed to mess up the boot image, and I was using a legit usb cable.
So the fact they offered a replacement in the first place, as I clearly voided ANY warranty I had (I didn't have one), I thought was cool of them to do.
Click to expand...
Click to collapse
My equipment is still under warranty, I have submitted the warranty service to the government and other official reply.
If there is no change in the order of execution, there is a problem. I think this is a defect.

They gave me the same BS. Their image plus their instructions brick your device and it's your fault because of some legaleese. I went back to OnePlus.

hs911 said:
isnt there a tool out for the Qualcomm HS-USB QDLoader 9008 to flash a new bootloader?
edit: my consideration comes from here: https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868
Click to expand...
Click to collapse
LG only

[SOLVED] A2017G Hard brick, Unauthroized ADB and DFU Only.

Hey guys,
Guess today it was my turn ****ing up.
I apparently have completely bricked my Axon 7 after trying to go from LOS 15.1 to stock oreo beta. The only thing I seem to be able to boot to is DFU mode and for some reason, if I press the Power button + Vol Down I will get stuck on the ZTE Logo and my PC will detect my phone through the ADB interface but every time I try doing something it says my device is unauthorized. Is there any way I can authorize the device whilst being completely bricked?
The only other thing I get is the unlocked bootloader warning screen. If I don't press anything the phone will be stuck there, if I select recovery the phone will simply shut down and anything else will result in a reboot. I have also tried a deep flash cable that that only results on the phone being stuck at the unlocked bootloader screen.
I cannot access the bootloader,
I cannot access EDL mode
I can access ADB, but device shows as unauthorized.
I can access DFU mode.
Any suggestions would be appreciated. I have looked at the Hard brick guide that involves taking the phone apart but that's not something I really want to do.
Thanks in advance.
Edit: My phone gets detected by MiFlash but every time I try flashing I get a cannot receive hello packet and object reference not set to an instance of an object.
ZTE axon 7 EDL tool detects it in ADB mode but says ERROR! NO ANSWER FROM PHONE!. Possibly since its not authorized with ADB.

Ouh....DFU? I think this thing is totally bricked.

I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?

Victor13f said:
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Click to expand...
Click to collapse
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !

raystef66 said:
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
Click to expand...
Click to collapse
Thank you for your help . It's a risk you take when flashing phones.

Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.

stinka318 said:
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
Click to expand...
Click to collapse
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!

Victor13f said:
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Click to expand...
Click to collapse
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....

stinka318 said:
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
Click to expand...
Click to collapse
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!

Victor13f said:
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Click to expand...
Click to collapse
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable

Choose an username... said:
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Click to expand...
Click to collapse
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!

Victor13f said:
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Click to expand...
Click to collapse
In that case you can just pretend that the phone got in that state by itself, it's not too morally correct but some people here pulled it off...

twice now i have gotten an axon 7 into this state. while mine have been a2017u models, i dont know that they are different than yours in that regard.
What worked for me the first time was letting the phone completely die. Being unable to boot into anything, it was somewhat a task to actually make it die, so i kept powering it on (which merely made the red led indicator come on). i did this over and over again over the course of a day at work whenever i noticed it had powered off.
eventually, the phone had no response at all. then, i plugged it up to my laptop, and left it, convinced i had killed it. a dialogue popped up after a minute or two on the phone screen saying to charge the phone by plugging it up. i had no access to fastboot or EDL mode prior. once i got that 'plug in to charge' screen, i switched it to the wall charger, and left it to charge a bit (50-60%) from that state, then, i unplugged it again, and somehow, i managed to get edl mode to work by unplugging it and pressing all three buttons and holding them (typical edl boot).
once there, i reflashed via MiFlash an earlier build. i rolled back using MiFlash as far back as i could. in the process, i lost my imei and serial, which i have yet to successfully recover, but i did get out of DFU pergatory. the imei thing seems to be caused by going back to MM which i did on both of my IMEI-less a2017u boards, but im only guessing. my dd axon 7 is the only one of the three boards with imei and serial, so maybe MM is a bad idea. lol.
The first time i recovered from DFU, i did it inadvertently by letting the phone die and then flashing in EDL mode as well. (i left it for a few weeks as i had given up on it.) after it died completely, and i plugged ut up to the computer and had the same experience, I flashed the beta oreo build for a2017 using miflash. the screen had stopped responding. and i ended up doing a RMA. I now know the screen response thing was bc of a faulty EDL file of B15. (happened again to another of my axon, so i retraced my steps and realized it was when i flashed b15 that it died) . the fix if your screen ever stops responding, but isnt physically damaged? re-flash via EDL a different file. it may take a few tries, but eventually a build will work. for me, it was Marshmallow. I still do not know for certain, but that possibly is what killed my IMEI. but hey, it boots and the screen works.
I genuinely hope posting my idiocy in toying with axon 7s has helped someone out there.

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