Hi, i dont know what happened before this state but now it is not booting and anything show on the screen. Device Manager shows Qualcomm HS-USB QDLoader 9008. Can this phone work normally or it is fully dead? Thanks in any case.
Optimusik said:
Hi, i dont know what happened before this state but now it is not booting and anything show on the screen. Device Manager shows Qualcomm HS-USB QDLoader 9008. Can this phone work normally or it is fully dead? Thanks in any case.
Click to expand...
Click to collapse
You can always get it up and running as long as it's only the software issue. Have you tried using the Wugfresh Toolkit/ any other toolkit and connecting your phone? Have you tried to reboot to bootloader or recovery?
If you haven't already, press and hold volume up + power button until you see the bootloader then connect your phone to your PC and install the toolkit of your preference and install the stock Rom, follow onscreen instructions on your PC. Hope this helps.
superviked said:
You can always get it up and running as long as it's only the software issue. Have you tried using the Wugfresh Toolkit/ any other toolkit and connecting your phone? Have you tried to reboot to bootloader or recovery?
If you haven't already, press and hold volume up + power button until you see the bootloader then connect your phone to your PC and install the toolkit of your preference and install the stock Rom, follow onscreen instructions on your PC. Hope this helps.
Click to expand...
Click to collapse
I would try this with pleasure but its always black screen anytime. And phone recognized by computer only in that mode that i described
It is definitely hard bricked. QDloader mode = Hard Brick. But if Google has released the blankflash files for the N6P (Idk if they have or not), then you can recover.
Optimusik said:
I would try this with pleasure but its always black screen anytime. And phone recognized by computer only in that mode that i described
Click to expand...
Click to collapse
This is the closest I found related to your issue, however this is the guide to resolve the same issue but for the Nexus 5 Hammerhead. Someone needs to confirm if the N6P images can be flashed with the same method.
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
superviked said:
You can always get it up and running as long as it's only the software issue.
Click to expand...
Click to collapse
Not true.
superviked said:
This is the closest I found related to your issue, however this is the guide to resolve the same issue but for the Nexus 5 Hammerhead. Someone needs to confirm if the N6P images can be flashed with the same method.
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
Click to expand...
Click to collapse
The boarddiag tool is specific to LG devices. It will be of no use here.
This is the first post I've seen for Angler that has a Qualcomm HS-USB QDLoader 9008. If it starts to happen more people will start to look into a fix. Until then I'm afraid the OP is bricked.
I'm having similar issues. For some reason I can't get passed the white Google screen. I can see the phone when I plug it in, wugfresh toolkit can even flash it back to stock. Yet, it won't go past the Google,in white, loading screen.
Sent from my SM-T800 using XDA-Developers mobile app
Have you installed TWRP, have you been able to boot into recovery/bootloader via ADB?
---------- Post added at 12:02 PM ---------- Previous post was at 11:40 AM ----------
theesotericone said:
Not true.
The boarddiag tool is specific to LG devices. It will be of no use here.
This is the first post I've seen for Angler that has a Qualcomm HS-USB QDLoader 9008. If it starts to happen more people will start to look into a fix. Until then I'm afraid the OP is bricked.
Click to expand...
Click to collapse
What I meant was the phone is not completely dead. It's in a state of coma but not dead. There's a way, it could take time but this can always come back to life, but the OP will have to wait for device and storage specific files and the boarddiag/ tool to reflash image files manually.
superviked said:
Have you installed TWRP, have you been able to boot into recovery/bootloader via ADB?
---------- Post added at 12:02 PM ---------- Previous post was at 11:40 AM ----------
What I meant was the phone is not completely dead. It's in a state of coma but not dead. There's a way, it could take time but this can always come back to life, but the OP will have to wait for device and storage specific files and the boarddiag/ tool to reflash image files manually.
Click to expand...
Click to collapse
I dont know the history of this phone. It came to me in this state. Now i know that i have to wait blankflash from Google. Thanks everybody for the answers.
Qualcomm HS-USB QDLoader 9008. Having the same issue. Hope there's a fix soon. Heart broken.
robertputt said:
Qualcomm HS-USB QDLoader 9008. Having the same issue. Hope there's a fix soon. Heart broken.
Click to expand...
Click to collapse
I would like to know what did you do to cause the phone to brick? I got the phone a week ago and I'm thinking if I should root or not. I became scared after I bricked my Moto X 2014 and there's still no blankflash files for it :crying:
seco2004 said:
I would like to know what did you do to cause the phone to brick? I got the phone a week ago and I'm thinking if I should root or not. I became scared after I bricked my Moto X 2014 and there's still no blankflash files for it :crying:
Click to expand...
Click to collapse
I did it myself, was trying to patchrom miui for the phone and must have used a wrong boot file or bootloader file, corrupted emmc.
first time i've ever hard bricked a phone and been flashing stuff for years, once you follow guides and use tested files you should be fine. found someone here in ireland to repair it for me. Only one huawei repair centre here
Recently found myself in the same predicament.
mzahiri said:
I'm having similar issues. For some reason I can't get passed the white Google screen. I can see the phone when I plug it in, wugfresh toolkit can even flash it back to stock. Yet, it won't go past the Google,in white, loading screen.
Sent from my SM-T800 using XDA-Developers mobile app
Click to expand...
Click to collapse
Same thing with my girlfriends phone, have u manage to fix it ? Thanx
letmarebrmbarove said:
Same thing with my girlfriend phone, have manage to fix it ? Thanx
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Check in here. No solution (yet, hopefully), but you're not alone with this issue.
count me in!
Related
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...
Hello, as I've written my Nexus 6P is hard bricked. I've done a terrible mistake, flashing from TWRP recovery a pixel rom for the wrong telephone (I didn't notice there was written bullhead instead of angler). After rebooting, the telephone is dead, the display doesn't go. When I connect to my PC, it says there's something wrong with the device connected. I know I did something very stupid, but if there's a chance to get back my phone restored I will strongly thank you...
Is the phone able to cold boot into recovery or the bootloader?
redduc900 said:
Is the phone able to cold boot into recovery or the bootloader?
Click to expand...
Click to collapse
Well, actually I don't know, as the display is off... I only know that when connected to PC, keeping pushed the power off button I hear the sound of a new USB device.
So when you press the power+volume down buttons to boot into the bootloader, you don't see anything on the screen?
redduc900 said:
So when you press the power+volume down buttons to boot into the bootloader, you don't see anything on the screen?
Click to expand...
Click to collapse
No, nothing at all
Does the phone show up under Ports in Device Manager?
redduc900 said:
Does the phone show up under Ports in Device Manager?
Click to expand...
Click to collapse
This is what I get-->Dispositivo USB sconosciuto
(in English is "unknown USB device)
Did you try holding the power and volume down for at least 10 seconds? Or did you just press it?
---------- Post added at 12:45 PM ---------- Previous post was at 12:42 PM ----------
Did you try this? Or qsil/qfil?
emtkr said:
This is what I get-->Dispositivo USB sconosciuto
(in English is "unknown USB device)
Click to expand...
Click to collapse
Hello..
Head over this thread:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Install Qualcomm drivers. I guess your phone will likely show up as:
Qualcomm HS-USB QDLoader 9008 in device manager
If it's the case, try following the guide in the thread you found Qualcomm drivers...
Good luck...
I tried also this last method, but it didn't work. . So unfortunately I had To bring It to assistance this morning...
emtkr said:
I tried also this last method, but it didn't work. . So unfortunately I had To bring It to assistance this morning...
Click to expand...
Click to collapse
Sorry...
Hopefully you'll get it back, up and running!
I'm sure you'll be more careful flashing firmware in the future. :good:
Cheers...
DEVILOPS 007 said:
Did you try holding the power and volume down for at least 10 seconds? Or did you just press it?
---------- Post added at 12:45 PM ---------- Previous post was at 12:42 PM ----------
Did you try this? Or qsil/qfil?
Click to expand...
Click to collapse
5.1 said:
Hello..
Head over this thread:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Install Qualcomm drivers. I guess your phone will likely show up as:
Qualcomm HS-USB QDLoader 9008 in device manager
If it's the case, try following the guide in the thread you found Qualcomm drivers...
Good luck...
Click to expand...
Click to collapse
Surely.. I pay my big fault.. thank you very much
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
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
hello ,
I had installed rescurssion remix rom on my phone and i had decided to change to stock rom. So I give my mobile to a mobile shop and they repaired and changed to stock rom.!!!!actually the problem is......after the repair of my mobile in the mobile shop when I switch power on it directly go to boot loader instead of showing boot logo..After that when it shows the update I updated . It suddenly HARD BRICKED.Only the white light near fingerprint sensor worked while charging. please help meee...:crying::crying::crying::crying:
please help me to make my mobile in good condition ........by solving the boot loader issue which shows as the start up...
If I've read your post correctly, you used an OTA update and that's when you had the white light blinking? When you connect your device to your computer, what is your device recognised as? Is it recognised as Qualcomm HS-USB 9008 or similar?
If so, you may wish to look at this guide to try to get your device fixed: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Do you know what the shop did for the repair, what stock ROM did they flash to your device?
echo92 said:
If I've read your post correctly, you used an OTA update and that's when you had the white light blinking? When you connect your device to your computer, what is your device recognised as? Is it recognised as Qualcomm HS-USB 9008 or similar?
If so, you may wish to look at this guide to try to get your device fixed: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Do you know what the shop did for the repair, what stock ROM did they flash to your device?
Click to expand...
Click to collapse
yes it recognize as Qualcomm HS-USB 9008 something like that
the shop has installed rom with build number NPJS25.93-14-18.....I think its april 2018 update
charuvilapauljohn said:
yes it recognize as Qualcomm HS-USB 9008 something like that
the shop has installed rom with build number NPJS25.93-14-18.....I think its april 2018 update
Click to expand...
Click to collapse
actually i did not know what did hey doo
what to do for the start up problem ith always starts with the boot loader
charuvilapauljohn said:
actually i did not know what did hey doo
what to do for the start up problem ith always starts with the boot loader
Click to expand...
Click to collapse
I'm confused by what help you're asking for, as you appear to be asking for help on how to fix a hard bricked device, and yet also asking for help on your device starting with the bootloader. If your device is fully hard bricked, then you wouldn't have a bootloader to boot to... Can I thus ask please is your device still in a blinking light state or are you now booting to the bootloader?
I asked you also in your other post if using fastboot oem fb_mode_clear would work in clearing the bootloader start: https://forum.xda-developers.com/showpost.php?p=76927663&postcount=421 However, if your device is truly hard bricked (and is in the Qualcomm HS-USB 9008 mode), then you need to try the blankflash as linked above, then re-flash the stock ROM - the NPJS25.93-14-18 April 2018 fastboot ROM and guide is here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
thanks..it worked
It worked...thanks a lot...I installed NPJS25.93-14-18 rom....
Now there is another problem..both the sim and the finger print is not working
charuvilapauljohn said:
It worked...thanks a lot...I installed NPJS25.93-14-18 rom....
Now there is another problem..both the sim and the finger print is not working
Click to expand...
Click to collapse
That's because you phone model is changed to G4 only (not plus,) and lost 2nd IMEI... (Check in about section)
If it's changed to G4, follow,
Follow linked thread to solve: post #139, and better to read all posts to get correct information. (Turn pages to Download correct HW.img that's meant for your device model)
https://forum.xda-developers.com/mo...luss-model-changed-to-g4-lost-t3496912/page14
the hw.img file not working
____Mdd said:
That's because you phone model is changed to G4 only (not plus,) and lost 2nd IMEI... (Check in about section)
If it's changed to G4, follow,
Follow linked thread to solve: post #139, and better to read all posts to get correct information. (Turn pages to Download correct HW.img that's meant for your device model)
https://forum.xda-developers.com/mo...luss-model-changed-to-g4-lost-t3496912/page14
Click to expand...
Click to collapse
As I found a hw.img file for my xt1643.and i tried to install.The TWRP RECOVERY got struck.And the adb command prompt is not showing anything