yashsingh1/xdaforums huggingface dataset:
[ONE General] macem29:
bricked not one, but 2 of these devices back to back, because I'm especially dumb....

found this thread, did all that it said, with one exception....to get device manager to see the phone,

and then windows 7 to install the driver for the Quallcomm Bulk Device, I had to hold volume down,

and power button....after that, drivers installed, recovery tool connected and did it's thing....

voila! both recovered from the dead and on stock CM11S 44S.....

thanks so much OP for this, what a lifesaver.....like $1,000 CDN worth of stuff that was junk, and is now alive....awesome!
[ONE General] Moxie136:
Thanks man, this saved my phone today.
[ONE General] najay:
thanks from this side too! Running as Admin is critical, and it worked like a champ!
[ONE General] rajesheber:
How do we update this tool to include the latest CM12 files.
[ONE General] christian2101:
hello,

if it helps, my recovery does not work on USB 3.0 but much better than USB 2.0.

I have other problem, despite the success of the recovery, my phone still does not turn on. It gets stuck on the boot screen. i can't use de recovery, i have just access to that fastboot .

I think that the program was successful because it worked like YouTube video, except for the last step where it says "your phone should work now correctly" (which does not happen for me).

Do you have any idea what is going on and how do I fix it properly to enjoy my phone?

Thank you (I will delete this reply if necessary).
[ONE General] locius:
Hi! If I am on CM12 Stock can I use this tool to restore CM11S??
[ONE General] locius:
I have bricken my phone, first the PC has detected it , and I have started to flash, then the flash has stopped, and has not go on, and now my OPO doesn't do anything. And my computer says that the qhsusb_bulk can not be installed, what can I do?
[ONE General] koolanil81:
I am in a terible situation i need your help to bring my OPO back to life.

1. There is no OS in OPO (by mistake i wiped system, cache n dalvik cache also), thus i cant get into recovery mode.

2. When i connect my OPO via USB cable i could see all the folders intact but can't paste into that.

3. When i launch into fastboot mode i can see cyanogen mod logo and its stuck there.

4. If i try to reboot, i can see only 1+ logo and nothing else works.

5. As i have already rooted n unlocked boot loader earlier using OPO tool kit, i could enter into TWRP recovery but nothing is working there.

6. Using "adb push" command i have pushed CM11S and CM12S zip files into OPO, but its installing via TWRP and i am getting failed error.

7. I also tried "adb install [zip file] i am getting error "AndroidManifest.xml" file missing.

I have recovery tool, running in administrator mode. When i connect the device its not getting detected, nothing is happening no progress in the tool kit.

Kindly advice and provide help to bring my OPO back into life.
[ONE General] koolanil81:
Recovery tool kit error

As i mentioned above nothing is happening when i connect the device and start the tool kit. Here is the screen shot of whats happening.

P.S. - My device will be in fastboot mode(CM icon only) .
[ONE General] alex.inthi:
I have flashed firmware using this tool. Still its going to fastboot mode. Any solution?
[ONE General] xavierpitz:
You just made my day !

Unbricked my hard bricked One (fastboot & recovery were dead).

I had a lot of struggle to make the Qualcomm chipset been properly recognized by the USB driver.

But after that I was able to bring my one back to life.

Thanks a lot Zyxxeil for this tutorial the tool & Titokhan for the link to the proper signed x64 drivers :

http://xdaforums.com/showpost.php?p=58145465&postcount=48
[ONE General] royaltartufo:
Hi [MENTION=6639987]xavierpitz[/MENTION]

How did you do it, because i'm stuck on that part, my usb don´t recognize the OPO, and i try it 5 different computers.

I plug the dead device on differents usb ports and the device manager don't recognize the OPO

Thks
[ONE General] xavierpitz:
I used the x64 drivers provided by Titokhan

http://xdaforums.com/showpost.php?p=58145465&postcount=48

Also what is really really important is to use the correct keypress on the One when trying the heart massage to resurrect it.

Don't think the key combination is the same as the one used to trigger a fastboot.

You really have to press power & volume+ at the same time,

and keep the pressure on those keys for at least 10 seconds until you hear your PC detecting a new device

.

In your Windows Device Manager it must appear as an additional COM port.

As long as it not properly recognized as a COM port it won't work.

Monitor your Device Manager when you plug/unplug your phone.

Also be sure afterwards to start the recovery.exe program with admin privileges.

