Hardbricked to Qualcomm USB 9008 - Nexus 6P Q&A, Help & Troubleshooting

Really hoping someone can help me out here. I have a Nexus 6P, Non-BLOD. Yesterday, after clean flashing the latest version of EvoX, while setting some things up, device randomly crashed. No Shut down animation or anything. Just black screen. Tried turning it on via Power Button and then Power And Volume Buttons but nothing works. Connected it to PC and see it's Detected as Qualcomm USB Bulk (9008) in Coms and Ports. Did some research and found out I have to flash via QFIL. And this is where I am stuck. I tried several versions, but it doesn't flash/gives Shara error. I tried reinstalling driver. I also read a guide here. But the Firmware link is dead and it says to flash via MiFlash, something I can't even try since the Link in the OP is dead. I tried some different versions of QFIL but all of them give a Sahara Communication error. Now I'm pretty much at a loss on what to do. I'd really like to fix my 6P. And I would appreciate anyone taking the time to point me in the right direction, or help me fix it. Thanks in Advance.

DarthVader said:
Really hoping someone can help me out here. I have a Nexus 6P, Non-BLOD. Yesterday, after clean flashing the latest version of EvoX, while setting some things up, device randomly crashed. No Shut down animation or anything. Just black screen. Tried turning it on via Power Button and then Power And Volume Buttons but nothing works. Connected it to PC and see it's Detected as Qualcomm USB Bulk (9008) in Coms and Ports. Did some research and found out I have to flash via QFIL. And this is where I am stuck. I tried several versions, but it doesn't flash/gives Shara error. I tried reinstalling driver. I also read a guide here. But the Firmware link is dead and it says to flash via MiFlash, something I can't even try since the Link in the OP is dead. I tried some different versions of QFIL but all of them give a Sahara Communication error. Now I'm pretty much at a loss on what to do. I'd really like to fix my 6P. And I would appreciate anyone taking the time to point me in the right direction, or help me fix it. Thanks in Advance.
Click to expand...
Click to collapse
Same thing happened to me in the same ROM (Weird) .. but i managed to flash the qfil successfully .. but still phone doesnt boot up .. here's what you should do ... try to hard reset the phone until you hear the disconnecting sound from pc . Ready all the necessary flash in the qfil and as soon as u hear the device connected hit the download button .. it will flash without the sahara protocol error . Be quick ! tell me if that fixed ur problem . Peace

hk1271 said:
Same thing happened to me in the same ROM (Weird) .. but i managed to flash the qfil successfully .. but still phone doesnt boot up .. here's what you should do ... try to hard reset the phone until you hear the disconnecting sound from pc . Ready all the necessary flash in the qfil and as soon as u hear the device connected hit the download button .. it will flash without the sahara protocol error . Be quick ! tell me if that fixed ur problem . Peace
Click to expand...
Click to collapse
Thanks. Can you share the files you used please? I can't for the life of me, find the correct download files. There was a Nexus6P_Unbrick by TenFar but all the links are down.

DarthVader said:
Thanks. Can you share the files you used please? I can't for the life of me, find the correct download files. There was a Nexus6P_Unbrick by TenFar but all the links are down.
Click to expand...
Click to collapse
I used another qfil firmware
https://drive.google.com/file/d/1PixuumVVzxBKUsQ88X3AJ21Hsi2mV3Zq/view
Here is the link .. you can find the firehose and all files in the firmare folder . Best of Luck

I have a similar situation where I am unable to power on the phone in any way, and I am only able to communicate with the qualcom USB 9008 driver.
I am following your instructions using the firmware files you provided (thank you!) and I can see an attempt is being made to download the files before sahara error occurs.
I don't think I enabled developer options when my Nexus 6P was working and wondered if sahara error is due to that.
I was wondering if you had previously enabled developer options by tapping on the build number several times, once the operating system booted and if that is a critical step in being able to recover the Nexus 6p from this hard bricked state where I am stuck in EDL 9008 mode, and unable to access bootloader, and volume+power keys do not do anything...I feel like I'm screwed (and already moved on) but using time these days to learn about android devices!
thanks!

Related

Heavy Hard Brick Zuk Z1 international Version

