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.
Related
Hello! Im new here
The thing is that I bought a bricked OPO today hoping that I could fix it. I've been like 4-5hrs straight trying and nothing!
The real problem is that my OPO is not being recognized by my computer. (Im running Windows 8.1)
When I connect it to the PC the device vibrates but no sound, I go to device manager and it's not there (not as QHSUSB_BULK, not as UNKNOWN DEVICE, not as nothing, it just dont exist)
I installed the Samsung drivers, OnePlusRestoreTool, Bacon Root ToolKit, OnePlus One Toolkit and nothing seem to work...
I tried to get it into FastBoot mode but it ony vibrates every 10 consecutive seconds I hold the vol up + pwr button and NOTHING happen, screen remain black and no sound by my PC recognizing the device...
I tried alternate USB, alternate cable and nothing...
If you guys can help me that would be awesome!
Thanks, and sorry for my bad english.
Maximuseml said:
Hello! Im new here
The thing is that I bought a bricked OPO today hoping that I could fix it. I've been like 4-5hrs straight trying and nothing!
The real problem is that my OPO is not being recognized by my computer. (Im running Windows 8.1)
When I connect it to the PC the device vibrates but no sound, I go to device manager and it's not there (not as QHSUSB_BULK, not as UNKNOWN DEVICE, not as nothing, it just dont exist)
I installed the Samsung drivers, OnePlusRestoreTool, Bacon Root ToolKit, OnePlus One Toolkit and nothing seem to work...
I tried to get it into FastBoot mode but it ony vibrates every 10 consecutive seconds I hold the vol up + pwr button and NOTHING happen, screen remain black and no sound by my PC recognizing the device...
I tried alternate USB, alternate cable and nothing...
If you guys can help me that would be awesome!
Thanks, and sorry for my bad english.
Click to expand...
Click to collapse
Hi mate, am in exact same situation as yours.
Did you have any luck fixing it?
Maximuseml said:
Hello! Im new here
The thing is that I bought a bricked OPO today hoping that I could fix it. I've been like 4-5hrs straight trying and nothing!
The real problem is that my OPO is not being recognized by my computer. (Im running Windows 8.1)
When I connect it to the PC the device vibrates but no sound, I go to device manager and it's not there (not as QHSUSB_BULK, not as UNKNOWN DEVICE, not as nothing, it just dont exist)
I installed the Samsung drivers, OnePlusRestoreTool, Bacon Root ToolKit, OnePlus One Toolkit and nothing seem to work...
I tried to get it into FastBoot mode but it ony vibrates every 10 consecutive seconds I hold the vol up + pwr button and NOTHING happen, screen remain black and no sound by my PC recognizing the device...
I tried alternate USB, alternate cable and nothing...
If you guys can help me that would be awesome!
Thanks, and sorry for my bad english.
Click to expand...
Click to collapse
1st of all uninstall QHSUSB_BULK this driver,after this download qualcomm 9008 driver google it and install this driver then you can connect your #bacon it going to detected and dont forgot this process has to be done test mode and refer thia thread also http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
sid_844 said:
1st of all uninstall QHSUSB_BULK this driver,after this download qualcomm 9008 driver google it and install this driver then you can connect your #bacon it going to detected and dont forgot this process has to be done test mode and refer thia thread also http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
First of all thanks for your reply.
I have seen this thread but as you can see to uninstall the old driver I need to:
' Go to Device Manager, right click on the bricked USB device (QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008) and go to Properties, click on Driver, then select Uninstall. Check the box to remove driver files, if prompted...'
But the device is not seen by the device manager.
Someone suggested in an other thread that I need just to press (not hold) power + volume button.
I will try that and let you know.
By the way what is 'test mode'?
Hello OPO owners.
I need some help in unbricking my device. I followed the tutorial with color.zip. Driver installation went without problem device manager showed as QDloader 9008 and msm8974downloadtool recognized the device and started flashing. so far no problem.
Problems start after device change to Qualcomm HS-USB Diagnostics 9006 (as it should be). in this state my OPO seems to "disconnect" every 8-10 seconds. in msm8974downloadtool and device manager it disappears for about half a second and the reappears for another 8 seconds. So the tool starts flashing and by the time it reaches system.img disconnect and the flashing starts again. kind of a bootloop
already tried different cables, usb-ports, computers (win 7 and win xp) without success. the disconnecting only appears in 9006 state, in 9008 state all is good.
any idea is welcome
Try this thread:
http://forum.xda-developers.com/one...overy-tool-v1-0-restore-t2991851/post57934891
tropenfrucht said:
Hello OPO owners.
I need some help in unbricking my device. I followed the tutorial with color.zip. Driver installation went without problem device manager showed as QDloader 9008 and msm8974downloadtool recognized the device and started flashing. so far no problem.
Problems start after device change to Qualcomm HS-USB Diagnostics 9006 (as it should be). in this state my OPO seems to "disconnect" every 8-10 seconds. in msm8974downloadtool and device manager it disappears for about half a second and the reappears for another 8 seconds. So the tool starts flashing and by the time it reaches system.img disconnect and the flashing starts again. kind of a bootloop
already tried different cables, usb-ports, computers (win 7 and win xp) without success. the disconnecting only appears in 9006 state, in 9008 state all is good.
any idea is welcome
Click to expand...
Click to collapse
[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
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.
please read title and help
restore it with msm tool
how to connect the phone screen is black
If the screen is black it may already be in EDL mode. Plug it into a computer and check device manager for something like "Qualcomm HS-USB QDLoader." If that's there, you just need to get the MSM Tool for your model and make sure you have the right drivers.
If you can't get it into EDL mode, you will have to file a warranty claim with OnePlus, no other choice. Mess around with the buttons and see if you can get it to reboot or try the EDL key combo (hold volume up and down and while holding plug in the USB cable that's plugged into the computer). You don't have a chance of repairing it yourself if you can't get into EDL, end of story.
pc recognizing this Qualcomm HS-USB QDLoader in device manager but in msm tool it is showing n/a.and also in device manager it is showing triangle error on device.i am using official driver provided by msm tool poster.
Need some help unbricking (solved)
I bricked my OP9 doing some stuff today. It will not turn on, access bootloader, or anything. When I plug it into my computer, it makes a connecting sound, waits 10 seconds, then disconnect sound, then repeats the process. I tried using MSM...
forum.xda-developers.com
It's can help you
Well you're not the only one I guess. That happened to me as well. So perhaps, Alhamdulillah I can help you out
The screen still remains black that means your phone is in the EDL and you'll need to get it out of it and then get back to EDL again to use msm.
Anyway, hold the power + volume up + down all simultaneously for a while. It'll take you to the Fastboot mode. Don't worry, it definitely will take you to the Fastboot mode.
Then you can do the rest of the flashing as you wish