Hi!
I Have a problem with my wife's OnePlus 3:
It is an OnePlus 3 64 gb with bootloader unlocked. It remained without battery, shutted down and when it was plugged again in the charger, hothing happened.
I swapped her motherboard in my phone and the issue is the same so i am excluding a battery issue. I plugged the phone in my pc and in control panel it appears like in the photo that I will attach below. It did not let me install any driver, the driver was automatically installed. I followed the guide for OnePlus 3 and downloaded "OnePlus3_Unbrick_Tool_Mini_androidbrick". The process was ok, it finalized with a green message but the phone is still dead. It disconnects and when I try to power it up nothing happens. If I connect it again, in control Panel it appears again like QDLoader 9008.
What am I doing wrong??
Thank you!
Happend to me a few days ago also had Qualcomm HS-USB QDLoader 9008' in device manager,
restored it whit this guide:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
Download what they tell you to and start from step 9, also ignore step 14.
I did it now. Followed all the steps and still no image on the screen, no leds turning on. The screen is fine, I tested it with my board.
What can be wrong with this phone??
You said that you swapped the board but your conclussion is that the battery is not the problem.
I'm very confused with that statement.
myhay_grm said:
Hi!
I Have a problem with my wife's OnePlus 3:
It is an OnePlus 3 64 gb with bootloader unlocked. It remained without battery, shutted down and when it was plugged again in the charger, hothing happened.
I swapped her motherboard in my phone and the issue is the same so i am excluding a battery issue. I plugged the phone in my pc and in control panel it appears like in the photo that I will attach below. It did not let me install any driver, the driver was automatically installed. I followed the guide for OnePlus 3 and downloaded "OnePlus3_Unbrick_Tool_Mini_androidbrick". The process was ok, it finalized with a green message but the phone is still dead. It disconnects and when I try to power it up nothing happens. If I connect it again, in control Panel it appears again like QDLoader 9008.
What am I doing wrong??
Thank you!
Click to expand...
Click to collapse
try hard bricked full tool, i done it with mini but only succeeded by full tool
Agreed. I had successfully restored the phone using the method 2 mentioned by Naman Bhalla in his XDA thread. For some people, it required multiple attempts with method 2 though I succeeded in the first attempt.:fingers-crossed:
jeffrey268 said:
Happend to me a few days ago also had Qualcomm HS-USB QDLoader 9008' in device manager,
restored it whit this guide:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
Download what they tell you to and start from step 9, also ignore step 14.
Click to expand...
Click to collapse
I managed to do every step correctly.
However at the end after the MSM tool finished, I unplugged my phone and it went to boot up, but I got this message:
https://imgur.com/a/niyuR0Z
Any ideas?
koreyg said:
I managed to do every step correctly.
However at the end after the MSM tool finished, I unplugged my phone and it went to boot up, but I got this message:
https://imgur.com/a/niyuR0Z
Any ideas?
Click to expand...
Click to collapse
Can u get to fastboot screen?
Related
So I bought a used G3 knowing about the issue it had; it didn't boot. I thought I could find a workaround to this but the phone doesn't boot, doesn't enter recovery or download mode. All the info I have is that when I take off the battery the pc sees it as an unknown device, while it's connected I press the power button for several seconds and it disconnects from the pc, reconnects after several more seconds of pressing the power button. Screen remains dead. Seller told me he had a perfectly working phone before he tried to root it and it never turned on again. One more indication is that the LED notification only flashed red a few times when I connected it to the wall charger and that was it. No LED working after that. I'm open to any suggestions though I guess I'm here for someone to tell me there's no hope reviving the device. Thanks in advance!
Same proble with mine but i bricked mines when update to lollipop and never turn on again . still waiting to some one help to revive my LG
If I come across any solution I'll post it here. In the meantime I've tried the following method on a freshly formatted laptop and I still get "Unknown Device" in Device Manager..
http://forum.xda-developers.com/showthread.php?t=2785089
same here
same problem, someone told me that if was the board or something like that and that it only can be fixed with a complete replacement of this, also, that it could be fixed with linux using comands to install .APK or .TOT.
linux sometimes sees it as Qualcomm CDMA Technologies MSM QHSUSB_BULK, using a virtual machine of linux ubuntu, windows 8.1 sees it as unknow device
LG dead since 3 months ago.................. i wasnt using the phone at all when this happended so........... :crying:
jc.delgado11 said:
same problem, someone told me that if was the board or something like that and that it only can be fixed with a complete replacement of this, also, that it could be fixed with linux using comands to install .APK or .TOT.
linux sometimes sees it as Qualcomm CDMA Technologies MSM QHSUSB_BULK, using a virtual machine of linux ubuntu, windows 8.1 sees it as unknow device
LG dead since 3 months ago.................. i wasnt using the phone at all when this happended so........... :crying:
Click to expand...
Click to collapse
I tried using a boot usb drive to see if ubuntu saw the device but it didn't. Maybe there's some things needed that I didn't do. The thing I don't understand the most is why do windows see it as an unknown device only with the battery out while if I connect the G3 with the battery on, it doesn't show anything on device manager..
Nubrig said:
So I bought a used G3 knowing about the issue it had; it didn't boot. I thought I could find a workaround to this but the phone doesn't boot, doesn't enter recovery or download mode. All the info I have is that when I take off the battery the pc sees it as an unknown device, while it's connected I press the power button for several seconds and it disconnects from the pc, reconnects after several more seconds of pressing the power button. Screen remains dead. Seller told me he had a perfectly working phone before he tried to root it and it never turned on again. One more indication is that the LED notification only flashed red a few times when I connected it to the wall charger and that was it. No LED working after that. I'm open to any suggestions though I guess I'm here for someone to tell me there's no hope reviving the device. Thanks in advance!
Click to expand...
Click to collapse
Hi there.
Please check these 2 threads out and see if any of it will help you. The one for the G2 can also be used for G3.
Here are the links:
http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091 With this technique you would have to find the software online somewhere but this method does revive dead G3 with these symptoms.
http://forum.xda-developers.com/showthread.php?t=2475045
If I helped somehow, hit the THANKS button.
Good luck!
The thing is I can only get the device to be recognized as an Unknown Device in Device Manager and only with its battery out. If I keep 'volume up' pressed nothing happens, it's only shown after I simply connect the USB cable and it pops up after 10 seconds or so. It's very consistent in the way it behaves..
A small update, sometimes when I pull and put the battery again, I connect the phone to a pc while holding down vol- and the pc makes the connected usb sound while the phone led is blinking red for a couple of minutes, then it stops. That's about all there is concerning the phone giving signs of life..
So, the other day my phone started acting weird. It randomly restarted, then worked another hour or so, and then started shutting down almost immediately after booting. I was running a Nexus 5X with rooted stock Android 7.0.0 (SuperSU root) and ElementalX kernel. It had been running this for a few months without any issues. I can't think of anything I did to trigger this. I didn't run any updates, I haven't flashed anything since I installed ElementalX couple months ago.
After a lot of troubleshooting (at first I could still get into the bootloader and recovery, but when I did, TWRP didn't recognize any partitions? I was unable to access the file system in TWRP), it finally got so bad that my phone is no longer recognized by my laptop other than "QHSUSB_BULK" device in the Device Manager (Windows 10 x64). Completely black screen, no response, no LED when plugging in adapter. One time I managed to get into the bootloader (randomly, no idea what triggered it) and I managed to put stock 7.1.1 on it, but soon after the installation of that, the exact same thing happened: random reboots, progressively getting worse to in the end: no recovery, no bootloader, only recognized as "QHSUSB_BULK". So I was back to the lowest point.
I read about a "hidden second bootloader" on the 5X, that would be accessable through Power+Both Volume keys, but that doesn't work at all for me (tried it for up to 1 minute of pressing).
After hours of searching (I probably read all the 5X + other phones's topics here that have this issue..), I came here: www.droidsavvy.com/unbrick-qualcomm-mobiles/
I followed those steps precisely, got my laptop to recognize the phone as 'Qualcomm HS-USB QDLoader 9008' by installing the Qualcomm drivers with driver signature verification turned off, but I just couldn't get the QFIL program to flash anything to my phone. It threw a "Download Fail:Sahara FailSahara Fail" saying it couldn't send the Flashing program to my phone. I tried several things here: attempted to power off the phone, then hold Volume up+plug in USB --> flash straight away, different driver/software versions, different laptop, but all to no avail.
I have no real way of telling whether the phone is on or off (it seems impossible to actually turn it off - if I hold power for 30 or so secs I do hear the USB disconnect-connect sound from my laptop, but the device is still shown as "QHSUSB_BULK" so it won't actually turn off properly).
My current hypothesis: it's a hardware fault (eMMC?) and as I'm still within warranty I can send it in for repair/replacement.
Perhaps there is a very slight chance that someone has also encountered this, and it's still a software problem which can be helped by me in some way?
Thanks in advance!
Its probably some part of the motherboard that is faulty. Take it into a repair center. Get it replaced.
I was trying to install Lineage onto it, but it kept erroring. A friend of mine said he could help, and he tried, but bricked it. He said he followed a guide, but left out steps, because he thought they were not important. Now I don't have a bootloader.
When I power on the device, it displays a USB logo with a white line under it for a split second, then powers off. If I connect a USB cable, it stays on for ~2 minutes before powering off again. No Windows or Linux computer detects it. Can I fix this somehow?
I saw unbrick guides for similar problems, but they were only for the 550 and 551 models.
Thanks in advance!
smileyhead said:
I was trying to install Lineage onto it, but it kept erroring. A friend of mine said he could help, and he tried, but bricked it. He said he followed a guide, but left out steps, because he thought they were not important. Now I don't have a bootloader.
When I power on the device, it displays a USB logo with a white line under it for a split second, then powers off. If I connect a USB cable, it stays on for ~2 minutes before powering off again. No Windows or Linux computer detects it. Can I fix this somehow?
I saw unbrick guides for similar problems, but they were only for the 550 and 551 models.
Thanks in advance!
Click to expand...
Click to collapse
i thought search thing works properly.. go to the following link
https://forum.xda-developers.com/zenfone2/help/guide-bring-to-life-zenfone-2-ze500cl-t3503144
So i was using my phone and decided to restart it after updating my adaway files but my phone never turned back on. The two press the power button screens did not show up either. I tried to uses the MSMdownload tool since i thought my phone was somehow bricked but that didnt work either, it just kept restarting the download process after everything was completed. my computer makes a sound when its connected and it connects correctly as a quallcomm 9008 device but even after all this nothing is working. has anyone experienced something like this or does anyone have any advice?
did you try to long press both power button and vol up ...you should feel a vibration...
maybe it's not turned of maybe it's error causing the screen to be off... also is there any heat?
Which method of the unbrick tool did you use? First or second? If the first, then maybe you should give the second also a try.
Sent from my ONEPLUS A3003 using Tapatalk
I've tried everything and I used th me second method yet nothing happened. I can see my phone get recognized by the computer and get listed on the MSN device list yet nothing happens after it finishes the process. After the green line shows up telling me that it's completed everything the process restarts writhing a few minutes unless I unplug it. No vibration no nothing the phone just died on me after I restarted it .
Try doing MSM on a different PC with all drivers installed , hope it helps
Try to repeat flashing again, there is no other way. Use method 2only. Extract tool again and try flash.
When I was used Xperia Z1, I bricked my phone with a soft brick. So I installed driver in my PC and flash Kernel though FASTBOOT(ADB) either it's not show Device in my PC (I show just "Unknown Device").
After that my phone can connect to my PC again (Now It shown C9303 or something that meant it know it's a phone).
So I can flash by Flashtools again. Soft brick is not scary as Hard brick, you'll find some way to bring it back easily.
Hope this help!
PS. Bricked Phone is WEAK in Battery, always connect it with charger.
Hi, I was wondering if anyone has encountered this problem? The phone has been updated to the latest firmware as of the 8th of October 2017. I was using the facebook app and it was crashing repeatedly; after a few times of attempting to restart the app and crashing, the phone froze (black screen) and I tried to do a soft reset (30 secs on power button) but to no avail. I noticed that when the phone is put on the charger, the white LED flash for the front facing camera started blinking. I tried plugging it into the laptop and noticed that "Qualcomm HS-USB QDLoader 9008" driver is installed. Of course white LED flash was blinking too. A bit of digging seems to suggest that the bootloader has been corrupted. How is this possible and how can it be fixed (stopping short of contacting motorola)? Thank you for any advice in advance.
Flash stock firmware !?
Unfortunately I can't even get into the recovery mode (aka down + power button as per instructions here - https://motorola-global-en-aus.cust...ail/a_id/113698/p/30,6720,9837/kw/clear cache). Any other ideas?
Try this: https://forum.xda-developers.com/showpost.php?p=72813119&postcount=6
Oh no, black screen hard brick (to my face)
MP1_ said:
Try this: https://forum.xda-developers.com/showpost.php?p=72813119&postcount=6
Click to expand...
Click to collapse
I have the same issue. Z2 NASH is booting and showing the qualcomm usb qloader in windows however I have no response from the gui or screen whatsoever. This happened immediately after a factory reset so, not only can I not boot to TWRP, but I also cannot communicate thru ADB. Please help if you can. I am currently following your guide here for flashing from windows and installing / flashing stock firmwares. I will post back my results. Thanks for any help you can offer...
I have the same issue, have there been any fixes? My Moto z2 play randomly bricked one night, same "Qualcomm HS-USB QDLoader 9008" in my "other devices" tab, and i have no clue what to do. My phone wont do a single thing, it was flashing the led on the right side when it was charging, now it does nothing at all. Any help is appreciated