HI everybody, I have a very big problem with my zuk. Trying to solve a problem about network, I thought to come back to stock via fastboot. But given that I was tired doing so many tries, I wrongly flash a zip file via fastboot instead of use adb, so the phone didn't turn on anymore. I must say first of all that it isn't my first phone, so I'm not a newbie. The real problem is: When I plug Zuk into my Pc( Windows 10) it isn't recognized as qhsusb_bulk ( It could be easy to solve the problem) but as "unknown usb device (Device Descriptor Request Failed)". I try to plug the phone pressing every button like Vol+ and power, Vol- and power but nothing to do. I' m already in Test Mode on Windows 10 and I deleted every Zuk or Qualcomm Drivers. Anyone can help me?
Thank you
Ps: Even If the screen is always off, Is there a way to boot into fastboot mode with hardware keys?
Xluk3 said:
HI everybody, I have a very big problem with my zuk. Trying to solve a problem about network, I thought to come back to stock via fastboot. But given that I was tired doing so many tries, I wrongly flash a zip file via fastboot instead of use adb, so the phone didn't turn on anymore. I must say first of all that it isn't my first phone, so I'm not a newbie. The real problem is: When I plug Zuk into my Pc( Windows 10) it isn't recognized as qhsusb_bulk ( It could be easy to solve the problem) but as "unknown usb device (Device Descriptor Request Failed)". I try to plug the phone pressing every button like Vol+ and power, Vol- and power but nothing to do. I' m already in Test Mode on Windows 10 and I deleted every Zuk or Qualcomm Drivers. Anyone can help me?
Thank you
Ps: Even If the screen is always off, Is there a way to boot into fastboot mode with hardware keys?
Click to expand...
Click to collapse
Not that I know,do you have the stock recovery or twrp?
I have the exact problem with my new zuk z1. Any idea is appreciated. The nice phone seems lost now.
Seems like you'll have to restore your zuk to the zui version again. Do you have qrst and zui version downloaded??
The service port never pops up
I do have the qpst and the zui rom. The main obstacle is that qualcomm service port never pop up.
Setup.zuk said:
I do have the qpst and the zui rom. The main obstacle is that qualcomm service port never pop up.
Click to expand...
Click to collapse
try this:
start QFIL from the QPST folder
Click browse on the programmer path row and select prog_emmc_firehose_8974.mbn from the directory where you unzipped the QPST ZUI ROM
and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone,
you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable
and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default.
On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings),
scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option
to change language to english incase you cant make out the chinese and you should be good to go
Nikosstamatiou said:
try this:
start QFIL from the QPST folder
Click browse on the programmer path row and select prog_emmc_firehose_8974.mbn from the directory where you unzipped the QPST ZUI ROM
and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone,
you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable
and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default.
On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings),
scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option
to change language to english incase you cant make out the chinese and you should be good to go
Click to expand...
Click to collapse
So i am having the same problem. The phone is not being recognized by the software. That is the whole problem. Any ideas?
Tarsa said:
So i am having the same problem. The phone is not being recognized by the software. That is the whole problem. Any ideas?
Click to expand...
Click to collapse
Actually, I think the problem is, that it will not reach the fastboot mode, due to the non-stop process of system-updating and boot-loop. I can observe for a very short time the message 'systemupdate will be installed' and then the screen becomes black again. This procedure is repeating every time. I will wait till the battery is empty and see, whether the boot with Volume-+--USB-cable will work.
mikarbach said:
Actually, I think the problem is, that it will not reach the fastboot mode, due to the non-stop process of system-updating and boot-loop. I can observe for a very short time the message 'systemupdate will be installed' and then the screen becomes black again. This procedure is repeating every time. I will wait till the battery is empty and see, whether the boot with Volume-+--USB-cable will work.
Click to expand...
Click to collapse
PLease do update me if you manage to fix it. This is getting very frustrating
I have the same problem, caused after a cyanogenmod update... Did someone fix this??
Another hard bricked Z1 here.
QFIL recognizes the phone (as Qualcomm 9008 etc.). So I am able to click Download, but after a few seconds, it fails with these errors:
Code:
[...]
Sending NOP
NOP: Fail Code: 9
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
in QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
in QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
I've tried many many times, and many different things. Still no luck .
I'd appreciate if anyone could input some new ideas of other stuff to try. Thanks
CarlosAir said:
Another hard bricked Z1 here.
QFIL recognizes the phone (as Qualcomm 9008 etc.). So I am able to click Download, but after a few seconds, it fails with these errors:
Code:
[...]
Sending NOP
NOP: Fail Code: 9
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
in QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
in QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
If tried many many times, and many different things. Still no luck .
I'd appreciate if anyone could input some new ideas of other stuff to try. Thanks
Click to expand...
Click to collapse
No idea, my device is actually dead.
mikarbach said:
No idea, my device is actually dead.
Click to expand...
Click to collapse
Aw .
I don't want to lose hope, but everything I've tried so far has failed. :| , and I don't know what else to try.
CarlosAir said:
Aw .
I don't want to lose hope, but everything I've tried so far has failed. :| , and I don't know what else to try.
Click to expand...
Click to collapse
Try another cable, another USB slot, another pc/laptop
mikarbach said:
No idea, my device is actually dead.
Click to expand...
Click to collapse
try to flash cos 12.1 with qfil.
its there somwhere on 4pda forum(search there).
Sent from my Z1 using XDA-Developers mobile app
So guys if I try to flash unofficial CM 13 do I risk bricking the device for good???
t.h.i said:
try to flash cos 12.1 with qfil.
its there somwhere on 4pda forum(search there).
Sent from my Z1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Of course I have tried this, with two different computers and two different USB cable, both actually working on my N5X. But the point is, that I do not reach the point, that qfil recognizes the phone. Also not with the trick of starting with power-button/USB-cable. It constantly tries to reboot and with adb I get a message 'not authorized' .
---------- Post added at 11:17 AM ---------- Previous post was at 11:05 AM ----------
carlese said:
So guys if I try to flash unofficial CM 13 do I risk bricking the device for good???
Click to expand...
Click to collapse
I think in my case the after the first successful CM13-snapshot-installation was two fold:
1. I have not enabled USB-debugging and do not have had connected it to my computer after the first CM13-installation.
2. Due to some unknown reason the automatically update via CM itself has boot looped.
The second point is not a real problem, I think. I have had a bootloop many times before with other phones, as well as with the Zuk, but I was always able to resolve the problem with adb. I think the first point was the problem, so adb wasn't possible, due to authorization problems. The reason why qfil does not work, I really do not know exactly, but qfil in fact was not able to recognize the phone.
I have the same problem. Totally bricked.
No charge, no PC recognise, nothing.
I tried with QFIL but the PC does not recognise the port.
I don't know what else I can do. Any ideas?
Thanks!
alexisdance said:
I have the same problem. Totally bricked.
No charge, no PC recognise, nothing.
I tried with QFIL but the PC does not recognise the port.
I don't know what else I can do. Any ideas?
Thanks!
Click to expand...
Click to collapse
Sry, no I do not have
Hello!
I have dealt with this sort of problem before and have successfully un-bricked my friend's device. I will be posting a guide to solve this problem soon.
Hang-on!

