Database Info

[Q] Phone won't turn on after nandroid backup+ firmware update

Solved: See post below.
So I decided to go back to Kitkat from Lollipop. To do this I went into TWRP and restored a 38R backup I made when I first got the phone in November. TWRP did its thing and booted back into 11S 38R and it seemed to work. What then happened was that I was prompted to update to 44S so I did and the phone rebooted into TWRP. TWRP came up with some sort of screen, I can't remember what it said but the last line said something about an MD5 check not beeing needed. It then turned off and I haven't been able to get it back on. I've tried holding down the power button on its own and after around 5 seconds it vibrates but nothing happens. Also when I plug it into my PC or charger the charging light doesn't turn on.
I've tried to get into recovery and fastboot mode by holding power button+up/down volume but nothing happens on screen but I still get a vibration. However when I press volume button up+power button it seems to be recognised in Windows and it brings up the device as "QHSUSB_BULK" but that is it.
Does anyone know how to fix this?
P.S: I've got a nandroid backup + modem backup from when I first got the phone available if that helps.

I was able to fix the issue using the Oneplus Recovery tool. The issue was that the phone was not being recognised by my PC despite installing the drivers included in the recovery tool. This post in the recovery tool thread had the answers:
"I also deactivate unsigned driver installation but still same fail... I found a Qualcomm HS-USB QDLoader 9008 2.1.0.5 for Windows 7 that I used. I opened the Device Manager, I found my device named QHSUSB_BULK with an yellow triangle. I pressed udate drivers , choose from computer and installed that Qualcomm HS-USB QDLoader 9008 2.1.0.5 I donwloaded. AFTER THAT the tool found my phone and I was manage to flash ROM took me half a day. I cant have done wrong , somethnig must be wrong with the drivers in the tool for w7 64bit or something . this was the first time I have hard bricked a phone EVER and I have flashed a lot . But im glad it worked out with that Qualcomm HS-USB QDLoader 9008 driver since that guy also had same problem as me and later got it to work with that driver. Qualcomm HS-USB Drivers"
http://forum.xda-developers.com/showpost.php?p=58074662&postcount=40
So that was how I fixed it.
Why it broke in the first place is a mystery but I'm just glad to be back on Kitkat 44S.

[Q] Bricked. Erased/messed up bootloader. Win recognized as "HS-USB QDLoader 9008".

[Q] Bricked. Erased/messed up bootloader. Win recognized as "HS-USB QDLoader 9008".
Hello.
Finally I hard bricked my Photon Q. I think I erased an unlocked bootloader. Right now phone cannot boot into fastboot mode. Power+Vol up, Power+Vol down held long do nothing. After connecting to Windows PC, phone is recognized as "HS-USB QDLoader 9008". I found drivers on the net. RSDlite recognizes device, but flashing fails with message that it cannot switch phone from download mode. I found QPST service software used to flash bootloader. Right now I think the problem is that I don't have proper bootloader images for Photon Q, and to be honest, I don't really know what options to use (the software seems quite complicated).
Has anyone encoutered (and solved) similar issues? Do you have any ideas, what to do? I tried some generic Qualcomm files, but couldn't flash them.
Anyone, please, help me, if you can.
Chris

Hardbricked OnePlus One Doesn't Get Recognized by RestoreTool

Hi all,
I have a OnePlus One that's hardbricked (it doesn't show any forms of life).
I followed this guide, but I'm stuck. I installed QPST Drivers, and Qualcomm 2012 Drivers (although after installing this one, I get a message stating that the newest drivers are already installed.).
At the moment, my device is recognized in device manager as "Qualcomm HS-USB- QDLoader 9008 (COM10)" and sometimes it doesn't get recognized at all. The device manager will then say "unknown device".
When the device is recognized as "Qualcomm HS-USB- QDLoader 9008 (COM10)", it doesn't get recognized by the OnePlusRestoreTool (even if I run it in administrator mode).
I'm using Windows 7.
Could any of you perhaps help me find a solution?
Thanks in advance!
Robert