EDIT : start the

OnePlusRestoreTool(64GB).exe program with admin privileges

(right mouse button -> start as administrator)
[ONE General] Marmotul:
Hello Zyxxeil,

I have a bricked one after new OTA for CM12 - the system went dark and nothing is displayed.

I managed to install the driver and all the details, however I am stopped with a "SaharaD" message displayed and the program is not doing anything anymore

the OnePlus Restore tool shows the attached messaged

used the Msm8974DownloadTool.exe program from the Color.zip archive and I have same error in the end. Screen shot is showing the big button validation with the system etc corrupted. Screen shot for this attached

Before getting the "SaharaD" message there are some files that are loaded, probably the first one, but then its stuck on this.

Any hints to make it alive?

Thanks a lot
[ONE General] xavierpitz:
Hello Marmotul,

Are you sure it is hard-bricked ?

After the OTA mine was only soft-bricked, I still had access to fastboot (short vol+/power) & recovery (short vol-/power) so I managed to un-softbrick it with the following :

http://xdaforums.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 (USE OLD IMAGE XNPH05Q 16 or 64 GB)

by fastloading the XNPH05Q files with the flash-all.bat script.

One day after the YNG1TAS17L flash-all.bat version was released, and this was the one that led to my One been hard-bricked.

If you're still able to fastboot then use my previous link and instructions.
[ONE General] Marmotul:
Unfortunately the screen is black and nothing is shown (not even led for battery).

Keys combination are not working and cannot enter or see any option or any fastboot/recovery

After doing all the researches I think I fell in the hard brick pit.
[ONE General] xavierpitz:
Ok if you're sure that it is hard-bricked (fastboot & recovery dead), then follow this tutorial. I was able to resurrect my One this way.

Look at my comment #145 for my feedback about this tutorial. http://xdaforums.com/showpost.php?p=60464973&postcount=145
[ONE General] Marmotul:
As you saw in the screen shots - the phone when connected to PC is observed in the tool as well in Device manager as Qualcom ...

so I am not sure what to follow from that post

The only information that could assist would be "Also be sure afterwards to start the recovery.exe program with admin privileges. ", but where is the recovery program you state?
[ONE General] xavierpitz:
Hello, sorry, I should have said the "OnePlusRestoreTool(64GB).exe" with admin privileges (right mouse button -> start as administrator)
[ONE General] ammarii:
can anyone help me?

I follow all the steps

nstructions

1.) Connect your phone to your PC.

2.) Make sure the OnePlusRecoveryTool is open and your PHONE IS OFF.

3.) Hold Volume UP + Power

4.) Your computer should detect it (If not then install proper drivers, Look below)

5.) Click Refresh - Something should be different on one of the columns of the program.

6.) Click Start (Make sure Normal Restore is ticked)

7.) It should flash (It might take a long time to flash System.img and or Userdata.img sometimes)

8.) It will show green once its done, at this point you can disconnect device and hold power to reboot.

I got the green text but when I tried to reboot its not working just vibrate with black screen
[ONE General] xavierpitz:
If it is able to vibrate it is not a dead brick anymore...

Are you able to fasboot or go to recovery ? (power&vol+ for 2 secs or power&vol- for 2 secs)
[ONE General] ammarii:
No I tried

Holding power = vibrate and nothing shows (black screen)

power&vol+ for 2 secs = vibrate and shows Qualcomm HS-USB Diagnostics 9008

power&vol- for 2 secs = nothing at all
[ONE General] xavierpitz:
The fact that is able to vibrate wonders me... For me if it vibrates it is not hard bricked...

Anyway... If it is properly discovered in your device manager as a COM port you should be able to resuscitate it with OnePlusRestoreTool(64GB).exe .

Be sure to start OnePlusRestoreTool(64GB).exe as an administrator (right mouse click --> run as admin).

You may also screenshot the LOG. Maybe somebody else can help you further with this, but I'm afraid I can't help any further.
[ONE General] ammarii:
sure I ran it as admin

actually I tried several times now I'll just keep it to charge and try it on other computer
[ONE General] ammarii:
Hello there

I tried it again an I got the green text and still the same its only vibrates and nothing happens

here is a screen shot
[ONE General] silvagroup:
You said tested with Windows 8.1 and 7 but not 64bit version? because even with sig verification off Windows 8.1 does not see this driver as 64 bit. Unless the tags are reversed guess I'll try that next since it's only thing I haven't yet tried.

