[GUIDE] [UNBRICK] Unbrick Oneplus One

The following thread helped you unbrick your bacon:

  • Yes, worked like a charm!

    Votes: 207 65.5%
  • Kinda, they got me on the right track

    Votes: 47 14.9%
  • No, I wasn't able to understand these directions

    Votes: 8 2.5%
  • No, these directions didn't work

    Votes: 54 17.1%

  • Total voters
    316
Search This thread

netbuzz

Senior Member
May 16, 2012
565
594
*** This guide has also been ported to SteemIt. Please visit and upvote it at https://steemit.com/oneplus/@delusionalgenius/how-to-unbrick-oneplus-one-bacon ***

*** I've been receiving many requests and PMs from members asking to help them unbrick their device. Please note that I no longer own this device (and even if I did I would not purposely brick it just to reproduce your problem), therefore I am unable to help out beyond this tutorial. ***


Hello,

First some background and credits:

There are a few ways to brick a phone. Sometimes it's lack of experience, sometimes it's an accidental thing, sometimes there just isn't an explanation for what went wrong... (share your experience here, if you wish). For me, I owned my OPO for about 4 hours before things went wrong. First thing I did was I rooted it and installed TWRP. After creating a nandroid backup of the stock image I installed my favorite custom ROM and restored all my apps with TiBu. Everything was great and configured just the way I wanted it. I then wiped my old phone (Nexus 4), installed a new ROM and got it all ready for my wife. She was so excited to get rid of her GNex and move up to the N4. But then, for whatever reason, I opened an app on my OPO that I used to manage, download, and install kernels with. It came up with "there is a new kernel update!" and I instinctively clicked on "Install". 10 seconds later my phone was bricked. Nothing came on the screen, no fastboot, no recovery, nothing to boot to, no way to send data to and from it. The second the screen went black and the phone became lifeless I got that wretched feeling in my gut as I realized I just flashed a N4 kernel on my new OPO. Restoring the kernel management app with TiBu made it act like it's still running on my old phone, and in my excitement I didn't take a second to think things through...
I received a bit of consolation when a quick XDA search revealed that I am not the only dumbass to brick his phone this very way. I joined forces with some pretty smart and desperate people and tried different things, all described in the following thread: http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696. Unfortunately it took us what seemed like many long weeks to figure it all out. Well, in the end a solution was found and I documented it in the the following post: http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136.

This was a few months ago, but I recently noticed many people continue to search for these directions and have problems finding them hidden among many pages and other threads, so I've decided to put this stand alone thread with these, now updated, directions.

Let me get one more thing straight, for the record. I did not find the way to unbrick the OPO. In fact I wasn't even the very first one to do it. It was a collective effort of few people who tried many different approaches and ideas, and I eventually documented these steps for others to follow. Being said, the following people deserve credit as well: @os_man, @rezor92, @Mnt-XDA. If I am forgetting other significant names and efforts, I apologize.


***CAUTION***
The following instructions are for hardware bricked devices ONLY and will not work on soft bricked devices. To determine whether your device is soft or hard bricked, click the button below:

Hardware brick
A hardware bricked OPO has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPO should be detected as QHSUSB_BULK USB. You might have a bricked OPO as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition.

Software brick
Please do not attempt to use these directions if your phone is soft bricked. A software bricked OPO is one that might be stuck in a bootloop, but has a working bootloader, recovery partition, fastboot, or adb. If you press the power button and images appear on the screen and you are able to enter fastboot mode (Power + VolUP) or recovery (Power + VolDOWN) then your device is soft bricked. This thread does not encompass soft brick recovery, the instructions below do not apply and will not work on these phones. Consult other threads for help on soft bricked devices.


If based on the above explanation of differences between soft and hard bricks you determined your device is hard bricked, here's what you will need to do...


1:
Download Color.zip from https://goo.gl/iDby26
After downloading, unzip the archive on your computer.

