Oneplus Two - Solution for Hard Bricked Device

[yoncy]

[Edited] In the end it worked, drivers were recognised, and i was able to flash default package. I think it makes sense first to connect the device is USB debugging mode and install default ONE Plus drivers (correct One+ ADB interface). What was strange was that after flashing, somehow device return back to the step that was stuck (bootloop when try to fast oem unlock), and it was unlocked successfully. Also i don't understand how Oxygen 2.1 was installed from those file sources (thought the tool haven't flashed the rom, just rec, boot etc and then factory reset from the bootloader unlock). Thanks , good luck to you, but i think it's confirmed that it works.

Is there any alternative to flash recovery or bootloader manually? For no reason i cannot install those drivers. Doesn't appear to me in Device Manager, i had uninstall all the Alcatel ADB ****ing interfaces. Also my work PC, don't want to start always in advanced reboot to disable drivers signing. Since device is locked cannot fastboot flash, fastboot erase.

 

[fonz83.sa]

Worked for me!!
Thanks i love u!!!

 

[XIONTAZ]

This worked!!!

Got it into that mode, its now running the full recovery package. If this works I owe you 5 boxes of cookies or a bottle of Scotch my good sir!

For those with the same issues; indeed make sure your phone is 100% off (my phone for instance started booting for 2 seconds when I plugged it into my computer, it basically went; On (2seconds) off. On (2 seconds) off. Infinitely looping. Just hold that power button for dear life and tell your phone its going to be all okay and wait for it to turn off completely. Then what I did is hold the power button+ and - together for 1 second and my Device manager showed QHUB. Installed drivers, used the Full Recovery program and it's now got H2 OS on it again. Thanks to everyone in this thread and especially Lord Boeffla!

This.... this right here is what I did not know!!!! my screen was black the whole time but the computer detected it as a adb device because of the driver. After the computer detected it(keep in mind the screen on my phone was not showing anything), then i was able to successfully pick the driver that op was talking about. Then it detected it as a COM Port device labeled "Qualcomm HS-USB QDLoader 9008". Then the QCOMDownload Tool started filling up progress bars. Now im back to stock! Thank you OP for finding these tools and for everyone who posted their troubles about this issue! My phone boots, however its in chinese... any help on how to make it all stock english? Im sure im a dummy, may have even skiped the comments about it since i was trying to at least boot it earlier, but any links/help would be wonderful.

Never mind on the above, once i reboot everything after setup and picked english, the english option appeared on the recovery as well. Thank you for all.

 

[gyan1230]

Last link is not oxygen Os, it is Hydrogen OS

Hard brick for OPT happens when you change critical partitions. It will follow improper firmware flash or accidental erase of certain partitions. The phone won't show any response when hardbricked.
The solution for OPT is similar to OPO - you just need a Qualcomm driver and a recover package. The only full recovery package available is very big and it restore the phone to Hyrdogen OS, with everything wiped. So it would not be very attractive.
Fortunately, thanks to this post from Chinese supporting forum, a minimal version of restore package is provided. It does not wipe user data and guarantee a recovery entry. you would normally be freed using this package. if not, please use the full package in the end of the post
Download link for driver
Download link for Recovery tool
uncompress the files to a local folder.

First step, turn off drive signature enforcement in windows 8/8.1/10. Tutorial Here

Second step, hold the power key for 20 seconds to force turn off power. connect OPT to usb, hold volume+ and power until your PC finds a new hardware (if it doesn't work, try hold volume+ and volume- together)

Third step, go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics 9006" device. Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).

Fourth step, when the driver is installed properly, run MSM8994DownloadTool.exe in the recover tools folder, using admin privileges . Clear start in top left corner and wait for it to finish.

Now your OPT should be able to enter TWRP recovery. It still won't boot but you can manually flash anything again (like the full Oxygen OS package).
The procedure is tested by me twice. Enjoy!


p.s: sorry the recovery image in the A2001_save_brick_mini.rar is Chinese. Please download this file, change the name to recovery.img and substitute the file in the recovery tool before flashing.


UPDATE：full Oxygen OS 150805 restoration package for those who experience recovery entry problem. Note that this package wipes everything including internal storage!

I want oxygen OS restoration package

 

[ryhan67]

Hi, it need to delete adb driver first for qualcom driver ?

 

[Shane_IL]

Hi, it need to delete adb driver first for qualcom driver ?

I had the same question because the device first shows as an ADB device, in the end I just held volume+ and power for a really long time and it changed to Qualcomm whatever.

BTW this guide saved my ass, thanks so much to the OP and other contributors, really thought my phone was bricked.

 

[flomitdreio]

I just want to share my experience with you:
I was stuck in a bootloop, after relocking my bootloader. I followed every single guide and method I was able to find on the net.
No recovery what so ever, Fastboot was ok, so I tryed "fastboot continue" => and my OPT was finally booting up.
So I checked the OEM-Unlock is allowed in the developer settings => it was.
So back to the fastboot and I tried to flash recovery (did'nt work) and unlocked the bootloader (did'nt work as well).
But still no recovery, and I just could get my OPT recognized as a qualcom device.

But then I tried to unlock the Bootloader again, wich resulted in a black display AND finaly the device was recognized as a "QHSUSB_BULK".
So I flashed the Qualcomm drivers successfully and was able to recover the Phone withe the provided tool!!! (Did it with the full Oxygen OS 150805 restoration package)

THANKS a lot for that great guide!! (@Lord Boeffla and @qwsdert4)

Cheers

 

[Guihardrock]

i have this problem (drivers link in down)
my phone is the a2001 with unlock oem off and i can boot the phone in fastboot mode but when i try to boot in recovery appear a linux penguin
ps: if someone could uploade the drivers again would be awesome
thanks @Lord Boeffla could you help me please?

finally work but the link for drivers is down so here you have the drivers https://onedrive.live.com/?id=6E672...0!1932&authkey=!AE3uu9vmnSmrrL8&action=locate

 

[knonn]

It finally worked ! Thanks a lot.

 

[scarletbaron]

So I effed up adn am stuck on the same bootloop.
I would like to know how you forced OnePlus Two to enter QUALCOMM-HS mode?

Thanks for create the steps to get through this issue
Day 1 with the device and things went kaput

Hi,

anyone knows how I can force the OnePlus Two to enter QUALCOMM-HS mode?

I have a "semi-bricked" OP2.

It can boot, but the recovery is broken and I cannot enter it anymore. Worse enough, the bootloader is locked and I cannot unlock it anymore.

So I am kinda stuck and thought this manual would bring me back recovery. But - I cannot get it to enter this specific emergency recovery mode as boot loaders are intact.

Any idea?

Thanks
Andi

 

[knonn]

So I effed up adn am stuck on the same bootloop.
I would like to know how you forced OnePlus Two to enter QUALCOMM-HS mode?

Thanks for create the steps to get through this issue
Day 1 with the device and things went kaput

You just have to randomly push volume up or down when it bootloop to make it display a black screen. Don't go on the Fastboot screen.

Envoyé de mon ONE A2003 en utilisant Tapatalk

 

[scarletbaron]

You just have to randomly push volume up or down when it bootloop to make it display a black screen. Don't go on the Fastboot screen.

Envoyé de mon ONE A2003 en utilisant Tapatalk

Thanks! Thats what I didnt know the BLACK SCREEN was what I was looking for.

Well I know how I ended up in this position.
After my first initial root (which was successful) I was flashing SuperSU to complete my rooting process when suddenly my network signal completely dropped and nothing worked.
One forumer said relocking the bootloader and unlocking it again will help get the signal back. Which was what I was atempting to do and it got bricked.

Thanks to all of ya'll I was able to get it to boot to an OS but now I still remain with the same initial problem of no signal.
Any suggestions?

 

[knonn]

Thanks! Thats what I didnt know the BLACK SCREEN was what I was looking for.

Well I know how I ended up in this position.
After my first initial root (which was successful) I was flashing SuperSU to complete my rooting process when suddenly my network signal completely dropped and nothing worked.
One forumer said relocking the bootloader and unlocking it again will help get the signal back. Which was what I was atempting to do and it got bricked.

Thanks to all of ya'll I was able to get it to boot to an OS but now I still remain with the same initial problem of no signal.
Any suggestions?

Did you try to complete flash and test another rom? Maybe try another supersu rom to flash. Your TWRP is the last 2.8.7.0 version isn't it?

Envoyé de mon ONE A2003 en utilisant Tapatalk

 

[scarletbaron]

Did you try to complete flash and test another rom? Maybe try another supersu rom to flash. Your TWRP is the last 2.8.7.0 version isn't it?

Envoyé de mon ONE A2003 en utilisant Tapatalk

Yup I tried all of that. Except changing the SuperSu.
I do recall, 3 months backk when I rooted my bros OPO a similar issue happened where the network was lost. By changining his sim card again he was able to get it up and running. Im assuming it will be the same for me and will go to my operator tomorrow.
I also tried my sim on by OPO with an nano tray converter and it did not recognize, but my OPO recognizes my dad's micro sim.
Thats what I have narrowed all of this to

 

[knonn]

Yup I tried all of that. Except changing the SuperSu.
I do recall, 3 months backk when I rooted my bros OPO a similar issue happened where the network was lost. By changining his sim card again he was able to get it up and running. Im assuming it will be the same for me and will go to my operator tomorrow.
I also tried my sim on by OPO with an nano tray converter and it did not recognize, but my OPO recognizes my dad's micro sim.
Thats what I have narrowed all of this to

Well I don't know why this happens to you... Maybe you did something wrong, maybe not. I can't help you more, sry.

 

[scarletbaron]

Well I don't know why this happens to you... Maybe you did something wrong, maybe not. I can't help you more, sry.

You helped quite a bit! Thank you!

 

[TheDj408]

Hey @qwsdert4 @Lord Boeffla ,
I made a video guide for the same! Add this in your Post as it may help others! THanks for the GUIDE!
I personally Hard bricked thrice

 

[AlexandrosGreen]

Hey first post here!
And not for a good reason...First of all i have OPT about 48 hours, i have oem unlock the bootloader and using toolbox instal TWRP and flash SU! Everything after that was perfect! After few hours and WITHOUT using the phone i felt it damn hot like something was runing background, try to turn the screen on with touch id and the power button but didnt work...try combination of buttons but nothing again, i conected it on my laptop and push the power button for about 20 seconds and the phone started normaly like nothing have happend! Last night the phone sudenly was off again without any reason...I knew the trick from the first time so i tryed t do the same but the phone wont boot try to go on recovery but nothing...i tryed to make it with the downloadtool and on my laptop screen everithing goes well and get the green letters but on the phone just a blackscreen.
As i was pushing buttons trying to power the phone i got a vibration and a linux penguin on my phone screen can anyone help me? I can see my phone only on QUALLCOM device..

 

[pratyush997]

@Lord Boeffla, Thanks for the tip! H2 OS Recovery works great!

 

[levid_h]

This is why in the package I modified and posted here, I replaced twrp with Hydrogen recovery.

Andi

Got my OPT bout few days ago started messin with it had twrp, root and i tried installing AK kernel then sht went bad real quick.
My OPT had no OS and the recovery didnt want to boot, followed the unbrick instructions and got everything back !!!! Thanks BTW. But now i cant flash twrp.
i have oem unlocked, ive lock and unlocked it in adb fasboot and checked it with device-info just to make sure. So its unlocked for sure
I have tried the erase recovery and erase cache commands before flashing recovery but the device wont flash or boot into twrp.
the adb cmds tell me "okay" after flash so up to that point all is good but then i cant boot into it. ive tried booting to it using fastboot boot cmd after flash and manually holding up + power after the flash
but it goes into a bootloop if i hold the vol down button and wont boot recovery, the only recovery i can boot to is stock recovery.
Can someone help i just want toflash twrp so i could root and run xposed on my OPT like i had in my OPO.