I have been at this for two days, post by post downloading everything I have run across here, and unfortunately am in the very same spot as when I started. And for the exception of less disk space, and who knows how many backdoors or other vulnerabilites I have introduced into my system, and yet here I sit with a black screen on my device.

If anybody with 64 bit Windows system and device with the black screen of death has truly been able to recover PLEASE post your step by step and drivers.

Biggest hang up from what I can see is the drivers right now. And unfortunately web search has not been fruitful in that regard at all either.

PS

No both the files must be 32 bit they won't on ^$bit system.

However I did finally deceide to go to Qualcomm downloaded the IoeDevelopment drivers, problem is which one theres got to be close a 100 hundred of them.

Saw 9006 is not it any one here have a clue ????

And is it the qcfilter, qcmdm, qcser, qcwwam. Oh yeah all have same amount.

Lleaning toward qcser since that seems to be the ones most mentioned here but again which one ???
[ONE General] royaltartufo:
Im on win7 x64 and try it all drivers and still on black screen and no vibration.
[ONE General] silvagroup:
Yeah. Windows seeing something. Tried in my Linux PC but doesn't pick up anything on USB at all, at least that I know could see, still exploring. Requested RMA from One Plus happened right after I received the device and it was updating the OS.

PS

Received a reply from One Plus which was mentioned in a previous post, and which also does nothing to fix this specific problem.

They have anything that hasn't been covered here in the thread already. You'd think they would but thread is considerably more informative although nothing that seems to be able to recover a device that can not fastboot.
[ONE General] slayeras:
Hello ,guys, I would appreciate some help if possible, my opo seems to be bricked, I can't do anything with it, its pretty dead. I have tried everything from windows xp to win 8.1 and different computers, my desktop , my laptop and I cant seem to see it in device manager so I can run the tool and recover my phone. Not bulk drivers no sounds when I plug it on my PC anything

It got bricked after trying to flash a cm11 because I had a lot of keyboard lag and ghost touches, the phone is unlocked rooted and twrp flashed. When it died it had 60% battery.

So please if anyone could help me, I am a step before throwing it to the wall...
[ONE General] spencerchong:
I'm on stock CM12S with bootloader unlocked, but no TWRP recovery (some weird annoying bug, can't boot into TWRP, eeps going to CM recovery) and not rooted.

can I use this tool to flash back to stock CM11S? Think I'll just stick with KitKat..
[ONE General] sir sniffalot:
I upgraded to CM12 and hated it, and phone would take 20 mins to re-start so decided to go back to CM11. In the process of downgrading I totally bricked my phone, totally unresponsive.

Then I found this thread and it worked a treat, took a few attempts before PC recognised the phone but everything worked out fine.

Excellent job, thanks!!!!
[ONE General] slayeras:
Nice to hear that you found a working solution, mind sharing with me because my pc cant recognize the phone whatever i do....

Edit: After a 24hr plugged onto a chinese wall charger and with no sign of anylife i just plugged it on to my pc it just popped up in device manager and i managed to fully restore it with the tool !!!
[ONE General] SpikyOrange:
Installer not showing progress bar

Hi, all the drivers and everything worked up until the installer then I got the same issue as to this guy:

www youtube com/watch?v=uc0seW9o6cI

(i removed the dots so that i could post the link)

Any fix? All help is appreciated
[ONE General] Zayn O'conner:
One Week.....

After one week of deep research of 3 threads. 1 week later finally got to unbrick my OPO.

First of this **** needs to be updated as hell. people giving bloody wrong drivers don't even work had to find the correct ones myself.

1) Disable driver signature enforment (check this if you get trouble ; )

2) Download Qualcomm Driver 2012.rar (sorry can't find link), extract to desktop.

3) Install Recovery tool and plug your phone in and hold VOL+ & Pow or (10secs around)

4) if you're PC recongizes you're good to go other wise try other drivers.

5) go to device manager, click on your OPO device and chose update driver software. Locate and Chose the Qualcom drivers.

6) open toolkit folder and open the toolkit as admin, you should see a line that's different than the others click on it then click START.

7) wait a lil bit and Voila.

8) Unplug phone and Hold Pow button for 10 secs then should boot into CM11S ;).

Process done with winds 8.1 64 bit.