2:
Next, you need proper Windows drivers. There are architectural differences between Windows XP and Windows 7/8, so follow the directions below that pertain to you. One quick note about the drivers: the installation and process is very simple and straightforward on Windows XP (I also tested successfully on Windows 2003), but proves to be quite a challenge when running on Windows 7 or 8. Over and over people report issues when attempting the unbrick procedure on Windows 7/8, some have more luck than others. Being said, if you have access to a Windows XP computer, I highly recommend that you use that. If you have no choice but to use a Windows 7 or 8 computer and have problems, please share them here and read others' experiences.

So first, by now you probably tried a few different things to fix your phone and you've already installed some drivers, including Qualcomm USB drivers for 9006 and 9008. My best advice is to uninstall the drivers you tried so far and use the ones listed below. 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. Then:

2a:
Windows XP users:
You are in luck, driver installation is straightforward. Go to the extracted Color.zip folder and find Driver.iso. Extract Driver.iso. Inside the extracted folder find Setup.exe. Run Setup.exe to install the drivers. The installer is Chinese, but all you need to do is click through the prompts.


2b:
Windows 7 and Windows 8:
These operating systems block unsigned driver installations by default. Follow these steps (thanks @nag4pl for testing these):
Download and extract these Qualcomm 2012 drivers: https://goo.gl/cIKnFZ. Connect your bricked phone and let Windows do its thing.
Now something very essential you need to do here is to execute two commands to allow you to install unsigned drivers for QHUSB_BULK. Click on Start Menu > Type cmd.exe > Right Click and Run as Administrator.
In the CMD window type in the following commands (hit enter after each):
Code:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
Code:
bcdedit.exe -set TESTSIGNING ON
After both the commands should run successfully, restart your computer.
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software. For driver software location provide the path where you have extracted Qualcomm 2012 drivers you downloaded and make sure 'Include Subfolders' is checked. Proceed through all the installation prompts ignoring any warnings.


3:
Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe as Administrator (right click on Msm8974DownloadTool.exe and select "Run as administrator") from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.

Clicking on "Enum" just rescans the busses. Clicking the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.

If you don't see your phone in the list of com devices, try unplugging/plugging in your phone a couple times, and rebooting it with VolUP + Power (hold 10 seconds). You will see it in Device Manager as well.

Once you see the phone in the list, click Start. You should see the programs start writing different files to the phone. Each time it writes a file you'll see a progress bar. Once you see this process happening, smile, you know you will be good to go... After all files are written, the com line with your device will turn green. You're good, unplug and reboot your phone. It will boot to ColorOS, the Chinese OS that comes on OPO.



4:
Optional Steps:
Your phone is no longer bricked. You now have a few options to get back to stock. The easiest way is to use a toolkit from http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418, or you can flash an image manually by following directions from: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541. Download the proper image zip and after extracting it, run the following commands in fastboot mode:

Code:
fastboot flash boot boot.img 
fastboot flash userdata userdata.img 
fastboot flash system system.img 
fastboot flash recovery recovery.img 
fastboot flash cache cache.img 
fastboot flash modem NON-HLOS.bin 
fastboot flash sbl1 sbl1.mbn 
fastboot flash dbi sdi.mbn 
fastboot flash aboot emmc_appsboot.mbn 
fastboot flash rpm rpm.mbn 
fastboot flash tz tz.mbn 
fastboot flash LOGO logo.bin

Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.


That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue.


Good luck! Share your experience here and let me know if I can improve this thread.
Please click the Thanks button if you found the above guide useful.
 
Last edited:

mysterio619

Senior Member
Aug 27, 2011
855
214
30
Bangalore
did this and it finally worked but still i have unknown baseband and no imei.........flashed coloros using the msm tool and rom goes into a bootloop......tried all the ways with no luck....even flashed the persist.img......still no luck.......my last hope is claiming warranty and act like a noob in service center.......will they get to know taht i unlocked the bootloader?
 
  • Like
Reactions: ttangar

netbuzz

Senior Member
May 16, 2012
565
594
did this and it finally worked but still i have unknown baseband and no imei.........flashed coloros using the msm tool and rom goes into a bootloop......tried all the ways with no luck....even flashed the persist.img......still no luck.......my last hope is claiming warranty and act like a noob in service center.......will they get to know taht i unlocked the bootloader?