[Hard Brick] Nexus 6P 7.1.2 Beta 2 [Solved]

Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
@rmorris003
You said the phone won't even power on. You mean no Google? Hold the power button down for a couple of minutes and see if it will reboot. If not put it on a charger, and after fully charging try the long press power button again. If you can get it to start, try to put it in fastboot mode. (ie. power+vol dn). If you can get to bootloader you can send fastboot commands and fix it. If you can get to this point, there are instructions here.
rmorris003 said:
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
Click to expand...
Click to collapse
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
5.1 said:
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
Click to expand...
Click to collapse
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
rmorris003 said:
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
Click to expand...
Click to collapse
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
5.1 said:
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
Click to expand...
Click to collapse
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
rmorris003 said:
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
Click to expand...
Click to collapse
You disabled driver signature and rebooted your computer? Then installed Qualcomm drivers from the thread I linked you to? I think you have to reboot your computer once more...
Good luck...
I held the power and vol down and now it shows up under com ports so this is a good sign.
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
rmorris003 said:
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
Click to expand...
Click to collapse
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
5.1 said:
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
Click to expand...
Click to collapse
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
You could report your experience in the other thread. Maybe it could help other users who faced the issue you had. :good:
Cheers...
rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
Falitheman said:
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Click to expand...
Click to collapse
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
5.1 said:
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
Click to expand...
Click to collapse
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Falitheman said:
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Click to expand...
Click to collapse
Hey,
What version of qpst did you install?
Good luck...
5.1 said:
Hey,
What version of qpst did you install?
Good luck...
Click to expand...
Click to collapse
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Falitheman said:
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Click to expand...
Click to collapse
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
5.1 said:
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
Click to expand...
Click to collapse
I tried with the version you suggested and i got the same error i just had. Can you send me your version so i can see if that works?

