[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3

[Mit Hipster]

Hello everybody!

I received my OP3 on Wednesday and I was so happy with it but yesterday, I took it out of my pocket and it wouldn't boot anymore (I haven't tried to flash it or to install a custom rom on it or anything, it happened spontaneously!). I recognised it was bricked quite quickly since I'm familiar with such things and I tried to boot it blindly in recovery mode, trying different combination of buttons. I managed to access a raw menu from which I think I performed a factory reset.

The problem is, since I wasn't sure about what I was doing and that the procedure was getting longer and longer, I lost patience and tried to shut down the phone... Big mistake! Now, the phone isn't doing anything anymore, impossible to access recovery mode or to make it display anything. I tried power cycling it as well but nothing changed.

So I found this guide, tried method 1 two times then method 2 then method 1 again and everytime the same result : No device, Sahara communication failed or firehose getufsinfo failed at the msmdownloadtool step (The phone is being recognised by my pc and the driver step is ok). I didn't manage to do anything else.

I'm so frustrated, the OP3 is great, it's my first high tier phone and I really enjoy it but a random brick after only 3 days without even trying to flash it or anything, you've got t be kinding me...

Please help, I don't want to send it back to customer support since I'll be traveling soon and I know I wouldn't get it back before my departure...

Sounds like bad hardware. You should probably request a replacement. Or, better yet, just return it and re-order, since you are within the 15 day return period.

 

[Skrawlr]

Sounds like bad hardware. You should probably request a replacement. Or, better yet, just return it and re-order, since you are within the 15 day return period.

Well, I was hoping it wouldn't come to that but ok, I wrote a service ticket, I hope it's going be quick! I will come back and report on what happened in case anybody is interested in the future.

Thanks for your post!

Edit 1 : Dropped the phone at a UPS point on monday and received an email today saying that they are going to release the replacement order to be processed. I'm still hoping it's gonna be quick, my guess is I will receive it at the end of next week.

Edit 2 : So during the process, I was contacted by an actual human asking for a few more information about the shipping adress, I responded subtly and kindly asking for a little compensation (i.e. a free phone case) but I didn't get any news on that side. Anyway, I received the phone yesterday so 8 days after dropping the previous one, wich is totally decent. I would have appreciated a compensation from OnePlus tough but in the end, very reactive customer serice, would recommand!

 

[itrystuff]

@Naman Bhalla: Thank you for this unbrick method. Method 2 worked for me.
However, like others here I get the ominous md5 fail messages after trying method 1. You said to others "don't check md5 sums" or "why do you check md5". The truth is nobody did this. The phone does this! I will attach a screenshot here in a few minutes so you can see what's happening after using method 1 and trying to boot.

And now I have some questions about security. I have no clue what the program did at all, where the drivers come from and how I can be sure there's not any malware installed that may hurt my privacy or finances in the long run. Don't get me wrong, I'm not accusing anybody of anything. I just feel uncomfortable not knowing what happened and not having a method to fully check the devices integrity. Is there such a method? At the moment using this tool, the drivers and all is based solely on trust. The web space where the unbrick tool is hosted, is it safe? May it become the target of a hacker attack one day?

 

[armandem]

Thank you soooooooooooooo much for this!
Being new to rooting (and an all round moron) I relocked my bootloader when the device wasn't anything close to being stock. This guide was so helpful in correcting my mistake.

At first I was stuck because 900E looks a lot like 9008 -.-
But the real issue was with step 7 and trying to get the MSM Download Tool to work. It just wouldn't find my device even though I was sure I had everything necessary installed.

In any case; this allowed the computer to find it, so if you're in the same boat as me I hope this helps.
Perhaps in the long run this post might save the support team more time than I wasted for them... although I doubt it...

Anyway, good luck and have a great day!

 

[Naman Bhalla]

@Naman Bhalla: Thank you for this unbrick method. Method 2 worked for me.
However, like others here I get the ominous md5 fail messages after trying method 1. You said to others "don't check md5 sums" or "why do you check md5". The truth is nobody did this. The phone does this! I will attach a screenshot here in a few minutes so you can see what's happening after using method 1 and trying to boot.

And now I have some questions about security. I have no clue what the program did at all, where the drivers come from and how I can be sure there's not any malware installed that may hurt my privacy or finances in the long run. Don't get me wrong, I'm not accusing anybody of anything. I just feel uncomfortable not knowing what happened and not having a method to fully check the devices integrity. Is there such a method? At the moment using this tool, the drivers and all is based solely on trust. The web space where the unbrick tool is hosted, is it safe? May it become the target of a hacker attack one day?