You should be able to boot to fastboot now. From there flash the cm11s image. I believe that "fastboot flash sbl1 sbl1.mbn" will fix the imei issue.

Also, unlocking bootloader does not void your warranty. Not with OPO.
 

os_man

Senior Member
Sep 30, 2005
241
78
50
istanbul
www.androidbrick.com
unbrick oneplus one, oppo 7

Hi there my friend, i had many works about unbricking solutions, a few of you know that, i have much easier and faster ways now, tested many times before i decided to share with you, it will be a long topic ( and my brain is messed up to sum them up clearly), as soon i can think clearly again, i start to write them, till then,
greetings from Istanbul to all geeks around thw world.

Ps: including restoring imei's if they got lost during this process.
Ps2: just a quick info abou imei, if your imei is "invalid" , this means your modem.bin (NON-HLOS.bin, baseband) is not inadaptable with your rom, just try flashing the right modem ( from fastboot), your imei will be back.

Ps3 : This will lead us to unbrick many Snapdragon's out there , not only oneplus one's or oppo's.
 
Last edited:

michaeldepotter

Senior Member
Aug 20, 2011
118
16
I had to use this tutorial some days ago.
There is also a modified .zip where the tool from OPO flashed CM11s instead of ColorOS.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851

I had many driver problems and i had to use this driver from qualcomm so my win7 could recognize the phone.


Tutorial to install the driver:
1. Open your device manager (Start - right click on computer - properties - devices manager)
2. Press on power + vol up for like 10 sec until you see a device showing up (called QHSUSB_BULK)
3. Right click on this devices and click on "Update Driver Software" -> "Browse my computer for driver software" -> locate the Qualcomm 2012\fre\Windows7 8 or vista folder depending on your setup. Update the driver.
 

nag4pl

Senior Member
Dec 6, 2013
76
50
Bangalore
I had to use this tutorial some days ago.
There is also a modified .zip where the tool from OPO flashed CM11s instead of ColorOS.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851

I had many driver problems and i had to use this driver from qualcomm so my win7 could recognize the phone.


Tutorial to install the driver:
1. Open your device manager (Start - right click on computer - properties - devices manager)
2. Press on power + vol up for like 10 sec until you see a device showing up (called QHSUSB_BULK)
3. Right click on this devices and click on "Update Driver Software" -> "Browse my computer for driver software" -> locate the Qualcomm 2012\fre\Windows7 8 or vista folder depending on your setup. Update the driver.



Hi, Dropbox link for drivers seems to be wrong.. could you please update correct one.. I am in very much need of it! pls!!
 

nag4pl

Senior Member
Dec 6, 2013
76
50
Bangalore
Back from Brick!!

First of all Thanks a lot to @netbuzz(for such a life saver guide on unbricking 1+1) and @michaeldepotter for providing link to download appropriate drivers.

Here is some good news by my findings and can be a quick help for those who do not have or can't get XP. You can use Windows 7 itself for the process mentioned by @netbuzz

All you need to do is:
1. Download drivers from link provided by @michaeldepotter : https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
2. Extract to some folder under C: or whichever drive you prefer.
3. Connect your bricked phone after pressing Volume Up and Power key (make sure phone vibrates once)
4. Now that QHUSB_BULK should be detected and Windows will eventually try to download drivers from update, which you can skip and close the window.

Now something very essential you need to do here is to execute some commands so that you will be able to install unsigned drivers for QHUSB_BULK.
4a. Click On Start Menu > Type cmd.exe > Right Click and Run as Administrator (make sure you are running cmd as admin)
4b. Now type below command
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
>hit Enter
bcdedit.exe -set TESTSIGNING ON
> hit Enter again
4c. Both the commands should run successfully, then restart your computer.
These steps are to disable driver sign verification. You must proceed to next steps only after above steps executed successfully.

After machine booted back to desktop

5. Now Open Device Manager by Start > Run > type "devmgmt.msc" and hit enter
6. You should be seeing ugly yellow warning under other devices for QHUSB_BULK.
7. Right click on the same > Update Driver Software > Browse my Computer for driver software
8. Now under driver software location, provide the path where you have extracted drivers which you downloaded from step 1. For me it was:
"C:\Users\Arjun\Downloads\Qualcomm 2012\fre\Windows7" - Remember to provide path only till windows 7 and make sure 'Include Subfolders' is checked.
9. Click next, and it should install driver for QHUSB_BULK. Click on Install Driver if you get any warnings.