Lenovo k6 Power Hard Bricked.

No Fastboot, No Recovery, No Download Mode, just a black screen. All Partitions of Phone got deleted. Pc is only detecting it as "Qualcomm HS-Usb Diagnostic 900E(Com10)" but unable to flash stock firmware. Getting the following error in Qfil.
...
"Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode".
Phone is also heating up as it have no OS installed.
I also faced this same problem in the past but i was able to recover my phone. Right now i don't remember how i did it but give me some time to think about it. I am sure someone else will help you just don't give up!!
Go to this link and try to follow their tutorial. It might help you.
https://firmwarefile.com/lenovo-vibe-k6-power-k33a42
ImSSin said:
I also faced this same problem in the past but i was able to recover my phone. Right now i don't remember how i did it but give me some time to think about it. I am sure someone else will help you just don't give up!!
Go to this link and try to follow their tutorial. It might help you.
https://firmwarefile.com/lenovo-vibe-k6-power-k33a42
Click to expand...
Click to collapse
Thank You ?
I am also trying my best to recover the phone and i will write here so that anyone who is facing this issue can recover his/her Phone.
No Solution found for this.
...
You have to send your Lenovo K6 Power to Lenovo Service Centre and get your Motherboard replaced.
If your phone is in guarantee then you will get free replacement no matter if your phone is rooted but please don't tell about root to them otherwise they will charge money for your small mistake.
what happened?
Do a new install
faizynadim said:
No Fastboot, No Recovery, No Download Mode, just a black screen. All Partitions of Phone got deleted. Pc is only detecting it as "Qualcomm HS-Usb Diagnostic 900E(Com10)" but unable to flash stock firmware. Getting the following error in Qfil.
...
"Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode".
Phone is also heating up as it have no OS installed.
Click to expand...
Click to collapse
Boss it seems that you have hard bricked your phone so it means it's first boot has been corrupted there is no chance as first boot is mandatory to flash any file, there are some tools like octopus, or Medusa box, they can repair your boot then the phone can be used its just an outside chance 5o get it in workable condition look for some person or Repairing person have this boot repairing gadget,
If this fails too or you have messed up very badly then, last option is mother board replacement, there is no software option to repair by yourself
Help please..!!!!
:crying:
Even I face the same problem...
How do I go to download mode..???
It's stuck at Lenovo screen .... It just turn off on low battery and reboots on long press of power button.. Is it compulsory to have 80% of charge to get into download mode..???
i did the same. it switches on with lenovo logo , shows the os logo animation and its stuck there. when i tried connecting it to phone it showing unspecified device.
i could get into a fastboot mode . but nothing ahead to that. please find me a solution
Help me same issue
faizynadim said:
No Fastboot, No Recovery, No Download Mode, just a black screen. All Partitions of Phone got deleted. Pc is only detecting it as "Qualcomm HS-Usb Diagnostic 900E(Com10)" but unable to flash stock firmware. Getting the following error in Qfil.
...
"Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode".
Phone is also heating up as it have no OS installed.
Click to expand...
Click to collapse
Did you find any solution for this, present i'm facing same issue, please tell me if you have any solution for this...

I'm trying to unbrick my x720 by QFIL but my pc won't recognize Qualcomm 9008 port