Don't ask me any questions i ain't no pro just followed guides and stuff. Hope y'all get lucky :)
[ONE General] sheikhrr:
I wonder...if this driver could turn a Samsung GT7562 which is in 'Samsung CDMA technology ' into QDLOAD 9008 mode ?
[ONE General] Filko84:
Help!

I need help with flashing.

I have instaled driver, connected as 9008 mode.

Phone is recognized and start flashing. Text turns green but I can not go to recovery and still in boot loop.

The log says:

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

Any help for this problem?

System is Win 7 x64 with Qualocomm 2012 drivers.
[ONE General] taphius:
Mine was doing this, I had to uninstall all the previous phone drivers I had on my system (nokia recovery suite was interfering with it from my messing around with my 1520.3). Once I did that and reinstalled the qualcomm drivers it worked perfectly.
[ONE General] Dvoraak:
Ugh. I think I'm done. 1st ever hard brick and none of the recovery tools or threads has helped. No doubt there's a driver issue but after every tool or thread has had me uninstalling and then reinstalling different drivers, some with command prompt help, some not, I don't even know where to start looking anymore. Once again I followed the instructions here (including the QPST) and no joy. My computer recognizes the phone and it shows up in devices, however nothing changes in this recovery program. No com line or green bars. If I hit start 3 columns fill up as if they just instantly installed. I think this OPO may be ready for the trash heap.

I know it doesn't sound like I'm asking for help but I really am...... Please?

*Edit* Nevermind.... Updated the qualcomm drivers for the 4th time (maybe the 5th) and that did the trick. Green progress bars and fingers crossed.

*Edit* SUCCESS!!!! So happy So happy and many thanks to Zyxxeil
[ONE General] Cerviche:
Newbie here

I have a question, what if i want the 25R version, can i just swap out the files in the recovery tool with the 25R files? or is there more to it?
[ONE General] Bittornado:
Actually I was wondering over the same question exactly! 44R has at least on my device showed a lot of battery exhausting problems, so 25R would really be my choice of reverting back to if possible...
[ONE General] pludgate:
Edit* Fixed my problem
[ONE General] DJayDeee:
I'm so happy!

Thanks you everyone.

You must be patient, it took me about 6 hours.

My problem was the driver and the solution was to install WinXP on another drive and the step 4 of the post #48 (Qualcomm 2012 drivers).

I also replcace the files in OnePlusRestoreTool folder with the YNG1TAS17L version.
[ONE General] blindwalker72:
Hey Guys!

I've read the whole thread now but still couldn't get it to work..

My problem was mentioned already:

-The phone isn't responding at all but can be detected by windows

-After installing the qualcomm drivers (tried all ever posted in this thread) the device is listed as "Qalcomm HS- USB QDLoader 9008" in the device manager

-When starting the OnePusRestoreTool (in Admin-Mode) the device is detected correctly

-After clicking start the file msimage.mbn starts to be flashed but before the green bar reaches 100% the phone gets disconnected

I've read that this could happen due to the wrong driver. I've already tried using the included Setup.exe in the "Drivers" directory, but it didn't help.

The setup was finished the first time I started it - i rebooted but the device could not be found by the OnePlusRestoreTool afterwards. Whenever I launch the Setup.exe now it just starts for a second and then closes automatically.

I'm currently on Mac using a VM running Win7 x64 - also tried running XP x86 with same results.

thanks in advance
[ONE General] SpikyOrange:
Frozen at installer

Hi, i tried your guide, and it all worked up to the point of the recovery tool. I clicked start, in 1 or 2 seconds the text became red, then froze on the word sahara.

youtube. com/watch?v=uc0seW9o6cI

This is a video of how it looks like, it is not mine. I have tried turning it on and off and all that but nothing works, could u suggest anything else to do?
[ONE General] taufiqs:
Hi. Need help!

I have install the driver and foolishly delete it. And now device manager didnt detect my qhusb_bulk or qualcom hsusb dloader 9008 anymore. Only unknown device under USB controller section.

Any idea?
[ONE General] taufiqs:
it shown not for windows x64? WTH? LoL

I guess i have to use windows xp then
[ONE General] flod10:
phone bricks

please, I need some help.

I follow all the steps on restor stock and in the final, when suppose to show me with green everything is ok, on the pc show me red and the phone is death.

any suggestion, please

sorry for my english
[ONE General] Filko84:
I have instaled several drivers.

Tried on fresh XP instalation, tried Qfil, MiFlash with same result.