Asus x014d bricked phone! problem with unbrick :(

SITUATION:
hello , My phone is an asus x014d. recently I switched it off , and it just would not boot up again.
when i press the power on button it shows "powered by android" then the "asus" logo.
PROBLEMS:
- I CANNOT ENTER RECOVERY MODE (by doing the power on + vol up)
- I CANNOT ENTER TO FASTBOOT
- Device manager only identifies device as "qualcomm hs-usb diagnostics 9006" instead of "qualcomm hs-usb diagnostics 9008"
- when QFIL for unbricking it yields error "sahara fail"
- when using eMMC software Download the errors i get are "timeout waiting" , box dialog "cookie(if present) not received"
- managed to get into qualcomm hs-usb diagnostics 9008 mode but i can only manage to do that after getting to 9006 then flashing stock rom with RAW HDD TOOL then i am able to get into 9008.
TL;DR - DESCRIPTION (**NOOB ALERT**)
after research , i found out that my phone is bricked. i learnt that i have to get my phone identified by the computer through the "qualcomm usb drivers" then flash through "QFIL" a tool used for unbricking devices that have qualcomm processors.
i was able to successfully install the drivers , and plug my phone to the pc it shows that it is charging so i press the power plus volume up , then phone switches off and device manager never shows me the "qualcomm hs-usb diagnostics 9008" unless after switching off i immediately press volume down then device manager shows me "qualcomm hs-usb diagnostics 9006".
QPST will not flash the device if it is on "qualcomm hs-usb diagnostics 9006" so i learnt how to format the eMMC with raw HDD tool and whenever i formatted the eMMC with the stock rom , the pc would identify the device under PORTS > "qualcomm hs-usb diagnostics 9008"
when using QPST i am given the error "sahara fail" , and when using eMMC software downloader i get the error "cookie not received" and sometimes timeout.
i cannot attempt to get my phone to revive my phone (it sticks on a logo and when it is completely off and plugged in it shows a battery charging animation).
- any insight on how to solve this?
- Is it a Software issue that can be solved without the intervention of hardware? is my issue strictly a hardware issue? (e.g malfunctioning logic board)?
i am ready to provide images and files or any further clarification if needed.
any help or guide into this issue would be greatly appreciated thanks for investing time into helping me and others.

AdelTheConfused said:
SITUATION:
hello , My phone is an asus x014d. recently I switched it off , and it just would not boot up again.
when i press the power on button it shows "powered by android" then the "asus" logo.
PROBLEMS:
- I CANNOT ENTER RECOVERY MODE (by doing the power on + vol up)
- I CANNOT ENTER TO FASTBOOT
- Device manager only identifies device as "qualcomm hs-usb diagnostics 9006" instead of "qualcomm hs-usb diagnostics 9008"
- when QFIL for unbricking it yields error "sahara fail"
- when using eMMC software Download the errors i get are "timeout waiting" , box dialog "cookie(if present) not received"
- managed to get into qualcomm hs-usb diagnostics 9008 mode but i can only manage to do that after getting to 9006 then flashing stock rom with RAW HDD TOOL then i am able to get into 9008.
TL;DR - DESCRIPTION (**NOOB ALERT**)
after research , i found out that my phone is bricked. i learnt that i have to get my phone identified by the computer through the "qualcomm usb drivers" then flash through "QFIL" a tool used for unbricking devices that have qualcomm processors.
i was able to successfully install the drivers , and plug my phone to the pc it shows that it is charging so i press the power plus volume up , then phone switches off and device manager never shows me the "qualcomm hs-usb diagnostics 9008" unless after switching off i immediately press volume down then device manager shows me "qualcomm hs-usb diagnostics 9006".
QPST will not flash the device if it is on "qualcomm hs-usb diagnostics 9006" so i learnt how to format the eMMC with raw HDD tool and whenever i formatted the eMMC with the stock rom , the pc would identify the device under PORTS > "qualcomm hs-usb diagnostics 9008"
when using QPST i am given the error "sahara fail" , and when using eMMC software downloader i get the error "cookie not received" and sometimes timeout.
i cannot attempt to get my phone to revive my phone (it sticks on a logo and when it is completely off and plugged in it shows a battery charging animation).
- any insight on how to solve this?
- Is it a Software issue that can be solved without the intervention of hardware? is my issue strictly a hardware issue? (e.g malfunctioning logic board)?
i am ready to provide images and files or any further clarification if needed.
any help or guide into this issue would be greatly appreciated thanks for investing time into helping me and others.
Click to expand...
Click to collapse
Try with official ASUS drivers or, try to use the com port mounted on the back of the motherboard, maby.. i wouldnt suggest it to use to com port. it would require some hardware knowledge

HOW TO UNBRICK THIS LG G2?

Hi everyone,
I have a second device as LG_G2 D802 and i gave it to a my friend. He said he rooted it and after a while bricked it.
Phone is not turning on normally, lights green and blue, LG logo appears and after a short while the phone is restarting. I can only enter download mode.
I've tried some options with using XDA topics but i couldn't solve it unfortunately. The last situation is: pc doesn't detect phone in download mode.
With short circuit, sometimes it seems as Qualcomm HS-USB Diagnostics 9006, sometimes Qualcomm HS-USB QDLoader 9008 in device manager.
I used SRK TOOL for 9006, it finished successfully but when i unplugged phone and plug battery and plug usb and enter in download mode, pc didn't detect phone, any devide, etc.
I used Boarddiag for 9008, AP TEST: Successful EMMC TEST: Successful SDRAM TEST: Successful, all process is successful. But again, in download mode, PC doesn't detect anything of the phone.
In the videos I watched, after successful SRK TOOL or Boarddiag processes, pc must detect phone in download mode but the same thing didn't happen to me
I used Win 8.1 64 bit and Win 7 X86, but same thing happened. Stuck in pc detecting problem in download mode. I installed drivers, too.
Is there anything that can be done about it?
Does anyone have an idea?
Thanks.