My problem is that I can't even try to do the procedure in the other threads that i've read because my pc simples dont recognize anything when i install the qualcomm drivers. Any tips? Thank you in advance. I want to try this thread [GUIDE][QFIL MODE]Unbrick your Le Pro3, tested and working. But simply the qualcomm port doesnt appear in the device manager.
Bad cable or need to reinstall drivers...
marik1 said:
Bad cable or need to reinstall drivers...
Click to expand...
Click to collapse
I tried with two different cables and reinstalled the drivers a few times now. No port in the device manager. Just the Android ADB Interface tha showed when I installed the leeco adb drivers. On the ports just appear the standard Comunication port and printer port. I tried everything, the volume bottons power, etc. The Flash One dont recognize the phone for QFIL.
Say sth more about your phone state and history...
marik1 said:
Say sth more about your phone state and history...
Click to expand...
Click to collapse
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
I've no idea how to help you... Sorry.
gradim said:
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
Click to expand...
Click to collapse
Instead of creating a new post why not just read the enormous unbrick forums that exists and have proven steps. Many, Many phones have been debricked using those steps.
Hint, read the last pages for updated links to the software tools needed.
Next, I just found this cable which will help immensely with unbricking your device: https://www.amazon.com/GPG-EDL-Cabl...r1&keywords=edl+cable+for+wall+qualcomm+usb+c
tsongming said:
Instead of creating a new post why not just read the enormous unbrick forums that exists and have proven steps. Many, Many phones have been debricked using those steps.
Hint, read the last pages for updated links to the software tools needed.
Next, I just found this cable which will help immensely with unbricking your device: https://www.amazon.com/GPG-EDL-Cabl...r1&keywords=edl+cable+for+wall+qualcomm+usb+c
Click to expand...
Click to collapse
I've tried four different cables now and nothing. Thank you for minding but I think there isn't a solution for my leeco. Its dead and no one can help him.
Is yours 722?
Sent from my SM-A730F using xda premium
mchlbenner said:
Is yours 722?
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
No, x720 6gb ram 64 rom.
gradim said:
No, x720 6gb ram 64 rom.
Click to expand...
Click to collapse
Is your phone completely Dead or do you have fashboot or anything working.
Do have a red flashing light?
Sent from my SM-A730F using xda premium
mchlbenner said:
Is your phone completely Dead or do you have fashboot or anything working.
Do have a red flashing light?
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
Completely dead, just vibrates when I press power and yes, I sometimes have the red light, sometimes flashing, sometimes stable.
gradim said:
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
Click to expand...
Click to collapse
Your phone is probably fixable.
Based on what you stated above, it seems that you downloaded and attempted to install the wrong version of TWRP and now your phone has no recovery at all.
Here is partial instructions I posted in the unbricking forum : https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
Use those instructions along with is mentioned below. I have personally helped so many people unbrick their phone that I have lost track and this is the reason why the posts are so long and extensive. Because sometimes what works for one person does not work for the next. So I have essentially have taken everyone's great advice and updated the links, made the instructions steps a little more concise and easier to read, fixed some incorrect steps or added the needed skipped steps. Plus added my own research into what I believe is now a definitive guide for unbricking the Leeco variants X720 and X727. The point of not reposting the information here is to keep everything from becoming more fragmented.
Yes, it's possible that you have a hardware issue. But, its also possible that it can be fixed!
Remember that you will not see the port unless you are in EDL mode
Just press volume △ (+) and volume ▽ (–) buttons together while powering the phone on.
It should now be EDL mode. If you cannot get into EDO mode, you cannot do anything else.
If you get an error, press and hold the power button while at the same time hold vol up + and down simultaneously plug the usb cord into the back of the computer while holding the buttons.
Yes, It's a pain and this is why the deep flash cable is handy....it's a special cable ( so your extra cables will do nothing to help you) The deep flash cable will automatically put your phone into EDL mode and allow you to use Flash on.
Install the Qualcomm QDLoader 9008 driver: https://goo.gl/9E3bKq or the from links provided in the unbrick forum.
There are multiple versions or Qfil, some have issues. I posted the correct one that works.
FOR anything else go to that forum read my and everyone else's posts. Again, I keep all of my linked files are up to date, and many are located on my own drives.
You can make one of these cables. Here's a video that shows you how:
https://www.youtube.com/watch v=kSiGsYK66gM&lc=z220yhtqvwyyct21pacdp432sh2xjecek10dae1jen5w03c010c.1524884617336803
it will not be a quick fix.
There are 4 or 5 different unbricking options and it requires persistence and patience.
The good news is that your phone has a solution that may work.
So when your where flashing a rom you got error 7 and your phone went dead.
I had gotten that same error.
Error could mean two things 1) update recovery or update firmware.
My point is sounds nice like hardware issue.
These phones are known for just dieing.
Also getting into that mode you have to push power+volume+volume- at the same time.
Sent from my SM-A730F using xda premium

Phone bricked, cannot flash because it randomly plugs/unplugs when connected to PC

