[GUIDE] [UNBRICK] Unbrick Oneplus One

The following thread helped you unbrick your bacon:

  • Yes, worked like a charm!

    Votes: 209 65.7%

  • Kinda, they got me on the right track

    Votes: 47 14.8%

  • No, I wasn't able to understand these directions

    Votes: 8 2.5%

  • No, these directions didn't work

    Votes: 54 17.0%
  • Total voters
    318
Search This thread
By:
Advanced…
V

vasubawa

Member
Apr 15, 2015
5
0
Can't See QHUSB_BULK

Hello, I tried your tutorial and I got stuck on the part where you have to go into the device manager and update drivers on QHUSB_BULK but I am unable to detect anything related to that on device manager, I am running windows 10 and I had a XP which isn't loading so can't use that, also does a virtual box work if i use windows XP on there?

I also get this when i tried running the Msm download tool:
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_backup0_64G.bin: OK
gpt_main0.bin: OK
gpt_main0_64G.bin: OK
userdata.img: FAILED
userdata_64G.img: FAILED
rawprogram0.xml: OK
rawprogram0_64G.xml: OK
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED

definitely looks like this phone is goofed big time so is there any way on fixing it?
 
Mr.Ak

Mr.Ak

Senior Member
Jan 14, 2015
4,410
1,970
23
*RESTRICTED AREA*
vasubawa said:
Hello, I tried your tutorial and I got stuck on the part where you have to go into the device manager and update drivers on QHUSB_BULK but I am unable to detect anything related to that on device manager, I am running windows 10 and I had a XP which isn't loading so can't use that, also does a virtual box work if i use windows XP on there?

I also get this when i tried running the Msm download tool:
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_backup0_64G.bin: OK
gpt_main0.bin: OK
gpt_main0_64G.bin: OK
userdata.img: FAILED
userdata_64G.img: FAILED
rawprogram0.xml: OK
rawprogram0_64G.xml: OK
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED

definitely looks like this phone is goofed big time so is there any way on fixing it?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=76112167&postcount=2
 
svnhvn

svnhvn

Senior Member
Aug 1, 2013
1,633
699
Jakarta, Far East
At last!! My Bacon revived!! Thank you Dev/s!!

Edit: Nope, false alarm. It went bootloop on Oneplus logo and cannot enter recovery mode.
 
Last edited:
J

jumis

Member
Dec 28, 2016
40
3
Hello. I do everything according to your instructions. the installation passes successfully but unfortunately after reboot the phone stops at the logo.
 
R

reginaldroshan

New member
Jul 20, 2016
1
0
OPO not powering on

Hi

When i run the Msm8974download tool on my windows8, im able to see my phone on the list but when i press start, it is only writing the msimage.mbn file and doesnt go past that. Please help

---------- Post added at 09:23 PM ---------- Previous post was at 09:03 PM ----------

Any solution for this bro?
 
J

jaynarang

Member
Jul 14, 2018
7
2
reginaldroshan said:
Hi

When i run the Msm8974download tool on my windows8, im able to see my phone on the list but when i press start, it is only writing the msimage.mbn file and doesnt go past that. Please help

---------- Post added at 09:23 PM ---------- Previous post was at 09:03 PM ----------

Any solution for this bro?
Click to expand...
Click to collapse
Change the battery of your phone. I also had same problem few months back. After trying MSM tool for atleast 2-3 months i got it working after i changed the battery and now its working flawlessly since last 4-5 months.
 
X

xinfernal

Member
Jul 11, 2014
29
0
--edit
solution for Unknown USB Device (Device Descriptor Request Failed)
seems random, didnt work on my desktop win 10, worked on my laptop win 10.
then after I gave up on everything for 2 hours I tried again and it worked on my desktop???
just keep trying and leave things to rest
///////////

Anyone have a solution to the msimage.mbn loop?
the phone disconnects when 80% of msimage.mbn is installed and it retries and loops from there.
-- edit
I solved this, by random it looks like.
I gave up yesterday evening and unplugged my phone from everything and put my pc to sleep.
This morning, started my pc (my cable was still in my pc but phone not connected).
Plugged my pc into my phone, it showed up in device monitor under ports as ""Qualcomm HS-USB QDLoader 9006 (COM7)", before it was ...9008 (COM6)
in the OPO tool, this time my opo showed up as AAIEe+ instead of com.
Previously it showed up as com and didnt work.
Now it worked
SEC6x6p.png

//////////

--edit
cyanogen loaded, but it keeps random reboot
and then it's hardbricked like before.
back to ...9008 and 'com' in the tool.
zzzzz
//////////

--edit
left it overnight unplugged again
this morning plugged it in, unknown device
unplugged, then held power button for 10 secs, then replugged into pc
shows up as --9006 in device manager
shows up as AAIEe+ in color os tool (no longer using the other tool just in case)
successfully rewrites
I go straight to fastboot and flash the stock OPO files
been working for 6 hrs now, should be ok.
 