This is the Qualcomm tool, which even OnePlus uses for fixing devices. So, don't worry of the security.

Sent from my OnePlus 3 using XDA Labs

 

[Krasendo]

This is the Qualcomm tool, which even OnePlus uses for fixing devices. So, don't worry of the security.

Sent from my OnePlus 3 using XDA Labs

Hi get something like @ itrystuff. What should i do? I dont check md5 checksum...

 

[jakkasirish1925]

device not detecting in msm tool..

my device is not being recognized in the MSM tool, I am running as admin.

in device manager under "PORTS" my device says "RELINK HS-USB QDLoader 9008 (COM5)....should it say this or something else? I understand the COM port could be different, though.

driver signature is turned off as well..

update: hold on, it may be working now....in the MSM tool under "Communication Status" it is downloading various system files now

---------- Post added at 11:01 AM ---------- Previous post was at 10:42 AM ----------

coolness, all is well now. Device is now booted up and I am going through the setup, right now. Thanks a lot!!!!

hello sir...
I accidentally wiped everything(including system data and something else) using the twrp recovery and ended up with no os installed...by using the "all in one tool" i hav locked the bootloader and flashed the stock recovery and i followed the METHOD 2 according to the instructions but my device is not detecting in the msm tool..after starting the tool there's nothing showing the communication status...But in the device manager my device is detected as "RELINK HS-USB QDLoader 9008 (COM3)"....please help me..sorry for bad english

 

[lukazzo]

after this i can lock bootloader?

 

[Mit Hipster]

after this i can lock bootloader?

If you plan on flashing custom ROMs, kernels or rooting, then leave the bootloader unlocked.

 

[Nadiro2000]

Thank you sooooo muuch bro'

 

[jakkasirish1925]

Got fixed my oneplus 3 by using the 1st method.. Thank you soo much

 

[shamsadnan]

Qualcomm driver not installing saying has in file is missing

 

[Fernix_]

But won't Oneplus fix the phone? Because unlocking the bootloader doesn't void the warranty. Or it doesn't work that way?

 

[2x4]

am i missing it, or is there not a guide for the basic universal unlock your BL, flash custom rom, return to stock, lock BL stuff?

 

[néonaloj]

And guys, NEVER EVER EVER Lock bootloader unless phone is completely stock.

If you plan on flashing custom ROMs, kernels or rooting, then leave the bootloader unlocked.

But guys, what if I want to sell my phone, wich is the case? So can you please tell me the secure way to lock back the bootloader?
If I am on stock recovery, with OOS installed, it should be all right, not?
Many thanks!!

 

[Mit Hipster]

But guys, what if I want to sell my phone, wich is the case? So can you please tell me the secure way to lock back the bootloader?
If I am on stock recovery, with OOS installed, it should be all right, not?
Many thanks!!

Do a complete wipe, flash the stock ROM, and then go into bootloader mode and, using fastboot, lock bootloader with the "fastboot oem lock" command.

 

[néonaloj]

Do a complete wipe, flash the stock ROM, and then go into bootloader mode and, using fastboot, lock bootloader with the?*fastboot oem lock command.

Thanks for your reply!
Did someone tried that method successfully?? 'Cause it looks like problems are coming when trying the re-lock the BL...

 

[Fernix_]

Thanks for your reply!
Did someone tried that method successfully?? 'Cause it looks like problems are coming when trying the re-lock the BL...

As far as I know there is no problem locking the BL when you have stock recovery, stock rom, no mods, and no root, AKA full stock. Anyway, if you are unsure about anything related to messing with the bootloader go read some guides and do your research. Hope I helped.

 

[acmerw]

before sending to rma i flashed with msm download tool full stock fw, relocked bl, no brick. if anyone having problems with sensors, laggy camera, i recommend to contact CS for rma service, they will replace motherboard (as for mine op3).

 

[mstrub]

Can't get device to be Listed as 9008

After I hold the volume up button for 10 seconds and plug the phone in, it shows up in my computer as Qualcomm HS-USB Diagnostics 900E (COM3), I have tried all the drivers/methods listed in the guide and none of them update it too the 9008 that should be listed. Anyone have any ideas?