All of this flashing tools complate with succcess but at the end I get only logo, no recovery, no OS to boot in!
[ONE General] HouseBeatz:
[MENTION=3929963]Zyxxeil[/MENTION] [MENTION=2217166]Conos[/MENTION]

Need your help - cant get it working, although devices is recognized from windows - the tool does not recognize.

I read everything in this thread, followed all steps but cant get the recovery working. I would really appreciate if you could assist me:

So as i said Windows recognizes my phone and in device manager it says Forge HS-USB QDLoader 9008. I tried to update that driver with the Qualcomm drivers posted in the thread but it says that I already have the actual drivers and does not overwrite them. I also installed the USB Drivers out of the DRIVER directory, but nothing helps. Same with QPST.

The tool does not recognize the phone, I have no idea what to do now to get this working.

Please help me with that :/

Thanks guys

EDIT: Got it working, had to force windows, not to install this Forge Driver...

Thanks anyway for this Workaround!
[ONE General] vineetjain77@gmail.com:
OPO starting issues

Dear [MENTION=3929963]Zyxxeil[/MENTION] - Thanks for sharing following procedure. I think you have given the 'downloads' in another post, but I saw that there were 3 web-links for downloads. So I did not understand which one I should pick for my OPO. Could you kindly give the web-link on this post, so that I could pick that? I will be really obliged. Kind Regards.
[ONE General] :
I really need some help with this. I'm getting nothing but the "Sahara" error. See this webm to see the process I go through on this tool and on the Color msdownloader. tinyurl.com/onevr6y
[ONE General] kthejoker20:
Glad someone finally did this, since all the latley cm12.1 have been bricking phone due to baseband updating issues
[ONE General] bobby2189:
usb device not recognized

I followed all the steps and installed all the drivers.

I get to the point where msimage.bin runs and the phone disconnects, and then reconnects as its supposed to.

BUT once it reconnects I get a "USB device not recognized or malfunctioned error" from windows. and of course the tool just freezes at that step.

Any one have any ideas?
[ONE General] ninjawulf98:
So I tried both this flash tool and the color os one.

I have with both the same isue that it shuts down after flashing 8974_msimage.mbn and it stops flashing and doesn't automaticly start the flashing again.

Yes ,I gave it administrator rights, I tried it with a clean windows xp computer, different cables, etc.

Actually my device isn't hard bricked but currently I cant flash any file through fastboot because the bootloader is relocked and I can't unlock it through the "fastboot oem unlock" command.

This is a very short explaination of the problem and I created a thread with some more explanation about the problem.

Any help is appreciated.
[ONE General] lephoenix73:
Any plan to update OPO Recovery tools to latest CM12S ?
[ONE General] NickosD:
I see the device at device manager as CMCC COMPOSITE ADB Interface under CMCC ADB Device. I am trying to install the qualcomm 2012 drivers and it says that the drivers are up-to-date. I tried unistalling them. Any ideas?
[ONE General] djhixson88:
Need help please (even though probably won't be for a while because of the OnePlus Two) but I've managed to get the proper drivers installed and am on windows 8.1. When I go to run the recovery it just keeps repeating the first flash which is 8974_msimage.mbn. I'm at a complete loss at this point after a week of trying to get the drivers on here for it to do this. Please anyone help I'd appreciate it.
[ONE General] hafiz_binshah:
perfect it returned my phone from dead :D
[ONE General] sihag:
Yup it worked eventually after 1 hour or so.

1.) Use Volume down and Power Buttons for 10-15 seconds while connected to USB.

it will show something like starting with a and not com.

2.) Just press start and wait. it will turn green after flashing files.
[ONE General] Kirlus:
Sahara

this guide did not work

if i press start no bars appears only xxxSaharaxxx is written

pls need help and sry for bad english
[ONE General] K4iZEN:
[MENTION=3929963]Zyxxeil[/MENTION] [MENTION=2217166]Conos[/MENTION]

to me it looks like my phone will stay dead.. I installed every driver. Made a clean installation and therefore it said "unknown device". After installing QPST, the "unknown device disappeard" and now it shows nothing up in the device manager. Also the tool won't recognize anything any1 got a possible solution for this one :(?
[ONE General] Younex:
Hello

I'm on CM11S and I want to update to Cyanogen OS 12.1

Is it possible to use this tool to restore CM11S later ?

Stock unroot locked bootloader