Now your driver set-up for QHUSB_BULK in Windows 7 is complete and now you may proceed with the steps to run Msm8974DownloadTool as provided by netbuzz.

I have attached the screenshots for the same just for confirmation.

SuccessfullDriver - showing successful installation of driver
FlashInProgress - showing tool flashing the system image
FlashSuccess - showing green row indicating successful flash.


Once again, thanks a lot for all the guide and help. Hope this quick guide helps some one in need!!
 

Attachments

  • SuccessfullDriver.png
    SuccessfullDriver.png
    56.6 KB · Views: 2,432
  • FlashInProgress.png
    FlashInProgress.png
    50.7 KB · Views: 2,426
  • FlashSuccess.png
    FlashSuccess.png
    49 KB · Views: 2,395

netbuzz

Senior Member
May 16, 2012
565
594
First of all Thanks a lot to @netbuzz(for such a life saver guide on unbricking 1+1) and @michaeldepotter for providing link to download appropriate drivers.

Here is some good news by my findings and can be a quick help for those who do not have or can't get XP. You can use Windows 7 itself for the process mentioned by @netbuzz

All you need to do is:
1. Download drivers from link provided by @michaeldepotter : https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
2. Extract to some folder under C: or whichever drive you prefer.
3. Connect your bricked phone after pressing Volume Up and Power key (make sure phone vibrates once)
4. Now that QHUSB_BULK should be detected and Windows will eventually try to download drivers from update, which you can skip and close the window.

Now something very essential you need to do here is to execute some commands so that you will be able to install unsigned drivers for QHUSB_BULK.
4a. Click On Start Menu > Type cmd.exe > Right Click and Run as Administrator (make sure you are running cmd as admin)
4b. Now type below command
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
>hit Enter
bcdedit.exe -set TESTSIGNING ON
> hit Enter again
4c. Both the commands should run successfully, then restart your computer.
These steps are to disable driver sign verification. You must proceed to next steps only after above steps executed successfully.

After machine booted back to desktop

5. Now Open Device Manager by Start > Run > type "devmgmt.msc" and hit enter
6. You should be seeing ugly yellow warning under other devices for QHUSB_BULK.
7. Right click on the same > Update Driver Software > Browse my Computer for driver software
8. Now under driver software location, provide the path where you have extracted drivers which you downloaded from step 1. For me it was:
"C:\Users\Arjun\Downloads\Qualcomm 2012\fre\Windows7" - Remember to provide path only till windows 7 and make sure 'Include Subfolders' is checked.
9. Click next, and it should install driver for QHUSB_BULK. Click on Install Driver if you get any warnings.

Now your driver set-up for QHUSB_BULK in Windows 7 is complete and now you may proceed with the steps to run Msm8974DownloadTool as provided by netbuzz.

I have attached the screenshots for the same just for confirmation.

SuccessfullDriver - showing successful installation of driver
FlashInProgress - showing tool flashing the system image
FlashSuccess - showing green row indicating successful flash.


Once again, thanks a lot for all the guide and help. Hope this quick guide helps some one in need!!

Thanks for this Win7/8 workaround. I'll be adding your info to the OP.
 
  • Like
Reactions: michaeldepotter

ttangar

Member
Feb 12, 2013
6
3
Finally Unbricked mine...Drivers resolved on Win 7

Second note about drivers is that I had the worst time trying to get things to work on my Windows 7 computers. Both Windows 7 and 8 block unsigned driver installations by default. I've tried overwriting these settings in Windows and spent half a day messing with it, and I never got things to work properly. At first all looked good to go, but then latter steps were failing. You might have a better luck getting drivers to work on Windows 7 or 8 (I've heard some people did it), but if you have access to a Windows XP or 2003 machine, try it first, it should save you some major headache.

Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.