Last edited:
A

adukale

Senior Member
Nov 27, 2012
70
22
Solapur-Pune-Mumbai
Hi
Like many people i am stuck with dead opo,when i use msm8974tool "8974_msimage.mbn" gets flashed and then phone gets disconnected. I used QFIL which flashed successfully but phone wont start.
So the opo is dead or is there any way i can get it working again?
Thanks
 
G

geminis65

New member
Dec 21, 2018
1
0
Muchisimas gracias de todo corazon, tengo un opo bloqueado por hardware y he estado a punto de tirarlo a la basura, habia probado varios metodos y nada y trasteando encontre vuestra pagina y lo he podido recuperar.muchisimas gracias por vuestra grandiosa ayuda.un saludo Ricardo
 
heisenberg_1205

heisenberg_1205

New member
Mar 9, 2019
2
0
Still under problem

I've performed procedures as stated.
But when I reboot the phone, the Red Oneplus Logo loads up but then phone automatically switches off.
Help!!!
 
A

Alchemist785

New member
Aug 18, 2020
1
0
How much time does it take to install the rom? My software seems to write things but there is no progress visible. No such dialog box. Start and enum button have become inactive though and stop button is highlighted. I am using Windows 10. Also I couldn't install the qualcomm drieves mentioned above even after running the commands of bcdedit. So I am doing it with the default updated drivers as I think the post is old. Although the phone is being detected on the msm8974 software.
 
T

trancinguy

Senior Member
Feb 4, 2013
355
83
Alchemist785 said:
How much time does it take to install the rom? My software seems to write things but there is no progress visible. No such dialog box. Start and enum button have become inactive though and stop button is highlighted. I am using Windows 10. Also I couldn't install the qualcomm drieves mentioned above even after running the commands of bcdedit. So I am doing it with the default updated drivers as I think the post is old. Although the phone is being detected on the msm8974 software.
Click to expand...
Click to collapse
I was in a bigger mess, locked bootloader, no ROM and no recovery, only fast boot. Kept searching on Google until I found a very old tool developed be two people from XDA, it restored my opo to Official Cyanogen KitKat 4.4.4, so try to look for it, If you can't find it, wait four days for me to post it.
 
L

lap87

Member
Sep 10, 2011
16
1
trancinguy said:
I was in a bigger mess, locked bootloader, no ROM and no recovery, only fast boot. Kept searching on Google until I found a very old tool developed be two people from XDA, it restored my opo to Official Cyanogen KitKat 4.4.4, so try to look for it, If you can't find it, wait four days for me to post it.
Click to expand...
Click to collapse

please post it, i am trying to save my OPO that i just now bricked when trying to restore to stock ROM from LineageOS 15.1.
 
T

trancinguy

Senior Member
Feb 4, 2013
355
83
lap87 said:
please post it, i am trying to save my OPO that i just now bricked when trying to restore to stock ROM from LineageOS 15.1.
Click to expand...
Click to collapse

OnePlusRestoreTool(64GB)

OnePlus One Recovery Tool (CM11) V.1.0 (64GB Only)

OnePlus One Recovery Tool made by Zxxeil and My Guinea Pig WEMZ
THIS PROGRAM IS ONLY FOR THE 64GB OPO
 
Last edited:
You must log in or register to reply here.

Similar threads

devilsshadow
[GUIDE] UNLOCK ADITIONAL BANDS FOR QUALCOMM DEVICES <OnePlus One EDITION>
Replies
1K
Views
663K
W
Warnold
Chromium
[GUIDE] OnePlus One - How to Unlock Bootloader, Install Custom Recovery and Root
Replies
1K
Views
629K
Kerrylee1738$$$
Kerrylee1738$$$
EddyOS
  • Sticky
[GUIDE] Return your OPO to 100% Stock (Current Build - CM13.1.2 - ZNH2KAS3P0)
Replies
1K
Views
662K
deathblade
deathblade
Heisenberg
  • Sticky
[GUIDE] Unlock/Root/Flash for OnePlus One
Replies
1K
Views
397K
Spannaa
Spannaa
the Doctor
  • Locked
[DISCUSSION][ROM][5.1]CyanogenMod 12.1 for Bacon[OFFICIAL Nightlies]
Replies
5K
Views
936K
D
Darth

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 171
    netbuzz
    netbuzz
    *** 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 (mirror needed).
    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: (mirror needed).
    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.
    View
    4
    Heisenberg
    Heisenberg
    Added to OnePlus One index thread:

    [INDEX] OnePlus One Resources Compilation Roll-Up

    Transmitted via Bacon
    View
    4
    M
    michaeldepotter
    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.
    View
    4
    nag4pl
    nag4pl
    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!!
    View
    3
    os_man
    os_man
    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.
    View

New posts