Hey, first time posting here but a long time lurker. Amazing community from what I've experienced.
Yesterday, my phone bricked out of the blue, not turning on and showing a rapidly blinking LED. It refuses to charge, and when plugged to a computer, it displays in the device manager as a Qualcomm 9008 device.
So far I've tried unplugging the battery once, holding down the power button for three minutes straight, holding down volume- and power button, and none worked.
Apparently, flashing the phone seems to work for a lot of people, but I cannot do it because my phone randomly disconnects and then reconnects to my computer, repeatedly. This happens every 20 seconds or so.
I've tried using different ports, uninstalling then reinstalling drivers, resetting my PC, using a different cable, but nothing helps.
I've got a big trip tomorrow, and I don't want to go away with a dead phone. What can I do?
Update: tried cleaning the phone's USB port and the USB itself, no luck.
You got into EDL mode, search for guides how to use it (basically install correct drivers, flash ROM, reboot).
_mysiak_ said:
You got into EDL mode, search for guides how to use it (basically install correct drivers, flash ROM, reboot).
Click to expand...
Click to collapse
I know it's in EDL mode and I've looked into every single guide I could find, that's why I'm posting here.
Nothing so far has worked and I'm trying to flash the phone to see if it works, since an user here posted a youtube video of someone using MiFlash to get the phone back working.
The issue is that my phone has micro-disconnects when USB plugged to my computer every 20-30 seconds, and because of that I cannot flash it.
Do you have correct drivers installed? Fastboot mode reboots after ~30s if there are no drivers installed. Might be the same for EDL.
_mysiak_ said:
Do you have correct drivers installed? Fastboot mode reboots after ~30s if there are no drivers installed. Might be the same for EDL.
Click to expand...
Click to collapse
I downloaded them from xiaomigeek (cannot share the link due to post count), as suggested in another thread.
Also I tried installing them automatically through Windows device manager, but I still have the same issue.
Hm, don't know then.. Maybe someone else experienced something similar and can help.
Small update, cleaning both the device and the USB ports with a brush and alcohol does nothing to prevent the "micro-disconnects".
KurisuSama said:
Small update, cleaning both the device and the USB ports with a brush and alcohol does nothing to prevent the "micro-disconnects".
Click to expand...
Click to collapse
Buddy those disconnects are not because of dirty port.. cleaning wont help..i actually had this problem with my first gen android phone it disconnects every 5 secs.. but once i hit flash in sp flash tool(mtk flasher) it stops disconnecting and starts receiving rom packets without problem
apexashwin said:
Buddy those disconnects are not because of dirty port.. cleaning wont help..i actually had this problem with my first gen android phone it disconnects every 5 secs.. but once i hit flash in sp flash tool(mtk flasher) it stops disconnecting and starts receiving rom packets without problem
Click to expand...
Click to collapse
Any resources where I could try this on the Mi A1?
Edit: correct me if I'm wrong, but after a bit of searching it seems I'm not unable to find a guide because there isn't one, but because sp flash tool isn't compatible with my phone.
Use another pc may be. Or another USB cable
.:Addicted:. said:
Use another pc may be. Or another USB cable
Click to expand...
Click to collapse
Tried both.
The cable doesn't seem to be the issue as a different cable yields the same results and another phone I've tested doesn't have any issues with it.
And I tried doing this on my laptop instead of my desktop PC, then on my roomate's PC, but the same thing happens.
KurisuSama said:
Any resources where I could try this on the Mi A1?
Edit: correct me if I'm wrong, but after a bit of searching it seems I'm not unable to find a guide because there isn't one, but because sp flash tool isn't compatible with my phone.
Click to expand...
Click to collapse
Sp flash tool is for phones with mtk CPU's only brother.. could u try different pc? Or try flashing via cmd?
---------- Post added at 04:25 AM ---------- Previous post was at 04:21 AM ----------
Btwn have u tried flashing the phon via miflash? Or u didn't cuz it disconnects? Well what happened to me is *I didn't even try to flash the phone with sp flash tool for 5 straight months cuz i thought its impossible to flash when it disconnects like this...but when i finally consoled myself to give it a try it flashed all the way to 100% without any problem..uh the phone stops disconnecting once the software pushes few packets to the phone
I have the same problem :/
If take to warranty they ill help or not?
Go into edl mode. Edit xml file that store info about partitions. Select few necessary. (like bootloader & idk about what other partition needed for sure, but just telling you to exclude big partition like system. You do your research on that. May be cosmicDan can tell you what partition you need to enter fastboot)
Im hoping you will be able to flash small partition.
So you can get into fastboot. Then try to boot twrp in fastboot to flash all partition from twrp image shared in xda. (May be use memory card & flash twrp image from there)
Good luck
this help me without remove battery http://en.miui.com/thread-1680467-1-1.html
i install driver qualcoom, after flashed rom and after i hold button power and work

Categories

Resources