I have used the override tool for certificates: DSEO - Driver signature enforcement overrider
to allow the unsigned drivers to be used and it worked like charm on windows 7 64 bit.
Also, I used the additional Qualcomm 2012 drivers and not sure which one might got picked in that mess :cyclops::cyclops:
Thanks!!
:good::good::angel::angel:
 

bhaismachine

Senior Member
Feb 14, 2011
294
133
Dallas
Well I managed to hardbrick my phone. I am download the ColorOS file from Mega at the moment. It's downloading at 30KB/s and will take around 6.5 hours. Is there any other source to download it from ? Thanks !

Also, about the driver ...

While I wait on the colorOS to download I want to clarify one more thing about the driver.

According to the screenshot of @nag4pl the driver should show as Qualcomm USB diagnostic 9006, while for me it shows as Qualcomm HS-USB QDloader 9008. Is this going to be an issue ?

This is what I did. I uninstalled the default driver that came with windows 7. After that it failed to install the driver provided in this forum because it kept saying that device descriptor failed. I rebooted the phone several times and changed the USB ports and eventually windows detected it but AGAIN with the windows driver even though I had checked the option to delete the original driver while uninstalling it. Through the update driver option I managed to force it to install the unsigned driver.

Now I can see both the drivers under the update drivers option. Interestingly the default driver is a version ahead of the unsigned driver provided in this forum.
My only concern is that I see a different driver name compared to the one posted by @nag4pl
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 171
    *** This guide has also been ported to SteemIt. Please visit and upvote it at https://steemit.com/oneplus/@delusionalgenius/how-to-unbrick-oneplus-one-bacon ***

    *** I've been receiving many requests and PMs from members asking to help them unbrick their device. Please note that I no longer own this device (and even if I did I would not purposely brick it just to reproduce your problem), therefore I am unable to help out beyond this tutorial. ***


    Hello,

    First some background and credits:

    There are a few ways to brick a phone. Sometimes it's lack of experience, sometimes it's an accidental thing, sometimes there just isn't an explanation for what went wrong... (share your experience here, if you wish). For me, I owned my OPO for about 4 hours before things went wrong. First thing I did was I rooted it and installed TWRP. After creating a nandroid backup of the stock image I installed my favorite custom ROM and restored all my apps with TiBu. Everything was great and configured just the way I wanted it. I then wiped my old phone (Nexus 4), installed a new ROM and got it all ready for my wife. She was so excited to get rid of her GNex and move up to the N4. But then, for whatever reason, I opened an app on my OPO that I used to manage, download, and install kernels with. It came up with "there is a new kernel update!" and I instinctively clicked on "Install". 10 seconds later my phone was bricked. Nothing came on the screen, no fastboot, no recovery, nothing to boot to, no way to send data to and from it. The second the screen went black and the phone became lifeless I got that wretched feeling in my gut as I realized I just flashed a N4 kernel on my new OPO. Restoring the kernel management app with TiBu made it act like it's still running on my old phone, and in my excitement I didn't take a second to think things through...
    I received a bit of consolation when a quick XDA search revealed that I am not the only dumbass to brick his phone this very way. I joined forces with some pretty smart and desperate people and tried different things, all described in the following thread: http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696. Unfortunately it took us what seemed like many long weeks to figure it all out. Well, in the end a solution was found and I documented it in the the following post: http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136.

    This was a few months ago, but I recently noticed many people continue to search for these directions and have problems finding them hidden among many pages and other threads, so I've decided to put this stand alone thread with these, now updated, directions.

    Let me get one more thing straight, for the record. I did not find the way to unbrick the OPO. In fact I wasn't even the very first one to do it. It was a collective effort of few people who tried many different approaches and ideas, and I eventually documented these steps for others to follow. Being said, the following people deserve credit as well: @os_man, @rezor92, @Mnt-XDA. If I am forgetting other significant names and efforts, I apologize.


    ***CAUTION***
    The following instructions are for hardware bricked devices ONLY and will not work on soft bricked devices. To determine whether your device is soft or hard bricked, click the button below:

    Hardware brick
    A hardware bricked OPO has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPO should be detected as QHSUSB_BULK USB. You might have a bricked OPO as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition.

    Software brick
    Please do not attempt to use these directions if your phone is soft bricked. A software bricked OPO is one that might be stuck in a bootloop, but has a working bootloader, recovery partition, fastboot, or adb. If you press the power button and images appear on the screen and you are able to enter fastboot mode (Power + VolUP) or recovery (Power + VolDOWN) then your device is soft bricked. This thread does not encompass soft brick recovery, the instructions below do not apply and will not work on these phones. Consult other threads for help on soft bricked devices.


    If based on the above explanation of differences between soft and hard bricks you determined your device is hard bricked, here's what you will need to do...


    1:
    Download Color.zip from https://goo.gl/iDby26
    After downloading, unzip the archive on your computer.

    2:
    Next, you need proper Windows drivers. There are architectural differences between Windows XP and Windows 7/8, so follow the directions below that pertain to you. One quick note about the drivers: the installation and process is very simple and straightforward on Windows XP (I also tested successfully on Windows 2003), but proves to be quite a challenge when running on Windows 7 or 8. Over and over people report issues when attempting the unbrick procedure on Windows 7/8, some have more luck than others. Being said, if you have access to a Windows XP computer, I highly recommend that you use that. If you have no choice but to use a Windows 7 or 8 computer and have problems, please share them here and read others' experiences.

    So first, by now you probably tried a few different things to fix your phone and you've already installed some drivers, including Qualcomm USB drivers for 9006 and 9008. My best advice is to uninstall the drivers you tried so far and use the ones listed below. 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. Then:

    2a:
    Windows XP users:
    You are in luck, driver installation is straightforward. Go to the extracted Color.zip folder and find Driver.iso. Extract Driver.iso. Inside the extracted folder find Setup.exe. Run Setup.exe to install the drivers. The installer is Chinese, but all you need to do is click through the prompts.


    2b:
    Windows 7 and Windows 8:
    These operating systems block unsigned driver installations by default. Follow these steps (thanks @nag4pl for testing these):
    Download and extract these Qualcomm 2012 drivers: https://goo.gl/cIKnFZ. Connect your bricked phone and let Windows do its thing.
    Now something very essential you need to do here is to execute two commands to allow you to install unsigned drivers for QHUSB_BULK. Click on Start Menu > Type cmd.exe > Right Click and Run as Administrator.
    In the CMD window type in the following commands (hit enter after each):
    Code:
    bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
    Code:
    bcdedit.exe -set TESTSIGNING ON
    After both the commands should run successfully, restart your computer.
    You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software. For driver software location provide the path where you have extracted Qualcomm 2012 drivers you downloaded and make sure 'Include Subfolders' is checked. Proceed through all the installation prompts ignoring any warnings.


    3:
    Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe as Administrator (right click on Msm8974DownloadTool.exe and select "Run as administrator") from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.

    Clicking on "Enum" just rescans the busses. Clicking the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.

    If you don't see your phone in the list of com devices, try unplugging/plugging in your phone a couple times, and rebooting it with VolUP + Power (hold 10 seconds). You will see it in Device Manager as well.

    Once you see the phone in the list, click Start. You should see the programs start writing different files to the phone. Each time it writes a file you'll see a progress bar. Once you see this process happening, smile, you know you will be good to go... After all files are written, the com line with your device will turn green. You're good, unplug and reboot your phone. It will boot to ColorOS, the Chinese OS that comes on OPO.



    4:
    Optional Steps:
    Your phone is no longer bricked. You now have a few options to get back to stock. The easiest way is to use a toolkit from http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418, or you can flash an image manually by following directions from: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541. Download the proper image zip and after extracting it, run the following commands in fastboot mode:

    Code:
    fastboot flash boot boot.img 
    fastboot flash userdata userdata.img 
    fastboot flash system system.img 
    fastboot flash recovery recovery.img 
    fastboot flash cache cache.img 
    fastboot flash modem NON-HLOS.bin 
    fastboot flash sbl1 sbl1.mbn 
    fastboot flash dbi sdi.mbn 
    fastboot flash aboot emmc_appsboot.mbn 
    fastboot flash rpm rpm.mbn 
    fastboot flash tz tz.mbn 
    fastboot flash LOGO logo.bin

    Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.


    That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue.


    Good luck! Share your experience here and let me know if I can improve this thread.
    Please click the Thanks button if you found the above guide useful.
    4
    Added to OnePlus One index thread:

    [INDEX] OnePlus One Resources Compilation Roll-Up

    Transmitted via Bacon
    4
    I had to use this tutorial some days ago.
    There is also a modified .zip where the tool from OPO flashed CM11s instead of ColorOS.
    http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851

    I had many driver problems and i had to use this driver from qualcomm so my win7 could recognize the phone.


    Tutorial to install the driver:
    1. Open your device manager (Start - right click on computer - properties - devices manager)
    2. Press on power + vol up for like 10 sec until you see a device showing up (called QHSUSB_BULK)
    3. Right click on this devices and click on "Update Driver Software" -> "Browse my computer for driver software" -> locate the Qualcomm 2012\fre\Windows7 8 or vista folder depending on your setup. Update the driver.
    4
    Back from Brick!!

    First of all Thanks a lot to @netbuzz(for such a life saver guide on unbricking 1+1) and @michaeldepotter for providing link to download appropriate drivers.

    Here is some good news by my findings and can be a quick help for those who do not have or can't get XP. You can use Windows 7 itself for the process mentioned by @netbuzz

    All you need to do is:
    1. Download drivers from link provided by @michaeldepotter : https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
    2. Extract to some folder under C: or whichever drive you prefer.
    3. Connect your bricked phone after pressing Volume Up and Power key (make sure phone vibrates once)
    4. Now that QHUSB_BULK should be detected and Windows will eventually try to download drivers from update, which you can skip and close the window.

    Now something very essential you need to do here is to execute some commands so that you will be able to install unsigned drivers for QHUSB_BULK.
    4a. Click On Start Menu > Type cmd.exe > Right Click and Run as Administrator (make sure you are running cmd as admin)
    4b. Now type below command
    bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
    >hit Enter
    bcdedit.exe -set TESTSIGNING ON
    > hit Enter again
    4c. Both the commands should run successfully, then restart your computer.
    These steps are to disable driver sign verification. You must proceed to next steps only after above steps executed successfully.

    After machine booted back to desktop

    5. Now Open Device Manager by Start > Run > type "devmgmt.msc" and hit enter
    6. You should be seeing ugly yellow warning under other devices for QHUSB_BULK.
    7. Right click on the same > Update Driver Software > Browse my Computer for driver software
    8. Now under driver software location, provide the path where you have extracted drivers which you downloaded from step 1. For me it was:
    "C:\Users\Arjun\Downloads\Qualcomm 2012\fre\Windows7" - Remember to provide path only till windows 7 and make sure 'Include Subfolders' is checked.
    9. Click next, and it should install driver for QHUSB_BULK. Click on Install Driver if you get any warnings.

    Now your driver set-up for QHUSB_BULK in Windows 7 is complete and now you may proceed with the steps to run Msm8974DownloadTool as provided by netbuzz.

    I have attached the screenshots for the same just for confirmation.

    SuccessfullDriver - showing successful installation of driver
    FlashInProgress - showing tool flashing the system image
    FlashSuccess - showing green row indicating successful flash.


    Once again, thanks a lot for all the guide and help. Hope this quick guide helps some one in need!!
    3
    unbrick oneplus one, oppo 7

    Hi there my friend, i had many works about unbricking solutions, a few of you know that, i have much easier and faster ways now, tested many times before i decided to share with you, it will be a long topic ( and my brain is messed up to sum them up clearly), as soon i can think clearly again, i start to write them, till then,
    greetings from Istanbul to all geeks around thw world.

    Ps: including restoring imei's if they got lost during this process.
    Ps2: just a quick info abou imei, if your imei is "invalid" , this means your modem.bin (NON-HLOS.bin, baseband) is not inadaptable with your rom, just try flashing the right modem ( from fastboot), your imei will be back.

    Ps3 : This will lead us to unbrick many Snapdragon's out there , not only oneplus one's or oppo's.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone